Sucess w/ new config files?

Has anybody had any luck with those new config files from ravi?

I've done a bit of messing around with the 1day config files still with no joy. Still getting wacked all over the park!

I have messed about for ages with the *.cfg files and I think the following

1- bowling attributes for cpu and human are stored in village, county and internat.cfg files
2- batting attributes for cpu are stored in compbat.cfg file.

These batting attributes combined with the 1day*.cfg files determines how the cpu bats during a 1 day game

Try these settings in your compbat.cfg file :
;
; Cricket98 Config
;

; Batting Config


; CPU Batting Settings

CpuDiffAffectPos 22222
CpuMaxPosAdjust 44444

; Virtual Bat Settings

DiffAffectVBatSize 0
VBatSize 99999

; Sroke Difficuly

DiffBias 0
ScoreBias 5680
StokeDiffBias 14856
FacedBias 30148
StyleBias 20096
OrderBias 60732
RandomBias 77777
EdgeDifficulty 3060
EdgeStroke 436
EdgeAverage 5680
EdgeOrder 0
EdgeBias 0

; Stroke Timing

DiffAffectTime 0
TimeStart 38016
TimeEnd 0
DiffAffectIdeal 10924
IdealWindow 30592

; Batsman Position Adjust

DiffAffectPos 22222
MaxPosAdjust 44444

; Ball Trajectory Adjust

DiffAffectTraj 0
MaxTrajAdjust 3072

;
; Cricket98 CPU Stroke Selection Config
;
CpuStumpRelPos 34516
CpuBatsmanRelPos 44564
CpuPitched 61168
CpuContactY 61168
CpuContactX 23156
CpuRandom 77777
CpuHistory 36264
CpuBatsmanStyle 30584
CpuDifficulty 53304
CpuBatsmanStyle2 23156
CpuFaced 50244
CpuBattingDefensive 10484
CpuBattingTypeMatch 15728
CpuRequest 13924
CpuReward 10500

I find the CPUReward value determines how aggressive the cpu bats at the end of the innings.
If you try the above settings, the combine them with the following settings for the 1day50.cfg file :


; Batting 1 Day Tactic Config

RunRate 0 3
RunRate 1 3
RunRate 2 3
RunRate 3 4
RunRate 4 6
RunRate 5 9
RunRate 6 9

StrokeProb 0 0 0
Def 48060
Mod 16604
Agg 8740
Six 0
StrokeProb 0 0 1
Def 46748
Mod 16604
Agg 8740
Six 0
StrokeProb 0 0 2
Def 40196
Mod 16604
Agg 8740
Six 0
StrokeProb 0 1 0
Def 41508
Mod 38448
Agg 8740
Six 8740
StrokeProb 0 1 1
Def 8740
Mod 46312
Agg 16604
Six 0
StrokeProb 0 1 2
Def 8740
Mod 46312
Agg 16604
Six 872
StrokeProb 0 2 0
Def 8740
Mod 51556
Agg 34516
Six 0
StrokeProb 0 2 1
Def 16604
Mod 42816
Agg 19660
Six 872
StrokeProb 0 2 2
Def 16604
Mod 46312
Agg 34516
Six 10484
StrokeProb 0 3 0
Def 8740
Mod 48060
Agg 16604
Six 872
StrokeProb 0 3 1
Def 16604
Mod 45440
Agg 19660
Six 10484
StrokeProb 0 3 2
Def 16604
Mod 45876
Agg 19660
Six 8740
StrokeProb 0 4 0
Def 16604
Mod 43252
Agg 34516
Six 8740
StrokeProb 0 4 1
Def 16604
Mod 49372
Agg 16604
Six 8740
StrokeProb 0 4 2
Def 8740
Mod 43252
Agg 19660
Six 8740
StrokeProb 0 5 0
Def 16604
Mod 46312
Agg 34516
Six 8740
StrokeProb 0 5 1
Def 16604
Mod 46312
Agg 19660
Six 16604
StrokeProb 0 5 2
Def 16604
Mod 46312
Agg 19660
Six 8740
StrokeProb 0 6 0
Def 8740
Mod 38448
Agg 19660
Six 8740
StrokeProb 0 6 1
Def 8740
Mod 38448
Agg 19660
Six 16604
StrokeProb 0 6 2
Def 8740
Mod 38448
Agg 19660
Six 8740
StrokeProb 1 0 0
Def 872
Mod 16604
Agg 8740
Six 8740
StrokeProb 1 0 1
Def 872
Mod 16604
Agg 8740
Six 8740
StrokeProb 1 0 2
Def 8740
Mod 16604
Agg 8740
Six 8740
StrokeProb 1 1 0
Def 872
Mod 31896
Agg 8740
Six 872
StrokeProb 1 1 1
Def 872
Mod 31896
Agg 8740
Six 872
StrokeProb 1 1 2
Def 15292
Mod 33204
Agg 8740
Six 1748
StrokeProb 1 2 0
Def 16604
Mod 51556
Agg 19660
Six 1748
StrokeProb 1 2 1
Def 8740
Mod 42816
Agg 16604
Six 1748
StrokeProb 1 2 2
Def 16604
Mod 46312
Agg 13980
Six 872
StrokeProb 1 3 0
Def 13980
Mod 66666
Agg 19660
Six 8740
StrokeProb 1 3 1
Def 16604
Mod 66666
Agg 19660
Six 0
StrokeProb 1 3 2
Def 13980
Mod 66666
Agg 34516
Six 8740
StrokeProb 1 4 0
Def 16604
Mod 66666
Agg 34516
Six 8740
StrokeProb 1 4 1
Def 13980
Mod 66666
Agg 34516
Six 1748
StrokeProb 1 4 2
Def 16604
Mod 66666
Agg 34516
Six 8740
StrokeProb 1 5 0
Def 0
Mod 66666
Agg 34516
Six 8740
StrokeProb 1 5 1
Def 0
Mod 66666
Agg 34516
Six 0
StrokeProb 1 5 2
Def 0
Mod 55555
Agg 33333
Six 0
StrokeProb 1 6 0
Def 0
Mod 55555
Agg 33333
Six 0
StrokeProb 1 6 1
Def 0
Mod 55555
Agg 33333
Six 0
StrokeProb 1 6 2
Def 0
Mod 55555
Agg 33333
Six 0
End

