config.yml

config.yml is the plugin's central file: it controls the server type, the database, the lobby, game rules and performance tuning. It ships with ready defaults that are production-tuned — most owners never need to touch the performance section at all.

#Server type

The server type selects how this instance participates in your network. Each topology is a config value, not a different download — you buy once and can migrate between setups as your network grows.

# plugins/BedWars/config.yml
# The shipped file contains the complete, commented configuration.
server:
  type: multi-arena        # multi-arena | bungee | auto-scale | shared

#Database

BedWars runs MongoDB and SQLite behind one unified interface — switching between them is a single config change, and all data is migrated automatically on the next restart. Connection pooling, write-ahead logging and busy-timeouts are pre-configured for maximum performance on both engines. Optional Redis support shares player levels and preferences across a BungeeCord network with automatic cache invalidation. Full details: Database & Storage.

database:
  engine: mongodb          # mongodb | sqlite

#Game rules

Scheduled match events are configurable through simple files with no hidden hard-coded behavior:

• Diamond and emerald generator tier-ups
• The bed destruction countdown
• The ender dragon sudden-death phase

Team-shared upgrades — sharpness, protection, haste, heal pool, base traps, dragon buffs and more — are part of the same configurable game rules. Players can preview the upgrades menu in-game with /bw upgradesmenu.

#Performance tuning

Every background batch size — from scoreboard refresh to hologram spawning — is exposed as a simple config value, so you can fine-tune the plugin for any hardware. The defaults are production-tuned already. Scoreboards, holograms and health indicators refresh only when their data actually changes, so idle players cost nothing. If the database slows down or drops a write under extreme load, the plugin protects the game first and logs the work for retry — your TPS is never the sacrifice.

#Startup protection

At startup, connections are politely held until every arena has finished loading, with a built-in failsafe so a single broken map can never lock your lobby forever. Players never fall into a half-loaded world — and never even notice the process.