Dwarf Fortress Wiki - User contributions [en]

World activities

2026-03-18T13:31:44Z

91.49.243.26: /* Notes */ Added note. Everybody feel free to verify for him/herself (and consider opening a bug-report).

{{migrated article}}
{{old}}
{{Quality|Unrated}}
{{av}}

After [[world generation]], game worlds continue to develop and advance while time passes in-game, simulating off-screen various activities in the world outside of the player's influence and without their direct input, referred to as "world activation".

World activation happens when you start a new [[Fortress mode|fortress]] or [[Adventure mode|adventure]] mode game, during the two weeks that pass in the [[calendar]] when you begin. Otherwise, it happens as [[time]] passes as you play at normal fortress/adventurer speed. You can play many games of [[Fortress mode|fortress]] and/or [[Adventure mode|adventure]] mode in the same world, each building up its history.

==Types of activities==
Types of activities that are simulated during world activation:

===Succession===
[[Historical figure]]s can get married, have children, do their various jobs, and die. All of their children can do the same, as they are also historical figures.

The various positions of [[nobles]] will either be inherited by another historical figure, or assigned to a new historical figure by the parent civilization when the position is [[Fun|vacated]] or they have an [[unfortunate accident]].
Conflicts over succession and illegitimate site ownership can emerge, and armed usurpations and insurrections can take place.

===Site changes===
[[Image:Legends_artifact_symbol_v50.07_01.png|800px|thumb|A legendary sword being made a symbol during world generation]]
Existing NPC [[site]]s are conquered, liberated, defended, destroyed, reclaimed and new sites are created[http://www.bay12forums.com/smf//index.php?topic=140544.msg6843526#msg6843526] while playing. Bandits will loot villages, armies will conquer cities, and forgotten beasts will ransack fortresses. Abandoned dwarven fortresses can be reclaimed by the player later.

As the player can do in [[fortress mode]], during [[world generation]] and [[world activities]]),{{verify}} certain [[item]]s, usually (always?){{verify}} [[artifact]]s, can also be chosen as the symbol of a [[army|group]]'s administrative position.

===Movement===
Consequently, all kinds of creatures and groups travel around on the world map. However, others teleport. No, really.

The following groups teleport:

* [[Caravan]]s
* [[Diplomat]]s
* [[Migrant]]s
* [[Megabeast|The]] [[Semi-megabeast|various]] [[Forgotten beast|beasts]]

The rest physically travel on the map, including:

* [[Bandit]]s
* [[Refugee]]s
* [[Scholar]]s
* [[Thief|Thieves]]
* [[Quester]]s
* [[Religion|Religious]] professions such as [[prophet]]s, [[monk]]s or [[pilgrim]]s
* [[Army|Armies]] like siegers or other invaders

[[File:Df goblins distracted by elves.png|thumb|Screenshot showing Goblin civs prioritizing conquering the Elves down south above attacking the player fort (here highlighted with a yellow 'A' due to the rumour of artifacts.) ASCII mode.]]

[[Army|Armies]] move around the map while playing for various reasons, including site invasion (not just to the player site), harassment, searching for work, reclamation of sites and more. As invaders need to actually travel the world map to get to your site, embarking close to a site of potential invaders increases the chances of an invasion. Other factors that influence the probability of an invasion are the "effective" population of said site{{verify}}, in other words, how many soldiers the site can spare to attack you. While a site may have a high population, it may be occupied with other, more important campaigns than the player's site.

The asterisks {{DFtext|*}} on the fast [[travel map]] in adventure mode are creatures and armies moving around on the world map.

===Non-player adventurers===
[[Quester|Non-player adventurers]] will group up in parties and wander around, or adventure alone. They will also go on [[quest]]s to retrieve [[artifact]]s in play, which they receive from [[historical figure]]s that are in power, for example, a lord or noble from another site. For fortress mode, this manifests as [[visitor]]s coming to your fort and requesting you hand over artifacts. If you say no to them, they may try to steal it from you, or outright attack your fort.

In adventurer mode, this is more subtle: non-player adventurers can be found who are looking for artifacts, and may compete with you when you are trying to get artifacts, if they happen to be looking for the same artifact. If you are holding the artifact they seek (even if you are hiding it in your backpack), they will try to mug you (like [[bandit]]s) and may also attack you, follow you around, or vocally demand that you give them the artifact.

