Cricket Captain 2019 Bug Reports

[biggy09]

A big bug imo that has been in since at least the last addition to my knowledge is the way the AI select bowlers, specifically in limited overs. FC is generally okay, besides the random batsman coming on first/second change, but limited overs is generally poor imo. A lot of times in both 50 over and t20 games the AI rarely uses a 6th (so never a 7th) bowler, and the opening bowlers will also a lot of the time bowl out 7+ overs each to start the innings, even if they are being smacked around.

Loving it regardless. Thanks.

[bryce87]

A big bug imo that has been in since at least the last addition to my knowledge is the way the AI select bowlers, specifically in limited overs. FC is generally okay, besides the random batsman coming on first/second change, but limited overs is generally poor imo. A lot of times in both 50 over and t20 games the AI rarely uses a 6th (so never a 7th) bowler, and the opening bowlers will also a lot of the time bowl out 7+ overs each to start the innings, even if they are being smacked around.

Yes Sureshot said that they are doing some work on this.
But to build on that AI will never use a spinner early in an innings either, so we need to break that also.
The AI will also never pick a spinner if the wear on the pitch is "very good".

I feel the need to trawl through my old posts about bugs that I found on CC18 which I do not believe were addressed.
Because Chris said he only just became aware that the AI was picking lower order players at #4, yet I had mentioned this at least three times in the CC18 bug report thread!

So here is some other ones I have:

1. Batsmen cannot run on LBW shout
2. When a batsman is caught, and batsmen cross, strike does not change
3. Retired hurt balls not attributed to batsman
4. Partnerships do not end when a batsman retires hurt
5. Regen batsmen should not bowl F or MF
6. AI does not regard winning/drawing international series, only focuses on game
7. AI prefers average allrounders over quality specialist bowlers in ODI+T20 (will often bat allrounders to 11)
8. IPL + PSL budgets become far too static and constrained
9. Pakistan and South Africa produce superior regens than other countries
10. When viewing fixtures, the screen should open on today, rather than the beginning of the season
11. Cannot select injury replacement for international squad
12. Alastair Cook "apparently" hit 213 runs in two 2nd XI T20 matches innings at a strikerate of 108. The scores show as 120 and 93*. In order to have done this he would have faced 197 balls for these runs across the two innings, accounting for 82% of the teams total balls (240), a statistical impossibility.
13. AI never chooses NOT to follow on

[Dhruv]

Sureshot Please tweak the bowling AI, it doesn't feel real. Also previously mentioned by others like bryce87

[Sureshot]

Yes Sureshot said that they are doing some work on this.
But to build on that AI will never use a spinner early in an innings either, so we need to break that also.
The AI will also never pick a spinner if the wear on the pitch is "very good".

I feel the need to trawl through my old posts about bugs that I found on CC18 which I do not believe were addressed.
Because Chris said he only just became aware that the AI was picking lower order players at #4, yet I had mentioned this at least three times in the CC18 bug report thread!

So here is some other ones I have:

1. Batsmen cannot run on LBW shout
2. When a batsman is caught, and batsmen cross, strike does not change
3. Retired hurt balls not attributed to batsman
4. Partnerships do not end when a batsman retires hurt
5. Regen batsmen should not bowl F or MF
6. AI does not regard winning/drawing international series, only focuses on game
7. AI prefers average allrounders over quality specialist bowlers in ODI+T20 (will often bat allrounders to 11)
8. IPL + PSL budgets become far too static and constrained
9. Pakistan and South Africa produce superior regens than other countries
10. When viewing fixtures, the screen should open on today, rather than the beginning of the season
11. Cannot select injury replacement for international squad
12. Alastair Cook "apparently" hit 213 runs in two 2nd XI T20 matches innings at a strikerate of 108. The scores show as 120 and 93*. In order to have done this he would have faced 197 balls for these runs across the two innings, accounting for 82% of the teams total balls (240), a statistical impossibility.
13. AI never chooses NOT to follow on

Have passed these on to Chris and Andy.

We actually have #4 correct in the game, partnerships don't end when a batsman retires hurt in real life.

[bryce87]

Have passed these on to Chris and Andy.

We actually have #4 correct in the game, partnerships don't end when a batsman retires hurt in real life.

Oh yes come to think of it you are right. I guess the problem more is that CC attributes the partnership to just two players rather than three. Thanks.

[Dhruv]

