Computer doesn't chase a total!!

[anakwalajinn]

Well, sorry if it was stupid to make a thread about this. But are EA humans??
I don't think so!
Anyway today I autoplayed a test match, Bangla all out for 215 and 512 and Zimbabwe made 740 runs or something like that and 4 overs left they needed 32 to win Zimbabwe, they made 13, match drawn! :
That wouldn't happen in reality, they would have tried to chase the total!
Stupid EA!
This thread was not about this incident, do u guys have more? I come back 2morrow, good night!

 

[ScobieB]

It always the other way round for me. And whenever I try to chase a total I end up being out.

 

[ricky1988]

Well in my 20/20 match i scored a high total cant remember how much, but the computer seems to be losing wickets quickly because they keep going for big shots, so they are chasing the runs from what i can see

 

[Big_D]

Seems that the computer has the same problems we do, it has real trouble scoring boundaries without using the six hit button.
So it trundles along at 4/5 runs an over, then an alarm goes off and it starts to slog, and you get a rain of sixes or a rain of wickets.

I find it does the same when setting a total. 8 wickets down and five overs to go, time to push the singles and get every run you can, right?
Wrong, the tailenders think they are bradman and start playing big shots, sometimes you can finish it quickly, sometimes they get a big score.

 

[anakwalajinn]

Man the computer sux! =P

 

[StormySteve]

Man the computer sux! =P

Nah....the game does :crying

Steve S.