Why are there so many? I parry a highlanders ballerina twirl one time, I get a gb, i parry it again, I whiff the gb, which leads to him getting a gb... So I get punished for trying to punish... Then I actually manage to throw him to the ground ( an extremely arduous task seeing as all you have to do is dodge backwards), I throw him to the ground, and whiff the attack. No punish yet again.
During the tournament, a player got beat when his character glitched and fell over for no reason. The announcers said and I quote " that's how realistic this game is... He tripped over a rock.". I literally vomited with disgust soon hearing that! Are you kidding me?! That's not a game mechanic, he just got ****ed over by this games ****ty inconsistency... And everyone acted like it's a real thing. If I parry attack a, I should get punish a! Not I might get punish a, or get punished myself for trying! That's some trash mechanics. Every move in this game should be consistent. If I throw someone to the ground, I should get whatever punish I am supposed to every time. I have dealt with this for a while, but when it happened 4 times in 1 duel, I couldn't handle it any longer. Please make the game consistent...
I can see your not that smart. Don't worry, I will dumb it down to barny style for you. It's not "distance" or "reach" I'm talking about. It is when The Exact Same Parry, stay with me now, On The Exact Same Attack, almost there keep going, Has Two Different Outcomes. This is called an Inconsistency. It isn't a purposeful mechanic. It is poor optimization. I know every character and I know what I can/can't get on just about every attack in the game. This has nothing to do with 2 characters having different punishments, it is about the same attack having 2 different results. I hope I didn't lose you on this. I know words are hard. Next time I'll have some pretty pictures for you!Originally Posted by kweassa1 Go to original post![]()
It could be the result of any number of factors. Yes, it's possible that there is some kind of inconsistency with the move itself, and if so, I'll ask you to send in a bug report to support so we can have someone look at it. It's also possible that things like latency, input lag, or even a misreading of the situation could have resulted in what you saw.
The best way to know for sure is to show us by video, so a good idea for next time would be to capture a clip to show to us that a definitive, undeniable problem exists. Otherwise it's extremely difficult for us to judge based solely on your words.
Also, let's be nice and behave on the forums ok? Here's a link to the forum rules if you need a refresher.
Closing thread