Target selectors

Target selectors are used in commands to select players and entities arbitrarily, without needing to specify an exact player name or a UUID. One or more entities can be selected with a target selector variable, and targets can be filtered from the selection based on certain criteria using the target selector arguments.

Summary of target selector variables

Variable	Selects
@p	the nearest player
@r	a random player
@a	all players
@e	all entities
@s	the entity executing the command
@n	the nearest entity
@c	the player's agent‌[edu only]
@v	all agents‌[edu only]
@initiator	the player who clicks an NPC dialogue button‌[BE & edu only]

A target selector variable identifies the broad category of targets to select. There are six in Java Edition, seven in Bedrock Edition and nine in Minecraft Education:

@p

Selects the nearest player from the command's execution. If there are multiple nearest players, caused by them being precisely the same distance away, the player who most recently joined the server is selected.

In Bedrock Edition, @p selects only players who are alive.

@n

Selects the nearest alive entity from the command's execution.

@r

Selects a random online player.

In Bedrock Edition, @r can be used to select non-player entities via the type selector argument; in Java Edition, to select a random entity, use @e[sort=random,limit=1] or @n[sort=random] instead.

In Bedrock Edition, @r can select only entities who are alive.

@a

Selects every online player (alive or dead).

@e

Selects all alive entities in loaded chunks, and all alive online players.

@s

Selects the entity (alive or not) that the command was executed as. It does not select anything if the command was not ran as an entity (e.g. from a command block or server console).

@c‌^{[Minecraft Education only]}

Selects the player's agent only.

@v‌^{[Minecraft Education only]}

Selects all agents. Works only if more than one agent exists.

@initiator‌^{[BE & edu only]}

Selects the player who interacts with a button in a JSON NPC dialogue.

Summary of target selector arguments

Selection by Spatial Properties
Argument(s)	Selection criteria
x, y, z	coordinate
distance‌[JE only] r, rm‌[BE only]	distance
dx, dy, dz	volume dimensions
x_rotation‌[JE only] rx,rxm‌[BE only]	vertical rotation (pitch)
y_rotation‌[JE only] ry,rym‌[BE only]	horizontal rotation (yaw)
Selection by Scoreboard Values
Argument(s)	Selection criteria
scores	scores
tag	tag
team ‌[JE only]	team name
Selection by Entity Species
Argument(s)	Selection criteria
name	entity name
type	entity type
family‌[BE only]	entity family
predicate‌[JE only]	predicate
Selection by Entity Data
Argument(s)	Selection criteria
nbt‌[JE only]	nbt
hasitem‌[BE only]	item
has_property‌[BE only]	property
Selection by Player Data
Argument(s)	Selection criteria
level‌[JE only] l,lm‌[BE only]	experience level
gamemode‌[JE only] m‌[BE only]	game mode
advancements‌[JE only]	advancements
haspermission‌[BE only]	permission
Selection by Traits
Argument(s)	Selection criteria
limit,sort‌[JE only] c‌[BE only]	limit

After a target selector, optional arguments can be used to narrow down the set of targets to a group that also matches certain criteria. When used with @a or @e, arguments narrow down the targets from the full list to a specific group. When used with @p or @r, the nearest or random player is selected from the group. When used with @s, the player using the command is targeted only if they would be in the narrowed group.

Argument-value pairs appear within square brackets after the target selector variable, separated by commas:

@<variable>[<argument>=<value>,<argument>=<value>,...].

In Java Edition, arguments and values are case-sensitive. Spaces are allowed around the brackets, equal signs, and commas, except in Java Edition between the target variable and the first bracket. Commas must be used to separate argument-value pairs.

If there are multiple argument-value pairs, they all must be satisfied to add a potential target to the group. (In other words, they are AND-ed together).

[x=<value>,y=<value>,z=<value>] — Define a position in the world that the selector starts at, for use with the distance argument, the volume arguments, or the sort and limit arguments. Using these arguments alone does not restrict the entities found (except in Java Edition), and affect only the sorting of targets. Cannot duplicate any one of these three arguments.

The positional components are doubles, allowing for values like 12.34. In Java Edition they are not center-corrected, meaning x=0 is not corrected to x=0.5. In Bedrock Edition, if distance or volume arguments are not used, positions that are written as integers are center-corrected, x=0 becomes x=0.5. To avoid this, use x=0.0 instead.

