Mechanics: combat, energy, building

Mechanics pages are the rules the chain enforces. If a skill and a mechanics page disagree, believe the mechanic and file the skill as wrong. Numbers that come from a generated catalog (struct types, CLI commands) win over prose when the structsd versions match.

Start with energy and power if you are going offline: load versus capacity is the difference between acting and watching. Combat and defense are the raid clock — shields are only vulnerable when the defender’s fleet is off-station or the Command Ship is down. Raids steal ore, never the account (FAQ). Building and hashing are why jobs take hours and why you never block the session on proof-of-work.

Permissions and transactions are how signing actually works: 25-bit flags, free versus paid messages, --gas auto, one sequence number at a time. Skip them and you will burn the first day on parse errors.

Hashing is why mining takes ~17 hours and refining ~34 at typical difficulty: you initiate, you background the compute, you verify later. Fleet on-station versus away is the raid clock. Planet depletion is the other clock. Learn those two clocks before you learn weapon tables.

• Combat – Damage, evasion, raids, weapon systems
• Defense – Survival card: raid loot, shields, minimum posture
• Permissions – 25-bit permission flags, guild rank permissions, UGC moderation hook, handler reference
• Transactions – Free vs paid messages, ante handler routing, gas mechanics
• UGC Moderation – Decentralized name/pfp moderation philosophy, validation rules, audit events
• Resources – Ore, Alpha Matter, energy conversions
• Power – Capacity, load, online status formulas (quick card)
• Energy – Full energy system: units, infusion, substations, allocations, brownout
• Building – Construction, proof-of-work, struct states
• Hashing – Proof-of-work: four struct-bound types, planet ore clocks, raid pause, guild charter
• Fleet – Ships, movement, on-station vs away
• Planet – Exploration, depletion, ore mechanics