Как изменить nbt теги игрока

Обновлено: 09.02.2023

The Minecraft Wiki is no longer considered as official by Microsoft and therefore several changes are required to be made, including to the wiki’s logo. Please read this announcement for more information.

Contents

Items [ ]

These can be used in /give and /replaceitem commands as well as /clear . For commands such as /summon and /setblock , place them inside of a tag.

These tags can be used on any item.

Color is a hexadecimal color value, except in decimal. An RGB to hexadecimal converter can be found here and a hexadecimal to decimal converter can be found here. Names and lore must be passed as raw JSON text.

The following syntax can also be used, and eliminates the need for backslashes:

To hide multiple tags, you need to add the value of the tags you want to hide. For example, if you want to hide the «Enchantments» and the «Attributes modifiers» tags, the value you need to put is 3 (1+2).

VALUE ranges from 1 to 127, representing 127 combinations.

Adding 1 hides «Enchantments»

Adding 2 hides «AttributeModifiers»

Adding 4 hides «Unbreakable»

Adding 8 hides «CanDestroy»

Adding 16 hides «CanPlaceOn»

Adding 32 hides other information, including potion effects, shield pattern info, «StoredEnchantments», written book «generation» and «author», «Explosion», «Fireworks», and map tooltips

Adding 64 hides «Dyed» on leather armors

Allowed 1 amount of same NBT Tags.

Unknown amount of allowed same NBT Tags.

The following table describes more details on Enchantments sub-tag.

The following table describes more details on display sub-tag.

The following table describes more details on the Fireworks sub-tag.

Colors is the initial color of the explosion written in decimal format.

FadeColors is the color that the explosion will fade to written in decimal format.

Flicker is whether the whether the explosion flickers while it fades. This is the effect applied when you add glowstone to the firework star.

Trail is whether the particles leave trails as they travel. This effect is applied when you add a diamond to the firework star.

Type is the shape of the firework:

0 is small ball,

1 is large ball,

2 is star-shaped,

3 is creeper-shaped,

Blocks [ ]

These tags are put on blocks as items.

Tutorials/Command NBT tags

Please update this page to reflect recent updates or newly available information.

NBT tags can be specified for items and entities created with the /give and /summon commands. Each tag has the format <tagname>:<value>; where <tagname> describes what it does and <value> is how much it applies. Multiple tags are separated by commas. (e.g.: ],display:<>> ). The contents of List tags are enclosed in square brackets [] , while the contents of Compound tags are enclosed in curly brackets <> – note that the entire data tag is itself a Compound tag (All within a set of <> ). Tag names are case-sensitive, and white space is ignored. additionally, some tags are either true or false (Example: )

The player can quickly find data tags (NBT) without the use of external editors by using /data to figure out the data for each entity or block entity. See more about this in the article Commands/data.

See Entity format for the various NBT Tags that are saved for each entity. This page also contains basic information for each NBT Tag.

When None is used in a tag name that means that this tag can be put directly into the start of the dataTag.

Как изменить тег игрока в Xbox Live с Xbox One

Тег игрока можно изменить не только на сайте, но и в настройках на приставке Xbox One. Все правила те же, что описаны выше для сайт. Изменения проводятся в настройках в пункте «Персонализация» — «Мой профиль» — «Настроить профиль». Нужно нажать на тег игрока и ввести новый ник.

Как изменить тег игрока в Xbox Live

Тег персонализирует игрока, выделяя его среди миллионов других пользователей Xbox Live. Каждый пользователь имеет свой индивидуальный тег игрока, который он задает при создании аккаунта Xbox Live.

В связи с реорганизацией Xbox Live тег игрока снова можно поменять бесплатно

«Консоль Xbox One и мобильное приложение скоро будут обновлены, чтобы в них показывался ваш новый тег игрока, — говорится на сайте. — В играх это произойдёт в какой-то день 2020 года».

Однако стоит учитывать, что после изменения тега, ваш прошлый псевдоним станет доступным другим пользователям.

Как изменить тег игрока в Xbox Live через сайт

Чтобы изменить тег игрока в Xbox Live через сайт, зайдите по этой ссылке и авторизуйтесь:

Появится окно, в нем нужно ввести новый тег игрока. Вводите любое желаемое имя, даже если оно занято, вам об этом сообщат. Жмите «Проверить доступность».

Если желаемый тег занят, появится информация о том, что вашему тегу будет присвоен номер. После этого вы можете или выйти на обратный экран или нажать «Изменить тег игрока», чтобы принять предлагаемый номер и желаемый тег.

Обратите внимание: Изменить предлагаемый номер нельзя.

Blocks [ ]

Note: This is also used for Command Block Minecarts

Generic [ ]

These tags can be used on most tile entitied blocks

Beacon [ ]

Spawner [ ]

These tags are used when using /setblock or /summon (spawner minecarts) to create spawners. Add only those data tags you want to avoid a potential error.

Как изменить тег игрока в майнкрафте

Тег игрока в Xbox можно легко поменять. Если тег игрока был создан во время начальной регистрации в службе Xbox (то есть не выбран вами), то его можно один раз изменить бесплатно. Все последующие изменения тега игрока в Xbox оплачиваются отдельно.

Если при регистрации вы выбрали свой тег игрока и хотите изменить его, с вас будет взята плата (размер платы зависит от валюты и региона).

Примечание. Microsoft может в любое время объявить тег игрока оскорбительным или недопустимым (даже если средство изменения тега игрока позволяет его создание) и изменить этот тег игрока без предупреждения. Подробнее о том, почему мы можем удалить тег игрока, см. в разделе Тег игрока и настоящее имя на веб-сайте безопасности Xbox.

