How to score fielders choice : bases loaded and 2 outs.
Situation is: Bases loaded, 2 outs and batter hits ground ball in play to SS who tags second base for the out.
When I choose ground ball, fielders choice and select shortstop as the fielder that made the play and click done the App first asks if runner crossing home is safe or out (it’s only option to choose). If I choose safe at home it then gives option to select safe or out for runners to both 2nd and 3rd. If I select out at 2nd it ends the inning as it should. The problem is that it scores the run that came across home plate which I thought should not count because it was a force out. In order to make it work I had to mark the batter out at first which is obviously not accurate for fielding stats.
Where am I going wrong?
Posted Jun 23, 2022, 7:13 PM UTC
Select “back” on the runner advancing to home. Then select “out” on the runner advancing to second.
Thanks so much. I see the back button now. It is a gray color on iPhone and I didn’t see it in the sun.
Seems a little counterintuitive to send the runner headed home back when it could just present all runners with safe/out options but I’m sure there are other scenarios where it makes sense for it to go in that order. Always learning with plays that happen I have not scored before.
I just tried in a practice game and this looks correct for all the stats. Watch and after you hit back on the runner coming from home it asks who is out at the top. Then you just mark the runner coming from first. Noticing that the heading changed helped convince me the stats would be correct.
Thank you for this answer, just had this situation last night and angrily scored the runner out 4-6 at home so that the run wouldn't count. Now I know I can use that back button.
Feels like an obvious workflow scenario to fix. It is complicated though (but only if no runner on first) and the FC happens on the runner b/w 2 and 3rd, it's a timed play and the run could count.
Given the beta launch years before it was ready and lack of responsiveness to necessary updates, plan to use this workaround indefinitely!