Recently, I found myself forming an impression of a multiplayer gaming project I had barely seen being played.

One short video claimed that almost the entire server had been banned. Another suggested the organizer had admitted to being a terrible owner. A third simply asked what was going on, accompanied by a crying emoji.

I didn’t know whether these headlines were serious, exaggerated, or jokes among people familiar with the project. I hadn’t watched enough to judge. Yet, after encountering a handful of clips, I was beginning to feel strangely informed.

I recognized the arguments, the names involved, and the questions people were asking. What I couldn’t tell you was much about the game itself.

I even found myself trying to understand a rumored rule restricting which players were allowed to kill others. I couldn’t establish whether the rule existed, let alone how it worked. Still, I was already wondering whether it was fair.

Somehow, I had become interested in the management of a game without developing much interest in what its participants were actually doing.

One video had simply led to another, each offering a new question to follow. My curiosity wasn’t directed at what the players would do next. I wanted to know how someone would respond to the latest controversy.

At first, I wondered whether the project itself had lost its direction. But I hadn’t seen enough to make that judgment.

What stayed with me was how naturally a conversation about an experience could become an attraction of its own. And what that might mean when the project eventually returned for another season.

The second story

Games are wonderful at producing stories nobody planned.

Someone builds a hidden passage beneath a rival settlement. A group discovers that their supplies have been stolen. An unlikely alliance forms, only to collapse when someone realizes they’ve been betrayed.

These situations are entertaining because of the environment that makes them possible. The layout of the world, the resources available, and the decisions players make all contribute to the outcome. A clever trick in Minecraft might be meaningless in another game.

But wherever people interact, disagreements are inevitable.

Perhaps someone questions whether the theft was allowed. The rules weren’t clear, or an organizer makes a decision that not everyone agrees with. Suddenly, there’s another story to follow.

Who was right? Was the ruling fair? Should the rules be changed?

These are reasonable questions. Shared experiences need boundaries, and discussing them can be essential to maintaining an enjoyable environment.

But the new story has an unusual quality: it doesn’t require much knowledge of the game.

We all recognize disagreements about fairness, authority, and responsibility. We understand the frustration of feeling mistreated or having a decision questioned. We can become curious about these situations long before we understand the circumstances that produced them.

Judging the disagreement fairly might require considerable context. Becoming interested in it doesn’t.

An organizer explains a decision. Someone challenges the explanation. Another person responds, bringing up an earlier incident. Soon, the discussion has acquired its own history, familiar personalities, and unresolved questions.

The original event is still there, somewhere in the background. But following the exchange no longer requires us to understand exactly what happened in the game.

The game produced the first story. The conversation has started producing the next one.

And that second story can travel much further than the first.

What the audience gets to see

Consider an evening spent playing with friends.

You explore, build something together, get into trouble, laugh about a ridiculous mistake, and eventually disagree about a rule. The disagreement takes a while to resolve, but it’s only one part of an otherwise enjoyable evening.

Now consider someone who never saw that evening.

They encounter a short video about the disagreement, followed by a reaction, and perhaps an explanation from the organizer the next day.

For this viewer, the disagreement isn’t an interruption of the experience. It’s nearly everything they’ve seen.

Nobody has to be dishonest for this to happen.

Every clip is a selection. Even a perfectly accurate video presents only a narrow window into something larger. When those windows repeatedly show the same kinds of events, they begin to shape what an outside observer associates with the project.

The discussion also provides its own continuity. Once we know the people involved and remember their previous disagreements, each new response carries meaning. We’re no longer starting from scratch. We’ve learned enough about the conversation to follow it comfortably.

Meanwhile, the game continues.

Players might discover unexpected possibilities, develop clever strategies, or create memorable moments together. But none of those developments necessarily answers the questions we’ve become invested in.

An impressive construction doesn’t tell us whether a controversial decision will be reversed. An unexpected alliance doesn’t resolve an argument about the rules.

So another response can feel more relevant than an evening full of gameplay.

The game doesn’t have to become less interesting. We can simply become interested in something else.

And because we’re still following the same people and the same project, that change can be surprisingly difficult to notice.

It also creates an interesting situation for the people producing the content.

A creator publishes an explanation because viewers deserve one. Another responds because they genuinely disagree. Someone shares the exchange because they find it interesting. Each decision makes sense on its own.

Together, these interactions can create an environment in which conversations about the project become increasingly visible and easier to follow.

New viewers may arrive knowing the controversies better than the gameplay. Existing viewers may begin anticipating familiar disagreements. Others remain interested in the game itself.

These audiences are following the same project, but they aren’t necessarily waiting for the same things.

And that distinction matters when the project returns.

The next season doesn’t start from zero

Let’s return to the stolen supplies.

Imagine the disagreement about that theft becoming one of the most widely discussed events of the season. The theft itself was an unexpected part of the game, but the debate about whether it should have been allowed continued long afterward.

Eventually, the season ends.

The organizers review the feedback, clarify the rules, and prepare a new season. They want to prevent misunderstandings and make the experience better for everyone.

