Jump to content
  • Welcome!

    Register and log in easily with Twitter or Google accounts!

    Or simply create a new Huddle account. 

    Members receive fewer ads , access our dark theme, and the ability to join the discussion!

     

There's no way we're carrying 5 RB's on the 53


FuFuLamePoo

Recommended Posts

again you guys are talking cap. im talking his current salary.

cap is due to the signing bonus, that the great marty hernia gave him. yes thats high, but it would have been higher if williams didnt take a pay cut. he reduce his base for 5 million to 1.8.

hes getting 1.8, thats his pay. hes not overpaid.

He is overpaid.

They work on contracts. Nitpicking out a random salary for one given year.....doesn't make him not overpaid.

Cap matters. Them playing with money to get that 1.8 figure is just that. Playing....playing with numbers bc he is overpaid.

They played with numbers.

Link to comment
Share on other sites

hes overcapped, not overpaid. if williams signed a new deal 2 years at 3,600,000, you'd still call that overpaid? a simple yes/no. 

 

cutting or trading, will still result in dead money. 9.6mill this year and 6mill next. might as well ride it given his low base. 

Link to comment
Share on other sites

again you guys are talking cap. im talking his current salary.

cap is due to the signing bonus, that the great marty hernia gave him. yes thats high, but it would have been higher if williams didnt take a pay cut. he reduce his base for 5 million to 1.8.

hes getting 1.8, thats his pay. hes not overpaid.

It doesnt sound like you comprehend how that math works.

Link to comment
Share on other sites

hes overcapped, not overpaid. if williams signed a new deal 2 years at 3,600,000, you'd still call that overpaid? a simple yes/no.

cutting or trading, will still result in dead money. 9.6mill this year and 6mill next. might as well ride it given his low base.

No. A fresh deal like that he wouldn't be overpaid. There is no fresh new deal here however....it is a mess. Cherry picking one number that is purely created for a yearly cap scenario isn't a reflection of what you state it is.....

We have runners with our without Williams. If we can use the 2 mill created in cap space to improve the OL significantly at one spot which lead to a better OL (run and pass).....that makes us a better team IMO. We have plenty of runners. Everyone healthy, Williams is the 4 best overall rush threat.

Link to comment
Share on other sites

Thank you. 

 

there is a mess attached to the 1.8, another term is needed rather than "overpaid". 

 

 

lets say panthers have offered williams a 2 year 3.6mill deal, IF he doesnt sign the panthers are charged 9.6 million in cap money(or 4.8 this yr and next). IF he does sign the deal, panthers have to carry 6mill in cap money this year and next. thats simply the deal. 

 

the 2 million you are reffering to is his current base, thats what is saved. dead money doesnt go away, so cut/trade that 9,6 is still charged to the cap. if june cut, its spilt in two years, its still 9.6 charged but over two years rather than one. so you save 2 mill, but you have to replace him with another contract player. lets just go with the min of 650,000

 

 

650,000(new replacement contract) + 4,800,000(june cut dead money) - 2,000,000(saving form base salary) = 3,450,000 in cap money.

Link to comment
Share on other sites

Thank you.

there is a mess attached to the 1.8, another term is needed rather than "overpaid".

lets say panthers have offered williams a 2 year 3.6mill deal, IF he doesnt sign the panthers are charged 9.6 million in cap money(or 4.8 this yr and next). IF he does sign the deal, panthers have to carry 6mill in cap money this year and next. thats simply the deal.

the 2 million you are reffering to is his current base, thats what is saved. dead money doesnt go away, so cut/trade that 9,6 is still charged to the cap. if june cut, its spilt in two years, its still 9.6 charged but over two years rather than one. so you save 2 mill, but you have to replace him with another contract player. lets just go with the min of 650,000

650,000(new replacement contract) + 4,800,000(june cut dead money) - 2,000,000(saving form base salary) = - 3,450,000 in cap money.

He holds the 8th highest cap figure bc he is overpaid....

He currently has a base salary if 1.8 this one year bc he is so overpaid they played with his contract to survive it.

I am strictly talking cap room. Cut him June 1....you create dead money but the positive is you create 2 mill in cap room. Now with that room you can lose your 4th best rush option and use the space to help add a starting lineman to improve your O. Rush won't take a backseat losing Williams most likely....likely improves with better OL play. All about fielding the best team vs best looking depth chart

