Ashes Cricket General Discussion

[Wealey]

Edging half volleys might not be an issue in itself but it all depends on frequency of the occurrence. I would prefer a batsman edging a half volley once in a blue moon or in case the shot or timing was incorrect. And on flat wkts, edging a half volley should be even rare. But in a video game, users need to know why they were dismissed - poor shot selection, poor footwork, poor timing etc. - or in a very rare case a dismissal despite everything being correct but that has to be a very rare event.

From my perspective that would be my feedback to beta folks and Big Ant team, i.e. to make sure that you edge for a reason, i.e. trying to drive a ball which is not quite full or the batsman driving to far from the body without reaching the pitch of the ball (i.e. poor footwork) or batsman is late etc. In other words I wouldn't want to have edges just for the sake of it. There has to be a cricketing reason which the end user can understand and improve upon.

I completely get what your saying, but god knows if that’s possible... but tbh anything I have timed I haven’t Edged.

In a perfect world your spot on. But I have no idea if feesible.

However like I said, it wasn’t perfect input.

 

[Wealey]

However I will add if people can’t have fun with the buid I’m playing now, then I’m not sure you ever will.

There’s only so much scrutinising you can do

 

[cricket_online]

I completely get what your saying, but god knows if that’s possible... but tbh anything I have timed I haven’t Edged.

In a perfect world your spot on. But I have no idea if feesible.

However like I said, it wasn’t perfect input.

It may not be but do pass on the feedback to Big Ant to see if it's feasible. If not then maybe they should have it on their priority list for the next iteration.

Edit: Or maybe Big Ant can share with us which batting modifier(s) to adjust to increase or decrease the edge frequency so folks can customize the batting experience to their liking

 

[blockerdave]

Yes, that may be the case but it is about a process.....so first they were not edging, now we have them edging........I do not want to get in to a us and them mentality.....I do not work for BA, I don't get paid or whatever...we show some stuff here because we are cricket nuts like yourself, have been somewhat disappointed in some of the things in the game and are trying to help to get things to a place that everyone can feel it is a good game of cricket.....I didn't invent that process or feel responsible for it: I am trying to constructively and with understanding work towards a better iteration of this game. I understand the frustration as well of there being a small group of so-called insiders who are privileged to play a version of the game that is in some ways is perhaps better than the game others are playing.....unfortunately the process is one that is taking time, will take time. In the end there is hopefully a game that will be the better for it.

I understand that. I certainly have no beef with anyone in the beta since i know exactly where you're coming from.

Inside or outside the beta I've always given my honest opinion, no sugar coating. For good or ill, in victory or defeat I just want to feel what I'm seeing is down to what I've done, and I can't feel that when there's no internal logic to the outcome.

I don't want to discourage you fellas from posting updates because hell knows this place is all the better for it! But equally when I see an issue like that, it's something I feel justified in commenting on.

 

[Dutch]

The good: some beautiful wickets: batsman genuinely beaten by the ball.
Ali was ineffective until around 68 odd overs, late in the day and took four wickets, the three bowled's absolute gems. The Smith wicket was a shocker: will come to that.
The new ball was very effective: Broad taking his wickets in his first couple of spells and right at the end, first ball of his first over with the new ball, absolutely obliterating Starc's woodwork
Once Lyon was out and Starc only had Hazlewood for company he went absolutely mental!
The game went to and fro....the middle order propped things up, the last wicket stand frustrated.
Had a couple of LBW's turned down......pitching outside leg.

The bad: the runout was a glitch, the one that two batsman just stand at one end until you throw down the stumps.
Smith's wicket was 'orrible: caught of his pad with the bat a mile away and he didn't review.

 

[blockerdave]

I don't think I am.
I would actually venture to say that there many other members in this thread who take it all way more personally than me: that the state of the game is an attack by BA on their personal integrity and lives. I certainly don't see it that way at all. I take it seriously, sure, and am not blind to that which still obviously needs tuning or looked at and am also not arrogant enough to think I see and know everything.

As the great Socrates said when the people asked him whether he was the wisest: after going about meeting many people he came back and said: yes I believe I am the wisest, as I am the only one who doesn't think he knows everything!
(Meant to be tongue in cheek for those unable to discern the difference.)

