订阅以下载
AutoPillock - universal flight automaton [SUPERSEDED]

AutoPillock is general-purpose control script with focus on grid movement, formation management and combat.
This script sums up most things I've made in areas related to grid flight: combat, autodocking, formations, missile, clangdrives, weapon controls, gravity drives, this kind of stuff.


While it may be not the best in some areas, it can replace a few dozens of scripts on its' own.
Drone/missile/carrier/torpedo are the same thing. Missile can fly and fight like a drone, and carrier can ram target and detonate its' warheads, and a drone can dock on a missile, because why not.
Point, formation, docking navigation, landing to surface, planetary circumnavigation, player crosshair follow.
Keep altitude, speed control, gravity align, zero-g mode near planet, planetary circumnavigation (orbit), limited collision avoidance.
Different attack behaviors for point or targeted entity attacks. Advanced vanilla and custom weapons control.
Automatic configured threat response - free fire, missile launch, attack, etc.
Condition-based commands autorun during combat (chance, target type, target size, etc), changing combat face (weapons can be installed in all 6 directions), sudden ramming, etc.
Jab - inertial torpedo launch using ship acceleration.
SubUnit - drones can launch owned guided missiles.
Ref-hack antenna-less agents that run in the same physical PB and can be dynamically added any time any quantities (missile, drone, etc).
They can have their own sub-units, and this recursive structure is ran by a single PB.
Missile behavior (arm warheads, evasion mode, trigger timers), space-planet or planet-space pathfinding (circumnavigation).
Single thrust or 3d thrust, gravity or even clang drive missiles.
Wingman: dynamically configured formations based on subordination tree.
Routing: commands can be mass-issued using global/wingman/sub-unit/index/tag filtering.
Autodocking to any friendly ship (moving or rotating - it does not matter) with navigation graph support (for closed-type carriers)
Cargo: simple trade behaviors (pull or push certain type of cargo).
Repeat behavior for making shuttles with multiple docking stops, waiting, timer triggers, etc.
Task queues can be saved permanently and executed automatically or by trigger. Repeat behavior for cyclic tasks.
Built-in thrust control:

• Gravity drive
  
• Normal 6-dir thrust
  
• Single direction thrust

External thrust provider script support:

• Two types of clangdrive (mass shift, MMF)
  
• VTOL
  
• Rover (very basic at the moment)

Formations based on tree subordination. Tree is formed based on ranks and/or proximity. Commands can be issued to the whole attached wing and propagated down.
Handling guns

• Ripple fire mode with individual gun aiming.
  
• Switching based on weapon cooldowns, combat distance accounts for available weapons.
  
• Support for weapons in all 6 directions.
  
• Default weapon accuracy is 2/5m for ripple/pressure weapon groups.

Weapon support

• W2 vanilla
  
• Custom groups with velocity, range, accuracy settings.
  
• Player-made weapons like AK-125/8, piston jolts, etc.
  
• torpedoes with timer/proximity fuse
  
• internally-controlled missiles (aka Sub-Units)

External combat script integration:

• RWC (custom turrets and rotor-displacement cannon)
  
• GRA/GAPS (gravity active protection system)

Condition-based commands autorun during combat and decisions on special weapon usage (missiles, torpedo jabs).

Task queue management. Default task, wait for signal, repeat task, etc.
Target environment analysis, listening to global targeting link and designator turrets.
Assigns attack orders to WeapBot and move orders to Pilot.
Desides how to react on nearby threats.
Desides how exactly to fly to task position (flight behaviors, circumnavigation, carrier sphere avoidance, altitude checks, etc).
Raycast point, rangefinder, GPS reader to provide simple targeting alternative to TGP script.
Gateway to Command script that allows RTS-like fleet control.
Flight and rotation.
Controls gyros and thrusters to get the grid in a certain spot and rotation, or delegates this task to ThrustProvider service for VTOL/Clang/Rover.
Responsible to collect only blocks that are logically relevant to the agent. For example, one grid can be a bunch of drones dead-merged together, and ApckUnit resolves that.
Recursive initialization of units (one PB can control many "virtual" units like drones or missiles that are dynamically initialized and detached by merge block, they don't need antenna).
Provides docking/departure services for friendly agents.
Two modes:
- simple, when no navigation graph is attached - one approach waypoint above connector, no locking.
- navgrapth - runs a* navigation algorithm to tell an agent the shortest route from entry point to assigned dock or vice versa. Allows building complex routes to internal hangars.
Polls designator turrets for targets, provides simple filtering like minimal size.
Listens to global targeting datalink.

Mods are not supported explicitly. See FAQ on how to make it work with WeaponCore.

Get the carrier control module blueprint, it has drones included.
Watch demos there, read the description for how to use it.
It got somewhat decent TMC menu set-up that would let you use it without reading too much docs and references.
Get the reference drone and paste it near an enemy, or pass it to pirate faction.
If you spawn many, they would share targeting data and help each other.
There is a missile-equipped variant to showcase the SubUnit feature. You can change missile launch probability in PB CustomData.

Read the building guide

Read the user guide (pinned discussion).
Read the script arguments reference

Please make sure you've read links above, and the FAQ. If you still have no answer, it's better to ask it there, not on this page.

Please do not ask questions until you read relevant description/guide and do not complain on this page.

Questions -> there is a FAQ
Bugs/complains -> Known Issues & Bug Reports
Suggestions -> Feature Suggestions