Author Topic: red-alert  (Read 2170 times)

0 Members and 1 Guest are viewing this topic.

Offline diamondgeezer

Dunno if any of you guys saw my thread over in the modding forum, but  here's the problem - when a ship warps out, it won't carry it's status to the next mission when you red-alert. In one mission, I have two transports reach a node and warp out, and then the player's wing follows. Of course, in the next mission, none of the ships have have carried their status (the player pressed Alt-J, which triggered the red-alert, but the game treats the carry status thing as if he'd jumped).

I know you can do stuff with stealth ships to transfer data like hull integrity about, but it'd be a helluva lot easier if you could have ships which warp out retain their status during a red-alert :nod:

 

Offline Solatar

  • 211
Doesn't the red-alert-carry-status sexp do that?

 

Offline diamondgeezer

Red Alert carry status is a check box in the ship properties. When you set a red-alert SEXP to end a mission, and the ship then appears in the following mission (assuming the second mission has the Red Alert box checked), then the ship will carry its status. However, if the ship has jumped out before the red-alert fires, then the ships will not carry its status if it is in the second mission. It needs to be present in the first mission when the red-alert SEXP fires.

 

Offline Sesquipedalian

  • Atankharz'ythi
  • 211
What we really need are (semi-)permanently recorded variables.  Ship stats must be recorded somewhere for the purposes of red alerts, so maybe that code could be taken and used to make permanent variables.  My vision runs like this:

Invoking the record-status sexp in mission1.fs2 causes the status of ShipA to be recorded like it is when a red-alert happens.  This record is retained until called for again in, say, mission3.fs2.  Flagging ShipA with a "previous-status" flag in mission3.fs2 causes it to arrive with its stats set to the values recorded previously under the entry for ShipA.

Right now it seems the data is 1) obviously not recorded until the moment of the invocation of the red-alert sexp, requiring that a ship be present if it is to be recorded at all, and 2) tossed out if the next mission is not flagged as a red alert mission.  Getting rid of the toss-out and making another sexp that records data for any ship or ships listed without ending the entire mission would probably solve this whole problem.  I'll add this to the sexp request list, too.
« Last Edit: December 17, 2002, 06:47:30 am by 448 »
Sesqu... Sesqui... what?
Sesquipedalian, the best word in the English language.

The Scroll of Atankharzim | FS2 syntax highlighting