Gamepedia was upgraded to MediaWiki version 1.31 on Wednesday November 14th. To learn more about the upgrade and its effects click here.

Chunk format

From Minecraft Wiki
Jump to: navigation, search

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.

NBT structure[edit]

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.

    •  DataVersion: Version of the chunk NBT structure.

    •  Level: Chunk data.

      •  xPos: X position of the chunk.

      •  zPos: Z position of the chunk.

      •  LastUpdate: Tick when the chunk was last saved.

      •  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). See Regional Difficulty for more specifics.

      •  Biomes: May not exist. 256 entries of biome data, one for each vertical column in the chunk. See Java Edition data values#Biomes 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 correspond to an unknown biome, Minecraft will also set them to the biome that would normally generate in that location.

      •  Heightmaps:

        •  LIGHT_BLOCKING:

        •  MOTION_BLOCKING:

        •  MOTION_BLOCKING_NO_LEAVES:

        •  OCEAN_FLOOR:

        •  OCEAN_FLOOR_WG:

        •  WORLD_SURFACE:

        •  WORLD_SURFACE_WG:

      •  CarvingMasks:

        •  AIR:

        •  LIQUID:

      •  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.

          •  Palette: Set of different block states used in the chunk.

            • : Block state

              •  Name: Id of the block

              •  Properties: List of block state properties, with [name] being the name of the block state property

                •  Name: The block state name and it's value.

          •  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.

          •  BlockStates: A variable amount of 64-bit longs, enough to fit 4096 indices. The indices correspond to the ordering of elements in the section's Palette. All indices are the same size in a section, which is the size required to represent the largest index (minimum of 4 bits). If the size of each index is not a factor of 64, the bits will continue on the next long.

          •  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 End tags (before 1.10, list of Byte tags).

      •  TileEntities: Each TAG_Compound in this list defines a block entity in the chunk. See Block Entity Format below. If this list is empty it will be a list of End tags (before 1.10, list of Byte tags).

      •  TileTicks: 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 or falling sand, and other activity. See Tile Tick Format below.

      •  LiquidTicks:

      •  Lights: A List of 16 lists.

      •  LiquidsToBeTicked: A List of 16 lists.

      •  ToBeTicked: A List of 16 lists.

      •  PostProcessing: A List of 16 lists.

      •  Status: One of the following: empty, base, carved, liquid_carved, decorated, lighted, mobs_spawned, finalized, fullchunk, or postprocessed.

      •  Structures:

        •  References:

          •  Structure Name:

        •  Starts:

          •  Structure Name: Only the structures that can spawn in this dimension are stored, for example, EndCity is only stored in the end chunks.

            •  ChunkX: Chunk X coordinate of the start of the structure. Absent if id is INVALID.

            •  ChunkZ: Chunk Z coordinate of the start of the structure. Absent if id is INVALID.

            •  id: If there's no structure of this kind in this chunk, this value is "INVALID", else it's the structure name.

            •  biome: The biome id this structure is in. Absent if id is INVALID.

            •  BB: Bounding box of the entire structure. Value is 6 ints: the minimum X, Y, and Z coordinates followed by the maximum X, Y, and Z coordinates. Absent if id is INVALID.

            •  Valid: 1 or 0 (true/false) - (Village only) Whether the village generated at least 3 non-roads. Absent if id is INVALID.

            •  Processed: (Monument only) List of chunks that have had their piece of the structure created. Absent if id is INVALID.


                •  X: Chunk X coordinate

                •  Z: Chunk Z coordinate

            •  Children: List of structure pieces making up this structure. Absent if id is INVALID.

              • : Structure piece data.

                •  id: Identifier for the structure piece. Typically a heavily abbreviated code rather than something human-readable.

                •  Rot: Rotation of ocean ruins and shipwrecks. Valid values are COUNTERCLOCKWISE_90, NONE, CLOCKWISE_90, and CLOCKWISE_180.

                •  BiomeType: The ocean temperature this ocean ruins is in. Valid values are WARM and COLD.

                •  Template: The template of the ocean ruin or shipwreck that was used.

                •  integrity: The integrity of this structure (only used by ocean ruins).

                •  TPX: The X coordinate origin of this ocean ruin or shipwreck.

                •  TPY: The Y coordinate origin of this ocean ruin or shipwreck.

                •  TPZ: The Z coordinate origin of this ocean ruin or shipwreck.

                •  isLarge: 1 or 0 (true/false) - If this ocean ruin is big.

                •  GD: Appears to be some sort of measure of how far this piece is from the start.

                •  O: Likely orientation of the structure piece.

                •  BB: Bounding box of the structure piece. (Does not include the part of a village roof that can overhang the road.) Value is 6 ints: the minimum X, Y, and Z coordinates followed by the maximum X, Y, and Z coordinates.

                •  Width: (Temples and huts) Width of the structure (X/Z).

                •  Height: (Temples and huts) Height of the structure (Y).

                •  Depth: (Temples and huts) Depth of the structure (X/Z).

                •  HPos: (Temples and huts) Y level the structure was moved to in order to place it on the surface, or -1 if it hasn't been moved yet.

                •  placedTrap1: 1 or 0 (true/false) - (Jungle temple) Whether the hallway arrow trap dispenser was placed.

                •  placedTrap2: 1 or 0 (true/false) - (Jungle temple) Whether the chest arrow trap dispenser was placed.

                •  placedMainChest: (1 or 0 (true/false) - Jungle temple) Whether the main chest was placed.

                •  placedHiddenChest: 1 or 0 (true/false) - (Jungle temple) Whether the hidden chest was placed.

                •  hasPlacedChest0: 1 or 0 (true/false) - (Desert temple) Whether chest was placed.

                •  hasPlacedChest1: 1 or 0 (true/false) - (Desert temple) Whether chest was placed.

                •  hasPlacedChest2: 1 or 0 (true/false) - (Desert temple) Whether chest was placed.

                •  hasPlacedChest3: 1 or 0 (true/false) - (Desert temple) Whether chest was placed.

                •  Witch: 1 or 0 (true/false) - (Witch hut) Whether the initial witch has been spawned for the hut.

                •  hr: 1 or 0 (true/false) - (Mineshaft "MSCorridor") Whether the corridor has rails.

                •  sc: 1 or 0 (true/false) - (Mineshaft "MSCorridor") Whether the corridor has cobwebs.

                •  hps: 1 or 0 (true/false) - (Mineshaft "MSCorridor") Whether the corridor has a cave spider spawner.

                •  Num: (Mineshaft "MSCorridor") Corridor length.

                •  tf: 1 or 0 (true/false) - (Mineshaft "MSCrossing") Whether the crossing is two floors tall.

                •  D: (Mineshaft "MSCrossing") Indicates the "incoming" direction for the crossing.

                •  Entrances: (Mineshaft "MSRoom") List of exits from the room.

                  • : Bounding box of the exit.

                •  Chest: 1 or 0 (true/false) - (Fortress "NeSCLT" and "NeSCRT") Whether this fortress piece should contain a chest but hasn't had one generated yet. (Stronghold "SHCC") Whether this chest in this stronghold piece was placed. (Village "ViS") Whether the blacksmith chest has been generated.

                •  Mob: 1 or 0 (true/false) - (Fortress "NeMT") Whether this fortress piece should contain a Blaze spawner but hasn't had one generated yet. (Stronghold "SHPR") Whether the Silverfish spawner has been placed in this piece.

                •  Seed: (Fortress "NeBEF") Random seed for the broken-bridge fortress piece.

                •  EntryDoor: (Stronghold) The type of door at the entry to this piece.

                •  Steps: (Stronghold "SHFC") Length of the corridor

                •  leftLow: 1 or 0 (true/false) - (Stronghold "SH5C") Whether the 5-way crossing has an exit on the lower level on the side with the upward staircase.

                •  rightLow: 1 or 0 (true/false) - (Stronghold "SH5C") Whether the 5-way crossing has an exit on the lower level on the side with the downward staircase.

                •  leftHigh: 1 or 0 (true/false) - (Stronghold "SH5C") Whether the 5-way crossing has an exit on the upper level on the side with the upward staircase.

                •  rightHigh: 1 or 0 (true/false) - (Stronghold "SH5C") Whether the 5-way crossing has an exit on the upper level on the side with the downward staircase.

                •  Tall: 1 or 0 (true/false) - (Stronghold "SHLi") Whether the library has an upper level.

                •  Type: (Stronghold "SHRC") Indicates whether the room contains a pillar with torches, a fountain, an upper level with a chest, or is just empty room.

                •  Source: 1 or 0 (true/false) - (Stronghold "SHSD") Whether the spiral staircase is the source of the Stronghold or was randomly generated.

                •  Left: 1 or 0 (true/false) - (Stronghold "SHS") Whether the corridor has an opening on the left.

                •  Right: 1 or 0 (true/false) - (Stronghold "SHS") Whether the corridor has an opening on the right.

                •  Type: (Village) Village type: 0=plains, 1=desert, 2=savanna, 3=taiga.

                •  Zombie: 1 or 0 (true/false) - (Village) Whether this village generated as a zombie village.

                •  VCount: (Village) Count of villagers spawned along with this piece.

                •  HPos: (Village) Y level the piece was moved to in order to place it on the surface, or -1 if it hasn't been moved yet.

                •  CA: (Village "ViF" and "ViDF") Crop in the farm plot.

                  •  Name: Id of the block

                  •  Properties: List of block state properties, with [name] being the name of the block state property

                    •  Name: The block state name and it's value.

                •  CB: (Village "ViF" and "ViDF") Crop in the farm plot.

                  •  Name: Id of the block

                  •  Properties: List of block state properties, with [name] being the name of the block state property

                    •  Name: The block state name and it's value.

                •  CC: (Village "ViDF") Crop in the farm plot.

                  •  Name: Id of the block

                  •  Properties: List of block state properties, with [name] being the name of the block state property

                    •  Name: The block state name and it's value.

                •  CD: (Village "ViDF") Crop in the farm plot.

                  •  Name: Id of the block

                  •  Properties: List of block state properties, with [name] being the name of the block state property

                    •  Name: The block state name and it's value.

                •  Terrace: 1 or 0 (true/false) - (Village "ViSH") Whether the house has a ladder to the roof and fencing.

                •  T: (Village "ViSmH") Table: 0 is no table, 1 and 2 place it on either side of the hut.

                •  C: (Village "ViSmH") Hut roof type.

                •  Length: (Village "ViSR") Length of the road piece.

