[Addon] Jamba - An assistant for multiboxers. Patch 5.0.4 Beta Testing. BETA #3 released.

Been getting this from the Jamba-item Use module. Most current beta3.

Code:

---

Message: Interface\AddOns\Jamba\LibActionButtonJamba-1.0.lua:1270: attempt to call global 'GetCompanionCooldown' (a nil value)
Time: 09/27/12 11:47:25
Count: 1
Stack: Interface\AddOns\Jamba\LibActionButtonJamba-1.0.lua:1270: in function `GetCooldown'
Interface\AddOns\Jamba\LibActionButtonJamba-1.0.lua:1058: in function <Interface\AddOns\Jamba\LibActionButtonJamba-1.0.lua:1057>
Interface\AddOns\Jamba\LibActionButtonJamba-1.0.lua:934: in function <Interface\AddOns\Jamba\LibActionButtonJamba-1.0.lua:928>
Interface\AddOns\Jamba\LibActionButtonJamba-1.0.lua:924: in function `UpdateAction'
Interface\AddOns\Jamba\LibActionButtonJamba-1.0.lua:454: in function `UpdateState'
Interface\AddOns\Jamba\LibActionButtonJamba-1.0.lua:429: in function `SetState'
Interface\AddOns\Jamba-ItemUse\JambaItemUse.lua:315: in function `UpdateItemsInBar'
Interface\AddOns\Jamba-ItemUse\JambaItemUse.lua:793: in function <Interface\AddOns\Jamba-ItemUse\JambaItemUse.lua:781>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[1]"]:9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?
...face\AddOns\Jamba\Libs\AceAddon-3.0\AceAddon-3.0.lua:514: in function `InitializeAddon'
...face\AddOns\Jamba\Libs\AceAddon-3.0\AceAddon-3.0.lua:629: in function <...face\AddOns\Jamba\Libs\AceAddon-3.0\AceAddon-3.0.lua:621>
Locals: <none>

---

Seeing an error when Im trying to do a basic setup after the install.

The navigation pane works fine, but when I click a checkbox or button, its throwing errors

Code:

---

5x Libs\6AceGUI-3.0-33\widgets\AceGUIWidget-Slider.lua:161: Usage: <unnamed>:SetValue(value)
<in C code>
Libs\6AceGUI-3.0-33\widgets\AceGUIWidget-Slider.lua:161: in function "SetValue"
Jamba-DisplayTeam-beta-1.0beta3\JambaDisplayTeam.lua:1073: in function "SettingsRefresh"
Jamba-DisplayTeam-beta-1.0beta3\JambaDisplayTeam.lua:1809: in function "?"
Libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:147: in function <Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
<string>:"safecall Dispatcher[2]":4: in function <string>:"safecall Dispatcher[2]":4
<in C code>
<string>:"safecall Dispatcher[2]":13: in function "?"
Libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:92: in function "SendMessage"
Jamba-beta-1.0beta3\JambaTeam.lua:579: in function <Jamba\JambaTeam.lua:566>
Jamba-beta-1.0beta3\JambaTeam.lua:1345: in function <Jamba\JambaTeam.lua:1343>
(tail call): ?
<in C code>
<string>:"safecall Dispatcher[4]":9: in function <string>:"safecall Dispatcher[4]":5
(tail call): ?
Masque-40300\Libs\AceGUI-3.0\AceGUI-3.0-33.lua:314: in function "Fire"
Libs\6AceGUI-3.0-33\widgets\AceGUIWidget-Button.lua:28: in function <Libs\AceGUI-3.0\widgets\AceGUIWidget-Button.lua:25>


Locals:
nil

---

When I try to invite my toons to a party they automaticly accepts, then leaves right after. When I disable Jamba they join the party with no problems. Attachment 696

This usually has to do with a conflict with other addons. Some include auto accept for invites that causes problems with the Jamba accept

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

Quote:

---

Originally Posted by Khatovar

This usually has to do with a conflict with other addons. Some include auto accept for invites that causes problems with the Jamba accept

---

Jup that was the problem, thx :)Stange thing i have used TukUI for a long time without getting this problem.

Any updates on when we will see beta 4, or a release?

Another strange issue I've noticed is that it's not setting FFA when you invite all your team members, even though it's set to do so in the option.

Quote:

---

Originally Posted by Igg

Another strange issue I've noticed is that it's not setting FFA when you invite all your team members, even though it's set to do so in the option.

---

It's doing the same thing to me. If you hit invite a second time you'll get the message that everyone is already in a group but it changes the loot setting to FFA.

Quote:

---

Originally Posted by Criels

It's doing the same thing to me. If you hit invite a second time you'll get the message that everyone is already in a group but it changes the loot setting to FFA.

---

