Chunk format

This article is about the latest official PC version of Minecraft. For the 2013 April Fools' day "Minecraft 2.0" version, see Minecraft 2.0/Chunk format.

Chunks store the terrain and entities within a 16×256×16 area. They also store precomputed lighting, heightmap data for Minecraft's performance, and other meta information.

Chunks were first introduced in Minecraft Infdev. Before the addition of the MCRegion format in Beta 1.3, chunks were stored as individual chunk files ".dat" where the file names contained the chunk's position encoded in Base36 - this is known as the Alpha level format. MCRegion changed this by storing groups of 32×32 chunks in individual ".mcr" files with the coordinates in Base10, with the goal being to reduce disk usage by cutting down on the number of file handles Minecraft had open at once. MCRegion's successor is the current format, Anvil, which only made changes to the chunk format. The region file technique is still used, but the region file extensions are ".mca" instead.

The major change from MCRegion to Anvil was the division of Chunks into Sections; each chunk has up to 16 individual 16×16×16 block Sections so that completely empty sections will not be saved at all. Preparation has also been made to support blocks with IDs in the range 0 to 4095, as compared to the previous 0 to 255 limitation. However, Minecraft is not fully prepared for such blocks to exist as items; many item IDs are already taken in the range 256 to 4095.

The Blocks, Data, BlockLight, and SkyLight arrays are now housed in individual chunk Sections. The Data, SkyLight, and BlockLight are arrays of 4-bit values, and the BlockLight and SkyLight arrays no longer house part of the block ID. The Blocks array is 8 bits per block, and the 4096-blocks support exists in the form of an optional Add byte array of 4-bits per block for additional block ID information. With the Anvil format, the NBT Format was changed from Notch's original specification to include an integer array tag similar to the existing byte array tag. It is currently only used for HeightMap information in chunks.

NBT Structure

See also: Information from the Anvil format page

Chunks are stored in NBT format, with this structure (see Block Format below for the ordering of the blocks within each array):

• The root tag.
  •  Level: Chunk data.
    •  xPos: X position of the chunk.
    •  zPos: Z position of the chunk.
    •  LastUpdate: Tick when the chunk was last saved.
    •  LightPopulated: 1 or 0 (true/false) - Unknown.
    •  TerrainPopulated: 1 or not present (true/false) indicate whether the terrain in this chunk was populated with special things. (Ores, special blocks, trees, dungeons, flowers, waterfalls, etc.) If set to zero then Minecraft will regenerate these features in the blocks that already exist.
    •  V: Currently always saved as 1 and not actually loaded by the game. Likely a chunk version tag.
    •  InhabitedTime: The cumulative number of ticks players have been in this chunk. Note that this value increases faster when more players are in the chunk. Used for regional difficulty: increases the chances of mobs spawning with equipment, the chances of that equipment having enchantments, the chances of spiders having potion effects, the chances of mobs having the ability to pick up dropped items, and the chances of zombies having the ability to spawn other zombies when attacked. Note that at values 3600000 and above, regional difficulty is effectively maxed for this chunk. At values 0 and below, the difficulty is capped to a minimum (thus, if this is set to a negative number, it will behave identically to being set to 0, apart from taking time to build back up to the positives).
    •  Biomes: May not exist. 256 bytes of biome data, one byte for each vertical column in the chunk. See Data Values for biome IDs. If this tag does not exist it will be created and filled by Minecraft when the chunk is loaded and saved. If any values in this array are -1, Minecraft will also set them to the correct biome.
    •  HeightMap: 1024 bytes(256 TAG_Int) of heightmap data. 16 × 16. Each byte records the lowest level in each column where the light from the sky is at full strength. Speeds computing of the SkyLight.
    •  Sections: List of Compound tags, each tag is a sub-chunk of sorts.
      • An individual Section.
        •  Y: The Y index (not coordinate) of this section. Range 0 to 15 (bottom to top), with no duplicates but some sections may be missing if empty.
        •  Blocks: 4096 bytes of block IDs defining the terrain. 8 bits per block, plus the bits from the below Add tag.
        •  Add: May not exist. 2048 bytes of additional block ID data. The value to add to (combine with) the above block ID to form the true block ID in the range 0 to 4095. 4 bits per block. Combining is done by shifting this value to the left 8 bits and then adding it to the block ID from above.
        •  Data: 2048 bytes of block data additionally defining parts of the terrain. 4 bits per block.
        •  BlockLight: 2048 bytes recording the amount of block-emitted light in each block. Makes load times faster compared to recomputing at load time. 4 bits per block.
        •  SkyLight: 2048 bytes recording the amount of sunlight or moonlight hitting each block. 4 bits per block.
    •  Entities: Each TAG_Compound in this list defines an entity in the chunk. See Entity Format below. If this list is empty it will be a list of Byte tags.
    •  TileEntities: Each TAG_Compound in this list defines a tile entity in the chunk. See Tile Entity Format below. If this list is empty it will be a list of Byte tags.
    •  TileTicks: May not exist. Each TAG_Compound in this list is an "active" block in this chunk waiting to be updated. These are used to save the state of redstone machines, falling sand or water, and other activity. See Tile Tick Format below. This tag may not exist.

Block Format

In the Anvil format, block positions are ordered YZX for compression purposes.

The coordinate system is as follows:

• X increases East, decreases West
• Y increases upwards, decreases downwards
• Z increases South, decreases North

This also happens to yield the most natural scan direction, because all indices in the least significant dimension (i.e. X in this case) appear for each index in the next most significant dimension; so one reads an array ordered YZX as one would a book lying with its top northward, all letters (or X-indices) on a single line (or Z-index) at a time, and all lines on a single page (or Y-index) at a time. For the 2D arrays (i.e. "Biomes" and "HeightMap") the inapplicable Y dimension is simply omitted, as though the book is only one page thick.

Each section in a chunk is a 16x16x16-block area, with up to 16 sections in a chunk. Section 0 is the bottom section of the chunk, and section 15 is the top section of the chunk. To save space, completely empty sections are not saved. Within each section is a byte tag "Y" for the Y index of the section, 0 to 15, and then byte arrays for the blocks. The "Block" byte array has 4096 partial block IDs at 8 bits per block. Another byte array "Add" is used for block with IDs over 255, and is 2048 bytes of the other part of the 4096 block IDs at 4 bits per block. When both the "Block" and "Add" byte arrays exist, the partial ID from the "Add" array is shifted left 8 bits and added to the partial ID from the "Blocks" array to form the true Block ID. The "Data" byte array is also 2048 bytes for 4096 block data values at 4 bits per block. The "BlockLight" and "SkyLight" byte arrays are the same as the "Data" byte array but they are used for block light levels and sky light levels respectively. The "SkyLight" values represent how much sunlight or moonlight can potentially reach the block, independent of the current light level of the sky.

