Where Does Dyson Sphere Program Store Mods?
Dyson Sphere Program mods load through BepInEx from a plugins folder in the game directory. Managers handle the désormais large scene.
Last updated
Dyson Sphere Program's Unity foundation means BepInEx plugins in the game directory, and the scene grew large enough that managers beat manual installs. Interface overhauls, blueprint tools, and production planners dominate. The plugins folder fills fast once automation fever sets in.
Simulation hooks make patch week interesting: recipe and balance mods break hardest, interface mods lightest. Update the loader, then mods, then load the factory. Keep megabase saves backed up before mod experiments, since a thousand hour galaxy deserves more caution than a test world.
Where Dyson Sphere Program stores this, by platform
[Steam]\steamapps\common\Dyson Sphere Program\BepInEx\plugins
Plugin dll files here loaded at startup. Prefer a manager once the set grows. Update loader before mods after game patches.
Frequently asked questions
All mods broke after an update. What now?
Update BepInEx first, then the mods. Factory game patches touch the simulation code mods hook into, so wholesale breakage after updates is normal. The manager shows which mods lag behind.
Do mods work in multiplayer?
Yes for interface and blueprint mods, no for anything touching recipes or balance. Formula changes desync multiplayer determinism checks, so keep those to solo galaxies.
Notice an outdated path? Let us know.