Erik Karlsson - D

[Bruyns]

You’re right not sure why I assumed both leagues did. Surprised we don’t have more ppl pushing for it in that league too.

[Shoalzie]

ADHL doesn't have it.

[TheNudge]

Have you seen the detail of that Kane trade?

The Blackhawks retained 50 percent of Kane's remaining pro-rated salary cap charge, and the Coyotes made the cap math work for the Rangers by joining the trade as a third team and retaining 25 percent.

I decided to post under this thread since retention was a major topic of conversation.

If we decide to give the green light for the retention idea next year. I think following the nhl and being able to add a third team for cap purposes is quite interesting. Would it be to task demanding for the person in charge would be the main issue? Any thoughts on this matter ?

[Florida Chris]

Have you seen the detail of that Kane trade?

The Blackhawks retained 50 percent of Kane's remaining pro-rated salary cap charge, and the Coyotes made the cap math work for the Rangers by joining the trade as a third team and retaining 25 percent.

I decided to post under this thread since retention was a major topic of conversation.

If we decide to give the green light for the retention idea next year. I think following the nhl and being able to add a third team for cap purposes is quite interesting. Would it be to task demanding for the person in charge would be the main issue? Any thoughts on this matter ?

It would certainly increase activity, and likely increase the amount of time needed for bottom teams to turn around their roster, as they could now use cap space as a asset.

[Shoalzie]

Retention is very doable but I think the issue with some GMs is the idea of having salary retention for too many years into the future. The idea of only allowing salary retention on contracts with 2 or less years remaining is easier to manage.

On my side of things with Google, I can implement it pretty much any way you want. I use the CapFriendly salary figures in what we do but I can also set custom values for any player. I can create a separate asset that would be just for salary retention so they'd go towards a team's cap.

Can we do it? Absolutely.

Do we have enough support to do it? That still seems to be up for debate.

[KapG]

I’m ok with salary retention these days I think as long as there is only a year or two left on the deal. Gotta keep it simple though

[TheNudge]

Retention is very doable but I think the issue with some GMs is the idea of having salary retention for too many years into the future. The idea of only allowing salary retention on contracts with 2 or less years remaining is easier to manage.

On my side of things with Google, I can implement it pretty much any way you want. I use the CapFriendly salary figures in what we do but I can also set custom values for any player. I can create a separate asset that would be just for salary retention so they'd go towards a team's cap.

Can we do it? Absolutely.

Do we have enough support to do it? That still seems to be up for debate.

I would definitely back the idea of making the retention a maximum of two years. Now the main question would the second idea make things too complicated (potential of adding a team to make the cap work like Zona did)? I know some of you previously said that you didn’t want any player’s to be retained to a greater % of 50%. The main issue with this idea is the lenght of the contract retaining. Suck to say this but I think this idea is a great idea but for the contracts that are expiring. Maybe make it a clause in the retention by allowing a maximum of a three team cap retention only for expiring contracts.

[Shoalzie]

I'd prefer we simplify the system as much as possible:

1. Set a limit of the number of years remaining on the deal (2 years seems to be the consensus)

2. Limit the number of times salary can be retained on a player (Preferably twice; first deal being 50%/50% split and a second deal being 25%/25% split of the remaining 50%).

I'd prefer we don't get too cute with the percentage of salary retained but not I'm saying custom percentages is a lot of work on my end.

[TheNudge]

I'd prefer we simplify the system as much as possible:

1. Set a limit of the number of years remaining on the deal (2 years seems to be the consensus)

2. Limit the number of times salary can be retained on a player (Preferably twice; first deal being 50%/50% split and a second deal being 25%/25% split of the remaining 50%).

I'd prefer we don't get too cute with the percentage of salary retained but not I'm saying custom percentages is a lot of work on my end.

Would you want to limit gm’s on the number of retention one is allowed?

[Shoalzie]

In the NHL CBA, they limit 3 contract retentions per season. That seems more than reasonable to me.

You don't want it to get out of control. If we limit it to 2 years remaining, when one contract expires, that becomes an opportunity to retain salary on a different player next season.

