3 Gamebreaking Buffer Input Bugs. Fix ASAP, they've been happening since Launch

[manliest_Man]

1. Uncancellable Taunt after Lunge. If you minor Lunge or Major Lunge and input a taunt, the full taunt plays out and you are 1000% more vunerable, it's as broken as the normal taunts were at Launch. I keep accidentally microlunging and I end up getting KO'ed because of it.
   
2. Position/Game Reset after catching a leg into a takedown. This more often happens when there is a bit of input lag/bad connection. I've been able to recreate it like this: " Catch Opponent's Body Kick: First - Quickly Tap X for takedown, then instantly tap Square for Punch as you are letting go of X."
   
3. Lunging Backwards or Sideways then Lunging Forward starts the Auto Full Speed running animation. This should only work when double lunging forward...

[RetractedMonkey]

Re: 3 Gamebreaking Buffer Input Bugs. Fix ASAP, they've been happening since Launch

None of these are gamebreaking except the game reset. I don't know how much they could do about that at this point. Maybe it has something to do with the netcode. I'm 100% positive the developers know about every single one of these, regardless.

As for the others: I don't think there are really any situations where you want to chain any lunge into a forward lunge. There should almost always be a better maneuver you could use.

Don't taunt after a lunge. Pretty simple solution there.

Gee, another very useful topic.

[RomeroXVII]

Re: 3 Gamebreaking Buffer Input Bugs. Fix ASAP, they've been happening since Launch

1. Uncancellable Taunt after Lunge. If you minor Lunge or Major Lunge and input a taunt, the full taunt plays out and you are 1000% more vunerable, it's as broken as the normal taunts were at Launch. I keep accidentally microlunging and I end up getting KO'ed because of it.
   
2. Position/Game Reset after catching a leg into a takedown. This more often happens when there is a bit of input lag/bad connection. I've been able to recreate it like this: " Catch Opponent's Body Kick: First - Quickly Tap X for takedown, then instantly tap Square for Punch as you are letting go of X."
   
3. Lunging Backwards or Sideways then Lunging Forward starts the Auto Full Speed running animation. This should only work when double lunging forward...

Double Lunging when you input the lunge once.

[LarsP]

Re: 3 Gamebreaking Buffer Input Bugs. Fix ASAP, they've been happening since Launch

None of these are gamebreaking except the game reset. I don't know how much they could do about that at this point. Maybe it has something to do with the netcode. I'm 100% positive the developers know about every single one of these, regardless.

As for the others: I don't think there are really any situations where you want to chain any lunge into a forward lunge. There should almost always be a better maneuver you could use.

Don't taunt after a lunge. Pretty simple solution there.

Gee, another very useful topic.

Is this condescending tone necessary in every thread that stresses a problem that you don´t prioritize?

[VitoBurrito]

Re: 3 Gamebreaking Buffer Input Bugs. Fix ASAP, they've been happening since Launch

It’s ea, of course there s a million glitches, u have to be satisfied with inferiority

[HereticFighter]

Re: 3 Gamebreaking Buffer Input Bugs. Fix ASAP, they've been happening since Launch

Double Lunging when you input the lunge once.

yep. its habit for me to hit block as i'm coming out of a lunge, particularly if i timed it a bit early and they tracked me anyways. double lunge happens frequently for me sometimes. Tracking on lunges in general is a little spotty

[RomeroXVII]

Re: 3 Gamebreaking Buffer Input Bugs. Fix ASAP, they've been happening since Launch

yep. its habit for me to hit block as i'm coming out of a lunge, particularly if i timed it a bit early and they tracked me anyways. double lunge happens frequently for me sometimes. Tracking on lunges in general is a little spotty

And body punches still track. That should be fixed soon though.

Sent from my SM-G965U using Operation Sports mobile app

[RetractedMonkey]

Re: 3 Gamebreaking Buffer Input Bugs. Fix ASAP, they've been happening since Launch

Is this condescending tone necessary in every thread that stresses a problem that you don´t prioritize?

Not at all. Only against the people that consistently make these topics. This isn't an issue on problems I personally prioritize. It's an issue with the life-or-death tone of objectively small issues.

If the game crashed and booted you from Xbox Live every time you threw a punch after a leg kick, I'd call that gamebreaking.

The fact that someone thinks when you can't cancel a taunt after a lunge to be a priority fix ASAP is not only indefensible, but offensive to my sensibilities.

And this guy makes these topics coooooonstantly. And if you can't see where someone would have an issue with any of this, ya might just be on the receiving end.

You guys don't even recognize the times where I do bite my tongue because I'm not wanting to be inflammatory. raypace made a topic which I vehemently disagree with the tone of. He likely experienced one match where his opponent subbed him and made an exaggerated topic about how it happens all the time. He doesn't normally do that and I haven't seen him be a nuisance anywhere else, so I just tried to help him. No 'personal flare' necessary. manliest_man has a very long track record of useless and ignorant posts. That draws my ire.

[SUGATA]

Re: 3 Gamebreaking Buffer Input Bugs. Fix ASAP, they've been happening since Launch

1. Uncancellable Taunt after Lunge. If you minor Lunge or Major Lunge and input a taunt, the full taunt plays out and you are 1000% more vunerable, it's as broken as the normal taunts were at Launch. I keep accidentally microlunging and I end up getting KO'ed because of it.
2. Position/Game Reset after catching a leg into a takedown. This more often happens when there is a bit of input lag/bad connection. I've been able to recreate it like this: " Catch Opponent's Body Kick: First - Quickly Tap X for takedown, then instantly tap Square for Punch as you are letting go of X."
3. Lunging Backwards or Sideways then Lunging Forward starts the Auto Full Speed running animation. This should only work when double lunging forward...

