blue b4 the moon
Well-Known Member
It's a limited overs game, the batsman is reducing the distance he needs to run/gain an unfair advantage, I have no problem at all with what the bowler has done.
The rules need changing. If a bowler runs up to bowl a delivery and completes his action but keeps hold of the ball, it is deemed a non-delivery which suggests the ball never entered the field of play. Therefore it could be sometimes argued in a mankad that the batsman has been run out but play hasn't technically restarted. I agree that the batsman is trying to gain an advantage and perhaps a 1 or 2 run deduction penalty, or the umpire declaring the ball has actually been delivered with no runs scored, should be the punishment. They'll soon stop. Hasn't Buttler been caught doing this before for England? That said, I see batsmen doing it all the time and it does annoy me.It's a limited overs game, the batsman is reducing the distance he needs to run/gain an unfair advantage, I have no problem at all with what the bowler has done.
Just watching the T20 game between Surrey and Middlesex. Quick question for you lads who are pretty well up to speed on the rules (laws?) of the game. The non striker had to scramble back to make his ground, having inched a fair way down the pitch for a possible single. Now, if he was to hit the stumps (with either his bat or a part of his body) would he be given out (hit wicket), the same as a batsman facing would if he hit the stumps? I'm assuming that, yes he would. The fact the non striker isn't facing wouldn't matter, I'm guessing.