Plugin:Bolt

Bolt
Server	Protection plugin  —  on Prism Party
Main command	/bolt
Sub commands	10
Access
Requirements	Plugin:Levels 1
Custom	No

Players are required to be at least Level 1 in order to access these features.

Bolt is a single-block and entity protection plugin used on some servers within the Prism Party Network. Bolt automatically protects most blocks placed by players with level 1. Similar to how Plugin:Claims allows players to create and manage land claims, Bolt enables players to manage their individual block protections to modify behaviors, trust other users, and manage access.

When blocks protected with Bolt are located on GriefDefender claims, the land claim protection settings always take priority. Players and staff should be mindful of which system is managing access for a given block, and adjust the protection(s) accordingly. As is the case with land claims, Bolt protections expire after 120 days of inactivity^{[See notes]}.

Bolt is a core plugin on Prism Party. Generally speaking, this means that the network can't update unless this plugin is also updated and working. Bugs impacting this plugin are considered severe.

Features

• Protects both blocks and entities
• Allows locking of almost any block
• Set different protection modes
• Trust users or groups on existing blocks
• Set blocks to require password for access

Configuring protections

Protection types

Protections types determine how other players should be allowed to interact with a locked container.

Private

The default mode for most blocks. Only the owner and trusted members can interact with the block.

Display

The default mode for signs and lecterns. Only the owner and trusted members can interact, but all players can view contents.

Deposit

The default mode for composters. All players can add items, but only the owner and trusted members can take items and interact.

Withdrawal

All players can remove items, but only the owner and trusted members can add items and interact. Useful for farm outputs.

Public

The default mode for enderchests. All players can interact, but only the owner and trusted members can break the block.

Access types

There are only two access types on Prism Party. Most protections will use the normal access type, while doors, trapdoors, and gates can optionally be assigned the autoclose access type.

Normal

The default access type for all protections.

Autoclose

Useful only for doors, trapdoors, and gates. Otherwise identical to the "normal" access type, this access type automatically closes doors and gates that have been opened by a player after 3 seconds. Useful for public builds where you want to enforce that a door or gate remains closed after use.

Source types

Source types determine who is allowed to access a protected container. For example, if the source type is set to "Player", then the specified players will be allowed to open the container.

Player

The default source type for all protections. Only players who have been trusted via /bolt edit can access the protection.

Password

All players who know the password have access to the protection, even if they were not explicitly trusted. The password can be given to a protection via /bolt password <password>, thus unlocking it for that user if the input is correct.

Permission

All players who possess a particular permission have automatic access to the protection, even if they were not explicitly trusted. This protection type is similar to password, but all players who are a part of a specified Rank or Level will have access to the protection. Other permissions can be specified if they are known to the user creating the protection. Please note that players are not able to modify the permission nodes of other users.

View all public permissions

• prism.rank.all - Targets all players. Effectively the same as making a protection public
• prism.rank.generic.player - Targets all players except staff. This is effectively the same as the previous permission since staff have access to all protections anyway
• prism.rank.generic.staff - Targets only staff members
• prism.rank.generic.donor - Targets all players who have a donor rank
• prism.rank.pebble - Targets only players with the pebble rank
• prism.rank.<rank> - Targets only players with the specified rank. The rank name must be in lowercase
• group.1 - Targets only players who are at least /level 1

Group

All players who are part of a group created via the /bolt group command have access to this chest. This is similar to the default "player" source type, except all players who are part of the specified group gain access automatically and do not need to be added to the individual protection manually via /bolt edit. This source type is useful when you have multiple protections that you wish to provide multiple players with access to, as it removes the need to type multiple commands per container.

Commands

[Square brackets] indicate optional parameters, while <angle brackets> indicate required parameters.

Lock

/bolt lock [mode]

Lock something, preventing access to untrusted players. Optionally provide a protection mode to lock with. If a mode isn't specified, defaults to Private.

Unlock

/bolt unlock

Unlock something, removing all protections.

Edit

/bolt edit <add|remove> <player>