For example, Carolina has 15 mil in cap room. Cut Williams as June 1 you have 17 mil in space.....yes you eat money but space is also created to help make a move at a more important and team impactful spot......once that could make the stable of rushers even better and offense as a whole. Cost is merely eating some money and parting with your 4th best rusher.

Link to comment
Share on other sites

dead money is cap money.

 

the june cut saves 2 million, but adds around 5 mill to 2015. plus given the last two years are dummy years that have dead cap money of 2+ mill in 2016 and 1+mill in 2017 no matter what happens. its a unusual contract with the void years at the end, thus you get one year of +2, then three straight years of minus/negative money. 

 

its pro/con deal thats somewhat even on both sides. if you cut him, -/+8mill is spread out starting 2015-2017 in lost cap space. plus you have to replace him with a player who needs a contract, but at a position of need. OR keep him this year and cut him afterwards(less dead money) OR keep him two years. panthers need all the space with incoming cam/luke/star/kk deals. but biting the bullet now, could have benefits too. i see both sides.

 

 

Link to comment
Share on other sites

dead money is cap money.

the june cut saves 2 million, but adds around 5 mill to 2015. plus given the last two years are dummy years that have dead cap money of 2+ mill in 2016 and 1+mill in 2017 no matter what happens. its a unusual contract with the void years at the end, thus you get one year of +2, then three straight years of minus/negative money.

its pro/con deal thats somewhat even on both sides. if you cut him, -/+8mill is spread out starting 2015-2017 in lost cap space. plus you have to replace him with a player who needs a contract, but at a position of need. OR keep him this year and cut him afterwards(less dead money) OR keep him two years. panthers need all the space with incoming cam/luke/star/kk deals. but biting the bullet now, could have benefits too. i see both sides.

Yes dead money counts against the cap.

But if Williams is cut it still creates cap room.

What is more important....keeping your 4th best rush threat or adding a starting vet rental on the OL (one that improves the ability of your top 3 rushers and pass attack).

The cap room created can be used to make us better despite having dead money along with it. Having all these RBs on the roster is essentially dead money to begin with....they can't be used anyway to justify the cap hits they are taking on the roster

Link to comment
Share on other sites

do the panthers need the 5mill in cap space for 2015?

 

 if the panthers had not drafted either barner or gaffeny would you still want him cut?

 

 

4th best is a hard sell, it been sooo long since stew has shown his skills. cam(could he hold uP?) as a pure RB would be interesting, rather than being a scramble yard getter. toblert is a great all around 3rd down back(long, catching, short yard etc). but theres a case for williams being 4th.

 

i personally think stew is the best(i have since 2009) and would improve mike shulas' credit vastly.

 

 

i see your point of using the 2mill on a position of need. 

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


  • PMH4OWPW7JD2TDGWZKTOYL2T3E.jpg

  • Topics

  • Posts

    • You joke, but it can always be worse. He might walk with a limp or need assistance. Different sport, but Lonzo Ball couldn't even walk up steps a year after his injury.
    • I mean... a lot of the information that could've helped set better expectations has always been out there: There was no RB on the team under contract for the 2025 - 2026 season except for Miles Sanders. The team did not have a second round pick going into the 2025 season due to the trade for Young. Chuba's extension did not happen until the beginning of November. Jonathon Brooks was the clear RB1 in the class with a massive gap between RB1 & RB2. Example: Dane Brugler had Brooks as RB1, overall #48; Blake Corum was RB2, #81 overall. The Giants held pick #47 and had just lost Saquon Barkley to the Eagles in free agency. They were going to take Brooks had the Panthers not jumped in front of them. So if we're framing things with that context: Chuba was expected to be RB1 Miles (at the time) was RB2 Brooks was essentially RB3, stashed for rehab in 2024 with a long runway. The original injury occurred Nov 2023 while the re-injury occurred December 2024. That is right in the high-risk window for recurrence, especially in explosive athletes. The fact that it also happened on a non-contact play suggests possible biomechanical issues such as muscle imbalance, rather than a failed surgery (or bad decision-making).   NFL teams invest heavily in medically vetting prospects. If there had been a clear red flag in imaging or recovery markers, the team is going to find it. This sucks and the Panthers have sucked, yes, but this wasn't blind optimism or malpractice by the front office. It was a calculated decision based on the roster, draft capital, positional scarcity, etc.
    • Yep, but they can all rotate with Brown, Brown and Robinson (sounds like a law firm). Can't continue to have Derrick Brown out there for 90+ percent of the defensive snaps. An injury was bound to happen. 
×
×
  • Create New...