My gut feeling is that if the violation is at say LG, may be it's looking to find a LG. In reality, should use player matrix to find other OL capable of playing LG on your roster.

It really shouldn't be doing anything to my roster. I have the minimum or more at every position group. I also have 2 at every position except for SS. I have 1 SS and 3 FSs. So there's really no logic for the computer to be messing with my rosters at all.
I'd like to know what check my roster is failing for the computer to be compelled to intervene. It's odd.

Wait, this story is even funnier. Is "funnier" a word?? Anyway. So as I said, I signed a LG, because the computer has been trying to sign a LG, right? Well, not only did it drop a LG after I signed one... but I just noticed it actually tried to sign another one on the same night. That's insane. Seriously.

Good summary/review of the auto manager function with respect to filling out the roster and ensuring positional coverage, Martin. Whatever the algorithm/code is now, what it was before did not create a problem, and more imporntantly, we had more people playing and paying for MFN that have quit or changed their membership to one team/free as a result of the auto manager problem and several other issues. I was ready to do the same, but decided Ive been here for several years and might as well support JDB and the game by continuing to invest in it with the MVP subscription. 20 bucks a month is not too much to ask to do so, but if it were 40 or more I would not be paying it. Hope is eternal, I think thats how the saying goes, however, my hopes are not too high atm.

The auto manager issue is only in MFN-TEST though; the problem is it's easier to say "not working, this is ****, going to leave" than give feedback.

Part of the problem is that when it was branded MFN-1, people could think "well, yeah, test but also a normal league".

Ideally what the league needs is experienced owners able to give as much detailed information as possible. Exactly what are you seeing, what have you done that may trigger events etc - that feedback is vital to try to narrow down areas that the problem may be in.

What I previously posted wasn't "Hey JDB, do this!" but thought from the top of my head to also show that this isn't an easy thing to a) implement or b) fix. There are so many considerations and factors involved.

The main aim of the overall change is to ensure players fill their rosters in a realistic manner; to avoid tanking by for example having QBs on roster and neither activating nor placing in depth chart. To achieve that it needs to look internally at your roster but also externally, and that's the problem.

I just think the general ethos of owners in MFN-TEST also needs to adjust slightly. Don't treat this as a normal, stable league - view it as a league where your feedback helps improve the game, where feedback is more important than titles. I think the re-branding will help on that score.

My RB's were finally allowed to play. My CB was cut for the fourth straight game sim for another rejected OL contract. I have 10 OL on the roster, I shouldn't need any more. My LDE Jones was also yet again deactivated for an OL, even though I already had 8 active with all positions doubled up and there were no warnings or anything out of the ordinary on the depth chart leading in.

No ST warnings?

My rationale for that is if you only had 8 active OL, didn't fill ST Blockers fully, that could be an issue?

No warnings, another OL signed again

I'm not sure if that happened to me too: 1 SLB released and 1 LDE signed to a 1-year contract. But for now, I've backed up my current roster externally so that I can check during the next sim run whether the AI messed up.

The AI shouldn't be able to take action on its own when GMs are active, unless warnings are ignored.
Warnings occured, but I managed to solve the problems. AI, however, seems to ignore actions be GMs.

It cut my starting LG, I presume because he's out injured for a couple games.
It tried (unsuccessfully) to sign a C. I believe that's also because I have one out injured. Is the computer trying to make sure I have at least 2 healthy, active players at each roster position? That's the only thing that kind of makes any sense. I mean it doesn't make sense if injuries are on... but it makes some kind of sense from a logic viewpoint.

I'd appreciate it if no one signs LG Dominguez, as I would like to pick him back up for his final season with me.

Also, my salary cap is starting to run low and my dead cap for next year is piling up as I keep having to make unexpected roster moves.