Bukkit

V3.12.2

Compiled/Tested with Bukkit 1.7.2-R0.3; Java7; Vault 1.2.31;Votifier 1.9

Fixes

• Corrected error in saving vote data in playerdata.yml (Ticket #417)
• Fixed issue where votes rewards not issued properly when votes made on multiple web sites (Ticket #419)
• Fixed issue with player 'online' status tracking when '/ontime reload players' command is executed (Ticket #423)
• Fixed spelling error in AFK message (Ticket #430)
• Fixed issue where vote and referral counts were incorrectly counted in multi-server systems (Ticket #439)
• Fixed issue where JDBC library was not auto-loaded when missing (No Ticket)
• Fixed problem where 'ontime import yml' was not working with new playerdata.yml format (No Ticket)
• Fixed issue with online player report that sometimes resulted in duplicate entries (No Ticket)

Functional Enhancements

• Added 'lastVote' (date) to data set available via OnTime's API (Ticket #424)
• Improved error handling of corrupt playerdata.yml files (Ticket #423)
• Added command so "shop" rewards can be purchased for a specified player via command (Ticket #420)
• Improved online reporting to update based on players in that table (improved performance) (Ticket #410)
• Improved task scheduling for online reports to improve performance (Ticket #410)

New Commands

• ontime rewards purchase <RewardID/RewardTag> <playerName>

IMPORTANT NOTES on V3.12.x

The "online tracking" function DOES NOT WORK properly in a multi-server configuration. If you are using a single OnTime MySQL database to store data from multiple servers, conflicts will arise between the servers, and errors and some server lag may result. Until I can get this corrected, please disable this function on all multi-server systems.

From OnTime/config.yml:

# Enable if Online player status should be tracked in MYSQL Table
onlineTrackingEnable: false

OnTime v3.12.x is compatible with Bukkit v1.2.5! So Tekkit Classic or other Bukkit v1.2.5 based servers can now enjoy the FULL CAPABILITIES of the OnTime and its companion plugins!

I have (hopefully) made reward management easier by expanding the use of the "rewardTag". A "rewardTag" is a string name that admins can assign to each reward they define. Then we executing other commands for that reward they can use the "rewardTag" in place of the "rewardID". "rewardID"s sometimes were confusing because they can change over time as rewards are added and removed, while the 'rewardTag' is fixed and will not change unless the admin changes it.

OnTime will automatically modify the contents of your config.yml, playerData.yml, output.yml and rewards.yml when you upgrade from any release previous to v3.12.0. OnTime will put a copy of your current versions of these files into the plugins/OnTime/backup folder prior to this update, so you can revert back if you find the need to downgrade back to an earlier version of OnTime.

If you are using OnTime V3.9.0 or later with CraftBukkit 1.6.2-R1..0, the definition and use of enchanted items as rewards will not function correctly. There was a change in the CraftBukkit enchantment functions that make it incompatible with OnTime, and I have not had time yet to address this issue.

Please see the release notes page for additional information about changes that have occurred since your last upgrade.

"ontime.*" Permission Group

In v3.11.0 support for the "ontime.*" wildcard permission has been removed. This was causing problems based on how OnTime sometime uses negated permissions. This has been replaced with better defined 'recommended' wildcard permission sets for 'admin', 'moderator', and 'player' roles.

ontime.track Permission

In v3.10.0 a new permission string ("ontime.track") was added, which allows admins to enable/disable OnTime tracking of individual players. When this is set to "false" OnTime will not process players upon login, nor will it create OnTime records for new players. This permission is "true" by default, and most permission plugins will pick up this default setting, and server owners will see no change from previous versions of OnTime. But some permission plugins (e.g. bPermissions, others?) do not pick up the default and treat this as "false" for all players, which effectively disables the OnTime plugin. In this case of such permission plugins, the "ontime.track" should be added to the base set of permissions for all groups whose users are to be tracked by OnTime.