The 2nd line gives the group name, this should be ':'.Look at the indentation closely, YAML is very strict that this is correct and will error if it is wrong.This example has a couple of notable characteristics worth pointing out and is quite useful for most servers: The basics of group manager can be summed up by the example shown here: The example config file is a little too big to post here, but it will be automatically generated the first time you start GM. This is where you declare the groups for which you are going to be using. This is the main and most important config file. Located at: plugins/GroupManager/worlds//group.yml Hardcore will use the groups files from MainWorld but will have its own user file, and all other worlds will use the Hardcore user file and Mainworld groups file. Mainworld, and the MainWorld_nether will share a folder. Skylands and Skylands2 will share the Skylands folder. In this example you would be expected to maintain several sets of config files. # This will take you into some more complex GM Mirroring. # This is an example GroupManager Mirroring system. #Minecraft per user yml file tutorial how to#Here is an example of how to use mirroring in GM # - world6 (this would cause world6 to mirror both files from world5) # - groups (World4 would use the groups.yml from world2, but it's own users.yml) # - users (World3 would use the users.yml from world2, but it's own groups.yml) # world2: (World2 would have it's own set of user and groups files) # Each child world can be configured to mirror the 'groups', 'users' or both files from its parent. # the element 'all_unnamed_worlds' specifies all worlds that aren't listed, and automatically mirrors them to it's parent. # the same user/groups files as the parent. # subsequent elements 'world_nether' and 'world_the_end' are worlds which will use # The first element 'world' is the main worlds name, and is the parent world. # Worlds listed here have their settings mirrored in their children. # Acceptable entries are - ALL,CONFIG,FINE,FINER,FINEST,INFO,OFF,SEVERE,WARNING # Level of detail GroupManager will use when logging. # Number of hours to retain backups (plugins/GroupManager/backup) # How often GroupManager will save it's data back to groups.yml and users.yml # *** NOTE: Having this feature enabled can allow improper use of Command Blocks which may lead to undesireable permission changes. # true will cause GroupManager to attempt name matching by default. # Default setting for 'mantogglevalidate' # The user will be able to promote players to the same group or even above. #Minecraft per user yml file tutorial full## With this enabled anyone set as op has full permissions when managing GroupManager The config file will look something like this: It is used to copy the permissions from a single world across to others. This config file is used when you have multiple worlds. Located at: plugins/GroupManager/config.yml The directory structure when you first generate the config files will look something like this: The standard config is usually something which is very similar to the layout detailed on the main page, but you will need to edit the configuration at least a little before use, if nothing else than adding yourself as admin. The very first time you run GM it will generate some config files which you can then edit and maintain. #Minecraft per user yml file tutorial download#When you first download GM, you will generally only have a.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |