Please upgrade your browser for the best possible experience.

Chrome Firefox Internet Explorer
×

The stun excuse


Banderal's Avatar


Banderal
01.29.2013 , 06:10 AM | #11
Quote: Originally Posted by paul_preib View Post
I guess at the end of the day one thing I'd just like to see is a little more of someone actively saying "that was me I screwed up"
I've seen it! I really have! In a Huttball a couple days ago, totally saw someone type into chat, "sorry, that crappy pass was my bad". But I know, screen shot or it didn't happen. I would have had a screen shot, but someone stunlocked me right then and I couldn't hit the screen-shot-keys on my keyboard.

Carter_Mathis's Avatar


Carter_Mathis
01.29.2013 , 06:31 AM | #12
I almost never feel stunlocked.... maybe it's because I save my cc break for when I need an escape, and not when I want to break a break-on-damage cc early... while I have a dot on me....

Lightning_'s Avatar


Lightning_
01.29.2013 , 06:41 AM | #13
Yes, just recently there was a player that was running with the ball on our own goal line for 15 secs. Eventually he died and when confronted he ofc said he was stunlocked. For the whole 15 secs. With the enemy team attacking him, so it was a hard stun all the time.

Well, now my eyes are opened and I realize how bad the stunlocks are in this game. Gonna start a new whine thread.

cycao's Avatar


cycao
01.29.2013 , 06:53 AM | #14
Quote: Originally Posted by cashogy_reborn View Post
welcome to the our current society. your actions are always someone else's responsibiltiy
QFE.

/5char

rainbow's Avatar


rainbow
01.29.2013 , 06:53 AM | #15
Quote: Originally Posted by Lightning_ View Post
Yes, just recently there was a player that was running with the ball on our own goal line for 15 secs. Eventually he died and when confronted he ofc said he was stunlocked. For the whole 15 secs. With the enemy team attacking him, so it was a hard stun all the time.

Well, now my eyes are opened and I realize how bad the stunlocks are in this game. Gonna start a new whine thread.
How in any possible way can you get chainstunned for 15 seconds?!? Another question - how could you even survive that?
Jar'Kai Sword:
Adwaennah - Sith Assassin
Evelynne - Operative
Adwaenyth - Jedi Sentinel

ArchangelLBC's Avatar


ArchangelLBC
01.29.2013 , 08:29 AM | #16
Quote: Originally Posted by rainbow View Post
How in any possible way can you get chainstunned for 15 seconds?!? Another question - how could you even survive that?
Overlapping bubble stuns can keep you stunned for that long and at 200 resolve per stun, not even the last one will fill your resolve bar, and all of it is hard stun.

