We’ve been getting lots of great suggestions since the launch of Spinfast Cricket 2.0, and we are already working on our first update to address the most popular demands quickly.

Here are our planned revisions:

1. Allow players to quit the field after beating the run chase total.

2. Make batting a little easier on Easy for newcomers (and add back in some of the assists on that level.

3. Make the CPU a little better at defending their wickets across all levels so they are more challenging to bowl out.

4. Fix the reported bowling bugs. PLEASE send us more information on these bugs as we have not been able to reproduce them yet.

5. Fix the reported first screen freeze. PLEASE send us more information on this bug as we have not been able to reproduce it yet.

6. Fix the run-chase targets not changing for different over lengths for some users. PLEASE send us more information on this bug as we have not been able to reproduce it yet.

What quality of life, fixes or balance issues are you most keen to see in this first update? Help us make the game you want to play.

We received a message from the in-game news link asking to:

“Please improve bowling actions – just not intuitive at all!”

After playing a bit of bowling, does anyone else feel this way?

I thought drawing the path of the ball you’d like to deliver seemed fairly intuitive, and it was the only way we could offer control of line, length, speed and left/right, top/back spin.

We also offered the mode where you just tap the screen to lock in the path. We figured that between the two we could give you a good balance of control and simplicity.

“Please get batting accuracy back.”

Is anyone else having trouble with this? If you are, do you feel the shots:
1) are too random (but in the right vague direction)
2) don’t go where you expect
3) are too hard to time even on Easy/Medium?

Thanks for the feedback Jay!

I’m afraid you’ve likely been bitten by the delayed input bug — we uploaded a fix a week ago but it hasn’t been made available through iTunes yet.

This problem is resolved in Cricket 2.1.1 and I appologise for the inconvenience you are experiencing at the moment. As soon as we discovered the problem, we isolated the cause and uploaded a fix within an hour… but we are now left waiting for Apple to pass it on to you our customers and there’s nothing more we can do to hurry the process along. It’s an incredibly frustrating situation for everyone!

Rj