Forcing an unearned run

[kunimura]

Is there a way to force runs to be unearned?

Here is the situation:

Beginning of the inning
-No outs
-Able walks
-Baker reaches base fielders choice on ball hit to 3rd. The throw goes to second in an attempt to put out Able but the throw is high. Able is safe at second and goes to third on the error. Baker advances to 2nd on the error.
-Charlie hits a home run

(What follows is irrelevant since Able's run should be unearned but the program forces it to be an earned run.)

Can I force that run to be unearned?

Also, is there any functionality to assign a run as earned to the pitcher but it would be a team unearned run?

Thanks.

[OhioTex]

FTM has said future release ( no time table given) will Give scorer more flexibility on assigning/ unassigning earned and unearned runs and over ruling auto assignments.

Until then you can play with assigning errors on throw or having runner go hom on error. All forceing stats like you want before Charlie hr.

[FTMSupport]

What OhioTex said is correct, and will help your issue, but there is a little more to this particular situation.

What we really need is to be able to distinguish between "Safe BECAUSE of Error" vs "Safe ON Error". There is a subtle distinction, but it changes the way earned runs are calculated. If a runner is safe BECAUSE of an error (i.e. they should have been out, but they were safe because the error occurred), then they should never be considered an earned run. If a runner advances ON an error (e.g. Right Fielder fumbles a ball or misses a cutoff man etc, thus allowing a runner to advance to third instead of staying at second), then the runner is still eligible to be earned. We currently always treat Batters making it to base as "because of", and runners advancing bases as "on the error". In a future release, we will allow selecting one or the other, and do ERA calculations accordingly.

[kunimura]

Thanks. Looking forward to the revision.

One solution may be to have a prompt that allows the scorer assign the run as earned or unearned when the run is plated. Granted, this may not be known until the 1/2 inning is over, but it would allow one to go to the pitch-by-pitch and modify after the fact. Having been an official scorer for a minor league team for over 10 years, there are just some calls that are easier done manually as opposed through a computer system.

Thanks again.

[kunimura]

One more item that I would recommend that be asked via a prompt would be whether the run be credited as an RBI.

Thanks.

[FTMSupport]

Do you have a case where we are not getting the RBI correct? That calculation is more straightforward than earned vs unearned run.

[jcbeckman]

And hopefully all these new prompts will be optional - for me the current defaults are working fine.

[FTMSupport]

We are not planning on creating new prompts... on the screen where you enter how runners advanced, there will be a new button in addition to just the "Error"... one will be for "BECAUSE OF error", and one will be "ON THE error". We do not know what the labels will be, but it will be no extra work when entering the plays.

[kunimura]

On the RBI, I was thinking of rule 10.04.c but after experimenting with the software, I can see how that is handled. So, nothing to report there.

Great software, just need to become more familiar and comfortable with it.

[marshall.caldwell]

According to 10.16 d, if the runner would not have made it into scoring position without the error' then the run should not be earned. I have a situation where the runner reached on BB (earned run elidgable), but reached 3rd on an error, then scored on a single. Then double play to end inning. The runner would never have scored from first on the single, so according to 10.16d, the run should not have been earned.