Bug Report: WeakAuras Not Displaying Correct Icon for GSE Sequence
Summary: WeakAuras fails to display the correct icon for the GSE sequence EA_BD_v0.4. Instead, it shows a question mark icon, indicating that the expected spell icon is not being retrieved or applied correctly.​

Steps to Reproduce:

Create or import the GSE sequence EA_BD_v0.4.

Set up a WeakAura to track the GSE_SEQUENCE_ICON_UPDATE event.

Activate the sequence in-game.

Observe that the WeakAura displays a question mark icon instead of the expected spell icon.​
WoW Lazy Macros

Expected Behavior: The WeakAura should display the icon corresponding to the spell defined in the GSE sequence.​

Actual Behavior: The WeakAura displays a question mark icon, suggesting that the spell icon is not being retrieved or applied correctly.​

Additional Information:

The GSE_SEQUENCE_ICON_UPDATE event is being triggered, but the spellinfo table appears to be empty or nil, leading to the fallback question mark icon.

Other GSE sequences with properly defined spells display their icons correctly in WeakAuras.

The issue persists across different characters and after reloading the UI.​
CurseForge

Logs:

makefile
Copy
Edit
Event: GSE_SEQUENCE_ICON_UPDATE
SourceName: EA_BD_v0.4
SpellInfo: table: 0000029AD8474100
Environment:

World of Warcraft Version: Retail 10.1.0

GSE Version: 3.2.16

WeakAuras Version: 2.19.0

Operating System: Windows 10 Pro 64-bit​

Steps Taken to Troubleshoot:

Verified that the spell defined in the GSE sequence exists in the character's spellbook.

Manually set the icon in the WeakAura to the expected spell icon, which resolved the issue temporarily.

Tested with other GSE sequences, which displayed their icons correctly.​

Request: Assistance in resolving the issue where WeakAuras does not display the correct icon for the GSE sequence EA_BD_v0.4. Any guidance on ensuring that the spellinfo table is populated correctly during the GSE_SEQUENCE_ICON_UPDATE event would be appreciated.

Sry my english is bad this is created by Chatgpt
🔵 Describe the bug:
A clear and concise description of what the bug is.

🔵 To reproduce: (Steps to reproduce the behavior)

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

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

🔵 Screenshots:
If applicable, add screenshots to help explain your problem.

🔵 Expected behavior:
A clear and concise description of what you expected to happen.

🔵 GSE.lua file:
Please provide your GSE.lua file or the export string for the specific macro that is causing an issue.

• To find the GSE.lua file:

1. First, make sure you have enabled the "File Name Extensions" checkbox in Explorer (View tab)
2. Browse to C:\path\to\wow\_retail_\WTF\Account\YourAccountName\SavedVariables\ or /path/to/WoW/_retail_/WTF/Account/YourAccountName/SavedVariables
3. Copy the GSE.lua file to your Desktop
4. Rename this copy to GSA.lua.txt
5. Then just drag it here in your message

• Note: If you do not include your GSE.lua file you are wasting your time and mine. 90% of the time, the first thing I will ask for is "Can you please upload your GSE.lua file?". This file is needed with the error to work out Why that error occured for you.

🔵 Desktop (please complete the following information):

• OS: [e.g. Windows 10 64bit]
• Game Version [e.g. classic/bcc/retail (9.1.0)]

🔵 GSE Version:

• Version: [e.g. 3.x.y]
• Downloaded From: [e.g. https://www.curseforge.com]

🔵 Additional context:
Add any other context about the problem here.

This isnt a bug - its a a situation within the sequence that is outside of the scope of what the weakaura can identify. There is neither a workaround or a solution.

The thing to be aware of is GSE doesn't actually DO or EXECUTE anything. It sends the commands you give it to WoW and WoW decides what it will do with those commands. Some combinations of commands and references simply cannot be evaluated to give an icon. The Sequence author can, if they are a patron, manually set an icon for that block so that it doesn't give a ? for the unknown state. You should be asking them to fix their sequence.

See #1621 for details.