Unbreakable magnum shot stun

Baphomet · December 2018

Will it be fixed soon?

And fear as well, seeing that is has been present since beta?

Betty_Booms · December 2018

Yea. Like that video in the other post where you see his toon breakng free three times before he actually does BF. Only reason he died....

Qbiken · December 2018

Remove CC-break from the global cooldown (the same way we can use synergies outside of the global cooldown). Not saying it's the best solution but it would help alot with other abilities that contains a stun

TheYKcid · December 2018

@Qbiken

That would be a really bad idea, imo.

CC is so important in the overall dynamic of combat not just because of the duration it disables someone for, but also because it consumes one of their GCDs in the process.

Offensively, this means that stunning someone at just the right time during a burst combo opens up a 1s window after they break, during which they can't heal/shield etc., giving you an opportunity to finish the kill. Defensively, stunning someone who's about to kill you buys you 1s, and the pressure relief is crucial to recovering and resetting.

Taking CC break off the GCD would be a monumental change to the pace of combat, and not in a good way, I feel.

The simplest solution would be to just refactor Draining's CC to work like Dizzying Swing's—which also applies a knockback followed by stun, but with none of the ridiculous bugs associated with the former. ZOS could even copypaste the coding for all I care.

Edit: punctuation

caeliusstarbreaker · December 2018

It’s totally a l2p issue dude, never mind the fact that other people say they have been having the same issues with the skill.. 8 people said they haven’t sooo you’re clearly wrong. Maybe if you use that one set that allows you to break free when cc break isn’t working because a skill is buggy then you’ll have a better chance... you just gotta adapt it’s your problem really. As a matter of fact how dare you even encroach on their play style.

Ranger209 · December 2018

Break free should not grant cc immunity. It should only "break you free" from the cc. CC immunity should be part of every CC ability that is cast. If you are hit with a CC debuff it should also grant you immunity as part of the debuff. The fact that it doesn't is what allows for chain CCing. When a group of people focus you down with CC abilities you get locked down and can not break free. They keep stunning you over and over before you can. If the immunity buff were applied to the CC debuffs across the board themselves this would not be possible. You would be immune to further CC after taking on the first CC. Then you would be able to break free without being focused down by more CC.

bardx86 · December 2018

Ranger209 wrote: »

Break free should not grant cc immunity. It should only "break you free" from the cc. CC immunity should be part of every CC ability that is cast. If you are hit with a CC debuff it should also grant you immunity as part of the debuff. The fact that it doesn't is what allows for chain CCing. When a group of people focus you down with CC abilities you get locked down and can not break free. They keep stunning you over and over before you can. If the immunity buff were applied to the CC debuffs across the board themselves this would not be possible. You would be immune to further CC after taking on the first CC. Then you would be able to break free without being focused down by more CC.

This is exactly what i have been saying for years.

Bashev · December 2018

TheYKcid wrote: »

@Qbiken

That would be a really bad idea, imo.

CC is so important in the overall dynamic of combat not just because of the duration it disables someone for, but also because it consumes one of their GCDs in the process.

Offensively, this means that stunning someone at just the right time during a burst combo opens up a 1s window after they break, during which they can't heal/shield etc., giving you an opportunity to finish the kill. Defensively, stunning someone who's about to kill you buys you 1s, and the pressure relief is crucial to recovering and resetting.

Taking CC break off the GCD would be a monumental change to the pace of combat, and not in a good way, I feel.

The simplest solution would be to just refactor Draining's CC to work like Dizzying Swing's—which also applies a knockback followed by stun, but with none of the ridiculous bugs associated with the former. ZOS could even copypaste the coding for all I care.

Edit: punctuation

@TheYKcid
Make break free consuming GD but let it removed from it. So if I am on CD let me break free and give me 1 sec CD till the next skill.

TheYKcid · December 2018

Bashev wrote: »

TheYKcid wrote: »

@Qbiken

That would be a really bad idea, imo.

CC is so important in the overall dynamic of combat not just because of the duration it disables someone for, but also because it consumes one of their GCDs in the process.

Offensively, this means that stunning someone at just the right time during a burst combo opens up a 1s window after they break, during which they can't heal/shield etc., giving you an opportunity to finish the kill. Defensively, stunning someone who's about to kill you buys you 1s, and the pressure relief is crucial to recovering and resetting.

