I got most of that, but if you look at the macro, there are some key things missing and different.
/castsequence [@mouseover,help,nodead][@player] VS /castsequence [@mouseover, help, [@player]
This is done on 2 lines.
I managed to get the keyrelease to fire and you are correct. I put an “@player” on the Ring of Peace and all is good.
I see what your saying. I have noted this here: Parser not handling two sets of []'s in a macro · Issue #230 · TimothyLuke/GSE-Advanced-Macro-Compiler · GitHub it will be fixed for the next release in the next day.
so I have just got the addon and I am a bit confused, all the videos seem to be for pre 2.0 looking to set up for an ascendance shammy
would this work on patch 3.3.5a if not if there any other macro addons like this that will?
No amd no
Hello guys
Im searching for the macro that enable blizzard dommage nameplates. So basicly the numbers
Thanks in advance
I am still missing something… I have read the posts, and these forums, and watched the video, but I still cannot import the Warlock Destruction macro. I type /gs press import, nothing happens, I copy and paste the macro, nothing happens, I try to drop it directly into the folder, still nothing. Please, tell me what step I am missing. The DH DK Monk Hunter and Shaman macros I have are all working fine.
What Version of GSE are you running and which macro are you trying to import?
[quote quote=42667]so I have just got the addon and I am a bit confused, all the videos seem to be for pre 2.0 looking to set up for an ascendance shammy
[/quote]
Hey Mike,
When you have time go over to Here and check this out Cymiryc has broken it down to a Single target,Ascendance(burst),AOE macros very easy peasy also if you need help he is very cool and helpful!
I have a question about the “!” before for example DH’s “eyebeam”???
Hi,
I have now after some time put the sequence to test to see if it goes 1,2,3 as stated.
And i cannot fathom that this thing can be correct.
So my test goes with this:
I press manually to see what fires, and Hand of Guldan has been my first spell when i enter combat.
Call Dreadstalker has been my second spell.
I have long had my suspicion that both the sequence and priority option doesnt work as explained.
Second test i go out of combat, (Yes macro is set to rest on combat). Now i change to priority.
First spell that goes off is Demonic Empowerment, second spell is Thal’kiel’s Consumption. Thats when im totally lost to how either Sequence or Priority is supposed to work, cause as it is now it just seems to fire of anything at random 
Please enlighten me, as i really need it.
"/castsequence [nochanneling] Demonbolt, Call Dreadstalkers, Demonic Empowerment, Life Tap",
"/castsequence [nochanneling] Demonbolt, Hand of Gul'dan, Demonic Empowerment",
"/castsequence [nochanneling] Summon Doomguard, Demonic Empowerment",
"/castsequence [nochanneling] Demonbolt, Hand of Gul'dan, Call Dreadstalkers, Thal'kiel's Consumption",
"/castsequence [nochanneling] Demonbolt, Demonbolt, Grimoire: Felguard, Demonic Empowerment",
AFAIK, it does nothing with eyebeam, it was used along time ago for making it a priority cast when you set ! before it, but doesnt work anymore it what i have read.
Now its used as a toggle. Like activating Volley for hunters, so it doesnt toggle it on and off.
I have now after some time put the sequence to test to see if it goes 1,2,3 as stated.
And i cannot fathom that this thing can be correct.
So my test goes with this:
I press manually to see what fires, and Hand of Guldan has been my first spell when i enter combat.
Call Dreadstalker has been my second spell.
I have long had my suspicion that both the sequence and priority option doesnt work as explained.
Second test i go out of combat, (Yes macro is set to rest on combat). Now i change to priority.
First spell that goes off is Demonic Empowerment, second spell is Thal’kiel’s Consumption. Thats when im totally lost to how either Sequence or Priority is supposed to work, cause as it is now it just seems to fire of anything at random
Please enlighten me, as i really need it.
Used GSE2
"/castsequence [nochanneling] Demonbolt, Call Dreadstalkers, Demonic Empowerment, Life Tap",
"/castsequence [nochanneling] Demonbolt, Hand of Gul'dan, Demonic Empowerment",
"/castsequence [nochanneling] Summon Doomguard, Demonic Empowerment",
"/castsequence [nochanneling] Demonbolt, Hand of Gul'dan, Call Dreadstalkers, Thal'kiel's Consumption",
"/castsequence [nochanneling] Demonbolt, Demonbolt, Grimoire: Felguard, Demonic Empowerment",
/gs debug is your friend
Sequential and Priority control the way the macro moves through the lines. In sequential it will move from line 1 to line 2 irrespective of whether the previous cast has finished or if the next spell is available or not. Priority is a mathematical probability that a spell on line 1 will be tried more times than a spell on line 3. Again it doesn’t know if it worked or not but can only move to the prescribed line.
Now this gets complicated when you start adding in castsequence lines as castsequences have their own behaviour. It won’t go the to next spell on that line unless the last time GSE was at that line the previous spell was cast. You can’t track this as it’s internal blizzard behaviour not something that GSE sncausing or controlling. GSE will reset the macro when you leave combat by default but it won’t reset the castsequence line. You need to add a reset=combat option to get it to fully reset.
Then there’s manual control and spamming and thet also have their own quirks if this makes any sense.
[quote quote=45196]AFAIK, it does nothing with eyebeam, it was used along time ago for making it a priority cast when you set ! before it, but doesnt work anymore it what i have read. Now its used as a toggle. Like activating Volley for hunters, so it doesnt toggle it on and off.
[/quote]
! Has never had anything to do with priority. It was for toggling an ability on and then not turning it off. Eg Devotion Aura /cast !Devotion Aura would turn it on if it was off but not turn it off if it was on. There are now 3 total abilities that players can cast that use this.
[quote quote=45205]/gs debug is your friend
Sequential and Priority control the way the macro moves through the lines. In sequential it will move from line 1 to line 2 irrespective of whether the previous cast has finished or if the next spell is available or not. Priority is a mathematical probability that a spell on line 1 will be tried more times than a spell on line 3. Again it doesn’t know if it worked or not but can only move to the prescribed line.
Now this gets complicated when you start adding in castsequence lines as castsequences have their own behaviour. It won’t go the to next spell on that line unless the last time GSE was at that line the previous spell was cast. You can’t track this as it’s internal blizzard behaviour not something that GSE sncausing or controlling. GSE will reset the macro when you leave combat by default but it won’t reset the castsequence line. You need to add a reset=combat option to get it to fully reset.
Then there’s manual control and spamming and thet also have their own quirks if this makes any sense.
[/quote]
If you can explain these 3 pictured for me, cause i dont understand debugger at all when the spell im casting isnt even on the line on the debugger,
https://s18.postimg.org/p41nayfux/warlock.png
https://s16.postimg.org/o72zwtnwl/warlock1.png
https://s3.postimg.org/mtjmww4tv/warlock2.png
Your using castsequences and they are getting stuck trying to cast a spell that needs a class specific resource. I’m guessing one of the spells on these lines needs soul shards and you don’t have enough when trying to cast that spell so it skips that line and moves to the next one which also needs Soul Shards so it skips and moves to the next one…
Again as it’s a castsequence there is no way for GSE to determine where the castsequence is up to but the red in those lines in the debugger is the key as to why that line wasn’t cast.
I think i will just accept that things are as they are
Cant wrap my head around this as much as id like to do, but thanks for trying Timothy 
@Andy K.
This may make things easier to understand: Understanding castsequence · TimothyLuke/GSE-Advanced-Macro-Compiler Wiki · GitHub
I think i made things more complicated than it really was. When i linked the pictures i assumed it would cast Demon Bolt, since its free, but that was most likely allready been done and it was on a spell that was on cd and moved to cast Dreadstalker, since that was the next castsequence line spell wich was avaliable.
Im not sure how i made this mess since i kinda knew how castsequence worked, it moves to the next spell in the castsequence when that line is triggered and the spell has been cast before, but i think i just overdid the thinking part a bit.
But about the debugger part, any chance you will be able to program it to actually show what the macro does instead of only the macro line that is cast? Like in my examples when it tries to cast a spell in a line wich shows up in debugger but since its likely on cd or no resources it cast the avaliable spell on the next line. But that doesnt show up in debugger. Or am i just being difficult now?