Multiconnect and sodium
Titaniumtown opened this issue ยท 6 comments
Expected Behavior
Should be able to connect to a 1.13 server (In my case cuberite)
Actual Behavior
Connects, renders some blocks, then freezes and crashes.
Reproduction Steps
connect to a 1.13 server (in my case, cuberite)
Attachments
System Information
- Java Version: openjdk 14
- CPU: Xeon x5470 oc'd to 4ghz
- GPU: GTX 980 Ti
This looks very similar to #189, which is interesting. In that case, the user is joining a Spigot/Bukkit/etc 1.8.x server with a multi-version plugin (likely ViaVersion). Here you are joining a 1.13.0 server with a multi-version client mod. This suggests something is fishy with the packet data itself, or at least how Sodium is interpreting it.
It would help if you report these issues to the multiconnect repository where I see them, rather than having to be told days later by a user who did see this.
Your crash log is missing information. Please post the full log and not just what you think is relevant.
@Titaniumtown Can you post the full log please as Earthcomputer suggested?
Closing as this user is unable to reply anymore, and Earth says the problem is fixed.
I'm pretty sure this is a duplicate of #189, but the use of protocol translation mods/plugins might be a clue? Maybe the protocol translation code syncs tags in a different order (or not at all) which causes the blockstate shape caches to not be loaded.
Tags are synchronized in a hashmap order, and multiconnect has had a check for ages that all required tags are present (vanilla also added a similar check more recently). The actual problem was that multiconnect was incompatible with the SodiumChunkCache, which was fixed a long time ago now.