Crön

Crön (abbreviated form of chronological) is a type of data resource in EV Nova. These crons are time based events.

The crön resource

ℹ️️

EV Bible text

The following information was transcribed from the Nova Bible, ©1995-2006 by Matt Burch. The original document can be viewed here.

Cron resources are used to define time-dependent events that occur in a manner that is invisible to the player but can cause interesting things to happen in the universe, via the manipulation of control bits. With it, you can create such things as:

• an event that occurs periodically during the course of the game
• an event that occurs at some fixed date during the game, as part of the story's set script
• an event, triggered by the actions of the player, that occurs after some fixed or random interval
• etc.

Fields

• FirstDay: The first day of the month (1-31) on which the cron event can be activated. If you set this to 0 or -1, this field will be ignored and only FirstMonth and FirstYear will be considered.
• FirstMonth: The first month of the year (1-12) on which the cron event can be activated. Set to 0 or -1 for this to be ignored.
• FirstYear: The first year in which the cron event can be activated. Set to 0 or -1 for this to be ignored.
• LastDay: The last day of the month (1-31) on which the cron event can be activated. Set to 0 or -1 for this to be ignored.
• LastMonth: The last month of the year (1-12) on which the cron event can be activated. Set to 0 or -1 for this to be ignored.
• LastYear: The last year in which the cron event can be activated. Set to 0 or -1 for this to be ignored.

• Random: The percent chance that the cron event will be activated during the date range defined above. Set to 100 for the event to be activated as soon as it can be.

• Duration: The duration during which the event is active, in days. If this is set to zero, the event will start and end on the same day, i.e. its OnStart and OnEnd scripts will be run at the same time.

• PreHoldoff: The number of days to "hold" the event in a waiting state after it is activated and before it starts. Set this to zero to have the event start immediately when it is activated.
• PostHoldoff: The number of days to hold the event in a waiting state after it ends and before it is deactivated. This is used to keep a repeating event from being activated immediately after it has just happened. Set this to zero to have the event be deactivated immediately after it ends.

Flags

• 0x0001: Continuous, iterative cron entry - keep evaluating the cron's OnStart field until the EnableOn expression is no longer true or the constraints of the Require fields are no longer met. This can create infinite loops, so be careful!
• 0x0002: Continuous, iterative cron exit - keep evaluating the cron's OnExit field until the EnableOn expression is no longer true or the constraints of the Require fields are no longer met. This can create infinite loops, so be careful!

• EnableOn: A control bit test string that is used to determine whether the cron event is eligible to be activated or not. Leave this blank if you are creating an event whose activation doesn't depend on the state of any control bits.

• OnStart: A control bit set string that is called when the cron event starts, after waiting through the PreHoldoff time, if any.

• OnEnd: A control bit set string that is called when the cron event ends.

Contribute

There are two fields.

When the cron event is active, these two Contribute fields together form a 64-bit flag that is subsequently combined with the Contribute fields from the player's ship and the other outfit items in the player's possession, to be used with the Require fields in the outf and misn resources.

Require

There are two fields.

These two Require fields together form a 64-bit flag that is logically and'ed with the Contribute fields from the player's current ship and outfit items. Unless for each 1 bit in the Require fields there is a matching 1 bit in one or more of the Contribute fields, the cron will not be activated. Leave these set to zero if unused.

News

• NewsGovt1-4: On planets or stations that are allied with the government
• GovtNewsStr1-4: whose ID is given by one of the NewsGovt fields, a string will be randomly selected from the STR# resource whose ID is given by the corresponding GovtNewsStr field, and will be displayed as news while the cron event is active. This allows you to let up to four different governments (and their allies) have their own "local news" for a given cron event. Set unused NewsGovt and GovtNewsStr fields to -1.
• IndNewsStr: The ID of a STR# resource from which to randomly select a string to be displayed in the news dialog while this cron event is in progress, if it doesn't have any applicable local news. Set to -1 for no independent news.

Some notes

1. Setting any of the above date fields to 0 or -1 effectively makes that field a wildcard field, which will match to anything.
2. If you want an event with a wide possible date range to be guaranteed to never run more than once, make it set a control bit in its OnEnd script that will prevent it from subsequently being eligible for activation.
3. The 'M' and 'N' control bit set string operators should probably not be used in conjunction with cron events, unless you really want to confuse the player by moving him around at seemingly random times.
4. Local news always takes precedence over independent news, even if there is no corresponding news string to display (the STR# ID must still be greater than zero to not be ignored). You can use this to make everyone in the universe except a particular government or set of governments report on something, for example.