Recer75 Posted June 8, 2012 Posted June 8, 2012 Hi I am a server Admin and i am trying to instal a decent Permission system on my server. I decided to try out PermissionsEx and i am satisfied with the result i am getting. The only problem i have encountered is that all machines like the mineer and quarry do not have the need permissions to modify the world. is it possible to make them get under the permission node to they who placed them or do it existe other solutions. This is my permission node groups: Guest: default: true permissions: - modifyworld.blocks.interact.* - -modifyworld.* Member: inheritance: - Guest permissions: VIP: inheritance: - Member permissions: Admin: inheritance: - VIP permissions: - '*' users: recer75: group: - Admin Sorry if i misspell or my grammar are wrong. Quote
bandworthy Posted June 9, 2012 Posted June 9, 2012 I have the same issue, my understanding is machines like the miner or pump are treated like a player, and with a permissions setup they need to be given permission just like a player to change the environment or they just sit there making the noise. But i have no idea what I'm supposed to enter these as whats the name? to use? this is my permissionEX file groups: Default: default: true permissions: - essentials.spawn - essentials.rules - essentials.motd - essentials.list - essentials.helpop - essentials.help - modifyworld.* prefix: '&e' options: build: false rank: '1000' Builder: permissions: - essentials.afk - essentials.back - essentials.back.ondeath - essentials.balance - essentials.balance.others - essentials.balancetop - essentials.chat.color - essentials.chat.shout - essentials.chat.question - 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 inheritance: - Default prefix: '&2' options: build: true rank: '500' Moderator: 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' 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 inheritance: - Moderator prefix: '&c[&7Admin&c]&f' suffix: '&f' options: build: true rank: '100' Owner: permissions: - '*' inheritance: - Admin prefix: '&c[&7Admin&c]&f' suffix: '&f' options: build: true rank: '0' users: bandworthy: group: - Owner kallkara: group: - Builder turkc: group: - Builder harzlek1: group: - Builder woopet: group: - Builder Any advice would be great thanks :) Quote
Forum Administrators sct Posted June 9, 2012 Forum Administrators Posted June 9, 2012 [buildCraft], [industrialCraft], etc Quote
Recer75 Posted June 9, 2012 Author Posted June 9, 2012 [buildCraft], [industrialCraft], etc Can you sow a permission file that works ? because i can't seem to get it to work. Quote
bandworthy Posted June 9, 2012 Posted June 9, 2012 users: bandworthy: group: - Owner kallkara: group: - Builder turkc: group: - Builder harzlek1: group: - Builder woopet: group: - Builder '[buildCraft]': group: - Owner '[industrialCraft]': group: - Owner see under users you can also add in game with command pex user [buildCraft] group set 'group with enough permissions name' for example Quote
Recer75 Posted June 9, 2012 Author Posted June 9, 2012 users: bandworthy: group: - Owner kallkara: group: - Builder turkc: group: - Builder harzlek1: group: - Builder woopet: group: - Builder '[buildCraft]': group: - Owner '[industrialCraft]': group: - Owner see under users you can also add in game with command pex user [buildCraft] group set 'group with enough permissions name' for example Ok now i have the permissions but i still got the same problem. Any ideas ? I am trying to run it on a tekkit 3.0.4 server. Here is my Permission.YML If i edit the Modifyworld Config.YML enable to false then it works but then guest can buld. groups: Guest: default: true permissions: - -modifyworld.* Member: VIP: inheritance: - Member Admin: inheritance: - VIP permissions: - '*' users: recer75: group: - Admin '[buildCraft]': group: - Admin '[industrialCraft]': group: - Admin Here is my Modyfyworld Config.YML enable: true itemRestrictions: false informPlayers: false whitelist: false messages: whitelistMessage: You are not allowed to join this server. Goodbye! prohibitedItem: You have prohibited item "%s". permissionDenied: Sorry, you don't have enough permissions Quote
bandworthy Posted June 9, 2012 Posted June 9, 2012 just wondering but everyone including the admin is inheriting the negated ' - -modifyworld.* ' from your default if you want everyone else to have it you'll have to give member ' - modifyworld.* ' I'm only new to this, and don't know if this is causing it to still not work Your modifyworld config is identical to mine so no issue there. Quote
j2ther Posted June 9, 2012 Posted June 9, 2012 To keep it clean you can set up a seperate group for the mod faux users and give them modifyworld.* Here is an example permissions.yml for you, the mod users are under the plugin group. http://pastebin.com/GNDuv8pv Also what version of PermissionsEx are you using? Version 19.2 currently has a problem recognizing the mod fake users, try 19.1 if you are not already. Quote
Grasfer Posted June 11, 2012 Posted June 11, 2012 Also what version of PermissionsEx are you using? Version 19.2 currently has a problem recognizing the mod fake users, try 19.1 if you are not already. Thanks, had to downgrade Perms version to 19.1 then it worked for me atleast. 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.