Minecraft:Tick - Revision history

SyncBot: Sync: updated from Minecraft

2026-10-24T11:23:55Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:23, 24 October 2026
Line 101:		Line 101:
	*{{BlockLink\|Block of Copper\|text=Copper block}}s (or any of its non-oxidized variants) may advance one stage in [[Minecraft:oxidation]].		*{{BlockLink\|Block of Copper\|text=Copper block}}s (or any of its non-oxidized variants) may advance one stage in [[Minecraft:oxidation]].
	*{{BlockLink\|Pointed dripstone}} and {{BlockLink\|sulfur spike}} may grow a stalagmite/stalactite if the conditions are met.		*{{BlockLink\|Pointed dripstone}} and {{BlockLink\|sulfur spike}} may grow a stalagmite/stalactite if the conditions are met.
			*{{BlockLink\|Icicle}}s may grow a stalactite if the conditions are met.{{upcoming\|java 26.4\|bedrock 26.60}}
	*{{BlockLink\|Pointed dripstone}} may fill a {{BlockLink\|cauldron}} below.		*{{BlockLink\|Pointed dripstone}} may fill a {{BlockLink\|cauldron}} below.
	*{{BlockLink\|Dried Ghast}} may reach the next stage of hydration or dehydration.		*{{BlockLink\|Dried Ghast}} may reach the next stage of hydration or dehydration.

SyncBot: Sync: updated from Minecraft

2026-10-20T11:11:53Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:11, 20 October 2026
Line 122:		Line 122:

	== Redstone tick ==		== Redstone tick ==
			{{exclusive\|bedrock\|section=1}}
	{{for\|Java Edition's community-made term\|Redstone tick (term)}}		{{for\|Java Edition's community-made term\|Redstone tick (term)}}
	{{see also\|Redstone mechanics}}		{{see also\|Redstone mechanics}}
	~~{{exclusive\|bedrock\|section=1}}~~
	'''Redstone tick''' is the basic unit of time in redstone mechanics: a delay of two [[Minecraft:game tick]]s, or {{frac\|2\|20}} {{frac\|1\|10}} of a second, giving 10 redstone ticks per standard 20-tick second.		'''Redstone tick''' is the basic unit of time in redstone mechanics: a delay of two [[Minecraft:game tick]]s, or {{frac\|2\|20}} {{frac\|1\|10}} of a second, giving 10 redstone ticks per standard 20-tick second.

SyncBot: Sync: updated from Minecraft

2026-09-30T11:18:33Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:18, 30 September 2026
Line 3:		Line 3:

	== Game tick ==		== Game tick ==
	A game tick is where ''Minecraft's'' game loop runs once. The game normally runs at a fixed rate of 20 ticks per second, so one tick happens every 0.05 seconds (50 milliseconds or 1/20 seconds), making an [[Minecraft:Daylight cycle\|in-game day]] last exactly 24 000 ticks (20 minutes). However, if the computer is unable to keep up with this speed, the amount of game ticks per second (TPS) decreases. As the vast majority of actions are timed based on tick count rather than on real time, this means that many things take longer on a slower computer.		A game tick is where ''Minecraft's'' game loop runs once. The game normally runs at a fixed rate of 20 ticks per second, so one tick happens every 0.05 seconds (50 milliseconds or 1/20 seconds), making an [[Minecraft:Daylight cycle\|in-game day]] last exactly 24,000 ticks (20 minutes). However, if the computer is unable to keep up with this speed, the amount of game ticks per second (TPS) decreases. As the vast majority of actions are timed based on tick count rather than on real time, this means that many things take longer on a slower computer.

	A statistic related to ticks per second (TPS) is milliseconds per tick (MSPT), the time a server actually uses to compute a tick. The TPS can be maintained at 20 only if the MSPT is no higher than 50. The following often contribute to server-side lag:		A statistic related to ticks per second (TPS) is milliseconds per tick (MSPT), the time a server actually uses to compute a tick. The TPS can be maintained at 20 only if the MSPT is no higher than 50. The following often contribute to server-side lag:

