You can do that yourself.Can mods add ONE after ANY in the thread title?
I think, given that there is still the occasional slog shot in tests, whatever method is used for setting the AI approach is reliant upon them scoring at a particular rate and maintaining that and in the short formats it becomes a lot more noticeable. If a workable solution to that is not possible then some variety would be nice. I've said several times that team mentalities would be good, if only in some way providing variations in how teams go about getting their runs. Teams have no individual character if at least there was something that showed teams being aggressive or cautious at different stages it'd feel a lot more realistic.
Generally my tactic, if I'd kept it tight for four or five balls would be to bowl short, they tended not to be able to slog balls they can't hit.
I think, given that there is still the occasional slog shot in tests, whatever method is used for setting the AI approach is reliant upon them scoring at a particular rate and maintaining that and in the short formats it becomes a lot more noticeable. If a workable solution to that is not possible then some variety would be nice. I've said several times that team mentalities would be good, if only in some way providing variations in how teams go about getting their runs. Teams have no individual character if at least there was something that showed teams being aggressive or cautious at different stages it'd feel a lot more realistic.
Generally my tactic, if I'd kept it tight for four or five balls would be to bowl short, they tended not to be able to slog balls they can't hit.
I thought it was something like this, I wasn't sure. The fluidity issue is what seems to be missing, it's probably difficult. Something like Duckworth Lewis - the target score of the AI adjusts in line with wickets in hand (or however DL works).In my mind the problem isn't necessarily that they have an aggressive approach and are trying to reach a certain determined run-rate, it's that there is never any penalties for them when hitting out.
An AI thought process of "I need a boundary therefore I will try to hit one" isn't so bad but at the moment it just goes "I need a boundary therefore I will hit one". There needs to be a balance based on quality of batsman/delivery/pitch etc and it's just not there right now.
On the target run-rate @francobaldo1 had how it works pretty figured out in his hack for DBC17. We were able to adjust the target run-rate for each batsman before every ball which meant you could actually make a batsman build a proper innings. The issue is there doesn't seem to be a methodology within the game to make this target fluid and suit the match situation, it is always 6.5-7rpo during powerplay then 4-4.5 outside those overs. I would like to see it adjust with batsman confidence at least.
EDIT: Just checked out out Franco's hack again and there is actually two values. "Run-Rate for this over" and "Run-Rate for this ball". Seems like most likely the 2nd one is the one causing the freebie slogs. Maybe he can explain how it works when not affected by the tweak?
I thought it was something like this, I wasn't sure. The fluidity issue is what seems to be missing, it's probably difficult. Something like Duckworth Lewis - the target score of the AI adjusts in line with wickets in hand (or however DL works).
It'd just be nice to see variations based on conditions, venue (setting par scores in stadium creator?), teams (setting mentalities or having them based on a captain's?) and the players (a secondary mentality for one day/t20?) in that team.
Some say the opposite... ![DOUBLEPOST=1528049482][/DOUBLEPOST]Specially when it comes to AI slogging , no matter what you are gonna bowl the AI will smash you out of the park when the scripts trigger.
Yes but pack that side of the field and swing shortish to off (if bowling to a righty)Short balls and Yorkers is what I use to keep it tight.