Creeper bypasses WorldGuard block protection when a player dies from explosion
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- java
- Domain
- authorization, security
Research direction
Start by reproducing the issue on Paper 26.1.2 with WorldGuard 7.0.17 and WorldEdit 7.4.3, following the listed creeper-death steps. Trace how the explosion and player death are handled for a protected region, then verify that an explosion never damages blocks when the player is neither owner nor member.
Written by the indexing model from the issue text.
Description
WorldEdit Version
- Bukkit-Official(7.4.3-beta-01+80c6d6122)
WorldGuard Version
- Bukkit-Official (7.0.17+2370-e42d8bc)
Platform Version
Paper 26.1.2 Build 72
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
In WorldGuard-protected regions, creeper explosions normally do not damage blocks. However, there is a bug where block protection is bypassed if a player who is not the owner or a member of the region dies as a result of a creeper explosion inside the region.
Expected Behavior
Creeper explosions should never damage blocks in a protected WorldGuard region under any circumstances if the player is not the owner or a member of that region.
Reproduction Steps
- Enter a WorldGuard-protected region owned by another player.
- Spawn or lead a creeper into the region.
- Ensure the player dies from the explosion.
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 72/100
grimmory-tools/grimmory#2850 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
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