Modern BedWars
A production-grade, network-scale BedWars core — built for networks that outgrow a single server
Proxy · Lobby · Game Server · Matchmaking Service — four modules, one network, zero recompiling to reconfigure.
A production-grade, network-scale BedWars core — built for networks that outgrow a single server
Proxy · Lobby · Game Server · Matchmaking Service — four modules, one network, zero recompiling to reconfigure.
Why Modern BedWars is different
Most BedWars plugins are built to run on one server. Modern BedWars is built to run a network. It ships as four independently deployable modules that talk to each other exclusively over Redis, no single point of failure tying your lobbies to your game servers. A dedicated standalone matchmaking service is the "brain" of the network: it owns the queues, allocates matches to game servers, and keeps everything in sync across as many machines as you can throw at it.
Add as many lobby servers and as many game servers as you want. The service load-balances between them automatically. Everything is backed by MariaDB for persistent stats/cosmetics/leaderboards and Redis for real-time cross-server state — the same stack proven networks run on.
- Horizontally scalable — add game servers under load without touching config on the rest of the network
- Fully config-driven — GUIs, prices, timings, physics constants, cosmetics and text are all YAML, not compiled Java
- Multi-language out of the box — per-player locale detection with automatic fallback, drop in new language files with zero code changes
- Admin console included — a live shell on the matchmaking service for queue/server/match inspection and map reloads
Network Architecture
| Module | Runs on | Role |
| Proxy (bedwars-proxy) | Velocity | Routing, party system, spectate, admin multiplier command |
| Lobby (bedwars-lobby) | Paper | Queueing, leaderboards, profiles, cosmetics, private games |
| Instance (bedwars) | Paper | Full match lifecycle — shop, generators, upgrades, traps, beds |
| Service | Standalone | Matchmaking brain — queue processing, server allocation, map sync |
All four talk over Redis only. MariaDB stores everything that needs to survive a restart: stats, cosmetics, disguises, leaderboards.
Gameplay — Game Server
- Solo / Duo / Trio / Squad game modes, each with independently tunable shop prices, upgrade prices and generator schedules
- Teams & beds — colored teams, shared team shop, bed-break elimination with final-kill credit, configurable post-respawn invulnerability
- Full shop system — categorized GUI (blocks/swords/armor/tools/bows/potions/specials), per-mode pricing tiers, armor-hierarchy downgrade guard, hotbar quick-buy, reset confirmation
- Generators — Iron / Gold / Diamond / Emerald plus team-upgraded Emerald Forge, with spawn delay/cap/batch fully configurable per mode and per upgrade level
- Team upgrades — single-purchase (Sharpened Swords, Reinforced Armor, Heal Pool, Beacon) and multi-tier (Armor I–IV, Haste Pickaxe I–II, Forge), all priced per game mode
- Traps — configurable catalogue (Tripwire, Feather Falling, Alarm, Mining Fatigue and more), each with its own effect/duration/target, plus a tunable "magic milk" immunity cooldown
- Cosmetics engine — arrow trails, fireball trails, victory dances, final-kill effects, kill messages, bed-break effects/messages, wood skins; unlockable/purchasable with in-game currency, persisted in MariaDB, with a paginated selector GUI and a master on/off + global intensity multiplier for server performance tuning
- Disguise system — cross-server disguise state that follows the player between lobby and game
- Configurable scoreboard — per-phase sidebar layout with a tunable refresh rate to trade live-ness for tick performance
- Fully tunable physics — egg-bridge distance limits, fireball velocity/knockback/damage, sponge absorption, on-screen title timings — all in config, none hardcoded
Lobby Features
- Queueing — join a mode queue, the matchmaking service handles allocation and sends you straight to your match
- Private games — host a custom match and invite friends with a join code
- Rejoin — reconnect to an in-progress match after a disconnect, tracked via Redis with a TTL
- Spectate — watch any live match from the lobby
- Profiles & stats — win/loss/kill/final-kill records pulled straight from MariaDB
- Leaderboards — cached, periodically refreshed, with a seasonal reset job
- Configurable GUI layout — slot positions, pagination size, and every user-facing string are de-hardcoded — reskin the lobby without a rebuild
- PlaceholderAPI support — expose rank/coins/level/stats placeholders to your other plugins
Proxy Features
- Automatic lobby/game routing by configurable server-name prefixes
- Full party system — /party chat, invite, join, kick, leader, leave, list
- Cross-server XP/coin multiplier admin command for events and promotions
- Cross-server /spectate entry point
Matchmaking Service — the network's brain
A standalone process (no Minecraft server needed) that keeps the whole network coordinated:
- Per-mode queue processing on a tunable interval, with player-stealing between under-filled queues and configurable timeouts
- Server rancher — tracks every live game server, recomputes load on an interval, and enforces a max-matches-per-server cap so no instance gets overloaded
- Play-again cooldown with a cache to stop queue-hammering abuse
- Map distribution — pushes the map list to every game server over Redis
- Live admin shell — status queues, list matches, list servers, maps reload, log, stop — plus an Actuator health endpoint
Party System
Two layers, selected automatically — no manual switching required:
- Built-in — Redis-backed party model shared across the whole network, with full GUI support on the lobby
- External plugin integration — if Party and Friends or Parties (AlessioDP) is already installed on your Bukkit servers, Modern BedWars detects it automatically at startup and defers to it as the source of truth. The built-in /party command is suppressed automatically so there's never a conflict, while queueing and party-follow-on-server-switch keep working transparently.
Already running a party plugin your community loves? Keep it. Don't have one? The built-in system just works.
Total Configuration Surface
Nothing gameplay-affecting is compiled into the jar. Every one of these ships as an editable file:
- game.yml — match timers/sizes, combat rules, egg-bridge, fireball physics, sponge absorption, magic-milk cooldown, trap-alarm timing, cosmetic tuning
- shop.yml — shop GUI layout + item prices per game mode
- upgrades.yml — team upgrade tiers, prices, GUI layout
- traps.yml — trap catalogue, effects, targets, GUI layout
- generators.yml — spawn rate/cap/amount per resource, mode and level
- cosmetics.yml / cosmetic.yml — cosmetic catalogue + GUI/pagination
- scoreboard.yml — sidebar layout + refresh rate
- hotbar.yml / items.yml / events.yml — hotbar layout, special items, event timeline
- Lobby GUI layout, service queue/rancher intervals, and Redis TTLs are all configurable too
Full per-file breakdown and a step-by-step install guide (Redis, MariaDB, all four modules, permissions, upgrading) is included with the resource.
Multi-language Support
Every player-facing message, GUI, title and actionbar is translatable. Messages resolve per-player by their Minecraft client locale, with automatic fallback to English for anything missing. Adding a new language is copy-a-file-and-translate — no code, no recompiling, no restart-required patching.
Requirements
| Java | 25 |
| Paper | 1.8-1.21 (lobby + game servers) |
| Velocity | 3.x latest (proxy) |
| Redis | 6.0+ |
| MariaDB / MySQL | MariaDB 10.6+ |
| SlimeWorldManager | Required on every game server |
| LuckPerms | Required on every server |
| PlaceholderAPI | Optional, lobby-side placeholders |
A single-machine dev/evaluation setup (everything running locally) is fully documented and takes about 20 minutes.
Support
Setup guidance, configuration help and bug reports are handled through:
Modern BedWars — the BedWars core your network won't outgrow.