Выполните следующие действия.

Примечание. Интерфейс консоли Xbox One переведен не на все языки.

После подтверждения нового тега игрока изменение вступит в силу в службе Xbox; если потребуется оплата, она будет произведена способом, выбранным в вашей учетной записи Microsoft. Вам не потребуется сообщать друзьям о смене тега игрока — их списки друзей будут обновлены автоматически.

Ниже описано, как это сделать.

1. На консоли Xbox 360 перейдите на страницу Социальные сети и выберите Войти или выйти.
2. Выберите свой профиль, чтобы войти в систему.
3. Прокрутите вправо до пункта Настройки и выберите Профиль.
4. Выберите Изменение профиля.
5. Выберите Тег игрока.
6. Выберите Ввести новый тег игрока.
7. Введите новый тег игрока (не более 15 символов) и выберите Готово.
   Если введенный тег игрока уже существует, вам будет предложено попробовать другой тег игрока.
8. После ввода или выбора нового тега игрока нажмите Да, использовать данный тег игрока.

После подтверждения нового тега игрока изменение вступит в силу в службе Xbox, и, если потребуется внесение дополнительных средств, оплата будет произведена способом, выбранным в учетной записи Microsoft. Вам не потребуется сообщать друзьям о смене тега игрока — их списки друзей будут обновлены автоматически.

Если тег игрока создан во время начальной регистрации (то есть не выбран вами самостоятельно), его можно один раз изменить бесплатно в приложении Компаньон консоли Xbox для Windows 10. Сделать это можно следующим образом.

После подтверждения нового тега игрока изменение вступит в силу в службах Xbox. Вам не потребуется сообщать друзьям о смене тега игрока — их списки друзей будут обновлены автоматически.

Entities [ ]

These tags are used when using the /summon command to spawn entities or when using the /data to edit the data of entities.

This tag determines only the entity’s velocity, not the direction that it’s facing.

The following table provides information on each tagname that can be added in an NBT Tag. These tagnames are specific to the /summon command.

Villager [ ]

These tags are used when summoning villagers. (Offers NBT can’t be done in 1.14+)

Item Frame [ ]

These tags are used when summoning itemframes.

Potion [ ]

These tags are used to customize potions

Armor Stand [ ]

These tags are used when summoning armor stands.

Note: The Equipment tag also works for armor stands.

Turtle [ ]

These tags are used when summoning turtles.

Каким должен быть тег игрока в Xbox Live

В 2019 году Microsoft перезапустила систему тегов. Теперь игроки могут брать такие же теги, как у других пользователей, но им будет присвоен индивидуальный номер. То есть, фактически теперь можно сменить тег игрока в Xbox Live на практически любой, какой игрок пожелает, за исключением нескольких ограничений.

В частности, теперь можно задавать ники не только латиницей, но и кириллицей, а также массой других языков.

Важно: Бесплатно изменить тег игрока в Xbox Live можно только один раз.

Читайте также:

  

• Ghost recon wildlands gold edition что входит

  

• Как сделать рубить деревья в майнкрафте

  

• После установки fnis в скайрим стоят как вкопанные растопырив руки

  

• Wow дикая лоза где взять

  

• Где хранятся сохранения clash of clans

