[1.14.4] Channels [uteamcore:network] rejected their server side version number during listping
fuzzyweapon opened this issue ยท 4 comments
Describe the bug
When disconnecting from a multiplayer forge server with u team core and useful backpacks, client gets the following error in latest.log:
[Netty Client IO #6/ERROR] [net.minecraftforge.fml.network.NetworkRegistry/NETREGISTRY]: Channels [uteamcore:network] rejected their server side version number during listping
Note that this doesn't seem to cause the player any negative impact that I can see.
To Reproduce
Steps to reproduce the behavior:
- Install 28.1.26 Forge client to vanilla launcher 1.14.4 instance.
- Install 28.1.26 Forge server to vanilla MP 1.14.4 server instance.
- Install u_team_core-1.14.4-2.7.4.134.jar to both client and server instances.
- Install useful_backpacks-1.14.4-1.7.1.41.jar to both client and server instances.
- Launch server (not LAN, but is hosted on localhost for this test).
- Launch client.
- Connect to server with client.
- Disconnect from server on client via
escmenu. - Observe client's
logs/latest.log
Expected behavior
No errors.
Versions
- Minecraft version: 1.14.4
- Forge version: 28.1.26
- UTeamCore version: 2.7.4.134
Found out this was because I had an entry in my multiplayer menu for the live server (which had a previous u-team-core loaded). I think this invalidates the bug and is by design, but I'll leave this up for you guys to judge.
As a side note, it seems a little weird to have a client reporting that they reject a server (vs a server rejecting a client, since typically, server should be authority).
Hello,
This issue was kind of my fault as I have forgotten to update the network version number.
This was introduced in this commit 57975fe which changed the value.
Nevertheless the client version and the server version should always match. Else there might be weird issues.
As a side note, it seems a little weird to have a client reporting that they reject a server (vs a server rejecting a client, since typically, server should be authority).
Definitely agree that this system is kind of weird. Currently we use the SimpleChannel of Minecraft Forge for our networking so we cannot change the behaviour there.
As this is working intended, I'll close for now.
Please reopen if any other issues occur.
~Johannes
