ADVANCED BIND GUIDE

Black_Specter · 02-04-2006 04:05 PM

ADVANCED BIND GUIDE
By BlackSpectre

The purpose for this guide is to provide more detailed information on HOW binds work so that the would-be bind designer can intelligently craft their own binds or troubleshoot them. This guide grew out of my desire to understand why a bind I created worked, and I figured I might as well write down what Ive learned in the hope that someone else might find the information useful. I have gathered the information in this guide from many different sources: the City of Heroes Forum, my own testing and experience, and from fellow gamers such as Innovator, Blueray, Cockaroach, and Zerotemp. It is my hope that presenting this information in one concise document will help others to create superb binds much easier than if they had to track down all this information on their own.

This guide assumes the reader is familiar with the /bind command in City of Heroes/Villains and has mastered its more common functions as detailed in other venues such as Curveballs excellent WHOLLY UNOFFICIAL AND FAIRLY INCOMPLETE GUIDE TO /BIND . As such, many details on how to create and use binds are omitted from this document. If you are new to binds, please read Curveballs guide above, read the binds section in the COH manual, and familiarize yourself with making binds before you read this guide.

TABLE OF CONTENTS:
1. Multiple Toggle Binds
2. Using Powexec_NAME
3. Using Powexec_TOGGLE
4. Combining Powexec_NAME and Powexec_TOGGLE
5. Using Toggle Keys
6. Toggle Key Text Binds
7. Understanding Multiple Powexec Commands For The SAME POWER
8. Movement Direction Commands
9. Click Power Binds
10. Using Powexec_AUTO
11. Turning Powers Off
12. Arranging Your Bind Commands
13. Dealing With LAG

MULTIPLE TOGGLE BINDS

Multiple toggle binds are binds that contain more than one toggle power. There are 6 commands used to activate a toggle power in a bind:
1) powexec_name [power name]
2) powexec_slot [slot#]
3) powexec_altslot [slot#]
4) powexec_alt2slot [slot#]
5) powexec_tray [slot#] [tray#]
6) powexec_toggleon [power name] (and its opposite, powexec_toggleoff [power name]).

The first five commands operate in the same way as powexec_name (1-5), while the powexec_toggleon command operates in a distinctly different manner.

The length of a bind can not exceed 255 characters. Omitting underscores _ in commands such as powexec_name, powexec_toggle_on and bind_load_file, and leaving out unneeded spaces is one way to cut and decrease the character count, in order to enable longer binds. For example, powexec_name becomes powexecname, bind_load_file becomes bindloadfile, etc. Underscores aren't even read by the command parser, and only serve to make commands easier to read. In fact, bind_load_file is the same as bindloadfile, or bindload_file, or b_i_n_d_l_o_a_d_f_i_l_e. When your binds get lengthy, space becomes precious because of the limit to the text size of a bind, so it's a good practice to leave underscores out. However, for the purposes of this guide, the published (easier to read) form of command names will be used.

Incidentally, a list of all the commands in the game can be seen by typing /cmdlist into the chat box.

USING POWEXEC_NAME

The first way to create multiple toggle binds is by using the powexec_name command. For example:
/bind Y "powexec_name super jump$$powexec_name temp invulnerability$$powexec_name unyielding$$powexec_name invincibility.

The bind above attaches 4 powers to a single key: Invincibility, Unyielding, Temp Invulnerability, and Super Jump. However, only one power will turn on whenever a key is pressed, but which one?

The power activation sequence in multiple toggle binds is fairly straight forward but it is critical to understanding binds. Toggle powers in binds execute from right to left. When binds containing a string of multiple powexec_name commands is executed, the bind shuts off ALL currently active powers in the bind string, and turns on the first non-active power starting from the right or beginning of the bind.

For ease of explanation, the first toggle power starting from the right will be designated A, the second power from the right as B, the third C, and so on (eg., /bind <key> powexec_name D$$powexec_name C$$ powexec_name B$$ powexec_name A).

Which toggle power turns on greatly depends upon whether or not a power is on or off at the time the bind is executed. So assuming first that all powers in the bind are off, the power activation sequence would go something like this: First the bind will attempt to turn on power A. If A is already on, then B will turn on. If B is already on, then A will turn on. If both A and B are on, C will turn on. If A, B, and C are on, then D will turn on, and so on. The bind searches for the first non-active power to turn ON starting from the right, while turning OFF all currently active powers in the bind string. Needless to say, if all the powers in the bind script are currently turned on, the bind will turn them all off. This bind, for example, will toggle on and off between Fly and Sprint, while turning off Unyielding and Invincibility (if they were on, otherwise no action):

/bind Y powexec_name Invincibility$$powexec_name Unyielding$$powexec_name Sprint$$powexec_name Fly

The typical multiple toggle bind will usually have only 2 toggle powers in it (toggling between A and B). However, inserting more than two toggle powers in a bind can ensure that those additional powers are turned off when the desired power is turned on (useful for conserving endurance, etc.). Powerexec_name also has fewer characters than powexec_toggleoff (discussed below), and therefore may be a more efficient choice for minimizing bind string length. Further, it is sometimes necessary to have a third or even fourth power in the bind script especially if the bind utilizes the toggle key function, is part of a text/toggle bind, or toggle powers are combined with movement and other types of commands within the same bind script.

USING POWEXEC_TOGGLE

The second way to create multiple command toggle binds is to string together a series of powexec_toggleon commands in the bind script (eg., /bind <key> powexec_toggleon D$$powexec_toggleon C$$powexec_toggleon B$$ powexec_toggleon A). Powexec_toggleon commands only turn powers on and can not turn off a power. Conversely, powexec_toggleoff only turns powers off.

