Foundation
Core vision and rules foundations documented
AFB’s mecha theme, shared-deck structure, Pilot identity, and Full Sync endgame were established as the project foundation.
AFB: Full Sync
Development Timeline
Major milestones in the growth of AFB: Full Sync.
A look at the major steps behind the game’s systems, testing, card work, and production direction.
Testing
Simulation lab foundation completed
The project gained deterministic runs, metrics, and validation so design questions could be tested instead of guessed.
Source structure
Project source stack reconciled
The working source stack was organised into a clearer source of truth for mechanical authority, stack interactions, and card-writing consistency.
Rules structure
Rules reference and card wording contract created
Separate references were created for mechanical resolution and card wording consistency, helping future card text, timing, object terms, zones, and combat interactions stay aligned.
Production
Full-pool production direction established
The project moved toward full-pool generation, audit, rewrite, trimming, and playtest selection instead of treating a small cut-down deck as the main design path.
Pilot design
Pilot creation method formalised
A repeatable Pilot design tool was created to test whether each Pilot works as a real gameplay engine.
Pilot design
Starter Pilot directions selected
The first ten starter Pilot directions became the working baseline for card support, counters, and lane identity.
Card pool
Wide-net card candidate pool expanded
A large raw card candidate pool was created for simulation, audit, cutting, merging, rewriting, and future playtest selection.
Testing
Simulation campaigns and reporting expanded
Simulation campaigns, reporting, telemetry, and decision-data tooling were expanded so design questions could be made visible and easier to test.
Card database
Card database and versioning workflow formalised
Card records began tracking identity, versions, design roles, audit state, relationships, rulings, balance notes, and playtest evidence.
Repair workflow
Versioned card repair workflow added
Failed card candidates can now be preserved, linked, and repaired instead of deleted, keeping design history useful for future decisions.