Well if your batsmen get out early (and mine usually do, just like in real life) and you stick in a so-called nightwatchman after say only 11 or 12 overs it looks a little strange. Luckily nobody's watching and nobody cares, least of all me!! I am bit of a perfectionist though and detail my scores in an excel spreadsheet sometimes (God I'm sadI need to get a girlfriend!:laugh)
I haven't got the patience for spreadsheets - feels too much like hard work.
I can confirm that this method does not work. Back to the drawing board.
hey im new here but this is what i tried and it is working pretty well.
im south africa playing england on normal, and i put swann in at number 5.
After the first wicket fell number 3 and 4 started slogging, as they usually do. But after they got out and swann came in every single batter after him played normally. So i ended day one with England on 359/9 off 90 overs. Which is pretty realistic, but this only seems to work if Swann is high up the order, maybe it has sometihng to do with him being classed as an allrounder or something?!?!
I tried reversing the SL batting order with some interesting results. First, I reduced all their placement and strenght skills to around 20-30. I left the openers, but put the tail-enders in positions 3,4,5,6. The first couple tailenders slogged and a couple batted normally. I eventually had the sixth wicket down for about 80 after 35 overs. When the sixth wicket fell, Sangakara, Jayawardene came in and played very realistic. They batted very well for about 20 overs and then for no apparent reason they started slogging. At one point they were even playing defensive shots to the spinners, but something seems to trigger them into slog mode.
They've either hard coded some AI behavior based on some fuzzy logic, or its based totally on confidence.
Another slight option im going to try is.... create say my own Clarke... Slip him in instead of the AI's Clarke and see if the created player bats a little differently. Could be clutching at straws to be honest!![]()