[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

    ftr

    Ok I am searching for help with permissions.

    It all worked, then I added some commands (before I just had /time and /tp commands added). And then it stopped working. I am searching for error long time already and I can't find it at all!

    So anyone please help me.

    This is how my config file looks like.

    Code:
    users:
          user1:
            permissions:
            groups:
            - admin
          user2:
            permissions:
            groups:
            - admin
        user3:
            permissions:
            groups:
            - user
          user4:
            permissions:
            groups:
            - user
        user5:
            permissions:
            groups:
            - user
          user6:
            permissions:
            groups:
            - user
          user7:
            permissions:
            groups:
            - user
        user8:
            permissions:
            groups:
            - default
        user9:
            permissions:
            groups:
            - default
    groups:
        default:
            permissions:
                permissions.build: false
                essentials.ping: true
        admin:
            permissions:
                permissions.*: true
                essentials.seen: true
                essentials.whois: true
                essentials.ban: true
                essentials.ban.exempt: true
                essentials.ban.notify: true
                essentials.ban.offline: true
                essentials.banip: true
                essentials.essentials: true
                essentials.tpall: true
                essentials.mute: true
                essentials.mute.exempt: true
                essentials.kick: true
                essentials.kick.exempt: true
                essentials.kick.notify: true
                essentials.kickall: true
                essentials.gc: true
                essentials.burn: true
                essentials.realname: true
                essentials.nick: true
                essentials.nick.others: true
                essentials.nick.color: true
    inheritance:
            - user
        user:
            permissions:
                permissions.build: true
                essentials.tp: true
                essentials.tpohere: true
                essentials.time: true
                essentials.time.set: true
                essentials.thunder: true
                essentials.weather: true
                essentials.suicide: true
                essentials.me: true
                essentials.help: true
                permissions.reload: true 
                essentials.ping: true
    inheritance:
            - default 
    messages:
        build: '&cYou do not have permission to build here.'
    
    If anyone tell me where I did mistake I will be glad!

    EDIT: I just read two post up to my and edited my config files, I reduced it to one group for test and it works! I will try to fully reconfigure it and see if it work.
     
  3. Offline

    axlsjolund

    Idk about the rest of you, but I can't get permissions.yml and PermissionsBukkit to play nice for the life of me.

    Everything is configured properly. Everything is updated. Running /permissions commands in-game to test that users/groups have access to specific nodes returns a true value, which means it recognizes that they do indeed have the permissions. But when a user goes to use said command, the server tells them they do not have permission.

    Seems to be a server contradiction.

    Any ideas as to the reason? Or better yet, anyone know a solution? Maybe a new build I am missing?
     
  4. Offline

    HAWKEYE10

    Ok so i installed this plugin but know every once in awhile the people and what rank they are changes
     
  5. Offline

    NumQuamRetro

    Hello everybody,

    i've installed PermissionsBukkit completely.
    But i've a question: What need i to write into the config.yml, to make two groups:
    Admins - Which can do all, op someone , deop etc.
    and
    Mods - Which are ops but CANT deop someone and cant OP someone and can only kick someone but dont ban??
    (and then the default and user groups, we do not have to talk about them)

    Hope for a speedy response.

    Thanks.
    NumQuamRetro
     
  6. Offline

    coolo1

    Ok, I have fixed basically everything now, but whenever someone joins my server I get http://pastebin.com/uzV0DHmC etc, etc. It fills heaps of space, annoys me and makes a massive lag spike. If I try to do any /permissions commands ingame the same kind of thing happens, I can post the error from that too if you want, and it says and internal error has occurred. Please help, this is really bugging me.
    [Edit] I forgot to mention, whenever I use /help it says Do you need halp?
     
  7. Offline

    FlingeR

    Hi everyone:
    I have this problem:
    I have the following groups: "default", "user", "mod" and "admin".

    How can I avoid that a member of the "mod" group change his own or another member of the sane group to the "admin" group ?
     
  8. Offline

    Sabersamus


    are you using the default permissions.yml in the root of your server?

    mod:
    permissions:
    permissions.*: false
    permissions.build: true
    permissions. (anything) relates to the Permissionsbukkit plugin, having permissions.* makes it so everything (other than build in the config above ^^) in the permissions plugin is not accessible for that group

    http://pastebin.com/8V1fe6LG
    this is assuming you dont use a different plugin for kicks and bans

    install a plugin for /help :3
    the bukkit default only works for ops.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Jul 14, 2016
  9. Offline

    Reytiger

    Silly problem with getting permissions.yml to give the children nodes to users.
    I tried a simple test with a single node.

    permissions.yml (in root directory)
    Code:
    test.node:
        children:
            test2.node: true
    
    config.yml (in the /plugins/PermissionsBukkit directory)
    Code:
    users:
        ReyTiger:
            permissions:
                test.node: true
    groups:
    ....
    using /perms check, PermissionsBukkit recognizes that I have test.node, but not test2.node.

    Pretty sure there's some glaring issue here that I'm missing.
     
  10. Offline

    coolo1

    I installed HelpPlus, but now if you use /help or /hp it kicks everyone off the server.
    [Edit] Also when I start my server it says that Help Plus [Info] Found config file. Loading overridden commands...
     
  11. Offline

    Foerster44

    I tried to follow Lynxdragon's instructions, but it didn't work somehow, it's still spitting out errors :( ...
    Can please someone say me what the problem is?
    Here's the permissions.yml:
    Show Spoiler
    default:
    children:
    permissions.build: false
    permissions.help: true

    admin:
    children:
    permissions.*: true
    CreeperHeal.*: true
    deathtpplus.*: true
    mcmmo.*: true
    monsterhunt.admincmd.huntstart: true
    monsterhunt.admincmd.huntstop: true
    monsterhunt.admincmd.huntzone: true
    spawnmob.*: true
    vanish.vanish: true
    vanish.nopickup: true
    vanish.nofollow: true
    prefixer.list: true
    prefixer.self: true
    prefixer.other: true
    prefixer.remove: true
    user:
    children:
    permissions.build: true
    appleseed.plant.*: true
    appleseed.wand: true
    deathtpplus.tombstone.*: true
    deathtpplus.deathtp.deathtp: true
    deathtpplus.deathtp.worldtravel: true
    HomeX.*: true
    mcmmo.ability.*: true
    mcmmo.skills.*: true
    mcmmo.commands.myspawn: true
    mcmmo.commands.setmyspawn: true
    mcmmo.item.*: true
    monsterhunt.usercmd.hunt: true
    monsterhunt.usercmd.huntscore: true
    monsterhunt.usercmd.huntstatus: true
    monsterhunt.usercmd.hunttele: true
    TreeAssist.Replant: true

    And the config.yml:
    Show Spoiler
    users:
    Foerster44:
    groups:
    - admin
    Foerster55:
    groups:
    - user
    adimetalhead1991:
    groups:
    - user
    Monster2233:
    groups:
    - user
    Eliminator1996:
    groups:
    - user
    sebbieinstein:
    groups:
    - user


    groups:
    default:
    permissions:
    default: true
    admin:
    permissions:
    admin: true
    inheritance:
    - user
    user:
    permissions:
    user: true
    inheritance:
    - default


    messages:
    build: '&cYou do not have permission to build here.'
    debug: false
     
  12. Offline

    axlsjolund

    Yes. I am. As I stated in my original post, everything is setup properly, but there's something still off with it.
     
  13. Offline

    Sabersamus

    ^^ try not using it :3 hopefully soon i will be in contact with SpaceManiac and get permission to post a fork of this project, like right here where i can provide official support.
     
  14. Offline

    Louis

    Hi folks, I've been trying to get this working and I thought I'd come here for help. As of now I just want players to be able to use the /help. This is the config.yml file (my name is roxthesox):

    What do I need to add to make this work?


    Code:
    users:
            roxthesox:
                    permissions:
                    groups:
                    - moderator
            arcoolka:
                    permissions:
                    groups:
                    - player
     
    groups:
            player:
                    permissions:
                            essentials.help: true
                            permissions.build: true
            moderator:
                    permissions:
                            essentials.depth: true
                            essentials.getpos: true
                    inheritance:
                    - players
     
  15. Offline

    devilquak

    Sorry for my idiocy, but I have a mundane question. Is there a permission similar to permissions.build: true/false that lets people interact with the world, such as pressing buttons, opening doors, placing minecarts, ect? Using permissions.build works great, but it prohibits any kind of interaction with the world, not just placing/destroying blocks. I've got a world that needs protecting, but it has a lot of railways, houses, and other interactive things that I would like people to be able to interact with. I really feel like an idiot asking about this, but there's got to be some sort of solution out there. Thanks.
     
  16. Offline

    Sabersamus

    im not sure, but if SpaceManiac :3 ever gets back to me i can make one when/if i release my fork of this plugin.

    EDIT: :3 i just checked bukkitdev page and he did get back to me, he is updating it *WOOT* :3 im not taking over the project, but as long as it will continue to be update <3 i dont mind

    i wish i was the one to bring it back to live </3

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Oct 10, 2018
  17. Offline

    hyperkungen

    What have i done wrong when i get this error when i start my server with my config?:(

    at org.yaml.snakeyaml.scanner.ScannerImpl.stalePossibleSimpleKeys(Scanne
    rImpl.java:398)
    at org.yaml.snakeyaml.scanner.ScannerImpl.needMoreTokens(ScannerImpl.jav
    a:229)
    at org.yaml.snakeyaml.scanner.ScannerImpl.checkToken(ScannerImpl.java:17
    8)
    at org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingKey.produce(Par
    serImpl.java:563)
    at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:161)
    at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:146)
    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
    :237)
    at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:160)
    at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java
    :237)
    at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:160)
    at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java
    :237)
    at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:160)
    at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:12
    3)
    at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:106)
    at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseCons
    tructor.java:121)
    at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:480)
    at org.yaml.snakeyaml.Yaml.load(Yaml.java:423)
    at org.bukkit.util.config.Configuration.load(Configuration.java:90)
    at org.bukkit.plugin.java.JavaPlugin.getConfiguration(JavaPlugin.java:12
    0)
    at com.platymuus.bukkit.permissions.BlockListener.<init>(BlockListener.j
    ava:15)
    at com.platymuus.bukkit.permissions.PermissionsPlugin.onEnable(Permissio
    nsPlugin.java:39)
    at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:231)
    at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader
    .java:1057)
    at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManage
    r.java:379)
    at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:191)
    at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:174
    )
    at net.minecraft.server.MinecraftServer.t(MinecraftServer.java:357)
    at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:344)
    at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:175)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:408)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:465)
    20:30:48 [INFO] [Vault][Permission] PermissionsBukkit hooked.

    Please answer

    Hyperkungen:)
     

    Attached Files:

  18. Offline

    Sabersamus

    can i see your config?
     
  19. Offline

    devilquak

    So he's continuing to support it? Or he's going to add some new features? If he doesn't, it's totally fine, I think that iSafe is what I was looking for. I'd still like to just keep PermissionsBukkit and not have to install a whole other plugin just for one thing though.

    Edit: Actually, iSafe doesn't cut it. The config doesn't want to comply with common sense (you'd think that true equals true, but no). Hence I re-emphasize my support for a permissions.interact node. Thank you.
     
  20. Offline

    Sabersamus

    The way he made it sound is that he's going to be picking it back up. I would have liked to continue this legacy ;) but its always nice to see authors continue old projects.
     
  21. Offline

    devilquak

    Yeah. This is the best perm plugin hands down, no one can afford to have it be abandoned.
     
  22. Offline

    coolo1

    Anyone know how I can fix /help kicking everyone off the server?
     
  23. Offline

    Sabersamus

    perhaps is a different plugin :3 all this plugin does is provide a place for permissions nodes to go, and give commands to be able to set them in game. nothing to do with /help or kicking players ;) trust me, i know. i read the code over a thousand times.
     
  24. Offline

    Louis

    Does anyone have a good thorough tutorial or is willing to walk me through this? I've ran servers in the past but I must of used a different plugin because I can't get this working for the life of me. I just deleted it and I'm starting from scratch, hopefully it'll work this time.
     
  25. Offline

    gabriel11798

    I'll gladly walk you though the whole thing prefixes, groups, everything. (no one helped me so i may as well be helping other people) Anytime today my skype is gabrielshin98 (makes file transfers easier and i won't have to type as much)

    -gabriel11798
     
  26. Offline

    coolo1

    Ok, if I give you the startup log would you be able to tell me what it is?
     
  27. Offline

    OakRaider4Life

    So if the root Permissions.yml is supposed to be for parent commands, where am I supposed to write my user and group permissions?
     
  28. Offline

    Sabersamus

    config.yml in your permissionsbukkit directory under /plugins :3
     
  29. Offline

    OakRaider4Life

    Silly me. Thanks for the reply.
     
  30. Offline

    coolo1

    I guess no one will be able to use /help then...
     
  31. Hey,

    I've been trying to fix a problem with my permissionsbukkit plugin for a long time now, and I can't seem to get it to work. Is there any way someone can guide me through setting up the permissions.yml and the config.yml. I have even tried YT, and I cant seem to get it to work!!!

    !!
     

Share This Page