As far as I remember timer does not work with "new turn" trigger.
To say the truth there are even more triggers that does not work together with some events. Be patient and spare your time for testing.

Try the following:
Choose a boolean flag, we name it B1 here.

In the "Set Timer" event make a logical conjunction in the trigger with "AND NOT B1".

Make an additional event *following* (!) the Set Timer event, namely a "Control Flag" event that sets B1 to "true" with the same trigger condition as of the Set Timer event (except that you leave away the conjuncted B1 condition, of course).

I'm confident it will work!

[This message has been edited by Final Bolt (edited 04-16-2004 @ 07:56 AM).]

Webusver, i'm not trying to use a "new turn" trigger...

Bolt, i tried what you suggested but the results are the same. after the 3rd day has passed, nothing happens. i tested it out with a Show Message event that should be taking place when the timer finishes its countdown, and it still doesn't work. is the Set Timer event broken or something?

The Set Timer event is in a row of new script statements that bear an occurence error. So it never reacts to setting occurence to "Once" but always behaves as if set to "Always". - I have pointed out this error after the release of SM but seemingly the developers have ignored what I am saying (they usually do!)

I had good results with the work-around so far, but of course I cannot exclude there being more errors conncetd to this event. And everything is made more complicated by the fact that scripts are not always and everywhere executed in sequential order.

[This message has been edited by Final Bolt (edited 04-17-2004 @ 04:36 AM).]

Are you sure about that Final Bolt? I have not seen this in my use of the timer event, but I could have missed it.

RajTanath: send me the file and I'll take a look at it. Seems like it should work. Include an explanation of what you are trying to do and what events are involved too, if you would.

I'm quite sure. I will write a little pamphlet about it when I have done more invetigations in all possibly involved script statements.

If your trigger conditions for Set Timer are - by coincidence - a one-time happening (like e.g. an enter area) you will likely not notice the error. But if you have conditions that persist, like e.g. a negative condition (new day + object (not) in area; but perhaps also a Request Answer, I'm not sure about this) you can easily see that the Set Timer occurs every day and thus resets itself again and again and appears to not function. In fact it functions too often!

I have proven in my new Creek Adventure 200 map that a New Day Set Timer can work perfectly when you apply the mentioned work-around.