Export to Hytale

Before you export

Hytale assets are set up
Your world height is 320 (see below)
Big map? Give TalePainter enough RAM first

Export

Open Export → World.
Choose the target folder. For singleplayer that’s your Hytale saves folder (%APPDATA%\Hytale\UserData\Saves on Windows).
Check the options:
- NPC spawning: turn it off for test worlds.
- Beyond the map border: what Hytale generates outside your map. Void (nothing), Standard or Elevated vanilla terrain.
- Custom Layers tab: the order custom layers are exported in. Use the up and down arrows, the top one goes first. The order is saved with your world.
Export and open the world in Hytale’s Singleplayer list.

World height: use 320

TalePainter offers 320, 512, 640 and 1024 blocks. Vanilla Hytale only loads worlds that are exactly 320 high. Higher exports finish without an error, but the chunks crash when Hytale loads them and nobody can join.

Stick to 320 for normal Hytale and for servers.
Going higher only works with a height mod in Hytale, for example the early plugin world-height-y320 from CurseForge in your earlyplugins folder. Players have run 1024 in singleplayer this way. Servers are untested.
More height also makes the export a lot slower, because all the air has to be written too.

Test only part of the map

A full export of a big map takes hours. To check one area:

Select only the tiles you want to see.
Put the spawn point inside that area.
Use Test Export.

What the export contains

The export is a complete Hytale save, not only the world:

MyWorld/
├── config.json
├── bans.json
├── permissions.json
├── whitelist.json
└── universe/
    ├── memories.json
    ├── players/
    └── worlds/
        └── default/        ← the actual world
            ├── config.json
            ├── chunks/
            └── resources/

This matters when you put the world on a server, see Dedicated server.

In creative mode you are OP

Since 1.1.0 you stay operator in creative worlds, no more /op self on every join.