RiskyChalice863 wrote: »[
That’s not how it has to work though. You can just attack a few times and get stunned and immediately break free (with a snare immunity ability easily making you immune to the prior effects if you want). After that you’ve got cc immunity. And you’ve got cc immunity after being able to control exactly when (and if) you got stunned/damaged and being able to immediately break free without requiring any reaction time to being stunned since you are triggering it yourself. I can’t understand how you could think that outcome is far worse than simply being stunned by a normal stun where the enemy chooses when to stun you and it happens.
The only reason you could have Eclipse applied to you again after 6 seconds is if the first cast never actually stunned you in the first place. If it actually stuns you, then that can’t happen. What you’re asking for is the equivalent of saying you should get cc immunity if you dodged Stone Giant. You don’t get cc immunity if you don’t actually get stunned.
I think there’s a real mental thing going on here. Here’s the deal with this version of Eclipse. If you think you can live through a stun (i.e. you’ve got the stamina to break free or the health to just tank it), then eat the stun and break free. If you think you can’t live through a stun, then apply heals and buffs and dots while the Eclipse is up. Unlike a normal stun, which can actually stun you at a time when you’re vulnerable, you basically should never die because of an Eclipse, since you control if and when it has any effect. Of course, if you can’t survive a stun and therefore just apply heals and buffs and dots during its duration, then it can just be applied again after its duration ends. But that time around you may be in a position to eat the stun and survive, and then you’re cc immune.
And none of this is even mentioning the fact that it can be cleansed.
The truth is that this version of Eclipse is a horrible offensive tool. No good player should EVER die as a result of an Eclipse stun because you control when and if you’re stunned. To compensate for its lack of offensive capability, the ability got a more drawn out cc mechanic (snare —> immobilize —> stun) and got more potential damage than most stuns. Basically, to compensate for the fact that you can control when and if you get stunned, the actual effect going along with that stun is a bit worse for the victim. I’d say that’s pretty balanced.
RiskyChalice863 wrote: »No I just think it’s weird that your definition of counterplay for this ability is that there should be a way to easily avoid being stunned by it. Can you avoid being stunned by any other stun in the game? No. If a DK hits you with Fossilize, you are stunned and there’s nothing you can do to prevent that from happening.