Inactive [ADMN/INFO] GroupManager v1.0 alpha-3 - A Permissions replacement [440-531]

Discussion in 'Inactive/Unsupported Plugins' started by AnjoCaido, Feb 17, 2011.

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


    GroupManager - The Permissions 2.x plugin sucessor.
    Version: v1.0 alpha-5

    Yes, it has multiworld and multigroup users support now. When 1.0 final release, next step is database (SQLite/MySQL).


    If you use Essentials:
    - Don't use both EssentialsGroupManager.jar and GroupManager.jar! Just choose one, because they are the same!
    - Don't use both EssentialsGroupBridge.jar and FakePermissions.jar! Just choose one, because they are the same!


    As the growth of this plugin is getting faster and faster, I needed to put multiword support the soon as I could.
    Now it's here. And GroupManager is keeping all of it's good stuff! Did I say it is going to bring a lot more of new stuff too?

    Purpose of the plugin:
    The purpose has changed. Permissions got better. But it still not enough. Why I did, and keep doing this?
    I started it thinking that it would make me happy. Now it's because it will make YOU happy.

    Advantages against Permissions:
    • User multigroup support.
    • Full command list to change anything during game or thru the console.
    • Good API to change things. You to change a player group you can do getPlayer(name).setGroup(getGroup(name))
    • Exception nodes.
    • It separates groups files from users files.

    New Features:
    • User multigroup support(yay!)
    • Multiworld support(meh).
    • It has world permission mirroring(you can make a world nether having the same permissions of world2 instead of default world1).
    • It saves only the files that will have contents changed.
    • It separates groups files from users files.
    • It cleans old backup files older than 24h.

    Previous Features(included):
    • It has the same file format as Permissions, no need to get used with anything new.
    • It comes with a fake Permissions plugin, that attaches GroupManager to all your permissions dependent plugins. No need to make any changes, nor update other plugins. Just adjust your permissions files and GO!
    • Commands to change users permissions are REALLY on-the-fly(no touching files).
    • It saves the permissions data periodically.
    • It backups every file before overwrites.
    • Tons of commands for complete user/group/permission management during game/console.
    • It has a fantastic temporary permissions system, that let's you to make changes in users, with the possibility to go back at any time(and it never is saved on files).
    • Negative nodes(aka '-'): You can take off specific permissions from users that have a full set.
    • Exception node(aka '+'): Used when a user/group has a set of negative nodes, and you want to allow a specific one.

    User's subgroups: a brief explanation
    You can see on the file structure(down here on same post), that users have an optional node called subgroups. That node is a list, just like "permissions" node. There you can list a user subgroup, it can be as many as you want.
    What a user inherits from subgroups? Only permissions. It means nothing on a subgroup's info node(prefix, suffix, build and other variables) will be considered.
    The user will still be considered as a member of that group, but will only inherits it's permissions, like some commands, kits, etc.

    This reduces the needs of a nest of groups inheriting each other.
    You can have one user in Peasant group, which has only some basics, and them let him join in Miner as a subgroup, where he can get Miner kits, or other related to miner group.
    Later, when your town needs a railer, you can just add the group Railer to him as subgroup, and he will have both things at same time. When the job is done, you just remove the subgroup.
    This gets even more interesting when you have groups related to towns, factions, teams… etc.

    World mirroring: a brief explanation
    Let's say you have a config file like this:
          minutes: 10
        level: INFO
              - world2
              - world3
              - world5
    It means that all your permissions of world2, and world3 will be the same of world1. And it means all permissions of world5 will be the same of world4.
    It won't copy any file. In fact, it won't matter if there is files for world2… when the permissions get load, every request for world2 will be redirected for world3. Simple as that.

    If no mirroring is specified, any world not loaded will automatically mirror the default world of the server.

    File structure: a brief explanation
    The files read for GroupManager 1.0+ for data management are two files per world. The users file are users.yml. The groups file are groups.yml.
    The thing is that those files are located in:

    So the file structure for the world called anjoCaidoWorld and netherWorld will be:

    The files might look like this:
            default: false
                build: false
                prefix: ''
                suffix: ''
            - SemiAdmin
            - '*'
            default: true
                build: false
                prefix: ''
                suffix: ''
            inheritance: []
            - essentials.spawn
            - essentials.motd
            - essentials.home
            - essentials.sethome
            default: false
                build: false
                prefix: '&c'
                suffix: 'Mod'
            - Default
            - essentials.tphere
            - essentials.item
            - essentials.give
            default: false
                build: false
                prefix: '&c'
                suffix: 'SemiAdmin'
            - Moderator
            - +groupmanager.mandemote
            - +groupmanager.manpromote
            - -groupmanager.*
            - '*'
            default: true
                build: false
                prefix: '&e'
                suffix: 'Peasant'
            - Default
            permissions: []
            default: false
                build: false
                prefix: ''
                suffix: ''
            - essentials.kit
            - essentials.kit.miner
            - flashlight.regular
            default: false
                build: false
                prefix: ''
                suffix: ''
            - essentials.kit
            - essentials.kit.healer
            - essentials.heal
            default: false
                build: false
                prefix: ''
                suffix: ''
            - essentials.kit
            - essentials.kit.farmer
            - essentials.spawnmob
            default: false
                build: false
                prefix: ''
                suffix: ''
            - essentials.kit
            - essentials.kit.railer
            group: Admins
                prefix: '&c'
                suffix: King
            permissions: []
            group: SemiAdmin
            permissions: []
            group: Moderator
            - essentials.god
            group: Peasant
                prefix: '&d'
                suffix: Miner
            permissions: []
              - Miner
            group: Peasant
                prefix: '&d'
                suffix: Healer
            permissions: []
              - Healer
            group: Peasant
                prefix: '&d'
                suffix: Farmer
            permissions: []
              - Farmer
            group: Peasant
                prefix: '&d'
                suffix: Miner
            permissions: []
              - Miner
              - Railer
    You can see that the node structure are exactly the same used for GroupManager 0.99d(-) and Permissions, it means you can use the same files here.
    Note: Every node that doesn't make part of the respective file is ignored. So if you are migrating from older GroupManager or Permissions you can just duplicate your files as groups.yml and users.yml. When comes the time where is needed to save the file, all unused data for each file will be discarded. So you don't need to split files, just duplicate them with correct names, it will work.

    Negative and Exception nodes: a brief explanation
    Let's say you have a group SemiAdmin like this.
        default: false
        permissions: [+groupmanager.manpromote, -groupmanager.*,
        inheritance: [Moderator]
        info: {prefix: '', build: false, suffix: ''}
    You should read this way:
    '*' -> means this group will have access to all commands.
    '-groupmanager.*' -> Where all his commands of groupmanager where removed.
    '+groupmanager.manpromote' -> Except manpromote.

    It means he can do everything that is not of GroupManager, AND manpromote.

    It's like listing essentials.*, worldedit.*, worldprotect.*, everyotherthing.* and groupmanager.manpromote.

    It gives a very big flexibility on permissions.

    For every level of inheritance,
    Every permission starting with '+' is tested first. Then comes permissions starting with '-'. Then comes normal permissions(including '*').

    • Now on multiword support, every command will act only on the selected world.
    • If none/invalid world is selected, it will run on the default world.
    • If the world selected is a mirrored world, it will work on the mirror world.
    (on next version, when a command involves a player, there will be a toggle that will automatically act on the victim(player) world is in)
        description: Move a player to desired group.(Adds to the file if not exists)
        usage: /<command> <player> <group>
        permission: groupmanager.manuadd
        description: Remove any user specific configuration. Make him default group.
        usage: /<command> <player>
        permission: groupmanager.manudel
        description: Add a group to a player's subgroup list.
        usage: /<command> <player> <group>
        permission: groupmanager.manuaddsub
        description: Remove a group to a player's subgroup list.
        usage: /<command> <player> <group>
        permission: groupmanager.manudelsub
        description: Add group to the system.
        usage: /<command> <group>
        permission: groupmanager.mangadd
        description: Removes group from the system(all it's users become default)
        usage: /<command> <group>
        permission: groupmanager.mangdel
        description: Add permission diretly to the player.
        usage: /<command> <player> <permission>
        permission: groupmanager.manuaddp
        description: Removes permission diretly from the player.
        usage: /<command> <player> <permission>
        permission: groupmanager.manudelp
        description: List all permissions from a player.
        usage: /<command> <player>
        permission: groupmanager.manulistp
        description: Verify if user has a permission, and where it comes from.
        usage: /<command> <player> <permission>
        permission: groupmanager.manucheckp
        description: Add permission to a group.
        usage: /<command> <group> <permission>
        permission: groupmanager.mangaddp
        description: Removes permission from a group.
        usage: /<command> <group> <permission>
        permission: groupmanager.mangdelp
        description: Lists all permissions from a group.
        usage: /<command> <group>
        permission: groupmanager.manglistp
        description: Check if group has a permission, and where it comes from.
        usage: /<command> <group> <permission>
        permission: groupmanager.mangcheckp
        description: Add a group to another group inheritance list.
        usage: /<command> <group1> <group2>
        permission: groupmanager.mangaddi
        description: Remove a group from another group inheritance list.
        usage: /<command> <group1> <group2>
        permission: groupmanager.mangdeli
        description: Add, or replaces, a variable to a user (like prefix or suffix).
        usage: /<command> <user> <variable> <value>
        permission: groupmanager.manuaddv
        description: Remove a variable from a user.
        usage: /<command> <user> <variable>
        permission: groupmanager.manudelv
        description: List variables a user has (like prefix or suffix).
        usage: /<command> <user>
        permission: groupmanager.manulistv
        description: Verify a value of a variable of user, and where it comes from.
        usage: /<command> <user> <variable>
        permission: groupmanager.manucheckv
        description: Add, or replaces, a variable to a group (like prefix or suffix).
        usage: /<command> <group> <variable> <value>
        permission: groupmanager.mangaddv
        description: Remove a variable from a group.
        usage: /<command> <group> <variable>
        permission: groupmanager.mangdelv
        description: List variables a group has (like prefix or suffix).
        usage: /<command> <group>
        permission: groupmanager.manglistv
        description: Verify a value of a variable of group, and where it comes from.
        usage: /<command> <group> <variable>
        permission: groupmanager.mangckeckv
        description: Tell the group that user belongs.
        usage: /<command> <player>
        permission: groupmanager.manwhois
        description: Creates a temporary permission copy for that user.
        usage: /<command> <player>
        permission: groupmanager.tempadd
        description: Remove the temporary permission copy for player.
        usage: /<command> <player>
        permission: groupmanager.tempdel
        description: List players in overload-permissions mode made by /tempadd.
        usage: /<command>
        permission: groupmanager.templist
        description: Remove all overrides made by command /tempadd.
        usage: /<command>
        permission: groupmanager.tempdelall
        description: Save all permissions on file.
        usage: /<command>
        permission: groupmanager.mansave
        description: Reload current world and config.yml. Or load given world.
        usage: /<command> [world]
        permission: groupmanager.manload
        description: List the groups available.
        usage: /<command>
        permission: groupmanager.listgroups
        description: Promote a player in the same heritage line to a higher rank.
        usage: /<command> <player> <group>
        permission: groupmanager.manpromote
        description: Demote a player in the same heritage line to a lower rank.
        usage: /<command> <player> <group>
        permission: groupmanager.mandemote
        description: Toggle on/off the validating if player is online.
        usage: /<command>
        permission: groupmanager.mantogglevalidate
        description: Toggle on/ff the autosave.
        usage: /<command>
        permission: groupmanager.mantogglesave
        description: Prints the selected world name
        usage: /<command>
        permission: groupmanager.manworld
        description: Select a world to work with next commands.
        usage: /<command> <world>
        permission: groupmanager.manselect
        description: Clear world selection. Next commands will work on your world.
        usage: /<command>
        permission: groupmanager.manclear
    All commands that changes permissions only allow you to change users below in a inheritance level(eg. Admins can't mod other Admins, but can modify Moderators).
    Except for Console, he can modify anyone.

    So, what happens with all of these plugins that already use Permissions?
    They will still work. I made a fake Permissions plugin, that will replace your old Permissions plugin. And the new fake one will attach directly on GroupManager system. So all plugins will think they are working with Permissions, but they will work with GroupManager.
    The most incredible thing is that all those plugins will receive the benefit of instant changes.

    I'm a server Administrator, what should I do to use it?
    If you already have Permissions, do this:
    1. Remove Permissions.jar from you plugins folder. (leave the Permissions folder there, if it is named diferently than this, the automatic import will not work)
    2. Paste GroupManager.jar with FakePermissions.jar on your plugins folder.
    3. Run.
    4. With all file structure done, you create your worlds folder and copy your files there.

    All your old plugins will still work like a charm.

    I'm a plugin developer, how should I use this plugin?
    You can read the java-doc, linked below. It's not complete yet, but it has the essential.
    Here is some code examples...

    Loading in your plugin:
    import org.anjocaido.groupmanager.GroupManager;
    import org.anjocaido.groupmanager.dataholder.worlds.WorldsHolder;
    import org.anjocaido.groupmanager.dataholder.WorldDataHolder;
    public void onEnable() {
            Plugin p = this.getServer().getPluginManager().getPlugin("GroupManager");
            if (p != null) {
                if (!this.getServer().getPluginManager().isPluginEnabled(p)) {
                GroupManager gm = (GroupManager) p;
                WorldsHolder wd = gm.getWorldsHolder();
            } else {
    WorldsHolder contains everything you need. You can easily do anything with it.

    Here is a example of a plugin that in a special circumstance, needed to put the player in a special group, with no permissions at all.
    public void markAsNotLoggedIn(Player player) {
                OverloadedWorldHolder perm = gm.getWorldsHolder().getWorldData(player);
                Group lockDown = perm.getGroup("NotLoggedIn");
                if(lockDown == null){
                    lockDown = perm.createGroup("NotLoggedIn");
    From now on the user is in this special group. And every change on him is temporary. Until the code below is executed.
    public void restorePermissions(Player player){
                OverloadedWorldHolder perm = gm.getWorldsHolder().getWorldData(player);
    And, finally, how to check a user permission:
    public boolean canChangeGroup(Player player){
                return gm.getWorldsHolder().getWorldPermissions(player).has(player,"groupmanager.mangroup");
    Q: It is compatible with permissions... but where it get it's data from?
    - A: It gets from users.yml and groups.yml in the world folder, located properly inside GroupManager worlds folder.
    Q: Can I use commands from other plugins to change permissions?
    - A: No. I made the decision to store data in GroupManager folder because I don't think it is right my plugin mess around with other ones files. Unfortunately, other plugins of group modification tries to access other files than mine.

    Version 1.0 alpha-5:
    • Fixed a bug in method String[] groups(groupName)
    • Added some functionality to Tasks class
    • Fixed some errors in JavaDoc
    • Changed templates to make use of Roles plugin
    Show Spoiler

    Version 1.0 alpha-4:
    • Fixed subgroups listing when using /manulistp
    Version 1.0 alpha-3:
    • Basic user multigroup support using subgroups concept.
    • Added tracking for minor bugs.
    Version 1.0 alpha-2:
    • Now /manload reloads config.yml(which means mirror configuration receives updates too).
    Version 1.0 alpha:
    • Fixed some issues with /manpromote and /mandemote for multiples inheritances
    • Added permission node for commands in plugin.yml. So the newer EssentialsHelp feature I created will filter commands that people don't have(dev #688).
    Version 1.0 pre-alpha-3:
    • Now /manucheckp and /mangcheckp tells you if the permission was negated by a negation node.
    • Now using Breadth-first search for inheritance harvest. It guarantees that closer groups in inheritance are checked first.
    • Fixed some bugs, where a negation node directly in a user could be ignored.
    • Now it reads old data.yml and auto-install it to default world if none is found.
    • Created a system where plugins can get detailed answers from a permission check.
    • Deprecated some inefficient methods(all of them redirects to the new efficient method), but they still works.
    Version 1.0 pre-alpha-2:
    • World selection is optional, except for console.
    • Not selecting a world makes it run on same world of the command sender.
    • Fixed "temporary permissions" system.
    • Fixed most of commands bugs(I fixed all errors I could see)
    • Fake Permissions says it's 2.5 now, so plugins like HeroChat works now(yay).
    • Fixed some unnecessary file saves.
    • Added /manclear to clear selection
    • /manselect now lists physical worlds if no parameters are given.
    • /manload can load a world not loaded before, if given a parameter.
    Version 1.0 pre-alpha:
    • Refactored a lot of things. Please check the java-docs.
    • Added multiworld support.
    • Split files in users.yml and data.yml
    • Saves only files that needs changes
    • Fixed some bugs
    • World mirroring
    • Basic commands for world selection, to keep old commands working.
    Version 0.99d:
    • Fixed more small bugs.
    • Saves in human readable format
    • Deletes backups older than 24 hours
    Version 0.99c:
    • Fixed small bugs. Like /mangaddi
    • Changed some classes package
    Version 0.99b:
    • Fixed Group Variables, that I broke last version.(restore your backups, yay)
    Version 0.99a:
    • User specific variables. Prefixes, Suffixes and more.
    • Negative permission node(prevails normal nodes). Like '-groupmanager.*'
    • Exception permission node(prevails negative nodes). Like '+groupmanager.manpromote'
    Version 0.9e:
    • It writes a template it self if doesn't find any data.yml file on the folder.
    Version 0.9d:
    • FakePermissions adapted to new CB builds.
    Version 0.9c:
    • Multiple inheritance fixed.
    • Added a command to toggle auto-saving, so you can edit the file while it is disabled.
    • Tested with server 1.3
    Version 0.9b:
    • Now variables work with spaced strings.(you can add prefix with spaces)
    • Fixed some errors while loading files in later 400+ builds.
    • FakePermissions got small update.
    Version 0.9:
    • Added variables manipulation command(things in info node, such as prefix, suffix, build, and custom ones)
    • Improved FakePermissions support for the Nijikokun's original one.
    • FakePermissions force loading of GroupManager before itself.
    Version 0.8:
    • Added tons of commands. Resulting in a complete control, inside the game.
    • Renamed some commands in the same format Wulfspider sugested.
    • FakePermissions.jar updated to take care oc Misc field, which some Permissions plugins need.
    Version 0.7:
    • Added commands /manpromote and /mandemote
    • Fixed a bug where a file with an empty permissions node in a group could fail the plugin to load.
    • now /addpermissions can only add permissions that the player have access.
    Version 0.6c:
    • Removed the debugging messages that occurs while other plugins check permissions.
    • Removed the debugging messages on FakePermissions
    Version 0.6b:
    • Fixed inheritance system I broke in 0.6. Sorry.
    Version 0.6:
    • Fixed some bugs
    • User/Group class modelled in tiny different way(check JavaDocs)
    • Commands work on Console
    Version 0.5:
    • First fully working release.

    Future plans (they are closer than you think):
    • Make commands for cloning files, and world mirroring.
    • Implements Nijiko's interface for permission changing.
    • Make it work, optionally, with SQLite/MySQL(thinking of Persistence plugin, anyone with ideas?).

    Latest Build Download:

    Other Downloads:
    Java Doc:

    Plugins I love to use with GroupManager:
    Roles, Essentials, AntiGrief, iChat, MultiVerse, WorldEdit and WorldProtect.

    Fake Permissions Source:
    TNC, Kohle, pat8u and 17 others like this.
  2. Offline


    you have to use another plugin for this, check out AntiGrief or AntiBuild plugins, most of them support this flag if they support permissions.
  3. Offline


    thx! Didn't know that [​IMG]
    I will use this AntiGrief
  4. Offline


    Version 0.7 out.
    Now has /manpromote and /manreload.

    Unlike /mangroup, which gives you permission to edit the user the way you want... those two new commands are very strict.

    If you have the group inheritance line:
    Admin > Moderator > Vip > Builder > Untrusted
    and give everyone /manpromote and /manreload

    Builder/Untrusted can't promote/demote anyone.
    Vip can promote Untrusted to Builder, or demote Builder to Untrusted.
    Moderator can do the same as Vip. Or Promote Builders/Untrusted to Vip. Or demote Vip to Builder/Untrusted.

    Long story short:
    With these you can manage any user levels that are below to yours. Give them higher/lower ranks, but still should be lower to yours.
    If you create a group that is not on same heritage line, no one can promote/demote them, because the GroupManager could not define which is higher or lower.
  5. Offline


    Wulfspider, sounds totally... win?
  6. Offline


    hmm...when i change my data.yml, GroupManager looks like not started (/plugins say only: AntiGrief, Permissions):
        default: true
        permissions: [general.spawn]
        inheritance: []
        info: {prefix: '', build: false, suffix: ''}
        default: false
        permissions: ['*']
        inheritance: [Moderator]
        info: {prefix: '', build: true, suffix: ''}
        default: false
        permissions: [general.time, general.teleport,, general.player-info]
        inheritance: [Default]
        info: {prefix: '', build: true, suffix: ''}
      permissions: {system: default}
  7. Offline


    Hello, could it be that the Trivia plugin doesn't work with this? I get always if I try to activate trivia “Error: null”.

  8. Offline


    If you added MySQL support to this, it would be perfect, since I'm planning to migrate as much of the server as possible to MySQL to integrate better with a site I'm making for it.
  9. Offline


    going to try this ASAP!!! becuase permissions is realy pissing me the hell off bigtime.
  10. Offline


    I know this might be a dumb question but I cant find it in any of the directions or anywhere that I have looked.

    How do I put users into groups via the console? I want to put myself in the Admins group but I cant figure it out. Thanks!
  11. Offline


    let's suppose you want make anjocaido as admin:
    on console type:
    mangroup anjocaido admin

    Notice: use no slashes to any command on Console
    --- merged: Feb 20, 2011 8:33 PM ---
    I'll check that plugin.
    --- merged: Feb 20, 2011 8:33 PM ---
    I plan to start developing for databases next week. If everything goes right with this plugin.
  12. Offline


    It still didn't work :( I will paste my console and maybe you could tell me if I entered the plugin wrong.. Thanks again dude!
    --- merged: Feb 20, 2011 8:34 PM ---
    2011-02-20 20:30:22 [INFO] Starting minecraft server version Beta 1.2_01
    2011-02-20 20:30:22 [INFO] Loading properties
    2011-02-20 20:30:22 [INFO] Starting Minecraft server on *:25565
    2011-02-20 20:30:22 [INFO] This server is running Craftbukkit version git-Bukkit-0.0.0-428-g51dd641-b52jnks (MC: 1.2_01)
    2011-02-20 20:30:22 [INFO] Preparing level "world"
    2011-02-20 20:30:22 [INFO] Preparing start region
    2011-02-20 20:30:23 [INFO] Preparing spawn area: 36%
    2011-02-20 20:30:24 [INFO] Preparing spawn area: 40%
    2011-02-20 20:30:26 [INFO] Preparing spawn area: 69%
    2011-02-20 20:30:27 [WARNING] Using the stupidly long constructor com.thelair.tuna.tpack.TPack(PluginLoader, Server, PluginDescriptionFile, File, File, ClassLoader) is no longer recommended. Go nag the plugin author of TPack to remove it! (Nothing is broken, we just like to keep code clean.)
    2011-02-20 20:30:27 [WARNING] Using the stupidly long constructor org.anjocaido.groupmanager.GroupManager(PluginLoader, Server, PluginDescriptionFile, File, File, ClassLoader) is no longer recommended. Go nag the plugin author of GroupManager to remove it! (Nothing is broken, we just like to keep code clean.)
    2011-02-20 20:30:27 [INFO] Hint! It's probably someone called 'AnjoCaido'
    2011-02-20 20:30:27 [SEVERE] Feb 20, 2011 8:30:27 PM org.bukkit.craftbukkit.CraftServer loadPlugins
    SEVERE: com/nijiko/Messaging (Is it up to date?)
    java.lang.NoClassDefFoundError: com/nijiko/Messaging
    at com.thelair.tuna.tpack.TPack.setupPermissions(
    at com.thelair.tuna.tpack.TPack.onEnable(
    at org.bukkit.plugin.SimplePluginManager.enablePlugin(
    at org.bukkit.craftbukkit.CraftServer.loadPlugin(
    at org.bukkit.craftbukkit.CraftServer.loadPlugins(
    at net.minecraft.server.MinecraftServer.e(
    at net.minecraft.server.MinecraftServer.c(
    at net.minecraft.server.MinecraftServer.d(
    Caused by: java.lang.ClassNotFoundException: com.nijiko.Messaging
    at$ Source)
    at Method)
    at Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    ... 12 more

    2011-02-20 20:30:27 [INFO] Done! For help, type "help" or "?"
  13. Offline


    Can you show me the error in the console?
    --- merged: Feb 20, 2011 8:36 PM ---
    It seems that plugin is using some unusual features of Permissions. Those are not in GroupManager yet because I couldn't find documentation of them.
    I'm still trying to understand those features, to put them inside GroupManager as soon as possible.
  14. Offline


    I deleted everything of Permissions when I put in GroupManager. I had just downloaded Permissions and I saw this and I thought it would be better and more simple so I downloaded GroupManager, took everything out from Permissions and put in GroupManager.. Do you know how I can fix this?
  15. Offline


    Yes, I plan to create commands very similar to those.

    If I get most of them working today. I think we'll have an update.
  16. Offline


    I think i got it to work! I added FakePermissions into it and its reading me now! THANK YOU!!! :):)
  17. Offline


    Take off the plugin TPack.

    I'm going to make a test with that plugin... maybe I get it working with TPack in some hours.
    --- merged: Feb 20, 2011 8:45 PM ---
    But TPack probably will still not work properly.
  18. Offline


    It worked for me? I can use boomstick and cuboid and all that :)
  19. Offline


    Version 0.8 is out with a new set of commands!

    Thanks for Wulfspider for command names suggestion.


    Please everyone update your FakePermissions.jar


    Advice: There is no need to use /mansave neither /manload to see the changes of every command. Those two commands you use only if you are sure you need to.
    --- merged: Feb 21, 2011 3:22 AM ---
    Now that the GroupManager is very well settled. Probably changes aren't going to be huge.

    Suggestions are still very well received.
  20. Offline


    Well ,as you implemented the hole set of comands to create and modify the groups parameter ingame, could u add a comand to edit the prefix of a created group? Or maybe set the /mangadd to add the prefix to be the same as the group name.
  21. Offline


    getting this error when players try to use LWC using 0.7 of the groupmanager

    Feb 21, 2011 1:10:37 AM org.bukkit.plugin.SimplePluginManager callEvent
    SEVERE: Could not pass event BLOCK_DAMAGED to LWC
    java.lang.NoClassDefFoundError: com/nijiko/permissions/Control
            at com.griefcraft.lwc.LWC.enforceProtectionLimits(
            at com.griefcraft.listeners.LWCBlockListener.blockTouched(
            at com.griefcraft.listeners.LWCBlockListener.onBlockDamage(
            at org.bukkit.plugin.RegisteredListener.callEvent(
            at org.bukkit.plugin.SimplePluginManager.callEvent(
            at net.minecraft.server.NetServerHandler.a(
            at net.minecraft.server.Packet14BlockDig.a(SourceFile:42)
            at net.minecraft.server.NetworkManager.a(SourceFile:232)
            at net.minecraft.server.NetServerHandler.a(
            at net.minecraft.server.NetworkListenThread.a(SourceFile:104)
            at net.minecraft.server.MinecraftServer.h(
  22. Offline


    Did you place FakePermissions.jar in your plugins folder?

    Maybe 0.8 maybe could do the trick, because fakepermissions was packed with all Permissions classes inside.
    But I'm not sure about it.
    --- merged: Feb 21, 2011 7:40 AM ---
    I'm going to make my AnjoPermissionsHandler extends Nijikokun's Control class... so everything should be fine...
  23. Offline


    Great, Amazing, just the right thing we needed! I love the promote feature! Good Job, CONTINUE! ;)
  24. Offline


    I was just using .7 and updated. This is not importing the old permissions yml correctly... .8 v
    Every time I try it manually it overwrites the edits i made.

    Edit: Fixed... seems the data.yml file got overwritten by this and that? Just did the whole thing from beginning and it worked.

    Edit2: After I noticed the file autosaved I checked the new data.yml and it's now converted differently. Ran it thru the yaml parser and get errors. Don't know if this is how it's meant to work.
  25. Offline


    Yay! Thanks for the changes.

    I wasn't sure about the need to use those commands or not either...
  26. Offline


    Post your original(working) and modified(not working) version of data.yml contents inside [ CODE ] and [ / CODE ] tags... so I can see what's going on.

    Unfortunately the parser changes the file... but it should be parsed by any YAML parser successfully.
    --- merged: Feb 21, 2011 10:26 AM ---
    I found out that some Plugins, like LWC, asks for permissions the wrong way.
    First: They use the static field Security, made by Nijikokun's. Access a field from another plugin while your plugin is loading is wrong. Always use methods(so the requested plugin can ask to itself to enable before your's), if available.
    Second: They load things from other plugins and don't verify if the requested plugin is loaded. You can easily verify that with isEnabled(), and then call the PluginLoader.enablePlugin(p) to enable in case if that one is disabled.

    That might be a reason of some plugins fail to load.


    Here is a version of LWC 1.53 that should run with latest build of CraftBukkit, where it works perfectly with GroupManager 0.9(releasing soon). And I just added 3 lines to the code. It's not that hard to code the right way after all.


    --- merged: Feb 21, 2011 12:44 PM ---
    Released version 0.9:
    Now it has variables support(everything inside info node), such as prefix, suffix and build.

    To add variables use:
    /mangaddv <group> <variable> <value>

    /mangaddv admin prefix &c
    /mangaddv moderator suffix &d
    /mangaddv vip build true

    String values with spaces doesn't work, yet.

    To remove use /mangdelv <group> <variable>
    Variables such as prefix, suffix and build get to their default values when removed: empty, empty and false.

    To list variables from a group use:
    /manglistv <group>

    To check the variable value use:
    /mangcheckv <group> <variable>

    FakePermissions got updated too. Make sure to use the latest version if you are having problems with some plugins.

    Long Constructor is still used, to maintain compatibility to other plugins
  27. Offline


    Thank you a lot! With version 0.9 trivia works. You could also add build 361 to the working ones.

  28. Offline


    doesnt work for me. Copying the file from the permissions folder didnt work, so i did it myself. but then, we still had no titles after i reloaded and my people couldnt use commands. Here is my permissions file.
  29. Offline


    Did you see any console errors? What plugins are you using(besides essentials, which is completely compatible)?

    Mainly, what is your chat plugin(or the plugin about the titles)?
    Didn't the essentials commands work?

    I tested your file... and the permissions work perfectly with Essentials. The plugin is loading fine.
    Did you put that data inside data.yml file?

    But as you have groups with spaces in their names(which is very uncommon, and not recommended), using most commands this plugin provides will not work, if they involve those groups names.
  30. Offline


    nope none of my members were able to do /home or /tp or /spawn. and i use ichat for titles.
  31. Offline


    iChat is compatible with GroupManager, as is Essentials(in fact, Essentials developers are working to include GroupManager in the package)...
    I tested your file, using usernames already listed there, of different groups, and it works here.

    Make sure to paste that file on GroupManager folder, with name: data.yml

    If you are using versions of plugins directly from repository, take care. Essentials is absorbing GroupManager, so you should not use the EssentialsGroupManager.jar... and I'm not sure of whats happening there, nothing is certain that works.

    iChat 1.4 has been largely tested, and it works. The main problem is that iChat makes a cache for groups prefixes and suffixes. So changing them doesn't affect during the game.
Thread Status:
Not open for further replies.

Share This Page