OnTime v3.1.0

Details

  • Filename
    OnTime.jar
  • Uploaded by
  • Uploaded
    Aug 7, 2012
  • Size
    154.54 KB
  • Downloads
    1,077
  • MD5
    f4862c51f598ebb0501fcd88e2d6869e

Supported Bukkit Versions

  • CB 1.3.1-R1.0

Changelog

V3.1.0

  • Compiled with Bukkit 1.3.1-R1.0
  • Added ability to define incentive reward for players to use the 'referred by' command
  • Expanded '/ontime reward refer' command to include [source/target] keyword
  • Fixed MC 1.3.1 issue with AsyncPlayerChatEvent
  • Fixed MC 1.3.1 related issue where reload (rl) of plugins didn't properly handle players that were online at the time of the reload
  • Added auto upgrade of rewards.yml and output.yml files associated with new 'ontime reward refer' option listed above.

V3.0.5

  • Compiled with Bukkit 1.2.5-R5.0, but tested (basic functions) with Bukkit 1.3.1-R0.1(Development build)
  • Fixed problem with Bukkit 1.3.1 where total playtime was not getting updated

V3.0.4

  • Compiled and tested with Bukkit 1.2.5-R5.0
  • Added ability to create multiple rewards with the same target time
  • Fixed Null Pointer error seen sometimes on server start or plugin reload
  • Fixed error where weekly/monthly rewards needed daily data collection to be enabled
  • Fixed error where daily play time could be stored as a negative time value

V3.0.3

  • Fixed error in handling of MySQL save and load of player data
    • Please see "Known caveats" section below for instructions on how to recover if you used V3.0.2, or are upgrading from any earlier version.

V3.0.2

  • Added "top player" rewards
  • Added '/ontime rewards top' command
  • Added new config.yml elements for "top player" rewards
  • Added new entries into output.yml for "top player" rewards
  • Fixed error in time/date calculation when issuing reports
  • Fixed error in placing wrong 'starting date' put into weekly and monthly reports
  • Fixed error in 'top xx daily' command starting numbering with 2, not 1.

V3.0.1

  • Never Released*

V3.0.0

  • Added MySQL storage option for OnTime Player Data
  • Added import of player name, total playtime, and last login data from 'logblock' plugin
  • Added simultaneous collection of daily, weekly, and monthly data. (Previous releases only one could be done at a time)
  • Added 'referred by' rewards
  • Added 'perpetual' rewards
  • Added export of OnTime data to .dat, .yml. and MySQL database formats
  • New Commands:
  • ontime import logblock
  • ontime export [dat/yml/mysql]
  • ontime rewards edit time
  • ontime rewards perp
  • ontime rewards refer
  • referred by

It is always recommended that you do a backup of your OnTime Data before installing a new version. Execute "/ontime backup" from the console or in game.
Note: If you are using MySQL for storage of player data and are still running OnTime V3.0.2, you will likely have multiple rows of "ontime-data" in the ontime-players table. After downloading and installing V3.0.3 - V3.0.5, or V3.1.0 and starting your server, please execute the following commands if you are still using MySQL for storage of player data:

/ontime remove ontime-data
/ontime save

This will remove the duplicate rows.

If you are upgrading from v3.0.4 - v3.0.6 the plugin will automatically make updates to the rewards.yml and output.yml files. There are no additional actions required for you to take other than to download the new OnTime.jar and reload or restart your server.

If upgrading from any version earlier than v3.0.3, the config.yml and output.yml files must be updated by hand using the following procedures:

  • New items have been added to the config.yml file.
  1. rename your old config.yml for reference
  2. if you didn't bother with the above step, then delete your old config.yml
  3. restart your server so new config.yml is created
  4. edit the new config.yml as needed (to return to previous settings etc.)
  • Lines have been added to and removed from the output.yml file
  1. rename your old output.yml for reference
  2. if you didn't bother with the above step, then delete your old output.yml
  3. restart your server so new output.yml is created
  4. edit the new output.yml as needed (to return to previous settings etc.)
  1. restart you server again