From 18591c434fcd1eff8c55872ffe5ac5d09262d9d6 Mon Sep 17 00:00:00 2001 From: FlightControl Date: Thu, 15 Jun 2017 07:02:20 +0200 Subject: [PATCH] Documentation --- Moose Development/Moose/AI/AI_A2A_Dispatcher.lua | 6 ++++-- docs/Documentation/AI_A2A_Dispatcher.html | 6 ++++-- docs/Documentation/Designate.html | 1 + docs/Documentation/Detection.html | 1 + docs/Documentation/Fsm.html | 3 ++- docs/Documentation/Settings.html | 2 +- docs/Documentation/Spawn.html | 10 ++-------- docs/Documentation/SpawnStatic.html | 1 - docs/Documentation/Spot.html | 4 ---- docs/Documentation/Task_Cargo.html | 1 + 10 files changed, 16 insertions(+), 19 deletions(-) diff --git a/Moose Development/Moose/AI/AI_A2A_Dispatcher.lua b/Moose Development/Moose/AI/AI_A2A_Dispatcher.lua index 6865a0e03..9429bf1b3 100644 --- a/Moose Development/Moose/AI/AI_A2A_Dispatcher.lua +++ b/Moose Development/Moose/AI/AI_A2A_Dispatcher.lua @@ -68,7 +68,7 @@ do -- AI_A2A_DISPATCHER -- It all depends on what the desired effect is. -- -- EWR networks are **dynamically constructed**, that is, they form part of the @{Set#SET_GROUP} object that is given as the input parameter of the AI\_A2A\_DISPATCHER class. - -- By defining in a **smart way the names or name prefixes of the groups** of EWR capable units, these units will be **automatically added or deleted** from the EWR network, + -- By defining in a **smart way the names or name prefixes of the groups** with EWR capable units, these groups will be **automatically added or deleted** from the EWR network, -- increasing or decreasing the radar coverage of the Early Warning System. -- -- See the following example to setup an EWR network containing EWR stations and AWACS. @@ -127,7 +127,9 @@ do -- AI_A2A_DISPATCHER -- ![Banner Image](..\Presentations\AI_A2A_DISPATCHER\Dia9.JPG) -- -- If it’s a cold war then the **borders of red and blue territory** need to be defined using a @{zone} object derived from @{Zone#ZONE_BASE}. - -- If a hot war is chosen then **no borders** actually need to be defined using the helicopter units other than it makes it easier sometimes for the mission maker to envisage where the red and blue territories roughly are. In a hot war the borders are effectively defined by the ground based radar coverage of a coalition. Set the noborders parameter to 1 + -- If a hot war is chosen then **no borders** actually need to be defined using the helicopter units other than + -- it makes it easier sometimes for the mission maker to envisage where the red and blue territories roughly are. + -- In a hot war the borders are effectively defined by the ground based radar coverage of a coalition. -- -- ## 4. Squadrons: -- diff --git a/docs/Documentation/AI_A2A_Dispatcher.html b/docs/Documentation/AI_A2A_Dispatcher.html index 3694b3389..947d2b9c5 100644 --- a/docs/Documentation/AI_A2A_Dispatcher.html +++ b/docs/Documentation/AI_A2A_Dispatcher.html @@ -648,7 +648,7 @@ therefore less CAP and GCI flights will spawn and this will tend to make just th It all depends on what the desired effect is.

EWR networks are dynamically constructed, that is, they form part of the Set#SET_GROUP object that is given as the input parameter of the AI_A2A_DISPATCHER class. -By defining in a smart way the names or name prefixes of the groups of EWR capable units, these units will be automatically added or deleted from the EWR network, +By defining in a smart way the names or name prefixes of the groups with EWR capable units, these groups will be automatically added or deleted from the EWR network, increasing or decreasing the radar coverage of the Early Warning System.

See the following example to setup an EWR network containing EWR stations and AWACS.

@@ -708,7 +708,9 @@ A hot war is one where CAP aircraft will intercept any detected

Banner Image

If it’s a cold war then the borders of red and blue territory need to be defined using a zone object derived from Zone#ZONE_BASE. -If a hot war is chosen then no borders actually need to be defined using the helicopter units other than it makes it easier sometimes for the mission maker to envisage where the red and blue territories roughly are. In a hot war the borders are effectively defined by the ground based radar coverage of a coalition. Set the noborders parameter to 1

+If a hot war is chosen then no borders actually need to be defined using the helicopter units other than +it makes it easier sometimes for the mission maker to envisage where the red and blue territories roughly are. +In a hot war the borders are effectively defined by the ground based radar coverage of a coalition.

4. Squadrons:

diff --git a/docs/Documentation/Designate.html b/docs/Documentation/Designate.html index c0c7ee573..70e3562df 100644 --- a/docs/Documentation/Designate.html +++ b/docs/Documentation/Designate.html @@ -900,6 +900,7 @@ function below will use the range 1-7 just in case

+ DESIGNATE.LaserCodes diff --git a/docs/Documentation/Detection.html b/docs/Documentation/Detection.html index 4893802ee..6e5b46606 100644 --- a/docs/Documentation/Detection.html +++ b/docs/Documentation/Detection.html @@ -2400,6 +2400,7 @@ The index of the DetectedItem.

+ #number DETECTION_BASE.DetectedItemMax diff --git a/docs/Documentation/Fsm.html b/docs/Documentation/Fsm.html index 5267af595..401b60084 100644 --- a/docs/Documentation/Fsm.html +++ b/docs/Documentation/Fsm.html @@ -1604,7 +1604,7 @@ A string defining the start state.

- #string + FSM._StartState @@ -1903,6 +1903,7 @@ A string defining the start state.

+ FSM.current diff --git a/docs/Documentation/Settings.html b/docs/Documentation/Settings.html index 4dce02244..7dca37cbf 100644 --- a/docs/Documentation/Settings.html +++ b/docs/Documentation/Settings.html @@ -1073,7 +1073,7 @@ true if metric.

- #boolean + SETTINGS.Metric diff --git a/docs/Documentation/Spawn.html b/docs/Documentation/Spawn.html index a9e356026..2e89a9cd3 100644 --- a/docs/Documentation/Spawn.html +++ b/docs/Documentation/Spawn.html @@ -2726,9 +2726,6 @@ when nothing was spawned.

- -

Overwrite unit names by default with group name.

-
@@ -2743,9 +2740,6 @@ when nothing was spawned.

- -

By default, no InitLimit

-
@@ -2781,7 +2775,7 @@ when nothing was spawned.

- #number + SPAWN.SpawnMaxGroups @@ -2798,7 +2792,7 @@ when nothing was spawned.

- #number + SPAWN.SpawnMaxUnitsAlive diff --git a/docs/Documentation/SpawnStatic.html b/docs/Documentation/SpawnStatic.html index d8aa5e633..bc91b9624 100644 --- a/docs/Documentation/SpawnStatic.html +++ b/docs/Documentation/SpawnStatic.html @@ -436,7 +436,6 @@ ptional) The name of the new static.

- #number SPAWNSTATIC.SpawnIndex diff --git a/docs/Documentation/Spot.html b/docs/Documentation/Spot.html index 5fdc3b305..ead3792db 100644 --- a/docs/Documentation/Spot.html +++ b/docs/Documentation/Spot.html @@ -765,7 +765,6 @@ true if it is lasing

- SPOT.ScheduleID @@ -779,7 +778,6 @@ true if it is lasing

- SPOT.SpotIR @@ -793,7 +791,6 @@ true if it is lasing

- SPOT.SpotLaser @@ -807,7 +804,6 @@ true if it is lasing

- SPOT.Target diff --git a/docs/Documentation/Task_Cargo.html b/docs/Documentation/Task_Cargo.html index a49a3383f..686daa411 100644 --- a/docs/Documentation/Task_Cargo.html +++ b/docs/Documentation/Task_Cargo.html @@ -524,6 +524,7 @@ based on the tasking capabilities defined in Task#TA
+ FSM_PROCESS.DeployZone