Features you want to see in next iteration of Big Ant Cricket

Players getting injured in a match.Would like to see this feature especially in a career mode.Players pulling up their muscles,cramps,hamstring would be fascinating.
 
Pitch marker! (Yeah I said it)
It can easily have an on/off option for those who don't want it there.
For anyone saying "it just takes practise" I offer you a challenge. Put the game down for 2 weeks and then come back to it. You will then realise how you need to constantly play the game to stay good.
 
Automatic changing of umpires - different umpires - for each game or throughout a series. Perhaps can choose 4 or so who will be the umpires for a series or tournament and they are automatically changed for each game.
Expanded commentary - I'm actually not too fussed that the commentary isn't by supposed well-known commentators. I find it more interesting and really, after a certain point you're not really listening to it anyway. Obviously with more dialogue and a bit better linking to the action so less irrelevant comments aren't happening, will only enhance the experience.
Better night time lighting - still only one shadow at night.
Some different batting and bowling actions.
More crowd interactivity - more noise relating to scenarios happening on the field and maybe even crowd catches from time to time.
More stadiums - they wouldn't have to be real. The created ones are fine.
Lastly, have outfields as they are in different parts of the world, i.e. subcontinent outfields aren't exactly full of lush, manicured grass.

Cheers:)
 
Pitch marker! (Yeah I said it)
It can easily have an on/off option for those who don't want it there.
For anyone saying "it just takes practise" I offer you a challenge. Put the game down for 2 weeks and then come back to it. You will then realise how you need to constantly play the game to stay good.

but with current mechanics that still wouldn't help you much - only at point of releasing ball does game know where ball would pitch - against a fast bowler you still would have 0.5 of sec (approx.) to play your shot?

I.e. leave it as it is :p
 
I'd like to see some sort of different mechanism for taking catches in a future iteration. Using the stick feels quite good for reflex catches in the infield, but when it comes to skied shots that take a while to come down, it is far too easy to just hold down sprint to get into position and point the right stick towards the ball. It is pretty much impossible to drop these catches.

I actually quite liked the way AC09 did it, with the slo-mo QTE you had to time. The easier catches were quite simple to take but still droppable and tough diving chances needed much more accurate timing.

I don't recall a grading system in AC09 for catches. You were as likely to drop a sitter as a perfectly timed shot at short cover. All catches were equally difficult which wasn't realistic.
 
I don't recall a grading system in AC09 for catches. You were as likely to drop a sitter as a perfectly timed shot at short cover. All catches were equally difficult which wasn't realistic.
Oh okay, maybe I'm wrong - it has been years since I played AC09. I remembered the QTE style catching but maybe just projected the varying difficulty onto it :p.
 
I don't recall a grading system in AC09 for catches. You were as likely to drop a sitter as a perfectly timed shot at short cover. All catches were equally difficult which wasn't realistic.

I think we did: the colours just changed slower? Although possible that was added in IC10... The difference between a wicket keeper/slips catch compared to an outfield skier was really noticeable.

The best system I could come up with is one where you control the hands with the two analogue sticks and have to keep them as close to the ball as you can as it comes towards you in slow motion: they are easier to control depending on the ability of the player.
 
i strongly dispute that the lack of edges are down to people not bowling well/right.

the edge system just isn't right, full stop. there "being edges" is not disputed, but nor does it refute the fact that there aren't enough, nor enough variation in types of edges... you should get edges that go wide of the slip, that don't carry, that fly over them etc. currently the human will edge and 99% got to WK and caught. the AI edges extremely rarely, and even more rarely to slip.

I don't think edges aren't too bad, but I just don't understand how they're happening. I seem to edge it all the freaking time, if anything they're too frequent, I'd say I edge a ball once every 20 deliveries facing fast bowlers and my career player is a no. 5 not facing the new ball.

but yeah, the AI very rarely edges, but probably that's realistic. Edges are the most common dismissal but overall, with a SR of 60 being the norm and edging accounting for about 2 every 5 dismissals (Blogs: Analysing Test dismissals across the ages | Cricket Blogs | ESPN Cricinfo this article states the type of dismissals but there's no way to see which fielder catches are caught in the deep or the ring and which ones are slip catches. I'm guessing about half and half) that's about 1 edge for every 120 balls. chuck in dropped edges, non-carrying ones, ones wide of the fielders or in the gaps and I think you'd probably get to about 1 edge every 30-40 balls for an average, good fast bowler. It may be less for some that rely on inswinging yorkers to get LBWs and bowleds.

so they aren't mega common, maybe they could be a bit less predictable in direction though, but I really don't think Big Any should spend loads of time making ways to get out more likely. the game is essentially goosed if batting remains as impossible as it has been.
 
I don't think edges aren't too bad, but I just don't understand how they're happening. I seem to edge it all the freaking time, if anything they're too frequent, I'd say I edge a ball once every 20 deliveries facing fast bowlers and my career player is a no. 5 not facing the new ball.

but yeah, the AI very rarely edges, but probably that's realistic. Edges are the most common dismissal but overall, with a SR of 60 being the norm and edging accounting for about 2 every 5 dismissals (Blogs: Analysing Test dismissals across the ages | Cricket Blogs | ESPN Cricinfo this article states the type of dismissals but there's no way to see which fielder catches are caught in the deep or the ring and which ones are slip catches. I'm guessing about half and half) that's about 1 edge for every 120 balls. chuck in dropped edges, non-carrying ones, ones wide of the fielders or in the gaps and I think you'd probably get to about 1 edge every 30-40 balls for an average, good fast bowler. It may be less for some that rely on inswinging yorkers to get LBWs and bowleds.

