Bug on entering overs without a legitimate ball

Hi Mark, as reported by John in a earlier thread, I have just tested the following scenario. New bowler comes on, bowls two balls, both beamers, umpire calls no ball to both and advises bowler is banned from bowling in the match. Cricketstat accepts the bowling figures of 0 0 2 0 and will even accept the two no balls being entered, however when you exit and go back in, the 0 0 2 0 is still there, the two no balls have disappeared. Tried this three times over for the same result. However if I try 0.1 0 2 0 it will accept two no balls.

1 person has
this problem
This topic is no longer open for comments or replies.