Can ALiVE modules be hooked up to triggers, or do they play well with triggers?
For example... Could I hook a placement module up to a trigger, so that the OPCOM only starts processing that TAOR once BLUFOR enters the trigger?
Can ALiVE modules be hooked up to triggers, or do they play well with triggers?
For example... Could I hook a placement module up to a trigger, so that the OPCOM only starts processing that TAOR once BLUFOR enters the trigger?
Does not work :( @Tupolov this would be an awesome idea though man. Could solve performance issues when combined with profiling... AI wouldn't even process parts of the map until they became relevant to the mission.
The modules for Objectives and Unit Placement are run at mission init, so it's not as simple as hooking them to a trigger. You can however script in additional objectives for the AI Commander and add profiles via trigger during runtime. Some examples are on the wiki: http://alivemod.com/wiki/index.php/Script_Snippets#Add_a_Custom_OPCOM_Objective
Profiles have next to no impact on performance whilst Virtualised, so if you set your TAOR's and placements up right there's really no need to trigger them on and off.
@Friznit thanks for the prompt response.would scripting in objectives allow the opcom to prioritize and focus better, perhaps? Also, follow on question. What does have the most performance impact?
Won't have in impact on performance. The new objectives will get prioritised using the same criteria (size and priority weighting) on the next OPCOM cycle.