Issue codes and lists #2926
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#2926
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?
What if there were half a dozen (at most) general report player codes, like:
22 failure to replant
33 disruptive/trolling
44 suspected cheating
55 you get the idea
then I could say /report NAME 22 (for example) and that 22 could be added to a list that I can see with a command like /22 =or= even added to the join information on that player. Then they can be watched to see if they learned or educated about the issue, for instance one today simply didn't notice that plants need to mature thru several stages, and that is probably the only reason they weren't replanting.
But mainly to add functionality to the report mechanic to make staff/bailiff job a bit easier.
/report PlayerName [any sentence with replant in it] could be parsed into 22 and added to list
I can see how replanting needs 22a and 22b
22a willful neglect
22b not understanding peppers/melons or picking prematurely
This seems to be related:
#4214
as much as love the artistic potential of trying to create a system to categorize the world, i don't personally think this proposal would be very useful. i could learn this system easily enough, and daydream would learn it by living it constantly, but i can't imagine anyone else would use it, and instead just use regular language to describe problems, as we do currently.