MI Foreman

[1.3.0] - 2026-10-03

Added

• The plan summary shows how much your linked machines can actually make (at base speed, from loaded machines) and what limits it, and limiting machines get a triangle on the graph.
• Pick the auto-detect scan radius for a single scan with the -/+ buttons beside Scan Nearby, instead of always using the configured default. Server admins can cap it with the new autolinkScanMaxRadiusChunks option.
• Machines a scan newly finds give off a brief particle burst, so they are easy to spot.
• The recipe graph shows how many linked machines it has no node for (never run yet, or running a recipe outside the plan), and the monitoring list marks machines still waiting for their first craft.
• Click that count to list those machines and place a never-run one on a graph node by hand. Only nodes the machine can actually run are offered, and when just one fits it's a single click. The machine's first real craft replaces the placement.

Changed

• Recipe graph wires now route around machine and resource cards instead of running straight through them, and wires sharing a corridor fan out side by side rather than overlapping into one line. A wire with nowhere sensible to go keeps its old straight connector.
• Where two graph wires cross, the one on top jumps over the other with a small bump.
• Moving a card, undo and redo only re-route the wires that actually changed, removing the brief hitch on very large graphs when a drag ends.
• Wires sharing a side of a card now attach at separate points, ordered by where they're headed, so a machine feeding several others shows separate wires instead of one thick line.
• Graph wires have a light outline, so where two cross the upper one visibly breaks the lower instead of the two merging.
• Machine nodes on the graph show how many of their linked machines are running (e.g. 3/4).

Fixed

• Plans now solve recycling loops and byproducts exactly. A byproduct one machine gives off is used by another branch that needs it before anything is imported, and two products from one recipe share its machines instead of each building their own.
• Plans no longer build loops that make something from nothing, like ingots packed from nuggets unpacked from ingots, or cables "made" by unpacking an energy hatch built from those cables (MI lists that recipe first). The plan switches the loop to a recipe that makes just that item from outside inputs, or imports the item when there isn't one. The item's card says which, and an Auto button next to Cycle Recipe drops your own pick so the plan can choose again. A loop you pick by hand is kept, with a warning. Existing goals switch over the next time their plan is recalculated; linked machines that ran the old loop recipes then show as off the graph. If cycling recipes earlier left a goal with a looping recipe picked, press Auto to let the plan fix it. /miforeman goal plan lists these picks as auto: <recipe>.
• Changing an existing goal's target could open its recipe graph off-screen, because the previous graph's camera and card positions were kept. A new target now opens centred.
• Plans asked for 60 times too many machines, and too much power and too many byproducts with them: the per-minute goal rate was being treated as per second. Iron plates at 60 a minute now need 5 compressors, not 300.
• A graph node with several machines on its recipe showed whichever machine happened to be linked last, so a starved machine could hide behind a working one. It now shows the worst.
• Idle machines no longer drop off the recipe graph after the clipboard is put away for a few seconds, or after a server restart. Each machine's last recipe is now saved with the world.

Known limitations

• The capacity readout assumes machines run at base speed, so overclocked or upgraded machines can make more than it says. Machines in unloaded chunks count as zero.
• When a plan swaps out a looping recipe on its own, it only uses recipes that make just that one item. Routes through recipes with byproducts (centrifuges, electrolyzers) are left for you to pick by hand.
• Batch multiblocks from addons, like MI Tweaks' Bulk Compactor, are linked and tracked, but a scan only offers them when the recipe they're running is the one the plan uses. If it isn't, cycle that item's recipe to match.