#3 is the MOST CRITICAL BUG here, i wrote about it before.
https://forums.operationsports.com/f...n-how-fix.html

Run is totally broken.

Lunging FWD after a BWD lunge as A BAIT - is a STANDARD for real life (provoke opponent's whiff) and for fighting games (possibly w some exceptions in input via cancelling into side step for ex), this is MUST HAVE.

Lack of this is unrealistic, breaking game balance and restrict footwork.

ANY experienced fighting player knows it. It is BASICS for fighting games. And there are no things to discuss here.
I hope Devs will see this or my topics about these issues - and will give us the ability to bait and punish opponent normally as real fighters has in real life! At least as a reward for those from community who spend their free time to make game better instead of trolling or insult others on OS.

Other BUFFER BUGS issues threads:
https://forums.operationsports.com/f...e-how-fix.html

https://forums.operationsports.com/f...s-how-fix.html

[xtremeba1000]

Re: 3 Gamebreaking Buffer Input Bugs. Fix ASAP, they've been happening since Launch

Double Lunging when you input the lunge once.

Double lunge bug is horrible. I get KO'd anytime I try to lunge cause It always lunges to one side then immediately to the opposite direction.

[TheGentlemanGhost]

Re: 3 Gamebreaking Buffer Input Bugs. Fix ASAP, they've been happening since Launch

Input in general is bad. Whether it's blocking, lunging or striking, the problem is all around in UFC 3. It wasn't like this before.

Sent from my SM-J700P using Operation Sports mobile app

[Skynet]

Re: 3 Gamebreaking Buffer Input Bugs. Fix ASAP, they've been happening since Launch

Double lunge bug is horrible. I get KO'd anytime I try to lunge cause It always lunges to one side then immediately to the opposite direction.

This isn't a bug, it's you entering two lunges from aggressive flicks on the stick where the stick goes back in the other direction after. We can't just ignore immediately pushed lunges in other directions, as one of the other issues here is asking for that exact thing (but without the running, which is a bug).

The thresholds for how far the stick has to move to register an input is actually pretty far already, the farther out it goes, the slower your intentional inputs get in. Sometimes you can even lose a frame or two if it's really far from center. That being the case, we're unlikely to change this threshold and help a handful of people while likely harming many others, when it's within your power to help yourself.

[RomeroXVII]

Re: 3 Gamebreaking Buffer Input Bugs. Fix ASAP, they've been happening since Launch

This isn't a bug, it's you entering two lunges from aggressive flicks on the stick where the stick goes back in the other direction after. We can't just ignore immediately pushed lunges in other directions, as one of the other issues here is asking for that exact thing (but without the running, which is a bug).

The thresholds for how far the stick has to move to register an input is actually pretty far already, the farther out it goes, the slower your intentional inputs get in. Sometimes you can even lose a frame or two if it's really far from center. That being the case, we're unlikely to change this threshold and help a handful of people while likely harming many others, when it's within your power to help yourself.

Thank you for clarifying.

[DaisukEasy]

Re: 3 Gamebreaking Buffer Input Bugs. Fix ASAP, they've been happening since Launch

This isn't a bug, it's you entering two lunges from aggressive flicks on the stick where the stick goes back in the other direction after. We can't just ignore immediately pushed lunges in other directions, as one of the other issues here is asking for that exact thing (but without the running, which is a bug).

The thresholds for how far the stick has to move to register an input is actually pretty far already, the farther out it goes, the slower your intentional inputs get in. Sometimes you can even lose a frame or two if it's really far from center. That being the case, we're unlikely to change this threshold and help a handful of people while likely harming many others, when it's within your power to help yourself.

If it's just the input from a controlstick snapping back passed it's default position then just temporarily increase the deadzone for X amount of beginning frames of a lunge input.

That way the snapping back won't create double inputs but you won't sacrifice speed either since people generally push the stick out entirely, don't input a second lunge within 5 frames of inputting the first one and generally buffer doubles lunges anyway..

Seems like a simple fix to me if that's actually the problem. But I might be missing something, who knows..

[Skynet]

Re: 3 Gamebreaking Buffer Input Bugs. Fix ASAP, they've been happening since Launch

If it's just the input from a controlstick snapping back passed it's default position then just temporarily increase the deadzone for X amount of beginning frames of a lunge input.

That way the snapping back won't create double inputs but you won't sacrifice speed either since people generally push the stick out entirely, don't input a second lunge within 5 frames of inputting the first one and generally buffer doubles lunges anyway..

Seems like a simple fix to me if that's actually the problem. But I might be missing something, who knows..

Were this an ideal world, that would be true. However, due to restrictions in the engine the game is built, we can't dynamically modify the ranges of the input like that. Might not make sense, and perhaps it doesn't, but the input system in our engine is very static in regards to what controller states constitute an input. It doesn't change at runtime at all, so we can't have temporary differences in the inputs.

All we can do, and what we've done in the past, is ignore inputs within a certain amount of time. However, that would also include ignoring inputs that were intentionally entered. I don't claim to know/understand why the engine is this way and what benefits or necessities if any went into that design, but it's the way it is and not something we have the power to change.

Edit: There are convoluted ways of achieving this by having multiple similar inputs that all have different thresholds, and only allowing some of them under different circumstances...but that's gross from a design point. Perhaps still worth doing if it solves the problem and there isn't a better way...the joys of game design!