Skip to content

Release 3.23.5

Latest

Choose a tag to compare

@tastybento tastybento released this 31 Oct 01:41
40b3f97

Release Highlights

  • 🔺 TNT protections now cover Sulfur Cube explosions: a Sulfur Cube that has absorbed TNT exploded without being checked by TNT_DAMAGE and WORLD_TNT_DAMAGE, so it could destroy builds on islands that had TNT damage turned off. These explosions now follow the TNT flags, and igniting a Sulfur Cube is gated by TNT_PRIMING.
  • /island go matches underscores and spaces: /island go happy_place now finds an island home named Happy Place.

Compatibility

✔️ Paper Minecraft 1.21.5 – 26.3
✔️ Java 25+

Upgrading

  1. As always, take backups just in case. (Make a copy of everything!)
  2. Stop the server.
  3. Replace the BentoBox jar with this one.
  4. Restart the server.
  5. You should be good to go!

🔺 Sulfur Cube explosions: if an island or world has TNT damage turned off, Sulfur Cube explosions there will now stop destroying blocks and damaging entities. AOneBlock ships with TNT_DAMAGE: true by default, so on AOneBlock they will still do damage unless you set it to false.

There are no new locale keys and no config.yml or panel template changes in this release.

Legend

  • 🔡 locale files may need to be regenerated or updated.
  • ⚙️ config options have been removed, renamed, or added.
  • 🔺 special attention needed.

Bug Fixes

🔺 Sulfur Cube Explosions Bypassed TNT Protection

[PR #3104]

A Sulfur Cube with absorbed TNT explodes as itself, not as primed TNT, so BentoBox did not treat the explosion as TNT. These explosions now follow TNT_DAMAGE (on islands) and WORLD_TNT_DAMAGE (off-island) for both block damage and entity damage. A player lighting a Sulfur Cube with flint and steel or a fire charge is now checked against TNT_PRIMING, as for a TNT block. Ignition by redstone, dispensers or other explosions has no player, so TNT_PRIMING cannot apply there, but the resulting explosion still follows TNT_DAMAGE. On servers older than Minecraft 26.2, which have no Sulfur Cube, nothing changes.

/island go Did Not Match Underscores to Spaces

[PR #3103]

Players often type underscores in place of spaces in command arguments, so /island go happy_place failed to find a home named Happy Place. Underscores are now treated as spaces when matching destination names. An exact match still wins, and a name that matches more than one destination is rejected rather than guessed. This follows on from #3024.


Other Improvements

  • The test suite now runs on MockBukkit's Minecraft 26.3 artifact, and BentoBox compiles against stable Paper 26.3 rather than an alpha build. The 26.3 cushion and straw bed protection tests, which had been skipped, now run. [PR #3105]

What's Changed

New Contributors

Full Changelog: 3.23.4...3.23.5