SyncBot: Fix template calls: add MC/ prefix

2026-04-09T20:34:17Z

Fix template calls: add MC/ prefix

← Older revision		Revision as of 20:34, 9 April 2026
Line 1:		Line 1:
	{{DISPLAYTITLE:Legacy ''Pocket Edition'' protocol}}		{{DISPLAYTITLE:Legacy ''Pocket Edition'' protocol}}
	{{about\|outdated information for ''[[Minecraft:Pocket Edition]]''\|a newer ''Pocket Edition'' protocol\|Pocket Edition protocol\|the protocol documentation for the latest version of {{BE}}\|Bedrock Edition protocol}}		{{about\|outdated information for ''[[Minecraft:Pocket Edition]]''\|a newer ''Pocket Edition'' protocol\|Pocket Edition protocol\|the protocol documentation for the latest version of {{MC/BE}}\|Bedrock Edition protocol}}
	{{outdated\|edition=bedrock}}		{{outdated\|edition=bedrock}}

	This article documents the '''protocol''' which ''[[Minecraft:Pocket Edition]]'' used before it was replaced by a [[Minecraft:Pocket Edition protocol\|newer ''Pocket Edition'' protocol]].{{~~when~~}}		This article documents the '''protocol''' which ''[[Minecraft:Pocket Edition]]'' used before it was replaced by a [[Minecraft:Pocket Edition protocol\|newer ''Pocket Edition'' protocol]].{{MC/When}}

	Unlike the {{JE}} protocol, this protocol uses UDP with (so far observed, at least) one message per packet. This makes the protocol easier to work with when it comes to packet serialization, and might offer latency improvements, but will inevitably have the usual UDP issues (packets lost, truncated, duplicated, out-of-order, etc.).		Unlike the {{MC/JE}} protocol, this protocol uses UDP with (so far observed, at least) one message per packet. This makes the protocol easier to work with when it comes to packet serialization, and might offer latency improvements, but will inevitably have the usual UDP issues (packets lost, truncated, duplicated, out-of-order, etc.).

	As of v0.9.0 alpha, clients appear to search for servers on only port 19132.		As of v0.9.0 alpha, clients appear to search for servers on only port 19132.
Line 64:		Line 64:
	Please note that packets 0x09 through 0x13 are not documented (yet).		Please note that packets 0x09 through 0x13 are not documented (yet).

	{{~~anchor~~\|0x01}}		{{MC/Anchor\|0x01}}
	=== ID_CONNECTED_PING_OPEN_CONNECTIONS (0x01) ===		=== ID_CONNECTED_PING_OPEN_CONNECTIONS (0x01) ===

Line 97:		Line 97:
	Clients start out by sending this packet to the IP broadcast address on port 19132 repeatedly (approx once per second) when joining a server was chosen on the main screen, and stops when the user selects a server (or leaves the screen). The ping ID from the client increases over time, and appears to be the number of milliseconds since the client program was started (might be used to measure server response latency).		Clients start out by sending this packet to the IP broadcast address on port 19132 repeatedly (approx once per second) when joining a server was chosen on the main screen, and stops when the user selects a server (or leaves the screen). The ping ID from the client increases over time, and appears to be the number of milliseconds since the client program was started (might be used to measure server response latency).

	{{~~anchor~~\|0x02}}		{{MC/Anchor\|0x02}}
	=== ID_UNCONNECTED_PING_OPEN_CONNECTIONS (0x02) ===		=== ID_UNCONNECTED_PING_OPEN_CONNECTIONS (0x02) ===

