Skip to content

Add to inputs context menu - #4

Open
samox73 wants to merge 2 commits into
SatisfactoryTools:masterfrom
samox73:add-to-inputs-context-menu
Open

samox73 wants to merge 2 commits into
SatisfactoryTools:masterfrom
samox73:add-to-inputs-context-menu

Conversation

@samox73

@samox73 samox73 commented Oct 17, 2026

Copy link
Copy Markdown

fixes #2

one remark: this PR includes a fix for inputs with weight 0. Previously inputs with weight 0 were drawn into the solver because byproducts are free. This resulted in inputs being displayed like this:

image

Steps to reproduce (on master)

  1. Create a new plan and request Supercomputer at 10/min. Keep the default settings and Automatic mode.
  2. In the Input tab, add Computer: amount 50/min, weight 0. The plan now uses the Computer input instead of building Computers, but also creates a byproduct of 10 Computer/min.

If you'd rather split the fix from the feature, I can do that. Just felt like they belong together.

Inputs with weight 0, and all inputs when input weights are turned off, were left out of the objective. Byproducts cost nothing, so once an input exceeded the demand the solver could draw it and dump it into a byproduct at no cost. Every input now carries a 1e-6 tie-break cost on top of its weight. That's far below any real weight (water: 0.01) and far above the 1e-9 dual tolerance, so it only breaks ties. 'Add to inputs' goes back to weight 0 now that free inputs behave.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature Request] Turn node into a plan input from its context menu

1 participant