Dancer Archive
Thread: How to make non-looping macros
Page 2 of 2
Tiaga
Fri Jan 14, 2005 1:24 am
#14
You can combine aliases and macros to make it really long.
And yes, /echo with color codes does work.
And yes, /echo with color codes does work.
Coreena
Sun Jan 16, 2005 11:28 am
#16
yeah, an /echo is nice
Also /echo messages can be colored using the \#RRGGBB codes, to see them better.
If I use /addalarm for those purposes its in that syntax:
/addalarmin 0 0 Buff done!
at the end of the macro.
It adds the alarm and immediately plays the sound, and the system message.
I decided to add it to the end of the macro and not timed at the start, because this way I can /dump the macro in between and don't get annoyed by an alarm later on that doesn't tells me anything anymore
Also /echo messages can be colored using the \#RRGGBB codes, to see them better.
If I use /addalarm for those purposes its in that syntax:
/addalarmin 0 0 Buff done!
at the end of the macro.
It adds the alarm and immediately plays the sound, and the system message.
I decided to add it to the end of the macro and not timed at the start, because this way I can /dump the macro in between and don't get annoyed by an alarm later on that doesn't tells me anything anymore
CaisaIsay
Mon Jan 17, 2005 2:39 pm
#17
To create macros and then load them from an external file, you would create the file (mine is called al.txt) and then when you log into SWG, you type /load filename (so for me I type /load al.txt) What is nice is you can create names for each of your macros and then use them like slash commands. I have several little ones that make things so much easier like :
mb: /mount Speederbike Swoop;
All I have to do is call my swoop and then type /mb. I'm also an ID so if I'm doing a stat migration, I have a macro that will start the image session and then add an alarm to let me know when to commit.
statm: /image;/alarmaddin 00 04 Stat Migration Done;
The only bad thing about using an alias file is you have to load it each time you log in.
Sunjammer
Mon Jan 17, 2005 10:12 pm
#19
Okay, that was weird. Serves me right for surfing at work, I guess. 
Sorry about the blank post. What I had asked -- before it mysteriously vanished -- was whether you could create a macro that would load all your alias files.
E.g.,
/load file1
/load file2
/load file3
/load file4
Then just run it when you log in.
Umi
Sorry about the blank post. What I had asked -- before it mysteriously vanished -- was whether you could create a macro that would load all your alias files.
E.g.,
/load file1
/load file2
/load file3
/load file4
Then just run it when you log in.
Umi
BoostAlotus
Tue Jan 18, 2005 10:43 am
#20
You know i think repeating macros are fine but they just need to make it so they stop reapeating after half an hour or something like that. It would get rid of A TON of buff bots but still make it so you can have crafting macro and so on.
CaisaIsay
Tue Jan 18, 2005 5:38 pm
#21
oooooh! That is a change since I quit and came back (was gone for almost a year) Very nice change! Thanks for the tip.
Tiaga
Tue Jan 18, 2005 11:52 pm
#22
It always has, really. Any time you do /alias in game to create an alias, it adds it to alias.txt (Or the most recent loaded/saved file) so it will be there next time you play. Thing is, aliases are one of the game's best kept secrets
Tiaga
Wed Jan 19, 2005 1:51 am
#23
On aliases, the game automatically loads alias.txt when it starts.
However I like putting aliases into their own files. So what I usually do is put each set of aliases in their own file with one that loads it in the main alias.txt file. For example, I have my buff timer alias in dancebufftimer.txt, and in alias.txt I have:
bufftimer:dance /load dancebufftimer.txt;/save dummy.txt;/bufftimer:dance
The /load is obvious as to what it does, the /save less so. I havea lot of self modifying aliases. As a result, every time the alias is modified, ALL alaises get saved to the last file loaded or saved. So if I just /load then that file will eventually get contaminated with all my aliases. The /save dummy.txt saves the aliases to a file that is never loaded so it doesn't matter what is in it.
Only drawback is that the alias recursion guard can stop this from working. (But oddly it hasn't been as big a problem lately..)
However I like putting aliases into their own files. So what I usually do is put each set of aliases in their own file with one that loads it in the main alias.txt file. For example, I have my buff timer alias in dancebufftimer.txt, and in alias.txt I have:
bufftimer:dance /load dancebufftimer.txt;/save dummy.txt;/bufftimer:dance
The /load is obvious as to what it does, the /save less so. I havea lot of self modifying aliases. As a result, every time the alias is modified, ALL alaises get saved to the last file loaded or saved. So if I just /load then that file will eventually get contaminated with all my aliases. The /save dummy.txt saves the aliases to a file that is never loaded so it doesn't matter what is in it.
Only drawback is that the alias recursion guard can stop this from working. (But oddly it hasn't been as big a problem lately..)
Page 2 of 2