With the powexec_toggleon command we can successively turn on several powers using only one key, but with multiple key presses. The bind will execute each command from right to left. Upon the first key press, the bind will attempt to activate power A. Upon the second key press, power B will activate. Upon the third key press, power C, and so on. Powexec_toggleon will IGNORE powers that are already on, and will seek out the next non-active power from the beginning of the chain onward with each successive key stroke. If all of the powers in the bind string are already on, no action will be taken. In addition, it appears that powexec_toggleon follows the same power activation sequence as powexec_name, with the one exception that it will not turn powers off.

Powexec_toggleon makes turning on powers using only one key much easier. Before this command existed, the only way to have one key turn on multiple toggle powers was to create a text/toggle bind that required the creation of multiple text files to operate. With this command, one bind will do it all! In addition, in some cases we may only want the bind to turn on the power so that we may turn the power off manually. In others we may use the powexec_toggleon to ensure that a toggle power is not turned off accidentally.

The corresponding command, powexec_toggleoff, works in a slightly different way. If a string of powexec_toggleoff commands are used in a single bind, the bind will turn off ALL powers in the bind script almost simultaneously. Powexec_toggleoff will never turn on a power, but will only turn powers off. The bind will also IGNORE all powexec_toggle commands for powers that are currently off, and search for the first active power from the beginning (right) of the bind string to turn off.

This feature to ignore command entries depending upon the on/off state of a power can cause some confusion if both powexec_toggleon and powexec_toggleoff are used together in the same bind. Consider this bind, for example:

/bind <key> powexec_toggleon A$$powexec_toggleoff A

This bind behaves similarly to a typical one power powexec_name bind, yet the way the commands are arranged is not at all like we would expect a powexec_name bind to look like. We might think that toggle_ON should swap places with toggle_OFF for the bind to work properly (and indeed it will work fine this way). However, because powexec_toggleoff ignores powers that are already turned off, the first command in the bind string is skipped over (assuming the desired power is already off before the bind is executed) and the next command in the string (toggle_on) is run instead. This means that when the bind key is first pressed, it will amazingly turn the power ON.

COMBINING POWEXEC_NAME and POWEXEC_TOGGLE

Multiple powexec_name and powexec_toggleon commands may be combined in the same bind. Mixed binds will operate in the same manner as described for the powexec_name command above from right to left, with the same base power activation sequence. The only difference, and its a big difference, is that powers turned on with the powexec_toggleon command will remain ON, while the powers activated with powexec_name will toggle on and off. Also powexec_toggle commands may be ignored in the bind depending upon the on/off state of the power.

This makes for some interesting possibilities. For example, with the following bind we can turn two powers on, and then toggle on and off between the last two powers (C and D) instead of the first two (A and B) as is usually the case:

/bind <key> powexec_name D$$powexec_name C$$powexec_toggleon B$$powexec_toggleon A.

The reason this works is because the bind will ignore any instances of powexec_toggleon whose powers are already on. So once powers A and B are turned on, the bind treats power C as if it were the first command in the bind string. This is also true for powexec_toggleoff, except it ignores powers that are already off rather than on.

USING TOGGLE KEYS

Toggle Keys, for lack of a better name, are already part of City of Heroes. We use them whenever we press the movement direction keys W, A, S, D, X; the space bar, the LAlt and LControl keys, and many others. A toggle key executes every command in a bind upon key PRESS, and then executes every command in the bind again upon key RELEASE. A toggle key is created by adding the + prefix command at the beginning of a bind string (eg., /bind <key> + $$powexec_name B$$powexec_name A). Notice there is a space between the + and $$. Without the space, the toggle key function will not work. In addition, any movement or similar command that includes a + at the beginning will also cause the key to behave as a toggle key if it is placed as the first command in the bind string (eg., /bind <key> +up$$powexec_name B$$powexec_name A).

In the bind above, Jump (the +up command) and power A will be activated when the key is PRESSED (and will continue to activate until the key is released). When the key is RELEASED Jump and power A will be turned off, and power B will turn on. Powers A and B toggle on and off between each other because of the toggling rule and power activation sequence of the powexec_name command (see above).

Instead of a + tag, a toggle key can also be made with a positive and negative movement command placed at the beginning of the bind string (eg., /bind <key> +down$$-down$$powexec_name A). The +down adds the functionality that causes the key pressed to be executed on both press and release, the -down ensures that it does not actually cause movement.

When the prefix ++ is used with a command at the beginning of a bind string (eg., /bind <key> ++forward$$powexec_name B$$powexec_name A), it serves to turn the toggle key function OFF. This means that the bind string will only be executed once per keystroke, and will not be executed upon key press and again upon key release.

Toggle keys help by allowing us to activate powers quicker, using less keystrokes. For example, a bind using 6 powexec_toggleon commands would take 6 keystrokes to turn all the powers on. However, adding + at the beginning of the bind would allow us to turn on all 6 powers in only 3 keystrokes because the bind is executing twice per keystroke (once when the key is pressed, and again when the key is released).

There is one caveat, however. When using toggle keys, it is important to make sure that you dont press and release the key too quickly. A very fast keystroke will sometimes cause the game to run the commands at key press and key release at the same time, essentially tacking on the same set of binds at the end of the original and treating the whole thing as one bind. Also, client-server-client lag (delays when your computer attempts to communicate with the games server, and visa versa) can cause similar errors.

TOGGLE KEY TEXT BINDS

Perhaps the most confusing, but also the most valuable, function for toggle keys is when they are used in combination with the bind_load_file command to create toggle key text binds. Toggle/text binds were explained fairly well in Curveballs Guide to Bind in his Using Toggle Binds section. What adding the + tag to the beginning of toggle/text binds does is to allow us to execute one bind string residing in a specific text file on key press, and then another bind string from a different text file on key release. With this, we can often circumnavigate around limitations placed on us by the game, and execute commands in combination that otherwise would be impossible.

For example, say you wanted your super hero to simultaneously leap into the air with a jump, turn on Fly with the F key, and make sure Sprint is turned off; but you ALSO wanted to be able to turn Fly off and Sprint on with a second stroke of the SAME key. Using a toggle key text bind we can create a bind that works in the desired manner, such as this bind below:

