Struct Types

Purpose: AI-readable reference for all buildable Structs. Stats, costs, power requirements, strategic role, and when to build. Struct types use integer IDs (not type-index format); query via GET /structs/struct_type/{id}.

Complete Struct Type Table

All 22 struct types, verified from chain genesis. Power draws are in watts (the chain stores milliwatts; W = chain value ÷ 1,000 — see energy.md — Units). Limit is the per-player build cap (buildLimit; unlimited = stackable).

Special Properties

The generating_rate values above (2/5/10) are the raw chain rate. In the Guild Stack DB this raw value is stored as generating_rate_p, and a generating_rate column is exposed as generating_rate_p * 1000 — read generating_rate_p when you want the per-gram rate quoted here. See integration-notes.md.

Planet struct health: baseline planetary structs (Ore Extractor, Ore Refinery, Orbital Shield Generator, Jamming Satellite, Ore Bunker, Planetary Defense Cannon) have 6 HP; power generators are hardened higher (Field Generator 8, Continental Power Plant 10, World Engine 10) and carry armour (damage reduction 1), so disrupting a planet’s power is a deliberate, costly raid objective. Armour-piercing weapons bypass that reduction (see Battleship). Fleet structs are unchanged: Command Ship 6 HP, all other fleet structs 3 HP.

Planetary Shield Contributions

Planet structs that contribute to your planet’s shield (a higher shield raises raid PoW difficulty for attackers). Shield values are scaled as fractions of the Command Ship rebuild window (BuildDifficulty 200), on top of a base shield of 25:

A planet’s shield = base 25 + the contributions of its online defense structs. One each of all four yields 25 + 25 + 12 + 50 + 13 = 125. Orbital Shield Generator and Ore Bunker (the structs whose only effect is shield) are unlimited, so the practical maximum is power-gated — stack them to harden a planet. The shield only matters while the raid is winnable (the defender’s Command Ship must be offline/destroyed — see combat.md).

Detailed Fleet Combat Properties

All fleet structs (IDs 1-13) deal 2 damage per primary weapon hit. DB-verified values below.

Attack Properties

All primary weapons are blockable and counterable. Armour-piercing weapons (Battleship primary) negate the target’s damage reduction during volley resolution. Armour-piercing is exposed on the struct type as explicit booleans (primaryWeaponArmourPiercing / secondaryWeaponArmourPiercing; chain v0.18.0), so read the flag rather than inferring from class. See combat.md for full targeting and defense mechanics.

Single-target: every fleet weapon has primaryWeaponTargets = 1 (and secondaryWeaponTargets = 1 on the Battleship, Starfighter, and Cruiser) — one struct hit per volley. struct-attack accepts a comma list of target IDs, but a targets = 1 weapon engages only one of them. This is distinct from multi-shot (primaryWeaponShots), which is multiple projectiles at a single target. See combat.md.

Defensive Properties

Stealth Mode: Stealthed structs can still be targeted by structs in the same ambit – stealth only blocks cross-ambit targeting. Attacking instantly deactivates stealth (2 charge to re-activate).

Charge Costs (All Struct Types)

Charge is a single per-player bar (see building.md); these are the costs each action draws from it, not per-struct values.

At 1 charge per block (~6 seconds), plan ~30 seconds of idle accumulation between 5-charge actions. The bar is shared across all the player’s structs.

Weapon Target Ambits

Each weapon can only hit specific ambits. The primaryWeaponAmbits field is a bitmask (Space=16, Air=8, Land=4, Water=2).

Threatened-By Matrix

Which structs can attack into each ambit:

Battleship’s armour-piercing primary covers Land and Water (ignoring damage reduction on Tanks and generators); its guided secondary reaches Space.

The Command Ship can attack into any ambit but must first move there via struct-move.

Ambit Bit-Flag Encoding

The possibleAmbit field (and the weapon-reach fields primaryWeaponAmbits / secondaryWeaponAmbits) is a bit-flag integer encoding which ambits apply. Each bit is 1 << enum:

The four combat ambits are Water/Land/Air/Space; none (1) is a placeholder and local (32) is the Command Ship’s current-ambit flag. Values are combined. For example:

• 6 = Land (4) + Water (2) — most planet structs
• 8 = Air only — air fleet units
• 16 = Space only — space fleet units, orbital planet structs
• 30 = Space (16) + Air (8) + Land (4) + Water (2) — Command Ship only

This reach bitmask is a different scale from the ambit enum (none=0, water=1, land=2, air=3, space=4, local=5) used by transaction messages and a struct’s stored operatingAmbit. When initiating a build or moving, pass the enum (the CLI accepts the name space|air|land|water), not the bitmask number. See building.md — Ambit Encoding and api/integration-notes.md — Ambit.

Categories

Fleet (IDs 1-13)

Fleet structs are combat units that operate in the fleet. The Command Ship (type 1) is special: only 1 per player, required for all planet operations, and can operate in any ambit.

Planet (IDs 14-22)

Planet structs are infrastructure built on a claimed planet. Require fleet on station and Command Ship online.

Build Requirements Summary

activateCharge = 2, buildCharge = 8, defendChangeCharge = 1 for all struct types (charge is a per-player bar). Most planet structs and the Command Ship are limited to 1 per player; Orbital Shield Generator and Ore Bunker (shield-only) and fleet combat structs (IDs 2-13) have no build limit.

Query

• Single type: GET /structs/struct_type/{id} (id = integer, e.g. 1, 2)
• All types: GET /structs/struct_type
• CLI: structsd query structs struct-type [id] or structsd query structs struct-type-all
• With cosmetics: Webapp GET /api/struct-type/{id}/full?class={class}

See Also

• entity-relationships.md — Struct ownership, location
• power.md — BuildDraw, PassiveDraw, capacity
• building.md — Build process, proof-of-work, -D flag
• building.md — Status field (numeric) — Canonical decoder for the numeric struct status bitmask
• resources.md — Conversion rates, ore flow
• combat.md — Combat struct roles
• valuation.md — Struct valuation
• schemas/entities/struct-type.md — Full schema
• reference/action-quick-reference.md — Build actions