1. Let the player choose which stump to take guard on.
2. There's a cutscene going on, and you press a button (say F1) to bring up the scorecard. Then you press it again and it goes. Press another button (F2) and the Wagon Wheel comes up. You know what I mean.
Excellent idea, different buttons for different stats that you can press whenever you want, as well as the stats coming up in between overs. Good stuff, Skater!
Also, LM, put a bit of tension into the 3rd umpire replay. The way EA and Codies do it is rubbish, there is no wait at all before the light comes up if it's a green light, so you can usually tell if it's going to be in or out immediately which destroys any sense of tension. Of course, there should be the option to skip it (for those who do such a thing)!
acknowledgement of hat-trick
Yep, have a proper celebration, not just the commentator saying: That's a hat-trick for....Sidebottom. Have a variety of different celebrations whenever a wicket is taken, especially if they reflect the position of the match.
i want the test match day times to be as realistic as possible. I find it a joke in some games (not to mention any names ahem) where you can finish a test in 1 or 2 days because the scoring rate is too quick or for whatever other reason. One of the great things about test matches is taking the days into account, which has a major impact on the result. So yes, i want to spend enough time on this aspect in play testing to make sure time moves along realistically. Obviously though it wont be in actual real time.
If you look at football games, the matches last for around 10 - 15 minutes, so nowhere near as long as a real match, yet it still feels like there's been a decent match with lots of twists and turns along the way. It would be preferable to have time move along more quickly than the tests to only last one or two days, (three if you're lucky), although not too quickly, obviously. It's a tricky thing to get the balance right, but I'm sure you won't let us down. Anyway, if some people aren't happy with what you come up with, have an option to have less overs in each day of the Test, sixty overs instead of ninety, for example. That way, everyone is happy.
I think swing should use an arrow but maybe the arrow might not always indicate how much it is swinging.
Agreed, in real cricket, a bowler might want to swing the ball, but it doesn't always happen. EA and Codies method is retarded, it lets you choose
exactly how much swing you want on each delivery.
How are you going to implement the aiming marker for bowling? How about a wobbly cursor? The better the bowler, the less it wobbles, hence reflecting his ability to put the ball where he wants it, whereas a lesser bowler's more wobbly cursor would make him spray it around more. Being able to use the mouse to bowl and the gamepad to bat would be a nice option.
Edit: So how many people are working on the game altogether?