GlymeraTameFly v7.0

Hytale Stable-5 Migration
All Glymera plugins updated for Hytale Server 0.5.x (Stable 5)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
​

All Glymera plugins have been updated for compatibility with Hytale Server 0.5.x (Stable 5). The previous versions targeted Hytale Server 0.4.x (Stable 4).

This document covers what changed in the Hytale Server API between Stable 4 and Stable 5, and which adjustments were required across plugins so that things keep working.

◆ Why a new major version

Stable 5 introduced a number of source-incompatible API changes. A plugin compiled against Stable 4 will either fail to load, fail silently on first use, or — in a few cases — crash the world thread. Because the surface of change is large, every plugin received a new major version number, even when the only functional behaviour change was a manifest flag.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━​

◆ What changed in Hytale Stable 5

▸ Vector math

• Internal Hytale vector types were replaced by JOML.
• com.hypixel.hytale.math.vector.Vector3d/3i/3f → org.joml.Vector3d/3i/3f
• Rotation helpers now use the Rotation3fc interface where the older API took a concrete Rotation3f.

▸ Particle / Sound API

• SpawnParticleSystem constructors gained additional arguments.
• PlaySoundEvent3D / ambient sound registration semantics tightened — long-running or looped sounds attached to a block must now use the block-state AmbientSoundEventId path; firing them with PlaySoundEvent3D from a tick handler no longer behaves correctly.

▸ Asset pack registration

• AssetModule.registerPack(...) now requires a PackSource parameter (use PackSource.MODS for plugin-installed packs).
• The IncludesAssetPack manifest flag is now strictly enforced. If a plugin both declares IncludesAssetPack: true and registers a runtime pack from its setup code, Hytale detects this as a duplicate registration and aborts boot with "Duplicate asset pack ... Remove the duplicate." For affected plugins IncludesAssetPack is now set to false; the actual asset pack is installed by the plugin at startup as before.

▸ HUD / UI system

• The HudManager API has moved to a keyed model — HUD entries now require a stable key and explicit lifecycle hooks.
• InteractiveCustomUIPage event bindings are wiped if the page is rebuilt while the client is processing a click. Plugins refreshing a HUD per tick had to throttle the rebuild rate (commonly to 1 Hz) so button presses are not lost.

▸ Player handles

• The Player component and the PlayerRef reference have been split. Plugins previously juggling one or the other now need to consider both.
• ServerPlayerListPlayer requires a worldUuid field — entries without it are silently dropped from the tab list.

▸ Entity utilities

• EntityUtils.toHolder(...) was removed. Lookups need to go through the entity store directly or via Ref<EntityStore>.

▸ Damage system

• Resistance fields on EntityEffect (damageResistanceValuesRaw, damageResistanceValues) now expect ResistanceModifier[], not StaticModifier[]. Plugins that previously injected resistances via reflection now use the ResistanceModifier(ResistanceCalculationType, float) constructor.
• The corresponding JSON CalculationType value "Multiplicative" is no longer accepted for damage resistance — it must be "Percent". Migrating large packs needed a bulk rewrite of Potion/Effect JSONs.
• Lethal-damage detection: EntityStatValue#getMin() is no longer a usable death-threshold. Lethal checks now compare the post-damage health against 0.0f directly. Plugins relying on the old behaviour would silently fail to fire and the player just died.

▸ ECS / system tick safety

• It is no longer legal to call mutating store methods (addComponent, removeEntity, …) directly from inside a system's tick handler. Doing so now throws IllegalStateException: Store is currently processing! Such calls must be deferred: either via the system's CommandBuffer, or by scheduling onto the next world tick with world.execute(...).

▸ Items, weapons and recipes

• Custom swords must declare Tags.Type: "Weapon" (not "Tool"), and they need their own complete InteractionVars block — these are no longer inherited from the parent template under Stable 5. A custom weapon without its own InteractionVars will spawn but cannot deal damage.
• Recipe bench IDs and recipe categories are now validated against the asset registry. Mistyped values cause Hytale to silently drop the recipe with no error message.

▸ Cosmetics

• CosmeticsToHide now only accepts a restricted, enumerated set of values. Custom values are rejected at asset-load time.

▸ Server authentication

