plurra plurra

Whitelist and OP: who gets onto your Minecraft server

Your address is shared in the group chat in seconds and passed on just as fast. With the whitelist, only the people you add get in. With OP rights, you hand commands to a few people you trust. Both work through the console in the dashboard.

Start a server

Inviting friends

There is nothing to set up for that. Copy the address from the dashboard, it looks like your-name.play.plurra.de. Your friends add it in Minecraft under Multiplayer → Add Server. They need the same Minecraft version as the server, which the dashboard shows.

As long as the whitelist is off, anyone who knows the address gets in. A server gets found even if you never share the address: there are programs that constantly scan for open Minecraft servers. For a private group, the whitelist is the first setting to turn on.

Whitelist in four steps

  1. Open the console

    The console is right at the front of the dashboard. The server has to be running. Type commands there without a slash in front.

  2. Add yourself

    whitelist add YourName and Enter. You first, or you lock yourself out too.

  3. Add your friends

    whitelist add Name for everyone who should play. What counts is the Minecraft account name, not the Discord one.

  4. Switch it on

    whitelist on. From now on only listed players get in. That stays after a restart.

The commands at a glance

  • whitelist add Name and whitelist remove Name: add or remove someone.
  • whitelist list: who is on it right now.
  • whitelist on and whitelist off: enforce the list or turn it off.
  • whitelist reload: reads the list again after you edited whitelist.json by hand.
  • With enforce-whitelist=true in server.properties, a reload also kicks players who are online but no longer on the list.

OP rights: who can use commands

op Name makes someone an operator. They can then use commands in game: change game mode, set the time, teleport, kick and ban players. deop Name takes it away again.

Only give OP to people you trust with the world. An operator with full rights can wreck everything you built, make others operators and stop the server.

How far the rights go is set by op-permission-level in server.properties. 4 is everything and the default. With 2, the usual gameplay commands stay, kicking, banning and giving OP go away. For finer control on Paper there are permission plugins like LuckPerms, see Installing plugins for how to add one.

Kicking and banning

  • kick Name: throws someone out, they can come straight back.
  • ban Name reason: bans for good. pardon Name lifts it, banlist shows all bans.
  • With a whitelist you rarely need a ban: removing someone and kicking them is enough.

Friends on phones or consoles

With crossplay on, Bedrock players come in through the Floodgate plugin. whitelist add doesn’t work for them, because they have no Java account. Floodgate brings its own command for that: fwhitelist add Gamertag. On the server, Bedrock players show up with a dot in front of their name, which is how Floodgate keeps them apart from Java names. We haven’t tested this with a real Bedrock device yet.

Questions

Why does the server say I’m not on the whitelist?
The whitelist is on and your name is missing. Whoever has the dashboard adds you with whitelist add.
Can my friends start the server?
No. Start, stop and the console in the dashboard belong to your account only. An operator with full rights can stop the server in game with stop, then you have to start it again.
Does a friend joining count against the 30-day deletion?
Yes. Any real player connecting counts, not just you.
How many people fit on the server?
With 2 GB of RAM, eight to ten at once on Paper with light plugins is realistic.

Bring your people in.

Create a server, share the address, turn on the whitelist.

Start a server