==Information==
{{DFtext|Greetings from the mountainhomes. Let's discuss our situation.|7:1}}

In an active fortress session, the player will get information about current events through the [[liaison]]. During the [[meeting]], communication of this information is implied. The actual information will appear on the [[Civilization and World Info]] screen, under the "News and rumors" tab.

== Notes ==
* In older versions, any world activity stopped after [[world generation]] finished. This is no longer the case since v0.40.01 and the changing of this is what is usually referred to as "world activation". "Restarting" [[world generation]] is not planned.

* Currently when new sites are founded during fortress mode by other civilizations, ie. forest retreats, hamlets/towns, dark pits or hillocks, then the civ_id (and cur_owner_id) is not set properly (for the created site), which can potentially lead to problems. Also the cur_owner_id of a site is usually not updated, if another civilization takes over a site in fortress mode. Furthermore, in such cases, the flag "dead" (in the property "flags" of the entity) of the previous site government is not set to true. In such cases it can also happen, that a historical figure, who is created on-the-fly, to be the FORCED_ADMINISTRATOR is not associated with any entity (eg. not belonging to any group) at all (despite being the forced administrator of the new government) and the historical figure can - in that case - ie. lack skills (info.skills is nil for that particular historical figure). In case of a destroyed site getting reclaimed by any civilization then the cur_owner_id will still be set to -1 after successfully reclaiming a site (as destroying a site does set the cur_owner_id to -1). Furthermore in case of new founded sites no entity-site link to the civilization might get created (and vice-versa, eg. the site does not get an entry under entity_links pointing to the new civ and the civ does not get an entry in site_links to the site). None of the above (except a forced administrator not associated with any group) can be seen without using tools like dfhack (ie. as legends and the game usually do not display these things, only the possible side-effects can be experienced in-game).

{{World}}
{{Category|World}}
{{Category|Legends mode}}

Position token

2026-03-16T21:06:24Z

91.49.243.26: /* Responsibilities */

{{Quality|Fine}}
{{av}}
{{Modding}}
Position tokens define [[noble]] positions for civilizations and site governments, inside [[entity token]]s. In the vanilla game, position token definitions can be found in <code>[[Game folder|<Dwarf Fortress>]]\data\vanilla\vanilla_entities\objects\entity_default.txt</code>.

__TOC__
{{clear}}

==Code==
A position is defined with a position 'code', as an argument in the [POSITION]-tag. The same code may be used multiple times, they don't have to be unique. This code is used as reference by APPOINTED_BY, SUCCESSION:BY_POSITION, REPLACE_BY and COMMANDER. 'MONARCH' is an example of this code.

==Position tokens==
These tokens belong in an entity definition, applying to a position (such as monarch) and should follow the [POSITION:POSITION_NAME] token.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Arguments
! Description

|-
| {{text anchor|ACCOUNT_EXEMPT}}
|
| The position holder is not subjected to the [[Dwarven economy|economy]]. Less than relevant right now.

|-
| {{text anchor|ALLOWED_CLASS}}
| {{token|CREATURE_CLASS|creature}} token
| rowspan=2 | ALLOWED_CLASS: Only creatures with the specified [CREATURE_CLASS] token may be appointed to this position. Multiple entries are allowed. ALLOWED_CREATURE: Restricts the position to the specified creature and caste. Multiple entries are allowed. These tokens only apply within the entity’s own race (including its castes).
In world generation, they limit which units may be assigned to the position, but they do not prevent other creature types from acquiring the position through alternative means (for example, via a coup).
In fortress mode, these tokens are enforced during manual appointment and succession.
During world generation, if all allowed castes have a POP_RATIO of 0, a unit of an allowed caste will still be generated to fill the position.

|-
| {{text anchor|ALLOWED_CREATURE}}
| CREATURE:CASTE

|-
| {{text anchor|APPOINTED_BY}}
| position
| This position can only be chosen for the task from the nobles screen, and is available only if there is an *argument* present. For example, the GENERAL is [APPOINTED_BY:MONARCH]. Contrast [ELECTED]. Being appointed by a MONARCH seems to handle a lot of worldgen stuff, and interferes with fort mode titles. Multiple entries are allowed. If you have neither an ELECTED-token nor a APPOINTED_BY-token, the holder may always be changed (like the expedition leader).
''Read more: [[Advanced_Entity_Position_Mechanics#Appointment]]''

|-
| {{text anchor|BRAG_ON_KILL}}
|
| A creature that kills a member of this position will be sure to talk about it a lot.

|-
| {{text anchor|CHAT_WORTHY}}
|
| In adventure mode, when referencing locations, an NPC may mention this position holder living there or having done some deed there; it also means that the position exists in world-gen, rather than being created only at the end of world-gen.

|-
| {{text anchor|COLOR}}
| [[Color]]
| Creatures of this position will have this [[Color]], instead of their profession color, e.g. [COLOR:5:0:1]. It is also applied to the name of the citizen in the units-screen.

|-
| {{text anchor|COMMANDER}}
| position:ALL
| This position will act as a commander of the specified position{{verify}}. E.g. GENERAL is [COMMANDER:LIEUTENANT:ALL]. Unknown if values other than ALL work. Multiple entries are allowed.
''Read more: [[Army]]''

|-
| {{text anchor|CONQUERED_SITE}}
|
| This position is a puppet ruler, left behind in a conquered site.

|-
| {{text anchor|DEMAND_MAX}}
| number (0-100)
| How many demands the position can make of the population at one time.

|-
| {{text anchor|DESCRIPTION}}
| string. Readable up to 470 characters in the nobles' screen.
| description of this position in the nobles screen.

|-
| {{text anchor|DETERMINES_COIN_DESIGN}}
|
| The site's (or civ's) minted [[coin]]s, if any, will have images that reflect the personality of this position holder.

|-
| {{text anchor|DO_NOT_CULL}}
|
| The position won't be culled from Legends as "unimportant" during world generation.

|-
| {{text anchor|DUTY_BOUND}}
|
| Members of this position will never agree to 'join' your character during adventure mode. They also don't settle anywhere else but in the capital, and will not [[immigration|emigrate]] from their site. If they are not DUTY_BOUND, they will live anywhere as they like.

|-
| {{text anchor|ELECTED}}
|
| The population will periodically select the most skill-eligible creature to fill this position for site-level positions at the player's fort. For responsibilities or positions that use more than one skill, no skill takes priority in electing a creature: an accomplished comedian is more qualified for the TRADE responsibility than a skilled appraiser. A creature may be elected to multiple positions at the same time. Contrast [APPOINTED_BY].
''More info: [[Elections]]''
''Read more: [[Advanced_Entity_Position_Mechanics#Elections]]''

|-
| {{text anchor|EXECUTION_SKILL}}
| weapon skill
| A mandatory sub-tag of [RESPONSIBILITY:EXECUTIONS]. Determines the weapon chosen by the executioner for their work.

|-
| {{text anchor|EXPORTED_IN_LEGENDS}}
|
| The various members who have filled this role will be listed in the civilisation's history.

|-
| {{text anchor|FLASHES}}
|
| The creature holding this position will visibly flash, like legendary citizens. Represents a properly noble station by default.

|-
| {{text anchor|GENDER}}
| male/female
| The position can only be held by the specified gender. Currently bugged {{bug|2714}}

|-
| {{text anchor|KILL_QUEST}}
|
| The position can assign quests to adventurers.

|-
| {{text anchor|LAND_HOLDER}}
| importance tier (1-10)
| This is an alternative to SITE, allowing positions to be created at civ-level 'as needed' for all sites that meet the requirements to have them, which are the values set in [[Difficulty#Land_holder|land holder difficulty]] [[settings]]. The character is tied permanently to a particular site, but also operates at the civ-level.
''Read more: [[Advanced_Entity_Position_Mechanics#land holders]]''

|-
| {{text anchor|LAND_NAME}}
| string. Readable up to 21 characters in the nobles' screen.
| The name the area takes on when under the control of a LAND_HOLDER. E.g. for the DUKE, [LAND_NAME:a duchy]. If the position is not a [[LAND_HOLDER]], the land_name is still displayed left of the position in the nobles menu.

|-
| {{text anchor|MANDATE_MAX}}
| number (0-100)
| The maximum number of mandates the position can make at once.

|-
| {{text anchor|MENIAL_WORK_EXEMPTION}}
|
| The position holder cannot be assigned labors. It only works for [SITE]-positions.

|-
| {{text anchor|MENIAL_WORK_EXEMPTION_SPOUSE}}
|
| The spouse of the position holder doesn't have to work, either - see above.
|-
| {{text anchor|MILITARY_SCREEN_ONLY}}
|
| This position cannot be appointed from the nobles screen. Intended for militia captains and other squad leaders to reduce clutter. Currently nonfunctional{{bug|8965}}

|-
| {{text anchor|NAME}}
| singular:plural. Readable up to 21 characters in the nobles' screen and up to 30 in the unit list.
| The name of the position.

|-
| {{text anchor|NAME_MALE}}
| singular:plural. Readable up to 21 characters in the nobles' screen and up to 30 in the unit list.
| If the creature holding the position is male, this is the position's name. E.g. for MONARCH, [NAME_MALE:king:kings]

|-
| {{text anchor|NAME_FEMALE}}
| singular:plural. Readable up to 21 characters in the nobles' screen and up to 30 in the unit list.
| If the creature holding the position is female, this is the position's name. E.g. for MONARCH, [NAME_FEMALE:queen:queens]

|-
| {{text anchor|NUMBER}}
|
* number/AS_NEEDED
| How many of the position there should be. If the [SITE] token exists, this is per site, otherwise this is per civilisation. AS_NEEDED applies mainly to positions involved with the military command chain; this is used to allow armies to expand to whatever size they need to be. Other non-military positions like the land_holders or the [[messenger]] with NUMBER:AS_NEEDED will also be appointed.
The problem with [[Lieutenant]]s and [[Captain]]s not being created, is their AS_NEEDED number. They are only then created when they're needed, and that has some pretty unusual conditions. When a fixed number is used, they are appointed with the creation of the civ.
If the NUMBER is set at a fixed value higher than 1, the position is always filled up full. If the position is available on embark, it is completely filled up with only the first dwarf.

|-
| {{text anchor|PRECEDENCE}}
| number (0-30000)/NONE
| How important the position is in society; a lower number is more important and displayed higher in the Nobles menu. For MONARCH it's 1, for MILITIA_CAPTAIN it's 200.

The game marks the first non-[SITE] position with [PRECEDENCE:1] as the ruler, for both embark screen and mountainhome purposes. When it is empty, [REPLACED_BY] another position, or not yet created because of [REQUIRES_POPULATION], the screen just says 'None' as the holders' name.

Landholders can become the ruler, if they are the first defined position with precedence of 1. civ-position can also be created without precedence. Positions may have the same precedence and will be appointed, although the effect is unknown. Precedence has no effect on who's doing the job, if both positions have the same responsibilities.

|-
| {{text anchor|PUNISHMENT_EXEMPTION}}
|
| The position holder will not be held accountable for his or her crimes. Currently nonfunctional.{{bug|4589}}{{verify|seems to prevent punishment when they are convicted of actual crime}}

|-
| {{text anchor|QUEST_GIVER}}
|
| The position holder can give quests in Adventure mode. Functionality in 0.31.13 and later is uncertain.

|-
| {{text anchor|REJECTED_CLASS}}
| CREATURE_CLASS Token
| Creatures of the specified class cannot be appointed to this position. Multiple entries are allowed

|-
| {{text anchor|REJECTED_CREATURE}}
| CREATURE:CASTE
| Restricts position holders by CREATURE type. Multiple entries are allowed. It doesn't seem to work in world-gen. When checking Legends mode, units are seen assigned this position regardless of their creature-type or caste. It does work in Fortress mode.

|-
| {{text anchor|REPLACED_BY}}
| position
| This position is absorbed by another down the line. For example, expedition leader is [REPLACED_BY:MAYOR]. Only a single entry is allowed.

It can work with both [REQUIRES_POPULATION] and [REQUIRES_MARKET].

The tag differs in function for landholders, see [[Advanced_entity_position_mechanics]]

|-
| {{text anchor|REQUIRED_BEDROOM}}
| number (0-1000000)
| The position holder requires a bedroom with at least this value.

|-
| {{text anchor|REQUIRED_BOXES}}
| number (0-100)
| The position holder requires at least this many boxes.

|-
| {{text anchor|REQUIRED_CABINETS}}
| number (0-100)
| The position holder requires at least this many cabinets.

|-
| {{text anchor|REQUIRED_DINING}}
| number (0-1000000)
| The position holder requires a dining room with at least this value.

|-
| {{text anchor|REQUIRED_OFFICE}}
| number (0-1000000)
| The position holder requires an office with at least this value.

|-
| {{text anchor|REQUIRED_RACKS}}
| number (0-100)
| The position holder requires at least this many weapon racks.

|-
| {{text anchor|REQUIRED_STANDS}}
| number (0-100)
| The position holder requires at least this many armour stands.

|-
| {{text anchor|REQUIRED_TOMB}}
| number (0-1000000)
| The position holder requires a tomb with at least this value.

|-
| {{text anchor|REQUIRES_MARKET}}
|
| Does not have anything directly to do with [[trade depot|trade depots]]. It means that in minor sites (such as hillocks) the position will not appear, while in major sites (such as dwarf fortresses) it will. Depending on its economical position in the region, a [[hamlet]] may build a market and develop into a [[Town]] eventually. That is when this position becomes available. It only works in combination with the [SITE]-token.

|-
| {{text anchor|REQUIRES_POPULATION}}
| number
| The position requires the population to be at least this number before it becomes available, or before the position holder will move in.

|-
| {{text anchor|RESPONSIBILITY}}
| responsibility
| The position holder does a thing. See the table below for suitable arguments. A position does not need to have a responsibility.

|-
| {{text anchor|RULES_FROM_LOCATION}}
|
| If there is a special location set aside for rulers, such as a human castle/mead hall, the position holder will always be found at that particular location. Does nothing for dwarven nobles, because at present, dwarves have no such special locations.

|-
| {{text anchor|SITE}}
|
| Every site government will have the defined number of this position instead of the whole civilization; provided that other criteria (if any) are met. Unless LAND_HOLDER is present instead, the defined number of the position will be created only for the civilization as a whole.

|-
| {{text anchor|SLEEP_PRETENSION}}
|
| The position holder will get upset if someone with a higher PRECEDENCE holds quarters with a greater value than their own.

|-
| {{text anchor|SPECIAL_BURIAL}}
|
| The civilization will inter the corpse of the position holder in a special grave, either in catacombs or in monuments. If that grave is disturbed, the position holder can return as a [[mummy]]. {{verify}}

|-
| {{text anchor|SPOUSE}}
| singular:plural. Readable up to 30 characters in the unit list.
| The name of the position holder's spouse.

|-
| {{text anchor|SPOUSE_FEMALE}}
| singular:plural. Readable up to 30 characters in the unit list.
| If the spouse of the creature holding the position is female, this is the spouse's position name.

|-
| {{text anchor|SPOUSE_MALE}}
| singular:plural. Readable up to 30 characters in the unit list.
| If the spouse of the creature holding the position is male, this is the spouse's position name.

|-
| {{text anchor|SQUAD}}
| number:singular:plural
| The position holder is authorized to form a military squad, led by themselves using the [[leader]] and [[military tactics]] skills. The number denotes the maximum headcount. The noun used to describe the subordinates (e.g. royal guard) is used in adventure mode for the adventurer. This token is used together with [RESPONSIBILITY:LAW_ENFORCEMENT] for giving [[quest]]s to adventurers as [[Hearthperson|hearthpeople]]. Further details: [[Advanced_entity_position_mechanics#Military]]

|-
| {{text anchor|SUCCESSION}}
|
* BY_HEIR / BY_POSITION:position
| How a new position holder is chosen. A single position can have multiple BY_POSITION tokens. See [[Noble]] for more information on how succession is handled in the game.
The SUCCESSION-Tag is also considered when a new positions opens up, for example when a required population number is reached. If a valid successor is available, they will be the one taking that position initially, without appointment or election.

|}

== Responsibilities ==
{| {{prettytable}}
|- bgcolor="#dddddd"
! Argument
! Description

|-
| {{text anchor|ACCOUNTING}}
| Found on [[bookkeeper]]. Position will use [[record keeper]] skill to keep track of stocks.

|-
| {{text anchor|ADVISE_LEADERS}}
|

|-
| {{text anchor|ATTACK_ENEMIES}}
| Found on elven [[ranger captain]] and human warrior. Effect unknown.{{verify}}

|-
| {{text anchor|BUILD_MORALE}}
| Found on [[champion]]. Citizens get a special thought for "talking to a pillar of society" when speaking to this noble.

|-
| {{text anchor|BUILDING_SAFETY}}
|

|-
| {{text anchor|COLLECT_TAXES}}
| Currently unused - was originally assigned to the tax collector.

|-
| {{text anchor|CONSTRUCTION_PERMITS}}
|

|-
| {{text anchor|DELIVER_MESSAGES}}
| Found on [[messenger]]. Position travels to other sites and uses [[social skill]]s.
|

|-
| {{text anchor|EQUIPMENT_MANIFESTS}}
| Currently unused - was originally assigned to the arsenal dwarf.

|-
| {{text anchor|ESCORT_TAX_COLLECTOR}}
| Currently unused - was originally assigned to the Royal Guards (squad members beneath the Hammerer).

|-
| {{text anchor|ESPIONAGE}}
| Found on [[dungeon master]] and the [[Elf|elven]] [[General|princess]] and uses the [[schemer]] skill.

|-
| {{text anchor|ESTABLISH_COLONY_TRADE_AGREEMENTS}}
| Found on [[outpost liaison]]. Position travels with the caravan and uses [[social skill]]s to make trade agreements with any settlements that it visits, provided they are domestic, report the news and promote {{token|LAND_HOLDER|e}} positions. Also reports recent news. Presumably has no effect at site level. Crucially, it does not visit foreign settlements, but the civ-level TRADE position does the exact same thing in its position. They arrive the same time as the caravan arrives, and this can thus be modded by setting {{token|ACTIVE_SEASON|e}}

|-
| {{text anchor|EXECUTIONS}}
| Found on [[hammerer]]. Position executes death penalty judgements with a weapon of the appropriate skill. Cannot be combined with LAW_ENFORCEMENT, resulting in the "Invalid Officer"-error.

|-
| {{text anchor|FIRE_SAFETY}}
|

|-
| {{text anchor|FOOD_SUPPLY}}
|

|-
| {{text anchor|HEALTH_MANAGEMENT}}
| Found on [[chief medical dwarf]]. Position will use [[diagnostician]] skill to evaluate [[wounds]] and schedule [[Health care|treatment]], reported in each citizen's Health tab.

|-
| {{text anchor|JUDGE}}
|

|-
| {{text anchor|LAW_ENFORCEMENT}}
| Found on [[sheriff]]/[[captain of the guard]]. Position and its subordinates are in charge of punishing criminals. A {{token|SITE|position}} position holding this responsibility plus the {{token|SQUAD|position}} token (or allowing the entity to have a {{token|SITE_VARIABLE_POSITIONS|e}} with this responsibility) is required for an adventurer from a given civilization to start as a [[hearthperson]], [[Captain of the guard|fortress guard]], etc. Cannot be combined with EXECUTIONS, resulting in the "Invalid Officer"-error.

|-
| {{text anchor|LAW_MAKING}}
| Found on [[monarch]]s and [[:Category:Aristocrats|nobles]]. Will be referred to as the leader of the site in adventure mode and they may designate the site as being the capital city for civ-level positions. This position is in charge of creating procedural positions, corresponding to either {{token|VARIABLE_POSITIONS|e}} or {{token|SITE_VARIABLE_POSITIONS|e}}. Position-holders that have attained [[immortality]] may issue oppressive edicts to protect themselves against suspicion.

|-
| {{text anchor|MAINTAIN_BRIDGES}}
|

|-
| {{text anchor|MAINTAIN_ROADS}}
|

|-
| {{text anchor|MAINTAIN_SEWERS}}
|

|-
| {{text anchor|MAINTAIN_TUNNELS}}
|

|-
| {{text anchor|MAKE_INTRODUCTIONS}}
| Position will make a 'social call' to an established foreign settlement, complimenting or insulting them depending on relations and reporting the news.

|-
| {{text anchor|MAKE_PEACE_AGREEMENTS}}
| Found on diplomat. Position negotiates peace treaties in order to end wars.

|-
| {{text anchor|MAKE_TOPIC_AGREEMENTS}}
| Found on [[diplomat]]. Position negotiates special agreements, such as tree cutting quotas. Used when elevating a settlement in the {{token|LAND_HOLDER|position}} chain up from level 1.

|-
| {{text anchor|MANAGE_ANIMALS}}
| Found on [[dungeon master]].

|-
| {{text anchor|MANAGE_LEADER_HOUSEHOLD_CLEANLINESS}}
|

|-
| {{text anchor|MANAGE_LEADER_HOUSEHOLD_DRINKS}}
|

|-
| {{text anchor|MANAGE_LEADER_HOUSEHOLD_FOOD}}
|

|-
| {{text anchor|MANAGE_PRODUCTION}}
| Found on [[manager]]. Position enables the use of workshop profiles and uses the [[organizer]] skill to process work orders entered in the job manager after the fortress population reaches 20.

|-
| {{text anchor|MEET_WORKERS}}
| Found on [[expedition leader]]/[[mayor]]. Position uses the various [[social skill]]s to hold meetings with unhappy citizens and try to pacify them with happy thoughts. In adventure mode, [SITE] positions with this responsibility handle petitions to make the player a performer for the local government.

|-
| {{text anchor|MILITARY_GOALS}}
| Found on [[monarch]]/[[:Category:Aristocrats|landholder]]/[[:Category:Elected Nobles|leaders]]. Character is in charge of going to war and making peace for the government they work for. Without a position with this responsibility at civ level the civilization will not be able to make peace and its sites will wage war on each other constantly, and as a result, all viable civilizations must have one leader with this tag at civ level. This appears not to be a problem for [[kobold]]s, presumably due to the {{token|SKULKING|e}}. If no position has this responsibility in fortress mode, players are unable to start [[missions]].

|-
| {{text anchor|MILITARY_STRATEGY}}
| Found on [[general]]/[[militia commander]]. Means that they will command the armies of their site or civilization. Issues the orders for the teams conducting raids or other operations away from the fortress. During worldgen, positions (of a civilization) will go on expeditions to tame exotic creatures (but this only yields a pet, not any training knowledge, and only of a race, for which the civilization has already some training knowledge). Counterintuitively not by the TAME_EXOTICS-position. The destinations of these expeditions are determined by the entities USE_(...)_ANIMALS-tokens.

|-
| {{text anchor|OVERSEE_LEADER_HOUSEHOLD}}
|

|-
| {{text anchor|PATROL_TERRITORY}}
| Found on elven ranger captain. Effect unknown.{{verify}}

|-
| {{text anchor|PREPARE_LEADER_MEALS}}
|

|-
| {{text anchor|RECEIVE_DIPLOMATS}}
| Found on [[monarch]]/[[:Category:Aristocrats|landholder]]/[[:Category:Elected Nobles|leaders]]. Position uses the various social skills to hold meetings with incoming diplomats and liaisons.

|-
| {{text anchor|RELIGION}}
| Found on elven [[druid]] and uses [[social skill]]s. Position informs you about worship cults{{verify}}

|-
| {{text anchor|SORT_AMMUNITION}}
| Currently unused - was originally assigned to the arsenal dwarf.

|-
| {{text anchor|TAME_EXOTICS}}
| Position will tame animals with the {{token|PET_EXOTIC}} token. Currently unused - was originally assigned to the dungeon master. Expeditions to tame exotic creatures will be done by the MILITARY_STRATEGY-position

|-
| {{text anchor|TRADE}}
| Found on [[broker]]. Position will use Appraisal skill to display value estimates and the various Social skills to trade at the depot. When applied to other civilizations, this position will arrive with the caravan to make trade agreements (like the Human Guild Representative from older versions) and behaves otherwise like the civ's own ESTABLISH_COLONY_TRADE_AGREEMENTS position holder. They arrive the same time as the caravan arrive and this can thus be modded by setting {{token|ACTIVE_SEASON|e}}

|-
| {{text anchor|UPGRADE_SQUAD_EQUIPMENT}}
| Currently unused - was originally assigned to the arsenal dwarf.

|}

== Related tokens ==
The following two ENTITY tokens are not actually position tokens, but bear mentioning on this page because they can modify the way that a civilization's positions behave:

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Arguments
! Description

|-
| {{text anchor|VARIABLE_POSITIONS}}
| Position responsibility or ALL
| Allows a responsibility to be taken up by a dynamically generated position (such as Law-maker).

|}

== Why won't my positions appear? ==
The way DF determines what positions will actually ''appear'' in your fortress is somewhat counter-intuitive and fairly limiting. This guide should help you understand what you can do to actually get your positions working properly.

There are five tokens governing which positions appear in your fortress - LAND_HOLDER, REQUIRES_POPULATION, APPOINTED_BY, ELECTED, and REPLACED_BY. The first two determine when your fortress is eligible for a new position, the next two determine how a new position for which your fortress is eligible can be added, and the fifth allows you to clear up obsolete positions. Unfortunately, they also interact in some strange ways that makes creating interesting position structures difficult.

When you start a new fortress, DF compiles a list of your initial positions. To do this, it looks at the requirements for each position - any position whose only requirement is less than seven dwarves (either because they have no requirement tokens, or because their only requirement tokens are [REQUIRES_POPULATION: =< 7] or [LAND_HOLDER:some trigger whose only requirement is some number of dwarves equal to or less than 7]). Most importantly, ''any'' position whose only requirement is a LAND_HOLDER requirement, regardless of what the trigger for that requirement is, will be added if another eligible starting position is REPLACED_BY it. '''A non-LAND_HOLDER position that is REPLACED_BY a LAND_HOLDER position will never appear.''' With this list compiled, the game culls all positions that are REPLACED_BY another eligible position, and then culls all positions that have the APPOINTED_BY token. '''You may not embark with any appointed positions.''' Any remaining positions are then filled by a dwarf chosen at random.

'''Positions do not automatically appear when you reach their requirements.''' For example, if you remove the ELECTED token from the Mayor, then the Mayor will never appear, even once you reach their required number of dwarves. '''For a position that does not appear at embark to appear in your fortress, it must be APPOINTED_BY another position or ELECTED.'''

Naturally, this is more complicated than it looks. '''APPOINTED_BY positions must be appointed by another position already in your fortress, or a civ-level position. Only LAND_HOLDER positions may be appointed by civ-level positions.''' LAND_HOLDER positions that are APPOINTED_BY civ-level positions are inherently tied to civ-level tokens with the ESTABLISH_COLONY_TRADE_AGREEMENTS responsibility. If a fortress meets the LAND_HOLDER_TRIGGER for a new LAND_HOLDER tier when a caravan leaves, then the next time the outpost liaison or equivalent arrives, they will offer to make you an official colony, which will allow you to select all positions for that LAND_HOLDER level. '''Each time they appear, the outpost liaison will only promote your fortress one tier up the LAND_HOLDER track.''' The biggest problem with this system is that you may set your LAND_HOLDER_TRIGGERS such that you are eligible for the first tier of LAND_HOLDER positions at embark. '''If you are eligible for the first tier of LAND_HOLDER positions at embark, then all first-tier positions will appear twice - once at embark, and again when the outpost liaison comes to appoint you to the first tier.'''

If civ-positions are neither APPOINTED_BY nor ELECTED, they still will be filled.

Read more: [[Advanced_Entity_Position_Mechanics]]

{{Category|Modding}}
{{Category|Tokens}}
[[ru:Position token]]

Talk:Variable positions

2026-03-16T17:03:19Z

91.49.243.26: /* Holding multiple variable positions in world-gen. */

----Hi! nice work so far!
A few points:
* I really wonder where the differences between human and goblins are coming from. Do you have any idea? I almost know for sure that the difference in MARKET-positions is because of humans have the CITY- type in DEFAULT_SITE_TYPE. But the others, I dont know. perhaps because of their values or ethics?
* There is a lot of vague language in this article ('Some religious entities(...)', which ones?), but also to much certainty, at places :-) . I would suggest to make it more tight. ChatGPT or another text AI can be of good use there, to remove any ambiguity
* The number of -1 is very strange to me, because this is an invalid value when writing raws for entities. Do you have any idea what the circumstances are for these positions? I see for example with the priests. Can it be that PRIEST is REPLACED_BY HIGH_PRIEST and also by highest priest? In that case, number -1 means: "currently replaced". It should not have a current holder. For example, can you check a site with a mayor, does the expedition leader has -1? in that case, its caused by replacement.
* Landholders are a strange bunch, I'm curious if you find out anything about those!
[[User:Joostheger|Joostheger]] ([[User talk:Joostheger|talk]]) 12:22, 12 February 2026 (UTC)

Thank you.
* Not sure. The thing is even if the goblins do overtake another site, no market officials will be created. So it is more likely an ethics or values thing. The same for the reduced number of different officials.
* Well no. And the thing about "Some religious entities" in that case is, that some religious entities do not have any positions (eg. due to no variable position being created during world gen for these religious entities), but all of these entities (with no positions) will probably not create an abbot (CUSTOM_LAW_MAKER), but priest and so on (if the world-gen could/would be restarted). But without checking all religious entities without positions in detail, it might be that in some cases an religious entity (which could create an abbot) does not have a position at the end of world gen. So while there is from one perspective some ambiguity, from another perspective it is very precise.
* The number -1 means that it is unlimited, meaning for that position an unlimited amount of assignments can be created.
* No there is no replacement between the priest. Look at the responsibilities for priest and the others. Also the highest priest is capped at one (ie. like the pope), while their is an unlimited number of high priests possible (like cardinals or bishops).
* So far all entries in the variable position were empty. So it seems that neither humans nor goblins are landholders. And I still need a little bit more familiarity with Lua, for a few more complicated scripts (which also correctly query the different abstract building types).

In general some info is still missing. And also I am in a few cases not sure yet, what exactly is the case, so some ambiguity might also stem from that. Only at the last step I will try to remove (unneccessary) ambiguity.

ps. At some point the commented out text passages should be removed (deleted), but if I would try to do it, it will be detected as possibly harmful and not be allowed.[[Special:Contributions/91.49.240.46|91.49.240.46]] 13:15, 12 February 2026 (UTC)
----
* Ok ill help you remove the commented lines, but you really should create an account :-)
* The number unlimited is written in the raws as AS_NEEDED. is that correct? If you, i'll suggest to replace the -1 with AS_NEEDED, to make that consistent with other positions and understandability
* I dont think you'll find any other landholders by the way. I think it isnt in variable positions to have that. Landholders arent also neccesary to let the game run and simulate an interesint world, while these variable positions are.
[[User:Joostheger|Joostheger]] ([[User talk:Joostheger|talk]]) 14:52, 12 February 2026 (UTC)

----
* Well I might eventually create an account, iff no email address (etc.) needs to be provided.
* The translation of data into understandable form is not a priority, but -1 will be changed eventually (or a note added).

ps. I will probably not edit anything in the next few hours on the article, so now or maybe tommorrow might be a good idea to remove the lines currently commented out.[[Special:Contributions/91.49.240.46|91.49.240.46]] 15:21, 12 February 2026 (UTC)

----
Most of the "easy" work has been done. Next steps would be (not necessarily in the stated order):
1. replacing/removing the technical flags.
2. further research on what the concret requirements for the creation of different official and market official positions on site level is.
3. Figureing out the reason why goblins so far only create variable positions on site level, when the leader was a custom bandit leader (ie. at least in case of the forced admin it should be possible).
4. Figureing out why the goblins only create a subset of all possible variable official positions (both on site and civ level).
5. Researching why the goblins do not create custom market officials.
6. Figureing out why in some cases the dwarves use the generic forced admin and not the forced admin from the dwarven raws.
7. Removing any ambiguity (if possible) from the page and improve understandability. For that I suggest that with pointing to the unclear part a discussion entry is made, so that I am made aware of it and can then clear it up.
8. Improve formatting and table presentation: ie. possibly move some info to other tables to reduce table width (of the existing table). Or use smaller fonts (scaling) for some table entries. etc.
9. Figureing out (and testing) which other values in the tags [variable_positions] (and variable_site_positions) are valid. I do not think that it is only [variable_positions:all]. (This won't be done by me).
10. Add section(s) for modifing the game data, so that in an existing world a few more variable positions are created (and filled with historical figures). So that the variable positions then function as if the variable positions had already been created (and filled) during world gen.

I am probably missing a few things. But that is all for now, from my part. Further edits (by me) to the variable positions page will not be done before next week.[[Special:Contributions/91.49.240.46|91.49.240.46]] 17:32, 13 February 2026 (UTC)
----
a few thoughs on your questions:
3: I quess that the most important factors are their DEFAULT_SITE_TYPE and their values. 4: same. See: [[https://www.bay12forums.com/smf/index.php?topic=110027.msg8610297#msg8610297]]. 5: Because there are no markets in the dark fortress. 6: I think that the entity MOUNTAINS (dwarves) always uses the raw-forced administrator. I think that what you have seen, are probably not entity type 1, but maybe like outcasts or villains or whatever. 9: I can see what i can do [[User:Joostheger|Joostheger]] ([[User talk:Joostheger|talk]]) 21:10, 17 February 2026 (UTC)

----
Well the dwarves are (probably) supposed to only use the forced
administrator as defined in the raws, but they are not.

In one case the site ruled by the forced administrator was originally
a human site, which was then taken over by a (dwarven) necromancer.
Afterwards a dwarven civ defeated the necromancer forces and formed a new government with a forced administrator (with precedence 100).
And the government still rules at the end of world gen.

The other was originally a dwarven site (hillock).
It was then taken over by a necromancer (again dwarven).
The dwarves (original owners) then took the site back and put
a forced administrator in place (again with precedence 100). But the
site did change its owner again afterwards.

To 3.: The goblins can take over other sites, so that is unlikely the cause. And would also not explain why the goblins with a custom bandit leader do create some officials, but the forced admin does not. (It is a totally different question, why the normal goblin site leaders do not create any officials.)

To 4.: Well for one thing the ethics (and not the values) might play a role (ie. most things being a "personal matter"). For some other things (chef, grain official) it is probably either that the goblins do neither drink nor eat or it is (indirectly) because of that as they might not have some labors/jobs (see [[https://dwarffortressbugtracker.com/view.php?id=11727]]). The later is probably also the reason, why they do not have doctors. The values on the other hand will probably play a role, whether the custom law maker is a diplomat (or has the military strategy responsibility).

To 5.: Again the goblins can take over other sites, so unless they always destroy the markets, when they occupy such a site, this cannot be the reason. But needs to be something else.

To. 9: The question is, whether the definitions allows multiple variable_position tags (resp. site variable position tags) or if only one is evaluated (and used). Furthermore the question is, whether only ALL and the name of a responsibility (like MANAGE_WORK_ORDERS) is allowed or if the name of the custom officials (as used as code) is also valid. And then a follow-up question would be, if ie. MILITARY_STRATEGY is written as entry, whether this will always create the CUSTOM_MILITARY_STRATEGY. And what about the cases, when an official has usually two responsibilities (like the "chef"), will that official be created with only one resp., if only one is given. Do both responsibilities need to be written (ie. with a comma as separator) in one tag. But that are all modding related questions (and not questions for modifying an existing world).

BTW: In many cases, when I looked into the history, a forced administrator was created usually after a site had been taken over by a necromancer (some time before). But I have not figured out yet, how I can easily check (from the entity definition), which group belongs to a necromancer and which not.[[Special:Contributions/91.49.240.46|91.49.240.46]] 16:44, 18 February 2026 (UTC)

== Variable Positions and Quests ==

Quiet a few variable positions do have the same flags set as ie. the CUSTOM_BANDIT_LEADER (who is according to the Quest page) able to give out quests to adventurers, allthough some of the variable positions do not have any squads (which again according to the Quest page is necessary to be able to give out quests), but then again the question is, whether that information on the Quest page (which seems to have been more or less only been migrated from an older version to the current v5x version) is current (or has even been correct for the older version). It is probably a good idea if someone tests out in the adventure mode, if ie. the guild leader (dean/doyen), merchant corporation leader (and representative) and other variable positions (who are mentioned on this page to have the quest_giver and/or kill_quest flag set) are able to give out quests to adventurers and then ie. update the Quest page with the results.[[Special:Contributions/91.49.240.46|91.49.240.46]] 14:05, 7 March 2026 (UTC)

== Holding multiple variable positions in world-gen. ==

Well while checking something else, I did come across a human necromancer, who currently holds 4 (variable) position assignments (and which are not former position assignments). The first three positions belong to an OUTCAST group, where the human holds the CUSTOM_OUTCAST_LT position (first assignment still active) and then two different CUSTOM_OUTCAST_FACTOR (assignments). The last position is the CUSTOM_LAW_MAKER (law-giver) of a human civilization (gained afterwards). The information is via dfhack and legends of a world directly after finishing world-gen (for the dfhack info a new game was started in the world and either before selecting the type of the game dfhack was used for analyzing the current game data or after selecting legends mode and analyzing the current game data with dfhack in addition to using the legends). In how far the necromancer is fullfilling all assignments is - of course - a totally different matter. An indepth analysis, how seldom/rare it is and which entities and position assignments are possible, will be done at a later date (possibly end of this month).[[Special:Contributions/91.49.243.26|91.49.243.26]] 11:52, 14 March 2026 (UT
----
Hello nameless one, love your work so far! Very impressive.
About CUSTOM_OUTCAST_LT being only a single one, there is another possible reason discussed in the forums. Search for 'army' and 'lieutentant'. It is, that there is (almost) never a reason to create more than one army commander, despite the civ being able to do so.
[[User:Joostheger|Joostheger]] ([[User talk:Joostheger|talk]]) 13:23, 15 March 2026 (UTC)
----
The squad size of the CUSTOM_OUTCAST_LT is zero (unless you do doubt the table entry), ie. in contrast to the usual army commanders. So the reason for no more than one CUSTOM_OUTCAST_LT has nothing to do, with being an army commander. To see for yourself, just ie. set the number for the OUTPOST_LIASION to AS_NEEDED and look whether you will get an OUTPOST_LIASION created (ie. the problem has not really anything to do with being an army commander or not, but with the AS_NEEDED or unlimited number, without the game knowing what condition to check, whether to create an (or another) assignment for the position, at least if the position is not tied to a number of locations/sites or the position being a landholder, which is again tied to the number of sites of a certain kind). And the reason for one CUSTOM_OUTCAST_LT getting created, instead of zero is already in the note.[[Special:Contributions/91.49.243.26|91.49.243.26]] 12:28, 16 March 2026 (UTC)

Addition: The only discussion I could find in the bay12 forums are from 2021 and thus concern v47 and not the current version. Besides considering that in my current game one human civ attacks itself nearly each year, shortly after their caravan returns home, in some cases with the attacker only a yak bull or yak cow (otherwise usually a single human), I do not think that any previous info about creation of army commanders is relevant, as yak bulls (and yak cows) are doing just fine as army commanders (of their one-yak-army). Or to put it in other words army commanders are currently created on the fly (otherwise in a world I did analyze there would be no way that a necromancer, with a tower, even if the necromancer would draft all position holders and itself as an army commander, could attack 20-30 different sites all at the start of a season of the same year; this btw. happened at least twice in the span of the 250 years of history in world-gen allthough with different necromancers).
ps. If you are wondering the yak bulls/cows and the humans are previous traders, who visited my fortress.[[Special:Contributions/91.49.243.26|91.49.243.26]] 17:02, 16 March 2026 (UTC)

Talk:Variable positions

2026-03-16T12:29:20Z

91.49.243.26: /* Holding multiple variable positions in world-gen. */

Variable positions

2026-03-15T11:41:53Z

91.49.243.26: /* Bandits */ Note about CUSTOM_OUTCAST_LT

{{Quality|Fine}}
{{Modding}}
{{stub}}
This page documents the variable positions that entities create when neccesary. This is - in vanilla - the case for [[human]] and [[goblin]] [[Civilization|civilizations]], but also for merchants' companies, guilds, mercenary groups, [[Religion|religious groups]] and [[Criminal|criminal]]s.

= Introduction =
Initially none of the positions marked as variable do exist for an entity. The positions will only exist for a given entity, if they are either created during world-gen, world activities(?) or by memory hacking or scripting (ie. with Lua). Ie. in vanilla all human civilizations have at the beginning of the world-generation no positions at all, neither on the site nor civ level, as all positions of the vanilla human civs are marked as variable (variable positions: all). When a variable (civ level) position is created, the position is only created for that civilization (entity) and not for any other entities of the same type. Ie. the creation of a law-giver for one human civ does not create law-givers for other human civs.

Also presumably all site-level positions for each entity are created on a per site basis, meaning the creation of a site ruler for one site (of a civ) does not also create the site ruler positions for any other site (of that civ).

The existence of a variable position does not mean that the position will also be filled by a historical figure. But during world-gen the creation of a position will usually be followed up with the position being filled. Ie. the human historical figure who forced the creation of a law-giver position, will usually become the first law-giver.

For the succession rules of a variable position (after the position has been initially filled by a historical figure), presumably, the same rules as for non-variable positions apply.

(Disclaimer: The following only applies during world-gen and normal world activities. Scripting and memory hacking can circumvent the normal limitations, but with currently unknown results).

For civ level entities, if the law-giving position is a variable position, the law-giving position does not (seem to) have any further requirements to be created (ie. no other position being already created). Ie. this position can be created by force (or popular support etc.) by any historical figure of that civ. But for all other variable (civ-level) positions the law-giving position must exist as usually the historical figure, who is the law-giver, does create the other variable positions (for various reason).

Something similar is probably the case for site level positions. Ie. if the ruler of a site is a variable position, that position needs to be created, before any other site-level variable positions can be created. And the site ruler can afterwards create other variable positions for that site. It is not yet clear if a site level ruling position can be created before a civ level ruling (law-giving) position is created (or exists). This also means that it should be possible, via memory-hacking or scripting, to create (and fill) the variable site level positions (for a player site), at least after the civ level law-giving position has been created (and the law-giving position has been filled), so that a human player site gets the maximum possible human site level positions (with the normal appointment rules for the succession/reappointment of the positions), without having to edit the raw files (as outlined in the human civ page), prior to creating a world, to make the variable positions of human civilisations to "static" ones.

Presumably for guilds (Merchant Guild and others), mercenary groups, religious orders (and criminals) also a "leader" position needs to be created by a historical figure, before other variable positions for that entity can be created.

== General Info ==
So far, no restrictions on allowed_class or allowed_creature have been found and also the rejected_creature and rejected_class entries are always empty. Squad_size is 0, except when a variable position (in the following sections) explictly states otherwise (ie. squad size for CUSTOM_BANDIT_LEADER, CUSTOM_LAW_MAKER and CUSTOM_LAW_MAKER_2 is 20). Also most other entries (of entity_position entry under "own") not mentioned in their section have standard values (ie. are empty). The best_appointment_precedence of all positions is 30001. Also the execution skill is always set to "-1" even for the CUSTOM_OFFICIAL_9, whose sole responsiblity is executions.

Also variable positions are usually only created (with the exception, if they replace another position), if the position will have at least one responsibility the already created (existing) positions for that entity does not have, regardless of whether there are any more prerequisites for a variable position to be created.

== Sources to process ==
See spoiler-sections of those posts.
* https://www.bay12forums.com/smf/index.php?topic=178697.msg8295235#msg8295235
* https://www.bay12forums.com/smf/index.php?topic=175434.msg8084095#msg8084095
* https://www.bay12forums.com/smf/index.php?topic=175434.msg8083631#msg8083631 (first answer)

= Civilizations =
If all positions of a civ are variable, then the CUSTOM_LAW_MAKER position needs to be created (in world-gen), before other positions (of the possible positions) can be created. After the creation (and filling) of the law-maker positions, the other variable positions (both CUSTOM_OFFICIALS_i and CUSTOM_MARKET_OFFICIALS_i, where i stands for a non-zero natural number) can be created in any order. These other positions are then always appointed by the law-maker of the civ. The law-maker position itself uses succession by heir.

In contrast to e.g the positions of the dwarven civilizations, where the site nobility positions (eg. baron, duke) do get added to the own position list (vector) of the civilization, the CUSTOM_LAW_MAKER (and CUSTOM_LAW_MAKER_2) positions (of a site government) are not added to the own position list (at least for civs with all variable positions). The "own" positions list (of the civ entity) only exclusively contains the variable positions of the civ, which are all created by the civ, and no positions which are the "ruler" of a site (even if the variable site position was appointed by the law maker of the civ). Also the "site" positions list is empty (or at least no entries were found so far).

The CUSTOM_LAW_MAKER position for goblins civs (in vanilla) are automatically created with the creation of the entity and there is no historical event which mentions the creation of that position. For the CUSTOM_LAW_MAKER positions of the human civs there is always a historical event which mentions the creation of that position, where the creation reason "As a matter of fact" is not possible, all other reasons, which are "Collaboration", "Threats of Violence", "Force of Argument" and "Wave of popular support", are possible (and seem equally likely to be used).

The following table gives an overview over the different possible rulers of a human or goblin civilization.

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name!!succession type!!Responsibilities!!Demands!!Mandates!!Precedence!!is diplomat!!human!!goblin

|-
!CUSTOM_LAW_MAKER
|master
|none
|law making, military goals, military strategy
|3
|2
|1
|no
|no
|yes

|-
!CUSTOM_LAW_MAKER
|master
|none
|law making, military goals,
|3
|2
|1
|yes
|no
|yes

|-
!CUSTOM_LAW_MAKER
|law-giver
|by heir
|law making, make peace agreements, military goals, military strategy
|3
|2
|1
|no
|yes
|no

|-
!CUSTOM_LAW_MAKER
|law-giver
|by heir
|law making, make peace agreements, military goals
|3
|2
|1
|yes
|yes
|no

|}

Note that the ruler (law-giver or master) is not a diplomat, if and only if the ruler has the military strategy responsibility. Otherwise it seems totally random, whether a ruler (law-giver) is a diplomat or not (ie. for human civilizations the position creation reason and the civilization values do not play any role at all). Also note that the master of a goblin civilization does not have peace agreements as a responsibility.

The creation of all non-ruling positions, ie. CUSTOM_OFFICIALs, of a civ are mentioned in the history, where all CUSTOM_OFFICIALs and CUSTOM_MARKET_OFFICIALs will always be created "as a matter of course", only the CUSTOM_MILITARY_GOALS and CUSTOM_MILITARY_STRATEGY positions can be created by any reason (including "as a matter of course").

The following table gives an overview of the possible non-ruling civ-level positions:

{| class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name prefix!!Name5!!Responsibilities!!Demands!!Mandates!!Precedence!!Number!!Flags11!!Flags22!!Color!!human!!goblin

|-
!CUSTOM_OFFICIAL_1
|yes3
|"keeper of the seal" / chancellor
|receive diplomats, make introductions and make topic agreements; optional: espionage
|3
|2
|20
|1
|yes
|no
|(5,0,1)
|yes
|yes

|-
!CUSTOM_OFFICIAL_2
|yes3
|justiciar
|law enforcement, collect taxes
|3
|2
|60
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_OFFICIAL_3
|yes
|treasurer
|trade, accounting
|2
|1
|70
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_OFFICIAL_4
|yes
|advisor/counselor
|advise leaders
|2
|1
|55
|1
|yes
|no
|(5,0,1)
|yes
|yes

|-
!CUSTOM_OFFICIAL_5
|yes3
|chamberlain
|oversee leader household
|1
|0
|80
|1
|yes
|no
|(5,0,1)
|yes
|yes

|-
!CUSTOM_OFFICIAL_6
|no
|master of beasts
|tame exotics, manage animals
|1
|0
|90
|1
|yes
|no
|(5,0,1)
|yes
|yes

|-
!CUSTOM_OFFICIAL_7
|yes
|butler / cup-bearer
|manage leader household food and drinks
|0
|0
|300
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_OFFICIAL_8
|yes
|doctor
|health management
|0
|0
|310
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_OFFICIAL_9
|yes
|executioner
|executions
|0
|0
|320
|1
|yes
|no
|(5,0,1)
|yes
|yes

|-
!CUSTOM_OFFICIAL_10
|yes
|chef
|prepare leader meals
|0
|0
|330
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_OFFICIAL_11
|yes
|housekeeper
|manage leader household cleanliness
|0
|0
|340
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_MILITARY_STRATEGY
|no
|general/(field) marshal / constable
|military strategy
|3
|2
|50
|1
|yes
|yes
|(5,0,1)
|yes
|yes

|-
!CUSTOM_MILITARY_GOALS4
|no
|war leader
|military goals, optional: military strategy
|3
|2
|45
|1
|yes
|yes
|(5,0,1)
|no
|no
|}
: ''Note'':
:* 1) These are the standard official flags: duty_bound, has_responsibilities, do_not_cull, has_met_pop_req, color, menial_work_exemption, has_received_positions and has_met_market_req.
:* 2) These are the following additional flags: flashes, brag_on_kill, chat_worthy, kill_quest, account_exempt, punishment_exemption, quest_giver and special_burial.
:* 3): Name prefix can be empty.
:* 4) These would be the values for the CUSTOM_MILITARY_GOALS position, but on the civ-level that position is not created, as the military goals responsibility is already performed by the law-giver/master (and for the military strategy responsibility the CUSTOM_MILITARY_STRATEGY position is created instead). But a CUSTOM_MILITARY_GOALS position would be created, if the civ leader would not have the military goals responsibility. The CUSTOM_MILITARY_GOALS position is - in vanilla - only created for site governments and then only, if the site leader is the FORCED_ADMINISTRATOR.
:* 5): Name prefixes are: high, head, chief and royal.

In the above table the responsibility "espionage" of the CUSTOM_OFFICIAL_1 is optional. A civ needs to have a "cunning" value of at least 11 for the CUSTOM_OFFICIAL_1 to have the responsibility, otherwise the official will not have the espionage responsibility, consequentially all CUSTOM_OFFICIAL_1 of goblin civs will have the espionage responsibility (as their default cunning value is 15). Only if the CUSTOM_OFFICIAL_1 is created with the "espionage" responsibility such officials can also be created for the site governments, where the leader of the site-government is not called "law-giver", (as all other responsibility are already performed by the standard custom site ruler). Also, the columns "human" and "goblin" dictate whether human and/or goblin civilizations can have the positions.

= Site Governments =
If all positions of a civ (and with that of a site government) are variable, then a leader position for the site government needs to be created (in world-gen), before other positions (of the possible variable positions) can be created. The created position is usually the CUSTOM_LAW_MAKER, but other positions have been found, ie. CUSTOM_BANDIT_LEADER and FORCED_ADMINISTRATOR.

Note that if a site is taken over during a war, then a new leader can be created directly with the formation of a new site government (even if the all site positions of the new owning civ are variable and the old site government did not have any leaders), in such cases the new leader position is either a FORCED_ADMINISTRATOR or - rarer - a CUSTOM_LAW_MAKER (only found, if the site taken over was a Town and both the defending and attacking civilization was human).

Note that human and goblin civilizations can also create further site positions, if the current site leader is the CUSTOM_BANDIT_LEADER (both) or FORCED_ADMINISTRATOR (only encountered/found in case of humans). All other races (eg. dwarves and elves) cannot.

Also a CUSTOM_LAW_MAKER can be created for a site government (of a human civilization) before a CUSTOM_LAW_MAKER for the civilization has been created.

Also note that not all site government entities need to be a child of a civilization entity, if they are not, then the CUSTOM_BANDIT_LEADER is used as a site-ruler (regardless of race, ie. even dwarven and the rare elven site government without connection to a civ will use the CUSTOM_BANDIT_LEADER as initial ruler/leader). Ie. a Necromancer founding a tower will generate a site government (or site entity), which does not have any parent entity, and does function as a civ entity for any of its child entities (and will use the CUSTOM_BANDIT_LEADER as ruler). But such Necromancer entities are not the only site entities without a parent civ (which can have positions), ie. some (all?) groups construction forts (and where the creation of the entity coincidies with the construction of the fort) will also not have a parent civ (and use the entity type site).

The following table gives an overview of the possible leader positions:

{| class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name!!Responsibilities!!squad8 size!!Demands!!Mandates!!Precedence!!goblin!!human!!elf!!dwarf!!flags!!appointment type

|-
!CUSTOM_BANDIT_LEADER1
|Boss, Captain, Chief, Chieftain, Commander, Leader, Master, Overlord, Ringleader or Warlord
|law making, law enforcement, receive diplomats, make introductions, make topic agreements, military strategy, military goals
|20
|2
|1
|55 or 10 (rare)
|yes
|yes
|yes
|yes
|standard bandit leader
|elected

|-
!FORCED_ADMINISTRATOR
|administrator
|law making, receive diplomats, meet workers, make topic agreements
|0
|3
|2
|100
|yes
|yes
|yes
|yes2
|forced admin
|none3

|-
!FORCED_ADMINISTRATOR4
|administrator
|law making, receive diplomats, meet workers, make topic agreements
|0
|3
|2
|65
|no
|no
|no
|yes
|dwarf forced admin
|none3

|-
!CUSTOM_LAW_MAKER5
|law-giver
|law making, make peace agreements, military goals; optional6: military strategy
|0
|3
|2
|1
|no
|yes
|no
|no
|civ law-giver
|by heir

|-
!CUSTOM_LAW_MAKER6
|lord
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|20
|3
|2
|1
|no
|yes
|no
|no
|standard leader
|by heir

|-
!CUSTOM_LAW_MAKER
|lord
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|20
|3
|2
|40
|yes
|yes
|no
|no
|standard leader
|by heir

|-
!CUSTOM_LAW_MAKER
|baron
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|20
|3
|2
|41
|no
|yes
|no
|no
|standard leader
|by heir; appointed by law-giver (civ)

|-
!CUSTOM_LAW_MAKER_27
|baron
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|20
|3
|2
|35
|no
|yes
|no
|no
|standard leader
|by heir; optional: appointed9

|}

: ''Notes'':
:* 1): Only leader position, if the entity (site-government) is not a child of a civilization, but can also appear, if the entity has a parent civ. Only site leader position of goblins, where other site positions will be created (both cases: with civ and without civ).
:* 2): 2 of the 53 forced administrator positions of dwarves (in a large 250 year histor world-gen world with many civs) used this forced administrator (rather than the one defined in the raws). No site official positions found for goblins so far, if the leader was a forced administrator.
:* 3): The position has no appointed_by defined, nor any form of succession by position or heir. And the position is also not elected. So how and if a forced admin gets refilled, in case of death of the previous position holder, is unclear.
:* 4): This is the forced administrator as defined in the (vanilla) dwarf raws.
:* 5): Was created once in a large 250 year history world-gen world with many civs. The parent civ did not have a law-maker position created. But this definition is not always used, if the law-maker position of the parent civ has not been created. Also the site-entity was the original owner/creator of the site.
:* 6): This position can get created for a newly formed site-entity, if a site-entity has created the law-maker position and afterwards the site-entity gets conquered by another entity (of the same civ) and at the time of conquest no law-giver was created (yet) for the civ.
:* 7: Can be created (and replaces the former site ruler), if the ruler (of a human site entity) was either a FORCED_ADMINISTRATOR or a CUSTOM_LAW_MAKER with the name "lord".
:* 8): If the squad size is greater than zero, then the squad members are called soldiers (CUSTOM_BANDIT_LEADER) or hearthpeople (otherwise).
:* 9): Always appointed by the law-giver of the civilization, if the previous site leader was a forced administrator. Otherwise the appointed_by (and appointed_by_civ) definition is either empty or set to the law-giver of the civ, eg. a CUSTOM_LAW_MAKER_2, which replaces a CUSTOM_LAW_MAKER, can be appointed (in which case appointed by the law-giver of the civ) or not be appointed at all.
:* "by heir" in the appointment type definition entry means, that the succession is by heir. If nothing else is mentioned in the table cell, then the position did get filled immediatly upon creation of the position and the first position holder was not appointed by the civ-leader, otherwise the first position holder was appointed by the civ-leader.
:* "standard bandit leader" entry in "flags" table cell means the same flags as the CUSTOM_BANDIT_LEADER of bandit groups are set.
:* "forced admin" entry in "flags" table cell: is_law_maker, duty_bound, has_responsibitities, flashes, brag_on_kill, chat_worthy, do_not_cull, kill_quest, is_leader, is_diplomat, exported_in_legends, determines_coin_design, account_exempt, color, rules_from_location, menial_work_exemption, sleep_pretesion, punishment_exemption, has_received_positions, quest_giver, special_burial.
:* "dwarf forced admin" entry in "flags" table cell: is_law_maker, duty_bound, has_responsibitities, flashes, brag_on_kill, chat_worthy, do_not_cull, kill_quest, is_leader, is_diplomat, exported_in_legends, determines_coin_design, account_exempt, color, menial_work_exemption, sleep_pretesion, punishment_exemption, has_received_positions, special_burial.
:* "standard leader" entry in "flags" table cell: is_law_maker, duty_bound, has_responsibilities, flashes, brag_on_kill, chat_worthy, do_not_cull, kill_quest, is_leader, exported_in_legends, determines_coin_design, account_exempt, color, rules_from_location, menial_work_exemption, punishment_exemption, has_received_positions, quest_giver, special_burial.
:* "civ law-giver" entry in "flags" table cell means that the flags of the CUSTOM_LAW_MAKER (civ level) are set, where the is_diplomat flag is only set, if (and only if) the law-giver does not have the military strategy responsibility. Also in this case the is_diplomat flag is only set, if the "law-giver" (of the site entity) does not have the military strategy responsibility.
:* Remark to forced administrator: The only differences between the forced administrator (only usable by the dwarves and defined in the raws) and the other forced administrator are, that the forced administrator of the dwarves is not a quest giver, does not rule from a location and has a different precedence.
:* The color of all leaders is the standard noble color (5,0,1), except for the forced administrators, who uses a different color entry (5,0,0).

