losing to stupidly high run chases

[Oli987]

Does anyone ever find when they declare and set a big total in not much time the other team sometimes randomly chase it down and start smashing you all round the park in a completely unrealistic fashion? It's happened to me on a few occasions. Despite being on top for 3 1/3 days I just managed to concede nearly 350 in 2 sessions to lose!

I'm pretty sure if most players stuck a batsman who wasn't settled on very aggressive on an uneven turning pitch they'd get out pretty qucik right? Well I guess the AI is different

 

[Myrmecophaga]

The documentation claims the AI doesn't cheat in any way, it just plays with complete knowledge of the statistics. Did you take any early wickets? I suspect that the first two batsmen have a go, and then if they fail the rest knuckle down.

 

[Bridger]

I got an answer from Chris Child on this subject on the ICC2008 forum, and he acknowledges that there is a problem with ridiculous high run chases and totals on 4th/5th day/seaming/turning pitches, and it will be addressed in future versions or upcoming patches.

 

[Niv]

Recently South Africa scored 427/6 when I declared leading by 500, with 4 sessions left.

Won the series 2 - 0 though

Although, for me it doesn't happen that often, and I imagine that it was a great batting performance despite my bowlers giving it everything.

 

[Oli987]

The documentation claims the AI doesn't cheat in any way, it just plays with complete knowledge of the statistics. Did you take any early wickets? I suspect that the first two batsmen have a go, and then if they fail the rest knuckle down.

Hmm I wouldn't think the AI cheats, simply that it can be a bit glitchy and unrealistic. I did take a couple of earlyish wickets, they were 50/1 at lunch then 90/2 about 10 overs after lunch chasing 390.

On a similar note has anyone else had an issue with spinners having less success on sharp turning pitches than good/average? (This has probably been discussed already)

 

[Myrmecophaga]

I didn't say it cheated- I said that the documentation says that it doesn't cheat.

I just lost a game by a wicket with a 381 run chase.

 

[GrahamB]

I got an answer from Chris Child on this subject on the ICC2008 forum, and he acknowledges that there is a problem with ridiculous high run chases and totals on 4th/5th day/seaming/turning pitches, and it will be addressed in future versions or upcoming patches.

Yep and about time too. It was a problem in the previous version also.

 

[boozemonster]

happen to me just now, set Lancashire 380 to win with 2 and a half sessions, took a couple of wickets with james harris (who is the leading wicket taker in the county circuit in my second season) and ended up loosing by 6 wickets on a terrible pitch.

as for chris child sorting this problem out in further versions or patches, we all know it'll be in versions not patches because he doesnt seem bother with them, he'd rather just wait a year and take your money again.

 

[Themer]

happen to me just now, set Lancashire 380 to win with 2 and a half sessions, took a couple of wickets with james harris (who is the leading wicket taker in the county circuit in my second season) and ended up loosing by 6 wickets on a terrible pitch.

as for chris child sorting this problem out in further versions or patches, we all know it'll be in versions not patches because he doesnt seem bother with them, he'd rather just wait a year and take your money again.

Theres going to be a patch/update in the very near future

 

[boozemonster]

we shall have to wait and see, i for one am not going to hold my breath

 

[afridi118]

happen to me just now, set Lancashire 380 to win with 2 and a half sessions, took a couple of wickets with james harris (who is the leading wicket taker in the county circuit in my second season) and ended up loosing by 6 wickets on a terrible pitch.

as for chris child sorting this problem out in further versions or patches, we all know it'll be in versions not patches because he doesnt seem bother with them, he'd rather just wait a year and take your money again.

hahahahaha i like this post

lol

thats why i bat second and if opposition's score more then 500 i bad slow and declare by 475 and give a chance to opposotion to bat and the usually declare by gibing u the target of 300+ and alot of times i have some time so i bat fast for 3 to 5 wkts if get a good start i win. if i lose wkts slow down and go for draw.

 

[Niv]

UNBELIEVABLE!

Four sessions and I couldn't take 10 wickets no matter what I tried.

(One of their batsman retired hurt, so it was technically 413/8)

 

[The_gas]

Yeah it needs looking at, many times the cpu bat on a turning, unven pitch likes its the flattest deck in the world.

 

[ZoraxDoom]

What I do when situations like this arise, is use a few part timers or just keep bowling my best bowlers. Set a custom field and change things up a little bit in terms of line and length or aggression. Usually does the job.

 

[Lanceknight]

What I do when situations like this arise, is use a few part timers or just keep bowling my best bowlers. Set a custom field and change things up a little bit in terms of line and length or aggression. Usually does the job.

Pretty much what I do. Throwing in a couple of overs from part-timers is usually a good idea. Keep changing the length and try going round the wicket. Do not let them settle to fields, keep moving them around.