OnTime v3.11.1

Details

  • Filename
    OnTime.jar
  • Uploaded by
  • Uploaded
    Dec 6, 2013
  • Size
    281.65 KB
  • Downloads
    1,908
  • MD5
    59dda5e4f2845900c79f36f01d56bae0

Supported Bukkit Versions

  • CB 1.6.4-R2.0
  • CB 1.6.2-R1.0
  • CB 1.2.5-R5.0

Changelog

V3.11.1

Compiled with Bukkit 1.6.4-R2.0; Java7; Vault 1.2.27;Votifier 1.9
Fixes
  • Fixed issue with hostName length MySQL Error (Ticket #384)
  • Fixed issue with NPE error on player login during server startup or plugin reload (Ticket #384)
  • Fixed issue with OnTime playerData table creation for new servers (Ticket #385)
  • Fixed issue with reward commands not working while OnTime is in suspend mode (No Ticket)

V3.11.0

Compiled with Bukkit 1.6.4-R2.0; Java7; Vault 1.2.27;Votifier 1.9
Fixes
  • Fixed reward.yml ‘rewardIDcounter’ increment problem (No Ticket)
  • Improved handling of “ontime.track” permission (No Ticket)
  • Fixed problem in output of "/ontime" when rewardsEnable and messageEnable both set to false. [Ticket #363]
  • Fixed issue where players sometimes ended up with HUGE playtimes (Ticket #369)
  • Fixed handling of kicked players (Ticket #333)
Functional Enhancements
  • Added ability to use RewardTag in addition to RewardID in all commands
  • Expanded API to provide access to “total points”
  • Added commands to set and modify RewardTags
  • Added “reward shop” capabilities
  • Added ability to set votifier “count” rewards to be single instance only (Ticket #360)
  • Added ability to see RewardTags in “reward list” command
  • Added recommended permission group settings (see below) (Ticket #361)
  • Added collection and storage of player’s hostname upon first login
New/Removed Permission

No permission strings were added, but sets of recommended permissions defaults were created.

  • ontime.player.*
  • ontime.moderator.*
  • ontime.admin.*

(Click here for more information)

The permission group of "ontime.*" was removed becuase it was causing some problems when used incorrectly.

New Commands
  • ontime rewards edit <RewardId> tag=<RewardTag>
  • ontime rewards shop [econ/points] <RewardID/RewardTag> <amount>
Changed/Enhanced Commands
  • ontime rewards add <parameters> tag=<RewardTag>
  • ontime rewards list tags
  • ontime rewards votifier <RewardID/RewardTag> count=xx [perpetual/single]
New Output Variables
  • [balance] - Used to display player's econ balance

IMPORTANT NOTES on V3.11.x

OnTime v3.11.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.

In this release I have also added the concept of a "Reward Shop". Reward Shops allow players to have some control over the rewards they receive by allowing them to spend earned Points or 'coins' (econ system units), on rewards defined by the admin. A 'sign' based shop format is used to provide the player interface, and this requires the use of OnTime's companion plugin OnSign.

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