Originally Posted by Xrystal
Have you tried testing with no addons and just a simple provider?
|
Yep, no addons, no modifications to any Blizzard code whatsoever, only using a macro to create and add a data provider (as shown in the video) - seems like adding a data provider (even a empty one that only prints what methods are called) is enough to cause the error.
Setting taintLog to 2 on live doesn't log anything in this case for me (not even INTERFACE_ACTION_BLOCKED_SHOWN, the logfile is completely empty), that's why I'm testing on the PTR with taintLog set to 11.
Blizzard bug?