Space Engineers

Space Engineers

70 ratings
Nanobot Build and Repair System Queuing / Display / Scripting (Maintained)
7
   
Award
Favorite
Favorited
Unfavorite
File Size
Posted
Updated
439.578 KB
29 Apr @ 5:55am
13 May @ 3:51am
8 Change Notes ( view )

Subscribe to download
Nanobot Build and Repair System Queuing / Display / Scripting (Maintained)

Description
WARNING!
- Please read the description and the original page too for details on the script.
- This script will not work correctly with other mod versions than the ones I posted bellow. Please use one of those versions as they are fixed to work with the script due to game updates.

Description
- Fixed version of the original script for the Nanobot Build and Repair System.
- Fixed issue where script was not compiling with the recent game updates.

Original Script & Credits
The original script was developed by Dummy08, but unfortunatelly he is not active on Steam anymore to maintain his work. I will try maintain this copy of the script.

The original script, description and documentation can be found at:
https://steamproxy.com/sharedfiles/filedetails/?id=867822734

Mode info-only
To display only the information without queuing any component builds in the assemblers, set the Argument value to info-only in the Programmable Block. After changing the argument, make sure to recompile and run the script again.

Mods
The script works with the following maintained Nanobot Build and Repair mod versions:

Nanobot Build and Repair System (Maintained):
https://steamproxy.com/sharedfiles/filedetails/?id=2111073562

Nanobot Build and Repair System - Original Resources:
https://steamproxy.com/sharedfiles/filedetails/?id=3099489876

Donate?
If you like to donate for my work, you can use the following link:
PayPal Donate[paypal.me]
104 Comments
MENINA DO PORAO 1 hour ago 
Is it working? Because it's not queuing any item to the assembler here.
GGdinkfamdog 6 hours ago 
@SKO85 I was using your version of the build and repair but i was still having problems. Ima try and trouble shoot again since im home from work but idk if it will have the same results.
Ambient 14 hours ago 
Just incase its not reported, it seems your version of this script/mod is causing crashes on dedicated servers. Testing with a few friends, after removing the mod file the crashes stopped happening.

We each had around 4-5 of the blocks placed each on our grids. Our grids were separated by a distance of about 4-5k km between them if that matters.
Perhaps you can look into it? The crashes occurred in a multitude of testing scenarios.
Crash on loading small or big ship in with projector (not every time, but enough to be a pattern)
Crash on loading grid with build and repair enabled (completely random this one)

I theorised it might be due to multiplayer synchronisation.
SKO85  [author] 18 hours ago 
@GGdinkfamdog, did you read the description? You need to use this version of the script with my version of the Build and Repair mod. The script does not work with the old version of the mod.
GGdinkfamdog 10 Sep @ 8:32pm 
So after trouble shooting its the scrpit its not liking something i just dont know what.
GGdinkfamdog 10 Sep @ 8:05pm 
I have a problem with both the script and the regular one, i switched from the old version to your maintained one but idk if my game liked it because now it wont build and its also trying to grind blocks that are apart of anoter grid. So idk if i did something or if i fucked it up when i changed.
SKO85  [author] 10 Sep @ 12:59am 
Script is not updated yet. Mod was reverted too due to an issue I came across with the game update. Working on it...
Entry45 10 Sep @ 12:38am 
does it take time to update?

steam is still saying may 13th
SKO85  [author] 9 Sep @ 2:40pm 
Mod has been updated. I will check the script and align with the mod versions asap. If something does not work with the script, please give me some time to fix it as I am testing the major mod changes and a game updated dropped too that might affect the mod or script.
Ernos 9 Sep @ 2:37pm 
Also to clarify, since I can't edit my last comment. This issue was happening before the Apex survival update, so best I can tell it's not an issue caused by this update