Page 1 of 1
Fielders Choice
Posted: Tue Jun 21, 2011 11:32 am
by JREagles
Sometimes when I have a runner on 2nd and the batter gets on due to a FC, the runner going to second gets forced out and iscore will show FC 6-4 on that batter (which is correct, as the example shows,but other times the runner going to second is shown as a FO batter # when the batter gets on due to a FC.
I recently noticed that it scored the latter when that runner was the third out.
I've also noticed it before where the runner was going to third from second and the batter was scored as a FC, but the play at third instead of showing FC 6-5,
it showed TO batter #.
Many thanks.
Re: Fielders Choice
Posted: Tue Jun 21, 2011 12:29 pm
by OhioTex
I suspect you did not enter the iscore key sequence as expected when entering the play originally, we can test for this and then correct in pitch by pitch if i am correct. ...
go to a game, When on the scorecard you get a FO# for the runner (and expected to get a FC-#-#), I suspect, you did not hit Safe, Fielders Choice for the play, instead selected single or bunt or some other way to reach on first other than FC... to test, go to a game that you see the FO# for a runner but expected to see a FC #-#, what does the scorecard show next to first on the batter who hit the fielders choice? if not a green FC what is it? If this is the issue, you should be able to correct it in pitch by pitch editor .
when on the scorecard you see a TO# for a base runner when you expected a FC #-#, my guess is you did not hit "force out" for what happened to the runner, instead hit Tag Out when prompted for what happened to runner on X base screen? even though physically tagged, it is still a force out. (yes that is a quark of baseball). you can test this , like before and correct in pitch by pitch editor also.
another possibility is the situation was not a force out (ie a free base in between batter and runners) so just a fielders decision to tag out a leading runner....
I have tested this with 0 out, 1 out, and 2 outs, and men at first, first and second, first, second and third, and not seen it make a difference. though i am sure i have not tested every possible combination.
let us know if this explains away the issues you have observed. If not, let us know.