Modding & Load Order / Starfield / Creation Engine 2

Starfield: Fixing Creations Load Order and StarfieldCustom.ini

A safe Creations load-order and StarfieldCustom.ini workflow for Starfield mods after the latest patch.

Official Steam Store header artwork for Starfield.

Starfield’s Creations platform made mod installation easier but did not remove load-order or archive-invalidation failures. The game can start cleanly and still ignore every custom asset.

Fixing Creations Load Order and StarfieldCustom.ini

Verified field fix

The shortest safe order for this issue:

  1. Update the mod manager and verify each Creation supports the current game build.
  2. Back up StarfieldCustom.ini before adding archive invalidation or plugin lines.
  3. Test with only one content creation enabled, then add groups of two.

Archive invalidation is still a prerequisite

Loose-file mods need the archive settings in StarfieldCustom.ini, but a malformed INI can crash the game before the menu. Create the file from a known-good example, back it up, and keep only the lines the mod author documents.

%USERPROFILE%/Documents/My Games/Starfield/StarfieldCustom.ini
[Archive]
bInvalidateOlderFiles=1
sResourceDataDirsFinal=

[General]
; Keep only documented settings here.
; A malformed entry can prevent the game from starting.
Back up the file first. Some Creations manage their own archive paths; do not duplicate them manually.

Creations still have dependencies

A creation can depend on another creation or a game update. Read the requirement list and load shared libraries first. If the Creations menu reports a conflict, remove the newer addition rather than letting the game shuffle a broken set.

Field notes before you change the build

A Starfield mod list is a dependency graph, not a popularity ranking. Confirm that the loader and shared frameworks match the current game build before sorting content mods. A missing dependency can look exactly like a bad load order.

Back up the active profile and a save before disabling anything. If the game starts cleanly with frameworks only, add content back in small batches and test the same menu, dialogue, or world load after each one.

  • Do not mix two mod-manager deployments over the same game folder.
  • Do not delete a content mod without testing a copied save first.
  • Do not paste a load order from a different game build and expect it to be stable.

Check it before you keep it

Launch to the title screen before loading a modded save

0 / 5 complete

Keep a known-good profile

Export the working mod list before the next patch. A short, documented stack is easier to repair than a folder full of files whose versions nobody recorded.

The line to keep

Start with the title screen, then the save. A clean INI and a short dependency chain are worth more than a full modlist.

Did this fix work on Patch 1.15.222 — Creations and stability?

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

Verified against 1.15.222 — Creations and stability. Votes are local-only telemetry.

Starfield: bench questions

2 answers
Do I need StarfieldCustom.ini for Creations?
Only for loose-file mods that require archive invalidation. Creations may manage their own assets, so follow the author’s instructions.
Why does my custom asset show as missing?
The mod may not be deployed, the archive rewrite may be disabled, or another creation may override the same record.
Filed under

Modding & Load Order

Patch tested: 1.15.222 — Creations and stability

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.