Difference between revisions of "Protocol FAQ:zh-cn"
| 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|世界边界]] ( | + | # '''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 |
# '''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"界面. | ||
| − | '' | + | ''请注意,如果采取以下步骤,Minecraft客户端将生成玩家:'' |
| − | # | + | # 握手([[Protocol Encryption|协议加密]]) |
| − | # | + | # 发送[[Protocol#Spawn Position|出生位置]]数据包 |
| − | # | + | # 发送[[Protocol#Player Position And Look (clientbound)|玩家位置和朝向]]数据包 |
| − | + | 虽然上述步骤对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. | |
=== ...我的客户端没有收到完整的地图区块! === | === ...我的客户端没有收到完整的地图区块! === | ||
| − | '' | + | ''主要内容: [[How to Write a Client|如何写一个客户端]]'' |
| − | + | 标准的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. | ||
| − | === ... | + | === ...客户端在一段时间后断开连接,并出现"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. | ||
Revision as of 12:15, 3 January 2022
有人一直问我们关于Minecraft: Java Edition的协议的问题,所以我们将尝试在本文档中解决一些最常见的问题.如果你仍然有问题,请加入我们的IRC频道,irc.libera.chat上的#mcdevs.
Contents
协议文档是否完整?
根据你的定义,完整!所有的数据包类型都是已知的,它们的布局也有记录.虽说缺少一些细枝末节,但制作功能性程序所需的一切都有了.我们还收集了Pre-release协议变化的信息,使我们能够快速记录新的版本.
客户端正常的登录顺序是什么?
关于与Mojang服务器的通信,请参阅认证.
建议的登录顺序如下,C代表客户端S代表服务端:
- 客户端连接到服务端
- C→S: 握手 State=2
- C→S: 开始登录
- S→C: 加密请求
- 客户端验证
- C→S: 加密响应
- 服务端验证(此时CS的连接均为加密)
- S → C: 设置压缩 (可选,启用压缩)
- S → C: 登录完成
- S → C: 加入游戏
- S → C: 插件信息:
minecraft:brand包含服务器的类型(可选) - S → C: 服务器难度 (可选)
- S → C: 玩家的能力 (可选)
- C → S: 插件信息:
minecraft:brand包含客户端的类型(可选) - C → S: 客户端设置
- S → C: 手持物品的变化
- S → C: 合成表
- S → C: 标签
- S → C: 实体状态 (不是OP权限级别,这个才是Entity statuses#Player)
- S → C: 命令
- S → C: 解锁合成表
- S → C: 玩家位置和朝向
- S → C: 玩家信息 (添加玩家的动作)
- S → C: 玩家信息 (更新延时动作)
- S → C: 更新视线位置
- S → C: 更新光照 (在以玩家位置为中心的正方形中,每个区块都发送一次.)
- S → C: 区块数据 (在以玩家位置为中心的正方形中,每个区块都发送一次.)
- S → C: 世界边界 (一旦世界完成了加载)
- S → C: 出生位置 ("家"出生点,不是客户端登录时的位置)
- S → C: 玩家位置和朝向 (必须,告诉客户端已经准备好生成了)
- C → S: 传送确认
- C → S: 玩家位置和朝向 (确认生成位置)
- C → S: 客户端状态 (在接收区块前或接收区块时发送,需要进一步测试,如果没有发送,服务端会正确处理.)
- S → C: 物品栏、实体...
正常状态的ping顺序是什么样子的?
当Notchian客户端和服务端在ping状态中交换信息时,数据包的交换情况如下:
离线模式
如果服务端处于离线模式,则不会发送加密请求数据包并且客户端也不会发送加密响应数据包.在这种情况下,加密永远也不会被启用,也不进行认证.
客户端可以判断出服务端是否处于离线模式,如果服务端直接发送了登录完成数据包而不发送加密请求数据包,则是离线模式,反之.
我觉得我做好了,但是...
...我的玩家没有生成!
在完成了基本操作之后(握手、登录开始、物品栏、出生位置、区块),你需要发送玩家的初始位置来让它们离开"Loading Map"界面.
请注意,如果采取以下步骤,Minecraft客户端将生成玩家:
虽然上述步骤对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服务端只有在你的客户端发送玩家状态更新数据包时才会发送完整的数据块(any of 玩家(0x03) through 玩家位置和朝向(0x06)).
...所有连接的客户端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.
...客户端正试图发送一个以0xFE01开头的无效数据包.
The client is attempting a legacy ping, this happens if your server did not respond to the Server List Ping properly, including if it sent malformed JSON.
...客户端在一段时间后断开连接,并出现"Timed out"错误
The server is expected to send a 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 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 following information needs to be added to this page: |
| Pseudo code example on how to parse a grouped packet? |
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 Update Block Entity (0x09) packet to open it.
First, the client must have at least an OP permission level of 2, or else the client will refuse to open the command block. (The op permission level is set with the Entity Status packet)
To actually open the command block:
- C→S: Player Block Placement (0x1C), with the position being the command block that was right-clicked.
- S→C: Update Block Entity (0x09), with the NBT of the command block.
And to save it, use the MC|AutoCmd plugin channel.
