4.1 Change

  • 3 posts
    #1 Apr 26, 2011 at 00:29 UTC - 0 likes

    In World of Warcraft version 4.1, Blizzard made a change to the COMBAT_LOG_EVENT_UNFILTERED event, giving it an extra argument. WeakAuras version 1.4b4 accounts for this, and any Event -> Combat Log triggers will continue to work automatically if you update WeakAuras. However, if you have any Custom Triggers that use the COMBAT_LOG_EVENT_UNFILTERED event, you will need to manually update them so that they work with 4.1. This post will show you exactly how to do so.

    1. Open the WeakAuras configuration. If this is the first time you have used WeakAuras since updating to 4.1, you should see a warning message that directs you to this page, and gives you a list of your displays that need manual updating. If you want to see this prompt again, you can type
      /script WeakAuras.CombatEventWarning()
    2. For each display that needs updating, select it and go to the Trigger tab. If the display has multiple triggers, find the trigger that is Type = "Custom" and Event(s) = "COMBAT_LOG_EVENT_UNFILTERED". Click the "Expand Text Editor" button next to the "Custom Trigger" input field.
    3. The first line of the custom code should look like
      function(_, _, message, _, source, _, _, dest, _, _, spell)
    4. You need to add another argument at the fourth position (you can just name it "_"). Once you do so, the first line should look like
      function(_, _, message, _, _, source, _, _, dest, _, _, spell)
    5. Repeat for all displays that were listed in Step 1.

    Edit: It was previously stated that the new argument should be placed in the third position. That was incorrect. Since WeakAuras also passes the event string as an argument at position 1, the new argument should be inserted at position 4. This has been updated above.

    Last edited Apr 26, 2011 by Mirrormn
    #2 Apr 27, 2011 at 00:22 UTC - 0 likes

    @Mirrormn: Go

    Appreciate the quick turnaround!

    #3 Jun 27, 2011 at 06:31 UTC - 0 likes

    Combat Log Event has changed again in 4.2. You now need to add arguments in positions seven (7) and eleven (11); essentially, one each after the usual "source" and "dest" arguments.

    For example:

    function(_, _, message, _, _, source, _, _, dest, _, _, spell)

    should be changed to

    function(_, _, message, _, _, source, _, _, _, dest, _, _, _, spell)
  • 3 posts

You must login to post a comment. Don't have an account? Register to get one!