Announcing maintenance so people come back

A planned outage and an unplanned one look identical to a player who did not know about it. The server is down, they do not know why, and whether they come back depends almost entirely on what they were told beforehand.

That makes the announcement part of the maintenance rather than something you do around it.

The three timings that matter

A week out, if it is significant. Anything that takes the server down for more than a few minutes, or that changes something players care about. A week is enough for people to plan around it and short enough that they still remember.

The day before. The reminder that actually works, because the week-out announcement has been forgotten by everyone except the people who were going to check anyway.

Fifteen minutes before, in game. Not five. Fifteen minutes is enough to finish a fight, get somewhere safe, and bank what you are carrying. Five produces a scramble and lost inventories, and lost inventories during planned maintenance are the ones people are angriest about, because they were avoidable.

On a roleplay server the in-game number is higher, because a scene takes longer to close than a dungeon run. Ask your players rather than guessing.

What the announcement has to say

Four things, and it is shorter than people make it:

• When it starts, in a timezone you have stated.
• How long you expect, with an honest margin rather than an optimistic one.
• What changes, in one sentence a player cares about — not the version number.
• What they should do, if anything. Log out somewhere safe, spend currency that is being reset, back up a build.

That last one is the item most often omitted and the one that prevents most of the complaints.

Overrun honestly

Maintenance runs long. When it does, say so at the time you said you would be finished, not when you actually finish.

"Still working, another hour" costs nothing. Silence past the stated time is what converts a planned outage into people assuming something went badly wrong, and the assumption is durable, because an unexplained absence is filled in by whoever is guessing.

Set a reminder for your own deadline. During the work you will not be watching the clock.

The one you can skip

Not everything needs an announcement, and treating every restart as an event is its own failure — a community that receives four notices a week stops reading them, and the one that mattered arrives to an audience that has learned to scroll past.

The line worth drawing: announce anything that takes something away. A restart that interrupts play, a change that resets progress, an outage of more than a few minutes. A routine nightly restart that people already expect does not need a fresh notice each time, only the standing one that says it happens.

That restraint is what keeps the important announcements legible.

Where to put it

Wherever your community actually reads, which for most servers is Discord rather than the game, and in the server's own MOTD as well, because that reaches the people who only ever see the server list without connecting.

The MOTD is the underused half. A player who opens their server list, sees your name greyed out, and reads "back at 07:00 UTC" has received the message without you reaching them at all.

Say when it is done

Short and specific: it is back, here is what changed, here is what to report if something looks wrong.

This is also the moment to have run the smoke test rather than to be running it: an all-clear that turns out to be wrong costs more than the outage did, because it spends the trust the good announcement earned.

Why this is worth the ten minutes

Every part of it is cheap and the alternative is expensive in a way that does not show up for weeks. Players who were not told do not complain; they quietly stop returning, and the population is down by five without any single person having said anything.

Planned maintenance handled well is one of the few things that makes a community more confident in a server rather than less: the demonstration that somebody is looking after it, which is exactly what a regular is trusting when they build something they cannot move.