Starter config.yml aligned with the SpigotMC BungeeCord Configuration Guide: listeners, servers, online_mode, ip_forward, permissions, and forced hosts. Review before production.
Listener
Global settings
With ip_forward true, set each backend Spigot/Paper online-mode=false and enable BungeeCord mode in backend config. See Spigot wiki: BungeeCord Configuration Guide and IP Forwarding.
A BungeeCord proxy needs a config.yml with listeners, server list entries, priorities, and online-mode / IP-forward settings before it will boot in a useful way. This tool builds a starter file for lobby-plus-game layouts so you are not copying random pastebins. It is not a finished production lockdown and not a Velocity TOML generator.
What this tool does
You set listener host and MOTD, map backend server names to host:port, choose priority order, optional forced hosts, and the common online_mode and ip_forward flags. The output is a config.yml in the general shape Bungee expects. You still place it on the proxy machine and harden permissions, firewalls, and groups.
Backends and IP forwarding
When ip_forward is true, backend Paper or Spigot servers usually run online-mode=false and are configured to trust the proxy. Get that wrong and you see broken UUIDs, cracked joins, or security holes. Only expose the proxy port publicly; keep game ports on private networks when you can.
Forced hosts and priorities
Priorities decide which backend players land on by default. Forced hosts map a domain name to a specific server entry so play.example.com and skyblock.example.com can split traffic. DNS must point those names at the proxy, not at random backend IPs, or the forced-host map will never run.
What to change before going live
Replace example hosts, default passwords-looking groups, and sample MOTDs. Review connection throttle, query settings, and permissions. Treat the download as a scaffold you review line by line, not as a file you open to the internet blindly.
Velocity note
Velocity uses a different config format and modern forwarding modes. If your network is Velocity-first, use Velocity docs for that path. This page targets classic BungeeCord-style config.yml for people still on that stack or learning proxy basics.
Quick questions
Can I use this live as-is?
Not safely. Fix hosts, permissions, and firewall rules, then open ports carefully.
What about Velocity?
Different format. This generates Bungee config.yml, not Velocity TOML.
Why offline-mode on backends?
The proxy authenticates with Mojang and forwards identity. Backends trust that only when forwarding is set up correctly.
Players land on the wrong server?
Check priorities, forced hosts, and DNS. The proxy only routes what the config and domain names describe.
Is Waterfall the same?
Waterfall is Bungee-compatible enough for many configs, but always test on your real proxy jar.
What do you think about this tool?
If something feels wrong, a Minecraft version is missing, the wording is confusing, or you have a better workflow idea, send it over. Real player feedback is how these tools get sharper.