Minecraft:Function (Bedrock Edition) - Revision history

SyncBot: Fix template calls: add MC/ prefix

2026-04-09T20:25:14Z

Fix template calls: add MC/ prefix

← Older revision		Revision as of 20:25, 9 April 2026
Line 1:		Line 1:
	{{about\|functions {{in\|BE}}\|the corresponding feature {{in\|JE}}\|Function (Java Edition)\|other uses\|Function}}		{{about\|functions {{MC/In\|BE}}\|the corresponding feature {{MC/In\|JE}}\|Function (Java Edition)\|other uses\|Function}}
	'''Functions''' allow players to run lists of commands using text files with the extension <code>.mcfunction</code>. This page covers how to use functions {{in\|BE}}.		'''Functions''' allow players to run lists of commands using text files with the extension <code>.mcfunction</code>. This page covers how to use functions {{MC/In\|BE}}.

	== Usage ==		== Usage ==
	Text files must be placed into a top-level folder named "functions" within a [[Minecraft:behavior pack]], located at {{mono\|behavior_packs/[''behavior_pack'']/functions}}. Subfolders can also be added to this folder. For example, running the function <code>sub/foo</code> runs the file located at {{mono\|[''behavior_pack'']/functions/sub/foo.mcfunction}}.		Text files must be placed into a top-level folder named "functions" within a [[Minecraft:behavior pack]], located at {{mono\|behavior_packs/[''behavior_pack'']/functions}}. Subfolders can also be added to this folder. For example, running the function <code>sub/foo</code> runs the file located at {{mono\|[''behavior_pack'']/functions/sub/foo.mcfunction}}.

	=== {{~~cmd~~\|reload}} ===		=== {{MC/Cmd\|reload}} ===
	'''Note:''' Currently {{~~cmd~~\|reload}} reloads only functions that already exist at the time the game is launched, meaning changes can be made to existing functions but the game must be restarted for newly added functions.		'''Note:''' Currently {{MC/Cmd\|reload}} reloads only functions that already exist at the time the game is launched, meaning changes can be made to existing functions but the game must be restarted for newly added functions.

	=== Success results ===		=== Success results ===
Line 14:		Line 14:
	Within the <code>.mcfunction</code> file, one valid command is placed per line, without the usual forward slash <code>/</code>. Players can add comments within the function text file by preceding them with a <code>#</code>.		Within the <code>.mcfunction</code> file, one valid command is placed per line, without the usual forward slash <code>/</code>. Players can add comments within the function text file by preceding them with a <code>#</code>.

	=== {{cd\|min_engine_version}} ===		=== {{MC/Cd\|min_engine_version}} ===
	Functions require a minimum engine version specified in the pack {{cd\|manifest.json}} file.		Functions require a minimum engine version specified in the pack {{MC/Cd\|manifest.json}} file.

	This field determines which version of a command to run. The number specified here should match the version number of the game. For example, {{~~cmd~~\|fill}} was changed in <code>[[Minecraft:Bedrock Edition 1.19.70\|1.19.70]]</code>. If your behavior pack has <code>"min_engine_version": [1, 19, 10]</code> and runs a function that contains {{~~cmd~~\|fill}}, it runs the older version of fill (as if the version was still <code>[[Minecraft:Bedrock Edition 1.19.10\|1.19.10]]</code>).		This field determines which version of a command to run. The number specified here should match the version number of the game. For example, {{MC/Cmd\|fill}} was changed in <code>[[Minecraft:Bedrock Edition 1.19.70\|1.19.70]]</code>. If your behavior pack has <code>"min_engine_version": [1, 19, 10]</code> and runs a function that contains {{MC/Cmd\|fill}}, it runs the older version of fill (as if the version was still <code>[[Minecraft:Bedrock Edition 1.19.10\|1.19.10]]</code>).

	==== Manifest example ====		==== Manifest example ====
Line 67:		Line 67:

	=== Commands ===		=== Commands ===
	==== {{~~cmd~~\|function}} ====		==== {{MC/Cmd\|function}} ====
	* Allows players to run a function once.		* Allows players to run a function once.
	* The commands in the function are run through the entity or command block that ran the <code>/function</code> command.		* The commands in the function are run through the entity or command block that ran the <code>/function</code> command.
