cjp240573 Posted January 7, 2013 Posted January 7, 2013 Hi. I hope someone can save my insanity here. Over the past week I have been trying to get a server running for a few friends. That part was easy. Installed ESSENTIALS MOD pack, that works great but what I need to do now is set permissions because I do not want others to be able to create WARP point and such like. I have downloaded PermissionsEx and installed the MOD and in the server start up it says that it is now enabled and I know it is running because from the console I can do 'pex groups' etc however for some reason I cannot get it to recognise any of my permissions that I set. I have read up on the mod and the configuration, albeit that the documentation to this is very fragmented all over the internet but it doesn't seem that complicated so I am sure I have missed something. Will keep this very simple of what my set up is. In c:\tekkit I have my server. This runs very well and I can connect to it Ok. in c:\tekkit\plugins\PermissionsEx\config.yml permissions: backend: file backends: file: file: permissions.yml superperms: {} in c:\tekkit\plugins\PermissionsEx\permissions.yml groups: default: default: true permissions: - modifyworld.* options: rank: '1000' Member: prefix: '&c(Member)&7' permissions: - '*' options: rank: '900' users: cjp240573: group: - Member .. as you can see, my login is cjp240573. This script is very small and basic. At the moment the above does not give or deny any permissions as such but I would like to see it working at least before I go any further with it. (as in, when I do a "say" in Minecraft it should output "(Member)" prefix before the message) so I know that I am in that group, but I cannot get to that stage. To see if working I would also expect to (from the console or game) do 'pex groups' and for it to show me the default and Member but when I do that it just shows me.. [iNFO] default #0 (rank: 1000@default) but does not show me the group I am in. (See pic) I do not know what to do or what to try. I would also like to add in there the ability for default user to not be able to use WARP. Any advise muchly appreciated. CJ Quote
Axle Posted January 8, 2013 Posted January 8, 2013 Well, if it is following that script to the letter, the 'Member' group is tabbed in to far and PEX will think it is part of the Default group, and PEX does not know how to handle 'Member' as a condition. Quote
Syndrogo Posted January 8, 2013 Posted January 8, 2013 My Permission example. Make sure to use Notepad ++ and change it to YAML groups: Guest: default: true permissions: - essentials.spawn - essentials.rules - essentials.motd - essentials.list - essentials.helpop - essentials.help - essentials.chat.color - essentials.chat.shout - essentials.chat.question prefix: '&e[Guest]' options: build: false rank: '1000' Member: permissions: - essentials.afk - essentials.balance - essentials.balance.others - essentials.balancetop - essentials.compass - essentials.depth - essentials.home - essentials.ignore - essentials.kit - essentials.kit.tools - essentials.mail - essentials.mail.send - essentials.me - essentials.msg - essentials.nick - essentials.pay - essentials.ping - essentials.powertool - essentials.protect - essentials.sethome - essentials.signs.use.* - essentials.signs.create.disposal - essentials.signs.create.mail - essentials.signs.create.protection - essentials.signs.create.trade - essentials.signs.break.disposal - essentials.signs.break.mail - essentials.signs.break.protection - essentials.signs.break.trade - essentials.suicide - essentials.time - essentials.tpa - essentials.tpaccept - essentials.tpahere - essentials.tpdeny - essentials.warp - essentials.warp.list - essentials.worth - treeassist.autoremove - treeassist.replant - treeassist.toggle inheritance: - guest prefix: '&2[LE Member]' options: build: true rank: '500' Mod: permissions: - essentials.ban - essentials.ban.notify - essentials.banip - essentials.broadcast - essentials.clearinventory - essentials.delwarp - essentials.eco.loan - essentials.ext - essentials.getpos - essentials.helpop.recieve - essentials.home.others - essentials.invsee - essentials.jails - essentials.jump - essentials.kick - essentials.kick.notify - essentials.kill - essentials.mute - essentials.nick.others - essentials.realname - essentials.setwarp - essentials.signs.create.* - essentials.signs.break.* - essentials.spawner - essentials.thunder - essentials.time - essentials.time.set - essentials.protect.alerts - essentials.protect.admin - essentials.protect.ownerinfo - essentials.ptime - essentials.ptime.others - essentials.togglejail - essentials.top - essentials.tp - essentials.tphere - essentials.tppos - essentials.tptoggle - essentials.unban - essentials.unbanip - essentials.weather - essentials.whois - essentials.world - permissions.user.promote.default - permissions.user.demote.default - permissions.manage.membership inheritance: - builder prefix: '&5[Mod]' options: build: true rank: '200' Admin: permissions: - -essentials.backup - -essentials.essentials - -essentials.setspawn - -essentials.reloadall - essentials.* - permissions.manage.users - permissions.manage.users.permissions - permissions.manage.users.permissions.timed - worldedit.* - treeassist.toggle.global - treeassist.reload inheritance: - mod prefix: '&c[Admin]' options: build: true rank: '100' Owner: permissions: - '*' inheritance: - admin prefix: '&4[Owner]' options: build: true rank: '0' users: Starcraft1535: group: - Owner Quote
cjp240573 Posted January 10, 2013 Author Posted January 10, 2013 My Permission example. Make sure to use Notepad ++ and change it to YAML Hi for all your help. Syndrogo. I have not had a change to play with this in anger, haven't had much time the weekend but I did put it in place and now it see's me in the Owner group which is where I expect to be. Am I right in saying that everything is DENY unless specified. What I mean to say is that in an old tutorial people were putting essentials.whois: true (or false) In your example you are putting - essentials.whois with one dash Or - -essentials.whois with two dashes is the meaning for True (top one) and False (bottom one) Many Thanks for your help. Regards CJ Quote
Syndrogo Posted January 10, 2013 Posted January 10, 2013 In permission bukkit you have to put essentials.whois: true (or false) for permissionsex you have to drop the : and true. Permissionsex likes to work if you list it in the groups permission it has to be true. To include all permission in a mod you would put - essentials.* Only want one dash If you want you can send me what commands you want each group to have and ill set it up for you. Quote
cjp240573 Posted January 10, 2013 Author Posted January 10, 2013 In permission bukkit you have to put essentials.whois: true (or false) for permissionsex you have to drop the : and true. Permissionsex likes to work if you list it in the groups permission it has to be true. To include all permission in a mod you would put - essentials.* Only want one dash If you want you can send me what commands you want each group to have and ill set it up for you. Ok, thank you. I got that. I was confused a bit because in your YML file (above) you but double dashes in. Admin: permissions: - -essentials.backup - -essentials.essentials - -essentials.setspawn - -essentials.reloadall Was that a typo? are there only meant to be one dash then? Admin: permissions: - essentials.backup - essentials.essentials - essentials.setspawn - essentials.reloadall Quote
Syndrogo Posted January 10, 2013 Posted January 10, 2013 Should just be: Admin: permissions: - essentials.backup - essentials.essentials - essentials.setspawn - essentials.reloadall But to give your admin all the commands use - essentials.* Quote
cjp240573 Posted January 11, 2013 Author Posted January 11, 2013 Should just be: Admin: permissions: - essentials.backup - essentials.essentials - essentials.setspawn - essentials.reloadall But to give your admin all the commands use - essentials.* Syndrogo. I do appreciate your help here. However last night I had a chance to play with the permissions.yml file and do some testing. This is what happened. Using your permissions.yml (with the extra -'s removed) I can log into the server, do a / and say something and that comes up with <Owner>cjp240573: so that's ok and it has understood my group. However to test the permissions on a the Guest: group I set the following. Ran a PEX RELOG and then did another / and said something else and that came up with <Guest>cjp240573: so again all looks good so far. However being in the Guest: group, according to the permissions.yml file you would not expect to be able to do /Setwarp or a /Delwarp would you? But it still let me do it. Would you expect in the Guest group with your permissions.yml file to be able to do AFK? because it lets me do it. Where I feel that it shouldn't. Also according to the YML file for Guest: the Build is false but it lets me build and destroy blocks... Sitting here now typing this out I am thinking is my username is in the owner.txt file, but even so would that still give me permissions to everything? by pass the permissions? even though I am in the Guest group?.. It is only when it doing what it says on the tin am I really able to branch out and add more intricate permissions line by line and test them. Sorry about this. Thanks for in advance for all your help. CJ users: cjp240573: group: - Guest Quote
Syndrogo Posted January 11, 2013 Posted January 11, 2013 Do you have your self set to OP? if so that the reason why you can put in commands. Also make sure you have the most up to date version: http://dev.bukkit.org/server-mods/permissionsex/ Lets try Debug and see what errors pop up. Debug Mode One of the best ways to troubleshoot a permissions problem with PEX is to turn on debug mode. In your PEX config.yml, set the following two options: Under the superperms section, set debug: to true Under the main permissions section, set debug: to true When these two options are set, PEX will display all permission node checks as they occur, making it much easier to figure out why a user or group is told they don't have permissions. When you are done, it is recommended to set the main debug line back to false, but leave the one for superperms turned on. Don't worry about PEX spamming your console or log, the debug output will not appear with this setting until you run pex toggle debug to turn on global debug. If you want to debug just a specific player, the pex user <user> toggle debug command can be used for that. Quote
cjp240573 Posted January 11, 2013 Author Posted January 11, 2013 Do you have your self set to OP? if so that the reason why you can put in commands. Also make sure you have the most up to date version: http://dev.bukkit.org/server-mods/permissionsex/ Lets try Debug and see what errors pop up. Debug Mode One of the best ways to troubleshoot a permissions problem with PEX is to turn on debug mode. In your PEX config.yml, set the following two options: Under the superperms section, set debug: to true Under the main permissions section, set debug: to true When these two options are set, PEX will display all permission node checks as they occur, making it much easier to figure out why a user or group is told they don't have permissions. When you are done, it is recommended to set the main debug line back to false, but leave the one for superperms turned on. Don't worry about PEX spamming your console or log, the debug output will not appear with this setting until you run pex toggle debug to turn on global debug. If you want to debug just a specific player, the pex user <user> toggle debug command can be used for that. Ok, great. I will try that. Will let you know. Many Thanks CJ Quote
cjp240573 Posted January 14, 2013 Author Posted January 14, 2013 Do you have your self set to OP? if so that the reason why you can put in commands. Also make sure you have the most up to date version: http://dev.bukkit.org/server-mods/permissionsex/ Lets try Debug and see what errors pop up. Debug Mode One of the best ways to troubleshoot a permissions problem with PEX is to turn on debug mode. In your PEX config.yml, set the following two options: Under the superperms section, set debug: to true Under the main permissions section, set debug: to true When these two options are set, PEX will display all permission node checks as they occur, making it much easier to figure out why a user or group is told they don't have permissions. When you are done, it is recommended to set the main debug line back to false, but leave the one for superperms turned on. Don't worry about PEX spamming your console or log, the debug output will not appear with this setting until you run pex toggle debug to turn on global debug. If you want to debug just a specific player, the pex user <user> toggle debug command can be used for that. Hi Syndrogo. Had some success which is good. I removed myself from the OPS text file and when I logged in as myself specified in the Guest group in the yml file it worked. I could not do anything really apart from the following. Which is good and when I tried to build it would not let me which is also good because you have stated options build false. However I then changed myself to be a member. So I changed my username from a Guest to a Member and logged in and that came up saying that I was in the member group. However it still would not let me build, even though the options for Member are build : true (however I have just noticed that the Member has an inheritance to Guest but if that brings over the build : false and that overrides the Member build : True, I'm not sure. I am still playing around with it. Also what is the best way to deny TNT everywhere? Thanks CJ - essentials.spawn - essentials.rules - essentials.motd - essentials.list - essentials.helpop - essentials.help - essentials.chat.color - essentials.chat.shout - essentials.chat.question Quote
Syndrogo Posted January 14, 2013 Posted January 14, 2013 Member: permissions: - essentials.afk - essentials.balance - essentials.balance.others - essentials.balancetop - essentials.compass - essentials.depth - essentials.home - essentials.ignore - essentials.kit - essentials.kit.tools - essentials.mail - essentials.mail.send - essentials.me - essentials.msg - essentials.nick - essentials.pay - essentials.ping - essentials.powertool - essentials.protect - essentials.sethome - essentials.signs.use.* - essentials.signs.create.disposal - essentials.signs.create.mail - essentials.signs.create.protection - essentials.signs.create.trade - essentials.signs.break.disposal - essentials.signs.break.mail - essentials.signs.break.protection - essentials.signs.break.trade - essentials.suicide - essentials.time - essentials.tpa - essentials.tpaccept - essentials.tpahere - essentials.tpdeny - essentials.warp - essentials.warp.list - essentials.worth - treeassist.autoremove - treeassist.replant - treeassist.toggle inheritance: - guest prefix: '&2[LE Member]' options: build: true rank: '500' As you can see at the bottom it has build true To stop TNT use WorldGuard. Quote
cjp240573 Posted January 15, 2013 Author Posted January 15, 2013 Member: permissions: - essentials.afk - essentials.balance - essentials.balance.others - essentials.balancetop - essentials.compass - essentials.depth - essentials.home - essentials.ignore - essentials.kit - essentials.kit.tools - essentials.mail - essentials.mail.send - essentials.me - essentials.msg - essentials.nick - essentials.pay - essentials.ping - essentials.powertool - essentials.protect - essentials.sethome - essentials.signs.use.* - essentials.signs.create.disposal - essentials.signs.create.mail - essentials.signs.create.protection - essentials.signs.create.trade - essentials.signs.break.disposal - essentials.signs.break.mail - essentials.signs.break.protection - essentials.signs.break.trade - essentials.suicide - essentials.time - essentials.tpa - essentials.tpaccept - essentials.tpahere - essentials.tpdeny - essentials.warp - essentials.warp.list - essentials.worth - treeassist.autoremove - treeassist.replant - treeassist.toggle inheritance: - guest prefix: '&2[LE Member]' options: build: true rank: '500' As you can see at the bottom it has build true I know Syndrogo but it still does not build or destroy. I will keep playing around with it, will let you know. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.