In Bedrock Edition, tilde notation is available for selector argument coordinates. Note: Caret notation is not.

In Java Edition, these arguments limit the search of entities to the current dimension. For example /execute in overworld as @e[x=0] will select only entities that are in the overworld.

Filter target selection based on their Euclidean distances from some point, searching for the target's feet (a point at the bottom of the center of their hitbox). If the positional arguments are left undefined, radius is calculated relative to the position of the command's execution. This argument limits the search of entities to the current dimension. Cannot duplicate these arguments.

In Java Edition: [distance=<value>] — Specifies the range of distance. Float ranges are supported to select a specific region. Only unsigned values are allowed.

In Bedrock Edition: [r=<value>] and [rm=<value>] — Specifies the maximum and minimum range to find entities, respectively. Only unsigned values are allowed.

Examples in Java Edition:

• @e[distance=10..] — Target all entities more than ten blocks away.
• @e[distance=..10] — Target all entities less than ten blocks away.
• @e[distance=10] — Target all entities exactly ten blocks away.
• @e[distance=8..16] — Target all entities more than eight blocks, but less than 16 blocks away (inclusive).

Examples in Bedrock Edition:

• @e[r=10] — Target all entities that are ten or fewer blocks away.
• @e[rm=10] — Target all entities that are ten or more blocks away.
• @e[rm=10,r=10] — Target all entities exactly ten blocks away.
• @e[rm=8,r=16] — Target all entities from 8 to 16 blocks away.

[dx=<value>,dy=<value>,dz=<value>] — Filter target selection based on their x-difference, y-difference, and z-difference from some point, as measured by entities' hitboxes. Cannot duplicate any one of these three arguments.

Numerically, this can be interpreted as creating a cuboid volume from the initial position (x,y,z) to (x+dx,y+dy,z+dz) but with the vector (1,1,1) added to the x-most, y-most, z-most corner (the upper south-east corner). Because of this, the volume to check can never be smaller than a cube with a side length of 1, and no single dimension of the volume can be less than 1. Then, all entities whose hitboxes at least partially intersect with that volume are selected. If the positional arguments are left out, the selection is interpreted as originating from the position of the command's execution. Any values are allowed, including signed and fractional numbers.

If all of the values are whole numbers, this can be interpreted as creating a volume of blocks from the initial position (x y z) to the delta position (x+dx y+dy z+dz)) and selecting any entity whose hitbox intersects with those blocks. So, if you have built a cuboid of blocks in the world, you can subtract the coordinates of one corner block from the coordinates of the opposite corner block to get the dx, dy, and dz values for selecting those entities.

Note that dx, dy, and dz specify signed differences from the given coordinate. They do not specify a separate coordinate, nor do they extend in both the positive and negative directions as you might expect from a position predicate.

Additionally, when only one or two volume arguments are present, any that are not specified are assumed to be set to zero. For example, @a[dx=15] is equivalent to @a[dx=15,dy=0,dz=0].

Examples:

• @e[x=1,y=2,z=3,dx=0,dy=0,dz=0] — Select all entities whose hitbox intersects with the block at 1 2 3.
• @e[x=1,y=2,z=3,dx=4,dy=5,dz=-6] — Select all entities whose hitbox intersects with the block region 1~5, 2~7, -3~3.
  • (or, the numerically speaking, a cuboid from 1.0 2.0 -3.0 to 6.0 8.0 4.0).
  • (or, mathematically speaking, the region that is { (x,y,z)∈R³ | x∈[1.0,6.0], y∈[2.0,8.0], z∈[-3.0,4.0] }), or