Block format[edit]


 This section needs updating. Some of the information no longer applies to the latest version.

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[edit]

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 south 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.

    •  NoGravity: 1 or 0 (true/false) - if true, the entity will not fall if in the air.

    •  Dimension: Only known to be used in <player>.dat to store the players last known location along with Pos. All other 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 nether portal. Initially starts at 300 ticks (15 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.

    •  CustomName: The custom name of this entity (text component [1.13]). 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.

    •  Passengers: The data of the entity riding. Note that both entities control movement and the topmost entity controls spawning conditions when created by a mob spawner.
      • See this format (recursive).

    •  Glowing: 1 or 0 (true/false) - true if the entity has a glowing outline.

    •  Tags: List of custom string data.

Mobs[edit]

Mob Entities
Entity ID Name
bat Bat
blaze Blaze
cave_spider Cave Spider
chicken Chicken
cow Cow
creeper Creeper
dolphin Dolphin
donkey Donkey
drowned Drowned
elder_guardian Elder Guardian
ender_dragon Ender Dragon
enderman Enderman
endermite Endermite
evoker Evoker
ghast Ghast
giant Giant
guardian Guardian
horse Horse
husk Husk
illusioner Illusioner
iron_golem Iron Golem
llama Llama
magma_cube Magma Cube
mooshroom Mooshroom
mule Mule
ocelot Ocelot
parrot Parrot
pig Pig
phantom Phantom
polar_bear Polar Bear
rabbit Rabbit
sheep Sheep
shulker Shulker
silverfish Silverfish
skeleton Skeleton
skeleton_horse Skeleton Horse
slime Slime
snow_golem Snow Golem
spider Spider
squid Squid
stray Stray
turtle Turtle
vex Vex
villager Villager
vindicator Vindicator
witch Witch
wither Wither
wither_skeleton Wither Skeleton
wolf Wolf
zombie Zombie
zombie_horse Zombie Horse
zombie_pigman Zombie Pigman
zombie_villager Zombie Villager

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.

Projectiles[edit]

Projectile Entities
Entity ID Name
arrow Arrow
dragon_fireball Ender Dragon Fireball
egg Egg
ender_pearl Ender Pearl
experience_bottle Bottle o' Enchanting
fireball Ghast Fireball
llama_spit Llama spit
potion Splash Potion
small_fireball Blaze Fireball/Fire Charge
shulker_bullet Shulker Bullet
snowball Snowball
spectral_arrow Spectral Arrow
trident Trident
wither_skull Wither Skull

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. While all projectiles share tags, they are all independently implemented through Throwable and ArrowBase.

Items and XPOrbs[edit]

Item Entities
Entity ID Name
experience_orb Experience Orb
item Dropped Item

Items and XPOrbs are a subclass of Entity.

Vehicles[edit]

Vehicle Entities
Entity ID Name
boat Boat
minecart Minecart
chest_minecart Minecart with Chest
command_block_minecart Minecart with Command Block
furnace_minecart Minecart with Furnace
hopper_minecart Minecart with Hopper
spawner_minecart Minecart with Spawner
tnt_minecart Minecart with TNT

Vehicles are subclasses of Entity.

Dynamic tiles[edit]

Dynamic Block Entities
Entity ID Name
falling_block Dynamic Tile
tnt TNT

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

Other[edit]

Other Entities
Entity ID Name
area_effect_cloud Area Effect Cloud
armor_stand Armor Stand
end_crystal End Crystal
evoker_fangs Evoker Fangs
eye_of_ender Eye of Ender
firework_rocket Firework Rocket
item_frame Item Frame
leash_knot Lead Knot
painting Painting
fishing_bobber Fishing Rod Bobber

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

Block entity format[edit]

Block Entities
Block Entity ID Associated Block
banner Banner
beacon Beacon
bed Bed
brewing_stand Brewing Stand
cauldron (BE) Cauldron
chest Chest
Trapped Chest
comparator Redstone Comparator
command_block Command Block
conduit Conduit
daylight_detector Daylight Detector
dispenser Dispenser
dropper Dropper
enchanting_table Enchanting Table
ender_chest Ender Chest
end_gateway End Gateway (block)
end_portal End Portal (block)
furnace Furnace
hopper Hopper
jukebox Jukebox
mob_spawner Monster Spawner
piston Moving Piston
shulker_box Shulker Box
sign Sign
skull Mob head
structure_block Structure Block

A block entity (not related to entity) is used by Minecraft to store information about a block that can't be stored in the block's block states. Block entities were called "tile entities" until the 1.8 snapshots and that term is still used in some command usage.

Tile tick format[edit]

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; 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

History[edit]

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.

Java Edition
1.3.1 12w21a Removed MaxExperience, RemainingExperience, ExperienceRegenTick, ExperienceRegenRate and ExperienceRegenAmount from MobSpawner.
1.4.2 12w34a Added entity WitherBoss.
1.5 13w02a Added entity MinecartTNT.
Minecart is now deprecated.
13w03a Added entity MinecartHopper.
13w06a Added entity MinecartSpawner.
1.6.1 13w16a Added entity EntityHorse.
13w21a Removed ArmorType from EntityHorse.
Removed Saddle from EntityHorse.
1.6.1-pre Readded Saddle to EntityHorse.
1.7.2 13w39a Added entity MinecartCommandBlock.
1.8 14w02a Added Lock to containers.
Item IDs are no longer used when specifying NBT data.
Added Block to FallingSand, using the alphabetical ID format.
14w06a Added ShowParticles to all mobs.
Added PickupDelay to item entities.
Setting Age to -32768 makes items which never expire.
Removed AttackTime from mobs.
14w10a Added rewardExp to Villager.
Added OwnerUUID for mobs that can breed.
Added Owner to Skull.
Changes to item frames and paintings: added Facing, TileX, TileY and TileZ now represent the co-ordinates of the block the item is in rather than what it is placed on, deprecated Direction and Dir.
14w11a Added entity Endermite.
Added EndermiteCount to Enderman.
14w21a CustomName and CustomNameVisible now work for all entities.
14w25a Added entity Guardian.
Added Text1, Text2, Text3 and Text4 to signs. The limit no longer depends on the amount of characters (16), it now depends on the width of the characters.
14w27a Added entity Rabbit. Added CommandStats to command blocks and signs.
14w28a Removed EndermiteCount from Enderman.
14w30a Added Silent for all entities.
14w32a Added NoAI for all mobs.
Added entity ArmorStand.
14w32c Added NoBasePlate to ArmorStand.
1.9 15w31a Added tags HandItems, ArmorItems, HandDropChances, and ArmorDropChances to Living, which replace the DropChances and Equipment tags.
Added HandItems and ArmorItems to ArmorStand.
Added Glowing to Entity.
Added Team to LivingBase.
Added DragonPhase to EnderDragon
Added entity Shulker, child of Entity.
Added entity ShulkerBullet, child of Entity.
Added entity DragonFireball, which extends FireballBase and has no unique tags.
Added entities TippedArrow and SpectralArrow, children of Arrow.
Added block EndGateway, child of TileEntity.
15w32a Tags and DataVersion tag can now be applied on entities.
Changed the Fuse tag's type for the PrimedTnt entity from "Byte" to "Short".
15w32c Introduced a limit on the amount of tags an entity can have (1024 tags). When surpassed it displays an error saying: "Cannot add more than 1024 tags to an entity."
15w33a Added entity AreaEffectCloud, child of Entity.
Added ExactTeleport and renamed Life to Age for EndGateway.
Added Linger to ThrownPotion.
Removed DataVersion from Entity. It is now only applied to Player only, child of LivingBase.
Removed UUID from Entity.
HealF under LivingBase has become deprecated.
Health under LivingBase has changed from type "Short" to "Float".
Equipment removed from ArmorStand and Living entity, its usage replaced by HandItems and ArmorItems which were added earlier.
15w33c Added BeamTarget to EnderCrystal.
15w34a Added powered and conditional byte tags to Control tile entity for command blocks.
Added life and power to FireballBase.
Added id inside SpawnData to MobSpawner.
Added powered to the Music tile entity for note blocks.
15w35a Added VillagerProfession to Zombie.
15w37a Added Enabled to MinecartHopper.
15w38a Added SkeletonTrap and SkeletonTrapTime to EntityHorse.
15w41a Replaced Riding with Passengers for all entities.
Added RootVehicle for all passengers.
Added Type to Boat.
15w42a Added Fuel to Cauldron (brewing stands).
15w43a Added LootTable and LootTableSeed to Chest, Minecart and MinecartHopper.
Added DeathLootTable and DeathLootTableSeed to all mobs.
Added life and power to all fireballs (FireballBase).
15w44a Added ShowBottom to EnderCrystal.
15w44b Added Potion and CustomPotionEffects to Arrow.
Added Potion to AreaEffectCloud.
15w45a Removed Linger from ThrownPotion. Instead, the potion will linger if the stored item has an ID of minecraft:lingering_potion.
ThrownPotion will now render as its stored item even if the item is not a potion.
15w46a MoreCarrotTicks from Rabbit is now set to 40 when rabbits eat a carrot crop, but is not used anyway.
15w47a Added PaymentItem to Beacon.
15w49a Removed PaymentItem from Beacon.
In order for a sign to accept text, all 4 tags ("Text1", "Text2", "Text3", and "Text4") must exist.
15w51b The original values of DisabledSlots in ArmorStand have changed in nature.
1.10 16w20a Added entity PolarBear.
Added ZombieType to Zombie, replacing VillagerProfession and IsVillager. Value of 6 indicates the "husk" zombie.
A value of 2 on SkeletonType indicates the "stray" skeleton.
NoGravity extended to all entities.
Added powered, showboundingbox and showair to Structure.
16w21a Added FallFlying to mobs and armor stands.
Added integrity and seed to Structure.
1.10-pre1 Added ParticleParam1 and ParticleParam2 to AreaEffectCloud.
1.11 16w32a Horse was split into entity IDs horse, donkey, mule, skeleton_horse and zombie_horse for their respective types. Type and HasReproduced removed from horse, ChestedHorse and Items tags now apply only to mule and donkey, and SkeletonTrap and SkeletonTrapTime tags now apply only to skeleton_horse.
Skeleton was split into entity IDs skeleton, stray and wither_skeleton. SkeletonType tag is removed from all skeleton types.
Zombie was split into entity IDs zombie, zombie_villager and husk. ZombieType tag is removed from all zombie types, ConversionTime and Profession tags now apply only to zombie_villager.
Guardian was split into entity IDs guardian and elder_guardian. Elder tag is removed from guardian.
Unused savegame IDs Mob and Monster were removed.
Pumpkin byte tag is added to snowman.
16w35a Added CustomName to banner.
16w39a Added llama, llama_spit, vindication_illager, vex, evocation_fangs and evocation_illager.
Added Color to shulker.
Added LocName, CustomPotionColor and ColorMap to items.
16w40a Added Johnny to vindication_illager.
Removed xTile, yTile, zTile, inTile, inGround from the FireballBase class (in large fireballs, small fireballs, dragon fireballs, and wither skulls).
16w41a llama_spit is now available as a save game entity.
16w42a Added crit to arrow.
16w43a Added OwnerUUIDLeast and OwnerUUIDMost to evocation_fangs.
16w44a Removed xTile, yTile, zTile, inTile, inGround from the fishing bobber entity.
1.11-pre1 Changed ench to require at least one compound.
1.12 17w13a Added entity Parrot, ShoulderEntityLeft/ShoulderEntityRight, seenCredits, recipeBook and Recipes.
17w14a Added isFilteringCraftable, isGuiOpen and recipes to recipeBook which is now a compound tag.
Added ConversionPlayerLeast and ConversionPlayerMost to entity Zombie.
17w16a Improved NBT parsing in commands.
17w17a Added toBeDisplayed to recipeBook, UpdateLastExecution and LastExecution.
17w17b Added LoveCauseLeast and LoveCauseMost to breedable entities.


Minecraft by Mojang AB, Microsoft Studios, 4J Studios, SkyBox Labs, Other Ocean Interactive and Telltale Games
Help
Game customization
Editions
Java
Bedrock
Previously Separate Titles
Discontinued
Legacy Console
Discontinued
Other
Discontinued
Official Merchandise
Other
Retrieved from "https://minecraft.gamepedia.com/index.php?title=Chunk_format&oldid=1280555"