Subscribe to download
[APck] ThrustProvider (Clang, Vtol, Rov)

External thrust provider (Merge Drive, Mass Shift Drive, VTOL and Rover) for the AutoPillock script.

This type of drive uses merge blocks pull to generate thrust. It gives constant acceleration independent of grid mass. This is the best possible way of moving large grids simspeed-wise because you don't need hundreds of thrusters.

It can be used as a stand-alone system too, being controlled by WASD directly, it won't do dampening but would do gravity compensation.

Get the assembly blueprint and follow simple instructions on its' page.


Add the programmable block with this script into some group, I'll refer to it as ThrustProvider group.
Add VTOL units (rotor and at least one thruster per unit). Add their rotors to ThrustProvider group.
Add grids' forward-gyro, remote, and optionally control seat/cockpit (for WASD controls) to ThrustProvider group.
If you are adding VTOL to an existing APck-controlled grid, you'd have to clear grid definitions so APck could see ThrustProvider PB.
At this point, after APck recompile, you should see TP:True in APck printout (below Services) in terminal.

Then, to tell APck that the movement is handled by TP from this point, run command:thrust-delegation:Vtol. You should see ThrustDelegation in APck printout from now on. ThrustProvider should show "controlling N VTOL units".

Done. Now APck would use VTOL.

Watch the video for full process.


Rover implementation would control wheels steering and propulsion. It would try to align the wheels that have Steering enabled with destination direction and override steering proportional to distance.

Setting up is the same (see above), but instead of VTOL rotors you would add motor suspensions to the script group, and use "command:thrust-delegation:Rover" in the APck (you should see TP: true in APck PB printout when both scripts are running on the same grid, which means APck did handshake with ThrustProvider).

Note that by default APck does not run Echo printout for performance reasons, you need to "toggle:echo" to see that.


1. Make sure APck runs on the grid (script starts successfully)
2. Add ThrustProvider PB and put it to a new group
3. Add any remote control and forward-gyro to the group (TP won't control the remote, but it is important to have the same block for position reference)
4. Add "hardware" blocks to TP group depending on operation kind (rover, vtol, etc)
5. Recompile TP, it should be working now
6. Recompile APck and have echo toggled on ("toggle:echo"), make sure it sees Thrust Provider (TP: true in the PB detailed info)
7. To make APck pass movement data to TP, run thrust delegation command with the chosen kind (command:thrust-delegation:Rover or command:thrust-delegation:Vtol or command:thrust-delegation:Clang). Normally you'd put that command into APck CustomData boot sequence, unless you have a hybrid grid that works both with normal thrusters and TP.
8. Verify all works by using some simple task, like command:create-task:cruise-fw
* To switch delegation off, use command:thrust-delegation:None