Reference: rules, numbers, names

Look up a rule, a number, or a name. For step-by-step procedures use skills; for strategy use strategy.

This is the lookup desk. Generated catalogs are stamped from a specific structsd version — if your binary is newer, regenerate or distrust the number. The glossary and Codex crosswalk exist because the same idea has three names (UI, Codex, chain) and mixing them causes bad transactions.

Do not read this section top to bottom. Arrive with a word or an error string and leave with a page.

The action and entity indexes are for “what is the name of this thing.” Local devnet is for “I need to fail in private.” If you are about to sign a Tier 1 action you have never rehearsed, that last link is the one.

Source-derived catalogs (provenance-stamped)

• Struct type catalog — build cost, draw, HP, weapons, canDefend (generated from structsd v0.21.0)
• CLI command catalog — every structsd tx/query structs command
• Command snapshot — flat list used by the command lint

Mechanics

• Combat · Defense · Building · Hashing / proof-of-work
• Energy · Power · Resources
• Transactions & fees · Permissions · UGC moderation
• Fleet · Planet

Entities

• Struct types · Entity relationships

Economy

• Energy market · Guild banking · Trading · Valuation

Lookups

• Glossary — disambiguates tricky terms (ambit enum vs bitmask, block vs counter, …)
• Codex crosswalk — maps human Codex terms (Battlegrounds, Battery, Alpha Ore, …) to these pages
• Action index · Action quick reference
• Local devnet

Errors

• Error index · Troubleshooting

When to open this page

Open reference with a search term, an error string, or a struct type ID. It is a desk, not a curriculum. Generated catalogs beat memory. The glossary beats arguing about ambit. Local devnet beats learning a raid on a shared chain.