Workflow

Modern game architectures rely heavily on config data: weapon damage, quest rewards, monster HP, and beyond. Adding even a single field requires synchronizing two distinct targets: the data loaded at runtime and the code used to access it. Doing this manually is repetitive, inefficient, error-prone, friction-heavy, and tedious.

Archmage eliminates all this pain by automating the workflow over the same source files: archmage export produces runtime data while archmage struct generates strongly typed code. This section covers the two pipelines and the mechanisms that shape their output.

Discover
FilesBuild
Type TreePrune

Data ExportParse, Validate
and TransformWriteConfig Dataatlas.jsonl10n.json

Code GenerationRender
TemplatesWriteTyped CodeConfigAtlas

Topic	Description
Data Export	Parses and validates config files, then writes configurations to the output directory, alongside atlas.json	View
Code Generation	Parses config files to extract data types, then renders templates into strongly typed code, and builds ConfigAtlas	View
Filtering Mechanisms	Controls which columns, rows, fields, config entries, and tree nodes are included in data export and code generation	View
L10n Pipeline	Collects l10n strings during data export and writes the aggregate to translation files	View
Readability & AI	Turns opaque values readable with --readable, and publishes each file’s schema with --schema	View