Skip to content

Help

Troubleshooting

What to do when the plugin can't connect, a run gets stuck, credits run out or an undo fails.

Most problems have a quick fix. Find the symptom below; if nothing here helps, email support@studpilot.app with the project name and roughly when it happened.

The plugin can't connect#

When you click Connect and the project does not find Studio:

  1. Is the place open? Studio must have a place open, not just the start page.
  2. Is the plugin installed and enabled? Open Plugins → Manage Plugins in Studio. StudPilot should be listed and switched on. If it is not there, install it.
  3. Are you signed in to the same account? The plugin connects to the account you are signed in with on studpilot.app.
  4. Is Studio in Play or Run mode? Stop the playtest; the plugin does not connect during one.
  5. Restart Studio. Plugins load when Studio starts, so a freshly installed or updated plugin needs a restart.

HTTP requests are disabled#

If the plugin says it cannot reach StudPilot, Studio is probably blocking its HTTP permission. This happens if you clicked Deny on the first prompt.

  1. In Studio, open Plugins → Manage Plugins.
  2. Find StudPilot and open its permissions.
  3. Allow HTTP requests to studpilot.app.
  4. Click Connect again in the project.

Your game's own Allow HTTP Requests setting (Game Settings → Security) is unrelated and does not need to be on. If you are on a school or work network, a firewall may also block the connection; try another network to check.

The agent seems stuck#

A long run can spend a while reading a big place or working through many changes, and the chat shows each step as it happens. If nothing new has appeared for a few minutes:

  • Check Studio is still connected. If Studio disconnected, the agent cannot continue changing the place. Reconnect and ask it to continue.
  • Reload the page. The run continues on StudPilot's side while the page is closed, and the chat catches up when you return.
  • Stop it. Click Stop, then send the request again, more specifically if you can. Changes made so far stay in the place and can be undone.

The agent built the wrong thing#

Undo the run, then send the request again with the detail that was missing. See Writing good requests. If it was close, reply in the same chat and say what to change instead.

Out of credits#

The app tells you when your credits reset: daily allowances at midnight UTC, monthly limits on the 1st. Everything except new requests keeps working. If you see "StudPilot has reached today's shared building capacity", it is the service-wide limit, not yours, and it resets at midnight UTC. See Credits and limits.

A run cost more than expected#

Runs are charged for the work they did, so a broad request on a large place can cost more than the typical figures. A run that failed without changing your place gives its credits back automatically. To spend less, make requests specific and name what they touch.

Undo failed#

If undoing a run does not go through:

  • Check Studio is connected to the same place the run was made in. Undo restores through the plugin, so it needs the place open and connected.
  • Stop any playtest. Undo cannot change the place while Studio is in Play or Run mode.
  • Try again. If the connection dropped part-way, a second attempt usually completes it.
  • Use Studio's undo. The agent's changes are also normal Studio undo steps, so Ctrl+Z (Cmd+Z) can take them back one at a time, as long as Studio has not been closed since.

If it still fails, do not keep editing that area by hand; email support with the project name and the run, and we will help restore it.

Something else#

Email support@studpilot.app. Include the project name, what you asked for, what happened and roughly when. Never include a password or card number.