If a leader does exist for a site entity, other variable positions can be created for that entity. In rare cases a variable official (or market official) position can even be created, if the requirements are not met (at least one of the flags has_met_pop_req and has_met_market_req is false for the position entry).

The following table gives an overview of the non-ruler variable positions of a site government.

{| class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name prefix1!!Name!!Name suffix2!!Responsibilities!!Demands!!Mandates!!Precedence!!Number!!Color!!human!!goblin!!add. flags3

|-
!CUSTOM_MARKET_OFFICIAL_1
|no
|sewer
|always
|maintain sewers
|0
|0
|500
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MARKET_OFFICIAL_2
|no
|grain / harvest
|always
|food supply
|1
|0
|450
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MARKET_OFFICIAL_3
|no
|fire
|always
|fire safety
|0
|0
|475
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MARKET_OFFICIAL_4
|no
|judge / magistrate / justice
|no
|judge
|1
|0
|350
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MARKET_OFFICIAL_5
|no
|building
|always
|construction permits, building safety
|1
|0
|460
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MARKET_OFFICIAL_6
|no
|road
|always
|maintain roads, bridges and tunnels
|1
|0
|375
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_16,7,8
|optional
|"keeper of the seal" / chancellor
|no
|espionage
|3
|2
|20
|1
|(5,0,1)
|yes
|yes
|no

|-
!CUSTOM_OFFICIAL_27,9
|optional
|justiciar
|no
|collect taxes
|3
|2
|60
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_3
|always
|treasurer
|no
|trade, accounting
|2
|1
|70
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_4
|always
|advisor / counselor
|no
|advise leaders
|2
|1
|55
|1
|(5,0,1)
|yes
|yes
|no

|-
!CUSTOM_OFFICIAL_5
|optional
|chamberlain
|no
|oversee leader houshold
|1
|0
|80
|1
|(5,0,1)
|yes
|yes
|no

|-
!CUSTOM_OFFICIAL_6
|no
|master of beasts
|no
|tame exotics, manage animals
|1
|0
|90
|1
|(5,0,1)
|yes
|yes
|no

|-
!CUSTOM_OFFICIAL_7
|always
|butler / cup-bearer
|no
|manage leader houshold food and drinks
|0
|0
|300
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_8
|always
|doctor
|no
|health management
|0
|0
|310
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_9
|always
|executioner
|no
|executions
|0
|0
|320
|1
|(5,0,1)
|yes
|yes
|no

|-
!CUSTOM_OFFICIAL_10
|always
|chef
|no
|prepare leader meals
|0
|0
|330
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_11
|always
|housekeeper
|no
|manage leader houshold cleanliness
|0
|0
|340
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MILITARY_STRATEGY4
|no
|general/(field) marshal / constable
|no
|military strategy
|3
|2
|50
|1
|(5,0,1)
|yes
|no
|yes

|-
!CUSTOM_MILITARY_GOALS5
|no
|war leader
|no
|military goals, optional: military strategy
|3
|2
|45
|1
|(5,0,1)
|yes
|no
|yes

|}

