weyne/MOOSE_DOCS
1
0
Fork 0
mirror of https://github.com/FlightControl-Master/MOOSE_DOCS.git synced 2025-08-15 10:37:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

MOOSE generated documentation [skip ci]

Browse Source
This commit is contained in:
Applevangelist 2021-12-20 12:06:00 +00:00
parent 1e732ea232
commit be8c95fcfd
69 changed files with 2023 additions and 1676 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Documentation/AI.AI_A2A_Cap.html
View File

@ -8495,7 +8495,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -8824,7 +8824,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -9098,7 +9098,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -9109,7 +9109,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -9142,7 +9142,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -9412,7 +9412,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -9554,7 +9554,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_A2A_Dispatcher.html
View File

@ -12863,7 +12863,7 @@ They will lock the parking spot.</p>
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -13192,7 +13192,7 @@ They will lock the parking spot.</p>
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -13466,7 +13466,7 @@ They will lock the parking spot.</p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -13477,7 +13477,7 @@ They will lock the parking spot.</p>
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -13510,7 +13510,7 @@ They will lock the parking spot.</p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -13780,7 +13780,7 @@ They will lock the parking spot.</p>
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -13922,7 +13922,7 @@ They will lock the parking spot.</p>
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_A2G_Dispatcher.html
View File

@ -14837,7 +14837,7 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -15166,7 +15166,7 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -15440,7 +15440,7 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -15451,7 +15451,7 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -15484,7 +15484,7 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -15754,7 +15754,7 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -15896,7 +15896,7 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

58
Documentation/AI.AI_AIR_Dispatcher.html
View File

@ -4440,6 +4440,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p> The Defender Default Settings over all Squadrons.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(AI_AIR_DISPATCHER).DefenderPatrolIndex" ><strong>AI_AIR_DISPATCHER.DefenderPatrolIndex</strong></a>
</div>
</div>
@ -9737,6 +9748,17 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
<p> The Defender Default Settings over all Squadrons.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(AI_AIR_DISPATCHER).DefenderPatrolIndex" ><strong>AI_AIR_DISPATCHER.DefenderPatrolIndex</strong></a>
</div>
</div>
@ -11054,6 +11076,17 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
<p> The Defender Default Settings over all Squadrons.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(AI_AIR_DISPATCHER).DefenderPatrolIndex" ><strong>AI_AIR_DISPATCHER.DefenderPatrolIndex</strong></a>
</div>
</div>
@ -11585,7 +11618,7 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -11914,7 +11947,7 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -12188,7 +12221,7 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -12199,7 +12232,7 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -12232,7 +12265,7 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -12502,7 +12535,7 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -12644,7 +12677,7 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>
@ -12677,6 +12710,17 @@ multiplied by the Overhead and rounded up to the smallest integer. </p>
<p> The Defender Default Settings over all Squadrons.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(AI_AIR_DISPATCHER).DefenderPatrolIndex" ><strong>AI_AIR_DISPATCHER.DefenderPatrolIndex</strong></a>
</div>
</div>

14
Documentation/AI.AI_Air.html
View File

@ -6931,7 +6931,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -7260,7 +7260,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -7534,7 +7534,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -7545,7 +7545,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -7578,7 +7578,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -7848,7 +7848,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -7990,7 +7990,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_Air_Patrol.html
View File

@ -8025,7 +8025,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -8354,7 +8354,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -8628,7 +8628,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -8639,7 +8639,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -8672,7 +8672,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -8942,7 +8942,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -9084,7 +9084,7 @@ Once the time is finished, the old AI will return to the base.</p>
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_Bai.html
View File

@ -9895,7 +9895,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -10224,7 +10224,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -10498,7 +10498,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -10509,7 +10509,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -10542,7 +10542,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -10812,7 +10812,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -10954,7 +10954,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_Balancer.html
View File

@ -3876,7 +3876,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -4205,7 +4205,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -4479,7 +4479,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -4490,7 +4490,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -4523,7 +4523,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -4793,7 +4793,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -4935,7 +4935,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_Cap.html
View File

@ -9506,7 +9506,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -9835,7 +9835,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -10109,7 +10109,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -10120,7 +10120,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -10153,7 +10153,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -10423,7 +10423,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -10565,7 +10565,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_Cargo.html
View File

@ -5695,7 +5695,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -6024,7 +6024,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -6298,7 +6298,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6309,7 +6309,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -6342,7 +6342,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6612,7 +6612,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -6754,7 +6754,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_Cargo_APC.html
View File

@ -7562,7 +7562,7 @@ AICargoAPC:SetCombatRadius( false )</code></pre>
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -7891,7 +7891,7 @@ AICargoAPC:SetCombatRadius( false )</code></pre>
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -8165,7 +8165,7 @@ AICargoAPC:SetCombatRadius( false )</code></pre>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -8176,7 +8176,7 @@ AICargoAPC:SetCombatRadius( false )</code></pre>
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -8209,7 +8209,7 @@ AICargoAPC:SetCombatRadius( false )</code></pre>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -8479,7 +8479,7 @@ AICargoAPC:SetCombatRadius( false )</code></pre>
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -8621,7 +8621,7 @@ AICargoAPC:SetCombatRadius( false )</code></pre>
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

82
Documentation/AI.AI_Cargo_Airplane.html
View File

@ -2619,6 +2619,20 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div class="w3-white" id="record_type">
<div class="fields w3-container w3-theme-l2">
<h2>Field(s)</h2>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(AI_CARGO_AIRPLANE).Airbase" ><strong>AI_CARGO_AIRPLANE.Airbase</strong></a>
<p> Set destination airbase for next :Route() command.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -2650,6 +2664,9 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p> Aircraft is on a depoly mission.</p>
</div>
</div>
@ -4395,6 +4412,20 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div class="fields w3-container w3-theme-l2">
<h2>Field(s)</h2>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(AI_CARGO_AIRPLANE).Airbase" ><strong>AI_CARGO_AIRPLANE.Airbase</strong></a>
<p> Set destination airbase for next :Route() command.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -4426,6 +4457,9 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p> Aircraft is on a depoly mission.</p>
</div>
</div>
@ -5013,6 +5047,20 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div class="fields w3-container w3-theme-l2">
<h2>Field(s)</h2>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(AI_CARGO_AIRPLANE).Airbase" ><strong>AI_CARGO_AIRPLANE.Airbase</strong></a>
<p> Set destination airbase for next :Route() command.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -5044,6 +5092,9 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p> Aircraft is on a depoly mission.</p>
</div>
</div>
@ -5443,7 +5494,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -5772,7 +5823,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -6046,7 +6097,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6057,7 +6108,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -6090,7 +6141,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6360,7 +6411,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -6502,7 +6553,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>
@ -6523,6 +6574,20 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div class="fields w3-container w3-theme-l2">
<h2>Field(s)</h2>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(AI_CARGO_AIRPLANE).Airbase" ><strong>AI_CARGO_AIRPLANE.Airbase</strong></a>
<p> Set destination airbase for next :Route() command.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -6554,6 +6619,9 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p> Aircraft is on a depoly mission.</p>
</div>
</div>

14
Documentation/AI.AI_Cargo_Dispatcher.html
View File

@ -6230,7 +6230,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -6559,7 +6559,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -6833,7 +6833,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6844,7 +6844,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -6877,7 +6877,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -7147,7 +7147,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -7289,7 +7289,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_Cargo_Dispatcher_APC.html
View File

@ -5830,7 +5830,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -6159,7 +6159,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -6433,7 +6433,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6444,7 +6444,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -6477,7 +6477,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6747,7 +6747,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -6889,7 +6889,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_Cargo_Dispatcher_Airplane.html
View File

@ -5424,7 +5424,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -5753,7 +5753,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -6027,7 +6027,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6038,7 +6038,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -6071,7 +6071,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6341,7 +6341,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -6483,7 +6483,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_Cargo_Dispatcher_Helicopter.html
View File

@ -5456,7 +5456,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -5785,7 +5785,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -6059,7 +6059,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6070,7 +6070,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -6103,7 +6103,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6373,7 +6373,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -6515,7 +6515,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_Cargo_Dispatcher_Ship.html
View File

@ -5499,7 +5499,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -5828,7 +5828,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -6102,7 +6102,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6113,7 +6113,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -6146,7 +6146,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6416,7 +6416,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -6558,7 +6558,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_Cargo_Helicopter.html
View File

@ -5760,7 +5760,7 @@ Adjust if necessary.</code></pre>
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -6089,7 +6089,7 @@ Adjust if necessary.</code></pre>
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -6363,7 +6363,7 @@ Adjust if necessary.</code></pre>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6374,7 +6374,7 @@ Adjust if necessary.</code></pre>
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -6407,7 +6407,7 @@ Adjust if necessary.</code></pre>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6677,7 +6677,7 @@ Adjust if necessary.</code></pre>
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -6819,7 +6819,7 @@ Adjust if necessary.</code></pre>
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_Cargo_Ship.html
View File

@ -6760,7 +6760,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -7089,7 +7089,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -7363,7 +7363,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -7374,7 +7374,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -7407,7 +7407,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -7677,7 +7677,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -7819,7 +7819,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_Cas.html
View File

@ -9731,7 +9731,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -10060,7 +10060,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -10334,7 +10334,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -10345,7 +10345,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -10378,7 +10378,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -10648,7 +10648,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -10790,7 +10790,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_ESCORT_DISPATCHER_REQUEST.html
View File

@ -3269,7 +3269,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -3598,7 +3598,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -3872,7 +3872,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -3883,7 +3883,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -3916,7 +3916,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -4186,7 +4186,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -4328,7 +4328,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_Escort_Dispatcher.html
View File

@ -3290,7 +3290,7 @@ Red_SU25T_EscortDispatcher:Start()</code></pre>
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -3619,7 +3619,7 @@ Red_SU25T_EscortDispatcher:Start()</code></pre>
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -3893,7 +3893,7 @@ Red_SU25T_EscortDispatcher:Start()</code></pre>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -3904,7 +3904,7 @@ Red_SU25T_EscortDispatcher:Start()</code></pre>
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -3937,7 +3937,7 @@ Red_SU25T_EscortDispatcher:Start()</code></pre>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -4207,7 +4207,7 @@ Red_SU25T_EscortDispatcher:Start()</code></pre>
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -4349,7 +4349,7 @@ Red_SU25T_EscortDispatcher:Start()</code></pre>
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/AI.AI_Formation.html
View File

@ -10531,7 +10531,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -10860,7 +10860,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -11134,7 +11134,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -11145,7 +11145,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -11178,7 +11178,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -11448,7 +11448,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -11590,7 +11590,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

26
Documentation/AI.AI_Patrol.html
View File

@ -3136,9 +3136,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p> This table contains the targets detected during patrol.</p>
</div>
</div>
@ -6386,9 +6383,6 @@ Note that this method is required, as triggers the next route when patrolling fo
<p> This table contains the targets detected during patrol.</p>
</div>
</div>
@ -7133,9 +7127,6 @@ Note that this method is required, as triggers the next route when patrolling fo
<p> This table contains the targets detected during patrol.</p>
</div>
</div>
@ -7606,7 +7597,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -7935,7 +7926,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -8209,7 +8200,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -8220,7 +8211,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -8253,7 +8244,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -8523,7 +8514,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -8665,7 +8656,7 @@ Note that this method is required, as triggers the next route when patrolling fo
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>
@ -8772,9 +8763,6 @@ Note that this method is required, as triggers the next route when patrolling fo
<p> This table contains the targets detected during patrol.</p>
</div>
</div>

14
Documentation/Actions.Account.html
View File

@ -4630,7 +4630,7 @@ There are 2 moments when state transition methods will be called by the state ma
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -4959,7 +4959,7 @@ There are 2 moments when state transition methods will be called by the state ma
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -5233,7 +5233,7 @@ There are 2 moments when state transition methods will be called by the state ma
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -5244,7 +5244,7 @@ There are 2 moments when state transition methods will be called by the state ma
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -5277,7 +5277,7 @@ There are 2 moments when state transition methods will be called by the state ma
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -5547,7 +5547,7 @@ There are 2 moments when state transition methods will be called by the state ma
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -5689,7 +5689,7 @@ There are 2 moments when state transition methods will be called by the state ma
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/Actions.Assign.html
View File

@ -4589,7 +4589,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -4918,7 +4918,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -5192,7 +5192,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -5203,7 +5203,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -5236,7 +5236,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -5506,7 +5506,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -5648,7 +5648,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/Actions.Assist.html
View File

@ -4811,7 +4811,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -5140,7 +5140,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -5414,7 +5414,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -5425,7 +5425,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -5458,7 +5458,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -5728,7 +5728,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -5870,7 +5870,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/Actions.Route.html
View File

@ -5231,7 +5231,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -5560,7 +5560,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -5834,7 +5834,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -5845,7 +5845,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -5878,7 +5878,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6148,7 +6148,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -6290,7 +6290,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/Cargo.Cargo.html
View File

@ -8472,7 +8472,7 @@ The cargo must be in the <strong>Loaded</strong> state.</p>
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -8801,7 +8801,7 @@ The cargo must be in the <strong>Loaded</strong> state.</p>
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -9075,7 +9075,7 @@ The cargo must be in the <strong>Loaded</strong> state.</p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -9086,7 +9086,7 @@ The cargo must be in the <strong>Loaded</strong> state.</p>
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -9119,7 +9119,7 @@ The cargo must be in the <strong>Loaded</strong> state.</p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -9389,7 +9389,7 @@ The cargo must be in the <strong>Loaded</strong> state.</p>
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -9531,7 +9531,7 @@ The cargo must be in the <strong>Loaded</strong> state.</p>
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

28
Documentation/Cargo.CargoGroup.html
View File

@ -1820,20 +1820,6 @@ Controls a network of short range air/missile defense groups.</p>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(CARGO_GROUP).CargoCarrier" ><strong>CARGO_GROUP.CargoCarrier</strong></a>
<p>self.CargoObject:Destroy()</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(CARGO_GROUP).CargoGroup" ><strong>CARGO_GROUP.CargoGroup</strong></a>
@ -3155,20 +3141,6 @@ This works for ground only groups.</p>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(CARGO_GROUP).CargoCarrier" ><strong>CARGO_GROUP.CargoCarrier</strong></a>
<p>self.CargoObject:Destroy()</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(CARGO_GROUP).CargoGroup" ><strong>CARGO_GROUP.CargoGroup</strong></a>

44
Documentation/Cargo.CargoUnit.html
View File

@ -1698,17 +1698,6 @@ Note that ground forces behave in a group, and thus, act in formation, regardles
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(CARGO_UNIT).CargoCarrier" ><strong>CARGO_UNIT.CargoCarrier</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(CARGO_UNIT).CargoInAir" ><strong>CARGO_UNIT.CargoInAir</strong></a>
@ -1727,6 +1716,17 @@ Note that ground forces behave in a group, and thus, act in formation, regardles
<p> Set cargo object.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CARGO_UNIT).RunCount" ><strong>CARGO_UNIT.RunCount</strong></a>
</div>
</div>
@ -2413,17 +2413,6 @@ Note that ground forces behave in a group, and thus, act in formation, regardles
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(CARGO_UNIT).CargoCarrier" ><strong>CARGO_UNIT.CargoCarrier</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(CARGO_UNIT).CargoInAir" ><strong>CARGO_UNIT.CargoInAir</strong></a>
@ -2442,6 +2431,17 @@ Note that ground forces behave in a group, and thus, act in formation, regardles
<p> Set cargo object.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CARGO_UNIT).RunCount" ><strong>CARGO_UNIT.RunCount</strong></a>
</div>
</div>

89
Documentation/Core.Fsm.html
View File

