Documentation StudioOps Pre-production
StudioOps

Blueprint

Your game's structure in nodes, turned into a production plan; search, templates and shortcuts.

What it is

Blueprint is a node canvas where you build your game piece by piece: scenes, levels, characters, objects and mechanics. Each piece gets what it needs to exist (UI, art, 3D models, animation, audio, programming) with its hours and the person who does it. What starts as a diagram ends up being the real production plan: how much work it is, who does it and how much it costs.

What it solves

The GDD says what the game is, but not how much work it is.
Every requirement has hours and an owner, so scope measures itself.
Scope grows without anyone noticing.
The Scope view adds up hours and cost as soon as you add a node.
Design, schedule and budget live in different files.
The same graph feeds Workflow (Gantt), Budget and Storyboard.

Tutorial: how to use it

  1. 1
    Build the structure

    Drag Game, Scene, Level, Character or Object nodes from the palette and connect them.

  2. 2
    Add requirements

    Attach what each piece needs: UI, image, 3D model, animation, audio or programming.

  3. 3
    Assign hours and people

    In the Inspector you set the task hours and connect the team member with their rate.

  4. 4
    Check Scope and Workflow

    See total hours and cost, and the Gantt with real dates per requirement.

Shortcuts & tips

  • Drop a wire on empty space and pick what goes there: the node appears already connected.
  • Right-click the background or press Tab to open the search; type in Spanish or English.
  • Right-click a node: add child, duplicate, copy, frame, align or delete.
  • Ctrl/⌘ + D duplicates · Ctrl/⌘ + C and V copy and paste, across projects too.
  • F frames the view · Q aligns in a column · Shift + Q in a row · Delete removes.
  • Click a wire's midpoint: reroute point, insert a node in between or remove the connection.
  • Templates (character, enemy, level, mechanic…) bring their requirements connected; hours start at 0 so you set your own.
  • A QA node is a test case: its name is the case and its description the steps.

How it connects