Conditions and Criterias

What is this?

This option decides whether an action is allowed to be done or not.

Break Condition:
    Criteria: LOGIC_OR
    Conditions:
    -   Criteria: IS_OWNER
    -   Criteria: HAS_PERMISSION
        Permission: fancywaystones.admin

Based on the example above, the condition is accepted if the player is owned of the waystone, or has the permission fancywaystones.admin

Criterias

RANDOM

Random will accept condition in percentage chance. The options are:

  • Chance the percentage chance of the condition will be accepted

For example:

Break Condition:
    Criteria: RANDOM
    Chance: 69

The example above will accept the condition if the player is lucky enough to have the 69% chance.

ENCHANTED

Enchanted will accept the condition if the player is holding any item that is enchanted. The options are:

For example:

Break Condition:
    Criteria: ENCHANTED
    Type: SILK_TOUCH
    Level: 1

The example above will accept the condition if the player is holding any tool with silk touch enchantment (minimum level 1)

EFFECT

Effect will accept the condition if the player is having a potion effect. The options are:

For example:

Break Condition:
    Criteria: EFFECT
    Type: DOLPHINS_GRACE
    Level: 0

The example above will accept the condition if the player has Dolphin grace effect.

LAND_ACCESS

Land access will accept the condition if the player has the access to build on that region.

For example:

Break Condition:
    Criteria: LAND_ACCESS

HAS_LAND_ACCESS

Same as Land Access

IS_MEMBER

Is Member will accept if the player is whitelisted on the waystone

For example:

Break Condition:
    Criteria: IS_MEMBER

HAS_PERMISSION

will accept if the player has the permission required

For example:

Break Condition:
    Criteria: HAS_PERMISSION
    Permission: 'fancywaystones.admin'

IS_OWNER

will accept if the player is the owner of the waystone

For example:

Break Condition:
    Criteria: IS_OWNER

IS_EXPLOSION

will accept if the condition occurred by an explosion (TNT, Creeper, etc)

For example:

Break Condition:
    Criteria: IS_EXPLOSION

WORLD_WHITELIST

will accept if the condition occurred in the world that is listed.

For example:

Break Condition:
    Criteria: WORLD_WHITELIST
    Worlds:
    - world
    - world_nether
    - world_the_end

TYPE_WHITELIST

will accept the condition if the waystone type is listed.

For example:

Break Condition:
    Criteria: TYPE_WHITELIST
    Types:
    - public
    - public_normal
    - public_nether
    - public_the_end

WHITELISTED_ENTITIES

OFFSET_DISTANCE

will accept if the offset distance set by the player for the waystone is in a specific range of distance.

  • Min Distance the minimum distance of the offset distance

  • Max Distance the maximum distance of the offset distance

IS_HOLDING

will accept if the player is holding the item specified in the config

Break Condition:
    Criteria: IS_HOLDING
    Display Name: 'Super Omegalol Pickaxe'
    Item:
        type: NETHERITE_PICKAXE
        amount: 2

The Display Name option is used to alter the display name for the item when shown in the chat. This option is optional.

LOGIC_NEGATE

will negate the condition. If the criteria inside accept the condition, it will negate it.

Break Condition:
    Criteria: LOGIC_NEGATE
    Condition:
        Criteria: IS_HOLDING
        Item:
            type: DIRT

The example above will accept the condition if the player is NOT holding a dirt.

LOGIC_OR

will accept the condition if any of the criteria inside accept the condition.

Break Condition:
    Criteria: LOGIC_OR
    Conditions:
    - Criteria: EFFECT
      Type: SPEED
      Level: 0
    - Criteria: EFFECT
      Type: JUMP
      Level: 0

The example above will accept the condition if the player has speed effect OR if the player has jump effect.

LOGIC_AND

Similar to logic_or, but will accept if all of the criteria inside accept the condition.

Break Condition:
    Criteria: LOGIC_AND
    Conditions:
    - Criteria: IS_HOLDING
      Item:
          type: DIAMOND_PICKAXE
    - Criteria: LOGIC_OR
      Conditions:
      - Criteria: ENCHANTED
        Type: SILK_TOUCH
        Level: 1
      - Criteria: EFFECT
        Type: DIG_SPEED
        Level: 0

The example above will accept the condition if the player is holding a diamond pickaxe and (enchanted with silk touch or has fast mining effect)

IS_ENVIRONMENT

will accept if the condition occurred in an environment

Break Condition:
    Criteria: IS_ENVIRONMENT
    Environment: NETHER

HAS_CONTEXT

will accept if the condition occurred in a context

Visit Condition:
    Criteria: HAS_CONTEXT
    Context: WARPSTONE

The example above will accept the condition if there is Warpstone Context. In other words, the player will be teleported if theyre using warpstone to teleport to the waystone.

STRING_MATCHES

If you are using PlaceholderAPI, you can use this to test if the value of 2 placeholders is the same.

Break Condition:
    Criteria: STRING_MATCHES
    A: '{player_name}'
    B: 'Septogeddon'
    Reason: 'You must be Septogeddon to do this'
    Reason Negate: 'You must not be Septogeddon to do this'
    Ignore Case: false

ALWAYS

always accept the condition

NEVER

never accept the condition

IS_WAYSTONE_ACTIVATED

will accept if the waystone is activated, similar to IS_MEMBER but only if the player actually discover it.

IS_NATURAL

will accept if the waystone is generated naturally using structure

IS_SAME_TYPE

will accept if the target waystone and the source waystone is the same type

IS_SAME_WORLD

will accept if the teleportation occurred in the same world

IS_SAME_SERVER

will accept if the teleportation occurred in the same server

IS_SAME_DIMENSION

will accept if the teleportation occurred in the same dimension

PreviousCustomize WaystoneNextCustomize Waypoints

Last updated