Small chime in on scripted fights. Talking in absolutes I side with silverquick. Small anecdote why: My static in ultimate Doesn't have a SAM and our DRG refuses to withhold burst to take down his add quick, so I as the nin conserve my first DWD and Assassinate to bolster my Doll kill time so I can get the first feed. I use the exact same set of GCD's and oGCD's to kill the bot, but because of crit variance on some really heavy hitters (A raiton, DWD, and a bhava go out) there have been times where I've killed my bot without completing the last two GCDs, a spinning edge, and a gust slash, And there have been times where even after both of those GCD's the bot is above 25%.
my typical pattern on Doll is Aeolian->DWD->Raiton->Assassinate->EARLIEST FEED TIME Spinning(Crit dependent)->Bhava (CD)->Gust (CD)->Bhava(CD) LATEST FEED TIME IF NO CRITS
I specifically use this combo cause the DWD is multi hit and thus less likely to cause crit variance, and the Assassinate is always crit+direct thus stable. The raiton is the scariest part. If raiton crits I'm immediately dropping Gust+bhava from the end. if Raiton AND 2-3 of DWD AND first bhava crits I've killed my doll. SO i have to watch DWD and Raiton to know whether to tab target switch to LL after Assassinate, or after the second bhava.
You could rationally argue my rotation tho doesn't change cause in that moment I just tab target to the boss earlier or later and my attacks remain the same, but my movement, and my targets have changed due to randomness in both the doll spawn position and the crits involved,
BUT thats not entirely true cause i convert a bhava into a frog if i save it.
Regardless tho the cumulus actions are take are different and reactionary to the spawn positions of the fight and crit variance.
(That math can be easily seen. as a crit is worth 50% extra damage the raiton crit potency gain is 400, and the DWD is 300 bhava is 150. While my two other GCDs Spinning and Gust are 220+330. IE if i crit Raiton and most of DWD ive already done spinning and gust's dmg. If i don't crit ANYTHING spinning and gust aren't enough to make up the 850 loss due to crit failure, and thus instead of saving a frog and/or Katon for when LL and LH are back together I'm forced to spend that 50 ninki to change my rotation for an extra bhava (300-450 if crit) to reduce the loss)
-Side note, this is even more frustrated by RNG i've discovered when the bot spawns in such a place that its in range to get hit by the Main tank paladins AoE move (Confiteor) that he naturally happens to be using at that point in a fight. So again for perfect dps uptime for both of us we have to be aware of where the bot spawns.

Reply With Quote


