Yeah, certainly trying to get it to be far more informative and analytical about things.
Part of it with scripting is being able to work backwards - write the line and then figure out how to get the game to call it at the right time. Problem is trying to preempt as many match situations as possible to be able to genuinely sound informative, rather than "x team will want to score more runs, the other team would want a wicket" kind of stuff.
and this is the key, and it ties in with what i said previously about contextual to the human player.
so a four is scored. am i batting or bowling. if batting - is it the first four in a while, have i eased the pressure? is it my 3rd four of the over? was it a well timed shot or an edge through a vacant slip area.
i want to hear things like:
he's eased the pressure that was building, that's the first boundary for (x) overs(in tests)/balls(in limited overs).
he's really on top of the bowler - that's his third four of this over.
he's got lucky with that edge through the vacant 2nd slip, but he's forced the captain to go defensive with his brilliant batting throughout the innings
he's continued his great timing with that shot
he's been struggling to time shots in this innings, but that shot shows he's beginning to find his form
if bowling:
he's let the batsman ease the pressure that was building after the tight bowling / dot balls / maidens
he keeps bowling those four balls and can't build the pressure
he's going to be taken out of the attack if he can't tighten up
how unlucky, he's found the edge but it's gone into space and raced for four
everything should be contextual not just to the format and match situation, but what the player is doing, and how they've been performing over the innings / span of several overs etc.