Advertise on CBF

Pages: 1 [2] 3

Author Topic: Mankad Made Easier  (Read 7844 times)

0 Members and 2 Guests are viewing this topic.

ProCricketer1982

  • Forum Legend
  • ******
  • Offline Offline
  • Posts: 7432
  • Trade Count: (0)
Re: Mankad Made Easier
« Reply #15 on: July 13, 2016, 09:38:08 PM »

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.
Logged

Woodyspin

  • International Captain
  • ****
  • Offline Offline
  • Posts: 2232
  • Trade Count: (0)
  • www.twitter.com/thewoodyspin
Re: Mankad Made Easier
« Reply #16 on: July 13, 2016, 09:41:34 PM »

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.

MD2812

  • International Captain
  • ****
  • Offline Offline
  • Posts: 1504
  • Trade Count: (+2)
  • Hi, I'm Joe
Re: Mankad Made Easier
« Reply #17 on: July 14, 2016, 08:30:21 AM »

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.

Mpt7

  • County 2nd XI
  • ***
  • Offline Offline
  • Posts: 474
  • Trade Count: (0)
Re: Mankad Made Easier
« Reply #18 on: July 14, 2016, 10:22:20 AM »

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
Logged

edge

  • Moderator
  • World Cup Winner
  • *****
  • Offline Offline
  • Posts: 4876
  • Trade Count: (0)
Re: Mankad Made Easier
« Reply #19 on: July 14, 2016, 10:50:47 AM »

@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.
Logged
HS: 156, BB: 7-20

Mpt7

  • County 2nd XI
  • ***
  • Offline Offline
  • Posts: 474
  • Trade Count: (0)
Re: Mankad Made Easier
« Reply #20 on: July 14, 2016, 11:46:35 AM »

@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

Logged

iand123

  • Moderator
  • World Cup Winner
  • *****
  • Offline Offline
  • Posts: 3918
  • Trade Count: (+13)
Re: Mankad Made Easier
« Reply #21 on: July 14, 2016, 11:55:23 AM »

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
Logged

MD2812

  • International Captain
  • ****
  • Offline Offline
  • Posts: 1504
  • Trade Count: (+2)
  • Hi, I'm Joe
Re: Mankad Made Easier
« Reply #22 on: July 14, 2016, 12:18:44 PM »

@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?

ProCricketer1982

  • Forum Legend
  • ******
  • Offline Offline
  • Posts: 7432
  • Trade Count: (0)
Re: Mankad Made Easier
« Reply #23 on: July 14, 2016, 03:51:55 PM »

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
Logged

Big Mac

  • County 1st XI
  • ***
  • Offline Offline
  • Posts: 588
  • Trade Count: (0)
Re: Mankad Made Easier
« Reply #24 on: July 14, 2016, 04:09:16 PM »

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 ;)
Logged

Gurujames

  • International Captain
  • ****
  • Offline Offline
  • Posts: 1663
  • Trade Count: (0)
Re: Mankad Made Easier
« Reply #25 on: July 14, 2016, 04:12:48 PM »

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.
Logged

brokenbat

  • International Captain
  • ****
  • Offline Offline
  • Posts: 2319
  • Trade Count: (0)
Re: Mankad Made Easier
« Reply #26 on: July 14, 2016, 05:04:46 PM »

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.
Logged

ProCricketer1982

  • Forum Legend
  • ******
  • Offline Offline
  • Posts: 7432
  • Trade Count: (0)
Re: Mankad Made Easier
« Reply #27 on: July 14, 2016, 05:31:38 PM »

So has this rule changed now ? As in, can it be used this weekend etc ?
Logged

Batbuddy99

  • County 1st XI
  • ***
  • Offline Offline
  • Posts: 925
  • Trade Count: (0)
  • https://royalascotcc.co.uk
Re: Mankad Made Easier
« Reply #28 on: July 14, 2016, 07:20:06 PM »

No gets updated officially October 1st 2017
Logged
Still working on turning massive netting potential into real match runs

KIPPERS

  • County 2nd XI
  • ***
  • Offline Offline
  • Posts: 381
  • Trade Count: (0)
Re: Mankad Made Easier
« Reply #29 on: July 14, 2016, 11:20:20 PM »

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.
Logged
Best bowling 9-33  7-26  best bat 53
Pages: 1 [2] 3
 

Advertise on CBF