Master HUD

In the dairy year

Spring scouting, summer irrigation, a market tick, a wage notice. If every companion draws its own overlay, the cab becomes a pile.

Master HUD is one shared draw. Companions publish. The loop paints.

The feel

You still see the information. You do not fight five HUDs for the same corner of the screen. The tablet remains the deep desk. Esc remains the pause glance. This is the while-you-drive layer.

If the core is missing, companions draw themselves. Standalone still works.

How it works

This is mod 3 in the load order. Companions flip a dirty flag instead of rebuilding HUD strings every frame. Master HUD calls their fetch only when the data actually changed.

Three ways a companion can join:

Path	What it is for
Overlay	Read-only text stacked in a screen corner. Multiple overlays in the same corner stack by priority.
Subscribe	The companion draws its own content (spray trails, harvest marks). Master HUD owns the loop and menu-suspend.
Panel	Self-draw plus mouse input. Can be gated so only the server admin sees it.

While any menu or dialog is open, Master HUD suspends all drawing and input. Companions do not each have to check “is a menu open?”. A keybind or the settings app can hide one overlay without touching the others.

There are no settings of its own. Install it and leave it loaded.

Console: mhStatus lists registered overlays and panels and whether drawing is suspended.

How you use it

• Install it with the cores.
• Use each companion’s own settings for what that overlay says. This core does not steal their story.

The outs

Crop stress, depot, tax, income, world events, and tablet notices can register here. Your eyes stay on the field.

What you need

Optional bedrock. Worth it as soon as two overlays share a save.