GriefPrevention3D

A fork of GriefPrevention that adds 3D subdivisions

File Details

GriefPrevention3D v18.1.1

  • R
  • Jun 8, 2026
  • 757.37 KB
  • 6
  • 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.1.1: Fix chest rotation bug when forcing cross-claim connections

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