SyncBot: Sync: updated from Minecraft

2026-09-09T11:14:35Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:14, 9 September 2026
Line 183:		Line 183:
	* [[Minecraft:Mechanism components]] ([[Minecraft:piston]]s, [[Minecraft:redstone lamp]]s, [[Minecraft:door]]s, etc.) activate during a C-tick and change block state; the resulting block update is processed on the next P-tick.		* [[Minecraft:Mechanism components]] ([[Minecraft:piston]]s, [[Minecraft:redstone lamp]]s, [[Minecraft:door]]s, etc.) activate during a C-tick and change block state; the resulting block update is processed on the next P-tick.
	* [[Minecraft:Redstone dust]] instead of following the 10-tick redstone cycle, it updates its power state on every game tick (20 times per second) which lets it carry 1 game tick long pulses. A dust line powered on an odd tick activates P-tick components, while one powered on an even tick activates C-tick components, meaning redstone dust can be pulsed for 1-tick for phase-specific P- and C-component activations. Its visual state only refreshes on P-ticks, meaning if it is only ticked on a C-tick, it will look off, even though it is technically on.		* [[Minecraft:Redstone dust]] instead of following the 10-tick redstone cycle, it updates its power state on every game tick (20 times per second) which lets it carry 1 game tick long pulses. A dust line powered on an odd tick activates P-tick components, while one powered on an even tick activates C-tick components, meaning redstone dust can be pulsed for 1-tick for phase-specific P- and C-component activations. Its visual state only refreshes on P-ticks, meaning if it is only ticked on a C-tick, it will look off, even though it is technically on.
	* [[Minecraft:Armor stand]]s, [[Minecraft:Hopper minecart\|Hopper Minecarts]], [[Minecraft:TNT minecart\|TNT minecarts]], and [[Minecraft:Sulfur Cube]]s that have absorbed TNT activate on both P- and C-ticks, making them the ~~few~~ components that respond on all 20 game ticks rather than 10.		* [[Minecraft:Entity components]] ([[Minecraft:Armor stand]]s, [[Minecraft:Hopper minecart\|Hopper Minecarts]], [[Minecraft:TNT minecart\|TNT minecarts]], and [[Minecraft:Sulfur Cube]]s that have absorbed TNT) activate on both P- and C-ticks, making them the only components that respond on all 20 game ticks rather than 10.

	==Java Edition's community-made terms==		==Java Edition's community-made terms==

SyncBot: Sync: updated from Minecraft

2026-09-05T11:18:58Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:18, 5 September 2026
Line 127:		Line 127:
	'''Redstone tick''' is the basic unit of time in redstone mechanics: a delay of two [[Minecraft:game tick]]s, or {{frac\|2\|20}} {{frac\|1\|10}} of a second, giving 10 redstone ticks per standard 20-tick second.		'''Redstone tick''' is the basic unit of time in redstone mechanics: a delay of two [[Minecraft:game tick]]s, or {{frac\|2\|20}} {{frac\|1\|10}} of a second, giving 10 redstone ticks per standard 20-tick second.

	The redstone system is calculated independently of the main [[Minecraft:game tick]] loop. Each redstone tick is split into two deterministic phases: a produce tick (P-tick) and a consume tick (C-tick). These two phases make up a single redstone tick		The redstone system is calculated independently of the main [[Minecraft:game tick]] loop. Each redstone tick is split into two deterministic phases: a produce tick (P-tick) and a consume tick (C-tick). These two phases make up a single redstone tick.

	=== Tick cycle ===		=== Tick cycle ===

SyncBot: Sync: updated from Minecraft

