Box Score Linking to Wrong Game Log
 

Running with the patch, I just finished playing a game. While looking at the postgame boxscore, I decided that I wanted to check out the game log. When I was looking at the game log, I knew something was wrong. Upon further investigation, I found that it was the log for a completely different game. The heading on the game log is correct, but the log itself is different.

Here is the box score.
Attachment 47882

And here is the game log.
Attachment 47883

One of the teams (Monclova Bandicoots) is the same, but the outcome is different, as is the other team.

Update:

This was all after the game was over but before pressing the finish game button and going back to the main page. Once I did that, I went and looked at the box score and log again, and it is correct now. I don't know what or where the problem is, but maybe someone has an idea,

Another Update:

When in the game, and you click on the Game Log tab, you get the correct game log. However, if you follow the Game Log link in the box score, you get the wrong game log. I figured this out when I simmed another game, so it is not a one time problem, I have been able to replicate it twice now.

Boxscore Anomaly
 

Came across this boxscore during my one of my league's initial Spring Training games. It shows the final score as 8-6, yet the runs shown for each inning do not add up to that. Furthermore, both the game log as well as the Pitcher's box (below) indicate a 3rd result - a score of 2-1. Strange.
Is it because it was April 1 on the schedule? Hmmm...

What the pitcher's saw:

I have the latest patch to boot.

I found the same problem and it has been officially been submitted as a bug.

This may be a mismatch of the box score, game log, and the issue may be reported separately. I am digging into the matter.

See also http://www.ootpdevelopments.com/boar...d.php?t=124151

Thanks Raidergoo. I should have searched a little more before posting a new thread. :p

Hi, and sorry for the late response. :(

This issue has definitely been resolved in Patch 2. I just confirmed it myself.

Thanks!

Steve

Merged a few related threads...