multiconnect

multiconnect

108k Downloads

Item texture error.

plusls opened this issue ยท 6 comments

commented

image
image
image

First I connect to an 1.16.1 fabric server, multiconnect work normally. After that I start singleplay, all item texture shuffled.

1.16.1 server with gravestone mod, it register gravestone block in server but cheat client that it is a player skull.

server address: beta.uestc.dev

commented

Again, if anyone can find a reliable way of reproducing this issue, it will be much easier for me to take a look at it

commented

This bug always occurs in my client(1.15.2), even when single player. Sometime when I open my inevntory and scroll to some item, the games crashes. Maybe because the game failed to show two textures mapped from the single object.

commented

it register gravestone block in server but cheat client that it is a player skull

You mean it "tells" the client, not "cheats" it? You almost had me insta-close this for cheat clients then.

Anyway, that sounds fishy, multiconnect is supposed to disconnect you when the server registry has been modified at all. Maybe it has something to do with that, I'll have to check exactly what the gravestone mod is doing. But I've had this happen after connecting to vanilla servers too, no idea what the cause is.

commented

In the case of the same version, fabric will send CustomPayloadC2SPacket to sync the block id registry.

But in the case of different versions, the CustomPayloadC2SPacket of fabric is blocked, so it can connect to the server directly.

As for cheat, it is because I originally intended to prevent the block synchronization behavior of the fabric, because the gravestone block has not texture, and the server tell the client that this is a vanilla skull block instead of a gravestone block. So the gravestone mod can support vanilla client.

commented

I can personally confirm that the gravestone mod does not cause this issue. It is simply an issue with multiconnect. I have connected to a fabric server with just multiconnect and loaded into a singleplayer world with this same issue. I don't exactly see why this is marked as low priority as it makes playing the game borderline impossible without restarting the game.

commented

I only know that i can reproduce this bug via gravestone mod. For developers, a way to stably reproduce bugs is very important.