GriefPrevention3D v18.0.5

Wiki: GriefPrevention3D Wiki

Highlights

• 1.8.8 Runtime Error Fixes — Fixed several runtime errors that occurred when running the plugin on Minecraft 1.8.8 servers with Java 11+.
• Expanded PvP Configuration — Added config options to allow container access and respawn anchor usage during PvP combat.
• AFK Accrual Bypass Permission — Added permission to bypass AFK checks for claim block accrual.
• New Claim Lifecycle Events — Added "Start" events for claim creation/resize and pre-delete event for addon integration.

1.8.8 Compatibility

• Fixed NoSuchMethodError: EntityExplodeEvent.getExplosionResult() — Added compatibility methods in CompatUtil to safely access explosion results, which don't exist in 1.8.8.
• Fixed NoClassDefFoundError: org.bukkit.event.block.BlockExplodeEvent — Created separate BlockExplodeEventHandler with conditional registration, as this event doesn't exist in 1.8.8 Spigot.
• Fixed NoClassDefFoundError: org.bukkit.event.entity.ItemMergeEvent — Created separate ItemMergeEventHandler with conditional registration, as this event doesn't exist in 1.8.8 Spigot.
• Fixed NoSuchMethodError: PlayerInventory.getItemInMainHand() — Replaced direct calls with CompatUtil.getItemInMainHand() throughout the codebase for 1.8.8 compatibility.

Netty Compatibility

• Note: PaperSpigot 1.8.8 has incompatible Netty epoll transport with Java 11+. Users experiencing "Unable to access address of buffer" errors should:
• Switch to regular Spigot 1.8.8 (recommended), or
• Add -Dio.netty.transport.noNative=true JVM flag (may not work on all PaperSpigot builds)

New Config Options

Two new options under GriefPrevention.PvP in config.yml:

Key	Default	Effect
AllowContainerAccess	false	When true, players can access containers (chests, shulker boxes, etc.) during PvP combat.
AllowRespawnAnchor	false	When true, players can use respawn anchors during PvP combat.

Existing servers will pick up the defaults on first load and have the keys persisted to config.yml automatically.

New Permissions

Permission	Default	Effect
griefprevention.accruals.afkbypass	op	Bypasses the AFK check for claim block accrual. Players with this permission will accrue claim blocks even if they are idle.
griefprevention.accruals	true	Controls whether a player receives claim blocks at the configured hourly rate when not AFK. Negating this permission disables accruals entirely.

New Events

StartClaimCreationEvent

Fired when a player starts creating a claim via the modification tool (golden shovel), before the claim is created. This event fires at the initial shovel click, allowing addons to:

• Validate claim creation before it begins
• Redirect to alternative claim creation flows
• Show custom claim creation UI
• Cancel the creation process entirely

StartSubdivideClaimCreationEvent

Extends StartClaimCreationEvent with additional context for subdivision creation. Includes the parent claim being subdivided.

StartClaimResizeEvent

Fired when a player starts resizing a claim via the modification tool, before the resize is applied. This event is cancellable and allows addons to:

• Validate resize operations before they complete
• Apply custom resize logic
• Cancel invalid resizes

PreDeleteClaimEvent

Fired before a claim is deleted, allowing addons to intercept and prevent deletion. This event is cancellable and provides the claim being deleted.

ClaimsInactivityExpireEvent

Fired when a player's claims expire due to inactivity. Unlike the per-claim ClaimExpirationEvent, this event fires once for all expired claims belonging to a player, providing:

• The UUID of the player whose claims expired
• A list of all expired claims
• A method to calculate total claim blocks freed

This is useful for economy integrations that need to handle bulk claim expiration efficiently.

Compatibility

Category	Support
Minecraft Versions	1.8.8 -> 26.1.x
Minimum Java	Java 11
Bukkit API Target	1.13

Server Recommendations for 1.8.8:

• Use Spigot 1.8.8 (not PaperSpigot) for best Java 11+ compatibility
• PaperSpigot 1.8.8 has Netty epoll issues with Java 11+ that cannot be resolved via JVM flags

Migration

No data migration is required.

Existing claims, configs, and player data remain compatible.