Matrix Games Forums

Running 1.16 Beta, Multiplayer, with all teams human-controlled. When I first started this assn., I went to each team's Manager/GM Tendencies Settings and gave every team the same tendencies in all areas. This is my preferred method of sim.

Halfway through the current season, I noticed that home run totals were way down (the 1976 White Sox had 10 team homers after 80+ games, for example). The league leader at the All-Star break was Yaz with 11.

Just as I was about to consider it a fluke or some new pitch the hitters hadn't caught on to, I decided to check the teams' tendencies. EVERY TEAM's tendencies had been changed by the program, and almost EVERY tendency was different from what I had set them up to be.

I reset each team to my desired settings and played on. I discovered that these changes are taking place whenever I use "Auto Assign Rosters", which I do for each team twice a month. This bug, or whatever, is a recent change to the program and I don't know exactly when it was "introduced". Whatever the case, it needs to go back where it came from soon. This thing totally disrupts the flow of the assn. and causes unnecessary delays every time I make a roster move.

***Doing the same thing with 1.18 Beta***

Hmm, I bet this bug is caused by a "feature" that Shaun introduced in the 1.12 beta patch.

- New: The AI now dynamically adjusts it's GM/Managerial tendencies based on the team's characteristics

A lot of us thought it would make the game more realistic and challenging if the UI recongnized it's strengths and weaknesses and changed it's tendencies as the season progressed.

Seems that Shaun didn't take into consideration a Multiplayer/All Human Association when adding the code. Good catch.

Agreed. This would be a great feature IF I were playing against the computer AI. Playing solo/multiplayer, this new feature only functions as a hurdle.

This should not be occuring for human-controlled teams and I would definately consider it a bug. [:)]  There should be no AI for a human controlled team.  I hope Shaun fixes this one up before the full patch comes out.  Good catch.

This is fixed for 1.19