11. CpuBallsFaced:
Same as BallsFacedLevel for Human Players, but this one for CPU.
This value determines CPU's confidence in batting(i.e.willingness to go after the bowling!). Lower this value means CPU may gain confidence quickly and viceversa for higher value.
If this value is 0.0 they may gain confidence so quickly after hitting few runs there by timing and placing are pretty easy, if CPU mistimed or edged a few confidence will fall gradually. Gradually increase this parameter to get it right!
12.13. CpuTacticsDefend, CpuBattingMatchType:
These are important defining parameters of how CPU estimate(approach!)the game.(Also sets the AutoPlay up!). Basically these values were set to 0.0 in-game by default. But we can tweak it a bit to get good results. Let us see!. Lesser these values, higher the aggressive approach(even after the wicket falls, still the new batsmen tends to play aggressively). Higher these values means more sensible appraoch(after the wicket falls CPU tend to play defensively to set!). Usually i set 0.5 and 5.0 respectively to get good results(even in AutoPlay) in Test Matches. But in ODIs this is no matter!(as the CPU tends to look at ODI20.cfg/ODI50.cfg pacing files or whatever ODI format you playing). Anyhow try to play around a bit to get good results. Suggested values are 0.2 and 1.0.
