Proxies and Bedrock

Configure Velocity, BungeeCord, Geyser, and Floodgate so every player connects cleanly.

Velocity and BungeeCord setup

Install Epsilon and PacketEvents directly on every Paper backend server behind your proxy. Nothing installs on Velocity or BungeeCord itself.

Move ViaVersion onto each backend

If ViaVersion is installed on your proxy, remove it from proxy/plugins and place it on each Paper backend instead.
Keep forwarding configured cleanly

On Velocity, keep modern forwarding enabled so player UUIDs and client details arrive cleanly on each backend server.
Forward proxy bans if using Cloud

Set ban-command and kick-command in plugins/epsilon/config.yml to use your network ban plugin so bans apply across all backends.

Bedrock players (Geyser and Floodgate)

Bedrock movement and combat differ fundamentally from Java Edition. Epsilon detects Geyser players automatically and lets them play normally without false flags.

Where Geyser runs	What Epsilon needs to recognize Bedrock players
On the Paper server	Keep Geyser default direct connection enabled, or install Floodgate on that Paper server.
On a Velocity proxy	Enable modern player forwarding in Velocity, or install Floodgate on each Paper backend with send-floodgate-data enabled and your proxy key.pem copied.
On a BungeeCord proxy	Install Floodgate on each Paper backend as well, with send-floodgate-data enabled and your proxy key.pem copied.