There are several different commands that allow you to customise the function of your claim. This page details what those commands are and what they do. Using /ps help will provide you with a list of available commands.
For a more general, less in-depth guide of the claiming system, read the Claiming guide.
/ps info lists information about your claim. Here are the things it tells you:
- Location: the location of your claim block.
- Priority: the priority of your claim in comparison to your other claims. See below for more information.
- Type: which ore your claim is, whether that be lapis, coal, redstone or diamond.
- Flags: these are uneditable flags that tell you a little bit of information about your claim.
- Owners: who the claim’s owners are.
- Members: who the claim’s members are.
- Bounds: the bounds of your claim. The two coordinates displayed are the lowest point to the north west and the highest point to the south east.
/ps add [username], /ps remove [username]
/ps add/remove allows you to add or remove a member. When you add a member to your claim, they can do everything you can do in the claim*, although they can’t alter the claim or claim block in any way.
*This can be changed if you edit the claim flags – see below.
/ps addowner [username], /ps removeowner [username]
/ps addowner/removeowner allows you to add or remove a claim owner. You are a claim owner, so when you add someone else as a claim owner they have just as much power over the claim as you do, including being able to add claim members/owners, edit claim flags, or even remove you from claim ownership.
/ps count, /ps count [username]
/ps count tells you how many claims you own. If you add someone’s username after it, you can see how many claims that person has.
/ps list lists the locations of all the claims that you own and are a member of.
/ps flag brings up a list of ‘flags’ that you can change. These flags allow you to customise the function of your claim.
Each flag does something different:
|use||Whether players can use redstone switches such as buttons or pressure plates,
or open doors and trapdoors.
|chest-access||Whether players can access chests, furnaces, hoppers, etc.|
|allow-block-break||Specifies which blocks players can break.|
|allow-block-place||Specifies which blocks players can place.|
|deny-block-break||Specifies which blocks players can’t break.|
|deny-block-place||Specifies which blocks players can’t place.|
|block-break||Whether players can break blocks.|
|block-place||Whether players can place blocks.|
|sleep||Whether players can sleep here.|
|damage-animals||Whether players can damage animals.|
To edit the flags that have ‘Allow Deny’ next to them, you simply click on allow or deny. Then, if you want to specify who is affected, you click ‘[ all ]’ next to it. You can cycle through several options: members, owners, non-members and non-owners.
For the flags that have ‘Edit’ next to them, you must put in a value of which block you want to be affected before you can change who it affects. For example, say you want to allow non-members to break dirt blocks. You click on ‘Edit’, which automatically inputs /ps flag allow-block-break into your text box. Because you want dirt blocks to be broken you would say /ps flag allow-block-break dirt. Then you say /ps flag to bring up the options again, and you click on ‘[ all ]’ until you reach non-members.
It’s possible to input more than one block in the value. When doing this, you simply list the blocks next to each other separated by a comma but no space. So if you’d wanted players to be able to break dirt and oak planks you’d say /ps flag allow-block-break dirt,oak_planks. However, if you want to change the players affected to anyone other than '[ all ]', you have to do this with only one block value before then adding the additional blocks.
The ‘Edit’ flags can be combined with block-break and block-place. If you wanted everyone to be able to break all blocks except for cobblestone, you’d click on ‘Allow’ next to block-break. Then you’d say /ps flag deny-block-break cobblestone.
To reset the ‘Edit’ flags, simply put null in place of a block, e.g. /ps flag deny-block-break null.
/ps rent brings up the list of rent commands.
- /ps rent lease [price] [period] - allows you to set the price and time period of your claim's lease. /ps rent lease 64 1w, for example, would set the lease at a price of 64 ems for 1 week.
- /ps rent stoplease - stops the lease, even if someone is already renting from you.
- /ps rent rent - rents the claim that you're standing in from the claim's owner.
- /ps rent stoprenting - stop renting the claim that you're standing in from the claim's owner.
Use /ps buy to buy the claim that you are standing in, if it's for sale.
/ps sell [price], /ps sell stop
With /ps sell [price] you can set the number of emeralds that your claim will be sold for. /ps sell stop stops the claim from being available to buy.
If you are ever unable to find your claim stone, but it is still protecting an area, it may be hidden. Use /ps unhide to reveal it.
/ps view uses particles to show you the border of your claim.
/ps unclaim returns the claim block to your inventory, unclaiming the area.
/ps priority [number]
/ps priority sets the priority number of your claim. Priority determines which claim takes precedence if you have two overlapping claims. The higher the number, the higher the priority; a claim with priority 2 supersedes a claim with priority 1. Here’s an example:
There are two claims – a redstone claim and a coal claim. These two claims overlap, as shown in this image. The coal blocks show the coal claim’s border, and the redstone blocks show the redstone claim’s border.
The coal claim has the user ‘Steve’ added as a member. Steve is not a member of the redstone claim. There is another player – ‘Alex’. Alex is not a member of either claim. In addition to this, the coal claim has the flag “chest-access” set to “allow” for all. The coal claim has a priority of 3. The redstone claim has a priority of 4. Because the redstone claim has a higher priority, it takes precedence over the coal claim. When Steve tries to break a block in the overlapping area, he can’t. When Alex tries to open the chest in the overlapping area, she can’t.
The claims’ owner comes along and changes the coal’s priority to 5. Now, because the coal claim’s priority is higher than the redstone claim’s, the coal claim takes precedence. This time Steve can break blocks in the overlapping area and Alex can open the chest.
How to Turn Your Claim Into…
There are several common uses for claims, other than just protecting your stuff. Here’s how to do some of them.
When making a hotel, you probably want non-members of your claim to be able to open doors, use pressure plates, and possibly even open chests.
To allow them to open doors, choose ‘Allow’ for the flag ‘use’.
To allow them to access chests, choose ‘Allow’ for the flag ‘chest-access’.
And that’s it! Making a hotel is that easy. Make sure to leave the settings for who the flag affects on ‘[ all ]’, otherwise you’ll have to add players to the claim for them to be able to do anything.
…A Shulker Area
Making a shulker area is a lot more complicated than making a hotel. There are two ways to do it – the first is more secure but requires two claims and limits which colour shulkers can be placed where, and the second doesn’t have this problem but means that players can place nearly any block in that area.
When making a shulker area, you want players to be able to place and break shulkers without breaking any other blocks. The ideal way to do that would be to do /ps flag allow-block-place shulker_box and /ps flag allow-block-break shulker_box. Unfortunately, each colour shulker box has its own ID so they all have to be typed out, and when they’re all in one string it’s too long for the chat text box. This means that you can’t allow all the shulker boxes to be placed/broken in one claim and must use two instead.
Here’s how to do it:
(These strings are quite long, so feel free to copy and paste them from here into your game.)
In the first claim, input /ps flag allow-block-place shulker_box,brown_shulker_box,red_shulker_box,orange_shulker_box,yellow_shulker_box,lime_shulker_box,green_shulker_box,cyan_shulker_box,light_blue_shulker_box
And also /ps flag allow-block-break shulker_box,brown_shulker_box,red_shulker_box,orange_shulker_box,yellow_shulker_box,lime_shulker_box,green_shulker_box,cyan_shulker_box,light_blue_shulker_box
This first claim will now allow brown, red, orange, yellow, lime, green, cyan, light blue and undyed shulker boxes to be placed and broken.
In the second claim, input /ps flag allow-block-place shulker_box,blue_shulker_box,purple_shulker_box,magenta_shulker_box,pink_shulker_box,white_shulker_box,light_gray_shulker_box,dark_gray_shulker_box,black_shulker_box
And also /ps flag allow-block-break shulker_box,blue_shulker_box,purple_shulker_box,magenta_shulker_box,pink_shulker_box,white_shulker_box,light_gray_shulker_box,dark_gray_shulker_box,black_shulker_box
This second claim will now allow blue, purple, magenta, pink, white, light grey, grey, black, and undyed shulker boxes to be placed and broken in it.
Next, so that players can open their shulkers, choose ‘Allow’ for the flag ‘chest-access’ in both claims.
That’s it. Now players can break and place shulker boxes in these two claims. If these claims are inside a larger claim, make sure that they have a higher priority than it.
For this method, players are prevented from breaking or placing any of the blocks that make up the shulker area, but they can break or place any other blocks. It is for this reason that this method is less secure. If you use this method to create a shulker area and someone abuses it, don’t hesitate to report it to a member of staff.
Here is an example shulker area:
The blocks that were used to build this area are iron blocks, packed ice, smooth quartz stairs, quartz blocks, quartz pillars, an end rod, and a birch sign.
The first step is to choose ‘Allow’ for the flags ‘block-break’ and ‘block-place’. This allows players to break and place blocks within your claim. Next, choose ‘Allow’ for the flag ‘chest-access’ to allow players to open their shulkers once they’ve placed them.
To prevent players from breaking the blocks that make up the shulker area, the command /ps deny_block_break must be used. For the example shulker area, the full command used would be /ps deny_block_break iron_block,packed_ice,smooth_quartz_stairs,quartz_block,quartz_pillar,end_rod,birch_sign. For your shulker area, replace the blocks listed here with the blocks that you used; the fewer blocks used to build the area, the easier it will be. If you use too many blocks, the string will become too long and this method won’t work correctly.
So that players don’t accidentally place any blocks that they can’t break, use the command /ps deny_block_place and input the same blocks that you used for /ps deny_block_break. You might also want to deny the placement of some other blocks; TNT for example.
Next, click on ‘[ all ]’ next to ‘deny_block_break’ and ‘deny_block_place’ until you reach non-owners. This means that you won’t be affected by these flags, although members of your claim will be.