Developer journal · About the game

Outpost (1994): The future I wanted to build

The ninth-grade excitement, the frustration, and the idea that became Far Reach Industries.

In 1994, I was in ninth grade. I was a nerd. Not a geek. Not a dork. A nerd.

So when my dad bought Outpost for our PC, I was excited. Here was a game about establishing a colony in space, and my imagination ran wild with the possibilities. I could picture humanity starting over on another planet, building a settlement, and figuring out how to survive.

The part that made it even better was that you had to prepare for the mission before you could build the colony. You had to think about where you were going and what you would need when you got there. For a ninth-grade nerd, that was a wonderful invitation: imagine the future, then figure out how to make it work.

I had version 1.0. That matters, because the game I experienced was the original release, with its missing features and rough edges. I waited what felt like forever for the promised patch. I never played version 1.5.

What it got right

Outpost gave my imagination somewhere to go. Its greatest strength was the idea that building a colony meant more than placing futuristic buildings on a map. You were responsible for making a new home possible.

Preparing the expedition was a huge part of that appeal. The colony began with decisions made before arrival. Choosing equipment and investigating destinations made the mission feel like something I had a hand in planning. I wanted to think through those problems. That was part of the fun.

The survival systems also fit the premise. Mining, power, food, recycling, housing, and research were the kinds of things a colony would actually need to worry about. Even when the execution fell short, the concept had weight. These buildings were supposed to keep people alive.

Building underground added to that feeling. A hostile planet should affect how a settlement develops, and Outpost understood that. It offered a future where people had to adapt to their surroundings.

Looking back, I think that is why the game has stayed with me. It made the possibility of a colony in space feel close enough to explore on our family PC.

What it got wrong

The biggest problem was the gap between the game’s promise and version 1.0.

Features described in the documentation, including roads and monorails, were missing from the original release. In a game about constructing and managing a colony, those omissions mattered. The manual helped you imagine a more complete game than the one you could actually play.

That made waiting for the patch part of my experience with Outpost. I was excited about what the game could become, and I kept waiting for the promised update. But I never played version 1.5, so I cannot offer a personal judgment on how much it improved things. Roads and monorails were eventually added; they simply were not part of the game I knew. Archived patch descriptions I remember my colony failing almost every time, and I usually had no clue why. For a ninth grader with ADHD, that was beyond frustrating. I wanted to figure it out, but I couldn’t tell what I had done wrong or what I should change on the next attempt.

Looking back at the criticism of the original release, those memories make sense. The game asked players to manage complicated systems without explaining them clearly enough. Contemporary reviewers reported inadequate information, unclear causes of shortages, and technical problems that could interrupt long campaigns.

To me, that is where a game like this needs to be strongest. I was interested in learning how a colony worked. The game needed to give me enough information to understand the consequences of my decisions. Complexity could have been part of the attraction, provided I could see what was happening and learn from it.

Why I still remember it

My feelings about Outpost start with that ninth-grade excitement. My dad brought home a game, and suddenly I had a whole possible future to think about.

That excitement also explains the disappointment. The premise was strong enough to make me care about what was missing. I wanted the colony, the preparation, and the survival systems to come together into the game I could imagine.

For me, Outpost remains a compelling idea attached to an unfinished experience. I remember the possibilities it opened up, and I remember waiting for the patch.

Version 1.0 was the game I had. The fuller version was the one I kept hoping to play.

That frustration stayed with me, but so did the excitement. Years later, I still remembered the possibilities I saw when my dad brought Outpost home. Preparing an expedition. Choosing a world. Building a colony somewhere people had no business living, then figuring out how to make it work.

That is where the idea for Far Reach Industries came from.

I wanted to capture that same spirit and get right the things that had frustrated me. I wanted a game that felt playable in 2026, with the depth to reward careful planning and an interface that helped me understand what was happening.

If my colony was running out of food, I wanted to know why. Was there a power shortage? Had I expanded faster than my farms could support? Was a missing part holding up production? Give me enough information to follow the problem back to its source, understand my options, and do something about it.

I can accept losing a colony because I made a bad decision. I want to understand that decision well enough to make a better one next time. The ninth grader with ADHD who kept watching his colonies fail deserved that chance, and so does anyone playing my game.

Far Reach Industries would be something new. Outpost supplied the spark, but I wanted to follow it somewhere of my own.

One of the first things I wanted to change was the reason we were going.

I had no interest in another story where Earth had been destroyed or become uninhabitable. That has been done, and frankly, I find it boring. It puts the whole undertaking under the same enormous obligation: go into space because humanity has no choice.

What if settling other worlds was an industry?

What if Earth was still there, and people were financing expeditions because they expected a return? There were resources to extract, contracts to fulfill, markets to reach, and fortunes to make. The motivation could be something much more familiar: tried-and-true human greed.

That opened up a whole new level of possibilities.

Suddenly, preparing the mission meant deciding what I could afford, what I needed, and which promises I was willing to make to get funded. A leased seed factory could give my colony a head start while creating a deadline: I had to build the industry to replace its capabilities before its operating life ran out.

And the people funding the settlement might have very different priorities from the people living there. A sponsor could want exports while the colony needed spare parts. A profitable operation could still be a terrible place to live. Another settlement could become a trading partner, a competitor, or the only reason mine survived.

Those are the tensions I wanted to explore. People could cooperate because both sides benefited, take risks because the potential reward was enormous, or become dependent on an arrangement they later regretted.

I wanted the player to feel the excitement I felt in 1994, then have the tools to turn that excitement into a working colony. A place that could survive, grow, and eventually decide what kind of future it wanted—even if that future was different from the one its investors had paid for.