Can I create custom timers in DotaSense?

Yes. The Windows app supports recurring game-clock events and manually triggered cooldown events, with names, icons, pre-alerts, sounds, and optional hotkeys.

What is the difference between a timer event and a manual cooldown?

A timer event repeats from the match clock using an interval and offset. A manual cooldown starts when you click or press its configured hotkey.

Can a custom timer detect that an enemy cast a spell?

No. A manual cooldown begins only when you trigger it. The app does not promise automatic detection of an enemy cast from a custom event.

Does the DotaSense browser timer support custom events?

The current browser timer provides a reviewed fixed cue list and manual Roshan or Aegis controls. The custom-event builder described here is a Windows desktop feature.

All guides

Recurring events · Manual cooldowns

Create a custom Dota 2 timer

Add one match-clock reminder or one manually triggered cooldown, test whether it changes your next action, and keep the alert set small enough to remain useful during a real match.

Reviewed August 29, 2026 against the current DotaSense Windows custom-event builder. The browser timer uses a fixed reviewed cue list and does not expose this builder.

RecurringInterval + offset

Use the match clock for events that repeat on a predictable schedule.

ManualClick or hotkey

Start a fixed or variable cooldown when the event actually happens.

RuleOne alert, one job

If the cue does not change a decision, remove it instead of making it louder.

Choose the clock first

Two custom timer types

Automatic schedule

Recurring timer event

Repeats from game time. Set an interval, an offset within that interval, a pre-notification, an optional start offset, and an optional stop time.

Observed event

Manual cooldown

Begins only when you trigger it. Use a click or non-conflicting hotkey for a spell, ward duration, buyback estimate, or another event you personally observed.

A custom event is not automatic detection.

The timer follows the schedule or trigger you provide. It cannot verify that a spell was cast, a ward was placed, or an objective actually spawned.

Match-clock events

Build a recurring event

Setting	Question it answers	Example
Interval	How often does the cue repeat?	Every 5 minutes
Offset	Where inside the interval does it occur?	At :53 of each minute
Pre-alert	How early do you need to prepare?	10 seconds before
Start offset	When should the schedule become active?	Begin after 5:00
Stop after	When does the cue stop being useful?	Stop after the laning phase

Use the smallest lead time that still lets you act. A warning that arrives too early becomes background noise; one that arrives after the route decision is already locked cannot help.

Observed cooldowns

Build a manual cooldown

Name the event

Use a label you can recognize at a glance, such as Black Hole or enemy buyback.

Set the window

Choose one duration or a minimum and maximum when the return time is uncertain.

Choose a trigger

Use the card or a hotkey that does not collide with Dota, Steam, Discord, or another overlay.

Add one cue

Select a readable icon and a sound that is distinct without overpowering game audio.

Trigger on evidence

Start it only when you actually see the cast, placement, death, or objective event.

Treat expiry as a check

A returned cooldown means re-evaluate the fight. It does not mean the enemy will cast immediately.

For enemy spell windows, use the more focused enemy cooldown tracker guide.

Start with a repeated mistake

Useful custom event examples

Periodic spawn

A patch-specific map cue

Add a recurring event only after verifying the current timing and mode. Retire it when the patch changes.

Spell cooldown

One long enemy ultimate

Trigger it when the cast is confirmed. Use a range if cooldown reduction or level information is incomplete.

Ward duration

A ward you personally observed

Start the timer at placement and remember that early dewarding can make the countdown irrelevant.

Personal routine

A decision check, not a game fact

Use a quiet periodic prompt for a minimap, buyback, smoke, or inventory check when the habit is the real target.

More is not better

Avoid alert overload

Add one custom event at a time. Play several games before adding another.
Use distinct cues. If two sounds mean different actions, they should not be easy to confuse.
Stop obsolete events. Use a stop time or disable the card when the cue no longer changes a decision.
Review false urgency. An alert should prompt a map check, not force a move into a bad state.
Delete stale patch facts. Recheck timings after updates instead of preserving an old schedule because it is already configured.

Quick answers

Dota 2 custom timer FAQ

Can I use a hero icon for a custom cooldown?

Yes. The current builder includes Dota objective art and the local hero icon catalog, with search for faster selection.

Can I set a variable cooldown window?

Yes. Manual events can keep a minimum and maximum duration so the display represents uncertainty instead of a false exact time.

Can I upload a custom sound?

The Windows app supports per-event sound controls and custom audio. Test the file, output device, and volume before relying on it.

Do custom events survive a restart?

The app saves custom events and their settings locally. Resetting all timer settings removes them, so treat a full reset as destructive.