OnTime V3.13.4

Details

  • Filename
    OnTime.jar
  • Uploaded by
  • Uploaded
    Aug 26, 2014
  • Size
    300.97 KB
  • Downloads
    7,572
  • MD5
    d3a69270bb85d4159554a9bc9f0fe45f

Supported Bukkit Versions

  • CB 1.7.9-R0.2
  • CB 1.6.4-R2.0
  • CB 1.2.5-R5.0

Changelog

V3.13.4

Compiled/Tested with Bukkit 1.7.9-R0.2; Java7; Vault 1.4.1;Votifier 1.9
Fixes
  • Fixed 'array out of range' error when "/ontime rewards" is executed (TIcket #507)
  • Fixed MySQL error seen when sometimes trying to save the 'online-report' (TIcket #497)
  • Fixed issue where 'ontime-data' is created if it is found missing from MySQL database. (TIcket #492)
  • Fixed issue where players online at the time of a plugin reload are logged in twice when OnTime reloads. (TIcekt # 481)
  • Fixed multi-server (e.g. Bungee) support problem where player data was lost or recorded incorrectly when players were OnLine at midnight (No Ticket)
  • Fixed console errors seen sometimes with 'audit logout' function (Ticket #476 & #473)

V3.13.3

Compiled/Tested with Bukkit 1.7.2-R0.3; Java7; Vault 1.2.31;Votifier 1.9
Fixes
  • Fixed another NPE issue of 'null' UUIDs (Ticket #470)

V3.13.2

Compiled/Tested with Bukkit 1.7.2-R0.3; Java7; Vault 1.2.31;Votifier 1.9
Fixes
  • Fixed issue of rapid promotions for votifier-based rewards. (Ticket #458)
  • Fixed NPE issue of 'null' UUIDs (Ticket #465)
  • Fixed problem with 'days on' rewards not scheduled properly (Ticket #437)

V3.13.1

Compiled/Tested with Bukkit 1.7.2-R0.3; Java7; Vault 1.2.31;Votifier 1.9
Fixes
  • Fixed MySQL 'Insert' error prevention storage of new player data. (Ticket #460)
  • Fixed NPE issue on player change world event while server is starting up (No Ticket)

V3.13.0

Compiled/Tested with Bukkit 1.7.2-R0.3; Java7; Vault 1.2.31;Votifier 1.9
Fixes
  • Fixed NPE error in "/ontime rewards recur" command when RewardTags are used. (Ticket #444)
  • Fixed array index error in AFK reporting (Ticket #451)
  • Fixed issue where referral source was not properly stored in the MySQL database. (Ticket #455)
  • Improved OnTime performance in many areas: (Ticket #445)
  • Auto save function
  • Votifier stats and reward processing
  • Player quit events
  • Report generation
Functional Enhancements
  • Added player executable command to purchase from reward shops (Ticket #420)
  • Added ability to disable votifier statistics collection, in support of multiple server environments (Ticket #446)
  • Added option where players will only be eligible for per-world rewards if they are on the world for a specific reward, at the time the reward is issued. Normally rewards are held until the player moves to the right world, but in this case the reward will be discarded if they are "off world". (No Ticket)
  • UUID Support (Phase I)
  • UUID information on players will now be collected and stored (both YML and MySQL methods). In this release the UUID information will NOT be used to verify a player's OnTime record, so if a player were to change their game ID, a new OnTime record will be created. (Ticket #442)
  • UUID can now be added to the output for the "/ontime <playerName>" command. (Ticket #442)
  • Improved handling of corruptions found in the "output.yml" file to help admins diagnose and fix YML syntax errors (Ticket #449)
  • Improved confirmation of reward edit when "/ontime rw refer" and "/ontime rw votifier" are used (No ticket)
New Permissions
  • ontime.rewards.purchase -

When 'true' players will be able purchase 'shop rewards' with the command "/ontime rewards purchase <rewardTag>". Default is 'true', (Ticket #420)

New Configuration Parameters
  • NONE
New Commands
  • ontime rewards purchase <RewardID/RewardTag>
New Output Variables
  • [uuid] - A player's Universal User ID
New Configurable Output
  • NONE

IMPORTANT NOTES on V3.13.x

While v1.7.9-R0.2 is listed as a compatible release, the OnTime V3.13.4 release still does NOT contain full support for UUIDs. The plugin should work and no errors or issues are expected, but with this version if a player were to change their name this would not be discovered by OnTime.

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.13.x is compatible with Bukkit v1.2.5! So Tekkit Classic or other Bukkit v1.2.5 based servers can enjoy the FULL CAPABILITIES of the OnTime and its companion plugins!

OnTime will automatically modify the contents of your config.yml, playerData.yml, and output.yml when you upgrade from any release previous to v3.13.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.