OnTime v3.0.3
Details
-
FilenameOnTime.jar
-
Uploaded by
-
UploadedJul 19, 2012
-
Size151.55 KB
-
Downloads1,104
-
MD5b14cdbda9d31f1e590888e5ee08022e7
Supported Bukkit Versions
- CB 1.2.5-R4.0
Changelog
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
Note: If you are using MySQL for storage of player data and had downloaded and installed 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 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.
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.
- rename your old config.yml for reference
- if you didn't bother with the above step, then delete your old config.yml
- restart your server so new config.yml is created
- 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
- rename your old output.yml for reference
- if you didn't bother with the above step, then delete your old output.yml
- restart your server so new output.yml is created
- edit the new output.yml as needed (to return to previous settings etc.)
- restart you server again