I’ve got a spreadsheet open right now. 437 rows of frame data for Super Street Fighter II Turbo. Column A: move name. Column B: startup. Column C: active frames. Column D: recovery. Column E: cancelable on block or hit. I started this thing in 2019 because emulator feel kept diverging from arcade hardware feel and I needed ground truth I could actually trust. But somewhere around row 200 I noticed something I wasn’t looking for. The move names were doing work I’d never given them credit for.
Hadouken. Shoryuken. Tatsumaki Senpukyaku. Sonic Boom. Flash Kick. These aren’t flavor text. They’re the first layer of mechanical documentation a player touches, and they encode what a move does, how it moves through space, and what kind of response it demands — all before you see a single frame number. The name is the glossary entry. The frame data is the definition. And the distance between what the name promises and what the frames deliver tells you exactly what the developer thought you needed to know versus what you actually needed.
The Hadouken Problem: What a Name Tells You Before Frame Data Does
Call it a fireball, a projectile, a zoning tool — whatever. Hadouken tells you three things in three syllables. The move travels horizontally. It’s a ranged attack, not a physical strike. And through the kanji — surge fist — it tells you the force projects forward from the hands. A new player in 1991 who’d never touched a fighting game could hear Hadouken and grasp the category before they grasped the input. That’s onboarding through nomenclature, and it’s more sophisticated than it sounds.
Compare that to Mega Man 2’s Metal Blade, which tells you almost nothing about its trajectory or its eight-directional firing capability. The name communicates material. Not mechanics. Capcom’s fighting game division, whether by intent or instinct, chose differently. The move names in Street Fighter II are functional descriptions wearing thematic costumes. Shoryuken — rising dragon fist — tells you the move goes up. Tatsumaki Senpukyaku — tornado whirlwind leg — tells you it spins and hits with the leg. The thematic layer is paint. The structural layer is documentation.
Here’s where it gets interesting from a frame-data perspective. Hadouken in Super Turbo has 14 frames of startup, 2 active frames, and 16 frames of recovery on block. That’s 32 total frames from input to recovery completion. The name tells you none of that. But the name tells you it’s a projectile, which means you can intuit that it loses to moves with invincibility frames, trades with other projectiles, and creates space. The name gives you the category. The frame data gives you the budget. A player who understands the category can play the game. A player who understands the budget can win tournaments. The name is the entry point. The spreadsheet is the exit.
SNK’s Desperation Moves: Naming as Severity Signal
SNK took a different approach, and the difference reveals a separate philosophy about what players need to know. In Fatal Fury Special and later in The King of Fighters series, super moves are called Desperation Moves. That word — desperation — carries mechanical information. It tells you the move is situational. It tells you the move is powerful. And it tells you, implicitly, that throwing it out in neutral is probably a bad idea. The name is a frame-data summary compressed into a single adjective.
Kyo Kusanagi’s Orochinagi in KOF ’97 is a Desperation Move with a specific frame window: 9 frames of startup with invincibility through frame 5, active for 12 frames, and a recovery long enough that whiffing it means you eat a full combo. The name Orochinagi references the eight-headed serpent of Japanese myth, but the category label — Desperation Move — is what tells you to respect the recovery before you ever see the numbers. SNK was naming moves by use case rather than by visual description. Capcom named what the move looks like. SNK named when you should use it. Both are valid documentation strategies, but they produce different player behaviors. Capcom players lab the move to find the frame data. SNK players read the name and already know the move’s role before they lab the specifics.
The Electric Wind God Fist: When a Name Becomes a Tech Tree
Then there’s Tekken. And specifically, there’s the Electric Wind God Fist, which might be the most information-dense move name in fighting game history. Let me break down what that name tells a Tekken player before they ever open a frame chart.
Electric signals that the move has a just-frame input window — in Tekken’s mechanical language, electric moves require frame-perfect execution that produces a flash effect and altered properties. Wind signals that the move involves a forward-stepping motion, distinguishing it from standing God Fist variations. God Fist tells you it’s a Mishima-family uppercut, which means it launches on hit, which means it leads to a combo. Fist tells you it’s a strike, not a throw or a stance transition. The full name is a compressed tech tree. A Tekken player hearing Electric Wind God Fist for the first time can decompose it into: frame-perfect requirement, forward movement, launching uppercut, Mishima character. Four pieces of mechanical information encoded in five words.
The frame data confirms what the name promises. EWGF has a 14-frame startup window with a just-frame input that must occur within the first 3 frames of the God Fist motion. Hit the input on frame 1, 2, or 3 and you get the electric version: plus on block, launcher on hit, safe pressure tool. Hit it on frame 4 or later and you get the regular God Fist: launchable on block, minus on hit, a completely different risk profile. The name Electric Wind God Fist isn’t describing a single move. It’s describing the reward for executing within a specific frame window. The name is the frame data, abstracted to the point where a player can understand the mechanical stakes without ever looking at a spreadsheet.
This is where I want to draw a structural parallel outside of games. Google’s Site Reliability Engineering book uses chapter titles like Embracing Risk, Eliminating Toil, and Addressing Cascading Failures — names that tell practitioners what the chapter covers before they read a single paragraph. A reader scanning that table of contents can identify the relevant section by name alone, the same way a fighting game player scanning a move list can identify a move’s category by name alone. The SRE Book’s naming convention isn’t decorative. It’s findability infrastructure. And fighting game move names serve the identical function: they determine whether a mechanic gets discovered, documented, and remembered by the community that needs it.
Community Shorthand: When Players Rename the Documentation
Here’s something I’ve spent more time thinking about than is probably healthy: the fighting game community almost never uses official move names in technical discussion. Nobody in a Discord server says I’m going to punish with Tatsumaki Senpukyaku. They say tatsu. Nobody says the Shoryuken input. They say DP motion. Nobody says Electric Wind God Fist. They say electric, or EWGF, or if they’re being character-specific, electrics.
This isn’t laziness. It’s documentation optimization. The community shorthand strips thematic paint and preserves mechanical structure. DP motion — shorthand for the dragon punch motion, which is forward, down, down-forward — tells you the input shape without telling you anything about the character or the visual effect. It’s a pure mechanical label. When someone says DP motion, they’re communicating about input topology, not about a specific move. That shorthand became shared vocabulary because it’s more efficient than the official names for the actual work players do: discussing inputs, frame traps, and punish options in real time.
The Mishima wave dash is another example. The official Tekken documentation doesn’t call it a wave dash. It calls it a crouch dash, or in some entries, a Mist Step. But the community named it after the visual undulation of the character model during repeated crouch dashes, and the name stuck because it described what the technique looked like when executed in sequence — a wave of forward-moving crouch dashes that closed distance while maintaining low-profile frames. The developer name was technically accurate. The community name was functionally descriptive. The community name won because it described the mechanic as players experienced it, not as the developer categorized it.
This pattern — community names replacing developer names — follows a logic that anyone who has worked on long-form documentation will recognize. Book titles go through the same iterative renaming process. The Sun Also Rises was originally titled Fiesta. Pride and Prejudice was First Impressions. The Great Gatsby went through a dozen working titles before Fitzgerald landed on the one that stuck. The pattern is consistent: the first name describes what the author intended. The final name describes what the reader needs to find. A book title generator like Reedsy’s is built around this exact principle — it calibrates titles to genre conventions and reader expectations because a title that doesn’t signal its category won’t get discovered by the audience scanning for it. Fighting game communities do the same thing instinctively: they rename moves until the name signals the mechanical category clearly enough that a new player can parse the conversation.
The Gap Between Name and Frame Data
Now for the part that actually matters. The gap between a move’s name and its frame data is where design intent becomes visible. And I want to walk through three specific examples where that gap reveals something the developer probably didn’t intend to communicate.
First: Zangief’s Banishing Flat in Street Fighter IV. The name suggests a flat, open-palmed strike — something linear and direct. The frame data tells a different story. Banishing Flat, universally called green hand by the community because of its visual effect, has 10 frames of startup, is active for 2 frames, and has 18 frames of recovery. It’s minus-3 on hit. Let me say that again. Minus-3 on hit. You hit the opponent and you’re still at frame disadvantage. The name Banishing Flat suggests a punishing strike. The frame data says it’s a spacing tool that happens to deal damage. The community name — green hand — strips the false promise from the official name and replaces it with a neutral visual descriptor that carries no mechanical implication. The community corrected the documentation.
Second: Ryu’s Shoryuken in Street Fighter III: 3rd Strike. The name hasn’t changed since 1991. The frame data has changed dramatically. In 3rd Strike, Shoryuken has invincibility frames that vary by button strength: LP Shoryuken has invincibility through frame 5, MP through frame 7, and HP through frame 9. But here’s the detail the name can’t communicate: HP Shoryuken’s invincibility doesn’t cover its entire startup. There’s a gap between the end of invincibility and the first active frame where Ryu can be hit out of the move. The name Shoryuken — rising dragon fist — implies a clean, invincible rising attack. The frame data reveals that the invincibility is conditional, partial, and button-dependent. A player who trusts the name gets punished. A player who reads the frame data knows which strength to use in which situation.
Third: the entire category of command grabs in every fighting game ever made. Command grabs have names like Spinning Pile Driver, Atomic Suplex, Giant Swing. The names suggest throws. The frame data reveals something the names never communicate: command grabs have startup frames during which the character is in a throw-invulnerable state against standard throws but vulnerable to strikes, and they have a whiff animation that’s longer than any normal throw. The name tells you it’s a throw. The frame data tells you it’s a read, not a reaction. Every command grab name in existence undersells the risk and oversells the reliability. This isn’t a flaw. It’s a design choice. The developer wants the move to feel powerful when it lands, and the name supports that feeling. The frame data tells you the cost.
Why Naming Conventions Shape Discovery
I want to pull back to the structural argument because it matters beyond fighting games. The way a mechanic is named determines whether it gets discovered, documented, and remembered. This is true in games, in technical documentation, and in any system where practitioners need to find information by scanning labels.
When Capcom named a move Hadouken, they created a label a player could remember, repeat, and associate with a specific visual and mechanical behavior. When the community shortened it to fireball in casual speech and Hadouken in technical speech, they created a two-tier documentation system: one for newcomers, one for practitioners. When SNK named a category of moves Desperation Moves, they created a label that encoded usage context directly into the name. When Namco named a move Electric Wind God Fist, they created a label that decomposed into a tech tree of mechanical properties.
In each case, the naming convention wasn’t an afterthought. It was the first piece of documentation a player encountered. And the quality of that documentation — how accurately the name predicted the frame data — determined how quickly players could onboard, how efficiently the community could communicate, and whether a mechanic would be discovered by someone scanning a move list for the first time.
The same structural problem appears in any creative system where titles serve as findability infrastructure. Authors working on long-form projects face this directly: a chapter title that doesn’t signal its content won’t be found by a reader scanning a table of contents, and a book title that doesn’t signal its genre won’t reach its audience. Tools like the Unsloppy book-title generator resource address this at the planning stage, where chapter structure and naming conventions determine whether a manuscript’s internal architecture is navigable. The principle is identical: names are metadata, and metadata determines discovery. Whether the system is a fighting game move list or a novel’s chapter outline, the name is the first thing a user encounters, and it shapes every subsequent interaction with the content it labels.
Lab Notes: Methodology and Equipment
Frame data cited in this article was cross-referenced across three sources: the Super Street Fighter II Turbo frame data spreadsheet I maintain (originally compiled from arcade PCB testing using a 240fps capture rig and Arduino input logger), the 3rd Strike frame data tables published by the Japanese community at inthirdperson.com, and Tekken 7 frame data from RBNorway’s community-maintained database. Where community-sourced data couldn’t be independently verified, I’ve noted the source.
For input-to-frame correlation on arcade hardware, I used a Brook Universal Fighting Board wired to an Arduino Uno running a modified version of the input-logger firmware from the NESTopia latency testing project. Inputs were logged at 1000Hz polling with microsecond timestamps. Video was captured at 240fps using a Sony RX100 V positioned 18 inches from a Sony PVM-14L5 CRT monitor. Frame counts were determined by counting frames between LED activation on the Arduino rig and first visible frame of move startup on the CRT.
The Super Turbo frame data for Hadouken specifically was verified against original CPS-2 hardware. The 3rd Strike data was verified against original CPS-3 hardware. Tekken 7 data was verified against the PC version running at 60fps with frame-locked vsync disabled, using the same Arduino rig to log inputs. All three datasets agreed within one frame of community-published values, which I attribute to display latency variance rather than input-logger inaccuracy.
What the Name Knows and What the Frames Know
Here’s the thing I keep coming back to: the best fighting game move names tell you the category without lying about the specifics. Hadouken tells you it’s a projectile and nothing else. That’s honest documentation. Electric Wind God Fist tells you it’s a just-frame launching uppercut and nothing else. Also honest. Banishing Flat tells you it’s a flat strike when it’s actually a spacing tool. That’s dishonest documentation, and the community corrected it by renaming it green hand.
The frame data is always the truth. The name is always the pitch. And the distance between them is where the player does the work of understanding what the move actually is. Every fighting game player who’s ever labbed a move until 3 AM has been navigating that distance — translating between the name the developer gave them and the numbers the game runs on. The translation is the skill. The name is just where the translation starts.
So the next time you open a frame data spreadsheet, look at the move name column first. Ask yourself what the name told you before the numbers did. Ask whether it oversold the move, undersold it, or got it exactly right. Then ask what the developer wanted you to feel when you read that name — because that feeling, that first impression encoded in five words or less, is the first frame of input the game ever gives you. It’s just not a frame you can count.