[Handsome&FairMike]

I'd prefer we simplify the system as much as possible:

1. Set a limit of the number of years remaining on the deal (2 years seems to be the consensus)

2. Limit the number of times salary can be retained on a player (Preferably twice; first deal being 50%/50% split and a second deal being 25%/25% split of the remaining 50%).

I'd prefer we don't get too cute with the percentage of salary retained but not I'm saying custom percentages is a lot of work on my end.

I'd be for this idea. Probably would suggest simplifying it to only 1 team retaining, but if you think you can handle it on the spreadsheet Scott, I'll let you guide the level of complexity.

[Matthew]

I'd even say keep It to only 1 or 2 retainments to begin with as a test run. We could end up with so so many absolutely abysmal teams.

I'd prefer a conservative approach to begin with and possibly open it to full nhl rules later on. We've had a pretty great league here for years. The pandemic has slowed trading down but that itself will be solved in the next year or two as the cap begins to rise.

[Welchie5]

I'm on board with implementing some cap retainment. I agree with Matthew, might be best to start simple - test the waters a bit - and then scale up if we find it is a) successful and b) not overly cumbersome on the back end

[TheNudge]

I like limiting the number of retention and I personally would set the max per team to 3.

[Florida Chris]

I'd prefer we simplify the system as much as possible:

1. Set a limit of the number of years remaining on the deal (2 years seems to be the consensus)

2. Limit the number of times salary can be retained on a player (Preferably twice; first deal being 50%/50% split and a second deal being 25%/25% split of the remaining 50%).

I'd prefer we don't get too cute with the percentage of salary retained but not I'm saying custom percentages is a lot of work on my end.

This with a limit 2-3 contract retentions per season looks pretty awesome. As a result though, the tradeoff, maybe should be stricter rules on not hitting games played.

[KapG]

I'd prefer we simplify the system as much as possible:

1. Set a limit of the number of years remaining on the deal (2 years seems to be the consensus)

2. Limit the number of times salary can be retained on a player (Preferably twice; first deal being 50%/50% split and a second deal being 25%/25% split of the remaining 50%).

I'd prefer we don't get too cute with the percentage of salary retained but not I'm saying custom percentages is a lot of work on my end.

This with a limit 2-3 contract retentions per season looks pretty awesome. As a result though, the tradeoff, maybe should be stricter rules on not hitting games played.

Was talking with thom about the games played thing while playing some Warzone the other day. You don’t want to penalize the rebuilding teams too much because there is no way to get talen but draft and trade in our league, but dropping one spot in the draft is a bit of a slap on the wrist.

[DApolloS]

I'm on board with implementing some cap retainment. I agree with Matthew, might be best to start simple - test the waters a bit - and then scale up if we find it is a) successful and b) not overly cumbersome on the back end

If we start slow, I'd say implement 1 year max retention (expiring contracts) and max of 2 contracts. Do that for 1 season and see if it helps movement. And then go to phase 2 the following year, max 2 years, 2 or 3 contracts.

[Bruyns]

I'm on board with implementing some cap retainment. I agree with Matthew, might be best to start simple - test the waters a bit - and then scale up if we find it is a) successful and b) not overly cumbersome on the back end

If we start slow, I'd say implement 1 year max retention (expiring contracts) and max of 2 contracts. Do that for 1 season and see if it helps movement. And then go to phase 2 the following year, max 2 years, 2 or 3 contracts.

I agree, I think one season test run to see if it accomplishes what we are looking for makes sense

[DApolloS]

I'm on board with implementing some cap retainment. I agree with Matthew, might be best to start simple - test the waters a bit - and then scale up if we find it is a) successful and b) not overly cumbersome on the back end

If we start slow, I'd say implement 1 year max retention (expiring contracts) and max of 2 contracts. Do that for 1 season and see if it helps movement. And then go to phase 2 the following year, max 2 years, 2 or 3 contracts.

I agree, I think one season test run to see if it accomplishes what we are looking for makes sense

And also to see if The people who have to do the work behind the scenes don't mind doing it.