Hello folks,
I know I'm reviving a thread for a finished project in an out of date game. But I hope you folks can help me.
My question is simple: Are "bowled top of off" wickets possible? I am about to finish an Ashes series, where I have had great fun, using these settings (albeit tinkered a little with the pitch/ball friction, and reskilling players). But I have found it impossible to get this dismissal. Generally, my dismissals are in order of frequency: Chopped on, edged caught slip/WK, short ball caught behind, caught in the deep, bowled from a miss, LBW, castled (last two are very rare). "Top of off" has never occurred. Is it just the way I bowl, or can I change some settings. Or is it yet another flaw in the game. In fact bowling over a player with a pacer tends to not happen, unless its chopped on.
I generally think its the latter of the three, with the defensive shot being far too powerful. If it does fail, generally it is a nick.
Sadly, you're going to be out of luck.
It is a LONG time since I played this game, and I didn't get C24 as it was always going to be guff, but if a player gets bowled, it is highly likely to be one of the following as you say:
A chop on - like this with a big edge on the cut or pull
Or even worse this nonsense
Or this fine one
Or this
The AI playing to leg and missing the ball -
There's another variation to this where they play much squarer with a leg glance, but it's the same result. Hoik across the line, miss, stumps go.
The only genuinely nice looking bowled I can remember was using India against England, when I managed to get one through the gate with the spinner against Rory Burns, but even then it took an inside edge
As you say, defensive shots really only get the edges that go to slip or the keeper, like this one
But at least they feel nice when they do.
Going through my back catalogue of wickets from that game, this looks to be the closest I came to top of off
I think it is because the AI is programmed to only get out at certain times. So the one above missed the bat only because it was also going to miss the stumps.
You can "feel" when a wicket is coming a lot of the time, and you also get spells where chances come (the rocket edges that fly to the boundary and magically find a gap every time) but the AI just isn't meant to lose a wicket yet.