I can't speak for what the code is now, but in the past there definitely was the possibility of knocking loose an interception because we had that happen and yet the defense retained possession (despite it being labeled "knocked loose" in the pbp). Supposedly that bug was fixed, so who knows if the "fix" might be the culprit here.
Forum > Discuss GLB Issues With Catch22 > RESOLVED BUGS > No knocked loose for defense :( - FILED BUG #183
robponce
offline
offline
Originally posted by NiborRis
So, my 2 cents - I find it certainly possible that there's no knocked loose on an interception. All this takes is a single example to disprove, but I wouldn't be surprised if the pbp-text can't even properly handle it, so even if it does exist we might not see it. WRs never show up with a deflection on an interception, and really shouldn't, and a knocked loose is a type of deflection so the check may just not be done. Hopefully people can look around for examples/counter-examples and we can get an idea. I don't think this is a candidate for trying to test just because it's so difficult to reliably create the scenario.
This is my exact thinking. I'm pretty sure it'd be something to check the source for if a check is even being made. My hunch (gut feeling) is that it is not.
The best person to ask would be Bort on this one.
So, my 2 cents - I find it certainly possible that there's no knocked loose on an interception. All this takes is a single example to disprove, but I wouldn't be surprised if the pbp-text can't even properly handle it, so even if it does exist we might not see it. WRs never show up with a deflection on an interception, and really shouldn't, and a knocked loose is a type of deflection so the check may just not be done. Hopefully people can look around for examples/counter-examples and we can get an idea. I don't think this is a candidate for trying to test just because it's so difficult to reliably create the scenario.
This is my exact thinking. I'm pretty sure it'd be something to check the source for if a check is even being made. My hunch (gut feeling) is that it is not.
The best person to ask would be Bort on this one.
RMiller517
offline
offline
Originally posted by robponce
This is my exact thinking. I'm pretty sure it'd be something to check the source for if a check is even being made. My hunch (gut feeling) is that it is not.
The best person to ask would be Bort on this one.
how i view that it was programmed by what i've heard from bort is that the catching algorithm is the one that is applied after it is decided who is doing the catching. that being said, it might be an entirely different algorithm that determines if a caught pass is knocked loose, on either offense or defense. i can't see why there would be two sets of code to do the same thing.
all that being said... i agree that bort is the best person to answer this, because it would be very tough to try and test to determine the difference.
This is my exact thinking. I'm pretty sure it'd be something to check the source for if a check is even being made. My hunch (gut feeling) is that it is not.
The best person to ask would be Bort on this one.
how i view that it was programmed by what i've heard from bort is that the catching algorithm is the one that is applied after it is decided who is doing the catching. that being said, it might be an entirely different algorithm that determines if a caught pass is knocked loose, on either offense or defense. i can't see why there would be two sets of code to do the same thing.
all that being said... i agree that bort is the best person to answer this, because it would be very tough to try and test to determine the difference.
robponce
offline
offline
Originally posted by RMiller517
how i view that it was programmed by what i've heard from bort is that the catching algorithm is the one that is applied after it is decided who is doing the catching. that being said, it might be an entirely different algorithm that determines if a caught pass is knocked loose, on either offense or defense. i can't see why there would be two sets of code to do the same thing.
all that being said... i agree that bort is the best person to answer this, because it would be very tough to try and test to determine the difference.
On Defense the coding is this:
Roll for INT -> Fail -> Roll for PD -> Pass or Fail -> CATCH -> Roll for Knocked Loose -> if success=Incomplete
This I know for fact.
What I allude to is that the knocked loose portion wasn't added or buffed until Jackhammer was added. It's possible that the offense has after the catch a roll to knocked loose, but is missing the "incomplete" portion where if it is knocked loose it is considered incomplete and not a fumble.
See what I'm saying?
how i view that it was programmed by what i've heard from bort is that the catching algorithm is the one that is applied after it is decided who is doing the catching. that being said, it might be an entirely different algorithm that determines if a caught pass is knocked loose, on either offense or defense. i can't see why there would be two sets of code to do the same thing.
all that being said... i agree that bort is the best person to answer this, because it would be very tough to try and test to determine the difference.
On Defense the coding is this:
Roll for INT -> Fail -> Roll for PD -> Pass or Fail -> CATCH -> Roll for Knocked Loose -> if success=Incomplete
This I know for fact.
What I allude to is that the knocked loose portion wasn't added or buffed until Jackhammer was added. It's possible that the offense has after the catch a roll to knocked loose, but is missing the "incomplete" portion where if it is knocked loose it is considered incomplete and not a fumble.
See what I'm saying?
Deathblade
offline
offline
There's actually 2 ways to look at it imo
Either, A), there's no such thing as knocked loose for interceptions...even if he only had the ball in his hands for 1/10th of a second (actually less, since it was only in his hands for half a tick, so 1/20th of a second). and that instead of getting the knocked loose, it counted as a fumble
Or, B), it WAS knocked loose, but before the ball hit the ground, the offense caught it. Would be possible that the circumstances are so rare that the PBP just didn't know (or in other words, wasn't coded) wtf to do. If the same thing would have happened for the defense, it would have been knocked loose -> intercepted, but the PBP read that it was a turnover for the offense, and offense can't intercept their own passes, so it was declared a fumble.
Either, A), there's no such thing as knocked loose for interceptions...even if he only had the ball in his hands for 1/10th of a second (actually less, since it was only in his hands for half a tick, so 1/20th of a second). and that instead of getting the knocked loose, it counted as a fumble
Or, B), it WAS knocked loose, but before the ball hit the ground, the offense caught it. Would be possible that the circumstances are so rare that the PBP just didn't know (or in other words, wasn't coded) wtf to do. If the same thing would have happened for the defense, it would have been knocked loose -> intercepted, but the PBP read that it was a turnover for the offense, and offense can't intercept their own passes, so it was declared a fumble.
RMiller517
offline
offline
Originally posted by Deathblade
There's actually 2 ways to look at it imo
Either, A), there's no such thing as knocked loose for interceptions...even if he only had the ball in his hands for 1/10th of a second (actually less, since it was only in his hands for half a tick, so 1/20th of a second). and that instead of getting the knocked loose, it counted as a fumble
Or, B), it WAS knocked loose, but before the ball hit the ground, the offense caught it. Would be possible that the circumstances are so rare that the PBP just didn't know (or in other words, wasn't coded) wtf to do. If the same thing would have happened for the defense, it would have been knocked loose -> intercepted, but the PBP read that it was a turnover for the offense, and offense can't intercept their own passes, so it was declared a fumble.
i see what you're saying. Relating to your case A, is it possible, though, that he did fully catch it, come down, and then fumble it?
In other words, If it does happen how rob says (which i agree that it does), then it is possible that the receiver passed the knocked loose roll, but then on the very next tick failed the fumble roll...no?
There's actually 2 ways to look at it imo
Either, A), there's no such thing as knocked loose for interceptions...even if he only had the ball in his hands for 1/10th of a second (actually less, since it was only in his hands for half a tick, so 1/20th of a second). and that instead of getting the knocked loose, it counted as a fumble
Or, B), it WAS knocked loose, but before the ball hit the ground, the offense caught it. Would be possible that the circumstances are so rare that the PBP just didn't know (or in other words, wasn't coded) wtf to do. If the same thing would have happened for the defense, it would have been knocked loose -> intercepted, but the PBP read that it was a turnover for the offense, and offense can't intercept their own passes, so it was declared a fumble.
i see what you're saying. Relating to your case A, is it possible, though, that he did fully catch it, come down, and then fumble it?
In other words, If it does happen how rob says (which i agree that it does), then it is possible that the receiver passed the knocked loose roll, but then on the very next tick failed the fumble roll...no?
NiborRis
offline
offline
Originally posted by jdbolick
I can't speak for what the code is now, but in the past there definitely was the possibility of knocking loose an interception because we had that happen and yet the defense retained possession (despite it being labeled "knocked loose" in the pbp). Supposedly that bug was fixed, so who knows if the "fix" might be the culprit here.
That's actually very insightful - I assume the bug was such that the defensive team got the ball at the prior LOS?
In that case this may just be a case of narrowly missing the window. Knocked loose interceptions have got to be extremely rare beasts. I think at this stage we just need to wait for more examples/counterexamples.
I can't speak for what the code is now, but in the past there definitely was the possibility of knocking loose an interception because we had that happen and yet the defense retained possession (despite it being labeled "knocked loose" in the pbp). Supposedly that bug was fixed, so who knows if the "fix" might be the culprit here.
That's actually very insightful - I assume the bug was such that the defensive team got the ball at the prior LOS?
In that case this may just be a case of narrowly missing the window. Knocked loose interceptions have got to be extremely rare beasts. I think at this stage we just need to wait for more examples/counterexamples.
NiborRis
offline
offline
Was looking for something else and found this gem:
http://goallineblitz.com/game/forum_thread.pl?thread_id=3629727&page=2#32199254
Originally posted by
Bort has reviewed the filed bug and said it needs some investigation but that for now he will make it to where INT's can not be KL'ed which should solve this issue. Change should go into effect before tomorrow's games - not sure he'll make a changelog update for the fix so posting here.
Looks like this is intentional, but it hasn't been revisited since. This was filed as Bug #48, but we cleaned out the old bugs and started fresh with the new bugs team. I'd like to refile a new bug on this to get Bort working on it again - from the Bugzilla report it's clear he always intended to go back and put a proper fix in place, and lack of knocked loose interceptions was an interim solution.
http://goallineblitz.com/game/forum_thread.pl?thread_id=3629727&page=2#32199254
Originally posted by
Bort has reviewed the filed bug and said it needs some investigation but that for now he will make it to where INT's can not be KL'ed which should solve this issue. Change should go into effect before tomorrow's games - not sure he'll make a changelog update for the fix so posting here.
Looks like this is intentional, but it hasn't been revisited since. This was filed as Bug #48, but we cleaned out the old bugs and started fresh with the new bugs team. I'd like to refile a new bug on this to get Bort working on it again - from the Bugzilla report it's clear he always intended to go back and put a proper fix in place, and lack of knocked loose interceptions was an interim solution.
NiborRis
offline
offline
And I'll go ahead and be the second verification, since I wasn't actually any of the other steps.
Please reference bug #48 when refiling this.
Please reference bug #48 when refiling this.
HouseRules
offline
offline
You are not logged in. Please log in if you want to post a reply.






