@ -1531,7 +1531,7 @@ FSM hierarchies allow for efficient FSM re-use, <strong>not having to re-invent
<p>The above diagram shows a graphical representation of a FSM implementation for a <strong>Task</strong>, which guides a Human towards a Zone,
orders him to destroy x targets and account the results.
Other examples of ready made FSM could be: </p>
Other examples of ready made FSM could be:</p>
<ul>
<li>route a plane to a zone flown by a human</li>
@ -1556,7 +1556,7 @@ Each of these FSM implementation classes start either with:</p>
<p>Detailed explanations and API specifics are further below clarified and FSM derived class specifics are described in those class documentation sections.</p>
<h2><strong>Dislaimer:</strong></h2>
<h2><strong>Disclaimer:</strong></h2>
<p>The FSM class development is based on a finite state machine implementation made by Conroy Kyle.
The state machine can be found on <a href="https://github.com/kyleconroy/lua-state-machine">github</a>
I've reworked this development (taken the concept), and created a <strong>hierarchical state machine</strong> out of it, embedded within the DCS simulator.
@ -1574,7 +1574,6 @@ Additionally, I've added extendability and created an API that allows seamless F
<hr/>
<h3>Author: <strong>FlightControl</strong></h3>
<h3>Contributions: <strong>funkyfranky</strong></h3>
@ -1617,13 +1616,13 @@ FSM hierarchies allow for efficient FSM re-use, <strong>not having to re-invent
<p>The above diagram shows a graphical representation of a FSM implementation for a <strong>Task</strong>, which guides a Human towards a Zone,
orders him to destroy x targets and account the results.
Other examples of ready made FSM could be: </p>
Other examples of ready made FSM could be:</p>
<ul>
<li>route a plane to a zone flown by a human</li>
<li>detect targets by an AI and report to humans</li>
<li>account for destroyed targets by human players</li>
<li>handle AI infantry to deploy from or embark to a helicopter or airplane or vehicle </li>
<li>handle AI infantry to deploy from or embark to a helicopter or airplane or vehicle</li>
<li>let an AI patrol a zone</li>
</ul>
@ -1660,12 +1659,12 @@ The method can then define its own custom logic to implement the FSM workflow, a
Most of the time, these Event Triggers are used within the Transition Handler methods, so that a workflow is created running through the state machine.</p>
<p>As explained above, a FSM supports <strong>Linear State Transitions</strong> and <strong>Hierarchical State Transitions</strong>, and both can be mixed to make a comprehensive FSM implementation.
The below documentation has a seperate chapter explaining both transition modes, taking into account the <strong>Transition Rules</strong>, <strong>Transition Handlers</strong> and <strong>Event Triggers</strong>.</p>
The below documentation has a separate chapter explaining both transition modes, taking into account the <strong>Transition Rules</strong>, <strong>Transition Handlers</strong> and <strong>Event Triggers</strong>.</p>
<h2>FSM Linear Transitions</h2>
<p>Linear Transitions are Transition Rules allowing an FSM to transition from one or multiple possible <strong>From</strong> state(s) towards a <strong>To</strong> state upon a Triggered <strong>Event</strong>.
The Lineair transition rule evaluation will always be done from the <strong>current state</strong> of the FSM.
The Linear transition rule evaluation will always be done from the <strong>current state</strong> of the FSM.
If no valid Transition Rule can be found in the FSM, the FSM will log an error and stop.</p>
<h3>FSM Transition Rules</h3>
@ -1673,7 +1672,7 @@ If no valid Transition Rule can be found in the FSM, the FSM will log an error a
<p>The FSM has transition rules that it follows and validates, as it walks the process.
These rules define when an FSM can transition from a specific state towards an other specific state upon a triggered event.</p>
<p>The method <a href="##(FSM).AddTransition">FSM.AddTransition</a>() specifies a new possible Transition Rule for the FSM. </p>
<p>The method <a href="##(FSM).AddTransition">FSM.AddTransition</a>() specifies a new possible Transition Rule for the FSM.</p>
<p>The initial state can be defined using the method <a href="##(FSM).SetStartState">FSM.SetStartState</a>(). The default start state of an FSM is "None".</p>
@ -1705,7 +1704,7 @@ These rules define when an FSM can transition from a specific state towards an o
<li>The From state can be a <strong>"*"</strong>, indicating that <strong>the transition rule will always be valid</strong>, regardless of the current state of the FSM.</li>
</ul>
<p>The below code snippet shows how the two last lines can be rewritten and consensed.</p>
<p>The below code snippet shows how the two last lines can be rewritten and condensed.</p>
<pre><code> FsmSwitch:AddTransition( { "On", "Middle" }, "SwitchOff", "Off" )
</code></pre>
@ -1714,8 +1713,8 @@ These rules define when an FSM can transition from a specific state towards an o
<p><img src="..\Presentations\FSM\Dia4.JPG" alt="Transition Handlers"/></p>
<p>An FSM transitions in <strong>4 moments</strong> when an Event is being triggered and processed. <br/>
The mission designer can define for each moment specific logic within methods implementations following a defined API syntax. <br/>
<p>An FSM transitions in <strong>4 moments</strong> when an Event is being triggered and processed.
The mission designer can define for each moment specific logic within methods implementations following a defined API syntax.
These methods define the flow of the FSM process; because in those methods the FSM Internal Events will be triggered.</p>
<ul>
@ -1740,7 +1739,7 @@ These parameters are on the correct order: From, Event, To:</p>
<p><img src="..\Presentations\FSM\Dia5.JPG" alt="Event Triggers"/></p>
<p>The FSM creates for each Event two <strong>Event Trigger methods</strong>. <br/>
<p>The FSM creates for each Event two <strong>Event Trigger methods</strong>.
There are two modes how Events can be triggered, which is <strong>synchronous</strong> and <strong>asynchronous</strong>:</p>
<ul>
@ -1748,7 +1747,7 @@ There are two modes how Events can be triggered, which is <strong>synchronous</s
<li>The method <strong>FSM:<strong>Event( __seconds</strong> )</strong> triggers an Event that will be processed <strong>asynchronously</strong> over time, waiting <strong>x seconds</strong>.</li>
</ul>
<p>The destinction between these 2 Event Trigger methods are important to understand. An asynchronous call will "log" the Event Trigger to be executed at a later time.
<p>The distinction between these 2 Event Trigger methods are important to understand. An asynchronous call will "log" the Event Trigger to be executed at a later time.
Processing will just continue. Synchronous Event Trigger methods are useful to change states of the FSM immediately, but may have a larger processing impact.</p>
<p>The following example provides a little demonstration on the difference between synchronous and asynchronous Event Triggering.</p>
@ -1875,10 +1874,10 @@ And there is no transition handling method defined for that transition, thus, no
This becomes in very useful for mission building, where mission designers build complex processes and workflows,
combining smaller FSMs to one single FSM.</p>
<p>The FSM can embed <strong>Sub-FSMs</strong> that will execute and return <strong>multiple possible Return (End) States</strong>. <br/>
<p>The FSM can embed <strong>Sub-FSMs</strong> that will execute and return <strong>multiple possible Return (End) States</strong>.
Depending upon <strong>which state is returned</strong>, the main FSM can continue the flow <strong>triggering specific events</strong>.</p>
<p>The method <a href="##(FSM).AddProcess">FSM.AddProcess</a>() adds a new Sub-FSM to the FSM. </p>
<p>The method <a href="##(FSM).AddProcess">FSM.AddProcess</a>() adds a new Sub-FSM to the FSM.</p>
<hr/>
@ -5652,7 +5651,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#string
<a id="#(FSM)._StartState" ><strong>FSM._StartState</strong></a>
@ -6083,7 +6082,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -6412,7 +6411,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -6686,7 +6685,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6697,7 +6696,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -6730,7 +6729,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -7000,7 +6999,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -7142,7 +7141,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>
@ -7255,7 +7254,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#string
<a id="#(FSM)._StartState" ><strong>FSM._StartState</strong></a>
@ -11508,7 +11507,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -11837,7 +11836,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -12111,7 +12110,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -12122,7 +12121,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -12155,7 +12154,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -12425,7 +12424,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -12567,7 +12566,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>
@ -17388,7 +17387,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -17717,7 +17716,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -17991,7 +17990,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -18002,7 +18001,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -18035,7 +18034,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -18305,7 +18304,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -18447,7 +18446,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>
@ -22278,7 +22277,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -22607,7 +22606,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -22881,7 +22880,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -22892,7 +22891,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -22925,7 +22924,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -23195,7 +23194,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -23337,7 +23336,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/Core.Goal.html
View File

@ -3387,7 +3387,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -3716,7 +3716,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -3990,7 +3990,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -4001,7 +4001,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -4034,7 +4034,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -4304,7 +4304,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -4446,7 +4446,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

58
Documentation/Core.Menu.html
View File

@ -1511,7 +1511,7 @@ Controls a network of short range air/missile defense groups.</p>
<li>Update menu structures.</li>
<li>Refresh menu structures intelligently, based on a time stamp of updates.
<ul>
<li>Delete obscolete menus.</li>
<li>Delete obsolete menus.</li>
<li>Create new one where required.</li>
<li>Don't touch the existing ones.</li>
</ul></li>
@ -1522,11 +1522,11 @@ Controls a network of short range air/missile defense groups.</p>
</ul>
<p>DCS Menus can be managed using the MENU classes.
The advantage of using MENU classes is that it hides the complexity of dealing with menu management in more advanced scanerios where you need to
The advantage of using MENU classes is that it hides the complexity of dealing with menu management in more advanced scenarios where you need to
set menus and later remove them, and later set them again. You'll find while using use normal DCS scripting functions, that setting and removing
menus is not a easy feat if you have complex menu hierarchies defined.
Using the MOOSE menu classes, the removal and refreshing of menus are nicely being handled within these classes, and becomes much more easy.
On top, MOOSE implements <strong>variable parameter</strong> passing for command menus. </p>
On top, MOOSE implements <strong>variable parameter</strong> passing for command menus.</p>
<p>There are basically two different MENU class types that you need to use:</p>
@ -1547,12 +1547,12 @@ On top, MOOSE implements <strong>variable parameter</strong> passing for command
</ul>
<hr/>
<p>- </p>
<p>-</p>
<h3>Author: <strong>FlightControl</strong></h3>
<h3>Contributions:</h3>
<hr/>
<p> </p>
</div>
<div class="w3-container w3-theme-d2"><h2><strong>Global(s)</strong></h2></div>
@ -1983,7 +1983,7 @@ Using this object reference, you can then remove ALL the menus and submenus unde
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(MENU_BASE).New">MENU_BASE:New(MenuText, ParentMenu)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Consructor</p>
<p>Constructor</p>
</td>
</tr>
<tr class="w3-border">
@ -2636,7 +2636,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(MENU_COALITION).New">MENU_COALITION:New(MenuText, ParentMenu)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Consructor</p>
<p>Constructor</p>
</td>
</tr>
<tr class="w3-border">
@ -3316,7 +3316,7 @@ If the function changes, no new menu needs to be generated if the menu text is t
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(MENU_COALITION_COMMAND).New">MENU_COALITION_COMMAND:New(MenuText, ParentMenu)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Consructor</p>
<p>Constructor</p>
</td>
</tr>
<tr class="w3-border">
@ -3969,7 +3969,7 @@ If the function changes, no new menu needs to be generated if the menu text is t
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(MENU_COMMAND_BASE).New">MENU_COMMAND_BASE:New(MenuText, ParentMenu)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Consructor</p>
<p>Constructor</p>
</td>
</tr>
<tr class="w3-border">
@ -4640,7 +4640,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(MENU_GROUP).New">MENU_GROUP:New(MenuText, ParentMenu)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Consructor</p>
<p>Constructor</p>
</td>
</tr>
<tr class="w3-border">
@ -5338,7 +5338,7 @@ If the function changes, no new menu needs to be generated if the menu text is t
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(MENU_GROUP_COMMAND).New">MENU_GROUP_COMMAND:New(MenuText, ParentMenu)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Consructor</p>
<p>Constructor</p>
</td>
</tr>
<tr class="w3-border">
@ -6048,7 +6048,7 @@ If the function changes, no new menu needs to be generated if the menu text is t
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(MENU_GROUP_COMMAND_DELAYED).New">MENU_GROUP_COMMAND_DELAYED:New(MenuText, ParentMenu)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Consructor</p>
<p>Constructor</p>
</td>
</tr>
<tr class="w3-border">
@ -6731,7 +6731,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(MENU_GROUP_DELAYED).New">MENU_GROUP_DELAYED:New(MenuText, ParentMenu)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Consructor</p>
<p>Constructor</p>
</td>
</tr>
<tr class="w3-border">
@ -7390,7 +7390,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(MENU_MISSION).New">MENU_MISSION:New(MenuText, ParentMenu)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Consructor</p>
<p>Constructor</p>
</td>
</tr>
<tr class="w3-border">
@ -8070,7 +8070,7 @@ If the function changes, no new menu needs to be generated if the menu text is t
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(MENU_MISSION_COMMAND).New">MENU_MISSION_COMMAND:New(MenuText, ParentMenu)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Consructor</p>
<p>Constructor</p>
</td>
</tr>
<tr class="w3-border">
@ -8655,7 +8655,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p>self:F( { RemoveParent } )</p>
<p> self:F( { RemoveParent } )</p>
</div>
@ -8794,7 +8794,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<h2><a id="#(MENU_BASE).New" ><strong>MENU_BASE:New(MenuText, ParentMenu)</strong></a></h2>
</div>
<p>Consructor</p>
<p>Constructor</p>
<div id= "#Functions##New" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -9061,7 +9061,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p>self:F( { RemoveParent } )</p>
<p> self:F( { RemoveParent } )</p>
</div>
@ -12387,7 +12387,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>The parent menu. This parameter can be ignored if you want the menu to be located at the perent menu of DCS world (under F10 other).</p>
<p>The parent menu. This parameter can be ignored if you want the menu to be located at the parent menu of DCS world (under F10 other).</p>
</div>
</div>
@ -12636,7 +12636,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
<h2><a id="#(MENU_COALITION).New" ><strong>MENU_COALITION:New(MenuText, ParentMenu)</strong></a></h2>
</div>
<p>Consructor</p>
<p>Constructor</p>
<div id= "#Functions##New" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -16608,7 +16608,7 @@ If the function changes, no new menu needs to be generated if the menu text is t
<h2><a id="#(MENU_COALITION_COMMAND).New" ><strong>MENU_COALITION_COMMAND:New(MenuText, ParentMenu)</strong></a></h2>
</div>
<p>Consructor</p>
<p>Constructor</p>
<div id= "#Functions##New" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -20408,7 +20408,7 @@ If the function changes, no new menu needs to be generated if the menu text is t
<h2><a id="#(MENU_COMMAND_BASE).New" ><strong>MENU_COMMAND_BASE:New(MenuText, ParentMenu)</strong></a></h2>
</div>
<p>Consructor</p>
<p>Constructor</p>
<div id= "#Functions##New" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -24313,7 +24313,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
<h2><a id="#(MENU_GROUP).New" ><strong>MENU_GROUP:New(MenuText, ParentMenu)</strong></a></h2>
</div>
<p>Consructor</p>
<p>Constructor</p>
<div id= "#Functions##New" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -28414,7 +28414,7 @@ If the function changes, no new menu needs to be generated if the menu text is t
<h2><a id="#(MENU_GROUP_COMMAND).New" ><strong>MENU_GROUP_COMMAND:New(MenuText, ParentMenu)</strong></a></h2>
</div>
<p>Consructor</p>
<p>Constructor</p>
<div id= "#Functions##New" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -32578,7 +32578,7 @@ If the function changes, no new menu needs to be generated if the menu text is t
<h2><a id="#(MENU_GROUP_COMMAND_DELAYED).New" ><strong>MENU_GROUP_COMMAND_DELAYED:New(MenuText, ParentMenu)</strong></a></h2>
</div>
<p>Consructor</p>
<p>Constructor</p>
<div id= "#Functions##New" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -36568,7 +36568,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
<h2><a id="#(MENU_GROUP_DELAYED).New" ><strong>MENU_GROUP_DELAYED:New(MenuText, ParentMenu)</strong></a></h2>
</div>
<p>Consructor</p>
<p>Constructor</p>
<div id= "#Functions##New" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -40167,7 +40167,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
<div class="w3-half">
<p>The parent menu. This parameter can be ignored if you want the menu to be located at the perent menu of DCS world (under F10 other).</p>
<p>The parent menu. This parameter can be ignored if you want the menu to be located at the parent menu of DCS world (under F10 other).</p>
</div>
</div>
@ -40427,7 +40427,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
<h2><a id="#(MENU_MISSION).New" ><strong>MENU_MISSION:New(MenuText, ParentMenu)</strong></a></h2>
</div>
<p>Consructor</p>
<p>Constructor</p>
<div id= "#Functions##New" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -44376,7 +44376,7 @@ If the function changes, no new menu needs to be generated if the menu text is t
<h2><a id="#(MENU_MISSION_COMMAND).New" ><strong>MENU_MISSION_COMMAND:New(MenuText, ParentMenu)</strong></a></h2>
</div>
<p>Consructor</p>
<p>Constructor</p>
<div id= "#Functions##New" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">

138
Documentation/Core.Message.html
View File

