Fixes some instances of PostTransfer not using new_parent argument (#88398)

## About The Pull Request

Since #87866 PostTransfer now has it's parent set to nil, and instead
has a `datum/new_parent` argument supplied to it.
Why does the ***post*** transfer proc not have it's parent set yet? Not
sure, but some procs (and the documentation) haven't been adjusted yet
and this PR fixes that

also:
fixes #88156 
fixes #88325 

## Why It's Good For The Game

Fix man good...

## Changelog

🆑
fix: /datum/component/PostTransfer() procs that didn't have their
new_parent arguments have now been fixed
fix: This means that turning into a Domain gondola shouldn't RR people
anymore
/🆑
This commit is contained in:
tonty
2024-12-08 15:49:49 +01:00
committed by GitHub
parent f317c5796b
commit b3085c973a
5 changed files with 12 additions and 12 deletions
@@ -76,15 +76,15 @@
avatar.set_temp_blindness(1 SECONDS) // I'm in
/datum/component/avatar_connection/PostTransfer()
/datum/component/avatar_connection/PostTransfer(datum/new_parent)
var/obj/machinery/netpod/pod = netpod_ref?.resolve()
if(isnull(pod))
return COMPONENT_INCOMPATIBLE
if(!isliving(parent))
if(!isliving(new_parent))
return COMPONENT_INCOMPATIBLE
pod.avatar_ref = WEAKREF(parent)
pod.avatar_ref = WEAKREF(new_parent)
/datum/component/avatar_connection/RegisterWithParent()