Watcher helps you manage your rotation by consolidating and condensing information onto a simple to read display. It allows you to focus on things that are more important like boss mechanics, your situational awareness, or listening to your raid leader; instead of being bogged down in the act of performing your rotation.
With deep and powerful configuration options, Watcher allows you to see exactly the information about your rotation that you want to see. Properly configured and customized, Watcher is a mighty tool for both new players just learning their classes as well as players that have been raiding since classic.
A GIF of Watcher running on a 2H Frost Death Knight:
Watcher also includes:
- A dynamic event-driven architecture; unlike some other rotation helping addons, Watcher won't tank your framerate
- Masque support for skinning icons
- A large number of visibility options to control exactly when Watcher shows up
- And more!
Through the use of a priority system as well as powerful filters for spells and abilities, Watcher displays your rotation in the familiar context of a timeline, with higher priority spells stacked on top of lower priority ones and upcoming abilities placed on the timeline according to when they will become useful. Abilities on the timeline are waiting for a wide variety of things: coming off of cooldown, waiting for resources, monitoring a DoT, etc.
A slightly old full walkthrough of Watcher configuration is located here
Spells can be configured to be cast based on a wide variety of filters whether that be the presence (or lack there of) of an aura on you or your target, your target's health percent, your mana/resource percent, whether a spell can be stolen or interrupted, whether you have a particular talent or glyph, among other options.
Found a bug or issue, or have a suggestion?
Please make bug or issue reports and suggestions on the project's official issue tracker.
Before you file a bug, please ensure you are running the latest Watcher version, 3.0.12.
The full, detailed changelog can be found here.