Combat Troop & Logistics Deployment (CTLD): Everyone wants to be a POG, until there's POG stuff to be done. (Mil Saying)

CTLD Concept

• MOOSE-based CTLD for Players.

• Object oriented refactoring of Ciribob's fantastic CTLD script.
• No need for extra MIST loading.
• Additional events to tailor your mission.
• ANY late activated group can serve as cargo, either as troops, crates, which have to be build on-location, or static like ammo chests.
• Option to persist (save&load) your dropped troops, crates and vehicles.
• Weight checks on loaded cargo.

0. Prerequisites

You need to load an .ogg soundfile for the pilot's beacons into the mission, e.g. "beacon.ogg", use a once trigger, "sound to country" for that. Create the late-activated troops, vehicles, that will make up your deployable forces.

Example sound files are here: Moose Sound

1. Basic Setup

1.1 Create and start a CTLD instance

A basic setup example is the following:

   -- Instantiate and start a CTLD for the blue side, using helicopter groups named "Helicargo" and alias "Lufttransportbrigade I"
   local my_ctld = CTLD:New(coalition.side.BLUE,{"Helicargo"},"Lufttransportbrigade I")
   my_ctld:__Start(5)

1.2 Add cargo types available

Add generic cargo types that you need for your missions, here infantry units, vehicles and a FOB. These need to be late-activated Wrapper.Group#GROUP objects:

   -- add infantry unit called "Anti-Tank Small" using template "ATS", of type TROOP with size 3
   -- infantry units will be loaded directly from LOAD zones into the heli (matching number of free seats needed)
   my_ctld:AddTroopsCargo("Anti-Tank Small",{"ATS"},CTLD_CARGO.Enum.TROOPS,3)
   -- if you want to add weight to your Heli, troops can have a weight in kg **per person**. Currently no max weight checked. Fly carefully.
   my_ctld:AddTroopsCargo("Anti-Tank Small",{"ATS"},CTLD_CARGO.Enum.TROOPS,3,80)

   -- add infantry unit called "Anti-Tank" using templates "AA" and "AA"", of type TROOP with size 4. No weight. We only have 2 in stock:
   my_ctld:AddTroopsCargo("Anti-Air",{"AA","AA2"},CTLD_CARGO.Enum.TROOPS,4,nil,2)

   -- add an engineers unit called "Wrenches" using template "Engineers", of type ENGINEERS with size 2. Engineers can be loaded, dropped,
   -- and extracted like troops. However, they will seek to build and/or repair crates found in a given radius. Handy if you can\'t stay
   -- to build or repair or under fire.
   my_ctld:AddTroopsCargo("Wrenches",{"Engineers"},CTLD_CARGO.Enum.ENGINEERS,4)
   myctld.EngineerSearch = 2000 -- teams will search for crates in this radius.

   -- add vehicle called "Humvee" using template "Humvee", of type VEHICLE, size 2, i.e. needs two crates to be build
   -- vehicles and FOB will be spawned as crates in a LOAD zone first. Once transported to DROP zones, they can be build into the objects
   my_ctld:AddCratesCargo("Humvee",{"Humvee"},CTLD_CARGO.Enum.VEHICLE,2)
   -- if you want to add weight to your Heli, crates can have a weight in kg **per crate**. Fly carefully.
   my_ctld:AddCratesCargo("Humvee",{"Humvee"},CTLD_CARGO.Enum.VEHICLE,2,2775)
   -- if you want to limit your stock, add a number (here: 10) as parameter after weight. No parameter / nil means unlimited stock.
   my_ctld:AddCratesCargo("Humvee",{"Humvee"},CTLD_CARGO.Enum.VEHICLE,2,2775,10)
   -- additionally, you can limit **where** the stock is available (one location only!) - this one is available in a zone called "Vehicle Store".
   my_ctld:AddCratesCargo("Humvee",{"Humvee"},CTLD_CARGO.Enum.VEHICLE,2,2775,10,nil,nil,"Vehicle Store")

   -- add infantry unit called "Forward Ops Base" using template "FOB", of type FOB, size 4, i.e. needs four crates to be build:
   my_ctld:AddCratesCargo("Forward Ops Base",{"FOB"},CTLD_CARGO.Enum.FOB,4)

   -- add crates to repair FOB or VEHICLE type units - the 2nd parameter needs to match the template you want to repair,
   -- e.g. the "Humvee" here refers back to the "Humvee" crates cargo added above (same template!)
   my_ctld:AddCratesRepair("Humvee Repair","Humvee",CTLD_CARGO.Enum.REPAIR,1)
   my_ctld.repairtime = 300 -- takes 300 seconds to repair something

   -- add static cargo objects, e.g ammo chests - the name needs to refer to a STATIC object in the mission editor, 
   -- here: it\'s the UNIT name (not the GROUP name!), the second parameter is the weight in kg.
   my_ctld:AddStaticsCargo("Ammunition",500)

