JAMBA [addon]

[Redbeard]

I would use the options interface and uncheck the "Enable auto quest completion" box which would grey out the entire screen. Then I would push the settings to the slave.

Which would change nothing.

If the command line works and the button doesnt then perhaps theres an issue with the options interface (or just mine).

[Solon]

IIRC I had to set my completion settings as I wished, push, /logout. Worked after login. The last time I set up a new team was quite some time ago though.

[Jafula]

I would use the options interface and uncheck the "Enable auto quest completion" box which would grey out the entire screen. Then I would push the settings to the slave.

Which would change nothing.

If the command line works and the button doesnt then perhaps theres an issue with the options interface (or just mine).

Had a look at the code. The problems you describe come from the selection of the quests rather than the completion part. The completion happens after the selections, i.e. after a quest has been selected. So, the command line I mention earlier will sort you out I think. Stick the toggle version of it in macro and you should be able to stop the auto selection, allowing you to choose which quest to pick and then the completion code can run (so leave the enable completion bit on essentially).

Hope that helps!

[gbremset]

Hi Jafula.

To add to your despair, I am experiencing similar problems as the people before me in this thread.
It is not only auto completion, but what appears to be a quite general problem with quest handling.
In my descriptions below, I sometimes use "click" as a reference to whatever function you use to select/accept/turn in/choose options etc.

I run wow on 1 or 2 computers (5 on 1 or 3+2), all with Jamba 6.2 and Keyclone as my program of choice.

No matter what setup I choose, the problem persists, and even though I've been trying hard to find some kind of logic in it, I'm really struggling to see any connections. The issues almost appear to be completely random, but it appears to get worse and worse the longer I play, and some times I even get error messages (turn-in only)

Quest pickup:
1: Select questgiver on all 5 characters and open interaction.
2: Choose desired quest (or only quest, makes no difference) on master
3: If the problem is there, some times, all slaves select the quest, some times, some slaves select the quest, but mostly none.
4: If the problem did not appear in step 3, some or all slaves will not "click" the accept button.
*** Some times, the slaves even auto collect the quests once I open the questgiver interaction. (But I have not tried your described solution for auto complete issues above)***

Quest turn-in:
1: Select questgiver on all 5 characters and open interaction.
2: Select quest to turn in
3: If there is a problem, some or all of the slaves may not select the quest
4: If reward, select reward and "click" confirm, else "click" confirm.
5: If there is a problem, some or all of the slaves may not select a reward, or select a reward but not "click" confirm.

As mentioned, I have seen error messages related to turn-in, and they all refer to some issues with quest handling, but I have been unable to force it to appear so I can post it here.. I will the next time it comes up.

In addition, and this is recently happened as well, but may possibly have some kind of relation.
I am using a "show-off" macro where my team speaks to eachother, using the /in x /s yyyyyyyyyy method, and towards the end of this macro, I am frequently getting error messages, and my timed /cheer at the end tends to get stuck on my screen. (Toon cheering continously)
To get it back to normal, I have to reload UI, which coincidentally is what I have to do to get the quest problem to go away for a short while too..

I hope I didn't bore you to death with my over-detailed description

Cheers
-Gizmo-

[Jafula]

Gbremset, thanks for the detailed description (and your donation ).

First thing I would do is disable all the other addons except Jamba and take your toons for a run through a few quests and see if the problems occur.

Also, try waiting after you make the first selection (up to 1 minute*) before you click accept to see if the toons that were failing actually catch up. It could be that the addon channel is slow.

Also make sure you push the quest and team settings from your master to all your other toons to make sure they all have the same settings (the settings need to be identical for Jamba to function correctly).

Also note that recently, Blizzard changed the low level quests to auto-accept (nothing to do with Jamba).

* Obviously waiting this long is not an option, but let's try and find out whats going on.

[Jafula]

Ah, also any error messages you get would be helpful (without the list of addons installed preferably).

[gbremset]

Right.. So here are the results from the Norwegian Jury:

(Oh.. I run with a latency of about 60-100ms on all 5, in case it makes any difference)

I disabled every addon except Jamba on all 4 slaves, and left Bartender4 on Main.
In addition, I changed the channel name of the default jamba channel, since you mentioned that it may be slow, it got me thinking that if there are more multiboxers on my server, and they all use the default settings, wouldn't this mean that they all use the same chat channel for communication? (Or have I missed something)

