Data

What Roblox creators build with AI (2026 data)

The short version

In 30 days, 7,898 creators started 34,862 builds with RoCode, an AI agent that works inside Roblox Studio. When a first message named a genre, simulators led with 30.1%, ahead of horror and survival. The median completed build took 2.9 minutes, and 79.6% of completed builds changed the game.

Window: 8 October to 6 November 2026 (UTC). Published 7 November 2026.

RoCode is an AI agent for Roblox Studio: a creator describes a feature in a web chat and a Studio plugin builds it in the place they have open. Over 50,000 creators have signed up, and over 300 join every day. This page counts what they asked for and what the agent did, from RoCode's own records. Every figure is an aggregate; no prompt, place or person is shown.

Finding 1

Simulators are the genre creators ask for most

Of 7,736 new chats, 2,168 (28.0%) named a game genre in the first message. Among those, 30.1% asked for a simulator, followed by horror (13.8%), survival (11.8%), tycoons (10.5%) and obbies (10.4%). Brainrot games were named in 9.4%.

  1. Simulator30.1%
  2. Horror13.8%
  3. Survival11.8%
  4. Tycoon10.5%
  5. Obby10.4%
  6. Brainrot9.4%
  7. Battlegrounds or fighting9.3%
  8. Anime8.7%
  9. Shooter or FPS7.4%
  10. RPG5.5%
  11. Racing4.3%
  12. RNG3.9%
  13. Roleplay3.4%
  14. Clicker3.2%
  15. Tower defense1.7%

Share of the 2,168 first messages that named a genre. A message can name more than one, so the shares add up to more than 100%. Battle royale (fewer than 20 chats) is left out. Our one-click starter prompts are not counted.

Finding 2

Maps and UI come up more often than whole games

Across all 7,736 first messages, the most common request was a map, world or building (31.3%), then UI such as a menu, shop or HUD (26.4%). 22.8% asked RoCode to make a game outright, and 15.3% opened with something to fix.

  1. Map, world or buildings31.3%
  2. UI: menu, shop, HUD, inventory26.4%
  3. Make a game22.8%
  4. Saving data, leaderboard or currency17.5%
  5. Fix a bug or error15.3%
  6. Combat, weapons or abilities12.2%
  7. NPCs and enemies9.8%
  8. Pets, eggs or trading8.8%
  9. Cars and vehicles5.0%

Share of 7,736 first messages that use words from each group (English keywords). A message can match several groups.

Finding 3

A typical AI build takes about 3 minutes

The median completed build took 2.9 minutes from start to finish. A quarter finished in under 0.8 minutes, and 90% finished within 10.6 minutes. The median build made 17 tool calls, 4 of them changes to the place.

How long completed builds took
Completed builds (26,014)Minutes
25% finished within0.8
Median (50%)2.9
75% finished within6.9
90% finished within10.6

Wall-clock time of each completed run, measured on RoCode's server.

Finding 4

8 in 10 completed builds changed the game

79.6% of completed builds made at least one change to the Studio place: a script written or edited, a part, model or UI created, a property set or something removed. The rest answered a question or only read the place. Of all 34,862 runs started, 74.6% completed, 17.5% were stopped by the creator, 4.7% failed and 3.2% ended part way.

How runs ended
All runs (34,862)Share
Completed74.6%
Stopped by the creator17.5%
Failed4.7%
Ended part way3.2%

A change is any call that creates, edits, moves or deletes something in the place.

Finding 5

Nearly every script change is checked in Studio

Of 14,868 completed builds that created or edited a script, 95.3% compile-checked the script inside Studio and 83.6% ran a playtest. 97.5% used at least one of those checks or read the Output window before finishing.

  1. Compile check in Studio95.3%
  2. Playtest in Studio83.6%
  3. Any check97.5%

Completed builds that called create_script or edit_script. A check that ran is not the same as a check that passed.

Finding 6

Reading the place is as common as writing to it

