Skip to content
Game save workbench
Local-first tools No installation Support status shown
SAVEEDITOR.COM
Browse tools
DEVICE-LOCAL Favorites and recent pages stay in this browser.

Save Editors

NieR Replicant Save Editor

Edit only Slot 1 money in a verified NieR Replicant ver.1.22474487139 PC GAMEDATA file and rebuild that slot checksum.

NieR Replicant ver.1.22474487139... PC

01 / Tool workbench

Use the runtime only when it is actually ready.

The application shell fails closed. An input interface is not enabled merely because a WordPress Tool record exists; the declared engine must be registered in the current build.

NieR Replicant Save Editor
BROWSER LOCAL

Checking whether the declared runtime module is loaded. No input has been processed.

Session change summary

No output has been built in this session.

What this game-specific editor changes

Edit only Slot 1 money in a verified NieR Replicant ver.1.22474487139 PC GAMEDATA file and rebuild that slot checksum.

Verified input boundary

The selected filename must be exactly GAMEDATA, remain under 1 MiB, contain a populated Slot 1 corruption marker value of 200, a bounded ASCII Slot 1 name, plausible money/experience, and a valid documented Slot 1 checksum.

What is deliberately not claimed

Slots 2-3, name/experience writes, inventory/weapons, endings/quests, console saves, malformed-slot repair, and files whose Slot 1 checksum is already invalid are not claimed.

Output

A separate GAMEDATA copy with only the Slot 1 32-bit money word and its documented 32-bit checksum changed.

Instructions

Close the game, back up GAMEDATA, select that exact PC file, verify the read-only Slot 1 name/experience, edit money, and keep the original until the output is tested.

Verification

Verified from published Slot 1 offsets/checksum code with two deterministic fixtures, exact byte-range assertions, negative checksum/marker tests, original immutability, and post-write reopen.

02 / Compatibility

Know the supported input before opening a file.

Compatibility fields are intentionally explicit. Missing values stay unclaimed rather than being filled with generic assumptions.

Accepted extensions

none

Platforms

PC

Supported versions / editions

NieR Replicant ver.1.22474487139 PC GAMEDATA, populated Slot 1 subset.

Input constraints

The selected filename must be exactly GAMEDATA, remain under 1 MiB, contain a populated Slot 1 corruption marker value of 200, a bounded ASCII Slot 1 name, plausible money/experience, and a valid documented Slot 1 checksum.

Known limitations

Slots 2-3, name/experience writes, inventory/weapons, endings/quests, console saves, malformed-slot repair, and files whose Slot 1 checksum is already invalid are not claimed.

Output / result

A separate GAMEDATA copy with only the Slot 1 32-bit money word and its documented 32-bit checksum changed.

03 / Instructions

Use a reversible workflow.

File-oriented workflows start with an untouched original. Tool-specific instructions add only details documented for this utility.

  1. 01Keep the original

    Preserve an untouched copy before creating or transforming binary output.

  2. 02Confirm scope

    Match the file size, format, platform, and version to the support information on this page.

  3. 03Process locally

    Use the runtime only when the page reports that its declared engine is loaded.

  4. 04Validate output

    Compare or test the result before replacing any working source file.

Tool-specific steps

Close the game, back up GAMEDATA, select that exact PC file, verify the read-only Slot 1 name/experience, edit money, and keep the original until the output is tested.

04 / Privacy and processing

The processing mode is part of the product contract.

SaveEditor.com should state local processing only when the implementation truly keeps file contents in the browser. Server or hybrid processing must be disclosed just as clearly.

Declared mode

Browser local

Runtime state

Operational

Tool-specific privacy notes

The selected save is processed entirely in the browser after explicit selection. Phase 38 game profile and codec scripts contain no fetch, XMLHttpRequest, WebSocket, or sendBeacon calls. The original bytes are kept immutable; a separate output is produced only after exact profile matching and a successful post-write reopen.

05 / Troubleshooting

When a file is rejected, do not force it.

A rejection can indicate an unsupported size, format, version, platform, or byte sequence. Preserve the original and correct the input instead of bypassing validation.

Wrong file or size

Re-check the documented input type and browser size limit before retrying.

Unsupported format

A generic converter does not imply support for every game-specific container, signing scheme, or serialization format.

Source was modified

Return to the untouched source instead of repeatedly processing a damaged or partially transformed file.

Known Tool issues

Renamed files, empty/corrupt Slot 1 data, checksum mismatches, or non-ASCII Slot 1 names fail closed rather than being guessed.

06 / Verification

Support claims should be traceable.

The verification date, method notes, and public references are kept separate from marketing language so compatibility can be reviewed over time.

Last verified2026-08-08
Profilenier-replicant-pc-gamedata-v1

Method notes

Verified from published Slot 1 offsets/checksum code with two deterministic fixtures, exact byte-range assertions, negative checksum/marker tests, original immutability, and post-write reopen.

Public references

  1. https://github.com/TwertyMax/NierReplicantSaveEditor/blob/main/Save.cs
  2. https://github.com/Acurisu/NieR-Replicant-ver.1.22474487139

07 / FAQ

Questions to answer before editing.

These answers are generated from the Tool record and current runtime state rather than generic compatibility promises.

Is NieR Replicant Save Editor ready to use?
The Tool record is verified and declares an operational runtime. The page enables its input controls only when the declared engine module is loaded in the current build.
Does processing stay in the browser?
Yes for this declared mode. The loaded runtime processes the explicit input in the browser; Tool-specific privacy notes describe the exact scope and limits.
Should I keep the original file?
Yes. Keep an untouched source file until any generated output has been validated.
What if my version is not listed?
Treat unlisted versions as unverified. Do not assume two releases use identical save layouts, checksums, signing, or serialization.

Related tools

Continue with the same tool family.

Only index-ready verified records from the same Tool Family are shown here.

Related guides

Read the guidance connected to this tool.

Only reviewed, index-ready Guides that explicitly reference this Tool are included.