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
CargoAllP {CG:Fab Assemblers} {Assembling:}
InvListX {CG:Fab Assemblers} +component +ammo +tool +oxygen +hydrogenbottle +datapad +consumable
This suppresses output of items with zero count.
For example
InventoryX {C:Cargo 1}
If you haven't had a screen fail to work because of a typo, you haven't used AutoLCD's long enough yet.
Everyone does something like that at some point.
I've just tried small hydrogen tanks work with Tanks command as they always did. You are doing something wrong. They fall into the same category as all hydrogen tanks.
But it's also here to save you time. :P
http://steamcommunity.com/sharedfiles/filedetails/?id=407158161
We also got new shiny discord server community.
Everyone is welcome to join us :)
https://discord.gg/JVyN2eBc66
Example : invlistx T:* +ore
For eg:
[AutoLCD]
Inventory={T:Cargo} +ingot
[SomeMod]
Have it start when it finds [AutoLCD], have it break at the next [X] tag. And process your commands with an = so it can set var = value like the VRage MyIni would expect.
This mostly affects cockpits, as they have multiple LCDs and functions. Simple LCD panels tend to only have one mod target them at a time.
No other ways to do it in the script right now.
Echo Farming complete:
DetailsNon {LongestGrowBlockName} {Growth} {Grow}
{Growth} and {Grow} should be translated if there is other game language than english
Like 1/5 (of group blocks) or in precent like 20%
The max execution time on grid with ~200 commands on around 40 LCDs is in average: ~69us - that means that you can have around 200 such grids and it would still not be visible on game performance.
The problem is that the script is just too large and it may take long time (~6ms per tick) to compile parts of it as they are used which causes the server plugin to stop it. Once all the parts of the script had been executed at least once it runs smoothly as explained above. Unfortunately there is really nothing more I can do about that. The script is just too large.
cheers
I'm proud to announce that we now have an amazing brand-new discord server! You can join by clicking the following link:
https://discord.gg/JVyN2eBc66
So let's try it.. here is 7 days invite for now: https://discord.gg/hT6q8yQA
See you there :-)
Also I'm happy that you figured it out @Norway174 it's always great to see how people use this in their builds!
This looks so cool now! Thanks for your amazing script! :D
https://i.imgur.com/LjavOMv.gif
And here is the full custom Data if anyone is interested:
Center << Build and Repair >>
Echo
PropBool {G:BuildAndRepairGroup1} {OnOff} {[1] Build and Repair:} {Active} {Offline}
PropBool {G:BuildAndRepairGroup1} {BuildAndRepair.AllowBuild} {[2] Can Build Projections:} {Yes} {No}
Echo
Center << Projector >>
PropBool {Ship Printer Projector} {OnOff} {[3] Projector:} {Active} {Offline}
Working {Ship Printer Projector}
I don't have much experience with how to organize it or manage community in it so I would definitely need some help from trusted people like you. I would also probably not dedicate it only to this script, but make it more about the community where people would keep in touch, have fun, relax, discuss and help each other with whatever. I really don't have any specific idea it was just a random thought I've had.
Maybe I will just make some bare bones server that we will shape together as a community and we will see what will happen. Maybe it will be just 3 of us there and 1 will be permanently offline (Kham), second one will not respond most of the time (me) and third one will be sad that he joined such server :-D
These comments and discussions are kind of difficult to keep track of, but I'm not sure if there would be enough interest and we've already made it 10 years without it so it may not be really necessary that's why I'm asking you :-)
As for the projector, the % number should work just fine. Thank you for the amazingly fast update! <3
Details command shows status of farm plots more reliably and removes Color tags that don't work in standard LCD text
Working command now shows percentage of number of blocks welded on projectors
Added title override feature for Oxygen commands (check guide for Oxygen command)
Fixed unused variable warning
Some minor optimizations
Enjoy :-)
@Smirkyguy I don't think they have any properties that can be read like that. I will try to implement something to get status of farm plots.
@Norway174 based on quick look at the code that you linked you are trying to read Action which the PropBool command cannot do (it can read only Properties).
Yes, projector completion bar would be possible but it would probably require new command if I wanted to also show progress bar and that means overhead in terms of code size which we are dangerously close to limit, I was thinking maybe including it in Working command which would show the percentage but no progress bar not sure if that is sufficient.
Love the script! But I was wondering, is it possible to use PropBool with modded blocks? Such as Nanobot Build and Repair?
I wanna display if a BAR is set to Allow Build or not.
I've got this Custom Data here set up:
Center << Build and Repair >>
Echo
PropBool {G:BuildAndRepairGroup1} {OnOff} {Build and Repair:} {Active} {Offline}
PropBool {G:BuildAndRepairGroup1} {AllowBuild} {Can Build Projections:} {Yes} {No}
The first line shows, the second does not. I'm fairly certain the correct keyword should be "AllowBuild". As seen here: https://github.com/SKO85/SE-Mods/blob/f54397fd2645736d470fafc506b24107f53113df/SKO-Nanobot-BuildAndRepair-System/Data/Scripts/SKO-Nanobot-BuildAndRepair-System/NanobotBuildAndRepairSystemTerminal.cs#L615
Or maybe I'm just reading it wrong? And that's not the correct keyword at all? Any help and guidance would be greatly appreciated. Thank you!
Thank You MMaster for this awesome script, and for putting up with our crazy ideas. :-)