Plugin and permissions help

Hi guys, I'm very new to running my own bukkit server and im having some trouble setting up plugin permissions.

I have installed word edit, simple spawn, qwick tree, and permissions bukkit.

I have followed he tutorial to the letter for permissions bukkit, but it doesnt create a the config.yml like its supposed to.

ATM qwicktree doesnt work at all (although it says ingame that its enabled), only I am able to use simplespawn commands, so far world edit seems to be working fine for me but no-one else (which is fine, thats the way i want it).

Thanks in advance for any help.

Stoney

 

I'd suggest using GroupManager and Essentials, and removing Permissions Bukkit, it will make your life easier in the long run.

Make sure Qwicktree is up to date and before you restart your server to install plugins, rename server.log to something else, restart then open the new server.log file, copy the contents to a PasteBin and post the link here.

 

I cant find a download just for groupmanager, is it essentisls groupmanager i need?

 

It's all here.

I use the dev builds (ridiculously hard to find: Bukkit page -> Dev/bleeding edge builds -> Teamcity/CI Downloads) because for some reason the Bukkit downloads don't have all Essentials plugins on the same version in one folder in the same place.

But the dev builds have always been 100% stable for me.

 

This is the server log file you wanted me to post (http://pastebin.com/Rrc5L9kK)

 

You don't seem to have any errors at all. Try adding this permission node to your default group in GroupManager->worlds->{worldname}->groups.yml:

Code:

    - QwickTree.use

If your server is running type 'manload' into the console to update the config files in-game.

 

Ok the qwicktree now works for me but no-one else can break any blocks or build anything ><

Sorry foe being a total noob here, never used any of this stuff before.

Edit, i have managed to allow players to build and destroy by default now thanks very much for your help

 

That's ok, we've all been there.

You'll need to set build: false to build: true for your default group in the groups.yml file I mentioned.

These groups are your ranks, all permission nodes listed for each group determine what each player in that group can do.

What you add to the 'prefix' option will determine their in-game rank tag. Bear in mind it's verbatim so for white brackets you need: '&f[&4Admin&f] '

Note the space on the end to stop the tag sticking to the player name.

I would also edit Essentials->config.yml to remove the ~ sign from nicknames (just delete it and leave it as '') and remove the c that colours Ops names red.

Then remove the < and > from around the outside of {DISPLAYNAME} and add a &f: after it and before {MESSAGE}. This will tidy up your chat a bit.

 

There isnt a line for build:true/false there will i need to add it?

I'm not that fussed about name prefix's yet. Its a small server with only a few friends playing, i just waned the plugins to allow qwicktree to work (which it is now) and to allow me to set 1 generic spawn point for new people or people that die, and allow everyone to set their own spawn poinnts for their homes. Also wanted world edit to work for me only to set protected areas for when people are finishing building projects.

All in all not that much needed but wow what an amount of stuff that comes with essentials it makes it look more complicated than i imagine it is.

 

Here's what the guest group looks like for one of my worlds:

Code:

groups:
  guest:
    default: true
    permissions:
    - essentials.teleport.timer.bypass
    inheritance:
    - g:one
    info:
      prefix: '&f[&7Guest&f] '
      build: true
      suffix: ''

The build option is underneath 'info'. It should be there by default but if it's not you can add it as it appears above, just make sure it's the same number of spaces (not tabs) away from the start of the line as it is here.

Essentials is great, you can do a lot with it but you don't need to do it all right away

 

Ah yeh i see it now >< i'm tryin to over think things now thanks bud. One last thing, how do i set a spawn point to cover all groups? when i do /setspawn it sets a spaw point for "default" users only and i cant see a command on http://wiki.ess3.net/wiki/Command_Reference/Perm to do this either by group or for everyone.

Think ive got my work cut out here trying to learn all of this lo