Quantcast WoWInterface - View Single Post - new at this/looking for assist
View Single Post
10-05-19, 09:23 AM   #3
aallkkaa
A Warpwood Thunder Caller
 
aallkkaa's Avatar
AddOn Author - Click to view addons
Join Date: Jun 2017
Posts: 98
Well, on your "filthy hack" snippet, you are trying to reset the methods :ClearAllPoints and :SetPoint of protected frames ('PlayerFrame', 'TargetFrame', etc), which is never a good idea, as other addons might need to use those methods as well; actually Blizzard might need to use those methods on their frames as well - and that's why they're protected.

And, as the error message you got implied, even using those methods (let alone modify the methods themselves) on protected frames doesn't go very well with Blizzard, particularly in combat.

There are some things you can do with the standard Blizzard frames, but usually only out of combat (rhis restriction is to prevent automation such as the game casting spell A or B in response to world events, without user interaction, AKA having the game play itself for you).
Not saying this is what you're trying to do (hardly looked at your code). But the above is something to keep in mind.

You can listen to the event PLAYER_REGEN_DISABLED to listen for player entering combat. PLAYER_REGEN_ENABLED lets you listen for player leaving combat. InCombatLockdown() returns true when you are in combat, and thus prevented from messing with protected frames.
  Reply With Quote