Scoring change

[tblodgett]

With a runner on second base middle of a game, I scored a batter as having an RBI double, scoring the runner, then advancing home on an error on the left fielder. After the game, huddling with the coaches, we decided that it rightfully should be an inside-the-park home run, that the left fielder's play didn't constitute an error. However, going back to the pitch-by-pitch, it won't let me change the scoring of that hit. Well, it will, but only backward, to like a single and an error. Inside the park isn't an option. (I run iScore on a Google tablet, so it's iScore for android). It seems to me when I used to run it on an iPad, I could have made this change without issue. How can I handle this now?

[FTMSupport]

Android and iOS are the same in this regard. You can downgrade a multi base hit into a lower base hit + advance on error, but you can not combine multiple events (hit + error) into a single event (homerun for example).

The easiest thing to do is probably to add a note to the play saying it was a home run, then use stat overrides to credit the player with a home run (and take away the error and double). To do this, go to Game Manager, select the game, select stats, and tap the fields you want to override and type in the new values.

[tblodgett]

Will I need to touch anything, such as a total bases field, or will slugging percentage, fielding percentage, etc. recalculate after the changes?

I would think that would be a pretty good enhancement, as it's not uncommon for errors to be changed into hits, or vice versa, in scoring reversals after games.

[brian_oshea]

This is the one & only time I think that I disagree with FTM. Changing the double + scoring on an error to a home rum does not change the score, does not change the number of runners on base & does not change the batting order or the number of outs. I fail to see why the change cannot be made. Maybe somebody can enlighten me why?

[FTMSupport]

Slugging, total bases, and other calculated fields based on these stats will automatically update.

@brian_oshea - sounds a lot easier than it is. Believe us when we say we would love to allow 100% editing of everything. But even in this seemingly simple case, there is a runner to deal with. The events that were recorded are 1. Batter hits double, 2. Runner scores on that double, 3. Batter advances home on error. So iScore would have to allow combining events 1 and 3 into a single event ignoring event 2 in between. It gets even more complicated when there are more runners in between, and iScore would have to "look ahead" to determine that in order to allow the edits.

[brian_oshea]

I guess no program can be 100% perfect but yours is likely 99.9%. This is likely a small inconvenience to put up with for an excellent program. I guess the moral is be right in the first place. lol

[mprusak]

Actually, the moral is to error on the side of awarding as a hit (a homerun in this case)...leaves you with the ability to correct back to 2B + error.

Although, being right all the time is a good approach too

[fasttina]

Brilliant advice to score on the side of awarding the hit that can be changed to an error later. Thanks so much!