: ''Notes'':
:* 1): The possible name prefixes are "chief", "head" and "high" (always) and also "royal", if the site leader has the name "law-giver". The name prefix can be empty, if the cell entry is "optional". A name prefix will always be present, if the cell entry is "always".
:* 2): The possible name suffixes are "administrator", "caretaker", "commissioner", "master" and "official". A name suffix will always be present, if the cell entry is "always".
:* 3): The additional flags are: flashes, brag_on_kill, chat_worthy, kill_quest, account_exempt, punishment_exemption, quest_giver and special_burial.
:* 4): Only ever created, if the first site leader was a FORCED_ADMINISTRATOR. Can even be created, if the FORCED_ADMINISTRATOR has already been replaced by a CUSTOM_LAW_MAKER_2.
:* 5): Only created, either after the CUSTOM_MILITARY_GOALS position was created and the CUSTOM_MILITARY_GOALS position was not created with the military strategy responsibility or if the leader has the name law-giver (and does not have the military strategy responsibility). Can even be created, if the first site leader was a FORCED_ADMINISTRATOR, who has already been replaced by a CUSTOM_LAW_MAKER_2.
:* 6): If the leader name is not law-giver (and the first site leader was not a FORCED_ADMINISTRATOR), then a CUSTOM_OFFICIAL_1 has the espionage responsibilty. All CUSTOM_OFFICIAL_1 of a civ (regardless of whether the CUSTOM_OFFICIAL_1 belongs to a site government or the civ government) will either have the espionage responsibility or do not have the espionage responsibility.
:* 7): If the leader has the name law-giver then this official position has the responsibilities (and also optional resp.) as given in the civ table for the official position and not the responsibilities as in this table. Ie. that is the only case where a CUSTOM_OFFICIAL_1 can be created for a site government without the espionage responsibility.
:* 8): The CUSTOM_OFFICIAL_1 has always the responsibility make introductions, if the first site leader/ruler was a FORCED_ADMINISTRATOR, even if the FORCED_ADMINISTRATOR has already been replaced (by a CUSTOM_LAW_MAKER_2).
:* 9): The CUSTOM_OFFICIAL_2 has always the responsibility law enforcement, if the first site leader/ruler was a FORCED_ADMINISTRATOR, even if the FORCED_ADMINISTRATOR has already been replaced (by a CUSTOM_LAW_MAKER_2).
:* In the above table the columns "human" and "goblin" donate, whether a site government of a human civilization or of a goblin civilization can have that position (or at least, if the position was encountered so far). Note so far only goblin site governments with a CUSTOM_BANDIT_LEADER did have further positions created.
:* All CUSTOM_MARKET_OFFICIALs created during world-gen seem to have an already constructed market present (and thus are not created for site governments ruling over a Hamlet or a Dark Pit as Hamlets and Dark Pits cannot have a market, but need to be a Town or Dark Fortress). Additionally the CUSTOM_MARKET_OFFICIAL_1 needs an already constructed sewer (which seems to be only created, after both a market and a keep are constructed). Also note that sewers are only constructed in towns (in contrast to ie. markets, which can also be found/constructed in other site types like Dark Fortresses, Fortresses, Hillocks, Caves and Forest Retreats).
:* In addtion to the above table the "best_appointment_precedence" is 30001. Also the following flags are set (true) for all officials, regardless, of whether belonging to a human or goblin site government: duty_bound, has_responsibilities, do_not_cull, color, menial_work_exemption and has_received_positions.
:* All of the positions are appointed by the current ruler of the site (ie. CUSTOM_LAW_MAKER, CUSTOM_BANDIT_LEADER, FORCED_ADMINISTRATOR), except the CUSTOM_MILITARY_STRATEGY position will be appointed by the CUSTOM_MILITARY_GOALS position, if the CUSTOM_MILITARY_GOALS position was created prior and the current ruler of the site government is a forced administrator.

Additionally the position entry usually has the flag active set and the flag is_replaced is false, otherwise the position would no longer be active (and might have been replaced).

= Bandits =
Bandits use the entity types 4 and 7, which are nomadic groups (type 4) and outcasts (type 7). It must also be noted that some CUSTOM_BANDIT_LEADER positions are used by site governments (typically goblin site governments) both with and without a parent civilization (site government is not a child of an entity of type 0). The creation of CUSTOM_BANDIT_LEADER and CUSTOM_OUTCAST_FACTOR positions is never mentioned as a historical event, but the creation of CUSTOM_OUTCAST_LT is (and is always created "as a matter of course").

The following table gives an overview over the possible variable positions used by bandits (some further info on bandit leaders is below the table).

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name!!appointment type!!Responsibilities!!squad size!!Demands!!Mandates!!Precedence!!Number!!add. flags1!!rules from location!!entity type

|-
!CUSTOM_BANDIT_LEADER
|Boss, Captain, Chief, Chieftain, Commander, Leader, Master, Overlord, Ringleader or Warlord
|elected
|law making, law enforcement, receive diplomats, make introduction, make peace agreements, make topic agreements, military strategy and military goals
|20
|2
|1
|55
|1
|yes
|no
|nomadic, outcast

|-
!CUSTOM_BANDIT_LEADER2
|Boss, Captain, Chief, Chieftain, Commander, Leader, Master, Overlord, Ringleader or Warlord
|elected
|law making, law enforcement, receive diplomats, make introduction, make peace agreements, make topic agreements, military strategy and military goals
|20
|2
|1
|10
|1
|yes
|no
|nomadic

|-
!CUSTOM_OUTCAST_LT3
|lieutenant
|appointed by bandit leader
|patrol territory, attack enemies
|0
|1
|0
|160
| -1
|no
|no
|outcast

|-
!CUSTOM_OUTCAST_FACTOR
|representative
|appointed by bandit leader
|trade and accounting
|0
|1
|0
|70
| -1
|yes (except is_law_maker)
|yes
|outcast

|}
: ''Notes'':
:* 1): Additional flags are: is_law_maker, flashes, brag_on_kill, chat_worthy, kill_quest, account_exempt and quest_giver
:* 2): Only difference to the other CUSTOM_BANDIT_LEADER is the increased precedence of 10, encountered in 11 of 148 bandit leaders (148 of 175 nomadic groups had leaders). The reason is of yet unknown, except that the CUSTOM_BANDIT_LEADER is also used by the goblin civilization (and some site governments, without an entity link to a parent civ, had a nomadic group with a custom bandit leader as a child entity).
:* 3: Currently only up-to one CUSTOM_OUTCAST_LT will be created for Outcast groups, despite allowing for an unlimited number. The possible reason for one getting created at all is that an assignment definition is automatically created with the creation of the position itself (while ie. for Ranger Captain, Milita Captain etc. there is currently never an assignment created, as they are neither land-holders nor is their number tied to a location or site).
:* Further note the common flags of these positions are: duty_bound, has_responsibilities, do_not_cull, is_leader, has_met_pop_req, menial_work_exemption, has_received_positions and has_met_market_req.
:* The entity type in the above table refers to the (as displayed by dfhack's gm-editor, when viewing an entity).

Additionally the bandit leader (CUSTOM_BANDIT_LEADER) always has a squad size of 20 and the squad members are refered to as "bandits".

= Religious Entities =
Some religious entities, which are considered "child"-entities of civilizations (no religious entity which was not a "child" of a civ entity has been found so far), also have variable positions - the other religious entities have no positions at all.
If a religious entity rules a site (always monastery?), then the only variable position (of that entity) seems to be the CUSTOM_LAW_MAKER and the name of the position seems to be always "abbot".
Otherwise the variable positions PRIEST, HIGH_PRIEST and HIGHEST_PRIEST can be created for that religious entity, where any such entity, if it has a position, will always have the PRIEST as position. Afterwards, the position HIGH_PRIEST can be created and at last - after the HIGH_PRIEST was created - the HIGHEST_PRIEST can be created. The names of these position are randomly created (more about the name generation is currently out-of-scope, ie. why a PRIEST might be called "sacred squid", "holy burial", "sacred rumor", "holy lemon" or "sacred paper" is out-of-scope at least for this wiki article). No temple is needed in an associated site for a religious entity (not ruling from a monastery) to create a priest, high priest or highest priest position.

Note that there is no historical event that mentions the creation of a PRIEST, HIGH_PRIEST or HIGHEST_PRIEST position.

An overview on the positions of religious entities is given in the following table:

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!name prefix!!name!!appointment type5!!Responsibilities!!Precedence!!Demands!!Mandates!!number!!missing common flags1!!additional flags2

|-
!CUSTOM_LAW_MAKER3
|
|abbot
|heir
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|100
|3
|2
|1
|is_diplomat
|all

|-
!PRIEST
|holy or sacred
|random4
|elected
|religion
|200
|0
|0
| -1
|none
|no

|-
!HIGH_PRIEST
|high, first or exalted
|random4
|elected
|law_making, receive diplomats and make topic agreements
|50
|3
|2
| -1
|none
|all (except determines_coin_design)

|-
!HIGHEST_PRIEST
|absolute or most sacred/high/exalted
|random4
|elected
|law_making, receive diplomats and make topic agreements
|1
|5
|3
|1
|none
|all (except determines_coin_design)

|}

Notes:
1): The common flags are: duty_bound, has_responsibilities, chat_worthy, do_not_cull, is_leader, is_diplomat, has_met_pop_req, rules_from_location, menial_work_exemption, punishment_exemption, has_received_positions and has_met_market_req. So if one of the flags is mentioned in a column, then the position does not have that flag.

2): The additional flags (in this case) are: is_law_maker, flashes, brag_on_kill, kill_quest, exported_in_legends, account_exempt, quest_giver, special_burial.

3): Is always the only position for that religious entity. And so far any such entity, which was found, always governed/ruled a monastery.

4): The name is one of the possible "name prefixes" for the position written before a completely random word, which may or may not depend on the religious spheres/domains worshipped by that religion.

5): The appointment/succession type is actually determined by flags, ie. elected and succession_by_heir. One of the flags is also true for these positions (but not explicitly mentioned in the common/additional flags).

Additional notes: The PRIEST, HIGH_PRIEST and HIGHEST_PRIEST have a variable color entry, but the color-flag (of the position entry) is false, so it is unclear whether currently the color entry has any effect.

= Mercenary Group =

All mercenary entities will have at least one position (the CUSTOM_MERCENARY_LEADER), this position is created with the creation of the group (and the creation of the entity is marked - in the history/legends - with the filling of the leader position). The only other possible position is the CUSTOM_MERCENARY_TREASURER and the creation of the CUSTOM_MERCENTARY_TREASURER is mentioned as a historical event (and is always created "as a matter of course").

Basic information about both positions are found in the table below (and the explanations below the table).

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name!!appointment type!!Responsibilities!!Precedence!!Demands!!Mandates!!number!! imp. flags1

|-
!CUSTOM_MERCENARY_LEADER
|usually "warlord", "leader", "general" or "overlord" but very unusual names are possible (see below table)
|elected
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|50
|2
|1
|1
|yes

|-
!CUSTOM_MERCENARY_TREASURER
|treasurer
|elected
|trade and accounting
|160
|1
|0
|1
|no

|}

Notes: 1): The imp. flags are flashes, brag_on_kill, chat_worthy, punishment_exemption, kill_quest and quest giver.

Both positions also have the is_leader flag and the following flags: duty_bound, has_responsibilities, has_met_pop_req, menial_work_exemption, has_received_positions and has_met_market_req.

For the mercenary leader also illustrous names such as lord twinkle, lord duty, lord savant, maze commander or secret commander can be created. In these cases the name seems to be generated by either adding a random word after the word lord or adding a random word before commander. Note that mercenary groups can bestow honors on either their members or their leaders and in case of leader only honors it might be that, instead of the leader name, the name of the currently highest bestowed honor (on the leader) is used.

= Guilds =
All guilds will always have all four of the variable positions mentioned in this section. Note that "merchant guilds" are merchant companies and an entirely separate entity.

The following table gives an overview of the four guild positions.

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name!!appointment type!!Responsibilities!!precedence!!demands!!mandates!!number!!add. flags1

|-
!CUSTOM_GUILD_LEADER
|dean/doyen
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|elected
|50
|2
|1
|1
|yes

|-
!CUSTOM_GUILD_ALDERPERSON
|alderperson
|meet workers, manage production
|elected
|150
|1
|0
|1
|no

|-
!CUSTOM_GUILD_STEWARD
|steward or treasurer
|trade
|elected
|160
|1
|0
|1
|no

|-
!CUSTOM_GUILD_CLERK
|clerk, bookkeeper, recordkeeper
|accounting
|elected
|170
|1
|0
|1
|no

|}

Notes:
1): The additional flags are: is_law_maker, flashes, brag_on_kill; chat_worthy, do_not_cull, kill_quest, account_exempt, rules_from_location, punishment_exemption and quest_giver.

All positions have the following flags in common:
duty_bound, has_responsibilities, do_not_cull, is_leader, has_met_pop_req, menial_work_exemption, has_received_positions, has_met_market_positions.

= Merchant Company =
Every merchant company will have a leader (CUSTOM_COMPANY_LEADER). Furthermore a merchant company can have a CUSTOM_COMPANY_FACTOR, to which an unlimited number of history figures can be assigned to (ie. a company can have multiple governors, but the number of current governors is always the same as the number of counting houses - branches - in non-headquarters sites). Also note that there is no history event, which mentions the creation of a position for a merchant company, still the CUSTOM_COMPANY_FACTOR position is only created with creation of the first branch of a company (and branch creation - purchase of a counting house or building of a new counting house - and filling of custom company factor position are always at exactly the same time according to the corresponding historical events).

An overview of both positions is given by the following table:

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!name!!appointment type!!Responsibilities!!Precedence!!Demands!!Mandates!!number!!additional flag

|-
!CUSTOM_COMPANY_LEADER
|master or head
|elected or succession by heir
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military goals, military strategy
|50
|2
|1
|1
|is_law_maker

|-
!CUSTOM_COMPANY_FACTOR
|agent, factor, administrator or governor
|appointed by company leader
|trade and accounting
|200
|1
|0
| -1
|none

|}

Both positions have the following flags in common:
duty_bound, has_responsibilities, flashes, brag_on_kill, chat_worthy, do_not_cull, kill_quest, is_leader, account_exempt, has_met_pop_req, rules_from_location, menial_work_exemption, punishment_exemption, has_received_positions, quest_giver and has_met_market_req.

Also note that in contrast to many other variable positions (of different entities) for the CUSTOM_COMPANY_LEADER both an election based appointment (or succession) and an succesion by heir is possible, but each merchant company will only have an elected leader or a leader (with inheritance).

