Poop Ok, lets hear it from the Matt Cassel nutthuggers! - Page 3

**BigMeatballDave** · 11-14-2010, 06:42 PM

Quote:

Originally Posted by milkman

There's no question that the D was responsible for the loss today.

Oh, without a doubt. However, what did Cassel do between Bronco scoring drives?

**BigMeatballDave** · 11-14-2010, 06:43 PM

Quote:

Originally Posted by DeezNutz

Cassel just orchestrated the greatest garbage time, stat-padding performance in NFL history.

When it mattered, he was ****ing awful, taking unnecessary sacks, missing open receivers, ensuring that we moved out of field goal range, and turning the ball over.

With zero pressure and the game out of reach, though, look the **** out! Cassel time, baby.

Chiefs Pantalones · 11-14-2010, 06:43 PM

Quote:

Originally Posted by BCD

Oh, without a doubt. However, what did Cassel do between Bronco scoring drives?

Eat a hotdog...

With NO MUSTARD! THE BASTARD!

**doomy3** · 11-14-2010, 06:43 PM

Quote:

Originally Posted by milkman

There's no question that the D was responsible for the loss today.

Not a ****ing doubt. This has become such an irrational board.

**Baby Lee** · 11-14-2010, 06:44 PM

Quote:

Originally Posted by BCD

Oh, without a doubt. However, what did Cassel do between Bronco scoring drives?

5 & O
3 & O
sacked out of FG range
sacked for defensive TD.

Other than that, meh.

Chiefs Pantalones · 11-14-2010, 06:44 PM

Quote:

Originally Posted by DeezNutz

Cassel just orchestrated the greatest garbage time, stat-padding performance in NFL history.

When it mattered, he was ****ing awful, taking unnecessary sacks, missing open receivers, ensuring that we moved out of field goal range, and turning the ball over.

With zero pressure and the game out of reach, though, look the **** out! Cassel time, baby.

lol pretty much

Lbedrock1 · 11-14-2010, 06:44 PM

Quote:

Originally Posted by Bane

33/53 469 yards 4 TD's 0 INT's.Enjoy.

Those stats are BS. We lost by 20 so we know why he threw for 469 yards. Soft coverage and less preassure. He still missing throws when we need him to make them.

tk13 · 11-14-2010, 06:44 PM

Quote:

Originally Posted by Baby Lee

Switching Lewis and McGraw for Price and Washington was a big part of that, though.

Remember the Colts w/ and w/o Sanders their SB year?

That's the sad part. Everyone here is so obsessed with Cassel's bowel movements no one is going to talk about the fact that our safeties were out and Washington got abused like a rented mule in the first 5 minutes.

chiefzilla1501 · 11-14-2010, 06:45 PM

Quote:

Originally Posted by patteeu

I don't know who the nuthuggers are, but it's ridiculous to have Cassel at the top of the hate list after the game the Chiefs just played.

You know me. I'm not the type to overreact to bad games by teams or players. I thought this was easily Cassel's worst game all season. That's independent of how the defense played or of his statistics in the first 2 quarters. The Chiefs didn't move down the field on offense because he was staring down his primary receiver and holding onto the ball too long.

Regardless of how the defense played, this was a terrible game for Cassel.

FAX · 11-14-2010, 06:45 PM

Quote:

Originally Posted by Baby Lee

5 & O
3 & O
sacked out of FG range
sacked for defensive TD.

Other than that, meh.

He always starts a little slow, though.

FAX

Three7s · 11-14-2010, 06:45 PM

Another big problem was the D-line. They were getting pushed around all game. NO PRESSURE AT ALL!

**Shogun** · 11-14-2010, 06:45 PM

Quote:

Originally Posted by Vanilla Thunder

Eat a hotdog...

With NO MUSTARD! THE BASTARD!

Maybe he needs to try Nachos?

BryanBusby · 11-14-2010, 06:46 PM

Cassel ****ing sucked, but it's irrelevant when your defense gives up almost 50 points to a shitty team.

FAX · 11-14-2010, 06:46 PM

Quote:

Originally Posted by chiefzilla1501

You know me. I'm not the type to overreact to bad games by teams or players. I thought this was easily Cassel's worst game all season. That's independent of how the defense played or of his statistics in the first 2 quarters. The Chiefs didn't move down the field on offense because he was staring down his primary receiver and holding onto the ball too long.

Regardless of how the defense played, this was a terrible game for Cassel.

You needlessly over-analyze the living crap out of things, Mr. chiefzilla1501. But, that's why I like you ... no homo.

You're right this time, though. The goats had Cassel scouted perfectly.

Gif it up.

FAX

milkman · 11-14-2010, 06:48 PM

Quote:

Originally Posted by Marcellus

Please let me hear from the defensive nuthuggers.

One performance was kind of expected, the other wasn't.

Hell I will give Cassel credit for at least taking what he could in garbage time, the defense couldn't even do that.

1 ****ing punt.

And **** Cassel for that Goddamn fumble.

What we are beginning to see is the defense has no depth and are getting worn, which also leads to the deficiencies that many of us were concerned about being exposed.

No consistent pass rush outside of Hali, no real NT, and only two competent 5 techs that are playing a lot minutes.

Add the fact that we were starting our 4th safety, a converted corner who looks even more lost at safety than he did at corner, and you have a recipe for bad defense.

11-14-2010, 06:31 PM
BigMeatballDave GBM 8-12-15 Join Date: Aug 2000 Location: Dayton, Oh. Casino cash: $10052154	Ok, lets hear it from the Matt Cassel nutthuggers!
Posts: 59,997

11-14-2010, 06:45 PM	#41
Three7s MVP Join Date: Nov 2008 Casino cash: $10084719	Another big problem was the D-line. They were getting pushed around all game. NO PRESSURE AT ALL!
Posts: 6,739

11-14-2010, 06:46 PM	#43
BryanBusby In Search of a Life Join Date: Mar 2006 Casino cash: $3689900 VARSITY	Cassel ****ing sucked, but it's irrelevant when your defense gives up almost 50 points to a shitty team.
Posts: 22,239