prompt → playable place

Describe the game.
We build it in Studio.

One command sets the genre. The panels set the shape. Spawn pulls the modules and map kits, renames them into your own namespace, writes the Luau that binds them, and hands you a place file you can open in Roblox Studio and publish.

/spawn

or set it by hand below — the console rebuilds on every change

build spec

Everything the sentence did not say

Genre, who can play it and on what, where players land when they join, and whether this is one place or a universe of them.

Six questions. Everything else takes a sensible default.

01What are you making?

02How many players in a server?

03Who can play it?

04Where do players land?

05How many places?

06How should it be built?

genre Tycoon

players & devices

lobby Lobby island

universe
    ai model Opus 5

    assembly from library
    usage this month

    0

      live build

      Watch it get made

      Every line below becomes something real in the place file: a ModuleScript, a folder of parts, a RemoteEvent, a DataStore schema, a teleport route.

      build #0412 history logs
      idle
      00.0s

      stdout

      starting points

      Eight genres, or your own words

      Pick one to prefill the prompt, then bend it however you like — the generator reads the whole sentence, not just the keyword.

      what you get

      Not a free model dump. A working place.

      Spawn writes what a competent Roblox dev would write, in the folders you would expect to find it in, with a Rojo project so it opens in your editor as well as Studio.

      • Modules, resolvedCommunity modules pinned to a version, required in the right order, with the ones that fight each other swapped out before the first run.
      • Luau that references itselfThe shop reads the same currency the collector writes. Rebirth costs come from one curve. Remotes are validated on the server, not trusted.
      • Map kits, placedPlots, corridors, stages and tracks are pasted from the kit library and dressed, not generated part by part — so the place file stays small enough to open.
      • Data and monetisationProfileService schemas, session locking, gamepass and dev-product receipts, and analytics events that fire on the moments you care about.
      
                

      the pipeline

      Five stages, no wizard

      1. 01

        Read the intent

        Your sentence becomes a spec: genre, loop, progression, server size, devices, monetisation.

      2. 02

        Pull the parts

        Modules and map kits come out of a curated library, pinned and ordered — nothing is written from scratch.

      3. 03

        Rebrand & patch

        Everything is renamed into your namespace, then the model you picked patches the Luau so the pieces agree.

      4. 04

        Assemble the place

        Kits are placed, UI is bound, data schemas are written, and the universe is wired if you asked for more than one place.

      5. 05

        Hand it over

        You get a .rbxl and a Rojo project. Open it in Studio, playtest, publish when you like — it is a normal place.

      pricing

      Build free. Pay for what you burn.

      Sandbox

      €0/ forever

      For trying ideas out loud.

      • 3 builds a day
      • 60K tokens a month
      • Astra and Fable 5
      • Studio file export
      most picked

      Creator

      €12/ month

      One experience you keep working on.

      • Unlimited builds
      • 2M tokens included
      • Every premium model, Opus 5 included
      • Edit by prompt after the first build
      • €4 per extra 1M tokens

      Studio

      €49/ month

      A universe of places, not one map.

      • Up to 8 places, teleports wired
      • 10M tokens included
      • Bring your own API keys
      • Blender mesh bridge
      • €3 per extra 1M tokens

      What are you building tonight?

      Type it. It will be open in Studio before you finish reading the docs you were about to open.