Print

[ppccopener]

Used to play Cheltenham civil service on tour years ago.

You can't raise your hands but I've seen it myself in out league happen so let's not throw stones in glass houses.

I do think this 'send off' business needs to be eliminated and treated just as a physical contact offence.

There's no need for it and most incidents start from here that I have seen.if there's a flashpoint it's usually this.

[SOULMAN1012]

Played a great game of cricket today. Oppo won the toss and batted and sent out Div 2 on Sat opening bat and they were 100-0 off 13. Young lad nicked him off to me and then the rest played around the other opening bat most of whom where younger players with a few county U15 and U16 players and they made 212-6 off 40

We made an ok start getting 25-1 off 6 when I came in at 3 and had a good partnership with other opener until on 31 my partner smashed and I mean smashed a straight drive back that the bowler turned away and jumped out the way off for the ball to smash of his boot and run me out at non strikers end, hows your luck. Lost a few more wickets and need 70 off last 10 and new lad that joined our club this year hit winning runs off the last ball of the game with us 9 down so last ball was either 1 run to win or a wicket and they won. Both teams throughly enjoyed the game. Our 12yr old county player who was given ok to play senior league cricket this week by his county coach picked up hid first senior wickets and also ended up 2*.

Starting to wonder why I play on Saturdays at the moment.

[ProCricketer1982]

Starting to wonder why I play on Saturdays at the moment.

because that sounds like a really good game.. 9 down, last ball win/loss (kinda doesn't matter) chasing somewhere between 180-220 ( less than 180 is a bit crap and more than 220 and it's a bit sloggy).. sounds pretty darn perfect Chris (excluding your bad luck on how you got out naturally)

[wcc]

Finally converted 20s and 30s to score 105 off 111 on Saturday. We posted 364/7 off 50 and bowled the opposition out for 105.

First ever 100 and i think only the second game ive played were we posted over 300 so a good day all round.

[edge]

Been a weird season but this week was one of the oddest games I've played in a while - opposition just didn't seem interested in trying to win the game. We stuck them in (I thought generously) on a slow but very much flat deck, one opener got yorked first ball but then they pretty much blocked it out and didn't even attempt to accelerate until the last 5 overs or so despite having plenty of wickets in hand. 148/7 off 40, way under par. Their bowling was mostly unambitious at best, opener was decent but first change bowled seam off two paces, we set off at 5 an over and were cruising. Sweepers out and pretty much no catching fielders from the first over. 30 runs to win they appear to suddenly wake up and spring a pacey youngster out of nowhere, he immediately nicked our set batsman off but all far too late and we won with nearly 12 overs to spare. Pretty much a repeat of the reverse fixture early in the season where they blocked to an under par total and we chased it one down. Guessing they didn't have their strongest side out, but what's the point? This is a team who are in a nip/tuck relegation battle and only one place below us in the league, just don't understand why they were so negative.

[ProCricketer1982]

Guessing they didn't have their strongest side out, but what's the point? This is a team who are in a nip/tuck relegation battle and only one place below us in the league, just don't understand why they were so negative.

If they didn't feel they could win or if they only had say 2-3 actual batsmen then why throw your wicket away?  Crap day if you go out there trying to score 250+, get out for 10 after all.. costly in time, money and energy. Have to assume there was a reason for it though as I doubt many players/teams go out there to lose intentionally.


random one.. It amuses me every innings both when fielding and batting that we have 'power plays'.. I'm yet to see any amateur team actually have the ability to genuinely use a power play (and no, sending out a hitter in a hit and hope style isn't really using it properly). I don't really get why they bother trying it as teams just don't have the batting power of professional team, the ability or the inclination of players to willingly throw their wicket away more than the odd time.

[edge]

If they didn't feel they could win or if they only had say 2-3 actual batsmen then why throw your wicket away?  Crap day if you go out there trying to score 250+, get out for 10 after all.. costly in time, money and energy. Have to assume there was a reason for it though as I doubt many players/teams go out there to lose intentionally.

No need to throw your wicket away, but you'd think at least aim for enough to give your bowlers a chance. They didn't appear to run out of batsmen at any point, number 8 was a young lad but still looked like he could hold a bat.

[mo_town]

1) Send off's really do need to be eliminated
2) Verbals on the field caused in the end things to boil over and someone to 'crack'.. It really is an amateur game , not some pro level stuff so just needs cutting out

Village or pro cricket, I think there is no place in cricket for such behaviour and this needs to be enforced right at the top in international cricket. What else can we expect when we see international cricketers do the same on Television. Ppl perceive such behaviour as 'cool' and emulate the same at their level. There need to be stricter laws against such things to make people understand that it is just not acceptable.

[ProCricketer1982]

No need to throw your wicket away, but you'd think at least aim for enough to give your bowlers a chance. They didn't appear to run out of batsmen at any point, number 8 was a young lad but still looked like he could hold a bat.

anything less than 180 and you're not really giving your bowlers a chance as you say. 180-225 makes it a good game

[DiscoStu]

