connect_range

This component behaves similar to connect_loc_behalf but for all turfs in range, hooking into a signal on each of them. Just like connect_loc_behalf, It can react to that signal on behalf of a separate listener. Good for components, though it carries some overhead. Can't be an element as that may lead to bugs.

Vars
connections	An assoc list of signal -> procpath to register to the loc this object is on.
range	The component will hook into signals only on turfs not farther from tracked than this.
tracked	The atom the component is tracking. The component will delete itself if the tracked is deleted. Signals will also be updated whenever it moves (if it's a movable).
turfs	The turfs currently connected to this component
works_in_containers	Whether the component works when the movable isn't directly located on a turf.

Var Details

var
connections
– /list

An assoc list of signal -> procpath to register to the loc this object is on.

var
range
–

The component will hook into signals only on turfs not farther from tracked than this.

var
tracked
– /atom

The atom the component is tracking. The component will delete itself if the tracked is deleted. Signals will also be updated whenever it moves (if it's a movable).

var
turfs
– /list

The turfs currently connected to this component

var
works_in_containers
–

Whether the component works when the movable isn't directly located on a turf.

connect_range /datum/component/connect_range

Vars

Var Details

var connections – /list

var range –

var tracked – /atom