Main config

You can see how to configure the plugin here.

The main config file is config.yml. Most of these options can be reloaded with /aurora reload, but storage related options and the ones marked below need a full server restart.

debug - leave it false if the developer doesn't say otherwise. It will log some extra information if it is enabled to the console

supported-languages - List here all the language codes you support (that have a messages_<code>.yml file). If a file doesn't exist yet, it will be generated from the default English one.

locale - your default language

use-per-player-locale - optionally, you can enable per-player localization support. See Per player localization.

number-format

locale - this will be used in number formatting (if use-per-player-locale is disabled)
int-format - number format pattern for whole numbers (without decimals)
double-format - number format pattern for decimal numbers
short-number-format - used where Aurora plugins display shortened numbers like 1.5K or 2M
- format - number format pattern for the shortened number
- suffixes - the suffix for each magnitude: thousand, million, billion, trillion and quadrillion

number-format:
  locale: en-US
  int-format: '#,###'
  double-format: '#,##0.##'
  short-number-format:
    format: '#,##0.##'
    suffixes:
      thousand: "K"
      million: "M"
      billion: "B"
      trillion: "T"
      quadrillion: "Q"

user-auto-save-in-minutes - how often should the plugin auto save user data in minutes? (default 10)

storage-type - where to store user data? can be either yaml or mysql. If you use mysql, leaderboard data is stored in MySQL as well, otherwise it is stored in a local SQLite database. To move existing data between the two, use /aurora dbmigrate.

mysql

host - SQL server ip address or domain host name
port - SQL server port (number)
ssl - Whether to use SSL or not for the connections
database - Name of the database to connect to
username - SQL username
password - SQL password
network-latency - How long does it take to send data from the server to the database server and back in milliseconds? Used for data sync when players are switching servers. /aurora debug latency can help you measure it.
pool-size - How many concurrent connections can we have?
sync-retry-count - How many times should we wait the network latency for the sync flag to be removed before we load the data anyways?

block-tracker

enabled - should the block tracker work? It tracks blocks placed by players, so other Aurora plugins can ignore them (for example to prevent place and break farming). The data is stored inside the chunks themselves, so there is nothing else to configure. Changing this requires a restart.

leaderboards

empty-placeholder - the text leaderboard placeholders show when there is no player on the requested position. (default ---)

default-economy-provider - which economy plugin should be used when an action or requirement doesn't specify one. Use auto-detect to pick one automatically, or the name of a provider from Economy providers. Changing this requires a full restart.

item-matchers - the item plugins Aurora should hook into to resolve custom items (see Item config). Integrations are only loaded if the plugin is installed. Remove an entry if that integration causes errors.

item-matchers:
  - "CustomFishing"
  - "Eco"
  - "ExecutableItems"
  - "ExecutableBlocks"
  - "HeadDatabase"
  - "ItemsAdder"
  - "MMOItems"
  - "MythicMobs"
  - "Nexo"
  - "Oraxen"
  - "ItemEdit"
  - "EvenMoreFish"
  - "KGenerators"
  - "CraftEngine"
  - "CrackShot"

item-resolver-priorities - when an item matches more than one item plugin (for example an item from one plugin that was built on top of another plugin's item), the resolver with the highest number wins. This decides which ID Aurora detects for an item, for example in /aurora debug itemid or in item based quest objectives. The keys are the item ID namespaces.

item-resolver-priorities:
  crackshot: 210
  customfishing: 200
  craftengine: 195
  eb: 190 # ExecutableBlocks
  emf: 180 # EvenMoreFish
  ei: 170 # ExecutableItems
  mmoitems: 160
  mythicmobs: 150
  eco: 140
  nexo: 130
  oraxen: 120
  ia: 110 # ItemsAdder
  itemedit: 100
  kgenerators: 95
  hdb: 90 # HeadDatabase
  aurora: 80

aurora-items

enable-id-resolver - Should Aurora try to recognize items registered through /aurora registeritem <id> and resolve them to aurora:<id>? This is experimental and may not work for every use case. Changing this requires a full restart.

config-version - DO NOT TOUCH THIS FOR YOUR OWN SAKE