@ -1648,25 +1648,25 @@ To send messages, you need to use the To functions.</p>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(MESSAGE).ToCoalition">MESSAGE:ToCoalition(CoalitionSide, Settings)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Sends a MESSAGE to a Coalition. </p>
<p>Sends a MESSAGE to a Coalition.</p>
</td>
</tr>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(MESSAGE).ToCoalitionIf">MESSAGE:ToCoalitionIf(CoalitionSide, Condition)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Sends a MESSAGE to a Coalition if the given Condition is true. </p>
<p>Sends a MESSAGE to a Coalition if the given Condition is true.</p>
</td>
</tr>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(MESSAGE).ToGroup">MESSAGE:ToGroup(Group, Settings)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Sends a MESSAGE to a Group. </p>
<p>Sends a MESSAGE to a Group.</p>
</td>
</tr>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(MESSAGE).ToRed">MESSAGE:ToRed()</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Sends a MESSAGE to the Red Coalition. </p>
<p>Sends a MESSAGE to the Red Coalition.</p>
</td>
</tr>
<tr class="w3-border">
@ -2323,7 +2323,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p>Clears all previous messages from the screen before the new message is displayed.</p>
<p>Not that this must come before all functions starting with ToX(), e.g. ToAll(), ToGroup() etc. </p>
<p>Not that this must come before all functions starting with ToX(), e.g. ToAll(), ToGroup() etc.</p>
<div id= "#Functions##Clear" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -2429,15 +2429,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- Create a series of new Messages.
-- MessageAll is meant to be sent to all players, for 25 seconds, and is classified as "Score".
-- MessageRED is meant to be sent to the RED players only, for 10 seconds, and is classified as "End of Mission", with ID "Win".
-- MessageClient1 is meant to be sent to a Client, for 25 seconds, and is classified as "Score", with ID "Score".
-- MessageClient1 is meant to be sent to a Client, for 25 seconds, and is classified as "Score", with ID "Score".
MessageAll = MESSAGE:New( "To all Players: BLUE has won! Each player of BLUE wins 50 points!", 25, "End of Mission" )
MessageRED = MESSAGE:New( "To the RED Players: You receive a penalty because you've killed one of your own units", 25, "Penalty" )
MessageClient1 = MESSAGE:New( "Congratulations, you've just hit a target", 25, "Score" )
MessageClient2 = MESSAGE:New( "Congratulations, you've just killed a target", 25, "Score")</code></pre>
<pre class="example"><code>
-- Create a series of new Messages.
-- MessageAll is meant to be sent to all players, for 25 seconds, and is classified as "Score".
-- MessageRED is meant to be sent to the RED players only, for 10 seconds, and is classified as "End of Mission", with ID "Win".
-- MessageClient1 is meant to be sent to a Client, for 25 seconds, and is classified as "Score", with ID "Score".
-- MessageClient1 is meant to be sent to a Client, for 25 seconds, and is classified as "Score", with ID "Score".
MessageAll = MESSAGE:New( "To all Players: BLUE has won! Each player of BLUE wins 50 points!", 25, "End of Mission" )
MessageRED = MESSAGE:New( "To the RED Players: You receive a penalty because you've killed one of your own units", 25, "Penalty" )
MessageClient1 = MESSAGE:New( "Congratulations, you've just hit a target", 25, "Score" )
MessageClient2 = MESSAGE:New( "Congratulations, you've just killed a target", 25, "Score")
</code></pre>
</div>
@ -2515,10 +2517,12 @@ The message display times are automatically defined based on the timing settings
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code> MessageAll = MESSAGE:NewType( "To all Players: BLUE has won! Each player of BLUE wins 50 points!", MESSAGE.Type.Information )
<pre class="example"><code>
MessageAll = MESSAGE:NewType( "To all Players: BLUE has won! Each player of BLUE wins 50 points!", MESSAGE.Type.Information )
MessageRED = MESSAGE:NewType( "To the RED Players: You receive a penalty because you've killed one of your own units", MESSAGE.Type.Information )
MessageClient1 = MESSAGE:NewType( "Congratulations, you've just hit a target", MESSAGE.Type.Update )
MessageClient2 = MESSAGE:NewType( "Congratulations, you've just killed a target", MESSAGE.Type.Update )</code></pre>
MessageClient2 = MESSAGE:NewType( "Congratulations, you've just killed a target", MESSAGE.Type.Update )
</code></pre>
</div>
@ -2565,13 +2569,15 @@ The message display times are automatically defined based on the timing settings
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- Send a message created to all players.
MessageAll = MESSAGE:New( "To all Players: BLUE has won! Each player of BLUE wins 50 points!", "End of Mission", 25, "Win" ):ToAll()
or
MESSAGE:New( "To all Players: BLUE has won! Each player of BLUE wins 50 points!", "End of Mission", 25, "Win" ):ToAll()
or
MessageAll = MESSAGE:New( "To all Players: BLUE has won! Each player of BLUE wins 50 points!", "End of Mission", 25, "Win" )
MessageAll:ToAll()</code></pre>
<pre class="example"><code>
-- Send a message created to all players.
MessageAll = MESSAGE:New( "To all Players: BLUE has won! Each player of BLUE wins 50 points!", "End of Mission", 25, "Win" ):ToAll()
or
MESSAGE:New( "To all Players: BLUE has won! Each player of BLUE wins 50 points!", "End of Mission", 25, "Win" ):ToAll()
or
MessageAll = MESSAGE:New( "To all Players: BLUE has won! Each player of BLUE wins 50 points!", "End of Mission", 25, "Win" )
MessageAll:ToAll()
</code></pre>
</div>
@ -2645,13 +2651,15 @@ MessageAll:ToAll()</code></pre>
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- Send a message created with the @{New} method to the BLUE coalition.
MessageBLUE = MESSAGE:New( "To the BLUE Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" ):ToBlue()
or
MESSAGE:New( "To the BLUE Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" ):ToBlue()
or
MessageBLUE = MESSAGE:New( "To the BLUE Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" )
MessageBLUE:ToBlue()</code></pre>
<pre class="example"><code>
-- Send a message created with the @{New} method to the BLUE coalition.
MessageBLUE = MESSAGE:New( "To the BLUE Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" ):ToBlue()
or
MESSAGE:New( "To the BLUE Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" ):ToBlue()
or
MessageBLUE = MESSAGE:New( "To the BLUE Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" )
MessageBLUE:ToBlue()
</code></pre>
</div>
@ -2714,20 +2722,22 @@ MessageBLUE:ToBlue()</code></pre>
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- Send the 2 messages created with the @{New} method to the Client Group.
-- Note that the Message of MessageClient2 is overwriting the Message of MessageClient1.
ClientGroup = Group.getByName( "ClientGroup" )
<pre class="example"><code>
-- Send the 2 messages created with the @{New} method to the Client Group.
-- Note that the Message of MessageClient2 is overwriting the Message of MessageClient1.
ClientGroup = Group.getByName( "ClientGroup" )
MessageClient1 = MESSAGE:New( "Congratulations, you've just hit a target", "Score", 25, "Score" ):ToClient( ClientGroup )
MessageClient2 = MESSAGE:New( "Congratulations, you've just killed a target", "Score", 25, "Score" ):ToClient( ClientGroup )
or
MESSAGE:New( "Congratulations, you've just hit a target", "Score", 25, "Score" ):ToClient( ClientGroup )
MESSAGE:New( "Congratulations, you've just killed a target", "Score", 25, "Score" ):ToClient( ClientGroup )
or
MessageClient1 = MESSAGE:New( "Congratulations, you've just hit a target", "Score", 25, "Score" )
MessageClient2 = MESSAGE:New( "Congratulations, you've just killed a target", "Score", 25, "Score" )
MessageClient1:ToClient( ClientGroup )
MessageClient2:ToClient( ClientGroup )</code></pre>
MessageClient1 = MESSAGE:New( "Congratulations, you've just hit a target", "Score", 25, "Score" ):ToClient( ClientGroup )
MessageClient2 = MESSAGE:New( "Congratulations, you've just killed a target", "Score", 25, "Score" ):ToClient( ClientGroup )
or
MESSAGE:New( "Congratulations, you've just hit a target", "Score", 25, "Score" ):ToClient( ClientGroup )
MESSAGE:New( "Congratulations, you've just killed a target", "Score", 25, "Score" ):ToClient( ClientGroup )
or
MessageClient1 = MESSAGE:New( "Congratulations, you've just hit a target", "Score", 25, "Score" )
MessageClient2 = MESSAGE:New( "Congratulations, you've just killed a target", "Score", 25, "Score" )
MessageClient1:ToClient( ClientGroup )
MessageClient2:ToClient( ClientGroup )
</code></pre>
</div>
@ -2740,7 +2750,7 @@ MessageClient2:ToClient( ClientGroup )</code></pre>
<h2><a id="#(MESSAGE).ToCoalition" ><strong>MESSAGE:ToCoalition(CoalitionSide, Settings)</strong></a></h2>
</div>
<p>Sends a MESSAGE to a Coalition. </p>
<p>Sends a MESSAGE to a Coalition.</p>
<div id= "#Functions##ToCoalition" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -2787,13 +2797,15 @@ MessageClient2:ToClient( ClientGroup )</code></pre>
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- Send a message created with the @{New} method to the RED coalition.
MessageRED = MESSAGE:New( "To the RED Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" ):ToCoalition( coalition.side.RED )
or
MESSAGE:New( "To the RED Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" ):ToCoalition( coalition.side.RED )
or
MessageRED = MESSAGE:New( "To the RED Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" )
MessageRED:ToCoalition( coalition.side.RED )</code></pre>
<pre class="example"><code>
-- Send a message created with the @{New} method to the RED coalition.
MessageRED = MESSAGE:New( "To the RED Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" ):ToCoalition( coalition.side.RED )
or
MESSAGE:New( "To the RED Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" ):ToCoalition( coalition.side.RED )
or
MessageRED = MESSAGE:New( "To the RED Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" )
MessageRED:ToCoalition( coalition.side.RED )
</code></pre>
</div>
@ -2806,7 +2818,7 @@ MessageRED:ToCoalition( coalition.side.RED )</code></pre>
<h2><a id="#(MESSAGE).ToCoalitionIf" ><strong>MESSAGE:ToCoalitionIf(CoalitionSide, Condition)</strong></a></h2>
</div>
<p>Sends a MESSAGE to a Coalition if the given Condition is true. </p>
<p>Sends a MESSAGE to a Coalition if the given Condition is true.</p>
<div id= "#Functions##ToCoalitionIf" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -2836,7 +2848,7 @@ MessageRED:ToCoalition( coalition.side.RED )</code></pre>
</div>
<div class="w3-half">
<p>Sends the message only if the condition is true. </p>
<p>Sends the message only if the condition is true.</p>
</div>
</div>
@ -2862,7 +2874,7 @@ MessageRED:ToCoalition( coalition.side.RED )</code></pre>
<h2><a id="#(MESSAGE).ToGroup" ><strong>MESSAGE:ToGroup(Group, Settings)</strong></a></h2>
</div>
<p>Sends a MESSAGE to a Group. </p>
<p>Sends a MESSAGE to a Group.</p>
<div id= "#Functions##ToGroup" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -2916,7 +2928,7 @@ MessageRED:ToCoalition( coalition.side.RED )</code></pre>
<h2><a id="#(MESSAGE).ToRed" ><strong>MESSAGE:ToRed()</strong></a></h2>
</div>
<p>Sends a MESSAGE to the Red Coalition. </p>
<p>Sends a MESSAGE to the Red Coalition.</p>
<div id= "#Functions##ToRed" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -2936,13 +2948,15 @@ MessageRED:ToCoalition( coalition.side.RED )</code></pre>
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- Send a message created with the @{New} method to the RED coalition.
MessageRED = MESSAGE:New( "To the RED Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" ):ToRed()
or
MESSAGE:New( "To the RED Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" ):ToRed()
or
MessageRED = MESSAGE:New( "To the RED Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" )
MessageRED:ToRed()</code></pre>
<pre class="example"><code>
-- Send a message created with the @{New} method to the RED coalition.
MessageRED = MESSAGE:New( "To the RED Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" ):ToRed()
or
MESSAGE:New( "To the RED Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" ):ToRed()
or
MessageRED = MESSAGE:New( "To the RED Players: You receive a penalty because you've killed one of your own units", "Penalty", 25, "Score" )
MessageRED:ToRed()
</code></pre>
</div>

33
Documentation/Core.Point.html
View File

@ -16164,17 +16164,6 @@ When moose is loading dynamically (for moose class development), tracing is swit
<p>the y coordinate in meters.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(POINT_VEC2).z" ><strong>POINT_VEC2.z</strong></a>
</div>
</div>
@ -16973,17 +16962,6 @@ When moose is loading dynamically (for moose class development), tracing is swit
<p>the y coordinate in meters.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(POINT_VEC2).z" ><strong>POINT_VEC2.z</strong></a>
</div>
</div>
@ -24717,17 +24695,6 @@ Creates a line on the F10 map from one point to another.</p>
<p>the y coordinate in meters.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(POINT_VEC2).z" ><strong>POINT_VEC2.z</strong></a>
</div>
</div>

4
Documentation/Core.Report.html
View File

@ -1602,7 +1602,7 @@ Controls a network of short range air/missile defense groups.</p>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(REPORT).Text">REPORT:Text(Delimiter)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Produces the text of the report, taking into account an optional delimeter, which is \n by default.</p>
<p>Produces the text of the report, taking into account an optional delimiter, which is \n by default.</p>
</td>
</tr>
<tr class="w3-border">
@ -2486,7 +2486,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<h2><a id="#(REPORT).Text" ><strong>REPORT:Text(Delimiter)</strong></a></h2>
</div>
<p>Produces the text of the report, taking into account an optional delimeter, which is \n by default.</p>
<p>Produces the text of the report, taking into account an optional delimiter, which is \n by default.</p>
<div id= "#Functions##Text" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">

22
Documentation/Core.ScheduleDispatcher.html
View File

@ -1516,8 +1516,8 @@ The SCHEDULEDISPATCHER class ensures that:</p>
<li>When a SCHEDULER object <em>is</em> attached to another object, then the SCHEDULER object is <em>not persistent</em> within memory after a garbage collection!</li>
</ul>
<p>The none persistency of SCHEDULERS attached to objects is required to allow SCHEDULER objects to be garbage collectged, when the parent object is also desroyed or nillified and garbage collected.
Even when there are pending timer scheduled functions to be executed for the SCHEDULER object, <br/>
<p>The non-persistency of SCHEDULERS attached to objects is required to allow SCHEDULER objects to be garbage collected when the parent object is destroyed, or set to nil and garbage collected.
Even when there are pending timer scheduled functions to be executed for the SCHEDULER object,
these will not be executed anymore when the SCHEDULER object has been destroyed.</p>
<p>The SCHEDULEDISPATCHER allows multiple scheduled functions to be planned and executed for one SCHEDULER object.
@ -1611,7 +1611,7 @@ The Schedule() method returns the CallID that is the reference ID for each plann
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(SCHEDULEDISPATCHER).PersistentSchedulers">SCHEDULEDISPATCHER.PersistentSchedulers</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Persistant schedulers.</p>
<p>Persistent schedulers.</p>
</td>
</tr>
<tr class="w3-border">
@ -1629,7 +1629,7 @@ The Schedule() method returns the CallID that is the reference ID for each plann
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(SCHEDULEDISPATCHER).ShowTrace">SCHEDULEDISPATCHER:ShowTrace(Scheduler)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Shopw tracing info.</p>
<p>Show tracing info.</p>
</td>
</tr>
<tr class="w3-border">
@ -2212,7 +2212,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(SCHEDULEDISPATCHER.ScheduleData).Repeat">SCHEDULEDISPATCHER.ScheduleData.Repeat</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Repeat time intervall in seconds.</p>
<p>Repeat time interval in seconds.</p>
</td>
</tr>
<tr class="w3-border">
@ -2302,7 +2302,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
#table
<a id="#(SCHEDULEDISPATCHER).PersistentSchedulers" ><strong>SCHEDULEDISPATCHER.PersistentSchedulers</strong></a>
<p>Persistant schedulers.</p>
<p>Persistent schedulers.</p>
</div>
@ -2331,7 +2331,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p>The development of this method was really tidy.
It is constructed as such that a garbage collection is executed on the weak tables, when the Scheduler is nillified.
It is constructed as such that a garbage collection is executed on the weak tables, when the Scheduler is set to nil.
Nothing of this code should be modified without testing it thoroughly.</p>
<div id= "#Functions##AddSchedule" class="w3-show w3-white">
@ -2415,7 +2415,7 @@ Nothing of this code should be modified without testing it thoroughly.</p>
</div>
<div class="w3-half">
<p>Radomization factor [0,1].</p>
<p>Randomization factor [0,1].</p>
</div>
</div>
@ -2622,7 +2622,7 @@ Nothing of this code should be modified without testing it thoroughly.</p>
<h2><a id="#(SCHEDULEDISPATCHER).ShowTrace" ><strong>SCHEDULEDISPATCHER:ShowTrace(Scheduler)</strong></a></h2>
</div>
<p>Shopw tracing info.</p>
<p>Show tracing info.</p>
<div id= "#Functions##ShowTrace" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -2796,7 +2796,7 @@ Nothing of this code should be modified without testing it thoroughly.</p>
#table
<a id="#(SCHEDULEDISPATCHER).PersistentSchedulers" ><strong>SCHEDULEDISPATCHER.PersistentSchedulers</strong></a>
<p>Persistant schedulers.</p>
<p>Persistent schedulers.</p>
</div>
@ -6108,7 +6108,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
#number
<a id="#(SCHEDULEDISPATCHER.ScheduleData).Repeat" ><strong>SCHEDULEDISPATCHER.ScheduleData.Repeat</strong></a>
<p>Repeat time intervall in seconds.</p>
<p>Repeat time interval in seconds.</p>
</div>

26
Documentation/Core.Scheduler.html
View File

