Structs Building

Procedure

1. Check requirements — Player online, sufficient Alpha Matter, valid slot (0–3 per ambit), Command Ship online, fleet on station (for planet builds). Query player, planet, fleet.
2. Initiate build — structsd tx structs struct-build-initiate [player-id] [struct-type-id] [operating-ambit] [slot] --from [key-name] --gas auto --gas-adjustment 1.5 -y.
3. Proof-of-work — structsd tx structs struct-build-compute [struct-id] -D [difficulty] --from [key-name] --gas auto --gas-adjustment 1.5 -y.
4. Complete build — structsd tx structs struct-build-complete [struct-id] --from [key-name] --gas auto --gas-adjustment 1.5 -y.
5. Activate — structsd tx structs struct-activate [struct-id] --from [key-name] --gas auto --gas-adjustment 1.5 -y.
6. Optional — Move, set defense, or activate stealth as needed.

Commands Reference

Limits: 1 PDC per player, 1 Command Ship per player. Command Ship must be in fleet. Generator infusion is IRREVERSIBLE. Common tx flags: --from [key-name] --gas auto --gas-adjustment 1.5 -y.

Verification

• structsd query structs struct [id] — status = Online (or Built/Offline if not activated)
• Struct appears in planet/fleet struct list

Error Handling

• “insufficient resources” — Check Alpha Matter; use structsd query structs player [id].
• “power overload” — Add capacity before activating; going offline blocks all actions.
• “invalid slot” — Slot 0–3 per ambit; check existing structs.
• “Command Ship required” — Command Ship must be online for planet builds.
• “fleet not on station” — Move fleet or wait before building on planet.

See Also

• knowledge/mechanics/building.md
• knowledge/mechanics/power.md
• knowledge/entities/struct-types.md
• knowledge/entities/entity-relationships.md