1.3 Add logistics zones

Add (normal, round!) zones for loading troops and crates and dropping, building crates

   -- Add a zone of type LOAD to our setup. Players can load any troops and crates here as defined in 1.2 above.
   -- "Loadzone" is the name of the zone from the ME. Players can load, if they are inside the zone.
   -- Smoke and Flare color for this zone is blue, it is active (can be used) and has a radio beacon.
   my_ctld:AddCTLDZone("Loadzone",CTLD.CargoZoneType.LOAD,SMOKECOLOR.Blue,true,true)

   -- Add a zone of type DROP. Players can drop crates here.
   -- Smoke and Flare color for this zone is blue, it is active (can be used) and has a radio beacon.
   -- NOTE: Troops can be unloaded anywhere, also when hovering in parameters.
   my_ctld:AddCTLDZone("Dropzone",CTLD.CargoZoneType.DROP,SMOKECOLOR.Red,true,true)

   -- Add two zones of type MOVE. Dropped troops and vehicles will move to the nearest one. See options.
   -- Smoke and Flare color for this zone is blue, it is active (can be used) and has a radio beacon.
   my_ctld:AddCTLDZone("Movezone",CTLD.CargoZoneType.MOVE,SMOKECOLOR.Orange,false,false)

   my_ctld:AddCTLDZone("Movezone2",CTLD.CargoZoneType.MOVE,SMOKECOLOR.White,true,true)

   -- Add a zone of type SHIP to our setup. Players can load troops and crates from this ship
   -- "Tarawa" is the unitname (callsign) of the ship from the ME. Players can load, if they are inside the zone.
   -- The ship is 240 meters long and 20 meters wide.
   -- Note that you need to adjust the max hover height to deck height plus 5 meters or so for loading to work.
   -- When the ship is moving, avoid forcing hoverload.
   my_ctld:AddCTLDZone("Tarawa",CTLD.CargoZoneType.SHIP,SMOKECOLOR.Blue,true,true,240,20)

2. Options

