Commander

Overview

Commander is a powerful device interface tool used to assign commands, messages and statements to buttons, levers and pressure plates.

How to use

Firstly, make sure you have VAULT installed, as well as any of the permissions plugins it can handle (such as PermissionsEx or bPermissions). This allows permissions detection for all permissions-based systems specified on the Vault page.

Supported Devices

As of right now, only four devices are supported and listed below. Wooden Button will be easy to implement when 1.4 is released. I am currently in progress of developing a tripwire interface system for Commander:

Wooden Pressure Plate, Stone Pressure Plate, Stone Button, Wooden Button, Lever

Command Types

Command Types specify how the command will be run:

Player, Op, Console

You may also use p, o or c
Note: it is impossible for non-ops to op themselves using the op command type, as after all commands have been initiated, it de-ops the player. It is possible on a console command type however.

Commands

An explanation of how these commands work is shown when you type the command in-game:

References

References add a very powerful aspect to the uses of commander. References allow you to display specific traits of the player or the server to the player. References can also be used in messages and statements:

Conditional references

With commander, you can force the command to continue on to the next command or stop running any further commands. This is useful when adding conditional statements on devices:

An useful example of this is:

@in admin>@@You are an admin>@return
/give @player 57 1

This will check if the player is an admin – if they are in the admin group, it sends a message to them saying "You are an admin" and then gives them one diamond block. if they are not in the admin group, @return sop any other commands from running.

A little note about conditional references

Commands in conditional references are run the same as any other commands – if you specify it to be run as the player, op or console, it will run them as the player, op or console.

Messaging

This plugin would be pretty useless if it didn't have a method to send custom messages to a player's chat screen. All color code formats are supported:

Statements

Statements allow you to run a command if a condition has been met, else optionally run an alternate command. This is useful if you want players with a specific permissions node, group or item to run a command:

Manually editing devices

Device data is saved to Commander/devices.yml by default. if you are using an earlier version of Commander, simply rename "commands.yml" to "devices.yml":

Editing devices manually is useful when you have created an empty interface and wish to manually add your own commands to the device. This is also useful when you wish to add commands that cannot be entered into minecraft by default, such as long WorldEdit generation commands.

By defaults, commands in the devices.yml file do not contain a forward slash (/). If you want to add a command, simply write it out without the forward slash. With WorldEdit commands, you need to add one forward slash (instead of two):

Permissions

Further Ideas

• I plan to convert all references into statements:

@player Bob>@@You are bob!>@@You are not bob!

@health 20>/give @player 57 1>@@You are not at full health

• Tripwire support
• I have LOOKED INTO adding commands to any block.

Homepage: dragonphase.com

ba55ment: ba55ment.org

Похожие моды

Captain Thunder Addon Switchable Inventories RealTime JoinLeaveMsg ColoursList OreUpgrader ColorTab SecureLogin