CurseForge · Minecraft mod

SerializerDebug

Automatically fix the error "Unknown Serializer Type xxx"

Choose a version Pick your version below, then grab the matching file.

Quick answer

Which SerializerDebug release should I use?

Updated 1 year ago

Latest stable file serializer_debug-1.0.1.jar

Game version 1.20.1

Loader Forge

SerializerDebug serializer_debug-1.0.1.jar targets 1.20.1 with Forge. The project page does not say whether this file belongs on the client, dedicated server, or both. No extra mods listed for this file.

Where it goes

Is SerializerDebug required on the client, server, or both?

The project page does not say whether this file belongs on the client, dedicated server, or both.

Client Source doesn’t say

Dedicated server Source doesn’t say

Loader for this release Forge

Required install it here Optional supported, not mandatory Not supported do not install here Source doesn’t say do not assume

The source does not explicitly classify this release as client-only or server-only.

Understand client and server requirements Read the Minecraft installation guide

What else does SerializerDebug serializer_debug-1.0.1.jar need?

serializer_debug-1.0.1.jar. Change the file and its required mods may change too.

No extra mods listed for this file

This file does not list any required mods. Do not add a library just because a different file uses it.

This file does not list any required or optional mods.

Before you install it

Add SerializerDebug without breaking your instance.

Built for SerializerDebug serializer_debug-1.0.1.jar. Pick another file and the loader, install side or required mods may change.

01
Stick to this file

Use serializer_debug-1.0.1.jar. It targets 1.20.1 with Forge; another release may have different loader, side or dependency requirements.
02
Bring the mods it needs

This file does not list any required mods. Do not add a library just because a different file uses it.
03
Put it on the correct side

The project page does not say whether this file belongs on the client, dedicated server, or both.
04
Pick the file you checked

Use the “Get this file” button beside serializer_debug-1.0.1.jar. It opens that exact file at the source.

About this project

What does SerializerDebug add?

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

Project description from CurseForge.

Pick your setup