27 lines
1.4 KiB
Markdown
27 lines
1.4 KiB
Markdown
---
|
|
type: User Story
|
|
title: "US-001: Start, pause, and administer the game"
|
|
description: Give server operators safe control over the Tyrant game's lifecycle and state.
|
|
status: done
|
|
---
|
|
|
|
# US-001: Start, pause, and administer the game
|
|
|
|
As a **server operator**, I want to start, pause, resume, and inspect the game so that it can coexist safely with maintenance and other server events.
|
|
|
|
## Acceptance criteria
|
|
|
|
- [x] An administrator can start the first game by assigning the initial Tyrant.
|
|
- [x] The administrator may assign the first Vigilante or allow random selection from eligible recently active players.
|
|
- [x] An administrator can pause and resume the game without deleting game state.
|
|
- [x] Pausing freezes progression, cooldowns, daily-use timers, inactivity checks, and pending-selection deadlines.
|
|
- [x] Role and class effects are suppressed while paused and restored when play resumes.
|
|
- [x] Administrative commands require the `spigottyrant.admin` permission, granted to server operators by default.
|
|
- [x] Administrators can inspect lifecycle state, roles, classes, Followers, purchases, levels, cooldowns, participation, and pending selections.
|
|
- [x] Destructive administrative operations require explicit confirmation.
|
|
|
|
## Related
|
|
|
|
- [Tyrant game state machine](../concepts/game-state-machine.md)
|
|
- [Configure and persist game state](us-012-configure-and-persist-state.md)
|