Batter history bug (?)

[jdonato]

I can confirm that this situation indeed happens. A player was ejected today after 3 AB. Two innings later his substitute came to bat for the first time, and it showed that he was 1 for 3. Stats are OK, it was just the history on the main display. Other subs in the same game showed OK.

[FTMSupport]

We believe we have this fixed for the next release, though since we do not have an exact set of steps to reproduce, we can not be positive until people do not report it after the next update.

[jojolemon]

FYI...still not fixed. I saw it again today. The problem seems to only appear when there's a defensive change and I make the offensive change to the line-up at the same time. Here was the situation today:

Visitor, bottom of the 5th: defensive substitution announced for center fielder. Also announced he was taking cf's place in line-up (batter #8). I noted both changes in iScore. The new player came up to bat in the top of the 6th (as the 3rd batter of the inning with 2 outs already recorded). Batter #7 (who had not changed) had this history to that point: single, double, single. In the 6th, he flew out to cf. Batter #8 went to the plate and iScore showed batter #7s history on screen (ie. single, double, single). The first center fielder had struck out twice and popped out to ss. So, again I suggest that iScore seems to just be leaving the previous batter's history onscreen instead of wiping it clean when a new batter with no history comes to the plate...if the batting substitution was made at the same time a defensive substitution was made. iScore did have the correct batter come to the plate. It just had the history on the screen wrong. The stats after the game were all fine. It's a cosmetic problem...and not a big one...but I've seen it in several instances now.

[FTMSupport]

Thank you for the great details... we will try and reproduce and get this fixed right away.

[PetroGuy]

I have also seen this issue. I have seen it in a little different situation. I was going to wait until I could see a few more instances and see if I could pin the details down a little better, but what I have now might help.

My son's team typically roster bats (all players at the game have Batting=Yes). As we get deeper into the season (and other teams are getting more serious about beating us), we are seeing more teams that bat 9 or 10 players instead of roster batting (at least one player has Batting = No). I have not seen this issue when both teams roster bat. I also have not had to make an offensive substitution to have this occur. We had a game last weekend where we were the home team and the starting lineups and positions for our team were set. The visitors hit a homerun in the top of the first. For the rest of the visitor's lineup, I got to see each player come to bat for the first time with a batter history of '1 for 1 Home run'. Once they got through the lineup, the history reflected the correct batter's information. All the stats are correct, it is a cosmetic issue only.

[jcbeckman]

I had the same thing, only with a single. Every player was marked "1 for 1, Single" until the entire batting order went through.