We have a winner! 2.5 changes to combat log a joke.
Ok, out of all the jokes yesterday this one was the bets because I actually fell for it. I reported yesterday that Slouken had posted on the UI forums about changes to the combat log in 2.5 due to the massive amount of complaints and bugs. What makes this believable is that there ARE a lot of complaints and bugs associated with the new combat log as it has pretty much rendered a lot of mods useless and overall just complicated things.
This is to be expected with change obviously but I didn’t really see what was wrong with the original combat log in the first place that would merit such an overwhelming change coupled with such a major content patch.
Either way Slouken you are the winner! You made a fool of me my friend well played. (src)
This is just temporary until Iriel gets his upcoming changes post going, but here are some upcoming changes in the 2.5 release:* Due to performance problems and numerous bugs, we’re reverting the combat log changes in 2.4, and going back to the old style combat log.Â
* We’re working on converting the Blizzard UI to use ’self’ and the other local arguments in favor of ‘this’ and argN . The old style arguments are going to be obsoleted, so we’re going to have an extra long PTR phase for 2.5 so AddOn authors can make sure they get all their code converted over to the new style.Â
You can actually start converting and testing your code in the live 2.4 build. A full list of the new style arguments is available here:
http://forums.worldofwarcraft.com/thread.html?topicId=36975623#5 April Fool ! :) [ Post edited by Slouken ]
Â



















