OnTime v2.4.0
Details
-
FilenameOnTime.jar
-
Uploaded by
-
UploadedJun 11, 2012
-
Size108.37 KB
-
Downloads519
-
MD554300fadcc7d58afc3682334bbe21e2e
Supported Bukkit Versions
- CB 1.2.5-R4.0
Changelog
V2.4.0
- Built with CB 1.2.5-R4.0
- Added AFK detection and AFK time deduction from OnTime totals (option)
- Added permission group based rewards. (player must be in a group with right permission to get specified rewards)
- Added option of tracking of OnTime data on monthly basis
- Added configurable console logging messages
- Fixed Null Pointer exception errors seen sometimes on startup and on player login/logout
V2.3.1b
This version is a test only version for certain users having plugin conflict issues and is NOT recommended for general usage.
V2.3.1
( A couple of people have recently asked how to recover potentially corrupt .dat files. The easiest way is to have a backup, so I've made it easier to make sure you have one.)
- Built with CB 1.2.5-R3.0
- Added '/ontime backup' command
- Added automated (daily) backup of .dat files (optional - enabled via config.yml)
V2.3.0
- Built with CB 1.2.5-R2.0
- Added XP reward type
- Added configurable output for '/ontime' and '/ontime <playername>' commands
- Added configurable output when rewards are issued
- Added configurable headers for Top XX lists
- Cleaned up output in Top XX lists to make it easier to resd
- Change 'Top xx' command syntax to make it easier to use weekly/daily data
- Added Individual Rewards
- Added Individual Reward commands:
- ontime rewards indi
- ontime rewards set
- ontime rewards delete
- Fixed Errors:
- [SEVERE] errors seen when OnTime Rewards are disabled and players log in
- Other 'null pointer' issues when OnTime Rewards are disabled.
- Wrong file path name on non-Windows servers
V2.2.1
- Fixed sync problem with permission plugins during server startup
This problem was seen with PEX, and resulted in permission rewards malfunction
- Fixed error in HTML formatted daily/weekly reports where 'total time' was always "N/A"
- Fixed error with kick events
With this error players were sometimes getting hours worth of OnTime credit when kicked.
V2.2.0
- Added HTML option for report output
- Added weekly (vs daily only) option for short-term tracking
- Added '/ontime today <#>' and '/ontime week <#>' commands
- Added enable/disable of reward messages to players
- Fixed error with recurring rewards when inventory full
V2.1.1
- Fixed problem with Group rewards failing for permissions-bukkit and zpermissions
- Fixed wrong 'new total time' output on 'set total' command when executed on online players
V2.1.0
- Built with Bukkit 1.2.5-R1.0
- Added recurring rewards
- Added permission rewards
- Added 'set days' command
- Changed 'set' command to 'set total'
- Added 'reward recur' command
- Added 'reward single' command
- Added support of Vault for Group and Permission rewards
- (expanded group support from Essentials GroupManager only in R2.0.x)
- Removed 'refresh' command
- Fixed 'days on' counter problem
V2.0.1
- Improved handling for servers without Essentials GroupManager
- Prevention of in-game 'add' of group rewards
- Check for GroupManager before trying to schedule or issue 'group' rewards (will prevent unhanded null exceptions seen in v2.0.0)
- Improved console messaging on OnTime startup if GroupManager is not present
- Added Log entries of admin use of 'remove', 'set' and 'add' (OnTime) commands (level 3)
V2.0.0
- Build with CB 1.2.4-R1.0
- Tested with servers running CB 1.1-R6, CB 1.2.3-R2.0, & 1.2.4-R1.0
- Added GroupManager Change rewards
- Added MC Item rewards
- Added 'set' and 'add' commands
- Added more information to '/ontime <userid>' display
- Added OnTime data update on player 'kick'
- Fixed 'TodayData.dat' corruption error
When upgrading from all previous versions, including V2.3.0
- The rewards.yml format has been modified. Old versions will automatically be updated to the new version, but it is a good idea to backup your old >rewards.yml before starting the new version the first time.
- 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.)
- New lines have been added to 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