The following options are available (with their defaults). Only set the ones you want changed:

     my_ctld.useprefix = true -- (DO NOT SWITCH THIS OFF UNLESS YOU KNOW WHAT YOU ARE DOING!) Adjust **before** starting CTLD. If set to false, *all* choppers of the coalition side will be enabled for CTLD.
     my_ctld.CrateDistance = 35 -- List and Load crates in this radius only.
     my_ctld.PackDistance = 35 -- Pack crates in this radius only
     my_ctld.dropcratesanywhere = false -- Option to allow crates to be dropped anywhere.
     my_ctld.dropAsCargoCrate = false -- Parachuted herc cargo is not unpacked automatically but placed as crate to be unpacked. Needs a cargo with the same name defined like the cargo that was dropped.
     my_ctld.maximumHoverHeight = 15 -- Hover max this high to load.
     my_ctld.minimumHoverHeight = 4 -- Hover min this low to load.
     my_ctld.forcehoverload = true -- Crates (not: troops) can **only** be loaded while hovering.
     my_ctld.hoverautoloading = true -- Crates in CrateDistance in a LOAD zone will be loaded automatically if space allows.
     my_ctld.smokedistance = 2000 -- Smoke or flares can be request for zones this far away (in meters).
     my_ctld.movetroopstowpzone = true -- Troops and vehicles will move to the nearest MOVE zone...
     my_ctld.movetroopsdistance = 5000 -- .. but only if this far away (in meters)
     my_ctld.smokedistance = 2000 -- Only smoke or flare zones if requesting player unit is this far away (in meters)
     my_ctld.suppressmessages = false -- Set to true if you want to script your own messages.
     my_ctld.repairtime = 300 -- Number of seconds it takes to repair a unit.
     my_ctld.buildtime = 300 -- Number of seconds it takes to build a unit. Set to zero or nil to build instantly.
     my_ctld.cratecountry = country.id.GERMANY -- ID of crates. Will default to country.id.RUSSIA for RED coalition setups.
     my_ctld.allowcratepickupagain = true  -- allow re-pickup crates that were dropped.
     my_ctld.enableslingload = false -- allow cargos to be slingloaded - might not work for all cargo types
     my_ctld.pilotmustopendoors = false -- force opening of doors
     my_ctld.SmokeColor = SMOKECOLOR.Red -- default color to use when dropping smoke from heli 
     my_ctld.FlareColor = FLARECOLOR.Red -- color to use when flaring from heli
     my_ctld.basetype = "container_cargo" -- default shape of the cargo container
     my_ctld.droppedbeacontimeout = 600 -- dropped beacon lasts 10 minutes
     my_ctld.usesubcats = false -- use sub-category names for crates, adds an extra menu layer in "Get Crates", useful if you have > 10 crate types.
     my_ctld.placeCratesAhead = false -- place crates straight ahead of the helicopter, in a random way. If true, crates are more neatly sorted.
     my_ctld.nobuildinloadzones = true -- forbid players to build stuff in LOAD zones if set to `true`
     my_ctld.movecratesbeforebuild = true -- crates must be moved once before they can be build. Set to false for direct builds.
     my_ctld.surfacetypes = {land.SurfaceType.LAND,land.SurfaceType.ROAD,land.SurfaceType.RUNWAY,land.SurfaceType.SHALLOW_WATER} -- surfaces for loading back objects.
     my_ctld.nobuildmenu = false -- if set to true effectively enforces to have engineers build/repair stuff for you.
     my_ctld.RadioSound = "beacon.ogg" -- -- this sound will be hearable if you tune in the beacon frequency. Add the sound file to your miz.
     my_ctld.RadioSoundFC3 = "beacon.ogg" -- this sound will be hearable by FC3 users (actually all UHF radios); change to something like "beaconsilent.ogg" and add the sound file to your miz if you don't want to annoy FC3 pilots.
     my_ctld.enableChinookGCLoading = true -- this will effectively suppress the crate load and drop for CTLD_CARGO.Enum.STATIc types for CTLD for the Chinook
     my_ctld.TroopUnloadDistGround = 5 -- If hovering, spawn dropped troops this far away in meters from the helo
     my_ctld.TroopUnloadDistHover = 1.5 -- If grounded, spawn dropped troops this far away in meters from the helo
     my_ctld.TroopUnloadDistGroundHerc = 25 -- On the ground, unload troops this far behind the Hercules
     my_ctld.TroopUnloadDistGroundHook = 15 -- On the ground, unload troops this far behind the Chinook

2.1 CH-47 Chinook support

The Chinook comes with the option to use the ground crew menu to load and unload cargo into the Helicopter itself for better immersion. As well, it can sling-load cargo from ground. The cargo you can actually create from this menu is limited to contain items from the airbase or FARP's resources warehouse and can take a number of shapes (static shapes in the category of cargo) independent of their contents. If you unload this kind of cargo with the ground crew, the contents will be "absorbed" into the airbase or FARP you landed at, and the cargo static will be removed after ca 2 mins.

2.1.1 Moose CTLD created crate cargo

Given the correct shape, Moose created cargo can be either loaded with the ground crew or via the F10 CTLD menu. It is strongly recommend to either use the ground crew or CTLD to load/unload Moose created cargo. Mix and match will not work here. Static shapes loadable into the Chinook are at the time of writing:

 * Ammo crate (type "ammo_cargo")
 * M117 bomb crate (type name "m117_cargo")
 * Dual shell fuel barrels (type name "barrels")
 * UH-1H net (type name "uh1h_cargo")

All other kinds of cargo can be sling-loaded.

2.1.2 Recommended settings

     my_ctld.basetype = "ammo_cargo"
     my_ctld.forcehoverload = false -- no hover autoload, leads to cargo complications with ground crew created cargo items
     my_ctld.pilotmustopendoors = true -- crew must open back loading door 50% (horizontal) or more
     my_ctld.enableslingload = true -- will set cargo items as sling-loadable
     my_ctld.enableChinookGCLoading = true -- will effectively suppress the crate load and drop menus for CTLD for the Chinook
     my_ctld.movecratesbeforebuild = false -- cannot detect movement of crates at the moment
     my_ctld.nobuildinloadzones = true -- don't build where you load.
     my_ctld.ChinookTroopCircleRadius = 5 -- Radius for troops dropping in a nice circle. Adjust to your planned squad size for the Chinook.

