When the Adventure Fails: Responsibility to the People at the Table

Sometimes you know.

You don't need to wait until the end of the session, ask everyone how they enjoyed themselves, read the comments afterward, or conduct some elaborate postmortem. You can feel it while the game is happening. Something that normally exists between the Game Master and the players—the exchange of energy that makes a roleplaying game come alive—simply isn't there.

You describe the scene.

Silence.

You present another clue.

Silence.

You look around the virtual table, hoping someone will seize upon something, ask the question that brings everything into focus, or make the decision that finally sets the story moving.

More silence.

For a Game Master, there may be few sounds quite as loud as players who have nothing they want to say.

I recently ran an episode of Star Trek Adventures that failed that badly.

I don't mean that it was merely below my usual standard, or that there were a couple of scenes I would handle differently if I ran them again. I mean that, by my own judgment, it was one of the worst roleplaying sessions I have ever presented. A few players who have gamed with me for years essentially agreed. They knew what my games normally felt like, and they knew this one wasn't working.

That hurt.

It should have.

Not because every creative failure ought to become an exercise in self-punishment, and certainly not because a Game Master should expect perfection from himself every time people gather around a table. It hurt because I care about the experience I give the people who have chosen to spend those hours with me.

That distinction matters.

There is a difference between bruised pride and responsibility.

The first says, I can't believe I failed.

The second asks, Why did this fail, and what am I going to learn from it?

I have been thinking a great deal about that question.

The episode was conceived as a mystery, and from the design side I thought I was attempting something ambitious. I wanted an intellectual challenge in which apparently unrelated clues gradually formed a coherent picture. There was a Federation field science installation, personnel transfers between the installation and the USS Azimuth, a supporting character, a cadet, scientists, and a mystery that I expected the players to slowly unravel. Our regular science officer was absent, which meant another player—normally playing the ship's executive officer—was operating a supporting character instead. That alone changed the chemistry of the group more than I anticipated.

Then there were the NPCs.

Too many of them.

In my notes they all made sense. Each existed for a reason. I knew who was arriving, who was departing, who belonged to the field team, who knew what, and how each person related to the underlying mystery. From behind the Game Master's screen, the structure seemed perfectly understandable because I possessed the one thing the players did not possess.

The answer.

That is one of the great traps in mystery design. Once you know the solution, it becomes remarkably difficult to remember what the mystery looks like to someone who doesn't.

A clue that seems obvious to the writer may be almost meaningless to the player. Three pieces of information that form an elegant pattern in my head may appear to the players as three completely unrelated facts. If the connection between those facts depends upon an assumption that exists only in my notes, I have not constructed a difficult mystery.

I have constructed an incomprehensible one.

There is a profound difference.

I had mistaken complexity for challenge.

Worse, I had overwritten the scenario. There was too much information competing for attention, too many characters requiring identification, too many relationships that mattered to me because I had designed them, and not enough clarity about what mattered to the players standing inside the situation.

I had built an elaborate machine and forgotten that the players could not see the gears.

Yet even that does not completely explain why the session failed, because there was another problem that may have been more important than all the others.

It wasn't the kind of Star Trek my players wanted that night.

I wanted to give them a cerebral mystery.

They wanted adventure.

They wanted the Original Series.

They wanted the sense that somewhere beyond the next planet there might be danger, discovery, a beautiful alien diplomat, a Klingon plot, a fistfight, a moral dilemma, a phaser drawn at exactly the wrong moment, or some impossible decision that Captain Kirk would have contemplated for approximately thirty seconds before ordering the Enterprise into danger.

They wanted swashbuckling Star Trek.

I gave them homework.

That may be an exaggeration, but not by very much.

And the painful thing is that all the production value in the world could not rescue it.

I had graphics.

I had Desilu-style backdrops designed to evoke the visual language of the Original Series.

I had audio through Syrinscape.

I had prepared scenes, characters, clues, and atmosphere. All the machinery I normally use to help turn a virtual tabletop into something resembling an episode of television was there.

None of it mattered.

The session fell flat.

The best comparison I can make is a stand-up comic who walks onto a stage convinced that the new material is brilliant, delivers the punchline, and hears nothing.

Not outrage.

Not heckling.

Nothing.

Crickets.

There is nowhere to hide in that moment.

You can have beautiful lighting. You can have the best microphone in the theater. You can have a perfectly designed stage and an expensive sound system. If nobody laughs, none of it matters.

Roleplaying games possess the same ruthless honesty.

The players either engage or they don't.

That doesn't mean every quiet player is bored, every failed clue is bad design, or every difficult session is the Game Master's fault. Groups have off nights. People are tired. Important players are absent. Real life intrudes. Chemistry changes depending upon who attends. Sometimes a perfectly good adventure encounters exactly the wrong combination of circumstances and simply refuses to ignite.

That happened here too.

Our missing science officer mattered. Another player was therefore occupying a different role from the one in which he normally helps shape the command dynamic aboard the Azimuth. The scenario itself depended heavily upon scientific investigation, making that absence particularly unfortunate. Fewer players meant fewer minds attacking the mystery from different directions, and the people who were present were being asked to engage with unfamiliar supporting characters and an unusually complicated cast.

Those things contributed to the failure.

But I don't want to hide behind them.

The scenario was also bad.

At least in the form in which I presented it, on that particular day, to that particular group, it was bad.

Being willing to say that matters.

I think one of the easiest traps for any experienced creator is to become defensive about failure. Experience can become armor. If you have run hundreds of successful sessions, received good reviews, entertained people for years, and developed confidence in your craft, there is a temptation to explain away the disaster.

The players weren't paying attention.

The wrong people were absent.

They didn't understand what I was trying to do.

They should have followed the clues.

Perhaps some of those statements might even contain a little truth.

They are also mostly useless.

The audience does not owe the performer the reaction the performer intended.

That lesson extends far beyond roleplaying games.

A reader does not owe an author excitement because the author spent three months designing the world.

A player does not owe a Game Master fascination because the Game Master spent six hours preparing the mystery.

Effort deserves respect, but effort does not guarantee effect.

That is a difficult truth for anyone who creates things.

We experience our work from the inside. We remember the hours that went into it. We remember the research, the discarded ideas, the maps, the rewrites, the moments when some complicated piece finally clicked into place. The audience experiences none of that. They encounter what we actually put in front of them.

That is all they can judge.

And that is fair.

It has made me think about something larger than one unsuccessful episode of Star Trek Adventures. What responsibility do I have to the people who choose to spend their time in worlds I create?

I think the answer is: quite a lot.

Time is one of the few genuinely irreplaceable things people give us.

My players could spend those hours doing almost anything. They could watch a movie, play a computer game, read a novel, spend time with their families, go out for dinner, or simply sleep. Instead, they choose to show up at my virtual table and say, in effect, All right. Take us somewhere.

That is an extraordinary act of trust when you think about it.

My Traveller players give me that trust when they board their ship and head into my own setting.

My Conan players give it to me when they enter some dangerous alley, forgotten ruin, or blood-soaked wilderness of the Hyborian Age.

My Dune players give it to me when they step into a universe of political intrigue, duty, betrayal, ecology, religion, and power.

