Wow, didn't realize Burnside would cause such a stir in WL. This is a first 
Forum > Champion League > New S41 WL Teams
Pena_FIN
offline
offline
Originally posted by TrevJo
Originally posted by Pena_FIN
Bort's timeout "logic" rears its ugly head, once again.
Timeout may have turned out to be irrelevant here. INT play started at 1:20, had it happened at 0:40 instead that wouldn't have prevented Burnside from throwing a 41 yard pass three plays later.
Like you said, in GLB it's the offense who calls timeouts in a tie game, like they did here. But that isn't the only screwed up thing here. Even if Sunday Funday turns the ball over like they did, they most definitely shouldn't be calling that defensive timeout at 1:04, since they a more than likely to get the ball back with time left any way. Then let's still assume that Burnside makes a 41 yarder any way, and they grind it to inside the FG range like they did. In that case SF would definitely stop the clock on 3rd down with a timeout and not let it run down to 1 second, which is what happened.
It's almost a perfect example of how the timeout logic can fail at common football logic in every way possible, all at once. None of SF's timeouts should have been called. And when they actually should have called one, they didn't.
I've long since accepted that the T.O. logic is fubar, and that it's still fair because it's equally fucked for both teams. But that was by far the worst example of it that I've ever seen. And in case anyone is wondering, I don't have any connection with either team, I don't care who won or lost.
Originally posted by Pena_FIN
Bort's timeout "logic" rears its ugly head, once again.
Timeout may have turned out to be irrelevant here. INT play started at 1:20, had it happened at 0:40 instead that wouldn't have prevented Burnside from throwing a 41 yard pass three plays later.
Like you said, in GLB it's the offense who calls timeouts in a tie game, like they did here. But that isn't the only screwed up thing here. Even if Sunday Funday turns the ball over like they did, they most definitely shouldn't be calling that defensive timeout at 1:04, since they a more than likely to get the ball back with time left any way. Then let's still assume that Burnside makes a 41 yarder any way, and they grind it to inside the FG range like they did. In that case SF would definitely stop the clock on 3rd down with a timeout and not let it run down to 1 second, which is what happened.
It's almost a perfect example of how the timeout logic can fail at common football logic in every way possible, all at once. None of SF's timeouts should have been called. And when they actually should have called one, they didn't.
I've long since accepted that the T.O. logic is fubar, and that it's still fair because it's equally fucked for both teams. But that was by far the worst example of it that I've ever seen. And in case anyone is wondering, I don't have any connection with either team, I don't care who won or lost.
bhall43
offline
offline
Is it sad that I wouldn't have even known that is how we lost if it wasn't brought up in this thread?
TrevJo
offline
offline
Originally posted by Pena_FIN
Like you said, in GLB it's the offense who calls timeouts in a tie game, like they did here. But that isn't the only screwed up thing here. Even if Sunday Funday turns the ball over like they did, they most definitely shouldn't be calling that defensive timeout at 1:04
I disagree with that. 3rd & 14.5 at the Burnside 15 yard line with 1:04 left? I think real defenses would be calling a timeout there.
Originally posted by Pena_FIN
since they a more than likely to get the ball back with time left any way.
Very little though. If they don't call the timeout there, Burnside can run it down to less than 25 seconds before 3rd down, leaving about 20 seconds before the 4th down punt (assuming a defensive stop), giving Sunday only about 15 seconds with which to get into field goal range. Even with 1 more timeout to use that could easily not be enough.
Like you said, in GLB it's the offense who calls timeouts in a tie game, like they did here. But that isn't the only screwed up thing here. Even if Sunday Funday turns the ball over like they did, they most definitely shouldn't be calling that defensive timeout at 1:04
I disagree with that. 3rd & 14.5 at the Burnside 15 yard line with 1:04 left? I think real defenses would be calling a timeout there.
Originally posted by Pena_FIN
since they a more than likely to get the ball back with time left any way.
Very little though. If they don't call the timeout there, Burnside can run it down to less than 25 seconds before 3rd down, leaving about 20 seconds before the 4th down punt (assuming a defensive stop), giving Sunday only about 15 seconds with which to get into field goal range. Even with 1 more timeout to use that could easily not be enough.
Edited by TrevJo on Apr 16, 2014 17:12:35
Originally posted by bhall43
Is it sad that I wouldn't have even known that is how we lost if it wasn't brought up in this thread?
word on the street is that you threw the game so you didn't have to go up against Baby Sizzle s41WLMVP this season.
Is it sad that I wouldn't have even known that is how we lost if it wasn't brought up in this thread?
word on the street is that you threw the game so you didn't have to go up against Baby Sizzle s41WLMVP this season.
bhall43
offline
offline
Originally posted by ProfessionalKop
word on the street is that you threw the game so you didn't have to go up against Baby Sizzle s41WLMVP this season.
I threw the game in order to stay out of a league with hhwc.
word on the street is that you threw the game so you didn't have to go up against Baby Sizzle s41WLMVP this season.
I threw the game in order to stay out of a league with hhwc.
Originally posted by bhall43
I threw the game in order to stay out of a league with hhwc.
that does make more sense but i like my idea as to why you didnt come up to WL better.
I threw the game in order to stay out of a league with hhwc.
that does make more sense but i like my idea as to why you didnt come up to WL better.
You are not logged in. Please log in if you want to post a reply.
