Cryopod

The Cryopod is an item to store your tames in, by freezing them into an "ice cube" state. Creatures stored in a cryopod do not count towards the tribe creature limit.

Usage
To capture a creature in a Cryopod, equip an empty Cryopod and while aiming close to them hold for a few seconds. Once a creature is Cryopodded it will act like an item, halting food consumption, and the Cryopod can be carried in a survivor or creature's inventory which makes mass transport of creatures easier.

The Cryopod will begin to discharge as soon as it is created, either through crafting or after being obtained from an Orbital Supply Drop, with a 30 day or one month decay period. The or a  will recharge the Cryopod as long as it is powered. If the Cryopod is not recharged before the charge reaches zero, it will disable and will be labelled as dead. When the Cryopod goes dead any creature inside the Cryopod will die and disappear forever, even after the Cryopod is recharged. The creature's death will be noted in the Tribe Log, and the dead Cryopod is unusable until it recharges in a. The Cryopod recharge timer is unaffected by, but the discharge rate can be slowed to half rate by placing the Cryopod into a.

1: Time to empty from a fully charged cryopod. Partially charged cryopods will have a proportionately shorter time. 2: The Cryofridge recharges the cryopod at the same rate it would get depleted in a normal inventory, as long as the Cryofridge remains powered

With the use of Cryopod, players can:


 * Transfer aquatic tames, via air (or fast land runner).
 * Transfer large land tames, who cannot be picked up by, via air.
 * Transfer more than one tame at once via one journey.
 * Effective on the way to some place that is extremely difficult to navigate on foot, such as the summit of Volcano.
 * Help tames when they get stuck.
 * Bring creatures that are larger than the entrance into caverns.
 * Surprisingly helpful in defeating Snow Cave, etc..
 * Store and protect weak tames.
 * Transfer tames with saddle, saving slots when using Obelisk Terminals (in case you have a lot of things to transfer to other servers).
 * Store strong tames and hide their power to competitors.

Error Notice
When certain conditions are not met, attempting to release the dinosaur out into the open will result in the following red message, with the dino still inside the cryopod:
 * Not Enough Space to deploy = the area where the dino is being deployed has insufficient space. This also happens if attempted to deploy at a closed Tek Cave or at a Boss Arena.
 * Must be deployed underwater = the dino inside the cryopod must be deployed in the water while the survivor is in water. Mostly applies if the dino is strictly an aquatic creature.
 * Too many dinos = either the tribe, or the server, has too many tamed creatures currently present.
 * >> Failed to spawn << = several errors, occasionally related to mods. This occurs if there is no proper asset (i.e: files in the Steam folder) for creatures to spawn, or the creature inside the cryopod has hit past the level limit that is permitted as a tamed creature.
 * Dino Class Not Allowed = The Dino you are trying to throw out is not allowed on the map, such as trying to bring a flyer to Aberration. This used to be overcome by bringing fertilized eggs of said Dino and hatching them on said server, but the parents will not be allowed into the world.

Cryo Sickness

 * Note that this is disabled by default in server setting, and in PvE Official Servers.

When a creature is un-Cryopodded, the survivor will receive a Status Effect known as Cryo Cooldown. Cryo Cooldown lasts for 5 minutes, and is tracked with a countdown timer in the bottom right of the screen. Any Creatures un-Cryopodded during Cryo Cooldown will get Cryo Sickness. Cryo Sickness lasts for 5 minutes, causes said creature to receive increased damage if attacked (10x normal damage), and renders the creature unconscious with a full bar of torpor. The words "Cryo Sickness" are displayed above any afflicted creature in red text for the full 5 minute duration. Creatures cannot be Cryopodded while Cryo Sickness is active, and even if the creature has a short torpor timer (like ) and wakes up from torpor before the Cryo Sickness wears off, it will not be rideable and will not respond to whistle commands until the Cryo Sickness wears off. Juvenile and adolescent Creatures with Cryo Sickness will not eat from troughs. The act of un-Cryopodding also resets the Cryo Cooldown timer for the survivor who unfroze it (only to the maximum value of 5 minutes, the timer does not stack past 5 minutes), so if releasing a large amount of creatures expected to endure Cryo Sickness, it is good practice to do so only in a well protected environment.

