Inactive [ADMN/DEV] PermissionsEx (PEX) v1.19.5 - Tomorrow is Today! [1.4.6-R0.1]

Discussion in 'Inactive/Unsupported Plugins' started by t3hk0d3, May 21, 2011.

  1. Offline

    t3hk0d3

    [​IMG]
    Version: 1.19.5

    PLEASE USE BUKKIT-DEV FORUM FOR DISCUSSION/HELP
    http://dev.bukkit.org/server-mods/permissionsex/
    THANKS IN ADVANCE.

    PermissionsEx (PEX) is a new permissions plugin, based on Permissions ideas and supports all of its features. But PEX is more! It offers different backends, powerful ingame management, fine grained restrictions for world modification.

    [​IMG]

    Current features
    1. Bukkit Permissions (SuperPerms) compatible.
    2. Several backend support. Currently bundled backends is File (YAML) and SQL (MySQL, SQLite). Also it's possible to add your own.
    3. YAML backend, with new, fully rethinked, config schema. Now all user, groups and their permissions are stored in one file - permission.yml. BTW file name is adjustable too.
    4. SQL backend, most delicious. Currently MySQL and SQLite supported, but other DB (like Postgre) are possible too. PEX deploys the DB scheme (tables and initial data) automatically. This means, that you only need to provide data on how to connect to the db, everything else PEX will handle by itself.
    5. Flexible architecture and API - you can change a lot programmatically.
    6. Compatibility layer with TheYeti's Permissions (2.7.4) (as a separate part of the plugin). In most cases plugins, which use Permissions, will alsowork with PEX also.
    7. Rich chat/console command interface. You can do almost everything ingame. Command list below.
    8. Modifyworld - Embedded restrictions mechanism (we call it "modifyworld"), which provides the possibility to control players abilities, such as destroying/placing blocks, riding carts/boats or even getting spotted by mobs and much more. Disabled by default.
    9. Multigroup inheritance. User, as well as Group, can be member of several groups. And inherit their permissions, options and prefix/suffix.
    10. Permissions based upon Regular Expressions. This mean you can use regular expressions. Example: modifyworld.blocks.(destroy|place).(3|12) - this permission allow place or destroy only sand (12) or dirt (3) blocks. There is still limitation on dot usage in your regexps - dots are escaped by default.
    11. Multiworld permissions. Just don't specify world and permission would work in any world.
    12. Multiworld inheritance. You can inherit different groups in different worlds.
    13. Easy migration from Permissions 2.x. Converter for both YAML and SQL are embedded into PermissionsCompat. Just use simple instruction.
    14. Perfomance friendly. Low-level caching helps alot when you have 100+ online users :)
    15. Promotional/Demotional system. You can assign ranks to groups and promote/demote users to higher/lower ranked group.
    16. World-inheritance - permissions/option of one world can be inherited by another world.
    17. Timed Permissions - you can give user permission only for some amount of time.
    18. Chat Manager - small chat plugin, bundled with PEX. With prefixes/suffiex and colors. Check wiki for more details.


    Documentation
    Wiki

    Basic setup tutorial (Thanks to lycano)

    Nice tutorial made by Bennetman


    Download
    Stable version

    Development version (mostly stable) - always lastest dev build.

    Sources
    https://github.com/PEXPlugins

    Builds
    http://webbukkit.org:8080/

    Maven Repository
    http://repo.tehkode.ru/browse/ru.tehkode

    IRC
    Join us on #permissionsex, irc.esper.net. Feel free to ask any related questions.

    Tools !NEW!
    Pex Auto-Setup Tool - MySQL and FlatFile !


    Changelog
    Show Changelog (open)
    v1.19.5
    Proper intervals for timed commands (both group/permissions management), without pesky seconds calculations (like /pex user t3hk0d3 timed add cool.permission 10days)
    Bugfixes.
    1.4.6 compatibility.


    v1.19.4
    Built for Bukkit 1.4.2-R0.1
    Added inventory permissions (modifyworld.items.put/take.<item>.of.<chest>)
    Added item hold permission (modifyworld.items.hold.<item>)
    Sdded monster egg spawn permission (modifyworld.spawn.<creature>)
    Few other minor fixes
    v.1.19.3
    Modifyworld improvements (configurable messages, now independent from PEX)
    /pex help command
    Minor improvements and bugfixes
    v.1.19.2
    New modifyworld permissions
    Some bugfixes
    v.1.19.1
    Bugfix release
    v1.19
    Bukkit R6 compatible.
    Several bugfixes!
    Permissions now case-insensetive.
    v1.18
    Users logging and cleanup feature.
    Non-inheriting nodes feature.
    Several Bugfixes.
    PermissionsCompat is finally remove from default bundle.
    v1.17
    User/group specific management permissions (permissions.manage.group.Admin)
    Fixed some superperms compatibility issues
    Fixed several bugs
    v1.16
    SuperPerms compatbility bridge were rewritten - no lags anymore and now with debug output (now you can view superperms checks).
    Numerous of bugs were fixed (Thanks you guys for reporting them)
    Modifyworld were improved (modifyworld.item.use)
    v1.15
    Compatiblity for 1317+
    Fixed perfomance issues with SuperPerms (if you still experience they try to disable "raw-permissions" in config.yml)
    Fixed issue with prefix inheritance
    v1.14
    Improved Options mechanism.
    Auto saving new users feature, disabled by default.
    SuperPerms bridge improved - more permissions supported by wildcards.
    File backend dumping now fully functional. SQL dumping is still bogus (do not dump world-specific inheritance and prefixes), will be fixed soon.
    Many bugfixes and minor improvements.
    v1.13
    Superperms (BukkitPerms) support
    Multiworld inheritance and prefixes/suffixes
    Groups weighting
    ChatManager, chat plugin which bundled with PEX.
    Modifyworld now separate plugin, but still bundled with PEX.
    API changed slightly, CustomEvents (PermissionsEntityEvent, PermissionsSystemEvent) introduced.
    Many lesser improvements and tons of bugfixes.
    v1.12
    API get slightly improved
    Ranking ladders.
    User/group name case-insensetivity.
    World-inheritance.
    Timed permissions.
    Modifyworld rules are get improved.
    Tons of minor improvements and bugfixes.
    v1.11
    Many bugfixes and improvements.
    MySQL connection stability improved - reconnection mechanism.
    v1.10
    Promotional/Demotional system.
    Perfomance improvement, with new low-level caching system (thx Joy)
    Modifyworld improved.
    Many lesser improvements and bugfixes.
    v1.06
    New p2compat backend, for easy migration from Permissions 2.x to PEX.
    v1.05
    Users/Groups dumping (pex dump <backend> <file>).
    New commands pex promote/demote. Actually this is just aliases for "pex user group set/remove"
    Few bugfixes.
    v1.04
    Players now can be informed about changes (has been added to group, changed permission/option). Disabled by default - set "permissions.informplayers.changes" to "true"
    Config node "permissions.verbose", which responsible for player informing about modifyworld restrictions has been renamed to "permissions.infromplayers.modifyworld".
    Autocomplete has been improved.
    New command "pex config <node> [value]". This command help to manipulate configuration file (config.yml) from console/chat interface.
    Many bugfixes.
    v1.03
    Autocomplete for users (taken from registred users and online users) and groups names.
    New command for user removing (pex user <user> delete)
    Fixed several nasty bugs. Thanks for bugreports!
    v1.02
    Compatibility layer loading order issue fixed. Now most of plugins should work.
    Tested with new CB 803 build.
    v1.01
    Regular expression permissions support.
    Newer permissions now added above (bugfix).
    Several bugfixes.
    v1.00
    Initial public release.
     
    BRampersad, grid21, MrRazull and 71 others like this.
  2. Offline

    cha198

    Hi my perms ranks are not working for some reason. here is my code

    Code:
    groups:
      User:
        default: true
        permissions:
        - essentials.spawn
        - bukkit.command.plugins
        - mobdisguise.mob.chicken
        - essentials.motd
        - ChestShop.shop.buy
        - ChestShop.shop.sell
        options:
          rank: '1000'
     
      Member:
        inheritance:
        - User
        permissions:
        - mobdisguise.mob.blaze
        - essentials.tp
        - creativegates.use
        - essentials.signs.use.buy
        - essentials.signs.use.sell
        worlds:
                world_nether:
                    permissions:
                    - essentials.god
        options:
          rank: '900'
     
      Mi:
      inheritance:
        - Member
      permissions:
        - essentials.pay
        - essentials.sell
        - essentials.mail.send
      options:
        rank: '800'
      B:
        inheritance:
            - Mi
        permissions:
        - mobdisguise.mob.zombie
        - essentials.msg
        - magiccarpet.*
        options:
          rank: '700'
     
      S:
        inheritance:
          - B
        permissions:
        - mobdisguise.mob.creeper
        - essentials.setwarp
        - essentials.compass
        options:
          rank: '600'
     
      C:
          inheritance:
            - S
          permissions:
          - essentials.fly
          - essentials.nick
          - essentials.nick.color
          - essentials.nick.magic
          options:
            rank: '500'
     
      N:
        inheritance:
            - C
        permissions:
        - essentials.repair.armor
        - mobdisguise.*
        worlds:
            Creative:
                permissions:
                - essentials.gamemode
        options:
          rank: '400'
     
      M:
          inheritance:
            - N
          permissions:
          - ChestShop.shop.create
          - essentials.repair.enchanted
          - essentials.chat.color
          - essentials.chat.magic
               options:
                   rank: '300'

    Please Help Me I really Need This.

    Thanks!
     
  3. This could be caused by almost anything. The usual suspect is a badly formatted permissions.yml. Put yours on something like pastie.org and put the link here.​

    This could be caused by almost anything. The usual suspect is a badly formatted permissions.yml. Put yours on something like pastie.org and put the link here.

    This could be caused by almost anything. The usual suspect is a badly formatted permissions.yml. Put yours on something like pastie.org and put the link here. Also look in your server.log to see if chatmanager is even starting up

    Umm, yes it does, at least one way of doing it does. The other involved editing the config.yml for the chatmanager, assuming you are using chatmanager.

    [​IMG]

    Notice the prefix is coloured.

    Try something like
    Code:
    prefix: '&c[prefix]&2'
    Your owner group is missing the prefix: entry and the dash for the '*' node. :)

    Your formatting is off in more than a few places.

    The Mi group isn't indented correctly at all
    c: may be too far in
    m: has the options section (not just the line) indented too far as well.

    Beyond that, stating that they are not working isn't specific enough. Need examples of commands run and what happened with the exact error, if any.

    https://github.com/PEXPlugins/PermissionsEx/wiki/Troubleshooting-and-FAQ#wiki-pex-help

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Sep 9, 2018
  4. Offline

    EMOberger

  5. Offline

    Pythong

    I'm using permissionsEX with Essentials and i'm having the a problem with protecting players from specific damage. It's just not working. Not sure if this is a Essentials problem or PeX? I searched Essentials support pages and came up with no results with the problems i'm having so i think it might be related to PeX.

    Pex is running the latest version 1.19.1 configured with SQL, i have the following permissions set for a rank:

    essentials.protect.damage.fall
    essentials.protect.damage.lava
    essentials.protect.damage.suffocation

    I can still take Fall/lava/suffocation damage even after a /pex reload


    Any ideas?
     
  6. Offline

    hoobz

    Thanks Justin :3
     
  7. Offline

    cha198

    Can you fix it for me please, i'm really bad at this.
     
  8. I'd try turning on debug and see what PEX is finding first during the permission node check, and perhaps look at adding the modifyworld nodes for preventing damage. I'm guessing that it's possible that PEX is finding the nodes from essentials, but essentials isn't canceling out the damage. if that is not the case, it could be that PEX isn't finding the essentials nodes before finding the allow nodes, in which case the debug output should show that.

    I'm sorry, but no, I'm not going to redo your permissions for you. I'm not trying to be a jerk, but being able to work with a permissions plugin and edit a simple text file is one of the basic things that a server admin/owner needs to be able to do. This is one of those 'teach a person to fish' things.

    If you can't quite get editing the file directly right, I'd suggest using the built-in PEX commands to add permissions, it will always use the right formatting, or read the PEX basics section on the wiki which covers what the formatting rules are for the permissions file. :)

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

    Pythong

    Thanks Justin i'm looking into it right now, with PEX DEBUG enaled it doesn't appear to show me any good information. Here is the output from the logs right up to my death by lava.



    I'm looking over the ModifyWorld permissions from PEX ( https://github.com/PEXPlugins/PermissionsEx/wiki/Modifyworld ) but I don't see anything in regards to nodes for preventing damage.

    Thanks,
    Python
     
  10. Offline

    Axiz

    Uh hey my inheritence isnt working
     
  11. Now that is interesting... Debug output should show the modifyworld nodes as well....

    Ok, this is what I get in debug when I jump into a pool of lava:
    Code:
    02:26:12 [INFO] User bacon_avenger checked for "modifyworld.damage.take.lava", "*" found
    02:26:12 [INFO] User bacon_avenger checked for "modifyworld.damage.take.fire", "*" found
    02:26:12 [INFO] User bacon_avenger checked for "modifyworld.damage.take.fire", "*" found
    02:26:12 [INFO] User bacon_avenger checked for "modifyworld.damage.take.firetick", "*" found
    If you aren't seeing that, I'd almost think that modifyworld isn't enabling?

    The damage nodes for modifyworld are under the entities section: https://github.com/PEXPlugins/PermissionsEx/wiki/Modifyworld#wiki-Entities

    Chances are your permissions are off. :)

    File backend? Can you post them on pastie.org or pastebin.com and link to them? And explain exactly what is not working?

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Sep 9, 2018
  12. Offline

    prizna

    I have set up teleport signs with essentials but my guests cant right click the signs because of lack of permissions, what perm is needed so a player can right click a sign?

    I have given the permission so they can teleport, but they aren't allowed to right click the sign, so it must be a modifyworld permission.
     
  13. Offline

    Kowak

    Hello,
    I need help with PEX. I want to set that only resident of cities (Towny) can use Lockette.
    How can i set this?
     
  14. Offline

    cha198

    Ok, thanks for the help! :)
     
  15. Offline

    Pythong

    Ahh i was missing the Modifyworld.jar file.

    I added that and i'm getting better debug.. here i was testing fall damage. This is what the pex debug shows:

    2012-04-09 08:39:38 [INFO] User Python_rb checked for "modifyworld.damage.take.fall", "modifyworld.*" found



    Now i have the default group setup with "modifyworld.*" and another group that inherits default's permissions. This new group has the essentials.protect.damage.fall so it looks like modifyworld is overlapping with essentials and cant protect me?
     
  16. Offline

    Gulogomi

    I have GroupManager and i have just installed PEX. Will PEX read the permissions or do i need to copy all the permissons from GroupManager and paste it to PEX and after that delete GroupManager or..? :)
     
  17. Offline

    Roervig2473

    http://pastebin.com/TS62Ktiw
     
  18. Offline

    Pythong

    Instead of figuring out why ModifyWorld was overlapping with essentials, i just reversed it and now control the lava/fall damage though Modifyworld:
    Thanks! Works like a charm now.

    -modifyworld.damage.take.lava
     
  19. In theory, a groupmanager permissions file might mostly work as it's YAML (I believe), but there are some things about how GM does it's nodes that do not translate over to PEX.

    And yes, if you are going to convert, you can't have multiple permissions managers running at the same time. :)

    Thank you.

    *looks*

    Interesting. Technically, I believe your rank numbers should be in quotes, but when I tested your permissions on my test server with the RB for 1.2.5 and PEX 1.19.1, I didn't see any errors, group set worked and promote and demote worked fine.

    I think your server.log is going to have to be looked at next to see what it shows. You haven't run /reload have you? PEX and a lot of other plugins don't play well with /reload

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Sep 9, 2018
  20. Offline

    prizna

    I have set up teleport signs with essentials but my guests cant right click the signs because of lack of permissions, what perm is needed so a player can right click a sign?

    I have given the permission so they can teleport, but they aren't allowed to right click the sign, so it must be a modifyworld permission.
     
  21. Offline

    EliTe_PiG

    All files including chatmanager config and my permissions.yml both work correctly, i also ran them through Online YAML Parser just to make sure, however when i try to promote myself through the console i recieve the error:

    Code:
    18:40:36[INFO] Promotion error: User are not in this ladder
    18:40:36[SEVERE] Ranking Error (console > EliTe_PiG): User are not in this ladder
    I also tried promoting myself through commands and i do not have the permissions to do so despite being in the Owner rank in permissions.yml
    Another thing that happens is when i talk with a prefix the prefix shows with the exception of the colours, the text is simply left plain white. Could anyone help me resolve these issues?
    My permissions.yml: http://pastebin.com/D3vgJkTR
    Any help would be much appreciated.
     
  22. What was the exact command you ran to promote the player?

    And unless you ran the command to promote yourself from the console, you can't do that. It's designed to keep people who somehow get access to the nodes from abusing the system and promoting themselves up to the highest possible rank.

    The chat stuff, I'm not sure I'm understanding the issue. The way you have your prefixes set up, the prefix name is in colour but everything after that is set to be in white.
     
  23. Offline

    EliTe_PiG

    I tried the command 'pex promote EliTe_PiG' which gave me the message about the ladders and the colours in my prefixes don't exist at all, it's all plain white. I then used the command 'pex user EliTe_PiG group set Owner' which seemed to work.
     
  24. That is odd.

    I put your permissions into my test setup and was able to promote myself (as well as your username in the permissions) all the way up to the owner group, at which point I received the error of the user is not promotable. The chat prefix is coloured as well.

    You are using chatmanager from PEX, yes? Is it showing up green when you run /plugins?
     
  25. Offline

    EliTe_PiG

    Yes it is running and also showing up green when i use /plugins, however there's a bigger problem, the groups i put my users in don't pickup the permissions for that group, i just had to manually add the permissions to my users through the 'pex user <user> add <permission>' command in console, everything else works pretty well.
    All users recieve the message 'You do not have access to this command' even when put in the group with the permission. I know its a lot but i really appreciate your help. Thanks.
     
  26. Offline

    mushy

  27. Offline

    djrocker_smit

    When I try to join I get this message in the console: 20:41:07 [WARNING] Failed to handle packet: java.lang.RuntimeException: Permissions manager is not accessable. Is the PermissionsEx plugin enabled?
    Can someone help me?
     
  28. The only problem I see with your pseudo permissions file you linked to was in the owner group in the multiworld section (the worlds: line is indented too far). Everything else looks OK.

    At this point, I'd start to wonder if you don't have another plugin blocking PEX somehow. My only suggestion right now would be to try it on a test setup with bukkit, PEX and one plugin of your choice. Start that up, see if it works and keep adding plugins until it stops. Anything more, and I'd need to see your actual permissions file (with the users section intact) so I could look and try to reproduce it on my testing setup.

    What command are you trying to use? Are you /reloading your server? (/reload doesn't play nice with PEX)

    Not enough information I'm afraid.
    https://github.com/PEXPlugins/PermissionsEx/wiki/Troubleshooting-and-FAQ#wiki-pex-help

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

    Viperdream

    I'm getting this error a lot:
    Code:
    2012-04-12 03:40:23 [SEVERE] java.lang.RuntimeException: Permissions manager is not accessable. Is the PermissionsEx plugin enabled?
     
    2012-04-12 03:40:23 [SEVERE]    at ru.tehkode.permissions.bukkit.PermissionsEx.getPermissionManager(PermissionsEx.java:148)
     
    2012-04-12 03:40:23 [SEVERE]    at ru.tehkode.permissions.bukkit.PermissionsEx.getUser(PermissionsEx.java:155)
     
    2012-04-12 03:40:23 [SEVERE]    at ru.tehkode.permissions.bukkit.superperms.PermissiblePEX.performCheck(PermissiblePEX.java:124)
     
    2012-04-12 03:40:23 [SEVERE]    at ru.tehkode.permissions.bukkit.superperms.PermissiblePEX.checkPermission(PermissiblePEX.java:110)
     
    2012-04-12 03:40:23 [SEVERE]    at ru.tehkode.permissions.bukkit.superperms.PermissiblePEX.hasPermission(PermissiblePEX.java:102)
     
    2012-04-12 03:40:23 [SEVERE]    at org.bukkit.craftbukkit.entity.CraftHumanEntity.hasPermission(CraftHumanEntity.java:102)
     
    2012-04-12 03:40:23 [SEVERE]    at org.bukkit.craftbukkit.CraftServer.broadcast(CraftServer.java:962)
     
    2012-04-12 03:40:23 [SEVERE]    at ltguide.base.Base.broadcast(Base.java:133)
     
    2012-04-12 03:40:23 [SEVERE]    at ltguide.base.Base.broadcast(Base.java:128)
     
    2012-04-12 03:40:23 [SEVERE]    at ltguide.base.Base.broadcast(Base.java:124)
     
    2012-04-12 03:40:23 [SEVERE]    at ltguide.minebackup.listeners.CommandListener.onCommand(CommandListener.java:47)
     
    2012-04-12 03:40:23 [SEVERE]    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
     
    2012-04-12 03:40:23 [SEVERE]    at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:166)
     
    2012-04-12 03:40:23 [SEVERE]    at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:473)
     
    2012-04-12 03:40:23 [SEVERE]    at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.java:821)
     
    2012-04-12 03:40:23 [SEVERE]    at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:781)
     
    2012-04-12 03:40:23 [SEVERE]    at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:764)
     
    2012-04-12 03:40:23 [SEVERE]    at net.minecraft.server.Packet3Chat.handle(Packet3Chat.java:34)
     
    2012-04-12 03:40:23 [SEVERE]    at net.minecraft.server.NetworkManager.b(NetworkManager.java:229)
     
    2012-04-12 03:40:23 [SEVERE]    at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:113)
     
    2012-04-12 03:40:23 [SEVERE]    at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78)
     
    2012-04-12 03:40:23 [SEVERE]    at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:551)
     
    2012-04-12 03:40:23 [SEVERE]    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:449)
     
    2012-04-12 03:40:23 [SEVERE]    at net.minecraft.server.ThreadServerApplication.run(SourceFile:492)
     
    2012-04-12 03:40:23 [SEVERE] null
     
    org.bukkit.command.CommandException: Unhandled exception executing command 'mbck' in plugin MineBackup v5.9.3
     
        at org.bukkit.command.PluginCommand.execute(PluginCommand.java:42)
     
        at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:166)
     
        at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:473)
     
        at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.java:821)
     
        at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:781)
     
        at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:764)
     
        at net.minecraft.server.Packet3Chat.handle(Packet3Chat.java:34)
     
        at net.minecraft.server.NetworkManager.b(NetworkManager.java:229)
     
        at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:113)
     
        at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78)
     
        at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:551)
     
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:449)
     
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:492)
     
    Caused by: java.lang.RuntimeException: Permissions manager is not accessable. Is the PermissionsEx plugin enabled?
     
        at ru.tehkode.permissions.bukkit.PermissionsEx.getPermissionManager(PermissionsEx.java:148)
     
        at ru.tehkode.permissions.bukkit.PermissionsEx.getUser(PermissionsEx.java:155)
     
        at ru.tehkode.permissions.bukkit.superperms.PermissiblePEX.isPermissionSet(PermissiblePEX.java:202)
     
        at org.bukkit.permissions.PermissibleBase.hasPermission(PermissibleBase.java:71)
     
        at ru.tehkode.permissions.bukkit.superperms.PermissiblePEX.checkPermission(PermissiblePEX.java:113)
     
        at ru.tehkode.permissions.bukkit.superperms.PermissiblePEX.hasPermission(PermissiblePEX.java:102)
     
        at org.bukkit.craftbukkit.entity.CraftHumanEntity.hasPermission(CraftHumanEntity.java:102)
     
        at org.bukkit.craftbukkit.CraftServer.broadcast(CraftServer.java:962)
     
        at ltguide.base.Base.broadcast(Base.java:133)
     
        at ltguide.base.Base.broadcast(Base.java:128)
     
        at ltguide.base.Base.broadcast(Base.java:124)
     
        at ltguide.minebackup.listeners.CommandListener.onCommand(CommandListener.java:47)
     
        at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
     
        ... 12 more
    
    What am I doing wrong?

    The same as mushy, I got it when I tried to use a command from Minebackup and various other commands from commanbook (/broadcast being an example)
     
  30. Offline

    mushy

    I try the /say command, and sometimes the /broadcast(essentials) and then the error occurs
     
  31. Offline

    EliTe_PiG

    I created a test server and gave one of my ranks the node 'diguisecraft.*' I put myself in this rank wasn't able to promote or demote myself through the use of 'pex promote EliTe_PiG' or 'pex demote EliTe_PiG' and recieved the error: User are not in this ladder. I then set myself to be in the Diamond group using the command 'pex user EliTe_PiG group set Diamond' and could not use '/d' command which i gave that rank the permission for.
    This is my permissions.yml which includes the users: http://pastebin.com/je9fhe3C
    I'm not sure how to fix it so i was hoping you'd take a look. Thanks again.
     

Share This Page