Protocol FAQ - Revision history

imported>Rmheuer: /* Offline mode */ Encryption is possible in offline mode now

2024-10-09T13:33:58Z

Offline mode: Encryption is possible in offline mode now

← Older revision		Revision as of 13:33, 9 October 2024
Line 54:		Line 54:

	=== Offline mode ===		=== Offline mode ===
	If the server is in offline mode, it will not send the [[Protocol#Encryption Request\|Encryption Request]] packet, and likewise, the client should not send [[Protocol#Encryption Response\|Encryption Response]]. In this case, encryption is never enabled, and no authentication is performed.		If the Notchian server is in offline mode, it will not send the [[Protocol#Encryption Request\|Encryption Request]] packet, and likewise, the client should not send [[Protocol#Encryption Response\|Encryption Response]]. In this case, encryption is never enabled, and no authentication is performed.

	Clients can tell that a server is in offline mode if the server sends a [[Protocol#Login Success\|Login Success]] without sending [[Protocol#Encryption Request\|Encryption Request]].		Clients can tell that a server is in offline mode if the server sends a [[Protocol#Login Success\|Login Success]] without sending [[Protocol#Encryption Request\|Encryption Request]].

			Versions 1.20.5 and newer support protocol encryption in offline mode, in which case the [[Protocol#Encryption Request\|Encryption Request]] packet can be sent with Should Authenticate set to false, and both the client and server should not authenticate with Mojang. However, it's currently not possible to configure the Notchian server to do this.

	== What does the normal status ping sequence look like? ==		== What does the normal status ping sequence look like? ==

imported>LassiPulkkinen: The IRC channel still exists, so include both.

2024-09-04T03:18:31Z

The IRC channel still exists, so include both.

← Older revision		Revision as of 03:18, 4 September 2024
Line 1:		Line 1:
	People very, very often have questions regarding the Minecraft Modern [[Protocol]], so we'll try to address some of the most common ones on this document. If you're still having trouble, join us on our [https://discord.gg/Tf4xwK3Ke7 discord].		People very, very often have questions regarding the Minecraft Modern [[Protocol]], so we'll try to address some of the most common ones on this document. If you're still having trouble, join us on our [https://discord.gg/Tf4xwK3Ke7 discord] or our IRC channel [ircs://irc.libera.chat:6697/mcdevs #mcdevs on irc.libera.chat].

	== Is the protocol documentation complete? ==		== Is the protocol documentation complete? ==

imported>Wiserdis: Changed the help link to the discord

2024-09-04T00:39:17Z

Changed the help link to the discord

← Older revision		Revision as of 00:39, 4 September 2024
Line 1:		Line 1:
	People very, very often have questions regarding the Minecraft Modern [[Protocol]], so we'll try to address some of the most common ones on this document. If you're still having trouble, join us on ~~IRC, channel~~ [~~ircs~~://~~irc~~.~~libera.chat:6697~~/~~mcdevs #mcdevs on irc.libera.chat~~].		People very, very often have questions regarding the Minecraft Modern [[Protocol]], so we'll try to address some of the most common ones on this document. If you're still having trouble, join us on our [https://discord.gg/Tf4xwK3Ke7 discord].

	== Is the protocol documentation complete? ==		== Is the protocol documentation complete? ==

imported>LassiPulkkinen: /* …my player isn't spawning! */ Typo.

2024-08-26T23:20:26Z

…my player isn't spawning!: Typo.

← Older revision		Revision as of 23:20, 26 August 2024
Line 78:		Line 78:
	* The player is in a loaded chunk (sent via [[Protocol#Chunk Data and Update Light\|Chunk Data and Update Light]]).		* The player is in a loaded chunk (sent via [[Protocol#Chunk Data and Update Light\|Chunk Data and Update Light]]).
	* The player is below the minimum world height or above the maximum world height (teleported via [[Protocol#Synchronize Player Position\|Synchronize Player Position]]).		* The player is below the minimum world height or above the maximum world height (teleported via [[Protocol#Synchronize Player Position\|Synchronize Player Position]]).
	* The player in spectator mode.		* The player is in spectator mode.
	* The player is dead (set via [[Protocol#Set Health\|Set Health]] or [[Protocol#Combat Death\|Combat Death]]).		* The player is dead (set via [[Protocol#Set Health\|Set Health]] or [[Protocol#Combat Death\|Combat Death]]).

imported>LassiPulkkinen: /* …my player isn't spawning! */ The loading screen has a 30 second timeout.

2024-08-26T23:07:07Z

…my player isn't spawning!: The loading screen has a 30 second timeout.

← Older revision		Revision as of 23:07, 26 August 2024
Line 74:		Line 74:
	=== …my player isn't spawning! ===		=== …my player isn't spawning! ===

	The Minecraft client will wait at the "Loading Terrain..." screen until late in the login sequence. As of 1.~~20.4~~, in order for the client to spawn, it must have received a [[Protocol#Game Event\|Game Event]] packet with event 13 ("Start waiting for level chunks"), and at least one of the following conditions must be met:		The Minecraft client will wait at the "Loading Terrain..." screen until late in the login sequence. As of 1.21, in order for the client to spawn, it must have received a [[Protocol#Game Event\|Game Event]] packet with event 13 ("Start waiting for level chunks"), and at least one of the following conditions must be met:

	* The player is in a loaded chunk (sent via [[Protocol#Chunk Data and Update Light\|Chunk Data and Update Light]]).		* The player is in a loaded chunk (sent via [[Protocol#Chunk Data and Update Light\|Chunk Data and Update Light]]).
Line 80:		Line 80:
	* The player in spectator mode.		* The player in spectator mode.
	* The player is dead (set via [[Protocol#Set Health\|Set Health]] or [[Protocol#Combat Death\|Combat Death]]).		* The player is dead (set via [[Protocol#Set Health\|Set Health]] or [[Protocol#Combat Death\|Combat Death]]).

			The client will also spawn after spending 30 seconds in the loading screen, even if it never received Game Event 13.

	In past versions, you could either (1.19.3 through 1.20.1) send the default spawn position packet or (pre-1.19.3) send the player position packet. In general, try sending packets that inform the client about the player's position in the world in order to get past the loading terrain screen.		In past versions, you could either (1.19.3 through 1.20.1) send the default spawn position packet or (pre-1.19.3) send the player position packet. In general, try sending packets that inform the client about the player's position in the world in order to get past the loading terrain screen.

imported>Targz: /* I think I've done everything right, but… */ updated for 1.21

2024-07-20T21:28:27Z

I think I've done everything right, but…: updated for 1.21

← Older revision		Revision as of 21:28, 20 July 2024
Line 83:		Line 83:
	In past versions, you could either (1.19.3 through 1.20.1) send the default spawn position packet or (pre-1.19.3) send the player position packet. In general, try sending packets that inform the client about the player's position in the world in order to get past the loading terrain screen.		In past versions, you could either (1.19.3 through 1.20.1) send the default spawn position packet or (pre-1.19.3) send the player position packet. In general, try sending packets that inform the client about the player's position in the world in order to get past the loading terrain screen.

	As of 1.~~20.4~~, the minimum packets that need to be received and sent by the server in order to get the client past the loading terrain screen and into the world appear to be:		In version 1.21, it became required to send the known packs packet with <code>minecraft:core</code> version <code>1.21</code>.

			As of 1.21, the minimum packets that need to be received and sent by the server in order to get the client past the loading terrain screen and into the world appear to be:

	# Receive [[Protocol#Handshake\|Handshake]]		# Receive [[Protocol#Handshake\|Handshake]]
Line 89:		Line 91:
	# Send [[Protocol#Login Success\|Login Success]]		# Send [[Protocol#Login Success\|Login Success]]
	# Receive [[Protocol#Login Acknowledged\|Login Acknowledged]]		# Receive [[Protocol#Login Acknowledged\|Login Acknowledged]]
	# Send [[Protocol#Registry Data\|Registry Data]]		# Send [[Protocol#Clientbound Known Packs\|Clientbound Known Packs]]
			# Receive [[Protocol#Serverbound Known Packs\|Serverbound Known Packs]]
			# Send multiple [[Protocol#Registry Data\|Registry Data]]
	# Send [[Protocol#Finish Configuration\|Finish Configuration]]		# Send [[Protocol#Finish Configuration\|Finish Configuration]]
	# Receive [[Protocol#Acknowledge Finish Configuration\|Acknowledge Finish Configuration]]		# Receive [[Protocol#Acknowledge Finish Configuration\|Acknowledge Finish Configuration]]

imported>Sas: Clarify default registries obtaining

2024-07-20T20:22:22Z

Clarify default registries obtaining

← Older revision		Revision as of 20:22, 20 July 2024
Line 96:		Line 96:
	# Send [[Protocol#Chunk Data and Update Light\|Chunk Data and Update Light]] and/or [[Protocol#Synchronize Player Position\|Synchronize Player Position]] (see above)		# Send [[Protocol#Chunk Data and Update Light\|Chunk Data and Update Light]] and/or [[Protocol#Synchronize Player Position\|Synchronize Player Position]] (see above)

	The most difficult part of this may be sending any necessary NBTs in the [[Protocol#Registry_Data\|Registry Data]] packet. ~~You~~ will probably need to record one from the standard server and replay it. Or you can find someone who has done that already, for example in [https://gist.github.com/Norbiros/f604ce46821e68c50260a169a9921560 Norbiros' gist]. You can also find JSON representation of this packet in [https://github.com/PrismarineJS/minecraft-data/blob/master/data/pc/1.20.2/loginPacket.json PrismarineJS/minecraft-data repo on GitHub].		The most difficult part of this may be sending any necessary NBTs in the [[Protocol#Registry_Data\|Registry Data]] packet. Note that if you tell the Notchian client you have 0 known packs, it will blatantly lie to you, so you will probably need to record one from the standard server and replay it. Or you can find someone who has done that already, for example in [https://gist.github.com/Norbiros/f604ce46821e68c50260a169a9921560 Norbiros' gist]. You can also find JSON representation of this packet in [https://github.com/PrismarineJS/minecraft-data/blob/master/data/pc/1.20.2/loginPacket.json PrismarineJS/minecraft-data repo on GitHub].

	=== …chunks are randomly showing and disappearing! ===		=== …chunks are randomly showing and disappearing! ===

imported>Targz: /* What's the normal login sequence for a client? */ Added known packs packets for 1.21 login sequence

2024-07-16T00:10:45Z

What's the normal login sequence for a client?: Added known packs packets for 1.21 login sequence

← Older revision		Revision as of 00:10, 16 July 2024
Line 8:		Line 8:
	(This is about joining a Minecraft server. See [[Microsoft Authentication Scheme]] for how to log in to a Minecraft account, and [[Protocol Encryption]] for details on player authentication during server login.)		(This is about joining a Minecraft server. See [[Microsoft Authentication Scheme]] for how to log in to a Minecraft account, and [[Protocol Encryption]] for details on player authentication during server login.)

	The recommended login sequence as of 1.~~20.4~~ looks like this, where '''C''' is the client and '''S''' is the server:		The recommended login sequence as of 1.21 looks like this, where '''C''' is the client and '''S''' is the server:
	# Client connects to the server		# Client connects to the server
	# '''C'''→'''S''': [[Protocol#Handshake\|Handshake]] State=2		# '''C'''→'''S''': [[Protocol#Handshake\|Handshake]] State=2
Line 23:		Line 23:
	# '''S''' → '''C''': [[Protocol#Clientbound Plugin Message (configuration)\|Clientbound Plugin Message]] (Optional, [[Plugin channel#minecraft%3Abrand\|<code>minecraft:brand</code>]] with the server's brand)		# '''S''' → '''C''': [[Protocol#Clientbound Plugin Message (configuration)\|Clientbound Plugin Message]] (Optional, [[Plugin channel#minecraft%3Abrand\|<code>minecraft:brand</code>]] with the server's brand)
	# '''S''' → '''C''': [[Protocol#Feature Flags\|Feature Flags]] (Optional)		# '''S''' → '''C''': [[Protocol#Feature Flags\|Feature Flags]] (Optional)
	# '''S''' → '''C''': [[Protocol#Registry Data\|Registry Data]]		# '''S''' → '''C''': [[Protocol#Clientbound Known Packs\|Clientbound Known Packs]]
			# '''C''' → '''S''': [[Protocol#Serverbound Known Packs\|Serverbound Known Packs]]
			# '''S''' → '''C''': [[Protocol#Registry Data\|Registry Data]] (Multiple)
	# '''S''' → '''C''': [[Protocol#Update Tags (configuration)\|Update Tags]] (Optional)		# '''S''' → '''C''': [[Protocol#Update Tags (configuration)\|Update Tags]] (Optional)
	# '''S''' → '''C''': [[Protocol#Finish Configuration\|Finish Configuration]]		# '''S''' → '''C''': [[Protocol#Finish Configuration\|Finish Configuration]]

imported>Mudkipdev at 15:26, 14 July 2024

2024-07-14T15:26:37Z

← Older revision		Revision as of 15:26, 14 July 2024
Line 12:		Line 12:
	# '''C'''→'''S''': [[Protocol#Handshake\|Handshake]] State=2		# '''C'''→'''S''': [[Protocol#Handshake\|Handshake]] State=2
	# '''C'''→'''S''': [[Protocol#Login Start\|Login Start]]		# '''C'''→'''S''': [[Protocol#Login Start\|Login Start]]
	# '''S'''→'''C''': [[Protocol#Encryption Request\|Encryption Request]] (~~Only if server is in online mode~~)		# '''S'''→'''C''': [[Protocol#Encryption Request\|Encryption Request]] (optional)
	# Client auth (Only if server sent Encryption Request)		# Client auth (Only if server sent Encryption Request)
	# '''C'''→'''S''': [[Protocol#Encryption Response\|Encryption Response]] (Only if server sent Encryption Request)		# '''C'''→'''S''': [[Protocol#Encryption Response\|Encryption Response]] (Only if server sent Encryption Request)

imported>LassiPulkkinen: Move Offline mode section under What's the normal login sequence for a client?; mention in packet trace.

2024-06-02T14:26:57Z

Move Offline mode section under What's the normal login sequence for a client?; mention in packet trace.

← Older revision		Revision as of 14:26, 2 June 2024
Line 12:		Line 12:
	# '''C'''→'''S''': [[Protocol#Handshake\|Handshake]] State=2		# '''C'''→'''S''': [[Protocol#Handshake\|Handshake]] State=2
	# '''C'''→'''S''': [[Protocol#Login Start\|Login Start]]		# '''C'''→'''S''': [[Protocol#Login Start\|Login Start]]
	# '''S'''→'''C''': [[Protocol#Encryption Request\|Encryption Request]]		# '''S'''→'''C''': [[Protocol#Encryption Request\|Encryption Request]] (Only if server is in online mode)
	# Client auth		# Client auth (Only if server sent Encryption Request)
	# '''C'''→'''S''': [[Protocol#Encryption Response\|Encryption Response]]		# '''C'''→'''S''': [[Protocol#Encryption Response\|Encryption Response]] (Only if server sent Encryption Request)
	# Server auth, both enable encryption		# Server auth, both enable encryption (Only if server sent Encryption Request)
	# '''S''' → '''C''': [[Protocol#Set Compression\|Set Compression]] (Optional, enables compression)		# '''S''' → '''C''': [[Protocol#Set Compression\|Set Compression]] (Optional, enables compression)
	# '''S''' → '''C''': [[Protocol#Login Success\|Login Success]]		# '''S''' → '''C''': [[Protocol#Login Success\|Login Success]]
Line 50:		Line 50:
	# '''S''' → '''C''': [[Protocol#Chunk Data and Update Light\|Chunk Data and Update Light]] (One sent for each chunk in a circular area centered on the player's position)		# '''S''' → '''C''': [[Protocol#Chunk Data and Update Light\|Chunk Data and Update Light]] (One sent for each chunk in a circular area centered on the player's position)
	# '''S''' → '''C''': inventory, entities, etc.		# '''S''' → '''C''': inventory, entities, etc.

			=== Offline mode ===
			If the server is in offline mode, it will not send the [[Protocol#Encryption Request\|Encryption Request]] packet, and likewise, the client should not send [[Protocol#Encryption Response\|Encryption Response]]. In this case, encryption is never enabled, and no authentication is performed.

			Clients can tell that a server is in offline mode if the server sends a [[Protocol#Login Success\|Login Success]] without sending [[Protocol#Encryption Request\|Encryption Request]].

	== What does the normal status ping sequence look like? ==		== What does the normal status ping sequence look like? ==
Line 63:		Line 68:

	(Note that '''C''' is the Notchian client and '''S''' is the Notchian server).		(Note that '''C''' is the Notchian client and '''S''' is the Notchian server).

	~~== Offline mode ==~~
	If the server is in offline mode, it will not send the [[Protocol#Encryption Request\|Encryption Request]] packet, and likewise, the client should not send [[Protocol#Encryption Response\|Encryption Response]]. In this case, encryption is never enabled, and no authentication is performed.

	~~Clients can tell that a server is in offline mode if the server sends a [[Protocol#Login Success\|Login Success]] without sending [[Protocol#Encryption Request\|Encryption Request]].~~

	== I think I've done everything right, but… ==		== I think I've done everything right, but… ==

← Older revision		Revision as of 21:28, 20 July 2024
Line 83:		Line 83:
	In past versions, you could either (1.19.3 through 1.20.1) send the default spawn position packet or (pre-1.19.3) send the player position packet. In general, try sending packets that inform the client about the player's position in the world in order to get past the loading terrain screen.		In past versions, you could either (1.19.3 through 1.20.1) send the default spawn position packet or (pre-1.19.3) send the player position packet. In general, try sending packets that inform the client about the player's position in the world in order to get past the loading terrain screen.

	As of 1.~~20.4~~, the minimum packets that need to be received and sent by the server in order to get the client past the loading terrain screen and into the world appear to be:		In version 1.21, it became required to send the known packs packet with <code>minecraft:core</code> version <code>1.21</code>.

			As of 1.21, the minimum packets that need to be received and sent by the server in order to get the client past the loading terrain screen and into the world appear to be:

	# Receive [[Protocol#Handshake\|Handshake]]		# Receive [[Protocol#Handshake\|Handshake]]
Line 89:		Line 91:
	# Send [[Protocol#Login Success\|Login Success]]		# Send [[Protocol#Login Success\|Login Success]]
	# Receive [[Protocol#Login Acknowledged\|Login Acknowledged]]		# Receive [[Protocol#Login Acknowledged\|Login Acknowledged]]
	# Send [[Protocol#Registry Data\|Registry Data]]		# Send [[Protocol#Clientbound Known Packs\|Clientbound Known Packs]]
			# Receive [[Protocol#Serverbound Known Packs\|Serverbound Known Packs]]
			# Send multiple [[Protocol#Registry Data\|Registry Data]]
	# Send [[Protocol#Finish Configuration\|Finish Configuration]]		# Send [[Protocol#Finish Configuration\|Finish Configuration]]
	# Receive [[Protocol#Acknowledge Finish Configuration\|Acknowledge Finish Configuration]]		# Receive [[Protocol#Acknowledge Finish Configuration\|Acknowledge Finish Configuration]]

← Older revision		Revision as of 00:10, 16 July 2024
Line 8:		Line 8:
	(This is about joining a Minecraft server. See [[Microsoft Authentication Scheme]] for how to log in to a Minecraft account, and [[Protocol Encryption]] for details on player authentication during server login.)		(This is about joining a Minecraft server. See [[Microsoft Authentication Scheme]] for how to log in to a Minecraft account, and [[Protocol Encryption]] for details on player authentication during server login.)

	The recommended login sequence as of 1.~~20.4~~ looks like this, where '''C''' is the client and '''S''' is the server:		The recommended login sequence as of 1.21 looks like this, where '''C''' is the client and '''S''' is the server:
	# Client connects to the server		# Client connects to the server
	# '''C'''→'''S''': [[Protocol#Handshake\|Handshake]] State=2		# '''C'''→'''S''': [[Protocol#Handshake\|Handshake]] State=2
Line 23:		Line 23:
	# '''S''' → '''C''': [[Protocol#Clientbound Plugin Message (configuration)\|Clientbound Plugin Message]] (Optional, [[Plugin channel#minecraft%3Abrand\|<code>minecraft:brand</code>]] with the server's brand)		# '''S''' → '''C''': [[Protocol#Clientbound Plugin Message (configuration)\|Clientbound Plugin Message]] (Optional, [[Plugin channel#minecraft%3Abrand\|<code>minecraft:brand</code>]] with the server's brand)
	# '''S''' → '''C''': [[Protocol#Feature Flags\|Feature Flags]] (Optional)		# '''S''' → '''C''': [[Protocol#Feature Flags\|Feature Flags]] (Optional)
	# '''S''' → '''C''': [[Protocol#Registry Data\|Registry Data]]		# '''S''' → '''C''': [[Protocol#Clientbound Known Packs\|Clientbound Known Packs]]
			# '''C''' → '''S''': [[Protocol#Serverbound Known Packs\|Serverbound Known Packs]]
			# '''S''' → '''C''': [[Protocol#Registry Data\|Registry Data]] (Multiple)
	# '''S''' → '''C''': [[Protocol#Update Tags (configuration)\|Update Tags]] (Optional)		# '''S''' → '''C''': [[Protocol#Update Tags (configuration)\|Update Tags]] (Optional)
	# '''S''' → '''C''': [[Protocol#Finish Configuration\|Finish Configuration]]		# '''S''' → '''C''': [[Protocol#Finish Configuration\|Finish Configuration]]

← Older revision		Revision as of 15:26, 14 July 2024
Line 12:		Line 12:
	# '''C'''→'''S''': [[Protocol#Handshake\|Handshake]] State=2		# '''C'''→'''S''': [[Protocol#Handshake\|Handshake]] State=2
	# '''C'''→'''S''': [[Protocol#Login Start\|Login Start]]		# '''C'''→'''S''': [[Protocol#Login Start\|Login Start]]
	# '''S'''→'''C''': [[Protocol#Encryption Request\|Encryption Request]] (~~Only if server is in online mode~~)		# '''S'''→'''C''': [[Protocol#Encryption Request\|Encryption Request]] (optional)
	# Client auth (Only if server sent Encryption Request)		# Client auth (Only if server sent Encryption Request)
	# '''C'''→'''S''': [[Protocol#Encryption Response\|Encryption Response]] (Only if server sent Encryption Request)		# '''C'''→'''S''': [[Protocol#Encryption Response\|Encryption Response]] (Only if server sent Encryption Request)