Designing Whisker 2: From First Click to Final Level

Designing a game isn't just about individual mechanics. It's about crafting the entire experience from the moment someone clicks "Play" to when they finish the last level.

The First 30 Seconds

The first impression matters more than I thought.

When players launch Whisker 2, they see:

1. Title screen (clean, cozy aesthetic, soft music)
2. "Start" button (big, obvious, can't miss it)
3. Fade to Level 1 (no long loading screen)

I learned from Murder Mystery that complicated menus lose players. Whisker 2's start screen has 3 buttons total:

• Start
• Settings
• Credits

That's it. No achievements menu. No stats. No tutorial select. Just "Start" and you're playing.

The Tutorial Problem

I hate tutorial levels. They're boring and players skip them anyway.

But I also playtested with people who had never played Whisker 1, and they were completely lost without explanation.

My solution: The first level IS the tutorial, but it doesn't feel like one.

Level 1 design:

• Only 2 customers
• Only 1 recipe to learn (sandwich)
• Only 3 ingredients visible
• Customer patience timer is super generous (90 seconds)
• Visual hints appear contextually

// Tutorial hints appear based on player action, not forced dialogue
if (playerNearIngredient && !hasPickedUpIngredient) {
    ShowHint("Click to pick up ingredient");
}

if (playerHasIngredient && playerNearCustomer && !hasServedCustomer) {
    ShowHint("Click customer to serve");
}

Players learn by doing, not by reading text boxes.

The Difficulty Curve

This was the hardest part to balance.

Level progression in Whisker 2:

Level	Customers	Recipes	Time Pressure	New Mechanic
1	2	1	Low	None (Tutorial)
2	3	2	Low	Oven introduced
3	4	2	Medium	None (Practice)
4	5	3	Medium	Combos introduced
5	6	3	High	Multiple orders
6	7	4	High	Everything combined

The pattern:

• Introduce new mechanic → Give practice level → Increase difficulty
• Never introduce 2 new things at once

I learned this from watching playtests. When I had "oven + combos" in the same level, people got overwhelmed and quit.

Mid-Game Pacing

Levels 3-4 are the "comfort zone." Players understand the basics and are starting to feel competent. This is where the game needs to feel satisfying, not stressful.

I added what I call "flow moments":

• When you serve 3 customers in a row without mistakes
• When you trigger a combo
• When you finish a level with time to spare

These moments needed to feel GOOD, so I added:

• Sparkle particle effects
• Encouraging voice lines from customers
• Score multiplier visual feedback
• Upbeat music variations

The code for "flow state" detection:

private int consecutiveSuccessfulServes = 0;

public void ServeCustomer(bool wasCorrect) {
    if (wasCorrect) {
        consecutiveSuccessfulServes++;
        
        if (consecutiveSuccessfulServes >= 3) {
            EnterFlowState();
        }
    } else {
        consecutiveSuccessfulServes = 0;
        ExitFlowState();
    }
}

private void EnterFlowState() {
    // Visual feedback
    backgroundParticles.SetActive(true);
    
    // Audio feedback
    music.pitch = 1.1f; // Slightly faster, more energetic
    
    // Gameplay bonus
    scoreMultiplier = 2f;
}

The Challenge Ramp

Levels 5-6 are where I want players to feel challenged but not frustrated.

The key difference:

• Challenge: "This is hard, but I can do it if I play better"
• Frustration: "This is impossible and I don't know why I'm failing"

How I design challenge:

1. Clear failure reasons
   When you lose, you know why (ran out of time, wrong order, missed ingredient)

2. Observable improvement
   You can see yourself getting faster each attempt

3. Player control
   Losses feel like YOUR mistakes, not random bad luck

4. Achievable goals
   Finishing the level is hard but not impossible

I playtested Level 6 about 15 times with different people. The goal was: 70% of players should beat it within 3 attempts.

Too easy → Boring
Too hard → Frustrating
Just right → 2-3 attempts, then satisfaction when you win

The Ending

This might sound small, but the ending matters.

When you beat Level 6, Whisker 2 shows:

1. Victory screen with final score
2. All the customers you served (little character icons)
3. "Thank you for playing!" message
4. Credits with wholesome music

I wanted players to feel accomplished, not just "oh it's over."

I added a little detail: The final customer gives you a thank-you note that says "You're the best chef ever!" with a hand-drawn heart.

One playtester said this made her smile. That's exactly what I wanted.

Designing for Return Players

Some people play Whisker 2 multiple times. For them, I added:

Score attack mode (unlocked after first completion)

• Same levels, but trying to beat your high score
• Leaderboard (local only, no online)
• New challenge modifiers (2x customers, half time, etc.)

Accessibility options (available from start)

• Adjust customer patience timers
• Toggle combo system on/off
• Adjust movement speed
• Colorblind mode for ingredients

These don't affect the core game, but they let different players enjoy it their way.

What I Learned About Player Experience

Every moment teaches players something.

• First 10 seconds → Is this game for me?
• First minute → How do I play?
• First level → Am I good at this?
• Mid-game → Am I improving?
• Late-game → Can I master this?
• Ending → Was this worth my time?

Designing these moments intentionally makes the difference between a game that's just "okay" and a game that people actually remember.

The technical implementation matters. The mechanics matter. But the player's emotional journey through the game matters most.

That's what I think about now when I design: Not just "what can the player do," but "how should the player FEEL?"