Got a question that the wiki doesn't answer? Ask on the forum (preferred), or join us on IRC.

BeastNode
About the ads

CommandBook/Item permissions

From EngineHub.org Wiki
Jump to: navigation, search

There are several ways that you can set up permissions for /item or /give.

Contents

Permissions

No restrictions

For no restrictions on /item or /give, you do not have to do anything.

Global whitelist

You can set a whitelist of items that everyone is able to spawn with /item or /give. Items that are not on the whitelist cannot be spawned. This affects everyone and you cannot make it per-group. However, you can give certain players the commandbook.override.any-item permission that allows them to override the whitelist. The whitelist is controlled inside the configuration file using the following:

allowed-items: [1,4,12,3]

Notice how 4 item types are listed with IDs 1, 4, 12, and 3.

Warning: You cannot use item names here.

Global blacklist

You can set a blacklist so that items on this list cannot be spawned by anyone except for users with the commandbook.override.any-item permission. Users can spawn any item that is not on the blacklist. The blacklist is controlled inside the configuration file using the following:

disallowed-items: [1,4,12,3]

Notice how 4 item types are listed with IDs 1, 4, 12, and 3.

Warning: You cannot use item names here.

Per-item permissions

You can go all out and assign permissions for all items. (Note, the commandbook.override.any-item permission still overrides everything.) First, you need to enable item-permissions-only in the configuration file. The two relevant permissions then are:

  • commandbook.items
  • commandbook.items.# (Where # is the item ID number.)

For example, you can give the commandbook.items permissions to everyone, but also deny the commandbook.items.5 permissions to prevent the spawning of wood.

Warning: You cannot use item names here.


Namespaces

Variants
Actions