Playing together
Whitelist, OP, and a server you can trust
Understand who can join, who can use commands, and how to manage Minecraft names without giving every friend operator powers.
Sharing an address is easy. Deciding who can join and what they can change is the part that keeps a small server enjoyable. MineBanish separates whitelist access from operator permissions. They answer two different questions: may this player enter the world, and may this player use administrative commands?
A whitelist is your guest list
The player list contains the Minecraft names allowed to join. On MineBanish, it supports the owner plus up to ten friends. Somebody who knows the server address but is not listed should be refused entry. The list is not the number of people currently online, and it does not give every listed person special powers.
Ask each friend for the name shown by their Minecraft Java profile. Do not enter an email, a MineBanish display name, a Discord handle or a console gamertag. Copy the spelling and capitalization carefully, especially where offline identities are involved. When somebody changes their Minecraft name, revisit the list rather than assuming the old entry will follow them automatically.
OP is a separate responsibility
An operator can use administrative commands supported by the chosen server software and version. Depending on the command, that can change the time, move players or alter the world. OP is useful for looking after a session, but it is not required to build, gather resources or play normally.
For a first world, one operator is usually easier to manage than an entire group of operators. Here is a planning example: Alex manages the server, while Sam and River join as ordinary players. This JSON is a note to explain the choices, not a file to upload or an API request.
{
"owner": "Alex",
"friends": ["Sam", "River"],
"operators": ["Alex"]
}The important line is the operator list. Being in friends does not mean being in operators. Apply those choices through the Players section of MineBanish settings; the service handles the server’s actual identity and permission files.
Edit while the server is stopped
Open the dashboard and stop the server. Wait for the stopped state, then open Settings and find the player controls. Add or remove names and review the OP switches next to them. Save the changes before starting again. Editing a local note without saving the settings does not change access on the running server.
If you remove somebody who was an operator, check both access and permissions. If you invite a new friend, start the server and let that person test joining before the group’s next planned session. They do not need to install the MineBanish app or create a hosting account.
Access, permissions and settings are different
| Control | What it changes | What it does not do |
|---|---|---|
| Whitelist | Which configured player names may join | It does not grant OP |
| OP switch | Administrative command permissions | It does not replace the whitelist |
| PvP setting | Whether players can hurt each other where supported | It does not control who joins |
| Server address | Where friends connect | It is not an account password |
Treat your MineBanish account password as private. Friends join the game through their own Minecraft clients; they do not need your hosting login. Sharing the hosting account also shares the ability to change settings, reset the world or delete the server.
Understand the authentication choice
A whitelist is not a substitute for authentication. In offline-mode environments, a player name alone is not proof that somebody owns a particular Minecraft account. Do not treat a familiar name as a verified identity. Review the account/authentication options available for your server and choose what is appropriate for your group.
MineBanish generates the identities needed by its selected server software. Do not copy a UUID from a random website into a local planning file and expect that to change access. Server and journey changes recreate the world rather than migrating every player’s inventory from a previous world.
When a friend is still refused entry
Check the exact error first. A whitelist refusal points toward the saved name or authentication choice. An incompatible-version error points toward the Minecraft client. A timeout or refused connection can mean the server is stopped, so adding the same name repeatedly will not fix it.
Compare the player’s actual name with the saved list, confirm the settings were saved, and check that the dashboard says the server is running. Use the connection guide if those checks do not explain the problem. A small, accurate guest list and deliberately chosen operators are easier to maintain than giving everyone every permission.
Put it into practice.
Open your server controls, or create your first world when you are ready.
Create server