After every Stable update the server's OAuth credentials must be refreshed:

1. auth logout
2. auth login device
3. Open the printed verification URL, complete the device authorisation
4. auth select <profile>

If the server is still on cached OAUTH_STORE credentials after a Stable update, every incoming player connection is rejected with serverAuthUnavailable and the client only sees "QUIC handshake failed".

▸ Manifest / ServerVersion

• Stable 5 enforces a recognisable ServerVersion declaration in each plugin's manifest.json. A malformed value prevents the server from booting. Glymera plugins declare "ServerVersion": "*" to remain agnostic across patch versions.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━​

◆ Plugin-data path

The plugin-data directory used by all Glymera plugins is now:

mods/de.glymera_<PluginName>/

(Previously it was plugins/<PluginName>/.) Existing configuration files are not migrated automatically — if you want to keep custom configuration from an older install, move the relevant files from the old plugins/ location into the new one before first launch.

GlymeraTameFly - Changelog

v6.0.0 (2026-04-19)

Bug Fixes

- Flight platform barriers left behind: Barrier blocks (the temporary 3x3 platform the flight tick places under a flying mount) were not being removed under certain conditions. Three scenarios were affected:
1. Server stop/restart while flying: shutdown() only cleared the state map without removing the blocks. Barriers stayed in the world permanently.
2. Player changes world while flying (e.g. via /bw tp): the old world never removed its barriers; the player got a fresh state in the new world with no link to the blocks left behind in the old one.
3. Multi-world tick race: the 50ms flight tick ran per world but shared a single global state map. World B's tick saw a player flying in world A as "not mounted", wiped the state, and called breakBlock at world-A coordinates inside world B — the real barriers in world A were orphaned.

Technical Details

• FlyState now carries a worldName field. The cleanup branch in processFlyingMounts skips states whose home world does not match the currently ticking world, so only the actual flying world performs cleanup.
• New helper cleanupStateInHomeWorld tears down the old platform on a world switch (e.g. /bw tp) via world.execute() on the source world's thread.
• removeAllBlocks is now retry-safe: positions are only removed from placedBlocks once getBlock confirms the block is air after the breakBlock call. Unloaded chunks are silently skipped and retried on the next tick.
• FlyState stays in the flyingPlayers map until every block is verifiably cleared (previously the state was removed immediately on dismount, so failing chunk loads lost the positions forever).
• Persistence via flystate.json in the plugin data directory: shutdown() serializes all open states (UUID, worldName, placedBlocks). start() loads them back into flyingPlayers. The normal flight tick then notices the missing mount and clears the platform on the world thread once the chunks are available.
• FlyCommand (/fly toggle) now also passes the current world name when creating a new state.

Known Limitations

- Barriers that were already orphaned in the world under v5.0.0 or earlier cannot be cleaned up retroactively by v6.0.0 — they are not tracked anywhere. A one-time manual removal (breaking or blasting them) is required. Any state created from v6.0.0 onwards cleans up correctly.

This plugin has been updated as part of a compatibility pass for Hytale version 2026.03.26 (Update 4). It is one of a series of plugins that have been reworked to support the new Hytale release.

Clean Release - All Plugins

2026-03-16

▸ Silent Operation

• Removed all debug and info log output from every plugin. Plugins now operate completely quietly in the background, keeping your server log clean and free of plugin messages.

▸ Major Version Bump

• All plugins have been bumped to the next major version to clearly distinguish this clean release from previous development builds.

▸ Universal Server Compatibility

• All plugins now use wildcard server versioning for maximum compatibility with future Hytale server updates.

Single-File Optimization Update (2026-03-14)

• Optimization: This plugin is part of a larger optimization series in which all multi-file plugins have been converted to single-file plugins. Previously, some plugins required both a JAR file and a separate asset pack folder. Now everything is contained in a single JAR - just drop it into your mods folder and you're good to go.
• New: Crafting recipes for Farmer Chest, Worker Chest and Guard Cages have been added (GlymeraFarmer, GlymeraWorker, GlymeraGuard only). Recipes can be enabled or disabled via the config option "craftingEnabled" (default: true).

Tame, ride, and fly a huge amount of animals in Hytale with 50 new tameable creatures.