Raven Iron Mods

Navigation Mod

Cairn

Stack stones on a headland and they burn — a trail of waymarks you build yourself, lit and remembered, on a world with no map.

ReleasedValheim / UnityC#v0.11.0

About Cairn

Versionv0.11.0
PlatformsClient, Dedicated Server, Linux, Windows
ReleaseOctober 19, 2026
StatusReleased

On a world with no map, knowing where you are is knowledge — and it lives in players’ heads and in screenshots pasted into Discord. Cairn moves it into the world, where it can be built, found, lit, and lost.

It adds no pieces, no assets, and nothing to your screen. It changes one vanilla piece: the Hoe’s stone, so that stones stack.


Building A Cairn

Stack four stones. Placeable_Stone is a vanilla Hoe piece costing one stone each, so a cairn is four stone and a minute’s work. Keep each stone within about 2.5 metres of its neighbour — the links chain, so a curved pile still counts as one cluster, and stacks that stand that close to each other join into one cairn with one light — and keep the whole pile no more than four metres across; spread past that and it reads as a building rather than a waymark, because a cairn is narrow and a building is wide, and that is how the mod tells them apart. The four metres is measured across the ground, so height does not count against it. By default a cluster counts as a cairn at four to a hundred stones — more than that is a structure, however narrow.

Stones stack. In vanilla a stone cannot go on another stone — the Hoe’s stone shows red when you aim it at one — so a cairn would have to be a ring on the ground. With Cairn a stone goes on a stone and the stack stays standing, so a cairn can rise. Only stones go on stones: a wall, a beam or anything else aimed at a stone still shows red, so a single pebble never becomes a foundation. This is the one vanilla piece Cairn changes, and it is a setting — StackableStones, on by default; false leaves the stone exactly as the game made it.

It lights itself. Within about twenty seconds — the length of the server’s sweep, by default — a fire appears on the crown, and it can be seen from hundreds of metres away.

Name it, if you want. Put a sign within six metres and write on it, and the place has a name. The six metres is measured along the ground, so a sign low on the side of a tall cairn still counts. A sign names one cairn: if two stand within reach of it, the nearer takes the name and the other stays lit, unnamed or named by a sign of its own. There is no map, so Cairn shows a name in only two places — Hugin the raven may say it when you stand at the cairn, and cairn landmarks lists it. A cairn with no sign is still a lit waymark — plenty of them should be.

Every one looks different because you built it, and uninstalling the mod leaves what it appears to be: a pile of rocks with a sign on it — though stones stacked on stones may fall once the mod is gone, because vanilla does not let one stone hold up another.


The Light

It holds roughly its size at distance rather than shrinking away — a fire on a far headland reads as a point of light the way a real one does, not as something that gets small until it is gone. Seen down a chain of fifteen cairns spanning 420m.

And it is hidden by terrain. A ridge between you and a cairn puts it out, so you have to move to see it. That is the difference between navigating and being told, and it is the reason this is a beacon and not a marker.

Colour is yours: BeaconColour takes hex — 4A9EFF for cold blue, 7CFF7C for something stranger. The default is firelight.

On a server, the lights reach your game as the server sends them: every lit cairn, up to BeaconMaxCount of them (250 by default). On a world with more than that, the server sends the ones nearest a player and the farthest stay dark until someone walks closer — so a cairn you have just built beside you lights. That is a cap on what is sent, not on how many cairns you can build, and in single player, or in the host’s own game, every cairn lights whatever it says. The server log warns once per session when it is over the cap.


The Raven

Stand at a named cairn and Hugin may land and say its name.

He is fussy, and deliberately so — vanilla will not land the bird below 30 metres of altitude, with anything hostile within ten metres, during a world event, or while tutorials are switched off in the game settings (vanilla counts the raven’s lines as tutorials). So he can be silent exactly when you would most want him, which is why nothing in the mod depends on him. He is a grace note, not a compass. cairn raven will tell you what it can see of why he has not come.


Your Tombstone

Optional, and off by default. On a world with no map there is no death pin, and finding your body can end a run. Turn on EnableTombstoneLights and a red light burns over your tombstone after you die.

  • Only you see it. The server tells every game where the tombstones are, and each game lights only the ones that belong to its own player — you see yours, other players see theirs.
  • Hills hide it, as they hide a cairn’s light, and it carries as far. You walk toward a glow you can see, not a marker.
  • It goes out once you empty the tombstone.
  • Older tombstones of yours that are still in the world get a light too, so turning it on also finds them.

It is not a landmark: it never enters the ledger, has no name, and Cairn stores nothing about it — the server finds the tombstones the world already holds, every few seconds.

Set EnableTombstoneLights on the server; in single player, set it in your own game. Any player can hide the light in their own game with ShowTombstoneLight = false, and TombstoneColour — hex, red by default — changes its colour in theirs. The server and every player who wants the light need Cairn 0.11.0 or newer; an older game simply ignores it.


What It Does Not Do

