Warrior General Games

Originally posted by DeVotchka
https://glb2.warriorgeneral.com/game/replay/624852/44530

That is a very bad one!!!

wow...

Originally posted by DeVotchka
https://glb2.warriorgeneral.com/game/replay/624852/44530

There any way knock lose can only happen right after a catch? It seem like the game no matter what is going to read it as a incomplete if it gets knocked lose no matter how many steps. But if the game read it as a fumble it would maybe fix this bug? It's like the games doesn't even think the WR moved after he made the catch or something.

Originally posted by DeVotchka
https://glb2.warriorgeneral.com/game/replay/624852/44530

Home field advantage strikes again lol

https://glb2.warriorgeneral.com/game/replay/634947/198803

Here’s another one for ya

nothing beats the first one posted by DeVotchka


I enjoying the lols regardless

That would’ve been a god dam TD lol...

Honestly, no idea how to fix this.

We have like, half a dozen sanity checks to make sure they are actually a fumble instead of knocked loose. Like, "if has ball more than 1 second, always a fumble". Then 5 more variations of that, yet this still happens.

Let's see, there's code for "if you move more than 3 yards, always a fumble". Somehow that's not working, either.

I noticed it happens more with HB's than other positions, for what its worth.

Originally posted by Corndog
Honestly, no idea how to fix this.

We have like, half a dozen sanity checks to make sure they are actually a fumble instead of knocked loose. Like, "if has ball more than 1 second, always a fumble". Then 5 more variations of that, yet this still happens.

is there something in the knock loose code that would cause it to over ride the fumble safety net codes you have in places?

Yeah, they probably have TOO many lines regarding it, and something's in the wrong order.

Had one game today. 5 steps, knocked loose. later in game catch, turn, fumble. lol