Quote Originally Posted by 'zanthor',index.php?page=Thread&postID=125563#post 125563
The focus doesn't seem to work reliably. I don't know if I'm using this right so I'll break down my config.

<snip>

Without the Focus command and utilizing Jamba to set focus to new master Jamba would announce that all 5 had the right new focus.
They however, did not. There wasn't any consistancy to it either.
Here's the low down on focus.
  1. The wow api FocusUnit() function is protected, so addons cannot call it. There is no way for Jamba to automatically set focus to a unit.
  2. But what Jamba can do is create a macro internally that runs "/focus master" where master is the toon you choose to be the master.
  3. When the master changes and you have the "Set Focus To Master" option checked in the Jamba Team configuration; Jamba will attempt to rewrite that macro to set focus to the new master. But if you are in combat, Jamba cannot rewrite that macro (forbidden by wow api).
  4. If Jamba succeeds in re-writing that macro; your toons tell the master that they have sucessfully changed the focus. You also get a failed message if you are in combat.
  5. Now having a macro without a means of calling that macro is a bit silly; so Jamba provides a key bind to call that macro. You need to bind a key on all your toons to the "Jamba Focus" key. You can find this binding in the wow keybinding interface.
  6. Once you have set up a key and the focus macro gets re-written, Jamba toons will tell the master that they have successfully changed the focus and they will also tell the master "Press E to activate." (If you had E bound as your Jamba Set Focus key.)
  7. So you press E on your keyboard which transmits the E keypress to your toons (using KeyClone, etc) and all the toons will run the /focus master command (which can be done in combat). Now they all have focus on the master.
So, its pretty much useless for PVP (cannot change focus in combat).

I use the target version of this setup for PVE. If I run with a new main, I don't have to change my /target macros to point to the new main. I run with "/cast [target=targettarget] UberSpellName" macros; so regardless of who my master is, when I press my "Jamba Target" key, I my toons always target the correct "master" toon.

Quote Originally Posted by 'zanthor',index.php?page=Thread&postID=125563#post 125563
Also an overall throttle on the warnings would be great, My current follow engine strobes a follow once a second... this means if I turn on melee I get "Follow Broke" messages 4x a second...
The throttling I could do; but how about if I implemented your follow strobe in Jamba-Follow; that way Jamba would know that Jamba was the cause of the follow break and would suppress the warning message. I could build a special build just for you over the next couple of days, say 0.2b and we can tweak it until you're happy. What do you think?

Quote Originally Posted by 'zanthor',index.php?page=Thread&postID=125563#post 125563
5 clients, 5 hotkeys to switch PIP.
For simplicty we'll say F1-F5

Each is also bound to macro's such as:
/jamba setmaster Sarnarn
/focus Sarnarn
/script fzStart("Sarnarn")

/jamba setmaster Samarn
/focus Samarn
/script fzStart("Samarn")
I have a suggestion for you. Don't use the Jamba "Set Focus To Master" option. Stay with what you have currently for focus.

An idea, please comment:

How about Jamba provided 5 "focus" macros and keybinds like you have bound to F1-F5. They might look like.

/jamba setmaster %TOON%
/focus %TOON%
/whatever-else-you-want you-can-edit-these just-leave-the-%TOON%-markers

So when you make a new team, Jamba writes these macros for you (on startup) by replacing %TOON% with the actual toon name. This way, when you add new toons, etc, you don't need to write a new macro for them.

There would be a system to map a toon to a key, so the correct key had the correct toons name in it.