Systems Monday — Factory Triage

The trigger

One of today’s clearest demand signals is the player asking for automation games that stay deep but never become sprawling and unwieldy like late-game Factorio or Satisfactory. There’s also a useful market-side constraint: with Steam’s old universal Daily Deals gone, a small game needs a sharper, instantly legible hook than “another factory builder.” A contract-based repair game is easier to explain, easier to screenshot, and easier to scope than an open-ended automation sandbox.

The idea

You run a small industrial maintenance firm that gets called into failing factories. Each mission is a broken, fixed-size production floor with specific faults: impossible ratios, jammed belts, bad splitter logic, unstable power draw, overflowing buffers, contaminated outputs, or maintenance neglect. Instead of starting from empty land and scaling forever, the player diagnoses what is wrong, makes targeted changes under a budget, and gets the line back online before the client loses the contract. The campaign is a chain of repair jobs across different industries, with new tools unlocked between missions and tighter constraints as you go.

The core loop

• Inspect the floor and read live throughput, power, waste, and downtime data.
• Identify the actual bottleneck instead of guessing.
• Pause, place a small number of approved parts, reroute lines, replace failing machines, or tune priorities.
• Run the factory for a short validation window and watch for jams, shortages, or overloads.
• Hit target output and quality goals under budget.
• Take payout, unlock one new service tool, and move to the next contract.

Why now

The player want is explicit: automation fans are asking for campaign structure and optimization depth without megafactory sprawl. There is also evidence that bounded, systems-heavy management games travel well right now; Against the Storm reaching tabletop is a useful sign that compact, replayable systems are resonating beyond the usual builder audience. This idea also meets the current storefront reality: “repair broken factories” is a cleaner store pitch than “small-scale automation game,” which matters more when discoverability is tighter.

Scope

The 3-6 month version is 20-30 handcrafted contracts built from a small set of reusable machines, conveyors, splitters, pipes, batteries, and sensors on a tile grid. Keep the camera 2D or simple orthographic 3D. Ship with 5-7 failure types, three biomes/industry skins, one progression track for new tools, and mission medals for budget/time/waste. First playable milestone: one factory room, three resources, basic belt logic, one dashboard, and three defect scenarios that can each be solved in under 15 minutes.

What kills it

Scope creep into freeform base-building kills this project. The moment you let players expand endlessly, you invite direct comparison with Factorio and Satisfactory, and they already own that fantasy. The game only works if diagnosis is the star: players must be able to see why a system is failing, test a fix quickly, and finish satisfied in a short session. If the telemetry is unclear, it becomes annoying maintenance busywork instead of smart triage.

If this fits your strengths, prototype one broken room with visible throughput graphs and three failure states before you design the campaign.