The endianness of the 2048-byte arrays (i.e. "Add," "Data," "BlockLight," & "SkyLight"), which give only 4 bits per block, seems to stand as the one anomalous exception to the otherwise consistent, format-wide standard of big-endian data storage. It also runs counter to the presumably natural human-readable printing direction. If the blocks begin at 0, they are grouped with even numbers preceding odd numbers (i.e. 0 & 1 share a byte, 2 & 3 share the next, etc.); under these designations Minecraft stores even-numbered blocks in the least significant half-byte, and odd-numbered blocks in the most significant half-byte. Thus block[0] is byte[0] at 0x0F, block[1] is byte[0] at 0xF0, block[2] is byte[1] at 0x0F, block[3] is byte[1] at 0xF0, etc. ...

The pseudo-code below shows how to access individual block information from a single section. Hover over text to see additional information or comments.

byte Nibble4(byte[] arr, int index){ return index%2 == 0 ? arr[index/2]&0x0F : (arr[index/2]>>4)&0x0F; }
int BlockPos = y*16*16 + z*16 + x;
byte BlockID_a = Blocks[BlockPos];
byte BlockID_b = Nibble4(Add, BlockPos);
short BlockID = BlockID_a + (BlockID_b << 8);
byte BlockData = Nibble4(Data, BlockPos);
byte Blocklight = Nibble4(BlockLight, BlockPos);
byte Skylight = Nibble4(SkyLight, BlockPos);

Entity Format

Every entity is an unnamed TAG_Compound contained in the Entities list of a chunk file. The sole exception is the Player entity, stored in level.dat, or in <player>.dat files on servers. All entities share this base:

• Entity data
  •  id: Entity ID. This tag does not exist for the Player entity.
  •  Pos: 3 TAG_Doubles describing the current X,Y,Z position of the entity.
  •  Motion: 3 TAG_Doubles describing the current dX,dY,dZ velocity of the entity in meters per tick.
  •  Rotation: Two TAG_Floats representing rotation in degrees.
    • The entity's rotation clockwise around the Y axis (called yaw). Due west is 0. Does not exceed 360 degrees.
    • The entity's declination from the horizon (called pitch). Horizontal is 0. Positive values look downward. Does not exceed positive or negative 90 degrees.
  •  FallDistance: Distance the entity has fallen. Larger values cause more damage when the entity lands.
  •  Fire: Number of ticks until the fire is put out. Negative values reflect how long the entity can stand in fire before burning. Default -20 when not on fire.
  •  Air: How much air the entity has, in ticks. Fills to a maximum of 300 in air, giving 15 seconds submerged before the entity starts to drown, and a total of up to 35 seconds before the entity dies (if it has 20 health). Decreases while underwater. If 0 while underwater, the entity loses 1 health per second.
  •  OnGround: 1 or 0 (true/false) - true if the entity is touching the ground.
  •  Dimension: Unknown usage; entities are only saved in the region files for the dimension they are in. -1 for The Nether, 0 for The Overworld, and 1 for The End.
  •  Invulnerable: 1 or 0 (true/false) - true if the entity should not take damage. This applies to living and nonliving entities alike: mobs will not take damage from any source (including potion effects), and cannot be moved by fishing rods, attacks, explosions, or projectiles, and objects such as vehicles and item frames cannot be destroyed unless their supports are removed. Note that these entities can be damaged by players in Creative mode.
  •  PortalCooldown: The number of ticks before which the entity may be teleported back through a portal of any kind. Initially starts at 900 ticks (45 seconds) after teleportation and counts down to 0.
  •  UUIDMost: The most significant bits of this entity's Universally Unique IDentifier. This is joined with UUIDLeast to form this entity's unique ID.
  •  UUIDLeast: The least significant bits of this entity's Universally Unique IDentifier.
  •  UUID: The Universally Unique IDentifier of this entity. Converts a hexadecimal UUID (for example: 069a79f4-44e9-4726-a5be-fca90e38aaf5) into the UUIDLeast and UUIDMost tags. Will not apply new UUIDLeast and UUIDMost tags if both of these tags are already present. The "UUID" tag is removed once the entity is loaded.
  •  CustomName: The custom name of this entity. Appears in player death messages and villager trading interfaces, as well as above the entity when your cursor is over it. May not exist, or may exist and be empty.
  •  CustomNameVisible: 1 or 0 (true/false) - if true, and this entity has a custom name, it will always appear above them, whether or not the cursor is pointing at it. If the entity hasn't a custom name, a default name will be shown. May not exist.
  •  Silent: 1 or 0 (true/false) - if true, this entity will not make sound. May not exist. Can be used in 14w30a or later.
  •  Riding: The data of the entity being ridden. Note that if an entity is being ridden, the topmost entity in the stack has the Pos tag, and the coordinates specify the location of the bottommost entity. Also note that the bottommost entity controls movement, while the topmost entity determines spawning conditions when created by a mob spawner.
    • See this format (recursive).
  •  CommandStats: Information identifying scoreboard parameters to modify relative to the last command run
    •  SuccessCountObjective: Objective's name about success of the last command (will be a boolean)
    •  SuccessCountName: Fake player name about success of the last command
    •  AffectedBlocksObjectuve: Objective's name about how many blocks were modified in the last command (will be an int)
    •  AffectedBlocksName: Fake player name about how many blocks were modified in the last command
    •  AffectedEntitiesObjective: Objective's name about how many entities were altered in the last command (will be an int)
    •  AffectedEntitiesName: Fake player name about how many entities were altered in the last command
    •  AffectedItemsObjective: Objective's name about how many items were altered in the last command (will be an int)
    •  AffectedItemsName: Fake player name about how many items were altered in the last command
    •  QueryResultObjective: Objective's name about the query result of the last command
    •  QueryResultName: Fake player name about the query result of the last command

Mobs

Mobs are a subclass of Entity with additional tags to store their health, attacking/damaged state, potion effects, and more depending on the mob. Players are a subclass of Mob.

Mob Entities
Entity ID	Name
Bat	Bat
Blaze	Blaze
CaveSpider	Cave Spider
Chicken	Chicken
Cow	Cow
Creeper	Creeper
EnderDragon	Ender Dragon
Enderman	Enderman
Endermite	Endermite
Ghast	Ghast
Giant	Giant
Guardian	Guardian
EntityHorse	Horse
LavaSlime	Magma Cube
MushroomCow	Mooshroom
Ozelot	Ocelot
Pig	Pig
PigZombie	Zombie Pigman
Rabbit	Rabbit
Sheep	Sheep
Silverfish	Silverfish
Skeleton	Skeleton Wither Skeleton
Slime	Slime
SnowMan	Snow Golem
Spider	Spider
Squid	Squid
Villager	Villager
VillagerGolem	Iron Golem
Witch	Witch
WitherBoss	Wither
Wolf	Wolf
Zombie	Zombie Zombie Villager

• Mobs have these additional fields:
  •  HealF: Amount of health the entity has, in floating point format. A value of 1 is half a heart. Used when more precise health values are needed, such as the health of entities being damaged by a player with the Weakness effect (if the player isn't holding an item that increases their attack damage, they deal 1/2 a health point, 1/4 a heart). If this tag exists, Health will be ignored.
  •  Health: Amount of health the entity has. Used when whole-number health values are needed, such as displaying a player's health on their HUD. If the HealF tag exists, this tag will be ignored.
  •  AbsorptionAmount: Amount of extra health added by Absorption effect.
  •  AttackTime: Number of ticks the mob's "invincibility shield" lasts after the mob was last struck. 0 when not recently hit.
  •  HurtTime: Number of ticks the mob turns red for after being hit. 0 when not recently hit.
  •  HurtByTimestamp: The last time the mob was damaged, measured in the number of ticks since the mob's creation. Updates to a new value whenever the mob is damaged, then updates again 101 ticks later for reasons unknown. Can be changed with the entitydata command, but the specified value does not affect natural updates in any way, and is overwritten if the mob receives damage.
  •  DeathTime: Number of ticks the mob has been dead for. Controls death animations. 0 when alive.
  •  Attributes: A list of Attributes for this mob. These are used for many purposes in internal calculations, and can be considered a mob's "statistics". Valid Attributes for a given mob are listed in the main article.
    • An individual Attribute.
      •  Name: The name of this Attribute.
      •  Base: The base value of this Attribute.
      •  Modifiers: A list of Modifiers acting on this Attribute. Modifiers alter the Base value in internal calculations, without changing the original copy. Note that a Modifier will never modify Base to be higher than its maximum or lower than its minimum for a given Attribute.
        • An individual Modifier.
          •  Name: The Modifier's name.
          •  Amount: The amount by which this Modifier modifies the Base value in calculations.
          •  Operation: 0, 1, or 2. Defines the operation this Modifier executes on the Attribute's Base value. 0: Increment X by Amount, 1: Increment Y by X * Amount, 2: Y = Y * (1 + Amount) (equivalent to Increment Y by Y * Amount). The game first sets X = Base, then executes all Operation 0 modifiers, then sets Y = X, then executes all Operation 1 modifiers, and finally executes all Operation 2 modifiers.
          •  UUIDMost: The most significant bits of this Modifier's Universally Unique IDentifier. Used to reference modifiers in memory and ensure duplicates are not applied.
          •  UUIDLeast: The least significant bits of this Modifier's Universally Unique IDentifier.
  •  ActiveEffects: The list of potion effects on this mob. May not exist.
    • A potion effect
      •  Id: The effect ID.
      •  Amplifier: The potion effect level. 0 is level 1.
      •  Duration: The number of ticks before the effect wears off.
      •  Ambient: 1 or 0 (true/false) - true if this effect is provided by a Beacon and therefore should be less intrusive on screen.
      •  ShowParticles: 1 or 0 (true/false) - true if particles are shown (affected by "Ambient"). false if no particles are shown.
  •  Equipment: The list of compound tags of the equipment the mob has. Each compound tag in the list is an Item without the slot tag. All 5 entries will always exist, but may be empty compound tags to indicate no item.
    • 0: The item being held in the mob's hand.
    • 1: Armor (Feet)
    • 2: Armor (Legs)
    • 3: Armor (Chest)
    • 4: Armor (Head)
  •  DropChances: List of float values from 0 to 1 representing the chance for a carried item to drop. By default these are all 0.085, but they get set to 2 if the mob picks up an item. Items with durability held by a mob that have an associated DropChances greater than 1.0 will retain the defined durability of the item. If the DropChances is 1.0 or lower, the durability is randomized. If the "Unbreakable" tag exists on the item, the durability will be assigned as defined, regardless of the DropChances value.
    • 0: Chance to drop the item being carried.
    • 1: Chance for the armor. (Feet)
    • 2: Chance for the armor. (Legs)
    • 3: Chance for the armor. (Chest)
    • 4: Chance for the armor. (Head)
  •  CanPickUpLoot: 1 or 0 (true/false) - true if the mob can pick up loot (wear armor it picks up, use weapons it picks up).
  •  NoAI: 1 or 0 (true/false) - If true, the mob's AI will be disabled. The mob will not attempt to move and cannot move, to the extent of not falling when normally able. Can be used in 14w32a or later
  •  PersistenceRequired: 1 or 0 (true/false) - true if the mob must not despawn naturally.
  •  Leashed: 1 or 0 (true/false) - whether the mob is leashed.
  •  Leash: Either contains a UUID long pair, if this leash connects to another entity, or an X, Y, Z int trio if this leash connects to a fencepost.
    •  UUIDMost: The most significant bits of the Universally Unique IDentifier of the entity this leash connects to.
    •  UUIDLeast: The least significant bits of the Universally Unique IDentifier of the entity this leash connects to.
    •  X: The X coordinate of the fencepost this leash connects to.
    •  Y: The Y coordinate of the fencepost this leash connects to.
    •  Z: The Z coordinate of the fencepost this leash connects to.
  •  GoldenAppleOverflow (removed): Unknown value.

• Additional fields for mobs that can breed:
  •  InLove: Number of ticks until the mob loses its breeding hearts and stops searching for a mate. 0 when not searching for a mate.
  •  Age: Represents the age of the mob in ticks; when negative, the mob is a baby. When 0 or above, the mob is an adult. When above 0, represents the number of ticks before this mob can breed again.
  •  ForcedAge: A value of age which will be assigned to this mob when it grows up. Incremented when a baby mob is fed.

• Additional fields for mobs that can be tamed by players:
  •  Owner: Name of the player that owns this mob for pre-1.8. Empty string if no owner.
  •  OwnerUUID: UUID of the player that owns this mob for 1.8. Empty string if no owner.
  •  Sitting: 1 or 0 (true/false) - true if the mob is sitting.

• Bat has these additional fields:
  •  BatFlags: 1 when hanging upside-down from a block, 0 when flying.

• Chicken has these additional fields:
  •  IsChickenJockey: 1 or 0 (true/false) - Whether or not the chicken is a jockey for a baby zombie. True if the chicken can naturally despawn. Other effects are unknown. Baby zombies can still control a ridden chicken even if this is set false.
  •  EggLayTime: Number of ticks until the chicken should lay its egg and reset this timer to a new roughly random value.

• Creeper has these additional fields:
  •  powered: 1 or 0 (true/false) - May not exist. True if the creeper is charged from being struck by lightning.
  •  ExplosionRadius: The radius of the explosion itself, default 3.
  •  Fuse: The number of ticks before the creeper will explode (does not affect creepers that fall and explode upon impacting their victim). Default 30.
  •  ignited: 1 or 0 (true/false) - Whether the creeper has been ignited by a Flint and Steel.

• Enderman has these additional fields:
  •  carried: ID of the block carried by the Enderman. When not carrying anything, 0.
  •  carriedData: Additional data about the block carried by the Enderman. 0 when not carrying anything.
  •  EndermiteCount: Number of Endermites that have spawned from teleportation by the Enderman (defaults to 0). Chance of spawn from next teleportation is (15 - EndermiteCount)% – i.e., 15% when 0, and 0% when 15.

• Endermite has these additional fields:
  •  Lifetime: How long the Endermite has existed in ticks. Disappears when this reaches around 2400.

• EntityHorse has these additional fields:
  •  Bred: 1 or 0 (true/false) - Unknown. Remains 0 after breeding. Causes horse to become persistent.
  •  ChestedHorse: 1 or 0 (true/false) - true if the horse has chests. As of 13w39b, a chested horse that is not a donkey or a mule will crash the game.
  •  EatingHaystack: 1 or 0 (true/false) - true if the horse is grazing.
  •  HasReproduced: 1 or 0 (true/false) - currently unused. Always 0.
  •  Tame: 1 or 0 (true/false) - true if the horse is tamed. (Non players mobs will not be able to ride a tamed horse if it has no saddle)
  •  Temper: Ranges from 0 to 100; increases with feeding. Higher values make a horse easier to tame.
  •  Type: The type of the horse. 0 = Horse, 1= Donkey, 2= Mule, 3 = Zombie, 4 = Skeleton.
  •  Variant: The variant of the horse. Determines colors. Stored as baseColor | markings << 8.
  •  OwnerName (deprecated): Contains the name of the player that tamed the horse. Has no effect on behaviour.
  •  OwnerUUID: Contains the UUID of the player that tamed the horse. Has no effect on behavior.
  •  Items: List of items. Only exists if ChestedHorse is true.
    • An item, including the Slot tag. Slots are numbered 2 to 16 for donkeys and mules, and none exist for all other horses.
      • See Item Format
  •  ArmorItem: The armor item worn by this horse. May not exist.
    • See Item Format
  •  SaddleItem: The saddle item worn by this horse. May not exist.
    • See Item Format
  •  ArmorType: (removed as of 13w21a) Armor type. 0 = none, 1 = iron, 2= gold, 3= diamond. Other values lead to loading of random textures.
  •  Saddle: (removed as of 13w21a snapshot and added again at 1.6.1 release) 1 or 0 (true/false) - true if there is a saddle on the horse.

• Ghast has these additional fields:
  •  ExplosionPower: The radius of the explosion created by the fireballs this ghast fires. Default value of 1.

• Guardian has these additional fields:
  •  Elder: 1 or 0 (true/false) - true if the Guardian is an Elder Guardian.

• Ozelot has these additional fields:
  •  CatType: The ID of the skin the ocelot has. 0 is wild ocelot, 1 is tuxedo, 2 is tabby and 3 is siamese. Does not determine an ocelot's behavior: it will be wild unless its Owner string is not empty, meaning wild ocelots can look like cats and vice versa.

• Pig has these additional fields:
  •  Saddle: 1 or 0 (true/false) - true if there is a saddle on the pig.

• Rabbit has these additional fields:
  •  RabbitType: Determines the skin of the rabbit. Also determines if rabbit should be hostile. 0=Brown, 1=White, 2=Black, 3=Black & White, 4=Gold, 5=Salt & Pepper, 99=Killer Rabbit of Caerbannog.
  •  MoreCarrotTicks:

• Sheep has these additional fields:
  •  Sheared: 1 or 0 (true/false) - true if the sheep has been shorn.
  •  Color: 0 to 15 - see wool data values for a mapping to colors.

• Skeleton has these additional fields:
  •  SkeletonType: 0 for normal skeleton, 1 for wither skeleton.

• Slime and LavaSlime have these additional fields:
  •  Size: The size of the slime. Note that this value is zero-based, so 0 is the smallest slime, 1 is the next larger, etc. The sizes that spawn naturally are 0, 1, and 3.
  •  wasOnGround: 1 or 0 (true/false) - true if slime is touching the ground.

• WitherBoss has these additional fields:
  •  Invul: The number of ticks of invulnerability left after being initially created. 0 once invulnerability has expired.

• Wolf has these additional fields:
  •  Angry: 1 or 0 (true/false) - true if the wolf is angry.
  •  CollarColor: The dye color of this wolf's collar. Present even for wild wolves (but does not render); default value is 14.

• Villager has these additional fields:
  •  Profession: The ID of the texture used for this villager. This also influences trading options.
  •  Riches: Currently unused. Increases by the number of emeralds traded to a villager any time they are traded.
  •  Career: The ID of this villager's career. This also influences trading options and the villager's name in the GUI (if it does not have a CustomName). If 0, the next time offers are refreshed, the game will assign a new Career and reset CareerLevel to 1.
  •  CareerLevel: The current level of this villager's trading options. Influences the trading options generated by the villager; if it is greater than their career's maximum level, no new offers are generated. Increments when a trade causes offers to be refreshed. If 0, the next trade to do this will assign a new Career and set CareerLevel to 1. Set to a high enough level and there will be no new trades to release (Career must be set to 1 or above).
  •  Willing: 1 or 0 (true/false) - true if the villager is willing to mate. Becomes true after certain trades (those which would cause offers to be refreshed), and false after mating.
  •  Inventory: Each compound tag in this list is an item in the villagers inventory, up to a maximum of 8 slots. Items in two or more slots that can be stacked together will automatically be condensed into one slot. If there are more than 8 slots, the last slot will be removed until the total is 8. If there are 9 slots but two previous slots can be condensed, the last slot will be present after the two other slots are combined.
    • An item in the inventory, excluding the Slot tag.
      • See Item structure.
  •  Offers: Is generated when the trading menu is opened for the first time.
    •  Recipes: List of trade options.
      • A trade option.
        •  rewardExp: 1 or 0 (true/false) - true if this trade will provide XP orb drops.
        •  maxUses: The maximum number of times this trade can be used before it is disabled. Increases by a random amount from 2 to 12 when offers are refreshed.
        •  uses: The number of times this trade has been used. The trade becomes disabled when this is greater or equal to maxUses.
        •  buy: The first 'cost' item, without the Slot tag.
          • See Item structure.
        •  buyB: May not exist. The second 'cost' item, without the Slot tag.
          • See Item structure.
        •  sell: The item being sold for each set of cost items, without the Slot tag.
          • See Item structure.

• VillagerGolem has these additional fields:
  •  PlayerCreated: 1 or 0 (true/false) - true if this golem was created by a player. If true, the golem will never attack the player.

• Zombie has these additional fields:
  •  IsVillager: 1 or 0 (true/false) - true if this zombie is an infected villager. May be absent.
  •  IsBaby: 1 or 0 (true/false) - true if this zombie is a baby. May be absent.
  •  ConversionTime: -1 when not being converted back to a villager, positive for the number of ticks until conversion back into a villager. The regeneration effect will parallel this.
  •  CanBreakDoors: 1 or 0 (true/false) - true if the zombie can break doors (default value is 0). If the difficulty is set to Hard, all zombies will have this tag set to 1. In any other difficulty, it is always set to 0.

• PigZombie has these additional fields:
  • All fields from Zombie
  •  Anger: Ticks until the Zombie Pigman becomes neutral. -32,768 to 0 for neutral Zombie Pigmen; 1 to 32,767 for angry Zombie Pigmen. Value depletes by one every tick if value is greater than 0.

Projectiles

Projectiles are a subclass of Entity and have very obscure tags such as X,Y,Z coordinate tags despite Entity Pos tag, inTile despite inGround, and shake despite most projectiles not being arrows.

Projectile Entities
Entity ID	Name
Arrow	Arrow
Snowball	Snowball
Egg (Removed - bug?)	Egg
Fireball	Ghast Fireball
SmallFireball	Blaze Fireball/Fire Charge
ThrownEnderpearl	Ender Pearl
ThrownExpBottle	Bottle o' Enchanting
ThrownPotion	Splash Potion
WitherSkull	Wither Skull

• Projectiles have these additional fields:
  •  xTile: X coordinate of the item's position in the chunk.
  •  yTile: Y coordinate of the item's position in the chunk.
  •  zTile: Z coordinate of the item's position in the chunk.
  •  inTile: ID of tile projectile is in.

• Projectiles except Fireball, SmallFireball, and WitherSkull have these additional fields:
  •  shake: The "shake" when arrows hit a block.

• Arrow has these additional fields:
  •  inData: Metadata of tile arrow is in.
  •  pickup: 0 = cannot be picked up by players. 1 = can be picked up by players in survival or creative. 2 = can only be picked up by players in creative.
  •  player: 1 or 0 (true/false) - If pickup is not used, and this is true, the arrow can be picked up by players.
  •  life: Increments each tick when an arrow is not moving; resets to 0 if it moves. When it ticks to 1200, the arrow despawns.
  •  damage: Damage dealt by the arrow, in half-hearts. May not be a whole number. 2.0 for normal arrows, and increased 0.5 per level of Power enchantment on the firing bow. If the Power enchantment is present, an additional 0.5 is added on (so Power I gives a bonus of 1.0, while Power II gives 1.5).
  •  inGround: 1 or 0 (true/false) - If the Projectile is in the ground or hit the ground already (For arrow pickup; you cannot pickup arrows in the air)

• Fireball, SmallFireball, and WitherSkull have this additional field:
  •  direction: List of 3 doubles. Should be identical to Motion.

• Fireball has this additional field:
  •  ExplosionPower: The power and size of the explosion created by the fireball upon impact. Default value 1.

• ThrownEnderpearl, ThrownExpBottle, ThrownPotion, and Snowball have this additional field:
  •  ownerName: The name of the player this projectile was thrown by.

• ThrownPotion has these additional fields:
  •  Potion: The item that was thrown, without the slot tag.
    • See Item format and Potion Effects tag tag.
  •  potionValue: If the Potion tag does not exist, this value is used as the damagevalue of the thrown potion.

Items

Items are a subclass of Entity.

Item Entities
Entity ID	Name
Item	Dropped Item
XPOrb	XP Orb

• Items have these additional fields:
  •  Age: The number of ticks the item has been "untouched". After 6000 ticks (5 minutes ) the item is destroyed. If set to -32768, the Age will not decrease, thus the item will not automatically despawn.

• Item has these additional fields:
  •  Health: The health of the item, which starts at 5. Items take damage from fire, lava, falling anvils, and explosions. The item is destroyed when its health reaches 0.
  •  PickupDelay: The number of ticks the item cannot be picked up. Decreases by 1 per tick. If set to 32767, the PickupDelay will not decrease, thus the item can never be picked up.
  •  Owner: If not an empty string, only the named player will be able to pick up this item, until it is within 10 seconds of despawning. Used by the give command (and can be set in a summon command) to prevent the wrong player from picking up the spawned item entity.
  •  Thrower: Set to the name of the player who dropped the item, if dropped by a player. Used by the "Diamonds to you!" achievement.
  •  Item: The inventory item, without the Slot tag.
    • See Item Format.

• XPOrb has these additional fields:
  •  Health: Same properties as Health in Item. However, this value is stored as a byte in saved data, and read as a short but clipped to the range of a byte. As a result, its range is 0-255, always positive, and values exceeding 255 will overflow.
  •  Value: The amount of experience the orb gives when picked up.

Vehicles

Vehicles are subclasses of Entity.

Vehicle Entities
Entity ID	Name
Boat	Boat
Minecart (deprecated)	Minecart Storage Minecart Furnace Minecart
MinecartRideable	Minecart
MinecartChest	Storage Minecart
MinecartFurnace	Furnace Minecart
MinecartSpawner	Spawner Minecart
MinecartTNT	TNT Minecart
MinecartHopper	Minecart with Hopper
MinecartCommandBlock	Minecart with Command Block

• All types of Minecarts may have these additional optional fields:
  •  CustomDisplayTile: Optional. 1 or 0 (true/false) - whether to display the custom tile in this minecart.
  •  DisplayTile: Optional. The ID of the custom block in the minecart.
  •  DisplayData: Optional. The Data value of the custom block in the minecart.
  •  DisplayOffset: Optional. The offset of the block displayed in the Minecart. Positive values move the block upwards, while negative values move it downwards. A value of 16 will move the block up by exactly one multiple of its height.
  •  CustomName: Optional. The custom name of this minecart. ("@" by default for command block minecarts)

• Minecart (deprecated since 13w02a) had these additional fields:
  •  Type: Type of the cart: 0 - empty, 1 - with a chest, 2 - with a furnace.
  • All fields from MinecartRideable, MinecartChest or MinecartFurnace depending on Type.

• MinecartChest and MinecartHopper have these additional fields:
  •  Items: List of items.
    • An item, including the Slot tag. Slots are numbered 0 to 26 for chests, and 0 to 4 for hoppers.
      • See Item Format

• MinecartFurnace have these additional fields:
  •  PushX: Force along X axis, used for smooth acceleration/deceleration.
  •  PushZ: Force along Z axis, used for smooth acceleration/deceleration.
  •  Fuel: The number of ticks until the minecart runs out of fuel.

• MinecartHopper has these additional fields:
  •  TransferCooldown: Time until the next transfer, between 1 and 8, or 0 if there is no transfer.

• MinecartTNT has these additional fields:
  •  TNTFuse: Time until explosion or -1 if deactivated.

• MinecartSpawner has these additional fields:
  • All fields from the MobSpawner Tile Entity, excluding the base Tile Entity fields.

• MinecartCommandBlock has these additional fields:
  •  Command: The command entered into the minecart.
  •  SuccessCount: Represents the strength of the analog signal output by redstone comparators attached to this minecart. Only updated when the minecart is activated with an activator rail.
  •  LastOutput: The last line of output generated by the minecart. Still stored even if the gamerule commandBlockOutput is false. Appears in the GUI of the minecart when right-clicked, and includes a timestamp of when the output was produced.
  •  TrackOutput: 1 or 0 (true/false) - Determines whether or not the LastOutput will be stored. Can be toggled in the GUI by clicking a button near the "Previous Output" textbox. Caption on the button indicates current state: "O" if true,"X" if false.

Dynamic Tiles

Dynamic tiles are a subclass of Entity and are used to simulate realistically moving blocks.

Dynamic Tile Entities
Entity ID	Name
PrimedTnt	TNT
FallingSand	Dynamic Tile

• PrimedTnt has these additional fields:
  •  Fuse: Ticks until explosion. Default is 80 (4 seconds).

• FallingSand has these additional fields:
  •  Tile (deprecated): The Block ID. Not limited to only sand, gravel, dragon eggs, or anvils. Although deprecated, this value is always present.
  •  TileID: The Block ID, as above, but now supporting the 1-4095 range. Only prior to 1.8 and its snapshots.
  •  Block: The Block ID using the alphabetical ID format: minecraft:stone. Only in and after 1.8 and its snapshots.
  •  TileEntityData: Optional. The tags of the tile entity for this block.
  •  Data: The data value for the block.
  •  Time: The number of ticks the entity has existed. If set to 0, the moment it ticks to 1, it will vanish if the block at its location has a different ID than the entity's TileID. If the block at its location has the same ID as its TileID when Time ticks from 0 to 1, the block will instead be deleted, and the entity will continue to fall, having overwritten it. (This was the result of Mojang's failed attempt to "fix" infinite sand/gravel/dragon egg/anvil/etc. generators by trying to have the falling sand entity delete the duplicated block the next tick) When Time goes above 600, or above 100 while the block is below Y=0, the entity is deleted.
  •  DropItem: 1 or 0 (true/false) - true if the block should drop an item that can be picked up when it breaks.
  •  HurtEntities: 1 or 0 (true/false) - true if the block should hurt entities it falls on.
  •  FallHurtMax: The maximum number of hitpoints of damage to inflict on entities that intersect this FallingSand. For vanilla FallingSand, always 40 (20 hearts).
  •  FallHurtAmount: Multiplied by the FallDistance to calculate the amount of damage to inflict. For vanilla FallingSand, always 2.

