Testinnings, run-rates on autoplay

[matskgjohansson]

Hi

Has anyone used autoplay during testmatches on cricket 2004?

For how many overs does the cpu bat and what is the general runrate?

Mats

 

[msardi_23]

Autoplay sucks. The cpu makes jack pooh runs. Australia bowl india out for 150 in india!!! Autoplay in 2002 was better. The only difference in 2004 it takes longer to score the runs, but the bad thing is they opposition bat pooh. Well in the games i have done so far anyway.

 

[matskgjohansson]

Thanks for the reply, good if it takes longer time, though, but you are right, the score also has to be competitive...

 

[ejaz]

Hey I had a good experience with autoplay. India playing Worcestershire in England .... green wicket on a cloudy day ... Worcs bowled out for 140 in 35 odd overs ... and the seamers taking all the 10 wkts ... 6 for Zaheer and 3 for Agarkar. U could never get any team out for that low a score in any conditions in C2002. I would say that autoplay has been improved in C2004.

 

[uman]

I LIKE AUTOPLAY SYSTEM CUZ I DON'T LIKE BOWLING.

 

[steven2106]

I like bowling as much as batting especially with the spinners. Unfortunately cricket2002 was too predictable and bowling became boring but it looks much better in Cricket2004. The CPU now play and miss at the quicks and get edges (all to 4th slip so far) and the spinners get bat-pad catches, which makes it feel more realistic. The good batsman put away anything offline and even go after the good stuff, so at least you cant bowl maiden after maiden like you could in 2002.

 

[uman]

IS THE AUTOPLAY SYSTEM SAME AS CRICEKT 2002. I MEAN IN TEST RUNRATE IS LIKE AROUND 6,7 OR ITS LIKE REAL RUNRATE AROUND 2,3.

 

[sachin]

whneever i played against the english county teams i got them out for around (general area)50-100.and i made alright totals(well apart from when matty hayden made two hundred).the autoplay is good in test but bad in one dayers.they score to slowly.