Page 1 of 1

Courtesy Runner Issue

Posted: Mon Jun 27, 2011 9:52 am
by johnemc
I had an issue using a courtesy runner recently. In Pitch by Pitch the courtesy runner showed up as batting the next time the original batter came up.

Here's what happened: The team had nine players batting and all had batted at least once. In a later inning, the catcher was up and singled. A courtesy runner was put in (tapped runner on first, tapped Courtesy Runner, selected player from the bench). The courtesy runner eventually scored. After a few batters, the player who was courtesy runner substituted in to bat for a different player (I substituted by tapping the batter, then selected the same bench player). He reached on an error and eventually scored.

Then, the catcher came back up to bat (yeah, it was a long half inning). On the scoring screen (iPhone), the catcher's number showed for the batter, so all seemed fine. The catcher popped up and the inning was over.

When I reviewed the Pitch by Pitch after the game, however, it showed that the courtesy runner was the one who popped up rather than the catcher. The stats, though, did record correctly.

I tried to substitute the catcher back in through Pitch by Pitch, but the courtesy runner showed up in the catcher position on defense and was listed twice in the offensive substitution screen.

I also recreated the problem by following the same steps (CR in, CR scores, catcher up 2nd time, pops up for out), but leaving out the part where the CR substitutes in for another batter.

I think what is happening is when a CR comes in to run, he is treated as a substitution behind the scenes and is substituted back out at the beginning of the next half inning rather than after his time on base is complete. So when the batter comes up a second time, the Pitch-by-Pitch still sees the CR as being in.

Since it's unusual, and the stats all seem okay, it's not a critical issue, but it was confusing, so thought I would pass the report on.

Re: Courtesy Runner Issue

Posted: Mon Jun 27, 2011 10:20 am
by FTMSupport
Thank you for reporting this. We will look into it in more detail and get it fixed for a future release.