duct

Vars
active	wheter to even bother with plumbing code or not
capacity	amount we can transfer per process. note that the ductnet can carry as much as the lowest capacity duct
color_to_color_support	TRUE to let colors connect when forced with a wrench, false to just not do that at all
connects	bitfield with the directions we're connected in
drop_on_wrench	wheter we just unanchored or drop whatever is in the variable. either is safe
duct	our ductnet, wich tracks what we're connected to
duct_color	the color of our duct
duct_layer	1,2,4,8,16
dumb	set to TRUE to disable smart duct behaviour
ignore_colors	TRUE to ignore colors, so yeah we also connect with other colors without issue
lock_connects	wheter we allow our connects to be changed after initialization or not
lock_layers	whether we allow our layers to be altered
neighbours	track ducts we're connected to. Mainly for ducts we connect to that we normally wouldn't, like different layers and colors, for when we regenerate the ducts
Procs
add_connects	add a connect direction
add_neighbour	add a duct as neighbour. this means we're connected and will connect again if we ever regenerate
attempt_connect	start looking around us for stuff to connect to
can_anchor	collection of all the sanity checks to prevent us from stacking ducts that shouldnt be stacked
connect_duct	connect to a duct
connect_network	see if whatever we found can be connected to
connect_plumber	connect to a plumbing object
create_duct	create a new duct datum
disconnect_duct	we disconnect ourself from our neighbours. we also destroy our ductnet and tell our neighbours to make a new one
generate_connects	Special proc to draw a new connect frame based on neighbours. not the norm so we can support multiple duct kinds
get_adjacent_ducts	get a list of the ducts we can connect to if we are dumb
handle_layer	update the layer we are on
lose_neighbours	remove all our neighbours, and remove us from our neighbours aswell
reconnect	''''''''''''''''optimized''''''''''''''''' proc for quickly reconnecting after a duct net was destroyed
remove_connects	remove a connect direction
reset_connects	remove our connects

Var Details

var
active
–

wheter to even bother with plumbing code or not

var
capacity
–

amount we can transfer per process. note that the ductnet can carry as much as the lowest capacity duct

var
color_to_color_support
–

TRUE to let colors connect when forced with a wrench, false to just not do that at all

var
connects
–

bitfield with the directions we're connected in

var
drop_on_wrench
–

wheter we just unanchored or drop whatever is in the variable. either is safe

var
duct
– /datum/ductnet

our ductnet, wich tracks what we're connected to

var
duct_color
–

the color of our duct

var
duct_layer
–

1,2,4,8,16

var
dumb
–

set to TRUE to disable smart duct behaviour

var
ignore_colors
–

TRUE to ignore colors, so yeah we also connect with other colors without issue

var
lock_connects
–

wheter we allow our connects to be changed after initialization or not

var
lock_layers
–

whether we allow our layers to be altered

var
neighbours
– /list

track ducts we're connected to. Mainly for ducts we connect to that we normally wouldn't, like different layers and colors, for when we regenerate the ducts

Proc Details

proc
add_connects
(new_connects)

add a connect direction

proc
add_neighbour
(/obj/machinery/duct/D, direction)

add a duct as neighbour. this means we're connected and will connect again if we ever regenerate

proc
attempt_connect
()

start looking around us for stuff to connect to

proc
can_anchor
(/turf/T)

collection of all the sanity checks to prevent us from stacking ducts that shouldnt be stacked

proc
connect_duct
(/obj/machinery/duct/D, direction, ignore_color)

connect to a duct

proc
connect_network
(/atom/movable/AM, direction, ignore_color)

see if whatever we found can be connected to

proc
connect_plumber
(/datum/component/plumbing/P, direction)

connect to a plumbing object

proc
create_duct
()

create a new duct datum

proc
disconnect_duct
(skipanchor)

we disconnect ourself from our neighbours. we also destroy our ductnet and tell our neighbours to make a new one

proc
generate_connects
()

Special proc to draw a new connect frame based on neighbours. not the norm so we can support multiple duct kinds

proc
get_adjacent_ducts
()

get a list of the ducts we can connect to if we are dumb

proc
handle_layer
()

update the layer we are on

proc
lose_neighbours
()

remove all our neighbours, and remove us from our neighbours aswell

proc
reconnect
()

''''''''''''''''optimized''''''''''''''''' proc for quickly reconnecting after a duct net was destroyed

proc
remove_connects
(dead_connects)

remove a connect direction

proc
reset_connects
()

remove our connects

duct /obj/machinery/duct

Vars

Procs

Var Details

var active –

var capacity –

var color_to_color_support –

var connects –

var drop_on_wrench –

var duct – /datum/ductnet

var duct_color –

var duct_layer –

var dumb –

var ignore_colors –

var lock_connects –

var lock_layers –

var neighbours – /list

Proc Details

proc add_connects(new_connects)

proc add_neighbour(/obj/machinery/duct/D, direction)

proc attempt_connect()

proc can_anchor(/turf/T)

proc connect_duct(/obj/machinery/duct/D, direction, ignore_color)

proc connect_network(/atom/movable/AM, direction, ignore_color)

proc connect_plumber(/datum/component/plumbing/P, direction)

proc create_duct()

proc disconnect_duct(skipanchor)

proc generate_connects()

proc get_adjacent_ducts()

proc handle_layer()

proc lose_neighbours()

proc reconnect()

proc remove_connects(dead_connects)

proc reset_connects()