GGFeed
Menu
GGFeedLightyear Frontier

Lightyear Frontier automation: pipes, dump storage and three-recipe queues

Build a working 1.0 production chain, configure storage filters and diagnose blocked pipes, missing inputs and recipe queues in Lightyear Frontier.

Coverage: 1.0 · v1.0.2563

The quick answer

Connect a compatible storage Output to a crafting Input with Automation Pipes, provide Energy and queue a recipe. Add an output destination, then verify a full production cycle before expanding the network.

A farming mech overlooking fields and a homestead in Lightyear Frontier
Publisher screenshot · FRAME BREAK / Coffee Stain Publishing

What you need before connecting anything

Automation begins at Milestone 4 in 1.0, although its full range expands later. Open the Build Menu and hover over the Constructs you intend to use. The menu identifies which storage types have Inputs and Outputs. A building that stores an item is not automatically a valid source for every connection.

The new chain is storage Output → Automation Pipe → crafting Input. Pipes can also move goods between suitable storage Constructs. They consume Energy; the number of old Automator connections is no longer the main limit for new layouts. Keep the operating network within the Energy you can supply.

Build a chain you can troubleshoot

  1. Pick one recipe needed for your next delivery. List every ingredient before placing the network.
  2. Place a compatible source storage and put the required inputs in it. Confirm the relevant Output in the Build Menu.
  3. Connect that Output to the crafting Construct’s Input using an Automation Pipe. Read any placement error instead of assuming a visible line means a working connection.
  4. Supply the Energy required by the machinery and pipes. Check the actual Construct information for the cost of your chosen setup.
  5. Queue just that recipe for Auto Craft. Watch one full cycle before adding other work.
  6. Add suitable output storage and its connection. Confirm that the result reaches that destination and that storage space remains available.
  7. Run another cycle. A chain that worked once from ingredients already inside a machine may still have a broken supply path.

This small-chain test gives you a known working section. Expand it one connection or recipe at a time so a new failure has a small number of possible causes.

Use filters to make dump storage useful

Each storage Construct has its own Resource Filter settings. Configure destinations separately; changing one chest does not set a global rule for the whole farm.

Filter choice Effect in the network Practical use
Accept a resource Compatible connected Constructs may send that resource to the storage while capacity remains A destination reserved for a particular production output
Deny a resource Pipes cannot send it into that storage; adjacent pickup into it is prevented, and manual placement gives a warning Keeping unwanted goods out of a specialized destination
Category filtering Apply the chosen rule across the selected category Organizing a larger set of resources without editing each item individually

For a dump-storage design, first decide where each resource should end up. Set destination filters, connect the storage and try one item from each intended category. Check the receiving inventory. A connection diagram alone cannot reveal an overly broad filter or a full destination.

Resource Filters use discovered items. If the material you want is missing from the options, discover it before setting up a destination rule for it.

Understand the three-recipe queue

A crafting Construct can cycle through up to three Auto Craft recipes. If a queued recipe lacks ingredients, the machine skips it and tries the next available recipe. The sequence loops; removing a recipe updates the order.

That behavior is useful when several outputs share a machine, but it can conceal shortages. A busy machine is not proof that your most important recipe is being produced. If only the easy recipe keeps running, inspect the ingredients for the other two.

For an urgent delivery, simplify the queue temporarily or put the critical work on a separately supplied machine. That is a planning choice: it makes the target easier to monitor, rather than assuming the queue reserves materials or guarantees an output ratio.

Diagnose a stopped chain in this order

Symptom Check first Next action
Nothing leaves source storage The storage has an Output and the correct item Confirm compatibility in the Build Menu, then inspect the connection
Pipe placement is rejected The error and pipe length Reposition the endpoints; 1.0 blocks pipes too short to function
Machine is idle Energy and the full ingredient list Restore the missing supply before changing recipes
One queued recipe never runs Ingredients for that recipe A different recipe can keep the machine busy while this one is skipped
Finished goods stop moving Destination space and Resource Filter Free capacity or correct the destination rule
An old water line stopped after updating Water Reservoir Output connection Rebuild the connection at its changed Output position

The Water Reservoir case is a specific 1.0 migration issue: the developer moved the Output to fix placement, and explicitly says existing pipes from that Output must be rebuilt.

Keep or replace old Automators?

Existing Automators remain in old saves, and those saves can still build them. New progression no longer unlocks them. For a new production area, plan around direct storage connections and Automation Pipes; for an existing farm, prove one replacement chain works before dismantling the old one.

If the machine itself lacks a recipe you expect to own, install the latest hotfix: v1.0.2563 fixes some recipes unlocking in the wrong order. For deciding which chain deserves attention next, return to the delivery and milestone planner.

More help with crafting & progression across our game guides.

Sources

  1. Lightyear Frontier 1.0 OUT NOW!FRAME BREAK · Checked Nov 7, 2026
  2. 1.0 Automation Improvements - Frontier NewsFRAME BREAK · Checked Nov 7, 2026
  3. HOTFIX NOVEMBER 6TH | v 1.0.2563FRAME BREAK · Checked Nov 7, 2026