[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. 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

    mrgreaper

    AH HA! JACKPOT
    just noticed the update, updated both of them now superpermbridge.myhome.home.basic.* works! so now for all the ones i have a problem with i just need to add superpermbridge. infront of and in theory (about to test that) it should work

    still no joy with with mchat :( but then you cant have everything (where would you keep it?)

     
  3. Okay, i tried a to add a simple permission node...

    Code:
    groups:
        default:
            permissions:
                permissions.build: false
                superpermsbridge.essentials.kick: true
                superpermsbridge.essentials.list: true
    
    Result:

    Code:
    2011-07-19 03:22:27 [INFO] crysis992 tried to use command /list
    2011-07-19 03:22:27 [INFO]  [PLAYER_COMMAND] crysis992: /list 
    2011-07-19 03:22:27 [WARNING] crysis992 was denied access to command.
    
    Im out of ideas how to setup it correctly :/
     
  4. Offline

    Bronski

    Are you saying we have to have a group called 'default' as the lowest rank? I seem to have it working with it changed to 'noob' but I'll change it back if it's going to cause a problem. And yes, I can use mchat to display it as something different or whatever.

    @mchat people... I posted my configs on that forum post. I think I got it working (though not completely pretty). YMMV :D
     
  5. Offline

    mrgreaper

  6. Offline

    HunterAP

    Reload delay... So I've been doing some testing trying to figure out what's up with what, and I've been seeing a pretty significant delay between the time that I modify or add a permission, and the time that it actually goes into effect. Using the reload command doesn't seem to speed up the process at all. It might be related to having another mod installed. Here is my current mod list:
    BigCatch, ChopTree, CommandBook, CraftBukkitUpToDate, Dynmap, Bukkitcontrib, Help, HeroChat, Hungry, Landmarks, LibertasLoader, MCMMO, MultiInv, PerformanceTweaks, RestartNow, SelfClosingDoors, ShelfSpeak, WorldEdit, WormholeXtreme, WormholeXtremeWorlds, and ZombieAttack.
    Forget this, didn't see the update at the top. Installing the update to see if it takes care of the problem.
     
  7. Offline

    mrgreaper

    been doing a lot of testing and commands have been instant for me

    if it helps i share the following plugins
    CommandBook, Dynmap, Bukkitcontrib, Landmarks, MCMMO, WorldEdit, WormholeXtreme

    (we have around 50+ plugins and no lag :) )
     
  8. Offline

    HunterAP

    Yeah, I edited my post. I missed the 1.1 update. Waiting on my users to finish something up before installing the update.
     
  9. Offline

    mrgreaper

    im lucky no one online at this time of night ..hmmm that could explain the lack of lag..

    from one admin to another goodluck chap

    i need to go play something with circles in it before i go insane (insaner)
     
  10. Offline

    VeryInsane

    Okay. Well I'm using heroChat for my prefix/suffix. Just sayin :p
     
  11. Offline

    HunterAP

    The delay between "/permissions reload" and things actually changing is fixed. Also, the error on logout is fixed. I'm currently going through and adding all of the individual permissions for my plugins.
     
  12. Offline

    Bronski

    Code:
    23:03:58 [INFO] Server permissions file permissions.yml is empty, ignoring it
    23:03:58 [INFO] Done (0.551s)! For help, type "help" or "?"
    Is that message coming from this plugin?

    I thought everything was in PermissionsBukkit/config.yml now. I do have this in my bukkit.yml file (root directory):

    Code:
        permissions-file: permissions.yml
    ... but I'm not sure why that line is there, where that file would reside, or what it's supposed to contain :D

    Permissions do seem to be working ok for me otherwise.

    Thanks.
     
  13. Offline

    mrgreaper

    have a look at the faq link in the first post then the for serverowners bit, seems to be a way we can group permissions so we can add say mcmmo.ability.* mcmmo.stats.* mcmmo.ptp to a created rpg.ourserver, then we only have to give people rpg.ourserver .... the permission.yml is located at the root of the server.... personly im gonna avoid it im used to using groups and shall stick to them

    think the error can be safely ignored :)
     
  14. For whatever reason your config appears to have contained some kind of invalid character. I filtered out all of the users who were just in the default group and that got rid of it, so here's an updated config.


    Make sure you have the latest PermissionsBukkit and SuperpermsBridge and get back to me.

    Yeah, right now if a player is not defined in the config.yml or do not have a 'groups:' node (they can have an empty one to be in no groups) they will inherit from the group named 'default'. Just changing 'noob' to 'default' will make first-joiners fall into it automatically.

    Alright, great to hear. Thanks for sharing your config with everyone else and thanks for all the other detailed posts about your problems.

    The Heroes team is aware of the Superperms issue but have told me it is low priority and probably will not be added until the next major release of HeroChat (HeroChat 5).

    Alright, good to hear.

    Take a look at FAQ question #3. Also mrgreaper explained it pretty well.

    In other news, got the Permissions 2.7/3.x converter almost done and will begin work on adding an mChat configuration generator to the existing converters for prefixes/suffixes.
     
  15. Offline

    Urahara72

    I cannot figure this out correctly. If someone can walk me through step by step to get this working with all of my plugins I would greatly appreciate it!
     
  16. Offline

    HunterAP

    When changing worlds, permissions do not change to match the world that you are joining. I tested this with several different users. I could force the permissions to update by doing "/permissions reload" but otherwise, the permissions stick around.

    If I assign a permission in a world to true, the permission seems to be globally set to true unless I set it to false globally. I don't think that it should work this way. I think that if I set a permission to true for a specific world, it should just be true for that world without having to explicitly define it as false globally.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 17, 2016
  17. Alright, if you could hop onto the Bukkit IRC (#bukkit on irc.esper.net) and ping me (just say SpaceManiac) I'll be able to get this worked out with you quicker. Helps me test fixes if I can just give you an update there.
     
  18. Offline

    Urahara72

    hello? you stopped responding
     
  19. Offline

    0mi4

    wtf( all people in my server start use /give diamond 64:D
     
  20. Offline

    AskCharlie

    idk if im posting this to the correct forum post, I believe this has something to do with permissionsbukkit, please correct me if I am wrong.

    When I hit escape and disconnect from the server this ALWAYS pops up for each user that exits that way...

    any ideas? it looks like it has to do with Bukkit Contrib as well.
     
  21. Redownload PermissionsBukkit, looks like your download got corrupted. You probably want SuperpermsBridge too.

    Make sure you have PermissionsBukkit 1.1.
     
  22. Offline

    Bronski

    This was likely reported, but if I reload on the console it seems perms all get reset to nothing (ie. I lose access to all commands as admin).​
    Thanks.​
     
  23. Offline

    ValBGaming

    One question... Can this do what Permissions 3.1.6 can do? Like, groups (With a default group), prefix/suffix, and group inheritance? If so I'll be happy to switch over, if not... *sigh* I want to switch over but if it can't do those things, then I can't...
     
  24. Offline

    Bronski

    I'm doing that with this and mchat for prefix/suffix and it seems to be working. Be prepared to put some time into it though.
     
  25. Offline

    Bukket

    Can you help me? I have a problem. I tried to give right to teleport to spawn but every time i tried not as admin it got denied It says you don't have permission..Here is the code. Please Come Back To me soon.
    PHP:
    users:
        
    ConspiracyWizard:
            
    permissions:
                
    permissions.exampletrue
                commandbook
    .spawntrue

            worlds
    :
            
    groups:
            - 
    admin
    groups
    :
        default:
            
    permissions:
                
    permissions.buildtrue
                commandbook
    .spawntrue
            worlds
    :
        
    admin:
            
    permissions:
                
    permissions.*: true
            inheritance
    :
            - 
    user
        user
    :
            
    permissions:
                
    permissions.buildtrue
                commandbook
    .spawntrue
            worlds
    :
                
    creative:
                    
    coolplugin.itemtrue
            inheritance
    :
            - default
    Also I have this problem. I think this is causing the other problem. This is my log
    http://pastebin.com/1cjfjycY

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 17, 2016
  26. I am unable to replicate this problem. Are you up to date?
    The leading whitespace on each line needs to be spaces. Tabs will break the YAML parser. That should fix your problem.
     
  27. Offline

    babystompa

    I'm using PermissionsBucket and DefaultPlugin and i'm not sure what i'm doing wrong. I'm getting expected ':' errors
    Code:
    users:
        babystompa:
            permissions:
                permissions.build: true
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: true
                dc.warps: true
                dc.warp: true
                dc.sethome: true
                dc.home: true
                dc.online: true
        mod:
            permissions:
                dc.time: true
                dc.spawnmob: true
                dc.creative: true
                dc.lightning: true
                dc.health: true
                dc.fly: true
                dc.teleport: true
                dc.god: true
                dc.setwarp: true
            inheritance:
            -default
        admin:
            permissions:
                permissions.*: true
            inheritance:
            -mod       
    Code:
    [SEVERE] Could not load 'plugins\PermissionsBukkit-1.1.jar' in folder 'plugins':
    while scanning a simple key
     in "<reader>", line 57, column 9:
                -default
                ^
    could not found expected ':'
     in "<reader>", line 58, column 5:
            admin:
            ^
    
        at org.yaml.snakeyaml.scanner.ScannerImpl.stalePossibleSimpleKeys(ScannerImpl.java:400)
        at org.yaml.snakeyaml.scanner.ScannerImpl.needMoreTokens(ScannerImpl.java:231)
        at org.yaml.snakeyaml.scanner.ScannerImpl.checkToken(ScannerImpl.java:182)
        at org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingValue.produce(ParserImpl.java:592)
        at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:163)
        at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:148)
        at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:132)
        at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230)
        at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:160)
        at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230)
        at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:160)
        at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230)
        at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:160)
        at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:122)
        at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105)
        at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:124)
        at org.yaml.snakeyaml.Yaml.load(Yaml.java:264)
        at org.bukkit.util.config.Configuration.load(Configuration.java:82)
        at org.bukkit.plugin.java.JavaPlugin.initialize(JavaPlugin.java:157)
        at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:175)
        at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:207)
        at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:130)
        at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:128)
        at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer.java:97)
        at net.minecraft.server.ServerConfigurationManager.<init>(ServerConfigurationManager.java:51)
        at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:132)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:335)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)
     
  28. There needs to be a space between any line starting with - and the string following it.

    Code:
    admin:
        permissions:
            permissions.*: true
        inheritance:
        - mod
    
     
  29. Offline

    babystompa

    I thank you greatly for the speedy reply but with DefaultPlugin I'm still able to use all the commands without being on the OPS or Listed as an admin
     
  30. Sorry, I didn't really read your post that closely. Download SuperPermsBridge, and that should fix your problem. I am guessing it's because DefaultCommands hasn't updated to the new permissions schema yet, so you'll need SuperPerms to bridge the gap while that is implemented.
     
  31. Offline

    Bukket

    I did what you say but i keep getting errors. Im using commandbook with permissions bukkit. Do I need SuperPermsBridge?
     

Share This Page