Hey... this is just a place where I can answer some of your suggestions
so you can all get an idea of why I did or didn't do something.

LAST UPDATE: Saturday 19/4 

Here goes...

1. make guys and ball bigger
> Yeah, this is the first thing I thought would come back. It's an
attempt to make it easier for the batsman to score. Sorry, I'm
not going to change it back, I would have to rewrite the AI.

2. if u move out sightly of crease cpu bowls no ball change it
> I think what is happening here is that the ai is trying to lob it
over you, but it might be a bit too sensitive by the sounds of it.

3. please make it quicker
> How slow is it? It should run at 50fps, which is pretty quick
(the same speed as the other Slime games). Try using Microsoft's
JVM rather than Sun's (in IE, look under Tools->Inet options->
Use Sun's JVM or something like that)

4. computer bowls to many no balls.
> Probably related to 2. I think the international AI died on me,
it was pretty hard to beat and now it seems it has gone soft.
UPDATE: It was related to 5 below, and should be fixed.

5. Also they should run if they've hit a four like we do
> Yep, I agree. Will look into it. UPDATE: this should be fixed now.

6. The computer will sometimes get out of the way of the ball and then
jump up and down next to it causing it to be a no ball.
> Fixed.

7. When the computer hits it near the wicket and it passes the crease
the runner can still run back and forth and the computer opponent
will never hit the wicket with the ball
> Will look into it.

8. If the computer bowls the ball, (and I have seen this sometimes with
the 2 person version as well) if the computer hits it somewhat high
and you reach for it many times it will go directly through you.
> You can only hit the ball once when you are batting. I assume this is
what is happening - you aren't timing the ball and are hitting it once
(really badly), then the ball continues to move through you.

9. The computer will keep bowling me a ball that is I assume too high
because it calls it a no ball
> Yep, there seems to be a problem with choosing which ball to bowl,
this needs to be fixed. UPDATE: I found out what happened here, it had
me stumped for a while. I added a delay before the AI bowls, so you
have time to play the ball, which stuffed up the timing of the AI's
movements to bowl a particular ball. Should be fixed.

10. The computer will just let the ball bounce on his head and never
bowl it.
> I've never seen this, I assume it's related to 9. We'll see.

11. There are World Cup teams missing, and some team colours are dodgy.
> Yep, I know. 1. I don't know some of the colours of the minnows,
and 2, I'm colour blind anyway so I can't tell my reds/greens/browns
apart :(

12. When I.m batting (particularly on the hardest level), often the
bowler goes a bit mad hitting the ball against the wall above the
keeper, allowing me to sneak plenty of runs
> Yep, I shall make the bowler a bit less jump happy!

13. What.d be really cool is some sort of .final. screen showing the
score and who won
> I plan to add some sort of funky ending screen thingy, that's
all I can say for now.

14. when u change the team that you want to bat first you cant change
it back to the computer which it was originally on.
> I forgot to change it back - you won't be able to watch the AI play
itself in the final game.

15. the bowls on international difficulty are too predictable.
> Yes - I'm not going to think up twenty or so different balls, they
would all be similar anyway. Each difficulty level only has two
or three balls to choose from, so international is no different
from other levels.

16. if its posssible to play people online
> No, I can only host static stuff on this server, and I don't have
the time or motivation to write a networked game.

17. maybe you could make something like a series of games to win the
World Cup, and then have an ending screen, like #13 on the page suggests
> Yeah, that might be the way to go - the annoying thing (I think)
about the current one player slime games is that you have to waste
time beating "easy" opposition to get to the harder levels - 
you can't have it both ways :( What to do...

18. when the cpu runner was at the bowlers end he randomly ran to the 
boundary and now it is stuck and wont go onto the next bowl.
> I will have to fix this, in the meantime, you can force the game
to go to the next ball by pressing S and K.

19. when they hit a single ( could be more ) and you get the ball close to 
the wicket and hit them the cpu batter moves slightly out of their crease 
and gets called out because they are a tiny bit out of the crease at the 
bowlers end
> Should be fixed shortly.

20. have 10 outs like they do in the real one
> Sorry, I won't be doing this - the way it is, the game is guaranteed
to be of a certain length. Maybe there will be a Test match version
one day?

21. if I bowl it direct to the wickey, but not too high, it sometimes 
bounces off him and comes back towards my bowler. When it touches the
bowler it then says 'no ball'.
> This will be fixed shortly.

22. it would b cool if u could spin the ball.
> I agree, but then I think the game would be getting too complex.