HEAVY SPOILER WARNING
HEAVY SPOILER WARNING
HEAVY SPOILER WARNING
IIRC,
'random' invasion points of scripted one-time-events are fix if they are derived from the same .map file. I.e. to randomize them again (after creation of event), it is necessary to load them into the map editor. This confers to events 36 - 40 below.
As you can see I have the invasion points 7-2-7-6-4 instead of NeroWould's 6-6-4-6-4 (which is probably a Pharao install).
As Max pointed out, the critical event is ' 19', this one is (logical) unavoidable and the only one with "moving" invasion points (but only from 1-3 and not 1-8).
Now the question: when is the invasion point of event 19 determined?
(You both are right)
When the soldiers of the previous event (18 water invasion) are disembarked, this event is from the 'event state machines point of view' completed. Now event 19 is triggered & the invasion point randomized. 3 months later the first invasion message of event 19 is emitted. A year later the invasion begins.
Who has seen the loophole???
A design flaw: if all transports of (18 water invasion) are sunk before reaching their destiny, event 19 is never triggered - resulting in a broken event chain. BTW, ..., ok, all who are interested know that thread. (The following information was obtained directly from "Iken" in my Cleo2.1 installation)
-------------------------------------------------------
EVE.EXE: Pharaoh/Cleo xxx.map & xxx.sav __EventListViewer__V1.6 (by civilis)
/*********************************| eve e iken.sav |***/ [...]' 16':
Request of a city, city: 5, (1x), Feb year 1,
'threat', delay 1 months, [status: 0/00]
goods: copper, amount: 200
comply:auto->' 17' reject:auto->' 20' belate:auto->' 17'' 17':
KR decrease, (trig), in months: 1, auto->' 18'
amount: 35, city: 5
' 18':
Invasion, (trig), in months: 6, cyclic->' 19'
enemy army, strength: 32, warships: 5, delay 9 months,
route: 5, invasionpoints: 9, target: random
' 19':
Invasion, (trig), in months: 3, cyclic->' 21'
enemy army, strength: 64, delay 12 months,
route: 5, invasionpoints: 1-3 [2], target: food' 20':
KR increase, (trig), in months: 1, random->' 18'
amount: 15, city: 5
' 21':
Invasion, (trig), in months: 3, cyclic->' 22'
enemy army, strength: 72, delay 12 months,
route: 5, invasionpoints: 3, target: troops
' 22':
Invasion, (trig), in months: 9, cyclic->' 23'
enemy army, strength: 24, warships: 6, delay 9 months,
route: 5, invasionpoints: 9, target: food
' 23':
Invasion, (trig), in months: 2, specific->' 25'
enemy army, strength: 96, delay 4 months,
route: 5, invasionpoints: 3, target: random
' 24':
City status change, (trig), in months: 1, auto->'stop'
city: 5 'trade route available'
' 25':
KR increase, (trig), in months: 6, direct->' 24'
amount: 25, city: 2
[...]' 36':
Invasion, (1x), Oct year 12, auto->'stop'
bedouin army, strength: 64, delay 6 months,
route: !!!route conflict, invasionpoints: 1-8 [7], target: random, [status: 0/00]' 37':
Invasion, (1x), Apr year 15, auto->'stop'
bedouin army, strength: 64, delay 6 months,
route: !!!route conflict, invasionpoints: 1-8 [2], target: random, [status: 0/00]' 38':
Invasion, (1x), Nov year 20, auto->'stop'
bedouin army, strength: 64, delay 4 months,
route: !!!route conflict, invasionpoints: 1-8 [7], target: random, [status: 0/00]' 39':
Invasion, (1x), Aug year 23, auto->'stop'
bedouin army, strength: 96, delay 6 months,
route: !!!route conflict, invasionpoints: 1-8 [6], target: random, [status: 0/00]' 40':
Invasion, (1x), Jan year 27, auto->'stop'
bedouin army, strength: 96, delay 4 months,
route: !!!route conflict, invasionpoints: 1-8 [4], target: random, [status: 0/00]