Run allowed on a Passed ball scored as Earned

[TexasRebel]

My ER figures are coming out incorrect, and I've narrowed it down to a few runs due to passed balls being counted as earned when they should stay unearned.

For example, today, 1 out, runners on 2nd and 3rd...

passed ball scores one, advances the other to 3rd
Single scores the other, and leaves runner on 1st
Double play ends the half

iScore counts both runs as earned, when the second, without the passed ball would have been left on 3rd base.

[FTMSupport]

1 out, runners on second and third. iScore would assume that the single would score both runners. For the purposes of determining if a passed ball that allowed a run to score should be earned or not, iScore considers a base hit to score any runners in scoring position (2nd or 3rd base). In the future, we will be allowing you to override that (for example, if it was an infield hit that definitely would have scored 1 of the 2, you would be able to override iScore giving the second run as earned. But for now, we are using the rules of the game, and the best interpretation of the rules we can to determine earned vs unearned. Thank you.

[TexasRebel]

ah, okay.

generally, for earned run calculation, a runner is only assumed to take as many bases as the batter-runner unless he is still on the base paths and shows otherwise. For instance, in this scenario. Since both runners were advanced a base, and had crossed home, the single would only award the 2nd runner 3rd base.

Logically, a base hit scores both RISP, but the benefit of the doubt goes to the defense when calculating the pitchers ERA.

I'll look forward to the option in the update.

[FTMSupport]

Actually, in this specific case, it is scorekeepers judgment according to the official MLB rulebook 10.16(d). Unfortunately iScore can't see the play to make a judgment, so we had to use a general rule as a default, and we chose that RISP would generally score on a base hit. We could have chosen either way, but since RISP implies a hit will score them, we chose that way. When we start allowing overrides, it can truly become a scorekeeper's judgment. Thank you.

[TexasRebel]

ah okay.

I'm scoring by the NCAA rulebook.

[FTMSupport]

Can you give us the reference to the NCAA rulebook that covers this situation? Thank you.

[TexasRebel]

Rule 10 - Scoring

SECTION 22. a. An earned run shall be charged against a pitcher when
a runner scores because of a safe hit, sacrifice hit, sacrifice fly, stolen
base, putout, fielder’s choice, base on balls, hit batter, balk or wild pitch
(even when the wild pitch is a third strike), provided that in each case
it is before the defensive team has had an opportunity to make a third
putout.
Note: In determining earned runs, the scorer shall reconstruct the inning as
if there were no errors or passed balls. Give the pitcher the benefit of the
doubt in determining the advancement of runners, had the defensive team
been errorless.


I cannot find mention of any more than this, but in the years I've followed scores of NCAA ball, no bases were ever awarded more than the farthest traveling runner... Maybe it's coincidence, maybe just agreed upon by the league's official scorers... there is no telling.

For instance, Situation: Runner on 2nd, 0 outs. Two passed balls score the runner on 2nd, and then:

A) a single with a runner on second, would move the runner to third in the reconstruction.

B) a walk and then a single where the runner on first moves to third would award the runner on 2nd two bases in the reconstruction also... (it has to as there would be nowhere for the runner on first to go otherwise)...


anyway. I look forward to the option. The more versitile a program like this is, the more it can cover! I'm still learning the tricks to this gizmo, and loving it.

[FTMSupport]

Sounds very similar to the MLB rule, but would still be a judgment call that iScore would not be able to determine. If it was a long single, the scorekeeper would be able to determine if the runner from second would have scored. If it is an infield single, then the runner probably would not score. Still involves a judgment call that iScore can not make. We agree giving the option to the scorekeeper will be a nice addition. Thank you for posting the rule.