Quote:
|
Originally Posted by hefalumps
Are you kidding? The game can't even count sac flies properly? I wonder if this happens all the time or just on particular occasions. I'm hoping it's only in unique situations, otherwise I'd like to think it would've been caught in beta testing. 
Was the runner advancing from third to home or from some other base to the next base? If it's the latter, maybe it's getting scored both as an at bat and a sac fly by accident. |
From third to home, and as both a sac fly and an AB... according to the box score.
Here's some more info:
This is from the game log, his sac fly:
Top of the 8th - Kansas City Royals batting - Pitching for Chicago (A) White Sox : LHP H. Hashimoto
Batting: RHB P. Suttle 0-0: Ball
1-0: Bunt for hit - play at first, batter safe!
Batting: SHB C. Larino 0-0: Called Strike
0-1: Foul Ball
Pickoff Throw to First - Error!
P. Suttle to second
0-2: Intentional Walk
Batting: LHB T. Goulding 0-0: Called Strike
Throwing error on steal attempt, E2
P. Suttle scores
C. Larino to third
0-1: Foul Ball
0-2: Ball
1-2: Fly out, F9 (Flyball, 9M)
Runner from 3rd tags up, SCORES, throw made
With a man on third this is the stats it shows for him in that split:
11 PA, 5 AB, 5 BB, 1 SF, 3 H, 2 R, 1 2B, 4 RBI, 4 TB, 2 K
So there it shows correct. The sac fly hasn't been counted as an AB.
In the box score, and the game log it shows the sac fly having been counted as an AB. The split for count being 1-2 shows up right...
Looks like it's scoring it correctly, but not reporting it correctly in the box score and game log... which is better than it screwing it up across the board.