Other

Other entity types that are a subclass of Entity but do not fit into any of the above categories.

Other Entities
Entity ID	Name
ArmorStand	Armor Stand
EnderCrystal	Ender Crystal
EyeOfEnderSignal	Eye of Ender
FireworksRocketEntity	Firework Rocket
ItemFrame	Item Frame
LeashKnot	Leash Knot
Painting	Painting

• ArmorStand has these additional fields:
  •  DisabledSlots: Bit field allowing disable place/replace/remove of armor elements. Given the armorPos value : 0 for Hand, 1 for Feet, 2 for Legs, 3 for Chest and 4 for Head, flag 1<<armorPos will disable remove of armorPos, 1<<(armorPos+8) will disable replace of armorPos, and 1<<(armorPos+16) will disable place of armorPos. For instance the flag 2096896 will disable every possible interactions with the ArmorStand. Flag 1 is a special case : it will disable removing all part and place/replace of Hand
  •  Equipment: The list of compound tags of the equipment the mob has. Each compound tag in the list is an Item without the slot tag. All 5 entries will always exist (even for players) but may be empty compound tags to indicate no item.
    • 0: The item being held in the entity's hand.
    • 1: Armor (Feet)
    • 2: Armor (Legs)
    • 3: Armor (Chest)
    • 4: Armor (Head)
  •  Invisible: 1 or 0 (true/false) - if true, ArmorStand will be invisible, although items on it will display.
  •  NoBasePlate: 1 or 0 (true/false) - if true, ArmorStand will not display the base beneath it.
  •  NoGravity: 1 or 0 (true/false) - if true, ArmorStand will not fall if in the air.
  •  Pose: Rotation values for the ArmorStand's pose.
    •  Body: Body-specific rotations.
      • : x-rotation.
      • : y-rotation.
      • : z-rotation.
    •  LeftArm: Left Arm-specific rotations.
      • : x-rotation.
      • : y-rotation.
      • : z-rotation.
    •  RightArm: Right Arm-specific rotations.
      • : x-rotation.
      • : y-rotation.
      • : z-rotation.
    •  LeftLeg: Left Leg-specific rotations.
      • : x-rotation.
      • : y-rotation.
      • : z-rotation.
    •  RightLeg: Right Leg-specific rotations.
      • : x-rotation.
      • : y-rotation.
      • : z-rotation.
    •  Head: Head-specific rotations.
      • : x-rotation.
      • : y-rotation.
      • : z-rotation.
  •  ShowArms: 1 or 0 (true/false) - if true, ArmorStand will display full wooden arms.
  •  Small: 1 or 0 (true/false) - if true, ArmorStand will be much smaller. Compare to a Baby Zombie.

