PayRank
This plug-in allows users to self-promote themselves to a provided static set of "ranks" using money or experience. Administrators can also promote/demote and specifically assign any of the defined ranks to a user at any time without taking player money or experience.
A "rank" is defined as a group and you can have as many of them as you like. Each "rank" allows you to define the price, experience cost, display name of the rank and the required group it will be using.
PayRank also provides simple chat coloring and formatting that can be configured to each rank.
See Configuration for further details.
Uses Metrics for sending completely anonymous data to http://mcstats.org for usage tracking.
Main - Installation - Configuration
CraftBukkit 1.4.7
The current version of PayRank appears to work fine on CB 1.4.7. No updates are needed. If you find a specific problem, please report it.
An update with new features will be made available as time permits.
Dependencies
Please note the following:
- PayRank requires plug-in Vault for managing both permissions and economy.
Commands
This is a list of the available commands that can be used:
Command | Description |
/payRank help | Displays help depending on other permissions. |
/payRank purchase | Increments the player to the next rank, if they can afford it. |
/payRank list | List all available ranks and their prices. |
/payRank promote <player> | Promote the user to the next rank regardless of cost. |
/payRank demote <player> | Decreases the player to the previous rank. No refunds ! |
/payRank give <player> <rank> | Give the user the exact rank regardless of level and cost. |
/payRank remove <player> | Removes the current rank from the user entirely. |
/payRank current [player] | Displays the current rank assigned to yourself or if given, the player. |
/payRank reload | Reloads all the configuration files for the plug-in. |
Permissions
This is a list of the available permissions:
Permission | Description |
payrank.list | Ability to list all available ranks. |
payrank.purchase | Ability to purchase a rank. |
payrank.promote | Ability to promote other players to the next rank regardless of cost. |
payrank.demote | Ability to demote other players to their previous rank. |
payrank.give | Ability to give a user the exact rank regardless of level and cost. |
payrank.remove | Ability to remove the current rank from a user leaving them with no rank assigned. |
payrank.current | Ability to see the current rank of yourself. |
payrank.current.others | Ability to see the current rank of others. |
payrank.reload | Ability to reload the plug-in configurations. |
Latest Changes
Version 1.2.3
- Updated to support CB 1.3.2-R1.0
- Appears to support CB 1.4.7-R1.0
Version 1.2.2 - For Bukkit 1.3.2-R0.1 ONLY
- Changed event PlayerChatEvent to AsyncPlayerChatEvent to support other chat plug-ins better (Factions for example)
Version 1.2.1
- Fixed issue with world permissions using bPermissions
- Fixed minor display bug in /payrank list
- Added additional bugging code
- Added usage of Metrics for sending completely anonymous data to http://mcstats.org for usage tracking.
See the Change Log for further details.
Coming Soon (still in planning)
- Multiple rank tree's. Ability to have several tree's in which users can be ranked within.
- Ability to assign multiple groups to a single rank so you can combine groups.
- Self-promote based on time spent in game (optional separate rank tree)
- Self-promote through signs.
- Other suggestions ?
Reporting errors
If submitting an error, please try to provide as much details as you can. Example: (but not limited to)
- Commands run
- Configuration files
- Permission manager used
- Bukkit version
- Detailed steps to reproduce (should it not be just the commands)
Any or all of the above will go a long way in helping me resolve your problem quickly and efficiently. All tickets will be looked at, but those that are written best will take priority.
Is there some way to make it so that there is no order to the purchasing of the ranks? It's not so important but it would make my life easier.
This uses Vault for permission management so in theory should work fine. However, if you run into problems, let me know the details and I can run some tests for you against your configurations.
Is this compatible with bPermissions?
Works like a charm, our players are very happy :) Thank you for all your help. I recommend this plugin to everyone :D
Okay, I've uploaded a new build to Bukkit. Version 1.1.1
This build appeared to have resolved the issues I was seeing with your configuration. Let me know if you run into any further problems.
Okay, can reproduce it using your settings. Looking into it now. Will get back to you very shortly.
This is my PEX config:
The reason why I use inheritance is because there are alot of permission nodes and it works excactly the same.
My PayRank config:
Still dosnt work, and like I said I use PEX for prefixes.
I downloaded PEX and installed it locally. I created a very, very basic permissions.yml for it and was able to log in as a user (non-op) and cycle through all the ranks.
Here's the permissions.yml I created:
I guess next step would be to try it using something your running with.
Sounds like the logic for purchase (checking current group) might not be working correctly for your permission plug-in. I ran into a similar problem with BukkitPermissions and had to add a specific code difference for that one.
Sounds like I might need to dig out PEX and try a local installation next.
Also, can you send me a snip of the permissions configuration around this plug-in ? Would help me try & reproduce it better. Thanks
I removed the chat module in PayRanks with the config and then set prefixes for the groups in PEX. But now I cant make it so that u go from Peasant -> Yeoman -> Squire , It just goes Peasant -> Yeoman -> Yeoman and so on... It charges for every time and i dont know what to do.
I can give someone Squire when i do /payrank give, or add them to the Squire group manually. But why doesnt it wotk with /payrank purchase?
@0Deminth0
Curious. When trying on someone else, does it actually change the group in your permissions at all when on the second person ? It sounds like there might be something else blocking the permission change.
I fixed it, I had to add a space before the prefix or else it wouldnt read the color or something :)
Although now I have a issue while trying to give and promote people to ranks. When I use /payrank promote or /payrank give nothing happens to their rank :o
I am able to use the commands on myself that is OP and it works. But the moment I try on someone else it says the have gotten promoted, but their rank and prefix havent changed. I have checked with /payrank current
Also when people try to use /payrank purchase, the plugin tells them they have been promoted, but they are actually thew same rank. They are also charged with the cost :/
The thing is that factions seems to change the template somehow, or they dont quite work together. Lets say a player creates a faction named Assassins, Then the outcome prefix would be &aAssassins &1[title] &f[player] in chat normally. But with PayRanks the whole prefix gets changed to white color and the title and faction gets stuck together like, for example: Assassins[Peasant] Deminth
This is how my ranks looks in the config:
{ "name": "Peasant", "group": "Peasant", "prefix": "&2[Peasant]&f ", "suffix": "", "template": "Template", "price": 0 },
Using the template:
{ "templates": [ { "name": "Template", "format": "[time][prefix][player][suffix]: ", "time": "", "worlds": [ { "name": "world", "displayName": "&e[World]&f" } ] }
I really hope you can help, thank you.
In what way is it interfering ? Is it stopping faction chat from displaying their values ?
Worse case, you could set my chatFormattingEnabled to false in the config and not have my plug-in do anything with chat.
Let me know what to look for and I can setup factions here locally and give it a look around to see what I can find out.
I got it to work, i deleted chat manager. But now PayRank interfere with faction prefix. What should i do? :O
@0Deminth0
I currently use PermissionsBukkit, which actually doesn't support the group based prefix/suffix that most other managers have.
I made the prefix/suffix work for PayRank without using those from the permissions config. Whatever prefix/suffix you have defined in your permissions for PEX won't actually be used, instead you'll need to configure it in the config.json for this plug-in. Leaving them in the PEX configuration file won't hurt anything, they'll be ignored.
If you're still having problems getting them to work, let me know your specific PEX version and possibly a clip of your config file to work against and I can take a look.
Hope that helps
How do I get the prefixes to work with PermissionsEX? Should I remove the prefix config from PEX completely or does it place a prefix anyway? :/
Version 1.1.0 Waiting approval.
Version 1.0.3 is waiting approval.
I've created an installation page that should help: Installation