What's new
Fantasy Football - Footballguys Forums

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Game Thread W3 - KansasCity V San Diego (1 Viewer)

WTH are the Chargers doing on defense....pathetic.....

I'm talking to you Cason...

 
Last edited by a moderator:
this is just hard to watch. how do you snap that ball w/ 20 second left on the clock? and how do you NOT give the ball to your best RB?

 
Norv should be fired for having that ball snapped with 23 seconds on the clock. horrible. his only saving grace is that Haley and Cassel said "ineptitude? You want ineptitude? I'll SHOW you ineptitude!"

 
Norv should be fired for having that ball snapped with 23 seconds on the clock. horrible. his only saving grace is that Haley and Cassel said "ineptitude? You want ineptitude? I'll SHOW you ineptitude!"
Norv is not the qb.
they had the measurement...he should have been in Rivers' ear and making damned sure he knew not to snap it until the last second. Never mind that the sneak call was idiotic in the first place when the Chiefs clearly knew it was coming and stacked the box for it. give it to Tolbert or Matthews. I say all this as a lifelong Charger fan (grew up in Michigan, but Bolts were always my AFC team) who is tired of Norvball. I'd kill for Martyball back!
 
I've mostly defended Norv but the last two weeks I've seen some of the dumbest play of my lifetime. If a team doesn't look prepared to play and/or makes dumb plays (not bad plays, dumb plays) that's on the coaching staff.

 
Norv should be fired for having that ball snapped with 23 seconds on the clock. horrible. his only saving grace is that Haley and Cassel said "ineptitude? You want ineptitude? I'll SHOW you ineptitude!"
Norv is not the qb.
they had the measurement...he should have been in Rivers' ear and making damned sure he knew not to snap it until the last second.
Snapping it at the last second would have been unwise, IMO.The primary goal was to get the first down. Taking a little extra time was secondary.If they wait until the last second to snap it, the defense will (at that point) know precisely when it will be snapped.A quick snap count is often a good thing on QB sneaks — especially in a situation like this where Kansas City should have been expecting Rivers to try to draw them offsides, and should have been determined not to jump early. It didn't work, but it's not obvious to me that it wasn't worth a try.
 
Last edited by a moderator:
Norv should be fired for having that ball snapped with 23 seconds on the clock. horrible. his only saving grace is that Haley and Cassel said "ineptitude? You want ineptitude? I'll SHOW you ineptitude!"
Norv is not the qb.
they had the measurement...he should have been in Rivers' ear and making damned sure he knew not to snap it until the last second.
Snapping it at the last second would have been unwise, IMO.The primary goal was to get the first down. Taking a little extra time was secondary.If they wait until the last second to snap it, the defense will (at that point) know precisely when it will be snapped.A quick snap count is often a good thing on QB sneaks — especially in a situation like this where Kansas City should have been expecting Rivers to try to draw them offsides, and should have been determined not to jump early. It didn't work, but it's not obvious to me that it wasn't worth a try.
I agree that you don't wait until 1 second is left, but 22 seconds left is a bad play.
 
Rivers has never been good at the QB sneak dating back to his college days
Rivers scored 17 rushing TDs in 51 starts in college. Given his lack of mobility, I think he showed that he was at least solid at the sneak.ETA: I mean, he's 6'5", 260 or so. He should be able to get a yard when needed. I was wondering why the Chargers didn't try the sneak last week when they had the ball on the 1 foot line and ended up getting stuffed twice on Tolbert runs.
 
Last edited by a moderator:
Norv should be fired for having that ball snapped with 23 seconds on the clock. horrible. his only saving grace is that Haley and Cassel said "ineptitude? You want ineptitude? I'll SHOW you ineptitude!"
Norv is not the qb.
they had the measurement...he should have been in Rivers' ear and making damned sure he knew not to snap it until the last second.
Snapping it at the last second would have been unwise, IMO.The primary goal was to get the first down. Taking a little extra time was secondary.If they wait until the last second to snap it, the defense will (at that point) know precisely when it will be snapped.A quick snap count is often a good thing on QB sneaks — especially in a situation like this where Kansas City should have been expecting Rivers to try to draw them offsides, and should have been determined not to jump early. It didn't work, but it's not obvious to me that it wasn't worth a try.
:goodposting:
 
Norv should be fired for having that ball snapped with 23 seconds on the clock. horrible. his only saving grace is that Haley and Cassel said "ineptitude? You want ineptitude? I'll SHOW you ineptitude!"
Norv is not the qb.
they had the measurement...he should have been in Rivers' ear and making damned sure he knew not to snap it until the last second.
Snapping it at the last second would have been unwise, IMO.The primary goal was to get the first down. Taking a little extra time was secondary.If they wait until the last second to snap it, the defense will (at that point) know precisely when it will be snapped.A quick snap count is often a good thing on QB sneaks — especially in a situation like this where Kansas City should have been expecting Rivers to try to draw them offsides, and should have been determined not to jump early. It didn't work, but it's not obvious to me that it wasn't worth a try.
I agree that you don't wait until 1 second is left, but 22 seconds left is a bad play.
:goodposting: he didn't have to run it down to the last second, but snapping it w/ 23 on the play clock was simply idiotic. you could get the same effect walking up to the line w/ 12 seconds on the clock and snapping it right away. It's all symptomatic of what I see as an extremely poorly coached team. mistakes of every kind imaginable and bad play calling all day long. Norv needs to go, because this team clearly isn't winning anything with him at the helm.
 
Norv should be fired for having that ball snapped with 23 seconds on the clock. horrible. his only saving grace is that Haley and Cassel said "ineptitude? You want ineptitude? I'll SHOW you ineptitude!"
Norv is not the qb.
they had the measurement...he should have been in Rivers' ear and making damned sure he knew not to snap it until the last second.
Snapping it at the last second would have been unwise, IMO.The primary goal was to get the first down. Taking a little extra time was secondary.If they wait until the last second to snap it, the defense will (at that point) know precisely when it will be snapped.A quick snap count is often a good thing on QB sneaks — especially in a situation like this where Kansas City should have been expecting Rivers to try to draw them offsides, and should have been determined not to jump early. It didn't work, but it's not obvious to me that it wasn't worth a try.
:goodposting:
Given the look of the defense and the caliber of the player Rivers is I would have hoped he would audible out of that situation. The LB'ers were so close to the line that play looked doomed well before the snap of the ball. As someone else eluded to Rivers is just too tall in those situations and can't get low enough quickly enough to get the push required for the first down. Plus, I just don't like the franchise risking himself on a week #3 play vs the Chiefs. Something goes wrong and Rivers gets hit by seven guys and misses a couple of game the season is pretty much over. Rivers is a pretty smart guy and reads defenses very well... in this instance he just threw himself into the teeth of the defense. He proves his toughness by standing in the pocket with pressure all the time, I don't need to see him diving into the line.
 
So about McCluster - those of you who watched the game, do you feel it's reasonable to expect similar stat lines going forward, say 50-60 total yards with the upside of some long TDs every once in a while?

 
So about McCluster - those of you who watched the game, do you feel it's reasonable to expect similar stat lines going forward, say 50-60 total yards with the upside of some long TDs every once in a while?
I won't pretend to know what to expect from the Chiefs gameplans going forward, but after watching the Chiefs play essentially w/o McCluster in the 1st half only to then make him the focus of the offense in the 2nd half, I think it's clear that he's by far the best playmaker not named Bowe on the roster. I have a hard time believing the Chiefs OC doesn't recognize that, so I think McCluster has big upside in coming weeks.
 

Users who are viewing this thread

Back
Top