Why no consistency with #CONDITION_POSITION ?

[DarkHorse2]

Why can I not use '[<]' symbol with #CONDITION_POSITION in surrender_2.txt like I can in popup.txt ?

Why have the same statements act differently?

In popup.txt I can do the following...

Code: Select all

; Axis have less than 4 units within 10 hexes of Warsaw(188,76)
#CONDITION_POSITION= 188,76 [10,10] [4,4] [1] [0] [<]

But this causes a scripting error in surrender_2.txt

---

CONDITION_POSITION error.jpg (131.78 KiB) Viewed 302 times

[Hubert Cater]

This will be possible in the next update/patch, e.g. all events that use the #CONDITION_POSITION will be able to make use of the [<] as well as the <unit_id, ...> functionality.

[DarkHorse2]

This will be possible in the next update/patch, e.g. all events that use the #CONDITION_POSITION will be able to make use of the [<] as well as the <unit_id, ...> functionality.

Excellent.

This is a good direction to go!