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 Aug 14, 2012Is it possible to get the players on WhiteList time and have promotions based around that?
-
View User Profile
-
Send Message
Posted Aug 14, 2012@GmK1 It is working correctly, it just looks wrong because of how the whole thing functions.
When the command is executed, a 'reward' for the "referred by" is scheduled for the target person, because it is his playtime that needs to be tracked. Once he hits the required amount of time, that 'referred by reward' gets converted into a 'has referred" reward for the player that made the referral. When this happens the person that was referred does not receive anything. He will only receive something if a referral target reward is also set up.
So, hang tight until the person that was referred his the target time and you will see that everything works as you think it should.
-
View User Profile
-
Send Message
Posted Aug 14, 2012I might be doing something very wrong, but when setting up Referral rewards exactly like you wrote in the example tutorial, the person who writes the /referred by command gets *all* the money, in their ontime list it mentions them both as reffered by target and the other one.
Any hints where to check what could be wrong?
-
View User Profile
-
Send Message
Posted Aug 12, 2012@xTitanCraftx
I understand, but I'm not going to be able to help you. Vault is the key to supporting the largest number of Bukkit servers, and it would be difficult to create and support multiple versions of my plugin. Sorry about that.
-
View User Profile
-
Send Message
Posted Aug 12, 2012@Edge209
Because Im just hosting a popular server on my laptop and I only have 2 Gb Ram and I already have 18 plugins and it is all only for the server , Then if i add vault plugin my server will be lag so much due to many plugins and my ram cant take it anymore D: and then I have to add your plugin so I will have 20 plugins it will cause me lag ,more again , Im just asking Mr.Owner .
If you could help I will appreciate it
-
View User Profile
-
Send Message
Posted Aug 11, 2012Thanks will test it. Looking forward to the final tutorial.<<reply 866643>>
-
View User Profile
-
Send Message
Posted Aug 11, 2012@rossyell
Rossyell,
Looks like your rewards.yml is in good shape for basic promotions to citizen and builder, and as long as these groups are defined in bpermissions, I would expect it to now be working for you.
I agree with your 'overwhelming' comment. I have a tendency to want to be exact and complete in my explanations, and this can lead to a situation where "more is less". I will keep working on fixing this.
Regarding your need to make a game mode change, I don't know if this is possible with bpermissions configuration, but I do know it can be done with OnTime Rewards, and you are on the right track by looking at the 'commands' section.
1. Edit your rewards.yml and add a 'survival command'. It should look like this:
2. Start/Restart server or reload (/rl) plugins
3. Execute the following command:
ontime rewards add command 0 2 0 survival
4. Done!
-
View User Profile
-
Send Message
Posted Aug 11, 2012Thanks - I think I have managed to get it working with some silly examples more to test than to keep in permanently - but pushing off to bed now as early morning so will wait feedback from my closed group of users tomorrow evening and refine both it and my bPermissions.
I will also try and think of a way to clarify your explanations - that in hindsight are probably more overwhelming than complex, and not much helped by the examples or the yml files. <<reply 866392>>
As requested the post of the current dumbed down rewards file is below:
# 'version' below is the version of this YML file. DO NOT CHANGE THIS
#
version: 5
#
#
# Do no modify the following
rewardIDCounter: 6
#
groups:
- default
- citizen
- builder
- moderator
- admin
#
commands:
#
rewards:
- S,A,0,1,0,0,0,0,I,50,DIAMOND,S2I50DIAMOND
- S,A,0,1,0,0,0,0,G,1,citizen,S4G1citizen
- S,A,0,8,0,0,0,0,X,1000,XP,S3X1000XP
- FT,A,1,0,0,0,0,0,I,2,STONE,S0I2STONE
- FS,A,1,0,0,0,0,0,I,20,PORK,S1I20PORK
- S,A,4,0,0,0,0,0,G,1,builder,S5G1builder
I am still puzzling over a bit of MC/ bPermissions/OnTime interaction. I have now set my server to start my users in adventure mode (2) so they can look around first and ensure the macontents get bored and go and grief elsewhere. I effectively need to promote them to survival mode after two hours and am not sure if my bPermissions file will let me do that once I refine it. What puzzled me was one of the examples:
commands:
# - creative:'creative [player]' NOTES: The (') around the string are REQUIRED & there should be no space before
# - kill:'kill [player]' or after these (') marks; [player] will be replaced
# with the target player's name when executed
#
I have probably missed the explanation somewhere. Any further info ? Can/ should I be changing my default users to survival in the rewards file as opposed to mucking around in my bPermissions config ?
Thanks once again.
-
View User Profile
-
Send Message
Posted Aug 11, 2012@rossyell
I'm trying to make it less confusing, so please keep the feedback coming.
1. You do not want to remove any of the comment markers in the YML files.. The plugin automatically fills in any missing sections. The best way to start the whole process is to run your server with no /ontime/rewards.yml file, letting the plugin generate a clean, blank template, and the go and edit that file. I will make note of this in the tutorials.
The entire top portion of the rewards.yml file with all the comment markers, was intended to be documentation plus a sample yml. The 'real' yml does not begin until the very bottom, and ( here is where the confusing part starts) the version I have posted to these bukkitdev pages only shows the first 'do not change' part, it does not include the group, rewards, or command section headers.
2. You must define all of your groups within your permissions plugin. So if Citizen is not found inside of bpermissions configuration files, then OnTime will spit out the error you see. ( Please ignore the 'groupmanager' part of that error message, it should have said bpermissions .)
3. It is a great suggestion that I post up sample config files to go along with the tutorials, and I will do that shortly
4. Can you repost your rewards.yml and use 'plain text' instead of wikicreole, so it better shows exactly what you have in that file.
5. I am going to spend some more effort to clean up this process to make it more clear, as you are not the only one I have confused.
-
View User Profile
-
Send Message
Posted Aug 11, 2012So I have added groups to my rewards yml file. Copy below
'version' below is the version of this YML file. DO NOT CHANGE THIS
I have used the console as below:
ontime rewards add group 0 2 0 Citizen
18:17:13 [INFO] Group Citizen not defined by GroupManager.
Why is it this hard ? I also use bpermissions
@Edge209
EDIT: OK I see from another post that Groupmanager is just a permissions system. From the install instructions:
"If the optional Permissions plugin is installed: 5.Edit /plugin/ontime/rewards.yml, listing the permissions groups from lowest to highest under the 'groups:' keyword"
Is this a typo ? Do I need to reenter my groups ? Will continue working on this so hopefully will answer it myself but if you get a chance - just confirm please.
-
View User Profile
-
Send Message
Posted Aug 11, 2012Great plugin but still confusing my simple mind - and thanks for the effort to help out with the tutorial. You have numerous config files all with clear statements not to change parts. I also not sure where the example parts of the config files end and the real bits start. I am assuming we remove the comments. May I suggest some real working example yml files we can just download as part of the tutorial.
I was also not clear on whether I needed to add any lines to my bpermissions file .....
-
View User Profile
-
Send Message
Posted Aug 10, 2012@numanumajosh
I just posted a new tutorial on how to set up promotions. Take a look at it and hopefully it will all then make sense.
Please let me know if it does not, since that means the tutorial needs work.
http://dev.bukkit.org/server-mods/ontime/pages/tutorials/3-auto-rank-group-promotions/
-
View User Profile
-
Send Message
Posted Aug 10, 2012I can't really get the config for OnTime. It's really confusing, especially since I have a LOT of ranks to cover. Are you planning on cleaning up the config a bit, in the future? Make it easier for config newbies like me to use (:
Or if someone can configure it for me, that would be great. I will send you my ranks, and the time for each promotion.
-
View User Profile
-
Send Message
Posted Aug 10, 2012Thanks so much for your help. Much appreciated, and thanks for developing such a great plugin.
-
View User Profile
-
Send Message
Posted Aug 10, 2012@Icefuzion
That error is likely the result of one of two things:
1. You do not have rewards enabled in /plugin/ontime/config.yml. The setting should be as follows:
# Enable if OnTime Rewards system to be enabled
rewardsEnable: true
2. Somehow your /plugin/ontime/rewards.yml file is missing a key piece of information, or it is a very old root version. After all of the explanation comments in that file you will find the following:
#
# 'version' below is the version of this YML file. DO NOT CHANGE THIS
#
version: 6
#
#
If this is missing or the version number listed is 4 or less, the plugin will automatically disable Rewards. The best way to fix this is to delete your current rewards.yml, restart the server so a clean version is generated. Then edit that new version and add back in your list of groups.
And then restart your server one more time, or do a plugin reload (/rl).
-
View User Profile
-
Send Message
Posted Aug 10, 2012Thanks for that detailed reply!
However, when trying to type in the command in-game it gives me this error: OnTime Rewards are not enabled on this server.
-
View User Profile
-
Send Message
Posted Aug 9, 2012@Icefuzion
I am working on a tutorial to hopefully make this less confusing for people, but since that is not yet ready, here is what you need to do.
Lets call the member ranks Member1 - Member5; donor ranks Donor1 - Doner5; and add in 'moderator', 'admin' and 'owner' for staff. Also lets have a 'default' group where everyone starts when they first join your server. For the automated promotions a player will move from Member group to Member group after every two hours of playtime.
Here is what you do:
Using an editor such as Notepad, edit the plugin/ontime/rewards.yml, and under the "groups:" keyword create an order list from lowest to highest rank of the groups. When done it would look like:
groups:
-Default
-Member1
-Member2
-Member3
-Member4
-Member5
-Donor1
-Donor2
-Donor3
-Donor4
-Donor5
-moderator
-admin
-owner
(Note that there should not be a blank line between 'groups:' and ' -Default', but this editor keeps inserting it on me. Also make sure to always use spaces and NEVER tabs when editing a .yml file.)
That's all you need to do to this file.
Then from the console or in-game from an op account execute these commands:
ontime rewards add group 0 2 0 Member1
ontime rewards add group 0 4 0 Member2
ontime rewards add group 0 6 0 Member3
ontime rewards add group 0 8 0 Member4
ontime rewards add group 0 10 0 Member5
That's it!
The first promotion from Default -> Member1 will happen after 0-days 2-hours 0-minutes, etc.
You only need to change these numbers to make the promotions happen in the time frames you want.
I hope that helps.
-
View User Profile
-
Send Message
Posted Aug 9, 2012This is so complicated...
What I need is: 5 member ranks that each level up after a different amount of hours. 5 donator ranks that stay, nothing should happen to them. And the same with staff.
What's the best way of doing this? I've been reading the help pages but find it rather confusing. Thanks in advance.
-
View User Profile
-
Send Message
Posted Aug 9, 2012@Icefuzion
You need to add your donor ranks to the bottom of the list of goups found in the plugin/ontime/rewards.yml.
e.g.:
groups:
- default
- citizen
- builder
- donorLevel1
- donorLevel2
- admin
- owner
Any auto promotions set for the default, citizen, or builder groups will not be applied to any of the other groups listed later because they are 'higher' groups in this priority order.
-
View User Profile
-
Send Message
Posted Aug 9, 2012Is it possible for my donator ranks to not get "promoted" to a lower rank after a certain amount of time? Is there some kind of permission to exclude them from getting promoted? But I still want them on the list. Please reply, I really need to know.