Bukkit

IMPORTING FROM 0.2: many changes were made to the configuration since 0.2, mainly the new tracks system. We highly recommend moving your 0.2 config file to a different location, running the new 0.3 version to generate a new config, and then copy your custom options back over.

There are many configurable options that you are able to modify in Karma. The file plugins/Karma/config.yml, which will be generated by your server on first run of the plugin, shows all the options. A bulk of them are for configuring messages. The default configuration generated by the plugin is similar to how the Warhub is set up for Karma.

The tracks section is for listing the server's tracks. When a player first joins the server, they are assigned a track. To change the one this is, set the default option on the track to true. Inside of the track, there are groups with their color and amount of Karma points. They can be in any order, as they are automatically sorted by their points internally.

Karma parties are configurable as well. You can set the interval at which they occur in minutes and the amount of points distributed. If you choose, you can provide additional Karma to players in war zones. There is a specified random chance for this and the amount of points granted.

When you first enable Karma and players that have joined before connect, their groups will be determined and then granted the amount of points they need. The extra amount that can be given is specified as a percent. The amount granted is a percent of the difference between their next rank's Karma and their current rank's points.

If you choose, you can also allow Karma to use a MySQL database server to store the data in, instead of the default SQLite file placed in plugins/Karma. Using MySQL is recommended in new server installs for it's stability. If you do not wish to use MySQL, you can configure the location of it's database. Karma only uses one table in the database called players. I would recommend regular backups if not using MySQL.

Karma checks if a player is AFK (away from keyboard) through a variety of ways. You can configure the ones it will check. If move is enabled, then they will become un-afk every time they move. Various contraptions have been developed over time that allow players to continuously move when idle, such as a minecart loop, so this option is recommended to be set to false to prevent players from being able to achieve ranks without actually being on the server and helping. Currently, a player is AFK when any of these triggers have not been called in the last 10 minutes, but we plan on making that delay configurable.