dbc hacks: fearsome tweak v2.90 +minigame v0.03

[Punk_Sk8r]

@wealey88 It happens quite often on 0.04, I think as gamers and edge fanatics we expect certain things to happen most if not all of the time (well I do anyway) but then I play more matches and more variations keep happening....on 0.04 I've had a good length delivery on the shorter side take the smallest of nicks off of a back foot defensive but it fell short of the keeper...and if you follow the ball trajectory from behind the bat it looks like it didn't take the edge at all....was amazing, also in general I've had a lot of forward defensive shots nicked...

I think the trick is bowl a good length but make it full, so just as it hits the green zone and a lot of the time I do it before the green zone and end up with yellow timing (can't remember what it says) and that makes the batsmen block a lot of shots because they're right on the stumps or outside off...

One more thing I also use the straight up seam delivery about 70-80% of the time, because that moves off a bit as it is and it seems to keep the batsmen in check more

 

[blockerdave]

i'm testing the new version, should solve some problems.

Some answers: version 1.01 is probably bugged on level High and Very High, so play only on Normal. Also on 1.01 it can be
more difficult to take wickets, i tried to balance the game. This will change in the next version.

If you have problems go back on v0.04, or also you can use both (not at the same time of course). On v0.04 you should play on High level (but it can be a little easy sometimes).

Also, when there is a "big change" in game, for example a new inning starts, i suggest to restart the hack.

i don't think it needs to become easier per se. but what seems to have been lost a little between v0.04 and v1.01 is some variation. for example, it's now much rarer to get a top-order dismissal via an edge, but there are still plenty of LBWs & bowleds. the edge dismissals of top-order seem to have been replaced by more bowleds, and more caught and bowleds. i think also again spinners are getting more edges than seamers as in v0.01 but i could be wrong. edges seem to be increased as you go down the order.

for me v0.04 was close to perfect. there were edges throughout the order, but varied and balanced: they were as likely to not carry or go into space as fly to gully.

My latest bowling innings was oddly the first one I've not taken any edge/catch dismissals (though i dropped the last man twice, a genuine bat/bad (was a beaut & would have been my first), and one in the slips. had 3 bowleds that were edged first (2 direct on to stumps 1 onto legs then stumps).

this is all observed on normal pressure / veteran, 4-ball over test or first class matches.

my last bowling innings was odd in general:

3 wickets for nothing at the beginning; 2 juicy partnerships, then a lower order collapse.

As an example of the v0.04/1.01 balance, as you can see above they scored 183 in 93 overs. v0.04 - on a better pitch, admittedly - they scored 310 in 112 overs.

 

[Punk_Sk8r]

@blockerdave In your opinion what would you say the issue with 0.04 was then? As you said it is very good and the edges are just awesome especially early on in the innings. I can't quite put my finger on what to improve, I was originally going to say improve the rate which batsmen score at but then it is cricket and sometimes teams do fail because I've had other matches where I've been hammered.

A recent match I had ENG vs IND, I simulated batting so I could bowl and made 247 in 50 overs. Anyway I got some early edges that went wide, one really thick edge too and one edge which was caught however the Indian batsmen made a really strong start, just take a look at this scorecard...so now I'm really confused as to what should be improved, I think if they could time the ball better that'd still be the main thing because with the seamers it can become easy to tie them down sometimes, but again contradicting myself because I tried everything here to get them out, had men out in the deep and all sorts but just couldn't win...

Oh and that catch by stokes bowled woakes lol...that was a square of the wicket.

 

[blockerdave]

@blockerdave In your opinion what would you say the issue with 0.04 was then? As you said it is very good and the edges are just awesome especially early on in the innings. I can't quite put my finger on what to improve, I was originally going to say improve the rate which batsmen score at but then it is cricket and sometimes teams do fail because I've had other matches where I've been hammered.

A recent match I had ENG vs IND, I simulated batting so I could bowl and made 247 in 50 overs. Anyway I got some early edges that went wide, one really thick edge too and one edge which was caught however the Indian batsmen made a really strong start, just take a look at this scorecard...so now I'm really confused as to what should be improved, I think if they could time the ball better that'd still be the main thing because with the seamers it can become easy to tie them down sometimes, but again contradicting myself because I tried everything here to get them out, had men out in the deep and all sorts but just couldn't win...

Oh and that catch by stokes bowled woakes lol...that was a square of the wicket.

to be honest i don't think there was an issue on v0.04. not for me anyway. the 310 all out was the most satisfying bowling innings i've had with or without the hack. that being said, it was a cracker of a pitch, and if i was always dismissing them for sub-350 on pitches like that you'd say the balance was off.

it's an impossible job, really, because in reality there should be times where they rack up 550/6 declared, but would we find that fun? i don't know...

 

[Punk_Sk8r]

to be honest i don't think there was an issue on v0.04. not for me anyway. the 310 all out was the most satisfying bowling innings i've had with or without the hack. that being said, it was a cracker of a pitch, and if i was always dismissing them for sub-350 on pitches like that you'd say the balance was off.

it's an impossible job, really, because in reality there should be times where they rack up 550/6 declared, but would we find that fun? i don't know...

Mmm tbh I quite like it when the CPU posts a huge total, makes it feel real and puts the pressure on you to bat well and I think it does vary as you said, I'm now on my 3rd match between ENG vs IND and the 2nd match they hit me about like no tomorrow and now they're 78-6 after 20 overs, a lot of good edges to the keeper, one beautiful bowled and some outfield catches...it'll be interesting to see what total they end up with here, I also wonder if bumping it up to legend will have an impact on their batting.

 

[steve121157]

I'm fascinated by this tweak so I started a new career yet again as Yorkshire and I'm enjoying a good first match at Durham.
I decided to leave the fearsome tweak on all the way through this time with some interesting results.
Batted first and made 345 in 103 overs with my player Liam Plunkett out LBW for a reasonable 36.
Durham started off badly and were 13 for 3 early on finishing on 143 all out in 42 overs.
Following on they have made a game of it and are currently 179 for 4 (23 behind) after 50 overs on day 3 at 11:34 am.

I've noticed a lot of maidens being bowled, but mostly by Durham (Collingwood 6, Onions 6, Rushworth 4 & Stokes 3)

Durham might get about 290-300 maybe a few more but looks like a comfortable win for Yorkshire.

Veteran level and normal level for the tweak.

UPDATE

Durham made 321 and Yorkshire were set 120 to win.
They made hard work of it but finished on 122 for 5.

 

[grkrama]

to be honest i don't think there was an issue on v0.04. not for me anyway. the 310 all out was the most satisfying bowling innings i've had with or without the hack. that being said, it was a cracker of a pitch, and if i was always dismissing them for sub-350 on pitches like that you'd say the balance was off.

it's an impossible job, really, because in reality there should be times where they rack up 550/6 declared, but would we find that fun? i don't know...

same here, have been satisfied with v.04 that i havnt tried the new ones. I still havnt properly played tests with it, but in limited overs on high pressure, legend , there are certainly matches when the AI goes after you especially if a partnership goes on flat pitches! I also think the bowler counts, say a spinner is more likely to trouble on flat or dusty oens than pacer, were as on grassy cracked ones, seamers own.

maybe placebo...but so far works out!

 

[Wealey]

to be honest i don't think there was an issue on v0.04. not for me anyway. the 310 all out was the most satisfying bowling innings i've had with or without the hack. that being said, it was a cracker of a pitch, and if i was always dismissing them for sub-350 on pitches like that you'd say the balance was off.

it's an impossible job, really, because in reality there should be times where they rack up 550/6 declared, but would we find that fun? i don't know...

I think this is a very key point. Cricket is one of those sports that very hard to achieve the ideal result.

As you said one day you could skittle a team out for 150 the next they could rack up 550.

However us as gamers would sit there and be like, what no edges? 550? Nah hack ain't working somethings up. When really it's the kind of variation you would see In the real game.

You almost need to complete a full 5 tests match series on a variation of wickets to fully appreciated what you are getting with the back activated.

 

[Gamer Pradosh]

I think this is a very key point. Cricket is one of those sports that very hard to achieve the ideal result.

As you said one day you could skittle a team out for 150 the next they could rack up 550.

However us as gamers would sit there and be like, what no edges? 550? Nah hack ain't working somethings up. When really it's the kind of variation you would see In the real game.

You almost need to complete a full 5 tests match series on a variation of wickets to fully appreciated what you are getting with the back activated.

Yeah for such a thing when the team is racking runs up the commentary should come into play [for DBC 17] where they should mention that the pitch is dead and nothing's happening and also suggest something like they should be gambling by bowling some part timer or set an unusual field to make the batsman play some shots, otherwise the runs would keep coming...Even tell what would work on that pitch like the new ball gets a bit of movement then after that its nothing etc.. Mainly telling that the pitch has nothing in it with some graphical representation say the movement they got in previous match in that stadium vs today [just a graphical representation,need not be actual data] just to make the player feel that he needs to bowl with patience and try something different to get the result...

 

[Wealey]

Mmm tbh I quite like it when the CPU posts a huge total, makes it feel real and puts the pressure on you to bat well and I think it does vary as you said, I'm now on my 3rd match between ENG vs IND and the 2nd match they hit me about like no tomorrow and now they're 78-6 after 20 overs, a lot of good edges to the keeper, one beautiful bowled and some outfield catches...it'll be interesting to see what total they end up with here, I also wonder if bumping it up to legend will have an impact on their batting.

This is the variation that I we need! Makes a series unpredictable!

 

[blockerdave]

You almost need to complete a full 5 tests match series on a variation of wickets to fully appreciated what you are getting with the back activated.

I'm actually playing a whole tour right now so should have a good sample by the end.

I played 2 tour matches, 1 test and had AI 22/2 in second test before starting the hack. Since then I've completed that test, played 1 more whole test, a whole tour match and 1 bowling innings of another test. I've got the rest of this test plus one more test to play.

Then I have an ODI warm up and ODI tri series, t20 warm up and 3 match t20 series to complete the tour.

By the end of all that I should have a good sample of the hack under various conditions.

 

[Punk_Sk8r]

@wealey88 @blockerdave Yeah totally agree and that's exactly what I said too wealey, in real cricket you do see a score like 76-8....and it's usually asian teams who crumble like this, so that adds to it even more. As you've both said more testing is needed, my plan was to test 3 innings of me bowling on veteran, 0.04 - normal pressure. But I think more is needed, so I might play 2 more innings

So far the scores India have posted against me have been...

228-10 - Had a few good partnerships to steady the ship
251-6 - They were chasing here and absolutely destroyed me, this match felt very real because a huge partnership build and then I got 2 quick wickets to put the pressure on but it wasn't enough
78-6 - This is currently the score after 20 overs in the 3rd ODI, got some great nicks one from a lovely forward defensive which I've recorded and 2 outfield catches of them slogging

I really need to patch my game with the correct licences etc, I saw some 2015 mega patch for world cup but it seems to have disappeared from the internet.

 

[blockerdave]

I really need to patch my game with the correct licences etc, I saw some 2015 mega patch for world cup but it seems to have disappeared from the internet.

fairly sure everything you'd want will be within this download section and the academy.

 

[Punk_Sk8r]

fairly sure everything you'd want will be within this download section and the academy.

Yeah there are things here and there but the download section just seems really messy for this game, I'm learning how to make mods (mainly kits) and hopefully I can go from there....

also just a heads up on that match that was 78-6 after 20, well here's the full scorecard below, didn't think this would be happening...I almost feel gutted that I couldn't get them out for under 200 haha, last wicket was a nice nick off of a forward defensive shot to Ali at 2nd slip!

 

[Wealey]

Can I just clarify what teams people are using?

Ruduced skills ! Or just any old!?