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

    AnjoCaido

    Yeah, that's pretty much it.
    Just like big'ol Permissions.


    But the idea is great...
    you might want moderators to have all spells except lavaspam.... so u do
    Spells.*
    [email protected]

    Or something like that.
     
  3. Offline

    RustyDagger

    Where in that post did i say that you cant use the * I never did FFS You ppl cant read I said that i cant use it the way that i like to AND NO Not every admin Group Uses '*' Mine sure as hell don't cause of plugins like this that have so many commands that i simply would never use.

    what i was trying to say is that all the nodes for the commands for this plugin need to be nested deeper and not just all under the plugin name so that i COULD USE 'pluginname.group.*'

    So Please read what i said again i never said you cant use the * I implied that the plugin made it hard that is all.

    And to the guy that said don't like it don't use it i already said i was not going to use it but apparently no1 can read that either.
     
  4. Offline

    captainbinary

    RustyDagger you obviously need to blow of some steam, but please dont point your anger towards the community. Its not a very nice thing to do, what if you was on the receiving end?
     
  5. Offline

    Zenexer

    @Nijikokun You lost your chance. GroupManager is already in Essentials: it has the publicity that it needs to replace Permissions. You were unwilling to release Permisisons under and open source license, and your support for your plugins is lacking. I suggest you lose your bullying attitude, because you are in no position to behave as arrogantly as you do.

    @AnjoCaido I'd love to talk to you on IRC if you happen to stop by.
     
  6. Offline

    phaed

    I actually named my permissions config.yml to asdata.yml
     
  7. Offline

    kovk

    I support this plugin - though it stripped out all my nice comments and collapsed all group perms down to a single line.

    I must say while I have a lot of respect for Nijikokuns work I am seeking replacements for all of it since he holds back releases and updates to the community for reasons which don't seem fully explained.
     
  8. Offline

    Nijikokun

    I care not about you zenexer.
     
  9. Offline

    ddoolin

    Agreed. Not to mention virtually no support.
     
    Spazmic likes this.
  10. Offline

    Jaga

    Claim I spout nonsense in your own thread, and then come dis the post I mentioned? /boggle

    Not going to derail this topic however - I think what AnjoCaido is doing is great work, and am glad to see it being accepted in other modder's work. [​IMG]
     
  11. Offline

    McLrn227

    It's a shame to see a plugin dev act like a child when we're all just trying to have fun.
     
  12. Offline

    PandaVidya

    so wait... im confused... is it better to use group manager or permissions?
     
  13. Offline

    Fireside

    It would be better if you went and did some more reading, so you can understand whats going on...
     
    brosef likes this.
  14. Offline

    PandaVidya

    I've been reading around but i dont get it :/ I'm not a fan of drama. I just want to play minecraft.
     
  15. Offline

    Junubee

    People are fighting for position of who runs the better user rights plug-in @PandaVidya. Quite frankly it's a little silly.

    As of right now Permissions has the most compatibility, and if you don't read the forum that's pretty much all you need to know. If you do, it apparently leaves a sour taste in your mouth.

    Edit: That said, once this plug-in is updated it basically does the same thing, even allowing compatibility with plug-ins that use Permissions exclusively. Everything's good that way.
     
    Direct1221 and Fireside like this.
  16. Offline

    Direct1221

    Gotta remember dude, Not all of us read everything new one here :p
    Just us special few :)

    User preference between the two. I prefer Permissions (Please don't flame my post for this) & I am sure there are many others that prefer GroupManager. Just grab one & try it out.
     
  17. Offline

    Blackstorm72

    I've tried both, they essentially do the same thing for me on the server.
    There's some small differences, but to me running a private server with <10 people, it doesn't really make much of a difference. I don't understand the fighting, nor do I much care - both are great plugins - This community has always been great, I don't see why there is anyway.
     
  18. Offline

    ddoolin

    This utilizes the same system as Permissions, creating a fake "Permissions" then applying it different, giving you GroupManager. It's Permissions with loads more functionality.
     
    Junubee likes this.
  19. Offline

    Fireside

    Sorry ppls, that did come out harshly.. Could be the vibe in here today... :S I understand theres a lot of reading to do. But it really is worth it to undestand one's options.

    Great reply Janubee. touche.. :)
     
  20. Offline

    McLrn227

    And the Permissions dev doesn't like that and is throwing a hissy fit about it.
    /simplification of the situation, for everyone
     
    Synicyde likes this.
  21. Offline

    Direct1221

    I completely agree. By that, I mean I agree the reading is totally worth it AND I agree Janubee's reply was an amazing one.
     
  22. Offline

    Synicyde

    I wanna add mass amounts of permissions at once but idk if its 'command.command','next.command' or derp.derp,command.next
     
  23. Offline

    Connor Griffin

    Wow I feel so stupid right now. I've been trying forever to get this working, and then I saw that this isn't yet supported for builds greater than 405. When it is updated, I would like to start using it, and seeing if it works. The easiest way to do that is to make sure my current configuration file will work. If I missed anything, please let me know.

    Permissions JAR and Folder: Deleted (renamed)
    Fake Permissions and GroupManager: Uploaded
    data.yml: Configued (see below)
    Code:
    plugin:
        permissions:
            system: groupusers
    
    groups:
        Default:
            default: true
            info:
                prefix: &7
                suffix: &f
                build: false
            inheritance:
            permissions:
                - 'essentials.compass'
                - 'essentials.depth'
                - 'essentials.ping'
                - 'essentials.spawn'
                - 'essentials.list'
                - 'essentials.home'
                - 'essentials.sethome'
                - 'essentials.mail'
                - 'essentials.whois'
                - 'essentials.getpos'
                - 'essentials.afk'
                - 'essentials.msg'
                - 'essentials.mail.send'
                - 'mcdocs.*'
        Builder:
            default: false
            info:
                prefix: &b
                suffix: &f
                build: true
            inheritance:
                - Default
            permissions:
                - 'essentials.warp'
                - 'lwc.protect'
                - '/stack'
                - 'essentials.portal'
                - 'tombstone.use'
                - 'tombstone.largetombstone.lwc'
                - 'tombstone.sign'
                - 'tombstone.freesign'
                - 'multiverse.tp'
                - 'multiverse.world.list'
                - 'multiverse.world.spawn'
                - 'multiverse.portal.list'
                - 'essentials.world'
                - 'warpz0r.warp'
                - 'warpz0r.list'
                - 'warpz0r.home'
                - 'warpz0r.sethome'
        Mod:
            default: false
            info:
                prefix: &4
                suffix: &f
                build: true
            inheritance:
                - Builder
            permissions:
                - 'essentials.time'
                - 'essentials.unban'
                - 'essentials.top'
                - 'essentials.tree'
                - 'essentials.bigtree'
                - 'essentials.give'
                - 'essentials.item'
                - 'essentials.tppos'
                - 'essentials.kickall'
                - 'essentials.setwarp'
                - 'lwc.mod'
                - '/god'
                - '/godother'
                - '/heal'
                - '/healother'
                - '/slay'
                - '/whitelist'
                - 'essentials.jump'
                - 'essentials.back'
                - 'essentials.broadcast'
                - 'essentials.delwarp'
                - 'tombstone.freechest'
                - 'essentials.nick'
                - 'essentials.modgrp'
                - 'warpz0r.set'
                - 'warpz0r.warpto'
                - 'warpz0r.remove'
        Admin:
            default: false
            info:
                prefix: &6
                suffix: &f
                build: true
            inheritance:
                - Mod
            permissions:
                - '*'
    
    users:
        anAdmin:
            group: Admin
            permissions:
        aBuilder:
            group: Builder
            permissions:
        aMod:
            group: Mod
            permissions:
     
  24. Offline

    AnjoCaido

    Next build will come in 10 hours. I plan to add Permissions 2.1 too. Stay tunned. Now I need to sleep.

    Prefix and suffix uses ' ' to wrap those characters


    File corrected
    Code:
    plugin:
        permissions:
            system: groupusers
    
    groups:
        Default:
            default: true
            info:
                prefix: '&7'
                suffix: '&f'
                build: false
            inheritance:
            permissions:
                - 'essentials.compass'
                - 'essentials.depth'
                - 'essentials.ping'
                - 'essentials.spawn'
                - 'essentials.list'
                - 'essentials.home'
                - 'essentials.sethome'
                - 'essentials.mail'
                - 'essentials.whois'
                - 'essentials.getpos'
                - 'essentials.afk'
                - 'essentials.msg'
                - 'essentials.mail.send'
                - 'mcdocs.*'
        Builder:
            default: false
            info:
                prefix: '&b'
                suffix: '&f'
                build: true
            inheritance:
                - Default
            permissions:
                - 'essentials.warp'
                - 'lwc.protect'
                - '/stack'
                - 'essentials.portal'
                - 'tombstone.use'
                - 'tombstone.largetombstone.lwc'
                - 'tombstone.sign'
                - 'tombstone.freesign'
                - 'multiverse.tp'
                - 'multiverse.world.list'
                - 'multiverse.world.spawn'
                - 'multiverse.portal.list'
                - 'essentials.world'
                - 'warpz0r.warp'
                - 'warpz0r.list'
                - 'warpz0r.home'
                - 'warpz0r.sethome'
        Mod:
            default: false
            info:
                prefix: &4
                suffix: &f
                build: true
            inheritance:
                - Builder
            permissions:
                - 'essentials.time'
                - 'essentials.unban'
                - 'essentials.top'
                - 'essentials.tree'
                - 'essentials.bigtree'
                - 'essentials.give'
                - 'essentials.item'
                - 'essentials.tppos'
                - 'essentials.kickall'
                - 'essentials.setwarp'
                - 'lwc.mod'
                - '/god'
                - '/godother'
                - '/heal'
                - '/healother'
                - '/slay'
                - '/whitelist'
                - 'essentials.jump'
                - 'essentials.back'
                - 'essentials.broadcast'
                - 'essentials.delwarp'
                - 'tombstone.freechest'
                - 'essentials.nick'
                - 'essentials.modgrp'
                - 'warpz0r.set'
                - 'warpz0r.warpto'
                - 'warpz0r.remove'
        Admin:
            default: false
            info:
                prefix: '&6'
                suffix: '&f'
                build: true
            inheritance:
                - Mod
            permissions:
                - '*'
    
    users:
        anAdmin:
            group: Admin
            permissions:
        aBuilder:
            group: Builder
            permissions:
        aMod:
            group: Mod
            permissions:
     
    Jaga likes this.
  25. Offline

    Connor Griffin

    Okay, thanks. I am not too worried about the release timeframe of the next build. Our server is still in the setup and testing phase, so no outside players are in it yet. We are using the older permissions, so everybody has every command for now. Using Permissions 2.1 just removes permissions for all plugins from nearly everybody (except ops, I think). The main reason for the post you quoted was to ask if my syntax was all correct, so could you please examine it closely and let me know? Thanks and good luck with your plugin. It seems like you put a whole lot of work into it.
     
  26. Offline

    ddoolin

    My permissions seem to work with b424...just saying. At least better than on b420.
     
  27. Offline

    MonsterTV

    So here is a problem, I update to 423 today, and realized that Permissions has turned ALL players into Admins. I double checked my file, and it is configured correctly. In that thread, it is a known bug, so I figured I'd try GroupManager, and I'm still getting the same problem. Is this a known bug here too?
     
  28. Offline

    AnjoCaido

    It's not GroupManager. It's your CB #423, which think everyone is OP.


    This version is fully working with #424.


    ---
    NOTE:Latest Dev builds of Essentials are somehow caching the permissions. So if you change groups during game, it doesn't work for Essential's commands.
    Remember, GroupManager is 100% working. Tested all commands and they are very well affected by group/permission changes.
    --- merged: Feb 23, 2011 9:26 AM ---
    Version 0.9c is out.

    Fixed multiple inheritance.
    Now there is a command to toggle auto-save.

    So it's possible to go and edit the file manually without risk of losing data, while you come back to game, to use /manload
     
  29. Offline

    PeterPAwN

    Tested with #424, works absolutly fine for me.
     
  30. Offline

    AnjoCaido

    0.9d released.

    Found out that the problem with Essentials wasn't Essentials. But FakePermissions was acting unexpected on this new CB(I think plugin verification on the pluginLoader is damaged)

    Should work fine with latest Essentials now.


    ---
    Oh, and forgot to say...
    Now that plugin verification is damaged. There was no reason to keep the verification I had on Constructor(I used to make sure GroupManager would run before the other plugins that call it wrong way). Thinking of that, FakePermissions finally took of the Long Contructor.
    But some plugins that doesn't do right might fail, again.
     
  31. Offline

    uncovery

    This looks really interesting. I have a question:

    I am assigning people to groups if they fill in a questionnaire. With the permissions plugin, I edited the permissions config file and gave people the right to reload the permissions manually in game to activate the changes.

    How would something like this work with your plugin?

    thanks!
     
Thread Status:
Not open for further replies.

Share This Page