My Star Trek Adventures players give it to me every time the USS Azimuth goes to warp.

Different games require different rhythms. Traveller can linger over trade, exploration, survival, and the consequences of decisions made parsecs ago. Conan should sometimes move with the savage momentum of a sword stroke. Dune can thrive on conversations in which every polite sentence conceals three threats. Star Trek should carry that wonderful combination of optimism, intelligence, danger, humanity, and adventure that made me fall in love with it in the first place.

My responsibility is not to make those games identical.

My responsibility is to understand why the people at each table came.

The same is true of readers.

Someone who opens one of my TransStellar stories is making the same fundamental bargain as someone joining one of my games. They are giving me their attention and asking me to make that investment worthwhile. The reader following Kars Vandor does not care how many spreadsheets I maintain or how carefully I have calculated the chronology of Known Space unless those things ultimately make the story richer. Someone reading one of my cyberpunk stories is not obligated to admire the setting if the characters never come alive. Someone entering one of my zombie apocalypse stories does not care how meticulously I worked out the collapse if there is nobody inside that collapse worth caring about. A fantasy world can contain ten thousand years of history and still be lifeless if the story happening today is dull.

Worldbuilding supports storytelling.

It cannot replace it.

Production values support Game Mastering.

They cannot replace it either.

That failed Star Trek session reminded me of this more effectively than a dozen successful sessions probably could have.

Success is pleasant, but it can be a poor teacher because success encourages us to assume that whatever we did must have been correct. Failure is less polite. Failure walks into the room, sits down directly across from you, and asks uncomfortable questions.

Were there too many NPCs?

Yes.

Were the clues sufficiently clear?

No.

Did I mistake confusion for intellectual difficulty?

Probably.

Did the absence of an important player damage the structure of the scenario?

Yes.

Did I recognize quickly enough what kind of adventure the players wanted?

No.

Did I keep trying to make the prepared material work after the energy at the table told me it wasn't working?

Probably longer than I should have.

Those are useful answers.

None requires me to conclude that I am a terrible Game Master.

That conclusion would be just as self-indulgent as refusing to acknowledge the failure at all.

One bad performance does not erase years of good ones.

But years of good performances do not make the bad one good.

Both things can be true simultaneously.

I think experienced creators sometimes need to remind themselves of that. Confidence should allow us to survive failure, not become immune to criticism. If I know I can run a good game, then I should be secure enough to admit when I ran a bad one. If I know I can write a good story, then I should be capable of looking at a weak manuscript and saying, This isn't there yet.

There is freedom in that.

The disaster becomes an event rather than an identity.

I ran a bad game.

That is very different from:

I am a bad Game Master.

The first statement contains useful information.

The second contains nowhere to go.

So I have chosen the first.

I ran a bad game.

Now I intend to run a better one.

That does not mean retreating into safety and never attempting another mystery. Quite the opposite. If failure teaches us only to stop experimenting, then we have learned the wrong lesson. I want to try difficult scenarios. I want to challenge players intellectually. I want to experiment with structures I have never used before. Some of those experiments will fail.

They are allowed to.

What they are not allowed to become is an excuse for carelessness.

There is an important distinction between accepting mistakes and accepting mediocrity.

Everyone gets a bad night.

Nobody should make bad nights the plan.

If a session fails because I attempted something ambitious and misjudged it, I can forgive myself. If the next session fails for exactly the same reasons because I couldn't be bothered to learn from the first one, that is different.

The first failure is tuition.

The second is refusing to attend class.

That principle applies to writing as much as gaming. A novel may fail. A character may not work. A chapter may need to be thrown away after weeks of effort. An experimental structure may prove unreadable. There is no shame in any of that. Creative work involves risk, and risk implies the possibility of failure.

The responsibility comes afterward.

Learn.

Rewrite.

Simplify.

Listen.

Try again.

Do better.

Not perfectly.

Better.

There is a phrase I have been thinking about lately: the audience deserves my best effort, but they do not require my perfection.

I like that distinction.

Perfection is impossible and chasing it can become another form of paralysis. Best effort is something different. Best effort means respecting preparation. It means paying attention during the performance rather than becoming enslaved to the notes. It means noticing when the players are deadly quiet and understanding that their silence is information. It means being willing to abandon something I spent hours preparing if the table has clearly found a more interesting direction.

It also means remembering that a roleplaying game does not belong entirely to the Game Master.

That may be the most important lesson of all.

I can write the scenario.

I can design the mystery.

I can create the NPCs, select the music, build the graphics, prepare the maps, establish the stakes, and understand everything that happened before the opening scene.

Then the players arrive.

At that moment it becomes ours.

Their curiosity matters.

Their expectations matter.

Their characters matter.

Their enjoyment matters.

The same strange transformation occurs when a book is published. Until publication, the manuscript belongs almost entirely to the writer. Afterward, readers bring themselves to it. They interpret characters in ways the author never expected. They care deeply about things the author thought were minor. They sometimes overlook things the author considered profound.

That is part of the bargain.

Creation begins privately.

Meaning becomes collaborative.

I find that humbling.

I also find it motivating.

Because I want the next episode of the USS Azimuth to be better.

I want the next Traveller session to leave my players arguing excitedly about what they should do next.

I want Conan to feel dangerous.

I want Dune to feel like every decision carries consequences.

I want readers entering Known Space to discover characters worth following across light-years. I want the TransStellar stories to reward the hours people invest in them. I want Kars Vandor and all the other people inhabiting my fiction to feel as alive to readers as they do to me. I want my cyberpunk cities to pulse with life, my post-apocalyptic worlds to hurt, and my fantasy landscapes to contain genuine wonder.

I will not accomplish that every time.

Nobody does.

There will be bad sessions.

There will be weak chapters.

There will be ideas that looked magnificent at midnight and ridiculous the following afternoon.

There will probably even be another night when I sit behind the virtual Game Master's screen, present something I was certain would work, and hear those terrible metaphorical crickets again.

When it happens, I hope I have enough confidence not to collapse under it and enough humility not to dismiss it.

I will listen.

I will figure out what happened.

I will learn whatever the failure has to teach me.

Then I will go back to work.

Because the people who come to my table deserve that.

The people who open my books deserve that.

And perhaps, in the end, I owe it to myself as well.

Not perfection.

Not an impossible promise that every game will be unforgettable and every book extraordinary.

Something much simpler.

Care about the work.

Care about the people receiving it.

Take risks.

Accept mistakes.

Never become comfortable making the same mistakes again.

And next time, do better.

 

Getting Out of My Own Way: Rediscovering Why I Write

There are times when the greatest obstacle standing between us and the things we want to accomplish is not money, opportunity, technology, age, or even time. Sometimes the obstacle is considerably closer to home. Sometimes it is the voice inside our own heads that insists we aren't ready yet, that the project isn't good enough, that there is too much left to do, or that perhaps the enormous thing we have imagined for ourselves is simply too enormous to accomplish.

I know that voice rather well.

