Ah, finally I'm home! Okay, here goes:
Straight from the Nova bible:
If you wish, you can make a dësc resource mutable via control bits - embedding a
special sequence of characters into the dësc resource will instruct Nova to
change the contents of the text on the fly. This sequence is delimited (marked)
by the characters "{" and "}", and follows this format:
{bXXX "string one" "string two"}
Where "XXX" is be replaced by the index of the control bit you wish to test. You
can add in a "!" character before the "bXXX" test in order to negate the result
of the test, but unlike the control bit test strings, you cannot perform
compound tests in a dësc resource - i.e., no testing of multiple bits at a time.
If the bit test (after being negated, if the "!" character is present) evaluates
to true, the first string will be substituted in place of all the characters
between (and including) the "{" and "}" characters. If the bit test evaluates to
false and there is a second string in the expression, that second string will be
substituted. If there is no second string, nothing will be substituted.
For example, consider this dësc resource:
This is a {b001 "great and terrific" "lousy, terrible"} example.
...if bit 001 is set, the output will be "This is a great and terrific example."
If bit 001 is not set, the output will be "This is a lousy, terrible example.".
Also note that if you want to include a quotation mark (") character in either
of the two strings, use standard C syntax to do it:
My name is {b002 "Dave "pipeline" Williams"}
This is also works with the player's gender - for example:
This is a test string and the player is {G "a male character" "a female pilot"}.
...in this case, the G character signifies that the following text is mutable
based on the player's gender; if the player is male, the first string is used,
otherwise the second string is used. Note that the "!" token works here as
usual.
You can also change the text based on whether or not the player is registered:
This is a test string you {P "have paid" "haven't paid"}.
...in this case, the P character signifies that the following text is mutable
based on whether or not the game is registered; if the player has registered,
the first string is used, otherwise the second string is used. Note that the
"!" token works here as usual, and you can also append a number to the P
character to specify a number of days, just as you can with the ncb Pxxx
test operator.
And also:
Whenever Nova displays a desc resource related to a mission, such as the
initial mission description (desc ID 4000-4255) or one of the special mission
briefings (e.g. CompText and QuickBrief) it performs one other special operation
on the text. It searches through the text and replaces a few special "wildcard"
symbols with pertinent mission information. This is extremely useful in setting
up mission briefings that include random information that wouldn't be known when
the description is written. These special symbols and their expansions are:
<DSY> The name of the destination system
<DST> The name of the destination stellar
<RSY> The name of the return system
<RST> The name of the return stellar
<CT> The name of the type of cargo to be carried
<CQ> The quantity of cargo to be carried
<DL> The date of the mission deadline, if any
<PAY> Absolute value of mission pay (does nothing if the mission pay
isn't monetary)
<REG> Who Nova is registered to, or "UNREGISTERED"
<PN> The player's name
<PNN> The player's nickname. If no nickname was specified, Nova will use
the player's full name here instead.
<PSN> The player's ship's name
<PST> The player's ship type (comes from the resource name of the player's
ship type's shďp resource)
<PRK> The ConvName of the highest-weighted active rank resource. If none
is found, this will be replaced with "captain".
<SRK> The ShortName of the highest-weighted active rank resource. If none
is found, this will be replaced with "captain".
<PRKnnn> Same as <PRK>, but only for ranks affiliated with government ID nnn.
Note that you can only do this once per description, or bad things
might happen.
<SRKnnn> Same as <SRK>, but only for ranks affiliated with government ID nnn.
Note that you can only do this once per description, or bad things
might happen.
<RRK> The full name of the most recently activated rank resource. Note
that it's best to only use this in a mission briefing where you
know that you've just given the player a rank, because otherwise
bad things could happen. (e.g. the most recently activated rank
pointer isn't cached between game sessions)
<OSN> The offering ship name (only works when offering a mission from a
ship)
<SN> Special ship name (Note: Nova will screw up if you use this in the
initial mission description, as it doesn't pick the special ship
names until you actually accept the mission.)
Is that what you wanted to know?
Edit: Let's see if that worked this time...
------------------
"I've just had an apostrophe!"
"I think you mean an epiphany."
"Lightning has just struck my brain!"
"Well, that must hurt!"
(This message has been edited by P-Psycho (edited 09-11-2002).)