Quote Originally Posted by 'Gadaí',index.php?page=Thread&postID=42755#post427 55
First of all, apologies if this is a frequent question, I tried searching the forums for similar posts and couldn't find any which addressed this specific issue.I've been triple boxing for a while now (palatank, resto shaman, frost mage), running 1 account on my 'main' machine (computer A) and the mage/shaman on a second machine (computer B). I've been using Keyclone up to this point to pass keystrokes from computer A to computer B and found it to be very useful/good/praiseworthy. Since I'm consider moving up to 5 accounts (thinking palatank, resto shaman, 3 x frost mage) I thought I should increase the available number of keys for controlling my alts actions (just been using the Numpad up to now, set up in Keyclone as a white list in the do-not-pass interface). With this in mind I purchased some Logitech G11 Keyboards. My initial disappointment at discovering that the G-keys were not in fact uniquely mapped (I assumed that the G11 would use a custom hardware profile, loaded from the installation disk, similar to the early 102 key keyboards) was soon replaced by annoyance with it's behaviour through Keyclone. An example seems to be called for so here we go:

On computer A I create a WoW set of bindings using CTRL + F1-F3 for G1-G3 and set the WoW key bindings to the default in the profiles (this is in the G11 software). In Keyclone I go into do-not-pass and add CTRL + F1-F3 to my white list, using the G1-G3 keys to set up the entries. On computer B I set CTRL + F1 as a secondary action key for strafe left for testing purposes. My control char is a paladin so each time CTRL + F1 is entered his Devotion Aura turns on or off (the default key binding within WoW for CTRL + F1) so I know that when I hit G1 Devotion will activate or de-activate if the G-key profile is working properly. When I hit the G1 key the Devotion aura fires on the paladin but on the second character the 'target self' function takes place - the WoW key binding for that being F1. I tried this using different key modifiers (ALT, SHIFt, ALT + SHIFT, CTRL + ALT, CTRL + SHIFT) and the behaviour is identical, that while the 'normal' key is being passed through Keyclone (F1/etc) that the modifying key (CTRl, ALT, SHIFT) is being lost after it is passed from computer A to computer B but before the combination is entered in WoW on computer B (since F1 on it's own will not be passed - I have tested that).

So - any suggestions as to the cause of this behaviour? Any advice would be appreciated :thumbsup:
This issue has been discussed numerous times on the forums. Here is what is happening:

On toon 1 you have ctrl+F1 mapped to devo aura
On toon2 you do not have anything mapped to ctrl+F1
On toon3 you do not have anything mapped to ctrl+F1

What WoW does when you press ctrl+F1 is look for a skill or function bound to that key. If it finds one, then it fires off that skill/function. If WoW doesn't find anything bound to ctrl+F1, it will assume that you meant to hit F1 and fire off any skill/function bound to F1. To avoid this "feature" of WoW, you can remap your keys so that you don't have this scenario happen, or you can use an addon like Trinity2 or Bongos to create "fake" hotbars where you can bind empty buttons to keymappings like your ctrl+F1 scenario above. For example, you could map ctrl+F1 on toon2 and toon3 to one of these empty buttons and then WoW would see that you had a button bound to ctrl+F1 and not do anything when you press that combination.

I preferred remapping to keybindings that don't have any similar bindings. For example:
ctrl+[
or
ctrl+shift+`
or
ctrl+alt+,

There are no default bindings to the left bracket, tilde, or comma so you can avoid WoW firing off skills that you don't want it to by utilizing these keys.