Namespaces

Variants
Views
Actions

Guide: Keybinds

From Star Trek Online Wiki
Jump to: ,

Contents

[] Simple Keybinding

Information on simple key binding and their functions can be found by following this .

[] Introduction

This article discusses both typing key binds into the local/chat window and editing the script in a bind file; however, it's primary focus is to enable the player to create a permanent file by which through editing one can have a permanent way to edit, save and restore scripts to make them permanent.

Following these steps, manipulating a bind file to add/remove becomes easy and enjoyable. This guide provides easy-to-read instructions to customize the gaming experience, regardless of experience level in coding and computers.

[] Considerations: Writing your scripted keybind file

Although this is a safe and recommended way to bind key combinations, there are a few things to consider:

  1. The system always works. However, if the syntax is wrong, the commands may not work as expected or at all.
  2. If the first character is not followed by a space, that will be ignored Ex: |Slipstream
  3. Writing the incorrect syntax will not break the game; however, it may show in the local/chat window the error 'Command not recognized'.
  4. If the binds get disarranged, simply use the "Reset to Default" in your Options:Key Binds menu, delete the bind-file and reload the game.
  5. Black box theory; as long as the syntax is correct and the command is recognized by the game: input equals output.
  6. Key binds aren't a hack and isn't considered cheating. They are an integral, and after making one, an essential part of the game.
  7. To ensure the key binds work in the order intended, due to timing constraints; you must pause between each keystroke, or if you wish to execute several keystroke rapidly you must list them in forward and reverse order. Example: A, B, C - may execute A, C, B; however by binding them thus: A, B, C, B, A, you ensure they execute A, B, C.
  8. Always include closing quote when binding multiple powers to a single key.
  9. Always include the separator $$ between multiple commands when binding multiple powers to a single key.

[] Rally Point Bug

  1. BOFF's ability to Set Rally Points is compromised if a script line contains a reference to "ContextAction 1" ex: Leftclick "ContextAction 1"

[] What is a key bind?

Like the Key bind ability found under Main Menu/Options/Key binds, Key binds are a shortcut for a predefined action assigned to a key on your keyboard; when pressed, it invokes an operation.

A keybind is also a scripted line in a text file which using STO's scripting language, proper format and syntax assigns a key to one or more than one predefined action. When loaded into the game from your computer, Pressing a key on your keyboard invokes one or more than one operation to occur in a predefined order.

Both methods produce keybinds; the details and limitations on how to accomplish this will be given below.

[] Why use key binds?

The purpose of a key bind is to provide a quick and efficient set of commands without the need for multiple key-presses. One example can be during combat; using multiple key-presses can limit the amount of space for skills due to keyboard limitations, whereas a customized bind could assign the same skills to one key.

The game parses multiple skills bound to a key faster than activating them separately. More seasoned players can remove debuffing skills on teammates with just one bind. By adding at least three seconds, the alternative is selecting a teammate and then activating the debuffing skill.

Key binds are essential to becoming a successful Starship Officer. Multiple key binds are essential to becoming a superior Starship Officer!

[] Definitions

This article contains lingo not familiar to all players. A legend has been provided:

  1. A "Key" is any button present on a keyboard that includes alphanumerical characters and function keys.
  2. A "Press" is the action of pushing and holding a key in the pressed position.
  3. A "Release" is the action of releasing a held key.
  4. A "Tap" is the action of pushing and releasing a key.
  5. A "Drag" is the action of holding down a mouse button and dragging the mouse.
  6. A "Click" is the action of holding down and releasing a mouse button.
  7. A "DoubleClick" is the action of Clicking twice.
  8. A "Press" is the action of holding down a mouse button.
  9. A "Left+Right" Click is the action of Clicking both the left and right mouse buttons at the same time.
  10. A "Mouse Scroll" is the action of rotating the wheel of the mouse either up or down, if present.

[] Loading & Saving Keybind file

Manipulating the bind file is quick, simple and only requires a basic text editor such as Notepad or Notpad++. Simply insert the desired binds with the proper syntax, then save the file from your computer and then load the file from the game. STO keeps the last copy of the file you loaded from logon to logon so you only need to load the file if you modify the file. Remember to make a backup of your changes, for if you accidentally reset and save the file from the game, you will lose the file you are modifying.
Including the following commands will allow you to quick load, or quick save the current keybind file.


