Assigning Collections and Teams

Collections connect team identities to spacecraft definitions.

Defining collections

"assets": {
  "space": [
    {
      "id": "SC_001",
      "name": "Pathfinder",
      "components": []
    }
  ],
  "collections": [
    {
      "id": "Main",
      "space_assets": ["SC_001"]
    }
  ]
}

A collection can contain one spacecraft or several:

{
  "id": "Blue Fleet",
  "space_assets": ["SC_001", "SC_002", "SC_003"]
}

Defining teams

"teams": [
  {
    "enabled": true,
    "id": 417263,
    "password": "X7M2Q9",
    "name": "Blue Team",
    "key": 42,
    "frequency": 612,
    "collection": "Main",
    "color": "#0050FF"
  }
]

Field	Purpose
enabled	Controls whether the team is constructed
id	Unique numeric team identity
password	Six-character participant access code
name	Display name
key	Initial telemetry cipher key
frequency	Initial radio frequency in MHz
collection	Collection ID assigned to the team
color	Team display color

Always set enabled explicitly. Use a unique ID and password for every team.

Validating the assignment chain

teams[].collection
    ↓ matches
assets.collections[].id
    ↓ lists
assets.collections[].space_assets[]
    ↓ matches
assets.space[].id

For Pathfinder:

Blue Team → Main → SC_001 → Pathfinder

Sharing collection definitions

If Blue Team and Green Team both use Main, Space Range creates a separate Pathfinder instance for each team. The teams do not control one shared spacecraft.

Use a neutral asset when a spacecraft should exist once and be targetable by multiple teams.

Common assignment failures

• duplicate team ID: the later team may not be added
• missing collection: team has no spacecraft
• misspelled spacecraft ID: that spacecraft is skipped
• disabled team: no ground controller or spacecraft is constructed
• empty collection: no spacecraft is assigned

Inspect the Console after construction and confirm the spacecraft list for every team in Operator.

Next, add passive mission objects.