2026-08-26T11:21:54Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:21, 26 August 2026
Line 183:		Line 183:
	* [[Minecraft:Mechanism components]] ([[Minecraft:piston]]s, [[Minecraft:redstone lamp]]s, [[Minecraft:door]]s, etc.) activate during a C-tick and change block state; the resulting block update is processed on the next P-tick.		* [[Minecraft:Mechanism components]] ([[Minecraft:piston]]s, [[Minecraft:redstone lamp]]s, [[Minecraft:door]]s, etc.) activate during a C-tick and change block state; the resulting block update is processed on the next P-tick.
	* [[Minecraft:Redstone dust]] instead of following the 10-tick redstone cycle, it updates its power state on every game tick (20 times per second) which lets it carry 1 game tick long pulses. A dust line powered on an odd tick activates P-tick components, while one powered on an even tick activates C-tick components, meaning redstone dust can be pulsed for 1-tick for phase-specific P- and C-component activations. Its visual state only refreshes on P-ticks, meaning if it is only ticked on a C-tick, it will look off, even though it is technically on.		* [[Minecraft:Redstone dust]] instead of following the 10-tick redstone cycle, it updates its power state on every game tick (20 times per second) which lets it carry 1 game tick long pulses. A dust line powered on an odd tick activates P-tick components, while one powered on an even tick activates C-tick components, meaning redstone dust can be pulsed for 1-tick for phase-specific P- and C-component activations. Its visual state only refreshes on P-ticks, meaning if it is only ticked on a C-tick, it will look off, even though it is technically on.
	* [[Minecraft:Armor stand]]s and [[Minecraft:Sulfur Cube]]s that have absorbed TNT activate on both P- and C-ticks, making them the few components that respond on all 20 game ticks rather than 10. ~~Other [[Minecraft:entities]] that interact with redstone, such as [[Minecraft:minecarts with hoppers]], and [[Minecraft:minecarts with TNT]], might also behave the same way.{{needs testing}}~~		* [[Minecraft:Armor stand]]s, [[Minecraft:Hopper minecart\|Hopper Minecarts]], [[Minecraft:TNT minecart\|TNT minecarts]], and [[Minecraft:Sulfur Cube]]s that have absorbed TNT activate on both P- and C-ticks, making them the few components that respond on all 20 game ticks rather than 10.

	==Java Edition's community-made terms==		==Java Edition's community-made terms==

SyncBot: Sync: updated from Minecraft

2026-08-19T11:17:24Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:17, 19 August 2026
Line 66:		Line 66:

	In both editions, the following things happen when a chunk gets ticked:		In both editions, the following things happen when a chunk gets ticked:
	* Mobs naturally [[Minecraft:Mob spawning\|spawn]].<ref group=note name=proximity>In {{JE}}, this requires a player within an 8-chunk radius.</ref>		* Mobs naturally [[Minecraft:Mob spawning\|spawn]].<ref group=note name=proximity>In {{JE}}, this requires a player within an 8-chunk radius. In {{BE}}, [[Minecraft:iron golem]]s only spawn in chunks directly loaded by the player ([[Minecraft:bugtracker:MCPE-226025\|MCPE-226025]]).</ref>
	* During a [[Minecraft:thunderstorm]], lightning may strike somewhere in the chunk ({{frac\|1\|100000}} chance).<ref group=note name=proximity/>		* During a [[Minecraft:thunderstorm]], lightning may strike somewhere in the chunk ({{frac\|1\|100000}} chance).<ref group=note name=proximity/>
	* {{frac\|1\|16}} chance that one column is chosen for weather checks on the topmost block:		* {{frac\|1\|16}} chance that one column is chosen for weather checks on the topmost block:

SyncBot: Sync: updated from Minecraft

