GSE: Sequences, Variables, Macros

GSE: Sequences, Variables, Macros

6M Downloads

[BUG]Block text does not match Compiled Text

LordImperialRuler opened this issue · 2 comments

commented

🔵 Describe the bug:
My macro was acting strange, lots of pauses of nothing happening at times. Here's what my Block Text says:
/cast [nochanneling] Mutilate
Here's what the Compiled template says:
[11] = {
["macrotext"] = "/cast [nochanneling] Sinister Strike",
["type"] = "macro"
},
The Compiled Template changed Mutilate to Sinister Strike which the Assassination rogue does not have. Not all Mutilate are changed to Sinister Strike which is strange

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

This is what I based the macro on. It has the same problem

https://wowlazymacros.com/t/assassination-war-within-11-0/41290

🔵 Desktop (please complete the following information):

  • OS: [e.g. Windows 11 64bit]
  • Game Version [11.2]

🔵 GSE Version:

  • Version: [3.2.08-a]
  • Downloaded From: [e.g. https://www.curseforge.com]
commented

This actually isn’t a bug.

WoW has a number of temporary buffs in classes where a spell or ability is replaced by another. As macros can’t tell that the temporary thing has happened you can either try to cast the base spell or the upgraded. If you cast the base spell, and the proc has occurred WoW will cast the updated. If you cast the updated and the proc hasn’t occurred WoW will do nothing.

in Legion each class was changed where there is 1 base class and every other spec is just an upgraded form of that class. Spells like Sinister Strike are upgraded when you change to the other specs.

See https://github.com/TimothyLuke/GSE-Advanced-Macro-Compiler/wiki/Base-Spells for more information and how you can verify this.

it is confusing when you first see it but you eventually get your head around it.

commented

Rogue’s are also one of the harder classes to get right. It always feels like it should be doing more when you are either energy starved or combo point starved.

The command
/gse debug
can also ahow you why actions were skipped and didn’t fire.