Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
AI_A2A_DISPATCHER:AddProcess(From, Event, Process, ReturnEvents)
Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
AI_A2G_DISPATCHER:AddProcess(From, Event, Process, ReturnEvents)
Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
The Defender Default Settings over all Squadrons.
- - - -The Defender Default Settings over all Squadrons.
- - - -The Defender Default Settings over all Squadrons.
- - - -Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
The Defender Default Settings over all Squadrons.
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
The AIR dispacher needs you to setup (various) defense coordinates, which are strategic positions in the battle field to be defended. +
The AIR dispatcher needs you to setup (various) defense coordinates, which are strategic positions in the battle field to be defended. Any ground based enemy approaching within the proximity of such a defense point, may trigger for a defensive action by friendly air units.
There are 2 important parameters that play a role in the defensive decision making: defensiveness and reactivity.
@@ -1721,7 +1721,7 @@ the higher the probability will be that a defense action will be launched!No, depending on the target type, and the threat level of the target, the probability of defense will be higher. -In other words, when a SAM-10 radar emitter is detected, its probabilty for defense will be much higher than when a BMP-1 vehicle is +In other words, when a SAM-10 radar emitter is detected, its probability for defense will be much higher than when a BMP-1 vehicle is detected, even when both enemies are at the same distance from a defense coordinate. This will ensure optimal defenses, SEAD tasks will be launched much more quicker against engaging radar emitters, to ensure air superiority. Approaching main battle tanks will be engaged much faster, than a group of approaching trucks.
@@ -1730,12 +1730,12 @@ Approaching main battle tanks will be engaged much faster, than a group of approThe AIR defense system works with Squadrons. Each Squadron must be given a unique name, that forms the key to the squadron. -Several options and activities can be set per Squadron. A free format name can be given, but always ensure that the name is meaningfull +Several options and activities can be set per Squadron. A free format name can be given, but always ensure that the name is meaningful for your mission, and remember that squadron names are used for communication to the players of your mission.
There are mainly 3 types of defenses: SEAD, CAS and BAI.
-Suppression of Air Defenses (SEAD) are effective agains radar emitters. Close Air Support (CAS) is launched when the enemy is close near friendly units. +
Suppression of Air Defenses (SEAD) are effective against radar emitters. Close Air Support (CAS) is launched when the enemy is close near friendly units. Battleground Air Interdiction (BAI) tasks are launched when there are no friendlies around.
Depending on the defense type, different payloads will be needed. See further points on squadron definition.
@@ -1795,7 +1795,7 @@ AIR defenses can come immediately into action.Yes, different COORDINATE types are possible to be used. -The COORDINATE_UNIT will help you to specify a defense coodinate that is attached to a moving unit.
+The COORDINATE_UNIT will help you to specify a defense coordinate that is attached to a moving unit.The default takeoff method is staight in the air. +
The default takeoff method is straight in the air. This takeoff method is the most useful if you want to avoid airplane clutter at airbases! But it is the least realistic one!
@@ -1859,10 +1859,10 @@ But it is the least realistic one!For each Squadron, depending on the helicopter or airplane type (modern, old) and payload, which overhead is required to provide any defense?
-In other words, if X enemy ground units are detected, how many Y defense helicpters or airplanes need to engage (per squadron)? +
In other words, if X enemy ground units are detected, how many Y defense helicopters or airplanes need to engage (per squadron)? The Y is dependent on the type of airplane (era), payload, fuel levels, skills etc. But the most important factor is the payload, which is the amount of AIR weapons the defense can carry to attack the enemy ground units. -For example, a Ka-50 can carry 16 vikrs, that means, that it potentially can destroy at least 8 ground units without a reload of ammunication. +For example, a Ka-50 can carry 16 vikrs, that means, that it potentially can destroy at least 8 ground units without a reload of ammunition. That means, that one defender can destroy more enemy ground units. Thus, the overhead is a factor that will calculate dynamically how many Y defenses will be required based on X attackers detected.
@@ -1912,7 +1912,7 @@ The defense system work through the definition of defense coordinates, which are Multiple defense coordinates can be setup. Defense coordinates can be strategic or tactical positions or references to strategic units or scenery. The AIR dispatcher will evaluate every x seconds the tactical situation around each defense coordinate. When a defense coordinate is under threat, it will communicate through the command center that defensive actions need to be taken and will launch groups of air units for defense. -The level of threat to the defense coordinate varyies upon the strength and types of the enemy units, the distance to the defense point, and the defensiveness parameters. +The level of threat to the defense coordinate varies upon the strength and types of the enemy units, the distance to the defense point, and the defensiveness parameters. Defensive actions are taken through probability, but the closer and the more threat the enemy poses to the defense coordinate, the faster it will be attacked by friendly AIR units.Please study carefully the underlying explanations how to setup and use this module, as it has many features. @@ -1961,7 +1961,7 @@ when these groups are spawned in or destroyed during the ongoing battle. By spawning in dynamically additional recce, you can ensure that there is sufficient reconnaissance coverage so the defense mechanism is continuously alerted of new enemy ground targets.
-The following example defens a new reconnaissance network using a Functional.Detection#DETECTION_AREAS object.
+The following example defense a new reconnaissance network using a Functional.Detection#DETECTION_AREAS object.
-- Define a SET_GROUP object that builds a collection of groups that define the recce network.
-- Here we build the network with all the groups that have a name starting with CCCP Recce.
@@ -2118,7 +2118,7 @@ while defining which helicopter or plane templates are being us
The method AI_AIR_DISPATCHER.SetSquadron() defines for you a new squadron.
-The provided parameters are the squadron name, airbase name and a list of template prefixe, and a number that indicates the amount of resources.
+The provided parameters are the squadron name, airbase name and a list of template prefixes, and a number that indicates the amount of resources.
For example, this defines 3 new squadrons:
@@ -2282,7 +2282,7 @@ If this parameter is not specified, then the default altitude will be used for t
Depending on the demand of requested takeoffs by the AIR dispatcher, an airfield can become overloaded. Too many aircraft need to be taken
off at the same time, which will result in clutter as described above. In order to better control this behaviour, a takeoff scheduler is implemented,
which can be used to control how many aircraft are ordered for takeoff between specific time intervals.
-The takeff intervals can be specified per squadron, which make sense, as each squadron have a "home" airfield.
+The takeoff intervals can be specified per squadron, which make sense, as each squadron have a "home" airfield.
For this purpose, the method AI_AIR_DISPATCHER.SetSquadronTakeOffInterval() can be used to specify the takeoff intervals of
aircraft groups per squadron to avoid cluttering of aircraft at airbases.
@@ -3519,7 +3519,7 @@ of the squadron will be destroyed. This to keep consistency of air operations no
AI_AIR_DISPATCHER:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -5885,7 +5885,7 @@ The Detection object is polymorphic, depending on the type of detection object c
- Tasking.Task_AIR#AI_AIR
+ AI.AI_Air#AI_AIR
Task
@@ -11378,7 +11378,7 @@ multiplied by the Overhead and rounded up to the smallest integer.
AI_AIR_DISPATCHER:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_Air_Patrol.html b/Documentation/AI.AI_Air_Patrol.html
index a8a005e95..40c2e0327 100644
--- a/Documentation/AI.AI_Air_Patrol.html
+++ b/Documentation/AI.AI_Air_Patrol.html
@@ -2464,7 +2464,7 @@ Use the method AI.AI_CAP
AI_AIR_PATROL:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -7902,7 +7902,7 @@ A random value in this bracket is then applied in the waypoint routing generatio
AI_AIR_PATROL:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_BAI.html b/Documentation/AI.AI_BAI.html
index b9408b118..35ee89e0f 100644
--- a/Documentation/AI.AI_BAI.html
+++ b/Documentation/AI.AI_BAI.html
@@ -2661,7 +2661,7 @@ is the point where a map object is to be destroyed (like a bridge).
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -9691,7 +9691,7 @@ Note that this method is required, as triggers the next route when patrolling fo
AI_BAI_ZONE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_Balancer.html b/Documentation/AI.AI_Balancer.html
index ee36b6961..e39debd24 100644
--- a/Documentation/AI.AI_Balancer.html
+++ b/Documentation/AI.AI_Balancer.html
@@ -1888,7 +1888,7 @@ otherwise the AI_BALANCER will trigger a Destroy event, and the
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -3672,7 +3672,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
AI_BALANCER:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_CAP.html b/Documentation/AI.AI_CAP.html
index fc501dd2f..36163dbe4 100644
--- a/Documentation/AI.AI_CAP.html
+++ b/Documentation/AI.AI_CAP.html
@@ -2574,7 +2574,7 @@ Use the method AI_CAP_ZONE.SetEngageZone
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -9301,7 +9301,7 @@ Note that this method is required, as triggers the next route when patrolling fo
AI_CAP_ZONE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_CAS.html b/Documentation/AI.AI_CAS.html
index a9b4f2294..431aabaeb 100644
--- a/Documentation/AI.AI_CAS.html
+++ b/Documentation/AI.AI_CAS.html
@@ -2592,7 +2592,7 @@ It can be notified to go RTB through the RTB event.
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -9527,7 +9527,7 @@ Note that this method is required, as triggers the next route when patrolling fo
AI_CAS_ZONE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_Cargo.html b/Documentation/AI.AI_Cargo.html
index b47b5e2dc..8f8063f09 100644
--- a/Documentation/AI.AI_Cargo.html
+++ b/Documentation/AI.AI_Cargo.html
@@ -1940,7 +1940,7 @@ Please consult the Cargo.Cargo module for more in
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -2755,7 +2755,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
+ Wrapper.Group#GROUP
AI_CARGO.CargoCarrier
@@ -4785,7 +4785,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
+ Wrapper.Group#GROUP
AI_CARGO.CargoCarrier
@@ -5397,7 +5397,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
+ Wrapper.Group#GROUP
AI_CARGO.CargoCarrier
@@ -5491,7 +5491,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
AI_CARGO:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -6897,7 +6897,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
+ Wrapper.Group#GROUP
AI_CARGO.CargoCarrier
diff --git a/Documentation/AI.AI_Cargo_APC.html b/Documentation/AI.AI_Cargo_APC.html
index 7dd773fec..b312fed37 100644
--- a/Documentation/AI.AI_Cargo_APC.html
+++ b/Documentation/AI.AI_Cargo_APC.html
@@ -2178,7 +2178,7 @@ The APCs will follow nearby roads as much as possible, to ensure fast and clean
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -7358,7 +7358,7 @@ AICargoAPC:SetCombatRadius( false )
AI_CARGO_APC:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_Cargo_Airplane.html b/Documentation/AI.AI_Cargo_Airplane.html
index b8eb85a4c..b44e4b3eb 100644
--- a/Documentation/AI.AI_Cargo_Airplane.html
+++ b/Documentation/AI.AI_Cargo_Airplane.html
@@ -1930,7 +1930,7 @@ time is not so much of an issue ...
AI_CARGO_AIRPLANE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -2742,6 +2742,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
Field(s)
+
+
+
+
+AI_CARGO_AIRPLANE.Airbase
+
+
+
+
+
+
@@ -2797,6 +2808,9 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
+
+ Aircraft is on a pickup mission.
+
@@ -4515,6 +4529,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
Field(s)
+
+
+
+
+AI_CARGO_AIRPLANE.Airbase
+
+
+
+
+
+
@@ -4570,6 +4595,9 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
+
+ Aircraft is on a pickup mission.
+
@@ -5130,6 +5158,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
Field(s)
+
+
+
+
+AI_CARGO_AIRPLANE.Airbase
+
+
+
+
+
+
@@ -5185,6 +5224,9 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
+
+ Aircraft is on a pickup mission.
+
@@ -5230,7 +5272,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
AI_CARGO_AIRPLANE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -6633,6 +6675,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
Field(s)
+
+
+
+
+AI_CARGO_AIRPLANE.Airbase
+
+
+
+
+
+
@@ -6688,6 +6741,9 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
+
+ Aircraft is on a pickup mission.
+
diff --git a/Documentation/AI.AI_Cargo_Dispatcher.html b/Documentation/AI.AI_Cargo_Dispatcher.html
index 954770637..9ca5d831a 100644
--- a/Documentation/AI.AI_Cargo_Dispatcher.html
+++ b/Documentation/AI.AI_Cargo_Dispatcher.html
@@ -2545,7 +2545,7 @@ Use AI_CARGO_DISPATCHER.SetHomeZon
AI_CARGO_DISPATCHER:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -6026,7 +6026,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
AI_CARGO_DISPATCHER:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_Cargo_Dispatcher_APC.html b/Documentation/AI.AI_Cargo_Dispatcher_APC.html
index f7e243a7b..04f38717c 100644
--- a/Documentation/AI.AI_Cargo_Dispatcher_APC.html
+++ b/Documentation/AI.AI_Cargo_Dispatcher_APC.html
@@ -2186,7 +2186,7 @@ Use AI_CARGO_DISPATCHER_APC.Se
AI_CARGO_DISPATCHER_APC:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -5626,7 +5626,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
AI_CARGO_DISPATCHER_APC:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_Cargo_Dispatcher_Airplane.html b/Documentation/AI.AI_Cargo_Dispatcher_Airplane.html
index a090c674b..adea80c9d 100644
--- a/Documentation/AI.AI_Cargo_Dispatcher_Airplane.html
+++ b/Documentation/AI.AI_Cargo_Dispatcher_Airplane.html
@@ -2097,7 +2097,7 @@ Check out the AI.AI
AI_CARGO_DISPATCHER_AIRPLANE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -5220,7 +5220,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
AI_CARGO_DISPATCHER_AIRPLANE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_Cargo_Dispatcher_Helicopter.html b/Documentation/AI.AI_Cargo_Dispatcher_Helicopter.html
index 9955d9367..3559badce 100644
--- a/Documentation/AI.AI_Cargo_Dispatcher_Helicopter.html
+++ b/Documentation/AI.AI_Cargo_Dispatcher_Helicopter.html
@@ -2135,7 +2135,7 @@ Use AI_CARGO_DISPATCHER
AI_CARGO_DISPATCHER_HELICOPTER:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -5252,7 +5252,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
AI_CARGO_DISPATCHER_HELICOPTER:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_Cargo_Dispatcher_Ship.html b/Documentation/AI.AI_Cargo_Dispatcher_Ship.html
index 95452cfe0..ae6d290d5 100644
--- a/Documentation/AI.AI_Cargo_Dispatcher_Ship.html
+++ b/Documentation/AI.AI_Cargo_Dispatcher_Ship.html
@@ -2133,7 +2133,7 @@ Use AI_CARGO_DISPATCHER_SHIP.
AI_CARGO_DISPATCHER_SHIP:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -5295,7 +5295,7 @@ AICargoDispatcherHelicopter:SetPickupSpeed( 200, 100 )
AI_CARGO_DISPATCHER_SHIP:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_Cargo_Helicopter.html b/Documentation/AI.AI_Cargo_Helicopter.html
index d38f209be..a85e96be9 100644
--- a/Documentation/AI.AI_Cargo_Helicopter.html
+++ b/Documentation/AI.AI_Cargo_Helicopter.html
@@ -2001,7 +2001,7 @@ time is not so much of an issue ...
AI_CARGO_HELICOPTER:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -2907,22 +2907,28 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
+ #number
AI_CARGO_HELICOPTER.landingheight
+
+ meter
+
-
+ #number
AI_CARGO_HELICOPTER.landingspeed
+
+ kph
+
@@ -4825,22 +4831,28 @@ Adjust if necessary.
-
+ #number
AI_CARGO_HELICOPTER.landingheight
+
+ meter
+
-
+ #number
AI_CARGO_HELICOPTER.landingspeed
+
+ kph
+
@@ -5495,22 +5507,28 @@ Adjust if necessary.
-
+ #number
AI_CARGO_HELICOPTER.landingheight
+
+ meter
+
-
+ #number
AI_CARGO_HELICOPTER.landingspeed
+
+ kph
+
@@ -5556,7 +5574,7 @@ Adjust if necessary.
AI_CARGO_HELICOPTER:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -7053,22 +7071,28 @@ Adjust if necessary.
-
+ #number
AI_CARGO_HELICOPTER.landingheight
+
+ meter
+
-
+ #number
AI_CARGO_HELICOPTER.landingspeed
+
+ kph
+
diff --git a/Documentation/AI.AI_Cargo_Ship.html b/Documentation/AI.AI_Cargo_Ship.html
index f66f69daa..ffe18aaa8 100644
--- a/Documentation/AI.AI_Cargo_Ship.html
+++ b/Documentation/AI.AI_Cargo_Ship.html
@@ -2073,7 +2073,7 @@ coordinate. The Ship will follow the Shipping Lane to ensure consistent cargo tr
AI_CARGO_SHIP:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -6556,7 +6556,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
AI_CARGO_SHIP:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_Escort.html b/Documentation/AI.AI_Escort.html
index 96cc281e3..48fee70ba 100644
--- a/Documentation/AI.AI_Escort.html
+++ b/Documentation/AI.AI_Escort.html
@@ -3022,7 +3022,7 @@ EscortPlanes = AI_ESCORT:New( EscortUnit, EscortGroup, "Desert", "Welcome to the
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -15373,7 +15373,7 @@ EscortPlanes = AI_ESCORT:New( EscortUnit, EscortGroup, "Desert", "Welcome to the
AI_ESCORT:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_Escort_Dispatcher.html b/Documentation/AI.AI_Escort_Dispatcher.html
index fd5412b06..66fb6fdbb 100644
--- a/Documentation/AI.AI_Escort_Dispatcher.html
+++ b/Documentation/AI.AI_Escort_Dispatcher.html
@@ -1763,7 +1763,7 @@ Controls a network of short range air/missile defense groups.
AI_ESCORT_DISPATCHER:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -3086,7 +3086,7 @@ Red_SU25T_EscortDispatcher:Start()
AI_ESCORT_DISPATCHER:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_Escort_Dispatcher_Request.html b/Documentation/AI.AI_Escort_Dispatcher_Request.html
index aa20e29bc..a9fa5e6bf 100644
--- a/Documentation/AI.AI_Escort_Dispatcher_Request.html
+++ b/Documentation/AI.AI_Escort_Dispatcher_Request.html
@@ -1765,7 +1765,7 @@ Controls a network of short range air/missile defense groups.
AI_ESCORT_DISPATCHER_REQUEST:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -3065,7 +3065,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
AI_ESCORT_DISPATCHER_REQUEST:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_Escort_Request.html b/Documentation/AI.AI_Escort_Request.html
index fbacb3f5c..833d162bb 100644
--- a/Documentation/AI.AI_Escort_Request.html
+++ b/Documentation/AI.AI_Escort_Request.html
@@ -3109,7 +3109,7 @@ EscortPlanes = AI_ESCORT_REQUEST:New( EscortUnit, EscortGroup, "Desert", "Welcom
AI_ESCORT_REQUEST:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -15462,7 +15462,7 @@ EscortPlanes = AI_ESCORT:New( EscortUnit, EscortGroup, "Desert", "Welcome to the
AI_ESCORT_REQUEST:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_Formation.html b/Documentation/AI.AI_Formation.html
index 599dbba01..206bd55e3 100644
--- a/Documentation/AI.AI_Formation.html
+++ b/Documentation/AI.AI_Formation.html
@@ -2229,7 +2229,7 @@ LargeFormation:__Start( 1 )
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -10327,7 +10327,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
AI_FORMATION:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/AI.AI_Patrol.html b/Documentation/AI.AI_Patrol.html
index 80c900d65..c50dd09b2 100644
--- a/Documentation/AI.AI_Patrol.html
+++ b/Documentation/AI.AI_Patrol.html
@@ -2358,7 +2358,7 @@ Use the method AI_PATROL_ZONE.ManageDa
AI_PATROL_ZONE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -3258,9 +3258,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
- This table contains the targets detected during patrol.
-
@@ -6508,9 +6505,6 @@ Note that this method is required, as triggers the next route when patrolling fo
-
- This table contains the targets detected during patrol.
-
@@ -7255,9 +7249,6 @@ Note that this method is required, as triggers the next route when patrolling fo
-
- This table contains the targets detected during patrol.
-
@@ -7402,7 +7393,7 @@ Note that this method is required, as triggers the next route when patrolling fo
AI_PATROL_ZONE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -8890,9 +8881,6 @@ Note that this method is required, as triggers the next route when patrolling fo
-
- This table contains the targets detected during patrol.
-
diff --git a/Documentation/Actions.Act_Account.html b/Documentation/Actions.Act_Account.html
index 2743149df..03ea08d01 100644
--- a/Documentation/Actions.Act_Account.html
+++ b/Documentation/Actions.Act_Account.html
@@ -1762,7 +1762,7 @@ Controls a network of short range air/missile defense groups.
-Send a message of the Task to the Group of the Unit.
+Send a message of the Tasking.Task to the Group of the Unit.
@@ -1898,7 +1898,7 @@ Controls a network of short range air/missile defense groups.
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -3407,7 +3407,7 @@ There are 2 moments when state transition methods will be called by the state ma
ACT_ACCOUNT:Message(Message)
-Send a message of the Task to the Group of the Unit.
+Send a message of the Tasking.Task to the Group of the Unit.
@@ -4426,7 +4426,7 @@ There are 2 moments when state transition methods will be called by the state ma
ACT_ACCOUNT:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Actions.Act_Assign.html b/Documentation/Actions.Act_Assign.html
index 3654c6f3e..376fdf587 100644
--- a/Documentation/Actions.Act_Assign.html
+++ b/Documentation/Actions.Act_Assign.html
@@ -1855,7 +1855,7 @@ The assignment type also allows to reject the task.
-Send a message of the Task to the Group of the Unit.
+Send a message of the Tasking.Task to the Group of the Unit.
@@ -1991,7 +1991,7 @@ The assignment type also allows to reject the task.
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -3344,7 +3344,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
ACT_ASSIGN:Message(Message)
-Send a message of the Task to the Group of the Unit.
+Send a message of the Tasking.Task to the Group of the Unit.
@@ -4385,7 +4385,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
ACT_ASSIGN:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Actions.Act_Assist.html b/Documentation/Actions.Act_Assist.html
index 69efbfd96..58e3fcc6d 100644
--- a/Documentation/Actions.Act_Assist.html
+++ b/Documentation/Actions.Act_Assist.html
@@ -1857,7 +1857,7 @@ At random intervals, a new target is smoked.
-Send a message of the Task to the Group of the Unit.
+Send a message of the Tasking.Task to the Group of the Unit.
@@ -1993,7 +1993,7 @@ At random intervals, a new target is smoked.
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -3456,7 +3456,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
ACT_ASSIST:Message(Message)
-Send a message of the Task to the Group of the Unit.
+Send a message of the Tasking.Task to the Group of the Unit.
@@ -4607,7 +4607,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
ACT_ASSIST:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Actions.Act_Route.html b/Documentation/Actions.Act_Route.html
index 00f90fc53..7461729b2 100644
--- a/Documentation/Actions.Act_Route.html
+++ b/Documentation/Actions.Act_Route.html
@@ -1914,7 +1914,7 @@ Upon arrival at the zone, a confirmation of arrival is sent, and the process wil
-Send a message of the Task to the Group of the Unit.
+Send a message of the Tasking.Task to the Group of the Unit.
@@ -2050,7 +2050,7 @@ Upon arrival at the zone, a confirmation of arrival is sent, and the process wil
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -3898,7 +3898,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
ACT_ROUTE:Message(Message)
-Send a message of the Task to the Group of the Unit.
+Send a message of the Tasking.Task to the Group of the Unit.
@@ -5027,7 +5027,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
ACT_ROUTE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Cargo.Cargo.html b/Documentation/Cargo.Cargo.html
index 0a3a8d4bb..8a678e281 100644
--- a/Documentation/Cargo.Cargo.html
+++ b/Documentation/Cargo.Cargo.html
@@ -2641,7 +2641,7 @@ All derived classes from CARGO follow the same state machine, expose the same ca
-Send a message of the Task to the Group of the Unit.
+Send a message of the Tasking.Task to the Group of the Unit.
@@ -2777,7 +2777,7 @@ All derived classes from CARGO follow the same state machine, expose the same ca
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -6965,7 +6965,7 @@ The cargo must be in the Loaded state.
CARGO:Message(Message)
-Send a message of the Task to the Group of the Unit.
+Send a message of the Tasking.Task to the Group of the Unit.
@@ -8270,7 +8270,7 @@ The cargo must be in the Loaded state.
CARGO:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Cargo.CargoGroup.html b/Documentation/Cargo.CargoGroup.html
index 69f05de47..bc88b2bd7 100644
--- a/Documentation/Cargo.CargoGroup.html
+++ b/Documentation/Cargo.CargoGroup.html
@@ -1934,20 +1934,6 @@ Controls a network of short range air/missile defense groups.
-CARGO_GROUP.CargoCarrier
-
-
-
-
-self.CargoObject:Destroy()
-
-
-
-
-
-
-
-
CARGO_GROUP.CargoGroup
@@ -3269,20 +3255,6 @@ This works for ground only groups.
-CARGO_GROUP.CargoCarrier
-
-
-
-
-self.CargoObject:Destroy()
-
-
-
-
-
-
-
-
CARGO_GROUP.CargoGroup
diff --git a/Documentation/Cargo.CargoUnit.html b/Documentation/Cargo.CargoUnit.html
index b33acc5ed..c0f4de054 100644
--- a/Documentation/Cargo.CargoUnit.html
+++ b/Documentation/Cargo.CargoUnit.html
@@ -1812,17 +1812,6 @@ Note that ground forces behave in a group, and thus, act in formation, regardles
-CARGO_UNIT.CargoCarrier
-
-
-
-
-
-
-
-
-
-
CARGO_UNIT.CargoInAir
@@ -1841,6 +1830,17 @@ Note that ground forces behave in a group, and thus, act in formation, regardles
Set cargo object.
+
+
+
+
+
+
+ #number
+CARGO_UNIT.RunCount
+
+
+
@@ -2527,17 +2527,6 @@ Note that ground forces behave in a group, and thus, act in formation, regardles
-CARGO_UNIT.CargoCarrier
-
-
-
-
-
-
-
-
-
-
CARGO_UNIT.CargoInAir
@@ -2556,6 +2545,17 @@ Note that ground forces behave in a group, and thus, act in formation, regardles
Set cargo object.
+
+
+
+
+
+
+ #number
+CARGO_UNIT.RunCount
+
+
+
diff --git a/Documentation/Core.Fsm.html b/Documentation/Core.Fsm.html
index 19ea10acb..30fd1f246 100644
--- a/Documentation/Core.Fsm.html
+++ b/Documentation/Core.Fsm.html
@@ -1664,8 +1664,8 @@ Each of these FSM implementation classes start either with:
- an acronym AI_, which indicates a FSM implementation directing AI controlled Wrapper.Group#GROUP and/or Wrapper.Unit#UNIT. These AI_ classes derive the #FSM_CONTROLLABLE class.
- - an acronym TASK_, which indicates a FSM implementation executing a TASK executed by Groups of players. These TASK_ classes derive the #FSM_TASK class.
- - an acronym ACT_, which indicates an Sub-FSM implementation, directing Humans actions that need to be done in a TASK, seated in a CLIENT (slot) or a Wrapper.Unit#UNIT (CA join). These ACT_ classes derive the #FSM_PROCESS class.
+ - an acronym TASK_, which indicates a FSM implementation executing a Tasking.Task#TASK executed by Groups of players. These TASK_ classes derive the #FSM_TASK class.
+ - an acronym ACT_, which indicates an Sub-FSM implementation, directing Humans actions that need to be done in a Tasking.Task#TASK, seated in a Wrapper.Client#CLIENT (slot) or a Wrapper.Unit#UNIT (CA join). These ACT_ classes derive the #FSM_PROCESS class.
Detailed explanations and API specifics are further below clarified and FSM derived class specifics are described in those class documentation sections.
@@ -1679,9 +1679,9 @@ Additionally, I've added extendability and created an API that allows seamless F
The following derived classes are available in the MOOSE framework, that implement a specialized form of a FSM:
- - #FSM_TASK: Models Finite State Machines for Tasks.
- - #FSM_PROCESS: Models Finite State Machines for Task actions, which control Clients.
- - #FSM_CONTROLLABLE: Models Finite State Machines for Wrapper.Controllables, which are Wrapper.Groups, Wrapper.Units, Clients.
+ - #FSM_TASK: Models Finite State Machines for Tasking.Tasks.
+ - #FSM_PROCESS: Models Finite State Machines for Tasking.Task actions, which control Wrapper.Clients.
+ - #FSM_CONTROLLABLE: Models Finite State Machines for Wrapper.Controllables, which are Wrapper.Groups, Wrapper.Units, Wrapper.Clients.
- #FSM_SET: Models Finite State Machines for Core.Sets. Note that these FSMs control multiple objects!!! So State concerns here
for multiple objects or the position of the state machine in the process.
@@ -1749,8 +1749,8 @@ Each of these FSM implementation classes start either with:
- an acronym AI_, which indicates an FSM implementation directing AI controlled Wrapper.Group#GROUP and/or Wrapper.Unit#UNIT. These AI_ classes derive the #FSM_CONTROLLABLE class.
- - an acronym TASK_, which indicates an FSM implementation executing a TASK executed by Groups of players. These TASK_ classes derive the #FSM_TASK class.
- - an acronym ACT_, which indicates an Sub-FSM implementation, directing Humans actions that need to be done in a TASK, seated in a CLIENT (slot) or a Wrapper.Unit#UNIT (CA join). These ACT_ classes derive the #FSM_PROCESS class.
+ - an acronym TASK_, which indicates an FSM implementation executing a Tasking.Task#TASK executed by Groups of players. These TASK_ classes derive the #FSM_TASK class.
+ - an acronym ACT_, which indicates an Sub-FSM implementation, directing Humans actions that need to be done in a Tasking.Task#TASK, seated in a Wrapper.Client#CLIENT (slot) or a Wrapper.Unit#UNIT (CA join). These ACT_ classes derive the #FSM_PROCESS class.

@@ -2004,7 +2004,7 @@ Depending upon which state is returned, the main FSM can contin
Global FSM_CONTROLLABLE
-Models Finite State Machines for Wrapper.Controllables, which are Wrapper.Groups, Wrapper.Units, Clients.
+Models Finite State Machines for Wrapper.Controllables, which are Wrapper.Groups, Wrapper.Units, Wrapper.Clients.
@@ -2015,7 +2015,7 @@ Depending upon which state is returned, the main FSM can contin
#FSM_CONTROLLABLE
FSM_CONTROLLABLE
-Models Finite State Machines for Wrapper.Controllables, which are Wrapper.Groups, Wrapper.Units, Clients.
+Models Finite State Machines for Wrapper.Controllables, which are Wrapper.Groups, Wrapper.Units, Wrapper.Clients.
@@ -2030,7 +2030,7 @@ Depending upon which state is returned, the main FSM can contin
Global FSM_PROCESS
-FSM_PROCESS class models Finite State Machines for Task actions, which control Clients.
+FSM_PROCESS class models Finite State Machines for Tasking.Task actions, which control Wrapper.Clients.
@@ -2041,7 +2041,7 @@ Depending upon which state is returned, the main FSM can contin
#FSM_PROCESS
FSM_PROCESS
-FSM_PROCESS class models Finite State Machines for Task actions, which control Clients.
+FSM_PROCESS class models Finite State Machines for Tasking.Task actions, which control Wrapper.Clients.
@@ -2126,7 +2126,7 @@ for multiple objects or the position of the state machine in the process.
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -3021,7 +3021,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
FSM_CONTROLLABLE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -3873,7 +3873,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-Send a message of the Task to the Group of the Unit.
+Send a message of the Tasking.Task to the Group of the Unit.
@@ -4009,7 +4009,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -4862,7 +4862,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -5902,7 +5902,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
FSM:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -11439,7 +11439,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
FSM_CONTROLLABLE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -16456,7 +16456,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
FSM_PROCESS:Message(Message)
-Send a message of the Task to the Group of the Unit.
+Send a message of the Tasking.Task to the Group of the Unit.
@@ -17431,7 +17431,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
FSM_PROCESS:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -22433,7 +22433,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
FSM_SET:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Core.Goal.html b/Documentation/Core.Goal.html
index 971985a1b..ecf7aa6fb 100644
--- a/Documentation/Core.Goal.html
+++ b/Documentation/Core.Goal.html
@@ -1816,7 +1816,7 @@ You can use this method to check asynchronously if a goal has been achieved, for
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -3183,7 +3183,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
GOAL:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Core.MarkerOps_Base.html b/Documentation/Core.MarkerOps_Base.html
index c713cc4b3..fb1cec1b7 100644
--- a/Documentation/Core.MarkerOps_Base.html
+++ b/Documentation/Core.MarkerOps_Base.html
@@ -1803,7 +1803,7 @@ Last Update: Sep 2022
MARKEROPS_BASE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -3627,7 +3627,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
MARKEROPS_BASE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Core.Message.html b/Documentation/Core.Message.html
index 509bf2f99..32b8adb2e 100644
--- a/Documentation/Core.Message.html
+++ b/Documentation/Core.Message.html
@@ -1660,7 +1660,7 @@ To send messages, you need to use the To functions.
Messages are sent:
- - To a Client using MESSAGE.ToClient().
+ - To a Wrapper.Client using MESSAGE.ToClient().
- To a Wrapper.Group using MESSAGE.ToGroup()
- To a Wrapper.Unit using MESSAGE.ToUnit()
- To a coalition using MESSAGE.ToCoalition().
diff --git a/Documentation/Core.Point.html b/Documentation/Core.Point.html
index 44531e82d..1837d31d9 100644
--- a/Documentation/Core.Point.html
+++ b/Documentation/Core.Point.html
@@ -1780,7 +1780,7 @@ on the map for all players, coalitions or specific groups:
Calculate if the coordinate has Line of Sight (LOS) with the other given coordinate.
Mountains, trees and other objects can be positioned between the two 3D points, preventing visibilty in a straight continuous line.
-The method COORDINATE.IsLOS() returns if the two coodinates have LOS.
+The method COORDINATE.IsLOS() returns if the two coordinates have LOS.
4.7) Check the coordinate position.
@@ -12908,7 +12908,7 @@ Creates a line on the F10 map from one point to another.
-If true, overwrite the original COORDINATE with the translated one. Otherwise, create a new COODINATE.
+If true, overwrite the original COORDINATE with the translated one. Otherwise, create a new COORDINATE.
@@ -17583,6 +17583,17 @@ When moose is loading dynamically (for moose class development), tracing is swit
the y coordinate in meters.
+
+
+
+
+
+
+
+POINT_VEC2.z
+
+
+
@@ -17809,7 +17820,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
-The x coodinate.
+The x coordinate.
@@ -17839,7 +17850,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
-The y coodinate.
+The y coordinate.
@@ -17922,7 +17933,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
-The x coodinate.
+The x coordinate.
@@ -17952,7 +17963,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
-The y coodinate.
+The y coordinate.
@@ -18381,6 +18392,17 @@ When moose is loading dynamically (for moose class development), tracing is swit
the y coordinate in meters.
+
+
+
+
+
+
+
+POINT_VEC2.z
+
+
+
@@ -25759,7 +25781,7 @@ Creates a line on the F10 map from one point to another.
-If true, overwrite the original COORDINATE with the translated one. Otherwise, create a new COODINATE.
+If true, overwrite the original COORDINATE with the translated one. Otherwise, create a new COORDINATE.
@@ -26722,6 +26744,17 @@ Creates a line on the F10 map from one point to another.
the y coordinate in meters.
+
+
+
+
+
+
+
+POINT_VEC2.z
+
+
+
@@ -30202,7 +30235,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
-The x coordinate value to add to the current x coodinate.
+The x coordinate value to add to the current x coordinate.
@@ -30246,7 +30279,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
-The y coordinate value to add to the current y coodinate.
+The y coordinate value to add to the current y coordinate.
@@ -30290,7 +30323,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
-The z coordinate value to add to the current z coodinate.
+The z coordinate value to add to the current z coordinate.
@@ -30384,7 +30417,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
-The x coodinate.
+The x coordinate.
@@ -30414,7 +30447,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
-The y coodinate.
+The y coordinate.
@@ -30444,7 +30477,7 @@ When moose is loading dynamically (for moose class development), tracing is swit
-The z coodinate.
+The z coordinate.
diff --git a/Documentation/Core.Set.html b/Documentation/Core.Set.html
index 911166550..d3742b55f 100644
--- a/Documentation/Core.Set.html
+++ b/Documentation/Core.Set.html
@@ -1636,11 +1636,11 @@ Controls a network of short range air/missile defense groups.
#SET_GROUP: Defines a collection of Wrapper.Groups filtered by filter criteria.
#SET_UNIT: Defines a collection of Wrapper.Units filtered by filter criteria.
#SET_STATIC: Defines a collection of Wrapper.Statics filtered by filter criteria.
- #SET_CLIENT: Defines a collection of Clients filtered by filter criteria.
+ #SET_CLIENT: Defines a collection of Wrapper.Clients filtered by filter criteria.
#SET_AIRBASE: Defines a collection of Wrapper.Airbases filtered by filter criteria.
#SET_CARGO: Defines a collection of Cargo.Cargos filtered by filter criteria.
#SET_ZONE: Defines a collection of Core.Zones filtered by filter criteria.
- #SET_SCENERY: Defines a collection of Warpper.Scenerys added via a filtered #SET_ZONE.
+ #SET_SCENERY: Defines a collection of Wrapper.Scenerys added via a filtered #SET_ZONE.
These classes are derived from #SET_BASE, which contains the main methods to manage the collections.
diff --git a/Documentation/Core.Spawn.html b/Documentation/Core.Spawn.html
index 51c65e00c..906ba79a4 100644
--- a/Documentation/Core.Spawn.html
+++ b/Documentation/Core.Spawn.html
@@ -2864,7 +2864,7 @@ and any spaces before and after the resulting name are removed.
-
+
@@ -3509,6 +3509,9 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
+
+ Don't repeat the group from Take-Off till Landing and back Take-Off by ReSpawning.
+
@@ -3586,6 +3589,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
+
+
+
+
+
+
+
+SPAWN.SpawnGrouping
+
+
+
@@ -3622,6 +3636,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
+
+
+
+
+
+
+
+SPAWN.SpawnInitAirbase
+
+
+
@@ -3721,20 +3746,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
-
-
-
-
-
- #boolean
-SPAWN.SpawnInitKeepUnitNames
-
-
-
-
- Overwrite unit names by default with group name.
-
@@ -3757,6 +3768,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
+
+
+
+
+
+
+
+SPAWN.SpawnInitModex
+
+
+
@@ -3768,6 +3790,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
+
+
+
+
+
+
+ #string
+SPAWN.SpawnInitSkill
+
+
+
@@ -3971,7 +4004,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- Flag that indicates if all the Groups of the SpawnGroup need to be visible when Spawned.
+ When the first Spawn executes, all the Groups need to be made visible before start.
@@ -4052,7 +4085,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-SPAWN.skill
+SPAWN.modulation
@@ -8882,6 +8915,9 @@ This is needed to ensure that Re-SPAWNing only is done for landed AIR Groups. Don't repeat the group from Take-Off till Landing and back Take-Off by ReSpawning.
+
@@ -8959,6 +8995,17 @@ This is needed to ensure that Re-SPAWNing only is done for landed AIR Groups.
+
+
+
+
+
+
+SPAWN.SpawnGrouping
+
+
+
@@ -8995,6 +9042,17 @@ This is needed to ensure that Re-SPAWNing only is done for landed AIR Groups.
+
+
+
+
+
+
+SPAWN.SpawnInitAirbase
+
+
+
@@ -9094,20 +9152,6 @@ This is needed to ensure that Re-SPAWNing only is done for landed AIR Groups.
-
-
-
-
-
- #boolean
-SPAWN.SpawnInitKeepUnitNames
-
-
-
-
- Overwrite unit names by default with group name.
-
@@ -9130,6 +9174,17 @@ This is needed to ensure that Re-SPAWNing only is done for landed AIR Groups.
+
+
+
+
+
+
+SPAWN.SpawnInitModex
+
+
+
@@ -9141,6 +9196,17 @@ This is needed to ensure that Re-SPAWNing only is done for landed AIR Groups.
+
+
+
+
+
+ #string
+SPAWN.SpawnInitSkill
+
+
+
@@ -9344,7 +9410,7 @@ This is needed to ensure that Re-SPAWNing only is done for landed AIR Groups. Flag that indicates if all the Groups of the SpawnGroup need to be visible when Spawned.
+ When the first Spawn executes, all the Groups need to be made visible before start.
@@ -9425,7 +9491,7 @@ This is needed to ensure that Re-SPAWNing only is done for landed AIR Groups.
-SPAWN.skill
+SPAWN.modulation
diff --git a/Documentation/Core.SpawnStatic.html b/Documentation/Core.SpawnStatic.html
index d97f129f3..ed21835df 100644
--- a/Documentation/Core.SpawnStatic.html
+++ b/Documentation/Core.SpawnStatic.html
@@ -1997,6 +1997,24 @@ such as position and heading.
Spawns a new static using a given template.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
@@ -2911,6 +2929,39 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
+
+
+
+
+
+
+
+SPAWNSTATIC.heliport_callsign_id
+
+
+
+
+
+
+
+
+
+
+SPAWNSTATIC.heliport_frequency
+
+
+
+
+
+
+
+
+
+
+SPAWNSTATIC.heliport_modulation
+
+
+
@@ -4274,6 +4325,39 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
+
+
+
+
+
+
+
+SPAWNSTATIC.heliport_callsign_id
+
+
+
+
+
+
+
+
+
+
+SPAWNSTATIC.heliport_frequency
+
+
+
+
+
+
+
+
+
+
+SPAWNSTATIC.heliport_modulation
+
+
+
diff --git a/Documentation/Core.Spot.html b/Documentation/Core.Spot.html
index 44086d314..aa8ae4d09 100644
--- a/Documentation/Core.Spot.html
+++ b/Documentation/Core.Spot.html
@@ -1950,7 +1950,7 @@ Controls a network of short range air/missile defense groups.
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -2836,6 +2836,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
+
+
+
+
+
+
+
+SPOT.Target
+
+
+
@@ -4130,6 +4141,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
+
+
+
+
+
+
+
+SPOT.Target
+
+
+
@@ -4186,7 +4208,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
SPOT:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -5663,6 +5685,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
+
+
+
+
+
+
+
+SPOT.Target
+
+
+
diff --git a/Documentation/Core.Zone.html b/Documentation/Core.Zone.html
index c065298fb..cf7d69064 100644
--- a/Documentation/Core.Zone.html
+++ b/Documentation/Core.Zone.html
@@ -2474,7 +2474,7 @@ This class is an abstract BASE class for derived classes, and is not meant to be
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -6423,7 +6423,7 @@ end
ZONE_BASE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Functional.ATC_Ground.html b/Documentation/Functional.ATC_Ground.html
index ab307db46..74c505a73 100644
--- a/Documentation/Functional.ATC_Ground.html
+++ b/Documentation/Functional.ATC_Ground.html
@@ -3869,7 +3869,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
+ #table
ATC_GROUND.Airbases
@@ -4454,7 +4454,7 @@ An airbase can be specified to set the maximum kick speed for.
-
+ #table
ATC_GROUND.Airbases
diff --git a/Documentation/Functional.Artillery.html b/Documentation/Functional.Artillery.html
index 39ee386ad..65be0e78a 100644
--- a/Documentation/Functional.Artillery.html
+++ b/Documentation/Functional.Artillery.html
@@ -3567,7 +3567,7 @@ normandy:Start()
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -15721,7 +15721,7 @@ The illumination bomb will burn for 300 seconds (5 minutes). Assuming a descent
ARTY:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Functional.Designate.html b/Documentation/Functional.Designate.html
index b1059586d..22407e556 100644
--- a/Documentation/Functional.Designate.html
+++ b/Documentation/Functional.Designate.html
@@ -2533,7 +2533,7 @@ Use the method DESIGNATE.SetMission() to
-Send a message of the Task to the Group of the Unit.
+Send a message of the Tasking.Task to the Group of the Unit.
@@ -2669,7 +2669,7 @@ Use the method DESIGNATE.SetMission() to
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -3555,6 +3555,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
+
+
+
+
+
+
+ #table
+DESIGNATE.LaserCodes
+
+
+
@@ -6719,6 +6730,17 @@ Using the menu system, the player can "forget" a designation, so that gradually
+
+
+
+
+
+
+ #table
+DESIGNATE.LaserCodes
+
+
+
@@ -7090,7 +7112,7 @@ Using the menu system, the player can "forget" a designation, so that gradually
DESIGNATE:Message(Message)
-Send a message of the Task to the Group of the Unit.
+Send a message of the Tasking.Task to the Group of the Unit.
@@ -7518,6 +7540,17 @@ Using the menu system, the player can "forget" a designation, so that gradually
+
+
+
+
+
+
+ #table
+DESIGNATE.LaserCodes
+
+
+
@@ -8287,6 +8320,17 @@ Using the menu system, the player can "forget" a designation, so that gradually
+
+
+
+
+
+
+ #table
+DESIGNATE.LaserCodes
+
+
+
@@ -8467,7 +8511,7 @@ Using the menu system, the player can "forget" a designation, so that gradually
DESIGNATE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -9944,6 +9988,17 @@ Using the menu system, the player can "forget" a designation, so that gradually
+
+
+
+
+
+
+ #table
+DESIGNATE.LaserCodes
+
+
+
diff --git a/Documentation/Functional.Detection.html b/Documentation/Functional.Detection.html
index 67532a857..5e225b785 100644
--- a/Documentation/Functional.Detection.html
+++ b/Documentation/Functional.Detection.html
@@ -2941,7 +2941,7 @@ The different values of Unit.Category can be:
DETECTION_AREAS:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -4525,7 +4525,7 @@ The different values of Unit.Category can be:
DETECTION_BASE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -6426,7 +6426,7 @@ The different values of Unit.Category can be:
DETECTION_TYPES:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -8085,7 +8085,7 @@ The different values of Unit.Category can be:
DETECTION_UNITS:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -14192,7 +14192,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
DETECTION_AREAS:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -19138,6 +19138,17 @@ When moose is loading dynamically (for moose class development), tracing is swit
+
+
+
+
+
+
+ #number
+DETECTION_BASE.DetectedItemMax
+
+
+
@@ -19281,6 +19292,17 @@ When moose is loading dynamically (for moose class development), tracing is swit
+
+
+
+
+
+
+ #boolean
+DETECTION_BASE.Locking
+
+
+
@@ -23819,6 +23841,17 @@ zones that reflect cloudy areas where detected units may not be so easily visual
+
+
+
+
+
+
+ #number
+DETECTION_BASE.DetectedItemMax
+
+
+
@@ -23962,6 +23995,17 @@ zones that reflect cloudy areas where detected units may not be so easily visual
+
+
+
+
+
+
+ #boolean
+DETECTION_BASE.Locking
+
+
+
@@ -24062,7 +24106,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
DETECTION_BASE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -25561,6 +25605,17 @@ zones that reflect cloudy areas where detected units may not be so easily visual
+
+
+
+
+
+
+ #number
+DETECTION_BASE.DetectedItemMax
+
+
+
@@ -25704,6 +25759,17 @@ zones that reflect cloudy areas where detected units may not be so easily visual
+
+
+
+
+
+
+ #boolean
+DETECTION_BASE.Locking
+
+
+
@@ -34385,7 +34451,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
DETECTION_TYPES:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -44078,7 +44144,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
DETECTION_UNITS:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Functional.DetectionZones.html b/Documentation/Functional.DetectionZones.html
index c69e24418..a6dbc70de 100644
--- a/Documentation/Functional.DetectionZones.html
+++ b/Documentation/Functional.DetectionZones.html
@@ -2639,7 +2639,7 @@ The different values of Unit.Category can be:
DETECTION_ZONES:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -8898,7 +8898,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
DETECTION_ZONES:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Functional.Fox.html b/Documentation/Functional.Fox.html
index 60ab60569..2ff69d351 100644
--- a/Documentation/Functional.Fox.html
+++ b/Documentation/Functional.Fox.html
@@ -2287,7 +2287,7 @@ fox:Start()
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -6482,7 +6482,7 @@ Don't set the explosion power too big or it will harm the aircraft in the vicini
FOX:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Functional.Mantis.html b/Documentation/Functional.Mantis.html
index 4d493b305..88eb457db 100644
--- a/Documentation/Functional.Mantis.html
+++ b/Documentation/Functional.Mantis.html
@@ -3743,17 +3743,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
-
-
-
-
-
- #table
-MANTIS.AcceptZones
-
-
-
@@ -3787,17 +3776,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
-
-
-
-
-
- #table
-MANTIS.ConflictZones
-
-
-
@@ -3886,17 +3864,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
The ME name of the HQ object
-
-
-
-
-
-
- #table
-MANTIS.RejectZones
-
-
-
@@ -4412,6 +4379,9 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
+
+ switch alarm state RED
+
@@ -4423,9 +4393,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
-self.SAMCheckRanges = {}
-
@@ -8290,17 +8257,6 @@ E.g. `mymantis:SetAdvancedMode(true, 90)`
-
-
-
-
-
-
- #table
-MANTIS.AcceptZones
-
-
-
@@ -8334,17 +8290,6 @@ E.g. `mymantis:SetAdvancedMode(true, 90)`
-
-
-
-
-
-
- #table
-MANTIS.ConflictZones
-
-
-
@@ -8433,17 +8378,6 @@ E.g. `mymantis:SetAdvancedMode(true, 90)`
The ME name of the HQ object
-
-
-
-
-
-
- #table
-MANTIS.RejectZones
-
-
-
@@ -8959,6 +8893,9 @@ E.g. `mymantis:SetAdvancedMode(true, 90)`
+
+ switch alarm state RED
+
@@ -8970,9 +8907,6 @@ E.g. `mymantis:SetAdvancedMode(true, 90)`
-
-self.SAMCheckRanges = {}
-
diff --git a/Documentation/Functional.Movement.html b/Documentation/Functional.Movement.html
index 45c041566..f84a93e82 100644
--- a/Documentation/Functional.Movement.html
+++ b/Documentation/Functional.Movement.html
@@ -2269,20 +2269,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
Field(s)
-
-
-
- #number
-MOVEMENT.AliveUnits
-
-
-
-
- Contains the counter how many units are currently alive.
-
-
-
-
@@ -2513,20 +2499,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
Field(s)
-
-
-
- #number
-MOVEMENT.AliveUnits
-
-
-
-
- Contains the counter how many units are currently alive.
-
-
-
-
diff --git a/Documentation/Functional.RAT.html b/Documentation/Functional.RAT.html
index 22ef115e6..54f65c125 100644
--- a/Documentation/Functional.RAT.html
+++ b/Documentation/Functional.RAT.html
@@ -3472,6 +3472,12 @@ manager:Stop(7200)
Type of terminal to be used when spawning at an airbase.
+
+
+
+
+
+
@@ -4454,7 +4460,7 @@ and any spaces before and after the resulting name are removed.
-
+
@@ -6848,6 +6854,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
Type of terminal to be used when spawning at an airbase.
+
+
+
+
+
+
+
+RAT.type
+
+
+
@@ -14728,6 +14745,17 @@ Initializes the ratcraft array and group menu.
Type of terminal to be used when spawning at an airbase.
+
+
+
+
+
+
+
+RAT.type
+
+
+
@@ -20662,6 +20690,17 @@ This is needed to ensure that Re-SPAWNing only is done for landed AIR Groups.Type of terminal to be used when spawning at an airbase.
+
+
+
+
+
+
+
+RAT.type
+
+
+
diff --git a/Documentation/Functional.Range.html b/Documentation/Functional.Range.html
index 19f165911..abfaa68f2 100644
--- a/Documentation/Functional.Range.html
+++ b/Documentation/Functional.Range.html
@@ -2984,7 +2984,7 @@ The could avoid the lua garbage collection to accidentally/falsely deallocate th
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -11483,7 +11483,7 @@ If a zone is not explicitly specified, the range zone is determined by its locat
RANGE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Functional.Scoring.html b/Documentation/Functional.Scoring.html
index 2ffc4987a..febda2e07 100644
--- a/Documentation/Functional.Scoring.html
+++ b/Documentation/Functional.Scoring.html
@@ -3094,7 +3094,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
+ #boolean
SCORING.penaltyoncoalitionchange
@@ -5614,7 +5614,7 @@ The scale magnifies the scores given to the players.
-
+ #boolean
SCORING.penaltyoncoalitionchange
diff --git a/Documentation/Functional.Suppression.html b/Documentation/Functional.Suppression.html
index bb5690205..2c8e8ae03 100644
--- a/Documentation/Functional.Suppression.html
+++ b/Documentation/Functional.Suppression.html
@@ -2741,7 +2741,7 @@ If no scenery object is near the group the TakeCover event is r
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -10571,7 +10571,7 @@ If the group consists of more than one unit, this referrs to the group strength
SUPPRESSION:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Functional.Warehouse.html b/Documentation/Functional.Warehouse.html
index 48c366a86..0aa86aab4 100644
--- a/Documentation/Functional.Warehouse.html
+++ b/Documentation/Functional.Warehouse.html
@@ -5018,7 +5018,7 @@ end
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -21008,7 +21008,7 @@ this request is used to put the groups back into the warehouse stock.
WAREHOUSE:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Ops.ATIS.html b/Documentation/Ops.ATIS.html
index 951d66173..341e60f24 100644
--- a/Documentation/Ops.ATIS.html
+++ b/Documentation/Ops.ATIS.html
@@ -2670,7 +2670,7 @@ atis:Start()
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -8381,7 +8381,7 @@ Note that the dew point is only an artificial information as DCS does not have a
ATIS:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Ops.Airboss.html b/Documentation/Ops.Airboss.html
index 048a0ad05..4771aecc5 100644
--- a/Documentation/Ops.Airboss.html
+++ b/Documentation/Ops.Airboss.html
@@ -5911,7 +5911,7 @@ If enabled, status and debug text messages will be displayed on the screen. Also
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -11376,7 +11376,7 @@ The true bearing can be obtained by setting the TrueNorth parameter to
-(Optional) Coodinate from which heading is calculated. Default is current carrier position.
+(Optional) Coordinate from which heading is calculated. Default is current carrier position.
@@ -30116,7 +30116,7 @@ If removed flight is the section lead, we try to find a new leader.
AIRBOSS:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -39549,9 +39549,6 @@ When moose is loading dynamically (for moose class development), tracing is swit
-
- Set case of f
-
@@ -39614,6 +39611,20 @@ When moose is loading dynamically (for moose class development), tracing is swit
+AIRBOSS.PlayerData.flag
+
+
+
+
+ Decrease stack/flag. Human player needs to take care himself.
+
+
+
+
+
+
+
+
AIRBOSS.PlayerData.grade
@@ -39767,9 +39778,6 @@ When moose is loading dynamically (for moose class development), tracing is swit
-
- Set section lead of player flight.
-
diff --git a/Documentation/Ops.CSAR.html b/Documentation/Ops.CSAR.html
index 0fbd1b590..e290bdef8 100644
--- a/Documentation/Ops.CSAR.html
+++ b/Documentation/Ops.CSAR.html
@@ -2513,6 +2513,12 @@ Create a late-activated single infantry unit as template in the mission editor a
+
+
+
+
+
+
@@ -2784,7 +2790,7 @@ Create a late-activated single infantry unit as template in the mission editor a
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -4282,25 +4288,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- #table
+
CSAR.downedPilots
-
- Replacement woundedGroups
-
-
-
-
-
-
-
- #number
-CSAR.downedpilotcounter
-
-
-
@@ -4399,6 +4391,17 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
contain a table for each SAR with all units he has with the original names
+
+
+
+
+
+
+
+CSAR.index
+
+
+
@@ -4607,20 +4610,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
-
-
-
- #number
-CSAR.rescuedpilots
-
-
-
-
- counter for saved pilots
-
-
-
@@ -4646,20 +4635,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
-
-
-
- #number
-CSAR.rescues
-
-
-
-
- counter for successful rescue landings at FARP/AFB/MASH
-
-
-
@@ -9629,25 +9604,11 @@ callsigns from playername or group name.
- #table
+
CSAR.downedPilots
-
- Replacement woundedGroups
-
-
-
-
-
-
-
- #number
-CSAR.downedpilotcounter
-
-
-
@@ -9746,6 +9707,17 @@ callsigns from playername or group name.
contain a table for each SAR with all units he has with the original names
+
+
+
+
+
+
+
+CSAR.index
+
+
+
@@ -9954,20 +9926,6 @@ callsigns from playername or group name.
-
-
-
-
- #number
-CSAR.rescuedpilots
-
-
-
-
- counter for saved pilots
-
-
-
@@ -9993,20 +9951,6 @@ callsigns from playername or group name.
-
-
-
-
- #number
-CSAR.rescues
-
-
-
-
- counter for successful rescue landings at FARP/AFB/MASH
-
-
-
@@ -10175,7 +10119,7 @@ callsigns from playername or group name.
CSAR:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -12077,25 +12021,11 @@ callsigns from playername or group name.
- #table
+
CSAR.downedPilots
-
- Replacement woundedGroups
-
-
-
-
-
-
-
- #number
-CSAR.downedpilotcounter
-
-
-
@@ -12194,6 +12124,17 @@ callsigns from playername or group name.
contain a table for each SAR with all units he has with the original names
+
+
+
+
+
+
+
+CSAR.index
+
+
+
@@ -12402,20 +12343,6 @@ callsigns from playername or group name.
-
-
-
-
- #number
-CSAR.rescuedpilots
-
-
-
-
- counter for saved pilots
-
-
-
@@ -12441,20 +12368,6 @@ callsigns from playername or group name.
-
-
-
-
- #number
-CSAR.rescues
-
-
-
-
- counter for successful rescue landings at FARP/AFB/MASH
-
-
-
diff --git a/Documentation/Ops.CTLD.html b/Documentation/Ops.CTLD.html
index fbc450e6e..167a470d3 100644
--- a/Documentation/Ops.CTLD.html
+++ b/Documentation/Ops.CTLD.html
@@ -3316,7 +3316,7 @@ If you use units build by multiple templates, they will effectively double on lo
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -7088,17 +7088,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
Field(s)
-
-
-
- #number
-CTLD.CargoCounter
-
-
-
-
-
-
@@ -7229,7 +7218,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- #table
+
CTLD.DroppedTroops
@@ -7254,28 +7243,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- #number
-CTLD.Engineers
-
-
-
-use as counter
-
-
-
-
-
-
-
- #table
CTLD.EngineersInField
-
-holds #CTLD_ENGINEERING objects
-
@@ -7307,7 +7279,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- #table
+
CTLD.FreeFMFrequencies
@@ -7329,14 +7301,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- #table
+
CTLD.FreeVHFFrequencies
-
- Beacons
-
@@ -7462,14 +7431,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- #table
+
CTLD.PilotGroups
-
- tables
-
@@ -7564,17 +7530,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
-
-
-
-
-
- #number
-CTLD.TroopCounter
-
-
-
@@ -7947,7 +7902,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- time to repair a unit/group
+ noob catch
@@ -14771,17 +14726,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
Field(s)
-
-
-
- #number
-CTLD.CargoCounter
-
-
-
-
-
-
@@ -14912,7 +14856,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- #table
+
CTLD.DroppedTroops
@@ -14937,28 +14881,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- #number
-CTLD.Engineers
-
-
-
-use as counter
-
-
-
-
-
-
-
- #table
CTLD.EngineersInField
-
-holds #CTLD_ENGINEERING objects
-
@@ -14990,7 +14917,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- #table
+
CTLD.FreeFMFrequencies
@@ -15012,14 +14939,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- #table
+
CTLD.FreeVHFFrequencies
-
- Beacons
-
@@ -15145,14 +15069,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- #table
+
CTLD.PilotGroups
-
- tables
-
@@ -15247,17 +15168,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
-
-
-
-
-
- #number
-CTLD.TroopCounter
-
-
-
@@ -15630,7 +15540,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- time to repair a unit/group
+ noob catch
@@ -15804,7 +15714,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
CTLD:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -17207,17 +17117,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
Field(s)
-
-
-
- #number
-CTLD.CargoCounter
-
-
-
-
-
-
@@ -17348,7 +17247,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- #table
+
CTLD.DroppedTroops
@@ -17373,28 +17272,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- #number
-CTLD.Engineers
-
-
-
-use as counter
-
-
-
-
-
-
-
- #table
CTLD.EngineersInField
-
-holds #CTLD_ENGINEERING objects
-
@@ -17426,7 +17308,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- #table
+
CTLD.FreeFMFrequencies
@@ -17448,14 +17330,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- #table
+
CTLD.FreeVHFFrequencies
-
- Beacons
-
@@ -17581,14 +17460,11 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- #table
+
CTLD.PilotGroups
-
- tables
-
@@ -17683,17 +17559,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
-
-
-
-
-
- #number
-CTLD.TroopCounter
-
-
-
@@ -18066,7 +17931,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
- time to repair a unit/group
+ noob catch
@@ -22076,17 +21941,6 @@ When moose is loading dynamically (for moose class development), tracing is swit
Can transport crate.
-
-
-
-
-
-
- #number
-CTLD.UnitCapabilities.length
-
-
-
@@ -22262,17 +22116,6 @@ When moose is loading dynamically (for moose class development), tracing is swit
Flag for direct loading.
-
-
-
-
-
-
-
-CTLD_CARGO.Mark
-
-
-
@@ -22422,17 +22265,6 @@ When moose is loading dynamically (for moose class development), tracing is swit
Flag for direct loading.
-
-
-
-
-
-
-
-CTLD_CARGO.Mark
-
-
-
@@ -26043,6 +25875,17 @@ When moose is loading dynamically (for moose class development), tracing is swit
+
+
+
+
+
+
+ Core.Point#COORDINATE
+CTLD_ENGINEERING.currwpt
+
+
+
@@ -26696,6 +26539,17 @@ When moose is loading dynamically (for moose class development), tracing is swit
+
+
+
+
+
+
+ Core.Point#COORDINATE
+CTLD_ENGINEERING.currwpt
+
+
+
diff --git a/Documentation/Ops.RecoveryTanker.html b/Documentation/Ops.RecoveryTanker.html
index 386cf06f9..a6e16595b 100644
--- a/Documentation/Ops.RecoveryTanker.html
+++ b/Documentation/Ops.RecoveryTanker.html
@@ -2592,7 +2592,7 @@ If enabled, text messages about the tanker status will be displayed on screen an
RECOVERYTANKER:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -7427,7 +7427,7 @@ The group name is the one specified in the RECO
RECOVERYTANKER:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Ops.RescueHelo.html b/Documentation/Ops.RescueHelo.html
index 7c6d59b78..4c01f8c0a 100644
--- a/Documentation/Ops.RescueHelo.html
+++ b/Documentation/Ops.RescueHelo.html
@@ -2422,7 +2422,7 @@ If enabled, text messages about the helo status will be displayed on screen and
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -6542,7 +6542,7 @@ The group name is the one specified in the RESCUEHE
RESCUEHELO:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Tasking.DetectionManager.html b/Documentation/Tasking.DetectionManager.html
index e1ddef8da..2facd1a1b 100644
--- a/Documentation/Tasking.DetectionManager.html
+++ b/Documentation/Tasking.DetectionManager.html
@@ -1886,7 +1886,7 @@ If an ad-hoc report is requested, use the method
DETECTION_MANAGER:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -4043,7 +4043,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
DETECTION_MANAGER:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Tasking.Mission.html b/Documentation/Tasking.Mission.html
index 2b030c07b..8d1e223fe 100644
--- a/Documentation/Tasking.Mission.html
+++ b/Documentation/Tasking.Mission.html
@@ -1807,7 +1807,7 @@ structure managing the tasks of the mission.
-Register a Task to be completed within the Tasking.Mission.
+Register a Tasking.Task to be completed within the Tasking.Mission.
@@ -1867,7 +1867,7 @@ structure managing the tasks of the mission.
-Return the next Task ID to be completed within the Tasking.Mission.
+Return the next Tasking.Task ID to be completed within the Tasking.Mission.
@@ -2161,7 +2161,7 @@ structure managing the tasks of the mission.
-Removes a Task to be completed within the Tasking.Mission.
+Removes a Tasking.Task to be completed within the Tasking.Mission.
@@ -2301,7 +2301,7 @@ structure managing the tasks of the mission.
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
@@ -3328,10 +3328,10 @@ If the Unit is part of a Task in the Mission, true is returned.
MISSION:AddTask(Task)
-Register a Task to be completed within the Tasking.Mission.
+Register a Tasking.Task to be completed within the Tasking.Mission.
-Note that there can be multiple Tasks registered to be completed.
+
Note that there can be multiple Tasking.Tasks registered to be completed.
Each Task can be set a certain Goals. The Mission will not be completed until all Goals are reached.
@@ -3350,7 +3350,7 @@ Each Task can be set a certain Goals. The Mission will not be completed until al
-is the Task object.
+is the Tasking.Task object.
@@ -3703,7 +3703,7 @@ If the Unit is part of a Task in the Mission, true is returned.
MISSION:GetNextTaskID(Task)
-Return the next Task ID to be completed within the Tasking.Mission.
+Return the next Tasking.Task ID to be completed within the Tasking.Mission.
@@ -3721,7 +3721,7 @@ If the Unit is part of a Task in the Mission, true is returned.
-is the Task object.
+is the Tasking.Task object.
@@ -3894,7 +3894,7 @@ If the Unit is part of a Task in the Mission, true is returned.
-The Name of the Task within the Tasking.Mission.
+The Name of the Tasking.Task within the Tasking.Mission.
@@ -3985,7 +3985,7 @@ If the Unit is part of a Task in the Mission, true is returned.
-{TASK,...} Structure of TASKS with the TASK number as the key.
+{TASK,...} Structure of TASKS with the Tasking.Task#TASK number as the key.
@@ -4680,7 +4680,7 @@ If the Unit is part of a Task in the Mission, true is returned.
-String indicating the mission briefing to be shown when a player joins a CLIENT.
+String indicating the mission briefing to be shown when a player joins a Wrapper.Client#CLIENT.
@@ -5899,10 +5899,10 @@ If the Unit is part of a Task in the Mission, true is returned.
MISSION:RemoveTask(Task)
-Removes a Task to be completed within the Tasking.Mission.
+Removes a Tasking.Task to be completed within the Tasking.Mission.
-Note that there can be multiple Tasks registered to be completed.
+
Note that there can be multiple Tasking.Tasks registered to be completed.
Each Task can be set a certain Goals. The Mission will not be completed until all Goals are reached.
@@ -5921,7 +5921,7 @@ Each Task can be set a certain Goals. The Mission will not be completed until al
-is the Task object.
+is the Tasking.Task object.
@@ -6665,7 +6665,7 @@ Each Task can be set a certain Goals. The Mission will not be completed until al
MISSION:AddProcess(From, Event, Process, ReturnEvents)
-Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
+Set the default #FSM_PROCESS template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task.
diff --git a/Documentation/Tasking.Task.html b/Documentation/Tasking.Task.html
index a73d99591..769d6e601 100644
--- a/Documentation/Tasking.Task.html
+++ b/Documentation/Tasking.Task.html
@@ -1649,7 +1649,7 @@ So a mission can be much more than just shoot stuff ... It can be a combination
A mission can be in a specific state during the simulation run. For more information about these states, please check the Tasking.Mission section.
-To achieve the mission goal, a mission administers Tasking.Tasks that are set to achieve the mission goal by the human players.
+
To achieve the mission goal, a mission administers #TASKs that are set to achieve the mission goal by the human players.
Each of these tasks can be dynamically created using a task dispatcher, or coded by the mission designer.
Each mission has a separate Mission Menu, that focuses on the administration of these tasks.
@@ -1754,7 +1754,7 @@ or to load/unload cargo.

-When we take back the command center menu, you see two addtional Assign Task menu items.
+
When we take back the command center menu, you see two additional Assign Task menu items.
The menu Assign Task On will automatically allocate a task to the player.
After the selection of this menu, the menu will change into Assign Task Off,
and will need to be selected again by the player to switch of the automatic task assignment.
@@ -1804,7 +1804,7 @@ The scoring is fully flexible, and different levels of awarding can be provided
The state completion is by default set to Success, if the goals of the task have been reached, but can be overruled by a goal method.
-Depending on the tactical situation, a task can be Cancelled by the mission governer.
+
Depending on the tactical situation, a task can be Cancelled by the mission governor.
It is actually the mission designer who has the flexibility to decide at which conditions a task would be set to Success, Failed or Cancelled.
This decision all depends on the task goals, and the phase/evolution of the task conditions that would accomplish the goals.
@@ -1813,16 +1813,16 @@ the task goal could be set to Failed, or .. Cancelled
However, it could very well be also acceptable that the task would be flagged as Success.
The tasking mechanism governs beside the progress also a scoring mechanism, and in case of goal completion without any active pilot involved
-in the execution of the task, could result in a Success task completion status, but no score would be awared, as there were no players involved.
+in the execution of the task, could result in a Success task completion status, but no score would be awarded, as there were no players involved.
These different completion states are important for the mission designer to reflect scoring to a player.
A success could mean a positive score to be given, while a failure could mean a negative score or penalties to be awarded.
-Author: FlightControl
+Author(s): FlightControl
-Contributions:
+Contribution(s):
@@ -1924,7 +1924,7 @@ You can do this with the OnAfterGoal method.
function Task:OnAfterGoal()
if condition == true then
- self:Success() -- This will flag the task to Succcess when the condition is true.
+ self:Success() -- This will flag the task to Success when the condition is true.
else
if condition2 == true and condition3 == true then
self:Fail() -- This will flag the task to Failed, when condition2 and condition3 would be true.
@@ -2002,13 +2002,13 @@ but can separately be modified later in your mission using the
-Assign the Task to a Wrapper.Group.
+Assign the #TASK to a Wrapper.Group.
-Assign the Task to an alive Wrapper.Unit.
+Assign the #TASK to an alive Wrapper.Unit.
@@ -2020,7 +2020,7 @@ but can separately be modified later in your mission using the
-Clear the Wrapper.Group assignment from the Task.
+Clear the Wrapper.Group assignment from the #TASK.
@@ -2092,7 +2092,7 @@ but can separately be modified later in your mission using the
-Gets the Task briefing.
+Gets the #TASK briefing.
@@ -2146,7 +2146,7 @@ but can separately be modified later in your mission using the
-Get the default or currently assigned Process template with key ProcessName.
+Get the default or currently assigned Core.Fsm#FSM_PROCESS template with key ProcessName.
@@ -2158,19 +2158,19 @@ but can separately be modified later in your mission using the
-Gets the FiniteStateMachine of Task with key TaskWrapper.Unit
+Gets the FiniteStateMachine of #TASK with key Wrapper.Unit.
-Gets the Task status.
+Gets the #TASK status.
-Returns the Task briefing.
+Returns the #TASK briefing.
@@ -2188,7 +2188,7 @@ but can separately be modified later in your mission using the
-Returns the Task name.
+Returns the #TASK name.
@@ -2212,7 +2212,7 @@ but can separately be modified later in your mission using the
-Returns if the Task has still alive and assigned Units.
+Returns if the #TASK has still alive and assigned Units.
@@ -2224,7 +2224,7 @@ but can separately be modified later in your mission using the
-Checks if there is a FiniteStateMachine assigned to TaskWrapper.Unit for Task
+Checks if there is a FiniteStateMachine assigned to Wrapper.Unit for #TASK.
@@ -2236,55 +2236,55 @@ but can separately be modified later in your mission using the
-Returns if the Task is assigned to the Group.
+Returns if the #TASK is assigned to the Group.
-Is the Task status Aborted.
+Is the #TASK status Aborted.
-Is the Task status Assigned.
+Is the #TASK status Assigned.
-Is the Task status Cancelled.
+Is the #TASK status Cancelled.
-Is the Task status Failed.
+Is the #TASK status Failed.
-Is the Task status Hold.
+Is the #TASK status Hold.
-Is the Task status Planned.
+Is the #TASK status Planned.
-Is the Task status Replanned.
+Is the #TASK status Replanned.
-Is the Task status Success.
+Is the #TASK status Success.
@@ -2338,7 +2338,7 @@ but can separately be modified later in your mission using the
-Send a message of the Task to the assigned Wrapper.Groups.
+Send a message of the #TASK to the assigned Wrapper.Groups.
@@ -2386,7 +2386,7 @@ but can separately be modified later in your mission using the
-Remove the menu option of the Task for a Wrapper.Group.
+Remove the menu option of the #TASK for a Wrapper.Group.
@@ -2404,19 +2404,19 @@ but can separately be modified later in your mission using the
-Remove the assigned menu option of the Task for a Wrapper.Group.
+Remove the assigned menu option of the #TASK for a Wrapper.Group.
-Remove the menu options of the Task to all the groups in the SetGroup.
+Remove the menu options of the #TASK to all the groups in the SetGroup.
-Remove FiniteStateMachines from Task with key TaskWrapper.Unit
+Remove FiniteStateMachines from #TASK with key Wrapper.Unit.
@@ -2452,7 +2452,7 @@ but can separately be modified later in your mission using the
-Send the briefng message of the Task to the assigned Wrapper.Groups.
+Send the briefing message of the #TASK to the assigned Wrapper.Groups.
@@ -2464,13 +2464,13 @@ but can separately be modified later in your mission using the
-Set the assigned menu options of the Task.
+Set the assigned menu options of the #TASK.
-Sets a Task briefing.
+Sets a #TASK briefing.
@@ -2500,7 +2500,7 @@ but can separately be modified later in your mission using the
-Set Wrapper.Group assigned to the Task.
+Set Wrapper.Group assigned to the #TASK.
@@ -2512,7 +2512,7 @@ but can separately be modified later in your mission using the
-Set the menu options of the Task to all the groups in the SetGroup.
+Set the menu options of the #TASK to all the groups in the SetGroup.
@@ -2530,7 +2530,7 @@ but can separately be modified later in your mission using the
-Set the planned menu option of the Task.
+Set the planned menu option of the #TASK.
@@ -2554,13 +2554,13 @@ but can separately be modified later in your mission using the
-Add a FiniteStateMachine to Task with key TaskWrapper.Unit
+Add a FiniteStateMachine to #TASK with key Wrapper.Unit.
-Sets the TimeOut for the Task.
+Sets the TimeOut for the #TASK.
@@ -2578,49 +2578,49 @@ but can separately be modified later in your mission using the
-Sets a Task to status Aborted.
+Sets a #TASK to status Aborted.
-Sets a Task to status Assigned.
+Sets a #TASK to status Assigned.
-Sets a Task to status Cancelled.
+Sets a #TASK to status Cancelled.
-Sets a Task to status Failed.
+Sets a #TASK to status Failed.
-Sets a Task to status Hold.
+Sets a #TASK to status Hold.
-Sets a Task to status Planned.
+Sets a #TASK to status Planned.
-Sets a Task to status Replanned.
+Sets a #TASK to status Replanned.
-Sets a Task to status Success.
+Sets a #TASK to status Success.
@@ -2692,19 +2692,19 @@ but can separately be modified later in your mission using the
-UnAssign the Task from a Wrapper.Group.
+UnAssign the #TASK from a Wrapper.Group.
-UnAssign the Task from the Wrapper.Groups.
+UnAssign the #TASK from the Wrapper.Groups.
-UnAssign the Task from an alive Wrapper.Unit.
+UnAssign the #TASK from an alive Wrapper.Unit.
@@ -3222,7 +3222,7 @@ but can separately be modified later in your mission using the
TASK:AssignToGroup(TaskGroup)
-Assign the Task to a Wrapper.Group.
+Assign the #TASK to a Wrapper.Group.
@@ -3264,7 +3264,7 @@ but can separately be modified later in your mission using the
TASK:AssignToUnit(TaskUnit)
-Assign the Task to an alive Wrapper.Unit.
+Assign the #TASK to an alive Wrapper.Unit.
@@ -3328,7 +3328,7 @@ but can separately be modified later in your mission using the
TASK:ClearGroupAssignment(TaskGroup)
-Clear the Wrapper.Group assignment from the Task.
+Clear the Wrapper.Group assignment from the #TASK.
@@ -3439,8 +3439,8 @@ but can separately be modified later in your mission using the
- TODO: Obscolete?
-- Fail processes from Task with key Wrapper.Unit
+
TODO: Obsolete?
+- Fail processes from #TASK with key Wrapper.Unit.
@param #TASK self
@param #string TaskUnitName
@return #TASK self
@@ -3473,7 +3473,7 @@ but can separately be modified later in your mission using the
TASK:GetBriefing()
-Gets the Task briefing.
+Gets the #TASK briefing.
@@ -3743,7 +3743,7 @@ but can separately be modified later in your mission using the
TASK:GetProcessTemplate(ProcessName)
-Get the default or currently assigned Process template with key ProcessName.
+Get the default or currently assigned Core.Fsm#FSM_PROCESS template with key ProcessName.
@@ -3815,7 +3815,7 @@ but can separately be modified later in your mission using the
TASK:GetStateMachine(TaskUnit)
-Gets the FiniteStateMachine of Task with key TaskWrapper.Unit
+Gets the FiniteStateMachine of #TASK with key Wrapper.Unit.
@@ -3857,7 +3857,7 @@ but can separately be modified later in your mission using the
TASK:GetStateString()
-Gets the Task status.
+Gets the #TASK status.
@@ -3876,7 +3876,7 @@ but can separately be modified later in your mission using the
TASK:GetTaskBriefing()
-Returns the Task briefing.
+Returns the #TASK briefing.
@@ -3990,7 +3990,7 @@ but can separately be modified later in your mission using the
TASK:GetTaskName()
-Returns the Task name.
+Returns the #TASK name.
@@ -4137,7 +4137,7 @@ but can separately be modified later in your mission using the
TASK:HasAliveUnits()
-Returns if the Task has still alive and assigned Units.
+Returns if the #TASK has still alive and assigned Units.
@@ -4209,7 +4209,7 @@ but can separately be modified later in your mission using the
TASK:HasStateMachine(TaskUnit)
-Checks if there is a FiniteStateMachine assigned to TaskWrapper.Unit for Task
+Checks if there is a FiniteStateMachine assigned to Wrapper.Unit for #TASK.
@@ -4294,7 +4294,7 @@ but can separately be modified later in your mission using the
TASK:IsGroupAssigned(TaskGroup)
-Returns if the Task is assigned to the Group.
+Returns if the #TASK is assigned to the Group.
@@ -4336,7 +4336,7 @@ but can separately be modified later in your mission using the
TASK:IsStateAborted()
-Is the Task status Aborted.
+Is the #TASK status Aborted.
@@ -4355,7 +4355,7 @@ but can separately be modified later in your mission using the
TASK:IsStateAssigned()
-Is the Task status Assigned.
+Is the #TASK status Assigned.
@@ -4374,7 +4374,7 @@ but can separately be modified later in your mission using the
TASK:IsStateCancelled()
-Is the Task status Cancelled.
+Is the #TASK status Cancelled.
@@ -4393,7 +4393,7 @@ but can separately be modified later in your mission using the
TASK:IsStateFailed()
-Is the Task status Failed.
+Is the #TASK status Failed.
@@ -4412,7 +4412,7 @@ but can separately be modified later in your mission using the
TASK:IsStateHold()
-Is the Task status Hold.
+Is the #TASK status Hold.
@@ -4431,7 +4431,7 @@ but can separately be modified later in your mission using the
TASK:IsStatePlanned()
-Is the Task status Planned.
+Is the #TASK status Planned.
@@ -4450,7 +4450,7 @@ but can separately be modified later in your mission using the
TASK:IsStateReplanned()
-Is the Task status Replanned.
+Is the #TASK status Replanned.
@@ -4469,7 +4469,7 @@ but can separately be modified later in your mission using the
TASK:IsStateSuccess()
-Is the Task status Success.
+Is the #TASK status Success.
@@ -4713,7 +4713,7 @@ If the Unit is part of the Task, true is returned.
TASK:MessageToGroups(Message)
-Send a message of the Task to the assigned Wrapper.Groups.
+Send a message of the #TASK to the assigned Wrapper.Groups.
@@ -5146,7 +5146,7 @@ If the Unit is part of the Task, true is returned.
TASK:RefreshMenus(TaskGroup, MenuTime)
-Remove the menu option of the Task for a Wrapper.Group.
+Remove the menu option of the #TASK for a Wrapper.Group.
@@ -5300,7 +5300,7 @@ If the Unit is part of the Task, true is returned.
TASK:RemoveAssignedMenuForGroup(TaskGroup, MenuTime)
-Remove the assigned menu option of the Task for a Wrapper.Group.
+Remove the assigned menu option of the #TASK for a Wrapper.Group.
@@ -5353,7 +5353,7 @@ If the Unit is part of the Task, true is returned.
TASK:RemoveMenu(MenuTime)
-Remove the menu options of the Task to all the groups in the SetGroup.
+Remove the menu options of the #TASK to all the groups in the SetGroup.
@@ -5395,7 +5395,7 @@ If the Unit is part of the Task, true is returned.
TASK:RemoveStateMachine(TaskUnit)
-Remove FiniteStateMachines from Task with key TaskWrapper.Unit
+Remove FiniteStateMachines from #TASK with key Wrapper.Unit.
@@ -5636,7 +5636,7 @@ If the Unit is part of the Task, true is returned.
TASK:SendBriefingToAssignedGroups()
-Send the briefng message of the Task to the assigned Wrapper.Groups.
+Send the briefing message of the #TASK to the assigned Wrapper.Groups.
@@ -5686,7 +5686,7 @@ If the Unit is part of the Task, true is returned.
TASK:SetAssignedMenuForGroup(TaskGroup, MenuTime)
-Set the assigned menu options of the Task.
+Set the assigned menu options of the #TASK.
@@ -5739,7 +5739,7 @@ If the Unit is part of the Task, true is returned.
TASK:SetBriefing(TaskBriefing)
-Sets a Task briefing.
+Sets a #TASK briefing.
@@ -5917,7 +5917,7 @@ If the Unit is part of the Task, true is returned.
TASK:SetGroupAssigned(TaskGroup)
-Set Wrapper.Group assigned to the Task.
+Set Wrapper.Group assigned to the #TASK.
@@ -5990,7 +5990,7 @@ If the Unit is part of the Task, true is returned.
TASK:SetMenu(MenuTime)
-Set the menu options of the Task to all the groups in the SetGroup.
+Set the menu options of the #TASK to all the groups in the SetGroup.
@@ -6115,7 +6115,7 @@ If the Unit is part of the Task, true is returned.
TASK:SetPlannedMenuForGroup(TaskGroup, MenuText, MenuTime)
-Set the planned menu option of the Task.
+Set the planned menu option of the #TASK.
@@ -6385,7 +6385,7 @@ If the Unit is part of the Task, true is returned.
TASK:SetStateMachine(TaskUnit, Fsm)
-Add a FiniteStateMachine to Task with key TaskWrapper.Unit
+Add a FiniteStateMachine to #TASK with key Wrapper.Unit.
@@ -6438,10 +6438,10 @@ If the Unit is part of the Task, true is returned.
TASK:SetTimeOut(Timer)
-Sets the TimeOut for the Task.
+Sets the TimeOut for the #TASK.
-If Task stayed planned for longer than TimeOut, it gets into Cancelled status.
+If #TASK stayed planned for longer than TimeOut, it gets into Cancelled status.
@@ -6558,7 +6558,7 @@ If the Unit is part of the Task, true is returned.
TASK:StateAborted()
-Sets a Task to status Aborted.
+Sets a #TASK to status Aborted.
@@ -6577,7 +6577,7 @@ If the Unit is part of the Task, true is returned.
TASK:StateAssigned()
-Sets a Task to status Assigned.
+Sets a #TASK to status Assigned.
@@ -6596,7 +6596,7 @@ If the Unit is part of the Task, true is returned.
TASK:StateCancelled()
-Sets a Task to status Cancelled.
+Sets a #TASK to status Cancelled.
@@ -6615,7 +6615,7 @@ If the Unit is part of the Task, true is returned.
TASK:StateFailed()
-Sets a Task to status Failed.
+Sets a #TASK to status Failed.
@@ -6634,7 +6634,7 @@ If the Unit is part of the Task, true is returned.
TASK:StateHold()
-Sets a Task to status Hold.
+Sets a #TASK to status Hold.
@@ -6653,7 +6653,7 @@ If the Unit is part of the Task, true is returned.
TASK:StatePlanned()
-Sets a Task to status Planned.
+Sets a #TASK to status Planned.
@@ -6672,7 +6672,7 @@ If the Unit is part of the Task, true is returned.
TASK:StateReplanned()
-Sets a Task to status Replanned.
+Sets a #TASK to status Replanned.
@@ -6691,7 +6691,7 @@ If the Unit is part of the Task, true is returned.
TASK:StateSuccess()
-Sets a Task to status Success.
+Sets a #TASK to status Success.
@@ -6732,7 +6732,7 @@ If the Unit is part of the Task, true is returned.
TASK:UnAssignFromGroup(TaskGroup)
-UnAssign the Task from a Wrapper.Group.
+UnAssign the #TASK from a Wrapper.Group.
@@ -6763,7 +6763,7 @@ If the Unit is part of the Task, true is returned.
TASK:UnAssignFromGroups()
-UnAssign the Task from the Wrapper.Groups.
+UnAssign the #TASK from the Wrapper.Groups.
@@ -6782,7 +6782,7 @@ If the Unit is part of the Task, true is returned.
TASK:UnAssignFromUnit(TaskUnit)
-UnAssign the Task from an alive Wrapper.Unit.
+UnAssign the #TASK from an alive Wrapper.Unit.
diff --git a/Documentation/Tasking.Task_A2A.html b/Documentation/Tasking.Task_A2A.html
index 53e4d9131..35a8435f2 100644
--- a/Documentation/Tasking.Task_A2A.html
+++ b/Documentation/Tasking.Task_A2A.html
@@ -1917,13 +1917,13 @@ The task is given a name and a briefing, that is used in the menu structure and
-Assign the Task to a Wrapper.Group.
+Assign the #TASK to a Wrapper.Group.
-Assign the Task to an alive Wrapper.Unit.
+Assign the #TASK to an alive Wrapper.Unit.
@@ -1935,7 +1935,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Clear the Wrapper.Group assignment from the Task.
+Clear the Wrapper.Group assignment from the #TASK.
@@ -2007,7 +2007,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Gets the Task briefing.
+Gets the #TASK briefing.
@@ -2061,7 +2061,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Get the default or currently assigned Process template with key ProcessName.
+Get the default or currently assigned Core.Fsm#FSM_PROCESS template with key ProcessName.
@@ -2073,19 +2073,19 @@ The task is given a name and a briefing, that is used in the menu structure and
-Gets the FiniteStateMachine of Task with key TaskWrapper.Unit
+Gets the FiniteStateMachine of #TASK with key Wrapper.Unit.
-Gets the Task status.
+Gets the #TASK status.
-Returns the Task briefing.
+Returns the #TASK briefing.
@@ -2103,7 +2103,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Returns the Task name.
+Returns the #TASK name.
@@ -2127,7 +2127,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Returns if the Task has still alive and assigned Units.
+Returns if the #TASK has still alive and assigned Units.
@@ -2139,7 +2139,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Checks if there is a FiniteStateMachine assigned to TaskWrapper.Unit for Task
+Checks if there is a FiniteStateMachine assigned to Wrapper.Unit for #TASK.
@@ -2151,55 +2151,55 @@ The task is given a name and a briefing, that is used in the menu structure and
-Returns if the Task is assigned to the Group.
+Returns if the #TASK is assigned to the Group.
-Is the Task status Aborted.
+Is the #TASK status Aborted.
-Is the Task status Assigned.
+Is the #TASK status Assigned.
-Is the Task status Cancelled.
+Is the #TASK status Cancelled.
-Is the Task status Failed.
+Is the #TASK status Failed.
-Is the Task status Hold.
+Is the #TASK status Hold.
-Is the Task status Planned.
+Is the #TASK status Planned.
-Is the Task status Replanned.
+Is the #TASK status Replanned.
-Is the Task status Success.
+Is the #TASK status Success.
@@ -2253,7 +2253,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Send a message of the Task to the assigned Wrapper.Groups.
+Send a message of the #TASK to the assigned Wrapper.Groups.
@@ -2301,7 +2301,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Remove the menu option of the Task for a Wrapper.Group.
+Remove the menu option of the #TASK for a Wrapper.Group.
@@ -2319,19 +2319,19 @@ The task is given a name and a briefing, that is used in the menu structure and
-Remove the assigned menu option of the Task for a Wrapper.Group.
+Remove the assigned menu option of the #TASK for a Wrapper.Group.
-Remove the menu options of the Task to all the groups in the SetGroup.
+Remove the menu options of the #TASK to all the groups in the SetGroup.
-Remove FiniteStateMachines from Task with key TaskWrapper.Unit
+Remove FiniteStateMachines from #TASK with key Wrapper.Unit.
@@ -2367,7 +2367,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Send the briefng message of the Task to the assigned Wrapper.Groups.
+Send the briefing message of the #TASK to the assigned Wrapper.Groups.
@@ -2379,13 +2379,13 @@ The task is given a name and a briefing, that is used in the menu structure and
-Set the assigned menu options of the Task.
+Set the assigned menu options of the #TASK.
-Sets a Task briefing.
+Sets a #TASK briefing.
@@ -2415,7 +2415,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Set Wrapper.Group assigned to the Task.
+Set Wrapper.Group assigned to the #TASK.
@@ -2427,7 +2427,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Set the menu options of the Task to all the groups in the SetGroup.
+Set the menu options of the #TASK to all the groups in the SetGroup.
@@ -2445,7 +2445,7 @@ The task is given a name and a briefing, that is used in the menu structure and
TASK_A2A:SetPlannedMenuForGroup(TaskGroup, MenuText, MenuTime)
-Set the planned menu option of the Task.
+Set the planned menu option of the #TASK.
@@ -2469,13 +2469,13 @@ The task is given a name and a briefing, that is used in the menu structure and
-Add a FiniteStateMachine to Task with key TaskWrapper.Unit
+Add a FiniteStateMachine to #TASK with key Wrapper.Unit.
-Sets the TimeOut for the Task.
+Sets the TimeOut for the #TASK.
@@ -2493,49 +2493,49 @@ The task is given a name and a briefing, that is used in the menu structure and
-Sets a Task to status Aborted.
+Sets a #TASK to status Aborted.
-Sets a Task to status Assigned.
+Sets a #TASK to status Assigned.
-Sets a Task to status Cancelled.
+Sets a #TASK to status Cancelled.
-Sets a Task to status Failed.
+Sets a #TASK to status Failed.
-Sets a Task to status Hold.
+Sets a #TASK to status Hold.
-Sets a Task to status Planned.
+Sets a #TASK to status Planned.
-Sets a Task to status Replanned.
+Sets a #TASK to status Replanned.
-Sets a Task to status Success.
+Sets a #TASK to status Success.
@@ -2607,19 +2607,19 @@ The task is given a name and a briefing, that is used in the menu structure and
-UnAssign the Task from a Wrapper.Group.
+UnAssign the #TASK from a Wrapper.Group.
-UnAssign the Task from the Wrapper.Groups.
+UnAssign the #TASK from the Wrapper.Groups.
-UnAssign the Task from an alive Wrapper.Unit.
+UnAssign the #TASK from an alive Wrapper.Unit.
@@ -2819,13 +2819,13 @@ The task is given a name and a briefing, that is used in the menu structure and
-Assign the Task to a Wrapper.Group.
+Assign the #TASK to a Wrapper.Group.
-Assign the Task to an alive Wrapper.Unit.
+Assign the #TASK to an alive Wrapper.Unit.
@@ -2837,7 +2837,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Clear the Wrapper.Group assignment from the Task.
+Clear the Wrapper.Group assignment from the #TASK.
@@ -2909,7 +2909,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Gets the Task briefing.
+Gets the #TASK briefing.
@@ -2963,7 +2963,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Get the default or currently assigned Process template with key ProcessName.
+Get the default or currently assigned Core.Fsm#FSM_PROCESS template with key ProcessName.
@@ -2975,19 +2975,19 @@ The task is given a name and a briefing, that is used in the menu structure and
-Gets the FiniteStateMachine of Task with key TaskWrapper.Unit
+Gets the FiniteStateMachine of #TASK with key Wrapper.Unit.
-Gets the Task status.
+Gets the #TASK status.
-Returns the Task briefing.
+Returns the #TASK briefing.
@@ -3005,7 +3005,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Returns the Task name.
+Returns the #TASK name.
@@ -3029,7 +3029,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Returns if the Task has still alive and assigned Units.
+Returns if the #TASK has still alive and assigned Units.
@@ -3041,7 +3041,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Checks if there is a FiniteStateMachine assigned to TaskWrapper.Unit for Task
+Checks if there is a FiniteStateMachine assigned to Wrapper.Unit for #TASK.
@@ -3053,55 +3053,55 @@ The task is given a name and a briefing, that is used in the menu structure and
-Returns if the Task is assigned to the Group.
+Returns if the #TASK is assigned to the Group.
-Is the Task status Aborted.
+Is the #TASK status Aborted.
-Is the Task status Assigned.
+Is the #TASK status Assigned.
-Is the Task status Cancelled.
+Is the #TASK status Cancelled.
-Is the Task status Failed.
+Is the #TASK status Failed.
-Is the Task status Hold.
+Is the #TASK status Hold.
-Is the Task status Planned.
+Is the #TASK status Planned.
-Is the Task status Replanned.
+Is the #TASK status Replanned.
-Is the Task status Success.
+Is the #TASK status Success.
@@ -3155,7 +3155,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Send a message of the Task to the assigned Wrapper.Groups.
+Send a message of the #TASK to the assigned Wrapper.Groups.
@@ -3203,7 +3203,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Remove the menu option of the Task for a Wrapper.Group.
+Remove the menu option of the #TASK for a Wrapper.Group.
@@ -3221,19 +3221,19 @@ The task is given a name and a briefing, that is used in the menu structure and
TASK_A2A_ENGAGE:RemoveAssignedMenuForGroup(TaskGroup, MenuTime)
-Remove the assigned menu option of the Task for a Wrapper.Group.
+Remove the assigned menu option of the #TASK for a Wrapper.Group.
-Remove the menu options of the Task to all the groups in the SetGroup.
+Remove the menu options of the #TASK to all the groups in the SetGroup.
-Remove FiniteStateMachines from Task with key TaskWrapper.Unit
+Remove FiniteStateMachines from #TASK with key Wrapper.Unit.
@@ -3269,7 +3269,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Send the briefng message of the Task to the assigned Wrapper.Groups.
+Send the briefing message of the #TASK to the assigned Wrapper.Groups.
@@ -3281,13 +3281,13 @@ The task is given a name and a briefing, that is used in the menu structure and
TASK_A2A_ENGAGE:SetAssignedMenuForGroup(TaskGroup, MenuTime)
-Set the assigned menu options of the Task.
+Set the assigned menu options of the #TASK.
-Sets a Task briefing.
+Sets a #TASK briefing.
@@ -3317,7 +3317,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Set Wrapper.Group assigned to the Task.
+Set Wrapper.Group assigned to the #TASK.
@@ -3329,7 +3329,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Set the menu options of the Task to all the groups in the SetGroup.
+Set the menu options of the #TASK to all the groups in the SetGroup.
@@ -3347,7 +3347,7 @@ The task is given a name and a briefing, that is used in the menu structure and
TASK_A2A_ENGAGE:SetPlannedMenuForGroup(TaskGroup, MenuText, MenuTime)
-Set the planned menu option of the Task.
+Set the planned menu option of the #TASK.
@@ -3371,13 +3371,13 @@ The task is given a name and a briefing, that is used in the menu structure and
-Add a FiniteStateMachine to Task with key TaskWrapper.Unit
+Add a FiniteStateMachine to #TASK with key Wrapper.Unit.
-Sets the TimeOut for the Task.
+Sets the TimeOut for the #TASK.
@@ -3395,49 +3395,49 @@ The task is given a name and a briefing, that is used in the menu structure and
-Sets a Task to status Aborted.
+Sets a #TASK to status Aborted.
-Sets a Task to status Assigned.
+Sets a #TASK to status Assigned.
-Sets a Task to status Cancelled.
+Sets a #TASK to status Cancelled.
-Sets a Task to status Failed.
+Sets a #TASK to status Failed.
-Sets a Task to status Hold.
+Sets a #TASK to status Hold.
-Sets a Task to status Planned.
+Sets a #TASK to status Planned.
-Sets a Task to status Replanned.
+Sets a #TASK to status Replanned.
-Sets a Task to status Success.
+Sets a #TASK to status Success.
@@ -3509,19 +3509,19 @@ The task is given a name and a briefing, that is used in the menu structure and
-UnAssign the Task from a Wrapper.Group.
+UnAssign the #TASK from a Wrapper.Group.
-UnAssign the Task from the Wrapper.Groups.
+UnAssign the #TASK from the Wrapper.Groups.
-UnAssign the Task from an alive Wrapper.Unit.
+UnAssign the #TASK from an alive Wrapper.Unit.
@@ -3721,13 +3721,13 @@ The task is given a name and a briefing, that is used in the menu structure and
-Assign the Task to a Wrapper.Group.
+Assign the #TASK to a Wrapper.Group.
-Assign the Task to an alive Wrapper.Unit.
+Assign the #TASK to an alive Wrapper.Unit.
@@ -3739,7 +3739,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Clear the Wrapper.Group assignment from the Task.
+Clear the Wrapper.Group assignment from the #TASK.
@@ -3811,7 +3811,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Gets the Task briefing.
+Gets the #TASK briefing.
@@ -3865,7 +3865,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Get the default or currently assigned Process template with key ProcessName.
+Get the default or currently assigned Core.Fsm#FSM_PROCESS template with key ProcessName.
@@ -3877,19 +3877,19 @@ The task is given a name and a briefing, that is used in the menu structure and
-Gets the FiniteStateMachine of Task with key TaskWrapper.Unit
+Gets the FiniteStateMachine of #TASK with key Wrapper.Unit.
-Gets the Task status.
+Gets the #TASK status.
-Returns the Task briefing.
+Returns the #TASK briefing.
@@ -3907,7 +3907,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Returns the Task name.
+Returns the #TASK name.
@@ -3931,7 +3931,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Returns if the Task has still alive and assigned Units.
+Returns if the #TASK has still alive and assigned Units.
@@ -3943,7 +3943,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Checks if there is a FiniteStateMachine assigned to TaskWrapper.Unit for Task
+Checks if there is a FiniteStateMachine assigned to Wrapper.Unit for #TASK.
@@ -3955,55 +3955,55 @@ The task is given a name and a briefing, that is used in the menu structure and
-Returns if the Task is assigned to the Group.
+Returns if the #TASK is assigned to the Group.
-Is the Task status Aborted.
+Is the #TASK status Aborted.
-Is the Task status Assigned.
+Is the #TASK status Assigned.
-Is the Task status Cancelled.
+Is the #TASK status Cancelled.
-Is the Task status Failed.
+Is the #TASK status Failed.
-Is the Task status Hold.
+Is the #TASK status Hold.
-Is the Task status Planned.
+Is the #TASK status Planned.
-Is the Task status Replanned.
+Is the #TASK status Replanned.
-Is the Task status Success.
+Is the #TASK status Success.
@@ -4057,7 +4057,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Send a message of the Task to the assigned Wrapper.Groups.
+Send a message of the #TASK to the assigned Wrapper.Groups.
@@ -4105,7 +4105,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Remove the menu option of the Task for a Wrapper.Group.
+Remove the menu option of the #TASK for a Wrapper.Group.
@@ -4123,19 +4123,19 @@ The task is given a name and a briefing, that is used in the menu structure and
TASK_A2A_INTERCEPT:RemoveAssignedMenuForGroup(TaskGroup, MenuTime)
-Remove the assigned menu option of the Task for a Wrapper.Group.
+Remove the assigned menu option of the #TASK for a Wrapper.Group.
-Remove the menu options of the Task to all the groups in the SetGroup.
+Remove the menu options of the #TASK to all the groups in the SetGroup.
-Remove FiniteStateMachines from Task with key TaskWrapper.Unit
+Remove FiniteStateMachines from #TASK with key Wrapper.Unit.
@@ -4171,7 +4171,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Send the briefng message of the Task to the assigned Wrapper.Groups.
+Send the briefing message of the #TASK to the assigned Wrapper.Groups.
@@ -4183,13 +4183,13 @@ The task is given a name and a briefing, that is used in the menu structure and
TASK_A2A_INTERCEPT:SetAssignedMenuForGroup(TaskGroup, MenuTime)
-Set the assigned menu options of the Task.
+Set the assigned menu options of the #TASK.
-Sets a Task briefing.
+Sets a #TASK briefing.
@@ -4219,7 +4219,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Set Wrapper.Group assigned to the Task.
+Set Wrapper.Group assigned to the #TASK.
@@ -4231,7 +4231,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Set the menu options of the Task to all the groups in the SetGroup.
+Set the menu options of the #TASK to all the groups in the SetGroup.
@@ -4249,7 +4249,7 @@ The task is given a name and a briefing, that is used in the menu structure and
TASK_A2A_INTERCEPT:SetPlannedMenuForGroup(TaskGroup, MenuText, MenuTime)
-Set the planned menu option of the Task.
+Set the planned menu option of the #TASK.
@@ -4273,13 +4273,13 @@ The task is given a name and a briefing, that is used in the menu structure and
-Add a FiniteStateMachine to Task with key TaskWrapper.Unit
+Add a FiniteStateMachine to #TASK with key Wrapper.Unit.
-Sets the TimeOut for the Task.
+Sets the TimeOut for the #TASK.
@@ -4297,49 +4297,49 @@ The task is given a name and a briefing, that is used in the menu structure and
-Sets a Task to status Aborted.
+Sets a #TASK to status Aborted.
-Sets a Task to status Assigned.
+Sets a #TASK to status Assigned.
-Sets a Task to status Cancelled.
+Sets a #TASK to status Cancelled.
-Sets a Task to status Failed.
+Sets a #TASK to status Failed.
-Sets a Task to status Hold.
+Sets a #TASK to status Hold.
-Sets a Task to status Planned.
+Sets a #TASK to status Planned.
-Sets a Task to status Replanned.
+Sets a #TASK to status Replanned.
-Sets a Task to status Success.
+Sets a #TASK to status Success.
@@ -4411,19 +4411,19 @@ The task is given a name and a briefing, that is used in the menu structure and
-UnAssign the Task from a Wrapper.Group.
+UnAssign the #TASK from a Wrapper.Group.
-UnAssign the Task from the Wrapper.Groups.
+UnAssign the #TASK from the Wrapper.Groups.
-UnAssign the Task from an alive Wrapper.Unit.
+UnAssign the #TASK from an alive Wrapper.Unit.
@@ -4629,13 +4629,13 @@ The task is given a name and a briefing, that is used in the menu structure and
-Assign the Task to a Wrapper.Group.
+Assign the #TASK to a Wrapper.Group.
-Assign the Task to an alive Wrapper.Unit.
+Assign the #TASK to an alive Wrapper.Unit.
@@ -4647,7 +4647,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Clear the Wrapper.Group assignment from the Task.
+Clear the Wrapper.Group assignment from the #TASK.
@@ -4719,7 +4719,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Gets the Task briefing.
+Gets the #TASK briefing.
@@ -4773,7 +4773,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Get the default or currently assigned Process template with key ProcessName.
+Get the default or currently assigned Core.Fsm#FSM_PROCESS template with key ProcessName.
@@ -4785,19 +4785,19 @@ The task is given a name and a briefing, that is used in the menu structure and
-Gets the FiniteStateMachine of Task with key TaskWrapper.Unit
+Gets the FiniteStateMachine of #TASK with key Wrapper.Unit.
-Gets the Task status.
+Gets the #TASK status.
-Returns the Task briefing.
+Returns the #TASK briefing.
@@ -4815,7 +4815,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Returns the Task name.
+Returns the #TASK name.
@@ -4839,7 +4839,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Returns if the Task has still alive and assigned Units.
+Returns if the #TASK has still alive and assigned Units.
@@ -4851,7 +4851,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Checks if there is a FiniteStateMachine assigned to TaskWrapper.Unit for Task
+Checks if there is a FiniteStateMachine assigned to Wrapper.Unit for #TASK.
@@ -4863,55 +4863,55 @@ The task is given a name and a briefing, that is used in the menu structure and
-Returns if the Task is assigned to the Group.
+Returns if the #TASK is assigned to the Group.
-Is the Task status Aborted.
+Is the #TASK status Aborted.
-Is the Task status Assigned.
+Is the #TASK status Assigned.
-Is the Task status Cancelled.
+Is the #TASK status Cancelled.
-Is the Task status Failed.
+Is the #TASK status Failed.
-Is the Task status Hold.
+Is the #TASK status Hold.
-Is the Task status Planned.
+Is the #TASK status Planned.
-Is the Task status Replanned.
+Is the #TASK status Replanned.
-Is the Task status Success.
+Is the #TASK status Success.
@@ -4965,7 +4965,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Send a message of the Task to the assigned Wrapper.Groups.
+Send a message of the #TASK to the assigned Wrapper.Groups.
@@ -5013,7 +5013,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Remove the menu option of the Task for a Wrapper.Group.
+Remove the menu option of the #TASK for a Wrapper.Group.
@@ -5031,19 +5031,19 @@ The task is given a name and a briefing, that is used in the menu structure and
TASK_A2A_SWEEP:RemoveAssignedMenuForGroup(TaskGroup, MenuTime)
-Remove the assigned menu option of the Task for a Wrapper.Group.
+Remove the assigned menu option of the #TASK for a Wrapper.Group.
-Remove the menu options of the Task to all the groups in the SetGroup.
+Remove the menu options of the #TASK to all the groups in the SetGroup.
-Remove FiniteStateMachines from Task with key TaskWrapper.Unit
+Remove FiniteStateMachines from #TASK with key Wrapper.Unit.
@@ -5079,7 +5079,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Send the briefng message of the Task to the assigned Wrapper.Groups.
+Send the briefing message of the #TASK to the assigned Wrapper.Groups.
@@ -5091,13 +5091,13 @@ The task is given a name and a briefing, that is used in the menu structure and
-Set the assigned menu options of the Task.
+Set the assigned menu options of the #TASK.
-Sets a Task briefing.
+Sets a #TASK briefing.
@@ -5127,7 +5127,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Set Wrapper.Group assigned to the Task.
+Set Wrapper.Group assigned to the #TASK.
@@ -5139,7 +5139,7 @@ The task is given a name and a briefing, that is used in the menu structure and
-Set the menu options of the Task to all the groups in the SetGroup.
+Set the menu options of the #TASK to all the groups in the SetGroup.
@@ -5157,7 +5157,7 @@ The task is given a name and a briefing, that is used in the menu structure and
TASK_A2A_SWEEP:SetPlannedMenuForGroup(TaskGroup, MenuText, MenuTime)
-Set the planned menu option of the Task.
+Set the planned menu option of the #TASK.
@@ -5181,13 +5181,13 @@ The task is given a name and a briefing, that is used in the menu structure and
-Add a FiniteStateMachine to Task with key TaskWrapper.Unit
+Add a FiniteStateMachine to #TASK with key Wrapper.Unit.
-Sets the TimeOut for the Task.
+Sets the TimeOut for the #TASK.
@@ -5205,49 +5205,49 @@ The task is given a name and a briefing, that is used in the menu structure and
-Sets a Task to status Aborted.
+Sets a #TASK to status Aborted.
-Sets a Task to status Assigned.
+Sets a #TASK to status Assigned.
-Sets a Task to status Cancelled.
+Sets a #TASK to status Cancelled.
-Sets a Task to status Failed.
+Sets a #TASK to status Failed.
-Sets a Task to status Hold.
+Sets a #TASK to status Hold.
-Sets a Task to status Planned.
+Sets a #TASK to status Planned.
-Sets a Task to status Replanned.
+Sets a #TASK to status Replanned.
-Sets a Task to status Success.
+Sets a #TASK to status Success.
@@ -5319,19 +5319,19 @@ The task is given a name and a briefing, that is used in the menu structure and
-UnAssign the Task from a Wrapper.Group.
+UnAssign the #TASK from a Wrapper.Group.
-UnAssign the Task from the Wrapper.Groups.
+UnAssign the #TASK from the Wrapper.Groups.
-UnAssign the Task from an alive Wrapper.Unit.
+UnAssign the #TASK from an alive Wrapper.Unit.
@@ -6483,7 +6483,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:AssignToGroup(TaskGroup)
-Assign the Task to a Wrapper.Group.
+Assign the #TASK to a Wrapper.Group.
@@ -6525,7 +6525,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:AssignToUnit(TaskUnit)
-Assign the Task to an alive Wrapper.Unit.
+Assign the #TASK to an alive Wrapper.Unit.
@@ -6589,7 +6589,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:ClearGroupAssignment(TaskGroup)
-Clear the Wrapper.Group assignment from the Task.
+Clear the Wrapper.Group assignment from the #TASK.
@@ -6700,8 +6700,8 @@ If the TargetZone parameter is specified, the player will be routed to the cente
- TODO: Obscolete?
-- Fail processes from Task with key Wrapper.Unit
+
TODO: Obsolete?
+- Fail processes from #TASK with key Wrapper.Unit.
@param #TASK self
@param #string TaskUnitName
@return #TASK self
@@ -6734,7 +6734,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:GetBriefing()
-Gets the Task briefing.
+Gets the #TASK briefing.
@@ -7004,7 +7004,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:GetProcessTemplate(ProcessName)
-Get the default or currently assigned Process template with key ProcessName.
+Get the default or currently assigned Core.Fsm#FSM_PROCESS template with key ProcessName.
@@ -7076,7 +7076,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:GetStateMachine(TaskUnit)
-Gets the FiniteStateMachine of Task with key TaskWrapper.Unit
+Gets the FiniteStateMachine of #TASK with key Wrapper.Unit.
@@ -7118,7 +7118,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:GetStateString()
-Gets the Task status.
+Gets the #TASK status.
@@ -7137,7 +7137,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:GetTaskBriefing()
-Returns the Task briefing.
+Returns the #TASK briefing.
@@ -7251,7 +7251,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:GetTaskName()
-Returns the Task name.
+Returns the #TASK name.
@@ -7398,7 +7398,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:HasAliveUnits()
-Returns if the Task has still alive and assigned Units.
+Returns if the #TASK has still alive and assigned Units.
@@ -7470,7 +7470,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:HasStateMachine(TaskUnit)
-Checks if there is a FiniteStateMachine assigned to TaskWrapper.Unit for Task
+Checks if there is a FiniteStateMachine assigned to Wrapper.Unit for #TASK.
@@ -7555,7 +7555,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:IsGroupAssigned(TaskGroup)
-Returns if the Task is assigned to the Group.
+Returns if the #TASK is assigned to the Group.
@@ -7597,7 +7597,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:IsStateAborted()
-Is the Task status Aborted.
+Is the #TASK status Aborted.
@@ -7616,7 +7616,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:IsStateAssigned()
-Is the Task status Assigned.
+Is the #TASK status Assigned.
@@ -7635,7 +7635,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:IsStateCancelled()
-Is the Task status Cancelled.
+Is the #TASK status Cancelled.
@@ -7654,7 +7654,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:IsStateFailed()
-Is the Task status Failed.
+Is the #TASK status Failed.
@@ -7673,7 +7673,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:IsStateHold()
-Is the Task status Hold.
+Is the #TASK status Hold.
@@ -7692,7 +7692,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:IsStatePlanned()
-Is the Task status Planned.
+Is the #TASK status Planned.
@@ -7711,7 +7711,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:IsStateReplanned()
-Is the Task status Replanned.
+Is the #TASK status Replanned.
@@ -7730,7 +7730,7 @@ If the TargetZone parameter is specified, the player will be routed to the cente
TASK_A2A:IsStateSuccess()
-Is the Task status Success.
+Is the #TASK status Success.
@@ -7974,7 +7974,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:MessageToGroups(Message)
-Send a message of the Task to the assigned Wrapper.Groups.
+Send a message of the #TASK to the assigned Wrapper.Groups.
@@ -8407,7 +8407,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:RefreshMenus(TaskGroup, MenuTime)
-Remove the menu option of the Task for a Wrapper.Group.
+Remove the menu option of the #TASK for a Wrapper.Group.
@@ -8561,7 +8561,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:RemoveAssignedMenuForGroup(TaskGroup, MenuTime)
-Remove the assigned menu option of the Task for a Wrapper.Group.
+Remove the assigned menu option of the #TASK for a Wrapper.Group.
@@ -8614,7 +8614,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:RemoveMenu(MenuTime)
-Remove the menu options of the Task to all the groups in the SetGroup.
+Remove the menu options of the #TASK to all the groups in the SetGroup.
@@ -8656,7 +8656,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:RemoveStateMachine(TaskUnit)
-Remove FiniteStateMachines from Task with key TaskWrapper.Unit
+Remove FiniteStateMachines from #TASK with key Wrapper.Unit.
@@ -8897,7 +8897,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:SendBriefingToAssignedGroups()
-Send the briefng message of the Task to the assigned Wrapper.Groups.
+Send the briefing message of the #TASK to the assigned Wrapper.Groups.
@@ -8947,7 +8947,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:SetAssignedMenuForGroup(TaskGroup, MenuTime)
-Set the assigned menu options of the Task.
+Set the assigned menu options of the #TASK.
@@ -9000,7 +9000,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:SetBriefing(TaskBriefing)
-Sets a Task briefing.
+Sets a #TASK briefing.
@@ -9178,7 +9178,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:SetGroupAssigned(TaskGroup)
-Set Wrapper.Group assigned to the Task.
+Set Wrapper.Group assigned to the #TASK.
@@ -9251,7 +9251,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:SetMenu(MenuTime)
-Set the menu options of the Task to all the groups in the SetGroup.
+Set the menu options of the #TASK to all the groups in the SetGroup.
@@ -9376,7 +9376,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:SetPlannedMenuForGroup(TaskGroup, MenuText, MenuTime)
-Set the planned menu option of the Task.
+Set the planned menu option of the #TASK.
@@ -9646,7 +9646,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:SetStateMachine(TaskUnit, Fsm)
-Add a FiniteStateMachine to Task with key TaskWrapper.Unit
+Add a FiniteStateMachine to #TASK with key Wrapper.Unit.
@@ -9699,10 +9699,10 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:SetTimeOut(Timer)
-Sets the TimeOut for the Task.
+Sets the TimeOut for the #TASK.
-If Task stayed planned for longer than TimeOut, it gets into Cancelled status.
+If #TASK stayed planned for longer than TimeOut, it gets into Cancelled status.
@@ -9819,7 +9819,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:StateAborted()
-Sets a Task to status Aborted.
+Sets a #TASK to status Aborted.
@@ -9838,7 +9838,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:StateAssigned()
-Sets a Task to status Assigned.
+Sets a #TASK to status Assigned.
@@ -9857,7 +9857,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:StateCancelled()
-Sets a Task to status Cancelled.
+Sets a #TASK to status Cancelled.
@@ -9876,7 +9876,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:StateFailed()
-Sets a Task to status Failed.
+Sets a #TASK to status Failed.
@@ -9895,7 +9895,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:StateHold()
-Sets a Task to status Hold.
+Sets a #TASK to status Hold.
@@ -9914,7 +9914,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:StatePlanned()
-Sets a Task to status Planned.
+Sets a #TASK to status Planned.
@@ -9933,7 +9933,7 @@ If the Unit is part of the Task, true is returned.
TASK_A2A:StateReplanned()
-Sets a Task to status Replanned.
+Sets a #TASK to status Replanned.