General Rotation Notes
The module does not assume you have chosen a "cookie cutter" talent build. No AddOn can function as a DPS maximiser for AoE fights, due to limitations in the programming API. Single target is assumed.

The default list of cool downs is merely a sample. Customise via the Cooldowns Panel, /wdw coo. You also go to here to list any rotation/queue exclusions.

Notes Specific to the Arcane Mage ModuleBURN commences when the Evo cooldown is below a threshold. The aim is to be down to 50% mana at exactly the time that Evo comes of CD.
Yup, impossible to predict so the module "learns" as it goes, starting at a low 15s. REPLENISH commences at 50% mana. Evo will be in queue position #1. Do it! CONSERVE occurs when Evo is on CD.

* Brilliance Buff *
Dalaran Brilliance / Arcane Brilliance will be suggested if your DB, AB, Legacy of the White Tiger or Dark Intent are about to expire or not present. Other raid buffs might be preferred. Just place your DB and AB in the "Exclude" list via the Cooldowns Panel, /wdw coo.

Modifiable Parameters New!
From the chat line, the following modifiable parameters can be adjusted by you. The values are saved between sessions.

/wdw amp burntimer=nn
'nn' is the time in seconds before Evocate comes off cooldown and is the ideal time to commence your burn phase. The default is 15 (seconds).

/wdw amp minmana=nn
'nn' is the ratio of current mana to maximum mana for which Evocate should be triggered. The default is 0.5 (i.e. 50%). Setting this too low will result in a never ending burn phase. Most players settle for 0.4 to 0.6.

/wdw amp train=x
Your Arcane Mage module can automatically learn the amount of time it takes for you to burn your mana down from 100% to 50%. Setting train=y will cause your 'burntimer' parameter to be adjusted automatically. A value of 'n' turns the training off.

New! The timer will be aggressively adjusted if your most recent burn phase ended too soon, and more so if this was before your Evocation was off CD. Conversely, the timer will be increasingly conservatively adjusted the more you exceeded the current time estimate.

/wdw amp
Shows the syntax. '/wdw amp list' will list all modifiable parameters and their current values.

How to Report Bugs & Suggest Improvements
Go to Tickets to report bugs. Line numbers from bug catching AddOns are useful. Lists of AddOns are of no use. The forum on this page is for suggestions and discussion.

Fun Stuff™ New!
At any time you may raise your arms high and command Storm, Earth and Fire. You indeed have the power of Go'el in your hands! Heed My Call™ with '/wdw sef' or '/wdw poth' in chat. Or say hello to yourself with '/wdw sal'. Enjoy!

Cookies, Beer & Donations
It is all about the Cookies & Beer although, and don't let Gallywix know about this, a "thank you" in the comments section fuels my programming appetite and is very much appreciated. And then, you could cut straight to because as Gallywix would say... "time is money, friend".

Included in the Icy Veins Arcane Mage Guide!
Special thanks to Damien, curator of the Icy Veins Arcane Mage Guide, for including this module on the DPS Macros and Addons page.

v2.12
=====
* Module MUST use v4.11 of main module due to show stopping bug fix for Mages with Incanter's Flow

v2.07
=====
* Added Rune of Power
* Better feedback with the "bt" option for those inclined.
* INCREASES to the burn timer are throttled exponentially now: old + diff^0.5
* DECREASES to the burn timer still a factor of 1/2 but an additional 1/4 if missed the Evo CD (which will be true almost always)
* Now checks for minimum WDW version as a help to keep things up to date

v2.06
=====
* Change 'sm' references to 'amp'
* Added special 'low mana' queue items for use during the Conserve phase
* Remove the Evocate icon from position #1 when mana is nearly full
* Included the new low mana logic in the 'bt' flag debug output
* Update TOC file for Patch 6.1

v2.04
====
* Module confused between minMana parameter as a ratio or percentage.
(Thanks to wowinterface member Baine for noticing this)
* Retain duplicate AM tests BUT safeguard against FOUR AMs appearing in the queue
* Removed a small block of redundant code in the Evo routine (benign)

Arcane a really low priority at the moment, even though I enjoyed it almost as much as Fire in the previous xpac and the rotation nailed the mana management (trivialised it really hehehe). Mainly because it sucks in high end raiding and I think no-one will down load it, except you and I lol.

But really, it might happen. But I am toying with Arms warrior next up.

