Chiefs Chiefs release WR Jeremy Maclin - Page 34

pugsnotdrugs19 · 05:42 PM

Wow

We have released wide receiver Jeremy Maclin.

➡️ https://t.co/xVXKqOhP3g pic.twitter.com/Gulky5JiAF
— Kansas City Chiefs (@Chiefs) June 2, 2017

The release of Maclin clears $10 million cap space since he was a post June 1 cut.
— Terez A. Paylor (@TerezPaylor) June 2, 2017

TigeRRUppeRRcut · 06-03-2017, 10:16 AM

Quote:

Originally Posted by staylor26

His YAC ability is ridiculous which is why I think he's a great fit in this offense.

I really like the work he put in on ST too. That showed me he's got the work ethic necessary to reach his potential.

The exact reason they picked up Chesson. Watching his game film the guy could snatch the ball and take off.

Frosty · 06-03-2017, 10:16 AM

Quote:

Originally Posted by JASONSAUTO

It was a third iirc

A 3rd and a 6th

http://www.kansascity.com/sports/nfl...e72502047.html

pugsnotdrugs19 · 06-03-2017, 10:20 AM

One thing that has always been a pet peeve of mine is the thinking that teams can just double team player X, and player Y, etc. and be just fine. It doesn't work that way. You can only truly double team one guy.

If you play single high and roll a safety up to bracket Kelce, you're taking the odds that your corners can handle the sidelines to themselves. And maybe they can, that probably depends on the personnel. Unless the single high safety has elite range, teams are not counting on him to cover from sideline to sideline.

If you are playing two high, you will more than likely account for the deep parts of the field (though the Reek TD vs. Oakland and the famous wide open GIF vs. PIT came against two high shells). However, you are leaving Kelce to be covered by linebackers or slot CBs, and that typically hasn't worked well for defenses.

My point is, the situation isn't near as dire as some would make it seem. Did our offense get worse losing Maclin? Yes. But long term, this will benefit us most as we head into the Mahomes era, and hopefully see that Robinson, Conley, or Chesson have legit ability.

NJChiefsFan · 06-03-2017, 10:22 AM

Quote:

Originally Posted by Otter

I'll just add:

1. One more "wow", didn't see this coming

2. Never understood the hate for Wilson although I agree he's not a #1 but also isn't paid as such

3. This season is going to be like watching one of your buddies go through the first 6-7 months of a divorce. If you have to ask what that means...

Wilson showed again in the playoff game why he is never going to be anything more than a high 4, low 3.

**Rausch** · 06-03-2017, 10:26 AM

Quote:

Originally Posted by NJChiefsFan

Wilson showed again in the playoff game why he is never going to be anything more than a high 4, low 3.

We'll now have a ton of 4th string guys starting.

At both WR positions...

TigeRRUppeRRcut · 06-03-2017, 10:26 AM

Quote:

Originally Posted by Hammock Parties

Yes, this is the bread and butter on offense. Not the WRs, and it never will be while Smith is the QB.

We are back to having a bottom 10 WR corps. We have one guy and some what ifs.

Seattle, Pitt and Atlanta have had great success using the run game to propel the passing offense. Matt Ryan put up career numbers when they paired Freeman with Coleman. Even better than when he had TG, Douglas, Julio, and Roddy White. Both Atlanta and New England saw 20% of their pass production come from running backs last year. KC is headed that way also with the Hunt pick.

**DaneMcCloud** · 06-03-2017, 10:29 AM

Quote:

Originally Posted by pugsnotdrugs19

Did our offense get worse losing Maclin? Yes.

This is pure and utter speculation.

The Chiefs won 12 games last year with Maclin playing like ass. He was targeted 15 times in the Texans game and caught six. That's pathetic. He was awful in the playoff game and missed 4 games entirely with a groin injury.

The Chiefs weren't getting a 27 year old Maclin that put up 1,088 yards in 2017. He's 29 and declining rapidly. It's also clear that the Chiefs thought that their younger guys are capable of filling the 530 yard void left by releasing Maclin.

The bottom line is that this move allows the young guys, be it Chesson, Robinson or even Seantavious Jones, an opportunity to step up and contribute.

I think this move has very little, if any, negative impact to the offense.

keg in kc · 06-03-2017, 10:34 AM

WR production often has more to do with QB than it does with WR. There aren't really that many Calvin Johnson calibre receivers out there. That's why teams like Pittsburgh, New Orleans, New England and even San Diego have managed to excel consistently for years on offense regardless of who they put on the field on the outside.

That said, this is still a bit of a head-scratcher.

**Rausch** · 06-03-2017, 10:36 AM

Quote:

Originally Posted by DaneMcCloud

He was targeted 15 times in the Texans game and caught six.

The texans have both a legit D and a legit CB.

Quote:

Originally Posted by DaneMcCloud

He was awful in the playoff game and missed 4 games entirely with a groin injury.

Injury is definitely a concern for Maclin.

His production in the Steelers game was 100% on Smith's shitty performance.

