(10-04-2015, 03:00 PM)grampahol Wrote: [ -> ]Let it go cupcakes ..It's a game.
I'm guessing this means that you can't back up your claim? Can't say that I'm surprised.
The ruling on the field, it was a Tyler Eiffert touchdown last week... Lol
So why didn't Eifert have a touchdown????? WTH?????
oh so now they can call new penalties on replays?
Should there have been a false start also?
what constitutes a catch? The league should really define this, since it seems to change a lot from game to game.
Nice penalty Peko. Not like the D is giving them enough on their own and you have to give them 15 yards.
unnecessary roughness? we're going to be losing this game soon with the chiefs getting the ball back at half, wtf.
Why can't skeptics be delightfully surprised and not thrown into "the butthurt" category who are eating crow.
It's a long season and hopefully post-season folks. You can still be reserved about his play.
We need neither reasonable calls NOR timeouts to beat the Chefs!
If this is a catch, Eifert scored last week.
Hard to figure out.
How that's a catch and Eifert's isn't is baffling. I won't argue the rule calls were correct, but the rule is stupidly written.
(10-04-2015, 03:03 PM)djam Wrote: [ -> ]It looked like a catch to me, but I dont understand the rules anymore apparently.
Neither do the teams, and everyone else watching!!
Kirkpatrick needs to quit talking shit to the WR. No need to fire guys up, especially when they keep burning you!
Damn, the D is shaky today.
(10-04-2015, 03:05 PM)reuben.ahmed Wrote: [ -> ]unnecessary roughness? we're going to be losing this game soon with the chiefs getting the ball back at half, wtf.
IDK, Chiefs will need to learn how to score touchdowns first.
About time we get another sack.
Ha Peko for his second sack of the day
Playing pretty dumb football right now.. Stupid penalties, stupid coaching. This is what kept Baltimore in the game last week.