-
Notifications
You must be signed in to change notification settings - Fork 0
Issues Setting up with Heroes #2
Comments
Not exactly - you can limit the number of titles to display, but assuming that's not exactly what you're after... Would something like a "if this permission exists then stop adding titles" node help? |
That would be perfect. A priority feature would also work well, but you seem to be keeping this plugin nice and simple. What about a command to remove all titles from a player? |
Added a "stop_prefix" config that prevents any further titles being added - add it to any other title in there, the default is "!!!" (without the quotes). Because the titles are permission based, you should be able to just give a permission to players who you don't want to have titles, and have that as the first entry. |
Thanks and I'm sorry, but how do I update to this? |
dev builds - http://files.mmo.me.uk/dev/ |
Is this the correct configuration? |
Yep - the only thing to remember is that Bukkit doesn't guarantee the order of the configuration (one of many points against it) - so it might decide not to have them in the correct order... |
How would one set the default title to blank? I've got normal players all figured out, but admins who are given the admin.title (!!![Admin]) permission still have the default title along with the Admin title. |
Order is important - put the Admin title first (and hope that Bukkit doesn't change the order)... |
Instead of a stop prefix could you add something that makes it so whoever has that permission uses ONLY that title? |
Trying to set up my server so that a players Heroes class will show up as a user's title. If you're not familiar with Heroes, you can grant permissions as a skill, granting the user that permission while they're in that class.
Got it to work fine, except for admins/ops. They have all permissions and therefore show as many titles as we have. I need several titles and a high setting for max-titles to allow their title to change.
Is there a way around this?
The text was updated successfully, but these errors were encountered: