Custom Bats Cricket Forum
General Cricket => World Cricket => Topic started by: Batbuddy99 on July 13, 2016, 12:29:19 PM
-
http://www.cricket.com.au/news/mankad-controversial-dismissal-endorsed-mcc-world-cricket-committee/2016-07-13?utm_source=facebook&utm_medium=social&utm_campaign=internationalcricket (http://www.cricket.com.au/news/mankad-controversial-dismissal-endorsed-mcc-world-cricket-committee/2016-07-13?utm_source=facebook&utm_medium=social&utm_campaign=internationalcricket)
Another rule that was discussed at the same time as the bat size regulations
Alterations have made it easier to Mankad non-striking batsmen
-
I hate this rule, just get on and bowl. if you back up too much and the batter hits it straight at the bowler they can run you out
it's really annoying when they go "HAHAHAHAHAHA" as they knock your bails off
-
I like this.
Even as a batsman, I think pinching yards should be punishable. The amount of times I've seen batsmen half way down the track when the ball is delivered.
Back up at your peril.
-
I like this.
Even as a batsman, I think pinching yards should be punishable. The amount of times I've seen batsmen half way down the track when the ball is delivered.
Back up at your peril.
What punishment do you think should be introduced?
-
One of the lads in my league got mankaded on Saturday, embarrassing to be honest, I hate the rule. Just hurry up and bowl.
-
I think the mankad should be part of the game, however I believe a warning should be delivered first.
I feel this should be the case because unlike other dismissals, you are not beating the batsman on your ability.
Whilst some batsman are trying to steal a yard, see Jos Buttler vs SL, I feel it is harsh on someone backing up in normal manner and at most can be accused of carelessness, see the U19 WC mankad.
After a warning, no batsman has a leg to stand on.
My personal worry with changing the rules is that we'll see it more often in club cricket. I don't think umpires I have played with would know either way if the batsman was out or not. Another reason why a warning may be suitable. A warning being as easy as informing the umpire/non striker that if he doesn't be careful you will mankad him, although appreciate a physical warning would make sure everyone was aware.
-
Make backing up just like a no ball is for the bowler.
The umpire calls the batsman for being over the line at the point of delivery. If its called any runs are cancelled but the batsman can still be out. Takes away any benefit from backing up too far then.
The problem will be with the umpire calling it I guess as they struggle enough with no-balls!
-
does anyone see a difference with this on Saturday league cricket and sunday friendlies?
I saw this done on a Sunday (friendly) this season without a warning. the umpire(a kid) did not know whether to give the batsman out or not
I asked the bowler what the *****£££££&&@@@@@@ he thought he was doing and he mumbled some garbage.
I spent post match apologising to the opposition who are a good bunch.
So I really don't like this mankad stuff.
For league cricket......hmmmmmm if a warning was issue prior yes probably but there would need to be a clear warning....and i'm not even sure then if I was Captain whether I would uphold any appeal from my bowlers
-
Make backing up just like a no ball is for the bowler.
The umpire calls the batsman for being over the line at the point of delivery. If its called any runs are cancelled but the batsman can still be out. Takes away any benefit from backing up too far then.
The problem will be with the umpire calling it I guess as they struggle enough with no-balls!
Picture of the only man able to umpire this:
(http://www.craveonline.com/images/stories/2011/2012/March/Comedy/5%20Celebs%20in%20Barfights/crazy_eyes.jpg)
-
This to me is a no brainer. When I am at the non-striker's end, I stand out of the crease but importantly with my bat grounded behind the line watching the bowler's delivery action. As sonn as the bowler releases the ball, I am off down the wicket and at nearly 51 years old, I easily can make it down the other end to any reasonable call. There is absolutely no need to start striding off down the wicket before the bowler has delivered the ball and if you've been warned once, you deserve to be given out.
-
We had an mankad incident a couple of weeks ago when we needed 3 to win of 2 balls.
The bowler did give the batsmen a warning, but the frustrating thing was that he wasnt leaving the crease before the bowler entered his delivery stride. Basically the bowler was running up and then not letting go of the ball - waiting for the batsmen to leave his crease and then took the stumps.
Got into a fairly heated debate with the league president (who is the bowlers Father!) but was told that it was up to the umpires so decided it wasnt worth debating. Ultimately it didnt affect the result as we had wickets in hand but still lost, but was frustrating.
-
sorry this is nonsense. Does the keeper ever warn the batsman about stumping's. All cricketers know which part of the pitch is theirs and which isn't. My only issue is that there is a different rule for ODI's and other cricket. In the league I have batters 2 yards out of their crease before i release the ball. That's cheating, I'll run them out, bugger warning the cheats. Its either a Law or not.
-
What punishment do you think should be introduced?
I think being given out, run out, is punishment enough. For me the only embarrassed party should be the batsmen. You wouldn't bat out of your crease to the spinner, so why set off down the track before the bowler has delivered the ball?
-
I hate this rule, just get on and bowl. if you back up too much and the batter hits it straight at the bowler they can run you out
it's really annoying when they go "HAHAHAHAHAHA" as they knock your bails off
Or
Don't leave your create until the ball is actually bowled?? Stop stealing yards.. Tbh, im becoming more a fan of the mankad as it's annoying when batsmen are stealing yards in games and think it's acceptable 'backing up'
-
Or
Don't leave your create until the ball is actually bowled?? Stop stealing yards.. Tbh, im becoming more a fan of the mankad as it's annoying when batsmen are stealing yards in games and think it's acceptable 'backing up'
Stealing a base in baseball is considered allowed but you can be run out, backing up too much is considered stealing and you can be run out... not the only sport to have something similar.
-
Stealing a base in baseball is considered allowed but you can be run out, backing up too much is considered stealing and you can be run out... not the only sport to have something similar.
So?
If you want to risk it do it, but a bowler should be able to just whip your bails off.
-
So?
If you want to risk it do it, but a bowler should be able to just whip your bails off.
exactly what im saying, just run faster between wickets.
-
sorry this is nonsense. Does the keeper ever warn the batsman about stumping's. All cricketers know which part of the pitch is theirs and which isn't. My only issue is that there is a different rule for ODI's and other cricket. In the league I have batters 2 yards out of their crease before i release the ball. That's cheating, I'll run them out, bugger warning the cheats. Its either a Law or not.
No, but the keeper has outskilled the batsman, and thus won their individual competition.
At what point should a batsman back up out the crease?
Many batsman walk down in time with the bowlers action, if the bowler complete's his action but doesn't release the ball the batsman may have left the crease but not through trying to steal a run but because the time the bowler has gained from holding on to the ball the batsman has continued his forewards movement. I don't feel I've worded that brilliantly, someone else may do better.
If a batsman is blatantly out his crease trying to get a run then fine, but if they're backing up slowly/as we're taught as colts then for me it's the bowler trying to steal a wicket as he's admitting he can't beat the batsman otherwise.
I'm happy for Mankad'ing to be in the game, but I believe once the delivery stride is entered if the bowler doesn't bowl it should be dead ball. Once their backfoot has landed I don't think you should be able to be out mankad for the reason above.
-
My issue with Mandkad is not that it is about stealing yards.
I can be nearly half way down the track after the bowler releases the ball. The point is once they are at the top of their delivery I am half way down the track and still in my crease length of my arms + the length of my bat
I leave as they release the ball - which is not stealing yards. however to Mankad you will often see the bowler complete their action, turn around and then run the batter out. I haven't done anything illegal or broken the law however the bowler has "tricked me"
I think it will always leave a bad taste as you are expecting the bowler to release the ball when they are completing the delivery. I equate it to batters pulling away as the bowler reaches the delivery stride to irritate a bowler. They could have seen a fly but it's just "playing dirty" to gain an advantage.
not my cup of tea but it is a legal part of the game
-
@Mpt7 you do know that's not how the Mankad law works? The bowler cannot run a batsman out backing up after he has completed his delivery action. Under the current law the run-out must happen before the bowler's back foot has even landed. If you've actually been run out as you describe, you shouldn't have been!
Law change makes sense to me, at present a Mankad pretty much has to be premeditated. With the change, if the bowler jumps and notices a batsman legging it down the track he's allowed to pull out of his action and run him out. More fit for purpose that way.
-
@edge if the bowler jumps then they still have to land. yes if you have some daft person charging down the wicket then you can essentially run them out but i still expect people to push the boundries to try and gain an advantage. it will always matter that much to someone
-
I've played in two games this season where this has come up. One of them was our bowlers acting like a complete idiot and mankadded their batsman without a warning, luckily common sense prevailed. The other was against one of our batsman who wasnt even out of the crease when the bowler kept stopping and told him he'd already warned him, on each occasion our bat told him to go for it as everytime he wasnt out of his crease. It was their umpire who then told our bat he was causing trouble and should stop it immediately, all a bit baffling tbh
I dont think this should be part of the game but think some clarity is needed around it. Making it "easier" to do will only result in more occurrences of this particularly at club level
-
@Mpt7 you do know that's not how the Mankad law works? The bowler cannot run a batsman out backing up after he has completed his delivery action. Under the current law the run-out must happen before the bowler's back foot has even landed. If you've actually been run out as you describe, you shouldn't have been!
Law change makes sense to me, at present a Mankad pretty much has to be premeditated. With the change, if the bowler jumps and notices a batsman legging it down the track he's allowed to pull out of his action and run him out. More fit for purpose that way.
I didn't know this, it is relieving to hear.
My worry being the rule is known but the details not. Do I trust the umpire to know this?
-
I've played in two games this season where this has come up. One of them was our bowlers acting like a complete idiot and mankadded their batsman without a warning, luckily common sense prevailed. The other was against one of our batsman who wasnt even out of the crease when the bowler kept stopping and told him he'd already warned him, on each occasion our bat told him to go for it as everytime he wasnt out of his crease. It was their umpire who then told our bat he was causing trouble and should stop it immediately, all a bit baffling tbh
I dont think this should be part of the game but think some clarity is needed around it. Making it "easier" to do will only result in more occurrences of this particularly at club level
Easy solution, don't leave your crease until the ball has left the bowlers hand. It's not rocket science
-
Easy solution, don't leave your crease until the ball has left the bowlers hand. It's not rocket science
Yep. Are you in the crease? No? Then you're out.
Batsmen always moaning about one thing or another ;)
-
If the non striking batsman only just makes it to the strikers end because he was backing up too far then his 'cheating' has prevented a legitimate run out.
-
The best, most simple and elegant explanation and justification is the actual rule change itself:
"A non-striker who is out of his crease before the point of release is either taking an advantage or is acting carelessly, and runs the risk of being legitimately run out"
Couldn't have said it better myself.
-
So has this rule changed now ? As in, can it be used this weekend etc ?
-
No gets updated officially October 1st 2017
-
the laws of cricket presently say the bowler cannot run the batsman out once he is in his delivery stride. Once the bowlers back foot has landed you can back up. The problem arises with the ODI regulation about once the bowler has let go of the ball. The bowler can choose not to let go of the ball whereas he cant pretend not to land his back foot.
-
the laws of cricket presently say the bowler cannot run the batsman out once he is in his delivery stride. Once the bowlers back foot has landed you can back up. The problem arises with the ODI regulation about once the bowler has let go of the ball. The bowler can choose not to let go of the ball whereas he cant pretend not to land his back foot.
So stay in your crease until you are sure ?
-
What I don't like is when you are legitimately backing up and you turn to watch the striker, only to find the bowler has stopped and is trying to take your bails off. When you time your backing up to leave the crease at the time of release and them stopping means you leave the crease
-
What I don't like is when you are legitimately backing up and you turn to watch the striker, only to find the bowler has stopped and is trying to take your bails off. When you time your backing up to leave the crease at the time of release and them stopping means you leave the crease
Exactly what happened to me a few weeks ago; the bowler was through his action and still took the bails off. Got a warning in the end after a dispute, ended up costing them 68 runs :D
-
What I don't like is when you are legitimately backing up and you turn to watch the striker, only to find the bowler has stopped and is trying to take your bails off. When you time your backing up to leave the crease at the time of release and them stopping means you leave the crease
Delay until you are sure then ?
-
I think the pro mankad camp would say that there is no such thing as "legitimate backing up"...it's not meant to be a risk free thing you take for granted. Just wait for the ball to leave the bowlers hand..I think it's very reasonable - keep watching the bowlers hand, and back up only when you see the ball released.
It's a game of mm now - you shouldn't be able to steal even one mm.