Covariant GameCovariant Game

Docs

Setup instructions for connecting your Minecraft servers to Covariant Game.

Proxy protocol (real player IPs)

When players connect through us, your backend sees our IP addresses instead of theirs. Proxy protocol is a standard that fixes this: it passes each player’s real IP to your backend, so features like IP banning and per-player logging work correctly.

Proxy protocol is always on for every connection through us. There is no option to turn it off: every backend receives proxy protocol, so every connection to your backend must speak it. Direct connections to your backend stop working — which is exactly what protects your server.

Your backend server must be configured to expect proxy protocol. If it is not, players cannot connect. Below are setup steps for the most common servers and proxies.

BungeeCord / Waterfall

In config.yml, set:

proxy_protocol: true

Velocity

In velocity.toml, set:

haproxy-protocol = true

Paper 1.19+

Only enable this if you are not running a proxy like BungeeCord or Velocity in front of your server. Paper supports proxy protocol natively since version 1.19, no plugin needed. In config/paper-global.yml, set:

proxy-protocol: true

Geyser (Bedrock)

Geyser is not configured with proxy protocol here: Bedrock players do not connect to it that way. Over NetherNet, we forward player IPs with the X-Forwarded-For header instead, and Geyser accepts that header from our IP list (game.covariantedge.com/ips.txt). The full Geyser setup steps are in the NetherNet guide — there are no other options to set.

If Geyser sits in front of your Java server, note that Geyser’s advanced.java.use-haproxy-protocol option is usually required as well: your Java side is configured to expect proxy protocol by this guide, so Geyser must send it.