Atko wrote: ↑Mon Sep 02, 2024 2:35 pm
Won toss, put 'em in, they scored 167-5, we scored 140-5. Same old story -
every batsman on aggro, but incapable of hitting the ball off the square, and still 5 wickets in the shed at the end. They should add a hyper-aggro option, maybe the buggers would start swinging the bat then?
I'll put it down to tight bowling by The Tykes and the nature of the pitch.
spark wrote: ↑Tue Sep 03, 2024 2:18 pm
.....
Every batter on aggro might be part of the problem. I think if you use too many aggressive or too many defensive orders they become less effective. I think if you have over a certain % of aggressive batters then the aggression tapers off. What that percentage is I've no idea.
I'd guess it's something like if you have 1 or 2 who have aggressive orders then they'd be very aggressive but if you have 5 or 6 they'd move more towards normal so might only be mildly aggressive.
casperj wrote: ↑Tue Sep 03, 2024 3:48 pm
.....
I'm not convinced that aggresive orders on batsmen works very well. In my limited experience about 50% of the time the batsmen scores at normal or slightly faster rates, and the other 50% of the time it's an 'out 4th ball for 1' sort of outcome. I use it very sparingly, and only when I'm certain that I can afford a few cheap wickets.
I'd recommend having a match with every batsmen on neutral (or with maybe 1 or 2 of the tailenders on agg) and see how that goes in comparison.
Yeah, the total aggro orders was something I started experimenting with last season when my youth squad was dropping rather low ratings-wise, of all places, in YOD, where I had a small degree of success. I concluded that T20 would be a natural environment to try that approach, but thusfar it's proven a bit of a damp squib. I've probably employed neutral orders for the majority of my FTP gameplay; I remember ash saying once in the old "ask ash" thread that the basic (or neutral) AI algorithm would adjust the batsman's approach to the conditions and match state of play; also that there was a sort of bit of "rubber band" coding that would over ride defensive or aggressive orders if they pushed the run rate curve too far out of shape from the norm. Back then I figured from this, that the ME knew best, so always had everyone on neutral - even the bowlers - and found this to be a successful approach.
I'd be disappointed, spark, if indeed there was a "normalizing" where blanket aggro orders were set, but assuming there have been no major changes to the ME since ash's "rubber band" comments, then I guess that may well be the effect I'm seeing.
Anyhoo, today we faced Two Star CC, and for some bizarre reason I forgot to change my orders, winning the toss and batting first (uh-oh) -
Two Star CC vs The Raging Speed Horns
League Twenty20 3.3
Weather Hot
Pitch Even
- we scored a lacklustre 127-10 off 19.4 - all aggro
- I don't mind too much though - at least we had a few swings and misses! In reply, the oppo knocked off the runs in 16 overs for the loss of a couple of wickets. That loss takes us back into the relegation zone with one win from 5 games.
Match Ratings
Two Star CC The Raging Speed Horns
Batting - Top Order 12,429 11,235
Batting - Middle Order 7,800 8,172
Batting - Tail 4,353 5,914
Bowling - Seam 11,646 (8) 11,130 (16)
Bowling - Spin 10,845 (12) 11,235 (4)
Fielding/Keeping 14,149 15,133
Overall 192,252 196,528
On a positive, our 2nd XI are inching ever closer to 200k