One thing which would really assist analysis would be to print scorecards in sequence order when you sim a series or multiple matches after each other.

So start with saving to card1.htm, if it exists try card2.htm, etc.

From today's testing, Wankhede works reasonably well in assisting the spinners (they consistently come out on top), but the scores are amazingly high there. Low control bowlers struggle ridiculously at Edgbaston (40 wides) - though especially if the batsmen can't bat, for some reason. Edgbaston may also be difficult to bat on but still gives decent totals (though that may be because my testing teams have proper batsmen down to 11)

Interestingly, it appears that if you put worse batsmen at the top of the order, they struggle a lot more than they would if you stick them at six.

A follower of the schools of Machiavelli, Bentham, Locke, Hobbes, Sutcliffe, Bradman, Lindwall, Miller, Hassett and Benaud
Member of ESAS, JMAS, DMAS, FRAS and RTDAS

when you're winning, you have friendsscores and dozens, real friendswhen you're winning, never lonelywhen you keep winning

I think the wides problem is related to length. When you set it to bowl on off stump, it seems to mean pitching it on off, rather than it reaching the stumps on off. Thus if you're bowling short, it ends up angling down the leg side. Couldn't this be changed? Seems a little irrational to be like this, if I'm right in thinking it is.

Also, I think wides are probably because the movement on pitches is probably a bit too much atm, though I don't know, obviously. Neil, didn't you have a program which showed visually what happened with each ball on certain pitch settings? Couldn't you experiment with that to find out the realistic parameters?

Another thing is that it's a bit hard to experiment as it stands, as the commentary seems to contradict itself. It'll say things like "... full of a length, on the stumps, left alone, wicketkeeper takes it easily" or something - if it's full and on the stumps... wouldn't he be bowled? Have lowered bounce to make doubly sure it's not going over the top, same commentary occurs, there are other examples as well where it can contradict itself.

Pretty playable still just from my little experiment just now, good work.

I think the wides problem is related to length. When you set it to bowl on off stump, it seems to mean pitching it on off, rather than it reaching the stumps on off. Thus if you're bowling short, it ends up angling down the leg side. Couldn't this be changed? Seems a little irrational to be like this, if I'm right in thinking it is.

Also, I think wides are probably because the movement on pitches is probably a bit too much atm, though I don't know, obviously. Neil, didn't you have a program which showed visually what happened with each ball on certain pitch settings? Couldn't you experiment with that to find out the realistic parameters?

Another thing is that it's a bit hard to experiment as it stands, as the commentary seems to contradict itself. It'll say things like "... full of a length, on the stumps, left alone, wicketkeeper takes it easily" or something - if it's full and on the stumps... wouldn't he be bowled? Have lowered bounce to make doubly sure it's not going over the top, same commentary occurs, there are other examples as well where it can contradict itself.

Pretty playable still just from my little experiment just now, good work.

The reason it runs like this is because of the way the match engine deploys swing and spin: the location the ball pitches is essential to the batsman's conception of line and length, leading to judgement, misjudgement, play-and-misses and nicks.

Having said that, keepers get less than half as many catches as outfielders. Needs changing: will also sort the 'wides' issue that appears most when there is a weak batsman on a bowler's track.

Lots of updates, as requested. A few extra grounds added - of which Lord's probably gives the best, balanced cricket as it's a fair track. Also have tweaked the bowling AI heavily regarding line, length and bowling changes. The stats file shows the latest round of testing - if you ignore the fact that Craig Cumming is topping the bowling averages after 8 overs in 75 games, then it's all awesome (also, Kamran Akmal has gone on one of his crazily good batting runs...)

Michael Clarke just bowled the last over of a T20 match against West Indies and took 1-1-0-1. Fairish enough, given that Ian Bradshaw faced 5 of the balls and Ramdin was out to the other. But then Australia needed 8 off the final over to win and Brad Hogg only managed 2 against Chris Gayle. Hmmm...

Sreesanth said, "Next ball he was beaten and I said, 'is this the King Charles Lara? Who is this impostor, moving around nervously? I should have kept my mouth shut for the next ball - mind you, it was a length ball - Lara just pulled it over the church beyond the boundary! He is a true legend."

More tweaking - very happy with how it's playing now: more feedback would be really appreciated, as would any data updates (looking for the right balance between bat and ball, swing and seam - the pitch really counts) or requests for changes, additions, or where we try to go next. I've simmed nearly 2,300 games in the last two days...

I've attached the latest version, and a card/bbb from a thrilling low-scorer between England and Sri Lanka at Exeter...

Just had a quick match at the Basin. Having the top order bat aggressively seemed to initiate away, throwing wicket of. Oram and Vincent on a lower aggression through the middle overs worked well. Don't think there's too much wrong with it - nothing that I noticed anyway. Also, bowling full and on the stumps (i.e. yorkers) worked very well in the death overs.