• FireworksRocketEntity has these additional fields:
  •  Life: The number of ticks this fireworks rocket has been flying for.
  •  LifeTime: The number of ticks before this fireworks rocket explodes. This value is randomized when the firework is launched: ((Flight + 1) * 10 + random(0 to 5) + random(0 to 6))
  •  FireworksItem: The crafted Firework Rocket item.
    • See Item format and Fireworks tag tag.

• Paintings and Item Frames share these additional fields:
  •  TileX: Prior to 1.8, the X coordinate of the block the painting/item frame is placed on. In 1.8 and later, the X coordinate of the block it's in.
  •  TileY: Prior to 1.8, the Y coordinate of the block the painting/item frame is placed on. In 1.8 and later, the Y coordinate of the block it's in.
  •  TileZ: Prior to 1.8, the Z coordinate of the block the painting/item frame is placed on. In 1.8 and later, the Z coordinate of the block it's in.
  •  Facing: In 1.8 and later, the direction the painting/item frame faces: 0 is south, 1 is west, 2 is north, and 3 is east.
  •  Direction (deprecated in 1.8): Prior to 1.8, the direction the painting/item frame faces: 0 is south, 1 is west, 2 is north, and 3 is east. In 1.8 and later, this tag is removed on loading of the entity.
  •  Dir (deprecated in 1.8): Same as Direction, except the meaning of values 2 and 0 are swapped. Pre-1.8, it is ignored if Direction is present. In 1.8 and later, this tag is removed on loading of the entity.

