Importing a Macro creates the Sequence in Uppercase and the /macro entry in normal case.

Question

Importing a Macro creates the Sequence in Uppercase and the /macro entry in normal case.

Zen-Karma opened this issue 6 years ago · 10 comments

Zen-Karma commented 6 years ago

This might just be doing it wrong but first Thanks for getting around to fixing the not being able to save issue. Now it seems I can't even get a basic /cast Rockbiter to work. I also tried the record macro part and when I press the macro nothing happens. I might just be doing something wrong and will have to wait to see some example macros but figured I'd post just in case. Also no LUA errors happening but I didn't stay on long so I can try again if you need me to.

SirEwing · Answer 1 · 2018-04-30T16:19:33.000Z

I just discovered what the problem is. You have to use all caps for the name of new macros.

Zen-Karma · Answer 2 · 2018-04-30T16:29:12.000Z

You're correct as I just tried and its working. TYSM!

SirEwing · Answer 3 · 2018-04-30T16:35:22.000Z

TimothyLuke I Suggest you add the need to use all caps when naming new macros to the instructions.

Zen-Karma · Answer 4 · 2018-04-30T15:11:45.000Z

Latest update, I got it to work by NOT renaming the macro and just leaving it as “NEW SEQUENCE” going to do some more messing around

SirEwing · Answer 5 · 2018-04-30T22:30:55.000Z

Just discover a related naming issue, on imported macros. Eventhough the name was in all caps, you still need to edit it out, and reinput the name in all caps, to get the macro to work.

SirEwing · Answer 6 · 2018-04-30T22:36:20.000Z

I imported Cymiryc's Arcane Mage macro from the website. It imported fine, But eventhough the name was in all caps, it would not work; Untill I edited its name out, and replaced it: With the exact same thing, again in all caps.

TimothyLuke · Answer 7 · 2018-04-30T20:17:28.000Z

That change happened For Beta 2. There is a one off process that is supposed to rename all your GSE macros to uppercase and it’s supposed to convert your macro name to uppercase when you press save. TimothyLuke

…

On 1 May 2018, at 2:05 am, SirEwing ***@***.***> wrote: TimothyLuke I Suggest you add the need to use all caps when naming new macros to the instructions. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

TimothyLuke · Answer 8 · 2018-05-02T04:27:14.000Z

I just imported CYM's Demonology macro and found that it was creating the following macro:

#showtooltip
/click [button:2] CymDemo RightButton; [button:3] CymDemo MiddleButton; [button:4] CymDemo Button4; [button:5] CymDemo Button5; CymDemo

It needed to instead create

#showtooltip
/click [button:2] CYMDEMO RightButton; [button:3] CYMDEMO MiddleButton; [button:4] CYMDEMO Button4; [button:5] CYMDEMO Button5; CYMDEMO

The problem is not resolved by editing the macro and changing this name. This just creates the second macro name. a /gs cleanorphans is still needed to remove the first incorrect macro.

TimothyLuke · Answer 9 · 2018-05-02T04:28:53.000Z

using the following as a test case:

dut5baWsIWBvqVwbMTKUjvQFHIBJs7KQ2Ry3KA)a)wPbsGmuIQbdA4uHdQqoMQCCvLSqcPLsq1IjswUepur6Puwgr55qMOIAQqzYOQPJCzvoSuptrCDOAJeu2kbPntL8ys(iHyBkuFwvP(oHYijsDAuz0QQgpb4KeetJa6AeOopv06iuDxvfFIi68cw8VytDYoFSB8YcwmSUEAcf79EVjVxS5ZvJxP4FXgHt)Bj2iev2Vx6xqJ084C6yUBvzf6vqCRgfS4Fbl(xmgvJia0w8kaAuHBWfVSymQgra40UwbW5Y18iQRdUck(jXyunIaq7V5xXaqr3kfVaJXOAebGs3AEaCDbGIGxLKV1Xl4ymQgraO0TMhaxxaOi4vj5BD8JJXOAebGYxXUcaACo(xDmjoNc)QxJUGfkMrNdHHRve3QJz3x4NM46AmjoNYlhcfS4FXyunIaWHSlV4OFox0haC(yxTuBLIxwmgvJiaCi7YlUIk1paOHZYUAaC(yxnNcaXCwAnf)KymooQjQvdaWHNa4qe6tOyYxe5UvLnyHIjVCUBvzdwOytxwPAkIgkumZXPeYC8YgpouOea

TimothyLuke · Answer 10 · 2018-05-02T04:38:47.000Z

this is the change for beta4

Share to