feat(saves): see what each save slot has and is missing, and change it, outside the game #1401

Open
mooki wants to merge 7 commits from mooki/Longshot:save-file-editor into main
Member

Type: feat · Risk: low · Tested on: Linux, Python 3.12 and 3.14 (game-free checks on a made-up game); one edited save loaded and looked at in the game on Linux, RTX 4090 · Needs: Windows

Why

Nothing lets a player look into a save without starting the game: how close a slot is to 100%, which Gold Skulltulas, chests or heart pieces are missing and where, whether a dungeon's map and keys are all there. Nothing lets a tester or someone finishing a save fix one thing in a file either; the only tools are copying whole save folders (scripts/longshot_saves.py) or the Debug tools inside a running game. This adds a command line save editor with a full report per slot and the same kind of edits the Debug tools make, with a backup before every write.

What changed

scripts/longshot_save_editor.py reads a save folder and the player's own game folder and reports, per slot, what the slot has and what it is missing, by name and area. set and clear take a flag, an entry, an area or a whole category; give takes items (counted ones within the cap the bags and wallets set), hearts, rupees and small keys; start puts Link at a named start place; copy copies a slot. Every write refuses while a game runs, copies the save folder first, writes each file whole beside its place and swaps it in with a rename, reads it back, and puts the files back if that fails. Nothing of the game is in the repository: the flag list, the item table, the quests, the placed objects and the names are read at run time from the game folder.

  • scripts/oot_savefile.py (new): the save file format and the readers under it. A save ends in a sorted table of 64-bit keys (one per placed object that is done: Gold Skulltulas, heart containers, heart pieces); the earlier tools never read it. A file read and written unchanged is byte for byte what it was. Also the game's BYML, SARC and zstd files (zstandard or Python 3.14's own zstd) and the atomic write.
  • scripts/longshot_save_editor.py (new): the catalogue (equipment, items, masks, upgrades, songs, quest items, hearts, heart containers and pieces, rupees, chests, Gold Skulltulas, each dungeon's map, compass, boss key and small keys, bosses, the Hall of Fallen Foes, story and side quests), the report (--json, --missing), the edits, the backup and the checks. It reuses scripts/longshot_saves.py for finding the save, the running-game check and the backup folder; that file is not changed.
  • tests/test_longshot_save_editor.py (new): 64 checks on a made-up game and made-up saves: the format, the catalogue, the report and every command with its refusals.
  • --json on every command (schema 1, what changed, the backup, a reason code for every refusal), for the launcher's save editor and other programs; the text output is unchanged.
  • docs/development.md: a row for LONGSHOT_GAME in the switch table; a check reads the editor's source for the LONGSHOT_ names it reads and fails when one has no row.
  • docs/save-editor.md (new) and one-line links from docs/saves.md, docs/saves-script.md and docs/development.md.
  • Game identifiers in the source: the rules that find things in the game's data name the identifiers they look for (an actor kind such as the Gold Skulltula, a flag family such as IsTreasureBoxOpen.), as gpu/vk/oot_cheat_items.h already names the pouch items. There is no list of flags, items or names in the source: the lists are read from the player's game folder at run time.
  • Unchanged on purpose: the save script, the game, the launcher. An edit writes the flags the game's own lists name and nothing more; the guide says what that does not do (a boss set done is its kill counter, heart container and boss key, not its events, door and warp; the mini-games are listed and never count for 100%).

Measurements

Verdict: nothing to measure: a command line tool that never runs with the game and is not in any build; no speed claim is made.

Flags and settings

One environment variable, read by the new save editor script only (not by the game or the builder).

Flag What it is Before this PR After this PR Effect Helps / doesn't help / untested Recommendation
LONGSHOT_GAME The game folder (with its romfs), or the RomFS folder, that scripts/longshot_save_editor.py reads when --game is not given not read unset: the editor uses the current folder if it holds romfs, else asks for --game names the folder once instead of on every command helps: tested by the checks (unset and empty are refused with a reason) set it in your shell if you edit saves often; leave it unset otherwise

Testing

Tested: python -I -B tests/test_longshot_save_editor.py: 64 checks, on Python 3.12 (the pinned one, with zstandard) and 3.14 (its own zstd), warnings as errors. On the base without the change the file does not exist, so the checks cannot run there. Whole suite on Linux, on this branch rebased onto main 544229a26: 665 passed, 40 failed, 17 skipped. The same 40 fail the same way on main 544229a26 itself (run one by one on a clean checkout), and none touches a save: test_bug_report_defaults, test_cpu_report, test_crt_options, test_damage_debug_menu, test_display_startup_failure, test_dlss_feature_size, test_failed_compile_keeps_objects, test_framegen_preset, test_fsr_uniform_ownership, test_guest_imported, test_hud_layout_row, test_import_reach, test_invalidate_vcore, test_linux_preflight, test_linux_pressure, test_linux_update, test_mirror_budget, test_missing_nup, test_mods_size_table, test_nonuniform_image_arrays, test_parallel_init_order, test_pending_guest_import, test_pipeline_play_cache, test_present_thread, test_profiling_mode, test_readback_timeout_source, test_replay_write_order, test_rumble_menu, test_run_all_changed, test_slow_frames, test_staging_burst, test_switch_table, test_target_image_pool, test_tested_configurations, test_upscaler_round_trip, test_upscaler_rows, test_vcore_escape, test_vk_occlusion_queries, test_vk_swapchain_compat, test_walk_key. Beyond the checks: the report was run on 315 slots of 54 saves (the early, test and a finished real save) without an error, and its numbers for a real finished save agree with what the game's own lists say about it (not published: a player's save). Edits were read back with an independent reader of the same format and agree. In the game (Linux, RTX 4090, driver kernel lines 0, windowless, build 220ffa599, 17 Nov 2026): one slot edited with the tool (6 hearts, 100 rupees, Hookshot, Bomb Bag, 20 bombs, Slingshot, all songs, a dungeon's map and compass, the Gold Skulltulas and one chest of Kokiri Forest, and the start place Hyrule Field, front of the market) was continued from the title with --boot continue. The game loaded it: Link stands on the drawbridge at the field's gate as a child, the HUD shows six hearts, and the pause menu's Items page shows 100 of 200 rupees, 20 bombs, the Slingshot and the Hookshot. The state tap read the edited flags back from the running game: maximum life and life 24 quarters, 100 rupees, IsGet of the Hookshot and of two songs, 20 bombs, the dungeon's map flag and the chest's open flag, all 1 or as set. Run summary: fatal=0 crash=0 devlost=0 kernel=0 nvrm=0. Picture, two panels (uploaded by the maintainer's tooling): 1. the start the tool set, six hearts; 2. the Items page, 100 of 200 rupees, 20 bombs, Slingshot and Hookshot.

The edited save loaded by the game: 1, Link at the new start the tool set (the drawbridge in front of the market) with the six hearts it set; 2, the pause menu's Items page with the 100 of 200 rupees, 20 bombs, the slingshot and the hookshot it set.

Not tested: the pause menu's Collection page (the songs were read back from the running game through the state tap, not seen on screen); the Load screen after the edit; Windows (the new file's tests have only run on Linux); a game version other than the one the tool was written against; a save edited with set all played to the end.

Must be tested:

  • Windows, any GPU: run python -I -B tests/test_longshot_save_editor.py and, with your own game folder, python -I scripts/longshot_save_editor.py --game <game folder> report, expecting 64 checks passing and one report per slot (by hand, or the fork's Windows CI part of the Python checks).

Risks

What could break: only the tool's own use: an edit writes flags the game does not check against each other, so a set boss or quest can leave the game in a state it would never reach itself. The backup folder keeps the save from before every edit, and the guide says how to put it back. Nothing the game runs is changed.

Turning it off: revert the commits; no other file depends on the new ones.

Compatibility: Nothing changes.

Checklist

Everyone

  • One topic.
  • The title is a Conventional Commit (type(scope): description) of the status line's type.
  • Why gives the reason plainly and links the issues that fit (the tracker searched).
  • Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what
    can't be run by hand is in Testing's Not testable by hand, with why.
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and
    in Risks.
  • Testing names what was tested, what wasn't, and what must still be tested, where and how.
  • Rebased on current main.
  • python -I -B tests/run_all.py passes (any failure that also fails on main is named).
  • No game files, dumps, build output or generated files.
  • third_party/ untouched (a new folder with a PROVENANCE.md instead).
  • The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

When it applies

  • Switches documented (docs/development.md; the README for a menu row) and shipped at their recommended value.
  • A check under tests/ that reads changed source updated in this PR, not weakened (the new checks read the new scripts: the reason codes and the switch row; no existing check was changed).
  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.
  • Docs updated.

New on this forge; not opened on GitHub.

**Type:** feat · **Risk:** low · **Tested on:** Linux, Python 3.12 and 3.14 (game-free checks on a made-up game); one edited save loaded and looked at in the game on Linux, RTX 4090 · **Needs:** Windows ## Why Nothing lets a player look into a save without starting the game: how close a slot is to 100%, which Gold Skulltulas, chests or heart pieces are missing and where, whether a dungeon's map and keys are all there. Nothing lets a tester or someone finishing a save fix one thing in a file either; the only tools are copying whole save folders (`scripts/longshot_saves.py`) or the Debug tools inside a running game. This adds a command line save editor with a full report per slot and the same kind of edits the Debug tools make, with a backup before every write. ## What changed `scripts/longshot_save_editor.py` reads a save folder and the player's own game folder and reports, per slot, what the slot has and what it is missing, by name and area. `set` and `clear` take a flag, an entry, an area or a whole category; `give` takes items (counted ones within the cap the bags and wallets set), hearts, rupees and small keys; `start` puts Link at a named start place; `copy` copies a slot. Every write refuses while a game runs, copies the save folder first, writes each file whole beside its place and swaps it in with a rename, reads it back, and puts the files back if that fails. Nothing of the game is in the repository: the flag list, the item table, the quests, the placed objects and the names are read at run time from the game folder. - `scripts/oot_savefile.py` (new): the save file format and the readers under it. A save ends in a sorted table of 64-bit keys (one per placed object that is done: Gold Skulltulas, heart containers, heart pieces); the earlier tools never read it. A file read and written unchanged is byte for byte what it was. Also the game's BYML, SARC and zstd files (`zstandard` or Python 3.14's own zstd) and the atomic write. - `scripts/longshot_save_editor.py` (new): the catalogue (equipment, items, masks, upgrades, songs, quest items, hearts, heart containers and pieces, rupees, chests, Gold Skulltulas, each dungeon's map, compass, boss key and small keys, bosses, the Hall of Fallen Foes, story and side quests), the report (`--json`, `--missing`), the edits, the backup and the checks. It reuses `scripts/longshot_saves.py` for finding the save, the running-game check and the backup folder; that file is not changed. - `tests/test_longshot_save_editor.py` (new): 64 checks on a made-up game and made-up saves: the format, the catalogue, the report and every command with its refusals. - `--json` on every command (`schema` 1, what changed, the backup, a reason code for every refusal), for the launcher's save editor and other programs; the text output is unchanged. - `docs/development.md`: a row for `LONGSHOT_GAME` in the switch table; a check reads the editor's source for the `LONGSHOT_` names it reads and fails when one has no row. - `docs/save-editor.md` (new) and one-line links from `docs/saves.md`, `docs/saves-script.md` and `docs/development.md`. - Game identifiers in the source: the rules that find things in the game's data name the identifiers they look for (an actor kind such as the Gold Skulltula, a flag family such as `IsTreasureBoxOpen.`), as `gpu/vk/oot_cheat_items.h` already names the pouch items. There is no list of flags, items or names in the source: the lists are read from the player's game folder at run time. - Unchanged on purpose: the save script, the game, the launcher. An edit writes the flags the game's own lists name and nothing more; the guide says what that does not do (a boss set done is its kill counter, heart container and boss key, not its events, door and warp; the mini-games are listed and never count for 100%). ## Measurements **Verdict:** nothing to measure: a command line tool that never runs with the game and is not in any build; no speed claim is made. ### Flags and settings One environment variable, read by the new save editor script only (not by the game or the builder). | Flag | What it is | Before this PR | After this PR | Effect | Helps / doesn't help / untested | Recommendation | |---|---|---|---|---|---|---| | `LONGSHOT_GAME` | The game folder (with its `romfs`), or the RomFS folder, that `scripts/longshot_save_editor.py` reads when `--game` is not given | not read | unset: the editor uses the current folder if it holds `romfs`, else asks for `--game` | names the folder once instead of on every command | helps: tested by the checks (unset and empty are refused with a reason) | set it in your shell if you edit saves often; leave it unset otherwise | ## Testing **Tested:** `python -I -B tests/test_longshot_save_editor.py`: 64 checks, on Python 3.12 (the pinned one, with `zstandard`) and 3.14 (its own zstd), warnings as errors. On the base without the change the file does not exist, so the checks cannot run there. Whole suite on Linux, on this branch rebased onto main 544229a26: 665 passed, 40 failed, 17 skipped. The same 40 fail the same way on main 544229a26 itself (run one by one on a clean checkout), and none touches a save: test_bug_report_defaults, test_cpu_report, test_crt_options, test_damage_debug_menu, test_display_startup_failure, test_dlss_feature_size, test_failed_compile_keeps_objects, test_framegen_preset, test_fsr_uniform_ownership, test_guest_imported, test_hud_layout_row, test_import_reach, test_invalidate_vcore, test_linux_preflight, test_linux_pressure, test_linux_update, test_mirror_budget, test_missing_nup, test_mods_size_table, test_nonuniform_image_arrays, test_parallel_init_order, test_pending_guest_import, test_pipeline_play_cache, test_present_thread, test_profiling_mode, test_readback_timeout_source, test_replay_write_order, test_rumble_menu, test_run_all_changed, test_slow_frames, test_staging_burst, test_switch_table, test_target_image_pool, test_tested_configurations, test_upscaler_round_trip, test_upscaler_rows, test_vcore_escape, test_vk_occlusion_queries, test_vk_swapchain_compat, test_walk_key. Beyond the checks: the report was run on 315 slots of 54 saves (the early, test and a finished real save) without an error, and its numbers for a real finished save agree with what the game's own lists say about it (not published: a player's save). Edits were read back with an independent reader of the same format and agree. In the game (Linux, RTX 4090, driver kernel lines 0, windowless, build 220ffa599, 17 Nov 2026): one slot edited with the tool (6 hearts, 100 rupees, Hookshot, Bomb Bag, 20 bombs, Slingshot, all songs, a dungeon's map and compass, the Gold Skulltulas and one chest of Kokiri Forest, and the start place Hyrule Field, front of the market) was continued from the title with `--boot continue`. The game loaded it: Link stands on the drawbridge at the field's gate as a child, the HUD shows six hearts, and the pause menu's Items page shows 100 of 200 rupees, 20 bombs, the Slingshot and the Hookshot. The state tap read the edited flags back from the running game: maximum life and life 24 quarters, 100 rupees, `IsGet` of the Hookshot and of two songs, 20 bombs, the dungeon's map flag and the chest's open flag, all 1 or as set. Run summary: `fatal=0 crash=0 devlost=0 kernel=0 nvrm=0`. Picture, two panels (uploaded by the maintainer's tooling): 1. the start the tool set, six hearts; 2. the Items page, 100 of 200 rupees, 20 bombs, Slingshot and Hookshot. ![The edited save loaded by the game: 1, Link at the new start the tool set (the drawbridge in front of the market) with the six hearts it set; 2, the pause menu's Items page with the 100 of 200 rupees, 20 bombs, the slingshot and the hookshot it set.](https://git.magicbean.dev/attachments/a7ec41d5-de2a-41ff-9f02-5af6c87c64a1) **Not tested:** the pause menu's Collection page (the songs were read back from the running game through the state tap, not seen on screen); the Load screen after the edit; Windows (the new file's tests have only run on Linux); a game version other than the one the tool was written against; a save edited with `set all` played to the end. **Must be tested:** - Windows, any GPU: run `python -I -B tests/test_longshot_save_editor.py` and, with your own game folder, `python -I scripts/longshot_save_editor.py --game <game folder> report`, expecting 64 checks passing and one report per slot (by hand, or the fork's Windows CI part of the Python checks). ## Risks **What could break:** only the tool's own use: an edit writes flags the game does not check against each other, so a set boss or quest can leave the game in a state it would never reach itself. The backup folder keeps the save from before every edit, and the guide says how to put it back. Nothing the game runs is changed. **Turning it off:** revert the commits; no other file depends on the new ones. **Compatibility:** Nothing changes. ## Checklist ### Everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`) of the status line's type. - [x] Why gives the reason plainly and links the issues that fit (the tracker searched). - [x] Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what can't be run by hand is in Testing's Not testable by hand, with why. - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [x] Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and in Risks. - [x] Testing names what was tested, what wasn't, and what must still be tested, where and how. - [x] Rebased on current `main`. - [x] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named). - [x] No game files, dumps, build output or generated files. - [x] `third_party/` untouched (a new folder with a `PROVENANCE.md` instead). - [x] The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled. ### When it applies - [x] Switches documented (docs/development.md; the README for a menu row) and shipped at their recommended value. - [x] A check under `tests/` that reads changed source updated in this PR, not weakened (the new checks read the new scripts: the reason codes and the switch row; no existing check was changed). - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. - [x] Docs updated. New on this forge; not opened on GitHub.
scripts/longshot_save_editor.py reads a save folder and reports, slot by slot, what the slot has and what it
is missing, by name and area: items, equipment, masks, upgrades, songs, quest items, hearts, heart containers
and pieces, rupees, chests, Gold Skulltulas, each dungeon's map, compass, boss key and small keys, bosses, the
Hall of Fallen Foes, story and side quests. set and clear take a flag, an entry, an area or a whole category;
give takes items (counted ones within the cap the bags and wallets set), hearts, rupees and small keys; start
puts Link at a named start place; copy copies a slot. Every write refuses while a game runs, copies the save
folder first, writes each file whole and swaps it in by a rename, reads it back and puts the files back if
that fails.

The categories, totals and the way each is told apart in the file are read from the player's own game folder
(--game): the flag list, the pouch table, the quests, the maps' placements and the game's text. Nothing of the
game is in the repository. scripts/oot_savefile.py is the layer below: the save file format (a file read and
written unchanged is byte for byte what it was, the 64-bit key table stays sorted), the game's BYML, SARC and
zstd files, and the atomic write.

tests/test_longshot_save_editor.py runs it all on a made-up game and made-up saves: the format, the
catalogue, the report, every command and its refusals.

Assisted-by: Claude Sonnet 5.5
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
docs/save-editor.md says what the report counts and where each count is read, what set, clear, give, start and copy
do and do not do, and what keeps a save safe. The report names a slot that cannot be read and goes on with the
others; the game's text falls back to another English archive, and the output is safe for a console that cannot
print the game's typographic quotes.

Assisted-by: Claude Sonnet 5.5
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Mini-games (the quests with no kind) are their own category: listed, never part of 100%, and `all` leaves them alone. Setting a boss also sets its heart container and its dungeon's boss key, and clearing takes them away. A bigger bomb bag, quiver, wallet or bag keeps the smaller tiers, and the slot card's item flags follow every item edit. The guide says what an edit still does not write.

Assisted-by: Claude Sonnet 5.5
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
--json prints one JSON object on stdout and nothing on stderr: for set, clear, give, start and copy what changed, the files written, the backup folder and a read-back verdict; for items and places the lists; for report a schema version. A refusal is {"ok": false, "error": {"code", "message"}} with a code a program can switch on (running, other_version, out_of_range, would_overwrite ...). The text output is unchanged. docs/save-editor.md has the keys and the codes.

Assisted-by: Claude Sonnet 5.5
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Fail carries a code and every place that raises it names one, so rewording a message cannot change what a program sees in --json. longshot_saves.py's refusals are given their codes where the editor calls it. Two checks: every Fail in the scripts has an explicit code the guide lists, and a patched message leaves the codes as they were.

Assisted-by: Claude Sonnet 5.5
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
docs(saves): the editor writes a slot's two files only, never the account's cleared-once mark
All checks were successful
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 9s
Website / Website on Cloudflare (pull_request_target) Has been skipped
CI / Workflow lint (actionlint) (pull_request) Successful in 17s
Guide screenshots / Guide images and local UI source review (pull_request) Successful in 18s
PR description / Description follows the template (pull_request_target) Successful in 11s
Third-party parts / As their notes say (pull_request) Successful in 23s
073339dd9d
Assisted-by: Claude Sonnet 5.5
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
mooki changed title from WIP: feat(saves): see what each save slot has and is missing, and change it, outside the game to feat(saves): see what each save slot has and is missing, and change it, outside the game 2026-11-17 11:51:21 +00:00
Author
Member

Pushed 6c45402bf. The forge checker warned that the diff adds LONGSHOT_GAME (the folder the save editor reads when --game is not given), so it now has a row in the switch table of docs/development.md, and a new check in tests/test_longshot_save_editor.py reads the editor's source for the LONGSHOT_ names it reads and fails when one has no row (it failed before the row was added). The description's Flags and settings section and the Switches documented box are filled in. Nothing else changed: 64 checks in that file pass on Python 3.12 and 3.14, test_env_on and test_doc_anchors pass.

Pushed 6c45402bf. The forge checker warned that the diff adds `LONGSHOT_GAME` (the folder the save editor reads when `--game` is not given), so it now has a row in the switch table of `docs/development.md`, and a new check in `tests/test_longshot_save_editor.py` reads the editor's source for the `LONGSHOT_` names it reads and fails when one has no row (it failed before the row was added). The description's Flags and settings section and the Switches documented box are filled in. Nothing else changed: 64 checks in that file pass on Python 3.12 and 3.14, `test_env_on` and `test_doc_anchors` pass.
docs(saves): LONGSHOT_GAME, the folder the save editor reads when --game is not given, has a row in the development guide
All checks were successful
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 7s
CI / Workflow lint (actionlint) (pull_request) Successful in 12s
Guide screenshots / Guide images and local UI source review (pull_request) Successful in 13s
Third-party parts / As their notes say (pull_request) Successful in 18s
PR description / Description follows the template (pull_request_target) Successful in 9s
6c45402bf7
A check reads the editor's source for the LONGSHOT_ names it reads and fails when one has no row in docs/development.md's switch table.

Assisted-by: Claude Sonnet 5.5
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Owner

Brought up to the ready-for-review standard (#1454): the checklist's Everyone list has two new boxes, added here from what this PR's description and comments show (please check they match what you know).

  • Tested on my own PC: ticked: Testing's Tested: the author ran the editor checks on Linux with Python 3.12 and 3.14, plus a game run of an edited save.
  • Nothing gets worse that I know of: ticked: A command-line tool with a one-line reason for no measurement, and Risks names no slowdown or memory cost.
Brought up to the [ready-for-review standard](https://git.magicbean.dev/MagicBeanDev/Longshot/src/branch/main/CONTRIBUTING.md#ready-for-review-out-of-wip) (#1454): the checklist's Everyone list has two new boxes, added here from what this PR's description and comments show (please check they match what you know). - *Tested on my own PC*: ticked: Testing's Tested: the author ran the editor checks on Linux with Python 3.12 and 3.14, plus a game run of an edited save. - *Nothing gets worse that I know of*: ticked: A command-line tool with a one-line reason for no measurement, and Risks names no slowdown or memory cost.
All checks were successful
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 7s
CI / Workflow lint (actionlint) (pull_request) Successful in 12s
Guide screenshots / Guide images and local UI source review (pull_request) Successful in 13s
Third-party parts / As their notes say (pull_request) Successful in 18s
PR description / Description follows the template (pull_request_target) Successful in 9s
This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u 'save-file-editor:mooki-save-file-editor'
git switch 'mooki-save-file-editor'
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot!1401
No description provided.