|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Contents
1. Overview
2. Abilities
3. Mine Carts
4. Misc.
5. Integrated Cicuits
6. Portals
7. Programs
8. Regions
9. Signs
Appendix E: Sample Configuration File ForceOne Essentials MineCraft Plugin is a collection of enhancements to MineCraft including portals, regions, mine cart updates, integrated circuits, abilities (flying, fire resistance, insta-break, insta-kill, water breathing, unlimited items), etc. Abilities give players the ability to do non-standard actions. • Drop chest upon death. • Fire resistance. • Flying with gold boots. • Insta-break. • Insta-kill. • No starvation. • Unlimited items. • Water breathing. Mine cart behavior modifications. • Booster track. • Destroy mine cart track. • Eject track. • Reverse track. • Slow track. • Stop track. • Ride signs. • Spawns mine cart when used. • Mine cart automatically destroyed when player exits. • Optionally charge player to user. Miscellaneous commands that do not fit under any other category. • "Get Info" mode. • Help information. • Permission list. • Player status. Integrated circuits perform complex logic in a small package replacing large areas of redstone circuitry. • Build integrated circuits in any shape. • Add/remove blocks to/from the integrated circuit dynamically. • "Get Info" mode integration. • Ownership. Portals teleport a play to another portal. • North/south/east/west/up/down facing portals. • Automatic portal construction/destruction. • Change orientation of portal. • Change destination of portal. • Multi-world support. • Portal ownership. Programs are used by integrated circuits to perform actions. • Full-featured programming language. • Assignment operators. • Boolean operators. • Bitwise operators. • Conversion operators. • Comparison operators. • Debug commands. • Flow control statements. • Math operators. • Stack support. • Call other programs. • Test programs. • Ownership. A region defines an area. • Toggle block placement/destruction protection. • Toggle PVP within region. • Toggle mob spawning within region. • Lock region for private access. • Region ownership. • Buy region signs. • Buying a region transfers ownership to player. • Requires economy. • Overlapped regions support. • Toggle invulnerability within region. • Region size limitation. • Protection bypass. • Region size bypass. • Region lock bypass. Signs perform an action when right-clicked or powered. • Colored signs. • Add colors to the text of your sign. • Repair signs. • Repair any item or certain types of items. • Optionally charge player to repair an item. • Time signs. • Change time to day or night. • Optionally charge player to change the time. • Weather signs. • Change the weather to sunny or stormy. • Optionally charge player to change the weather. • Wireless signs. • Send/receive the redstone power wirelessly. • Unlimited channels supported. • Each player has their own set of channels. • Wool color signs. • Change the color of wool when powered/unpowered. Permissions control who can use certains features in ForceOne Essentials. • Full permission support through PermissionsBukkit. • Permission support for users and ops in configuration file (ignored if permissions plugin is found). • Feature toggle in configuration file. Some features support charging a player per use. The following enconomy plugins are supported: • iConomy 4 • iConomy 5 • iConomy 6+ • BOSEconomy 6 • BOSEconomy 7 • Essentials Economy 2.2.17+ • MultiCurrency By downloading or installing the ForceOne Essentials MineCraft Plugin you agree to the terms set forth in the End User License Agreement (EULA). 1.2.1. END USER LICENSE AGREEMENT (EULA) END-USER LICENSE AGREEMENT FOR FORCEONE ESSENTIALS MINECRAFT PLUGIN. PLEASE READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT CAREFULLY BEFORE CONTINUING WITH THIS PROGRAM INSTALL. ForceOne Technologies' End-User License Agreement ("EULA") is a legal agreement between you (either an individual or a single entity) and ForceOne Technologies for the ForceOne Technologies software product(s) identified above which may include associated software components; media; printed materials; and "online" or electronic documentation ("SOFTWARE PRODUCT"). By installing, copying, or otherwise using the SOFTWARE PRODUCT you agree to be bound by the terms of this EULA. This license agreement represents the entire agreement concerning the program between you and ForceOne Technologies (referred to as "licenser") and it supersedes any prior proposal, representation, or understanding between the parties. If you do not agree to the terms of this EULA, do not install or use the SOFTWARE PRODUCT. The SOFTWARE PRODUCT is protected by copyright laws and international copyright treaties as well as other intellectual property laws and treaties. The SOFTWARE PRODUCT is licensed, not sold. 1. GRANT OF LICENSE. The SOFTWARE PRODUCT is licensed as follows: (a) Installation and Use. ForceOne Technologies grants you the right to install and use copies of the SOFTWARE PRODUCT on your computer running a validly licensed copy of the operating system for which the SOFTWARE PRODUCT was designed (e.g., Microsoft Windows Vista, Microsoft Windows 7, Microsoft Windows Server 2008, Linux, and OS-X). (b) Backup Copies. You may make copies of the SOFTWARE PRODUCT as may be necessary for backup and archival purposes. 2. DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS. (a) Maintenance of Copyright Notices. You must not remove or alter any copyright notices on any and all copies of the SOFTWARE PRODUCT. (b) Distribution. You may not distribute copies of the SOFTWARE PRODUCT to third parties. Evaluation versions available for download from ForceOne Technologies's websites may be freely distributed. (c) Prohibition on Reverse Engineering, Decompilation, and Disassembly. You may not reverse engineer, decompile, or disassemble the SOFTWARE PRODUCT except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation. (d) Rental. You may not rent, lease, or lend the SOFTWARE PRODUCT. (e) Support Services. ForceOne Technologies may provide you with support services related to the SOFTWARE PRODUCT ("Support Services"). Any supplemental software code provided to you as part of the Support Services shall be considered part of the SOFTWARE PRODUCT and subject to the terms and conditions of this EULA. (f) Compliance with Applicable Laws. You must comply with all applicable laws regarding use of the SOFTWARE PRODUCT. 3. TERMINATION Without prejudice to any other rights, ForceOne Technologies may terminate this EULA if you fail to comply with the terms and conditions of this EULA. In such event, you must destroy all copies of the SOFTWARE PRODUCT in your possession. 4. COPYRIGHT All title, including but not limited to copyrights, in and to the SOFTWARE PRODUCT and any copies thereof are owned by ForceOne Technologies or its suppliers. All title and intellectual property rights in and to the content which may be accessed through use of the SOFTWARE PRODUCT is the property of the respective content owner and may be protected by applicable copyright or other intellectual property laws and treaties. This EULA grants you no rights to use such content. All rights not expressly granted are reserved by ForceOne Technologies. 5. NO WARRANTIES ForceOne Technologies expressly disclaims any warranty for the SOFTWARE PRODUCT. The SOFTWARE PRODUCT is provided "AS IS" without any express or implied warranty of any kind, including but not limited to any warranties of merchantability, noninfringement, or fitness of a particular purpose. ForceOne Technologies does not warrant or assume responsibility for the accuracy or completeness of any information, text, graphics, links or other items contained within the SOFTWARE PRODUCT. ForceOne Technologies makes no warranties respecting any harm that may be caused by the transmission of a computer virus, worm, time bomb, logic bomb, or other such computer program. ForceOne Technologies further expressly disclaims any warranty or representation to Authorized Users or to any third party. 6. LIMITATION OF LIABILITY In no event shall ForceOne Technologies be liable for any damages (including, without limitation, lost profits, business interruption, or lost information) rising out of use of or inability to use the SOFTWARE PRODUCT even if ForceOne Technologies has been advised of the possibility of such damages. In no event will ForceOne Technologies be liable for loss of data or for indirect, special, incidental, consequential (including lost profit), or other damages based in contract, tort, or otherwise. ForceOne Technologies shall have no liability with respect to the content of the SOFTWARE PRODUCT or any part thereof including but not limited to errors or omissions contained therein; libel; infringements of rights of publicity; privacy; trademark rights; business interruption; personal injury; loss of privacy; moral rights; or the disclosure of confidential information. ForceOne Essentials has the following prerequisites: • MineCraft 1.0.0 (http://www.MineCraft.net) • CraftBukkit 1.0.1-R1 (http://www.bukkit.org) • (optional) iConomy 4, 5, and 6+; BOSEconomy 6 and 7; Essentials Economy 2.2.17+; and MultiCurrency economy plugins Download the ForceOne Essentials package (MD5: 9e3ab7c5b42b809b96a13c50ec0ee193). By downloading the ForceOne Essentials MineCraft Plugin you agree to the terms set forth in the End User License Agreement (EULA). 1. Download the ForceOne Essentials package. 2. Unzip the ForceOne Essentials package into your plugins folder. 3. Modify the "ForceOneEssentials\config.yml" file. 4. Restart your MineCraft server. • None. MineCraft Essentials: • Time and weather signs: Disabling the ability to create time and weather signs in Mincraft Essentials or ForceOne Essentials should resolve this problem. • Elevators 1.5.1. VERSION 1.2.0 (2012-1-2) • ADDED: Drop chests ability. • ADDED: Repair signs. • FIXED: Unlimited items. • FIXED: Register.jar error messages. • FIXED: ForceOne Essentials using itself for economy. 1.5.2. VERSION 1.1.0 (2011-12-30) • ADDED: Portal support. • FIXED: Help text. 1.5.3. VERSION 1.0.1 (2011-12-24) • FIXED: Bedrock at lowest point of map can be broken using insta-break allowing player to fall through. • FIXED: Insta-kill sometimes requires two strikes. 1.5.4. VERSION 1.0.0 (2011-12-22) • ADDED: No starvation ability. • ADDED: Ability to disable features in config file. • FIXED: Resetting world cause ICs to throw exceptions. • MISC: Code clean up. 1.5.5. VERSION 0.1.0 (2011-5-23) • Initial release. If you have questions, suggestions, or issues with ForceOne Essentials you may contact us by e-mail by selecting "Contact Us" from the main menu. The drop chests ability makes a player drop a chest containing their inventory when the player dies. The chest is accessible by any player that uses it. The fire resistance ability makes a player immune to damage from both fire and lava. A player with the foe.fireresistance permission is granted this ability. The flying ability allows a player fly by wearing a pair of gold boots and holding down the sneak button. A player with the foe.flying permission is granted this ability. The insta-break ability allows a player to break any block with a single strike. A player with the foe.instabreak permission is granted this ability. The insta-kill ability allows a player to kill any mob with a single strike. A player with the foe.instakill permission is granted this ability. The no starvation ability prevents a player from starving to death. A player with the foe.nostarvation permission is granted this ability. The unlimited items ability allows a player to place an unlimited number of blocks regardless of the number contained in their inventory. If a player picks up an block or item that is already in their inventory that inventory item will not be incremented. A player with the foe.unlimiteditems permission is granted this ability. The water breathing ability prevents a player from drowning when the player runs out of air. A player with the foe.waterbreathing permission is granted this ability. The following commands are used with abilities: The fireresistance command toggles the player's fire resistance ability off and on. Syntax: /foe fireresistance Parameters: None. Permissions Required: The flying command toggles the player's flying ability off and on. Syntax: /foe flying Parameters: None. Permissions Required: The instabreak command toggles the player's insta-break ability off and on. Syntax: /foe instabreak Parameters: None. Permissions Required: The instakill command toggles the player's insta-kill ability off and on. Syntax: /foe instakill Parameters: None. Permissions Required: The nostarvation command toggles the player's no starvation ability off and on. Syntax: /foe nostarvation Parameters: None. Permissions Required: The unlimiteditems command toggles the player's unlimited items ability off and on. Syntax: /foe unlimiteditems Parameters: None. Permissions Required: The waterbreathing command toggles the player's water breathing ability off and on. Syntax: /foe waterbreathing Parameters: None. Permissions Required: Grants a player fire resistance and allows them to toggle fire resistance off and on. Grants a player the flying ability and allows them to toggle flying off and on. Grants a player the insta-break ability and allows them to toggle insta-break off and on. Grants a player the insta-kill ability and allows them to toggle insta-kill off and on. Grants a player no starvation and allows them to toggle starvation off and on. Grants a player unlimited items and allows them to toggle unlimited items off and on. Grants a player water breathing and allows them to toggle water breathing off and on. A booster track speeds up the mine cart to its top speed when it rolls over the booster track. Booster tracks are created by placing a rail block on top of a red wool block.
3.1.2. DESTROY MINE CART TRACK A destroy mine cart track destroys the mine cart when it rolls over the destroy mine cart track. Destroy mine cart tracks are created by placing a rail block on top of a black wool block.
An eject track ejects the rider when the mine cart rolls over the eject track. Eject tracks are created by placing a rail block on top of a gray wool block.
A reverse track reverses the direction of the mine cart when it rolls over the reverse track. Reverse tracks are created by placing a rail block on top of a dark green wool block.
A slow track slows the mine cart down when it rolls over the slow track. Slow tracks are created by placing a rail block on top of an orange wool block.
A stop track stops the mine cart when it rolls over the stop track. Stop tracks are created by placing a rail block on top of a light gray wool block.
The ride sign spawns a mine cart when used. The player using the sign is placed in the mine cart when it is spawned. A ride sign is created by placing a sign adjacent to a rail block or as a wall sign above a rail block. The first line of the sign must be "[Ride]". The next line, which is optional, may be the cost to ride. The third line, also optional, is the direction the spawned mine cart should travel when it is created. If no direction is specified, the sign must be placed at the terminus of the track. The first line of the sign will turn blue if it has been created successfully; otherwise it will turn red. Mine carts spawned by a ride side will automatically disappear when it no longer contains riders. The foe.signs.create.ride or foe.signs.ride.create permission is required to be able to create a ride sign. The foe.signs.use.ride or foe.signs.ride.use permission is required to be able to use a ride sign. Example:
The following permissions are used with mine carts: Allows a player to create a "Ride" sign. Allows a player to create a "Ride" sign. Allows a player to use a "Ride" sign. Allows a player to use a "Ride" sign. The debug command toggles "Debug" mode on and off. Syntax: /foe debug Parameters: None. Permissions Required: The getinfo command toggles "GetInfo" mode on and off. When "GetInfo" mode is on, a player may right-click on a block with a bone to see the block's coordinates, redstone power, input number (if the block is an input of an integrated circuit), and output number (if the block is an output of an integrated circuit). By default "GetInfo" mode is off. Syntax: /foe getinfo Parameters: None. Permissions Required: None. The help command displays the specified page of the list of available commands or the first page if no page is specified. Syntax: /foe help [page] Parameters: page -- The help page to display. Permissions Required: None. The permissions command displays the specified page of the list of permissions or the first page if no page is specified. Syntax: /foe permissions [page] Parameters: page -- The permissions page to display. Permissions Required: None. The status command displays the specified page of the player's status or the first page if no page is specified. Syntax: /foe status [page] Parameters: page -- The status page to display. Permissions Required: Allows a player to toggle additional debug information on or off. Grants a player the ability to view their status. Integrated circuits run a program whenever one of its inputs changes and changes the state of its outputs to reflect the output of the program. The following is an example of an integrated circuit with two inputs and one output. Integrated circuits consist of three parts: the body, the inputs, and the outputs.
The body of the integrated circuit is created using iron blocks. The blocks must be adjacent to, on top of, or below each other. There is no limit to the size and configuration of the iron blocks that make up the body. On one of the iron blocks a wall sign is placed. This sign has two lines. The first line is always "[IC]". This denotes that the sign represents an integrated circuit. The second line is the name of the program that is run when any of the inputs for the integrated circuit changes state. The first line of the sign will turn blue if it has been created successfully; otherwise it will turn red. The foe.signs.create.ic or foe.signs.ic.create permission is required to be able to create an IC sign. Example:
The inputs of an integrated circuit are created using gold blocks. A single gold block represents a single input. A gold block must be adjacent to, on top of, or below one of the iron blocks that make up the body of the integrated circuit. An input's state will change when the state of a redstone wire, button, lever, or pressure plate that is adjacent to it changes. The outputs of an integrated circuit are created using levers. A single lever represents a single output. A lever must be mounted on one of the iron blocks that make up the body of the integrated circuit. You may modify the integrated circuit at any time. When you add or remove blocks, the integrated circuit will automatically reconfigure itself. You may use the /foe getinfo command to get the information related to an input or an output. The input number or output number the cooresponds to the selected input or output will be displayed. The following permissions are used with integrated circuits: Allows a player to create an "IC" sign. Allows a player to create an "IC" sign. A portal allows you to instantly teleport from one portal to another. To create a portal use the /foe portal create command. The blocks for the portal will automatically be placed for you; any existing blocks will be destroyed. The opening of the portal will be facing in the direction specified. A portal's location is determined by the position of the player when the command is initiated. The following commands are used with portals: The create command creates a new portal at the current player location. Syntax: /foe portal create <name> <NORTH|SOUTH|EAST|WEST|UP|DOWN> [destination|NONE] Parameters: name -- The name of the portal. NORTH -- Create the portal with the opening facing north. SOUTH -- Create the portal with the opening facing south. EAST -- Create the portal with the opening facing east. WEST -- Create the portal with the opening facing west. UP -- Create the portal with the opening facing up. DOWN -- Create the portal with the opening facing down. destination -- The name of the destination portal. NONE -- Set the destination to nothing. Permissions Required: Example: /foe portal create MyPortal EAST YourPortal Creates a new portal named "MyPortal" facing east. The delete command deletes an existing portal. Syntax: /foe portal delete <name> Parameters: name -- The name of the portal. Permissions Required: foe.portal.delete or ownership Example: /foe portal delete MyPortal Deletes the portal named "MyPortal". 6.2.3. /FOE PORTAL DESTINATION The destination command changes the destination of an existing portal. Syntax: /foe portal destination <name> <destination|NONE> Parameters: name -- The name of the portal. destination -- The name of the destination portal. NONE -- Set the destination to nothing. Permissions Required: foe.portal.modify or ownership Example: /foe portal destination MyPortal YourPortal Sets the portal "MyPortal" to the destination "YourPortal". The help command displays the specified page of the list of available commands or the first page if no page is specified. Syntax: /foe portal help [page] Parameters: page -- The help page to display. Permissions Required: None. Example: /foe portal help 3 The list command displays a list of all the portals. Syntax: /foe portal list Parameters: None. Permissions Required: foe.portal.list or ownership Example: /foe portal list 6.2.6. /FOE PORTAL ORIENTATION The orientation command changes the orientation of an existing portal. Syntax: /foe portal orientation <name> <NORTH|SOUTH|EAST|WEST|UP|DOWN> Parameters: name -- The name of the portal. NORTH -- Create the portal with the opening facing north. SOUTH -- Create the portal with the opening facing south. EAST -- Create the portal with the opening facing east. WEST -- Create the portal with the opening facing west. UP -- Create the portal with the opening facing up. DOWN -- Create the portal with the opening facing down. Permissions Required: foe.portal.modify or ownership Example: /foe portal orientation MyPortal WEST Sets the orientation of the portal "MyPortal" to open to the west. The owner command sets the owner of the specified portal. Syntax: /foe portal owner <name> <player> Parameters: name -- The name of the portal. player -- The name of the player. Permissions Required: foe.portal.modify or ownership Example: /foe portal owner MyRegion JohnDoe The rename command renames the specified portal. Syntax: /foe portal zorder <name> <newname> Parameters: name -- The name of the portal. newname -- The new name of the portal. Permissions Required: foe.portal.modify or ownership Example: /foe portal rename MyRegion YourRegion The following permissions are used with portals: Allows a player to create a portal. Allows a player to delete a portal. Allows a player to list a portal. Allows a player to modify a portal. Programs execute a series of instructions using a set of supplied inputs generating a series of outputs. A program is structured as a series of lines of code. Each line contains one opcode. Lines are numbered starting at 0. Programs support 256 inputs. Each input contains a Boolean value that indicates the current state of the input. Inputs are numbered starting at 0. Inputs are shared when a program calls another program. Programs support 256 outputs. Each output contains a Boolean value that indicates the current state of the output. Outputs are numbered starting at 0. Outputs are shared when a program calls another program. Each program has 256 general purpose registers available. Each register may contain either a Boolean or Integer value. Registers are numbered starting at 0. Registers are not shared when a program calls another program. In addition to the general purpose registers, each program has an IFSTATE register. This register holds the result of the last boolean operation. Other operators may also read or modify the IFSTATE register directly. The IF operator reads the value IFSTATE register to determine whether or not to transfer control to the specified label. The IFSTATE register is not shared when a program calls another program. Each program has a stack available to it. The stack may hold both Boolean and Integer values. The stack is shared when a program calls another program. The operands are used in the syntax of the operators and indicate what operands may be used for a given operator. The syntax of an operand is expressed using regular expressions. The Ix operand specifies an input. Data Type: Boolean Syntax: I[0-9]+ The number specified must be a value between 0 and 255 inclusive. The Ox operand specifies an output. Data Type: Boolean Syntax: O[0-9]+ The number specified must be a value between 0 and 255 inclusive. The Rx operand specifies a register. Data Type: Boolean or Integer Syntax: R[0-9]+ The number specified must be a value between 0 and 255 inclusive. The IFSTATE operand specifies the IFSTATE register. Data Type: Boolean Syntax: IFSTATE The LABEL operand specifies a label. Data Type: String Syntax: [A-Za-z_][A-Za-z0-9_]{0,49} The BOOLEAN operand specifies a literal Boolean value. Data Type: Boolean Syntax: TRUE|FALSE|T|F The INTEGER operand specifies a literal Integer value. Data Type: Integer Syntax: -?[0-9]+ The value specified must be between -2,147,483,648 to 2,147,483,647 inclusive. The STRING operand specifies a literal String value. Data Type: String Syntax: .* An opcode is a single instruction that performs a task within a program. The following opcodes may be used in a program: The SET operator assigns the value specified by the second operand to the first operand. If the data type of second operand does not agree with the data type of the first operand an error will be thrown. Syntax: SET Rx|Ox|IFSTATE Ix|Rx|IFSTATE|BOOLEAN The SET operator assigns the value specified by the second operand to the first operand. If the data type of second operand does not agree with the data type of the first operand an error will be thrown. Syntax: The AND operator computes the conjunction of the first and second operands and stores the result in the third operand. If the third operand is not specified, the result is stored in the IFSTATE register. Its output is shown by the following truth table:
Syntax: AND Ix|Rx|IFSTATE|BOOLEAN Ix|Rx|IFSTATE|BOOLEAN (Rx|Ox|IFSTATE)? The NAND operator computes the negation of the conjunction of the first and second operands and stores the result in the third operand. If the third operand is not specified, the result is stored in the IFSTATE register. Its output is shown by the following truth table:
Syntax: NAND Ix|Rx|IFSTATE|BOOLEAN Ix|Rx|IFSTATE|BOOLEAN (Rx|Ox|IFSTATE)? The NOR operator computes the negation of the disjunction of the first and second operands and stores the result in the third operand. If the third operand is not specified, the result is stored in the IFSTATE register. Its output is shown by the following truth table:
Syntax: NOR Ix|Rx|IFSTATE|BOOLEAN Ix|Rx|IFSTATE|BOOLEAN (Rx|Ox|IFSTATE)? The NOT operator computes the negation of the first operand and stores the result in the second operand. If the second operand is not specified, the result is stored in the IFSTATE register. Its output is shown by the following truth table:
Syntax: NOT Ix|Rx|IFSTATE|BOOLEAN (Rx|Ox|IFSTATE)? The OR operator computes the disjunction of the first and second operands and stores the result in the third operand. If the third operand is not specified, the result is stored in the IFSTATE register. Its output is shown by the following truth table:
Syntax: OR Ix|Rx|IFSTATE|BOOLEAN Ix|Rx|IFSTATE|BOOLEAN (Rx|Ox|IFSTATE)? The XOR operator computes the exclusive disjunction of the first and second operands and stores the result in the third operand. If the third operand is not specified, the result is stored in the IFSTATE register. Its output is shown by the following truth table:
Syntax: XOR Ix|Rx|IFSTATE|BOOLEAN Ix|Rx|IFSTATE|BOOLEAN (Rx|Ox|IFSTATE)? The XNOR operator computes the negation of the exclusive disjunction of the first and second operands and stores the result in the third operand. If the third operand is not specified, the result is stored in the IFSTATE register. Its output is shown by the following truth table:
Syntax: XNOR Ix|Rx|IFSTATE|BOOLEAN Ix|Rx|IFSTATE|BOOLEAN (Rx|Ox|IFSTATE)? The BAND operator computes the conjunction of the first and second operands and stores the result in the third operand. Syntax: The BNAND operator computes the negation of the conjunction of the first and second operands and stores the result in the third. Syntax: BNAND Rx|INTEGER Rx|INTEGER Rx The BNOR operator computes the negation of the disjunction of the first and second operands and stores the result in the third operand. Syntax: The BNOT operator computes the negation of the first operand and stores the result in the second operand. Syntax: The BOR operator computes the disjunction of the first and second operands and stores the result in the third operand. Syntax: The BXOR operator computes the exclusive disjunction of the first and second operands and stores the result in the third operand. Syntax: The BXNOR operator computes the negation of the exclusive disjunction of the first and second operands and stores the result in the third operand. Syntax: BXNOR Rx|INTEGER Rx|INTEGER Rx The SHL operator shifts the bits of the INTEGER specified by the first operand to the left by the number of bits specified in the second operand and stores the result in the third operand. Syntax: The SHR operator shifts the bits of the INTEGER specified by the first operand to the right by the number of bits specified in the second operand and stores the result in the third operand. Syntax: The BIT operator sets the third operand to TRUE if the bit specified by the second operand is set to 1 in the INTEGER specified by the first operand; otherwise the third operand is set to FALSE. If the third operand is not specified, the result is stored in the IFSTATE register. Syntax: BIT Rx|INTEGER Rx|INTEGER (Rx|Ox|IFSTATE)? The INT operator converts a series of BOOLEAN values into an INTEGER and stores the result in the last operand. The first BOOLEAN operand corresponds to the high-order bit. Syntax: INT Ix|Rx|IFSTATE|BOOLEAN( Ix|Rx|IFSTATE|BOOLEAN)* Rx The EQ operator sets the third operand to TRUE if the first operand is equal to the second operand; otherwise the third operand is set to FALSE. If the third operand is not specified, the IFSTATE register is used instead. Syntax: EQ Ix|Rx|IFSTATE|BOOLEAN|INTEGER Ix|Rx|IFSTATE|BOOLEAN|INTEGER (Rx|Ox|IFSTATE)? The GT operator sets the third operand to TRUE if the first operand is greater than to the second operand; otherwise the third operand is set to FALSE. If the third operand is not specified, the IFSTATE register is used instead. Syntax: GT Rx|INTEGER Rx|INTEGER (Rx|Ox|IFSTATE)? The GTE operator sets the third operand to TRUE if the first operand is greater than or equal to the second operand; otherwise the third operand is set to FALSE. If the third operand is not specified, the IFSTATE register is used instead. Syntax: GTE Rx|INTEGER Rx|INTEGER (Rx|Ox|IFSTATE)? The ISBOOL operator sets the second operand to TRUE if the first operand contains a BOOLEAN value; otherwise the second operand is set to FALSE. If the second operand is not specified, the IFSTATE register is used instead. Syntax: The ISINT operator sets the second operand to TRUE if the first operand contains an INTEGER value; otherwise the second operand is set to FALSE. If the second operand is not specified, the IFSTATE register is used instead. Syntax: The LT operator sets the third operand to TRUE if the first operand is less than to the second operand; otherwise the third operand is set to FALSE. If the third operand is not specified, the IFSTATE register is used instead. Syntax: LT Rx|INTEGER Rx|INTEGER (Rx|Ox|IFSTATE)? The LTE operator sets the third operand to TRUE if the first operand is less than or equal to the second operand; otherwise the third operand is set to FALSE. If the third operand is not specified, the IFSTATE register is used instead. Syntax: LTE Rx|INTEGER Rx|INTEGER (Rx|Ox|IFSTATE)? The NEQ operator sets the third operand to TRUE if the first operand is not equal to the second operand; otherwise the third operand is set to FALSE. If the third operand is not specified, the IFSTATE register is used instead. Syntax: NEQ Ix|Rx|IFSTATE|BOOLEAN|INTEGER Ix|Rx|IFSTATE|BOOLEAN|INTEGER (Rx|Ox|IFSTATE)? The PRINT operator displays the value of the specified operand. Syntax: The REM operator allows you to place a comment in the program. It otherwise does nothing. Syntax: REM STRING? The CALL operator executes the program specified by the first operand. Another player's program may be called by specifing the player name and the program name seperated by two colons. When the program completes, execution continues on the next line. If the specified program does not exist, an error will be thrown. Called programs use the same inputs, outputs, and stack as the calling program. The registers and IFSTATE register are not shared. If the called program throws and error, execution of the calling program is halted. Syntax: CALL STRING Example: CALL MyProgram Calls the program "MyProgram". CALL JohnDoe::YourProgram Calls the program "YourProgram" belonging to the player "JohnDoe". The GOTO operator transfers execution to the location of the LABEL specified in the first operand. When searching for a LABEL, the search begins at line 0 of the program. A LABEL is not case-sensitive. If more than one LABEL operator exists with the same LABEL, the first LABEL operator is used. Subsequent LABEL operators are ignored. If a LABEL is not found, an error will be thrown. Syntax: GOTO LABEL The IF operator changes the next line in the program that will be executed based on the value of the IFSTATE register. If the IFSTATE register contains TRUE, execution is transferred to the location of the LABEL specified by the first operand. If the second operand is specified and the IFSTATE register contains FALSE, execution is transferred to the location of the LABEL specified by the second operand; otherwise execution continues at the next line. When searching for a LABEL, the search begins at line 0 of the program. A LABEL is not case-sensitive. If more than one LABEL operator exists with the same LABEL, the first LABEL operator is used. Subsequent LABEL operators are ignored. If a LABEL is not found, an error will be thrown. Syntax: The LABEL operator identifies the current location in the program with the LABEL specified by the first operand. A LABEL is not case-sensitive. Syntax: The STOP operator halts program execution. Syntax: STOP The WAIT operator causes the program to be suspended for the number of ticks specified by the first operand. A tick is 1/10th of a second. Syntax: The ADD operator adds the INTEGER specified by the first operand to the INTEGER specified by the second operand and stores the result in the third operand. Syntax: The DEC operator subtracts 1 from the INTEGER specified by the first operand and stores the result in the first operand. Syntax: The DIV operator divides the INTEGER specified by the first operand by the INTEGER specified by the second operand and stores the result in the third operand. Syntax: The INC operator adds 1 to the INTEGER specified by the first operand and stores the result in the first operand. Syntax: The MOD operator divides the INTEGER specified by the first operand by the INTEGER specified by the second operand and stores the remainder in the third operand. Syntax: The MUL operator multiplies the INTEGER specified by the first operand by the INTEGER specified by the second operand and stores the result in the third operand. Syntax: The SUB operator subtracts the INTEGER specified by the second operand from the INTEGER specified by the first operand and stores the result in the third operand. Syntax: The PEEK operator assigns the value on the top of the stack to the specified operand. The value is not removed from the stack. If the data type of value does not agree with the data type of the operand an error will be thrown. If the stack is empty an error will be thrown. Syntax: The POP operator assigns the value on the top of the stack to the specified operand. The value is removed from the stack. If the data type of value does not agree with the data type of the operand an error will be thrown. If the stack is empty an error will be thrown. Syntax: The PUSH operator puts the specified operand on top of the stack. Syntax: PUSH Ix|Rx|BOOLEAN|INTEGER|IFSTATE The following commands are used with programs: The add command adds a new line of code to the specified program. You may add more than one line by separating each opcode with semi-colons. Syntax: /foe program add <name> <opcode>[;<opcode>[...]] Parameters: name -- The name of the program. opcode -- The opcode to add to the program. Permissions Required: Example: /foe program add MyProgram SET O0 I0 Adds one line to the program "MyProgram". /foe program add MyProgram AND I0 I1 R0;AND I2 I3 R1;AND R0 R1 O0 Adds three lines to the program "MyProgram". The clear command removes all code from the specified program. Syntax: /foe program clear <name> Parameters: name -- The name of the program. Permissions Required: Example: /foe program clear MyProgram Removes all code from the program "MyProgram". The create command creates a new empty program with the specified name. Syntax: /foe program create <name> Parameters: name -- The name of the program. Permissions Required: Example: /foe program create MyProgram Creates a program named "MyProgram". The delete command deletes the specified program. You must confirm deletion of the program by using the command "/foe program confirm" or reject the deletion of the program by using the command "/foe program reject". Syntax: /foe program delete <name|CONFIRM|CANCEL> Parameters: name -- The name of the program. CONFIRM -- Confirm the deletion of a program. CANCEL -- Reject the deletion of a program. Permissions Required: Example: /foe program delete MyProgram Requests that the program "MyProgram" be deleted and then confirms the deletion. The help command displays the specified page of the list of available commands or the first page if no page is specified. Syntax: /foe program help [page] Parameters: page -- The help page to display. Permissions Required: None. The insert command inserts a new line of code to the specified program at the specified line. You may insert more than one line by separating each opcode with semi-colons. Syntax: /foe program insert <name> <line> <opcode>[;<opcode>[...]] Parameters: name -- The name of the program. line -- The line to insert the code at. opcode -- The opcode to add to the program. Permissions Required: Example: /foe program insert MyProgram 3 SET O0 I0 Inserts one line at line 3 to the program "MyProgram". /foe program insert MyProgram 2 AND I0 I1 R0;AND I2 I3 R1;AND R0 R1 O0 Inserts three lines at line 2 to the program "MyProgram". The list command displays a list of all programs or the code within a specified program belonging the specified player starting at an optionally specified line number. If no player is specified, then the current player is assumed. When listing the code within a program, if the end of the program is reached then "EOL" is printed. Syntax: /foe program list [[player::]name [line]] Parameters: player -- The name of the player. name -- The name of the program. line -- The line number to begin listing the code at. Permissions Required: Example: /foe program list Displays a list of all programs. /foe program list MyProgram Displays the code in the program "MyProgram" starting at line 0. /foe program list MyProgram 32 Displays the code in the program "MyProgram" starting at line 32. The owner command changes the owner of the specified program to the specified user. Syntax: /foe program owner <name> <player> Parameters: name -- The name of the program. player -- The name of the player. Permissions Required: Example: /foe program owner MyProgram JohnDoe Changes the owner of "MyProgram" to "JohnDoe". The remove command removes the specified number of lines of code starting at the specified line. If the number of lines of code to remove is not specified, a single line of code is removed. Syntax: /foe program remove <name> <line> [lines] Parameters: name -- The name of the program. line -- The line number to start removing code at. lines -- The number of lines of code to remove. Permissions Required: Example: /foe program remove MyProgram 4 Removes a line of code from the program "MyProgram" at line 4. /foe program remove MyProgram 7 2 Removes two lines of code from the program "MyProgram" starting at line 7. The rename command renames the specified program. Syntax: /foe program <name> <newname> Parameters: name -- The name of the program. newname -- The new name of the program. Permissions Required: Example: /foe program rename MyProgram YourProgram Renames the program "MyProgram" to "YourProgram". The run command runs the specified program using the specified input belonging the specified player. If no player is specified, then the current player is assumed. Syntax: /foe program run <[player::]name> [input[ input[...]]] Parameters: name -- The name of the program input -- A boolean value that indicates the value of the input. Permissions Required: Example: /foe program run MyProgram 1 0 1 1 Runs the program "MyProgram". The following permissions are used with programs: 7.9.1. FOE.PROGRAM.CHANGEOWNER Allows a player to change the owner of program. Allows a player to write programs. Regions may be created using two methods. Regions may not be larger than the size defined in the configuration file unless you have the foe.region.bypass.size permission. The foe.region.create permission is required in order to create regions. 8.1.1. CREATING A REGION USING COORDINATES A region may be created using a specified set of coordinates. Use the /foe region create command specifing the name of the new region and the coordinates of each corner of the region. 8.1.2. CREATING A REGION USING SELECTION A region may be created using a selection tool. Use the /foe region create command specifing the name of the new region. The selection tool will be automatically added to your inventory. Right-click to select the first corner of the region. Right-click again to select the second corner of the region to finish creating the region. Use the /foe region create command to exit selection mode without creating the region. Regions may be modified using two methods. Regions may not be larger than the size defined in the configuration file unless you have the foe.region.bypass.size permission. The foe.region.modify permission is required or you must be the owner in order to modify a region. 8.2.1. MODIFYING A REGION USING COORDINATES A region may be modified using a specified set of coordinates. Use the /foe region modify command specifing the name of the new region and the coordinates of each corner of the region. 8.2.2. MODIFYING A REGION USING SELECTION A region may be modified using a selection tool. Use the /foe region modify command specifing the name of the new region. The selection tool will be automatically added to your inventory. Right-click to select the first corner of the region. Right-click again to select the second corner of the region to finish modifing the region. Use the /foe region modify command to exit selection mode without modifing the region. When protection is enabled for a region, players that do not own the region or who do not have the foe.region.bypass.protection permission cannot place or destroy blocks within that region. When locking is enabled for a region, players that do not own the region, are on the region's allow list, or who do not have the foe.region.bypass.lock permission may not enter the region and will be ejected to the closest border. Regions are allowed to overlap. When a player is within the overlapped portion of two or more regions, the z-order of the regions controls which region is used when checking for protection and locking. The region with lowest z-order is used. If two regions have the same z-order, then the region that was created first is used. Example:
Given the two overlapped regions above, if region 2 has a z-order of 0 and region 1 has a z-order of 1, then when a player moves into the blue area region 2 is used to determine protection and locking. The buy region sign allows a player to buy a region. A buy region sign is created by placing a sign within a region. The first line of the sign must be "[BuyRegion]". The next line must the cost charged to the player using the sign. The first line of the sign will turn blue if it has been created successfully; otherwise it will turn red. When a player uses the sign, the player will become the owner of the region and the sign will be destroyed. The foe.signs.create.buyregion or foe.signs.buyregion.create permission is required to be able to create a buy region sign. The foe.signs.use.buyregion or foe.signs.buyregion.use permission is required to be able to use a buy region sign. Example:
The following commands are used with regions: The allow command adds a player to the list of allowed players for the specified region. Syntax: /foe region allow <name> <player> Parameters: name -- The name of the region. player -- The name of the player. Permissions Required: foe.region.modify or ownership Example: /foe region allow MyRegion JohnDoe Allows JohnDoe to enter the region "MyRegion". The create command creates a new region. If the coordinates are not specified, the corners of the region are defined by right-clicking on a block using a bone. Regions may not be larger than the size defined in the configuration file unless the user has the foe.region.bypass.size permission. Syntax: /foe region create <name [x1 y1 z1 x2 y2 z2]|CANCEL> Parameters: name -- The name of the region. x1 -- The first x-coordinate of the region. y1 -- The first y-coordinate of the region. z1 -- The first z-coordinate of the region. x2 -- The second x-coordinate of the region. y2 -- The second y-coordinate of the region. z2 -- The second z-coordinate of the region. CANCEL -- Cancel region creation. Permissions Required: Example: /foe region create MyRegion Enters selection mode to create the region "MyRegion". 8.7.3. /FOE REGION CURRENTREGION The currentregion command displays a list of regions that the player is current located in sorted in the order that regions are evaluated in. Syntax: /foe region currentregion Parameters: None. Permissions Required: Example: /foe region currentregion Displays the regions the player is currently located in. The delete command deletes the specified region. Syntax: /foe region delete <name> Parameters: name -- The name of the region. Permissions Required: foe.region.delete or ownership Example: /foe region delete MyRegion Deletes the region "MyRegion". The deny command removes a player to the list of allowed players for the specified region. Syntax: /foe region deny <name> <player> Parameters: name -- The name of the region. player -- The name of the player. Permissions Required: foe.region.modify or ownership Example: /foe region deny MyRegion JohnDoe Prohibits JohnDoe from entering the region "MyRegion". 8.7.6. /FOE REGION ENTERMESSAGE The entermessage command sets the message displayed when a player enters the specified region. If the message is omitted, no message is displayed to the player. Color codes may be used in the message. Syntax: /foe region entermessage <name> [message] Parameters: name -- The name of the region. message -- The message displayed. Permissions Required: foe.region.modify or ownership Example: /foe region entermessage MyRegion &4Entering MyRegion! The expand command expands the specified region up or down. Syntax: /foe region expand <name> <UP|DOWN|BOTH> <blocks|MAX> Parameters: name -- The name of the region. UP -- Expand the region up. DOWN -- Expand the region down. BoTH -- Expand the region up and down. blocks -- The number of blocks. MAX -- Expand the region to the limit. Permissions Required: foe.region.modify or ownership Example: /foe region expand MyRegion both max The help command displays the specified page of the list of available commands or the first page if no page is specified. Syntax: /foe region help [page] Parameters: page -- The help page to display. Permissions Required: None. Example: /foe region help 3 The info command displays information about the specified region. If the region is omitted, information about the current region is displayed. Syntax: /foe region info [name] Parameters: name -- The name of the region. Permissions Required: foe.region.info or ownership Example: /foe region info MyRegion 8.7.10. /FOE REGION INVULNERABILITY The invulnerability command turns invulnerability on or off within the specified region. Syntax: /foe region invulnerability <name> [on|1|true|yes|off|0|false|no] Parameters: name -- The name of the region. Permissions Required: foe.region.modify or ownership Example: /foe region invulnerability MyRegion off 8.7.11. /FOE REGION LEAVEMESSAGE The leavemessage command sets the message displayed when a player leaves the specified region. If the message is omitted, no message is displayed to the player. Color codes may be used in the message. Syntax: /foe region leavemessage <name> [message] Parameters: name -- The name of the region. message -- The message displayed. Permissions Required: foe.region.modify or ownership Example: /foe region leavemessage MyRegion &4Leaving MyRegion! The list command displays a list of all the regions. Syntax: /foe region list Parameters: None. Permissions Required: Example: /foe region list The pvp command locks or unlocks the specified region. Syntax: /foe region lock <name> [on|1|true|yes|off|0|false|no] Parameters: name -- The name of the region. Permissions Required: foe.region.modify or ownership Example: /foe region lock MyRegion off The modify command modifies the specified region. If the coordinates are not specified, the corners of the region are defined by right-clicking on a block using a bone. A region defined this way must be confirmed. Regions may not be larger than the size defined in the configuration file unless the user has the foe.region.bypass.size permission. Syntax: /foe region modify <name [x1 y1 z1 x2 y2 z2]|CANCEL> Parameters: name -- The name of the region. x1 -- The first x-coordinate of the region. y1 -- The first y-coordinate of the region. z1 -- The first z-coordinate of the region. x2 -- The second x-coordinate of the region. y2 -- The second y-coordinate of the region. z2 -- The second z-coordinate of the region. CANCEL -- Cancel region modification. Permissions Required: foe.region.modify or ownership Example: /foe region modify MyRegion The owner command sets the owner of the specified region. Syntax: /foe region owner <name> <player> Parameters: name -- The name of the region. player -- The name of the player. Permissions Required: foe.region.modify or ownership Example: /foe region owner MyRegion JohnDoe The pvp command turns protection on or off within the specified region. Syntax: /foe region protect <name> [on|1|true|yes|off|0|false|no] Parameters: name -- The name of the region. Permissions Required: foe.region.modify or ownership Example: /foe region protect MyRegion off The pvp command turns PVP on or off within the specified region. Syntax: /foe region pvp <name> [on|1|true|yes|off|0|false|no] Parameters: name -- The name of the region. Permissions Required: foe.region.modify or ownership Example: /foe region pvp MyRegion off The rename command renames the specified region. Syntax: /foe region zorder <name> <newname> Parameters: name -- The name of the region. newname -- The new name of the region. Permissions Required: foe.region.modify or ownership Example: /foe region rename MyRegion YourRegion The zorder command sets the z-order of the specified region. Syntax: /foe region zorder <name> <zorder> Parameters: name -- The name of the region. zorder -- The z-order. Permissions Required: foe.region.modify or ownership Example: /foe region zorder MyRegion 2 The following permissions are used with regions: Allows a player to enter locked regions without explicit permission. 8.8.2. FOE.REGION.BYPASS.PROTECTION Allows a player to ignore region protection. Allows a player to create a region greater than the size restriction. Allows a player to create a region. Allows a player to delete a region they do not own. Allows a player to view information about a region. Allows a player to list regions. Allows a player to modify a region they do not own. 8.8.9. FOE.SIGNS.BUYREGION.CREATE Allows a player to create a "BuyRegion" sign. 8.8.10. FOE.SIGNS.BUYREGION.USE Allows a player to use a "BuyRegion" sign. 8.8.11. FOE.SIGNS.CREATE.BUYREGION Allows a player to create a "BuyRegion" sign. 8.8.12. FOE.SIGNS.USE.BUYREGION Allows a player to use a "BuyRegion" sign. Colored signs allow you to color the content on a sign. Use the following character sequences in the text of the sign to change the color:
The foe.signs.create.colored or foe.signs.colored.create permission is required to be able to create a colored sign. The repair sign repairs an item when used. A repair sign is created by placing a sign. The first line of the sign must be "[Repair]". The next line must be a repair type. The third line, which is optional, is the cost charged to the player using the sign. The first line of the sign will turn blue if it has been created successfully; otherwise it will turn red.
The foe.signs.create.repair or foe.signs.repair.create permission is required to be able to create a repair sign. The foe.signs.use.repair or foe.signs.repair.use permission is required to be able to use a repair sign. Example:
The time sign changes the time when used. A time sign is created by placing a sign. The first line of the sign must be "[Time]". The next line must be either "day" or "night". The third line, which is optional, is the cost charged to the player using the sign. The first line of the sign will turn blue if it has been created successfully; otherwise it will turn red. The foe.signs.create.time or foe.signs.time.create permission is required to be able to create a time sign. The foe.signs.use.time or foe.signs.time.use permission is required to be able to use a time sign. Example:
The weather sign changes the weather when used. A weather sign is created by placing a sign. The first line of the sign must be "[Weather]". The next line must be either "sunny" or "stormy". The third line, which is optional, is the cost charged to the player using the sign. The first line of the sign will turn blue if it has been created successfully; otherwise it will turn red. The foe.signs.create.weather or foe.signs.weather.create permission is required to be able to create a weather sign. The foe.signs.use.weather or foe.signs.weather.use permission is required to be able to use a weather sign. Example:
Redstone current may be transmitted wirelessly through the use of transmit and receive signs. When redstone current powers a transmit sign, that current is sent to all receive signs that have the same channel and owner as the transmit sign. The foe.signs.create.wireless or foe.signs.wireless.create permission is required to be able to create a wireless signs. The transmit sign transmits redstone current. A transmit sign is created by placing a sign. The first line of the sign must be "[Transmit]". The next line must be the channel. The first line of the sign will turn blue if it has been created successfully; otherwise it will turn red. The owner of a successfully created transmit sign will appear on the last line. Example:
The receive sign receives redstone current. A receive sign is created by placing a sign. The first line of the sign must be "[Receive]". The next line must be the channel. The first line of the sign will turn blue if it has been created successfully; otherwise it will turn red. The owner of a successfully created receive sign will appear on the last line. Example:
The wool color sign changes the color of the block of wool it is mounted on based on redstone current flowing to the sign. A wool color sign is created by placing a sign on a block of wool. The first line of the sign must be "[WoolColor]". The second line must be the color to change the wool to when redstone current is flowing to the sign. The third line, which is optional, must be the color to change the wool to when redstone current is not flowing to the sign. The first line of the sign will turn blue if it has been created successfully; otherwise it will turn red. If the sign is mounted on the end of a line of wool, the last block of wool (the block furthest from the sign) will change color instead. The foe.signs.create.woolcolor or foe.signs.woolcolor.create permission is required to be able to create a wool color sign. Example:
The colors command displays a list of colors used by colored signs. Syntax: /foe colors [page] Parameters: page -- The page to display. Permissions Required: foe.signs.create.colored or foe.signs.colored.create The following permissions are used with signs: 9.8.1. FOE.SIGNS.CREATE.COLORED Allows a player to create a colored sign. Allows a player to create a "Time" sign. 9.8.3. FOE.SIGNS.CREATE.REPAIR Allows a player to create a "Repair" sign. 9.8.4. FOE.SIGNS.CREATE.WEATHER Allows a player to create a "Weather" sign. 9.8.5. FOE.SIGNS.CREATE.WIRELESS Allows a player to create a "Transmit" or "Receive" sign. 9.8.6. FOE.SIGNS.CREATE.WOOLCOLOR Allows a player to create a "WoolColor" sign. 9.8.7. FOE.SIGNS.COLORED.CREATE Allows a player to create a colored sign. 9.8.8. FOE.SIGNS.REPAIR.CREATE Allows a player to create a "Repair" sign. Allows a player to use a "Repair" sign. Allows a player to create a "Time" sign. Allows a player to use a "Time" sign. Allows a player to use a "Repair" sign. Allows a player to use a "Time" sign. Allows a player to use a "Weather" sign. 9.8.15. FOE.SIGNS.WEATHER.CREATE Allows a player to create a "Weather" sign. Allows a player to use a "Weather" sign. 9.8.17. FOE.SIGNS.WIRELESS.CREATE Allows a player to create a "Transmit" or "Receive" sign. 9.8.18. FOE.SIGNS.WOOLCOLOR.CREATE Allows a player to create a "WoolColor" sign. Boolean Boolean is data type that represents the values TRUE or FALSE. Integer Integer is a signed integral data type that stores values in the range -2,147,483,648 to 2,147,483,647 inclusive. label A label indentifies a location in a program. Labels must start with an upper alpha, lower alpha, or underscore character. The remaining characters may be upper alpha, lower alpha, numeric, or underscore characters. A label may not be more than 50 characters long. stack A stack is a last in, first out (LIFO) data structure. The stack can have either Boolean or Integer data types as an element. A stack is characterized by three fundamental operations: push, pop and peek. The push operation adds a new item to the top of the stack. If the stack is full the stack is then considered to be in an overflow state. The pop operation removes an item from the top of the stack. A pop either reveals previously concealed items or results in an empty stack. If the stack is empty when a peek operation is initiated, then it goes into underflow state (It means no items are present in stack to be removed). The peek operation gets the item from the top-most position and returns it to the user without removing it. The same underflow state can also occur in a peek operation if stack is empty. /foe colors [page] Displays a list of colors used by colored signs. /foe debug Toggles debug on and off. /foe fireresistance Toggles fire resistance off and on. /foe flying Toggles flying off and on. /foe getinfo Displays information about the selected block. /foe help [page] Displays help information. /foe instabreak Toggles insta-break off and on. /foe instakill Toggles insta-kill off and on. /foe nostarvation Toggles starvation off and on. /foe permissions [page] Displays the permissions reference. /foe portal create <name> <NORTH|SOUTH|EAST|WEST|UP|DOWN> [destination|NONE] Creates a new portal at the current player location. /foe portal delete <name> Deletes an existing portal. /foe portal destination <name> <destination|NONE> Changes the destination of a portal. /foe portal help [page] Displays the specified page of the list of available commands or the first page if no page is specified. /foe portal list Displays a list of all the portals. /foe portal orientation <name> <NORTH|SOUTH|EAST|WEST|UP|DOWN> Changes the orientation of a portal. /foe portal owner <name> <player> Changes the owner of a portal. /foe portal zorder <name> <newname> Renames a portal. /foe program add <name> <opcode>[;<opcode>[...]] Adds a new line to a program. /foe program clear <name> Removes all lines of code from a program. /foe program create <name> Creates a new program. /foe program delete <name|CONFIRM|CANCEL> Deletes a program. /foe program help [page] Displays help information. /foe program insert <name> <line> <opcode>[;<opcode>[...]] Inserts a line of code into a program. /foe program list [[player::]name [line]] Displays the list of programs or lists the code for a program. /foe program owner <name> <player> Changes the owner of a program. /foe program remove <name> <line> [lines] Removes a line of code from a program. /foe program rename <name> <newname> Renames a program. /foe program run <[player::]name> [input[ input[...]]] Runs a program with the specified input. /foe region allow <name> <player> Allows a player to enter a region. /foe region create <name [x1 y1 z1 x2 y2 z2]|CANCEL> Creates a new region. /foe region currentregion Displays the regions the player is currently in. /foe region delete <name> Deletes a region. /foe region deny <name> <player> Denies access to player from entering a region. /foe region entermessage <name> [message] Displays or sets the enter message of a region. /foe region expand <name> <UP|DOWN|BOTH> <blocks|MAX> Expands or contracts a region. /foe region help [page] Displays help information. /foe region info Displays information about a region. /foe region invulnerability <name> [on|1|true|yes|off|0|false|no] Sets invulnerability within a region. /foe region leavemessage <name> [message] Displays or sets the leave message of a region. /foe region list Displays a list of regions. /foe region lock <name> [on|1|true|yes|off|0|false|no] Locks or unlocks a region. /foe region modify <name [x1 y1 z1 x2 y2 z2]|CANCEL> Modifies a region. /foe region owner <name> <player> Sets the owner of a region. /foe region protect <name> [on|1|true|yes|off|0|false|no] Protects or unprotects a region. /foe region pvp <name> [on|1|true|yes|off|0|false|no] Turns PVP on or off for a region. /foe region rename <name> <newname> Renames a region. /foe region zorder <name> <zorder> Changes the z-order of a region. /foe status [page] Displays status information. /foe unlimiteditems Toggles unlimited items off and on. /foe waterbreathing Toggles water breathing off and on. foe.debug Allows a player to toggle additional debug information on and off. foe.fireresistance Grants a player fire resistance and allows them to toggle fire resistance off and on. foe.flying Grants a player the flying ability and allows them to toggle flying off and on. foe.instabreak Grants a player the insta-break ability and allows them to toggle insta-break off and on. foe.instakill Grants a player the insta-kill ability and allows them to toggle insta-kill off and on. foe.nostarvation Grants a player no starvation and allows them to toggle starvation off and on. foe.portal.create Allows a player to create a portal. foe.portal.delete Allows a player to delete a portal. foe.portal.list Allows a player to list a portal. foe.portal.modify Allows a player to modify a portal. foe.program.changeowner Allows a player to change the owner of program. foe.program.write Allows a player to write programs. foe.region.bypass.lock Allows a player to enter locked regions without explicit permission. foe.region.bypass.protection Allows a player to ignore region protection. foe.region.bypass.size Allows a player to create a region greater than the size restriction. foe.region.create Allows a player to create a region. foe.region.delete Allows a player to delete a region they do not own. foe.region.info Allows a player to view information about a region. foe.region.list Allows a player to list regions. foe.region.modify Allows a player to modify a region they do not own. foe.status Allows a player to display their status. foe.signs.buyregion.create Allows a player to create a "BuyRegion" sign. foe.signs.buyregion.use Allows a player to use a "BuyRegion" sign. foe.signs.colored.create Allows a player to create a colored sign. foe.signs.create.buyregion Allows a player to create a "BuyRegion" sign. foe.signs.create.colored Allows a player to create a colored sign. foe.signs.create.ic Allows a player to create an "IC" sign. foe.signs.create.repair Allows a player to create a "Repair" sign. foe.signs.create.ride Allows a player to create a "Ride" sign. foe.signs.create.time Allows a player to create a "Time" sign. foe.signs.create.woolcolor Allows a player to create a "WoolColor" sign. foe.signs.create.weather Allows a player to create a "Weather" sign. foe.signs.create.wireless Allows a player to create a "Transmit" or "Receive" sign. foe.signs.ic.create Allows a player to create an "IC" sign. foe.signs.repair.create Allows a player to create a "Repair" sign. foe.signs.repair.use Allows a player to use a "Repair" sign. foe.signs.ride.create Allows a player to create a "Ride" sign. foe.signs.ride.use Allows a player to use a "Ride" sign. foe.signs.use.buyregion Allows a player to use a "BuyRegion" sign. foe.signs.use.repair Allows a player to use a "Repair" sign. foe.signs.use.ride Allows a player to use a "Ride" sign. foe.signs.use.time Allows a player to use a "Time" sign. foe.signs.use.weather Allows a player to use a "Weather" sign. foe.signs.time.create Allows a player to create a "Time" sign. foe.signs.time.use Allows a player to use a "Time" sign. foe.signs.woolcolor.create Allows a player to create a "WoolColor" sign. foe.signs.weather.create Allows a player to create a "Weather" sign. foe.signs.weather.use Allows a player to use a "Weather" sign. foe.signs.wireless.create Allows a player to create a "Transmit" or "Receive" sign. foe.unlimiteditems Grants a player unlimited items and allows them to toggle unlimited items off and on. foe.waterbreathing Grants a player water breathing and allows them to toggle water breathing off and on. &0 Black &1 Dark Blue &2 Dark Green &3 Dark Aqua &4 Dark Red &5 Dark Purple &6 Gold &7 Gray &8 Dark Gray &9 Blue &a Green &b Aqua &c Red &d Light Purple &e Yellow &f White Appendix E: SAMPLE CONFIGURATION FILE #The following controls the features that are enabled. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Copyright (c) 2011 ForceOne Technologies. Web site design copyright (c) 2011 ForceOne Technologies. Logos are copyright and/or trademarked by their respective holders. All rights reserved. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Home | MineCraft | Go | Illusions | References | Contact Us | About Us | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
