CPU Pitcher Shutout Glitch?

[bfindeisen]

I am curious if anyone else has noticed this...and if it is in fact a hard coding error.

It seems that regardless of the Pitch Count, Pitcher Energy, Confidence, Manager Pull Slider, or Game Situation the CPU Manager will refuse to remove his starter if he hasn't yielded a run yet. I've seen this multiple times, but most recently in a game I played as the Red Sox vs. Yankees. Freddy Garcia pitched a CG shut out, but really should have/would have been removed in the 6th inning due to Pitch Count, Energy, and Game Situation. In the 6th, he was over 100 pitches, had 0 energy, and I continued to threaten offensively by accumulating walks and singles, but just couldn't score. Well, because he had not yielded a run, the CPU let him continue to pitch...to well over 150 pitches, with me continuing to get on base and hit him, but then I would get thrown out at the plate or picked off or struck out. Bottom line: the CPU let the pitcher throw for 4 innings on 0 Energy and well over 120 pitches.

Is this just hard coded that way?

As I'm sure other have pointed out, SCEA really needs to completely revamp the CPU manager decision making. It often makes no sense to do what the CPU does, like bringing in RHPs to face lefties and LHPs to face righties, leaving starters in too long or taking them out too quickly, have no sense of the game situation, not utilizing setup men and closers properly, using no baseball information to make informed decisions about pitching matchups, etc.

[ralphieboy11]

The CPU bullpen logic has been mentioned in previous topics, so the mods may point you there.

I have witnessed this issue with a pitcher being left in too long as well.

I will note it does not always happen with a pitcher that has not given up a run. It seems it only occurs when the team has a decent lead.

I have seen a pitcher pulled with a 1-0 or 2-0 lead, sometimes in the 6th inning. In those instances, I feel like it was a little early. It would be nice if CPU managerial decisions were more customizable than the hard to figure out manager hook slider.

[JG1986]

Quote: Originally Posted by bfindeisen

I am curious if anyone else has noticed this...and if it is in fact a hard coding error. It seems that regardless of the Pitch Count, Pitcher Energy, Confidence, Manager Pull Slider, or Game Situation the CPU Manager will refuse to remove his starter if he hasn't yielded a run yet. I've seen this multiple times, but most recently in a game I played as the Red Sox vs. Yankees. Freddy Garcia pitched a CG shut out, but really should have/would have been removed in the 6th inning due to Pitch Count, Energy, and Game Situation. In the 6th, he was over 100 pitches, had 0 energy, and I continued to threaten offensively by accumulating walks and singles, but just couldn't score. Well, because he had not yielded a run, the CPU let him continue to pitch...to well over 150 pitches, with me continuing to get on base and hit him, but then I would get thrown out at the plate or picked off or struck out. Bottom line: the CPU let the pitcher throw for 4 innings on 0 Energy and well over 120 pitches. Is this just hard coded that way? As I'm sure other have pointed out, SCEA really needs to completely revamp the CPU manager decision making. It often makes no sense to do what the CPU does, like bringing in RHPs to face lefties and LHPs to face righties, leaving starters in too long or taking them out too quickly, have no sense of the game situation, not utilizing setup men and closers properly, using no baseball information to make informed decisions about pitching matchups, etc.

http://www.operationsports.com/forum...anagement.html

Weird, I just posted basically the same thing last night. Tommy Hanson threw 166 pitches, 8 walks, yet I couldn't muster anything against him. He was just as effective at zero energy as he was when he started the game. I would scatter hits in each inning but he would come back with a double play or strikeout, etc.

[nomo17k]

Quote: Originally Posted by ralphieboy11

The CPU bullpen logic has been mentioned in previous topics, so the mods may point you there. I have witnessed this issue with a pitcher being left in too long as well. I will note it does not always happen with a pitcher that has not given up a run. It seems it only occurs when the team has a decent lead. I have seen a pitcher pulled with a 1-0 or 2-0 lead, sometimes in the 6th inning. In those instances, I feel like it was a little early. It would be nice if CPU managerial decisions were more customizable than the hard to figure out manager hook slider.

I think this seems to be the issue. The AI manager leaves the starter in if he has a chance with a decent lead. Probably there should be a pitch count check or something. (though I'm not particularly fond of the recent pitch count craze in MLB...)

[cusefan74]

I was down 7-0 in a game and they pulled their pitcher in the 6th inning after I got a walk and a single. The pitcher was not even close to 100 pitches and had plenty of energy left. So I don't think if they have shutout going that it matters.

[moemoe24]

Seems like I remember in MVP baseball once the pitcher gave up 10 hits he was pulled. I liked that.

[shadia147]

So far in my Franchise, the starting pitching seems about right. But then, I have my settings so that a pitcher rarely goes past 100-110 pitches even in a complete game. I think the most I've seen has been 130, that was an Opening Day shutout 2 hitter by Ricky Romano. Usually in a rout or shutout, my starters get taken out in the eighth or ninth inning. I think thats about right.

[C_Bailey24]

I think the more glaring problem is the cpu pitchers are WAY too effective with 0 energy. I just got shutout in back to back games by Jeremy Guthrie and Chacin. Guthrie threw about 130 pitches and Chacin about 140. With 0 energy you should see a few more meatballs. These guys were still around the black and the corners well into the 9th. 18 scoreless innings all thanks to the overpowered pitcher confidence.