Hi there everyone, Ive been using PEX for a long time, basicaly almost since its release. But I never end up using the SuperPerms support. Now I have 2 plugins that are SuperPerms ONLY plugins and I need it now. I tried multiple stuff and nothing worked. An example of my permissions.yml at bukkit folder: Code: craft.iron.pick: description: Iron pick skill default: false children: crafting.iron.pick: true My Pex Config: Code: permissions: backends: file: file: permissions.yml backend: file superperms: enable-wildcards: true disable-unmatched: false strict-mode: true parent-nodes: true enable: true debug: true compatibility-mode: true createUserRecords: true debug: false basedir: plugins\PermissionsEx Then what I try to do is give the permission "craft.iron.pick" to the player I want to be able to craft an iron pick. But they still cant, even with the permission. Can anyone help me? Ive been watching tutorials everywhere and I cant find no one explaining this, SuperPerms + Pex. Thanks, Ralms. Note: Changing Permissions manager isnt an option since I need Modifyworld.
PEX does not support setting up custom nodes in bukkit's permissions.yml. Unless it got added later, I haven’t tried doing it since SuperPerm support was first added. PEX’s SuperPerm support basically means it will feed its permissions into Bukkit's SuperPerm system, so that SuperPerm only plugins can still check for permissions without being PEX aware. So all you need to do is give crafting.iron.pick to you users like normal, PEX will handle the rest in the background. One note: After adding a permission in-game, I always have to type /pex reload before SuperPerm plugins see the change.
That is what I though and I did that the first time, I got suprised when it didnt work. So I though It could have been a wrong config or something.
You dont have ModifyWorld XD "If you need any help with PermissionsEx, send me a PM!" Can you help me?? EDIT by Moderator: merged posts, please use the edit button instead of double posting.
I personally aren't that good with the superperms support that PermissionsEx has. I will take a look for you and tinker around a bit though.
I did a really basic setup with both of those plugins, taking their default settings. Using PEX, the SuperPerm support is working. For CommandShop, I granted group User commandshops.user.* and group Admin commandshops.manager.*. For BanRecipe group Default was given total permission and then I negated TNT in group User. Hope this example helps. https://www.dropbox.com/s/fa245l9tdm77k50/permtest.zip Excuses my type-o's in the server log.
Command shop default permissions for user is True. What I wanted was deny shop select and create, but the only way I did it was by blocking with CommandHelper xD banrecipe.46 ?? that worked? that blocked the crafting and default was able to do it? Intresting. Thanks a lot, I will try it was soon as possible, going to school now =) Hi there Paswaru, I tried that test server you set-up. And weirdly ban-recipe doesnt seem to be blocking any crafting table. If Im not wrong the default recipes that were there was TnT and flit'n'steal (didnt check). Tryied to deny those to default group and it still allows them to craft everything. Im in class, so I will try more around it later. Thanks for the help, Ralms. Paswaru, Ive been testing arround in the small set up you did for me, which I apreciate a lot but you have the exact same issues as me. The BanRecipe permissions are denied whatever what and the commandshop ones, I cant deny it. Anyone knows any solution to this? Thanks. EDIT by Moderator: merged posts, please use the edit button instead of double posting.
im too lazy to read everything here Ralm tell me in short what is your goal and what is the problem and i see what can be done + plugins names
Get 2 SuperPerms permissions only plugins, such as CommandShop and BanRecipe to work with Pex. Altough BanRecipe seem to be working on the other day, it was weird. Dunno.
many users use command shop with pex so i dont believe it need anything more to work as for ban recipe i gonna try it now but well why you just prevent users from using some items ? cause pex's modifyworld can do that
Im not preventing anyone to use stuff, Im preventing from crafting. Its for a mechanic I have in my server. My problem with commandshop was, since its normal commands are default true, I wanted to block shop creation.
why you dont switch from command shop to for example showcase ? http://dev.bukkit.org/server-mods/scs/ and if you really need that command shop i found this 1st you need to extract commandshop.jar for example to desktop and than open that folder and there you will have plugin.yml open it and hit ctrl and push F to trigger search now search word "create" and now 1st thing you will find is commandshops.manager.*: description: Owners and Managers can create, move or destroy shops and manage shops (using the set commands) default: true i dont know and this should be set to op commandshops.manager.*: description: Owners and Managers can create, move or destroy shops and manage shops (using the set commands) default: op now you need to select all files and add it to jar ALL FILES NOT FOLDER COMMANDSHOP.JAR and after you pack it it need to have commandshop.jar name and should work now as for ban recipe i check on later or maybe its that one commandshops.manager.*: description: Owners and Managers can create, move or destroy shops and manage shops (using the set commands) default: true children: commandshops.manager.add: true commandshops.manager.create: opcommandshops.manager.destroy: true commandshops.manager.move: true commandshops.manager.remove: true commandshops.manager.set: true commandshops.manager.set.owner: true commandshops.user.*: true i dont know you will need to make tests EDIT by Moderator: merged posts, please use the edit button instead of double posting.
Hm, I didnt knew I could just change that, ok thanks. You dont need to caps like that I know to do stuff, Im event starting in programing plugins. Thanks a lot, I will give it a try.
OK hmm if i want use permissionsEx and superperms I must write superperms nodes to permissions.yml in server folder or config.yml in PermissionsEx folder???
What in the end I kinda figure out is that Pex can manage permissions nodes from the plugins even if they are declared as SuperPerms nodes. Just add them normaly. Doing stuff like custom nodes in permissions.yml wont work in PEX.
This statement may no longer be true. I got a PM today from someone asking for help on how to format the Bukkit's permissions.yml. After helping him with that, he tried assigning it with PEX and says it worked. I've not tried it myself yet, but PEX may have added support for custom nodes from permissions.yml.
I tried it 3 weeks ago and it didnt work. On top of that I just checked Pex change log and there no note on that. Very much likely that guy made the node default true, giving access to everyone whenever they have permission or not, since you can do that in permissions.yml Im not sure but I still beleive it doesnt support, although I havent tried the true lattest version of pex.
That in fact maybe the case. The example I sent him had everything set to true. I didn't know Bukkit's permissions.yml would actually assign stuff.
OK thanx so much now i have nice plugins Multiworld and moooore with pex and superperms THX SO MUCH !!!! houba1970 from Czech republic