Why Game Menus Are the Most Overlooked Design Argument in Any Game

Every game has a moment before the game begins. You press start, the title card fades, and something appears on screen—a grid, a cursor, a blinking text field, a clock. This is the menu. We have been trained to treat it as logistical overhead: the thing you click through to reach the thing you want. But the menu is where the designer’s assumptions about you become legible. Not in the narrative. Not in the art direction. In the interface. The menu is the only place in a game where the rules of engagement are stated explicitly before play begins—where the game tells you what kind of attention it expects, how much of your time it plans to occupy, and whether it considers you a guest or an employee.

Most players never read menus as design. They experience them as friction. But friction is design. The distance between pressing a button and seeing its result is an argument about how much the designer trusts you to act deliberately. The number of clicks between you and a save file is an argument about whether your time belongs to you or to the game. The fact that you must name your character before you can move is an argument about whether identity is something you bring to the game or something the game assigns to you. These are not neutral interface decisions. They are ideological positions rendered as buttons and grids.

The Attache Case: Inventory as Spatial Anxiety

Resident Evil 4’s inventory system is the most overanalyzed mechanic in survival horror, and I am about to overanalyze it again, because it deserves it. Leon’s attache case is a grid. Items occupy rectangles of varying size. You rotate them, nestle them alongside one another, and rearrange them every time you pick up something new. The grid is finite. The items are awkward. The act of managing the case takes longer than the act of shooting the ganados that drop the items.

Here is what the grid argues: that survival is not about what you carry but about what you can fit. The grid makes inventory a spatial problem, not a numerical one. Most games before RE4—and most games after—treated inventory as a weight limit or a slot count. You can carry twelve items. You can carry fifty kilograms. The specific shape of each item is irrelevant. The attache case rejects this abstraction. A rifle is not “one item.” It is a long, horizontal rectangle that will not fit next to your shotgun unless you rotate it vertical, and if you rotate it vertical, it blocks the column where you wanted to put the first aid spray.

[annotation: The attache case grid in RE4. Items are irregular rectangles. The grid is tight. The cursor moves in discrete steps. Every placement decision locks out adjacent space. The interface communicates scarcity through geometry, not numbers.]

This is an argument about anxiety under pressure. A weight limit says “you must choose what to carry.” The attache case says “you must choose how to arrange what you carry, and the arrangement itself is a cost.” The cognitive load of tetris-ing your inventory is the mechanic’s point. The game does not want you to feel that you have enough. It wants you to feel that you almost have enough, that one more pickup will require a sacrifice, that the space itself is hostile. The grid is not a container. It is a pressure chamber.

The remake of RE4 softened this. The grid is still present, but items are less irregular, the case is larger, and the crafting system lets you consolidate ammunition into compact stacks. The remake’s interface argues something different from the original: that inventory tension should be a flavor, not a tax. This is a defensible position. It is also a completely different argument about what survival horror should feel like, and it was made entirely at the menu level, without changing the story, the enemies, or the core combat loop.

The Stamp and the Clock: Papers, Please and Interface as Labor

If RE4’s inventory grid makes scarcity spatial, Papers, Please makes morality clerical. The game’s interface is a desk. You drag documents, align stamps, check dates, and cross-reference rulebooks. The clock ticks. The queue of applicants grows. Every approval or denial is a stamp—a single, physical, satisfying mechanical action—and every stamp is a moral decision compressed into a bureaucratic gesture.

The menu in Papers, Please is the game. There is no layer beneath the interface where the “real” game happens. You are not playing a character who stamps documents. You are stamping documents. The interface does not represent labor. It is labor. And the clock at the top of the screen is not a timer. It is a wage argument. You earn money per processed applicant. You need money for food, heat, medicine. The clock is the mechanism that converts your moral decisions into economic pressure. You want to be careful, to read each document closely, to catch the forgeries. The clock says: you cannot afford to be careful. The interface says: your carefulness has a price.

[annotation: The Papers, Please desk interface. The clock dominates the upper right. The rulebook is a separate tab you must open and close. Every document is draggable. The stamp is the only object that makes a sound. The interface trains you to associate moral action with manual effort.]

This is what makes the stamp mechanic ideologically distinct from a dialogue-wheel moral choice. When a BioWare game asks “save or sacrifice,” the decision is abstract, weightless, reversible by reload. When Papers, Please asks you to deny entry to a woman whose papers are expired, the decision is physical. You drag the denial stamp to her passport. You press the button. The stamp lands. The ink dries. She leaves. The interface makes you perform the refusal with your hands. There is no “undo” for a stamp. The game does not autosave before moral decisions. It autosaves after them. The menu is where ethics become manual labor, and the argument is that bureaucracy is not a system that processes moral decisions—it is a system that replaces them with procedural actions until the person performing them stops feeling the weight.

The Naming Screen: Identity as First Contract

Before you manage inventory, before you stamp passports, before you even see the game world, many games ask you to type a name. This is the naming screen, and it is the first contract between designer and player. The game asks: who are you? And the interface constrains how you can answer.

Some games give you a blank field. Some give you a list. Some generate a name for you and ask you to accept it. The constraints are not technical. They are ideological. A blank field says: bring yourself to this game. A list says: choose from the selves we have prepared. A generated name says: you are who we say you are, and your only agency is to accept or resist.

Disco Elysium does not let you name your character. You wake up with a name already assigned—Raphael Ambrosius Costeau—and the game’s opening hours are partly about discovering what that name means, what it has done, and whether you want to keep it. The naming screen is replaced by an amnesia screen. You do not choose who you are. You choose whether to remember. The Thought Cabinet extends this: thoughts arrive as cards you can equip, and equipping them changes your character’s internal monologue, available dialogue options, and skill behavior. Identity is not chosen at the start. It is accrued, revised, and sometimes inflicted. The game’s interface treats consciousness as inventory you cannot drop—items that take up space in your mind, that can be equipped and unequipped but never fully discarded, and that shape what you are capable of perceiving.

