Offsets in triggered events

[George LeS]

If an event includes an offset, if it is triggered after it's startdate, when does the system treat is as having already passed through part of the offset period, or does it act as if the offset started when the trigger condition is met?

For example, say the event includes a trigger condition requiring Infra 4, has a start date of 1/1/1500, & an offset of 36000 (100 years). You actually reach infra 4 on 1/1/1520. Does the offset period run from
(a) 1/1/1500 - 12/30/1599, or is it
(b) 1/1/1520 - 12/30/1619, or
(c) 1/1/1520 forward, but acting as if the 1st 20% of the time had already passed.

I'm specifically asking because I'm interested in the use of paired events to fine-tune the probability of the result. And this obviously would make a big difference. (Can't find the thread, but I remember the method.)

 

[sturmvogel]

I believe it's c, as I'm pretty sure that it's neither a (the offset doesn't come into play until the trigger conditions are met) nor b since the deathdate is fixed. So it's possible that the event won't fire at all if the offset is too long and the triggers are achieved late.

 

[George LeS]

I believe it's c, as I'm pretty sure that it's neither a (the offset doesn't come into play until the trigger conditions are met) nor b since the deathdate is fixed. So it's possible that the event won't fire at all if the offset is too long and the triggers are achieved late.

The method I'm referring to, someone posted it some time ago. I thought it looked useful. You set up 2 events, E1 & E2, each of which includes a command sleeping the other. Say E1 has a start of 1/1/1419, & a 100-day offset. E2 has an exact date, which occurs during the offset period for E1. By picking the date of E2, you have effectively given each a % chance of firing.

I like this idea, but I'm not at all sure how it will work if both are dependent on an earlier event, & I'm not sure how to test it, either.

 

[sturmvogel]

The method I'm referring to, someone posted it some time ago. I thought it looked useful. You set up 2 events, E1 & E2, each of which includes a command sleeping the other. Say E1 has a start of 1/1/1419, & a 100-day offset. E2 has an exact date, which occurs during the offset period for E1. By picking the date of E2, you have effectively given each a % chance of firing.

I like this idea, but I'm not at all sure how it will work if both are dependent on an earlier event, & I'm not sure how to test it, either.

I really don't see the utility of this. Seems like a lot of coding that could be better put to use judiciously picking your offset and deathdates.

 

[George LeS]

I really don't see the utility of this. Seems like a lot of coding that could be better put to use judiciously picking your offset and deathdates.

IMO, being able to adjust probabilities is a big benefit. It would take a lot of work, granted, & several events, but you could replace the clear either/or lines currently in place, with graded odds.

Take Heretics Converted & Unexpected Invention. They're really complementary, but it always bothered me that this seemed unrealistic, that there is a clear point on the sliders where each becomes possible. It would be much better if high Inno gave you 10 x the odds of the Manu, & 1/10 the chance of a conversion.

 

[Garbon]

But those are random events, you wouldn't be able to use the sleep commands on random events.

 

[George LeS]

But those are random events, you wouldn't be able to use the sleep commands on random events.

But you can use triggers in random events.
(a) You may be able to use an event itself, for a trigger (I'll test this),
(b) you can definitely use the effects of an event,
(c) you can trigger a random event from a non-random event (I've tried this), and
(d) you can set up an event, mirroring the effects of a random event.