Minecraft:Argument types: Difference between revisions

Newer edit →

VisualWikitext

Revision as of 15:19, 9 April 2026

This page contains a list of all command argument types. Template:TOC

Java Edition

brigadier:bool

Template:Arg desc

Official examples

Template:Anchor

brigadier:double

Template:Arg desc

Each double argument may have a custom minimum and maximum value.

Precision varies throughout number line; the maximum absolute value is about 1.8×10³⁰⁸.

Official examples

JSON properties in command syntax output

Template:Nbt: The root properties object.
- Template:Nbt: The maximum value of this double argument.
- Template:Nbt: The minimum value of this double argument.

brigadier:float

Template:Arg desc

Each float argument type may have a custom minimum and maximum value.

Precision varies throughout number line; the maximum absolute value is about 3.4×10³⁸.

Official examples

JSON properties in command syntax output

Template:Nbt: The root properties object.
- Template:Nbt: The maximum value of this float argument.
- Template:Nbt: The minimum value of this float argument.

Template:Anchor

brigadier:integer

Template:Arg desc

Each integer argument type may have a custom minimum and maximum value.

Maximum range is from −(2³¹) to (2³¹ − 1), or from (−2,147,483,648) to (2,147,483,647).

Official examples

JSON properties in command syntax output

Template:Nbt: The root properties object.
- Template:Nbt: The maximum value of this integer argument.
- Template:Nbt: The minimum value of this integer argument.

Template:Anchor

brigadier:long

Template:Arg desc

Note: Although a long argument type is present in brigadier, it is not used by Minecraft.

Each long argument type may have a custom minimum and maximum value.

Maximum range is from −(2⁶³) to (2⁶³−1), or from (−9,223,372,036,854,775,808) to (9,223,372,036,854,775,807).

Official examples

JSON properties in command syntax output

Template:Nbt: The root properties object.
- Template:Nbt: The maximum value of this long argument.
- Template:Nbt: The minimum value of this long argument.

Template:Anchor

brigadier:string

Template:Arg desc

Each string argument type can accept either a single word (no spaces), a quotable phrase (either single word or quoted string), or a greedy phrase (taking the rest of the command as the string argument).

Official examples

Single word

Quotable phrase

Greedy phrase

JSON properties in command syntax output

Template:Nbt: The root properties object.
- Template:Nbt: The type of this string argument. Can be Template:Cd, Template:Cd, or Template:Cd

Template:Anchor

minecraft:angle

Template:Arg desc

Official examples

Template:Anchor

minecraft:block_pos

Template:Arg desc

Official examples

Template:Anchor

minecraft:block_predicate

The format of block_predicate parameters is block_id[block_states]{data_tags}, in which block states and data tags can be omitted when they are not needed.