2.2 User functions

2.2.1 Adjust or add chopper unit-type capabilities

Use this function to adjust what a heli type can or cannot do:

   -- E.g. update unit capabilities for testing. Please stay realistic in your mission design.
   -- Make a Gazelle into a heavy truck, this type can load both crates and troops and eight of each type, up to 4000 kgs:
   my_ctld:SetUnitCapabilities("SA342L", true, true, 8, 8, 12, 4000)

   -- Default unit type capabilities are: 
   ["SA342Mistral"] = {type="SA342Mistral", crates=false, troops=true, cratelimit = 0, trooplimit = 4, length = 12, cargoweightlimit = 400},
   ["SA342L"] = {type="SA342L", crates=false, troops=true, cratelimit = 0, trooplimit = 2, length = 12, cargoweightlimit = 400},
   ["SA342M"] = {type="SA342M", crates=false, troops=true, cratelimit = 0, trooplimit = 4, length = 12, cargoweightlimit = 400},
   ["SA342Minigun"] = {type="SA342Minigun", crates=false, troops=true, cratelimit = 0, trooplimit = 2, length = 12, cargoweightlimit = 400},
   ["UH-1H"] = {type="UH-1H", crates=true, troops=true, cratelimit = 1, trooplimit = 8, length = 15, cargoweightlimit = 700},
   ["Mi-8MT"] = {type="Mi-8MT", crates=true, troops=true, cratelimit = 2, trooplimit = 12, length = 15, cargoweightlimit = 3000},
   ["Mi-8MTV2"] = {type="Mi-8MTV2", crates=true, troops=true, cratelimit = 2, trooplimit = 12, length = 15, cargoweightlimit = 3000},
   ["Ka-50"] = {type="Ka-50", crates=false, troops=false, cratelimit = 0, trooplimit = 0, length = 15, cargoweightlimit = 0},
   ["Mi-24P"] = {type="Mi-24P", crates=true, troops=true, cratelimit = 2, trooplimit = 8, length = 18, cargoweightlimit = 700},
   ["Mi-24V"] = {type="Mi-24V", crates=true, troops=true, cratelimit = 2, trooplimit = 8, length = 18, cargoweightlimit = 700},
   ["Hercules"] = {type="Hercules", crates=true, troops=true, cratelimit = 7, trooplimit = 64, length = 25, cargoweightlimit = 19000},
   ["UH-60L"] = {type="UH-60L", crates=true, troops=true, cratelimit = 2, trooplimit = 20, length = 16, cargoweightlimit = 3500},
   ["AH-64D_BLK_II"] = {type="AH-64D_BLK_II", crates=false, troops=true, cratelimit = 0, trooplimit = 2, length = 17, cargoweightlimit = 200}, 
   ["MH-60R"] = {type="MH-60R", crates=true, troops=true, cratelimit = 2, trooplimit = 20, length = 16, cargoweightlimit = 3500}, -- 4t cargo, 20 (unsec) seats
   ["SH-60B"] = {type="SH-60B", crates=true, troops=true, cratelimit = 2, trooplimit = 20, length = 16, cargoweightlimit = 3500}, -- 4t cargo, 20 (unsec) seats
   ["Bronco-OV-10A"] = {type="Bronco-OV-10A", crates= false, troops=true, cratelimit = 0, trooplimit = 5, length = 13, cargoweightlimit = 1450},
   ["Bronco-OV-10A"] = {type="Bronco-OV-10A", crates= false, troops=true, cratelimit = 0, trooplimit = 5, length = 13, cargoweightlimit = 1450},
   ["OH-6A"] = {type="OH-6A", crates=false, troops=true, cratelimit = 0, trooplimit = 4, length = 7, cargoweightlimit = 550},
   ["OH58D"] = {type="OH58D", crates=false, troops=false, cratelimit = 0, trooplimit = 0, length = 14, cargoweightlimit = 400},
   ["CH-47Fbl1"] = {type="CH-47Fbl1", crates=true, troops=true, cratelimit = 4, trooplimit = 31, length = 20, cargoweightlimit = 8000},

2.2.2 Activate and deactivate zones

Activate a zone:

   -- Activate zone called Name of type #CTLD.CargoZoneType ZoneType:
   my_ctld:ActivateZone(Name,CTLD.CargoZoneType.MOVE)