So far, everything sounds like a sensible improvement.

But when the next season begins, the audience doesn’t arrive with a blank memory.

Some viewers remember the previous controversy. They know which rule caused the disagreement, who defended the decision, and who criticized it.

Before anyone has stolen a single item, a familiar question is already waiting:

What happens when someone tests the new rule?

Eventually, a player does something resembling the previous incident. The circumstances might be entirely different, and the updated rules might address the situation perfectly.

Still, viewers familiar with the earlier disagreement recognize the similarity. Someone makes a comparison. Another person explains why this situation is different.

An event that would once have been judged primarily by its place in the game now carries the history of an earlier conversation.

The organizers may have improved the experience considerably. Yet part of the audience is watching for something the previous season taught them to expect.

This alone doesn’t change the format. Audience expectations and creative decisions are two different things.

But now suppose the organizers notice that viewers repeatedly ask for explanations of individual rulings. Rather than answering the same questions throughout the week, they introduce a short segment after each session to discuss decisions and clarify the rules.

It’s useful, transparent, and well-intentioned.

It’s also a new feature of the show.

What once happened occasionally around the game now has a regular place within its presentation. Viewers know when to expect explanations, editors have another kind of content to highlight, and each discussion can provide context for the next.

The audience’s expectations have moved beyond influencing how the experience is interpreted. They’re beginning to influence how it is presented.

This is only one possible path. Organizers can choose not to change their format, and an audience’s interests don’t automatically determine what creators produce.

But when those interests do inform creative decisions, the effects can accumulate across iterations.

A project doesn’t only inherit its participants, mechanics, and lessons from previous seasons. It also inherits an audience with an increasingly established idea of what makes it entertaining.

Designing for the experience

I’ve spent a fair amount of time thinking about game design, particularly the feelings that games create.

In an earlier article, Feeling First, I explored the idea of beginning with the experience we want players to have rather than simply assembling mechanics and hoping something interesting emerges.

Multiplayer party games make this especially apparent. The rules are important, but the moments I care about are what happens between people because of those rules.

The unexpected cooperation. The ridiculous betrayal. The laughter when a clever plan fails spectacularly.

Those moments are difficult to prescribe. We can create opportunities for them, but much of their appeal comes from allowing players to surprise one another.

That makes the distinction between an experience and its surrounding conversation relevant from a design perspective.

Suppose I created a multiplayer game intended to encourage playful competition. One evening, a disagreement about the rules becomes the most discussed event. People begin sharing reactions, comparing interpretations, and questioning how the game was managed.

My immediate concern wouldn’t be that people were discussing the rules. Their criticism might reveal something I need to improve.

I’d be more interested in what people were taking away from the experience.

Did the game produce the feelings I intended? Were those moments meaningful to the players but largely invisible to the audience? Or had the rules themselves become a source of frustration that overshadowed the experience?

Those questions point toward very different decisions.

Clearer rules might improve the game. Better presentation might help an audience appreciate what the players are doing. In other circumstances, the surrounding social discussion might be the most entertaining part of the format, and there may be good reasons to embrace it.

What matters is recognizing which experience we’re designing for.

Because once a project has an established audience, the temptation to build on what already attracts attention is entirely understandable.

You learn what people respond to. You recognize familiar patterns. You find ways to make the next iteration smoother and more engaging.

That knowledge is valuable, but it can also create a subtle tension.

A format may become increasingly successful at delivering what its audience expects, while leaving less room in its presentation for the unexpected possibilities that once made it distinctive.

The game itself hasn’t lost those possibilities. The players might still be discovering them every day.

But an audience accustomed to following familiar social conflicts may have fewer reasons to look for something different.

And when the same creators move to another game, those expectations can come along.

The mechanics change. The world offers new opportunities. Yet the public conversation may quickly return to recognizable rivalries, disputed decisions, and familiar reactions.

The experience is new, but the audience already knows which story it’s waiting for.

What carries over

Looking back at those short videos, I still can’t say whether the project itself had lost anything.

Perhaps the participants were having a wonderful time. Perhaps the disagreements were important and justified. The fragments I encountered couldn’t tell me much about the experience as a whole.

But they revealed how easily an audience can become familiar with the conversation surrounding an activity without becoming familiar with the activity itself.

That distinction becomes more consequential when the project continues.

An audience doesn’t merely remember what happened. It develops expectations about what deserves attention. Those expectations influence how new events are understood, and sometimes the decisions made about what to present next.

Over successive iterations, a format can drift toward the parts of itself that audiences already recognize, even while the underlying activity continues offering something entirely different.

For someone designing these experiences, that seems worth remembering.

Improving a familiar formula is valuable. So is listening to an audience. But neither should be confused with preserving the conditions that allow genuinely unexpected stories to emerge.

The next project might offer new mechanics, a fresh environment, and opportunities nobody has explored before.

Whether those possibilities become the stories people care about depends on more than what the creators put into the game.

It also depends on what the audience arrives looking for.

You can reset the world. But you don’t reset what the audience has learned to care about.