More Info: How to Install Mods
Need Help? Click here for more information on How to Install Mods.
This thread was automatically marked as Locked.
Need Help? Click here for more information on How to Install Mods.
This thread was automatically marked as Locked.
I'm going to cover three fairly basic and fairly popular setups:
The Ranks System. This is the timeless system where a user starts out as a basic user or builder and works his way up a hierarchy of groups to get more permissions. Great for maps where you focus on building, and you want the noobies to prove themselves before you give them creative mode or something
The Teams Setup. This is another popular setup where you have multiple groups that you want to be essentially the same [i.e: They would have the same permissions or almost the same permissions] Good for working with plugins that checks your permissions group for something like chat colour or a plugin that allows/denies access to an area based on your group etc...
The Mods Setup. This setup can really be used in conjunction with any of the other two, and it's very simple.
Now if you're a seasoned permissions pro and you're rolling your eyes right now, just remember that this is geared toward the guy who has little or no setup experience with PermissionsBukkit.
When you download and install the plugin for the first time, it generates a file called 'config.yml'. Now this is where all the magic is going to happen. When you open the file for the first time you'll notice that a bunch of stuff is already typed in here. This is the default configuration and it serves to show you what this file is supposed to look like.
Now don't get intimidated yet, this might look a wee bit confsing at first, but in a few minutes this is going to look like a well oiled machine.
If you'll look at the way this hiarachy is set up, you'll see that the main groups in this file are 'users' and 'groups', and these groupings have little subgroupings attached to them and so on.
We'll take a look at the 'users' section first.
You probably noticed that I replaced 'ConspiracyWizard' with '<username>'. That's just because all 'ConspiracyWizard' was, was an example username. And this is just less confusing.
So what is this telling us? Well it's listing a user, and it's saying what permissions this user has, and what group he/she's in.
Now what have I done? I put my username in here, gave myself some 'real' permission nodes and assigned myself to a group [n00b]. If you don't know what permission nodes are, they're essentially little chunks of permissions that different plugins will give you. If I have a plugin that lets people change their usernames and give themselves nicknames, then it might have two different permission 'chunks'. nicknameplugin.setnickname, and nicknameplugin.setnickname.others. If I only have the first node and not the second, then I'll only be able to set my own nickname and not anyone else's. It's just a way of keeping track of who is allowed to do what, with which plugins.
And I can add as many users to this list as I want as long as I follow the same spacing hierarchy.
Now unless you're weird and like to do a lot more work than you have to, you'll rarely use the 'permissions' line of the 'users' section to setup your permissions. Because usually a player's permissions are defined by their group.
You'll observe that the way this section is set up isn't so different from the 'users' section. There are three groups added here already for us, 'default', 'admin', and 'user'. The only thing worth mentioning about that is that the 'default' group is always the one a player is put into when they first join by...Well by default. So I try to avoid changing the name of this group just in case it messes with that functionality at all.
So I added some group names to this list. You'll see that under each group it lists 'permissions' and 'inheritance'. It also lists one called 'worlds' in one of the groups [and we can add that line to the 'n00b' group if we wanted to] and I'll talk more about that later.
Now I've added some permissions to these groups and set their inheritance. So the group 'n00b' inherits all the same permissions from group 'default' [which isn't much] PLUS the permissions I specifically gave them and the group 'BossN00bz' gets all the same permissions as 'n00b' PLUS all the permissions I specifically gave them.
So now Catatonic27 can build, and smite people since he's in permissions group 'n00b' but he can't change his gamemode because his group doesn't have permission to do that. However, since Boxxy is in group 'BossN00bz' she can build, smite AND change her gamemode. You see, group 'BossN00bz' is better than 'n00b' because they get all the same permissions PLUS an extra one.
And we can add as many more groups as we want just like users. I also added a 'world' line to our new group that makes it so that whenever a user that is in this group enters 'world_nether' they get the permission to shoot fireballs that they would not have anywhere else.
Now I said I'd show you how to do a few different kinds of setups. And I already kind of showed you how to so a Ranks System by using the 'inheritance' function. A Teams System is pretty easy.
You see I left BlueTeam's permissions line blank because they inherited all the same perms as RedTeam. So these two groups are functionally the same. Except now I can use a chat colour plugin to set the colour for group 'RedTeam' to RED, and the colour for group 'BlueTeam' to BLUE.
"Duuude - You know what would be awesome? If like, the two different teams had like different special abilities and powers and stuff..."
Well that's easy enough to do:
So I added the permission to fly for RedTeam, but specifically denied to for BlueTeam. I then gave BlueTeam the smite permission. I didn't change the inheritance at all, just gave/denied a few permissions nodes.
Now as for the Mods System, it's not anything we haven't already gone over. It's just that in some cases, you don't want a moderator to be OP [that is, have ALL permissions] But you still want them to have ALL the essentials commands/permissions but don't feel like writing them all out.
So what did here was give the 'mod' group a .* node. And what that is, is a node that gives access to every permission for said plugin. essentials.* means he can do anything that essentials lets him. I even went in and denied him one command that I didn't want him to have. That's a LOT easier than typing every node out, setting it to : true and then setting that one node to : false.
I hope I was able to help you budding server admins out, and if you have any other questions, feel free to PM me.
May the force be with you all.
And yes, if you're not using Notepad ++...Just don't even bother.
You know, now that I think about it, you probably could. As long as you don't give it an 'inheritance' line I'm pretty sure sure you could make it anything you want. Silly me.
Here are the perms:
groups:
Guest:
default: true
permissions:
- essentials.afk
- essentials.motd
- essentials.spawn
- essentials.tpaccept
- essentials.help
- essentials.helpop
- essentials.rules
- mobarena.use.join
- mobarena.use.leave
- mobarena.use.spectate
- mobarena.use.arenalist
- mobarena.use.playerlist
- quarantine.play
- chestlock.free
- scsigns.use
- simplespleef.start
- supplysign.access
- multiverse.access.*
- multiverse.portal.access.*
inheritance: []
info:
prefix: '&e[Guest]&f'
build: false
suffix: ''
NOTE: All other ranks inherit.
I didn't really want to turn this thread into an "OMG my perms dont work please fix them for me" page, but since I'm already here replying to you, I might as well point out a few things:
- This is not PermissionsBukkit
- This thread is called "Setting Up PermissionsBukkit [TUTORIAL]"
- I did not claim to be an expert in PEX, GroupManager, or whatever it is you are using.
- I know that when using PermissionsBukkit, there is a 'permissions.build' node [which you do no have listed] that needs to be set to true in order to be allowed to build. I do not know if this is the case here, but it's work a shot.
Another thing I noticed:
"build: false" on the second line from the bottom. That seems like kind of an obvious thing to consider.
My Permissionsbukkit has the same format but my Permissions still don't work. Here are MY Perms. Soliders Are guests, Heroes are members, Demigods are Donors, Minorgods are Moderators, and Gods are Admins Please help!
users:
ConspiracyWizard:
permissions:
permissions.*: true
groups:
- admin
etock:
permissions:
commandbook.spawn: true
groups:
- Solider
LegendMayne:
permissions:
commandbook.spawn: true
groups:
- Solider
Fabian_2k9:
permissions:
commandbook.spawn: true
groups:
- God
firelord043:
permissions:
commandbook.spawn: true
groups:
- MinorGod
groups:
Solider:
permissions:
permissions.build: true
commandbook.spawn: true
commandbook.kit.starter: true
commandbook.return: true
iConomy.money: true
iConomy.pay: true
commandbook.warp: true
permissions.destroy: true
bukkit.command.help: true
commandbook.home.set: true
commandbook.home.teleport: true
commandbook.call: true
commandbook.away: true
God:
permissions:
permissions.*: true
permissions.all: true
inheritance:
- MinorGod
Hero:
permissions:
factions.kit.fullplayer: true
factions.money.*: true
commandbook.return: true
commandbook.msg: true
inheritance:
- Solider
Demigod:
permissions:
commandbook.warp.teleport: true
commandbook.heal.other: true
commandbook.heal: true
inheritance:
-Hero
-Solider
MinorGod:
permissions:
commandbook.bans.ban: true
commandbook.kick: true
commandbook.warp.set: true
commandbook.bans.unban: true
inheritance:
-Demigod
-Hero
-Solider
Help is greatly appreciated.
You can do quite a lot with PermisisonsBukkit from the console or in-game. I recommend that you give this page a read.
Hope that helped, thanks!
Locked.