User Pass
Home Sign Up Contact Log In
Forum > Goal Line Blitz > any one ever see a "fair catch" that wasnt caught??
Guppy, Inc
offline
Link
 
http://glb.warriorgeneral.com/game/replay.pl?game_id=2928037&pbp_id=1239685

i dont recall ever seeing this beofre. i've seen them with 0 return yards, but I dont recall it being called a fair catch. there were no defenders close enough to trigger the fair catch and the returner had plenty of time to pick it up,
 
lexden11
offline
Link
 
Happens loads at lower levels / bad dots
 
darncat
offline
Link
 
I've seen exactly that before, but not since coming back to the game 4 season ago
Think of it as the fair catch fake where the punting team tries then to down the ball b4 it go in the EZ
except its the returner trying to down it instead! It seems like it thus works out for the punting team
as if they downed it when it reached its maximum roll (the returner never seem to get it b4 it stops bouncing)
unless it reached the end zone, which i'm trying to remember if i've ever seen happen, but is bound to at some point
 
Guppy, Inc
offline
Link
 
Originally posted by lexden11
Happens loads at lower levels / bad dots


i see plenty of bounces where the returner goes gets it, but you've seen them called fair catches?
 
ProfessionalKop
Gangstalicious
offline
Link
 
Originally posted by Guppy, Inc
i see plenty of bounces where the returner goes gets it, but you've seen them called fair catches?


Be thankful the play actually ended. Surprised it didn’t break the entire game.
 
Guppy, Inc
offline
Link
 
its weird that the players froze when the ball first bounces. i had to check the next play to see where the ball was actually spotted.
 
Blink 182
offline
Link
 
WAI

Broken is the new normal.
 
darncat
offline
Link
 
that's what always happens if the guy calls fair catch and then doesn't catch the ball
you don't often see it, cuz c'mon... catch the damn ball
 
Guppy, Inc
offline
Link
 
Originally posted by darncat
that's what always happens if the guy calls fair catch and then doesn't catch the ball
you don't often see it, cuz c'mon... catch the damn ball


glb only calls for a fair catch if a defender is within 5 yards of the returner. when the ball hits at the 19, the nearest defender is at the 27
 
Seric
offline
Link
 
Originally posted by Guppy, Inc
glb only calls for a fair catch if a defender is within 5 yards of the returner. when the ball hits at the 19, the nearest defender is at the 27


keep in mind the graphics are only an approximation of what's going on, not the exact place.
 
TJ Spikes
offline
Link
 
Originally posted by Guppy, Inc
glb only calls for a fair catch if a defender is within 5 yards of the returner. when the ball hits at the 19, the nearest defender is at the 27


IMO the fair catch was probably called up where the ball first bounced, around the 19... there was an unimpeded tackler (named Calling Dr. Death) that would have crushed the return man if he didn't call for the fair catch, and actually caught it.

The glitch is that the defense stops and doesn't pursue the bouncing ball. IRL, it's common practice for a returner to call for a fair catch, and then let it bounce, if they think the ball will bounce into the endzone for a touchback. The defense has to pursue the ball, because they can down the ball. If the ball had rolled into the endzone, it should have been a touchback.

But yeah, I've never seen it it in GLB before either.

 
darncat
offline
Link
 
Originally posted by Guppy, Inc
glb only calls for a fair catch if a defender is within 5 yards of the returner. when the ball hits at the 19, the nearest defender is at the 27


You answered your own question!

"glb only calls for a fair catch if a defender is within 5 yards of the returner." "the returner" not "the ball".
the returner attempted to make a fair catch, because there was a defender w/in 5 yards who might've popped him-
however, when he missed the ball, its irrelevant where the ball landed. the defender was w/in 5 yards
of where he tried to catch it, so he called fair catch, as would make sense if "glb only calls for a fair catch
if a defender is within 5 yards of the returner. " as you mentioned
 
darncat
offline
Link
 
Originally posted by TJ Spikes
IMO the fair catch was probably called up where the ball first bounced, around the 19... there was an unimpeded tackler (named Calling Dr. Death) that would have crushed the return man if he didn't call for the fair catch, and actually caught it.

The glitch is that the defense stops and doesn't pursue the bouncing ball. IRL, it's common practice for a returner to call for a fair catch, and then let it bounce, if they think the ball will bounce into the endzone for a touchback. The defense has to pursue the ball, because they can down the ball. If the ball had rolled into the endzone, it should have been a touchback.

But yeah, I've never seen it it in GLB before either.



yeah, i'd expect that's due to the reverse glitch of the return man hurrying his ass off to inexplicably down the ball...
 
Theo Wizzago
Coyote
offline
Link
 
A long time ago (something for the few who love to go digging through the archives) there was a thread about a fumble. Now a fumble in and of itself is nothing for this game. However... this fumble lasted for a VERY long time as the pile of dots near the sidelines looked like a mound of fruity jello during a major earthquake... while the ball sat quietly on the field about 5-10 yards away. It was (still is) major gut laughing worthy and why I never pay any attention at all to what looks like glitches in the replays. WAI.
 
ProfessionalKop
Gangstalicious
offline
Link
 
i havent seen a replay like that in a long time theo but they did happen a few times every season. infuriating as a coordinator.
 


You are not logged in. Please log in if you want to post a reply.