AI patch is now ready - Need testers

[crick4life]

Again if you reckon your batting is too good then all it will take is reduce your bat size to far lower than it is right now. Using the config editor when your turn to bat comes change the BatWindowIdealSize to 0.5. Change it back to 1.5 when you guys are bowling again. This will ensure you guys cannot score runs as quickly as you can right now. One other thing I did was to introduce falling of wickets quite often to ensure you cant score 350-400 every game. If you guys are claiming you are raking up 350s+ then the only way to make it harder for yourself is to change the bat size. Also drop the TargetSizeMin from 0.29000 to 0.05000, that will pretty much ensure you wont get even 5 wides in a game hopefully. Also with the change in targetsizemin you wont get too many balls you can cream for fours. Give it a go guys with altering the settings as any more changes to what it is currently will simply make CPU a lot weaker and I doubt if you can get a competetive game.

 

[groobz]

Ravi is there any setting which edits the cpu autosim totals?

 

[msamina]

Ok, Ravi. I will give it a shot by changing the BatWindowIdealSize to 0.5 when I bat. Anyway, mostly I do not end up scoring more than 320 like Radaga.

Even though, unlike Radaga I mostly score in the high 250's, I don't want to end my innings after just 30 overs. I would like to bat out the 50 overs even if the going is tough. If, this is the only change that is required, I think the patch is ready to be released.

Great work, Ravi. The matches are certainly very competitive due to all the upgrades that you have provided. Thank you.

 

[msamina]

Radaga,

If you play with the latest patch that Ravi sent to me for testing, the CPU might even chase your 320 + score successfully!! Can you believe it?

 

[potter]

Is there any chance of someone posting a legend of what exactly what each section of the config editor does so i have some idea of what i might want to change???? pleeeze.

 

[Vijay2004]

Can we have the final patch 9

Dear Ravi,

We are looking forward to your final patch 9. Please upload it here

The game is great with all your updates

Thanks

 

[tutsipoppy2]

yea ravi i need help with getting edges in my patch. my patch is complete in every other sence but i'm unable to get edges with that patch.

plz tell me as to what to edit and to what value to get edges so that i can an idea. later i can increase and decrease the values.

 

[bumba]

yes ravi, please upload you ver 9.0 patch (final version) asap as we are eagerly waiting for the same as we are for the pakistan vs india first ODI at karachi.

babai

 

[T20]

Originally posted by bumba
yes ravi, please upload you ver 9.0 patch (final version) asap as we are eagerly waiting for the same as we are for the pakistan vs india first ODI at karachi.

babai

Come on India!! and Ravi

 

[robertporter]

is ther emuch difference between the beta and the one that is yet to be dowloaded.

 

[groobz]

Is there anyway to lower the strength of advance 6 smash?. i score at about 15 per over if i use that.

 

[msamina]

Ravi,

I have batted 20 overs against Australia. In order to accurately judge the effect of changing the value that you specified, the first 10 overs I played with the value at 1.5 and the next 10 overs I played with the value set at 0.5.

After 10 overs, my score was 97/1 (similar to the previous match where I had scored 102/2 after 10). After the next 10 overs(at the end of 20 overs) with the value at 0.5, I scored 154/3. In the previous match though I had scored about 50 runs more. So, I think this is perfectly reasonable.

Bowl with the value of BatWindowIdealSize set at 1.5 and bat with the value set to 0.5. If batsmen like Radaga or Squiz still find it a bit easy, then they can reduce this value even further.

I think I can positively give this patch a go ahead.

 

[crick4life]

Thats sound quite good Murali, thanks for going through all the stuff I threw at you. More than me you will need to be thanked if the newer patch works out well for others.


Groobz, not sure if tweaking the autosim is possible but surely will see if I can do anything about it. As regards to the advance shot, I assure you I am not having the same problem as you although I can suggest a tweak or two I know which will not be a part of this patch. You will need to first download the patch and then tweak the values to stop this happenning.

Babai/Vijay2004, thanks for your interest in the patch. I will definately upload it here in a while after making sure I have sorted the right version.

robertporter, there are quite a few changes in the one Murali tested. More or less it was to tweak the CPU batting to bat smarter, outfield speed for different pitches changed to suite the pitch type, less but reasonable edges and there were lot more which I cant remember right away.

Tutsipoppy2, its not easy to suggest the edge value unless I can have a look at other attributes in your file. The edges also depend on swing/seam, weather, bat size, pos adjust, traj adjust and more. I will see what I can do though it may not be perfect but just that you will need to wait for a day or two for me to have a look at your files.

 

[msamina]

Ravi,

Thanks. I have some comments about batting and bowling using your patch:

I found that one way to make bowling MORE challenging using your patch is to set the game difficulty level to 'medium' before bowling and revert to 'hard' during batting. With this approach, a user need not keep on changing the value in the .GOB file before batting / bowling. They can constantly set the value to be 0.5 in ODI Hard or whatever value they feel comfortable with and then leave it at that. There is no need to modify anything for 'medium' difficulty level.

I found that in 'Hard' mode if the CPU scores at the rate of 6 per over with 'Medium' mode the CPU scores around 8 or 9 an over. You are still able to restrict the score to slightly less or greater than 300 with some intelligent bowling and innovative field settings, but it keeps you on your toes. Today, I played a match against New Zealand, just an independent trial and batting first NZ scored 307 all out in 48.2 overs and when I batted in hard mode, I ended up making only 242 all out after 45.5 overs.

[EDIT] Generally, if I am bowling in hard mode there is no necessity for me to spread out my field till after the 45th over. I only keep 2 fielders outside the circle till that point. When I was trying out bowling in 'Medium' difficulty I was forced to spread out my field after 15 overs, since the CPU was scoring so fast. You can test it out yourself. [EDIT]

Now, I find it so difficult to win matches - thanks to you

 

[Radaga]

Originally posted by crick4life
Again if you reckon your batting is too good then all it will take is reduce your bat size to far lower than it is right now. Using the config editor when your turn to bat comes change the BatWindowIdealSize to 0.5. Change it back to 1.5 when you guys are bowling again. This will ensure you guys cannot score runs as quickly as you can right now. One other thing I did was to introduce falling of wickets quite often to ensure you cant score 350-400 every game. If you guys are claiming you are raking up 350s+ then the only way to make it harder for yourself is to change the bat size. Also drop the TargetSizeMin from 0.29000 to 0.05000, that will pretty much ensure you wont get even 5 wides in a game hopefully. Also with the change in targetsizemin you wont get too many balls you can cream for fours. Give it a go guys with altering the settings as any more changes to what it is currently will simply make CPU a lot weaker and I doubt if you can get a competetive game.

Thanks for your help there Ravi!

i havent been able to play all week because i have a had a lot of school work and cricket training.

Will test out with changing the BatWindowIdealSize on Saturday afternoon.

Cheers :cool: