Valheim portal hub design for a shared server

A good Valheim portal hub on a shared server is a small, plain building a short walk outside the main base, with one portal per destination, every tag written down on a sign beside it, and a naming scheme agreed before the second person builds a portal. Vanilla portals pair one to one by exact tag, so a hub is really a row of separate pairs that happen to start in the same room. Get the names right and the hub runs itself for months. Get them wrong and players start arriving in each other's abandoned outposts, which is the most common portal complaint on any group server.

This post is about designing the hub itself. The mechanics underneath it - how pairing works, what a duplicate tag does, which items are blocked - are in Valheim portals: tags, pairing and teleport rules. If the server is not running yet, start with the Valheim dedicated server guide.

What a portal hub is, and why a group needs one#

In single-player, portals grow organically: one at home, one at the current outpost, rename and move as you go. With two or three people that still works. With six or ten it falls apart, for three reasons.

• Everyone builds portals. Each player has their own outposts, mining camps and private bases. Without a plan, the world fills with dozens of portals, half of them called home.
• Pairing is first come, first served. The server links any two unpaired portals with the same tag. It does not know which one you meant.
• Nobody knows what exists. A new player, or someone back after a fortnight away, has no way to see the network. There is no menu in vanilla; a portal shows only its own tag.

A hub solves all three. It gives the group one place where every shared destination starts, one set of names everybody uses, and one wall of signs that doubles as a map of the network. It also concentrates portal traffic somewhere you chose, rather than in the middle of whichever base happened to grow biggest.

What a hub is not is a portal network in the modded sense. Every portal in the hub still has exactly one partner. The hub is an arrangement of pairs, plus the discipline to keep them tidy.

Where to put the hub#

The rule that matters most is that arriving loads everything around you. When a player steps through a portal, their client loads the destination zones: the terrain, every building piece, every creature, every fire and smelter. If nobody else is there, that player also becomes the owner of those zones and starts simulating them. Valheim server lag: zone ownership and desync explains the mechanism in full; for a hub it boils down to this:

Zones in Valheim are 64 metres square, and a client keeps the zones around the player loaded, not just the one they stand in. A hub 60-100 metres from the base edge will not make the base vanish from view, but it does mean players arrive in a lighter area and the loading screen ends sooner. On a world where the main base has grown to thousands of pieces, the difference between arriving inside it and arriving beside it is noticeable on modest PCs.

Other placement rules, in order of importance:

1. Flat, natural ground. Do not level a hillside for the hub. Terrain edits are stored per zone and loaded by everyone who passes through, and a hub is the most-visited spot on the map. Find ground that is already flat - Meadows has plenty.
2. Near the shared storage, but not on top of it. The point of a hub is getting home with loot. A short path from the hub to the chest room is ideal.
3. Outside every private ward. A hub inside someone's ward means nobody else can add a portal to it. See Valheim wards and griefing for what a ward blocks.
4. Away from raid paths. Raids target bases. A portal is a structure with health, and a raid that flattens the hub breaks every pair at once - and a broken pair can re-pair with an old portal of the same name elsewhere.
5. Not in deep water or on a floating platform. Portals obey structural support like any other piece.

If the group has not built a main base yet, Valheim base placement for shared servers covers choosing one, including how far apart private bases should be.

A tag naming scheme that survives ten players#

Tag collisions are the whole problem a hub exists to solve, so the scheme is the most important design decision. A scheme that works on most servers has three rules.

1. Name the destination, not the location. The hub portal that goes to the swamp camp is tagged swamp-camp, and so is the portal at the swamp camp. Both ends describe the same link. You never need a separate "home" name on the far side.
2. Shared destinations have a short plain name. Private ones have an owner prefix. trader, bonemass, iron-1 belong to everyone. ana-base, dato-mine, luka-farm belong to one player.
3. Nobody uses a bare word for a private portal. No home, base, mine or farm without a prefix. These are the names everyone reaches for first, and they are the ones that collide.

A concrete table, as it might appear on the hub sign:

Some groups prefer a biome code plus a number: bf1, sw1, sw2, mt1, pl1, ml1, al1. It is shorter to type and sorts nicely on a sign, but it says nothing about the place, so it needs the sign to make sense. Either style works if everyone uses it.

A few practical points about tags:

• Tags are matched exactly. Swamp-1 and swamp-1 are different tags. Pick lower case and say so in the rules.
• Avoid trailing spaces. An invisible space at the end of a tag is a common reason two portals that "say the same thing" do not connect.
• Do not leave a portal untagged, even for a minute. An empty tag is a valid tag, and two empty-tag portals anywhere in the world will pair with each other.
• Name immediately, then furnish. The habit to teach is: place the portal, tag it, then build the walls.

Laying out the hub building#

A hub building does not need to be pretty, but some layouts are much easier to live with than others.

Layouts that work:

• A corridor. Portals in a line along both walls, a sign above each. Easy to extend - add a bay at the end - and easy to read. The usual choice.
• A ring. Portals in a circle facing a central point. Looks good, but it fills up and is awkward to expand without rebuilding.
• Two rooms. One for shared destinations, one for private bases. Useful on servers with more than six or seven regular players, where private portals would otherwise crowd out the shared ones.

Details that make a hub pleasant:

1. Leave space between portals. You arrive standing in front of the portal you came through, facing outwards. Portals packed shoulder to shoulder mean players walk straight back into the wrong one.
2. A roof and walls. Portals are structures and take weather damage when exposed, like any wood piece. A roof also keeps the interior dry for resting.
3. A fire and a bench, sparingly. A single fire gives a rested bonus and light. It also counts as a base piece for raid purposes, so do not overdo it. A dozen torches is a dozen light sources every arriving client has to draw.
4. A chest for portal mats. A shared chest with fine wood, greydwarf eyes and surtling cores means anyone can replace a broken portal on the spot. The recipe is in the portal rules post linked above.
5. An ore drop. On default portal rules, players cannot carry ore through. A chest just outside the far-end portals, labelled "ore for the boat", saves arguments. Moving metal the long way is covered in moving ore without portals.

Keep the hub to one or two zones' worth of pieces. It is visited more than any other place, so every piece in it is paid for many times over.

Keeping the hub from becoming a lag point#

A portal sitting idle costs almost nothing. The server periodically checks unpaired portals to see if a match has appeared, and with a few dozen portals in a world that is not something you will measure. The lag people blame on hubs almost always comes from what surrounds them, and from who owns the zone.

What actually makes a hub heavy:

• Building it inside or onto the main base. Every arrival loads the base. This is the big one.
• Decoration. Hundreds of decorative pieces, item stands and banners in a room everyone walks through. Each is an object every client must load.
• Light sources. Torches, sconces and braziers are cheap individually and expensive in bulk, especially on weaker graphics cards.
• Loose items on the floor. Players drop things by the portal to get through with ore-free inventories, and forget them. Items lying in a base area do not despawn, so they accumulate. The cleanup options are in Valheim dropped items and world cleanup.
• Tames parked at the hub. Animals are simulated by the zone owner and are some of the more expensive objects in Valheim. Do not keep the wolf pack in the portal room.
• Terraforming. Levelled, raised or path-painted ground all add terrain data to the zone. See Valheim terraforming on servers for how that is stored.

Zone ownership matters too. The first player to arrive at the hub becomes its owner and simulates it for everybody nearby. If that player has a poor connection, others standing in the hub see rubber-banding. The hub being small and quiet keeps the cost of that low; it does not remove it. When lag follows one player, the fix is the same as anywhere else - they step away or relog, and ownership moves.

Hub upkeep: retiring portals and handling breakage#

A hub drifts. Copper runs out, outposts are abandoned, people leave the server. Old portals with old names are where trouble comes from, because a broken pair re-pairs with any free portal carrying the same tag.

A short routine, every few weeks or after each boss:

