Your postings sound very much like the ramblings of today's politicans or better yet today's journalists. You're only presenting a VERY MINOR part of the story to support your position which leads people who read your postings to a completely wrong conclusion. But that seems to be the way things work these days, eh Ken?
Here's the complete story so that anyone reading this can draw a conclusion based on ALL THE FACTS!
Cook, the LH RP in question pitches 42/3 innings, faces 15 batters, allows 1 hit and strikes out while walking none. The last six batters of the game were ERSTAD, GRUDS, KLESKO, GLAUS, THOME, and SHINJO in that order. 3 good LH hitter, 3 good RH hitters albeit 2 of them are strikeout risks, THOME and GLAUS. (Both of them should be on "hot streak stats" according to their recent major league performances)
Now Cook enters the game with a MAXIMUM BFA OF SIX and the game tied. He continues to the last two innings of the game allowing only 1 hit, striking out 3, and starts those final two innings with a -3, negative 3 BFA. He faces the above named batters in that order and strikes out all six period! Now granted, there is a randomness factor involved with each batter/pitcher situation that allows for differences in major league performance vs. simulation performances. BUT SOMETHING TELLS ME THAT SOMETIMES, AS IN THIS CASE, THAT RANDOMNESS FACTOR APPEARS TO LOCK UP WHEN THE ROBOT IS INVOLVED AND THESE KIND OF LUDICROUS HAPPENINGS RESULT. We call that in IT a "system bug" that can and should be addressed and fixed.
Cook's major league ERA is 4.04 and his 9 inning SO ratio is 6.00 per nine, at least in the majors. Here is SO ratio for the 42/3 IP was was around 18.00 per 9 and of course 27.00 per 9 during the last two innings. The whole point to this presentation is that I'm trying to document a system problem with the random selector process that seems to appear with increasing frequency with robot guided teams and this SERIOUSLY AFFECTS THE OUTCOMES OF OUR GAMES.
END OF STORY.