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






On Youtube 


First of all - great script!
I'm trying to move one of my ideas into production using Mother OS, but I notice some strange behaviour:
Scenario: control multiple actuators (pistons+hinges) grouped by tags. For example 4 hinges with one tag, another 4 hinges with other tag, 4 pistons with own tag etc.
Observation: when I use distance or rotate commands for tags with couple blocks, sometimes rotors or pistons end with diferent values (like piston fulle extend even if it's not set to that distance)
Question: Do I make mistake? Or it's bug?
@LordKrono I appreciate the patience! I can look into this implementation a bit further, though I don’t see it scaling well beyond the most simple of setups. Nonetheless let me explore it a bit and perhaps there’s a golden nugget in here somewhere!
On that note, Mother v1.0 will be releasing VERY soon and has a ton of QoL stuff I think you guys will really like!
The Empire must grow.
Mother OS should be compatible with the Apex update and should be able to interface with the added farming blocks as Terminal Blocks. However, their API is limited unfortunately. (ie. you are unable to target the Farm Plot's lights via the programmable block API). I hope they improve this in future updates.
Would you mind sharing more info about your errors? What are you trying to do?
MOS is ALL about automation :) It exposes many of the common actions you’d otherwise reach for via a timer block or toolbar action. It also has “hooks” which give you access to some of the common triggers like connectors connecting, doors opening, etc. For more advanced triggers, the event controller is still your best bet, but I’ve done my best to cover the most common use cases (doors, landing gear, cockpits, sensors). I think one of the key benefits of MOS is your ability to copy and paste all of your automations via the custom data fields of your blocks with a very approachable syntax so you aren’t trying to learn an entire programming language just to use it.
The Command Cheatsheet gives an overview of the available commands, and the modules (ie. Door Module) will outline the available hooks to trigger your automations.
Happy engineering!