📦 Prefab Material Analyzer

Hytale Prefab Material Analyzer

Turn an unreadable prefab file into an actionable build plan: a clean structure-only shopping list, readable block names, collection progress and top-down Y layers.

✓ Local and private

Open a Hytale prefab to get a clean shopping list and a layer-by-layer construction guide.

1
Import the prefab

Choose the .prefab.json exported by Hytale or a compatible creative tool.

2
Prepare the materials

Use Structure only to exclude terrain and track what you have already collected.

3
Build one layer at a time

Start at the suggested Y layer, follow the top-down map and mark completed layers.

How to use it

  • Import the .prefab.json and keep Structure only selected to remove dirt, grass and terrain foundation.
  • Collect the readable material list, recording how many blocks you already have; internal state variants are merged automatically.
  • Use the prefab anchor as your origin, build the suggested lowest Y layer from the top-down map and mark each layer complete.
  • Highlight individual materials when a layer is complex, then export CSV or print the checklist for another screen.

From prefab file to a build you can execute

A raw .prefab.json is useful to the game but difficult for a player to read. The analyzer converts block coordinates into a clean material list, separates terrain from the actual structure, merges internal state variants and identifies the first useful building layer.

The result is designed for manual construction: gather the listed blocks, use the anchor as the origin, reproduce each top-down Y layer and mark it complete. Parsing happens in a Web Worker and the file remains in your browser.

What the analyzer solves

  • Remove thousands of terrain blocks from a structure-only shopping list
  • Merge corner, door and other state variants into their base material
  • Understand X, Y and Z placement without reading JSON
  • Highlight one material while building a complex layer
  • Track collected materials and completed layers independently
  • Export a portable checklist for a second screen or mobile device

Interpret the result safely

  • Keep the original prefab unchanged.
  • Review ignored Empty entries and duplicate-coordinate warnings.
  • Treat unknown block names as version or asset-pack dependencies.
  • Verify anchor and orientation inside Hytale before building.
  • Use the layer viewer as a plan, not a replacement for an in-game preview.

How to use the layer map in Hytale

The layer map is a top-down plan, not an automatic importer. Treat the prefab anchor as coordinate 0,0,0, build the suggested lowest structural Y layer first, and then advance upward. X is shown horizontally and Z vertically so you can reproduce the footprint without guessing where each block belongs.

For large layers, select a material in the highlight filter. Other blocks become muted while the selected material stays colored, which is useful for placing walls, roofs, stairs or decorative passes separately.

Why Structure only is the recommended scope

Many exported prefabs contain dirt, grass or other terrain beneath the actual building. White Castle, for example, contains thousands of foundation blocks before the first architectural layer. Structure only removes those terrain categories from the shopping list and starts the layer guide at the first useful construction level.

Switch to Full prefab only when you deliberately need to reproduce the landscape foundation. The original coordinates are preserved in both modes.

How material names are cleaned up

Hytale can store internal state names for corners, open doors, watered soil and similar variants. Those entries are not usually separate inventory items. HyTools merges names containing State_Definitions into their placeable base block and reports how many internal variants were combined.

The readable material name is shown first, while the original block ID remains visible underneath for troubleshooting asset packs or version differences.

How progress is matched to a file

HyTools calculates a SHA-256 fingerprint from the local file and uses it only as the browser-storage key. This keeps material counts and completed layers for different prefabs separate without uploading the file or retaining its contents.

If the prefab changes, its fingerprint changes and it receives a separate plan. Export CSV for a spreadsheet or print the checklist when you need the plan outside this browser.

Format reference

The implementation follows the public structure used by Hytale prefab parsers: version fields, anchor coordinates and arrays of named blocks, fluids and entities.

Frequently asked questions

Is my prefab uploaded?

No. The file is read by a background worker in your browser and never sent to HyTools.

Why are Empty blocks excluded?

Empty entries describe vacant cells rather than materials you must collect, so they are reported as a warning but excluded from totals.

Can this edit or render the prefab in 3D?

No. This version focuses on material planning, validation and a practical 2D layer viewer.

How do I use the Y layers in game?

Treat the prefab anchor as the origin. Start with the lowest structural Y suggested by the tool, reproduce the X/Z top-down pattern, then move to the next Y layer.

Why did the material count become smaller after import?

Structure-only mode excludes terrain and the analyzer merges internal State_Definitions variants into the placeable base block instead of treating them as separate inventory items.