= Raw tokens =
The tokens that manage the creation of positions are [[Entity_token#SITE_VARIABLE_POSITIONS|SITE_VARIABLE_POSITIONS]] and [[Entity_token#VARIABLE_POSITIONS|VARIABLE_POSITIONS]].

SITE_VARIABLE_POSITIONS allows for the creation of lords, hearthpersons, and [[boss]]es, and [VARIABLE_POSITIONS] allows creation of Law-makers.

Talk:Variable positions

2026-03-14T11:52:36Z

91.49.243.26: /* Holding multiple variable positions in world-gen. */ new section

Variable positions

2026-03-14T11:38:59Z

91.49.243.26: /* Site Governments */

{{Quality|Fine}}
{{Modding}}
{{stub}}
This page documents the variable positions that entities create when neccesary. This is - in vanilla - the case for [[human]] and [[goblin]] [[Civilization|civilizations]], but also for merchants' companies, guilds, mercenary groups, [[Religion|religious groups]] and [[Criminal|criminal]]s.

= Introduction =
Initially none of the positions marked as variable do exist for an entity. The positions will only exist for a given entity, if they are either created during world-gen, world activities(?) or by memory hacking or scripting (ie. with Lua). Ie. in vanilla all human civilizations have at the beginning of the world-generation no positions at all, neither on the site nor civ level, as all positions of the vanilla human civs are marked as variable (variable positions: all). When a variable (civ level) position is created, the position is only created for that civilization (entity) and not for any other entities of the same type. Ie. the creation of a law-giver for one human civ does not create law-givers for other human civs.

Also presumably all site-level positions for each entity are created on a per site basis, meaning the creation of a site ruler for one site (of a civ) does not also create the site ruler positions for any other site (of that civ).

The existence of a variable position does not mean that the position will also be filled by a historical figure. But during world-gen the creation of a position will usually be followed up with the position being filled. Ie. the human historical figure who forced the creation of a law-giver position, will usually become the first law-giver.

For the succession rules of a variable position (after the position has been initially filled by a historical figure), presumably, the same rules as for non-variable positions apply.

(Disclaimer: The following only applies during world-gen and normal world activities. Scripting and memory hacking can circumvent the normal limitations, but with currently unknown results).

For civ level entities, if the law-giving position is a variable position, the law-giving position does not (seem to) have any further requirements to be created (ie. no other position being already created). Ie. this position can be created by force (or popular support etc.) by any historical figure of that civ. But for all other variable (civ-level) positions the law-giving position must exist as usually the historical figure, who is the law-giver, does create the other variable positions (for various reason).

Something similar is probably the case for site level positions. Ie. if the ruler of a site is a variable position, that position needs to be created, before any other site-level variable positions can be created. And the site ruler can afterwards create other variable positions for that site. It is not yet clear if a site level ruling position can be created before a civ level ruling (law-giving) position is created (or exists). This also means that it should be possible, via memory-hacking or scripting, to create (and fill) the variable site level positions (for a player site), at least after the civ level law-giving position has been created (and the law-giving position has been filled), so that a human player site gets the maximum possible human site level positions (with the normal appointment rules for the succession/reappointment of the positions), without having to edit the raw files (as outlined in the human civ page), prior to creating a world, to make the variable positions of human civilisations to "static" ones.

Presumably for guilds (Merchant Guild and others), mercenary groups, religious orders (and criminals) also a "leader" position needs to be created by a historical figure, before other variable positions for that entity can be created.

== General Info ==
So far, no restrictions on allowed_class or allowed_creature have been found and also the rejected_creature and rejected_class entries are always empty. Squad_size is 0, except when a variable position (in the following sections) explictly states otherwise (ie. squad size for CUSTOM_BANDIT_LEADER, CUSTOM_LAW_MAKER and CUSTOM_LAW_MAKER_2 is 20). Also most other entries (of entity_position entry under "own") not mentioned in their section have standard values (ie. are empty). The best_appointment_precedence of all positions is 30001. Also the execution skill is always set to "-1" even for the CUSTOM_OFFICIAL_9, whose sole responsiblity is executions.

Also variable positions are usually only created (with the exception, if they replace another position), if the position will have at least one responsibility the already created (existing) positions for that entity does not have, regardless of whether there are any more prerequisites for a variable position to be created.

== Sources to process ==
See spoiler-sections of those posts.
* https://www.bay12forums.com/smf/index.php?topic=178697.msg8295235#msg8295235
* https://www.bay12forums.com/smf/index.php?topic=175434.msg8084095#msg8084095
* https://www.bay12forums.com/smf/index.php?topic=175434.msg8083631#msg8083631 (first answer)

= Civilizations =
If all positions of a civ are variable, then the CUSTOM_LAW_MAKER position needs to be created (in world-gen), before other positions (of the possible positions) can be created. After the creation (and filling) of the law-maker positions, the other variable positions (both CUSTOM_OFFICIALS_i and CUSTOM_MARKET_OFFICIALS_i, where i stands for a non-zero natural number) can be created in any order. These other positions are then always appointed by the law-maker of the civ. The law-maker position itself uses succession by heir.

In contrast to e.g the positions of the dwarven civilizations, where the site nobility positions (eg. baron, duke) do get added to the own position list (vector) of the civilization, the CUSTOM_LAW_MAKER (and CUSTOM_LAW_MAKER_2) positions (of a site government) are not added to the own position list (at least for civs with all variable positions). The "own" positions list (of the civ entity) only exclusively contains the variable positions of the civ, which are all created by the civ, and no positions which are the "ruler" of a site (even if the variable site position was appointed by the law maker of the civ). Also the "site" positions list is empty (or at least no entries were found so far).

The CUSTOM_LAW_MAKER position for goblins civs (in vanilla) are automatically created with the creation of the entity and there is no historical event which mentions the creation of that position. For the CUSTOM_LAW_MAKER positions of the human civs there is always a historical event which mentions the creation of that position, where the creation reason "As a matter of fact" is not possible, all other reasons, which are "Collaboration", "Threats of Violence", "Force of Argument" and "Wave of popular support", are possible (and seem equally likely to be used).

The following table gives an overview over the different possible rulers of a human or goblin civilization.

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name!!succession type!!Responsibilities!!Demands!!Mandates!!Precedence!!is diplomat!!human!!goblin

|-
!CUSTOM_LAW_MAKER
|master
|none
|law making, military goals, military strategy
|3
|2
|1
|no
|no
|yes

|-
!CUSTOM_LAW_MAKER
|master
|none
|law making, military goals,
|3
|2
|1
|yes
|no
|yes

|-
!CUSTOM_LAW_MAKER
|law-giver
|by heir
|law making, make peace agreements, military goals, military strategy
|3
|2
|1
|no
|yes
|no

|-
!CUSTOM_LAW_MAKER
|law-giver
|by heir
|law making, make peace agreements, military goals
|3
|2
|1
|yes
|yes
|no

|}

Note that the ruler (law-giver or master) is not a diplomat, if and only if the ruler has the military strategy responsibility. Otherwise it seems totally random, whether a ruler (law-giver) is a diplomat or not (ie. for human civilizations the position creation reason and the civilization values do not play any role at all). Also note that the master of a goblin civilization does not have peace agreements as a responsibility.

The creation of all non-ruling positions, ie. CUSTOM_OFFICIALs, of a civ are mentioned in the history, where all CUSTOM_OFFICIALs and CUSTOM_MARKET_OFFICIALs will always be created "as a matter of course", only the CUSTOM_MILITARY_GOALS and CUSTOM_MILITARY_STRATEGY positions can be created by any reason (including "as a matter of course").

The following table gives an overview of the possible non-ruling civ-level positions:

{| class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name prefix!!Name5!!Responsibilities!!Demands!!Mandates!!Precedence!!Number!!Flags11!!Flags22!!Color!!human!!goblin

|-
!CUSTOM_OFFICIAL_1
|yes3
|"keeper of the seal" / chancellor
|receive diplomats, make introductions and make topic agreements; optional: espionage
|3
|2
|20
|1
|yes
|no
|(5,0,1)
|yes
|yes

|-
!CUSTOM_OFFICIAL_2
|yes3
|justiciar
|law enforcement, collect taxes
|3
|2
|60
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_OFFICIAL_3
|yes
|treasurer
|trade, accounting
|2
|1
|70
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_OFFICIAL_4
|yes
|advisor/counselor
|advise leaders
|2
|1
|55
|1
|yes
|no
|(5,0,1)
|yes
|yes

|-
!CUSTOM_OFFICIAL_5
|yes3
|chamberlain
|oversee leader household
|1
|0
|80
|1
|yes
|no
|(5,0,1)
|yes
|yes

|-
!CUSTOM_OFFICIAL_6
|no
|master of beasts
|tame exotics, manage animals
|1
|0
|90
|1
|yes
|no
|(5,0,1)
|yes
|yes

|-
!CUSTOM_OFFICIAL_7
|yes
|butler / cup-bearer
|manage leader household food and drinks
|0
|0
|300
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_OFFICIAL_8
|yes
|doctor
|health management
|0
|0
|310
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_OFFICIAL_9
|yes
|executioner
|executions
|0
|0
|320
|1
|yes
|no
|(5,0,1)
|yes
|yes

|-
!CUSTOM_OFFICIAL_10
|yes
|chef
|prepare leader meals
|0
|0
|330
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_OFFICIAL_11
|yes
|housekeeper
|manage leader household cleanliness
|0
|0
|340
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_MILITARY_STRATEGY
|no
|general/(field) marshal / constable
|military strategy
|3
|2
|50
|1
|yes
|yes
|(5,0,1)
|yes
|yes

|-
!CUSTOM_MILITARY_GOALS4
|no
|war leader
|military goals, optional: military strategy
|3
|2
|45
|1
|yes
|yes
|(5,0,1)
|no
|no
|}
: ''Note'':
:* 1) These are the standard official flags: duty_bound, has_responsibilities, do_not_cull, has_met_pop_req, color, menial_work_exemption, has_received_positions and has_met_market_req.
:* 2) These are the following additional flags: flashes, brag_on_kill, chat_worthy, kill_quest, account_exempt, punishment_exemption, quest_giver and special_burial.
:* 3): Name prefix can be empty.
:* 4) These would be the values for the CUSTOM_MILITARY_GOALS position, but on the civ-level that position is not created, as the military goals responsibility is already performed by the law-giver/master (and for the military strategy responsibility the CUSTOM_MILITARY_STRATEGY position is created instead). But a CUSTOM_MILITARY_GOALS position would be created, if the civ leader would not have the military goals responsibility. The CUSTOM_MILITARY_GOALS position is - in vanilla - only created for site governments and then only, if the site leader is the FORCED_ADMINISTRATOR.
:* 5): Name prefixes are: high, head, chief and royal.

In the above table the responsibility "espionage" of the CUSTOM_OFFICIAL_1 is optional. A civ needs to have a "cunning" value of at least 11 for the CUSTOM_OFFICIAL_1 to have the responsibility, otherwise the official will not have the espionage responsibility, consequentially all CUSTOM_OFFICIAL_1 of goblin civs will have the espionage responsibility (as their default cunning value is 15). Only if the CUSTOM_OFFICIAL_1 is created with the "espionage" responsibility such officials can also be created for the site governments, where the leader of the site-government is not called "law-giver", (as all other responsibility are already performed by the standard custom site ruler). Also, the columns "human" and "goblin" dictate whether human and/or goblin civilizations can have the positions.

= Site Governments =
If all positions of a civ (and with that of a site government) are variable, then a leader position for the site government needs to be created (in world-gen), before other positions (of the possible variable positions) can be created. The created position is usually the CUSTOM_LAW_MAKER, but other positions have been found, ie. CUSTOM_BANDIT_LEADER and FORCED_ADMINISTRATOR.

Note that if a site is taken over during a war, then a new leader can be created directly with the formation of a new site government (even if the all site positions of the new owning civ are variable and the old site government did not have any leaders), in such cases the new leader position is either a FORCED_ADMINISTRATOR or - rarer - a CUSTOM_LAW_MAKER (only found, if the site taken over was a Town and both the defending and attacking civilization was human).

Note that human and goblin civilizations can also create further site positions, if the current site leader is the CUSTOM_BANDIT_LEADER (both) or FORCED_ADMINISTRATOR (only encountered/found in case of humans). All other races (eg. dwarves and elves) cannot.

Also a CUSTOM_LAW_MAKER can be created for a site government (of a human civilization) before a CUSTOM_LAW_MAKER for the civilization has been created.

Also note that not all site government entities need to be a child of a civilization entity, if they are not, then the CUSTOM_BANDIT_LEADER is used as a site-ruler (regardless of race, ie. even dwarven and the rare elven site government without connection to a civ will use the CUSTOM_BANDIT_LEADER as initial ruler/leader). Ie. a Necromancer founding a tower will generate a site government (or site entity), which does not have any parent entity, and does function as a civ entity for any of its child entities (and will use the CUSTOM_BANDIT_LEADER as ruler). But such Necromancer entities are not the only site entities without a parent civ (which can have positions), ie. some (all?) groups construction forts (and where the creation of the entity coincidies with the construction of the fort) will also not have a parent civ (and use the entity type site).

The following table gives an overview of the possible leader positions:

{| class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name!!Responsibilities!!squad8 size!!Demands!!Mandates!!Precedence!!goblin!!human!!elf!!dwarf!!flags!!appointment type

|-
!CUSTOM_BANDIT_LEADER1
|Boss, Captain, Chief, Chieftain, Commander, Leader, Master, Overlord, Ringleader or Warlord
|law making, law enforcement, receive diplomats, make introductions, make topic agreements, military strategy, military goals
|20
|2
|1
|55 or 10 (rare)
|yes
|yes
|yes
|yes
|standard bandit leader
|elected

|-
!FORCED_ADMINISTRATOR
|administrator
|law making, receive diplomats, meet workers, make topic agreements
|0
|3
|2
|100
|yes
|yes
|yes
|yes2
|forced admin
|none3

|-
!FORCED_ADMINISTRATOR4
|administrator
|law making, receive diplomats, meet workers, make topic agreements
|0
|3
|2
|65
|no
|no
|no
|yes
|dwarf forced admin
|none3

|-
!CUSTOM_LAW_MAKER5
|law-giver
|law making, make peace agreements, military goals; optional6: military strategy
|0
|3
|2
|1
|no
|yes
|no
|no
|civ law-giver
|by heir

|-
!CUSTOM_LAW_MAKER6
|lord
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|20
|3
|2
|1
|no
|yes
|no
|no
|standard leader
|by heir

|-
!CUSTOM_LAW_MAKER
|lord
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|20
|3
|2
|40
|yes
|yes
|no
|no
|standard leader
|by heir

|-
!CUSTOM_LAW_MAKER
|baron
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|20
|3
|2
|41
|no
|yes
|no
|no
|standard leader
|by heir; appointed by law-giver (civ)

|-
!CUSTOM_LAW_MAKER_27
|baron
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|20
|3
|2
|35
|no
|yes
|no
|no
|standard leader
|by heir; optional: appointed9

|}

: ''Notes'':
:* 1): Only leader position, if the entity (site-government) is not a child of a civilization, but can also appear, if the entity has a parent civ. Only site leader position of goblins, where other site positions will be created (both cases: with civ and without civ).
:* 2): 2 of the 53 forced administrator positions of dwarves (in a large 250 year histor world-gen world with many civs) used this forced administrator (rather than the one defined in the raws). No site official positions found for goblins so far, if the leader was a forced administrator.
:* 3): The position has no appointed_by defined, nor any form of succession by position or heir. And the position is also not elected. So how and if a forced admin gets refilled, in case of death of the previous position holder, is unclear.
:* 4): This is the forced administrator as defined in the (vanilla) dwarf raws.
:* 5): Was created once in a large 250 year history world-gen world with many civs. The parent civ did not have a law-maker position created. But this definition is not always used, if the law-maker position of the parent civ has not been created. Also the site-entity was the original owner/creator of the site.
:* 6): This position can get created for a newly formed site-entity, if a site-entity has created the law-maker position and afterwards the site-entity gets conquered by another entity (of the same civ) and at the time of conquest no law-giver was created (yet) for the civ.
:* 7: Can be created (and replaces the former site ruler), if the ruler (of a human site entity) was either a FORCED_ADMINISTRATOR or a CUSTOM_LAW_MAKER with the name "lord".
:* 8): If the squad size is greater than zero, then the squad members are called soldiers (CUSTOM_BANDIT_LEADER) or hearthpeople (otherwise).
:* 9): Always appointed by the law-giver of the civilization, if the previous site leader was a forced administrator. Otherwise the appointed_by (and appointed_by_civ) definition is either empty or set to the law-giver of the civ, eg. a CUSTOM_LAW_MAKER_2, which replaces a CUSTOM_LAW_MAKER, can be appointed (in which case appointed by the law-giver of the civ) or not be appointed at all.
:* "by heir" in the appointment type definition entry means, that the succession is by heir. If nothing else is mentioned in the table cell, then the position did get filled immediatly upon creation of the position and the first position holder was not appointed by the civ-leader, otherwise the first position holder was appointed by the civ-leader.
:* "standard bandit leader" entry in "flags" table cell means the same flags as the CUSTOM_BANDIT_LEADER of bandit groups are set.
:* "forced admin" entry in "flags" table cell: is_law_maker, duty_bound, has_responsibitities, flashes, brag_on_kill, chat_worthy, do_not_cull, kill_quest, is_leader, is_diplomat, exported_in_legends, determines_coin_design, account_exempt, color, rules_from_location, menial_work_exemption, sleep_pretesion, punishment_exemption, has_received_positions, quest_giver, special_burial.
:* "dwarf forced admin" entry in "flags" table cell: is_law_maker, duty_bound, has_responsibitities, flashes, brag_on_kill, chat_worthy, do_not_cull, kill_quest, is_leader, is_diplomat, exported_in_legends, determines_coin_design, account_exempt, color, menial_work_exemption, sleep_pretesion, punishment_exemption, has_received_positions, special_burial.
:* "standard leader" entry in "flags" table cell: is_law_maker, duty_bound, has_responsibilities, flashes, brag_on_kill, chat_worthy, do_not_cull, kill_quest, is_leader, exported_in_legends, determines_coin_design, account_exempt, color, rules_from_location, menial_work_exemption, punishment_exemption, has_received_positions, quest_giver, special_burial.
:* "civ law-giver" entry in "flags" table cell means that the flags of the CUSTOM_LAW_MAKER (civ level) are set, where the is_diplomat flag is only set, if (and only if) the law-giver does not have the military strategy responsibility. Also in this case the is_diplomat flag is only set, if the "law-giver" (of the site entity) does not have the military strategy responsibility.
:* Remark to forced administrator: The only differences between the forced administrator (only usable by the dwarves and defined in the raws) and the other forced administrator are, that the forced administrator of the dwarves is not a quest giver, does not rule from a location and has a different precedence.
:* The color of all leaders is the standard noble color (5,0,1), except for the forced administrators, who uses a different color entry (5,0,0).

If a leader does exist for a site entity, other variable positions can be created for that entity. In rare cases a variable official (or market official) position can even be created, if the requirements are not met (at least one of the flags has_met_pop_req and has_met_market_req is false for the position entry).

The following table gives an overview of the non-ruler variable positions of a site government.

{| class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name prefix1!!Name!!Name suffix2!!Responsibilities!!Demands!!Mandates!!Precedence!!Number!!Color!!human!!goblin!!add. flags3

|-
!CUSTOM_MARKET_OFFICIAL_1
|no
|sewer
|always
|maintain sewers
|0
|0
|500
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MARKET_OFFICIAL_2
|no
|grain / harvest
|always
|food supply
|1
|0
|450
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MARKET_OFFICIAL_3
|no
|fire
|always
|fire safety
|0
|0
|475
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MARKET_OFFICIAL_4
|no
|judge / magistrate / justice
|no
|judge
|1
|0
|350
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MARKET_OFFICIAL_5
|no
|building
|always
|construction permits, building safety
|1
|0
|460
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MARKET_OFFICIAL_6
|no
|road
|always
|maintain roads, bridges and tunnels
|1
|0
|375
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_16,7,8
|optional
|"keeper of the seal" / chancellor
|no
|espionage
|3
|2
|20
|1
|(5,0,1)
|yes
|yes
|no

|-
!CUSTOM_OFFICIAL_27,9
|optional
|justiciar
|no
|collect taxes
|3
|2
|60
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_3
|always
|treasurer
|no
|trade, accounting
|2
|1
|70
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_4
|always
|advisor / counselor
|no
|advise leaders
|2
|1
|55
|1
|(5,0,1)
|yes
|yes
|no

|-
!CUSTOM_OFFICIAL_5
|optional
|chamberlain
|no
|oversee leader houshold
|1
|0
|80
|1
|(5,0,1)
|yes
|yes
|no

|-
!CUSTOM_OFFICIAL_6
|no
|master of beasts
|no
|tame exotics, manage animals
|1
|0
|90
|1
|(5,0,1)
|yes
|yes
|no

|-
!CUSTOM_OFFICIAL_7
|always
|butler / cup-bearer
|no
|manage leader houshold food and drinks
|0
|0
|300
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_8
|always
|doctor
|no
|health management
|0
|0
|310
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_9
|always
|executioner
|no
|executions
|0
|0
|320
|1
|(5,0,1)
|yes
|yes
|no

|-
!CUSTOM_OFFICIAL_10
|always
|chef
|no
|prepare leader meals
|0
|0
|330
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_11
|always
|housekeeper
|no
|manage leader houshold cleanliness
|0
|0
|340
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MILITARY_STRATEGY4
|no
|general/(field) marshal / constable
|no
|military strategy
|3
|2
|50
|1
|(5,0,1)
|yes
|no
|yes

|-
!CUSTOM_MILITARY_GOALS5
|no
|war leader
|no
|military goals, optional: military strategy
|3
|2
|45
|1
|(5,0,1)
|yes
|no
|yes

|}

