HyperFactions v0.14.0 — Hytale 0.5.6 & 0.6.0-pre.4 Compatibility

Summary

HyperFactions 0.14.0 brings the plugin onto Hytale's current API. After the 0.5.x ("Update 5") release line moved the Player entity off CommandSender, switched math types to JOML, and tightened the manifest's SemverRange parsing, this release migrates the entire plugin to match — and adds forward compatibility with the Hytale 0.6.0-pre.4 ("Update 6") pre-release from the same codebase.

This is the first release in ~3 months, so it folds together the 0.5.x migration and a full pre-release API audit.

Two JARs are attached, built from identical source:

Download the JAR that matches your server. The stable JAR will not load on a 0.6.0-pre.4 server, and the pre-release JAR will not load on a 0.5.x server (manifest version ranges are enforced strictly).

Changed

Hytale 0.5.x ("Update 5") Compatibility

• Messaging & permissions — the Player entity no longer implements CommandSender; all player-facing messages and permission checks now route through PlayerRef.
• Math types — vectors migrated from com.hypixel.hytale.math.vector.Vector3d/3f/3i to JOML (org.joml.*); accessors getX/getY/getZ() → x()/y()/z(). Rotations use the dedicated Rotation3f/Rotation3fc type (pitch()/yaw()), and the fluid-refill raycast uses JOML's copy-constructor / mul() in place of clone() / scale().
• World map — removed the obsolete UpdateWorldMapSettings.biomeDataMap field (gone in 0.5.3).
• Manifest — conformed version fields to the stricter 0.5.x SemverRange codec: ServerVersion is channel-resolved (^${serverVersion}) and OptionalDependencies use >=x.y.z (no space after >=), both of which otherwise hard-fail manifest loading.

Hytale 0.6.0-pre.4 ("Update 6") Pre-Release Support

• Audited the full Hytale API surface the plugin uses — ECS / component system, codec, UI builder & pages, protocol / packets, universe / world / storage, commands, events, builtin gameplay (farming / tagset / interaction / damage), plugin lifecycle, and all reflection targets — against the 0.6.0-pre.4 source. No hard breaks; the plugin compiles and passes its full test suite on both 0.5.6 and 0.6.0-pre.4 from one codebase.
• World map — ClaimImageBuilder now reads blocks and environment data from the BlockChunk component (blockChunk.getBlock(...) / getEnvironment(...)) instead of the WorldChunk.getBlock(...) / getBlockChunk() accessors that were deprecated in 0.6.0-pre.4. Behavior is identical (same world-bounds guards) and compiles cleanly on both channels.

Build Tooling

• Gradle upgraded to 9.3.0; build targets are resolved per channel via -Phytale_channel=release|pre-release against maven.hytale.com.
• HyperPerms integration validated against HyperPerms 2.10.0; the reflection-based adapter is unchanged and still degrades gracefully when HyperPerms is absent.

Fixed

• Build (dual-channel safety) — the libs/ compile-classpath now excludes any local HytaleServer*.jar / Server-*.jar. A stale local server JAR could previously shadow the channel-resolved Hytale dependency and silently defeat the -Phytale_channel release/pre-release switch, producing a JAR built against the wrong API.

Upgrade Notes

• Pick the right JAR for your server (see the table above). Most servers running the current stable Hytale want HyperFactions-0.14.0.jar.
• No config or data migration is required beyond the automatic ones the plugin already runs on startup.
• HyperPerms users: 2.10.0 is recommended, but the integration remains optional and reflection-based.

Full changelog: https://github.com/HyperSystems-Development/HyperFactions/compare/0.13.1...0.14.0 82 files changed, +574 / −552 since 0.13.1.