SELF-CONTAINED DEV BLOG: WHY A CONTAINER SHIP

A container ship is the most isolated place a normal person can legally stand on. That's the sentence I wrote in my notebook in like, the third week of preproduction on Self-Contained, and that sentence is basically the entire reason the game exists in its current form. Everything else is downstream of that one realisation.

I want to talk about how I got there, because I keep getting asked the same question over and over on the dev streams and on Twitter and in the Discord. Why a boat. Why not an oil rig. Why not a submarine. Why not a space station. Why not a remote arctic research base. Those are all great horror settings and I respect every game that has used them. But there's a specific reason a container ship works for what I'm trying to do, and the reason isn't just vibes. It's structural.

So here's the long version. The version that doesn't fit in a tweet.

The most isolated civilian place on Earth

When you start sketching out a horror game, one of the first questions you ask is "why doesn't the protagonist just leave." If your protagonist can leave at any time, you don't have a horror game, you have a haunted house attraction. The whole engine of dread runs on the player understanding, on a gut level, that there is no exit.

Horror writers solve this in a hundred ways. The cabin is snowed in. The phones are dead. The bridge is out. The killer cut the brake lines. It's a classic problem and there are classic answers. But these answers always have a slight artificiality to them. The writer had to engineer the trap. You can feel the hand of the author placing the obstacles. A storm is just a little too convenient. A flat tire is a little too on-the-nose.

A container ship doesn't need any of that. A container ship is, by its actual real-world function, a sealed environment. You are physically thousands of miles from the nearest landmass for weeks at a time. Your only contact with the rest of the human race is a satellite phone and an AIS transponder, and both of those can fail or be disabled in ways that are completely consistent with the normal operation of the vessel. The trap is the workplace. The trap was already there before the horror started.

That's the thing that hooked me. I didn't have to invent the prison. The prison is just a job that real people do every day.

What weeks at sea actually mean

Most people, when they imagine being on a ship, imagine a ferry crossing or a cruise. A few hours, maybe a few days, with land visible most of the time and a cabin steward bringing you towels. They do not imagine the actual reality of working merchant marine on a container vessel.

The average voyage on a transpacific route is something like fourteen to twenty days. The crew is small. Modern ships are crewed by maybe twenty people, sometimes fewer, for a vessel the length of four football fields. The bridge is staffed in shifts. Most of the ship is empty most of the time. There are entire decks you might not visit for the whole crossing if your job doesn't take you there.

The radio works, technically. You can call out. But who are you calling. The Coast Guard isn't going to scramble a helicopter for you in the middle of the Pacific Ocean. The nearest other vessel is probably hours away. If something happens at three in the morning during a Force 8 storm twelve hundred nautical miles from the nearest port, you are on your own in a way that almost no one in the modern world ever experiences.

That's the texture I want the game to have. Not "spooky abandoned ship." Not "ghost ship." A working ship, with a working crew, doing a job that is just genuinely this isolated as a baseline state. The horror builds on top of a normalcy that is already pretty unsettling once you actually think about it.

Design constraints are a feature

Here's the part that's going to sound like cope but I promise it isn't. I'm a solo dev. I don't have a team of forty people building me an open world. Every single asset, every single room, every single sound, has to be made by one person who also has to write the code and design the systems and do the marketing and answer the emails.

A container ship is a perfect setting for a solo project because it is, by design, repetitive and modular. The hull is divided into bays. The bays contain stacks of containers. The accommodation block is a stack of decks with corridors that all look broadly similar. The engine room is below. The bridge is on top. There's a rough taxonomy of about twelve to fifteen distinct location types, and once you've built those, you can recombine them into a believable ship.

That sounds like a limitation but it's actually liberating. When the world has a logic, the player learns the logic, and then the game gets to play with the logic. You know what a corridor looks like. You know what an engine room looks like. So when something is wrong with one of them, you notice immediately. Horror runs on the violation of expected patterns. A space that you understand can be made strange in a way that a space you don't understand cannot.

I keep coming back to a quote from one of the Iron Lung dev posts where he talks about the limitations of the submarine being the actual creative engine. You can't see anything. The walls are inches from your face. There is no map, no ally, no backup. And those constraints didn't shrink the game, they sharpened it. A small space with rules is more interesting than a big space without them.

The water below

Okay. The actual horror. Let's talk about the water.

I wrote about thalassophobia in an earlier piece on ocean horror games, and I'm not going to repeat the whole thing here, but the short version is that the human brain has a very old, very wordless reaction to deep dark water. We did not evolve to be in it. We can't see in it. We can't breathe in it. We are not at the top of the food chain in it. Every part of our body is screaming at us, on an instinctive level, that the water is not for us.

