KarmicShare v0.23

Details

  • Filename
    KarmicShare.jar
  • Uploaded by
  • Uploaded
    Jan 23, 2012
  • Size
    154.05 KB
  • Downloads
    362
  • MD5
    8ad398daf98091ff9a32c4e47a29cb1c

Supported Bukkit Versions

  • CB 1.0.1-R1

Changelog

Changes in this update:

v0.23

  • Completely assimilated custom LogBlockQuestioner package.
    • Should resolve conflicts with existing LogBlockQuestioner.jar. They should now coexist fine.
  • Config is reloaded before saving on server stop. Changes to config.yml should now be preserved on plugin disable.

v0.22

  • Removing a group also removes the group's associated items from the item table.

v0.21

  • Massive internal refactoring and optimization.
    • Smaller file size for what its worth...
  • Fix on the drain command when giving a specific group name.
  • Minor edits on strings.

v0.2

  • MySQL support
  • Drain command now accepts a group name, so you can specify what item pool you want to empty.

IMPORTANT:

If you were on a release before v0.2, and wish to use MySQL. Run the updated plugin as it is at least once for the following reasons:

  • Add the new config automatically to the config.yml.
  • VERY important changes to the database and table names.

If you do not run it at least once, and configure everything manually from MySQL, then there is no way use the built-in auto-import process. This is because the tables from SQLite will have a different naming scheme than the MySQL tables. You will have to either:
1) Manually import from SQLite to MySQL
2) Rename the SQLite database tables to the appropriate table names
3) Revert the version number to something before '0.2', set mysql.use to false in the config, and then run at least once to update the SQLite tables to the appropriate names

  • Using admin command /ks admin add <item> ... does not allow for item name like the user's version of take /ks take <item name>. May or may not bother with this... Perhaps in the future.It can parse the name if given it as defined in Bukkit's Material class, but not in KarmicShare's normalized way.
  • Initial per-item karma defaults are still quite limited...