The Game Boy Reversing Emulator (RE) is a fork of the libRetro Same Boy emulator tailored for reverse engineering.
The main aim is to generate information that will be useful for the disassembling and exploration of your chosen game.
It does this by tracing and logging information about asm instructions, functions, memory addresses, DMAs etc as the user plays the game.
The emulator is built on the libRetro core of the SameBoy emulator, the reasons for this include:
The reversing functionality is contained in a library called LibRetroReversing which itself is based on LibRetro which encompasses common reverse engineering functionality that is shared among multiple Reversing Emulators.
This allows for new features and bug fixes to be easily ported across multiple games consoles. For example the Tool-Assisted-Superplay features are available across all libRetroReversing cores.
There is no better cross-platform UI kit than the web itself, it is highly likely you have a web browser on your system and so if your computer can browse Facebook then you can reverse games with our UI!
The emulator contains all the functionality of a standard Game Boy Color emulator but adds additional features for helping reverse engineer the game back into compatible source code.
One very important feature of the reversing emulator is the ability to record all the button presses made during a playthrough.
This allows you to play the game at full speed but then later playback the same button presses with full logging enabled.
This is an effective way to log a games functionality without having to play at unbearable framerates.
Since we have the functionality to record all the player input and replay it back on demand, this allows us to add Tool-Assisted-Superplay (TAS) features.
We provide a UI to edit the user input on a frame-by-frame basis, including functionality to preview a section of the game in a loop so you can optimize the input as much as possible.
Once a playthrough has been completed the user has the ability to playback the input states and create named save states for interesting parts of the game.
The name of the save state and the frame number it was saved at are used to give the reverser a hint as to where a function or chunk of memory was used.
For example if a save state was created and called “Start of Level 2” then any function that first gets called in Level 2 will be labelled as such.