Skip to content

Using StudPilot

Writing good requests

What to put in a request so the agent gets it right the first time.

The agent understands plain language, and a single sentence is often enough. But the request is the only thing it knows about what you have in your head, so a little detail goes a long way. The expensive request is almost always the one that had to be sent twice.

Say what it is for#

Describe the result and who it is for, not just the object. "A shop" could be a dozen things. "A shop where players spend coins on three speed upgrades, opened from a button on the left of the screen" is one thing.

Point at what exists#

If the request touches something already in your place, name it. The agent can read your place and will look, but a name removes the guesswork.

  • "The door in Workspace.Lobby" rather than "the door".
  • "The Coins leaderstat" rather than "the money".
  • "The script that spawns enemies" works too; the agent will search for it.

You can also select something in Studio before you send. The agent sees the current selection, so "make the selected parts glass" does what it says.

Give the numbers you care about#

Timings, sizes, prices, colours, limits. "A 30 second intermission", "a 4 by 4 stud grid", "costs 250 coins". Where you leave a number out, the agent picks a sensible default and tells you what it picked.

One goal per message#

A request can be big ("a full round system"), but keep it to one goal. Five unrelated changes in one message are harder to review and harder to undo separately. Send them one after another instead; each run gets its own checkpoint.

Describe behaviour, not code#

You do not need to know how to script. "When a player touches the lava they respawn at the last checkpoint they reached" is a better request than a half-remembered API. If you do know what you want technically, say so: "use a RemoteEvent, validate on the server".

Examples#

VagueBetter
Make a menu.Add a main menu with Play, Settings and Credits buttons. Play closes the menu and spawns the player.
Add enemies.Add a zombie that walks toward the nearest player and deals 10 damage a second on contact. Spawn three at the points in Workspace.ZombieSpawns.
Fix my game.Players say they lose their coins when they rejoin. Check how Coins is saved and loaded and fix it.
Make it look nicer.Change the lobby lighting to late afternoon: warm sun, soft shadows, light fog in the distance.

When the result is not right#

Reply in the same chat and say what is off: "the button is too small on phones", "it should only trigger once per player". The agent keeps the context of the run. If the result is far off, undo the run and ask again with the detail you now know was missing.