Cricket 19 General Discussion

[Deleted member 185125]

I personally feel the controls are very well captured, except the defense shot (will talk about this towards the end).

Cricket as a game generally involves a lot of premeditation, whether its batting or bowling, though the premeditation is not limited to a single shot (or delivery) per se, but a set of two/three alternate plans with a backup option. E.g. almost every single international batsmen, if you talk to them or even listen to their interviews, will tell you that they premeditate what the bowling team is upto and thus decipher what the bowler is going to bowl next (listen to Kohli's statement about Rashid Khan when the captains were interviewed together just before the WC. He talked about how it was only in this edition of the IPL, While sitting in the dressing room he was able to predict 11 of the 12 balls he bowled, after 3 years of playing him in the IPL. That shows that batsmen work on these things which shows that they need to work on them because it's impossible to score consistently in cricket if you are not able to predict the bowling).

The batsmen thus target some areas of the field on the basis of their prediction of where the bowler is going to bowl next.

However, if the ball is not bowled where they expect it to, they still have a plan B and maybe a plan C in place which mostly involves them adjusting their shot on the basis of what is bowled to them, and this is where I feel the current defence shot controls need to be 'expanded' a bit, to allow you to stop your shot and turn it into a defensive one (this is what the commentators refer to as 'checking the shot'), which is such a key element of the game of cricket. This is the plan B or C that the batsmen have incase the ball does not land where they expected it to.

After playing the last game, I had posted an idea on these forums (and also sent it as a PM to Ross, Mikey and MattW) that it would be great if we could stop the RS while moving it forward (using the legacy controls for playing a shot. The new controls are....well not for me), before it crosses the center point of the axis, the shot should be registered as a defense by the game (and maybe later it can be further enhanced to make the ball chip up in the air if we played the shot too early or stopped it marginally after the center point of the axis).

Leaving the ball in this game already caters to this as you can press the RS at the last second to leave the ball even if that wasn't your plan A (so you didn't premeditate it but adjusted on the basis of the ball bowled to you). However there is no such option to adjust your shot to a defensive one as for this you need to press a trigger on the controller and thus is not intuitive.

Maybe BigAnt can change the controls to pressing L3 for leaving the delivery and pressing R3 for defensive shot, if it's not possible to implement what I suggested earlier.

Will definitely work if the game can identify the pressure applied on the Trigger button or/and the force applied on the sticks while on classic controls. Probably be difficult to implement for standard controls.

 

[cricket_online]

I personally feel the controls are very well captured, except the defense shot (will talk about this towards the end).

Cricket as a game generally involves a lot of premeditation, whether its batting or bowling, though the premeditation is not limited to a single shot (or delivery) per se, but a set of two/three alternate plans with a backup option. E.g. almost every single international batsmen, if you talk to them or even listen to their interviews, will tell you that they premeditate what the bowling team is upto and thus decipher what the bowler is going to bowl next (listen to Kohli's statement about Rashid Khan when the captains were interviewed together just before the WC. He talked about how it was only in this edition of the IPL, While sitting in the dressing room he was able to predict 11 of the 12 balls he bowled, after 3 years of playing him in the IPL. That shows that batsmen work on these things which shows that they need to work on them because it's impossible to score consistently in cricket if you are not able to predict the bowling).

The batsmen thus target some areas of the field on the basis of their prediction of where the bowler is going to bowl next.

However, if the ball is not bowled where they expect it to, they still have a plan B and maybe a plan C in place which mostly involves them adjusting their shot on the basis of what is bowled to them, and this is where I feel the current defence shot controls need to be 'expanded' a bit, to allow you to stop your shot and turn it into a defensive one (this is what the commentators refer to as 'checking the shot'), which is such a key element of the game of cricket. This is the plan B or C that the batsmen have incase the ball does not land where they expected it to.

After playing the last game, I had posted an idea on these forums (and also sent it as a PM to Ross, Mikey and MattW) that it would be great if we could stop the RS while moving it forward (using the legacy controls for playing a shot. The new controls are....well not for me), before it crosses the center point of the axis, the shot should be registered as a defense by the game (and maybe later it can be further enhanced to make the ball chip up in the air if we played the shot too early or stopped it marginally after the center point of the axis).

Leaving the ball in this game already caters to this as you can press the RS at the last second to leave the ball even if that wasn't your plan A (so you didn't premeditate it but adjusted on the basis of the ball bowled to you). However there is no such option to adjust your shot to a defensive one as for this you need to press a trigger on the controller and thus is not intuitive.

Maybe BigAnt can change the controls to pressing L3 for leaving the delivery and pressing R3 for defensive shot, if it's not possible to implement what I suggested earlier.

I hear you regarding pre-meditation and having 2-3 shots or go-to areas planned. I do the same while batting now but the approach works (at least for me) as long as the control remains RS as I can change/tweak the RS between the 2-3 areas I had planned. It's intuitive and works well. The problem is when you have to use shoulder buttons (i.e. L1/L2, R1/R2) as the only way you can use these buttons along with RS is for you to get additional time, i.e. increasing the ball marker display time which takes some of the fun out of batting. It's quite difficult to suddenly press shoulder buttons at the last moment and not something you can do instinctivelly the way you can change the direction of RS.

