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

    AnjoCaido

    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:
    Code:
    settings:
      data:
        save:
          minutes: 10
      logging:
        level: INFO
      permission:
        world:
          mirror:
            world1:
              - world2
              - world3
            world4:
              - 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:
    plugins/GroupManager/worlds/WORLDNAME

    So the file structure for the world called anjoCaidoWorld and netherWorld will be:
    plugins/GroupManager/worlds/anjoCaidoWorld/groups.yml
    plugins/GroupManager/worlds/anjoCaidoWorld/users.yml
    plugins/GroupManager/worlds/netherWorld/groups.yml
    plugins/GroupManager/worlds/netherWorld/users.yml

    The files might look like this:
    groups.yml
    Code:
    groups:
        Admins:
            default: false
            info:
                build: false
                prefix: ''
                suffix: ''
            inheritance:
            - SemiAdmin
            permissions:
            - '*'
        Default:
            default: true
            info:
                build: false
                prefix: ''
                suffix: ''
            inheritance: []
            permissions:
            - essentials.spawn
            - essentials.motd
            - essentials.help
            - essentials.home
            - essentials.sethome
        Moderator:
            default: false
            info:
                build: false
                prefix: '&c'
                suffix: 'Mod'
            inheritance:
            - Default
            permissions:
            - essentials.tp
            - essentials.tphere
            - essentials.item
            - essentials.give
        SemiAdmin:
            default: false
            info:
                build: false
                prefix: '&c'
                suffix: 'SemiAdmin'
            inheritance:
            - Moderator
            permissions:
            - +groupmanager.mandemote
            - +groupmanager.manpromote
            - -groupmanager.*
            - '*'
        Peasant:
            default: true
            info:
                build: false
                prefix: '&e'
                suffix: 'Peasant'
            inheritance:
            - Default
            permissions: []
        Miner:
            default: false
            info:
                build: false
                prefix: ''
                suffix: ''
            inheritance:
            permissions:
            - essentials.kit
            - essentials.kit.miner
            - flashlight.regular
        Healer:
            default: false
            info:
                build: false
                prefix: ''
                suffix: ''
            inheritance:
            permissions:
            - essentials.kit
            - essentials.kit.healer
            - essentials.heal
        Farmer:
            default: false
            info:
                build: false
                prefix: ''
                suffix: ''
            inheritance:
            permissions:
            - essentials.kit
            - essentials.kit.farmer
            - essentials.spawnmob
        Railer:
            default: false
            info:
                build: false
                prefix: ''
                suffix: ''
            inheritance:
            permissions:
            - essentials.kit
            - essentials.kit.railer
    users.yml
    Code:
    users:
        anjocaido:
            group: Admins
            info:
                prefix: '&c'
                suffix: King
            permissions: []
        gmcouto:
            group: SemiAdmin
            permissions: []
        zenexer:
            group: Moderator
            permissions:
            - essentials.god
        aMiner:
            group: Peasant
            info:
                prefix: '&d'
                suffix: Miner
            permissions: []
            subgroups:
              - Miner
        aHealer:
            group: Peasant
            info:
                prefix: '&d'
                suffix: Healer
            permissions: []
            subgroups:
              - Healer
        aFarmer:
            group: Peasant
            info:
                prefix: '&d'
                suffix: Farmer
            permissions: []
            subgroups:
              - Farmer
        tempRailer:
            group: Peasant
            info:
                prefix: '&d'
                suffix: Miner
            permissions: []
            subgroups:
              - 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.
    Code:
    groups:
      SemiAdmin:
        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.

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

    Commands:
    • 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)
    Code:
    commands:
      manuadd:
        description: Move a player to desired group.(Adds to the file if not exists)
        usage: /<command> <player> <group>
        permission: groupmanager.manuadd
      manudel:
        description: Remove any user specific configuration. Make him default group.
        usage: /<command> <player>
        permission: groupmanager.manudel
      manuaddsub:
        description: Add a group to a player's subgroup list.
        usage: /<command> <player> <group>
        permission: groupmanager.manuaddsub
      manudelsub:
        description: Remove a group to a player's subgroup list.
        usage: /<command> <player> <group>
        permission: groupmanager.manudelsub
      mangadd:
        description: Add group to the system.
        usage: /<command> <group>
        permission: groupmanager.mangadd
      mangdel:
        description: Removes group from the system(all it's users become default)
        usage: /<command> <group>
        permission: groupmanager.mangdel
      manuaddp:
        description: Add permission diretly to the player.
        usage: /<command> <player> <permission>
        permission: groupmanager.manuaddp
      manudelp:
        description: Removes permission diretly from the player.
        usage: /<command> <player> <permission>
        permission: groupmanager.manudelp
      manulistp:
        description: List all permissions from a player.
        usage: /<command> <player>
        permission: groupmanager.manulistp
      manucheckp:
        description: Verify if user has a permission, and where it comes from.
        usage: /<command> <player> <permission>
        permission: groupmanager.manucheckp
      mangaddp:
        description: Add permission to a group.
        usage: /<command> <group> <permission>
        permission: groupmanager.mangaddp
      mangdelp:
        description: Removes permission from a group.
        usage: /<command> <group> <permission>
        permission: groupmanager.mangdelp
      manglistp:
        description: Lists all permissions from a group.
        usage: /<command> <group>
        permission: groupmanager.manglistp
      mangcheckp:
        description: Check if group has a permission, and where it comes from.
        usage: /<command> <group> <permission>
        permission: groupmanager.mangcheckp
      mangaddi:
        description: Add a group to another group inheritance list.
        usage: /<command> <group1> <group2>
        permission: groupmanager.mangaddi
      mangdeli:
        description: Remove a group from another group inheritance list.
        usage: /<command> <group1> <group2>
        permission: groupmanager.mangdeli
      manuaddv:
        description: Add, or replaces, a variable to a user (like prefix or suffix).
        usage: /<command> <user> <variable> <value>
        permission: groupmanager.manuaddv
      manudelv:
        description: Remove a variable from a user.
        usage: /<command> <user> <variable>
        permission: groupmanager.manudelv
      manulistv:
        description: List variables a user has (like prefix or suffix).
        usage: /<command> <user>
        permission: groupmanager.manulistv
      manucheckv:
        description: Verify a value of a variable of user, and where it comes from.
        usage: /<command> <user> <variable>
        permission: groupmanager.manucheckv
      mangaddv:
        description: Add, or replaces, a variable to a group (like prefix or suffix).
        usage: /<command> <group> <variable> <value>
        permission: groupmanager.mangaddv
      mangdelv:
        description: Remove a variable from a group.
        usage: /<command> <group> <variable>
        permission: groupmanager.mangdelv
      manglistv:
        description: List variables a group has (like prefix or suffix).
        usage: /<command> <group>
        permission: groupmanager.manglistv
      mangcheckv:
        description: Verify a value of a variable of group, and where it comes from.
        usage: /<command> <group> <variable>
        permission: groupmanager.mangckeckv
      manwhois:
        description: Tell the group that user belongs.
        usage: /<command> <player>
        permission: groupmanager.manwhois
      tempadd:
        description: Creates a temporary permission copy for that user.
        usage: /<command> <player>
        permission: groupmanager.tempadd
      tempdel:
        description: Remove the temporary permission copy for player.
        usage: /<command> <player>
        permission: groupmanager.tempdel
      templist:
        description: List players in overload-permissions mode made by /tempadd.
        usage: /<command>
        permission: groupmanager.templist
      tempdelall:
        description: Remove all overrides made by command /tempadd.
        usage: /<command>
        permission: groupmanager.tempdelall
      mansave:
        description: Save all permissions on file.
        usage: /<command>
        permission: groupmanager.mansave
      manload:
        description: Reload current world and config.yml. Or load given world.
        usage: /<command> [world]
        permission: groupmanager.manload
      listgroups:
        description: List the groups available.
        usage: /<command>
        permission: groupmanager.listgroups
      manpromote:
        description: Promote a player in the same heritage line to a higher rank.
        usage: /<command> <player> <group>
        permission: groupmanager.manpromote
      mandemote:
        description: Demote a player in the same heritage line to a lower rank.
        usage: /<command> <player> <group>
        permission: groupmanager.mandemote
      mantogglevalidate:
        description: Toggle on/off the validating if player is online.
        usage: /<command>
        permission: groupmanager.mantogglevalidate
      mantogglesave:
        description: Toggle on/ff the autosave.
        usage: /<command>
        permission: groupmanager.mantogglesave
      manworld:
        description: Prints the selected world name
        usage: /<command>
        permission: groupmanager.manworld
      manselect:
        description: Select a world to work with next commands.
        usage: /<command> <world>
        permission: groupmanager.manselect
      manclear:
        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:
    Code:
    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)) {
                    this.getServer().getPluginManager().enablePlugin(p);
                }
                GroupManager gm = (GroupManager) p;
                WorldsHolder wd = gm.getWorldsHolder();
            } else {
                this.getPluginLoader().disablePlugin(this);
            }
        }
    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.
    Code:
    public void markAsNotLoggedIn(Player player) {
                OverloadedWorldHolder perm = gm.getWorldsHolder().getWorldData(player);
                Group lockDown = perm.getGroup("NotLoggedIn");
                if(lockDown == null){
                    lockDown = perm.createGroup("NotLoggedIn");
                }
                perm.overloadUser(player.getName());
                perm.getUser(player.getName()).setGroup(lockDown);
        }
    From now on the user is in this special group. And every change on him is temporary. Until the code below is executed.
    Code:
    public void restorePermissions(Player player){
                OverloadedWorldHolder perm = gm.getWorldsHolder().getWorldData(player);
                perm.removeOverload(player.getName());
        }
    And, finally, how to check a user permission:
    Code:
    public boolean canChangeGroup(Player player){
                return gm.getWorldsHolder().getWorldPermissions(player).has(player,"groupmanager.mangroup");
        }
    F.A.Q.
    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.

    Changelog:
    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:
    http://www.mdn.fm/files/276497_as2zr/GroupManager-1.0-alpha-5.zip


    ===========================================
    Other Downloads:
    Java Doc:
    http://www.mdn.fm/files/276266_vqd0d/JavaDoc-GroupManager-1.0-alpha-3.zip

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


    ===========================================
    Source:
    https://github.com/gmcouto/GroupManager
    Fake Permissions Source:
    https://github.com/gmcouto/FakePermission
     
    TNC, Kohle, pat8u and 17 others like this.
  2. Offline

    Wulfspider

    Looks like that fixed my other problem I saw too... where every command was echoing. Yayy! Thanks for the quick updates Anjo, and excellent work! Have a cookie! :D
     
  3. Offline

    AnjoCaido

    yummie
     
  4. Offline

    Deatlev

    I cant get this to work :( i have no idea what to write in the config, i need permissions for TPack and im a noob and dunno how to get any permissions at all...

    edit: I knew I've seen ur name before...you made my minecraft launcher
     
  5. Offline

    AnjoCaido

    You edit the data.yml for permissions, in GroupManager.
    Get the template on the folder and edit from there.

    There are nodes called permissions... just like this for groups:
    groups:
    Or this, for users:
    The permissions node is a list node... it means you can list a lot of things.
    In YAML you can do list in two ways:
    It's your choice how to write the file. Those last examples contains the permissions of TPack. Just fill it on the group/user you want.

    You need to keep all nodes aligned(put spaces) just like on the template packed. It is very important to do that. Search on google for notepad++(I'm not sure if this is the one people recommend, I don't use Windows) to edit the file, or any editor that parse YAML, it will make sure the file is valid.
     
  6. Offline

    Juze

    I'm excited, though I don't seem to find much of use for this yet.
     
  7. Offline

    Deatlev

    lol i still dont understand so much xD could you just give an example how it would be if i want permission for TPack and maybe some groups that gives right blabla...i dont even know what im talking about
    Edit again: i log on and it says i dont got permission to use that command, how i get permissions to it?
    edit: i did this
    permissions: [tpack.boomstick,
    tpack.cuboid,
    tpack.time,
    tpack.snap,
    tpack.items]
     
  8. Offline

    AnjoCaido

    Think as a plugin about teams PvP wich uses permissions and a spefic territory on Map for battles.
    You could map the teams easily detecting if the a user got in the Battle territory, then you overload him, and set him on a group "Neutral" that he can choose teams using commands, /Blue or /Red... after he chooses the blue team, his group is changed to BlueTeam, he then receives special permissions, wich allow him to enter on the arena by the Blue gate, and do other commands related to blueteam... he goes there and fight. When he dies or he's got out of the arena, the overload is taken off... and his group and permissions are the same as he started off.
    Nothing special here. You could do that before, just needed to program more. But it was very high risk, because all those group modifications were directly on file, and any problems on your server or a plugin may cause that guy stay saved on BlueTeam.

    Now imagine if it happens two teams of 10 people at same time.(like server crashing)

    Can you see the effort is going to set all those people up to their groups back?

    It just won't happen in GroupManager.
     
  9. Offline

    HotelErotica

    @AnjoCaido Would it be possible to add just a promotion command that'll let you bump someone up through the ranks and it'll only let you move someone to a rank below your self So if your groups were Untrusted, Guest, Regular, Mod, Admin. A Regular could move someone to guest and a mod could move someone up to regular.
     
  10. Offline

    AnjoCaido

    You need to make sure if you put that on the same group your user are registered into.

    If your user is not on the file, put it there. There is a big template in data.yml in GroupManager folder provided in the ZIP file.
    --- merged: Feb 19, 2011 9:42 AM ---
    Good idea. it will be on... today.

    Or maybe not today... let me think...
    As the permissions system can support parallel inheritance lines. mmm... I think I can do.
     
  11. Offline

    Wulfspider

    I guess a command to add a permission to a group is already thought of? As well as the removal of a group, moving all users from one group to another, and combining /mancommit and /manreload into one command.

    Some new commands?
    /manuadd => add user to group
    /manudel => delete user from group, not implemented yet...
    /mangadd => add group, not implemented yet...
    /mangdel => delete group, not implemented yet...
    /manuaddp => add permission to user
    /manudelp => delete permission from user
    /mangaddp => add permission to group
    /mangdelp => delete permission from group

    How about some changes in commands too that make a little more sense too?
    /overload => /tempadd
    /underload => /tempdel
    /listoverload => /listtemp
    /mancommit => /mansave
    /manreload => /manrel
    /mancommit + /manreload => /manapply

    :D
     
  12. Offline

    WMisiedjan

    Somehow I get errors with Essentials plugins:
    Code:
    SEVERE: Could not pass event PLAYER_JOIN to Essentials
    java.lang.NoClassDefFoundError: Lcom/nijiko/Misc;
            at java.lang.Class.getDeclaredFields0(Native Method)
            at java.lang.Class.privateGetDeclaredFields(Unknown Source)
            at java.lang.Class.getField0(Unknown Source)
            at java.lang.Class.getField(Unknown Source)
            at com.earth2me.essentials.Essentials.isPlayerAuthorized(Essentials.java
    :112)
            at com.earth2me.essentials.EssentialsPlayerListener.onPlayerJoin(Essenti
    alsPlayerListener.java:136)
            at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.ja
    va:124)
            at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.jav
    a:60)
            at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.j
    ava:214)
            at net.minecraft.server.ServerConfigurationManager.a(ServerConfiguration
    Manager.java:88)
            at net.minecraft.server.NetLoginHandler.b(NetLoginHandler.java:86)
    
    And
    Code:
    2011-02-19 11:32:32 [INFO] [PLAYER_COMMAND] WMisiedjan: /help
    java.lang.NoClassDefFoundError: Lcom/nijiko/Misc;
            at java.lang.Class.getDeclaredFields0(Native Method)
            at java.lang.Class.privateGetDeclaredFields(Unknown Source)
            at java.lang.Class.getField0(Unknown Source)
            at java.lang.Class.getField(Unknown Source)
            at com.earth2me.essentials.Essentials.isPlayerAuthorized(Essentials.java
    :112)
            at com.earth2me.essentials.Essentials.isPlayerAuthorized(Essentials.java
    :97)
            at com.earth2me.essentials.help.EssentialsHelpWorker.onCommand(Essential
    sHelpWorker.java:22)
            at com.earth2me.essentials.help.EssentialsHelp.onCommand(EssentialsHelp.
    java:51)
            at org.bukkit.command.PluginCommand.execute(PluginCommand.java:17)
    
    I think it somehow cannot find Permissions?
     
  13. Offline

    Deatlev

     
  14. Offline

    Wulfspider

    Right now you have to make groups manually in the data.yml file. Just copy another group from the name to the end of the info line.

    Example:

    VIP:
    default: false
    permissions: [essentials.tp, tpack.*]
    inheritance: [Member]
    info: {prefix: '', build: true, suffix: ''}


    Mine may look different than yours... but that should give you the idea of where to start and stop.

    All you have to do to add a user to a group is use the command:
    /mangroup playername groupname
    Example: /mangroup Deatlev Admins
    After you do that, you use /mancommit and /manreload to apply the changes and reload the permissions.
    You can enter that in the server console. Same would apply for other groups.
     
  15. Offline

    WMisiedjan

  16. Offline

    Deatlev

    Ok i got myself on admin group
    and it works
    everything on tpack works...EXEPT Cuboid :( it says item dosent exist when i try
    and the item.txt list is whre it sohuld be i thin..in plugins folder, and the items i try with ARE in there so i dunno why it dosent work

    BTW thanks for such fast answers ;D highly appreciated
    Edit: doesnt work...still tried to move it...bah..
     
  17. Offline

    Wulfspider

    So you are using a form of permissions... ;) Try deleting the data.yml you customized, and use the default example and see if the error is still there. If so, then just edit your data.yml carefully with a basic text editor or use a program that parses like Anjo said such as Netbeans.

    You need a wood shovel equipped ;)
     
  18. Offline

    WMisiedjan

    This is what happened: I deleted data.yml and Essentials worked. I closed the server. Copied the orginal example data.yml and Essentials didn't work. (Got errors and everything as mentioned before.)
     
  19. Offline

    Deatlev

    i got a wood shovel.... but it says item dosent exist when i do /cfill [itemid]
     
  20. Offline

    Jandalf

    nice plugin, seems to be really helpfull, but i dont get it to work. everytime i make a change in the data.yml the changes were reseted after a serverrestart... i cant make groups or make me a higher rank in the file...
     
  21. Offline

    Deatlev

    Ok my server is fked up, /give dosent work it says item not found or item dosnt exist and i want colored names, like...[admin] Deatlev in green
     
  22. Offline

    Duendek86

    I have just say that at permissions thread, I you do first I'll give you a try in my server :)
     
  23. Offline

    Yogoda

    Just want to say I'm using it and it works perfectly :) love it !

    It was hard at first because a lot of my players were in non existing groups, so the plugin was making java errors and not loading. You could display a warning instead when a group does not exist, I think a lot of ppl might have problems with that.
     
  24. Offline

    SAMDAN

    Excuse me, but I disagree w/ the "no way to edit it w/out touching files." What about the /modgrp command.
    This seems to work fine, although I think it is w/ essentials.
     
  25. Offline

    nerdnosyd

    Thank you thank you thank you thank you thank you thank you THANK YOU! I've just cut down on server reboots by at least 50% now that I can modify my permissions on the fly and test stuff.
     
  26. Offline

    xZise

    Hello, for some reason following file works with Permissions but not with GroupManager:
    Code:
    # Supports "Default" and "GroupUsers"
    plugin:
        permissions:
            system: default
    
    groups: 
        Default: 
            default: true 
            info: 
                prefix:  
                suffix: 
                build: false 
            inheritance:  
            permissions: 
                - 'essentials.spawn' 
                - 'essentials.compass' 
                - 'warp.to.own' 
                - 'warp.to.invited' 
                - 'warp.to.global' 
        Prisoner: 
            default: false
            info: 
                prefix: '&0' 
                suffix: 
                build: false 
            inheritance: 
            permissions: 
    users: 
        xZise: 
            group: Default 
            permissions: 
                - 'permissions.reload' 
                - 'warp.sign.other'
    If I remove the “Prisoner” Node it works. It's not fatal (because I don't need the group), but maybe this could cause other bugs.
    The console output:
    Code:
    java.lang.ClassCastException: [Ljava.lang.String; cannot be cast to java.util.List
            at org.anjocaido.groupmanager.DataHolder.load(DataHolder.java:296)
            at org.anjocaido.groupmanager.GroupManager.<init>(GroupManager.java:90)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
            at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:77)
            at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:117)
            at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:82)
            at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:53)
            at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:171)
            at net.minecraft.server.MinecraftServer.c(MinecraftServer.java:158)
            at net.minecraft.server.MinecraftServer.d(MinecraftServer.java:110)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:209)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:512)
    19.02.2011 16:55:17 org.anjocaido.groupmanager.GroupManager <init>
    SCHWERWIEGEND: null
    java.lang.Exception: Your Permissions config file is invalid.  See console for details.
            at org.anjocaido.groupmanager.DataHolder.load(DataHolder.java:333)
            at org.anjocaido.groupmanager.GroupManager.<init>(GroupManager.java:90)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
            at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:77)
            at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:117)
            at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:82)
            at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:53)
            at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:171)
            at net.minecraft.server.MinecraftServer.c(MinecraftServer.java:158)
            at net.minecraft.server.MinecraftServer.d(MinecraftServer.java:110)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:209)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:512)
    19.02.2011 16:55:17 org.bukkit.plugin.SimplePluginManager loadPlugins
    SCHWERWIEGEND: Could not load plugins/GroupManager.jar in plugins: null
    org.bukkit.plugin.InvalidPluginException
            at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:79)
            at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:117)
            at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:82)
            at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:53)
            at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:171)
            at net.minecraft.server.MinecraftServer.c(MinecraftServer.java:158)
            at net.minecraft.server.MinecraftServer.d(MinecraftServer.java:110)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:209)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:512)
    Caused by: java.lang.reflect.InvocationTargetException
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
            at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:77)
            ... 8 more
    Caused by: java.lang.IllegalArgumentException: Permissions file is in wrong format
            at org.anjocaido.groupmanager.GroupManager.<init>(GroupManager.java:94)
            ... 13 more
    Fabian
     
  27. Offline

    captainbinary

    I have a problem, whenever i edit my config.yml file manually or when server is closed, to say add [admin] to the prefix so it shows with hero chat, it automatically converts the file back to the way it was on last run. What am i doing wrong?

    I am using windows 7 64bit, Groupmanager v0.6c, CB 335
     
  28. Offline

    AnjoCaido

    It seems your Essentials version is trying to use a different object inside the Permissions plugin, to do something.
    I didn't port the class Misc, as it was not documented by Nijikokun. Most plugins doesn't need anything morhe than the Permissions handler.
    I'm going to take a look at it.
    --- merged: Feb 19, 2011 8:09 PM ---
    Are you editing data.yml in GroupManager folder? if yes:
    Send your data.yml with your prefix as you like. Let me take a look at it.
    --- merged: Feb 19, 2011 8:17 PM ---
    Oops... sorry... that's a bug...

    Fixed it. Wait for next version, coming shortly.
    --- merged: Feb 19, 2011 8:19 PM ---
    You say that because you don't know how /modgrp works.

    It modify the file. Everything you do with it is saved. And then it calls permission plugin to reload the file.
    --- merged: Feb 19, 2011 8:23 PM ---
    Are you editing data.yml on GroupManager folder?
    --- merged: Feb 19, 2011 8:25 PM ---
    It would be very nice. But for the next days I want it completely compatible with Permissions.

    But I have some ideas of how do that.
     
  29. Offline

    SAMDAN

    Bla bla bla. It modifys the file, but he said manually modify it. I'm not a retard.
     
  30. Offline

    Jandalf

    yes, i found my problem, i copy the groupmanagerfolder in the pluginfolder and then started the server, so that GM cant copy the permissions data file. now i delete the GM folder start the server again and everything works:)
     
  31. Offline

    Ratarn

    hi. i want to forbid new players to build.
    so i though that the flag "build: false" is to set this. But new players can still build/destroy anything.
    Group definition:
    Code:
      Default:
        default: true
        permissions: [general.spawn]
        inheritance: []
        info: {prefix: '&7[Gast]', build: false, suffix: ''}
    Is there an fix, or do i have to use an other plugin to forbid build?
     
Thread Status:
Not open for further replies.

Share This Page