Kentucky Route Zero does something quieter. The game gives you names to choose from at various points, but the names are not your character’s name. They are the names of other people—coworkers, strangers, figures from the past. You are assigning identities to characters you do not control, filling in gaps in a story you are witnessing rather than driving. The naming screen in Kentucky Route Zero is not about self-expression. It is about complicity. The game asks you to name someone, and by naming them, to accept responsibility for their existence in the narrative. The interface makes you a co-author, but not of yourself. Of the world.

That same discipline applies to title and framing decisions: before publishing, editors need a way to test a heading promises the same thing the article actually delivers, which is where novel title ideas that fit the project can function as a planning aid rather than a substitute for domain evidence.

[annotation: Kentucky Route Zero’s naming prompts appear mid-dialogue, not on a title screen. The cursor blinks in a text field embedded in the conversation. There is no confirmation prompt. Once you type and press enter, the name is committed. The interface treats naming as a narrative act, not a pre-game configuration.]

The naming screen is also where game design faces the same constraint problem that external ideation tools attempt to solve for writers. A tool that generates novel title ideas from genre and tone parameters is doing something structurally similar to what a game naming menu does: it defines the boundaries of acceptable output before the user engages. The difference is that a game naming interface does this to a person who is about to inhabit the identity being constrained, while an external generator does it for a creator who will evaluate the output from outside. Both are arguments about the relationship between constraint and authorship—but only the game menu forces the user to live inside the constraint it imposes.

Constraint, Authorship, and the Interface as Argument

The naming screen connects to a broader principle that runs through every menu type I have discussed: the interface is where constraint becomes ideology. A game’s title is also a naming decision—a contract between creator and audience that precedes the content. “Resident Evil” argues that horror is domestic. “Papers, Please” argues that bureaucracy has a voice. “Disco Elysium” argues that decadence is a place. These are not descriptions. They are positions, and they are made before the player touches a single mechanic.

The same principle applies to the tools creators use to arrive at those positions. A parameterized title generator like the one documented at Reedsy’s book title generator lets you input genre, tone, and core conflict to produce title candidates. The interface is a set of constraints—dropdown menus, radio buttons, text fields—that frame naming as a system of parameters. This is structurally identical to a game’s naming screen: both define the boundaries of acceptable output before the user engages. The generator’s output is only useful when the author recognizes that the title is not a label—it is the first argument the work makes. The tool can produce candidates, but the ideological decision of which candidate fits the argument remains human.

The Authors Guild has made a related argument about what happens when naming decisions are delegated to machines. Their best practices guide for authors navigating AI tools treats naming as a profession-defining act—one that machines can approximate but cannot author, because the ideological weight of a title cannot be parameterized without flattening the very contract it establishes. The guide’s concern maps directly onto game interface design: a generated character name is not the same as a chosen character name, because the act of choosing is what makes the name meaningful. When the system assigns identity, the player’s relationship to that identity shifts from authorship to negotiation.

Sometimes that shift is the point. Disco Elysium’s pre-assigned name is a deliberate argument about amnesia and self-reconstruction. Kentucky Route Zero’s naming prompts are a deliberate argument about complicity and authorship. In both cases, the menu is making an argument the designer intended. But when a naming screen defaults to a generated name without thought—when the constraint is simply a default the designer did not evaluate—the menu is making an argument the designer did not intend, and the player is living inside it without recognizing the contract they have been forced to sign.

The Save Dialog: Time as Territory

One more menu, because it is the one that reveals the most. The save dialog. Every game that has one is making an argument about your time, and the argument is encoded in the interface.

A save-anywhere system says: your time is yours. You can leave when you want. The game will wait. A checkpoint system says: your time is partly ours. You can leave, but only at moments we designate, and if you leave mid-section, you lose progress. A save-only-at-inns system says: your time is ours, and rest is a resource you must purchase. An autosave-only system says: you cannot leave. You can stop playing, but the game decides when your progress counts. You are not in control of your own exits.

Outer Wilds has no manual save. The game autosaves when you die, and you die every twenty-two minutes when the sun explodes. The save system is the time loop. Your progress is your knowledge, which persists across loops, but your physical state resets. This is not a save system bolted onto a game. It is a game built around a save system. The interface argues that the only persistent resource is what you know, and that knowledge is the only thing worth saving. The game does not let you save your position because your position does not matter. It lets you save your understanding because your understanding is the only thing that changes.

Compare this to a game that lets you save anywhere but also lets you reload anywhere. The quicksave-quickload loop is an argument about failure: that failure is reversible, that the player should never have to live with consequences, that the optimal play pattern is to save before every decision and reload if the outcome is unsatisfactory. This is a philosophical position. It says: the game does not trust you to learn from mistakes. It trusts you to avoid them through save-scumming. The interface has decided that consequence is optional, and it has made that decision at the menu level, without a single line of dialogue or a single frame of cutscene.

[annotation: A comparison of save interfaces. Outer Wilds: no save button, autosave on death, death is periodic and inevitable. Quick-save games: save button mapped to a hotkey, instant, unlimited. The difference is not convenience. It is whether the game considers failure a state to be erased or a state to be incorporated.]

The Designer’s Responsibility: Menus Are Never Neutral

Here is the problem with treating menus as overhead: every default is a decision, and every decision is an argument. When a designer ships a menu they did not think about, they have not avoided making an argument. They have made one accidentally, and accidental arguments are the worst kind because the designer cannot defend them, the player cannot read them, and the critic cannot evaluate them. They simply exist, shaping the player’s relationship to the game without anyone acknowledging that shaping is happening.