BEQL Chat Spam #85


  • New
  • Defect
Closed
Assigned to endymion172
  • _ForgeUser397128 created this issue Jul 26, 2010

    What steps will reproduce the problem?
    1. BEQL is putting to much unnecessary info in the chat box everytime you get a new quest, finish a quest or when you complete a line item in a quest.
    2.
    3.

    What is the expected output? What do you see instead?
    No BEQL chat spam.

    What version of the product are you using?
    It says r328, but I think it is suppose to be r238.

    Do you have an error log of what happened?
    no

    Please provide any additional information below.

  • _ForgeUser397128 added the tags New Defect Jul 26, 2010
  • _ForgeUser397128 added an attachment Jul 26, 2010
    Attachment was deleted Nov 8, 2016
  • _ForgeUser397128 added an attachment WoWScrnShot_072610_113346.jpg Jul 26, 2010

    WoWScrnShot_072610_113346.jpg

  • The_Hendo72 posted a comment Jul 28, 2010

    A work-around was posted on Curse.com

    Quote from macarthor on Curse.com:

    about the noisy debug message

    i've solved the problem with the following steps:

    1. open interface/addons/beql/beql.lua with a editting tool (better ultraedit, but notepad not recommended), comment the following line with "":

    DEFAULT_CHAT_FRAME:AddMessage("bEQL: " .. tostring(text))
    

    2. in interface/addons/beql/beql.lua change debug = true to debug = false

    3. open WTF\account\XXXXX\SavedVariables\beql.lua change debug = true to debug = false

    now, enjoy the clear world :)

  • _ForgeUser397128 posted a comment Aug 2, 2010

    I tried the work around posted below. It does not work. It disables BEQL totally. I have system messages turned off at the moment.

  • The_Hendo72 posted a comment Aug 7, 2010

    That's strange. Are you sure you did it correctly?

    Just asking because it's working fine on mine.

  • aoifedivinealliance posted a comment Aug 7, 2010
    Worked on mine too, but I did it on r237and then upgraded to r238 when it came out. Don't know if that would make a difference or not.
  • _ForgeUser397128 posted a comment Aug 7, 2010

    It is possible that I did it wrong. Do you put the quotation marks ("") around this statement as shown.

    "DEFAULT_CHAT_FRAME:AddMessage("bEQL: " .. tostring(text))"

    The rest of it was no problem. I did the above change and it disabled BEQL. Any suggestion are appreciated.

  • The_Hendo72 posted a comment Aug 8, 2010

    There should be no quotes around it.

    DEFAULT_CHAT_FRAME:AddMessage("bEQL: " .. tostring(text))

    The only quotes are the set INSIDE the brackets.


    Edited Aug 8, 2010
  • _ForgeUser397128 posted a comment Aug 11, 2010

    I am not sure what happened, but in my saved variable beql.lua I could not find debug=true. I had a beql.lu~ so I compared the files. Found all the debug=true in the beql.lu. Changed them to false and deleted the .lua file that had no debug=true. Changed the .lu~ to .lua and everything is working now. Thanks.

  • endymion172 self-assigned this issue Nov 5, 2019
  • endymion172 unassigned issue from _ForgeUser1183196 Nov 5, 2019
  • endymion172 closed issue Nov 5, 2019

To post a comment, please login or register a new account.