Files
spigot-stealth/design/user-stories/us-004-administer-player-stealth.md
T

2.2 KiB

type, title, description, status
type title description status
User Story US-004: Inspect and manage player stealth Give administrators durable controls for online and offline progression, unlocks, and active concealment. backlog

US-004: Inspect and manage player stealth

As a server administrator, I want to inspect and correct player stealth state so that I can support players whether they are online or offline.

Acceptance criteria

  • /stealthadmin status <player|uuid> reports accumulated time, unlock status, prepared-login state, and current concealment state.
  • Status inspection works for online players and known offline players selected by exact current or previously recorded name or UUID.
  • /stealthadmin grant <player|uuid> grants the unlock to an online or known offline player without altering accumulated time unnecessarily.
  • Granting an already-owned unlock is safe and clearly reports that no change was needed.
  • Granting the unlock sends the normal full-screen title and chat notification when the target is online.
  • /stealthadmin reset <player|uuid> confirm clears accumulated time, unlock ownership, prepared-login state, and current concealment for an online or known offline player.
  • Reset requires explicit confirmation and safely restores an online concealed player to ordinary identity presentation.
  • /stealthadmin list lists every currently online concealed player and clearly reports when there are none.
  • Concealed players remain absent from administrators' ordinary tab lists and retain hidden overhead name tags; the admin command is the supported discovery mechanism.
  • Commands clearly reject unknown, ambiguous, malformed, or otherwise invalid targets without creating unintended player records.
  • Administrative inspection and modification require an operator-default administrative permission.
  • State-changing operations persist before success is reported and are safe under retries.
  • Grant and reset actions record the administrator, target UUID, and action in the server log without blocking the server tick thread.