Skip to content

Fixes clone pod runtime

Rob Nelson requested to merge pull/13176/clonepod-runtime into Bleeding-Edge

Created by: Kammerjunk

Fixes this when the clone pod has a connected of null:

[05:19:21] Runtime in cloning.dm,364: Cannot read null.pod1
  proc name: Destroy (/obj/machinery/cloning/clonepod/Destroy)
  usr: Test Dummy (kammerjunk) (/mob/dead/observer)
  usr.loc: The floor (133, 64, 2) (/turf/simulated/floor)
  src: the cloning pod (/obj/machinery/cloning/clonepod/full)
  src.loc: the floor (132,66,2) (/turf/simulated/floor)
  call stack:
  the cloning pod (/obj/machinery/cloning/clonepod/full): Destroy()
  qdel(the cloning pod (/obj/machinery/cloning/clonepod/full), 0, 0)
  Kammerjunk (/client): Delete(the cloning pod (/obj/machinery/cloning/clonepod/full))

Instead of deleting the clone pod and making a machine frame instead, it'll create the machine frame and leave the clone pod (which will be indestructable to everything, even admin deletion) Not sure exactly why it happens to begin with. I suspect it'll happen whenever mechanics makes their own clone pod, but it seems to not be the only time it'll happen.

Merge request reports