http://iscoresports.com/

On one of our forums, we got into a baseball discussion regarding relievers and earned runs. A scenario is provided below. After we discussed, someone pointed us to rule 10.16 of the MLB rules that confirmed it. After we found the answer, I ran it through iScore, and it looks like it's coming up with an incorrect result. Here's the scenario:

Pitcher A starts the inning.

Batter 1 singles
Batter 2 strikes out (1 out)
Batter 3 reaches on an error, Batter 1 goes to second
Batter 4 singles, scoring Batter 1, Batter 3 goes to third
Batter 5 strikes out (2 out)

Pitcher B replaces Pitcher A

Batter 6 walks, loading the bases
Batter 7 walks, forcing in a run, bases still loaded
Batter 8 homers, grand slam

iScore scores this as:
Pitcher A - 1 ER
Pitcher B - 3 ER

Pitcher B is correct because of rule 10.16. For Pitcher A, in the scenario above the error caused Batter 1 to move to second. If not for the error, he wouldn't be in scoring position when Batter 4 singled. Pitcher A shouldn't be charged with an ER, should he?

I think it should be:
Pitcher A - 0 ER
Pitcher B - 3 ER
Team Total - 0 ER

just reading what you describe.. And not seeing in person.. It would seem iscore logic is sound. I would have gone with iscore view of 1 earned run for pitcher A.

As described, you did not specifiy Batter 1 advance to second due to an error.. So iscore would have to assume you had a scenerio, where batter 3 reaches first due to error and batter 1 would have made it to second had there been errorless play. (this is quite plausible scenerio. simple example, hit and run, slow ground ball to third, only play is at first, but wild throw by third basemen lets runner reach, score it e5..) then single scores and an earned run

If you disagree with iscore, you can override the earned run in stats

FTMSupport wrote:You can edit the stats directly by going to Game Manager, selecting the game, selecting Pitching Stats, then tap the ER value for the pitcher and reduce the earned runs by one. iScore will get earned runs correct most of the time, but there will be occasions where scorekeeper's judgment may be involved where iScore can not get it correct, and this manual override allows you to account for that.