Spent some time today on target dummy with the strategy of forcing myself to treat Phylactery / DFO procs as well as Eclipse cycles as so much background noise. In other words I did not clip dots based on trinket procs, I did not delay Starfall or Hyperspeed Gloves or Force of Nature for procs or for specific Eclipse cycles. I pretty much popped things as they came back up whenever they came back up and refreshed dots only when they needed refreshing. The one exception to this is there is pretty much either an enforced DoT clip after an Eclipse to get the haste from Nature's Torment OR an enforced DoT drop if you let it drop a few seconds before the Eclipse in anticipation of refreshing it then to proc Nature's Torment.
In this fashion, I was moving between Eclipse cycles faster -- sometimes I got lucky on dots getting refreshed during "good" trinket procs, sometimes I didn't. Nukes benefitted from the procs either way. I probably have more Nature's Torment uptime as a result of wasting less GCDs clipping and micro-managing dots (I'll have to review log for that). Long and short, using this strategy over a prolonged dummy rotation (~28 minutes and ~20 million damage) put me right at the same 12k sustained I got from micro-managing and clipping dots based on procs.
So . . . with all of that said, if I could get feedback to the devs, my statement would be that we change the description and function of 3/3 Nature's Torment to read:
"You gain 15% spell haste after you gain Solar or Lunar Eclipse, lasting 15 sec."
That's it. No cooldown -- however fast you can get to the opposite Eclipse is how fast you can get the Nature's Torment proc again. Just as it is now. Still meets what I think the design goal is (to encourage us to move between Eclipses -- actually meets it even better as you couldn't just wait 1 minute in the same Eclipse -- you have to go proc the other to get it again). The only difference is the proc of the Eclipse grants the effect rather than a mandatory DoT cast thereafter which may or may not make sense at the time.
This way we can let the dots that are currently up persist. The won't get the immediate bonus of the Eclipse but, as long as we naturally refresh them at their end sometime within the Eclipse (very likely they will expire in that ~15 seconds), that dot will carry the buff even after the Eclipse drops, so on and so forth, repeating the same refresh strategy through each Eclipse cycle ad infinitum.
Acting in this way and with Nature's Torment revised, I could pretty much remove most of the clipping concerns I have at the moment. Without dot clipping / dropping caused by our reaction to Nature's Torment, haste would allow dots to scale as intended. The remaining issues will be how we manage to be in the right Eclipse for things like AoE but, at least for the stand-still, single-target rotation, I have fewer issues.
The other revision would be to change Lunar Shower to tone that down a bit -- something to the effect of 10/20/30% -- number crunchers could figure out what would be reasonable and, overall, it's fairly workable as a talent tree.
Extended log from today at:
World of Logs - Real Time Raid Analysis
for those interested.