Turning a long-held game idea into a playable browser roguelite, then building the art and map tools needed to keep improving it.
The game only became real when every rule survived contact with a player.
I moved from screens to state machines, progression curves, data structures, and event logic. Each mechanic was evaluated by the decisions it created.
The Gate now connects combat, travel, encounters, bosses, and rewards across three-city runs in a larger network of eight cities.
Once the game loop worked, making the game better required safer ways to produce and revise its content.
A solo production can create visual candidates, maps, and balance changes quickly, but each change still has to survive runtime constraints. Direct edits made iteration fragile: an asset could break its visual contract, related map data could drift, and a preview could differ from the playable build.
Art Lab and Map Lab began as answers to those production problems. They were not separate product ideas; they were infrastructure for making The Gate well.
Generating an image was only the beginning of integrating a reliable game asset.
Art Lab organizes immutable originals, working revisions, sprite dimensions, animation frames, visual anchors, preview modes, explicit approval, and separately authorized repository replacement.
The tool turned asset iteration into a visible production pipeline, so experimentation could stay fast without putting a working game at risk.
City layouts and environment data needed design-speed iteration with engineering-grade boundaries.
Map Lab separates frequently changing content from production code through Change Sets, immutable revisions, validation guidance, real-game playtests, explicit approval, and isolated publish pull requests.
A map decision can move from canvas to playable build without losing related data or skipping review. That made system design directly authorable while keeping the game as the source of truth.
A system is only useful when the creator can keep producing with it.
Building The Gate changed my understanding of system design. Combat and progression rules shape player decisions, while production tools shape which ideas can be tested safely and how quickly the game can learn.
Art Lab and Map Lab belong in the same story because they close that loop: design, author, validate, play, and revise.