Mathias Neumann

Are there any updates on this issue? I wanted to use the API, but I specifically need this feature for my use case.

It actually looks like Velocity does **not** support the Fabric-API properly. Fundamental additions made to the Login Process are not supported by Velocity and are causing these errors. Essentially Velocity...

Yeah, it could be possible to generalize this approach so that every channel gets forwarded like that, but I'm not sure. Either way this would be a temporary workaround and...

LandonDeam's Problem is probably that (Login-)PluginMessages with the Channel-ID `fabric-networking-api-v1:early_registration` are not forwarded properly which causes kind of a chain reaction that results in non-joinable Fabric servers when the Fabric...

It requires marginal code changes (one line of code, to be exact). Everything else is just downgrading dependencies (MC and Fabric). Replace L16 of [Fabric's SignedVelocity.java](https://github.com/4drian3d/SignedVelocity/blob/main/backend/fabric/src/main/java/io/github/_4drian3d/signedvelocity/fabric/SignedVelocity.java) with this: `public static...

@levlevin if you still need a build for 1.20.6: https://github.com/HuebCraftDev/SignedVelocity this fork probably wont be maintained. I just needed a build for 1.20.6 and created one myself

For all Velocity Plugin devs reading this: an ugly hotfix is to just send the message to the `RegisteredServer` yourself and returning `ChatEvent.denied()` even when you just modify the messages...