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
See the reply for a repaired version
http://forum.keenswh.com/threads/can-someone-correct-this-script.7368103/
I haven't tested it but here it is (lunchtime browsing at work)
What is wrong? D:
In this case, for example, a drill drone would:
STOP another sequence of timer blocks controlling forward motion
TURN OFF a pair of thrusters with control override (as a backup)
TURN OFF gyro override controls
TURN ON a beacon to indicate the drone is full and needs collection.
All of these things can be done with timers. This same program could, say, trigger additional refineries in a station or a return autopilot program in a different programming block. But this program wouldn’t need editing, because all you’d need to change is the name and actions listed on the timer block.
Just a thought.
I have no idea if it will auto-update! Please let me know.