Originally Posted by ZOS_ChipHilseberg
This patch also includes a change to the Lua security system. Now when you register a callback for a script handler, event, or update it will run that callback as insecure code even if the code itself is secure. This only impacts registering existing secure closures (not addon created closures), so it should have little impact overall.
|
Can you provide an example or two of code affected by this change? And a new resolution for these cases?
EDIT:
Errors without pointing at which addon generated them, as I try to open a container.
EDIT2: Chip, is there an official recommendation on how to replace our old code with new code that is "secure" now? Why make this change without informing us further? The following code from one of my addons is now "insecure" and raises the above unuseful error:
EDIT3: I am still curious to hear an official response about this issue! In the meanwhile, if this can help other developers, in my case I hooked into the global events: