Xbox 360
Blue Dragon
3 projects on the board for the Xbox 360 version: 3 recomp, 0 decomp.
- First released
- 2006
| Kind | Project | Claimed | Maintainer | Description (the repository's) | Toolchain | Status | Runs on | Version | Released | Last commit | Started | Licence | Language | Repository | ID |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| recomp | zolaware/reblue | no | Recompilation of Blue Dragon | Windows / Linux | nightly-v1.4.0-d0d3de0aa-s351bc94d | 2026-11-12 | 2026-10-05 | 2026-02-07 | BSD-3-Clause | C++ | public | blue-dragon-zolaware | |||
| recomp | dj5927/reblue-android | no | Unofficial Android port work for re:Blue (Blue Dragon), with optional Korean retail-data import tools. | Android | 2026-09-17 | 2026-09-17 | BSD-3-Clause | C++ | public | blue-dragon-dj5927 | |||||
| recomp | ivoefcarvalho-netizen/reblue_android | no | Android Port of Re:Blue | Android | 2026-09-05 | 2026-09-04 | Python | public | blue-dragon-ivoefcarvalho-netizen |
Rows come from the projects' public repositories, read every day; status and notes are the owner's word once they claim the row. Game facts are from Wikidata (CC0). The whole table · Add or correct a project
If one of these projects is yours
A .recomp.json to start from
Committed at the root of the repository, this file claims the row and writes it. The values below are what the board reads from the project today: correct what is wrong, choose the status, add what only you can say (notes, the help you want, who maintains it), and change the file when the status changes. Every field and the values it takes.
Save it as .recomp.json on the default branch. The board reads it every day; the
row then shows as claimed and says what the file says. Left without a status, the row shows none.