First about certain drones.
There are several ways of sending commands to multiple agents;
- bc:{full command} sends it to everybody
- w:{full command} sends it to subordinates of this one
- p:{full command} sends to parent ship
- bc<tag>:{full command} sends to units that have matching tag

From 0.9.92 the main way of commanding certain drone is done through <tag>.

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.


To refresh active drones you can recycle everyone with 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.


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 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.


WC breaks targeting, both turret AI and raycast, and also changes the way weapons are triggered. There are ways to solve those issues:

1. Targeting. To make APck see enemies under WC, you can use an adapter script by WARECRAFTER.
It would pass WeaponCore targeting data into APck, and that means you can use WC weapons for detecting enemies:

Pre 1.0:
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2923079499
1.0 compatible version:
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=3006407323

2. Triggering weapons. Use 'hd-coax' custom weapon grouping feature to wrap up WC weapons (see building guide for more info).


by NightRaid:

Originally posted by Nightraid Mine:

Been on the same spot as you so here is what I did.

1. After those process you did, put 2 additional timer blocks. Put a [fire][ref] and [cease] tags on the 2 timer. Example: Timer 1 [fire][ref] and Timer 2 [cease]. These timers will be used to trigger the start and stop shooting of your coax weapon.
Note: when putting your timer, press Ctrl +. This will show which is the front side of the timer as it is important to orient your timers facing front.
2. Put your 2 timers in a group and tag the group with [hd-coax][v=500][r=1000]. Example: Timer Group [hd-coax][v=500][r=1000]. The v and r values you can change, I think r is range v I forgot.
3. Put your weapon coax group on the timer hotbar. Put Shoot On in the timer with [fire][ref] then Shoot Off on the [cease].
4. Not sure if necessary but i ran command:clear-defs on the autopillock PB to be sure
5. Your weapon groups should fire when they detect the enemy and stop when no enemy detected.

by AN Marc Appledash:

Originally posted by AN Marc Appledash:

Just to make this clear the thing below is only for use With Weapon Core

you can also set the weapons shootmode to keyfire set the burst amount and have the timer that is used for the hd-coax tag to start it self and have the guns get triggerd with Shoot Modes Keytoggle/keyFire.

this will make the timer trigger the shoot once command for the gun with the set burst count and trigger it self this will work perfect since it only gets activated once the timer is line up with the target.

this way you can make it so that WC guns dont overheat

Yeah, that happens because you set response to Attack, which means it would create attack task (thats default behavior) immediately when it gets suitable target. At that point you have task queue which looks like: attack, move, wingman.
After it gets done with attack task, it would do the 2nd and 3rd tasks.
Solution is to set the response behavior to Attack only after it gets done with the move task - thats what exec task is for. It allows to execute arbitrary command at the moment it actually starts (rather than gets in the task queue).
I.e. you need to make move, exec, wingman tasks in this exact order.