File Details
GriefPrevention3D v18.0.8
- R
- Jun 7, 2026
- 755.53 KB
- 0
- 26.1.2+44
File Name
GriefPrevention3D.jar
Supported Versions
- 26.1.2
- 26.1.1
- 26.1
- 1.21.5-Snapshot
- 1.21.11
- 1.21.10
- 1.21.9
- 1.21.8
- 1.21.7
- 1.21.6
- 1.21.5
- 1.21.4
- 1.21.3
- 1.21.2
- 1.21.1
- 1.21
- 1.20.3-Snapshot
- 1.20.5-Snapshot
- 1.20.6
- 1.20.5
- 1.20.4
- 1.20.3
- 1.20.2
- 1.20.1
- 1.20
- 1.19.4
- 1.19.3
- 1.19.2
- 1.19.1
- 1.19
- 1.18.2
- 1.18.1
- 1.18
- 1.17
- 1.16
- 1.15
- 1.14
- 1.13
- 1.12
- 1.11
- 1.10
- 1.9
- 1.8.3
- 1.8.1
- 1.8
v18.0.8: Fix claimed double chest split by adjacent single chest
GriefPrevention3D v18.0.8
Wiki: GriefPrevention3D Wiki
Thanks to @thiagorigonatti for fixing this issue!
Upstream Issue Fix
Placing a chest next to a claimed double chest breaks the double chest (#2606)
Before: Placing a single chest outside a claim adjacent to a double chest fully inside the claim would forcibly split the double chest into two singles — even though no cross-claim double chest was actually formed.
After: The double chest is left untouched when the placed chest remains single.
The root cause was in denyConnectingDoubleChestsAcrossClaimBoundary: it assumed any chest placed near a double chest had connected to it, and unconditionally split both blocks. The fix adds a guard that checks the placed chest's type after placement — if it is still Chest.Type.SINGLE, the method returns early and the neighboring double chest is preserved.
Compatibility
| Category | Support |
|---|---|
| Minecraft Versions | 1.8.8 -> 26.1.x |
| Minimum Java | Java 8 |
| Bukkit API Target | 1.13 |
Migration
No data migration is required.
See Also
- Issue #2606 — Upstream bug report
- PR #2607 — Upstream fix by @thiagorigonatti