One of the things I have been thinking about lately is self-confidence, although perhaps persistence is the better word. Confidence suggests certainty, and I am not certain that creative people ever really possess that for very long. We can feel absolutely convinced about a story on Monday and wonder whether we have any business calling ourselves writers by Thursday. Creation has always contained that contradiction. You must possess enough confidence to believe that something inside your imagination deserves to exist outside of it, while retaining enough humility to recognize that getting it there requires work.

The trick is learning not to become your own worst enemy somewhere between those two things.

I was reminded of that recently by something utterly mundane: moving files.

The old Novel Factory site is finally being shut down, and although I had already migrated my work to Novel Factory 3, I found myself faced with that peculiar anxiety every writer who has worked digitally understands. Were all the manuscripts really there? Had everything transferred correctly? Was there some forgotten project sitting in an old account that I would remember only after the server disappeared forever?

There are few phrases more terrifying to a writer than permanently deleted.

So I started checking.

Then I started transferring.

And I kept transferring.

By the time I finally stopped, it was about 1:30 in the morning. I had spent hours making certain that manuscripts, projects, notes, fragments, characters, and stories accumulated over years of work were safely moved into their new home.

It should have been administrative work, the literary equivalent of cleaning out an old filing cabinet.

Instead, something unexpected happened.

I rediscovered myself.

As I opened those projects one after another, I began encountering characters I had not thought about for some time. There were stories that had once consumed my imagination and then quietly moved into the background while some other project demanded attention. There were unfinished manuscripts, half-developed worlds, scenes that still made me smile, and ideas that immediately reminded me why I had been excited enough to begin writing them in the first place.

It was rather like walking through an enormous house I had been building for years and discovering rooms I had forgotten were there.

Behind one door was space opera.

Behind another was fantasy.

Farther down the corridor were the survivors of a zombie apocalypse, still waiting for me to discover what happened to them.

Somewhere else neon reflected from rain-soaked streets while cyberpunk characters continued living dangerous lives in a future I had temporarily left behind.

Everywhere I looked there were people.

That may have been the thing that struck me most strongly. I tend to talk about worldbuilding in terms of maps, civilizations, histories, star systems, political boundaries, technologies, and timelines because those are the enormous structures that fascinate me. Yet when I went through those manuscripts again, what I rediscovered were not structures.

I rediscovered characters.

People with ambitions and failures, loves and grudges, victories and terrible mistakes. People who had once been little more than an idea and who, somewhere during the process of writing them, had acquired voices of their own.

They were still there.

They had simply been waiting.

That realization produced a feeling I hadn't expected from an evening spent performing digital housekeeping. Instead of finishing the night exhausted and irritated that I had spent so many hours transferring files, I found myself excited.

Look at all of this.

Look at everything still waiting to be written.

There is a danger in thinking that way, of course, because the sheer volume of unfinished creative work can become intimidating. Every writer with more ideas than time eventually confronts that problem. A dozen exciting projects can inspire you, but fifty can paralyze you. The imagination sees the finished library while the calendar sees Tuesday afternoon.

That is where being your own worst enemy becomes remarkably easy.

You begin measuring yourself against the finished version of everything you hope someday to create.

Of course you lose that comparison.

The finished novels exist perfectly inside your imagination. The actual manuscripts contain awkward paragraphs, continuity problems, unfinished chapters, scenes requiring revision, characters who need additional development, and all the other evidence that writing is something constructed rather than summoned fully formed from the ether.

The imagined career is equally perfect. Every book is finished. Every map is beautiful. Every series is complete. Readers have discovered the stories. The worlds are known.

Reality consists of opening the manuscript and writing the next page.

For a long time I think I sometimes allowed the enormous scale of my ambition to work against me. When you want to create something large, it becomes terribly easy to concentrate on how much remains unfinished rather than how much has already been accomplished. The horizon continually retreats as you approach it. Finish one world and ten neighboring worlds suddenly become interesting. Establish one historical date and it creates questions about the century surrounding it. Finish one story and the characters begin suggesting another.

There will always be more.

Perhaps the answer is not to resent that fact.

Perhaps that is the gift.

I don't actually want to reach a morning when I sit down at my desk and discover that there are no more stories I want to tell. I don't want every world completely mapped, every character's life resolved, every civilization fully documented, and every mystery explained. What an extraordinarily empty achievement that would be.

I want to wake up knowing there is something else waiting.

The work I did that night reminded me how fortunate I am to have accumulated so many things that still excite me.

I am a space opera writer, certainly, and that remains at the center of so much of what I want to accomplish. There is something about the enormous scale of space opera that continues to speak to me: civilizations separated by light-years, ships crossing the darkness, ancient histories, political struggles, exploration, war, discovery, and ordinary human beings trying to understand their place inside something unimaginably large.

But that isn't the only place my imagination lives.

I love fantasy because sometimes I want history to become myth, and sometimes I want the darkness beyond the forest to contain something that astronomy cannot explain. I love zombie apocalypse stories because stripping civilization away creates an extraordinarily brutal question about who people become when all the structures they trusted disappear. I love cyberpunk because beneath all its neon, technology, corporations, artificial intelligence, and urban decay lies a deeply human argument about identity, freedom, power, and what remains of us when technology can alter almost everything else.

Different genres allow me to ask different questions.

Yet the strange thing I rediscovered while moving all those manuscripts is how unmistakably they remain my questions.

The scenery changes. The characters change. A starship becomes a sword, a frontier colony becomes a ruined city, an interstellar corporation becomes a cyberpunk megacorporation, but certain things remain. People confront systems larger than themselves. They inherit histories they did not create. They struggle with duty and freedom, loyalty and ambition, civilization and chaos. They try to leave something behind.

Perhaps writers spend their entire lives asking a handful of questions in increasingly elaborate ways.

If so, I have plenty of questions left.

What I need now is the confidence to answer them.

Not the confidence that says everything I write will be brilliant. That kind of confidence is useless, and probably dangerous. I want the quieter kind: the confidence that allows me to keep working when a chapter is difficult, to finish rather than endlessly prepare, to revise rather than despair, and to accept that an imperfect completed manuscript can become an excellent book while the perfect unwritten novel can become nothing at all.

That last lesson may be one of the hardest for an ambitious creator to accept.

There is always another improvement available.

There is always more research.

There is always another map that could be refined, another timeline that could be reconciled, another character biography that could be expanded, another scientific detail that could be checked. I enjoy all of those things, and they genuinely strengthen my work, but they can also become wonderfully sophisticated ways of avoiding the frightening moment when the book must simply be finished and allowed to leave my hands.

At some point, preparation has to become publication.

At some point, dreaming has to become doing.

That does not mean abandoning the dream's scale. Quite the opposite. I have spent enough years imagining what I want to create that I see no reason to make the ambition smaller now. If anything, rediscovering those manuscripts reminded me that the dream is larger than I had recently allowed myself to remember.

There are a lot of books in there.

There are a lot of characters waiting for their turn.

There are stories I had almost forgotten that immediately made me want to start writing again.

So perhaps the path forward is not some dramatic transformation. Perhaps it is simply refusing to sabotage myself.

Open the manuscript.

Write the chapter.

Finish the book.

Then finish another.

Organize the worlds, preserve the notes, maintain the chronology, build the maps, but remember what all of those things exist to support.

Stories.

