Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
Okay, I think I understand. When the first mďsn evaluates, bwhatever is set, which the crön requires. The crön starts at some soon point depending on its random chance of happening, lasts five days, then sets a second bit, which allows the second mďsn to occur. Right?
Will the randomization factor give it a little variation besides five days immediately after the first mďsn?
-K
------------------ -- Art History = Cool! ...and yes, I'm odd. --
If you play with the randomization, it should add some variance, though not too much. If you are going to play with randomization, consider turning the duration down to, say 3 days, because there is always the tiny possibiity that it will take like 50 days before the crön's random factor is met.
------------------ Eat blazing electric death! (url="http://"http://www.evula.org/infernostudios/ept/")Unofficial EV and EVO Ports(/url): Both currently in FC1. Please post any bugs (url="http://"http://www.ev-nova.net/forums/viewforum.php?f=26")here(/url).
Augh! It's not working at all.. I looked in my debuglog, and it says that the crön is being activated, and b7003 (which the crön sets) is set in the pilotlog, and so the mďsn has everything needed in order to start, but it never shows up. It's set to appear in the Mission BBS, with ATTN: <PN> as the title, and requires (b7000 & b7003) & !b7001. I've tested four times, and it never shows up.. the crön, according to debuglog, works, but nothing seems to happen. wail Why do my stupid resources not like me?
(edit) Going to move this to a new topic, as this one is rather bogged down and not entirely relater..(/edit)
(This message has been edited by Kate (edited 06-02-2003).)