Documentation updates for correctness and clarity.
General code formatting updates.
Ajustment to POSITIONABLE:GetCoord to make use of existing POINT:UpdateFromVec3.
Added comments about clarifying the difference between POSITIONABLE:GetCoordinate() and POSITIONABLE:GetCoord() and to perhaps consider a renaming or merging the functions with an optional flag.
**AI_FORMATION**
- Performance improvents. This also affects the **RESCUEHELO** class.
**EVENT**
- Added events when object is of category BASE.
**FSM**
- Removed a few tracing calls.
- Updated docs.
**POINT**
- Added Update Vec functions to COORDINATE.
- Added *overwrite* option to COORDINATE:Translate() function.
- Removed second COORDINATE:Translate() function.
- Optimized COORDINATE:GetClosestAirbase() function.
- Added *Offset* parameter to COORDINATE:IsLOS() function.
**RADIO**
- Updated BEACON type and system enums.
**RADIOQUEUE**
- Use Vec3 instead of COORDINATE. Performance improvement.
**SET**
- Added some functions.
**TIMER**
- Added new class. Little sister of SCHEDULER class.
**DCS**
- Minor changes regarding docs.
**ATIS**
- Added "Miles.ogg", "StatuteMiles.ogg", "Zulu.ogg".
**ENUMS**
- Added ENUMS.Formation.Vehicle
- Added ENUMS.AlarmState
** PROFILER**
- Added new lua profiler.
**UTILS**
- Minor changes and additions.
**AIRBASE**
- Improved Registration.
- Improved Parking spot handling.
- Aded :IsAirdrome(), IsHelipad(), IsShip() functions.
- Improved :GetRunwayData() for Syria airports.
**CONTROLLABLE**
- Fixed bug in :CommandSetFrequency() fuction (Hz vs. MHz).
- Updated/fixed :TaskFAC_AttackGroup() function.
**GROUP**
- Added :GetThreatLevel() function.
- Added :IsInZone() function to check if any unit is in the zone.
**MARKER**
- Added new class handling F10 markers using FSM.
The units are then removed from each SET that is subscribed to a set of UNIT objects or GROUP objects! Also the DATABASE is correctly managing this new removal method.
This to prevent the DATABASE getting corrupted with dead units, which were removed with :Destroy(), but which weren't cleaned from the database.
Fixed near range issue for carriers. now the infantry disappearance range for boarding is calculated by the carrier bounding range, which is derived from the bounding rectangle on the Y-axis. The near range parameter can still be provided and will be interpreted as the loading range for static cargo objects!
