Litematica and WorldEdit

Litematica and WorldEdit

Expanded Building reads and writes Litematica (.litematic) and WorldEdit / Sponge (.schem) schematics directly. There is no detour via a projection you have to rebuild by hand: the file becomes a blueprint, and from then on it behaves exactly like one you planned yourself – same preview, same rotation, same material list, same builder.

Neither Litematica nor WorldEdit needs to be installed.

Folders

Each format has its own folder. Both are created on first start:

config/expanded_building/
├── blueprints/   your own blueprints (.json)
├── litematic/    Litematica files (.litematic)
└── schem/        WorldEdit files (.schem)

Just copy files into the right folder – no renaming needed.

Commands

Command	Purpose
/eb litematic list	List the files in the litematic folder
/eb litematic load <file> [carve]	Import a file and start positioning it
/eb litematic save <name> <project>	Export a project as .litematic
/eb schem list	List the files in the schem folder
/eb schem load <file> [carve]	Import a file and start positioning it
/eb schem save <name> <project>	Export a project as .schem

• Tab completes file names from the folder, including quotes if a name contains spaces.
• The file extension is optional, and upper/lower case does not matter.
• carve works as for your own blueprints and is on by default (see Blueprints).

As with blueprint load, you must be in planning mode: the import goes into your current planning session and is only written into the world when you place it. Positioning works exactly as described on the Blueprints page.

Supported formats

Format	Read	Written
.litematic	Versions 1 to 6, any number of regions	Version 5, one region
.schem	Sponge versions 2 and 3, gzip-compressed or raw	Sponge version 2

The older version is written because every reader that understands the new one also reads the old one, but not the other way round.

A .litematic often consists of several regions (Litematica writes one per selection box). All of them are merged into one blueprint. Regions with a negative size are handled correctly, so buildings are not mirrored.

The old MCEdit .schematic format with numeric block IDs is not supported – those IDs have had no meaning since Minecraft 1.13. Save such files as .schem or .litematic first.

What is dropped on import

• Air. Empty positions are not imported as clearing instructions – otherwise a 50×50×50 file would become 125,000 clearing commands. Empty space is covered by the blueprint's bounding box instead, which is exactly what carve clears.
• Blocks from mods that are not installed. They are skipped and reported in chat with count and block ID.
• Contents, entities and ticks. Blueprints only store block states, never NBT. Chests arrive empty, signs without text.
• Block properties that do not exist in this version. A file from another Minecraft version may carry properties this version does not know; they are dropped, the block stays.

On export, clearing instructions are written as air, because that is exactly what they are – a position that should be empty.

Limits

maxBlueprintBlocks (default 100,000) applies here too. A file with more blocks is rejected before anything is positioned.