🩺Troubleshooting

Most first-run issues are a missing password or a Redis/MariaDB reachability problem. Work through the table before opening a support ticket.

Symptom	Likely cause
list servers in the service shell stays empty	A game server isn't registering — check its server-id matches the proxy's gamePrefix (config.json) and that it points at the same Redis as the service.
Players stuck in queue	No instance is reporting heartbeats; or max-match-per-server is 0; or every instance is already at capacity.
Lobby/game plugin fails to enable with a DB error	config.yml password is empty — set it.
GUIs render raw keys like master.profile.title	The key is missing from the active language file. Copy it from messages_en_US.properties.
Tick lag on game servers under load	Raise the sidebar refresh interval in defaults/scoreboard.yml (refresh the scoreboard less often).
A node stops receiving messages	Different Redis instance, wrong Redis password, different database: index, or a network policy blocking port 6379.

Log locations

• Service: ./logs/bedwars-service.log (rotated daily, capped at 1 GB).

• Bukkit plugins: standard Paper console + logs/latest.log.

Connectivity checks

Test Redis from a node:

redis-cli -h <redis-host> -p 6379 -a <password> ping

Test MariaDB from a node:

mysql -h <mariadb-host> -u bedwars -p bedwars -e "SELECT 1;"

Start / stop order

• Start: service → proxy → lobby → game (brain up first so registrations succeed).

• Stop: game → lobby → proxy → service (brain down last so in-flight messages have somewhere to go).

Upgrading a jar

1. Stop the affected node.

2. Replace the Bedwars-<module>-1.0.jar with the new build.

3. Keep your existing config.yml / application.properties / mariadb.json / redis.json / config.json and any edited defaults/*.yml.

4. Skim shipped defaults vs your copy for new keys and copy them in (the plugins don't auto-merge missing keys).

5. Start the node.