Hello again. Apparently I am now getting the same issue @Dragon Engineer had. My drones undock but don't move away after that, they just point at the direction they are suppossed to go. This is the drone model I am currently using. I have gone over it time and time again and can't find what I did wrong. https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=473094698

@Marcelo
Can I see two large thrusters on the back? The script has had issues automatically detecting large thrusters for some reason, (sometimes does sometimes doesn't) so it would be pointing the way it should, but not thrusting, try swapping them out for small thrusters (if that is the case) see if it works then,

Space engineers just became an RTS as well. This couldnt be any cooler.

I havent tried it yet but I have read all the features in it and some of the comments what I think should be added as well are

- Mine, repair/build and grind options for drones (repair/build and build might not be possible due to script limitations. Hopefully there is a way around it)
- remotely operated construction of ships and vehicles
- Hot-keys
- Give command one after the other where it would complete one first and then do the next task.

These are all RTS inspired ideas, which would allow players to play this as an RTS and would make managing and maintaining a large fleet easier.

EDIT: Just throught of this: How would the ai classify the ship as destroyed or will the person in control have to give the order to stop attacking?

just make a mods of this. more simple.

@Bad Humour
Thanks for the suggestions!, Utilities management is on the way, (welding, grinding, salvage resupply) but it's still got quite a while to go yet, and remotely operated things is possible, just using the vanilla P-block! I'll make a separate suggestions list at the top too,

Regarding destroyed blocks, it's a combination, grids below a certain size are disregarded, at the moment, anything larger and you have to manually re-designate, It's something I'm working on, and trying to get keen to release some more API for!

Originally posted by Rdav:

@Bad Humour
Thanks for the suggestions!, Utilities management is on the way, (welding, grinding, salvage resupply) but it's still got quite a while to go yet, and remotely operated things is possible, just using the vanilla P-block! I'll make a separate suggestions list at the top too,

Regarding destroyed blocks, it's a combination, grids below a certain size are disregarded, at the moment, anything larger and you have to manually re-designate, It's something I'm working on, and trying to get keen to release some more API for!

Cool cant wait for updates

***No Blueprints no script***
Hi Radav I dont seem to have any blueprints showing up in my library. Am I missing something here? Theres no mod to load in the mod loader and nothing for me to find in the scripter library.

Subscribing to the blueprint on this page should put it in your blueprints library (with other ship blueprints), right at the bottom with the other workshop ships, sometimes it takes a while to come up there, let me know if it's still not showing up and I'll see what I can do

Found what I think is a bug or a setup issue. I was setting up the script and it displays the interface but it doesnt allow me to control it with any of the non-default arguments.

The Programmamble block also states "Caught exception during execution of script:Object reference not set to instance of an object"

The programmable block was also a part of a sub-grid of the ship maybe that is what's causing the issue.

@Bad Humor
Thanks for the bug-report, sounds like the script has 'crashed' if you recompile the mothership script (press edit, check code, ok, remember and exit) it should work again, did you press anything on the menu before this happened, or was it just when setting up?

Originally posted by Rdav:

@Bad Humor
Thanks for the bug-report, sounds like the script has 'crashed' if you recompile the mothership script (press edit, check code, ok, remember and exit) it should work again, did you press anything on the menu before this happened, or was it just when setting up?

I did recompile it a couple of times but the error persists. Its my own setup not from the your own modular setup but it should still work as there is no difference other than the programmable block being on a sub-grid. I tried it on the main grid and I still have the issue.

And it doesn't say 'Missing text panels' in the programmable block at all, hmm very odd, it should stop automatically if any key-components aren't detected? Does it happen instantly after it's placed or does it happen after you try navigating the menu? Lastly do you have any sensors on your ship?

Originally posted by Rdav:

And it doesn't say 'Missing text panels' in the programmable block at all, hmm very odd, it should stop automatically if any key-components aren't detected? Does it happen instantly after it's placed or does it happen after you try navigating the menu? Lastly do you have any sensors on your ship?

It now happens every instant I place the programmable block and load the script but I first found it when I was trying to navigate the menu.

EDIT: Yea it happens the first time it runs

I have stopped the crash from happening by manually running the default argument by just pressing run without the timer block.

Its like the script is running too fast

@Bad Humour
Hmmm, that is weird, how many times can you press it before it stops? also, the sensors are there many on your ship? I have a feeling they could be detecting something that's not a grid, and going funky because of it,