2026-08-17T11:22:51Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:22, 17 August 2026
Line 104:		Line 104:
	*{{BlockLink\|Dried Ghast}} may reach the next stage of hydration or dehydration.		*{{BlockLink\|Dried Ghast}} may reach the next stage of hydration or dehydration.
	*{{BlockLink\|Eyeblossom}} may open at night and close at day.		*{{BlockLink\|Eyeblossom}} may open at night and close at day.
			*{{BlockLink\|Fire}} and {{BlockLink\|soul fire}}, may burn out or spread.{{only\|bedrock\|short=1}}

	Because random block ticks are granted randomly, there is no way to predict when a block can receive its next tick. {{IN\|java}}, the ''median'' time between ticks is '''47.30''' seconds (<math>\log_{\frac{4096-3}{4096}}(0.5) \approx</math> 946.03 game ticks). That is, there is a 50% chance for the interval to be equal or shorter than 47.30 seconds and a 50% chance for it to be longer than 47.30. However, sometimes it is much longer or shorter: for example, there is a 1.38% chance for the interval to be less than one second and a 1.23% chance for the interval to be over five minutes. On ''average'', blocks are updated every '''68.27''' seconds (<math>\frac{4096}{3} \approx</math> 1365.33 game ticks). For the math behind these numbers, see the Wikipedia entries for the [[Minecraft:wikipedia:geometric distribution\|geometric distribution]].		Because random block ticks are granted randomly, there is no way to predict when a block can receive its next tick. {{IN\|java}}, the ''median'' time between ticks is '''47.30''' seconds (<math>\log_{\frac{4096-3}{4096}}(0.5) \approx</math> 946.03 game ticks). That is, there is a 50% chance for the interval to be equal or shorter than 47.30 seconds and a 50% chance for it to be longer than 47.30. However, sometimes it is much longer or shorter: for example, there is a 1.38% chance for the interval to be less than one second and a 1.23% chance for the interval to be over five minutes. On ''average'', blocks are updated every '''68.27''' seconds (<math>\frac{4096}{3} \approx</math> 1365.33 game ticks). For the math behind these numbers, see the Wikipedia entries for the [[Minecraft:wikipedia:geometric distribution\|geometric distribution]].
Line 191:		Line 192:
	==== Half–redstone tick ====		==== Half–redstone tick ====
	Certain features like scaffolding or leaves propagating updates, or a piston with 1-game-tick start delay, introduce a community-made term "half–redstone ticks," meaning one [[Minecraft:game tick]].		Certain features like scaffolding or leaves propagating updates, or a piston with 1-game-tick start delay, introduce a community-made term "half–redstone ticks," meaning one [[Minecraft:game tick]].

			=== Zero-ticking ===
			{{main\|Tutorial:Zero-ticking}}

	=== Piston tick ===		=== Piston tick ===
