Protocol FAQ:zh-cn - Revision history

imported>Zhou2008 at 02:13, 4 January 2022

2022-01-04T02:13:02Z

← Older revision	Revision as of 02:13, 4 January 2022
(No difference)

imported>Zhou2008 at 02:13, 4 January 2022

2022-01-04T02:13:02Z

← Older revision		Revision as of 02:13, 4 January 2022
Line 87:		Line 87:
	The Notchian client may group packets if the size of the packet and delay between the last packet are too small. To solve this issue, you must use the Packet Length to infer there is another packet by comparing it and the data length.		The Notchian client may group packets if the size of the packet and delay between the last packet are too small. To solve this issue, you must use the Packet Length to infer there is another packet by comparing it and the data length.

	{{Need Info\|~~Pseudo code example on how to parse a grouped packet~~?}}		{{Need Info\|关于如何解析分组数据包的伪代码示例?}}

	== ~~How do I open~~/~~save a command block~~? ==		== 如何打开/保存命令方块? ==
	The process to actually open the command block window clientside is somewhat complex; the client actually uses the [[Protocol#Update Block Entity\|Update Block Entity (0x09)]] packet to open it.		The process to actually open the command block window clientside is somewhat complex; the client actually uses the [[Protocol#Update Block Entity\|Update Block Entity (0x09)]] packet to open it.

	First, the client must have at least an {{Minecraft Wiki\|Server.properties#op-permission-level\|OP permission level}} of 2, or else the client will refuse to open the command block. (The op permission level is set with the [[Protocol#Entity Status\|Entity Status]] packet)		First, the client must have at least an {{Minecraft Wiki\|Server.properties#op-permission-level\|OP permission level}} of 2, or else the client will refuse to open the command block. (The op permission level is set with the [[Protocol#Entity Status\|Entity Status]] packet)

	~~To actually open the command block~~:		要想真正打开命令方块:

	# '''C'''→'''S''': [[Protocol#Player Block Placement\|Player Block Placement (0x1C)]], with the position being the command block that was right-clicked.		# '''C'''→'''S''': [[Protocol#Player Block Placement\|Player Block Placement (0x1C)]], with the position being the command block that was right-clicked.

imported>Zhou2008 at 12:15, 3 January 2022

2022-01-03T12:15:40Z

← Older revision	Revision as of 12:15, 3 January 2022
(No difference)

imported>Zhou2008 at 12:15, 3 January 2022

2022-01-03T12:15:40Z

← Older revision		Revision as of 12:15, 3 January 2022
Line 35:		Line 35:
	# '''S''' → '''C''': [[Protocol#Update Light\|更新光照]] (在以玩家位置为中心的正方形中,每个区块都发送一次.)		# '''S''' → '''C''': [[Protocol#Update Light\|更新光照]] (在以玩家位置为中心的正方形中,每个区块都发送一次.)
	# '''S''' → '''C''': [[Protocol#Chunk Data\|区块数据]] (在以玩家位置为中心的正方形中,每个区块都发送一次.)		# '''S''' → '''C''': [[Protocol#Chunk Data\|区块数据]] (在以玩家位置为中心的正方形中,每个区块都发送一次.)
	# '''S''' → '''C''': [[Protocol#World Border\|世界边界]] (~~Once the world is finished loading~~)		# '''S''' → '''C''': [[Protocol#World Border\|世界边界]] (一旦世界完成了加载)
	# '''S''' → '''C''': [[Protocol#Spawn Position\|出生位置]] ("家"出生点,不是客户端登录时的位置)		# '''S''' → '''C''': [[Protocol#Spawn Position\|出生位置]] ("家"出生点,不是客户端登录时的位置)
	# '''S''' → '''C''': [[Protocol#Player Position And Look (clientbound)\|玩家位置和朝向]] (必须,告诉客户端已经准备好生成了)		# '''S''' → '''C''': [[Protocol#Player Position And Look (clientbound)\|玩家位置和朝向]] (必须,告诉客户端已经准备好生成了)
Line 47:		Line 47:

	# '''C''' → '''S''': [[Protocol#Handshake\|握手]] State=1		# '''C''' → '''S''': [[Protocol#Handshake\|握手]] State=1
	# ~~服务器将协议State设置为1~~		# 服务端将协议State设置为1
	# '''C''' → '''S''': [[Protocol#Request\|请求]]		# '''C''' → '''S''': [[Protocol#Request\|请求]]
	# '''S''' → '''C''': [[Protocol#Response\|响应]]		# '''S''' → '''C''': [[Protocol#Response\|响应]]
Line 63:		Line 63:
	在完成了基本操作之后([[Protocol#Handshake\|握手]]、[[Protocol#Login Start\|登录开始]]、[[Protocol#Window Items\|物品栏]]、[[Protocol#Spawn Position\|出生位置]]、[[Protocol#Chunk Data\|区块]]),你需要发送玩家的[[Protocol#Player Position And Look\|初始位置]]来让它们离开"Loading Map"界面.		在完成了基本操作之后([[Protocol#Handshake\|握手]]、[[Protocol#Login Start\|登录开始]]、[[Protocol#Window Items\|物品栏]]、[[Protocol#Spawn Position\|出生位置]]、[[Protocol#Chunk Data\|区块]]),你需要发送玩家的[[Protocol#Player Position And Look\|初始位置]]来让它们离开"Loading Map"界面.

	''~~Note that if the following steps are taken~~, ~~a Minecraft client will spawn the player~~:''		''请注意,如果采取以下步骤,Minecraft客户端将生成玩家:''
	# ~~Do Handshake~~ (~~see~~ [[Protocol Encryption]])		# 握手([[Protocol Encryption\|协议加密]])
	# ~~Send~~ [[Protocol#Spawn Position\|~~Spawn Position~~]] ~~packet~~		# 发送[[Protocol#Spawn Position\|出生位置]]数据包
	# ~~Send~~ [[Protocol#Player Position And Look (clientbound)\|~~Player Position And Look (clientbound)~~]] ~~packet~~		# 发送[[Protocol#Player Position And Look (clientbound)\|玩家位置和朝向]]数据包

	~~While the above steps are sufficient for Minecraft~~ 1.4.5, it is good form to send packets that inform the client about the world around the player before allowing the player to spawn.		虽然上述步骤对Minecraft 1.4.5来说已经足够了, it is good form to send packets that inform the client about the world around the player before allowing the player to spawn.

	=== ...我的客户端没有收到完整的地图区块! ===		=== ...我的客户端没有收到完整的地图区块! ===
	''~~Main article~~: [[How to Write a Client]]''		''主要内容: [[How to Write a Client\|如何写一个客户端]]''

	~~The standard Minecraft server sends full chunks only when your client is sending player status update packets~~ (any of [[Protocol#Player\|~~Player~~ (0x03)]] through [[Protocol#Player Position And Look\|~~Player Position And Look~~ (0x06)]]).		标准的Minecraft服务端只有在你的客户端发送玩家状态更新数据包时才会发送完整的数据块(any of [[Protocol#Player\|玩家(0x03)]] through [[Protocol#Player Position And Look\|玩家位置和朝向(0x06)]]).

	=== ...所有连接的客户端spasm and jerk uncontrollably! ===		=== ...所有连接的客户端spasm and jerk uncontrollably! ===
Line 81:		Line 81:
	The client is attempting a [[Server_List_Ping#1.6\|legacy ping]], this happens if your server did not respond to the [[Server List Ping]] properly, including if it sent malformed JSON.		The client is attempting a [[Server_List_Ping#1.6\|legacy ping]], this happens if your server did not respond to the [[Server List Ping]] properly, including if it sent malformed JSON.

	=== ...~~the client disconnects after some time with a~~ "Timed out" ~~error~~ ===		=== ...客户端在一段时间后断开连接,并出现"Timed out"错误 ===
	The server is expected to send a [[Protocol#Keep Alive (clientbound)\|Keep Alive]] packet every 1-15 seconds (if the server does not send a keep alive within 20 seconds of state change to Play, the client will disconnect from the server for '''Timed Out'''), and the client should respond with the serverbound version of that packet. If either party does not receive keep alives for some period of time, they will disconnect.		The server is expected to send a [[Protocol#Keep Alive (clientbound)\|Keep Alive]] packet every 1-15 seconds (if the server does not send a keep alive within 20 seconds of state change to Play, the client will disconnect from the server for '''Timed Out'''), and the client should respond with the serverbound version of that packet. If either party does not receive keep alives for some period of time, they will disconnect.

imported>Zhou2008 at 12:08, 3 January 2022

2022-01-03T12:08:15Z

← Older revision	Revision as of 12:08, 3 January 2022
(No difference)

imported>Zhou2008 at 12:08, 3 January 2022

2022-01-03T12:08:15Z

← Older revision		Revision as of 12:08, 3 January 2022
Line 26:		Line 26:
	# '''S''' → '''C''': [[Protocol#Declare Recipes\|合成表]]		# '''S''' → '''C''': [[Protocol#Declare Recipes\|合成表]]
	# '''S''' → '''C''': [[Protocol#Tags\|标签]]		# '''S''' → '''C''': [[Protocol#Tags\|标签]]
	# '''S''' → '''C''': [[Protocol#Entity Status\|实体状态]] (为{{Minecraft Wiki\|Server.properties#op-permission-level\|OP权限级别}};见[[Entity statuses#Player]])		# '''S''' → '''C''': [[Protocol#Entity Status\|实体状态]] (不是{{Minecraft Wiki\|Server.properties#op-permission-level\|OP权限级别}},这个才是[[Entity statuses#Player]])
	# '''S''' → '''C''': [[Protocol#Declare Commands\|命令]]		# '''S''' → '''C''': [[Protocol#Declare Commands\|命令]]
	# '''S''' → '''C''': [[Protocol#Unlock Recipes\|解锁合成表]]		# '''S''' → '''C''': [[Protocol#Unlock Recipes\|解锁合成表]]

imported>Zhou2008 at 12:05, 3 January 2022

2022-01-03T12:05:20Z

← Older revision	Revision as of 12:05, 3 January 2022
(No difference)

imported>Zhou2008 at 12:05, 3 January 2022

2022-01-03T12:05:20Z

← Older revision		Revision as of 12:05, 3 January 2022
Line 61:		Line 61:
	== 我觉得我做好了,但是... ==		== 我觉得我做好了,但是... ==
	=== ...我的玩家没有生成! ===		=== ...我的玩家没有生成! ===
	~~After sending the common-sense packets~~ ([[Protocol#Handshake\|~~Handshake~~]], [[Protocol#Login Start\|~~Login Start~~]], [[Protocol#Window Items\|~~inventory~~]], [[Protocol#Spawn Position\|~~compass~~]]~~, and~~ [[Protocol#Chunk Data\|~~chunks~~]]), ~~you need to finally send the player their~~ [[Protocol#Player Position And Look\|~~initial position~~]] ~~for them to leave the “Loading Map” screen~~.		在完成了基本操作之后([[Protocol#Handshake\|握手]]、[[Protocol#Login Start\|登录开始]]、[[Protocol#Window Items\|物品栏]]、[[Protocol#Spawn Position\|出生位置]]、[[Protocol#Chunk Data\|区块]]),你需要发送玩家的[[Protocol#Player Position And Look\|初始位置]]来让它们离开"Loading Map"界面.

	''Note that if the following steps are taken, a Minecraft client will spawn the player:''		''Note that if the following steps are taken, a Minecraft client will spawn the player:''

imported>Zhou2008 at 11:55, 3 January 2022

2022-01-03T11:55:18Z

← Older revision	Revision as of 11:55, 3 January 2022
(No difference)

imported>Zhou2008 at 11:55, 3 January 2022

2022-01-03T11:55:18Z

← Older revision		Revision as of 11:55, 3 January 2022
Line 60:		Line 60:

	== 我觉得我做好了,但是... ==		== 我觉得我做好了,但是... ==
	=== ~~…my player isn't spawning~~! ===		=== ...我的玩家没有生成! ===
	After sending the common-sense packets ([[Protocol#Handshake\|Handshake]], [[Protocol#Login Start\|Login Start]], [[Protocol#Window Items\|inventory]], [[Protocol#Spawn Position\|compass]], and [[Protocol#Chunk Data\|chunks]]), you need to finally send the player their [[Protocol#Player Position And Look\|initial position]] for them to leave the “Loading Map” screen.		After sending the common-sense packets ([[Protocol#Handshake\|Handshake]], [[Protocol#Login Start\|Login Start]], [[Protocol#Window Items\|inventory]], [[Protocol#Spawn Position\|compass]], and [[Protocol#Chunk Data\|chunks]]), you need to finally send the player their [[Protocol#Player Position And Look\|initial position]] for them to leave the “Loading Map” screen.

Line 70:		Line 70:
	While the above steps are sufficient for Minecraft 1.4.5, it is good form to send packets that inform the client about the world around the player before allowing the player to spawn.		While the above steps are sufficient for Minecraft 1.4.5, it is good form to send packets that inform the client about the world around the player before allowing the player to spawn.

	=== ~~…my client isn't receiving complete map chunks~~! ===		=== ...我的客户端没有收到完整的地图区块! ===
	''Main article: [[How to Write a Client]]''		''Main article: [[How to Write a Client]]''

	The standard Minecraft server sends full chunks only when your client is sending player status update packets (any of [[Protocol#Player\|Player (0x03)]] through [[Protocol#Player Position And Look\|Player Position And Look (0x06)]]).		The standard Minecraft server sends full chunks only when your client is sending player status update packets (any of [[Protocol#Player\|Player (0x03)]] through [[Protocol#Player Position And Look\|Player Position And Look (0x06)]]).

	=== ~~…all connecting clients spasm~~ and jerk uncontrollably! ===		=== ...所有连接的客户端spasm and jerk uncontrollably! ===
	For newer clients, your server needs to send 49 chunks ahead of time, not just one. Send a 7×7 square of chunks, centered on the connecting client's position, ''before'' spawning them.		For newer clients, your server needs to send 49 chunks ahead of time, not just one. Send a 7×7 square of chunks, centered on the connecting client's position, ''before'' spawning them.

	=== ~~…the client is trying to send an invalid packet that begins with 0xFE01~~ ===		=== ...客户端正试图发送一个以0xFE01开头的无效数据包. ===
	The client is attempting a [[Server_List_Ping#1.6\|legacy ping]], this happens if your server did not respond to the [[Server List Ping]] properly, including if it sent malformed JSON.		The client is attempting a [[Server_List_Ping#1.6\|legacy ping]], this happens if your server did not respond to the [[Server List Ping]] properly, including if it sent malformed JSON.

	=== ~~…the~~ client disconnects after some time with a "Timed out" error ===		=== ...the client disconnects after some time with a "Timed out" error ===
	The server is expected to send a [[Protocol#Keep Alive (clientbound)\|Keep Alive]] packet every 1-15 seconds (if the server does not send a keep alive within 20 seconds of state change to Play, the client will disconnect from the server for '''Timed Out'''), and the client should respond with the serverbound version of that packet. If either party does not receive keep alives for some period of time, they will disconnect.		The server is expected to send a [[Protocol#Keep Alive (clientbound)\|Keep Alive]] packet every 1-15 seconds (if the server does not send a keep alive within 20 seconds of state change to Play, the client will disconnect from the server for '''Timed Out'''), and the client should respond with the serverbound version of that packet. If either party does not receive keep alives for some period of time, they will disconnect.

	=== ...~~my client isn't sending a Login Start packet~~! ===		=== ...我的客户端没有发送登录开始数据包! ===
	The Notchian client may group packets if the size of the packet and delay between the last packet are too small. To solve this issue, you must use the Packet Length to infer there is another packet by comparing it and the data length.		The Notchian client may group packets if the size of the packet and delay between the last packet are too small. To solve this issue, you must use the Packet Length to infer there is another packet by comparing it and the data length.

← Older revision		Revision as of 12:15, 3 January 2022
Line 35:		Line 35:
	# '''S''' → '''C''': [[Protocol#Update Light\|更新光照]] (在以玩家位置为中心的正方形中,每个区块都发送一次.)		# '''S''' → '''C''': [[Protocol#Update Light\|更新光照]] (在以玩家位置为中心的正方形中,每个区块都发送一次.)
	# '''S''' → '''C''': [[Protocol#Chunk Data\|区块数据]] (在以玩家位置为中心的正方形中,每个区块都发送一次.)		# '''S''' → '''C''': [[Protocol#Chunk Data\|区块数据]] (在以玩家位置为中心的正方形中,每个区块都发送一次.)
	# '''S''' → '''C''': [[Protocol#World Border\|世界边界]] (~~Once the world is finished loading~~)		# '''S''' → '''C''': [[Protocol#World Border\|世界边界]] (一旦世界完成了加载)
	# '''S''' → '''C''': [[Protocol#Spawn Position\|出生位置]] ("家"出生点,不是客户端登录时的位置)		# '''S''' → '''C''': [[Protocol#Spawn Position\|出生位置]] ("家"出生点,不是客户端登录时的位置)
	# '''S''' → '''C''': [[Protocol#Player Position And Look (clientbound)\|玩家位置和朝向]] (必须,告诉客户端已经准备好生成了)		# '''S''' → '''C''': [[Protocol#Player Position And Look (clientbound)\|玩家位置和朝向]] (必须,告诉客户端已经准备好生成了)
Line 47:		Line 47:

	# '''C''' → '''S''': [[Protocol#Handshake\|握手]] State=1		# '''C''' → '''S''': [[Protocol#Handshake\|握手]] State=1
	# ~~服务器将协议State设置为1~~		# 服务端将协议State设置为1
	# '''C''' → '''S''': [[Protocol#Request\|请求]]		# '''C''' → '''S''': [[Protocol#Request\|请求]]
	# '''S''' → '''C''': [[Protocol#Response\|响应]]		# '''S''' → '''C''': [[Protocol#Response\|响应]]
Line 63:		Line 63:
	在完成了基本操作之后([[Protocol#Handshake\|握手]]、[[Protocol#Login Start\|登录开始]]、[[Protocol#Window Items\|物品栏]]、[[Protocol#Spawn Position\|出生位置]]、[[Protocol#Chunk Data\|区块]]),你需要发送玩家的[[Protocol#Player Position And Look\|初始位置]]来让它们离开"Loading Map"界面.		在完成了基本操作之后([[Protocol#Handshake\|握手]]、[[Protocol#Login Start\|登录开始]]、[[Protocol#Window Items\|物品栏]]、[[Protocol#Spawn Position\|出生位置]]、[[Protocol#Chunk Data\|区块]]),你需要发送玩家的[[Protocol#Player Position And Look\|初始位置]]来让它们离开"Loading Map"界面.

	''~~Note that if the following steps are taken~~, ~~a Minecraft client will spawn the player~~:''		''请注意,如果采取以下步骤,Minecraft客户端将生成玩家:''
	# ~~Do Handshake~~ (~~see~~ [[Protocol Encryption]])		# 握手([[Protocol Encryption\|协议加密]])
	# ~~Send~~ [[Protocol#Spawn Position\|~~Spawn Position~~]] ~~packet~~		# 发送[[Protocol#Spawn Position\|出生位置]]数据包
	# ~~Send~~ [[Protocol#Player Position And Look (clientbound)\|~~Player Position And Look (clientbound)~~]] ~~packet~~		# 发送[[Protocol#Player Position And Look (clientbound)\|玩家位置和朝向]]数据包

	~~While the above steps are sufficient for Minecraft~~ 1.4.5, it is good form to send packets that inform the client about the world around the player before allowing the player to spawn.		虽然上述步骤对Minecraft 1.4.5来说已经足够了, it is good form to send packets that inform the client about the world around the player before allowing the player to spawn.

	=== ...我的客户端没有收到完整的地图区块! ===		=== ...我的客户端没有收到完整的地图区块! ===
	''~~Main article~~: [[How to Write a Client]]''		''主要内容: [[How to Write a Client\|如何写一个客户端]]''

	~~The standard Minecraft server sends full chunks only when your client is sending player status update packets~~ (any of [[Protocol#Player\|~~Player~~ (0x03)]] through [[Protocol#Player Position And Look\|~~Player Position And Look~~ (0x06)]]).		标准的Minecraft服务端只有在你的客户端发送玩家状态更新数据包时才会发送完整的数据块(any of [[Protocol#Player\|玩家(0x03)]] through [[Protocol#Player Position And Look\|玩家位置和朝向(0x06)]]).

	=== ...所有连接的客户端spasm and jerk uncontrollably! ===		=== ...所有连接的客户端spasm and jerk uncontrollably! ===
Line 81:		Line 81:
	The client is attempting a [[Server_List_Ping#1.6\|legacy ping]], this happens if your server did not respond to the [[Server List Ping]] properly, including if it sent malformed JSON.		The client is attempting a [[Server_List_Ping#1.6\|legacy ping]], this happens if your server did not respond to the [[Server List Ping]] properly, including if it sent malformed JSON.

	=== ...~~the client disconnects after some time with a~~ "Timed out" ~~error~~ ===		=== ...客户端在一段时间后断开连接,并出现"Timed out"错误 ===
	The server is expected to send a [[Protocol#Keep Alive (clientbound)\|Keep Alive]] packet every 1-15 seconds (if the server does not send a keep alive within 20 seconds of state change to Play, the client will disconnect from the server for '''Timed Out'''), and the client should respond with the serverbound version of that packet. If either party does not receive keep alives for some period of time, they will disconnect.		The server is expected to send a [[Protocol#Keep Alive (clientbound)\|Keep Alive]] packet every 1-15 seconds (if the server does not send a keep alive within 20 seconds of state change to Play, the client will disconnect from the server for '''Timed Out'''), and the client should respond with the serverbound version of that packet. If either party does not receive keep alives for some period of time, they will disconnect.

← Older revision		Revision as of 12:08, 3 January 2022
Line 26:		Line 26:
	# '''S''' → '''C''': [[Protocol#Declare Recipes\|合成表]]		# '''S''' → '''C''': [[Protocol#Declare Recipes\|合成表]]
	# '''S''' → '''C''': [[Protocol#Tags\|标签]]		# '''S''' → '''C''': [[Protocol#Tags\|标签]]
	# '''S''' → '''C''': [[Protocol#Entity Status\|实体状态]] (为{{Minecraft Wiki\|Server.properties#op-permission-level\|OP权限级别}};见[[Entity statuses#Player]])		# '''S''' → '''C''': [[Protocol#Entity Status\|实体状态]] (不是{{Minecraft Wiki\|Server.properties#op-permission-level\|OP权限级别}},这个才是[[Entity statuses#Player]])
	# '''S''' → '''C''': [[Protocol#Declare Commands\|命令]]		# '''S''' → '''C''': [[Protocol#Declare Commands\|命令]]
	# '''S''' → '''C''': [[Protocol#Unlock Recipes\|解锁合成表]]		# '''S''' → '''C''': [[Protocol#Unlock Recipes\|解锁合成表]]