I'm finding a worrying trend that you can make batsmen score more runs if they just slog. There doesn't seem to be much punishment for going big with the AI. Going to have to force myself to tone AI slogging down before I sim anything proper.
yes, runrateball makes a drastic change. Probably was better to do what spoobir suggested, to set the variable runrateover to a very high value, and let the AI choose what to do.
Tomorrow i will update it. About the batsmen scoring easily, they usually do if they have high skill and confidence. I tried with some average team and i was losing wickets.
yes, runrateball makes a drastic change. Probably was better to do what spoobir suggested, to set the variable runrateover to a very high value, and let the AI choose what to do.
Tomorrow i will update it. About the batsmen scoring easily, they usually do if they have high skill and confidence. I tried with some average team and i was losing wickets.
I meant with the shots. I had Bairstow play no conservative shots, only front foot attacking, and he belted 112 not out. Root and Vince didn't get out doing that either. That's a fault with the game not your mod, where the AI going for big shots doesn't result in field changes in test matches, and there is not enough chance to get the AI bowled when they hit out.
I'm starting a proper Ashes playthrough where I don't use such extreme sliders, but a more subtle change.
I meant with the shots. I had Bairstow play no conservative shots, only front foot attacking, and he belted 112 not out. Root and Vince didn't get out doing that either. That's a fault with the game not your mod, where the AI going for big shots doesn't result in field changes in test matches, and there is not enough chance to get the AI bowled when they hit out.
I'm starting a proper Ashes playthrough where I don't use such extreme sliders, but a more subtle change.
i noticed that when Kane Williamson (one of the strongest player in the game) has full confidence, he becomes almost impossible for me to dismiss (bowling on pro).
Tried also a game AI vs AI between Scotland and Zimbabwe, where i was controlling the batsmen (Scotland), and it was difficult to score. I was 30-2 after 10 over i think,
with lots of edges, most fun i have had in a long time ^^
Certainly looks that players values are important.
updated the Lua Consoles to fix a bug with long lines of code.
Now a cool thing, a Lua script that will allow to set a custom run rate for both the batsmen (they will use their own run rate). It
doesnt require any external mod, you need only to put the code in the console window. I post it just in case someone is interested,
so he can create his own code or even an AI (could be possible soon).
First run this part in the spoiler to initialize it (you dont need to understand this part).
Then, everytime you want update the run rate, first use this script:
InitStrikers()
now the striker at the crease will be considered Striker1, the other Striker2.
Then create/update these scripts. In this case, striker1 will use a custom run rate
for the over, and the default run rate for the ball. The striker2 will use default run
rate for both (so the only effective change is for striker1 run rate per over).
Hope it's not too complicated.
native.RunRateCalculator.getDesiredRunsForThisOver=CustomRunRateOverFunc
native.RunRateCalculator.getDesiredRunRateForThisBall=OriginalRunRateBallFunc
end
native.RunRateCalculator.getDesiredRunsForThisOver=OriginalRunRateOverFunc
native.RunRateCalculator.getDesiredRunRateForThisBall=OriginalRunRateBallFunc
end
Currently only the AI shot selection and the Lua console work. However you can use it
with the main Fearsome Tweak mod.
Now you can activate/set a custom run rate (for over and ball) for both batsman.
You should use mostly "run rate over" because it is used to calculate the "run rate ball".
Use "run rate ball" only if you want to affect the batsman mentality for the current delivery.
USAGE:
select a batsman (1 or 2), activate the button that you want to use (run rate over and run rate ball or both), insert the run rate values in the 2 fields and press "set run rate".
I'm going to have a play with the run rate mod. Right now, try as i might, i cannot make the AI batsmen get 100. It is almost scripted that they nick off at about 70 odd, it's infuriating!
Have just tried the run rate mod and it still seems the value for the over gets stuck as the same for both batsmen.
I'm going to have a play with the run rate mod. Right now, try as i might, i cannot make the AI batsmen get 100. It is almost scripted that they nick off at about 70 odd, it's infuriating!
Have just tried the run rate mod and it still seems the value for the over gets stuck as the same for both batsmen.
i will make a video on how to use it, will edit this.
By the way this is an example:
-press "batsman 1"
-select "use custom run rate over"
-deselect "use custom run rate ball" (so it's not used).
-insert the value for "run rate over", for example 4. It means that the batsman will try to get that RR. No need to insert a value for "run rate ball" because is not used.
-press "set run rate"
then press "batsman 2" and do the same (with other settings for RR).
To test it, i suggest to select "use custom run rate ball" for one of the batsman, set "run rate ball" to 6 and press "set run rate".
Now one of the two batsman will try to slog, the other will not be aggressive.
i will make a video on how to use it, will edit this.
By the way this is an example:
-press "batsman 1"
-select "use custom run rate over"
-deselect "use custom run rate ball" (so it's not used).
-insert the value for "run rate over", for example 4. It means that the batsman will try to get that RR. No need to insert a value for "run rate ball" because is not used.
-press "set run rate" Edit
then press "batsman 2" and do the same (with other settings for RR).
To test it, i suggest to select "use custom run rate ball" for one of the batsman, set "run rate ball" to 6 and press "set run rate".
Now one of the two batsman will try to slog, the other will not be aggressive.
Yeah sorry I have followed it to a T and whenever is set a number batsman 1 in the number box carries over to batsman 2. Then click "set run rate" And then I set a different number into 2, click "set run rate", and that number carries across to batsman 1. I don't want to be a hassle so I will await the video
Yeah sorry I have followed it to a T and whenever is set a number batsman 1 in the number box carries over to batsman 2. Then click "set run rate" And then I set a different number into 2, click "set run rate", and that number carries across to batsman 1. I don't want to be a hassle so I will await the video
Well it clearly works then. Is it possible to have both batsmen with differing "run rate per over"?
Sorry if I am being excessively demanding. I also noticed that the stroke editor picks up the identities of the two batsmen immediately. Mine takes a few deliveries to.
In terms of being able to tell ai to go for it in limited over final overs this is great! Stupid we have to trick them and it is a mystery why ba cant just code this in but this tool is invaluable
Well it clearly works then. Is it possible to have both batsmen with differing "run rate per over"?
Sorry if I am being excessively demanding. I also noticed that the stroke editor picks up the identities of the two batsmen immediately. Mine takes a few deliveries to.
yes you can already do that (press batsman 1, select custom run rate over, press batsman 2, select custom run rate over). Remember to press
the "set value" button after you change the value.
If it looks that is not working, try to activate/deactivate the various option, in case they are stuck for some bugs (like when you reboot your computer).
@Langeveldt forgot to say that in the latest update (0.21) the batsmen are identified immediately. Also, the separate run rate
is only for this update (in case you were using the old).
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
