Config Masks

MMOItems Recommended: Use this external plugin to get the most out of this feature.

Allow only certain items to be stored in slots.

/goop containers config masks <container> <slots> [<type/id> <name>]

Allow only MMOItems of certain Types, IDs, or in general, items of certain kinds (armor / ranged weapons / axes)

Only one item fits here, and that is m MEDALLIONS THERMOCORE.

Args Breakdown (What everything does)

<container>

<slot>

    • Slot numbers that you want to edit. Always a positive integer number.

    • Though you normally target containers with the c key...

      • For this command do not use it, just do 0-8,9,17 instead of c0-8,c9,c17

      • You don't actually have the container open now so this c key wouldn't work anyway

[type/id]

    • Target of the mask you want to apply

      • type Will restrict to only certain MMOItem Type. Requires MMOItems.

      • id Will restrict to only certain MMOItem IDs, this requires MMOItems.

        • The ID mask can also be used to check vanilla material. Use this if you do not have MMOItems.

    • Do not specify to clear all masks of this slot.


If type was chosen

<name>

    • A comma-separated list of MMOItem Types.

      • If any MMOItem Type has any spelling mistake, the entire thing will fail to load.

    • Or any OnApply Mask (that you specify in the config file onapply-masks.yml)


If id was chosen

    • A comma-separated list of things to check for:

      • Vanilla kind checks, that target the vanilla material of the item

        • ARMOR, HELMET, CHESTPLATE, LEGGINGS, BOOTS, HEAD ~ Things that can be equipped in armor slots.

        • TOOL, FISHING_ROD, TRIDENT, RANGED_WEAPON, CROSSBOW, MELEE_WEAPON, AXE, SWORD ~ Held items.

        • SHULKER, LEAVES, BUTTON, PRESSURE_PLATE, DOOR, TRAPDOOR ~ Misc stuff that has been suggested.

      • MMOItem IDs of your choosing.

    • Precede any of each mask with the ! symbol to negate it.

      • See simple examples section for clarification.

Tips

  • Masks prevent items from being stored in slots, by the attributes of the item being stored.

    • To prevent players from storing items in slots, based on attributes of the player (like lack of permission), see Restrictions.


  • ID Masks are treated as whitelists and blacklists.

    • If you start the id mask with the ! symbol, it will be sent into the blacklist.

    • If the item matches any of the blacklisted ids, it is not accepted into the slot. Skip this step if there is no blacklist.

    • The item must be in the whitelist, or it will not be accepted into the slot. Skips this step if there is no whitelist.


  • If you do not have the plugin MMOItems, you may only focus on the id with one of the pre-loaded kind checks.


  • You can only specify one type mask, and calling the command again will overwrite the previous.


  • You can specify an infinite number of ID masks, just make them a comma-separated list.

Simple Examples:

/goop containers config masks BANK 0-54 type CurrencyMask

Makes all the storage slots of 'BANK' only accept MMOItems that are defined in the OnApply Mask 'CurrencyMask'


/goop containers config masks ARMORY_BOX 0-8 id HELMET,HEAD

First row of the 'ARMORY_BOX' will only accept helmets and heads to be put inside it.


/goop containers config masks BOWS_STRAPON 0-17 id RANGED_WEAPON,!CROSSBOW,!THORN_WAND

Suppose you want to make a 'BOWS_STRAPON' container that allows players to store all their bows, but not crossbows. And you have an MMOItem that is a material bow (so it would be detected by kind RANGED_WEAPON) but its actually a wandor something. You exclude those things like this.