[ADMN/DEV] PermissionsBukkit v2.0 - Official Default Groups Plugin [1.5.2-R1.0]

Discussion in 'Archived: Plugin Releases' started by SpaceManiac, Jul 17, 2011.

  1. Offline

    SpaceManiac

    PermissionsBukkit - the Official Default Groups Plugin
    Current Version: v2.0
    Find PermissionsBukkit on BukkitDev!

    If you are getting a specific error or cannot determine what is wrong with your permissions file, filing a ticket on BukkitDev will make me much more likely to respond to you; general questions are best to ask in this thread or on the forums on BukkitDev.

    It's been a long time coming, but with the accomplishment of build 1000 Bukkit has finally accomplished a built-in Permissions system (codenamed Superperms). For more info on how they work, and how to integrate them with your plugin, see the official Permissions FAQ. Keep in mind that you should rarely, if ever, have to hook this plugin directly; instead keep things in the realm of checking player.hasPermission("yourplugin.node"). The FAQ thread has more info on how to use Superperms with things like chat prefixes/suffixes.

    Features:
    • Storage of users and groups in plugins/PermissionsBukkit/config.yml.
    • Both users and groups can be assigned individual permissions and parent groups to inherit permissions from.
    • Support for global and per-world permissions.
    • Reload configuration from file with out reloading the plugin.
    • Ability to check if a player has a specific permission node.
    • Ability to dump all permissions a player has and the plugins that set them.
    • Ability to print plugin, description, and default for a given permission node.
    • Ability to modify the permissions of groups and users and the groups of a user in-game.
    • Built-in antibuild via the "permissions.build" node (defaults to allowing anyone to build).
    • A minimalistic bridge from Permissions 3.0 to Superperms is available as a separate plugin, which does not depend on PermissionsBukkit.
    Command Usage:

    Show Spoiler
    PermissionsBukkit uses the command /permissions, with aliases /perms and /perm.

    /permissions reload - reload the configuration from disk.
    /permissions check <node> [player] - check if a player or the sender has a permission (any plugin).
    /permissions info <node> - prints information on a specific permission.
    /permissions dump [player] [page] - prints info about a player's (or the sender's) permissions.
    /permissions setrank <player> <group> - set a player to be in a group with per-group permissions.
    /permissions group - list group-related commands.
    /permissions group list - list all groups.
    /permissions group players <group> - list players in a group.
    /permissions group setperm <group> <[world:]node> [true|false] - set a permission on a group.
    /permissions group unsetperm <group> <[world:]node> - unset a permission on a group.
    /permissions player - list player-related commands.
    /permissions player groups <player> - list groups a player is in.
    /permissions player setgroup <player> <group,...> - set a player to be in only the given groups.
    /permissions player addgroup <player> <group> - add a player to a group.
    /permissions player removegroup <player> <group> - remove a player from a group.
    /permissions player setperm <player> <[world:]node> [true|false] - set a permission on a player.
    /permissions player unsetperm <player> <[world:]node> - unset a permission on a player.

    All commands have in-game help and are usable from the server console.

    Configuration:
    Show Spoiler
    A permission node is a string like 'permissions.build', usually starting with the name of the plugin. Refer to a plugin's documentation for what permissions it cares about. Each node should be followed by true to grant that permission or false to revoke it, as in 'permissions.build: true'. Some plugins provide permission nodes that map to a group of permissions - for example, PermissionsBukkit has 'permissions.*', which automatically grants permissions for all PermissionsBukkit commands. You can also specify false for permissions of this type.

    Users inherit permissions from the groups they are a part of. If a user is not specified here, or does not have a 'groups' node, they will be in the group 'default'. Permissions for individual users may also be specified by using a 'permissions' node with a list of permission nodes, which will override their group permissions. World permissions may be assigned to users with a 'worlds:' entry.

    Groups can be assigned to players and all their permissions will also be assigned to those players. Groups can also inherit permissions from other groups. Like user permissions, groups may override the permissions of their parent group(s). Unlike users, groups do NOT automatically inherit from default. World permissions may be assigned to groups with a 'worlds:' entry.

    The cannot-build message is configurable. If it is left blank, no message will be displayed to the player if PermissionsBukkit prevents them from building, digging, or interacting with a block. Use '&' characters to signify color codes.

    An example configuration file might look like this:
    Code:
    users:
        ConspiracyWizard:
            permissions:
                permissions.example: true
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
    

    Permissions:
    Show Spoiler
    PermissionsBukkit checks for the following permission nodes:
    • permissions.build - Allows a player to build. Defaults to true.
    • permissions.help - Allows viewing of usage for /permissions.
    • permissions.reload - Allows use of /permissions reload.
    • permissions.check - Allows use of /permissions reload.
    • permissions.info - Allows use of /permissions reload.
    • permissions.dump - Allows use of /permissions reload.
    • permissions.group.help - Allows viewing of usage for /permissions group.
    • permissions.group.list - Allows use of /permissions group list.
    • permissions.group.players - Allows use of /permissions group players.
    • permissions.group.setperm - Allows use of /permissions group setperm.
    • permissions.group.unsetperm - Allows use of /permissions group unsetperm.
    • permissions.player.help - Allows viewing of usage for /permissions player
    • permissions.player.groups - Allows use of /permissions player groups.
    • permissions.player.setgroup - Allows use of /permissions player setgroup.
    • permissions.player.addgroup - Allows use of /permissions player addgroup.
    • permissions.player.removegroup - Allows use of /permissions player removegroup.
    • permissions.player.setperm - Allows use of /permissions player addgroup.
    • permissions.player.unsetperm - Allows use of /permissions player removegroup.
    Also, the following parent nodes are provided for convenience:

    • permissions.* - Maps to permissions.help, .reload, .check, .info, .dump, and to permissions.group.* and permissions.player.*. Defaults to op.
    • permissions.group.* - Maps to permissions.group.help, .list, .players, .setperm, and .unsetperm.
    • permissions.player.* - Maps to permissions.player.help, .groups, .setgroup, .addgroup, .removegroup, .setperm, and .unsetperm.


    Frequently Asked Questions:
    1. Where are my * nodes? (open)
    Bukkit's Superperms has no built-in concept of a global '*' node that automatically gives all permissions, which is intentional - a player can instead be given all permissions by being given 'op' status (that is, listed in ops.txt). Additionally, individual plugins define a parent node (which could be 'pluginname.*' or 'pluginname.all' or anything else) which maps to whatever subpermissions in that plugin the author desires.

    An example is PermissionsBukkit, which provides three such permissions: 'permissions.group.*' for all /permissions group commands, 'permissions.player.*' for all /permissions player commands, and'permissions.*' for all /permissions commands (including permissions.group.* and permissions.player.*).

    If you are using SuperpermsBridge, you can do something similar to '*' nodes for plugins which use Permissions 2.7/3.1 - see the next FAQ for more information.
    2. How do I use SuperpermsBridge? (open)
    SuperpermsBridge is kind of like FakePermissions for GroupManager or PermissionsBridge for PermissionsEx. Once it's installed, it pretends to be the Permissions plugin and converts any plugins that use Permissions 2.7 or Permissions 3.1 to use Superperms instead.

    You can have PermissionsBukkit without SuperpermsBridge or SuperpermsBridge without PermissionsBukkit if you like, but both of these are limited in functionality. If you install SuperpermsBridge without PermissionsBukkit you will not be able to make use of PermissionsBukkit's groups feature or admin commands, and if you install PermissionsBukkit without SuperpermsBridge, plugins that have not updated to use Superperms directly will not function.

    For plugins that use Permissions 2.7/3.1, you can use the special node 'superpermbridge.*' to give the equivalent of what used to be the '*' node for plugins that do not use Superperms directly. If you don't want to give the * node, you can also use the node 'superpermbridge.pluginname' to do the equivalent of what used to be the 'pluginname.*' node. Once again, these only apply to plugins that SuperpermsBridge handles and not to plugins using Superperms directly.
    3. How do I use the root permissions.yml? (open)
    The file 'permissions.yml' in the root of your server can be used to set up custom parent permissions. Parent permissions are a single node that, when given to a player or group, automatically give all their children node. Here's a simple example:
    Code:
    server.basics:
        children:
            commandbook.motd: true
            commandbook.say: true
            commandbook.say.me: true
            commandbook.time: true
    
    Now, if you give a player the node 'server.basics', they automatically get all the nodes listed here. Children may also say 'false' instead of 'true', in which case giving the parent will remove the child instead of giving it.

    You can also specify a description if you like, which can be used by plugins to provide information on your node (such as PermissionsBukkit's /perm info command). If you want, you can also provide a default, which can be one of "true", "false", "op", or "notop". CraftBukkit will automatically assign everyone, no one (default), ops, or non-ops the children permissions based on the specified default. Without any plugin like PermissionsBukkit, you can use this defaults system as a limited way to assign people permissions. Here's a more complex example:
    Code:
    server.basics:
        description: Basic permissions for My Cool Server.
        default: true
        children:
            commandbook.motd: true
            commandbook.say: true
            commandbook.say.me: true
            commandbook.time: true
    server.admin:
        description: Admin permissions for My Cool Server.
        default: op
        children:
            commandbook.broadcast: true
            commandbook.teleport: true
            commandbook.kick: true
            commandbook.ban: true
    
    You can also define permissions without children, but this is of limited usefulness in permissions.yml (though is important in plugin.yml; see question #6)
    4. How do I switch from (other Permissions plugin)? (open)
    Depends on the Permissions plugin! If you were using PEX's YAML backend, I have a converter done and available on the PermissionsBukkit Tools page. Also available on the tools page is an automatic converter for Essentials GroupManager users.yml and groups.yml files. Automatic converters for Permissions 2.7 and 3.x are on their way, but in the meantime you can still convert your configurations manually.
    5. Where are prefixes and suffixes (or option nodes)? (open)
    Bukkit Superperms has no built-in prefix/suffix settings or non-boolean permission nodes, so individual chat plugins will have to start supporting Superperms in order to make use of non-Permissions-plugin based prefixes and suffixes. Herochat, iChat, and Simple Suffix are all aware of the Superperms update, but in the meantime you can use mChat, which already supports Superperms.

    Once you install mChat and configure the mchat.prefix, mchat.suffix, and mchat.group names in its configuration file (see the example), use PermissionsBukkit to give players or groups the permissions "mchat.prefix.admin", replacing "admin" with whatever node you configured. For example, with an mchat configuration that looks similar to this:
    Code:
    da-name-format: '+prefix+name&e'
    date-format: HH:mm:ss
    message-format: '+prefix+name&f: +message'
    mchat:
        prefix:
            admin: '&4DtK [SO] &7 '
            sadmin: '&9DtK [SA] &7 '
            jadmin: '&aDtK [JA] &7  '
            member: '&cDtK [M] &7 '
    
    You can assign players or groups the mchat.prefix.admin node to get the "SO" prefix, mchat.prefix.sadmin to get the "SA" prefix, and so on.
    6. (Coders) How do I set up my plugin.yml? (open)
    Take a look at this post in Dinnerbone's FAQ for an example. This is a lot like the setup of permissions.yml (see above), but you can also define non-parent permissions (just include description and default and leave out children).
    7. Is PermissionsBukkit outdated? (open)
    No! PermissionsBukkit 2.0 was last updated for 1.3.1-R2.0, is verified to work on 1.4.7-R1.0, and is unlikely to break on future releases.

    Downloads:
    Current Version:

    PermissionsBukkit v2.0 (jar) (details)
    Old Versions:
    PermissionsBukkit v1.6 (jar) (details)

    [​IMG]

    Changelog:

    Friday 7 September 2012 (2.0)
    • Fixed a case-sensitivity issue with setting per-world permissions that could cause some permissions to fail to apply.
    • Added /perm setrank <player> <group> subcommand (alias rank) with per-group permissions (permissions.setrank and permissions.setrank.<group>)
    • Added plugin metrics via http://mcstats.org/plugin/PermissionsBukkitMCStats (disableable in plugins/PluginMetrics/config.yml)
    Wednesday 29 February 2012 (1.6)
    • Fixed some massive issues that were caused due to having uploaded a buggy, in-development version instead of 1.5.
    • Note: If your configuration was messed up as a result of this issue, the new build should gradually correct it as needed.
    Saturday 25 February 2012 (1.5b)
    • Revamped to be compatible with R5.
    • Fixed issues with permissions not carrying properly on world change.
    • Many internal improvements for performance and stability.
    • SuperpermsBridge: in honor of R5 removing deprecated code, SuperpermsBridge is officially gone!
    Monday 18 July 2011 (1.1/1.2)
    • Fix BukkitContrib incompatibility issues.
    • Improved the output of the /perm check command.
    • Fixed issues when 'users:' is not specified in the config file.
    • Fixed the /permissions reload command.
    • SuperpermsBridge: improve wildcard handling; in addition to 'superpermbridge.*' and 'superpermbridge.pluginname', now supported are 'superpermbridge.plugin.*', 'superpermbridge.plugin.subnode.*', and so on.
    Monday 18 July 2011 (1.0/1.1)
    • SuperpermsBridge: adding the special 'superpermbridge.*' and 'superpermbridge.pluginname' nodes (see #2 in the FAQ for details).
    Sunday 17 July 2011 (1.0/1.0)

    • Initial release of PermissionsBukkit v1.0 and SuperpermsBridge v1.0.
     
    madmac, Gesundheit, tripleX and 23 others like this.
  2. Offline

    Flatliner

    It's like you read my mind :) I've been using the vanilla client for all my tests but switching to the spout client hasn't helped. Oh yeah, I mentioned this a few posts ago, but I never bothered to ask what this logging actually means. This was after I enabled debugging many posts ago:

    Code:
    14:17:25 [INFO] [PermissionsBukkit] [Debug] Player Flatliner_ quit, unregistering...
    14:17:25 [INFO] [PermissionsBukkit] [Debug] Unregistering Flatliner_: player did not have attachment
    Where it says player did not have attachment, that's the only thing I've been able to find in the logs that's different. It always shows that if I disconnect after losing my permissions from a reload. Normally when I have my permissions, if I leave it just says I left.

    It makes it sound like after a reload I'm not getting "re-attached" to permissionsbukkit.
     
  3. Offline

    Celtic Minstrel

    @midget_3111 – He knows, it's just that the other plugins he is using apparently aren't.

    @Mercury – If you intend to switch over to PermissionsBukkit, I would recommend switching entirely rather than running two permissions systems in parallel. There is another option though. You could instead switch to PermissionsEx, which would be able to handle SpoutEssentials as well as your plugins that expect Permissions. I'm not 100% sure, but you might even be able to use your existing config without any changes.
     
  4. Offline

    ShAd0w2kXX

    Hello there.
    Kinda new to bukkit so I'm not sure what I'm doing wrong but;
    Per world permissions I have set seem to persist between worlds when they're not supposed to. I'm just curious if I've done anything wrong. Here's a snapshot of what my permissions file looks like.
    Code:
    users:
        Shadow:
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: true
                SuperSigns.UseAll: true
                SuperSigns.CreateAll: true
                superpermbridge.XcraftGate.use.*: true
                chestlock.own: true
                chestlock.lock: true
                chestlock.unlockable: true
                chestlock.usekey: true
                chestlock.free: true
                deathpenalty.losemoney: true
                fruitful.drop.*: true
                iConomy.access: true
                iConomy.bank.access: true
                iConomy.bank.deposit: true
                iConomy.bank.join: true
                iConomy.bank.main: true
                iConomy.bank.transfer: true
                iConomy.bank.withdraw: true
                iConomy.list: true
                iConomy.payment: true
                showcase.basic: true
                signlift.create.*: true
                signlift.use.normal: true
                signlift.use.private.own: true
                SignShop.Signs.*: true
                sortal.createwarp: true
                sortal.warp: true
                sortal.register: true
                epicquest.*: true
                mobbounty.collect: true
                war.player: true
                war.warp: true
                autocraft.transport: true
                choptree.chop: true
                admincmd.spawn.tp: true
            worlds:
                Shadow:
                    admincmd.time.*: true
                    admincmd.item.add: true
                    admincmd.tp.home: true
                    admincmd.tp.players: true
                    admincmd.player.god: true
                    admincmd.player.clear: true
                    admincmd.weather.clear: true
                    instabreak.toggle: true
                    admincmd.player.fly: true
        admin:
            permissions:
                superpermbridge.*: true
                simpleprefix.admin: true
            inheritance:
            - mod
        mod:
            permissions:
                permissions.build: true
                simpleprefix.mod: true
                admincmd.player.kick: true
            inheritance:
            - default
        adventurer:
            permissions:
                permission.build: false
                simpleprefix.adventurer: true
    messages:
        build: '&cYou cannot do that.'
    
    As far as I can tell I have followed everything exactly. The issue is that my world "Shadow" is a creative world, so as you can see I've added permissions for spawning and flying and such. But I have other worlds that are strictly legit survival worlds that shouldn't have those permissions enabled, yet my friend can spawn items in both "Shadow" and "Survival" (my survival world :p)(Before anyone says anything, YES I named my creative world after my player name :p)
    Is there something wrong here? Any help would be great :D
    EDIT: Ive tried setting the permissions to a different group and it seems that PermissionsBukkit is just ignoring the worlds: tag all together. I'm not sure what the issue is, but at the moment it is impossible for me to set it so that people can use specific commands in only one world.
     
  5. Offline

    xaviergmail

    Oh god I can be dumb sometimes ._. thanks a lot!
     
  6. Offline

    CaptainPrice943

    Hi.
    I'm new to this forum, so pardon me if the way I posted my code is... Uhhh... Messy?
    Anyways. Here is my code for the config.yml file created by PermissionsBukkit.jar (i got it out of a folder and edited it)
    users:
    Code:
     CaptainPrice943:
            permissions:
                permissions.example: true
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: true
                essentials.spawn
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.' [code]
    
    Whenever I try to change it and give myself new permissions it doesn't work. And when I posted myself as admin nothing shows up in-game. To reload my server, i have tried using the reload command, and stopping the server and turning it back on.
    What am I doing wrong?
    If you tell me how to put it into the code thing, i can do that

    Okay. I put my code into a YAML parser. I figured out the bug that caused the command problem, but i still can't make myself admin

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 17, 2016
  7. This is a known issue in 1.1, have you tried the latest dev build @ http://ci.onarandombox.com/job/Perm.../target/bukkit-permissions-0.1.0-SNAPSHOT.jar


    Edit: didn't notice someone had already beaten me to it
     
  8. Offline

    CaptainPrice943

    Yeah I figured it out myself. Thanks
    And, when I try to use a node like worldedit.* to give myself all the commands. Why doesnt it work?
     
  9. Offline

    ShAd0w2kXX

    Thanks! It works perfectly now! :D
    I'm not sure if this is the best answer, but I've noticed that if a permissions node doesn't work on it's own, it seems to work fine if used with superpermbridge. For example, my command 'XCraftGate.use.*' didn't work on it's own, but 'superpermbridge.XCraftGate.use.*' worked fine.
    No harm in trying it I guess. ^^
     
  10. Offline

    Phat32

    Does PermissonsBukkit work with multiworld? I don't see a way to have different configs for different worlds
     
  11. Yeah it works. see this example the guy posted above you:

    Code:
    users:
        CaptainPrice943:
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: true
                essentials.spawn
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default


    the coolplugin.item node is only true in world "creative."
     
  12. Ok. I maked permissions today for a server off my friend. But it does not work. But they can build... Realy weird.
    Code:
    ##############################################
    #--------------------------------------------#
    #-------------------USERS--------------------#
    #--------------------------------------------#
    ##############################################
    users:
        NAAM:
            permissions:
            groups:
            - default
        Niellz:
            permissions:
            groups:
            - admin
        PoisonDragon:
            permissions:
            groups: 
            - mod
        Hahstom:
            permissions:
            groups:
            - mod
        Wartynewt:
            permissions:
            groups:
            - default
        No_pixels:
            permissions:
            groups:
            - default
        Doemsdagding:
            permissions:
            groups:
            - default
        Mikalpark:
            permissions:
            groups:
            - default
        Flappie134:
            permissions:
            groups:
            - default
        W3ssl3y:
            permissions:
            groups:
            - default
        Ibooja:
            permissions:
            groups:
            - default
        Nickwout6:
            permissions:
            groups:
            - default
        Woutboy6:
            permissions:
            groups:
            - default
        NeatlyMaxed:
            permissions:
            groups:
            - default 
        Dobbeuh:
            permissions:
            groups:
            - default
        147eragon:
            permissions:
            groups:
            - default
        Coolwess:
            permissions:
            groups:
            - default
        Kenny_13:
            permissions:
            groups:
            - default
        KennyPlox:
            permissions:
            groups:
            - default
        Offer:
            permissions:
            groups:
            - default
        Thedutchkid100:
            permissions:
            groups:
            - default
        Theezakj:
            permissions:
            groups:
            - default
        Thunderwave8:
            permissions:
            groups:
            - default
        Tijmtio:
            permissions:
            groups:
            - default
        Woutboyj:
            permissions:
             - default
    ##############################################
    #--------------------------------------------#
    #------------------GROUPS--------------------#
    #--------------------------------------------#
    ##############################################
    groups:
        default:
            permissions:
                permissions.build: true
                changename.own: true
                changename.get: true
                craftbook.mech.ammeter.use: true
                craftbook.mech.bridge: true
                craftbook.mech.bookshelf.use: true
                craftbook.mech.cauldron: true
                craftbook.mech.elevator: true
                craftbook.mech.elevator.use: true
                craftbook.mech.gate: true
                craftbook.mech.light-switch: true
                craftbook.ic.safe.*: true
                craftbook.ic.restricted.*: true
                kff.teleport: true
                kff.lookAt: true
                kff.coordinates: true
                lockette.user.create.chest: true
                lockette.user.create.dispenser: true
                lockette.user.create.door: true
                lockette.user.create.furnace: true
                simpletime.day: true
                simpletime.night: true
                simpletime.sunrise: true
                simpletime.sunset: true
                simpletime.sun: true
                simpletime.rain: true
                simpletime.thunder: true
                simpletime.help: true
                simpletime.version: true
                spawnmob.kill.monsters: true
                spawnmob.kill.animals: true
                spawnmob.kill.all: true
                SpawnX.spawn: true
                warpy.warp: true
                warpy.list: true
        mod:
            permissions:
                permissions.build: true
                appleseed.plant.*: true
                appleseed.plant.apple: true
                ppleseed.infinite.plant: true
                appleseed.infinite.fertilizer: true
                appleseed.wand: true
                appleseed.sign.place: true
                changename.other: true
                lockette.admin.create.chest: true
                lockette.admin.create.dispenser: true
                lockette.admin.create.door: true
                lockette.admin.create.furnace: true
                lockette.admin.break: true
                lockette.admin.bypass: true
                lockette.admin.snoop: true
                OpenInv.openinv: true
                OpenInv.search: true
                OpenInv.crossworld: true
                OpenInv.exempt: true
                OpenInv.override: true
                warpy.add: true
                warpy.remove: true
                permissions.player.addgroup: true
            inheritance:
            - default
        admin:
            permissions:
                permissions.build: true
                permissions.help: true
                permissions.reload: true
                permissions.player.chek: true
                permissions.info: true
                permissions.dump: true
                permissions.group.help: true
                permissions.group.list: true
                permissions.group.setperm: true
                permissions.group.unsetperm: true
                permissions.player.help: true
                permissions.palyer.groups: true
                permissions.player.setgroups: true
                permissions.player.addgroups: true
                permissions.player.removegroups: true
                permissions.player.setperm: true
                permissions.player.unsetperm: true
                lockette.admin.restart: true
                spawnmob.kits: true
                spawnmob.wolf.tamed: true
                spawnmob.creeper.electrocuted: true
                spawnmob.kill.all: true
                spawnmob.mspawn.delay: true
                spawnmob.mspawn.chek: true
                SpawnX.setspawn: true
            inheritance:
            - mod
       
    messages:
        build: '&cJe hebt het recht niet om hier te bouwen!'
    
    
     
  13. Offline

    G180397

    Is it possible to assign different groups to users depending on their world?
    Thankyou for your time
     
  14. Ya. Tho in users:
    World:
    blbablabla:
    group:
    -balbala

    (PS.Im not sure)
     
  15. Offline

    92921376

    The server console won't even recognize permissions commands at all and my mods that require permissions won't work. Here is my config file:
    Code:
    users:
        ConspiracyWizard:
            permissions:
                permissions.example: true
            groups:
            - admin
        '92921376':
            permissions:
                mobbounty.collect: true
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
                mobbounty.collect
                mobbounty.commands.mb
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission!'
    
     
  16. Offline

    TheMadMan697

    try use
    superpermbridge.worldedit.*

    (if you are using superpermbridge that is)
     
  17. Offline

    moselekm

    You guys are amazing. This one thing basically taught me how to do set permissions properly.

    superpermbridge.xxxxx.xxxxxx noding is a nice little trick to make certain plugin permissions work. Thanks so much!
     
  18. Offline

    G180397

    That didn't work but thanks anyway
     
  19. Offline

    Tech_BuRn

    I've got an issue with permissions handling different worlds. Group A has access to plugin.example when in world1 but not in world2. Which is what I want, however the only way the permissions are enforced is when the player disconnects and reconnects or the /permissions reload command is used. I guess permissions doesn't refresh or check what world a player warps to and assign the correct permission? I'm using craftbukkit 1051 bukkit permissions 1.1 and DefaultCommands -DEV (has basic bukkitperm support)
    Is there a fix for this or is this a problem with DefaultCommands perhaps? I'm using the multi-world support built into vildaberper's DefaultCommands.
     
  20. Offline

    krinsdeath

    The only way to do this would be to set up different groups with different permissions on different worlds, and then assign ~all~ of those groups to that user.
    Code:
    users:
      exampleGuy:
        groups:
        - world_users
        - world_nether_users
      theUser:
        groups:
        - world_users
        - skyland_users
    groups:
      world_users:
        worlds:
          world:
            some.node: true
      world_nether_users:
        worlds:
          world_nether:
            some.other.node: true
      skyland_users:
        worlds:
          world_skylands:
            some.skyland.node: true
    
    Update to the latest dev build here.

    @mikelong1994 - Weird problem. I'm unfamiliar with ChopTree, but it may not be compatible with Superperms. As for worldedit, try poking around in the config and seeing if any keys jump out at you - it may be ignoring your permissionsbukkit (I know commandbook has a "default ops to all permissions" feature, so).

    Also, in the future, paste your configs into [code][/code] tags or pastebin, so that they retain their formatting and we can tell if there's an indentation or syntax problem.
     
  21. Offline

    vSanjo

    First off, amazing work you're all doing - whilst i'm sure the problems around are just teething problems, it's exciting watching the progress! :D

    My problem(s) are few but probably something simple i'm missing.
    Firstly, mChat wasn't recognising admins from users, etc. I've traced this back to PermissionsBukkit not grouping users properly. It's very weird, actually. If I set someone as an admin (lord), they are put into the user (villager) group but is noted as admin in the config.yml. I thought it was something to do with being an OP, or whatever - but even setting a person to an OP changes nothing, they're still at user level of permissions.

    I may be using PermissionsBukkit wrong, but I hope someone can have a look at the files in question and see what (if anything on my side) needs fixing. There's a few other plugins not working as they should (read: not at all) such as BiomeSound, egtCaelumProcurator, TexturePackChooser - so I reckon i'm doing something stupid to be honest.

    mChat:
    config.yml
    info.yml

    PermissionsBukkit:
    config.yml

    Permissions:
    permissions.yml

    If you require anything else, just ask. :)
     
  22. Offline

    Celtic Minstrel

    @vSanjo – I think you need to give permissions in PermissionsBukkit in order to assign prefixes to users. I'm not sure how that works with mChat though.
     
  23. Offline

    vSanjo

    Each group does have permission for mChat. It's not actually mChat breaking - it's PermissionsBukkit not changing player groups properly or giving the right permissions (saying a user is in one group but giving permissions of another).
     
  24. Offline

    theakore

    Whenever someone on the server uses the servers /reload command (not /permissions reload), it's like permissions bukkit ignores the config.yml everyone on the server is put into the default group and no one has access to any commands. the logs dont show any errors. this is a pretty big issue! please help!

    edit: after the server wide /reload the permissions bukkit /reload command does not fix the issue.
     
  25. Offline

    Captain Kirk

    do you have to do the true thing after each command... Like

    bb.admin.info: true
     
  26. Offline

    vSanjo

    I'd like to add to my previous problem that I also have this occurring too.
     
  27. Offline

    Zocomen

    Getting this error when I log in:
    Code:
    2011-08-13 21:04:16 [INFO] Zocomen [/90.224.83.158:55404] logged in with entity id 110 at ([Vanguard] -133.4375, 67.0, 117.375)
    2011-08-13 21:04:16 [SEVERE] Exception in thread "Thread-210"
    2011-08-13 21:04:16 [SEVERE] java.lang.NoSuchMethodError: com.nijiko.permissions.PermissionHandler.getUserObject(Ljava/lang/String;Ljava/lang/String;)Lcom/nijiko/permissions/User;
    2011-08-13 21:04:16 [SEVERE]     at me.kalmanolah.okb3.OKmain.CheckPermission(OKmain.java:408)
    2011-08-13 21:04:16 [SEVERE]     at me.kalmanolah.okb3.OKRunnable.run(OKRunnable.java:156)
    2011-08-13 21:04:16 [SEVERE]     at java.lang.Thread.run(Thread.java:636)
    Also, even if I set superpermbridge.* in my permissions for me, It don't give me permission's for some plugins.
    For example, Citizens. I can't create a simple npc.
    Not getting any error of that problem.
    Please help ASAP.
     
  28. Offline

    rmb938

    Not sure if this is a bukkit bug or what. But sometimes when a person switch worlds there group name adds a capital. So like if their group is master it says they are in Master and they don't get the permissions.
     
  29. Offline

    Celtic Minstrel

    @Captain Kirk – Yes, or you can put false instead to revoke that permission.

    @Zocomen – superpermbridge.* does not give all permissions. I'd guess that Citizens works properly without using the bridge, which means you'll need to look up how to give all Citizens permissions. Most likely it'll be something like citizens.* or citizens.all.
     
  30. Offline

    Zocomen

    What permission node give's all the permission's then?
    Edit: You know how to solve the error too?
     
  31. Offline

    RoKGeppie

    this plugin is pure junk, it doesnt auto add players to groups like phoenix's plugin did, and its barely compatible with any plugins, using this plugin is a server owners worst nightmare.
     

Share This Page