EngineHub / EngineHub/WorldGuard

dubious interpretation of use / interact flags

Open
#1,574 5 comments 0 reactions 0 assignees View on GitHub
status:pending type:bug
Dominant language
Java
Stars
938
Forks
671
PR merge metrics
No merged PRs in 30d

Description

**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:
![Screenshot_1](https://user-images.githubusercontent.com/14167723/81343452-4e93a280-90b5-11ea-8fbf-a45afeab77b2.png)
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?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.