So, I’ve done alot of simming with franchise since I got the game. Trying multiple different scenarios, rosters, settings and at least 10 seasons with at least 12 teams. Just really wanted to dive in under the hood and get a grasp on how everything works. One of the big selling points of this years game was the improved roster logic by the CPU. While yes there are some improvements like more balanced overalls and potentials for players, there still a lot that needs work. So through my various testing, the opening day live roster finally highlighted what to me is the biggest problem with trade logic in the game.
The biggest problem is positional balance, and the CPU prioritizing that above all else including potential and overall which should not be the case. The first few live rosters offered more positional balance, but the opening day live update adjusted players to the position they are currently listed at in real life. So what you now have is some teams being loaded at certain positions, and super thin at others. I will use the cardinals as an example. On the OD update they have 3 players listed as first baseman, and like 8 or 9 listed at shortstop. This in itself is not a problem. Players have secondary positions for a reason. Teams in real life play players at their secondary position all the time in real life so that they can get someone in the lineup who is blocked. I will use the cardinals as an example again. Nolan Gorman is a second baseman, but is a guy who came up projected as a third baseman, and would probably benefit from a move back into a position where his abilities profile better. But since the cardinals have a really good third baseman they play him at second. The problem with the CPU logic is that they completely disregard positional versatility.
So the cardinals have 3 “official” first baseman. Nevermind the fact that they also have other players that can play first base, they see that they only have 3 first baseman and panic. It’s the reason why you’ll see trades like JJ wetherholt a consensus top 30 prospect at shortstop getting traded for a C potential first baseman. In real life teams aren’t going to trade their top prospect at a loaded position just so they can have a guy at triple A who’s primary position is first base. Thats because real organizations value talent over position 9 times out of 10 and will often move guys to different positions to simulate balance in their lineup. The problem is the CPU does not have the ability to change a players primary position like the human user does. The CPU prioritizes roster balance over talent and is often why you see some of the wacky moves that happen.
What I’d like to see SDS do is possibly implement the ability for the CPU to change players positions based on fit, or even do what FIFA does. You lock a players positions based at the start of franchise but give the user the ability to “train” a player to a different position, or even add a position to their profile. The better the player fits a positions profile the quicker they can change/add that position to their profile. For instance it would be more difficult to train a 1B at SS, but if you wanted to train a first baseman to play left or right field it might only take a month of training in season.
Just some observations and thoughts I figure I’d post and see what others think
The biggest problem is positional balance, and the CPU prioritizing that above all else including potential and overall which should not be the case. The first few live rosters offered more positional balance, but the opening day live update adjusted players to the position they are currently listed at in real life. So what you now have is some teams being loaded at certain positions, and super thin at others. I will use the cardinals as an example. On the OD update they have 3 players listed as first baseman, and like 8 or 9 listed at shortstop. This in itself is not a problem. Players have secondary positions for a reason. Teams in real life play players at their secondary position all the time in real life so that they can get someone in the lineup who is blocked. I will use the cardinals as an example again. Nolan Gorman is a second baseman, but is a guy who came up projected as a third baseman, and would probably benefit from a move back into a position where his abilities profile better. But since the cardinals have a really good third baseman they play him at second. The problem with the CPU logic is that they completely disregard positional versatility.
So the cardinals have 3 “official” first baseman. Nevermind the fact that they also have other players that can play first base, they see that they only have 3 first baseman and panic. It’s the reason why you’ll see trades like JJ wetherholt a consensus top 30 prospect at shortstop getting traded for a C potential first baseman. In real life teams aren’t going to trade their top prospect at a loaded position just so they can have a guy at triple A who’s primary position is first base. Thats because real organizations value talent over position 9 times out of 10 and will often move guys to different positions to simulate balance in their lineup. The problem is the CPU does not have the ability to change a players primary position like the human user does. The CPU prioritizes roster balance over talent and is often why you see some of the wacky moves that happen.
What I’d like to see SDS do is possibly implement the ability for the CPU to change players positions based on fit, or even do what FIFA does. You lock a players positions based at the start of franchise but give the user the ability to “train” a player to a different position, or even add a position to their profile. The better the player fits a positions profile the quicker they can change/add that position to their profile. For instance it would be more difficult to train a 1B at SS, but if you wanted to train a first baseman to play left or right field it might only take a month of training in season.
Just some observations and thoughts I figure I’d post and see what others think
Comment