Build 256
--------------
New event-type: “Unit is in area”. This allows the scenario author to fire an event when a specified unit remains inside a given area for the specified amount of time. The unit-filter is the same as with the “Unit is destroyed/damaged” triggers so you can filter the eligibility from side-wide all the way down to specific unit. The specified time can vary from 1 second all the way to entire decades.

The time accumulation to fulfill the trigger must be continuous; so for example if the specified time is 2 hours, and an eligible unit stays in the area for 1 hour but then steps out even for a few seconds and comes back in, the trigger’s “clock” is reset and the unit (or another eligible one) must again stay in the area for at least 2 hours.

Build 258
-------------------
• New major feature: OODA delay (reaction time – tactical surprise). Each platform has a given OODA value which dictates its delay in engaging new contacts after first targeting them. The value depends on a number of factors but primarily is affected by the platform’s technological level and its degree of combat system automation & integration.
Tactically this feature means that platforms no longer instantly engage threats right upon detecting them, but have a given delay – which can often prove fatal. Some highly-automated systems like Aegis or most modern CIWS systems (and most decoy & countermeasure launchers) are not affected by this and can instantly engage threats.

Iosef escribió:Menos videos y una fecha de lanzamiento por dios.....