That's why I'm not a big fan of advance down the wkt shots or advance/sweep shots or aggressive ground shots (L2+R2) as you pretty much decide to play the shot before the ball is bowled, and that's why I barely use them. I can live without all those shots as they are not the basic/fundamental cricketing shots, and require some sort of pre-meditation to some extent in real life as well. But leg glance is a different story as it's a basic cricket shot just like running the ball down to 3rd man or flick off the pads which doesn't require any pre-meditation in actual cricket. Such a shot should not require an additional button such as R1 else you will end up shelving it more often than not, or worse end up fumbling with shoulder buttons and ending up playing a different shot altogether.

IMO it's better to add back foot leg glance animation based on height, i.e. anything below chest area off the backfoot results in a leg glance and anything chest high or higher results in pull/hook animation. No additional button/control scheme and results in what happens in real cricket most of the time. The only tweak to this logic would be for spinners where a red short delivery (long hop) off the back foot should result in a pull if played in front off square and glance if played behind square.

 

[Acid Burn]

Couldnt agree more with cricket_online.

Spot on !

 

[gkvarma18]

Playing the game on Ps4, I can't find shadows option. Where is it in settings menu to enable/disable.

 

[Kiko_97]

One request I have which was removed in Ashes from DBC 17, is the confidence meters for DRS reviews. You get the cutscene of the captain and keeper/batsmen talking and it would be nice to see if its worth a review, as i've wasted a few I was convinced by on my own only for an LBW to be just missing or I missed a catch drop short. @MattW @mikeymerren any reason why this was scrapped in Ashes?

 

[FaizanN]

 

[Rhone]

I hear you regarding pre-meditation and having 2-3 shots or go-to areas planned. I do the same while batting now but the approach works (at least for me) as long as the control remains RS as I can change/tweak the RS between the 2-3 areas I had planned. It's intuitive and works well. The problem is when you have to use shoulder buttons (i.e. L1/L2, R1/R2) as the only way you can use these buttons along with RS is for you to get additional time, i.e. increasing the ball marker display time which takes some of the fun out of batting. It's quite difficult to suddenly press shoulder buttons at the last moment and not something you can do instinctivelly the way you can change the direction of RS.

That's why I'm not a big fan of advance down the wkt shots or advance/sweep shots or aggressive ground shots (L2+R2) as you pretty much decide to play the shot before the ball is bowled, and that's why I barely use them. I can live without all those shots as they are not the basic/fundamental cricketing shots, and require some sort of pre-meditation to some extent in real life as well. But leg glance is a different story as it's a basic cricket shot just like running the ball down to 3rd man or flick off the pads which doesn't require any pre-meditation in actual cricket. Such a shot should not require an additional button such as R1 else you will end up shelving it more often than not, or worse end up fumbling with shoulder buttons and ending up playing a different shot altogether.

Your post makes sense and is well thought out, but is a subjective view of batting. Personally I use bumpers a lot...especially for sweeping spinners and nudging singles to spread fields with R1. Everyone plays differently.

At this stage batting is a huge plus in cricket 19 so rather than tinker with it heavily and risk annoying some one else who has a different view of batting I think mapping it to R1 makes a lot of sense. There is now an option to nudge the ball into the legside off the back foot that feels intuitive and logical, rather than a clothed pull shot with R1 depressed, which always looks a bit wrong to me.

There remain 3 ways to play the pull (regular, lofted and aggressive grounded) and now we may have an option to play a more conservative stroke into the legside off the backfoot. As a compromise it works for me.

 

[angad]

IMO it's better to add back foot leg glance animation based on height, i.e. anything below chest area off the backfoot results in a leg glance and anything chest high or higher results in pull/hook animation. No additional button/control scheme and results in what happens in real cricket most of the time. The only tweak to this logic would be for spinners where a red short delivery (long hop) off the back foot should result in a pull if played in front off square and glance if played behind square.

I get what you are saying regarding the leg glance. However, I do feel Leg Glance is always more like a precision shot while a pull is more of an attacking shot.

If the attacking ground shot button modifier (R2+L2) is still there then I would rather like to see the leg glance being assigned to the precision shot modifier button as well as to RS movement without any bumper/trigger pressed while a pull shot should be executed for the attacking ground shot (R2+L2) as well as the aerial shot buttons should be used (as aggressive shots are always predetermined).

Maybe take it a step ahead and make it dependent on the batsman's mentality. For aggressive and brute, let pull shot be executed for RS movement without modifier as well as R2+L2 as well as aerial modifier, while leg glance be limited to precision modifier. For defensive or balanced batsmen precision modifier and RS movement without any modifier executes the leg glance while for pull shot they need the aggressive modifiers.

 

[Wealey]

At this stage these things are all now personal preferences and how people would like the game to play...

I’d rather focus on key elements of cricket that may not be working well or need tweaking that would benefit everyone regardless of play style.

 

[angad]

