Space Engineers

Space Engineers

APCK Control Module
cheerkin  [developer] 22 Nov, 2022 @ 1:51am
FAQ
Q: can you tell certain drones to dock or not to dock?

First about certain drones.
There are several ways of sending commands to multiple agents;
- command:bc:{full command} sends it to everybody
- command:w:{full command} sends it to subordinates of this one
- command:w-send-task:{create-task-...} sends task to subordinates of this one, adding your current Point as a target (for tasks that need coordinates - move, attack, land, etc)
- command:x-send-task:{create-task-...} sends task to current SelectedId, adding your current Point as a target

To have SelectedId set, you can use use command:pick-target (run twice - activate it, then point crosshair near the drone until you see drone ID on the panel, activate second time to stop search mode). At the moment, there is one inconvenience - the script uses forward gyro as a position from where you "look" forward, so on this particular build you'd have to aim crosshair lower than the drone.

If you want to command certain drone, not necessary subordinate, you can also use TMCs' context feature (you'd have to put your commands of interest in the drones' TMC CustomData).

Docking command is command:request-docking.

Then, if you want to exclude some drones from docking with others, then its' a bit trickier. You can give certain drones command:wait-for-signal and they would hold position until you send them command:signal.

Is there a command I can run to refresh active drones on scam and autopillock?

To refresh active drones you can recycle everyone with command:bc:command:recycle. That way carrier clears its' subordinate list, and they will re-link up to it.

Or recycle only the drone that was added (the drone assigns itself to a nearby carrier, not vice versa), in case you did not lose anyone but added a new one.

If a drone gets destroyed the others have issues waiting on the destroyed drone to dock. Not sure the best way to handle this without refreshing every drone PB and command ship PB

command:cancel-current-route executed on carrier would remove current active docking process and release the lock, letting next queued drone start its' docking route.

Another option would be rebooting everyone as you said, for that there is a command:bc:command:recycle (everyone) or command:w:command:recycle (only wingmen). That would require ordering dock again and may not resolve the issue as the problematic drone can be responsive but unable to dock because of damage.
Last edited by cheerkin; 25 Nov, 2022 @ 8:12am