A big bug imo that has been in since at least the last addition to my knowledge is the way the AI select bowlers, specifically in limited overs. FC is generally okay, besides the random batsman coming on first/second change, but limited overs is generally poor imo. A lot of times in both 50 over and t20 games the AI rarely uses a 6th (so never a 7th) bowler, and the opening bowlers will also a lot of the time bowl out 7+ overs each to start the innings, even if they are being smacked around.

Loving it regardless. Thanks.

Please take this into consideration, Sureshot. It's a big bug

[clamel]

Bumrah just bowled out 7 overs to start, then came in around 30th over to finish his 10 overs in an ODI vs my Kiwis. It looked strange indeed. I faced India in 5 ODI and they used 5 bowlers in 4 of those matches. Bumrah was only used in this strange match that luckily I managed to win.

I heard so much negativ talk for the difference between white and red-ball matches in this game. My thoughts (fairly a newbie) is that it is harder in whiteball but one have to play out each bowl. Several times you "catch" a no-ball situation and must put the batter to full agg to take advantage of the Free Hit. It takes a lot more micro-management to play both One-Day and T20 games. Constant checking fielding and who face who in the next situation, having the agg go up and down depending who bowl and who's on strike.
Still I think the batsmen should be a little more aggressive in the death overs and chasing a score. Even with full agg they often keep on just letting one ball after the other slip by, even if they are settled enough (50%). The match is slipping away in front of your eyes and you can't do nothing about it.

Perhaps more fielding position for the later PowerPlays in those white-ball games. You can of course create new ones but it would be nice if even the AI got a crack on selecting some more fielding setups with more blokes covering the bounderies in the last overs. As it is now the AI is more restricted than you only getting the defined fields that comes with the game. A little bit of programming changes would do nicely on that.

The key to this game is the handling in white-ball cricket. It has a little bit more steps to take to get it better IMHO.

[Dhruv]

Please fix the bowling AI
- bowlers not picked based on the pitch
- main bowlers bowling out early in the innings in od and t20
- spinners bowling at the death

Also the selection of the standard and right playing XI
specially in the IPL, which is 2nd big tournament after CWC

Please include the changes in 19.04 .

Thank you.

[clamel]

Just think I noticed something in ODI and T20 games. It's good with the extra aggr level, BUT maybe it should also be a bit of a faster period for the batsman to get settled. This is one point of view of course, but when batsmen are clearly getting to app 50% settled they start to be more aggresive even without messing with the aggr-level. This is of course natural but surely watching cricket players in white-ball format do looks to be more alert earlier than playing in red-ball cricket. It's kind of up-stressed environment and those with V-Aggr and Aggr-sets as batsman should perhaps be faster reaching good comfortable ready to start cracking them 4s and 6s. In T20 there just isn't any time to fiddle around like in a 4-5 day game. Having the aggressive level indicator perhaps even work in reverse order for those who comes in on strike, if you got the game "under control". Calming a batter down, not swinging for the fences. I know it's in the game already but it tends to my view that it's based on red-ball cricket.

Of course this takes a bit of programming, but it might make the shorter formats more easier to handle. Now they are very hard and takes a lot of micromanagement to get a win, and still the batsmen looks too calm and taking their time to get settled on strike in the death overs and lots of runs to chase down.

[bryce87]

Man of the Match Awards still have a way to go

[DaveRobbo]

Not a major bug by any means but I've noticed in two County Championship games now where the away team declines the option to bowl first without the toss, they then win the toss and proceed to bowl first anyway.

[Bearded]

I don't know if it's a bug as such but the English One Day final should be played at Lords, not in India

[biggy09]

A bug I've noticed is if you take the final wicket of the innings on the last ball of the game it doesn't acknowledge that the over has been bowled. In this SS for example, Thomas bowled out his 4th over and on the last ball he got Emrit LBW. So the total overs bowled in the game were 19, but if you add up the overs bowled in the bowling figures it is only 18, Thomas should have 4 overs bowled for his figures.

SS for reference - https://gyazo.com/ea84244e56f88ec998c8818a212f1a82

Having gone back and tracked his overs bowled through the season, the over is being counted in the stats, just not showing up on that specific match score sheet. Cheers.

[Sureshot]

I don't know if it's a bug as such but the English One Day final should be played at Lords, not in India

This has been fixed for the next patch.

[Lojoda]

A bug I found is when a bowler takes 19 wickets in a match, the records screen for the country is not updated