Best Practices

Superbullet works best when it can see your game and builds on what already exists. This is the workflow, in order.

The Workflow at a Glance

1. Connect Roblox Studio, so Superbullet works on your real project.
2. Start from a Library, or a game template, instead of from nothing.
3. Give useful context: what it does, what it touches, where it shows up.
4. Pick the mode and model that fit the job.
5. Review and test in a playtest.
6. Iterate in small steps.

Connect Roblox Studio First

With Studio connected, Superbullet works on your actual project: the scripts and folders you see in its File Explorer, and the systems already in them. Without that, it has to guess, and guesses turn into duplicate systems and code that doesn't fit your game.

Before you send a request, check the top of the chat says Studio: Active and Studio: Connected, and that Studio has the experience you mean to change open.

Start From a Library

Many common systems already exist as Superbullet Libraries, for example fishing, pets with egg hatching, sliding movement, a fireball skill and an admin panel. A library is already built and tested, so your request becomes "install it and adjust it" instead of "build it from nothing".

1. Ask for the system in chat, for example Add a pet system to my game. Superbullet searches its library marketplace for a ready-made match before writing anything new.
2. Pick it in the Use marketplace library? window and click Use selected library.
3. Understand it in Ask Mode before changing it: "How does the pet system decide which pet hatches?" Ask Mode only reads, so nothing changes.
4. Make it yours in Agent Mode: change its look and numbers, and connect it to your other systems ("Make eggs cost 250 coins from the existing currency system").

Some libraries bring the systems they need with them. Fireball Skill, for example, installs a Skill System, Rock Debris System and DamageHandler first. Check what's already in your project before asking for a system that might duplicate one.

Browse what's available in Libraries, or follow Adding Your First Library for the full install.

Game template or library? A game template is a whole playable game to start from, like Combat Game. A library adds one system to a game. If a template is close to the game you want, start your game from it, then add libraries for the systems it doesn't have.

Give Useful Context

Tell Superbullet what the system does, which systems it touches, where players see it, and the rules that matter. Name the systems you already have, so it uses them instead of making new ones.

Vague

Add an efficiency system.

Specific

Add an efficiency upgrade that makes pets collect coins 5% faster per level, up to level 10. Each level costs coins from the existing currency system and is bought from a button in the pet inventory. Save the level with the player's data.

One feature per request. For something big, ask for the core first, then add to it.

Pick the Mode and Model

The mode sets how the AI works. Pick it in Mode: under the chat box:

• Agent Mode (the default): most builds and edits.
• Super Agent Mode: a large system that touches many others. It plans first, for your review.
• Ask Mode: questions and exploring. Read-only, so it changes nothing.
• Debugging Mode: one specific bug you can't explain.

See AI Modes for when to use each.

The model is which AI does the work. Pick it in AI Model above the chat. Models differ in strength and cost, and the menu labels the ones marked Expensive or pro only:

• Retrieving libraries and small systems: BulletLearnV1-Beta, Superbullet's own model, is the best fit.
• Everyday edits and small scripts: a lighter model is enough. The menu describes Claude Haiku 4.5 as a cheaper model for everyday scripting tasks and small edits.
• Complex systems and tough bugs: a stronger model can be worth it. Claude Opus 5.5 is described as the most capable for complex reasoning, and is marked Expensive.
• Thinking versions reason longer before answering. The menu recommends Claude Opus 5.5 (Thinking) for architecting complex systems, but says to use it sparingly due to its high cost.

Review and Test in a Playtest

• Read the AI's summary of what it changed. Its suggested next steps are optional; each one is another AI task that uses tokens.
• Play it in Studio and watch the Output window for errors.
• Remove test tools before you publish. Some libraries add test panels, like the SKILL TESTER in Fireball Skill.

Iterate in Small Steps

• Change one thing at a time, and test in between. When something is almost right, ask for that specific fix instead of a rebuild.
• Something broken? Use Ask Mode to understand it, or Debugging Mode to find the cause, before asking for a fix.
• Start a new session for a new feature. Click + New next to Session:. Everything in the current session goes along with each request, so a long session makes every request use more tokens. The size counter under your token count shows how full it is.