This section is for engineers building the simulation and training content behind a Space Range exercise. Choose one complete path based on how you want to work.

If you only need to run a scenario that someone else built, follow Hosting a Space Range instead.

Choose your path

Beginner: Build in Space Range Intermediate: Convert a Studio Mission Advanced: Author with JSON

Beginner: build in Space Range

Build the complete exercise through the Space Range window. This path walks through every section in the order you need it:

  • scenario metadata, simulation, and universe
  • spacecraft and components
  • collections and teams
  • ground stations and objects
  • the operator brief
  • every question type
  • scenario events and available presets
  • construction, testing, and export

Start the beginner path

Intermediate: convert a Studio mission

First build and test a normal Studio spacecraft mission through the Inventory, Outliner, Properties, and existing Studio tutorials. Then audit that mission for the hardware and ground network Space Range needs, assign the placed spacecraft to teams, and add the exercise layer without rebuilding it from scenario definitions.

This path assumes you already understand the main Studio workspace. It also explains why Construct Scenario can replace an Inventory-built mission and how to avoid that mistake.

Start the intermediate path

Advanced: author with JSON

Define the complete Space Range scenario in strict JSON. This path documents the full file lifecycle and schema: metadata, simulation, universe, stations, spacecraft, components, power and fuel networks, collections, teams, neutral assets, docking, ground and space objects, questions, events, validation, and handoff.

It uses the same structures Studio loads and constructs. It does not require the beginner or intermediate sequence.

Start the advanced path

What every path produces

Each path ends with a tested .zen project that a facilitator can import and run. A minimum useful exercise has:

  • at least one enabled team
  • at least one controllable spacecraft
  • a valid team-to-spacecraft assignment
  • one or more valid ground stations
  • the communications and computing hardware required by the operator workflow
  • a participant brief
  • tested questions and scenario events when the exercise uses them

The authoring method changes. The final validation standard does not.