Skip to content

Guides

Improve an existing game

Work on a place that already has years of scripts and builds in it.

StudPilot is not just for new places. Connect a game you have been working on for a long time and the agent works inside it, reading what is already there before it changes anything.

Start by asking#

On an unfamiliar or large place, a good first message is a question, not a change:

Give me an overview of how this game is put together: the main
systems, where their scripts are, and how data is saved.

The agent reads the place and explains it. Asking costs a fraction of a build and gives both of you a shared picture of the game.

Then change it#

Add a daily login reward to the existing Coins system: 25 Coins on
day one, going up by 25 each consecutive day up to day seven.

The agent builds on what exists. It finds the Coins system you already have and extends it, rather than creating a second one next to it.

Clean-up and refactoring#

  • "The shop scripts repeat the same purchase code five times. Merge them into one ModuleScript without changing behaviour."
  • "Find deprecated API calls in my scripts and replace them."
  • "Move all the remote events into one folder in ReplicatedStorage and update every script that uses them."

For changes that touch many scripts, the summary lists every script it edited, and the whole run undoes in one click.

Tips#

  • Be specific about what must not change: "keep the existing save format so players don't lose progress".
  • Work in steps: understand, then plan, then change. Ask the agent for a plan first if the change is large.
  • Keep publishing as you normally would. Checkpoints cover the agent's runs, not your whole history.