PEXtras
PEXtras
A simple plugin that adds a few extra features with PermissionsEx! Highly recommended for use with Buycraft
Current features:
- /pextras upgrade [name] [Required Rank] [New Rank] - Upgrade a player to a new rank, but only if they have the required rank!
- /pextras [suffix|prefix] add start [name] [Prefix Addition] - Add some text to the beginning of a players prefix! (Supports minecraft color codes)
- /pextras [suffix|prefix] add end [name] [Prefix Addition] - Add some text to the end of a players prefix! (Supports minecraft color codes)
- /pextras [suffix|prefix] remove [name] [Remove from Prefix] - Remove some text from a players prefix!
You CAN use multiple words at the end of prefix or suffix commands, however if you want to insert or remove just a space, put {space}. Also if you want to use a rank name with a space in it, just type it all as one word with {space} everywhere you want a space.
Permissions for each of these commands is as follows:
pextras.upgrade pextras.prefix.add pextras.suffix.add pextras.prefix.remove pextras.suffix.remove
Requirements:
- PermissionsEx
- Chat Manager, part of PermissionsEx zip files but a separate jar
Example Use with Buycraft:
- Add a package to Buycraft name "Rank1 to Rank2"
- Set the price as the difference between Rank1 and Rank2
- Add command "pextras upgrade {name} Rank1 Rank2"
Now when a player buys that package, it will check if they have Rank1, and if they do, it removes Rank1 and gives them Rank2!
Known Problems / Bugs:
- None! Report 'em if you find 'em
Please feel free to leave any bug reports, requests for additions, questions, concerns, or just feedback below!
How is the "upgrade" part of this plugin different from just using PEX's built-in ladder system? Is it mainly for buycraft so that someone buys rank23, it only works in-game if they are rank22?
LHammonds
@gabep10
I haven't been following this, apologies. I don't plan to add database support for this as only a small population of users would find this useful and it would be somewhat tedious.
@kill_da_trolls
I don't understand what you're saying. Can you clarify?
Any ways, I'll have a look at the source code and update it shortly.
EDIT: Actually I'm looking at the source and it appears that it should still work with the current versions of both PEX and Bukkit. I'll put up a file listed for the current version of Bukkit anyways, to make it clear it is still up to date. Can anyone confirm it does not work?
@kill_da_trolls
i did a bad thing and decompiled the plugin. Threw 1.7.9 craftbukkit as a source, and the latest PEX (Apr 19, 2014), and surprise surprise, there were no errors in the code, nor any missing dependencies or deprecated things.
in other words: The plugin works great. What is missing is checking 'rank: 1000' and the such for a higher rank. with that said, keep in mind that the order your ranks are in the config mean nothing to the plugin as to which comes first without giving it rank numbers.
source: PEX@GitHub - Basic PEX Ranking
This plugin is in bad need of an update, if I do /pextras upgrade kill_da_trolls Default Voter it just automatically updates me despite if I am a higher rank than Voter.
Basically this plugin either needs to be updated to support the latest version of PermissionsEx, or if someone could tell me a version of PermissionsEx that this plugin is currently compatible with without the /pextras upgrade bug then that would be appreciated.
Can you add this plugin so that it gets information from a mysql database?
Very good plugin
@igztryhard
I can't replicate this problem, when I upgrade a player the first rank is removed.
When a player upgrades from lets say C-VIP -> I-VIP They keep both ranks, C-VIP and I-VIP
@Zawmbee Should be up shortly, with suffixes and multi-word changes now! Wasn't planning on updating it, but with 1.2k downloads and some support shown from users, I gladly will!
@LenaDINNERTIME If you check the post, the permission node for all of those was "pextras.admin", however in the latest version there are individual permission nodes. The purpose of this plugin is to add small "pieces" to prefixes and suffixes, /pex user prefix only allows you to entirely reset it. I find it personally useful, so that if players have multiple ranks, I can just add a "[RankName]" to the front of their prefix without having to worry about what other ranks they need to have.
@RealDopey
Update this please xD
Does this plugin support setting rank prefix priority for multiple groups? Pex normally shows prefixes at which a rank was added to the player last, and this is a problem.
If not, perhaps add a feature to allow players to choose which prefix they'd like to show off?
Great plugin, but i'm pretty sure /pex user prefix works just as good, only that it's change-able regardless of rank. Which isn't much of a problem considering you as an opp'd admin of your server will change player's prefixes to the new "rank" to your preference.
Which leads me to ask as to why you don't have permission nodes? I would never allow my moderators op.
@Iaccidentally
how? can you please inform us? i've been trying to find a way for a long time, and i dont want to switch to pex just for an upgrade feature.
How about allowing players with the perm nodes, to change their own prefix ? max character count 16 though
@SwiftSwamp
GM already has similar commands built in, there is no need for a plugin like this for GM.
@SwiftSwamp
Just use PEX :P
I wish there was something like this for GroupManager =p
Can't wait to use this plugin. Keep up the good work.