Studio basics

Massif Studio is the editor inside Minecraft. Your projects are saved and compiled on Massif Cloud; Massif Client runs the terrain preview on your computer. Studio starts Client for you. Once you have installed Studio and linked your account, press G to open the editor.

Start with a world

Choose New project and a starter world. The getting-started checklist guides you through a terrain edit, a biome edit and an export. You can close it and reopen it from the toolbar.

Start with a small change to an existing node. Editing the graph sends the change to Cloud for compilation; a valid result updates your local terrain preview. Undo lets you step back.

Move between graph and world

The left rail opens Project, Library and Revisions drawers. Click the active icon again to close its drawer. Press Tab, or use the toolbar switch, to move between graph and world focus. The toolbar’s opacity controls adjust how much of each you see.

Nodes describe the generator. Wires connect their outputs to other nodes’ inputs. You can reuse parts of a graph as groups; double-click a group instance to edit its shared definition. Use the breadcrumb to return to the world graph. Changes to a shared definition affect its instances.

Nodes and networks explains the main kinds of data flowing through a graph.

Inspect a change

Enable a noise node’s preview to inspect its field. The 2D card shows values with contours; hover a cell for its value. In 3D, drag to orbit and use the slider to change the solid threshold. Scroll over a preview to zoom; double-click its image to reset the zoom.

To keep the terrain still while tuning a field, press Pause beside Preview. Node cards keep updating after valid edits while terrain stays at the paused version. Resume catches the terrain up. An update already being installed can still finish after you press Pause.

In world focus, point at terrain over empty canvas to see which nodes made a block. Alt + click jumps to its node. Hovering or selecting a material rule highlights nearby surface blocks it painted.

Save, share and export

Cloud owns the saved project and its edit history. Collaborators edit the same project with their assigned permissions. Compilation errors are reported in Studio; fix them before exporting.

Export produces a signed .massif file for a server. When it is ready, download it from your account and follow the Paper or Minestom guide. The server generates new chunks from the export, independently of Studio and Cloud. Exporting again does not rewrite chunks already generated on your server.