Managing your Minecraft whitelist, ops list and bans is far quicker from the Player Manager in the LPV5 panel than from the console. It shows who is online live, reads your whitelist, ops and ban lists, and turns each of these actions, kick, ban, pardon, op, deop and whitelist add or remove, into a single click. (The panel also includes deeper tools such as teleport, gamemode, broadcast, freeze and an inventory editor, but this guide focuses on whitelist, ops and bans.) Behind the scenes it sends the matching console command, so you do not need to configure RCON. It resolves usernames to UUIDs through Mojang, shows player avatars, and keeps an audit log of who did what. This guide covers each action, and the main thing to remember is that the live online-player list and the kick action need the server running, while ban/op/whitelist changes also work on a stopped server via on-disk edits.
What the Player Manager Does
The Player Manager is your moderation hub. It shows the players currently online, read live from the server console, alongside your whitelist, ops and bans. It reads those lists straight from whitelist.json, ops.json and banned-players.json, so what you see in the panel matches what the server enforces. Every moderation action you take is sent to the server as a console command, which means there is no RCON for you to set up or maintain.
Note: Loafhosts runs Java Edition servers, so the lists map directly to the standard whitelist.json, ops.json and banned-players.json files
Note: Actions are delivered as console commands, so RCON configuration is not required on your part
See Who Is Online
At the top of the Player Manager you get a live list of online players, parsed from the console. Each player shows their avatar, which makes it easy to pick the right person when two usernames look similar. From this list you can act on anyone connected right now, which is exactly what you want when something is happening on the server and you need to respond fast.
- Sign in to LoafHub at hub.loafhosts.com
- Open your Minecraft server and open the Player Manager
- Check that the server is running so the online list populates
- Find the player you want in the online list
- Use the action buttons next to their name
Tip: Avatars make moderation faster during an incident, since you can match the face to the report
Tip: Keep the Player Manager open during events so you can react the moment something goes wrong
Manage the Whitelist
The whitelist controls who is allowed to join, and the Player Manager lets you add or remove players from it without editing JSON by hand. Adding a player resolves their username to a UUID through Mojang and writes the entry for you, which avoids the classic mistake of whitelisting a misspelled name that never actually lets the right person in. The underlying command is shown below for reference, but you only need to click.
| Command | Description | Example |
|---|---|---|
whitelist add | Add a player to the whitelist | whitelist add Notch |
whitelist remove | Remove a player from the whitelist | whitelist remove Notch |
Tip: Resolving names to UUIDs means a player who later changes their username stays whitelisted
Tip: If you want the whitelist enforced, make sure white-list is enabled in server.properties via the Config Editor
Grant and Remove Operator Status
Operators have elevated permissions, so the Player Manager handles op and deop as deliberate, one-click actions. Granting op adds the player to ops.json and gives them command access; removing it takes that access away. Because the action runs as a console command, it applies immediately on the running server rather than waiting for a restart.
| Command | Description | Example |
|---|---|---|
op | Grant operator status to a player | op Notch |
deop | Remove operator status from a player | deop Notch |
Warning: Operator status is powerful, so only op people you trust, and deop them when they no longer need it
Kick, Ban and Pardon Players
For enforcement you have kick, ban and pardon. A kick disconnects a player immediately without stopping them from rejoining, which is useful for a quick warning. A ban blocks them and records the entry in banned-players.json, and a pardon lifts that ban. All three are single clicks in the panel and run as console commands, so there is nothing to type and no syntax to get wrong.
| Command | Description | Example |
|---|---|---|
kick | Disconnect a player without banning them | kick Notch |
ban | Ban a player from the server | ban Notch |
pardon | Lift a ban on a player | pardon Notch |
Tip: Use kick as a first-step warning and reserve ban for repeat or serious offences
Tip: To reverse a ban, use pardon on the player from the bans tab rather than editing the file
UUID Resolution and the Audit Log
Two features make the Player Manager trustworthy for a team. First, usernames are resolved to UUIDs via Mojang, which is what keeps whitelist and ban entries tied to the real account even if a name changes. Second, every action is audit-logged, so you have a record of who kicked, banned or opped whom. That log is invaluable when you run a server with multiple admins and need to understand a decision after the fact.
Warning: On an offline-mode server, Mojang may not be able to resolve UUIDs, so name-based actions can behave differently than on an online-mode server
Note: The audit log gives a shared admin team accountability without anyone needing console access
Note: UUID resolution is why a renamed player keeps their whitelist and ban status intact
Why Actions Need the Server Running
Here is the key requirement: kick is the only action that requires the server running, since it only affects a live session. op/deop, ban/pardon and whitelist add or remove still work when the server is stopped, because the panel writes the change directly into ops.json, banned-players.json or whitelist.json on disk, and the server applies it the next time it starts. Note that adding a player offline (op, ban, or whitelist add) needs Mojang to resolve the name to a UUID, so only valid paid Java accounts can be staged this way. If the online list is empty and your buttons do nothing, the first thing to check is whether the server is actually up.
- Open the Console tab and confirm the server is running
- If it is stopped, start it and wait for it to finish loading
- Return to the Player Manager
- Confirm the online list has populated
- Take your moderation action
Warning: If the server is offline, kick cannot be delivered because there is no live session. op/deop, ban/pardon and whitelist changes are still applied by editing the on-disk JSON files and take effect on next start
Frequently Asked Questions
How do I add a player to my Minecraft whitelist?
Open the Player Manager in the LPV5 panel, go to the whitelist tab, and add the player by name. On a running server the panel issues the whitelist command and the server resolves the name to a UUID; if the server is stopped the panel resolves the UUID via Mojang itself and writes the whitelist.json entry. Either way, no manual file editing is needed.
Does the player manager need RCON?
No. Actions are sent as standard console commands, so there is no RCON for you to configure. You just click kick, ban, op or whitelist and the panel delivers the command.
Why are my moderation actions not working?
kick needs the server running. If op, ban or whitelist add fails while the server is stopped, it is usually because the username could not be resolved to a Mojang UUID (check spelling, only paid Java accounts resolve). Removals such as deop, pardon and whitelist remove work offline without a Mojang lookup. Start the server from the Console tab if you need to kick a live player.
Can I op and deop players from the panel?
Yes. The Player Manager grants and removes operator status with one click using the op and deop commands, and because they run on the live console the change applies immediately.
How does the player manager handle username changes?
It resolves usernames to UUIDs via Mojang, so whitelist and ban entries stay tied to the underlying account even if the player later changes their username.
Does it work on offline-mode servers?
It still sends console commands, but on an offline-mode server Mojang may not resolve UUIDs, so name-based actions can behave differently than on an online-mode server.