WowAce

Please don't, as alliance on a horde dominated pvp server sometimes it's necessary to hop in a group to realm hop just to turn the emissary quest in, or complete a regular quest. The auto-kick features just makes a bad situation even more impossible.

you taking up a spot in my group because you CHOOSE to play on a pvp realm isn't my concern.  realm hoppers suck!.

also updated to beta to check it out, thanks :)

Suggestion: Can you make an option where you can queue your current group to a WQ? My spouse and I usually group up together and occasionally like to have other join us for more difficult, or time-consuming WQs.

There should be a way to temporarely ban a specific group/leader or let me manually look for a specific WQ group when needed. Sometimes there is a leader that is either AFK or not even in the questing zone. If I leave the party and search again, even if there are more groups, this same leader will be the "first apply" and I'll end up joining his team again. This is specially bad when trying to do WQ outside daily cache's rotation, as there will be less people joining these specific WQ.

Yes, so much this! Reasons for having to look for another group are multiple, one I find to happen most often is some folks just troll others and convert groups into raids, hence quest objectives can't be completed. Or pve characters are joining pvp realms and low level alts just get one shotted. I just came here to ask to add "search next group" button like it is in the other group finder addon. If we leave, and click the search group button again, we're most likely about to get in to the same group we just left.

On raid night, as raid lead, I am having to disable this add-on.  I click on the "invite members" from the calendar and it immediately converts back to party, kicks everyone except the a "party's worth".

I presume this has something to do with some world quests allowing 5 players vs. raid sizes.

I'm not sure if the add-on can distinguish the difference, but annoying to have to disable an add-on just to raid.

Getting this LUA error (it doesn't mention WQA explicitely, but it happens when using the automation keybind while already queued for something else  (e.g. for a BG).

39x FrameXML\LFGList.lua:2094: attempt to perform arithmetic on local 'appDuration' (a nil value)
FrameXML\LFGList.lua:2094: in function `LFGListSearchEntry_Update'
FrameXML\LFGList.lua:2164: in function <FrameXML\LFGList.lua:2160>

Locals:
self = LFGListSearchPanelScrollFrameButton4 {

...

And another one - this time without context, but its triggered from within WQA:

1x WorldQuestAssistant\core.lua:378: attempt to index local 'bi' (a nil value)
WorldQuestAssistant\core.lua:378: in function <WorldQuestAssistant\core.lua:375>

I am using the addon on multiple characters and noticed that I have to reconfigure/copy settings when using it on a new char because it always starts out with a char specific profile.

Would it be possible to make the default profile default? (pun intended :) )

Love this addon a lot! It's a lot sleeker than WQGF and more compact with the buttons all being right next to the quest itself.  Not sure if WQGF had the "Leave party when flying" or not, but I love being able to do it with WQA. 

The only gripe I have, and I see that it's getting fixed, is the PvP realms not always being blocked when I toggle the block option. It's normally fine, but when doing Legion Invasions on my alts, people will one shot and grief pretty often. 

Overall an amazing addon!

Wouldnt that prevent pvp realms characters from joining pve realms based groups?