Skip to content

HuskHomes 4.6 - New config layout, platform APIs

Compare
Choose a tag to compare
@WiIIiam278 WiIIiam278 released this 13 Feb 18:07
· 173 commits to master since this release
8d0871a

Please note, as announced on Discord, starting with this release support for Minecraft 1.16 and Java 16 has been dropped. HuskHomes now requires Java 17 / Minecraft 1.17.1 as a minimum.

HuskHomes 4.6 introduces a new config layout, adds per-platform API publishing, and now targets Fabric 1.20.4 / Sponge 1.19.4 (API v10) / Spigot 1.17.1+ running Java 17. You must regenerate your config.yml and messages-xx-xx.yml files for this release

  • Added an option to force users to respawn at the /spawn position when they die, courtesy of @Yuhtin (#540)
  • The layout of config.yml has been reworked to have a better layout.
  • The plugin's version requirements have now changed. Additionally, HuskHomes now requires Java 17.
    • Fabric: Updated to target Minecraft 1.20.4
    • Sponge: Updated to target API v10 (Minecraft 1.19.4)
    • Paper/Spigot: A minimum of Minecraft 1.17.1 is now required.
  • Added Brazilian Portuguese (pt-br) locales, courtesy of @EmanuelFNC (#548)
  • Added French (fr-fr) locales, courtesy of @Funasitien (#527)
  • Updated the Simplified Chinese (zh-cn) locales, courtesy of @jhqwqmc (#554)
  • API: Improved the Teleport API to now provide methods to catch and gracefully handle TeleportationException, displaying what went wrong to the user
  • API: The way the HuskHomes API is published has been changed.
    • APIs are now published per-platform; huskhomes-bukkit, huskhomes-fabric, huskhomes-sponge, and huskhomes-common can now be targeted.
    • Existing Bukkit API developers can update their build scripts to target the net.william278.huskhomes:huskhomes-bukkit artifact
    • BaseHuskHomesAPI is no longer an abstract class; you can now retrieve an instance of the base class with BaseHuskHomesAPI.getInstance()
    • Otherwise, there are no breaking changes.

To update, drag+drop and regenerate (delete, and let regenerate) both your config.yml and messages-xx-xx.yml files.