Summary of bug:
The AI does a pretty poor job of handling pitchers. The last game I played Oakland's starter was pitching a good game against me, only giving up 3 runs through 6, and was leading 5-3. In the 7th I started to get to him, and was really hitting some shots. I fully expected him to get pulled, but he was left in to the tune of 6 runs. Six runs. He was approaching his pitch limit too. Regardless of that, in real life he would've been pulled at the first sign of trouble.
Other games I have played the AI seemed to pull pitchers too early. This usually happened in the first or second inning, when I start to get maybe 3-4 runs, and the AI manager would go to the pen without really giving the pitcher a realistic chance to work himself out of it.
So by my own estimation, early on the AI manager is too quick to make a change, and later in the game he is too stubborn. Seems to me like it should be the other way around.
Game Mode you were playing:
This poor management seems to happen pretty frequently, and I've been playing Play Now and MLB Today modes.
What happened to trigger it?
Poorly designed code.
Can you reproduce it? If so, how?:
Pretty much, just play a game.
Video/Picture proof:
None available.

.
. If I am not really careful, sometimes my swing input will linger just long enough after I make contact to influence my baserunners. If I get a hit, and don't notice and correct the mistake, sometimes a guy running to first to beat out the throw will have been directed (by me accidentally) to run to third base. His speed changes because instead of running through the bag he will slow down to make the turn to second base. Or, I can have a man on 2nd and after I hit a deep fly ball, he misses the opportunity to tag up and advance to 3rd because he was already running there. The time that it takes him to stop halfway and run back to tag up has eliminated any chance to be safe should I still send him. I know that I should just be more careful, but it seems that maybe they could shorten the input time for baserunning from being immediately after contact to a half second or a full second. This would allow any lagging input by the user from batting to not cause silly baserunning errors.
Comment