@ -1501,10 +1501,10 @@ Controls a network of short range air/missile defense groups.</p>
<ul>
<li>Schedule functions over time,</li>
<li>optionally in an optional specified time interval, </li>
<li>optionally <strong>repeating</strong> with a specified time repeat interval, </li>
<li>optionally <strong>randomizing</strong> with a specified time interval randomization factor, </li>
<li>optionally <strong>stop</strong> the repeating after a specified time interval. </li>
<li>optionally in an optional specified time interval,</li>
<li>optionally <strong>repeating</strong> with a specified time repeat interval,</li>
<li>optionally <strong>randomizing</strong> with a specified time interval randomization factor,</li>
<li>optionally <strong>stop</strong> the repeating after a specified time interval.</li>
</ul>
<hr/>
@ -1595,7 +1595,7 @@ A separate schedule is created by using the MasterObject using the method :Sched
<h3>Construct a SCHEDULER object without a volatile schedule, but volatile to the Object existence...</h3>
<ul>
<li><p><a href="##(SCHEDULER).New">SCHEDULER.New</a>( Object ): Setup a new SCHEDULER object, which is linked to the Object. When the Object is nillified or destroyed, the SCHEDULER object will also be destroyed and stopped after garbage collection.</p>
<li><p><a href="##(SCHEDULER).New">SCHEDULER.New</a>( Object ): Setup a new SCHEDULER object, which is linked to the Object. When the Object is set to nil or destroyed, the SCHEDULER object will also be destroyed and stopped after garbage collection.</p>
<p>ZoneObject = ZONE:New( "ZoneName" )
MasterObject = SCHEDULER:New( ZoneObject )
@ -1658,9 +1658,9 @@ As a result, the MasterObject will cancel the planned schedule.</p>
</ul>
<p>The above example creates a new MasterObject, and does schedule the first schedule as part of the call.
Note that 2 variables are returned here: MasterObject, ScheduleID... <br/>
Later in the logic, the repeating schedule with SchedulerID is stopped. <br/>
A bit later, the repeating schedule with SchedulerId is (re)-started. </p>
Note that 2 variables are returned here: MasterObject, ScheduleID...
Later in the logic, the repeating schedule with SchedulerID is stopped.
A bit later, the repeating schedule with SchedulerId is (re)-started.</p>
<h2>Create a new schedule</h2>
@ -1673,14 +1673,14 @@ This method is used by the :New() constructor when a new schedule is planned.</p
MasterObject = SCHEDULER:New( ZoneObject )
</code></pre>
<p>Several parameters can be specified that influence the behaviour of a Schedule.</p>
<p>Several parameters can be specified that influence the behavior of a Schedule.</p>
<h3>A single schedule, immediately executed</h3>
<pre><code>SchedulerID = MasterObject:Schedule( ZoneObject, ScheduleFunction, {} )
</code></pre>
<p>The above example schedules a new ScheduleFunction call to be executed asynchronously, within milleseconds ...</p>
<p>The above example schedules a new ScheduleFunction call to be executed asynchronously, within milliseconds ...</p>
<h3>A single schedule, planned over time</h3>
@ -1704,7 +1704,7 @@ and repeating 60 every seconds ...</p>
<p>The above example schedules a new ScheduleFunction call to be executed asynchronously, within 10 seconds,
and repeating 60 seconds, with a 50% time interval randomization ...
So the repeating time interval will be randomized using the <strong>0.5</strong>, <br/>
So the repeating time interval will be randomized using the <strong>0.5</strong>,
and will calculate between <strong>60 - ( 60 * 0.5 )</strong> and <strong>60 + ( 60 * 0.5 )</strong> for each repeat,
which is in this example between <strong>30</strong> and <strong>90</strong> seconds.</p>
@ -1715,7 +1715,7 @@ which is in this example between <strong>30</strong> and <strong>90</strong> sec
<p>The above example schedules a new ScheduleFunction call to be executed asynchronously, within 10 seconds,
The schedule will repeat every 60 seconds.
So the repeating time interval will be randomized using the <strong>0.5</strong>, <br/>
So the repeating time interval will be randomized using the <strong>0.5</strong>,
and will calculate between <strong>60 - ( 60 * 0.5 )</strong> and <strong>60 + ( 60 * 0.5 )</strong> for each repeat,
which is in this example between <strong>30</strong> and <strong>90</strong> seconds.
The schedule will stop after <strong>300</strong> seconds.</p>
@ -2684,7 +2684,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Time interval in seconds after which the scheduler will be stoppe.</p>
<p>Time interval in seconds after which the scheduler will be stopped.</p>
</div>
</div>

26
Documentation/Core.Settings.html
View File

@ -1533,7 +1533,7 @@ Controls a network of short range air/missile defense groups.</p>
<tr>
<td class="style="width:40%;"><p><h2>Global <strong>SETTINGS</strong></h2></p></td>
<td class="style="width:60%;">
<p>Takes care of various settings that influence the behaviour of certain functionalities and classes within the MOOSE framework.</p>
<p>Takes care of various settings that influence the behavior of certain functionalities and classes within the MOOSE framework.</p>
</td>
</tr>
</table>
@ -1544,13 +1544,13 @@ Controls a network of short range air/missile defense groups.</p>
<a href="##(SETTINGS)">#SETTINGS</a>
<a id="SETTINGS" ><strong>SETTINGS</strong></a>
<p>Takes care of various settings that influence the behaviour of certain functionalities and classes within the MOOSE framework.</p>
<p>Takes care of various settings that influence the behavior of certain functionalities and classes within the MOOSE framework.</p>
<hr/>
<p>The SETTINGS class takes care of various settings that influence the behaviour of certain functionalities and classes within the MOOSE framework.
<p>The SETTINGS class takes care of various settings that influence the behavior of certain functionalities and classes within the MOOSE framework.
SETTINGS can work on 2 levels:</p>
<ul>
@ -1574,7 +1574,7 @@ These menus can be found <strong>on level F10 under "Settings"</strong>. There a
<p>A menu is created automatically per Command Center that allows to modify the <strong>Default</strong> settings.
So, when joining a CC unit, a menu will be available that allows to change the settings parameters <strong>FOR ALL THE PLAYERS</strong>!
Note that the <strong>Default settings</strong> will only be used when a player has not choosen its own settings.</p>
Note that the <strong>Default settings</strong> will only be used when a player has not chosen its own settings.</p>
<h2>2.2) Player settings menu</h2>
@ -1584,7 +1584,7 @@ Note that when a player has not chosen a specific setting, the <strong>Default s
<h2>2.3) Show or Hide the Player Setting menus</h2>
<p>Of course, it may be requried not to show any setting menus. In this case, a method is available on the <strong>_SETTINGS object</strong>.
<p>Of course, it may be required not to show any setting menus. In this case, a method is available on the <strong>_SETTINGS object</strong>.
Use <a href="##(SETTINGS).SetPlayerMenuOff">SETTINGS.SetPlayerMenuOff</a>() to hide the player menus, and use <a href="##(SETTINGS).SetPlayerMenuOn">SETTINGS.SetPlayerMenuOn</a>() show the player menus.
Note that when this method is used, any player already in a slot will not have its menus visibility changed.
The option will only have effect when a player enters a new slot or changes a slot.</p>
@ -1611,8 +1611,8 @@ See below a comprehensive description of each.</p>
<ul>
<li>A2G BR: <a href="https://en.wikipedia.org/wiki/Bearing_(navigation">Bearing Range</a>.</li>
<li>A2G MGRS: The <a href="https://en.wikipedia.org/wiki/Military_Grid_Reference_System">Military Grid Reference System</a>. The accuracy can also be adapted.</li>
<li>A2G LL DMS: Lattitude Longitude <a href="https://en.wikipedia.org/wiki/Geographic_coordinate_conversion">Degrees Minutes Seconds</a>. The accuracy can also be adapted.</li>
<li>A2G LL DDM: Lattitude Longitude <a href="https://en.wikipedia.org/wiki/Decimal_degrees">Decimal Degrees Minutes</a>. The accuracy can also be adapted.</li>
<li>A2G LL DMS: Latitude Longitude <a href="https://en.wikipedia.org/wiki/Geographic_coordinate_conversion">Degrees Minutes Seconds</a>. The accuracy can also be adapted.</li>
<li>A2G LL DDM: Latitude Longitude <a href="https://en.wikipedia.org/wiki/Decimal_degrees">Decimal Degrees Minutes</a>. The accuracy can also be adapted.</li>
</ul>
<h3>3.1.2) A2G coordinates setting <strong>menu</strong></h3>
@ -1713,7 +1713,7 @@ but there isn't any player context (no player unit to reference from), the MGRS
<p>The settings can be changed by using the <strong>Default settings menu</strong> on the Command Center or the <strong>Player settings menu</strong> on the Player Slot.</p>
<p>Each Message Type has specific timings that will be applied when the message is displayed.
The Settings Menu will provide for each Message Type a selection of proposed durations from which can be choosen.
The Settings Menu will provide for each Message Type a selection of proposed durations from which can be chosen.
So the player can choose its own amount of seconds how long a message should be displayed of a certain type.
Note that <strong>Update</strong> messages can be chosen not to be displayed at all!</p>
@ -1728,7 +1728,7 @@ Note that <strong>Update</strong> messages can be chosen not to be displayed at
<h2>3.5) <strong>Era</strong> of the battle</h2>
<p>The threat level metric is scaled according the era of the battle. A target that is AAA, will pose a much greather threat in WWII than on modern warfare.
<p>The threat level metric is scaled according the era of the battle. A target that is AAA, will pose a much greater threat in WWII than on modern warfare.
Therefore, there are 4 era that are defined within the settings:</p>
<ul>
@ -2714,7 +2714,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#string
<a id="#(SETTINGS).A2ASystem" ><strong>SETTINGS.A2ASystem</strong></a>
@ -2769,7 +2769,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(SETTINGS).Metric" ><strong>SETTINGS.Metric</strong></a>
@ -4808,7 +4808,7 @@ It is advised to use this method at the start of the mission.</p>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#string
<a id="#(SETTINGS).A2ASystem" ><strong>SETTINGS.A2ASystem</strong></a>
@ -4863,7 +4863,7 @@ It is advised to use this method at the start of the mission.</p>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(SETTINGS).Metric" ><strong>SETTINGS.Metric</strong></a>

489
Documentation/Core.Spawn.html
View File

File diff suppressed because it is too large Load Diff

84
Documentation/Core.SpawnStatic.html
View File

@ -1865,24 +1865,6 @@ such as position and heading.</p>
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(SPAWNSTATIC)._SpawnStatic">SPAWNSTATIC:_SpawnStatic(Template, CountryID)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Spawns a new static using a given template.</p>
</td>
</tr>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(SPAWNSTATIC).heliport_callsign_id">SPAWNSTATIC.heliport_callsign_id</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
</td>
</tr>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(SPAWNSTATIC).heliport_frequency">SPAWNSTATIC.heliport_frequency</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
</td>
</tr>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(SPAWNSTATIC).heliport_modulation">SPAWNSTATIC.heliport_modulation</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
</td>
</tr>
</table>
@ -2789,39 +2771,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPAWNSTATIC).heliport_callsign_id" ><strong>SPAWNSTATIC.heliport_callsign_id</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPAWNSTATIC).heliport_frequency" ><strong>SPAWNSTATIC.heliport_frequency</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPAWNSTATIC).heliport_modulation" ><strong>SPAWNSTATIC.heliport_modulation</strong></a>
</div>
</div>
@ -4043,39 +3992,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPAWNSTATIC).heliport_callsign_id" ><strong>SPAWNSTATIC.heliport_callsign_id</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPAWNSTATIC).heliport_frequency" ><strong>SPAWNSTATIC.heliport_frequency</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPAWNSTATIC).heliport_modulation" ><strong>SPAWNSTATIC.heliport_modulation</strong></a>
</div>
</div>

146
Documentation/Core.Spot.html
View File

@ -2669,6 +2669,50 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPOT).ScheduleID" ><strong>SPOT.ScheduleID</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPOT).SpotIR" ><strong>SPOT.SpotIR</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPOT).SpotLaser" ><strong>SPOT.SpotLaser</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPOT).Target" ><strong>SPOT.Target</strong></a>
</div>
</div>
@ -3882,6 +3926,50 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPOT).ScheduleID" ><strong>SPOT.ScheduleID</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPOT).SpotIR" ><strong>SPOT.SpotIR</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPOT).SpotLaser" ><strong>SPOT.SpotLaser</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPOT).Target" ><strong>SPOT.Target</strong></a>
</div>
</div>
@ -4264,7 +4352,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -4593,7 +4681,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -4867,7 +4955,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -4878,7 +4966,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -4911,7 +4999,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -5181,7 +5269,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -5323,7 +5411,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>
@ -5386,6 +5474,50 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPOT).ScheduleID" ><strong>SPOT.ScheduleID</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPOT).SpotIR" ><strong>SPOT.SpotIR</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPOT).SpotLaser" ><strong>SPOT.SpotLaser</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(SPOT).Target" ><strong>SPOT.Target</strong></a>
</div>
</div>

14
Documentation/Core.Zone.html
View File

@ -5769,7 +5769,7 @@ end
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -6098,7 +6098,7 @@ end
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -6372,7 +6372,7 @@ end
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6383,7 +6383,7 @@ end
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -6416,7 +6416,7 @@ end
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6686,7 +6686,7 @@ end
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -6828,7 +6828,7 @@ end
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/Functional.Arty.html
View File

@ -15925,7 +15925,7 @@ The illumination bomb will burn for 300 seconds (5 minutes). Assuming a descent
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -16254,7 +16254,7 @@ The illumination bomb will burn for 300 seconds (5 minutes). Assuming a descent
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -16528,7 +16528,7 @@ The illumination bomb will burn for 300 seconds (5 minutes). Assuming a descent
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -16539,7 +16539,7 @@ The illumination bomb will burn for 300 seconds (5 minutes). Assuming a descent
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -16572,7 +16572,7 @@ The illumination bomb will burn for 300 seconds (5 minutes). Assuming a descent
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -16842,7 +16842,7 @@ The illumination bomb will burn for 300 seconds (5 minutes). Assuming a descent
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -16984,7 +16984,7 @@ The illumination bomb will burn for 300 seconds (5 minutes). Assuming a descent
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

69
Documentation/Functional.Designate.html
View File

@ -3422,17 +3422,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(DESIGNATE).LaseDuration" ><strong>DESIGNATE.LaseDuration</strong></a>
</div>
</div>
@ -6590,17 +6579,6 @@ Designate:SetFlashStatusMenu( false )</code></pre>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(DESIGNATE).LaseDuration" ><strong>DESIGNATE.LaseDuration</strong></a>
</div>
</div>
@ -7400,17 +7378,6 @@ Designate:SetFlashStatusMenu( false )</code></pre>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(DESIGNATE).LaseDuration" ><strong>DESIGNATE.LaseDuration</strong></a>
</div>
</div>
@ -8180,17 +8147,6 @@ Designate:SetFlashStatusMenu( false )</code></pre>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(DESIGNATE).LaseDuration" ><strong>DESIGNATE.LaseDuration</strong></a>
</div>
</div>
@ -8708,7 +8664,7 @@ Designate:SetFlashStatusMenu( false )</code></pre>
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -9037,7 +8993,7 @@ Designate:SetFlashStatusMenu( false )</code></pre>
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -9311,7 +9267,7 @@ Designate:SetFlashStatusMenu( false )</code></pre>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -9322,7 +9278,7 @@ Designate:SetFlashStatusMenu( false )</code></pre>
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -9355,7 +9311,7 @@ Designate:SetFlashStatusMenu( false )</code></pre>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -9625,7 +9581,7 @@ Designate:SetFlashStatusMenu( false )</code></pre>
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -9767,7 +9723,7 @@ Designate:SetFlashStatusMenu( false )</code></pre>
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>
@ -9852,17 +9808,6 @@ Designate:SetFlashStatusMenu( false )</code></pre>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(DESIGNATE).LaseDuration" ><strong>DESIGNATE.LaseDuration</strong></a>
</div>
</div>

89
Documentation/Functional.Detection.html
View File

@ -14264,7 +14264,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -14593,7 +14593,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -14867,7 +14867,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -14878,7 +14878,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -14911,7 +14911,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -15181,7 +15181,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -15323,7 +15323,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>
@ -18915,6 +18915,17 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(DETECTION_BASE).Locking" ><strong>DETECTION_BASE.Locking</strong></a>
</div>
</div>
@ -23606,6 +23617,17 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(DETECTION_BASE).Locking" ><strong>DETECTION_BASE.Locking</strong></a>
</div>
</div>
@ -24032,7 +24054,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -24361,7 +24383,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -24635,7 +24657,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -24646,7 +24668,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -24679,7 +24701,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -24949,7 +24971,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -25091,7 +25113,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>
@ -25352,6 +25374,17 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(DETECTION_BASE).Locking" ><strong>DETECTION_BASE.Locking</strong></a>
</div>
</div>
@ -34253,7 +34286,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -34582,7 +34615,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -34856,7 +34889,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -34867,7 +34900,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -34900,7 +34933,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -35170,7 +35203,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -35312,7 +35345,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>
@ -43831,7 +43864,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -44160,7 +44193,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -44434,7 +44467,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -44445,7 +44478,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -44478,7 +44511,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -44748,7 +44781,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -44890,7 +44923,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/Functional.FOX.html
View File

@ -6627,7 +6627,7 @@ Don't set the explosion power too big or it will harm the aircraft in the vicini
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -6956,7 +6956,7 @@ Don't set the explosion power too big or it will harm the aircraft in the vicini
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -7230,7 +7230,7 @@ Don't set the explosion power too big or it will harm the aircraft in the vicini
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -7241,7 +7241,7 @@ Don't set the explosion power too big or it will harm the aircraft in the vicini
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -7274,7 +7274,7 @@ Don't set the explosion power too big or it will harm the aircraft in the vicini
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -7544,7 +7544,7 @@ Don't set the explosion power too big or it will harm the aircraft in the vicini
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -7686,7 +7686,7 @@ Don't set the explosion power too big or it will harm the aircraft in the vicini
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

6
Documentation/Functional.Mantis.html
View File

@ -3345,9 +3345,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p> switch alarm state RED</p>
</div>
</div>
@ -7010,9 +7007,6 @@ E.g. `mymantis:SetAdvancedMode(true, 90)`</code></pre>
<p> switch alarm state RED</p>
</div>
</div>