(End of this week I go on an 8 day holiday. See what happens when I get back refreshed.

Dalaran / Arcane Brilliance buff: More a quality of life thing. Raid buffs are a bit difficult for a raid leader to get everyone to agree on at times and v2.11 has better "more aware" raid buff logic, checking against Legacy of the White Tiger, Dark Intent, etc.

Requires WDW v4.10 as that in turn has improvements to showing Rune of Power expiries and so on.

Prismatic Crystal slides to the left based upon (1) how soon until it is up again and (2) how many Arcane Charges you have.

At position #2 that means it is the NEXT ability after position #1. So do whatever is in position #1 and then place your crystal. Placement can be tricky sometimes so to avoid interrupting your DPS, your crystal will often stay at #2, until you lay it down.

Prior to v2.09, it could get to position #2 even while still on a CD greater than is appropriate at that position.

Not just a quick 'toc' file update to force the AddOn to load in Patch 6.1 (lol)...

Evocate is now force removed from queue position #1 when your mana is almost full. Previously it waited for you to interrupt the channeling.

Some players were experiencing low mana during the conserve phase. With v2.06, the more desperate your mana situation, the more desperate (i.e. less than optimal) is the suggestion to Arcane Missiles / Barrage.

Yes AM and ABa are a DPS loss but so too is low mana. Better to get the player's mana back up during conserve (defined as Evocate on CD). Feel free to pot etc to override this. The AddOn will adjust itself.

'/wdw deb bt' enables some messages each time your burn timer has been 'trained'. It now will also add a message if the low mana logic caused an ABa or AM to be queued. '/wdw deb 0' to turn all this off.

Some of you might have noticed that the Arcane Mage module might suggest FOUR Arcane Missiles. Sure it is brief and not exactly often but it *can* happen.

This is due to the priority logic being satisfied for multiple AM tests and my only tracking AMs for two of those tests.

----------

For several hours a post here suggested I would throttle the "training" of the burn timer. Removed / recanted. I am satisfied that the module already has a built in safeguard against incomplete rotations adversely affecting the burn timer training.

----------

The Minimum Mana % parameter, which a player may select, has a default of 50%. In the module I use a value of 0.5 (of maximum mana). Somewhere I got the ratio and percentage mixed up. Doh!

See discussion with Baine, below.

----------

Many thanks to Baine for noticing the "never ending burn" problem. His scenario sounded convoluted but it was a very real and quite serious bug which would occur under normal game play.

but it's just not acting as it should
when i log in (with no saved variables at all for WeDontWipe), enter /wdw deb bt
it works as it should
once i do a /reload, the file gets written, the value for the burntimer is as expected and given by that debug print

but after that reload, the burn phase just never ends...
when i delete the contents of that file (effectively removing the WeDontWipeDB), make it read only, the addon works as expected (well, doesn't save settings, but that's not an issue right now)
when i do a reload using that modification, it works every time. suggesting evo as it should etc

when i make that file writable again (hence enabling WeDontWipeDB) and do a reload, it works once
but every login or reload after that, burn phase never ends...
(at least that's how it behaves on my end...)

Investigating. Quite a convoluted situation BUT I did manage to replicate the problem. Altering the saved variables file from R/W to R had no effect (for me - maybe because I use OS X on an iMac) but it was when I DELETED the file that, after a couple of "/reload ui", the BURN phase was never ending.

Edit: Got it. LOL. I outsmarted myself. So that I could display a percentage as a % number but also use the same value as a ratio, I internally multiply or divide by 100 and.... yeah. Fix on its way. Sigh.

but it's just not acting as it should
when i log in (with no saved variables at all for WeDontWipe), enter /wdw deb bt
it works as it should
once i do a /reload, the file gets written, the value for the burntimer is as expected and given by that debug print

but after that reload, the burn phase just never ends...
when i delete the contents of that file (effectively removing the WeDontWipeDB), make it read only, the addon works as expected (well, doesn't save settings, but that's not an issue right now)
when i do a reload using that modification, it works every time. suggesting evo as it should etc

when i make that file writable again (hence enabling WeDontWipeDB) and do a reload, it works once
but every login or reload after that, burn phase never ends...
(at least that's how it behaves on my end...)

i've deleted my savedvariables for WeDontWipe before doing anything this time
set /wdw deb bt
(i had that before as well, but only received multiple messages that this mode had been set, infight and out of combat as well)
started on the dummy in the garrison
suggested evo this time as expected, got that message that the timer was adjusted
looks like it's working (for now^^)

Support AddOn Development!

You have just downloaded by the author . If you like this AddOn why not consider supporting the author? This author has set up a donation account. Donations ensure that authors can continue to develop useful tools for everyone.