dbc17 hacks: fearsome tweak v1.51

[Dutch]

Good work Franco!

 

[blockerdave]

I think one of @Wouldubeinta 's tools might be able to do that? Not sure though.

Yeah. I think none of them look at the academy files directly, but where he has posted the career save source code i think I may be be able to repurpose that to at least list the academy player variables and see where I get from there.

 

[normal10]

Hello Franco!

I got my new computer so started to use your tweak , but the thing is 1.51 is crashing for me and with batting modifier, i cant get it to work, i can only hit through covers and square leg, can you please upload the file with batting modifier where you used percentage bar instead of X Y Z, because this is the only option i use. Thank you

 

[francobaldo1]

@blockerdave my tools are usually something to search various things in memory or in the code (like the Lua console). Usually is Wouldubeinta the guy that
can help with archives and save files. However if you download the file "state_dump.txt" in the first post, you can see if it contains some variable name
that you might need, then i can try to give you some info.

@Spoobir i play on medium/medium

@normal10 i'll see if i find the backup, i recently formatted my pc

 

[blockerdave]

@blockerdave my tools are usually something to search various things in memory or in the code (like the Lua console). Usually is Wouldubeinta the guy that
can help with archives and save files. However if you download the file "state_dump.txt" in the first post, you can see if it contains some variable name
that you might need, then i can try to give you some info.

@Spoobir i play on medium/medium

@normal10 i'll see if i find the backup, i recently formatted my pc

thanks mate, i will check that out. i've been looking at @Wouldubeinta source code for the save editor, and I see he is able to access a lot of the player data, but he doesn't access appearance variables. i'm hoping i can use his code as a base to find the appearance variables...

i have an idea for something

 

[Dutch]

thanks mate, i will check that out. i've been looking at @Wouldubeinta source code for the save editor, and I see he is able to access a lot of the player data, but he doesn't access appearance variables. i'm hoping i can use his code as a base to find the appearance variables...

i have an idea for something

interesting , care to share?

 

[Spoobir]

@blockerdave my tools are usually something to search various things in memory or in the code (like the Lua console). Usually is Wouldubeinta the guy that
can help with archives and save files. However if you download the file "state_dump.txt" in the first post, you can see if it contains some variable name
that you might need, then i can try to give you some info.

@Spoobir i play on medium/medium

@normal10 i'll see if i find the backup, i recently formatted my pc

Hey Franco, I was really meaning the AI Difficulty. eg Pro/Veteran/Legendary.

I'm still thinking Legendary could be the best way to go.

 

[blockerdave]

interesting , care to share?

I'd like to see if what i'm planning is feasible based on my limited skills, before embarrassing myself by saying how i'll have a man on mars in 3 weeks

 

[francobaldo1]

uploaded AI shot selection v0.03 (link in the first post)

-now you can use two different settings for the batsmen
-improved randomizer script chance for the shots

USAGE:
launch the game and the mod and press START when you are in the game menu. Then wait 20-30 seconds.
Now go in a match, then press the "batsman 1" button to change the shots for the first batsman. After you change
your settings, press the button "set for this batsman".
There is a design problem of the interface, so only change the settings of the batsman at the crease. If you want to change
the settings for batsman 2, wait until he is on strike.

in the top left corner you will see the batsman info id.
B1 is the id of the first batsman.
B2 is the id of the second.
B3 is the id of the batsman at the crease.

It should work, but have some patience because of some design problem.

@Spoobir i play on pro, probably will change to veteran for the AIvsAI matches.

 

[Langeveldt]

uploaded AI shot selection v0.03 (link in the first post)

-now you can use two different settings for the batsmen
-improved randomizer script chance for the shots

USAGE:
launch the game and the mod and press START when you are in the game menu. Then wait 20-30 seconds.
Now go in a match, then press the "batsman 1" button to change the shots for the first batsman. After you change
your settings, press the button "set for this batsman".
There is a design problem of the interface, so only change the settings of the batsman at the crease. If you want to change
the settings for batsman 2, wait until he is on strike.

in the top left corner you will see the batsman info id.
B1 is the id of the first batsman.
B2 is the id of the second.
B3 is the id of the batsman at the crease.

It should work, but have some patience because of some design problem.

@Spoobir i play on pro, probably will change to veteran for the AIvsAI matches.

Amazing

 

[francobaldo1]

Amazing

almost, i will need to change something in the interface.

If someone has tried it, please note that there is also a problem with the settings not sticking sometimes. So,
when you change the settings for 1 batsman, it's better to set again also the other batsman (when he comes back
to the crease).

 