I have written recently about wanting to push myself toward greatness, and I remain aware of how uncomfortable that word can sound. Greatness is something other people usually confer after the fact, and declaring oneself great is a fairly reliable way of demonstrating the opposite. Yet I see nothing wrong with pursuing it. There is a tremendous difference between claiming greatness and attempting great work.

I cannot control the first.

I can devote myself to the second.

That may be the most useful form of self-confidence I can cultivate now. I do not need to know that I will succeed. I need to believe that the attempt is worthwhile. I need enough faith in the stories I rediscovered at 1:30 in the morning to give them the opportunity to become finished books.

And I need to remember that the person most capable of preventing me from doing that is probably me.

So I am trying to get out of his way.

There is an entire library sitting in front of me—not a hypothetical library anymore, but manuscripts, characters, settings, scenes, histories, and ideas that already exist in various stages of completion. Moving them from one piece of software to another reminded me that I have not spent all these years merely dreaming about becoming a writer.

I have been writing.

Now the task is to keep going.

Space opera. Fantasy. Cyberpunk. Zombie apocalypse. Strange worlds, ruined worlds, magical worlds, future worlds. Characters I know intimately and characters I have only begun to meet.

They are all waiting.

Maybe someday other people will decide whether any of it deserves to be called great. That judgment isn't mine to make, and perhaps it never was.

Mine is the simpler responsibility.

Do the work.

Finish the stories.

Believe enough in what I have already created to stop standing in its way.

And keep going.

At Warp Speed: Learning to Run Star Trek Adventures

 

There are roleplaying games in which the Game Master can prepare a dungeon, populate its rooms, establish the opposition, anticipate several likely routes through the adventure, and arrive at the table reasonably confident that somewhere within those preparations lies most of what the players are going to encounter. There are other games in which preparation remains important, but the players possess enough freedom that the person running the game must be prepared to improvise when they inevitably wander beyond whatever boundaries were imagined beforehand.

Then there is Star Trek Adventures.

After spending considerable time running it, I have come to believe that one of the most interesting things about the game is also one of the things that made it surprisingly difficult for me to learn: when it is working properly, Star Trek Adventures moves. It can move astonishingly quickly, not necessarily in terms of combat rounds or dice rolls, but in terms of ideas. A conversation on the bridge becomes a sensor investigation, which becomes a scientific mystery, which becomes first contact, which becomes a diplomatic problem, which suddenly becomes an engineering emergency because one of the players has just suggested doing something that never occurred to me when I prepared the adventure.

And now everyone at the table is looking at me.

What happens next?

That, I have discovered, is where Star Trek Adventures really lives.

I did not learn that immediately. In fact, it probably took me a good six months before I felt that I genuinely understood how to run the game, and that was after spending roughly three months on the other side of the screen as a player in another GM's campaign. Those months playing were important because they allowed me to experience the rhythm of the system without simultaneously worrying about every NPC, every rule, every complication, and every narrative possibility. I could watch what another Game Master did, see how scenes flowed into one another, and begin to understand how the machinery underneath the game supported the fiction.

Even with that experience, however, running it was another matter entirely.

I have been running roleplaying games for a very long time, and one lesson that experience repeatedly teaches is that familiarity with one game does not automatically translate into mastery of another. There are certainly universal skills involved in being a Game Master—pacing, description, characterization, improvisation, understanding one's players—but every good roleplaying system has its own rhythm. If you try to force it into the rhythm of another game simply because that is what you already know, you can technically run it while completely missing what makes it special.

With Star Trek Adventures, I eventually realized that I had to stop thinking so much about adventures as sequences of events and start thinking about them as situations possessing momentum.

That distinction changed everything.

I can prepare the mystery. I can know what happened before the Enterprise—or, in my own campaign, the USS Azimuth—arrived. I can know what the alien civilization wants, what the Romulans are attempting to conceal, why a Federation ship disappeared, or what terrible mistake an archaeological expedition made before the opening scene. I can understand the motivations of the important NPCs and establish what will happen if Starfleet does absolutely nothing.

What I cannot reliably know is how the crew will respond.

Nor should I.

That is Star Trek.

The Captain Says, "Open a Channel"

Consider something as simple as encountering an unknown vessel.

In another science-fiction game, I might reasonably expect the players to begin discussing weapons, armor, relative velocity, firing solutions, and tactical positioning. Those things certainly exist in Star Trek Adventures, and combat can become very important, but Starfleet officers possess an enormous range of alternatives before anyone fires a phaser.

The captain might open a channel.

The science officer might perform a detailed sensor sweep.

The communications officer might notice something peculiar hidden inside the transmission.

The engineer might determine that the other vessel's apparently hostile behavior is actually the result of a failing propulsion system.

The medical officer might realize that something detected aboard the ship suggests an epidemic.

The tactical officer might recognize that the vessel's movements are inconsistent with an attack.

Then one player asks a question that changes everything:

"Can we modify the sensors to separate the two signals?"

That question may not exist anywhere in my notes.

It exists now.

The entire adventure can pivot around it.

As Game Master, I have perhaps thirty seconds to decide whether the idea is plausible, what combination of Attribute and Discipline seems appropriate, how difficult the Task should be, what information success reveals, what Complications might mean, and—most importantly—whether this wonderful idea has just exposed a possibility in the story that I hadn't considered myself.

Sometimes the answer is yes.

Those are often the best moments of the game.

Starfleet Officers Are Extremely Capable People

One reason Star Trek Adventures demands so much flexibility from the GM is that the player characters are not wandering adventurers waiting for someone to hand them a quest.

They are Starfleet officers.

They have a starship.

They have laboratories.

They have sensors.

They have transporters.

They have a sickbay staffed by highly trained professionals. They have engineers capable of solving extraordinary technical problems. They have computers containing enormous quantities of information. They can consult specialists elsewhere aboard the ship, call senior officers into a briefing, launch shuttlecraft, modify equipment, analyze strange particles, perform orbital surveys, and contact other civilizations.

And, perhaps most dangerously for a Game Master's carefully prepared plot, they can talk to one another.

A table full of intelligent players discussing a mystery from the perspectives of command, science, engineering, medicine, security, navigation, and diplomacy is an extraordinarily effective problem-solving machine.

They will think of things I didn't.

I've learned to hope that they do.

My job is not to defend my solution from them.

My job is to determine what happens when their solution meets the universe.

That realization was probably one of the major milestones in learning to run the system.

The Rules Eventually Become Invisible

During my first months with the game, I was understandably conscious of the mechanics. Which Attribute applies? Which Discipline? What is the Difficulty? How does Momentum work here? Should this create Threat? Is this an Extended Task? What Trait is currently affecting the situation?

Those questions matter, particularly while learning the system, but concentrating too heavily on them can make a Star Trek story feel strangely mechanical.

Eventually something clicked.

I stopped beginning with the rules.

I began with the fiction.

What is happening?

What is the officer trying to accomplish?

What makes it difficult?

What would success actually mean?

Only then do I reach for the mechanics necessary to resolve the uncertainty.

The 2d20 system works remarkably well when approached this way because so much of it can be interpreted through the circumstances of the story. Traits, Advantages, Complications, Momentum and Threat provide a vocabulary for turning fictional developments into mechanical consequences without requiring the fiction to stop while everyone consults a completely separate tactical reality.

