Autoplay Problems

E

ejaz

Guest
Hey guys:

I am relatively a beginner to Cricket 2002. So I mostly just bat and let the CPU bat on autoplay so that I dont need to bowl.

Have u guys ever seen the CPU team get out for less that 250 or so ?? Coz every time i autoplay, be it Australia or Zimbabwe, they do run up scores of above 250. Doesnt seem so realistic, does it ?? Is there some patch anywere to fix this problem ?? Or maybe I should learn to bowl now !!!! :lol:

Someone help,
Kewldude_78
 
autoplay aint cheating....it is just we dont have the time to sit there and bowl so many overs...for 3 hours and then finally bat for 3 more...
 
EVery one has a diffrent opinion, I dont think autoplay is anyway of cheating.
 
Bowling's the fun part of cricket2002, batting's the bit you should autoplay. If you're good enough at bowling it won't take you three hours anyway.
 
Yea, correct. Well in TEST matches I can bowled out whole CPU team with 15 overs probably 10-15 mins and in ODI within 10 overs.
 
Well, the Autoplay feature has been made available to us by EA, and I do tend to use it quite a bit..... I suppose I'd bowl a lot more if the bowling cursor didn't move so fast on Normal or Difficult levels when using a Gravis GamePad.... Is there a way around that or would that be considered cheating too?!
 
Why would you want to? That's the whole point of changing the difficulty setting, it's to make it harder. If you want it to move slower, play on easy.
 
yea but my keyboard is very sensitive or my comp is fast or something, and if the curser is on one side of the pitch and i give the keyboard a little tap it zooms to the other side! way too fast.
 

Users who are viewing this thread

Top