pkWaystones Fix: Now with Painting Table Support

New Feature - Painting Table Support

- Added support for KawaMood's Painting Table datapack alongside Kawamood's Waystones datapack. The barrel timing fix now applies to Painting Tables using the same fix. - Painting Table entries are cached the same way as Waystones in the plugin data folder. - Painting Table placement and removal is detected the same way as Waystones.

Updated Datapack Detection

- Both datapacks will be detected during startup and on /pkfix reload. If one of the datapacks is not installed then the barrel timing fix for that datapack is inactive and no scan is attempted. - Both detection results are reported in console on startup and on /pkfix reload.

Stuck Lock Fixed

- Some users were experiencing a locked Waystone after opening and closing it. The barrel timing fix would sometimes leave the Waystone locked so I've changed the timing as to when the barrel is unlocked to resolve that issue. This shouldn't require players to relog or move 20 blocks away anymore.

What's Changed

- ### Rewrote Waystone detection on first startup - ### Rewrote detection when placing/removing a Waystone - ### Expanded debug logging to make it easier to diagnose future issues. - ### Added commands (needs op permission) - /pkfix rescan — manually rebuilds the cache from Kawamood's Waystones datapack storage - /pkfix reload — reloads config.yml without restarting - /pkfix status — lists all cached Waystones with coordinates, paginated - /pkfix force — toggles Brute Force mode (see below)

Brute Force mode

- Normally the barrel timing fix only applies to barrels that are recognised as Waystones. Brute Force mode applies the barrel timing fix to every downward-facing barrel on the server regardless. Useful for troubleshooting, but leaving it on permanently may impact performance. It is persistent through server restarts via the config.yml. A warning is printed to console on startup if it's active.

Initial Release