Repository navigation
v2.2.0
VonixGuardian v2.2.0
Server-side block, inventory, and entity auditing with rollback tools for modded Minecraft.
Highlights
Taken from CHANGELOG.md section [2.2.0]. Schema version is 9.
Fixed
- Orphaned block entities after rollback (
OE1). A rollback that cleared or replaced a block usedtrySetBlock(..., AIR, null). VanillaLevel.setBlock(pos, state, UPDATE_ALL)only removes a block entity as a side effect of aBlockEntity-owning block-state change, so a stale block entity at the position survived the write, was re-serialised into the region file, and on the next chunk load reconstructed its recorded id (minecraft:bed/minecraft:banner) against an unrelated block state. That throwsClassCastExceptioninsideBedBlockEntity/BannerBlockEntity, aborts the block entity, and repeats per affected position on every chunk load — observed live as 142 console errors from a single affected area, with permanent cosmetic loss of bed colour and banner pattern.WorldMutator#tryClearBlocksets the block to air first, while the genuine block entity is still attached, so vanilla's own removal path runs. It then reads the position with a non-creating check (EntityCreationType.CHECK). A survivor is removed explicitly. The method returns true only when the final state is air and that check read is null. It does not call an entity-creating accessor between the removal and the state write. If the air write does not land, the block entity is left in place so its contents are not discarded. The engine routes every removing inverse (BLOCK_PLACE,IGNITE/BUCKET_EMPTY/STRUCTURE_GROW/PORTAL_CREATE/FLUID_FLOW,BURN/FADE/LEAVES_DECAY/BUCKET_FILL, and explosion block clears) through it instead of a plain airsetBlock.trySetBlockgoes through oneplaceBlockhelper per cell. After the state write, a non-creating read must be null when the target block owns no block entity. When the target owns one and no NBT was supplied, the fresh entity is not treated as stale. A failed place restores the previous state and returns false.- Container deposit rollback on the 1.18.2, 1.19.2, 1.20.1, and 1.21.1 cells counts matching stacks before it shrinks any of them. A short quantity returns false and leaves the remainder in place. The 26.x cells already did this preflight.
- Implemented across all 13 loader cells.
- A place that targets a block entity reports failure when no block entity is present after the write, and NBT is applied only when the entity at the position is the type the target block creates. A pre-existing entity that belongs to another block fails the place and restores the previous state instead of receiving the snapshot.
- Compensation restores captured NBT even when the previous state is already present (
setBlockreturning false is not treated as a failed restore).
- Admission drops are journaled before they are counted when the quarantine has capacity. Queue overflow and an explosion-join rejection append to the durable quarantine outbox before the drop counter moves. A full quarantine cannot retain the action: it increments the overflow counter and logs the action type, id, world, and coordinates at ERROR, so the drop is counted and visible but not replayable.
/vg statusprintsdropped,quarantined,qOverflow, andqWriteFail. A rejected explosion handoff is journaled asentries=<n>at the explosion centre only; the per-block list is not retained, so that row is a loss record and not a rollback source. - Open rollback batches stay open. Boot does not replay them.
/vg statuslists open batch ids, mode (ROLLBACK/RESTORE), affected counts, andvg_repair_requiredrows. Staff inspect those rows before re-running a rollback or restore.
Changed
- NBT-less rollback of a block position reports failure when the clear does not land, instead of reporting success with a stale block entity left behind.
purge.autoPurgeSecondsstays0(GuardianConfig.DEFAULT_AUTO_PURGE_SECONDS).0means unbounded retention.7776000(90 days) isSUGGESTED_BUSY_SERVER_AUTO_PURGE_SECONDSand is not written into existing configs. Boot logs one warning when the loaded value is0.rollback.requireConfirmdefaults tofalse. Rollback and restore still apply immediately at op level 3. Setting it totruemakes/vg applythe confirmation. The permission table is unchanged.- Privacy docs match the shipped
Privacy(false, …)default.hashIps: truewith the placeholder salt is a hard validation error. Hash width and salt handling are unchanged. Schema version stays 9.
Added
OrphanedBlockEntityClearTestplus fake-level and source-contract tests for the clear/place order, the container preflight, and the Gradle profile split.- Thirteen primary jars at
mod_version2.2.0: Fabric and Forge on 1.18.2, 1.19.2, and 1.20.1; Fabric and NeoForge on 1.21.1; NeoForge on 26.1.2; Fabric and NeoForge on 26.2 and 26.3. - NeoForge 26.2 cell (
mc-26.2/common+mc-26.2/neoforge) targeting Minecraft 26.2 / NeoForge 26.2.0.88. Java 25, ModDevGradle 2.0.147, MixinJAVA_25, Shadow 8.3.9. Loader ranges: NeoForge[26.2.0.88,26.3), Minecraft[26.2,26.3). Build profilemc262on Gradle 9.2.0. The jar version is the rootmod_version. - NeoForge 26.3 cell (
mc-26.3/common+mc-26.3/neoforge) for Minecraft 26.3. The loader pin is NeoForge26.3.0.6-beta(ModDevGradle 2.0.147, Java 25, MixinJAVA_25). The artifact version is the rootmod_version(vonixguardian-neoforge-26.3-2.2.0.jar), with no extra suffix. Build profilemc263on Gradle 9.2.0. Re-pinneoForge.versionwhen NeoForge publishes a stable 26.3 loader. This cell is one of the thirteen release jars. - Fabric 26.2 cell (
mc-26.2/fabric, packagemc.v26_2): Loom 1.17.21, Fabric Loader 0.19.5, Fabric API0.161.0+26.2, Java 25. Build profilemc262fabricon Gradle 9.6.0. It is not configured bymc262. - Fabric 26.3 cell (
mc-26.3/fabric): Fabric Loader 0.19.5, Fabric API0.161.0+26.3, Loom 1.17.x, Java 25. Build profilemc263fabricon Gradle 9.6.0. It is not configured bymc263.
Thirteen primary jars share version 2.2.0. 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.2.0.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.2.0.jar |
vonixguardian-neoforge-26.3-2.2.0.jar |
| 26.2 | vonixguardian-fabric-26.2-2.2.0.jar |
vonixguardian-neoforge-26.2-2.2.0.jar |
| 26.1.2 | — | vonixguardian-neoforge-26.1.2-2.2.0.jar |
| 1.21.1 | vonixguardian-fabric-1.21.1-2.2.0.jar |
vonixguardian-neoforge-1.21.1-2.2.0.jar |
| 1.20.1 | vonixguardian-fabric-1.20.1-2.2.0.jar |
vonixguardian-forge-1.20.1-2.2.0.jar |
| 1.19.2 | vonixguardian-fabric-1.19.2-2.2.0.jar |
vonixguardian-forge-1.19.2-2.2.0.jar |
| 1.18.2 | vonixguardian-fabric-1.18.2-2.2.0.jar |
vonixguardian-forge-1.18.2-2.2.0.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.