"Make it fun" sounds like a vibe, not a spec. But fun is something you can reason about - if you know what your player actually returns for. For a roguelike audience, that's meaningful decisions and runs that never feel the same twice.
Design toward what they come back for
The combat loop is the demo - it gets someone to try once. What keeps a roguelike player is the economy around it: 33 buff types drafted between waves so every run forks differently, a territory layer to fight over, and sigil meta-progression that makes losing still feel like progress. None of that is decoration. Each system exists because the target player's idea of fun is choice, and choice is what I built toward.
Players forgive a simple loop wrapped in rich decisions. They abandon a deep loop with nothing to decide.
Treat fun as a requirement
Naming the fun makes it buildable, not vague:
- Decide what your audience returns for - here, variety and meaningful trade-offs.
- Build the systems that produce it (the draft, the economy, the meta-progression), not just the core action.
- Measure against replay: if runs blur together, the fun requirement isn't met yet.