v50 Steam/Premium information for editors
  • v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
  • Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.

Editing Position token

Jump to navigation Jump to search

Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.

If you are creating a redirect to the current version's page, do not use any namespace. For example: use #REDIRECT [[Cat]], not #REDIRECT [[Main:Cat]] or #REDIRECT [[cv:Cat]]. See DF:Versions for more information.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 6: Line 6:
 
__TOC__
 
__TOC__
 
{{clear}}
 
{{clear}}
 
==Code==
 
A position is defined with a position 'code', as argument in de [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==
 
==Position tokens==
Line 27: Line 24:
 
| {{text anchor|ALLOWED_CLASS}}
 
| {{text anchor|ALLOWED_CLASS}}
 
| {{token|CREATURE_CLASS|creature}} token
 
| {{token|CREATURE_CLASS|creature}} token
| Only creatures with the specified class token can be appointed to this position. Multiple entries are allowed
+
| Only creatures with the specified class token can be appointed to this position.
  
 
|-
 
|-
 
| {{text anchor|ALLOWED_CREATURE}}
 
| {{text anchor|ALLOWED_CREATURE}}
 
| CREATURE:CASTE
 
| CREATURE:CASTE
| Restricts the position to only the defined [[caste]]. Multiple entries are allowed. Only works with a caste of the entity's current race. It does not prevent other creature-types to gain that position, at least not in world-gen.
+
| Restricts the position to only the defined [[caste]]. Only works with a caste of the entity's current race. (If the entity had multiple CREATURE: tokens)
  
 
|-
 
|-
 
| {{text anchor|APPOINTED_BY}}
 
| {{text anchor|APPOINTED_BY}}
 
| position
 
| 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]]
+
| 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.
  
 
|-
 
|-
Line 53: Line 50:
 
| {{text anchor|COLOR}}
 
| {{text anchor|COLOR}}
 
| 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.
+
| Creatures of this position will have this color, instead of their profession color, e.g. [COLOR:5:0:1].
  
 
|-
 
|-
 
| {{text anchor|COMMANDER}}
 
| {{text anchor|COMMANDER}}
 
| position:ALL
 
| 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
+
| 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.
  
 
|-
 
|-
Line 83: Line 80:
 
| {{text anchor|DUTY_BOUND}}
 
