|
Originally Posted by Zidomo
No, its not another addon necessarily causing them. Its mods not designed 100% properly for the patch that is the root cause of them. The CT mod author (Cide) has admitted that the CT mods (improperly) taint frames (I've already posted in the main CTMod 2.0 Bugs thread about them). Consequently, those errors will occur if you have any other mod trying to (safely or not) use those frames.
There are ways around frame tainting to become 100% compliant with the patch, but some mods (such as CT) aren't doing it.
On the other hand, if a mod going nuts tainting frames/calling protected functions (like CT mods are) are not interfering with other mods you may have installed, it may not be a gigantic issue. But those who like to find bugs with BugGrabber/BugSack or similar mods will have a tougher time trying to dig through all those ADDON_ACTION_BLOCKED errors to find other mod errors. |
That's not what I said at all. Taint is not avoidable at all times. The only reason this "problem" even exists is because BugSack is logging it by default, which it definitely shouldn't.