Changelog

Several pages said RoCreator can generate a 3D model for a prop. It cannot: the outside service that path uses has no credits on our account, so the server turns the request down instead of queueing a job that could never finish. Every one of those claims now says so plainly.

Guides. Complete, paste-and-run Luau for a grappling hook, a double jump, sprinting on Shift and a chase NPC — none of which need RoCreator installed.

This changelog.

An NPC's damage, reach and stun are now derived from the size of the model you actually got, instead of from fixed numbers. A large NPC's attacks used to pass straight through you because its arms were longer than the hard-coded range.

When the AI invents an Explorer path that is nearly right, it is now matched against your real tree before anything runs — including when only the separators differ, so AttackTitan finds Attack_Titan.

Auto-fix used to drop your original request when it repaired its own broken output, so the second attempt answered a slightly different question than the one you asked.

RoCreator can search the Roblox Toolbox and insert an existing model into your place. It refuses anything carrying a script — nothing gets parented into your game that could run code you did not ask for.

Ask for something that has to walk or chase you and you now reliably get a model with a Humanoid in it. Before, the best-rated search result was often a static display mesh, so the AI script waited forever on a Humanoid that never existed and the NPC just stood there. The plugin now loads candidates in order and keeps the first one that is genuinely a character rig.

Inserted character models were being welded rigid, turning every one of them into a statue.

A model aimed at StarterPack is now corrected to somewhere it can actually appear. StarterPack only ever distributes Tools, so a Model sent there was handed to nobody and vanished while the command still reported success.

Searches keep the series or franchise you named. Stripping it turned "a titan from Attack on Titan" into a search for "titan", which on the Toolbox belongs to something else entirely.

Groundwork for installing the plugin from the Roblox Creator Store instead of copying a file into a folder by hand. The switch is in place and flips as soon as the listing is ready.

Corrected four of our own internal records that turned out to be wrong about the state of the plugin listing, after checking them logged out — the way a stranger sees it — rather than from an owner's dashboard.

A logged-out visitor could not obtain the plugin at all, and the install instructions described seven steps as though they were one.

Phones were served the wrong version of the homepage hero first and swapped it after JavaScript arrived.

The site's own description dropped the word "fastest". We have not measured prompt-to-applied time honestly enough to claim it, so it is gone until we have.

Ten new checks that catch classes of broken Luau before it reaches your place — a string that looks like a path being called as an instance, FireServer called from a server Script, JavaScript-style let and const, a not-before-comparison precedence slip that silently kills a feature, and six more.

The email waitlist was returning a 500 on its own database index, so some submissions were being lost.

Raw error text from third-party services was being rendered straight into the chat, occasionally including internal configuration names.

Seven accessibility defects on the dashboard: a composer whose focus ring did not match any other input, disabled buttons that still glowed and were still reachable, and pages missing the skip-link target that lets a keyboard user jump past the navigation.

The generation progress bar stepped in visible jumps instead of moving.

The landing page shows real recorded footage rather than an illustration, and asks for testimonials instead of inventing them.

One error message blamed the single Luau construct that was definitely not the problem.

You can tell us whether a generation actually worked. Nothing in the product could ask before, so every quality claim we had was inferred rather than reported.

We measured whether our own auto-fix repairs anything: it worked barely half the time. Published here rather than quietly improved, because the number is the reason the checks above exist.

A ClassName the Roblox engine cannot construct is now caught against Roblox's own API dump before the command runs, instead of failing in your Explorer.

An internal drafting note was being published on the public Terms and Privacy pages.

Two live false positives in a check that was already rejecting valid builds.

A generation with nothing to deliver waited five minutes for Studio to deliver it before giving up.

Tools that were dead on click, and .Touched connected to a Model — which never fires — are both caught before the code lands.

A grappling hook generation was reaching for a part that had never been created.