Repository navigation
VonixGuardian v2.3.2
Server-side block, inventory, and entity auditing with rollback tools for modded Minecraft.
Highlights
Taken from CHANGELOG.md section [2.3.2]. Schema version is 9.
Rollback of a used container no longer fails. A live server logged 257 failed rows in a
single batch — every CONTAINER_WITHDRAW and CONTAINER_DEPOSIT — and left the batch open
with REPAIR_REQUIRED.
Fixed
- A container rollback insisted on the exact slot it recorded. Returning items to a chest
is not the same as returning them to one coordinate: by the time an operator runs the
rollback the chest has been used again, so that slot holds something else, or holds the same
item but is full. The mutator refused in both cases, which is why one batch failed hundreds
of rows at once. It now places the stack wherever it fits — topping up matching partial
stacks first, then any empty slot — and fails only when the container is genuinely full.
Applied to all thirteen loader cells; the container code is duplicated per cell, and the
first pass fixed only 1.18.2 Forge. - The failure line now names the row's data. The old message was
mutation unsuccessful for action id=14356372 type=CONTAINER_WITHDRAW, repeated 257 times.
It could not distinguish a missing container from a full one from one holding different
items — three different problems with three different fixes. It now reports world,
position, target item, amount and slot.
Added
- A boundary guard fails the build if any loader cell loses the anywhere-fallback, which is
what caught that the first pass had fixed only one of thirteen.
Verification
- 1,531 tests, 0 failures on the core module.
- All thirteen cells rebuilt and packaged: 1.18.2 through 26.3 on Fabric, Forge and NeoForge.
- Not verified on a live server. The 257-failure batch has not been re-run against the
world that produced it, so this fix is proven by compilation and unit coverage, not by
observing the batch complete. - The underlying type-only item matching in
tryRemoveFromContainer(it matches on item id,
not NBT) is unchanged and still a known limitation against modded items with identical ids
and different payloads.
Thirteen primary jars share version 2.3.2. The NeoForge 26.3 cell is built against the NeoForge loader pin 26.3.0.6-beta. The jar name is vonixguardian-neoforge-26.3-2.3.2.jar.
This release covers the thirteen Fabric, Forge, and NeoForge cells below.
Public wiki: https://modwiki.vonix.network/mods/vonixguardian/
Drop-in jars
| MC version | Fabric | Forge / NeoForge |
|---|---|---|
| 26.3 | vonixguardian-fabric-26.3-2.3.2.jar |
vonixguardian-neoforge-26.3-2.3.2.jar |
| 26.2 | vonixguardian-fabric-26.2-2.3.2.jar |
vonixguardian-neoforge-26.2-2.3.2.jar |
| 26.1.2 | — | vonixguardian-neoforge-26.1.2-2.3.2.jar |
| 1.21.1 | vonixguardian-fabric-1.21.1-2.3.2.jar |
vonixguardian-neoforge-1.21.1-2.3.2.jar |
| 1.20.1 | vonixguardian-fabric-1.20.1-2.3.2.jar |
vonixguardian-forge-1.20.1-2.3.2.jar |
| 1.19.2 | vonixguardian-fabric-1.19.2-2.3.2.jar |
vonixguardian-forge-1.19.2-2.3.2.jar |
| 1.18.2 | vonixguardian-fabric-1.18.2-2.3.2.jar |
vonixguardian-forge-1.18.2-2.3.2.jar |
Pick the matching jar for your server, drop into mods/, restart.
Verifying
SHA-256 checksums are in SHA256SUMS. Run:
sha256sum -c SHA256SUMS
Configuration
On first boot, the mod writes config/vonixguardian/config.json. See README for the full schema.
Commands
/vg inspect, /vg lookup, /vg rollback, /vg restore, /vg purge, /vg near, /vg undo, /vg status, /vg reload, /vg help. Alias: /guardian.
See CHANGELOG.md for the full feature surface.