Q: Any other targeting options other than turret AI?
A: Yeah, it has two other options - pirate GetNearestPlayer and Camera Raycast. Those will go to separate target vector "channel" though, and to attack drone has to have specific waypoint activated.

Q: Pirate GNP?
A: Change the grid to SPRT faction. The drone will target the nearest player (including you) within 20km (I believe) range.

Q: How to use TGP's raycast for locking?
1. Place camera named "coaxial-cam" for target designation.
2. Place cameras named "scan-array-cam-xx", the more the marrier.
3. Use argument "command:scan" on TGP.
*. For actual attack use argument "command:force-wp:gatle his♥♥♥♥♥off" on Autopillock
("command:scan" while pointing coaxial-cam to actual target). After successful locking you should see increasing ParseVectorsCount on Autopillock PB output, that indicates it's getting data from TGP. At this point you can force APck to activate engagement waypoint.

Q: What is the [clock=12] tag for?
A: It sets frequency of PB run. 12 means every 12th tick, it averages to 5 runs per second. I recommend setting 1 for host, 12 for drones.
Lower the number the faster refresh, but the higher the simpseed impact.

Q: Can I set my main ship as the host without the script controlling it, so I can still fly it and have the drones escort me?
A: Sure, just keep it in default state of Disabled cruise control. Check the CustomData and remove "command:set-mode:WP" which forces them to start acting. With empty CustomData they should not iterate through waypoints.

Q: I'm not sure I follow how to script swarm formations.
1. Replace [drone] tag with [host] tag in PB name, this will be the master ship.
2. Enable wingman broadcast on it by making PB CustomData look like this (all commands new line):
toggle:turret-response
toggle:broadcast-wingman
instead of
[command:wp-next]
3. After you spawn [drone] grids they should hook up to host and go to formation.
- "toggle:turret-response" switches drone react to enemy grids on/off,
- removing the "command:pillock-mode:WP" from Custom Data init sequence leaves autopilot an Disabled state so you can fly it yourself.
- "toggle:broadcast-wingman" will switch on formation vectors transmit for all registered peers (drones).
4. Optional. If you want your drones to attack a distant target, you have to toggle:broadcast-vectors on host. Vectors should be provided to host by its' TGP script, or by GPS coordinates command.

* after changing init sequence in Custom Data you want to either recompile the script or ctrl-x ctrl-v the whole grid.
** and you can do this for pirate faction ships - set up a host ship, change its faction to SPRT, then change a drone to pirate faction, then copy them in any numbers. This way drones won't spread out and will always return to their master ship.
Basically this is the way I set everything up in that arena battle video, the concept is pretty simple.

===============Hints for own drone basic design.===============

Remote control named "autopillock-remcon".
Gyro named "forward-gyro".
Easy orientation note: place gyro on top of Remote block, gyro control panel same orientation as front of remote block.

Fixed-mount weapons: group them into "coaxial-weapons".

For Grav Gen exclusions on large grid gravity drive based ships(eg. Defiant Mk2):
Find in the source:
b => Fw.CubeGrid == b.CubeGrid
Replace with:
b => Fw.CubeGrid == b.CubeGrid && !b.CustomName.Contains("tag")
That will exclude GGen with "tag" in it's name from grid's propulsion system.

===============Arguments/Custom Data===============

command:pillock-mode:WP
Enables APck and starts the first waypoint.

command:force-wp:{wp name}
Forces the drone into specific waypoint. Waypoint is more like behavior rather than specific coordinates in space.

Currently available waypoints:
find host - the first waypoint by default, drone searches for host by sending handshake sequence
init - sequence for repeated merge block slug strikes
gatle his♥♥♥♥♥off - close combat, basically as when AI turret detects an enemy, but uses TargetVectors data "channel" (guided from host ship or by onboard TGP)
request docking - asks host for free docking connector
Missile strike - for host to use drones as guided missiles. All drones will receive commands: command:recycle, command:pillock-mode:WP, command:force-wp:ram.
ram - use drone as guided missile (going to current TargetVectors in adaptive spiral pattern, then arm warheads, turnoff artificial mass, fuse warheads, etc)

command:set-value:{key}:{value}
Sets various parameters at runtime (best used in Custom Data of PB).
cqb-distance - Sets Close Quarters Battle distance (for turret intercept / gatle his♥♥♥♥♥off).
avoid-dz - true/false - sets enemy sphere avoidance at CQB, defaults true.
salvo-distance - sets the range that a Draugr or other similar drone will stay at to deliver repeated merge block slug strikes before entering CQB.
salvo-wave-count - sets the amount of merge block slug strikes.
cq-jab - if set to zero switches the CQB Jab parameter off. A Jab is a solid merge block slug strike at very close range.
inertia-gyro-divisor - default is 7. Regulates the amount of signal the gyros receive. Larger is recommended for heavy ships with lots of gyro power like Draugr. Set this to 1 and then increase if you see that your drone oscillates around aimpoint.
follow-formation-on-start - default is true. Drone goes to formation position (data "channel" WingmanVectors).

toggle:{key}
Switches stuff on/off.

broadcast-wingman - for host, gives all peers their position vectors (data "channel" WingmanVectors).
broadcast-vectors - for host, gives all peers current target vectors (data "channel" TargetVectors).
stealth-antenna - for drone, sets antenna radius to 1000m after successful handshake with host.
turret-response - sets if drone would interrupt its' current activity to engage targets dictated by AI turret (data "channel" TurretVectors).
wingman-circle-rotation - for host, sets cool looking circling formation On/Off for its' connected drones.
damp-when-idle - sets if the APck should use dampening when idle (switched to WP mode but with no actual data for waypoints).

===============Customization via named timers===============

There is a "hook" that tries to run a specifically named timer block whenever the drone starts or ends a waypoint. This way you can add some actions that can run PB with arguments, changing the control flow of the Autopillock.

Notation for timer naming:
{waypoint name}.OnStart
{waypoint name}.OnComplete

For example, timer block named "small threat response.OnStart" would be triggered when a small grid drone engages small grid detected by designator turret.

If you want the drone to dock to the host grid after the very first engagement, you can make a timer named "small threat response.OnComplete" and the action for timer would be to run Autopillock PB with argument "command:force-wp:request docking".