[LoneKnight]

I've been ignoring this issue for a while, but solving it would make my life a lot easier. It seems that when I use and-in-sequence, it doesn't work. According to the description, when the events or information you put in become true in the order they are listed with the SEXP, the effect should trigger. But this doesn't seem to happen. I have a simple and-in-seqence: event-true and key-pressed, but it doesn't work even after I know that these have happened in the correct order. I even tried the key-press before the event was true to see if the order was backwards but no change. Any idea on why and-in-sequence doesn't seem to work?

[LordPomposity]

If the key is pressed before the event becomes true, FS2O will stop checking for the key to be pressed again. Try adding key-reset to the event that event-true is checking for. Not sure if this is the problem, but it's worth checking.

[mjn.mixael]

and-in-sequence definitely works. Please see the attached mission.

[attachment deleted by ninja]

[Black Wolf]

I know it used to give me all kinds of grief - SCP may have fixed it, or it may have never been broken, and I always used it wrong, but I avoid it as a matter of course these days.

[karajorma]

and-in-sequence is one of the most misused/misunderstood SEXPs out there. Post the mission and/or the SEXP and we can tell you if it should work.

[TopAce]

Basically, "and-in-sequence" mandates that the conditions turn true only in the given order, else the event will be false(!), not incomplete.

Or is there more to it?

[karajorma]

Nope. That's all there is to it, but people often make mistakes with and-in-sequence because they use a NOT sexp with it and forget that this will evaluate to true at the start of the mission.

[LoneKnight]

Basically, "and-in-sequence" mandates that the conditions turn true only in the given order, else the event will be false(!), not incomplete.

Okay, so what I was trying to do was have an event that checks for the Player hitting a button, but only after a certain time has elapsed. I now know that if the Player was to hit the button before the time elapsed, it would render the sequence false.

This is what I had:

and-in-sequence
       -has time elapsed
       -key pressed

How would I change this so that this isn't rendered false if the Player uses key press before the time elapses?

[Droid803]

...why don't you just use regular and, and then just use key-reset-multiple right before said time elapses.