Once I became comfortable enough with that vocabulary, the game became much faster.

More importantly, it became much more like Star Trek.

I Prepare Problems, Not Answers

This has changed the way I prepare episodes.

I still prepare extensively. I enjoy preparation far too much ever to become one of those Game Masters who arrives with three sentences scribbled on an index card and trusts entirely to improvisation. I want to know the history behind the episode. I want to understand the location, the antagonists, the mystery, the scientific problem, and the people involved.

But I increasingly resist preparing the solution.

If an ancient installation is producing a dangerous phenomenon, I need to understand what the installation is doing and why. I do not necessarily need to decide that the players must reach Engineering Room B, recover the control crystal, decipher three inscriptions, and shut down the reactor.

Perhaps they will.

Perhaps the chief engineer will propose reversing something through the deflector dish, in the finest Star Trek tradition.

Perhaps the science officer will realize the phenomenon can be neutralized rather than stopped.

Perhaps the captain will discover that the apparently abandoned installation is not abandoned at all and decide that shutting it down would constitute an act of aggression.

Perhaps someone will ask a question that transforms my understanding of the situation.

When that happens, the prepared background doesn't become useless. Quite the opposite. Because I know why the situation exists, I can extrapolate what happens when the players interfere with it in ways I never anticipated.

Preparation gives improvisation something solid to stand upon.

That may sound contradictory, but I think it is one of the central skills of Game Mastering. The more deeply I understand a situation, the less I need to predict what the players will do.

Keeping Up with the Crew

There are sessions when running Star Trek Adventures feels almost like trying to keep pace with the bridge crew while they are operating at full speed.

"Sensor sweep."

"What do we detect?"

"Can I analyze that?"

"Does the computer have any record of this phenomenon?"

"Can Engineering compensate?"

"I want to hail them."

"Can we beam through the interference?"

"What happens if we reverse polarity?"

"Captain, I think they're trying to communicate."

And all of this can happen in minutes.

The GM is moving between physics, characterization, Starfleet procedure, game mechanics, established Star Trek lore, the prepared episode, and whatever completely unexpected direction the players have just discovered.

I find it exhilarating.

It is also exhausting.

When the game is really working, though, there comes a moment when I stop feeling like the person presenting an adventure and start feeling as though I am watching an episode of Star Trek emerge spontaneously around the table.

Nobody wrote this episode.

Not completely.

I established the situation. The players brought their characters. The rules provided uncertainty. Then all of us discovered the story together.

Writing the Star Trek Stories I Dreamed About

There is another reason running this particular game means something to me.

I loved Star Trek long before I understood how stories were constructed. As a kid, I could watch those ships disappear into the stars and imagine that somewhere beyond the television screen there must be thousands of other stories that simply hadn't been filmed yet. I wanted to tell some of them, although at that age I didn't really understand how someone went about doing such a thing.

Much later in life I even reached out toward that professional world, including a very brief conversation with Rick Berman during the era of Enterprise. Nothing came of it, but the desire to tell Star Trek stories never really disappeared.

Now I get to do it every time we play.

There is no television production budget. I don't have to worry about whether the alien planet set is available this week or whether the episode can afford another visual-effects sequence. If I want a shattered planet surrounded by the remains of an ancient civilization, it exists. If the Azimuth needs to encounter something no Federation scientist has ever seen, then somewhere beyond the next star it is waiting.

The only real budget is imagination.

And my players have an unlimited line of credit.

Six Months to Understand Something Simple

After roughly three months playing the game and another six months learning to run it, I eventually arrived at a principle that sounds embarrassingly simple:

Don't try to control Star Trek.

Set it in motion.

Understand the situation well enough that it can react honestly to whatever the players attempt. Know the people involved. Know what they want. Know the scientific mystery well enough that reasonable questions produce reasonable answers. Understand the starship and the crew. Know enough about the rules that they support the moment rather than interrupting it.

Then listen.

Players will tell you what they find interesting by what they investigate.

They will tell you what they care about by whom they try to save.

They will tell you what kind of Starfleet officers they have become by the decisions they make when phasers would be easier than diplomacy.

And occasionally they will invent a solution so wonderfully Star Trek that the only appropriate response from behind the Game Master's screen is to smile, consider the consequences for a moment, and say:

"All right. How are you going to do that?"

Perhaps that is why it took me months to really learn how to run Star Trek Adventures. I was learning the rules, certainly, but I was also learning when to get out of their way. I was learning that preparation does not mean predicting the story, that improvisation does not mean being unprepared, and that giving players freedom does not mean surrendering structure.

It means knowing your universe well enough to let people explore it.

After all these years of Game Mastering, there aren't many things more satisfying than realizing that the players have just taken an episode somewhere I never expected it to go—and discovering that I can still keep up with them.

Most of the time, anyway.

And when I can't?

Well, Captain, that's why we have commercial breaks.

 

The Audacity to Build a Universe

There is a particular kind of thought that becomes uncomfortable almost as soon as you say it aloud.

I want to become a famous worldbuilder.

Even writing the sentence makes me hesitate. There is something about declaring an ambition openly that feels vaguely improper, particularly when the ambition is large. It is much easier, and certainly safer, to say that I simply want to write some good books, create some interesting worlds, run some memorable games, and perhaps find an audience along the way. Those are respectable aspirations. They are modest enough that nobody is likely to raise an eyebrow.

But they are not quite the truth.

The truth is that I want to build something extraordinary.

I want to create a science-fiction universe large enough, deep enough, and consistent enough that people can wander through it for years. I want readers to argue about its history, gamers to explore its forgotten corners, and perhaps someday people I will never meet to draw maps of places that began as marks on one of mine. I want the civilizations, wars, colonies, trade routes, political movements, explorers, starships, and ordinary people of Known Space to acquire that peculiar quality possessed by the fictional worlds I have loved throughout my life: the feeling that somewhere, somehow, they continue existing after I close the book.

And occasionally I stop and ask myself a rather uncomfortable question.

Is that ambition?

Or is it hubris?

The distinction matters.

Hubris, at least in its classical sense, is not merely having an enormous dream. It is the conviction that one is somehow entitled to greatness, that the normal limitations governing everyone else should not apply, or that greatness has already been achieved simply because one has imagined achieving it. There is something almost tragic about hubris because it confuses desire with destiny.

Ambition is different. Ambition looks at the mountain and says, I am going to try to climb that.

Hubris looks at the mountain and says, I belong at the summit.

I hope I understand the difference.

Because lately I have been thinking about the mountain.

I am sixty years old now, and there is something about reaching this point in life that changes one's relationship with time. When you are twenty, an unfinished project feels temporary. There will always be another year. There will always be another opportunity. The notebook can sit on the shelf because someday you will return to it. The novel can wait. The map can remain unfinished. The great project can begin next year.

Eventually, however, "someday" begins demanding an appointment.

That realization need not be morbid. In some ways I find it extraordinarily liberating. I have spent enough of my life discovering what interests me that I no longer need to apologize for those interests. I know what makes me happy. I know what fascinates me. I know the kinds of stories that have stayed with me since childhood, and I know what I want to spend my remaining creative years doing.

