connect_mob_behalf

This component behaves similar to connect_loc_behalf, but working off clients and mobs instead of loc To be clear, we hook into a signal on a tracked client's mob We retain the ability to react to that signal on a seperate listener, which makes this quite powerful

Vars
connections	An assoc list of signal -> procpath to register to the mob our client "owns"
tracked	The master client we're working with
tracked_mob	The mob we're currently tracking
Procs
handle_tracked_qdel	Delete ourselves when our tracked client is deleted
on_logout	update_signals on tracked mob logout
unregister_signals	Unregister signals on tracked mob
update_signals	Re-register signals on tracked mob

Var Details

var
connections
– /list

An assoc list of signal -> procpath to register to the mob our client "owns"

var
tracked
– /client

The master client we're working with

var
tracked_mob
– /mob

The mob we're currently tracking

Proc Details

proc
handle_tracked_qdel
()

Delete ourselves when our tracked client is deleted

proc
on_logout
(/mob/source)

update_signals on tracked mob logout

proc
unregister_signals
()

Unregister signals on tracked mob

proc
update_signals
()

Re-register signals on tracked mob

connect_mob_behalf /datum/component/connect_mob_behalf

Vars

Procs

Var Details

var connections – /list

var tracked – /client

var tracked_mob – /mob

Proc Details

proc handle_tracked_qdel()

proc on_logout(/mob/source)

proc unregister_signals()

proc update_signals()