FLY1.TXT:
f "+up$$powexec_toggleon fly$$bind_load_file c:\[file location]\fly2.txt"

FLY2.TXT:
f "+up$$powexec_toggleoff sprint$$bind_load_file c:\ [file location]\fly3.txt"

FLY3.TXT:
f "+down$$powexec_toggleon sprint$$bind_load_file c:\ [file location]\fly4.txt"

FLY4.TXT:
f "+down$$powexec_toggleoff fly$$bind_load_file c:\ [file location]\fly1.txt"

The above toggle key text bind will execute the first bind (fly1.txt) and load the second on the key press, and execute the second bind (fly2.txt) and load the third on the key release. Then it will execute the third bind (fly3.txt) and load the fourth on the second key press, and execute the fourth bind (fly4.txt) and load the first bind again on key release looping back to start over again. This simulates an on/off toggle key for two powers (Fly and Sprint), something impossible to do without toggle key text binds.

Notice that in each bind above there is a + tag. Without a + tag or a place holder at the beginning of every other bind (the bind executed on key release), the toggle key function will not work. Instead of a + tag at the beginning of the second bind, a place holder consisting of a blank space after the first quotation mark and before the first command separator ($$) can often suffice IF only + is used alone in the previous bind string and not attached to a movement command. For example:

TEXTBIND1.TXT:
Y "+ $$powexec_name A$$bind_load_file c:\[file location]\textbind2.txt"

TEXTBIND2.TXT:
Y " $$powexec_name B$$bind_load_file c:\ [file location]\textbind1.txt"

This method of creating a toggle key can cut down or reduce the number of characters used in a bind, and also allows us to create a toggle key without movement commands mucking up the works but dont forget the blank space before the first $$ command separators for each text bind or this toggle key arrangement will not function properly.

UNDERSTANDING MULTIPLE POWEXEC COMMANDS FOR THE SAME POWER

Multiple powexec_name and powexec_toggle commands for the SAME POWER can cause some baffling results, behave contrary to the normal bind rules, and lock up a bind so that it no longer works. Believe it or not, these quirks can actually come in handy when trying to design a bind that works the way we want it to work. More importantly, understanding how multiple powexec commands for the SAME POWER affect binds is crucial for understanding how some binds behave when executed under less than optimal conditions, such as when lag is affecting game play or when a bind key is pressed too quickly. Under these poor conditions, entire bind strings are often duplicated and treated as one bind or separate toggle/text binds merged so that we end up executing multiple commands for the same power.

In most cases when two or more powexec commands for the SAME POWER are executed in a bind, a conflict between the commands takes place. The duplicated power briefly turns on, turns off, and then defaults to an ON state. When such a conflict occurs, it prevents any other powexec commands in the bind from operating. Of course, whether or not this command conflict occurs depends upon the specific combination of powexec commands and their position or sequence in the bind string upon execution. For example, combining a powexec_NAME <same power> command with a powexec_TOGGLEOFF <same power> command will have a different result than combining two powexec_NAME <same power> commands.

For ease of use, A will represent the duplicated power. I will give an example bind showing the combination and sequence of commands, and then an explanation of the binds behavior:

/bind <key> powexec_NAME A$$powexec_NAME A
When two or more powexec_name commands for the SAME POWER are used in a bind (eg., /bind Y "powexec_name Super Jump$$powexec_name Super Jump), the power will be turned on if it was not already active. However, the bind will not turn the power off if the bind key is pressed again. The usual command to turn off all the powers in the bind string executes first (and the power turns off briefly as well as any other powers in the bind string), but then a command to turn on the power occurs second almost instantly. This happens ONLY if the command to turn on the first duplicated power is executed in the bind string, following the normal power activation sequence described previously. It also does not matter where the second instance of powexec_name <SAME POWER> is located in the bind string for this phenomenon to occur. Further, once powexec_name <SAME POWER> is executed, the bind will prevent all other powers in the bind from executing and the bind will essentially lock up. For example, the following bind will ONLY execute Fly, will never turn it off, and will never toggle on Stealth (contrary to the normal bind rules): /bind Y powexec_name Fly$$powexec_name Stealth$$powexec_name Fly.

/bind <key> powexec_TOGGLEON A$$powexec_TOGGLEON A
This bind above seems to behave normally, as if there was only one powexec_toggleon command. Multiple instances of powexec_toggleon <same power> do not seem to interfere with the binds operation, and the additional commands appear to be ignored.

/bind <key> powexec_TOGGLEOFF A$$powexec_TOGGLEOFF A
This bind above behaves differently depending upon the on/off state of the power. If the power is already OFF, the bind will do nothing and the commands appear to be ignored. However, if the power is already ON, then the bind will behave as two powexec_NAME <same power> commands it will NOT turn the power off, and will prevent any other powexec commands in the bind string from executing. The powexec_toggleoff <same power> commands can be placed ANYWHERE in the bind string, but one of the commands must be executed for this behavior to occur (following the power activation sequence for multiple command binds previously described above).

/bind <key> powexec_TOGGLEOFF A$$powexec_TOGGLEON A
This bind will toggle the power on and off, and seems to behave normally according to the power activation rules for powexec_toggleon/off commands

/bind <key> powexec_TOGGLEON A$$powexec_TOGGLEOFF A
This bind will toggle the power on and off, and seems to behave normally according to the power activation rules for powexec_toggleon/off commands.

/bind <key> "powexec_NAME A$$powexec_TOGGLEON A"
This bind above will turn power A on, and then toggle it off upon the next key press in short, the one instance of powexec_name <same power> within the bind negates the ability for powexec_toggleon to keep a power on. The powexec_name command does not need to be right next to the powexec_toggleon command for this to happen. It can be placed ANYWHERE in the bind string and this toggling on/off behavior will still occur. For example, /bind <key> powexec_name Fly$$powexec_name Unyielding$$powexec_name Invincibility$$powexec_toggleon Fly. This bind will turn Fly on and off, while toggling between Fly and Invincibility. However, if two instances of powexec_name <same power> are placed in the bind, and one of the commands executed, the bind will turn on the power and keep it on, ignoring all other powers in the bind string.

/bind <key> "powexec_TOGGLEON A$$powexec_NAME A"
This bind will toggle power A on and off. In short, the powexec_toggleon command is ignored. If a powexec_toggleon <same power> command appears elsewhere in the bind, it will not affect its operation.

/bind <key> "powexec_TOGGLEOFF A$$powexec_NAME A"
This bind above will turn power A on, keep it on, and will never turn it off. It behaves exactly as if two powexec_name commands for the same power were placed in the same bind. The powexec_toggleoff <same power> command can occur ANYWHERE in the bind string and this behavior will still take place, but only if powexec_name <same power> is the first command in the string. Further, this combination prevents all other powers in the bind string from executing. For example, this bind will only turn Super Jump on: /bind Y " powexec_name unyielding$$powexec_toggleoff super jump$$powexec_toggleon temp invulnerability$$powexec_name super jump".

/bind <key> "powexec_NAME A$$powexec_TOGGLEOFF A"
This bind will turn power A on and keep it on. It behaves very similarly to when two powexec_name commands for the same power are placed in a bind. However, this only occurs if the powexec_name <same power> command is executed in the bind string, following the normal power activation sequence for powexec commands. Otherwise, the bind will behave normally.

In any bind string that has two commands that would create a conflict when executed, a conflict will occur regardless of what other powexec <same power> commands reside in the bind string. For example, when powexec_NAME <same power> and powexec_TOGGLEON <same power> are combined, the bind will function normally. But if you add another instance of powexec_NAME <same power>, a conflict will result when the command is executed, turning the power on and locking up the bind:

This bind will operate normally:
/bind Y "powexec_TOGGLEON fly$$powexec_NAME fly"

But this bind will create a conflict:
/bind Y "powexec_NAME fly$$powexec_TOGGLEON fly$$powexec_NAME fly"

When a conflict between two powexec commands for the same power occurs, it can often have a side effect of slowing down the execution of a power, sometimes enough to allow a different type of command (such a movement command) to execute before the power does. This might be useful in some bind applications.

MOVEMENT DIRECTION COMMANDS

The movement direction commands are actually toggles (eg., +forward, +backward, +left, +right, +up, etc.). This means that when a direction command is issued, it will stay on until the command is issued again to turn it off. In game, these commands appear to be special commands turning on during key press, and off upon key release but what is really happening is that the movement command executes upon key press (turning on the power), and then executes the same command again upon key release (turning off the power) in short, utilizing the + prefix or toggle key function.

The ++ prefix, on the other hand, serves to turn the toggle key function OFF. When used with a movement command (eg., ++forward, ++backward, ++left, etc.), the prefix will cause the command to be toggled ON, and will continue to activate, until the button is pressed again, toggling it off.

Anything you can toggle (using ++ or +/-) you can explicitly turn on or off by adding the argument 1 (on) or 0 (off) after them (eg., /bind Y up 1$$powexec_name). For most commands that take a numeric argument (including the toggles), you can check the current value by issuing the command without any arguments.

CLICK POWER BINDS

Click powers can be executed using any of the powexec commands. As indicated by Curveballs Bind Guide, only one click power can be activated at a time (unless powexec_auto is also used to activate a second click power). A mixed click and toggle bind will pretty much behave as a normal toggle bind as described above with one big exception when a click power is executed a second time, the click power will either be activated or queued up to be activated once it has recharged and NOT toggled on and off. This means that if a click power is placed as the first power to activate in a bind string, no other powers will be executed (excepting powexec_auto), no matter how many times the bind key is pressed. For example:

/bind <key> powexec_name TOGGLE$$powexec_name TOGGLE$$powexec_name CLICK

This bind above will only execute the click power. Therefore, its usually best to place a click power command after all of the toggle power commands in the bind string or at least somewhere other than at the beginning of the string so that toggle powers have a chance to execute before the click power.

USING POWEXEC_AUTO

This command only works for click powers, and will not work for toggle powers. Essentially, powexec_auto sets a click power on auto-fire allowing the click power to activate automatically upon recharge until auto-fire is deselected. This command toggles auto-fire on and off, and can be placed ANYWHERE in the bind for it to work. However, if more than one powexec_auto command is included in a bind string, the command will only turn auto-fire on, and will NOT turn auto-fire off. As with other powexec commands, powexec_auto command is executed from right to left in the bind string (eg., /bind Y powexec_auto D$$powexec_auto C$$powexec_auto B$$powexec_auto A). So in unlikely cases where multiple powexec_auto commands are used together, only the first power (A) will be set on auto-fire. This may be useful to avoid turning auto-fire off if the same bind key is pressed again. In addition, if two powexec_auto commands are used for the SAME POWER in a bind (eg., powexec_auto Gash$$powexec_auto Gash), they will cancel each other out and prevent the command from executing (neither turning auto-fire on nor off).

When powexec_auto is used in the same bind with either powexec_name or powexec_toggleon/off, it will execute on every keypress regardless of its location in the bind string. However, it is a best practice to place powexec_auto commands at the end of the bind string, after all other powexec commands have had a chance to execute in order to avoid any potential power activation problems. (eg., /bind <key> powexec_auto D$$powexec_name C$$powexec_name B$$powexec_toggleon A)

TURNING POWERS OFF

Besides the normal ways to toggle powers off using powexec_NAME and powexec_TOGGLEOFF commands, powers can also be turned off by adding the following commands to the beginning (right) of a bind string:

Powexec_unqueue -- cancels a queued power. It will also turn off any powers that are included in the same bind string, as long as the powexec_unqueue command is executed in the bind following the normal power activation sequence. So the best place to put the command, if you want to turn powers off, is at the beginning of the bind string (from right to left) to make sure its activated, like so: /bind Y powexec_name invincibility$$powexec_name unyielding$$powexec_name fly$$powexec_unqueue This bind will only turns the powers off, and will not turn them on. When used with powexec_toggleon, the unqueue command will cause the bind not to function. When used with the powexec_toggleoff command, the unqueue command will turn off all powers and cancel queues.

Powexec_abort -- cancels the auto-attack power and the queued power. It behaves exactly like powexec_unqueue above, including turning powers in the bind string off, as well as canceling queues and auto-fire.

ARRANGING YOUR BIND COMMANDS

Types of powers/commands:

Click Power Command -- attacks, inspirations, various powers such as Build Up, Hasten, etc.
Toggle Power Command -- powers that toggle on and off, such as Fly, Super Jump, Temporary Invulnerability, etc.
Movement Command -- +up, +down, +forward, +backward, +left, +right. +turnright, +turnleft, +autorun
Emotes -- animated movements such as wave, bow, grief, etc.
Text Message Commands -- tell, team, local, broadcast, etc.
Variables -- $target, $name, $origin, $archetype, $level, $battlecry
File Loading Commands -- bind_load_file
Miscellaneous -- costume (cc 0, cc 1, etc.), map, chat, sgmode, follow, target_enemy_near, etc.

The order or sequence in which you arrange command types in your bind strings is crucial for the proper operation of your bind. If you were paying attention while you were reading this guide, youd already know most of what Im about to explain. Of course, arranging your bind commands in the order I am about to suggest is not, usually, a rule set in stone. You are free to experiment with different arrangements, many of which I suspect would work fine. Keep in mind that bind strings are executed from right to left. The following is an example bind with the preferred parsing:

/bind Y +forward$$CC 0$$team I am ready now, $target.$$emote thumbsup$$powexec_auto Gash$$powexec_name Dark Blast$$powexec_name Fly$$bind_load_file C:\[file location]\ready.txt

Rewriting the bind above using the command types would look like this:

/bind Y MOVEMENT commands$$MISCELANEOUS commands$$TEXT commands$$EMOTE commands$$AUTO-FIRE commands$$CLICK POWER commands$$TOGGLE POWER commands$$FILE LOADING commands

Having File Loading commands execute first, before any of the other commands, helps ensure that the new text bind is loaded. Remember, the very first command from the right is the command that will be executed first.

Next comes toggle power commands such as powexec_toggleon and powxec_name. These come before click power commands so they will activate.

Then comes click power commands because no toggle power command will active after a click power has activated.

After this comes auto-fire commands so they do not interfere with click or toggle power execution.

Emotes are then executed because their animations take time to process.

Text and Miscellaneous commands take no time to execute, so these are placed last to minimize their interference with other commands, but really can be placed anywhere in the bind string.

Movement commands can be placed elsewhere in the bind string, but if you want the toggle key function to be activated with the command, the movement power must be placed at the end (far left) of the bind string so that the + prefix activates the toggle key function.

DEALING WITH LAG

Unfortunately, we all will encounter LAG at one time or other while playing COH, so saying a few words about how LAG adversely affects binds and what we can do to adjust our binds to ensure they operate correctly is probably worthwhile. This is especially true for me, since Ive been playing with a low speed 56k dial-up connection. Lag seems to affect the operation of my binds far more than others who are on a broadband connection.

Lag occurs when the games computer (server) is having trouble communicating with your computer (client), and visa versa. There can be pauses, hiccups, and slowdowns in bind execution; and sometimes a bind might not execute at all. I am certainly no expert on this subject, but three things appear to happen to binds during lag:

1) the bind is duplicated and run as if the two bind strings were actually one bind string,
2) the bind is truncated and/or only partial commands are communicated to the server, or
3) the bind or part of the bind is delayed in executing.

