Originally Posted by Jasmer
Is it because they're actually unlockable, then? Also, the pet frame also has the same function() end and no taint problems as far as I can tell.
|
When you overwrite a variable or function (like you did) and then blizzard's code runs
your function it taints the entire execution path after that point, which means if they have a function that calls TargetFrameToT:SetPoint() after you replaced it then everything in the blizzard function after that point can't do anything that's restricted or protected (like show or hide a unit frame).