I know y’all are working on this, but I wanted to post this one as well… similar issue where the starter got the win when he wasn’t supposed to, but on this one the LOSS was also incorrect. The starter came out of the game with the tying run on 2nd, the bullpen gave up that run, and 2 more… the reliever should have got the loss, but didn’t.

https://baseball.apbago.com/baseball/history/boxscore?boxScoreId=457280

@wildfire2099 Purposeful… we were asked to do it.

Thanks,
Jeremy

out league must have over 100 custom teams so dont think limit

@sstein Should be good to go now. Fallout from yesterday’s deployment attempt.

Thanks,
Jeremy

@wabillk Hi!

Make sure you’ve selected Custom Teams: On during game configuration.

acaf3bd6-6d54-4e2a-869d-591c17623bfd-image.png

Thanks,
Jeremy

I end up choosing the year that contains the team I am looking for to scroll, but I only have 3 seasons. It does work better for me than scrolling down the entire list.

good point it is annoying

thanks for the update! i understand you have lots happening.

Hi! Thanks for letting us know. There are a lot of Ohtani related fixes in 2.5.0, our upcoming release.

I will make sure to include this issue.

Thanks,
Jeremy

Thanks! Enjoying the game.

Thank you Jeremy - I will give that a try.

Cheers!

Sean - Raysfan

Very useful! I had seen some behavior like that, but didn’t know exactly what order to do things. Thanks!

@sstein Hi!

No worries, please let me or support know if it resets again.

Thanks,
Jeremy

@sstein Just for the record, @APBA-GO-Jeremy has addressed this issue. Thanks, Jeremy!

@APBA-GO-Jeremy

Thanks Jeremy!

This issue continues to come up. I had a second column 8 hit and run yesterday and it got scored as an out should have been a single.

Is this issue being looked at and corrected?

@adamdavidson2718 Hi!

I had to verify with the Alpharetta team to get the correct answer for your data question.

You are correct, on APBA GO prior to 1954, there are only 25 players available per team.

Thanks,
Jeremy

@RandySteinman It does! I’m supposed to be reviewing a fix for the issue later today.

If it’s good, it’ll be included in our next release.

Thanks,
Jeremy