4.1 COMBAT_LOG_EVENT_UNFILTERED changes
4.1 adds a new arg, hideCaster (boolean), and of course, with blizz tradition, not at the end, but right smack in the middle offseting rest of args and breaking mods not updated to account for it. This boolean isn't logged by /combatlog so that parsing seems unaffected.
4.0.6 COMBAT_LOG_EVENT_UNFILTERED(timestamp, event, sourceGUID, sourceName, sourceFlags, destGUID, destName, destFlags, ...) 4.1 COMBAT_LOG_EVENT_UNFILTERED(timestamp, event, hideCaster, sourceGUID, sourceName, sourceFlags, destGUID, destName, destFlags, ...) |
.. that sucks. :(
|
not really, it's a 2 second fix in most mods when 4.1 launches, to support it now though just means some if/else rules and a client build check to have your mod support ptr and live similtaniously.
|
To perhaps help explain why it's in the middle instead of the end... The different CLEU events add returns to the end of the normal CLEU returns.
|
What does the new item mean, though?
-Crissa |
it's a flag telling the combat log if it should show the message or not, this could possibly mean events firing for spells currently not fired for CLEU?
|
Thanks for that note, I'll have some changing to do come 4.1
|
lol, lovely place to stick it. Thanks for the heads up though. :D
|
When trying to make mods compatible between 4.0.6 and 4.1 I noticed that GetBuildInfo() is still returning 40000 as its 4th value on the PTR, even though the 1st value is "4.1.0". I resorted to this for consistency's sake:
Code:
local clientVersion |
All times are GMT -6. The time now is 06:03 AM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI