Pocket Minecraft Protocol - Revision history

imported>FG6: Fix UpdateBlockPacket table

2023-05-12T23:48:02Z

Fix UpdateBlockPacket table

← Older revision	Revision as of 23:48, 12 May 2023
(No difference)

2023-05-12T23:48:02Z

Fix UpdateBlockPacket table

2022-06-19T00:37:36Z

ID_OPEN_CONNECTION_REQUEST_2 (0x07)

← Older revision	Revision as of 00:37, 19 June 2022
(No difference)

2022-06-19T00:37:36Z

ID_OPEN_CONNECTION_REQUEST_2 (0x07)

← Older revision		Revision as of 00:37, 19 June 2022
Line 256:		Line 256:
	\| class="col1 centeralign" \| 1 + 4 bytes		\| class="col1 centeralign" \| 1 + 4 bytes
	\| class="col2 centeralign" \| <code>0x043f57fefd</code>		\| class="col2 centeralign" \| <code>0x043f57fefd</code>
	\| class="col3" \| ~~An XOR~~ of the ~~server IPv4~~ address		\| class="col3" \| 0x4 for IPv4 and the twos complement of each byte of the servers ip address,
	\|- class="row3"		\|- class="row3"
	\| class="col0 centeralign" \| Server UDP Port		\| class="col0 centeralign" \| Server UDP Port
Line 280:		Line 280:

	{{anchor\|0x08}}		{{anchor\|0x08}}

	=== ID_OPEN_CONNECTION_REPLY_2 (0x08) ===		=== ID_OPEN_CONNECTION_REPLY_2 (0x08) ===

2021-12-22T22:56:49Z

The number they did not know the purpose of is actually an XOR of the server ip.

← Older revision	Revision as of 22:56, 22 December 2021
(No difference)

2021-12-22T22:56:49Z

The number they did not know the purpose of is actually an XOR of the server ip.

← Older revision		Revision as of 22:56, 22 December 2021
Line 253:		Line 253:
	\| class="col4" \|		\| class="col4" \|
	\|- class="row2"		\|- class="row2"
	\| class="col0 centeralign" \| ~~Security + Cookie~~		\| class="col0 centeralign" \| Server Address
	\| class="col1 centeralign" \| 1 + 4 bytes		\| class="col1 centeralign" \| 1 + 4 bytes
	\| class="col2 centeralign" \| <code>0x043f57fefd</code>		\| class="col2 centeralign" \| <code>0x043f57fefd</code>
	\| class="col3" \| ~~Unused, '''not''' constant value*, but usually similar to <code>0x043f57fefd</code>~~		\| class="col3" \| An XOR of the server IPv4 address
	\|- class="row3"		\|- class="row3"
	\| class="col0 centeralign" \| Server UDP Port		\| class="col0 centeralign" \| Server UDP Port
Line 279:		Line 279:
	Sent from client in response to packet 0x06.		Sent from client in response to packet 0x06.

	* Instances have been observed where the value <code>0x043f57fefd</code> is not always present, but similar values are sent.
	{{anchor\|0x08}}		{{anchor\|0x08}}
	=== ID_OPEN_CONNECTION_REPLY_2 (0x08) ===		=== ID_OPEN_CONNECTION_REPLY_2 (0x08) ===

2020-06-08T11:03:58Z

Remove colon

← Older revision	Revision as of 11:03, 8 June 2020
(No difference)

2020-06-08T11:03:58Z

Remove colon

← Older revision		Revision as of 11:03, 8 June 2020
Line 6:		Line 6:
	\|HEADING = Heads up!		\|HEADING = Heads up!
	\|CONTENT = This is outdated information for Minecraft Pocket Edition.'''. For the latest Bedrock Edition protocol documentation see [[Bedrock Protocol]].		\|CONTENT = This is outdated information for Minecraft Pocket Edition.'''. For the latest Bedrock Edition protocol documentation see [[Bedrock Protocol]].
	}}:		}}

	Unlike the Minecraft 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 Minecraft 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.).

2020-06-08T11:03:27Z

Add info about Bedrock Protocol

← Older revision	Revision as of 11:03, 8 June 2020
(No difference)

2020-06-08T11:03:27Z

Add info about Bedrock Protocol

← Older revision		Revision as of 11:03, 8 June 2020
Line 1:		Line 1:
			{{Box
			\|BORDER = #9999FF
			\|BACKGROUND = #99CCFF
			\|WIDTH = 100%
			\|ICON =
			\|HEADING = Heads up!
			\|CONTENT = This is outdated information for Minecraft Pocket Edition.'''. For the latest Bedrock Edition protocol documentation see [[Bedrock Protocol]].
			}}:

	Unlike the Minecraft 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 Minecraft 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.).