NOTICE: This league is using the BLEEDING EDGE game engine. For more information, click here.

The new user interface is in preview!

Want to check it out? Click here! (If you don't like it, you can still switch back)

League Forums

Main - Community Help Forum

re: priority cuts

By Infinity on Trial
12/05/2015 8:55 am
Is there a way to designate who should be cut first in the event that I end up with too many players on the roster?

A trade I had proposed was accepted while I was asleep at 12:55 a.m., and the result was the computer cut an active second-year CB I was dependent on (both for coverage skills and as an elite PR). IF I can re-sign him, it will cost me a lot more than he was scheduled to make (on top of the penalty for cutting him). This is infuriating.

I had worse players with minimum contracts who were inactive and at positions in abundance, so I'd also like to know how the CPU decides which guy to cut.

Re: re: priority cuts

By setherick
12/05/2015 9:16 am
Infinity on Trial wrote:
Is there a way to designate who should be cut first in the event that I end up with too many players on the roster?

A trade I had proposed was accepted while I was asleep at 12:55 a.m., and the result was the computer cut an active second-year CB I was dependent on (both for coverage skills and as an elite PR). IF I can re-sign him, it will cost me a lot more than he was scheduled to make (on top of the penalty for cutting him). This is infuriating.

I had worse players with minimum contracts who were inactive and at positions in abundance, so I'd also like to know how the CPU decides which guy to cut.


+1 this. I want a cut list. I'm tired of cutting players while crossing my fingers that the FAs I want sign with me.

Re: re: priority cuts

By WarEagle
12/05/2015 1:08 pm
+1

Re: re: priority cuts

By Morbid
12/05/2015 1:30 pm
+1

I know I have had to cut a player before just in case the trade went through before game sim
Last edited at 12/05/2015 1:31 pm

Re: re: priority cuts

By jdavidbakr - Site Admin
12/05/2015 2:27 pm
Added this to the feature request list.