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

[Igg]

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

[Kruschpakx4]

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?

[Tin]

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

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

[CyberThug]

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.

[Jafula]

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).

[CyberThug]

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.

[Criels]

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.

[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.

[Khatovar]

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.

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.

[Baltyre]

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 ?