All I know is these settings make for great 50 over 1 day matches. Good luck !!!

Finally, I got some files that work. Much thanks, this is quite good. Although I thought the PC was still a bit too aggressive in the later overs. I've bowled 2 games so far and although I haven't managed to get pass 40 overs there's definetly been an improvment!

My experience is, any attempt to speed up the bowling or
add more swing and spin, make the game too radical.

Batting gets too hard and a lot of unatural looking things
seem to happen. Like a lot of leg bys going for four, and strange
looking strokes by the AI bats men.

Zimrahil's cfs don't effect this, so I'll give them a try.

Gunner04
If you find the computer still bats too aggressively at end of innings, then change CPUReward value to 9999.
Then try to bowl good line and length just outside off stump.
Also I never use spinners in the last 7 overs.

Also, I use my settings on test level - you may find cpu is more likely to bat the 50 overs ?

Hope this helps

Well, I've tried adjusting the CPU Reward Value in the compbat.cfg file however they batsmen play no defensive shots what so ever. They play like men possessed somehow I don't think they would have managed the 50 overs and If they did it would have been with like 400 on the board.

The value you gave me is 10500, but the original/default value is somethign like 51010 so what should I expect from 99999?

Also in the 1day50.cfg file, how do you know which parts are for which time in the innings?

Do the batsmen not even play defensive when you bowl good line and length ??

With the settings I have posted, the batsmen play defensive frequently for all types of bowlers. And if CPUReward=9999, then bowling slower balls on good length outside off stump always produces defensive shots at end of innings.
I would have thought setting value to 99999 will result in even more aggression

Unfortunately, I do not know which parts of 1day50.cfg file relates to which time of innings - its a case of guess work I am afraid.

Best thing in your case is to increase the defensive values, and decrease the aggressive values and in particular the sixes values. Just keep making backups of the 1day50.cfg file and experiment.

In reply to Damp Pitch,
I agree that u can overdo the spin etc.
but my experience with it is make big changes to the pace/spin/seam play a match and just keep on tweaking it until it's realistic.
Like now I have changed the Seam in Test matches so I've created the famous 'Corridor of uncertainty' , before when a ball was about 1-foot outside off-stump or so u could leave it as u knew it was going to stay straight,now u have to play at those cause they might cut back in or they could seam back out.
Also increased spin on wickets makes spinners very difficult to play on spinning wickets.

zimrahil

I've been messign around with the config file, but though I did get them to be a little........key word being little......less aggressive.

They tried to hit over the top too much during the middle overs and although during the later overs they weren't too aggressive they end up running out of wickets.

Now you must have played with theses settings much more than me, have you ever managed to bowl out the 50 overs?

I've bowled about 6 games so far 4 or normal pitches, 1 hard 1 dusty.

So far I've managed to reach 42 overs, but that's it and nobody's managed 200 runs against me.

Now this either means I'm a very good bowler or.......theres still something glitchy somewhere. And when I put the cpureward to 99999 they are even more attacking than at the death with no apparent comprehension of the word defence.

So the original settings are good but when you said about adjusting the cpu reward is where things get screwed up.

The previous settings are very good, esp. the fact that good balls are rewarded with solid defence and rubbish sent to the fence.

Also what you told me about adjusting the reward value, I can't see how adjusting it to 99999
would make them more likely to last the full 50. Of course, you will knowwhat is supposed to happen. So I'm curious as to what happens when you play with them. So if you say that you've managed to bowl out 50 overs then I'm gonna have to take your word for it and then assume that I'm too good a bowler and try it again. But definetly they're too aggressive in the middle overs, definetly.

Gunner04

I have as you rightly deduce used these settings a number of times and I have bowled my 50 overs on a number of occasions (but not all).

I am curious when you say the cpu bats too aggressive during the middle overs -what types of bowlers are you using - is it pace men. I tend to use spinners and swing bowlers more during the middle which ties the batsmen down more.

If you like if you send me your email address I could post you the following

compbat.cfg
internat.cfg
1day50.cfg

I use these settings on the test level. It would be interesting to see if you used these settings also on test level what sort of results you get.

Also I didn't say setting the reward value to 99999 would make them more likely to bat the 50 overs, the opposite is more like to be true.

Anyway if you want the files so we can compare results then let me know

Zimrahil

Yes, e-mail me you're files. My address is [email protected]

What changes have you made to the internat.cfg file?

As I was saying, they play too aggressively in the middle overs. Esp. to the spinners, they keep trying slog sweep them at least once every 2 or 3 overs sometimes twice and end up getting out. So it ends up that at around the 35th over they're usually 6 or 7 wickets down.

Anyway e-mail me the files, I'll be very interested to see what happens with them!

Zimrahil,
Been reading the posts between yourself and gunner04.
Can you send the files to me too,so Ican give them a try?
[email protected]
Cheers

Ben,
what files did you alter to create the 'corridor of uncertainty'? Does it work in county and test mode? I'd be grateful if you could post your new settings.
Cheers,
Mike