Platform: Xbox One X
Game Version: v 0.1.1292
Game Mode: Ashes series
Match Type: Test
Teams used: England v Australia
Ground: Lords - second test, specifically. (However, have seen this same issue in countless other matches, modes, & venues as well.)
Over Count: 67th over, and again in the 69th over, (although repeatedly happening randomly).
Issue: Wicket keeper standing up to the stumps for a spinner repeatedly missing basic catches or stops, (ball not struck/nicked by the batsman & the ball not bowled wide).
I'm aware there have been countless complaints of keepers simply not reacting at all since game release to fast or spin bowling when it's a ball they could undoubtedly have reached or at least got a glove to if they actually tried, but instead decided to become an on field spectator. Failing that, at the very least they could attempt to reach any tough chances rather than just standing there. (Like the absolutely inhuman & Herculean leaps I keep seeing from certain fast bowlers who are apparently capable of launching themselves completely over & across the pitch in the blink of an eye, (whilst instantly reversing their direction of travel too) to catch a fast moving ball off their own bowling.). Yet, it seems that it's intentional to portray specialist wicket keepers in game as lazy who just can't be bothered to put any effort into the tougher chances or that they're just utterly incompetent. (I often see 1st slip making a ridiculous dive across to take a ball headed straight for the keeper as well.). This seriously needs attention & it's not like there hasn't been sufficient time to address these issues since the game was released.
What's more, after noting at least two of these occurrences in one innings for this bug report, both times the ball missed absolutely everything as it passed by the batsman & the stumps, (although they weren't wides either). Again, the keeper just stood watching as the ball passed by. However, the AI batsmen ran 2 or 3 runs both times despite no contact of any kind with the ball & the umpire then incorrectly signalled "leg byes" instead of the actual "byes", & these byes were then incorrectly recorded as leg byes on the scorecard as well. (Granted, a small issue as technically the batting side gets the same benefit either way but it really should be factually correct.)
(These are yet more issues I'm seeing
repeatedly in
multiple different match types, game modes, & at
multiple different venues. It's not just specific to this match alone.)
With regards
.