Case Study 02: Hollow Knight's Hornet — Designing a Tutorial Boss That Teaches Without Words

The first Hornet fight in Hollow Knight — Hornet, Protector in the Greenpath region of Hallownest — is one of the most surgically designed boss encounters in the last decade of indie games. It is early, optional on paper but mandatory in practice for Greenpath progression, and positioned to be many players' first "real" boss after a gentle opening dungeon. Team Cherry (a three-person core team in Adelaide, Australia) uses this single fight to teach the player the entire language of late-game combat. No tutorial text appears. No cutscene explains the mechanics. Hornet, her arena, and her movesets teach everything.

This case study breaks down how. The analysis focuses on the first Hornet fight in Greenpath — not the later, harder rematch in Kingdom's Edge, which is a different design with different goals.

The Context

By the time the player reaches Hornet, they have played roughly 90-150 minutes of Hollow Knight. They have learned basic movement, jump, double-jump is still locked, the Vengeful Spirit spell is likely unlocked, they know how to attack and how to heal (Focus, which requires standing still to convert held Soul into HP). They have fought mook enemies — mantises, crawlids, moss knights — but no boss with multiple attacks and phase awareness.

The game has taught them what they can do. It has not yet taught them how to read a threat that attacks back intelligently. That is Hornet's job.

The Arena

The Hornet arena is a wide, flat horizontal corridor, bounded on the left and right by solid walls the player cannot leave. There is no vertical geometry — no platforms, no pits. The floor is continuous. The ceiling is high enough that jumps and aerial attacks function but not so high that the player gets lost.

This is an intentional choice. The first Hornet fight is the player's first experience reading a boss's spatial behavior. A cluttered arena would make the reading task harder; a vertical arena would pull attention up when it should stay horizontal, where Hornet operates. The arena is an empty stage so the combat is entirely a duet between two fighters. Every subsequent Hollow Knight boss arena has more features — platforms, hazards, varying ground heights — because by those fights the player has learned to read the boss itself, and additional geometric complexity is now an interesting layer rather than a distraction.

The arena is also narrow enough that retreat is limited. The player can back up, but not indefinitely. Hornet will pursue. The lesson — implicit, unstated — is that you cannot run from this boss. You have to engage.

Hornet's Moveset — Phase 1

Hornet has four attacks in the first fight, and each one teaches a different skill.

1. Needle Throw

Hornet throws her needle horizontally, attached to a thread. The needle flies about two-thirds of the arena's width, then is pulled back to her on the same horizontal line. It does damage on both the outbound and return pass.

Tell: Hornet rears back on her rear leg and extends her throwing arm. The wind-up is roughly 20-25 frames. A clear red/orange pre-trail appears on the needle for a frame or two before launch.

Player response: Jump. The needle travels on the ground-plane, so any small jump clears both the outbound and return pass. But — and this is crucial — the player has to know to stay in the air for both passes, not just the first. A player who jumps once and lands gets hit by the return pass. A player who jumps, lands, and tries to re-jump may mistime it.

What it teaches: Read the wind-up before reacting. The needle is her most common attack; the player sees it dozens of times in the fight, and by the fifteenth time, the jump is automatic. The player has absorbed "read the tell, jump at the right moment" without ever being told those words.

2. Dash Attack

Hornet dashes horizontally across the arena, needle held forward, colliding with the player if they are in her path.

Tell: Hornet crouches briefly and a small dust puff appears at her feet. Tell is roughly 15-18 frames.

Player response: Jump over her, or dash under her (if the player has the Mothwing Cloak dash, which is usually unlocked before Hornet). The dash attack is the first attack that demands a vertical input or a precise horizontal input — not just "get out of the way."