14
Documentation/Functional.Range.html
View File

@ -10223,7 +10223,7 @@ If a zone is not explicitly specified, the range zone is determined by its locat
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -10552,7 +10552,7 @@ If a zone is not explicitly specified, the range zone is determined by its locat
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -10826,7 +10826,7 @@ If a zone is not explicitly specified, the range zone is determined by its locat
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -10837,7 +10837,7 @@ If a zone is not explicitly specified, the range zone is determined by its locat
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -10870,7 +10870,7 @@ If a zone is not explicitly specified, the range zone is determined by its locat
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -11140,7 +11140,7 @@ If a zone is not explicitly specified, the range zone is determined by its locat
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -11282,7 +11282,7 @@ If a zone is not explicitly specified, the range zone is determined by its locat
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

372
Documentation/Functional.Rat.html
View File

@ -3358,12 +3358,6 @@ manager:Stop(7200)
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(RAT).termtype">RAT.termtype</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Type of terminal to be used when spawning at an airbase.</p>
</td>
</tr>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(RAT).type">RAT.type</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
</td>
</tr>
<tr class="w3-border">
@ -3491,11 +3485,11 @@ manager:Stop(7200)
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(RAT).InitAIOnOff">RAT:InitAIOnOff(AIOnOff)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Turns the AI On or Off for the <a href="Wrapper.Group.html">Wrapper.Group</a> when spawning.</p>
</td>
</tr>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(RAT).InitAirbase">RAT:InitAirbase(AirbaseName, Takeoff, TerminalTyple, TerminalType)</a></p></td>
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(RAT).InitAirbase">RAT:InitAirbase(AirbaseName, Takeoff, TerminalType)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Set spawns to happen at a particular airbase.</p>
</td>
@ -3503,7 +3497,7 @@ manager:Stop(7200)
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(RAT).InitArray">RAT:InitArray(SpawnAngle, SpawnWidth, SpawnDeltaX, SpawnDeltaY)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Makes the groups visible before start (like a batallion).</p>
<p>Makes the groups visible before start (like a battalion).</p>
</td>
</tr>
<tr class="w3-border">
@ -3603,7 +3597,7 @@ and any spaces before and after the resulting name are removed.</p>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(RAT).InitRadioCommsOnOff">RAT:InitRadioCommsOnOff(switch)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Sets the radio comms on or off.</p>
<p>Sets the radio communication on or off.</p>
</td>
</tr>
<tr class="w3-border">
@ -3663,7 +3657,7 @@ and any spaces before and after the resulting name are removed.</p>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(RAT).InitRepeat">RAT:InitRepeat()</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>For planes and helicopters, when these groups go home and land on their home airbases and farps, they normally would taxi to the parking spot, shut-down their engines and wait forever until the Group is removed by the runtime environment.</p>
<p>For planes and helicopters, when these groups go home and land on their home airbases and FARPs, they normally would taxi to the parking spot, shut-down their engines and wait forever until the Group is removed by the runtime environment.</p>
</td>
</tr>
<tr class="w3-border">
@ -3736,6 +3730,7 @@ and any spaces before and after the resulting name are removed.</p>
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(RAT).ParkAircraft">RAT:ParkAircraft(SpawnAirbase, TerminalType, Parkingdata, SpawnIndex)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Will park a group at an <a href="Wrapper.Airbase.html">Wrapper.Airbase</a>.</p>
</td>
</tr>
<tr class="w3-border">
@ -3795,7 +3790,7 @@ and any spaces before and after the resulting name are removed.</p>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(RAT).SpawnAtParkingSpot">RAT:SpawnAtParkingSpot(Airbase, Spots, Takeoff)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Spawn a group on an <a href="Wrapper.Airbase.html">Wrapper.Airbase</a> at a specific parking spot. </p>
<p>Spawn a group on an <a href="Wrapper.Airbase.html">Wrapper.Airbase</a> at a specific parking spot.</p>
</td>
</tr>
<tr class="w3-border">
@ -4324,18 +4319,6 @@ and any spaces before and after the resulting name are removed.</p>
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(RAT)._TranslateRotate">RAT:_TranslateRotate(SpawnIndex, SpawnRootX, SpawnRootY, SpawnX, SpawnY, SpawnAngle)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
</td>
</tr>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(RAT).communication">RAT.communication</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
</td>
</tr>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(RAT).livery_id">RAT.livery_id</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
</td>
</tr>
<tr class="w3-border">
@ -6711,17 +6694,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p>Type of terminal to be used when spawning at an airbase.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(RAT).type" ><strong>RAT.type</strong></a>
</div>
</div>
@ -14602,17 +14574,6 @@ Initializes the ratcraft array and group menu.</p>
<p>Type of terminal to be used when spawning at an airbase.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(RAT).type" ><strong>RAT.type</strong></a>
</div>
</div>
@ -14749,12 +14710,14 @@ Initializes the ratcraft array and group menu.</p>
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- Find the first alive @{Wrapper.Group} object of the SpawnPlanes SPAWN object @{Wrapper.Group} collection that it has spawned during the mission.
local GroupPlane, Index = SpawnPlanes:GetFirstAliveGroup()
while GroupPlane ~= nil do
<pre class="example"><code>
-- Find the first alive @{Wrapper.Group} object of the SpawnPlanes SPAWN object @{Wrapper.Group} collection that it has spawned during the mission.
local GroupPlane, Index = SpawnPlanes:GetFirstAliveGroup()
while GroupPlane ~= nil do
-- Do actions with the GroupPlane object.
GroupPlane, Index = SpawnPlanes:GetNextAliveGroup( Index )
end</code></pre>
end
</code></pre>
</div>
@ -14843,11 +14806,13 @@ If no index is given, it will return the first group in the list.</p>
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- Find the last alive @{Wrapper.Group} object of the SpawnPlanes SPAWN object @{Wrapper.Group} collection that it has spawned during the mission.
local GroupPlane, Index = SpawnPlanes:GetLastAliveGroup()
if GroupPlane then -- GroupPlane can be nil!!!
<pre class="example"><code>
-- Find the last alive @{Wrapper.Group} object of the SpawnPlanes SPAWN object @{Wrapper.Group} collection that it has spawned during the mission.
local GroupPlane, Index = SpawnPlanes:GetLastAliveGroup()
if GroupPlane then -- GroupPlane can be nil!!!
-- Do actions with the GroupPlane object.
end</code></pre>
end
</code></pre>
</div>
@ -14902,12 +14867,14 @@ end</code></pre>
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- Find the first alive @{Wrapper.Group} object of the SpawnPlanes SPAWN object @{Wrapper.Group} collection that it has spawned during the mission.
local GroupPlane, Index = SpawnPlanes:GetFirstAliveGroup()
while GroupPlane ~= nil do
<pre class="example"><code>
-- Find the first alive @{Wrapper.Group} object of the SpawnPlanes SPAWN object @{Wrapper.Group} collection that it has spawned during the mission.
local GroupPlane, Index = SpawnPlanes:GetFirstAliveGroup()
while GroupPlane ~= nil do
-- Do actions with the GroupPlane object.
GroupPlane, Index = SpawnPlanes:GetNextAliveGroup( Index )
end</code></pre>
end
</code></pre>
</div>
@ -15013,7 +14980,7 @@ end</code></pre>
<h2><a id="#(RAT).InitAIOnOff" ><strong>RAT:InitAIOnOff(AIOnOff)</strong></a></h2>
</div>
<p>Turns the AI On or Off for the <a href="Wrapper.Group.html">Wrapper.Group</a> when spawning.</p>
<div id= "#Functions##InitAIOnOff" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -15025,11 +14992,25 @@ end</code></pre>
<div class="w3-row w3-margin-left w3-border-bottom w3-border-l2">
<div class="w3-half">
<p>
#boolean
<strong><strong>AIOnOff</strong></strong>
</p>
</div>
<div class="w3-half">
<p></p>
<p>A value of true sets the AI On, a value of false sets the AI Off.</p>
</div>
</div>
<h2><strong>Return value:</strong></h2>
<div class="w3-row w3-border-bottom w3-margin-left">
<div class="w3-half">
<p><a href="##(SPAWN)">#SPAWN</a>:</p>
</div>
<div class="w3-half">
<p>The SPAWN object</p>
</div>
</div>
</div>
@ -15040,7 +15021,7 @@ end</code></pre>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<div class="w3-theme-l2">
<h2><a id="#(RAT).InitAirbase" ><strong>RAT:InitAirbase(AirbaseName, Takeoff, TerminalTyple, TerminalType)</strong></a></h2>
<h2><a id="#(RAT).InitAirbase" ><strong>RAT:InitAirbase(AirbaseName, Takeoff, TerminalType)</strong></a></h2>
</div>
<p>Set spawns to happen at a particular airbase.</p>
@ -15085,7 +15066,7 @@ end</code></pre>
<div class="w3-half">
<p>
#number
<strong><strong>TerminalTyple</strong></strong>
<strong><strong>TerminalType</strong></strong>
</p>
</div>
<div class="w3-half">
@ -15094,16 +15075,6 @@ end</code></pre>
</div>
</div>
<div class="w3-row w3-margin-left w3-border-bottom w3-border-l2">
<div class="w3-half">
<p>
<strong><strong>TerminalType</strong></strong>
</p>
</div>
<div class="w3-half">
<p></p>
</div>
</div>
<h2><strong>Return value:</strong></h2>
<div class="w3-row w3-border-bottom w3-margin-left">
<div class="w3-half">
@ -15126,7 +15097,7 @@ end</code></pre>
<h2><a id="#(RAT).InitArray" ><strong>RAT:InitArray(SpawnAngle, SpawnWidth, SpawnDeltaX, SpawnDeltaY)</strong></a></h2>
</div>
<p>Makes the groups visible before start (like a batallion).</p>
<p>Makes the groups visible before start (like a battalion).</p>
<p>The method will take the position of the group as the first position in the array.
@ -15203,12 +15174,12 @@ CAUTION: this directive will NOT work with OnSpawnGroup function.</p>
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- Define an array of Groups.
Spawn_BE_Ground = SPAWN
:New( 'BE Ground' )
<pre class="example"><code>
-- Define an array of Groups.
Spawn_BE_Ground = SPAWN:New( 'BE Ground' )
:InitLimit( 2, 24 )
:InitArray( 90, 10, 100, 50 )
</code></pre>
</code></pre>
</div>
@ -15302,7 +15273,8 @@ When groups are still alive and have become inactive due to damage and are unabl
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>
Spawn_Helicopter:InitCleanUp( 20 ) -- CleanUp the spawning of the helicopters every 20 seconds when they become inactive.</code></pre>
Spawn_Helicopter:InitCleanUp( 20 ) -- CleanUp the spawning of the helicopters every 20 seconds when they become inactive.
</code></pre>
</div>
@ -15339,8 +15311,8 @@ Spawn_Helicopter:InitCleanUp( 20 ) -- CleanUp the spawning of the helicopters e
<p>Coalition of the group as number of enumerator:</p>
<ul>
<li><a href="DCS.html##(coaliton.side).NEUTRAL">DCS#coaliton.side.NEUTRAL</a></li>
<li><a href="DCS.html##(coaliton.side).RED">DCS#coaliton.side.RED</a></li>
<li><a href="DCS.html##(coalition.side).NEUTRAL">DCS#coalition.side.NEUTRAL</a></li>
<li><a href="DCS.html##(coalition.side).RED">DCS#coalition.side.RED</a></li>
<li><a href="DCS.html##(coalition.side).BLUE">DCS#coalition.side.BLUE</a>
</li>
</ul>
@ -15372,7 +15344,7 @@ Spawn_Helicopter:InitCleanUp( 20 ) -- CleanUp the spawning of the helicopters e
<p>Sets the country of the spawn group.</p>
<p>Note that the country determins the coalition of the group depending on which country is defined to be on which side for each specific mission!</p>
<p>Note that the country determines the coalition of the group depending on which country is defined to be on which side for each specific mission!</p>
<div id= "#Functions##InitCountry" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -15394,10 +15366,10 @@ Spawn_Helicopter:InitCleanUp( 20 ) -- CleanUp the spawning of the helicopters e
<ul>
<li><a href="DCS.html##(country.id).RUSSIA">DCS#country.id.RUSSIA</a></li>
<li><a href="DCS.html##(county.id).USA">DCS#county.id.USA</a>
</li>
<li><a href="DCS.html##(county.id).USA">DCS#county.id.USA</a></li>
</ul>
</div>
</div>
<h2><strong>Return value:</strong></h2>
@ -15581,16 +15553,16 @@ Note that InitGroupHeading does <em>not</em> rotate the groups route; only its i
<pre class="example"><code>
mySpawner = SPAWN:New( ... )
-- Spawn the Group with the formation rotated +100 degrees around unit #1, compared to the mission template.
mySpawner:InitGroupHeading( 100 )
-- Spawn the Group with the formation rotated +100 degrees around unit #1, compared to the mission template.
mySpawner:InitGroupHeading( 100 )
Spawn the Group with the formation rotated units between +100 and +150 degrees around unit #1, compared to the mission template, and with individual units varying by +/- 10 degrees from their templated facing.
mySpawner:InitGroupHeading( 100, 150, 10 )
-- Spawn the Group with the formation rotated units between +100 and +150 degrees around unit #1, compared to the mission template, and with individual units varying by +/- 10 degrees from their templated facing.
mySpawner:InitGroupHeading( 100, 150, 10 )
Spawn the Group with the formation rotated -60 degrees around unit #1, compared to the mission template, but with all units facing due north regardless of how they were laid out in the template.
mySpawner:InitGroupHeading(-60):InitHeading(0)
or
mySpawner:InitHeading(0):InitGroupHeading(-60)
-- Spawn the Group with the formation rotated -60 degrees around unit #1, compared to the mission template, but with all units facing due north regardless of how they were laid out in the template.
mySpawner:InitGroupHeading(-60):InitHeading(0)
-- or
mySpawner:InitHeading(0):InitGroupHeading(-60)
</code></pre>
</div>
@ -15622,7 +15594,7 @@ mySpawner:InitHeading(0):InitGroupHeading(-60)
</div>
<div class="w3-half">
<p>Indicates the maximum amount of units in the group. </p>
<p>Indicates the maximum amount of units in the group.</p>
</div>
</div>
@ -15699,13 +15671,13 @@ mySpawner:InitHeading(0):InitGroupHeading(-60)
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>
Spawn = SPAWN:New( ... )
Spawn = SPAWN:New( ... )
-- Spawn the units pointing to 100 degrees.
Spawn:InitHeading( 100 )
-- Spawn the units pointing to 100 degrees.
Spawn:InitHeading( 100 )
-- Spawn the units pointing between 100 and 150 degrees.
Spawn:InitHeading( 100, 150 )
-- Spawn the units pointing between 100 and 150 degrees.
Spawn:InitHeading( 100, 150 )
</code></pre>
</div>
@ -15837,7 +15809,7 @@ When a <a href="##(SPAWN).New">SPAWN.New</a> is executed and the limit of the am
</div>
<div class="w3-half">
<p>The maximum amount of units that can be alive at runtime. </p>
<p>The maximum amount of units that can be alive at runtime.</p>
</div>
</div>
@ -15868,10 +15840,12 @@ This parameter accepts the value 0, which defines that there are no maximum grou
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- NATO helicopters engaging in the battle field.
-- This helicopter group consists of one Unit. So, this group will SPAWN maximum 2 groups simultaneously within the DCSRTE.
-- There will be maximum 24 groups spawned during the whole mission lifetime.
Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):InitLimit( 2, 24 )</code></pre>
<pre class="example"><code>
-- NATO helicopters engaging in the battle field.
-- This helicopter group consists of one Unit. So, this group will SPAWN maximum 2 groups simultaneously within the DCSRTE.
-- There will be maximum 24 groups spawned during the whole mission lifetime.
Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):InitLimit( 2, 24 )
</code></pre>
</div>
@ -15902,7 +15876,7 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):InitLimit( 2, 24 )</
</div>
<div class="w3-half">
<p>Livery name. Note that this is not necessarily the same name as displayed in the mission edior.</p>
<p>Livery name. Note that this is not necessarily the same name as displayed in the mission editor.</p>
</div>
</div>
@ -15975,7 +15949,7 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):InitLimit( 2, 24 )</
<h2><a id="#(RAT).InitRadioCommsOnOff" ><strong>RAT:InitRadioCommsOnOff(switch)</strong></a></h2>
</div>
<p>Sets the radio comms on or off.</p>
<p>Sets the radio communication on or off.</p>
<p>Same as checking/unchecking the COMM box in the mission editor.</p>
@ -15996,7 +15970,7 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):InitLimit( 2, 24 )</
</div>
<div class="w3-half">
<p>If true (or nil), enables the radio comms. If false, disables the radio for the spawned group.</p>
<p>If true (or nil), enables the radio communication. If false, disables the radio for the spawned group.</p>
</div>
</div>
@ -16131,7 +16105,7 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):InitLimit( 2, 24 )</
</div>
<div class="w3-half">
<p>If true, SPAWN will perform the randomization of the <a href="Wrapper.Group.html">Wrapper.Group</a>s position between a given outer and inner radius. </p>
<p>If true, SPAWN will perform the randomization of the <a href="Wrapper.Group.html">Wrapper.Group</a>s position between a given outer and inner radius.</p>
</div>
</div>
@ -16186,7 +16160,7 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):InitLimit( 2, 24 )</
<p>Randomizes the defined route of the SpawnTemplatePrefix group in the ME.</p>
<p>This is very useful to define extra variation of the behaviour of groups.</p>
<p>This is very useful to define extra variation of the behavior of groups.</p>
<div id= "#Functions##InitRandomizeRoute" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -16261,11 +16235,13 @@ This parameter is useful to avoid randomization to end at a waypoint earlier tha
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- NATO helicopters engaging in the battle field.
-- The KA-50 has waypoints Start point ( =0 or SP ), 1, 2, 3, 4, End point (= 5 or DP).
-- Waypoints 2 and 3 will only be randomized. The others will remain on their original position with each new spawn of the helicopter.
-- The randomization of waypoint 2 and 3 will take place within a radius of 2000 meters.
Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):InitRandomizeRoute( 2, 2, 2000 )</code></pre>
<pre class="example"><code>
-- NATO helicopters engaging in the battle field.
-- The KA-50 has waypoints Start point ( =0 or SP ), 1, 2, 3, 4, End point (= 5 or DP).
-- Waypoints 2 and 3 will only be randomized. The others will remain on their original position with each new spawn of the helicopter.
-- The randomization of waypoint 2 and 3 will take place within a radius of 2000 meters.
Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):InitRandomizeRoute( 2, 2, 2000 )
</code></pre>
</div>
@ -16302,7 +16278,7 @@ In other words, this method randomizes between a defined set of groups the templ
</div>
<div class="w3-half">
<p>A table with the names of the groups defined within the mission editor, from which one will be choosen when a new group will be spawned. </p>
<p>A table with the names of the groups defined within the mission editor, from which one will be chosen when a new group will be spawned.</p>
</div>
</div>
@ -16318,17 +16294,18 @@ In other words, this method randomizes between a defined set of groups the templ
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- NATO Tank Platoons invading Gori.
-- Choose between 13 different 'US Tank Platoon' configurations for each new SPAWN the Group to be spawned for the
-- 'US Tank Platoon Left', 'US Tank Platoon Middle' and 'US Tank Platoon Right' SpawnTemplatePrefixes.
-- Each new SPAWN will randomize the route, with a defined time interval of 200 seconds with 40% time variation (randomization) and
-- with a limit set of maximum 12 Units alive simulteneously and 150 Groups to be spawned during the whole mission.
Spawn_US_Platoon = { 'US Tank Platoon 1', 'US Tank Platoon 2', 'US Tank Platoon 3', 'US Tank Platoon 4', 'US Tank Platoon 5',
<pre class="example"><code>
-- NATO Tank Platoons invading Gori.
-- Choose between 13 different 'US Tank Platoon' configurations for each new SPAWN the Group to be spawned for the
-- 'US Tank Platoon Left', 'US Tank Platoon Middle' and 'US Tank Platoon Right' SpawnTemplatePrefixes.
-- Each new SPAWN will randomize the route, with a defined time interval of 200 seconds with 40% time variation (randomization) and
-- with a limit set of maximum 12 Units alive simultaneously and 150 Groups to be spawned during the whole mission.
Spawn_US_Platoon = { 'US Tank Platoon 1', 'US Tank Platoon 2', 'US Tank Platoon 3', 'US Tank Platoon 4', 'US Tank Platoon 5',
'US Tank Platoon 6', 'US Tank Platoon 7', 'US Tank Platoon 8', 'US Tank Platoon 9', 'US Tank Platoon 10',
'US Tank Platoon 11', 'US Tank Platoon 12', 'US Tank Platoon 13' }
Spawn_US_Platoon_Left = SPAWN:New( 'US Tank Platoon Left' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplate( Spawn_US_Platoon ):InitRandomizeRoute( 3, 3, 2000 )
Spawn_US_Platoon_Middle = SPAWN:New( 'US Tank Platoon Middle' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplate( Spawn_US_Platoon ):InitRandomizeRoute( 3, 3, 2000 )
Spawn_US_Platoon_Right = SPAWN:New( 'US Tank Platoon Right' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplate( Spawn_US_Platoon ):InitRandomizeRoute( 3, 3, 2000 )</code></pre>
Spawn_US_Platoon_Left = SPAWN:New( 'US Tank Platoon Left' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplate( Spawn_US_Platoon ):InitRandomizeRoute( 3, 3, 2000 )
Spawn_US_Platoon_Middle = SPAWN:New( 'US Tank Platoon Middle' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplate( Spawn_US_Platoon ):InitRandomizeRoute( 3, 3, 2000 )
Spawn_US_Platoon_Right = SPAWN:New( 'US Tank Platoon Right' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplate( Spawn_US_Platoon ):InitRandomizeRoute( 3, 3, 2000 )</code></pre>
</div>
@ -16380,17 +16357,19 @@ In other words, this method randomizes between a defined set of groups the templ
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- NATO Tank Platoons invading Gori.
<pre class="example"><code>
-- NATO Tank Platoons invading Gori.
-- Choose between different 'US Tank Platoon Templates' configurations to be spawned for the
-- 'US Tank Platoon Left', 'US Tank Platoon Middle' and 'US Tank Platoon Right' SPAWN objects.
-- Choose between different 'US Tank Platoon Templates' configurations to be spawned for the
-- 'US Tank Platoon Left', 'US Tank Platoon Middle' and 'US Tank Platoon Right' SPAWN objects.
-- Each new SPAWN will randomize the route, with a defined time interval of 200 seconds with 40% time variation (randomization) and
-- with a limit set of maximum 12 Units alive simulteneously and 150 Groups to be spawned during the whole mission.
-- Each new SPAWN will randomize the route, with a defined time interval of 200 seconds with 40% time variation (randomization) and
-- with a limit set of maximum 12 Units alive simultaneously and 150 Groups to be spawned during the whole mission.
Spawn_US_Platoon_Left = SPAWN:New( 'US Tank Platoon Left' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplatePrefixes( "US Tank Platoon Templates" ):InitRandomizeRoute( 3, 3, 2000 )
Spawn_US_Platoon_Middle = SPAWN:New( 'US Tank Platoon Middle' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplatePrefixes( "US Tank Platoon Templates" ):InitRandomizeRoute( 3, 3, 2000 )
Spawn_US_Platoon_Right = SPAWN:New( 'US Tank Platoon Right' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplatePrefixes( "US Tank Platoon Templates" ):InitRandomizeRoute( 3, 3, 2000 )</code></pre>
Spawn_US_Platoon_Left = SPAWN:New( 'US Tank Platoon Left' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplatePrefixes( "US Tank Platoon Templates" ):InitRandomizeRoute( 3, 3, 2000 )
Spawn_US_Platoon_Middle = SPAWN:New( 'US Tank Platoon Middle' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplatePrefixes( "US Tank Platoon Templates" ):InitRandomizeRoute( 3, 3, 2000 )
Spawn_US_Platoon_Right = SPAWN:New( 'US Tank Platoon Right' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplatePrefixes( "US Tank Platoon Templates" ):InitRandomizeRoute( 3, 3, 2000 )
</code></pre>
</div>
@ -16426,7 +16405,7 @@ In other words, this method randomizes between a defined set of groups the templ
</div>
<div class="w3-half">
<p>A SET_GROUP object set, that contains the groups that are possible unit representatives of the group to be spawned. </p>
<p>A SET_GROUP object set, that contains the groups that are possible unit representatives of the group to be spawned.</p>
</div>
</div>
@ -16442,20 +16421,22 @@ In other words, this method randomizes between a defined set of groups the templ
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- NATO Tank Platoons invading Gori.
<pre class="example"><code>
-- NATO Tank Platoons invading Gori.
-- Choose between different 'US Tank Platoon Template' configurations to be spawned for the
-- 'US Tank Platoon Left', 'US Tank Platoon Middle' and 'US Tank Platoon Right' SPAWN objects.
-- Choose between different 'US Tank Platoon Template' configurations to be spawned for the
-- 'US Tank Platoon Left', 'US Tank Platoon Middle' and 'US Tank Platoon Right' SPAWN objects.
-- Each new SPAWN will randomize the route, with a defined time interval of 200 seconds with 40% time variation (randomization) and
-- with a limit set of maximum 12 Units alive simulteneously and 150 Groups to be spawned during the whole mission.
-- Each new SPAWN will randomize the route, with a defined time interval of 200 seconds with 40% time variation (randomization) and
-- with a limit set of maximum 12 Units alive simultaneously and 150 Groups to be spawned during the whole mission.
Spawn_US_PlatoonSet = SET_GROUP:New():FilterPrefixes( "US Tank Platoon Templates" ):FilterOnce()
Spawn_US_PlatoonSet = SET_GROUP:New():FilterPrefixes( "US Tank Platoon Templates" ):FilterOnce()
--- Now use the Spawn_US_PlatoonSet to define the templates using InitRandomizeTemplateSet.
Spawn_US_Platoon_Left = SPAWN:New( 'US Tank Platoon Left' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplateSet( Spawn_US_PlatoonSet ):InitRandomizeRoute( 3, 3, 2000 )
Spawn_US_Platoon_Middle = SPAWN:New( 'US Tank Platoon Middle' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplateSet( Spawn_US_PlatoonSet ):InitRandomizeRoute( 3, 3, 2000 )
Spawn_US_Platoon_Right = SPAWN:New( 'US Tank Platoon Right' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplateSet( Spawn_US_PlatoonSet ):InitRandomizeRoute( 3, 3, 2000 )</code></pre>
-- Now use the Spawn_US_PlatoonSet to define the templates using InitRandomizeTemplateSet.
Spawn_US_Platoon_Left = SPAWN:New( 'US Tank Platoon Left' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplateSet( Spawn_US_PlatoonSet ):InitRandomizeRoute( 3, 3, 2000 )
Spawn_US_Platoon_Middle = SPAWN:New( 'US Tank Platoon Middle' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplateSet( Spawn_US_PlatoonSet ):InitRandomizeRoute( 3, 3, 2000 )
Spawn_US_Platoon_Right = SPAWN:New( 'US Tank Platoon Right' ):InitLimit( 12, 150 ):SpawnScheduled( 200, 0.4 ):InitRandomizeTemplateSet( Spawn_US_PlatoonSet ):InitRandomizeRoute( 3, 3, 2000 )
</code></pre>
</div>
@ -16486,7 +16467,7 @@ Spawn_US_Platoon_Right = SPAWN:New( 'US Tank Platoon Right' ):InitLimit( 12, 150
</div>
<div class="w3-half">
<p>If true, SPAWN will perform the randomization of the <a href="UNIT.html">UNIT</a>s position within the group between a given outer and inner radius. </p>
<p>If true, SPAWN will perform the randomization of the <a href="UNIT.html">UNIT</a>s position within the group between a given outer and inner radius.</p>
</div>
</div>
@ -16528,11 +16509,13 @@ Spawn_US_Platoon_Right = SPAWN:New( 'US Tank Platoon Right' ):InitLimit( 12, 150
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- NATO helicopters engaging in the battle field.
-- The KA-50 has waypoints Start point ( =0 or SP ), 1, 2, 3, 4, End point (= 5 or DP).
-- Waypoints 2 and 3 will only be randomized. The others will remain on their original position with each new spawn of the helicopter.
-- The randomization of waypoint 2 and 3 will take place within a radius of 2000 meters.
Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):InitRandomizeRoute( 2, 2, 2000 )</code></pre>
<pre class="example"><code>
-- NATO helicopters engaging in the battle field.
-- The KA-50 has waypoints Start point ( =0 or SP ), 1, 2, 3, 4, End point (= 5 or DP).
-- Waypoints 2 and 3 will only be randomized. The others will remain on their original position with each new spawn of the helicopter.
-- The randomization of waypoint 2 and 3 will take place within a radius of 2000 meters.
Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):InitRandomizeRoute( 2, 2, 2000 )
</code></pre>
</div>
@ -16563,7 +16546,7 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):InitRandomizeRoute(
</div>
<div class="w3-half">
<p>A table with <a href="Zone.html">Zone</a> objects. If this table is given, then each spawn will be executed within the given list of <a href="Zone.html">Zone</a>s objects. </p>
<p>A table with <a href="Zone.html">Zone</a> objects. If this table is given, then each spawn will be executed within the given list of <a href="Zone.html">Zone</a>s objects.</p>
</div>
</div>
@ -16579,7 +16562,8 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):InitRandomizeRoute(
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code> -- Create a zone table of the 2 zones.
<pre class="example"><code>
-- Create a zone table of the 2 zones.
ZoneTable = { ZONE:New( "Zone1" ), ZONE:New( "Zone2" ) }
Spawn_Vehicle_1 = SPAWN:New( "Spawn Vehicle 1" )
@ -16587,7 +16571,7 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):InitRandomizeRoute(
:InitRandomizeRoute( 1, 1, 200 )
:InitRandomizeZones( ZoneTable )
:SpawnScheduled( 5, .5 )
</code></pre>
</code></pre>
</div>
@ -16600,7 +16584,7 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):InitRandomizeRoute(
<h2><a id="#(RAT).InitRepeat" ><strong>RAT:InitRepeat()</strong></a></h2>
</div>
<p>For planes and helicopters, when these groups go home and land on their home airbases and farps, they normally would taxi to the parking spot, shut-down their engines and wait forever until the Group is removed by the runtime environment.</p>
<p>For planes and helicopters, when these groups go home and land on their home airbases and FARPs, they normally would taxi to the parking spot, shut-down their engines and wait forever until the Group is removed by the runtime environment.</p>
<p>This method is used to re-spawn automatically (so no extra call is needed anymore) the same group after it has landed.
@ -16626,15 +16610,15 @@ So ensure that the routes for groups that respawn, always return to the original
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- RU Su-34 - AI Ship Attack
-- Re-SPAWN the Group(s) after each landing and Engine Shut-Down automatically.
SpawnRU_SU34 = SPAWN
:New( 'Su-34' )
<pre class="example"><code>
-- RU Su-34 - AI Ship Attack
-- Re-SPAWN the Group(s) after each landing and Engine Shut-Down automatically.
SpawnRU_SU34 = SPAWN:New( 'Su-34' )
:Schedule( 2, 3, 1800, 0.4 )
:SpawnUncontrolled()
:InitRandomizeRoute( 1, 1, 3000 )
:InitRepeatOnEngineShutDown()
</code></pre>
</code></pre>
</div>
@ -16667,10 +16651,10 @@ SpawnRU_SU34 = SPAWN
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- RU Su-34 - AI Ship Attack
-- Re-SPAWN the Group(s) after each landing and Engine Shut-Down automatically.
SpawnRU_SU34 = SPAWN
:New( 'Su-34' )
<pre class="example"><code>
-- RU Su-34 - AI Ship Attack
-- Re-SPAWN the Group(s) after each landing and Engine Shut-Down automatically.
SpawnRU_SU34 = SPAWN:New( 'Su-34' )
:SpawnUncontrolled()
:InitRandomizeRoute( 1, 1, 3000 )
:InitRepeatOnEngineShutDown()
@ -16707,13 +16691,14 @@ SpawnRU_SU34 = SPAWN
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code>-- RU Su-34 - AI Ship Attack
-- Re-SPAWN the Group(s) after each landing and Engine Shut-Down automatically.
SpawnRU_SU34 = SPAWN
:New( 'Su-34' )
<pre class="example"><code>
-- RU Su-34 - AI Ship Attack
-- Re-SPAWN the Group(s) after each landing and Engine Shut-Down automatically.
SpawnRU_SU34 = SPAWN:New( 'Su-34' )
:InitRandomizeRoute( 1, 1, 3000 )
:InitRepeatOnLanding()
:Spawn() </code></pre>
:Spawn()
</code></pre>
</div>
@ -16934,8 +16919,9 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' )</code></pre></li>
<li><pre class="example"><code>-- Create a new SPAWN object based on a Group Template defined from scratch.
Spawn_BE_KA50 = SPAWN:NewWithAlias( 'BE KA-50@RAMP-Ground Defense', 'Helicopter Attacking a City' )</code></pre></li>
<li><pre class="example"><code>
-- Create a new CSAR_Spawn object based on a normal Group Template to spawn a soldier.
local CSAR_Spawn = SPAWN:NewWithFromTemplate( Template, "CSAR", "Pilot" )</code></pre></li>
-- Create a new CSAR_Spawn object based on a normal Group Template to spawn a soldier.
local CSAR_Spawn = SPAWN:NewWithFromTemplate( Template, "CSAR", "Pilot" )
</code></pre></li>
</ul>
</div>
@ -17073,17 +17059,16 @@ The first parameter of the SpawnFunction is the <a href="Wrapper.Group.html##(GR
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code> -- Declare SpawnObject and call a function when a new Group is spawned.
local SpawnObject = SPAWN
:New( "SpawnObject" )
<pre class="example"><code>
-- Declare SpawnObject and call a function when a new Group is spawned.
local SpawnObject = SPAWN:New( "SpawnObject" )
:InitLimit( 2, 10 )
:OnSpawnGroup(
function( SpawnGroup )
:OnSpawnGroup( function( SpawnGroup )
SpawnGroup:E( "I am spawned" )
end
)
:SpawnScheduled( 300, 0.3 )
</code></pre>
</code></pre>
</div>
@ -17098,6 +17083,7 @@ The first parameter of the SpawnFunction is the <a href="Wrapper.Group.html##(GR
<p>Will park a group at an <a href="Wrapper.Airbase.html">Wrapper.Airbase</a>.</p>
<div id= "#Functions##ParkAircraft" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
<h2><strong>Defined in:</strong></h2>
@ -17188,9 +17174,9 @@ Note that each point in the route assigned to the spawning group is reset to the
You can use the following enumerations to search for the pre-defined airbases on the current known maps of DCS:</p>
<ul>
<li><a href="Wrapper.Airbase.html##(AIRBASE).Caucasus">Wrapper.Airbase#AIRBASE.Caucasus</a>: The airbases on the Caucasus map. </li>
<li><a href="Wrapper.Airbase.html##(AIRBASE).Nevada">Wrapper.Airbase#AIRBASE.Nevada</a>: The airbases on the Nevada (NTTR) map. </li>
<li><a href="Wrapper.Airbase.html##(AIRBASE).Normandy">Wrapper.Airbase#AIRBASE.Normandy</a>: The airbases on the Normandy map. </li>
<li><a href="Wrapper.Airbase.html##(AIRBASE).Caucasus">Wrapper.Airbase#AIRBASE.Caucasus</a>: The airbases on the Caucasus map.</li>
<li><a href="Wrapper.Airbase.html##(AIRBASE).Nevada">Wrapper.Airbase#AIRBASE.Nevada</a>: The airbases on the Nevada (NTTR) map.</li>
<li><a href="Wrapper.Airbase.html##(AIRBASE).Normandy">Wrapper.Airbase#AIRBASE.Normandy</a>: The airbases on the Normandy map.</li>
</ul>
<p>Use the method <a href="Wrapper.Airbase.html##(AIRBASE).FindByName">Wrapper.Airbase#AIRBASE.FindByName</a>() to retrieve the airbase object.
@ -17422,16 +17408,16 @@ You can use the returned group to further define the route to be followed.</p>
You can use the following enumerations to search for the pre-defined airbases on the current known maps of DCS:</p>
<ul>
<li><a href="Wrapper.Airbase.html##(AIRBASE).Caucasus">Wrapper.Airbase#AIRBASE.Caucasus</a>: The airbases on the Caucasus map. </li>
<li><a href="Wrapper.Airbase.html##(AIRBASE).Nevada">Wrapper.Airbase#AIRBASE.Nevada</a>: The airbases on the Nevada (NTTR) map. </li>
<li><a href="Wrapper.Airbase.html##(AIRBASE).Normandy">Wrapper.Airbase#AIRBASE.Normandy</a>: The airbases on the Normandy map. </li>
<li><a href="Wrapper.Airbase.html##(AIRBASE).Caucasus">Wrapper.Airbase#AIRBASE.Caucasus</a>: The airbases on the Caucasus map.</li>
<li><a href="Wrapper.Airbase.html##(AIRBASE).Nevada">Wrapper.Airbase#AIRBASE.Nevada</a>: The airbases on the Nevada (NTTR) map.</li>
<li><a href="Wrapper.Airbase.html##(AIRBASE).Normandy">Wrapper.Airbase#AIRBASE.Normandy</a>: The airbases on the Normandy map.</li>
</ul>
<p>Use the method <a href="Wrapper.Airbase.html##(AIRBASE).FindByName">Wrapper.Airbase#AIRBASE.FindByName</a>() to retrieve the airbase object.
The known AIRBASE objects are automatically imported at mission start by MOOSE.
Therefore, there isn't any New() constructor defined for AIRBASE objects.</p>
<p>Ships and Farps are added within the mission, and are therefore not known.
<p>Ships and FARPs are added within the mission, and are therefore not known.
For these AIRBASE objects, there isn't an <a href="Wrapper.Airbase.html##(AIRBASE)">Wrapper.Airbase#AIRBASE</a> enumeration defined.
You need to provide the <strong>exact name</strong> of the airbase as the parameter to the <a href="Wrapper.Airbase.html##(AIRBASE).FindByName">Wrapper.Airbase#AIRBASE.FindByName</a>() method!</p>
@ -17517,7 +17503,7 @@ You need to provide the <strong>exact name</strong> of the airbase as the parame
</div>
<div class="w3-half">
<p>(optional) Table holding the coordinates and terminal ids for all units of the group. Spawning will be forced to happen at exactily these spots!</p>
<p>(optional) Table holding the coordinates and terminal ids for all units of the group. Spawning will be forced to happen at exactly these spots!</p>
</div>
</div>
@ -17533,7 +17519,8 @@ You need to provide the <strong>exact name</strong> of the airbase as the parame
</div>
</div>
<h2><strong>Usage:</strong></h2>
<pre class="example"><code> Spawn_Plane = SPAWN:New( "Plane" )
<pre class="example"><code>
Spawn_Plane = SPAWN:New( "Plane" )
Spawn_Plane:SpawnAtAirbase( AIRBASE:FindByName( AIRBASE.Caucasus.Krymsk ), SPAWN.Takeoff.Cold )
Spawn_Plane:SpawnAtAirbase( AIRBASE:FindByName( AIRBASE.Caucasus.Krymsk ), SPAWN.Takeoff.Hot )
Spawn_Plane:SpawnAtAirbase( AIRBASE:FindByName( AIRBASE.Caucasus.Krymsk ), SPAWN.Takeoff.Runway )
@ -17563,7 +17550,7 @@ You need to provide the <strong>exact name</strong> of the airbase as the parame
<h2><a id="#(RAT).SpawnAtParkingSpot" ><strong>RAT:SpawnAtParkingSpot(Airbase, Spots, Takeoff)</strong></a></h2>
</div>
<p>Spawn a group on an <a href="Wrapper.Airbase.html">Wrapper.Airbase</a> at a specific parking spot. </p>
<p>Spawn a group on an <a href="Wrapper.Airbase.html">Wrapper.Airbase</a> at a specific parking spot.</p>
<div id= "#Functions##SpawnAtParkingSpot" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">
@ -17875,7 +17862,7 @@ You can use the returned group to further define the route to be followed.</p>
-- Spawn at the zone center position at 2000 meters from the ground!
SpawnAirplanes:SpawnFromPointVec3( SpawnPointVec3 )
</code></pre>
</code></pre>
</div>
@ -18438,7 +18425,7 @@ The <strong>first waypoint</strong> (where the group is spawned) is replaced wit
-- Spawn at the zone center position at the height randomized between 2000 and 4000 meters.
SpawnAirplanes:SpawnInZone( SpawnZone, nil, 2000, 4000 )
</code></pre>
</code></pre>
</div>
@ -18549,7 +18536,7 @@ The <strong>first waypoint</strong> (where the group is spawned) is replaced wit
<div class="w3-half">
<p>The variation to be applied on the defined time interval between each new spawn.
The variation is a number between 0 and 1, representing the %-tage of variation to be applied on the time interval.</p>
The variation is a number between 0 and 1, representing the % of variation to be applied on the time interval.</p>
</div>
</div>
@ -18571,7 +18558,7 @@ The variation is a number between 0 and 1, representing the %-tage of variation
-- This is calculated as follows:
-- Low limit: 600 * ( 1 - 0.5 / 2 ) = 450
-- High limit: 600 * ( 1 + 0.5 / 2 ) = 750
-- Between these two values, a random amount of seconds will be choosen for each new spawn of the helicopters.
-- Between these two values, a random amount of seconds will be chosen for each new spawn of the helicopters.
Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):SpawnScheduled( 600, 0.5 )</code></pre>
</div>
@ -20548,17 +20535,6 @@ This is needed to ensure that Re-SPAWNing only is done for landed AIR Groups.</p
<p>Type of terminal to be used when spawning at an airbase.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(RAT).type" ><strong>RAT.type</strong></a>
</div>
</div>

14
Documentation/Functional.Suppression.html
View File

@ -10775,7 +10775,7 @@ If the group consists of more than one unit, this referrs to the group strength
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -11104,7 +11104,7 @@ If the group consists of more than one unit, this referrs to the group strength
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -11378,7 +11378,7 @@ If the group consists of more than one unit, this referrs to the group strength
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -11389,7 +11389,7 @@ If the group consists of more than one unit, this referrs to the group strength
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -11422,7 +11422,7 @@ If the group consists of more than one unit, this referrs to the group strength
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -11692,7 +11692,7 @@ If the group consists of more than one unit, this referrs to the group strength
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -11834,7 +11834,7 @@ If the group consists of more than one unit, this referrs to the group strength
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/Functional.Warehouse.html
View File

@ -20357,7 +20357,7 @@ this request is used to put the groups back into the warehouse stock.</p>
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -20686,7 +20686,7 @@ this request is used to put the groups back into the warehouse stock.</p>
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -20960,7 +20960,7 @@ this request is used to put the groups back into the warehouse stock.</p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -20971,7 +20971,7 @@ this request is used to put the groups back into the warehouse stock.</p>
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -21004,7 +21004,7 @@ this request is used to put the groups back into the warehouse stock.</p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -21274,7 +21274,7 @@ this request is used to put the groups back into the warehouse stock.</p>
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -21416,7 +21416,7 @@ this request is used to put the groups back into the warehouse stock.</p>
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

33
Documentation/Ops.Airboss.html
View File

@ -29823,7 +29823,7 @@ If removed flight is the section lead, we try to find a new leader.</p>
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -30152,7 +30152,7 @@ If removed flight is the section lead, we try to find a new leader.</p>
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -30426,7 +30426,7 @@ If removed flight is the section lead, we try to find a new leader.</p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -30437,7 +30437,7 @@ If removed flight is the section lead, we try to find a new leader.</p>
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -30470,7 +30470,7 @@ If removed flight is the section lead, we try to find a new leader.</p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -30740,7 +30740,7 @@ If removed flight is the section lead, we try to find a new leader.</p>
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -30882,7 +30882,7 @@ If removed flight is the section lead, we try to find a new leader.</p>
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>
@ -38750,7 +38750,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
<p> Set case of f</p>
<p> Set case to that of lead.</p>
</div>
@ -38809,6 +38809,20 @@ When moose is loading dynamically (for moose class development), tracing is swit
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(AIRBOSS.PlayerData).flag" ><strong>AIRBOSS.PlayerData.flag</strong></a>
<p> Decrease stack/flag. Human player needs to take care himself.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -39008,6 +39022,9 @@ When moose is loading dynamically (for moose class development), tracing is swit
<p> Set time stamp.</p>
</div>
</div>

14
Documentation/Ops.Atis.html
View File

@ -8198,7 +8198,7 @@ Note that the dew point is only an artificial information as DCS does not have a
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -8527,7 +8527,7 @@ Note that the dew point is only an artificial information as DCS does not have a
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -8801,7 +8801,7 @@ Note that the dew point is only an artificial information as DCS does not have a
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -8812,7 +8812,7 @@ Note that the dew point is only an artificial information as DCS does not have a
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -8845,7 +8845,7 @@ Note that the dew point is only an artificial information as DCS does not have a
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -9115,7 +9115,7 @@ Note that the dew point is only an artificial information as DCS does not have a
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -9257,7 +9257,7 @@ Note that the dew point is only an artificial information as DCS does not have a
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

149
Documentation/Ops.CSAR.html
View File

@ -3540,7 +3540,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CSAR).FreeVHFFrequencies" ><strong>CSAR.FreeVHFFrequencies</strong></a>
@ -3629,14 +3629,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CSAR).allheligroupset" ><strong>CSAR.allheligroupset</strong></a>
<p> GROUP_SET of all helis</p>
</div>
</div>
@ -3842,14 +3839,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CSAR).csarUnits" ><strong>CSAR.csarUnits</strong></a>
<p> table of CSAR unit names</p>
</div>
</div>
@ -3870,14 +3864,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CSAR).downedPilots" ><strong>CSAR.downedPilots</strong></a>
<p> Replacement woundedGroups</p>
</div>
</div>
@ -4184,20 +4175,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CSAR).rescuedpilots" ><strong>CSAR.rescuedpilots</strong></a>
<p> counter for saved pilots</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -4223,20 +4200,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CSAR).rescues" ><strong>CSAR.rescues</strong></a>
<p> counter for successful rescue landings at FARP/AFB/MASH</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -8332,7 +8295,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CSAR).FreeVHFFrequencies" ><strong>CSAR.FreeVHFFrequencies</strong></a>
@ -8421,14 +8384,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CSAR).allheligroupset" ><strong>CSAR.allheligroupset</strong></a>
<p> GROUP_SET of all helis</p>
</div>
</div>
@ -8634,14 +8594,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CSAR).csarUnits" ><strong>CSAR.csarUnits</strong></a>
<p> table of CSAR unit names</p>
</div>
</div>
@ -8662,14 +8619,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CSAR).downedPilots" ><strong>CSAR.downedPilots</strong></a>
<p> Replacement woundedGroups</p>
</div>
</div>
@ -8976,20 +8930,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CSAR).rescuedpilots" ><strong>CSAR.rescuedpilots</strong></a>
<p> counter for saved pilots</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -9015,20 +8955,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CSAR).rescues" ><strong>CSAR.rescues</strong></a>
<p> counter for successful rescue landings at FARP/AFB/MASH</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -9512,7 +9438,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -9841,7 +9767,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -10115,7 +10041,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -10126,7 +10052,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -10159,7 +10085,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -10429,7 +10355,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -10571,7 +10497,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>
@ -10643,7 +10569,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CSAR).FreeVHFFrequencies" ><strong>CSAR.FreeVHFFrequencies</strong></a>
@ -10732,14 +10658,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CSAR).allheligroupset" ><strong>CSAR.allheligroupset</strong></a>
<p> GROUP_SET of all helis</p>
</div>
</div>
@ -10945,14 +10868,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CSAR).csarUnits" ><strong>CSAR.csarUnits</strong></a>
<p> table of CSAR unit names</p>
</div>
</div>
@ -10973,14 +10893,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CSAR).downedPilots" ><strong>CSAR.downedPilots</strong></a>
<p> Replacement woundedGroups</p>
</div>
</div>
@ -11287,20 +11204,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CSAR).rescuedpilots" ><strong>CSAR.rescuedpilots</strong></a>
<p> counter for saved pilots</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -11326,20 +11229,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CSAR).rescues" ><strong>CSAR.rescues</strong></a>
<p> counter for successful rescue landings at FARP/AFB/MASH</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">

