GriefPrevention3D v18.1.0

Wiki: GriefPrevention3D Wiki

Thanks to @thiagorigonatti for fixing this issue!

Upstream Issue Fixes

Inconsistent chest connection choice near claim borders (#2611)

When placing a chest near a claim border with two possible single chest neighbors (one inside the claim and one outside), Minecraft's natural double-chest connection priority sometimes chose the wrong side, resulting in a double chest that crossed the claim boundary.

Before: The plugin detected the cross-claim connection and forcibly split both chests to SINGLE, which could break valid connections and produce inconsistent behavior depending on placement direction.

After: The plugin:

• Detects which side Minecraft already connected to and checks whether that connection crosses a claim boundary.
• If the connected side is denied but another valid single chest exists inside the same claim, the plugin reconnects the placed chest to the allowed side, forming a proper double chest within the claim.
• If no valid connection exists, the cross-claim double chest is split cleanly.
• Handles normal vs. trapped chest type mismatches and only considers left/right sides for valid connection faces.

This also fixes visual ghost blocks on the denied connection side.

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 #2611 — Inconsistent chest connection choice near claim borders
• Fix commit by @thiagorigonatti