Soi would I, something I've been asking after since TBC...it also fits the Moonkin lore, it being a feral creature. But yes, that would help. So far for me though, threat issues have a reason based on who's tanking, but then I don't dishout enormous amounts of damage yet.

I'd like to get some preliminary feedback on a balance rotation helper I threw together. I have every intention of working this into the amazing clcInfo addon which I recently stumbled across while reading the ret forums here on EJ, but for the moment I am just working on getting all of the logic in order.

This is really my first foray into writing any sort of "addon," and it's not much of an addon at that, so if you have any advice feel free to share!

The addon really is very simple, like I said, and all it currently does is display two lines: the first line is what your next cast should be, and the second is what should follow that cast. So if you're testing, you ought to be pressing the button on the first line, and be ready to press the button on the second line next.

At the moment the logic is as follows:
These conditions are based on the following assumptions (which I think make sense, based on Hamlet's guide):

• If we are ever 1 cast from an eclipse, it is always most beneficial to proc the eclipse, cast one eclipse appropriate nuke, and then follow that with eclipse buffed instants or starsurge
• Dot refreshing with clipping (currently at 1 second, something I'd like to change dynamically based on the haste at which the current dot was cast, allowing exact 1 tick clipping) where moonfire tries to gain the NG buff unless we're in solar, in which case NG is better for IS
• Starsurge is next most important
• Nukes are the fallback

That said, there are certainly a few things that certainly could be improved upon, namely the dynamic clipping as I mentioned. It also seems that there should be some mechanic to keep dots from getting too spread apart (I feel like there must be something negative to this, not sure what though, so maybe not).

Anyway, please give me any feedback you may have - especially let me know if you notice finicky behavior (not following the rules) and try to give me a way to reproduce it.

NOTE: BalancePowerTracker is required for this addon to function, I didn't feel like re-writing the "virtual" eclipse stuff, but eventually I will make it standalone. For now, if you don't have BPT, go grab it along with balanceRotation and give it a whirl!

DOWNLOAD
balanceRotation: http://dl.dropbox.com/u/6413071/balanceRotation.zip
BalancePowerTracker: Balance Power Tracker : WoWInterface Downloads : Cataclysm Beta

Regarding the CLC balance addon:

There is a addon called Ovale which is what i am using to do as you are doing for the CLC. It has already Eclipse Energy logic that predicts the eclipse proccs.

The code below is the one i am currently using and is by my testing the best dps rotation.

Although this is back seat moderation and i will get a infraction for it, perhaps it is best to create a separate thread for this kind of discussions since it could clutter up this thread.

I would log your test on a 83 target dummy and upload it to a phrase site like worldoflogs or similar, also can you tell the stats for normal set (leather spec, 4x10) vs no leather spec and no 4x10?

While I am liking the new eclipse mechanic, I am still a little disappointed by euphorias inclusion of another flat RNG that we have no control over. Just wondering how bad it would be to have it based on starfire and wrath crits (and not a chance on crit either) rather than a flat 24%. And/or if starsurge also had the chance to give double energy.

This is how it was originally. I'm honestly not sure why they changed it as it provided another lever with which we could scale / adjust performance with gear.

In a nutshell, they wanted a little bit of random in all rotations. Honestly I don't see a problem with either implementation, but I think the current version allows for talent to always be useful; Rather than being subpar at the start of the expansion and really powerful by comparison at the end when crit levels are higher.

I think right now where people are easily sitting at 45-50% crit in a raid, it looks less attractive than it would if it still operated off of crit.

On the whole sunfire vs. moonfire discussion.....

I think it may have been intentional to make sunfire less powerful than moonfire in tick rate since insect swarm is also buffed by solar. This way they could make it so your dots were ticking for the same combined amount when you were eclipsed regardless of type of eclipse, and a lower combined rate when not eclipsed.

If I had to make a guess as to why sunfire is roughly the same as uneclipsed moonfire, and insect swarm was so much more powerful at first, it would probably be that the ratios they developed didn't have sufficient testing done with the IS and MF glyphs equipped.

Would have been fairly easy to test my theory (by simply removing the glyphs) if they hadn't already hot-fixed the dots.


...Oh well.


Also I was in a raid recently that we were unable to use 2 rebirths in one fight.
Other players in the raid stated that only one can be used per fight now.

Has anyone else seen something similar happen?
It would be nice to know if this was a bug, or by design.
By design would be a bit irritating, druids contribute much less in general to the raid with this new setup already.

It's been a bit random. There certainly are times we are unable to use 2 rebirths in one fight, but sometimes we can. Even more annoying, sometimes other druids can't rebirth for 30 minutes after one druid does it, even after dropping combat and entering a new one. It seems rather buggy and inconsistent at the moment.

By design. It was in the patch notes.

EDIT: Okay, not in patch notes. I knew it was coming before they released the patch so it must have been somewhere, PTR, beta, random Q and A. Not sure.

EDIT #2: This is just a rumor I guess.

I think this is the best priority list I've seen so far (although I guess it's technically addon code).




On the 4 second limit on DoT clipping

Let me preface by saying that when I use "clipping" I mean, refreshing a DoT 'ahead of time' before the last tick (ie. not "ideal" DoT refreshing).

Why wouldn't the clipping cut-off point be 37% of the duration/ticks of the dot (6.66 seconds)?

I think this is the justification for clipping at the end of eclipse.

Which is greater:
100% DPS for 36 seconds (2 non-eclipse IS's)
100% DPS for (18 - x) seconds and 137% DPS for 18 seconds

Where x is the number of seconds left on the DoT when I clip.

1.00 * 36 < 1.00 * (18 - x) + 1.37 * 18
x < 6.66

When x is less than 6.66, clipping the DoT is more damage.

This is assuming:
1. I didn't clip at the beginning of the eclipse (the part about NG below explains why)
2. I want to keep as close to 100% IS/MF uptime as possible
3. I want to cast one IS/MF during every solar/lunar eclipse, respectively (to gain maximum DPSc from eclipse)

Obviously the ideal scenario is that I just refresh the DoT normally during the eclipse, but that doesn't always work out.

Also, going off number of ticks may be more accurate here (ie. only clip when a DoT has less than 37% of it's ticks remaining), but I don't have an addon that shows number of ticks remaining so I can't do that in a fight reliably. Do those addons exist?



For those that are wondering, "What about NG for eclipse?"

I don't think it's always necessary to delay DoTs before eclipse or clip DoTs at the start of eclipse. I don't see why it matters if eclipse itself is in NG, or if my spam up to the next eclipse is in NG because eclipse bonuses are based on number of casts, not how fast I cast (DoTs are an exception, but clipping DoTs in eclipse is what this is all about [you should name your addon Eclippser btw]).

What about losing DPS by not having NG on my eclipsed DoT? Delaying the NG proc to the end of eclipse does not necessarily mean fewer DoTs affected by NG. Instead of NG guaranteed to affect Lunar MF or Solar IS during each eclipse by delaying/clipping DoTs, it's possible to have two NG DoTs during the same eclipse. If I refresh a DoT that will not be buffed by an imminent eclipse and then refresh/clip the eclipsed DoT towards the end of that eclipse, NG can last until I cast the first non-buffed post-eclipse DoT of the following eclipse (I clip the NG by half a second or so). This then procs the next NG that is applied to the eclipse-buffed DoT that follows. This only happens if the difference in the duration of the DoTs is greater than 7-8 seconds.

That was kind of a convoluted explanation, so here's an example:

• At 100 lunar energy pre-eclipse and IS duration < 1 sec and MF/Sunfire duration > 8 sec
• Refresh IS before lunar procs
• Proc lunar by casting Wrath or having a Wrath already in motion hit the target
• Cast SF/SS through Lunar
• Refresh MF during lunar to proc NG (or clip it if it's still going at the end of eclipse)
• Cast SF/SS to solar
• Refresh IS post-solar while still under the first NG to proc the next NG (this is where it's necessary to have the stagger in the DoTs; I have to cast the MF during lunar at least 6 seconds after I cast IS pre-lunar, or NG cannot make it through to the next eclipse)
• Cast Wrath/SS through solar
• Refresh/cast Sunfire under new NG while in solar

In that example, 2 DoTs are still affected by an NG proc, although it's a solar IS and a Sunfire instead of solar IS and a lunar MF (a relative DPS loss) [EDIT: After thinking about it, gaining an extra tick of Sunfire is actually the same as a tick of lunar MF so this isn't a loss at all, but the following point is still relevant I think]. However, the benefit of doing it this way is not having to clip DoTs at the start of eclipse, or delay refreshing DoTs just before eclipse to ensure one eclipsed and NG DoT per eclipse. If this saves even one DoT tick from being clipped/delayed, I think it makes sense. Giving up one extra tick of a buffed DoT for a tick of an unbuffed DoT is less than one tick of our weakest DoT (the max DPS lost ended up being about 37% of one IS tick, but the math was ugly so I didn't post it).

I am not saying that refreshing DoTs immediately before eclipse procs is always appropriate; this only applies to DoTs that will not be buffed by the incoming eclipse. The DoTs also have to be staggered by at least 7 seconds to pull this off. Furthermore, I am not saying we should stagger our DoTs to make this happen, but rather when our DoTs become staggered I think this is the appropriate way to deal with it.

Sounds complicated, but the point is I find the timing works out so NG is not wasted no matter when I proc it as long as the DoTs are staggered by more than 7 seconds and I follow a clipping rule at the end of eclipses.

If I were going to add it to the code it might look like this (placed above your Wrath/SF casts at 100 energy):

if Eclipse Energy equal to 100
and IS greater than 7 sec
and MF < 1
and TargetDead more than 6 seconds
Cast MF

if Eclipse Energy equal to -100
and MF greater than 7 sec
and IS < 1
and TargetDead more than 6 seconds
Cast IS



On Starfall priority for people without Starsurge glyph (which I think we're assuming makes the cooldown up for every lunar, although sometimes inconsistently):

I think someone mentioned earlier in the thread that saving Starfall for lunar is only worth it as long as you don't keep it for more than 37% of the CD (or 22.2 seconds). I think you caught onto that with your comment but I figured I'd spell it out just in case. Coincidentally, 22 seconds is more or less how long it takes me to go from solar eclipse to lunar eclipse w/ maximum DoT refreshing. So kind of hacky way to do it for people with no SS glyphs would be to say:

if LUNAR or (if no SOLAR and Eclipse Energy equal or more to 0) Cast STARFALL


.