Fix solo-play win condition, floor-spawn clipping, and make round-end block removal instantaneous
Build / build (push) Successful in 1m17s

This commit is contained in:
Michael Burgess
2026-08-07 08:09:45 -04:00
parent c78d35d104
commit 07d210d8db
3 changed files with 57 additions and 31 deletions
+7 -1
View File
@@ -134,12 +134,18 @@ disabled, deleted, or the plugin shuts down, so it never leaks entities.
off entirely. Eliminated players become spectators at the configured spectator location.
- Last player standing wins; rewards, stats and celebration effects (fireworks, titles,
sounds) fire automatically.
- **Solo play**: if a match starts with only one player (e.g. `min-players: 1` for testing),
"one player remaining" is the expected steady state, not a win — the match keeps running
rounds, each shorter than the last, until that player is actually eliminated or leaves.
With two or more players, the match ends the moment only one remains.
## Configuration overview
- **`config.yml`** — global settings: `ui.*` toggles for scoreboard/bossbar/titles/actionbar,
`sounds.*` (Bukkit `Sound` enum names; invalid names are logged and skipped, never crash
the plugin), `performance.floor-blocks-per-tick` (batch size for floor mutations),
the plugin), `performance.floor-blocks-per-tick` (batch size for floor *generation* and
*restoration*, spread across ticks — the round-end removal of non-target blocks is always
instantaneous, all at once, by design),
`defaults.*` (used only when `/bp create` seeds a new arena), `default-floor-materials`
(the full 16-color concrete palette by default), `rewards.winner.commands`, and
`integrations.placeholderapi`.