Procedural Models hits Full Release — Roblox's AI + parametric 3D pipeline lands in Team Create

Mallow, Roblox shipped something called "Procedural Models" out of beta this week. The blog post says "build parametrized 3D models with code or AI." My eyes glazed over. Should brand teams care?

Yes, and for a specific reason. Let me start with what it physically is. Procedural Models is a new Instance type in Roblox Studio. You insert one via Insert Object → ProceduralModel. It looks like a regular Model in the Explorer, but underneath it has a Generator property pointing at a Luau ModuleScript. That script defines the rules — "build a ladder this tall, with rungs this far apart, in this color."

And then?

And then you set attributes — RungSpacing, RungThickness, Color, whatever the script exposes. The moment you change a value, the script re-runs and the 3D geometry rebuilds in place. No more deleting, re-importing, repositioning.

Wait, that sounds like just "parametric design." Houdini, Grasshopper, those tools have done this for years. What's new?

Two things. (1) It runs natively inside Studio with no external tool in the loop — no export-import dance. (2) The Roblox Assistant can generate the Generator Module for you. You type /generate_procedural_model A stylized round medieval castle with a red-brick base and white-plastered upper tier and the Assistant writes the Luau, sets up the attributes, and gives you a working ProceduralModel. Optionally you attach a reference image to anchor the visual style.

So I prompt, get a model, then tweak it via sliders instead of redoing the prompt.

Exactly. Prompting is the rough cut. Attributes are the fine adjustment. That separation is the entire point — generative AI gives you the starting shape, parametric controls make it brand-usable.

And what changed at Full Release versus the April 23 beta?

Three concrete things. (1) Team Create is now supported, so multi-person teams can actually use it on the same place file. (2) ProceduralModels now work in published, live games — not just Studio sessions. (3) Memory leak and the "stuck at zero size" resizing bug are fixed. Plus it's enabled by default — no Beta Features panel toggle anymore.

Team Create being absent during beta was a real blocker for agencies, right?

Right. During beta, only one person on the place file could realistically use it without merge conflicts. For a 5-person agency build, that killed adoption. Now it's collaborative from day one.

What kinds of things make sense to procedural-ize?

Anything where you'd otherwise build N variants by hand. Roblox's own examples in the announcement: ladders, suspension bridges that adjust cable count based on length, dining sets, medieval castles, foliage. Community examples: procedural islands, procedural forests, procedural shelves. The common pattern: "same thing, different dimensions / colors / counts."

Translate to brand work.

Picture a brand experience with a retail-store mechanic. You need 12 product display shelves at slightly different sizes for different zones. Old workflow: 3D artist builds one, duplicates 12 times, manually resizes each, swaps the product photos. New workflow: a single ProceduralModel with Width / Height / ShelfCount / ProductImageId attributes. Drop 12 instances, set 12 different attribute combinations, done.

And if the brand sends "actually make all the products purple"?

Change one attribute on a parent, propagate, regenerate. Minutes instead of half a day. The same logic applies to event variants — "holiday version with snow," "summer version with shorter awning," "co-promo version with partner branding swapped in." One Generator Module, many configured instances.

What's the gotcha? There's always a gotcha.

Two big ones. (A) Every regenerate overwrites the Generated folder. If your 3D artist hand-polishes a vertex after generation, those edits vanish the next time anyone touches an attribute. (B) "Join Surfaces" is incompatible — joints break during generation. So you can't use legacy weld-snapping with procedural pieces.

So what's the safe handoff workflow?

Two phases. Pre-lock: while you're iterating, keep the ProceduralModel live and let attributes drive everything. Post-lock: once the design is final, clear the Generator property. That "bakes" the current geometry into a standard Model — no more regeneration, safe for artist polish. Roblox calls this the recommended path for final assets.

Other limitations?

Packages are not supported yet. Roblox says it's coming "in the next few months" alongside other Package improvements, but right now you can't convert a ProceduralModel into a Package for cross-place reuse. That's a real constraint for studios shipping multiple experiences off shared assets. Workaround for now: bake to standard Model first, then Package.

What about pricing? Does the Assistant call cost Robux?

Roblox hasn't published rate limits or per-prompt costs for /generate_procedural_model in the Full Release post. Treat it as included in the existing Assistant entitlement for now, but assume that posture could change as usage scales.

Where does Studio MCP come in?

Studio MCP — Roblox's Model Context Protocol bridge — means external tools like Claude Code or Cursor can drive Procedural Model generation from outside Studio. For agencies running an AI-assisted pipeline, you can scaffold ten variants from a planning doc without ever opening Studio yourself.

From the brand side, what should we be checking?

Three things. (1) Ask your dev partner whether their Studio templates have been updated to use ProceduralModels for repeating asset families — shelves, signage, modular building pieces. If they're still duplicating-and-resizing in 2026, that's a productivity tell. (2) For experiences with seasonal variant cadence (monthly drops, event refreshes), confirm the variant strategy uses attributes rather than separate Model trees. (3) If your asset library is going to be shared across multiple places, surface the Package limitation early so it's planned around, not discovered mid-launch.

Failure patterns to avoid?

Two. (A) Brand approves a variant after the artist hand-polished it, the dev iterates one more attribute, the polish disappears, and approvals reset. Always bake before polish. (B) Assistant generates a model that looks right at the default attribute values, but the geometry breaks at the extremes the campaign actually needs. Test the corner cases — minimum size, maximum count, edge colors — before approving the Generator.

…So, the executive summary?

(1) Procedural Models exits beta May 18, 2026. New Instance, Generator Module in Luau, Assistant generation via /generate_procedural_model, Studio MCP support, Team Create works, live in published games. (2) Brand value: variant generation at scale, AI-rough-cut + parametric fine-tune workflow, event refresh becomes a config change. (3) Gotchas: regenerate wipes manual edits (bake before polish), no Packages yet, Join Surfaces broken. (4) Check your dev partner is actually using it for repeating asset families — it's the productivity differentiator for the second half of 2026.

"Build N variants" used to be a budget item. Now it's an attribute table.