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.
function(_, _, message, _, source, _, _, dest, _, _, spell)
function(_, _, message, _, _, source, _, _, dest, _, _, spell)
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.
Appreciate the quick turnaround!
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.
should be changed to
function(_, _, message, _, _, source, _, _, _, dest, _, _, _, spell)
You must login to post a comment. Don't have an account? Register to get one!