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

[Ualaa]

I'm experiencing the same issue as Owltoid, in the above post.
Latest (current) version of Jamba.

I have IS Boxer, which does a Mapped Key Action > FTL Follow Me (Current Window) & Pop Up Text "FTL Follow Me", bound to a mouse thumb button.

When I push the button, I get Jamba warnings that follow has broken on two toons.
However, all four toons follow correctly.

While the toons are still following, if I push the mouse button (follow bound to it), I get the warning that two toons have broken follow.
But follow has not broken, and they are behind me correctly.

To be clear, the warning of a follow broken comes up, whenever I initiate follow.
But follow works correctly.
Further, when I do independent slave movement, it still correctly informs me of follow breaking (well, when Follow Breaking notification is enabled, it does anyway.)

Going into Jamba options for Follow, I have disabled the notification that follow has broken.
I'd rather have the Jamba Warning if follow breaks, so this is a temporary fix.

[Staph]

I'm having issues with the strobe follow. It worked fine the first day of using it but yesterday it didn't work. I used the command same way both days /jamba-follow strobeonme all.

Secondly is there anyway to move the quest tracker from the middle of my screen? I tried holding alt and dragging and ctrl+alt plus other combinations with no success. It's just stuck in the dead center of my screen. Team and items moved fine with alt.

Thanks in advance.

[moosejaw]

To move the quest tracker you have to enable the movement from the jamba settings /jamba. There should be a check box to enable movement.

[Kris1234]

Hey,
I am getting this error with using Jamba with Tour Guide, Let me know if this is a Tour Guide issue and i;ll contact them instead

Date: 2010-10-26 13:27:25
ID: 2
Error occured in: Global
Count: 1
Message: ...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua line 842:
Usage: GetQuestLogTitle(index)
Debug:
[C]: ?
[C]: GetQuestLogTitle()
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:842:
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:837
(tail call): ?
[C]: ?
[C]: RemoveQuestWatch()
TourGuide\Broker.lua:61: UpdateStatusFrame()
TourGuide\QuestTracking.lua:50:
TourGuide\QuestTracking.lua:44
[C]: pcall()
TourGuide\Dongle.lua:247:
TourGuide\Dongle.lua:246
TourGuide\Dongle.lua:334:
TourGuide\Dongle.lua:328

[Kris1234]

and I seem to be getting this on other toons:

Date: 2010-10-26 16:40:51
ID: 6
Error occured in: Global
Count: 1
Message: ...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua line 842:
Usage: GetQuestLogTitle(index)
Debug:
[C]: ?
[C]: GetQuestLogTitle()
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:842:
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:837
(tail call): ?
[C]: ?
[C]: RemoveQuestWatch()
tomQuest2\tomQuest2.lua:4570: ?()
...Bot\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147:
...Bot\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147
[string "safecall Dispatcher[1]"]:4:
[string "safecall Dispatcher[1]"]:4
[C]: ?
[string "safecall Dispatcher[1]"]:13: ?()
...Bot\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: Fire()
...face\AddOns\Jamba\Libs\AceEvent-3.0\AceEvent-3.0.lua:120:
...face\AddOns\Jamba\Libs\AceEvent-3.0\AceEvent-3.0.lua:119

[Jafula]

Looks like TomQuest and TourGuide are incompatible with Jamba Quest Watcher at the moment. You will have to use one or the other until I get a chance to look at the issues and see if I can fix them.

Thanks for reporting them!

[Jafula]

I'm experiencing the same issue as Owltoid, in the above post.
Latest (current) version of Jamba.

I have IS Boxer, which does a Mapped Key Action > FTL Follow Me (Current Window) & Pop Up Text "FTL Follow Me", bound to a mouse thumb button.

When I push the button, I get Jamba warnings that follow has broken on two toons.
However, all four toons follow correctly.

While the toons are still following, if I push the mouse button (follow bound to it), I get the warning that two toons have broken follow.
But follow has not broken, and they are behind me correctly.

To be clear, the warning of a follow broken comes up, whenever I initiate follow.
But follow works correctly.
Further, when I do independent slave movement, it still correctly informs me of follow breaking (well, when Follow Breaking notification is enabled, it does anyway.)

Going into Jamba options for Follow, I have disabled the notification that follow has broken.
I'd rather have the Jamba Warning if follow breaks, so this is a temporary fix.

Unfortunately its not going to be easy to fix this issue. When you start following from a standstill you get a follow begin, a follow end and then a follow begin event. I have no idea why there is a follow begin, end before a follow begin! I had to set up a counter to try and track these and it all falls apart when you actually break follow and try and follow again, because then you don't get the extra follow begin/end events, so my counter fails and I have no idea how to tell which situation is which.

In the next release, I have implemented a new option that will only warn if follow breaks when your toon is outside of follow range. This is better in that you still get a follow broken warning when your toon is too far away to follow, but otherwise, you can still use the follow status from the Jamba-Display-Team window to see who is following.

I've asked Blizzard to fix the issues that caused this in the suggestions thread on the forum, but I can't see it being a priority for them!

[Owltoid]

Damn Jafula, you really know your stuff! Thanks for going to bat for us again!

[Ualaa]

The Jamba team display, with the experience percentage or health levels, correctly displays the follow status (green following, red broken follow). It is just the raid warning, which is off.

If there is no raid warning on the screen, until the toons are out of follow range, that solves the issue.

Thank you.

[ElectronDF]

So if you check for a follow begin, follow end and follow begin in less than 2 milliseconds, then ignore the error doesn't work?