/whitelist is broken?

Discussion in 'Bukkit Help' started by mrcheesete0, Apr 9, 2012.

Thread Status:
Not open for further replies.
  1. Offline

    mrcheesete0

    my admin team can't use the /whitelist command when I give them permissions following this page:
    http://wiki.bukkit.org/CraftBukkit_commands

    on 1.2.5-R1.0 with Group Manager 2.9.1

    I tried even just giving them bukkit.* and they can't do it.
     
  2. Offline

    MikeA

    The /whitelist command is for Bukkit, not Group Manager. You're using Group Manager, you must give them Group Manager permissions.
     
  3. Offline

    mrcheesete0

    Group Manager is just a permissions plugin, that handles the permissions. /whitelsit command is not used in groupmanager. it is a bukkit command.

    the permission bukkit.command.ANYTHINGELSE is broken, and none of them are giving my admins access to the Bukkit commands they should have.

    any help would be great since my admins can't whitelist anyone

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 25, 2016
  4. Offline

    mrcheesete0

    any at all
     
  5. Offline

    Wendo

    By default, with groupmanager these permissions are included in the bukkit_admin group, which your admin group should be inheriting. My guess is they aren't though and that's your problem

    Code:
        - bukkit.command.whitelist
        - bukkit.command.whitelist.add
        - bukkit.command.whitelist.disable
        - bukkit.command.whitelist.enable
        - bukkit.command.whitelist.list
        - bukkit.command.whitelist.reload
        - bukkit.command.whitelist.remove
     
  6. Offline

    mrcheesete0

    I deleted the whole globalgroups file and started the world-based group files from scratch after clearing them.
    I hate defaults.

    I'll C+P my group config (which as I am writing this I JUST thought of a way to make it 10X smaller due to me being an idiot. -.-)

    Here it is:

    http://pastie.org/3772552

    Originally my Default had -bukkit.* and Admin was Inheriting Default, so I thought that might be the problem, so I switched the -bukkit.* to the individual -bukkit. nodes in case the inheritance from default was canceling out.


    WHen I run /mangcheckp on any bukkit. node, it comes back saying they inherit it from Admin, but it reports Permission Node: null as to whether or not bukkit is reading them have it.

    dun de dun dun da dum

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 25, 2016
Thread Status:
Not open for further replies.

Share This Page