bavarian blue
Well-Known Member
- Joined
- 14 Aug 2010
- Messages
- 2,603
Just caught brief highlights of the game, what an atmosphere!!
I remember when you had to bowl 90 before 6 oclock in a test match.Remember when you had to bowl 20 overs in 75 minutes.?
It’s been deconstructed.It's a mess imo. As for that scorecard on screen......
It's a mess imo. As for that scorecard on screen......
sounds like bollox to meIt doesn't show on the screen in full for me.
It seems a bit pointless unless I'm missing something - 100 balls in 10 ball sets, allowing the bowler to change after 5. It just doesn't seem different enough to be significant.
The only way to stop poor over rates is 6 runs per over not bowled in the allotted time in an average test match day would be up past a 70 run penalty that would soon speed things up.
Thats a great idea they all know each others strengths and weakness.The constant team meetings and field changes play a big factor in everything taking so much longer. My solution would be to only allow the field to be changed at the start of the over and if the batsman changes.
Too sensible. They‘re more likely to introduce a ”power” over where the team batting get double scoring.The constant team meetings and field changes play a big factor in everything taking so much longer. My solution would be to only allow the field to be changed at the start of the over and if the batsman changes.