Save Editors
Change only the already-verified Steam account ID field.
01 / Tool workbench
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.
No output has been built in this session.
This Tool exposes one field that an earlier verified writer already edits safely. It does not introduce a new offset, checksum rule, container assumption or platform variant.
The existing source parser opens the original first; the output must reopen successfully and non-focused editable fields must remain equal.
Processing stays local in the browser and the source file is never modified in place.
02 / Compatibility
Compatibility fields are intentionally explicit. Missing values stay unclaimed rather than being filled with generic assumptions.
Accepted extensions
No extension list is recorded.
Platforms
PC
Supported versions / editions
Exactly the same save family already accepted by sekiro-pc-sl2-steamid-v1.
Input constraints
Input must satisfy the already-verified sekiro-pc-sl2-steamid-v1 parser and stay within the permanent 16 MiB local ceiling.
Known limitations
Focused existing-authority editor. No new offset or field authority is introduced.
Output / result
Separate validated edited copy; source remains untouched.
03 / Instructions
File-oriented workflows start with an untouched original. Tool-specific instructions add only details documented for this utility.
Preserve an untouched copy before creating or transforming binary output.
Match the file size, format, platform, and version to the support information on this page.
Use the runtime only when the page reports that its declared engine is loaded.
Compare or test the result before replacing any working source file.
Tool-specific steps
Back up the save, choose it locally, and let SaveEditor run the existing verified source parser before this Tool becomes available.
04 / Privacy and processing
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
Runtime state
Tool-specific privacy notes
Browser-local processing only. No fetch, XMLHttpRequest, WebSocket, sendBeacon or cloud-account request is used.
05 / Troubleshooting
A rejection can indicate an unsupported size, format, version, platform, or byte sequence. Preserve the original and correct the input instead of bypassing validation.
Re-check the documented input type and browser size limit before retrying.
A generic converter does not imply support for every game-specific container, signing scheme, or serialization format.
Return to the untouched source instead of repeatedly processing a damaged or partially transformed file.
Known Tool issues
A refusal means the existing source parser or writer refused the file/value. Phase 71 does not bypass those constraints.
06 / Verification
The verification date, method notes, and public references are kept separate from marketing language so compatibility can be reviewed over time.
Method notes
Verified as a narrow surface over existing parser/writer authority with source immutability, strict field allowlists for editors, deterministic receipts for read-only surfaces, malformed-input refusal and source/installable parity.
Public references
07 / FAQ
These answers are generated from the Tool record and current runtime state rather than generic compatibility promises.
Related tools
Only index-ready verified records from the same Tool Family are shown here.