http://iscoresports.com/

I've had a weird issue happen twice now in our last two games. Some time in the middle of the game, I notice that the player that iScore says is up to bat is actually not the actual player. In both cases where I have seen this, it lists a player that I had previously marked as not batting in the pre-game lineup as the batter. Not knowing what to do in the middle of the game I just kept scoring, and in both cases when I looked at the stats at the end of the game everything was ok. The batter that was never supposed to be at-bat had no batting stats, and the player that did actually bat had the correct stats, even though when I was scoring it listed the wrong name for the player who was up to bat. There were no other out of order batters or strangeness during the scoring other than this weirdness.

What may be related to this is that in both cases I had preset the lineup before the game started which included a player that was supposed to play. I put him in the batting order and preset his field positions. Then, just as the game was about to begin, the other coach said the player was a no-show. So I simply moved the kid to the bottom of the batting order and marked him as not batting. I did not however change his preset fielding positions since I had no idea what the other coach was going to do because of the no-show. I made all these changes before I pressed "Play!" and began scoring the game. Perhaps iScore is getting confused because of this (a player who doesn't hit but does substitute in the field)?

I am using an iPad with the latest 3.52 (3.51.106) software.

Thanks!

The preset fielders would put the players in the fielding positions, but it would not change the batting lineup (offense and defense are tracked separately as many youth leagues allow you to have players bat that are not in the field and vice versa).

If you can give us steps to reproduce this issue, we would like to see it. If the stats came out correct, then we are probably not going to be able to use your existing game data to see the issue because it sounds like things are correct. But if you have a list of steps we can do to see this same issue, we would like to reproduce it.