[Multiverse] Only OPs can use /mvtp

Discussion in 'Bukkit Help' started by JakobDylanC, Apr 28, 2012.

Thread Status:
Not open for further replies.
  1. Offline

    JakobDylanC

    For some reason, only OPs can use the /mvtp command. I have no idea how to fix it. I tried adding "mvtp" to the list of user commands within the Essentials config, but it didn't seem to work.

    List of plugins:

    Essentials
    Multiverse-Core
    Multiverse-Inventories
    Safe Creeper
    SkyChest
     
  2. Offline

    zipfe

  3. Offline

    JakobDylanC

    Okay, but where am I putting these permissions? Which config file? My permissions.yml in my server root folder is completely empty.

    Ok, I got PermissionsBukkit. Is this what it should look like? The 2 world names are "world" and "creative".

    Code:
    # 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.
     
    users:
        ConspiracyWizard:
            permissions:
                permissions.example: true
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: true
    multiverse.access.world
    multiverse.access.creative
    multiverse.core.tp.self
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
    multiverse.access.world
    multiverse.access.creative
    multiverse.core.tp.self
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
     
    debug: false
    Update: Now that I have PermissionsBukkit, no one can do anything. Sleep, /home, not even /help.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 25, 2016
Thread Status:
Not open for further replies.

Share This Page