Not sure what you intend to change though, there is no explicit checks in the code which forbid that kind of connector facing. It's just not advised to do it like that because of how routing/docking works.

Sure it is, but I'm not going to help with that, it goes against the tech design here and would produce more issues than benefits.

Is it possible to edit the code for connectors facing in the opposite direction of the drills? I've gotten it to work a few times through random chance but it's never been consistent.

gona move this to bugs , as im apperently to dumb to fix it xD

NP! The main thing is when you ask on that thread, people who might have had this issue can help you as well (many are still subscribed to comments there).

i kinda feel bad now to keep asking here so thx anyways

So you are saying you are aware that issues are posted in the dedicated discussion and you still post it here, I wonder what are the mechanics behind your life decision making. Anyways, maybe try clearing the state, looks like the miner is stuck in a docking attempt which is no longer relevant.

so been trying for hours so im kinda frustrated atm but i had the thruster issue which i resolved now i have this -- 0.00: Assigned role: Agent
0.00: subset: 62
4.93: CommandAutoPillock: command:create-wp:Name=DynamicDock.echelon,Ng=Forward,AimNormal=0.512127289511435;-0.345951921186113;-0.786157050191187,TransformChannel=docking:-6.82121026329696E-13:9.31144050753119E-13:-28.2500000000073:command:pillock-mode:DockingFinal
4.93: Added DynamicDock.echelon, total: 1
4.93: Standby -> CwpTask
4.95: HC EPIC FAIL
NTV:docking
Behavior:Deserialized Behavior
System.InvalidOperationException: Nullable object must have a value.
at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
at Program.<>c__DisplayClass83_1.<lj>b__13(Vector3D ë)
at Program.à.I(Int32 H, Action`1 F, ƻ D)

insted of playing i was troubleshooting this and didnt get far xD
i know wrong section but i coud really use some help :D

@cheerkin
The features look impressive. Thank you for developing and sharing.
Like the previous poster @Bockda I too look forward to the source code release.

Yeah, at some point. I have new WIP version in progress.

Cheerkin would you release source code?
looking to adapt some parts for priv use.

1. You probably mean warnings - ignore them, they are meant for programmer, not for you
2. If you have issues please post in bug reports, as being asked in the description right here

{LINK REMOVED}https://ibb.co/hxC0ZCjw

I sadly recieve many errors when compiling the code.

Thank you. i see they tend to set there own names.
When i move to a new zone and set one to command:create-task. some times the others say docking and do nothing. i tried to move them, redock them nothing seems to help unless i command:clear-storage-state then redock and do command:mine

What you see in logs is ID, you can use color to identify drones in the GUI. Logs are for troubleshooting purposes, I don't see a reason to use some custom name there.

Is there a way to set a custom name for the drones and not just a set of numbers?

No worries, just copy there your original message (with more details if there any) so it won't get buried here. Also people there might've had similar issues. For now I have no idea where to start, that never happened to me before and sounds like general issue with the game - if that is the case, would be good to post it on the Keen support forum if you would be able to find repro steps.

omg, I just caught the comment about the pinned bug report section!
I'll delete the comments when this is all resolved except for one to be used for context, and of course a thank you and or an apology from myself!

and yes I did check power, even adding new batteries which in creative recharge automatically.

"causes all cargo transfer to cease":
Im not sure about sorters, but automatic push / pull wasn't working, and vessels with power and connected pipes which were never connected to a programmable block were not allowing me to manually transfer between containers as well, they were all blacked out when you picked up an item. I could only ever add resources to the block I was directly accessing.

It was a global issue, which is very strange indeed.
it's fairly reproducible, but for the sake of bug testing, I will create a new world with no extra mods installed, just to see what might have happened.

By "causes all cargo transfer to cease" you mean even in-game features do not work, like sorters or manual drag-n-drop? Or that script ceases to push ore to the designated container?
If you happen to experience this bug again would be helpful if you posted a video showing what's going on (also, please move this in the pinned bug reports discussion).

for more context, one way this occurs is when docking. it will transfer some items and then get stuck. if I do something like force it to undock or delete the connector, it will go offline, and require that I place a new battery to fix this. if it matters, I am playing in creative mode. The rest of the script seems to work fine, it's just that when this happens everything stops working correctly, the script seems to be affected by whatever is happening as well and locks up despite being recompiled. Drones don't move, things like that.

I would like to report a bug. some form of strangeness is occuring where something in the script causes all cargo transfer to cease. I have to close to desktop to fix this. it has affected ships without programmable blocks on it. When I reload the world I find the cargo container I was looking at which was broken fixed again.

Hi! Thanks! I think it is possible, but not recommended as collisions may happen due to drone rotation. If you are using just 1 drone, should be fine.

Hi, is it possible to use this script with a connector on the back of the drone too?
Thank you in advance, and nice work by the way.

Does it bother you? Regarding your question, there is a Change Notes link in the upper top on every WS script page.

question. will this script ever update? i'm getting the https://ibb.co/0j8TsG3c when recompile script.

Only by code modification, there is a field at the top (MAX_SP = 104.38f).

outside of the shaft they are limited to 104 can they go to modded max speed with a setting change?

thanks cheerkin for the mod! I guess my problem arises when it does both, doesnt look ahead, and then goes at max speed into a mountainside.

> not possible to change the max speed, they fly as fast as they can outside of the shafts
> minimum altitude like that won't work for multiple reasons, the main one is that you can get the altitude only at the point below, so if you are even remotely fast you won't have time to adjust to the slope steep enough. Also that would mess up the idea of isolated height echelons

getAbove-altitude 20 Flat value that is added to pathing, useful when drones need to fly over a wall to docking area


I get that I can set this to get it over the mountain, but not all my jobs are over the mountain. is there no setting in autopillock that keeps a minimum altitude while commuting from base to jobsite and back?

Is it possible to change the max speed on the miners?

(the antennas)

it wont work if theyre on the same grid

I see, I suspected antenas would play a role here.

I was thinking to have 2 set of antenas on each dispatcher
One with a very short range for compile and assign really really nearby drones

and a long range antena for the rest of functionalities, remote access, etc.

and just make sure to turn off long range antena while setting up drones.

I'll give it a try

There is no way atm, they will interfere if their antenna ranges overlap (or dispatchers are on the same grid). You will need to move away or turn the base dispatcher off, then recompile all drones so they link up only to the ship dispatcher.

How can I assign drones to different dispatchers?
I have a base at a moon's surface and my main ship both with its own dispatcher.

Hm, no, that is not implemented, and tbh still looks a bit counter-logical. If you are able to fly certain drone to a mining position in that environment, that means it is capable to operate? Why call in the different group then? Sounds like you want the drone to act as a designator ship, but there is already a feature of raycast from dispatcher for task creation.
"command:create-task:group-constraint:B" should not be hard to implement though.

Thanks for the reply! Sorry, I think I was unclear (or I misunderstood).

I understand the purpose of group-constraints to limit the task to a single type of agent. Not trying to run multiple tasks on a single dispatcher, just use one group to trigger a different group.

What I was hoping is that it was possible to trigger a group-constraint for a different group than the triggering agent. For example:

Drone group A: SG miner w/ H2 thrusters.
Drone group B: LG miner w/ Ion thrusters.

Drone A moves into position above the deposit via RC. Uses a 'create task' command, but instead of triggering the task in group-constraint for type A, it routes it to type B (<<This is the part I'm not sure if it's possible). Drone A moves away via RC, while drone type B moves in to start drilling.

Something like "command:create-task:group-constraint:B"? Though I don't think that exists, is there something with a similar functionality?

For now only one running task per dispatcher is supported. The idea behind group constraints was to use a subset of drones based on environment (e.g. not letting gravdrive miners join the task on planet, atmo-thruster drones in space, etc.)

Hey - thanks for the script! (Thought I had posted this already, but perhaps not?)

Is there a way to 'create-task' but aimed at a different group-constraint? I (think I) understand how those interact, but not sure how to pipe the 'create-task' command to a different group.

(So that, for example, a SG drone might be able to send LG miners to its location ... or a non-miner drone running as an Agent can scout out deposits, and then send mining drones to dig it out.)

Hi everyone,

Just noticed "adaptive docking". I didn't see the drones doing that before, but now they are and it causes a lot of crashes around the docking location.
Is there any way to disable it?

I can't find it in the arguments section, custom data, or code. Perhaps I overlooked it?

https://steamcommunity.com/sharedfiles/filedetails/?edit=true&id=3492922450 is my ship in it's current state if you want to give it a shot at trying to get the drones to move.

like, right now i dismantled the one in space, now they aren't waiting for it to do whatever so they can go next, they are trying to launch while connected to the connectors. 3 are idle, one is docking, the other is changing shaft. all are actually docked. they wont take off but they'll happily empty their hydrogen tanks trying. haha

yea i just get them reset, and not launch and if one of them is stuck in space, and i can't see the screen i just have to dismantle it.

Alright i've been having a hell of a time getting them started on teh server, they worked for a bit but when they get stuck and wont respond to commands i can't get them to get back in their paces. the drones and dispatcher have all been clear-storage-state 'd and i used a camera to run the create job task because issue

1) most of the job screens on the drones just go dark at some point so i can't use those. but i have camera job creation so that's fine i guess. recompiling a-menucommand block doesn't do it. sometimes the screen is in a different font and you can't interact with it.

2) they are all docked and on job creation they say 'ChangingShaft' while docked and they just sit there lol feel free to import and play around with the ship, i can't seem to make this script perform better than a single seat mining ship and i really want it to. Weather it's them just hanging out because they're in some queue waiting for one of the drones to hit the next step or what..

The logic is simple, look up "group-constraint" in the script arg reference. Regarding multi tasking work-around, probably I've meant using two dispatchers and two sets of drones differentiated by that value (you still can't have more than one task per dispatcher instance).

Hi @cheerkin, Thanks for the reply. You are totally right, they would collide, I was mistaken.

I see there is a group constraint, which you suggest can be used to differentiate between thruster and grid types. How can you set this up, and is it possible to create your own groups?
My goal is to have multiple tasks running from the same dispatcher. "assigning some "group-constraint"-like tag now seems as a quick dirty solution - until we get multi-tasking."
That is your comment from may 17th 2022, that is how I got the idea.