Working on the hockey simulator pt.2

[djneo]

I'm very happy that One More Try is back after some very long, but well-deserved rest from a hockey game

He was kind enough and agreed to help me finish some the important stuff, that will at the end of the road hopefully make this project the best hockey simulator available (not only) on PC.


Hopefully, I can learn one or two things in the process again
We talked little and decided to make a new thread, to track the new stuff easily.

We'll start with the shot accuracy separately for NPCs and human-controlled players. This is very important to raise the overall difficulty of the game.


HUMAN





NPCs

[One More Try]

I think it might be f1, you can right click 80ab73e4 and follow the branch to a new code section then scroll down and see if it mentions f1. You can also choose symbols -> generate symbols from symbols databsase from the top menu. This will color code the different blocks.

Other than looking for f1, doing the cheat search thing I mentioned might find it.

Before, I mentioned it was weird that f0 was different between the two, but I forgot you have to hit Step once for it to run the Instruction that the game paused on. After hitting Step it will run the green line and will then load the correct f0, which would be the same for both players and npcs. It would be the f0 that your AR code creates, and you'd check it by right clicking a float box and choosing to display the floats and not the default hex.

[djneo]

this what I get by following the branch, I see "f1" mentioned several times (if I did that correctly).





EDIT: tried that second method, but no success, it keep freezing the game on my side

[One More Try]

By second method do you mean cheat search?

You did that correctly, but it's not what we want. I can check the cheat search and that area of code next.

[djneo]

By second method do you mean cheat search?

You did that correctly, but it's not what we want. I can check the cheat search and that area of code next.

Ya, I tried that search method with both master build and Ishiruka. Whenever I use it with the debugger it freezes. I tried it even without the debugger attached and then it doesn't freeze, but I had still no success


I'm getting lost in it little, to be honest, hah.

[One More Try]

Well you did pretty good already. Can you remind me what the controls are for shooting?

[djneo]

hah, you are very kind

Im expecting you are using the default gamepad setup, so let me double check real quick, so I don't misleading you.

[djneo]

so the easier way for you , I think it will be if you go to options> controller setup and switch to e "RETRO" configuration. This way you can easily shoot with buttons.

You have it nicely described there too:

SLAP SHOT= A
WRIST SHOT= Y

You should also probably turn off the "auto aiming" in controller settings. Thean you can manually aim your shot with LS (when shooting)

[One More Try]

Thanks. I think I found the area it's used. It's not clear yet though.

This is an interesting float. Maybe you already have notes on it. 80e563ac (remember to change 80 to 04 for AR). Default is 0.5 and it seems to check shot accuracy. Not sure if it's just for player or not. There's about 10 floats in that region. You never should mess with values of 43300000 and 80000000 as they are typically for basic programming logic and not real floats.

/edit I don't think I need more codes, but if I find something you already have notes on that's super helpful.
/edit 80e56450 , 80e56460 , 80f4c2f8

At the very least, I'm close to being able to make a code that says if shot accuracy = 0 then use the original float you have to lower accuracy more, otherwise don't change it. I'll work on it more later. Off for now.

[djneo]

awesome!

Do you want me to list all the codes that I have found through those 2 years that are somehow related to shooting? Not sure if it wouldn't only slow you down.


yes, that's what I have noticed as well. If the float is 176 or 08000000 it usually breaks something and is not usable or editable. These are also usually next to each other.

EDIT:

ya, if its E4, E5, E6, F4, F5, F6, F7, F8, F9, FA, FB then is I probably have all these combinations tested. But I definitely double check, there is always a chance that I could overlook something useful, given the enormous number of possible combination.

EDIT 2: I always try these combinations with float 0 and on another run with float 60