There are a few problems. As I guessed, the scorer left an atbat blank
before the first out in the 5th inning. That's the point where K-ForCE
stopped accumulating pitching and fielding stats, yielding 4.0 innings.

It look like batter 8 (#33) left the game. K-ForCE doesn't deal with this
situation very well. In most leagues, the team is required to take an out
in the case. But in little league, they aren't. The only way to deal with
this is to score the batter as a fielder's choice (FC), then replace the
'FC' with an 's'. WHAT? That's right. Scoring an 'FC' is the only way
that the runners aren't auto advanced. And 's' is the only way a batter
won't be charged with an atbat or walk or some other offensive stat. The
's' stands for Sacrifice. And the lowercase says 'don't count this when
accumulating stats'. It's used to score something like a 'Sac E3'. In this
case, the batter shouldn't be charged with an atbat because the intent was
to Sacrifice. And he shouldn't be credited with a hit either. So this is
the only way (I know of) that the batter can reach base without having an
effect on his offensive stats. K-ForCE v2.3 has a menu item for 'SAC E'.
In that case, score it as that and change the comment to lowercase.

BTW. Did you know that by scoring an 'E' as lowercase it won't charge an
error. This is useful when two runner advance because of an error. There
is only one error charged. Scoring the other as lowercase 'e' allow for
more descriptive score keeping.


The Validate Game Data function identified the issues. Here is the text
from the Validate Game Data window:

Validation Results for Visiting Team
INFO: 11 batter(s) found
ERROR: Pos. EF is covered by two players at the same time: 8 - rys and 12 -
klein, 1st Inning
ERROR: Starting pos. LF omitted
ERROR: Pos. CF is covered by two players at the same time: 22 - hill and 1 -
sanchez, 1st Inning
ERROR: Inning 5 has less than 3 outs
ERROR: Inning 5 has less than 3 outs
ERROR: Inning 5 has less than 3 outs
ERROR: Inning 5 has less than 3 outs
ERROR: Batter 9, 5th Inning batted out of order.
ERROR: Batter 10, 5th Inning batted out of order.
ERROR: Batter 11, 5th Inning batted out of order.
ERROR: Batter 9, 7th Inning batted out of order.
ERROR: Batter 10, 7th Inning batted out of order.
ERROR: Batter 11, 8th Inning batted out of order.
ERROR: Batter 9, 9th Inning batted out of order.
ERROR: Batter 10, 9th Inning batted out of order.
ERROR: Batter 11, 9th Inning batted out of order.
____________________________
Validation Results for Home Team
INFO: 9 batter(s) found

It's a bit like a compiler; some errors cascade. That's why there's
multiple errors reported for the 5th inning.

One thing the Validate doesn't catch is, the scorer left the name and number
blank when a player subs for himself. We plan to support this in the
future; but for now, that will not produce the correct fielding/pitching
stats. The player's name needs to be re-enter on each line that the player
changes position.