Results -9 to 0 of 69

Threaded View

  1. #11
    Player
    Rongway's Avatar
    Join Date
    Aug 2013
    Posts
    4,186
    Character
    Cyrillo Rongway
    World
    Hyperion
    Main Class
    Black Mage Lv 100
    Quote Originally Posted by Mansion View Post
    But second thing, Bard and Machinist DPS output is not linear but very bursty. Say a MCH had high agro, uses its Tactician, Refresh being already used ; each 60sec MCH can rip agro in its Wildfire 10sec window, or build just as much as the amount that was dropped just before.
    Yes, they are bursty, but that actually doesn't have a real effect on enmity drops. Burst is more relevant to enmity suppression. However, for enmity drops, it doesn't matter when a burst happens in relation to the drop ability cooldown, as you drop half of all enmity that happened before the ability. And even if, for some reason, you used it immediately before a burst instead of waiting another ten seconds, that would just make your next enmity drop ability more valuable, ultimately resulting in the timing of the burst not mattering.

    Quote Originally Posted by Mansion View Post
    In reality, it's different. Because Refresh is not primarily an agro drop, but a Mana regen for the party (or milking an extra tick of Foe Requiem). You don't use it on cooldown for agro, it's situational.
    This also should have little effect on the overall analysis. If you're using it specifically for Foe Requiem, then you will delay it at most 60s, after which you will only be 30s farther ahead on enmity than expected. On the next Tactician, you'd only be 15s ahead on enmity than expected, if at all (this will depend on if you decide to delay Tactician since you used Refresh so recently). None of this is enough to rip aggro off a competent tank.

    And if you're using it for MP recovery, well, don't just sit on it just to sit on it. Use it. Healers have their own recovery abilities that will hold them over until Refresh cools down.
    (0)
    Last edited by Rongway; 01-05-2019 at 06:41 PM.
    Error 3102 Club, Order of the 52nd Hour

Tags for this Thread