exporting macros

Question

exporting macros

Baeon opened this issue 6 years ago · 8 comments

the new export feature has no way to inspect the macros when posted to the website. this makes evaluating if i want to try them before loading them impossible. is there any way to make it so that the export function will also export something similar to what it used to export? a line-by-line breakdown that shows mods, and conditionals, etc.

TimothyLuke · Answer 1 · 2018-07-19T04:58:21.000Z

No. You can do a line by line eval in game. There is a "WLM Format" option when you export that creates a summary of whats in the macro. There was no reliable other way for macros to translate across languages. While the greatest percentage of players play on enUS, more people play something else. (deDE, brMX, esES, esMX etc). See #409 #392 and #382

…

On Thu, Jul 19, 2018 at 2:04 PM, Baeon ***@***.***> wrote: the new export feature has no way to inspect the macros when posted to the website. this makes evaluating if i want to try them before loading them impossible. is there any way to make it so that the export function will also export something similar to what it used to export? a line-by-line breakdown that shows mods, and conditionals, etc. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#425>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjBFRlWpO-zDwQqlzIrfFLr87ef1urOks5uIAw-gaJpZM4VVvKq> .

-- *TimothyLuke*

Baeon · Answer 2 · 2018-07-19T06:46:18.000Z

do the macro commands/mods/conditionals change when the client language changes? does "/cast" become "/somethingfrenchthatmeanscast" when using the french client?

I totally understand and appreciate that the "real" export string has to be the WA gibberish, but copy/pasting each macro on a page into the client just to look at it seems tedious. as a layperson, it seems like it could be done to make it translate just for viewing purposes.

TimothyLuke · Answer 3 · 2018-07-19T06:56:13.000Z

No the spell names all change. /cast Judgement becomes /cast Judg'men or something similar and unless I keep a table of each spell and what to translate it to. Thats why there is a tick box for people exporting to start with a preprepared summary for when they paste to WLM. (#409)

…

On Thu, Jul 19, 2018 at 4:16 PM, Baeon ***@***.***> wrote: do the macro commands/mods/conditionals change when the client language changes? does "/cast" become "/somethingfrenchthatmeanscast" when using the french client? I totally understand and appreciate that the "real" export string has to be the WA gibberish, but copy/pasting each macro on a page into the client just to look at it seems tedious. as a layperson, it *seems* like it could be done to make it translate just for viewing purposes. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#425 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjBFQPOmJCWpXb07JWUrpK5to38hBpfks5uICs6gaJpZM4VVvKq> .

-- *TimothyLuke*

TimothyLuke · Answer 4 · 2018-07-19T06:56:48.000Z

That table alone took up 400mb - 1.2gb of ingame memory on non enUS clients. On Thu, Jul 19, 2018 at 4:26 PM, Timothy Minahan <[email protected]> wrote:

…

No the spell names all change. /cast Judgement becomes /cast Judg'men or something similar and unless I keep a table of each spell and what to translate it to. Thats why there is a tick box for people exporting to start with a preprepared summary for when they paste to WLM. (#409) On Thu, Jul 19, 2018 at 4:16 PM, Baeon ***@***.***> wrote: > do the macro commands/mods/conditionals change when the client language > changes? does "/cast" become "/somethingfrenchthatmeanscast" when using > the french client? > > I totally understand and appreciate that the "real" export string has to > be the WA gibberish, but copy/pasting each macro on a page into the client > just to look at it seems tedious. as a layperson, it *seems* like it > could be done to make it translate just for viewing purposes. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#425 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAjBFQPOmJCWpXb07JWUrpK5to38hBpfks5uICs6gaJpZM4VVvKq> > . > -- *TimothyLuke*

-- *Timothy Minahan**M* 0406 413 680 | *E *[email protected]

Baeon · Answer 5 · 2018-07-19T07:23:36.000Z

ahh, ok... thanks for taking the time to explain. and as always, thanks for all the hard work you put into this.

TimothyLuke · Answer 6 · 2018-07-19T07:40:54.000Z

Not a problem at all, The thing that I need Blizzard to fix is that each spell has an ID and an English and a localised name. Eg English 1 Judgement French 1 Juge’me (Or similar) When it internally does things it uses the 1. (CastSpellById(1)). When we do things we need to do the second (castSpellByName(Judgement)) but with in the game there is nothing we can use to convert from Judgement to Juge’men. The French client has no idea what Judgement is. There are 300k different spell ids and many different variations of the name from when you had spell ranks etc. If that makes any sense? TimothyLuke

…

On 19 Jul 2018, at 4:53 pm, Baeon ***@***.***> wrote: ahh, ok... thanks for taking the time to explain. and as always, thanks for all the hard work you put into this. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

ronpritch1 · Answer 7 · 2018-07-20T13:23:49.000Z

When I do a WLM export I get this.

``dqZUbaWsc4TOk2gQqZevPztj3uH(fL6BOQStr2lSBk2pjnmrLFl0qjKbtIHlkDqc0Xq5COs1cffwkrAXcSCs9qur9uKLjPNRQjsqnvfnzIy6uDzPUUk1grLYwrfzZOc2UOOpIkPhlX0e0HvAKOsCBvYOjuVwbojb5zkOtRIZtu9zrvJJOCxuvnyyIedKGshjKQycAUwTXFqvgRwzvqc3CyVTCKyGOSDriHrIpgibVDXrniUQxJKRv)IxlqJBrh5uR)t08yIedtKyGSl77QkvzSC5YHufKDzFxvHvRCpePHGSl77Qk8nuwisHGSl77QkCoAf))(vvOR9fdI3ymlVNRJdsgirX3h3IoIjsmq2L9DvfwihdHdIl9kbbGsDzacaLrB5iaK0JjpdbGM6Jzq7veasGwU02Q3VXeoibA5I09)yIedKTV68T3M(sUQcpMO4vFXpps6vc)WbrENLB3MIFIgqI0NO(4Ybj9yYxrair6ECl6iMiXazx23vvgggwLbh0uFmdANHa4WbnUM71siJ36mBJFIgKbC4a`ARMS
Talents 2112212

This macro contains 1 macro version. This Sequence was exported from GSE 2.3.01.

Macro Version 1

Step Function: Priority
Pre Macro: Victory Rush

KeyPress: Contains various utility functions.

Main Sequence: Mortal Strike, Execute, Overpower

Post Macro: Slam

`

Line by line....you mean a spell list. I guess where I am confused is the macro I downloaded....is doing a lot more then whats said. This is where I am confused as far as being able to see what macro is doing compared to old version.

I apologize for not fully understand, it just it was a lot simpler before to find errors and add and remove items from the macros where now.....I feel like I don't know whats its doing without watching combat log.

TimothyLuke · Answer 8 · 2018-07-20T21:37:49.000Z

This is a summary that is formatted to give you the initial guts of a post to WLM. It’s up to you the poster to decide how much more information to add in or how much to take out. The reality is that unless you were watching GSE’s Sequence debug you were only guessing what it was actually doing anyway. Even watching the combat log will only tell you what worked and not what was skipped and why. As for the line by line view that the export used to give you, you have this in the edit window within the game. TimothyLuke

…

On 20 Jul 2018, at 10:53 pm, ronpritch1 ***@***.***> wrote: When I do a WLM export I get this. ``dqZUbaWsc4TOk2gQqZevPztj3uH(fL6BOQStr2lSBk2pjnmrLFl0qjKbtIHlkDqc0Xq5COs1cffwkrAXcSCs9qur9uKLjPNRQjsqnvfnzIy6uDzPUUk1grLYwrfzZOc2UOOpIkPhlX0e0HvAKOsCBvYOjuVwbojb5zkOtRIZtu9zrvJJOCxuvnyyIedKGshjKQycAUwTXFqvgRwzvqc3CyVTCKyGOSDriHrIpgibVDXrniUQxJKRv)IxlqJBrh5uR)t08yIedtKyGSl77QkvzSC5YHufKDzFxvHvRCpePHGSl77Qk8nuwisHGSl77QkCoAf))(vvOR9fdI3ymlVNRJdsgirX3h3IoIjsmq2L9DvfwihdHdIl9kbbGsDzacaLrB5iaK0JjpdbGM6Jzq7veasGwU02Q3VXeoibA5I09)yIedKTV68T3M(sUQcpMO4vFXpps6vc)WbrENLB3MIFIgqI0NO(4Ybj9yYxrair6ECl6iMiXazx23vvgggwLbh0uFmdANHa4WbnUM71siJ36mBJFIgKbC4a`ARMS Talents 2112212 This macro contains 1 macro version. This Sequence was exported from GSE 2.3.01. Macro Version 1 Step Function: Priority Pre Macro: Victory Rush KeyPress: Contains various utility functions. Main Sequence: Mortal Strike, Execute, Overpower Post Macro: Slam ` Line by line....you mean a spell list. I guess where I am confused is the macro I downloaded....is doing a lot more then whats said. This is where I am confused as far as being able to see what macro is doing compared to old version. I apologize for not fully understand, it just it was a lot simpler before to find errors and add and remove items from the macros where now.....I feel like I don't know whats its doing without watching combat log. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

Share to