Information
There are a few things to note when Cryopodding a creature:


 * If the creature cannot be released from the cryopod (due to one of the reasons mentioned in the 'Error Notice' section above), a corresponding message in red text will be displayed, and both the Cryopod and creature within remain unaffected.
 * Anything in the creature's inventory will drop once they are Cryopodded (this includes any other slot, like weapon slot for ). The only main exception are both the (if it is wearing one), and Modules for  (Durability will degrade when Cryopodding).
 * The individual that releases a creature from a Cryopod takes ownership of said creature.
 * Since they are an item, if a survivor or creature dies with a Cryopod in inventory, the Cryopodded creature is at risk of theft (or loss).
 * The ability to drop (default, , ) a filled Cryopod for someone else to pick up allows for easier trading of creatures (compared to having to unclaim and then claim the creature). It is not sure if this is an unintended way to get around the Tribe Governance setting of Only Admins Can Unclaim.
 * Cryopodding a baby (baby, juvenile or adolescent) creature inside a Cryopod will pause the imprint timer and food consumption, and if asking for care, will change what it wants whenever it is un-Cryopodded. Babies Cryopodded prior to the related patch will still have their imprint timer reset to 8 hours next time they are released.
 * Cryopodding a Female will not reset the breeding timer unless the Cryopod containing it was recently transferred to another server. Timer for mating interval continues to tick down even when the Female is Cryopodded. Females Cryopodded prior to the patch related will still have their breeding timer reset the next time they are released.
 * If a mammal is gestating, Cryopodding will reset the pregnancy and upon un-Cryopodding the Female will be on a regular mating cooldown interval (based on server settings).
 * Passive XP gain is solely determined by game time since time of Cryopodding, multiplied by their idle XP rates, multiplied by a final 1.05 return. Creatures at maximum level or  will not gain any passive XP.
 * Any creature inside a Cryopod will gain 5% more passive experience, compared to the same creature not Cryopodded.
 * Transferring the cryopod to another server resets this timer, causing it to lose all pending experience points earned since podding it. You must unpod the creature for it to obtain the experience points before transferring it to another server.
 * Cryopodded creatures will have their gender displayed along with all current stat values when hovered over with the infobox activated. This does not apply to creatures that were Cryopodded prior to the patch that includes it.
 * Recently uncryopodded creature will have a temporary debuff that severely reduces the amount of damage it can deal by 90%, or based on the server setting set. This only happens if the server has set that setting.
 * In Aberration, creatures that either are not part of Extinction or Aberration (or not having an aberrant counterpart), or are in the list of banned creatures, cannot be released from their cryopods unless the server setting for Foreign Dino Downloads is enabled.

Restrictions
The following creatures (including forcetamed) cannot be cryofrozen into a cryopod:

Note that the 'Giant Bee' refers to the bees spawned by, not the queen herself.

Only the Ice and Chalk Golem variant of Rock Elemental from Valguero are affected.

Placed vehicles with exception of the Tek ATV cannot be cryofrozen either, though freezing of the Tek ATV is most likely not intended, as the Cryopod will show a picture of a Raptor when the Tek ATV is cryofrozen.

Bugs

 * 292.100 - Releasing a creature will automatically set the released creature to follow the survivor who released it. This persists on unconscious creature which cannot be whistled on any command to stop as they will still "follow" the survivor even under an unconscious state.
 * This can be remedied by fast traveling to another bed far from where the creature is.
 * If you Cryofreeze a creature, all the folders created inside it will disappear similar to what happens when uploading a creature.
 * When transferring filled cryopods on singleplayer or unofficial servers, there is a chance that the creature's level will be reset to 1, the saddle will be deleted and any imprint quality will be lost along with any mutations.
 * This is a result of transferring between non-clustered servers, and is directly caused by the obelisk removing custom item byte data within the item.
 * When transferring a creature in an obelisk via cryopod, there is a chance the retrieved cryopod will display a picture of a Raptor and be un-deployable despite still having the correct name and stats for your creature.
 * This is a result of the class variable being lost, and is the direct result of transferring a creature class to a server that does not have the dino file/data. Most common with modded dinos, but can still occur with special creatures from free DLC content. In layman's terms, it's the equivalent of trying to spawn a modded dino without having the mod installed, except it will never resolve itself.
 * If your character is slot capped (black Weight.png icon), freezing a creature will not update the state of the cryopod you used and it will remain empty until you re-log or transfer it out of your inventory. This bug only seems to occur on dedicated servers, not single-player.