Increase Dyson module consumption, especially without computation #14509
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the Dyson formula fixed, revisiting the consumption is in order, especially as the old balancing was done with an incorrect script (It had module count and consumption swapped).
"Current" values with existing coefficients and a fixed consumption function, although the consumption has always been at a static 1 module per hour due to a bug in the formula.
Increasing computation is fairly inconsequential, and the module consumption still makes the Dyson spammable even without computation.
Module consumption with new values:
Adding computation becomes almost mandatory, with each quantum computer (at 25k computation/s) reducing the module consumption by roughly 30% (additive). The computation is capped at 100 000/s to still keep a minimum running cost of 64 modules per hour (One recipe/hour)
This should reduce the viability of spamming dozens of Dysons, add some running cost to properly-supplied Dysons, while still keeping them a competitive option (Naqfuel I am looking at you).