YADS: A work in progress dcs server

After a unit has been killed and successfully respawned, it attempts to return to its previous location.

To avoid clusters of wrecks, and easy re-targeting, the reinforcement destination should be at a random location near the site of destruction. Optimally not inside buildings/trees, but that may be too annoying/impossible to reasonably get sorted, and should be a separate issue.

Additional conditions: If possible/available, group the unit with another unit. Should one of the units be damaged/killed en-route, disperse the remaining units for 2-5 minutes (DCS mission editor flag - disperse under fire?) In the event a unit is killed en-route, set reinforcement location to new death location.

The current waypoints of persistent units should also be persistent over restarts.

Otherwise units on the move will stop whenever the mission or YADS is restarted. That's especially an issue for automatic respawns, because they will stop wherever they are on their way to the frontline when a restart happens.

possible solutions:

• mechanism to kill units in an area with a special troop drop, will find hidden units and doesn't need line of site (use explosion api, like enigmas troop insert)
• Area "clear" process. land a certain amount of troops in a concentrated zone (min X troops and vehicles in range). Once met, if less then 1/2 units in the area we automatically remove them (assume they are stuck in a tree). To avoid things dissapearing in front of people we should put this in a relatively long delay. So it resolves itself just before being frustrating. instead of instantly deleting the last unit.

Spawn a small group of infantry (different predefined squads for different Trucks/APCs for example) when a ground unit of the same coalition around them is damaged or destroyed.

Makes more sense than spawning infantry on a destroyed unit.

First implementation idea:

1. handle unit gone event, maybe unit damaged event
2. search for closest unit with "unitEmpty=False" flag in radius (1km?)
3. spawn randomly chosen squad around found unit
4. set flag "unitEmpty" so we don't spawn multiple squads from same unit

considerations: don't define OP squads (RPGs are hard, MANPADS are hard)

Errors when naval units are in a mission:

  unit: {
    id: 39,
    name: 'Naval-1-1',
    coalition: 3,
    type: 'Forrestal',
    position: { lat: 34.907013766222875, lon: 33.75533160822897 },
    groupName: 'Naval-1',
    numberInGroup: 1,
    speed: 1.3594386535012912,
    heading: 326,
    category: 4
  }
}
Error: expected alt to be a number
    at positionLLFrom (F:\Documents\Git\yet-another-dcs-server\src\common.ts:179:11)
    at unitFrom (F:\Documents\Git\yet-another-dcs-server\src\unit.ts:253:29)
    at F:\Documents\Git\yet-another-dcs-server\src\group.ts:45:50
    at Array.map (<anonymous>)
    at Object.callback (F:\Documents\Git\yet-another-dcs-server\src\group.ts:45:30)
    at Object.onReceiveStatus (F:\Documents\Git\yet-another-dcs-server\node_modules\@grpc\grpc-js\src\client.ts:348:28)
    at Object.onReceiveStatus (F:\Documents\Git\yet-another-dcs-server\node_modules\@grpc\grpc-js\src\client-interceptors.ts:462:34)
    at Object.onReceiveStatus (F:\Documents\Git\yet-another-dcs-server\node_modules\@grpc\grpc-js\src\client-interceptors.ts:424:48)
    at F:\Documents\Git\yet-another-dcs-server\node_modules\@grpc\grpc-js\src\call-stream.ts:330:24
    at processTicksAndRejections (node:internal/process/task_queues:77:11)```