If you are unlucky you might also have to do a logging session and hit the triggers to get them.Īnyway your job then would be to have the do rumble functions always active (either change all the rumble checks to return positive, or force something to set the 'is GB player?' set* flag) and either overwrite the inbuilt rumble command(s) with the EZFlash one (you might need to first figure out what it does) or redirect them to the location you stuck the EZFlash rumble command/'library' into instead. You might be able to find them on instruction levels (some branch to some known location or something that is found basically with control and f in a text disassembly) If you are lucky then the game will have its own rumble function that everything calls. Everything after that will reference the flag in some manner instead of playing with hardware (not that you can in this if it is boot only detection). Then there will be a flag placed somewhere in memory.

If I were to speculate then after the detection I don't know that it would be any easier than the 'find some activator, hook the game and fire the command you paste in' approach given in the guide ( ) other than the activators already being there.

Gamecube gba player borders