I want to build worlds.

Not casually.

Not apologetically.

I want to see how far I can take it.

That means pushing myself.

It means there are mornings when inspiration does not arrive and I work anyway. It means there are maps that need correcting for the third or fourth time because consistency matters to me. It means opening old manuscripts and discovering that a date I wrote fifteen years ago contradicts something I established elsewhere, and then spending an afternoon untangling the chronology rather than pretending nobody will notice.

It means learning things I did not know I needed to learn.

Astronomy leads to stellar evolution. Stellar evolution leads to questions about planetary formation. Planetary formation leads to orbital distances and temperatures. Those lead to climate, which leads to agriculture, which leads to economics, which leads to trade, which leads to politics, which leads to war, which leads back to the map.

Worldbuilding is wonderfully inconvenient that way. Everything eventually connects to everything else.

That interconnectedness has become one of the great pleasures of my work.

The universe I have been constructing for years—Known Space, and particularly the Aurin Cluster where so many of my stories take place—is increasingly becoming something I can examine rather than merely invent. I can look at a world on a Traveller-style sector map and ask why it is there, who discovered it, when it was surveyed, when the first permanent colony was established, what civilization claimed it, what routes connected it to neighboring systems, and how those relationships changed across centuries.

Sometimes the answers already exist in notes written years ago. Sometimes they are buried in an old manuscript. Sometimes a roleplaying campaign established something I had almost forgotten. Occasionally two sources disagree and I have to become the historian of my own imaginary universe, deciding which account represents the truth.

I find that enormously satisfying.

There is something almost absurd about carefully establishing the founding date of a fictional colony that perhaps twenty readers will ever hear about. Yet I don't regard the work as wasted. The reader does not need to know everything the author knows. In fact, I think the opposite is true. The reader should always suspect that there is more.

A fictional universe becomes convincing when the horizon extends beyond the story.

If a character mentions a war that happened three hundred years earlier, I want that war to have happened. I want to know approximately when it began, why it began, who fought it, and what consequences remained generations later. If a merchant vessel follows an established jump route through the Aurin Cluster, I want that route to exist on the map. If a colony orbits one member of a binary star system, I want to understand what those stars are doing to one another and what that means for the worlds around them.

Almost none of this needs to appear in exposition.

It simply needs to be true.

Perhaps that is the strange obsession at the center of my approach to worldbuilding: I want imaginary things to possess facts.

Not vague possibilities that change whenever a plot requires them, but facts. This world is here. This star is this type. This colony was founded during this period. This empire reached this boundary. This war altered this region. This exploration vessel passed through here before settlers followed generations later.

Once something becomes fixed, something interesting happens.

I can stop inventing around it and start discovering its consequences.

That is when worldbuilding becomes exciting for me.

It is also where gaming has been such an important part of my creative life. A roleplaying setting cannot exist entirely as scenery because players have the inconvenient habit of walking behind the scenery. They ask questions the creator did not anticipate. They travel toward the supposedly unimportant world. They want to know what company owns the starport, why the local government dislikes its neighbor, how long the abandoned station has been drifting there, and whether the old military route on the map is still usable.

A novelist can sometimes quietly guide the audience away from the unfinished parts of the set.

A game master has no such luxury.

Players will find them.

After decades of running games, I suspect that experience has permanently shaped the way I write fiction. I instinctively want the door at the end of the corridor to open, even if I never expected anyone to try it. I want there to be something on the other side.

That does not mean everything must be designed in advance. If anything, Traveller taught me the opposite. Procedural generation, randomness, and improvisation have been some of my most productive collaborators. A randomly generated result often gives me something I would never have deliberately chosen, and then my job becomes figuring out why it makes sense.

That interplay between order and randomness fascinates me. I establish the framework, allow chance to disturb it, and then use intuition to decide what deserves to become permanent. Gradually the accidental becomes historical. A random world becomes a colony. The colony acquires neighbors. The neighbors acquire interests. Those interests create conflict. Conflict becomes history, and eventually history becomes another line on the map.

Years later, I may not even remember which part began with a die roll.

By then it is simply true.

This is why I have become increasingly serious about documenting the chronology of Known Space. I am pulling dates from scattered manuscripts, campaign notes, sector files, old maps, and half-remembered ideas and trying to assemble them into a single coherent historical structure. I want to know when sectors were explored, when subsectors were surveyed, when colonies were established, when political entities appeared and disappeared, and how the great periods of expansion and collapse relate to the lives of the characters in my novels.

It is painstaking work.

I love it.

And that brings me back to the uncomfortable ambition with which I began.

I want to become a famous worldbuilder.

There. I said it again.

But perhaps I have been concentrating on the wrong word.

Famous is largely beyond my control.

I cannot command readers to care. I cannot declare that something I have created deserves a place alongside the fictional universes that inspired me. History is filled with writers who believed they were creating masterpieces and were forgotten, just as it contains writers who never imagined their work would survive them.

Recognition belongs to other people.

The building belongs to me.

That is the part I can control.

I can sit down tomorrow and map another subsector. I can reconcile another historical contradiction. I can finish another novel. I can calculate another world's orbit, create another civilization, document another century, and make one more corner of Known Space slightly more coherent than it was yesterday.

Perhaps the healthier ambition, then, is not to become famous at all.

It is to become worthy of being remembered.

Those are very different goals.

Fame asks, How many people know my name?

Craft asks, How good can I make this?

That second question interests me much more, because there is no obvious endpoint. Every time I learn something new, I discover another weakness in what I built before. Every improved map reveals something that needs reconsideration. Every new story exposes another unexplored corner of the universe. The project grows alongside the person creating it.

There is humility in that, or at least there ought to be.

The universe is always larger than the map.

The story is always larger than the outline.

And the work one imagines creating is always more magnificent than the work actually sitting on the desk.

The distance between those two things is where effort lives.

So perhaps it is not hubris to dream enormously.

Perhaps hubris would be believing that dreaming is enough.

If I announced that I had already created one of the great science-fiction universes merely because I had filled hard drives with maps and notes, that would be vanity. If I believed readers owed me attention because I had spent years doing the work, that would be entitlement.

But looking at the worlds I have built so far and saying, I wonder how far I can take this before I'm finished?

I don't think there is anything wrong with that.

I think there is something rather wonderful about it.

At this stage of my life, I have little interest in deliberately making my dreams smaller so that failure will hurt less. I would rather attempt something unreasonable and discover how much of it I can accomplish.

There are still books to write. There are still sectors to map. There are histories that exist only as fragments scattered across old notes, waiting to be reconciled. There are colonies without founding dates and worlds whose suns I have not yet properly considered. There are wars that need causes, borders that need histories, civilizations that need centuries in which to become themselves.

There is an enormous amount of work left.

Good.

I would be terribly disappointed if there weren't.

Because perhaps the dream was never really to finish Known Space.

Perhaps the dream is to spend the years I have been given exploring it, pushing farther into the map, becoming a better writer and cartographer as I go, and leaving behind enough interstellar trade routes, worlds, histories, and stories that someone else might someday want to explore them too.

