Framework

What should players be able to upgrade in an RPG base?

Let players upgrade the parts of a base that change what they can attempt, who they deal with, or what they can protect: capabilities, defences, reach, people and services, standing, supplies and information. A forge, hidden dock or sensor array earns its place when it opens new actions, changes future choices or creates relationships. Costs and complications can add play, but they need not come with every upgrade. A passive bonus can help, but works best alongside a visible capability or choice. Offer fewer, larger choices with more than one good path.

A fortified courtyard at golden hour with a smithy under construction, scaffolding on a watchtower and a steward studying plans

Why upgrade lists go flat

Most base upgrade lists start as a reward table. Walls add defence, a library adds a bonus to research, a better galley improves recovery. Each item is reasonable, and after a few purchases the base is stronger without being any more interesting. Players stop reading the list because nothing on it changes what happens next session.

A useful test is to imagine the upgrade missing. If the campaign would play the same way without it, the upgrade may be only a number. If it gives the group a new route, ally or answer to a problem, it is doing visible work. A passive bonus can still be useful, but it should usually reinforce a capability or choice rather than be the whole reason the upgrade exists.

Upgrade categories at a glance

Category	The question it answers	Example upgrades	Possible cost, dependency or consequence
Capability	What new things can the group do?	Forge or workshop, laboratory, archive, hangar or stables, ritual chamber, training yard	Rare materials, specialist staff, accidents and failed projects
Safety and resilience	What can the base survive?	Walls or armour plating, watch posts, infirmary, backup power, stores, escape routes, flood or fire protection	Staffing or upkeep if the group wants to track it; a stronger base may draw a more serious attacker
Reach	How far does the party's influence extend?	Scouts, transport, messenger network, portal or jump gate, agents abroad, trade routes	Exposure, rival claims on the same territory, people far away who need protecting
People and services	Who becomes available?	Artisans, healers, spies, scholars, guards, merchants, diplomats, residents or crew specialists	Wages or personal wants; people may also be threatened or bribed
Standing and political power	How does the base change the party's social position?	Audience hall, guild charter, legal authority, embassy, public works	Obligations to superiors, envoys with agendas, envy from established powers
Economy and logistics	How does the base sustain itself?	Farms and granaries, workshops, market rights, salvage processing, fuel or power supply	Supply chains, taxes, bad harvests or labour disputes
Information	What can the party learn earlier or more reliably?	Observatory, spy network, records office, long-range sensors, paid informants	Leaks, false reports, and the question of who else is listening

The upgrade design test

Run each proposed upgrade through five questions before it goes on the list. You do not need a strong answer to every one, but an upgrade should manage at least two:

What new action does this enable? Name something the party can now try that they could not before: forge a key from a wax impression, reach an island in one tide, hear about a raid before it lands.
What new relationship or complication might it create? A workshop may depend on a craftsperson or rare material. An infirmary can simply save lives, though it might also draw people seeking care. A spy network may create a new source or a risk of leaks. These are possible hooks, not required drawbacks.
Who in the world notices or cares? A guild, a lord, a rival crew, a customs office, the neighbours. If nobody would react, the upgrade has no hooks outside the walls.
What does it take to build, and does it need upkeep? A build requirement can be coin, time, materials from a particular place, a specialist or a faction's favour; it can give the project a story. Treat upkeep separately: wages, fuel or maintenance belong in the campaign only if recurring management is part of the fun.
How does it alter future adventures? Some upgrades change which jobs the party can take, how far they can travel, or what they learn first. Those are the ones players remember.

If the answer to all five is "not much", the upgrade is probably decoration. Keep it as colour, or fold it into a larger upgrade that does pass.

Five ways to make upgrades available

How players earn an upgrade shapes what they chase between sessions. Each model suits a different campaign, and most tables do well mixing two or three:

Pay for it Spend coin, salvage or trade goods. Simple to run, though it can turn the base into a shop if nothing else is involved.
Work on it Use downtime or projects to build between adventures, and attract residents, crew or labourers if the work needs them. Oversight can matter if the table wants to play it out; the build need not go wrong by default.
Adventure for it Require a mission or discovery: recruit a master shipwright, survey a site, recover a blueprint or learn an old technique. The project can point towards an adventure.
Earn permission or access Tie some upgrades to reputation or faction relationships. The guild may send artisans only once it trusts the party or accepts an apology for last season's betrayal.
Build prerequisites Make one facility depend on another: a dry dock may need a harbour wall, or a spy network a trusted handler. Tiers give direction, but long chains can harden into one correct path.

Player priorities and more than one good path

Players invest in a base when their choices shape it. A group that builds a clinic, an intelligence network and guest quarters is creating a different kind of stronghold from one that builds walls, barracks and siege workshops. Ask: what does choosing this upgrade say about the base the players want?

