|
benny1564 Novice
Joined: 22 Jun 2004 Posts: 48
|
|
_________________ |
|
|
|
Maelstrom Apprentice
Joined: 10 Feb 2005 Posts: 158
|
Posted: Thu Aug 04, 2005 6:14 pm |
You might be able to delay it by a single line but that might be sub-optimal. I will think about it and if I come up with anything better ill post back...
#TRIGGER {^whatever$}
#TRIGGER {^whatever$*$} |
|
|
|
MattLofton GURU
Joined: 23 Dec 2000 Posts: 4834 Location: USA
|
Posted: Thu Aug 04, 2005 8:48 pm |
If you want to ensure two things happen in a given order, it's probably best to use one trigger and a #PRIORITY command. #PRIORITY works effectively within a code block, but I've no clue if it spans across triggers (I'm really doubting it does, though), and wrapping your first effect in #PRIORITY will guarantee it gets processed and completed before the second effect is worked on.
|
|
_________________ EDIT: I didn't like my old signature |
|
|
|
Vitae Enchanter
Joined: 17 Jun 2005 Posts: 673 Location: New York
|
Posted: Thu Aug 04, 2005 10:20 pm |
if both fire off of the same line why not just have
#trigger {line} {A;B}
where A is an alias of what happens in trigger A and B is an alias what happens in B
zmud will send alias A and then B, but won't over lap on one another.
at least not that I have seen.
or am i misunderstanding the question? |
|
|
|
Vijilante SubAdmin
Joined: 18 Nov 2001 Posts: 5182
|
Posted: Fri Aug 05, 2005 12:09 am |
You can also use the 'Move Up' and 'Move Down' buttons, in the Settings Editor, to control this. As with all settings, make sure that sorting is not active when trying to control the specific order.
|
|
_________________ The only good questions are the ones we have never answered before.
Search the Forums |
|
|
|
|
|