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

[Tutunkommon]

Not to be overly negative, but I downloaded 0.6 and upgraded from 0.4g today. I just finally got frustrated to the point that I managed to find a copy of 0.4g to go back to and did so happily. A short list of what I was struggling with, offered as a list of starting points for debugging.

1: All my settings were lost going from 0.4 to 0.6. Worse, when I went back to 0.4 everything was lost again (the original 0.4 settings apparently were destroyed by 0.6)

2: It was a lot of work to get my team added and showing up on everyone's list. I built the team on the master and added just the master to everyone else. This was the same as 0.4g. When I "pushed" to the team, however, nothing happened. This was because everyone (including the master!) was showing up as offline in the master's list. (Dont understand how the master can ever show himself as offline.) I did some reading, renamed the channel, made sure that everyone was appearing in the channel list, added to slaves to the master's 'friend' list, and it sort of started working.

3: The team list that is supposed to show everyones XP (and now health too!). I had values and percentage both turned on. Everyone had 100/100 (100%) XP and health. Except the master. For whatever reason, the master never showed up in the team list.

4: As I came in for a landing from a flight path, all but one of the slaves got D/C'ed. When I logged everyone back in, the master never saw the connected toon as logging back in (because it never logged out). This caused that toon to show Offline in the team list. Guess who never received and invites, and never showed on the team list?

--Items 2 and 4 lead me to think that the code is trying to be too 'clever', and only send data / commands to toons that it determines are online. The problem is that it is frequently wrong in that assessment, and there is no easy way to tell it that those toons are actually there. Code that ignores me because it thinks it is smarter than me is frustrating...

5: The quest watcher puts a large, invisible frame across the center of the screen. This interfered with the mouse when I try to click-drag to adjust my camera view. I had to click off to the side of the screen. in order for it to register.

I still think Jamba is practically required to multi-box properly, and can't imagine trying to play without it. That is why it was so frustrating when so many things didn't work properly. Luckily, I had a working version that I was able to revert to so I can continue to play.

[Maxion]

Not to be overly negative, but I downloaded 0.6 and upgraded from 0.4g today. I just finally got frustrated to the point that I managed to find a copy of 0.4g to go back to and did so happily. A short list of what I was struggling with, offered as a list of starting points for debugging.

1: All my settings were lost going from 0.4 to 0.6. Worse, when I went back to 0.4 everything was lost again (the original 0.4 settings apparently were destroyed by 0.6)

2: It was a lot of work to get my team added and showing up on everyone's list. I built the team on the master and added just the master to everyone else. This was the same as 0.4g. When I "pushed" to the team, however, nothing happened. This was because everyone (including the master!) was showing up as offline in the master's list. (Dont understand how the master can ever show himself as offline.) I did some reading, renamed the channel, made sure that everyone was appearing in the channel list, added to slaves to the master's 'friend' list, and it sort of started working.

3: The team list that is supposed to show everyones XP (and now health too!). I had values and percentage both turned on. Everyone had 100/100 (100%) XP and health. Except the master. For whatever reason, the master never showed up in the team list.

4: As I came in for a landing from a flight path, all but one of the slaves got D/C'ed. When I logged everyone back in, the master never saw the connected toon as logging back in (because it never logged out). This caused that toon to show Offline in the team list. Guess who never received and invites, and never showed on the team list?

--Items 2 and 4 lead me to think that the code is trying to be too 'clever', and only send data / commands to toons that it determines are online. The problem is that it is frequently wrong in that assessment, and there is no easy way to tell it that those toons are actually there. Code that ignores me because it thinks it is smarter than me is frustrating...

5: The quest watcher puts a large, invisible frame across the center of the screen. This interfered with the mouse when I try to click-drag to adjust my camera view. I had to click off to the side of the screen. in order for it to register.

I still think Jamba is practically required to multi-box properly, and can't imagine trying to play without it. That is why it was so frustrating when so many things didn't work properly. Luckily, I had a working version that I was able to revert to so I can continue to play.

Pretty sure settings were carried over when I upgraded my Jamba, but I had been getting every version in between and not done such a large version jump.

To quickly add a team, invite everyone to a group, and broadcast the command /jamba-team addparty

Make sure everyone has the correct channel and password set, then relog after broadcasting.

Give Jamba time to load the xp bars etc upon logging in, if you start doing stuff too fast, they sometimes get stuck at 100%.

Make sure to do "/jamba-team iammaster all" on the master after loading and inviting.

if it bugs after a dc, try relogging those characters, though fixing the stuff above should take care of it.

Alt-click and drag to get the quest watcher out of the way, or just disable it in the settings (as I have until they make it possible to click stuff behind it).

[valle2000]

I guess many others also use the click-to-move option on their slaves (in combination with interact you can make slaves run toward mobs/npcs). However it annoys me to have this activated on my master, since it's so easy to by mistake click on the ground.

So my question/wish is; In jamba you have an option to set focus to master. Would it be possible to add a sub option to "Automatically activate click-to-move on slaves and inactivate it on master"?

