Previous fix on "avoid reading limits from Custom Data if PID controller (default method) is used" is not viable. Reverted to normal read if Custom Data contains limits.

NOTE: If you loaded and used this version while your rotors are limit locked (very old non PID versions that set rotor limits), your limits in custom Data is screwed. You need to stop the script, clear all Custom Data, and redo your rotor setup before running this script.

Minor fix to avoid reading limits from Custom Data if PID controller (default method) is used.

Fixed rotors snapping despite set to use PID controller by default.

1) Seperate sets of weapons, such that if one arm is damaged, the weapons on other arms still shoot.
2) Fixed division by zero for manual launch torpedos.
3) Fixed rocket launcher detection issue.

Added the following features:

1) Dual / Quad Arm Turret support.
2) PID Control instead of Rotor Angle Snapping (you can still enable this snapping method via Custom Data config => rotorUsePDCtrl=false).
3) Custom Weapon Profiles (allow different modded weapons to be used for different turrets by setting Custom Data config in the Azimuth Rotor of the particular PDC). More tutorials to be added.

Fixed dual and quad rotor issue.

Fixed bug where Manual Torpedo launched does not have guidance due to communication problems.

Fixed non existent targets stuck in infinite network communications loop (resulting in DDS keeps on shooting non existent targets).

Fixed issues with dual / quad arm turrets support.

Fixed network tracks transmission from 10 seconds (unintended typo in config) to 3/4 seconds.

Fixed major issues:
1) Missile offset targeting now working properly.
2) Missile communication for initial lock-on not working properly.