# Criterias

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.

<table id="bkmrk-name-parameters-desc"><tbody><tr><td>**Name**</td><td>**Parameters**</td><td>**Description**</td></tr><tr><td>ID</td><td>String itemID</td><td>Match the item id (e.g. `minecraft:stone`).

Blocks without a corresponding item can't be matched

</td></tr><tr><td>Meta</td><td>int meta</td><td>Match the item meta or damage. </td></tr><tr><td>Dimension</td><td>String dimName</td><td>the world name where the entry should apply.

The id is also allowed

</td></tr><tr><td>Nbt</td><td>String nbtJson</td><td>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.

</td></tr><tr><td>Player</td><td>String name</td><td>The playername of the player for which the the entry should be valid

</td></tr><tr><td>Mod</td><td>String modid</td><td>The modID the item will be matched against. The modID is the first part of the item's resource location (e.g. `minecraft` for `minecraft:stone`)

</td></tr><tr><td> </td><td> </td><td> </td></tr><tr><td>Not</td><td>Criteria crit</td><td>Negates a given criteria (e.g. `Not(Dimension(0))` will be any dimension exept 0)

</td></tr><tr><td>And</td><td>Criteria c1, Criteria c2</td><td>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

</td></tr><tr><td>Or</td><td>Criteria c1, Criteria c2</td><td>Combines two criterias with a logical OR

</td></tr></tbody></table>