Fun w/ SimulationCraft: Eclipse and DoTs

I'm starting a new series I am calling "Fun with SimulationCraft." I have two goals for this series. The first is to answer some of the more common rotation and proc questions that are difficult to answer with simple math. The second goal is to make myself and hopefully you guys more familure with SimulationCraft. The better we understand the tool the better we understand the results and our DPS.

The Question: Eclipse - Nukes vs DoTs

As we all know Eclipse is a major part of Moonkin DPS. It is also very unpredictable, and impossible to fit into a nice rotation where all the buff's, cooldowns, and dot timers line up. It is inevitable that you will face a situation where your Eclipse has just procced, but your DoTs have only 5 seconds left on them.

What do you do in this situation? Do you spend a GCD and pressious Eclipse time on a spell that is unaffected by the buff, or do you continue to nuke and let your DoTs fall off?

It's a tough question, that I have changed my mind on a couple of times.

My Theory:

I've thought about this issue many times. A while ago I decided that the best course of action was to refresh DoTs if Eclipse had more then 4 or 5 seconds left on it, but skip the DoTs otherwise. My reasoning is fairly simple. When you ask a couple of questions.

What do you lose by casting a DoT when the Eclipse buff is up? - You lose a GCD that could have been used to cast a Nuke buffed by Eclipse.

What do you gain by casting a DoT when the Eclipse buff is up? - You gain the damage that the DoT will tick for until the end of the Eclipse buff.

When I asked myself these two questions I realized something. I'm not asking if I should cast a DoT. I'm asking when I should cast a DoT. The choice is do I cast it during Eclipse or right after Eclipse expires. I can extend this logic a littler further also. If I make this choice regarding the DoT, I'm making a similar choice about the Nuke. If I cast the DoT during Eclipse, I will be casting a Nuke right after Eclipse expires. If I skip the DoT during Eclipse, then I'm losing a Nuke after Eclipse expires because I need to refresh the DoT.



What I realized was that when I cast a DoT, I am not preventing a Nuke from being cast. However, I may be preventing a Nuke from being buffed by Eclipse. So, the question is which is more valuable: damage from increased DoT uptime or the addtional damage from an Eclipsed Nuke?

I won't detail the math but i will use a quick example to show you how I made my choice. On average my Wrath casts hit for 6377 damage without Eclipse. With Eclipse they hit for 9030 damage on average. There for I lose 2653 damage if a wrath cast is pushed out of the Eclipse buff by a DoT. My Insect Swarm ticks for 1280 damage on average. It would take roughly two ticks of IS to make up for the lost Eclipse damage. Since IS ticks every 2 seconds, if I had more then 2 seconds left on Eclipse then casting the DoT made more sense.

Obviously this is an over simplification of the issue. This is why I haven't published anything in the past regarding this question. Now SimulationCraft hs here to make me look like a genius or an idiot.

What SimulationCraft Says:


Once again I used my self as an example and I asked multiple questions. Here is the results from the first set.

Condition	DPS
Never Skip	8267
Skip on Opposite	8175
Skip Always	8061

Never Skip means that I refresh the DoT when ever it is down. Even if Eclipse is up with only a few seconds left.
Skip on Opposite means you refresh the DoT only to take advantage of Improved Insect Swarm. Therefore, if Lunar Eclipse is up you would refresh Moonfire but not Insect Swarm.
Skip Always means you skip both DoTs if either Eclipse buff is up.

As you can see from the table above, the results are leaning towards refreshing your DoTs instead of skipping them, but we have another question to ask. As I said before I will skip the refresh if I have only a few seconds left on Eclipse. Is that the right choice?

Seconds Remaining	DPS
1 sec	8278
2 sec	8277
3 sec	8277
4 sec	8279
5 sec	8273
6 sec	8264
7 sec	8273
8 sec	8252
9 sec	8255
10 sec	8236
11 sec	8219
12 sec	8186
13 sec	8180
14 sec	8142
15 sec	8058

These results show that I can do slighly better DPS by skipping the DoTs whe I have 5 or few seconds left on Eclipse, but the DPS increase is very minor. Even if you start skipping your DoTs with 9 seconds left on Eclipse your only losing a tiny amount of DPS.

TL:DR

Well, the good news is I don't look like an idiot, but my method wasn't a huge success either. Skipping my DoTs with just a few seconds left on Eclipse did result in a slight DPS increase, but its not anything that will make or break our rotation.

The main conclusion I will draw from my tests is that the loss of DoT uptime is a bigger DPS loss then not having a nuke affected by Eclipse. If you skip your DoTs entirely while Eclipse is up it is roughly a 2.49% DPS loss.

Do It Yourself: If you would like to run this analysis for yourself. Here is how you do it.

Go download SimulationCraft from here.

SimulationCrafts GUI interface has gotten a lot better since I last posted on the tool. On the Import tab you can down load your toon from the Armory or WoWhead. Importing your profile will populate the Simulate tab with your script. The default setting is to always refresh DoTs.

To always skip DoTs replace the Moonfire and Insect Swarm lines with:

actions+=/moonfire,if=!ticking&!buff.lunar_eclipse.up&!buff.solar_eclipse.up
actions+=/insect_swarm,if=!ticking&!buff.lunar_eclipse.up&!buff.solar_eclipse.up

To skip DoTs when the Opposite buff is up change the lines to:

actions+=/moonfire,if=!ticking&!buff.solar_eclipse.up
actions+=/insect_swarm,if=!ticking&!buff.lunar_eclipse.up

To skip DoTs when when there is only 4 seconds left on either Eclipse change the lines to:

actions+=/moonfire,if=!ticking&(buff.lunar_eclipse.downbuff.lunar_eclipse.remains>4)&(buff.solar_eclipse.downbuff.solar_eclipse.remains>4)
actions+=/insect_swarm,if=!ticking&(buff.lunar_eclipse.downbuff.lunar_eclipse.remains>4)&(buff.solar_eclipse.downbuff.solar_eclipse.remains>4)

Finally, I would like to say thanks to Dedmonwakeen and Starfox the Creater and Druid developer of SimulationCraft for walking me though some of the changes that needed to be made.