Formats
Developer-facing field reference. Each page traces a stat field from its storage (DB column, rule-file key, or binary layer byte) through the code that consumes it, with worked numeric examples. Player-facing "what does it mean in game" summaries live in the features and content sections — this is where the exact types, defaults, formulas, and code paths are.
| Page | Contents |
|---|---|
| Plant fields | Plant rule file format (GenXY), every rule field with type/default/consumer, the growth state machine, validation checks |
| Ore fields | minerals + mineralconfigs columns, the node-generation formulas, node lifecycle and persistence, extraction mechanics |
| Deployable fields | How deployables are identified, capsule↔object pairing, and the aggregate fields that drive placed objects |
| Zone files | The binary terrain layer files: struct layouts, flag bits, save cycle, and what lives in the DB instead |
Conventions:
- GenXY is the settings serialization used for rule files and
entitydefaults.options(token characters perGenxyToken.cs; see Plant fields → file format). - Code paths are relative to
src/. - Where a value is a constant (not data), the file and constant name are given.
Pages
- Deployable fields — How deployables are identified, capsule-object pairing, and the aggregate fields that drive placed zone objects.
- Ore fields — The minerals and mineralconfigs tables, node-generation formulas, node lifecycle, and extraction mechanics.
- Plant fields — Plant rule file format (GenXY), every rule field with type, default, and consumer, plus the growth state machine.
- Zone files — The binary terrain layer files: naming, struct layouts, flag bits, the save cycle, and what lives in the DB instead.