Okay I am trying to give guests and members access to a few essentials commands like spawn,list,help,home,sethome etc. But I'm used to the permissions so I tried my best to modify the page just as a test but it didn't work and I get this error when I run it.
18:26:09 [SEVERE] Error occurred while enabling PermissionsBukkit v1.1 (Is it up to date?): while parsing a block mapping; expected <block end>, but found BlockMappingStart
while parsing a block mapping
in "<reader>", line 49, column 8:
expected <block end>, but found BlockMappingStart
in "<reader>", line 51, column 9:
Yeah it is the right file I just didn't bothering copying all the comments at the top of the file.
Here is the whole thing.
# PermissionsBukkit configuration file
# 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 all admin permissions. 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.
build: '&cYou do not have permission to build here.'