PlayerInteractionFrameManager while in combat

a while back blizzard changed all the player interactions to go through a single PlayerInteractionFrameManager function.

if you replace a single frame that uses that function, you need to raw hook it so you can stop its default frame from opening.

it all works fine until youre in combat and try to interact with something your own code doesnt care (so runs the original function) because the game will spit out an “interface action failed because of an addon” error and closes the window - its not an addon blocked message (so nothing in the taint log), its just the basic in combat prevention.

does anyone know of a workaround for this? its raw hooked, checking for being in combat wont work as the default frame wont open if you just exit. calling the original function - which is combat protected - will fail (its what happening now).

if you dont raw hook the function then the default frames will always open, along with yours - and closing those default frames (via code) initiates interaction closure which closes yours as well.

using one of the mounts that have vendors/merchants on them and walking over a low level mob is the easiest way to test it.