Manual / Volume One / Last revised April 2026

The field manual.

Everything you need to ship your first feature with Pisces. Read top to bottom in twenty minutes, or jump to the section that's biting you. The agent does the typing — you do the deciding.

1. Install the bridge.

Pisces lives in two places: a web interface where you chat, and a Studio plugin that acts as the bridge. You need both connected to do anything.

  1. Get your API key. Sign in at piscesofficial.com and copy the key from your dashboard.
  2. Install the plugin from the Roblox Creator Marketplace. Click this link and hit Install. Auto-updates push themselves — no .rbxmx wrangling.
  3. Connect. In Studio, open the Pisces · Web Connector panel from the toolbar. Paste your key. Click Connect.
  4. Accept the two prompts. Studio asks for HTTP requests and script editing — both are required. More about permissions.
You'll see Connected · Baseplate (or whatever place you have open) at the top of the web interface within two seconds. If it stays Disconnected for more than five, see troubleshooting.

2. Your first chat.

Open piscesofficial.com in your browser, sign in, and the chat is ready. Try one of these, then watch what the agent does:

  • "Make me a sword that does 25 damage and has a 0.6s cooldown."
  • "Add a coin pickup system. Coins persist across sessions."
  • "Walk me through what's in this game and what looks broken."

Pisces will plan what it's about to build, then emit tool calls — script creates, edits, property changes — that show up in your tree in real time. Each change is its own card with a red/green diff so you can see exactly what landed.

3. Editing existing scripts.

The model prefers edit_script for any change to existing logic. Edits are content-anchored, not line-numbered, which means they survive renames, formatter passes, and concurrent edits from you.

// User: "Bump the seahorse hunt day from 1 to 2."
// Pisces:
edit_script(
  target = "ServerScriptService.SeahorseAI.Brain",
  old_text = "local START_HUNT_DAY = 1",
  new_text = "local START_HUNT_DAY = 2"
)

If the anchor doesn't match (you renamed it, you reformatted), Pisces falls through nine progressively-relaxed matchers — line-trimmed, whitespace-tolerant, indent-flexible, and so on — before giving up and asking you to read the file fresh.

4. Undo & restore.

Three layers of undo, in order of preference. The fastest is right inside the chat — every action the agent takes shows up in the activity bar with an inline Undo control.

  1. Activity-bar Undo (web). Each tool call in piscesofficial.com's activity drawer has a one-click Undo button next to it — works for create_script, edit_script, fix_script, delete_script, create_part, property changes, and rig spawns. Pisces dispatches the inverse mutation directly through the plugin — no AI call, no PU cost. Also undoes the snapshot in Studio so Ctrl+Z stays in sync.
  2. Ctrl+Z in Studio. Every change Pisces makes is a single ChangeHistoryService entry. Press it once and the script (or instance) reverts. Use this when Studio is the focused window.
  3. Ask in chat. "Undo your last edit to NavConfig." Costs ~1 PU but works even when the snapshot is gone or you've made other changes since.

The activity bar is always docked at the bottom of the web prompt. Click any past action to expand its diff, or hit the small ↶ Undo control on the row. No keyboard shortcut needed.

Activity drawer · 3 recent actions
12:42 edit_script SeahorseAI.Brain · 1 line −0.7 PU ↶ Undo
12:38 create_script LightingController −0.4 PU ↶ Undo
12:34 grep_scripts "seahorse" · 4 hits −0.2 PU — read

5. Prompt patterns that work.

Pisces is fluent in plain English, but it works best when your request is concrete enough to test. Some shapes that consistently land:

Game systems

  • "Add a coin pickup system. Coins persist across sessions and show in a leaderstats GUI."
  • "Build a 3-stage round system: lobby → match (3 min) → intermission (15 s)."
  • "Make day pass 2× faster than default and turn into night smoothly."

UI / UX

  • "Add a health bar that follows the camera. Fades when full."
  • "Make a shop GUI with three items, scrollable, ESC to close."

Combat & abilities

  • "Sword tool with 25 damage, 0.6s cooldown, hit-particle."
  • "Double jump on space-press, with cooldown of 1.2s."
Tip. If you're modifying something that already exists (lighting, spawner, leaderstats), say so. Pisces will grep_scripts first and edit the existing system instead of building a duplicate.

6. Playtests.

After every build, Pisces calls playtest_verify with a goal and (when useful) a script of in-world actions. The result comes back as runtime errors, console output, and observed events. If it fails, Pisces reads the relevant script, patches the bug, and re-runs — up to three iterations before stopping to ask you.

7. Skills.

For domain-heavy work (combat moves, anime ability mechanics, advanced VFX, pathfinding) Pisces can load skill packs: focused expert templates baked from real production code. The agent decides when to load one. You don't need to invoke them manually.

8. Tool reference.

ToolWhat it doesPU
read_scriptsPull full source of one or more scripts.0.2–0.4
grep_scriptsText/regex search across the codebase.0.1–0.3
create_scriptMake a new Script, LocalScript, or ModuleScript.0.4
edit_scriptAnchor-based surgical edit.0.5–0.8
fix_scriptLine-range replacement (legacy fallback).0.5–0.8
delete_scriptRemove a script.0.2
set_propertySet one property on an instance.0.2
create_part / create_modelBuild geometry.0.3–0.6
playtest_verifyRun Play Solo with a goal.1.0–1.5
web_searchResearch a Roblox API or external concept.0.4
ask_questionPisces asks you to disambiguate.0.0

9. Troubleshooting.

"Plugin not connected"

The web tab can't see your Studio plugin. Open the Pisces · Web Connector panel in Studio and confirm the status dot is green. If not, click Connect again. If still red, check that HttpRequests are enabled (Studio prompts on first install).

"API Key Invalid"

Copy the key fresh from your dashboard — there's a copy button. Whitespace at the ends will fail.

"Insufficient PU"

You're out of daily allowance. Wait for the 00:00 UTC reset, top up with a one-time pack, or upgrade your plan. The dashboard shows your balance live.

"Connection Failed"

Network or backend hiccup. Refresh the web tab, then re-click Connect in Studio. If it persists for more than a minute, ping the maintainer through the dashboard's Message the developer form.

10. Pisces Units (PU).

PU is what every tool call spends. The number on each card is what that one action cost. Most chats land between 1 and 4 PU; large feature builds with playtests run 8–20 PU. Your plan's daily allowance refreshes at 00:00 UTC, and one-time top-up packs never expire.

PU is meant to track real cost — model tokens, plugin operations, playtest minutes. We tune the per-tool numbers monthly. The changelog notes any rate change.

Need a human?

Use the dashboard's Message the developer form — it lands directly in the maintainer's inbox. Response window is typically under 24h on weekdays.

Discord

Trade prompts, ask questions, and surface bugs in real time with other builders. Invite link is on your dashboard once you're signed in.