Hytale World Doctor
Scan a Hytale world the way the server reads it: every region file, every stored chunk, every block palette. Find what is broken - unreadable chunks, bad compression, the converted-world "everything is underground" heightmap bug, blocks the game cannot resolve - and download repaired region files. Runs in your browser; nothing is uploaded.
Findings
Repaired files
Download hytale-world-repairs.zip - copy the files over the originals (same paths) with the server stopped. A README with exact steps is inside.
Want this on a real server? Supercraft hosts Hytale →
What is actually inside a Hytale world
Hytale stores chunks in *.region.bin files - each one an indexed container of up
to 32x32 chunks, each chunk a compressed document holding ten 32x32x32 block sections with
name-based palettes, a surface heightmap, biome tints, entities and per-block components. The
doctor implements that format faithfully (it was built against real dedicated-server saves and
cross-checked with an independent community parser), so a scan here is a dry run of what your
server will accept.
When a chunk is damaged, the game's behavior ranges from silently regenerating terrain to crashing on interaction, depending on where the damage sits. The doctor's philosophy: repair what can be repaired exactly (heightmaps), remove what the game itself cannot read (so terrain regenerates cleanly instead of crashing), and report - never guess about - everything else.
Moving a fixed world to always-on hosting? Hytale server hosting - upload the world folder through the file manager and it is live.
FAQ
Why does my converted world render as if everything is underground?
Converters that write blocks without recomputing the per-column surface heightmap leave the stored surface at the wrong height - the renderer then treats whole areas as below ground and teleports drop you under the map. The doctor recomputes the surface from the blocks actually present and rewrites just that heightmap. Your builds are untouched.
Why does the world crash when breaking or placing blocks?
Usually an unreadable chunk (truncated or badly compressed) or palette entries the game cannot resolve. Unreadable chunks get quarantined so the server regenerates them; unmapped blocks are listed by name and count so you can see what the converter missed.
A conversion "finished" suspiciously fast and the world folder is smaller. Did it lose chunks?
Run the checkup: the summary counts every chunk actually stored per region file. A silent partial conversion shows up immediately as missing regions or sparsely filled ones.
Is anything uploaded?
No. Files are read in your browser, one region at a time, and the repair zip is built locally. Multi-gigabyte worlds are fine through the folder picker.
What about RocksDB worlds?
Worlds switched to the optional RocksDB chunk backend are detected and reported as unsupported - the tool will not misread them. The default file store, which converters and most servers use, is fully supported.
What does the doctor actually check?
Region container integrity (magic, index table, segment bounds), per-chunk decompression, the chunk document structure (block sections, palettes, entities, per-block components), palette block names against the game's naming scheme, and the stored surface heightmap against the blocks actually present. Fixes: unreadable chunks are dropped from the region index so the server regenerates that terrain, and wrong heightmaps are rebuilt in place. Everything else is reported, not silently rewritten.
Which worlds does it support?
Any world using Hytale's default file chunk store - the universe/worlds/<name>/chunks/*.region.bin layout that dedicated servers, singleplayer and the community Minecraft-to-Hytale converters all write. Worlds switched to the optional RocksDB backend are detected and reported as unsupported rather than misread.
Will I lose builds when a chunk is quarantined?
A quarantined chunk was unreadable to the game as well - it is the chunk that crashes the server or shows as a hole. Removing it from the region index makes the server regenerate that 32x32 column of terrain on first visit. Everything the doctor can read stays byte-identical.