It probably has to do with dungeons being a second group over the top of the group you form in a city. Entering crz areas also resets the groups. An easy fix I found is just add /ffa to my follow macro. That way every time I hit follow it sets the loot to ffa and if it's already set it silently ignores the change. Of course you may need to use a different macro to throw /ffa on if you run with others.

Quote:

---

Originally Posted by Murdabenne

Any updates on when we will see beta 4, or a release?

---

Hoping to get a release out within a week. Got a geocaching MEGA event this weekend that is interfering with my wow time!

Quote:

---

Originally Posted by Owltoid

Everything seems to be functioning well except the reply to whispers when forwarded from a slave toon. I receive the message but am unable to reply unless I click on the original senders name (ie I can't just reply to my slave and have it be sent to the original sender)

---

So, this seems to be working for me, I've tried with Real ID and normal whispers. In the /jamba-talk settings, make sure you have selected "Forward via fake links for clickable links and players" and "Add forwarder to reply queue on master".

Quote:

---

Originally Posted by ElectronDF

If my team has people that are offline, Jamba makes it seem like there are people that are not friends or are strangers, so it puts the loot as group loot. If you take the people that are offline out of the group, it work like expected.

---

I can't reproduce this. Are your offline team members still listed in the Jamba Team list? If they are not they will appear to be strangers.

So a list of fixes I have made but not yet released:

• Mounts will now work in the item bar.
• New slash command for Toon: Currency > /jamba-toon currencyhide
• Toon: Currency now shows correct labels for Ironpaw Tokens and Epicurean's Award
• Autoselect quest will now work if one or more quests in the NPCs list are still incomplete.
• Autocomplete quest will now work if the NPC has non-quest related functions.
• Fixed a bug where auto select / complete quests were missing an additional parameter to a wow api function (that was added in MOP).
• Fixed taint issue where team list would try and draw in combat (upon master switch if team list not already showing).
• Fixed taint issue where item bar would try and draw in combat (upon master switch item bar not already showing).

You can follow progress along here:

https://trello.com/board/jamba/5042d7856fc039ef1b37b44b

:-)

Jafula,
is there a fix for currently not showing up on master as a default when checked and group loot not set to FFA?

Got a request regarding jamba procc, I'm currently playing enhancement shamans and jamba procc always shows me maelstorm ready when one charge proccs, but I think its way more usefull if it only shows up when you got 5 charges, could you change it that way?

Code:

---

320x [ADDON_ACTION_BLOCKED] AddOn "!Swatter" tried to call the protected function "SecureHandlersUpdateFrame:SetAttribute()".
!BugGrabber-r188\BugGrabber.lua:587: in function <!BugGrabber\BugGrabber.lua:587>
<in C code>
FrameXML\SecureHandlers.lua:690: in function <FrameXML\SecureHandlers.lua:677>
(tail call): ?
Jamba-beta-1.0beta3\LibActionButtonJamba-1.0-20.lua:446: in function "UpdateState"
Jamba-beta-1.0beta3\LibActionButtonJamba-1.0-20.lua:429: in function "SetState"
Jamba-ItemUse-beta-1.0beta3\JambaItemUse.lua:315: in function "UpdateItemsInBar"
Jamba-ItemUse-beta-1.0beta3\JambaItemUse.lua:693: in function "SettingsRefresh"
Jamba-ItemUse-beta-1.0beta3\JambaItemUse.lua:757: in function "?"
libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:147: in function <libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
<string>:"safecall Dispatcher[2]":4: in function <string>:"safecall Dispatcher[2]":4
<in C code>
JambaTeam.lua:780: in function "ReceiveCommandSetMaster"
Jamba-beta-1.0beta3\JambaTeam.lua:1453: in function "JambaOnCommandReceived"
Jamba-beta-1.0beta3\JambaCore.lua:339: in function "OnCommandReceived"
Jamba-beta-1.0beta3\JambaCommunications.lua:408: in function "?"
libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:147: in function <libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
<string>:"safecall Dispatcher[4]":4: in function <string>:"safecall Dispatcher[4]":4
<in C code>
<string>:"safecall Dispatcher[4]":13: in function "?"
libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:92: in function "Fire"
DataStore-r37\libs\AceComm-3.0\AceComm-3.0-7.lua:339: in function <DataStore\libs\AceComm-3.0\AceComm-3.0.lua:321>

Locals:
nil

---

Code:

---

