AI batting - innings pacing experiences

AshleyWilliam

Banned
Joined
Sep 22, 2014
The most recent patches have improved the pacing of the AI's innings when batting very well in tests and one dayers. The scores produced are realistic. Up to 450 odd for tests, and 270 odd for ODI's, But after doing a lot of testing, T20's are still a major issue. The first 6 powerplay overs are fine. The AI can go around 8-9 runs an over. But from this point on they grind to a halt. It seems like they are programmed to try and score at 5 runs per over - meaning the average score they make is only about 120. Even by 'cheating' and leaving only 3-4 men outside the circle, they still score at an unrealistic snails pace.

@fiction - you guys have done a great job in fixing the pacing in tests and one-dayers. In the upcoming patch, could the AI pacing in T20's please be looked at - this would massively help in improving the playability of the game in this format. Perhaps if you ask the AI to attempt to maintain a scoring rate of 8/9 rpo after the powerplay. Id rather get smashed around the park than see them block out maiden overs. Thanks
 
The most recent patches have improved the pacing of the AI's innings when batting very well in tests and one dayers. The scores produced are realistic. Up to 450 odd for tests, and 270 odd for ODI's, But after doing a lot of testing, T20's are still a major issue. The first 6 powerplay overs are fine. The AI can go around 8-9 runs an over. But from this point on they grind to a halt. It seems like they are programmed to try and score at 5 runs per over - meaning the average score they make is only about 120. Even by 'cheating' and leaving only 3-4 men outside the circle, they still score at an unrealistic snails pace.

@fiction - you guys have done a great job in fixing the pacing in tests and one-dayers. In the upcoming patch, could the AI pacing in T20's please be looked at - this would massively help in improving the playability of the game in this format. Perhaps if you ask the AI to attempt to maintain a scoring rate of 8/9 rpo after the powerplay. Id rather get smashed around the park than see them block out maiden overs. Thanks
But realistically speaking, you do see players blocking out maiden overs in a t20 game. What scores on average have you seen AI score in a t20 and at what difficulty? I usually find myself chasing 140+ scores in a t20 game on legend, but maybe either I'm bowling reasonablly well or a little on the horrid side.
 
But realistically speaking, you do see players blocking out maiden overs in a t20 game. What scores on average have you seen AI score in a t20 and at what difficulty? I usually find myself chasing 140+ scores in a t20 game on legend, but maybe either I'm bowling reasonablly well or a little on the horrid side.

Hi Fiction, thanks for the reply.

The average scores I'm getting for T20's is about 115-120. This is also on legend difficulty. I create custom competitions (such as the current champions league which I have recreated) which allows me to change difficulty. I bat on pro, and bowl on legendary in an attempt to make the AI as competitive as I can. As I said, rpo is perfect for the powerplay overs. Its the rest of the innings that just grinds to a halt. There is also no marked attempt to increase the run rate in the last few overs, unlike 50 over one day matches where the AI seems to up the pace.

Not sure what other people's experiences are? I think I have read somewhere that others have the same issue too.
 
I reckon we should wait for other people's opinions before considering making some changes.
 
Well, for me, the scoring rate looks fine in t20s at the moment. Recently had the Aussie Domestic t20 cup with my career player where the team I am playing for managed to reach the finals. The other team in the finals was Western Warriors - from previous experiences, this side had proven to be tough to beat, they deserved to be in the finals. Previously, I was thinking its a glitch in the game that they were scoring so many runs in simulation runs. However, when I did get to playing in the finals against them, they hammered my 4 overs for 55 overs (and ended up scoring 200+ runs) - and I was the leading wicket-taker in the tournament with 17 wickets :eek:
 
You didn't play Western Warriors in a T20 Final.
 
  • Like
Reactions: Ren
Well, for me, the scoring rate looks fine in t20s at the moment. Recently had the Aussie Domestic t20 cup with my career player where the team I am playing for managed to reach the finals. The other team in the finals was Western Warriors - from previous experiences, this side had proven to be tough to beat, they deserved to be in the finals. Previously, I was thinking its a glitch in the game that they were scoring so many runs in simulation runs. However, when I did get to playing in the finals against them, they hammered my 4 overs for 55 overs (and ended up scoring 200+ runs) - and I was the leading wicket-taker in the tournament with 17 wickets :eek:

I'm not talking about career mode and simulating. I'm purely talking about bowling to the AI from start to finish in real time. Simulated scores are fine. Real-time scores are the problem.

I would like feedback on people's experience with real-time scoring rates by the AI please.

Also, Western Warriors don't play in the Domestic T20 in Australia - you might have mixed it up with a one day match or got confused with another team.
 
Last edited:
I'm not talking about career mode and simulating. I'm purely talking about bowling to the AI from start to finish in real time. Simulated scores are fine. Real-time scores are the problem.

I would like feedback on people's experience with real-time scoring rates by the AI please.

Also, Western Warriors don't play in the Domestic T20 in Australia - you might have mixed it up with a one day match or got confused with another team.


Apologies - You are correct. Seem to have gotten my teams mixed up.
Real time scoring rates seem fine too. Just completed a t20 match on veteran; It was a against a higher ranked team and expectedly, they scored heavily (170+). Their bowling seemed incongruent to their ratings though, as I managed to win fairly easily.
 
Apologies - You are correct. Seem to have gotten my teams mixed up.
Real time scoring rates seem fine too. Just completed a t20 match on veteran; It was a against a higher ranked team and expectedly, they scored heavily (170+). Their bowling seemed incongruent to their ratings though, as I managed to win fairly easily.

What, you just completed one then?
 
What, you just completed one then?


Yes, and I have played whole tournaments both before and after the current patch (16 team et. al - Note my 150+ hours on steam). Didnt really see a pattern. Some teams surprised me while others disappointed, but not to the effect of 'oh my, they are always scoring low'.
 
Last edited:
AI batting need much aggression for t20 . It's a big improvement in the game.
 
I agree with OP AI play defensive shots in last overs wheater it's t20 or ODI but I'm talking about Pro here. They also miss free hits most of the time and they give up on winning in last overs. I don't want AI to be pounding me all the time though :)
 
I am totally agree with Ashley . AI batting must be improved in t20 games. In t20 cricket average score is around 160 in real world that never happened when AI bat. At pro level AI score never cross 130 against 2 star rating bowling attack. And When they chase 140 they never get it . In last 5 over they don't attack while they have 6 or more wickets in hand. They also miss most of free hits . So please in next update AI batting must be improved specially in shorter format.

Sorry for my bad English.
 

Users who are viewing this thread

Top