-
Notifications
You must be signed in to change notification settings - Fork 897
On the topic of power (and O2/H2) distribution #580
Comments
I like that ... would simplify my base extremly |
Simplest implementation would be to have source cost and sink priority be the same thing for storage devices, on the condition that power draw only occurs when priority > cost. Then there would only be one value to configure on all blocks for any given resource. There is a single edge case I can think of where you would want to be able to configure source cost and sink priority separately, which is if you wanted to trickle charge your storage, but that can be worked around by installing a storage buffer at a lower priority in the system, then using it to charge any higher priority buffers once it has sufficient energy stored. |
My Idea was, that I have my main Reactor that powers my whole base, but when it runs out of power, a secondary reactor engages and only powers the MedBay (example) |
I would like to see a change to a system where everything is manually connected. Maybe like a metagrid that is normally invisible but in wire edit mode you can place and remove wire connections that are inside armor blocks. Maybe to even make it more interesting basic electronic circuit symbols could be added so you can have power only travel in one direction (diode) or have power build up at any one point and then discharge (capacitor) etc... |
Current Algorithm
The current power distribution algorithm works as follows (more or less; this is somewhat simplified):
This algorithm prevents a number of desirable behaviors (though they may be accomplished in theory via programmable blocks or mods):
Proposed Algorithm (breaking change)
Rather than having power sources have a priority (where higher are used first), they should instead have a cost representing how important a sink has to be to draw power from them. Sample reference costs:
We then assign a value to any given sink, indicating whether or not it is worth powering from any given source, as well as its priority relative to other sinks. This is very similar to the existing priority for sinks, but on the same scale as the source costs. Sample reference costs:
Algorithm
Configurability
Although we should endeavor to provide sensible default costs and priorities for sources and sinks, making the values configurable on a per-block basis (whether via programmable block scripts or the UI) would give players an extraordinary amount of control about how their power gets allocated for minimal development overhead. If you want your rover to charge from your base batteries, give its batteries a higher charge priority than the base's battery power cost. (Note that any individual battery must always have its cost exceed its charge priority). If you are operating a ship that only has reactors, your power priorities will most likely be different from a station that runs on solar and batteries and only has reactors for emergencies.
Configuration would also allow for scenarios such as a vessel that runs primarily on reactors, but uses batteries for burst power.
Other effects
Under this algorithm, "stockpiling storage" (e.g. a battery with the charging flag set) is simply storage for which the source cost has been set to
Infinity
. A battery with the discharging flag set has a sink priority of-Infinity
.Edit: Added "other effects" section
The text was updated successfully, but these errors were encountered: