Identify the problem before you edit anything

Not every “save issue” is the same problem. The editor can help with several different classes of failure, but the fix path changes depending on what is actually broken.

Start by separating the issue into one of these buckets:

  • the editor will not open or cannot find the save,
  • the save loads but the wrong file was edited,
  • a reward, unlock or account flag is missing,
  • a quest or progress state is stuck,
  • a deep field needs JSON work because the normal UI does not expose it.

That small classification step saves a lot of wasted editing.

Rule out path and compatibility mistakes first

Sometimes the save is fine and the problem is somewhere else:

  • the wrong folder was opened,
  • the Game Pass path changed,
  • the JAR path needs Java,
  • or the editor build is behind the newest patch content.

Check these pages before you go deeper:

Use the least invasive editor path first

If a normal screen in the editor exposes the system you need, use that first. Do not jump straight into JSON because it feels more powerful.

For example:

  • reward problems often belong in the account and reward sections,
  • unlock questions can live in discovery or account-oriented areas,
  • inventory issues should start in the visual inventory UI,
  • and only narrow edge cases should begin in raw JSON.

That order gives you a clearer rollback path when something does not behave the way you expected.

Change one class of data at a time

Do not repair a stuck mission, add rewards, resize inventories and rewrite JSON in the same session if your real goal is only to fix one broken state.

The safe troubleshooting rhythm is:

  1. make one targeted change,
  2. save,
  3. load the game,
  4. verify the result,
  5. continue only if the first change behaved correctly.

This matters even more when you are working around a recent game update or an unusual platform path.

Move to raw JSON only when the normal screens stop helping

There are real cases where JSON is the only practical route. Mission repair and edge-case state fixes sometimes end up there. But JSON should be treated like a deliberate escalation, not like the starting point.

If you reach that stage, use Edit raw JSON safely and keep the session narrow.

Know when it is time to check issue reports

If you can reproduce the problem consistently, you are using the correct save, and the issue still looks tied to a fresh patch, new reward mapping or a changed save-path format, it is time to read or file an issue instead of inventing more local fixes.

That is especially true for:

  • new expedition rewards,
  • recent Game Pass path changes,
  • brand-new game systems,
  • or missing fields right after a patch.

The right final stop is usually GitHub Issues.