kiwi,
it'll be helpful if you can take any one modification and post the how-to procedure..that way we'll understand it better.
<span style='color:#000000
ost_uid0'>Thanks for all the interest shown, the support has been excellent. Well, to be honest the changes I have spoken of is only in its infancy state. I have been playing around with settings with some results, though all have not been encouraging. Sam in the previous posts has mentioned that the parameters defining is quite a problem which I totally agree although the parameters as mentioned by him are a problem here. The values are a bit of problem, looks like direct porting of values for the parameters are not really going to be effective. For instance the vertical values might have been defined in BLC as 99999 but with C2K2 it might be 9999999. Preserving BLC value will have drastic effects, I think the only way to get around this is to test the game with different values. I do not mind writing up what I know but for now I have not mastered the art of tweaking of Config files yet, If by chance I will someday I will be more than happy to share it with others. There are few changes that can made to cricket2002.exe to make the game very much a challenge for any player. Have a look at the following :
1. Open cricket2002.exe with a hex editor and search for value "TargetSizeMax" and "TargetSizeMin" as text string. Update the string "TargetSizeMax" and "TargetSizeMin" with null hex values (a zero) and playing the game will make the cursor disappear almost till the bowler is about to bowl. This will not let the player know where the CPU is going to pitch the ball beforehand. This should only be tried when batting as you will not be able to see the ball marker beforehand when bowling and will result in not bowling on the stumps at all.
2. The value "MaxTrajAdjust" reflects the ability of the batsman to read the trajectory(swing or swerve or spin) of the ball. This helps in playing all the shots out of the middle of the bat notwithstanding who the bowler is, what amount of swing or spin is imparted if the value is very high which is what the case is with C2K2. If you are always blasting the bowlers out of attack in test, I suggest update this text string also with hex values of zero. This way you will not be able to read the swing at all, the ability to score runs will depend on your expertise on playing or knowing cricket. The other string "MaxPosAdjust" will also need to be updated to zero or null values in the HEX value for corresponding string. I have tried these and have found batting something like real life, for instance a ball swinging in and close to the body is very hard to cut or slash and you will miss most of the times trying to cut it. Whereas a ball swinging away or given width outside offstump banged in short can be cut for four runs. The same happens when you incorporate the changes I have mentioned above. This will enhance batting experience and will sure satisfy hard core Gamers. This will particularly help in Test matches where you will need patience to stick to the wicket and only try to score off the bad balls.
Please also note that I have tried the above settings only for batting and not while bowling to CPU. The same effects will show on CPU when you make these changes, it will be beaten in the air more often than not. I am not asking for bouquets for this post of mine but I only ask please do not hurl brickbats and abuses after having made changes following my instruction and not getting it to work. If you are unsure of doing it or in doubt please do not attempt it and consider this post as one of those everyday stupid ones.
Apologies to those who wanted me to put my version of cricket2002.exe on the web given I hate to upload files on the net (lack of patience is one reason), if anyone is happy to host it I am more than happy to mail it.</span>