Setting notify-enter to false blocks entry to region
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start by reproducing the five-step notify-enter sequence on WorldGuard 7.0.15-snapshot with WorldEdit 7.3.17-snapshot and Paper 1.21.8-58, then inspect the change from commit f8415ed. Done means a persisted notify-enter: false flag no longer prevents entry, including for op'ed players, and the behavior has regression coverage.
Written by the indexing model from the issue text.
Description
WorldEdit Version
7.3.17-snapshot
WorldGuard Version
7.0.15-snapshot
Platform Version
Paper version 1.21.8-58-main@9aaaadf
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
With commit #f8415ed regions on our server cannot be entered, when there's "notify-enter: false" in the region file. (We had one region where notify-enter was enabled years ago and disabled later, a pretty rare case). This also happens to op'ed players.
Setting "notify-enter: true" or removing the "notify-enter: false" entry from the region file completely makes it accessable again.
Expected Behavior
the config entry "notify-enter: false" for a region does not affect entry to the region.
Reproduction Steps
- /rg flag freefarm notify-enter true
- /rg flag freefarm notify-enter false
- (trying to enter the region bounces the player back)
- /rg flag freefarm notify-enter true
- (region is can be entered again)
Optional WorldGuard-Report
No response
Anything Else?
No response
- Dominant language
- Java
- Stars
- 938
- Forks
- 674
- Avg merge
- 22h 57m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 2/5 1-3 hours Newbie friendliness 65/100
aoqia194/leaf-loader#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
apache/streampark#4521 ·
-
Update license yearOpen0 - Backlog 1 - Ready documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
cbor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
FasterXML/jackson-dataformats-binary#844 ·
Maintainers usually reply within 1 day
-
Issue: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
OpenAPITools/openapi-generator#25107 ·
Maintainers usually reply within 1 day