Spherewright

Spherewright

Chinese · English

Chinese

Spherewright connects external AI agents to the "Dyson Sphere Project" through MCP. It provides structured observation and bounded action, while allowing collection, handcrafting, research, construction, energy consumption, flight, logistics and preservation to continue to adhere to the normal mechanics of the game.

This package contains Spherewright 0.3.3 for Windows x64:

• BepInEx 5 Plugin loaded by "Dyson Sphere Project";
• Single file self-contained Spherewright.Mcp.exe for external Agent applications to connect to;
• The opening mobile playbook provided by MCP synchronization.

Users do not need a source code repository or .NET SDK.

Support scope

• "Dyson Sphere Project" 0.10.34.28529
• BepInEx 5.4.17
• Windows x64
• Single player peaceful mode (turn off black fog/combat)
• Arbitrary sandbox settings and resource multipliers; they are reported but do not expand the Spherewright's action capabilities

v0.3.3 has been verified separately on this machine: creating a new non-sandbox 1× world, importing a non-sandbox 100× world, and importing a sandbox 1× world. All three complete the first building through normal actions and save. Spherewright does not invoke sandbox tools, nor does it inject items, energy, or technology. Black Mist/Combat, Multiplayer or Nebula, as well as extensive third-party mod compatibility are not supported at this time.

Install and connect MCP

• Install Spherewright and its BepInEx dependencies through Mod Manager or r2modman.
• Launch "Dyson Sphere Project" once from the selected Mod profile and let the Plugin generate the configuration and protected runtime description files.
• Find BepInEx/plugins/Arcueid_77-Spherewright/Spherewright.Mcp.exe in the profile.
• Register this EXE as the local stdio MCP Server in the external Agent application. Do not pass runtime description files, authentication tokens, or archive names on the command line.
• Spherewright is read-only by default. When you need to operate the game, set Safety.AllowWrites=true in BepInEx/config/dev.spherewright.bridge.cfg of the profile, and then restart the game.

Send directly to Agent

Connect to the Spherewright MCP and first read the current game status and built-in instructions. If there is a protected renewal entrance, continue, otherwise create a new file; if the current file is an old file that I manually loaded, prepare to import first and wait for my clear confirmation. Only advance according to the normal game mechanism, automatically recover when encountering a jam or power shortage, and save and report normally every time a production line is completed.

Start from new file

Leave the game in the idle main menu, enable Safety.AllowWrites and tell the Agent to create a new Spherewright file. Spherewright creates peaceful, non-sandbox, 1× worlds through the normal new process, with the internal name Spherewright_New_*. The Agent should read the opening-movement playbook issued with the MCP before taking its first action.

Load old files and continue playing

Enable both Safety.AllowWrites=true and Safety.AllowUserSaveImport=true in the configuration, restart the game, and then let the player manually load the target and peaceful single-player save in the game menu. Let the Agent prepare for the import; it will first display instructions for side-effect-free preflight and wait for your explicit confirmation in a follow-up message. After confirmation, Spherewright will only create Spherewright_Imported_* independent copies through the normal save API, and the original files will not be overwritten, renamed, deleted, or become a recovery target. The Journal starts from the import point and does not re-create the previous first event; players and Agents will continue in the copy in the future.

Downloads, Evidence and Licensing

• GitHub Releases: Manual package installation, checksums, and rollback instructions
• v0.3.2: Sol Max and Luna Max dual model black box acceptance compariso …