Instal Steam
login
|
bahasa
简体中文 (Tionghoa Sederhana)
繁體中文 (Tionghoa Tradisional)
日本語 (Bahasa Jepang)
한국어 (Bahasa Korea)
ไทย (Bahasa Thai)
Български (Bahasa Bulgaria)
Čeština (Bahasa Ceko)
Dansk (Bahasa Denmark)
Deutsch (Bahasa Jerman)
English (Bahasa Inggris)
Español - España (Bahasa Spanyol - Spanyol)
Español - Latinoamérica (Bahasa Spanyol - Amerika Latin)
Ελληνικά (Bahasa Yunani)
Français (Bahasa Prancis)
Italiano (Bahasa Italia)
Magyar (Bahasa Hungaria)
Nederlands (Bahasa Belanda)
Norsk (Bahasa Norwegia)
Polski (Bahasa Polandia)
Português (Portugis - Portugal)
Português-Brasil (Bahasa Portugis-Brasil)
Română (Bahasa Rumania)
Русский (Bahasa Rusia)
Suomi (Bahasa Finlandia)
Svenska (Bahasa Swedia)
Türkçe (Bahasa Turki)
Tiếng Việt (Bahasa Vietnam)
Українська (Bahasa Ukraina)
Laporkan kesalahan penerjemahan
The amount if items is one thing, but the weight of ores in "k" and "m" is irritating. Can that change to "t", "kt" and "Mt" (tons, so isnteat of "+1.2m Ore" to "1.2 kt Ore"?
So kg, t, kt, Mt, Gt (Megatons, gigatons, i guess, never will be more than gigatons..
For example "Center (#FF77FF) Hello, World
so that the Color of that text is in the code?
or PowerV {#AA0000 Reactor} ?
Would be AWESOME.
Thanks for getting back to me. I suspected as much. I'm trying to decide between implementing your solution or learning how to code and building my own script.
I was thinking of doing something like:
- Sensor triggers and runs a programmable block with an argument. Maybe the sensors location name as the argument.
- The programmable block receives that argument and writes it to its own custom data field.
- Using the AutoLCD Command: CustomData, display the field on a text panel somewhere.
- Sensor no longer detects anything and runs the programmable block again but this time with a key phrase as the argument that would have the PB search and delete the sensors location name from the Custom Data field.
Every sensor I place would do the same thing but would submit its own unique location as the argument. So basically the programmable block would just be recording a live list of locations.
for example
PropBool {block name} {PropertyName} {Text before value} {true text} {false text}
becomes something like
PropBool {yourlightname} {OnOff} {Sensor Status:} {Active} {Clear}
You can play around with the text in the Text Before, True Text and False Text sections to match your own needs.
I thought using the command: working would but it only shows its on/off state, not whether it's been triggered.
To monitor blocks only on the grid the PB is placed on you can use T:*
Or to monitor on all parts of the 'construct' such as attached via rotor or piston you can use C:*
More information on these can be found near the top of the guide in the sections titled
"Same grid blocks filtering" and
"Same construct blocks filtering"
@0 AutoLCD
DamageX {Miner}
it doesnt show me info about my ship. Could you tell me what can i do with this? Thanks for reply!