: ''Notes'':
:* 1): The possible name prefixes are "chief", "head" and "high" (always) and also "royal", if the site leader has the name "law-giver". The name prefix can be empty, if the cell entry is "optional". A name prefix will always be present, if the cell entry is "always".
:* 2): The possible name suffixes are "administrator", "caretaker", "commissioner", "master" and "official". A name suffix will always be present, if the cell entry is "always".
:* 3): The additional flags are: flashes, brag_on_kill, chat_worthy, kill_quest, account_exempt, punishment_exemption, quest_giver and special_burial.
:* 4): Only ever created, if the first site leader was a FORCED_ADMINISTRATOR. Can even be created, if the FORCED_ADMINISTRATOR has already been replaced by a CUSTOM_LAW_MAKER_2.
:* 5): Only created, either after the CUSTOM_MILITARY_GOALS position was created and the CUSTOM_MILITARY_GOALS position was not created with the military strategy responsibility or if the leader has the name law-giver (and does not have the military strategy responsibility). Can even be created, if the first site leader was a FORCED_ADMINISTRATOR, who has already been replaced by a CUSTOM_LAW_MAKER_2.
:* 6): If the leader name is not law-giver (and the first site leader was not a FORCED_ADMINISTRATOR), then a CUSTOM_OFFICIAL_1 has the espionage responsibilty. All CUSTOM_OFFICIAL_1 of a civ (regardless of whether the CUSTOM_OFFICIAL_1 belongs to a site government or the civ government) will either have the espionage responsibility or do not have the espionage responsibility.
:* 7): If the leader has the name law-giver then this official position has the responsibilities (and also optional resp.) as given in the civ table for the official position and not the responsibilities as in this table. Ie. that is the only case where a CUSTOM_OFFICIAL_1 can be created for a site government without the espionage responsibility.
:* 8): The CUSTOM_OFFICIAL_1 has always the responsibility make introductions, if the first site leader/ruler was a FORCED_ADMINISTRATOR, even if the FORCED_ADMINISTRATOR has already been replaced (by a CUSTOM_LAW_MAKER_2).
:* 9): The CUSTOM_OFFICIAL_2 has always the responsibility law enforcement, if the first site leader/ruler was a FORCED_ADMINISTRATOR, even if the FORCED_ADMINISTRATOR has already been replaced (by a CUSTOM_LAW_MAKER_2).
:* In the above table the columns "human" and "goblin" donate, whether a site government of a human civilization or of a goblin civilization can have that position (or at least, if the position was encountered so far). Note so far only goblin site governments with a CUSTOM_BANDIT_LEADER did have further positions created.
:* All CUSTOM_MARKET_OFFICIALs created during world-gen seem to have an already constructed market present (and thus are not created for site governments ruling over a Hamlet or a Dark Pit as Hamlets and Dark Pits cannot have a market, but need to be a Town or Dark Fortress). Additionally the CUSTOM_MARKET_OFFICIAL_1 needs an already constructed sewer (which seems to be only created, after both a market and a keep are constructed). Also note that sewers are only constructed in towns (in contrast to ie. markets, which can also be found/constructed in other site types like Dark Fortresses, Fortresses, Hillocks, Caves and Forest Retreats).
:* In addtion to the above table the "best_appointment_precedence" is 30001. Also the following flags are set (true) for all officials, regardless, of whether belonging to a human or goblin site government: duty_bound, has_responsibilities, do_not_cull, color, menial_work_exemption and has_received_positions.
:* All of the positions are appointed by the current ruler of the site (ie. CUSTOM_LAW_MAKER, CUSTOM_BANDIT_LEADER, FORCED_ADMINISTRATOR), except the CUSTOM_MILITARY_STRATEGY position will be appointed by the CUSTOM_MILITARY_GOALS position, if the CUSTOM_MILITARY_GOALS position was created prior and the current ruler of the site government is a forced administrator.

Additionally the position entry usually has the flag active set and the flag is_replaced is false, otherwise the position would no longer be active (and might have been replaced).

= Bandits =
Bandits use the entity types 4 and 7, which are nomadic groups (type 4) and outcasts (type 7). It must also be noted that some CUSTOM_BANDIT_LEADER positions are used by site governments (typically goblin site governments) both with and without a parent civilization (site government is not a child of an entity of type 0). The creation of CUSTOM_BANDIT_LEADER and CUSTOM_OUTCAST_FACTOR positions is never mentioned as a historical event, but the creation of CUSTOM_OUTCAST_LT is (and is always created "as a matter of course").

The following table gives an overview over the possible variable positions used by bandits (some further info on bandit leaders is below the table).

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name!!appointment type!!Responsibilities!!squad size!!Demands!!Mandates!!Precedence!!Number!!add. flags1!!rules from location!!entity type

|-
!CUSTOM_BANDIT_LEADER
|Boss, Captain, Chief, Chieftain, Commander, Leader, Master, Overlord, Ringleader or Warlord
|elected
|law making, law enforcement, receive diplomats, make introduction, make peace agreements, make topic agreements, military strategy and military goals
|20
|2
|1
|55
|1
|yes
|no
|nomadic, outcast

|-
!CUSTOM_BANDIT_LEADER2
|Boss, Captain, Chief, Chieftain, Commander, Leader, Master, Overlord, Ringleader or Warlord
|elected
|law making, law enforcement, receive diplomats, make introduction, make peace agreements, make topic agreements, military strategy and military goals
|20
|2
|1
|10
|1
|yes
|no
|nomadic

|-
!CUSTOM_OUTCAST_LT
|lieutenant
|appointed by bandit leader
|patrol territory, attack enemies
|0
|1
|0
|160
| -1
|no
|no
|outcast

|-
!CUSTOM_OUTCAST_FACTOR
|representative
|appointed by bandit leader
|trade and accounting
|0
|1
|0
|70
| -1
|yes (except is_law_maker)
|yes
|outcast

|}
: ''Notes'':
:* 1): Additional flags are: is_law_maker, flashes, brag_on_kill, chat_worthy, kill_quest, account_exempt and quest_giver
:* 2): Only difference to the other CUSTOM_BANDIT_LEADER is the increased precedence of 10, encountered in 11 of 148 bandit leaders (148 of 175 nomadic groups had leaders). The reason is of yet unknown, except that the CUSTOM_BANDIT_LEADER is also used by the goblin civilization (and some site governments, without an entity link to a parent civ, had a nomadic group with a custom bandit leader as a child entity).
:* Further note the common flags of these positions are: duty_bound, has_responsibilities, do_not_cull, is_leader, has_met_pop_req, menial_work_exemption, has_received_positions and has_met_market_req.
:* The entity type in the above table refers to the (as displayed by dfhack's gm-editor, when viewing an entity).

Additionally the bandit leader (CUSTOM_BANDIT_LEADER) always has a squad size of 20 and the squad members are refered to as "bandits".

= Religious Entities =
Some religious entities, which are considered "child"-entities of civilizations (no religious entity which was not a "child" of a civ entity has been found so far), also have variable positions - the other religious entities have no positions at all.
If a religious entity rules a site (always monastery?), then the only variable position (of that entity) seems to be the CUSTOM_LAW_MAKER and the name of the position seems to be always "abbot".
Otherwise the variable positions PRIEST, HIGH_PRIEST and HIGHEST_PRIEST can be created for that religious entity, where any such entity, if it has a position, will always have the PRIEST as position. Afterwards, the position HIGH_PRIEST can be created and at last - after the HIGH_PRIEST was created - the HIGHEST_PRIEST can be created. The names of these position are randomly created (more about the name generation is currently out-of-scope, ie. why a PRIEST might be called "sacred squid", "holy burial", "sacred rumor", "holy lemon" or "sacred paper" is out-of-scope at least for this wiki article). No temple is needed in an associated site for a religious entity (not ruling from a monastery) to create a priest, high priest or highest priest position.

Note that there is no historical event that mentions the creation of a PRIEST, HIGH_PRIEST or HIGHEST_PRIEST position.

An overview on the positions of religious entities is given in the following table:

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!name prefix!!name!!appointment type5!!Responsibilities!!Precedence!!Demands!!Mandates!!number!!missing common flags1!!additional flags2

|-
!CUSTOM_LAW_MAKER3
|
|abbot
|heir
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|100
|3
|2
|1
|is_diplomat
|all

|-
!PRIEST
|holy or sacred
|random4
|elected
|religion
|200
|0
|0
| -1
|none
|no

|-
!HIGH_PRIEST
|high, first or exalted
|random4
|elected
|law_making, receive diplomats and make topic agreements
|50
|3
|2
| -1
|none
|all (except determines_coin_design)

|-
!HIGHEST_PRIEST
|absolute or most sacred/high/exalted
|random4
|elected
|law_making, receive diplomats and make topic agreements
|1
|5
|3
|1
|none
|all (except determines_coin_design)

|}

Notes:
1): The common flags are: duty_bound, has_responsibilities, chat_worthy, do_not_cull, is_leader, is_diplomat, has_met_pop_req, rules_from_location, menial_work_exemption, punishment_exemption, has_received_positions and has_met_market_req. So if one of the flags is mentioned in a column, then the position does not have that flag.

2): The additional flags (in this case) are: is_law_maker, flashes, brag_on_kill, kill_quest, exported_in_legends, account_exempt, quest_giver, special_burial.

3): Is always the only position for that religious entity. And so far any such entity, which was found, always governed/ruled a monastery.

4): The name is one of the possible "name prefixes" for the position written before a completely random word, which may or may not depend on the religious spheres/domains worshipped by that religion.

5): The appointment/succession type is actually determined by flags, ie. elected and succession_by_heir. One of the flags is also true for these positions (but not explicitly mentioned in the common/additional flags).

Additional notes: The PRIEST, HIGH_PRIEST and HIGHEST_PRIEST have a variable color entry, but the color-flag (of the position entry) is false, so it is unclear whether currently the color entry has any effect.

= Mercenary Group =

All mercenary entities will have at least one position (the CUSTOM_MERCENARY_LEADER), this position is created with the creation of the group (and the creation of the entity is marked - in the history/legends - with the filling of the leader position). The only other possible position is the CUSTOM_MERCENARY_TREASURER and the creation of the CUSTOM_MERCENTARY_TREASURER is mentioned as a historical event (and is always created "as a matter of course").

Basic information about both positions are found in the table below (and the explanations below the table).

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name!!appointment type!!Responsibilities!!Precedence!!Demands!!Mandates!!number!! imp. flags1

|-
!CUSTOM_MERCENARY_LEADER
|usually "warlord", "leader", "general" or "overlord" but very unusual names are possible (see below table)
|elected
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|50
|2
|1
|1
|yes

|-
!CUSTOM_MERCENARY_TREASURER
|treasurer
|elected
|trade and accounting
|160
|1
|0
|1
|no

|}

Notes: 1): The imp. flags are flashes, brag_on_kill, chat_worthy, punishment_exemption, kill_quest and quest giver.

Both positions also have the is_leader flag and the following flags: duty_bound, has_responsibilities, has_met_pop_req, menial_work_exemption, has_received_positions and has_met_market_req.

For the mercenary leader also illustrous names such as lord twinkle, lord duty, lord savant, maze commander or secret commander can be created. In these cases the name seems to be generated by either adding a random word after the word lord or adding a random word before commander. Note that mercenary groups can bestow honors on either their members or their leaders and in case of leader only honors it might be that, instead of the leader name, the name of the currently highest bestowed honor (on the leader) is used.

= Guilds =
All guilds will always have all four of the variable positions mentioned in this section. Note that "merchant guilds" are merchant companies and an entirely separate entity.

The following table gives an overview of the four guild positions.

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name!!appointment type!!Responsibilities!!precedence!!demands!!mandates!!number!!add. flags1

|-
!CUSTOM_GUILD_LEADER
|dean/doyen
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|elected
|50
|2
|1
|1
|yes

|-
!CUSTOM_GUILD_ALDERPERSON
|alderperson
|meet workers, manage production
|elected
|150
|1
|0
|1
|no

|-
!CUSTOM_GUILD_STEWARD
|steward or treasurer
|trade
|elected
|160
|1
|0
|1
|no

|-
!CUSTOM_GUILD_CLERK
|clerk, bookkeeper, recordkeeper
|accounting
|elected
|170
|1
|0
|1
|no

|}

Notes:
1): The additional flags are: is_law_maker, flashes, brag_on_kill; chat_worthy, do_not_cull, kill_quest, account_exempt, rules_from_location, punishment_exemption and quest_giver.

All positions have the following flags in common:
duty_bound, has_responsibilities, do_not_cull, is_leader, has_met_pop_req, menial_work_exemption, has_received_positions, has_met_market_positions.

= Merchant Company =
Every merchant company will have a leader (CUSTOM_COMPANY_LEADER). Furthermore a merchant company can have a CUSTOM_COMPANY_FACTOR, to which an unlimited number of history figures can be assigned to (ie. a company can have multiple governors, but the number of current governors is always the same as the number of counting houses - branches - in non-headquarters sites). Also note that there is no history event, which mentions the creation of a position for a merchant company, still the CUSTOM_COMPANY_FACTOR position is only created with creation of the first branch of a company (and branch creation - purchase of a counting house or building of a new counting house - and filling of custom company factor position are always at exactly the same time according to the corresponding historical events).

An overview of both positions is given by the following table:

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!name!!appointment type!!Responsibilities!!Precedence!!Demands!!Mandates!!number!!additional flag

|-
!CUSTOM_COMPANY_LEADER
|master or head
|elected or succession by heir
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military goals, military strategy
|50
|2
|1
|1
|is_law_maker

|-
!CUSTOM_COMPANY_FACTOR
|agent, factor, administrator or governor
|appointed by company leader
|trade and accounting
|200
|1
|0
| -1
|none

|}

Both positions have the following flags in common:
duty_bound, has_responsibilities, flashes, brag_on_kill, chat_worthy, do_not_cull, kill_quest, is_leader, account_exempt, has_met_pop_req, rules_from_location, menial_work_exemption, punishment_exemption, has_received_positions, quest_giver and has_met_market_req.

Also note that in contrast to many other variable positions (of different entities) for the CUSTOM_COMPANY_LEADER both an election based appointment (or succession) and an succesion by heir is possible, but each merchant company will only have an elected leader or a leader (with inheritance).

= Raw tokens =
The tokens that manage the creation of positions are [[Entity_token#SITE_VARIABLE_POSITIONS|SITE_VARIABLE_POSITIONS]] and [[Entity_token#VARIABLE_POSITIONS|VARIABLE_POSITIONS]].

SITE_VARIABLE_POSITIONS allows for the creation of lords, hearthpersons, and [[boss]]es, and [VARIABLE_POSITIONS] allows creation of Law-makers.

Talk:Support

2026-03-12T16:51:18Z

91.49.243.26: /* Required Labor(s)? */

Trying out my tactical support with a wall on top linked to a lever. I built two supports with a stair (IuI) between in DF 50 off of steam. I just can't get these dwarfs to build supports in V50. Is it working? [[User:Dominick|Dominick]] [[User_talk:dominick|(TALK)]] 03:28, 24 December 2022 (UTC)

== Required Labor(s)? ==
Running vanilla DF, Premium edition (53.11), and was confirming which Labors are needed to be active now to build which Supports. It seems... none???!!! I designated 4 supports - 1 each stone, wood, metal bar, and glass - and turned off ALL labors on ALL dwarfs via the game (not using Dwarf Therapist atm, nor is it even connected) - and all 4 supports were still constructed. No experience was gained (fisherdwarf still had only "fishing", no other skill). When Mason was turned on, 2 xp were gained when that dwarf was able to get the job. Seems like a bug. Could someone confirm/refute this, pls, thx. [[user:Albedo]] [[User_talk:Albedo|(TALK)]] ''aka'' [[Special:Contributions/108.85.197.99|108.85.197.99]] 16:26, 12 March 2026 (UTC)

By default not all "Labors" are assigned to a work detail. And if I recall correctly, I do have a work detail for floor/wall constructions, so there is a labor for it. Furthermore what was the setting of your dwarves concerning "Specializing" (would they do all labors or only the ones they were assigned via occupation/work detail)? The thing about Mason getting exp for Construction also depends on the materials used for construction (if I recall correctly, for ie. a wood construction or wooden Trade Depot the Mason is not supposed to get exp)...[[Special:Contributions/91.49.243.26|91.49.243.26]] 16:50, 12 March 2026 (UTC)

Variable positions

2026-03-12T14:22:42Z

91.49.243.26: /* Site Governments */

{{Quality|Fine}}
{{Modding}}
{{stub}}
This page documents the variable positions that entities create when neccesary. This is - in vanilla - the case for [[human]] and [[goblin]] [[Civilization|civilizations]], but also for merchants' companies, guilds, mercenary groups, [[Religion|religious groups]] and [[Criminal|criminal]]s.

= Introduction =
Initially none of the positions marked as variable do exist for an entity. The positions will only exist for a given entity, if they are either created during world-gen, world activities(?) or by memory hacking or scripting (ie. with Lua). Ie. in vanilla all human civilizations have at the beginning of the world-generation no positions at all, neither on the site nor civ level, as all positions of the vanilla human civs are marked as variable (variable positions: all). When a variable (civ level) position is created, the position is only created for that civilization (entity) and not for any other entities of the same type. Ie. the creation of a law-giver for one human civ does not create law-givers for other human civs.

Also presumably all site-level positions for each entity are created on a per site basis, meaning the creation of a site ruler for one site (of a civ) does not also create the site ruler positions for any other site (of that civ).

The existence of a variable position does not mean that the position will also be filled by a historical figure. But during world-gen the creation of a position will usually be followed up with the position being filled. Ie. the human historical figure who forced the creation of a law-giver position, will usually become the first law-giver.

For the succession rules of a variable position (after the position has been initially filled by a historical figure), presumably, the same rules as for non-variable positions apply.

(Disclaimer: The following only applies during world-gen and normal world activities. Scripting and memory hacking can circumvent the normal limitations, but with currently unknown results).

For civ level entities, if the law-giving position is a variable position, the law-giving position does not (seem to) have any further requirements to be created (ie. no other position being already created). Ie. this position can be created by force (or popular support etc.) by any historical figure of that civ. But for all other variable (civ-level) positions the law-giving position must exist as usually the historical figure, who is the law-giver, does create the other variable positions (for various reason).

Something similar is probably the case for site level positions. Ie. if the ruler of a site is a variable position, that position needs to be created, before any other site-level variable positions can be created. And the site ruler can afterwards create other variable positions for that site. It is not yet clear if a site level ruling position can be created before a civ level ruling (law-giving) position is created (or exists). This also means that it should be possible, via memory-hacking or scripting, to create (and fill) the variable site level positions (for a player site), at least after the civ level law-giving position has been created (and the law-giving position has been filled), so that a human player site gets the maximum possible human site level positions (with the normal appointment rules for the succession/reappointment of the positions), without having to edit the raw files (as outlined in the human civ page), prior to creating a world, to make the variable positions of human civilisations to "static" ones.

Presumably for guilds (Merchant Guild and others), mercenary groups, religious orders (and criminals) also a "leader" position needs to be created by a historical figure, before other variable positions for that entity can be created.

== General Info ==
So far, no restrictions on allowed_class or allowed_creature have been found and also the rejected_creature and rejected_class entries are always empty. Squad_size is 0, except when a variable position (in the following sections) explictly states otherwise (ie. squad size for CUSTOM_BANDIT_LEADER, CUSTOM_LAW_MAKER and CUSTOM_LAW_MAKER_2 is 20). Also most other entries (of entity_position entry under "own") not mentioned in their section have standard values (ie. are empty). The best_appointment_precedence of all positions is 30001. Also the execution skill is always set to "-1" even for the CUSTOM_OFFICIAL_9, whose sole responsiblity is executions.

Also variable positions are usually only created (with the exception, if they replace another position), if the position will have at least one responsibility the already created (existing) positions for that entity does not have, regardless of whether there are any more prerequisites for a variable position to be created.

== Sources to process ==
See spoiler-sections of those posts.
* https://www.bay12forums.com/smf/index.php?topic=178697.msg8295235#msg8295235
* https://www.bay12forums.com/smf/index.php?topic=175434.msg8084095#msg8084095
* https://www.bay12forums.com/smf/index.php?topic=175434.msg8083631#msg8083631 (first answer)

= Civilizations =
If all positions of a civ are variable, then the CUSTOM_LAW_MAKER position needs to be created (in world-gen), before other positions (of the possible positions) can be created. After the creation (and filling) of the law-maker positions, the other variable positions (both CUSTOM_OFFICIALS_i and CUSTOM_MARKET_OFFICIALS_i, where i stands for a non-zero natural number) can be created in any order. These other positions are then always appointed by the law-maker of the civ. The law-maker position itself uses succession by heir.

In contrast to e.g the positions of the dwarven civilizations, where the site nobility positions (eg. baron, duke) do get added to the own position list (vector) of the civilization, the CUSTOM_LAW_MAKER (and CUSTOM_LAW_MAKER_2) positions (of a site government) are not added to the own position list (at least for civs with all variable positions). The "own" positions list (of the civ entity) only exclusively contains the variable positions of the civ, which are all created by the civ, and no positions which are the "ruler" of a site (even if the variable site position was appointed by the law maker of the civ). Also the "site" positions list is empty (or at least no entries were found so far).

The CUSTOM_LAW_MAKER position for goblins civs (in vanilla) are automatically created with the creation of the entity and there is no historical event which mentions the creation of that position. For the CUSTOM_LAW_MAKER positions of the human civs there is always a historical event which mentions the creation of that position, where the creation reason "As a matter of fact" is not possible, all other reasons, which are "Collaboration", "Threats of Violence", "Force of Argument" and "Wave of popular support", are possible (and seem equally likely to be used).

The following table gives an overview over the different possible rulers of a human or goblin civilization.

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name!!succession type!!Responsibilities!!Demands!!Mandates!!Precedence!!is diplomat!!human!!goblin

|-
!CUSTOM_LAW_MAKER
|master
|none
|law making, military goals, military strategy
|3
|2
|1
|no
|no
|yes

|-
!CUSTOM_LAW_MAKER
|master
|none
|law making, military goals,
|3
|2
|1
|yes
|no
|yes

|-
!CUSTOM_LAW_MAKER
|law-giver
|by heir
|law making, make peace agreements, military goals, military strategy
|3
|2
|1
|no
|yes
|no

|-
!CUSTOM_LAW_MAKER
|law-giver
|by heir
|law making, make peace agreements, military goals
|3
|2
|1
|yes
|yes
|no

|}

Note that the ruler (law-giver or master) is not a diplomat, if and only if the ruler has the military strategy responsibility. Otherwise it seems totally random, whether a ruler (law-giver) is a diplomat or not (ie. for human civilizations the position creation reason and the civilization values do not play any role at all). Also note that the master of a goblin civilization does not have peace agreements as a responsibility.

The creation of all non-ruling positions, ie. CUSTOM_OFFICIALs, of a civ are mentioned in the history, where all CUSTOM_OFFICIALs and CUSTOM_MARKET_OFFICIALs will always be created "as a matter of course", only the CUSTOM_MILITARY_GOALS and CUSTOM_MILITARY_STRATEGY positions can be created by any reason (including "as a matter of course").

The following table gives an overview of the possible non-ruling civ-level positions:

{| class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name prefix!!Name5!!Responsibilities!!Demands!!Mandates!!Precedence!!Number!!Flags11!!Flags22!!Color!!human!!goblin

|-
!CUSTOM_OFFICIAL_1
|yes3
|"keeper of the seal" / chancellor
|receive diplomats, make introductions and make topic agreements; optional: espionage
|3
|2
|20
|1
|yes
|no
|(5,0,1)
|yes
|yes

|-
!CUSTOM_OFFICIAL_2
|yes3
|justiciar
|law enforcement, collect taxes
|3
|2
|60
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_OFFICIAL_3
|yes
|treasurer
|trade, accounting
|2
|1
|70
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_OFFICIAL_4
|yes
|advisor/counselor
|advise leaders
|2
|1
|55
|1
|yes
|no
|(5,0,1)
|yes
|yes

|-
!CUSTOM_OFFICIAL_5
|yes3
|chamberlain
|oversee leader household
|1
|0
|80
|1
|yes
|no
|(5,0,1)
|yes
|yes

|-
!CUSTOM_OFFICIAL_6
|no
|master of beasts
|tame exotics, manage animals
|1
|0
|90
|1
|yes
|no
|(5,0,1)
|yes
|yes

|-
!CUSTOM_OFFICIAL_7
|yes
|butler / cup-bearer
|manage leader household food and drinks
|0
|0
|300
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_OFFICIAL_8
|yes
|doctor
|health management
|0
|0
|310
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_OFFICIAL_9
|yes
|executioner
|executions
|0
|0
|320
|1
|yes
|no
|(5,0,1)
|yes
|yes

|-
!CUSTOM_OFFICIAL_10
|yes
|chef
|prepare leader meals
|0
|0
|330
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_OFFICIAL_11
|yes
|housekeeper
|manage leader household cleanliness
|0
|0
|340
|1
|yes
|no
|(5,0,1)
|yes
|no

|-
!CUSTOM_MILITARY_STRATEGY
|no
|general/(field) marshal / constable
|military strategy
|3
|2
|50
|1
|yes
|yes
|(5,0,1)
|yes
|yes

|-
!CUSTOM_MILITARY_GOALS4
|no
|war leader
|military goals, optional: military strategy
|3
|2
|45
|1
|yes
|yes
|(5,0,1)
|no
|no
|}
: ''Note'':
:* 1) These are the standard official flags: duty_bound, has_responsibilities, do_not_cull, has_met_pop_req, color, menial_work_exemption, has_received_positions and has_met_market_req.
:* 2) These are the following additional flags: flashes, brag_on_kill, chat_worthy, kill_quest, account_exempt, punishment_exemption, quest_giver and special_burial.
:* 3): Name prefix can be empty.
:* 4) These would be the values for the CUSTOM_MILITARY_GOALS position, but on the civ-level that position is not created, as the military goals responsibility is already performed by the law-giver/master (and for the military strategy responsibility the CUSTOM_MILITARY_STRATEGY position is created instead). But a CUSTOM_MILITARY_GOALS position would be created, if the civ leader would not have the military goals responsibility. The CUSTOM_MILITARY_GOALS position is - in vanilla - only created for site governments and then only, if the site leader is the FORCED_ADMINISTRATOR.
:* 5): Name prefixes are: high, head, chief and royal.

