dubious interpretation of use / interact flags

[kikelkik]

Versions WorldEdit version: 7.1.0;8e55131 WorldGuard version: 7.0.2 (release) ; 7.0.3-SNAPSHOT;2036-47cd96a (latest dev) Platform version: git-Paper-260 (MC: 1.15.2) (Implementing API version 1.15.2-R0.1-SNAPSHOT)

Describe the bug

To Reproduce Flags: resulting permissions for a nonmember within the region dis_61 (global: use ALLOW, interact NONE):

• harvest beehive? NO
• open/use beacon? NO
• open/use anvil? YES (should be "no")
• trigger tripwire? NO (should be "yes")
• trigger pressure plate? YES

with global: use ALLOW, interact ALLOW within the region dis_61

• harvest beehive? YES (should be "no")
• open/use beacon? YES (should be "no")
• open/use anvil? YES (should be "no")
• tigger tripwire? YES
• trigger pressure plate? YES

Example conclusions:

• It seems to be impossible to allow tripwire triggering AND deny beacon changes on protected regions.
  • why isn't tripwire affected by the use ALLOW? It should work equivalent to a pressure plate (USE)
  • a beacon could also be affected by chest-access because its technically an inventory you're opening
• anvil usage is not protectable, anvils get damage when they're used -> not cool
  • same as beacon: why isn't it managed by chest-accesss?

[kikelkik]

So could you already take spend a bit of time for this ticket? :)

[TheoRetisch1]

I have the same problem, I also want to protect beacons, berry bushes and bee hives while allowing other non-harmful interactions. I think the logical limits on the actions are very easy to define: Anything that in itself causes immediate harm (such as changing a beacon effect, destroying an anvil ...), should not be allowed by the interact and use flags.

[kikelkik]

Do you have a chance to get further with this? :)

[IamTheRichie]

I have the same problem with protecting berry bushes and bee hives and I would love to see the proposed flag differentiation being implemented.

[kikelkik]

I would appreciate any reaction on this