Quote Originally Posted by Tanathya View Post
Refresh and Tactician, especially the first, is usually used on CD (note the "usually" there), and Tactician is normally up there on demand. Again, I would attach an enmity generation reduction to them on top of that. The burst is high, the enmity generation after that isn't. And I can tell you as a samurai, whose burst isn't exactly brilliant, as I struggled not to grab the hate off a tank shortly after the fights began when Diversion was crappy, on Deltascape Savage.

The likelihood of having a SAM, a NIN, or a WAR has nothing to do with the fact that PLD and DRK don't have it. DRG isn't only invited for their piercing resistance down, but also for their decent damage on top of Battle Littany and Dragon Sight. So, by that logic, the likelihood of having a DRG is quite high. It's as if they gave BRD and MCH their own piercing resistance down and the next step would be to ask for a Battle Littany kind of skill for themselves.

I would just take these resistances down away, they're not interesting in the least.
Do you realize they fixed Division for a reason, yes? It's irrelevant now since they addressed the issue. And depending on the group, progression and possible mistakes, Tactician and Refresh may not be available. It's silly design to blow support abilities solely to dump your aggro when an ability exists purely to accommodate that very purpose. Most physical range will prefer a 90% queller over a 50% dump. Likewise, why attach the aforementioned queller to another skill when you can just give them Division and accomplish the same feat?

Of course it does. Three jobs apply slashing, thus making it far less likely Paladin and Dark Knight will suffer a damage loss. I never said it was the only reason, however it's a contributing factor. Physical Range suffer more than any other job without a Dragoon. They either need to remove Piercing or allow other jobs to apply it (Samurai is screaming for relevancy) because, again, why should only one job be able to apply it when Slashing does not have such limitations?