Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Maybe have two (or more) versions of the block, with different abilities? For instance, have a Mark1 BaRS that can only grind or weld blocks connected to it's own grid? Then a Mark2 with a higher component cost that can grind or weld blocks within range. Maybe a Mark3 with the collection and cleanup features?
I would like to suggest a bit more options for 'fine tuning' how the BaRS goes about building blocks. For instance, I noticed that when using the assembler auto-queing script, even though it ques up parts to build one particular block at a time, tie BaRS actually spreads the requested parts among every block that uses said parts. This means that, for example, if I place doen first a refinery, then some upgrade modules, even though it ques up the parts to build the refinery first, it'll spready some of the parts to the upgrade modules, and thus the refinery takes longer to be completed since it has to wait for additional parts. This may be a byproduct of having multiple BaRS on the same grid at once, but it would be nice to have the option of telling them to fully construct one block first before moving on to another.
I put a option in where you can now switch immediately pushing of 'items' on/off.
Hope this helps
also...not complaining by any means, but the new xml feature to edit default values does NOT include an option to default to "on" for your new item pusher functionality.
Without to be a know-it-all :-)
The option is there (but I was to lazy to document it) and default is 'on'. (This default works only for new placed blocks, allready placed block will behave as before, with this option being 'false').
If you type /nanobars /cpsf you get an xml including all supported options.
would be great for designing a ship then going through and armoring or adding a reinforced skeleton to it.
But you can ask you to add to it the opportunity to hack.