William

**This issue is caused by Velocity as of yet not having implemented a chat API for the chat changes introduced in 1.19.2**. To fix it, simply [install UnsignedVelocity](https://modrinth.com/plugin/unsignedvelocity) and its'...

~~Update: Enquired with the Velocity team, they're working on the API still and this will be resolved soonish :-) I'll leave this open until then!~~ It'll probably be awhile before...

I have updated this post https://github.com/WiIIiam278/HuskChat/issues/72#issuecomment-1200896060 with more details and a FAQ.

> Hey any updates reguarding that ? Nope. When Velocity adds their chat API, things can move. Waiting on them :)

> Is there a workaround with like using a older Velocity Version? Nope. This is a Velocity issue; they haven't implemented a chat API yet as they want to do...

@voruti That's neat! Only issue of course is that you can't format the (at least, locally received) messages, or do channel switching, etc, which I think is pretty extremely important

Not sure bungee or velocity APIs will support this (they definitely don't at the moment), or if it's even practical, plus we target 1.16 API rather than 1.19 -- but,...

1.19.3 note: this feature has been adjusted somewhat, the packet now displays an uncustomisible "Message deleted" thing in chat if you do this. There's actually no API provided by anyone...

It's not currently really, it goes by what the name is as defined by your proxy. I guess I could add some way of adjusting the capitalisation? But substituting it...

In short, yes -- I designed HuskSync's core logic decoupled to allow for that in the future -- if you want to port to fabric and maintain it, please go...