Map rotations are policy, not configuration

A map rotation looks like a list in a config file. It is the clearest statement a server makes about who it is for, and it is usually assembled by accident — maps added when somebody asked, none ever removed.

The result is a rotation that describes the history of requests rather than the identity of the server, and players read it accurately even when nobody wrote it deliberately.

What a rotation communicates

Three things, whether you intended them or not.

Who this is for. A rotation heavy on competitive maps says one thing; one full of joke maps and novelty gimmicks says another. A rotation containing both says the server has not decided, and the players who want either will find a server that has.

How long a session is. Twelve maps at twenty minutes is a four-hour loop. A player who joins twice a week sees a fraction of it and never develops familiarity with any of it. Familiarity is most of what makes somebody feel like a regular.

Whether newcomers are welcome. A rotation of six advanced maps is a closed door with no sign on it. Nobody is turned away; they simply have a bad first hour and do not return.

The accumulation problem

Rotations grow because adding is easy and removing is social. Somebody asks for a map, it gets added, and now removing it means telling that person no — retroactively, which is harder than saying no in the first place.

Ten years of that produces a forty-map rotation where two-thirds are played once a month and nobody can name them. The rotation is technically larger and functionally smaller, because the maps people actually like are now diluted.

The servers that stay healthy prune. It is uncomfortable and it is the single highest-leverage thing an admin can do to a rotation: the same restraint that keeps a plugin list from becoming a liability.

The case for a short rotation

Six to eight maps is enough for variety and short enough that a twice-a-week player learns them all.

That learning is the mechanism. A player who knows a map has opinions about it, positions on it, and moments they remember on it. A player cycling through forty maps has none of that for any of them, and a server where nothing is familiar is a server nobody is attached to.

This is the same density argument that makes a small server feel busier than a large one: concentration produces attachment, dispersion produces indifference.

Voting is not a neutral mechanism

Map voting sounds democratic and reliably produces the same three maps forever, because the plurality is whatever the current population already likes, which is a feedback loop, not a preference.

The people who would have liked map four are not there to vote for it, because they left when it stopped appearing. A vote measures who is present, and who is present was determined by previous votes.

If you use voting, seed it: force a map that is not in the winning set every few rounds. That is not undemocratic; it is the only way the vote keeps measuring anything.

Rotations as a scheduling tool

The other thing a rotation can do, and almost never does, is match the time of day.

Peak hours want the maps that work with a full server. Quiet hours want small maps that are playable with six people. A server running its 32-player flagship map at 3am with five people on it is presenting its worst face to whoever arrives, which is precisely the window where a newcomer's first ten minutes decide everything.

Most server software can do time-based rotation. Almost nobody configures it.

The map that is carrying the server

Every long rotation has one map that is doing a disproportionate share of the work, and most owners cannot name it.

It is the one where the population climbs rather than holds, where people who were about to leave stay for another round, and where the chat is busiest. It is frequently not the map the regulars say they like best, because what people enjoy and what keeps them logged in are different questions with different answers.

Finding it takes nothing more than watching the player count against the rotation for a week. The reason to bother is that a rotation is usually pruned by asking people what to remove, and what actually matters is knowing what must not be removed.

Servers that lose their carrying map to a vote never quite recover, and nobody afterwards connects the decline to the change, because the map that went was genuinely unpopular with the people who were asked.

How to change one

Write down what your server is for, in one sentence. Then read the rotation and remove everything that does not serve it.

That will be uncomfortable and it will be the most informative half-hour you spend on the server, because the maps you cannot justify removing are the ones that tell you what the server has actually become, which is not always what the owner thinks it is, and is exactly what a stranger sees on any listing before deciding whether to join.