I treat “game feel” and “how the game treats you” as one continuum, and this manual walks it from 33 milliseconds to seven years.
Swink called the sensation of controlling a digital object the most overlooked phenomenon in HCI, and the field mostly stopped reading at a hundred milliseconds. The sensation of being governed by a digital system (measured by it, priced by it, recognized by it over months) is the same phenomenon at longer exposure, and it gets even less credit. A hitstop and a ranked split are both the game telling you what your actions meant. So Section 01’s chapters are ordered by timescale, shortest to longest, because the structure is the argument:
01.01 Game feel. The first 33 milliseconds. The smallest statements: hitstop, recoil, the weight of a death. A time-to-kill number is a philosophy of dying. I shipped inside two studios that held opposite ones, both coherent.
01.02 Game UX. The session. Can they do it, do they understand it, does it feel good? In that order, no skipping. Web UX serves a user who wants to leave. We serve a player who wants to stay, and that changes most of what the web taught us.
01.03 Onboarding. The first hours. Marketing is a promise the game has to keep, launch day is part of the tutorial, and somewhere in the first session there’s a moment where the player nods. Everything before that nod is running on credit.
01.04 Competitive systems. The season. A ladder is a contract about what gets measured and what being measured costs. Keeping that contract explicit is the whole job. That, and the one thing a matchmaker must never be allowed to optimize.
01.05 Metagame. The account. One match record, opened up, powers tier lists, mastery, social resumes, and a third-party ecosystem no first-party roadmap could buy. Also: what the battle pass genuinely fixed, and what it traded the dice for.
01.06 Social systems. The community. The scoreboard is a values statement, probably the purest expression of this preface. What a game makes visible, players optimize, so choose what you display like it’s doctrine (because it is).
01.07 Live ops. The years. Who owns a shipped system: you, or the people living in it? The patch is the product, a season is a promise structure, and a reversal budget is insurance you buy hoping never to learn why you needed it.
After that comes Section 02, Design Vision: the template I use to take a game from a blank page to a first playable, including the Inside-Out Model for deciding what to build first, next, and later. Then Section 03, Getting Unstuck: twenty-one process tricks for getting unstuck, in three suits. No theory, just moves.