47 labels
1. kind/breaking
something that alters or disables an existing game mechanic
1. kind/invalid
Not a valid report, e.g. created by mistake with no content.
1. kind/protocol
something concerning how staff should react to player requests, or how players should treat each other
2. prio/good first issue
the resolution to this is could be done by a new minetest contributor, who doesn't yet understand the mod ecosystem
2. prio/interesting
one of us has real interest in getting this implemented or fixed. however, more research might be needed.
3. source/art
art needs to be created or found for this to exist. includes sound, 3d modelling, and in-game building.
3. source/client
Issue is with the minetest client, or with player client configuration or the technical details of their setup
3. source/engine
Issue is due to a bug or feature of the minetest engine
3. source/ingame
Problem and solution exist in-game, e.g. builds or player moderation
3. source/lag
A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues
4. step/approved
Alias has approved this feature, someone should implement it
4. step/blocked
we plan to do this, but other work has to be finished first
4. step/discussion
issue is under discussion, a solution has not been dictated or agreed upon
4. step/partially fixed
this is mitigated or partially solved, but more work needs to be done
4. step/ready to deploy
has been QA tested by another person. has no outstanding issues. might be installed on prod, but needs final testing
4. step/ready to QA test
the code is supposedly fixed, but needs to be tested.
4. step/want approval
Someone can quickly implement this if Alias approves the change/feature
5. result/wontfix
the reported issue won't be changed, whether it's intentional or not.
ugh/QA main
That's something we can only wait and see whether it hapens again: On the main server