The Creation Kit distributed by Bethesda since June 2024 has reshuffled the modding landscape for Starfield. On Xbox, only mods published through the game’s integrated Creations system are accessible. On PC, two paths coexist: official Creations and Nexus mods, which are often more ambitious but reliant on SFSE (Starfield Script Extender) and its native plugins. Understanding this architecture before touching any files avoids most post-installation crashes.
SFSE and Address Library: the technical layer that guides often overlook
SFSE injects functions into the Starfield executable to allow advanced mods to modify behaviors that would otherwise be inaccessible. The problem: each game update alters the memory addresses used by SFSE.
The Address Library for SFSE Plugins plugin serves as an abstraction layer between SFSE and these addresses. When Bethesda releases a patch, Address Library must be updated before dependent mods can function again. We recommend systematically checking three items before restarting a modified game:
- Does the installed version of Starfield (visible in Steam or Xbox properties) match the one indicated on the SFSE page?
- Has Address Library been updated for this specific version of the game?
- Have the mods using SFSE published a compatibility note since the last patch?
If any of these three points are not verified, launch the game without SFSE-dependent mods. An unsynchronized mod can at best cause a desktop return, and at worst, silent save corruption.
For those wishing to install Starfield mods without going through SFSE, official Creations and some Nexus mods relying solely on .esm/.esp files remain functional after a patch, as they use Bethesda’s native plugin engine.
StarfieldCustom.ini file: configuration and common pitfalls on PC
Manually installing mods on PC involves creating or modifying the StarfieldCustom.ini file, located in the Documents/My Games/Starfield folder. This file allows the loading of external plugins by adding the [Archive] section with the line bInvalidateOlderFiles=1.
A common pitfall concerns Game Pass PC players. The StarfieldCustom.ini file can exist in two distinct locations: in the Xbox installation folder (C:XboxGamesStarfieldContent) and in the user folder. The user folder takes precedence. Modifying the wrong file means not modifying anything at all.
Accessing files on Game Pass PC
Windows Explorer blocks access to the installation folder of Game Pass games by default. To access it, open the Xbox app, right-click on Starfield, then Manage. The Files tab offers a Browse button that opens the protected directory.
This action is necessary for mods that replace textures or meshes directly in the game’s structure. Mods distributed as .zip or .7z archives must be extracted manually into the correct subfolder (Data, most often).
Bethesda Creations vs. Nexus Mods: choosing the right path according to your platform
On Xbox, the question does not arise: Creations is the only mod distribution channel. The free Creation Kit allows modders to publish their work on Bethesda.net, and console players access it through the in-game menu.
On PC, Nexus Mods remains the dominant platform for complex mods. The main difference lies in the allowed dependencies. Creations cannot include SFSE components or modify the executable. Nexus mods, on the other hand, do not have this restriction.
Paid mods and verified Creations
Bethesda offers a Verified Creator Program that allows the sale of Creations. Nexus Mods, for its part, has announced rules governing paid mods to preserve the free ecosystem. Free Nexus mods remain overwhelmingly predominant, but the coexistence of the two models deserves attention to avoid paying for a mod available for free elsewhere.
Protecting your Starfield saves before and during modding
No competing guide seriously addresses save management in a modded context. Removing a mod that adds scripts or objects to the game world can render a save unusable. The Creation Engine 2 records references to loaded plugins directly in the save file.
We recommend maintaining two distinct save profiles:
- A “vanilla” or lightly modded profile, without any SFSE mods, to retain access to Steam and Xbox achievements
- A profile dedicated to heavy modding, with a backup copy made before each addition or removal of a mod
- An external archive folder (outside the Starfield directory) to store manual saves, safe from automatic cleanup
The Achievement Enabler mod reactivates achievements even with loaded mods, but it relies on SFSE and therefore breaks with each game update. If achievements matter to you, the separate profile remains the most reliable method.
Plugin load order: what changes stability
Mod managers like Vortex or Mod Organizer 2 offer automatic sorting of the load order. In Starfield, the order in which .esm and .esp files are read by the engine determines which changes overwrite others.
A texture mod loaded after an interface mod generally does not conflict. However, two mods modifying the same data table (inventory, skills, NPCs) will produce unpredictable results if their order is not managed. Check compatibility notes on each Nexus page before activating a new plugin.
The stability of a modded installation depends less on the number of mods than on the rigor with which dependencies and load order are maintained. A setup of a few well-sorted mods runs better than a list of several dozen piled up without verification.