238
Documentation/Ops.CTLD.html
View File

@ -5530,6 +5530,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div class="fields w3-container w3-theme-l2">
<h2>Field(s)</h2>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CTLD).CargoCounter" ><strong>CTLD.CargoCounter</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -5597,6 +5608,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p>Name of the class.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CTLD).CrateCounter" ><strong>CTLD.CrateCounter</strong></a>
</div>
</div>
@ -5628,7 +5650,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).CtldUnits" ><strong>CTLD.CtldUnits</strong></a>
@ -5650,7 +5672,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).DroppedTroops" ><strong>CTLD.DroppedTroops</strong></a>
@ -5675,11 +5697,28 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CTLD).Engineers" ><strong>CTLD.Engineers</strong></a>
<p>use as counter</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).EngineersInField" ><strong>CTLD.EngineersInField</strong></a>
<p>holds #CTLD_ENGINEERING objects</p>
</div>
</div>
@ -5711,7 +5750,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).FreeFMFrequencies" ><strong>CTLD.FreeFMFrequencies</strong></a>
@ -5722,7 +5761,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).FreeUHFFrequencies" ><strong>CTLD.FreeUHFFrequencies</strong></a>
@ -5733,11 +5772,14 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).FreeVHFFrequencies" ><strong>CTLD.FreeVHFFrequencies</strong></a>
<p> Beacons</p>
</div>
</div>
@ -5863,11 +5905,14 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).PilotGroups" ><strong>CTLD.PilotGroups</strong></a>
<p> tables</p>
</div>
</div>
@ -5951,6 +5996,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CTLD).TroopCounter" ><strong>CTLD.TroopCounter</strong></a>
</div>
</div>
@ -6275,6 +6331,9 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p> time to repair a unit/group</p>
</div>
</div>
@ -12648,6 +12707,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div class="fields w3-container w3-theme-l2">
<h2>Field(s)</h2>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CTLD).CargoCounter" ><strong>CTLD.CargoCounter</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -12715,6 +12785,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p>Name of the class.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CTLD).CrateCounter" ><strong>CTLD.CrateCounter</strong></a>
</div>
</div>
@ -12746,7 +12827,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).CtldUnits" ><strong>CTLD.CtldUnits</strong></a>
@ -12768,7 +12849,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).DroppedTroops" ><strong>CTLD.DroppedTroops</strong></a>
@ -12793,11 +12874,28 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CTLD).Engineers" ><strong>CTLD.Engineers</strong></a>
<p>use as counter</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).EngineersInField" ><strong>CTLD.EngineersInField</strong></a>
<p>holds #CTLD_ENGINEERING objects</p>
</div>
</div>
@ -12829,7 +12927,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).FreeFMFrequencies" ><strong>CTLD.FreeFMFrequencies</strong></a>
@ -12840,7 +12938,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).FreeUHFFrequencies" ><strong>CTLD.FreeUHFFrequencies</strong></a>
@ -12851,11 +12949,14 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).FreeVHFFrequencies" ><strong>CTLD.FreeVHFFrequencies</strong></a>
<p> Beacons</p>
</div>
</div>
@ -12981,11 +13082,14 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).PilotGroups" ><strong>CTLD.PilotGroups</strong></a>
<p> tables</p>
</div>
</div>
@ -13069,6 +13173,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CTLD).TroopCounter" ><strong>CTLD.TroopCounter</strong></a>
</div>
</div>
@ -13393,6 +13508,9 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p> time to repair a unit/group</p>
</div>
</div>
@ -13858,7 +13976,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -14187,7 +14305,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -14461,7 +14579,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -14472,7 +14590,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -14505,7 +14623,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -14775,7 +14893,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -14917,7 +15035,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>
@ -14938,6 +15056,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div class="fields w3-container w3-theme-l2">
<h2>Field(s)</h2>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CTLD).CargoCounter" ><strong>CTLD.CargoCounter</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -15005,6 +15134,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p>Name of the class.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CTLD).CrateCounter" ><strong>CTLD.CrateCounter</strong></a>
</div>
</div>
@ -15036,7 +15176,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).CtldUnits" ><strong>CTLD.CtldUnits</strong></a>
@ -15058,7 +15198,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).DroppedTroops" ><strong>CTLD.DroppedTroops</strong></a>
@ -15083,11 +15223,28 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CTLD).Engineers" ><strong>CTLD.Engineers</strong></a>
<p>use as counter</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).EngineersInField" ><strong>CTLD.EngineersInField</strong></a>
<p>holds #CTLD_ENGINEERING objects</p>
</div>
</div>
@ -15119,7 +15276,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).FreeFMFrequencies" ><strong>CTLD.FreeFMFrequencies</strong></a>
@ -15130,7 +15287,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).FreeUHFFrequencies" ><strong>CTLD.FreeUHFFrequencies</strong></a>
@ -15141,11 +15298,14 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).FreeVHFFrequencies" ><strong>CTLD.FreeVHFFrequencies</strong></a>
<p> Beacons</p>
</div>
</div>
@ -15271,11 +15431,14 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(CTLD).PilotGroups" ><strong>CTLD.PilotGroups</strong></a>
<p> tables</p>
</div>
</div>
@ -15359,6 +15522,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CTLD).TroopCounter" ><strong>CTLD.TroopCounter</strong></a>
</div>
</div>
@ -15683,6 +15857,9 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p> time to repair a unit/group</p>
</div>
</div>
@ -19476,17 +19653,6 @@ When moose is loading dynamically (for moose class development), tracing is swit
<p>Can transport crate.</p>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(CTLD.UnitCapabilities).length" ><strong>CTLD.UnitCapabilities.length</strong></a>
</div>
</div>