In the above table the responsibility "espionage" of the CUSTOM_OFFICIAL_1 is optional. A civ needs to have a "cunning" value of at least 11 for the CUSTOM_OFFICIAL_1 to have the responsibility, otherwise the official will not have the espionage responsibility, consequentially all CUSTOM_OFFICIAL_1 of goblin civs will have the espionage responsibility (as their default cunning value is 15). Only if the CUSTOM_OFFICIAL_1 is created with the "espionage" responsibility such officials can also be created for the site governments, where the leader of the site-government is not called "law-giver", (as all other responsibility are already performed by the standard custom site ruler). Also, the columns "human" and "goblin" dictate whether human and/or goblin civilizations can have the positions.

= Site Governments =
If all positions of a civ (and with that of a site government) are variable, then a leader position for the site government needs to be created (in world-gen), before other positions (of the possible variable positions) can be created. The created position is usually the CUSTOM_LAW_MAKER, but other positions have been found, ie. CUSTOM_BANDIT_LEADER and FORCED_ADMINISTRATOR.

Note that if a site is taken over during a war, then a new leader can be created directly with the formation of a new site government (even if the all site positions of the new owning civ are variable and the old site government did not have any leaders), in such cases the new leader position is either a FORCED_ADMINISTRATOR or - rarer - a CUSTOM_LAW_MAKER (only found, if the site taken over was a Town and both the defending and attacking civilization was human).

Note that human and goblin civilizations can also create further site positions, if the current site leader is the CUSTOM_BANDIT_LEADER (both) or FORCED_ADMINISTRATOR (only encountered/found in case of humans). All other races (eg. dwarves and elves) cannot.

Also a CUSTOM_LAW_MAKER can be created for a site government (of a human civilization) before a CUSTOM_LAW_MAKER for the civilization has been created.

Also note that not all site government entities need to be a child of a civilization entity, if they are not, then the CUSTOM_BANDIT_LEADER is used as a site-ruler (regardless of race, ie. even dwarven and the rare elven site government without connection to a civ will use the CUSTOM_BANDIT_LEADER as initial ruler/leader).

The following table gives an overview of the possible leader positions:

{| class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name!!Responsibilities!!squad8 size!!Demands!!Mandates!!Precedence!!goblin!!human!!elf!!dwarf!!flags!!appointment type

|-
!CUSTOM_BANDIT_LEADER1
|Boss, Captain, Chief, Chieftain, Commander, Leader, Master, Overlord, Ringleader or Warlord
|law making, law enforcement, receive diplomats, make introductions, make topic agreements, military strategy, military goals
|20
|2
|1
|55 or 10 (rare)
|yes
|yes
|yes
|yes
|standard bandit leader
|elected

|-
!FORCED_ADMINISTRATOR
|administrator
|law making, receive diplomats, meet workers, make topic agreements
|0
|3
|2
|100
|yes
|yes
|yes
|yes2
|forced admin
|none3

|-
!FORCED_ADMINISTRATOR4
|administrator
|law making, receive diplomats, meet workers, make topic agreements
|0
|3
|2
|65
|no
|no
|no
|yes
|dwarf forced admin
|none3

|-
!CUSTOM_LAW_MAKER5
|law-giver
|law making, make peace agreements, military goals; optional6: military strategy
|0
|3
|2
|1
|no
|yes
|no
|no
|civ law-giver
|by heir

|-
!CUSTOM_LAW_MAKER6
|lord
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|20
|3
|2
|1
|no
|yes
|no
|no
|standard leader
|by heir

|-
!CUSTOM_LAW_MAKER
|lord
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|20
|3
|2
|40
|yes
|yes
|no
|no
|standard leader
|by heir

|-
!CUSTOM_LAW_MAKER
|baron
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|20
|3
|2
|41
|no
|yes
|no
|no
|standard leader
|by heir; appointed by law-giver (civ)

|-
!CUSTOM_LAW_MAKER_27
|baron
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|20
|3
|2
|35
|no
|yes
|no
|no
|standard leader
|by heir; optional: appointed9

|}

: ''Notes'':
:* 1): Only leader position, if the entity (site-government) is not a child of a civilization, but can also appear, if the entity has a parent civ. Only site leader position of goblins, where other site positions will be created (both cases: with civ and without civ).
:* 2): 2 of the 53 forced administrator positions of dwarves (in a large 250 year histor world-gen world with many civs) used this forced administrator (rather than the one defined in the raws). No site official positions found for goblins so far, if the leader was a forced administrator.
:* 3): The position has no appointed_by defined, nor any form of succession by position or heir. And the position is also not elected. So how and if a forced admin gets refilled, in case of death of the previous position holder, is unclear.
:* 4): This is the forced administrator as defined in the (vanilla) dwarf raws.
:* 5): Was created once in a large 250 year history world-gen world with many civs. The parent civ did not have a law-maker position created. But this definition is not always used, if the law-maker position of the parent civ has not been created. Also the site-entity was the original owner/creator of the site.
:* 6): This position can get created for a newly formed site-entity, if a site-entity has created the law-maker position and afterwards the site-entity gets conquered by another entity (of the same civ) and at the time of conquest no law-giver was created (yet) for the civ.
:* 7: Can be created (and replaces the former site ruler), if the ruler (of a human site entity) was either a FORCED_ADMINISTRATOR or a CUSTOM_LAW_MAKER with the name "lord".
:* 8): If the squad size is greater than zero, then the squad members are called soldiers (CUSTOM_BANDIT_LEADER) or hearthpeople (otherwise).
:* 9): Always appointed by the law-giver of the civilization, if the previous site leader was a forced administrator. Otherwise the appointed_by (and appointed_by_civ) definition is either empty or set to the law-giver of the civ, eg. a CUSTOM_LAW_MAKER_2, which replaces a CUSTOM_LAW_MAKER, can be appointed (in which case appointed by the law-giver of the civ) or not be appointed at all.
:* "by heir" in the appointment type definition entry means, that the succession is by heir. If nothing else is mentioned in the table cell, then the position did get filled immediatly upon creation of the position and the first position holder was not appointed by the civ-leader, otherwise the first position holder was appointed by the civ-leader.
:* "standard bandit leader" entry in "flags" table cell means the same flags as the CUSTOM_BANDIT_LEADER of bandit groups are set.
:* "forced admin" entry in "flags" table cell: is_law_maker, duty_bound, has_responsibitities, flashes, brag_on_kill, chat_worthy, do_not_cull, kill_quest, is_leader, is_diplomat, exported_in_legends, determines_coin_design, account_exempt, color, rules_from_location, menial_work_exemption, sleep_pretesion, punishment_exemption, has_received_positions, quest_giver, special_burial.
:* "dwarf forced admin" entry in "flags" table cell: is_law_maker, duty_bound, has_responsibitities, flashes, brag_on_kill, chat_worthy, do_not_cull, kill_quest, is_leader, is_diplomat, exported_in_legends, determines_coin_design, account_exempt, color, menial_work_exemption, sleep_pretesion, punishment_exemption, has_received_positions, special_burial.
:* "standard leader" entry in "flags" table cell: is_law_maker, duty_bound, has_responsibilities, flashes, brag_on_kill, chat_worthy, do_not_cull, kill_quest, is_leader, exported_in_legends, determines_coin_design, account_exempt, color, rules_from_location, menial_work_exemption, punishment_exemption, has_received_positions, quest_giver, special_burial.
:* "civ law-giver" entry in "flags" table cell means that the flags of the CUSTOM_LAW_MAKER (civ level) are set, where the is_diplomat flag is only set, if (and only if) the law-giver does not have the military strategy responsibility. Also in this case the is_diplomat flag is only set, if the "law-giver" (of the site entity) does not have the military strategy responsibility.
:* Remark to forced administrator: The only differences between the forced administrator (only usable by the dwarves and defined in the raws) and the other forced administrator are, that the forced administrator of the dwarves is not a quest giver, does not rule from a location and has a different precedence.
:* The color of all leaders is the standard noble color (5,0,1), except for the forced administrators, who uses a different color entry (5,0,0).

If a leader does exist for a site entity, other variable positions can be created for that entity. In rare cases a variable official (or market official) position can even be created, if the requirements are not met (at least one of the flags has_met_pop_req and has_met_market_req is false for the position entry).

The following table gives an overview of the non-ruler variable positions of a site government.

{| class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name prefix1!!Name!!Name suffix2!!Responsibilities!!Demands!!Mandates!!Precedence!!Number!!Color!!human!!goblin!!add. flags3

|-
!CUSTOM_MARKET_OFFICIAL_1
|no
|sewer
|always
|maintain sewers
|0
|0
|500
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MARKET_OFFICIAL_2
|no
|grain / harvest
|always
|food supply
|1
|0
|450
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MARKET_OFFICIAL_3
|no
|fire
|always
|fire safety
|0
|0
|475
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MARKET_OFFICIAL_4
|no
|judge / magistrate / justice
|no
|judge
|1
|0
|350
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MARKET_OFFICIAL_5
|no
|building
|always
|construction permits, building safety
|1
|0
|460
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MARKET_OFFICIAL_6
|no
|road
|always
|maintain roads, bridges and tunnels
|1
|0
|375
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_16,7,8
|optional
|"keeper of the seal" / chancellor
|no
|espionage
|3
|2
|20
|1
|(5,0,1)
|yes
|yes
|no

|-
!CUSTOM_OFFICIAL_27,9
|optional
|justiciar
|no
|collect taxes
|3
|2
|60
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_3
|always
|treasurer
|no
|trade, accounting
|2
|1
|70
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_4
|always
|advisor / counselor
|no
|advise leaders
|2
|1
|55
|1
|(5,0,1)
|yes
|yes
|no

|-
!CUSTOM_OFFICIAL_5
|optional
|chamberlain
|no
|oversee leader houshold
|1
|0
|80
|1
|(5,0,1)
|yes
|yes
|no

|-
!CUSTOM_OFFICIAL_6
|no
|master of beasts
|no
|tame exotics, manage animals
|1
|0
|90
|1
|(5,0,1)
|yes
|yes
|no

|-
!CUSTOM_OFFICIAL_7
|always
|butler / cup-bearer
|no
|manage leader houshold food and drinks
|0
|0
|300
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_8
|always
|doctor
|no
|health management
|0
|0
|310
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_9
|always
|executioner
|no
|executions
|0
|0
|320
|1
|(5,0,1)
|yes
|yes
|no

|-
!CUSTOM_OFFICIAL_10
|always
|chef
|no
|prepare leader meals
|0
|0
|330
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_OFFICIAL_11
|always
|housekeeper
|no
|manage leader houshold cleanliness
|0
|0
|340
|1
|(5,0,1)
|yes
|no
|no

|-
!CUSTOM_MILITARY_STRATEGY4
|no
|general/(field) marshal / constable
|no
|military strategy
|3
|2
|50
|1
|(5,0,1)
|yes
|no
|yes

|-
!CUSTOM_MILITARY_GOALS5
|no
|war leader
|no
|military goals, optional: military strategy
|3
|2
|45
|1
|(5,0,1)
|yes
|no
|yes

|}

: ''Notes'':
:* 1): The possible name prefixes are "chief", "head" and "high" (always) and also "royal", if the site leader has the name "law-giver". The name prefix can be empty, if the cell entry is "optional". A name prefix will always be present, if the cell entry is "always".
:* 2): The possible name suffixes are "administrator", "caretaker", "commissioner", "master" and "official". A name suffix will always be present, if the cell entry is "always".
:* 3): The additional flags are: flashes, brag_on_kill, chat_worthy, kill_quest, account_exempt, punishment_exemption, quest_giver and special_burial.
:* 4): Only ever created, if the first site leader was a FORCED_ADMINISTRATOR. Can even be created, if the FORCED_ADMINISTRATOR has already been replaced by a CUSTOM_LAW_MAKER_2.
:* 5): Only created, either after the CUSTOM_MILITARY_GOALS position was created and the CUSTOM_MILITARY_GOALS position was not created with the military strategy responsibility or if the leader has the name law-giver (and does not have the military strategy responsibility). Can even be created, if the first site leader was a FORCED_ADMINISTRATOR, who has already been replaced by a CUSTOM_LAW_MAKER_2.
:* 6): If the leader name is not law-giver (and the first site leader was not a FORCED_ADMINISTRATOR), then a CUSTOM_OFFICIAL_1 has the espionage responsibilty. All CUSTOM_OFFICIAL_1 of a civ (regardless of whether the CUSTOM_OFFICIAL_1 belongs to a site government or the civ government) will either have the espionage responsibility or do not have the espionage responsibility.
:* 7): If the leader has the name law-giver then this official position has the responsibilities (and also optional resp.) as given in the civ table for the official position and not the responsibilities as in this table. Ie. that is the only case where a CUSTOM_OFFICIAL_1 can be created for a site government without the espionage responsibility.
:* 8): The CUSTOM_OFFICIAL_1 has always the responsibility make introductions, if the first site leader/ruler was a FORCED_ADMINISTRATOR, even if the FORCED_ADMINISTRATOR has already been replaced (by a CUSTOM_LAW_MAKER_2).
:* 9): The CUSTOM_OFFICIAL_2 has always the responsibility law enforcement, if the first site leader/ruler was a FORCED_ADMINISTRATOR, even if the FORCED_ADMINISTRATOR has already been replaced (by a CUSTOM_LAW_MAKER_2).
:* In the above table the columns "human" and "goblin" donate, whether a site government of a human civilization or of a goblin civilization can have that position (or at least, if the position was encountered so far). Note so far only goblin site governments with a CUSTOM_BANDIT_LEADER did have further positions created.
:* All CUSTOM_MARKET_OFFICIALs created during world-gen seem to have an already constructed market present (and thus are not created for site governments ruling over a Hamlet or a Dark Pit as Hamlets and Dark Pits cannot have a market, but need to be a Town or Dark Fortress). Additionally the CUSTOM_MARKET_OFFICIAL_1 needs an already constructed sewer (which seems to be only created, after both a market and a keep are constructed). Also note that sewers are only constructed in towns (in contrast to ie. markets, which can also be found/constructed in other site types like Dark Fortresses, Fortresses, Hillocks, Caves and Forest Retreats).
:* In addtion to the above table the "best_appointment_precedence" is 30001. Also the following flags are set (true) for all officials, regardless, of whether belonging to a human or goblin site government: duty_bound, has_responsibilities, do_not_cull, color, menial_work_exemption and has_received_positions.
:* All of the positions are appointed by the current ruler of the site (ie. CUSTOM_LAW_MAKER, CUSTOM_BANDIT_LEADER, FORCED_ADMINISTRATOR), except the CUSTOM_MILITARY_STRATEGY position will be appointed by the CUSTOM_MILITARY_GOALS position, if the CUSTOM_MILITARY_GOALS position was created prior and the current ruler of the site government is a forced administrator.

Additionally the position entry usually has the flag active set and the flag is_replaced is false, otherwise the position would no longer be active (and might have been replaced).

= Bandits =
Bandits use the entity types 4 and 7, which are nomadic groups (type 4) and outcasts (type 7). It must also be noted that some CUSTOM_BANDIT_LEADER positions are used by site governments (typically goblin site governments) both with and without a parent civilization (site government is not a child of an entity of type 0). The creation of CUSTOM_BANDIT_LEADER and CUSTOM_OUTCAST_FACTOR positions is never mentioned as a historical event, but the creation of CUSTOM_OUTCAST_LT is (and is always created "as a matter of course").

The following table gives an overview over the possible variable positions used by bandits (some further info on bandit leaders is below the table).

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name!!appointment type!!Responsibilities!!squad size!!Demands!!Mandates!!Precedence!!Number!!add. flags1!!rules from location!!entity type

