Grief Prevention & Land Claim

Guide to Claiming Land
In order to protect your new piece of land you have found you will want to claim some land to mark it as your own and prevent unwanted visitors from building and taking stuff from it. In this Guide to Claiming Land, everything from basic claiming to advanced subdivisions to become a mayor will be covered.

You can only set a claim in the Overworld also knows as the Players World.

What is a Claim?
In essence, a “claim” is a square region of land that is marked in your name on the server, which, by default, other players cannot build, break or pillage within. We use a plugin called GriefPrevention to do this. Claims have some other properties, too. Creeper and Wither explosions, Endermen block moving and TNT will not work by default within claims and even fluids such as water and lava cannot flow from outside to inside a claim.

Claims work on a system of “Claim Blocks”, of which you earn every hour and can purchase more useing /buyclaimblocks anytime ingame . Each square block in a claim you make uses one of your claim blocks. This means that claims can only be of finite size. In-game, claims are visualized by temporary markings of gold and glowstone that are only temporary and cannot be mined.

Creating Claims: There are three methods of creating a claim.

1 – Placing a chest for the first time will create an automatic claim around it.: When you first place down a Chest a 10×10 claim will be automatically setup around it protecting the area. Note that this only works the first time, and the chest cannot be within an existing claim.

2 – Golden Shovel : You can create a claim with a Golden Shovel tool.
Step One: Hold out your golden shovel in your Main Hand and Right-Click on the ground where you want the first corner of your claim to be.
Step Two: While continuing to hold the Golden Shovel in your hand, walk over to the spot you want the second corner of your claim and Right Click it. Note that claims have to be over 100 square blocks in size. (10×10+ or equivalent)

3 -Command: You can use the /claim command to make a claim. Simply type /claim <size of claim> to create a claim. The size you input will be the number of blocks from you to the new border of the claim.

Configuring Claims

Abandoning Claims:
You can do /unclaim or /abandonclaim while standing in a claim to remove it. You will then be given back the claim blocks to use with other claims. In addition, you can use /abandonallclaims to abandon all of your claims and regain all of your claim blocks back for use. You can also abandon all of your claims by typing /abandonclaim or /unclaim while standing outside of a claim.

Viewing Claims:
While holding a stick in your hand, you can right click within a claim to view the claim borders marked in temporary Gold Blocks and Glowstone. Any subclaims within the claim will also appear marked in temporary Iron Blocks and Wool.

You can also view a list of all of your claims and their co-ordinates using the /claimslist command.

Resizing Claims:
Simply right click one of the golden corners of a claim to resize it. If you make the claim larger, you will need to have the right amount of claim blocks to support the expansion.

Claims Explosions:
It’s possible to enable explosions within a claim by standing in it and typing /claimexplosions.

Subdividing Claims:
By Subdividing Claims, you are able to create subclaims within a regular “top-level” claim you made as demonstrated in the “Creating Claims” section. This is useful in particular for creating plots in a town, as you are able to trust people in a subclaim without them being trusted in the larger claim. Unlike regular claims, there’s no size limitations on subclaims and so they can be as small as one block; subclaims do not take up claim blocks.

Apart from that, Subclaims act like regular claims. They are marked out by temporary Iron and Wool blocks. Do note though, that players trusted in the top level claim will retain their permissions inside any subclaims. Only the owner of the main top level claim can create subclaims within it.

Creating Subclaims:
To create subdivisions, you will first need to be standing within the claim you wish to subdivide and type /subdivideclaims
Step One: As with regular claims, to create a subclaim you hold a golden shovel and right click on a spot on the ground to act as the first corner of your claim, but this time the spot must be within your claim
Step Two: Walk over to the spot where your second corner will go, and right click there. Your subclaim will now be marked in temporary Iron Blocks and wool blocks.

Removing Subclaims:
To remove a subclaim, simply stand within one and type /unclaim or /abandonclaim to remove it. If you now wish to remove the main top level claim you can now simply type /AbandonTopLevelClaim to remove everything.

Restricting Subclaims (Advanced):
As mentioned before, players trusted in the top-level claim have the same permissions in any subclaims created within the claim. However, you can restrict subclaims to stop this and specify specific permissions for all players within subclaims. To do this, stand within the subclaim you wish to restrict and type /RestrictSubclaim. Note that only the claim owner can do this.

1 – Make sure to continue holding your shovel when creating, resizing or subdividing a claim. It may come as second nature to stop holding your shovel when moving from corner to corner, but this will reset the process. Your shovel must remain in your hands.
2 – If you have a large claim that you wish to extend in a certain direction, you can simply stand inside the claim and face the direction you wish to extend it by and type /extendclaim <# of blocks>. Of course, you need to make sure you have enough claim blocks to make the extension first.
3 – By standing outside a claim when trusting people, you can add them to all of your claims at once.
4 – If you need any help claiming, be sure to ask a moderator in-game who will be happy to assist you.

Claim Permissions: Trusting People
By default, nobody will be able to build or do anything on your claim. If you want to add someone to a claim, however, there’s a set of tools you can use to do so giving various levels of access.

