03-08-2024, 12:25 AM
You need a hook address (Breakpoint) that occurs whenever an item is used and a register (r14 thru r31) contains the Slot. Regarding the slot part, if you don't have such a register, that can be coded in "from scratch". Basically there are some functions embedded in the game's memory which you can use (call) to get info (i.e. Slot of Player).
Basically you will write a code that does this..
*If Item used was Bolt or Blooper, then Execute
*Load Slot of Player (not required if this is already contained in a non-volatile register)
*Check Slot of Player (check for numbers 0 thru 3)
*If Slot of Player is 0 thru 3, and Item used is Star, then Execute
The issue that will arise is what will constitute "Execute". I personally don't know how Dolphin's .log files work. Are the .log files able to determine a Conditional Write Breakpoint? Or can the .log files tell what what value is written when a Write Breakpoint occurs?
For example. the term Execute could mean "byte value of 1 written to 0x80001500"
By default code will write byte value of 0 to 0x80001500.
0x80001500 is an address from what is known as the Unused EVA Area. Link - https://mariokartwii.com/showthread.php?tid=1106
If the .log files can differentiate between the two diff byte values being written at that address, then you should be good to go. Have RGB lights do an action for byte 1, and a different action for byte 0.
Of course you can have more options. Like byte 0 = Nothing met. Byte 1 = Bolt. Byte 2 = Blooper. Byte 3 = Star from human Player.
Basically you will write a code that does this..
*If Item used was Bolt or Blooper, then Execute
*Load Slot of Player (not required if this is already contained in a non-volatile register)
*Check Slot of Player (check for numbers 0 thru 3)
*If Slot of Player is 0 thru 3, and Item used is Star, then Execute
The issue that will arise is what will constitute "Execute". I personally don't know how Dolphin's .log files work. Are the .log files able to determine a Conditional Write Breakpoint? Or can the .log files tell what what value is written when a Write Breakpoint occurs?
For example. the term Execute could mean "byte value of 1 written to 0x80001500"
By default code will write byte value of 0 to 0x80001500.
0x80001500 is an address from what is known as the Unused EVA Area. Link - https://mariokartwii.com/showthread.php?tid=1106
If the .log files can differentiate between the two diff byte values being written at that address, then you should be good to go. Have RGB lights do an action for byte 1, and a different action for byte 0.
Of course you can have more options. Like byte 0 = Nothing met. Byte 1 = Bolt. Byte 2 = Blooper. Byte 3 = Star from human Player.