Jamba 0.5 available for testing (Update 12).

[Ughmahedhurtz]

First thing I'll note is that it is MUCH easier to set up a new team or reset from scratch with this version. The changes to the group/team window are nifty.

[edit1] Hmm. OK, just tried to do the Defending Wyrmrest Temple quest and the slaves would accept the quest but would not select the first chat option in the dialog presented by the Wyrmrest Guardian ("We need to get into the fight. Are you ready?")

[Jafula]

Looks like the modules were in subfolders.

Yes, there are seperate addons now.

You _might_ be able to run Jamba-0.4 and JambaDev in parallel if you wanted to.

I'm keen for feedback on the new team and quest overhaul.

[Ughmahedhurtz]

The config interface is much cleaner, IMO, and seems to be easier to access certain options (more logical?). Haven't had nearly the delays in pushing changes to alts, either.

No issues with the taxi module so far. No issues with accepting quests that I can see. The accept from team/guild works fine, as does the disband/invite stuff.

[edit] Hmm...well, tried to reproduce the issue I mentioned above by chatting with Khadgar in Shattrath but his chat dialogs all work just fine for the group. I'll keep at it and see if I can find another one that doesn't go through.

[edit2] OK, couple of strange things I notice about the Core: Team panel:

• Cannot push a new team's settings to alts until they're already in a group together. Verified this twice, once after setting the group up and seeing it work and then removing all the members and disbanding the party to start over.
  [edit] Settings push does not work at all unless they're in a group. On my paladins, I cannot get the invite button to work either after setting up the new team and then clicking "Disband."
• Invite doesn't work either until you group invite normally.

[edit3] OK, the above two problems do not appear once you save all the changes, get it working like you want, and then do a /console reloadui.

• Removing a member requires two clicks of the "Accept" button on the "Are you sure you wish to remove....." dialog, _except_ for the bottom-most member. Wierd. Also leaves an empty list of slaves unless you remove the bottom-most character.
• Personal preference/usability issue: when you change the comms channel/password, it should ideally try to reconnect using the new settings immediately instead of having to "OK" out of the whole config panel and then go back into it again. Not sure if it's possible but would be nifty.

[edit4]

• The behavior with the previous jamba was that if you selected a gossip option to mount a vehicle (like the dragon for Aces High) your alts would click the gossip only if your main did, so on quests where you cannot mount successfully unless you stagger the mounts, you could click your alts one at a time to mount in sequence. With this jamba, clicking any alt's gossip causes the rest of the alts to click that same gossip item, as if everyone was master. Is this an oops or is this new/intended behavior?

[Jafula]

The config interface is much cleaner, IMO, and seems to be easier to access certain options (more logical?). Haven't had nearly the delays in pushing changes to alts, either.

No issues with the taxi module so far. No issues with accepting quests that I can see. The accept from team/guild works fine, as does the disband/invite stuff.

[edit] Hmm...well, tried to reproduce the issue I mentioned above by chatting with Khadgar in Shattrath but his chat dialogs all work just fine for the group. I'll keep at it and see if I can find another one that doesn't go through.

[edit2] OK, couple of strange things I notice about the Core: Team panel:

• Cannot push a new team's settings to alts until they're already in a group together. Verified this twice, once after setting the group up and seeing it work and then removing all the members and disbanding the party to start over.
  [edit] Settings push does not work at all unless they're in a group. On my paladins, I cannot get the invite button to work either after setting up the new team and then clicking "Disband."
• Invite doesn't work either until you group invite normally.

[edit3] OK, the above two problems do not appear once you save all the changes, get it working like you want, and then do a /console reloadui.

• Removing a member requires two clicks of the "Accept" button on the "Are you sure you wish to remove....." dialog, _except_ for the bottom-most member. Wierd. Also leaves an empty list of slaves unless you remove the bottom-most character.
• Personal preference/usability issue: when you change the comms channel/password, it should ideally try to reconnect using the new settings immediately instead of having to "OK" out of the whole config panel and then go back into it again. Not sure if it's possible but would be nifty.

[edit4]

• The behavior with the previous jamba was that if you selected a gossip option to mount a vehicle (like the dragon for Aces High) your alts would click the gossip only if your main did, so on quests where you cannot mount successfully unless you stagger the mounts, you could click your alts one at a time to mount in sequence. With this jamba, clicking any alt's gossip causes the rest of the alts to click that same gossip item, as if everyone was master. Is this an oops or is this new/intended behavior?

Thanks for the feedback!

I'll check to see why the settings cannot be pushed out of group in the first instance. Likewise for invite. I'll see if I can reproduce the team screen problems you found.

I think I'll be able to reconnect the comms channel when you change it. I'll add a reconnect button to the GUI for this purpose.

Intended change, with Jamba Quest, everyone is a master. In your case, you will have to open the dialogs on each toon seperately.

[Ughmahedhurtz]

Gotcha. I'll keep poking at things while I run my dailies today and let you know if I see anything else worth noting.

Cheers!