Formato indev

The .mclevel map format is an old map format, created by Notch. It is based on the NBT Format.

The map format is in use since indev version 0.31.

While Alpha (and Infdev) levels use NBT files, they have a very different file format.

For details on the infinite map format, see Alpha Level Format.

NBT Structure

• 
   MinecraftLevel: The root tag.
  • 
     About: Information about the level.
    • 
       CreatedOn: The Unix time when the level was created.
    • 
       Name: The name of the level, always "A Nice World".
    • 
       Author: The name of the user who created the level.
  • 
     Environment: Information about the environment of the level, which varies based on the map generation settings.
    • 
       TimeOfDay: The number of ticks since the start of the level. Affects the day/night cycle.
    • 
       SkyBrightness: The sky light level, 0 to 15.
    • 
       SkyColor: The color of the sky.
    • 
       FogColor: The color of the fog.
    • 
       CloudColor: The color of the clouds.
    • 
       CloudHeight: The height of the clouds (Y coordinate).
    • 
       SurroundingGroundType: The Block ID of the "surrounding ground".
    • 
       SurroundingGroundHeight: The height of the "surrounding ground".
    • 
       SurroundingWaterType: The Block ID of the "surrounding water".
    • 
       SurroundingWaterHeight: The height of the "surrounding water".
  • 
     Map: The actual map data.
    • 
       Width: The width of the level.
    • 
       Length: The length of the level.
    • 
       Height: The height of the level.
    • 
       Spawn: List of 3 TAG_Shorts for the X, Y, and Z spawn coordinates.
    • 
       Blocks: Width*Length*Height bytes of Block IDs.
    • 
       Data: Width*Length*Height bytes of Block Data and Lighting.
  • 
     Entities: List of TAG_Compounds for the entities in the level.
    • 
      An entity. See Chunk format -> Entity Format. Not all information is relevant to Minecraft Indev. The player has its own entity, shown below as an example.
      • 
         id: The entity ID. In this case, "LocalPlayer".
      • 
         Pos: List of 3 TAG_Doubles for the X, Y, and Z position of the player.
      • 
         Rotation: List of 2 TAG_Floats for the Yaw and Pitch of the player's view.
      • 
         Motion: List of 3 TAG_Doubles for the X, Y, and Z motion in meters per tick.
      • 
         FallDistance: How far the player has fallen.
      • 
         Health: The number of hit points the player has. 20 is 10 hearts.
      • 
         AttackTime: Number of ticks the player is immune to attacks.
      • 
         HurtTime: Number of ticks the player is red from being attacked.
      • 
         DeathTime: Number of ticks the player has been dead for - used for controlling the death animation.
      • 
         Air: The number of ticks before the player starts to drown. Starts at 300.
      • 
         Fire: When negative, the number of ticks before the player can catch on fire. When positive, the number of ticks before the fire is extinguished.
      • 
         Score: The player's score.
      • 
         Inventory: List of TAG_Compounds representing the items in the player's inventory.
        • 
          An inventory item.
          • 
             Slot: The Slot the item is in.
          • 
             id: The Item ID.
          • 
             Damage: The item's data value, or damage value for tools.
          • 
             Count: The number of this item in the stack. Range -128 to 127. Values less than 2 are not displayed in-game.
  • 
     TileEntities: List of TAG_Compounds for the tile entities in the level.
    • 
      A tile entity.
      • See Chunk format -> Tile Entity Format. Not all information is relevant to Minecraft Indev.
      • 
         Pos: Position of the tile entity. X coordinate is Pos % 1024, Y is (Pos >> 10) % 1024, Z is (Pos >> 20) % 1024.

Blocks

The block byte array is used to define the types of blocks that occupy a map. The number of bytes in the array may be calculated by multiplying the dimensions of the map. Y being the up direction rather than Z. For Hex values see Block IDs.

To access a specific block from either the block or data array from XYZ coordinates, use the following formula:

Index = x + (y * Height + z) * Width

Data

The Data byte array is used for lighting and extra block data. The first 4 bit contains the extra block data (also known as metadata) and the other 4 bits the lighting.

For extended information on block metadata, refer to Data values.

Lighting

There are 16 levels of lighting for a block ranging from 0x0 (no light) to 0xF (full light).