Closed TheSabotender closed 5 months ago
This seems to happen when the client has the mod, but the server doesn't. My guess is that because the client has an extra blockstate for the lantern block, but the server doesn't, things will get messed up. If my guess is right, then I don't think there is a way I can fix this issue. However, I will mess around and see if there is anything that I can do to fix this.
In the meantime, I will try to add a warning when this bug could happen. This warning will inform the user that they should remove the mod of they could experience "severe issues."
not mod related but u might want to look into polymc its a launcher that lets u have seperate instances with their own mod and saves
Since the implementation of Statement, this should not happen. I'll do some testing when I have time to confirm that this is fixed.
@ThePoultryMan this should also be applied to the 1.20 branch as it messes all of the blockstates up in large modpacks.
This issue no longer seems to happen since integrating statement.
I have this mod installed locally, when connecting to a vanilla 1.19 server, some blocks are replaced:
In the screenshot you can see Mud becoming leafs, Dripstone becoming copper blocks, and at the edge of the picture a Composter becoming Water