I haven't been playing for very long in my league yet, but I've noticed the same thing on my minor league team. I started by managing my Rookie League team so I set my fatigue to Very Low, not wanting my pitchers to throw a lot of pitches plus get my relievers some time. My starters are almost always throwing complete games with pitch counts of 130+ or at least going deep into games with pitch counts that are way too high. This is with starters that have endurance ratings ranging from 84 down to 56 (1-100 scale). I finally had to set pitch counts for all my starters just so I could get my relievers into some games. This worked fine for me until the AI decided to change my entire pitching staff (but that is a problem for another post).
I do have a problem with using pitch counts on my starters to reduce the number of pitches thrown. If my pitcher is throwing a great game (no-hitter, shutout, etc.), I would be more willing to leave a guy in the game, but setting a pitch count means he will come out once he reached his pitch count no matter what the situation. The fatigue setting needs to have more of an effect on the number of pitches thrown. I don't think it should be a set number of pitches, but at least a guideline to use, something along the lines of:
Very Low - 80
Low - 95
Normal - 110
High - 125
Very High - 140+
These numbers could be used along with a pitcher's personal endurance setting to determine approximately how many pitches he should be good for each game. Then the AI will just need to evaluate how the pitcher is throwing throughout the game to determine whether he stays in the game past his approximate pitch count or comes out before it.
EDIT: This league was started following the initial release of 2006.
|