Jamba 0.5 available for testing (Update 12).

[Jafula]

Yep. Still getting spammed with either the last accepted quest or (if I just logged in) empty accepted quest as in the pic. ONLY does it if I use my accept macro.

/script --/click SmartBuff_KeyButton
/console Sound_EnableSFX 1

/script AcceptGroup();
/script AcceptQuest();
/script AcceptTrade();
/script RetrieveCorpse();
/script RepopMe(); 
/focus dondeltoro

/in 5 /script StaticPopup_Hide("PARTY_INVITE")
/in 5 /script StaticPopup_Hide("QUEST_ACCEPT")
/in 5 /script StaticPopup_Hide("CONFIRM_SUMMON") 

/script SelectGossipOption(1)

You are getting this spam when you use your accept macro, because you have /script AcceptQuest() in it. I have no way of knowing that this AcceptQuest is coming from your macro and not a genuine WoW call.

Re: the accept quest spam on login. I'm guessing there is another addon that iterates all the quests when you log in and somehow Jamba is getting caught up in it. I'll have a closer look.

[Jafula]

Things I would like to know:

1) Have you had any crashes using 0.5 update 2 with regards to taxis?

2) Does 0.5 update 2 fix all your channel problems?

[Ughmahedhurtz]

Things I would like to know:

1) Have you had any crashes using 0.5 update 2 with regards to taxis?

2) Does 0.5 update 2 fix all your channel problems?

I haven't had any taxi crashes with 0.5 at all, though I've not paid specific attention to it.

Regarding the channel problems, I've been leaving it default and leaving it alone. I'll go play with that some tomorrow after some sleep.

[Jafula]

I haven't had any taxi crashes with 0.5 at all, though I've not paid specific attention to it.

Regarding the channel problems, I've been leaving it default and leaving it alone. I'll go play with that some tomorrow after some sleep.

Mmmmm, sleep ...

[Ughmahedhurtz]

You are getting this spam when you use your accept macro, because you have /script AcceptQuest() in it. I have no way of knowing that this AcceptQuest is coming from your macro and not a genuine WoW call.

Ya know, you're absolutely right. I'll just pull that line because Jamba does that stuff so well that the only time it doesn't, I forget I even had a keybind for it and just end up using mouseclick broadcasting. :P

[Jafula]

Ok, I had this happen again twice now. Once in a raid, once in a heroic. The raid time did "Raid1 is not a valid party member".......etc.

It appears to happen most when I enter / exit an instance. And its not on all WoW installs, just one or two randomly.

It doesn't appear to do any harm - its just something I noticed.

Thanks! The raid1 gives me a big clue to where the problem is happening. Cheers for the feedback!