Overview

##What is a Timer?

A timer in Aevum is a countdown. You give it a duration; it ticks down once per second and, when it reaches zero, it ends — firing a TimerEndEvent and any matching actions. Think round timers, event countdowns, grace periods, cooldowns shown on a scoreboard.

/aevum timer create <name> <time> [scope] [target]

Example: /aevum timer create event 5m creates a global 5-minute countdown named event.

##Lifecycle

1. Create — create <name> <time> registers the timer and starts it counting down.
2. Run — it ticks every second (firing TimerTickEvent); you can pause, resume, or adjust it with add / remove / set at any time.
3. End — at zero it stops and fires TimerEndEvent. This is where end actions run — e.g. broadcast a message, give a reward, run a command.

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

##What's timer-specific

• It ends. Unlike a stopwatch, a timer has a target of zero and an end event/action. Stopwatches count up forever and have no end.
• set sets the remaining time — e.g. set event 2m makes it 2 minutes from now.
• Action context — when a timer ends, actions receive %event% = end, plus %id%, %name%, %time%, %seconds%. See config.yml.

##Marks (checkpoints)

A mark records the remaining time at the moment you mark it — useful for "halfway" splits or stage boundaries.

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

Marks are readable via Timer Placeholders and the API.

##Next steps

• Timer Commands — the full command reference.
• Timer Placeholders — show timers on scoreboards, tab and chat.
• Getting Started — scopes, targets, time format and marks explained.
• config.yml — fire rewards and messages when a timer ends.