so they aren't mega common, maybe they could be a bit less predictable in direction though, but I really don't think Big Any should spend loads of time making ways to get out more likely. the game is essentially goosed if batting remains as impossible as it has been.


there is no way you can generate AI (I am talking about AI only) edges every 30-40 balls in DBC. 300-400 maybe. and there is very little variation. the AI edge system is way, way off and not realistic at all
 
there is no way you can generate AI (I am talking about AI only) edges every 30-40 balls in DBC. 300-400 maybe. and there is very little variation. the AI edge system is way, way off and not realistic at all

That's why I think adding square drive shot in the game can solve that edges issue as square drive when not timed well can create edges to slips based on the force and timing of the shot...So slips and gully catches are very much possible if included....
 
there is no way you can generate AI (I am talking about AI only) edges every 30-40 balls in DBC. 300-400 maybe. and there is very little variation. the AI edge system is way, way off and not realistic at all

I haven't played my bowler enough but I definitely get them more than every 100 balls. my batsman gets 2-3 overs of off spin in ODI matches and he's got about 3 or 4 edged outs with about 10 games played. they haven't been blocks, but yeah, got one coming off the top of a reverse sweep just the last game I played and I only bowled 2 overs.

the few games I have played with my proper bowlers I've had a couple of edges too, though I'd like a few more seeing as this is a specialist bowler and I think I managed two in about 25 overs (including one annoying one that made no sound and I never appealed.)

it's odd really, because it does seem my experience is different to yours, I would like them a bit more but not 10 times more, that to me would be the ball flying off the edge all the time. whereas you can probably survive more than 15 balls an innings, whereas to me that's just not going to happen.
 
Last edited:
I haven't played my bowler enough but I definitely get them more than every 100 balls. my batsman gets 2-3 overs of off spin in ODI matches and he's got about 3 or 4 edged outs with about 10 games played. they haven't been blocks, but yeah, got one coming off the top of a reverse sweep just the last game I played and I only bowled 2 overs.

the few games I have played with my proper bowlers I've had a couple of edges too, though I'd like a few more seeing as this is a specialist bowler and I think I managed two in about 25 overs (including one annoying one that made no sound and I never appealed.)

it's odd really, because it does seem my experience is different to yours, I would like them a bit more but not 10 times more, that to me would be the ball flying off the edge all the time. whereas you can probably survive more than 15 balls an innings, whereas to me that's just not going to happen.

again, you're bringing human batting into it. i'm talking AI batting, human bowling. my main experience is of bowling in casual matches, FC and AI edges are far too rare.
 
but they're linked surely? the problem will probably be more to do with the AIs decision making, it seems to overly punish itself, meaning if it misjudged the line instead of being corrected to get closer to the ball it flashes wildly.

I get way more edges than the AI but I play and miss an awful lot less. I edge because if I see a fast bowler bowl straight at me after bouncing me 19 times in a row I panic and try and block, sometimes I just instinctively push forward and the ball is going more off so get an edge. whereas the AI seems react by misreading a ball and trying to heave it over leg when it's outside off.

I definitely don't find it as bad as you're saying, what I was suggesting by bringing in my ability to face fast bowling was that, for whatever reason, I am just better at bowling than you where you are probably better to bat much better than me. I look at the review thing to see the pitch bounce, check the batsmans weaknesses and then try and set a field to encourage him to play to those weak spots. in this regard I think it almost kinda works quite well, and doing this do manage to find the edge way more than once every 300 balls.
 
Last edited:
I think we did: the colours just changed slower? Although possible that was added in IC10... The difference between a wicket keeper/slips catch compared to an outfield skier was really noticeable.

The best system I could come up with is one where you control the hands with the two analogue sticks and have to keep them as close to the ball as you can as it comes towards you in slow motion: they are easier to control depending on the ability of the player.

I was talking about AC09 and don't recollect slip catches being any different from outfield ones.
 
but they're linked surely? the problem will probably be more to do with the AIs decision making, it seems to overly punish itself, meaning if it misjudged the line instead of being corrected to get closer to the ball it flashes wildly.

I get way more edges than the AI but I play and miss an awful lot less. I edge because if I see a fast bowler bowl straight at me after bouncing me 19 times in a row I panic and try and block, sometimes I just instinctively push forward and the ball is going more off so get an edge. whereas the AI seems react by misreading a ball and trying to heave it over leg when it's outside off.

I definitely don't find it as bad as you're saying, what I was suggesting by bringing in my ability to face fast bowling was that, for whatever reason, I am just better at bowling than you where you are probably better to bat much better than me. I look at the review thing to see the pitch bounce, check the batsmans weaknesses and then try and set a field to encourage him to play to those weak spots. in this regard I think it almost kinda works quite well, and doing this do manage to find the edge way more than once every 300 balls.

I agree i am not a brilliant bowler, but equally i am not terrible. If the game expects mcgrath accuracy to get an edge that's a major design flaw because all bowlers can get edges and virtually none are as accurate as mcgrath! The game doesn't allow the "magic" ball - who gives a toss that i sorayed the first 5 down leg side that one pitched on off and moved away and you nicked it sucker! That doesn't exist as far as i can tell.

Youre right in that the AI behaviour is a massive issue, as i and others have said it's basically middle or miss, but the fact that 99% of edges are thin edges, very very few thick, and very little other variation in height, speed and carry suggests that the system is just wrong. Between patch 2 on xbox and PC i reckon i have bowled upwards of 500 overs. I don't think i have seen 10 AI edges. I am not getting smashed around at 10 or more an over... I have tried different conditions, including setting a greentop, uneven bounce, heavy cracks to no discernible effect; i can get visible swing and spin (seam appears not to exist). I get less than 1 edge per 300 balls. Something is massively wrong somewhere.
 

Users who are viewing this thread

Top