v1.7.2

Details

  • Filename
    DonationPoints.jar
  • Uploaded by
  • Uploaded
    Jun 16, 2013
  • Size
    39.71 KB
  • Downloads
    629
  • MD5
    f5947e4a6cf8eebc49eb68e556a57857

Supported Bukkit Versions

  • CB 1.5.2-R1.0

Changelog

Version 1.7.2

  • You can now use custom names on the MySQL / SQLite tables.
  • Config Strings are now public so you should be able to access them using the API. (Untested, Developers Only, In the Commands class)
  • /dp package info now shows the prerequisite to the package.
  • Balances now round out to 2 decimal places to prevent messy decimals on /dp balance, /dp give, etc.
  • Checks if the player has an account on /dp give. (Will not create one, it will instead just tell you that the player does not have an account)

Version 1.7.1

Crucial Fix

  • Fixes packages not being responsive.
  • Fix Config NullPointerExceptions
  • Fix ConfigChecker

(Basically took everything in 1.7.0 and fixed it)

Version 1.7.0

Small update, but pushing it to the next "major" version. I need more suggestions for the plugin. Any features you want added? Let me know.

New Features:

  • The plugin will not check your config for you when it loads to make sure you have all of the fields there. This relies on the Config Version. The Config Version will always be the version of the plugin it is on without any decimals involved. IE 170 = 1.7.0
    • If your config version does not match 170, it will update your config including all fields that you are missing. (Even those that came in earlier versions). For optimal use, never change the config version.
    • The Config will generate an example package as well, instead of God / Kick. This is to show all of the fields that should be in the package section. So you can check this to see if your packages need updating.
    • When a new config is out, it will NEVER delete the contents of your old config, simply add the new ones that are needed.
  • PreRequisites
    • Each package can have a configurable pre-requisite. What this does is it makes it so that the player must have purchased a certain package before they can purchase another one. Example use would be: VIP2 requires the user to have already purchased VIP1.

Leave new feature suggestions / bug fixes in the form of a Ticket / Comment. Thank you!

Your title here... ===None