Four refusals that look unrelated — a pod that won't open, a download that won't arrive, a baby you can't claim, a pair that won't mate — can share one blocker: a full tame limit. The symptom alone does not prove that the limit is the cause.
What you see
- "Too many dinos" when you try to release a Cryopod.
- An uploaded creature stays in ARK Data instead of downloading.
- ASA: "Cannot Claim: Tame Cap reached" or "Cannot Imprint: Tame Cap reached" on a baby (messages added in 65.3).
- A breeding pair refuses to mate.
Why it happens
When the tame-cap message or the current counts confirm the limit, the tribe or the whole map is full. ARK has two limits (ARK Wiki, Server configuration):
- MaxPersonalTamedDinos — a limit per tribe, off unless the server sets one;
- MaxTamedDinos — a limit for the whole server, 5,000 by default.
A reached cap can block these actions:
- "If there are too many tamed creatures in the server, it will not download into the server" — the creature waits in ARK Data until a slot opens (ARK Wiki, CrossARK Transfers).
- "Too many dinos" is the Cryopod's message for the same limit (ARK Wiki, Cryopod).
- "If there are too many tamed creatures in the server or in the tribe, the pair will refuse to mate until there is a free spot" (ARK Wiki, Breeding).
- "Creatures stored in a cryopod do not count towards the tribe creature limit" (ARK Wiki, Cryopod). A pod even lets you transfer a creature over the limit, but the limit applies again when you release it (ARK Wiki, CrossARK Transfers).
Server hosts often lower MaxTamedDinos, because tamed creatures are the main cause of server lag (LOW.MS). This cluster's own limits are not published on the site — ask an admin.
What you can do
- Free slots by putting creatures you are not using into Cryopods: pods do not count toward the tribe limit.
- Then try downloading, releasing, claiming or breeding again. Freeing a slot removes the tame-cap blocker only; other transfer, Cryopod, claiming or mating conditions can still prevent the action. If it still fails, record the current message and check those conditions.
- Claim newborns at once: unclaimed babies "can quickly die from hunger" (ARK Wiki, Breeding). If a baby is waiting, free a slot first, then claim it.
- Travel with creatures in Cryopods, and release them only where the destination has room.
- Ask an admin for this cluster's per-tribe and server limits.
When to ask an admin
When you need the limits, or the message keeps coming although you are clearly under them. An admin can tell you this cluster's MaxPersonalTamedDinos and MaxTamedDinos values; hosts that lower the cap should publish it (LOW.MS).
Tell an admin the map, the time (the clock in your profile menu shows the server's time), your character's name, what you carried or had uploaded, and the exact message on the screen. For a transfer: both maps and both times. Report the same day — the backups reach back only about two days. Contact admin is in your profile menu; the Guides page has a question box.
Avoid it next time
- Stay under the tribe limit and keep creatures you are not using in Cryopods (ARK Wiki).
- Keep those pods in a powered Cryofridge: a pod discharges elsewhere, and a creature in a dead pod is lost — see the guide 'Died in a Cryopod' (ARK Wiki, Cryopod).
