What's new
Claims & permissions

How to protect your Minecraft base and manage claim permissions

A claim protects only what the installed system and its settings cover. Start by identifying that system, then test the permissions rather than trusting a label.

3 min readUpdated

Claim the right area, verify it with an untrusted player and give teammates only the access they need. Protection is not a backup or a universal guarantee.

Before you start

  • Confirm the world allows permanent building and is not a resettable resource world.
  • Find the server’s official claim or plot tutorial.
  • Keep valuables out of the area until protection has been checked.

Follow these steps

  1. Identify the actual protection system

    The server may use GriefPrevention, towns, plots, region permissions or custom tools. Ask how to create land protection, how much land you can own and whether inactivity or unpaid upkeep can remove it. Do not assume a shovel or command from another server works here.

  2. Confirm boundaries and what is covered

    Check the full footprint of the house, storage and farms, including vertical or world-specific limits. Ask about explosions, liquids, fire, animals and machines. Protections can differ between worlds and servers.

  3. Test before storing important items

    With a consenting player who has no access, try harmless tests of placing a block and opening an empty container. A test of one action does not verify every hazard. Fix gaps before moving your supplies.

  4. Grant the smallest useful permission

    A visitor may need a door, not chest access or building rights. Use the installed system’s permission tiers. Re-check the selected claim and exact nickname before adding someone; do not give people authority to delegate permissions unless necessary.

  5. Review access and keep evidence

    Remove former teammates and check shared storage regularly. If something is damaged, preserve coordinates, timestamps and screenshots, then report through the server’s staff channel. Ask about restoration policy rather than promising a rollback.

GriefPrevention permission examples

Only for servers using GriefPrevention. Permissions and server settings can restrict these commands.

GriefPrevention permission examples
CommandTypical accessUse with care
/AccessTrust PlayerNameAccess to buttons, levers and beds.Access to entrances may still matter.
/ContainerTrust PlayerNameContainer access and additional interactions.This is broader than access-only permission.
/Trust PlayerNameEditing in the claim.Give only to trusted builders.
/TrustListList permissions in the claim.Review the claim you are standing in.
/UnTrust PlayerNameRemove a player’s claim permission.Check other claims and shared systems separately.

Common mistakes to avoid

Confusing a home, bed or chest lock with a claim

Travel and storage features may leave walls, animals or the surrounding land unprotected.

Claiming only the inside of a house

Exterior farms, roof extensions and redstone may sit outside the protected area. Check boundaries after expanding.

Common questions

Does a claim stop every possible kind of griefing?

No universal guarantee applies. Coverage depends on the plugin, its settings, the world and interactions with other plugins. Rules and staff support remain important.

Can I protect land on an anarchy server?

Only if that server provides a protection system. If griefing is allowed, do not expect staff to restore a base.

Should I give full trust to everyone in my team?

Not by default. Give the minimum access needed, review it periodically and make shared ownership expectations clear.

Official references

For the game or plugin described above. Your server’s rules and configuration take precedence for its custom features.

Still can’t get into the game? Read connection help. Questions about your server’s settings? Ask its staff through the official support channel.