Store Page
Space Engineers
All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Space Engineers

Store Page
Space Engineers >  Workshop > Dummy08's Workshop > Nanobot Build and Repair System > Discussions
Nanobot Build and Repair System
Description Discussions96 Comments3417 Change Notes
 This topic has been pinned, so it's probably important
Dummy08  [developer] 29 Oct, 2017 @ 5:39pm
2
Block Settings
Settings could be stored either per PC:(..\SpaceEngineers\Storage\857053359.sbm_NanobotBuildAndRepairSystem\ModSettings.xml)
or per World:
..\\SpaceEngineers\Saves\XXXXXXX\MyWorld\Storage\NanobotBuildAndRepairSystem_NanobotBuildAndRepairSystem\ModSettings.xml.
Per world setting allways superseed, PC settings.

Setting file on single player game:
You can create settings file by typing either:
/nanobars -cwsf (for a world settings file)
/nanobars -cpsf (PC settings file)
into ingame chat (type /nanobars for help)

Settings file on dedicated server:
On dedicated servers it is intentionaly not allowed to execute the commands to created the settings file. Otherwise any client would be able to influence the server configurationv (e,g. if the serve admin decides to have an server wide config file, and any client would be allowed to create an world config file, this would change the setting of the server. Even if the values will be the same, it would be nightmare for the admin to check all hosted worlds, after he made a change to the server wide config file.)

So that sayed, as server admin you could create a template file using a simple/empty world (with this mod) running on a single player version, change any setting he like and upload the file to the server as server wide setting or world specific setting.


The settings file allows to control:
Setting
Range
Purpose
Range
1..1000m (75m Default)
The maximum operation range of the block. (Small version allways 1/3)
MaximumOffset
0..1000m (150m Default)
The maximum offest of the operation area from center of the block. (Small version allways 1/3)
WeldingMultiplier
0.001..1000 (1 Default)
Additional multiplier for welding performance
GrindingMultiplier
0.001..1000 (1 Default)
Additional multiplier for grinding performance
AllowedSearchModes
Grids BoundingBox
Use this to allow/disallow the search modes
SearchModeDefault
(Grids default)
Default mode for new blocks
AllowedWorkModes
WeldBeforeGrind
GrindBeforeWeld
GrindIfWeldGetStuck
WeldOnly
GrindOnly
Use this to allow/disallow the working modes
WorkModeDefault
(WeldBeforeGrind default)
Default mode for new blocks
AllowBuildFixed
(false default)
If true user can't change 'Build new'
AllowBuildDefault
(true default)
Default or fixed value for 'Build new'
UseIgnoreColorFixed
(false default)
If true user can't change Ignore Color
UseIgnoreColorDefault
(true default)
Default or Fixed value for 'Use Ignore Color'
IgnoreColorDefault
(<float>321</float><float>100</float><float>51</float> default)
Default or fixed color value for ignore color
UseGrindColorFixed
(false default)
If true user can't change Grind Color
UseGrindColorDefault
(true default)
Default or Fixed value for 'Use Grind Color'
GrindColorDefault
(<float>321</float><float>100</float><float>50</float> default)
Default or fixed color value for grind color
UseGrindJanitorFixed
(false default)
If true user can't change 'Janitor grinds' optiions
UseGrindJanitorDefault
(NoOwnership Enemies default)
Default or fixed janitor options
AreaSizeFixed
(false default)
If true user can't change this option
PriorityFixed
(false default)
If true user can't change weld/grind priority
CollectPriorityFixed
(false default)
If true user can't change collect priority
PushIngotOreImmediatelyFixed
(false default)
If true user can't change this option
PushIngotOreImmediatelyDefault
(true default)
Default or Fixed value for 'Ingot pushing'
PushComponentImmediatelyFixed
(false default)
If true user can't change this option
PushComponentImmediatelyDefault
(false default)
Default or Fixed value for 'Component pushing'
PushItemsImmediatelyFixed
(false default)
If true user can't change this option
PushItemsImmediatelyDefault
(true default)
Default or Fixed value for 'Items pushing'
CollectIfIdleFixed
(false default)
If true user can't change this option
CollectIfIdleDefault
(false default)
Default or Fixed value for 'Collect only if idle'
SoundVolumeFixed
(false default)
If true user can't change this option
SoundVolumeDefault
0..2 (1=50% default)
Default or Fixed Sound volume
AllowedEffects
(WeldingVisualEffect WeldingSoundEffect GrindingVisualEffect GrindingSoundEffect TransportVisualEffect default)
Which kind of effects should be shown/played
ScriptControllFixed
(false default)
if true script control is disabled
FriendlyDamageTimeoutTicks
-
Wait time after friendly damged blocks get repaired
MaximumRequiredElectricPowerStandby
(0.00002 default‬)
Power consumption while switched on but nothing to do
MaximumRequiredElectricPowerTransport
(0.01 default)
Power consumption while transport
MaximumRequiredElectricPowerWelding
(0.002 default)
Power consumption while welding
MaximumRequiredElectricPowerGrinding
(0.0015 default)
Power consumption while grinding
SourcesAndTargetsUpdateIntervalTicks
-
Interval for checking for new block to grind weld (!change wisely)
MaxBackgroundTasks
(4 default)
The Mod uses up to N background task to search for damaged/grind/collected blocks/items

