Open-source project
zolaware/reblue avatar
zolaware/reblue

re:Blue: Blue Dragon rebuilt as a native application

Recompilation of Blue Dragon

838 stars36 forksC++BSD-3-Clause

At a glance

What is it?
A static recompilation of the 2006 Xbox game that runs natively with 4K output, modern resolutions and a mod manager. It contains no game assets, so it needs disc images from your own copy of the game.
Who is it for?
re:Blue suits a player who owns the Xbox original and wants it running on a modern PC or handheld with a high frame rate and a mod loader, and who is comfortable with a tool that pulls files from their own discs. It does not suit anyone without a legitimate copy of the three discs, since the project contains no assets and the installer validates the images.
Can I use it commercially?
Yes. BSD-3-Clause is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 14 days ago.
What is it written in?
Mainly C++, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on October 22, 2026, and from our analysis. They are not legal advice.

Editorial analysis

Static recompilation, not emulation

re:Blue rebuilds Blue Dragon as a native application through static recompilation, which the README describes as translating the original code into something your machine runs directly rather than emulating a console around it. The distinction matters for what the project can offer. An emulator reproduces the hardware behaviour of the original Xbox, and improving on it means fighting that reproduction. A recompilation produces a native binary, so higher frame rates, modern resolutions and real mod support become ordinary development tasks rather than hardware emulation problems. The project is built on the ReXGlue SDK, which does the translation work, and the result is a C++ codebase with CMake presets, vcpkg manifests and a src tree. The README is explicit at the top that re:Blue is an unofficial project containing no assets from the original game, and that it is useless without a legal backup of the ISO images from the global release.

The installer wants your three discs

The setup wizard is the entry point and it is specific about what it needs. Blue Dragon shipped on three DVDs, and the wizard asks you to point it at a disc image of each one in turn, checking each before letting you continue. Once you choose an install location, the program copies itself there and restarts from that location, so the folder you extracted the zip into can be deleted. The wizard then copies the game files out of the discs and lets you pick a graphics quality preset. It only needs to run once, and if files go missing later, launching with --repair reopens it against the existing install and copies back only what is needed. DLC can also be installed from this installer or from the config menu inside the game. Nothing about this is a bypass, which is why the project can exist as open source without shipping anything from the original game.

The hardware floor is a 2015 era PC

The requirements are spelled out in detail, which is unusual and useful. The minimum calls for Windows 10 version 1909 or later, Ubuntu 24.04, Fedora 40 or SteamOS 3.6 or later, or macOS 13.3 Ventura or later, with an Intel Core i5-4460, an AMD Ryzen 3 1200 or an Apple M1, 8 GB of RAM, and a GTX 1050 Ti or RX 570 with DirectX 12 and Shader Model 6.0, Vulkan 1.2 or Metal. Fifteen gigabytes of storage are needed. The recommended tier raises that to Windows 11, SteamOS 3.6 or macOS 14 Sonoma, a Ryzen 5 5600X or Core i5-12400 or M2, 16 GB of RAM and an RTX 2060 or RX 5700, with 8 GB of VRAM suggested for 4K with MSAA. Platform support is narrower than the requirements list suggests: Windows is x86-64 only, Linux covers AMD64 and ARM64 including the Steam Deck and other handhelds, and macOS is ARM64, with the AMD64 and Vulkan variants available only in builds from source.

What recompilation buys, feature by feature

Everything in the feature list is new to re:Blue and configurable in game from the title screen or the camp menu. On the graphics side, resolutions up to 4K windowed or fullscreen on any monitor, aspect ratios from 4:3 through 21:9 and 32:9, four quality presets, MSAA up to 8x or SSAA up to 4x, anisotropic filtering, shadow quality and draw distance, depth of field adjustment, and unlocked frame rate with optional caps and VSync. The quality of life list is where the recompilation shows: saving from the camp menu anywhere rather than only at save points, a field of view adjustment from 45 to 120 degrees, a full area map with zoom and floor switching, optional markers for hidden items and chests with per-floor counts, an achievement list with eight new re:Blue achievements, separate centre, rear and subwoofer levels for 5.1 and 7.1 tuning, and full native keyboard and mouse support where menus take the mouse directly, with hover to move, click to confirm and the wheel to scroll.

Profiles, mods and the files on disk

Where everything lives is documented, and it is all under the install folder. Saves and settings go in the default profile folder, the configuration file is named reblue.toml and sits next to them, the game files copied from the discs go into a game folder and mods into a mods folder. Updates are not destructive: copying a newer build over an existing installation leaves the saves, settings and mods alone, and there is no need to point the wizard at the discs again. Multiple sets of saves are supported, with each profile its own folder holding that profile's saves, settings, achievements and DLC toggles, selected with the --profile argument, where anything other than default starts fresh. Mods are installed through the mod manager in the config menu, which takes either a mod folder or a zip file and puts the contents where they belong. Official DLC is supported, and there is a built-in mod manager rather than a separate tool.

Building from source with CMake and vcpkg

re:Blue builds with CMake and vcpkg against the ReXGlue SDK, and the README gives the two commands:

sh
cmake --preset win-amd64-release       # or linux-amd64-release
cmake --build --preset win-amd64-release

Presets cover win-amd64, win-vk, linux-amd64, linux-arm64, mac-amd64 and mac-arm64, each in Debug, Release and RelWithDebInfo. The win-amd64 preset produces both the DirectX 12 executable, reblue.exe, and the Vulkan one, reblue_vk.exe, while win-vk builds the Vulkan executable alone. As with running the game, building requires the files from your own copy of Blue Dragon. The repository root holds the usual pieces for a C++ project of this shape, with CMakeLists.txt, CMakePresets.json, a vcpkg.json manifest, a thirdparty directory, tools, generated assets and a reblue_manifest.toml. The licence is BSD-3-Clause, the repository is not archived with the last push on 2026-10-09, and the release feed mixes stable tags such as v1.3.1 from 2026-10-05 with nightly builds carrying a build counter.

Editorial conclusion

re:Blue suits a player who owns the Xbox original and wants it running on a modern PC or handheld with a high frame rate and a mod loader, and who is comfortable with a tool that pulls files from their own discs. It does not suit anyone without a legitimate copy of the three discs, since the project contains no assets and the installer validates the images. Before building or installing, check the platform list, because Vulkan on Windows and AMD64 on macOS only exist in source builds, and note that saving anywhere and the wider mod support both depend on the re:Blue layer rather than the original game.

Frequently asked questions

What is re:Blue?

It is a static recompilation of the Xbox game Blue Dragon, rebuilt as a native application using the ReXGlue SDK, so the original code runs directly on the machine rather than through an emulator.

What do I need to run re:Blue?

Disc images of all three retail Blue Dragon DVDs from your own copy of the game. The project contains no assets from the original, and the setup wizard checks each disc image as you point it at them.

Where does re:Blue store my saves and configuration?

Everything lives under the folder you installed to. Saves and settings are in the default profile folder, the configuration file is reblue.toml inside it, game files copied from the discs go in the game folder and mods in the mods folder.

Will updating re:Blue delete my save data?

No. The README says you can copy a newer build over your existing installation and your saves, settings and mods are left alone, with no need to reinstall or point the wizard at your discs again.

How do I install mods in re:Blue?

Use the mod manager in the config menu. It accepts a mod folder or a zip file and places the contents where the game expects them, and the project also supports the official DLC.

Official sources

  1. Issues
  2. License: BSD-3-Clause
  3. README
  4. Releases
  5. zolaware/reblue on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/zolaware-reblue.svg)](https://hysenlabs.com/projects/zolaware-reblue)

Was this useful?