I have been Alpha of BfA for a while but they have only just started to allow Mods to be tested against the new client. I have a mostly working GSE. I’m not ready to release an alpha version yet as there is a lot of things in the underlying libraries that need to be updated for it to work properly.
Things to be aware of:
Trinkets and most offensive cooldowns are now ON the GCD. This means that for a lot of macros there are significant changes to KeyPress and KeyRelease. It looks like its a case of one ability per click where you could do a /target and a /cast but nothing else. This is the big gotcha in that I got a sequence to load and run but it wouldn’t enact any abilities. This was because I had Crusade on KeyPress and it wouldn’t fall through past that part.
The other is that Castsequence seems to have been removed and it now behaves like cast. Ie it will only cast the first spell in the castsequence part and not move on. This so far looks to be a deliberate choice by Blizzard. If this is the case then it will make GSE more needed for macroing than less as it will be the only way to program up a button going forward. This is definately a watch this space thing.
The good news is that the functions that are broken are broken as the underlying Ace3 libraries havn’t been updated yet.
High level things that I will need to think through
All the sample Macros will need to be rewritten and the Tick boxes for things like trinkets etc will need a rework. The tickboxes in the editor were to reduce the boilerplate that was prevalent in the original GS. Im still of the view that “/use 13” is not obvious for trinkets so may include a shorthand of some sort like “/use trinket1” and “/use boots”.
Abilities have also been pruned and changed in BfA. This gives me the thought to look again at the translator, The translator holds a list of every US spell and its local equivalent as even though each spell has an internal spell ID, macros can only use the spell name. This is a significant memory overhead for non enUS clients. If castsequence is indeed gone and with the compact macro format introduced in GSE 2.2.00 I could change the macro storage engine to store macros based on the spell ID and then present this back up to the client after looking up the spell name. This will improve the performance for non US clients and reduce the ram needed. It will also deal with some hunter spells that are not available in GSE due to special characters in the language.
I have been looking into different requested options like talent based macros and level based macros. Im not going to do these as there are other ways of achieving this within the current frameworks. I will be exploring further multiple loop style macros. I had this mostly working from a request from John Mets but it hasnt been ready for release yet. This will probabely be a significant change.
Apart from this it looks to be business as usual.