RTTS 3-2 count CPU pitching strategy needs work
-
I exclusively play RTTS so I don't know if the CPU pitches differently in other modes. I have usually played at all star hitting difficulty until switching to hall of fame in 2023. What I've noticed in RTTS for both difficulty levels (more so with Hall of Fame) is that the CPU throws too many breaking balls way off the plate in 3-2 counts. For example, there are too many times when I'll be batting with no one on base and the score is like 8-1 (I'm losing), and the CPU will get behind 2-0 or 3-0, throw consecutive strikes to get back to 3-2, and then throw a breaking ball way off the plate. This even happens in all star games and spring training.
I enjoy the challenge of the nastier CPU pitch patterns on the higher difficulty levels but I also think that nastiness needs to align better with the situation. MLB pitchers don't risk walks in exhibitions or when the score is lopsided in meaningful games. If an MLB pitcher wants to pitch around someone, they're not going to waste pitches getting behind, fighting back to even, and then trying to get the hitter to chase way out of the zone on 3-2. They would just intentionally walk or throw 4 straight balls.
Baseball would be a very different game if pitchers routinely threw breaking balls way off the plate in 3-2 counts regardless of the situation. The higher difficulty AI should be smart enough to know when it makes sense to intentionally go out of the zone on 3-2. With first base open in a tight game, it makes sense. With no open base in any game, it doesn't make sense. In spring training and all star games, it doesn't make sense.
This game at higher difficulty levels doesn't reward the player for working deep into the count. It's not reasonable to expect the player to protect against fastballs and account for a breaking ball way out of the zone in every 3-2 count regardless of the situation. I'm okay with a tough pitch in a corner or on the edge, but pitches that aren't even close is taking it too far.
-
Absolutely nailed it with this post.
I feel SDS is running with an AI logic that makes the CPU try to do the opposite of what the general baseball-minded hitter is expecting; which in your example, the general baseball-minded would expect a pitch 3-2 pitch to be in the zone, so if it's throw out of the zone, they will strikeout.
The thing is, if your team is losing 8-1 and the pitcher grooves a pitch down the middle and you smash a 400ft bomb, SDS is worried that the community will say that's too predictable. If they configure it so there is higher chance for pop fly or flyout, they will be worried that the community will say that's unrealistic.
Catch 22, but yes I agree the logic needs a lot of work.
-