Quote:
Originally Posted by Pdubya64
That makes me immediately question:
What is it then that the game engine doesn't have or hasn't calculated in order to make it behave this way in the inaugural season?
That seems really odd.  |
My imported roster is running through new code that has different"improved" values(?) for evaluation than the last version. The thought is after the AI has gone through using that particular code once, the second time through will result in fewer moves. IE a lot of players are now, based on the new code, where the code thinks they "should" be.
I posted, as an example, earlier in this thread that in v23 after import, in my first v23 season there were 56 trades in the offseason to spring training window. In my second season there were 29 trades in the same window, with the same settings. It's just what I think happens based on what I see in my game from year to year.
I don't play with the new rosters included but I think there is a similar action with that too. The roster team at OOTP Dev. set 'em up to be as accurate as possible but then the AI takes over and makes it's moves. From what I have read, users there too, think there are fewer moves the second season as the rosters and AI reach a kind of equilibrium (for lack of a better word).