[The Domain Game] part 2: Setting Up a Domain

Reconstruction of an early stage of Kidwelly Castle

 Now that you've convinced your players that having a base of operations is a good idea, they have to actually get one. While there are certain benefits that accrue to characters of a certain level upon acquiring such a base, it is not necessary that they are at that level before they can try. They can simply buy a building, of course, or pay to have one built, but other options exist. They might take over an existing castle or fort by replacing its current owners through proper application of force, which was mentioned in the comments to the previous post in this series. This is probably the most attractive option, especially if the players want to have an unusual and difficult to construct base of operations such as Quasqueton, the underground fortress built and then abandoned for unknown reasons by Rogahn the Fearless and Zelligar the Unknown, presented in B1 In Search of the Unknown. But players of a certain bent—I am certainly of this mind—will want to create their castle or whatever entirely from scratch. It's a similar sort of joy to that of playing a tower defense game, watching the defenses you designed operate to repel attackers, as well as being much like designing imaginary home floor plans. You can put in a library of the sort you would like to see, secret passages, and other objects of your home-owning fantasies.

Either way, the base of operations is going to cost the players money, and getting them to spend money is always a good thing. See page 25 of the DMG for the cost of maintenance, but the upshot is that it will cost 1% of the cost of the stronghold each month to keep it from starting to decay. There's no exact method listed for adjudicating what happens if that amount isn't paid, but any DM/GM is perfectly capable of introducing leaking roofs, cracks in the walls, and other home maintenance inconveniences based on their assessment of how much the players are underpaying. But how much did the place cost, since you need to know that to assess the maintenance cost? It's really a simple matter to just add up the elements, as listed in the DMG, again, this time on pages 106-108. It's perhaps a little more effort to figure out how many person-days of mining it took for excavated strongholds like Quasqueton in order to price how much the tunnels cost, but the information is there to do it. As an aside, if you can get them to do it, stone giants make the best miners, but dwarfs are not far behind and are much more hireable for the purpose.

While this is fine for the purposes of having a place to stash their stuff, players at lower levels will lack an important legal right: the right to tax the population. This only comes, for Fighters and Clerics, at 9th level, or 12th level for Magic-Users. Thieves don't worry about legalities, of course, but nobody takes a Thief seriously as head of a Thieves' Guild until they reach 10th level. This makes getting that maintenance cost much easier, though of course lower level characters can always go off adventuring to find treasure to pay for their home bases.

There are some other options, such as setting up a business (Dragon magazine issue 113 "A Capital Idea") or a mine (Dragon magazine issue 152 "In a Cavern, in a Canyon…"), or finding a similar business opportunity. Thieves can always set up a protection racket, run numbers, traffic in illegal items, or whatever, as long as they have the blessing of the local Thieves' Guild and pay their dues. Yay, sandbox play!

In any case, the players will be acquiring money and spending it. This is part of the reason that I usually suggest that the DM award XP for money spent (on most things; training is an example of a cost where I'd not award XP for the monetary outlay) rather than money acquired, and to go ahead and give players XP regardless of the source of the money. This encourages the players to, potentially at least, do more than just rob tombs all day erryday, and leads to more social roleplaying than murderhoboing.

Now, when they do get to the point of being able to legally tax their citizenry, that can end up being potentially very lucrative. A Fighter, in the Players Handbook, is able to get 7 silver pieces per month per inhabitant, on average. The article "Armies from the Ground Up" in Dragon magazine issue 125 offers guidelines on allowing the ruler to vary this rate from 5 silver pieces to 9 silver pieces, with rewards and consequences for the variations. If that particular system doesn't appeal to you, there's a similar but different system for setting different tax rates in "Meanwhile, Back at the Fief…", found in the same issue. But at the basic rate, with a modest population of only 10,000 scattered across the fairly large domain that AD&D assumes (for Fighters, a region ranging from 40 to 100 miles across, which is bigger than Luxembourg or Rhode Island; a 40 mile diameter circle is over 1250 square miles, compared to the roughly 1000 square miles of each of those two examples), gives 70,000 silver pieces per month. That is 3500 gold pieces per month, kids, or 42,000 gold pieces per year. It may take some time to build up to that level of population, of course, if the new domain is being carved out of the howling wilderness, but an active campaign of inviting settlers and accepting the wandering bands that show up will have the population getting up there.

The suggestion in the DMG (pages 93-94) is to start with campaign hexes of 30 miles across, divide them up into 1 mile hexes, then divide those up into hexes of around 200 yards across in the direct region of the place the players intend to build their fortress. These hex sheets, Trevor's Hex Grids, will come in handy for these suggestions, including a large hex divided into 30 hexes across, as well as a hex divided into 10 hexes across (a 1 mile hex divided into 10 across will have 176-yard smaller hexes, close enough to the DMG recommendation of ~200 yards). There's also a large hex divided into 24 across, in case you prefer a 24-mile campaign hex, or for that matter one that is 12 miles across such as I've seen used in one case for a hex map of North America. The players will then spend some time exploring and clearing these hexes of monstrous denizens, using the normal wilderness adventuring rules, to make them safe for the settlers to come. After clearing them, the players should set up patrols of mercenary or loyal soldiers to keep them cleared of intruders. At this time, the encounter checks are modified so that the whole domain experiences one check per day to see if some encounter has appeared on the perimeter, and another check per week to see if a monster or group has shown up in the interior of the domain.

If those encounters are with friendly types, such as "men", "elves", or the like, it is possible that they will settle down and join the growing population of the domain. If a monster or other hostile, then the players will need to deal with them as appropriate. A lycanthrope, for example, might require figuring out who, exactly, is transforming and ravaging the people, while an ankheg needs to be tracked down and destroyed before it tears up too many farms. But does the lycanthrope really need to be destroyed? Maybe it can be recruited to aid the players' growing army, if they're willing to take on that risk. A wandering tribe of orcs or goblinoids might be defeated in open battle and run out of the domain, or they might be induced to settle down and ally themselves with the players. How will they react to being forced to pay taxes or to being called up for military service (see pages 105-106 of the DMG for one set of guidelines)? How will their proximity affect the human population of the region? And so on. So-called "wandering" encounters should be seen by the DM/GM as scenario, or at least scenario idea, generators. These adventuring possibilities, alone, will keep the players busy, but there's still more that can happen.