Could be they had a healer there keeping them up so long (last night I was carrying the ball on my shadow cause our team had no one else even remotely capable. I must have had the ball for over a solid minute as I got knocked off the scaffold right before the last fire, into the pit, got out of the pit, ran all the way back to mid with the ball, getting stunned, or rooted, or attacked the whole time, took the mid ramp up and still managed to score.

With good healers and all your cooldowns up (for classes with decent cooldowns) you'd be surprised how long you can stay up.
In update 2.9 the game will simply uninstall itself for you.

-Wnd

Aebrynis's Avatar


Aebrynis
01.29.2013 , 08:32 AM | #17
Quote: Originally Posted by paul_preib View Post
While I understand that this game is extremely CC heavy and folks spend a lot of time stunned, I always find it funny how readily "stunlocked" is thrown out there by people figuring it's the best excuse.

While it has always been the chief answer to "why didn't you pass?" in huttball (even if said ballcarrier was still moving around the map when killed), finding it used more and more elsewhere too, such as earlier today watching a commando dpsing down the player in front of him while another opponent (non stealther) planted right behind him, for the final door at about the one minute mark.

After the cap "couldn't get him, stunlocked" then when two different players called him out that he was actively firing at someone else when it happened "well I didn't see anyone else helping so not my fault".


I guess at the end of the day one thing I'd just like to see is a little more of someone actively saying "that was me I screwed up"-- may not make me any less frustrated at a loss, but at least then I'd be mad about losing in general instead of at a specific person
Not being able to pass a Huttball because of a stunlock is a very real situation. Mainly because if you have the ball, and if the other team has even a passing idea about what they're supposed to be doing, they're going to gang up on you and do everything they can to immobilize you and then beat the **** out of you, and stuns are the most effective way to make sure you stay in place.

In a situation like that, if I get stunlocked and burned down, all the grousing afterwards counts for exactly squat, and it really doesn't help when someone's screeching "WHY DIDNT U PASS???" Never mind the usual garbage grammar, I'm sure we all have time to take two to eight seconds to stop and present an in-depth battlefield analysis as to why we were standing immobile in one place with a horde of Republic ball players trying to shove their lightsabers and autocannons up our hindquarters.

It doesn't matter if I'm the one who 'didn't pass', if I was the one waiting to be passed to, or whether I'm simply on the same team. The pass wasn't made, I need to accept that, and I need to fight back the impulse of screaming at someone for an answer that will ultimately not satisfy me or anyone else.

Having said that, I do understand your frustration at someone simply not paying attention, and then claiming 'stunlock' as an excuse. Before I stopped playing Civil War altogether, I would have "Enemies at snow!" typed in and ready for me to hit the 'Return' key, and I would have my zoomed-out perspective constantly panning using the left mouse key (a tip someone passed along to me). Upon getting sapped by a shadow or scoundrel, or seeing incoming red above someone, I would scream like a stuck piglet (hit the 'Return' key), and then figure out what I was going to do to delay the cap until help arrived. And it always baffled me why some people never did the same when guarding the nodes in the same fashion (i.e. no stealth abilities myself).

Apart from being constructive (tips afterwards, regardless of reaction), there's not a lot anyone can do to change any of this. One has to be proactive - in my case, I refuse to play in Civil War, and it's vastly improved my opinion of PvP. _Plus I know asking for answers during a match is a recipe for a blood pressure spike, so I don't bother - the answer is never good enough.

Ybini's Avatar


Ybini
01.29.2013 , 08:39 AM | #18
Seems like the stunlocking thing happens when you're undergeared really. Reason it seems is because you have the choice to wait through your first stun to break cc, which when you're undergeared you may not live through, or breaking the cc. So you opt to break cc and get stunned again and die anyway, or if you wait you're dead within one more hit anyway.

paul_preib's Avatar


paul_preib
01.29.2013 , 07:52 PM | #19
Quote: Originally Posted by Aebrynis View Post
Not being able to pass a Huttball because of a stunlock is a very real situation. Mainly because if you have the ball, and if the other team has even a passing idea about what they're supposed to be doing, they're going to gang up on you and do everything they can to immobilize you and then beat the **** out of you, and stuns are the most effective way to make sure you stay in place.

In a situation like that, if I get stunlocked and burned down, all the grousing afterwards counts for exactly squat, and it really doesn't help when someone's screeching "WHY DIDNT U PASS???" Never mind the usual garbage grammar, I'm sure we all have time to take two to eight seconds to stop and present an in-depth battlefield analysis as to why we were standing immobile in one place with a horde of Republic ball players trying to shove their lightsabers and autocannons up our hindquarters.

It doesn't matter if I'm the one who 'didn't pass', if I was the one waiting to be passed to, or whether I'm simply on the same team. The pass wasn't made, I need to accept that, and I need to fight back the impulse of screaming at someone for an answer that will ultimately not satisfy me or anyone else.

Having said that, I do understand your frustration at someone simply not paying attention, and then claiming 'stunlock' as an excuse. Before I stopped playing Civil War altogether, I would have "Enemies at snow!" typed in and ready for me to hit the 'Return' key, and I would have my zoomed-out perspective constantly panning using the left mouse key (a tip someone passed along to me). Upon getting sapped by a shadow or scoundrel, or seeing incoming red above someone, I would scream like a stuck piglet (hit the 'Return' key), and then figure out what I was going to do to delay the cap until help arrived. And it always baffled me why some people never did the same when guarding the nodes in the same fashion (i.e. no stealth abilities myself).

Apart from being constructive (tips afterwards, regardless of reaction), there's not a lot anyone can do to change any of this. One has to be proactive - in my case, I refuse to play in Civil War, and it's vastly improved my opinion of PvP. _Plus I know asking for answers during a match is a recipe for a blood pressure spike, so I don't bother - the answer is never good enough.
While I realize it can happen as someone who's sat there spamming "H" (my huttball pass keybind) praying it'll go off before I go down, this was more a commentary on those people who are very obviously not stunned that throw it out, something I am seeing far too often. If you were running/shooting/etc. then don't bother trying to say you were stunned, you don't have to take the weight of everything with a "it was me I'm terrible" etc. but just do your team the courtesy of staying quiet as they all know you were not at all "stunlocked"
Cyperian -- Sorceror Cyterian-- Sentinel Cyrellian-- Trooper Cyprian-- Sage
Cylerian-- Scoundrel Kyrellian-- Sniper
Of the Bloodborne and Deargna-Fhuil Legacies

Keyran-Halcyon's Avatar


Keyran-Halcyon
01.29.2013 , 09:16 PM | #20
Quote: Originally Posted by paul_preib View Post
While I understand that this game is extremely CC heavy and folks spend a lot of time stunned, I always find it funny how readily "stunlocked" is thrown out there by people figuring it's the best excuse.

While it has always been the chief answer to "why didn't you pass?" in huttball (even if said ballcarrier was still moving around the map when killed), finding it used more and more elsewhere too, such as earlier today watching a commando dpsing down the player in front of him while another opponent (non stealther) planted right behind him, for the final door at about the one minute mark.

After the cap "couldn't get him, stunlocked" then when two different players called him out that he was actively firing at someone else when it happened "well I didn't see anyone else helping so not my fault".


I guess at the end of the day one thing I'd just like to see is a little more of someone actively saying "that was me I screwed up"-- may not make me any less frustrated at a loss, but at least then I'd be mad about losing in general instead of at a specific person
The biggest thing I have noticed, and sadly done some myself, is when you get jumped and stunned your mind tends to panic and your first reaction is to run or fight back against what is hitting you instead of either defending the objective or typing for help in chat.

I routinely do this to players on my scoundrel, instead of using dirty kick right after the shoot first stun wears off, I use my leg blast that I have specced to give me a root. Most players will panic at the fact they cannot move and they won't even fight back because they think they are still stunned.

But I agree its common place for people to blame everyone else but themselves when something goes wrong.
<Art Supplies>
Captain Hng Slo & Master Teh-Hauss