Yay or Nay : Silence/stun abilties that have potency attached

In my book this is a non-issue at even a semi-decent level of play. Auto piloting is a general problem and not one specific to stun/silences, people just need to get good and know when they need to save their silence/stun abilities for special enemy skills and when they can use them on cd as a dps increase. Pointing out the fact that these abilities can be used as a dps boost when their secondary effects aren't needed as a bad thing is not the correct approach imo, just learn the correct utilization.

Ya so many times something could have been stunned but some one used their stun move for damage and it gained resistance.

Yes please.

They need to remove the stun effect on MNKs shoulder tackle, too. They already have another stun, they don't need another, especially since shoulder tackle is so useful

Naaaaaaaaaaaaaay. It's incredibly stupid that those types of abilities have damage attached to them. It would be way better for them to, you know, be used to stun/silence/etc stuff as mechanics call for than just blow the CD when it's up for free DPS. This is the only MMO I can think of that attaches damage to these abilities (from the ones I've played, anyway).

DR is stupid, too (why not just make all boss abilities immune to stuns/silence save for a few choice ones??), but that's a different topic.

Honestly I love my ogcd stuns with damage. As someone that makes MNK and DRG which both have double ogcd stuns I can't imagine why you'd wanna change that. It gives attacks much more utility and knowing when to use them and when you don't need to stun or silence is just a part of being a good dps or tank.

Quote:

---

Originally Posted by Meow9000

Honestly I love my ogcd stuns with damage. As someone that makes MNK and DRG which both have double ogcd stuns I can't imagine why you'd wanna change that. It gives attacks much more utility and knowing when to use them and when you don't need to stun or silence is just a part of being a good dps or tank.

---

And what about those who aren't good? Why should the rest of the party suffer from a stunnable ability resisting the good tanks stun because the derpgoon kept going duuuur LEG SWEEEEEP!!! (0 _ 0)

Quote:

---

Originally Posted by Meow9000

Honestly I love my ogcd stuns with damage. As someone that makes MNK and DRG which both have double ogcd stuns I can't imagine why you'd wanna change that. It gives attacks much more utility and knowing when to use them and when you don't need to stun or silence is just a part of being a good dps or tank.

---

Would it not be functionally the same to have an additional ability that stuns but deals no damage? You also have the other perspective of telling MNKs and DRGs to not use their gap closers on fights like Levi EX because the add needs to be stun locked.

I see no issue keeping potencies on utility oGCD attacks. It provides options, allows for various strategies and setups, and keeps them relevant. In this game, moves like Blunt Arrow having potencies attached to them gives you the following choices: do you hold onto it for to use when you need it, or use it whenever it comes off cooldown for extra DPS? There is nothing wrong with that. Certain oGCDs with varying utility effects can also be used to benefit the party. Does that Wavetooth Sahagin or Dreadknight need to be stun-locked, or will those attacks be better off used ASAP to reduce the damage from Sacred Cross? Both situations are viable. Finally, those abilities having potencies means that no matter the situation, they will always be used and will have a place on your hotbar. As a BRD main, I have Repelling Shot and Blunt Arrow on mine in case I need to quickly get out of an AoE or interrupt a spell cast. On the same token, I can use both of them for extra DPS if there is no need to hold onto them. Shadowbind, unfortunately, only inflicts Bind, which is hardly ever used in the majority of content since the status can be broken with a simple attack, on top of the attack having no potency value. It's an underwhelming ability in both its effect and lack of damage to the point where it's virtually useless outside of niche scenarios.

I say keep the potencies on those attacks. Discretion, or lack thereof, should not be a reason to remove them.

Attaching potency to them just meant the developers can't design content around actually needing the utility in the average content since it'll always be on cooldown by default of maximizing your dps. Doubly-so for Stun where you can burn the three-debuff resistance in mere seconds if you have a DRG or MNK in the group.

Actually never quite understood why Silence is exempt from the debuff resistance change that was made back in 2.1ish. Probably because Turn2's primary mechanic would be completely broken if it were.

Quote:

---

Originally Posted by SlyRoyale

or will those attacks be better off used ASAP to reduce the damage from Sacred Cross? Both situations are viable. Finally, those abilities having potencies means that no matter the situation, .

---

If we had more abilities like this though, all it does is cause more button bloating because you have to keep it equipped for every scenario. It doesn't necessarily add "depth" to the job either if you're just using it off cooldown, and the effect of being it used on interrupts isn't lost if the ability did only just that. Mug would be an extreme example of this where it's a 90s oGCD damage cooldown for 140 potency, but ninjas keep it on their bar anyway because straight up not using it for damage would be a waste.

Ultimately, it's also for this reason why I dislike the design/concept of abilities like gauss round and <here I'd like to come up with another example but I really can't> because it has no speical interaction with the rest of the job's tool kit, it's just a straight up damage skill that has no cast time, doesn't use GCD and ultimately doesn't amount to requiring any thought when it comes to using it (whereas even in your case, you'd have to put up some second thought to using oGCDs with stun/silenced attached to it, if it was applicable in the first place), and the cooldown isn't long enough for you to have to actually put it aside to align with cooldowns.