The commands to manually set this are, to turn it on:
/run ConsoleExec("Autointeract 1")

To turn it off:
/run ConsoleExec("Autointeract 0")

What do you think of this idea? And would it be possible to implement this in jamba?

[Maxion]

I guess many others also use the click-to-move option on their slaves (in combination with interact you can make slaves run toward mobs/npcs). However it annoys me to have this activated on my master, since it's so easy to by mistake click on the ground.

So my question/wish is; In jamba you have an option to set focus to master. Would it be possible to add a sub option to "Automatically activate click-to-move on slaves and inactivate it on master"?

The commands to manually set this are, to turn it on:
/run ConsoleExec("Autointeract 1")

To turn it off:
/run ConsoleExec("Autointeract 0")

What do you think of this idea? And would it be possible to implement this in jamba?

I use click to move on my slaves but not my master, but I don't spend enough time with another master to where I'd want to change the click to move settings for it, but if I did I'd just include those lines in my master changing macros.

[Yopie Ismypie]

The best add on for wow boxers, now I wish someone was able to make something for Eve!

[Jafula]

I guess many others also use the click-to-move option on their slaves (in combination with interact you can make slaves run toward mobs/npcs). However it annoys me to have this activated on my master, since it's so easy to by mistake click on the ground.

So my question/wish is; In jamba you have an option to set focus to master. Would it be possible to add a sub option to "Automatically activate click-to-move on slaves and inactivate it on master"?

The commands to manually set this are, to turn it on:
/run ConsoleExec("Autointeract 1")

To turn it off:
/run ConsoleExec("Autointeract 0")

What do you think of this idea? And would it be possible to implement this in jamba?

I like it, here's a ticket and its on the todo list:

http://wow.curseforge.com/addons/jam...vate-click-to/

[Ghallo]

I know it has been a while (I submitted the request in Feb) but have you had a chance to look at the Jamba Tag request I posted (I believe it is bug #75). Thanks for the great addon!

[Jafula]

I know it has been a while (I submitted the request in Feb) but have you had a chance to look at the Jamba Tag request I posted (I believe it is bug #75). Thanks for the great addon!

Sorry Ghallo, it completely slipped my mind.

http://wow.curseforge.com/addons/jam...dd-and-remove/

I'll put it in for next release.

P.S. If you have other requests like this that I've said I'd do, best to bug me every couple of weeks, or leave subtle hints around like Maxion does.

[Jafula]

Not to be overly negative, but I downloaded 0.6 and upgraded from 0.4g today. I just finally got frustrated to the point that I managed to find a copy of 0.4g to go back to and did so happily. A short list of what I was struggling with, offered as a list of starting points for debugging.

Thanks for taking the time to post this.

1: All my settings were lost going from 0.4 to 0.6. Worse, when I went back to 0.4 everything was lost again (the original 0.4 settings apparently were destroyed by 0.6)

Shouldn't have happened, I changed the variable the settings get saved to when I moved from 0.4 to 0.5. Sorry about that.

2: It was a lot of work to get my team added and showing up on everyone's list. I built the team on the master and added just the master to everyone else. This was the same as 0.4g. When I "pushed" to the team, however, nothing happened. This was because everyone (including the master!) was showing up as offline in the master's list. (Dont understand how the master can ever show himself as offline.) I did some reading, renamed the channel, made sure that everyone was appearing in the channel list, added to slaves to the master's 'friend' list, and it sort of started working.

Yay! It works!

3: The team list that is supposed to show everyones XP (and now health too!). I had values and percentage both turned on. Everyone had 100/100 (100%) XP and health. Except the master. For whatever reason, the master never showed up in the team list.

Re: XP and Health at 100% on load. This is normal. You need to buff / attack someone for the status bars to update. The master should have been in the team list, though...

4: As I came in for a landing from a flight path, all but one of the slaves got D/C'ed. When I logged everyone back in, the master never saw the connected toon as logging back in (because it never logged out). This caused that toon to show Offline in the team list. Guess who never received and invites, and never showed on the team list?

Bummer.

--Items 2 and 4 lead me to think that the code is trying to be too 'clever', and only send data / commands to toons that it determines are online. The problem is that it is frequently wrong in that assessment, and there is no easy way to tell it that those toons are actually there. Code that ignores me because it thinks it is smarter than me is frustrating...

Agreed, the code is trying to be clever. You can see the history of why this came about if you read all this thread. I'm going to add an option to "always assume team is online" to the core: communications section, which will solve your frustration.

5: The quest watcher puts a large, invisible frame across the center of the screen. This interfered with the mouse when I try to click-drag to adjust my camera view. I had to click off to the side of the screen. in order for it to register.

I have a fondness for invisible frames! Will see if I can make it less obtrusive.

I still think Jamba is practically required to multi-box properly, and can't imagine trying to play without it. That is why it was so frustrating when so many things didn't work properly. Luckily, I had a working version that I was able to revert to so I can continue to play.

You can also download any of the old versions from here:

http://wow.jafula.com/addons/1-jamba...elease-history

I hope with all these changes I am making that you will give the next version a go.

Jafula.