Charging two errors / post-game editing

[baystatebaseball]

Here's the situation:

- Bases loaded
- 1 out
- Batter hits a ground ball to short, and the shortstop boots the ball (E6)
- Runner from 3rd scores (RBI for batter)

At this point the shortstop recovers the ball and makes a wild throw to third. The ball flies out of play, and all runners advance one base, scoring another run.

The shortstop committed two errors on this play: the original boot allowing the runner to reach first; and the throw that allowed a second run to score.

When I scored the play as it happened, the resulting stats showed just one error. How do I record two errors when they're committed by the same player? More important, how do I edit the game to fix this after-the-fact?

I've done some playing around, and discovered the following:

- If the second error is committed by another position, it gets properly captured
- I can (in real time) assign an error (the second error) after I "score what I see". This updates the stats. Unfortunately, I didn't do this at the time, and I don't think I'm able to assign an error in post-game editing.

So I have two questions ...

- What's the best way to score this while it's happening?
- Is there any way to correct the stats after-the-fact?

... and a request:

- If there's not a way to assign an error after-the-fact, please add the ability to do so.

Thanks!

[FTMSupport]

When entering a "single play" --- from the time the player hits the ball until the last runner has been accounted for --- any errors assigned to a player will be treated as a single error for stats purposes. This allows you to advance multiple runners and assign all the advancing to that same player. To get a second error on the same player, you would have to enter it as part of a separate sequence, or use the Misc->Assign Error as you found.

We do not currently have a way to add errors after the fact. Our next release (v2.80) will allow you to manually override stats, so you will be able to increase the fielder's errors by 1 when that release is out. We are in final testing of that release now, so it should be out shortly.