Line 74:		Line 74:
	<div class="treeview">		<div class="treeview">
	==== Command syntax ====		==== Command syntax ====
	*{{~~nbt~~\|compound}} The root object.		*{{MC/Nbt\|compound}} The root object.
	**{{~~nbt~~\|list\|values}}: A list of functions.		**{{MC/Nbt\|list\|values}}: A list of functions.
	***{{~~nbt~~\|string}}: A function.		***{{MC/Nbt\|string}}: A function.

	=== tick.json ===		=== tick.json ===
Line 84:		Line 84:
	== History ==		== History ==
	{{HistoryTable		{{HistoryTable
	\|{{HistoryLine\|bedrock}}		\|{{MC/HistoryLine\|bedrock}}
	\|{{HistoryLine\|\|1.8.0\|dev=beta 1.8.0.8\|Added function files.\|Function files are available only in behavior packs.}}		\|{{MC/HistoryLine\|\|1.8.0\|dev=beta 1.8.0.8\|Added function files.\|Function files are available only in behavior packs.}}
	\|{{HistoryLine\|\|1.13.0\|dev=beta 1.13.0.1\|Function files are now visible in command list.}}		\|{{MC/HistoryLine\|\|1.13.0\|dev=beta 1.13.0.1\|Function files are now visible in command list.}}
	}}		}}

	== Navigation ==		== Navigation ==
	{{Navbox Bedrock Edition}}		{{MC/Navbox Bedrock Edition}}

	ja:関数 (Bedrock Edition)		ja:関数 (Bedrock Edition)

SyncBot: Remove broken links to missing pages

2026-04-09T15:50:28Z

Remove broken links to missing pages

← Older revision		Revision as of 15:50, 9 April 2026
Line 51:		Line 51:

	=== More complex function example ===		=== More complex function example ===
	This function builds a basic house around the executor. Note that because the function runs commands in order, the [[Minecraft:glass]] windows and ~~[[Minecraft:~~spruce door]] replace the walls created by the first command.		This function builds a basic house around the executor. Note that because the function runs commands in order, the [[Minecraft:glass]] windows and spruce door replace the walls created by the first command.

	<pre>fill ~-2 ~-1 ~-2 ~2 ~2 ~2 stone_bricks 0 hollow		<pre>fill ~-2 ~-1 ~-2 ~2 ~2 ~2 stone_bricks 0 hollow
Line 79:		Line 79:

	=== tick.json ===		=== tick.json ===
	*The '''tick.json''' file is also located in the {{mono\|behavior_packs/[''behavior_pack'']/functions}} folder, specifying functions to be executed on every ~~[[Minecraft:~~game tick]]. Functions running in this file are executed by the server at origin 0, 0, 0 in the overworld. Functions in this file are executed as soon as the world is initialized, regardless of whether or not the player has been loaded.		*The '''tick.json''' file is also located in the {{mono\|behavior_packs/[''behavior_pack'']/functions}} folder, specifying functions to be executed on every game tick. Functions running in this file are executed by the server at origin 0, 0, 0 in the overworld. Functions in this file are executed as soon as the world is initialized, regardless of whether or not the player has been loaded.
	</div>		</div>

Line 92:		Line 92:
	{{Navbox Bedrock Edition}}		{{Navbox Bedrock Edition}}

	~~[[Minecraft:~~ja:関数 (Bedrock Edition)]]		ja:関数 (Bedrock Edition)
	~~[[Minecraft:~~pt:Funções (Edição Bedrock)]]		pt:Funções (Edição Bedrock)
	~~[[Minecraft:~~uk:Функція (Bedrock Edition)]]		uk:Функція (Bedrock Edition)
	~~[[Minecraft:~~zh:基岩版函数]]		zh:基岩版函数

~2026-DolphinMeadowSnow8508: Added more links.

2026-04-05T13:18:41Z

Added more links.

New page

{{about|functions {{in|BE}}|the corresponding feature {{in|JE}}|Function (Java Edition)|other uses|Function}}
'''Functions''' allow players to run lists of commands using text files with the extension <code>.mcfunction</code>. This page covers how to use functions {{in|BE}}.

== Usage ==
Text files must be placed into a top-level folder named "functions" within a [[Minecraft:behavior pack]], located at {{mono|behavior_packs/[''behavior_pack'']/functions}}. Subfolders can also be added to this folder. For example, running the function <code>sub/foo</code> runs the file located at {{mono|[''behavior_pack'']/functions/sub/foo.mcfunction}}.

