Vonix Guardian

VonixGuardian 2.3.2

Rollback now completes on the paths that kept failing. A live batch went from 1 applied to 880 applied.

Fixes:

• Every ENTITY_KILL respawn failed. EntitySentinel records mobs as "#mob:minecraft:pillager" and ResourceLocation.tryParse cannot parse a leading '#', so nothing was ever respawned. All 74 failures in one batch were this single bug.
• BURN rollback cleared the wrong thing. A burn row names the block that burned away; rollback cleared the position to air - already air - so every burn row reported failure. It now restores the burnt block.
• MALFORMED_PAYLOAD=434 named no cause. The real answer was a config key, not corruption: storage.persistNbt was false, so inventory rows were written without item identity. Now reported as MISSING_ITEM_IDENTITY with its own wording.

New: a release gate that boots the jar on a throwaway Forge server, drives commands over RCON and runs a real rollback. 2.3.1 shipped broken because a mixin that fails to apply compiles perfectly - build success proved nothing. The gate catches that class of defect; proven by failing the shipped 2.3.1 and passing this build.

Verified: 1531 tests, 0 failures; boot-verified; rollback exercised with 0 mutation failures. 13 jars, server-side only.

Not verified: MySQL is untested - every runtime check runs SQLite, while the live server is MySQL-backed. The 434 rows already written without item identity cannot be recovered.

Full notes: https://github.com/Vonix-Network/VonixGuardian/releases/tag/v2.3.2