Knowledgebase >>>>Pre-made PermissionsEX File Here is a pre-made permissions file for PermissionsEX. It has several groups configured for you already, with increasing amount of permissions and capabilities. There are other groups configured for easy donation ranks, or whatever you like: • Guest This group is the default group for anyone joining the server for the first time. They can use common commands such as /tpa, /tpahere, /warp, /worth, etc.
I am having trouble with the powertool, I want my Mods to be able to use powertool and activate it. They can put commands on their item, but. General, nick, essentials.nick.others, Gives you permission to give other players a nick name. General, powertool, essentials.powertool, Allow access to the /powertool command. General, powertool, essentials.powertool.append, Allows adding multiple commands to a single powertool. General, powertooltoggle, essentials.
(See the permissions.yml file for a complete list.) • Member This group has a few more permissions, such as the ability to use a compass, workbench and multiple sethomes. (See the permissions.yml file for a complete list.) • Citizen This group keeps their experience on death and has access to a couple more kits.
(See the permissions.yml file for a complete list.) • Moderator The moderator group has quite a few typical permissions for your trusted Moderators. Windows 7 Extreme Edition 32 Bit Iso Download. They have enough power to mute, kick and jail people, but not enough to be able to abuse your players or server. • Elite This group has the ability to fly as well as repair all items and other abilities.
(See the permissions.yml file for a complete list.) • Admin The admin group has almost as many permissions and abilities as the co-owner and owner groups. Give this rank only to your most trusted staff. • Co-Owner The coowner group has almost all the permissions of the owner.
• Owner The owner group should have all the permissions needed to run and administer your server without having operator (op). This group shold be reserved for you and you alone. Just copy and paste over your existing file. You must install PermissionsEX first, then restart the server.
The permissions.yml file will appear in Multicraft under Files, Config Files.
PowerTool — Bind commands to items Originally requested by InflamedSebi. PowerTool allows you to bind commands to your in-hand items. Any item may be assigned commands for both left-click and right-click. Bound commands remain until you manually clear the binding. Please post bugs and/or feature requests as.
Features • Bound commands may include special tokens which are appropriately substituted when the item is used. Currently, these are: Token Description%p The name of the player you left-clicked or right-clicked. Chest Patch Lineage 2 Classes. %x X-coordinate of the block targeted by your crosshairs%y Y-coordinate of the block targeted by your crosshairs%z Z-coordinate of the block targeted by your crosshairs%Y Y-coordinate of the nearest air block above the block targeted by your crosshairs All of these tokens are configurable.
• Works in creative mode. Right-clicking and left-clicking players in creative mode will generally work, even when far away (up to 100 blocks). • Ability to define global power tools. These are administrator-defined binds that can be made available to whoever you want (based on permissions). • Fine-grained control over the use of power tools via permissions.
• Global power tools may grant temporary permissions or even be run as the console. Needless to say, these features should be used with care. • The number of player-created binds may be limited based on group/permission. • Items may be further differentiated by custom display name (e.g. When given one via Anvils). Note this option is off by default, enable it in the configuration file. Commands There's only one command, /powertool which may also be abbreviated /pt or /ptool: • /powertool left — Binds the command (and its arguments) to the left-click action of the current item.
The command must not include the first slash. This may also be abbreviated as /powertool l. • /powertool right — Binds the command (and its arguments) to the right-click action of the current item. This may also be abbreviated as /powertool r.
• /powertool left — With no command to bind, the currently-bound left-click command is cleared from the current item. Use /powertool right to clear the right-click command. • /powertool list — Displays all player-defined power tools for the current player. • /powertool clear — Clears all bound commands from the current item. • /powertool clear — Clears all bound commands from the specified item.
• /powertool clear -a — Clears all bound commands from all items. • /powertool on — Enable power tools for this session (default is on). • /powertool off — Disable power tools for this session. • /powertool toggle — Toggle power tools availability. Can also be abbreviated as /powertool t.
• /powertool reload — Re-reads config.yml. Permissions PowerTool only supports Bukkit permissions (aka Superperms). By default, ops have all permissions. • powertool.use — Allows the use and creation of power tools. (Has powertool.use.* and powertool.create as child permissions.) • powertool.use.* — Allows the use of all power tools. • powertool.use. — Allows the use of a specific power tool identified by item-id.
Item-id may be numeric (e.g. 322 for golden apple), or the with or without underscores (e.g.
GOLDEN_APPLE or GOLDENAPPLE). Note that Bukkit permissions are not case-sensitive, so both powertool.use.golden_apple and powertool.use.GOLDEN_APPLE work fine. • powertool.create — Allows the creation of personal power tools. A player must be given this permission in order to use the left/right/list/clear subcommands. • powertool.reload — Allows use of /powertool reload Additionally, per-group power tool limits may be defined using permissions. See the options section in config.yml for details.
Global, Administrator-defined Binds By editing config.yml, the server administrator can define binds for use by anyone with the powertool.use permission. For example: powertools: string: left-click: plugins right-click: version The item ID ('string' in the above example) may be an integer item ID or a name. If using an integer item ID, you must quote it as a string, e.g. '287' for 'string.' If using a name, you must use a standard Bukkit material name (). For example, for golden apples, you may use one of: • GOLDEN_APPLE • 'golden apple' (since it has a space, it must be quoted) • goldenapple Examples • Promote and demote users using the left-click and right-click actions of the current item: /powertool l promote%p /powertool r demote%p • Bind WorldEdit's copy & paste commands. Remember that many WorldEdit commands normally start with two slashes, but you must always omit the first slash.
/powertool left /copy /powertool right /paste License & Source PowerTool is released under the. Sources may be found on GitHub: • • Development builds of this project can be acquired at the provided continuous integration server. These builds have not been approved by the BukkitDev staff. Use them at your own risk. • (Requires ToHPluginUtils.jar) • (includes ToHPluginUtils, like the version distributed on dev.bukkit.org) To Do • Allow setting/clearing global power tools from the command line (for those with the proper permission, of course).
• Allow player-specific power tools to override global ones. • Allow global power tool flags (e.g.
Run-as-console) to be assigned to each individual action.