1. Walk the hub and check every swirl. A dark portal has no partner. Either its far end was destroyed or someone renamed it.
2. Retire, do not abandon. When a destination is finished, rename both ends to something unique like retired-bf-copper, or deconstruct both. Never leave one end standing with its live name.
3. Update the sign. The sign is the network map. A sign that is wrong is worse than none.
4. Reuse names deliberately. If swamp-1 is retired and a new swamp outpost is built, call it swamp-2. Reusing swamp-1 invites the new portal to pair with a forgotten old one.
5. Repair after raids. A raid that destroys a far-end portal leaves the hub end dark. Rebuild it with the same tag at once, before somebody else's old portal of that name takes the link.

Handling the classic failures:

Admins can help with the last two on a busy server. With devcommands enabled, an admin can fly to a stray portal and fix it; the commands and their costs are in Valheim devcommands explained. Writing the naming scheme into the server rules - see writing rules for a public Valheim server - stops most of it happening at all.

Hubs on different portal settings#

The portals world modifier changes what a hub is for.

# Default: ore, bars and dragon eggs blocked-modifier portals normal# Metals allowed through - the hub becomes the logistics centre-modifier portals casual# No portals at all - no hub-modifier portals veryhard

On default rules, the hub carries people, food and gear. Metal travels by boat or cart, so the main base and its smelters should sit near the water, and the hub's far-end portals at mining camps need a dock or a cart road nearby. The hub is a convenience; the shipping lanes are the real logistics.

On `portals casual`, the hub becomes the most important building in the world. Ore goes straight from the mine to the smelter, so put the smelting room close to the hub and make the path between them short and wide - this is where every trip ends. Expect much heavier hub traffic, which is one more reason to keep the hub outside the base itself.

On `portals veryhard` there are no portals, and the equivalent of a hub is a harbour: docks, a shared boat shed and cart roads. Valheim world modifiers and presets covers the trade-off between these, and why changing the setting mid-world is harder socially than technically.

On a panel host the modifier goes in the Startup tab's extra-arguments field and takes effect at the next restart. On RE:NODE that is the Startup tab of the Valheim server, and since backup slots come with every tier, take a backup before changing the portal rules on a world that already has a network, so you can go back if the group does not like the result.

Modded hubs: portal menus and destination pickers#

Mods change the design problem completely. TargetPortal by Smoothbrain, the best-known of them, lets a portal open a map of other portals and pick a destination, so one portal in the hub can reach everywhere. That removes tag collisions as a concept and replaces the row of pairs with a single gate.

The costs are the same as for any gameplay mod:

• Every client needs it, at the same version as the server. Players without it are kicked or desync.
• It makes the server PC-only. Xbox and Game Pass console players cannot install mods, so a crossplay group with console players cannot use it.
• Patch day breaks it until the author updates. A hub that depends on a mod is a hub that stops working for a day or two after some Valheim updates.

Installing mods on both sides is covered in Valheim mods with BepInEx on a server. For most groups of up to ten, a vanilla hub with a good naming scheme is enough, and it keeps console friends in the game.

FAQ#

How many portals can a Valheim hub have?

There is no fixed limit in vanilla. Each portal is one building piece, and dozens are fine. What limits a hub in practice is readability and the cost of the building around it, not the portal count.

Should every player have their own portal in the hub?

For regular players, yes - one portal each, tagged with their name and -base, back to their private house. It stops private portals competing with shared names and makes it obvious who owns what.

Can two hub portals lead to the same destination?

Not with the same tag. Only two portals pair per tag. If two players want direct portals to the same outpost, build two pairs with different tags, such as swamp-1a and swamp-1b.

Why does our hub take ages to load into?

Usually because it sits in or next to a heavy base, or because the hub itself is crowded with pieces, lights and dropped items. Move the hub out or strip it down; a bigger server plan will not change client loading time.

Is it safe to move the hub to a new spot?

Yes, if you do it in order. Build the new hub portals with temporary unique tags, then retag them to the live names one at a time while deconstructing the matching old hub portal. Never have three portals with one live tag at once.

Do portal hubs work for Xbox players on a crossplay server?

Yes. Vanilla portals, tags and the portals modifier are all part of the game, so console players use the hub exactly as PC players do. Only modded portal menus exclude them.