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

[Frosty]

Here's an idea for an addition to Jamba...

I've only been multiboxing for a few days, but I've already spammed guildchat with accidental chat from all characters a few times. Some people in the guild find it annoying. :whistling:

So would it be possible to stop all messages to /g from all character but the master? I know I could remove them from the guild, but then I'd not be able to see /g when I switch main.

If you are using keyclone, add Enter/Return to your do-not-pass list. You might also want to use the Mute/Pause button before chatting with anyone.

[Jafula]

First up, Jamba-Quest 0.2 is a lot better than it is in 0.1a (IMHO).

So, I've been doing a little testing on Jamba-Quest.

Without any "questing" addons, seems fine.

With the following "quest" addons installed: QuestHelper, CarboniteQuest, QuestsFu, MobMap (as well as Cartographer, full Auctioneer, Bartender 4, X-Perl Unit Frames, Jamba, DevTools, some others).

Small Problem

The "problems" are mainly to do with the quest log; accepting/declining/completing quests from npcs seems fine.

When I select a quest ... no delay.

When I abandon a quest ... delay of about 10 seconds. I watch my quest log get "parsed" twice, so the slaves run through all the quests they have twice. This is because those addons are calling select quest behind the scenes and Jamba hooks this functionality. I have tried to accept a quest immediately after this; and have had to wait for the other addons to finish "parsing" before the slaves would accept the quest.

I have described fixes in previous posts to help with the delay. I have another proposal.

Proposed Solution

Edit: Made a Jamba-Quest GUI instead after feedback from beta testers. All delay problems solved.

[s]I'm going to add an option to only send commands to slaves when modifier keys are pressed. For instance, only send select quest, abandon quest, quest watch commands when ctrl and alt are pressed. This is going to default to off. You can choose the modifier keys (alt, ctrl, shift - either or left or right).

So you run Jamba-Quest (0.2); if you find you get unacceptable delays, you can turn on the "Only send commands if modifier key pressed" option. Then you have to remember to have the modifier keys pressed when doing select, abandon, watch commands. (And you must remember to select before abandon...)

Should I apply this "modifier key down" only to the quest log or to the npc quest interactions as well?

