Hard Light Productions Forums
Modding, Mission Design, and Coding => The FRED Workshop => Topic started by: Molaris on May 16, 2014, 04:04:25 pm
-
I'm looking to have 3 waves of fighters coming in a mission. I intend to use the same fighter/bomber wings and just have them arrive at 3 points in the mission. What would be the most effective way of doing this? I figured maybe "when event true" type of set up, but how would I set it up for 3 separate events? I thought an "and" would work, but wanted to make sure it wouldn't cause a problem. Thanks guys
-
Easiest solution: don't use the same wing names.
As far as I'm aware, the only way to do want you want while keeping the same wing names is to bypass the wave system altogether and create new ships with SEXPs, which is a lot of effort just to avoid using more wing names.
(I may be wrong, of course; others are far more experienced with FRED than I.)
-
Just create three different wings with wing names that are like this
Beta#1
Beta#2
Beta#3
I think that is a work around for it.
-
Assuming you want the numbers to continue to go from 1 and up (and not repeat), there's ways you could pull that off. Basically you just turn the arrival cues into "windows" where they turn true at the point they are supposed to arrive, and then false again shortly after. If an arrival cue turns false, any reinforcement wings won't arrive again. (If repeating numbers is okay, Cyborg's idea would work. There's a semi-recent code change that ensures the wing number is visible with wing names containing a #)
So its sort of like
when
-or
--and
---is event true delay
----event1
----0
---not
----is event true delay
-----event1
-----5
--and
----etc etc etc
This is also a neat way to keep friendly reinforcements at a good balance between "everyone dies 30 seconds in and never respawns" and "8 waves are needed to survive and do the work for the player"
-
Just create three different wings with wing names that are like this
Beta#1
Beta#2
Beta#3
I think that is a work around for it.
IIRC, this should work since this year.
-
Just create three different wings with wing names that are like this
Beta#1
Beta#2
Beta#3
I think that is a work around for it.
IIRC, this should work since this year.
But then you'll get three different Beta 1s. If that's fine, that solution is easiest, but I'd personally go with Axem's solution (which I am totally going to make a note of... that's a useful trick).
-
I'm looking to have 3 waves of fighters coming in a mission. I intend to use the same fighter/bomber wings and just have them arrive at 3 points in the mission. What would be the most effective way of doing this? I figured maybe "when event true" type of set up, but how would I set it up for 3 separate events? I thought an "and" would work, but wanted to make sure it wouldn't cause a problem. Thanks guys
What I do is to have the wing arrive "near" or "in front of" an invisible ship (like a navbuoy textured with "invisible"), and then use set-object-position on the ship.
EDIT: Never mind, I answered a different question than the one you asked. :p
-
Goober, I actually like that and will keep it in mind for future referance :-) thanks
Axem, you answered it EXACTLY. I had a strange feeling that the if I goofed it up, the game would create a loop of fighters warping in instead of one wave on cue. Thank you guys. You are all a great help
-
I'm gonna be honest, I'm a little lost. Axem's idea sounds great, but alcohol and exhaustion are messing with me, hahaha. So do I create the event in the event viewer and then go to arrival cues and have them arrive when the event is true? And would 3 separate refered to events within one event block work in the arrive cue? Just checking cause the arrival cue won't allow me to change the "true" argument to a "when". I'm still learning, but enjoying this more and more I do it. much appreciated!
and I have it all laid out, but what would I do with the "do nothing" line? seems like I am missing something.
-
Heh, whoops, yes the arrival cues would get all the ands and ors and is-event-trues. There is no when there, I just was a bit too much on autopilot on writing sexps in text. :)
[attachment deleted by an evil time traveler]
-
ooohhh, I made an event in even viewer. ok, thank you Axem. that helps much better
it didn't work, and I think it's because I added an "and" underneath the primary "and"
so I have
and
is-event-true-delay
AI Goal Add
0
not
is-event-true-delay
AI Goal Add
5
and
is-event-true-delay
AI Goal 3
0
not
is-event-true-delay
AI Goal 3
5
is that other "and" screwing things up? I will recheck it asap, but I gotta get up early
-
Keep in mind that the "and" sexp can have more than two arguments. You're not the first person to fail to realize that -- even Volition made that mistake!
-
Also look back at my original sexp, the "root" logical sexp there is an OR before the ANDs.