It'd not just length, though. Prediction of line is perhaps more important and, for bowled opportunities, whether the batter is playing close to their pads or not. It's a difficult one to solve as it seems that changing the factors to favour one sort of dismissal, a little more, will have a knock-on effect on other dismissal types. We can only guess at how it is coded and I'm 100% sure BA are way better than us at coming up with ways to make appropriate adjustments.
That said, I'd love it if there was a bit more evidence of a good bowling spell (going passed the edge a few times in an over, good line and length not allowing the batter to free their arms, nicked edges that don't quite carry, back-to-back maidens, restricting runs with a required run rate creeping up, sharp turn from spinners not being read, ball starting to swing, etc.) making the likelihood of a wicket increase a bit. Not making it certain...we still want those recoveries of run rate after defensively seeing off the new ball, for instance...but just more of a pattern that if you bowl well, wickets are more likely; if you bowl poorly or the batter gets in, then it should become harder to get them out. Certainly not suggesting that it becomes formulaic: bowl two maidens = 1 wicket...just that the odds of a mistake edge up a bit. And the mistakes should be things like increased errors in judging line or length, reaching for wide deliveries that they should have left, playing away from the body, picking the wrong ball to attempt to hit for a boundary, clumsy defensive pushes granting edges or bat-pad chances, playing with the pads to a ball that goes straight...essentially all the things I do whenever I'm batting in DBC17, no matter how many hours I put in.
