Block Actions - Revision history

imported>Pesekjak at 18:07, 21 June 2024

2024-06-21T18:07:25Z

← Older revision		Revision as of 18:07, 21 June 2024
Line 43:		Line 43:
	\| <code>minecraft:bell</code>		\| <code>minecraft:bell</code>
	\| [[#Bell\|Bell]]		\| [[#Bell\|Bell]]
			\|-
			\| {{Minecraft Wiki\|Decorated Pot}}
			\| <code>minecraft:decorated_pot</code>
			\| [[#Decorated Pot\|Decorated Pot]]
	\|-		\|-
	\|colspan="2"\| Anything else		\|colspan="2"\| Anything else
Line 187:		Line 191:

	If the action is 1, this is the direction from which the bell was rung (down=0, up=1, north=2, south=3, west=4, east=5). If the bell was rung by a player, this is the face of the block they clicked on; otherwise, it is based on the bell's facing state. After 5 ticks, if there are raiders nearby, the bell resonates and 40 ticks later causes them to glow for 60 ticks. Whether there are raiders nearby will only be recalculated if 60 ticks have passed since the last recalculation.		If the action is 1, this is the direction from which the bell was rung (down=0, up=1, north=2, south=3, west=4, east=5). If the bell was rung by a player, this is the face of the block they clicked on; otherwise, it is based on the bell's facing state. After 5 ticks, if there are raiders nearby, the bell resonates and 40 ticks later causes them to glow for 60 ticks. Whether there are raiders nearby will only be recalculated if 60 ticks have passed since the last recalculation.

			== Decorated Pot ==

			=== Action ID ===

			There is only one action, with ID '''1''', which causes the decorated pot to play a wobble animation.

			=== Action Parameters ===

			The wobble animation is played when inserting items to the pot, the parameter changes the "wobble style", '''0''' if the interaction is positive, '''1''' if negative and items could not be inserted.

	[[Category:Protocol Details]]		[[Category:Protocol Details]]
	[[Category:Minecraft Modern]]		[[Category:Minecraft Modern]]

imported>LassiPulkkinen: Add Category:Protocol Details.

2024-02-26T18:50:55Z

Add Category:Protocol Details.

← Older revision		Revision as of 18:50, 26 February 2024
Line 188:		Line 188:
	If the action is 1, this is the direction from which the bell was rung (down=0, up=1, north=2, south=3, west=4, east=5). If the bell was rung by a player, this is the face of the block they clicked on; otherwise, it is based on the bell's facing state. After 5 ticks, if there are raiders nearby, the bell resonates and 40 ticks later causes them to glow for 60 ticks. Whether there are raiders nearby will only be recalculated if 60 ticks have passed since the last recalculation.		If the action is 1, this is the direction from which the bell was rung (down=0, up=1, north=2, south=3, west=4, east=5). If the bell was rung by a player, this is the face of the block they clicked on; otherwise, it is based on the bell's facing state. After 5 ticks, if there are raiders nearby, the bell resonates and 40 ticks later causes them to glow for 60 ticks. Whether there are raiders nearby will only be recalculated if 60 ticks have passed since the last recalculation.

			[[Category:Protocol Details]]
	[[Category:Minecraft Modern]]		[[Category:Minecraft Modern]]

imported>WinX64: /* Piston */ Added a rough summary of the missing piston info

2023-03-30T15:33:03Z

Piston: Added a rough summary of the missing piston info

← Older revision		Revision as of 15:33, 30 March 2023
Line 66:		Line 66:
	== Piston ==		== Piston ==

	~~Extends or retracts~~ the piston. Always used on the piston base (either sticky or regular), never on the head~~. Also plays the extending/retracting sound~~.		Controls the state of the piston and affected blocks. Always used on the piston base (either sticky or regular), never on the head.

	{{Need Info\|~~It's unclear what blocks~~ and ~~tile entities~~ the client ~~needs~~ to ~~create~~, ~~and which ones~~ the server ~~creates. From~~ a ~~rough glance~~, ~~it seems like~~ the ~~server changes~~ the piston ~~base~~ block, but ~~the~~ client ~~needs to create~~ the ~~piston head~~, ~~create~~ the ~~block 36es~~, and ~~create~~ the piston moving ~~tile~~ entities. ~~As such~~, the server ~~needs~~ to ~~make~~ the ~~same assumptions as~~ the client, ~~or else ghost~~ blocks ~~may occur~~.}}		{{Need Info\|The tick logic for moving piston block entities is the roughly the same for both client and server, except that the client will wait an extra 5 ticks before setting the pushed blocks to their new state. Why does this happen? Why does the client even set the new blocks on its own in the first place, if their final state is going to be received by the server anyway? Is it a lag-compensation mechanism?}}

			Upon receiving this action, the Notchian client is responsible for:
			* Calculating if the action is possible, and which blocks will be affected;
			* Changing pushed blocks into <code>MOVING_PISTON</code> blocks and their respective moving piston block entities (client-side only);
			* Changing the pushed blocks' new block states once the action is finished (action takes 3 ticks, but blocks are set after an extra 5 ticks; client-side only).

			On the other hand, the server Notchian server is responsible for:
			* Calculating if the action is possible, and which blocks will be affected;
			* Initiating the actual action through the [[Protocol#Block_Action\|Block Action]] packet;
			* Playing the piston extend/retract sound;
			* Changing pushed blocks into <code>MOVING_PISTON</code> blocks and their respective moving piston block entities (server-side only);
			* Immediately sending updates for blocks that would be destroyed by the piston action (through [[Protocol#Block_Update\|Block Update]] or [[Protocol#Update_Section_Blocks\|Update Section Blocks]]);
			* Calculate entity collision mid-push/mid-pull and update their position accordingly;
			* Changing the pushed blocks' new block states once the action is finished (after 3 ticks, through [[Protocol#Block_Update\|Block Update]] or [[Protocol#Update_Section_Blocks\|Update Section Blocks]]).


			{{Warning2\|Some important points to be noted about the Notchian implementations are:
			* The calculation for blocks to be pushed/destroyed is the same on both server and client, and they rely on that assumption. Attempting to change the logic in one side may lead to de-sync issues.
			* Although the server creates <code>MOVING_PISTON</code> blocks and moving piston block entities, they're not sent to the client, and are kept on the server merely to keep track of the action progression (to handle collision, block changes upon completion etc.). The client is responsible for creating such blocks and entities on its side upon receiving [[Protocol#Block_Action\|Block Action]] packet.
			* <code>MOVING_PISTON</code> blocks and moving piston block entities can be received in a [[Protocol#Chunk_Data_and_Update_Light\|Chunk Data]] packet. However, the block entity data is ignored by the client and <code>MOVING_PISTON</code> blocks are set in their default state (empty). This could potentially be intentional, as the piston animation is short (3 ticks long), and the client will subsequently receive updates for the final block states from the server;}}

	=== Action IDs ===		=== Action IDs ===

	~~{{Need Info\|This may have changed in~~ 1~~.13; there is also a~~ ''2'' ~~state that seems~~ to ~~be used if a piston was canceled mid-push (maybe)~~.}}		'''0''' to extend the piston, '''1''' to retract it, and '''2''' to cancel an ongoing extension.

	'''0''' to ~~extend~~ the piston, ~~'''1'''~~ to ~~retract it~~.		In Notchian implementations, action ID '''2''' is defined by when a piston is retracted (e.g.: due to loss of power) mid-extension. The semantics for this action also change based on the type of piston:
			* if the piston is a normal one, the action has the same result as a normal retraction;
			* if the piston is a sticky one, it will be retracted without pulling any blocks.

			{{Warning\|Sending an extension action to an already-extended piston has no effect, but sending retraction actions to an already-retracted piston may cause undesired results, such as the block directly in front of the piston head dissappearing on the client.}}

	=== Action Parameters ===		=== Action Parameters ===

	The direction the piston is facing ~~(which~~ is ~~a metadata field on~~ the piston). ~~This is only used when~~ the piston ~~is retracting~~ to ~~generate~~ the ~~nearest block 36; all other parts appear ignore this parameter and use~~ the ~~piston's actual metadata field~~.		The direction the piston is facing.

			Any value can be sent for piston extension, since the direction is infered from the piston's block state, but it must match the actual direction for piston retractions (action ID '''1''' and '''2''').

			{{Warning\|Sending a mismatched direction for piston extension has no effect, but sending a mismatched direction to piston retractions will cause the piston block to assume the new sent direction on the client.}}

	{\| class="wikitable"		{\| class="wikitable"

imported>WinX64: Beacon block action no longer exists

2023-03-26T05:04:29Z

Beacon block action no longer exists

@@ Line 26: / Line 26: @@
   | {{Minecraft Wiki|Ender Chest}}
   | <code>minecraft:ender_chest</code>
   |-
   | {{Minecraft Wiki|Mob Spawner}}
@@ Line 119: / Line 115: @@
 When the action ID is 1, this is the number of players who have the chest open. If 0, then the chest is closed; if 1 or more the chest is open.
 == Spawner ==

imported>WinX64: Updated chest info and merged it with the ender chest section

2023-03-26T01:26:06Z

Updated chest info and merged it with the ender chest section

← Older revision		Revision as of 01:26, 26 March 2023
Line 19:		Line 19:
	\| {{Minecraft Wiki\|Chest}}		\| {{Minecraft Wiki\|Chest}}
	\| <code>minecraft:chest</code>		\| <code>minecraft:chest</code>
	\|rowspan="2"\| [[#Chest\|Chest]]		\|rowspan="3"\| [[#Chest\|Chest]]
	\|-		\|-
	\| {{Minecraft Wiki\|Trapped Chest}}		\| {{Minecraft Wiki\|Trapped Chest}}
Line 26:		Line 26:
	\| {{Minecraft Wiki\|Ender Chest}}		\| {{Minecraft Wiki\|Ender Chest}}
	\| <code>minecraft:ender_chest</code>		\| <code>minecraft:ender_chest</code>
	~~\| [[#Ender Chest\|Ender Chest]]~~
	\|-		\|-
	\| {{Minecraft Wiki\|Beacon}}		\| {{Minecraft Wiki\|Beacon}}
Line 113:		Line 112:
	=== Action IDs ===		=== Action IDs ===

	There is only one action, with ID '''1'''. It is used to update the number of players who are looking in the chest, which in turn is used to update lid animation.		There is only one action, with ID '''1'''. It is used to update the number of players who are looking in the chest, which in turn is used to update lid animation.

	~~This value seems to be recalculated~~ and ~~sent~~ every 20 ticks.		The Notchian server sends this whenever a player opens or closes the chest, and every 5 ticks (0.25 seconds) while at least one player has the chest open.

	=== Action Parameters ===		=== Action Parameters ===

	When the action ID is 1, this is the number of players who have the chest open. ~~If 0, then the chest is closed; if 1 or more the chest is open.~~		When the action ID is 1, this is the number of players who have the chest open. If 0, then the chest is closed; if 1 or more the chest is open.

	~~== Ender Chest ==~~

	~~=== Action IDs ===~~

	There is only one action, with ID '''1'''. It is used to update the number of players who are looking in the ender chest, which in turn is used to update lid animation. This is recalculated and resent every 80 ticks (4 seconds), even if the value hasn't changed.

	~~=== Action Parameters ===~~

	~~When the action ID is 1, this is the number of players who have the chest open.~~ If 0, then the chest is closed; if 1 or more the chest is open.

	== Beacon ==		== Beacon ==

imported>VidTu: Fix capitalization and rename "param" to "Parameters"

2022-11-26T23:50:04Z

Fix capitalization and rename "param" to "Parameters"

← Older revision		Revision as of 23:50, 26 November 2022
Line 65:		Line 65:
	Ignored, always 0.		Ignored, always 0.

	=== Action ~~param~~ ===		=== Action Parameters ===

	Ignored, always 0.		Ignored, always 0.
Line 81:		Line 81:
	'''0''' to extend the piston, '''1''' to retract it.		'''0''' to extend the piston, '''1''' to retract it.

	=== Action ~~param~~ ===		=== Action Parameters ===

	The direction the piston is facing (which is a metadata field on the piston). This is only used when the piston is retracting to generate the nearest block 36; all other parts appear ignore this parameter and use the piston's actual metadata field.		The direction the piston is facing (which is a metadata field on the piston). This is only used when the piston is retracting to generate the nearest block 36; all other parts appear ignore this parameter and use the piston's actual metadata field.
Line 117:		Line 117:
	This value seems to be recalculated and sent every 20 ticks.		This value seems to be recalculated and sent every 20 ticks.

	=== Action ~~param~~ ===		=== Action Parameters ===

	When the action ID is 1, this is the number of players who have the chest open. If 0, then the chest is closed; if 1 or more the chest is open.		When the action ID is 1, this is the number of players who have the chest open. If 0, then the chest is closed; if 1 or more the chest is open.

	== Ender ~~chest~~ ==		== Ender Chest ==

	=== Action IDs ===		=== Action IDs ===
Line 127:		Line 127:
	There is only one action, with ID '''1'''. It is used to update the number of players who are looking in the ender chest, which in turn is used to update lid animation. This is recalculated and resent every 80 ticks (4 seconds), even if the value hasn't changed.		There is only one action, with ID '''1'''. It is used to update the number of players who are looking in the ender chest, which in turn is used to update lid animation. This is recalculated and resent every 80 ticks (4 seconds), even if the value hasn't changed.

	=== Action ~~param~~ ===		=== Action Parameters ===

	When the action ID is 1, this is the number of players who have the chest open. If 0, then the chest is closed; if 1 or more the chest is open.		When the action ID is 1, this is the number of players who have the chest open. If 0, then the chest is closed; if 1 or more the chest is open.
Line 139:		Line 139:
	Note that the beacon beam is also recomputed every 80 ticks (4 seconds), but no block action occurs when that happens. The block action allows placing of a beacon and recoloring of the beam to potentially be instant, but does not make all other changes to the beam instant.		Note that the beacon beam is also recomputed every 80 ticks (4 seconds), but no block action occurs when that happens. The block action allows placing of a beacon and recoloring of the beam to potentially be instant, but does not make all other changes to the beam instant.

	=== Action ~~param~~ ===		=== Action Parameters ===

	Ignored.		Ignored.
Line 149:		Line 149:
	There is only one action, with ID '''1''', which resets the delay in the spawner to the minimum spawn delay.		There is only one action, with ID '''1''', which resets the delay in the spawner to the minimum spawn delay.

	=== Action ~~param~~ ===		=== Action Parameters ===

	Ignored.		Ignored.

	== End ~~gateway~~ ==		== End Gateway ==

	=== Action ID ===		=== Action ID ===
Line 159:		Line 159:
	There is only one action, with ID '''1''', which triggers the {{Minecraft Wiki\|End Gateway (block)#Beam\|purple beam}} emitted by the end gateway when an entity passes through it.		There is only one action, with ID '''1''', which triggers the {{Minecraft Wiki\|End Gateway (block)#Beam\|purple beam}} emitted by the end gateway when an entity passes through it.

	=== Action ~~param~~ ===		=== Action Parameters ===

	Ignored.		Ignored.
Line 171:		Line 171:
	There is only one action: 1, which updates the number of players who are looking in the shulker box.		There is only one action: 1, which updates the number of players who are looking in the shulker box.

	=== Action ~~param~~ ===		=== Action Parameters ===

	If the action is 1, updates the number of players who have the shulker box open. If 0, the shulker box enters its closing animation; if 1, the shulker box enters its opening animation.		If the action is 1, updates the number of players who have the shulker box open. If 0, the shulker box enters its closing animation; if 1, the shulker box enters its opening animation.
Line 183:		Line 183:
	There is only one action: 1, which triggers the bell animation.		There is only one action: 1, which triggers the bell animation.

	=== Action ~~param~~ ===		=== Action Parameters ===

	If the action is 1, this is the direction from which the bell was rung (down=0, up=1, north=2, south=3, west=4, east=5). If the bell was rung by a player, this is the face of the block they clicked on; otherwise, it is based on the bell's facing state. After 5 ticks, if there are raiders nearby, the bell resonates and 40 ticks later causes them to glow for 60 ticks. Whether there are raiders nearby will only be recalculated if 60 ticks have passed since the last recalculation.		If the action is 1, this is the direction from which the bell was rung (down=0, up=1, north=2, south=3, west=4, east=5). If the bell was rung by a player, this is the face of the block they clicked on; otherwise, it is based on the bell's facing state. After 5 ticks, if there are raiders nearby, the bell resonates and 40 ticks later causes them to glow for 60 ticks. Whether there are raiders nearby will only be recalculated if 60 ticks have passed since the last recalculation.

	[[Category:Minecraft Modern]]		[[Category:Minecraft Modern]]

imported>ImHarvol: /* Action IDs */

2021-08-15T08:42:54Z

Action IDs

← Older revision		Revision as of 08:42, 15 August 2021
Line 115:		Line 115:
	There is only one action, with ID '''1'''. It is used to update the number of players who are looking in the chest, which in turn is used to update lid animation.		There is only one action, with ID '''1'''. It is used to update the number of players who are looking in the chest, which in turn is used to update lid animation.

	This value seems to be recalculated every ~~200~~ ticks~~, but isn't resent until a player closes/reopens~~.		This value seems to be recalculated and sent every 20 ticks.

	=== Action param ===		=== Action param ===

imported>Pokechu22: Add Bell

2020-11-21T23:21:59Z

Add Bell

@@ Line 44: / Line 44: @@
 <code>minecraft:''<color>''_shulker_box</code>
   | [[#Shulker Box|Shulker Box]]
   |-
   |colspan="2"| Anything else
@@ Line 158: / Line 162: @@
 Ignored.
 == Shulker Box ==
@@ Line 172: / Line 174: @@
 If the action is 1, updates the number of players who have the shulker box open.  If 0, the shulker box enters its closing animation; if 1, the shulker box enters its opening animation.

imported>Pokechu22: /* Action ID */ It actually triggers the purple beam

2018-09-06T02:15:51Z

Action ID: It actually triggers the purple beam

← Older revision		Revision as of 02:15, 6 September 2018
Line 153:		Line 153:
	=== Action ID ===		=== Action ID ===

	There is only one action, with ID '''1''', which triggers the {{Minecraft Wiki\|End Gateway (block)#Beam\|~~magenta~~ beam}} emitted by the end gateway when an entity passes through it.		There is only one action, with ID '''1''', which triggers the {{Minecraft Wiki\|End Gateway (block)#Beam\|purple beam}} emitted by the end gateway when an entity passes through it.

	=== Action param ===		=== Action param ===

imported>Pokechu22: /* Action IDs */ Possibly outdated for pistons

2018-09-05T23:09:18Z

Action IDs: Possibly outdated for pistons

← Older revision		Revision as of 23:09, 5 September 2018
Line 72:		Line 72:

	=== Action IDs ===		=== Action IDs ===

			{{Need Info\|This may have changed in 1.13; there is also a ''2'' state that seems to be used if a piston was canceled mid-push (maybe).}}

	'''0''' to extend the piston, '''1''' to retract it.		'''0''' to extend the piston, '''1''' to retract it.