CoreConfig

ExpCraft Core Configuration

ExpCraft consists of one bukkit plugin that loads several modules. The modules affecting the players in a certain way.

The core (the bukkit plugin) is responsible for storing players progress, executing commands and determine permissions. There are several variations on how the core can do this. What it really does is described in the plugins/ExpCraft/config/Core.properties configuration file.

Default Configuration

# whether to play the level-up sound when reaching a new level for an
# EC module
Chat.PlayLevelUpSound=true
# whether to notify all player about the progress of a player 
Chat.NotifyAll=true
#
# Chat colors
Colors.ColorOne=GOLD
Colors.ColorTwo=YELLOW
Colors.ColorGood=GREEN
Colors.ColorBad=RED
#
# A constant affecting how much experience must be earned to gain a level
# The larger this value is, the harder ExpCraft becomes
Levels.Constant=20
# Largest reachable level
Levels.LevelCap=100
# How to store experience
Database=FlatFile

The colors define how ExpCraft will format chat messages. Each message sent to player is prefixed with a ColorOne [EC]. A normal informational message will be written in ColorTwo. A positive message will be written in ColorGood. Warnings and other bad messages will appear in ColorBad.

There are two supported ways to store experience: FlatFile, or, Bukkit. FlatFile means, ExpCraft creates a Properties file for each module in plugins/ExpCraft/data/. The other values indicate to store experience in a database. Bukkit comes bundled with all the drivers required to access the mentioned database engines. See next paragraph.

Bukkit

To delegate the database access to bukkit you have to state the database type in the Core.properties and the database connection in the bukkit.yml.

Database=Bukkit

Ensure that you only have one Database: line in the file!

Note that the old native SQL implementations and their corresponding configuration options are no longer supported. Any DbConnection information in the Core.yml is ignored.

At the end of bukkit.yml - which is part of the bukkit server installation - there is a section for the database connection parameters:

# example for MySQL
database:
  username: user
  isolation: SERIALIZABLE
  driver: com.mysql.jdbc.Driver
  password: pass
  url: jdbc:mysql://localhost:3306/minecraft

And

# example for SQLite
database:
  username: bukkit
  isolation: SERIALIZABLE
  driver: org.sqlite.JDBC
  password: walrus
  url: jdbc:sqlite:bukkit.db

MySQL and SQLite

The option to access databases directly through JDBC has been removed. Use the Bukkit database method instead!