We had an interesting incident on Saturday, and one which I'm not sure what the correct outcome should have been.
We are comfortably mid-table, opposition probably need 1 or 2 wins to steer clear of relegation. So the match means a little more to them. We batted first and our opener was given out LBW by their umpire when he clearly got some bat on it. Their skipper immediately said it should be not out, decision is reversed. Everyone is happy. The opposition then bat and they are in trouble when their skipper comes to the crease (90-5 chasing 180 fwiw). First ball he gets hit on the pads, we go up and their umpire gives him out LBW. He says that he hit it. Our bowler thought it hit both pads or his bat hit his pad (two noises), our keeper thought he hit it, our skipper was at point so had no idea. We said that we'll stick with the umpire's decision as we aren't sure. Their skipper blows a gasket, accuses the bowler of cheating but walks off after a couple of minutes of debate and indecision. It left a bad taste in the mouth and although we won it felt very hollow not because of our efforts but because of this and our bowler reacting negatively to being called a cheat.
So what would you guys have done? Should the fact that they reversed a decision in our innings have any bearing on this incident? Does the fact that it's their umpire have any bearing?

Genuinely interested to see any thoughts on this because we, as a team after the match, couldn't agree.

[ProCricketer1982]

We had an interesting incident on Saturday, and one which I'm not sure what the correct outcome should have been.
We are comfortably mid-table, opposition probably need 1 or 2 wins to steer clear of relegation. So the match means a little more to them. We batted first and our opener was given out LBW by their umpire when he clearly got some bat on it. Their skipper immediately said it should be not out, decision is reversed. Everyone is happy. The opposition then bat and they are in trouble when their skipper comes to the crease (90-5 chasing 180 fwiw). First ball he gets hit on the pads, we go up and their umpire gives him out LBW. He says that he hit it. Our bowler thought it hit both pads or his bat hit his pad (two noises), our keeper thought he hit it, our skipper was at point so had no idea. We said that we'll stick with the umpire's decision as we aren't sure. Their skipper blows a gasket, accuses the bowler of cheating but walks off after a couple of minutes of debate and indecision. It left a bad taste in the mouth and although we won it felt very hollow not because of our efforts but because of this and our bowler reacting negatively to being called a cheat.
So what would you guys have done? Should the fact that they reversed a decision in our innings have any bearing on this incident? Does the fact that it's their umpire have any bearing?

Genuinely interested to see any thoughts on this because we, as a team after the match, couldn't agree.

You will get two answers


Those who simply care about winning will say 'he's out'

Those who want to win but want to win fairly will say ' call him back'...

you can't rely on umpires, especially club/league ones.. they are terrible

sadly, this happens way to often.. a bowler from one end saturday appealed three times on me.. I hit every single one and at one point he not only double appealed but was on the floor then spent the next x balls clapping me and generally being rude.. If that's the type of cricket people want then so be it. Problem is, with league umpires it's so worth a shout as they are so poor that players no longer play fairly.. always trying to steal a decision even though they know it's not out. THen call it 'part of the game'

[Jimbo]

I don't think there's any obligation to call someone back unless you're certain they were given wrongly, particularly when it's their own player umpiring. We've called guys back this year and had one of our guys called back.

Equally, Saturday I had a catch turned down by the oppo umpire because he couldn't see me take it cleanly. I was 100% it was a clean catch, batsman thought it bounced before it was taken. If the umpire isn't sure then it's not going to be given, that's part of the sport. Have to accept when it goes your way and when it doesn't I think.

[SurreySam]

The weekend just gone epitomises my season so far. I can't seem to score when I need to and can, when it doesn't really matter.

Saturday league match - 2 ball duck.
Sunday friendly - 51* retired, to give others a knock.

[More Glue Than Wood]

first win in two months (thankfully) on saturday - after losing 6 on the bounce and getting smashed in 3 of those we finally managed to win this weekend - a huge relief for all and with 2 games to go we have a chance of staying up - which will be a good achievement if we do - we are a medium sized club's 3rd team playing in a league with mostly smaller 1st teams - whose teams are normally much stronger/more experienced than we are

[six and out]

We had an interesting incident on Saturday, and one which I'm not sure what the correct outcome should have been.
We are comfortably mid-table, opposition probably need 1 or 2 wins to steer clear of relegation. So the match means a little more to them. We batted first and our opener was given out LBW by their umpire when he clearly got some bat on it. Their skipper immediately said it should be not out, decision is reversed. Everyone is happy. The opposition then bat and they are in trouble when their skipper comes to the crease (90-5 chasing 180 fwiw). First ball he gets hit on the pads, we go up and their umpire gives him out LBW. He says that he hit it. Our bowler thought it hit both pads or his bat hit his pad (two noises), our keeper thought he hit it, our skipper was at point so had no idea. We said that we'll stick with the umpire's decision as we aren't sure. Their skipper blows a gasket, accuses the bowler of cheating but walks off after a couple of minutes of debate and indecision. It left a bad taste in the mouth and although we won it felt very hollow not because of our efforts but because of this and our bowler reacting negatively to being called a cheat.
So what would you guys have done? Should the fact that they reversed a decision in our innings have any bearing on this incident? Does the fact that it's their umpire have any bearing?

Genuinely interested to see any thoughts on this because we, as a team after the match, couldn't agree.

The only time I have ever called someone back in all my previous years as captain was when a bowler of ours mankad'd someone.

Calling someone back for whatever reason is a dangerous game, as your experience shows it can often do more harm than good, as suddenly you expect the same treatment which might not get reciprocated. Then it all kicks off.

And that doesn't make me someone who just cares about winning. Just someone who realises umpires are there for a reason and you get good and bad decisions, that's part of our wonderful game.