This solution is for YOU. (I personally won't be using it.) Is this an acceptable solution for those who plan to use Jamba-Quest? Would you use it?

Please comment if you can spare the time. [/s]

Thanks, Jafula.

[Moorea]

sounds like a good compromise; hopefully it can work by default with reasonably low delays (I use questhelper only on the main toon)


> Should I apply this "modifier key down" only to the quest log or to the npc quest interactions as well?

I would say only quest log if the npc quest interactions mostly work (and that can be turned off if not)

[Ughmahedhurtz]

I'll be happy to beta test that change if you'd like.

[Griznah]

jafula:
I'm sorry, I haven't played WoW today, so haven't been able to try the pre2, but changes sounds nice. Pre1 wasn't too bad, fixed a lot. I had some trouble figuring out what all the options were tho..

[Metalocalypse]

Yes, its been developed and coming in 0.2.

/jamba setmaster <target> <tag>

and

/jamba setmeasmaster <tag>

The command is typed/macroed on one toon and all the toons with the tag supplied execute the command as well. There is a default tag of "all" for each toon. You can add your own tags as well.

I'm guessing that in your case, you add "/jamba setmeasmaster all" to your switch macro on each character. Easy.

Jamba can do this IN combat.

Another addition you might like is the ability to send messages/warnings to a private channel. So all your toons have the channel in a chat frame and all the messages/warnings go to that channel. Or party chat or guild chat.

Will this also allow me to setup my partyleader like a /pr <me> command? I mean I understand that this will set the 'jambamaster', but would jamba be able to promote the master to party leader if one of the other jamba members is able to promote?
Either way I think I'll find this addition simply awesome.

[Jafula]

Here's an idea for an addition to Jamba...

I've only been multiboxing for a few days, but I've already spammed guildchat with accidental chat from all characters a few times. Some people in the guild find it annoying. :whistling:

So would it be possible to stop all messages to /g from all character but the master? I know I could remove them from the guild, but then I'd not be able to see /g when I switch main.

I think Frosty answered that question for you. I don't think I'd easily be able to override what was sent to guild chat if I did try and implement such a thing.

I loaded this up last night and my mouse started doing "Stupid mouse tricks". It would just stop and then jump to another portion of the screen. I run two boxes with Mutliplicity and Hotkeynet, the primary(Master) machine has on monitor and the "Slave" machine has 2 monitors. I'll try it again this evening but I was wondering if anyone else has seen this happen.

Anyway great work Jafula :thumbsup:

Only stupid mouse tricks I get are on one machine and with hotkeynet. I've had the cursor jump a few times on my slaves (seperate monitor) but never on my main.

Will this also allow me to setup my partyleader like a /pr <me> command? I mean I understand that this will set the 'jambamaster', but would jamba be able to promote the master to party leader if one of the other jamba members is able to promote?
Either way I think I'll find this addition simply awesome.

Not yet, but PromoteToLeader does not seem to be a wow api protected function so I could add that as an option to Jamba-Group in 0.3 for you. Do you want it so that it automatically happens when you change the master (as an option); or a seperate "/jamba setmeasleader <tag>" command?

[zanthor]

I think Frosty answered that question for you. I don't think I'd easily be able to override what was sent to guild chat if I did try and implement such a thing.

There was another mod running about that squelched ALL outbound chat from alts. Also unless sendchatmessage is protected you could do an old fashioned hook...

http://www.wowwiki.com/API_SendChatMessage

I haven't done UI Dev in a while but I believe it would be something akin to:

local function MySendChatMessage(msg, chatType, language, channel)
 	if(LeaderFlagSet) then
      	Blizz_SendChatMessage(msg, chatType, language, channel);
 	end
end
Blizz_SendChatMessage = SendChatMessage;
SendChatMessage = MySendChatMessage;

Of course I'm sure this is dirty code somehow, some best practice against doing it this way, etc etc... but my 12 seconds of typing and 3 seconds of testing didn't find any errors ...

[Dooz]

Hey Jaf,
Downloaded / installed beta. I didn't delete old Jamba, wasn't sure if you wanted me to do this or not. Beta works with all my mods, no lua errors. Pushed tags from my main to slaves, worked perfectly. Slaves auto follow after combat :thumbsup: . Still playing with the focus master. Abandon quests didn't work.... even with quest silently on I still got caught in a mountain of spam. I had the questlog open on all toons and it cycled through all my quests on each toon every time I tried to abandon a quest from my main. I tried to abandon with the questlog open on the master and closed on all others, and got the same thing. I took a screeny of it and i'm going to put it in my gallery. My main had the "Master" tag; and all other toons had a "Slave" tag. Invite Group, Disband group worked perfectly. Set loot to free worked. Auto accept res worked too.

I'll spend a little more time with it in the morning.

[Jafula]

Hey Jaf,
Downloaded / installed beta. I didn't delete old Jamba, wasn't sure if you wanted me to do this or not. Beta works with all my mods, no lua errors. Pushed tags from my main to slaves, worked perfectly. Slaves auto follow after combat :thumbsup: . Still playing with the focus master. Abandon quests didn't work.... even with quest silently on I still got caught in a mountain of spam. I had the questlog open on all toons and it cycled through all my quests on each toon every time I tried to abandon a quest from my main. I tried to abandon with the questlog open on the master and closed on all others, and got the same thing. I took a screeny of it and i'm going to put it in my gallery. My main had the "Master" tag; and all other toons had a "Slave" tag. Invite Group, Disband group worked perfectly. Set loot to free worked. Auto accept res worked too.

I'll spend a little more time with it in the morning.

Thanks for the updates Dooz. Glad that most of it is working! I believe I have solved the spam / delay problem. I couldn't do much about the spam, as it was being caused by Jamba hooking functions that other addons used a lot. So what I have done now is change the way the quest log changes go from master to slave.

You select a quest on the master and it gets noticed by the Jamba-Quest gui (see image below). Then you have four commands you can tell your slaves. Select, abandon, add and remove watch. If you click abandon / watch the master will do the action as well (to save having to click twice).

You can show and hide the jamba-quest GUI with the command

/jamba-quest show

I've PM'd you a link to the new beta with this system in it. Now there is no repeated spam being sent; and I hope all the delay problems are gone. No more watching your toons cycle through all their quests! Yay!