Get an Epic Experience with Premium


Boss Encounters Login to Add Favorites
  • World of Warcraft
  • 1,463 Monthly Downloads
  • Supports: 6.2.0
  • 97,639 Total Downloads
  • Updated 06/23/2015
  • Created 02/07/2013
  • 36 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: Public Domain
  • Newest File: v1.22

About BigWigs_AutoReply

BigWigs [AutoReply] is a 3rd party module for BigWigs that replicates the auto reply functionality found in Deadly Boss Mods. Features include:

  • Works for all encounters in which a BW module is loaded.
  • Ability to filter outgoing whispers and <DBM> auto replies.

I will be on the lookout for problems with the opening of Highmaul this week. I'll do my best to post updates as soon as I can.


  • Update for 6.2


First Previous Page 2 of 3 Next Last
  • #19

    BW_AR is definitely still replying to OQ whispers. I tested it today in LFR, and as soon as the fight started, BW_AR sent out boss notifications to about 7 other oqueue users. (And then ironically, one of them running DBM auto-replied to my BW_AR whisper :P)

    I have the "/bwar filter" option turned off. Is there some other setting I need to have turned on?

    Edit: I can't really do anything to capture the exact strings oQueue is sending, because it automatically hides the whispers, and it signals other users to stop syncing on logout and reloadui.

    I've tried manually setting my broadcast to "(OQ)" but other users don't appear to begin syncing unless an additional command is sent by the addon (which is hidden, of course)

    Last edited by JTF195 on 8/9/2013 6:36:34 PM
  • #18

    They should be completely independent. I'll take a look and see if I can reproduce the problem.

    Edit: I still don't have OQueue, but I tested receiving whispers containing the phrase 'OQ,' during boss encounters and they were ignored with filtering both on and off. I also went through the code themselves and they are entirely seperate. Is it possible that the OQ messages that were broadcast did not contain 'OQ,'? If you can link to a screenshot of this happening I can try and reproduce the exact issue.

    Last edited by kiezo on 7/22/2013 2:51:02 PM
  • #17

    Is this option tied to 

    "/bwar filter"? 

    I like having the filter turned off so I can see my incoming and outgoing whispers, but it seems as though it is sending autoreplies in response to oQueue sync whispers I recieve when I have it off.

  • #16

    in the next version there is an option to ignore messages containing certain strings. As long as all the sync messages contain 'OQ,' it should work fine. 1.09 should be on Curse by the end of the weekend.

  • #15

    Forgot '==nil' in my if statement, but still not working : /


    EDIT: herp derp, should be ~= nil

    Last edited by slybootz on 6/6/2013 2:39:09 AM
  • #14

    Here's some example whispers I took from OQ's forums:

    [17:23:05] [W From] [|Kf57|kPlutonium|k]: OQ,0W,AvuEys,2,premade,G7gUik,cGFjIHJvZiBHQnIA,ITHWBdwGBE8BL4AAAAAAAAAAAAAAAAAABQ7JxHAA,NTY3MjEjdHRhTTswNDtuZWRkaUcA,c2xhZUggMiBkZWVO,A,BAF,#to:Magicsac,#rlm:1,#fr:Pÿle-218

    [17:23:10] [W From] [|Kf57|kPlutonium|k]: OQ,0W,AB4IpV,2,scores,,50EC9C49,108,#to:Magicsac,#rlm:1,#fr:Pÿle-218

    [17:23:20] [W From] [|Kf57|kPlutonium|k]: OQ,0W,AiA3FK,4,premade,GxNZkm,QVRDIHNuZWdydXVC,ITAABV8IAHWB4yAAKAABBiAjAAAAAOmABQ7JxZAA,Njk1MSNuZWdydXVCOzA4MTtuZWdydXVC,LgAA,B,ACG,#to:Magicsac,#rlm:1,#fr:Pÿle-218

    Last edited by slybootz on 6/5/2013 8:35:23 PM
  • #13

    OQ sends messages that are typically hidden to the user, and from what I recall, they always start with the letters OQ (in all caps).

    My lua is very novice, and I was trying to add something like follows, but it wasn't working:

        if string.find(msg, "OQ") then return end

  • #8

    Hi. A request;


    Would like to be able to see how many raiders are alive in the message, just like how DBM's reply works. Thank you!

  • #9

    Should be simple enough - I will add an option for it in the next version.

  • #10

    Thank you very much!

  • #7

    Just to update, I've got a fix almost ready. Just testing a little further to make sure it didn't screw anything else up and then I'll get it on Curse.

  • #5

    Thanks for the new version, but did you notice that there were bugs reported in the CurseForge ticket tracker? I didn't test it yet with the new version, but from looking over your code changes it seems that at least bug 1 is still there in the new version since AR:ReportRaidDifficulty() returns nil when not in an instance.

  • #6

    Just noticed it actually- been busy with finals the past few weeks. Should have a fix out in a few hours.

  • #3

    needs to send the message without showing the message, the same way DBM does it, and just print something that says it auto responded. but that's just what i think.

  • #4

    Thanks for the feedback - I've got something like this implemented in the next version that I'm currently testing. Look out for it soon. Currently, filters out the automated reply and any <DBM> auto-replies you may get as a result of that whisper. Then at the end of the encounter you get a quick notification of the names/toons of those who whispered you. If all goes well should be ready early next week.

    Will add an option to toggle it off for those who like to chat during encounters.

    Last edited by kiezo on 4/22/2013 8:52:13 PM
  • To post a comment, please login or register a new account.
Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster addon downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

PAX South Alienware Giveaway