what an efficient process we've got going here
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > CB decides to allow TD instead of tackling - NOT A BUG - CLOSED
sarcasm?
It's better than it used to be - we're still refining the process and are trying to minimize sending over unnecessary items for Bort to look at. It doesn't mean we're always right when we ask for more proof of the issue but sometimes things are so unusual (like this play) that you really do need to see it happen more than once.
It's better than it used to be - we're still refining the process and are trying to minimize sending over unnecessary items for Bort to look at. It doesn't mean we're always right when we ask for more proof of the issue but sometimes things are so unusual (like this play) that you really do need to see it happen more than once.
recockulous
offline
offline
Originally posted by olatunde
Originally posted by Snakebite99
Looked like a stiff arm
Yeah, maybe if the ball carrier was Plastic Man. The carrier is over 5 yds away from the safety in this one:
http://goallineblitz.com/game/replay.pl?game_id=927249&pbp_id=15305927
Originally posted by Snakebite99
Looked like a stiff arm
Yeah, maybe if the ball carrier was Plastic Man. The carrier is over 5 yds away from the safety in this one:
http://goallineblitz.com/game/replay.pl?game_id=927249&pbp_id=15305927
Cryptotich
offline
offline
Originally posted by jdbolick

What is your explanation?
Every thing that happens on the field is a result of the code. If you have a better explanation then let us know. I am guessing that because you did not put one forth, that you do not have one.
Give me some thing to work with here.

What is your explanation?
Every thing that happens on the field is a result of the code. If you have a better explanation then let us know. I am guessing that because you did not put one forth, that you do not have one.
Give me some thing to work with here.
jdbolick
offline
offline
Originally posted by Cryptotich
What is your explanation? Every thing that happens on the field is a result of the code. If you have a better explanation then let us know. I am guessing that because you did not put one forth, that you do not have one. Give me some thing to work with here.
Multiple people have articulated why "head fake" was a nonsensical explanation. How would I know the actual culprit without seeing the code itself? I have no idea what did cause it, but everyone besides you knows that it wasn't a head fake.
What is your explanation? Every thing that happens on the field is a result of the code. If you have a better explanation then let us know. I am guessing that because you did not put one forth, that you do not have one. Give me some thing to work with here.
Multiple people have articulated why "head fake" was a nonsensical explanation. How would I know the actual culprit without seeing the code itself? I have no idea what did cause it, but everyone besides you knows that it wasn't a head fake.
Cryptotich
offline
offline
Originally posted by jdbolick
Multiple people have articulated why "head fake" was a nonsensical explanation. How would I know the actual culprit without seeing the code itself? I have no idea what did cause it, but everyone besides you knows that it wasn't a head fake.
You ever seen a "head fake" listed in the PBP?
Multiple people have articulated why "head fake" was a nonsensical explanation. How would I know the actual culprit without seeing the code itself? I have no idea what did cause it, but everyone besides you knows that it wasn't a head fake.
You ever seen a "head fake" listed in the PBP?
NiborRis
offline
offline
Originally posted by Jack Del Rio
what an efficient process we've got going here
Yeah, it worked great. Single incident was brought forth, possible "working as designed" suggestions were rejected, then the community brought forth more clear examples of the same issue so the issue could be taken to Bort with enough information to get him started on something identified as very likely a real issue.
That's like the dream scenario for a support organization.
what an efficient process we've got going here
Yeah, it worked great. Single incident was brought forth, possible "working as designed" suggestions were rejected, then the community brought forth more clear examples of the same issue so the issue could be taken to Bort with enough information to get him started on something identified as very likely a real issue.
That's like the dream scenario for a support organization.
driftinggrifter
offline
offline
Originally posted by Cryptotich
Originally posted by jdbolick
Multiple people have articulated why "head fake" was a nonsensical explanation. How would I know the actual culprit without seeing the code itself? I have no idea what did cause it, but everyone besides you knows that it wasn't a head fake.
You ever seen a "head fake" listed in the PBP?
The Dots get smaller.....and not because of the cold weather nethier
Originally posted by jdbolick
Multiple people have articulated why "head fake" was a nonsensical explanation. How would I know the actual culprit without seeing the code itself? I have no idea what did cause it, but everyone besides you knows that it wasn't a head fake.
You ever seen a "head fake" listed in the PBP?
The Dots get smaller.....and not because of the cold weather nethier

ok, this thread is veering off topic - Bug has been filed. I'll update this thread when/if it gets resolved.
Locking thread.
Locking thread.
You are not logged in. Please log in if you want to post a reply.




























