No matter how you set the attributes, the game will just decide to over-ride them when it's "wicket time"
I'm not so sure about that, here's what I will say: The fielding still remains a huge issue for me, especially when it comes to catches.
The proof is in the games feedback itself. Lets use this T20 scenario I face all the time... I hit a six, clean over the mid off boundary and the games feedback tells me it's 90 meters. Couple of singles, an over later I hit another six, same place to the same bowler and it goes for lets say, 85 meters. Both times I've watched the replay, both times the trajectory and the arc are about the same, maybe slightly left or right, maybe fractionally shorter but essentially I'm timing it correctly and clearing the boundary easily each time, almost always into the crowd somewhere. The best scenario I can use is I hit the side-screen and got the XP for doing it (a scenario that's happened to me often).
The AI changes the field, pushes mid off back. Great, that's smart AI. The fielder is now on the boundary at mid off... but I decide to take him on anyway. Wait for the right delivery, then I hit another six. The game tells me it's gone 85 meters again, except this time the fielder at Mid Off has run back over the boundary and in the animation-replay he catches it just over the boundary line. Obviously I'm not out, but previously I was clearing the boundary line into the crowd, or hitting the sidescreen and getting it "85 meters" now all of a sudden it's the same measurement but the fielder is catching is just over the line?
Something doesn't add up...
Next time I take on the fielder, with the same trajectory, the same timing or very little change and the ball suddenly drops down, warps from a clearly 'over the boundary' trajectory to Mid Off who stands and catches the ball, and I'm out.
It's hugely frustrating. I don't think it's
scripted per-say ...but there has to be a code in the game somewhere that says if X fielder is within Y distance of the ball, they can catch it. The "Y" needs to be reduced so it's human. The speeds the fielders move in the field, some of the time, are still quite comically superhuman. Just the other night playing online against a random they set a fielder smack bam behind the bowler on the boundary line, who could then cover anything on the boundary position moving left or right from Cover to Deep Midwicket...
...and that's a human player, the AI doesn't do that anymore, but their boundary runners still cover too much ground in the outfield, yet somehow move too slowly towards the ball on many occasions.
That's why I don't think there's scripted dismissals, or edges or anything else. I just think using the field mechanics as a capsule of the games niggles, some elements are just set to incorrect levels of acceptable cricket possibilities. There's absolutely no excuse for an AI (or human) player to place a fielder on a boundary line and be able to have you getting caught out for shots that the game tells you were clearing the boundary both visually and statistically mere moments earlier. I fully believe it's down to the warping-effect that happens in catches because the game allows too larger an area for catches to be possible in relation to the fielder, both vertically and horizontally.
Wow, that's the most I've typed in a long time.