If that eventually makes me a famous worldbuilder, wonderful.

If it doesn't, I will still have built the universe I spent most of my life wanting to see.

And there is no hubris in doing the work.

 

Drawing the Horizon

There are moments, usually very late at night after everyone else has gone to bed, when I find myself staring at a map of stars and wondering whether I became a writer because I loved maps, or whether I became fascinated with maps because, somewhere deep inside, I was always trying to write stories that were simply too large to fit on a single page. After all these years, I honestly cannot say which came first. Memory is an unreliable historian, prone to polishing rough edges and arranging events into tidy narratives that probably never existed quite that way. What I do know is that maps have occupied my imagination for as long as I can remember, not merely as practical tools for finding one's way from one place to another, but as objects that quietly suggest a much deeper truth about the world. Every map, no matter how simple, is really an admission that there is more beyond the edge of our immediate experience than we can ever fully know.

As children we learn that maps represent places. It is one of those lessons that seems so obvious we seldom question it. We unfold an atlas and are told that this line is a river, this color represents a mountain range, these dots are cities, and those borders separate nations. It is all very neat and orderly, as though the world patiently waited for cartographers to come along and describe it. Only much later does one begin to appreciate that maps do not simply record geography. They record history. Every coastline is the result of geological forces that have been at work for millions of years. Every national boundary is the visible scar left by diplomacy, migration, conquest, compromise, or exhaustion. Every road exists because countless people decided, over the course of generations, that this particular route was more useful than another. Even the empty places tell stories, although they whisper rather than shout. A desert says something very different about the human condition than a fertile river valley. An isolated island invites a different history than a crossroads between continents.

The longer one studies maps, the more one realizes that they are not static documents at all. They are biographies.

Perhaps that is why I have never been satisfied with treating a fictional map as decoration. In many novels a map serves much the same purpose as an illustration. It helps the reader understand where things happen, but once the story begins it quietly fades into the background, having fulfilled its obligation. There is nothing inherently wrong with that. Many wonderful books have done exactly this. Yet I have never been able to convince myself that such a map is truly alive. It tells me where the mountains are, but not why they matter. It shows me kingdoms without explaining why those kingdoms came to exist in precisely those places. It identifies rivers without asking how those rivers shaped commerce, agriculture, language, or the ambitions of generations long forgotten. A beautiful map can still feel strangely hollow if it has no memory.

That word—memory—has gradually become one of the central ideas in my approach to worldbuilding.

Civilizations remember.

Sometimes they remember accurately, and sometimes they remember badly, but they always remember. Roads remain long after the empires that built them have vanished. Religious boundaries survive political revolutions. Old trade routes continue to influence commerce centuries after the original reasons for their existence have been forgotten. Languages carry echoes of migrations that occurred before written history. Cities are built upon older cities, each generation leaving behind foundations that become invisible to those who walk above them. The present is never created from nothing. It rests upon layer after layer of accumulated decisions stretching backward through time.

I have always believed that fictional universes deserve the same courtesy.

It is a curious phrase when one thinks about it. Courtesy. Yet I can think of no better word. If I ask a reader to suspend disbelief and accept that humanity has spread among the stars, that governments have risen and fallen across hundreds of worlds, that merchants cross interstellar distances in search of profit while explorers continue pressing against the boundaries of the unknown, then surely I owe that reader a universe that behaves as though those things have actually happened. Not because every detail must appear on the page, but because every detail should exist whether it appears or not.

This conviction has led me down some wonderfully strange roads.

There are evenings when I begin with the innocent intention of placing a single new world upon a map and discover, several hours later, that I have spent the entire night researching stellar evolution, binary orbital stability, atmospheric chemistry, or the economics of frontier trade. To anyone observing from the outside, it would seem an extraordinary amount of effort for a planet that may occupy no more than two paragraphs in a novel years from now. Sometimes I smile at the absurdity of it myself. Then I remember that medieval cathedral builders devoted entire lifetimes to carving details into stone ceilings that almost no one would ever examine closely. They did it because the integrity of the whole depended upon the care invested in every part, whether visible or hidden.

Worldbuilding, at least for me, has become something very similar.

People occasionally ask how many worlds exist in my setting, and I honestly cannot answer the question with any certainty. There are too many, and every year there are more. The map continues to expand, not because I have set out to create the largest fictional universe imaginable, but because every answer naturally gives birth to another question. Place a colony here and one must ask where its settlers originated. Answer that question and another immediately follows: why did they leave? If they left because of political unrest, then what caused that unrest? Was it economic? Religious? Environmental? Military? Once that history exists, neighboring worlds begin reacting to it, because history is never isolated. Every decision exerts a kind of gravitational pull upon the decisions around it.

This is where Traveller entered my life and quietly altered the way I think about creation itself.

Many people know Traveller because of its elegant rules, its straightforward vision of interstellar adventure, or its remarkable longevity as a roleplaying game. For me, however, Traveller offered something far more profound than a rules system. It offered a philosophy. It suggested that universes need not be entirely invented. They could be discovered.

That may seem like an odd distinction, but I believe it lies at the heart of procedural generation.

There is sometimes an assumption that using tables, dice, or algorithms somehow diminishes creativity, as though accepting the guidance of probability were an admission that one's imagination has failed. My experience has been precisely the opposite. Left entirely to my own preferences, I begin repeating myself without realizing it. I favor familiar climates, familiar political arrangements, familiar patterns of settlement. Imagination, for all its virtues, develops habits. Randomness interrupts those habits. It politely but firmly asks questions I would never have thought to ask on my own.

What if this habitable world orbits not one sun but two?

What if the primary star is dimmer than expected?

Why would a prosperous civilization choose to settle such an inconvenient system?

How does a colony survive when its nearest neighbors lie several parsecs away?

These are not inconveniences.

They are invitations.

The dice have not written the story. They have merely asked a better opening question than I was about to ask myself.

Over time I have come to think of procedural generation less as creation than as conversation. The tables propose. I respond. Sometimes I reject a result because it contradicts the larger logic of the setting. More often I find myself accepting an unexpected outcome simply because it leads somewhere more interesting than my original plan. Randomness, when treated with respect rather than obedience, becomes an extraordinarily creative collaborator. It possesses no imagination whatsoever, yet it continually pushes mine into unfamiliar territory.

There is another idea that has gradually become inseparable from all of this, and it is a word I have probably repeated more often than my readers would care to count.

Consistency.

At first glance consistency seems rather dull. It lacks the romance of exploration or the excitement of discovery. It sounds like bookkeeping, and perhaps there is a little truth in that. Yet I have come to believe that consistency is one of the deepest forms of respect an author can offer the people who invest themselves in a fictional world.

Reality is consistent.

Not perfect.

Not predictable.

Certainly not fair.

But consistent.

The laws governing the universe do not change because the next chapter requires them to. Continents do not drift overnight. Rivers do not decide to flow uphill because it would produce a more dramatic scene. History leaves consequences, and those consequences accumulate. If I expect readers to believe in the Aurin Cluster, then the Aurin Cluster must possess the same quiet reliability. A trade route established centuries ago should continue influencing commerce unless history provides a reason for its disappearance. Political borders should remain stable until politics changes them. A colony founded upon an arid world should not suddenly become lush simply because I forgot what I wrote five years earlier.

