And it just happened again for me, with no issue. '53 Yankees vs '16 Brooklyn. Joe Collins reaches on a one-out error. Next batter, Hank Bauer, hits a two-run HR for a 2-0 New York lead. Updated box score correctly shows that only one of the runs is unearned.

This has now been fixed. I guess I whined enough.

Nate

Huh. Now they are back. Maybe it’s a thing with “Archive” and “Active”? The collection only appears in “Archive”.

It happened again today, but I think I have finally isolated this issue.

It seems to happen to players who, in autoplay games, are playing in a defensive position that is NOT the primary defensive position on their card profile.

I moved the Dodgers’ Floyd Herman to 1B for today’s autoplay game against the Reds (both are BATS3 pre-expansion teams). Herman is listed as an OF, but 1B is also a position available to him. When I set the Dodgers’ lineup before the game, I noticed the “1B” in the tab beside Herman’s name was a different color than everyone else’s tab. I thought that was interesting… and honestly wondered if that might anything to do with this ongoing problem.

I played the the game. Sure enough, Herman has been omitted from the Game History box score (see bottom graphic below). In the postgame box score, note how he went 3-for-4, with a double, HR and 4 RBI. But he does not appear in the Game History box score.

Nor do his updated stats appear in Collections. Which really sucks, given that he is a leading batter in the 56-game season I am currently playing.

But I really think this is the issue. Would really appreciate it being resolved.

Will send my suspicions to Support…

Screen Shot 2023-12-07 at 2.23.36 PM.png
Screen Shot 2023-12-07 at 2.24.20 PM.png

@mattlandis yep, I’m an Idiot, yes, 1

not only does it not match anyone on the Mets, but it matches no one at all in 2022 or 2021. Very curious!

@striker2550 Yes it will be replaced.

I was the owner.

Still happening…Screenshot_20230706_151516_Chrome.jpg Screenshot_20230706_151659_Chrome.jpg

@mariner Thanks so much for the heads up.

Everyone might be at the convention?

@apba__dave Anytime I see something glitchy like that, I send details of it to GO Support. When GO first launched in 2016, there were quite a few little gremlins like that in the game engine. Over time, the majority of them have been fixed. But I’m sure a few (like this one) still exist.
I have found the GO Support team to be very appreciative of hearing about glitches like this, and that they’re usually resolved by the next update. Sending them a screen shot of the issue also seems to be very helpful.

Screen Shot 2023-06-12 at 12.36.40 PM.png