sisterbrawl-onboarding-coach

1. Evaluation of the Tutorial Design

Onboarding Trigger: The trigger timing is fundamentally flawed. The TutorialOverlay is displayed when phase === 'character-select' || phase === 'lobby'. This forces the player to practice combat inputs (WASD, Z, V, C) before they are even in the game arena. They cannot see their character perform the actions, completely divorcing the physical input from visual gameplay feedback.
Readability of Hints: Visually, the text is highly readable (large white text on a dark backdrop with clear step indicators). However, the instructions are mechanically misleading.
Clarity of Rules: Clarity is very low. Step 2 (“Attack with Z, Block with V”) secretly requires the player to press Z then V sequentially. If the player presses V first, nothing happens. Step 4 requires a strict Z → Z → C sequence, but any wrong key press silently resets the combo sequence to zero without any UI feedback, easily leaving players confused and stuck.

2. Gaps in the Tutorial Flow

Mechanics without Context: While the tutorial names blocking, specials, and combos, it doesn’t explain their function. It doesn’t tell the player how blocking works (e.g., does it mitigate all damage or just some?), nor does it explain the core win condition of the game (e.g., drain health to 0 vs. ring out).
Missing Character Specifics: Step 3 states “each sister has a unique ability!”, but because the tutorial traps the player in the lobby/character select phase, they haven’t locked in their character or seen the arena, leaving them with no idea what those abilities actually are.
False “Auto-Advance” Setup: Step 4’s data object implies it should auto-advance upon a click (validate: () => true, autoAdvance: true), but the underlying handleKeyDown function aggressively hijacks Step 4, ignoring those properties and forcing the strict key sequence anyway.

3. Usability/Clarity Score

Score: 1 / 5 (The tutorial demands strict, hidden sequential inputs with zero visual feedback, and does so before the player even has visual access to the game arena).

4. Top 2 Specific Findings

Out-of-Context Execution: Players are forced to execute movement and combat inputs against a static UI overlay during the lobby or character-select phase. They never get to see the character move, attack, or block in response to their learning inputs.
Silent Sequence Resets: Steps 2 and 4 require strict, sequential key presses (Z, then V; Z, then Z, then C). The underlying tracking variables (step2Progress and comboStep) have no visual representation in the UI. If a player makes a mistake, the step resets silently, providing zero feedback and creating massive friction to simply start the game.