In my experience, the most common bind error when executed under lag conditions is that the bind string is duplicated, tacked onto the end of the first bind string, and then executed as one bind string. This happens most often with toggle key binds. So a bind such as this one:

/bind Y +up$$powexec_name Sprint$$powexec_name Fly

might be turned into a bind string that looks something like this one during lag conditions:

/bind Y +up$$powexec_name Sprint$$powexec_name Fly$$+up$$powexec_name Sprint$$powexec_name Fly

The double movement commands (+up) would have no affect on the operation of the bind, but the twin instances of powexec_NAME Fly would cause a command conflict and the bind would malfunction (see the section UNDERSTANDING MULTIPLE POWEXEC COMMANDS FOR THE SAME POWER above).

This duplication of bind strings during lag occurs mostly for binds that utilize the toggle key function, where the bind is executed on key press, and then executed again on key release. In addition, toggle key text binds that load multiple binds from text files add a layer of complexity to this problem that can be very confusing.

My guess (and it is only a guess) about what is really happening behind the scenes with toggle keys and lag is that when the bind key is pressed and released, the game attempts to execute the bind but communication fails between the client/server, and the command is not processed. Instead, the first set of commands issued on key press and the second set of commands issued on key release are stored in a queue, waiting to be executed when communication is re-established. Once communication is resumed, the game runs both bind strings at the same time as one bind.

When designing or troubleshooting a toggle key bind, its important to take into consideration the possibility that the bind may be duplicated sometime during game play. Creating binds that, if duplicated, will not cause same-power command conflicts is easier said than done, however. Whether or not a command conflict occurs depends on the specific commands used in the bind as well as their sequence in the bind. Your best bet would be to look at the UNDERSTANDING MULTIPLE POWEXEC COMMANDS FOR THE SAME POWER section above, and see what would happen if any of your toggle key binds were duplicated, and then experiment with different command arrangements that might not cause conflicts if repeated. There is, however, one saving grace here. Duplicate instances of the powexec_TOGGLEON <same power> command will not cause conflicts, so whenever possible use powexec_toggleon to turn on powers instead of powexec_name.

