Playing with a companion

What the companion is

The optional companion bridge lets your existing assistant control a separate physical character in the same local world. The game does not launch a replacement language model. The character has its own saved inventory, health, food, hydration, breath, tool durability, position and small game journal.

The bridge supports movement, navigation, gathering, mining, placing, crafting, food and drink, item transfer, combat and observation. Survival actions need actual resources, reach and tool durability. It is one companion slot, not network multiplayer.

Connect

1. Keep the game installed with its integration files. Optional cloud control needs Python 3, ChatGPT/custom-MCP access and the HTTPS helper; normal solo play remains offline.
2. Run Connect your Dot.sh. It starts the scoped local connection service and prints an HTTPS /mcp address and pairing information.
3. In ChatGPT's plugin/custom-MCP controls, add that endpoint with OAuth and follow the pairing flow. The local pairing code is the one printed by the helper or shown in the game's J panel.
4. Use the same existing assistant conversation and a stable saved game identity. Ask it to read the game rules, join the world and choose a useful purpose.
5. Leave the helper running while connected. Turn off the companion link locally to revoke external game control.

No OpenAI API key is needed for this bridge. Do not publish pairing codes or connection credentials in a wiki, game book or chat log. Restarting the entire temporary HTTPS helper changes its address; a stable user-managed HTTPS endpoint avoids that limitation.

Useful ways to ask for help

Ask for a concrete local task: “Bring six natural logs without breaking my build,” “Walk to this workshop and stop beside the deck,” or “Check your food and water, then help me explore that coast.” The assistant should observe actual results and adjust when an action fails.

The current default activity is Observe. Explore requires a destination and reason; Patrol requires deliberately chosen waypoints. Gather uses real tools, stops at its quantity goal and avoids player-edited blocks. Hold stops voluntary movement while optional survival/defense responses can remain active. An empty wandering loop is not the current behavior.

Menus and stopping

The current game keeps its world running while Escape, settings, J, inventory and other ordinary menus are open. Your body is not protected by the menu, and a connected companion may continue acting. This is also the current solo-world behavior; older companion guides describe a different pause policy.

Choose Save & return to title or save and close the game to stop this world's simulation. The legacy /freeze_all command opens the world menu but does not freeze it. Disconnecting disables external control and retains the saved character; it is not a world-pause command. Releasing the companion slot removes that character and game notes and drops its possessions for recovery.

Boundaries

The assistant can receive compact observations, bounded visible scene details, sound cues and optional images from its own eyes. It does not automatically receive all private ChatGPT history or every memory. Game notes are for game facts and plans. The bridge does not grant arbitrary terminal, file, email or account access.

Saved experience stores measured attempts and skill summaries. It does not fine-tune the assistant's underlying model. Cloud reasoning, network access, account limits and scheduling still affect response time; local movement support is not a guarantee of expert or instant combat decisions.