[Addon] Jamba - An assistant for multiboxers. Old Thread

[blast3r]

[Addon] Jamba - An assistant for multiboxers. 13th Update - 0.4e released.[/url]
I was close with the names - these are from the above link.

/jamba setmeasmaster <tag>
/jamba setmaster <target> <tag>

Forgot about these, you could also put these to use

/jamba setfocusmaster <tag>

/jamba setfocus <target> <tag>

Thanks a lot! Maybe this weekend I will play around with it and see if I can get something to work for me.

[Maxion]

While i know you said you use FTL system, I would recommend using a system that lets you have conditionals in your casting macros that lets them work regardless of whether the toon is the master or not.
Not sure how possible that is to do with a FTL system.

Since I use a focus the leader system, and example of how i macro it would be:

/cast [target=focustarget,exists][target=target,exists][] Lightning Bolt

(i realize the abbreviation of "focus the leader" is FTL too, heh, normally just call it a focus system, but anyway, I assume by FTL you mean focusless targetless leaderless system, which is only useful in hardcore arena pvp)

[Marious]

So like the subject says: Issue with WoW windows crashing when I don't take all the toons on a taxi run. So has anyone experience it at all? I think its related with JAMBA but not sure.

[Diablostar]

Hi guys,
I'm havin an issue with Jamba. I'm running 4 toons from one WoW folder on my slave PC. Each toon uses its own config.wtf. I installed jamba in the addon folder and set up a group with my main char on my main pc. The problem is now that jamba doesn't store the settings when i logout with my toons. So when I login again the only charater in the jamba-core is the char itself. But all the other team members are gone.

I'm using ISBOXER with jamba and I have the Jamba-ISBoxer.lua in my saved variable folder. But that's the only one.


So what do I wrong?

Cheers
d

[Ughmahedhurtz]

So like the subject says: Issue with WoW windows crashing when I don't take all the toons on a taxi run. So has anyone experience it at all? I think its related with JAMBA but not sure.

Same here. Anyone already on a bird crashes to the desktop when the master takes a flight path. If they're not on a bird, you just get the warning about "I cannot figure out where to go" message. You should be able to switch it to solo mode before doing that if you're not all synched up.

/jamba solo

I've been meaning to try that but it's so rare that I do anything to cause the problem that it's not been a priority. :P

[Maxion]

Hi guys,
I'm havin an issue with Jamba. I'm running 4 toons from one WoW folder on my slave PC. Each toon uses its own config.wtf. I installed jamba in the addon folder and set up a group with my main char on my main pc. The problem is now that jamba doesn't store the settings when i logout with my toons. So when I login again the only charater in the jamba-core is the char itself. But all the other team members are gone.

I'm using ISBOXER with jamba and I have the Jamba-ISBoxer.lua in my saved variable folder. But that's the only one.


So what do I wrong?

Cheers
d

Assuming you are running windows vista you need to make sure the permissions on the savedvariables .lua files are set to allow writing.
Either run wow in admin mode (which adds an annoying confirmation box before starting each one),
or set the permissions on the files/folders to allow user/owner/admin to write to them.
(what i do is just set it for the whole wow orwtf folder, so it changes it for everything inside, just remember to do it again after running the game after installing a new addon so its .lua files are there)

[Brandish]

Hmm. Well, as you know, I am enamored by the Battered Jungle Hat as of late. I got another one today, and when I went to sell, off it went... which I've been watching for, and I bought it back and went into /jamba-sell to set the exception and Battered Jungle Hat was already there! All of the proper boxes were checked, but the sell exception was being ignored. I re-added the item, and it returned to working properly (``DID NOT SELL <cherished grey item on excetion list>'') The bug was happening after relogging. Not certain what other info would be helpful in tracking this down.

[Drecan]

I've noticed a few bugs with this addon but haven't used the sell stuff part yet due to the fact that I have a 'sell junk' addon on all my toons and I watch what it sold just because I've always been that way. But honestly I think something should be programmed or tried to be (sorry I would attempt to do it myself but not very good with lua stuff lol I'm a VB type of guy) making the 'master' ignore the 'follow after combat' rule cause it sucks having to get it set up on the master to push it to the others and then forgeting to uncheck that and he just randomly trys to follow one of the slaves lol. if it is an option send me a PM saying i'm dumb lol.

[Jafula]

So like the subject says: Issue with WoW windows crashing when I don't take all the toons on a taxi run. So has anyone experience it at all? I think its related with JAMBA but not sure.

Same here. Anyone already on a bird crashes to the desktop when the master takes a flight path. If they're not on a bird, you just get the warning about "I cannot figure out where to go" message. You should be able to switch it to solo mode before doing that if you're not all synched up.

/jamba solo

I've been meaning to try that but it's so rare that I do anything to cause the problem that it's not been a priority. :P

I was not able to reproduce this on my EU server. Are folks still having problems?

[Jafula]

Hmm. Well, as you know, I am enamored by the Battered Jungle Hat as of late. I got another one today, and when I went to sell, off it went... which I've been watching for, and I bought it back and went into /jamba-sell to set the exception and Battered Jungle Hat was already there! All of the proper boxes were checked, but the sell exception was being ignored. I re-added the item, and it returned to working properly (``DID NOT SELL <cherished grey item on excetion list>'') The bug was happening after relogging. Not certain what other info would be helpful in tracking this down.

Thanks for the bug report. I'll see if I can reproduce the problem.