该模组将尝试自动修复“未知序列化器类型 110”或其他类似错误。此模组必须安装在客户端和服务端上。
这些错误的根本原因是服务端和客户端都与特定的“序列化器”关联了 ID 编号,如果客户端或服务端的这些编号不匹配,就会出现“未知序列化器类型”的错误。
安装该模组后,您应该能够成功连接到服务器。
此模组最初是为了修复 Cobblemon 的 bug 而开发的,但它应该能适用于任何存在序列化器不同步问题的模组。
默认情况下,该模组会在客户端和服务端记录序列化器 ID/对象对,如果出现不同步,您很可能可以根据日志确定问题所在。
它还会尝试在客户端侧自动纠正此错误。
该模组包含一个具有以下选项的配置:
“忽略序列化器错误”:
默认为 FALSE - 如果切换为 true,此选项将强制忽略序列化器错误,因此您将无法再收到“未知序列化器类型”错误。除非万不得已,否则不建议开启此选项。
“仅显示错误”:
默认为 TRUE - 如果切换为 false,它将详细打印发生的任何实体 ID 序列化操作。如果设置为 true,则仅在检测到错误时打印。
“重新排序客户端 ID”:
默认为 TRUE - 这是尝试在客户端侧自动修复不同步的设置。服务器将在登录时向其发送其序列化器列表,客户端将重新排序其内部序列化器列表以与服务端匹配。如果数据包到达,客户端侧日志中将显示日志语句:“Handle ClientboundSerializerSyncPacket”。如果此数据包与客户端侧存在不匹配,它将重新排序客户端侧的序列化器。这将被记录为“Init remap:” - 如果在日志中看到此语句,则表明存在不同步,且客户端已自动校正以与服务端匹配。
以下是修复经常遇到此错误的 Cobblemon 的实际日志输出示例:
[27Dec2024 14:26:17.924] [Netty Client IO #10/ERROR] [net.minecraft.network.syncher.EntityDataSerializers/]: [SerializerDebug] Init remapping process using server data, size=51
[27Dec2024 14:26:17.925] [Netty Client IO #10/ERROR] [net.minecraft.network.syncher.EntityDataSerializers/]: [SerializerDebug] Init remap: from clientId=29 to serverId=28 for server className=com.cobblemon.mod.common.api.net.serializers.Vec3DataSerializer
[27Dec2024 14:26:17.925] [Netty Client IO #10/ERROR] [net.minecraft.network.syncher.EntityDataSerializers/]: [SerializerDebug] Init remap: from clientId=30 to serverId=29 for server className=com.cobblemon.mod.common.api.net.serializers.StringSetDataSerializer
[27Dec2024 14:26:17.926] [Netty Client IO #10/ERROR] [net.minecraft.network.syncher.EntityDataSerializers/]: [SerializerDebug] Init remap: from clientId=31 to serverId=30 for server className=com.cobblemon.mod.common.api.net.serializers.PoseTypeDataSerializer
[27Dec2024 14:26:17.926] [Netty Client IO #10/ERROR] [net.minecraft.network.syncher.EntityDataSerializers/]: [SerializerDebug] Init remap: from clientId=32 to serverId=31 for server className=com.cobblemon.mod.common.api.net.serializers.IdentifierDataSerializer
[27Dec2024 14:26:17.926] [Netty Client IO #10/ERROR] [net.minecraft.network.syncher.EntityDataSerializers/]: [SerializerDebug] Init remap: from clientId=28 to serverId=32 for server className=com.bobmowzie.mowziesmobs.server.ServerProxy$1
The mod will attempt to automatically fix the error "Unknown serializer type 110" or other similar errors. The mod must be installed on client + server.
The root cause of these errors is that the server and client have ID numbers associated with specific "serializers" and if there is a mismatch of these numbers on the client/server, it will give an error "unknown serializer type".
After installing the mod, you should be able to successfully connect to the server.
This was developed primarily to fix a Cobblemon bug, but it should work for any mods that have a serializer de-sync issue.
The mod will by default log the serializer ID/object pair on the client and server, and if there is any de-sync, you will most likely be able to identify what the problem is based on the logs.
It will also attempt to auto-correct this error on the client side.
The mod has a config with the following options:
"Ignore serializer error":
Defaulted to FALSE - if toggled to true this option will forcefully ignore serializer errors, and as such it would be impossible to get the "unknown serializer type" error. It is not recommended to turn this on unless all else fails.
"Only Show Errors":
Defaulted to TRUE - If toggled to false it will do verbose printing of any entity ID serialization that happens. If set to true, it will only print when there is an error detected.
"Reorder client IDs":
Defaulted to TRUE - This is the setting that tries to automatically fix the de-sync on the client side. The server will send its serializer list to the client upon login, and the client will reorder its own internal serializer list to match that of the server. If the packet arrives, the client-side logs will show the log statement: "Handle ClientboundSerializerSyncPacket". If this packet has a mismatch with the client-side, it will reorder the client-side serializers. This will be logged as "Init remap:" - if you see this statement in the logs then you know that there was a de-sync and the client has been auto-corrected to match the server.
Below is an example of actual log output to fix Cobblemon, which frequently gets this error:
[27Dec2024 14:26:17.924] [Netty Client IO #10/ERROR] [net.minecraft.network.syncher.EntityDataSerializers/]: [SerializerDebug] Init remapping process using server data, size=51
[27Dec2024 14:26:17.925] [Netty Client IO #10/ERROR] [net.minecraft.network.syncher.EntityDataSerializers/]: [SerializerDebug] Init remap: from clientId=29 to serverId=28 for server className=com.cobblemon.mod.common.api.net.serializers.Vec3DataSerializer
[27Dec2024 14:26:17.925] [Netty Client IO #10/ERROR] [net.minecraft.network.syncher.EntityDataSerializers/]: [SerializerDebug] Init remap: from clientId=30 to serverId=29 for server className=com.cobblemon.mod.common.api.net.serializers.StringSetDataSerializer
[27Dec2024 14:26:17.926] [Netty Client IO #10/ERROR] [net.minecraft.network.syncher.EntityDataSerializers/]: [SerializerDebug] Init remap: from clientId=31 to serverId=30 for server className=com.cobblemon.mod.common.api.net.serializers.PoseTypeDataSerializer
[27Dec2024 14:26:17.926] [Netty Client IO #10/ERROR] [net.minecraft.network.syncher.EntityDataSerializers/]: [SerializerDebug] Init remap: from clientId=32 to serverId=31 for server className=com.cobblemon.mod.common.api.net.serializers.IdentifierDataSerializer
[27Dec2024 14:26:17.926] [Netty Client IO #10/ERROR] [net.minecraft.network.syncher.EntityDataSerializers/]: [SerializerDebug] Init remap: from clientId=28 to serverId=32 for server className=com.bobmowzie.mowziesmobs.server.ServerProxy$1
评论 0
登录后参与评分
还没有评论,来抢沙发吧