Starfield Toolkit

A Windows GUI for managing Bethesda Creations — load order, updates, rule books, and Fast Lane compatibility, without ever touching your game files.

File locations

Where the toolkit reads from, and where it writes to. Paths use typical Windows conventions; substitute your own username.

Game files the tool reads

Starfield's own files live under %LOCALAPPDATA%\Starfield\ (i.e. C:\Users\<you>\AppData\Local\Starfield\). Bethesda writes these; the toolkit only touches Plugins.txt.

FilePathAccess
Plugins.txt%LOCALAPPDATA%\Starfield\Plugins.txtRead + write (on Apply only)
ContentCatalog.txt%LOCALAPPDATA%\Starfield\ContentCatalog.txtRead only
Plugin files<Steam>\steamapps\common\Starfield\Data\*.esm, *.espRead only (TES4 header only)
Important Plugins.txt is the only game file the toolkit writes to, and only when you explicitly Apply a load-order change. Plugin files themselves are never modified.

Toolkit data directory

The toolkit stores its own data under %APPDATA%\StarfieldToolkit\ (Roaming — i.e. C:\Users\<you>\AppData\Roaming\StarfieldToolkit\). Paste %APPDATA%\StarfieldToolkit into Explorer's address bar to jump there.

PathContents
config.jsonApp preferences (game path, window layout, rule-book registry, etc.).
creations_catalogue.jsonOffline creations catalogue (populated by the scraper tool; used by the description parser and Fast Lane baseline).
images\Cached creation thumbnails.
rules\Your user-authored rule books (JSON, one per file).

No log files, cache subtrees, or snapshot directory are created automatically. Load-order snapshots are saved only to the path you pick in the Save-Snapshot file dialog.

Bundled with the binary

Read-only, packed inside StarfieldToolkit.exe (extracted to a temp dir at launch via PyInstaller):

Clearing state