Better Pearls - Fix Ender Pearl Exploit v1.5

• Pearl tracking keeps a direct entity reference, avoiding Bukkit entity lookups for every active pearl on every tick.
• Per-world configuration is resolved once and reused; velocity checks use squared magnitudes and are skipped when disabled.
• In-flight counters and pending teleport state are indexed in O(1), with ordered handling for multiple pearls hitting one player.
• Pearl trails use one shared lazy task, and the task stops automatically when no tracked pearls remain.
• Cooldown BossBars/action bars use one shared 10 Hz task instead of one task per player per tick.
• Stats and optional pearl teleport logs write asynchronously, keeping disk I/O off the server thread.

• Block-face contact is excluded from clipping, so pearls flying alongside walls and corners are not falsely flagged.
• A normal hit on the sampled block clears that transient clip observation; a flag remains when the pearl emerges and continues through geometry.
• Expensive full-flight raycasts run only after real clipping evidence.
• Cross-pearl destinations use the actual collision-shape height for slabs, stairs and other partial blocks.
• Entity, counter, pending-state and task cleanup is unified for invalidation, expiry, cancellation, reload and shutdown.

• No anti-glitch protections were removed or weakened.
• No manual config migration is required; existing settings remain valid.
• Replace the JAR and restart the server. The plugin manifest now reports version 1.5.0.

v1.4 removes the last few cases where a perfectly good pearl was still cancelled instead of redirected. Throwing a pearl close to a wall no longer counts as a glitch, and when a pearl does need a safe landing the plugin now searches harder to find one, so it redirects you to a good spot rather than eating the pearl. No settings changed - your config and language files keep working exactly as they are.

Fixed Pearl no longer cancelled when thrown alongside a wall
A pearl flying close to - but not into - a block was treated as a glitch and the teleport was cancelled. The anti-glitch check now only flags a pearl whose centre is actually inside solid geometry, so legal throws along walls and corners work normally.

Fixed Legal landings near corners, ledges and narrow gaps no longer cancel
When a pearl landed somewhere the player's body would clip a block, the plugin could fail to find a safe spot and cancel. The safe-landing search now tries harder - more push attempts, a drop-down fallback and a nearest-open-space sweep - so the pearl is redirected to a valid spot instead of being cancelled.

Improved Cleaner anti-glitch detection
The per-tick clip check now uses a precise centre-in-block test instead of a whole bounding-box overlap, which removes edge-case false positives while still catching real tunnels.

Good News No Settings Are Removed or Required
Your current config.yml and language files work exactly as before. No new options were added; the improved detection and redirecting are on by default with no setup needed.

1. Replace BetterPearls.jar with the new version.
2. No manual config changes are required.
3. Restart the server.

v1.3 changes how the anti-glitch behaves. Instead of cancelling a pearl that would drop you inside a block, you are now moved to the nearest safe landing spot - the pearl still works, but it can no longer clip you through walls. It also fixes a few cases where a perfectly legal throw was treated as a glitch, and does a bit less work on busy servers. No settings were removed - everything keeps working exactly as before.

New Pearls redirect instead of cancelling
If a pearl would teleport you into a wall or a too-tight space, you are now moved to the nearest safe spot instead of being left in place. A pearl that clips through a wall is pulled back to a safe landing on your side, so it can't be used to escape through it. Control it with redirect-on-glitch in config.yml (default true).

New Per-world options for four settings
redirect-on-glitch, anti-cannon, max pearls in flight and velocity multiplier can now be set per world, so you can run different rules on different maps from a single config.

New Hex colors in messages
Language files now support &#RRGGBB hex colors in addition to the standard & codes.

Fixed Legal throws no longer blocked by the flight-path check
A pearl thrown over a low wall or a corner could be pulled back to the wall by the anti-glitch raycast, making the pearl land short. The check now only corrects a pearl that actually entered a block.

Fixed Rare double-refund when a pearl was hit by an explosion mid-teleport
A pearl destroyed by TNT in the same moment it teleported could refund the pearl and still teleport you. The refund is now skipped when the teleport is already being handled.

Fixed Invalid-sound warning when pearl-sound was missing
The default sound now matches the shipped config value, so the console no longer logs an invalid-sound warning in that edge case.

Improved Cheaper anti-glitch scanning
The per-tick clip check now only scans pearls that are actually moving fast. Slow and resting pearls - which can't tunnel through a block - are skipped. This lowers main-thread load when many pearls are in flight and also removes most false positives near block edges.

Improved Pearl log no longer reopens the file for every line
When pearl logging is enabled, entries are written through a persistent buffered writer, which is cheaper on busy servers.

Good News No Settings Are Removed
Your current config and language files keep working exactly as before. The new redirect-on-glitch option is added automatically on first start and defaults to true; set it to false if you prefer the old cancel behaviour.

1. Replace BetterPearls.jar with the new version.
2. No manual config changes are required - redirect-on-glitch is added automatically and defaults to true.
3. If you prefer the old "cancel the pearl" behaviour, set redirect-on-glitch to false in config.yml.
4. Restart the server.

FV