No map. No compass. No waypoints, markers, pins, arrows, HUD, or readout of any kind. If you learn where you are, you learn it by looking at the world.

It adds no prefabs — a cairn is recognised, never provided — ships no assets, and leaves vanilla recipes alone by default: StonePileStoneCost is the one setting that touches one, and it does nothing at its default of 0. The one vanilla piece it changes is the Hoe’s stone, so that stones stack, and StackableStones = false puts that back.


Technical Specifications

Parameter Detail
Runs On Client & Server — one DLL, all three roles
Target Runtime BepInExPack Valheim 5.4.2351
Engine Target Valheim (Unity Engine)
Requires Valheim 1.0.7 or newer — tested on 1.0.20
Current Version 0.11.0
Prefabs Added None. A cairn is detected, not provided
Vanilla Pieces Changed One — the Hoe’s stone, so stones stack (StackableStones, on by default)
Persistence Landmarks stored per world, beside the save, in plain text you can read. Tombstone lights store nothing

Configuration

Everything is in BepInEx/config/com.raveniron.cairn.cfg, and every value carries a note explaining what it costs. The ones most worth knowing:

Setting What it controls
PileMinPieces How many stones make a cairn (4) — raise it if decorative stones start lighting up
PileMaxPieces Most stones a cairn may have before it counts as a structure (100) — a backstop; the footprint rule does the real work
PileLinkMeters How close stones must sit to link into one pile — each to its neighbour, not across the whole pile (2.5m)
PileMaxExtentMeters The footprint that separates a waymark from a building (4m)
LandmarkPairMeters How far a sign may stand from the cairn it names (6m), measured along the ground
StackableStones Stones go on stones (on). false leaves the vanilla stone as the game made it. It is read on each player’s game, and on the server when the world loads — change it everywhere, then restart
StonePileStoneCost Stone cost of vanilla stone_pile — 0 (default) leaves it alone, anything else rewrites the recipe. It applies in the game of whoever sets it, so setting it on a dedicated server changes nothing for players
BeaconColour Hex, RRGGBB
BeaconMaxDistanceMeters How far a light carries (800m)
BeaconMaxCount The most lit cairns the server sends to players at once (250), nearest a player first. Not a limit on how many you can build. Set it on the server; 500 is the most it accepts
BeaconOcclusion Terrain hides beacons. Leave this on
EnableLandmarks The server’s sweep for stacked stones and the signs beside them. Leave it on — off, no new cairn is ever found, so none lights (cairns found earlier keep their light). It is not the switch for names: for that, turn off EnableRavenVoice or leave your signs blank
LandmarkRotationSeconds How quickly a new cairn is noticed (20s)
EnableRavenVoice The bird
EnableTombstoneLights A red light over your own tombstone (off). Set it on the server

When an update changes a default, Cairn moves your value only if it was still at the old default, and keeps anything you set yourself — the log says which, and the file as it was is saved beside it as a .bak before a value changes. The ConfigVersion line under [0 - Meta] records that this has been done; leave it alone.


Console

cairn status · landmarks · beacons · raven · prefabs <text> · pieces <text> · save

Each reports state rather than verdicts — beacons says whether a light is out of range or hidden behind a hill, raven shows whether a raven is in the scene at all, whether the game’s tutorials are off, your altitude against the 30-metre floor, and how far the nearest named cairn is. They exist because guessing at each of those cost an afternoon.

landmarks lists names: every one in single player, and when you play on a server the named cairns near you, nearest first, with how far away each is. status says whether tombstone lights are on and how many of the tombstones it knows about are yours, and on the server how many cairns are lit against how many are sent. pieces shows, for each buildable piece, whether something can be placed on it and why not.


Installation

Install on the server and the clients. One DLL does all three roles: a dedicated server sweeps the world and owns the ledger, a client draws the lights and carries the raven’s line, a listen host does both.

Stacking needs every machine, the server included: the player who places a stone checks the placement, and whichever machine owns a stack decides whether it stands. On an older Cairn, or with Cairn removed, stacked stones may fall.

Only the server sends beacons and tombstone positions. It drops any such push a client sends instead of relaying it, and a player’s game ignores one that does not claim to come from the server. Each world keeps its own ledger, and leaving a world saves it and clears its lights — so going from single-player to a server, or from one world to another, does not carry one world’s cairns into the next.


Compatibility

Little is patched that another mod is likely to want. Environment and weather are read-only, so the season mods are untouched; no prefab is added, so no save is at risk; and nothing is written to Minimap, so a map mod and this one simply ignore each other — though running both does rather blunt the point. The one hook on shared networking is a server-side check on routed messages: it drops only Cairn’s own beacon and tombstone messages when a client sends them, and every other message goes through as vanilla would handle it. The one hook near building is a postfix on the placement check, which can only turn a placement vanilla allowed into a refusal — a piece other than a stone aimed at a stone — and never allows one that was refused.


Download on Hexium →

Part of the RavenIron Suite

Every RavenIron project is engineered server-authoritative in C# and .NET, and shares the same forge.