You Are the Computer

I used to read FGU Space Opera as a story game that had swallowed too many tables. Fourteen characteristics. Planet-of-birth modifiers. Skill budgets. Yearly command bids. Government Support Index. Corruption Index. It felt like the book could not stop adding columns.

That is the wrong complaint. The book is not failing to be elegant. It is succeeding at being a machine.

In 1980, a lot of the hobby was already thinking like software. People were typing Star Trek games in BASIC, generating Traveller subsectors from procedures, filling hexes with factors. Space Opera never pretended the computer had arrived. The CPU was you. The dice were the RNG. The tables were lookup functions. The character sheet was the output screen.

There is a beauty in a game that pretends to be a computer program. The two volumes read like source code for an infinite universe generator that also happens to print a person. You feed it a class, a birth world, a stretch of years. It returns gravity, Damage Factor, a skill budget, a command log, a planet with a repression index. Same pipeline, different scale. Character creation and sector creation are the same habit: inputs, modifiers, derived values, a file you can keep running.

You do not roll 2d6 and write Strength-7. You roll d100, spend a class pool of bonus percentage points, and look the result up on a conversion table biased toward player characters. The result is 1 to 19. Then the book computes: carrying capacity, Damage Factor, stamina, shock resistance, Characteristic Rolls on a d20. GTA, Mechanical Aptitude, and Electronics Aptitude sit on the sheet like separate processors. They are the numbers later procedures will ask for.

Planet of birth is more input, not color text. Gravity, atmosphere, and climate rewrite the registers. High-G adds Strength and takes Agility. The character is not “from a heavy world” in the story sense first. The character is a record that has already been run through an environment module.

Classic Traveller’s life path is a loop: survive the term, roll a skill, decide whether to risk another pass. Space Opera is a batch job. Characteristics are finished before anyone puts on a uniform. Initial service is one block of years. Skills arrive as a lump when the career is over. StarForce command is a yearly bid with rank gates and a prior-command log. Eligibility, then a function, then an output.

That output is not decoration. Skill and history are the access keys. An entertainer does not get a battlefleet. A veteran who already skippered a heavy cruiser does not walk into the room as one more voice. The log is why the next bid is legal, why the words carry, why someone hands you a larger hull and a larger problem. The program remembers what you have already run.

Worlds work the same way. Spectral type, zones, gravity, hydrographics — then a stack of indices that sound like settings and behave like variables: support, loyalty, repression, corruption, xeno-acceptance. A later procedure can call the repression index the same way it calls the gravity.

The layout is messy in the usual FGU way. Procedures live three chapters from the numbers they need. That is what happens when the program is printed in two volumes instead of compiled. The instinct underneath is still hardware. Fans put chargen and hulls into actual spreadsheets because the book was already asking to be one. Fill a Space Opera sheet, and you are stepping through a routine: find the input, apply the modifier, write the derived value, go to the next line.

The stark part is the point. Factors, target numbers, and success chances are visible. If you know the math before you fire the star torpedoes, you can put yourself in a winning position before the dice leave the hand. Range, sensors, the lock, the hull you brought. If you do not know your chances, you are not being dramatic. You are playing blind against a system that will happily compute the shot without you.

Traveller trains you to survive a sequence of rolls and see who walks out. Space Opera trains you to finish the procedure and read the file. The romance is still there — StarForce, mercenaries, thanokalamine in the medkit — but it sits on top of factors.

Stop asking whether each table is fun. Ask what it is computing. Once you treat the page as a program, the formulas stop being clutter. They are the game that was already running before anyone said the word computer out loud.