[Spoon]

but you dont have to use chains, you could also use is-event-true-msecs-delay, if you need to really fine tune the delay between two events (though in the case of a string of messages, I dont really see why you would. but just throwing it out there!)

[Trivial Psychic]

Sometimes I use send-message-list for single messages, but I make use of the fact that the delay for the first message is BEFORE the message plays.  For example, I have a directive linked to a ship departing safely, but perhaps I don't want the message concerning this departure to play exactly at the same time, but I also don't want to create another event chaining to the directive event, so I use send-message-list.  Give it a few seconds (or a few thousand milliseconds) and the delay takes place before the message plays.

[AdmiralRalwood]

Sometimes I use send-message-list for single messages, but I make use of the fact that the delay for the first message is BEFORE the message plays.  For example, I have a directive linked to a ship departing safely, but perhaps I don't want the message concerning this departure to play exactly at the same time, but I also don't want to create another event chaining to the directive event, so I use send-message-list.  Give it a few seconds (or a few thousand milliseconds) and the delay takes place before the message plays.

So why don't you just put the delay in the condition? Like if you want it to play 2 seconds after the ship leaves, just set the delay for has-departed-delay to 2.

[karajorma]

Sometimes the trigger condition doesn't include any of the delay SEXPs.