debiankaios reports: fast mails with /mail <player> ... #1661
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1661
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
debiankaios reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
There is already a was to write a mail to opffline users. Do /m PLAYERNAME MESSAGE. If the player is not online, they will be sent a mail.
Regarding your "fast" way: ´/mail player topic message´ will most likely confuse everything, when topic or mesage contains a blank. It needs to be something along /mail player$topic$message or similar.
i think there should just be
/mail [player [topic topic topic]]
, where[]
indicates optional parameters and not any sort of delimiter.no need to compose the whole mail via command, as alias says, do
/m playername message
if you want to do something like that.I do see some benefit to implement a command but its a very specific request which should be solved in a more general sense. We can implement this if we really see a need, know how to do it and what exactly we want to achieve with it. So far it only solves a very small problem. So I'd give it low prio and a maybe result.