Batting experience in the Next Version

[T.J.Hooker]

If the bowler fielding is toned down then the batting angle of the shot needs to have more uncertainty such that only a perfectly timed shot goes dead straight, and poorer shots go to mid on/off.

I'd say it just needs to be difficult enough to generate real power down the ground, and it needs to be something of a skill. There are plenty of test batsmen who just don't have a lot of power straight.

Mike Atherton, for instance :

 

[cooks1st100]

For batting we need more skills. Say a person is a good front foot cover driver, a good hooker but a bad cutter, how would you rate him? High offside or low offside? High backfoot or low backfoot? There arent enough skills to make every individual seem different, that and a shot through midwicket are all I need for batting to feel almost perfect...

I have mentioned for a while the idea of having a shot editor which would be assigned individually shot that every single shot could be tweaked and again giving a sense of individuality, it would be along the line of this:

Shot: Straight Drive:
Animation: A choice of animation for the particular shot.
Timing: Size of timing window
Range: Think of this as a cone. For a more precise shot, the cone would be smaller and vice versa.
Power: I would like a slider for this.
Edge: The edge probability from playing this shot. Maybe just low, normal, high.
Middle: A rating for how easily batsman finds the middle with this particular shot. Maybe just low, normal and high, or possibly a smaller timing window, inside the timing window.
Middle range: Same as range but for when you middle the ball.
Middle Power: As above.

The range, timing, middle and edge attributes would fluctuate in-game dependant on performance and as particular shots are played.

 

[Deleted member 149013]

I don't think what I've suggested would require any additional processing power than is currently in the game, especially with the right data structures.

Most of what I'm suggesting is purely academy data configuration and everything is known prior to to delivery - nothing additional is required to be calculated on the fly than what would be done now, though it might be processed differently.

Importantly, my concept essentially requires no AI - the batsman's vulnerability is known, the bowler's plan(s) are set in advance - the picking of an individual plan or field doesn't need a smart AI.

The reason I would prefer my suggestion over the similar idea of @cooks1st100 is precisely that there's no AI or overhead. Allied to that it gives infinite flexibility and variation of opponent and importantly how you bat with a given player:

Eg an Alec Stewart type, vulnerable vs spin first up, could murder it when well set. So with my set up you have that genuine immersion of playing more watchfully against a certain type of bowler or bowling at certain times in your innings.

You’ve stumped me on this one Dave. If your bowling/batting/fielding plans work then maybe you should be working at Big Ant.

You seem to have a good grasp on how best to improve the game..

 

[Markkkkk]

I have mentioned for a while the idea of having a shot editor which would be assigned individually shot that every single shot could be tweaked and again giving a sense of individuality, it would be along the line of this:

Shot: Straight Drive:
Animation: A choice of animation for the particular shot.
Timing: Size of timing window
Range: Think of this as a cone. For a more precise shot, the cone would be smaller and vice versa.
Power: I would like a slider for this.
Edge: The edge probability from playing this shot. Maybe just low, normal, high.
Middle: A rating for how easily batsman finds the middle with this particular shot. Maybe just low, normal and high, or possibly a smaller timing window, inside the timing window.
Middle range: Same as range but for when you middle the ball.
Middle Power: As above.

The range, middle and edge attributes would fluctuate in-game dependant on performance and as particular shots are played.

Exactly, although this would be a pain to make via the academy it would make the game as realistic as possible...

 

[isrararrafi]

I love @blockerdave 's idea about bowling plans.

 

[Dutch]

You’ve stumped me on this one Dave. If your bowling/batting/fielding plans work then maybe you should be working at Big Ant.

You seem to have a good grasp on how best to improve the game..

He nicked all his ideas off Tazzron....cheeky!

 

[cooks1st100]

I love @blockerdave 's idea about bowling plans.

This feels like when you tell a joke and no-one laughs, then someone else tells it a few minutes later and everybody p****es themselves!!

 

[cooks1st100]

I'd like to see a feature similar to that of Cricket Coach and be able to design bowling plans which then could be assigned to individual bowlers. The more skilled the bowler equals the better execution of the plan. This would improve the AI bowling a great deal and by being able to share the plans via the academy the possibilities would be endless.

A bowler could be assigned 5 plans for each: Attacking, Normal, Defensive. This would mean if you were to face a team with 5 bowlers you could potentially be facing 25 different ways the AI would be trying to take your wicket and each team could be set up uniquely.

Post [HASHTAG]#1093[/HASHTAG] Jan 24 2015!! LOL!!

 

[blockerdave]

Post [HASHTAG]#1093[/HASHTAG] Jan 24 2015!! LOL!!

it's the way I tell em

 

[Biggs]

I'm sure I've said this before as well. So let's just do the logical thing and credit me for it from here on out...

 

[cooks1st100]

TBH I'm glad we're thinking along the same lines and others agree. I feel it would be a major step forward.

@blockerdave in regards to your earlier reply regarding taking the AI out of it. I feel that it will still need to know when to apply attacking plans and when it should be more defensive. Otherwise there could very well be situations when unsuitable plans in relation to the game situation would be implemented. How would you suggest this could be managed?

 

[blockerdave]

TBH I'm glad we're thinking along the same lines and others agree. I feel it would be a major step forward.

@blockerdave in regards to your earlier reply regarding taking the AI out of it. I feel that it will still need to know when to apply attacking plans and when it should be more defensive. Otherwise there could very well be situations when unsuitable plans in relation to the game situation would be implemented. How would you suggest this could be managed?

By having vulnerabilities per innings stage for the batsman, which would determined be a combination of combination of runs scored, balls faced and confidence. The "AI" is only determining the switch to a new stage, the plans for the stage is set by the academy configuration.

 

[Ajh1977]

The only problem I can see with that idea if you are going to use vunerabilities is, say your player is weak vs spin early in his innings, and you're behind the run rate with not many overs left and the spinners are on, how do you attack and up the run rate if you need to play yourself in? Would you introduce something different for different formats, (test,ODI,T20)

 

[Gamer Pradosh]

The only problem I can see with that idea if you are going to use vunerabilities is, say your player is weak vs spin early in his innings, and you're behind the run rate with not many overs left and the spinners are on, how do you attack and up the run rate if you need to play yourself in? Would you introduce something different for different formats, (test,ODI,T20)

I would say that the batsman has to just keep nudging the ball into the gap and take those quick runs....

 

[blockerdave]

The only problem I can see with that idea if you are going to use vunerabilities is, say your player is weak vs spin early in his innings, and you're behind the run rate with not many overs left and the spinners are on, how do you attack and up the run rate if you need to play yourself in? Would you introduce something different for different formats, (test,ODI,T20)

i think that's part of cricket though, isn't it? that your batsmen (or bowlers) may not have the skills for the situation.

Also it's relative: the vulnerability of Ponting to LBW early in his innings isn't gonna be the same as McGrath's vulnerability to being bowled.