[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

    lpjz2

    How would i restrict a group from using chests using LWC / WorldGuard
     
  3. Offline

    Heliwr

    You are scaremongering by repeatedly telling people it won't work when it clearly does, if you have valid security concerns then stick with those. It is not your place to tell me or anyone else that we can't use a gun or nutmeg or metanodes, especially under false pretenses. As long as you continue to do that, I will continue to correct.

    This probably belongs in one of those threads, but in WG chests within a claimed/defined region are only accessible by owners/members of that region by default. The WG thread OP has a nice pdf document showing how to claim regions.

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

    Galameth

    Just checked, people with permission.build: false with essentials installed cannot open doors or chests.

    It throws a "You do not have permission to build" warning, but meh.

    I did. I do. I still have. and Always have.

    YOU turned this into an "I hate permissions.* nodes" and started this idiotic "crusade" against me, getting information wrong at LEAST three times now.

    And in no way shape or form are they false pretenses. YOU just don't get why. You are also derailing the entire point of the damned thread by choosing to attack me rather then answer the questions which are stacking up.

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

    Heliwr

    Correcting false information is not derailing the thread, I am merely pointing out that metanodes do function despite your continued protestations to the contrary. Metanodes work, and when you stop claiming otherwise I will likely fade back into the woodwork. It is the lies that keep me engaged in this thread, not any personal animosity towards you.
     
  6. Offline

    Galameth

    I don't care what keeps you here. The point is, this thread is about, and only about, permissionsBukkit. It is only about the specific questions asked. It is NOT about metanodes, and the only reason it was brought up was because it is PROVEN that removing them has helped people. On multiple occasions. My standpoint is NOT that metanodes do not work as a given, it's that they have been KNOWN to not work. I have solid examples of it not working for people. Not EVERY case, but they DO exist.

    All you are saying is, because it works for YOU and because the DEV SAYS SO we should use them and there is no way they couldn't possibly work.

    I am saying that, without using them, without having to wonder "is it my *'s? Is it that I dont have permbridge?" that you can do away with them and gave a garunteed, working, set of permissions.

    I am saying there is an ALTERNATIVE to using *'s.

    YOU keep implying I am saying they flat out don't work.

    YOU are refusing to actually read my posts and are putting words in my mouth.

    YOU have made this thread entirely confrontational, which IS derailing it.

    YOU had no reason to even post a response as your original post is invalid and inaccurate, yet you KEEP using it as a basis to "correct" me.

    I could care less what the "devs" grace us with in THEIR plugins. All I care is that you can, infact, setup PERMISSIONSBUKKIT without using metanodes.

    Despite what you're personal opinion is, it IS lazy, it is NOT efficient. If it WERE I would not have spent the last two weeks fixing peoples configs.
     
  7. Offline

    Heliwr

    Any metanodes that were not working correctly were very likely not configured correctly or were attempted for plugins that don't even support them. For plugins that support them, and I am talking about superperms plugins not the bridge, they are just as robust as individual nodes. As for being lazy, fine I am lazy. That right is mine and everyone else's, it does not invalidate that metanodes are a valid functioning alternative. I fully acknowledge using individual nodes for most (but not all) plugins is also an alternative, but it is not the only option and pretending otherwise is withholding a useful tool from people setting up their permissions.
     
  8. Offline

    Celtic Minstrel

    Um what? The permissions.build node doesn't make PermissionsBukkit cancel build/place events; it takes a step back and actually cancels interact events. With that it mind, it should deny people from opening chests. Unless that was changed at some point.
     
  9. Offline

    Galameth


    Not only have I never said it was the only option, or not the only option, but I don't "pretend" otherwise.

    Though I am glad we have come to a common ground of sorts.
    Now stop this. Anything beyond it and I consider it a personal attack.

    There is one thing I could use help with.

    Expi1 Has his permissions set up properly, has higher groups inherit from lower groups and override where he wants commands as needed, but for some reason, he has a group whose "worlds:" permissions inherit, but the commands specific to that group do not.

    I.E.:

    members:
    permissions.nodes: (do not inherit to the next level)

    worlds:
    test:
    permissions.nodes (do inherit the next level)

    So someone who is in a group that inherits -members can use the "test" worlds permissions but not the other.

    I'm not familiar enough with some of his plugins to know if they are restricting that. Care to join in?
     
  10. Offline

    Heliwr

    I can try, do you have pastebins?
     
  11. Offline

    Galameth

  12. Offline

    lpjz2

    hmm, they could still open chests on my server? - Anyway i fixed this error by Adding chest interactions into the WorldGuard Blacklist for the default group :) Thanks for your help
     
  13. Offline

    Heliwr

    Now that galameth and celtic minstrel mention it, I don't remember having any problems with default account stealing from unprotected chests since I installed PermissionsBukkit (a recurring problem when I was running permissions2/3). Can your default account with permissions.build: false break and place blocks as well?
     
  14. Offline

    Galameth

    It by all means shouldn't.
    I have a default group with everything permissions. and bukkit.command. set to false and when players join they cant access any commands, edit any blocks, nor open any chests/doors. If they do it rewinds the action and replaces whatever they did.
     
  15. Offline

    goodoletom

    I got a problem. The Nodes for like plugins r working but regular nodes like /kick /list are not working. What is wrong.
     
  16. Offline

    Heliwr

    By default those are only accessible to people in ops.txt, have you tried assigning the nodes (http://wiki.bukkit.org/Command_Permissions)?
     
  17. Offline

    Franky1223

    I have a small problem. All my groups have prefixes and suffixes set for iChat, but those for my default group don't show up. It just writes everything white D:
     
  18. Offline

    Cruxsky

    Can you have an option to use color codes in the config file to change the color of the names in the group?
     
  19. Offline

    hypertrax

    so does anywone know's what i do wrong here?

    My bukkit console wont start, its still in processes and server runs. but it wont come on my screen.
    and when i enter the game it says no permission.

    this is my config: http://pastebin.com/Ff10HGUu
     
  20. Offline

    BINCraft

    Can you help me in Permissions setting
    I edit config.yml likes this
    Show Spoiler
    users:
    ConspiracyWizard:
    permissions:
    permissions.example: true
    groups:
    - admin
    groups:
    default:
    permissions:
    permissions.build: true
    citizens.trader.modify.stock: true
    citizens.trader.use.trade: true
    citizens.trader.use.help: true
    iConomy.holdings: true
    iConomy.help: true
    iConomy.payment: true
    admin:
    permissions:
    permissions.*: true
    iConomy.*: 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.'


    and I get Error likes this
    Show Spoiler
    while scanning for the next token
    found character '\t' that cannot start any token
    in "<reader>", line 40, column 1:
    citizens.trader.modify.stock: ...
    ^

    at org.yaml.snakeyaml.scanner.ScannerImpl.fetchMoreTokens(ScannerImpl.ja
    va:360)
    at org.yaml.snakeyaml.scanner.ScannerImpl.checkToken(ScannerImpl.java:18
    3)
    at org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingKey.produce(Par
    serImpl.java:564)
    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.composeMappingNode(Composer.java
    :228)
    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.composeMappingNode(Composer.java
    :230)
    at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:160)
    at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:12
    2)
    at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105)

    at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseCons
    tructor.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.j
    ava:175)
    at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.
    java:215)
    at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager
    .java:136)
    at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:139)
    at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer.java:104)
    at net.minecraft.server.ServerConfigurationManager.<init>(ServerConfigur
    ationManager.java:52)
    at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:136)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:348)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:417)


    Help me please I try again and again but It shows error :(
     
  21. Offline

    drudigger

    Need some help???? what am i doing wrong?


    161 recipes
    17 achievements
    11:25:30 [INFO] Starting minecraft server version Beta 1.8.1
    11:25:30 [INFO] Loading properties
    11:25:30 [INFO] Starting Minecraft server on *:25565
    11:25:31 [INFO] This server is running Craftbukkit version git-Bukkit-0.0.0-1112
    -g54a13b2-b1240jnks (MC: 1.8.1)
    11:25:32 [SEVERE] ebean.properties not found
    11:25:32 [INFO] DataSourcePool [rTriggers] autoCommit[false] transIsolation[SERI
    ALIZABLE] min[2] max[20]
    11:25:32 [INFO] SubClassFactory parent ClassLoader [org.bukkit.plugin.java.Plugi
    nClassLoader]
    11:25:33 [INFO] Entities enhanced[0] subclassed[1]
    11:25:34 [INFO] LWC: Loading shared objects
    11:25:34 [INFO] LWC: Protection cache: 0/10000
    11:25:34 [INFO] LWC: Native library: plugins/LWC/lib/native/Windows/x86/sqlitejd
    bc.dll
    11:25:34 [SEVERE] Could not load 'plugins\PermissionsBukkit-1.2.jar' in folder '
    plugins':
    while scanning for the next token
    found character '\t' that cannot start any token
    in "<reader>", line 5, column 1:
    /stop: true
    ^

    at org.yaml.snakeyaml.scanner.ScannerImpl.fetchMoreTokens(ScannerImpl.ja
    va:360)
    at org.yaml.snakeyaml.scanner.ScannerImpl.checkToken(ScannerImpl.java:18
    3)
    at org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingKey.produce(Par
    serImpl.java:564)
    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.composeMappingNode(Composer.java
    :228)
    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.composeMappingNode(Composer.java
    :230)
    at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:160)
    at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:12
    2)
    at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105)

    at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseCons
    tructor.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.j
    ava:175)
    at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.
    java:215)
    at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager
    .java:136)
    at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:139)
    at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer.java:104)
    at net.minecraft.server.ServerConfigurationManager.<init>(ServerConfigur
    ationManager.java:52)
    at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:136)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:348)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:417)
    11:25:35 [INFO] Preparing level "world"
    11:25:35 [INFO] Default game type: 0
    11:25:35 [INFO] Preparing start region for level 0 (Seed: -2371862144130187827)
    11:25:44 [INFO] Preparing spawn area: 24%
    11:25:45 [INFO] Preparing spawn area: 61%
    11:25:46 [INFO] Preparing start region for level 1 (Seed: -673451055627626173)
    11:25:46 [INFO] Preparing spawn area: 0%
    11:25:47 [INFO] Preparing spawn area: 12%
    11:25:48 [INFO] Preparing spawn area: 57%
    11:25:49 [INFO] Preparing spawn area: 97%
    11:25:49 [INFO] CommandBook 1.6 enabled.
    11:25:49 [SEVERE] CommandBook: Unable to read default configuration: config.yml
    11:25:49 [SEVERE] CommandBook: Unable to read default configuration: kits.txt
    11:25:49 [WARNING] CommandBook: 2 Warps(s) loaded
    11:25:49 [WARNING] CommandBook: 1 Homes(s) loaded
    11:25:49 [INFO] CommandBook: Maximum wrapper compatibility is enabled. Some feat
    ures have been disabled to be compatible with poorly written server wrappers.
    11:25:49 [INFO] CommandBook: 0 banned name(s) loaded.
    11:25:49 [INFO] CommandBook: Using the Bukkit Permissions API.
    11:25:50 [INFO] [HeroChat] HeroChat version 4.10.3 enabled.
    11:25:50 [INFO] [rTriggers] Loaded: Version 2.32
    11:25:50 [INFO] WorldEdit 4.7 enabled.
    11:25:50 [SEVERE] WorldEdit: Unable to read default configuration: config.yml
    11:25:50 [INFO] WorldEdit: Using the Bukkit Permissions API.
    11:25:50 [INFO] LWC: Loaded 137 locale strings (0 overrides)
    11:25:51 [INFO] LWC: Permissions API: SuperPermsPermissions
    11:25:51 [INFO] LWC: Currency API: NoCurrency
    11:25:51 [INFO] LWC: Loading SQLite
    11:25:51 [INFO] LWC: Using: Native
    11:25:51 [INFO] LWC: Precached 58 protections.
    11:25:51 [INFO] LWC: At version: 3.53 (b294)
    11:25:51 [INFO] Done (1.649s)! For help, type "help" or "?"
    >
     
  22. Offline

    Regulus123

  23. Offline

    Keitho

    Heliwr - Please shut the fuck up, Galameth is trying to help people and your here slowing him down and stopping him from helping. If you say he is all wrong Why dont you start giving people some fucking help rather than add more useless posts making it harder for Galameth to help us :/
     
  24. Offline

    Sudogaron

    Even with a user set as default where permissions.build is "false". you can still destroy and build...

    I do a /perms check on the user and it shows permissions.build is false for that user.

    Am I missing something?
     
  25. Offline

    Heliwr

    Like I said, some people may find knowing that defined metanodes are just as robust as individual nodes useful and therefore helpful. Also, in what universe do you think telling someone to shut up on the internet is ever successful?

    That is odd, lpjz2 had that problem yesterday too but I have never seen it myself. Maybe try posting a pastebin of your config?

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

    Sudogaron

    Figured it out, /reload fails for some reason even though it says reload complete. I had to restart the server after every change. I'm probably going back to PEX maybe. I just need a permissions plugin to work with worldguard/worldedit and thats it. I keep having so many issues with this.
     
  27. Offline

    Heliwr

    Good to know, I had thought that was an issue only with older versions of Spout. Maybe @lpjz2 can confirm if restarting mitigates his problem too.
     
  28. Offline

    mrthu1000

    help!

    ?

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

    hypertrax


    found character '\t' that cannot start any token
    in "<reader>", line 40, column 1:


    \t token (tabs)
    never use tabs in .yml the error is on line 40 column 1. use notepad++ to edit the file!
     
  30. Offline

    Keitho

    My BukkitPermissions Still isint Working :/ I dont see anything wrong with it but there is something wrong with it :/ Its really annoying me now. Ever since I started to try use this plugin , it hasint worked for me. Config file : http://pastebin.com/kqxByVBJ
     
  31. Offline

    Heliwr

    What isn't working? At first glance it looks like you want every group to have every available permission since you give them superpermbridge.*, so at least for plugins that still support permissions2/3 you're giving all of your users everything. Also, I think case is important - change all instances of Default to default.
     

Share This Page