Neutral assets are full spacecraft definitions constructed once without team ownership. The docking array can connect docking adapters, power interconnects, or fuel interconnects at scenario start.
Creating a neutral spacecraft
Define the spacecraft normally under assets.space, then reference its ID:
"assets": {
"space": [
{
"id": "HUB",
"name": "Shared Hub",
"components": [
{
"class": "Docking Adapter",
"name": "Port A"
}
]
}
],
"collections": [],
"neutral": ["HUB"]
}The hub is constructed once. It is not copied per team and cannot be commanded as a team-owned spacecraft. It can still act as a target when the supported operation permits it.
Adding initial docking
Both spacecraft need compatible named components.
"docking": [
{
"from_team": 417263,
"from_asset": "SC_001",
"from_target": "Dock",
"to_asset": "HUB",
"to_target": "Port A",
"capture_distance": 0.5,
"capture_angle": 5.0
}
]Team-owned endpoints need the team ID and spacecraft asset ID so Studio can identify the correct constructed copy. A neutral endpoint can be addressed by its asset ID.
Connecting power
For a power bridge:
- add a Power Interconnect to both spacecraft
- connect both interconnects to their local
power.bus - add a
dockingentry whose targets are the two Power Interconnect names
Connecting fuel
Use the same pattern with Fuel Interconnect components and local fuel.bus definitions. Physical docking and fuel connectivity remain separate concerns unless both are configured.
Avoiding connection errors
Studio skips invalid connections when:
- an endpoint has no asset ID
- the team ID does not identify the intended constructed copy
- a component name does not exist
- the two component types are incompatible
- a local power or fuel bus does not include the interconnect
Check the Console and test each local network before testing the cross-spacecraft connection.
For component behavior, see:
Next, define scored questions.