|-
!CUSTOM_BANDIT_LEADER
|Boss, Captain, Chief, Chieftain, Commander, Leader, Master, Overlord, Ringleader or Warlord
|elected
|law making, law enforcement, receive diplomats, make introduction, make peace agreements, make topic agreements, military strategy and military goals
|20
|2
|1
|55
|1
|yes
|no
|nomadic, outcast

|-
!CUSTOM_BANDIT_LEADER2
|Boss, Captain, Chief, Chieftain, Commander, Leader, Master, Overlord, Ringleader or Warlord
|elected
|law making, law enforcement, receive diplomats, make introduction, make peace agreements, make topic agreements, military strategy and military goals
|20
|2
|1
|10
|1
|yes
|no
|nomadic

|-
!CUSTOM_OUTCAST_LT
|lieutenant
|appointed by bandit leader
|patrol territory, attack enemies
|0
|1
|0
|160
| -1
|no
|no
|outcast

|-
!CUSTOM_OUTCAST_FACTOR
|representative
|appointed by bandit leader
|trade and accounting
|0
|1
|0
|70
| -1
|yes (except is_law_maker)
|yes
|outcast

|}
: ''Notes'':
:* 1): Additional flags are: is_law_maker, flashes, brag_on_kill, chat_worthy, kill_quest, account_exempt and quest_giver
:* 2): Only difference to the other CUSTOM_BANDIT_LEADER is the increased precedence of 10, encountered in 11 of 148 bandit leaders (148 of 175 nomadic groups had leaders). The reason is of yet unknown, except that the CUSTOM_BANDIT_LEADER is also used by the goblin civilization (and some site governments, without an entity link to a parent civ, had a nomadic group with a custom bandit leader as a child entity).
:* Further note the common flags of these positions are: duty_bound, has_responsibilities, do_not_cull, is_leader, has_met_pop_req, menial_work_exemption, has_received_positions and has_met_market_req.
:* The entity type in the above table refers to the (as displayed by dfhack's gm-editor, when viewing an entity).

Additionally the bandit leader (CUSTOM_BANDIT_LEADER) always has a squad size of 20 and the squad members are refered to as "bandits".

= Religious Entities =
Some religious entities, which are considered "child"-entities of civilizations (no religious entity which was not a "child" of a civ entity has been found so far), also have variable positions - the other religious entities have no positions at all.
If a religious entity rules a site (always monastery?), then the only variable position (of that entity) seems to be the CUSTOM_LAW_MAKER and the name of the position seems to be always "abbot".
Otherwise the variable positions PRIEST, HIGH_PRIEST and HIGHEST_PRIEST can be created for that religious entity, where any such entity, if it has a position, will always have the PRIEST as position. Afterwards, the position HIGH_PRIEST can be created and at last - after the HIGH_PRIEST was created - the HIGHEST_PRIEST can be created. The names of these position are randomly created (more about the name generation is currently out-of-scope, ie. why a PRIEST might be called "sacred squid", "holy burial", "sacred rumor", "holy lemon" or "sacred paper" is out-of-scope at least for this wiki article). No temple is needed in an associated site for a religious entity (not ruling from a monastery) to create a priest, high priest or highest priest position.

Note that there is no historical event that mentions the creation of a PRIEST, HIGH_PRIEST or HIGHEST_PRIEST position.

An overview on the positions of religious entities is given in the following table:

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!name prefix!!name!!appointment type5!!Responsibilities!!Precedence!!Demands!!Mandates!!number!!missing common flags1!!additional flags2

|-
!CUSTOM_LAW_MAKER3
|
|abbot
|heir
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|100
|3
|2
|1
|is_diplomat
|all

|-
!PRIEST
|holy or sacred
|random4
|elected
|religion
|200
|0
|0
| -1
|none
|no

|-
!HIGH_PRIEST
|high, first or exalted
|random4
|elected
|law_making, receive diplomats and make topic agreements
|50
|3
|2
| -1
|none
|all (except determines_coin_design)

|-
!HIGHEST_PRIEST
|absolute or most sacred/high/exalted
|random4
|elected
|law_making, receive diplomats and make topic agreements
|1
|5
|3
|1
|none
|all (except determines_coin_design)

|}

Notes:
1): The common flags are: duty_bound, has_responsibilities, chat_worthy, do_not_cull, is_leader, is_diplomat, has_met_pop_req, rules_from_location, menial_work_exemption, punishment_exemption, has_received_positions and has_met_market_req. So if one of the flags is mentioned in a column, then the position does not have that flag.

2): The additional flags (in this case) are: is_law_maker, flashes, brag_on_kill, kill_quest, exported_in_legends, account_exempt, quest_giver, special_burial.

3): Is always the only position for that religious entity. And so far any such entity, which was found, always governed/ruled a monastery.

4): The name is one of the possible "name prefixes" for the position written before a completely random word, which may or may not depend on the religious spheres/domains worshipped by that religion.

5): The appointment/succession type is actually determined by flags, ie. elected and succession_by_heir. One of the flags is also true for these positions (but not explicitly mentioned in the common/additional flags).

Additional notes: The PRIEST, HIGH_PRIEST and HIGHEST_PRIEST have a variable color entry, but the color-flag (of the position entry) is false, so it is unclear whether currently the color entry has any effect.

= Mercenary Group =

All mercenary entities will have at least one position (the CUSTOM_MERCENARY_LEADER), this position is created with the creation of the group (and the creation of the entity is marked - in the history/legends - with the filling of the leader position). The only other possible position is the CUSTOM_MERCENARY_TREASURER and the creation of the CUSTOM_MERCENTARY_TREASURER is mentioned as a historical event (and is always created "as a matter of course").

Basic information about both positions are found in the table below (and the explanations below the table).

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name!!appointment type!!Responsibilities!!Precedence!!Demands!!Mandates!!number!! imp. flags1

|-
!CUSTOM_MERCENARY_LEADER
|usually "warlord", "leader", "general" or "overlord" but very unusual names are possible (see below table)
|elected
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|50
|2
|1
|1
|yes

|-
!CUSTOM_MERCENARY_TREASURER
|treasurer
|elected
|trade and accounting
|160
|1
|0
|1
|no

|}

Notes: 1): The imp. flags are flashes, brag_on_kill, chat_worthy, punishment_exemption, kill_quest and quest giver.

Both positions also have the is_leader flag and the following flags: duty_bound, has_responsibilities, has_met_pop_req, menial_work_exemption, has_received_positions and has_met_market_req.

For the mercenary leader also illustrous names such as lord twinkle, lord duty, lord savant, maze commander or secret commander can be created. In these cases the name seems to be generated by either adding a random word after the word lord or adding a random word before commander. Note that mercenary groups can bestow honors on either their members or their leaders and in case of leader only honors it might be that, instead of the leader name, the name of the currently highest bestowed honor (on the leader) is used.

= Guilds =
All guilds will always have all four of the variable positions mentioned in this section. Note that "merchant guilds" are merchant companies and an entirely separate entity.

The following table gives an overview of the four guild positions.

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!Name!!appointment type!!Responsibilities!!precedence!!demands!!mandates!!number!!add. flags1

|-
!CUSTOM_GUILD_LEADER
|dean/doyen
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military strategy, military goals
|elected
|50
|2
|1
|1
|yes

|-
!CUSTOM_GUILD_ALDERPERSON
|alderperson
|meet workers, manage production
|elected
|150
|1
|0
|1
|no

|-
!CUSTOM_GUILD_STEWARD
|steward or treasurer
|trade
|elected
|160
|1
|0
|1
|no

|-
!CUSTOM_GUILD_CLERK
|clerk, bookkeeper, recordkeeper
|accounting
|elected
|170
|1
|0
|1
|no

|}

Notes:
1): The additional flags are: is_law_maker, flashes, brag_on_kill; chat_worthy, do_not_cull, kill_quest, account_exempt, rules_from_location, punishment_exemption and quest_giver.

All positions have the following flags in common:
duty_bound, has_responsibilities, do_not_cull, is_leader, has_met_pop_req, menial_work_exemption, has_received_positions, has_met_market_positions.

= Merchant Company =
Every merchant company will have a leader (CUSTOM_COMPANY_LEADER). Furthermore a merchant company can have a CUSTOM_COMPANY_FACTOR, to which an unlimited number of history figures can be assigned to (ie. a company can have multiple governors, but the number of current governors is always the same as the number of counting houses - branches - in non-headquarters sites). Also note that there is no history event, which mentions the creation of a position for a merchant company, still the CUSTOM_COMPANY_FACTOR position is only created with creation of the first branch of a company (and branch creation - purchase of a counting house or building of a new counting house - and filling of custom company factor position are always at exactly the same time according to the corresponding historical events).

An overview of both positions is given by the following table:

{|class="sortable wikitable" style="text-align:center;"
|- style="background:#F2F2F2;"
!Position!!name!!appointment type!!Responsibilities!!Precedence!!Demands!!Mandates!!number!!additional flag

|-
!CUSTOM_COMPANY_LEADER
|master or head
|elected or succession by heir
|law making, law enforcement, receive diplomats, make introductions, make peace agreements, make topic agreements, military goals, military strategy
|50
|2
|1
|1
|is_law_maker

|-
!CUSTOM_COMPANY_FACTOR
|agent, factor, administrator or governor
|appointed by company leader
|trade and accounting
|200
|1
|0
| -1
|none

|}

Both positions have the following flags in common:
duty_bound, has_responsibilities, flashes, brag_on_kill, chat_worthy, do_not_cull, kill_quest, is_leader, account_exempt, has_met_pop_req, rules_from_location, menial_work_exemption, punishment_exemption, has_received_positions, quest_giver and has_met_market_req.

Also note that in contrast to many other variable positions (of different entities) for the CUSTOM_COMPANY_LEADER both an election based appointment (or succession) and an succesion by heir is possible, but each merchant company will only have an elected leader or a leader (with inheritance).

= Raw tokens =
The tokens that manage the creation of positions are [[Entity_token#SITE_VARIABLE_POSITIONS|SITE_VARIABLE_POSITIONS]] and [[Entity_token#VARIABLE_POSITIONS|VARIABLE_POSITIONS]].

SITE_VARIABLE_POSITIONS allows for the creation of lords, hearthpersons, and [[boss]]es, and [VARIABLE_POSITIONS] allows creation of Law-makers.

Structure

2026-03-12T14:16:56Z

91.49.243.26: /* Types */

{{migrated article}}
{{Quality|Fine}}
{{av}}

'''Structures''' are constructed or erected buildings found in [[site]]s. Structures acquire a history that can be viewed in [[Legends mode]].

=== Types ===
* [[Catacombs]] can be found in Dark Fortresses, Caves (rare), Fortresses, Hillocks (rare), Forest Retreats and Towns.
* [[Counting house]] can be found in Dark Fortresses (rare), Fortresses, Forest Retreats and Towns. Constructed by Merchant Companies.
* [[Guildhall]] can be found in Fortresses, Forest Retreats (only founded during the reign of a dwarven/human civ of a forest retreat) and Towns. Constructed by Guilds.
* [[Keep]] can be found in Dark Fortresses, Caves (rare), Fortresses, Forest Retreats and Towns.
* [[Library]] can be found in Fortresses and Towns, but - while not found so far - it cannot be currently ruled out that a Library might get constructed in a Forest Retreat or Dark Fortress (after a human/darven civilization did take over a site).
* [[Market]] can be found in Dark Fortresses, Caves (rare), Fortresses (all Fortresses, which are founded after year 1 during world-gen will construct a market as first building), Hillock (rare), Forest Retreats and Towns.
* [[Mead hall]] can be found in Dark Pits, Hillocks, Hamlets and Forest Retreats. If during world-gen a Dark Pit becomes a Dark Fortress or a Hamlet becomes a Town, then a previously constructed Mead Hall will cease to exist.
* [[Sewer]] can only be found in Towns.
* [[Tavern]] can be found in Dark Fortresses, Hillocks (rare), Fortresses, Forest Retreats and Towns.
* [[Temple]] can be found in Dark Fortresses, Caves, Hillocks, Fortresses, Forest Retreats, Towns, Monestaries and Forts. A Monestary will always have a temple.
* [[Tomb]] can be found in Dark Fortresses, Hillock (rare), Fortresses, Forest Retreats, Towns and Tombs (site).
* [[Tower (structure)|Tower]] can only be found in Towns.
* [[Underworld spire]] can only be found in Dark Fortresses.

''Note:'' Mountain Halls do not contain any structure.

{{World}}

{{Category|Adventurer mode}}

Guild

2026-03-12T14:15:26Z

91.49.243.26: /* Guilds in World Generation */ changed Mountain Halls to Fortress

{{Quality|Fine}}
{{av}}

'''Guilds''' are organizations established when enough members of your [[fortress]] are labeled with the same specific [[profession]] (e.g. Carpenter, Brewer or Bonecarver), or practice any professions in the same general category (e.g. Woodworker. Farmer or Craftsdwarf). The required number of members defaults to 10, but this can be changed in the [[Difficulty#Guilds|difficulty]] settings. Allowing many dwarves to do the same [[labor]]s can lead to them learning enough of that skill to form a guild, as can migrants arriving with skills in the same category. Dwarves in a fortress with a a guild for their profession and a guild for the more general category will be members of both guilds.

The name of a guild and its associated guildhall will reflect the profession of the guild, for example a [[Metalsmith]] guild called "The Guild of Oiling" with a guildhall named "The Cave of Copper", or a [[Ranger]] guild called "The Autumnal Guild" with a guildhall named "The Grove of Deer", and so on.

== Guildhall ==
{{main|Guildhall}}
Shortly after establishment, the guild will petition for the construction of a guildhall, where its members will socialize and hold [[skill]] demonstrations, slowly training them in the skill. However, any guildhall can be built at any time, and even if a guild is not established, any one with the right skill can still hold public demonstrations for idlers; this is useful for having dwarves teach each other [[strange_mood|desirable]] skills. If a guild grows to enough members (25 by default, but can also be changed), they will petition for a Grand guildhall.

A guildhall requires a certain [[Zone#Quality and value|zone value]] to be considered established, as [[appraiser|appraised]] by the fortress' [[broker]]. The default values are 2000☼ to upgrade a meeting place to a guildhall and 10,000☼ for a grand guildhall, but these can be changed in the [[Difficulty#Guilds|difficulty]] settings. Accepting such a petition, but failing to deliver one with enough value, will cause negative thoughts for the guild members after one [[Calendar|year]].

==List of guilds==
This is a list of guildhalls that you can select when adding a new [[location]] (e.g. {{menu icon|z}} -> set a zone -> [[File:Ui location add.png|28px]] -> "New guildhall" -> choose a guild type). General guilds are in '''bold''', followed by specific guilds they include.

There are many [[peasant]] and other non-productive "professions" that will not have guildhalls.

{| {{prettytable}}
|-
! [[Miner]] hall
|-
! [[Woodworker]] hall
| [[Carpenter]] hall • [[Bowyer]] hall • [[Woodcutter]] hall
|-
! [[Stoneworker]] hall
| [[Engraver]] hall • [[Mason]] hall
|-
! [[Ranger]] hall
| [[Animal caretaker|Animal Caretaker]] hall • [[Hunter]] hall • [[Trapper]] hall • [[Animal dissector|Animal Dissector]] hall
|-
! [[Metalsmith]] hall
| [[Furnace operator|Furnace Operator]] hall • [[Weaponsmith]] hall • [[Armorsmith|Armorer]] hall • [[Blacksmith]] hall • [[Metalcrafter]] hall
|-
! [[Jeweler]] hall
| [[Gem cutter|Gem Cutter]] hall • [[Gem setter|Gem Setter]] hall
|-
! [[Craftsdwarf]] hall
| [[Woodcrafter]] hall • [[Stonecrafter]] hall • [[Leatherworker]] hall • [[Bone carver|Bone Carver]] hall • [[Weaver]] hall • [[Clothier]] hall • [[Glassmaker]] hall • [[Potter]] hall • [[Glazer]] hall • [[Wax worker|Wax Worker]] hall • [[Strand extractor|Strand Extractor]] hall
|-
! [[Fishery worker|Fishery Worker]] hall
| [[Fisherdwarf]] hall • [[Fish dissector|Fish Dissector]] hall • [[Fish cleaner|Fish Cleaner]] hall
|-
! [[Farmer]] hall
| [[Cheese maker|Cheese Maker]] hall • [[Milker]] hall • [[Cook]] hall • [[Thresher]] hall • [[Miller]] hall • [[Butcher]] hall • [[Tanner]] hall • [[Dyer]] hall • [[Grower|Planter]] hall • [[Herbalist]] hall • [[Brewer]] hall • [[Soaper|Soap Maker]] hall • [[Potash maker|Potash Maker]] hall • [[Lye maker|Lye Maker]] hall • [[Wood burner|Wood Burner]] hall • [[Shearer]] hall • [[Spinner]] hall • [[Presser]] hall • [[Beekeeper]] hall
|-
! [[Engineer]] hall
| [[Mechanic]] hall • [[Siege engineer|Siege Engineer]] hall • [[Siege operator|Siege Operator]] hall • [[Pump operator|Pump Operator]] hall
|-
! [[Doctor]] hall
| [[Diagnostician|Diagnoser]] hall • [[Bone doctor|Bone Doctor]] hall • [[Suturer]] hall • [[Surgeon]] hall
|}

==Guilds in World Generation==
Guilds are formed in world generation, by civilizations that value [[Personality value#CRAFTSMANSHIP|craftsmanship]], such as [[dwarf|dwarves]] and [[human]]s. These guilds will have various [[historical figure]]s take up positions in them, as well as build themselves guildhalls in settlements, and have also been observed to occasionally help construct monasteries for [[Temple|religious groups]]. There are always four possible positions in the generated guilds: A Leader (dean/doyen, handles negotiations), an Alderman (manages work orders), a Steward (handles trade) and a Clerk/[[Record keeper]] (see [[Variable_positions#Guilds| variable guild positions]] for further technical details about the positions). The formation of a guild will always also result in the construction of a guild hall at the same time, but the guild positions (which are created with the formation of the guild) might not get filled for a long time (and stay empty) or only some of them getting filled with a historical figure during world generation. In most cases the site, where the guild hall is constructed, is a Fortress or Town, but occasionally a guild can also be found at a Forest Retreat (controlled by humans or dwarves when the guild was founded and not by the [[elf| tree-huggers]]).

The guild positions are not yet available within fortress mode (and are in fact superfluous as the responsibilities are already performed by the recordkeeper, manager, broker and mayor/expedition leader of any dwarven fortress), and thus, guilds made in fortresses don't get them.

{{D for Dwarf}}
In light of recent accidents, the Farmer's Guild has been restricted from performing any gelding demonstrations until further notice.

Fisherdwarves with Master or higher skill in fishing appear to be able to lead milking demonstrations at legendary level, regardless of their actual Milker skill.

Despite recent events in the human world, the Writer's Guild of the Mountainhomes is still working...for now.

The Stone Carvers Guild has been outlawed for undwarven activities. The Stone Cutters Guild has been outlawed for failure to follow Dwarven Occupation Safety Guidelines.
{{Category|Jobs}}{{Template:V50 entities}}
[[ru:Guild]]

Company

2026-03-12T14:14:12Z

91.49.243.26: Changed Mountain Halls to Fortresses (as the type "MountainHalls" according to dfhack can translate to Fortress in Legends Mode) and Mountain Halls (Legends Mode) do not contain any structures.

{{Quality|Fine}}
{{av}}

Trade '''companies''' are mostly world-gen only entities focused on lucrative trade (but their positions, see [[Variable_positions#Merchant_Company|variable positions]], have the necessary flags set to give [[Quest|quests]] to adventurers in adventure mode). Their Headquarters - a [[counting house]] - will usually be founded in a [[town]], but could occasionally also be found in a [[Forest_retreat|forest retreat]] (ie. during a time the forest retreat was taken over by humans). Their Headquarters cannot switch ownership. Branches (or trade outposts), which are also based in counting houses, can be founded in other sites (including forest retreats, Fortresses and dark fortresses) and can either be build or purchased and these counting houses can switch ownership (ie. due to bandits having taken over a counting house and using it as a base of operation). In worldgen, traveling merchants and companies piggy-back on the more abstract industry/trade simulation that links most sites. At their peaks, the companies will form multiple branches (or trade outposts) in other civs along the trade routes to facilitate more cross-civ link formation.

Trade companies are distinct from [[mercenary]] orders, although these are sometimes also called companies.
 
{{Template:V50 entities}}
{{Category|World}}
[[ru:Company]]