Cannot join dedicated server with Cardinal Components API (unhandled packet: cardinal-components:entity_sync)
unilock opened this issue ยท 5 comments
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:
- Set up a Minecraft 1.21.1 client and server with NeoForge 21.1.77
- Install the following mods on both sides:
- Sinytra Connector v2.0.0-beta.3+1.21.1
- Forgified Fabric API v0.104.0+2.0.18+1.21.1
- Cardinal Components API v6.1.2
- Trickster (specifically this build with Sinytra Connector support)
- Accessories v1.1.0-beta.16+1.21.1
- CICADA v0.9.1+1.21-1.21.1
- Lavender v0.1.14+1.21
- owo-lib v0.12.15-beta.9+1.21
- Start the client and the server
- Attempt to join the server from the client
- Disconnect due to
This server requires Cardinal Components API (unhandled packet: cardinal-components:entity_sync)
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 #166 and Sinytra/Connector#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.
Should be fixed by #170, haven't tested
#170 does appear to have fixed the issue :)