BungeeViaProxy

# BungeeViaProxy ## TL;DR **BungeeViaProxy** is a (https://github.com/SpigotMC/BungeeCord) plugin that fixes compatibility issues with (https://github.com/ViaVersion/ViaProxy), enabling you to manage multiple backend servers running different Minecraft versions using a single ViaProxy instance. - **Why?** (https://github.com/ViaVersion/ViaBungee) was discontinued in Minecraft 1.20.2. To continue using BungeeCord with the latest Minecraft versions, you need ViaProxy. However, ViaProxy introduces challenges when combined with BungeeCord, such as improper hostname forwarding and duplicate server errors. - **How does it help?** BungeeViaProxy resolves these issues by ensuring correct hostname forwarding and avoiding duplicate server errors, allowing seamless integration of ViaProxy and BungeeCord. - **Who should use this?** Minecraft server administrators running networks with BungeeCord and multiple backend servers that need support for Minecraft versions including 1.20.2 and later, but want to avoid the complexity of managing (https://github.com/ViaVersion/ViaVersion) on each backend server. !(https://cdn.modrinth.com/data/cached_images/1ab51ac8c69d5b9bdfeb504cfa24e410efaacc4c.png) ## Table of Contents - (#overview) - (#use-case) - (#how-it-works) - (#features) - (#installation) - (#note) - (#configuration) - (#example-configuration) ## Overview **BungeeViaProxy** is a BungeeCord plugin designed to address compatibility issues when using (https://github.com/ViaVersion/ViaProxy) with (https://github.com/SpigotMC/BungeeCord). This plugin is especially useful for networks with multiple backend servers running different Minecraft versions, where you want to minimize the overhead of maintaining ViaVersion plugins on each backend server. (https://github.com/ViaVersion/ViaBungee) support was discontinued as of Minecraft 1.20.2, making it necessary to migrate to ViaProxy for compatibility with newer versions of the game. This guide is valuable for those who wish to continue using BungeeCord with the latest Minecraft versions while avoiding the burden of individually updating (https://github.com/ViaVersion/ViaVersion) on each backend server. By leveraging ViaProxy with wildcard-domain-handling, a single ViaProxy instance can support multiple backend servers, simplifying updates and reducing resource usage. ## Use Case BungeeViaProxy is ideal for: - Networks using BungeeCord to manage multiple backend servers running different Minecraft versions. - Administrators who want to maintain compatibility with the latest Minecraft versions using ViaProxy and Bungeecord. - Reducing the operational overhead of updating ViaVersion plugins on individual backend servers by centralizing version translation via ViaProxy. **Important:** When using ViaProxy in such a setup, it must be placed between BungeeCord and the backend servers. Additionally, in ViaProxy's configuration: - `proxy-online-mode` must be disabled. - `auth-method` must be set to `NONE`. - `wildcard-domain-handling` must be set to `PUBLIC`. - `target-address` is ignored (anything is OK) while using `wildcard-domain-handling`. ## How It Works Normally, each backend server would require a separate ViaProxy instance. However, this can lead to increased memory consumption and additional update efforts. To address this, ViaProxy supports the `wildcard-domain-handling` feature, allowing a single ViaProxy instance to handle connections to multiple backend servers. This is achieved by using a specific address format for each backend server: ``` address.<backend-ip>.port.<backend-port>.version.<backend-version>.f2.viaproxy.<viaproxy-ip>.nip.io:<viaproxy-port> ``` These addresses can then be listed in the `config.yml` of BungeeCord, enabling seamless connection management through a single ViaProxy instance. However, this setup introduces certain challenges, which BungeeViaProxy resolves. ## Features 1. **Correct Hostname Forwarding:** When `wildcard-domain-handling: PUBLIC` is enabled in ViaProxy, it may fail to retrieve the hostname specified in BungeeCord's configuration, preventing proper server routing. BungeeViaProxy ensures that any address containing `.viaproxy.` is forwarded correctly to the backend server. 2. **Avoiding Duplicate Server Errors:** BungeeCord treats servers with different hostnames as identical if they resolve to the same IP address, resulting in the error: `You are already connected to this server!`. BungeeViaProxy resolves this by using unresolved `InetSocketAddress` objects, ensuring unique identification for servers with different hostnames. ## Installation 1. Download the latest release of BungeeViaProxy. 2. Place the plugin `.jar` file into your BungeeCord `plugins` directory. 3.