Ban Entry Structure
Every ban entry has a structure consisting of Criterias, Actions and Triggers
A ban entry may have multiple criterias that will be matched against when checking a block or item. Every criteria has to match for a ban entry to fit.
Match the item id (e.g.
Blocks without a corresponding item can't be matched
|Match the item meta or damage.
the world name where the entry should apply.
The id is also allowed
Matches the item's NBT tag. For blocks it matches to the tile entity's NBT.
For blocks without tile entity this criteria will be ignored.
The playername of the player for which the the entry should be valid
The modID the item will be matched against. The modID is the first part of the item's resource location (e.g.
Negates a given criteria (e.g.
|Criteria c1, Criteria c2
Combines two criterias with a logical AND. This is not very useful in the ban entry itself because the criterias in the ban entry are already linked to each other with AND
|Criteria c1, Criteria c2
Combines two criterias with a logical OR
A ban entry may have multiple actions that will be executed when an item or block matches its criterias.
Removes the item or block from the world.
By default the player can keep the block or item that is banned (this is useful when an item is only banned in some dimensions).
|Prints a message to the player.
|Logs the incident to the console
|Kicks the player from the server with the given message
|String kickMessage, String banMessage
|Bans a player from the server
|Executes a command in a console point of view
|Executes a command in a player point of view
The command of ServerCommand and PlayerCommand has some patterns for the execution environment:
|The player name
The player's UUID with hypens
|The item id
|The item meta / damage
|The item stack size
|The dimension id of the incident
There are different incidents where RestrictIO checks whether the item or block is banned. You can specify for every Ban entry in which case it should be checked.
|When a block gets broken
|The block being broken
|When a block gets placed
|The block being placed
|Periodic (all 30s) scan of all player inventories
|All stacks in the player's inventory
|When a player drops an item or when he dies
|The item(s) being dropped
|When a player tries to pickup an item
|The items will be picked up
|When a player interacts (item rightclick, block left or rightclick)
|The (optional) block the player interacts with and/or (optional) the item in hand
|When the reciepes get registered. The reciepe will be disabled globally!
|All standard shape(less) crafting outputs
For performance reasons you should use as few triggers as possible for your needs.
Don't use BlockBreak/BlockPlace in conjunction with ItemInteract!
ItemInteract covers the them.
- Blocking a machine that is not placed
- ReciepeRegistration (when not allowed anywhere)
- Blocking a machine that may have already been placed
- ReciepeRegistration (when not allowed anywhere).
- Completely blocking an item or block that is already in inventories and in the world