If you would like to change some settings you don't have to keep all entries in the file, as long as you the keep the XML syntax and the 'version' info. E.G if you like to change the 'Range' and 'IgnoreColorDefault' only you could create a file like:
<?xml version="1.0" encoding="utf-16"?> <SyncModSettings xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Version>5</Version> <Range>75</Range> <Welder> <IgnoreColorDefault> <float>321</float> <float>100</float> <float>51</float> </IgnoreColorDefault> </Welder> </SyncModSettings>
This will keep all other values at there defaults and maybe more important you will automatically received future enhancements(e.g. new WorkModes)


Limit Blocks:
To limit the BaR Systems per user you could add the following to your servers Sandbox.sbc <BlockTypeLimits>
<dictionary>
<item>
<Key xsi:type="xsd:string">SELtdNanobotBuildAndRepairSystem</Key>
<Value xsi:type="xsd:short">8</Value>
</item>
..
Last edited by Dummy08; 20 Sep, 2019 @ 10:17am
< >
Showing 46-60 of 93 comments
Skallabjorn 30 Sep, 2019 @ 1:47pm 
is it possible to completely disable ( and have it not shown in options ) the grind enemy blocks option. That is have it off as default and not show as an item that can be turned back on in the controls?
#46
Marc 7 Nov, 2019 @ 2:48pm 
Dummy08 you have a list of the commands else where? some reason steam only let's me see half the command list above. not sure where the issue is, but it's annoying.
#47
Roknori 3 Dec, 2019 @ 4:41am 
Originally posted by Skallabjorn:
is it possible to completely disable ( and have it not shown in options ) the grind enemy blocks option. That is have it off as default and not show as an item that can be turned back on in the controls?

I'm actually curious about this also. The server I'm a part of would love to use this but we'd like to avoid people potentially abusing it for just remotely grinding other people's grids.

