Servux sends oversized plugin message through Velocity when MiniHUD is installed on the client

[Eldon27232]

Environment:

• Proxy: Velocity 3.5.0-SNAPSHOT
• Backend: Fabric 1.21.x with FabricProxy-Lite
• Server mod: Servux
• Client mod: MiniHUD

Problem:
When a player with MiniHUD joins this Fabric backend through Velocity, the connection to the backend is dropped immediately after joining.

Velocity log shows:
io.netty.handler.codec.CorruptedFrameException: Packet sent for class com.velocitypowered.proxy.protocol.packet.PluginMessagePacket was too big (expected 229378 bytes, got 277132 bytes)

Behavior:

• Servux installed on backend + MiniHUD on client -> disconnect
• Remove MiniHUD -> works
• Remove Servux -> works

This strongly suggests that a Servux-related plugin message becomes too large when sent through Velocity.

Could Servux be sending too much data in a single plugin message on join?
Is there any config option to reduce the initial sync size or split the payload into smaller packets?

[Eldon27232]

Environment:

• Minecraft: 1.21
• Proxy: Velocity 3.5.0-SNAPSHOT (git-6ce432e4-b588)
• Proxy forwarding mode: modern
• Backend: Fabric 1.21
• Backend forwarding mod: FabricProxy-Lite 2.10.1
• Server mod: Servux 0.3.16
• Client mod: MiniHUD

Problem:
When a player connects to my Fabric backend through Velocity, the player joins successfully and is then immediately disconnected back to the lobby, but only when:

• Servux is installed on the backend, and
• MiniHUD is installed on the client.

If either one is removed, the problem disappears.

Velocity-side error:
io.netty.handler.codec.CorruptedFrameException: Packet sent for class com.velocitypowered.proxy.protocol.packet.PluginMessagePacket was too big (expected 229378 bytes, got 277132 bytes)

Observed behavior:

• Player connects to the backend successfully
• A very large PluginMessagePacket is sent immediately after join
• Velocity rejects it and disconnects the backend connection
• Player is sent back to the lobby

What I tested:

1. Remove MiniHUD from the client, keep Servux on the backend -> works normally
2. Keep MiniHUD on the client, remove Servux from the backend -> works normally
3. Keep both Servux and MiniHUD, connect through Velocity -> disconnect happens consistently

Server-side notes:

• Servux version is 0.3.16
• I could not find a standalone Servux config file in the backend config directory, so I could not reduce or disable the initial sync payload from configuration
• I also noticed this startup warning involving Servux:
  @reDIrect conflict. Skipping carpet-extra.mixins.json:ServerPlayNetworkHandlerMixin from mod carpet-extra ... already redirected by mixins.servux.json:network.MixinServerPlayNetworkHandler_EasyPlace from mod servux ...

Question:
Is Servux sending too much data in a single plugin message when MiniHUD is present on join?
If so, is there any way to:

• reduce the initial sync size,
• split the payload into smaller packets, or
• disable the specific sync feature causing this?

Additional context:
The backend log shows the player does successfully join and then immediately disconnect, which matches the Velocity-side oversized packet error.

[02:40:02] E_ldon joined the game
[02:40:02] E_ldon lost connection: Disconnected