Minecraft Wiki
Advertisement
This article is about the unofficial format used by many community programs. For the similar format used by structure blocks, see Structure block file format.
"Schematic" redirects here. For schematics on the Minecraft Wiki, see Help:Schematic.
Paper
The contents of this page are not supported by Mojang Studios or the Minecraft Wiki. 
Information icon
This feature is exclusive to Java Edition. 

The .schematic file format was created by the community to store sections of a Minecraft world for use with third-party programs (including MCEdit, Minecraft Note Block Studio, Redstone Simulator, WorldEdit, and Schematica). Schematics are in NBT format and are loosely based on the Indev level format. Indices for the Blocks and Data arrays are ordered YZX - that is, the X coordinate varies the fastest. This is similar to block ordering for Classic, Indev, and Anvil levels. This format cannot store or distinguish air blocks that should overwrite existing blocks from those that shouldn't.

NBT Structure[]

Coordinates in schematics range from (0,0,0) to (Width-1, Height-1, Length-1).

  •  Schematic: Schematic data.
    •  Width: Size along the X axis.
    •  Height: Size along the Y axis.
    •  Length: Size along the Z axis.
    •  Materials: This is "Classic" for schematics exported from Classic levels, "Pocket" for those from Pocket Edition levels, and "Alpha" for those from Alpha and newer levels.
    •  Blocks: Block IDs defining the terrain. 8 bits per block. Sorted by height (bottom to top) then length then width—the index of the block at X,Y,Z is (Y×length + Z)×width + X.
    •  AddBlocks: Extra bits that can be used to further define terrain; optional. Two nibbles are put into each index in this array. Unlike normal chunks, even indexes go on the high nibble and odd indexes go on the low nibble.
    •  Add deprecated: Old versions of Schematica used this instead of AddBlocks. Byte array where each byte contains additional data to define terrain, in order. This tag should not be written.
    •  Data: Block data additionally defining parts of the terrain. Only the lower 4 bits of each byte are used. (Unlike in the chunk format, the block data in the schematic format occupies a full byte per block.)
    •  Entities: List of Compound tags.
    •  TileEntities: List of Compound tags.
    •  Icon Used by Schematica as an item to use as an icon for the schematic. Does not include a Slot tag.
      • Tags common to all items
    •  SchematicaMapping: ID mapping for the version this schematic was saved in, used by Schematica. Provided only for materials used in the schematic.
      •  [name]: Indicates that name has the given ID (e.g. [name] being minecraft:stone and the value being 1).
    •  ExtendedMetadata: Arbitrary additional data, provided by Schematica for extensions. Optional, and is provided only if not empty.
    •  WEOriginX: WorldEdit-only origin X coordinate; optional but if one is provided all parts should be.
    •  WEOriginY: WorldEdit-only origin Y coordinate; optional but if one is provided all parts should be.
    •  WEOriginZ: WorldEdit-only origin Z coordinate; optional but if one is provided all parts should be.
    •  WEOffsetX: WorldEdit-only offset X coordinate; optional but if one is provided all parts should be.
    •  WEOffsetY: WorldEdit-only offset Y coordinate; optional but if one is provided all parts should be.
    •  WEOffsetZ: WorldEdit-only offset Z coordinate; optional but if one is provided all parts should be.
    •  itemStackVersion: MCEdit2-only; 17 if items use numeric IDs (1.7.x) and 18 if items use text IDs (1.8.x).
    •  BlockIDs: MCEdit2-only; maps numeric block IDs to textual IDs.
      •  [number]: The textual ID for the given number (e.g. [number] is 1 and the value is minecraft:stone)
    •  ItemIDs: MCEdit2-only; maps numeric item IDs to textual IDs. Provided only if itemStackVersion is 17.
      •  [number]: The textual ID for the given number (e.g. [number] is 1 and the value is minecraft:stone)
    •  TileTicks: MCEdit-Unified only; list of queued block updates (as in the chunk format)
    •  i: The ID of the block; used to activate the correct block update procedure.
    •  p: If multiple tile ticks are scheduled for the same tick, tile ticks with lower p are processed first. If they also have the same p, the order is unknown.
    •  t: The number of ticks until processing should occur. May be negative when processing is overdue.
    •  x: X position
    •  y: Y position
    •  z: Z position
    •  Biomes: MCEdit-Unified only; a byte array containing all biomes in the schematic.

Implementations[]

Advertisement