Only two slight issues - Permissions, CommandBook

For some reason, when people connect to my server, it doesn't put them in my "Player" group in Permissions, which is the group I have set to default. Rather, it puts the players in a new "Default" group that doesn't even exist. Here's the config for groups that I have:

Code:

groups:
    Player:
        default: true
        info:
            prefix: '&1'
            suffix: ''
            build: true
        inheritance:
        permissions:
        - myhome.home.basic.set.
        - mywarp.warp.basic.*
        - lwc.protect
        - commandbook.motd
        - commandbook.rules
        - commandbook.time.check
        - commandbook.who
        - commandbook.msg
        - commandbook.whereami
        - commandbook.say.me
        - mywarp.warp.sign.warp
        - mywarp.warp.sign.create
    Mod:
        default: false
        info:
            prefix: '&2'
            suffix: ''
            build: true
        inheritance:
        - Member
        permissions:
        - commandbook.kick
        - commandbook.bans.ban
        - commandbook.bans.unban
        - commandbook.bans.isbanned
        - commandbook.return
        - commandbook.teleport
        - commandbook.teleport.other
        - lwc.mod
        - autosave.save
    Admin:
        default: false
        info:
            prefix: '&4'
            suffix: ''
            build: true
        inheritance:
        permissions:
        - '*'

Before you ask, I have tried putting new players in the "Player" group by using the Users config, but that doesn't work either. The &1, &2 and &4 in the suffixes are for nChat, so the player group will be shown in that color. I have no idea why it's placing new players in a non-existant "Default" group, can anyone help me with that? Much appreciated.

Second off, when players first connect to my server, they don't go to the spawn I set it at it, which is on top of a plateau, but rather, 20 blocks away from the spawn, on the ground. When they die though, they go to the spawn, and /spawn takes them from the spawn. I was thinking about just getting SpawnX or something, but if there's an easy fix within CommandBook, that would be super.

Just some extra information, I am running Windows 7 Ultimate, x64 architecture. I'm running CraftBukkit build 1000. I am running the following plugins on my server:

• AutoSave
• BorderGuard
• CommandBook
• LWC
• MyHome
• MyWarp
• Help
• nChat
• Permissions
• WorldEdit
• WorldGuard
• ChopTree

Only a couple steps away from hosting a server for en masse at the Minecraft forums!

 

im not sure why it's putting users in your default, but i did notice that your spacing is off with permissions. there should be 12 spaces before permission nodes and apostrophes around the nodes.
example

Code:

groups:
    Player:
        default: true
        info:
            prefix: '&1'
            suffix: ''
            build: true
        inheritance:
        permissions:
            - 'myhome.home.basic.set.'
            - 'mywarp.warp.basic.*'
            - 'lwc.protect'
            - 'commandbook.motd'
            - 'commandbook.rules'
            - 'commandbook.time.check'
            - 'commandbook.who'
            - 'commandbook.msg'
            - 'commandbook.whereami'
            - 'commandbook.say.me'
            - 'mywarp.warp.sign.warp'
            - 'mywarp.warp.sign.create'

and i don't expect this to fix your default problem, but try adding a default group and set the default to false for it? maybe if it recognizes that there is one but it's set to false, it'll make the default group player. i'm just taking a wild guess. never seen this issue before.

 

That's...odd, I thought I did have apostrophes in the nodes. I'll do what you said and see if it does anything, thanks for the help.

 

You probably did have quotes on the lines but because your Mod group is inheriting from Member and you don't have a Member group, that triggers Permissions to fix a few things. I'm sure at some point you had a bogus Member group in the file with just an inheritance and permissions nodes right? When that happened, Permissions saved the file in a format that it likes.

 

Well, no dice Current Permissions config:

Code:

groups:
    Default:
        default: false
        info:
            prefix: ''
            suffix: ''
            build: false
        inheritance:
    Player:
        default: true
        info:
            prefix: '&1'
            suffix: ''
            build: true
        inheritance:
            -Default
        permissions:
            - 'myhome.home.basic.set,'
            - 'mywarp.warp.basic.*'
            - 'lwc.protect'
            - 'commandbook.motd'
            - 'commandbook.rules'
            - 'commandbook.time.check'
            - 'commandbook.who'
            - 'commandbook.msg'
            - 'commandbook.whereami'
            - 'commandbook.say.me'
            - 'mywarp.warp.sign.warp'
            - 'mywarp.warp.sign.create'
    Mod:
        default: false
        info:
            prefix: '&2'
            suffix: ''
            build: true
        inheritance:
           - Player
        permissions:
           - 'commandbook.kick'
           - 'commandbook.bans.ban'
           - 'commandbook.bans.unban'
           - 'commandbook.bans.isbanned'
           - 'commandbook.return'
           - 'commandbook.teleport'
           - 'commandbook.teleport.other'
           - 'lwc.mod'
           - 'autosave.save'
    Admin:
        default: false
        info:
            prefix: '&4'
            suffix: ''
            build: true
        inheritance:
        permissions:
           - '*'

I wonder what I'm doing wrong.

 

You need a space after the - and before the Default.

As for them being a new player, deleting their player.dat doesn't make them a new player. Removing them from your users.yml makes them a new player to Permissions.

 

^ Tried that, still not working.

Code:

groups:
    Default:
        default: false
        info:
            prefix: ''
            suffix: ''
            build: false
        inheritance:
    Player:
        default: true
        info:
            prefix: '&1'
            suffix: ''
            build: true
        inheritance:
            - Default
        permissions:
            - 'myhome.home.basic.set,'
            - 'mywarp.warp.basic.*'
            - 'lwc.protect'
            - 'commandbook.motd'
            - 'commandbook.rules'
            - 'commandbook.time.check'
            - 'commandbook.who'
            - 'commandbook.msg'
            - 'commandbook.whereami'
            - 'commandbook.say.me'
            - 'mywarp.warp.sign.warp'
            - 'mywarp.warp.sign.create'
    Mod:
        default: false
        info:
            prefix: '&2'
            suffix: ''
            build: true
        inheritance:
           - Player
        permissions:
           - 'commandbook.kick'
           - 'commandbook.bans.ban'
           - 'commandbook.bans.unban'
           - 'commandbook.bans.isbanned'
           - 'commandbook.return'
           - 'commandbook.teleport'
           - 'commandbook.teleport.other'
           - 'lwc.mod'
           - 'autosave.save'
    Admin:
        default: false
        info:
            prefix: '&4'
            suffix: ''
            build: true
        inheritance:
        permissions:
           - '*'

 

Your default works just fine as you have it in the groups above. I tested it on my test server. Unless you are using the global files when you shouldn't, removing him from the users.yml file and having him log in would create a new user record and assign it the default group which would be Player.

 

Oh shit. I've been using the global files

EDIT: This completely solved all of my problems. Thank you, good sir.

The only issue I have left is the spawn. When people first join the server, they spawn where they shouldn't. But when they die or do /spawn, they go to the normal spawn. Must have something to do with CommandBook. Please note that the lower spawn is not directly below the proper one.



EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

@Swordfyre
The initial spawn is always in a different location. I assumed it was to protect new players from griefers. You can get plugins that allow you to change that location but I don't know of one right now.

 

The initial spawn is actually hundreds of blocks away.

Found the ExactSpawn plugin, haven't had an issue since. I'll be sure to thank you two for helping me.

EDIT by Moderator: merged posts, please use the edit button instead of double posting.