Taking CC break off the GCD would be a monumental change to the pace of combat, and not in a good way, I feel.

The simplest solution would be to just refactor Draining's CC to work like Dizzying Swing's—which also applies a knockback followed by stun, but with none of the ridiculous bugs associated with the former. ZOS could even copypaste the coding for all I care.

Edit: punctuation

@TheYKcid
Make break free consuming GD but let it removed from it. So if I am on CD let me break free and give me 1 sec CD till the next skill.

@Bashev that is already how the system works lol.

ALL normally-functioning CCs will reset your GCD when they stun you. This is why you are always able to break-free instantly, regardless of when your last ability-cast occurred.

The few exceptions to this are CCs that force you to endure the animation (eg. Time Stop, Permafrost freeze), and clearly bugged ones like Draining.

Bashev · December 2018

TheYKcid wrote: »

Bashev wrote: »

TheYKcid wrote: »

@Qbiken

That would be a really bad idea, imo.

CC is so important in the overall dynamic of combat not just because of the duration it disables someone for, but also because it consumes one of their GCDs in the process.

Offensively, this means that stunning someone at just the right time during a burst combo opens up a 1s window after they break, during which they can't heal/shield etc., giving you an opportunity to finish the kill. Defensively, stunning someone who's about to kill you buys you 1s, and the pressure relief is crucial to recovering and resetting.

Taking CC break off the GCD would be a monumental change to the pace of combat, and not in a good way, I feel.

The simplest solution would be to just refactor Draining's CC to work like Dizzying Swing's—which also applies a knockback followed by stun, but with none of the ridiculous bugs associated with the former. ZOS could even copypaste the coding for all I care.

Edit: punctuation

@TheYKcid
Make break free consuming GD but let it removed from it. So if I am on CD let me break free and give me 1 sec CD till the next skill.

@Bashev that is already how the system works lol.

ALL normally-functioning CCs will reset your GCD when they stun you. This is why you are always able to break-free instantly, regardless of when your last ability-cast occurred.

The few exceptions to this are CCs that force you to endure the animation (eg. Time Stop, Permafrost freeze), and clearly bugged ones like Draining.

And when u add fear, eclipse and petrify and who knows what else and we will have a full list.
When I am CC I want to use my break free immediately.

TheYKcid · December 2018

Yup, I agree that we should always be able to break-free immediately.

Whether ZOS wants to achieve that by addressing the specific offending skills, or universally changing break-free mechanics, is ultimately up to them. I do think your suggestion is solid, though.

FYI, Eclipse is uniquely unlike all other CCs, because it doesn't reset your GCD (which is fair, since it doesn't actually stun you, and you are free to perform all actions whilst it's applied to you). If you want to break Eclipse, you need to stop casting abilities immediately and wait for GCD.

ZOS_Mika · December 2018

We have removed a handful of unnecessary and off topic comments from this thread. Please ensure that the discussion stays civil and doesn't go off the rails. Thanks for your understanding.

Ranger209 · December 2018

Certain animations seem to be the worst offenders, fear and knockbacks, rune cage had one too. These seem to take a cooldown before you can even try to break free, which makes it even easier to chain stun. Again if the CC debuff itself also triggered cc immunity you could not be chain stunned. With the Break free skill applying cc immunity you can get chain stunned because you can get stunned again and again before you are afforded the opportunity to actually try to break free.

Waffennacht · December 2018

Ranger209 wrote: »

Certain animations seem to be the worst offenders, fear and knockbacks, rune cage had one too. These seem to take a cooldown before you can even try to break free, which makes it even easier to chain stun. Again if the CC debuff itself also triggered cc immunity you could not be chain stunned. With the Break free skill applying cc immunity you can get chain stunned because you can get stunned again and again before you are afforded the opportunity to actually try to break free.

Deep freeze and Permafrost have the frozen animation and it's just as bad; though very rare unless via permafrost

Kadoin · December 2018

Baphomet wrote: »

Will it be fixed soon?

And fear as well, seeing that is has been present since beta?

Doubt it, its been broken for a long while since they changed how disorients worked. In Summerset it was at its worst when you shot someone with that skill + rune cage. If it was done right, your target would need to relog or use the help menu to fix the stun on it (could not be broken at all). Good thing they fixed that one at least...I think! I hope...