Keep more than one good path. If one sequence is obviously best, the group will follow it and the base will look like every other group's. Offer two or three options that pull in different directions: a stronger wall or a better-paid watch, a trading post or a hidden dock, a research wing or a training yard. Each should be good at something different; complications are optional.

Let the fiction propose upgrades too. When a player says the crew needs somewhere to keep a prisoner, or the village needs a well that does not freeze, that request may be better than anything on a prepared list. Agree a clear build requirement and add it.

Example

Worked example: the same smithy, two ways

A fantasy party holds a small keep and has saved enough to build a smithy. The GM has to decide what the smithy does.

The bonus version: The smithy grants a bonus to crafting and repair checks made at the keep. The players buy it, note the bonus, and rarely mention it again. It is a reasonable choice, and it changes nothing about the campaign.
The version that opens play: The smithy lets the party repair gear between expeditions and attempt items they cannot buy, provided they supply the materials. Its master, Ilsa, will only stay if the keep can source good iron, so the party now cares about the ore road through the hills. Her work attracts two apprentices and a travelling tinker with rumours. The local lord notices that the keep can now arm its own guards.
Why it works: The upgrade adds a capability, a person with a want, a supply problem and a political reaction. The next session has a reason to visit the ore road and a lord who wants to know what the party is arming for.

Example

Cross-genre upgrades that change play

The same pattern holds outside fantasy strongholds. Each upgrade below changes what the group can do; some also create a complication:

Criminal crew: a hidden dock: The crew can move goods by water and slip out of the district when the watch closes the streets. The dock also sits on a rival gang's stretch of the canal, so every shipment is now a question of territory.
Sci-fi ship: a long-range sensor array: The party spots derelicts, patrols and distress calls earlier than anyone nearby. The array draws power the engines sometimes need, and its emissions are easy to detect for anyone who knows what to look for.
Settlement: a clinic: Wounded characters and residents recover faster, and the settlement becomes known as a place of care. That benefit may be enough on its own; if the campaign wants another hook, refugees might arrive or the healer might ask for an escort.
Why these work: None is only a bigger number. Each creates a visible capability, even when it does not add a new problem to solve.

Common problems and how to avoid them

Watch for these as the base grows:

Too many tiny upgrades Ten small choices produce less play than three large ones. Combine minor improvements into a single upgrade with a clear purpose.
Upgrades that only grant passive modifiers A bonus is fine as part of an upgrade. It works best when it reinforces a visible capability or choice, but it need not come with an obligation or complication.
A mandatory correct build path If one route is plainly best, adjust the costs or give the alternatives stronger reasons to exist. Players should argue about priorities, not look up the answer.
Upgrades with no visible fiction Describe the new building, the new faces and the new noise. If the players cannot picture the change, they will not remember it.
Upkeep by default Recurring costs are useful only when the group wants ongoing management. Settle one-time build requirements separately, and let a facility simply work if tracking its upkeep would add bookkeeping without play.
Upgrades as punishment magnets If every new building is attacked the following session, players learn to stop building. Let threats be telegraphed, occasional and answerable, and let some upgrades simply work.
Spreadsheet micromanagement Some groups enjoy tracking every sack of grain. Many do not. Unless the table has asked for it, track a few resources that matter and handle the rest in the fiction.

Build a quick upgrade menu

Before the next base-planning session, prepare two or three options:

Offer different priorities Give the options distinct strengths, with no single correct choice.
Name the capability State what new action, protection or reach each upgrade provides.
Make the build requirement concrete Name the materials, work, person or permission needed. Include ongoing upkeep only if recurring management suits the campaign.
Show who will notice Name a person, faction or neighbour who may care, without making their reaction a required penalty.
Leave room for another idea Invite the players to propose an alternative that fits the fiction.

Was this useful?

Systems built for this

Blades in the Dark
The crew sheet lists lair and crew upgrades such as a boat, a hidden lair, a vault and a workshop, which the crew earns through advancement.
Stonetop
The steading sheet ties each improvement to specific requirements such as people, materials, communal work or time, and some improvements change what the town can do.
Forbidden Lands
Stronghold rules let characters spend treasure and resources on facilities such as a forge, mill or better defences once they have claimed a castle or ruin.

Keep upgrades tied to the people and places they affect

Every upgrade that passes the design test creates links: a smithy to its master, the master to an ore road, the ore road to the lord who taxes it. Codex Cryptica keeps each of those as its own entry with connections between them, so when the party considers the next upgrade you can see who it will affect and what is already under strain.

Generate the settlement or ship that serves as the base, add the residents and factions who care about it, and record each upgrade with its cost, its keeper and the complication it brought.

Generate a settlement