ConditionPerms_CONFIG

# ------------------------------ #
#
#  ConditionPerms
#  (c) Maxim Van de Wynckel
#
# ------------------------------ #

#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
# GENERAL PLUGIN SETTINGS
#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#

## Config version (DO NOT EDIT)
config: 1

## Language file
lang: 'en'

## Debug mode
debug: false

## Log to file
log:
  enabled: true
  # Reset log on startup
  reset: false

## Update checking
update:
  check: true # RECOMMENDED YOU LEAVE THIS TRUE

#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
# PLUGIN SPECIFIC SETTINGS
#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#

# Placeholder settings
placeholder:
  # logs the memory usage of placeholders on startup
  log-memory: false
  # Clear unused placeholders that are not enabled.
  clear-unused: true


# Condition engine
# This is the engine that will be used to evaluate the conditions
# Only edit when you know what you are doing!
engine: 'javascript'


# Configure the database. This database is used to keep track
# of the players that have been granted the condition permissions
# already.
#
# Default it is set up for SQLite. MySQL support
# is possible but for this use case not recommended.
#
# NOTE: The databases are not convertible
database:
  # Database name
  database: "conditionperms"
  # Database username
  username: bukkit
  # Database isolation type
  isolation: SERIALIZABLE
  # Database driver
  driver: org.sqlite.JDBC
  # Database password
  password: walrus
  # Database driver URL
  # {DIR} will be replaced with the plugin directory
  # {NAME} will be replaced wit the plugin name
  url: jdbc:sqlite:{DIR}{NAME}.db

# A list of all conditions you configured
# You can add your own conditions yourself
# For more detailed info see the plugin page
conditions:
  health-example: # This is a random name given to a condition
    condition: '{health} < 10' # Here you define the statement of the condition
    checkinterval: 60 # This is the interval in ticks the condition is checked
    revoke: true # If set to true conditions will be revoked when no longer met
    cooldown: 0 # This is the check cooldown (in ticks) after the check is true. A use could be:
                # for example you want to check if a player is in an area (fast)
                # and you want to send a message every X ticks.
    allplayers: false # Check the condition on all players (performance drop)
    commands-on-grant: # Execute all commands below this when the condition is met
    - 'say {player} has low health! Help him!!'
    commands-on-revoke: # Execute all commands on revoke (revoke needs to be true)
    - 'say {player} is back OK!'
    permissions: # Grant and/or revoke following permissions
    - ''
    permission-world: '' # The world used to add permissions to, leave empty for player location
  fly-example: # This is a random name given to a condition
    condition: '{isflying}' # Here you define the statement of the condition
    checkinterval: 10 # This is the interval in ticks the condition is checked
    revoke: true # If set to true conditions will be revoked when no longer met
    allplayers: false # Check the condition on all players (performance drop)
    commands-on-grant: # Execute all commands below this when the condition is met
    - 'console:say {player} is flying ...'
    commands-on-revoke: # Execute all commands on revoke (revoke needs to be true)
    - 'console:say {player} is no longer flying :)'
    permissions: # Grant and/or revoke following permissions
    - ''
    permission-world: '' # The world used to add permissions to, leave empty for player location
  # The example below is a bit more tricky. It uses the Math lib. to check if a player is in a 10 block range of his bed
  bed-location-example:
    condition: '(Math.abs({x} - {bed_x}) < 10) && (Math.abs({y} - {bed_y}) < 10) && (Math.abs({z} - {bed_z}) < 10)'
    checkinterval: 20
    revoke: true
    allplayers: false
    commands-on-grant:
    - 'console:say {player} you are close to your bed!'
    commands-on-revoke:
    - 'console:say {player} no no! wrong way!'
    permissions: []
    permission-world: ''