Example Uses

From ServerSigns
Jump to: navigation, search

This page is intended to serve as an example of the various ways in which ServerSigns can be used to achieve a large array of different tasks on a Minecraft Server.

Restrict access to a chest (or other blocks which can be used/opened)

Purpose

Useful if an administrator wants to limit who can interact with a certain block, or add a cost to using the block.

Example 1 - Required Permission Restriction

Actions

  1. /svs create
  2. right click the desired block
  3. /svs setpermissions lockedChest m:&7&oThis chest is locked!
  4. right click the ServerSign
  5. /svs setcancel fail_only
  6. right click the ServerSign

Result

The created ServerSign will only work for players who do have the permission node "serversigns.use.lockedChest" - if they don't have enough permission, they'll be sent the message "&7&oThis chest is locked!". By setting the "cancel mode" to "fail_only" we instruct the ServerSign to only cancel the interaction event if the player fails to execute the ServerSign (i.e. they don't have enough permissions in this case) - it's the interaction event that controls whether a chest, door, or other interact-able block is used!

Example 2 - 'Must Not Have Permission' Restriction

Actions

  1. /svs create
  2. right click the desired block
  3. /svs cancelpermission chest.access.blocker m:&7&oYou cannot use this chest!
  4. right click the ServerSign
  5. /svs setcancel fail_only
  6. right click the ServerSign

Result

The created ServerSign will only work for players who do not have the permission node "chest.access.blocker" - if they do have the permission node, they'll be sent the message "&7&oYou cannot use this chest!". By setting the "cancel mode" to "fail_only" we instruct the ServerSign to only cancel the interaction event if the player fails to execute the ServerSign (i.e. they don't have enough permissions in this case) - it's the interaction event that controls whether a chest, door, or other interact-able block is used!