Local Minecraft Java repair tool

Wake up frozen vaults

Reset stale vault timing data in a structure or complete Java world. Everything runs in this browser, your source is never changed, and the fix downloads as a separate copy.

The vault timing bug

Why a vault freezes

Each vault stores a tick for when it may next update. Worlds carried through some edits or version jumps leave that value set far in the future, so the vault never re-arms: it ignores its key, plays no animation, and drops no loot. Zeroing the timer wakes every affected vault at once.

A field of dark, inactive vaults that ignore the player
Frozen stuck timer, no response
The same vaults glowing and active after the fix
Fixed active and lootable
  1. 1
    Choose

    Drop a structure, zipped world, or world folder.

  2. 2
    Inspect

    It scans locally and builds a separate fixed copy.

  3. 3
    Swap in

    Download the copy and test a vault before going live.

Only one vault? Fix it in-game. Java Edition. Stand on the vault, enable commands, and run this as operator. 0L is a 64-bit Long.
/data modify block ~ ~-1 ~ server_data.state_updating_resumes_at set value 0L

Repair a world or structure

Drop a .nbt, .zip, or world folder Java structure .nbt, a zipped world, or a world folder. Bedrock is not supported.
No files selected

Runs locally. Nothing is uploaded, this page has no processing server.

Ready when you are.

Exact repair scope minecraft:vault → server_data → state_updating_resumes_at (Long) = 0

Only the existing eight-byte value is zeroed. No vault configuration, loot table, rewarded-player list, block state, entity, terrain, or other world data is intentionally altered.

Prefer to fix it by hand? Vanilla commands, structure export, NBTExplorer, and safety notes

Manual alternatives

A few vaults only? Vanilla commands or NBTExplorer may be quicker. Make a backup first in either case.

01 Fix one vault in-gameVanilla /data command

The one-liner at the top of this page uses relative coordinates. To target a vault by absolute position instead:

/data modify block <x> <y> <z> server_data.state_updating_resumes_at set value 0L
  • Use 0L with a capital or lowercase L. It is a 64-bit Long. 0s makes a Short and is the wrong type.
  • This resets the timer only. Loot configuration, rewarded players, and the ominous setting are kept.
  • Do not repair with /setblock; it can discard the vault's existing block-entity data.
02 Repair a structure before exportRound-trip through a structure block
  1. Place and load the structure with a structure block.
  2. Run the command above once for every vault coordinate.
  3. Save the structure immediately under a new name.
  4. Use that new .nbt in WorldPainter.

The vault's visual ominous block state is separate from this frozen timer. This repair does not turn a regular vault ominous or change its key and loot.

03 Edit it with NBTExplorerManual tag editing
Structure .nbt

Open a copied structure file, expand blocks, and inspect each list entry's nbt compound. Find entries whose id is minecraft:vault.

Complete Java world

Open a copied world folder, then its dimension's region folder and relevant r.x.z.mca. Expand the chunk and block_entities. Older formats may show a Level wrapper or call the list TileEntities.

For every matching vault, expand minecraft:vault → server_data → state_updating_resumes_at, confirm the tag type is Long, set its value to 0, and save. Searching the string minecraft:vault is safer than opening every numbered entry.

Close Minecraft and stop the server before editing. Never edit the only copy of a world, and never delete an entire block entity or region to clear this one value.

Applying the result

  1. Keep your original world as the backup. The tool never overwrites it.
  2. Fully stop Minecraft or your server before replacing any save files.
  3. For a world, the download is an overlay: it holds only the region files that changed. Extract it into your world folder, replacing the originals, then test a vault near a player. A single structure downloads as one fixed .nbt instead.

Compatibility: Java Edition Anvil regions using gzip, zlib, or uncompressed chunks. Rare LZ4 or external (.mcc) chunks are preserved and reported as not scanned. World folders are read one file at a time, so even multi-GB saves fit in memory. A single zipped world is decompressed in full, so very large zips still need the folder instead.