Zh:Protocol FAQ - Revision history

imported>Kaniol at 08:53, 18 November 2019

2019-11-18T08:53:03Z

← Older revision		Revision as of 08:53, 18 November 2019
Line 1:		Line 1:
	人们总是会有一些关于Minecraft Modern [[ZH:Protocol\|协议]]的问题，所以我们将在本文档中讲述其中一些最常见的。如果你仍有麻烦，在IRC上加入我们，[irc://irc.freenode.net/mcdevs irc.freenode.net上的频道#mcdevs].		人们总是会有一些关于Minecraft Modern [[ZH:Protocol\|协议]]的问题，所以我们将在本文档中讲述其中一些最常见的。如果你仍有麻烦，在IRC上加入我们，[irc://irc.freenode.net/mcdevs irc.freenode.net上的频道#mcdevs]。

	== 协议文档完备了吗？ ==		== 协议文档完备了吗？ ==
Line 7:		Line 7:
	== 客户端的正常登入顺序是什么样的？ ==		== 客户端的正常登入顺序是什么样的？ ==

	有关与Mojang服务器的交流，见[[ZH:Authentication\|认证]]		有关与Mojang服务器的交流，见[[ZH:Authentication\|认证]]。

	推荐的登入流程看起来像这样，其中'''C'''是客户端而'''S'''是服务端：		推荐的登入流程看起来像这样，其中'''C'''是客户端而'''S'''是服务端：

	# 客户端连接至服务端		# 客户端连接至服务端
	# '''C'''→'''S''': [[ZH:Protocol#~~Handshake~~\|~~Handshake~~]] ~~State~~=2		# '''C'''→'''S''': [[ZH:Protocol#握手\|握手]]状态=2
	# '''C'''→'''S''': [[ZH:Protocol#开始登入\|开始登入]]		# '''C'''→'''S''': [[ZH:Protocol#开始登入\|开始登入]]
	# '''S'''→'''C''': [[ZH:Protocol#加密请求\|加密请求]]		# '''S'''→'''C''': [[ZH:Protocol#加密请求\|加密请求]]
Line 49:		Line 49:
	如果服务端为离线模式，它不会发送[[ZH:Protocol#加密请求\|加密请求]]数据包，相似地，客户端也不应发送[[ZH:Protocol#加密响应\|加密响应]]。在这种情况下，从不会启用加密，也不会出现任何认证。		如果服务端为离线模式，它不会发送[[ZH:Protocol#加密请求\|加密请求]]数据包，相似地，客户端也不应发送[[ZH:Protocol#加密响应\|加密响应]]。在这种情况下，从不会启用加密，也不会出现任何认证。

	如果服务端发送了一个不含[[ZH:Protocol#加密请求\|加密请求]]的[[ZH:Protocol#登入成功\|登入成功]]~~，那么客户端就会知道服务器为离线模式~~		如果服务端发送了一个不含[[ZH:Protocol#加密请求\|加密请求]]的[[ZH:Protocol#登入成功\|登入成功]]，那么客户端就会知道服务器为离线模式。

	== 我觉得我啥都没做错，但是… ==		== 我觉得我啥都没做错，但是… ==
Line 55:		Line 55:
	=== …我的玩家没有生成！ ===		=== …我的玩家没有生成！ ===

	发送一些常规的数据包之后（[[ZH:Protocol#~~Handshake~~\|~~Handshake~~]]、[[ZH:Protocol#开始登入\|开始登入]]、[[ZH:Protocol#窗口物品\|物品栏]]、[[ZH:Protocol#生成位置\|指南针]]和[[ZH:Protocol\|区块数据\|区块]]），你最后会需要将玩家的[[ZH:Protocol#玩家位置和外观\|初始位置]]发送给他们，这样他们就会离开“加载地图中”的屏幕。		发送一些常规的数据包之后（[[ZH:Protocol#握手\|握手]]、[[ZH:Protocol#开始登入\|开始登入]]、[[ZH:Protocol#窗口物品\|物品栏]]、[[ZH:Protocol#生成位置\|指南针]]和[[ZH:Protocol\|区块数据\|区块]]），你最后会需要将玩家的[[ZH:Protocol#玩家位置和外观\|初始位置]]发送给他们，这样他们就会离开“加载地图中”的屏幕。

	''注意如果使用了以下步骤，那么一个Minecraft客户端会生成玩家：''		''注意如果使用了以下步骤，那么一个Minecraft客户端会生成玩家：''

	# 执行握手（见[[ZH:Protocol Encryption]])		# 执行握手（见[[ZH:Protocol Encryption\|协议加密]])
	# 发送[[ZH:Protocol#生成位置\|生成位置]]数据包		# 发送[[ZH:Protocol#生成位置\|生成位置]]数据包
	# 发送[[ZH:Protocol#玩家位置和外观\|玩家位置和外观]]数据包		# 发送[[ZH:Protocol#玩家位置和外观\|玩家位置和外观]]数据包

	上述步骤对于Minecraft 1.4.~~5来说已经足够了，发送数据包是一种很好的形式，因为这会在允许玩家生成之前告知客户端玩家周围的世界~~		上述步骤对于Minecraft 1.4.5来说已经足够了，发送数据包是一种很好的形式，因为这会在允许玩家生成之前告知客户端玩家周围的世界。

	=== …我的数据包没有接受到完整的地图区块！ ===		=== …我的数据包没有接受到完整的地图区块！ ===

imported>Kaniol at 15:10, 17 November 2019

2019-11-17T15:10:52Z

Show changes

imported>Kaniol: Kaniol moved page ZH:协议FAQ to ZH:Protocol FAQ

2019-09-30T23:36:45Z

Kaniol moved page ZH:协议FAQ to ZH:Protocol FAQ

← Older revision	Revision as of 23:36, 30 September 2019
(No difference)

imported>Hempflower: Created page with "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 havi..."

2019-09-29T16:38:06Z

Created page with "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 havi..."

New page

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 [irc://irc.freenode.net/mcdevs #mcdevs on irc.freenode.net].

== Is the protocol documentation complete? ==

Depending on your definition, ''yes''! All packet types are known and their layout documented. Some finer details are missing, but everything you need to make functional programs is present. We also collect information on the [[pre-release protocol]] changes, allowing us to quickly document new releases.

== What's the normal login sequence for a client? ==

See [[Authentication]] for communication with Mojang's servers.

The recommended login sequence looks like this, where '''C''' is the client and '''S''' is the server:

# Client connects to server
# '''C→S''': [[Protocol#Handshake|Handshake]] State=2
# '''C→S''': [[Protocol#Login Start|Login Start]]
# '''S→C''': [[Protocol#Encryption Request|Encryption Request]]
# Client auth
# '''C→S''': [[Protocol#Encryption Response|Encryption Response]]
# Server auth, both enable encryption
# '''S→C''': [[Protocol#Set Compression|Set Compression]] (Optional, enables compression)
# '''S→C''': [[Protocol#Login Success|Login Success]]
# '''S→C''': [[Protocol#Join Game|Join Game]]
# '''S→C''': [[Protocol#Plugin Message (clientbound) |Plugin Message]]: [[Plugin channel#minecraft%3Abrand|<code>minecraft:brand</code>]] with the server's brand (Optional)
# '''S→C''': [[Protocol#Server Difficulty|Server Difficulty]] (Optional)
# '''S→C''': [[Protocol#Player Abilities (clientbound)|Player Abilities]] (Optional)
# '''C→S''': [[Protocol#Plugin Message (serverbound)|Plugin Message]]: [[Plugin channel#minecraft%3Abrand|<code>minecraft:brand</code>]] with the client's brand (Optional)
# '''C→S''': [[Protocol#Client Settings|Client Settings]]
# '''S→C''': [[Protocol#Held Item Change (clientbound)|Held Item Change]]
# '''S→C''': [[Protocol#Declare Recipes|Declare Recipes]]
# '''S→C''': [[Protocol#Tags|Tags]]
# '''S→C''': [[Protocol#Entity Status|Entity Status]]
# '''S→C''': [[Protocol#Declare Commands|Declare Commands]]
# '''S→C''': [[Protocol#Unlock Recipes|Unlock Recipes]]
# '''S→C''': [[Protocol#Player Position And Look (clientbound)|Player Position And Look]]
# '''S→C''': [[Protocol#Player Info|Player Info]] (Add Player action)
# '''S→C''': [[Protocol#Player Info|Player Info]] (Update latency action)
# '''S→C''': [[Protocol#Update View Position|Update View Position]]
# '''S→C''': [[Protocol#Update Light|Update Light]] (One sent for each chunk in a square centered on the player's position)
# '''S→C''': [[Protocol#Chunk Data|Chunk Data]] (One sent for each chunk in a square centered on the player's position)
# '''S→C''': [[Protocol#World Border|World Border]] (Once the world is finished loading)
# '''S→C''': [[Protocol#Spawn Position|Spawn Position]] (“home” spawn, not where the client will spawn on login)
# '''S→C''': [[Protocol#Player Position And Look (clientbound)|Player Position And Look]] (Required, tells the client they're ready to spawn)
# '''C→S''': [[Protocol#Teleport Confirm|Teleport Confirm]]
# '''C→S''': [[Protocol#Player Position And Look (serverbound)|Player Position And Look]] (to confirm the spawn position)
# '''C→S''': [[Protocol#Client Status|Client Status]] (sent either before or while receiving chunks, further testing needed, server handles correctly if not sent)
# '''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|Logic Success]] without sending [[Protocol#Encryption Request|Encryption Request]].

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

=== …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.

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

# Do Handshake (see [[Protocol Encryption]])
# Send [[Protocol#Spawn Position|Spawn Position]] packet
# Send [[Protocol#Player Position And Look|Player Position And Look]] packet

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]]''

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! ===

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 ===

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 server is expected to send a [[Protocol#Keep Alive (clientbound)|Keep Alive]] packet every second, 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.

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

== 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.

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.
# '''S'''→'''C''': [[Protocol#Update Block Entity|Update Block Entity (0x09)]], with the NBT of the command block.

And to save it, use the [[Plugin channels#MC.7CAutoCmd|<code>MC|AutoCmd</code> plugin channel]].