[Phanx]

"X tried to call the protected function Y" errors are not meant to be taken literally. (Well, maybe Blizzard intended for them to be taken literally, but if so they royally botched the implementation, because it just doesn't work that way.) It almost never means that X actually tried to call Y directly. It just means that X touched something that touched something that touched something that touched something that touched something that's somehow involved somewhere in the chain of Blizzard code that calls Y, rendering the whole chain of execution tainted.

Look for any places in your code where you overwrite functions or variables that are originally defined in Blizzard code, or if it's not obvious, you can enable taint logging to get a full report of everything you're tainting. Find the ACTION_FORBIDDEN error in the taint log, figure out which variable it says is tainted, and then trace that variable back through the log to see where it was first tainted.