Open AngelofWoe opened 2 years ago
It seems to be caused by vanilla clients without the mod. Probably from the addition of the portal block. I tried with two identical clients, one with the mod and one without. Only the vanilla one crashes.
Do you have any other mods adding blocks on the server? I'm guessing its from the block registry mismatch. 1.17 didn't seem to care about this, maybe they broke this in 1.18
I'm running the client with the mod (and without). There are no block mods on the server.
I pulled Lithium and Dynmap off (the only other two mods we're running right now)
The only mods I'm running client side for this testing.
fully working on my 1.19.2 server, even works behind a velocity proxy too ... sometimes you just have to update ....
Server running 1.18 and the most up to date Fabric loader and Fabric API. Server is a test upgrade for a 1.17.1 server running Fabric, Lithium, and Datapack Portals. Our 1.17.1 instance is running fine, but on the test version of 1.18 I'm running, any time the 1.18 version of Datapack Portals is loaded on the server, all clients crash when attempting to render the blocks that make up the portals. Crashes don't seem to be tied to any mods on the client side, the clients can have absolutely no mods installed or just Datapack Portals and they crash.
The launcher on the client gives the same error mentioned in the following 1.18 preview bug report marked as resolved:
https://bugs.mojang.com/browse/MC-242647 "The game crashed whilst getting block state Error: cqm: Missing Palette entry for index 67. Exit Code: -1"
However, I can only duplicate this error when the server is running datapackportals-1.1.0-1.18.jar. After removing the mod from the server, client behavior is normal.
No errors are seen on the server end.