Bukkit.yml

This page has been suggested for inclusion in the Official Documentation This page has been marked for inclusion in the Bukkit Offical Documentation section, Docs. You can deliberate about it's inclusion on it's Talk page.

Bukkit.yml is a file that provides you with a wide variety of options for configuring your CraftBukkit server.

Sections in the YAML

The headings listed below are the top-level keys in the YAML file.

settings

General CraftBukkit server options.

• allow-end: (boolean) Is the End enabled. Default: true
• warn-on-overload: (boolean) Does the server show "[WARNING] Can't keep up! Did the system time change, or is the server overloaded?" messages. Default: true
• spawn-radius: (integer, radius) How many blocks in radius the spawn protection should apply to. Default: 16
• permissions-file: (string, filename) The name of your custom permissions file. Default: permissions.yml
• update-folder: (string, foldername) The name of the folder to put updated plugins in, which will be moved upon restart. Default: update. NOTE: The folder MUST be in the plugins folder. Absolute paths do NOT work.
• ping-packet-limit: (integer, packets/sec) Currently disabled. Previously: How much packets a second the ingame ping list can use, maximum. Default: 100
• use-exact-login-location: (boolean) See below for details. Default: false
• world-container: (string, foldername) The name of a folder to store all the world directories in. If not included in your file, defaults to the current working directory.
• plugin-profiling: (boolean) Measure time taken by plugin for events. Default: false
  • This allows the command: /timings
• connection-throttle: (long, milliseconds) The delay before a client is allowed to connect again after a recent connection attempt. A value of 0 disables the connection throttle but leaves your server susceptible to attacks (only recommended for test servers). Default: 4000

use-exact-login-location

Since Minecraft added the feature of pushing entities out whenever they are stuck inside a block, players have often found themselves above the location they logged out of when logging back in (especially if they were in a cave). This new bukkit.yml setting allows servers to disable or enable this behaviour.

If true, we will bypass Vanilla's behaviour of checking for collisions and moving the player if needed when they login.

If false, we will continue to follow Vanilla's behaviour and move players that 'collide' with objects when they login.

ticks-per

CraftBukkit server options that determine the tick delay for specific features

animal-spawns

This bukkit.yml setting allows servers to set the tick delay for animal spawns.

Example Usage:

• A value of 1 will mean the server will attempt to spawn animals every tick.
• A value of 400 will mean the server will attempt to spawn animals every 400th tick.
• A value below 0 will be reset back to Minecraft's default.

Note: If set to 0, animals spawning will be disabled. We recommend using spawn-animals to control this instead.

Minecraft default: 400.

monster-spawns

This bukkit.yml setting allows servers to set the tick delay for monster spawns.

Example Usage:

• A value of 1 will mean the server will attempt to spawn monsters every tick.
• A value of 400 will mean the server will attempt to spawn monsters every 400th tick.
• A value below 0 will be reset back to Minecraft's default.

Note: If set to 0, monsters spawning will be disabled. We recommend using spawn-monsters to control this instead.

Minecraft default: 1.

auto-updater

Controls the built in update checker.

• enabled: (boolean) Is the update checker enabled. Default: true
• on-broken: (string array) What to do if the version the server is on is known to have a large bug or exploit. Can be "warn-ops" and/or "warn-console". Default: [warn-console, warn-ops]
• on-update: (string array) What to do if the version the server is on is out of date. Can be "warn-ops" and/or "warn-console". Default: [warn-console, warn-ops]
• preferred-channel: (string) Which release channel is preferred for this server. Can be "rb", "beta" or "dev". Default: rb
• host: (string) The update checker location. You probably should never change this, unless you know what you're doing. Default: dl.bukkit.org

aliases

This section allows you to map aliases to commands. Example:

aliases:
    # This creates a new command called "canihasbukkit", which when used it actually performs "version"
    canihasbukkit: version
    
    # And this will execute both "save-all" and then "stop" when you type "savestop"
    savestop: [save-all, stop]
    
    # If a command already exists called "give", it will be rewritten. This is handy if you've two plugins
    # fighting for the same name.
    give: somepluginsgive

database

This section lets you set various database-related configuration options, for the database which will be shared by plugins that use the internal eBeans server. Most plugins do not use this, so whether or not you need to configure it is up to you. Changing these properties will change how all plugins that use the eBeans server integrated with Bukkit connect to their database.

• username: (string) Username to connect to database. May be ignored depending on driver.
• password: (string) Password to connect to database. May be ignored depending on driver.
• isolation: (one of SERIALIZABLE, ...) Generally leave this alone unless advised otherwise.
• driver: (string, JDBC class name) The JDBC driver class that should be used. See the documentation for your database's Java driver for this value.
• url: (string, JDBC database URL) The URL to connect to the database. For MySQL/PostgreSQL or other server-client databases, this will generally include the hostname, port and database name. For file-based databases, such as SQLite, this will usually include the filename.

The following are examples of what each configuration would look like for the two most commonly used database applications.

SQLite Configuration (default):

database:
  username: bukkit
  isolation: SERIALIZABLE
  driver: org.sqlite.JDBC
  password: walrus
  url: jdbc:sqlite:{DIR}{NAME}.db

Note: the {DIR} and {NAME} words represent the directory of the plugin data folder and the name of the individual db file. They are actual variable names Bukkit uses, therefore changing these settings are not recommended.

MySQL Configuration example:

database:
  username: {USERNAME}
  isolation: SERIALIZABLE
  driver: com.mysql.jdbc.Driver
  password: {PASSWORD}
  url: jdbc:mysql://{IP}:{PORT}/{DATABASENAME}

Note: {USERNAME}, {PASSWORD}, {IP}, {PORT}, and {DATABASENAME} are not actual variable names that Bukkit uses like in the SQLite example. They just represent data you should change to get the MySQL configuration to work correctly.

*OPTIONAL* worlds

This section lets you define the generators for the worlds that bukkit loads by default.

Prereqs: You MUST have the generator installed already, and the generator's developer must have {{{load: startup}}} in their plugin.yml.

If you want your world, named 'world1' (the same thing you have as 'level-name' in server.properties) and wanted to use the CleanroomGenerator with no params, you could do this:

 settings:
   ...
 aliases:
   ...
 database:
   ...
 worlds:
   world1:
     generator: CleanroomGenerator

If you wanted some custom params:

 settings:
   ...
 aliases:
   ...
 database:
   ...
 worlds:
   world1:
     generator: CleanroomGenerator:10,stone,20,dirt,1,grass