block_id is required, and it should be in the format of resource location(if namespace isn't set it defaults to minecraft:).
- It can also be the resource location of a block tag prefixed with #, such as #minecraft:planks.
Block states are inside [], comma-separated and properties and values must be supported by the block or all blocks in the tag. They are optional.
- minecraft:stone[doesntexist=purpleberry] is unparseable, because stone doesn't have doesntexist.
- minecraft:redstone_wire[power=tuesday] is unparseable, because redstone_wire's power is a number between 0 and 15.
Data tags are inside {}. They are optional.
When test for block, only the states provided are tested.
- If a command tests for redstone_wire[power=15], it checks only power, but ignores other states such as north.

Official examples

Template:Cd
Template:Cd
stone[foo=bar]
Template:Cd
#stone[foo=bar]{baz:nbt}

Template:Anchor

minecraft:block_state

The format of block_state parameters is block_id[block_states]{data_tags}, in which block states and data tags can be omitted when they are not needed.

block_id is required, and it should be in the format of resource location (if namespace isn't set it defaults to minecraft:).
Block states are inside [], comma-separated and must be properties/values supported by the blocks. They are optional.
- minecraft:stone[doesntexist=purpleberry] is unparseable, because stone doesn't have doesntexist.
- minecraft:redstone_wire[power=tuesday] is unparseable, because redstone_wire's power is a number between 0 and 15.
Data tags are inside {}. They are optional.
When placing blocks, any states provided are set, but anything omitted retain their default values, depending on the block type.
- If a command sets redstone_wire[power=15], it is set power to 15, but north is a default value (in this case, set to none).

Official examples

Template:Cd
Template:Cd
stone[foo=bar]
foo{bar:baz}

Template:Anchor

minecraft:color

Template:Arg desc

Official examples

Template:Anchor

minecraft:column_pos

Template:Arg desc

Official examples

Template:Anchor

minecraft:component

Template:Arg desc

Official examples

Template:Anchor

minecraft:dimension

Template:Arg desc

Official examples

Template:Anchor

minecraft:entity

Template:Arg desc

Each entity argument may place limits on the number of entities (single/multiple) selected or the type of entities (player/any entity) selected.

Official examples

JSON properties in command syntax output

Template:Nbt: The root properties object.
- Template:Nbt: The amount of entities that can be selected. Can be Template:Cd or Template:Cd.
- Template:Nbt: The target entity type. Can be Template:Cd or Template:Cd.

Template:Anchor

minecraft:entity_anchor

Template:Arg desc

Official examples

Template:Anchor

minecraft:float_range

Template:Arg desc

Official examples

Template:Anchor

minecraft:function

Template:Arg desc

Official examples

Template:Anchor

minecraft:game_profile

Template:Arg desc

Official examples

Template:Anchor

minecraft:gamemode

Template:Arg desc

Official examples

Template:Anchor

minecraft:heightmap

Template:Arg desc

Official examples

Template:Anchor

minecraft:int_range

Template:Arg desc

Official examples

Template:Anchor

minecraft:item_predicate

The format of item_predicate parameters is <item_type>[<list of tests>], in which the list of tests with [] can be omitted when not needed.

<item_type> is required.
- It can be in the format of resource location (if namespace isn't set it defaults to minecraft:).
- It can also be the resource location of a block tag or item tag with the prefix of #, such as #minecraft:planks.
- It can also be a wildcard character * to match any item type.
The list of tests is optional. Test entries are inside [] and separated with <separator>.
A test entry can be:
- <component_id> - Checks if a component exists.
  - <component_id> is the ID of a data component.
- <component_id>=<value> - Matches exact value of a component.
  - <value> is a representation of component value in SNBT format.
- <predicate_id>~<value> - Checks an item sub-predicate
  - <predicate_id> is the ID of an item sub-predicate.
  - <value> is a representation of item sub-predicate in SNBT format.
  - Example: *[damage~{durability:{min:3}}] matches any stack with at least 3 uses left.
- minecraft:count - Matches the stack size.
  - count - Always passes.
  - count=<positive_int> - Passes only when the stack size equals to the given value.
  - count~<positive_int> - Passes only when the stack size equals to the given value.
  - count~<int_range> - Passes when the stack size is in the specified range.
    - <int_range> is an SNBT of {min:<min value>, max:<max value>}. Both min and max are optional.
  - Example: *[count~{max:2}] matches any stack with count <= 2.
- Any test entry above can be negated by prefixing with !.
  - Example: *[!count=1] matches any stack that has count other than 1.
A <separator> can be:
- | - Logical OR.
- , - Logical AND.
- Unlike most programming languages, the precedence of | (Logical OR) is higher than , (Logical AND).
- That means tests entries joined with | are treated as a single entry to check multiple alternatives.
- Example: *[!damage|damage=0, count=1] looks for items without damage component or with 0 damage, and its count must be 1.

Official examples

Template:Anchor

minecraft:item_slot

Template:Arg desc

Official examples

Template:Anchor

minecraft:item_slots

Template:Arg desc

Official examples

Template:Anchor

minecraft:item_stack

The format of item_stack is <item_id>[<list of components>], in which the list of components with [] can be omitted when not needed.

<item_id> is required, and it should be in the format of resource location (if namespace isn't set it defaults to minecraft:).
The list of data components is optional. Data component entries are inside [] separated with ,.
- A data component entry can be:
  - <component_id>=<value> - Sets value of a data component.
    - <component_id> is the ID of a data component.
    - <value> is a representation of component value in SNBT format.
  - !<component_id> - Removes a default data component of the item.
When giving items, any components provided are set or removed, but anything omitted retain their default values, depending on the item type.

Official examples

Template:Anchor

minecraft:loot_modifier

Template:Arg desc

Official examples

Template:Anchor

minecraft:loot_predicate

Template:Arg desc

Official examples

Template:Anchor

minecraft:loot_table

Template:Arg desc

Official examples

Template:Anchor

minecraft:message

Template:Arg desc

Official examples

Template:Anchor

minecraft:nbt_compound_tag

Template:Arg desc

Official examples

{}
{foo:bar}

Template:Anchor

minecraft:nbt_path

Template:Arg desc

An example

Template:Cd

Template:Cd
- Template:Cd
  - <the first list element>
    - Template:Cd
      - Template:Cd
  - <the second list element>

Official examples

Template:Anchor

minecraft:nbt_tag

Template:Arg desc

Official examples

Template:Anchor

minecraft:objective

Template:Arg desc

Official examples

Template:Anchor

minecraft:objective_criteria

Template:Arg desc

Official examples

Template:Anchor

minecraft:operation

Template:Arg desc

Official examples

Template:Anchor

minecraft:particle

Template:Arg desc

Official examples

Template:Anchor

minecraft:resource

Template:Arg desc

Official examples

JSON properties in command syntax output

Template:Nbt: The root properties object.
- Template:Nbt: The registry ID.

Template:Anchor

minecraft:resource_key

Template:Arg desc

Official examples

JSON properties in command syntax output

Template:Nbt: The root properties object.
- Template:Nbt: The registry ID.

Template:Anchor

minecraft:resource_location

Template:Arg desc It is resolved during command execution into the unregistered content, or sent to the client to resolve into a client-side content.

Official examples

Template:Anchor

minecraft:resource_or_tag

Template:Arg desc

Official examples

JSON properties in command syntax output

Template:Nbt: The root properties object.
- Template:Nbt: The registry ID.

Template:Anchor

minecraft:resource_or_tag_key

Template:Arg desc

Official examples

JSON properties in command syntax output

Template:Nbt: The root properties object.
- Template:Nbt: The registry ID.

Template:Anchor

minecraft:resource_selector

Similar to resouce_location except enables the use of wildcard characters.

* - matches from 0 to any number of characters
? - matches exactly one character

Official examples

Template:Cd - matches all IDs
Template:Cd - matches everthing in the minecraft namespace
Template:Cd - matches IDs in the folder subfolder in the custom namespace that end in _test_ followed by one additional character.

Template:Anchor

minecraft:rotation

Template:Arg desc

Official examples

Template:Anchor

minecraft:score_holder

Template:Arg desc

Each score holder argument may specify if it can select only one score holder or multiple score holders.

Examples

Official examples

JSON properties in command syntax output

Template:Nbt: The root properties object.
- Template:Nbt: The amount of score holders that can be selected. Can be Template:Cd or Template:Cd.

Template:Anchor

minecraft:scoreboard_slot

Template:Arg desc

Official examples

Template:Anchor

minecraft:style

Template:Arg desc

Official examples

Template:Cd

Template:Anchor

minecraft:swizzle

Template:Arg desc

Official examples

Template:Anchor

minecraft:team

Template:Arg desc

Official examples

Template:Anchor

minecraft:template_mirror

Template:Arg desc

Official examples

Template:Anchor

minecraft:template_rotation

Template:Arg desc

Official examples

Template:Anchor

minecraft:time

Template:Arg desc

Official examples

JSON properties in command syntax output

Template:Nbt: The root properties object.
- Template:Nbt: The minimum time in game ticks.

Template:Anchor

minecraft:uuid

Template:Arg desc

Official examples

Template:Cd

Template:Anchor

minecraft:vec2

Template:Arg desc

Official examples

Template:Anchor

minecraft:vec3

Template:Arg desc

Official examples

Removed

Template:Anchor

minecraft:entity_summon

Template:Arg desc

Official examples

Template:Anchor

minecraft:item_enchantment

Template:Arg desc

Official examples

Template:Anchor

minecraft:mob_effect

Template:Arg desc

Official examples

Bedrock Edition

Template:Update

BlockStateCommandParam

Also known as BLOCK_STATE_ARRAY.

Template:Arg desc

CommandCompareOperator

Also known as COMPAREOPERATOR.

Template:Arg desc

CommandFilePath

Also known as PATHCOMMAND.

Template:Arg desc

CommandIntegerRange

Also known as FULLINTEGERRANGE.

Template:Arg desc

CommandMessage

Also known as MESSAGE_ROOT.

Template:Arg desc

CommandOperator

Also known as OPERATOR.

Template:Arg desc

CommandPosition

Also known as POSITION.

Template:Arg desc

CommandPositionFloat

Also known as POSITION_FLOAT.

Template:Arg desc

CommandRawText

Also known as RAWTEXT.

Template:Arg desc Template:Anchor Template:Anchor

CommandSelector<Actor> and CommandSelector<Player>

Also known as SELECTION.

CommandSelector<Actor> is used to specify entities. Template:Arg desc

CommandSelector<Player> is used to specify players. Template:Arg desc

CommandWildcardInt

Also known as WILDCARDINT.

Must be a 32-bit integer, or an asterisk (Template:Cd) to represent MIN_INT(-2,147,483,648),

float

Also known as VAL.

Template:Arg desc

int

Also known as INT.

Template:Arg desc

Json::Value

Also known as JSON_OBJECT.

Template:Arg desc

RelativeFloat

Also known as RVAL.

Template:Arg desc Template:Anchor

std::basic_string

Also known as ID.

Template:Arg desc Template:Anchor

std::unique_ptr<Command>

Also known as SLASHCOMMAND.

Represents a complete command.

WildcardCommandSelector<Actor>

Also known as WILDCARDSELECTION.

Template:Arg desc Template:Anchor

Enum

Must be an unquoted string without space.

History

Template:Missing information Template:HistoryTable

References

Navigation

Template:Navbox commands

fr:Types d'arguments ja:引数の型 lzh:附項之類 pt:Tipos de argumentos ru:Типы аргументов zh:参数类型

@@ Line 92: / Line 92: @@
 {{Arg desc|je=long}}
-Note: Although a long argument type is present in [[Minecraft:brigadier]], it is not used by ''Minecraft''.
+Note: Although a long argument type is present in brigadier, it is not used by ''Minecraft''.
 Each long argument type may have a custom minimum and maximum value.
@@ Line 169: / Line 169: @@
 The format of block_predicate parameters is <code>''block_id''[''block_states'']{''data_tags''}</code>, in which block states and data tags can be omitted when they are not needed.
-* <code>block_id</code> is required, and it should be in the format of [[Minecraft:resource location]](if namespace isn't set it defaults to <code>minecraft:</code>).
+* <code>block_id</code> is required, and it should be in the format of resource location(if namespace isn't set it defaults to <code>minecraft:</code>).
-** It can also be the resource location of a [[Minecraft:Tags|block tag]] prefixed with <code>#</code>, such as <code>#minecraft:planks</code>.
+** It can also be the resource location of a block tag prefixed with <code>#</code>, such as <code>#minecraft:planks</code>.
-* [[Minecraft:Block state]]s are inside <code>[]</code>, comma-separated and properties and values must be supported by the block or all blocks in the tag. They are optional.
+* Block states are inside <code>[]</code>, comma-separated and properties and values must be supported by the block or all blocks in the tag. They are optional.
 ** <code>minecraft:stone[doesntexist=purpleberry]</code> is unparseable, because <code>stone</code> doesn't have <code>doesntexist</code>.
 ** <code>minecraft:redstone_wire[power=tuesday]</code> is unparseable, because <code>redstone_wire</code>'s <code>power</code> is a number between 0 and 15.
-* [[Minecraft:NBT format|Data tags]] are inside <code>{}</code>. They are optional.
+* Data tags are inside <code>{}</code>. They are optional.
 * When test for block, only the states provided are tested.
 ** If a command tests for <code>redstone_wire[power=15]</code>, it checks only power, but ignores other states such as <code>north</code>.
@@ Line 192: / Line 192: @@
 The format of block_state parameters is <code>''block_id''[''block_states'']{''data_tags''}</code>, in which block states and data tags can be omitted when they are not needed.
-* <code>block_id</code> is required, and it should be in the format of [[Minecraft:resource location]] (if namespace isn't set it defaults to <code>minecraft:</code>).
+* <code>block_id</code> is required, and it should be in the format of resource location (if namespace isn't set it defaults to <code>minecraft:</code>).
-* [[Minecraft:Block state]]s are inside <code>[]</code>, comma-separated and must be properties/values supported by the blocks. They are optional.
+* Block states are inside <code>[]</code>, comma-separated and must be properties/values supported by the blocks. They are optional.
 ** <code>minecraft:stone[doesntexist=purpleberry]</code> is unparseable, because <code>stone</code> doesn't have <code>doesntexist</code>.
 ** <code>minecraft:redstone_wire[power=tuesday]</code> is unparseable, because <code>redstone_wire</code>'s <code>power</code> is a number between 0 and 15.
-* [[Minecraft:NBT format|Data tags]] are inside <code>{}</code>. They are optional.
+* Data tags are inside <code>{}</code>. They are optional.
 * When placing blocks, any states provided are set, but anything omitted retain their default values, depending on the block type.
 ** If a command sets <code>redstone_wire[power=15]</code>, it is set <code>power</code> to 15, but <code>north</code> is a default value (in this case, set to <code>none</code>).
@@ Line 360: / Line 360: @@
 The format of item_predicate parameters is <code><''item_type''>[<''list of tests''>]</code>, in which the list of tests with <code>[]</code> can be omitted when not needed.
 * <code><''item_type''></code> is required.
-** It can be in the format of [[Minecraft:resource location]] (if namespace isn't set it defaults to <code>minecraft:</code>).
+** It can be in the format of resource location (if namespace isn't set it defaults to <code>minecraft:</code>).
-** It can also be the resource location of a [[Minecraft:Tags|block tag or item tag]] with the prefix of <code>#</code>, such as <code>#minecraft:planks</code>.
+** It can also be the resource location of a block tag or item tag with the prefix of <code>#</code>, such as <code>#minecraft:planks</code>.
 ** It can also be a wildcard character <code>*</code> to match any item type.
 * The list of tests is optional. Test entries are inside <code>[]</code> and separated with <code><''separator''></code>.
 * A test entry can be:
 ** <code><''component_id''></code> - Checks if a component exists.
-*** <code><''component_id''></code> is the ID of a [[Minecraft:data component]].
+*** <code><''component_id''></code> is the ID of a data component.
 ** <code><''component_id''>=<''value''></code> - Matches exact value of a component.
 *** <code><''value''></code> is a representation of component value in SNBT format.
 ** <code><''predicate_id''>~<''value''></code> - Checks an item sub-predicate
-*** <code><''predicate_id''></code> is the ID of an [[Minecraft:item sub-predicate]].
+*** <code><''predicate_id''></code> is the ID of an item sub-predicate.
 *** <code><''value''></code> is a representation of item sub-predicate in SNBT format.
 *** Example: <code>*[damage~{durability:{min:3}}]</code> matches any stack with at least 3 uses left.
@@ Line 424: / Line 424: @@
 === minecraft:item_stack ===
 The format of item_stack is <code><''item_id''>[<''list of components''>]</code>, in which the list of components with <code>[]</code> can be omitted when not needed.
-* <code><''item_id''></code> is required, and it should be in the format of [[Minecraft:resource location]] (if namespace isn't set it defaults to <code>minecraft:</code>).
+* <code><''item_id''></code> is required, and it should be in the format of resource location (if namespace isn't set it defaults to <code>minecraft:</code>).
-* The list of [[Minecraft:Data component format|data components]] is optional. Data component entries are inside <code>[]</code> separated with <code>,</code>.
+* The list of data components is optional. Data component entries are inside <code>[]</code> separated with <code>,</code>.
 ** A data component entry can be:
 *** <code><''component_id''>=<''value''></code> - Sets value of a data component.
-**** <code><''component_id''></code> is the ID of a [[Minecraft:data component]].
+**** <code><''component_id''></code> is the ID of a data component.
 **** <code><''value''></code> is a representation of component value in SNBT format.
 *** <code>!<''component_id''></code> - Removes a default data component of the item.
@@ Line 964: / Line 964: @@
 {{HistoryTable
 |{{HistoryLine|java}}
-|{{HistoryLine||1.13|dev=17w45a|[[Minecraft:Command]] arguments are now handled with Brigadier.}}
+|{{HistoryLine||1.13|dev=17w45a|Command arguments are now handled with Brigadier.}}
 |{{HistoryLine||1.14|dev=19w08a|Now allows single quotes for strings in commands.<ref>{{Link|url=https://github.com/Mojang/brigadier/pull/52|title=Allow single quote in strings by boq · Pull Request #52 |website=Mojang/brigadier – GitHub}}</ref>}}
 |{{HistoryLine||1.16|dev=20w17a|Added <code>minecraft:uuid</code> argument type.}}
@@ Line 978: / Line 978: @@
 |{{HistoryLine||1.19|dev=22w11a|Now <code>minecraft:item_predicate</code> and <code>minecraft:block_predicate</code> require tag to exist when parsing instead of executing.<ref>{{bug|MC-124984|resolution=Fixed}}</ref>}}
 |{{HistoryLine|||dev=22w19a|Added <code>minecraft:template_mirror</code> and <code>minecraft:template_rotation</code> argument types.}}
-|{{HistoryLine||1.19.3|dev=22w42a|Added <code>minecraft:resource_key</code> and <code>minecraft:resource_or_tag_key</code> argument types, which are used for reloadable registry entries (i.e. [[Minecraft:Resource location#Registered pack contents|registered pack contents]]).
+|{{HistoryLine||1.19.3|dev=22w42a|Added <code>minecraft:resource_key</code> and <code>minecraft:resource_or_tag_key</code> argument types, which are used for reloadable registry entries (i.e. registered pack contents).
 |Now <code>minecraft:resource</code> and <code>minecraft:resource_or_tag</code> are used only for un-reloadable registry entries.
 |Removed <code>minecraft:mob_effect</code>, <code>minecraft:entity_summon</code> and <code>minecraft:item_enchantment</code> argument types. Replaced by <code>minecraft:resource</code>.}}
@@ Line 997: / Line 997: @@
 [[Category:Commands]]
-[[Minecraft:fr:Types d'arguments]]
+fr:Types d'arguments
-[[Minecraft:ja:引数の型]]
+ja:引数の型
-[[Minecraft:lzh:附項之類]]
+lzh:附項之類
-[[Minecraft:pt:Tipos de argumentos]]
+pt:Tipos de argumentos
-[[Minecraft:ru:Типы аргументов]]
+ru:Типы аргументов
-[[Minecraft:zh:参数类型]]
+zh:参数类型