Comments and Keybind the Load and Save of a keybinding File
/ bind_load_file C:\Workstations\_Game Binds\STO_Bind_Space.txt Loads your existing file
Shift+/ bind_save_file C:\Workstations\_Game Binds\STO_Bind_SpaceTest.txt Saves current with new name.
Note: The actual file location should be used. This can be any location on your local machine that you remember. Plus you will be able to save and load a file for Space, RPG, and Shooter Mode.


[] STO Wiki Commands File

For a list of all console commands, see the article. Note: this page is out of date and needs work.

There are three classifications of commands in this article:

[] Executable

These commands cause an action/power to be perform once each time the command is given, or in script, each time the key is pressed.

Distribute Shield Power
Local/Chat Scripted
  /+power_exec Distribute_Shields     p "+power_exec Distribute_Shields"
NOTE:
 When scripting the bindfile.txt the first character is the letter (symbol or key on the keyboard) used to bind this action (here: the letter p is used) followed by a blank space, and then note the action is always enclosed in double quotes. This means, when the bind file is loading into the game, the 'p' key on the keyboard will perform this power or action.

[] Non-Continuous

These commands cause an action/power to be toggled on or off during a single key press.

Turn Left
Local/Chat Scripted
  /+turnleft     p "+turnleft"
NOTE:
 When scripting the bindfile.txt the first character is the letter used to bind this action (here: the letter p is used) followed by a blank space, and then note the action is always enclosed in double quotes.

[] Continuous

These commands cause an action/power to be toggled on or off until canceled by user input.

Strafe Left (Continuous- press key once to strafe left continuous, again to stop)
Local/Chat (do action) Scripted (bind to 'p' key)
  /++left     p "++left"

[] Using Commands

Commands can be used/manipulated in two ways:

[] Chat Window

Entering a command in the chat window requires that it be prefixed with '/' (forward slash). This method uses the syntax:

Chat Window Commands - single command key bind syntax
Syntax Example
 /bind <key> <toggle><command> <Param1> <Param2> ...    /bind p +STOTrayExecByTray 0 0
This command will bind to the p key the power stored in your personal tray Row 1, Column 1.

A list of commands recognized in-game is available by entering the following command in the chat window:

/cmdlist

This command will generate a list of commands in the [system] chat channel which can usually be found under the NPC tab; it is yellow by default. Note: This list can be quite long.

[] Bind File

This method uses the syntax:


Bind file: scripting syntax for a single command key bind
Syntax Example
 <key> "<toggle><command> <Param1> <Param2> ..."    p "+STOTrayExecByTray 0 0"
Scripts the code to bind to the p key the power stored in your personal tray Row 1, Column 1.

Commands in the bind file must be loaded in-game before being usable. Either method will generate the same result. Using a bind file has the benefit recognizing other binds previously created.

[] Clearing Binds

This command will erase all customized key binds and restore the Cryptic defaults.

/unbind_All

Using the "Reset to Default" button will only reset the game to the key binds created by Cryptic. Any binds that these don't overwrite will still exist.

[] Command Variables

Many commands require parameters to function properly. These parameters will appear as text between <chevrons> and are required to assign a value to most commands; some commands require more than one input. These include:

[] Binaries <bin>

Binaries are either 1/+ (on) or 0/- (off). Binary inputs are denoted as <bin>; Typing /combatlog 1 will toggle the combatlog on, while /combat 0 will toggle it off. To verify the value of activation in a binary command, simply enter /combatlog.

[] Integers: <int>

Integers are whole numbers: 0, 1, 2, 3 and so on. The input requirement is denoted by <int> or <value>.

[] Strings: <string>

A string is a sequence of characters required to properly execute. Examples include, but are not limited to: player names, power names and chat channels. When scripting key bind commands, all commands are considered strings and inserted in the script between two quotes.

[] Parameters: <Param#>

A parameter is a reference or value that is passed to a command. In this case, <Param#> is loosely used to identify any of the above.

[] Basics of the Bind

Some things to note:

  1. The player must be in space to manage space key binds.
  2. The player must be on the ground to manage ground key binds.