Deactivate a zone:

   -- Deactivate zone called Name of type #CTLD.CargoZoneType ZoneType:
   my_ctld:DeactivateZone(Name,CTLD.CargoZoneType.DROP)

2.2.3 Limit and manage available resources

When adding generic cargo types, you can effectively limit how many units can be dropped/build by the players, e.g.

         -- if you want to limit your stock, add a number (here: 10) as parameter after weight. No parameter / nil means unlimited stock.
         my_ctld:AddCratesCargo("Humvee",{"Humvee"},CTLD_CARGO.Enum.VEHICLE,2,2775,10)

You can manually add or remove the available stock like so:

         -- Crates
         my_ctld:AddStockCrates("Humvee", 2)
         my_ctld:RemoveStockCrates("Humvee", 2)

         -- Troops
         my_ctld:AddStockTroops("Anti-Air", 2)
         my_ctld:RemoveStockTroops("Anti-Air", 2)

Notes: Troops dropped back into a LOAD zone will effectively be added to the stock. Crates lost in e.g. a heli crash are just that - lost.

2.2.4 Create own SET_GROUP to manage CTLD Pilot groups

         -- Parameter: Set The SET_GROUP object created by the mission designer/user to represent the CTLD pilot groups.
         -- Needs to be set before starting the CTLD instance.
         local myset = SET_GROUP:New():FilterPrefixes("Helikopter"):FilterCoalitions("red"):FilterStart()
         my_ctld:SetOwnSetPilotGroups(myset)

3. Events

The class comes with a number of FSM-based events that missions designers can use to shape their mission. These are:

3.1 OnAfterTroopsPickedUp

This function is called when a player has loaded Troops:

   function my_ctld:OnAfterTroopsPickedUp(From, Event, To, Group, Unit, Cargo)
     ... your code here ...
   end

3.2 OnAfterCratesPickedUp

This function is called when a player has picked up crates:

   function my_ctld:OnAfterCratesPickedUp(From, Event, To, Group, Unit, Cargo)
     ... your code here ...
   end

3.3 OnAfterTroopsDeployed

This function is called when a player has deployed troops into the field:

   function my_ctld:OnAfterTroopsDeployed(From, Event, To, Group, Unit, Troops)
     ... your code here ...
   end

3.4 OnAfterTroopsExtracted

This function is called when a player has re-boarded already deployed troops from the field:

   function my_ctld:OnAfterTroopsExtracted(From, Event, To, Group, Unit, Troops)
     ... your code here ...
   end

3.5 OnAfterCratesDropped

This function is called when a player has deployed crates to a DROP zone:

   function my_ctld:OnAfterCratesDropped(From, Event, To, Group, Unit, Cargotable)
     ... your code here ...
   end

3.6 OnAfterCratesBuild, OnAfterCratesRepaired

This function is called when a player has build a vehicle or FOB:

   function my_ctld:OnAfterCratesBuild(From, Event, To, Group, Unit, Vehicle)
     ... your code here ...
   end

   function my_ctld:OnAfterCratesRepaired(From, Event, To, Group, Unit, Vehicle)
     ... your code here ...
   end

3.7 A simple SCORING example:

To award player with points, using the SCORING Class (SCORING: my_Scoring, CTLD: CTLD_Cargotransport)

   my_scoring = SCORING:New("Combat Transport")

   function CTLD_Cargotransport:OnAfterCratesDropped(From, Event, To, Group, Unit, Cargotable)
       local points = 10
       if Unit then
         local PlayerName = Unit:GetPlayerName()
         my_scoring:_AddPlayerFromUnit( Unit )
         my_scoring:AddGoalScore(Unit, "CTLD", string.format("Pilot %s has been awarded %d points for transporting cargo crates!", PlayerName, points), points)
       end
   end

   function CTLD_Cargotransport:OnAfterCratesBuild(From, Event, To, Group, Unit, Vehicle)
     local points = 5
     if Unit then
     local PlayerName = Unit:GetPlayerName()
     my_scoring:_AddPlayerFromUnit( Unit )
     my_scoring:AddGoalScore(Unit, "CTLD", string.format("Pilot %s has been awarded %d points for the construction of Units!", PlayerName, points), points)
     end
    end

4. F10 Menu structure

CTLD management menu is under the F10 top menu and called "CTLD"

4.1 Manage Crates

Use this entry to get, load, list nearby, drop, build and repair crates. Also see options.

