The first thirty seconds

Think back to the last new server you joined. Not the one you've been playing for years: any old one, the kind you try out for an afternoon. It's very likely you decided whether you liked it before playing absolutely anything. You didn't reason it out. You didn't compare modes or look at the shop. You simply appeared somewhere and something inside you said this looks good or this is just another one.

That judgement happened in about thirty seconds. And it is, almost certainly, the stretch of the experience that the fewest people design.

Thin slices

In the early nineties, the psychologists Nalini Ambady and Robert Rosenthal ran an experiment that is still uncomfortable. They filmed university lecturers teaching and cut out clips a few seconds long. Without sound. Then they showed them to people who had never met those lecturers and asked them to rate them.

The ratings of those strangers, made from a few seconds of silent video, were remarkably similar to those of the students who had spent an entire semester in their classes. Ambady and Rosenthal called this phenomenon thin slices: judgements formed from a ridiculously small amount of information, and strikingly persistent afterwards.

It's best not to conclude from this that first impressions are wise. The lesson is a different one, and more useful: that they form anyway, whether or not we have enough information, and that afterwards they are very hard to shift. The mind doesn't wait for data. It fills in.

A spawn is a thin slice. It is the few-second fragment from which someone is going to build a whole idea of a place where they might spend years.

What gets read in half a minute

If you watch what a person actually does in their first thirty seconds, they aren't playing. They're reading the place. And they read quite specific things.

They read whether anyone else is there. A place without movement is interpreted as abandoned almost instantly, however beautiful it is; seeing other people talking, running or building makes the brain conclude that something happens there. They read whether there's hostility: if the first thing to cross the chat is a fight, they already know what kind of place it is. They read whether there's something in the distance that makes them want to head towards it — a tower, some islands, a pier — because curiosity needs a visible destination. They read the sound, which almost nobody considers and which does more emotional work than half of what can be seen. And they read, above all, whether they're being asked for something.

That last point is what separates two experiences that look very similar from the outside. There are places where you arrive and they let you look. And there are places where you arrive and, before you've even turned the camera, they've already shown you three signs, an offer with a countdown, a notice that someone has bought a rank and a menu that opens by itself. None of those things is for you. All of them are for the place.

The mistake isn't ugliness, it's haste

When a spawn fails, it's almost never because it's badly built. It fails through haste.

Haste has an understandable logic. Everyone passes through there, so it seems the obvious place to put whatever you want to be seen. And there's a reasonable fear that someone will come in, understand nothing and leave, from which comes the urge to explain everything as soon as possible: the rules, the modes, the commands, the ranks, the Discord, Saturday's event. All at once, in one go.

The result is paradoxical. In trying to make sure nobody gets lost, you make sure everyone feels overwhelmed. Someone who has just arrived can't process fifteen messages; what they do is stop reading them. And in trying to make sure nobody leaves, you convey exactly what drives people away: that this place is in a hurry to get something out of you.

The opposite isn't explaining nothing, either. It's explaining at the moment it's needed, and not a second before. Letting guidance appear when someone looks for it, not when they appear. Having a clear place to go, without going there being compulsory. Making sure the first minute demands no decision at all.

Holding back is the hard part

There's an ugly asymmetry in all this. Designing noise is easy and noticed straight away; holding back is hard and never noticed. Nobody writes on a forum that they liked a server because it didn't interrupt them when they joined. The absence of overwhelm isn't remembered as a merit: it's remembered, with luck, as a place where it felt good to be.

That's why the places that get the half-minute right tend to be places made by someone who thought about the person arriving rather than the figure they produce. The difference between asking how do I stop them leaving and asking how do I make them feel oriented and at ease isn't a nuance. It gives rise to two different places, and you can tell in the first few seconds of each.

Arriving at a place, not a platform

There's an image that captures well what is at stake here. The difference between entering a platform and entering a home.

When you enter a platform, the place immediately starts working on you: it offers, it suggests, it measures, it nudges. When you enter a home, the home does nothing. It lets you take your coat off. And yet within two seconds you can tell whether you're comfortable, because someone thought about what it's like to be there before you arrived.

A server can be either of those things, and it's decided almost entirely in the first half-minute. Not in the map, nor in the list of modes, nor in what the description says. In whether someone, while building the door, remembered who was going to walk through it.

Next time you try a new place, stand still for thirty seconds before you touch anything. You'll learn much more than you think.