Labels
Depends on balancing 1. kind/breaking
something that alters or disables an existing game mechanic 1. kind/bug
Something is not working 1. kind/construction
A build needs fixing 1. kind/documentation
Needs proper documentation 1. kind/enhancement
New feature 1. kind/griefing
players despoiling builds or nature 1. kind/invalid
Not a valid report, e.g. created by mistake with no content. 1. kind/meme
issue is mostly a joke 1. kind/node limit
something which works for or against the node limit 1. kind/other
Something not within the other kinds 1. kind/protocol
something concerning how staff should react to player requests, or how players should treat each other 2. prio/controversial
not likely to happen w/out a lot of discussion 2. prio/critical
Very important 2. prio/elevated
something players are eager to have fixed 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. 2. prio/low
Not so important 3. source/art
art needs to be created or found for this to exist. includes sound and 3d modelling. 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/integration
Two or more nonbuggy mechanics conflict 3. source/lag
A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues 3. source/mod upstream
Problem is upstream (not engine/client) 3. source/unknown 3. source/website
Affects the website 4. step/approved
Alias has approved this feature, someone should implement it 4. step/at work
Being worked on 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/help wanted
Need some help 4. step/needs confirmation 4. step/partially fixed
this is mitigated or partially solved, but more work needs to be done 4. step/question
More information is needed 4. step/ready to deploy
has been QA tested by another person. has no outstanding issues. may be installed but unverified on prod 4. step/ready to QA test
the code is fixed, but needs to be tested. 4. step/want approval
Someone can quickly implement this if Alias approves the change/feature 5. result/cannot reproduce 5. result/duplicate
This issue or pull request already exists 5. result/fixed
problem is fixed 5. result/maybe
Needs more research 5. result/wontfix
This won't be fixed ugh/petz ugh/QA main
That's something we can only wait and see whether it hapens again: On the main server ugh/QA NOK
Fix didn't yield the expected results ugh/QA OK
tested
Apply labels
Clear labels
1. kind/balancing
Depends on balancing 1. kind/breaking
something that alters or disables an existing game mechanic 1. kind/bug
Something is not working 1. kind/construction
A build needs fixing 1. kind/documentation
Needs proper documentation 1. kind/enhancement
New feature 1. kind/griefing
players despoiling builds or nature 1. kind/invalid
Not a valid report, e.g. created by mistake with no content. 1. kind/meme
issue is mostly a joke 1. kind/node limit
something which works for or against the node limit 1. kind/other
Something not within the other kinds 1. kind/protocol
something concerning how staff should react to player requests, or how players should treat each other 2. prio/controversial
not likely to happen w/out a lot of discussion 2. prio/critical
Very important 2. prio/elevated
something players are eager to have fixed 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. 2. prio/low
Not so important 3. source/art
art needs to be created or found for this to exist. includes sound and 3d modelling. 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/integration
Two or more nonbuggy mechanics conflict 3. source/lag
A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues 3. source/mod upstream
Problem is upstream (not engine/client) 3. source/unknown 3. source/website
Affects the website 4. step/approved
Alias has approved this feature, someone should implement it 4. step/at work
Being worked on 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/help wanted
Need some help 4. step/needs confirmation 4. step/partially fixed
this is mitigated or partially solved, but more work needs to be done 4. step/question
More information is needed 4. step/ready to deploy
has been QA tested by another person. has no outstanding issues. may be installed but unverified on prod 4. step/ready to QA test
the code is fixed, but needs to be tested. 4. step/want approval
Someone can quickly implement this if Alias approves the change/feature 5. result/cannot reproduce 5. result/duplicate
This issue or pull request already exists 5. result/fixed
problem is fixed 5. result/maybe
Needs more research 5. result/wontfix
This won't be fixed ugh/petz ugh/QA main
That's something we can only wait and see whether it hapens again: On the main server ugh/QA NOK
Fix didn't yield the expected results ugh/QA OK
tested
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/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
Milestone
Set milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Assign users
Clear assignees
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#3685
Reference in new issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
No
Yes
this would allow staff and bailiffs to grant/revoke tnt/cannon privs. ability to use tnt is often requested, and it should be relatively "safe" these days, though it can clearly be abused to destroy landscape or unprotected things. it should be off by default, but we should be ok to grant it, so long as we can fix the major issues programmatically.
cf. #3401
I don't really see an advantage in giving players Tnt privs even if just being given by bailiffs/Staff. I mean we have so many report about destroyed landscape which are still not fixed, Tnt will just increase it. Or what's the advantage of giving tnt? For what will they use it?
it's moreso so they can place cannons. also, people keep asking for tnt privs, though i personally wouldn't give it to everyone who's asked.
using tnt to destroy the landscape would be a quick way to lose tnt privs.
I also think that most people ask for the priv to get cannons and not tnt.
Its a bit sad that alot of times this might be denied because of tnt and as a first step I would suggest moving tnt to a seperate priv. Of course explosive cannonballs would require both privs.
I don´t see many real usecases for tnt but need to reread current tnt limits.
Before a priv is distributed, it should be clear what it is intended to serve at all.
I couldn't think of any other reason to use TNT than to test the effect of TNT on our walls, because Voice started placing TNT. That's why we organized the TNT Bailiff event.
In addition, there is no reason to ignite TNT. As far as I'm concerned, TNT can disappear from the game altogether. Of course, we can't ban the boom blocks on Voice, but we don't need to.
perhaps we should separate TNT from the cannoneer priv, and make it a creative-only item?
I've heard from some players on other servers in the past (might even have been MC) that they intended to use TNT for landscaping. The TNT holes would then form a random base from which their projects could proceed.
Based on what I've seen about terraforming, I'm very reluctant to have players use TNT. In some rare exceptional situations it might be used in a good way. Most of the time it wouldn't. In such rare cases where it's justified it wouldn't be too much of a burden to have staff take care of what is needed.
Other than that - we might have a special small area like for the wall testing event where players could place TNT to see how it works and play with it. But...the fun is limited, and it's not really needed.
Perhaps a decorative TNT block could be useful here and there. But then, TNT has been invented/used for explosions from 1889 onward - not excactly medieval. Doesn't fit in.
Cannons are another factor. They're pretty useless as a defense against the Voice, and the cannonballs should definitely not destroy the landscape (only entities!), but still - cannons are a valuable decorative element for many fortresses and city walls. Builders need to be able to place them where needed. Perhaps a priv like oceanbuilder could do?
That's a good idea.