Play your own Switch games on iPhone/iPad — one-click macOS app, no terminal. | 把 Switch 游戏装进 iPhone:图形界面一键构建,不用命令行。Bring your own game.
Swift apple-siliconcustom-formathomebrewiosipaipadipadosiphonemetalnative-portnintendo-switchnxnativeromfsswitch-games
Release notes: English first, Chinese second
v0lumehif4e66de56542
diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.mdindex 544ea7ee..72c382f9 100644--- a/.github/copilot-instructions.md+++ b/.github/copilot-instructions.md@@ -11,4 +11,4 @@ Read [AGENTS.md](../AGENTS.md) (the fork's, at the root) and [CONTRIBUTING.md](.- You work on a Linux runner and cannot build or run the macOS app. The macOS jobs of `tests.yml` are the check: do not claim a Swift or Metal change works until they are green.- A PR that changes the launcher needs before and after screenshots. You cannot capture them on a Linux runner: say so under Screenshots and ask for them in the PR (CONTRIBUTING.md, "For AI agents and other tools").- Issues and PRs follow the forms and the PR template (CONTRIBUTING.md, "For AI agents and other tools").-- Release notes follow `.github/release_notes_template.md`, Chinese first, then English, no emojis.+- Release notes follow `.github/release_notes_template.md`, English first, then Chinese, no emojis.diff --git a/.github/release_notes_template.md b/.github/release_notes_template.mdindex fddfb7bc..e5cca95e 100644--- a/.github/release_notes_template.md+++ b/.github/release_notes_template.md@@ -3,7 +3,7 @@ Template for the notes of a release. Copy it to a file, fill it in, delete thesePublish with `gh release edit <tag> --notes-file <file>`. Never paste notes from a chat: pasted text brings emojis along.Rules (RELEASING.md, "Release notes" has the same list):-- Chinese first, English second, with the same content in both.+- English first, then Chinese, with the same content in both.- No emojis, no pictograms and no symbols in the text (no warning signs, no flags, no arrows).- No semicolons (also not the full-width one), no em-dashes (also not the Chinese double dash).- Plain English and plain Chinese. Short sentences.@@ -16,39 +16,12 @@ Rules (RELEASING.md, "Release notes" has the same list):<!-- One line: the version and what it is about. -->**vX.Y.Z: the one thing this release is about.**-## 中文--<!-- First paragraph, only when players must act, for example "update now". Bold, plain words, no symbol. Delete it when no action is needed. -->-**App 版本是 0.7.3 或更早?请立即更新。** 一句话说明什么会出问题,一句话说明更新后会怎样。详情:链接。--<!-- The headline feature: a heading line and 3 to 5 sub-bullets. Delete the group when there is no headline feature. -->-**重点**--**功能的名称**-- 一个要点-- 一个要点-- 一个要点--<!-- One bullet per change: a bold lead, a colon, one or two plain sentences, the numbers as #N. -->-**新增**-- **改动的标题**:玩家现在能做什么,一两句话(#N、#M)--**修复**-- **修复的标题**:原来哪里出错,现在会怎样(#N)--**已知问题**-- **问题的标题**:哪里还不能用,暂时怎么办(#N)--<!-- Write "暂无已知问题" when there are none. -->--**系统要求**-- iOS 或 iPadOS 26 或更新版本-## English-<!-- The same content as the Chinese part, in the same order, with the same numbers. -->+<!-- First paragraph, only when players must act, for example "update now". Bold, plain words, no symbol. Delete it when no action is needed. -->**On 0.7.3 or older? Update now.** One sentence on what breaks and one on what the update does. Details: link.+<!-- The headline feature: a heading line and 3 to 5 sub-bullets. Delete the group when there is no headline feature. -->**Highlights****Name of the feature**@@ -56,6 +29,7 @@ Rules (RELEASING.md, "Release notes" has the same list):- One point- One point+<!-- One bullet per change: a bold lead, a colon, one or two plain sentences, the numbers as #N. -->**New**- **Lead of the change**: what a player can do now, in one or two sentences (#N, #M)@@ -70,6 +44,33 @@ Rules (RELEASING.md, "Release notes" has the same list):**Requires**- iOS or iPadOS 26 or later+## 中文++<!-- The same content as the English part, in the same order, with the same numbers. -->++**App 版本是 0.7.3 或更早?请立即更新。** 一句话说明什么会出问题,一句话说明更新后会怎样。详情:链接。++**重点**++**功能的名称**+- 一个要点+- 一个要点+- 一个要点++**新增**+- **改动的标题**:玩家现在能做什么,一两句话(#N、#M)++**修复**+- **修复的标题**:原来哪里出错,现在会怎样(#N)++**已知问题**+- **问题的标题**:哪里还不能用,暂时怎么办(#N)++<!-- Write "暂无已知问题" when there are none. -->++**系统要求**+- iOS 或 iPadOS 26 或更新版本+---<!-- The install line (v0.7.2 and v0.7.3 had it). Keep it for a final release. -->diff --git a/AGENTS.md b/AGENTS.mdindex 27ce68dc..e4b86bb7 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -12,4 +12,4 @@ This is the fork's guide. The engine has its own, upstream's: [engine/AGENTS.md]- **Merging with admin rights.** An admin merge never goes over a red check. That holds even when @LNPANDY overrides an objection. If a re-review is slow, the other maintainer pings the reviewer and does not merge with admin rights.- **Checks.** `cd frontend && swift build && swift test` for the Mac launcher (its tests read `engine/`, so sync first), `python3 -m unittest discover -s frontend-qt/tests` for the Qt front end (and `python3 frontend-qt/gen_localization.py` leaves `frontend-qt/nspb_qt/localization.py` unchanged), `python3 -m unittest discover tools/tests` for the tools. The engine's own tests run in `engine/` as `tests.yml` does. The pre-commit hook runs `python3 tools/engine.py check` when `patches/` or `.upstream-ref` is staged. The pre-push hook runs the checks above for the files the push changes, `tools/githooks.py` has the list. Fix the failure, do not bypass the hook.- **Language and text.** Everything is in English except the Chinese pages (`*.zh-CN.md`) and the launcher's strings. No semicolons in UI strings, READMEs and docs.-- **Release notes.** They follow `.github/release_notes_template.md`, Chinese first, then English, no emojis.+- **Release notes.** They follow `.github/release_notes_template.md`, English first, then Chinese, no emojis.diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex e2069b81..1bee29f9 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -78,5 +78,5 @@ Issue forms and the PR template apply in the browser only. `gh issue create`, th- **Ideas and plans.** These have no form. Write plain sections that fit the content, for example `### Idea`, `### Plan` and `### Done when`. Leave out the problem fields (`This is`, `NX2Apple version`, `Computer and OS`, `Copy diagnostics`). Open it with the labels `idea` and `no-triage`.- **Pull requests.** Use the sections of [.github/pull_request_template.md](.github/pull_request_template.md): `gh pr create --template .github/pull_request_template.md`, or the same headings in `--body`. Answer each section and remove the `<!-- -->` hints. Under Fix or feature, tick one box. A change to the engine follows the rule above.- **Screenshots.** A PR that changes the launcher needs before and after images in its body (see "A pull request"). On a Mac, capture the changed views of `frontend/` with `NX_LAUNCHER_CAPTURE_DIR=<dir> swift test` and `NX_CAPTURE_LANG` for the language (`de`, `sv` or `zh`, English is the default). `frontend-qt/` has no capture, so take its screenshots by hand. Attach the images with `gh pr create --attach` or `gh pr edit --attach`, once per file. Write `` in the body and pass `--attach ./before.png`. `gh` uploads the file and rewrites the path to a `https://github.com/user-attachments/assets/...` URL. This needs `gh` 2.99.0 or newer, push access to the repository, and an OAuth or personal access token (a GitHub App token is rejected). Afterwards, read the body back and check that it holds the asset URLs and no local paths. If your `gh` or token cannot attach, say so under Screenshots, give the paths of the captures, and ask the user to attach them. An agent without a Mac (a Linux runner) says under Screenshots that it could not capture the views and asks for screenshots in the PR.-- **Release notes.** They follow `.github/release_notes_template.md`, Chinese first, then English, no emojis.+- **Release notes.** They follow `.github/release_notes_template.md`, English first, then Chinese, no emojis.- Never attach or commit keys, game files or data extracted from a game, and do not paste key values into a log or a diagnostics report.diff --git a/RELEASING.md b/RELEASING.mdindex 997b5937..ef16d13a 100644--- a/RELEASING.md+++ b/RELEASING.md@@ -57,7 +57,7 @@ A final tag on a commit without a candidate fails. In an emergency, a manual runCI writes a short body: the version and the tested candidate. The readable notes are written by a person or an agent from [.github/release_notes_template.md](.github/release_notes_template.md).-- Chinese first, English second, under `## 中文` and `## English`, with the same content in both. Each part has one bullet per change, grouped in bold: a notice, Highlights, New, Fixed, Known issues, Requires.+- English first, Chinese second, under `## English` and `## 中文`, with the same content in both. Each part has one bullet per change, grouped in bold: a notice, Highlights, New, Fixed, Known issues, Requires.- No emojis, no pictograms and no symbols in the text. No semicolons (also not the full-width one) and no em-dashes. Plain English and plain Chinese.- People are written as `@login`, the owner as `@LNPANDY`.- Every claim comes from the changelog row, the merged pull requests or the issues. Nothing is invented.