From separate systems to one playable loop
During early development, Zombie Citizen was not yet a complete survival shooter. Movement, combat, resources, weapons, progression, and interface feedback existed as separate pieces. The immediate challenge was connecting them into a run players could understand without a developer standing beside them.
The target loop was simple to describe: move through the arena, survive pressure, collect materials, improve your build, and keep going. Making each step readable took coordinated work across programming, art, and interface design.
What mattered: The first playable did not come from one feature. It came from making combat, feedback, resources, and progression understandable as one loop.
Showing the player what changed
We started with the information surrounding the player. That included health, movement and interaction icons, weapon icons, resource counts, active power-ups, and the first HUD.
Infection, wounds, and changing conditions also needed clear feedback. During a fast run, the player should be able to answer three questions at a glance:
How much danger am I in?
What resources and upgrades do I have?
What can I do next?
That work made the interface part of the game loop rather than decoration around it.
Connecting combat, resources, and progression
Under the interface, we tuned movement speed and melee damage, added level-ups and buffs, and made enemies drop crafting materials. Weapons began moving toward distinct gun types with their own statistics and crafted bonuses.
We also rebuilt ranged combat around physical projectiles for both players and ranged enemies. Projectiles made timing and positioning easier to read while giving each weapon more room to develop its own identity.
Once these systems connected, defeating an enemy could create a resource decision. That resource could support an upgrade, which could change the next wave.
Building interface and mechanics together
One lesson from this stage still guides the project: a system is not finished when the code works. Players need to notice it, understand its effect, and know what action is available next.
That is why level-up and crafting screens developed alongside their underlying systems. Weapon and resource icons had to match the mechanics. Damage and health feedback had to remain understandable while enemies were moving.
Later playtests showed us which signals worked and which assumptions made sense only to the team.
What this foundation enabled
This was early development, not the public alpha. It established the foundation for the first arena, enemy spawning, escalating waves, mobile builds, the pre-alpha polish pass, and structured public playtesting.
Future updates will show how those systems changed once more players started interacting with them.