Line 131:		Line 131:
	Same as [[#0x01\|ID_CONNECTED_PING_OPEN_CONNECTIONS (0x01)]], but with the Packet ID changed.		Same as [[#0x01\|ID_CONNECTED_PING_OPEN_CONNECTIONS (0x01)]], but with the Packet ID changed.

	{{~~anchor~~\|0x05}}		{{MC/Anchor\|0x05}}

	=== ID_OPEN_CONNECTION_REQUEST_1 (0x05) ===		=== ID_OPEN_CONNECTION_REQUEST_1 (0x05) ===
Line 177:		Line 177:


	{{~~anchor~~\|0x06}}		{{MC/Anchor\|0x06}}

	=== ID_OPEN_CONNECTION_REPLY_1 (0x06) ===		=== ID_OPEN_CONNECTION_REPLY_1 (0x06) ===
Line 222:		Line 222:


	{{~~anchor~~\|0x07}}		{{MC/Anchor\|0x07}}

	=== ID_OPEN_CONNECTION_REQUEST_2 (0x07) ===		=== ID_OPEN_CONNECTION_REQUEST_2 (0x07) ===
Line 271:		Line 271:
	Sent from client in response to packet 0x06.		Sent from client in response to packet 0x06.

	{{~~anchor~~\|0x08}}		{{MC/Anchor\|0x08}}

	=== ID_OPEN_CONNECTION_REPLY_2 (0x08) ===		=== ID_OPEN_CONNECTION_REPLY_2 (0x08) ===
Line 321:		Line 321:


	{{~~anchor~~\|0x1A}}		{{MC/Anchor\|0x1A}}
	=== ID_INCOMPATIBLE_PROTOCOL_VERSION (0x1A) ===		=== ID_INCOMPATIBLE_PROTOCOL_VERSION (0x1A) ===

Line 359:		Line 359:
	Sent when the server doesn't support the RakNet protocol specified in 0x05.		Sent when the server doesn't support the RakNet protocol specified in 0x05.

	{{~~anchor~~\|0x1C}}		{{MC/Anchor\|0x1C}}

	=== ID_UNCONNECTED_PING_OPEN_CONNECTIONS (0x1C) ===		=== ID_UNCONNECTED_PING_OPEN_CONNECTIONS (0x1C) ===
Line 407:		Line 407:
	<b>Since MCPE 0.11.0, the server name has a different format.</b>		<b>Since MCPE 0.11.0, the server name has a different format.</b>

	{{~~anchor~~\|0x1D}}		{{MC/Anchor\|0x1D}}

	=== ID_ADVERTISE_SYSTEM (0x1D) ===		=== ID_ADVERTISE_SYSTEM (0x1D) ===
Line 485:		Line 485:
	The receiver will use the Packet number in the 0xC0 packet and send it back.		The receiver will use the Packet number in the 0xC0 packet and send it back.

	{{~~anchor~~\|0xA0}}		{{MC/Anchor\|0xA0}}

	=== NAK (0xA0) ===		=== NAK (0xA0) ===
Line 570:		Line 570:
	The second packet number is optional and only there when bool is false.		The second packet number is optional and only there when bool is false.

	{{~~anchor~~\|Packet_Encapsulation}}		{{MC/Anchor\|Packet_Encapsulation}}

	== Packet Encapsulation format ==		== Packet Encapsulation format ==
Line 670:		Line 670:


	{{~~anchor~~\|Encapsulated_Login_packets}}		{{MC/Anchor\|Encapsulated_Login_packets}}

	== Encapsulated Login packets ==		== Encapsulated Login packets ==
Line 2,619:		Line 2,619:

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

	[[Category:Pocket Edition]]		[[Category:Pocket Edition]]
	{{~~license~~ wiki.vg}}		{{MC/License wiki.vg}}

SyncBot: Remove broken links to missing pages

2026-04-09T15:54:17Z

Remove broken links to missing pages

← Older revision		Revision as of 15:54, 9 April 2026
Line 7:		Line 7:
	Unlike the {{JE}} protocol, this protocol uses UDP with (so far observed, at least) one message per packet. This makes the protocol easier to work with when it comes to packet serialization, and might offer latency improvements, but will inevitably have the usual UDP issues (packets lost, truncated, duplicated, out-of-order, etc.).		Unlike the {{JE}} protocol, this protocol uses UDP with (so far observed, at least) one message per packet. This makes the protocol easier to work with when it comes to packet serialization, and might offer latency improvements, but will inevitably have the usual UDP issues (packets lost, truncated, duplicated, out-of-order, etc.).

	As of ~~[[Minecraft:~~v0.9.0 alpha]], clients appear to search for servers on only port 19132.		As of v0.9.0 alpha, clients appear to search for servers on only port 19132.

	Clients don't pick any specific port to listen on.		Clients don't pick any specific port to listen on.
Line 674:		Line 674:
	== Encapsulated Login packets ==		== Encapsulated Login packets ==

	After packets 0x05 through 0x08 are sent, the client will send the first encapsulated packets (0x09 through 0x13). After 0x13 the game begins. You can check the login sequence ~~[[Minecraft:Pocket_Editon_Login\|~~here]].		After packets 0x05 through 0x08 are sent, the client will send the first encapsulated packets (0x09 through 0x13). After 0x13 the game begins. You can check the login sequence here.

	=== Client Connect (0x09) ===		=== Client Connect (0x09) ===

imported>RedX at 18:29, 27 December 2025

2025-12-27T18:29:44Z

Show changes

Minecraft:Legacy Pocket Edition protocol - Revision history

SyncBot: Fix template calls: add MC/ prefix

SyncBot: Remove broken links to missing pages

imported>RedX at 18:29, 27 December 2025