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
"amount {G:interior turrets} interiorturret doesn't return anything. However, running amount on its own, will eventually show the interior turrets.
Has anyone else had this problem?
void ItemsConf() {
// ITEMS AND QUOTAS LIST
// (subType, mainType, quota, display name, short name)
// VANILLA ITEMS
// ORE
Add("Iron", "Ore", 0, "Железо");
Add("Gold", "Ore", 0, "Золото");
Add("Stone", "Ore", 0, "Камень");
Add("Cobalt", "Ore", 0, "Кобальт");
Add("Silicon", "Ore", 0, "Кремний");
...
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.