mff/pipeworks
1
0
Fork 0
forked from mtcontrib/pipeworks
Code Issues Pull Requests Releases Wiki Activity

todo: update new flow logic items for cleanup handler work

Browse Source
This commit is contained in:
thetaepsilon-gamedev 2017-10-08 11:41:42 +01:00
parent 6a25e56336
commit 7e09da50c2
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
todo/new_flow_logic.txt
View File

@ -3,10 +3,11 @@ Currently, only "simple" flowable nodes exist, and they will always equalise pre
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. 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. This would enable devices such as the airtight panels, sensor tubes and valves to have correct flow behaviour.
-- Implement clean-up functionality for output nodes in non-finite mode -- (may not be possible) stop removing water nodes that were not placed by outputs when off
register.output() needs to be equipped with an extra "cleanerfn" argument, which is saved into the node's output table entry. 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.
When the pressure level falls below the lower level in non-finite mode, this function would be called by run_output() to e.g. remove a created water source. This is annoying though not game-breaking in non-finite mode, where water sources can at least be easily replenished.
Additionally, the outputfn needs to be equipped with a flag to convey the finite mode, so that in non-finite mode the outputfn will drain pressure continuously until the pressure falls below the threshold. 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 -- 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. 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.