I am investigating more about this game by examining the memory so starting a thread here to document my finds and create a discussion to help us learn more about how this game works(and by extension how to exploit when it doesn't). Addresses and Mechanics added to this list will be labelled by what we think they are and I will update this OP when additional ones are posted in discussion. Speculation is invited but please label it clearly if possible; posting in forum so finds are documented and anyone can weigh in.

List of Addresses:

Course Segment Counter = 0xDFF3A124

Lap Counter? = 0xDFF547C0

List of Relevant Mechanics:

Off Course Reset - This mechanic places the player back on the course after you jump over the barriers around the course

Crash Reset - This mechanic places the character back on the course after they have crashed

CHECK Value - This Value is a maximum value found on every course 4294967295/FFFFFFFF

D85B0C0E accesses DFF547C2 to write lap

D85B0C0E writes to DFF547C0(Lap Counter)

D8324237 accesses DFF3A124(Lap Segment)

D8324F9E accesses DFF3A124(Lap Segment)

D863FD93 accesses DFF3A124(Lap Segment)

D8324237 continually accessed while game is unpaused

D8324F9E continually accessed while the game is unpaused stops accessing while occupying the Lap Segment behind the finish line

D80CBFDE accesses 24A1F3DF(Lap Counter) after Start of Each Race or Restart Race 4 times

D8238CDE accesses 24A1F3DF(Lap Counter) after Start of Each Race or Restart Race Once

DFF60F74 Increments value with the timer onscreen DFF60F74(Timer Counter)

D84FFD6F accesses DFF60F74(Timer Counter) right before each lap completes

List of Known Behaviors:

• Course Segment Counter advances while in Off Course area as well as on the course
• Off Course Reset places you back on the course in the segment that was last driven on(speculation)

There are some comments in the code that have been highlighted here on the cutting room floor https://tcrf.net/Excitebike_64