Quote Originally Posted by 'lacitpo',index.php?page=Thread&postID=117203#post 117203
So this is purely for focus management. Seems like a great system. Have you thought about a /jamba settarget command also?
I have now. Because of wow api restrictions, Jamba target changes could only happen out of combat. So on the fly in combat target changing is out. BUT, what if you could set up 3 target commands, each with its own key bind.
  1. Before combat, you set up mob1 as target1, mob2 as target2 and mob3 as target3.
  2. At the start of combat, you press key1 which targets mob1.
  3. Nuke mob1 out of existance while tanking the rest.
  4. When mob1 is dead; press key2 which targets mob2.
  5. Nuke mob2 out of existance while tanking the rest.
  6. When mob2 is dead; press key3 which targets mob3.
  7. Nuke mob3 out of existance and give your tank a rest.
So a couple of new commands:

/jamba settarget <#> <target> <nickname>

/jamba settargetresolve <#> <target> <nickname>

The command settargetresolve gets the actual name of the mob from the <target> and places that in the internal macro instead of <target>. E.g., if my slaves were targetting my main, and my main was targeting mob1 then

/jamba settarget 1 targettarget slave => /target targettarget

/jamba settargetresolve 1 targettarget slave => /target mob1

I'd throw in a raid icon option as well somewhere. And a gui, because I don't want to type all those slash commands the whole time. Although shouldn't be too hard to bind the commands to a key using Trinity (or similar). Maybe allow up to 5 targets. Is that enough?

EDIT:

And if while in combat you got an add / mob that wasn't Jamba targetted, you could fall back to (in my case) a keypress that causes slaves to target the master (my spells are all the "/cast [target=targettarget, harm] [] Lightning Bolt" style macros)