I do not know how people have'nt noticed this. Test match engine is more broken than t20 engine. I recently did an Indian and Australian international save and here are the things that are pretty unrealistic are:
1.Opposing teams score over 350 in a day way more often than in real life. I have even seen 400 scored more than thrice.
And funnily enough we find tougher to score than AI 2.Lower order comebacks happen almost every game
Seriously every match you get a team 50/4 they end up making over 400. Last 4 wickets pile up 200 runs often
3. Pitch effects do not work
Playing a Ind vs Eng test. I prepared a spinners pitch. Ashwin, Jadeja and Kuldeep were smashed around and Eng made 507 with first wicket falling after 70 overs
4. Too many Draws
So many pitch matches happen where aggregate stats for the match are sonething like 1500/18
Remedies:
1. Make pitch effects stronger
2. Batsmen should generally score at 3 r.p.o and around 3.5 rpo on a really flat pitch
3. Ability of lower order and aggresive batsmen should be nerved.
4. Successful chases of 200 should be an exception rather than a rule
1.Opposing teams score over 350 in a day way more often than in real life. I have even seen 400 scored more than thrice.
And funnily enough we find tougher to score than AI 2.Lower order comebacks happen almost every game
Seriously every match you get a team 50/4 they end up making over 400. Last 4 wickets pile up 200 runs often
3. Pitch effects do not work
Playing a Ind vs Eng test. I prepared a spinners pitch. Ashwin, Jadeja and Kuldeep were smashed around and Eng made 507 with first wicket falling after 70 overs
4. Too many Draws
So many pitch matches happen where aggregate stats for the match are sonething like 1500/18
Remedies:
1. Make pitch effects stronger
2. Batsmen should generally score at 3 r.p.o and around 3.5 rpo on a really flat pitch
3. Ability of lower order and aggresive batsmen should be nerved.
4. Successful chases of 200 should be an exception rather than a rule
Comment