Open unilock opened 6 days ago
Wasn't this fixed in 2.0.17? Or did it break again?
Testing v2.0.16 and v2.0.18 had the same results, as described here. v2.0.17 leads to a disconnect similar to that of https://github.com/Sinytra/ForgifiedFabricAPI/issues/166 and https://github.com/Sinytra/Connector/issues/1512 (on a dedicated server, not singleplayer!)
Sometimes, the game does let me join, but the server log is spammed with:
[Netty Server IO #1/WARN] [ne.ne.ne.ne.re.NetworkRegistry/]: No registration for payload cardinal-components:chunk_sync; refusing to decode.
[Netty Server IO #1/WARN] [ne.ne.ne.ne.re.NetworkRegistry/]: No registration for payload cardinal-components:entity_sync; refusing to decode.
...among similar messages for other payload types from Fabric mods.
With Cardinal Components API installed, alongside a Fabric mod that adds a Component that requires syncing between client and server (in this case, Trickster), the client disconnects immediately after joining a dedicated server. (singleplayer works fine)
latest.log (client): https://gist.github.com/unilock/9ea8f4888b3ecffbb023474066bb9b4d latest.log (server): https://gist.github.com/unilock/c5f16e51b70fc77c8f14864afb8fb019
To reproduce:
This server requires Cardinal Components API (unhandled packet: cardinal-components:entity_sync)