4.2 Manage Troops

Use this entry to load, drop and extract troops. NOTE - with extract you can only load troops from the field that were deployed prior. Currently limited CTLD_CARGO troops, which are build from one template. Also, this will heal/complete your units as they are respawned.

4.3 List boarded cargo

Lists what you have loaded. Shows load capabilities for number of crates and number of seats for troops.

4.4 Smoke & Flare zones nearby or drop smoke, beacon or flare from Heli

Does what it says.

4.5 List active zone beacons

Lists active radio beacons for all zones, where zones are both active and have a beacon. @see CTLD:AddCTLDZone()

4.6 Show hover parameters

Lists hover parameters and indicates if these are curently fulfilled. Also @see options on hover heights.

4.7 List Inventory

Lists invetory of available units to drop or build.

5. Support for Hercules mod by Anubis

Basic support for the Hercules mod By Anubis has been build into CTLD - that is you can load/drop/build the same way and for the same objects as the helicopters (main method). To cover objects and troops which can be loaded from the groud crew Rearm/Refuel menu (F8), you need to use CTLD_HERCULES.New() and link this object to your CTLD setup (alternative method). In this case, do not use the Hercules_Cargo.lua or Hercules_Cargo_CTLD.lua which are part of the mod in your mission!

5.1 Create an own CTLD instance and allow the usage of the Hercules mod (main method)

         local my_ctld = CTLD:New(coalition.side.BLUE,{"Helicargo", "Hercules"},"Lufttransportbrigade I")

Enable these options for Hercules support:

         my_ctld.enableHercules = true
         my_ctld.HercMinAngels = 155 -- for troop/cargo drop via chute in meters, ca 470 ft
         my_ctld.HercMaxAngels = 2000 -- for troop/cargo drop via chute in meters, ca 6000 ft
         my_ctld.HercMaxSpeed = 77 -- 77mps or 270kph or 150kn

Hint: you can only airdrop from the Hercules if you are "in parameters", i.e. at or below HercMaxSpeed and in the AGL bracket between HercMinAngels and HercMaxAngels!

Also, the following options need to be set to true:

         my_ctld.useprefix = true -- this is true by default and MUST BE ON. 

5.2 Integrate Hercules ground crew (F8 Menu) loadable objects (alternative method, use either the above OR this method, NOT both!)

Integrate to your CTLD instance like so, where my_ctld is a previously created CTLD instance:

       my_ctld.enableHercules = false -- avoid dual loading via CTLD F10 and F8 ground crew
       local herccargo = CTLD_HERCULES:New("blue", "Hercules Test", my_ctld)

You also need:

• A template called "Infantry" for 10 Paratroopers (as set via herccargo.infantrytemplate).
• Depending on what you are loading with the help of the ground crew, there are 42 more templates for the various vehicles that are loadable.

There's a quick check output in the dcs.log which tells you what's there and what not. E.g.:

       ...Checking template for APC BTR-82A Air [24998lb] (BTR-82A) ... MISSING)   
       ...Checking template for ART 2S9 NONA Skid [19030lb] (SAU 2-C9) ... MISSING)   
       ...Checking template for EWR SBORKA Air [21624lb] (Dog Ear radar) ... MISSING)   
       ...Checking template for Transport Tigr Air [15900lb] (Tigr_233036) ... OK)   

Expected template names are the ones in the rounded brackets.

5.2.1 Hints

The script works on the EVENTS.Shot trigger, which is used by the mod when you drop cargo from the Hercules while flying. Unloading on the ground does not achieve anything here. If you just want to unload on the ground, use the normal Moose CTLD (see 5.1).

DO NOT use the "splash damage" script together with this method! Your cargo will explode on the ground!

There are two ways of airdropping:

1) Very low and very slow (>5m and <10m AGL) - here you can drop stuff which has "Skid" at the end of the cargo name (loaded via F8 Ground Crew menu)
2) Higher up and slow (>100m AGL) - here you can drop paratroopers and cargo which has "Air" at the end of the cargo name (loaded via F8 Ground Crew menu)

Standard transport capabilities as per the real Hercules are:

          ["Hercules"] = {type="Hercules", crates=true, troops=true, cratelimit = 7, trooplimit = 64}, -- 19t cargo, 64 paratroopers

5.3 Don't automatically unpack dropped cargo but drop as CTLD_CARGO

