Randy The Racoon

steam game technical design

Use cartoony weapons, run over humans, take down the Goose Mafia, drop giant snowballs into crowds, fly your stunt car across a packed island. A Simpsons Hit & Run-inspired sandbox where the fun comes from embracing the chaos.

Role Solo technical designer & developer
Inspired by Simpsons Hit & Run
Focus Emergent chaos, immersive world
Status Released on Steam

The short versionFun through chaos

pillar

Let the player discover

Fun through an immersive world rather than complex mechanics, with the player discovering it themselves.

approach

Systems that collide

Connected systems and simple tools create emergent gameplay, and I leaned into the chaos instead of controlling it.

validation

Heavy playtesting

Playtests made sure players never got lost or confused without a tutorial or voiceover.

Deep diveHow I designed it

Randy jumping onto a pig with a broom

Embracing the chaos

Emergent gameplay. Weapons, vehicles, crowds and NPCs all interact, so players create their own stories.

Immersion over complexity. A world that's fun to poke at beats a deep mechanic that needs explaining.

One unique feature. Randy the raccoon reacts to player actions, which gives it a lot of personality.

Learning from other games, for the right players

inspiration

Simpsons Hit & Run was the reference for the open-world sandbox feel, so I studied why it worked instead of copying it.

audience

I made design decisions based on the target audience: players who want to mess around, not master a system.

systems

Missions, NPCs, dialogue, a minimap and a physics-based car are all connected, so one action can ripple through the world.

Randy's island

Design challenge: introducing the world organically

What I ruled out. A voiceover or intro text would've been easy, but it broke a core pillar: let the player discover the world themselves.

What I did instead. NPCs explain the world through dialogue, so players pick things up as they play.

The trade-off. It meant heavy playtesting to make sure players didn't get lost or confused. It ended up being the right call.

Playtesting loop

Watch players no hints, no explanations
→
Spot confusion where do they get lost?
→
Adjust dialogue NPCs guide instead
→
Test again repeat

My partWhat I did

01
design

Organic onboarding

NPC dialogue introduces the world instead of a voiceover or intro text

02
design

Emergent chaos

Weapons, vehicles and crowds that combine into unscripted moments

03
design & gameplay

Missions & NPCs

Designed and built the mission and NPC systems that run the world

04
gameplay

Car feel

A physics-based car controller tuned for stunts

05
design

Audience-first decisions

Choices made around who the game is for

06
production

Playtesting

Heavy playtesting to keep players oriented without a tutorial

Want the code side? See the programming breakdown →

Looking backTakeaways

Don't fight the chaos

Giving systems room to collide produced better moments than scripting them.

Protect your pillars

If I hadn't written down the core mechanics, I would have lost sight of what made the game unique.

Test with real players

Playtests showed where players got lost, which is where my assumptions were wrong.

GalleryScreenshots

Library capsule Screenshot 1 Screenshot 2 Screenshot 3 Screenshot 4 Screenshot 5 Screenshot 6 Screenshot 7 Screenshot 8 Screenshot 9