Edit a protection to add or remove another player's access.

Modify

/bolt modify <add|remove> <access type> <source type> <sources>

Add or remove sources with given access to a protection's access list.

Access types

The access type dictates how the protection should interact with trusted players.

Sources

The actual sources to use, based on the specified source type. For example, if the source type is "player", then this parameter should be the username of a player.

Group

/bolt group <create|delete|add|remove|list> <group name/usernames> [player names]

Create and manage custom player groups which can then be applied to protections using the group sources type. When specifying multiple usernames to add or remove from a group, separate the usernames with a space.

Trust

/bolt trust <add|remove> <source type> <sources> [access type]

View or modify your global trust list. Players with access to the specified source type will be able to access all of your protected containers globally. This setting applies immediately across all protections, thus removing the need to manually modify all protections if you wish to allow access across a large array of protections.

Run /bolt trust to view your trust list.

Transfer

/bolt transfer <player name>

Transfer ownership of a single protection to another user. The original settings of that protection are retained, meaning that unless you added yourself to the container using /bolt edit you will no longer be able to open it once transferred.

Password

/bolt password <password>

Enter a password for a protection that has a password source added. This command is not used to create password-protected containers, but is instead used to open a password-protected container owned by another player.

To create a password-protected container, use /bolt modify add normal password <password> instead.

Mode

/bolt mode <mode>

Toggle on or off a player mode. Player mode toggles modify how the Bolt plugin interacts with your actions.

Player modes

nolock

Toggle whether or not containers should be automatically protected when placed.

nospam

Toggle whether or not protection alerts should be shown in the actionbar.

persist

Toggle whether modifications from /bolt modify and /bolt edit should apply only to a single clicked container, or apply to every container that is clicked with until disabled. This setting prevents you from needing to type the same command multiple times to modify an array of containers.

Info

/bolt info

View information about a protection, such as the protection type and access list.

Examples

Bulk-edit multiple containers

/bolt mode persist then type your desired command and click each container.

Allow players to see the contents of a chest, but not add or remove items

/bolt lock display

Trust multiple people on some containers

1. First create a group using /bolt group create <group name>. The name of your group cannot already be in use by another player.
2. Once the group is created, add users to it with /bolt group add <usernames>. You can add multiple names at once, separated by a space.
3. Run /bolt modify add normal group <group name> and click the block to apply the change. Now, all users within the created group will have access to the container. Users can be added or removed from the group at any time.

Trust someone across all of your containers

1. Run /bolt trust add player <username>. Any players you trust will have access to all your protections globally.

You can view users or sources you have trusted with /bolt trust.

Trust everyone who is at least /Level 1 on a container

1. Run /bolt modify add normal permission group.1. Any players who inherit the specified group/permission have automatic access to the container.

Create a password-protected container

1. On the container you would like to lock with a password, run Template:Cmd.
2. Click the block to apply the change. From here on, all players who know the password can open the container by first running /bolt password <password> until they log out.

Make a door automatically close after opening

1. Doors, gates, and trapdoors can be set to automatically close after 3 seconds. Autoclose must be manually activated per user in most cases but since most doors are automatically protected, this is often redundant.
2. Set it so that all users are able to access autoclose for the door by running /bolt modify add autoclose permission prism.rank.all. Even though all users have access to auto-close on the door, only those who have been given access to open the door will be able to actually use it.
3. You can now optionally add other users to access the door via /bolt edit add <name> or change the protection type (such as making it public) with /bolt lock <type>.

Notes

• Group names must be unique. If a group named "Friends" already exists for another user, you will not be able to name your group that.
• Block protections are set to expire 120 days after the protected block was last interacted with. This differs from the expiry behavior of land claims, which only expire after 120 days of player inactivity.
  • This means that active players may still lose protections on blocks they have not interacted with for prolonged periods of time.
• Redstone features are automatically enabled for all protected blocks, unnecessitating the use of commands like /chopper on.
• Land claims permissions override chest access. In order to give a player access to a container within a claim, that player must be trusted in both the claim and on the container.