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

    Itssnowing

    @Donny Try using this? It's the Essentials version, but I imagine it's been updated to work with 600+
    Also, this.

    Hey people! Use the links up above and place them in your permissions folder to use GroupManager for 602+!
    They're stolen from Essentials :B
     
  3. Offline

    SeeD419

    You sir, answered my question.

    Thank you[diamond] I wish that was outlined more clearly in the OP...buuuut I guess you can't have your [cake] and eat it too...
     
  4. Offline

    diegokilla

    What if i don't have/want any essentials stuff... is that strictly groupmanagers, just built for essentials?
     
  5. Offline

    Itssnowing

    It's exactly the same as Groupmanager. There is no difference than the one you would download in this thread, other than that one's built for 602+.
    No Essentials added. Though it might give a name like Groupmanager essentials or something.
    (By my understanding.)
     
  6. Offline

    diegokilla

    TBH i have been running the old 1.0alpha5 with 617 with no errors... Debating on whether i should just update or hold off... hrrmmm.
     
  7. Offline

    Itssnowing

    To be honest, I haven't even tried the links I posted >.>
     
  8. Offline

    untergrundbiber

    When i use the say-command on the server-console its says:

    "You don't have permission" in red

    it's a groupmanger problem or what else?
     
  9. Offline

    Itssnowing

    Config files, please. Are you getting any errors? Not to say I'll be able to understand them, I'm used to Permissions errors.
     
  10. Offline

    OrtwinS

    Wait a minute, your saying 1.0 alpha 5 didnt break with 617 (or even better, 621)?
    I never get the weird errors some other people always seem to get so if anyone can confirm it works for them I'm sure it will work for me as well :D
     
  11. Offline

    fitofinsanity

    I'll confirm that it works with CB 640. I never get weird errors either, but I only run 5 plugins.
     
  12. Offline

    OrtwinS

    I run 22, but I'm going down to 8 to stick with my core needs for anti-grief and roleplay.
    I'll test it with 621, I'll let you know.

    EDIT:
    yay! alpha5 works perfectly on 621
    (I do not use 617 because WE and WG run at 621)
     
  13. Offline

    OneNonlyNova

    for me it's not working on 617 or 621 :(
     
  14. Offline

    devatrox

    I updated to the Essential Group Manager 1.0(alpha-5) on Bukkit 612 and since then the chatprefix in the configuration doesn't work. I only have color codes in it, but now it always shows the group a user belongs to like so "[Admins] devatrox" with all the names in red. No errors in the log.
    (edit) Nevermind, I have accidently installed Essentials Chat, so that's maybe where this is coming from.

    Also a question: If a user is in ops.txt, has this any effect on the permissions? Because I put myself in Moderator group for testing purposes but I still had all admin permissions like /item and Worldedit stuff. Or is that just a bug I didn't notice yet? Didn't have a chance to ask any other player to test this because we are pretty low on users at the moment (server not yet public).

    Here is the relevant part of my groups.yml
    Code:
      Moderator:
        default: false
        permissions:
        - essentials.tp
        - essentials.tphere
        - general.player-info
        - general.teleport
        - general.teleport.here
        - general.time
        - essentials.signs.*
        - essentials.setwarp
        - essentials.delwarp
        - essentials.kick
        - groupmanager.*
        - BetterShop.admin.*
        - worldguard.stopfire
        inheritance:
        - donator
        info:
          prefix: '&2'
          build: true
          suffix: ''
      Admins:
        default: false
        permissions:
        - '*'
        inheritance:
        - moderator
        info:
          prefix: '&3'
          build: true
          suffix: ''
     
  15. Offline

    Alphard

    It doesn't seems to be working with any plugin I have.
    Essentials Group Manager is loading, but the other plugins can't find it.
     
  16. Offline

    untergrundbiber

    Code:
    groups:
      Player:
        default: false
        permissions:
        - cleaner.clean
        - cleaner.clean.force
        - commandbook.kit.starter
        - heroicrebuke.list
        - iConomy.list
        - iConomy.payment
        - iConomy.rank
        - lwc.protect
        - mcbans.vote
        - mcbans.vote.kick
        - myhome.home.*
        - mywarp.warp.basic.warp
        - petition
        - PortableTorch.Allow
        - simpleshop.buy
        - simpleshop.buy.gift
        - simpleshop.sell
        - worldguard.locate
        - worldguard.stack
        - wormhole.simple.use
        inheritance:
        - gast
        info:
          prefix: ''
          build: true
          suffix: ''
      Gast:
        default: true
        permissions:
        - commandbook.motd
        - commandbook.msg
        - commandbook.rules
        - commandbook.say.*
        - commandbook.spawn
        - commandbook.whereami
        - commandbook.who
        - commandbook.whois
        inheritance: []
        info:
          prefix: '&8[Gast] '
          build: false
          suffix: ''
      OP:
        default: false
        permissions:
        - -worldedit.delchunks
        - -worldedit.scripting.*
        - -worldedit.snapshots.*
        - -worldedit.reload
        - cleaner.preview.*
        - commandbook.give.*
        - commandbook.kit.*
        - commandbook.teleport
        - commandbook.teleport.other
        - commandbook.time
        - commandbook.whois*
        - creativestick.*
        - falsebook.*
        - griefalertr.ignore
        - griefalertr.use
        - griefalertr.view
        - groupmanager.*
        - heroicrebuke.active
        - heroicrebuke.add
        - heroicrebuke.clear
        - heroicrebuke.info
        - heroicrebuke.list.others
        - iConomy.access
        - lwc.mod
        - magiccarpet.mc
        - mcbans.ban.global
        - mcbans.ban.local
        - mcbans.ban.temp
        - mcbans.ban.view
        - mcbans.kick
        - mcbans.lookup
        - mcbans.mod
        - mcbans.unban
        - myhome.*
        - mywarp.*
        - petition.*
        - SimpleAlias.*
        - simpleshop.items.*
        - worldedit.*
        - worldguard.allowfire
        - worldguard.god
        - worldguard.heal
        - worldguard.stopfire
        - wormhole.*
        inheritance:
        - player
        info:
          prefix: '&2[OP] '
          build: true
          suffix: ''
      Admin:
        default: false
        permissions:
        - '*'
        - griefalertr.ignore
        - griefalertr.use
        - griefalertr.view
        - lwc.admin
        - mcbans.admin
        inheritance: []
        info:
          prefix: '&c[Admin] '
          build: true
          suffix: ''
    
    

    I'm in the admin group, but i think that is indifferent for command direct on the server console,don't?
     
  17. Offline

    ArchTyriel

    Ah your problem is really easy to see.
    In the Admin group don't have any other permissions than " - '*' "
    That permission is default to having ALL permissions.
    Adding any permissions on top of that leads to unpredictable behavior.

    In a nutshell... Shit goes down.
     
  18. Offline

    untergrundbiber

    I try it, but its the same:

    Code:
    say Test
    15:28:54 [INFO] You don't have permission.
    
    admin-group:

    Code:
    Admin:
        default: false
        permissions:
        - '*'
        inheritance: []
        info:
          prefix: '&c[Admin] '
          build: true
          suffix: ''
    
     
  19. Offline

    spoothie

    I use Build 617
    Every time I restart my server (so that the GroupManager configs can reload), new GroupManager config files are created and the ones that i've uploaded are overwritten. Does sb have the same problem? What am i doing wrong?
    (Sry for my bad english...;) )
     
  20. Offline

    OneNonlyNova

    you have to shutdown change and then start server ;)
    groupmanager saves the backup on shutdown :)
     
  21. Offline

    Volitle

    Is there anyway from stopping my server from double tagging. for example at the moment it is

    [Moderator] Mod Playername

    but i want it back to normal where it was

    Mod Playername

    Im using groupmanager v1.0 alpha 5 with essentialschat
     
  22. Offline

    spoothie

    Thanks OneNonlyNova :)
    But Antibuild still doesn't work.
    Code:
      Default:
        default: true
        permissions:
        - essentials.rules
        inheritance: []
        info:
          prefix: '[Default] '
          build: false
          suffix: ''
    Anything wrong here?

    And yes, I've written "build: true" at the end of the config file of Normal Essentials (/plugins/Essentials/config.yml).
     
  23. Offline

    KAi_B

    when does it will be updated to Craftbukkit 617?
     
  24. Offline

    Matimba

    I have a few questions /requests:
    Is the github up to date?
    Could someone update the Java Doc with the classes?
    Is the WorldDataHolder no longer in the code?
    If so what mthod can i use instead of writeGroups() or writeUsers()?

    I hope someone can help me out with this because i feel unable to hook into GroupManager otherwise :/
     
  25. Offline

    Heinz Harald

    You have to stop your server first. Then upload your new config file. After uploading ist complete, you can start your server.
    Everytime your server starts, the plugin loads the config file into the cache. When you uploading on the running server you have to use the /manload command to load the new uploaded file into the cache. When missing this command, groupmanager will write the cached file over the uploaded.
     
  26. Offline

    Fausterion

    I just started using Bukkit recently, and I'm having major troubles with GroupManager and Permissions. No matter which plugin I run, my users seem to have full access to all commands. I'm self testing a server on my desktop by adding or removing myself from the admin group. I can see that at least part of the plugin recognizes that I'm in the admin group or not, as my name changes colour accordingly via the essentials plugin suite.

    I'm running a 1.4 server, using the latest craftbukkit which I got from here today http://wiki.bukkit.org/Setting_up_a_server .


    Code:
    groups:
      User:
        default: true
        permissions:
        - essentials.afk
        - essentials.helpop
        - essentials.list
        - essentials.mail
        - essentials.mail.send
        - essentials.me
        - essentials.motd
        - essentials.msg
        - essentials.rules
        - essentials.suicide
        - essentials.whois
        - lwc.protect
        - essentials.help
        inheritance: []
        info:
          prefix: ''
          build: true
          suffix: ''
      Moderator:
        default: false
        permissions:
        - essentials.ban
        - essentials.banip
        - essentials.broadcast
        - essentials.kick
        inheritance:
        - user
        info:
          prefix: '&2'
          build: true
          suffix: ''
      Admin:
        default: false
        permissions:
        - '*'
        inheritance: []
        info:
          prefix: '&c'
          build: true
          suffix: ''
    Code:
    users:
      Fausteriona:
        subgroups: []
        permissions: []
        group: Admin
      Wolz:
        subgroups: []
        permissions: []
        group: Admin
      McRiot:
        subgroups: []
        permissions: []
        group: Moderator
      D3siminated:
        subgroups: []
        permissions: []
        group: Moderator
    (you can see I added an a at the end of my name to throw me into the users group).

    I know that as a user, I have admin access as I can use commands like spawnmob and kick.

    So what am I doing wrong?
     
  27. Offline

    OneNonlyNova

    so you all are running 617 and have no problems with groupmanager?
     
  28. Offline

    spoothie

    Didn't you read the past 2 pages? xD
    In my case, Antibuild doesn't work with GroupManager... :(
     
  29. Offline

    axebyte

    I am on 621 and having no issues that i notice anyhow.
     
  30. Offline

    ultimak

    Im running it just fine without issues.
     
  31. Offline

    spoothie

    Does Antibuild work for your builds?
     
Thread Status:
Not open for further replies.

Share This Page