Ambrosia Garden Archive
    • Misn on~whatever fields


      when do they fire?

      For some reason I haven't been able to get consistent results here. Do A*** F*** and S*** operators instigate the onaccept, onfail and onabort fields (irrispectively), or is the bible serious when it says "when the player aborts the mission"?

      Also, when are failed missions aborted? I can see from pilot logs that it isnt instant. Does it not happen until you reach the returnstellar anyway? Does the Failtext keep a failed mission from aborting until it is read?

      I will experiment with these to see if I can get consistent results, but Im certain that others here know much more about missions than I do.

    • Oops, back button disoriented me. Sorry, move to dev corner please, of course.

    • I know for a fact that Sxxx evaluates OnStart/OnAccept/OnWhateverTheHellitIs, Axxx evaluates OnAbort, and Fxxx evaluates OnAbort. Well, okay, the Fxxx and Axxx I haven't actually tested but I have tested the Sxxx causing it to act as if you had normally accepted it, and it works perfectly, so it only seems logical that Axxx would cause it to act as if you had clicked the abort button and Fxxx would cause it to act as if you had failed the mission normally.

      By the way, it's generally a good idea to use xxx as RID# placeholders for ncb set strings. I thought you were swearing at first glance! :blink:

      This post has been edited by orcaloverbri9 : 17 February 2005 - 06:34 PM

    • Here's what I've come up with so far. I have both when the set strings fire (mostly) and when the messages show up:

      OnAccept: Is evaluated before the OnAccept message. Is also evaluated when you start a mission using the Sxxxx NCB operator.

      OnRefuse: Fires when you click the "refuse" button, but after the OnRefuse message.

      OnSuccess: I have not tested this, but I assume that it works as advertised.

      OnFailure:
      So far I have been unable to get the OnFail message to display. This may have an effect on when the NCB set strings are fired. (does anyone have a fool-proof way to get that message to display?)
      Fires as soon as you fail the mission if you fail via the SpecialShip.
      Fires as soon as you are scanned.
      Fires as soon as you miss the mission's deadline.
      Fires as soon as you are disabled if the "fail on disable/destroy" flag is set.
      Does not fire until you reach TravelStel if you use Fxxxx.

      OnAbort:
      Fires immediately when the player aborts.
      Fires when mission is auto-aborted.
      Fires when ship is destroyed if the "fail on disable/destroy" flag is not set.

      OnShipDone: Fires immediately, after the OnShipDone message.
      NOTE: If you have no SpecialShip goal, the shipdone message (but not the NCB set string) will fire off the first time you enter space after starting the mission (if you reload the pilot file before landing again, the game will not have saved the fact that SpecialShipGoal is "done," and will thus display the message again).

      (In case you're wondering, I've started work on a guide to exactly when every one of these set strings fires.)

      This post has been edited by Edwards : 17 February 2005 - 10:59 PM