SalarySwishSalarySwish
Avatar

AGKH123

Member Since
Feb. 24, 2020
Forum Posts
5
Posts per Day
0.0
Forum: Trade Machine ProposalsOct. 1, 2020 at 12:35 p.m.
<div class="quote"><div class="quote_t">Quoting: <b>Flavortown</b></div><div>Is that link supposed to be an example of Kesler being on LTIR and his cap hit not counting... because it still does. lol.

I don't think you understand how it actually works, but that's okay.

There's a reason why Ottawa took on Gaborik and Callahan's contracts. Its because once placed on LTIR ,their cap hits still count, yet they only have to pay a fraction of the salary with insurance paying the rest. Thats how they got the the league lower limit of $60.2M and actually spending only somewhere around $45M.

Teams like Toronto utilized LTIR contracts like because its gave them flexibility and allowed them to exceed the upper limit of $81.5M because of accruable cap space. Heres an explanation of what Toronto did last year by Frank Seravalli...

"But the Leafs actual full-season cap hits still amounted to north of $95 million, well above the $81.5 million cap.

A big reason why the Maple Leafs were able to remain cap compliant was the long-term injury flexibility provided by Horton’s ($5.3 million) and Clarkson’s ($5.25 million) cap hits.

By inching as close to the $81.5 million cap as possible, the Leafs were then allowed to exceed the cap by an amount equal to the nearly the full combined $10.55 million cap hits of those two long-injured players."</div></div>

It literally doesnt count against the upper limit of the cap? like I do not get how you dont understand that at this point, its either stupidity, ignorance or both

Keslers cap will not count against the Ducks upper limit this season or next unless he is deemed fit to play (which is pretty much impossible at this point)

The Ducks could go out and sign someone at a 6M AAV if they wanted and not need to trade any cap to make it fit. Keslers would move to the LTIR and essentially negate it. It doesnt actually remove it and he still gets paid but it wouldnt count against the upper limit should the Ducks exceed that
Forum: Trade Machine ProposalsOct. 1, 2020 at 11:54 a.m.
<div class="quote"><div class="quote_t">Quoting: <b>Flavortown</b></div><div>You should go to the CBA drop down menu and click on LTIR FAQ.

"When a player is placed on LTIR, their cap hit remains on the teams cap payroll and it continues to count as it always did. It also does not provide the club with additional cap-space savings that can be banked for future use while the team operates above the salary cap. Instead, LTIR provides relief if the club's averaged club salary, or payroll, begins to exceed the upper limit."

Furthermore, if you go to Anaheim's page, Capfriendly already has Kesler on LTIR and look at their current project cap space.... $470,001. But you do you man.</div></div>

You really are thick headed. LTIR has always removed the cap hit, it doesnt get rid of the money but it doesnt get used against the cap, Kesler has him on the regular IR where that hit still counts, not on the LTIR

Go make a ducks ACGM and put Kesler on the LTIR, his cap hit is essentially removed. It really isnt that hard to understand and look at past examples for proof (Clarkson, Horton, Robidas, etc)

Read past the first two lines of that page. Im not saying Keslers cap hit might be essentially ignored I am flat out telling you with 100% certainty if he is placed on the LTIR his cap hit doesnt affect the Ducks and they will have cap space.

The cap space isnt accounted for until it is needed, which is why it isnt appearing as of now, because they havent exceeded the upper limit, once they do Keslers cap hit will be removed

<a href="https://www.capfriendly.com/armchair-gm/team/1968560">https://www.capfriendly.com/armchair-gm/team/1968560</a>

I know what I am talking about, whereas you clearly do not and need to actually do research before you make your self look like even more of an idiot
Forum: Trade Machine ProposalsOct. 1, 2020 at 8:20 a.m.
Forum: Armchair-GMSep. 28, 2020 at 11:09 a.m.