Mother DocsMother Docs
Buy me a Coffee
Steam Workshop
Discord
  • Cheatsheet
  • Mother OS (Ingame Script)
  • Mother GUI
  • Mother Autopilot System (MAPS)
  • Mother Core (Script Framework)
  • Mother Dev Tools
  • Motherland
  • Powered by Mother
  • Brand Guidelines
Buy me a Coffee
Steam Workshop
Discord
  • Cheatsheet
  • Mother OS (Ingame Script)
  • Mother GUI
  • Mother Autopilot System (MAPS)
  • Mother Core (Script Framework)
  • Mother Dev Tools
  • Motherland
  • Powered by Mother
  • Brand Guidelines
  • Cheatsheet
  • Mother OS (Ingame Script)
    • Getting Started

      • Upgrade Guide
      • Installation
      • Command Line Interface (CLI)
      • Configuration
      • Modules
    • Core Modules

      • Activity Monitor
      • Almanac
      • Block Catalogue
      • Intergrid Message Service
      • Local Storage
      • Merge Block Module
    • Extension Modules

      • Air Vent Module
      • AutoLCD Module
      • Battery Module
      • Terminal Block Module
      • Cockpit Module
      • Connector Module
      • Display Module
      • Door Module
      • Gas Tank Module
      • Hinge Module
      • Landing Gear Module
      • Light Module
      • Piston Module
      • Programmable Block Module
      • Rotor Module
      • Screen Module
      • Sensor Module
      • Sorter Module
      • Sound Block Module
      • Thruster Module
      • Timer Block Module
      • Wheel Module
    • Compatibility
    • Troubleshooting
    • Examples
  • Mother GUI
    • Getting Started

      • Installation
      • Configuration
    • Commands
    • Menus
    • Views
    • Examples
  • Mother Autopilot System (MAPS)
    • Getting Started

      • Upgrade Guide
      • Installation
    • Modules

      • Flight Planning Module
      • Map Module
      • Flight Control Module
      • Attitude Module
      • Docking Module
  • Mother Core (Script Framework)
    • Getting Started

      • Upgrade Guide
      • Installation
      • Architecture Overview
      • Managing Script Size & Complexity
    • Building A Module
    • Mother CLI (Console)
    • Core Modules
      • Activity Monitor
      • Almanac
      • Block Catalogue
      • Clock
      • Command Bus
      • Configuration
      • Event Bus
      • Intergrid Message Service
      • Local Storage
      • Log
      • Terminal
    • Utilities

      • Color Helper
      • Number Helper
      • Security
      • Serializer
    • Testing
    • Tutorials
  • Mother Dev Tools
  • Motherland
  • Powered By Mother
  • Brand Guidelines

AutoLCD Module

The AutoLCD module lets you swap what a screen shows from a Mother command. It works with Automatic LCDs 2 (AutoLCDs) by MMaster, which draws live ship data on LCD panels and cockpit screens.

  • Defining Views
  • Commands
    • autolcd/print
    • autolcd/clear
  • How It Works
  • Responses
  • Faster Updates

Requires Automatic LCDs 2

Mother does not draw anything itself. It copies a named view into the target block's Custom Data and AutoLCD does the rendering. You must run AutoLCDs in a programmable block on the same grid - which you should, because it's great.

Defining Views

Views live in the [autolcd] section of the Mother OS programmable block's Custom Data. Each key is a view name and the value is the AutoLCD command text for one screen. We use the | prefix for multi-line values.

Automatic LCDs 2 Full Guide

Mother OS > Custom Data
[autolcd]
PowerView=
| Power {T:*}
| Working {TG:Batteries}

HydrogenTanksView=
| tanks {TG:*} hydrogen
| StopDistance
| StopTime
  • Mother copies the text exactly as written. It does not interpret {T:...}, ; separators or // comments.
  • Mother's $VARIABLE and {{parameter}} substitution does not apply to [autolcd] views.
  • View names are case-insensitive.
  • Edits to the section are picked up automatically. You do not need to run boot.

Commands

autolcd/print

Copy a view to a screen. AutoLCD then renders it.

autolcd/print <Block|Group|#tag>[:SurfaceIndex] <View>
ArgumentDescription
TargetA block name, group or #tag. Add :<index> to select a surface on a cockpit or other multi-screen block. The index defaults to 0.
ViewThe name of a view in the [autolcd] section.

If the target matches several blocks, each one is updated.

Example

Terminal
; Show the power view on a text panel
autolcd/print "Engineering LCD" PowerView;

; Show the hydrogen view on the second cockpit screen
autolcd/print "Pilot Cockpit:1" HydrogenTanksView;

; Update every screen tagged #status
autolcd/print #status PowerView;

Use it from a command or Mother GUI menu to build screens that switch between views:

Mother OS > Custom Data
[commands]
ShowPowerView=autolcd/print "Pilot Cockpit:1" PowerView
ShowHydrogenView=autolcd/print "Pilot Cockpit:1" HydrogenTanksView

autolcd/clear

Remove the AutoLCD commands for one screen so AutoLCD stops drawing on it. Other screens on the same block are not changed.

autolcd/clear <Block|Group|#tag>[:SurfaceIndex]

Example

Terminal
autolcd/clear "Pilot Cockpit:1";

How It Works

AutoLCD reads its commands from the area of a block's Custom Data below the --- line. Mother only edits that area, so the rest of the block's configuration (such as [general] and [hooks]) is never changed.

Pilot Cockpit > Custom Data
[general]
; Mother configuration is untouched

---
@0 autolcd
Power {T:*}
@1 autolcd
tanks {T:*} hydrogen

Each @<index> autolcd header starts the commands for one screen. When you print a view, Mother replaces only that screen's section.

  • Custom data in the older AutoLCD layout (no --- line) is converted the first time you print to that block.
  • If the Custom Data is not valid, for example it has a broken [section], Mother leaves it unchanged and reports an error.
  • Views are written for a single screen. A view that contains an @<n> autolcd header or a --- line is rejected.

Responses

MessageCause
Block updated: <target> -> <view>The view was copied.
Cleared AutoLCD on <target>The screen was cleared.
AutoLCD view not found: <view>The view is not defined in [autolcd].
AutoLCD cannot update <block>: custom data is not valid iniThe block's Custom Data could not be parsed.

Faster Updates

Stock AutoLCD can take several seconds to react to a Custom Data change, so a printed view may feel slow to appear. Two small edits to the AutoLCD script reduce that to about half a second:

  1. Poll Custom Data every 0.5 seconds instead of every 5 seconds.
  2. Remove the random start delay on each command.

Warning

The author of AutoLCD asks that the script, and any derivation of it, is not republished. Keep a patched copy for personal use only.

Last Updated: 10/19/26, 3:04 PM
Contributors: lukejamesmorrison
Prev
Air Vent Module
Next
Battery Module