SyncBot: Sync: updated from Minecraft

2026-05-24T11:02:39Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:02, 24 May 2026
Line 361:		Line 361:
	* <code><''item_type''></code> is required.		* <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 [[Minecraft: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 [[Minecraft:Tag (Java Edition)\|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.		** 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>.		* The list of tests is optional. Test entries are inside <code>[]</code> and separated with <code><''separator''></code>.

SyncBot: Sync: updated from Minecraft

2026-05-13T11:02:10Z

Sync: updated from Minecraft

Show changes

SyncBot: Fix template calls: add MC/ prefix

2026-04-09T19:01:38Z

Fix template calls: add MC/ prefix

Show changes

SyncBot: Remove broken links to missing pages

2026-04-09T15:19:09Z

Remove broken links to missing pages

imported>VECthba: /* Navigation */

2026-03-29T02:41:04Z

Navigation

Show changes

← Older revision		Revision as of 15:19, 9 April 2026
Line 92:		Line 92:
	{{Arg desc\|je=long}}		{{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.		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.		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: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.		** <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.		* 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>.		** 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.		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: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.		** <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.		* 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>).		** 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.		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.		* <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.		** 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>.		* The list of tests is optional. Test entries are inside <code>[]</code> and separated with <code><''separator''></code>.
	* A test entry can be:		* A test entry can be:
	** <code><''component_id''></code> - Checks if a component exists.		** <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><''component_id''>=<''value''></code> - Matches exact value of a component.
	*** <code><''value''></code> is a representation of component value in SNBT format.		*** <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''>~<''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.		*** <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.		*** Example: <code>*[damage~{durability:{min:3}}]</code> matches any stack with at least 3 uses left.
Line 424:		Line 424:
	=== minecraft:item_stack ===		=== 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.		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:		** A data component entry can be:
	*** <code><''component_id''>=<''value''></code> - Sets value of a data component.		*** <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><''value''></code> is a representation of component value in SNBT format.
	*** <code>!<''component_id''></code> - Removes a default data component of the item.		*** <code>!<''component_id''></code> - Removes a default data component of the item.
Line 964:		Line 964:
	{{HistoryTable		{{HistoryTable
	\|{{HistoryLine\|java}}		\|{{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.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.}}		\|{{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\|\|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\|\|\|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.		\|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>.}}		\|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]]		[[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:参数类型

Minecraft:Argument types - Revision history

SyncBot: Sync: updated from Minecraft

SyncBot: Sync: updated from Minecraft

SyncBot: Fix template calls: add MC/ prefix

SyncBot: Remove broken links to missing pages

imported>VECthba: /* Navigation */