After a look through the events file I noticed that some events have two arguments (i.e. two turns are given).
Judging from the events that this is done for (world_is_round, timurids_invasion_warn and similar), I concluded that these turn settings probably give an interval from which one turn is randomly chosen by the game to trigger the event.
As an example:
This would mean that the America's are discovered in between turns 320 and 328Code:event historic world_is_round date 320 328
[Edit] The dates are supplied in years, not in turns. That means the game will be discovered between turns 160 and 164[/Edit]
If anybody's interested, this is how the discovery of America works:
This means that after the world_is_round event mentioned above, America can be discovered. When somebody sends a ship there, you get another historic_event and afterwards, when somebody sees an Aztec token, the Aztecs are finally activated and another historic event is triggered.Code:;-- World is round -- monitor_event EventCounter EventCounterType world_is_round and EventCounter > 0 ; unhide America restrict_strat_radar false terminate_monitor end_monitor ;-- America discovered -- monitor_event TileSeen not FactionType aztecs and not FactionType slave and IsPositionInRect 0 48 40 141 historic_event america_discovered event/america_discovered.bik terminate_monitor end_monitor ;-- Aztecs contacted -- monitor_event ObjSeen TargetFactionType aztecs and not FactionType slave unfreeze_faction_ai aztecs add_events event counter disable_no_brigands date 0 event counter disable_no_pirates date 0 end_add_events historic_event aztecs_contacted event/aztecs_contacted.bik terminate_monitor end_monitor
What actually excites me about these are the two new events: ObjSeen and TileSeen that will allow us to create a whole new class of similar discovery events and probably a lot more because we can for example check if an army can see an opposing one, etc. pp.


Reply With Quote



Bookmarks