Mortis Development
  • 👋Mortis Development
  • Mortis Core
    • Commands & Permissions
    • Custom Items
      • Detectors
      • Crafting Recipes
    • Custom Menus
      • Menu Items
      • Actions
        • Action Types
      • Requirements
    • Custom Blocks
    • Custom Mobs
    • Randomizer
    • Actions
      • Action Types
    • Requirements
      • Requirement Types
    • Default Configs
  • Mortis Minion
    • Commands & Permissions
    • Placeholders
    • Minions
      • Layouts
      • Minion Tiers
    • Skins
    • Fuels
    • Shippings
    • Upgrades
    • External Storages
    • Action Types
    • Default Configs
  • Mortis Bank
    • Commands & Permissions
    • Placeholders
    • Accounts
    • Action Types
    • Default Configs
Powered by GitBook
On this page

Was this helpful?

  1. Mortis Core

Requirements

All requirements related options & configurations

requirement:
  mininum: 1
  stop-at-success: true
  success-actions:
    ...
  deny-actions:
    ...
  requirements:
    example-requirement:
      ...
    example-requirement-2:
      ...
requirement:
  # Minimum requirements are optional.
  # If they are not set, then all
  # requirements will be needed for the
  # click commands to be executed.
  # In this example, only one of the
  # requirements will be needed.
  min: 1
  # This option is good for when you use minimum_requirements.
  # Instead of the plugin checking all the requirements,
  # it will stop when it has enough.
  stop_at_success: true
  requirements:
    # You can define multiple requirements.
    # Each requiremnt should have a unique name.
    requirement_name:
      type: TYPE
      # These commands will be exeucted if
      # the requirement they're set for is
      # met even if the others are not.
      # You should be careful and not confuse
      # these with click_commands: !!!
      success_commands:
      - "[ACTIONTYPE] ACTION"
      - "[ACTIONTYPE] ACTION"
      # These commands will be executed if
      # the requirement they're set for is
      # not met even if the others are.
      deny_commands:
      - "[ACTIONTYPE] ACTION"
      - "[ACTIONTYPE] ACTION"
      # This option is only required if you
      # want ot use minimum_requirements:
      # Minimum requirements will only work
      # for the optional requirements
      optional: true
  # This can only be defined for open and
  # left/right click requirement
  deny_commands:
    - "[ACTIONTYPE] ACTION"
    - "[ACTIONTYPE] ACTION"
open-requirement:
  requirements:
    permission:
      type: has permission
      permission: "enchanter.enchant"
PreviousAction TypesNextRequirement Types

Was this helpful?