You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Players can place cushions in other players' protected regions on Minecraft 26.3 (WorldGuard 7.0.20) #2317
Minecraft 26.3. The exact server build is not included in this report.
Bug Description
Players can place cushions inside another player's protected WorldGuard region, despite not being an owner or member and not having permission to build there.
The cushion protection added in #2315 covers breaking existing cushions, but placement appears to remain unprotected.
Expected Behavior
Placing a cushion should respect the region's build protection. A player who cannot build in a region should not be able to place cushions there, while authorized owners and members should still be able to place them.
Reproduction Steps
Use Minecraft 26.3 with WorldGuard 7.0.20 and a compatible WorldEdit version.
Create a protected region owned by player A, with ordinary build protection and no explicit build allowance for outsiders.
Join as player B, who is not an owner or member, is not an operator, and has no WorldGuard bypass permission.
Confirm that player B cannot place ordinary blocks in the region.
As player B, attempt to place a cushion inside the region.
The reported result is that the cushion can be placed despite the region's build protection.
Optional WorldGuard-Report
Not attached.
Anything Else?
Source inspection of the 7.0.20 release (0b6c3f1) shows that EventAbstractionListener.handleBlockRightClick handles placement of minecarts, boats, armor stands, end crystals, and spawn eggs, but has no cushion placement branch:
This looks like a missing placement-to-region-protection path, separate from the entity break handling added by #2315.
The gameplay behavior is reported by the server operator; an independent clean-server reproduction and complete version/report outputs are not attached. The source observation above is independently checked.
Activity