TWICE Hill was wide open deep and he never saw it. The one deep pass he attempted to Maclin was thrown out of bounds on purpose. Go back and look...

The Chiefs weren't getting a 27 year old Maclin that put up 1,088 yards in 2017. He's 29 and declining rapidly. It's also clear that the Chiefs thought that their younger guys are capable of filling the 530 yard void left by releasing Maclin.

The bottom line is that this move allows the young guys, be it Chesson, Robinson or even Seantavious Jones, an opportunity to step up and contribute.

I think this move has very little, if any, negative impact to the offense.[/QUOTE]

Hammock Parties · 06-03-2017, 10:36 AM

Quote:

Originally Posted by TigerUppercut

Because the Seahawks had such a great receiving corps when they won the SB. Stupid.

They won with top 5 defense and a top 10 QB. Neither of which we have.

NJChiefsFan · 06-03-2017, 10:36 AM

Quote:

Originally Posted by Rausch

We'll now have a ton of 4th string guys starting.

At both WR positions...

Hill is a 4th string WR? Conley isn't either. Whatever point you had gets lost with the massive exaggeration. Would you take 4th string WR compensation for Hill? Cause 31 teams would probably be willing to give us 4th string value for him.

pugsnotdrugs19 · 06-03-2017, 10:37 AM

Quote:

Originally Posted by DaneMcCloud

This is pure and utter speculation.

No it isn't. The Chiefs cut a good WR and replaced him with no one, therefore they got worse.

I get the move. Gives the young guys a chance to get experience and prove their worth before they play with Mahomes one day. Gives us the necessary cap flexibility that is needed before the season. But the 2017 Chiefs absolutely got worse yesterday, as the WR depth and experience took a big hit.

beach tribe · 06-03-2017, 10:38 AM

Quote:

Originally Posted by TigerUppercut

I'll continue to root for maclin when he's not playing us because he was a great teammate and helped out the rookies immensely, unfortunately it was the body and mind that let him down. Wish him the best.

There is no us.

When are you going to get that through your head?

**DaneMcCloud** · 06-03-2017, 10:38 AM

Quote:

Originally Posted by Rausch

The texans have both a legit D and a legit CB

Give me a break. Maclin dropped perfectly placed balls in that game, period.

Maclin tried to blame his slump on the loss of his best friend that week but he played like shit the rest of the season.

**DaneMcCloud** · 06-03-2017, 10:39 AM

Quote:

Originally Posted by pugsnotdrugs19

No it isn't. The Chiefs cut a good WR and replaced him with no one, therefore they got worse.

I get the move. Gives the young guys a chance to get experience and prove their worth before they play with Mahomes one day. Gives us the necessary cap flexibility that is needed before the season. But the 2017 Chiefs absolutely got worse yesterday, as the WR depth and experience took a big hit.

Pure and utter speculation

06-02-2017, 05:36 PM
pugsnotdrugs19 SUPER BOWL CHAMPIONS Join Date: Aug 2013 Casino cash: $6639447	Chiefs cut Jeremy Maclin Wow We have released wide receiver Jeremy Maclin. ➡️ https://t.co/xVXKqOhP3g pic.twitter.com/Gulky5JiAF — Kansas City Chiefs (@Chiefs) June 2, 2017 The release of Maclin clears $10 million cap space since he was a post June 1 cut. — Terez A. Paylor (@TerezPaylor) June 2, 2017 Last edited by pugsnotdrugs19; 06-02-2017 at 05:42 PM..
Posts: 29,037

06-03-2017, 10:20 AM	#498
pugsnotdrugs19 SUPER BOWL CHAMPIONS Join Date: Aug 2013 Casino cash: $6639447	One thing that has always been a pet peeve of mine is the thinking that teams can just double team player X, and player Y, etc. and be just fine. It doesn't work that way. You can only truly double team one guy. If you play single high and roll a safety up to bracket Kelce, you're taking the odds that your corners can handle the sidelines to themselves. And maybe they can, that probably depends on the personnel. Unless the single high safety has elite range, teams are not counting on him to cover from sideline to sideline. If you are playing two high, you will more than likely account for the deep parts of the field (though the Reek TD vs. Oakland and the famous wide open GIF vs. PIT came against two high shells). However, you are leaving Kelce to be covered by linebackers or slot CBs, and that typically hasn't worked well for defenses. My point is, the situation isn't near as dire as some would make it seem. Did our offense get worse losing Maclin? Yes. But long term, this will benefit us most as we head into the Mahomes era, and hopefully see that Robinson, Conley, or Chesson have legit ability.
Posts: 29,037

06-03-2017, 10:34 AM	#503
keg in kc oxymoron Join Date: Feb 2001 Location: OP/KC/Whatever Casino cash: $9556299	WR production often has more to do with QB than it does with WR. There aren't really that many Calvin Johnson calibre receivers out there. That's why teams like Pittsburgh, New Orleans, New England and even San Diego have managed to excel consistently for years on offense regardless of who they put on the field on the outside. That said, this is still a bit of a head-scratcher.
Posts: 58,682