Island Border

## Summary Border 4.8.5 is a compatibility and permissions patch. The headline fix restores compatibility with DeathChest, grave plugins, and other death-drop handlers, which Border has silently been breaking since 4.7.0. The second fix makes the border colour and type commands actually usable by players again — the permissions they check were never declared, so they quietly fell back to op-only. ### Compatibility BentoBox API 3.12.0+ Minecraft 1.21.5 – 1.21.11, 26.1.x Java 21 ### Upgrading 1. Stop the server. 2. Replace Border-4.8.4.jar in plugins/BentoBox/addons/ with Border-4.8.5.jar. 3. Start the server. No config or locale changes required.

Permission rename: the declared node [gamemode].bordertype has been renamed to [gamemode].border.bordertype. If you granted or denied [gamemode].bordertype in LuckPerms (or similar), update it to the new node. The old node was never actually checked by the command, so it had no effect either way — but any rule referencing it is now dead weight.

Colour commands are usable again: [gamemode].border.color now defaults to true, so ordinary players can run the colour command as documented. The individual colours (.red, .green, .blue) remain op by default. If you were granting these explicitly to work around the bug, you can leave those grants in place — they still work.

### Legend - special attention needed. --- ## Bug Fixes ### Death drops no longer hijacked from other plugins [[PR #182](https://github.com/BentoBoxWorld/Border/pull/182)] The death-drop protection added in 4.7.0 handled PlayerDeathEvent at NORMAL priority by pulling every item out of event.getDrops(), spawning them by hand, and clearing the list. Any plugin that stores death drops — DeathChest, grave plugins, keep-inventory features — runs at a later priority and saw an empty event, while the items were already lying on the ground. With the default bounce-back: true, that silently broke all of them; it was tracked down on a live server where DeathChest chests were always coming up empty. Border now leaves the event's drops untouched. onPlayerDeath runs at MONITOR — after every other plugin has decided what happens to the items — and only records the death spot and island for one tick. A new ItemSpawnEvent handler applies the same bounce-back to items the server spawns that tick near a recorded death spot. If another plugin takes the drops, nothing spawns and nothing is tracked; if the drops survive, they bounce back inside the border exactly as before. Vanilla drop behaviour (velocities, despawn timers) is preserved too, since the server spawns the items itself. ### Border colour and type permissions were never declared [[PR #180](https://github.com/BentoBoxWorld/Border/pull/180)] Found while investigating [#179](https://github.com/BentoBoxWorld/Border/issues/179) addon.yml did not declare the permissions the commands actually check: - [gamemode].border.color — checked by BorderColorCommand (both /[gamemode] border color and /[gamemode] bordercolor). Undeclared, so it had no default and fell back to op only, contradicting the documentation and stopping players from using the command at all. Now declared true. - [gamemode].border.color.red|green|blue — checked in BorderColorCommand, documented as op. Now declared with an op default. - [gamemode].bordertype was declared but never checked — BorderTypeCommand asks for [gamemode].border.bordertype. The declaration has been renamed to the permission that is really used, keeping its false default. Note that this was not the cause of the exception reported in [#179](https://github.com/BentoBoxWorld/Border/issues/179) — that is [BentoBox#3042](https://github.com/BentoBoxWorld/BentoBox/issues/3042) — but it is why the colour command was unusable for the reporting player in the first place. --- ## Other Improvements - CurseForge and Hangar publishing. Releases now publish the attached jar to CurseForge and Hangar automatically, alongside the existing Modrinth workflow. [[PR #176](https://github.com/BentoBoxWorld/Border/pull/176)] - Modrinth game versions brought up to date. The listing now covers 1.21.5 – 1.21.11 and 26.1.x instead of stopping at 1.21.4. [[PR #175](https://github.com/BentoBoxWorld/Border/pull/175)] - MockBukkit pinned to Maven Central 4.110.0 instead of a jitpack snapshot, so test builds are reproducible. ## What's Changed * Stop death bounce-back from hijacking the drops by @tastybento in https://github.com/BentoBoxWorld/Border/pull/182 * Declare the border colour and bordertype permissions by @tastybento in https://github.com/BentoBoxWorld/Border/pull/180 * ci: bump publish-platforms pin to the multipart-JSON fix by @tastybento in https://github.com/BentoBoxWorld/Border/pull/181 * ci: bump pinned publish-platforms.yml to ca2dcd1 by @tastybento in https://github.com/BentoBoxWorld/Border/pull/178 * ci: bump pinned reusable workflow to fe4b1f0 by @tastybento in https://github.com/BentoBoxWorld/Border/pull/177 * Add CurseForge publish workflow (publishes the release asset) by @tastybento in https://github.com/BentoBoxWorld/Border/pull/176 * Update Modrinth game-versions to current MC range by @tastybento in https://github.com/BentoBoxWorld/Border/pull/175 * Pin MockBukkit to Maven Central 4.110.0 instead of jitpack snapshot by @tastybento Full Changelog: https://github.com/BentoBoxWorld/Border/compare/4.8.4...4…