NBT Tags for Vex – Wiki Guide
This Minecraft tutorial explains the NBT tags (formerly called data tags) that you can use for a vex in Minecraft Java Edition (PC/Mac) 1.16, 1.17, 1.18, 1.19 and 1.20.
TIP: If you are not running Minecraft Java Edition (PC/Mac) 1.16/1.17/1.18/1.19/1.20, find NBT tags for vex in another version of Minecraft:
- Java Edition (PC/Mac) 1.14/1.15
- Java Edition (PC/Mac) 1.11/1.12
Background
In Minecraft Java Edition 1.16, 1.17, 1.18, 1.19 and 1.20, the entity value for a vex is vex
. The vex
entity has a unique set of data tags that can be used in Minecraft commands such as: /summon and /data.
What are NBT tags (formerly called Data Tags)?
NBT tags allow you to set certain properties of an entity (such as vex
). The NBT tag is always surrounded in {} such as {CustomName:”\”John\””}. If there is more than one NBT tag used in a game command, the NBT tags are separated by a comma such as {CustomName:”\”John\””, Health:25.0f}.
List of NBT Tags
Here is a list of the NBT tags that you can use for vex
in Minecraft Java Edition (PC/Mac) 1.16, 1.17, 1.18, 1.19 and 1.20:
NBT Tag | Value (Description) | Works With |
---|---|---|
LeftHanded | 0 (The vex is right-handed) 1 (The vex is left-handed) Example |
/summon /data |
CustomName |
name (The name to assign to the vex) Example |
/summon /data |
Health |
number (The number of health points the vex has) Example |
/summon /data |
AbsorptionAmount |
number (The number of absorption health points the vex has) Example |
/summon /data |
Invulnerable |
0 (The vex will take damage like normal) Example |
/summon /data |
PersistenceRequired |
0 (The vex will despawn naturally) Example |
/summon /data |
NoAI |
0 (The vex will have artificial intelligence and will move/behave like normal) Example |
/summon /data |
Silent |
0 (The vex will make its usual noises in the game) Example |
/summon /data |
Fire |
ticks (The number of game ticks until the vex is no longer on fire – there are 20 ticks in a second) Example |
/summon /data |
PortalCooldown |
ticks (The number of game ticks until the vex can go through a portal again – there are 20 ticks in a second) Example |
/summon /data |
Air |
ticks (The number of game ticks the vex has air left for) Example |
/summon /data |
HandItems |
Items that the vex is holding in its hands, listed in this order: right hand, left hand Syntax Example |
/summon /data |
HandDropChances |
The drop chances for each of the 2 items listed in HandItems. A value of 1.0f means 100% chance of the item being dropped when the vex is killed, 0.5f means 50%, 0.2f means 20%, and so on. Example |
/summon /data |
id |
vex (The entity value used to represent a vex in the EntityTag or Passengers tag) Example |
/summon /give |
Passengers |
The mob that is riding on the vex. Use the entity value for the passenger mob Example of skeleton as passenger |
/summon /data |
NBT Tag Examples
To summon a vex with a custom name of John:
/summon vex ~ ~ ~ {CustomName:"\"John\""}
To summon a vex with a custom name of John and has no artificial intelligence:
/summon vex ~ ~ ~ {CustomName:"\"John\"", NoAI:1}
Target Selectors
Before we finish discussing data tags, let’s quickly explore how to use the @e target selector. The @e target selector allows you to target entities in your commands. If you use the type=vex
value, you can target vexs:
@e[type=vex]
Target Selector Examples
To change the nearest vex to have no artificial intelligence:
/data merge entity @e[type=vex,limit=1,sort=nearest] {NoAI:1}
To kill all vexs:
/kill @e[type=vex]
Next, learn how to use the game commands in Minecraft.
Command Examples
Here are some game command examples for a vex in Minecraft: