bPermissions
bPermissions
Welcome to bPermissions, a Superperms Manager for Bukkit! bPermissions focuses on being unique from the rest of the Permission managers. It's very simple to set up and use, it's lightning fast, fully featured, and has a great support team!
Some features:
- bPermissions has a gui client specifically designed to make running a server so easy that you'll forget that you ever used any other permissions plugin. Get it here!
- bPermissions has a unique command structure, never before seen in a permission manager. It's best used for adding lots of nodes to a user or group from the console or in-game, less typing!
- bPermissions has everything you would expect from a Permissions manager. Prefix and suffix support, inheritance, per-player permissions, multiworld support, promotion/demotion tracks, and even group priorities for multi-group setups.
- Note - bPermissions only defines prefixes and suffixes. You need a chat plugin such as bChatManager for them to show up in chat.
Commands
Say you have a user called 'Bob' and you want to put him in the group 'admin' and give him the prefix 'awesome'.
- /world yourmainworld - selects the world "yourmainworld"
- /user bob - selects the user "bob"
- /user setgroup admin - set bob's group as "admin"
- /user meta prefix awesome - set bob's prefix to "awesome"
You can do the same with groups!
- /world yourmainworld - again, selects the world
- /group admin - selects the group "admin"
- /group addgroup moderator - makes the admin group inherit from the moderator group
- /group meta prefix &c[Admin] - sets the admin prefix to "&c[Admin]"
Some other commands are as follows
- /permissions (or /bperms,/bp,/p) - general commands for bPermissions are prefixed by this
- /permissions import pex - import a pex permissions.yml in the pex folder
- /permissions reload - reloads your bPermissions files
- /permissions save - if auto-save is false, this saves your perms
- /permissions backup - backup your permissions
- /permissions helpme - for the lazy among you, this spews out some basic permissions files into your folder.
In order to use these commands, you'll need the permissions node bPermissions.admin
For configurable /promote and /demote tracks, you'll want to use permissions tracks. To read about those, visit this page
Want more commands? We have some others over on the commands page. Check 'em out!
Editing Files
bPermissions creates per world groups.yml and users.yml files in the bPermissions folder, which allow you to configure permissions on a per world basis.
Because bPermissions was designed to be configured largely via commands, bPermissions will often overwrite changes to these files especially if you /reload or restart the server.
If you've edited the files, you MUST use /permissions reload to load the modified files into the server, otherwise the permissions changes won't apply. Because a standard /reload unloads all plugins like a server stop, we cannot tell the difference between them and this will overwrite changes to your files with whatever the server last stored.
World mirroring
Worlds are mirrored like so:
world_mirroring_to: world_mirroring_from world_nether: world world_the_end: world
This duplicates the whole config for that world. Currently there's no way to have just the users or the groups mirrored, stay tuned for an update that adds this!
bPermissions and EssentialsChat
Allow me to put this issue to bed. Essentials Chat + bPermissions works for prefix and color.
This guide is for current users of EssentialsChat and want to use bPermissions along with it.
Players have colored rank prefixes and faction chat modes are also colored. All text can be colored by the players too using color codes such as &c.
bPermissions\world\groups.yml ( code snippet )
default: default groups: ## Peasant ## default: permissions: - group.default - group.userannouncer - group.userauction groups: - userannouncer - userauction meta: priority: '100' ## Citizen ## rank1: permissions: - group.default - group.rank1 groups: - default meta: priority: '200'
It has nothing configured for prefix but the group names are important (default, rank1)
Essentials\config.yml ( Code Snippet )
change-displayname: true #add-prefix-suffix: false player-commands: - chat.color - chat.format - chat.shout - chat.question chat: radius: 0 group-formats: default: '&8&lPeasant &r&8{DISPLAYNAME}&7:&r {MESSAGE}' rank1: '&8&lCitizen &r&7{DISPLAYNAME}&7:&r {MESSAGE}' moderator: '&e&l[Mod] &r&3{DISPLAYNAME}&7:&r {MESSAGE}' admin: '&c&l[Admin] &r&e{DISPLAYNAME}&7:&r {MESSAGE}'
Please direct all other Essentials support to their official support networks.
How do I get support?
First, we highly recommend you go read the FAQ page. If the answer isn't there, there's a few options of support.
- Visit the #bananacode irc channel on irc.esper.net. Just head there, as your question, and wait for someone to help you. It might be a while before you get an answer, so be patient!
- You can file a ticket. This is recommended if you don't have the time to hang around in the IRC or you have a bug report. Be prepared to check back to the ticket though, and make sure you attach your bPermissions groups and users yml files to the ticket.
- Comment on the bPermissions main page.
Note that as there's only one (slightly inactive) maintainer at the moment, any support queries may take some time.
However you choose to get support, "pls dont use txt spk," and make sure you use actual grammar.
I'm a developer!
If you wish to hook your plugin into bPermissions, please see the Developer Page for more information! If you wish to contribute code to bPermissions, fork us on GitHub!
Development builds of this project can also be downloaded from GitHub now. These builds have not been approved by the BukkitDev staff, and are possibly buggy. Use them at your own risk.
-
View User Profile
-
Send Message
Posted Mar 28, 2013why don't you use a [prefix] name [suffix]
-
View User Profile
-
Send Message
Posted Mar 28, 2013@IndigoParadox
I was thinking about that, but i guess i should have given more info as to why i need to separate prefixes. In my server there are ranks you earn as you play longer, giving you new prefixes as the ranks go up. The issue is that if people add them and i add them to another donator group, i need them to have a prefix from both their normal group based on time played, and their donator rank.
-
View User Profile
-
Send Message
Posted Mar 28, 2013Nevermind... LOL!
-
View User Profile
-
Send Message
Posted Mar 27, 2013@ballisticknife0
Couldn't you just add the two prefixes in the Prefix: ' ' area? like this;?
prefix: ' '
prefix: ' [Prefix1] [Prefix2] '
-
View User Profile
-
Send Message
Posted Mar 27, 2013@BerryMe
Can't you use the shorthand command described above to select player, world and group at the same time?
-
View User Profile
-
Send Message
Posted Mar 27, 2013Is there a way to remove the bpermissions select a world and set group message? I have a sign that auto-assigns a player to a group but when they click it they get the annoying pop-up [bPermissions] Set selected world to world [bPermissions] player selected [bPermissions] Set player's group to group
Is there anyway I can remove that?
-
View User Profile
-
Send Message
Posted Mar 27, 2013Is this plugin capable of having to prefixes? Ex. [Prefix1][Prefix2]Name
-
View User Profile
-
Send Message
Posted Mar 27, 2013This plugin works fine in 1.5.1?? god, please
-
View User Profile
-
Send Message
Posted Mar 27, 2013Is there an ETA on an update? The lag it's causing will force me to switch permissions systems soon as it's chasing people away from my server. Please, please help.
-
View User Profile
-
Send Message
Posted Mar 25, 2013@w7gamer
Yea I can use it but even ops need the permission nodes, which is kinda funny
as you might have missed the backpack.share IS in my previous post
-
View User Profile
-
Send Message
Posted Mar 25, 2013@aug_88
You need to addperm backpack.share to allow it to be shared over worlds. the backpack size doesn't set the size of it, only how far they are allowed to upgrade it. To ACTUALLY upgrade it you need to run the /backpack upgrade command enough times to reach the wanted size (defaults to 9 slots which are free if you have the use perm).
-
View User Profile
-
Send Message
Posted Mar 25, 2013@aug_88
My problem listed further down is also with backpack (and Portables by same author). I stripped my server down to only bperms and backpack more or less and even if I have OP and full perms for backpack I can't use it as I get "not enough permissions". Can you use Backpack with bPermissions at ALL?
Oh, and why not set the perks up together in a separate group and just add that group to the player? (use, free upgrade, max size)
-
View User Profile
-
Send Message
Posted Mar 25, 2013how on earth does this work with buycraft ? I have added the Backpack plugin and i want it to be a donater perk. for those donating 5 euro i added this package
world * (i rekon the * selects all worlds ?)
user {name}
user addperm backpack.use
user addperm backpack.upgrade
backpack.share
permissions save
permissions reload
those are the commands in package one
-------but if someone wants to buy the bigger pack i has used thisworld *
user {name}
user addperm backpack.use
user addperm backpack.upgrade
user addperm backpack.size.18
backpack.share
permissions save
permissions reload
etc etc
for some reason this wont work, however i see ingame I got my bought package but alas it keeps saying insufficent perms etc it seems only to work torugh ingame commands so i dont know wha tim doing wrong :(
-
View User Profile
-
Send Message
Posted Mar 25, 2013@I9hdkill It seems to be bPermissions because everything works fine when I remove bPermissions.
-
View User Profile
-
Send Message
Posted Mar 24, 2013Have a slight problem here. I am OP AND have the permissions set for a plugin but when I use the spout hotkeys nothing happen. If I use the commands I get that I don't have permissions. No error is generated (even in debug mode nothing shows). The same settings worked just fine in PEX for some reason.
-
View User Profile
-
Send Message
Posted Mar 24, 2013Hello creators of my favorite superperms plugin:
I have a problem, and it just started today. I went off to add Moderator to my group.yml in World and I come back to test and nobody has the rank next to their name anymore. Whenever someone talks, it would say [g] [Nation|Town] [Rank] Username: (ex. [g] [Hyrule|Jaedenar] [Owner] JPstang99:) but now it only shows [g] [Nation|Rank] Username. How can I get the rank back to the side of the person's username?
-
View User Profile
-
Send Message
Posted Mar 24, 2013Uhmm this is a weird one. I have like 4 worlds on my server, 2 of them have also the nether and end worlds for them. Using Multiverse for the multiworld magaement. Alright, So for 3 of the worlds, I mirror the permissions from one world and the other world, I created its own permissions. Since I didn't want premium members using the premium perks in it. In 1.5.1 I am seeing and getting reports that premium members are able to use their premium powers in the world where in the permissions files there is no desginations of the premium group and no user in the users list has been given the premium group designation. This is rather troublesome as the world that doesn't have the premium perks is the Factions world and we really can't have people getting an upper hand over the others. I was wondering, has this been noted by other people too? IS this an isolated case? What could I do to help identify and resolve the problem?
Thank you,
Oscar
-
View User Profile
-
Send Message
Posted Mar 24, 2013@cam246
This could be an issue with an other plugin that provide prefixes.
herochat, etc
-
View User Profile
-
Send Message
Posted Mar 23, 2013I have updated my server to 1.5 and I am using the current 1.4.7 version of bPermissions. The prefixes seem to be duplicating them self and adding the 2 prefix to the players name. I have a screen shot and my config file of my bPermissions.
Image: http://i.imgur.com/ukJQYyW.jpg Config: http://pastebin.com/Lt0XPeA4
Does anybody have an explanation for this?
-
View User Profile
-
Send Message
Posted Mar 23, 2013I notice lag whenever i (de/pro)mote someone @ v2.10.5.
Already tried to cleanup the users.yml using /perm cleanup but that didn't help, so i'll use 2.10.4 for now ;-)
Looking forward to the new release! :)