Cricket 24 - General Discussion

We could if Wouldubeinta also adds a script packer to his Blobset tools. The config files for weather and lighting are there once you extract the game. The .Lua files are compresse though I think and we'd need that script compiler that he's made available in the past.
thanks for suggestions, how to use Wouldubeinta would be appreciated
 
I just realised that some boundaries (4s) aren't getting registered. It happened twice in a single test match. It happened at Lord's. I don't know if it is happening due to the shape of the ground.
 
Bowling in this game is one of the worst gaming experiences of all time I don't think I've ever gotten the AI out bowled. Does anyone else just bat and then simulate the bowling innings?
 
Bowling in this game is one of the worst gaming experiences of all time I don't think I've ever gotten the AI out bowled. Does anyone else just bat and then simulate the bowling innings?
I find it much easier when playing T20s, but it's terrible in tests. I keep bowling consistent lines and lengths for 20 overs straight and I still have no luck with getting wickets.
 
Bowling in this game is one of the worst gaming experiences of all time I don't think I've ever gotten the AI out bowled. Does anyone else just bat and then simulate the bowling innings?

I've been batting for both teams for some time now. Not because I can't get wickets, but because bowling feels so dull. It just feels so random, with seemingly little reason behind wickets when they do fall. I'm not entirely sure how, but the bowling mechanics need some improvement to make the experience feel engaging and rewarding.
 
Bowling in this game is one of the worst gaming experiences of all time I don't think I've ever gotten the AI out bowled. Does anyone else just bat and then simulate the bowling innings?
When you eventually get one it's scripted for the AI to play around the ball so it hits the stumps.

Even BL05 and Cricket 07 made those dismissals natural occurrences
 
I find it much easier when playing T20s, but it's terrible in tests. I keep bowling consistent lines and lengths for 20 overs straight and I still have no luck with getting wickets.
I've been batting for both teams for some time now. Not because I can't get wickets, but because bowling feels so dull. It just feels so random, with seemingly little reason behind wickets when they do fall. I'm not entirely sure how, but the bowling mechanics need some improvement to make the experience feel engaging and rewarding.
One thing I have sort of worked out is that bowling the length in the yellow seems to have moderate success, certainly more than the ideal length indicator. Most wickets I take are the AI smashing a hook shot to the boot laces of short leg which gets annoying after a while. I can get about 30 edges an innings but 28 of them instantly hit the ground which is frustrating. I hate the way your swing/seam is either nothing or exaggerated there's no subtle movement.

Bowling to plans doesn't work as there is no way to genuinely get a batter out, creating pressure with maidens doesn't work because the AI can easily smash a boundary even when they are in the red for confidence and the biggest disappointment is that the pitch doesn't matter because it will still seam a lot on a dustbowl and turn sideways on green tops and the pitches don't deteriortate either I am currently playing Pakistan v India in Chennai on a late day 3 pitch that is on fast wear and the only change to the pitch is one medium sized crack on a good length there aren't even any foot prints showing.

It's real annoying the SWC 99 and the early 2000s EA cricket games were able to nail pitches but Big Ant can't get one of the most important aspects of the sport implemented.

When you eventually get one it's scripted for the AI to play around the ball so it hits the stumps.

Even BL05 and Cricket 07 made those dismissals natural occurrences
I am finding the AI is leaving balls and has play & misses because it knows the ball will go over the stumps. I've never had a yorker get a bowled dismissal and only rarely I might get an edge fly to gully or something. The wickets just feel like the AI are getting themselves out because it's that time in the script to be dismissed.

Question for everyone: This is me bowling, what happens next in this screenshot?
20250629170900_1.jpg

If you answered with the batsman getting safely back in to his crease before the wicketkeeper even begins to attack the sumps despite you immediately pressing the button for the stumping you are correct, incredibly frustrating. Also does that pitch which has fast deterioration setting look like there's been 150 odd overs bowled at the time?
 
Question for everyone: This is me bowling, what happens next in this screenshot?
View attachment 305824

If you answered with the batsman getting safely back in to his crease before the wicketkeeper even begins to attack the sumps despite you immediately pressing the button for the stumping you are correct, incredibly frustrating. Also does that pitch which has fast deterioration setting look like there's been 150 odd overs bowled at the time?
It's a little thing, and in the grand scheme of the issues with recent games it is waaaay down the list, but show me a close fielder in the world that isn't turning away/hands on head/ducking/taking cover at a shot like that when they're fielding that close

Instead he just holds his identical pose to the slip fielder and waits to see if he's eating one from 3 yards away.
 
@Bluebagger While bowling the AI will give scripted wicket. This is the limitation of the gameplay. Even against the human opponent (as in pro-team) its difficult to get bowled and LBWs. One of the reason is, the batsman (AI or human) as oppose to actual cricket cannot play those 'across the line midwicket slog' or 'slice over cover' to get quick runs and in the process get bowled. In C24 those unorthodox does not connects properly so nobody uses those, so goes the chances of getting a bowled dismissal.
 
Finding this really poor. Have been bowling a really good consistent line until the AI just starts stepping across the stumps and whacking 94mph balls to the leg side, with that hideous hook animation.

If it’s this bad now, I can’t imagine what it was like at launch. Just noticed they’re launching RL26 when their cricket and rugby union games are still a mess. Rugby 25 in particular is pitiful.
 
At one point it was working ok now its regressed a lot.It won't be fixed they are already working on cricket 26 which i think will have the same release schedule as afl 26.Quick announcement and then available 2 weeks later.Nov-Dec time my guess.
 
At one point it was working ok now its regressed a lot.It won't be fixed they are already working on cricket 26 which i think will have the same release schedule as afl 26.Quick announcement and then available 2 weeks later.Nov-Dec time my guess.
Unless they've rewrote the entire engine from scratch, it'll be Cricket 22 v3.0. There's five animations which if I still see in this new release I shall be going postal.
 

Users who are viewing this thread

Top