Hard Light Productions Forums

Modding, Mission Design, and Coding => The FRED Workshop => Topic started by: FUBAR-BDHR on February 02, 2007, 01:48:47 pm

Title: Repeating events and is-event-true-delay
Post by: FUBAR-BDHR on February 02, 2007, 01:48:47 pm
I was looking back at one of the missions I started in 2001 and never finished.  Noticed there was a message in there that never seems to show up.  Last night it hit me that the events the message is based on are repeating and the message is based on is-event-true-delay.  So that got me thinking:  When is a repeating event true or false?  Then I passed out and was being chased by a Ravana and a bunch of sexps all night.  Remember kids don't drink and FRED before bed. 

I can easily fix the mission by popping in a variable but am curious as to how it works or  is supposed to work.
Title: Re: Repeating events and is-event-true-delay
Post by: Trivial Psychic on February 02, 2007, 10:17:22 pm
Then I passed out and was being chased by a Ravana and a bunch of sexps all night.  Remember kids don't drink and FRED before bed.
I had something similar happen to me.  I had taken my very first look at FRED, and was somewhat sick at the time.  Flu and feverish states tend to result in some weird dreams for me, and that night sexps took on physical manifestations and were constantly cutting off my attempts to escape.  It was really weird.  FRED isn't nearly as scary to me these days.  I now look forward to FREDding.
Title: Re: Repeating events and is-event-true-delay
Post by: CP5670 on February 02, 2007, 10:26:42 pm
Interestingly enough, I ran into some trouble with this myself only today. is-event-true-delay recognized that the repeating event had fired, but the delay didn't work at all for some reason. I've had numerous problems with repeating events in the past and it seems to be best to just avoid referencing to them directly with is-event-true-delay. Although I think I have done it in some other missions and it works fine.
Title: Re: Repeating events and is-event-true-delay
Post by: FUBAR-BDHR on February 02, 2007, 11:12:36 pm
I've had many problems with them in the past.  Seem better now then they were in retail but I don't know if that has to do with code or system speed.  Just adding a variable with default 0 and changing it to 1 when the event fires solves the problem.  Of course then FRED pulled a fast one on me and switched the message being sent to the first one on the list.   Note this was FRED2 not FRED2_Open.