Aska NPC Villager Management: What I've Learned Running a Settlement
The thing that pulled me into Aska – and kept me there long after I'd poked at every other survival game on the shelf – wasn't the axe-swinging or the Viking aesthetic. It was the villagers. You're not soloing this one. You're running a little Iron Age HR department, and the whole game bends around whether your people are fed, warm, rested, and pointed at something useful.
I've sunk somewhere around forty hours into a single settlement now, most of it on a persistent LOW.MS server shared with two friends. In that time I've made most of the beginner mistakes at least once: summoned too early, built the bloomery on the wrong side of the river, let a whole household freeze because I forgot warmth was a need. This is what I wish I'd known sooner.
How summoning actually works (and what the game doesn't spell out)
Your first villagers don't come from an ability. They come from a structure you build – the Eye of Odin. It's a small 1x1 tile shrine that has to be placed on hoe-levelled ground inside your settlement. Until it exists, you are a solo Viking with a lot of trees to chop.
The currency for summoning is Jotun Blood, which you'll find mining blood-stained nodes out in the world with a stone pickaxe or better. The cost is five Jotun Blood per summon. Flat. It does not scale with your population.
This is worth underlining because a lot of guides get it wrong. What does scale is the arrival timer – the more villagers you already have, the longer you wait for the next one to show up. Early summons can turn up in about ten minutes of play. By the time you've got a dozen people, you're looking at a proper stretch. The cost stays five.
When you activate the Eye with blood loaded, it shows you two candidate villagers to choose between. Each candidate has five random perks, and the game reveals two of them up front – the other three you only learn as the villager works, eats, sleeps, and fights in your settlement. You pick the one whose visible perks fit what you actually need. More on perks in a minute.
Jobs and stations – who does what
New villagers arrive as Builders by default. Until you walk them over to a station and assign them, they'll help with construction and generic fetching. That's fine for the first in-game day or two, but you'll want to specialise them quickly.
The real roles, grouped by what they actually do:
Production
- Woodcutters – chop and haul timber.
- Hunters – bring back meat and hides from wild game.
- Fishers – assigned to fishing spots for a steadier, lower-drama food source.
- Farmers – tend plots and livestock; by far the most reliable long-term food once your settlement is stable.
- Cooks – assigned to a Cooking Hut, turning raw ingredients into proper meals (which feed villagers better than raw food).
- Smiths – assigned to the Bloomery and Workshops, refining ore and producing tools, weapons, and upgraded gear.
Support
- Firekeepers – keep fires and braziers fed. Easy to undervalue until you lose someone to cold.
- Kennel worker – assigned to the kennel, manages your tamed wolves.
Combat
- Barracks warriors – a Barracks assigns up to three warriors with a defence radius around the building.
- Archery Range archers.
- Watchtower guards stationed on the perimeter.
Militia assignment is a separate mechanic layered on top of this – you can call villagers off their day jobs into a militia when a threat turns up, at the cost of whatever they were doing.
A few rules I now live by:
- One villager, one station. Splitting them mentally is fine; the game expects a single assignment.
- Distance is the silent tax. A woodcutter whose cabin is on the opposite side of the settlement from the forest just… walks. A lot.
- Food producers near food storage. Smiths near the ore they refine. This is obvious until you're mid-build and it stops being obvious.
The six needs (and the three everyone forgets)
Every villager has six needs. If a guide is telling you three, that guide is pre-1.0 or wrong:
- Housing – each villager needs an assigned bed in a cottage or longhouse. No bed, no good rest.
- Food – cooked meals beat raw, and variety beats monotony.
- Water – rain collectors or wells inside the settlement radius.
- Rest – villagers sleep on a schedule. If their day is packed wall-to-wall with work or their home is too noisy/too cold, they sleep badly.
- Warmth – this is the one that'll gut you in your first winter. Firekeepers, hearths, indoor braziers. Don't assume summer layouts will survive December.
- Morale – a composite of everything else plus leisure. If the other five are covered, morale mostly takes care of itself.
Honest opinion: warmth and rest are the two needs players under-plan for. It's very easy to set up a settlement that runs beautifully in summer, then watch it fall apart the first time snow hits and your villagers are sleeping in unheated single rooms. Build for winter from day one.
Settlement layout – what actually worked for me
This is the one section that's more opinion than mechanic, so treat it as a prompt rather than a blueprint.
- Central storage. Put your main storage building roughly in the middle. Every villager traverses it. Every unnecessary metre they walk is time not worked.
- Production rings, not random scatter. Gather on the edge (forest, quarry, water). Process in the middle (bloomery, workshops, cooking hut). Store and sleep centrally. Materials flow inward, never criss-crossing.
- House clusters near work. A woodcutter's cottage belongs near the treeline. A smith's belongs near the bloomery. If you have a player-count house district "because it looks nice," accept the travel cost.
- Defence perimeter that matches your threat model. Watchtowers on the approaches, a Barracks covering the main gate, an Archery Range somewhere with clear sightlines. You don't need full walls on day one – you need eyes on the direction trouble actually comes from.
- Plan for the expansion you haven't built yet. Leave room for two more houses, another workshop, a second Cooking Hut. Settlements that run out of infill space get ugly fast.
Perks worth hunting for
Remember: two perks are visible at summon, three are hidden until they surface. Over dozens of summons, some perks have earned a spot on my mental shortlist:
- Cold Resistance / Snow Strider – these genuinely change winter. A villager who doesn't seize up in the cold can keep working when the rest of the settlement has retreated indoors.
- Craftsman – flat-out useful on a workshop smith. If one of the visible perks is Craftsman on a candidate, I almost always take that one for the Bloomery.
- Iron Stomach / Iron Lungs – the resilience perks. Boring on paper, load-bearing in practice, because they reduce the number of things that can tip a villager into the red.
- Night Shadow – a villager who works at night fills in the gap when everyone else is asleep. Pairs well with a Firekeeper role.
And then there are the negative perks. Chill Sensitive and Feeble Logger exist – if you see one on a visible slot and you're in a cold biome or leaning hard on woodcutting, pass.
My first villager, I picked purely for a crafting-adjacent perk on the visible slots. Turned out her three hidden perks included Night Shadow and one of the resilience ones. She became the single most productive resident of the settlement by accident. The lesson I took isn't "you'll get lucky" – it's that two visible perks is genuinely partial information. Don't agonise over the choice. Pick the less-bad option and let the hidden rolls do their thing.
Why a persistent server changes the calculation
This is where the hosting bit actually matters, and I'll keep it short.
Aska villagers continue working when players are offline, but only if the world is set to stay alive. On a peer-to-peer host, the world pauses when the host logs off – farms stop, crafting queues halt, winter stops ticking down but progress stops with it. On a dedicated server you can set keep server world alive = true in your server configuration and your settlement keeps running overnight. That means villagers gather, farms grow, food stockpiles build, and meanwhile your defences have to actually hold – because raids and seasons don't pause either.
More than in most survival games, this changes how Aska feels. You log in to a settlement that moved without you, good or bad. If you're running a four-player group on split schedules, it's close to essential – and it's the main reason I moved our world onto a LOW.MS Aska server after trying it peer-to-peer first. Persistent world, backups that aren't my problem, and enough headroom to grow the population without worrying about the host's laptop. If you're setting up for the first time, the getting started guide and the co-op settings walkthrough will save you an evening of trial and error; if things go sideways later, the troubleshooting guide covers the usual suspects.
Forty hours in, I've still got perks to uncover and a Barracks I keep meaning to rebuild in a better spot. That's Aska working as intended.