FAQ

Does this work with Nexus mods?

No. The toolkit targets players using Bethesda's official Creations store exclusively. If you install mods from Nexus or by hand, their plugin files will appear in your load order and the TES4 sorter will still do the right thing — but the toolkit's API-driven features (details, updates, Fast Lane check) only work for catalogued creations. Mixing is at your own risk and unsupported.

Linux? macOS?

Windows only. Starfield on Steam. There are no plans to port. The codebase is Python, so you might get it running on Proton with some grief, but we don't test that path.

Windows Defender / SmartScreen warns about the binary

The binary is unsigned. SmartScreen will show a "Windows protected your PC" banner on first launch — click More info, then Run anyway. The project source is open and the binary is built in GitHub Actions from a pinned commit; you can audit the build yourself, or build from source if you prefer.

Auto-Sort moved something I don't want moved

You have two tools: in the Diff dialog, reject that specific move with Ignore. For a permanent fix, create a user rule book that pins the creation where you want it — user rule books win against all other sorters at the same priority level. See Rule books.

Apply is refused with a TES4 error

Your current load order (after your per-item accepts/ignores) violates a master dependency. The dialog names the pair. Either accept the move that fixes the dependency, or investigate the plugin file — rarely, a broken plugin declares a master that isn't actually needed.

What about cycles?

If Auto-Sort detects a cycle (two creations each demanding to load after the other), it refuses to propose a partial ordering and shows the cycle in the diff. Disable one of the rules involved — usually a rule book — and retry.

Why is Fast Lane Check marking everything "Updated"?

Either your creations really have all been updated, or a previous toolkit release's baseline predates them. Make sure you're on the latest toolkit build.

Can I share my rule books?

Yes — they're plain JSON, machine-independent. Copy the files out of your user rule books directory and hand them to whoever needs them.

Where are the logs?

The current release doesn't persist logs to disk — the GUI writes diagnostics to stdout only. If you're running the packaged StarfieldToolkit.exe from a regular double-click, there's nothing to attach.

If you can reproduce the problem, re-launch from a terminal (Win+R → cmd, then "C:\path\to\StarfieldToolkit.exe") so stdout is visible, reproduce the bug, and paste the terminal output into the issue.

I'm paranoid — what does the tool actually write?

• To the game folder: only %LOCALAPPDATA%\Starfield\Plugins.txt, only on Apply.
• To %APPDATA%\StarfieldToolkit\: config.json, the offline creations catalogue, cached thumbnails, and any rule books you author.
• Never: plugin files, the game's Data folder, registry, or anything outside its own scope.