| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| GriefPrevention3D.jar | 2026-06-07 | 773.7 kB | |
| README.md | 2026-06-07 | 1.6 kB | |
| v18.0.8_ Fix claimed double chest split by adjacent single chest source code.tar.gz | 2026-06-07 | 522.2 kB | |
| v18.0.8_ Fix claimed double chest split by adjacent single chest source code.zip | 2026-06-07 | 678.7 kB | |
| Totals: 4 Items | 2.0 MB | 0 | |
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