as an aside, I think I might resurrect my all hunter team - sounds like fun
Printable View
as an aside, I think I might resurrect my all hunter team - sounds like fun
The complexity of setting up an FTL system is greatly reduced if you have a /click macro that takes care of the targeting. If that's the case, then your other macros are all very small and simple (simply referencing the click button and then casting the spell).
As far as Fur's comments of what happens when the main toon dies, that is exactly the FTL's strength: flexibility. It doesn't matter which of my 5 windows I'm in, if that's where I hit the keystroke from then all others treat that toon as the current master without me having to do a thing.
I agree that the FTL system is more complicated to set-up than the focus-based system. Other than that extra complication, the FTL system is superior in every way since it has the flexibility to do everything the focus system can, but also has other functionality. In my opinion, it's analogous to HKN and Keyclone. Keyclone is reportedly more simple to set-up, but I know HKN has more functionality once you get past the initial stage. Does that mean every user should use HKN or an FTL system? Absolutely not. All it means is that if you want to have the most "powerful" system, then those are your best options. If you are most interested in initial set-up, then perhaps Keyclone and focus-based is the best option.
Owltoid,Quote:
Originally Posted by 'Owltoid',index.php?page=Thread&postID=206362#post 206362
I'm reaching out for some help. hehe. I know there is a big FTL guide out there, but I thought that it required Keyclone to use. I, like you, use HKN, and I'd love to know how you set up an FTL system using HKN. I know with Keyclone, they did some fancy stuff where the same key could be used on all five windows. Is that the same with the HKN version? Sorry if this is addressed elsewhere, but I'm really curious now, as I'd like to set up an FTL system using HKN.
Fur, I think it's not necessarily a heirarchy, but moreso a way of just allowing you to switch WoW windows, press a key, and now that window is considered the "leader" And you can do that on all five of the different windows, so that switching leaders is really a matter of bringing that leader's window to the forefront and pressing some key. Makes it real handy if one of your player's dies, or falls, sort of like what you mentioned.Quote:
Originally Posted by 'Fursphere',index.php?page=Thread&postID=206368#po st206368
The main issue is simply in setting it up. There's a neat guide for how to do it with Keyclone, but I asked Owl above how he pulls it off with HKN, since that's what I use for replication, too.
Sorry Fur, that's not correct. The "L" in FTL is for "leaderless."Quote:
Originally Posted by 'Fursphere',index.php?page=Thread&postID=206368#po st206368
As mentioned above, the only thing an FTL system cares about is what window the command came from. If you are dual-boxing then maybe one window will always send "lctrl + command" and the other window will always send "ralt + command". The macros have those modifiers in them so that if it received "lctrl + command" it knows to assist Owltoid, whereas if it received "ralt + command" then it knows to assist Fursphere.
This can all be simplified if, instead of having the conditionals in your spell macro, you instead make a /click button that's only job is reading the conditionals and assigning the target. Sorry, I don't have the macros in front of me, otherwise I'd post some examples.
Here is a snippet of some HKN code that deals with an FTL system. It's pretty basic, really. All you do is launch your 5 instances of WoW (giving them unique names like WoW1, WoW2, etc) and then ask HKN which window the command was sent for. HKN then sends whatever keystrokes you want it to (in this case it reads that it came from WoW2 and therefore appends "RCtrl Ralt" to the keystoke so all clients know to assist my WoW2 toon).
Code://General Sharing
<Hotkey ScrollLockOn a, c, d, f, g, r, t>
<Passthrough>
<If ActiveWinIs WoW1>
<SendLabel WoW2, WoW3, WoW4, WoW5>
<Key RCtrl %Trigger%>
<Else If ActiveWinIs WoW2>
<SendLabel WoW1, WoW3, WoW4, WoW5>
<Key RCtrl RAlt %Trigger%>
<Else If ActiveWinIs WoW3>
<SendLabel WoW1, WoW2, WoW4, WoW5>
<Key RCtrl RAlt RShift %Trigger%>
<Else If ActiveWinIs WoW4>
<SendLabel WoW1, WoW2, WoW3, WoW5>
<Key RAlt %Trigger%>
<Else If ActiveWinIs WoW5>
<SendLabel WoW1, WoW2, WoW3, WoW4>
<Key RAlt RShift %Trigger%>
<Endif>
<Hotkey ScrollLockOn LShift a, c, d, m, r>
<Passthrough>
<If ActiveWinIs WoW1>
<SendLabel WoW2, WoW3, WoW4, WoW5>
<Key RCtrl %Trigger%>
<Else If ActiveWinIs WoW2>
<SendLabel WoW1, WoW3, WoW4, WoW5>
<Key RCtrl RAlt %Trigger%>
<Else If ActiveWinIs WoW3>
<SendLabel WoW1, WoW2, WoW4, WoW5>
<Key RCtrl RAlt RShift %Trigger%>
<Else If ActiveWinIs WoW4>
<SendLabel WoW1, WoW2, WoW3, WoW5>
<Key RAlt %Trigger%>
<Else If ActiveWinIs WoW5>
<SendLabel WoW1, WoW2, WoW3, WoW4>
<Key RAlt RShift %Trigger%>
<Endif>
//Hotkeys for the macros that are not target specific
<HotKey ScrollLockOn b, 1, 2>
<SendLabel WoW1, WoW2, WoW3, WoW4, WoW5>
<Key %Trigger%>
<Hotkey ScrollLockOn Shift b, i, x, 2>
<SendLabel WoW1, WoW2, WoW3, WoW4, WoW5>
<Key %Trigger%>
<Hotkey ScrollLockOn Ctrl m, p, r, z>
<SendLabel WoW1, WoW2, WoW3, WoW4, WoW5>
<Key %Trigger%>
<Hotkey ScrollLockOn Alt m>
<SendLabel WoW1, WoW2, WoW3>
<Key %Trigger%>
//Follow when lead is autorunning
<MovementHotkey ScrollLockOn MButton>
<Passthrough>
<If ActiveWinIs WoW1>
<SendLabel WoW2, WoW3, WoW4, WoW5>
<Key RCtrl LShift Z>
<Else If ActiveWinIs WoW2>
<SendLabel WoW1, WoW3, WoW4, WoW5>
<Key RCtrl RAlt LShift Z>
<Else If ActiveWinIs WoW3>
<SendLabel WoW1, WoW2, WoW4, WoW5>
<Key RCtrl RAlt RShift LShift Z>
<Else If ActiveWinIs WoW4>
<SendLabel WoW1, WoW2, WoW3, WoW5>
<Key RAlt LShift Z>
<Else If ActiveWinIs WoW5>
<SendLabel WoW1, WoW2, WoW3, WoW4>
<Key RAlt RShift LShift Z>
<Endif>
i know im late to the argument....
i started off using targettarget. but have switched to focustarget. i find focustarget superior. no supporting evidence? ya, none. just my opinion.
alright folks, work with all the methods here and find what fits your style. kk.. going back to workplace obscurity.
I think the important difference is that the in-game macros / addons that were disabled were changing state or reacting to changes in game and leveraging that information to make "smart" choices with a single button press by performing various status checks.
I am not sure I''d agree with that statement here - Yes there is a logic block. However, it does not manipulate in-game keybinds at all. Once defined, a keypress will always generate the same key combo in-game without changing or modifying its behavior.Quote:
but you're still using logical arguments to manipulate ingame key bindings.
It's simply a mechanism for re-mapping a keystroke. Keyclone supports keymapping which is functionally equivalent as far as I can tell (and I would assume uses a somewhat approach in the code).
Cant we do this in game (check for character death)? its not explicitly using if / then syntax but....
/stopcasting [target=Lefthoof, nodead]
/cast [target=Lefthoof] Revive;
I think you're late to the party here, Fursphere. This is how FTL is always implemented. All it's doing is sending a different set of modifier keys depending on the window it's being broadcast from. The in-game macro has conditionals using the "mod" conditional to have a different assist target (etc) depending on the modifier keys held down -- each set corresponds to a different character. This way, just like using Focus with the active window being the Focus Target, it doesn't matter which toon you are playing, your followers will always follow,assist, etc the one you are playing.Quote:
Originally Posted by 'Fursphere',index.php?page=Thread&postID=206392#po st206392
http://www.dual-boxing.com/wiki/inde...aderless_Setup
Using if/then statements to determine the state of the program in the OS (i.e., window in foreground or background) is a far cry from checking the state of a toon within the program. One uses data from the operating system, the other uses data from the game. Making decisions based on data in game is where the TOS line is drawn. This doesn't seem to be even close to a gray area to me.
The decision to change focus on a toon or who to follow or assist can only be made by the user pressing the button to make it so. What Fur seems to be saying here is that if someone is using a hardware KVM switch to box with, it would be Breaking TOS to have that KVM button also pass a key to the program. This is what we're talking about here. No data from WoW is pressing that button for you, and software broadcasting those keys in the same way is no different.