SilverDragon - Rare Scanner

SilverDragon - Rare Scanner

20M Downloads

WotLK - Macro Issue

Wyr3d opened this issue ยท 1 comments

commented

The previous version worked fine, but the latest update has mixed results.

On one char the macro appears to work fine, but the works "scanning for X entities" pops up in the chat log, and sometimes fails to see mobs ever if they are nearby

On another character it fails every time popping up with the message:

You are attempting to run a custom script - blah blah warning"

Attempting to allow despite the warning (which is not reccommended by the way) results in throwing up a LUA error for DBM for some reason:

Date: 2022-11-01 05:02:02
ID: 1
Error occured in: AddOn: DBM-Core
Count: 1
Message: Error: AddOn DBM-Core attempted to call a forbidden function (SetAllowDangerousScripts()) from a tainted execution path.
Debug:
[string "=[C]"]: SetAllowDangerousScripts()
[string "@..\FrameXML\StaticPopup.lua"]:4165: OnAccept()
[string "@..\FrameXML\StaticPopup.lua"]:5228: StaticPopup_OnClick()
[string ":OnClick"]:1:
[string "
:OnClick"]:1
Locals:

I have already posted this error in DBM, but I don't think that's the problem, as disabling DBM throws up a LUA error for a different addon each time, for example:

Date: 2022-11-01 05:05:04
ID: 1
Error occured in: AddOn: FleecingTip
Count: 1
Message: Error: AddOn FleecingTip attempted to call a forbidden function (SetAllowDangerousScripts()) from a tainted execution path.
Debug:
[string "=[C]"]: SetAllowDangerousScripts()
[string "@..\FrameXML\StaticPopup.lua"]:4165: OnAccept()
[string "@..\FrameXML\StaticPopup.lua"]:5228: StaticPopup_OnClick()
[string ":OnClick"]:1:
[string "
:OnClick"]:1
Locals:
None

Both of these addons function normally otherwise (although the latter is out of date) so it is much more likely to be a SilverDragon problem

commented

There's some pretty awkward issues to do with macros using /click and secure action buttons in the prepatch, and we're hoping to get them fixed before/in the actual expansion launch. It's fairly-impossible currently to write a macro that'll reliably work to click a button, because exactly what you have to do is (a) buggy and (b) depends on a user-changeable setting.

That said, the latter character is experiencing that issue as a side-effect of #182 that I didn't consider, because I'm so used to /script having been approved on every single character I ever play. You can avoid it in the short term by disabling the option in settings that tells the macro to be more chatty. I'll look at making it not happen.