[F9thRet]

Just wanted to pop in and say thanks Jafula, for all the new features.

You Rock!

Stephen

[Igg]

Jaf,
I'm getting the issue of not all the team's quests are showing up in the quest watcher even though they all have it.

Anyway I can help you with the debugging of this?

[Maxion]

Originally Posted by Igg

Jaf,
I'm getting the issue of not all the team's quests are showing up in the quest watcher even though they all have it.

Anyway I can help you with the debugging of this?

Make sure they are all set to track the quest, and have the checkmark next to it in the quest log.

[Igg]

Originally Posted by Maxion

Make sure they are all set to track the quest, and have the checkmark next to it in the quest log.

That did it, 2 of my toons didn't have auto quest tracking enabled.

Thanks.

[buzzerbeater]

Hello,

I'm new in here and have some questions.

Is there any Starter Guide for this Addon?

Because my first Problem is, that the slave is never Online.
It doesnt matter which Char I use to try it.

Is it a problem to use Win 7 or start WoW from the same direction? Do I need two wow Folders or wow.exe?

Greets

[TheFallenOne]

Bit of a minor inconvenience since the latest Jamba update, it kind of broke my round-robin setup. Figured I'd check here if there was another way to do it, or if not, if we could get the functionality back.

Basically, here's how my (random example spell) Frost Nova worked. The macro for all toons was:

/castsequence #RRStart#Frost Nova#RREnd#

Then, each toon would be using a different variable set. Toon1 would use variable set FTL1, Toon2 would use FTL2, etc., all with the same macro set.

FTL1 would have RRStart set as:
FTL2 would have RRStart set as: ,
FTL3 would have RRStart set as: ,,
FTL4 would have RRStart set as: ,,,
FTL5 would have RRStart set as: ,,,,

And then the same thing for RREnd, but in reverse order. This means that each toon would end up with a round-robined macro for Frost Nova without any extra work from me!

It worked great, however, this last update has, as far as I can tell, eliminated the ability to use the same macro set with different variable sets on a per-toon basis. I'm stuck to using one variable set per macro set. I *could* duplicate the macro set for each toon and use tags to turn them on for specific toons, HOWEVER, this would cause 5x the data to be included when I "push" macro sets... and it already takes 45 seconds to a minute to push *ONLY* the macro settings with THREE sets. I can't imagine what it would be like with fifteen.

Is there any way to do this still, or could this system be setup again? The easiest way I can think of is allowing the user to duplicate Macro/Variable set entries in the new "Macro" section, using different variable sets for each. That would allow me to set it up properly using tags.

[Jafula]

Originally Posted by TheFallenOne

Bit of a minor inconvenience since the latest Jamba update, it kind of broke my round-robin setup. Figured I'd check here if there was another way to do it, or if not, if we could get the functionality back.

Basically, here's how my (random example spell) Frost Nova worked. The macro for all toons was:

/castsequence #RRStart#Frost Nova#RREnd#

Then, each toon would be using a different variable set. Toon1 would use variable set FTL1, Toon2 would use FTL2, etc., all with the same macro set.

FTL1 would have RRStart set as:
FTL2 would have RRStart set as: ,
FTL3 would have RRStart set as: ,,
FTL4 would have RRStart set as: ,,,
FTL5 would have RRStart set as: ,,,,

And then the same thing for RREnd, but in reverse order. This means that each toon would end up with a round-robined macro for Frost Nova without any extra work from me!

It worked great, however, this last update has, as far as I can tell, eliminated the ability to use the same macro set with different variable sets on a per-toon basis. I'm stuck to using one variable set per macro set. I *could* duplicate the macro set for each toon and use tags to turn them on for specific toons, HOWEVER, this would cause 5x the data to be included when I "push" macro sets... and it already takes 45 seconds to a minute to push *ONLY* the macro settings with THREE sets. I can't imagine what it would be like with fifteen.

Is there any way to do this still, or could this system be setup again? The easiest way I can think of is allowing the user to duplicate Macro/Variable set entries in the new "Macro" section, using different variable sets for each. That would allow me to set it up properly using tags.

I will see what I can do. Its going to be tricky, because the nice, easy way of managing multiple macro sets like you ask means breaking the existing macro sets you already have built....

Here's a ticket for your request:

http://wow.curseforge.com/addons/jam...ultiple-times/

I assume that you are still using an older version because of this.

[TheFallenOne]

Originally Posted by Jafula

I assume that you are still using an older version because of this.

For now I'm still using the newest version and have just removed the round robin functionality, as it's not essential while I'm questing - once I hit 80 (at 74.5 right now) I'll either be downloading an old version or reworking my macros into whatever form works with the current version (since I won't be changing macros much at that point).

[Reglar]

I have a weird issue, just popped up in the last few weeks, no changes that I recall making to jamba.

I have my toons setup to purchase water and reagents when they shop. They now buy 5x as many of them as I needed. When I say 5x the number, it actually does 5 discreet buys, each time buying the amount needed.

I turned off auto-buy to see if it was another mod buying stuff - nothing bought so no other addons doing it

I deleted and re-added the items in case the data was corrupt - no change, still bought 5x what I needed.

I thought maybe there was some party multiplier going on, so dropped and logged out a character, still 5x.

I checked the .lua savedvariables and it looked ok:

            ["merchant"] = {
                ["autoBuy"] = true,
                ["autoBuyItems"] = {
                    ["|cffffffff|Hitem:44605:0:0:0:0:0:0:0:80|h[Wild Spineleaf]|h|r"] = {
                        ["tag"] = "all",
                        ["name"] = "Wild Spineleaf",
                        ["amount"] = 20,
                    },
                },
            },

I checked the purchase module LUA but nothing jumped out at me.

----

I debugged it some more, procedure ProcessMerchantShow is being invoked 5 times. I traced it back, and yes, its being invoked 5 times from the event, so I am at a loss. I checked registration and MERCHANT_SHOW is only registered once.

I guess there's some add-on conflict, I'll experiment more.

----

Update 2 - well its an interaction with ISBOXER, when I enable that mod then 5 purchases are made, if I disable it, normal 1. I'll see what I can dig up and if necessary open an ISBOXER thread on it.

----

Update 3 - I logged onto the ISBOXER chat channel, but Lax didn't have any ideas why it would happen, so back to asking anyone who has ideas...

----

Update 4 - and I found the issue, I had ISBOXER setup with a repair key sequence, and it invoked another key sequence to interact with target, both used broadcast to all, so it was chain broadcasting and each window was getting hit with 5 interact key requests. I changed it to not call the other key sequence and my issue went away.

Not sure why this wasn't happening before but just glad its fixed.

[taurolyon]

Originally Posted by buzzerbeater

Hello,

I'm new in here and have some questions.

Is there any Starter Guide for this Addon?

Because my first Problem is, that the slave is never Online.
It doesnt matter which Char I use to try it.

Is it a problem to use Win 7 or start WoW from the same direction? Do I need two wow Folders or wow.exe?

Greets

Did you put both party members in your team list on both toons? You will need to in order to make sure that JAMBA on both clients update each other and communicate.

I use Win7 x64, and I just reopen the same WOW.EXE each time. You do not need to copy or install a second WoW client.