Line 199:		Line 203:

	== History ==		== History ==
	~~{{Incomplete section}}~~

	=== ''Java Edition'' ===		=== ''Java Edition'' ===
			{{Missing information\|section\|Java Edition history}}
	{{HistoryTable		{{HistoryTable
	\|{{HistoryLine\|java pre-classic}}		\|{{HistoryLine\|java pre-classic}}
Line 217:		Line 221:

	=== ''Bedrock Edition'' ===		=== ''Bedrock Edition'' ===
			{{Missing information\|section\|Bedrock Edition history}}
	{{HistoryTable		{{HistoryTable
	\|{{HistoryLine\|bedrock}}		\|{{HistoryLine\|bedrock}}
	\|{{HistoryLine\|\|1.8.0\|dev=beta 1.8.0.8\|Added the game rule {{cd\|randomTickSpeed}}.}}		\|{{HistoryLine\|\|1.8.0\|dev=beta 1.8.0.8\|Added the game rule {{cd\|randomTickSpeed}}.}}
	}}		}}

			=== ''Legacy Console Edition'' ===
			{{Missing information\|section\|Legacy Console Edition history}}

	== References ==		== References ==

SyncBot: Sync: updated from Minecraft

2026-08-16T11:15:47Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:15, 16 August 2026
Line 181:		Line 181:
	* [[Minecraft:Power components]]/[[Minecraft:Transmission components]] ([[Minecraft:repeater]]s, [[Minecraft:comparator]]s, [[Minecraft:redstone torch]]s, [[Minecraft:observer]]s, etc.) read their input during a P-tick; after their configured delay, they write their new output on the following C-tick.		* [[Minecraft:Power components]]/[[Minecraft:Transmission components]] ([[Minecraft:repeater]]s, [[Minecraft:comparator]]s, [[Minecraft:redstone torch]]s, [[Minecraft:observer]]s, etc.) read their input during a P-tick; after their configured delay, they write their new output on the following C-tick.
	* [[Minecraft:Mechanism components]] ([[Minecraft:piston]]s, [[Minecraft:redstone lamp]]s, [[Minecraft:door]]s, etc.) activate during a C-tick and change block state; the resulting block update is processed on the next P-tick.		* [[Minecraft:Mechanism components]] ([[Minecraft:piston]]s, [[Minecraft:redstone lamp]]s, [[Minecraft:door]]s, etc.) activate during a C-tick and change block state; the resulting block update is processed on the next P-tick.
	* [[Minecraft:Redstone dust]] instead of following the 10-tick redstone cycle, it updates its power state on every game tick (20 times per second) which lets it carry 1 game tick long pulses. A dust line powered on an odd tick activates P-tick components, while one powered on an even tick activates C-tick components, meaning redstone dust can be pulsed for 1-tick for phase-specific P- and C-component activations. Its visual state only refreshes on P-ticks, meaning if it is only ticked on a C-tick, it will look off, even though it is technically on~~. A [[Minecraft:Redstone_circuits/Pulse#Observer_Pulse_generator\|observer pulse generator]] is easy to generate only C-tick pulses~~.		* [[Minecraft:Redstone dust]] instead of following the 10-tick redstone cycle, it updates its power state on every game tick (20 times per second) which lets it carry 1 game tick long pulses. A dust line powered on an odd tick activates P-tick components, while one powered on an even tick activates C-tick components, meaning redstone dust can be pulsed for 1-tick for phase-specific P- and C-component activations. Its visual state only refreshes on P-ticks, meaning if it is only ticked on a C-tick, it will look off, even though it is technically on.
	* [[Minecraft:Armor stand]]s and [[Minecraft:Sulfur Cube]]s that have absorbed TNT activate on both P- and C-ticks, making them the few components that respond on all 20 game ticks rather than 10. Other [[Minecraft:entities]] that interact with redstone, such as [[Minecraft:minecarts with hoppers]], and [[Minecraft:minecarts with TNT]], might also behave the same way.{{needs testing}}		* [[Minecraft:Armor stand]]s and [[Minecraft:Sulfur Cube]]s that have absorbed TNT activate on both P- and C-ticks, making them the few components that respond on all 20 game ticks rather than 10. Other [[Minecraft:entities]] that interact with redstone, such as [[Minecraft:minecarts with hoppers]], and [[Minecraft:minecarts with TNT]], might also behave the same way.{{needs testing}}

SyncBot: Sync: updated from Minecraft

2026-08-14T11:12:06Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:12, 14 August 2026
Line 181:		Line 181:
	* [[Minecraft:Power components]]/[[Minecraft:Transmission components]] ([[Minecraft:repeater]]s, [[Minecraft:comparator]]s, [[Minecraft:redstone torch]]s, [[Minecraft:observer]]s, etc.) read their input during a P-tick; after their configured delay, they write their new output on the following C-tick.		* [[Minecraft:Power components]]/[[Minecraft:Transmission components]] ([[Minecraft:repeater]]s, [[Minecraft:comparator]]s, [[Minecraft:redstone torch]]s, [[Minecraft:observer]]s, etc.) read their input during a P-tick; after their configured delay, they write their new output on the following C-tick.
	* [[Minecraft:Mechanism components]] ([[Minecraft:piston]]s, [[Minecraft:redstone lamp]]s, [[Minecraft:door]]s, etc.) activate during a C-tick and change block state; the resulting block update is processed on the next P-tick.		* [[Minecraft:Mechanism components]] ([[Minecraft:piston]]s, [[Minecraft:redstone lamp]]s, [[Minecraft:door]]s, etc.) activate during a C-tick and change block state; the resulting block update is processed on the next P-tick.
	* [[Minecraft:Redstone dust]] instead of following the 10-tick redstone cycle, it updates its power state on every game tick (20 times per second) which lets it carry 1 game tick long pulses. A dust line powered on an odd tick activates P-tick components, while one powered on an even tick activates C-tick components, meaning redstone dust can be pulsed for 1-tick for phase-specific P- and C-component activations. Its visual state only refreshes on ~~produce~~ ticks, meaning if it is only ticked on a ~~consume~~ tick, it will look off, even though it is technically on.		* [[Minecraft:Redstone dust]] instead of following the 10-tick redstone cycle, it updates its power state on every game tick (20 times per second) which lets it carry 1 game tick long pulses. A dust line powered on an odd tick activates P-tick components, while one powered on an even tick activates C-tick components, meaning redstone dust can be pulsed for 1-tick for phase-specific P- and C-component activations. Its visual state only refreshes on P-ticks, meaning if it is only ticked on a C-tick, it will look off, even though it is technically on. A [[Minecraft:Redstone_circuits/Pulse#Observer_Pulse_generator\|observer pulse generator]] is easy to generate only C-tick pulses.
	* [[Minecraft:Armor stand]]s and [[Minecraft:Sulfur Cube]]s that have absorbed TNT activate on both P- and C-ticks, making them the few components that respond on all 20 game ticks rather than 10. Other [[Minecraft:entities]] that interact with redstone, such as [[Minecraft:minecarts with hoppers]], and [[Minecraft:minecarts with TNT]], might also behave the same way.{{needs testing}}		* [[Minecraft:Armor stand]]s and [[Minecraft:Sulfur Cube]]s that have absorbed TNT activate on both P- and C-ticks, making them the few components that respond on all 20 game ticks rather than 10. Other [[Minecraft:entities]] that interact with redstone, such as [[Minecraft:minecarts with hoppers]], and [[Minecraft:minecarts with TNT]], might also behave the same way.{{needs testing}}

← Older revision		Revision as of 11:23, 24 October 2026
Line 101:		Line 101:
	*{{BlockLink\|Block of Copper\|text=Copper block}}s (or any of its non-oxidized variants) may advance one stage in [[Minecraft:oxidation]].		*{{BlockLink\|Block of Copper\|text=Copper block}}s (or any of its non-oxidized variants) may advance one stage in [[Minecraft:oxidation]].
	*{{BlockLink\|Pointed dripstone}} and {{BlockLink\|sulfur spike}} may grow a stalagmite/stalactite if the conditions are met.		*{{BlockLink\|Pointed dripstone}} and {{BlockLink\|sulfur spike}} may grow a stalagmite/stalactite if the conditions are met.
			*{{BlockLink\|Icicle}}s may grow a stalactite if the conditions are met.{{upcoming\|java 26.4\|bedrock 26.60}}
	*{{BlockLink\|Pointed dripstone}} may fill a {{BlockLink\|cauldron}} below.		*{{BlockLink\|Pointed dripstone}} may fill a {{BlockLink\|cauldron}} below.
	*{{BlockLink\|Dried Ghast}} may reach the next stage of hydration or dehydration.		*{{BlockLink\|Dried Ghast}} may reach the next stage of hydration or dehydration.

← Older revision		Revision as of 11:11, 20 October 2026
Line 122:		Line 122:

	== Redstone tick ==		== Redstone tick ==
			{{exclusive\|bedrock\|section=1}}
	{{for\|Java Edition's community-made term\|Redstone tick (term)}}		{{for\|Java Edition's community-made term\|Redstone tick (term)}}
	{{see also\|Redstone mechanics}}		{{see also\|Redstone mechanics}}
	~~{{exclusive\|bedrock\|section=1}}~~
	'''Redstone tick''' is the basic unit of time in redstone mechanics: a delay of two [[Minecraft:game tick]]s, or {{frac\|2\|20}} {{frac\|1\|10}} of a second, giving 10 redstone ticks per standard 20-tick second.		'''Redstone tick''' is the basic unit of time in redstone mechanics: a delay of two [[Minecraft:game tick]]s, or {{frac\|2\|20}} {{frac\|1\|10}} of a second, giving 10 redstone ticks per standard 20-tick second.