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.

Discover
FilesBuild
Type TreePrune

Data ExportParse, Validate
and TransformWriteConfig Dataatlas.jsonl10n.json

Code GenerationRender Config
StructuresWriteTyped CodeConfigAtlas

On top of that, Archmage supports team collaboration — an optional workflow for config data editing with no file locks, no binary merge conflicts.

Team CollaborationEdit in
Google SheetsDownload
with ArchmageCommit to
Repository

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, renders config structures into strongly-typed code, and builds ConfigAtlas	View
Team Collaboration	Edit config data in Google Sheets, pull it into the repository as spreadsheet files — no file locks, no binary merge conflicts	View
L10n Pipeline	Collects l10n strings during data export and writes the aggregate to translation files	View
Readability & AI	Turns opaque numbers readable with --readable, and publishes each file’s schema with --schema	View
Filtering Mechanisms	Controls which columns, rows, fields, config entries, and tree nodes are included in data export and code generation	View