Confuse handling of lectern
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Reproduce the behavior on WorldGuard 7.0.8-beta-01 with WorldEdit 7.2.12, Paper 1.19.2, and a region using interact=true and chest-access=true. Verify that taking and returning a book from a lectern both work without build permission, while preserving the stated region restrictions.
Written by the indexing model from the issue text.
Description
WorldEdit Version
7.2.12
WorldGuard Version
7.0.8-beta-01
Platform Version
git-Paper-141 (MC: 1.19.2)
Confirmations
- I am using the most recent Minecraft release.
- I am using a version of WorldEdit compatible with my Minecraft version.
- I am using a version of WorldGuard compatible with my Minecraft version.
- I am using the latest or recommended version of my platform software.
- I am NOT using a hybrid server, e.g. a server that combines Bukkit and Forge. Examples include Arclight, Mohist, and Cardboard.
- I am NOT using a fork of WorldEdit, such as FastAsyncWorldEdit (FAWE) or AsyncWorldEdit (AWE)
Bug Description
If a player want to take a book from a lectern, the region need the activated "interact" flag (to open the GUI) and the "chest-access" flag to take the book.
But if the player wants to put the book back on the lectern, he must have building rights. This makes no sense compared to a normal inventory block.
Expected Behavior
With activated "interact" flag, the player has access to put the book back to the lectern too. He does not need build-permission for the region.
Reproduction Steps
- Region with a region-owner, "interact = true", "chest-access = true"
- Testplayer take a book
- Testplayer can't put the book back
Optional WorldGuard-Report
No response
Anything Else?
Now, the general question: was it planned this way and can it be changed?
- Dominant language
- Java
- Stars
- 939
- Forks
- 672
- Avg merge
- 22h 57m
- Merged PRs (30d)
- 1
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EngineHub/WorldGuard
-
status:pending type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EngineHub/WorldGuard#2305 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
EngineHub/WorldGuard#2311 · 1 comment ·
-
status:pending type:bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
EngineHub/WorldGuard#2302 · 4 comments ·
-
status:pending type:feature-request
Difficulty 4/5 3-5 days Newbie friendliness 45/100
EngineHub/WorldGuard#2301 · 5 comments ·
-
status:pending type:feature-request
Difficulty 5/5 Over a week Newbie friendliness 25/100
EngineHub/WorldGuard#2288 · 1 comment ·
All issues in EngineHub/WorldGuard
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oracle/javavscode#652 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenAPITools/openapi-generator#25014 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
AloisSeckar/demos-java#380 ·