Repository navigation
Export and Litematica
Export writes a palette as a schematic, and Litematica can load it as a selected placement.
Open Export from Palettes or Gradient. Diorama's Export starts with the wall you see. Select Layout and Format, then press Export. You don't need creative mode, operator rights or Litematica to save a file.
.litematic is for Litematica and Forgematica. Its metadata has the palette name, your player name as author, and the share string as description. .nbt is a vanilla structure file. Both preserve block-state properties. Neither contains entities, inventories or other block-entity data.
| Layout | What it writes |
|---|---|
| Strip | One block per entry, in palette order |
| Wall | One column per entry, three blocks high by default |
| Patch grid | One square per entry, 3 by 3 by default, in reading order from the top left |
| Noise clusters | A wall of clustered blocks, mixed by weight |
| Height gradient | A wall running through palette order from bottom to top, with weights setting the shares |
| Random dither | A wall of randomly mixed blocks, by weight |
All layouts are upright, one block deep. Width runs east, and height runs upward. Diorama layouts start at 16 by 9. Height and Width allow up to 256 where they apply. Patch allows 1 to 16. Gap adds one block of air between entries in Strip, Wall and Patch grid. It doesn't apply to the mixed walls.
Weights affect the three mixed walls. Strip, Wall and Patch grid give each entry the same space.
The exporter leaves out unknown blocks, invalid states and entries past a layout's 256-block limit. It reports what it left out. If no blocks resolve, it writes no file. Vanilla structure blocks have a smaller 48-block loading limit. Use a suitably sized layout for those.
In .nbt, gap cells are omitted. Loading that structure doesn't clear existing blocks in its gaps.
The Export folder setting takes priority. A relative path starts in your game folder. With it empty, files go to Litematica's configured schematics folder when available, or <game>/schematics/ otherwise.
Names look like chroma-castle-wall.litematic. Spaces and punctuation in a palette name become hyphens. If that name exists, the next file is chroma-castle-wall-2.litematic, then -3. An export never silently overwrites a file.
Vanilla doesn't search Chroma's export folder. For a singleplayer world, copy an .nbt file into <game>/saves/<world>/generated/minecraft/structure/. Create those folders if needed. For example, put chroma-castle-wall.nbt there, then use a structure block in Load mode with the name minecraft:chroma-castle-wall.
On a server, the file needs to go in that server world's corresponding folder. Loading structures needs the game's permission to use structure blocks. Keep the structure within the vanilla 48-block size limit.
Export and place writes a .litematic and loads it into Litematica. It creates a selected schematic placement, ready for Litematica's tools to move. The default origin is the block you look at within reach. If there is no such block, it uses your position. The Litematica placement setting can always use Where you stand instead.
This loads a schematic placement. It doesn't put blocks into the world. Use Litematica itself for any later building or pasting.
Export and place stays greyed out without Litematica, for .nbt, or outside a world. Forgematica on NeoForge uses the same integration. Install that mod's own dependencies too. If loading fails, Chroma reports the error and keeps the exported file.
You can also load a file through Litematica's own menus.
/chroma export chroma1:stone,andesite/Castle wall litematic
/chroma export "chroma1:stone,andesite/My wall" patch_grid nbt
/chroma export chroma1:stone,andesite/Castle strip litematic place
/chroma place chroma-castle-strip
/chroma place searches the export folder. Give the file name with or without its extension. The export options and quoting rules are on Keys and commands. Commands use the default wall height or mixed-wall size; use the dialog to change dimensions.