Went to do some questing with the above changes, and everything went perfectly smooth for a little while, then the slaves starts responding slower and slower to my clicks. Particularly quest accept directly after turning in appears very slow. (Quests that does not need new interaction with quest giver) This appears to be pretty consistent.
And the more quests I do, the slower it gets..

After about 10-12 quests, the accepting of quests starts getting slow too. I just accepted the quest "Crowleg" Dan in Howling Fjord, and from the first interaction screen to the actual quest screen (click on the ! line) it took 49 seconds from click on master till the last slave had accepted. Then clicked decline, and back on the quest, and it came up instantly, same with the final "accept" for the quest.

I'm still waiting for the error message to appear, but it has only appeared when turning in the tournament dailies so far, so maybe tomorrow.

I'm gonna be cheeky and add a new question to this as well.. Why does the item bar allow some items, and not let me drop in others?


EDIT: The first freeze came when handing in the quest "Sorlof's Booty" and accepting the quest "Shield of the Aesirites", where the accepting of "Shield of the Aeserites" failed on all 4 slaves (Waited 1.5 minute just to be sure)
EDIT-2: I forgot to mention that I started this test session with the first quest in the pirate camp in Howling Fjord (The quest "Street" cred), and followed through until the end of "A Return to Resting".

[gbremset]

And I finally got the error message, this time on a different toon than before, but it's the same message.

Date: 2010-07-24 12:23:02
ID: 1
Error occured in: Global
Count: 1
Message: Invalid reward choice in GetQuestReward([choice])
Debug:
(tail call): ?
[C]: ?
[C]: GetQuestReward()
Jamba-Quest\JambaQuest.lua:1680: CheckForOverrideAndChooseQuestReward()
Jamba-Quest\JambaQuest.lua:1740: DoChooseQuestReward()
Jamba-Quest\JambaQuest.lua:3012: JambaOnCommandReceived()
Jamba\JambaCore.lua:239: OnCommandReceived()
Jamba\JambaCommunications.lua:353: ?()
...er4\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147:
...er4\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147
[string "safecall Dispatcher[4]"]:4:
[string "safecall Dispatcher[4]"]:4
[C]: ?
[string "safecall Dispatcher[4]"]:13: ?()
...er4\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: Fire()
...erface\AddOns\Jamba\Libs\AceComm-3.0\AceComm-3.0.lua:268:
...erface\AddOns\Jamba\Libs\AceComm-3.0\AceComm-3.0.lua:257

The quest being handed in was "Taking the battle to the enemy" from the Silver Covenant exalted dailies. and the item in question was the "Champion's Writ", but I've also seen it when selecting "Champion's Purse"

[Jafula]

And I finally got the error message, this time on a different toon than before, but it's the same message.

Date: 2010-07-24 12:23:02
ID: 1
Error occured in: Global
Count: 1
Message: Invalid reward choice in GetQuestReward([choice])
Debug:
(tail call): ?
[C]: ?
[C]: GetQuestReward()
Jamba-Quest\JambaQuest.lua:1680: CheckForOverrideAndChooseQuestReward()
Jamba-Quest\JambaQuest.lua:1740: DoChooseQuestReward()
Jamba-Quest\JambaQuest.lua:3012: JambaOnCommandReceived()
Jamba\JambaCore.lua:239: OnCommandReceived()
Jamba\JambaCommunications.lua:353: ?()
...er4\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147:
...er4\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147
[string "safecall Dispatcher[4]"]:4:
[string "safecall Dispatcher[4]"]:4
[C]: ?
[string "safecall Dispatcher[4]"]:13: ?()
...er4\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: Fire()
...erface\AddOns\Jamba\Libs\AceComm-3.0\AceComm-3.0.lua:268:
...erface\AddOns\Jamba\Libs\AceComm-3.0\AceComm-3.0.lua:257

The quest being handed in was "Taking the battle to the enemy" from the Silver Covenant exalted dailies. and the item in question was the "Champion's Writ", but I've also seen it when selecting "Champion's Purse"

Seems like the tourament quests handle things a little differently that the normal quests. When I play WoW, I'm doing some of the tournament stuff, so I'll keep and eye out for this one and try and fix it when I come across it.

If any more non tournament quests exhibit this behaviour, I'd like to know.

[Jafula]

I'm gonna be cheeky and add a new question to this as well.. Why does the item bar allow some items, and not let me drop in others?

I'm not sure, I used a certain type of item box from the Blizzard WoW API that does not consume action identifiers. It seems to have a mind of its own, but I can place most items in it. Spells and actions won't work, but most items will. Do you have an example of item that won't work?