Prevention: Whitelists, Claims and Logging
The easiest way to deal with griefing and stealing is to prevent them before anyone even spawns into the world. A small private or semi-private SMP relies on trust, backed up by a few basic server tools.
- Enable a whitelist: Never leave a community server open to random joins. On Java servers, run
/whitelist on and add approved players with /whitelist add <name> (you can also build batch commands using tools.9minecraft.net). Bedrock Dedicated Server calls this an allowlist, while Minecraft Realms only lets invited friends join. - Screen new recruits: When recruiting through a moderated finder like smp.9minecraft.net, ask applicants to fill in a short application form or join a brief voice interview on your Discord before you whitelist them.
- Install block logging: On a Java or crossplay server, install a logging plugin like CoreProtect before opening the world. It quietly records every block placed or broken and every item taken from or put into a chest, without changing vanilla gameplay.
- Consider land claims: If your group runs a semi-vanilla SMP and wants hard protection, land-claim plugins or datapacks let players lock their bases and chests so others cannot break blocks or open containers unless trusted.
- Take regular backups: If you run a vanilla server or a Realm where plugins are not an option, automatic world backups are your main safety net against major damage.
Investigating Reports Fairly
When a player reports missing diamonds or a blown-up base, resist the urge to accuse anyone in public chat. Jumping to conclusions creates unnecessary drama, especially when the cause turns out to be a wandering creeper or a friend who thought a chest was public.
- Gather the details privately: Ask the player who reported the issue for the exact coordinates, what went missing or broke, and roughly when they last saw everything intact.
- Check the logs in-game: Teleport to the location and turn on your logging tool's inspector mode (in CoreProtect, run
/co i). Left-click or right-click the affected blocks or chests to see the exact username and timestamp for every action. - Look for context: Check surrounding blocks and nearby chests too. Sometimes a player accidentally breaks a block and leaves a sign, or takes items from a chest in a shared shopping district because the price sign fell off.
- Investigating on Realms or plain vanilla: Without logging plugins, check your server console for login times, ask players privately if they were in the area, and inspect the damage carefully before making a decision.
Rolling Back Damage and Restoring Items
Once you confirm that a build was griefed or items were stolen, fix the damage quickly. Leaving a ruined base sitting in the world makes the victim feel ignored and gives the griefer the reaction they wanted.
If you use CoreProtect on a semi-vanilla server, you can undo a specific player's actions in seconds without resetting anyone else's progress:
- Stand near the damaged area and run a rollback command specifying the user, time, and radius, such as
/co rollback u:<name> t:12h r:30. - Preview or check the result to make sure all broken blocks, killed villagers or pets, and stolen chest contents are back where they belong.
- If you made the rollback radius too small or too large, run
/co restore with the same settings to undo it and try again.
On Minecraft Realms or strictly vanilla servers without plugins, you have two choices: restore the entire world from a recent backup if the griefing is widespread, or use operator commands and creative mode to manually rebuild the damaged structure and replace the stolen items for the victim.
Warnings, Temp Bans and Permanent Bans
Not every rule violation deserves the same response. Separating honest mistakes from malicious behavior keeps your moderation consistent and predictable.
- Minor mistakes (Verbal or written warning): A new member harvests a farm without replanting, takes iron from an unmarked starter chest thinking it belongs to the community, or forgets to fill in a creeper hole in the shopping district. Explain the rule privately, ask them to replace the items or fix the hole, and log the warning for your staff.
- Moderate violations (Temporary ban or probation): A player takes a few items from a base chest, triggers a trap that causes someone to lose gear, or keeps breaking a rule after a clear warning. Roll back their actions, issue a temporary ban from the server, and require them to acknowledge the rules before returning.
- Severe griefing (Immediate permanent ban): Someone intentionally burns down a build, lavacasts a base, slaughters a trading hall, or steals stacks of valuables across the server. Ban their account immediately with
/ban <name>, remove them from the whitelist with /whitelist remove <name>, and remove them from your Discord server.
Staying Neutral During Player Drama
Long-running SMP seasons naturally run into social friction—arguments over border lines, shop prices in a Hermitcraft-style shopping district, prank wars that go one step too far, or pvp disputes on a lifesteal or factions server. As the owner or moderator, your job is to enforce the rules fairly, not to take sides with your closest friends.
- Move arguments out of public chat: When two players start arguing in in-game chat or a public Discord channel, step in politely and ask both to pause. Move the discussion to a private ticket or staff channel where everyone can cool down.
- Stick to written rules and evidence: Base your decisions on what your server rules actually say and what the logs show. If two players misunderstood a verbal deal over land or trades, help them reach a compromise and then update your rules so it does not happen again.
- Avoid favoritism: Hold your longtime friends and fellow moderators to the exact same standards as someone who joined from smp.9minecraft.net yesterday. Nothing kills a small SMP faster than a staff group that excuses rule-breaking from their own friend circle.
- Keep safety boundaries clear: Remind everyone to keep general conversations in the group's public channels and never share personal details like real names, ages, schools, or addresses during disputes.
When to Remove a Member for Good
Sometimes a player never breaks a single block illegally, yet still drains the life out of the server. They might constantly bend the rules, complain about every community event, start petty arguments in voice chat, or make new recruits feel unwelcome.
It is time to remove a member when:
- You have already given them a clear warning about their behavior and nothing has changed.
- Other peaceful, active players start logging on less often specifically to avoid playing while that person is online.
- They repeatedly push boundaries, argue with staff over minor requests, or try to turn every disagreement into a server-wide debate.
When you decide to let someone go, handle it quickly and without a public spectacle. Remove them from the whitelist, send a short, polite message explaining that they are no longer a good fit for the group, and remove them from the Discord. You do not need to post a long callout message in announcements—simply let your remaining community enjoy a peaceful world again.
Questions
Can I use CoreProtect on a vanilla-style SMP without ruining the vanilla feel?
Yes. CoreProtect runs on the server side and does not add any non-vanilla items, mobs, or mechanics for regular players. Many Hermitcraft-style and semi-vanilla servers use it quietly in the background purely for staff investigations and rollbacks.
How do I stop griefing on a Minecraft Realm where plugins are not allowed?
On Java or Bedrock Realms, rely on carefully screening players on Discord before sending an invite, and use the built-in automatic backups feature inside the Realm settings. If someone griefs the world, remove their invite and restore the Realm to a backup from just before they joined.
Should I allow pranks on a small community SMP?
Pranks can be fun if you set strict ground rules: no fire, no TNT, no lava, no killing pets or villagers, and never placing a prank that destroys blocks or causes a player to lose their inventory. Make it a rule that the prankster must help clean up afterward.
What should I do if a griefer is right in the middle of destroying spawn?
Run /ban and /whitelist remove immediately so they cannot break anything else. Do not waste time trying to clean up by hand while they are still online; ban them first, then use your rollback plugin or restore your latest world backup.