THIS IS YOUR CAPTAIN DEV BLOG: MAKING FLIGHT FUNNY

The first time someone laughed at my game, I was sitting at my desk at two in the morning, watching a playtester on Discord try to land a 737 with one engine on fire and a flight attendant screaming about the snack cart. They didn't laugh at the screaming. They didn't laugh at the fire. They laughed when the autopilot voice, which I had recorded in my closet using a USB microphone duct-taped to a sock, calmly announced "destination reached" as the plane skidded sideways across a runway and came to rest in a duty-free shop. That was the moment I realized comedy in games is not about jokes. It's about timing.

I have been working on This Is Your Captain for about fourteen months now. It started as a small project to teach myself a new physics system, and it became the thing I wake up thinking about. The pitch is simple. You are a deeply unqualified pilot in charge of an aircraft full of unhappy passengers, and your job is to get them somewhere, ideally alive, while running an in-flight service that involves announcing things over the PA, dealing with mechanical problems, and occasionally throwing peanuts at people. It is supposed to be funny. That last part has been the hardest design problem of my career.

Why comedy games usually fail

Most attempts at comedy in games fall flat for the same reason. The developer wrote jokes. Jokes are great in writing. They are great in standup. They are great in films and TV shows where the timing and delivery are controlled by humans who have studied for years how to make a sentence land. In a game, the player controls the timing. The player decides when to push the button, when to look at the screen, when to skip the dialogue. You cannot write a joke and expect the player to deliver it correctly, because they are not your performer. They are your scene partner, and they did not read the script.

Most comedy games try to solve this by being relentless. They throw a joke every three seconds, assuming that some of them will land based on volume alone. This works for about twenty minutes and then becomes exhausting. Borderlands does this. The Stanley Parable does it better, but only because the script is structured around the player's resistance to the script, which is a different trick entirely. Most other attempts produce that specific feeling of watching someone try too hard at a party. You stop laughing not because the jokes got worse, but because you became aware of the effort behind them.

The other failure mode is the opposite. Some games try to be funny by being weird. They put a banana in a hat and assume that's enough. It isn't. Weird is not funny. Weird is just weird. Without a contrast against something normal, there's nothing for the weirdness to push against. A banana in a hat is funny if the banana is wearing the hat to a job interview. The hat alone is just a hat.

What actually works

I spent a long time studying games that actually made me laugh, and I noticed a pattern. The funniest moments in games are almost never written. They emerge from systems. Goat Simulator is the obvious example. The game itself is just a physics sandbox with a goat in it. The comedy comes from the player doing something reasonable, like trying to lick a person, and the physics responding in a completely unreasonable way, like flinging the person into orbit. The developer didn't write that joke. They built a system flexible enough to produce jokes the player could discover.

Surgeon Simulator works the same way. The controls are intentionally broken in a specific direction. Every input you make is filtered through a hand that doesn't quite obey you, and the comedy comes from the gap between your intention and the result. You meant to pick up a scalpel. You picked up the patient's heart instead. That gap, the distance between what you tried to do and what actually happened, is where most comedy lives in games.

Untitled Goose Game took a different angle. The goose itself is not funny in any meaningful way. It's just a goose. What's funny is the situation. You are a goose with goals, and your goals involve ruining the day of every human in the village. The comedy comes from the absurd seriousness with which the game treats your honking war crimes. The villagers react with appropriate alarm. The to-do list reads like a corporate task tracker. The contrast between the mundane structure and the actual content is the joke, and that joke renews itself every time you cross off a new item.

I keep coming back to four principles when I'm designing for comedy. Timing, escalation, unexpected outcomes, and player agency for screwing up. Timing means the system has to deliver the punchline at the right moment, not when the writer thought it would land. Escalation means each beat needs to be slightly worse than the last one, building pressure until the release. Unexpected outcomes means the player needs to be surprised by what happens, even when they caused it. And player agency for screwing up means the player has to be the one creating the disaster, because you laugh harder at the things you broke yourself.

Aviation is the wrong subject for comedy

I picked the worst possible subject. Real aviation is not funny. It is a profession built on checklists, sterile cockpits, and a rigorously enforced culture of avoiding distraction. Every funny thing that happens on a real plane happens despite the system, not because of it. The flight attendants are trained to be calm. The pilots are trained to be boring. The announcements are written to be reassuring. There is nothing inherently comedic about a Boeing.

That's actually the point. The contrast between the seriousness of real aviation and the absurd chaos of an arcade flight game is where the comedy can live. If I just made a wacky plane game with cartoon graphics, it wouldn't work. It would feel like a kids' show. But if the game treats itself like a real aviation simulator, with proper instrument panels and authentic-sounding radio chatter and a pre-flight checklist, and then immediately violates every one of those expectations by having the autopilot try to land in a parking lot, the gap between the form and the content does the comedy work for me.

I spent weeks watching real cockpit voice recordings, reading FAA incident reports, and listening to actual ATC chatter. Not because I wanted to make the game realistic, but because I needed to know what I was breaking. You can't subvert a convention you don't understand. The real reason airline pilots say "souls on board" instead of "passengers" is haunting and serious. The reason my pilot says "souls on board" while the cabin pressure gauge is ticking down toward the red zone is funny precisely because I learned the original meaning first.

Passengers as characters

The biggest design breakthrough came when I stopped thinking of passengers as obstacles and started thinking of them as characters. Early prototypes had passengers as a number. You had forty souls on board. They had a satisfaction meter. The meter went down when bad things happened. It was a system, and systems are not funny by themselves.

Then I added a guy named Gerald. Gerald is in row twelve, seat C. He has been on this flight for an hour. His meal preference is vegetarian, which the airline has failed to honor. He has pressed the call button six times. He is not violent. He is not even particularly angry. He is just persistent in a way that becomes funnier the longer you ignore him. Eventually, if you keep ignoring Gerald, he stands up during turbulence and starts walking toward the cockpit to discuss the meal situation in person.

Gerald changed the whole game. Once I had one named passenger with a clear personality and an escalating set of demands, the game became a comedy. The flight wasn't about flying anymore. It was about Gerald, and the eight other named passengers I added after him, and the way their small problems compounded into chaos while you were trying to keep the plane in the air. The comedy was structural. The player wasn't being told a joke. They were caught in a sitcom they had to fly out of.

This is the principle I keep landing on. Comedy in games needs characters because characters give the player something to react to. A system without characters produces simulations. A system with characters produces stories. And funny things mostly happen in stories, not in simulations.

The announcement system

The other piece I'm most proud of is the in-flight announcement system. The player has a microphone. They can press a button and read from a list of pre-written announcements, or they can record their own. The list contains the standard ones, like welcoming passengers aboard, advising them to fasten their seatbelts, and informing them of the cruising altitude. It also contains some that I had a lot of fun writing, like apologizing for the smell, explaining why the plane is upside down, and asking if anyone in row fourteen is a doctor or, failing that, a mechanic.

The funny part is the timing. The player decides when to make the announcement. The system doesn't force them. So you get these moments where everything is on fire, the plane is descending, Gerald is at the cockpit door, and the player calmly presses the button to inform passengers that beverage service has been temporarily suspended. The player created that joke. I just gave them the components.

I went back and forth on whether to let players record their own announcements. There's a real risk that voice input becomes a way for players to be tedious instead of funny. But I decided to keep it because the funniest playtests have been the ones where the player commits. They put on a pilot voice. They explain the situation in detail. They thank the passengers for flying with us today. The contrast between their measured tone and the visible disaster is where the comedy multiplies, and I couldn't have written that better than they perform it.

What I had to cut

A lot of things I thought would be funny weren't. I had a sequence where the plane would lose all its luggage during takeoff, with suitcases spilling out of the cargo hold and bouncing across the runway. On paper, that's a great visual gag. In practice, it happened at the start of the flight, before the player had any emotional investment in the situation, and it just felt random. Random is not funny. Random is noise.

I also had a feature where birds would occasionally hit the windshield. Real bird strikes are a serious problem for aviation, and I thought playing with that fear would land. It didn't. The birds felt mean. There's a difference between comedy that involves chaos and comedy that involves cruelty, and bird strikes landed on the wrong side of that line. I cut them.

The biggest cut was a multiplayer mode. I spent two months building a co-op version where one player flies and the other manages the cabin. It worked technically. It just wasn't as funny as single player. When two people are sharing the chaos, they can blame each other. The comedy depends on you being responsible for everything, on every disaster being your fault. Splitting the responsibility split the laughter, and I shelved the mode for a possible expansion later.

Why I'm still doing this

Comedy is hard, and aviation comedy is harder, and solo development on a comedy game might be the worst project structure for getting honest feedback. Nobody wants to tell the developer that their joke didn't work. Playtesters will laugh politely. Friends will say it's great. The only honest signal you get is the laugh that happens when the player has forgotten you're watching. Those laughs are rare, and you have to design specifically to produce them.

But when it works, it really works. Last week I watched someone fly a plane backwards across the Atlantic because they got confused about the heading indicator, while Gerald demanded a complimentary upgrade and the autopilot insisted the destination had been reached three times in a row, and the player was laughing so hard they couldn't breathe. They didn't know they were being filmed. The laugh was real. That recording is on my desktop, and I watch it sometimes when I'm tired and I can't remember why I'm doing this.

If you want to read more about why I think games like this matter, my piece on Getting Over It covers some of the same territory from the opposite direction. Foddy made frustration into content. I'm trying to make incompetence into comedy. They're closer than they sound.

The plane is still in the hangar. Gerald is still in row twelve. Beverage service has been temporarily suspended.