[BUG]
Siodar opened this issue Β· 3 comments
π΅ on Evoker only import macros and after logging out and back in, the macros are gone from GSE. but still see the buttons in the game macro menu and on the action bar :
A clear and concise description of what the bug is.
π΅ import Devastaion macro. Logout. Log back in. Check for macros in GSE: (Steps to reproduce the behavior)
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
π΅ No Error message:
Paste the error message in this blockquote.
π΅ S:
If applicable, add screenshots to help explain your problem.
π΅ Macros to stay saved in GSE:
A clear and concise description of what you expected to happen.
π΅ **
GSE.lua.txt
:**
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:
- First, make sure you have enabled the "File Name Extensions" checkbox in Explorer (View tab)
- Browse to
C:\path\to\wow\_retail_\WTF\Account\YourAccountName\SavedVariables\
or/path/to/WoW/_retail_/WTF/Account/YourAccountName/SavedVariables
- Copy the
GSE.lua
file to your Desktop - Rename this copy to
GSA.lua.txt
- 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.
π΅ Windows 11 64
- OS: [e.g. Windows 10 64bit]
- Game Version [e.g. classic/bcc/retail (9.1.0)]
π΅ GSE v.3.1.08 patreonpreview:
- Version: [e.g. 3.x.y]
- Downloaded From: [e.g. https://www.curseforge.com]
π΅ Additional context:
Add any other context about the problem here.
Hi @Siodar
DO you have any update on this or can i close it out? I need somehting to import against your GSE.lua file. Everything i use works.
The entry in /macro is a red herring. When you βcreate iconβ it created this stub entry that fires your macro when you click.
To test this further I need two things:
- your GSE.lua file
- A test import to use
it could be that your evoker macro bucket could be corrupt. You could try a /gse forceclean and that may resolve it. If it doesnβt I need the above.