The "xxx" in "bxxx" are the three digits you assign to the ncb (Nova Control Bit). The expression Bxxx (or bxxx), where xxx are those three digits, means check to see if the ncb is turned on, while !Bxxx (or !bxxx) checks to see if it's turned off.
In the s˙st resource, then, this expression goes in the VisBit field (VisBit means "This is the ncb that determines if this system is active or not").
So, let's say, for example, you want two versions of the Kania system -- the regular one, and one where the Hypergate's been irreparably destroyed -- won't ever regenerate. You duplicate the Kania system, but in place of the spöb with the active hypergate, the duplicate refers to another spöb with the same name but basically inactive, using the damaged Hypergate graphic.
So we first assign a VisBit -- in this case, let's arbitrarily pick b5273 (the ncbs number from b0 to b9999), after making sure that b5273 isn't used anywhere else in the Nova Scenario first (and as far as I know, no one's mapped out a currently-used ncb list for Nova 1.0.3 yet, and I made up b5273, which, for all I know, could be used, but let's say for the sake of argument that it isn't) to our two systems.
Now, you want the first version, the one with the active Hypergate, to be the default, the system you come to when you first start the game. The event that triggers our destroyed Hypergate hasn't happened yet, and when you first start up Nova, all the ncbs start off turned off, so that means in the original Kania s˙st we want to put !b5273 in the VisBit field. This tells Nova to make the original Kania active if b5273 is turned off (which it is to begin with). In our copy without the active Hypergate, we put b5273 in the VisBit field.
What happens now is that when b5273 gets set, the original version of Kania will be turned off, while the copy will be turned on.
Now you're probably asking "Okay, so how do I turn on b5273?" The answer is: pretty much anywhere where ncbs can be activated. You could, for instance, make an oütf called "Destroy the Kania Hypergate," and in the OnBuy field put b5273. Then, as soon as that oütf is purchased, the bit is set and our two systems flip on and off, respectively. Or, as Russell said, you could make a crön which is set to go off at a certain time, and at the end of that time the systems switch on/off by putting b5273 in the OnEnd field. Or, if you fail a particular mission, you could turn that ncb on as a consequence, by putting b5273 in the OnFail field.
Does that help?
(edit) Oh, and I think you have to make sure the systems linked to your first system must also be linked to your second system. (/edit)
------------------
Starfleet Adventures: A Star Trek TC for EVN (url="http://"http://www.ev-nova.net/forums/viewtopic.php?t=145") Discussion Board (/url)
Starfleet Adventures (url="http://"http://www.ev-nova.net/forums/viewtopic.php?t=71")Progress Log(/url)
It is better to feed the goat than it is today.
(This message has been edited by UncleTwitchy (edited 01-30-2003).)