Entertainer Archive

---

Isabow wrote:

Tiaga,

Pardon my n00b-ness. Do I write this in notepad and save it to my SWG folder? How will this input into the game so I can use it? Will I get a new icon ingame or will I have to put in a "start" command to get it rolling?

---

Copy the text and paste it into notepad, save it to your SWG folder in c:\Program Files\StarWarsGalaxies as bufftimer.txt

In the game to use it just type /load bufftimer.txt and you should get a message that it was loaded. To use just type /bufftimer <name>

This is a great little tool, thanks ever so much Tiaga.

/Hug Tiaga

---

FuschiaD wrote:

Itcould have something to do with the fact that it's almost 5 in the morning for me... but that makes my head hurt, Tiaga. >.< Can you put it into 5 year old terms? I might be able to grasp some of that.

---

I was thinking about the same thing...through my sleep-clogged eyes very little of this makes sense to me and somehow I doubt it will make sense even after I get some sleep. I understand how to make this work, but I don'treally know why it works. It would be nice to know so I could tweak it if I needed to and so I could have a chance of writing my own in the future.

To avoid the alias spam I just created a new chat tab that has spatial, chat channels, group and guild chat on it, then pulled it off the main box to create it's own window.

Gonna split this up and examine it line by line....

---

Tiaga wrote:

Edit: Ultimate buff timer v 2.0

bufftimer /:buff:start;/:buffre:setname

:buffre:setname /alias :buffre:alias /:buffre:cmd
:buffre:setcmd /alias :buffre:cmd
:buff:tell:set /alias :buff:tell:send /tell

:buff:start /pause 0.2;
/:buffre:setcmd /tell;
/pause 0.2;
/:buff:tell:start;
/:buffre:setcmd /:buff:time;
/pause 0.2;
/:buffre:alias

:buff:time /pause 210;
/:buff:tell:all;
/:buff:tell:set

:buff:tell:all /pause 0.2;
/:buff:tell:1;
/:buff:tell:2;
/pause 2;
/:buff:tell:3

:buff:tell:start /:buffre:alias Just watch me and sit tight for 3 minutes. I'll send you a tell when the buff is done.
:buff:tell:1 /:buff:tell:send Your buff is done! You can stop watching whenever you are ready to leave.
:buff:tell:2 /:buff:tell:send If you will be getting a buff from a musician, be sure to stop watching me first, or the buffs may not work.
:buff:tell:3 /:buff:tell:send Thank you for supporting live entertainers! We'll still be here when the buffbots are gone.

---

I get very creative with my aliases. My other big confusing alias takes keypresses to determine what to do next. That one is a lot simpler though.

I just need to sit down and mess with it some.. Doing a swap shouldn't be hard though. The only reason it's broken out into so many aliases is to make it easier to read and modify. Even the way it is now, I think I could get everything swapping, so only the first /bufftimer would give alias spam. The rest only need to swap back before a pause, and swap to the spam window after.

I'll have to experiment some to see what works best, but /bufftimer will need to start with a swap, then probably /:buffre:setname swap back. /bufftimer can't do it directly for obvious reasons. /:buff:start would need a swap after the first pause, and around every following pause. /:buff:time will need to start by swapping back, then swapping again after the pause. /:buff:tell:set will need to start with a swap back as well, then /:buff:tell:all will swap around each pause, and swap back at the very end.

With all that, there will be the message from /bufftimer, but nothing else. One line in response to typing a command I can deal with.

There are a number of reasons I prefer aliases over macros. The main one is they are easy to install. Just save a text file and /load it. I never type /alias in game. I share the SWG folder then edit the files on a second computer. I also never let the game save my aliases, I like to keep the files pure the way I edited them. For this reason, I have a alias I use instead of /load:

:alias:load /:alias:delaysave dummy.txt;/load
:alias:delaysave /pause 0.1;/save

That way it loads the alias file then saves to dummy.txt, where any /alias command changes are saved. The reason I do this is because my aliases are self modifying, any file I /load becomes "infected" with all my aliases. Each time you /alias, it saves then all to the last file /loaded or /saved. My main aliases.txt has a bunch of aliases defined, but most of them are in the form of /:alias:load filethatdefinesthisalias.txt;/pause 0.2;/thisalias.

The other reason I prefer aliases over macros is that macros have an enforced /pause 0.25 at their start. The only time I use macros over aliases is when I want to bind a hotkey to it, or I need to do looping and hit the alias recursion guard.

The one command per line thing is why I have so many aliases that aren't necessary. I split the aliases out as much as I can. Songs I do one line per /sing. Music I usually have an alias for each phrase of the arrangement.. For example one for the verse, one for the chorus and so on. The way I write them, I can then do /:music:verse music:verse music:chorus music:verse music:verse music:chorus music:bridge music:verse music:chorus to lay things out. Can't do that with macros.

I also hate having to scroll through a million and a half macros to find the one I want for keybindings/toolbars. Aliases it doesn't matter as long as I know the name.

Yeah I do the same too. But when I want a command to start immediately, I stick to alias instead of /macro.