14
Documentation/Ops.RecoveryTanker.html
View File

@ -7618,7 +7618,7 @@ The group name is the one specified in the <a href="##(RECOVERYTANKER).New">RECO
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -7947,7 +7947,7 @@ The group name is the one specified in the <a href="##(RECOVERYTANKER).New">RECO
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -8221,7 +8221,7 @@ The group name is the one specified in the <a href="##(RECOVERYTANKER).New">RECO
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -8232,7 +8232,7 @@ The group name is the one specified in the <a href="##(RECOVERYTANKER).New">RECO
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -8265,7 +8265,7 @@ The group name is the one specified in the <a href="##(RECOVERYTANKER).New">RECO
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -8535,7 +8535,7 @@ The group name is the one specified in the <a href="##(RECOVERYTANKER).New">RECO
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -8677,7 +8677,7 @@ The group name is the one specified in the <a href="##(RECOVERYTANKER).New">RECO
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/Ops.RescueHelo.html
View File

@ -6746,7 +6746,7 @@ The group name is the one specified in the <a href="##(RESCUEHELO).New">RESCUEHE
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -7075,7 +7075,7 @@ The group name is the one specified in the <a href="##(RESCUEHELO).New">RESCUEHE
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -7349,7 +7349,7 @@ The group name is the one specified in the <a href="##(RESCUEHELO).New">RESCUEHE
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -7360,7 +7360,7 @@ The group name is the one specified in the <a href="##(RESCUEHELO).New">RESCUEHE
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -7393,7 +7393,7 @@ The group name is the one specified in the <a href="##(RESCUEHELO).New">RESCUEHE
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -7663,7 +7663,7 @@ The group name is the one specified in the <a href="##(RESCUEHELO).New">RESCUEHE
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -7805,7 +7805,7 @@ The group name is the one specified in the <a href="##(RESCUEHELO).New">RESCUEHE
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/Tasking.DetectionManager.html
View File

