OnTime v3.0.2

Download

Details

  • Filename
    OnTime.jar
  • Uploaded by
    View _ForgeUser8455416's Profile
    _ForgeUser8455416
  • Uploaded
    Jul 17, 2012
  • Size
    151.05 KB
  • Downloads
    471
  • MD5
    c02fed125dd927cedc24f8fa1035f3e1

Supported Bukkit Versions

  • CB 1.2.5-R4.0

Changelog

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

Note: There is a bug in version 3.0.2 that will prevent proper operation with MYSQL storage option, so please only download this version if you will use DAT of YAML options for dataStorage.

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.

If upgrading from ANY earlier version, including v3.0.0, the config.yml and output.yml files must be updated 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