Important Batting Loophole for Pace Bowling

[Mubashwer]

I was finding batting very challenging and fun until I found an easy way to slog boundaries. If I have the batsman move across the crease, exposing the wickets behind him, one can slog easily in the region behind square leg.

If there is a no fielder in fine leg/ deep fine leg / square, keeping the L stick between 6'o clock and 7'o clock will lead to boundaries. Even non-ideal timing will almost always get the ball beyond the fielder in the backward short leg. (Same timing will lead to catch when slogging in the cover/mid-off region fielder at mid-off or cover)

If there is a fielder in the fine leg / deep fine leg, keeping the L stick at 8'o clock and slogging will lead to boundaries. It will almost always be away from the fielder at backward square leg.

When there is a fielder at Square, it might be a bit risky but I have not tried it out much.


Problem is, I have been hitting boundaries and boundaries in this way against Pace bowling (leading to easy victories) and its not challenging nor fun. I don't want to tinker with difficulty settings cause timing of other shots are in the sweet spot for me and I don't want to ruin that. You can say I can just seal it off, but if there is a way to slog and get runs faster, I itch to use that. I want to use this shot but this should be a bit more difficult to execute with more risk.

Realistically, these shots should not have the same power as slogging in the cover/mid-off/on region. It should be a bit more difficult to do if the ball is quite a distance away from the leg. Currently this shot is safer than most normal ground shots.

So I request @MattW to please try to do something to nerf it a bit. Maybe reduce its power or make it more difficult to connect if the ball is far away from the leg?

I have included a couple of the shots in the video for example. The second one is relatively good timing but even poorer timing won't get caught. Video: sloggging behind square - Streamable

 

[passwordistaco]

What level are you playing?

 

[Mubashwer]

What level are you playing?

Medium/Medium/Veteran. I also tried out hard, but these shots were still easy. I don't want to change difficulty because of one shot. I'll try to seal it off I guess.

 

[passwordistaco]

I've just tried doing this too and it worked an absolute treat. Hit a 15 ball 50 on pro. It's like there is no risk associated with it as the fine leg and square leg are up

 

[mattk]

Just tried this and I was able to score tons of runs through a vacant mid on and mid wicket as well. I don't think its something that Big Ant needs to worry about because the easiest way for the loophole not to be a problem is just not to use it.

 

[cricket_online]

Just tried this and I was able to score tons of runs through a vacant mid on and mid wicket as well. I don't think its something that Big Ant needs to worry about because the easiest way for the loophole not to be a problem is just not to use it.

This should be fixed and IMO it will be fixed when Big Ant fix the poor OOB fields which are way too aggressive and most of them not realistic. I mean how many fields in real world don't have a fielder at deep fine leg or someone behind square on the leg side? Or how many times are there fields without mid on even when you score bunch of runs through the gap or fields with multiple close-in fielders and just 2 outside the fielding circle in shorter formats! Once the poor AI fields go away, issues and loopholes like these will also go away.

 

[mattk]

This should be fixed and IMO it will be fixed when Big Ant fix the poor OOB fields which are way too aggressive and most of them not realistic. I mean how many fields in real world don't have a fielder at deep fine leg or someone behind square on the leg side? Or how many times are there fields without mid on even when you score bunch of runs through the gap or fields with multiple close-in fielders and just 2 outside the fielding circle in shorter formats! Once the poor AI fields go away, issues and loopholes like these will also go away.

Yeah actually I agree with you. That's a great point about the fields.

 

[Drsniper]

I was finding batting very challenging and fun until I found an easy way to slog boundaries. If I have the batsman move across the crease, exposing the wickets behind him, one can slog easily in the region behind square leg.

If there is a no fielder in fine leg/ deep fine leg / square, keeping the L stick between 6'o clock and 7'o clock will lead to boundaries. Even non-ideal timing will almost always get the ball beyond the fielder in the backward short leg. (Same timing will lead to catch when slogging in the cover/mid-off region fielder at mid-off or cover)

If there is a fielder in the fine leg / deep fine leg, keeping the L stick at 8'o clock and slogging will lead to boundaries. It will almost always be away from the fielder at backward square leg.

When there is a fielder at Square, it might be a bit risky but I have not tried it out much.


