About 2.2.1. Why I should keep difficulty on max? What's the point?

Also, I think it's better to stop timer at the "Congratulations" screen (not the loading screen) because if it would at the finish line, people could lose the count of laps and accidentally stop the timer in the wrong place. So that kind of timing solves the problem. What's you think?

(upd)IMPORTANT NOTE I have tested this on other hardware and it doesn't work :( [Because of the second problem I mentioned below] Only "day", "time", "isLoading" adresses is working. This make me really upset cuz I have no clue how to fix this...

Ok so I made a simple autosplitter/load removal script for that category.

Download link: https://drive.google.com/file/d/1Ninmq6-T9oOOm8ewmMX00KEYsUkuiuVg

Example how to setup autosplitter script: https://www.speedrun.com/nfsu2/guide/wdbpc

What the autosplitter can do: -Automatically starts timer when starting new career as soon as the loading screen disappear. (based on time and date: 1 DAY 12:00 AM) -Splits when change club. Means the action take effect when you defeat a racer of the next club. -Splits when you enter the ROC. (based on time and date: 180 DAY 08:00 AM) -Splits when you win the ROC. Means the action take effect when you're gain controls at "Congratulations, you won the Race of Champions!" loading screen -Can show Load Removal Time (LRT)

Some issues I noticed: -The ROC enter split only splits if you skip the remaining days. This means if you enter the ROC at 180 day it won't skip. It also won't split if you have already entered the ROC once (don't split at 361 day, 542 day, etc). -I don't tested these splits on the other hardware. If static adresses (that i wrote in my asl script) changes on other hardware, that might be problem that I can't fix for now. I'm not an expert in reverse engineering. But this game has huge amount of base address offsets to access the value (cuz the game runs on JVM i guess(which can cause the issue)). -Also I notice that LRT at loading screen sometimes resumes a bit earlier (at 0.1 sec) than loading screen actually disappear. At the same time, it is sufficiently accurate at loading screens where you need to press enter to continue. +0.1 sec it's not a huge problem for now (I think), so I leave it as it is. Hopefully it will be fixed in the future.

If you have some questions or suggestions on how to improve my code or you disagree with the start/finish timing, leave a comment below.

In addition I leave there my splits and layout. In case you want it.

Splits: https://drive.google.com/file/d/1n2-U9VpOtm9g3Q7PunUPWjR5Np6-nJDu Layout: https://drive.google.com/file/d/1ObVeuk8XUgVcMTKbUUWDYoP-n-s6Ev9P