It'd be handy to have a "Hooks" cheat sheet in the same style as the Commands cheat sheet.

I see the potential of this script, it's incredible, but i lack programming knowledge and there's not much examples. I would like if you could publish a step-by-step beginner guide to setup LCDs and do some basic tasks for ships or other grids. I love automation and would like to use more heavily Mother os, but I need more help I think. Thank you!

Best scripting i have used!!! Still just getting started with all the hooks and commands but would definitely rate 10 out of 5 stars

I can recommend trying the discord server - and ask there - Awesome community !

Is there an example/tutorial world available somewhere? Currently I'm trying out the dock command, but nothing is happening. I have probably missed something but it's not obvious. I'm able to send a flightplan to a ship to fly to a waypoint and then attempt docking. Both acknowledges the request but nothing happens.

Other than that I have been setting up fairly complex ship automation (as far as you can get without using complex conditions) and having a lot of fun. :-)

Btw Air Vents appears sensitive to extra white space chars, especially around pipe chars. Be careful with indentation to improve readability. And use tags whenever possible instead of block groups, it's awesome! No more triggering stuff on other grids that were recently connected.

Hi, this script sounds quite interesting! I used "easy automation" quite heavily for many of builds but my great complain it is not responsive while doing one thing. So my question is: Is your script kind of "multithreaded"?
To clarify what I mean: Imagine an automation where a rotor rotates very slowly into position. Can your script (while the rotor is going) call another piston, rotor or light and still control the first rotors end position?
Or another scenario: For a complex mechanical landing gear, pistons and hinges need to be moved depending on each others position. Let's say a piston should extend to 5 m, but at 2 m, another pistons needs to be retracted to a certain position. Is that something your script can currently do?
And last question: Can you abort current ongoing movements of rotors / hinges / pistons? Just in case you tell a rotor to go to a specific angle but then you need to change or stop that.
Thanks in advance,
Tom

Hi @Kool_Majster!

You and me both, though I'm secretly hoping they just extend the mod API to enable these types of tools with fewer restrictions. The character count restriction is a real doozy. I've done my best to design Mother for future adaptation to SE2 but it's early days still.

I would like to see this as well as the mmaster LCD functionality, as an vanilla feature in Space Engineers 2.
Really great Idea and user friendly with all settings in the custom data

I checked also group access and individual - each have the same results - it seems that not every block listed have set upper and lower limits which cause issues

Hi,

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?

@holocene MOS requires a remote control block so that could be the issue? I’ve run her with most of the new blocks from Apex and haven’t had issues so hopefully this is it!

@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.

I tried to load the OS onto a large grid freighter I built, and kept getting block errors. I’ll see if I can scrounge up the log when I get a chance! Thanks for the reply, it’s rare to see such a helpful and responsive mod author 🙏

Hello, I added a request for a feature that I think could be very useful for the pistons in the appropriate section but, having received no response there, I try to point this out here. I apologize for any disturbance, I do not want to seem oppressive, it's just to understand if I have proposed something useful. Thank you so much for your wonderful work!

Hi holocene!

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?

Hello, will this be updated for the Apex Survival DLC? I'm getting errors and it seems to be related to it not knowing what to do with those blocks

awesome to hear! thanks for informing me about this stuff

Hi Oddbase, it’s a great question!

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!

hey! does this have anything relating to automation in it? i really want to have an operation system that automatically detects certain things and does decisions based off those things. like an event controller but more options basically

Hey @ThaScadian!

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

Is there any way to indicate when to stop looking in Custom data?

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

Hi @Lilaqz! It’s a great question :) yes Mother should avoid asteroids in space as it uses the remote control blocks collision avoidance by default. Asteroids also don’t typically appear directly in your flight path while flying. I just flew 1000km last night without an issue.

Happy engineering!

i have a question, when its going from gps to gps in space will it avoid asteroids that it might collide with?

JAPAN EMPIREEEEE!!!

