Development retrospective
From greybox to a playable survival loop
How Chancla Fury's first day established movement, combat, mobile controls, and a testable web build.
Starting with the loop
Chancla Fury began as a small survival-game experiment: move, avoid a growing crowd, and create enough space to fight back. The first implementation focused on a greybox that could answer basic questions quickly. Was movement readable? Did the arena feel fair? Could the same controls work with a keyboard and on a phone?
Making the prototype testable
The early work added repeatable checks around movement and combat instead of treating the prototype as disposable. That decision mattered later. New characters, weapons, bosses, and account systems all continued to depend on the original loop, so having a stable baseline made iteration less risky.
A web game from the beginning
The game was packaged as a browser-first experience from its first day. Touch controls and compact layouts were not postponed until the end. They became constraints that shaped the interface, enemy readability, and the amount of information we could show during a run.
What we learned
A prototype does not need final art, but it does need a clear question. This one proved that the central joke and the survival loop could carry a real game. The next step was to give that loop a cast, a setting, and progression worth returning to.