Structs Exploration

Important: Entity IDs containing dashes (like 3-1, 4-5) are misinterpreted as flags by the CLI parser. All transaction commands in this skill use -- before positional arguments to prevent this.

Procedure

1. Check eligibility — structsd query structs planet [id]. Exploration requires currentOre == 0 (planet complete). One planet per player at a time; old planet is released on explore.
2. Explore — structsd tx structs planet-explore --from [key-name] --gas auto --gas-adjustment 1.5 -y -- [player-id]. New planet: 5 ore, 4 slots per ambit. Fleet moves to new planet. When ore = 0, planet status = complete, all structs destroyed, fleets sent away.
3. Move fleet — To relocate between planets: structsd tx structs fleet-move --from [key-name] --gas auto --gas-adjustment 1.5 -y -- [fleet-id] [destination-location-id].
4. Chart — Query planet, grid, attributes to evaluate resource potential and strategic value.

Commands Reference

Rules: Starting ore = 5. New planet when ore = 0. One planet per player at a time. Common tx flags: --from [key-name] --gas auto --gas-adjustment 1.5 -y.

Verification

• structsd query structs planet [id] — new planet has currentOre = 5, maxOre = 5
• structsd query structs planet-all-by-player [player-id] — planet list updated
• structsd query structs fleet [id] — fleet location matches destination (onStation/away)

Error Handling

• “planet not complete” — Deplete ore (currentOre = 0) before exploring.
• “fleet away” — Fleet must be available; wait for return or check fleet state.
• “invalid destination” — Use valid location ID; query grid for options.

See Also

• knowledge/mechanics/planet — Planet properties, ore, slots
• knowledge/mechanics/fleet — Fleet movement, on-station rules
• knowledge/entities/entity-relationships — How entities connect