25 Minecraft server owner tips from watching 2,500 live servers

Most owner tips are the same list of plugins in a different order. These are not. We ping every server listed here at least every five minutes, keep the history, and read the reports and the support inbox, so each tip below is either something the numbers say or something we watch go wrong every week. Twenty-five of them, each a short paragraph, grouped into the listing, uptime and hours, people, and money and risk.

Where a tip has a whole guide behind it, it links there instead of repeating it. The numbers are from the roughly 2,500 servers that were online on our list when we pulled them; the full set is on the statistics page. Every one is a correlation, and every one is free to act on.

Your listing and your numbers

• 1. Slots are not players, and big slot counts make you look empty. The median server on our list is 5% full. Servers with 20 or fewer slots have a median of 2 players online; 21 to 100 slots, 5; 101 to 500, 15; 501 to 2,000, 49; and above 2,000 it drops back to 44. Busy servers raise their limit, not the other way round. "4/500" reads as abandoned; "4/30" reads as a small community. Set max-players to a number you could actually fill on a good night.
• 2. Use both MOTD lines. Java shows two lines under your name and most servers waste the second one. Line one says what the server is, line two says why to join now (a new season, an event, crossplay). The MOTD guide has the syntax.
• 3. Tag every mode you run. 48% of servers list one mode or none. Servers listing four or more have a typical count of 37 players against 10 for the rest. Do not invent modes, but if you have a KitPvP arena on your survival server, say so; that is where players filter.
• 4. A Discord link is worth more than a website, but only if it is alive. 20% of listings have a Discord and their median is 48 players against 10 without. A dead invite is worse than none. Our Discord guide keeps it small enough to stay alive.
• 5. Write 250 characters of description. Only 15% of servers do; their median is 20 players against 11. It is also 2.5 of the 12 points on our strength meter, the biggest single item.
• 6. Use a real subdomain, not a raw IP. 47% of online addresses start with play., mc., join. or hub., 32 sit on a free host's subdomain, and none of the online servers use a bare IP. An address players can remember is a five-minute DNS job; see the domain guide.
• 7. Treat the strength meter as a checklist. Median listing strength here is 3.5 out of 12, and 59% of listings are under 4. When we checked in late September 2026, almost nobody had reached 8, which is the bar for a Rising spot on page one (claimed listings only, and only while the server is growing). It is the cheapest ranking gain on the site: how we rank lists every item and its points.

Uptime, hours and honest counts

• 8. Answer every ping. Offline servers always sort below online ones and drop out of the Rising and ad spots, and an outage during your peak hour loses the players who tried right then. A home PC that sleeps is not a host.
• 9. Know your peak hour and be there. Your listing's 7-day chart shows it. Events go just before it, staff are online during it, and maintenance happens as far from it as possible. 12 of our 100 Server Score points are for busy hours, not averages.
• 10. Update within days of a release. "Outdated server" is the second most common reason a player leaves before joining. Run ViaVersion for a range and state the range on the listing.
• 11. "Server empty for 60 seconds, pausing" is a setting. It is pause-when-empty-seconds in server.properties, default 60, a vanilla feature since 1.21.2 (see the wiki). It is not why your server is empty; this is.
• 12. Never fake the count. About 3% of online servers (70 when we last counted) carry a count flag: a cosmetic maximum, a number that never moves, a count above the maximum. Flagged servers lose the spotlight and Rising spots and sort below honest ones. Players check anyway, and a fake 40 with 2 in chat is worse than an honest 2.
• 13. Open a Bedrock port if you run Java. 31% of Java servers answer a Bedrock ping and their median is 26 players against 6. Geyser on UDP 19132, then our probe adds you to the crossplay list automatically. The crossplay guide takes an evening.

People: staff, players and you

• 14. Hire from your regulars, on a trial. A helper with chat tools only, for two to four weeks, promoted by track. Applications from strangers who list five other servers they staff are the ones that go wrong. The staff guide has the template.
• 15. Say no to players, with a reason, within a week. The suggestion channel is where communities are lost. Every idea gets an answer; most of the answers should be no. A new mode for one loud player, a rule change mid-season for three, a plugin because a bigger server has it: no. "No, because it would split the 15 people online into two rooms" is respected. Silence is not.
• 16. Do not confuse Discord members with players. 200 members and 4 online is not a community; 20 regulars with no Discord is. Count the people who log in, and build for them. Our community guide is about those twenty.
• 17. Warn in private, praise in public, and hold friends to a stricter standard. A public argument at spawn between staff and a player costs more than a week of griefing. A rank for the co-owner's friend costs more than that.
• 18. Play. The owner in the count, building, is the best retention tool a small server has. Owners who only appear to ban people run servers that feel policed.
• 19. Schedule your own absence. Post the dates of a week off and hand one thing over completely. Servers rarely die of a cause; they die because the person holding them up stopped without saying so. If that is already happening, read reviving a dying server before you do anything drastic.

Money and risk

• 20. Know your monthly number and what covers it. Hosting, the domain, any paid plugins, divided by the players you actually have. If the store would need to sell to a third of your players every month to break even, the server is a hobby with a budget, which is fine; plan it as one and do not spend on promotion to close the gap.
• 21. Read the EULA before you build the store. Mojang's usage guidelines limit what a server can sell: no competitive advantage, no capes, no cash-out currency. Owners find this out from a chargeback or a takedown. The EULA guide lists what is allowed.
• 22. Back up three ways and test one restore. Automatic backups on the host, a copy off the host, and a copy you made by hand before any reset or plugin change. A backup you have never restored is a hope. The backup guide has a script.
• 23. Never wipe a purchase. In a reset, a merge, a rename, a rank rework: whatever a player paid for survives. It is the one line in any change that turns a veteran into a one-star review, and the season guide lists what to keep.
• 24. Do not buy votes, and do not swap them. Staff here can take up to 10 Server Score points off a server caught buying votes or faking counts, and the change is logged. Ten points is pages, not places. Real votes, connected through NuVotifier to a reward, are 15 points for nothing.
• 25. Spend on promotion last. Paid spots multiply what your server does to new players. Until the ten-minute test passes and the day-7 returns hold, an ad is a faster way to find out that they leave. When they stay, our advertise page says exactly where a spot shows and what happens if you go offline.

Most of this list is done from your listing's edit page. If the server is not on here yet, add it; if it is, claim it from its server page and go down the strength meter until it reads 8. That is tips 2 through 7 in one sitting.

Quick questions