/accesstrust <player> : Lets the player interact with buttons, levers and doors and set a home with /sethome, but not access containers and chests.

/containertrust <player> : Lets the player use chests and containers, from hoppers and droppers to shulkers and furnaces, as well all permissions from access trust

/buildtrust – Lets the player place and break things inside the claim, as well as all permissions from container and access trust.

/permissiontrust <player> : Lets the player trust other players to the claim. However, this is separate from other trust levels. Players with permission trust can only trust other players to their level of trust (e.g: If a player has container trust and permission trust, then the player is able to give other players container trust but not build Trust). Players with permission trust are not able to give other players permission trust.
On the flip-side, you can remove a player from the trust list using the /untrust <player> command.

Another handy command is /trustlist, which lets players with permission trust and the claim owner view a list of everyone with permissions on a claim.

Finally, the claim owner can add the public to the different permission levels. Replace the <player> on any of the trust commands with the word “public”/”all”/”everyone” to do so. Of course, you can also use /untrust public to remove the public from the different trust levels. Note that the public cannot have permission trust.

* * Players Minecraft added some more useful permissions that all players have access to* *

/setflag NoMonsterSpawns : Disables all monster spawns except for dungeon spawners and spawn eggs (both
of which GriefPrevention limits to players with build permission in land claims). Also removes monsters
which spawn outside the flagged area and then wander in.

/setflag NoMobSpawns : Prevents ALL mobs from spawning (not just monsters) in an area. Same exceptions as
for the NoMonsterSpawns flag above.

/setflag AllowPvP : This is the flag for creating PvP arenas, where players can fight. This flag overrides
GriefPrevention’s PvP protections in land claims where you set it, allowing players who are standing in
an AllowPvP area to damage other players. If you want to also disable PvP in the wilderness (outside of
land claims), you can do that in the GriefPreventionFlags config file (it’s a per-world setting).

/SetFlag EnterMessage and /SetFlag ExitMessage – Sends a message to players when they enter or exit (respectively) a land claim. These messages support formatting codes using the dollar sign ($). Example usage: /SetFlag EnterMessage $1Welcome to %owner%’s house!

/setflag NoPlayerDamage : Prevents ALL damage to players in areas where it’s set. Think about new player
starting areas, non-lethal parkour challenges, and secrets hidden underneath presumably lethal lava

/setflag HealthRegen 5 : HealthRegen – Regenerates the amount of health you specify every 5 seconds for any players in the flagged area. To give you a sense of scale when setting this flag’s regeneration rate, default max player
health is 20.

/setflag NoHunger 5 : NoHunger – Prevents damage from starvation and food level loss for all players inside the flagged area. (Food level may be momentarily lost, but will be restored to its previous value shortly). Optionally, you
may specify an amount of food level to be regenerated per 5 seconds. For example: /SetFlag NoHunger 5
would regenerate 5 food levels per five seconds (max food level is 20).

/setflag NoMobDamage : NoMobDamage – Disables non-player damage to passive mobs and named aggressive mobs. Player damage is already limited by GriefPrevention (/ContainerTrust for animals, /Trust for villagers, but
named monsters are never protected). One use of this flag might be to protect your spawn
animals/villagers from monsters and clever players who might push them into lava, off a cliff, or under a

/setflag NoPetDamage : Cancels ALL damage to pets in flagged areas, even direct damage from their owners. A
“pet” is any tameable entity with an owner, like a dog, cat, or horse for example.

/setflag NoEnter : Requires players to have /AccessTrust or higher permission in a land claim (or the
gpflags.bypass permission node) before they may move into a flagged area. This flag requires an
explanatory message, which will be sent to any rejected player, and is only effective when applied to
land claims (not worlds). Example usage: /SetFlag NoEnter You don’t have the %owner%’s permission to
enter this area.

/SetFlag CommandBlackList : Prevents players from using any commands you list in the flagged area, unless
they have the gpflags.bypass permission. Example usage: /SetFlag CommandBlackList

/SetFlag CommandWhiteList : Prevents players from using any commands except those you list in the
flagged area, unless they have the gpflags.bypass permission. Example usage: /SetFlag CommandWhiteList tell;me;home

/setflag InfiniteArrows : IWhen an arrow lands in an area where this flag is active, the arrow will be sent back to
the firing player’s inventory. This includes arrows which hit live targets like monsters and other players,
and they will still deal damage. This cannot be used to duplicate arrows using an infinity-enchanted
bow. A great option for shooting ranges and combat arenas!

/setflag NoFlight : Prevents players from legitimately flying (this is not a no-cheating flag, see other plugins to
fight hacked clients) in the flagged area. Invincible players will fall when entering the area, while others
will be teleported down to the first non-air block beneath them.

/setflag NoLeafDecay : Prevents leaves in the flagged area from disappearing when the logs holding them up are

/setflag NoLootProtection : Disables GriefPrevention’s player death loot “antitheft” feature in the flagged area,
allowing any player to pick up the items a player drops when he or she dies in that area. Useful for
competitive areas where loot can be a reward, like PvP arenas.

To Remove any of these flags use /unsetserverflag <name>