Just a note of thanks for all the help and support that I have received from this community. You never know the story of people who are using stuff. I have had a lot of notes from people with various physical disabilities who have expressed that GS-E is helping them play. Honestly these comments are more for you guys than for me.
1.1 - Localisation
Having said that I have been asked about localization. THe problem is that macros run in the client side language. THere is deeply hidden Blizzard Code that needs a string (programmer speak for a line of text) describing the action. If you take a macro from here thats written in english and run it on a french client it doesnt know what /cast Consecration is as you need the french rather than english spelling.
Ok I have a plan. It is going to take some time but I have a plan. Of super importance to me is being able to come here to wowlazymacros and be able to explicitly read what a macro is doing. While some mods have an encrypted string that they share (Weakauras) the last thing I want is to look at a string like that and hope it will be ok and not cause a problem like the scam chat exploit. I cant stress how important readability is to me.
The first thought was to store macros with the spell id rather than the name. So a sequence would look like “/cast 11234” THat breaks the readability straight off. No one would know what that is exactly doing without having to cross check. It also means that you cannot take a GS-E macro and run it with the original GnomeSequencer. That’s not a direction I want to go.
Rather than store than store the spellID I am going to make a better LibBabble-Spell. LibBabble-Spell was a mod that translated spell names. It hasnt been updated since wow 2.3 but it is an idea. LibBabble-Spell was deprecated as 98% of what it did could be achieved in changes that Blizzard made to the ingame API. U*nfortunately our use case is the 2%.
The plan for this is as follows. I will write a small mod that exports the spell name and spellID which we save in a text file. The file will look like:
2=“Hand of Reckoning”,
} Etc But when you run the same mod on another client it will create the same list and order but in Russian or German or French. I would need people with these clients to run the export as a once off. If something was added in 7.1 then all we would need to do to update the translater is to rerun the export.
It would be a relatively minor performance cost (an extra 2 or 3 seconds) at startup to hook these translation files and translate into your local client language. We could then add a lang= line to the sequence with a default of EN. And a global option to use the translater. If the global option is off it will only use sequences that it finds that are in your clients language. If you have all your sequences in FR and have turned say Draiks Bundled off you then don’t need the translator. The editor will have two tabs for export - an en to share and a local version to save in myMacros
The translater itself will be an optional mod so that you can choose to disable it.