In short
RoCode is an AI coding agent for Roblox Studio. You describe a change in the web chat at rocode.app/chat, and the free RoCode plugin carries out the agent's steps in the place you have open. To start, sign in at rocode.app with an email code, Google, Roblox or Discord, install the plugin from the Roblox Creator Store, allow the permissions Studio asks for, open a place and keep rocode.app/chat open. If Studio is signed in to the same Roblox account you use on RoCode, it connects by itself. Otherwise type the 8-character pairing code from the RoCode panel into the chat, then press Connect in the panel to confirm.
- You need Roblox Studio on Windows or Mac, kept up to date, and a desktop browser. Phones are not supported, and in Brave you turn Shields off for rocode.app.
- You connect once. Studio connects by itself when it is signed in to the same Roblox account you use on RoCode (plugin 3.9.13 or newer); otherwise you type a pairing code, which is valid for 15 minutes and works once. After that, the plugin reconnects on its own.
- The chat has two modes. Build makes changes in Studio. Ask answers questions about your game with read-only tools and changes nothing.
- RoCode works in Studio's edit mode and compile-checks the scripts it writes. With plugin 3.9 or newer, Build mode can also run a short playtest and read the errors, and with plugin 3.9.11 or newer control a test character to check the game works; Ask mode never playtests. With a plugin older than 3.9, press Play and check the result yourself.
- Starter is free with 1 credit a day on GPT-6 Luna, refilled at 00:00 UTC, and needs no card. Paid plans start at $9.99 a month for 150 credits and add GLM 5.3 Flash and Claude Sonnet 5.5. Claude Opus 5.5 comes with Studio and up, and GPT-6 Astra with Ultra.
On this page
What RoCode is
RoCode (RoCode.app) is an AI coding agent for Roblox Studio. You describe a feature in a web chat at rocode.app. A free RoCode plugin from the Roblox Creator Store then carries out the agent's steps in the place you have open: it reads the objects and scripts a step needs, writes the Luau, creates or edits Scripts, LocalScripts, ModuleScripts and other instances, and compile-checks its scripts inside Studio before it finishes.
| Part | What it does |
|---|---|
Web chatrocode.app/chat | Holds the conversation, the model picker, and the step-by-step log of each run. It opens in a desktop browser. |
Relayrelay.rocode.app | RoCode's server between the chat, the plugin and the model. It sends your request through OpenRouter, a service that reaches many AI models through one account, to the model you picked, its backup or, for a message with images, a model that reads them, and passes the model's steps to the plugin. With plugin 3.9.14 or newer it also sends the screenshots taken for the look check to a model that reads images. |
| Studio plugin RoCode, from the Creator Store | Carries out the agent's steps inside Studio with 27 tools that read, create, edit, check and playtest. It keeps a WebSocket connection to the relay, and the relay is the only server it talks to. Studio itself contacts Roblox to load the Creator Store models Insert Model places and, with plugin 3.9.13 or newer, to look up the Roblox name it is signed in with. |
| Your place | The place open in the connected Studio window. The plugin sends the place name and id when it connects, and each run starts with your camera position and up to 8 selected objects, so “this” can mean your selection. Anything else leaves it only when a step asks for it, when the look check takes its screenshots (plugin 3.9.14 or newer), or when you type / in the chat to pick an object. There is no place-file upload and no background sync. |
GPT-6 Luna, GLM 5.3 Flash, Claude Sonnet 5.5, Claude Opus 5.5 and GPT-6 Astra are third-party models that RoCode runs through OpenRouter with its own instructions and Studio tools. RoCode has no models of its own. See Models and credits for which plan includes which model.
Each message runs in one of two modes, picked in the composer: Build, which makes changes in Studio, or Ask, which answers questions about your game without changing anything. See Build and Ask modes.
RoCode (rocode.app) is not Roo Code, the VS Code extension, and not RoCodes.gg or rocode.org.
Requirements
| You need | Details |
|---|---|
| Roblox Studio | On Windows or Mac, kept up to date. The plugin keeps a live connection to RoCode through Studio's WebSocket support, and an older Studio build without it cannot connect. |
| The RoCode plugin | Free, from the Roblox Creator Store. |
| A desktop browser | For rocode.app/chat. Phones are not supported: on a phone the chat shows a desktop-only message. In Brave, Shields block the connection to Studio, so turn Shields off for rocode.app or use Chrome or Edge. |
| A network that reaches the relay | Studio has to reach relay.rocode.app over WebSockets. School or work networks that block this cannot connect. |
| A RoCode account | Free. Sign in at rocode.app with an email code, Google, Roblox or Discord. No card needed. You need to be 13 or older, and under 18 you need a parent or guardian's permission. |
Not needed: a desktop app, a command line, config files, an MCP server or your Roblox password. RoCode never asks for your Roblox password.
Install the plugin and pair it with the chat
Install and connect, step by step
- Create a free account. Sign in at rocode.app with an email code, Google, Roblox or Discord. See Sign-in options.
- Install the plugin. Open the RoCode plugin on the Creator Store and install it. Installed plugins appear in Studio's Plugins tab. In Studio's plugin manager, RoCode is listed as RoCode AI.
- Allow the permissions. When Studio asks, allow HTTP requests to relay.rocode.app, and Script Injection. The table below says why.
- Open a place in Roblox Studio: a game you are working on, or a new Baseplate.
- Open the chat. Open rocode.app/chat in a desktop browser. If Studio is signed in to the same Roblox account you signed in with or linked on RoCode, it connects by itself (plugin 3.9.13 or newer). If the chat shows Connect Studio, click it.
- Or use a pairing code. If Studio does not connect by itself, the RoCode panel shows an 8-character code; if you do not see it, click Use a pairing code. In the chat's Connect to Roblox Studio card, type the code and press Connect.
- Confirm in Studio. After a code, the RoCode panel shows a confirm row with your account. Press Connect (or Allow) there. It waits up to 2 minutes, then shows a new code.
Sign-in options
| Option | What to know |
|---|---|
| Email code | RoCode emails you a one-time sign-in code. There is no password. |
| Sign in with your Google account. | |
| Roblox | Sign in with your Roblox account. RoCode never asks for your Roblox password. A Roblox sign-in does not link to an existing RoCode account, so if you already use RoCode, keep your usual sign-in to keep your plan and chats. Adding an email afterwards is optional: it is for receipts and for signing in without Roblox. |
| Discord | Sign in with your Discord account. |
The Studio permissions the plugin asks for
| Permission | Why the plugin needs it | If you declined it |
|---|---|---|
HTTP requests to relay.rocode.app | RoCode's server, and the only host the plugin talks to. It checks it when it loads, and again if connecting keeps failing, and warns in the Output if it is blocked. Studio itself contacts Roblox to load the Creator Store models Insert Model places and, with plugin 3.9.13 or newer, to look up the Roblox name it is signed in with. | Allow it in Plugins > Manage Plugins > RoCode AI. |
| Script Injection | Lets RoCode create and edit scripts. | With plugin 3.9.2 or newer, RoCode will not start a Build run while it is off; Ask mode still works. Turn it on for RoCode AI in Plugins > Manage Plugins (the pencil icon). The plugin checks again every 30 seconds; if it still says the permission is off, restart Studio. |
One Studio setting is optional and stays your job: Enable Studio Access to API Services. You need it to test data store saving in Studio, and RoCode cannot change it for you. In Studio, open File > Experience Settings > Security, turn it on and click Save. The place has to be published first. Studio then uses the same data stores as the live game, so Roblox recommends turning this on only in a separate test copy.
How pairing works
| Detail | How it works |
|---|---|
| Without a code | With plugin 3.9.13 or newer, Studio connects by itself when it is signed in to the same Roblox account you signed in with or linked on RoCode and rocode.app/chat is open. The code below is for every other case. |
| The code | 8 characters, shown in the RoCode panel like ABCD-EFGH. It never uses the characters I, L, O, 0 or 1. |
| Where to type it | In the chat's Connect to Roblox Studio card, then press Connect. |
| Confirm in Studio | The RoCode panel then shows a confirm row with your account. Press Connect (or Allow) in the panel. If you do not, it waits up to 2 minutes and then shows a new code. |
| How long it lasts | The same code for 15 minutes. |
| How often it works | Once. The code is forgotten as soon as it is used. |
| Next time | The plugin stores a connection key in Studio's plugin settings and reconnects on its own. No code needed. |
| Which places | Once paired, the plugin reconnects in any place you open on that computer. To stop that, disable RoCode AI in Plugins > Manage Plugins. |
| More than one Studio | Only one Studio window is connected at a time. Opening a place in a second window moves the connection there. |
| Different networks | If Studio and the browser are on different public networks, for example behind a VPN or iCloud Private Relay, the chat shows Connect anyway. Press it, then type a new code from the RoCode panel. |
Your first run
The chat will not send a message until a Studio is connected: the send button stays off, and hovering over it shows Connect the plugin first. Once Studio is connected, describe one change.
Write a good first prompt
- Big asks build in rounds. A whole game starts as a playable first version, then you add more with the next-round buttons. Small changes work best one at a time.
- Say what should happen, in plain words. You do not need class names or to know where scripts go.
- Point at what matters. Type
/in the message box to attach an exact Studio object path, such as the script you want changed. With the + button you can also attach up to 12 text files (20,000 characters in total) and up to 4 images per message, on any model. - Just a question? Switch the composer to Ask and nothing in your place changes.
- Or dictate it. The mic button records your prompt; the transcript lands in the message box for you to edit and send.
Free tools. No idea yet? The game idea generator suggests a game with its first prompts. The other free tools are a DevEx calculator, a Robux tax calculator, a thumbnail size checker and a Luau playground that runs Luau in your browser. They need no account.
Add a sprint on Left Shift that drains a stamina bar at the bottom of the screen and refills it when the player stops running.
- Can look through the place first, with tools such as Search Game and Read Script, so it builds around what is already there
- Creates the scripts with Create Script and the bar's UI objects with Create Instance, each in the service it belongs in by default
- Compile-checks the scripts it wrote with Check Script before it finishes
- Sends its changes to Studio in batches, and each batch is an undo point in Studio
An example prompt written by us. The tool names are real, but what a run does depends on your place. With plugin 3.9 or newer RoCode can run a short playtest itself; you can always press Play in Studio to try the result.
Where RoCode puts things
| You ask for | It creates | Where |
|---|---|---|
| Server logic: coins, damage, saving, rounds | Script | ServerScriptService |
| Input, camera and UI behaviour | LocalScript | StarterPlayer > StarterPlayerScripts |
| Screens and menus | ScreenGui | StarterGui |
| Parts, models and structures | Part, Model | Workspace |
Scripts use game:GetService(), and properties are set as Studio's own types, such as Color3, Vector3, UDim2, CFrame and Enum values. To learn why server code and player code go in different places, see LocalScript vs Script vs ModuleScript.
What you see while it works
- A step-by-step log. The chat lists each step by the tool labels in the tools table. Every read and every deletion shows with its path.
- How long it takes. It depends on the task, the size of your place and the model. One run can last up to 80 model turns or 5 hours. The chat shows the credits a run is using while it works.
- Your next prompt can wait in line. While a run is working, you can queue the next prompt. You can have up to 3 runs going at once.
- No edits during a playtest. If a playtest is running when a change is due, RoCode stops the test first, including one you started. If Studio is still in Play after 20 seconds, it changes nothing and asks you to press Stop.
Stop and Continue
Stop a run whenever you like. If a run stops partway, from an error or a usage limit, the changes made so far stay, and Continue picks up where it stopped. A failed run that already changed your place offers Continue instead of starting the prompt again. Runs that you stop count up to where they stopped. When a run fails because of a problem on our side, its credits go back to your balance automatically.
Chat settings
| Setting | What it changes |
|---|---|
| Explain scripts | On lets RoCode add a short summary of how its code works. Off asks for code only. |
| Code comments | On lets RoCode add comments where they help. Off asks for code with no comments. |
| Print statements | On lets RoCode add print() calls for debugging. Off tells it not to add them. |
Build and Ask modes
Every message runs in one of two modes. Build is the default and changes your place. Ask, added on 9 October 2026, answers questions about your game and changes nothing.
| Mode | What it does | Use it for |
|---|---|---|
| Build | Makes changes in Studio. The agent can use all 27 tools: it reads your place, creates and edits scripts and instances, compile-checks its scripts and, with plugin 3.9 or newer, can run a short playtest. | Adding a feature, fixing a bug, building a screen or a structure. |
| Ask | Answers questions about your game without changing anything. It may use only the 10 reading tools; any other tool is refused and never sent to Studio, and it never runs a playtest. The reply is labelled Answer. | Learning how a script works, finding where something lives, asking about an error, or planning a change before you make it. |
Switch modes in the composer
- Look at the toolbar under the message box. On the left are the + button for attachments, the mode chip and the plugin status. On the right are the model picker, the mic and Send.
- Click the mode chip. It shows the mode you are in, Build unless you changed it.
- Pick Ask (Answers questions about your game without changing anything) or Build (Makes changes in Studio).
- Type your message. In Ask mode the box reads Ask anything about your game..., and your message is tagged Ask in the chat.
The choice is remembered in that browser, so a chat you open later starts in the mode you last picked. Check the chip before you send a change.
Where is the coin total saved, and why does it reset when I rejoin?
- Looks through the place with reading tools such as Search Scripts, Search Game and Read Script
- Can read Studio's Output with Check Output, including errors from a playtest you ran
- Changes nothing and never runs a playtest: Create Script, Edit Script, Delete Instance and every other tool that changes the place are refused in Ask mode
- Replies with an Answer, and if something needs fixing, says what it would change and where and suggests switching to Build
An example prompt written by us, in Ask mode. The tool names are real, but what a run reads depends on your place.
What Ask can read
An Ask run may use these 10 tools, all of which only read: List Children, Get Descendants, Find Child, Search Game, Search Scripts, Get Properties, Inspect Model, Read Script, Check Output and Check Script. Check Script only compiles a script; it never runs it. Playtest is not one of the 10: a playtest runs your place's scripts, so Ask never starts one.
Good to know about Ask
- It still needs a connected Studio. Ask reads your place, so the chat will not send until the plugin is connected.
- Ask runs are short. They are made for an answer, not a long job. Ask a follow-up if you want more detail.
- From answer to change. When Ask suggests a fix, switch the chip to Build and ask for the change.
- A prompt keeps its mode. A queued, retried or continued prompt runs in the mode it was sent in, even if you switch the chip afterwards.
The 27 tools
The agent works through 27 tools in the plugin, and every plan gets all 27. Playtest needs plugin 3.9 or newer, and Insert Model needs plugin 3.9.14 or newer. With plugin 3.9 to 3.9.13 the agent has 26 of them, and with an older plugin 25. In Build mode it can use any of them; in Ask mode only the 10 that read. This is each one by the label the chat shows, grouped by area.
| Tool | Area | What it does |
|---|---|---|
| Create Script | Code | Creates a Script, LocalScript or ModuleScript with its full source. |
| Edit Script | Code | Edits an existing script by replacing the exact lines that change, or rewrites it whole. |
| Read Script | Code | Reads a script with line numbers, whole or by line range. Up to 12,000 characters per read. |
| Search Scripts | Code | Searches the text inside scripts and returns matching lines. It scans up to 300 scripts under where it starts. |
| List Children | Context | Lists an object's direct children with name, class and path, and flags duplicate names. |
| Get Descendants | Context | Lists everything under an object, up to 500 objects per call. |
| Find Child | Context | Finds one child by its exact name under a path. |
| Search Game | Context | Searches object names and class names, never script code. Up to 20 matches. |
| Get Properties | Context | Reads a set of key properties for the object's class, plus every attribute and tag. Not every property. |
| Inspect Model | Context | Reads every part under a model or folder in one call, up to 80: position, size, Anchored, CanCollide and Transparency, and which parts float, sit under the ground, are invisible or are loose. |
| Check Output | Context | Reads lines from Studio's Output (all, errors, warnings, or errors and warnings), including Server and Client lines from your last playtest. |
| Create Instance | Studio hierarchy | Creates any non-script object, such as a Part, Folder, Model, RemoteEvent, Value or UI object, with properties, under an existing parent. |
| Set Property | Studio hierarchy | Sets one writable property, converting values to Vector3, UDim2, Color3, CFrame, Enum values and object references. Not every property type can be set. |
| Set Attribute | Studio hierarchy | Sets an attribute on an object. |
| Add Tag | Studio hierarchy | Adds a CollectionService tag. |
| Remove Tag | Studio hierarchy | Removes a CollectionService tag. |
| Clone Instance | Studio hierarchy | Copies an object, optionally renamed or moved to a new parent. |
| Delete Instance | Studio hierarchy | Removes an object that RoCode created in this chat or that you asked it to remove, and reports any siblings with the same name that are left. With plugin 3.8.5 or newer, the object is moved to a RoCodeTrash folder in ServerStorage instead of being destroyed. For anything else, the delete is refused and RoCode is told to ask you. See Deletions. |
| Group Selection | Studio hierarchy | Groups the objects on the agent's own list into a Model. |
| Ungroup Model | Studio hierarchy | Ungroups a Model, moving its children to the model's parent. With plugin 3.8.5 or newer, the empty Model goes to the RoCodeTrash folder. |
| Pivot To | Studio hierarchy | Moves a part or model by setting its pivot. |
| Build Structure | Studio hierarchy | Builds a Model from a list of parts (class, size, position, colour, material, shape) in one call. |
| Place Prefab | Studio hierarchy | Places one of the 12 ready-made structures below, built from parts. |
| Insert Model | Studio hierarchy | Places a free Creator Store model it finds by searching with your own words: well rated, with a reasonable triangle count. It can also insert a model, decal or mesh from an asset ID or Creator Store link you give. A model is scaled to the height asked for, and any scripts inside are removed, so it arrives as a still prop. Plugin 3.9.14 or newer. |
| Build UI | Interface | Starts a ScreenGui from one of 7 layouts or a blank panel, with placeholder items and a companion LocalScript. With plugin 3.9 or newer it also takes a style. |
| Check Script | Checks | Compiles a script with Luau's compiler inside Studio and adds a short list of warnings. Covers one script, a folder or the whole game. |
| Playtest | Checks | Presses Play for a test of 3 to 30 seconds (15 by default), collects the server and client errors and warnings, then stops the test. Plugin 3.9 or newer, Build mode only, at most twice a run plus once more to check its own fix. With plugin 3.9.11 or newer, a test character also plays the game to check it works. The chat log shows it as run playtest. See The short playtest. |
You may also see Agent Selection in the log. It is the agent's internal list of paths, used before Group Selection, and it is never Studio's own selection. It is not one of the 27.
The 12 ready-made structures
Place Prefab builds these from parts: no meshes. Anything else is built from parts, or placed from the Creator Store with Insert Model (plugin 3.9.14 or newer).
Scenery, buildings and props are designed new for each game, so games do not all share the same models: a nature generator makes trees, bushes, rocks and flowers that are each different, buildings come from designed blueprints, and props are built from parts. RoCode uses Creator Store models when you ask for ready-made or realistic ones, and for animals, creatures, food and vehicles. Vehicles are found by searching with your words, then made drivable with its tested vehicle kit.
- Wall
- Floor slab
- Roof wedge
- Room
- House shell
- Tower
- Platform
- Bridge
- Staircase
- Fence segment
- Arena
- Obstacle course
The 7 UI layouts
Build UI starts a ScreenGui from a shop, inventory, HUD, dialog, leaderboard, notification or settings layout, or a blank panel. Layouts come with placeholder items. The companion LocalScript adds hover effects and makes the Close button hide the screen; the game logic is written as separate scripts. RoCode can also build a ScreenGui object by object, with Frames, TextButtons, TextLabels, ScrollingFrames and UICorner. A loading screen is not one of the layouts. For how one works, see how to make a custom loading screen.
With plugin 3.9 or newer, Build UI also takes a style: simulator, blocky, clean or dark, or auto, which matches the GUIs already in your game.
Checks, Output and undo
What Check Script checks
Check Script runs a script through Luau's compiler inside Studio. A compile error comes back with its line and column. It also warns about the patterns below. It doesn't type-check, lint or run your code, so it catches compile errors and a few risky patterns, not logic bugs.
| It warns about | What to do instead |
|---|---|
wait(), spawn() and delay() | Use task.wait(), task.spawn() and task.delay(). |
loadstring | Avoid running code built from strings. |
A require that does not point to a ModuleScript | Point it at the ModuleScript you meant. |
| A ModuleScript that does not return a value | Return the module's table or value at the end. |
A GetService name that does not exist | Fix the service name. |
After every Create Script or Edit Script, the agent is told to run Check Script on that script before it finishes. If a check fails, RoCode can't finish the run until a later check passes. After two tries it can finish, and it tells you what is still failing.
Errors from your playtests
RoCode reads Studio's Output only when a step asks for it, usually with Check Output. It does not watch the Output window. Runtime lines come only from playtests: Check Output reads the Server and Client lines of your last playtest, and with plugin 3.9 or newer, Playtest reports the errors and warnings from RoCode's own short test. To fix a problem you found yourself:
- Press Play in Studio and reproduce the problem.
- Tell RoCode what broke. You can press Stop first: Server and Client lines from your last playtest are kept.
- Check Output reads the Output, then RoCode reads the script around the error line and edits it.
- Play again to confirm the fix.
The short playtest
With plugin 3.9 or newer, a Build run can press Play for a test of up to 30 seconds, collect the server and client errors and warnings, and then stop the test. If Studio does not stop within 20 seconds, it asks you to press Stop. If you are already in Play, it does not start a second test or stop yours. It runs at most twice a run, plus once more to check its own fix, never alongside a change, and Ask mode never runs one. The agent decides when to playtest, so not every build gets one.
RoCode can playtest your game in Studio and control a test character to check it works. With plugin 3.9.11 or newer, the test character walks, jumps and steps on parts, and with plugin 3.9.15 or newer it also presses keys, clicks on-screen buttons and types. It then checks that things happened, such as damage, values or parts, and reports each check as passed or failed. The test takes no screenshots and checks only what the agent chose to test, so it cannot tell whether the game is fun. Press Play yourself to judge that. With a plugin older than 3.9, RoCode cannot start a playtest: press Play and tell it what broke.
The look check
With plugin 3.9.14 or newer, a Build run that built or changed something you can see takes screenshots of it in Studio before it finishes, at most once a run: usually two, from opposite corners, plus one of the screen UI when it built UI. They are taken in edit mode, never during a playtest, and the plugin puts your camera and selection back afterwards. RoCode sends them through OpenRouter to GLM 5.3 Flash, with DeepSeek V4.1 Flash as backup, on every plan. That model lists clear problems, such as parts floating or sunk into the ground, gaps or the wrong scale, and the agent fixes the ones that are real. The chat does not show the screenshots, and RoCode does not store them. The look check cannot tell whether your game is fun. If Studio is minimized or the check fails, the run finishes without it. Ask mode never runs one.
Undo, batch by batch
RoCode sets an undo point in Studio before and after each batch of changes, so Ctrl+Z (⌘Z on Mac) steps back through its work one batch at a time while Studio is open. A run is usually several batches, so undoing a longer run takes several presses. Reads and playtests set no undo point. The chat's Revert button only rewinds the conversation, not Studio.
Deletions
Since 9 October 2026, RoCode deletes or ungroups an object only when one of these is true:
- RoCode created that object earlier in the same chat.
- Your message asks it to remove or rebuild the object: by its name or the name of something it is inside, by saying everything, or while you have it, or something it is inside, selected in Studio.
- RoCode asked whether to delete it, and you said yes.
Otherwise the delete is refused before it reaches Studio, and RoCode is told to ask you. The rule covers deleting and ungrouping only, not moving, renaming or rewriting an object. In Ask mode, Delete Instance is refused.
With plugin 3.8.5 or newer, a deleted object is not destroyed. The plugin moves it to a RoCodeTrash folder in ServerStorage with its original location recorded, and Scripts in that folder stop running. The folder is saved with your place and keeps the deletes of the 30 most recent runs (up to 25,000 objects); older ones, and anything deleted from inside the trash, are gone for good.
Each deletion shows in the chat with its path and is part of that batch's undo point in Studio, so you can undo it batch by batch.
The header line in new scripts
Scripts made with Create Script, and scripts rewritten whole, start with the comment -- Generated by RoCode AI | https://rocode.app. Targeted edits don't add it.
Models and credits
| Model | Plans | What to know | What it uses |
|---|---|---|---|
| GPT-6 Luna | Every plan | Made by OpenAI. The free model. It reads images. | On Starter, your 1 free credit a day. On a paid plan, your 2 daily credits (any model, saved up to 10), then your plan credits. |
| GLM 5.3 Flash | Pro and up | Made by Z.ai. The default after you upgrade. | Your monthly credits, at the lowest rate of the paid models |
| Claude Sonnet 5.5 | Pro and up | A stronger model from Anthropic. RoCode asks you to confirm the first time you pick it. | Your monthly credits, used faster than on GLM 5.3 Flash |
| Claude Opus 5.5 | Studio and up | Anthropic's top model. RoCode asks you to confirm the first time you pick it. | Your monthly credits, used faster than on GLM 5.3 Flash |
| GPT-6 Astra | Ultra | OpenAI's top model, and the one that uses credits fastest. RoCode asks you to confirm the first time you pick it. | Your monthly credits, used fastest |
| Your own model | Any paid plan | A model ID you choose on OpenRouter. It must support tool calling, and not every model completes runs with RoCode's tools yet. | Your OpenRouter balance |
Ultra includes every model. Starter users get GPT-6 Luna.
The model picker sits on the right of the composer toolbar, under the message box. It shows every model. A model your plan does not include has a lock and the name of the plan it needs.
You can attach images on every model: PNG, JPG or WebP, under 10 MB each, up to 4 per message. GPT-6 Luna, the free model, reads images itself. With your own key, pick a model that reads images.
If a paid model is slow to start, RoCode first tries the same model through another provider. If GLM 5.3 Flash still fails, DeepSeek V4 Flash can finish a text task, charged at its lower price, and the line under the reply says so. If GPT-6 Luna, the free model, does not start answering, DeepSeek V4 Flash, a backup model, can finish the run. On other models the run stops, and a run that fails on our side gets its credits back. Runs on your own key never switch.
The first time you pick Claude Sonnet 5.5, Claude Opus 5.5 or GPT-6 Astra, RoCode shows what it costs and asks you to confirm. If you are under 18, a parent or guardian needs to agree. Long chats cost more on these three models, so start a new chat for a new task.
What a credit is
A credit measures what a run costs to compute. Stronger models and longer runs use more. The chat shows the credits a run is using while it works and the total under every reply.
For scale, at current rates: an advanced task uses about 4 credits, and a standard task (GPT-6 Luna) about 0.4. That makes Pro about 35 advanced tasks a month or 350 standard tasks, Studio about 80 or 750 and Ultra about 125 or 1,200. Long tasks use more. Claude Sonnet 5.5, Claude Opus 5.5 and GPT-6 Astra use credits faster. On the free model, 1 credit is enough for a small task or two.
Starter gets 1 free credit a day on GPT-6 Luna. Paid plans also get 2 daily credits every 24 hours that work on any model, build up to 10 if you do not use them, and are used before your plan credits.
Your balance is at the top of the chat. On a paid plan it reads like 118.4 credits. On Starter it reads like 0.6 of 1 left today. Click it to see your plan credits and when they reset, your pack credits, and the free credits left today. The line under each reply shows what the run used, the model that ran, the number of steps and the time. The Usage section of your account page shows your balance, the reset date, the last 14 days and every run with its credits, and you can download it as a CSV file. Voice input uses a small amount of credits.
If you stop a run, it counts up to where it stopped. A run that fails because of a problem on RoCode's side gets its credits back automatically. One run also pauses after a set number of credits and asks before it goes on; see Limits.
When credits reset
| Detail | Starter (free) | Paid plans |
|---|---|---|
| Allowance | 1 credit a day | 150, 320 or 500 credits a month, no daily cap, plus 2 daily credits on any model that build up to 10. |
| Resets | Every day at 00:00 UTC | Monthly plans: each month, when your payment goes through. Annual plans: every 30 days. The chat shows the exact date and time. |
| Unused credits | Don't carry over | Plan credits don't carry over. Pack credits never expire. |
| When you run out | Wait for 00:00 UTC, when free credits refill, add a credit pack, or upgrade. | Add a credit pack, move up a plan, use your own key, or wait for the reset. Your 2 daily credits also keep coming, on any model. |
Your own OpenRouter key (paid plans only)
- Plans: every paid plan. It is not available on Starter.
- Where: the last card in the chat's model picker, tagged OpenRouter. You add an OpenRouter API key (
sk-or-v1-...) and a model ID. - Billing: OpenRouter bills your account, and no RoCode credits are used, even after your monthly credits run out.
- Subscriptions: none needed. Claude, Claude Code and ChatGPT subscriptions can't be connected.
- Checked: the key, with OpenRouter, when you save. The model is not checked, so try yours on a small task first.
- Stored: encrypted, and you can remove it any time. See Privacy and security.
Credit packs
On any plan you can buy extra credits on the account page: from 50 credits for $4.99 up to 1,200 credits for $99.99. Packs are used after the monthly credits, and they never expire. If your plan ends, they stay on your account. On Starter, packs are used after your free credits and run on GPT-6 Luna.
| Pack | Price |
|---|---|
| 50 credits | $4.99 |
| 220 credits | $19.99 |
| 580 credits | $49.99 |
| 1,200 credits | $99.99 |
Limits
| Limit | Value |
|---|---|
| Runs at once | Up to 3 per account |
| One run | Up to 80 model turns (calls to the model), each able to use several tools, or 5 hours |
| One Ask run | Short, and read-only: only the 10 reading tools |
| Credits in one run | One run pauses after a set number of credits and asks before it goes on. The limit depends on the model, and it can be lower on smaller plans. You can continue or let it finish up. |
| Playtest | Up to 30 seconds each, at most 2 a run plus 1 to check its own fix, in Build mode with plugin 3.9 or newer; the test character needs plugin 3.9.11 or newer |
| Get Descendants | Up to 500 objects a call |
| Search Game | Up to 20 matches |
| Search Scripts | Up to 300 scripts under where it starts |
| Script source per read | 12,000 characters; longer scripts are read in line ranges |
| What the model sees per read | Trimmed to 4,000 characters, 6,000 for checks and playtests, 12,000 for script source |
| Text attachments | Up to 12 files and 20,000 characters in total. Binary place and model files (.rbxl, .rbxm) are not accepted. |
| Image attachments | PNG, JPG or WebP, under 10 MB each, up to 4 per message, on any model |
| Voice input | Up to 4 minutes a recording; the transcript lands in the message box for you to edit |
What RoCode does not do today
- Judge whether your game is fun, or play it for you outside its own short playtests
- Take screenshots while your game runs. The look check (plugin 3.9.14 or newer) takes screenshots only of what a Build run built, in edit mode. You can attach your own screenshots on any model.
- Generate meshes, textures or animations from scratch. It places existing Creator Store models instead: ones it finds by searching with your words, or a model, decal or mesh from an asset ID or link you give
- Hand-sculpt or paint terrain. It can build Terrain for you (hills, mountains, lakes, rivers, islands and beaches) with a generated script; touching it up by hand stays yours
- Publish or save your place, or change your experience's settings on Roblox's website. It can change place properties such as gravity, like any edit in Studio.
- Build a finished, balanced game from one sentence
- Work on a phone: the chat shows that it is a desktop app only
It also has no tools for game passes, developer products, uploading assets or turning on API Services. Apart from its short playtest, it does not run your scripts. It writes Luau that uses DataStoreService, RemoteEvents, TweenService or PathfindingService like any Roblox script, and builds the instances those scripts need, but its playtest checks only what the agent chose to test, so play the game yourself to confirm they work.
The same limits in plain words, with the complaints you may read online and whether they are still true: What RoCode can't do.
Safety: what RoCode can reach, and how to undo it
RoCode never asks for your Roblox password and never uploads your place file. The plugin sends back the results of the steps a run asks for, which can include full script text, plus your camera position and up to 8 selected objects when a run starts, look check screenshots of what a Build run built (plugin 3.9.14 or newer), and the place name and id when it connects. The current plugin's own network connection goes only to RoCode's server at relay.rocode.app, over an encrypted connection. Studio itself contacts Roblox to load the Creator Store models Insert Model places and, with plugin 3.9.13 or newer, to look up the Roblox name it is signed in with.
Each batch of changes is an undo point you can step back with Ctrl+Z (⌘Z on Mac) while Studio is open. With plugin 3.8.5 or newer, deleted objects go to a RoCodeTrash folder in ServerStorage, which keeps the deletes of the 30 most recent runs. Payment happens in Paddle's own checkout, so you enter your card with Paddle, not on a RoCode form.
Who runs RoCode: a sole trader in the United Kingdom, trading as RoCode (see the Terms); email support@rocode.app.
RoCode (rocode.app) is not Roo Code, the VS Code extension, and not RoCodes.gg or rocode.org.
RoCode changes the place you have open, so it is fair to ask what it can reach and how you take a change back. The detail below is what the plugin and RoCode's server do today. What is stored, and who processes a request, is under Privacy and security. The same answers, with how to disconnect or remove RoCode, are on one page: Is RoCode safe?
What the plugin can and cannot reach
- Only RoCode's server. The plugin's own requests go only to relay.rocode.app. Studio itself contacts Roblox to load the Creator Store models Insert Model places and, with plugin 3.9.13 or newer, to look up the Roblox name it is signed in with.
- One Studio window. Only one Studio window is connected to your account at a time. When a step asks, RoCode can read any object or script in the place open there.
- What a step sends back. Step results can include object names, properties and full script text, and a script edit sends the script before and after. When you type
/in the chat, the plugin sends up to 15 matching names, classes and paths. - No publishing or spending. The plugin has no code to publish or save your place, upload assets or spend Robux. Insert Model places only existing Creator Store assets, found by searching with your words or from an asset ID or link you give, and removes any scripts inside a model.
- Your Roblox user id. The current plugin sends the Roblox user id and name Studio is signed in with while it pairs, so RoCode can connect Studio to the RoCode account that has the same Roblox account.
Studio's permission prompts
Studio may ask you to allow the plugin to reach relay.rocode.app, and the plugin needs Script Injection to create and edit scripts. You can change both for RoCode AI in Plugins > Manage Plugins. The Studio permissions table says what each one is for and what to do if you declined it.
Taking a change back
- Undo. Ctrl+Z steps back one batch at a time, and a run is usually several batches, so undoing a longer run takes several presses. See Undo, batch by batch.
- Deletes. The RoCodeTrash folder is saved with your place and holds up to 25,000 objects; deletes older than the 30 most recent runs, and anything deleted from inside the trash, are gone for good. Deletions says when RoCode may delete at all.
- No edits during a playtest. Before a change, RoCode stops a running playtest, including one you started. If Studio is still in Play after 20 seconds, it changes nothing and asks you to press Stop.
- Your script edits. Edit Script will not replace a whole script that changed after RoCode last read it, and smaller edits are applied to the script's current text, so your other changes stay.
Pairing, sign-in and your own key
- Pairing. Connecting with a pairing code uses a one-time 8-character code that expires after 15 minutes, and Studio then asks you to confirm the account. See How pairing works.
- Signing out. Sign out in the RoCode panel deletes the connection key saved in that Studio; it does not revoke the key itself. Disconnect Studio in the chat signs out every Studio connected to your account.
- No RoCode password. You sign in with an email code, Google, Discord or Roblox; RoCode has no passwords of its own.
- Your own key. If you add your own OpenRouter key, it is encrypted with AES-256-GCM before it is stored.
The read-only mode, and playtests
Ask mode is read-only: it can use only 10 reading tools, and RoCode's server refuses any tool that would change your place before it reaches Studio. It never runs a playtest. Use Ask to look around a game before you let Build change it. See Build and Ask modes.
In Build mode with plugin 3.9 or newer, RoCode can press Play for a short test, and a playtest runs your place's scripts like any Play test. If you turned on Studio Access to API Services, Studio uses the same data stores as the live game, so Roblox recommends doing that only in a separate test copy.
Independent from Roblox
RoCode is an independent product. It is not affiliated with, endorsed by, or sponsored by Roblox Corporation, and it is not Roblox Assistant. You need to be 13 or older to use it, and under 18 you need a parent or guardian's permission.
Privacy and security
This is how RoCode works today. The Privacy Policy is the full policy, and the Terms cover using RoCode.
| Topic | How it works |
|---|---|
| What it can read | The place open in the connected Studio window: objects, properties, attributes, tags, script source and Output. Each run starts with your camera position and up to 8 selected objects. Beyond that, it reads when a step of a run asks, or when you search with / in the chat. Each read a run makes shows in the chat. With plugin 3.9.14 or newer, the look check also takes screenshots of what a Build run built; the chat does not show them. |
| What gets uploaded | No place file and no background sync. The plugin sends back the results of the steps a run asks for, which can include full script text (a script edit sends the script before and after), and the place name and id when it connects. The model sees what each read returns, trimmed per read. With plugin 3.9.14 or newer, a Build run also sends up to three small screenshots of what it built, for the look check. RoCode does not store them. |
| Your Roblox account | RoCode never asks for your Roblox password, and the plugin's own requests go only to relay.rocode.app. The current plugin sends the Roblox user id and name Studio is signed in with only while it pairs, to find the RoCode account that has the same Roblox account. It works only on the place open in the connected Studio window, and the plugin has no code to publish or save your place, upload assets or spend Robux. Insert Model places only existing Creator Store assets, found by searching with your words or from an asset ID or link you give, and removes any scripts inside a model. |
| Which places | Only the one Studio window that is connected. Once paired, the plugin reconnects in any place you open on that computer. To stop that, disable RoCode AI in Plugins > Manage Plugins. |
| What is stored | Your chats, so you can pick up later: prompts, attached text files, replies, chat titles, the code RoCode wrote or read, and the Output lines it saw. Chats stay until you delete them. Run records (tool names, object paths, error messages and partial replies) stay until you delete your account. |
| Who processes a request | Every call to the model goes through OpenRouter to a hosting provider for the model that runs your request: the one you picked, its backup, or, for a message with images, a model that reads them. Look check screenshots go through OpenRouter to GLM 5.3 Flash, or to DeepSeek V4.1 Flash as backup. Chat titles, suggested next prompts and voice input go through OpenRouter too. RoCode has no models of its own. RoCode's database and relay run in the United States, some site functions run on Vercel's edge network near you, and model hosts may be anywhere. |
| Encryption | HTTPS for the site and the chat, and an encrypted connection between the plugin and RoCode's servers. RoCode can read stored chats. |
| Your OpenRouter key | Encrypted with AES-256-GCM before it's stored. It's decrypted only on RoCode's servers, to run your requests and to show it back to you in the model picker. Remove it any time. |
| On your computer | The plugin keeps a connection key in Studio's plugin settings so it can reconnect, and a copy of recent Output lines. Every 30 seconds it adds and removes a temporary script in ServerStorage to check its Script Injection permission. On a shared computer, disable the plugin when you're done. |
| Deleting your account | Deleting your account cancels your subscription right away, then deletes your profile, chats, messages, keys and run records. Kept: billing records needed for refunds and chargebacks (including your email address on payment emails), per-run usage records that keep your old account ID, and usage analytics with your account ID removed. |
RoCode's instructions also tell the agent to treat text inside your place as data, not instructions, and to refuse exploits, backdoors and scripts meant to harm players or steal data.
Troubleshooting
Most setup problems are one of the cases below. If yours is not, ask in the RoCode Discord, which is where support happens.
Studio can't connect, or the plugin says WebSocket is not available
Update Roblox Studio. The plugin keeps its live connection to RoCode through Studio's WebSocket support, and older builds do not have it. Your network also has to reach relay.rocode.app over WebSockets; school or work networks that block this cannot connect.
The plugin says it can't reach relay.rocode.app
Allow HTTP requests to relay.rocode.app for RoCode AI in Plugins > Manage Plugins, then click Reset in the RoCode panel. It is the only host the current plugin talks to, and the plugin checks it when it loads and again if connecting keeps failing.
RoCode cannot create or edit scripts
Script Injection was probably declined. With plugin 3.9.2 or newer, RoCode will not start a Build run while it is off; Ask mode still works. Turn it on for RoCode AI in Plugins > Manage Plugins (the pencil icon). The plugin checks again every 30 seconds and before each script write; if it still says the permission is off, restart Studio.
Studio does not connect by itself
It connects by itself only when Studio is signed in to the same Roblox account you signed in with or linked on RoCode, with plugin 3.9.13 or newer and rocode.app/chat open. If the chat shows Connect Studio, click it. Otherwise use a pairing code: the RoCode panel shows it, or click Use a pairing code there, then type it into the chat.
The code is not accepted
A code is valid for 15 minutes and works once, so type the code the RoCode panel shows now. It never contains I, L, O, 0 or 1.
I typed the code but Studio is still not connected
Look at the RoCode panel in Studio. It shows a confirm row with your account: press Connect (or Allow) there. If nobody confirms within 2 minutes, the panel shows a new code, so type that one into the chat.
The send button stays off in Ask mode
Ask reads your place, so it needs a connected Studio like Build does. Pair the plugin first, then send your question.
I signed in with Roblox and my plan or chats are missing
A Roblox sign-in does not link to an existing RoCode account, so it is a separate account. Sign out and sign in the way you usually do, with your email code, Google or Discord, to keep your plan and chats.
The chat asks me to press Connect anyway
Studio and the browser are on different public networks, for example because of a VPN or iCloud Private Relay. Press Connect anyway, then type a new code from the RoCode panel.
The plugin briefly says "No chat found"
Keep the chat open. The plugin reconnects and the same code comes back.
The connection moved to another Studio window
Only one Studio window is connected at a time: opening a place in a second window moves the connection there. Work in one Studio window while you use RoCode.
I use Brave and cannot connect
Brave Shields block the connection to Studio. Turn Shields off for rocode.app, or use Chrome or Edge.
RoCode connects in places I did not mean it to
Once paired, the plugin reconnects in any place you open on that computer. Disable RoCode AI in Plugins > Manage Plugins when you do not want that. On a shared computer, disable the plugin when you are done.
A script called RoCodePermissionCheck keeps appearing in ServerStorage
That is expected. Every 30 seconds the plugin adds and removes a temporary script there to check its Script Injection permission.
Check Script reports a syntax problem in a script that looks right
The current plugin can report an unbalanced delimiter in a valid script, for example one with an apostrophe in a comment. Open the script in Studio: the Script Editor underlines real errors, and the Script Analysis window (the Analysis button in the Script tab) lists them. If Studio shows no error there, you can ignore that report. A failed check cannot block a run for ever: after two tries the run can finish, and RoCode tells you what is still failing.
A run stopped partway
The changes made so far stay. Press Continue to pick up where it stopped. If it paused at its credit limit for one run, you can also press Finish up. If it stopped because you ran out of credits, see When credits reset.
RoCode missed the script I meant
In a big place Search Scripts covers only up to 300 scripts under where it starts. Name the folder or script in your message, or attach it with /.
My own model does not finish runs
The model must support tool calling, and not every model completes runs with RoCode's tools yet. The key is checked when you save, but the model is not, so try another model ID on a small task.
Data store saving does not work in Studio
Turn on Enable Studio Access to API Services in File > Experience Settings > Security, then click Save. The place has to be published first, and RoCode cannot change this setting. Studio then uses the same data stores as the live game, so turn it on in a separate test copy.
Plans
| Plan | Monthly | Annual | Credits | Models |
|---|---|---|---|---|
| Starter (free) | Free, no card | None | 1 a day, refilled at 00:00 UTC | GPT-6 Luna |
| Pro | $9.99 a month | $83.99 a year | 150 a month | Adds GLM 5.3 Flash and Claude Sonnet 5.5 |
| Studio (Recommended) | $19.99 a month | $167.99 a year | 320 a month | Adds Claude Opus 5.5 |
| Ultra | $29.99 a month | $251.99 a year | 500 a month | Adds GPT-6 Astra |
- Every plan gets all 27 tools. Paid plans add more models, your own OpenRouter key and no daily cap, and their runs go ahead of Starter runs in the queue.
- Free credits do not need the Discord, and neither does paying.
- Annual plans cost 30% less than 12 months of the monthly plan, are billed once a year and get the same credits, refilled every 30 days. An annual plan bought before credits stays as it is.
- If you subscribed to Studio or Ultra before the current prices, you keep your price and credits until you change plan.
- Paddle runs checkout as the merchant of record: it takes the payment, handles sales tax or VAT, issues the invoice and is the seller on your receipt. RoCode does not store card details.
- If you are under 18, ask the cardholder before you buy.
- Cancel from your account page. You keep your plan to the end of the paid period and aren't charged again.
Upgrades, downgrades and the full comparison are on the pricing page. Comparing free options? See free AI for Roblox Studio.
Refunds
- Refunds are in full within 14 days of any payment, including renewals and credit packs. That applies for any reason, wherever you live.
- How to ask: at paddle.net, or by replying to your Paddle receipt.
- After a refund, new plans, upgrades and credit packs are paused for 60 days. The credits that payment bought are removed.
- After 14 days: payments are not refundable, except where the law requires.
Support questions
Is RoCode made by Roblox?
No. RoCode is an independent product, built by its founder, Abdullah Hasan. It is not affiliated with, endorsed by, or sponsored by Roblox Corporation, and it is separate from Roblox Assistant.
Is RoCode safe?
RoCode never asks for your Roblox password and never uploads your place file. The current plugin's own network connection goes only to RoCode's server at relay.rocode.app, over an encrypted connection. Studio itself contacts Roblox to load the Creator Store models Insert Model places and, with plugin 3.9.13 or newer, to look up the Roblox name it is signed in with. When a step asks, RoCode can read any object or script in the open place, and what it reads goes through OpenRouter to the provider hosting the model. With plugin 3.9.14 or newer, screenshots of what a Build run built also go through OpenRouter, to GLM 5.3 Flash or, as backup, DeepSeek V4.1 Flash. Each batch of changes is an undo point while Studio is open, deletes go to a RoCodeTrash folder in ServerStorage (plugin 3.8.5 or newer), and Ask mode answers questions without changing anything. You sign in without a RoCode password and pay in Paddle's own checkout. More on Is RoCode safe?
What is Ask mode in RoCode?
Ask is the second mode in the RoCode composer, next to Build. Build makes changes in Studio. Ask answers questions about your game without changing anything: it may use only 10 reading tools, such as Read Script, Search Scripts and Check Output, and any tool that would change the place is refused. To switch, click the mode chip on the toolbar under the message box and pick Ask. Ask still needs a connected Studio, because it reads your place.
Which AI models does RoCode use?
Third-party models, run through OpenRouter with RoCode's own instructions and Studio tools. RoCode has no models of its own. GPT-6 Luna is on every plan, including the free Starter plan. GLM 5.3 Flash and Claude Sonnet 5.5 come with Pro, Claude Opus 5.5 with Studio and up, and GPT-6 Astra with Ultra. On any paid plan you can also use your own OpenRouter key with a model that supports tool calling.
How many credits does a task use in RoCode?
It depends on the model and the length of the run. At current rates, an advanced task uses about 4 credits and a standard task on GPT-6 Luna about 0.4. Long tasks use more, and Claude Sonnet 5.5, Claude Opus 5.5 and GPT-6 Astra use credits faster. The chat shows the credits a run is using while it works and the total under every reply.
Do I have to pair every time I open Studio?
No. With plugin 3.9.13 or newer, Studio connects by itself when it is signed in to the same Roblox account you use on RoCode. Otherwise you type a pairing code once: the plugin then stores a connection key in Studio's plugin settings and reconnects on its own, in any place you open on that computer.
Is there a RoCode download?
There is no desktop app to download. RoCode is a web chat at rocode.app plus a free plugin you install from the Roblox Creator Store.
Can I use RoCode on a phone?
No. The chat needs a desktop browser, and Roblox Studio has to run on Windows or Mac.
Can I write to RoCode in another language?
Yes. The chat, the plugin and these docs are in English, but you can write your prompts in your own language, and RoCode usually answers in it. Some notices and all buttons stay in English. Pages in Spanish: IA para Roblox Studio and Crear juegos de Roblox con IA. In Portuguese: IA para Roblox Studio and Criar jogos no Roblox com IA. In French: IA pour Roblox Studio and Créer un jeu Roblox avec l'IA.
Does RoCode press Play or publish my game?
In Build mode with plugin 3.9 or newer, it can press Play for a short playtest to check for errors, and with plugin 3.9.11 or newer control a test character to check the game works; Ask mode never does. It never publishes or saves your place, and it cannot change your experience's settings on Roblox's website. You publish yourself.
Can I use my own OpenRouter key on the free plan?
No. Your own OpenRouter key is part of every paid plan. Starter uses GPT-6 Luna with 1 credit a day.
Where do I get help?
In the RoCode Discord. Say what you tried and what the chat or the plugin panel shows.
Sources and further reading
- RoCode Plugin on the Roblox Creator Store. the plugin this page describes
- Pricing. every plan, credit packs, changing plans and refunds
- Privacy Policy. the full privacy policy
- Terms of Service. the terms for using RoCode
- Changelog. every release, newest first, including the one-time pairing code on 27 September 2026
- Free Roblox creator tools. a game idea generator, DevEx and Robux tax calculators, a thumbnail size checker and a Luau playground, with no account
- Roblox Studio scripts. copy-ready, type-checked Luau from the guides, sorted by what it builds
- Roblox Creator Docs: Creator Store. installing a plugin from the Creator Store
- Roblox Creator Docs: Data stores. turning on Studio access to API Services, and why to use a test copy
- Roblox Creator Docs: Output. the Output window that Check Output reads
- Roblox Creator Docs: Script Editor. where the Script Analysis window lists errors in a script