Overview

##What is a Stopwatch?

A stopwatch in Aevum is a count-up clock. It starts at zero, ticks up once per second, and runs until you pause, reset or delete it — there's no target and no end. Think speedrun timers, "time survived" counters, session trackers, or anything you want to keep climbing.

/aevum stopwatch create <name> [scope] [target]

Example: /aevum stopwatch create run creates a global stopwatch named run. Note there's no time argument — a stopwatch has no duration.

---

##Lifecycle

1. Create — create <name> registers the stopwatch (it begins at zero).
2. Run — it ticks up every second (firing StopwatchTickEvent); pause, resume, or adjust it with add / remove / set whenever you like.
3. Reset — reset sends it back to zero without deleting it. There is no end — a stopwatch keeps counting until you stop it.

Check the current value and state any time with status (running, paused or stopped).

---

##What's stopwatch-specific

• It counts up, forever. No target, no TimerEndEvent equivalent — use pause/reset/delete to stop it.
• reset — a stopwatch-only verb that zeroes the elapsed time but keeps the instance.
• set sets the elapsed time — e.g. set run 30s makes it read 00:30.
• Action context — stopwatches fire a tick event every second, so actions receive %event% = tick. Always gate stopwatch actions with %divisible_by_<n>% (or another condition) so they don't run every second. See config.yml.

---

##Marks (checkpoints)

A mark records the elapsed time at the moment you mark it — perfect for laps and splits.

/aevum stopwatch mark <name> <label>
/aevum stopwatch marks <name>
/aevum stopwatch unmark <name> <label|*>

Marks are readable via Stopwatch Placeholders and the API.

---

##Next steps

• Stopwatch Commands — the full command reference.
• Stopwatch Placeholders — show stopwatches on scoreboards, tab and chat.
• Getting Started — scopes, targets, time format and marks explained.
• config.yml — fire rewards and messages on a tick.