Your game.
A new way to understand it.
Turn your own lawful MKDS cartridge dump into a native game and a Rust source workspace. Explore how it works and how the research is checked. No ROM or game download is supplied.
Choose your path
Build and change your copy
Graphical launcher, source navigation, dictionary, textures, native switches and verification.
RESEARCHERSStudy the method
Instruction lifting, IR, raised code, flag liveness, type inference and hardware replacement.
GENERAL READERSFollow the story
What recompilation means, why MKDSrust exists, the block-by-block journey and what comes next.
Current progress
All 12,736 functions have raised output. Opt-in native services now include CPU-less ARM7 sound execution; the latest budget-free acceptance measurement uses about 28% less CPU per frame. Native defaults, save files, graphics fixes and readability polish remain work in progress.
These are dated measurements, not universal compatibility claims. Read current status and limits.
Evidence you can inspect
The exact reference race is bit-identical after source transformations. Native race comparisons require pinned randomness, documented masks and loading offsets; menus and battle retain differences.
How verification works · Native hardware research · TimelineHistorical mapping inventory, distinct from the 12,736-function whole-program raised-code count. Classifications describe annotation evidence, not game completion or universal verification. Search 11,175 records.