From Chaos to Clockwork: The Journey to Building TickForge
TickForge started as a late-night obsession. I wanted to build RPG combat that was cinematic, skill-based, and 100% reproducible. No random quirks. No “it worked on my machine.” Just pure, deterministic simulation.

Jump to sections
I’ve always believed the best ideas come from frustration — and TickForge is proof of it.
In every RPG system I built over the past few years, something always broke determinism. Even with fixed update loops, two runs of the same battle produced different results. As an engineer, that was unacceptable.
So I started designing a new kind of framework — one that would treat time as a law, not a variable.
The Spark
The idea for TickForge started during a prototype for Machinata Blitz — a turn-based boss-battler where timing mattered. I wanted inputs graded like Paper Mario, visuals orbiting like Persona 5, and yet results that could be replayed tick-perfectly. Unity’s default systems just weren’t built for that kind of determinism.
So, I began from scratch.
Phase by Phase
Phase 1: CoreSim
I wrote a fixed-tick simulation engine with a seeded RNG and ordered execution. It became the “clock” that every other system listens to.
Phase 2: ROCS
I wanted combat to feel rhythmic. ROCS divides an arena into 12 orbit sectors — players and enemies rotate oppositely. It’s part combat, part choreography.
Phase 3: ODIS
This was my favorite — deterministic timing input. You press at just the right tick window, and ODIS grades you. Perfect inputs always align, even on different frame rates.
Phase 4–5: CRE and GS3S
CRE handles damage math and ensures identical outcomes across replays. GS3S adds data-driven stats and “realm laws” to make balance tunable.
Phase 6: Integration
All pieces came together in one demo — deterministic combat, replay validation, and a full battle loop.
The Breakthrough Moment
The first time I ran a replay log and got identical results line by line, I knew I had something special. It wasn’t just a framework — it was a proof of determinism in Unity.
What Comes Next
TickForge Pro will bring in the tactical layer—turn systems, AI commanders, and card abilities. Then we’re porting to Unreal Engine for deterministic C++ support.
The dream is to make TickForge the de-facto standard for deterministic RPG simulation — for solo devs, indie teams, and studios alike.
Reflection
TickForge isn’t just about code. It’s about rethinking how we build combat: not as chaos, but as clockwork. Every action, every tick, every outcome—predictable, precise, and fair.
If you’ve ever wanted your combat to feel intentional down to the millisecond, that’s what TickForge is built for.
TickForge v1 (Base Edition) launches soon on the Unity Asset Store.
Follow my devlogs, behind-the-scenes notes, and progress updates at thealiraza.com and on YouTube.
Need help with a similar technical challenge?
I help teams diagnose performance bottlenecks, optimize WebGL delivery, and turn difficult interactive builds into production-ready experiences.
Contact Ali Raza