SerializerDebug

Quick rating

SerializerDebug

No reviews yet

Automatically fix the error "Unknown Serializer Type xxx"

QoL & Tweaks
Mod Loaders
Forge
Minecraft

Community voices

Reviews

Versions
Loading versions…
Match includes

Click once to include, again to exclude, again to clear

Rating Any
Any 0.5 1.0 1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0
Min
Max
Play Status
Reviews
Time Played
hrs+
Verified developers only
Has developer response
List view
Grid view
Compact view
Sort by
Date
Rating
Helpful
Unhelpful
Edited
Sort ascending
Delete this review?

This removes your review from the project. You can write a new review after.

Review submitted for moderation

Your review has been sent to moderators, who will check that it meets our guidelines before it appears publicly.

No reviews yet. Be the first to review this project!

Get it on

Available Platforms

About

Project Details

Type
Mod
Latest Version
serializer_debug-1.0.1.jar
Authors

For authors

Embed Badge

If you're the author of this project, you can embed a live badge anywhere that supports HTML or Markdown. It updates automatically whenever ratings change.

Custom banner text
ModDex rating badge preview

Use HTML for any page that supports it, or Markdown for README files and Markdown-based descriptions.

Identifiers

Platform IDs

CurseForge ID

Resources

External Links

Source Issues Wiki Discord

About

Description

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

Screenshots

Gallery

  • The Error
    The Error
  • Serializers remapping
    Serializers remapping If you see this error text, "Init remap", it means your local serializers were NOT in sync with the server and your login would have failed. The mod should automatically sync with the server.

Versions

Files

Relations

Project Relations

More like this

Similar Mods

Suggestions use data such as tags, dependencies, dependents, descriptions, titles, and more to rank how much they overlap with this mod.

On ModDex

Community snapshot

0
Ratings
0
Followers
0
In stacks

By the numbers

Statistics

~490,000
Downloads
Last Updated
Created
Last synced
When ModDex last fetched this project from CurseForge or Modrinth. Every project is re-checked on a schedule, and any project that ships a new file is synced automatically within hours of the release.
New file updates sync automatically
How syncing works