Reminds me of what they used to about Amos Tversky - that the sooner you realised he was smarter than you, the smarter you were.

 

[Dutch]

The good: some beautiful wickets: batsman genuinely beaten by the ball.
Ali was ineffective until around 68 odd overs, late in the day and took four wickets, the three bowled's absolute gems. The Smith wicket was a shocker: will come to that.
The new ball was very effective: Broad taking his wickets in his first couple of spells and right at the end, first ball of his first over with the new ball, absolutely obliterating Starc's woodwork
Once Lyon was out and Starc only had Hazlewood for company he went absolutely mental!
The game went to and fro....the middle order propped things up, the last wicket stand frustrated.
Had a couple of LBW's turned down......pitching outside leg.

The bad: the runout was a glitch, the one that two batsman just stand at one end until you throw down the stumps.
Smith's wicket was 'orrible: caught of his pad with the bat a mile away and he didn't review.


View attachment 206105

Buuuut....England put the Aussies into bat......and will feel justified in doing so but the Aussies have 300 on the board.....a balanced and competitive days play!

Buuuut...as I am not that good at batting it's probably more than enough!

 

[blockerdave]

I've been edging the ball since day one. There was a little dry spell but they returned with a vengeance when I upped the minimum bowling speed and went to hardest batting. I've had some cracking batting experiences lately with only minor adjustments.

It really amazes me how big an issue this is.

I edge too!

 

[blockerdave]

Edging half volleys might not be an issue in itself but it all depends on frequency of the occurrence. I would prefer a batsman edging a half volley once in a blue moon or in case the shot or timing was incorrect. And on flat wkts, edging a half volley should be even rare. But in a video game, users need to know why they were dismissed - poor shot selection, poor footwork, poor timing etc. - or in a very rare case a dismissal despite everything being correct but that has to be a very rare event.

From my perspective that would be my feedback to beta folks and Big Ant team, i.e. to make sure that you edge for a reason, i.e. trying to drive a ball which is not quite full or the batsman driving to far from the body without reaching the pitch of the ball (i.e. poor footwork) or batsman is late etc. In other words I wouldn't want to have edges just for the sake of it. There has to be a cricketing reason which the end user can understand and improve upon.

To add complexity, there's more to it than that... it' not just length, it's line. A fraction too wide and the edge probability goes up as you lose control.

Then there's players ability for the drive etc.

So many parts.

 

[79cricket]

I edge too!

Some do but most don't edge it. I happy to hear that the problem has been fixed and I can't wait to test.
Never happened in there last 2 games so no idea why Ashes had this happen.

 

[79cricket]

I've been edging the ball since day one. There was a little dry spell but they returned with a vengeance when I upped the minimum bowling speed and went to hardest batting. I've had some cracking batting experiences lately with only minor adjustments.

It really amazes me how big an issue this is.

I must say you love to say the same quote over and over again, we get it you edge it but a lot don't and have had this problem from day one.
There should be no tweak to make edges happen, just has to be part of the game and goes up as you move up the difficulty levels. PS I edged on easy sometimes on DBC17.

Anyway thanks to the Beta team for there hard work.

 

[cricket_online]

To add complexity, there's more to it than that... it' not just length, it's line. A fraction too wide and the edge probability goes up as you lose control.

Then there's players ability for the drive etc.

So many parts.

There is. All I'm saying is that edges should not be based on a dice roll. It should be based on some cricketing logic, and which the game should be able to tell the users as part of feedback mechanism so the users know why they edged and improve.

 

[Dutch]

Not needed

 

[Dutch]

Okay I can't be arsed after all.

 

[wasteyouryouth]

Some do but most don't edge it. I happy to hear that the problem has been fixed and I can't wait to test.
Never happened in there last 2 games so no idea why Ashes had this happen.

Have you done a survey?

I don't see how it's a problem that needs to be fixed. It seems a subjective issue as to why some do and some don't get edges. Unfortunately that level of nuanced thinking seems to be beyond many people; if they don't get edges then they aren't in the game at all. I do have confidence that the beta testers think of it in terms of cause and effect rather than just saying "we want more edges."

I'm merely in the sceptical camp of @blockerdave and @cricket_online (sorry if I am misrepresenting your viewpoint), in that I would want an increase of edges to be a result of something more complex than just turning up or turning down the ''edge frequency" number.