BdLib

BdLib

Mods
97M Downloads

Server Client Version Mismatch

BeccaAsHeck opened this issue ยท 8 comments

commented

Hey so I'm running this inside a pack with someone on a server, and I keep receiving a version mismatch error. I double checked the file versions several times, switched between 1.15.0.4 and 1.15.0.3, redownloaded the file several times to be absolutely sure. Is this simply related to early stages of porting over to 1.16.5? It seems to work for my bf but not for me.

The error in the log file is always the same one:
[25May2021 22:36:10.375] [Netty Client IO #1/ERROR] [net.minecraftforge.fml.network.NetworkRegistry/NETREGISTRY]: Channels [bdlib:multiblock] rejected their server side version number

I appreciate your work though

Regards
Becca

commented

I can't reproduce this.

Make sure the mod is installed on both the client and the server, and that the version is the same.

If it still doesn't work post your debug.log from both server and client.

commented

@CanBoy67 from your log:

Channel 'bdlib:multiblock' : Version test of 'ABSENT ?' from server : REJECTED

which means the mod is either not loaded on the server or something is broken on the other side (that's why i asked for both logs)

commented

I had the exact same issue with this mod and only fixed it by flat out removing this mod and advanced generators from pack and server
Client debug.log

commented

Client debug log
Server debug log

These are both logs

image
I just replaced bdlib both on client and server with the same downloaded file

Edit: Forgot to mention the error is persisting through the latest update

commented

I think i see what the problem is, something is causing Advanced Generators to touch the code for a channel in BdLib before it was properly initialized and it gets the wrong mod id...

Still can't reproduce it on my test server, but i'll change how that bit works to hopefully fix it.

commented

Please try with the following versions and let me know if it fixes the issue:

commented

I had the exact same issue as the other people in this thread, after updating to the versiosn above it fixed the issue for me.

commented

Great i'm closing this then, if anyone still has problems with the fixed version feel free to reopen.