The second thing that might happen during lag is that a bind command (or the bind string) may be truncated because of loss of communication. For example, powexec_name Unyielding might be truncated to powexec_name Unyieldi or powexec_na or pow. Truncated or partial commands will be ignored by the game, so it might mess up your power activation sequence (which power activates when). Otherwise, partial commands really dont cause any trouble, they simply will not function is all.
The best bet to try to avoid this is simply to use multiple powexec_toggleon <same power> commands to make sure that at least one of the complete commands is executed. Unfortunately, duplicating other powexec commands in a bind might cause problems, depending upon the specific commands used in the bind and their location in the bind string.

The third thing that happens to binds during lag is that delays in power activation occur. You might press a key, and some commands may be executed, but a power may not turn on except after a lengthy pause. I dont know why it works, but Ive found that adding at least two powexec_toggleon <same power> commands to a bind string tends to eliminate power activation delays in binds. For example, /bind Y +up$$powexec_name Sprint$$powexec_toggleon Fly$$powexec_toggleon Fly.

Level 50s:
BlackSpectre, Dark Defender (Guardian)
Thorin, Invul/Axe Tank (Justice)
Volcano Juice, Fire/Stone Tank
Professor ?, Mind/FF Controller
Stone Forge, Stone/Fire Tank

CaptA · 02-04-2006 05:06 PM

Wow. Nice job!

"...freedom isn't a commodity to compromise." -- Captain America, New Avengers #21

Guide to Base Teleporters

Dant3 · 02-04-2006 06:52 PM

I must be missing something here - I've read through Screwball's guide AND this one but I can't seem to get a toggle to work for CoF.
I have set up a bind that makes CoF activate, and local message "Fear Me!" display,

CTRL+5 "+ $$local FEAR ME!$$powexec_name cloak of fear$$bind_load_file c:\Program Files\City of heroes\dantekeybinds2.txt"

with an additional file (dantekeybinds2.txt)

CTRL+5 + $$powexec_toggleoff cloak of fear$$bind_load_file c:\Program Files\City of Heroes\dantekeybinds1.txt

which I would like to turn off CoF, without repeating the local message.
Problem is - it doesn't work. CoF deactivates but displays local message again - I'm guessing it's something to do with the bind load command in the first txt file?

Black_Specter · 02-04-2006 07:18 PM

Dant3,

I'm not on the Forums much, so this was not intended to be an "Ask the Expert" thread. In fact, I'm hoping my guide will let everyone troubleshoot their own binds.

Try getting rid of the "+ " prefix in both text files so the bind will only execute once upon each keystroke, rather than twice -- once on key press and once again on key release. You don't need the toggle key function to use text/toggle binds.

Level 50s:
BlackSpectre, Dark Defender (Guardian)
Thorin, Invul/Axe Tank (Justice)
Volcano Juice, Fire/Stone Tank
Professor ?, Mind/FF Controller
Stone Forge, Stone/Fire Tank

Black_Specter · 02-05-2006 11:42 AM

Got to thank Dant3 for posting his question. I didn't think it was necessary to repeat what Curveball said about text/toggle binds in his guide. But if people have difficulty understanding something about binds even after reading both Curveball's and my guide... perhaps I should put some additional things in the guide?

Please let me know if everything makes sense, or if there is something you don't understand that I didn't address. I'll do my best to help out. Also I'll write up a revision of my guide and re-post it with credit and gratitude to you.

Also, although I really hope this guide is useful, feel free to let me know if you feel it's not very helpful. Please let me know what I can do to improve it, if anything, or if you think it's great as is?

All the best,

BlackSpectre

Level 50s:
BlackSpectre, Dark Defender (Guardian)
Thorin, Invul/Axe Tank (Justice)
Volcano Juice, Fire/Stone Tank
Professor ?, Mind/FF Controller
Stone Forge, Stone/Fire Tank

Innovator · 02-05-2006 01:44 PM

Nice job! Very informitive!

Gaean_Conspiracy · 02-06-2006 10:30 AM

I've found using toggleon/toggleoff in togglekey binds to execute inconsistently. For example:

file1 (c:\cohkb\HoverSS\SP\0.txt)
BUTTON4 "+ $$forward 0$$backward 1$$up 0$$down 0$$mouselook 1$$powexec_name SPRINT$$powexec_name SPRINT$$bindloadfile c:\cohkb\HoverSS\SP\B.txt"

file2 (c:\cohkb\HoverSS\SP\B.txt)
BUTTON4 "+ $$forward 0$$backward 0$$up 0$$down 0$$powexec_toggleoff SPRINT$$bindloadfile c:\cohkb\HoverSS\SP\0.txt"

Those binds are supposed to on press force sprint on and start moving forward and on release turn sprint off and stop all movement; however, while turning sprint on upon keypress works fine, turning sprint off upon keyrelease often fails although movement does stop.

I don't quite see how lag induced truncation or duplication could explain this, except perhaps if the 2 binds were combined; thereby, making the duplicate powexec_name SPRINT invocations fail the powexec_toggleoff SPRINT.

Note that either of the following in file2 work fine, with the later being better, but causing weapons to be sheathed:
BUTTON4 "+ $$forward 0$$backward 0$$up 0$$down 0$$powexec_name SPRINT$$bindloadfile c:\cohkb\HoverSS\SP\0.txt"

BUTTON4 "+ $$forward 0$$backward 0$$up 0$$down 0$$powexec_name SPRINT$$unqueue$$bindloadfile c:\cohkb\HoverSS\SP\0.txt"

It might also be worth noting that the two files actually contain a whole set of about a dozen keybind which might accentuate lag issues slightly.

Golden_Ace · 02-06-2006 11:13 AM

Great, now i've got to put another file on my favorit's list.

One thing. You might want to post a link to all known slash commands.

I use this link but it's old and out of date. I have not found a new one yet.