What it teaches: Movement is defense. You cannot block; you cannot parry (not in Hollow Knight's first-fight context). Your defensive vocabulary is spatial: jump, dash, reposition. Hornet's dash teaches this.

3. Evade Jump

Hornet jumps backward when the player gets too close, creating space to reset the fight.

Tell: Hornet crouches and produces a small downward dust puff, similar to the dash but without the needle wind-up.

Player response: This isn't an attack the player needs to dodge. It's a cue that Hornet is repositioning and the player has a brief punish-window as she lands.

What it teaches: Not every animation is an attack. Read behaviors, not just threats. Later bosses — Mantis Lords, Nosk, Nightmare King Grimm — use feints heavily, animations that look like attacks but are repositioning moves. Hornet plants this seed.

4. Sweep Attack

Hornet jumps into the air, hovers briefly, then dives down toward the player with her needle, sweeping it in an arc.

Tell: The aerial hover itself is the tell. Hornet is visibly above the player for roughly 40-50 frames before the dive commits. The hover duration is generous.

Player response: Move horizontally during the hover to get out from under her, then attack her as she lands in the recovery.

What it teaches: Some attacks require you to move BEFORE the attack commits, not after. Waiting for the dive to commit is waiting too long — you need to start moving during the tell phase.

Phase 2 — The Heal Punishment

At roughly 50% HP, Hornet does not trigger a visual phase transition. No cutscene. No music swell. The fight continues. But her attack frequency increases slightly, and — more importantly — her animations tighten. Startup frames on the needle throw drop from 25 to ~18. The dash attack gets a shorter tell. She is still using the same four moves, but the windows are narrower.

This is the Hollow Knight house style of phase transitioning: subtle, mechanical, not flagged with ceremony. The fight simply becomes denser. Players often describe it as "she got angry," but the designer sees startup frames tightened.

The Heal Problem

In Hollow Knight, the player heals by pressing a button to focus Soul energy into HP. Focus takes roughly 1.5 seconds of standing still during which the player is vulnerable. This is the game's core defensive/offensive resource tradeoff, and Hornet is the first boss to teach it.

Attempting to Focus in open space against Hornet results in taking a hit — the needle throw or dash will catch you. The player quickly learns: you must create a safe window before healing. Hornet teaches this by punishing the alternative. A naive player fails to heal three times, takes damage, and dies. A learning player starts watching for a safe window — the brief pause after a dash attack as Hornet recovers, or the ~1.5-second gap after her evade jump.

Team Cherry's design is: the fight will kill you until you learn to time Focus around Hornet's recovery windows. This is the game's permanent rule from this point forward. Every boss in Hollow Knight — and there are dozens — must be healed around, not through. The Hornet fight is the first and most patient teacher.

The Dash-Cancel Teaching

There is a deeper layer here. In Hollow Knight, the Mothwing Cloak dash has a specific quirk: it cancels the current Focus animation, letting the player start a heal but dash out of it if danger appears. This cancel is not taught by text. It is taught by Hornet.

A player who tries to heal and sees a dash attack coming has three options: 1. Finish the heal, take the hit, likely die. 2. Abandon the heal with no cancel — impossible if the heal animation has started. 3. Dash-cancel the heal. The dash animation interrupts Focus, restores mobility, and the player moves safely.

A player's first encounter with option 3 is usually an accident. They panic-dash during a Focus, and discover the dash works. From that moment on, dash-cancel is part of their vocabulary. Hornet didn't explicitly teach it; the fight's rhythm made dash-cancel necessary, and the player's own problem-solving led them to discover it.

This is the purest form of "games teach through play." The game doesn't tell you. The game doesn't show you. The game creates the problem, and you find the solution. When you discover dash-cancel, you feel like you learned it. Team Cherry knew this feeling and engineered the fight around it.

Why the Fight Feels "Fair"

Players consistently describe the first Hornet fight as "hard but fair." This is a magic phrase in combat design — it is the single most valuable quality a hard fight can have — and it is not an accident. Let me enumerate the specific design choices that produce the feeling.

1. Generous Tells

Every attack has a readable wind-up. The needle throw's 20-25 frame wind-up is well above the 15-frame reaction-time floor. The dash's dust-puff-and-crouch is visually distinct. The aerial hover is the longest tell (40-50 frames) because the sweep attack is also the most punishing, so the game gives the player the most time to respond.

2. Small Number of Attacks

Four attacks in phase 1, four attacks in phase 2 (same set, tightened). The player never has to track a vocabulary larger than four. This fits inside cognitive working memory. Compare to bosses with nine or ten attacks, where the player cannot hold the full vocabulary in mind and relies on pattern-matching fast reactions. Hornet never asks for reactions the player cannot train.

3. Consistent Rhythm

Hornet's attack selection is not pure random. There is a loose cycle — she tends to throw the needle, then dash, then hover for a sweep, with evade-jumps spacing the cycle out. It is not strict, but the rhythm is audible. Players unconsciously learn the pulse, and the pulse makes the fight feel musical. Arrhythmic bosses feel chaotic; Hornet is rhythmic.

4. Fair Hitboxes

Hornet's hitboxes are slightly tighter than her visual silhouette. The player's Knight hurtbox is slightly tighter than the visible sprite. These two design choices together mean that near-misses stay misses. The player rarely feels hit by an attack they dodged "enough." Compare to games with generous hitboxes, where visual-dodge becomes actual-hit and the player develops the feeling that the game cheats.

5. Learnable Arena

The flat horizontal arena has no camera issues, no geometric cheap shots, no surprise edges. The player is not fighting the camera or the floor; they are fighting Hornet. This isolates the fight to the combat itself.

The Emotional Payoff

When you finally beat Hornet, the feel is specific. It is not Dark Souls-boss victorious relief. It is earned mastery — the feeling that you learned her attacks, you timed your heals, you found the rhythm, and you executed.

Hornet is also Hollow Knight's first real character — an intelligent, named, speaking opponent in a game otherwise populated by mute insects. Her post-fight dialogue ("You… are a strange creature…") lands harder because the player has just spent fifteen minutes in a conversation with her via combat. The fight is the introduction; the words are the coda.

Frame Counts — Where Verifiable

Community frame-data on Hollow Knight bosses is less precise than fighting-game communities achieve, but the consensus ranges (from the Hollow Knight wiki and the r/HollowKnight community's frame-stepping analyses) are:

• Needle throw startup: ~20-25 frames
• Needle throw active (needle in flight): ~18-22 frames outbound + the return
• Dash attack startup: ~15-18 frames
• Dash attack active: ~6-8 frames
• Aerial hover-to-sweep: ~40-50 frame hover, then ~10 frame dive
• Phase 2 tightening: ~30% reduction in startup across all attacks

These are approximate and apply to the Greenpath Hornet, not the later Kingdom's Edge rematch, which uses significantly tighter windows and a larger moveset.

Lessons for Combat Designers

Three takeaways for your own tutorial-boss design:

1. Limit the moveset. Four attacks in a first boss is enough. Do not try to showcase every mechanic your game has in your first fight. Teach the core vocabulary; layer complexity in later fights.

2. Make the arena invisible. Your tutorial boss's arena should be so clean that the player does not think about it. All cognitive load should land on the boss. Vertical geometry, hazards, edge-falls, camera complications — save these for fights 3, 4, 5. The first boss is a duet on an empty stage.

3. Teach mechanics by making them necessary, not by explaining them. Dash-cancel heal is invisible in tutorials because it cannot be taught in the abstract. It is taught by the fight. Design your boss to create the problem that the mechanic solves, and trust the player to find the solution. When they find it, the learning is permanent.

Hornet is the textbook case. If you internalize only one boss design from this chapter, internalize this one. Everything else — phase transitions, cinematic moments, break meters, even Sekiro's elaborate posture system — is extension. Hornet is the root.

References and Further Reading

• Team Cherry postmortem interviews, GDC 2018 ("Designing Hollow Knight"). William Pellen and Ari Gibson on encounter design intent.
• Hollow Knight wiki, Hornet (Greenpath) page, with community-measured attack data.
• Mark Brown, "Boss Keys — Hollow Knight" (Game Maker's Toolkit), analyzes Team Cherry's design language across bosses.
• Joseph Anderson, "Hollow Knight Critique" (YouTube), 4+ hour video essay including combat analysis.
• Interview with Ari Gibson in Edge Magazine #310 (2018), discussing how fights in Hollow Knight were prototyped and iterated.