GriefPrevention3D v18.1.1

Wiki: GriefPrevention3D Wiki

Thanks to @thiagorigonatti for fixing this issue!

Upstream Issue Fixes

Chest force-rotation near claim borders

When placing a chest near a claim border, the plugin's chest connection logic could select a neighboring chest as a valid connection target based solely on claim ownership, without checking whether the two chests could naturally form a double chest in vanilla Minecraft. This caused the plugin to force-rotate the existing chest's facing direction to match the placed chest — producing a visual and functional state that would never occur naturally.

Before: The plugin called setFacing() on the neighboring chest, rotating it to match the placed chest even when the neighbor was oriented in a different direction.

After: The plugin:

• Only considers a neighboring chest as a valid connection target if both chests face the same direction (matching vanilla behavior).
• Verifies that both chests can connect on the relevant faces before establishing a double chest.
• Resets the placed chest to SINGLE before reconnecting, preventing stale connection state.
• Removes all setFacing() calls on existing chests — the plugin no longer force-rotates neighbors.

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

• Fix commit by @thiagorigonatti