ES
DEMinecraft Whitelist and Permissions Before Inviting Friends
A server can be online and still not be ready for friends. If anyone can join, or if half the group has operator access, the first session can turn into cleanup instead of playtime.
Separate two jobs before sharing the IP: the whitelist decides who can join, and permissions decide what those players can do.
Quick whitelist setup
On Java servers, the basic commands are:
/whitelist onto enable the whitelist./whitelist add PlayerNameto allow a player./whitelist remove PlayerNameto remove access./whitelist listto check who is allowed.
Test this with one friend before announcing the server. If the whitelist is wrong, it is better to find out with one person than with everyone waiting in voice chat.
Do not use OP as your permission system
Operator access is not a role system. It gives broad control over game mode, teleporting, items, bans, and server commands. For a private server, keep OP limited to one or two trusted admins.
If you use plugins, create simple roles instead: player, moderator, admin. LuckPerms is built for this kind of setup. Give each role only the commands it actually needs, and avoid solving every problem by making someone OP.
What to check before launch
If you edit server.properties, confirm the whitelist setting is enabled. Review spawn protection, PVP, game mode, difficulty, and the message you will send to the group. Include version, address, rules, and what to do if someone cannot join.
If you are still preparing the whole server, use the server checklist before inviting friends. For base settings, read the server.properties guide.
On Mineando
Mineando lets you prepare the server, test access, stop when you are done, and adjust permissions before the real session. A good first night is boring administratively: friends join, rules are clear, and nobody has more power than they need.
