Bug Resolved

Can't force update of insufficient parts

sfogarty · Jul 19, 2026

When I have a red-dotted input, I often can't clear it no matter what I do to the previous elements in the chain. See below for example: no matter what I do, I can't get the steel ingots to the steel beam at more than 40. If I delete the connection, the output of the ingots pops up... but as soon as I connect it back to the beam constructor in it drops back down. https://pioneertoolbox.com/planner/s/hwtUa6q8EAJEx59Kv7IKGQ

Update from the maintainer

Fixed in v0.16.1 Your plan taught us something: it was solving correctly the whole time. The planner just refused to tell you why. I rebuilt your setup from the link. The whole line is sized by the limestone miner pinned at 60. That gives 20 concrete, which runs the Encased Industrial Beam at 0.56 of a machine, which needs 10 beams, which needs exactly 40 ingots. That is your stuck 40. Raising ore or coal could never move it, because those miners are auto-sized and just follow demand back down. What I fixed: a red dot now names the actual bottleneck, so your beam node says "Limestone (source)" instead of leaving you digging three machines upstream. And sharing one ingot node between two constructors is now deterministic, so the "sometimes works, not reliably" behaviour is gone. If you want that EIB at its full limit: limestone to 108. Please retest and tell me if any red dot still lies to you.

4 comments

Xuqari maintainer · Jul 19, 2026

Thanks for reporting. I'll take a look at this!
sfogarty · Jul 19, 2026

It seems to be related to sharing nodes. When recreating this, if I manually made a motor output (by dragging inputs into new boxes), everything was fine. If I then added an encased industrial beam, it works until I try to share the steel ingots between beams and pipes. It works correctly if I have two steel ingot nodes. If I ensure that the input nodes to the steel ingot node have enough output, then it sometimes seems to work - but not reliably.
sfogarty · Jul 31, 2026

I encountered the problem again, when trying to set the number of constructors to a specific number. However, that was because there wasn't enough output to justify those constructors: once I added the output box (yay new feature!) it all resolved itself.
sfogarty · Jul 31, 2026

https://pioneertoolbox.com/planner/s/QQNLypZmJbfeqScGGMuJjQ Here's an example of the "confusing red dot". It looks like I don't have enough iron to fuel two iron plate constructors, when really I don't have enough *output* to justify the two iron plate constructors.