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.

Difference between revisions of "v0.31:Position token"

From Dwarf Fortress Wiki
Jump to navigation Jump to search
Line 119: Line 119:
 
| MENIAL_WORK_EXEMPTION
 
| MENIAL_WORK_EXEMPTION
 
|  
 
|  
| The position cannot be assigned labours, and will generally just lounge around like nobles do.
+
| The position cannot be assigned labours, and will generally just lounge around like nobles do. Currently does not actually work. {{bug|3721}}
  
 
|-
 
|-
 
| MENIAL_WORK_EXEMPTION_SPOUSE
 
| MENIAL_WORK_EXEMPTION_SPOUSE
 
|  
 
|  
| The spouse of the position holder doesn't have to work, either.
+
| The spouse of the position holder doesn't have to work, either. Also doesn't work either. {{bug|3721}}
  
 
|-
 
|-

Revision as of 21:05, 12 May 2011

This article is about an older version of DF.

These tokens define positions in entity_*.txt files. See Template:L.

Position Tokens

These tokens belong in an entity definition. These tokens apply to a position (such as monarch, dungeon master, etc) and should follow the [POSITION:POSITION_NAME] token.

Token Arguments Description
ACCOUNT_EXEMPT The position holder is not subjected to the Dwarven Economy.
ALLOWED_CLASS CREATURE_CLASS Token Only creatures with the specified class token can be appointed to this position in Fortress Mode. Has no effect on world generation.
ALLOWED_CREATURE ??? Unknown - may restrict position holders by CREATURE type.
APPOINTED_BY position The position used as an argument selects creatures to fill the role in question. For example, the GENERAL is [APPOINTED_BY:MONARCH].
BRAG_ON_KILL A creature that kills this position will be sure to talk about it a lot.
CHAT_WORTHY In adventure mode, when referencing locations an NPC may mention this position holder living there or having done some deed there.
COLOR color Creatures of this position will have this colour, instead of their profession colour. e.g. [COLOR:5:0:1]
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.
CONQUERED_SITE This position will be available to creatures when the site has been taken over by another civilisation.
DEMAND_MAX number (0-100) How many demands at one time the position can make of the population.
DETERMINES_COIN_DESIGN Coins minted will have images that reflect the personality of this position holder.
DO_NOT_CULL The position won't be culled during world generation.[Verify]
DUTY_BOUND Members of this position will never agree to 'join' your character during adventure mode.
ELECTED The population will periodically select the creature to fill this position.
EXPORTED_IN_LEGENDS The various members who have filled this role will be listed in the civilisation's history.
FLASHES The creature holding this position will flash on the display.
GENDER
  • MALE/FEMALE
The position can only be held by specified gender.
KILL_QUEST The position can assign quests to adventurers.
LAND_HOLDER number The position will arrive when the LAND_HOLDER_TRIGGER in the entity definition has been met.
LAND_NAME string The name the area takes on when under the control of a LAND_HOLDER. E.g. for the DUKE, [LAND_NAME:a duchy]
MANDATE_MAX number (0-100) The maximum number of mandates the position can make at once.
MENIAL_WORK_EXEMPTION The position cannot be assigned labours, and will generally just lounge around like nobles do. Currently does not actually work. Bug:3721
MENIAL_WORK_EXEMPTION_SPOUSE The spouse of the position holder doesn't have to work, either. Also doesn't work either. Bug:3721
MILITARY_SCREEN_ONLY The position only shows up in the Military screen.[Verify]
NAME singular:plural The name of the position.
NAME_MALE singular:plural If the creature holding the position is male, this is the position's name. E.g. for MONARCH, [NAME_MALE:king:kings]
NAME_FEMALE singular:plural If the creature holding the position is female, this is the position's name. E.g. for MONARCH, [NAME_FEMALE:queen:queens]
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.
PRECEDENCE number (0-30000) How important the position is in society; a lower number is more important. For MONARCH it's 1, for MILITIA_CAPTAIN it's 200.
PUNISHMENT_EXEMPTION The position holder will not be held accountable for his or her crimes.
QUEST_GIVER The position holder can give quests in Adventurer mode. Functionality in 0.31.13 and later is uncertain.
REJECTED_CLASS CREATURE_CLASS Token Creatures of the specified class cannot be appointed to this position in Fortress Mode. Has no effect on world generation.
REJECTED_CREATURE ??? Unknown - may restrict position holders by CREATURE type.
REPLACED_BY position For when one position is a lesser form of another. For example, expedition leader is [REPLACED_BY:MAYOR].
REQUIRED_BEDROOM number (0-1000000) The position holder requires a bedroom with at least this value.
REQUIRED_BOXES number (0-100) The position holder requires at least this many boxes.
REQUIRED_CABINETS number (0-100) The position holder requires at least this many cabinets.
REQUIRED_DINING number (0-1000000) The position holder requires a dining room with at least this value.
REQUIRED_OFFICE number (0-1000000) The position holder requires an office with at least this value.
REQUIRED_RACKS number (0-100) The position holder requires at least this many weapon racks.
REQUIRED_STANDS number (0-100) The position holder requires at least this many armour stands.
REQUIRED_TOMB number (0-1000000) The position holder requires a tomb with at least this value.
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.
RESPONSIBILITY responsibility See the table below for the available responsibility tokens. E.g. [RESPONSIBILITY:TAME_EXOTICS]
RULES_FROM_LOCATION Unknown[Verify]
SITE The civilisation will attempt to have this position separate for each site.
SLEEP_PRETENSION The position holder will get upset if someone with a higher precedence holds quarters with a greater value than their own.
SPOUSE singular:plural The name of the position holder's spouse.
SPOUSE_FEMALE singular:plural If the spouse of the creature holding the position is female, this is the spouse's position name.
SPOUSE_MALE singular:plural If the spouse of the creature holding the position is male, this is the spouse's position name.
SQUAD number:singular:plural The position holder will be accompanied by this many whatevers; e.g. for HAMMERER, [SQUAD:10:royal guard:royal guards]
SUCCESSION
  • BY_HEIR / BY_POSITION:position
