OnTime
OnTime
Now every MineCraft server can track the playtime (current login, daily, weekly, monthly, and all time) for all players with this powerful, full function plugin. With OnTime a “top 10” list can be generated in game, current and total playing statistics can be displayed (also in game), and daily/weekly/monthly reports of all players can be generated and viewed (off line).
Administrators can define OnTime Rewards which will result in econ amounts, items (including enchanted items and potions), item kits, group add/delete, group promotion/demotion, permission grant/denial, command executions, loyalty points, personalized messages, and XP to be automatically issued to a player when they have achieved a specified amount of daily, weekly, monthly, or total playtime on the server.
Rewards can also be issued when players refer other players to the server, voted for the server, played for a specified number of different days, been absent from the server for a specified number of days, shops with their accumulated points or wealth, upon player's death, or they achieve status as a top player. A built in Votifier Listener makes issuing of rewards for web-site voting a snap. Vault is used so OnTime Rewards and permissions are supported by multiple economy and permission plugins.
SUBSCRIBE TO GET LATEST UPDATES
Don't forget to subscribe to OnTime to make sure you are automatically made aware of OnTime updates,which will give you the link to download the latest version even before it is approved by BukkitDev moderators!
Plugin Notes
IMPORTANT NOTES on V4.1.4
Recompiled V4.1.3 using Spigot API for MC 1.9. No other changes or fixes
IMPORTANT NOTES on V4.1.3
The new outputs for vote and refer daily, weekly, monthly totals are not automatically added to the "/ontime <player name>" display. If you want to see this data, then you will need to edit the "output.yml" file.
IMPORTANT NOTES on V4.1.2
- The primary purpose of this update was to address some lingering issues with duplicate MySQL records created when a player changed names.
- In addition to address some base code issues, the "/ontime uuid merge" command was modified to require that one or two player names, or the keyword 'all' be provided when using this command. If a single player name is provided with the command any records with the same UUID as that associated with the provided name will be combined into a single record. The player name associated with that UUID will be the name specified in the command. If 'all' is specified OnTime will merge all records found for each unique UUID..
- If two player names are specified in the command then records containing those two player names will be merged into a single record, and they will be associated with the second player specified and its UUID.
- A new configuration parameter has been added to have ontime auto merge duplicate player records for a given UUID, upon the next login of player seen using such UUIDs. It is recommended that this method be used to correct the duplicate record issue over the 'merge' or 'clean' commands.
- Caution should be taken when the 'ontime uuid replace' and 'ontime uuid merge all' commands are used on systems with large player databases. It may take a very long time for these commands to complete, and should only be run at periods of low player traffic. While these command are running, all OnTime functions will be suspended and players will not receive playtime credit; they will not receive rewards; and votes etc. will not be counted.
- There are still some significant issues with OnTime working properly when 'multiServerEnable' is set to TRUE. It is recommended that until I get these issued addressed that this OnTime function not be used.
IMPORTANT NOTES on V4.1.1
This update fixes issues with duplicate UUID records created when player's change names. This fix will address all future changes but does not directly address the existing duplicates. For this I have extended the "uuid" commands to include an option that will 'merge' the duplicate records into a single record. Please see HERE for more information on the "uuid" command, and specifically the "merge" keyword.
Prior to upgrading to OnTime V4.1.x you MUST have already upgraded to OnTime v3.13.4. Attempting to upgrade from any version prior to V3.13.4 will not properly auto update any of the OnTime YML configuration files. So if you are using any version prior to v3.13.4, load that version first into your plugin directory, restart your server or re-load your plugins, then replace with V4.1.x and do another server restart or plugin reload.
IMPORTANT NOTES on V4.1.x
This version of OnTime contains a significant software re-write in order to be compatible with MineCraft V1.8, with support for UUIDs, and changeable player names. This version was fully tested with Spigot/Bukkit v1.8.1, and this will be the primary MIneCraft server base supported. OnTime V4.1.x will NOT WORK with Bukket v1.25 nor Tekkit classic. It should still work with the last Bukkit releases (1.7.2 / 1.7.9 ), but no significant testing has been done with these releases, so servers using those versions are better off using the latest OnTime V3.x release.
The "online tracking" function still 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 will automatically modify the contents of your config.yml, playerData.yml, and output.yml when you upgrade from any release previous to v4.1.x. 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.
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 was 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 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.
Online Support
If I am online you may find me here for IRC
bpermissions plugin compatibility
- If you are going to use OnTime rewards, make sure that the "groups:" keyword is set to "- all" instead of "- global" when using bPermissions.
- Make sure to add the permission string "ontime.track" to your base group, or all groups for which you want tracking enabled.
Integration with AFK Terminator
I have an independent plugin "AFKTerminator" that detects and potentially eliminates AFK Machines. An "AFK Machine" allows a player to avoid "AFK" detection through continual movement. See the [|Other Function] page for more details.
Integration with OnSign
There is a second companion plugin for OnTime, which I have named OnSign. OnSign allows players to create MC signs that will show a player's current online/offline status, time of last login/logout, and their daily/weekly/monthly and total scores for playtime, votes, and referrals. With OnSign you can also create signs showing the "top" players for playtime, votes, and referrals. With OnSign v1.3.0 or later OnSign supports signs that interact with the OnTime Shop rewards, allowing players to pick their own rewards by spending Points or 'coins'.
OnSign and OnTime version compatibility
- OnTime v3.8.1 or earlier will work with OnSign v1.0.0
- OnTime v3.8.2 - v3.9.0 will work with OnSign v1.1.0
- OnTime v3.9.1 - v3.10.3 will work with OnSign v1.2.0
- OnTime v3.11.0 or later will work with OnSign v1.3.0
- OnTime v4.1.x or later (may work with OnSign v1.3.0 (I have not tested this yet, but it should still be working)
Automated Update Check
OnTime performs an automated check to see if there is a new version of the plugin available for download. It will NOT download new versions, but simply notify the server administrator that one exists via console messages. By default, this function is enabled, but can be disabled by setting "updateCheckEnable" in the OnTime/config.yml to 'false'.
Features:
(Items in BOLD are new in the latest 4.1.x release of OnTime)
- ^Player Statistics
- Display your own OnTime data: (configurable) plugin default: current login, daily, weekly, monthly, and total time on the server
- Display anther player's OnTime data: (configurable) plugin default: days since first login, different days on server, current login time, AFK status, AFK time for login, today, week and month; current day, week, and month play time, total OnTime, points accumulated, econ balance, next OnTime reward(s), and voting and referral statistics.
- Display player's total, daily, weekly, and monthly playtime on a per-world basis, in addition to the standard per-server basis
- Display all online players’ current session and total time
- Display ‘top #’ players, ranked by play time
- Display ‘top #’ players, ranked by total time for the day, week, and month
- Display 'top #' players, ranked by total points
- Display 'top #' players who have voted for your server for today, week, month or total
- Display the 'top # sites' to see where the votes are originating
- Display the 'top #' players who have referred other players for today, week, month or total
- Display the 'top #' players who are logging AFK time on your server for today, current week, and current month
- Display list of players referred by a specified player.
Rewards
- Define rewards issued to players for their time played on the server:
- Cash! (Economy)
- MineCraft Items
- Enchanted Items
- Potions
- Item sub-types (e.g. Chiseled Stone)
- MineCraft Item Kits
- Permission Group Add/Remove
- Permission Group Promotion/Demotion
- Give Permissions
- Take Away Permissions
- Execute (almost) any command
- XP (experience points)
- 'Loyalty' Points
- Send a message
- Issue Rewards based on daily, weekly, monthly, or total playtime. For the server, or unique rewards per-world.
- Define Econ, Item, Command, and XP rewards as recurring or perpetual
- Define rewards for referring new players to the server
- Define reward to be issued when a player identifies who referred them.
- Define rewards to be issued when players vote online for your server (via Votifier)
- Define rewards to be issued when a player has been absent from the server for a specified number of days
- Define rewards to be issued when a player dies
- Define rewards that players can purchase using Points or 'coins'
- Definition of Individual (or indi) Rewards, which can be issued to a specific player at a specified future time.
- Issue some rewards to only members of certain permission groups. e.g. donors
- Issue rewards to the 'top' playtime, points, voting, or referring players daily, weekly, monthly, and/or overall total
- Give ‘temporary’ rewards such as rank/group memberships or permissions
- Enable/disable display of 'reward issued' messages to all players
- Enable/disable display of ‘reward issued’ messages on a per-reward basis
- Customize displayed ‘reward issued’ message on a per-reward basis
- Broadcast a message to all Online players when someone else receives a reward. (Good way to advertise rewards issued for voting and referring players.)
- Display of the next rewards to be issued to all online players
- Ability to suspend issue of rewards while a player is AFK.
- Define rewards that are only issued when player is in a specified world
- Make purchase of a 'shop' reward for a specified player via admin command
- Make a purchase of a 'shop' reward by a player for themselves
Messages
- Pre-define messages that can be issued to players at login, or based on time
- Define messages adhoc (on the fly) that can be issued to players at login, or based on time
- Assign customized messages to be displayed when rewards are issued
- Send a message to a player based on play time (daily, weekly, monthly, or total play time)
- Define 'welcome' messages to the player, and server announcements on player's login showing OnTime data
- Enable/Disable server broadcast announcements per player via permissions node
- Manage messages set via edit of .yml file or in-game/console add/remove/list commands.
Manipulate a Player's Data
- Manually add a player to the OnTime database
- Set a player's total OnTime
- Set a player's number of different days on server
- Set a player's first login to the server date
- Set a player's total points
- Add or subtract time to/from a player's total OnTime
- Add or subtract points to/from a player's total points
- Remove a player from the OnTime data files
- Configure plugin to exclude players time 'AFK' from total and daily/weekly/monthly calculations
- Import player names and their total OnTime (play time) data from YML files, OnTime Reports, or LogBlock plugin.
- HTML, TXT, and MYSQL Report format options
- Generate a report file of all players total time and time stamp of last login event
- Generate a report file of all players time on your server today, for the week, or for the month
- Generate a report of player's AFK time daily, weekly, and monthly
- Configure the 'first day of the week' for weekly reports
- Configure the 'first day of the month' for monthly reports.
- Auto generation of total, daily, weekly, and monthly reports
- Auto purge/delete of old report files/tables you no longer want
- Generation of an 'OnLine Report' which stores an admin defined set of data for all online players to a MYSQL table
Manage The OnTime Plugin
- Find missing UUIDs by importing from Mojang's servers
- Automated detection of the availability of a new version of OnTime
- Select method for storing the OnTime player data: .yml files (default), or MySQL database
- Auto-purge inactive or players with low total OnTime from the data files
- Execute admin defined commands when players are purged from the OnTime data files.
- Scheduled saves of OnTime data to disk
- Auto update of all online players data, file save, and data purge on server shutdown/reset
- 'test’ commands to simulate login/logout events; creating fake OnTime records; test daily reports; test votifier rewards
- Logging of OnTime auto purge activity, player login and quit events, and reward system events
- Manual and Automated Generation of Backup versions of OnTime '.dat' files.
- Import playername and total OnTime data from a .yml file.
- Importplayername, total OnTime and last login data from the 'logblock plugin' MySQL database.
- Configure OnTime Report file names and location
- Administrator defined "help" information that players can easily access.
- Suspend/Resume all OnTime activity while administering rewards or other OnTime data manipulation
- Enable/Disable/Configure OnTime LogFile and Console data in game or from the console
Other Plugin Integration
- Use of Vault for support of multiple economy and permission plugins [REQUIRED]
- Integration with Vault Permissions for group changes and permissions add
- Import playername, total OnTime and last login data from the 'logblock plugin' MySQL database.
- Issue rewards when players vote for you server on website which also support Votifier.
- Integration with "AfkTerminator" for discounting time spent AFK while using an AFK Machine
- Integration with OnSign, to display player information, top players, build Reward shop, all on user defined signs.
- API: OnTime offers an APIto allow other plugin integration with access to OnTime's collected data for player's time on the server, votes, and referrals.
- Execute other plugin console commands when players are auto-purged by OnTime
Please see the pages for permissions, configuration, commands, etc.
Installation
- Place ontime.jar in your plugin folder
- Download vault.jar and place that also in your plugin folder
- (Option) Download a Vault supported permissions plugin and place that in your plugin folder
- (Option) Download and install the AFKTerminator plugin
- (Option) Download and install the OnSign plugin
- (Option) Download and install the votifier plugin
- Modify permissions groups to enable OnTime functions. (click here for permission nodes)
- Reset your server
If the optional Permissions plugin is installed: - Edit /plugin/ontime/rewards.yml, listing the permissions groups from lowest to highest under the 'groups:' keyword
If the optional commands rewards are to be used: - Edit /plugin/ontime/rewards.yml, defining the commands that can be 'rewarded' under the 'commands:' keyword
If the optional 'kit' rewards are to be used: - Edit /plugin/ontime/rewards.yml, defining the kits that can be 'rewarded' under the 'kits:' keyword
If the optional MySQL database is to be used to maintain the player data: - Edit the /plugin/ontime/config.yml, enabling the use of mysql and setting up the definition of the MySQL database.
If the you want to change the output the plugin sends a player: - Edit /plugin/ontime/output.yml, following the instructions found in that file.
If the optional OnTime Messages is to be used to displayed timed messages to players: - Edit the /plugin/ontime/messages.yml, to add any pre-defined messages you need. (editing this file is not required to use this feature.)
- If the config.yml, output.yml and/or rewards.yml have been modified, then you must reload this data with the command "/ontime reload all"
Future Enhancements Under Consideration
- See BukkitDev Tickets tab for OnTime
Feature Requests:
If you want to request a feature to be added to this plugin, or you think any of the above should be given a higher priority, please submit a ticket or vote for existing ones.
Please Leave Comments
I'd love to hear what you think (good and bad) about this plugin. It will help me know if it's worth keeping up on the maintenance. Thanks. Edge
Change Log
For a more detailed change log, see here.
V4.1.4
Compiled/Tested with Spigot/Bukkit V1.9; Java8; Vault 1.5.2; Votifier 1.9
- Recompiled V4.1.3 using Spigot API for MC 1.9. No other changes or fixes
V4.1.3
Compiled/Tested with Spigot/Bukkit V1.8.1; Java7; Vault 1.5.2; Votifier 1.9
Fixes
- Fixed problem with "indi" rewards info listing time as "9999 days" instead of "(individual)" in reward info display (Ticket #543)
- Fixed issue where votifier rewards could end up with a 9999 day delay, if redefined from an indi to votifier reward (Ticket #543)
- Fixed lingering issue with race condition between login and changeWorld events on servers with dedicated 'spawn' worlds. (No Ticket)
Functional Enhancements
- Added ability to display daily, weekly, and monthly totals for votes and referrals to the "/ontime <player name>" output. (Ticket #541)
New Output Variables
- [dailyVotes] - Display a players vote total for the current day
- [weeklyVotes] - Display a player's vote total for the current week
- [monthlyVotes] - Display a player's vote total for the current month
- [dailyRerfer] - Display a players referral total for the current day
- [weeklyRefer] - Display a player's referral total for the current week
- [monthlyRefer] - Display a player's referral total for the current month
V4.1.2
Compiled/Tested with Spigot/Bukkit V1.8.1; Java7; Vault 1.5.2; Votifier 1.9
Fixes
- Addressed additional issues with duplicate UUID records created when players change names (Tickets #537, 539)
- Fixed issue where race condition could happen between change-world and join player events on servers with 'spawn' worlds. (No Ticket)
- Fixed issue with "multiServerName" set to invalid value by OnTime autoupgrade (Ticket #536)
Functional Enhancements
- Expanded "uuid" command to support merging of specified player records
- Added auto merge function, to take care of merging player records (same UUID different player name) on login (MySQL only)
- Updated API for compatibility with new v2.0.0 of OnSign
New Permissions
- None
New Configuration Parameters
- uuidMergeEnable: (Default False) - If 'true' OnTime will automatically merge player records if there are multiple records for a single UUID but different player names.
Modified Commands
- ontime uuid [merge] <playername 1> {<playername 2>}
Merges player records to create a single record. Valid for both MySQL and YML dataStorage
New Output Variables
- None
New Configurable Output
- None
V4.1.1
Compiled/Tested with Spigot/Bukkit V1.8.1; Java7; Vault 1.5.2; Votifier 1.9
Fixes
- Addressed issue with duplicate UUID records created when players change names (Ticket #537)
- Fixed issue with daily report SQL syntax error (No Ticket)
- Fixed issue with online report NPE when logging enabled at level 1 (No Ticket)
- Addressed issue where player's total time could not be set to zero, and where current login time was always added to any set value. (Ticket #534)
Functional Enhancements
- Added new 'uuid' command that merges multiple UUID records into a single record (sums times, picks oldest first login, newest playerName, etc.)
- Added support for negative econ (a.k.a. tax) reward (Ticket # 532)
New Permissions
- None
New Configuration Parameters
- None
New Commands
- ontime uuid [merge]
Helps manage UUIDs in the OnTime database. Merges duplicated UUID records, into a single record.
New Output Variables
- None
New Configurable Output
- Rewards: tax - This output is used when negative econ (a.k.a a tax) is imposed on a player
V4.1.0
Compiled/Tested with Spigot/Bukkit V1.8.1; Java7; Vault 1.5.2; Votifier 1.9
Fixes
- OnTime's config.yml has been restructured to make it easier to find elements within (No Ticket)
- Fixed output backup function which was not working previously (No Ticket)
- Fixed issue where players added with "/ontime add player" command were auto-purged on start of next new day. (No Ticket)
- Fixed MySQL 'backup' methodolgy (No Ticket)
- Fixed 'Help' file processing that generated errors in OnTime logfile during at plugin startup (No Ticket)
Functional Enhancements
- UUID Support (Phase II)
- UUIDs missing for players already in the OnTime database, can be imported from Mojang if available
- UUIDs are now used to distinguish players
- If a player changes names, the new name will be auto associated with the UUID, no playtime etc. will be lost
- If a player tries to login with a player name already associated with a UUID found in the OnTime database, the new UUID will not be tracked. This will prevent confusion in the server of having two players with the same player name (at least from an OnTime perspective)
- Command added to help manage UUIDs in OnTime's database
- Added per-world tracking and rewards.
- The time a player spends in each world on the server is now tracked in addition to the total time spent on the server. This includes total, daily, weekly, and monthly times.
- Per-world rewards are improved because it is based on the time spent in the world, not just issued in a particular world based on total server time.
- Improved "AFK" with instant detection when back from AFK
- Removed requirement that a space " " be inserted in some configurable output strings
New Permissions
- None
New Configuration Parameters
- MySQL:multiServerTable - Default = ontime_multiserver
- perWorldEnable - Default: false
New Commands
- ontime <other> <worldname>/[ALL] - see player's time in a particular world, or for all worlds
- ontime uuid [CLEAN | FIND | PURGE | REPLACE]
Helps manage UUIDs in the OnTime database. (Please read command details before using these as records could be lost unintentionally)
New Output Variables
- None
New Configurable Output
- dateNotAavailabe: Used when a date/time piece of data is not found.
-
View User Profile
-
Send Message
Posted Sep 5, 2013The votifier link in the install steps is dead.
-
View User Profile
-
Send Message
Posted Sep 5, 2013How can i make a reward that only players with a specific permission will get it?
-
View User Profile
-
Send Message
Posted Sep 1, 2013@Edge209
1. I was going to deliver the same effect by using another plugin to run a command for a player. For example, with essentials, "/sudo <player> referred by none". I am fine with either method as long as it gives the same result.
2. I did set a time limit to half an hour (well past any possibility of referring someone) so there is no need (at least personally) to check for the permission. Anyone who would have the permission would be past the time limit already. Adding another check to the command will decrease performance for all users, and will probably only end up helping a few people switch systems. If you were to add it, I would at least add a way to disable it so everyone does not need to see the performance decrease (no matter how small it may be).
On a side note, I find it a bit annoying that I have to update the groups: field of the rewards.yml every time I change permissions. I needed the feature when I first started using the plugin to prevent high ranking players to be deranked from a play time reward, but now I have no use for it. I suggest that if the plugin detects a permission group not on the list, it just tacks it on to the end. So if I create a new group "prisoner" it would add it automatically to the end of the list.
-
View User Profile
-
Send Message
Posted Sep 1, 2013@gustebeast
So, you are willing to trust that the players will actually say "none" instead of claiming someone to get another reward?
I understand your need to have a way to convert from permissions to MYSQL tracking methods, but can think of a couple of other options.
1. Create a command similar to your idea, but have it be something that an admin/moderator can execute. "/referred deny <playerName>"
2. Create an automated function that will check that if MySQL is enabled for "referred" tracking but comes back negative, before proceeding it would also check the permission string and if it is there then update the MYSQL to be consistent. This would only work as players log into the system, so you would have to leave the permission strings in there for some time until you think you all of your current players have been on the system. In this method any new "referred by" would use the MYSQL and not create any new players with the permission string.
What do you think?
-
View User Profile
-
Send Message
Posted Sep 1, 2013Could you add this command.
"/referred by none"
I am switching over to MySQL from the permissions based system and I need a way to mark players as not referred. After a user types this command they will not be able to claim a referrer.
-
View User Profile
-
Send Message
Posted Sep 1, 2013@Edge209
Okay good to know. ^.^ Looks like it's going through for players who have logged in after the reward was created, so I know it's working. Just wanted to make sure something wasn't wrong.
Thanks so much!
-
View User Profile
-
Send Message
Posted Sep 1, 2013@sakura_blades
Hi, OnTime keeps no record of who has received a specific reward, so anyone that has already passed the time of the reward when it is created will not receive the reward. Sounds like this is what you are seeing, so it's all good.
-
View User Profile
-
Send Message
Posted Sep 1, 2013So I set up a daily login reward:
/ontime rewards add econ 75 20m daily
And it doesn't seem to be working? So unless it's not going to reward players who have already met the requirement for 20m today, and will reward everyone else who wasn't online before/when I created the reward.... I think there's something up with it?
please help? :\
-
View User Profile
-
Send Message
Posted Aug 31, 2013@MineLab
In this case the exclusive will not matter because the 'demotion' reward is linked only to that promotion, so it will only be applied to someone who is VIP.
No, this won't work for someone who is VIP, but you can schedule the demotion manually with the command: " /ontime rewards set 2 real <playerName> 30d"
-
View User Profile
-
Send Message
Posted Aug 31, 2013@Edge209
Okay thanks that what i need :)
But is it usefull to do that "/ontime rewards exclusive 2 add VIP" ?
And, is this (the demotion) will work for people that are already VIP ?
~ sorry for bad english
-
View User Profile
-
Send Message
Posted Aug 30, 2013@MineLab
If I understand your question, you want someone with a VIP rank to be returned back to a DEFAULT rank after 30 days. If this is right, the answer is yes. Please see this tutorial for instructions on how to do this. You will also want to read the tutorial about setting up basic promotions, as some of the initial configuration settings needed will be found there.
http://dev.bukkit.org/bukkit-plugins/ontime/pages/tutorials/5-advanced-rewards/#w-temporary-rank
in your case I think the commands you want to execute are:
Basic Promotions: http://dev.bukkit.org/bukkit-plugins/ontime/pages/tutorials/3-auto-rank-group-promotions/
-
View User Profile
-
Send Message
Posted Aug 30, 2013This plugins seems to be pretty cool :)
But i have a question: can I configure it so that VIP are DEFAULT after a month (30 real days) ?
-
View User Profile
-
Send Message
Posted Aug 28, 2013@crunkazcanbe
You can open a ticket and I will look at it eventually, but to be honest it may be awhile until I get to it because I think it is out of my direct control. It would be helpful though to you if you also approach the PEX team to see if they perhaps can provide some idea about what is going on.
-
View User Profile
-
Send Message
Posted Aug 28, 2013@Edge209
Do you plan on trying to figure this error out and releasing a new update ? I mean everything is running fine but its just kind of a OCD type thing to where I don't like seeing any errors in the console on start up or shut down . ;) It only happens when I shut down and there are players still on .
-
View User Profile
-
Send Message
Posted Aug 28, 2013@geekyservers
I'm not sure why the command would not work for an OP'd player, and even more baffled why it does not work on console. Try giving your player the permission "ontime.moduser" and then try the command "/ontime set first <playername> <dd>D" again.
-
View User Profile
-
Send Message
Posted Aug 28, 2013@crunkazcanbe
It looks like OnTime is trying to take care of some online players during the shutdown, but PEX has already been disabled when OnTime checks some permissions. I've not seen this happen before and I don't have any ideas at this point if there is something I can do to fix this since bukkit controls the order of plugin enable/disable. This could have an adverse affect on player's who are online at the time of the shutdown, as their OnTime records may not get updated properly.
-
View User Profile
-
Send Message
Posted Aug 27, 2013@Edge209
Thanks! I tried using many variances as an OP'd user / even the console:
/ontime set [days/first/total] <player name> {<dd>D} {<hh>H} {<mm>M}
'set days' will set the player's different days on to the number of days specified by <dd>D 'set first' will set the player's fist login timestamp to be <dd> days prior to the current day. Time will be set to midnight. 'set total' will set the player's Total OnTime to the time specified by <dd>D=days, <hh>H=hours, and <mm>M=minutes.
-But I keep getting told I have no permission to do it. Is there another way?
-
View User Profile
-
Send Message
Posted Aug 27, 2013@Edge209 that helped man everything is working smooth now i actually figured that out on my own lol but idk what this error is when i stop my server everything is running smooth though
I get this everytime i stop the server
11:41:01 PM [INFO] [OnTime] Disabling OnTime v3.8.7 11:41:01 PM [SEVERE] Error occurred while disabling OnTime v3.8.7 (Is it up to date?) 11:41:01 PM ru.tehkode.permissions.exceptions.PermissionsNotAvailable: Permissions manager is not accessable. Is the PermissionsEx plugin enabled? 11:41:01 PM at ru.tehkode.permissions.bukkit.PermissionsEx.getPermissionManager(PermissionsEx.java:194) 11:41:01 PM at net.milkbowl.vault.permission.plugins.Permission_PermissionsEx.playerHas(Permission_PermissionsEx.java:209) 11:41:01 PM at net.milkbowl.vault.permission.Permission.playerHas(Permission.java:136) 11:41:01 PM at me.edge209.OnTime.PermissionsHandler.playerHas(PermissionsHandler.java:94) 11:41:01 PM at me.edge209.OnTime.AwayFK.update(AwayFK.java:352) 11:41:01 PM at me.edge209.OnTime.PlayerEventListener.logoutPlayer(PlayerEventListener.java:306) 11:41:01 PM at me.edge209.OnTime.OnTime.onDisable(OnTime.java:185) 11:41:01 PM at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:219) 11:41:01 PM at org.bukkit.plugin.java.JavaPluginLoader.disablePlugin(JavaPluginLoader.java:481) 11:41:01 PM at org.bukkit.plugin.SimplePluginManager.disablePlugin(SimplePluginManager.java:401) 11:41:01 PM at org.bukkit.plugin.SimplePluginManager.disablePlugins(SimplePluginManager.java:394) 11:41:01 PM at org.bukkit.craftbukkit.v1_6_R2.CraftServer.disablePlugins(CraftServer.java:281) 11:41:01 PM at net.minecraft.server.v1_6_R2.MinecraftServer.stop(MinecraftServer.java:349) 11:41:01 PM at net.minecraft.server.v1_6_R2.MinecraftServer.run(MinecraftServer.java:445) 11:41:01 PM at net.minecraft.server.v1_6_R2.ThreadServerApplication.run(SourceFile:582)
-
View User Profile
-
Send Message
Posted Aug 27, 2013@crunkazcanbe
You are really close. Your mistake is that the reward times are not relative to those before them, but to the total time played.
The way you have it now is you are rewarding all three levels after the first minute of play, and hence the player ends up in the highest level at the end.
So if you want a promotion to each group, but one minute apart starting with the first minute, then these are the commands you need to run:
-
View User Profile
-
Send Message
Posted Aug 27, 2013OK I have it to where I get promote in 1 min on each promotion but it isn't working with my 4 ranks . They are as following
Basic-1
Basic-2
Basic-3
Basic-4
I typed /ontime rw add promotion Basic-2 1m
/ontime rw add promotion Basic-3 1m
/ontime rw add promotion Basic-4 1m
When I get promoted I get all the promotion messages saying
You have been playing for 1 minute and 18 seconds
You have been promoted to Basic-2
You have been promoted to Basic-3
You have been promoted to Basic-4
Why does the 1 minute I wait for to be promoted skip me straight to Basic-4 group ?
I want to wait 1 minute before each promotion. Am I typing the commands wrong ?
@EDGE209
jmw408352 is prob having the same problem as me . BTW If you want to know I'm using pex . I was using AutoRank but was having problems with it so i came to this and now I'm having problems with this and before I get asked yes I have all the groups listed in the right order in the config file . This is super annoying I have yet to find a ranking plugin based on time work correctly .