[] Syntax

To create a bind that works, there must be proper syntax or it will not function.

[] Single Command Syntax

To summarze:

Single Command Key Binding Syntax
Chat Script
 /bind <key> <toggle><command> <Param1> <Param2> ...    <key> "<toggle><command> <Param1><Param2> ..."
Note the absence of the '/bind' and the presence of " (quotation) for the bind file.
The quotation marks are required in the bind file.

Definitions:
<key> is the keyboard shortcut to execute the command.
<toggle> is an optional parameter to indicate '+' (single action) and '++' (continuous action).
<command> is the game command that is desired.
<Param#> is any parameter(s) the command may require.

[] Multiple Commands Syntax - $$

The key to using multiple commands is putting multiple commands in succession. This is accomplished by $$ (double dollar signs).


Bind file: Multiple Commands Syntax - $$

Chat    /bind <key> <toggle><command> <param1> $$ <toggle><command2> <param2> $$ ...
Script    <key> "<toggle><command> <param1> $$ <toggle><command2> <param2> $$ ..."

[] Special Keys & Names

Most keys the syntax for <key> is just the character itself. Special keys use custom syntax, examples include:


Special Keys*

Script Name    Description of Key
Alt+Tab    ***CAUTION*** DON'T USE*
Lbutton or Rbutton    Left Mouse Button
Shift    Shift Key*
LShift or Rshift    Left or Right Shift Key*
Leftdrag or Rightdrag    Press Left or Right Mouse Button while dragging mouse
Rightdoubleclick or Leftdoubleclick Click Left or Right Mouse Button Twice
Middleclick    Click Mouse Wheel, if available
MButton    Middle Mouse Button
Mousechord    Press both Left and Right mouse buttons simultaneously
Wheelplus or Wheelminus    Scroll Mouse Wheel UP or DOWN
Numpad1    The number "1" key on the number pad† 
Button4 through Button8    Mouse Button 4 through Button 8$dagger
F5    F5 key† 
Scroll   Scroll, Pause, Break Key* 
NumLock    Numlock Key* 
Control    Control, PrtScn, SysRq Key* 
grave    Accent key (`); commonly known as the Tilde (~) key‡  
Alt    Alt key* 
Script Name of Named Keys
Esc
Home
End
Pageup or Pagedown
Space
Add
Subtract
Decimal
Multiply
Divide
Insert
Up Up Arrow
Down Down Arrow
Left Left Arrow
Right Right Arrow

Most keys and key combinations are problem free; but listed below are some examples that should be taken into consideration: One possible key combination that may cause game instability or crashes is the Alt+Tab combination: This key combo can be assigned in the game but may conflict with Windows Alt-Tab command which allows the user to select another window causing an Operating System/Game failure. By not assigning Alt-Tab, this problem can be avoided.

*Take care when using these keys as they can cause conflict with the game when used with other keys (Note: not all keys have this problem, an example would be "LShift" or "RShift" vs "Shift"


†The other keys of this type are named similarly by changing the parameter. Ex: Numpad0...9, F1...5, and Shifta...z, etc.

‡Many other of the symbol keys can be used similarly, to discover their names, either look them up in a table, or one could bind the key through the Options/KeyBind, then /bind_save_file <path>temp.txt and look at the file in question for the key bind and discover its name.

Note: Similarly, many actions in the Main Menu/Options/KeyBind window can be assigned keys, then saving the /bind_save_file <path>temp.txt file and looking up the key bind simply for the purpose of identifying their script name.


[] Bindfile

[] Generating a Bind file

The player's basic key binds for a character can be found in the Options:Key Binds menu. To generate a character's bind file, write the following in the chat window:

/bind_save_file <filename>.txt

[] Locating a Bind File

For those using Windows 7 & Vista it is located:

C:\Users\Public\Games\Cryptic Studios\Star Trek Online\Live

Else:

C:\Users\<user>\Games\Cryptic Studios\Star Trek Online\Live

For the Steam users, it will be located:

C:\Program Files (x86)\Steam\steamapps\common\star trek online\Star Trek Online\Live

For XP it will be located:

C:\Program Files\Cryptic Studios\Star Trek Online\Live

[] Loading/Saving a Bind File

To load a bind file from the root STO directory, simply type the following command:

/bind_load_file <filename>.txt

To save:

/bind_save_file <filename>.txt

A bind file isn't limited to the root directory and can be placed anywhere on the computer. In order to load it, it must be specified entirely as:

/bind_load_file C:\<path to file>\<filename>.txt

To save the file:

/bind_save_file C:\<path to file>\<filename>.txt

[] Working with Binds

[] Single Commands

In the Options:Key Binds menu, the default binds are as follows:

i = Inventory
k = Skills
u = Status
o = People
j = Missions
l = Log
m = Map

There are very specific commands associated with these functions. When the mouse is placed over "Inventory" or similar, the following pop-up appears: Use manually with /GenSendMessage Root ShowInventory. The command /GenSendMessage Root ShowInventory is what's toggled on/off when the key "i" is pressed. A couple examples of this are as follows:

Skills = /GenSendMessage Root ShowPowers
Map = /GenSendMessage Root ShowMap

The following is a list of commands that will bring up the respective windows:

Skills GenSendMessage Root ShowPowers
People GenSendMessage Root ShowPeople
Missions GenSendMessage Root ShowMissions
Captain's Log GenSendMessage Root ShowCaptainLog
Map GenSendMessage Root ShowMap
Fleet GenSendMessage Root ShowFleet
Hail Starfleet GenSendMessage Root ShowRemoteContacts
Review Tickets GenSendMessage TicketWindow_Root ShowWithoutScreenshot
Assignments GenSendMessage Root ShowShipCrewAssignments
Status GenSendMessage Root ShowStatus
Tray Powers GenSendMessage Root ShowTrayPowers
Inventory GenSendMessage Root ShowInventory

Note: some of the command keys have been changed to facilitate mnemonic recall and accommodate my play style. 'S' is used for Status instead of 'U'. 'P' is now People instead of 'O'.

If you use the mouse to navigate, like I do, you can cut'n'paste these commands directly into your bindfile. All you WASD-ers (I should open thread about the inefficiency of that.), you can do the same without fear that your A & S keys will be hijacked.

The next step is to clear the previous designations to prevent my window calamity from still occurring. (Remember I said I'd fix that.) To do so, you simply use double-quotes (""). So, add these:

i ""
k ""
u ""
O ""
j ""
l ""
m ""

One more step and we're done ...

You will note that there are many keys with "(null)" next to them. The means that there was no value present when you created the file. You have to remove the '(null)' because the game doesn't recognize this as a valid command and will deny your file. So, just do a find/replace. In notepad, ctrl+h opens this window. In the "find" type (null). Do not put anything in "replace". Press "Replace All" and voila all the nasty nulls disappear.

Phew. Finally, With these changes made, save your bindfile. Just to make sure the changes are there open it again and, hopefully these changes are in place, close it again.

Now, let's test the magic. Go to STO and load (/bind_load_file <filename>.txt) your bind file. Press 'Control' and tap the 'I' key. You should see your Inventory window pop open. Do it again and it closes. 'Control+M' opens and closes your map.

Bravo, you're on your way to becoming a keybind freakazoid like me. (Binds are like tatoos ... once you have one, you want more.)

Alright, I lied. Open that file and let's add a few more ...

/bind Add throttleadjust .10

- or –

Add "throttleadjust .10"

Effect: When the numberpad plus key is tapped the ship's throttle will increase by one-tenth(.10).

/bind subtract throttleadjust -.10

- or –

subtract "throttleadjust -.10"

Effect: When the numberpad subtract key is tapped the ship's throttle will decrease by one-tenth(.10).

[] Keybinding Chat & Emote

Now, there is an exception to every rule and here it is: Commands differ when it comes to chat channels, but the syntax remains the same. You simply drop the use of quotation marks ("") all together.

Example:

/bind a Team Welcome to my parlor, gentlemen.

- or –

a Team Welcome to my parlor, gentlemen.

Effect: When the A-key is tapped, "Welcome to my parlor, gentlemen." is expressed in the Team chat channel.

One final note, you cannot have linefeeds (code that moves the cursor down one line) in the string, so be careful if you put these together in an editor. Notepad has a "Word Wrap" feature (under Format) that I disable when saving the file.

My thanks to Naevius for pointing this out.

[] Multiple Commands

Okay, you are well on your way to being a Binder. But wait, what's that you say? Yeah, I've got the single command binds down; that's easy peasy, but didn't you say something about targeting blah-blah and healing blah-blah one key? Well, that's more than one command. So, now your wondering: How do I do make that magic happen?

Well, …

The key to using multiple commands is concatenation. That's a big word for putting multiple commands one after the other. To do this you use $$ (double dollar signs). So our now our bind command looks something like:

/bind <key> <toggle><command> <param1> $$ <toggle><command2> <param2> $$ ...

- or -

<key> "<toggle><command> <param1> $$ <toggle><command2> <param2> $$ ..."

Example:

Let's say you use the three tray display which causes you to lose your bridge crew display and weapons display. (The one with the bridge officers in their pretty colors and their powers next to them.) I can give all that back with one of my favorite keybinds:

/bind F5 GenJailAdd Hud_Weapons_Root $$ GenJailAdd Hud_Bridgecrew_Trays_Root

- or -

F5 "GenJailAdd Hud_Weapons_Root $$ GenJailAdd Hud_Bridgecrew_Trays_Root"

Effect: Tapping F5 opens the weapons HUD display and opens the Bridge Crew Tray.

[] Toggle Commands

Several commands use toggles, either plus (+) or minus (-), to turn them on or off. These operators I have classified as Non-continuous and Continuous.

By placing a + (plus) in front of a command, the command is ON while your key is pressed, and off when released. Using ++ (double-plus) causes the action to continue even after the key is released.

The syntax for a non-continuous commands is:

/bind <key> <bin><command><param1><...>

- or -

<key> “<bin><command>"

Example:

/bind numpad4 +left

- or -

numpad4 “+left”

Effect: Causes you to turn left while the number pad 4-key is pressed. The turn stops when the key is released.

You could assign another key with -left. When pressed it will cause the first pressed key to stop the left turn. However, this is negated by simply releasing the initial key.

The second toggle command, Continuous, uses the ++ (double plus). With this toggle the bind is activated when the key is tapped and deactivated when the key is tapped again. This TOGGLES (hence the name) the command ON and OFF.

Example:

/bind numpad4 ++left

- or -

numpad4 “++left”

Effect: TApping the 4-key on the number pad results in a continuous left-hand turn. When the key is tapped again, the turn is canceled.

[] Using Powers (in space)

To use your powers and your Bridge Officer powers in space you need be able to reference their location within the powers display. The powers display is divide into ten (10) trays by ten (10) slots. If you use the three-tray display you see:

1st Tray = 1 2 3 4 5 6 7 8 9 0
2nd Tray = C1 C2 C3 C4 C5 C6 C7 C8 C9 C0
3rd Tray = A1 A2 A3 A4 A5 A6 A7 A8 A9 A0

For the purposes of binding, the trays are numbers 0 thru 9; with the first (1st) tray being 0 and the last (10th) being 9. Your slots are similarly numbered starting at 1 = 0 and going to 0 (or 10) = 9. This convention stems from the fact that counting actually starts at zero (0) not one (1); hence 0, 1, 2, 3 … not … 7, 8, 9, 0.

To use the fourth (4th) power in Second (2nd) tray designated by C4, you can use Control+4 to execute the associated power; however, in keybind scripting language this would be [1 3].

Alt-8 gets the eighth (8th) power in the third (3rd) tray; and in keybind scripting language, this would be [2 7], and so on.

1st Tray = 0 0, 0 1, 0 2, 0 3, 0 4, 0 5, 0 6, 0 7, 0 8, 0 9
2nd Tray = 1 0, 1 1, 1 2, 1 3, 1 4, 1 5, 1 6, 1 7, 1 8, 1 9
.
.
.
10th Tray = 9 0, 9 1, 9 2, 9 3, 9 4, 9 5, 9 6, 9 7, 9 8, 9 9

Tipp: when you use and use for GUI row 2 as the first it will change the accounting ,it will become Tray 1 with start 0 0

[] Using Multiple Powers

Now you say, “That's all and well, but those are the default binds Cryptic provides. I want more.” Use this syntax:

/bind <key> +STOTrayExecByTray <tray> <slot> $$ +STOTrayExecByTray <tray> <slot> $$ ...

- or -

<key> “+STOTrayExecByTray <tray> <slot> $$ +STOTrayExecByTray <tray> <slot> $$ ...”

Using the beam overload/target subsystems shields examples, the bind looks something like this:

/bind 4 +STOTrayExecByTray 2 7 $$ +STOTrayExecByTray 1 3

- or -

4 “+STOTrayExecByTray 2 7 $$ +STOTrayExecByTray 1 3”

Effect: Tapping the 4 key activates Target Subsystems Shields. Tapping it again activates Beam Overload.

[] Activation Limitations

Keybinds aren't the be all end all of Star Trek Online; there are some limitations to using them:

[] Multiple powers = Multiple presses

Many times you will be required to press the <key> multiple times to activate each power bound to that <key>. So, if you have ten (10) powers bound to one key, you will likely have to press that key 10x to get each one to activate.

Now, you're gonna groan, “But isn't that what the binds are for? Why can't we activate all these power with the press of a button?” The answer to that is what I call the “I win button” or, conversely, the “I'm indestructible button” (aka, hammer meet anvil). Cryptic has graciously incorporated (Thank you, again.) the multiple press requirement to prevent anyone from creating just such a monster (or two).

[] Cooldowns slooooow ya down

When the powers being activated share cooldowns such as with the Emergency Power to X powers. Say you have Emergency Power to Shields 1 & 2. If, In the above example, EPtS1 is in A8 and EPtS2 is in C4 pressing the 4-key the first time will activate the first EPtS. Pressing it again immediately afterward will not result in the second EPtS being activated. Since there is a 30s shared cooldown any keypress within those 30s is ignored. Once the cooldown is clear the second (or more) power can be activated.

Everything has an "Activation Time" attached to it. Some are instant with 0s. Others are delayed by .5s. This WILL affect your bind activation sequence.

[] Relax it's only a game

You MUST allow time for the power to activate before pressing the <key> again. If you don't, it is possible that a power will be skipped over and won't be activated until it is next in line. What does this mean? Well, all you button mashers out there pounding on your keyboard like your fingers are auditioning for River Dance need to s l o o o o w d o o o o w n.

[] Ordering

There are two phases to using a compound keybind. Phase 1 occurs when you press the keybind button the first time. Phase 2 occurs when you press the button a second time within a short duration. Any repeated button pressing without a pause longer than 0.5 seconds will maintain Phase 2.

In Phase one the order is from left to right. In Phase 2 the order is from right to left. If you have a keybind that activates all the slots in tray 10, then pressing the button once will run ability in slot 1 and queue the ability in slot 2. If we press the button a second time with out a long pause between the first press, we will enter phase 2. If Slot 2 has not yet activated we will replace it in the queue with the ability in slot 10, and it will be next. Any repeated key presses of the same keybind with in a short duration will maintain phase 2 and queue items.

This feature can be used to create a fail safe queue order. Creating a mirror of a command will allow the priority to be fixed.

A standard command activating the full tray 10 using the keybind import file method would appear as follows:

numpad0 "+STOTrayExecByTray 9 0 $$ +STOTrayExecByTray 9 1 $$ +STOTrayExecByTray 9 2 $$ +STOTrayExecByTray 9 3 $$+STOTrayExecByTray 9 4 $$ +STOTrayExecByTray 9 5 $$ +STOTrayExecByTray 9 6 $$ +STOTrayExecByTray 9 7 $$+STOTrayExecByTray 9 8 $$ +STOTrayExecByTray 9 9"

The keyset is assigned to the numerical keypad's 0 key. If we create a mirror set of this key we can ensure that the priority will always be given to the abilities in the lower slots.

numpad0 "+STOTrayExecByTray 9 0$$+STOTrayExecByTray 9 1$$+STOTrayExecByTray 9 2$$+STOTrayExecByTray 9 3$$+STOTrayExecByTray 9 4$$+STOTrayExecByTray 9 5$$+STOTrayExecByTray 9 6$$+STOTrayExecByTray 9 7$$+STOTrayExecByTray 9 8$$+STOTrayExecByTray 9 9$$+STOTrayExecByTray 9 8$$+STOTrayExecByTray 9 7$$+STOTrayExecByTray 9 6$$+STOTrayExecByTray 9 5$$+STOTrayExecByTray 9 4$$+STOTrayExecByTray 9 3$$+STOTrayExecByTray 9 2$$+STOTrayExecByTray 9 1$$+STOTrayExecByTray 9 0"

In this set we are listing all the slots from slot 1 through slot 10 and then back to slot 1 again. If we do this then in Phase 1 Slot 1 will get first priority since it is listed first. In Phase 2 Slot 1 will get first priority again since it is listed last.

This is an important feature since it allows you to prioritize your abilities. Those in lower slots receive priority. Using this method will allow you to setup a complex chain of buffs, debuffs, and attacks that might require a specific order. Or it may allow you to maintain abilities that you would like to keep up at all times.

[] FAQ

[] Q: I don't like having to select my power setting with my mouse every time I need to change settings. How can I bind the in-game presets to keys.

A: I have all my presets for Weapons, Shields, Engines and Balanced bound to my F9, F10, F11 and F12 keys, respectively. The my bindfile I have:

Power Presets
F9 "StatsPreset_Load Preset_1"
F10 "StatsPreset_Load Preset_2"
F11 "StatsPreset_Load Preset_3"
F12 "StatsPreset_Load Preset_4"

There is a more indepth method, fairly complex and confusing method using slider commands to tweak the power setting to exactly where you want them. If anyone wants to know more send me a PM and I'll help you out.

Note: It is fine to group similar keybinds together and give them a Title. The system will ignore the Title, in this case Power Presets, and continue loading the binds.

[] Q: I'm having a hard time finding my teammates to send them heals. Is there an easy way to do this.

A: Of course; there are actually two ways:

Method #1: The F1 - F5 keys are designated Self (F1), Teammate 1 (F2) and so on. You could bind the desired command to a single button and use the F-key to target your teammate and the bound key to apply the power. So you'd do this:

<key> "+STOTrayExecByTray <row> <slot>"

Then you just tap F-key and then <key> to get your teammate the help they need.

Method #2: I have binds for 30 separate keys set to target any given teammate and send them the needed aid. It looks something like this:

Science Team
i "Target_self $$ +STOTrayExecByTray 6 8"
o "TargetTeammate 1 $$ +STOTrayExecByTray 6 8"
p "TargetTeammate 2 $$ +STOTrayExecByTray 6 8"
[ "TargetTeammate 3 $$ +STOTrayExecByTray 6 8"
] "TargetTeammate 4 $$ +STOTrayExecByTray 6 8"

In this example, my Science Team is located on the seventh tray in the ninth position; hence 6 8. The keys i, o, p, [ (right bracket), and ] (left bracket) are used to apply a Science Team to Myself (i), the first teammate in the list (o) ...

This makes removing that dastardly Jam Sensors or the equally troublesome Scramble Sensors quick and easy. A teammate need but ask and I shall deliver unto them.

[] Q: Esc, Option, Key Bind tab. Esc, Option, Key Bind tab. I'm tired of having to do this over and over each time I want to change a predefined keybind. Is there an easier way.

A: Bouncing in and out can get tiresome; so try:

<key> "keybinds"

This will bind a key to open the keybinds tab. Hit it again and *poof* it closes.

[] Q: I want to be able to distribute my shields constantly during battle. You say you've done it, but you said it wasn't a toggle thingy. What gives?

A: I have bound the distribute shields command (/+power_exec Distribute_Shields) to my fire button. I use the space bar as my fire button; so everytime I press the space bar either I Fire Weapons or I activate a power. Distribute shields is one of those dozen powers.

Try this

space "GenSendMessage HUD_Root FirePhasers $$ +power_exec Distribute_Shields"

This will alternate firing all your energy weapons and distributing your shields each time you presst the space bar. Downside of this is it fires ALL energy weapons ... cannons & beam. If you want to only fire one type of weapon, you'll have to bring each weapon into the powers tray and use a series of +STOTrayExecByTray <row> <slot>.

Note: You really don't have to spam the fire button to fire your weapons unless you have each weapon individually represented in the bind. The next time you have the opportunity, find a buddy. Open a PvP challenge and test this. Press your fire buttion ONCE. Count how long it takes for all your weapons to cycle; I'll bet that for every energy weapon that is activated you'll have just as many seconds to wait. If you fire 4 weapons ... ~4 sec; 8 ... ~8s.

THAT is how often you MUST to press your fire button to maintain a constant rate of fire ... not every quarter second. Give your keyboard a break. (It also might last a little longer.)

[] Q: Can I make my torpedoes high yield and fire them at the same time?

A: You sure can. Try this:

<key> "+STOTrayExecByTray <row> <slot> $$ GenSendMessage HUD_Root FireTorps"

[] Q: I PvP alot and end up in PuGs where everyone is shooting at a different target. I want to be able to provide some leadership and get everyone focusing on the same target. Can you help?

A: Hehehe, oh can I. My teammates all get a giggle when I call out targets in team chat. Try this:

<key> Team Make your target: $target.

The $target string will capture your target's identity and insert it in the phrase.

I have rotating phrases (Set weapons to maximum and hit ...; I despise ...; Dispense with ...). Suffice it to say I have quite a few (and growing). My method is a little more complex, but anyone who wants additional assistance with jazzing <jazz fingers> things up, send me a PM and we'll get ya going.

[] Q: I have to do soo much in a space mission I forget to run my maintenance skills. What can I do?

You can setup a keybind on your spacebar that fires your weapons, executes abilities on a tray, and distributes your shields. You will be required to press the spacebar repeatedly.

In this situation we will use Tray 3. We will place all our important tray abilities from left to right. Left having the highest priority. If we use this with the Ordering method listed above we can use the following keybind:

Space "+STOTrayExecByTray 2 0$$+STOTrayExecByTray 2 1$$+STOTrayExecByTray 2 2$$+STOTrayExecByTray 2 3$$+STOTrayExecByTray 2 4$$+STOTrayExecByTray 2 5$$+STOTrayExecByTray 2 6$$+STOTrayExecByTray 2 7$$+STOTrayExecByTray 2 8$$+STOTrayExecByTray 2 9$$+Power_Exec Distribute_Shields$$GenSendMessage HUD_Root FireAll$$+Power_Exec Distribute_Shields$$+STOTrayExecByTray 2 9$$+STOTrayExecByTray 2 8$$+STOTrayExecByTray 2 7$$+STOTrayExecByTray 2 6$$+STOTrayExecByTray 2 5$$+STOTrayExecByTray 2 4$$+STOTrayExecByTray 2 3$$+STOTrayExecByTray 2 2$$+STOTrayExecByTray 2 1$$+STOTrayExecByTray 2 0"

Now in tray 3 we can place our Emergency Power to Shields (both copies) and our Tactical Team (both copies) and while hitting space bar once a second our abilities on tray 3 will run as they become available.

[] Conclusion

Keybinding is simple and easy, once you know how. Using keybinds will up your game and make you more responsive to the demands of combat. They help you assist your teammates quickly in time of need. AND, when others use them, they help your teammates keep you alive.

Hopefully, I haven't completely confused everyone and now you have at least an insight as to how to bind commands to keys and how it all goes together. If you are confounded I will do my best to clear things up just keep the questions coming; I'm here to help.

[] test, Test, TEST

One last thing about multiple commands, timing is everything in this game. Be sure to test it first to see that everything is happening when you want it to happen. You don't want to use your beam overload before your target subsystems shields ... kind of a waste.

[] Disclaimer

Finally, I'm not a Vulcan. This is not a perfect work; there may be (probably are) errors or omissions. This is also my first attempt at providing a guide for others to learn from. What may seem logical to me may not to you. If you find something wrong, please let me know and if you know the answer, definitely let me know. I know there is more I can learn. When something new is found or corrected, I will make the change and notate it for everyone to see.

Oh, one last tidbit ...

KEYBINDS ARE ESSENTIAL TO SUCCESS IN PvP.

Happy Hunting ... (klinks)

Zed

[] External links

Edited by -- 20:08, 24 February 2013 (UTC) Gervnd@cyberpapa STO

Retrieved from ""