Okami HD. Now that Sys-netcheat is running... I want to find the timer for the race against Kai in Yospet Forest. This race is only available before the final dungeon. If you could do it earlier - like when you reach Ponc'tan - you could try it off and on while you are playing the game. I beat this on the Wii and I am a way better gamer now so why can I not beat it on the Switch? I am not going to lose though. I am going to hack this game - with the help of my friends.
Link to 30 sec video for flavor.
EDIT I made a mistake before this one is mine and 30 seconds.
I will try anything. Now I am trying u8 - u64 for the timer in seconds counting down. Next I will try it counting up. Suggestions welcome.
EDIT I start the race and press + to pause the timer. Most of my nested searches end up empty which seems reasonable. I find the following 2 occurrences weird :
So I start with time elapsed and let it increment (by leaving the + menu). Sometimes the list only loses a few addresses after 2 or 3 increments with nested searches or even 5 increments and nested searches. I expect stuff to be changing but a whole lot of counters being incremented by same amount as mine and after the same pauses?
EDIT. Okami takes up 9.4 gigabytes but this only explains the need for nested searches. This does not explain how after the 8th consecutive csearch I had 49 hits but the next csearch only reduced the number of hits to 29. /
EDIT
The other bit of weird is that the addresses occur in different ranges. I started out with 32xxxxxxxx and had this for several boots of the switch. Then I had 52xxxxxxxx, on another boot 67xxxxxxxx and so on. Is the game loading in different places or is Sys-netcheat looking somewhere random? If it matters I am using the physical copy released in Japan with universal subtitles.
EDIT. Does the code dynamically allocate stacks to confound hackers?
Example
https://i.imgtc.com/OHbrXw5.jpg
ONE request. Let me get a match on a timer in microseconds when I only know the value in seconds.
Thank you Paperjin, Jakibaki, 0x40, Colassal, Team Atlas, GBAtempers and GBAtemp. Finally got it to work by tweaking fire wall per 0x40, right clicking to run the client server as admin, and carefully reading Team Atlas' guide. I just set up my SD card from scratch. default build. extract. copy contents of sd folder to root of SDcard. Insert lines from sys-netcheat.ini to hekate_IPL.ini.
Before you start doing rcm mode payloads, have a charger for your joy-cons otherwise you have to dock them on the switch to charge them and remove the paper clip.
Monday 2019.NOV.4: I thought I had mastered launching. After failing to connect with Remote Client for hours and trying everything, I thought of checking the switch's IP. It exchanged with the PC. Du-uh.
* * * * * *
I have tried looking for mss and seconds in all sizes counting up and counting down and different initial values. I am going to repeat my searches because it is so easy to make mistakes. I have gotten some freezes when poking values but to be expected. Is it possible that the game counts tenths of a second or even micro seconds?
Micro seconds is traditional but I think I need a search which only matches up to seconds because microseconds could be anything. I am reading this c++ link
https://en.cppreference.com/w/cpp/chrono. Having read this it seems that the chrono library was launched in 2011 and therefore was not available when Okami was developed.
Perhaps a 32 bit variable (
2,147,483,647 max positive value) 0 0MS .nnn nnn ? Game starts with 4:59. Whether it does tenth of seconds or microseconds, I need a floor search or >= displayed value and less than displayed value minus one.