How a new position holder is chosen.

Responsibilities

Argument Description
ACCOUNTING Found on bookkeeper. Position will keep track of stocks.
ATTACK_ENEMIES Found on elven ranger captain and human warrior. Effect[Verify]
BUILD_MORALE Found on champion. Effect[Verify]
COLLECT_TAXES Found on tax collector. Will collect taxes in further versions, when economics are back.
EQUIPMENT_MANIFESTS Found on arsenal dwarf. Effect[Verify]
ESCORT_TAX_COLLECTOR Found on hammerer. Position will accompiany the COLLECT_TAXES position[Verify]
ESTABLISH_COLONY_TRADE_AGREEMENTS Found on outpost liaison. Position will make trade agreements with the civilisation's colonies.
EXECUTIONS Found on hammerer. Position will deliver beatings for great justice.
HEALTH_MANAGEMENT Found on chief medical dwarf. Enables the z menu health screen. Other effect[Verify]
LAW_ENFORCEMENT Found on sheriff/captain of the guard. Position is in charge of imprisoning criminals.
LAW_MAKING Found on monarch/landholders. Effect[Verify]
MAKE_INTRODUCTIONS Found on diplomat. Effect[Verify]
MAKE_PEACE_AGREEMENTS Found on diplomat. Required for a civilisation to end a war[Verify]
MAKE_TOPIC_AGREEMENTS Found on diplomat. Effect[Verify]
MANAGE_PRODUCTION Found on manager. Position will verify work orders.
MEET_WORKERS Found on expedition leader/mayor. Dwarves want one of these around to complain to[Verify]
MILITARY_GOALS Found on monarch/landholder/leaders. Effect[Verify]
MILITARY_STRATEGY Found on general/militia commander. Effect[Verify]
PATROL_TERRITORY Found on elven ranger captain and human warrior. Effect[Verify]
RECEIVE_DIPLOMATS Found on monarch/landholder/leaders. Position will hold meetings with incoming diplomats/liaisons.
RELIGION Found on elven druid. Possibly it's the one who can tell you information about worship cults[Verify]
SORT_AMMUNITION Found on arsenal dwarf. Effect[Verify]
TAME_EXOTICS Found on dungeon master. Position will tame creatures with the [PET_EXOTIC] token.
TRADE Found on broker. Position will trade at the depot when set to broker only. When applied to other civilizations, the position will arrive with the caravan to make trade agreements.
UPGRADE_SQUAD_EQUIPMENT Found on arsenal dwarf. Effect[Verify]

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:

Token Arguments Description
LAND_HOLDER_TRIGGER
  • land holder number
  • population
  • wealth exported
  • created wealth
Defines when a particular land-holding noble (baron, count, duke in vanilla) will arrive at a fortress.
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 counterintuitive 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 his 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, he will offer to make you an official colony, which will allow you to select all positions for that LAND_HOLDER level. Each time he appears, 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.