Static Recompilation for Game Preservation

Blue Dragon launched on the Xbox 360 in 2006, carrying the weight of massive expectations in three discs, published as Microsoft’s dip into the Japanese RPG market. The title was conceived by industry legends: Final Fantasy creator Hironobu Sakaguchi, Dragon Ball character designer Akira Toriyama, and talented composer Nobuo Uematsu also famous for his works on various soundtracks of several Final Fantasy titles. Despite the critical acclaim and the game eventually added to Xbox backward compatibility, the game remained an Xbox 360 exclusive for nearly two decades at this point.

That was until re:Blue, the native PC project led by developer Tom Clay. Rather than relying on traditional emulation, re:Blue leverages static recompilation to basically convert the Xbox 360 binary directly into native x86-64 code. The result isn’t just accessibility through an emulation layer, but a fully native PC port with quality-of-life adjustments such as unlocked frame rates, adjustable resolution, and other in-game convenience upgrades, with several optimizations including reduced loading times, customizable controls, and low resource overhead suitable for handhelds like the Steam Deck. Now how did they manage to do all this recompilation? Said someone somewhere.
First, let’s discuss emulation vs recompilation. Emulation works by having the emulator program replicate an environment made to work like the original console architecture to unpack the game files, it reads and translates the instructions in the game files into instructions that are understood by the host device as we play. The issue here is the emulator program introduces CPU overhead as it encounters new codes and shaders to translate, causing stutters during gameplay. Static recompilation, in this case re:Blue, uses an analysis tool called ReXGlue which is rooted in Xenia, an emulator for Xbox 360. ReXGlue itself is inspired by a recompiler named XenonRecomp which was developed to recompile Sonic Unleashed, another game for the Xbox 360 which never got a rerelease in other platforms, so the community took it upon themselves. ReXGlue although used emulation as a foundation, it takes a different path of generating code ahead of time to be built and run natively. ReXGlue is a framework that translates the raw game instructions into C++ code, it is then compiled through CMake into a runnable exe file for Windows. The framework translates the native Xbox hardware method of rendering the game into modern pipelines such as DirectX 12 and Vulkan, as the game came in 3 discs, the files are merged into unified file system. Input system is also translated to receive user input from direct mouse and keyboard and modern controller API such as XInput.

Since re:Blue generates native source code, the developer team could inject the quality-of-life additions. Graphics setting customization was added, which allows sliders and graphic quality adjustments to exceed the original intended quality. Disc transition was seamlessly connected in sections where the 360 version requires changing the game discs to proceed. As of writing this, recompiler project still requires so much customization as games and software from this period still used specific internal tools different for each studio and only shared the same hardware architecture they run on. With the standardization of game engines such as Unreal and Unity, added with the fact these engines are also publicly available, it is speculated that recompilation development will only grow faster and more efficient going forward.
The re:Blue project has proven a change in software preservation where we are not tied down by emulator to replicate the old native hardware to run these obsolete games. Static recompilation transforms the obsolete software instructions into fully customizable source code ensuring accessibility in modern devices.
Technical marvel aside, this begs the question “is this legal?” Short answer: yes, but perhaps it is more nuanced than that. The publishing of re:Blue itself is completely legal, it is a freeware compatible with the Blue Dragon game, this tool falls under derivative work and is not commercialized using the Blue Dragon franchise. However, there is an argument that this tool enables illegal redistribution of the game as running the recompiler requires an original copy of the 360 game, how one got the game into their possession is not on the re:Blue developers. Ideally this hypothetical user actually purchased the game discs in the past, and it falls well under fair use for the customer to make a backup of the software for personal use. But what do you think?
Author
Eric Savero Hermawan S.Kom., M.Kom.
References
hedge-dev/XenonRecomp: A tool for recompiling Xbox 360 games to native executables. (n.d.). Retrieved September 3, 2026, from https://github.com/hedge-dev/XenonRecomp
rexglue/rexglue-sdk: Xbox 360 Recompilation Runtime and Toolkit. (n.d.). Retrieved September 3, 2026, from https://github.com/rexglue/rexglue-sdk
zolaware/reblue: Recompilation of Blue Dragon. (n.d.). Retrieved September 3, 2026, from https://github.com/zolaware/reblue#faq
Comments :