Count-by-Count stats

[KBLover]

I notice there's a difference between being ahead and behind in the count in game. Of course, that lines up with what we expect.

Does that mean that Control and Eye ratings can help players beyond preventing and taking walks?

Does the game engine generate more ahead/even/behind in the count situations based on how these ratings are interacting with each other?

[Anyone]

Originally Posted by KBLover

I notice there's a difference between being ahead and behind in the count in game. Of course, that lines up with what we expect.

Does that mean that Control and Eye ratings can help players beyond preventing and taking walks?

Does the game engine generate more ahead/even/behind in the count situations based on how these ratings are interacting with each other?

It's been established that when an at bat starts the computer "rolls the dice" and determines its outcome, so it probably simply to mimic real life ahead/behind in the count stats generates a sequence that puts the batter ahead in the count more often when the batter has been decided to have a good outcome to his at bat, and vice versa.

Eye doesn't improve what happens if/when the ball is put in play. Changing it in the editor does not change a player's "expected" batting average or slugging percentage.

I hope that a better eye (and worse avoid K's) generate longer sequences in general, meaning the pitcher has to throw more pitches, but I don't know of anyone who's checked to see one way or the other.