Readers seldom notice consistency directly.

They feel it.

The effect is almost subconscious. They begin trusting the setting because it behaves as though it exists independently of the current story. That trust is one of the most valuable gifts a worldbuilder can earn.

Maintaining that trust has required more tools than I ever imagined owning. Over the years I have accumulated mapping software, astronomical references, databases, campaign notes, timelines, spreadsheets, Traveller utilities, and enough interconnected files that they sometimes resemble a small archival project more than the workspace of a novelist. Campaign Cartographer, Cosmographer, Scabard, astronomical simulations, notebooks filled with observations made years apart—all of them contribute a small piece to the larger puzzle. None of them writes the stories. They simply preserve the memory of the universe so that I do not have to rely entirely upon my own.

And yet, for all the software, all the calculations, all the careful organization, I have come to suspect that what I am really building is not a collection of maps at all.

I am building confidence.

Confidence that when a reader encounters a remote colony in one novel, that world has neighbors. It has ancestors. It has weather shaped by its sun, a calendar shaped by its orbit, politics shaped by centuries of compromise, and ordinary people whose lives extend beyond the boundaries of the chapter in which they briefly appear. The reader may never consciously think about any of this, but I hope they will sense it in the same way one senses the age of an old city without knowing every event that occurred there.

Known Space has gradually become the canvas upon which all of these ideas converge, and within it the Aurin Cluster has become the place where they are tested. Most of my stories begin there. Most of my Traveller campaigns unfold there. It is no longer simply a setting. It has become, in a very real sense, a historical landscape whose future I discover one story at a time. Every new system enriches those around it. Every new trade route changes someone's fortunes. Every border carries the memory of an old argument. Every unexplored hex reminds me that the unknown remains as essential to imagination as the known.

Perhaps that is why I no longer think of myself primarily as an author inventing worlds.

More often, I feel like a cartographer standing at the edge of an unfinished chart.

There is something profoundly hopeful about that image. The old maps of our own world often carried blank spaces around their edges, not because the cartographers lacked skill, but because they possessed humility. They understood that knowledge is always incomplete, that every generation inherits mysteries it cannot fully solve, and that tomorrow's explorers will return with discoveries that force today's maps to be redrawn.

I find myself hoping that my own fictional universe always retains a few blank spaces as well.

Not because I have neglected to fill them, but because wonder requires horizons.

The day every mystery has been cataloged, every star named, every civilization completely explained, and every question answered will be the day the universe becomes smaller than the imagination that created it.

I would rather leave another unexplored hex waiting beyond the frontier.

After all, every journey worth taking begins with a map, but no great journey has ever ended there. The map is only the first promise that somewhere beyond the horizon lies a story waiting to be discovered, and I suspect that as long as I am able to write, I will continue adding one more star, one more world, one more forgotten trade route, and one more page to the long history of a place that exists nowhere except in my imagination—and, if I have done my work well enough, in yours as well.

 

Why Every Great Space Opera Has History

When most people think about space opera, they imagine starships.

Huge battles between fleets.

Alien civilizations.

Faster-than-light travel.

Exotic planets orbiting distant suns.

Those things are certainly part of the genre, but I don't think they're what keeps readers coming back.

I think readers come back because of the history.

Not the history they're reading.

The history they feel.

Civilizations, Not Technology

Take a moment and think about some of the greatest space opera settings ever created.

Isaac Asimov's Foundation begins after thousands of years of Galactic Empire.

Frank Herbert's Dune takes place over ten thousand years into humanity's future, where entire institutions have risen and fallen countless times.

Star Trek presents a Federation with centuries of exploration behind it, surrounded by powers whose own histories stretch back even further.

Babylon 5 isn't simply about a diplomatic station. It's built upon ancient races, forgotten wars, and mysteries that have shaped younger civilizations for millennia.

The Expanse may feel more contemporary, but even there, the tensions between Earth, Mars, and the Belt come from decades of political evolution before the first page ever begins.

Traveller has always understood this as well. Behind every subsector map lies the weight of the Third Imperium, the Long Night, the Rule of Man, and civilizations whose ruins still influence the present.

None of these universes begin at Year One.

They arrive already carrying the weight of history.

History Makes a Universe Feel Real

Think about visiting an old European city.

You walk through streets where people have lived for hundreds or even thousands of years.

Buildings have been rebuilt.

Governments have changed.

Wars have been fought.

Empires have risen and collapsed.

You don't need someone to explain every event for the place to feel authentic.

You simply know that generations came before you.

The same principle applies to great space opera.

The best fictional universes don't feel freshly constructed.

They feel inherited.

Every Ruin Tells a Story

One of my favorite things to place in a science fiction setting is something abandoned.

An orbital station nobody remembers how to repair.

A colony ship that never reached its destination.

A jump beacon still functioning after three centuries.

An empty military fortress whose enemy disappeared generations ago.

A planet where the cities remain but the people do not.

None of these need lengthy explanations.

Their existence creates questions.

Who built this?

Why was it abandoned?

What happened here?

History becomes another character in the story.

Wars Leave Shadows

History isn't simply about dates and timelines.

It's about consequences.

Borders exist because somebody fought for them.

Trade routes exist because explorers found them.

Refugees settle new worlds because somewhere else became unlivable.

Political alliances form because two civilizations once faced a common enemy.

Even peace has a history.

When readers sense these invisible layers beneath the narrative, the universe suddenly feels much larger than the story itself.

The Universe Keeps Moving

One of the lessons I've learned over decades of running role-playing games is that worlds shouldn't stop evolving just because the players aren't looking.

Governments change.

Companies fail.

Colonies prosper.

Religions divide.

Technology advances.

Heroes grow old.

Children become leaders.

History never pauses.

It simply waits for the next generation to inherit it.

Building the Aurin Cluster

This idea has become one of the guiding principles behind my own universe.

For years I imagined I needed to design an entire galaxy before I could tell meaningful stories.

Eventually I realized something simpler.

Nearly all of my novels—and nearly all of my Traveller campaigns—take place within one region of space.

The Aurin Cluster.

Rather than spreading my efforts across thousands of worlds all at once, I'm concentrating on making this one region feel authentic.

Every polity has a reason for existing.

Every border has a history.

Every trade route developed because someone discovered it, fought over it, or depended upon it.

Every abandoned station, forgotten colony, and ruined battlefield exists because something happened long before my characters arrived.

My hope is that readers never feel like they're walking through a stage set.

Instead, I want them to feel like they've stepped into a living civilization that has been evolving for centuries—and will continue evolving long after the story ends.

Looking Back from the Future

Sometimes I imagine historians living five hundred years after the events of my novels.

What would they write about?

Which wars would they remember?

Which explorers would become legends?

Which political decisions would reshape entire civilizations?

If I can answer those questions, even if readers never see most of the answers, then I know the universe has begun to feel alive.

Because in the end, I don't believe readers fall in love with space opera because of starships.

They fall in love because those starships are sailing through civilizations that feel like they existed long before the first chapter—and will still exist after the final page is turned.