[Rodo]

Spoiler:

I think I got the first one.... the problem seems to be that is-destroyed-delay will never work in an AND just because it only turns true or false if the cruiser gets destroyed or it departs. (well if the cruiser departs after destroying the Cain it might work i guess)

[Androgeos Exeunt]

Spoiler:

Question 10: Why use "and-in-sequence"? Maybe you should just use "and" instead.

[Polpolion]

ten

Spoiler:

Assuming the Fenris is present before the Cain is destroyed, that part will be true instantly, and thus not be in the correct sequence.

eleven

Spoiler:

Not too much of an idea, so I'm going to have to make some 'educated conjectures'. Noting how sneaky "every-time" and "is-event-true" work together, I'm going to guess that there's something weird with the repeats here as well. Furthermore, I'm going to assume that the <arguments> are like variables, with semi-permanent values. Given my previous coding "experience", I'm going to guess that you need to tell FRED to stop using a specific argument, because you only have one actual "argument" to evaluate. Why FRED wouldn't do that automatically at the end of the SEXP doesn't really make sense, though.

[NGTM-1R]

Spoiler:

Question 10: Why use "and-in-sequence"? Maybe you should just use "and" instead.

Spoiler:

That'd return the Fenris true instantly rather than checking the Cain was dead first.

10. I have a feeling there's a stage missing here, and the not needs to be preceded by something...but I'm not sure what.

11. As I would never handle that set of circumstances in that fashion, I haven't got a damn clue.

[Axem]

10:

Spoiler:

and-in-sequence breaks horribly if the sequence is broken. And as many people know, not is-destroyed-delay likes to fire off at arrival of your ship.

11:

Spoiler:

Well in-sequence needs an invalidate-argument in order to actually move on to the next one.

However, random-of sounds like it would work, except that if its anything like the rand function in FRED, it will return the same random result even if its called multiple times. You need to use the random-multiple-of (like you would use rand-multiple if you needed truely random results)

[FreeSpaceFreak]

10

Spoiler:

The 'not' on the Fenris triggers before the is-destroyed-delay on the Cain.

11 Dunno.

[TrashMan]

10.

Spoiler:

I think you need a AND argument insted of And-in-sequnce.  I remember that working for me with the exact same SEXP.

Alternatively, you can have the Fenris jump out if the Cain is destroyed and simply check if he jumped out.[/spolier]

11.
dunno really.

[Androgeos Exeunt]

10.

[spolier]

Spoiler:

I think you need a AND argument insted of And-in-sequnce.  I remember that working for me with the exact same SEXP.

Alternatively, you can have the Fenris jump out if the Cain is destroyed and simply check if he jumped out.[/spolier]

11.
dunno really.

Are the italicised bolded sections deliberate?

[TrashMan]

friggin typo...fixed..Fix your post and remove that too.

[Axem]

I was thinking, "Man, a mod sure could fix that...

OH WAIT!"

And the I dunnos for 11 show that people need to learn to use arguments. C'mon if you can use variables, conditional arguments aren't that much harder.

[karajorma]

Question 10 - Answer

This one is a classic  that's popped up a few times on this board. In fact I got the idea for this question when I looked through some very old posts and saw Trashman having almost the exact same problem.

The answer is that at the start of the mission the Fenris isn't destroyed so that part of the SEXP comes true instantly. Using And instead of And-in-sequence is the correct answer here.

And-in-sequence is a powerful SEXP but most people have made mistakes like the above and become wary of using it. But that's one more reason I said it's good to get rid of superstition. Better to know why your attempt to use and-in-sequence didn't work than to avoid using the "cursed" SEXP.

Question 11 - Answer

I was a little nasty with this one as it's actually two questions in one. Quite a few got it correct as to why the use of in-sequence wasn't working but less people understood why random-of hadn't worked and thought it was the same issue.

The in-sequence SEXP won't move onto the next argument in the list until the one it is currently dealing with has been invalidated. Since this wasn't happening the event would keep repairing turret01 forever. What you need is something like this



Unfortunately that crashes almost any build of FS2_Open since they don't have the fix I added to SVN last night (It's in this build). But since there is a more complicated way to make that work with even 3.6.9 (using variables to pass the argument to the inner when) I considered it a fair question.

As for using Random-of I'll give everyone an extra day to go back and see if they can figure out what's wrong there.

[TrashMan]

No new questions?

[karajorma]

Not until I get a few more people trying to puzzle out the second half of the last one.

Seriously though, I should have some new ones later this week.

[FUBAR-BDHR]

Couldn't it also break due to hits-left-subsystem and turrets?

Spoiler:

random-of returns the same argument every time it's called.  You would need to use random-multiple-of and something to check that the turret hasn't been repaired once in case it could be damaged again.

[karajorma]

Couldn't it also break due to hits-left-subsystem and turrets?

It's got the optional 3rd argument to prevent that. After warning people of that gotcha I'd look rather silly if I did it myself in the same thread.

[FUBAR-BDHR]

Yea I remember seeing that when you first posted the question now.  My beer level must be low.

[NGTM-1R]

And the I dunnos for 11 show that people need to learn to use arguments. C'mon if you can use variables, conditional arguments aren't that much harder.

Pfffft, like I said, I wouldn't ever handle it that way.

[Colonol Dekker]

Bah i'm on my phone i can't see the questions. I'll try in the morning.
 
Fubar, what's the BDHR for? Another acronym or old squad tags? Dunno why i'm asking, just curious.

[Goober5000]

Dunno why i'm asking, just curious.

I believe that's the reason why you're asking.

[FUBAR-BDHR]

Fubar, what's the BDHR for? Another acronym or old squad tags? Dunno why i'm asking, just curious.

Way off topic but since it already got a Goober response it stands for Beer Drinking Hell Raisers.  Yes it's a Squadwar squad and were still around although most don't play anymore.  Trying to fix that. 

http://www.165thbdhr.com/