This feature is exclusive to Java Edition.
This article is about the NBT file format. For using NBT in commands, see Tutorials/Command NBT Tags.
The Named Binary Tag format is used by Minecraft for the various files in which it saves data. The format is described by Notch in a very brief specification. The format is designed to store data in a tree structure made up of various tags. All tags have an ID and a name. The original known version was 19132 as introduced in Minecraft Beta 1.3, and since then has been updated to 19133 with Anvil, with the addition of the Int Array tag. The NBT format dates all the way back to Minecraft Indev with tags 0 to 10 in use.
TAG definition
Add more columns [discuss]
This section might benefit of the addition of the "prefix and/or suffix in SNBT" column.
A tag is an individual part of the data tree. The first byte in a tag is the tag type (ID), followed by two bytes for the length of the name, then the name as a string in UTF-8 format (Note TAG_End is not named and does not contain the extra 2 bytes; the name is assumed to be empty). The name of tags may contain spaces, although Minecraft itself never saves tags with spaces in the names. Finally, depending on the type of the tag, the bytes that follow are part of that tag's payload. This table describes each of the 12 known tags in version 19133 of the Named Binary Tag format:
| ID | Icon | Tag Type | Payload | Defined in commands | Description | Storage Capacity |
|---|---|---|---|---|---|---|
| 0 | TAG_End | None. | - | Used to mark the end of compound tags. This tag does not have a name, so it is only ever a single byte 0. It may also be the type of empty List tags. | N/A | |
| 1 | TAG_Byte | 1 byte / 8 bits, signed | <number>b or <number>B
|
A signed integral type. Sometimes used for booleans. | Full range of -(27) to (27 - 1) (-128 to 127) | |
| 2 | TAG_Short | 2 bytes / 16 bits, signed, big endian | <number>s or <number>S
|
A signed integral type. | Full range of -(215) to (215 - 1) (-32,768 to 32,767) | |
| 3 | TAG_Int | 4 bytes / 32 bits, signed, big endian | <number>
|
A signed integral type. | Full range of -(231) to (231 - 1) (-2,147,483,648 to 2,147,483,647) | |
| 4 | TAG_Long | 8 bytes / 64 bits, signed, big endian | <number>l or <number>L
|
A signed integral type. | Full range of -(263) to (263 - 1) (-9,223,372,036,854,775,808 to 9,223,372,036,854,775,807) | |
| 5 | TAG_Float | 4 bytes / 32 bits, signed, big endian, IEEE 754-2008, binary32 | <number>f or <number>F
|
A signed floating point type. | Precision varies throughout number line; See Single-precision floating-point format. Maximum value about 3.4*1038 | |
| 6 | TAG_Double | 8 bytes / 64 bits, signed, big endian, IEEE 754-2008, binary64 | <decimal number>, <number>d or <number>D
|
A signed floating point type. | Precision varies throughout number line; See Double-precision floating-point format. Maximum value about 1.8*10308 | |
| 7 | TAG_Byte_Array | TAG_Int's payload size, then size TAG_Byte's payloads. | [B;<byte>,<byte>,...]
|
An array of bytes. | Maximum number of elements ranges between (231 - 9) and (231 - 1) (2,147,483,639 and 2,147,483,647), depending on the specific JVM. | |
| 8 | TAG_String | TAG_Short's payload length, then a UTF-8 string with size length. | <a-zA-Z0-9 text> or "<text>"
|
A UTF-8 string. It has a size, rather than being null terminated. | 32,767 bytes interpretable as UTF-8 (see UTF-8 format; most commonly-used characters are a single byte). | |
| 9 | TAG_List | TAG_Byte's payload tagId, then TAG_Int's payload size, then size tags' payloads, all of type tagId. | [<value>,<value>,...]
|
A list of tag payloads, without repeated tag IDs or any tag names. | Due to JVM limitations and the implementation of ArrayList, the maximum number of list elements is (231 - 9), or 2,147,483,639. Also note that List and Compound tags may not be nested beyond a depth of 512. | |
| 10 | TAG_Compound | Fully formed tags, followed by a TAG_End. | {<tag name>:<value>,<tag name>:<value>,...}
|
A list of fully formed tags, including their IDs, names, and payloads. No two tags may have the same name. | Unlike lists, there is no hard limit to the amount of tags within a Compound (of course, there is always the implicit limit of virtual memory). Note, however, that Compound and List tags may not be nested beyond a depth of 512. | |
| 11 | TAG_Int_Array | TAG_Int's payload size, then size TAG_Int's payloads. | [I;<integer>,<integer>,...]
|
An array of TAG_Int's payloads. | Maximum number of elements ranges between (231 - 9) and (231 - 1) (2,147,483,639 and 2,147,483,647), depending on the specific JVM. | |
| 12 | TAG_Long_Array | TAG_Int's payload size, then size TAG_Long's payloads. | [L;<long>,<long>,...]
|
An array of TAG_Long's payloads. | Maximum number of elements ranges between (231 - 9) and (231 - 1) (2,147,483,639 and 2,147,483,647), depending on the specific JVM. |
The List and Compound tags can be and often are recursively nested. It should also be noted that, in a list of lists, each of the sub-lists can list a different kind of tag.
File Format
An NBT file is a GZip'd Compound tag, name and tag ID included. Some of the files utilized by Minecraft may be uncompressed, but in most cases the files follow Notch's original specification and are compressed with GZip. In the Xbox 360 Edition, chunks are compressed with XMemCompress, a variation of an LZX compression algorithm. There is no header to specify the version or any other information - only the level.dat file specifies the version.
As used in Minecraft
Minecraft's use of the NBT format is odd at times. In some instances, empty lists may be represented as a list of Byte tags rather than a list of the correct type, or as a list of End tags in newer versions of Minecraft, which can break some older NBT tools. Additionally, almost every root tag has an empty name string and encapsulates only one Compound tag with the actual data and a name. For instance:
- The root tag for most Minecraft NBT structures.
- SomeName: The only tag contained within the root tag - it has a name and contains all the actual data.
Another noticeable oddity is that, although the original specification by Notch allows for spaces in tag names, and even the example uses spaces in the tag names, Minecraft has no known files where any tags have spaces in their names. There is also inconsistent use of letter case, mostly either lowerCamelCase or UpperCamelCase, but sometimes even in all lowercase.
Uses
- level.dat is stored in compressed NBT format.
- <player>.dat files are stored in compressed NBT format.
- idcounts.dat is stored in uncompressed NBT format.
- villages.dat is stored in compressed NBT format.
- map_<#>.dat files are stored in compressed NBT format.
- servers.dat, which is used to store the list of saved multiplayer servers as uncompressed NBT.
- Chunks are stored in compressed NBT format within Region files.
- scoreboard.dat is stored in compressed NBT format.
- Generated structures are stored in compressed NBT format.
- Saved Structures are stored in compressed NBT format.
Software
Mojang has provided sample Java NBT classes for developers to use and reference as part of the source code for the McRegion -> Anvil converter. Other than this, the community has developed programs to view and modify compressed and uncompressed NBT files:
| Name | NBT Version | Description | Screenshot |
|---|---|---|---|
| [1] | 19132 | CL-NBT is an NBT implementation in Common Lisp that can read and write NBT files and load and save McRegion files. Anvil format works with slight modification. | |
| MineBack Ultimate | 19133 | MineBack Ultimate provides a full NBT editor supporting all available types of NBT format file (Map, Level, World etc.). It comes with a modern GUI and many helper functions. | File:MineBackNBTEditor.png |
| NBTEdit | 19132 | Allows for viewing and modifying NBT files via a Windows tree control. It is outdated not only from being an NBT version behind, but because it does not support multiple tags with the same name and it forces incorrect ranges on some types, and it lacks support for uncompressed NBT files. | File:NBTEdit Level.Dat.png |
| NBTExplorer - Forum Post | 19133 | Inspired by and based on NBTEdit, this program allows viewing and editing of NBT files via a Windows tree control. It supports compressed and uncompressed NBT files, and allows for direct editing of the NBT structures in MCRegion and Anvil files, level.dat, etc. | File:NBTExplorer.png |
| NBT grammar for Synalyze It! | 19132 | Using this grammar Synalyze It! displays a color-coded hex dump along with the parsed tag tree. Currently only uncompressed files are supported. | File:Synalyze-It-NBT-decoded.png |
| NEINedit | 19132 | NBT editor for mac with a text-based tree structure. | File:NEINedit.png |
| NBT2YAML | 19133 | nbt2yaml presents a command line interface for reading and editing Minecraft NBT files using a custom YAML format. It also includes a Python API for parsing and writing NBT files to/from a simple Python data structure. | |
| webNBT | 19133 | webNBT is an NBT-editor that runs in modern browsers without requiring the user to download an application or use third-party browser plugins (like Flash or Java). |
History
| Java Edition | |||||
|---|---|---|---|---|---|
1.0.0{{Extension DPL}}<ul><li>[[Cooked Cod|Cooked Cod]]<br/>{{redirect|Cooked Fish|cooked salmon|Cooked Salmon}}
{{Item
| title = Cooked Cod
| image = Cooked Cod.png
| renewable = Yes
| heals = {{hunger|5}}
| stackable = Yes (64)
}}
'''Cooked cod''' is a food item obtained by cooking [[raw cod]].
== Obtaining ==
=== Mob loot ===
====Cod====
[[Cod]] always drops 1 [[Raw Cod|raw cod]] when killed, unaffected by Looting.<ref>{{bug|MC-212795||Salmon & Fish mobs are not affected by Looting}}</ref> If it is killed while on [[fire]], it drops 1 cooked cod instead.
====Dolphins ====
When killed, [[Dolphin|dolphins]] drop 0–1 raw cod. The maximum amount is increased by 1 per level of [[Looting]], for a maximum of 0-4 with Looting III. If killed while on fire, they drop cooked cod instead.
====Guardians and elder guardians====
[[Guardian]]s and [[elder guardian]]s have a 40% and 50% chance, respectively, to drop raw cod when killed. {{IN|java}}, cooked cod is dropped if a guardian is on fire when killed.
Guardians and elder guardians also drop a 2.5% chance to drop a random fish, with 60% of them being raw cod, which drops as cooked if the guardian was on fire. The chance of getting the fish drop is increased by 1% per level with [[Looting]] (for a maximum of 5.5% with Looting III), but the type of fish is not affected.
====Polar bears====
[[Polar bear]]s have a 75% chance of dropping 0–2 raw cod when killed. The maximum amount can be increased by 1 per level of Looting, for a maximum of 0-5 with Looting III. If killed while on fire, they drop cooked cod instead.
===Chest loot===
{{LootChestItem|cooked-cod}}
===Cooking===
Cooked cod can be obtained by cooking [[raw cod]] in a [[furnace]], [[smoker]], or [[campfire]].
{{smelting|Raw Cod|Cooked Cod|0,35}}
===Trading===
Novice-level Fisherman [[Villager|villagers]] have a 50% chance to sell 6 cooked cod for 6 raw cod and 1 [[emerald]].
== Usage ==
=== Food ===
To eat cooked cod, press and hold {{control|use}} while it is selected in the hotbar. Eating one restores {{hunger|5}} [[hunger]] and 6 hunger [[Hunger#Mechanics|saturation]].
=== Wolves ===
{{IN|Bedrock}}, cooked cod can be used to feed a wolf not at full health, healing by {{hp|5|mob=1}}. However, unlike other wolf food, cooked cod cannot be used to speed up the growth of baby wolves nor used to breed them.
==Sounds==
{{Sound table/Entity/Food}}
== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showitemtags=y
|showforms=y
|generatetranslationkeys=y
|displayname=Cooked Cod
|spritetype=item
|nameid=cooked_cod
|itemtags=fishes
|form=item
|foot=1}}
{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|showaliasids=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Cooked Cod
|spritetype=item
|nameid=cooked_cod
|aliasid=cooked_fish
|id=268
|form=item
|translationkey=item.cooked_fish.name
|foot=1}}
== Achievements ==
{{load achievements|Delicious Fish}}
== Advancements ==
{{load advancements|Husbandry;A Balanced Diet}}
== Video ==
<div style="text-align:center">{{yt|nPl0HUGPMcA}}</div>
== History ==
{{History|java alpha}}
{{History||v1.2.0|snap=<nowiki>?|slink=:Category:Information needed requiring unarchived version|[[File:Cooked Cod JE1 BE1.png|32px]] Added cooked fish, which restores {{hp|5}}.}}
{{History|java beta}}
{{History||1.5|Cooking fish now gives the '''Delicious Fish''' [[achievement]].}}
{{History||1.8|snap=Pre-release|Cooked fish is now stackable to 64.
|Cooked fish now fills {{hunger|5}} instead of {{hp|5}}.}}
{{History|java}}
{{History||1.3.1|snap=12w21a|Farmer [[villager]]s now [[trading|buy]] 9–12 cooked fish for 1 [[emerald]].}}
{{History||1.8|snap=14w02a|[[Trading]] has been changed: fisherman [[villager]]s now [[trading|sell]] 6 cooked fish for 1 [[emerald]] plus 6 [[raw cod|raw fish]].
|Farmer villagers no longer buy cooked fish.}}
{{History|||snap=14w04a|The name of cooked fish has been corrected from <code>cooked_fished</code> to <code>cooked_fish</code>.}}
{{History|||snap=14w25a|Cooked fish are now obtainable rare [[drops]] from [[guardian]]s and [[elder guardians]].}}
{{History||1.13|snap=17w47a|The different data values for the <code>cooked_fish</code> IDs have been split up into their own IDs.
|"Cooked Fish" have been renamed to "Cooked Cod".
|Prior to [[1.13/Flattening|''The Flattening'']], these [[item]]s' numeral ID were 349 and 350.}}
{{History|||snap=18w08b|[[Cod]], and other [[fish]], have been added as [[mob]]s, which [[drops|drop]] their cooked [[item]] form when killed with [[fire]].
|[[File:Cooked Cod JE2 BE2.png|32px]] The texture of cooked cod has been changed.}}
{{History|||snap=18w10a|Cooked cod now generates in [[buried treasure]] [[chest]]s.}}
{{History||1.14|snap=18w43a|[[File:Cooked Cod JE3.png|32px]] The texture of cooked cod has been changed.}}
{{History|||snap=18w47b|[[File:Cooked Cod JE4 BE3.png|32px]] The texture of cooked cod has been changed, once again to match {{el|be}}.}}
{{History|pocket alpha}}
{{History||v0.11.0|snap=build 1|[[File:Cooked Cod JE1 BE1.png|32px]] Added cooked fish.}}
{{History||v0.12.1|snap=build 1|Cooked fish now restores [[hunger]] instead of [[health]].}}
{{History||v0.16.0|snap=build 1|Cooked fish is now [[drops|dropped]] by [[guardian]]s and [[elder guardian]]s.}}
{{History|pocket}}
{{History||1.0.4|snap=alpha 1.0.4.0|Fisherman [[villager]]s now [[trading|sell]] 6 cooked fish for 1 [[emerald]] plus 6 [[raw cod|raw fish]].}}
{{History|bedrock}}
{{History||1.4.0|snap=beta 1.2.14.2|[[Cod]] and other [[fish]] have been added as [[mob]]s, which [[drops|drop]] their cooked [[item]] form when killed with [[fire]].
|[[File:Cooked Cod JE2 BE2.png|32px]] The texture of cooked fish has been changed.}}
{{History||1.5.0|snap=beta 1.5.0.4|[[File:Cooked Cod JE4 BE3.png|32px]] The texture of cooked fish has been changed.}}
{{History||1.7.0|snap=beta 1.7.0.2|"Cooked Fish" has been renamed to "Cooked Cod".}}
{{History||1.11.0|snap=beta 1.11.0.4|Fisherman [[villager]]s now have a 50% chance to [[trading|sell]] 6 cooked cod for 6 [[raw cod]] and 1 [[emerald]].}}
{{History||1.16.100|snap=beta 1.16.100.52|Cod now drop their cooked cod when killed with fire.}}
{{History|console}}
{{History||xbox=TU1|xbone=CU1|ps=1.0|wiiu=Patch 1|[[File:Cooked Cod JE1 BE1.png|32px]] Added cooked fish.}}
{{History||xbox=TU5|Cooked fish is now stackable to 64.
|Cooked fish now fills [[hunger]] instead of [[health]].}}
{{History||xbox=TU69|ps=1.76|wiiu=Patch 38|"Cooked Fish" has been renamed to "Cooked Cod".
|[[File:Cooked Cod JE2 BE2.png|32px]] The texture of cooked cod has been changed.}}
{{History|new 3ds}}
{{History||0.1.0|[[File:Cooked Cod JE1 BE1.png|32px]] Added cooked fish.}}
{{History|foot}}
== Issues ==
{{Issue list}}
{{Items}}
[[Category:Food]]
[[Category:Renewable resources]]
[[de:Gebratener Kabeljau]]
[[es:Bacalao cocinado]]
[[ko:익힌 대구]]
[[pt:Bacalhau assado]]
[[ru:Жареная треска]]
[[th:Cod (ไอเทม)]]
[[zh:熟鳕鱼]]</li><li>[[Block Inspector|Block Inspector]]<br/>{{MinecraftEdu feature}}
{{stub}}
{{Item
| image = BlockInspector.png
| stackable = No {{verify}}
}}
'''Block Inspector''' is an item used to display the name of the block the player is looking at on screen.
== Data values ==
{{ID table
|generatetranslationkeys=java
|displayname=Block Inspector
|spritetype=item
|nameid=block_inspector|foot=1}}
==History==
{{History|MinecraftEDU}}
{{History||0.9848|[[File:BlockInspector.png|32px]] Added block inspectors.}}
{{History|foot}}
{{Items}}</li></ul></nowiki> | September 28, 2011 | Notch works on "saving arbitrary data with item instances." | |||
