My god, he was awful in that sequence.What are you doing Phil? What a terrible set of plays.
My god, he was awful in that sequence.What are you doing Phil? What a terrible set of plays.
Rivers played a lot better than I thought he wouldLOL
Rivers is trash
I think Indy is a better team that Pittsburgh is right now - if the Steelers beat the Browns, I really like the Bills' chances next week.I don’t understand why they’re so excited. Even if they make it to the Super Bowl, they know what happens then.
Seemed about a yard and a half short to me.He reached the end zone. Me surprised.
They win?I don’t understand why they’re so excited. Even if they make it to the Super Bowl, they know what happens next.
He didn’t. Brissett has to throw that there.He reached the end zone. Me surprised.
On further review I think you're right. Unless the guy behind the guy catches it, they don't make it.Seemed about a yard and a half short to me.
How much of that is actually luck?You can be lucky without ref interference. But just off the top of my had the Colts have had an interception dropped and a missed fumble recovey that a Colts player fell right on top of. Also two very close sidelines catches that were called complete on the field that led to a TD drive. The Colts also missed a gimme FG and called a toss on 3rd and goal from the 1.
You're right. He might have had nobody open and gotten jumpy about getting sacked and game over.But he was in the pocket and still had time to consider his options, I thought.
I was confused on that whole frigging sequence. Clock was running, then Bills called TO when I would have let the mistake cost the Colts more time. Ended up working out because the Bills would have had a completion at the 40 for a spike instead of a few incompletions then hail mary.There was 19 secs left at the snap before the TO, but they ran it to 14?
From the bills side almost all of it?How much of that is actually luck?
No question they benefited from some bad play-calling and execution from the Colts, who won the battle in the trenches on both sides of the ball. Recovering Allen’s fumble is the one big stroke of luck they got. Agree to disagree on the sideline catches — making plays is making plays, and officials getting the calls right doesn’t count as luck, even though it doesn’t always happen. The only reason we’re even talking about the dropped INT was an atrocious on-field call that was reversed on replay; that was just a very nice pass-defense by the DB.You can be lucky without ref interference. But just off the top of my had the Colts have had an interception dropped and a missed fumble recovey that a Colts player fell right on top of. Also two very close sidelines catches that were called complete on the field that led to a TD drive. The Colts also missed a gimme FG and called a toss on 3rd and goal from the 1.
If??Another good thing about this result if you dislike KC: they won't know who their opponent is until after tomorrow night's game and can't start scouting until then.
It would have made it to the end zone if the ref didn’t inexplicably mark the first down pick of 2 yards back about 3 yards so it ended up being 2nd and 11 instead of 2nd and 8 (two plays before the Hail Mary).Seemed about a yard and a half short to me.
Apparently, the guy fumbled backwards out of bounds, which explains the yards difference. Doesn't explain the clock starting 5 seconds before they actually snapped the ball thoughIt would have made it to the end zone if the ref didn’t inexplicably mark the first down pick of 2 yards back about 3 yards so it ended up being 2nd and 11 instead of 2nd and 8 (two plays before the Hail Mary).
Sub-60 completion percentage with the kind of protection he got isn’t very good. League-average QB play probably wins this game for the Colts.Rivers played a lot better than I thought he would
I'm afraid there's almost no chance the next game lives up to the drama and quality of the first game. (Which might suit you anyway, if Seattle wins...)GO HAWKS!
The clock started after the review when the ref told it to wind.With :28 left on the clock, the clock started when Rivers yelled ‘ready’, two seconds before the snap. The play went out of bounds at 0:21, then kept running down to 0:19. Then the clock started again as soon as the ball was placed, running down to 0:15 at the snap. What the hell?
Count the easy drops. I have 4 in my mind.Sub-60 completion percentage with the kind of protection he got isn’t very good. League-average QB play probably wins this game for the Colts.
Ah, I forgot about that replay and that makes sense. I do think Pittman was going forward and they ran two seconds off after he was out though.The clock started after the review when the ref told it to wind.
Pittman fumbled the ball backwards out of bounds. Looks like the clock resumes when the refs spot the ball in that scenario?
Just the worst passes and then a hail mary that was so short, it gave the Bills DBs a running start to pound the ball into the ground, making the ball utterly uncatchable.My god, he was awful in that sequence.
It will be close. Seattle seems incapable of playing in a blowout.I'm afraid there's almost no chance the next game lives up to the drama and quality of the first game. (Which might suit you anyway, if Seattle wins...)
I did say drama *and* quality.It will be close. Seattle seems incapable of playing in a blowout.
Any given Saturday.I'm afraid there's almost no chance the next game lives up to the drama and quality of the first game. (Which might suit you anyway, if Seattle wins...)
I rewatched it. The line judge threw a bean bag indicating fumble. He ruled a forward fumble out of bounds, by rule the ball is moved back to the spot of contact and the runner is considered down at that spot (inbounds). So the clock was started as soon as the referee got word from the sideline that there was a fumble on the play.Apparently, the guy fumbled backwards out of bounds, which explains the yards difference. Doesn't explain the clock starting 5 seconds before they actually snapped the ball though
If he did truly fumble backwards out bounds,I think it makes sense. Going backwards out of bounds is considered loss of forward progress (in bounds) and doesn’t stop the clock. (99% sure on this)Apparently, the guy fumbled backwards out of bounds, which explains the yards difference. Doesn't explain the clock starting 5 seconds before they actually snapped the ball though
Yup. Mine has completely frozen. Must be the Wolford news lolDraftkings app currently shitting the bed. Not like it’s a big betting weekend or anything.