Plugins.txt Enabler

Requirements


Starfield Script Extender for Steam editions or an ASI loader (Install tutorial) for Game Pass editions.


Installation


Install with your mod manager of choice, e.g. Mod Organizer 2, Vortex, or...


For manual SFSE installs, place SFPluginsTxtEnabler.dll in the corresponding Starfield\Data\SFSE\Plugins folder. An example path is: C:\steamapps\common\Starfield\Data\SFSE\Plugins\SFPluginsTxtEnabler.dll


For manual ASI loader installs, place SFPluginsTxtEnabler.asi in the game root directory next to Starfield.exe. An example path is: C:\XboxGames\Starfield\Content\SFPluginsTxtEnabler.asi


How do I load custom ESP/ESL/ESM plugins?


Some mod managers will automatically handle the setup portion. However, in the event you aren't using a mod manager, you'll have to manually create and edit plugins.txt with notepad as explained below.


Plugins.txt must be created in Starfield's local AppData folder. This is usually: C:\Users\<Your Username>\AppData\Local\Starfield\Plugins.txt


Plugins.txt must first contain a # line and then asterisked lines for each ESP, ESL, or ESM you want to load:
[quote]# This file is used by Starfield to keep track of your downloaded content. (You HAVE to keep a # on the first line here)
*MySpecialMod.esp
*AnotherMod.esl
*ShipStorage.esp
*Custom Plugin With Spaces.esm
*UnlimitedSprint.esp
*YetAnotherSpecialMod.esm[/quote]
Save plugins.txt and launch the game. Note that this isn't a tutorial on how to organize your load order. Starfield has near-identical plugin loading functionality compared to Fallout 4 and most guides apply. See LOOT's introduction for more information.


Logs


Limited diagnostic information is logged to SFPluginsTxtEnabler.log in Documents\My Games\Starfield\SFSE\Logs for SFSE and in Documents\My Games\Starfield\Logs for ASI loaders.


Warning


Starfield does not officially support loading custom ESP/ESL/ESM plugin files. Files created outside of Bethesda's editor may be broken in subtle ways. Use with caution.