1. Back up before you edit

This is the rule that matters more than every reassuring sentence on the internet. The project supports backup-aware use for a reason.

Keep a clean rollback copy before you:

  • unlock rewards,
  • rewrite inventory data,
  • change location fields,
  • or touch raw JSON.

2. Open the correct save first

An edit can look “broken” when the wrong save was changed. Before you do anything more interesting than a test edit, confirm the folder and save slot really belong to the playthrough you mean to change.

If you are not sure, use Find your save files.

3. Use the normal editor screens before raw JSON

If the editor already exposes the system you need, start there. The visual UI is easier to reason about, easier to reverse and much easier to test cleanly than a blind JSON session.

JSON should be the escalation path, not the default.

4. Make one change, then validate it in game

Do not queue ten edits and hope they all work together. The safe rhythm is:

  1. change one logical block,
  2. save,
  3. load the game,
  4. confirm the result,
  5. continue only if that result is correct.

This is what keeps a narrow task narrow.

5. Treat new patch content as version-sensitive

Brand-new items, reward IDs and certain new systems can lag after a large game update. The editor can still be extremely useful while one narrow part of the newest content is not fully mapped yet.

That is why you should check Compatibility and changelog when the specific thing you want belongs to the latest patch cycle.

6. Stop when the problem becomes unclear

If you no longer know which field controls the result you want, or if the data structure looks different from what you expected, stop and verify before you keep going.

At that point, the right next move is usually: