🔵 Describe the bug:

The sequence does not display any icon that can be selected for each action.

🔵 To reproduce: (Steps to reproduce the behavior)

1. Open GSE
2. Open the MM_ST sequence
3. No icons are shown

🔵 The error:
Paste the error message in this blockquote.

no LUA error

🔵 Screenshots:

🔵 Expected behavior:
I should see, for each action, a pop-up with the list of icons corresponding to the spells contained in the action.

🔵 GSE.lua file:

GSE.lua.txt

🔵 Desktop (please complete the following information):

• OS: MacOS Sequoia
• Game Version Retail 11.0.2

🔵 GSE Version:

• Version: GSE-3.2.16.b.1
• Downloaded From: Discord

What I have done is if WoW cannot determine the spell it shows the ? icon so you can always set an icon.

What makes this an interesting bug is why WoW cannot determine the spell. The issue is in HOW you have written the sequence.

It all comes down to the placement of /startattack. First off this command is redundant in TWW. /startattack is built into each Hunter ability but people like to put it into sequences for pseudo comfort. When the whole block is sent to WoW to go what is the icon - it goes through the SecureCmdOptionParse process. This evaluates all the mods and returns the command. When sent as an entire block - WoW goes the /startattack command is the command as its the first one that matches the modifiers and there is no icon for that. Removing that in the next block and Kill Shot's icon is shown by default instead.

try 3.2.16-b-4-gd3dfe28

Have you tried 3.2.16-b-3-g89c5405 ?

Have you tried 3.2.16-b-3-g89c5405 ?

yes the latest one.

t all comes down to the placement of /startattack. First off this command is redundant in TWW. /startattack is built into each Hunter ability but people like to put it into sequences for pseudo comfort.
As I told you during the early development of GSE 3.2 this summer, without that command, the first available target is not automatically targeted, despite the /targetenemy command.
Anyway, I will do further testing to see if I can remove it.

Now works perfectly!
tyvm Tim!

As I told you during the early development of GSE 3.2 this summer, without that command, the first available target is not automatically targeted, despite the /targetenemy command.

I’m not writing this to be antagonistic but my experience and all the testing I have done I found the complete opposite results. /startattack does nothing for targetting. All it does is turn on your auto attack. For me it doesn’t even engage auto shot but my melee auto attack. Engaging auto shot is done by the actual hunter abilities. All ranged abilities (from BFA on) also target something if you don’t have a target however it is less reliable and repeatable than /targetenemy.

Your modifiers on /targetenemy are curious. Try swapping to /targetenemy [noharm][dead]. Your [noharm,nocombat] means it won’t switch target till you leave combat. This will never be processed outside your first block as for every other block, by being in combat means this can never happen. Any target switching is the result of your hunter abilities innate target switching rather than the /targetenemy line.