Originally Posted by LBXZero
What macros do you have? If you have any macros, I suggest posting the macros here for review.
Also, if something that "is not Blizzard" modifies a frame in some way, it becomes "tainted". Tainted code can't directly use certain functions completely (like functions that cast spells) and can't directly use some functions while in combat (Show and Hide frame functions for example). If a block of script triggers the taint alert, the WoW Client disables all of the associated tainted functions. Whatever happened in a macro script, it tried to hide the Target of Target frame while in combat, which caused the taint error in which Blizzard disabled the Target of Target frame's script as a result.
Given the taint log is referring to "MACRO_TAINT", my first assumption is to look at your macros to see what they are doing. Macros that just use macro commands should be fine, but macros that run Lua scripts are at risk.
|
Thanks for the explanation!
I actually found the problem some day after my post - it was a macro (with lua script). Script to move the player debuff frame:
/run DebuffButton1:ClearAllPoints()
/run DebuffButton1:SetPoint("CENTER", -220, -250)
/run DebuffButton1.SetPoint = function() end
This was causing the "Interface failed because of addon." in my chat, then causing target of target to stop working.