Having issue with permissions file #248


  • New
  • Defect
Open
Assigned to spacemaniac
  • _ForgeUser1881482 created this issue Feb 9, 2013

    Having a lot of issues getting the latest dev version to work with 1.4.7 - the config.yml namely.

    Here is what happens.

    My config file is as follows:

    <<code>># PermissionsBukkit configuration file

    1. A permission node is a string like 'permissions.build', usually starting
    1. with the name of the plugin. Refer to a plugin's documentation for what
    1. permissions it cares about. Each node should be followed by true to grant
    1. that permission or false to revoke it, as in 'permissions.build: true'.
    1. Some plugins provide permission nodes that map to a group of permissions -
    1. for example, PermissionsBukkit has 'permissions.*', which automatically
    1. grants all admin permissions. You can also specify false for permissions
    1. of this type.
    1. Users inherit permissions from the groups they are a part of. If a user is
    1. not specified here, or does not have a 'groups' node, they will be in the
    1. group 'default'. Permissions for individual users may also be specified by
    1. using a 'permissions' node with a list of permission nodes, which will
    1. override their group permissions. World permissions may be assigned to
    1. users with a 'worlds:' entry.
    1. Groups can be assigned to players and all their permissions will also be
    1. assigned to those players. Groups can also inherit permissions from other
    1. groups. Like user permissions, groups may override the permissions of their
    1. parent group(s). Unlike users, groups do NOT automatically inherit from
    1. default. World permissions may be assigned to groups with a 'worlds:' entry.

    users:

    13era:

    permissions:

    bukkit.commands.op: true

    bukkit.commands.deop: true

    permissions.build: true

    groups:

    default:

    permissions:

    essentials.tpaccept: true

    essentials.tpdeny: true

    essentials.sethome: true

    essentials.home: true

    essentials.delhome: true

    admin:

    suffix: A

    permissions:

    permissions.*: true

    essentials.*: true

    worldguard.*: true

    worldedit.*: true

    silkspawners.*: true

    groupmanager.*: true

    alchemicalcauldron.*: true

    inheritance:

    - mods

    mods:

    suffix: M

    permissions:

    essentials.kick: true

    essentials.kill: true

    essentials.tempban: true

    essentials.ban: true

    essentials.unban: true

    essentials.tpa: true

    essentials.tp: true

    inheritance:

    - default<</code>>

    when doing /permissions reload, it says reload was completed fine. However upon doing /permissions group list it replies with NOTHING, and behaves as if there is not a single group present except default.

    Upon reopening the file after doing the reload, the file changes to:

    <<code>># PermissionsBukkit configuration file

    1. A permission node is a string like 'permissions.build', usually starting
    1. with the name of the plugin. Refer to a plugin's documentation for what
    1. permissions it cares about. Each node should be followed by true to grant
    1. that permission or false to revoke it, as in 'permissions.build: true'.
    1. Some plugins provide permission nodes that map to a group of permissions -
    1. for example, PermissionsBukkit has 'permissions.*', which automatically
    1. grants all admin permissions. You can also specify false for permissions
    1. of this type.
    1. Users inherit permissions from the groups they are a part of. If a user is
    1. not specified here, or does not have a 'groups' node, they will be in the
    1. group 'default'. Permissions for individual users may also be specified by
    1. using a 'permissions' node with a list of permission nodes, which will
    1. override their group permissions. World permissions may be assigned to
    1. users with a 'worlds:' entry.
    1. Groups can be assigned to players and all their permissions will also be
    1. assigned to those players. Groups can also inherit permissions from other
    1. groups. Like user permissions, groups may override the permissions of their
    1. parent group(s). Unlike users, groups do NOT automatically inherit from
    1. default. World permissions may be assigned to groups with a 'worlds:' entry.

    bukkit.commands.op: true

    bukkit.commands.deop: true

    permissions.build: true

    essentials.tpaccept: true

    essentials.tpdeny: true

    essentials.sethome: true

    essentials.home: true

    essentials.delhome: true

    suffix: M

    permissions.*: true

    essentials.*: true

    worldguard.*: true

    worldedit.*: true

    silkspawners.*: true

    groupmanager.*: true

    alchemicalcauldron.*: true

    inheritance:

    - default

    essentials.kick: true

    essentials.kill: true

    essentials.tempban: true

    essentials.ban: true

    essentials.unban: true

    essentials.tpa: true

    essentials.tp: true

    <</code>>

    No matter what i do, how i save, what i change, it just keeps reverting to this. And i cant get it to work :/

  • _ForgeUser1881482 added the tags New Defect Feb 9, 2013

To post a comment, please login or register a new account.