• Welcome to the Cricket Web forums, one of the biggest forums in the world dedicated to cricket.

    You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join the Cricket Web community today!

    If you have any problems with the registration process or your account login, please contact us.

*Official* IPL 2019

mr_mister

Cricket Web: All-Time Legend
The law was amended recently to say that you could only mankad someone if you haven't started your action. Ashwin saw that Buttler wasn't looking and took advantage of that within the rules.
Action or delivery stride?
 

Spark

Global Moderator
OK I just watched the footage and Buttler deserved to get run out that way. Ashwin hadn't even started his bowling action and Buttler wasn't watching and was out of his crease. It was extremely poor match awareness by Buttler. He wasn't paying attention to the one thing he's supposed to pay attention to as the non striker. The amount of time that Ashwin had to perform the run out was incredible. There should be nothing controversial about a batsman getting out due to their own stupidity.
Sure it should, if it happened in a patently ludicrous way given the intention of the laws. There is no "well the batsman was dumb" clause in the laws.
 

Borges

International Regular
The law was amended recently to say that you could only mankad someone if you haven't started your action.
Ah! That explains Ashwin's actions, and also why the umpire ruled Buttler out. Playing by the rules is perfectly fine by me.
A batsman can be run out even if there is no intent to take a run; a batsman can be Makaded even if there is no obvious intent to gain an unfair advantage.
 

Borges

International Regular
The MCC stance on this seems to be clear:
although there are some valid arguments for not allowing dismissals of this sort, mcc felt that it would be wrong to carve out an exception in these circumstances for a fundamental principle that a batsman can be run out if the wicket is put down when he/she is out of his/her ground. Furthermore, the law emphasises the importance of the non-striker remaining in his/her ground until the ball is released, which is felt to be important. With tv now potentially ruling that a batsman has made his/her ground by millimetres, it seems wrong toallow them a head-start of sometimes several feet in setting off. So, the policy in the law has not been changed but rather the outcome is being more strongly emphasised to avoid confusion.

It is worth stressing that giving a warning for such dismissals has often been seen as a convention but has never been part of the laws. The fielding sidehas the option not to appeal, or to withdraw the appeal if they do not want to dismiss the batsman in this way.
 

mr_mister

Cricket Web: All-Time Legend
Ah so Ashwin acted like a dick but acted within the rules. Just like Greg and Trevor Chappell.

Conventions matter in cricket. Dunno why but they do and always have
 

Spark

Global Moderator
Ah so Ashwin acted like a dick but acted within the rules. Just like Greg and Trevor Chappell.

Conventions matter in cricket. Dunno why but they do and always have
Probably because we would like to think of the sport as defined by how ordinary people play it on their local fields every weekend, rather than bequeathed to us from up on high.
 

mr_mister

Cricket Web: All-Time Legend
Harsha Bhogle's take from a press conference last night:


Now everyone around India will have their own ideas on that, and we always get tweets and messages about different things that happen, so I don't expect anybody to agree with me, I don't expect you'll get more than fifty percent agreement on anything. Let me just tell you what I think about it. I think it was a disgraceful performance from a captain who got his carrom ball wrong today and I think it should never be permitted to happen again. We keep reading, and hearing that the players are under a lot of pressure, and that they're tired and jaded, and perhaps their judgment and their skill is blunted, well perhaps they might advance that as an excuse for what happened out there today. Not with me they don't. I think it was a very poor performance. One of the worst things I have ever seen done on a cricket field.

Good night.
 

TheJediBrah

Request Your Custom Title Now!
A glimpse I got of Warney's embarrassing twitter rant (the latest) on the topic led me to think that Harsha was defending Ashwin for it at one stage. Did I just mis-read that
 

vandem

State Captain
And he's a liar. Can't even take responsibility for his actions. "Speaking at the post-match press conference, Ashwin said his Mankad was simply instinctive and stressed he did not pre-meditate the dismissal". But his left left has already landed in his bowling position when he stops, pivots, and makes the "run out". So he expects us to believe that he is running in to bowl, but is looking at the non-strikers feet, not the batsman he is bowling to? Ffs. He does know there were cameras?

https://www.news.com.au/sport/crick...e/news-story/11ade1c6af796aced102036d4cfb0c04
 

ankitj

Hall of Fame Member
I do think it makes for weird viewing when a batsman is mankaded. But it's purely because of convention. There is nothing huge being asked of the batsman to wait until the ball is bowled. Even if the bowler completes the action but doesn't deliver the ball and runs out non-striker instead, it's fair game if we didn't have the baggage of convention. Just watch the ball go in the air before you take your bat out of crease ffs. Someone mentioned that the batsman already has too many things to focus on -- no, the non-striker doesn't have that many things.

Besides, game is loaded in favour of batsmen; more power to bowlers who mankad out batsmen :ph34r:
 

ankitj

Hall of Fame Member
Harsha Bhogle's take from a press conference last night:


Now everyone around India will have their own ideas on that, and we always get tweets and messages about different things that happen, so I don't expect anybody to agree with me, I don't expect you'll get more than fifty percent agreement on anything. Let me just tell you what I think about it. I think it was a disgraceful performance from a captain who got his carrom ball wrong today and I think it should never be permitted to happen again. We keep reading, and hearing that the players are under a lot of pressure, and that they're tired and jaded, and perhaps their judgment and their skill is blunted, well perhaps they might advance that as an excuse for what happened out there today. Not with me they don't. I think it was a very poor performance. One of the worst things I have ever seen done on a cricket field.

Good night.
OK, that's taking it too far.
 

Borges

International Regular
There is nothing huge being asked of the batsman to wait until the ball is bowled ... Just watch the ball go in the air before you take your bat out of crease ffs.
Yes, yes, yes. More and even more batsmen need to be Mankaded, as a matter of routine.
Automatic drastic punishment of batsmen who violate the rules, who essentially cheat in running between the wickets, should become the norm.
 

ankitj

Hall of Fame Member
Yes, yes, yes. More and even more batsmen need to be Mankaded, as a matter of routine.
Automatic drastic punishment of batsmen who violate the rules, who essentially cheat in running between the wickets, should become the norm.
But if you disallow Mankad then you have to also allow non-striker to stand half way on the pitch when ball is being bowled. Slipper slope works both ways.
 

Borges

International Regular
But if you disallow Mankad then you have to also allow non-striker to stand half way on the pitch when ball is being bowled.
Mankading should never be disallowed; it should be encouraged. Make them run the full length of the pitch if they want to try and steal a quick run.
 

Arachnodouche

International Captain
No problem whatsoever with Mankading. Non-striker being presumptuous and bowler showing awareness, don't know why the latter's team shouldn't be rewarded with a wicket. Didn't see it so don't know if Ashwin stopped, but isn't stopping and stuttering part and parcel of his ****** bowling action anyway? Batsmen ought to be more clued in to that.
 
Last edited:

Jarquis

Cricket Web: All-Time Legend
You know what's against the 'spirit' of the game? It's non-strikers advancing a few inches every ball knowing the only 2 bad scenarios that can happen are:
1. Bowler giving him a harmless 'warning'
2. Bowler being portrayed as a villain after Mankading.

It's a win-win situation for batsmen.
Apart from the fact he’s out?

‘Normal’ mankads are fine. This wasn’t.
 

Top