Silksong Advanced Mode Save Editing Guide

Quick Edit vs Popular Actions vs Advanced Mode

Before opening Advanced Mode

1. Close Silksong so the game is not writing the slot while you inspect it.
2. Confirm the filename matches the intended slot: user1.dat through user4.dat.
3. Use Download Original Backup and keep that untouched file outside the live save folder.
4. Write down the symptom you are trying to solve and change only evidence related to it.
5. Keep the game version in mind when comparing a community post or older backup.

A backup is more than a precaution. It creates a known-good comparison point. If the edited file loads but progression behaves strangely, you can restore the exact bytes you started with instead of trying to reverse several guesses.

How to search

1. Upload the original userX.dat and download an original backup.
2. Open Advanced Mode after the Popular Actions cards.
3. Search an item name, field name, or visible value. Search is case-insensitive.
4. Use Previous and Next to move through highlighted matches.
5. Read the surrounding object before changing anything.

Search is case-insensitive and checks visible item names, field names, and values. The match counter tells you how many results exist, while Previous and Next move through them without relying on the browser's page search. Matching objects expand automatically so the highlighted value is shown in context.

Start with the language used by the save, not only the wording shown in the game UI. A resource may live under a legacy or internal name—Rosaries, for example, use geo. When you do not know the field, search a nearby item name from a verified guide before trying broad terms such astrue or 0.

Common data types

Boolean

true or false, often used for an unlocked or completed state.

Number

A count, mode, level, or progress value. The valid range depends on the field.

String

Text such as an item Name or game version.

Object / array

Grouped values. Do not delete brackets, commas, or neighboring entries.

Read the whole object, not one matching line

A match is a location hint, not a complete explanation. Item records can combine fields such as Name, IsUnlocked,HasBeenSeen, and AmountLeft. Progression can also be represented by a counter plus separate acquisition flags. Changing one value may update the visible number while leaving the underlying state inconsistent.

{
  "Name": "Example Item",
  "Data": {
    "IsUnlocked": true,
    "HasBeenSeen": true,
    "AmountLeft": 1
  }
}

Do not copy this example as a fix. It only shows why the surrounding keys matter. A safe edit needs a field path, a current value, an expected value, and evidence that the same relationship applies to the uploaded game version.

Verified example: Rosaries

Quick Edit writes Rosaries to playerData.geo. In Advanced Mode, searching geo locates the same numeric field. Change only the number and keep the JSON punctuation intact.

"geo": 250

This is a good Advanced Mode example because the same field is already used by the mature Quick Edit control. You can compare both views and see that only a numeric resource value changes. If Quick Edit supports the task, prefer it; Advanced Mode is useful here for learning how search and paths work.

Validate one change before making another

1. Record the original field path and value.
2. Make one small edit and generate a separate downloaded file.
3. Keep the original filename so the slot remains clear.
4. With Silksong closed, place the edited copy in the matching save folder.
5. Open the slot and check the target value, location, inventory, and progression.
6. Save normally, close the game, and open it again to confirm the game can rewrite the file.

The second launch matters. A file can appear correct once but fail after the game writes new state. If anything unrelated changes, stop and restore the original backup before testing a different idea.

When Advanced Search finds no results

A missing result does not prove the feature is absent or broken. Some entries do not appear until the player has encountered or collected them, different builds may use different names, and the relevant state may be stored in a neighboring object. Confirm the correct slot and game version, try the exact item name, then stop if the only next step would be inventing a flag.

Edits to avoid without complete evidence

• Deleting objects, arrays, punctuation, or unknown fields.
• Changing every matching flag because one community reply reported success.
• Forcing quest, boss, travel, or reward state before its related game events occur.
• Applying a release-build workaround to a later save without checking the version.
• Stacking several edits before launching the game and verifying the first one.

Advanced Mode FAQ

Does opening Advanced Mode change my save?

No. Opening and searching the decoded data is read-only. A new file is created only after you make a change and choose the download action.

Why should I use Quick Edit when the same field is searchable?

Quick Edit applies validation and presents a player-facing control for a known field. It reduces the chance of editing a similarly named value or damaging JSON structure.

Can I use a field value from Reddit or Steam?

Treat a community post as a case report, not a universal schema. Match the symptom, field path, current value, game version, and all related flags before deciding whether the report applies to your save.