Furien2007-03-10 22:31:45
Much love to anyone who can code or point me to an existing script for either...
(Zmud scripts, mind)
-Capturing Shiptells in aetherspace and putting them into a separate window.
or
-Putting a timer on songs (I can supply lines for that), and alerting you/automatically refraining when it hits a certain time spot.
(Yes, I'm so totally inept that I don't even know how to activate a timer, or create a new window.)
(Zmud scripts, mind)
-Capturing Shiptells in aetherspace and putting them into a separate window.
or
-Putting a timer on songs (I can supply lines for that), and alerting you/automatically refraining when it hits a certain time spot.
(Yes, I'm so totally inept that I don't even know how to activate a timer, or create a new window.)
Unknown2007-03-11 00:10:46
What client? I have some handy song timers for MUSHclient.
Furien2007-03-11 00:41:41
Oh, duh, I knew I was forgetting something. It's Zmud, sadly.
Kharaen2007-03-11 02:52:24
QUOTE(Furien @ Mar 10 2007, 05:31 PM) 389899
Much love to anyone who can code or point me to an existing script for either...
(Zmud scripts, mind)
-Capturing Shiptells in aetherspace and putting them into a separate window.
or
-Putting a timer on songs (I can supply lines for that), and alerting you/automatically refraining when it hits a certain time spot.
(Yes, I'm so totally inept that I don't even know how to activate a timer, or create a new window.)
(Zmud scripts, mind)
-Capturing Shiptells in aetherspace and putting them into a separate window.
or
-Putting a timer on songs (I can supply lines for that), and alerting you/automatically refraining when it hits a certain time spot.
(Yes, I'm so totally inept that I don't even know how to activate a timer, or create a new window.)
One down.
Drathys2007-03-11 03:21:45
For capturing channels, I use (from my "communication" class):
which captures all channels into a window named Comms.
I am not particularly happy with using capture-all triggers (*), but it easily allows for messages of arbitrary length.
You can restrict it to just one channel by changing the first trigger (replace the first * with the channel name)
As for the songs, you can probably just use an alarm:
EDIT: That's what I get for doing too many things at once.
CODE
#TRIGGER {^~(*~)~: (*)} {#t+ capComms} "Communication"
#TRIGGER "capComms" {*} {#capture Comms;#gag} "Communication" {disable}
#TRIGGER {~"$} {#t- capComms} "Communication"
#TRIGGER "capComms" {*} {#capture Comms;#gag} "Communication" {disable}
#TRIGGER {~"$} {#t- capComms} "Communication"
which captures all channels into a window named Comms.
I am not particularly happy with using capture-all triggers (*), but it easily allows for messages of arbitrary length.
You can restrict it to just one channel by changing the first trigger (replace the first * with the channel name)
As for the songs, you can probably just use an alarm:
CODE
#TRIGGER {^PLACE TRIGGER LINE HERE$} {#ALARM +time-to-wait-in-seconds {#SHOW MESSAGE HERE (or execute alias / whatever}}
EDIT: That's what I get for doing too many things at once.
Sybl2007-04-10 22:35:50
That channel capture script is mediocre... I'm at work right now, but when I get home I'll post the script I use to get my ship tells in a separate window.