Tames are the cheapest lag a Valheim group can build and the slowest to notice. Every wolf, boar, lox, hen and asksvin is a creature with its own AI, running on the computer of whichever player is closest to it - not on the server - and breeding keeps adding more until a nearby cap stops it. A pen of six boars costs nothing. A barn of eighty wolves turns the main base into a slideshow for whoever walks in, and no server plan fixes it, because the work is happening on the players' machines. The rules that keep tames useful are short: breed for a purpose, keep pens small and away from the hall, cull the surplus with the butcher knife, and agree a per-player limit before anyone starts a wolf army.
What can be tamed, and how#
Valheim has five tameable creatures in the current game, one or two per biome as you progress. Taming works the same way for the wild ones: the creature has to be calm (not alerted to you), it has to eat food you leave on the ground, and taming progresses while it stays fed and undisturbed. Hit it, or let it see you as a threat, and progress pauses until it calms down. Uninterrupted, taming takes a few items of food and something like half an hour of real time; the exact timer differs by creature and has been adjusted in patches, so treat that as an order of magnitude.
| Creature | Where | Eats | Why groups keep them |
|---|---|---|---|
| Boar | Meadows | Berries, mushrooms, carrots, turnips, onions | Raw meat and leather scraps, early food |
| Wolf | Mountains | Raw meat and fish | Fighting companions, base guards |
| Lox | Plains | Barley, cloudberries, flax | Lox meat and pelts, rideable with a saddle |
| Hen | From eggs | Seeds | Eggs and feathers, cooking ingredients |
| Asksvin | Ashlands | Ashlands plants such as vineberries | Rideable with a saddle, late-game mount |
Two of these do not come from the wild in the usual way. Hens never spawn in the world: you start from eggs, which Haldor sells after Yagluth has been killed and which can also be found in the Plains sealed towers from Hildir's quests. An egg placed on its own (not in a stack), near a fire and under a roof stays warm and hatches into a chick that is tame from birth. Asksvin can be tamed from the wild, but they are strong enough to break most walls, so groups usually tame them in a pit, or hatch them from eggs found in the Ashlands, which works like the hen eggs - warmth, roof, one egg at a time.
Wolves are the tame most groups regret having too many of. They fight, they follow, and they breed readily on cheap food, which makes a wolf barn the obvious project for anyone with a stack of raw meat and an afternoon.
Lox and asksvin can be ridden once you craft a saddle for them. Only one player rides at a time, and the rider's client drives the creature, which is one of the few cases where a tame's simulation follows a player rather than staying with the zone.
Who simulates a tame on a server#
To understand why tames cost what they cost, you need the one rule from the Valheim dedicated server guide that explains most multiplayer behaviour: the world is divided into zones, and each zone is simulated by the first player who walks into it. The server stores the creatures, relays their state and hands ownership around. It does not run their AI unless nobody else does.
That has three consequences for tames.
- A tame does nothing while nobody is near it. It is saved in the world file as an object with its position, health, taming state and name. It does not get hungry, wander off or breed while its zone is unloaded. This is why breeding seems to stall when nobody stays home - the animals only accumulate the state they need to breed while someone is close enough to keep the zone active.
- The player nearest the pen pays for it. The AI, pathfinding and physics of every tame in the active area run on that player's machine. Forty wolves in a barn are forty sets of AI and forty physics bodies pushing against each other, every frame, on one person's CPU. A player with a modest PC becomes the bottleneck for everyone who arrives after them.
- Everyone else receives the result. The owner sends each creature's state to the server, and the server relays it to every other player in range. More creatures means more objects to synchronise, and that is the part that shows up as rubber-banding and monsters teleporting near the base.
The server itself does feel tames, but less directly: every creature is one more object stored in the world, saved to disk at every save interval and sent to each player who walks into range. A world with hundreds of tames has a bigger .db, longer save hitches and longer loading when someone arrives at the base. Valheim server performance and lag covers how to tell server-side lag from the client-side kind, and it matters here, because tame lag is mostly the client-side kind.
How breeding works, and where it stops#
Breeding is automatic. Tamed animals of the same species that are fed and calm, with a partner close by, gradually build up towards a pregnancy. When it completes, an offspring appears - a piglet, a wolf cub, a lox calf - and grows into an adult over time. Offspring are tame from birth.
The brake on this is a population check. Before an animal can breed, the game counts how many creatures of its species are within a small radius around it, and if the count is at or above that species' limit, it does not breed. The values that mods expose for this suggest vanilla checks a radius of about 10 metres for the population and about 3 metres for a partner, with limits in the region of four or five for boars, wolves and lox and higher for hens and asksvin.
| Setting | Approximate vanilla value | What it means |
|---|---|---|
| Population check radius | About 10 m | Animals further away are not counted |
| Partner range | About 3 m | A partner must be this close |
| Limit: boar, wolf, lox | Roughly 4-5 nearby | Breeding stops at this count |
| Limit: hen, asksvin | Higher, around 10 | Small creatures, bigger flocks |
| Requirement | Tamed, fed, calm | A hungry animal never breeds |
Those numbers have moved between versions and are not shown anywhere in the game, so do not build a pen to the centimetre around them. Check a current source for your version if you need exact values. The principle is what matters: the cap is local. It only stops breeding inside its radius.
That is how runaway breeding happens. A pen wider than the check radius, or several pens a short walk apart, or offspring that wander out of the pen, each give the game a fresh space in which the count is under the limit. Wolves are the usual case: a group feeds a pen generously, cubs escape through a gap in the fence or are told to follow somebody, and the barn becomes a field of wolves. Every one of them is permanent until something kills it.
Feeding is the other half. An animal must be fed to breed, so a group can stop a pen growing simply by not feeding it. Animals do not starve to death in Valheim; a hungry tame just stops breeding. That makes feeding the actual control knob, and it is more reliable than trying to manage pen sizes.
Why big pens lag, and how much is too much#
There is no published number for "too many tames", because the cost depends on the player's machine, the creature and what else is in view. Some honest reference points from how the game behaves:
- Small pens are effectively free. Five or six boars or a handful of wolves add nothing anyone will notice.
- Large creatures cost more than small ones. Lox are big physics bodies with long collision boxes. A crowded lox pen is noticeably heavier than the same number of hens.
- Crowding is worse than count. Fifty wolves spread across a meadow are cheaper than fifty wolves in a barn where every one of them collides with its neighbours every frame.
- Followers travel. A wolf told to follow walks wherever its player goes, including into other people's bases, and stays wherever the player logged off.
The symptom pattern is distinctive. The server's CPU graph looks normal. Players far from the base report no problems. Whoever arrives at the main base sees their frame rate drop, monsters near the base stutter, and the person who was there first is blamed for having a bad connection. If that matches, count the animals before you look at anything else.
Valheim base placement for shared servers explains how far apart heavy things need to be before standing in one stops loading the other. The short version for pens: a few dozen metres from the main hall is enough to stop players from loading the barn every time they craft, and further is better for a large one.
Feeding, pens and keeping tames alive#
Tames die. Raids target bases, and a raid that arrives while the group is out can kill a whole pen of boars. Wolves charge into fights they cannot win. Lox and asksvin take environmental damage like anything else. There is no respawn - a dead tame is gone, and what it drops lies on the ground with everything else.
Useful habits that cost nothing:
- Build pens inside the base defences. A raid that spawns at the edge of a base kills whatever is outside the walls first.
- Make feeding easy. A feeding trough is just food dropped on the floor inside the pen. Keep a chest of animal food next to the pen and agree who refills it.
- Name the important ones. Tames can be named, which makes it obvious that a lox belongs to someone's project and is not spare.
- Do not let pens touch walkways. Animals push players, and a wolf that blocks a doorway is a small daily irritation for everyone.
- Use a pit for asksvin. They break stone walls. A deep pit holds them where a fence does not.
Tamed animals have no owner. Anybody on the server can command, feed or ride a tame, and wards do not protect animals the way they protect pieces and chests. If your group has strong feelings about "my wolves", that has to be a rule, not a game feature. Wards and griefing covers what wards do protect.
Culling the surplus#
Players cannot kill their own tamed animals with ordinary attacks. The intended tool is the butcher knife, which kills a tame in one hit, and that is the right way to turn surplus boars into meat or to thin an overgrown wolf barn. Ask before you use it on animals somebody else bred.
Admins with devcommands have stronger tools, and they are blunt. On a vanilla dedicated server devcommands does not work at all; on a server with the ServerDevcommands mod these are the ones that touch tames:
| Command | Effect | Use on a shared world |
|---|---|---|
killall | Kills every creature nearby, tames included | Almost never near a base |
killenemies | Kills nearby enemies, spares tames | The safe one for clearing monsters |
killtame | Kills nearby tamed creatures | Culling a runaway barn, with consent |
tame | Tames every tameable creature nearby | Restoring a pen after a loss |
devcommandskillenemiesIf a tame cull goes wrong, a backup restore is the only real undo. Valheim server backups and world corruption covers taking one, and restoring rolls back the whole world, not just the animals - which is why the backup should be taken immediately before the cull, not the night before.
Dead tames leave drops, and a mass cull leaves a carpet of meat and pelts. Pick it up, or clear it, because items on the ground are their own performance cost; dropped items and world cleanup has the details.
Tame rules worth setting for a group#
For a group of friends, one conversation is enough. For a public server, write it down. These are the rules that prevent the problems above, with the reason beside each so people follow them:
1. Up to 10 tames per player. Breed for a purpose, cull the rest. Reason: big pens lag everyone who walks past them.2. Pens at least 50 m from the main hall, portal hub and docks. Reason: whoever stands nearest pays for the animals' AI.3. Stop feeding a pen that is full. Hungry tames do not breed.4. Followers stay home when you log off. A wolf left in someone else's base is your wolf in their base.5. Ask before culling or riding someone else's animals.6. Admins cull runaway pens after warning in Discord, with a backup.Ten per player is a starting point, not a measured limit; the community server rules post uses the same number for the same reason. A small group can be generous. A public server with twenty regulars and an unlimited tame rule will eventually have one barn that ruins one area of the map.
Two more decisions belong at the start, not after an argument:
- Wolves as raid defence. A pack of wolves around the base does make raids easier. It also makes the base the expensive zone on the server. Agree on a pack size.
- Shared livestock. A communal boar pen and a communal hen coop, fed from a shared chest, means nobody needs their own. That is the single most effective way to keep the total count down. Shared farming and food covers running the food side of the base as a group.
Mods that change taming and breeding#
Breeding behaviour is one of the more commonly modded systems, and mods here have to be treated like any gameplay mod: server and every client on the same version, usually with config enforced from the server. The pattern to look for on Thunderstore is a mod that exposes the per-species population cap and check radius as config values, so you can tighten them rather than loosen them. Lowering a wolf cap is a far more useful change on a busy server than raising one.
Before you add one, read Valheim mods with BepInEx on a server for the install, and remember the cost: any mod that clients must have rules out Xbox players on a crossplay server. For most groups, the vanilla cap plus a feeding rule does the job without a mod.
On RE:NODE, the parts of this that touch the server are already in the panel. The console graphs show memory and CPU against the plan's limits, which is the quickest way to prove that tame lag is not the server's problem. Backup slots come with every Valheim plan, so a snapshot before a cull is one button, and so is restoring it. And the Schedules tab can run a daily backup at an hour nobody plays, so the copy you need after an accident is never older than a day.
FAQ#
Why have my tamed animals stopped breeding?
Usually one of three reasons: they are hungry, the population within roughly 10 metres is already at the species limit, or nobody has been close enough to keep their zone loaded. Feed them, move some animals out of the check radius, and stay nearby for a while.
Do tames keep breeding while everyone is offline?
No. A creature is only simulated when a player is close enough to load its zone. With nobody nearby, a pen is frozen exactly as it was left - no hunger, no breeding, no wandering.
Will a bigger server plan stop the lag around our wolf barn?
Rarely. The AI and physics of nearby creatures run on the player who owns the zone, not on the server. If the server's CPU and memory graphs are well under their limits during the lag, the fix is fewer animals or moving the barn away from busy areas.
Can another player steal or kill my tames?
Anyone can feed, command or ride a tamed animal, and wards do not protect creatures. Ordinary attacks do not hurt tames, but a butcher knife or an admin command will. Protecting someone's animals is a server rule, not a game mechanic.
How do we get rid of fifty extra wolves?
Stop feeding them so the pen stops growing, then cull with a butcher knife. An admin running ServerDevcommands can use killtame while standing inside the pen, but it kills every tame in range - take a backup first and warn everyone.
Do hens need a dedicated server to work?
No. Hens hatch from eggs kept warm by a fire under a roof and are tame from birth, on any server or in single player. On a server the egg still only warms and hatches while someone is nearby to keep its zone loaded.