[Spoobir]

So after my attempts to get better test match scores proved fruitless (India were 100 odd for 7 when I gave up on that last match) I decided to go the other way and see what would happen if I played a t20 with blocking turned off and defensive shots scaled down a lot. I bowled as both teams, Wicket was hard/pristine, and here was the result:

You can see a pretty damn exciting game but not such a great batting effort by either side if I'm honest. Sri Lanka had a massive top order collapse and only managed to recover somewhat. Australia were the opposite where they were sitting pretty with 6 wickets left and about 15 runs needed and suddenly it seemed they became obsessed with trying to hit sixes and holing out in the deep over and over. I also had to turn off the helicopter shot because it screwed with the running, the batsman will hit the shot and then stand there like a pillock for about 2 seconds even if the non-striker sets off.

Overall I'm having to say that as great as this shot selection tool is (and I'll definitely do more testing in both tests and limited over) a huge problem is that the AI just fundamentally sucks at batting. Shot placement is terrible to the point where it seems like they don't even know where the fielders are, and even on a flat, true surface they struggle to time the ball to the boundary (this is much more of the case in test matches). They also don't seem to get any harder to dismiss at higher confidence, in fact reaching max confidence can often, in my experience, be a death sentence for the AI batsmen as they get out soon after.

So yes encouraging signs (even just getting rid of the bat-pad-smash in test matches is a huge leap) but still a long way to go...

 

[francobaldo1]

So after my attempts to get better test match scores proved fruitless (India were 100 odd for 7 when I gave up on that last match) I decided to go the other way and see what would happen if I played a t20 with blocking turned off and defensive shots scaled down a lot. I bowled as both teams, Wicket was hard/pristine, and here was the result:

You can see a pretty damn exciting game but not such a great batting effort by either side if I'm honest. Sri Lanka had a massive top order collapse and only managed to recover somewhat. Australia were the opposite where they were sitting pretty with 6 wickets left and about 15 runs needed and suddenly it seemed they became obsessed with trying to hit sixes and holing out in the deep over and over. I also had to turn off the helicopter shot because it screwed with the running, the batsman will hit the shot and then stand there like a pillock for about 2 seconds even if the non-striker sets off.

Overall I'm having to say that as great as this shot selection tool is (and I'll definitely do more testing in both tests and limited over) a huge problem is that the AI just fundamentally sucks at batting. Shot placement is terrible to the point where it seems like they don't even know where the fielders are, and even on a flat, true surface they struggle to time the ball to the boundary (this is much more of the case in test matches). They also don't seem to get any harder to dismiss at higher confidence, in fact reaching max confidence can often, in my experience, be a death sentence for the AI batsmen as they get out soon after.

So yes encouraging signs (even just getting rid of the bat-pad-smash in test matches is a huge leap) but still a long way to go...

thanks mate, will edit this post soon with the new update. There were a lot of small problems (for example, the randomizer) that probably didnt make the first version work.
Better to do the testing on the next update (will explain why later)

 

[francobaldo1]

uploaded AI shot selection v0.04 (link in the first post)

- fixed settings not sticking and other things.

USAGE:
launch the game and the mod and press START when you are in the game menu. Then wait 20-30 seconds.
Now go in a match, then press the "batsman 1" button to change the shots for the first batsman. After you change
your settings, press the button "set for this batsman". Now the batsman at the crease will be considered Batsman 1,
and will use these settings. When the second batsman is on strike, press "batsman 2" button and do the same. After that,
the batsmen will keep using their own settings, until you change them or someone is dismissed.

@Spoobir Ok, i think with this version i can start to test AI vs AI. Will post a video, maybe i can give some useful info.

As said in previous message, the randomizer was producing "ugly" results with the batsman chance to play a shot.
Now it should be a lot better. Also another thing to know, currently i am forcing the AI to not discard any shots in its
first analysis, doing something similar to a human player. For example, as a human you can decide to play irrational shots
like a sweep against the bouncer, while the AI automatically discard them. I thought it was a good idea, however it might
cause some "confusion" to the AI, sometimes selecting strange shots (like you said, the block advance). So, certainly
there will be more tweaks in the next updates, for example letting the AI to discard some of the irrational shots (block advance,
some back foot aggressive etc.).

There would be some more details to write, but i dont want to make the post too long. So, just want to say that this update
should be a more accurate test, if someone wants to try it.

 

[Dutch]

Fantastic Franco; hopefully this will give DBC 17 a real boost and we will have to see what might be required in Ashes Cricket!