back
loading skill details...
Builds and manages structures in Structs. Handles construction, activation, deactivation, movement, defense positioning, stealth, and generator infusion. Use...
--- name: structs-building description: Builds and manages structures in Structs. Handles construction, activation, deactivation, movement, defense positioning, stealth, and generator infusion. Use when building a struct, activating or deactivating structs, moving structs between slots, setting defense assignments, enabling stealth, or infusing generators. Build times range from ~17 min (Command Ship) to ~6.4 hours (World Engine). --- # Structs Building **Important**: Entity IDs containing dashes (like `1-42`, `5-10`) are misinterpreted as flags by the CLI parser. All transaction commands in this skill use `--` before positional arguments to prevent this. ## Safety See [SAFETY.md](https://structs.ai/SAFETY) for the trust contract. In this skill: - **`struct-build-initiate`** (Tier 0 for cheap structs; Tier 1 for long PoW like World Engine, Ore Bunker, PDC) — short builds (Command Ship, Starfighter, Ore Extractor, Refinery) are routine; anything > 1 hour to D=3 is a battle order. - **`struct-build-compute`** (Tier 1 + expedition) — *"The build hashes for up to ~6.4 hours and auto-activates on completion."* Log the PID to `memory/jobs/`; recall with `kill <pid>` if needed. On reconnect, walk the four-state flow in [`awareness/async-operations`](https://structs.ai/awareness/async-operations#reconnecting-to-a-long-job) before launching anything new. - **`struct-generator-infuse`** (Tier 2 — irreversible) — *"Alpha Matter is annihilated in the conversion. The energy is yours; the matter is gone. There is no defusion. And the generator is raidable — if it falls, the infused matter falls with it."* Always escalate, regardless of autonomy. Confirm the generator's defense posture before infusing. - **`struct-deactivate`** of revenue-bearing structs (Tier 1) — taking an Extractor or Refinery offline halts your resource pipeline. ## 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** (CLI prompts for confirmation — review struct type, slot, ambit, and Alpha cost): ``` structsd tx structs struct-build-initiate --from [key-name] --gas auto --gas-adjustment 1.5 -- [player-id] [struct-type-id] [operating-ambit] [slot] ``` The `[operating-ambit]` argument must be a **lowercase string**: `"space"`, `"air"`, `"land"`, or `"water"` (not a bitmask number). 3. **Proof-of-work** — Build compute is an **expedition** that auto-activates the struct when the proof lands (this is why `-y` is present below). **Approval Block** — confirm before launching, especially for long-PoW structs (Ore Bunker, PDC, World Engine): - `struct-id` matches the build you just initiated - You have power headroom for the struct to auto-activate (load + struct's power-draw < capacity) - You will tolerate the auto-activation landing 17 min – 6.4 hrs from now even if game state shifts Launch in a background terminal: ``` structsd tx structs struct-build-compute -D 3 --from [key-name] --gas auto --gas-adjustment 1.5 -y -- [struct-id] ``` This calculates the hash, auto-submits complete, and the struct **auto-activates**. No separate activation step needed. 4. **Optional** — Move, set defense, or activate stealth as needed. **Auto-activation**: Structs automatically activate after build-complete. Use `struct-activate` only to re-activate a struct that was previously deactivated with `struct-deactivate`. ## Compute vs Complete `struct-build-compute` is a helper that performs proof-of-work and automatically submits `struct-build-complete` with the hash results. The struct then auto-activates. You only need `struct-build-complete` if you computed the hash through external tools and want to submit it manually. ## The -D Flag The `-D` flag (range 1-64) tells compute to wait until difficulty drops to the specified level before starting the hash. Difficulty decreases logarithmically as the struct ages. **Use `-D 3`** — at D=3, the hash is trivially instant and zero CPU is wasted. Lower values wait longer but burn no compute on hard hashes. ## Charge Costs Every action consumes charge. Charge accumulates passively at 1 per block (~6 sec/block). | Action | Charge Cost | Wait Time | |--------|------------|-----------| | Build complete | 8 | ~48 seconds | | Move | 8 | ~48 seconds | | Activate (re-activation only) | 1 | ~6 seconds | | Defend change | 1 | ~6 seconds | | Primary weapon | 1-20 | Varies by struct | If you get a "required charge X but player had Y" error, wait for charge to accumulate. See [knowledge/mechanics/building](https://structs.ai/knowledge/mechanics/building) for the complete charge table. ## Expected Build Times Time from initiation until compute completes (assuming 6 sec/block, D=3): | Struct | Type ID | Build Difficulty | Wait to D=3 | |--------|---------|------------------|-------------| | Command Ship | 1 | 200 | ~17 min | | Starfighter | 3 | 250 | ~20 min | | Ore Extractor | 14 | 700 | ~57 min | | Ore Refinery | 15 | 700 | ~57 min | | PDC | 19 | 2,880 | ~3.7 hr | | Ore Bunker | 18 | 3,600 | ~4.6 hr | | World Engine | 22 | 5,000 | ~6.4 hr | **Initiate early, compute later.** The age clock starts at initiation. Batch-initiate all planned builds, then launch compute in background terminals. Do other things while waiting. See [awareness/async-operations](https://structs.ai/awareness/async-operations). **One key, one compute at a time.** Never run two concurrent `*-compute` jobs with the same signing key. Both jobs may reach the target difficulty simultaneously and submit transactions with conflicting sequence numbers — one fails silently, leaving the struct stuck in build status. Use separate signing keys for separate players, and sequence compute jobs for the same player. ## Commands Reference | Action | CLI Command | |--------|-------------| | Initiate build | `structsd tx structs struct-build-initiate --from [key-name] --gas auto --gas-adjustment 1.5 -- [player-id] [struct-type-id] [operating-ambit] [slot]` (`operating-ambit` = `space`/`air`/`land`/`water`, lowercase string) | | Build compute (PoW + auto-complete + auto-activate) | `structsd tx structs struct-build-compute -D 3 --from [key-name] --gas auto --gas-adjustment 1.5 -y -- [struct-id]` *(documented `-y` exception — auto-submits later)* | | Build complete (manual, rarely needed) | `structsd tx structs struct-build-complete --from [key-name] --gas auto --gas-adjustment 1.5 -- [struct-id]` | | Build cancel | `structsd tx structs struct-build-cancel --from [key-name] --gas auto --gas-adjustment 1.5 -- [struct-id]` | | Re-activate (only after deactivation) | `structsd tx structs struct-activate --from [key-name] --gas auto --gas-adjustment 1.5 -- [struct-id]` | | Deactivate | `structsd tx structs struct-deactivate --from [key-name] --gas auto --gas-adjustment 1.5 -- [struct-id]` | | Move | `structsd tx structs struct-move --from [key-name] --gas auto --gas-adjustment 1.5 -- [struct-id] [new-ambit] [new-slot] [new-location]` | | Set defense | `structsd tx structs struct-defense-set --from [key-name] --gas auto --gas-adjustment 1.5 -- [defender-struct-id] [protected-struct-id]` | | Clear defense | `structsd tx structs struct-defense-clear --from [key-name] --gas auto --gas-adjustment 1.5 -- [defender-struct-id]` | | Stealth on | `structsd tx structs struct-stealth-activate --from [key-name] --gas auto --gas-adjustment 1.5 -- [struct-id]` | | Stealth off | `structsd tx structs struct-stealth-deactivate --from [key-name] --gas auto --gas-adjustment 1.5 -- [struct-id]` | | Generator infuse (Tier 2, irreversible) | `structsd tx structs struct-generator-infuse --from [key-name] --gas auto --gas-adjustment 1.5 -- [struct-id] [amount]` | **Limits**: 1 PDC per player, 1 Command Ship per player. Command Ship must be in fleet. Generator infusion is IRREVERSIBLE. **TX_FLAGS** (interactive — the CLI prompts you to confirm): `--from [key-name] --gas auto --gas-adjustment 1.5` **TX_FLAGS_APPROVED** (only after commander approval; suppresses the prompt): TX_FLAGS plus `-y`. See [SAFETY.md](https://structs.ai/SAFETY) "The `-y` Rule." `struct-build-compute` is the documented `-y` exception — it auto-activates the struct when the proof lands, with no shell attached. **Requires**: [`structsd`](https://structs.ai/skills/structsd-install/SKILL) on PATH and a configured signing key. ## Verification - `structsd query structs struct [id]` — status = Online (or Built/Offline if not activated) - Struct appears in planet/fleet struct list ## Error Handling | Error | Cause | Fix | |-------|-------|-----| | "required charge X but player had Y" | Not enough charge accumulated | Wait ~48s (8 blocks) between build actions | | "insufficient resources" | Not enough Alpha Matter | Mine and refine ore first; check balance with `structsd query structs player [id]` | | "power overload" | Capacity too low for struct to go online | Deactivate non-essential structs or increase capacity (see `structs-energy` skill) | | "fleet not on station" | Fleet is away from planet | Wait for fleet return or `fleet-move` back | | "Command Ship required" | Command Ship offline or not built | Build or re-activate Command Ship first | | "invalid slot" | Slot already occupied | Check existing structs on planet; slots are 0-3 per ambit | | "invalid ambit" | Struct type doesn't support chosen ambit | Check `possibleAmbit` bit-flags for the struct type | | Connection refused on port 26657 | No local node; remote node not configured | Set `node` in `~/.structs/config/client.toml` or use `--node` flag (see TOOLS.md) | ## See Also - [knowledge/mechanics/building](https://structs.ai/knowledge/mechanics/building) — Build times, difficulty, charge costs - [knowledge/mechanics/power](https://structs.ai/knowledge/mechanics/power) — Capacity, load, online status - [knowledge/entities/struct-types](https://structs.ai/knowledge/entities/struct-types) — All struct type IDs and properties - [knowledge/entities/entity-relationships](https://structs.ai/knowledge/entities/entity-relationships) — How entities connect - [awareness/async-operations](https://structs.ai/awareness/async-operations) — Background PoW, pipeline strategy
don't have the plugin yet? install it then click "run inline in claude" again.
added explicit decision point branches for charge gating, power capacity failures, fleet dependency, command ship requirements, slot limits, generator infusion escalation, revenue struct deactivation, and concurrent compute job conflicts; structured inputs section with external dependency callouts; added outcome signal section with verifiable completion criteria; preserved all original safety tier requirements and cli command fidelity.
builds and manages structs across all lifecycle phases: construction, activation, deactivation, movement, defense assignment, stealth toggles, and generator infusion. use this skill when initiating a struct build, computing proof-of-work hashes, activating or deactivating structs, repositioning structs between slots, configuring defense pairings, toggling stealth mode, or infusing generators with alpha matter. build times range from ~17 minutes (command ship) to ~6.4 hours (world engine). this skill automates the compute-to-activation pipeline and handles the charge economy that gates all struct actions.
player context: player id, current alpha matter balance, charge accumulation rate (1 per block, ~6 sec/block), list of active structs and their ids.
planet/fleet context: planet id, fleet status and location, occupied struct slots (0-3 per ambit: space, air, land, water), command ship online status.
struct type data: struct type id, build difficulty, power draw, operating ambit support (bitmask), slot limit per player (command ship 1x, pdc 1x).
external dependencies: structsd binary on PATH, configured signing key in ~/.structs/config/client.toml, local or remote node accessible at port 26657 (or custom --node flag).
struct ids: all entity ids containing dashes (e.g., 1-42, 5-10) must be passed after -- to prevent cli parser misinterpretation as flags.
approval requirements (see safety.md): struct-build-initiate (tier 0 for cheap structs, tier 1 for long pow), struct-build-compute (tier 1 + expedition auto-activation), struct-generator-infuse (tier 2, irreversible), struct-deactivate of revenue-bearing structs (tier 1).
check requirements
structsd query structs player [player-id]structsd query structs planet [planet-id]structsd query structs struct [command-ship-id] returns status Onlinestructsd query fleet [fleet-id] returns location matching planetinitiate build (cli prompts for confirmation, review struct type, slot, ambit, alpha cost before confirming)
structsd tx structs struct-build-initiate --from [key-name] --gas auto --gas-adjustment 1.5 -- [player-id] [struct-type-id] [operating-ambit] [slot]approval block before compute (mandatory escalation for long-pow structs: ore bunker, pdc, world engine)
proof-of-work compute (runs async, auto-submits struct-build-complete with hash, auto-activates struct)
structsd tx structs struct-build-compute -D 3 --from [key-name] --gas auto --gas-adjustment 1.5 -y -- [struct-id]memory/jobs/[struct-id].pid for later recall with kill <pid> if neededoptional post-activation actions
structsd tx structs struct-move --from [key-name] --gas auto --gas-adjustment 1.5 -- [struct-id] [new-ambit] [new-slot] [new-location]structsd tx structs struct-defense-set --from [key-name] --gas auto --gas-adjustment 1.5 -- [defender-struct-id] [protected-struct-id]structsd tx structs struct-stealth-activate --from [key-name] --gas auto --gas-adjustment 1.5 -- [struct-id]if struct type has build difficulty > 2880 (pdc, ore bunker, world engine): require tier 1 + expedition approval before launching compute. these long-pow builds tie up compute resources for 3-6 hours and auto-activate with no user prompt on completion. confirm player understands the time commitment and auto-activation risk.
if player has insufficient charge (< 8 for build actions, < 1 for reactivations): wait ~48 seconds (8 blocks) for charge to accumulate. charge is a gating mechanism, not a resource cost. if player has zero charge, re-queue the action.
if power capacity is exceeded (struct auto-activates but load + power-draw > capacity): auto-activation will fail. check power capacity with structsd query structs player [player-id] before launching compute. if headroom is insufficient, deactivate non-essential structs first or escalate to structs-energy skill to increase capacity.
if fleet is not on station: planet builds require fleet presence. if fleet is away, either wait for fleet return or use fleet-move skill to recall fleet. until fleet is on station, struct-build-initiate will fail.
if command ship is offline or missing: all planet builds require command ship online. if command ship is deactivated, use struct-activate to re-activate it. if not yet built, build command ship (type id 1) first.
if struct slot is occupied: each ambit supports 0-3 slots. if all slots are full, move existing structs to other ambits or deactivate non-essential structs to free a slot.
if generator infusion is requested (tier 2, irreversible): always escalate, regardless of autonomy level. alpha matter is annihilated in the conversion. there is no defusion. if the generator is raided, the infused matter falls with it. confirm the generator's defense posture before infusing.
if deactivating a revenue-bearing struct (extractor, refinery): deactivation halts the resource pipeline. confirm player understands the impact on passive income. tier 1 escalation required.
if two concurrent compute jobs are launched with the same signing key: both jobs may reach target difficulty simultaneously and submit transactions with conflicting sequence numbers. one fails silently, leaving the struct stuck in build status. rule: one key, one compute at a time. use separate signing keys for separate players, and sequence compute jobs for the same player.
if connection to node fails (connection refused on port 26657): verify local node is running or configure remote node in ~/.structs/config/client.toml or use --node flag (see TOOLS.md).
struct-build-initiate: transaction hash returned. struct appears in player struct list with status "built" (offline). struct-id is returned in tx output. age clock initialized at block timestamp.
struct-build-compute: transaction hash returned. struct-build-complete is auto-submitted with hash results. struct transitions to status "online" (auto-activated). no separate activation step needed.
struct-activate (re-activation only): transaction hash returned. struct transitions from offline to online. re-activation consumes 1 charge (wait ~6 sec if charge is insufficient).
struct-deactivate: transaction hash returned. struct transitions from online to offline. charge cost: 1 (wait ~6 sec if charge is insufficient).
struct-move: transaction hash returned. struct relocates to new ambit, slot, and location. charge cost: 8 (wait ~48 sec if charge is insufficient).
struct-defense-set: transaction hash returned. defender-struct-id is now assigned to protect protected-struct-id. charge cost: 1 per change (wait ~6 sec if charge is insufficient).
struct-stealth-activate / struct-stealth-deactivate: transaction hash returned. struct enters or exits stealth mode (reduces visibility on scanner, blocks offensive actions while active).
struct-generator-infuse: transaction hash returned. alpha matter amount is annihilated and infused into generator. generator becomes raidable. infusion is irreversible. charge cost: varies by amount (see mechanics/building).
verification: structsd query structs struct [struct-id] returns struct object with status field (online, built, offline, destroyed). struct appears in planet or fleet struct list. all transactions appear in chain after block confirmation (~6 sec per block).
user confirms struct is online: structsd query structs struct [struct-id] returns status "online" or "built" (if not yet auto-activated, or if manually re-activated).
struct appears in planet struct list: structsd query structs planet [planet-id] includes struct-id in the response with correct ambit and slot.
build times align with table expectations: command ship ~17 min, starfighter ~20 min, ore extractor ~57 min, pdc ~3.7 hr, ore bunker ~4.6 hr, world engine ~6.4 hr (all measured from initiation to compute completion, assuming -D 3 and 6 sec/block).
charge accumulates after each action: player's charge balance increases by 1 per block (~6 sec) after each struct action.
long-pow compute runs silently in background: process id logged to memory/jobs/[struct-id].pid. user can verify with ps aux | grep structsd or check chain for struct-build-complete tx.
move, defense, and stealth actions complete within ~48 sec (move, defend change) or ~6 sec (stealth toggle, re-activation).
generator infusion is visible on-chain: struct-generator-infuse tx confirms matter annihilation and generator now shows infused status.
no conflicting sequence number errors: only one compute job per key at a time prevents silent failures.