Huh? Why do you say that?Ngakoue trade means either Hunter is injured worse than they are letting on or Dalvin is gone. Might be both.
I'm guessing he means next year. I think they're wisely reading the tea leaves and aren't going to offer a running back a multi-year contract at $14m+.Huh? Why do you say that?
Real confidence boost.
JMHO, not amazing. His inability to complete a season doesn't merit a new deal, and he has zero leverage.Real confidence boost.
Amazing he doesn't get a deal.
I took Dalvin at 1.12 but got sniped on Mattison. The value at 12 was too good to pass up IMO. Got sniped on Mattison in the 9th, but that was too rich IMO. I had both last year and Mattison got hurt too. Just grabbed Boone as my last pick instead.On the train this year - grabbed him at 1.04 and Mattison in the 9th in my 12 team PPR redraft. I agree that the risk seems a bit lower for him since he has such a good back up.
Yeah, that's fair. He's just grossly underpaid at this moment.JMHO, not amazing. His inability to complete a season doesn't merit a new deal, and he has zero leverage.
As are all elite players working on their rookie contract. It's the way the system is set up.Yeah, that's fair. He's just grossly underpaid at this moment.
Look at why they’re paying Kirk Cousins and enough said. And yes my dumb team tried to pay him more.That's an awful lot of money to give to an injury-prone RB who has only played in 29 of 48 possible NFL games.
Rotoworld:Just signed a 5 year 63M dollar extension
Vikings signed RB Dalvin Cook to a five-year, $63 million extension.
There was talk Cook would hold out this summer but he reported to Vikings camp on time. Cook broke off contract talks with in August. The sides were able to come together to get something done before Week 1. Cook's new deal comes with a $15.5 million signing bonus and his $12.6 million APY makes him the sixth highest paid back ahead of Derrick Henry. He got $2.4 million less annually than Alvin Kamara.
SOURCE: NFL Network
Sep 12, 2020, 12:21 PM ET
A few years from now, 10 other backs will make more. If the Vikes didn't pay him, another team would.That's an awful lot of money to give to an injury-prone RB who has only played in 29 of 48 possible NFL games.
This is fair. Maybe we’re the ones underestimating RBs worth.A few years from now, 10 other backs will make more. If the Vikes didn't pay him, another team would.
Is that a good reason to sign him though?A few years from now, 10 other backs will make more. If the Vikes didn't pay him, another team would.
No, not necessarily a good reason, I'm just stating what would have happened.Is that a good reason to sign him though?
We got a ton of evidence the last several seasons that paying for RB's is a foolish decision. Hell, Kubiak is a part of the staff that began to prove RB's are replaceable. Its like everyone agreed RB's are replaceable, and then a handful of teams said, except for our guy, defeating the entire point.
... and this is wrong somehow? There are some RBs that profile as replacement-level, and some aren't. I see nothing wrong with that statement. If you think you can easily replace Christian McCaffrey or Saquon Barkley's production, go for it. Otherwise you pay them.Is that a good reason to sign him though?
We got a ton of evidence the last several seasons that paying for RB's is a foolish decision. Hell, Kubiak is a part of the staff that began to prove RB's are replaceable. Its like everyone agreed RB's are replaceable, and then a handful of teams said, except for our guy, defeating the entire point.
I mean, yes I think so. Gurley, Johnson, Freeman, and Bell are all very recent examples of extremely productive guys who got paid big money and their teams instantly regretted it. All of those guys (maybe not Freeman) were considered elite RB's at the time. Cook has not proven at all that he is on the level McCaffrey/Barkley are, or where Gurley/Bell were.... and this is wrong somehow? There are some RBs that profile as replacement-level, and some aren't. I see nothing wrong with that statement. If you think you can easily replace Christian McCaffrey or Saquon Barkley's production, go for it. Otherwise you pay them.
The reality is the studies say that any single player outside of a QB has a remarkably small effect on a team's projected win total and is not worth paying big money to. Obviously that isn't a realistic way to run a team but everyone always cherry picks RBs out of those kind of studies when really the studies apply to any non-QB.I mean, yes I think so. Gurley, Johnson, Freeman, and Bell are all very recent examples of extremely productive guys who got paid big money and their teams instantly regretted it. All of those guys (maybe not Freeman) were considered elite RB's at the time. Cook has not proven at all that he is on the level McCaffrey/Barkley are, or where Gurley/Bell were.
I can see the case for paying a truly elite RB, especially one who also catches 80+ passes. I wouldn't, but I can see the case for it. But, Cook is neither of those things.
To end on a positive, I will say Cook was more deserving than Joe Mixon or Melvin Gordon.
Who knows how much is guaranteed. Outside of the 15.5 mill signing bonus.That's an awful lot of money to give to an injury-prone RB who has only played in 29 of 48 possible NFL games.
True, but we also don't consistently see rookies(even undrafted ones) just stepping in and being solid starters instantly like we do at RB, and CB's usually aren't on their way out at 27.The reality is the studies say that any single player outside of a QB has a remarkably small effect on a team's projected win total and is not worth paying big money to. Obviously that isn't a realistic way to run a team but everyone always cherry picks RBs out of those kind of studies when really the studies apply to any non-QB.
Yes we've had 4 straight big money RB contracts that worked out poorly for the teams that signed them. That is the thing about a sample size of 4. A few years back we had like 6 in a row with CB's getting huge deals and then turning into complete trash but teams still dole out huge money to CBs.
Prior to these recent 4 we had a ton of RBs that played at elite levels into their late 20's. We're coming off the weakest group of late 20's RBs in modern NFL history here (remember all these guys that are in their mid-late 20's now are the guys who were young when 19 of the first 24 picks in dynasty startup drafts were WRs because there were so few good young RBs in the league at the time), so I'm not sure I would necessarily apply their performance at age 25+ going forward too strictly.
It's not just Gurley, Johnson, Freeman, and Bell. Don't forget McKinnon's 4 year, $30M contract with SF.FreeBaGeL said:Yes we've had 4 straight big money RB contracts that worked out poorly for the teams that signed them. That is the thing about a sample size of 4.
Yes, all positions pale in comparison to QB in terms of impact on the game. But those other positions still can be reasonably ranked relative to each other, in terms of impact and thus priority of investment. I would say RB should be ranked higher than PK, P, LS, and FB, for those teams that care about FB. Beyond that, I'm not sure I would rank RB higher than any other position. Are you saying you disagree with that?FreeBaGeL said:The reality is the studies say that any single player outside of a QB has a remarkably small effect on a team's projected win total and is not worth paying big money to. Obviously that isn't a realistic way to run a team but everyone always cherry picks RBs out of those kind of studies when really the studies apply to any non-QB.
I was referencing some articles written on how the different positions affect projected wins and betting lines.Yes, all positions pale in comparison to QB in terms of impact on the game. But those other positions still can be reasonably ranked relative to each other, in terms of impact and thus priority of investment. I would say RB should be ranked higher than PK, P, LS, and FB, for those teams that care about FB. Beyond that, I'm not sure I would rank RB higher than any other position. Are you saying you disagree with that?
Dalvin Cook rushed 12 times for 50 yards and two touchdowns in the Vikings' Week 1 loss to the Packers.
He also bagged a pair of two-point conversions but was a non-factor in the passing game, catching just one pass for a loss of two yards on two targets. Considering the Vikings were getting blown out most of the day, it was a very productive box score for Cook, who just signed his big-money extension Saturday. Cook will be a top-five running back play every week, and that will be no different for Week 2 against the Colts.
- Rotoworld
Dalvin Cook rushed 14 times for 63 yards and a touchdown in the Vikings' Week 2 loss to the Colts, adding two receptions for eight yards.
With the Vikings' offense going off the rails in back-to-back weeks, Cook now has just 29 touches through two games. Cook's rushing efficiency has still been just fine amidst the chaos, a good indicator going forward. Cook's life will just be infinitely more difficult if Kirk Cousins can't get the passing game out of neutral. Cook will be a good bet to reach 15 carries for the first time against the similarly run-heavy Titans in Week 3. Cook should nevertheless be treated as a back-end RB1 until the Vikings get some of this sorted out.
- Rotoworld
They're bad, but I think they'll adjust and get him more involved in the pass game if the blowout losses continue.I'm worried. The Vikings look to be horrible. And he isn't being used in the passing game despite being down so much.
Hope you are correct because there is very little chance that the Vikings can roll with a balanced O including a run game. The Vikes are not going to have leads in many games this season.They're bad, but I think they'll adjust and get him more involved in the pass game if the blowout losses continue.
The offense has two legit weapons - Cook and Thielen. They have two (Irv and Jefferson) that could develop into one, but they aren't there yet. The rest are role players, at best. They're going to feed their best play makers, regardless of the count. This serves as a good reality check week for the coaches, that this team is not good and how they approached the first two games isn't going to work with this particular group. Cook owners are probably not going to get their ROI, but he will continue to be startable even if this offense continues to suck out loud.Hope you are correct because there is very little chance that the Vikings can roll with a balanced O including a run game. The Vikes are not going to have leads in many games this season.
Mattison called, he feels a tad disrespected.The offense has two legit weapons - Cook and Thielen. They have two (Irv and Jefferson) that could develop into one, but they aren't there yet. The rest are role players, at best. They're going to feed their best play makers, regardless of the count. This serves as a good reality check week for the coaches, that this team is not good and how they approached the first two games isn't going to work with this particular group. Cook owners are probably not going to get their ROI, but he will continue to be startable even if this offense continues to suck out loud.
What @Tanner9919 pointed out about their schedule along with this makes me worried because their D has looked brutal! I don't understand why he is not more involved - any insights from Vikings fans?I'm worried. The Vikings look to be horrible. And he isn't being used in the passing game despite being down so much.
If something were to happen to Cook then Mattison gets that workload, but til then I think what we've seen is what we're gonna get outta him.Mattison called, he feels a tad disrespected.
Maybe they should put Mattison and Cook on the field at the same time.If something were to happen to Cook then Mattison gets that workload, but til then I think what we've seen is what we're gonna get outta him.
Unless they WANT to lose. Perhaps they are playing for a future top draft pick.Maybe they should put Mattison and Cook on the field at the same time.
They should, but for what are likely silly reasons many NFL staffs don't use 2 backs in that manner even when they have complimentary...**ahem**...'talent' like the Vikings. Logic and NFL decision making often don't go hand-in-hand.Maybe they should put Mattison and Cook on the field at the same time.
Because of giving up safeties in both games as well as interceptions and just plain sucking and going 3 and out the Vikings have barely had the ball on offense.What @Tanner9919 pointed out about their schedule along with this makes me worried because their D has looked brutal! I don't understand why he is not more involved - any insights from Vikings fans?
What would be the benefit of doing that?Maybe they should put Mattison and Cook on the field at the same time.
Fantasy stats for our players, of course.What would be the benefit of doing that?
Get some playmakers on the field. I would try something if I was the Vikings. That doesn’t help the horrible D but they are only going to win games by scoring a lot of points. The D isn’t winning games for Minnesota.What would be the benefit of doing that?
The only problem with this is that their line and run blocking is horrible. Playing a 2nd RB most likely exacerbated the problem. The Vikings are a mess, but Dalvin will be fine. The rest of the offensive fantasy relevant players (Thielen, Jefferson, Smith) I’m not so sure about.Get some playmakers on the field. I would try something if I was the Vikings. That doesn’t help the horrible D but they are only going to win games by scoring a lot of points. The D isn’t winning games for Minnesota.
I’m a Cook owner and don’t follow the Vikings but they need to score points since the D isn’t winning games. I would use Cook or Mattison as a WR of some sort. The Vikes can continue what they are doing and keep losing as well. I don’t care as long as a Cook gets FF points.The only problem with this is that their line and run blocking is horrible. Playing a 2nd RB most likely exacerbated the problem. The Vikings are a mess, but Dalvin will be fine. The rest of the offensive fantasy relevant players (Thielen, Jefferson, Smith) I’m not so sure about.