Version Connector 1.5.1

Redirect different client versions to different servers. With Forge support and load balancing!

  1. Phoenix616
    Tested Minecraft Versions:
    • 1.7
    • 1.8
    • 1.9
    • 1.10
    • 1.11
    • 1.12
    • 1.13
    • 1.14
    • 1.15
    • 1.16
    • 1.17
    • 1.18
    Source Code:
    [​IMG] Made in Germany with love (and beer)
    Bungee plugin to connect different Minecraft client versions to different servers when he joins your BungeeCord network. You can even specify the exact protocol version you want to send to a different server as long as your BungeeCord supports those versions.

    It also contains a simple load balancer (add multiple server names to a version separated by a comma like in the config example below) which connects players to the server with the lowest player count and a really basic support to connect Forge clients to a different server. (Only works with 1.8-1.13 Forge clients)

    This plugin will not allow older or newer versions to connect to your network if the BungeeCord proxy/Minecraft server does not support the old version! You have to use some other plugin/program to do that. (E.g. ViaVersion, ProtocolSupport or Travertine)

    Versions with string representation:
    It will fallback to the version with the closest protocol number below the actual client's protocol. You can however set the protocol version directly if you want or propose additions to the ProtocolVersion enum.
    Italic ones are in the latest dev builds
    • 1.18 (Protocol version 757)
    • 1.17.1 (Protocol version 756)
    • 1.17 (Protocol version 755)
    • 1.16.5 (Protocol version 754)
    • 1.16.4 (Protocol version 754)
    • 1.16.3 (Protocol version 753)
    • 1.16.2 (Protocol version 751)
    • 1.16.1 (Protocol version 736)
    • 1.16 (Protocol version 735)
    • 1.15.2 (Protocol version 578)
    • 1.15.1 (Protocol version 575)
    • 1.15 (Protocol version 573)
    • 1.14.4 (Protocol version 498)
    • 1.14.3 (Protocol version 490)
    • 1.14.2 (Protocol version 485)
    • 1.14.1 (Protocol version 480)
    • 1.14 (Protocol version 477)
    • 1.13.2 (Protocol version 404)
    • 1.13.1 (Protocol version 401)
    • 1.13 (Protocol version 393)
    • 1.12.2 (Protocol version 340)
    • 1.12.1 (Protocol version 338)
    • 1.12 (Protocol version 335)
    • 1.11.2 (Protocol version 316)
    • 1.11.1 (Protocol version 316)
    • 1.11 (Protocol version 315)
    • 1.10 (Protocol version 210)
    • 1.9.4 (Protocol version 110)
    • 1.9 (Protocol version 107)
    • 1.8 (Protocol version 47)
    • 1.7.6 (Protocol version 5)
    • 1.7.2 (Protocol version 4)
    Please note: It is not necessary for a version to have a string constant! You can just add the protocol number in the config. (e.g. 477 for 1.14 or 404 for 1.13.2)
    Code (YAML):
    debug: false
    # Minimum amount of players that need to be online on one server to start balancing
    # new players to the other server (e.g. between lobby_1_8_a & lobby_1_8_b)
    : 0
    : lobby_prot_34 # Lobby for specific protocol version
    : lobby_1_8_a, lobby_1_8_b # Lobbies for 1.8
    : lobby_1_9 # Lobby for 1.9
    : well_we_dont_know # Lobby for an Unknown version (not a fallback if no config for version was found!)
    : forge_lobby_1_9
    : forge_lobby_1_8_a, forge_lobby_1_8_b
    : survival_1_8
    : survival_1_10
    : survival_wat
    : forge_suvival_1_9
    : forge_suvival_1_8_a, forge_suvival_1_8_b
    This config defined two different groups of servers, one for lobbies and one for survival servers.

    Once a player that uses 1.8 connects to your network that has the server lobby_1_9 as the default one configured he will automatically be redirected to connect to the lobby_1_8_a server, but only if the server lobby_1_8_b doesn't have less players online. (By adjusting the start-balancing setting you could only start the balancing once 10 players for example are on the server lobby_1_8_a)

    When the player then tries to switch to the server survival_1_10 (e.g. via a portal that only supports defining a single target server) he will be connected to the server survival_1_8 instead as it matches his version.​


    /versionconnector, aliases: /vercon, /vc, permission: versionconnector.command

    /vc reload versionconnector.command.reload
    Reloads the config

    /vc config versionconnector.command.config
    Shows the current mapping of version to server set in the config

    /vc check versionconnector.command.check
    Shows how many players are connected with which version/protocol

    /vc check <playername> versionconnector.command.check.other
    Shows the version and protocol of a specific player

    /vc check -all versionconnector.command.check.all
    Shows a sorted list of all players and their versions​


    The source can be found on this GitHub Repo including direct release jar downloads via the release tab.​

    Development builds can be found on the Jenkins as usual:
    Programming is time intensive and I would really appreciate your support!
    So if you can afford it or make commercially use of this plugin feel free to buy me a beer.
    Patreon with rewards: [​IMG]
    Ðoge: D7G4Svo7GTNHpuhjwUBj2k7qANnZHwYD4p
    BTC: 1EXMFRknc7kLwCmM1zf5LXNnPD4ihVCEhQ

    My Resources:
    This resource is distributed without any warranty or liability by the author.
    Diclo, 96Maciek96, Aoro and 2 others like this.

Recent Reviews

  1. MiftikCZ19
    Version: 1.5.1
    I´m added this plugin to my 1.16.5 spigot server, but i can´t connect with 1.8.9
    1. Phoenix616
      Author's Response
      Please read the description, this plugin does not allow you to connect to a server with a mismatching version, it allows redirecting different versions to different servers.
  2. monaldcry7758
    Version: 1.5.1
    Hello, I've installed VersionConnector but it doesn't work, even after following the whole guide correctly.
    Is there another guide or tutorial about it?
    1. Phoenix616
      Author's Response
      The resource description, default config as well as the GitHub readme should contain all the information regarding how to set it up correctly. If you have issues applying that for your unique situation then feel free to write about it in the discussion thread, in my IRC channel (#moep on or discord (
  3. AlexMiller
    Version: 1.5.1
    Update 1.16.2)
    1. Phoenix616
      Author's Response
      1.16.2 is already supported in it by using the protocol ID and with a string version in the dev builds.
  4. Kalendarz2
    Version: 1.5
    Great plugin, everything works as intended.
    Exactly what I was looking for :)
    1. Phoenix616
      Author's Response
      Thank you :)
  5. U-ENERGYoff
    Version: 1.4.1
    It is the best plugin of the world and bungeecord! But I have one question:
    Is it support ProtocolSupportBungee? I really need it!
    1. Phoenix616
      Author's Response
      If ProtocolSupportBungee doesn't mess with Bungee's inbuilt protocol version detection then this should work just fine with it.
  6. WoomeliCODES
    Version: 1.4.1
    This plugin is a dog shit... Never use this shit! This will break your server! So dont use this!
    1. Phoenix616
      Author's Response
      Can you please provide some information about how it breaks your server in the discussion thread or a github issue? (Especially the especially error messages if there are any but configs, general debug logs and plugin, server and client versions also helps) I'm able to use it without any "breaking" going on and so are multiple others.
  7. minecraft7net
    Version: 1.3.1
    excellent resource used on my network many thanks for improvements and quick add feature requests :) and please keep this good work
  8. DiscowZombie
    Version: 1.1
    Nice :)

    I go test and I tell you :) I espert my problem is corrected ! The command are convenant ;)