Better question: why should it be blockable?
olemanwinter wrote: »CC break is done exactly the same way as "bashing" (interrupting), hold right mouse button and then hit left mouse button.
It's called "Break Free" when used this way, but when you are not CC'd, it is a "bash".
So, I'm right, yeah?
Both Fear and Fossilize are CC. Both are either "Bashed" before hand or "Break free" after begun, Correct?
The skills are activated, stopped, and broken in exactly the same way.
Sooooo....
/END THREAD
Attorneyatlawl wrote: »
Attorneyatlawl wrote: »"
It's the only CC in the game you cannot prevent in advance by blocking, and it's also the only aoe "soft" cc that does not break on damage. Templars can hit you with a ground target shards, but you are free if even so much as a DoT tick from them hits you. DK's can fossilize you, but as soon as you're hit you have a chance to react. Same deal with sorcerers and their rune prison.
Attorneyatlawl wrote: »You also can block most cc's like these. However, if an NB fears you and you don't have enough stamina to CC break, you're done: they can unload damage on you as you run helplessly in a random direction. On magicka builds this is particularly nasty an issue as you already run on a tightrope to manage blocking important attacks.
Attorneyatlawl wrote: »"
It is also a damage debuff, snare, and hits three targets, while granting a major armor buff from their class passive. It's very obviously over the top . Add in the cc break bugs it is associated with currently on top of that, and you have a near abusive skill to run around spamming in 1vX or other fights.
Yes, you are correct. However, there is a bug currently w/ Break Free that makes it hard to break Fear immediately sometimes.
You can still break it, just not the instant that you're hit w/ it. This does not happen all the time, but enough to be annoying.
olemanwinter wrote: »Yes, you are correct. However, there is a bug currently w/ Break Free that makes it hard to break Fear immediately sometimes.
You can still break it, just not the instant that you're hit w/ it. This does not happen all the time, but enough to be annoying.
Fair enough. But this is a thread about why fear should be "Blockable" by design, not unbreakable by bug.
imho, enough evidence and logic has been presented that it's clearly.../end thread.
Attorneyatlawl wrote: »@dduke, that is all fine and good if it's your opinion, but it isn't factual. And comparing a one and a half second cast time spell that automatically breaks on damage to an instant aoe cc with added debuffs which doesn't break on damage I'd just silly in the first place. By the way, Templar shards can be blocked. And as a Nightblade I have access to the two hand skill line just like everyone else. The difference is you aren't free once I hit you, and you're snared and debuffed, as I slap on soul harvest just prior to give myself 20 percent more damage and a heal debuff on you (low 50 Ultimate cost means it's almost always available) alongside my always active 8 percent dmg from minor berserk . After you've been slapped by two emoowered+ high damage hits, debuffed including a heal debuff and snare, if you're still alive my next hit does 48 percent more dmg between wrecking blow empower and soul harvest. Better hope your healer is spamming breath of life!
Attorneyatlawl wrote: »Already made two large posts explaining how regardless of the bug, it is tragically imbalanced.
Attorneyatlawl wrote: »olemanwinter wrote: »Yes, you are correct. However, there is a bug currently w/ Break Free that makes it hard to break Fear immediately sometimes.
You can still break it, just not the instant that you're hit w/ it. This does not happen all the time, but enough to be annoying.
Fair enough. But this is a thread about why fear should be "Blockable" by design, not unbreakable by bug.
imho, enough evidence and logic has been presented that it's clearly.../end thread.
Already made two large posts explaining how regardless of the bug, it is tragically imbalanced.
Attorneyatlawl wrote: »olemanwinter wrote: »Yes, you are correct. However, there is a bug currently w/ Break Free that makes it hard to break Fear immediately sometimes.
You can still break it, just not the instant that you're hit w/ it. This does not happen all the time, but enough to be annoying.
Fair enough. But this is a thread about why fear should be "Blockable" by design, not unbreakable by bug.
imho, enough evidence and logic has been presented that it's clearly.../end thread.
Already made two large posts explaining how regardless of the bug, it is tragically imbalanced.
And I already made a reply that you ignored about why you cannot simply look at the ability in a vacuum.
olemanwinter wrote: »Attorneyatlawl wrote: »Already made two large posts explaining how regardless of the bug, it is tragically imbalanced.
But you...are wrong. :-/
Attorneyatlawl wrote: »olemanwinter wrote: »Yes, you are correct. However, there is a bug currently w/ Break Free that makes it hard to break Fear immediately sometimes.
You can still break it, just not the instant that you're hit w/ it. This does not happen all the time, but enough to be annoying.
Fair enough. But this is a thread about why fear should be "Blockable" by design, not unbreakable by bug.
imho, enough evidence and logic has been presented that it's clearly.../end thread.
Already made two large posts explaining how regardless of the bug, it is tragically imbalanced.
And I already made a reply that you ignored about why you cannot simply look at the ability in a vacuum.
There's also a state called no stamina that can cause the same issues, which most people mistake for it being unbreakable
olemanwinter wrote: »I'll make a deal counselor, see if you have some concept of actual balance and fairness.
If Fear was made blockable...would you concede that it should then also do damage as well?!?!?
Because all your comparisons are against abilities that do more than a simple, single CC.
It's not a question of whether NBs have the best offense in the game; that is a simple truth.
Here is another simple truth: NBs have the worst defenses in the game as well, and depend heavily on their burst and disabling opponents for victory. They cannot turtle like other classes, and their escape is the only one neutered almost entirely by a potion.
Now, in the current meta where everybody values burst for kills over pretty much everything else, it creates a situation where the burstiest class w/ the best CC clearly looks like it stands head and shoulders above the others. This has really always been the case in the past as well, but it was balanced by proportionately larger health pools and MUCH longer TTKs.
That is no longer the case, so things look unbalanced, and pointers are being waved directly at NBs who are doing what they've always done. What was once considered a gimmicky "gank" class that hit hard and got hit harder is now what everyone wants to be running, because it's fully possible to dismantle opponents before they know what hit them and continue doing so.
Fix the extremely low TTKs and you "fix" the issue w/ NBs, relegating them once again to the balance that was always inteneded.
Attorneyatlawl wrote: »I'll just quote myself again
SuraklinPrime wrote: »Fear is preventable but not blockable, it is not blockable because there need to be counters to all things and fear is the counter to permablockers.
Have you never seen a SAP essence tank?Here is another simple truth: NBs have the worst defenses in the game as well, and depend heavily on their burst and disabling opponents for victory. They cannot turtle like other classes, and their escape is the only one neutered almost entirely by a potion.
Gargragrond wrote: »SuraklinPrime wrote: »Fear is preventable but not blockable, it is not blockable because there need to be counters to all things and fear is the counter to permablockers.
Well then, why not make the fear only affect blocking opponents? Right now it seems to be a "counter" to every non-permablocker as well.
SuraklinPrime wrote: »For every plus NBs have there are things that other classs can do to us that are as bad... I think people just get more angry with being ganked half way to a destination and so say NBs are too strong when the reality is that you probably get killed much more by other classes but as it is in full on combat you don't notice it so kuch and the rage is less as a result.
Does your data include deaths before 1.6. This could explain why you were killed mostly by DKs and you killed a lot of them too.SuraklinPrime wrote: »This is over several months of stats and lots of both kills and deaths.