mirror of
https://github.com/mt-mods/pipeworks.git
synced 2024-11-08 16:33:58 +01:00
18 lines
2.0 KiB
Plaintext
18 lines
2.0 KiB
Plaintext
-- Directionality code
|
|
Currently, only "simple" flowable nodes exist, and they will always equalise pressure with all six neighbours.
|
|
A more sophisticated behaviour for this would be flowable node registration with some kind of custom callback, such that water can only flow into or out of these nodes in certain directions.
|
|
This would enable devices such as the airtight panels, sensor tubes and valves to have correct flow behaviour.
|
|
|
|
-- (may not be possible) stop removing water nodes that were not placed by outputs when off
|
|
In non-finite mode, spigots and fountainheads will vanish water sources in their output positions, even if those output nodes did not place them there.
|
|
This is annoying though not game-breaking in non-finite mode, where water sources can at least be easily replenished.
|
|
Fixing this would require some kind of metadata marker on water nodes placed by spigots and fountains, such that only water sources placed while the device is "on" are removed when it is "off".
|
|
It is debateable whether existing water sources should be marked for removal when the device turns on again.
|
|
|
|
-- Automated switching between node variants based on pressure thresholds
|
|
Within flowlogic.run(), an additional hook which would be useful is a "node changer" callback, to switch between variations of a pipe depending on pressure level.
|
|
For regular pipes, this is mostly aesthetic, as the empty/loaded variants of the pipes have different texures.
|
|
However, the flow sensor is currently a broken device under the new flow logic, as there is nothing to switch this device between the "on" and "off" state - in order to produce a mesecons output, separate nodes are required due to mesecon's API being limited to only on/off for a given node, with no facility for a callback function which could e.g. inspect pressure metadata.
|
|
To make this work, a new registry table would be needed to check if a flowable node has this property.
|
|
In terms of ordering, this callback should be run after outputs have been processed.
|