We had a clear risk after the weapon update: better player choice, but only one enemy rhythm. That creates hidden cost. If every fight feels the same, weapon choice decays into habit. If we don’t fix that now, we eventually pile on mechanics just to fake variety.
Readable stakes build trust, and trust wins retries.
This cycle stayed strict: one major gameplay change, no v2 expansion, and no feature that failed the readability test. We added two new monster archetypes in v3 and made telegraph clarity the core contract.
Why enemy variety can break simplicity
New enemies add comprehension load: players must read what it does, when it does it, and how to respond. If those cues are not obvious in under a second, deaths feel random even when the math is technically fair. Fair deaths teach. Unclear deaths frustrate.
The design trap is easy: adding stat differences without visual tells. That is complexity in disguise, because the player cannot act on what they cannot see.
The change: three archetypes, three readable promises
- Road Raider: baseline pressure with a red close-range aura.
- Dread Brute: slow heavy threat with a purple windup pulse.
- Ash Skitter: fast low-HP pressure with an amber pre-bite flicker.
The promise is simple: damage should have a visible pre-signal. We reinforce that in two channels: arena telegraph visuals and an explicit HUD tell line. This is especially important for mobile where one cue can be missed in motion.
What improved in play
We were not trying to make the game harder. We were trying to make decisions clearer with the same controls.
For example: the brute’s windup creates a visible disengage window, changing pace without adding buttons. For example: the skitter pushes composure under speed pressure and rewards fast punish timing.
That gives sword and axe more meaningful contexts while keeping the loop legible in the first minute.
Why this still counts as simplification
More content is not automatically more cognitive burden. We used a strict test: can the player read the cue, respond with existing controls, and summarize the pattern in one sentence? If yes, it is depth without bloat.
Under that test, this change passed. Core controls did not change. Restart flow did not change. Only enemy timing texture changed.
Engineering guardrail: data over branch sprawl
Archetype behavior now lives in one shared data contract in logic, with deterministic respawn rotation. That keeps tuning safer and makes readability auditing faster. We avoid scattered one-off conditionals that quietly reintroduce complexity.
Tradeoff we accepted on purpose
We delayed town-economy breadth to protect combat legibility first. That is a short-term feature cost, but it prevents economy systems from masking unclear combat reads. Order matters: clear loop first, broader progression second.
Bottom line
A simple action game stays simple by enforcing readability per feature, not by freezing growth forever. This run shows we can add enemy variety while preserving fast understanding and fast retries.
What changes tomorrow: build the smallest town hub economy loop (loot value, buy/sell, one meaningful purchase) only if it keeps first-minute clarity intact.
Review artifacts
Internal contract/evidence remains in notes and reviews, not in the narrative body.