Issue with sequence naming
MechaZao opened this issue · 2 comments
Using Beta12 on live, I cannot name my warrior sequence FURY. if I do so, the sequence will not fire, and any attempt at editing it causes GSE to stop working properly until I reload. Naming the sequence FURY_DPS made it work just fine and editable without issue.
I tried this with a clean install as well.
First off you are using the BfA beta build on live. There will be issues as the new GSE build is expecting different WoW API elements that aren’t present in Live till the PrePatch hits.
The issue of not being able to call the macro Fury is working as intended. Each macro has a hidden object that it operates with. Each of these objects have a unique name. Blizzards internal code also creates these objects in the same area. If an object already exists, GSE won’t let you create a macro of the same name as you then get problems when two processes are trying to use the same object for different purposes.
This existed with PVP and WW in Legion and sometimes macros with those names worked other times it broke things very badly. GSE now checks to prevent these conflicts.
TimothyLuke
… On 28 Jun 2018, at 2:08 am, MechaZao ***@***.***> wrote:
Using Beta12 on live, I cannot name my warrior sequence FURY. if I do so, the sequence will not fire, and any attempt at editing it causes GSE to stop working properly until I reload. Naming the sequence FURY_DPS made it work just fine and editable without issue.
I tried this with a clean install as well.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.