Error messages when using a lazymacro
lynspottery opened this issue · 1 comments
🔵 Describe the bug:
As the title states, I keep getting error messages when I use a lazymacro.
🔵
I have no idea how to explain this except to say this error message shows up in red letters across my screen just as soon as I use one of the lazymacros setup with gse.
🔵
Paste the error message in this blockquote.
[Nothing to Attack]
🔵 Screenshots:
If applicable, add screenshots to help explain your problem.
🔵 Expected behavior:
I did not expect any error message when using the lazymacros provided. All worked just fine until Bliz's patch last week.
🔵 There is no lua error to show, the red error message just pops up on the screen and there is no LUA error text anywhere.
🔵 Desktop (please complete the following information):
- Windows 11 64bit
- Game Version retail (current)
🔵 GSE Version:
- Version: GSE Advanced Macro Compiler 3.1.42.zip
- Downloaded From: https://www.curseforge.com]
🔵 Additional context:
All I know is whenever I use a lazymacro that I have from using /gse, I get that error message across the screen even though I'm targeting a mob and attacking it. Also I attempted to attach a jpg file showing it, but don't see it here.
Hi Lynspottery.
This it looks like this is happening as you are spamming the macro and trying to cast something while the GCD is in effect or you have a trinket that needs to be used on a player but your macro is trying to use it on an enemy. It’s WoW throwing this warning and it can be turned off in WoW’s settings. After the UI refresh with Dragonflight, I don’t know where this setting is now located and may be a command that you need to run once.
GSE assumes that you the player knows best. So if you have imported a template that has errors in it or requires you to do specific things like setting a focus, GSE can’t correct them it needs you the player to. I can’t look further into this as you havnt attached your GSE.lua file.
As this isn’t a bug with GSE (ie something wrong with GSE itself that I need to fix), but a WoW UI setup thing, I will move this to the discussion area.