• ItemFrame has these additional fields:
  •  Item: The item, without the slot tag. If the item frame is empty, this tag does not exist.
    • See Item Structure.
  •  ItemDropChance: The chance the item will drop when the item frame breaks. 1.0 by default.
  •  ItemRotation: The number of times the item has been rotated 45 degrees clockwise.

• Painting has these additional fields:
  •  Motive: The name of this Painting's art.

Tile Entity Format

Tile Entities (not related to Entities) are used by Minecraft to store information about blocks that can't be stored in the 4-bits of block data the block has. They have also recently been referred to as Block Entities, though "Tile Entity" is still a more common name for them.

Tile Entities
Tile Entity ID	Associated Block
Airportal	End Portal
Banner	Banner
Beacon	Beacon Block
Cauldron	Brewing Stand
Chest	Chest Trapped Chest
Comparator	Comparator
Control	Command Block
DLDetector	Daylight Sensor
Dropper	Dropper
EnchantTable	Enchantment Table
EnderChest	Ender Chest
FlowerPot	Flower Pot
Furnace	Furnace
Hopper	Hopper
MobSpawner	Monster Spawner
Music	Note Block
Piston	Piston Moving
RecordPlayer	Jukebox
Sign	Sign
Skull	Head
Trap	Dispenser

All tile entities share this base:

• Tile entity data
  •  id: Tile entity ID
  •  x: X coordinate of the Tile Entity.
  •  y: Y coordinate of the Tile Entity.
  •  z: Z coordinate of the Tile Entity.

• Various containers may have these additional fields:
  •  CustomName: Optional. The name of this container, which will display in its GUI where the default name ordinarily is. For Command Blocks, the name will replace the usual '@' when using commands such as "say" and "tell".

• •  Lock: Optional. When not blank, prevents the container from being opened unless the opener is holding an item whose name matches this string.

• •  CommandStats: Information identifying scoreboard parameters to modify relative to the last command run.
    •  SuccessCountName: Player name to store success of the last command. Can be a player selector but may only have one resulting target.
    •  SuccessCountObjective: Objective's name to store the success of the last command.
    •  AffectedBlocksName: Player name to store how many blocks were modified in the last command. Can be a player selector but may only have one resulting target.
    •  AffectedBlocksObjective: Objective's name to store how many blocks were modified in the last command.
    •  AffectedEntitiesName: Player name to store how many entities were altered in the last command. Can be a player selector but may only have one resulting target.
    •  AffectedEntitiesObjective: Objective's name to store how many entities were altered in the last command.
    •  AffectedItemsName: Player name to store how many items were altered in the last command. Can be a player selector but may only have one resulting target.
    •  AffectedItemsObjective: Objective's name to store how many items were altered in the last command.
    •  QueryResultName: Player name to store the query result of the last command. Can be a player selector but may only have one resulting target.
    •  QueryResultObjective: Objective's name to store the query result of the last command.

• Banner has these additional fields:
  •  Base: Determines background color of the banner.
  •  Patterns: List of all patterns applied to the banner.
    • : An individual pattern.
      •  Color: Color of the section.
      •  Pattern: Section of the banner the color is applied to.

• Beacon has these additional fields:
  •  Levels: The number of levels available from the pyramid.
  •  Primary: The primary power selected, see Potion effects for IDs. 0 means none.
  •  Secondary: The secondary power selected, see Potion effects for IDs. 0 means none.

• Cauldron has these additional fields:
  •  Items: List of items in the brewing stand.
    • : An item, including the slot tag. Slots are numbered 0 to 3.
      • See Item Format.
  •  BrewTime: The number of ticks the potions have been brewing for.

• Chest has these additional fields:
  •  Items: List of items in the chest.
    • : An item, including the slot tag. Chest slots are numbered 0-26 with 0 in the top left corner.
      • See Item Format.

• Comparator has these additional fields:
  •  OutputSignal: Represents the strength of the analog signal output by this redstone comparator. Likely used because the block itself uses its four bits of metadata to determine its rotation, powered state, and subtraction mode state, and comparators can hold a specific amount of power even in circuits without redstone wire.

• Control has these additional fields:
  •  Command: The command to issue to the server.
  •  SuccessCount: Represents the strength of the analog signal output by redstone comparators attached to this command block. Only updated when the command block is activated with a redstone signal.
  •  LastOutput: The last line of output generated by the command block. Still stored even if the gamerule commandBlockOutput is false. Appears in the GUI of the block when right-clicked, and includes a timestamp of when the output was produced.
  •  TrackOutput: 1 or 0 (true/false) - Determines whether or not the LastOutput will be stored. Can be toggled in the GUI by clicking a button near the "Previous Output" textbox. Caption on the button indicates current state: "O" if true,"X" if false.

• FlowerPot has these additional fields:
  •  Item: The Block ID of the plant in the pot. Known valid blocks are minecraft:sapling (6), minecraft:tallgrass (31), minecraft:deadbush (32), minecraft:yellow_flower (37), minecraft:red_flower (38), minecraft:brown_mushroom (39), minecraft:red_mushroom (40), minecraft:cactus (81). Other block and item IDs may be used, but not all will render. Together with Data, this determines the item dropped by the pot when destroyed.
  •  Data: The data value to use in conjunction with the above Block ID. For example if Item is 6 (a sapling block), the Data is used to indicate the type of sapling. See Data Values for details.

• Furnace has these additional fields:
  •  BurnTime: Number of ticks left before the current fuel runs out.
  •  CookTime: Number of ticks the item has been smelting for. The item finishes smelting when this value reaches 200 (10 seconds). Is reset to 0 if BurnTime reaches 0.
  •  CookTimeTotal: Number of ticks It takes for the item to be smelted.
  •  Items: List of items in the furnace slots.
    • : An item in the furnace, including the slot tag:
      Slot 0: The item(s) being smelted.
      Slot 1: The item(s) to use as the next fuel source.
      Slot 2: The item(s) in the result slot.
      • See Item Format.

• Hopper has these additional fields:
  •  Items: List of items in the hopper slots.
    • : An item in the hopper, including the slot tag.
      • See Item Format.
  •  TransferCooldown: Time until the next transfer, naturally between 1 and 8 or 0 if there is no transfer.