| {{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. If they are not DUTY_BOUND, they will live anywhere as they like.
+
| Members of this position will never agree to 'join' your character during adventure mode.
  
 
|-
 
|-
 
| {{text anchor|ELECTED}}
 
| {{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]]
+
| 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].
  
 
|-
 
|-
Line 117: Line 114:
 
|-
 
|-
 
| {{text anchor|LAND_HOLDER}}
 
| {{text anchor|LAND_HOLDER}}
| importance tier (1-10)
+
| importance tier (1-3)
| This is an alternative to SITE.  What it does is allow 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 LAND_HOLDER_TRIGGER.  The character is tied permanently to a particular site but also operates at the civ-level. Since 50* modded levels of higher than 3 are possbile.
+
| This is an alternative to SITE.  What it does is allow 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 LAND_HOLDER_TRIGGER.  The character is tied permanently to a particular site but also operates at the civ-level.
Read more: [[Advanced_Entity_Position_Mechanics#land holder]]
 
  
 
|-
 
|-
 
| {{text anchor|LAND_NAME}}
 
| {{text anchor|LAND_NAME}}
 
| string
 
| string
| 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.
+
| The name the area takes on when under the control of a LAND_HOLDER. E.g. for the DUKE, [LAND_NAME:a duchy]
  
 
|-
 
|-
Line 159: Line 155:
 
| singular:plural
 
| singular:plural
 
| If the creature holding the position is female, this is the position's name. E.g. for MONARCH, [NAME_FEMALE:queen:queens]
 
| If the creature holding the position is female, this is the position's name. E.g. for MONARCH, [NAME_FEMALE:queen:queens]
 
|-
 
| {{text anchor|DESCRIPTION}}
 
|
 
| description of this position in the nobles screen.
 
  
 
|-
 
|-
Line 169: Line 160:
 
|  
 
|  
 
* number/AS_NEEDED
 
* 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.
+
| 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 only to positions involved with the military command chain; this is used to allow armies to expand to whatever size they need to be. Non-military positions with NUMBER:AS_NEEDED will not be appointed.
The problem with [[Lieutenant]]s and [[Captain]]s not been created, is their AS_NEEDED number. They are only then created when the'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}}
 
| {{text anchor|PRECEDENCE}}
 
| number (0-30000)/NONE
 
| 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 just assumes that anything with [PRECEDENCE:1] is the ruler, for both embark screen and mountainhome purposes. A civ-position will also be created without precedence. Positions may have the same precedence and will be appointed, although the effect is unknown.  
+
| 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.
  
 
|-
 
|-
 
| {{text anchor|PUNISHMENT_EXEMPTION}}
 
| {{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}}
+
| The position holder will not be held accountable for his or her crimes. Currently nonfunctional.{{bug|4589}}
  
 
|-
 
|-
Line 191: Line 180:
 
| {{text anchor|REJECTED_CLASS}}
 
| {{text anchor|REJECTED_CLASS}}
 
| CREATURE_CLASS Token
 
| CREATURE_CLASS Token
| Creatures of the specified class cannot be appointed to this position. Multiple entries are allowed
+
| Creatures of the specified class cannot be appointed to this position.
  
 
|-
 
|-
 
| {{text anchor|REJECTED_CREATURE}}
 
| {{text anchor|REJECTED_CREATURE}}
 
| CREATURE:CASTE
 
| 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.
+
| Restricts position holders by CREATURE type.
  
 
|-
 
|-
 
| {{text anchor|REPLACED_BY}}
 
| {{text anchor|REPLACED_BY}}
 
| position
 
| position
| This position is absorbed by another down the line. For example, expedition leader is [REPLACED_BY:MAYOR]. Only a single entry is allowed.
+
| This position is absorbed by another down the line. For example, expedition leader is [REPLACED_BY:MAYOR].
  
 
|-
 
|-
Line 256: Line 245:
 
| {{text anchor|RESPONSIBILITY}}
 
| {{text anchor|RESPONSIBILITY}}
 
| responsibility
 
| responsibility
| The position holder does a thing. See the table below for suitable arguments. A position does not need to have a responsibility.
+
| The position holder does a thing. See the table below for suitable arguments.
  
 
|-
 
|-
Line 302: Line 291:
 
|  
 
|  
 
* BY_HEIR / BY_POSITION:position
 
* 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.
+
| 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 populationnumber is reached. If a valid successor is available, he will be the one taking that position initially, without appointment or election.
 
  
 
|}
 
|}
Line 318: Line 306:
  
 
|-
 
|-
| {{text anchor|ADVISE_LEADERS}}
+
| {{text anchor|ADVISE_LEADERS}}{{version|0.47.01}}
 
|
 
|
  
Line 330: Line 318:
  
 
|-
 
|-
| {{text anchor|BUILDING_SAFETY}}
+
| {{text anchor|BUILDING_SAFETY}}{{version|0.47.01}}
 
|
 
|
  
Line 338: Line 326:
  
 
|-
 
|-
| {{text anchor|CONSTRUCTION_PERMITS}}
+
| {{text anchor|CONSTRUCTION_PERMITS}}{{version|0.47.01}}
|
 
 
 
|-
 
| {{text anchor|DELIVER_MESSAGES}}
 
| Found on [[messenger]]. Position travels to other sites and uses [[social skill]]s.
 
 
|
 
|
 
  
 
|-
 
|-
Line 356: Line 338:
  
 
|-
 
|-
| {{text anchor|ESPIONAGE}}
+
| {{text anchor|ESPIONAGE}}{{version|0.47.01}}
 
| Found on [[dungeon master]] and [[General|princess]] and uses the [[schemer]] skill.
 
| Found on [[dungeon master]] and [[General|princess]] and uses the [[schemer]] skill.
  
 
|-
 
|-
 
| {{text anchor|ESTABLISH_COLONY_TRADE_AGREEMENTS}}
 
| {{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 LAND_HOLDER 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 arrive and this can thus be modded by setting [[Entity_token#ACTIVE_SEASON]]
+
| 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 LAND_HOLDER 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.
  
 
|-
 
|-
 
| {{text anchor|EXECUTIONS}}
 
| {{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.
+
| Found on [[hammerer]]. Position executes death penalty judgements with a weapon of the appropriate skill.
  
 
|-
 
|-
| {{text anchor|FIRE_SAFETY}}
+
| {{text anchor|FIRE_SAFETY}}{{version|0.47.01}}
 
|
 
|
  
 
|-
 
|-
| {{text anchor|FOOD_SUPPLY}}
+
| {{text anchor|FOOD_SUPPLY}}{{version|0.47.01}}
 
|
 
|
  
Line 380: Line 362:
  
 
|-
 
|-
| {{text anchor|JUDGE}}
+
| {{text anchor|JUDGE}}{{version|0.47.01}}
 
|
 
|
  
 
|-
 
|-
 
| {{text anchor|LAW_ENFORCEMENT}}
 
| {{text anchor|LAW_ENFORCEMENT}}
| Found on [[sheriff]]/[[captain of the guard]]. Position and its subordinates are in charge of punishing criminals. A [SITE] position holding this responsibility plus the SQUAD token (or allowing the entity to have a SITE_VARIABLE_POSITION with this responsibility) is required for an adventurer from a given civilization to start as a hearthperson, fortress guard, etc. Cannot be combined with EXECUTIONS, resulting in the "Invalid Officer"-error.
+
| Found on [[sheriff]]/[[captain of the guard]]. Position and its subordinates are in charge of punishing criminals. A [SITE] position holding this responsibility plus the SQUAD token (or allowing the entity to have a SITE_VARIABLE_POSITION with this responsibility) is required for an adventurer from a given civilization to start as a hearthperson, fortress guard, etc.
  
 
|-
 
|-
Line 392: Line 374:
  
 
|-
 
|-
| {{text anchor|MAINTAIN_BRIDGES}}
+
| {{text anchor|MAINTAIN_BRIDGES}}{{version|0.47.01}}
 
|
 
|
  
 
|-
 
|-
| {{text anchor|MAINTAIN_ROADS}}
+
| {{text anchor|MAINTAIN_ROADS}}{{version|0.47.01}}
 
|
 
|
  
 
|-
 
|-
| {{text anchor|MAINTAIN_SEWERS}}
+
| {{text anchor|MAINTAIN_SEWERS}}{{version|0.47.01}}
 
|
 
|
  
 
|-
 
|-
| {{text anchor|MAINTAIN_TUNNELS}}
+
| {{text anchor|MAINTAIN_TUNNELS}}{{version|0.47.01}}
 
|
 
|
  
Line 417: Line 399:
 
|-
 
|-
 
| {{text anchor|MAKE_TOPIC_AGREEMENTS}}
 
| {{text anchor|MAKE_TOPIC_AGREEMENTS}}
| Found on diplomat. Position negotiates special agreements, such as tree cutting quotas. Used when elevating a settlement in the LAND_HOLDER chain up from level 1.
+
| Found on diplomat. Position negotiates special agreements, such as tree cutting quotas.
  
 
|-
 
|-
| {{text anchor|MANAGE_ANIMALS}}
+
| {{text anchor|MANAGE_ANIMALS}}{{version|0.47.01}}
 
| Found on [[dungeon master]].
 
| Found on [[dungeon master]].
  
 
|-
 
|-
| {{text anchor|MANAGE_LEADER_HOUSEHOLD_CLEANLINESS}}
+
| {{text anchor|MANAGE_LEADER_HOUSEHOLD_CLEANLINESS}}{{version|0.47.01}}
 
|
 
|
  
 
|-
 
|-
| {{text anchor|MANAGE_LEADER_HOUSEHOLD_DRINKS}}
+
| {{text anchor|MANAGE_LEADER_HOUSEHOLD_DRINKS}}{{version|0.47.01}}
 
|
 
|
  
 
|-
 
|-
| {{text anchor|MANAGE_LEADER_HOUSEHOLD_FOOD}}
+
| {{text anchor|MANAGE_LEADER_HOUSEHOLD_FOOD}}{{version|0.47.01}}
 
|
 
|
  
Line 449: Line 431:
 
|-
 
|-
 
| {{text anchor|MILITARY_STRATEGY}}
 
| {{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, position will go on expeditions to tame exotic creatures. Counterintuitively not by the TAME_EXOTICS-position. The destinations of these expeditions are determined by the entities USE_(...)_ANIMALS-tokens.  
+
| Found on [[general]]/[[militia commander]]. During worldgen, position will go on expeditions to tame exotic creatures. 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.{{version|0.44.01}}
  
 
|-
 
|-
| {{text anchor|OVERSEE_LEADER_HOUSEHOLD}}
+
| {{text anchor|OVERSEE_LEADER_HOUSEHOLD}}{{version|0.47.01}}
 
|
 
|
  
Line 460: Line 442:
  
 
|-
 
|-
| {{text anchor|PREPARE_LEADER_MEALS}}
+
| {{text anchor|PREPARE_LEADER_MEALS}}{{version|0.47.01}}
 
|
 
|
  
Line 477: Line 459:
 
|-
 
|-
 
| {{text anchor|TAME_EXOTICS}}
 
| {{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
+
| Position will tame animals with the {{token|PET_EXOTIC}} token. Currently unused - was originally assigned to the dungeon master.
  
 
|-
 
|-
 
| {{text anchor|TRADE}}
 
| {{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 [[Entity_token#ACTIVE_SEASON]]
+
| 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.
  
 
|-
 
|-
Line 524: Line 506:
  
 
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.'''
 
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|Modding}}
 
{{Category|Tokens}}
 
{{Category|Tokens}}
 
[[ru:Position token]]
 
[[ru:Position token]]

Please note that all contributions to Dwarf Fortress Wiki are considered to be released under the GFDL & MIT (see Dwarf Fortress Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)

Templates used on this page:

This page is a member of 2 hidden categories: