Thread: 8.0 DPS Job Rework Workshop/Megathread. Goals, Design Principles, and Mock-Ups.

Originally Posted by Shurrikhan

Barring that, it just means your rotation is externally affected instead, though, no? If even a single raid buff remains and there is no penalty otherwise for holding for up to 120s (no fight-specific vulnerability window for enemies or buff window for you or DPS check or %HP phase threshold, etc), you'll do it within that raidbuff.

Which is why I specifically stated in my original post that this Monk is in an environment without temporary damage raid buffs.

Originally Posted by Shurrikhan

Moreover, let's say we do somehow remove all raidbuffs, all encounter-based variation of damage output, and all DPS checks so that one has no pressure to use a skill at any particular given time. Would that even be better gameplay anyways?

In a vacuum, who knows. Now, whilst I didn't specify this (at least, I don't think I did), it does have some interplay with encounter design. If you have 2 targets that you can potentially cleave with Masterful Blitzes, or even mob packs mid fight that it would be beneficial to have the more flexible window. Of course, other jobs will have more strict burst phases and this can lead to cases where, say, Dragoon and Black Mage's burst do not line up with the mob pack coming, but Monk and Dancer, being a bit more flexible, is more than enough, so Dragoon and Black mage can stay single target on the boss whilst Monk and Dancer take care of the adds. So it is a scenario where, rather than tying everything to the 2 minute rotation, we break things up and have the potential to split focus with different jobs handling different things based on their kit. It is about making the interaction between the job kit and the encounter more intertwined.

Originally Posted by Shurrikhan

Would something like that work?

As I said, not a Ninja main, I just liked Dancing Edges animation. I will leave any potential changes to people who actually want to use Ninja.

Originally Posted by Shurrikhan

Apart from a rare few mistaking DoTs for an identity (when the identity is instead usually, at best, just trading control/utility for raw throughput over time, assuming the DoT job exists in an MMO not plagued by decontextualized numbers-envy), I don't think anyone's suggested adding a DoT "just for the sake of adding a DoT".

Yeah, It was just clarification as, in the past, it seemed they wanted to add a DoT to every job just for the sake of it.