It is possible to combine selection by distance and selection by volume, in which case the command select targets only within the overlap of both regions (within a certain radius of the volume's initial point and not outside the defined volume) — but note that distance selection checks that the point at an entity's feet intersects with some sphere, whereas volume selection checks that the entity's hitbox overlaps with some region.

[scores={<objective>=<value>,...}] — Filter target selection based on their scores in the specified objectives. All tested objectives are in a single object, separated by commas. Each objective and score value pair is separated by an equals sign. The score values support integer ranges. Cannot duplicate this argument.

• @e[scores={myscore=10}] — Select all entities with a score in objective myscore of exactly ten.
• @e[scores={myscore=10..12}] — Select all entities with a score in objective myscore of between ten and 12 (inclusive).
• @e[scores={myscore=5..}] — Select all entities with a score in objective myscore of five or greater.
• @e[scores={myscore=..15}] — Select all entities with a score in objective myscore of 15 or less.
• @e[scores={foo=10,bar=1..5}] — Select all entities with a score in objective foo of exactly ten, and a score in objective bar of between one and five (inclusive).

In Bedrock Edition, ! can be used to invert selection.

• @e[scores={myscore=!10}] — Exclude any entities with a score in objective myscore of exactly ten.
• @e[scores={myscore=!10..15}] — Exclude any entities with a score in objective myscore of between ten and 15 (inclusive).

Filter target selection based on the entity's scoreboard tags. Multiple tag arguments are allowed, and all arguments must be fulfilled for an entity to be selected.

[tag=<string>] — Include only targets with the specified tag.

[tag=!<string>] — Exclude any targets with the specified tag.

[tag=] — Include only targets with exactly zero tags.

[tag=!] — Include only targets that have at least one tag.

Filter target selection based on teams. Arguments testing for equality cannot be duplicated, while arguments testing for inequality can.

[team=<teamName>] — Include only targets in the given team.

[team=!<teamName>] — Exclude any targets in the given team.

[team=] — Include only targets not in a team.

[team=!] — Exclude any targets not in a team.

Limit the number of selectable targets for a target selector.

When using the variables @p and @r, this argument defaults to one. Applying the limiting argument to them may increase the number of nearest or random targets selected. When applying this argument to @a or @e, this argument returns only a limited number of targets. Cannot duplicate these arguments.

In Java Edition: [limit=<value>,sort=(nearest|furthest|random|arbitrary)] — Limit the number of targets, and specify selection priority.

• sort=nearest — Sort by increasing distance. (Default for @p)
• sort=furthest — Sort by decreasing distance.
• sort=random — Sort randomly. (Default for @r)
• sort=arbitrary — Do not sort. This often returns the oldest entities first due to how the game stores entities internally, but no order is guaranteed. (Default for @e, @a)

In Bedrock Edition: [c=<value>] — Limit the number of targets.

For @p, @a, and @e, [c=<value>] selects only the specified number of targets by increasing distance from the selector's position. When c is negative, it reverses the order of targeting (for example, @p[c=-1] targets the furthest player). Inverse sorting does not work with @r.

Examples in Java Edition:

• @a[limit=3,sort=nearest] or @p[limit=3] — Select the nearest three players.
• @a[limit=4,sort=furthest] — Select the furthest four players.
• @a[limit=2,sort=random] or @r[limit=2] — Select two players, chosen randomly.

Examples in Bedrock Edition:

• @a[c=3] — Select the nearest three players.
• @a[c=-4] — Select the furthest four players.
• @r[c=2] — Select two living players, chosen randomly.

Filter target selection based on the entity's experience levels. This naturally filters out all non-player targets. Cannot duplicate these arguments.

In Java Edition: [level=<value>] — Specifies the range of levels. Integer ranges are supported to select a range of values.

In Bedrock Edition: [l=<value>] and [lm=<value>] — the maximum and minimum level range to search for, respectively.

Examples in Java Edition:

• @a[level=10] — Select all players who have exactly ten levels.
• @a[level=8..16] — Select all players who have between eight and 16 levels (inclusive).

Examples in Bedrock Edition:

• @a[lm=10,l=10] — Select all players who have exactly ten levels.
• @a[lm=8,l=16] — Select all players who have between eight and 16 levels (inclusive).

Filter target selection by game mode. This naturally filters out all non-player targets. Arguments testing for equality cannot be duplicated, while arguments testing for inequality can.

In Java Edition:

[gamemode=<gamemodeName>] — Include only players in the given game mode.

[gamemode=!<gamemodeName>] — Exclude any players in the given game mode.

In Bedrock Edition:

[m=<gamemodeName>] — Include only players in the given game mode.

[m=!<gamemodeName>] — Exclude any players in the given game mode.

Permitted values for <gamemodeName> are spectator, survival, creative, adventure and default‌^{[BE only]}. In Bedrock Edition, the shorthand values s and 0, c and 1, a and 2, and d and 5 may be used for Survival mode, Creative mode, Adventure mode, and Default mode respectively.

Filter target selection by name. Values are strings, so spaces are allowed only if quotes are applied. This cannot be a JSON text compound. Arguments testing for equality cannot be duplicated, while arguments testing for inequality can.

[name=<givenName>] — Include only targets with the given name.

[name=!<givenName>] — Exclude any targets with the given name.

Filter target selection based on the entity's rotation along the pitch axis, measured in degrees. Values range from -90 (straight up) to 0 (at the horizon) to +90 (straight down). Cannot duplicate these arguments.

In Java Edition: [x_rotation=<value>] — Specifies the range of x-rotation. Float ranges are supported to select a specific range of angles.

In Bedrock Edition [rx=<value>] and [rxm=<value>] — Specifies the maximum and minimum x-rotation, respectively.

Examples in Java Edition:

• @e[x_rotation=0] — Select all entities that are looking directly at the horizon.
• @e[x_rotation=30..60] — Select all entities that are looking between 30° and 60° (inclusive) below the horizon.
• @e[x_rotation=..0] — Select all entities that are looking at or above the horizon.

Examples in Bedrock Edition:

• @e[rxm=0,rx=0] — Selects all entities that are looking directly at the horizon.
• @e[rxm=30,rx=60] — Selects all entities that are looking between 30° and 60° (inclusive) below the horizon.
• @e[rx=0] — Select all entities that are looking at or above the horizon.

Filter target selection based on the entity's rotation along the yaw axis, measured clockwise in degrees from due south (or the positive Z direction). Values vary from -180 (facing due north) to -90 (facing due east) to 0 (facing due south) to +90 (facing due west) to +180 (facing due north again). Cannot duplicate these arguments.

In Java Edition: [y_rotation=<value>] — Specifies the range of y-rotation. Float Ranges are supported to select a specific range of angles.

In Bedrock Edition: [ry=<value>] and [rym=<value>] — Specifies the maximum and minimum y-rotation values, respectively.

Examples in Java Edition:

• @e[y_rotation=0] — Select all entities that are facing due south.
• @e[y_rotation=-90..0] — Select all entities that are facing in the 90° between due east and due south (inclusive).
• @e[y_rotation=0..180] — Select all entities that are not facing at all east.

Examples in Bedrock Edition:

• @e[rym=0,ry=0] — Select all entities that are facing due south.
• @e[rym=-90,ry=0] — Select all entities that are facing in the 90° between due east and due south (inclusive).
• @e[rym=0,ry=180] — Select all entities that are not facing at all east.

Filter target selection based on the entity's identifier. The given entity type must be a valid entity ID or entity type tag‌^{[Java Edition only]} used to identify different types of entities internally. The namespace can be left out if the ID is within the minecraft namespace. Entity IDs or tags are case-sensitive. Arguments testing for equality cannot be duplicated, while arguments testing for inequality can. In Java Edition, using this argument with @a, @p or @r is not allowed.

[type=<entityType>] — Include only targets of the specified entity type or tag.

[type=!<entityType>] — Exclude any targets of the specified entity type or tag.

In Java Edition, the option type=<entityType> (without ! symbol) can appear only once, and type=!<entityType> cannot appear with it. If type=<entityType> does not exist, then type=!<entityType> may appear multiple times.

Examples:

• @e[type=creeper] - Include only creepers.
• @e[type=creeper, type=pig] - Invalid selector.
• @e[type=creeper, type=!pig] - Invalid selector.
• @e[type=!creeper, type=!pig] - Exclude all creepers and pigs.

Filter target selection based on the entity's type_family behavior component. Default values used by the vanilla behavior pack include among others more broad terms like mob and inanimate, as well as more specific families like zombie and skeleton, and single-mob families like wandering_trader and creeper. Multiple family arguments are allowed, and all arguments must be fulfilled for an entity to be selected.

Main article: family

[family=<family>] — Include only targets in the specified type family.

[family=!<family>] — Exclude any targets in the specified type family.

• @e[family=skeleton] — Select all skeletons, wither skeletons, strays, bogged, parched, and withers.
• @e[family=mob,family=!monster] — Select all mobs that are not monsters (so for example cows, chickens, pigs, but not zombies or skeletons).
• @e[family=monster,family=undead] — Select all monsters that are also undead (that includes monsters like zombies and skeletons, but not creepers, spiders or endermen).

Filter target selection based on the entity's NBT data. The NBT data is written in its SNBT format. Duplicate nbt arguments are allowed, and all arguments must be fulfilled for an entity to be selected.

See NBT format#Testing NBT tags for more information about this.

Note that this selector argument should be used with care, as accessing NBT data is a heavy process for the CPU.

[nbt=<compoundTag>] — Include only targets with the specified NBT data.

[nbt=!<compoundTag>] — Exclude any targets with the specified NBT data.

• @a[nbt={OnGround:true}] — Select all players on the ground.
• @e[type=sheep,nbt={Color:0b}] — Select all sheep that are dyed white.
• @e[type=item,nbt={Item:{id:"minecraft:slime_ball"}}] — Selects all slime ball item entities.
• @e[nbt={Tags:[a,b]}] is the same as @e[tag=a,tag=b]. The latter is simpler and reduces CPU load.

Filter target selection based on the entity's advancements. This naturally filters out all non-player targets. All advancements are in a single object, with a list of individual advancement IDs between the braces afterward. The values are true or false. For advancements with one criterion, testing for that criterion always gives the same results as testing for the advancement. Cannot duplicate this argument.

[advancements={<resource location>=<bool>}] — Include only players with the specified advancements and values.

[advancements={<resource location>={<criteria>=<bool>}}] — Include only players with the specified advancement's criteria.

• @a[advancements={story/smelt_iron=true}] — Include only players who have completed the advancement minecraft:story/smelt_iron.
• @a[advancements={story/form_obsidian=false}] — Include only players who haven't completed the advancement minecraft:story/form_obsidian.
• @a[advancements={story/follow_ender_eye=true}] is the same as @a[advancements={story/follow_ender_eye={in_stronghold=true}}].
• @a[advancements={adventure/kill_all_mobs={witch=true}}] — Include only players who have killed a witch, for the advancement minecraft:adventure/kill_all_mobs.

Filter target selection by predicates. The given values must be a valid predicate represented by a resource location. Duplicate predicate arguments are allowed, and all arguments must be fulfilled for an entity to be selected.

[predicate=<resource location>] — Include only targets that match the specified predicate.

[predicate=!<resource location>] — Exclude any targets that match the specified predicate.

Filter target selection based on whether the entity has the specified items. The given values must be enclosed by square brackets or braces. Cannot duplicate this argument, but multiple items can be specified with square brackets.

[hasitem={<argument>=<value>,<argument2>=<value2>,...}] — Include only targets that have the specified items.

[hasitem=[{<argumentA>=<valueA>,...},{<argumentB>=<valueB>,...}]] — Include only targets that have item A and item B, etc.

All acceptable arguments are as follows:

(More information about what this section is looking for should be given as this section is too vauge.)

• item (required)

  Must be an item ID.

• data

  Specifies the item data for the item(s). Must be a 32-bit integer number. Values that are invalid for the specified item id default to 0. If not specified, defaults to 0.

  Note that because it defaults to 0, selectors like {item=potion} can target only water bottle, though {item=potion,data=1} can target mundane potion.

  Currently doesn't work on blocks' direct item forms (e.g. dirt, stone). For these items, data is always considered as invalid and defaults back to 0, and aux value of these items in inventory are also always considered as 0. That means you can't target items like coarse dirt, green wool solely.

  For potion and tipped arrow, aux value represents the data value of potion effect, and currently invalid values crash the game.

• quantity

  Specifies the amount of the items the entity has. Must be an integer range (e.g. 1 - exact match of 1. ..5 - less than or equal to 5. 5.. - more than or equal to 5. 0..5 - between 0 and 5, inclusive.).

  ! can be used to invert selection. For example, {item=apple,quantity=!5} can exclusive entities who have five apples.

  When not specified, defaults to quantity=1... When quantity=0, entities must have 0 the specified item (i.e. do not have the specified item) to be targeted.

• location and slot

  Specifies the inventory slot to test. See Slot for details.

  Specifying slot without location is invalid.

  slot must be an integer range. (e.g. 1 - exact match of 1. ..5 - less than or equal to 5. 5.. - more than or equal to 5. 0..5 - between 0 and 5, inclusive.)

• Example using location: @s[hasitem={item=stick,location=slot.weapon.mainhand}]

[haspermission={<permission>=<state>,...}] — Filter target selection based on the player permissions status. All tested permissions are in a single object, separated by commas. Cannot duplicate this argument.

• @a[haspermission={camera=enabled}] — Include only players who have the camera permission enabled.
• @a[haspermission={movement=disabled}] — Include only players who have the movement permission disabled.
• @a[haspermission={camera=disabled,movement=enabled}] — Include only players who have the camera permission disabled and the movement permission enabled.

Filter target selection based on the entity's property. All tested properties are in a single object, separated by commas. Cannot duplicate this argument.

[has_property={<property>=<value>,...}] — Include only targets that have the specified property values.

[has_property={<property>=!<value>,...}] — Exclude only targets that have the specified property values.

[has_property={property=<property>,...}] — Include only targets that have the specified properties.

[has_property={property=!<property>,...}] — Exclude only targets that have the specified properties.

• @e[type=chicken,has_property={minecraft:climate_variant=!"cold"}] — Selects all chickens that do not have the minecraft:climate_variant property cold.
• @e[has_property={minecraft:climate_variant="warm"}] — Selects all entities that have the minecraft:climate_variant property warm (it would only apply to cows, chickens, etc.).
• @e[has_property={minecraft:has_nectar=true}] — Selects all entities that have the minecraft:has_nectar property true (it would only apply to bees).
• @e[has_property={minecraft:creaking_swaying_ticks=!1..}] — Selects all entities that do not have the minecraft:creaking_swaying_ticks property 1 or higher (it would apply to all entities except creakings that are swaying).
• @e[has_property={minecraft:climate_variant=!"temperate",property=minecraft:climate_variant}] — Selects all entities that have the minecraft:climate_variant property except those whose value is temperate.
• @e[has_property={property=minecraft:armadillo_state}] — Selects all entities that have the minecraft:armadillo_state property.

List of entity properties:

Some command arguments require a player-type selector, while some require an entity-type selector.

Entity type means that there's no additional restrictions. Any valid selector can be used in this command argument.

A player-type selector is a selector that can only select players, including:

• @e, @n with type=player.
• @a, @p (without type argument in Bedrock Edition).
• @r with type=player‌^{[Bedrock Edition only]} or without type argument.

In Java Edition, if a command argument requires a player type selector, but the entered argument is not in player type, the command is unparseable.

In Bedrock Edition, if a command argument requires a player type selector, but the entered argument is not in player type, the command is parseable but fails.

Some command arguments require a single-type selector, while some require a multiple-type selector.

Multiple type means that there's no additional restrictions. Any valid selector can be used in this command argument.

A single-type selector is a selector that can only select one target, including:

• @a, @e with limit=1.
• @s without limit argument.
• @p, @r without limit argument or with limit=1.

If a command argument requires a single-type selector, but the entered argument is not in single-type, the command is unparseable.

Java Edition
1.4.2			12w32a				Added target selectors.
			12w38a				Added target selector arguments with x, y, z, r, m and c.
			12w39b				Added l and lm target selector arguments for indicating players with a maximum level, and minimum level, respectively.
							Added the rm target selector argument for indicating players from a minimum distance.
?							Added the name target selector argument.
1.5			?				Added the score_objective and score_objective_min target selector arguments, where objective should be replaced with the objective to test.
							Added the team target selector argument.
1.8			14w02a				Added the @e target selector variable.
							Added the type target selector argument.
			14w03a				Added dx, dy, and dz target selector arguments.
			14w07a				Added rx, rxm, ry and rym target selector arguments.
1.9			15w32b				Added the tag target selector argument.
			16w02a				The m selector now accepts the standard literal gamemode values and abbreviations, such as a and adventure, and these may be negated as well.
1.11			16w38a				Removed implicit target selectors (for example, @e[167,28,454]).
							Invalid target selectors (such as @e[Type=creeper], @e[asdf=nonexistent], and @e[malformed]) now generate an error instead of being silently ignored.
1.12			17w16b				Added the @s target selector variable.
1.13			17w45a				Target selector arguments can now be quoted.
							The shorthand argument names have been renamed. m -> gamemode l or lm -> level r or rm -> distance rx or rxm -> x_rotation ry or rym -> y_rotation c -> limit
							Arguments that formerly had a "min" and "max" now support ranges using .. (for example distance=12..34).
							x, y, z, distance, x_rotation, and y_rotation arguments are now doubles.
							x and z are no longer center-corrected.
							gamemode argument no longer allows numerical or shorthand IDs.
							limit argument no longer supports negative values for sorting by furthest.
							name argument now supports spaces (as long as it is quoted).
							Multiple occurrences of the same argument is now possible.
							Added sort and advancements arguments.
							Specifying scores now looks like scores={foo=1,bar=1..5}.
			17w45b				Added the nbt target selector argument.
1.15			19w38a				Added the predicate target selector argument.
1.21			24w21a				Added the @n selector which selects the nearest entity.
			pre1				@n no longer selects dying entities.[1]
1.21.5			25w05a				The team argument can now select non-living entities.[2]

Pocket Edition Alpha
v0.16.0			build 1				Added target selectors along with Commands.
Bedrock Edition
1.17.10			beta 1.17.10.22				Added the @initiator target selector variable.
1.18.30			beta 1.18.20.21				Added the hasitem target selector argument.
1.19.80			Preview 1.19.80.21				Added the haspermission target selector argument.
1.20.70			Preview 1.20.70.21				Added the has_property target selector argument.
1.21.100			Preview 1.21.100.21				Added the @n selector which selects the nearest entity.

Issues relating to "Target selectors" are maintained on the bug tracker. Issues should be reported and viewed there.

• Commands
• Entity format

v t e Commands
All editions	clear clone damage deop difficulty effect enchant execute fill function gamemode gamerule give help kick kill list locate loot me msg op particle place playsound recipe reload ride say schedule scoreboard setblock setworldspawn spawnpoint spreadplayers stopsound summon tag teleport tell tellraw time title tp transfer w weather xp Removed placefeature
JE & BE only	stop whitelist
JE only	advancement attribute ban ban-ip banlist bossbar data datapack debug defaultgamemode dialog experience fetchprofile fillbiome forceload item jfr pardon pardon-ip perf publish random return rotate save-all save-off save-on seed setidletimeout spectate stopwatch swing team teammsg tm test tick trigger unpublish version waypoint worldborder Debug chase debugconfig debugmobspawning debugpath raid serverpack spawn_armor_trims warden_spawn_tracker Removed ? achievement banip blockdata broadcast chunk entitydata home iron locatebiome replaceitem setspawn solid stats testfor testforblock testforblocks toggledownfall unban wood
BE only	aimassist allowlist changesetting clearrealmevents controlscheme dedicatedwsserver gametips packstack party​[upcoming] project reloadconfig reloadpacketlimitconfig save sendshowstoreoffer set_movement_authority Removed bossbar mixer tptobiome volumearea Developer aigoals automate automateactivetool automatebreakblock automatefindblock automatefly automategetinteractionpositionforblock automatelookat automatemove automatemoveto automateplaceblock bhave bounds cleanroom clearslot clearinventory crash crashclient crashserver createlocalworld destroyblock dumpblocknames dumpentitiesclient dumpentitiesserver enchantrandom fillchestblock filldrive findanchoredbuildpos findflatarea findnearbypickups fixbiomes fly getactivescreen getavgendframerate getavgremaindertimepercent getavgrendertime getavgticktime getavgunaccountedtimepercent getblockname getbrightness getchestcontents getchunkdirtycount getchunkrebuildcount getchunksortcount getcpu getdurability getexperience getfps getgpu getgpumemory getguiscale getmsaalevel getos getplayerbiome getplayerid getpos getpower getprofilersecondsperupdate getresolution getselecteditemcount getskin getstructure getsysteminfo getsystemmem getviewdistance getworldname health hunger islargechestblock isplayercrouching isplayerflying isplayergrounded isworldloaded kit leaveworld loadbehaviortreedefinitions log lookat memwarn nearbyentityisbaby networkstats notifyprofiler paths pause placefromhand playerstat profile redstonetest register3pserver resupply rot selectinventoryitem sendmodalform setbrightness setguiscale setskin setviewdistance showallitems showfrustum simlock simscale simulationtype skin spawnfeature spawning spawnitem spawnmob stoptime systemstat testassets timelock tptosuitabletree villages wipeout
edu only	classroommode closechat code codebuilder lesson remove videostream Removed position videostreamaction
BE & Edu only	? ability agent alwaysday camera camerashake clearspawnpoint codebuilder_actorinfo connect daylock dialogue drop enableencryption event fog getlocalplayername gettopsolidblock hud immutableworld inputpermission listd mobevent music ops permission playanimation querytarget replaceitem script scriptevent setmaxplayers structure takepicture testfor testforblock testforblocks tickingarea titleraw toggledownfall wb worldbuilder wsserver Removed clearfixedinv detect executeasself move place setfixedinvslot setfixedinvslots test transferserver
Joke	debugdim transform vote warp
Related	Argument types Permission level Slot

Retrieved from "https://minecraft.wiki/w/Target_selectors?oldid=3616821"