Starfield.exe directly (e.g., a non-SFSE achievement enabler), rendering the game incompatible or partially incompatible with SFSE plugins that employ signature or byte array searchessfse_loader.exe) (whenever you launch the game, you have to do so with this loader)sfse_loader.exe) (whenever you launch the game, you have to do so with this loader)plugins.txt)StarfieldCustom.ini[Archive]
bInvalidateOlderFiles=1
sResourceDataDirsFinal=
enable_plugin_management to true in the Starfield Support plugin optionsIf you have not already done so, disable the "Hide extensions for known file types" filter in File Explorer.
plugin.txt file (the correct file name is plugins.txt)plugin.txt.txt file (the correct file name is plugins.txt)plugins.txt.txt file (the correct file name is plugins.txt)plugins..txt file (the correct file name is plugins.txt)plugins.txt file (the game cannot guess what you mean; the file names must be exact)plugins.txt file to a location where the game cannot find the fileplugins.txt file to a location outside %LOCALAPPDATA%\Starfieldplugins.txt filesTestFile entries with the sTestFile key in the plugins.txt filesStartingCjavascript-event-strippedbat line into StarfieldCustom.ini (the correct key is sStartingConsoleCommand but a Nexus bug obfuscates the key in comments)Plugins.txt Enabler and use of
sTestFileare mutually exclusive!plugins.txtis used by all BGS games.sTestFileis not for end users to load mods and will break the game.
sTestFile* keys from StarfieldCustom.inisTestFile* keys from INI files distributed by some modsThese are NOT errors, although some people confidently (and wrongly) say otherwise:
# symbol at the top of the plugins.txt file (the # symbol denotes a comment, which is skipped by the parser; this line does nothing)sStartingConsoleCommand in StarfieldCustom.ini (the game works with both plugins.txt and console commands)