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
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!
You can definitely use MOS with Automatic LCDs :) MOS conforms to the recommended Custom Data config format, but AutoLCDs does not. As a result, you should put all MOS config before a triple dash line “—-“ and AutoLCDs config after.
PB > Custom Data
[general]
…
[commands]
…
—-
echo AutoLCDs stuff
PowerStored {T:*}
…
MMaster covers this in the AutoLCDs documentation under the Compatibility with other scripts section :) I hope this helps!
https://steamcommunity.com/sharedfiles/filedetails/?id=407158161#:~:text=not%20considered%20comment!-,Compatibility%20with%20other%20scripts,-Keen%20has%20added
I'm trying to implement the tag system with AutoLCD2 so that I can keep that script from eating too many resources at all times. But it seems it cannot find the tags if there is anything that is not a part of motherOS in the custom data
Happy engineering!
When checking the code, it has an error.
Program(720,60): Warning: The field 'Program.e.?' is never used
Program(326,301): Warning: The field 'Program.e.?' is assigned but its value is never used
Thanks for your patience and enjoy the Fieldwork update!
https://discord.com/invite/PrrmBujmXQ
Version 0.2.10 is now out and comes with Tags. Tags allow you to group blocks without overcrowding your Terminal tab with block groups. Enjoy!
https://youtu.be/PkYn7pcir70
Version 0.2.9 is released with some improvements to the reliability of auto-docking. I recommend using this in space for now, but feel free to try with planetary procedures as well. Mother has several fail-safes that should prevent crashing but I am still working on better path finding due to some collision avoidance challenges of the remote control block.
You can now print custom messages to LCD screens using the `screen/print` command.
Enjoy :)
https://lukejamesmorrison.github.io/mother-docs/
Already tried it and it's super easy. Maybe the pathfinding capability needs to be improved, 'cause the vanilla Remote Control block is still kinda buggy when handling the docking in rather tight space. But Mother is already a game changer at this current state tho.
Can't wait to use Mother's auto docking feature inside the atmosphere. (next update maybe? :3 )
Anw, awesome update!
Version 0.2.8 finally comes with the beta version of auto docking! Please give it a try and let me know what needs to be improved :)
I have also released a major improvement to Mother's documentation and I look forward to your feedback!
https://lukejamesmorrison.github.io/mother-docs/
Thanks for the support!!
Forgive my enthusiasm :)
Cheers!
https://github.com/lukejamesmorrison/mother-docs/blob/main/IngameScript/Modules/Core/Security.md
I love the idea as well for communication with other grids running Mother, which does make me wonder about the security concerns of using it. For instance, would a hostile be able to fly by and just @thatGuy SelfDestruct?
Sadly Keen didn’t feel I was the best candidate for their open roles at the moment. It’s very unfortunately as I’d love to work on this incredible project, and feel that I made a pretty compelling case. I’ll just keep making Mother more awesome and we’ll see what happens ;)
Good for you! Hwayting!
Thanks for your support and encouragement @Unruly, @ColTeH!!!!