Ok so...
I’ll try explain this as best as possible.
Before hand everyone hated the last ball smash.
Then it was the feeling the AI were scripted to reach a run rate of about 3.5.
Now as I’m sure you will agree with what you see the AI’s run rate fluctuates, as you see more in the rest of the session.
The last ball smash etc was due to the AI getting bogged down and needing some kind of release.
The defending was slightly decreased to increase 1’s and 2’s.
You can still get the AI to defend.
Those mentalities were mostly precise with Taylor being balanced.
Also my bowling input wasn’t always spot on.
In a bit shell, to get an organic feel or non scripted batting with no obvious pattern to boundaries the AI defending was ever so slightly decreased was the change that was needed.
Which in my opinion is a worthwhile sacrifice. You can still however get them to leave and block..
Hope this makes some sense!
Basically you keep going perfect perfect with bowling and the AI have no scripted target, they simply won’t go anywhere!!
To add to this, and be more clearer there can be 2 scenarios.Dose the AI take match situation as well. As in if AI needs like 100 win in the last session with say 7 wickets remaining, will AI take risks?
This is way too much for a video game to handle with present technology but for the sake of the argument, i would prefer AI to go for it with whatever the pitch conditions UNLESS AI is already 3 down for 20 chasing 120 to win. So say AI is 100 for 3 and its a bad wicket, lets go for it. If they lose 2 wickets within 30 balls or final hour and have last 4 wickets standing , they you block everything. Like i said wayyy to much for a video game. Cricket is a completed game!To add to this, and be more clearer there can be 2 scenarios.
1. 100 in a session with 7 wickets on Day 5 pitch which is still good for batting (less deviation and spin)
2. 100 in a session with 7 wickets on Day 5 pitch which is good for bowling (more uneven bounce and spin)
@WealeyH and @Dutch What is your thought on this ?
That Williamson dismissal .
@WealeyH
Thought I noticed a suspicious cut at 5:12 and the score goes up by 6. Guess I just have my tinfoil hat on too tight.
Great ball to get rid of Kane though.
[DOUBLEPOST=1522413361][/DOUBLEPOST]
In all fairness was bandicam stopping at 10 mins. Think if I recall correctly I got hit over my head
Rippers from Moeen on day one. ICC rates this pitch POOR!