NBT tags can be specified for items and entities created with the /give and /summon commands. Each tag has the format <tagname>:<value> where <tagname> describes what it does, and <value> is what it applies. Multiple tags are separated by commas. (e.g. {CustomName:'"Bob"', Invisible:true). The contents of List tags are enclosed in square brackets [], while the contents of Compound tags are enclosed in curly brackets {} – note that the entire data tag is itself a Compound tag (All within a set of {}). Tag names are case-sensitive, and white space is ignored. Additionally, some tags which are either true or false are stored as Byte tags (Example: {NoAI:1b})

The player can quickly find data tags (NBT) without the use of external editors by using /data to figure out the data for each entity or block entity. See more about this in the article Commands/data.

See Entity format for the various NBT Tags that are saved for each entity. This page also contains basic information for each NBT Tag.

When None is used in a tag name that means that this tag can be put directly into the start of the dataTag.

Items

These can be used in /give and /item commands as well as /clear. For commands such as /summon and /setblock, place them inside of a tag.

Example:

{id:"minecraft:stone",Count:3b, ..., tag:{Name:'{"text":"Name Here"}', ...}}

These tags can be used on any item.

The following table describes more details on Enchantments sub-tag.

Example command: /give @p minecraft:carved_pumpkin{Enchantments:[{id:"minecraft:efficiency",lvl:5s}]} 1

The following table describes more details on display sub-tag.

{
	"text": "Sample name"
}

[
	{
		"text": "First line"
	},
	{
		"text": "Second line"
	}
]

Example command: /[[Commands/'"`uniq--nowiki-0000000f-qinu`"'|'"`uniq--nowiki-0000000f-qinu`"']]

One can further modify the text with things like italics and boldness like so: /[[Commands/'"`uniq--nowiki-00000010-qinu`"'|'"`uniq--nowiki-00000010-qinu`"']]

The following table describes more details on the Fireworks sub-tag.

Blocks

These tags are put on blocks as items.

Entities

These tags are used when using the /summon command to spawn entities or when using the /data to edit the data of entities.

The following table provides information on each tagname that can be added in an NBT Tag. These tagnames are specific to the /summon command.

Villager

These tags are used when summoning villagers. (Offers NBT can’t be done in 1.14+)

Item Frame

These tags are used when summoning itemframes.

Potion

These tags are used to customize potions

Armor Stand

These tags are used when summoning armor stands.

Note: The Equipment tag also works for armor stands.

Turtle

These tags are used when summoning turtles.

Blocks

Tags used in /setblock and /fill:

Note: This is also used for Command Block Minecarts

Generic

These tags can be used on most tile entitied blocks

Beacon

Spawner

These tags are used when using /setblock or /summon (spawner minecarts) to create spawners. Add only those data tags you want to avoid a potential error.

Sub-tags used in the SpawnPotentials data tag.

See also

• Tutorials/Command blocks and functions

References

NBT tags are used to specify information for items and entities created with the «/give«, «/summon«, «/tellraw» (for the JSON message), «/fill«, «/blockdata^{{Until 1.13}}«, «/setblock«, and «/clear» commands.

Each Tag has the format <tagname>:<value>. Tag names are case-sensitive. The payloads of List Tags are enclosed in square brackets [...], with each additional unnamed Tag separated by a comma. The payloads of Compound Tags are enclosed in braces {...}, with each additional Named Tag separated by a comma — Note that the entire entity data tag is itself an unnamed Compound Tag.

You can find a lot of tag names, especially in entities and block entities by using the «/data get entity" or /data get block command.

How To Get Them?

To get the NBT tag of a specific entity (for example, creeper), you use the command /data get entity @e[type=creeper,limit=1] to get the full data of the creeper itself. For more specific selectors, see Commands

Tag Basics

Structure of a Tag

First off, each tag has three parts:

tagType (byte, 0-12)

name (TAG_String)

[its payload]

When using commands, the tagType is figured out based on the given name, and the payload is what follows the colon — basically its value. The payload ought to fit the expected syntax. So a tag expecting an integer will not accept a string.

Number types can be denoted with a letter at the end of the value (such as 0b for a byte). Without a letter, the code assumes an integer, which works fine for most numbers but behaves differently. Using a literal integer like this to exceed a type’s expected range simply wraps the number back to 0 at the limit.

Tag Types

00 TAG_End

Unnamed, no payload, unusable in commands. Used in data storage to mark the end of TAG_Compound.

01 TAG_Byte

Payload: A single signed byte (8 bits)

Ranges from -128 to 127. Used for many booleans.

In Commands: ...b or ...B

02 TAG_Short

Payload: A single signed short integer (2 bytes, big endian)

Ranges from -215 to 215-1

In Commands: ...s or ...S

03 TAG_Int

Payload: A single signed integer (4 bytes, big endian)

Ranges from -231 to 231-1

In Commands: A literal number without a decimal

04 TAG_Long

Payload: A single signed long integer (8 bytes, big endian)

Ranges from -263 to 263-1

In Commands: ...l or ...L

05 TAG_Float

Payload: A floating-point number (4 bytes, big endian, IEEE 754-2008, single precision)

Maxes around 1038.23, or 1.698x1038

In Commands: ...f or ...F, decimal or no decimal

06 TAG_Double

Payload: A floating-point number (8 bytes, big endian, IEEE 754-2008, double precision)

Maxes around 10307.95, or 8.913x10307

In Commands: ...d, ...D, or a decimal number

07 TAG_Byte_Array

Payload: Unnamed TAG_Int (length), then an array of bytes of unspecified format. The length of this array is <length> bytes.

In Commands: [B; <byte>, <byte>, ... ]

(<length> is determined by the length of the given array)

08 TAG_String

Payload: Unnamed TAG_Short (length), then an array of bytes of length <length>. defining a string in UTF-8 format.

In Commands: "<text>"

(<length> is determined by the length of the given text)

Note that as is usual with most strings, if quotes are to be included within the string, escape codes (") must be used for the inner quotes in commands.

09 TAG_List

Payload: Unnamed TAG_Byte (tagId), unnamed TAG_Int (length), then a sequential list of unnamed Tags of type <tagId>. The length of this array is <length> Tags.

In Commands: [<value>, <value>, ...]

(<length> is determined by the length of the given list)

10 TAG_Compound

Payload: A sequential list of unique Named Tags. This array is terminated by a TAG_End.

Nested Compound Tags are terminated by their own internal End Tags.

In Commands: {<tag name>: <value>, <tag name>: <value>, ... }

(The terminating TAG_End is irrelevant to command usage)

11 TAG_Int_Array

Payload: Unnamed TAG_Int (size), then an array of unnamed TAG_Ints. The length of this array is <size> Tags.

An array of integers.

In Commands: [I; <integer>, <integer>, ... ]

(<size> is determined by the size of the given array)

12 TAG_Long_Array

Payload: Unnamed TAG_Int (size), then an array of unnamed TAG_Longs. The length of this array is <size> Tags.

In Commands: Used as [L; <long>, <long>, ... ]

(<size> is determined by the size of the given array)

Tag Payloads

The payload is the data a Tag carries. It might be a number or, in the case of Compound Tags and List Tags, other Tags. In using commands, one simply needs to avoid mismatching expected data types, keep values within expected ranges, and close all brackets [...] and braces {...} that are opened.

For a deeper understanding of payloads, it might help to look at what an example Compound Tag would look like in data.

ON DISK: 00001010 00000000 00000011 01101000 01100001 01101101 00001000 00000000 00000111 01110000 01101001 01100111 01001110 01100001 01101101 01100101 00000000 00000110 01001000 01100001 01101101 01110000 01110101 01110011 00000011 00000000 00000101 01110110 01100001 01101100 01110101 01100101 00000000 00000000 00000000 01111000 00000000
    DEC: 10       0        3        h        a        m        8        0        7        p        i        g        N        a        m        e        0        6        H        a        m        p        u        s        3        0        5        v        a        l        u        e        0        0        0        120      0

       __ ___ _____ _ ___ _____________ ___ ___________ _ ___ _________ _________ _
BYTES: 10 0 3 h a m 8 0 7 p i g N a m e 0 6 H a m p u s 3 0 5 v a l u e 0 0 0 120 0
                   |8: TAG_String      |  payload      |3: TAG_Int     | payload | TAG_End |
    10:TAG_Compound|                                payload                                |

This is understood in the following way. Recall that all named tags have a tagId (1 byte), a name (Unnamed TAG_String), and a payload.

• The first byte of data read is the tagId. Above is 10, so this represents a TAG_Compound. The next two bytes read are the length of its name. (Two bytes because it expects a short — see Structure of a Tag above.) The given length is 3. Those next 3 bytes read ham. So far it’s been revealed that the first Tag is a Compound Tag named «ham». Its payload is everything that follows, until TAG_End.
  • The next byte is 8, so this is a TAG_String. The upcoming unnamed TAG_String tells us it has the 7-byte name of «pigName». Its payload follows.
    • The next short is 6, so the «pigName» has a value that’s 6 bytes long. Those bytes read Hampus. The completed first Tag is TAG_String("name"):6 Hampus
  • The next byte is 3, so next is a TAG_Int. It has the 5-byte name of «value». Its payload follows in the next 4 bytes: 120. The next completed Tag is TAG_Int("value"): 120
  • The next byte is 0, so next is a TAG_End.

The completed Compound Tag is as follows:

TAG_Compound("ham"):
   TAG_String("pigname"): 6 Hampus,
   TAG_Int("value"): 120,
   TAG_End

Using a command to summon a pig with this example tag would look like this:

/summon minecraft:pig ~ ~ ~ {ham:{pigname:"Hampus",value:120}}

List of Entity Data Tags

Minecraft code spawns entities with set Tags and values. Entities are themselves saved as tags within the world’s chunk data. Every detail about an entity is stored in its data tag. All tags are referenced by the game’s code to control entity behaviour.

The following tags are common to all entities.

id: <TAG_String>

Entity ID.

pos: <TAG_List>

[<TAG_Double>, <TAG_Double>, <TAG_Double>]

Three doubles describe current X, Y, Z position of entity

Motion: <TAG_List>

[<TAG_Double>, <TAG_Double>, <TAG_Double>]

Three doubles describe the current dX, dY, dZ velocities of entity (in metres per tick)

Rotation: <TAG_List>

[<TAG_Float>, <TAG_Float>]

Two floats describe entity’s rotation in degrees

• First float is clockwise rotation around the Y axis, with 0° facing in the positive Z direction, or due south. Ranges from 0.0 to 360.0
• Second float is declination from the horizon. Ranges from -90.0 (upwards) to +90.0 (downwards)

FallDistance: <TAG_Float>

Distance entity has fallen. Fall damage taken scales with this number. 0 for any entity at rest

Fire: <TAG_Short>

Ticks until a burning entity’s fire ends. Negative values are how many ticks an entity can stand in fire before burning. -20 for an entity not on fire

Air

Ticks until an entity runs out of air while underwater. While this value is 0 and the entity is underwater, it takes damage. Fills to 300 for any entity above water

OnGround: <TAG_Byte>

0 for false, 1 for true. True when the entity is touching the ground

NoGravity: <TAG_Byte>

0 for false, 1 for true. If true, entity is unaffected by gravity and stops changing Y position

Dimension: <TAG_Int>

0 for the Overworld, -1 for the Nether, and 1 for the End. Only known to be used for player data

Invulnerable: <TAG_Byte>

0 for false, 1 for true. When true, mobs don’t take damage from any source and cannot be moved by force. Objects like item frames cannot be destroyed unless a supporting block is removed

PortalCooldown: <TAG_Int>

Number of ticks until the entity may teleport through a nether portal. Starts at 300 ticks

UUIDMost: <TAG_Long>

The most significant 64 bits of this entity’s Universally Unique Identifier (UUID).

UUIDLeast: <TAG_Long>

The least significant 64 bits of this entity’s Universally Unique Identifier (UUID).

CustomName: <TAG_String>

The entity’s custom name string.

In Minecraft Java Edition 1.14, <TAG_String> must itself have quotes, as well as the standard quotes that go around strings. This means that escape codes are needed for the inner ones, so syntax looks like the following, (if one is to name an entity Gerald).

CustomName: ""Gerald""

Another way that this works is by setting it to an apparent compound tag specifying a block of text, done this way:

CustomName: "{"text":"Gerald"}"

CustomNameVisible: <TAG_Byte>

0 for false, 1 for true. If true, this entity’s custom name always appears above its head, whether or not the player is looking at it.

Silent: <TAG_Byte>

0 for false, 1 for true. If true, this entity is silent.

Passengers: <TAG_String>

Data for the entity riding this entity.

Glowing: <TAG_Byte>

-0 for false, 1 for true. When true, the entity has a cartoonish, glowing outline.

Tags: <TAG_String>

List of custom data.

Mobs

The following tags are common to all mobs

Health: <TAG_Float>

Amount of health an entity has.

AbsorptionAmount: <TAG_Float>

Amount of additional, temporary health added by the Absorption status effect.

HurtTime: <TAG_Short>

Set to 10 when a mob is struck, colouring it red. Decreases by 1 per tick until 0, when the mob turns normal colour again.

HurtByTimestamp: <TAG_Long>

Timestamp in the mob’s life when it was last damaged, measured in ticks since its creation.

DeathTime: <TAG_Short>

Number of ticks since the mob’s death. 0 for any living mob.

FallFlying: <TAG_Byte>

0 for false, 1 for true. When true and the mob is wearing the elytra, they’ll glide.

Attributes: <TAG_List>

[<TAG_Compound>, <TAG_Compound>, ... ]

List of Attributes for a mob.

Attribute Tags

Name: <TAG_String>

Given name for the Attribute. Might be generic.maxHealth or horse.jumpStrength.

Base: <TAG_Double>

—

Modifiers: <TAG_List>

List of modifiers acting on the Attribute.

Modifier Tags

Name: <TAG_String>

—

Amount: <TAG_Double>

—

Operation: <TAG_Int>

—

UUIDMost: <TAG_Long>

—

UUIDLeast: <TAG_Long>

—

ActiveEffects: <TAG_List>

[<TAG_Compound>, <TAG_Compound>, ... ]

List of potion effects.

Effect Tags

Id: <TAG_Byte>

—

Amplifier: <TAG_Byte>

—

Duration: <TAG_Int>

—

Ambient: <TAG_Byte>

—

ShowParticles: <TAG_Byte>

—

ShowIcon: <TAG_Byte>

—

HandItems: <TAG_List>

[<TAG_Compound>, <TAG_Compound>]

Describes items the entity is holding. These Compound Tags have Tags Common to All Items. Slot is discluded.

<TAG_Compound 0>: The item held in the mob’s main hand.

<TAG_Compound 1>: The item held in the mob’s off-hand.

ArmorItems: <TAG_List>

[<TAG_Compound>, <TAG_Compound>, ... ]

What the entity is wearing. These Compound Tags have Tags Common to All Items. Slot is discluded.

<TAG_Compound 0>: The item worn on the feet.

<TAG_Compound 1>: The item worn on the legs.

<TAG_Compound 2>: The item worn on the chest.

<TAG_Compound 3>: The item worn on the head.

HandDropChances: <TAG_List>

—

ArmorDropChances: <TAG_List>

—

DeathLootTable: <TAG_String>

—

DeathLootTableSeed: <TAG_Long>

—

CanPickUpLoot: <TAG_Byte>

—

NoAI: <TAG_Byte>

—

PersistenceRequired: <TAG_Byte>

—

LeftHanded: <TAG_Byte>

—

Team: <TAG_String>

—

Leashed: <TAG_Byte>

—

Leash: <TAG_Compound>

—

Mobs That Breed

Mobs that can breed include Cows, Chickens, Pigs, Sheep, Villagers, Cats, and Dogs.

InLove: <TAG_Int>

Counts down number of ticks until this mob stops searching for a mate. Default 0 for a mob not doing so.

Age: <TAG_Int>

Age of the mob in ticks. When less than 0 and counting up, represents a baby mob. Adult mobs use this value to count down how many ticks until it can breed again.

ForcedAge: <TAG_Int>

LoveCauseLeast: <TAG_Long>

Least significant bits of the UUID for the entity that caused this animal to breed

LoveCauseMost: <TAG_Long>

Most significant bits of the UUID for the entity that caused this animal to breed

Mobs That Raid

Coming Soon

Specific Mobs

The following lists are specific to each mob

CustomName: ""Gerald""

CustomName: "{"text":"Gerald"}"

CustomName: ""Gerald""

CustomName: "{"text":"Gerald"}"

Other

To Be Removed

The rest of this page is likely to be removed.

Blocks («/setblock» or «/fill«)

Containers

Items: []The ID and other info of an item.

|_ id: {}The ID of the item.

|_ Slot: {}The slot number. Note that this starts at 0, not 1.

|_ tag: {}Other info of the item.

Items (/give)

All Items

Enchantments: Enchantments on the item.

|_ An enchantement. (List)

       |_ id: The name of the enchantment. Cannot be a number.

       |_ lvl: The level of the enchant. Range is -32768 to 32767.

display: Display properties.

|_ Name: The Custom Name of the item. Range of characters that can be used seems to be infinite.

       |_ Name: ["{"text":"enter custom name here"}"]

|_ color: The Custom Color of Leather Armor.

|_ Lore: The description of an item. Separate lines of text with a comma after the bracket, prior to the last quotation mark

       |_ Lore: ["{"text":"a line of text"}"]

Potions

CustomPotionEffects: Custom effects that a potion will have.

|_ A potion effect.

       |_ Id: The ID of the effect.

       |_ Duration: The duration of the potion effect.

       |_ Amplifier: The potency (+1) of the effect. Kept at 0 to keep a level 1 effect.

       |_ Ambient: (0/1) 0 is false, 1 is true. True if the effect is provided
by a beacon and thus should be less intrusive on screen.

Written Book

author: The author of the book.

title: The title of the book.

pages: The pages in the book.

|_ A page. Separate pages with a comma.

Tools

Unbreakable: (0b/1b) 0b is false, 1b is true. If value is 1b, the tool will never lose durability.

CanDestroy: What blocks this tool can destroy when in adventure mode.

        |_ A block ID.

CanPlaceOn: What blocks can be placed on in adventure mode.

        |_ A block ID.

Title and Tellraw

/title: /title (PlayerName) [(sub)title] {text:»PutTextHere»,color:»PutColorHere»},(Optional){text:»MoreTextHere»,color»PutColorHere»} (Add [] to enclose if doing multiple text tags)

/tellraw: /tellraw (PlayerName) {text:»PutTextHere»,color:»PutColorHere»},(Optional){text:»PutTextHere»,color:»PutColorHere»} (Add [] to enclose if doing multiple text tags)

NBT tags are used to specify information for items and entities created with the «/give«, «/summon«, «/tellraw» (for the JSON message), «/fill«, «/blockdata^{{Until 1.13}}«, «/setblock«, and «/clear» commands.

Each Tag has the format <tagname>:<value>. Tag names are case-sensitive. The payloads of List Tags are enclosed in square brackets [...], with each additional unnamed Tag separated by a comma. The payloads of Compound Tags are enclosed in braces {...}, with each additional Named Tag separated by a comma — Note that the entire entity data tag is itself an unnamed Compound Tag.

You can find a lot of tag names, especially in entities and block entities by using the «/data get entity" or /data get block command.

How To Get Them?

To get the NBT tag of a specific entity (for example, creeper), you use the command /data get entity @e[type=creeper,limit=1] to get the full data of the creeper itself. For more specific selectors, see Commands

Tag Basics

Structure of a Tag

First off, each tag has three parts:

tagType (byte, 0-12)

name (TAG_String)

[its payload]

When using commands, the tagType is figured out based on the given name, and the payload is what follows the colon — basically its value. The payload ought to fit the expected syntax. So a tag expecting an integer will not accept a string.

Number types can be denoted with a letter at the end of the value (such as 0b for a byte). Without a letter, the code assumes an integer, which works fine for most numbers but behaves differently. Using a literal integer like this to exceed a type’s expected range simply wraps the number back to 0 at the limit.

Tag Types

00 TAG_End

Unnamed, no payload, unusable in commands. Used in data storage to mark the end of TAG_Compound.

01 TAG_Byte

Payload: A single signed byte (8 bits)

Ranges from -128 to 127. Used for many booleans.

In Commands: ...b or ...B

02 TAG_Short

Payload: A single signed short integer (2 bytes, big endian)

Ranges from -215 to 215-1

In Commands: ...s or ...S

03 TAG_Int

Payload: A single signed integer (4 bytes, big endian)

Ranges from -231 to 231-1

In Commands: A literal number without a decimal

04 TAG_Long

Payload: A single signed long integer (8 bytes, big endian)

Ranges from -263 to 263-1

In Commands: ...l or ...L

05 TAG_Float

Payload: A floating-point number (4 bytes, big endian, IEEE 754-2008, single precision)

Maxes around 1038.23, or 1.698x1038

In Commands: ...f or ...F, decimal or no decimal

06 TAG_Double

Payload: A floating-point number (8 bytes, big endian, IEEE 754-2008, double precision)

Maxes around 10307.95, or 8.913x10307

In Commands: ...d, ...D, or a decimal number

07 TAG_Byte_Array

Payload: Unnamed TAG_Int (length), then an array of bytes of unspecified format. The length of this array is <length> bytes.

In Commands: [B; <byte>, <byte>, ... ]

(<length> is determined by the length of the given array)

08 TAG_String

Payload: Unnamed TAG_Short (length), then an array of bytes of length <length>. defining a string in UTF-8 format.

In Commands: "<text>"

(<length> is determined by the length of the given text)

Note that as is usual with most strings, if quotes are to be included within the string, escape codes (") must be used for the inner quotes in commands.

09 TAG_List

Payload: Unnamed TAG_Byte (tagId), unnamed TAG_Int (length), then a sequential list of unnamed Tags of type <tagId>. The length of this array is <length> Tags.

In Commands: [<value>, <value>, ...]

(<length> is determined by the length of the given list)

10 TAG_Compound

Payload: A sequential list of unique Named Tags. This array is terminated by a TAG_End.

Nested Compound Tags are terminated by their own internal End Tags.

In Commands: {<tag name>: <value>, <tag name>: <value>, ... }

(The terminating TAG_End is irrelevant to command usage)

11 TAG_Int_Array

Payload: Unnamed TAG_Int (size), then an array of unnamed TAG_Ints. The length of this array is <size> Tags.

An array of integers.

In Commands: [I; <integer>, <integer>, ... ]

(<size> is determined by the size of the given array)

12 TAG_Long_Array

Payload: Unnamed TAG_Int (size), then an array of unnamed TAG_Longs. The length of this array is <size> Tags.

In Commands: Used as [L; <long>, <long>, ... ]

(<size> is determined by the size of the given array)

Tag Payloads

The payload is the data a Tag carries. It might be a number or, in the case of Compound Tags and List Tags, other Tags. In using commands, one simply needs to avoid mismatching expected data types, keep values within expected ranges, and close all brackets [...] and braces {...} that are opened.

For a deeper understanding of payloads, it might help to look at what an example Compound Tag would look like in data.

ON DISK: 00001010 00000000 00000011 01101000 01100001 01101101 00001000 00000000 00000111 01110000 01101001 01100111 01001110 01100001 01101101 01100101 00000000 00000110 01001000 01100001 01101101 01110000 01110101 01110011 00000011 00000000 00000101 01110110 01100001 01101100 01110101 01100101 00000000 00000000 00000000 01111000 00000000
    DEC: 10       0        3        h        a        m        8        0        7        p        i        g        N        a        m        e        0        6        H        a        m        p        u        s        3        0        5        v        a        l        u        e        0        0        0        120      0

       __ ___ _____ _ ___ _____________ ___ ___________ _ ___ _________ _________ _
BYTES: 10 0 3 h a m 8 0 7 p i g N a m e 0 6 H a m p u s 3 0 5 v a l u e 0 0 0 120 0
                   |8: TAG_String      |  payload      |3: TAG_Int     | payload | TAG_End |
    10:TAG_Compound|                                payload                                |

This is understood in the following way. Recall that all named tags have a tagId (1 byte), a name (Unnamed TAG_String), and a payload.

• The first byte of data read is the tagId. Above is 10, so this represents a TAG_Compound. The next two bytes read are the length of its name. (Two bytes because it expects a short — see Structure of a Tag above.) The given length is 3. Those next 3 bytes read ham. So far it’s been revealed that the first Tag is a Compound Tag named «ham». Its payload is everything that follows, until TAG_End.
  • The next byte is 8, so this is a TAG_String. The upcoming unnamed TAG_String tells us it has the 7-byte name of «pigName». Its payload follows.
    • The next short is 6, so the «pigName» has a value that’s 6 bytes long. Those bytes read Hampus. The completed first Tag is TAG_String("name"):6 Hampus
  • The next byte is 3, so next is a TAG_Int. It has the 5-byte name of «value». Its payload follows in the next 4 bytes: 120. The next completed Tag is TAG_Int("value"): 120
  • The next byte is 0, so next is a TAG_End.

The completed Compound Tag is as follows:

TAG_Compound("ham"):
   TAG_String("pigname"): 6 Hampus,
   TAG_Int("value"): 120,
   TAG_End

Using a command to summon a pig with this example tag would look like this:

/summon minecraft:pig ~ ~ ~ {ham:{pigname:"Hampus",value:120}}

List of Entity Data Tags

Minecraft code spawns entities with set Tags and values. Entities are themselves saved as tags within the world’s chunk data. Every detail about an entity is stored in its data tag. All tags are referenced by the game’s code to control entity behaviour.

The following tags are common to all entities.

id: <TAG_String>

Entity ID.

pos: <TAG_List>

[<TAG_Double>, <TAG_Double>, <TAG_Double>]

Three doubles describe current X, Y, Z position of entity

Motion: <TAG_List>

[<TAG_Double>, <TAG_Double>, <TAG_Double>]

Three doubles describe the current dX, dY, dZ velocities of entity (in metres per tick)

Rotation: <TAG_List>

[<TAG_Float>, <TAG_Float>]

Two floats describe entity’s rotation in degrees

• First float is clockwise rotation around the Y axis, with 0° facing in the positive Z direction, or due south. Ranges from 0.0 to 360.0
• Second float is declination from the horizon. Ranges from -90.0 (upwards) to +90.0 (downwards)

FallDistance: <TAG_Float>

Distance entity has fallen. Fall damage taken scales with this number. 0 for any entity at rest

Fire: <TAG_Short>

Ticks until a burning entity’s fire ends. Negative values are how many ticks an entity can stand in fire before burning. -20 for an entity not on fire

Air

Ticks until an entity runs out of air while underwater. While this value is 0 and the entity is underwater, it takes damage. Fills to 300 for any entity above water

OnGround: <TAG_Byte>

0 for false, 1 for true. True when the entity is touching the ground

NoGravity: <TAG_Byte>

0 for false, 1 for true. If true, entity is unaffected by gravity and stops changing Y position

Dimension: <TAG_Int>

0 for the Overworld, -1 for the Nether, and 1 for the End. Only known to be used for player data

Invulnerable: <TAG_Byte>

0 for false, 1 for true. When true, mobs don’t take damage from any source and cannot be moved by force. Objects like item frames cannot be destroyed unless a supporting block is removed

PortalCooldown: <TAG_Int>

Number of ticks until the entity may teleport through a nether portal. Starts at 300 ticks

UUIDMost: <TAG_Long>

The most significant 64 bits of this entity’s Universally Unique Identifier (UUID).

UUIDLeast: <TAG_Long>

The least significant 64 bits of this entity’s Universally Unique Identifier (UUID).

CustomName: <TAG_String>

The entity’s custom name string.

In Minecraft Java Edition 1.14, <TAG_String> must itself have quotes, as well as the standard quotes that go around strings. This means that escape codes are needed for the inner ones, so syntax looks like the following, (if one is to name an entity Gerald).

CustomName: ""Gerald""

Another way that this works is by setting it to an apparent compound tag specifying a block of text, done this way:

CustomName: "{"text":"Gerald"}"

CustomNameVisible: <TAG_Byte>

0 for false, 1 for true. If true, this entity’s custom name always appears above its head, whether or not the player is looking at it.

Silent: <TAG_Byte>

0 for false, 1 for true. If true, this entity is silent.

Passengers: <TAG_String>

Data for the entity riding this entity.

Glowing: <TAG_Byte>

-0 for false, 1 for true. When true, the entity has a cartoonish, glowing outline.

Tags: <TAG_String>

List of custom data.

Mobs

The following tags are common to all mobs

Health: <TAG_Float>

Amount of health an entity has.

AbsorptionAmount: <TAG_Float>

Amount of additional, temporary health added by the Absorption status effect.

HurtTime: <TAG_Short>

Set to 10 when a mob is struck, colouring it red. Decreases by 1 per tick until 0, when the mob turns normal colour again.

HurtByTimestamp: <TAG_Long>

Timestamp in the mob’s life when it was last damaged, measured in ticks since its creation.

DeathTime: <TAG_Short>

Number of ticks since the mob’s death. 0 for any living mob.

FallFlying: <TAG_Byte>

0 for false, 1 for true. When true and the mob is wearing the elytra, they’ll glide.

Attributes: <TAG_List>

[<TAG_Compound>, <TAG_Compound>, ... ]

List of Attributes for a mob.

Attribute Tags

Name: <TAG_String>

Given name for the Attribute. Might be generic.maxHealth or horse.jumpStrength.

Base: <TAG_Double>

—

Modifiers: <TAG_List>

List of modifiers acting on the Attribute.

Modifier Tags

Name: <TAG_String>

—

Amount: <TAG_Double>

—

Operation: <TAG_Int>

—

UUIDMost: <TAG_Long>

—

UUIDLeast: <TAG_Long>

—

ActiveEffects: <TAG_List>

[<TAG_Compound>, <TAG_Compound>, ... ]

List of potion effects.

Effect Tags

Id: <TAG_Byte>

—

Amplifier: <TAG_Byte>

—

Duration: <TAG_Int>

—

Ambient: <TAG_Byte>

—

ShowParticles: <TAG_Byte>

—

ShowIcon: <TAG_Byte>

—

HandItems: <TAG_List>

[<TAG_Compound>, <TAG_Compound>]

Describes items the entity is holding. These Compound Tags have Tags Common to All Items. Slot is discluded.

<TAG_Compound 0>: The item held in the mob’s main hand.

<TAG_Compound 1>: The item held in the mob’s off-hand.

ArmorItems: <TAG_List>

[<TAG_Compound>, <TAG_Compound>, ... ]

What the entity is wearing. These Compound Tags have Tags Common to All Items. Slot is discluded.

<TAG_Compound 0>: The item worn on the feet.

<TAG_Compound 1>: The item worn on the legs.

<TAG_Compound 2>: The item worn on the chest.

<TAG_Compound 3>: The item worn on the head.

HandDropChances: <TAG_List>

—

ArmorDropChances: <TAG_List>

—

DeathLootTable: <TAG_String>

—

DeathLootTableSeed: <TAG_Long>

—

CanPickUpLoot: <TAG_Byte>

—

NoAI: <TAG_Byte>

—

PersistenceRequired: <TAG_Byte>

—

LeftHanded: <TAG_Byte>

—

Team: <TAG_String>

—

Leashed: <TAG_Byte>

—

Leash: <TAG_Compound>

—

Mobs That Breed

Mobs that can breed include Cows, Chickens, Pigs, Sheep, Villagers, Cats, and Dogs.

InLove: <TAG_Int>

Counts down number of ticks until this mob stops searching for a mate. Default 0 for a mob not doing so.

Age: <TAG_Int>

Age of the mob in ticks. When less than 0 and counting up, represents a baby mob. Adult mobs use this value to count down how many ticks until it can breed again.

ForcedAge: <TAG_Int>

LoveCauseLeast: <TAG_Long>

Least significant bits of the UUID for the entity that caused this animal to breed

LoveCauseMost: <TAG_Long>

Most significant bits of the UUID for the entity that caused this animal to breed

Mobs That Raid

Coming Soon

Specific Mobs

The following lists are specific to each mob

CustomName: ""Gerald""

CustomName: "{"text":"Gerald"}"

CustomName: ""Gerald""

CustomName: "{"text":"Gerald"}"

Other

To Be Removed

The rest of this page is likely to be removed.

Blocks («/setblock» or «/fill«)

Containers

Items: []The ID and other info of an item.

|_ id: {}The ID of the item.

|_ Slot: {}The slot number. Note that this starts at 0, not 1.

|_ tag: {}Other info of the item.

Items (/give)

All Items

Enchantments: Enchantments on the item.

|_ An enchantement. (List)

       |_ id: The name of the enchantment. Cannot be a number.

       |_ lvl: The level of the enchant. Range is -32768 to 32767.

display: Display properties.

|_ Name: The Custom Name of the item. Range of characters that can be used seems to be infinite.

       |_ Name: ["{"text":"enter custom name here"}"]

|_ color: The Custom Color of Leather Armor.

|_ Lore: The description of an item. Separate lines of text with a comma after the bracket, prior to the last quotation mark

       |_ Lore: ["{"text":"a line of text"}"]

Potions

CustomPotionEffects: Custom effects that a potion will have.

|_ A potion effect.

       |_ Id: The ID of the effect.

       |_ Duration: The duration of the potion effect.

       |_ Amplifier: The potency (+1) of the effect. Kept at 0 to keep a level 1 effect.

       |_ Ambient: (0/1) 0 is false, 1 is true. True if the effect is provided
by a beacon and thus should be less intrusive on screen.

Written Book

author: The author of the book.

title: The title of the book.

pages: The pages in the book.

|_ A page. Separate pages with a comma.

Tools

Unbreakable: (0b/1b) 0b is false, 1b is true. If value is 1b, the tool will never lose durability.

CanDestroy: What blocks this tool can destroy when in adventure mode.

        |_ A block ID.

CanPlaceOn: What blocks can be placed on in adventure mode.

        |_ A block ID.

Title and Tellraw

/title: /title (PlayerName) [(sub)title] {text:»PutTextHere»,color:»PutColorHere»},(Optional){text:»MoreTextHere»,color»PutColorHere»} (Add [] to enclose if doing multiple text tags)

/tellraw: /tellraw (PlayerName) {text:»PutTextHere»,color:»PutColorHere»},(Optional){text:»PutTextHere»,color:»PutColorHere»} (Add [] to enclose if doing multiple text tags)

This Minecraft tutorial explains the NBT tags (formerly called data tags) that you can use for a player in Minecraft Java Edition (PC/Mac) 1.16, 1.17, 1.18 and 1.19.

Background

Players have a unique set of NBT tags that can be used in Minecraft commands such as: /data and /scoreboard.

What are NBT tags (formerly called Data Tags)?

NBT tags allow you to set certain properties of a player. The NBT tag is always surrounded in {} such as {Dimension:»minecraft:the_nether»}. If there is more than one NBT tag used in a game command, the NBT tags are separated by a comma such as {Dimension:»minecraft:the_nether», foodLevel:20}.

List of NBT Tags

Here is a list of the NBT tags that you can use for a player in Minecraft Java Edition (PC/Mac) 1.16, 1.17, 1.18 and 1.19:

NBT Tag Examples

To get the NBT tags (or data tags) for the nearest player:

/data get entity @p

Next, learn how to use the game commands in Minecraft.

Other NBT Tags

Here are some of the other NBT tags (formerly called data tags) in Minecraft:

В теме 10 сообщений