VERSUS
Budokai
GameCube · NTSC-U
The one that started the series on GameCube. One-on-one fights, ported to native code.
Ubuntu 26.04 & Android dev builds
Your wish has been granted
Alpha 1.3 is out
New in 1.3: London and Amsterdam servers join the US ones: five regions in all.
From 1.2: Quick Match in Budokai and Budokai 2 jumps straight to character select with every fighter unlocked. Windows is still Vulkan only.
See the downloadsSite visits
GameCube DBZ trilogy · native ports
The Nimbus Project
Skip the emulator. Ride the Nimbus.
1 BUDOKAI DISC
YOUR OWN NTSC-U DISC
- DISCS 3/3
- TEXTURES 3/3
- MOVIES 1/1
Budokai, Budokai 2 and Sagas, each running as its own native core. A hybrid core between recompilation and decompilation, not emulation. All three on Linux (Ubuntu 26.04 for now), Windows and Android. One launcher. HD rendering. Online netplay.
Click a ball to select · Continue to goTap a ball to select · Continue to go · scroll to ride the Nimbus
Native. Not emulated.
Nimbus runs on a hybrid core that sits between recompilation and decompilation. Each game gets its own native core, and those cores run on a shared Nimbus host and renderer. There's no Dolphin, no emulator and no interpreter emulating the hardware. Every game can be played in Original or Remastered mode, and crossplay has been tested across Linux, Windows and Android. Detailed architecture notes are coming to the site later.
What you get is a standalone game that starts like any other app, renders through a modern GPU pipeline and is built to outrun emulation, with headroom left over for higher resolutions and HD assets.
- One build for the whole trilogy, one launcher
- Your own legally obtained disc, nothing else
- Keyboard, mouse and gamepad out of the box
Three games. One trilogy.
All three GameCube releases (NTSC-U), each ported on its own and all started from the same launcher.
VERSUS
Budokai 2
GameCube · NTSC-U
The bigger sequel, with head-to-head netplay. Crossplay between Linux, Windows and Android is in testing.
Ubuntu 26.04 & Android dev builds
2P CO-OP
Sagas
GameCube · NTSC-U
The action-adventure entry, with two-player co-op, local or online.
Ubuntu 26.04 & Android dev builds
The originals
The North American GameCube releases these ports are built from. Flip a case to see its back, or open it to see the full cover.
One launcher. Every mode.
One window for the whole trilogy. Pick a game, see its status at a glance (ready, no disc, no core) and choose how to play. Keyboard, mouse or gamepad all work, with a CRT filter on top.
- PLAYStart the game, solo.
- HOST GAMEGet a join code to share with a friend.
- JOIN GAMEPaste the code and you're in. Recent hosts are remembered.
- LOCAL 2 PLAYERSTwo pads, one screen.
Online netplay
Play over your LAN, or over the internet through Nimbus relays with a short join code. After each session the launcher shows how it went: the other player, ping and input delay. Sagas plays as two-player co-op; Budokai and Budokai 2 play head-to-head.
Under the hood
The same engine room powers every game in the trilogy.
Nimbus GX Renderer
A modern graphics backend built on Aurora, WebGPU (Dawn) and SDL3. It recreates the GameCube's graphics on today's GPUs.
Nimbus Host
The shared host layer for windowing, input, audio, saves and netplay, so each port can stick to the game itself.
Nimbus Core
The game code in each core: the original game logic, carried over into a native core.
Nimbus Port Kit
The tooling that turns a disc into a standalone build, reused across all three games.
HD everything
Higher internal resolutions, AI-upscaled texture packs for all three games and HD movies for Sagas. Grab them in Downloads.
Built to outrun emulation
No emulator overhead means more headroom. In Sagas benchmarks on the dev laptop, the native build ran faster than Dolphin at both 1× and 5× internal resolution.
Platforms
Where things stand right now. Alpha 1.3 is out for all three platforms (2026-11-02); it's an early alpha, and work continues.
Linux
Alpha 1.3The main development platform. All three games are in one trilogy build. Ubuntu 26.04 (64-bit x86) is the supported distro for now; other distros aren't supported yet.
Android
Alpha 1.3All three games run on Android 13+, in one arm64 app. Sagas runs comfortably above full speed on handhelds such as the Retroid Pocket 5 and the RG Slide.
Windows
Alpha 1.3All three games run natively on Windows, in one portable x64 folder with the same launcher, host and renderer as Linux and Android. Tested on Windows 11 x64; it needs an AVX2-class (x86-64-v3) CPU and a Vulkan-capable GPU (this release is Vulkan only). Sagas two-player co-op isn't fully covered on Windows yet.
Benchmarks
Early dev resultsEarly numbers from current Android dev builds, measured on real hardware and shown with the core they were measured on, next to Dolphin on the same device. Results vary by device and game: on the RG Slide, Nimbus is behind Dolphin in all three games, while on the Pixel 9a it ties in Sagas, is slightly ahead in Budokai and is behind in Budokai 2. Closing the gaps is ongoing work. Linux and Windows results are coming.
Loading the benchmark readout…
How we test: Method TBD. We'll publish the test scenes, settings and capture method alongside the first results.
Submit your results — coming soonOnline. Across platforms.
Nimbus has its own netplay, written for this project with no third-party netcode. Here's how players find each other, how a match stays in sync and what the servers do.
Crossplay
Linux , Android and Windows
An Ubuntu PC, a Windows PC and an Android handheld can play the same match. Both run the same game code in lockstep, so neither side is the "real" one. Our Budokai 2 test pair, an Ubuntu PC and a Retroid Pocket 5, played 14,000 fields (about 4 minutes) over LAN with no desyncs, then the same length over the internet relay. That run included a pause, the app going to the background, a Wi-Fi drop and a deliberate desync, and both sides finished with identical game memory. On Windows, a Windows PC and the same Retroid Pocket 5 matched our reference checkpoints over the relay in all three games. In Budokai 2 they also got through changing inputs, a background and resume, and recovery from a forced desync in both directions.
- Linux ⇄ AndroidTested: Budokai 2Tested: Sagas co-opNot yet: Budokai
- Windows ⇄ AndroidTested: all three
- Windows ⇄ LinuxIn testing: Budokai 2
Crossplay is enabled game by game, only for build pairs we've checked play identically. Mismatched builds refuse to connect instead of drifting apart. Windows and Linux have played Budokai 2 over LAN; online matchmaking between them is still being verified. Sagas co-op isn't fully covered on Windows yet.
How you find each other
Join code
TestedHost online and you get a code like K7Q2M-R8XWD-3HNPA-YT6QE (20 characters, no look-alike letters). Your friend types it in and you meet at a Nimbus relay. The code also holds the secret that encrypts your match and says which relay to use, and its last character catches typos.
LAN / direct
TestedHost on your home network and the launcher shows a line like address:27960/token. The other player enters it and connects straight to you over UDP. There's no automatic discovery yet, but the launcher remembers recent hosts.
Quick match & public games
In testing on AndroidThe matchmaking lobby pairs you with someone playing the same game and build, or lists public games anyone can join. The player who waited longer hosts, and both sides report the result. It's in the Android app now and still being tested. It's coming to the Linux and Windows launchers too, so every platform will get it.
Tournaments
In developmentSingle-elimination brackets for 4 to 32 players, best of 1, 3 or 5, with byes, forfeits and organizer rulings. The lobby server already handles them, and they're coming to every platform: Linux, Windows and Android. No launcher has the screens yet.
How a match stays in sync
Lockstep, not rollback
Both devices run the full game and trade controller input every video field (about 60 times a second). Inputs are delayed by a few fields so the other player's input arrives in time. The delay is set from your ping (1 to 12 fields) and adjusts during play. Every packet repeats the last 16 fields, so a lost packet costs nothing.
Desync check & recovery
Every 60 fields both sides compare a fingerprint of the game's memory. If they ever differ, the host sends its save state, both load it and play continues, instead of quietly carrying on out of sync. Forced desyncs recover in our tests, including through the relay.
Same game, same save
Before a match starts the two sides compare the game, build and settings, and refuse to connect if they don't match. The joiner plays on a copy of the host's memory card, so unlocks match, and their own card isn't touched.
Co-op & versus
Sagas is two-player co-op: player 2 presses START to drop in. Budokai and Budokai 2 are head-to-head. A session is two devices, which between them can bring up to 4 controllers. That's supported in the code, but so far we've only tested one controller per device. You can see ping and input delay in-game, and on-screen symbols show when the other player has paused, the game is waiting, the connection has dropped or a resync is running.
The servers
Player 1hosts, gets a codeNimbus relayforwards sealed packetssees no game data
Player 2joins with the codeLobbyquick match, public games, results. It hands over a join code but never carries game traffic.
Relays
TestedSmall UDP services written for Nimbus, with relays in West US, Central US, East US, London and Amsterdam. You can pick one or leave it on "Auto". The host registers with every relay and the joiner meets it at the one with the lowest combined ping. Session requests have to be signed with the Nimbus relay key, and every address is rate-limited.
Encryption
Internet matches are end-to-end encrypted (XChaCha20-Poly1305) with keys derived from the join code, so a relay only ever handles ciphertext. Lobby requests are encrypted and signed. LAN/direct sessions are unencrypted; use a join code for encrypted play.
Your identity
There are no accounts or passwords. The lobby knows you by a name plus a short tag (like PICCOLO#3031), backed by a key file created on your device. Keep that file private.
Self-hosting
Not yetThe game reads its relay list from a settings file, but the relay and lobby programs aren't published, so you can't run your own servers yet. There's also no spectator mode or chat right now.
| Game | Linux ⇄ Linux, internet | Linux ⇄ Linux, LAN/direct | Linux ⇄ Android | Windows ⇄ Android | Windows ⇄ Linux |
|---|---|---|---|---|---|
| Budokai | Tested | Supported | Not yet | Tested, relay | Not yet |
| Budokai 2 | Tested | Tested | Tested (photo) | Tested, relay, incl. resume & recovery | In testing (LAN played) |
| Sagas | Tested, incl. co-op | Tested | Tested, co-op (photo) | Tested, relay (co-op not fully) | Not yet |
Tested: two devices finished a session with identical game memory. Supported: the same code path, not yet run as its own test. The Linux ↔ Android internet test used the relay only. Windows ↔ Android "Tested" means both sides matched our reference checkpoints over the relay. In testing: played, but not yet verified end to end. Direct paths have so far been tested between Linux PCs, and between Windows and Linux on LAN.
Downloads
Every file has a SHA-256 checksum so you can check your download.
Main distro
Launcher + all stable modules, bundled in one. Alpha 1.3 is out for Linux, Android and Windows (released 2026-11-02). The three games' runtime components are bundled; original disc images are not included, so you need your own NTSC-U discs. Third-party license notices ship inside every download.
Bundles: launcher · host shared-20261102 · renderer v5zz-shared · cores for all three games
Loading…
Also on GitHub Releases. Looking for Alpha 1.2, 1.1 or 1.0? They're under Other versions on each card and in Previous releases.
What's new in Alpha 1.3
Released 2026-11-02 for Linux, Windows and Android. Android installs over the existing app and keeps your links, settings and saves.
New servers in Europe
New- London and Amsterdam join West US, Central US and East US: the server menu now has five regions on Linux, Windows and Android.
- Auto picks the region with the lowest latency, and you can still choose one yourself.
- The menu still works with keyboard, gamepad and touch. See the network map.
Smooth upgrade
Automatic- If you use the stock server list, it upgrades automatically.
- Custom server lists, settings, saves and linked files are kept.
- Install the full 1.3 download to get the new server menu. The standalone modules are unchanged.
How matches connect
Unchanged- The East US lobby still handles Quick Match and public rooms. Private join codes skip the lobby.
- Your game runs on your own device. Players try a direct connection and use a relay when needed.
- Auto still works with players on earlier versions. To pin a match to London or Amsterdam, both players need Alpha 1.3.
Previous releases
Alpha 1.2 · 2026-11-02
Quick Match in Budokai and Budokai 2 starts at character select with every fighter unlocked.
Quick Match, straight to the fight
New- In Budokai and Budokai 2, Quick Match now drops you right at the 1P-vs-2P character select with every fighter unlocked.
- There's no separate Quick Versus menu item: it's simply how Quick Match starts now.
- Local Two Players uses the same unlocked setup.
- Tournament, public rooms and manual host/join start the same way as before. Sagas is unchanged.
Your saves stay yours
New- Each quick start uses its own separate session memory card, so your regular saves aren't touched.
- Normal Play keeps using your regular card.
- The two unlocked memory-card seeds and the quick-start states are intentionally bundled in the downloads. No disc images, other personal saves, source files or signing keys are included.
Friends on older versions
Compatible- Mixed Alpha 1.0, 1.1 and 1.2 matchmaking still works. Whoever hosts decides how the match starts: a 1.2 host starts at the unlocked character select, and an older host uses the original start.
- No need to split players up by version. The usual core compatibility requirements still apply.
- Install the full 1.2 download to get these launcher changes. Updating only the host module doesn't add them to an older launcher.
Alpha 1.1 · 2026-11-02
Android touch polish, the Sagas outline fix and Components versions & rollback.
Android touch controls
New- Cleaner, translucent GameCube-style buttons with clearer labels and visible feedback when you press them.
- Shoulder buttons sit below the performance overlay, START is a wider pill, and the D-pad has arrows.
- Buttons respond to their drawn shapes, with a little thumb margin. New touch-opacity slider (30–90%) and a small stick dead zone.
- The four-star Dragon Ball menu button has an amber finish, and dragging it no longer opens the menu by accident.
- Touch controls hide automatically when a gamepad is connected (the menu ball stays). You can still show or hide them yourself.
Sagas outlines
Fixed- Black character outlines no longer disappear during projectile and explosion effects, including in co-op.
Components: versions & rollback
New- New Components > Versions / rollback screen on Linux, Windows and Android.
- See whether each part is bundled or replaced, its signed version label where available, and its exact fingerprint.
- Your previous selection is kept. Rollback brings it back and Restore bundled returns to the stock parts; both apply the next time you launch a game and don't touch saves or linked files.
- A damaged previous file is rejected without changing what's active.
- Alpha 1.2 · 2026-11-02 · full notes: RELEASE-NOTES.txt. Downloads and SHA-256 checksums stay available under Other versions on each Main distro card.
- Alpha 1.1 · 2026-11-02 · full notes: RELEASE-NOTES.txt. Downloads and SHA-256 checksums stay available under Other versions on each Main distro card.
- Alpha 1.0 · 2026-11-01 · the first public release for Linux, Windows and Android. Its downloads and checksums are also under Other versions.
Modules
The host, renderer and the three game cores are also available on their own, signed, for each platform. You don't need them to play: the main distro already bundles everything and automatically selects its bundled cores. Swap a part from the launcher's Components menu without reinstalling. The launcher itself only updates through the main distro.
Module set 1.2 (unchanged in 1.3): host shared-20261102 · renderer v5zz-shared · three game cores per platform · catalog.json
Loading the module list…
Installing a module:
- Android: select the
.nimbus-componentfile directly in Components. - Linux and Windows: extract the ZIP and keep the binary next to its
.ticketfile, then select it in Components. - Changes apply the next time you launch a game. Nimbus doesn't download or update modules automatically, and parts can't be swapped mid-game.
- Rollback (Components > Versions / rollback) restores your previous selection, and Restore bundled goes back to the stock parts. It isn't an automatic recovery system.
- Use only the files for your platform: each one has its own SHA-256. Standalone Linux core modules need an x86-64-v3 CPU; on older (baseline) CPUs, stick with the cores bundled in the main distro.
- Module version labels (for example
c19a6-bolt,alpha-1.0orv5zz-shared) are separate from the distro version. Online play is limited to reviewed cores; other cores still work offline.
HD packs
Optional HD texture and movie packs for each game. They need the native Nimbus build and your own disc. The Windows build uses the same shared pack loader as Linux, so the same packs apply there; we haven't run one on Windows yet.
Loading the pack list… If nothing shows up, open packs.json directly.
Checking a download
On Linux run sha256sum FILE; on Windows run certutil -hashfile FILE SHA256. The result must match the SHA-256 shown on the card. Each pack is a single zip.
About the project
Free. No catch.
FreeEverything here is free: the native builds, the modules, the HD packs and online play. There's no price, no paywall, no premium tier, and we don't take donations.
Closed source, for now
Open source plannedThe Nimbus Project is custom built for these three games, and we plan to make it open source. It isn't open source yet because of:
- Server hosting: we run the relay and online servers.
- Networking: keeping online play and netplay secure and stable.
- Cross compatibility: keeping the Linux, Windows and Android builds matched so crossplay works.
- Continued, focused development: keeping the work concise and moving.
We also plan to release a mature toolset in the future.
Gallery
Captures from the native builds of all three games. Click a tile to see it larger, and compare Original and Remastered modes below.
Original vs Remastered
The same moment from the native build, once in Original mode and once in Remastered mode. Drag the handle, or focus it and use the arrow keys.
Devlog & roadmap
- Done
One launcher for the trilogy
CRT menu, per-game status, keyboard, mouse and gamepad.
- Done
Netplay in the launcher
HOST, JOIN and LOCAL 2 PLAYERS, join codes, ping and input delay. Internet play goes through Nimbus relays.
- Done
HD packs
AI-upscaled texture packs for all three games and HD movies for Sagas, built and validated. Publishing in Downloads soon.
- Done
The trilogy on Android
Budokai, Budokai 2 and Sagas all run on Android, on par with Linux. Sagas runs above full speed on the Retroid Pocket 5 and RG Slide.
- Now
Budokai & Budokai 2
Bringing both fighters up to the same level as Sagas.
- Done
The trilogy on Windows
Budokai, Budokai 2 and Sagas run natively on Windows 11 x64, with the same launcher, host and renderer as Linux and Android. First published in Alpha 1.0.
- Done
Alpha 1.1
Released 2026-11-02: polished Android touch controls, the Sagas outline fix, Components versions & rollback, and separate module downloads. See the 1.1 notes.
- Done
Alpha 1.2
Released 2026-11-02: Quick Match in Budokai and Budokai 2 starts right at character select with every fighter unlocked, and Local Two Players uses the same setup. See the 1.2 notes.
- Done
Servers in Europe
Alpha 1.3 (2026-11-02) adds London and Amsterdam relays, for five regions alongside West, Central and East US, on Linux, Windows and Android. See the network map and What's new.
- Now
Crossplay
Linux and Android: tested with Budokai 2, where the Linux and Retroid Pocket 5 test pair played 14,000-field sessions on LAN and over the internet relay and recovered from a forced desync. Sagas co-op has now been tested between Linux and Android as well; Budokai is next. Windows and Android: all three games matched our reference checkpoints over the relay. Windows and Linux: in testing with Budokai 2. See Online.
- Now
Budokai 2 HD movies
Both movies are extracted frame by frame and waiting to be upscaled.
- Next
Lobby everywhere
Quick match, public games and tournaments in every launcher: Linux, Windows and Android.
Planned & ideas
What we're working toward next. These are plans and ideas, not promises, and there are no dates yet.
Cel shading for Sagas
In progressNimbus uses its own runtime and renderer, so we can add new looks like a cel-shaded mode for Sagas, plus other visual effects. See a first look.
Budokai 2 co-op campaign
In progressPlay through the Budokai 2 story with a friend, on top of the netplay the launcher already has.
Sagas co-op improvements
In progressQuality-of-life fixes for Sagas co-op, which already works between Linux and Android.
Cross-platform World Tournament
PlannedWorld Tournament mode with players on Linux, Windows and Android in the same bracket.
Speed on budget devices
GoalSagas lagging on a Unisoc T820 phone is one of the reasons Nimbus exists. The goal is smooth, full-speed play on modest Android hardware, not just flagship handhelds.
Full devlog coming soon.
FAQ
Is this an emulator?
No. Nimbus runs on a hybrid core that sits between recompilation and decompilation. Each game gets its own native core, and those cores run on a shared Nimbus host and renderer. Dolphin isn't involved, and there's no emulator and no interpreter emulating the hardware. Detailed architecture notes are coming to the site later.
Do I need my own copy of the game?
Yes. No disc images included; your own NTSC-U discs are required. Bring your own legally obtained disc of Budokai, Budokai 2 or Sagas, and the launcher shows NO DISC until it finds one.
Which versions are supported?
The North American (NTSC-U) GameCube releases of all three games.
Can I play with a friend online?
Yes. Host a game from the launcher, send your friend the join code and they join over your LAN or over the internet through Nimbus relays. Sagas is co-op; Budokai and Budokai 2 are versus. Local two-player works too.
Which Linux distros are supported?
Ubuntu 26.04 (64-bit x86) for now. Other distros aren't supported yet.
Will it run on my handheld?
The Android build runs all three games and needs a 64-bit (arm64) device running Android 13 or later. Sagas runs above full speed on handhelds like the Retroid Pocket 5 and RG Slide.
What are the HD packs?
Optional downloads that swap in AI-upscaled textures (all three games) and upscaled movies (Sagas). They work with the native builds only, and you can switch back to the originals from the F1 menu at any time. See Downloads.
Does it cost anything? Is it open source?
It's free: the builds, the HD packs and online play, with no paywalls and no donations. The Nimbus Project is closed source for now, and we plan to make it open source. It isn't yet because of server hosting, networking, cross compatibility and keeping development focused; we also plan to release a mature toolset in the future. See About the project.
When is it coming out?
It's out. Alpha 1.3 came out on 2026-11-02 for Ubuntu 26.04, Windows 11 (Vulkan) and Android 13+ (arm64), following Alpha 1.2 and 1.1 earlier the same day and Alpha 1.0 on 2026-11-01. Get it from Main distro. It's an early alpha; follow the roadmap above for what's next.
How do I reach you?
Email TheNimbusProject@yahoo.com.
Special Thanks
The Nimbus Project stands on a lot of other people's work. Thank you.
The original games
- Dragon Ball Z: Budokai and Dragon Ball Z: Budokai 2: developed by Dimps (GameCube versions ported by Pyramid), published in North America by Atari.
- Dragon Ball Z: Sagas: developed by Avalanche Software, published by Atari.
- Dragon Ball was created by Akira Toriyama, with Bird Studio/Shueisha and Toei Animation.
- Nintendo GameCube is a trademark of Nintendo.
Open-source and third-party software in the downloads
Licenses are as stated in the notice files shipped with Alpha 1.0. The full license texts ship inside each download (licenses/THIRD_PARTY_NOTICES.txt on Windows, assets/THIRD_PARTY_NOTICES.txt in the Android app, and inside the Linux .run).
Rendering and graphics 10
Listed in the notices of all three downloads
- Aurora (encounter/aurora) MIT · renderer platform layer
- Dawn and Tint (WebGPU) BSD-3-Clause · GPU backend
- SPIRV-Tools Apache-2.0 · inside Dawn
- SPIRV-Headers MIT · inside Dawn
- PartitionAlloc BSD-3-Clause · inside Dawn
- Abseil C++ Apache-2.0
- SDL 3 Zlib · window, input and audio
- Dear ImGui MIT · menus and HUD
- dav1d BSD-2-Clause · HD movie playback (AV1)
- magic_enum MIT
Core libraries 9
Listed in the notices of all three downloads
- {fmt} MIT (with an optional exception) · logging
- xxHash BSD-2-Clause · hashing
- SQLite Public domain · pipeline cache
- Zstandard (zstd) BSD-3-Clause (dual BSD / GPL-2; used under BSD)
- jemalloc BSD-2-Clause · host memory allocator
- Boost.Context BSL-1.0 · guest thread switching
- Monocypher BSD-2-Clause or CC0-1.0 (used under BSD-2-Clause) · netplay encryption, join codes
- libpng Libpng · PNG textures and artwork
- zlib-ng Zlib · compression
Fonts 2
Listed in the notices of all three downloads
- Roboto Medium (Christian Robertson / Google) Apache-2.0 · HUD text
- DejaVu Sans Mono Bold / Bitstream Vera Bitstream Vera / DejaVu · launcher bitmap font
Linux system libraries 31
Linux .run only: unmodified Ubuntu 26.04 packages, used only when your system lacks its own copy
- alsa-lib LGPL-2.1+
- PulseAudio client library LGPL-2.1+
- libasyncns LGPL-2.1+
- FLAC GPL-2+ or LGPL-2.1+
- libogg BSD-3-Clause
- libvorbis / libvorbisenc BSD-3-Clause
- Opus BSD-3-Clause
- mpg123 LGPL-2.1
- LAME LGPL-2+
- libsndfile LGPL-2.1+
- Wayland (client, cursor, egl) X11
- libdecor Expat
- libX11, libX11-xcb, libXau, libXcursor, libXext, libXfixes, libXi, libXrandr, libXrender, libXss, libXtst X.Org permission notices (full text in the build)
- libXdmcp OpenGroup-MIT
- libxcb X.Org-style permission notice (full text in the build)
- libxkbcommon MIT-style permission notices (full text in the build)
- libdrm Expat
- Mesa (libgbm) MIT
- D-Bus GPL-2+ or AFL-2.1, and Expat and Tcl-BSDish
- systemd (libsystemd) LGPL-2.1+
- AppArmor (libapparmor) GPL-2+ (library files LGPL-2.1+)
- libffi Expat
- Expat MIT
- FreeType FTL
- GNU FriBidi LGPL-2.1+
- Brotli MIT
- bzip2 BSD-variant
- zlib Zlib
- Zstandard (libzstd) BSD-3-Clause or GPL-2
- libpng (system copy) libpng
- GCC runtime (libgcc_s, libstdc++) GPL-3+ with the GCC Runtime Library Exception 3.1
Toolchain runtimes 2
Shipped as runtime libraries in the Windows and Android builds
- LLVM libc++ and libunwind license file not included in this build · Windows libc++.dll / libunwind.dll, Android libc++_shared.so
- MinGW-w64 winpthreads license file not included in this build · Windows libwinpthread-1.dll
Map data
The coastlines in our network map come from Natural Earth (1:110m land), free public-domain map data.
Disclaimer
All games, characters, names, artwork, music and trademarks belong to their respective owners. The Nimbus Project claims none of it as its own.
The Nimbus Project is an unofficial fan project. It is not affiliated with or endorsed by Nintendo, Atari, Dimps, Avalanche Software, Bird Studio/Shueisha, Toei Animation or any other rights holder.
No disc images or game data are distributed. You need your own NTSC-U discs.
The Nimbus launcher, host, renderer and core tooling are our own original code.