=== {{cmd|reload}} ===
'''Note:''' Currently {{cmd|reload}} reloads only functions that already exist at the time the game is launched, meaning changes can be made to existing functions but the game must be restarted for newly added functions.

=== Success results ===
Upon successfully running a function, a message displays in chat: "Successfully executed {{mono|[''amount'']}} function entries."

== Function syntax ==
Within the <code>.mcfunction</code> file, one valid command is placed per line, without the usual forward slash <code>/</code>. Players can add comments within the function text file by preceding them with a <code>#</code>.

=== {{cd|min_engine_version}} ===
Functions require a minimum engine version specified in the pack {{cd|manifest.json}} file.

This field determines which version of a command to run. The number specified here should match the version number of the game. For example, {{cmd|fill}} was changed in <code>[[Minecraft:Bedrock Edition 1.19.70|1.19.70]]</code>. If your behavior pack has <code>"min_engine_version": [1, 19, 10]</code> and runs a function that contains {{cmd|fill}}, it runs the older version of fill (as if the version was still <code>[[Minecraft:Bedrock Edition 1.19.10|1.19.10]]</code>).

==== Manifest example ====
A manifest is required for [[Minecraft:Add-on|Add-Ons]], behaviour packs and resource packs to work. Note that the three dots <code>...</code> must be replaced with an actual UUID, which can be generated with a UUID generator like [https://www.uuidtools.com/minecraft UUIDTools.com].<pre>{
"format_version": 3,
"header": {
"name": "House Building Add-On",
"description": "Let the game build houses for you using this Add-On",
"uuid": "...",
"version": "1.0.0",
"min_engine_version": "1.26.10"
},
"modules": [
{
"type": "data",
"uuid": "...",
"version": "1.0.0"
}
],
"metadata": {
"authors": ["Minecraft Wiki"],
"product_type": "addon"
}
}</pre>
=== Simple function example ===

<pre>
title @p title Test
setblock ~ ~2 ~ sulfur_bricks
say Test
<nowiki>#</nowiki>this is a comment
</pre>

=== More complex function example ===
This function builds a basic house around the executor. Note that because the function runs commands in order, the [[Minecraft:glass]] windows and [[Minecraft:spruce door]] replace the walls created by the first command.

<pre>fill ~-2 ~-1 ~-2 ~2 ~2 ~2 stone_bricks 0 hollow
fill ~-2 ~-1 ~-2 ~2 ~-1 ~2 spruce_planks
fill ~ ~ ~2 ~ ~ ~2 spruce_door 1
fill ~-2 ~1 ~ ~-2 ~1 ~ glass
fill ~2 ~1 ~ ~2 ~1 ~ glass
fill ~ ~1 ~-2 ~ ~1 ~-2 glass</pre>

== Running a function ==
Functions attempt to run all commands within a single tick, including the commands of nested functions called within another function.

=== Limits ===
A single function call runs up to 10,000 commands (including calls to other functions, i.e. recursion).

=== Commands ===
==== {{cmd|function}} ====
* Allows players to run a function once.
* The commands in the function are run through the entity or command block that ran the <code>/function</code> command.
* Syntax: <code>/function <path/to/function/file></code>

<div class="treeview">
==== Command syntax ====
*{{nbt|compound}} The root object.
**{{nbt|list|values}}: A list of functions.
***{{nbt|string}}: A function.

=== tick.json ===
*The '''tick.json''' file is also located in the {{mono|behavior_packs/[''behavior_pack'']/functions}} folder, specifying functions to be executed on every [[Minecraft:game tick]]. Functions running in this file are executed by the server at origin 0, 0, 0 in the overworld. Functions in this file are executed as soon as the world is initialized, regardless of whether or not the player has been loaded.
</div>

== History ==
{{HistoryTable
|{{HistoryLine|bedrock}}
|{{HistoryLine||1.8.0|dev=beta 1.8.0.8|Added function files.|Function files are available only in behavior packs.}}
|{{HistoryLine||1.13.0|dev=beta 1.13.0.1|Function files are now visible in command list.}}
}}

== Navigation ==
{{Navbox Bedrock Edition}}

[[Minecraft:ja:関数 (Bedrock Edition)]]
[[Minecraft:pt:Funções (Edição Bedrock)]]
[[Minecraft:uk:Функція (Bedrock Edition)]]
[[Minecraft:zh:基岩版函数]]