@ -4247,7 +4247,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -4576,7 +4576,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -4850,7 +4850,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -4861,7 +4861,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -4894,7 +4894,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -5164,7 +5164,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -5306,7 +5306,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/Tasking.Mission.html
View File

@ -6869,7 +6869,7 @@ Each Task can be set a certain Goals. The Mission will not be completed until al
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -7198,7 +7198,7 @@ Each Task can be set a certain Goals. The Mission will not be completed until al
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -7472,7 +7472,7 @@ Each Task can be set a certain Goals. The Mission will not be completed until al
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -7483,7 +7483,7 @@ Each Task can be set a certain Goals. The Mission will not be completed until al
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -7516,7 +7516,7 @@ Each Task can be set a certain Goals. The Mission will not be completed until al
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -7786,7 +7786,7 @@ Each Task can be set a certain Goals. The Mission will not be completed until al
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -7928,7 +7928,7 @@ Each Task can be set a certain Goals. The Mission will not be completed until al
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/Tasking.Task_A2A_Dispatcher.html
View File

@ -5101,7 +5101,7 @@ If too large, any airborne cap may not be able to reach the detected target area
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -5430,7 +5430,7 @@ If too large, any airborne cap may not be able to reach the detected target area
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -5704,7 +5704,7 @@ If too large, any airborne cap may not be able to reach the detected target area
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -5715,7 +5715,7 @@ If too large, any airborne cap may not be able to reach the detected target area
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -5748,7 +5748,7 @@ If too large, any airborne cap may not be able to reach the detected target area
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6018,7 +6018,7 @@ If too large, any airborne cap may not be able to reach the detected target area
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -6160,7 +6160,7 @@ If too large, any airborne cap may not be able to reach the detected target area
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/Tasking.Task_A2G_Dispatcher.html
View File

@ -5245,7 +5245,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -5574,7 +5574,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -5848,7 +5848,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -5859,7 +5859,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -5892,7 +5892,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6162,7 +6162,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -6304,7 +6304,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

8
Documentation/Tasking.Task_Cargo.html
View File

@ -3113,7 +3113,7 @@ based on the tasking capabilities defined in <a href="Tasking.Task.html##(TASK)"
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a href="Cargo.Cargo.html##(CARGO)">Cargo.Cargo#CARGO</a>
<a id="#(FSM_PROCESS).Cargo" ><strong>FSM_PROCESS.Cargo</strong></a>
@ -3150,7 +3150,7 @@ based on the tasking capabilities defined in <a href="Tasking.Task.html##(TASK)"
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(TASK_CARGO).CargoLimit" ><strong>TASK_CARGO.CargoLimit</strong></a>
@ -4572,7 +4572,7 @@ based on the tasking capabilities defined in <a href="Tasking.Task.html##(TASK)"
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(TASK_CARGO).CargoLimit" ><strong>TASK_CARGO.CargoLimit</strong></a>
@ -9104,7 +9104,7 @@ If the Unit is part of the Task, true is returned.</p>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#number
<a id="#(TASK_CARGO).CargoLimit" ><strong>TASK_CARGO.CargoLimit</strong></a>

198
Documentation/Tasking.Task_Cargo_Dispatcher.html
View File

@ -3086,6 +3086,50 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div class="fields w3-container w3-theme-l2">
<h2>Field(s)</h2>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(TASK_CARGO_DISPATCHER).CSARBriefing" ><strong>TASK_CARGO_DISPATCHER.CSARBriefing</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(TASK_CARGO_DISPATCHER).CSARDeployZones" ><strong>TASK_CARGO_DISPATCHER.CSARDeployZones</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(TASK_CARGO_DISPATCHER).CSARTaskName" ><strong>TASK_CARGO_DISPATCHER.CSARTaskName</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(TASK_CARGO_DISPATCHER).CSARTasks" ><strong>TASK_CARGO_DISPATCHER.CSARTasks</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -3101,7 +3145,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(TASK_CARGO_DISPATCHER).DefaultDeployZones" ><strong>TASK_CARGO_DISPATCHER.DefaultDeployZones</strong></a>
@ -4165,6 +4209,50 @@ This method can only be used once!</p>
<div class="fields w3-container w3-theme-l2">
<h2>Field(s)</h2>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(TASK_CARGO_DISPATCHER).CSARBriefing" ><strong>TASK_CARGO_DISPATCHER.CSARBriefing</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(TASK_CARGO_DISPATCHER).CSARDeployZones" ><strong>TASK_CARGO_DISPATCHER.CSARDeployZones</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(TASK_CARGO_DISPATCHER).CSARTaskName" ><strong>TASK_CARGO_DISPATCHER.CSARTaskName</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(TASK_CARGO_DISPATCHER).CSARTasks" ><strong>TASK_CARGO_DISPATCHER.CSARTasks</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -4180,7 +4268,7 @@ This method can only be used once!</p>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(TASK_CARGO_DISPATCHER).DefaultDeployZones" ><strong>TASK_CARGO_DISPATCHER.DefaultDeployZones</strong></a>
@ -5023,6 +5111,50 @@ This method can only be used once!</p>
<div class="fields w3-container w3-theme-l2">
<h2>Field(s)</h2>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(TASK_CARGO_DISPATCHER).CSARBriefing" ><strong>TASK_CARGO_DISPATCHER.CSARBriefing</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(TASK_CARGO_DISPATCHER).CSARDeployZones" ><strong>TASK_CARGO_DISPATCHER.CSARDeployZones</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(TASK_CARGO_DISPATCHER).CSARTaskName" ><strong>TASK_CARGO_DISPATCHER.CSARTaskName</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(TASK_CARGO_DISPATCHER).CSARTasks" ><strong>TASK_CARGO_DISPATCHER.CSARTasks</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -5038,7 +5170,7 @@ This method can only be used once!</p>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(TASK_CARGO_DISPATCHER).DefaultDeployZones" ><strong>TASK_CARGO_DISPATCHER.DefaultDeployZones</strong></a>
@ -5436,7 +5568,7 @@ This method can only be used once!</p>
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -5765,7 +5897,7 @@ This method can only be used once!</p>
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -6039,7 +6171,7 @@ This method can only be used once!</p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6050,7 +6182,7 @@ This method can only be used once!</p>
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -6083,7 +6215,7 @@ This method can only be used once!</p>
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6353,7 +6485,7 @@ This method can only be used once!</p>
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -6495,7 +6627,7 @@ This method can only be used once!</p>
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>
@ -6516,6 +6648,50 @@ This method can only be used once!</p>
<div class="fields w3-container w3-theme-l2">
<h2>Field(s)</h2>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(TASK_CARGO_DISPATCHER).CSARBriefing" ><strong>TASK_CARGO_DISPATCHER.CSARBriefing</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(TASK_CARGO_DISPATCHER).CSARDeployZones" ><strong>TASK_CARGO_DISPATCHER.CSARDeployZones</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(TASK_CARGO_DISPATCHER).CSARTaskName" ><strong>TASK_CARGO_DISPATCHER.CSARTaskName</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(TASK_CARGO_DISPATCHER).CSARTasks" ><strong>TASK_CARGO_DISPATCHER.CSARTasks</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
@ -6531,7 +6707,7 @@ This method can only be used once!</p>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#table
<a id="#(TASK_CARGO_DISPATCHER).DefaultDeployZones" ><strong>TASK_CARGO_DISPATCHER.DefaultDeployZones</strong></a>

14
Documentation/Tasking.Task_Manager.html
View File

@ -3750,7 +3750,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -4079,7 +4079,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -4353,7 +4353,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -4364,7 +4364,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -4397,7 +4397,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -4667,7 +4667,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -4809,7 +4809,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

14
Documentation/Tasking.Task_Zone_Capture_Dispatcher.html
View File

@ -4458,7 +4458,7 @@ The TaskPrefix will be appended with a . + a number of 3 digits, if the TaskPref
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -4787,7 +4787,7 @@ The TaskPrefix will be appended with a . + a number of 3 digits, if the TaskPref
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -5061,7 +5061,7 @@ The TaskPrefix will be appended with a . + a number of 3 digits, if the TaskPref
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -5072,7 +5072,7 @@ The TaskPrefix will be appended with a . + a number of 3 digits, if the TaskPref
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -5105,7 +5105,7 @@ The TaskPrefix will be appended with a . + a number of 3 digits, if the TaskPref
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -5375,7 +5375,7 @@ The TaskPrefix will be appended with a . + a number of 3 digits, if the TaskPref
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -5517,7 +5517,7 @@ The TaskPrefix will be appended with a . + a number of 3 digits, if the TaskPref
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>

78
Documentation/Wrapper.Group.html
View File

@ -4751,7 +4751,18 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(GROUP).InitRespawnRandomizePositionZone" ><strong>GROUP.InitRespawnRandomizePositionZone</strong></a>
<a id="#(GROUP).InitRespawnRandomizePositionInner" ><strong>GROUP.InitRespawnRandomizePositionInner</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(GROUP).InitRespawnRandomizePositionOuter" ><strong>GROUP.InitRespawnRandomizePositionOuter</strong></a>
@ -8858,7 +8869,18 @@ So each unit of the group is respawned at exactly the same parking spot as it cu
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(GROUP).InitRespawnRandomizePositionZone" ><strong>GROUP.InitRespawnRandomizePositionZone</strong></a>
<a id="#(GROUP).InitRespawnRandomizePositionInner" ><strong>GROUP.InitRespawnRandomizePositionInner</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(GROUP).InitRespawnRandomizePositionOuter" ><strong>GROUP.InitRespawnRandomizePositionOuter</strong></a>
@ -17399,7 +17421,18 @@ Note that when the WayPoint parameter is used, the new start mission waypoint of
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(GROUP).InitRespawnRandomizePositionZone" ><strong>GROUP.InitRespawnRandomizePositionZone</strong></a>
<a id="#(GROUP).InitRespawnRandomizePositionInner" ><strong>GROUP.InitRespawnRandomizePositionInner</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(GROUP).InitRespawnRandomizePositionOuter" ><strong>GROUP.InitRespawnRandomizePositionOuter</strong></a>
@ -21038,7 +21071,18 @@ Coordinates are dependent on the position of the maps origin.</p>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(GROUP).InitRespawnRandomizePositionZone" ><strong>GROUP.InitRespawnRandomizePositionZone</strong></a>
<a id="#(GROUP).InitRespawnRandomizePositionInner" ><strong>GROUP.InitRespawnRandomizePositionInner</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(GROUP).InitRespawnRandomizePositionOuter" ><strong>GROUP.InitRespawnRandomizePositionOuter</strong></a>
@ -21692,7 +21736,18 @@ If the Identifiable is alive, true is returned. </p>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(GROUP).InitRespawnRandomizePositionZone" ><strong>GROUP.InitRespawnRandomizePositionZone</strong></a>
<a id="#(GROUP).InitRespawnRandomizePositionInner" ><strong>GROUP.InitRespawnRandomizePositionInner</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(GROUP).InitRespawnRandomizePositionOuter" ><strong>GROUP.InitRespawnRandomizePositionOuter</strong></a>
@ -21952,7 +22007,18 @@ If the Identifiable is alive, true is returned. </p>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(GROUP).InitRespawnRandomizePositionZone" ><strong>GROUP.InitRespawnRandomizePositionZone</strong></a>
<a id="#(GROUP).InitRespawnRandomizePositionInner" ><strong>GROUP.InitRespawnRandomizePositionInner</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
<a id="#(GROUP).InitRespawnRandomizePositionOuter" ><strong>GROUP.InitRespawnRandomizePositionOuter</strong></a>

80
Documentation/Wrapper.Marker.html
View File

@ -2986,6 +2986,28 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(MARKER).tocoaliton" ><strong>MARKER.tocoaliton</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(MARKER).togroup" ><strong>MARKER.togroup</strong></a>
</div>
</div>
@ -5070,6 +5092,28 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(MARKER).tocoaliton" ><strong>MARKER.tocoaliton</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(MARKER).togroup" ><strong>MARKER.togroup</strong></a>
</div>
</div>
@ -5452,7 +5496,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Current FSM state. </p>
<p>Current FSM state.</p>
</div>
</div>
@ -5781,7 +5825,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Table of call backs. </p>
<p>Table of call backs.</p>
</div>
</div>
@ -6055,7 +6099,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6066,7 +6110,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Function. </p>
<p>Function.</p>
</div>
</div>
@ -6099,7 +6143,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Event name. </p>
<p>Event name.</p>
</div>
</div>
@ -6369,7 +6413,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>Name. </p>
<p>Name.</p>
</div>
</div>
@ -6511,7 +6555,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
<div class="w3-half">
<p>true, FSM is in this state. </p>
<p>true, FSM is in this state.</p>
</div>
</div>
@ -6662,6 +6706,28 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(MARKER).tocoaliton" ><strong>MARKER.tocoaliton</strong></a>
</div>
</div>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(MARKER).togroup" ><strong>MARKER.togroup</strong></a>
</div>
</div>