plumbing 
Vars | |
| demand_color | What color is our demand connect? |
|---|---|
| demand_connects | direction in wich we act as a demander |
| distinct_reagent_cap | How many distinct reagents can we accept at once Ex - if this was set to "3", our component would only request the first 3 reagents found, even if more are available |
| ducting_layer | The layer on which we connect. Don't add multiple. If you want multiple layer connects for some reason you can just add multiple components with different layers |
| ducts | Index with "1" = /datum/ductnet/theductpointingnorth etc. "1" being the num2text from NORTH define |
| reagents | shortcut to our parents' reagent holder. The holder that sends reagents into the pipeline |
| supply_color | What color is our supply connect? |
| supply_connects | directions in wich we act as a supplier |
| tile_covered | Whether our tile is covered and we should hide our ducts |
Procs | |
| Initialize | turn_connects is for wheter or not we spin with the object to change our pipes |
| active | Returns if the machine is active or not |
| can_give | returns TRUE when they can give the specified amount and reagent. called by process request |
| enable | settle wherever we are, and start behaving like a piece of plumbing |
| get_all_network_reagents | Returns a list of all distinct reagent types available in the passed duct network. The passed net can be null, it is handled. |
| get_original_direction | Give the direction of a pipe, and it'll return wich direction it originally was when its object pointed SOUTH |
| process_request | check who can give us what we want, and how many each of them will give us |
| recipient_reagents_holder | Returns the reagent holder meant to receive the reagents. Can be different from the one that sends reagents to the network |
| send_request | called from in process(). only calls process_request(), but can be overwritten for children with special behaviour |
| transfer_to | this is where the reagent is actually transferred and is thus the finish point of our process() |
Var Details
demand_color
What color is our demand connect?
demand_connects
direction in wich we act as a demander
distinct_reagent_cap
How many distinct reagents can we accept at once Ex - if this was set to "3", our component would only request the first 3 reagents found, even if more are available
ducting_layer
The layer on which we connect. Don't add multiple. If you want multiple layer connects for some reason you can just add multiple components with different layers
ducts
Index with "1" = /datum/ductnet/theductpointingnorth etc. "1" being the num2text from NORTH define
reagents
shortcut to our parents' reagent holder. The holder that sends reagents into the pipeline
supply_color
What color is our supply connect?
supply_connects
directions in wich we act as a supplier
tile_covered
Whether our tile is covered and we should hide our ducts
Proc Details
Initialize
turn_connects is for wheter or not we spin with the object to change our pipes
active
Returns if the machine is active or not
can_give
returns TRUE when they can give the specified amount and reagent. called by process request
enable
settle wherever we are, and start behaving like a piece of plumbing
get_all_network_reagents
Returns a list of all distinct reagent types available in the passed duct network. The passed net can be null, it is handled.
get_original_direction
Give the direction of a pipe, and it'll return wich direction it originally was when its object pointed SOUTH
process_request
check who can give us what we want, and how many each of them will give us
recipient_reagents_holder
Returns the reagent holder meant to receive the reagents. Can be different from the one that sends reagents to the network
send_request
called from in process(). only calls process_request(), but can be overwritten for children with special behaviour
transfer_to
this is where the reagent is actually transferred and is thus the finish point of our process()