Client Crash on Bungee Server Switch
Opened this issue ยท 6 comments
When switching servers on a 1.7.10 Bungee network. I get the following crash:
BigReactors 0.4rc8 on a Cauldron server on a Bungee network.
Not sure what a Bungee network is, but this problem results either from a corrupted world or from mismatched blockIDs. I expect the problem lies with your configs.
I logged in fine the second time, but there is no IDs in 1.7? Bungee is just used to connect multiple servers together seamlessly.
There are IDs behind the scenes, actually. They're mapped from string names to ID numbers on client login, and generally programmers don't have to think about them. When you initially connect to a server, you get its mappings loaded on your client.
In this case, you probably have two servers which have assigned different behind-the-scenes IDs to multiblock glass. On one server, an ID is assigned to some block with a wide range of metadata (e.g. wool); on another server, it's assigned to multiblock glass, which has 2 metadata IDs.
If you initially connected to the latter server, then transferred to the former, it's conceivable that some colored wool was interpreted by your client as multiblock glass, which then tried to retrieve a texture for the glass which falls outside the metdata range for multiblock glass.
As that's a data corruption condition, the system fails noisily and takes down your client.
This is probably a problem with the Bungee system; it likely needs to perform an ID remap each time you switch servers, or else you need to ensure that all your servers use identical blockIDs.
While they use identical sets of mods and configs (I believe - will check), Bungee performs a handshake reset to connect to each server properly I believe. I'll have a look into it myself and make sure everything is as it should be.
Either way, the fact that there's a metadata mismatch is an indication of either map corruption or a configuration problem. This isn't a BR issue.