At this stage these things are all now personal preferences and how people would like the game to play...

I’d rather focus on key elements of cricket that may not be working well or need tweaking that would benefit everyone regardless of play style.

Fair enough

 

[cricket_online]

Your post makes sense and is well thought out, but is a subjective view of batting. Personally I use bumpers a lot...especially for sweeping spinners and nudging singles to spread fields with R1. Everyone plays differently.

At this stage batting is a huge plus in cricket 19 so rather than tinker with it heavily and risk annoying some one else who has a different view of batting I think mapping it to R1 makes a lot of sense. There is now an option to nudge the ball into the legside off the back foot that feels intuitive and logical, rather than a clothed pull shot with R1 depressed, which always looks a bit wrong to me.

There remain 3 ways to play the pull (regular, lofted and aggressive grounded) and now we may have an option to play a more conservative stroke into the legside off the backfoot. As a compromise it works for me.

I agree that it's my view and opinion of the batting controls. Though I would love it if Big Ant do give a mapping option to you whether you want to map glance to R1 or Pull, similar to how they allow you to map the leave button button to either R3 or X. I consider leg glances a more fundamental shot and would map it to RS and the pull/hook shot to R1 whereas others might want to do the opposite.

The simple reason for me to do so would be that almost any batsman is able to play glances or tuck the ball to fine leg whereas very few batsmen are good players of hook/pull shot and not all batsmen have the shot in their repertoire. Thus it makes sense to play the glance shot easily via RS compared to a more complicated approach via R1, i.e. it should take more effort/complexity from a batting perspective to play a pull/hook compared to a glance/tuck down the leg side.

P.S. - Another reason to map pull/hook shot to R1 would be that it would reflect real cricket where you need better reflexes and reaction time to pull/hook deliveries compared to tucking/glancing the ball to the leg side. On similar lines if you want to be proficient playing hook/pull shots on the game, you would need to manage using R1 modifier with RS.

 

[cricket_online]

I get what you are saying regarding the leg glance. However, I do feel Leg Glance is always more like a precision shot while a pull is more of an attacking shot.

If the attacking ground shot button modifier (R2+L2) is still there then I would rather like to see the leg glance being assigned to the precision shot modifier button as well as to RS movement without any bumper/trigger pressed while a pull shot should be executed for the attacking ground shot (R2+L2) as well as the aerial shot buttons should be used (as aggressive shots are always predetermined).

Maybe take it a step ahead and make it dependent on the batsman's mentality. For aggressive and brute, let pull shot be executed for RS movement without modifier as well as R2+L2 as well as aerial modifier, while leg glance be limited to precision modifier. For defensive or balanced batsmen precision modifier and RS movement without any modifier executes the leg glance while for pull shot they need the aggressive modifiers.

I look at batting differently. As mentioned in my previous post, I look at shots as basic/fundamental ones and others which are more complicated to play and which are not played by all the batsmen. From that perspective, a leg glance or tuck down the leg side is similar to flicking the ball off the pads, i.e. it is a pretty basic shot similar to drives which is played by almost all the batsmen. On the other hand shots such as pulls/hooks, sweeps & revers sweeps or special shots are more complicated and not played by every batsman. In fact there are quite a few batsmen out there who can't play a half-decent pull/hook shot to save their lives whereas you will struggle to name a batsman who's proficient in pulling/hooking the ball but can't play a glance or tuck the ball down to fine leg.

Taking the above-mentioned view of batting, I would have/map all the base shots, i.e. which can be played by everyone and are comparatively easier to play, to the Right Stick. Other shots can be layered on top of it, i.e. Pull/Hook using R1 modifier, Sweep with L1, Special shots with say another modifier etc. This approach reflects the batting in real life and that's why I would love to have the ability to map leg glances to either R1 or Right Stick.

 

[blockerdave]

it seems the wides/byes issue, while reduced significantly, is still present on any pitch from soft and up and especially medium and hard.

it's a length issue, not line. essentially the AI is banging it in really short and the umpires are calling it wide. it does need looking at.

i think the game is generally excellent, but given improved AI was a trailed "feature", i think the AI when bowling has been a disappointment unfortunately.

 

[Rhone]

it seems the wides/byes issue, while reduced significantly, is still present on any pitch from soft and up and especially medium and hard.

it's a length issue, not line. essentially the AI is banging it in really short and the umpires are calling it wide. it does need looking at.

i think the game is generally excellent, but given improved AI was a trailed "feature", i think the AI when bowling has been a disappointment unfortunately.

How have you found AI in the longer formats? I cant fault T20 and list A/Odi, but I am seeing very low scores in first class/tests, lots of batting collapses and am yet to see a single drawn match.

This is with both games I have played in, and numerous games largely simulated in career mode. Shorter formats seem spot on, longer formats are 2 day wicket fests.

 

[WubbaLubbaDubDub]

In my second game in World Championship where somehow I am playing against Pakistan instead of Australia. Do not know what happened. Also once again on a medium good surface Paksitan are 23/0 in 7 overs.

I am playing with Medium Pro difficulty