[Addon] Jamba - An assistant for multiboxers. Old Thread

[Bettysue]

The easiest way to prevent self follow is to remove the toons name from the follow macro, for instance say you had the macro you posted on the character Celestis, you would remove

[mod:ctrl,mod:shift,nomod:alt]Celestis

or if you use something like keyclone or HKN to send the modifiers to the alts but not the main then put your "targetting" macro on a bar somewhere, and then make the follow macro something like

/clearfocus
/click [mod] MultiBarRightButton1
/follow focus

that would click the top right button on the right side bars

and that button would have the following macro from your example

/focus [mod:ctrl,mod:shift,nomod:alt]Celestis;
[mod:ctrl,mod:alt,nomod:shift]Celestîs;
[mod:alt,mod:shift,nomod:ctrl]Celestïs;
[mod:ctrl,mod:alt,mod:shift]Célèstis;
[nomod]player

[Svpernova09]

I'm still getting the crash when the main takes a FP but the slaves don't. I wasn't able to reliably reproduce it. I'll keep working at it.

[falsfire3401]

I'd taken a temporary pause in true mb'ing while waiting for 3.2 and cheap mounts. Now that 3.2 is here I'm actively controlling 3 toons.

Previously, I used to get quest status updates on the master in the default chat when the slaves progressed on a quest, be it killing mobs or looting items. It was very helpful to know whether or not the slave actually had accepted the quest, and their progress without having to glance at the second monitor when they loot something!

Since I started up again, these notifications are gone. I've made sure that "Quest Silently" is turned off in my jamba options, and none of my jamba options have changed except I've added a 3rd toon to the team (was just two toons before).

Any idea what option might be causing the total lack of quest progress messages?

[Jafula]

This is a very raw Jamba 0.5 out that needs some love. Please test it and provide some feedback in the thread.

http://www.dual-boxing.com/showthread.php?t=23377

[Heenan]

Hi Jafula,

I have a question about your quest log window helper. What are the base requirements for this to function?

On my horde server it has never worked correctly. When I would choose "select" only one alt ever followed the main's selections. I recently changed servers, and as soon as I made my new team it worked flawlessly. I believe I had installed 0.4f before starting there, so maybe that was it. But within the last 2 days the functionality has completely stopped working. It won't do group selects or abandons (a bummer when you're running through areas grabbing all quests just to see that they're gray).

I really love this functionality. Do you have any ideas? Corrupt .lua files maybe?

Edit: I've been running the same mods for the last year, so nothing has changed there.

Edit2: I've purged all Jamba related files and reinstalled 0.4g. This is still not working. Anyone know?

[Jafula]

Hi Jafula,

I have a question about your quest log window helper. What are the base requirements for this to function?

On my horde server it has never worked correctly. When I would choose "select" only one alt ever followed the main's selections. I recently changed servers, and as soon as I made my new team it worked flawlessly. I believe I had installed 0.4f before starting there, so maybe that was it. But within the last 2 days the functionality has completely stopped working. It won't do group selects or abandons (a bummer when you're running through areas grabbing all quests just to see that they're gray).

I really love this functionality. Do you have any ideas? Corrupt .lua files maybe?

Edit: I've been running the same mods for the last year, so nothing has changed there.

Edit2: I've purged all Jamba related files and reinstalled 0.4g. This is still not working. Anyone know?

Hi,

Sorry you are having this trouble.

Serveral things to check...

1) Are you opening the quest log/quest npcs dialogs on all the toons first, before you do the actions on your master? If not, you need to start doing this.

2) Is your team configured correctly, i.e. the same toon list / master / all toons enabled on _every_ toon. Read this article.

3) Have you tried with just the Jamba addon (and no other addons)? Maybe a mod has been updated that now conflicts with Jamba.

[Heenan]

Hi,

Sorry you are having this trouble.

Serveral things to check...

1) Are you opening the quest log/quest npcs dialogs on all the toons first, before you do the actions on your master? If not, you need to start doing this.

2) Is your team configured correctly, i.e. the same toon list / master / all toons enabled on _every_ toon. Read this article.

3) Have you tried with just the Jamba addon (and no other addons)? Maybe a mod has been updated that now conflicts with Jamba.

So I fixed my problem in case anyone runs into this.

The problem was the Jamba quest log helper would not select quests for the group for abandoning and marking. CT_Mod (CT_Core specifically) was conflicting with this. I had enabled the "show quest level in quest log" option. As soon as I disabled that it worked again. I didn't want to have to disable CT_Core, but disabling the quest levels made it work again. QuestHelper shows the levels in its log anyway, so it's fine.

[Jafula]

I'd taken a temporary pause in true mb'ing while waiting for 3.2 and cheap mounts. Now that 3.2 is here I'm actively controlling 3 toons.

Previously, I used to get quest status updates on the master in the default chat when the slaves progressed on a quest, be it killing mobs or looting items. It was very helpful to know whether or not the slave actually had accepted the quest, and their progress without having to glance at the second monitor when they loot something!

Since I started up again, these notifications are gone. I've made sure that "Quest Silently" is turned off in my jamba options, and none of my jamba options have changed except I've added a 3rd toon to the team (was just two toons before).

Any idea what option might be causing the total lack of quest progress messages?

Sorry, I turned that functionality off by default in a recently release.

Go into Jamba-Talk options, and check 'Forward UI Errors' and 'Forward UI Information'.