Incompatibility problem with SunLight plugin's chat module

[A248]

@Xbani I am opening this issue to track the incompatibility with SunLight's chat module. I'm cc'ing @nulli0n who develops SunLight.

Original bug described here: #282 (comment)

Triggers:

• SunLight's event priority seems to make no difference
• Its chat component setting apparently does

I wasn't able to figure out how the chat component setting causes mutes to break. I will do more work on this and maybe collaborate with the Sunlight developers.

In the meantime, I have some tips for you:

• You're running LibertyBans on both the proxy and backend servers. Have you tried just installing it on the backend servers (and not the proxy), and setting it up as explained in the docs?
• It's possible that the bug is compounded by an interaction with SignedVelocity. If it's possible and you have the time to test with pre-1.19 clients on a copy of your network without SignedVelocity, we can rule out SignedVelocity as a factor.

[Xbani]

Hi, I've try the backend only. No fix with the particular usecase of Components Messages with sunlight chat.
I'll not be able to test pre-1.19 since I cant find a Sunlight version for pre-1.19.
I'll switch back to Use_Component = false from SunlightChat for now.

Thanks for the support

[A248]

Please try using SignedVelocity-Legacy and tell me if it works.

The maintainer of SunLight chat has not responded, but I looked at their code anyway since it's open source.

[nulli0n]

I'm working on rewriting the most of the SunLight's code, where it'll use Paper's AsyncChatEvent that has native component support.