• Fixed issue with missiles not avoiding the firing platform
  
• Update version to match LiDAR Mapping Script

• Added support for proximity sensors for warhead detonation. Missiles can now use a forward-facing camera or a sensor to assist in ensuring warhead detonation when nearing a target.
  
• Corrected the gravity calculations for missile guidance. Missiles now more accurately find their target.
  
• Fixed a bug with "Roll Speed" and "Toggle Spiral" commands not executing while missile is in flight

• Removed an unused variable

• Fixed a potential issue with antennae having broadcasting disabled - script now ensures it is enabled when launching
  
• Fixed a potential issue with batteries set to "Recharge-only" - script now sets them to discharge when launching

• Added collision avoidance. Missiles will now avoid colliding with the platform that fired them.
  
• Added configurable settings for the initial launch power for missile thrusters, found in the top portion of the script.
  
• Added missile sequencing. Missiles may now be fired in a user-defined sequence. See guide for details.

• Added a configurable setting in the top of the script to set the number of ticks a missile will fly (after launch) before gyros and thrusters are activated.

• Updated to work with new version of LiDAR Mapping Script (missile cluster support)

• Script now handles cases where thrusters and/or gyroscopes are turned off by default.
  
• Added a failsafe in the event a timer is set to run the PB every tick in addition to the self-run property.

• Script has been updated to work with the new version of my LiDAR Mapping Script.
  
• Missiles now take an additional parameter for launch / update commands:a tick count that tells the missile how many ticks to wait before launching.

--Script has been updated to work with the new version of my LiDAR Mapping Script.

--Missiles now take an additional parameter for launch / update commands: the TimeStamp from the MyDetectedEntityInfo (see Usage for details).