Event priority?

[Olle_Petersson]

I've been checking around the events in current scenarios, and found a few where more than one event was triggered simultaneously (by date).
Here a group variable was set in one event and used in another, which wouldn't work if the "use" event was processed before the "set" event.

In another scenario one event checked for victory at the end of each month and another event checked for game lost (by time) at the end of each year.
This means that if I meet the victory conditions during december 1999, then at 2400hrs 1999-12-28 both the victory and loss events will have their conditions met.
Will it be a win or loss?

In short:
What determines in which order events are processed?

TIA
Olle

[CafeDave]

Hi Olle,
I have come up against this problem a few times in my scenario too.   It seems that with Tropico, like in RRT2, there are a few built-in event priorities, which I think are as follows:
1. Month end will occur before year end and year begin before month begin.  Same for weeks and days.  This is how RRT2 worked anyway.
2. A called event will actually show its message before any message in the event that called it, even though the conditions and other settings would have been evaluated first in the calling event.  In my scenario I set up a briefing event with a message to appear after the briefing then called the actual intro event which appears first.
3. I think a choice event occurring at the same time as another event will show its message first.

That's all I know of right now.

[Olle_Petersson]

Thanks for the reply. I guess I'll have to make a few tests.

1. Month end will occur before year end ...

This much I guessed too, and it seems sensible.

Priority by CheckFrequency, from top to bottom:

• OnlyWhenCalled
• YearBegin
• MonthBegin
• WeekBegin
• DayBegin
• DayEnd
• WeekEnd
• MonthEnd
• YearEnd

Added: This posting was my 100th, which made me a Rebel!!!

Cheers
Olle

[CafeDave]

Woohoo!  Congrats Olle!  Watch out for Eddy though.  

[Coconut Kid]

There seems to be a principle here.

A specifically called event shows its message first no matter if other related events transpired to call it.

Calendar scheduled events work their way from year begin through to year end. It's cutting it very fine to distinguish between day begin and day end.

It may be helpful to remember that all the data in the Almanac is produced with these same priorities. The Almanac automatically appears at year end. However, it can be called at any time -- when is the data produced for the 'called' Almanac?