[Issue] Proxy MOTD is displayed instead of server MOTD when using BCC + Velocity on Forge 1.20.1

[Diamondback88]

Minecraft Version

1.20.1

Modloader

Forge 47.3.0

Mod version

forge-4.0.8+mc1.20.1

Latest version?

• Yes

Repeatable?

• Yes

Link to log files

https://mclo.gs/Em3oGH8

Steps to reproduce the issue

1. Install a Velocity server with the latest version of Velocity. Set the player-info-forwarding-mode to "modern" in velocity.toml, and configure your modded server in here as well.
2. Add the latest version of the Ambassador plugin to the plugins folder; this is needed for Velocity on Forge 1.20.1.
3. Set up the latest version of ProxyCompatibleForge for your modded server; this is also needed for Velocity on Forge 1.20.1.
4. Boot the server and notice that the MOTD doesn't say "A Minecraft Server," but instead it says whatever you set the motd field to in velocity.toml.

Description of the issue you are having

When using Velocity with Forge & this mod, you should be your modded server's MOTD rather than your proxy's MOTD. Instead, you incorrectly see your proxy's MOTD.

Information

• I have provided as much information as possible

[2lay]

I've reproduced this issue with the same results on my end.

[LevyWilson]

Same on my end. My servers use Velocity and PCF for modpacks ranging from 1.18 to 1.21 servers. I have to remove BCC from all servers or the MOTD doesn't update like it should.

[MRMDevStudios]

We’ve encountered a related but slightly different issue while running a Velocity proxy setup. Specifically, we're using the AJQueue sorting plugin on our proxy, and it fails to properly transfer users when BetterCompatibilityChecker (BCC) is enabled.

After some testing, we identified that BCC appears to inject additional packets during the handshake phase, which Velocity is unable to decode correctly. This seems to interfere with both MOTD handling and player forwarding in more complex proxy environments.

As a temporary workaround, we resolved the issue by removing BCC. I haven’t revisited this in a few months since that workaround was sufficient for the time being, but it’s far from ideal. Each time we update modpacks that include BCC, we’re forced to manually remove the mod again—which isn’t sustainable at scale.

Ideally, BCC could include a mechanism to detect when it's running behind a proxy and switch to proxy-compatible behavior—either by skipping certain handshake logic or using a more compatible communication method.

We’d prefer a proper fix over continuing with the workaround and would be happy to provide additional logs or help test potential solutions.