Besides checking scripts and playtesting, the agent most often edited and read scripts, listed what is inside an object and read properties. About a third of completed builds built a structure from parts, created a script or created an instance.

  1. Compile-check a script55.3%
  2. Run a playtest52.0%
  3. Edit a script48.8%
  4. Read a script48.0%
  5. List an object's children38.2%
  6. Read properties37.9%
  7. Build a structure from parts34.5%
  8. Create a script33.8%
  9. Create an instance33.6%
  10. Set a property32.8%
  11. Search scripts for text29.3%
  12. Delete an instance24.9%
  13. Create UI9.0%

Share of 26,014 completed builds that called each tool at least once.

Finding 7

When a Studio step fails, it is usually a wrong path

The most common specific reason a step failed was an object or script that was not where the agent looked (11.0% of runs). Next came edits refused because Studio was in a playtest (9.1%), and script edits that no longer matched the script's text because it had changed since it was read (5.9%).

Share of runs that hit each failure at least once
FailureShare of runs
Object or script not found at that path11.0%
Studio was in a playtest, so the edit was refused9.1%
Script text changed since it was read5.9%
Two objects with the same name at that path3.0%
Studio disconnected during the run1.9%
Step timed out0.6%
Wrong value type for a property0.5%
Not a valid class name0.4%
"Not a valid member" property or child0.4%
Other or unclassified tool errors24.3%

Share of all 34,862 runs. Most failed steps are retried in the same run; a run that hit a failure can still complete. Codes for RoCode's own safety checks (for example a delete that needs your confirmation) are left out.

Finding 8

Sunday is the busiest day, 17:00 UTC the busiest hour

Weekends were 8 of the 30 days but 34.5% of all builds. An average Sunday had 1,598 builds, 37.5% above the daily average of 1,162, and an average Saturday 1,412. Thursday was the quietest day with 930. By hour, starts peak at 17:00 UTC (6.3% of all builds) and are lowest at 06:00 UTC (2.2%).

  1. Monday1,132
  2. Tuesday1,031
  3. Wednesday1,095
  4. Thursday930
  5. Friday1,029
  6. Saturday1,412
  7. Sunday1,598

Average runs per calendar day by the UTC weekday they started (the window has 5 Thursdays and Fridays and 4 of every other day).

Method

How we measured

  • Window. 30 days, from 00:00 UTC on 8 October 2026 to the end of 6 November 2026 (UTC).
  • What counts as a build. One run of the agent: a creator sends a message, the agent works in Studio and stops. 34,862 runs by 7,898 accounts are counted; 26,014 of them completed. A run counts as changing the game when it made at least one call that creates, edits, moves or deletes something in the place.
  • Genres and requests. Taken from the first message of each chat started in the window (7,736 chats), by matching English keywords such as "obby", "tycoon" or "tower defense". We did not read or publish the messages one by one. Messages written fully in another language are counted in the totals but rarely match a keyword, so the shares are a floor, not an exact split. Clicks on our own one-click starter prompts are left out.
  • Accounts left out. RoCode's own admin account and any account with 200 or more runs in the window (9 accounts, 3,338 runs), which are mostly test and benchmark accounts.
  • Sign-ups. 51,794 accounts existed on 7 November 2026. 11,205 signed up in the window, an average of 374 a day (median 353).
  • Privacy. Only aggregates are published. No prompt, place, game name or account is shown, and any group of fewer than 20 people or runs is left out or merged into "other".
  • Limits. These are RoCode's users, not all Roblox creators. The genres reflect who finds an AI tool for Roblox Studio, and the tool numbers reflect how RoCode's agent works.

Cite

Cite this data

RoCode, "What Roblox creators build with AI (2026 data)", 7 November 2026, https://www.rocode.app/roblox-ai-build-data

You are welcome to quote any figure on this page with a link to it. For questions about the data, email support@rocode.app. More about the product: RoCode facts and Roblox game genres.

Build your own game in Studio.

Free every day, no card required. Install the plugin, describe the feature, and see what lands in Studio.