Is this the official NX2navi website?

No. It is an English install guide for tangerineturtle1/NX2navi. Software issues belong on GitHub.

Do you sell the game?

No. Buy Nintendo titles from legitimate storefronts. This site has no cart and no checkout flow at all here.

Which routes does sitemap.xml list?

Home, /install, /install/windows, /setup, /controls, /requirements, /troubleshoot, /release, /setup-vs-source, /about, /contact, plus /privacy-policy and /terms-of-service. That matches GUIDE_PATHS and llms.txt.

Where do download buttons actually go?

GitHub’s latest-release API for tangerineturtle1/NX2navi, matching NX2navi-Setup- .exe. If that call fails, the button becomes Open release Assets so you pick the file by name.

NX2navi · Windows · Vulkan

About this site

nx2navi.online explains how to download and start NX2navi. It is independent of Nintendo and of the people who publish the GitHub Releases. English only for now. Windows Setup is the documented player path on this domain.

Setup and updates come from GitHub Releases for tangerineturtle1/NX2navi. Latest tag is read at request time.

What we publish

English install pages for Windows, plus first-time setup, controls, hardware floor, a Setup versus source comparison, release-file notes, and short troubleshooting. Download links point at GitHub Releases for tangerineturtle1/NX2navi. There is no account, no search, and no comment thread. Structured data on these pages is WebSite, Organization, SoftwareApplication, WebPage, and FAQ where a page has questions.

Repository: https://github.com/tangerineturtle1/NX2navi
Releases / Assets: https://github.com/tangerineturtle1/NX2navi/releases
Issues: https://github.com/tangerineturtle1/NX2navi/issues
Launcher doc: docs/launcher.md
Controls doc: docs/controls.md
Hardware: README.md system requirements

Independence and trademarks

We are not affiliated with Nintendo. We are not the NX2navi maintainers. The Legend of Zelda, Ocarina of Time, Nintendo Switch, and Nintendo Switch 2 are trademarks of Nintendo. NX2navi itself describes an independent, non-commercial fan project. If this guide disagrees with the README, trust the repository and email support@nx2navi.online so we can fix the sentence. Nothing here is a license to copy Nintendo’s game or to redistribute a built folder that contains it.

What the inbox is for

support@nx2navi.online is for wording, privacy, and accessibility on this domain. NX2navi crashes belong on GitHub Issues with logs\nx2navi.log. Advertising may appear later if a publisher ID is configured; privacy policy covers that. Today the pages are readable without an account cookie. Download buttons keep sending browsers to Releases.

How these pages are built

The site is a small Next.js app. Pages are English, Brazilian Portuguese, and German. There is no user database. Download buttons ask GitHub for the latest release at request time; if that call fails, you still get a link to Assets. We would rather show a fallback than invent a filename. Sitemap lists home, install, Windows, setup, controls, requirements, troubleshoot, releases, Setup versus source, about, contact, privacy, and terms. llms.txt lists the same routes for automated readers. If a crawler indexes a download URL, it should be a github.com URL. JSON-LD on guide pages is a graph of WebSite, Organization, SoftwareApplication pointing at the GitHub repo, WebPage, and FAQPage when a page has questions. robots.txt allows crawlers and names sitemap.xml. Favicon and theme tokens are a light page with a green accent, not a store blue. None of that infrastructure is Nintendo’s CDN.

Why the page tree looks like this

The information architecture is a home download panel, per-OS install where an OS actually exists, first setup, controls, hardware, troubleshoot, a releases explainer, a comparison page, then about and contact. For this project the only OS page is Windows. The comparison is Setup versus source, not Canary versus Stable, because GitHub tags here are a single channel. Software bugs still go upstream. GitHub remains the place for the Setup file.

Accuracy and updates

When the README changes a requirement — CPU flags, Vulkan extensions, RAM, disk — this guide should follow. Until someone edits the page, the repository wins. When a new Asset name appears, the matcher on the home panel looks for Setup-<version>.exe with the project prefix; a renamed file will fall back to Assets. That is deliberate. We would rather send you to the list than deep-link a stale object. If you find a sentence that still describes an old fog bug as current after a fix release, write the site inbox with the URL. Do not open a GitHub issue against the port for a typo on this domain. Do not open a site email for a particle crash. Split those jobs and both get answered faster. Screenshots of the in-game F1 menu belong on Issues only when they show a rendering bug. Capture overlays and frame-time graphs are fine to share. A still of the title screen is not a license to upload the binary next to it. Ask before you assume a capture is fair use in your country. Header links cover Download, Install, Setup, Controls, and Troubleshoot. The sidebar adds Windows, Requirements, Setup vs Source, About, Contact, Privacy, and Terms so the sitemap and the chrome stay in the same tree.

FAQ

Is this the official NX2navi website?: No. It is an English install guide for tangerineturtle1/NX2navi. Software issues belong on GitHub.
Do you sell the game?: No. Buy Nintendo titles from legitimate storefronts. This site has no cart and no checkout flow at all here.
Which routes does sitemap.xml list?: Home, /install, /install/windows, /setup, /controls, /requirements, /troubleshoot, /release, /setup-vs-source, /about, /contact, plus /privacy-policy and /terms-of-service. That matches GUIDE_PATHS and llms.txt.
Where do download buttons actually go?: GitHub’s latest-release API for tangerineturtle1/NX2navi, matching NX2navi-Setup-<version>.exe. If that call fails, the button becomes Open release Assets so you pick the file by name.