Jamba 0.5 available for testing (Update 12).

[Ughmahedhurtz]

LOL! OK, just deleted all my settings LUA files and guess what? The UghJamba channel is still connected on all my druids. :P In fact, if I right-click the chat tab, go to Global Channels, I see both UghJamba and JambaTeamOnline channels in there.

[Jafula]

LOL! OK, just deleted all my settings LUA files and guess what? The UghJamba channel is still connected on all my druids. :P In fact, if I right-click the chat tab, go to Global Channels, I see both UghJamba and JambaTeamOnline channels in there.

Thanks for your two posts, they will help when I get to the code...

I use the wow api JoinPermanentChannel which is why the channels hang around and probably part of the problem. My bad.

*Edit* If you are up to hacking, try changing all instances of JoinPermanentChannel to JoinTemporaryChannel in the JambaCommunications.lua file. Characters leave temporary channels when they log out. (I assume I wrote it so that the code tries to join the channel when the character logs in.)
But, the JoinTemporaryChannel might or might not accept a password (two sources of conflicting documentation).

[Ughmahedhurtz]

OK, just resetting things and going through the basic config process again. I changed the JoinPermanentChannel to JoinTemporaryChannel as you suggested.

1. /jamba-team add <member1>, etc. to add all my druids to the team
2. /jamba-team invite, worked OK after I let it "settle" a few seconds.
3. Went into JambaDev-->Core: Communications settings.
4. Changed channel to UghJamba, and pw to Ugh.
5. Push Settings.
6. ERROR: All 5 reset the UI to JambaTeamOnline and JambaPassword in the UI. JambaTeamOnline is the only one that shows up in the UI.
7. Changed it back to UghJamba/Ugh and clicked OKAY to close the settings dialog.
8. Went back into Interface-->Addons-->JambaDev-->Core: Communications, and it's reset back to JambaTeamOnline/JambaPassword again. All alts show offline. Checked global channels and no jamba channels are connected at all anymore.
9. Did a /console reloadui and the default channel is connected (JambaTeamOnline/JambaPassword).

So with the JoinTemporaryChannel thing set up, it doesn't appear to be able to select a non-default channel at all anymore.

[Ughmahedhurtz]

On a related note, how difficult would it be to have Jamba just save all its settings globally? I ask because with the 0.5 dev version, I just add everone to every group and everyone's chat/warning/etc. settings are identical. Would be much easier to set up and copy configs to alt accounts if the only thing that was character-specific was the master setting.

[edit] And frankly, for 0.5 I think I'd not even bother with the Jamba Buy/Sell stuff as FreeRefills and AutoProfitX both handle those so well.

[Jafula]

On a related note, how difficult would it be to have Jamba just save all its settings globally? I ask because with the 0.5 dev version, I just add everone to every group and everyone's chat/warning/etc. settings are identical. Would be much easier to set up and copy configs to alt accounts if the only thing that was character-specific was the master setting.

[edit] And frankly, for 0.5 I think I'd not even bother with the Jamba Buy/Sell stuff as FreeRefills and AutoProfitX both handle those so well.

Global wouldn't be a problem; but I can imagine situations where global might not be suitable for everyone.

I'm going to support profiles, so you should be able to set one team up and then copy profiles and tweak stuff. There will also be a push settings button on the top level Jamba config that will ask each module in turn to push its settings.

I like my version of Jamba buy/sell and have ideas for it, but it is definitely the last on the 0.5 list (I plan to release 0.5 when the Display Team, Follow and Me modules are complete).

[Ughmahedhurtz]

The "profile" thing you mention should fit the bill, as will the global "push settings" thing. Honestly, while I gripe about that, it's still easier than 0.4 and I really only have to do it once per team. I wouldn't consider it a high-priority usability issue.