Bug - Third out forced on second, runner on third scores?

[Tomy.]

During yesterday's game I ran into this problem. 2 outs, bases loaded. Hit center field strong grounder, ball in play all runners start advancing. Runner on second forced out 8-4 (3rd out inning over) but the program marked the runner from 3rd as scored. It is entirely possible that I marked the 3rd base runner accidentally that way when the program asked (should have hit held up instead of advanced), but it would be great if the program could automatically disregard it or at least notify me that I did something stupid (like when I mark a steal for the same base where the runner is already on). I assume this should be obvious since the 3rd out on 2nd base will end the inning. I had to backpedal at the end of the game and re-score part of the game to correct this.

[FTMSupport]

iScore has not idea what you are going to enter for future runners when you have already entered "In Play" for the batter. If you enter Out for the batter with 2 outs, then we do not score the run, but if you enter "In Play", when it asks about the runner on third, use the "Run Not Scored" button. You could have done this in post game edits as well (go to Game Manager, select the game, select Pitch by Pitch, scroll to the play, tap the pitch, tap Edit next to the event that said the run scored and change to "Run Not Scored").