Player-First Design: The TwinZilla Philosophy
How we design games at TwinZilla — from Bagabond’s hex tactics to live ops — with players, fairness, and long-term support at the center.
At TwinZilla, player-first isn’t a slogan on a pitch deck. It’s the question we ask before we add a feature, tune a number, or ship a build:
Will this make the player’s next minute more fun, fair, or understandable?
If the answer is “maybe, if they read the manual,” we keep working.
What player-first actually means for us
Clarity over noise
Players should always know whose turn it is, what an ability will do, and why they won or lost. Surprise can be delightful in story; in systems, unexplained surprise often feels like a bug.
That’s why projects like Bagabond emphasize readable turn flow and enemies that telegraph intent before they act. You get tension — without feeling cheated.
Depth over feature checklists
We’d rather ship one mechanic that players master and love than ten shallow systems nobody remembers.
In tactics games, depth comes from positioning, resource tradeoffs, and synergies — not from menus full of redundant options. Our design reviews ask: can we cut this and the game gets better?
Respect for player time
People play between meetings, after school, or at midnight before bed. Sessions can be short. Progress should feel meaningful even when time is limited.
Dungeon runs, wave-based rooms, and clear rewards in Bagabond are built for “one more room” energy — not mandatory grinding to have fun.
Long-term support, not launch-and-leave
Games aren’t fireworks. They’re relationships.
From day one we think about:
- Balance patches — data-driven abilities and encounters designers can tune
- Community feedback — what’s confusing, what’s delightful, what’s broken
- Live operations — events, content drops, and fixes when players stick around
Player-first design includes planning for the Tuesday three months after launch, not only the hype trailer.
Technology in service of fun
Our engineering choices exist so designers can iterate and players feel smoothness:
- Unity for rich 2D presentation and cross-discipline workflows
- Data-driven actions and encounters so tuning doesn’t require a code deploy for every tweak
- Separation of rules and presentation so animation and UI don’t silently change combat outcomes
We don’t chase tech trends to impress other developers. We adopt tools when they remove friction for the team or improve the play experience.
Bagabond: philosophy in practice
Bagabond is our turn-based tactical game in development — and it’s where many of these ideas meet:
| Principle | In Bagabond |
|---|---|
| Readable combat | Hex grid, phased turns, clear targeting |
| Fair challenge | Enemy intents shown before execution |
| Meaningful runs | Rooms, waves, loot, and build experimentation |
| Designer velocity | Scriptable content, editor tooling, internal docs |
We’re not claiming it’s finished. We are claiming the goal is clear: a game we’d want to play ourselves — the same joy we felt discovering tactics and RPGs years ago.
Working with other creators
TwinZilla also supports partners through consultation, analysis and optimization, and full game development. Player-first applies there too: we’ll tell you when a feature serves metrics more than people, and we’ll help fix it when it doesn’t.
If you’re building something ambitious and want a studio that thinks in players and worlds, not just milestones — say hello.
The filter, summarized
Before we ship, we ask:
- Is the next action obvious?
- Is failure understandable?
- Is success satisfying?
- Will we still be proud to support this in six months?
When those answers line up, we’re on the right path.
That’s player-first at TwinZilla. Not perfection on day one — care on every day after.