Cargo can be defined to be automatically dropped as crates.

         my_ctld.dropAsCargoCrate = true -- default is false

The idea is, to have those crate behave like brought in with a helo. So any unpack restictions apply. To enable those cargo drops, the cargo types must be added manually in the CTLD configuration. So when the above defined template for "Vulcan" should be used as CTLD_Cargo, the following line has to be added. NoCrates, PerCrateMass, Stock, SubCategory can be configured freely.

         my_ctld:AddCratesCargo("Vulcan",      {"Vulcan"}, CTLD_CARGO.Enum.VEHICLE, 6, 2000, nil, "SAM/AAA")

So if the Vulcan in the example now needs six crates to complete, you have to bring two Hercs with three Vulcan crates each and drop them very close together...

6. Save and load back units - persistance

You can save and later load back units dropped or build to make your mission persistent. For this to work, you need to de-sanitize io and lfs in your MissionScripting.lua, which is located in your DCS installtion folder under Scripts. There is a risk involved in doing that; if you do not know what that means, this is possibly not for you.

Use the following options to manage your saves:

         my_ctld.enableLoadSave = true -- allow auto-saving and loading of files
         my_ctld.saveinterval = 600 -- save every 10 minutes
         my_ctld.filename = "missionsave.csv" -- example filename
         my_ctld.filepath = "C:\\Users\\myname\\Saved Games\\DCS\Missions\\MyMission" -- example path
         my_ctld.eventoninject = true -- fire OnAfterCratesBuild and OnAfterTroopsDeployed events when loading (uses Inject functions)
         my_ctld.useprecisecoordloads = true -- Instead if slightly varyiing the group position, try to maintain it as is

Then use an initial load at the beginning of your mission:

       my_ctld:__Load(10)

Caveat: If you use units build by multiple templates, they will effectively double on loading. Dropped crates are not saved. Current stock is not saved.

7. Complex example - Build a complete FARP from a CTLD crate drop

Prerequisites - you need to add a cargo of type FOB to your CTLD instance, for simplification reasons we call it FOB:

       my_ctld:AddCratesCargo("FARP",{"FOB"},CTLD_CARGO.Enum.FOB,2)

The following code will build a FARP at the coordinate the FOB was dropped and built (the UTILS function used below does not need a template for the statics):

     -- FARP Radio. First one has 130AM name London, next 131 name Dallas, and so forth. 
     local FARPFreq = 129
     local FARPName = 1  --numbers 1..10

     local FARPClearnames = {
       [1]="London",
       [2]="Dallas",
       [3]="Paris",
       [4]="Moscow",
       [5]="Berlin",
       [6]="Rome",
       [7]="Madrid",
       [8]="Warsaw",
       [9]="Dublin",
       [10]="Perth",
       }

     function BuildAFARP(Coordinate)
       local coord = Coordinate  --Core.Point#COORDINATE

       local FarpNameNumber = ((FARPName-1)%10)+1 -- make sure 11 becomes 1 etc
       local FName = FARPClearnames[FarpNameNumber] -- get clear namee

       FARPFreq = FARPFreq + 1
       FARPName = FARPName + 1

       FName = FName .. " FAT COW "..tostring(FARPFreq).."AM" -- make name unique

       -- Get a Zone for loading 
       local ZoneSpawn = ZONE_RADIUS:New("FARP "..FName,Coordinate:GetVec2(),150,false)

       -- Spawn a FARP with our little helper and fill it up with resources (10t fuel each type, 10 pieces of each known equipment)
       UTILS.SpawnFARPAndFunctionalStatics(FName,Coordinate,ENUMS.FARPType.INVISIBLE,my_ctld.coalition,country.id.USA,FarpNameNumber,FARPFreq,radio.modulation.AM,nil,nil,nil,10,10)

       -- add a loadzone to CTLD
       my_ctld:AddCTLDZone("FARP "..FName,CTLD.CargoZoneType.LOAD,SMOKECOLOR.Blue,true,true)
       local m  = MESSAGE:New(string.format("FARP %s in operation!",FName),15,"CTLD"):ToBlue() 
     end

     function my_ctld:OnAfterCratesBuild(From,Event,To,Group,Unit,Vehicle)
       local name = Vehicle:GetName()
       if string.find(name,"FOB",1,true) then
         local Coord = Vehicle:GetCoordinate()
         Vehicle:Destroy(false)
         BuildAFARP(Coord) 
       end
     end