correct me if I'm wrong, but as he made no attempt to play a shot he can't steal a run anyway?not an attempt to steal a single or going down the crease to play the ball.
Might be a gap in my knowledge sonI don't know. Doesn't matter anyway the point is he wasn't trying to claim an advantage just a brain fade.correct me if I'm wrong, but as he made no attempt to play a shot he can't steal a run anyway?
He scored 155! Nonsense comment of the highest order. Sure he'll score 200 off with 1s and 2s players don it all the time....I knew Stokes would get out. He had too many shots that were reckless, even though they went for boundaries, and he constantly seemed frustrated when hitting to a fielder. He was too impatient. McCullum is rubbing off on him in a very bad way.
Before Stokes got out, they could've won the game with 1's and 2's. And the odd boundary. The shot Stokes got out with shows his impatience.
Did you even read what I said ? He basically threw the game away even though he scored 155. It's irresponsible batting.He scored 155! Nonsense comment of the highest order. Sure he'll score 200 off with 1s and 2s players don it all the time....
Yeah let's blame the guy who through his gustsy batting managed to put us in a position with a long tail where we might of queeked over the line. Do you actually watch test cricket, do you actually know how hard it is to chase down 70+ runs? With the tail.Did you even read what I said ? He basically threw the game away even though he scored 155. It's irresponsible batting.
Short ball has been awkard for both sides on this Lords pitch. I think we go back to day 1 and one wicket taken. Probably let Australia score 100 runs too many. Not to say we haven't lost it due to other areas since but it feels like that the crucial part and we've been playing catch up ever since.A good effort from Stokes, but the game was lost much earlier with some reckless batting.
In that situation "unsporting conduct" meant "letting the officers win"That run out reminds me of a cricket game I played in the army. On the basis that I could bowl a ball in the general area of the wicket I ended up spammed for the Sqn cricket team. We played the HQ Sqn which was full of all the regimental big wigs. Our wicker keeper was a grizzly Staff Sergeant who had actually played for Essex as kid before joining up. He stumped out most of the HQ batting line up who kept wandering outside the creese after the ball had been bowled. It took the loss of their entire top order before they actually stopped doing it. The CO lost his cool a bit and protested about "Unsporting conduct" but in the laws of the game there was nothing wrong with the dismissals much to anger of the mainly public school/officer heavy HQ side a much to the amusement of our mainly enlisted Sqn side. I'm just shocked it doesn't happen more often.
Thing is the umpire was already starting to give the bowler his things so in his mind it was over, but technically it hadn't been called. For me, like a mankad, if this becomes a thing then it's just going to waste time. It's a trick that should only work once in a while and it's a cheap trick because 99% of the time players aren't going to waste time on that kind of nonsense. Even the majority of his team were acting like the over was finished, but were happy to take advantage of one player being sneaky.The Spirit of the Game law and the fact you can actually withdraw an appeal always makes things like this more nebulous. At least it wasn't a mankad.
In this kind of situation how often does dead ball actually get called in a cricket match? Nobody is entirely sure if umpires called over or not.