Flags
Using Flags
:;Flags are the main customization force behind Gateways. They manipulate behavior of individual gates, networks, and paths. The types of flags vary wildly from open/closing animations for gates, toll pricing, visibility, what material the portal opens with... All flags can be edited by using the commands '/gate flag <gate> <flagtype> <value>', '/net flag <network> <flagtype> <value>', and '/path flag <from> <to> <flagtype> <value>'. To see the current state of flags, use '/<gate/net/path> info' on the gate/net/path you wish to look at.
All flags have a default state on creation of their parent. These defaults can be set in Gateways' configuration file. Additionally, each flag has its own permission node so you can hand out permissions to players for editing flags on a flag-by-flag basis. For example, you can only let donators be able to edit their gate's portal material by uniquely giving them the 'gateways.gate.flag.substance' permission.
Gate Flags
| Name | Desciption | Parameters |
|---|---|---|
| SUBSTANCE | Sets what material is used for opening | (LAVA,WATER,NETHER,ENDER,WEB) |
| USABLE | Determines if gate can be used as outgoing gate | (TRUE/FALSE) |
| RETURN | Allows travelling back when used as receiving gate | (TRUE/FALSE) |
| VISIBLE | Determines if gate can be used/seen for incoming connections | (TRUE/FALSE) |
| LOCAL | Determines if gate can be used/seen for local connections | (TRUE/FALSE) |
| LOCK | Locks gate so it can’t be used at all (for temporary disabling) | (TRUE/FALSE) |
| PRICE | Determines the price of using the gate in a connection | (DOUBLE) |
| PASSWORD | Sets a password for connecting to the gate | (STRING) |
| PERMISSION | Sets a permissions node requirement for the gate | (STRING) |
| PROTECT | Protects the area around the gate from other players & explosions | (TRUE/FALSE) |
| ONOPEN | Sets the open animation | (FLICKER/EXPAND/CONTRACT/INSTANT) |
| ONCLOSE | Sets the closing animation | (FLICKER/EXPAND/CONTRACT/INSTANT) |
| WHITELIST | Determines if the usage of the gate is whitelisted by USER* list | (TRUE/FALSE) |
Network Flags
| Name | Desciption | Parameters |
|---|---|---|
| LOCK | Locks network so it can’t be used at all (for temporary disabling) | (TRUE/FALSE) |
| MULTIWORLD | Determines if network can be used between worlds | (TRUE/FALSE) |
| PASSWORD | Sets a password for connecting with the network | (STRING) |
| PERMISSION | Sets a permissions node requirement for the network | (STRING) |
| PRICE | Determines the price of using the network in a connection | (DOUBLE) |
| WHITELIST | Determines if the usage of the network is whitelisted by USER* list | (TRUE/FALSE) |
| PUBLIC | Determines if linking gates to network requires MEMBER* status | (TRUE/FALSE) |
Path Flags
| Name | Desciption | Parameters |
|---|---|---|
| LOCK | Locks path so it can’t be used at all (for temporary disabling) | (TRUE/FALSE) |
| PASSWORD | Sets a password for connecting with the path | (STRING) |
| PERMISSION | Sets a permissions node requirement for the path | (STRING) |
| PRICE | Determines the price of using the path in a connection | (DOUBLE) |
*See Gate Permissions for more details
-
View User Profile
-
Send Message
Posted Feb 25, 2012Curious why you would use a double data type instead of int or long, double seems a little over done. You could probably even get away with short to reduce memory usage. Also the plugin looks great!