A container ship sits on top of, conservatively, several kilometres of cold black water. The hull is thick. You don't see the water most of the time. You feel it. You hear it. The ship moves under you in a way that is constant and never quite the same twice. At night, when you go out on deck, the water is just an absence. You can hear it but you cannot see where it ends, because there is no light source down there and the horizon is not visible.

I wanted that feeling in the game. The water is not a level. The water is a presence. You almost never go in it. You don't really need to. The threat of it, the proximity of it, the awareness that it is right there underneath everything, does most of the work. The game is about what happens on the ship. But the ship is on the water. And the water is the thing.

The references that got me here

I would be lying if I said I came up with this in a vacuum. The reason I trust the container ship setting is that I've seen pieces of this idea work in other games and I've spent a lot of time figuring out why.

Still Wakes the Deep is the obvious one. An oil rig is not a container ship, but it's the same family of setting. Industrial workplace. Surrounded by water. Small crew. Real jobs. The supernatural element grows out of a workplace that already feels miserable and stressful in a credible way. Watching that game, I kept thinking about how the horror lands harder because the rig feels like a place. It's not a haunted asset pack. The lockers have stickers on them. The break room has someone's mug. The bunk has a paperback novel face down on it. The horror wouldn't work without the boring believable details.

Dredge is doing something different but related. It's not a horror game in the same sense, but it understands water. The way the fog rolls in. The way the shapes in the water at night refuse to resolve into anything you can name. The way the player learns to dread the dark hours. Dredge taught me that the ocean itself can carry an enormous amount of dread without you ever showing the player a monster. The expectation of a monster is doing more work than the monster ever could.

And Iron Lung. I'll never stop talking about Iron Lung. A rusted tin can in a sea of blood on a moon nobody has ever surveyed. You see almost nothing. You navigate by a grid and a low resolution camera. The whole game is constraint as art. It's the purest expression of an idea I've ever played. Self-Contained is not Iron Lung. Self-Contained has way more space and way more systems. But the philosophy of "make the smallest thing that scares the most" comes directly from that game.

There are others. Rebirth chapter of REC. The first half of Alien Isolation, before it shows its hand. The Outer Wilds DLC, which is not a container ship but understands what isolation in a small dark place feels like. I've also been reading a lot about real-world maritime disasters and incidents, the El Faro report in particular, because there's a quality to those documents that fiction can't really fake. Real ships go missing in real ways and the documentation of those events is some of the most chilling reading I've ever done.

What this all means for the actual game

I'm not going to spoil anything because the game isn't out yet and frankly the marketing team, which is also me, would like to keep some powder dry. But I can tell you in the abstract.

You're on the ship. You have a job. The job is mundane. The crew is small and you don't know all of them well because you joined this voyage two days before departure. Something happens, fairly early, that you can't explain. The radio is not as helpful as it should be. The captain is not as helpful as he should be. You start noticing things. The game expands from there.

The container ship is not a backdrop. The container ship is the antagonist's habitat. The setting is what gives the antagonist its power, because the setting was already isolating, already disorienting, already designed to keep you in one place for weeks at a time. The horror is just exploiting features of the environment that were always there.

That's the design pitch in one paragraph. A real workplace, slightly weaponised, with no exit by design rather than by contrivance.

Why I'm glad I committed to this

I've been working on Self-Contained for a while now. I've changed a lot of things during development. The combat system. The save system. The HUD. The story structure. The protagonist's backstory got rewritten three times. But the setting has never wavered, not once, not even when I was deep in a refactor and questioning everything else.

That's how I know it was the right call. The setting is the thing the rest of the game keeps coming back to. Every time I get stuck on a design problem, I ask myself "what would actually be true on a container ship," and most of the time the answer is right there. The constraints of the setting are not fighting me. They're feeding me.

If you want to dig deeper into why isolation is such fertile ground for horror, I wrote a more general piece on why isolation horror works that goes into the psychology side of it. And if you want to see how this stuff connects to horror design more broadly, what makes horror games scary covers some of the underlying mechanics. I'm not going to keep linking my own posts at you, that's the last of it.

The next dev blog is probably going to be about the lighting setup, because I've been losing my mind over a single dynamic light in the engine room for about a month and I think I've finally figured it out. Until then, thanks for reading. I'll be back in the Discord later answering whatever new variant of "why a boat" you can come up with.

It's because boats are scary. That's the answer. That's always been the answer.