Slash Commands A to Z

Great Guide! Good Job!

[color=gold][b][size=5]♪ Sometimes you feel like a Tank, Sometimes you don't! ♪[/size][/color][/b]

[url=http://boards.cityofheroes.com/showthread.php?t=114726][color=black][b][size=5]Moon [color=red]Hazard [color=black]Zone![/size][/color][/color][/color][/b][/url]

Black_Specter · 02-07-2006 09:35 PM

Gaean_Conspiracy,

[ QUOTE ]
I don't quite see how lag induced truncation or duplication could explain this, except perhaps if the 2 binds were combined; thereby, making the duplicate powexec_name SPRINT invocations fail the powexec_toggleoff SPRINT.

[/ QUOTE ]

Right. This is EXACTLY what is happening.

The problem is the command conflict that is caused by the twin instances of powexec_name Sprint in your first text file. They will force the power to turn on and not turn off... and if the two text file binds are executed as one bind string, then the conflict will take precidence over the powexec_toggleoff... and keep the power on. So the inconsistancy is pretty much explained right there.

When the key is pressed too quickly or there is lag, the two bind files will be merged and will not behave correctly. When the key is not pressed too quickly, or there is not lag, then the bind should behave appropriately for the most part... I say for the most part becaues the two instances of powexec_name <same power> are still creating a command conflict that may not be able to be resolved by the time the second text file bind is executed upon key release.

When dealing with toggle key text binds, the bind string in each text file is not duplicated, instead the bind string in the first text file is merged with the bind string in the second text file, and they are executed as if they were one long bind string.

My recommendation... replace the powexec_name commands with powexec_toggleon commands.

Let me know if this works.

Level 50s:
BlackSpectre, Dark Defender (Guardian)
Thorin, Invul/Axe Tank (Justice)
Volcano Juice, Fire/Stone Tank
Professor ?, Mind/FF Controller
Stone Forge, Stone/Fire Tank

Black_Specter · 02-07-2006 09:51 PM

[ QUOTE ]
Great, now i've got to put another file on my favorit's list.

[/ QUOTE ]
Thanks, man! That's a REAL compliment!

[ QUOTE ]

One thing. You might want to post a link to all known slash commands.

I use this link but it's old and out of date. I have not found a new one yet.

[/ QUOTE ]

Well, I thought of that. On the second page of Curveball's Bind Guide (there's a link at the beginning of my guide) he lists not only a list of all slash commands (slightly out of date), but also the DEFAULT key binds of all keys used by the game! An invaluable resource!

That said, I was thinking about including a complete list, but I knew that any list would become obsolete fairly quickly with susequent updates, so instead I gave everyone a way to get their own, CURRENT, COMPLETE, and UP TO DATE list of slash commands by typing in /cmdlist into their text box.

The slash command list currently used by the game pops up in the global box, and you can copy this to the clipboard using the /copychat_global command, and then paste it into a word processing file for your future reference.

This way everyone can stay up to date on their own without relying the the kindness of strangers in the Forum.

Level 50s:
BlackSpectre, Dark Defender (Guardian)
Thorin, Invul/Axe Tank (Justice)
Volcano Juice, Fire/Stone Tank
Professor ?, Mind/FF Controller
Stone Forge, Stone/Fire Tank

Local_Man · 02-08-2006 02:31 PM

This is a really nice advanced guide . . . and I plan to print it out and use it -- a lot. Added to Favorites!

I love using binds, especially when I get responses like, "How did you do that so fast?"

LOCAL MAN! The most famous hero of all. There are more newspaper stories about me than anyone else. "Local Man wins Medal of Honor." "Local Man opens Animal Shelter." "Local Man Charged with..." (Um, forget about that one.)
Guide Links: Earth/Rad Guide, Illusion/Rad Guide, Electric Control

Gaean_Conspiracy · 02-10-2006 09:02 AM

I tried replacing all of the powexec_name SPRINT commands with powexectoggle_off/_on SPRINT and the results were terrible. What seems to work pretty well is using powexectoggle_on to turn sprint on and just powexecname to turn them off. I suspect that putting a unqueue after powexec_name SPRINT would be even more effective, but that would cause weapon redraws.

Black_Specter · 02-11-2006 06:16 PM

[ QUOTE ]
I tried replacing all of the powexec_name SPRINT commands with powexectoggle_off/_on SPRINT and the results were terrible. What seems to work pretty well is using powexectoggle_on to turn sprint on and just powexecname to turn them off. I suspect that putting a unqueue after powexec_name SPRINT would be even more effective, but that would cause weapon redraws.

[/ QUOTE ]

Well, I'm glad you found an arrangement that works. Binds are quirky, especially when executed under poor conditions.

Level 50s:
BlackSpectre, Dark Defender (Guardian)
Thorin, Invul/Axe Tank (Justice)
Volcano Juice, Fire/Stone Tank
Professor ?, Mind/FF Controller
Stone Forge, Stone/Fire Tank

Black_Specter · 02-12-2006 12:53 AM

Oop! Just noticed I made a mistake on the previous page of posts... the command to copy the global chat is not "/copychat_global" but rather "/copychat global". Sorry, about the silly underscore typo.

I HAVE revised this Advanced Bind Guide a bit already. I've added a bit about text binds, and another bit about clearing binds from keys, as well as clarified some language in the LAG section to make it less confusing and more accurate.

Should I just post the additions here, or create a new thread when I'm finished with the whole revision?

Level 50s:
BlackSpectre, Dark Defender (Guardian)
Thorin, Invul/Axe Tank (Justice)
Volcano Juice, Fire/Stone Tank
Professor ?, Mind/FF Controller
Stone Forge, Stone/Fire Tank

Innovator · 02-12-2006 01:08 AM

If you do repost, I just noticed one fix that's needed. Change all open and close quotes (ie and ) to just a standard quote ("). Binds using the former will not work. To fix, after typing in Word, cut and paste to notepad and do a search and replace for those quotes that Word places.

