Modding & Load Order / Death Stranding 2: On The Beach / Decima

Death Stranding 2: On The Beach: Safe Mod Install, Load Order & Post-Patch Conflict Recovery

Install mods on Death Stranding 2: On The Beach without breaking the build: framework order, script conflicts after a patch, and a clean rollback path that keeps your saves intact.

Cover artwork for Death Stranding 2: On The Beach on the GamePathHub field file.

Mods are a dependency graph, not a folder

Death Stranding 2: On The Beach loads content in a defined order. A mod that overwrites a script another mod depends on will not fail immediately — it fails after the next patch, or when a specific level loads. That delayed failure is why “it worked yesterday” is not evidence.

The safe install sequence

A clean Death Stranding 2: On The Beach mod stack

Rollback-safe

Build the stack so you can remove any single layer without losing the profile.

  1. Copy the whole save profile and the configuration folder to a dated backup.
  2. Install the framework or loader first, at the exact version the mod author pins.
  3. Add mods in small groups and launch after each group.
  4. Keep a text file listing mod name, version, and source. A screenshot of a mod manager is not a rollback plan.
  5. After a game patch, disable everything, launch vanilla once, then re-enable the framework before the content mods.

Where the configuration lives

%LOCALAPPDATA%\KojimaProductions\DeathStranding2\
[Display]
WindowMode=Fullscreen
VSync=0
MaxFPS=0

[Graphics]
UpscalingQuality=Quality
Decima updates can reset the display block. Re-check after every patch rather than assuming the file persisted.

Post-patch conflicts have a signature

A script mismatch usually produces a load-time error naming a specific file. A framework mismatch usually produces a silent failure: the game boots, the mod menu is missing, and nothing else is wrong. A load-order conflict can be intermittent and save-specific.

Read the actual error text before changing load order. Reordering a stack to fix a missing framework turns one correct diagnosis into three wrong ones.

Ordering rules that survive patches

  • Framework or loader before any content that declares it as a dependency.
  • Asset replacements before gameplay overhauls that reference those assets.
  • Localisation files last if a patch ships new strings.
  • One major overhaul at a time. Two systems that both rewrite the same table cannot both win.

Verify the stack

Mod stack verification for Death Stranding 2: On The Beach

0 / 5 complete

The line to keep

A mod stack you can rebuild from a text file is worth more than a beautiful stack you cannot diagnose. Decima changes its asset paths between major patches; the text file is the part that survives.

Did this fix work on Patch 1.0.8 — Decima PC performance patch?

One click. No account. Your vote is stored in this browser and de-duplicated per file.

Verified against 1.0.8 — Decima PC performance patch. Votes are local-only telemetry.

Death Stranding 2: On The Beach: bench questions

2 answers
Is this Death Stranding 2: On The Beach fix safe for my current save?
Yes when you back up the profile first. The routine changes configuration and caches, not the save file itself. If a fix edits an active save, the file path and the backup step are called out in the guide.
How do I know the modding & load order fix worked?
Repeat the same action that failed before the change and compare like for like. For crashes, that means a cold launch. For frame pacing, that means the same route with a frame-time capture. A fix you cannot re-test is not verified.
Filed under

Modding & Load Order

Patch tested: 1.0.8 — Decima PC performance patch

This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.

Continue the file stack Game hub ↗
Index: Pagefind Type a game, symptom, or tool

    ↑↓ navigate ↵ open GPH / COMMAND SEARCH
    Local profile / hardware telemetry

    My rig

    Stored only in this browser. Game hubs use it to estimate whether your build clears the recommended specification — nothing is uploaded.

    No profile yet. Save once and the masthead, spec pages, and tool prefills follow.

    Telemetry never leaves this browser.