Loving this mod. Especially the hooks grant You so many ways to automate without needing a couple of additional mods/scripts. It is just great. Thanks for making this!

@Tuggs, these warnings shouldn't cause any issues booting and using Mother OS. As long as you see something in your terminal window after clicking Save, then you should be good to go!

May 4
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

Mother OS is now update and work as expected with the new Fieldwork update :) Happy engineering!

Hi all, the latest update has broken a few items in Mother and I am troubleshooting it now! Hoping to have a fix out with a bunch of new hooks very soon!

Thanks for your patience and enjoy the Fieldwork update!

Hey Bakeneko, I'd recommend hoping over to the discord channel! I'd be happy to help if you can provide a code snippet for your custom data field. Cheers

https://discord.com/invite/PrrmBujmXQ

Hello, first of all I want to say I appreciate a lot the work you are doing with this mod, I actually watched every youtube video you made about it. The problem is that the custom data for the almanac is not working on my current playthrough, I am trying to increase the scale to 10000m and changing the center with a GPS point but nothing changes. I have tried putting the custom data in the LCD as well as in the PB. I have tried several values and different formats, have also tried without putting the ini stuff like "[general]". I dont know what I am doing wrong.

@NeedyThunder thanks for letting me know! I’m hoping to push an update tomorrow and should be able to fix this in time :) Cheers

Is anyone else having issues with hooks onUnlock function? It seems to only trigger the function once the landing gear or connector is no longer able to connect to something rather than when the block actually unlocks.

Three Words... I LOVE IT

Hey Space Engineers :)

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

Hi all!

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/

The auto docking is supposed to be the "press and leave it" feature, but I think I'll just gonna watch it while thinking how cool it is, haha!
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!

Hi all!

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/

THANK YOU!!

Hi @ilsa, great question! I am working on this now and hope to have a solution soon :) For now, commands run sequentially.

This is outstanding! Is it possible to run commands sequentially? ie: I want to move a rotor to 0, and THEN rotate a hinge to 45 after the rotor has completed it's movement? One option would be to use a wait with the longest possible required time, but then if the rotor only has to move a little, there is a very visible delay.

@Iron_Fiore I'd love to keep you in the loop as I build out auto docking! I really appreciate the support and enthusiasm so keep it coming :) If you haven't already, hop on to the Discord server where the chats about feature dev and bugs is a bit more vibrant.

Thanks for the support!!

The autodocking feature - nice! :-)

@Agentluke, That is massively exciting to hear. I've using brute force to make Mother handle docking with some success, but what your describing sounds like a dream. I'd love to help play test anything you develop. I don't have a lot of coding experience, but I have 5,000 hours in SE and I can absolutely put Mother to the test.

Forgive my enthusiasm :)

@Iron_Flore thanks for jumping in! Landing/docking with AP is not within the capabilities of Mother...yet. But I am very close to an auto-docking module that will enable thi,s and shouldn't require you to worry about settings on the remote control block. Mother will allows the grids to communicate and share info about docking (connector px, approach distance/course) so you won't need to do much aside from tell your ship to dock with another. I'm hoping to have this out for testing in a week or two. For now, I still recommend using AI blocks for that "last mile" as the remote control block isn't great in tight spaces or close to a planet's surface.

Cheers!

@Lokey_71 great consideration and as Iron_Flore noted, Mother currently allows you to encrypt your comms. You can see more about this on the Security page of the documentation. I do intend to expand this further, where you can communicate on multiple channels, each with their own passcode. Almost there ;)

https://github.com/lukejamesmorrison/mother-docs/blob/main/IngameScript/Modules/Core/Security.md

This is very cool

@Agentluke, Mother seems to turn collision avoidance on at every way point, this makes lading on autopilot impossible. It would also be nice to get some more handles on the remote block, specifically the forward direction options. It can be done with timer blocks but it's ungainly.

@Lokey_71, Pass keyed encryption is already a feature, you can set it up in the custom data.

Very interesting!
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?

@Agentluke, I'm very sorry to hear that. Better luck next time.