[quote='Ughmahedhurtz',index.php?page=Thread&postID =120181#post120181]Also, as a follow-up to the delays when group-selecting quest accept/complete/etc., I was able to reproduce it mainly when spam was coming across (xxx does not have quest blah). I did, however, try setting them all to "Silently Quest" or whatever the silent checkbox is. It helped but I was still able to reproduce 5-9 second delays where w/o silent, it was 20-40 seconds. Improved but hopefully your planned updates will resolve the rest of that latency.[/quote]I have Mobmap installed (not updated in a while). On my quest log, if I collapse a quest headers (group), so the quests underneath the header are invisible, I get this spam / delay problem...

Mobmap hooks the QUEST_LOG_UPDATE event. In the handler for this event, Mobmap can call ExpandQuestHeader and CollapseQuestHeader. It also calls SelectQuestLogEntry which is what Jamba picks up on and uses to send a select quest command to the slaves.

Mobmap works when the quest window is hidden. Mobmap is calling ExpandQuestHeader inside a handler for QUEST_LOG_UPDATE; problem is that ExpandQuestHeader causes the QUEST_LOG_UPDATE event to fire, which then calls this handler, which then calls ExpandQuestHeader, causing QUEST_LOG_UPDATE, ... infinite loop (well until you expand all your quest headers).

Jamba goes for a ride on this infinite loop and sends commands to the slaves EVERY UPDATE. Noooooo.... ;( This is what slows all the commands down and is A cause of the delays.

If you are curious install about what events are happening in the background, you can install the [url='http://www.wowinterface.com/downloads/info3999-DevTools.html']devtools addon[/url] . Type /dtevents to see the event listed as they happen.

I could uninstall MobMap; but then all your fine folk might have similar (slightly buggy in certain situation) addons like this as well; so I can't beat this that way. My solution is to only send Jamba quest commands when the quest log frame is visible. (And I don't collapse my headers in my quest logs anymore.)

(Aside: I love MobMap and I mean no offense to Slarti; its a quick fix for Mobmap to stop this and it only happens if you have collapsed quest header groups; its just that MobMap affects Jamba and I'd like to let others know about this problem as you may have the same setup as me.)

If you have MobMap installed and are getting command delays; try and make sure all your quest header groups are expanded.

So I have implemented a rule to only do Jamba-Quest commands when the QuestLogFrame is visible. Which solves the problem! And is a logic thing to do. Coming to you in 0.2. Edit: This does not apply to the slave auto-accept, auto-accept-escort and auto-complete quest options.

Is there any one out there using Jamba-Quest, that has a non-standard quest log or other addons that they think might have similar behaviour?