Black_Specter · 02-12-2006 12:15 PM

[ QUOTE ]
If you do repost, I just noticed one fix that's needed. Change all open and close quotes (ie and ) to just a standard quote ("). Binds using the former will not work. To fix, after typing in Word, cut and paste to notepad and do a search and replace for those quotes that Word places.

[/ QUOTE ]

Oh, wow! Look at that. In the past, HTML and forums wouldn't take those open and closed quotes, and changed them to standard ones... guess times are a'changing.

Thank you again, Innovator!

Level 50s:
BlackSpectre, Dark Defender (Guardian)
Thorin, Invul/Axe Tank (Justice)
Volcano Juice, Fire/Stone Tank
Professor ?, Mind/FF Controller
Stone Forge, Stone/Fire Tank

Baneful · 02-14-2006 02:55 AM

LoL i was gonna say "i didnt even know you could do "open" and "closed" Quotes..."

The Official Resident Fanboi of dUmb
Always Allow/Disallow Mystic Fortune Prompt!

PCSAR

judgestarx · 02-22-2006 01:56 PM

nice guide!

Uknee · 02-22-2006 02:02 PM

Dig it gonna try some of these out.

Fire_Storm · 03-05-2006 09:41 PM

Man, you are the bomb.

I use cutom key mapping anyway. I put all my powers in the right hand typing area.

Your binds work for macro too. My fire/fire tanker now uses this bind...(if i didn't make a typo for it)

/Macro On "powexec_name Blazing Aura$$powexec_toggleon Acrobatics$$powexec_toggleon Combat Jumping$$powexec_toggleon Plasma Shield$$powexec_toggleon Tough$$powexec_toggleon Fire Shield"

now i turn on weave and toggle BA off and on. It is so easy now.

You are the bomb. I am now lookng to see what this gude will do with swaping trays and what not.

GREAT GUIDE!

Thnx

RogueDemonhunter · 03-05-2006 09:47 PM

Good work. Now if I can just get off my butt and take the time to actualy apply some of these...

Thanks,

Rogue Demonhunter

Black_Specter · 03-06-2006 11:21 PM

Thanks for the compliments, guys! I'm glad some of this stuff was useful.

I polished and added a few things to this Advanced Bind Guide and have reposted it here as ADVANCED BIND GUIDE v1.1 .

Hopefully this second draft is clearer and easier to understand. The additional material deals with how to clear binds from keys, a new section on text binds, and a couple other small, but important things. I expect (and hope) v1.1 of this guide to be the final draft.

As an aside, yeah, the bind rules apply to macros as well. A little trick I learned regarding key binds and macros, is that you can bind a macro to a key, or rather have a key bind execute a macro by using the powexec_tray command.

Level 50s:
BlackSpectre, Dark Defender (Guardian)
Thorin, Invul/Axe Tank (Justice)
Volcano Juice, Fire/Stone Tank
Professor ?, Mind/FF Controller
Stone Forge, Stone/Fire Tank

American_Valor · 03-16-2006 02:49 PM

[ QUOTE ]
Man, you are the bomb.

I use cutom key mapping anyway. I put all my powers in the right hand typing area.

Your binds work for macro too. My fire/fire tanker now uses this bind...(if i didn't make a typo for it)

/Macro On "powexec_name Blazing Aura$$powexec_toggleon Acrobatics$$powexec_toggleon Combat Jumping$$powexec_toggleon Plasma Shield$$powexec_toggleon Tough$$powexec_toggleon Fire Shield"

now i turn on weave and toggle BA off and on. It is so easy now.

You are the bomb. I am now lookng to see what this gude will do with swaping trays and what not.

GREAT GUIDE!

Thnx

[/ QUOTE ]

Ok you might want to check those toggle up powers with your macro you might discover it only activating the last one in the series. Unless I7 made a change I don't know about and yes this is an awesome guide.

Remember Keep being a Hero

Valor

Quote:

by Star Ranger 4
WIN LOSE OR DRAW, WE WILL FIGHT.
WE ARE HEROES This is what we DO!

When you wake up seek the courage and strength to do the right thing.
Decide that this will be another day in which you Walk The Talk.

MA #14724 Operation: Discredit @American Valor
Sentinel Of Liberty SG

Innovator · 03-17-2006 08:02 AM

[ QUOTE ]
[ QUOTE ]
Man, you are the bomb.

I use cutom key mapping anyway. I put all my powers in the right hand typing area.

Your binds work for macro too. My fire/fire tanker now uses this bind...(if i didn't make a typo for it)

/Macro On "powexec_name Blazing Aura$$powexec_toggleon Acrobatics$$powexec_toggleon Combat Jumping$$powexec_toggleon Plasma Shield$$powexec_toggleon Tough$$powexec_toggleon Fire Shield"

now i turn on weave and toggle BA off and on. It is so easy now.

You are the bomb. I am now lookng to see what this gude will do with swaping trays and what not.

GREAT GUIDE!

Thnx

[/ QUOTE ]

Ok you might want to check those toggle up powers with your macro you might discover it only activating the last one in the series. Unless I7 made a change I don't know about and yes this is an awesome guide.

Remember Keep being a Hero

Valor

[/ QUOTE ]

Nothing seems to be wrong with his bind, it should work as he says it does. powexec_toggleon is a command that basically turns the power on if the power is off, otherwise the command ignored.

I Am Legend! (1601th post)

Golden_Ace · 03-17-2006 08:17 AM

[ QUOTE ]
I Am Legend! (1601th post)

[/ QUOTE ]

Gratz!

[color=gold][b][size=5]♪ Sometimes you feel like a Tank, Sometimes you don't! ♪[/size][/color][/b]

[url=http://boards.cityofheroes.com/showthread.php?t=114726][color=black][b][size=5]Moon [color=red]Hazard [color=black]Zone![/size][/color][/color][/color][/b][/url]