Incorrect run out bug.

eaglesrjh

School Cricketer
Joined
Sep 17, 2014
Guess this may be a tough one to sort but will describe as best I can.

In short I was run out by someone throwing the stumps down despite the fact they where already broken. This I believe is against the rules of cricket as once the stumps are broken and the bails off then a run out can only be done by pulling a stump out of the ground with ball in hand or possibly by knocking a stump clean out of the ground with a throw or by rebuilding the wicket and knocking them down again.

in gameplay terms this is what happened,

hit a straight drive and started to run.

ball hit the non striker and deflected onto the stumps knocking the bails off (no fielder had touched it so this is correctly not out)

continue run, bowler runs back, picks up the ball and throws ball, hits stumps but does not remove one of them from the ground by any means.

given run out whereas by the rules of cricket (as I understand them) I should have been safe.

If I'm wrong on the rule then please let me know.
 
It seems reasonable at this point for them not to have that part of the rules entirely implemented. Whilst it would be nice to see it in the future, it would be a lot of work in the first attempt for something quite rare.
 
thanks for the confirmation guys, as said in my post I guessed it may not be an easy one to sort as it's quite a complicated rule.

No bother, rare event, will take this run out on the chin and know better for the future.

still a great game.

Thanks.
 
There's another similar kind a bug I want to point out.

Pacer bowling to me, I left the ball. Keeper takes it on its way back.
I just press the run button and quickly press the return immediately. The batsmen returns before the keeper hits the stumps with an underarm throw. After all this, the ball seems to tangle in the wickets and the wickets-hitting-sound keeps on coming after every two seconds. I start to run again as the keeper didnt approach the wicket. As soon as i leave the crease, the wicket-hitting-sound (without anybody near the wicket or the ball) comes and I am given run out!

Has anybody else experienced the same?
 
Yes I've had that when I first got the game.

I've just accepted it as a limitation of the game, it's designed to check if you're in the crease when the ball hits the stumps, if not you're out.

Not really a bug as such, just the code doing it's thing.
 
Good share. Also, during a BARS reply, even though the replay shows that bowler landed his foot much above the bowling crease, its not taken into consideration and the batsmen will be given out. Isn't this a blunder? @BigAntStudios
 

Users who are viewing this thread

Top