Type of bug

Exploit

/ess dump all output

https://essentialsx.net/dump.html?id=f8e83c7b4ad74d5f9e402146452e3740

Error log (if applicable)

None

Bug description

When using the Fabulously Optimized Minecraft Modpack off Curseforge and logging in to a server and typing something causes everyone on the server to be disconnected for the first message typed.

Steps to reproduce

1. Run the server with Essentials Discord Plugin.
2. Login two accounts to the server with one of them using the Fabulously Optimized Minecraft Modpack off curseforge.
3. Have the account using the modpack type anything into chat.

Expected behaviour

No one gets disconnected and message is handled properly.

Actual behaviour

Everyone gets disconnected when the person types.

[17:49:22 INFO]: HolesInDonuts: test
[17:49:22 INFO]: DefinitelyAFrog lost connection: Disconnected
[17:49:22 INFO]: - DefinitelyAFrog
[17:49:22 INFO]: HolesInDonuts lost connection: Disconnected
[17:49:22 INFO]: - HolesInDonuts

With the message:

Chat message validation failure.

Would not be an Essentials bug, either Paper (it's not) or a Client issue.

It isn't a client issue. This only happens when Essentials Discord is used. I believe that special client is adding on special characters into chat in some way that is causing the Essentials Discord to parse and kick everyone. Regardless of what client you use, everyone gets disconnected.

It isn't a client issue. This only happens when Essentials Discord is used. I believe that special client is adding on special characters into chat in some way that is causing the Essentials Discord to parse and kick everyone. Regardless of what client you use, everyone gets disconnected.

It would be a Spigot/Paper issue then. Extremely low chance it's us

As JRoy already mentioned, not really anything for us to "fix" here given that Essentials Discord doesn't do anything beside use standard API on our end.

Just as a general note here, the mod pack you linked also contains mods which are known to impact chat, so I wouldn't be surprised if this is in fact a client issue. Especially if this is not reproducible without these mods. It's very unlikely that there's anything we can do here, so you'll probably want to either report upstream (to the specific offending mod, or Spigot/Paper, as appropriate) or find another workaround if possible.