4x [ADDON_ACTION_BLOCKED] AddOn "Jamba-ItemUse" tried to call the protected function "JambaItemUseWindowFrame:Show()".
!BugGrabber-r188\BugGrabber.lua:587: in function <!BugGrabber\BugGrabber.lua:587>
<in C code>
Jamba-ItemUse-beta-1.0beta3\JambaItemUse.lua:276: in function "SetItemUseVisibility"
Jamba-ItemUse-beta-1.0beta3\JambaItemUse.lua:692: in function "SettingsRefresh"
Jamba-ItemUse-beta-1.0beta3\JambaItemUse.lua:757: in function "?"
libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:147: in function <libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
<string>:"safecall Dispatcher[2]":4: in function <string>:"safecall Dispatcher[2]":4
<in C code>
<string>:"safecall Dispatcher[2]":13: in function "?"
libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:92: in function "SendMessage"
Jamba-beta-1.0beta3\JambaTeam.lua:579: in function <Jamba\JambaTeam.lua:566>
Jamba-beta-1.0beta3\JambaTeam.lua:780: in function "ReceiveCommandSetMaster"
Jamba-beta-1.0beta3\JambaTeam.lua:1453: in function "JambaOnCommandReceived"
Jamba-beta-1.0beta3\JambaCore.lua:339: in function "OnCommandReceived"
Jamba-beta-1.0beta3\JambaCommunications.lua:408: in function "?"
libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:147: in function <libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
<string>:"safecall Dispatcher[4]":4: in function <string>:"safecall Dispatcher[4]":4
<in C code>
<string>:"safecall Dispatcher[4]":13: in function "?"
libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:92: in function "Fire"
DataStore-r37\libs\AceComm-3.0\AceComm-3.0-7.lua:339: in function <DataStore\libs\AceComm-3.0\AceComm-3.0.lua:321>

Locals:
nil

---

Currently running the beta release Jamba addon, I am still rather new and may just be doing something wrong. I have noticed however that no matter which team I bring online, if I do not push the jamba settings for the team section at each login, the follow command does not work on any of the characters.. As soon as I push the settings though everything works fine. I have the = hotkey slot set on each slave with the command: /jamba-follow master. Its as if they don't recognize the main toon as master until I push the settings even though when I open up jamba on the slave screens it shows my main toon is master. Outside of that the only other consistent thing I have noticed is the currency window opens by default on all toons even though I have it set on all toons to open on start up for master only.