I see where you can disable the grind modes, but specifically the enemy blocks option being disabled would be nice.
#48
Erebus Alpha 27 Dec, 2019 @ 4:59am 
Is it possible to force the build & repair system to stop welding and grinding, if the ship gets damaged? I would prefer that this device not be used as a self-repair mechanism during combat.
Last edited by Erebus Alpha; 27 Dec, 2019 @ 5:00am
#49
KorTiK 2 Apr, 2020 @ 4:42am 
\SpaceEngineers\Storage\857053359.sbm_NanobotBuildAndRepairSystem\ - There are no such folders. And it doesn't. Where can I find them?
#50
Bodyboarder2528 24 Apr, 2020 @ 2:19am 
if build and repair subtype is this SELtdNanobotBuildAndRepairSystem whats drill and fills one
#51
Dummy08  [developer] 24 Apr, 2020 @ 2:52pm 
Originally posted by bodyboarder2528:
if build and repair subtype is this SELtdNanobotBuildAndRepairSystem whats drill and fills one
SELtdNanobotDrillSystem :-)
#52
Bodyboarder2528 24 Apr, 2020 @ 6:22pm 
Originally posted by Dummy08:
Originally posted by bodyboarder2528:
if build and repair subtype is this SELtdNanobotBuildAndRepairSystem whats drill and fills one
SELtdNanobotDrillSystem :-)
thanks
#53
Bodyboarder2528 24 Apr, 2020 @ 8:53pm 
will that also over small grid or is their a separate name
#54
Dummy08  [developer] 25 Apr, 2020 @ 1:58am 
Originally posted by bodyboarder2528:
will that also over small grid or is their a separate name
Ok the complete Answer is:
Large Block: SubtypeId = SELtdLargeNanobotDrillSystem
Small Block: SubtypeId = SELtdSmallNanobotDrillSystem
BlockPairName = SELtdNanobotDrillSystem
#55
Bodyboarder2528 25 Apr, 2020 @ 2:21am 
Originally posted by Dummy08:
Originally posted by bodyboarder2528:
will that also over small grid or is their a separate name
Ok the complete Answer is:
Large Block: SubtypeId = SELtdLargeNanobotDrillSystem
Small Block: SubtypeId = SELtdSmallNanobotDrillSystem
BlockPairName = SELtdNanobotDrillSystem
ok also issue is this didnt work
Limit Blocks:
To limit the BaR Systems per user you could add the following to your servers Sandbox.sbc <BlockTypeLimits>
<dictionary>
<item>
<Key xsi:type="xsd:string">SELtdNanobotDrillSystem</Key>
<Value xsi:type="xsd:short">8</Value>
</item>
#56
Dummy08  [developer] 25 Apr, 2020 @ 2:32am 
Originally posted by bodyboarder2528:
Originally posted by Dummy08:
Ok the complete Answer is:
Large Block: SubtypeId = SELtdLargeNanobotDrillSystem
Small Block: SubtypeId = SELtdSmallNanobotDrillSystem
BlockPairName = SELtdNanobotDrillSystem
ok also issue is this didnt work
Limit Blocks:
To limit the BaR Systems per user you could add the following to your servers Sandbox.sbc <BlockTypeLimits>
<dictionary>
<item>
<Key xsi:type="xsd:string">SELtdNanobotDrillSystem</Key>
<Value xsi:type="xsd:short">8</Value>
</item>
Most common mistake is not enable the general block limits mode. E.G. <BlockLimitsEnabled>NONE</BlockLimitsEnabled> -> <BlockLimitsEnabled>PER_PLAYER</BlockLimitsEnabled>
If you are unsure use the server GUI to do the settings.
Hope this helps
#57
Bodyboarder2528 25 Apr, 2020 @ 2:51am 
its on as assembles are limited will look further into it
#58
Bodyboarder2528 25 Apr, 2020 @ 7:55pm 
ok limits is working for assemblers and that but now drill and fill
https://imgur.com/a/QXzTLp2
#59
Dummy08  [developer] 26 Apr, 2020 @ 2:36am 
Originally posted by bodyboarder2528:
ok limits is working for assemblers and that but now drill and fill
https://imgur.com/a/QXzTLp2

This must be local issue, I've just tested it and it works in my environment:
Block Limit
Just make sure you add the right block name. In case of blocklimits you have to use the BlockPairName which is "SELtdNanobotDrillSystem".

By the way this is a game internal function that could not be influenced by a mod, so if it is not working you have to post your issue to keen :-)
#60
< >
Showing 46-60 of 93 comments
Per page: 1530 50