Network mode (Velocity)¶
Note: Network mode and the
NewBedwars-Proxyplugin are available from 2.6-beta. Version 2.5-beta and older can not run on a network.
NewBedwars can run on a proxy network: lobby servers where players choose a game, and game servers that host the arenas. Players and parties are moved between them automatically.
By default (Network.Mode: NONE) NewBedwars is a single server and nothing on this page applies.
What you need¶
| Where | What |
|---|---|
| Velocity proxy | NewBedwars-Proxy-<version>.jar in plugins/ (Velocity 4.x, Java 25) |
| Every lobby and game server | NewBedwars-<version>.jar (same version on all of them) |
| Optional | A MySQL/MariaDB database that game servers and the proxy can reach |
Set up Velocity forwarding as usual (player-info-forwarding-mode = "MODERN" in velocity.toml, proxies.velocity in each Paper server's config/paper-global.yml).
Install the proxy plugin. Besides routing, it blocks players from sending fake NewBedwars network messages to your servers. Don't run
Network.Mode: GAME/LOBBYwithout it.
Scoreboard¶
/server/ in scoreboards.yml shows the server's name (Network.ServerId); the default waiting scoreboard has a Server: line. A line with /server/ is left out on a single server. Existing scoreboards.yml files are not changed by an update: add the line yourself.
Is MySQL required?¶
(For a single server see storage.md.)
No. Every feature works without a database, on one server or on a network. MySQL/MariaDB only adds:
| Feature | Without MySQL | With MySQL |
|---|---|---|
Stats and player data (Storage.Type: MYSQL) |
Each server keeps its own stats, leaderboards and player settings in JSON files | Shared by every server of the network |
Server status (Network.MySQL.Enabled on game servers + mysql: in the proxy config) |
The proxy only knows a game server's arenas while a player is online on it; a server it has not heard from is still tried and picks an arena itself | The proxy always knows every game server's arenas, also right after a restart |
| Rejoin notice on the lobby | Works when somebody else is still online on that game server to carry the message | Always works (the status table carries the rejoin places) |
Joining through the proxy, parties, rejoining, map voting, RestartAfterGames, NPCs and placeholders all work without MySQL.
Server config (plugins/NewBedwars/config.yml)¶
Network:
Mode: GAME # GAME on game servers, LOBBY on lobby servers
ServerId: "game1" # this server's name in velocity.toml [servers]
LobbyServer: "" # GAME: lobby to send players to; empty = the proxy picks the least full lobby
LocalLobby: false # GAME: false = no /bw setLobby needed on game servers (see below)
LobbyJoinMessages: true # LOBBY: show "<player> joined/left the game" (game servers never show it)
RestartAfterGames: 0
TicketTimeoutSeconds: 10
StatePublishSeconds: 5
MySQL:
Enabled: false # GAME: write the server status to the shared table (uses the MySQL section)
HeartbeatSeconds: 5
Storage:
Type: MYSQL # share stats, leaderboards and languages across the network
MySQL:
Host: "localhost"
Port: 3306
Database: "newbedwars"
User: "root"
Password: ""
SslMode: PREFERRED # DISABLED, PREFERRED, REQUIRED, VERIFY_CA or VERIFY_IDENTITY
AllowPublicKeyRetrieval: false # only for MySQL 8 without SSL; less secure
Game servers (Mode: GAME)¶
- Set up arenas as on a single server. One server can host one or many arenas. Arena groups are not set here (see the lobby below);
/bw groupon a game server only lists them, and its owndata/groups.jsonis not used. - No lobby needed (
LocalLobby: false, default): players who arrive and wait for their arena, or who leave a game, wait for that moment invisibly in spectator mode at the world spawn, then go into the arena or on to a lobby server. WithLocalLobby: truethey are teleported to this server's/bw setLobbylocation instead (the old behaviour). - Players who arrive from the proxy go straight into the arena the proxy picked (parties together). A player who arrives without a join request is sent back to the lobby after
TicketTimeoutSeconds. Staff withnewbedwars.network.bypass(default: op) can stay, e.g. to set up arenas. - After a game (or
/bw lobby), players go to a lobby server. With map voting, players who vote move to the next arena on the same server. RestartAfterGames: <n>(0 = off): afternfinished games the server is marked "restarting": the proxy and lobbies send no new players there, running games finish normally, and once no arena has players everyone left is sent to a lobby and the server shuts down. Your start script (or panel) has to start it again; the plugin only stops it. Useful to clear memory and old chunks of game servers that run for days.- Map voting across servers: at the end of a game the vote offers the free arenas of the same group on every game server (the item shows the server). If an arena on another server wins, everyone (parties together) is moved there through the proxy.
Lobby servers (Mode: LOBBY)¶
- No arenas are loaded.
/bw joinopens the arena selector with the arenas of all game servers; clicking an arena takes you to exactly that server's arena./bw join <group|arena>asks the proxy for the best game: an arena name that exists on several servers means the fullest of them that has room./bw join <server>:<arena>(andARENA <server>:<arena>join NPCs) go only to that server's arena.- Arena groups are made here with
/bw group(see commands.md)./bw group add <group> <arena>adds that arena on every game server that has it;/bw group add <group> <server>:<arena>only one server's arena. Problems and team sizes are checked against the arenas the game servers report. The proxy uses them right away for routing and the arena lists, also for game servers nobody is on, and sends them to every game server (each keeps the last copy indata/network-groups.json, so it still knows them after a restart); joining a group, its NPCs and placeholders and the map vote across servers all use them. With several lobby servers the last edit wins and is copied to the other lobbies. /bw arena listshows the arenas of all game servers (server, group, state, players);/bw arena infoexplains how to set arenas up on a network. All other/bw arenasubcommands (create, setup, backup, …) are refused here: run them on the game server that has the arena./bw spectateopens a menu of the running games on all game servers;/bw spectate <arena>watches that game.- Join NPCs:
GROUP,ARENAandSELECTORsend players to game servers (the oldNETWORKaction was removed; NPCs that still have it work asGROUP). Holograms and the%newbedwars_group_<name>_...%placeholders show the network's numbers. - Only the party admin can join; the whole party is moved.
Proxy config (plugins/newbedwars-proxy/config.yml)¶
game-servers: [game1, game2] # names from velocity.toml
lobby-servers: [lobby]
ticket-timeout-seconds: 10
state-stale-seconds: 15
party-invite-seconds: 60
mysql:
enabled: false
host: "localhost"
port: 3306
database: "newbedwars"
user: "root"
password: ""
ssl-mode: PREFERRED # DISABLED, PREFERRED, REQUIRED, VERIFY_CA or VERIFY_IDENTITY
allow-public-key-retrieval: false
poll-seconds: 5
- The proxy picks the fullest arena that still has room (the same rule as
/bw joinon one server). If the game server refuses (the arena filled up in the meantime), the proxy tries one other server. If that fails too, the players go back to the lobby. - Game servers can only report their arenas while a player is online on them. A game server the proxy has not heard from recently is still tried, and it then picks an arena itself. With MySQL enabled on the game servers and on the proxy, the proxy always knows every server's arenas.
- If
game-serversis not empty, the proxy only accepts arena states (plugin messages and MySQL rows) from those servers; anything else is ignored and logged once. With an empty list the proxy learns game servers from what they report (at most 128). A server that has been silent for ten timesstate-stale-secondsis forgotten until it reports again. - MySQL rows carry the game server's own clock, so the proxy never compares it with its clock: a server counts as alive when its row's heartbeat changes between two polls.
- Incoming data is size-limited (64 arenas per server, names up to 64 characters, 256 rejoin places per server, 128 servers). When the network state for the lobbies would not fit one plugin message, rejoin data is left out first, then the least useful arenas (running and empty ones) are cut, and the proxy logs it once.
- A player who just sent a join request cannot start another one for about 2 seconds (lobby servers also wait 1 second between requests). Join tickets carry a relative lifetime, so differing clocks between proxy and game servers do not matter.
/nbwproxy(permissionnewbedwars.proxy.admin) lists the game servers and arenas the proxy knows.- Proxy texts are in
plugins/newbedwars-proxy/lang/en.ymlandpl.ymland are chosen by the player's client language.
Stats and player data¶
With Storage.Type: MYSQL on every server (same database), stats, leaderboards (/bw leaderboard, placeholders), languages and quick-buy layouts are shared by the whole network. A game's result is added to the stats on the database, so games ending on several servers at once never overwrite each other. A player's data is read when they join a server; leaderboards and online players' stats are refreshed every minute. On the first start with an empty database, that server's JSON data is imported once.
Rejoining¶
When a player leaves a running game while their team is still playing (disconnect or /bw lobby), the game server keeps their place for RejoinTime minutes and tells the network about it. On a lobby server the player gets a title, a sound, a clickable "Click to rejoin" button and an action bar reminder with the time left. /bw rejoin (or the button) sends them back to that game server and arena. A player who was the last of their team has no place to go back to (their team is out).
Parties¶
In network mode, /party (alias /p) is handled by the proxy, so parties survive server switches. The commands are the same as on a single server.
Security¶
- Firewall your backend servers (lobby and game) from the internet and only let the proxy reach them. With Velocity modern forwarding the forwarding secret is the only thing that stops someone from connecting to a backend directly and claiming any identity. Keep
forwarding.secretprivate and never expose backend ports. - The proxy never forwards the
newbedwars:mainplugin channel from players to servers, so clients cannot forge join tickets or party data. Messages from a backend are checked against the sending player's connection, the sender's role (only lobbies define groups) and the size limits above. - MySQL:
ssl-modedefaults toPREFERRED(encrypt when the server supports it, no certificate check). For a database on another machine useREQUIRED, orVERIFY_CA/VERIFY_IDENTITYwith a trusted certificate, and a dedicated database user that only has access to the NewBedwars database. Only game servers and the proxy need thenbw_serverstable; treat the credentials inconfig.ymlas secrets. - Hardening added in 2.6-beta: a join request is only accepted for the player who sent it (target at most 64 characters); a game server can only move players that are on it; join tickets expire and a lobby allows one join request per player per second; the proxy drops oversized or malformed messages and reserves arena slots only until the real state arrives; when
game-serversis set in the proxy config, states from other servers are ignored (and logged once); the proxy only reads the first 256nbw_serversrows. The proxy config and item/GUI YAML are loaded with a safe loader (no!!javatags), and/bw arena importlimits unpacked size to 2 GB. - MySQL:
MySQL.AllowPublicKeyRetrieval(proxy:allow-public-key-retrieval) defaults tofalse. If the connection fails after updating with acaching_sha2_passworduser and no SSL, set it totrueor usessl-mode: REQUIRED.
Limits¶
- BungeeCord is not supported yet (Velocity only).