TaleGuard v1.1.0

Hytale 0.6 support. Every guard re-pointed at the 0.6.5 server, a new guard for player block damage, and a boot-time check that tells you which guards are live.

⚠️ Requires Hytale 0.6

• This jar is TaleGuard-1.1.0-hytale-0.6.jar and declares ServerVersion >=0.6.0 <0.7.0. Mixins bind to exact server descriptors, so a server on another line now refuses the jar instead of loading guards that would silently not apply. Still on Hytale 0.5? Stay on v1.0.0.
• Install into the server's earlyplugins/ folder — not mods/. A server without an interactive console (panel, systemd, Docker) must be started with --accept-early-plugins.

Guards ported to 0.6

All 28 redirects across 18 mixins bind against Hytale 0.6.5 — checked against the server's bytecode and loaded on a live 0.6.5 server.

• Crop harvest — FarmingUtil.harvest takes the chunk-store accessor first and no longer gets the World, block type or rotation.
• Crop stage change, block state change, hammer — these interactions now resolve the block through its chunk section and abort when that lookup comes back empty; the guard sits on that lookup.
• Builder tools — paste, extrude, line and stack queue through the new addToQueue overload.
• Block pickup — removeBlock now receives the block's section, which a denial invalidates directly.
• Item pickup — the closest-player lookup is gone; the list of players in range is filtered instead.
• Explosions — guarded where ExplosionUtils damages each block. 0.6 passes no tool id there, so the old test could never match again.
• New: player block damage — mining through BreakBlockInteraction, single blocks and area tools. Area tools only damage the blocks the hook allows.
• Removed the item-durability mixin: it was never registered, and its target is gone in 0.6.

Checks itself at boot

• Every redirect is looked up in the running server's code at boot. The log says [TaleGuard] all 28 redirect(s) match this server. — or names each guard that won't apply. The result is also published as taleguard.redirects.audit and taleguard.redirects.broken.
• The check now runs from the early plugin itself. It used to live in the plugin entry point, which the server only starts when the jar is also in mods/ — so on a normal install it never ran.

Also

• Guards that had stopped binding on 0.5.6 were repaired (renamed BuilderTools handlers, harvest returning boolean, NPC spawns, fluid spread).
• The manifest's Version is expanded (1.0.0 shipped a literal ${version}) and the dead ID key is gone. Declare the dependency as "Stoshe:TaleGuard" — Stoshe:stoshe.taleguard never matched.
• Mod icon, shown in a world's Mods tab, and Stoshe Labs as the author.
• README: the protection table lists the exact type each surface sends to your hook.