Problem is, I have been hitting boundaries and boundaries in this way against Pace bowling (leading to easy victories) and its not challenging nor fun. I don't want to tinker with difficulty settings cause timing of other shots are in the sweet spot for me and I don't want to ruin that. You can say I can just seal it off, but if there is a way to slog and get runs faster, I itch to use that. I want to use this shot but this should be a bit more difficult to execute with more risk.

Realistically, these shots should not have the same power as slogging in the cover/mid-off/on region. It should be a bit more difficult to do if the ball is quite a distance away from the leg. Currently this shot is safer than most normal ground shots.

So I request @MattW to please try to do something to nerf it a bit. Maybe reduce its power or make it more difficult to connect if the ball is far away from the leg?

I have included a couple of the shots in the video for example. The second one is relatively good timing but even poorer timing won't get caught. Video: sloggging behind square - Streamable

Is this on PS4/XBone or PC?

 

[Jerm]

This should be fixed and IMO it will be fixed when Big Ant fix the poor OOB fields which are way too aggressive and most of them not realistic. I mean how many fields in real world don't have a fielder at deep fine leg or someone behind square on the leg side? Or how many times are there fields without mid on even when you score bunch of runs through the gap or fields with multiple close-in fielders and just 2 outside the fielding circle in shorter formats! Once the poor AI fields go away, issues and loopholes like these will also go away.

Too many pre-set fields I think are wrongly categorised, I get "Defensive" fields with 3 slips and 2 outside circle? etc...

I think they need to fix ALL the pre-set fields, and maybe allow users to select which pre-set fields can be used by AI, or some way for the user to have some input here..

 

[Pat]

This should be fixed and IMO it will be fixed when Big Ant fix the poor OOB fields which are way too aggressive and most of them not realistic. I mean how many fields in real world don't have a fielder at deep fine leg or someone behind square on the leg side? Or how many times are there fields without mid on even when you score bunch of runs through the gap or fields with multiple close-in fielders and just 2 outside the fielding circle in shorter formats! Once the poor AI fields go away, issues and loopholes like these will also go away.

AI fields are an issue reported for DBC 14 as well. This definitely should have been fixed in 17 but I can understand you can't sell that on the back of the cover - "New intelligent fields set by CPU based on match conditions" is perhaps not good enough feature for marketing. The fact that it is still not fixed has me worried because it means either it's too complex (which means we need to realise a patch cannot fix it) or perhaps low priority for them at this point.

 

[zimrahil]

Agree with above - better default AI fields will help alleviate this issue

 

[ben1983]

I think when the AI takes out mid on in the longer forms of the game its quite good, it makes you go for a slog and opens you up for edges, especially I dbc17, didn't matter in dbc14 as edges were rarer than rocking horse sh*t. I tried the fine leg slog and could score easily, although the super human keeper did catch a couple off spinners.

 

[Mubashwer]

Is this on PS4/XBone or PC?

PC. But I don't think there isn't much difference after patch 3.

 

[cricket_online]

Too many pre-set fields I think are wrongly categorised, I get "Defensive" fields with 3 slips and 2 outside circle? etc...

I think they need to fix ALL the pre-set fields, and maybe allow users to select which pre-set fields can be used by AI, or some way for the user to have some input here..

IMO I would make things simple. I will just have 5 fields each in the following categories for pacers and corresponding ones for spinners...
- Aggressive/Attacking
- Balanced
- Conservative
- Defensive

Essentially you have only 20 fields for pacers and 20 for spinners. So total 40 basic fields which are realistic would be much better than bunch of weird ones. E.g., in shorter formats I usually see a field where nearly the whole leg side doesn't have a fielder between overs 40-50 or when 6th wkt falls (and any wkt after that). Do you really need such a field? I say keep it simple and limit the no. of OOB fields which are realistic and actually do what they are supposed to such as conservative or defensive.

 

[cricket_online]

I think when the AI takes out mid on in the longer forms of the game its quite good, it makes you go for a slog and opens you up for edges, especially I dbc17, didn't matter in dbc14 as edges were rarer than rocking horse sh*t. I tried the fine leg slog and could score easily, although the super human keeper did catch a couple off spinners.

It may be a decent tactic for a short while. But when you see batsmen plundering runs in that area then any team would change tactics and plug the gap. AI doesn't.