Minecraft:Ticking area - Revision history

SyncBot: Fix template calls: add MC/ prefix

2026-04-09T21:03:23Z

Fix template calls: add MC/ prefix

← Older revision		Revision as of 21:03, 9 April 2026
Line 1:		Line 1:
	{{about\|the {{BE}} mechanic that keeps certain chunks updated continuously\|the command in {{JE}}\|Commands/forceload}}		{{about\|the {{MC/BE}} mechanic that keeps certain chunks updated continuously\|the command in {{MC/JE}}\|Commands/forceload}}
	{{Exclusive\|bedrock\|education}}		{{MC/Exclusive\|bedrock\|education}}

	A '''ticking area''' is a player-specified group of chunks that continues to be updated even when there is no player nearby. Because the chunks remain active, processes such as growth, decay, spawning, movement, and [[Minecraft:redstone]] operations aren't suspended in them when no players are present, provided at least one player remains somewhere in the [[Minecraft:dimension]].		A '''ticking area''' is a player-specified group of chunks that continues to be updated even when there is no player nearby. Because the chunks remain active, processes such as growth, decay, spawning, movement, and [[Minecraft:redstone]] operations aren't suspended in them when no players are present, provided at least one player remains somewhere in the [[Minecraft:dimension]].
Line 41:		Line 41:

	== Spawning ==		== Spawning ==
	{{~~main~~\|Mob spawning}}		{{MC/Main\|Mob spawning}}

	Mob spawning does not occur in ticking area chunks without the presence of a player, as all forms of mob spawning attempts are done in a radius centered on a player. However, when a player is present in those chunks, the ticking area does not prevent mob spawning. Zombified piglins spawning from portals is an exception; it solely relies on randomtickspeed.		Mob spawning does not occur in ticking area chunks without the presence of a player, as all forms of mob spawning attempts are done in a radius centered on a player. However, when a player is present in those chunks, the ticking area does not prevent mob spawning. Zombified piglins spawning from portals is an exception; it solely relies on randomtickspeed.
Line 47:		Line 47:
	== Creation and management ==		== Creation and management ==

	A player creates and manages ticking areas by executing a {{~~cmd~~\|tickingarea}} command. Up to ten ticking areas, each containing up to 100 chunks, can exist at one time in a world. Note that commands can be used in a world only if cheats are enabled. This makes the world ineligible for earning achievements, so ticking areas and earning achievements are mutually exclusive.		A player creates and manages ticking areas by executing a {{MC/Cmd\|tickingarea}} command. Up to ten ticking areas, each containing up to 100 chunks, can exist at one time in a world. Note that commands can be used in a world only if cheats are enabled. This makes the world ineligible for earning achievements, so ticking areas and earning achievements are mutually exclusive.

	To create a ticking area, specify its location and size in a {{~~cmd~~\|tickingarea add}} command. There are two forms:		To create a ticking area, specify its location and size in a {{MC/Cmd\|tickingarea add}} command. There are two forms:
	* In the first form, specify two pairs of coordinates in the world. The coordinates specify the opposite corners—either northeast and southwest or northwest and southeast—of the ticking area.		* In the first form, specify two pairs of coordinates in the world. The coordinates specify the opposite corners—either northeast and southwest or northwest and southeast—of the ticking area.
	* In the second form, specify a center coordinate and a radius of 1 to 4 chunks. Although these arguments suggest a circular area, in actuality the ticking area includes all chunks within 'r' chunks, ''including diagonally'', of the chunk containing the center. This defines a square whose sides are twice the given radius + 1. For example, specifying a radius of 2 results in a square ticking area 5 chunks on a side.		* In the second form, specify a center coordinate and a radius of 1 to 4 chunks. Although these arguments suggest a circular area, in actuality the ticking area includes all chunks within 'r' chunks, ''including diagonally'', of the chunk containing the center. This defines a square whose sides are twice the given radius + 1. For example, specifying a radius of 2 results in a square ticking area 5 chunks on a side.
Line 56:		Line 56:
	Note that the Y coordinate is checked for validity but otherwise ignored. This is because a chunk encompasses an entire column of blocks from the bottom of the world to its top, so it includes every possible Y value.		Note that the Y coordinate is checked for validity but otherwise ignored. This is because a chunk encompasses an entire column of blocks from the bottom of the world to its top, so it includes every possible Y value.

	To display a list of current ticking areas, execute a {{~~cmd~~\|tickingarea list}} command. This shows each ticking area's name (if provided) and corner coordinates (for the first form) or center coordinates and radius (for the second form). The coordinates shown in the list may not match those entered because the game adjusts them to the actual corner or center coordinates of a chunk. By default, this command lists only ticking areas in the player's current dimension; the optional <code>all-dimensions</code> argument can be used to see all ticking areas in the world.		To display a list of current ticking areas, execute a {{MC/Cmd\|tickingarea list}} command. This shows each ticking area's name (if provided) and corner coordinates (for the first form) or center coordinates and radius (for the second form). The coordinates shown in the list may not match those entered because the game adjusts them to the actual corner or center coordinates of a chunk. By default, this command lists only ticking areas in the player's current dimension; the optional <code>all-dimensions</code> argument can be used to see all ticking areas in the world.

	To remove a ticking area from the list, execute a {{~~cmd~~\|tickingarea remove}} command specifying either the ticking area's name or the coordinates of a point in the world. Specifying a name deletes only that ticking area. Specify a point deletes all ticking areas in the current dimension containing that point. An optional <code>remove_all</code> argument removes all ticking areas in all dimensions.		To remove a ticking area from the list, execute a {{MC/Cmd\|tickingarea remove}} command specifying either the ticking area's name or the coordinates of a point in the world. Specifying a name deletes only that ticking area. Specify a point deletes all ticking areas in the current dimension containing that point. An optional <code>remove_all</code> argument removes all ticking areas in all dimensions.

	==History==		==History==
	{{HistoryTable		{{HistoryTable
	\|{{HistoryLine\|bedrock}}		\|{{MC/HistoryLine\|bedrock}}
	\|{{HistoryLine\|\|1.2.0\|dev=beta 1.2.0.2\|Added ticking areas.}}		\|{{MC/HistoryLine\|\|1.2.0\|dev=beta 1.2.0.2\|Added ticking areas.}}
	}}		}}

	==Issues==		==Issues==
	{{Issue list\|projects=mcpe}}		{{MC/Issue list\|projects=mcpe}}

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

	fr:Zone persistante		fr:Zone persistante

SyncBot: Remove broken links to missing pages

2026-04-09T16:07:49Z

Remove broken links to missing pages

imported>Aed8814 at 08:33, 1 December 2025

2025-12-01T08:33:07Z

New page

{{about|the {{BE}} mechanic that keeps certain chunks updated continuously|the command in {{JE}}|Commands/forceload}}
{{Exclusive|bedrock|education}}

A '''ticking area''' is a player-specified group of [[Minecraft:chunk]]s that continues to be updated even when there is no player nearby. Because the chunks remain active, processes such as growth, decay, [[Minecraft:Mob spawning|spawn]]ing, movement, and [[Minecraft:redstone]] operations aren't suspended in them when no players are present, provided at least one player remains somewhere in the [[Minecraft:dimension]].

==Behavior==
Normally, only the chunks closely surrounding a player are updated by the game. These chunks are said to be in the player's '''chunk update range'''. As the player moves through the world, new chunks that come into range are added to the list of updated chunks and older chunks that pass out of range are removed. Only the chunks in the list are updated to reflect the passage of time. This means, for instance, that if a player spends time exploring or in another dimension, [[Minecraft:crops]] won't grow and any [[Minecraft:smelting]], or automated [[Minecraft:farming]] underway when the player left remains unfinished when the player returns.

Ticking areas solve this problem by keeping player-designated chunks from being suspended. Each chunk in a ticking area is updated exactly as if it were perpetually in a player's chunk update range.

===Events processed===
The following time-related events occur without interruption in ticking areas, provided there is at least one player in the same dimension (the [[Minecraft:Overworld]], [[Minecraft:The Nether]], or [[Minecraft:The End]]) as the ticking area:
* [[Minecraft:Water]] flows and breaks non-solid blocks.
* [[Minecraft:Lava]] flows, sets fire to nearby [[Minecraft:flammable|flammable blocks]], destroys [[Minecraft:item (entity)|item entities]], and interacts with water.
* [[Minecraft:Fire]] spreads to adjacent flammable blocks.
* Dropped items fall and despawn after 5 minutes if not picked up or collected by a [[Minecraft:hopper]].
* Passive [[Minecraft:mob]]s grow up, and move around normally.
* [[Minecraft:Sheep]] eat [[Minecraft:Grass Block|grass]] and grow [[Minecraft:wool]].
* [[Minecraft:Sand]], [[Minecraft:gravel]], and [[Minecraft:concrete powder]] fall if the block beneath them is moved or broken.
* Primed [[Minecraft:TNT]] falls and explodes.
* [[Minecraft:Minecart]]s function normally.
* [[Minecraft:Redstone]] mechanisms and devices function normally, provided they are entirely contained within ticking areas.
* [[Minecraft:Crops]], [[Minecraft:mushroom]]s, [[Minecraft:sapling]]s, and [[Minecraft:nether wart]] grow to maturity if the circumstances are suitable.
* [[Minecraft:Farmland]] changes its hydration in response to available water.
* [[Minecraft:Leaves]] decay if not connected to a [[Minecraft:log]].
* [[Minecraft:Grass Block|Grass]] and [[Minecraft:mycelium]] spread to adjacent blocks.
* [[Minecraft:Ice]] forms and melts in response to changes in [[Minecraft:light]]ing.
* [[Minecraft:Weather|Rain, snow, and lightning]] occur and have their usual effects.
* Hostile mobs move around as usual.

===Suspended events===

Many of the above events involve entities moving or spreading, which raises the possibility of updates in a ticking area affecting blocks in outside chunks. If an outside chunk is within any player's chunk update range, of course, the chunk is active and these events proceed as usual. However, if the outside chunk is inactive the effects are suspended in most cases. Specifically,
* Flowing water or lava can spread to the first adjacent block in an outside chunk, but the flow becomes suspended there until the outside chunk becomes active.
* Fire can spread to the first adjacent flammable block outside the ticking area. Like water and lava, it becomes suspended there; although visible, its animation does not run and it cannot spread further until the outside chunk becomes active.
* Grass and mycelium can spread to the first adjacent block in an outside chunk, but the affected block does not actually change its appearance until its chunk becomes active; it then changes instantly. Grass and mycelium ''cannot'' spread beyond the first such block, nor from such a block into the ticking area, until the outside chunk becomes active.
* Pumpkin and melon stems growing on the edge of a ticking area can place their fruits on an adjacent block in an outside chunk.
* An entity (mob, minecart, arrow, etc.) that attempts to move into an outside chunk becomes suspended as soon as it leaves the ticking area. It remains visible but motionless. When the outside chunk becomes active, the entity resumes moving.
* Exploding TNT can damage or destroy blocks in an inactive chunk, and unlike other events its effects are not limited to adjacent blocks. However, secondary effects in the outside chunk are suspended until the chunk becomes active. For instance, if an explosion destroys a block that supported sand or gravel, the sand or gravel does not fall immediately. The same thing happens with items that were attached to destroyed blocks, such as item frames and redstone torches; they do not drop until the chunk is activated.
* Primed TNT that has been launched into an inactive chunk is suspended in mid-air within the first outside block it enters. It disappears until the outside chunk becomes active, at which time it resumes its flight and countdown.

== Spawning ==
{{main|Mob spawning}}

Mob spawning does not occur in ticking area chunks without the presence of a player, as all forms of mob spawning attempts are done in a radius centered on a player. However, when a player is present in those chunks, the ticking area does not prevent mob spawning. [[Minecraft:Zombified piglin]]s spawning from portals is an exception; it solely relies on randomtickspeed.

== Creation and management ==

A player creates and manages ticking areas by executing a {{cmd|tickingarea}} [[Minecraft:command]]. Up to ten ticking areas, each containing up to 100 chunks, can exist at one time in a world. Note that commands can be used in a world only if cheats are enabled. This makes the world ineligible for earning [[Minecraft:achievements]], so ticking areas and earning achievements are mutually exclusive.

To create a ticking area, specify its location and size in a {{cmd|tickingarea add}} command. There are two forms:
* In the first form, specify two pairs of coordinates in the world. The coordinates specify the opposite corners—either northeast and southwest or northwest and southeast—of the ticking area.
* In the second form, specify a center coordinate and a radius of 1 to 4 chunks. Although these arguments suggest a circular area, in actuality the ticking area includes all chunks within 'r' chunks, ''including diagonally'', of the chunk containing the center. This defines a square whose sides are twice the given radius + 1. For example, specifying a radius of 2 results in a square ticking area 5 chunks on a side.
Optionally, specify a name for the ticking area to identify it in subsequent commands.

Note that the Y coordinate is checked for validity but otherwise ignored. This is because a chunk encompasses an entire column of blocks from the bottom of the world to its top, so it includes every possible Y value.

To display a list of current ticking areas, execute a {{cmd|tickingarea list}} command. This shows each ticking area's name (if provided) and corner coordinates (for the first form) or center coordinates and radius (for the second form). The coordinates shown in the list may not match those entered because the game adjusts them to the actual corner or center coordinates of a chunk. By default, this command lists only ticking areas in the player's current dimension; the optional <code>all-dimensions</code> argument can be used to see all ticking areas in the world.

To remove a ticking area from the list, execute a {{cmd|tickingarea remove}} command specifying either the ticking area's name or the coordinates of a point in the world. Specifying a name deletes only that ticking area. Specify a point deletes all ticking areas in the current dimension containing that point. An optional <code>remove_all</code> argument removes all ticking areas in all dimensions.

==History==
{{HistoryTable
|{{HistoryLine|bedrock}}
|{{HistoryLine||1.2.0|dev=beta 1.2.0.2|Added ticking areas.}}
}}

==Issues==
{{Issue list|projects=mcpe}}

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

[[Minecraft:fr:Zone persistante]]
[[Minecraft:ja:ティック領域]]
[[Minecraft:pt:Área de marcação]]
[[Minecraft:ru:Активная область]]
[[Minecraft:zh:常加载区域]]

← Older revision		Revision as of 16:07, 9 April 2026
Line 2:		Line 2:
	{{Exclusive\|bedrock\|education}}		{{Exclusive\|bedrock\|education}}

	A '''ticking area''' is a player-specified group of ~~[[Minecraft:chunk]]s~~ that continues to be updated even when there is no player nearby. Because the chunks remain active, processes such as growth, decay, ~~[[Minecraft:Mob~~ spawning~~\|spawn]]ing~~, movement, and [[Minecraft:redstone]] operations aren't suspended in them when no players are present, provided at least one player remains somewhere in the [[Minecraft:dimension]].		A '''ticking area''' is a player-specified group of chunks that continues to be updated even when there is no player nearby. Because the chunks remain active, processes such as growth, decay, spawning, movement, and [[Minecraft:redstone]] operations aren't suspended in them when no players are present, provided at least one player remains somewhere in the [[Minecraft:dimension]].

	==Behavior==		==Behavior==
	Normally, only the chunks closely surrounding a player are updated by the game. These chunks are said to be in the player's '''chunk update range'''. As the player moves through the world, new chunks that come into range are added to the list of updated chunks and older chunks that pass out of range are removed. Only the chunks in the list are updated to reflect the passage of time. This means, for instance, that if a player spends time exploring or in another dimension, ~~[[Minecraft:~~crops]] won't grow and any ~~[[Minecraft:~~smelting]], or automated ~~[[Minecraft:~~farming]] underway when the player left remains unfinished when the player returns.		Normally, only the chunks closely surrounding a player are updated by the game. These chunks are said to be in the player's '''chunk update range'''. As the player moves through the world, new chunks that come into range are added to the list of updated chunks and older chunks that pass out of range are removed. Only the chunks in the list are updated to reflect the passage of time. This means, for instance, that if a player spends time exploring or in another dimension, crops won't grow and any smelting, or automated farming underway when the player left remains unfinished when the player returns.

	Ticking areas solve this problem by keeping player-designated chunks from being suspended. Each chunk in a ticking area is updated exactly as if it were perpetually in a player's chunk update range.		Ticking areas solve this problem by keeping player-designated chunks from being suspended. Each chunk in a ticking area is updated exactly as if it were perpetually in a player's chunk update range.
Line 12:		Line 12:
	The following time-related events occur without interruption in ticking areas, provided there is at least one player in the same dimension (the [[Minecraft:Overworld]], [[Minecraft:The Nether]], or [[Minecraft:The End]]) as the ticking area:		The following time-related events occur without interruption in ticking areas, provided there is at least one player in the same dimension (the [[Minecraft:Overworld]], [[Minecraft:The Nether]], or [[Minecraft:The End]]) as the ticking area:
	* [[Minecraft:Water]] flows and breaks non-solid blocks.		* [[Minecraft:Water]] flows and breaks non-solid blocks.
	* [[Minecraft:Lava]] flows, sets fire to nearby ~~[[Minecraft:flammable\|~~flammable blocks]], destroys [[Minecraft:item (entity)\|item entities]], and interacts with water.		* [[Minecraft:Lava]] flows, sets fire to nearby flammable blocks, destroys [[Minecraft:item (entity)\|item entities]], and interacts with water.
	* [[Minecraft:Fire]] spreads to adjacent flammable blocks.		* [[Minecraft:Fire]] spreads to adjacent flammable blocks.
	* Dropped items fall and despawn after 5 minutes if not picked up or collected by a [[Minecraft:hopper]].		* Dropped items fall and despawn after 5 minutes if not picked up or collected by a [[Minecraft:hopper]].
	* Passive [[Minecraft:mob]]s grow up, and move around normally.		* Passive [[Minecraft:mob]]s grow up, and move around normally.
	* ~~[[Minecraft:~~Sheep]] eat [[Minecraft:Grass Block\|grass]] and grow [[Minecraft:wool]].		* Sheep eat [[Minecraft:Grass Block\|grass]] and grow [[Minecraft:wool]].
	* [[Minecraft:Sand]], [[Minecraft:gravel]], and ~~[[Minecraft:~~concrete powder]] fall if the block beneath them is moved or broken.		* [[Minecraft:Sand]], [[Minecraft:gravel]], and concrete powder fall if the block beneath them is moved or broken.
	* Primed [[Minecraft:TNT]] falls and explodes.		* Primed [[Minecraft:TNT]] falls and explodes.
	* [[Minecraft:Minecart]]s function normally.		* [[Minecraft:Minecart]]s function normally.
	* [[Minecraft:Redstone]] mechanisms and devices function normally, provided they are entirely contained within ticking areas.		* [[Minecraft:Redstone]] mechanisms and devices function normally, provided they are entirely contained within ticking areas.
	* ~~[[Minecraft:~~Crops]], [[Minecraft:mushroom]]s, [[Minecraft:sapling]]s, and ~~[[Minecraft:~~nether wart]] grow to maturity if the circumstances are suitable.		* Crops, [[Minecraft:mushroom]]s, [[Minecraft:sapling]]s, and nether wart grow to maturity if the circumstances are suitable.
	* [[Minecraft:Farmland]] changes its hydration in response to available water.		* [[Minecraft:Farmland]] changes its hydration in response to available water.
	* [[Minecraft:Leaves]] decay if not connected to a [[Minecraft:log]].		* [[Minecraft:Leaves]] decay if not connected to a [[Minecraft:log]].
	* [[Minecraft:Grass Block\|Grass]] and [[Minecraft:mycelium]] spread to adjacent blocks.		* [[Minecraft:Grass Block\|Grass]] and [[Minecraft:mycelium]] spread to adjacent blocks.
	* [[Minecraft:Ice]] forms and melts in response to changes in ~~[[Minecraft:light]]ing~~.		* [[Minecraft:Ice]] forms and melts in response to changes in lighting.
	* ~~[[Minecraft:Weather\|~~Rain, snow, and lightning]] occur and have their usual effects.		* Rain, snow, and lightning occur and have their usual effects.
	* Hostile mobs move around as usual.		* Hostile mobs move around as usual.

Line 43:		Line 43:
	{{main\|Mob spawning}}		{{main\|Mob spawning}}

	Mob spawning does not occur in ticking area chunks without the presence of a player, as all forms of mob spawning attempts are done in a radius centered on a player. However, when a player is present in those chunks, the ticking area does not prevent mob spawning. ~~[[Minecraft:~~Zombified ~~piglin]]s~~ spawning from portals is an exception; it solely relies on randomtickspeed.		Mob spawning does not occur in ticking area chunks without the presence of a player, as all forms of mob spawning attempts are done in a radius centered on a player. However, when a player is present in those chunks, the ticking area does not prevent mob spawning. Zombified piglins spawning from portals is an exception; it solely relies on randomtickspeed.

	== Creation and management ==		== Creation and management ==

	A player creates and manages ticking areas by executing a {{cmd\|tickingarea}} ~~[[Minecraft:~~command]]. Up to ten ticking areas, each containing up to 100 chunks, can exist at one time in a world. Note that commands can be used in a world only if cheats are enabled. This makes the world ineligible for earning ~~[[Minecraft:~~achievements]], so ticking areas and earning achievements are mutually exclusive.		A player creates and manages ticking areas by executing a {{cmd\|tickingarea}} command. Up to ten ticking areas, each containing up to 100 chunks, can exist at one time in a world. Note that commands can be used in a world only if cheats are enabled. This makes the world ineligible for earning achievements, so ticking areas and earning achievements are mutually exclusive.

	To create a ticking area, specify its location and size in a {{cmd\|tickingarea add}} command. There are two forms:		To create a ticking area, specify its location and size in a {{cmd\|tickingarea add}} command. There are two forms:
Line 72:		Line 72:
	{{Navbox Bedrock Edition}}		{{Navbox Bedrock Edition}}

	~~[[Minecraft:~~fr:Zone persistante]]		fr:Zone persistante
	~~[[Minecraft:~~ja:ティック領域]]		ja:ティック領域
	~~[[Minecraft:~~pt:Área de marcação]]		pt:Área de marcação
	~~[[Minecraft:~~ru:Активная область]]		ru:Активная область
	~~[[Minecraft:~~zh:常加载区域]]		zh:常加载区域