Plugin will no longer work on >1.19.1

[Marfjeh]

It seems that Velocity added a kill switch that causes clients to be kicked when using this plugin, they do no longer want to support chat manipulation at the proxy level.

So when sending a message with the plugin will result into this:

There is a issue opened at velocity talking about this exact issue: PaperMC/Velocity#804

[unilock]

It works fine for me on 1.19.2, Paper build #119 + Velocity build #171. Maybe you have another conflicting plugin?

[Marfjeh]

It happens when setting passthrough to false in the config file.

[confor]

i stopped moderating and coding for servers when 1.18 came out so i'm unfamiliar with the 1.19 microsoft chat thing and i have no idea whats happening there, but i'll be paying attention to the velocity dev discord to see how this can be fixed.

[BBaoVanC]

Currently on my server I edited Velocity to make this work. This should work fine when you have passthrough set to false (I've been running it for a few weeks). As a side effect, it disables chat reporting since it replaces every chat message with a system message.

See BBaoVanC/Velocity@13e79bc

I know that Five is working on making proper API to make this all work properly with the chat signing system, so hopefully this will be fixable in the future.

[Marfjeh]

Yeah I also patched it out and its working fine now. I wanted to point out about the kill switch they added

[BBaoVanC]

Related: PaperMC/Velocity#816

[confor]

the current build works fine on my velocity with a 1.19.2 server 🤷

[BBaoVanC]

the current build works fine on my velocity with a 1.19.2 server 🤷

It only happens if passthrough is set to false; see

velocity-chat/src/main/java/me/confor/velocity/chat/modules/GlobalChat.java

Lines 76 to 77 in ce9d03d

	if (!config.GLOBAL_CHAT_PASSTHROUGH)
	event.setResult(ChatResult.denied());

[BBaoVanC]

This should be fixed by installing UnSignedVelocity. I will test this on my server soon.