Studio tour

The studio is a full game editor in a browser tab. It follows one path in six steps — Map → Cast → Build → Rules → Test → Publish — and this page tours it panel by panel. If what you want is the logic of that path, read The six steps instead.

Screen layout#

The top bar#

It never changes, whatever the step. From left to right:

The step line#

Just below it, one line says where you are and what the step is for (“Map — the ground, the sky, the water”), with the ⌘K reminder on the right. It disappears during a test, where the screen belongs to the game.

The body of the screen#

The entry screen#

With no project open, the studio offers three ways to start, as three cards: Start from a game (the nine complete games, playable at once), Start from a map (eight starting maps as real top-down thumbnails, then a mode), and Empty project. Below: your projects saved in this browser, each with its mode, its date and a “published” label when relevant, and the Import button to reopen a .sandbox.json.

Map#

The right-hand panel, top to bottom:

Cast#

Cast gathers everything that acts in the game. At the top, two buttons: Pick a character opens a full-screen browser of the library’s animated characters and creatures (search field, All / Characters / Creatures / Animated filters, the animation count on each thumbnail); Model my own creates a fresh voxel character and opens the asset editor. Either way the model lands on the map at once and placing stays armed: the next click puts down another.

Below come the four groups, in the order they matter. Every row is one model in one role: thumbnail, name, how many copies, how many animations, four buttons (select, place on the map, edit asset, remove every copy — the player is replaced rather than removed, so it has no remove) and the role’s settings, which apply to every copy in the row at once.

At the very bottom of the panel, the inspector details the entity selected in the view, copy by copy, for the settings that concern only one of them (position, scale, path, events).

Build#

Three columns, and a right-hand panel in five sections.

Outliner#

The left column lists entities grouped by role, with a field to filter the scene and the number of selected entities. Each row lets you set a tag or hide / show the entity.

Viewport#

In the middle, the editable scene — the same view as on the Map and Cast steps: click to select, Shift to add to the selection, move, rotate and scale gizmos, copy-paste and duplicate. Post-processing does not apply in the editor, only in game.

Right panel#

The asset editor#

Model and Animate are not steps: they are the two surfaces of one editor, opened from Cast or Build. Its bar carries a Back button that names the step you came from (“Back · Build”), the asset’s name, and the Model | Animate switch. Esc closes the editor and returns you exactly where you were.

Model#

On the left, the asset’s view; on the right, the panel. It holds the asset list with its three creation buttons, the library, the AI generation panel, the asset’s properties (rename, export as JSON, duplicate, delete), then the editor for its kind: voxel tools and parts for a grid, pieces, gizmos and materials for a primitive assembly, height and animations for an imported model.

Animate#

For an imported model, the surface lists the animations inside the file (one click previews them) and lets you borrow the clips of another rigged library character that shares the same skeleton. For a voxel or primitive asset, you create keyframe clips (position, rotation, scale per part), with a duration, a loop and presets that read the part names.

Rules#

The Rules step gathers the game logic on one page with five sections:

Test#

Test runs the game in the public runtime, on a copy of the document: playing never changes your project. Restart starts a fresh round, and the button at the top right of the frame goes fullscreen (Esc leaves it). The runtime is the same as on the game page: what you test is what players get — with one difference: no wallet is asked for here, while a published game needs one to start.

Publish#

On the left, the listing (64-character title, 400-character description) and the 1280×720 cover, captured from the game or uploaded as a PNG. On the right, what’s missing — the same four lines as the chip in the top bar, each one clickable to reach the step that fixes it — six numbers about the document (assets, entities, terrain size, weight, registry, publish fee), the Publish button, the .sandbox.json export and the export of the whole scene as GLB, glTF, OBJ, STL or USDZ.

Quick add#

⌘K (or CtrlK, or the magnifier in the top bar) opens quick add anywhere in the studio. It searches the whole library and the starter assets at once; the arrow keys move the highlight, Enter adds the asset to the project and arms the map, Esc closes. If you were on Rules, Test or Publish, the studio takes you back to Build so the next click has ground to land on.

Projects, saving and history#

Deep links#

Next#