JAIL REASON #4838
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4838
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?
*We need to structure the /jail command so that a reason is required to complete the action. There is no rush because you can jail someone whether they're online or not, unlike most commands - so while doing it quickly is often times fels like a serious need, you in fact do have a few seconds to write a reason.
This would mean months later when the player returns staff can evaluate what the next move should be - which involves going into jail chat and asking them to explain how the reasons they're in jail aren't going to happen anymore or they start with bans (day/week/month/year/perm) whatever is needed.
We can't ask if someone has learned a lesson and then not know what the lesson was supposed to be.... well we can but I'd rather know what went wrong.*
Or, if someone goes to jail, a /report will automatically open here. Here are the names of the two participants, as well as a time stamp. Then you can write a few lines, perhaps with the first results of a conversation.
verbana expects a reason when banning someone or otherwise changing their status, though it can be omitted. people were pretty good about recording why something happened on bls, though.
Duplicate of #3323 takeaway9. But since there is no proper documentation there:
/j
can be just an alias for/jail
.REASON
can be optional argument.Doing quick
/j NAME
and after that/jail NAME REASON
could just append the reason to the record/log.With the introduction of tags, what should we do with this issue? Do tags suffice?
For me tags would be ok for documentation of the longtime jail reason.
IMO tags are good.