Pick a release file

The player file versus helper files

On a typical NX2navi tag you will see NX2navi-Setup-<version>.exe, NX2navi-app-<version>.zip, a runtime zip whose name includes a Python version, and NX2navi-update.json. Setup is the file new players run next to a dump. The app zip and runtime zip are pieces the launcher can fetch when it updates itself. The JSON file tells that updater what to pull. If you treat every Asset as an alternate game, you will unpack a runtime and wonder why Ocarina of Time is not inside. Source zips and tarballs from GitHub’s automatic archive buttons are for people who follow docs/building.md, not for SmartScreen.

Latest versus a specific tag

The download panel on this site asks GitHub for the latest non-draft release and then picks the Setup name with a version number. When GitHub rate-limits the request, we stop guessing and send you to the release page. Pinning an older tag is how you roll back after a graphics regression. 0.5.0, for example, restored fog and lighting after 0.4.0. If you already had 0.4.0, the notes said to start the launcher and take 0.5.0 rather than hunt Setup again. Read the body of the tag you are about to run. NX2navi changes quickly in early development; a month-old blog post may describe a file that no longer exists.

How this site uses GitHub

Download clicks go to github.com/tangerineturtle1/NX2navi/releases. If the button on this page and the Assets list disagree, trust Assets. If the prose here and the README disagree, trust the README. Check the filename before you run anything that arrived through a chat app. A file called NX2navi that is actually an unrelated executable is not a GitHub Asset.

Rollback to an older tag

Open the Releases list, open the older tag, download that tag’s Setup, and run it the same way as a first install. Keep the dump where the launcher already expects it. Shader caches from a newer tag may be rebuilt; that is expected. The project asks you not to share the built game folder; it is the output of this PC’s compile.

Reading a tag body before you click

Each GitHub release body is short on purpose. It names the Setup file for new installs and tells existing players whether the launcher can self-update. It lists hardware again so a phone-sized GPU does not surprise you. It lists fixes and known issues so you do not file a duplicate about fog or particles. If the body and this page disagree on a filename, the body on that tag wins. Pre-release marks matter: this site’s latest-release API skips drafts, but it will still follow whatever GitHub calls the latest stable tag. Do not scrape random forks that copy the name. The only Releases URL this guide intends is the project’s own releases list on GitHub. Source tarballs GitHub generates automatically are not Setup. Checksums, if a tag publishes them, live on that tag too. If a chat paste shows a Mega or mediafire link with the same filename, treat it as unrelated. Filename collision is not provenance. Wait for the Assets list even when a friend swears their copy is faster. If you need the exact object, copy the browser_download_url from the GitHub API, not from a screenshot of Discord. Direct download on this domain matches NX2navi-Setup-<version>.exe only. The app zip, runtime zip, and update.json stay on the same tag so the launcher can fetch them; they are not a second player install. After 0.4.0, people with a working launcher were told to accept 0.5.0 in-app rather than hunt a second Setup. Read that sentence on the tag you actually opened.

FAQ

Where does Direct download go?

GitHub Releases. The button matches NX2navi-Setup-<version>.exe on the latest tag, or falls back to Assets.

I already installed an older tag. Do I need Setup again?

Try the launcher’s update first. Use Setup from the new tag if the launcher cannot update. After that class of update, the first boot can rebuild shaders again for about a minute and a half.

Which Asset is safe to ignore for a first install?

The app zip, the runtime zip, update.json, and the automatic source archives GitHub adds. Those feed the launcher or a source checkout, not a first-run Setup on Windows.