A pod remembers its creature by class. If that class goes missing, the pod shows a Raptor — and the wrong move can delete the creature for good.

What you see
- The pod's picture turned into a Raptor while its name and stats still look right, and deploying does nothing.
- Releasing the pod deleted it, and no creature appeared.
- "Failed to spawn" on a modded creature, or ARK Data shows used slots with nothing in them.
Why it happens
"If one were to cryo a modded creature, and remove the originating creature's mod, then the class gets nullified", and releasing a creature whose class has been nullified removes the item, with no creature created (ARK Wiki). After an Obelisk transfer, a pod can show a Raptor picture and be un-deployable when the destination lacks the creature's files (ARK Wiki).
Players hit this with creatures from a map or mod the destination doesn't have, with variants converted between maps (the Ice Wyvern), between maps with different mods, and after game updates (Steam, 2019–2020).
Our ASE maps run no mods. On ASA, check that the destination currently loads the creature's required mod, particularly after a mod is removed, replaced or updated.
Not every Raptor picture means trouble: creatures without their own icon get a Raptor-like placeholder, and a podded Tek ATV shows a Raptor too (ARK Wiki).



