Minecraft:Tick - Revision history

SyncBot: Sync: updated from Minecraft

2026-07-25T11:11:06Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:11, 25 July 2026
Line 196:		Line 196:
	=== ''Java Edition'' ===		=== ''Java Edition'' ===
	{{HistoryTable		{{HistoryTable
			\|{{HistoryLine\|java pre-classic}}
			\|{{HistoryLine\|\|Cave game tech test\|Added game ticks.
			\|The game runs at a fixed rate of 60 ticks a second, so one tick happens every 0.016̃ seconds (16̃ milliseconds or 1/60th of a second).}}
			\|{{HistoryLine\|???}}
			\|{{HistoryLine\|\|???\|link=none\|The game now runs at a fixed rate of 20 ticks a second, so one tick happens every 0.05 seconds (50 milliseconds or 1/20 seconds).}}
	\|{{HistoryLine\|java}}		\|{{HistoryLine\|java}}
	\|{{HistoryLine\|\|1.8\|dev=14w17a\|Added the [[Minecraft:game rule]] {{cd\|randomTickSpeed}}.}}		\|{{HistoryLine\|\|1.8\|dev=14w17a\|Added the [[Minecraft:game rule]] {{cd\|randomTickSpeed}}.}}

SyncBot: Sync: updated from Minecraft

2026-07-09T11:14:04Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:14, 9 July 2026
Line 114:		Line 114:

	== Redstone tick ==		== Redstone tick ==
			{{for\|Java Edition's community-made term\|Redstone tick (term)}}
	{{see also\|Redstone mechanics}}		{{see also\|Redstone mechanics}}
	{{exclusive\|bedrock\|section=1}}		{{exclusive\|bedrock\|section=1}}
Line 179:		Line 180:
	{{exclusive\|java\|section=1}}		{{exclusive\|java\|section=1}}
	=== Redstone tick ===		=== Redstone tick ===
	The term "'''redstone tick'''" is a community-made term describing a basic unit of time ~~measurement~~ in redstone mechanics: a delay of two [[Minecraft:game tick]]s, or {{frac\|2\|20}} {{frac\|1\|10}} of a second. However, no components are strictly tied to a mandatory alignment of 2-game-tick increments. This term references & exists because most redstone components, such as repeaters, torches, comparators, etc, have delays in increments of 2 game ticks. For example, a redstone repeater can be set to delays of 2, 4, 6, or 8 game ticks, which could instead be described as 1 to 4 redstone ticks. There is no "redstone tick" hard-coded unit in the game's engine.		The term "'''redstone tick'''" is a community-made term describing a 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. However, no components are strictly tied to a mandatory alignment of 2-game-tick increments. This term references & exists because most redstone components, such as repeaters, torches, comparators, etc, have delays in increments of 2 game ticks. For example, a redstone repeater can be set to delays of 2, 4, 6, or 8 game ticks, which could instead be described as 1 to 4 redstone ticks. There is no "redstone tick" hard-coded unit in the game's engine.

	==== Half–redstone tick ====		==== Half–redstone tick ====

SyncBot: Sync: updated from Minecraft

2026-07-08T11:17:07Z

Sync: updated from Minecraft

@@ Line 116: / Line 116: @@
 {{see also|Redstone mechanics}}
 {{exclusive|bedrock|section=1}}
-'''Redstone tick''' is a unit of time that describes a delay of two [[Minecraft:game tick]]s, creating a {{frac|1|10}} of a second delay.
+'''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 game loop. Redstone updates are processed using two [[Minecraft:game tick]]s, split into two deterministic phases known as produce ticks (P-Ticks) and consume ticks (C-Ticks), or alternatively as Output Ticks and Input Ticks.
+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
-These two phases form a single redstone tick, which spans 2 game ticks. There are 10 redstone ticks per standard 20-game-tick second.
+=== Tick cycle ===
-'''Tick cycle'''
+* Produce tick ({{va|P-tick}}) — occurs first, on odd-numbered game ticks; components output or send their signal.
-*Output/produce tick ({{va|P-tick}}): Occurs first on odd-numbered game ticks. During this phase, components output or send their signal.
+* Consume tick ({{va|C-tick}}) — occurs second, on even-numbered game ticks; components read and respond to the signals they receive.
-'''Component Behavior'''
+{| class="wikitable" style="text-align:center;"
-*[[Minecraft:Power components]] ([[Minecraft:repeater]]s, [[Minecraft:comparator]]s, [[Minecraft:redstone torch]]s, [[Minecraft:observer]]s, etc.): These components read their input side during an output/produce tick. After their configured delay, they update their output side and produce an input/consume tick.
+! Redstone tick !! Game tick !! Time (s) !! Phase
-*[[Minecraft:Mechanism components]] ([[Minecraft:piston]]s, [[Minecraft:redstone lamp]]s, [[Minecraft:door]]s, etc.): These components are activated during an input/consume tick and change their block state, which then creates block updates processed in the subsequent output/produce tick.
+|-
-*[[Minecraft:Redstone dust]] updates its power state on every game tick (20 times per second), independently of the dedicated redstone tick system. This allows it to transmit pulses with a duration of only 1 game tick. A dust line powered on an odd game tick serves as an output for components processing on P-Ticks, while one powered on an even game tick serves as an output for components on C-Ticks. This makes redstone dust one of the few components that can be "1-ticked" and used to create phase-specific pulses. Redstone dust only updates visually on output/produce ticks, meaning that on an input/consume tick, while technically on, it looks visually off.
+| rowspan="2" | 1 || 1 || 0.05 || P-tick
-*[[Minecraft:Armor stand]]s update on both input and output ticks, meaning they are one of the few redstone components that utilize all 20 game ticks. Other [[Minecraft:entities]] that interact with redstone, such as [[Minecraft:sulfur cube]]s that have absorbed TNT, [[Minecraft:minecarts with hoppers]], and [[Minecraft:minecarts with TNT]] might also be able to utilize all 20 game ticks instead of being tied to redstone's 10 P or C ticks.{{needs testing}}
+|-
-The transmission and timing of redstone signals are determined by these ticks, which govern when redstone devices output power and when they respond to input.
+=== Component behavior ===
-== Piston 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.
 {{exclusive|java|section=1}}
 The '''piston tick''' is a different way to divide the game tick, based on the ''Immediate Update Theory'' by Sancarn and Selulance.<ref>Referred to as "immediate update bug" or "lever bug" in the original video https://www.youtube.com/watch?v=HCgkllZq338</ref> It was created by the Chinese redstone community in order to simplify the calculation of piston timings, but it never gained popularity in the Western community.

SyncBot: Sync: updated from Minecraft

2026-06-07T11:15:38Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:15, 7 June 2026
Line 79:		Line 79:
	Most blocks ignore this tick, but some use it to do something:		Most blocks ignore this tick, but some use it to do something:
	*[[Minecraft:Crops]] may grow or uproot.		*[[Minecraft:Crops]] may grow or uproot.
	*[[Minecraft:~~Mushroom~~]]s may spread or uproot.		*[[Minecraft:Mushrooms]] may spread or uproot.
	*~~[[Minecraft:~~Vines]] may spread.		*{{BlockLink\|Vines}} may spread.
	*{{IN\|BE}}~~, [[Minecraft:fire]]~~ may burn out or spread.		*{{BlockLink\|Fire}} may burn out or spread.{{only\|bedrock\|short=1}}
	*~~[[Minecraft:~~Ice]] and ~~[[Minecraft:~~snow]] layers may melt.		*{{BlockLink\|Ice}} and {{BlockLink\|snow}} layers may melt.
	*~~[[Minecraft:~~Leaves]] may decay.		*{{BlockLink\|Leaves}} may decay.
	*~~[[Minecraft:~~Farmland]] hydration is updated.		*{{BlockLink\|Farmland}} hydration is updated.
	*~~[[Minecraft:Cacti]]~~, ~~[[Minecraft:~~sugar cane]], ~~[[Minecraft:~~kelp]], ~~[[Minecraft:~~bamboo]], ~~[[Minecraft:~~chorus flower]]s, ~~[[Minecraft:~~mangrove propagule]]s and ~~[[Minecraft:~~sweet berry bush]]es may grow.		*{{BlockLink\|Cactus}}, {{BlockLink\|sugar cane}}, {{BlockLink\|kelp}}, {{BlockLink\|bamboo}}, {{BlockLink\|chorus flower}}s, {{BlockLink\|mangrove propagule}}s and {{BlockLink\|sweet berry bush}}es may grow.
	*~~[[Minecraft:~~Grass block]]s and ~~[[Minecraft:~~mycelium]] may spread.		*{{BlockLink\|Grass block}}s and {{BlockLink\|mycelium}} may spread.
	*Grass ~~blocks~~, mycelium, and ~~[[Minecraft:~~nylium]] may decay (only if the condition is met).		*{{BlockLink\|Grass block}}s, {{BlockLink\|mycelium}}, and {{BlockLink\|nylium}} may decay (only if the condition is met).
	*[[Minecraft:Sapling]]s may grow into a [[Minecraft:tree]].		*[[Minecraft:Sapling]]s may grow into a [[Minecraft:tree]].
	*~~[[Minecraft:~~Lava]] may set fires nearby.<ref group=note>In {{JE}}, this requires a player within an 8-chunk radius. However, {{cmd\|gamerule allowFireTicksAwayFromPlayer}} removes this requirement if set to true.</ref>		*{{BlockLink\|Lava}} may set fires nearby.<ref group=note>{{IN\|JE}}, this requires a player within an 8-chunk radius. However, {{cmd\|gamerule allowFireTicksAwayFromPlayer}} removes this requirement if set to true.</ref>
	*~~[[Minecraft:~~Mud]] may turn into ~~[[Minecraft:~~clay]] if placed on top of a block with ~~[[Minecraft:~~pointed dripstone]] underneath.		*{{BlockLink\|Mud}} may turn into {{BlockLink\|clay}} if placed on top of a block with {{BlockLink\|pointed dripstone}} underneath.
	*Lit ~~[[Minecraft:~~redstone ore]] turns off.		*Lit {{BlockLink\|redstone ore}} turns off.
	*~~[[Minecraft:~~Nether portal ~~block]]s~~ may spawn a [[Minecraft:zombified piglin]].		*{{BlockLink\|Nether portal}} blocks may spawn a [[Minecraft:zombified piglin]].
	*~~[[Minecraft:~~Turtle egg]]s crack or hatch.		*{{BlockLink\|Turtle egg}}s crack or hatch.
	*~~[[Minecraft:~~Campfire]] smoke appears.		*{{BlockLink\|Campfire}} smoke appears.
	*~~[[Minecraft:~~Budding amethyst]] may grow an ~~[[Minecraft:~~amethyst bud]] on any of its sides as longs as there is no solid block.		*{{BlockLink\|Budding amethyst}} may grow an {{BlockLink\|amethyst bud}} on any of its sides as longs as there is no solid block.
	*~~[[Minecraft:~~Block of Copper\|Copper block]]s (or any of its non-oxidized variants) may advance one stage in ~~oxidation.~~		*{{BlockLink\|Block of Copper\|text=Copper block}}s (or any of its non-oxidized variants) may advance one stage in [[Minecraft:oxidation]].
	*[[Minecraft:~~Pointed dripstone~~]] may fill a cauldron below.		*{{BlockLink\|pointed dripstone}} may fill a {{BlockLink\|cauldron}} below.
	*~~[[Minecraft:Pointed~~ dripstone]] may grow a stalagmite/stalactite if the conditions are met.		*{{BlockLink\|pointed dripstone}} may grow a stalagmite/stalactite if the conditions are met.

	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]].

SyncBot: Sync: updated from Minecraft

2026-06-03T11:13:34Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:13, 3 June 2026
Line 1:		Line 1:
	{{about\|\|random ticks\|Random Tick\|the command\|Commands/tick}}		{{about\|\|random ticks\|Random Tick\|the command\|Commands/tick\|function uses\|Tick.json}}
	Nearly all video games (including ''Minecraft'') are driven by one big {{w\|Control flow#Loops\|program loop}}. Just as every gear in a clock is synchronized with the pendulum, every task involved in advancing a game simulation is synchronized with the game loop. Appropriately, one cycle of the game loop is called a '''tick'''.		Nearly all video games (including ''Minecraft'') are driven by one big {{w\|Control flow#Loops\|program loop}}. Just as every gear in a clock is synchronized with the pendulum, every task involved in advancing a game simulation is synchronized with the game loop. Appropriately, one cycle of the game loop is called a '''tick'''.

SyncBot: Sync: updated from Minecraft

2026-06-02T11:16:46Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:16, 2 June 2026
Line 1:		Line 1:
	{{~~for~~\|the command\|Commands/tick}}		{{about\|\|random ticks\|Random Tick\|the command\|Commands/tick}}
	Nearly all video games (including ''Minecraft'') are driven by one big {{w\|Control flow#Loops\|program loop}}. Just as every gear in a clock is synchronized with the pendulum, every task involved in advancing a game simulation is synchronized with the game loop. Appropriately, one cycle of the game loop is called a '''tick'''.		Nearly all video games (including ''Minecraft'') are driven by one big {{w\|Control flow#Loops\|program loop}}. Just as every gear in a clock is synchronized with the pendulum, every task involved in advancing a game simulation is synchronized with the game loop. Appropriately, one cycle of the game loop is called a '''tick'''.

SyncBot: Sync: updated from Minecraft

2026-05-27T11:15:04Z

Sync: updated from Minecraft

SyncBot: Sync: updated from Minecraft

2026-05-02T11:11:26Z

Sync: updated from Minecraft

Show changes

SyncBot: Fix template calls: add MC/ prefix

2026-04-09T21:03:21Z

Fix template calls: add MC/ prefix

Show changes

SyncBot: Remove broken links to missing pages

2026-04-09T16:07:48Z

Remove broken links to missing pages

Show changes

← Older revision		Revision as of 11:15, 27 May 2026
Line 116:		Line 116:
	{{see also\|Redstone mechanics}}		{{see also\|Redstone mechanics}}
	{{exclusive\|bedrock\|section=1}}		{{exclusive\|bedrock\|section=1}}
	'''Redstone tick''' is a unit of time that describes a delay of two game ~~ticks~~, creating a {{frac\|1\|10}} of a second delay.		'''Redstone tick''' is a unit of time that describes a delay of two [[Minecraft:game tick]]s, creating a {{frac\|1\|10}} of a second delay.
			<!-- concurrent threads claim is unproven
			The redstone system is calculated on concurrent threads, meaning that redstone updates are processed independently of the main game loop. This architecture utilizes a two-phase tick system, known as produce ticks (P-Ticks) and consume ticks (C-ticks), or alternatively as Output Ticks and Input Ticks.-->

	The redstone system is calculated ~~on concurrent threads, meaning that redstone updates are processed~~ independently of the main game loop. ~~This architecture utilizes a~~ two~~-phase~~ tick ~~system~~, known as produce ticks (P-Ticks) and consume ticks (C-~~ticks~~), or alternatively as Output Ticks and Input Ticks.		The redstone system is calculated independently of the main game loop. Redstone updates are processed using two [[Minecraft:game tick]]s, split into two deterministic phases known as produce ticks (P-Ticks) and consume ticks (C-Ticks), or alternatively as Output Ticks and Input Ticks.

	These two phases form a single redstone tick, which spans 2 game ticks. There are 10 redstone ticks per standard 20-game-tick second.		These two phases form a single redstone tick, which spans 2 game ticks. There are 10 redstone ticks per standard 20-game-tick second.
Line 129:		Line 131:
	*[[Minecraft:Power components]] ([[Minecraft:repeater]]s, [[Minecraft:comparator]]s, [[Minecraft:redstone torch]]s, [[Minecraft:observer]]s, etc.): These components read their input side during an output/produce tick. After their configured delay, they update their output side and produce an input/consume tick.		*[[Minecraft:Power components]] ([[Minecraft:repeater]]s, [[Minecraft:comparator]]s, [[Minecraft:redstone torch]]s, [[Minecraft:observer]]s, etc.): These components read their input side during an output/produce tick. After their configured delay, they update their output side and produce an input/consume tick.
	*[[Minecraft:Mechanism components]] ([[Minecraft:piston]]s, [[Minecraft:redstone lamp]]s, [[Minecraft:door]]s, etc.): These components are activated during an input/consume tick and change their block state, which then creates block updates processed in the subsequent output/produce tick.		*[[Minecraft:Mechanism components]] ([[Minecraft:piston]]s, [[Minecraft:redstone lamp]]s, [[Minecraft:door]]s, etc.): These components are activated during an input/consume tick and change their block state, which then creates block updates processed in the subsequent output/produce tick.
	*[[Minecraft:Redstone dust]] updates its power state on every game tick (20 times per second), independently of the dedicated redstone tick system. This allows it to transmit pulses with a duration of only 1 game tick. A dust line powered on an odd game tick serves as an output for components processing on P-Ticks, while one powered on an even game tick serves as an output for components on C-Ticks. This makes redstone dust one of the few components that can be "1-ticked" and used to create phase-specific pulses. Redstone dust only updates visually on output/produce ticks, meaning on input/consume tick while technically on looks visually off.		*[[Minecraft:Redstone dust]] updates its power state on every game tick (20 times per second), independently of the dedicated redstone tick system. This allows it to transmit pulses with a duration of only 1 game tick. A dust line powered on an odd game tick serves as an output for components processing on P-Ticks, while one powered on an even game tick serves as an output for components on C-Ticks. This makes redstone dust one of the few components that can be "1-ticked" and used to create phase-specific pulses. Redstone dust only updates visually on output/produce ticks, meaning that on an input/consume tick, while technically on, it looks visually off.
	*[[Minecraft:Armor stand]]s update on both input and output ticks meaning they are one of the few redstone components that ~~utilizes~~ all 20 ticks. [[Minecraft:~~Minecarts~~ with hoppers]] and [[Minecraft:minecarts with TNT]] might also be able to utilize all 20 game ~~tick~~ instead of being tied to P or C ticks.{{needs testing}}		*[[Minecraft:Armor stand]]s update on both input and output ticks, meaning they are one of the few redstone components that utilize all 20 game ticks. Other [[Minecraft:entities]] that interact with redstone, such as [[Minecraft:sulfur cube]]s that have absorbed TNT, [[Minecraft:minecarts with hoppers]], and [[Minecraft:minecarts with TNT]] might also be able to utilize all 20 game ticks instead of being tied to redstone's 10 P or C ticks.{{needs testing}}

	The transmission and timing of redstone signals are determined by these ticks, which govern when redstone devices output power and when they respond to input.		The transmission and timing of redstone signals are determined by these ticks, which govern when redstone devices output power and when they respond to input.