Macro Waypoint Multi-Word Titles

[cautious_asparagus]

I'm having issues with setting up macro waypoints that accept multiple words in a title. 

For example, the macro I am trying to set up is:

/waypoint addati pick ~0 ~0 ~0 false #FF8C00 Native Copper Surface Bits

For reference, the default command is:

/waypoint addati [icon] [x] [y] [z] [pinned] [color] [title]

When I use this command in the chat, it works flawlessly and exactly as intended. However, when I use it in a macro, it has this issue:

It instead uses only the first word of the title argument, and I don't know how to isolate multiple words of the title as one argument. I've tried to use some delimiting characters (such as "Native Copper Surface Bits") but it doesn't seem to work. I would appreciate some help.

[Steel General]

Some combination of holding shift, alt, and/or control while pressing space might get the nonbreaking space character (You can also type one with alt-0160, in some interfaces).  You might be able to copy one from elsewhere and paste it into the game.  It looks just like the space character, but the system won't read it as white-space - it'll think the whole phrase is one word.  It's possible, though, the game interface will not allow that character to be used, or at least accessed in that way.  It may change the way the title is displayed, relative to the non-macro method.

[cautious_asparagus]

I have discovered the issue, which should have been obvious from the start.

The command window in the macro UI is too small. It's not the word count at all. The window is not wide enough for my command to be one single line.

As we can see, the command for the waypoint wraps around and goes to a lower line. This invalidates the entire command. Until they allow (or if they do, please tell me how) resizing of windows, this cannot be fixed. That really sucks.

Edited November 25, 2024 by cautious_asparagus

[Thorfinn]

Interesting.  I'm pretty sure it used to work. I don't use the macro editor.  I just open it in a text editor (npp) that has proper copy/paste and cursor controls. 

[Brady_The]

On 11/25/2024 at 5:42 PM, cautious_asparagus said:

That really sucks.

There's a workaround you can utilize.

[cautious_asparagus]

On 11/26/2024 at 7:07 PM, Brady_The said:

There's a workaround you can utilize.

Forgot to reply, that workaround worked. Thank you. I would have never thought to edit the macro files themselves.

Edited December 2, 2024 by cautious_asparagus