• MobSpawner has these additional fields:
  •  SpawnPotentials: Optional. List of possible entities to spawn. If this tag does not exist, but SpawnData exists, Minecraft will generate it the next time the spawner tries to spawn an entity. The generated list will contain a single entry derived from the EntityId and SpawnData tags.
    • : A potential future spawn. After the spawner makes an attempt at spawning, it will choose one of these entries at random and use it to prepare for the next spawn.
      •  Type: Overwrites EntityId when preparing the next spawn.
      •  Weight: The chance that this spawn will be picked as compared to other spawn weights. Must be non-negative and at least 1.
      •  Properties: Overwrites the contents of SpawnData when preparing the next spawn. Not optional; an empty one will be created if it does not exist.
  •  EntityId: The Entity ID of the next entity(s) to spawn. Both Mob Entity IDs and other Entity IDs will work. Warning: If SpawnPotentials exists, this tag will get overwritten after the next spawning attempt: see above for more details.
  •  SpawnData: Contains tags to copy to the next spawned entity(s) after spawning. Any of the Entity or Mob tags may be used. Note that if a spawner specifies any of these tags, almost all variable data such as mob equipment, villager profession, sheep wool color, etc., will no longer be automatically generated, and must also be manually specified (note that this does not apply to position data, which will be randomized as normal unless Pos is specified. Similarly, unless Size and Health are specified for a Slime or Magma Cube, these will still be randomized). This, together with EntityId, also determines the appearance of the miniature entity spinning in the spawner cage. Note: this tag is optional: if it does not exist, the next spawned entity will use the default vanilla spawning properties for this mob, including potentially randomized armor (this is true even if SpawnPotentials does exist). Warning: If SpawnPotentials exists, this tag will get overwritten after the next spawning attempt: see above for more details.
  •  SpawnCount: How many mobs to attempt to spawn each time.
  •  SpawnRange: The radius around which the spawner attempts to place mobs randomly. The spawn area is square, includes the block the spawner is in, and is centered around the spawner's x,z coordinates - not the spawner itself. It is 2 blocks high, centered around the spawner's y coordinate (its bottom), allowing mobs to spawn as high as its top surface and as low as 1 block below its bottom surface. Vertical spawn coordinates are integers, while horizontal coordinates are floating point and weighted towards values near the spawner itself. Default value is 4.
  •  Delay: Ticks until next spawn. If 0, it will spawn immediately when a player enters its range. If set to -1 (this state never occurs in a natural spawner; it seems to be a feature accessed only via NBT editing), the spawner will reset its Delay, and (if SpawnPotentials exist) EntityID and SpawnData as though it had just completed a successful spawn cycle, immediately when a player enters its range. Note that setting Delay to -1 can be useful if you want the game to properly randomize the spawner's Delay, EntityID, and SpawnData, rather than starting with pre-defined values.
  •  MinSpawnDelay: The minimum random delay for the next spawn delay. May be equal to MaxSpawnDelay.
  •  MaxSpawnDelay: The maximum random delay for the next spawn delay. Warning: Setting this value to 0 crashes Minecraft. Set to at least 1.
  •  MaxNearbyEntities: Overrides the maximum number of nearby (within a box of spawnrange*2+1 x spawnrange*2+1 x 8 centered around the spawner block) entities whose IDs match this spawner's entity ID. Note that this is relative to a mob's hitbox, not their physical position. Also note that all entities within all chunk sections (16x16x16 cubes) overlapped by this box are tested for their ID and hitbox overlap, rather than just entities which are within the box, meaning a large amount of entities outside the box (or within it, of course) can cause substantial lag.
  •  RequiredPlayerRange: Overrides the block radius of the sphere of activation by players for this spawner. Note that for every gametick, a spawner will check all players in the current world to test whether a player is within this sphere. Note: Requires the MaxNearbyEntities property to also be set.
  •  MaxExperience (removed): Unknown.
  •  RemainingExperience (removed): Unknown.
  •  ExperienceRegenTick (removed): Unknown.
  •  ExperienceRegenRate (removed): Unknown.
  •  ExperienceRegenAmount (removed): Unknown.

• Music has these additional fields:
  •  note: Pitch (number of right-clicks).

• Piston has these additional fields:
  •  blockId: Block_IDs of the block being moved.
  •  blockData: Data value of the block being moved.
  •  facing: Direction in which the block will be pushed.
  •  progress: How far the block has been moved.
  •  extending: 1 or 0 (true/false) - true if the block is being pushed.

• RecordPlayer has these additional fields:
  •  Record: Record currently playing. 0 is no record. Otherwise, it is the item ID of the record (e.g. 2261 for the "mall" record). Other IDs can be used to make other items or blocks pop out with a data value of 0. This is always overridden by the ID in RecordItem.
  •  RecordItem: The item, without the Slot tag.
    • See Item Format.

• Sign has these additional fields:
  •  Text1: First row of text.
  •  Text2: Second row of text.
  •  Text3: Third row of text.
  •  Text4: Fourth row of text.

Only the first 16 characters of each line are read, the rest are discarded. (As of 1.8 snapshot 14w25a, the character limit depends on the width of the characters.)

• Skull has these additional fields:
  •  SkullType: The type of the skull, similar to the Item IDs. (See Data values#Heads)
  •  ExtraType: Name of the player this is a skull of for pre-1.8.
  •  Rot: The orientation, similar to signs. (See Data values#Sign Posts)
  •  Owner: 1.8's definition for the skull's owner.
    •  Id: UUID of owner.
    •  Name: Username of owner.
    •  Properties
      •  textures
        • : An individual texture.
          •  Signature
          •  Value

• Trap and Dropper have these additional fields:
  •  Items: List of items in the dispenser/dropper
    • : An item, including the slot tag. Slots are numbered 0-8.
      • See Item Format.

Tile Tick Format

Tile Ticks represent block updates that need to happen because they could not happen before the chunk was saved. Examples reasons for tile ticks include redstone circuits needing to continue updating, water and lava that should continue flowing, recently placed sand or gravel that should fall, etc. Tile ticks are not used for purposes such as leaf decay, where the decay information is stored in the leaf block data values and handled by Minecraft when the chunk loads. For map makers, tile ticks can be used to update blocks after a period of time has passed with the chunk loaded into memory.

• A Tile Tick
  •  i: The ID of the block as an integer prior to 1.8 snapshots and a string after 1.8 snapshots; used to activate the correct block update procedure.
  •  t: The number of ticks until processing should occur. May be negative when processing is overdue.
  •  p: If multiple tile ticks are scheduled for the same tick, tile ticks with lower p will be processed first. If they also have the same p, the order is unknown.
  •  x: X position
  •  y: Y position
  •  z: Z position

References