My idea on the areas protection system #1378
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1378
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?
If I'm not mistaken currently the contents of the default chests and armor stands can also be used by those who do not own the area.
The steel anvil and doors are usable only by the owner even if they are in free areas.
And there are other types of protection for container objects.
I would propose something different.
Everything in the protected area can only be used by the owners including the contents of the basic chest. Then the exception is possible by creating for example a free chest (or any other object) that can be used by anyone.
a "shared" armor stand is already a request - #374
you can craft an anvil into a public version with a piece of paper.
there are a variety of doors, some of which are public, some of which are owned by a specific player, some of which are protected (shared by everyone in a region).
on blocky survival, i did end up implementing an override whereby unlocked chests became protected, and created explicit "public" chests. https://github.com/BlockySurvival/bls_custom/blob/master/custom_items/public_chests.lua
Nice. What i meant was to have a uniformity of behavior in a protected area where everything should be protected by default.
I imagine that the area protection system acts exclusively at the node level and therefore not prevent opening a chest and taking and putting items inside it. Instead each protected object as a locked chest has its own protection system indipendent of the areas.
Here's the code I wrote to augment various items with inventories with protection:
https://github.com/BlockySurvival/bls_custom/blob/master/node_inventory_protection.lua
Making open chests protected in protected areas would be a bad idea. Most advanced players use them to exchange items or as donation chests.
New players may not be aware of the existence of locked chests, but then...they don't know much about other things either and need to learn sooner or later. If they managed to protect their area, they're at least slightly advanced already.
we wouldn't change the behavior of default chests w/out providing another solution for this. the point is to change the default behavior to something that's not as hostile to neophytes.
I'd like to close this as "maybe" and solve this in the chests and doors unification issue: your-land/administration#172