Before the first player
The list is unglamorous and every item has ended a server when skipped:
- Permissions. LuckPerms groups with sane inheritance from minute one — default, member, vip, staff. Nobody debugs perms well at hour two of a launch.
- Backups. World, plugins, database — on a schedule, with one copy offsite. Tested restore, not assumed restore.
- Grief insurance. CoreProtect in, rollbacks ready. New servers attract the first wave on day one.
- Spawn. Built or mapped, with rules visible, a join hub that doesn't dump players into wilderness, and a Discord link in the MOTD.
The first hour
Be online. The first joins set the tone for everyone who arrives after them — greet, teleport arrivals to spawn instead of letting them fall into a hillside, and watch the console while plugins cold-load: the only errors some plugins ever log appear exactly once, at first join. No tutorial spam, no wall of commands. Presence beats documentation on launch night.
Days one and two
Collect feedback in-game — a feedback command that files to a channel staff actually reads. Fix the loudest complaint within twenty-four hours and post a changelog players can see; nothing proves a server is alive like visible response. Add zero new plugins unless something is broken. Stability is the product this week; features are week three.
And keep the restore plan where you can reach it. The first forty-eight hours are when you'll want it, if the list above got skipped somewhere.
RnK is a Minecraft developer with six years in the game — plugins, server setups and performance work across Paper, Spigot and Folia backends. Three networks run day to day; the rest of the time is client work. The bench is open on Discord.