Ihave two crons set up like so:
First cron (321)
Duration 0
Pre and post holdoff 0.
Avail on: b3800 & (b3801 & (b3811 & !b3812))
On Start: g600 b3802
On End: !b3800 !b3801 b3812
First cron (302)
Duration 3
Pre and Post holdoff 0.
Avail on: !b3801 & (b3812 & !b3813)
On start: !b3800 b3801
On end: b3800

Now once b3800, b3801 and b3811 are set, you would expect the following to happen:
321 kicks in, and does G600 and b3802.
321 immediately ends and does ! b3800, !b3801, and b3812
Next day, 302 kicks in, and does !b3800 and b3801.
3 days later, 302 does b3800
End state:
B3800, b3801, b3811, b3812, b3802.
(which in turn enables another cron)

In fact, the following happens (excerpted from the debug log:
landing on spob 426 (Earth)
evaluating ncb set string '!b6021' (terminating cron 184)
evaluating ncb set string '!b6022' (terminating cron 185)
evaluating ncb set string '!b6033' (terminating cron 192)
evaluating ncb set string 'b3800' (terminating cron 301)
evaluating ncb set string 'g600 b3802' (activating cron 321)
evaluating ncb set string '!b3800 !b3801 b3812' (terminating cron 321)
landing on spob 426 (Earth)
evaluating ncb set string '!b6021' (terminating cron 184)
evaluating ncb set string '!b6022' (terminating cron 185)
evaluating ncb set string '!b6033' (terminating cron 192)
evaluating ncb set string '!b3800 b3801' (activating cron 302)
evaluating ncb set string '!b3800 !b3801 b3812' (terminating cron 321)
(and three days later, 302 ends and sets b3800)

Thus, the on end for 321 evals twice, leaving the end state as
B3800, !b3801, b3811, b3812, b3802.
Thus 302 runs a second time before all the bits are set the way they should be.
This is a Bad Thing.

Another apparent bug:
In the pilot log the following is shown:
184 - durationCounter: -3582 holdoffCounter: 0
185 - durationCounter: -3573 holdoffCounter: 0
192 - durationCounter: -3585 holdoffCounter: 0
Those should have all been deactivated, well, about a DECADE AGO!
What the heck is up with them! Thier On End's are getting evaluted every single f***ing day!!!!! WHY?!

This was observed on PC nova, and it is not clear wheather this happens on the Mac version.

What are people's thoughts on this all?
-Az

------------------

You shouldn't have duration, pre-holdoff, and post-holdoff all set to zero.

------------------
Moderator- (url="http://"http://www.AmbrosiaSW.com/cgi-bin/ubb/forumdisplay.cgi?action=topics&number;=9&SUBMIT;=Go&mrxak;=cool")EV Developer's Corner(/url) | (url="http://"http://www.ambrosiasw.com/cgi-bin/ubb/forumdisplay.cgi?action=topics&number;=69SUBMIT=Go&mrxak;=cool")Uplink Web Board(/url) | (url="http://"http://forums.evula.com/viewforum.php?f=18")mrxak's Assorted Webspace Forum(/url) | (url="http://"http://forums.evula.com/viewforum.php?f=48")Starcraft Forum(/url) | | (url="http://"http://directory.perfectparadox.com/profile.php?id=00008")My Profile(/url) | (url="http://"http://www.AmbrosiaSW.com/cgi-bin/ubb/postdisplay.cgi?forum=Forum10&topic;=007599-2&whichpost;=mrxak11-06-200203:22PM")mrxak(/url)
(url="http://"http://www.evula.org/mrxak/")mrxak's Assorted Webspace(/url) | (url="http://"http://www.evula.org/mrxak/Haikus/haikuarchive.html")The Haiku Archive(/url) | (url="http://"http://www.evula.org/mrxak/EV/N/mbspt/mbspt.html")mrxak's Big Secret Plug-in/Tutorial(/url) | (url="http://"http://www.evula.org/mrxak/EV/N/amtc/amtc.html")A mrxak TC(/url) | (url="http://"http://www.ambrosiasw.com/cgi-bin/vftp/dl-redirect.pl/TheChallenge102.sea.bin?path=evn/plugins&file;=TheChallenge102.sea.bin")The Challenge v1.0.2(/url)
(url="http://"http://www.AmbrosiaSW.com/cgi-bin/ubb/search.cgi?action=intro")Search First(/url) | (url="http://"http://www.macgamer.net/games/uplink/")Uplink Guide(/url) | (url="http://"http://www.evula.com/survival_guide/")EV/O/N Guide(/url) | (url="http://"http://www.ambrosiasw.com/cgi-bin/ubb/forumdisplay.cgi?action=topics&number;=31&SUBMIT;=Go")Plug-in Guide(/url) | (url="http://"http://www.AmbrosiaSW.com/webboard/Forum9/HTML/003091.html")Plug-in Testers(/url) | (url="http://"http://www.AmbrosiaSW.com/webboard/Forum9/HTML/003196.html")Developers(/url) | (url="http://"http://www.AmbrosiaSW.com/games/evn/addons.html")Nova Addons(/url) | (url="http://"http://www.resexcellence.com/support_files/resedit.shtml")ResEdit(/url) | (url="http://"http://w00tware.ev-nova.net/")NovaTools(/url)
"Seize opportunity by the beard, for it is bald behind." -Bulgarian Proverb

Quote

Originally posted by mrxak:
**You shouldn't have duration, pre-holdoff, and post-holdoff all set to zero.

**

The ones with all of those set to zero are instantaneous events. In the final version there will be 4 or 5 sets of them, all with identical enableon fields, but with different require fields (the coresponding contribute bits being in the ships). Thus, i need only have one set of crons to do each delay (some ships will have a longer delay between breakdowns), and one set of crons for each kind of damage to assign (an "engine damage" outfit that would make a Leviathan owner very sad wouldnt even be noticed by the captain of a PV IV). The alternative of having one set of crons for each combination of damage type and delay would use a prohibitive number of crons (and be less than graceful).

Do you propose that the issue of all of those fields being set to zero is the cause of this bug? How many of them theoretically have to be non-zero for everything to work?

Does anyone have any thoughts on the issue I pointed out with the stock scenario, where crons just dont go away?
-Az

------------------

What mrxak is saying is exactly what Matt Burch told him. He raised the problem on the Nova beta list, and Matt said "Setting all those values to zero is wrong."

Sorry, didn't get any more info than that.

Dave @ ATMOS

Quote

Originally posted by pipeline:
**What mrxak is saying is exactly what Matt Burch told him. He raised the problem on the Nova beta list, and Matt said "Setting all those values to zero is wrong."

Sorry, didn't get any more info than that.

Dave @ ATMOS**

Aaah, Okay.
Thanks.
Mabey tossing a 1 into the post-holdoff will make it happier. (in anycase, i worked around the issue here by just putting all the ncb set commands into the OnStart)

There is still the strange issue in the stock scenario with crons running forever, though, that I cannot explain, and which doesnt effect me directly, but makes me wonder about it.
-Az

------------------