Multi-Version Support

Gate classic can route backend connections through managed Via-powered Java protocol translation. This lets clients join backend servers even when the client and backend Minecraft versions differ.

Enable it with:

config:
  via:
    enabled: true

Gate starts ViaLite and routes backend connections through it. This applies to configured servers and API-registered servers, so dynamic Connect/session backends can use the same version translation path.

Topology

Java player
  -> Gate classic
  -> ViaLite
  -> backend server

Bedrock player
  -> GeyserLite
  -> Gate classic
  -> ViaLite
  -> backend server

ViaLite sits behind Gate. Gate accepts the player, handles routing and events, and then ViaLite translates the backend-facing Java protocol where needed.

Bedrock Players

GeyserLite translates Bedrock sessions into Java protocol before the player reaches Gate. ViaLite can then help with Java backend version differences behind Gate.

ViaLite does not replace Geyser protocol support. If Geyser does not support a new Bedrock or Java version yet, production networks should usually wait for official upstream Geyser support before upgrading Bedrock-critical backends.

Gate Lite

Gate Lite raw-pipes backend traffic after the initial handshake so backend servers keep authentication ownership. Managed Via translation needs to decode and rewrite packets after login, so it belongs to Gate classic backend connections, not Gate Lite.

Runtime Details

For runtime modes, platform support, pins, offline deployment, and release policy, see ViaLite.