What timezones do to a community

Two people can be regulars on the same server for a year and never meet. Nothing is wrong with the server; they are simply awake at different times, and a community is made of overlap rather than of membership.

This is the least discussed structural fact about running a server, and it quietly decides more than most of the decisions owners agonise over.

A server is several communities wearing one name

The evening crowd and the late-night crowd are different groups with different norms. They have different jokes, different tolerance for noise, and frequently different opinions about the rules — not because anybody disagreed, but because each group worked out its own conventions without meeting the other.

The admin usually knows one of them well and the other by report. Whichever one shares their timezone is the one they experience as "the server", and the other is a set of logs.

That asymmetry is fine until a dispute crosses the boundary, at which point a decision gets made about people the decider has never played with.

Why the second timezone never quite takes

A server that is busy at 20:00 UTC and empty at 04:00 does not have a quiet period. It has a period where arriving is unrewarding, and arriving is how the period would stop being quiet.

The loop is self-sealing: a newcomer at the wrong hour finds four people, decides the server is small, and does not come back. Their absence keeps it at four. The measured shape of a server's day is therefore not evidence about demand across the day — it is mostly a record of when the server was already busy.

Breaking it requires somebody to be present unrewarded for weeks, which is a real cost and the reason most attempts to grow a second timezone fail after a fortnight.

What actually seeds an off-peak population

Not advertising it. A group.

Off-peak populations start when three or four people who already know each other decide to play at the same time, and they hold because those people are each other's reason to be there. One committed player at 04:00 is alone; four are a session, and a newcomer who arrives finds something happening.

This is the same mechanism as seeding a server at launch, with the difference that the server already exists and the empty hours look like a failure rather than a beginning.

The region question is not the timezone question

Where the machine is affects ping. What time people play affects whether there is anybody to ping.

These get conflated constantly, and a server that moves its host to chase a population has usually solved the smaller problem. A hundred milliseconds is noticeable; an empty server is decisive, and the tradeoff only looks close because latency is the part that is easy to measure, which is how region decisions get made on the wrong number.

What to do about the split

Name it. A server that says plainly that it is busiest at certain hours has removed the main way newcomers form a wrong impression, and the people who arrive at the quiet time arrive expecting it.

Give each side its own admin. The single most useful recruitment criterion on a server with a real split is not experience or judgement: it is being awake at the hour nobody else is.

Do not run events at one time forever. An event schedule anchored to the founder's evening tells the other half of the community what it is, and they are right.

Resist merging them. Attempts to force overlap (mandatory server-wide events, moving the whole rotation to one prime time) reliably annoy both groups. Two functioning populations under one name is a good outcome, not a problem to fix.

The handover that happens every day

On a server with a real split there is a moment each day when one population is leaving and the other is arriving, and almost nothing is designed around it.

It is the most useful hour the server has. It is the only time the two halves are in the same place, the only time a piece of news reaches everybody at once, and the only opportunity for the relationships that make two populations feel like one community rather than two servers sharing an address.

Servers that notice it use it: announcements go out then, events start then, and the admins from each side overlap deliberately rather than by accident. Servers that do not notice it have a quiet trough in the middle of the day where the outgoing crowd has left and the incoming one has not arrived, which reads to anybody browsing as a server that is emptying out.

The difference between those two is entirely a matter of having looked at a graph of the day once.

The part nobody says

The quiet timezone is usually treated as the server's weak half, and it is frequently the stronger one. Small groups that hold together without an audience, without events, and without the owner watching are made of exactly the people a server most wants to keep.

They are also the ones most likely to leave without anybody noticing, because the metric that would have shown it is buried under a peak that did not change.