AevumAevum

Commands

##Introduction

This page lists every timer command. They all live under /aevum timer …. A timer counts down to zero; time arguments accept 90, 90s, 5m, 1h30m, 2d (see time format).

INFO

Plus the plugin-wide /aevum help [page] and /aevum reload. Stopwatches have their own command page.

##Timer commands

Command Example Description
/aevum timer create <name> <time> [scope] [target] /aevum timer create event 5m Creates a timer. Scope is global (default), player or team.
/aevum timer add <name> <time> [target] /aevum timer add event 30s Adds time to a timer.
/aevum timer remove <name> <time> [target] /aevum timer remove event 30s Removes time from a timer.
/aevum timer set <name> <time> [target] /aevum timer set event 2m Sets a timer's remaining time.
/aevum timer status <name> [target] /aevum timer status event Shows a timer's time and state.
/aevum timer pause <name> [target] /aevum timer pause event Pauses a timer.
/aevum timer resume <name> [target] /aevum timer resume event Resumes a paused timer.
/aevum timer mark <name> <label> [target] /aevum timer mark event half Records a checkpoint at the current remaining time.
/aevum timer marks <name> [target] /aevum timer marks event Lists a timer's checkpoints.
/aevum timer unmark <name> <label/*> [target] /aevum timer unmark event half Removes a checkpoint. Use * to clear them all.
/aevum timer list /aevum timer list Lists all timers with their scope and instance count.
/aevum timer delete <name> [target] /aevum timer delete event Deletes a timer.

##Scopes & targets (recap)

The optional [scope] on create and [target] on every other command control who a timer belongs to and which owners a command affects.

Argument Values Meaning
[scope] global (default), player, team One shared timer, one per player, or one per Stella team.
[target] (empty) Yourself (player-run only). From console a target is required.
[target] <player> / <team> A single online player or a single team.
[target] @all Every owner under that name.

Full details in Getting Started → Scopes. For a global timer the target is ignored.


##Explanation

  • Creatingcreate registers a timer under a name and scope and starts the countdown. The scope is locked to that name afterwards.
  • Adjusting timeadd, remove and set change the remaining value live.
  • Controlpause, resume and status manage the run state.
  • Checkpointsmark, marks and unmark record and inspect named splits (the remaining time at each mark). They surface through Timer Placeholders and the API.
  • Listing & deletinglist shows every name with its scope and instance count; delete removes them.
  • Ending — when a timer reaches zero it fires its end event and any matching actions.