1) If there should be any problems, check your 'permissions.yml' here or here (German instructions)Ĭopy the content of the file and paste it into the left box.Here is a complete "permissions.yml" you can optimize for your needs: More information are available at the offical PermissionsEx Wiki. If there should be any errors or permissions not working, control your permissions.yml here. Using inheritance, you need to add a line called "inheritance:"Īnd the command to set ranks: /pex promote Ĭongratulations!, you have completed this tutorial and you're able to cope with PermissionsExsowie and also to configure it! This can be achieved with a new line called "inheritance": "Miner" is created, this group can inherit all permissions of the "Player" group. To set a prefix we use: /pex group prefix "&4" is a color code, other color codes can be found here:Ĭolor codes always look like "&" + number/letter without "#". Now all players in group "Admin" have a red prefix. Should a group be allowed to execute all but one command, you can keep the '- *' permissions and add a permissions with an extra '-'. To do this for a specific world only: /pex group add The permissions.yml file should look like: To add modifyworld.* to the group "Player" we execute the following command: Other groups can have a "default: false", but this is not necessary. To set a group as default, so that every new player joins this group, you have to add "default: true" to this group. Set a player's group: /pex user group set The default group (Player) should not get admin permissions (- '*'). This overrides PEX's permissions! Players entered into ops.txt have complete access to all commands! Insert the following into 'permissions.yml'ĬAUTION: Only the server admin should be entered into the ops.txt (located in the root directory). Using the following you grant the group "Admin" all permissions ("*"):Įditing the permissions.yml located in the PermissionsEx folder: To create a group open the console and type: This can be achieved using the console or by editing the "permissions.yml" file. The next step is to configure the "permissions.yml"Īt first, we create a group called "Admin", which gets all permissions to administrate the server. Activate ChatManager if installed by setting "enable: true" in plugins/ChatManager/config.yml.After creation of, Permissions.yml, you can edit the file with Notepad or Notepad ++.After starting your server with PEX it will create a folder called ,PermissionsEx containing the "permissions.yml" and "config.yml" file.Only use the "permissions.yml" in the 'PermissionsEx' folder! Make sure, PermissionsEX (PEX) is the only Permissions-Plugin running! PermissionsEx (PEX) creates all needed config-files automatically on it's first start. (Or you can use other chat plugins like herochat or mchat) Using ChatManager.jar, if you want to use "&-color codes".Using Modifyworld.jar, to restrict building/destroying blocks and much more.
Click on "Plugins" under 'Minecraft - Bukkit' (left sidebar).ġ) via a FTP browser like Filezilla by upload the 'PermissionsEx.jar' file into the ,plugins folderĢ) via the Nitrado Webinterface under ,Bukkit Plugins The newest PermissionsEx version can be found here.
Supports default settings like displaying prefix, suffix and colors. Chat-Manager - useful Chat-Plugin, coming with PEX.Performance friendly - Low-Level-Caching helps a lot when you have 100+ players online (decreases sever load).Easy migration from Permissions 2.x! Converter for YAML and SQL using PermissionsCompat.Multi world permissions - global permissions.You can control inheritance and players' prefix/suffix.Allow or deny destroying blocks, riding a boat or not getting attacked by monsters. Complete control over what players can do (Modifyworld).There is no need to edit the files manually. You can even control PEX via ingame commands. PEX creates the DB-scheme (tables and first entries) automatically.
0 kommentar(er)
