Add mult support for machinery where applicable #3147
Merged
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.
[balance][input wanted]
About the PR
Adding support for "mult" to various machinery to account for missed periodic processing incurred by what the people call "lag".
Why's this needed?
Provides more consistent user experience by accounting for variability of machine processing. The goal is to err on the side of the player to avoid situations where overall processing delay doesn’t cause thrashing with the powernets as the overall behavior is non-deterministic.
This will be accomplished by scaling actions performed while ignoring scaling of power usage, as we can not be certain that scaling would also occur for machinery that would provide power to the powernet for the reset. (Would love for someone to tell me I’m wrong)
Atmos scaling is limited as suddenly influxes of activity would cause unusual behavior that would be impossible to rationalize from a player perspective and an absolute nightmare to debug and investigate.