Quick update - a release 1.0 has gone out on curse.com with the latest bug fixes (to be documented later). Please note that the item bar and battlepets are not getting along (but there shouldn't be any lua errors).

thx for the update, using it now, so far so good. I also figured out the issue with the master resetting .. turns out isboxer was overriding the settings.

I've been using the 1.0 release for a little over 20 hrs now between three different teams. Excellent job Jafula. The only errors I've had occur were related to other addons and I was able to quickly resolve them.

The only issue I continue to have I also had with the beta version. Quest tracker is showing the wrong number of characters that are on a quest. If all five characters have a quest it will show 2/5 until I open the quest window and press "track all". I don't think it's a conflict with another addon, latency issue maybe? quest are being accepted to quickly when I IWT? I tried to make a macro so I wouldn't need to open the quest window after each quest but nothing I tried worked (/jamba-quest-watcher-track all, etc). Other than this small issue it's worked flawlessly for me.

I'm on 1.0 also and having an issue with the quest watcher. Sometimes, when I complete a quest with all toons, it gets left in the tracker for some of the other toons. I can resolve this by switching to each toon and clicking "update" at the top, so it's not a big deal. Just a bit annoying.

Quote:

---

Originally Posted by Criels

Quest tracker is showing the wrong number of characters that are on a quest. If all five characters have a quest it will show 2/5 until I open the quest window and press "track all". I don't think it's a conflict with another addon, latency issue maybe? quest are being accepted to quickly when I IWT? I tried to make a macro so I wouldn't need to open the quest window after each quest but nothing I tried worked (/jamba-quest-watcher-track all, etc). Other than this small issue it's worked flawlessly for me.

---

Quote:

---

Originally Posted by Bollwerk

I'm on 1.0 also and having an issue with the quest watcher. Sometimes, when I complete a quest with all toons, it gets left in the tracker for some of the other toons. I can resolve this by switching to each toon and clicking "update" at the top, so it's not a big deal. Just a bit annoying.

---

I don't know if the quest tracker thing is specifically Jamba. I use TomQuest2 for quest tracking and I see the same behavior at random intervals. Sometimes it won't report everyone having turned in a quest, sometimes it'll randomly reset and stop updating {showing 1 toon at 0/20 when they have some or all already}, sometimes it won't pick up a toon at all.

Leaving party and reinviting fixes it in my case {reloadui works sometimes, but usually not}. A toon crashing or rapid-fire accept/turn-in seem to be the causes. So since it's happening with a different party quest addon too, it does sound like something on Blizz's end.

I have some problem with Jamba with a cross-realm team.
Can you work something to make it use wisp or even party chan instead of the jamba chan when all chars are not on the same server ?

Currently getting this error when using Elv UI and using a potion on the item bar

EDIT: Its anything that has a cooldown, so quest item too

...terface\AddOns\ElvUI\modules\actionbars\cooldow n.lua:147: Usage: GetActionCooldown(slot)
Time: 11/10/12 20:26:42
Count: 8
Stack: [C]: ?
[C]: in function `GetActionCharges'
...terface\AddOns\ElvUI\modules\actionbars\cooldow n.lua:147: in function <...terface\AddOns\ElvUI\modules\actionbars\cooldo wn.lua:121>
(tail call): ?
[C]: in function `SetCooldown'
Interface\FrameXML\Cooldown.lua:4: in function `CooldownFrame_SetTimer'
Interface\AddOns\Jamba\LibActionButtonJamba-1.0.lua:1139: in function `method'
Interface\AddOns\Jamba\LibActionButtonJamba-1.0.lua:686: in function <Interface\AddOns\Jamba\LibActionButtonJamba-1.0.lua:683>
Interface\AddOns\Jamba\LibActionButtonJamba-1.0.lua:764: in function <Interface\AddOns\Jamba\LibActionButtonJamba-1.0.lua:733>

Im having an issue with stobing follow please help. Lately the last few days im runnin my caster team. I always use alt+shift+f (strobing follow) enabled so if i get feared / knockbacked or whatever it will automatically start follow again. After fightin for a while now this stops working and if follow breaks the characters wont automatically begin following. i have to /reload on all characters, turn keymaps off and back on and then hit alt+shift+f again to re enable strobing and then it works again for a while. Any ideas how to fix this or why it is happening?

I've seen this mentioned one or two other times, but haven't seen an answer. My JAMBA feature for "Automatically set loot to:" isn't working. I have it set to free-for-all, but it never changes. Not a big deal in the least, because I'm capable of switching from group loot myself, but I do sometimes forget after having to do a console reloadui or something. Just wondering if this has been addressed and I'm not seeing it. Jamba is an amazing piece of software.

So how do I get the item use bar to update? When it fills up with quest items it stops updating with the newest item. Any idea if that is how it is supposed to work?

Quote:

---

Originally Posted by Multibocks

So how do I get the item use bar to update? When it fills up with quest items it stops updating with the newest item. Any idea if that is how it is supposed to work?

---

I don't know if this is intended or not. For as long as I remember using this feature, I've just dragged a quest item out of the bar to clear it when I'm done with it and freed up that space for another one. I've never needed more than 2 quest items in the bar at the same time, that I recall. I don't recall an instance where I had all 5 slots full (I only use 5), and had Jamba auto-replace one of the items for me when I got a new quest item.

On occasion (meaning perhaps half the time I log in) I get an error about a chat channel that Jamba creates called "JambaTeamIsOnline" and it asks me for a password. When I looked at the communications .lua file, I see that the password for that chat channel is "JambaTeamPassword" but when I try to enter that it doesn't work.

What this means is that Jamba no longer updates the Team Bar with XP/Health statistics although other aspects of Jamba appear to be working.

Anyone else experience that? Suggestions?

Quote:

---

Originally Posted by Gomotron

On occasion (meaning perhaps half the time I log in) I get an error about a chat channel that Jamba creates called "JambaTeamIsOnline" and it asks me for a password. When I looked at the communications .lua file, I see that the password for that chat channel is "JambaTeamPassword" but when I try to enter that it doesn't work.

What this means is that Jamba no longer updates the Team Bar with XP/Health statistics although other aspects of Jamba appear to be working.

Anyone else experience that? Suggestions?

---

Just change it. Under
Jamba > Advanced> Core:Communications change the channel name and channel password on every toon to something else. Log out for a few seconds and log back in.

Is there any way to resize the option window ? For some reason I often get stuck with this : http://i.imgur.com/C0KBt.jpg and I can only fix it by deleting the WTF folder

I only had Jamba active and I often switch between Window(FullScreen) and Window mode ( I know the switch also affects recount size and some other addons size)

Will there be an update soon?

Quote:

---

Originally Posted by Auddax

Is there any way to resize the option window ? For some reason I often get stuck with this : http://i.imgur.com/C0KBt.jpg and I can only fix it by deleting the WTF folder

I only had Jamba active and I often switch between Window(FullScreen) and Window mode ( I know the switch also affects recount size and some other addons size)

---

Grab the latest Jamba - 5.1.1 and try the new slash command:

/jamba resetsettingsframe

Let me know if that fixes it for you!

Quote:

---

Originally Posted by drarkan

Will there be an update soon?

---

Is now ok? :o

New thread for Jamba and new release. Woot! Updates for WoW 5.1 have just been posted on curse.com.

http://www.dual-boxing.com/threads/4...release-thread

(Moderators, please leave this one open for a bit longer, I'll close it when I'm done with it.)