Ashes Cricket General Discussion

What bowling difficulty were you playing on? Currently I'm weary of going higher than Hard because Hardest seems just a bit too punishing. But if it gets to a point where the AI respects actual good bowling and can't just smash a four or six whenever they want then Hardest might be the way to go.
It shouldnt matter which bowling level you play at to be fair; the ai should play in a certain way appropriate to the match format and match situation. Timing windows is the only thing that should increase/decrease with the different difficulties and the ai’s ability to counter what you chuck at them, that is what is being striven for.

If I as a user find amateur my level then I deserve an authentic experience just like the person playing on legend.

What should make a huge difference is Milton Keynes against Australia, whatever the user difficulty.[DOUBLEPOST=1519293118][/DOUBLEPOST]Another aspect being worked on is human batting: how to tweak things so that you can play the ball as it pitches rather than out of the bowlers hand, and have a reasonable risk/reward equation. Again this needs to be reflected differently in different formats and with different mentalities and skills.
 
Last edited by a moderator:
It shouldnt matter which bowling level you play at to be fair; the ai should play in a certain way appropriate to the match format and match situation.

But if you're playing on easy bowling and can land every ball to hit the top of off then wouldn't an "authentic" experience being the AI struggling to score, leading to lower run-rates and more chance of wickets.

AI should play based on where the ball is bowled (most of the time anyway). Difficulty level should determine how hard it is for you to bowl where you want it. That's what I'm getting at
 
Not sure whether this issue has been mentioned before but just to add to the list..

The cross delivery works fine but the way it's bowled , the ball position is wrong or shall I say reversed in action...The initial release is the way ball should be after bouncing and vice versa..
 
What are everyone's views on whether this game would more polished if DBC17 had never been released. If they'd have got the license pre-DBC17 development they may have not released in 2016 and had longer to work on Ashes. However, was it a vital step in stress testing their mechanics, etc, and is it better having Ashes as the third iteration rather than a second iteration?

Or would BA have needed the cash from DBC17 to develop Ashes. I won't pretend to know about the licensing deal, but I imagine the license holders just take a cut of sales rather than BA having to bid for the license.
 
But if you're playing on easy bowling and can land every ball to hit the top of off then wouldn't an "authentic" experience being the AI struggling to score, leading to lower run-rates and more chance of wickets.

AI should play based on where the ball is bowled (most of the time anyway). Difficulty level should determine how hard it is for you to bowl where you want it. That's what I'm getting at
Yes and no. It depends what the goal is of the different user settings: I believe user settings should allow the user to select a level that gives them a satisfactory experience rather than an easy one: each level should represent a challenge.

If I am good at the game I will find rookie too easy but whether I am on rookie or legend I should have an ai scoring and playing realistically and appropriately
 
Yes and no. It depends what the goal is of the different user settings: I believe user settings should allow the user to select a level that gives them a satisfactory experience rather than an easy one: each level should represent a challenge.

If I am good at the game I will find rookie too easy but whether I am on rookie or legend I should have an ai scoring and playing realistically and appropriately

I'm not sure we're even disagreeing. With the approach I'm suggesting a weaker player will bowl more bad balls even on easier difficulties.

On the current live build the AI only really respects good bowling some of the time, if they need to they can hit boundaries whenever they please. On the build @WealeyH is talking about it appears they maybe respect good bowling a bit too much. Which is why I asked what the difficulty was to see if bowling more bad balls led to increased run-rate. Unless he's a bowling god it seems this is not the case.
 
I'm not sure we're even disagreeing. With the approach I'm suggesting a weaker player will bowl more bad balls even on easier difficulties.

On the current live build the AI only really respects good bowling some of the time, if they need to they can hit boundaries whenever they please. On the build @WealeyH is talking about it appears they maybe respect good bowling a bit too much. Which is why I asked what the difficulty was to see if bowling more bad balls led to increased run-rate. Unless he's a bowling god it seems this is not the case.
I guess it is about tweaking ai to play in a way that is appropriate to the match and the format: in T20 we want them launching it, in FC not., unless its the tailenders having a wallop or a well set batsman punishing tired bowlers or whatever. At the same time they need to post appropriate and challenging scores. I have come to the conclusion and appreciation that it is a very very complicated thing to get it right! It nearly asks for them to release three seperate versions of the game!
 
No batting second.
I always prefer to chase. Just simulate the bowling and bat.

Will try to share some screenshots of the nice AI field sets at various stages of odi innings.

One was I tried a lofted shot over mid off and mistimed it, runrate req was 8 , next ball AI had a fielder on deep mid off.

interesting.

when i have chased i find this is when the AI uses the ring field, changes more often etc.
 
I guess it is about tweaking ai to play in a way that is appropriate to the match and the format: in T20 we want them launching it, in FC not., unless its the tailenders having a wallop or a well set batsman punishing tired bowlers or whatever. At the same time they need to post appropriate and challenging scores. I have come to the conclusion and appreciation that it is a very very complicated thing to get it right! It nearly asks for them to release three seperate versions of the game!

Is this sort of match scenario specific stuff even possible with how the game is coded? That is not something I'm expecting to be accurately portrayed, although something like if the AI has a target of 120 to get in the final session of a test match I would definitely expect them to try and go at 4 an over (unless they lose a bunch of wickets of course).
 
Is this sort of match scenario specific stuff even possible with how the game is coded? That is not something I'm expecting to be accurately portrayed, although something like if the AI has a target of 120 to get in the final session of a test match I would definitely expect them to try and go at 4 an over (unless they lose a bunch of wickets of course).
I guess that you have to throw up if that possible tho if u no what I mean
 
interesting.

when i have chased i find this is when the AI uses the ring field, changes more often etc.
Yes the ring field pops up every now and then but only in the first 10 overs.
 

Users who are viewing this thread

Top