Dwarf Fortress Wiki - User contributions [en]

Intro movie

2026-04-16T01:21:36Z

Ziusudra: updated intro to past tense

The '''intro movie''' to ''Dwarf Fortress'' played with old versions when the game was opened, unless it was [[DF2014:Technical_tricks#Intro_Movie|disabled]].

==Opening credits==
First, the [[Bay 12 Games]] logo is displayed. Second, the Bay 12 Games motto (''Beyond Quality'') appears.
In the next scene ''A [[Toady One]] The Great Production'' is pulled across the screen on a wheeled platform by a dwarf.
[[File:intro_movie_1.gif|frame|center]]
{{-}}

==Title==
The camera pans down from a blue sky to the entrance to a dwarven mountainhome. The title ''Slaves to Armok: God of Blood Chapter II: Dwarf Fortress'' appears above the entrance. Dwarves can be seen on the ground, and one enters the mountainhome.
[[File:intro_movie_2.gif|frame|center]]
{{-}}

==Blacksmith==
The camera enters the mountainhome and finds its way to a blacksmith using an anvil and hammer to form a glowing-hot piece of metal.
[[File:intro_movie_3.gif|frame|center]]
{{-}}

==Cavern lake==
The camera then pans to the left and enters a door leading to a bridge that crosses a cavern lake.
[[File:intro_movie_4.gif|frame|center]]
{{-}}

==Sparring dwarves==
The camera enters a door at the end of that bridge and focuses on two dwarves [[sparring]] with adamantine weapons.
[[File:intro_movie_5.gif|frame|center]]
{{-}}

==Miner==
The camera then goes into the door on the left and goes down several tunnels until it comes to a dwarf mining. The miner strikes the wall of the cavern, makes a hole, and loses his pickaxe down said hole.
[[File:intro_movie_6.gif|frame|center]]
{{-}}

==Unspeakable Fun==
The miner looks into the hole and is attacked by [[hell|something]].
[[File:intro_movie_7.gif|frame|center]]
{{-}}

[[Category:Game]]
[[ru:Intro movie]]

Advanced world generation

2026-04-15T02:42:06Z

Ziusudra: /* Interaction between Mesh Size and Weighted Ranges */ added ignore grid size for rectangular world

{{migrated article}}
{{Quality|Superior}}
{{av}}
:''This article contains information on advanced world generation. For information on basic world generation, see [[World generation]].'' ''See [[World token]] to more easily find information by the names used in the world_gen.txt file, [[World rejection]] for information on solving problems related to worlds always being rejected, and [[Worldgen examples]] for example worlds.''

[[File:adv_worldgen_v50.png|thumb|400px|right|The advanced world generation screen. ''(Click to enlarge)'']]'''Advanced world generation''', also labeled as '''detailed mode''', allows substantially more detail-oriented options of customization than standard, basic world generation. This gives the player much more control over how their world is generated. To better understand this article, it is advised that one should read about [[World generation|'''basic world generation''']] first.

The advanced world generation screen is reached by clicking "Create new world" at the main menu, then clicking "Detailed mode". Once at that screen, clicking "Basic options" will return the user to the standard world generation screen.

== Parameter sets ==
There are multiple default sets of all the advanced world generation parameters hard-coded in ''Dwarf Fortress'', which will be overridden by the <tt>prefs/world_gen.txt</tt> file in the main ''Dwarf Fortress'' directory, if it exists. It does not exist by default, you must create it, either by saving the default sets, or saving a copy from the [[world_gen.txt]] wiki page or elsewhere. This file can then be edited with a text editor, and you can copy and paste other players' sets of parameters into it. For sources of such parameter sets see [[Advanced_world_generation#Parameter_set_examples|Parameter set examples]] below.

To get back the default sets, move the existing <tt>prefs/world_gen.txt</tt> to somewhere else (like Documents), or delete it if you do not want to keep the changes, then load the sets in the game, it will then use the hardcoded defaults.

== User interface ==
First, there is a line of text inputs and buttons along the top of the screen, from left to right:
* The drop down menu of currently defined parameter sets, click the down arrow to select a set that you want to work with. The currently selected set can be renamed by clicking the current name or the [[File:Quill.png]] button. The first set in the file is selected by default, usually "LARGE ISLAND". See [[#Parameter set title|Parameter set title]].
* The dimensions of the world for the selected set, see [[#World dimensions|World dimensions]].
* A text entry box to set all of the seed options to the same seed, will show "Random seed", "Various seeds", or, if all four seeds are set to use the same value, that value. See [[Advanced_world_generation#Seed_values|Seed values]] and [[Advanced_world_generation#Seed_values|Seed notes]].
* The Copy Button to make a copy of the currently selected set and appends it to the bottom of the list.
* The red Delete button to delete the currently selected set, you will be prompted to confirm the deletion.
* The New parameter set to create a new parameter set and appends it to the bottom of the list. This seems to just copy the default "LARGE REGION" set.
* The Save button to save all of the current sets to the <tt>prefs/world_gen.txt</tt> file.
* The Load button to load from the same file, there is no confirmation, '''any unsaved changes will be lost'''. If that file does not exist, this resets all of the sets to the defaults.

Most of the middle is the parameters themselves, with a scroll bar to the right. Each row of the list can include:
* The name of the option
* The range of accepted values; not every option has this, and does not always match the displayed value, for example "0 to 1" might show as "No" and "Yes".
:* Sometimes the range might not initially show on rows that it should, reloading the sets with the Load button sometimes fixes that.{{bug|13176}}
* A plus button to increase the value or cycle through options, when applicable (this button will be missing if the range is missing.)
* The current value; can be clicked to edit, to actually set a value you must press {{k|enter}}, without doing that, clicking another entry box or right clicking will instead reset to the currently set value.
* An edit button to show that the previous box is editable, same as clicking on the text box.
* A minus button to decrease the value or cycle through options, when applicable (this button will be missing if the range is missing).
* A red button to disable this parameter, when applicable, usually setting the value to 0, or -1.

{{notice bar|bgcolor=#faa|bordercolor=#f00|All of the buttons below leave this screen and do not prompt to save the sets, so unsaved changes may be lost.}}
At the bottom right are 3 or 4 more buttons:
* The Create world button to do just that using the currently selected set, '''unsaved changes are lost'''.
* The Basic options button to go back to the normal world generation screen, unsaved changes are not lost if you come directly back to Detailed mode.
* The [[Mods]] button to go to the mod selection screen, unsaved changes are not lost if you come directly back to Detailed mode. Only shown if mods are available.
* Back to main menu button to do just that, '''unsaved changes are lost'''.

=== World painter ===
:''Main article: [[World painter]]
The '''world painter''' tool is not in the current version of ''Dwarf Fortress''; it allowed you to paint features onto a map. '''However''', those maps can still be used when generating a world by pasting world painter parameter set maps created in old versions into the <tt>prefs/world_gen.txt</tt> file. [[Utilities#Perfect_World_DF|Perfect World DF]] is a utility that uses the same parameter functionality as the world painter to paint a map, and it also can work with the current version of ''Dwarf Fortress''.

== Generating a world ==
You can either use an already-defined parameter set, or you can edit them, though it is highly suggested to edit a copy of one of the defaults. Once you are happy with the parameters you should save the values you just edited before you click the Create world button. Information about each parameter is documented below.

The phases of the world generation process are (this order is not completely correct):
* Preparing elevation...
* Setting temperature...
* Running rivers...
* Forming lakes and minerals...
* Growing vegetation...
* Verifying terrain...
* Importing wildlife...
* Recounting legends...
* Placing civilizations...
* Making cave civilizations...
* Making cave pops...
* Placing other beasts...
* Placing megabeasts...
* Placing good/evil...
* Placing caves...
* Prehistory generation
* Finalizing civ mats...
* Finalizing art...
* Finalizing uniforms...
* Finalizing sites...

== Seed notes ==
The world generation process uses a PRNG (Pseudo Random Number Generator) algorithm. A PRNG will produce a sequence of numbers that "looks" random, even though the actual sequence of numbers will always be the same if the PRNG is started with the same seed value. Basically this means that if you run world generation with a certain seed value on your computer, and someone else runs world generation with the same seed value on their computer, the same sequence of random numbers will be generated on both computers. The practical impact of this is that someone else can generate exactly the same world that you generated by entering the same seed value that you used.

In the current version, the seed values for the world itself and the names seem to produce the same result, but you will get changes in events which will result in a very different world history.{{bug|6934}} Keep this in mind if you want to regenerate a particular world.

The way that a world is generated can also be affected by certain world tokens. Changing them causes that code to use more or fewer PRNG values, causing later uses to get different parts of the sequence. So, you cannot for example, change the minimum and maximum rainfall and get 'the same world but drier or wetter', instead, a different world is generated. That said, it would also seem that certain small changes to these world tokens can occasionally generate a very similar world, however, other tokens are more sensitive. For more information see the forum thread [http://www.bay12forums.com/smf/index.php?topic=112132.msg3404199#msg3404199 here].

The following are tokens which use the PRNG values in ways that changing them will likely cause broader changes:

* [DIM:X:X]
* [ELEVATION:X:X:X:X]
* [RAINFALL:X:X:X:X]
* [TEMPERATURE:X:X:X:X]
* [DRAINAGE:X:X:X:X]
* [VOLCANISM:X:X:X:X]
* [SAVAGERY:X:X:X:X]
* [ELEVATION_FREQUENCY:X:X:X:X:X:X]
* [RAIN_FREQUENCY:X:X:X:X:X:X]
* [DRAINAGE_FREQUENCY:X:X:X:X:X:X]
* [TEMPERATURE_FREQUENCY:X:X:X:X:X:X]
* [SAVAGERY_FREQUENCY:X:X:X:X:X:X]
* [VOLCANISM_FREQUENCY:X:X:X:X:X:X]
* [PARTIAL_OCEAN_EDGE_MIN:X]
* [COMPLETE_OCEAN_EDGE_MIN:X]
* [HAVE_BOTTOM_LAYER_1:X]
* [MINERAL_SCARCITY:X] {{cite talk/this|Mineral scarcity}}

Many other world parameters, such as end year and embark points, can, however, be changed without it having any effect on the geography of the world generated from the seed values.

Normally, you don't enter these seed values, the game comes up with values based on some other sort of pseudo-random information from things like the current date and time.

When generating a world, ''Dwarf Fortress'' records the seeds it used in [[gamelog.txt]]; they can also be found with <code>gui/gm-editor world.worldgen.worldgen_parms</code> in [[DFHack]].

== Advanced parameters ==
There are essentially 4 types of controls for the generation of the surface map;

'''Terrain parameters''': as described below, these 5 variables define the basic background world, how hot or cold it is, how much rainfall, how high the mountains are. The world automatically goes through the temperature range along the Y axis, although sometimes it will be hotter in the north, other times in the south, or cold at both. Minimum, maximum and X,Y variance can drastically alter the world.

'''Weighted meshes''': these are a way to fine-tune the amount of the 5 basic variables on the map. They can be used to set the specific distribution of different elevations or rainfall areas for example.

'''Feature parameters''': such as rivers, mountain peaks, volcanoes, and oceans, which can cause rejections if the terrain parameters don't allow enough suitable locations for the features to be placed.

'''Rejection parameters''': ''Dwarf Fortress'' uses a 'belt-and-braces' approach to world generation. The above controls allow you to shape the world, then the rejection parameters throw it out if it does not meet certain criteria. There are a number of rejection parameters for the number and degree of the 5 basic variables, for biome types, etc. If the world does not meet the requirements of any one rejection parameter the world is rejected and re-randomised. Also see [[World rejection]].

Leaving tokens out of a set in <tt>world_gen.txt</tt> will cause the game to use default values which are not adjusted for smaller world sizes, this may cause smaller worlds to always be rejected.

If you are experimenting with world design, there is also a [[Settings#Feature_toggles|game setting]] that will log the rejection reasons to ``[[map_rejection_log.txt]]``. With that information you can then either adjust the rejection parameters to allow those worlds, or the other parameters to prevent them from trying to generate. ''Dwarf Fortress'' will keep adding to the file, so you may want to trim or delete it occasionally.

The parameters are described below in the order that they appear in the list in the game, which is not necessarily the order they appear in <tt>world_gen.txt</tt>. See [[world token]] for an index that will help you look things up by token name. The tokens used in <tt>world_gen.txt</tt> are at the bottom of each of the following parameter descriptions.

=== Parameter set title ===
This sets the name of the parameter set itself, as used in the list of sets (this has nothing to do with the name of the generated world).
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITLE:<name>]</nowiki></tt>
| <tt><nowiki>[TITLE:MEDIUM ISLAND]</nowiki></tt>
| Required
|}

=== World dimensions ===
The size of the map for the current set can be changed by changing the Width and Height values at the top next to the set title. You will need to confirm this, since changing the dimensions of the world will change other parameters, because many of them have different defaults depending on the surface area available.

Larger maps usually take longer to generate and may reduce [[Frames per second|FPS]] in-game, though this is really a matter of larger worlds usually having more civilizations, sites, historical figures, and events; restricting the number of those can speed up the process. Non-square maps may result in crashes{{bug|2928}}.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DIM:<width>:<height>]</nowiki></tt>
| <tt><nowiki>[DIM:257:257]</nowiki></tt>
| Valid values are 17, 33, 65, 129, and 257, other values will use one of those. Changing the size in the file without adjusting other parameters can cause many rejections.
|}

=== Seed values ===
Enables the use of, and specifies seed values for, different parts of the world generation process. Just entering a specific seed does not enable it, that must be done separately, although using the box at the top to set all the seeds to the same value does enable them all. Enabling a seed puts the token in using what ever is in the text box below. If you enable a seed, but do not enter a seed, the string "Seed text" will be used (<tt><nowiki>[SEED:Seed text]</nowiki></tt>). Trying to use a <tt><nowiki>]</nowiki></tt> in the string in the file will end the seed there, since it closes the token, any text after that will be ignored. Normally, just leave these set to Random, unless trying to reproduce the results of a previous world generation. See also the [[Advanced_world_generation#Seed_notes|seed notes section]] above.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEED:<text>]</nowiki></tt>
| <tt><nowiki>[SEED:31337]</nowiki></tt>
| rowspan="4" |
For each of these not in the config file, a random seed will be used, and the first seed is not used to generate the others. The seeds used are output to [[gamelog.txt]] when world generation starts.
|-
| <tt><nowiki>[HISTORY_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[HISTORY_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[NAME_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[NAME_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[CREATURE_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[CREATURE_SEED:31337]</nowiki></tt>
|}

=== World name ===
As previously mentioned, the title of the parameter set doesn't affect the name of the world. You can specify a particular name for your world, or leave the value blank for a random one. (The [[DFHack]] utility adds an option to rename the world using the in-game languages.)
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CUSTOM_NAME:<name>]</nowiki></tt>
| <tt><nowiki>[CUSTOM_NAME:Realm of Cheese Engravings]</nowiki></tt>
| For a random name, simply don't use this token.
|}

=== Embark Points ===
The number of points for equipment and animals when embarking in fortress mode (there is no equivalent setting for adventure mode). Normally, the default of 1504 is fine, but can be increased for various purposes like experimentation or to help dwarves survive in a particularly evil world, or reduced for certain [[challenges]].
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EMBARK_POINTS:<number>]</nowiki></tt>
| <tt><nowiki>[EMBARK_POINTS:1504]</nowiki></tt>
| 0 to 10,000
|}

=== End year ===
The maximum number of years generated for the world, although generation can be paused and the world used as is any time after the second year; the same as the [[World_generation#History|History]] parameter in basic world gen, except that you can enter an exact value. A too-short history can limit the materials available to civilizations, and [[Chosen|certain adventure mode features]] are only available after certain site events, while too long a history often leads to civilizations dying.

For more information on the history aspect of the game, see [[Legends]] and [[Calendar#Ages|Ages]].
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[END_YEAR:<number>]</nowiki></tt>
| <tt><nowiki>[END_YEAR:250]</nowiki></tt>
| 2 to 10,000
|}

=== Population cap after civ creation ===
A soft limit to the total number of [[historical figure]]s alive at the same time during generation across all civilizations, only preventing the birth of new historical figures.{{cite forum|140544/5701667}} Each civilization is allotted a percentage of the total by the percentage of sites they control.{{cite forum|159164/7553641}} Civilizations also have non-historical populations, and there is no setting to limit those (in early versions, all civilization members were historical figures, this is also why the name of this setting is misleading). Each [[entity]] also has limits from their raws, see the [[Entity_token#Population|population]] entity tokens, and setting this to unlimited will not remove those.

Huge historical figure populations can slow generation and the game in general.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_POPULATION:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_POPULATION:15000]</nowiki></tt>
| -1 to 100,000, -1 is no limit
|}

=== Site cap after civ creation ===
Total number of [[site]]s that can be directly created by all civilizations combined like [[hillocks]], [[hamlet]]s, [[dark pits]], [[forest retreat]]s, etc. Does not prevent the placement of initial civilization sites, though they will then be counted for the limit. Does not affect creature sites like [[cave]]s or [[lair]]s, group sites like [[castle]]s, [[monastery|monasteries]], [[tower_(necromancy)|tower]]s, [[fort]]s, or [[camp]]s, or unpopulated sites like [[tomb]]s. After this limit is reached, no civilization will be able to place new sites. See the [[Entity_token#Placement|placement]] entity tokens for other ways that civilization site placement can be limited.

Increasing this will slow generation down and reduce the available places for player sites. Since the {{token|MAX_SITE_POP_NUMBER|entity}} entity token limits the historical figure population per site, this site cap can also limit the total historical figure population of all civilizations combined, and some expand faster than others getting more sites before the limit is reached.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SITE_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SITE_CAP:1500]</nowiki></tt>
| -1 to 100,000, -1 is no limit
|}

=== Beast control ===

These parameters don't usually matter too much, but may matter for small numbers of beasts.

==== Percentage of Megabeasts and Titans Dead for Stoppage ====

The world starts out with a certain number of powerful megabeast and titan entities in existence. If a percentage of the megabeast and titan population dies out during history generation, then history generation will stop early. For example, if the elimination value is 80%, and the generated history starts with 200 entities and 160 of those 200 entities are eliminated by historical events before the End Year is reached, history generation will stop immediately.

If you want to end the creation of your world at the beginning of a certain age, choose the following values:
* Age of Legends: ~34%
* Age of Heroes: ~67%
If there are three or fewer titans or megabeasts in your world, the age will be given a special name reflecting the remaining megabeasts/titans, instead.

==== Year to Begin Checking Megabeast Percentage ====

The percentage of dead [[megabeast]]s and [[titan]]s for stoppage will not be checked until this year is reached in history generation. This can be used to ensure that a world reaches a certain year even if all of the megabeasts in the world are slain earlier.

If the number of living [[megabeast]]s and [[titan]]s starts at or drops to less than four, then world generation will always stop if the current year is equal to or greater than the Year to Begin Checking Megabeast Percentage ''regardless'' of how many [[megabeast]]s and [[titan]]s are dead — Percentage of Megabeasts and Titans Dead for Stoppage is ignored. The number of megabeasts and titans at the start of the world is set by the sum of the [[Advanced_world_generation#Max_Megabeasts_Caves|Max Megabeasts Caves]] and [[Advanced_world_generation#Titan_Parameters|Titan Number]] parameters.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[BEAST_END_YEAR:<year>:<percentage or -1>]</nowiki></tt>
| <tt><nowiki>[BEAST_END_YEAR:200:80]</nowiki></tt>
| Use -1 as percentage to disable. Year must still be at least 2.
|}

=== Cull Unimportant Historical Figures ===
{{main|Historical figure}}
Whether to remove unimportant dead historical figures after history generation; a short CPU-intensive step, but saves space which can speed up loading, saving, and running games with large histories. Legends mode will refer to culled creatures as "an unknown creature", and they will not appear in engravings, but likely would not have anyway.

Exactly what is considered important is not clear. A member of an abstract group killing a named creature is not. Creating an artifact is not, even if that artifact had important history. Unculled historical figures can have parentage described as "The identity of" that parent "has been lost to time", so just having children is not, though having living direct relations seems to prevent culling.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CULL_HISTORICAL_FIGURES:<0 or 1>]</nowiki></tt>
| <tt><nowiki>[CULL_HISTORICAL_FIGURES:0]</nowiki></tt>
| 0 = No, 1 = Yes
|}

=== Reveal All Historical Events ===

Setting this to Yes will allow access to most information about the history of the world in [[Legends mode]]. All events will be revealed, but some [[historical figure]]s, [[site]]s, [[region]]s, and [[civilization]]s and other entities may not be, possibly because they are not known to any civilization. If set to No, then you will have to discover historical information in [[adventure mode]] or by instructing dwarves to make engravings.{{Verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[REVEAL_ALL_HISTORY:<0 or 1>]</nowiki></tt>
| <tt><nowiki>[REVEAL_ALL_HISTORY::1]</nowiki></tt>
| 0 = No, 1 = Yes
|}

=== Terrain Parameters ===

These set limits and variance for terrain elevation, rainfall, temperature, drainage, volcanism, and savagery which determines how those values are generated. What biomes exist are then determined by how these factors overlap with each other.

==== Minima and Maxima ====
These are the absolute minimum and maximum values that can ever be generated for a particular map square characteristic. By ''subtly'' tweaking the min and max values, vastly different maps can be made. Changing these can cause the occurrence of certain [[Biome|biomes]] to become impossible, so you may want to use [[#Terrain Mesh Sizes and Weights|Weighted Ranges]] instead.

==== X and Y Variance ====
These control how wildly things like elevation and rainfall can vary between adjacent map squares. For example, if these values are set to the maximum of 3,200 for elevation then you will end up with more very low areas right next to very high areas. The number for X determines the east-west variance and the number for Y determines the north-south variance. By setting only one of these to a high value you can, for example, create horizontal or vertical bands of areas which are more similar to each other.

Generally speaking, raising both of these values will create a more random "patchwork" of many small biomes while setting both x and y values to 0 will cause every square on the map to use a single random value for the given characteristic.

For "patchwork" worlds to avoid being rejected, [[#Maximum Number of Subregions|Maximum Number of Subregions]] will probably need to be increased from the default.

==== Elevation ====
This controls the range of terrain elevations that can occur in the world. Usually, you just want to leave the min/max values alone. Raising the minimum elevation can, for example, make it impossible for oceans to exist. This does '''not''' directly control the number of available Z-levels at a particular site, though high maximum values may contribute to peaks, which can raise the number of above ground Z-levels - in other words, a maximum elevation of 400 and minimum of 1 does not mean you get 400 Z-levels, but it might increase the number of Z-levels somewhat in some regions compared to others. Raising the variance will result in a more bumpy, uneven landscape.

Some biomes/features that are impacted by elevation:
* A high minimum (above 99) means no oceans, as they need elevations below 100.
* A low maximum (below 300) means no mountains, as mountains need elevations above 300.
* Rivers will be placed when the elevation maximum is 104 or higher. Therefore, keeping both values above 100 and below 104 will prevent all water tiles from appearing.
* Mountain peaks can only form at elevations of 400.

==== Rainfall ====
Controls the amount of rainfall in each map square/area. Setting the minimum or maximum too high or low can make the formation of certain biomes impossible. Rainfall causes it to [[rain]] more in a given area, which can have various effects. Also makes more rivers appear on the world map.

Note that if [[#Do Orographic Precipitation and Rain Shadows|orographic precipitation and rain shadows]] is on, then mountains will cause additional variance in rainfall, so (for example) rainfall below the specified minimum can occur in the shadow of a mountain. If you want the minimum and maximum for this parameter to be absolutely respected, you must turn off the orographic precipitation option.

Additionally, with 'Orthographic Precipitation' turned on, orthographic precipitation and rain shadows will only occur in regions with greater than or equal to 50 drainage. [http://www.bay12forums.com/smf/index.php?topic=139916.0 [Report, reproduced 2022]]

==== Temperature ====
{{main|Climate|Temperature}}
These parameters control how hot or cold various areas will be. If you lower the minimum and maximum values, the world will be colder overall, for example. As with the others, changing these values too much could make it impossible for certain biomes to exist. The temperature scale used in this setting is related to regular degrees Urist by the equation "local temp = world temp * 0.75 + 10000".{{cite forum|169696/8395484}} This scale doesn't seem to be used anywhere else in the game. See [[Climate]] for more info.

These parameters form the "base" temperature for an area, and describe peak summer temperature in a scale that isn't used elsewhere in the game. This number also does not correspond 1:1 with the final climate. [[Temperature]] is always influenced by a number of variables, including elevation, time of year, thick forestation, and if [[Advanced_world_generation#Poles|poles]] are enabled, latitude. These other variables are factored in after the temperature mesh is applied, and frequently bring temperatures above and below their set minimum and maximum values. ''The inclusion of Poles is particularly strong in this regard, as it allows latitude to raise and/or lower temperatures by more than 75 degrees Celsius! That said, the temperatures aren't raised or lowered by more than about 65 degrees past the set minimum and maximum. Furthermore, for typical ranges, the temperature will never be raised more than about 25 degrees past the maximum (but will still drop up to about 65 degrees Celsius below the minimum).'' (unsure about exact values, research needed)

Elves can spawn where the temperature is 10 degrees or warmer, and humans can spawn where the temperature is 0 degrees or warmer.

==== Drainage ====
Changing drainage parameters will change the way water-affected biomes are formed. Low drainage will contribute to the formation of [[Lake|lakes]], [[River|rivers]], and [[Swamp|swamps]]. High drainage will cause water to sink into the ground rather than sit on the surface, which is important for forming hills.

Lower drainage values have been reported to contribute to the formation of thicker soil layers, though it is currently unknown exactly how other factors (such as elevation or perhaps rain) impact soil formation.

==== Volcanism ====
Volcanism controls the occurrence of igneous [[layer]]s, and the formation of volcanoes. For a volcano to form, a square must have a volcanism value of 100, so reducing the maximum from 100 will make volcanoes impossible. Raising the minimum will increase the rarity of non-igneous layers.

Setting the minimum to a high value is not a good way to produce multiple volcanoes, as you are likely to get a "Volcanism not evenly distributed" rejection. Instead, use the Minimum Number of Volcanoes parameter, and possibly adjust the weighted ranges for volcanism as described below.

==== Savagery ====
These parameters control the level of [[Surroundings#Savage|savagery]] on the map. Raising the minimum savagery too high may make it impossible for certain races to exist, and similarly lowering the maximum too far can make it impossible for certain creatures to exist. The largest chance of having unusable maps comes from a too-high savagery value.

==== Configuration Tokens ====
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[ELEVATION:1:400:401:401]</nowiki></tt>
| Range: 0 to 400 Maximum of 400 required for mountain peaks. Variance range: 0-3200
|-
| <tt><nowiki>[RAINFALL:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[RAINFALL:0:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|-
| <tt><nowiki>[TEMPERATURE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE:25:75:200:200]</nowiki></tt>
| Range: -1000 to 1000 Variance range: 0-3200
|-
| <tt><nowiki>[DRAINAGE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE:0:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|-
| <tt><nowiki>[VOLCANISM:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM:1:100:200:200]</nowiki></tt>
| Range: 0 to 100 Maximum of 100 required for volcanoes. Variance range: 0-3200
|-
| <tt><nowiki>[SAVAGERY:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY:1:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|}

=== Terrain Mesh Sizes and Range Weights ===
[[File:World_map-large-32x32-elevation-mesh.png|thumb|300px|A large world generated with an Elevation Mesh Size of 32×32 and range weights set to 1:0:0:0:1 (i.e., only extreme high and low elevations). Note how the grid intersections are either set very high (mountains) or very low (oceans) and the space between them is smoothed out.]]
These parameters influence the relative proportions of terrain feature ranges, without making other ranges impossible. For example, to have many more low-elevation squares exist, without making it impossible for high elevations; this makes changing these parameters often preferable to simply changing the above min/max values. See the image on the right for an example.

The basic steps of applying weighted ranges are as follows:
# Divide the world into a grid of quantity <code>2''MeshSize'' - 1</code> areas in both X and Y direction.
# At each grid intersection, set the value according to the weighted ranges.
# Smooth out the areas between the intersection points.
# Add noise according to the variance parameters.
Where ''MeshSize'' is the raw parameter value found in the <code>[[world_gen.txt]]</code>.

==== Interaction between Mesh Size and Weighted Ranges ====
Mesh size determines how many intersection points the world will have. As an example, setting it to 2×2 means the world will be divided into 4 areas, 2 across and 2 tall, and there will be a total of 9 intersection points (3×3), including the outer-most corners. The grid intersection points are in the middle of world tiles, and the minimum size for a grid area is a span of 9 world tiles in either direction, with adjacent areas sharing an overlapping world tile. On a pocket world, this means one grid tile will span 9×9 world tiles, whereas on a large world, one grid tile will span 129×129 world tiles. A pocket world will always use a 2×2 grid of 9×9 world tiles, since it has only 17×17 tiles total (even if the game UI allows setting those worlds to a 4×4 grid, which can happen when changing the world size; changing the world size doesn't adjust mesh size limits, but saving then reloading the parameters does). A world that is 17 tiles wide, but 257 tall, and set to a 32×32 mesh size, will have 3×33 intersection points.

Setting mesh size to something other than Ignore, will apply random values at those intersections, with those random values being more likely to be in the ranges with higher weights. Setting to Ignore will cause the weighted range settings to be ignored for that terrain characteristic; instead setting the 4 corners of the world to completely random values and smoothing between those, or in other words, using a 1×1 grid for square worlds; while for rectangular worlds, using the same ratio as the world dimensions with 1 in the narrow dimension (for example, a 1×16 grid for a 17×257 world).

For example, if the Elevation Weighted Range parameters are set to <code>60:10:10:10:10</code> (starting with the 0-20 range, and these values do not need to add up to any particular number), and elevation min and max are left at the defaults of 1 and 400 respectively, then about 60% (on average) of the grid line intersection points will be set to an elevation in the range of 1-80 (0% to 20%), and the other ranges will be represented by around 10% of the intersection points each. The exact distribution is still left up to chance, though ''on average'' it will be close to this specification. This allows random number generation to be non-linear for the given terrain characteristic.

Setting the weight for a range to None only prevents intersection points from being set to a value in that range; terrain between intersection points can still be smoothed to values in ranges set to None that are between the intersection point values. Setting all the weights to None just puts them all at the same weight, the same as the default of all at 1.

Weighted ranges do not make rejection checks, although they can be responsible for many rejections if you neglect to adjust or disable some of the [[#Minimum Number of Mid/Low/High Characteristic Squares|Minimum Number of Mid/Low/High Characteristic Squares]], for example.

==== Interaction between these and Variances ====
The end result can vary greatly depending on how the corresponding [[#X_and_Y_Variance|X and Y Variance]] parameters are set. First of all, if the variance is too high, the noise it adds can completely negate the effect of the weighted ranges. For instance, with a 2×2 mesh, the default variance parameters are high enough that usually the mesh grid can hardly be recognized. How strong the variance's effect is, is also dependent on the mesh size. Having a larger mesh size (i.e. smaller grid tiles) means the variance also has to be higher for a visible effect. For instance, with a variance of 400, the effects are clearly visible with a 2×2 mesh and barely visible at all with a 8×8 mesh. Note that this effect is directly dependent on the mesh size and not, as one might expect, on the actual size of the grid tiles. This means, that a large world with a 32×32 mesh will look essentially the same as a pocket world with a 2×2 mesh, only stretched to 256 times the size.

Also see this [http://www.bay12forums.com/smf/index.php?topic=139916.0 forum post] for more details.

==== Configuration Tokens ====
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[ELEVATION_FREQUENCY:2:1:2:3:4:5]</nowiki></tt>
| rowspan="6" | Valid mesh values:

1 = Ignore

2 = 2x2

3 = 4x4

4 = 8x8

5 = 16x16

6 = 32x32

(limited by world size)
|-
| <tt><nowiki>[RAIN_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[RAIN_FREQUENCY:3:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[DRAINAGE_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE_FREQUENCY:4:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[TEMPERATURE_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE_FREQUENCY:1:1:1:1:1:1]</nowiki></tt>
|-
| <tt><nowiki>[SAVAGERY_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY_FREQUENCY:5:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[VOLCANISM_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM_FREQUENCY:1:1:1:1:1:1]</nowiki></tt>
|}

=== Poles ===

With this, you can influence how polar regions are added. The poles can be on the north or south edge, and the equator will be on the opposite edge, or in the middle if there are two poles. If poles are set to NONE, then there will be no seasonal changes in the weather (e.g. no winter snow in temperate biomes).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[POLE:<placement>]</nowiki></tt>
| <tt><nowiki>[POLE:NORTH]</nowiki></tt>
| Viable options: NONE, NORTH_OR_SOUTH, NORTH_AND_OR_SOUTH, NORTH, SOUTH, NORTH_AND_SOUTH
|}

=== Minimum Mountain Peak Number ===

This will cause the world to be rejected if fewer than this many peaks (based on elevation) are present on the map. EG: elevations of 400 must be possible for mountain peaks to occur. If set to zero, then worlds will not be rejected based on number of peaks.

You may need to adjust elevation parameters, such as the highest weighted range, in order to get the desired number of elevation-400 squares needed for larger numbers of peaks. Like volcanoes, mountain peaks can make embark zones more interesting, but other than that, they don't appear to "do" anything special. Reportedly, they do increase the highest Z-level above ground in all embark zones in the same region, even if the selected embark zone does not include the peak.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PEAK_NUMBER_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[PEAK_NUMBER_MIN:20]</nowiki></tt>
| Elevations of 400 must occur for peaks to form.
|}

=== Minimum Partial Edge Oceans ===

This will cause a world to be rejected unless there are at least this many oceans touching an edge of the map. If set to zero then worlds will not be rejected based on this criterion. Setting both this parameter and Minimum Complete Edge Oceans to values that total more than 4 when added together may cause all worlds to be rejected as you can't have both a partial and complete edge ocean on a given edge.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PARTIAL_OCEAN_EDGE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[PARTIAL_OCEAN_EDGE_MIN:2]</nowiki></tt>
| Maximum of 4
|}

=== Minimum Complete Edge Oceans ===

This will cause a world to be rejected unless there are at least this many oceans which completely cover an edge of the map. Since a square map only has 4 edges, the maximum value possible is 4. If set to zero then worlds will not be rejected based on this criterion but still might end up with complete edge oceans by chance.

Note that the ability for this many edge oceans to exist will be limited by elevation. Therefore, to actually create large oceans you will probably need to change things like the Elevation Mesh Size and Weighted Ranges to increase the number and distribution of very low elevation squares on the map. In addition, if Complete Edge Oceans is set to any value ''other'' than 0 or 4, you may need to lower elevation variance for at least one of the axes: if set too high, such as a variation of 1600 for both X and Y axes (the default for Large Island and Medium Island parameter sets), the game may generate worlds very slowly or even hang.{{bug|565}}

Given appropriate weight, range, and variance values for things like elevation, a setting of: 1 results in a world that seems like a chunk of coastline. One edge of the map will be completely underwater and there will be ocean taking up much of the map on that side (think the east or west coast of the United States, the north coast of Canada, or southern Europe). If your edge ocean happens to pick your world's frozen side, most of it will be glacier.

*2 results in another coastline along with the first one -- the map could end up looking something like Panama if the oceans pick opposite sides of the map.
*3 results in a peninsula, like Florida in the US. There will be oceans surrounding 3 sides of the map, and land touching only one side of the map.
*4 results in one or more island(s) depending on things like elevation variance and weights. Regardless of whether you get one island or multiple islands, the entire map will be surrounded by water.

Unfortunately, there's no easy way to control which oceans end up on which edges, except perhaps setting X/Y variance to different values.

Edge oceans will take up part of the other edges too. For example, a full edge ocean on the east side will have part of the north and south sides underwater, but that does ''not'' add to the ''partial'' edge oceans count.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[COMPLETE_OCEAN_EDGE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[COMPLETE_OCEAN_EDGE_MIN:0]</nowiki></tt>
| Maximum of 4
|}

=== Minimum Volcano Number ===

The game will attempt to place this many volcanoes, but there must be at least this many squares with a volcanism of 100, if there are not the world will be rejected. Therefore, [[Advanced_world_generation#Volcanism|maximum volcanism]] above must be set to 100, and adjusting the [[Advanced_world_generation#Configuration_Tokens_2|volcanism weighted range]] above for 80-100 to a higher value can increase the number of those squares.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[VOLCANO_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[VOLCANO_MIN:15]</nowiki></tt>
| Volcanoes require a volcanism of 100 to occur.
|}

=== Mineral Scarcity ===
Controls the frequency at which minerals occur; setting this value higher will decrease both the number of different types and amounts of ore and gems present on a map. The default value will result in many metal ores, while the old default of ''sparse'' would be only a few ores, which may be limiting until other metals can be requested and traded for.

The options "Very Rare", "Rare", "Sparse", "Frequent", and "Everywhere" in the [[World_generation#Basic_world_generation_menu|basic world generation menu]] use the values 50000, 10000, 2500, 500 and 100 respectively.

According to [http://www.bay12forums.com/smf/index.php?topic=79018.msg2063804#msg2063804 research] by Shandra in v0.31.25, this is the relationship between the value of this setting and the approximate number of gems and ore:

[[File:MineralSetting_v25_limit10k.png]]

This is for the same 8x8 embark region in a world which is otherwise the same, except for the mineral scarcity parameter (although most of the detailed information comes from experiments with previous versions). (The chart legend has an error, the first "Pot.(Types)" should read "Pot.(Amount)".)
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MINERAL_SCARCITY:<number>]</nowiki></tt>
| <tt><nowiki>[MINERAL_SCARCITY:100]</nowiki></tt>
| Range: 100 to 100,000
|}

=== Max Megabeast Caves ===

This is the number of [[megabeast]]s placed at the beginning of history. Megabeasts are [[hydra]]s, [[bronze colossus]]es, [[roc]]s, and [[dragon]]s, which are all placed in equal proportions [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415177#msg3415177 data].

Increasing this value can lead to early extinction of civilizations.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[MEGABEAST_CAP:75]</nowiki></tt>
| Megabeasts count towards BEAST_END_YEAR calculation.
|}

=== Max Semi-Megabeast Caves ===

This is the number of [[semi-megabeast]]s placed at the beginning of history. Semimegabeasts are [[giant]]s, [[ettin]]s, [[minotaur]]s, and [[cyclops]], which are placed in equal proportions [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415188#msg3415188 data].

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEMIMEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SEMIMEGABEAST_CAP:150]</nowiki></tt>
| Semimegabeasts do not count towards the BEAST_END_YEAR calculation.
|}

=== Titan Parameters ===

==== Number ====

This controls the number of [[titan]]s that exist at the beginning of history[http://www.bay12forums.com/smf/index.php?topic=112465.msg3415203#msg3415203 data]. The number of forgotten beasts is unaffected by this parameter [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415155#msg3415155 data].

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TITAN_NUMBER:33]</nowiki></tt>
| Titans count towards BEAST_END_YEAR calculation.
|}

==== Attack Population Requirement ====

[[Titan]]s will begin to attack your fort once at least this many dwarves inhabit it, regardless of whether any other attack criteria have been met.

This number defaults to 80, which isn't usually too difficult to deal with.

==== Exported Wealth Requirement ====

Titans will begin to attack your fort once you have exported at least this many [[Currency|dwarfbucks]]-worth of goods, regardless of whether or not any other criteria have been met. This parameter defaults to None (disabled).

==== Created Wealth Requirement ====

Titans will begin to attack your fort once the fort's total wealth has reached this many [[Currency|dwarfbucks]] in value. This happens regardless of whether any of the other criteria, such as population, have been met; therefore, even with 1 dwarf, a fort could be attacked if the fort were worth at least this value.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_ATTACK_TRIGGER:<population>:<exp wealth>:<created wealth>]</nowiki></tt>
| <tt><nowiki>[TITAN_ATTACK_TRIGGER:80:0:100000]</nowiki></tt>
| 0 = None (disabled). Only one requirement must be met for an attack.
|}

=== Number of Demon Types ===

[[Demon]]s are similar to [[titan]]s and [[forgotten beast]]s, in that they are procedurally generated, but most are not unique. Thus, many different types of demons can exist in the world, but there will also be many individuals of most types. Thanks to [[Underworld spire|certain fun things]], fewer demon types also means fewer goblin civilizations.{{cite forum|112465/7392706}} You need at least 2 demon types, or else goblin civilizations won't exist initially, though if dwarves breach the underworld during world generation, at least one will be generated then.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DEMON_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[DEMON_NUMBER:52]</nowiki></tt>
| 0 to 1000
|}

=== Number of Night Troll Types ===

The number of different [[night troll]]s, also procedurally generated, that will exist in the world. Setting this to zero means that the world will have no night trolls, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[NIGHT_TROLL_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[NIGHT_TROLL_NUMBER:77]</nowiki></tt>
| 0 to 1000
|}

=== Number of Bogeyman Types ===
The number of different [[bogeyman]] forms that will exist in the world. Bogeymen are procedurally generated, though their forms do not vary by much. Setting this to zero means that the world will have no bogeymen, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[BOGEYMAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[BOGEYMAN_NUMBER:27]</nowiki></tt>
| 0 to 1000
|}

=== Number of Nightmare Types ===
The number of different [[nightmare]] forms that will exist in the world. Nightmares are procedurally generated. Setting this to zero means that the world will have no nightmares, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[NIGHTMARE_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[NIGHTMARE_NUMBER:27]</nowiki></tt>
| 0 to 1000
|}

=== Number of Vampire Curse Types ===

The number of different types of [[Vampire|vampires]] that will exist in the world. Although they are generated at the start of a new world, they aren't different from each other. Setting this to zero means no vampires will exist.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[VAMPIRE_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[VAMPIRE_NUMBER:72]</nowiki></tt>
| 0 to 1000
|}

=== Werebeast Parameters ===

==== Number of Werebeast Curse Types====

The number of different types of [[werebeast]]s that can exist in the world. It is common for werebeasts, unlike vampires, to assume many different forms and variations, the most well-known of these amount to different species of animals, from lizards, to wolves, to even bears. Setting this to zero means no werebeasts will exist, and will also remove a large amount of [[fun]] from the game.

In vanilla, there are only 82 possible unique werebeast species. Any further species will generate as wereblobs.{{bug|13308}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[WEREBEAST_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[WEREBEAST_NUMBER:58]</nowiki></tt>
| 0 to 1000
|}

==== Attack Population Requirement ====

Werebeasts will begin to attack your fort once at least this many dwarves inhabit it, regardless of whether any other attack criteria have been met. This number defaults to 50 which will often be reached in the second year of the fort.

==== Exported Wealth Requirement ====
Werebeasts will begin to attack your fort once you have exported at least this many [[Currency|dwarfbucks]]-worth of goods, regardless of whether or not any other criteria have been met. This parameter defaults to 5000.

==== Created Wealth Requirement ====

Werebeasts will begin to attack your fort once the fort's total wealth has reached this many [[Currency|dwarfbucks]] in value. This happens regardless of whether any of the other criteria, such as population, have been met; therefore, even with 1 dwarf, a fort could be attacked if the fort were worth at least this value.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[WEREBEAST_ATTACK_TRIGGER:<population>:<exp wealth>:<created wealth>]</nowiki></tt>
| <tt><nowiki>[WEREBEAST_ATTACK_TRIGGER:50:5000:50000]</nowiki></tt>
| 0 = None (disabled). Only one requirement must be met for an attack.
|}

=== Number of Secret Types ===

The number of secrets that exist in the world. Currently, all secrets are secrets of life and death, and the ones holding these secrets are [[necromancer]]s, thus, setting this to zero means that no necromancers will appear.
Non-necromancer towers can still appear (extremely rarely) with zero secrets, constructed by independent undead groups.
The primary difference between having 1 or 1000 secrets is the chance of your world having any necromancer towers at all. With 1, this chance is low. With the default number, it's seemingly guaranteed.
Even with 1 secret, if you have any necromancer towers at all, it is likely a great number will quickly appear in world generation (though this isn't guaranteed).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SECRET_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[SECRET_NUMBER:52]</nowiki></tt>
| 0 to 1000
|}

=== Number of Regional Interaction Types ===

The number of interactions that can be caused in regions, which may incorporate evil rain and cloud types. Currently, only evil region interactions are generated this way.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[REGIONAL_INTERACTION_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[REGIONAL_INTERACTION_NUMBER:20]</nowiki></tt>
| 0 to 1000
|}

=== Number of Disturbance Interaction Types ===
The number of different [[Mummy|disturbed dead]] that can exist in the world. Setting this to zero should prevent any mummy from appearing{{verify}}, but it will not prevent the creation of [[tomb]]s.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DISTURBANCE_INTERACTION_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[DISTURBANCE_INTERACTION_NUMBER:10]</nowiki></tt>
| 0 to 1000
|}

=== Number of Evil Cloud / Evil Rain Types ===

This number specifies how many [[Weather#Evil weather|various face-melting, eye-boiling, and zombifyingly-fun]] clouds of pure evil may appear in your world. Setting this to zero means you no longer will ever have to deal with encroaching dust walls of doom in that world. It is generally advised to keep this value low...

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EVIL_CLOUD_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[EVIL_CLOUD_NUMBER:45]</nowiki></tt>
| 0 to 1000
|}

The latter number states how many different types of green-ooze drenchers, disconcerting blood-showers, and sickly yellow slime-baths can occur in your world. Compared to evil clouds though, this one hardly is worth stressing out about, usually.... Setting this to zero means the only semi-solid to fully-liquid fluids to fall from the sky will be pure H2O.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EVIL_RAIN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[EVIL_RAIN_NUMBER:352]</nowiki></tt>
| 0 to 1000
|}

=== Generate Divine Materials ===
This turns the generation of [[Divine_metal|divine metals]] on or off. It does not influence the creation of [[vault]]s. Probably determines whenever or not using divination dice spawns weapons.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GENERATE_DIVINE_MATERIALS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[GENERATE_DIVINE_MATERIALS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Generate Mythical Materials ===

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GENERATE_MYTHICAL_MATERIALS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[GENERATE_MYTHICAL_MATERIALS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Mythical Healing ===

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALLOW_MYTHICAL_HEALING:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_MYTHICAL_HEALING:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Divination, Experiments, and Necromancy types ===
These allow or disallow [[die|divination]], demon or necromancer [[experiment]]s, and the more advanced [[necromancer]] abilities.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALLOW_DIVINATION:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_DIVINATION:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_DEMONIC_EXPERIMENTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_DEMONIC_EXPERIMENTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_EXPERIMENTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_EXPERIMENTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_LIEUTENANTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_LIEUTENANTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_GHOULS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_GHOULS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_SUMMONS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_SUMMONS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Desired Good/Evil Square Counts ===

These values change the amount of [[Surroundings#Good|good or evil]] tiles on the map, depending on the size of the region they are being considered for. The counts are for all tiles in all subregions of a given size considered together, ''not'' counts for each subregion considered separately (all tiles in the same subregion share the same [[surroundings]] values).

As used here, a "subregion" is a named world area. Subregion names and locations for a generated world are viewable in legends mode under "Regions". Subregions are classified by size the same way for all map sizes: 1-24 tiles is Small, 25-99 tiles is Medium, and 100+ tiles is Large.

The counts used here will always be restricted to regions of the given size, no matter how large the count. Also, the count is more of a goal than a minimum or maximum. As a result, you can end up with many more or many fewer than the requested number of squares in some situations. In particular, if you have something like a case where only 3 large regions exist in a world, and you request "1 evil square" in large regions, you will end up with one of the large regions being ''entirely evil''. So any non-zero value in one of these settings essentially means "force at least one region of this size to be all good/evil."

Note that the "evilness" of evil biomes is also impacted by savagery. Certain civilizations cannot exist in good and/or evil squares, so too many of one or the other may limit the size of certain types of civilizations - dwarves, for example, need non-aligned biomes. Creating too many evil biomes seems to lead to the danger of many civilizations' early extinction.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GOOD_SQ_COUNTS::<med region>:<lg region>]</nowiki></tt>
| <tt><nowiki>[GOOD_SQ_COUNTS:100:1000:2000]</nowiki></tt>
| rowspan="2" | Set count to zero to disable for that region size.
|-
| <tt><nowiki>[EVIL_SQ_COUNTS::<med region>:<lg region>]</nowiki></tt>
| <tt><nowiki>[EVIL_SQ_COUNTS:100:1000:2000]</nowiki></tt>
|}

=== Minimum Biome Square Counts ===

These numbers control whether or not a world will be rejected based on a lack of different [[biome|biomes]]. Raising these numbers will '''not''' automatically generate the given number of squares of the given biome! For a biome to exist, certain conditions like elevation and rainfall must exist.

These parameters simply filter out worlds that (for example) randomly fail to have enough high elevation squares to support a given number of mountains, etc. Some settings may cause worlds to always be rejected. For example, if for some reason the maximum elevation parameter is set to a value below what will support mountain biomes, it will be impossible to satisfy a non-zero requirement for mountain squares. The same principle goes for other conditions and biomes such as low elevations and oceans, etc.

Certain civilizations require different biomes to exist (such as dwarves and mountains), so eliminating certain biomes will make it impossible for certain civilizations to form.

These parameters often result in infinite world rejection problems. See [[World rejection]] for information on solving problems related to worlds always being rejected due to one or more of these parameters.

0 means no minimum for rejection - setting it to 0 does not guarantee 0 squares of that biome.

==== Biome Type Requirement Table ====

Terrain requirements for various biomes are described below.{{Verify}} Note that some of the exact ranges are unknown.

{| {{prettytable}}
|- bgcolor="#dddddd"
! rowspan="2" | Biome
! colspan="4" | Terrain Requirement
|-
! Elevation
! Rainfall
! Temperature
! Drainage
|-
| Swamp/Marsh
| 100-299
| 33-100
| Non-Freezing
| 0-32
|-
| Desert/Badland
| 100-299
| 0-9
| non-freezing
| note1
|-
| Forest
| 100-299
| 66-100
| non-freezing
| 66-100
|-
| Mountains
| 300-400
| N/A
| N/A
| N/A
|-
| Ocean
| 0-99
| N/A
| N/A
| N/A
|-
| Glacier
| 100-299
| N/A
| Freezing
| 80(?)-100
|-
| Tundra
| 100-299
| N/A
| Freezing
| 0-66
|-
| Grassland
| 100-299
| 0-66
| Non-Freezing
| 0-66
|-
| Hills
| 100-299
| 0-66
| Non-Freezing
| 66-100
|}
note1 drainage: 00-32 sand desert, 33-49 rocky wasteland, 50-65 rocky wasteland but different characters/appearance, 66-100 badlands

==== Minimum Initial Square Count ====

'''Note: The exclusive purpose of these parameters is to cause world rejection.'''

This is the minimum number of squares of the given biome that must exist before things like erosion take place. One thing to keep in mind is the maximum number of squares on a map of a given size - if the total number of squares on a map is lower than the sum of all square count parameters, then you will get infinite world rejection.

To determine the number of squares on a map, just multiply the dimensions. In practice these parameters will need to sum to lower than the maximum because some space is needed for "slack".

{| {{prettytable}}
|- bgcolor="#dddddd"
! Map Size
! Number of Squares
|-
| 17×17
| 289
|-
| 33×33
| 1089
|-
| 65×65
| 4225
|-
| 129×129
| 16614
|-
| 257×257
| 66049
|}

==== Minimum Initial Region Count ====

This is the minimum number of regions of contiguous biome squares that must exist before other processes such as erosion take place.

==== Minimum Final Region Count ====

This many regions of the given biome must exist after erosion and similar phases of generation have been completed.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[REGION_COUNTS:SWAMP:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:SWAMP:1032:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:DESERT:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:DESERT:1032:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:FOREST:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:FOREST:4128:13:12]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:MOUNTAINS:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:MOUNTAINS:8256:9:9]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:OCEAN:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:OCEAN:8256:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:GLACIER:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:GLACIER:0:0:0]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:TUNDRA:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:TUNDRA:0:0:0]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:GRASSLAND:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:GRASSLAND:8256:13:12]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:HILLS:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:HILLS:8256:13:12]</nowiki></tt>
|}

=== Erosion Cycle Count ===

Tells the world generator how long the world has to erode its tall peaks down to mountainsides during the 'running rivers...' stage of world creation. The higher this number, the less jagged the world will be, and the more wide the major rivers will be. If you use the maximum number, your mountains will dissolve before your eyes into plains which can lead to rejections if there aren't enough mountains to use for river start points and dwarven civilization origin points.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EROSION_CYCLE_COUNT:<number>]</nowiki></tt>
| <tt><nowiki>[EROSION_CYCLE_COUNT:250]</nowiki></tt>
| Range: 0 to 1000
|}

=== Minimum/Desired River Start Locations ===

This is the minimum number of riverheads that must exist before and after erosion takes place. Worlds will be rejected if they fail to meet these numbers. As with minimum biome counts, raising this number doesn't automatically create this many riverheads. Other conditions like terrain and rainfall must exist for rivers to form.

Extremely high pre-erosion values speed erosion greatly, while low post erosion values are useful for limiting rejects due to lack of river origin points. One can try the 800 value to get more lakes.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[RIVER_MINS:<min pre-erosion>:<des post-erosion>]</nowiki></tt>
| <tt><nowiki>[RIVER_MINS:200:400]</nowiki></tt>
| Range: 0 to 800
|}

=== Periodically Erode Extreme Cliffs ===

If enabled, makes every impassable rock wall into a series of ramps. Some prefer to pump up erosion to about 250, and turn the "Desired pre-erosion river count" to 0 for good erosion and no extra canyons.

Normally this is set to Yes (1).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PERIODICALLY_ERODE_EXTREMES:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[PERIODICALLY_ERODE_EXTREMES:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Do Orographic Precipitation and Rain Shadows ===

Toggle that allows terrain height to affect rainfall. For example, moist air coming from the ocean blows over the land. As the terrain gets higher, it forces the moist air up, causing it to rain on the seaward side of a mountain. Eventually, all the rain has fallen if the mountain is tall enough. So, when the breeze goes over the top, there's no moisture left to fall on the other side, creating a rain-shadow. In the current version, regions where drainage is above 50 will also create rain shadows, regardless of the underlying biome and elevation.{{cite forum|140685/5484064}}

Turning this on should create a tendency for more extreme rainfall in regions, creating more forests, deserts, marshlands, and grasslands. Also note that it can create rainfall outside of min-max rainfall settings, so even in a world with a 0 max rainfall you may get rainfall biomes. Turning it off should result in more controllable, less complex rainfall conditions based on rainfall parameters as it adds a random element which can distort or otherwise mess up the climates on a pregenerated map.

This should be disabled if you're importing a map or using a preset map file that has weather.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[OROGRAPHIC_PRECIPITATION:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[OROGRAPHIC_PRECIPITATION:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Maximum Number of Subregions ===

This is the number of separate biomes (the flashing regions you see on embark when you hit F1, F2, etc. when there's more than one biome on the embark location) that are allowed to exist on the entire map.

Setting this to very low values will result in numerous rejections depending on [[#X and Y Variance|variance parameters]]. If variance values are set to high numbers, many small biomes will be created causing rejection if this parameter value is not increased beyond the default.

Increasing the value of this tag is often a must when generating "patchwork" worlds with lots of biome variance, but simply increasing it without increasing variance parameters will not guarantee more biomes.

It is also interesting to note that the maximum subregions is 5000 which is more than the total number of squares for a pocket or small map. However, for a medium or large map (16641 or 66049 squares) it quickly becomes a mere fraction of the total number of possible subregions. In fact it would be quite easy on a large map to end up with far too many subregions and get endless rejections of this type.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SUBREGION_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[SUBREGION_MAX:2750]</nowiki></tt>
| Range: 1 to 5000
|}

=== Cavern Parameters ===
[[Caverns]] are the hollow areas underground, which dwarves tend to encounter when they're digging around. The '''Cavern Layer Number''' parameter determines how many cavern systems will be generated, not including the magma layer or the Bottom layer. Defaults to three - setting it to lower values could help FPS. Setting it to 2 will merge cavern 3 species into the 2nd cavern, and setting it to 1 will merge all into one cavern. However, disabling them entirely by setting it to 0 will make it impossible to grow any underground plants, as none will exist for your civilization to cultivate, nor will they be available on embark.

*Setting caverns to a sub-3 number (Spoiler, highlight to view) erases about one-third of HFS spires{{Bug|10267}} and prevents dig deep disasters. Additionally, random plant or animal species can be more frequently absent.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_COUNT:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_COUNT:3]</nowiki></tt>
| Range: 0 to 3
|}

==== Cavern Layout Parameters ====

Open caverns and dense passageways are not mutually exclusive. When both are raised, bizarre results can occur, such as layers showing a combination of open caverns, a cluster of network passages, and natural walls sprinkling the inside of an otherwise open cavern. [http://www.bay12forums.com/smf/index.php?topic=76355.msg1936859#msg1936859 Reference]

If you want the largest open spaces possible, then decrease the density and increase the openness. If you want a labyrinth of passageways, lower the openness and raise the passage density.

Another interesting note about the cavern layers is that the seed and number of demon types affect the layout of the caverns.

<gallery widths=200 heights=200 perrow=2>
File:Open00Density100.jpg|Cavern slice with Openness of 0 and Density of 100
File:Open100Density00.jpg|Cavern slice with Openness of 100 and Density of 0
File:Open100Density100.jpg|Cavern slice with Openness of 100 and Density of 100
File:Open50Density50.jpg|Cavern slice with Openness of 50 and Density of 50
</gallery>

===== Layer Openness min/max =====

Dictates the size of cavern passages. When Passage Density (see below) is set to minimum (0), caverns will be open expanses. Raising the maximum will increase the size of the caverns.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MAX:100]</nowiki></tt>
|}

===== Layer Passage Density min/max =====

Determines how many passages form the cavern. If openness (see above) is set to minimum and density increased, then you will get a maze-like network of small criss-crossing passages. Raising the values further increases the number of the maze-like passages.

Caverns will be large, open spaces at 0, and comprised of many small vertical shafts of rock at 100. Setting both values to be the same results in a uniform look for the caverns.{{Verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MAX:100]</nowiki></tt>
|}

===== Layer Water min/max =====

Determines the minimum and maximum percentage of water each cavern can contain.

Caverns with a water level of 10 or higher can support creatures and plants from the "Subterranean Water" biome, and caverns with a water level of 90 or lower can support the "Subterranean Chasm" biome; levels of 10-90 support ''both'' biomes, while levels below 10 or above 90 support only one.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_WATER_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_WATER_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_WATER_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_WATER_MAX:100]</nowiki></tt>
|}

==== Magma Layer ====

This parameter controls whether the [[magma sea]] exists.

Setting 1/Yes causes the magma layer to exist, value 0/No prevents it. Appears not to have any impact on volcanoes nor volcanism, so even if 0/No, there will still be embark locations with magma. If a [[volcano]] exists, it appears to always tap the magma sea, but the magma sea will not be revealed by revealing the volcano.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[HAVE_BOTTOM_LAYER_1:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[HAVE_BOTTOM_LAYER_1:1]</nowiki></tt>
|}

==== Bottom Layer ====

Determines if the space below the magma sea exists. If Yes the "HFS" layer is always present. Normally you want to leave this set to Yes for maximum fun.

If enabled, this will force the magma layer above it.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[HAVE_BOTTOM_LAYER_2:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[HAVE_BOTTOM_LAYER_2:1]</nowiki></tt>
|}

=== Z Levels (Depth) Settings ===

These parameters control the "thickness" of various "layers" on the map. Note that a "layer" in this case does not refer to one Z-level, but refers to a number of related Z-levels such as "levels above ground".

The following table assumes that you have 3 cavern layers. (out of a minimum of 0-3) The Levels Above Layer settings control how many Z-Levels are above each layer. A layer may itself consist of multiple Z-Levels (and almost always does).

{|style="margin:1em 1em 1em 0;background:#F9F9F9;border:1px #AAA solid;border-collapse:collapse;" class="wikitable"
|-style="background:#F2F2F2;text-align:center;"
!style="border:1px #AAA solid;padding:0.2em;" width="120"|Setting Name
!style="border:1px #AAA solid;padding:0.2em;" width="200"|Token
!style="border:1px #AAA solid;padding:0.2em;"| Description
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Ground
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_GROUND:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| The number of Z-levels of air above the highest surface level. Has no impact on how many Z-levels deep the surface layer is.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above layer 1
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_1:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of stone above the first cavern layer. Making this higher will guarantee ''at least'' that many levels to build your fortress, but will have no impact on how many z-levels thick the surface layer is. Also, the top of a cavern may be higher than the rest of a cavern, so in practice there will be more "solid" levels than this above the cavern.
As of version 0.31.25 this setting is inaccurate. The actual number of z-levels may vary in a range of approx. ±5, which may result in non-existence of any solid z-levels between a surface layer and first cavern layer.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 2
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_2:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very top of the second cavern and the very bottom of the first cavern.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 3
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_3:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very top of the third cavern and the very bottom of the second cavern.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 4
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_4:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very highest magma and the very bottom of the third cavern. Spoiler Hidden (select invisible text to read): Making this high will give a large area for HFS veins, so that it never touches caverns, giving more to mine '''if''' it was impacting the cavern previously.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 5
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_5:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Uncertain. May control the number of levels of "Semi Molten Rock" between HFS and Magma, may control number of levels of magma, may impact both. In experimentation, the overall depth of all magma sea and semi-molten rock levels appears to increase, but not consistent enough to say for certain. Only valid if Magma Layer present. Spoiler Hidden:Often the HFS vein will only extend as high as the highest magma, making this the only guaranteed way to increase amount of HFS to mine, but unfortunately also creating enormous useless semi-molten z-levels
|-
|style="border:1px #AAA solid;padding:0.2em;"| At Bottom
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_AT_BOTTOM:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Appears to be number of levels of HFS chamber. Only valid if Bottom Layer present, often having no impact. Values larger than default result in strange things.
|}

Some implications:
* The number of surface layers (e.g. soil), at this time, cannot be controlled. For example, on a map with 1 layer of peat, then a layer of silt, then a layer of obsidian, there is no control to let you increase either one to be, say, 20 z-levels. (though you may get lucky with the obsidian).
* There can be multiple stone layers between the cavern and the surface, so, increasing Levels Above Layer 1 may give you more conglomerate or more granite, and you have no control over which stone layer spans those Z-levels.
* The layers shown on embark span across the cavern layers in an unknown and inconsistent way. Sometimes those 10 different layers of stone are evenly distributed over your 400 z-level deep map, sometimes the first 9 get 1 z-level each and the last gets the other 391 levels. No way to control found yet.
* The HFS chamber, if present, will always extend into the rock layers, and appears to always make contact with the bottom cave. Large values for levels above layer 5 and layer 4 can result in enormous chambers, but the number of levels at the top (the part with undead) appears to be unaffected.
* Unconfirmed whether number of levels between caverns has any impact on cavern height. There will be connecting ramps and/or shafts between cavern layers no matter how many levels are between them.
* '''Very Important''': These values appear to apply across a whole 16x16 region, not just embark areas. That means that if a 16x16 region is completely flat, but has one tall mountain in one far corner, even if you set Levels Above Ground low (e.g. 2 z-levels) you still have all the empty air of the highest mountain in every embark tile (e.g. 200 z-levels). Also can happen to the semi-molten layer, and can lead to unexpected behavior.
* Very large or small values can cause strange things to happen.

=== Minimum/Maximum Natural Cave Size ===
It's not clear what effect these currently have, other than changing them can change the location of caves somewhat.{{verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVE_MIN_SIZE:<number>]</nowiki></tt>
| <tt><nowiki>[CAVE_MIN_SIZE:5]</nowiki></tt>
| rowspan="2" | Range: 1 to 500
|-
| <tt><nowiki>[CAVE_MAX_SIZE:<number>]</nowiki></tt>
| <tt><nowiki>[CAVE_MAX_SIZE:25]</nowiki></tt>
|}

=== Number of Caves ===
The number of caves generated in mountainous and non-mountainous regions, mountain caves will always be generated on the edge of mountain ranges next to non-mountainous regions. Lurking [[kobold]]s set up shop in caves, and store their stolen items there - a setting of 0 in both will stop kobold civilizations from appearing. Special note: a cave is not initially a [[lair]], although beasts can later use them as their lair.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[MOUNTAIN_CAVE_MIN:100]</nowiki></tt>
| rowspan="2" | Range: 0 to 800
|-
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:200]</nowiki></tt>
|}

=== Number of Mythical Sites ===
The number of [[mysterious dungeon|mysterious sites]] generated around the world. The extended effects of setting this to 0 has not been determined{{verify|is chosen still available? is quest still given? etc.}}.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MYTHICAL_SITE_NUM:<number>]</nowiki></tt>
| <tt><nowiki>[MYTHICAL_SITE_NUM:200]</nowiki></tt>
| rowspan="2" | Range: 0 to 800
|}

=== Make Caves Visible ===
If set to no (default) then the location of caves will not be marked on the map. If set to yes, caves will appear on the map so that they may be sought out or avoided as desired.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALL_CAVES_VISIBLE:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALL_CAVES_VISIBLE:0]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Init Options to Show Tunnels ===

If enabled, you will be able to see the underground tunnels often built by dwarves on the world map, and they will appear as black lines, similar to roads.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SHOW_EMBARK_TUNNEL:<0-2>]</nowiki></tt>
| <tt><nowiki>[SHOW_EMBARK_TUNNEL:2]</nowiki></tt>
| 0 = No 1 = Only in Finder 2 = Always
|}

=== Number of Civilizations ===

This number of [[civilization]]s will be placed on the map before history generation begins. These civilizations may later die out due to historical events. It is noteworthy that the chance for any given civilization to be destroyed through megabeasts decreases with a higher total number of civilizations present[http://www.bay12forums.com/smf/index.php?PHPSESSID=7348f68f41a9659443c05b2acf534e6c&topic=112465.15 data]. The five races are dwarf, elf, human, goblin, and kobold; they will generally be placed in equal numbers until the quota has been reached. If there are not enough biomes or other worldgen prerequisites for an even distribution, certain civs will be much more or less frequent than others[http://www.bay12forums.com/smf/index.php?PHPSESSID=7348f68f41a9659443c05b2acf534e6c&topic=112465.15 data]. If there is an odd number of civs (not divisible by 5), then the remainder is distributed randomly. Kobold civs require caves to be placed; if no caves exist, then kobolds are skipped and will not appear. This does not cause rejections [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415125#msg3415125 data]. Goblin civilizations require multiple demons, see the [[#Number_of_Demon_Types|number of demon types]] section above.

Note that a high value here can cause lots of map rejections, particularly on smaller maps as there simply isn't enough room or regions to put them all in.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_NUMBER:40]</nowiki></tt>
| Range: 0 to 300
|}

=== Playable Civilization Required ===

If this is set to yes (default) then worlds will be rejected if no civilization with [[Entity token|CIV_CONTROLLABLE]] can be placed. In an unmodded game, only the dwarves have this token.

If set to no, the result may be a world that cannot be played in Fortress Mode.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PLAYABLE_CIVILIZATION_REQUIRED:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[PLAYABLE_CIVILIZATION_REQUIRED:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Minimum Number of Mid/Low/High Characteristic Squares ===

Sets the minimum possible number of squares of certain ranges of each of the region qualities, such as elevation, rain, drainage, volcanism, savagery, and temperature. These need to be changed to reflect your regional meshes and weights, and are responsible for a HUGE number of map rejections. These values can all be set to 0 for much fewer map rejections, particularly in the case of more wacky, non-standard maps.

These values will cause worlds to be rejected unless at least the given number of squares of the given type are randomly generated. Setting these values too high could result in worlds always being rejected if other parameters such as the maximum/minimums for elevation, etc., don't allow enough of those squares to get generated.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[ELEVATION_RANGES:8256:16512:8256]</nowiki></tt>
| rowspan="5" | Minimum number of squares that must have low, medium, and high amounts of the given attribute. 
0 = No minimum
|-
| <tt><nowiki>[RAIN_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[RAIN_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[DRAINAGE_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[SAVAGERY_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[VOLCANISM_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM_RANGES:8256:16512:8256]</nowiki></tt>
|}

==World rejection==

:''Main article: [[World rejection]]''

If you are having the common problem of generated worlds always being rejected by the world generator, see [[v0.31:World rejection|Solving World Rejection Problems (v0.31 page)]] as it contains many detailed suggestions on how to troubleshoot and solve these issues.

== Parameter set examples ==

If you're trying to do something specific, then the [[Worldgen examples]] - complete parameter sets that can be copied directly into your ''world_gen.txt'' file and customized as desired - might be helpful.
If none of the examples suit your needs, [[Worldgen tricks]] has strategies and tips on making a world just right for you.

For many, many more examples see:
* [http://www.bay12forums.com/smf/index.php?topic=101280 DF2012 (v0.34) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=140180 DF2014 (v0.40) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=168543.0 DF2014 (v0.44.02+) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=175538 DF2014 (v0.47.01+) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=180805.0 DF2022 (v0.50.01+) WorldGen "Cookbook" Thread]

{{World}}

Advanced world generation

2026-04-15T01:53:27Z

Ziusudra: /* Interaction between Mesh Size and Weighted Ranges */ added all weights at none

{{migrated article}}
{{Quality|Superior}}
{{av}}
:''This article contains information on advanced world generation. For information on basic world generation, see [[World generation]].'' ''See [[World token]] to more easily find information by the names used in the world_gen.txt file, [[World rejection]] for information on solving problems related to worlds always being rejected, and [[Worldgen examples]] for example worlds.''

[[File:adv_worldgen_v50.png|thumb|400px|right|The advanced world generation screen. ''(Click to enlarge)'']]'''Advanced world generation''', also labeled as '''detailed mode''', allows substantially more detail-oriented options of customization than standard, basic world generation. This gives the player much more control over how their world is generated. To better understand this article, it is advised that one should read about [[World generation|'''basic world generation''']] first.

The advanced world generation screen is reached by clicking "Create new world" at the main menu, then clicking "Detailed mode". Once at that screen, clicking "Basic options" will return the user to the standard world generation screen.

== Parameter sets ==
There are multiple default sets of all the advanced world generation parameters hard-coded in ''Dwarf Fortress'', which will be overridden by the <tt>prefs/world_gen.txt</tt> file in the main ''Dwarf Fortress'' directory, if it exists. It does not exist by default, you must create it, either by saving the default sets, or saving a copy from the [[world_gen.txt]] wiki page or elsewhere. This file can then be edited with a text editor, and you can copy and paste other players' sets of parameters into it. For sources of such parameter sets see [[Advanced_world_generation#Parameter_set_examples|Parameter set examples]] below.

To get back the default sets, move the existing <tt>prefs/world_gen.txt</tt> to somewhere else (like Documents), or delete it if you do not want to keep the changes, then load the sets in the game, it will then use the hardcoded defaults.

== User interface ==
First, there is a line of text inputs and buttons along the top of the screen, from left to right:
* The drop down menu of currently defined parameter sets, click the down arrow to select a set that you want to work with. The currently selected set can be renamed by clicking the current name or the [[File:Quill.png]] button. The first set in the file is selected by default, usually "LARGE ISLAND". See [[#Parameter set title|Parameter set title]].
* The dimensions of the world for the selected set, see [[#World dimensions|World dimensions]].
* A text entry box to set all of the seed options to the same seed, will show "Random seed", "Various seeds", or, if all four seeds are set to use the same value, that value. See [[Advanced_world_generation#Seed_values|Seed values]] and [[Advanced_world_generation#Seed_values|Seed notes]].
* The Copy Button to make a copy of the currently selected set and appends it to the bottom of the list.
* The red Delete button to delete the currently selected set, you will be prompted to confirm the deletion.
* The New parameter set to create a new parameter set and appends it to the bottom of the list. This seems to just copy the default "LARGE REGION" set.
* The Save button to save all of the current sets to the <tt>prefs/world_gen.txt</tt> file.
* The Load button to load from the same file, there is no confirmation, '''any unsaved changes will be lost'''. If that file does not exist, this resets all of the sets to the defaults.

Most of the middle is the parameters themselves, with a scroll bar to the right. Each row of the list can include:
* The name of the option
* The range of accepted values; not every option has this, and does not always match the displayed value, for example "0 to 1" might show as "No" and "Yes".
:* Sometimes the range might not initially show on rows that it should, reloading the sets with the Load button sometimes fixes that.{{bug|13176}}
* A plus button to increase the value or cycle through options, when applicable (this button will be missing if the range is missing.)
* The current value; can be clicked to edit, to actually set a value you must press {{k|enter}}, without doing that, clicking another entry box or right clicking will instead reset to the currently set value.
* An edit button to show that the previous box is editable, same as clicking on the text box.
* A minus button to decrease the value or cycle through options, when applicable (this button will be missing if the range is missing).
* A red button to disable this parameter, when applicable, usually setting the value to 0, or -1.

{{notice bar|bgcolor=#faa|bordercolor=#f00|All of the buttons below leave this screen and do not prompt to save the sets, so unsaved changes may be lost.}}
At the bottom right are 3 or 4 more buttons:
* The Create world button to do just that using the currently selected set, '''unsaved changes are lost'''.
* The Basic options button to go back to the normal world generation screen, unsaved changes are not lost if you come directly back to Detailed mode.
* The [[Mods]] button to go to the mod selection screen, unsaved changes are not lost if you come directly back to Detailed mode. Only shown if mods are available.
* Back to main menu button to do just that, '''unsaved changes are lost'''.

=== World painter ===
:''Main article: [[World painter]]
The '''world painter''' tool is not in the current version of ''Dwarf Fortress''; it allowed you to paint features onto a map. '''However''', those maps can still be used when generating a world by pasting world painter parameter set maps created in old versions into the <tt>prefs/world_gen.txt</tt> file. [[Utilities#Perfect_World_DF|Perfect World DF]] is a utility that uses the same parameter functionality as the world painter to paint a map, and it also can work with the current version of ''Dwarf Fortress''.

== Generating a world ==
You can either use an already-defined parameter set, or you can edit them, though it is highly suggested to edit a copy of one of the defaults. Once you are happy with the parameters you should save the values you just edited before you click the Create world button. Information about each parameter is documented below.

The phases of the world generation process are (this order is not completely correct):
* Preparing elevation...
* Setting temperature...
* Running rivers...
* Forming lakes and minerals...
* Growing vegetation...
* Verifying terrain...
* Importing wildlife...
* Recounting legends...
* Placing civilizations...
* Making cave civilizations...
* Making cave pops...
* Placing other beasts...
* Placing megabeasts...
* Placing good/evil...
* Placing caves...
* Prehistory generation
* Finalizing civ mats...
* Finalizing art...
* Finalizing uniforms...
* Finalizing sites...

== Seed notes ==
The world generation process uses a PRNG (Pseudo Random Number Generator) algorithm. A PRNG will produce a sequence of numbers that "looks" random, even though the actual sequence of numbers will always be the same if the PRNG is started with the same seed value. Basically this means that if you run world generation with a certain seed value on your computer, and someone else runs world generation with the same seed value on their computer, the same sequence of random numbers will be generated on both computers. The practical impact of this is that someone else can generate exactly the same world that you generated by entering the same seed value that you used.

In the current version, the seed values for the world itself and the names seem to produce the same result, but you will get changes in events which will result in a very different world history.{{bug|6934}} Keep this in mind if you want to regenerate a particular world.

The way that a world is generated can also be affected by certain world tokens. Changing them causes that code to use more or fewer PRNG values, causing later uses to get different parts of the sequence. So, you cannot for example, change the minimum and maximum rainfall and get 'the same world but drier or wetter', instead, a different world is generated. That said, it would also seem that certain small changes to these world tokens can occasionally generate a very similar world, however, other tokens are more sensitive. For more information see the forum thread [http://www.bay12forums.com/smf/index.php?topic=112132.msg3404199#msg3404199 here].

The following are tokens which use the PRNG values in ways that changing them will likely cause broader changes:

* [DIM:X:X]
* [ELEVATION:X:X:X:X]
* [RAINFALL:X:X:X:X]
* [TEMPERATURE:X:X:X:X]
* [DRAINAGE:X:X:X:X]
* [VOLCANISM:X:X:X:X]
* [SAVAGERY:X:X:X:X]
* [ELEVATION_FREQUENCY:X:X:X:X:X:X]
* [RAIN_FREQUENCY:X:X:X:X:X:X]
* [DRAINAGE_FREQUENCY:X:X:X:X:X:X]
* [TEMPERATURE_FREQUENCY:X:X:X:X:X:X]
* [SAVAGERY_FREQUENCY:X:X:X:X:X:X]
* [VOLCANISM_FREQUENCY:X:X:X:X:X:X]
* [PARTIAL_OCEAN_EDGE_MIN:X]
* [COMPLETE_OCEAN_EDGE_MIN:X]
* [HAVE_BOTTOM_LAYER_1:X]
* [MINERAL_SCARCITY:X] {{cite talk/this|Mineral scarcity}}

Many other world parameters, such as end year and embark points, can, however, be changed without it having any effect on the geography of the world generated from the seed values.

Normally, you don't enter these seed values, the game comes up with values based on some other sort of pseudo-random information from things like the current date and time.

When generating a world, ''Dwarf Fortress'' records the seeds it used in [[gamelog.txt]]; they can also be found with <code>gui/gm-editor world.worldgen.worldgen_parms</code> in [[DFHack]].

== Advanced parameters ==
There are essentially 4 types of controls for the generation of the surface map;

'''Terrain parameters''': as described below, these 5 variables define the basic background world, how hot or cold it is, how much rainfall, how high the mountains are. The world automatically goes through the temperature range along the Y axis, although sometimes it will be hotter in the north, other times in the south, or cold at both. Minimum, maximum and X,Y variance can drastically alter the world.

'''Weighted meshes''': these are a way to fine-tune the amount of the 5 basic variables on the map. They can be used to set the specific distribution of different elevations or rainfall areas for example.

'''Feature parameters''': such as rivers, mountain peaks, volcanoes, and oceans, which can cause rejections if the terrain parameters don't allow enough suitable locations for the features to be placed.

'''Rejection parameters''': ''Dwarf Fortress'' uses a 'belt-and-braces' approach to world generation. The above controls allow you to shape the world, then the rejection parameters throw it out if it does not meet certain criteria. There are a number of rejection parameters for the number and degree of the 5 basic variables, for biome types, etc. If the world does not meet the requirements of any one rejection parameter the world is rejected and re-randomised. Also see [[World rejection]].

Leaving tokens out of a set in <tt>world_gen.txt</tt> will cause the game to use default values which are not adjusted for smaller world sizes, this may cause smaller worlds to always be rejected.

If you are experimenting with world design, there is also a [[Settings#Feature_toggles|game setting]] that will log the rejection reasons to ``[[map_rejection_log.txt]]``. With that information you can then either adjust the rejection parameters to allow those worlds, or the other parameters to prevent them from trying to generate. ''Dwarf Fortress'' will keep adding to the file, so you may want to trim or delete it occasionally.

The parameters are described below in the order that they appear in the list in the game, which is not necessarily the order they appear in <tt>world_gen.txt</tt>. See [[world token]] for an index that will help you look things up by token name. The tokens used in <tt>world_gen.txt</tt> are at the bottom of each of the following parameter descriptions.

=== Parameter set title ===
This sets the name of the parameter set itself, as used in the list of sets (this has nothing to do with the name of the generated world).
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITLE:<name>]</nowiki></tt>
| <tt><nowiki>[TITLE:MEDIUM ISLAND]</nowiki></tt>
| Required
|}

=== World dimensions ===
The size of the map for the current set can be changed by changing the Width and Height values at the top next to the set title. You will need to confirm this, since changing the dimensions of the world will change other parameters, because many of them have different defaults depending on the surface area available.

Larger maps usually take longer to generate and may reduce [[Frames per second|FPS]] in-game, though this is really a matter of larger worlds usually having more civilizations, sites, historical figures, and events; restricting the number of those can speed up the process. Non-square maps may result in crashes{{bug|2928}}.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DIM:<width>:<height>]</nowiki></tt>
| <tt><nowiki>[DIM:257:257]</nowiki></tt>
| Valid values are 17, 33, 65, 129, and 257, other values will use one of those. Changing the size in the file without adjusting other parameters can cause many rejections.
|}

=== Seed values ===
Enables the use of, and specifies seed values for, different parts of the world generation process. Just entering a specific seed does not enable it, that must be done separately, although using the box at the top to set all the seeds to the same value does enable them all. Enabling a seed puts the token in using what ever is in the text box below. If you enable a seed, but do not enter a seed, the string "Seed text" will be used (<tt><nowiki>[SEED:Seed text]</nowiki></tt>). Trying to use a <tt><nowiki>]</nowiki></tt> in the string in the file will end the seed there, since it closes the token, any text after that will be ignored. Normally, just leave these set to Random, unless trying to reproduce the results of a previous world generation. See also the [[Advanced_world_generation#Seed_notes|seed notes section]] above.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEED:<text>]</nowiki></tt>
| <tt><nowiki>[SEED:31337]</nowiki></tt>
| rowspan="4" |
For each of these not in the config file, a random seed will be used, and the first seed is not used to generate the others. The seeds used are output to [[gamelog.txt]] when world generation starts.
|-
| <tt><nowiki>[HISTORY_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[HISTORY_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[NAME_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[NAME_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[CREATURE_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[CREATURE_SEED:31337]</nowiki></tt>
|}

=== World name ===
As previously mentioned, the title of the parameter set doesn't affect the name of the world. You can specify a particular name for your world, or leave the value blank for a random one. (The [[DFHack]] utility adds an option to rename the world using the in-game languages.)
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CUSTOM_NAME:<name>]</nowiki></tt>
| <tt><nowiki>[CUSTOM_NAME:Realm of Cheese Engravings]</nowiki></tt>
| For a random name, simply don't use this token.
|}

=== Embark Points ===
The number of points for equipment and animals when embarking in fortress mode (there is no equivalent setting for adventure mode). Normally, the default of 1504 is fine, but can be increased for various purposes like experimentation or to help dwarves survive in a particularly evil world, or reduced for certain [[challenges]].
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EMBARK_POINTS:<number>]</nowiki></tt>
| <tt><nowiki>[EMBARK_POINTS:1504]</nowiki></tt>
| 0 to 10,000
|}

=== End year ===
The maximum number of years generated for the world, although generation can be paused and the world used as is any time after the second year; the same as the [[World_generation#History|History]] parameter in basic world gen, except that you can enter an exact value. A too-short history can limit the materials available to civilizations, and [[Chosen|certain adventure mode features]] are only available after certain site events, while too long a history often leads to civilizations dying.

For more information on the history aspect of the game, see [[Legends]] and [[Calendar#Ages|Ages]].
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[END_YEAR:<number>]</nowiki></tt>
| <tt><nowiki>[END_YEAR:250]</nowiki></tt>
| 2 to 10,000
|}

=== Population cap after civ creation ===
A soft limit to the total number of [[historical figure]]s alive at the same time during generation across all civilizations, only preventing the birth of new historical figures.{{cite forum|140544/5701667}} Each civilization is allotted a percentage of the total by the percentage of sites they control.{{cite forum|159164/7553641}} Civilizations also have non-historical populations, and there is no setting to limit those (in early versions, all civilization members were historical figures, this is also why the name of this setting is misleading). Each [[entity]] also has limits from their raws, see the [[Entity_token#Population|population]] entity tokens, and setting this to unlimited will not remove those.

Huge historical figure populations can slow generation and the game in general.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_POPULATION:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_POPULATION:15000]</nowiki></tt>
| -1 to 100,000, -1 is no limit
|}

=== Site cap after civ creation ===
Total number of [[site]]s that can be directly created by all civilizations combined like [[hillocks]], [[hamlet]]s, [[dark pits]], [[forest retreat]]s, etc. Does not prevent the placement of initial civilization sites, though they will then be counted for the limit. Does not affect creature sites like [[cave]]s or [[lair]]s, group sites like [[castle]]s, [[monastery|monasteries]], [[tower_(necromancy)|tower]]s, [[fort]]s, or [[camp]]s, or unpopulated sites like [[tomb]]s. After this limit is reached, no civilization will be able to place new sites. See the [[Entity_token#Placement|placement]] entity tokens for other ways that civilization site placement can be limited.

Increasing this will slow generation down and reduce the available places for player sites. Since the {{token|MAX_SITE_POP_NUMBER|entity}} entity token limits the historical figure population per site, this site cap can also limit the total historical figure population of all civilizations combined, and some expand faster than others getting more sites before the limit is reached.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SITE_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SITE_CAP:1500]</nowiki></tt>
| -1 to 100,000, -1 is no limit
|}

=== Beast control ===

These parameters don't usually matter too much, but may matter for small numbers of beasts.

==== Percentage of Megabeasts and Titans Dead for Stoppage ====

The world starts out with a certain number of powerful megabeast and titan entities in existence. If a percentage of the megabeast and titan population dies out during history generation, then history generation will stop early. For example, if the elimination value is 80%, and the generated history starts with 200 entities and 160 of those 200 entities are eliminated by historical events before the End Year is reached, history generation will stop immediately.

If you want to end the creation of your world at the beginning of a certain age, choose the following values:
* Age of Legends: ~34%
* Age of Heroes: ~67%
If there are three or fewer titans or megabeasts in your world, the age will be given a special name reflecting the remaining megabeasts/titans, instead.

==== Year to Begin Checking Megabeast Percentage ====

The percentage of dead [[megabeast]]s and [[titan]]s for stoppage will not be checked until this year is reached in history generation. This can be used to ensure that a world reaches a certain year even if all of the megabeasts in the world are slain earlier.

If the number of living [[megabeast]]s and [[titan]]s starts at or drops to less than four, then world generation will always stop if the current year is equal to or greater than the Year to Begin Checking Megabeast Percentage ''regardless'' of how many [[megabeast]]s and [[titan]]s are dead — Percentage of Megabeasts and Titans Dead for Stoppage is ignored. The number of megabeasts and titans at the start of the world is set by the sum of the [[Advanced_world_generation#Max_Megabeasts_Caves|Max Megabeasts Caves]] and [[Advanced_world_generation#Titan_Parameters|Titan Number]] parameters.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[BEAST_END_YEAR:<year>:<percentage or -1>]</nowiki></tt>
| <tt><nowiki>[BEAST_END_YEAR:200:80]</nowiki></tt>
| Use -1 as percentage to disable. Year must still be at least 2.
|}

=== Cull Unimportant Historical Figures ===
{{main|Historical figure}}
Whether to remove unimportant dead historical figures after history generation; a short CPU-intensive step, but saves space which can speed up loading, saving, and running games with large histories. Legends mode will refer to culled creatures as "an unknown creature", and they will not appear in engravings, but likely would not have anyway.

Exactly what is considered important is not clear. A member of an abstract group killing a named creature is not. Creating an artifact is not, even if that artifact had important history. Unculled historical figures can have parentage described as "The identity of" that parent "has been lost to time", so just having children is not, though having living direct relations seems to prevent culling.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CULL_HISTORICAL_FIGURES:<0 or 1>]</nowiki></tt>
| <tt><nowiki>[CULL_HISTORICAL_FIGURES:0]</nowiki></tt>
| 0 = No, 1 = Yes
|}

=== Reveal All Historical Events ===

Setting this to Yes will allow access to most information about the history of the world in [[Legends mode]]. All events will be revealed, but some [[historical figure]]s, [[site]]s, [[region]]s, and [[civilization]]s and other entities may not be, possibly because they are not known to any civilization. If set to No, then you will have to discover historical information in [[adventure mode]] or by instructing dwarves to make engravings.{{Verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[REVEAL_ALL_HISTORY:<0 or 1>]</nowiki></tt>
| <tt><nowiki>[REVEAL_ALL_HISTORY::1]</nowiki></tt>
| 0 = No, 1 = Yes
|}

=== Terrain Parameters ===

These set limits and variance for terrain elevation, rainfall, temperature, drainage, volcanism, and savagery which determines how those values are generated. What biomes exist are then determined by how these factors overlap with each other.

==== Minima and Maxima ====
These are the absolute minimum and maximum values that can ever be generated for a particular map square characteristic. By ''subtly'' tweaking the min and max values, vastly different maps can be made. Changing these can cause the occurrence of certain [[Biome|biomes]] to become impossible, so you may want to use [[#Terrain Mesh Sizes and Weights|Weighted Ranges]] instead.

==== X and Y Variance ====
These control how wildly things like elevation and rainfall can vary between adjacent map squares. For example, if these values are set to the maximum of 3,200 for elevation then you will end up with more very low areas right next to very high areas. The number for X determines the east-west variance and the number for Y determines the north-south variance. By setting only one of these to a high value you can, for example, create horizontal or vertical bands of areas which are more similar to each other.

Generally speaking, raising both of these values will create a more random "patchwork" of many small biomes while setting both x and y values to 0 will cause every square on the map to use a single random value for the given characteristic.

For "patchwork" worlds to avoid being rejected, [[#Maximum Number of Subregions|Maximum Number of Subregions]] will probably need to be increased from the default.

==== Elevation ====
This controls the range of terrain elevations that can occur in the world. Usually, you just want to leave the min/max values alone. Raising the minimum elevation can, for example, make it impossible for oceans to exist. This does '''not''' directly control the number of available Z-levels at a particular site, though high maximum values may contribute to peaks, which can raise the number of above ground Z-levels - in other words, a maximum elevation of 400 and minimum of 1 does not mean you get 400 Z-levels, but it might increase the number of Z-levels somewhat in some regions compared to others. Raising the variance will result in a more bumpy, uneven landscape.

Some biomes/features that are impacted by elevation:
* A high minimum (above 99) means no oceans, as they need elevations below 100.
* A low maximum (below 300) means no mountains, as mountains need elevations above 300.
* Rivers will be placed when the elevation maximum is 104 or higher. Therefore, keeping both values above 100 and below 104 will prevent all water tiles from appearing.
* Mountain peaks can only form at elevations of 400.

==== Rainfall ====
Controls the amount of rainfall in each map square/area. Setting the minimum or maximum too high or low can make the formation of certain biomes impossible. Rainfall causes it to [[rain]] more in a given area, which can have various effects. Also makes more rivers appear on the world map.

Note that if [[#Do Orographic Precipitation and Rain Shadows|orographic precipitation and rain shadows]] is on, then mountains will cause additional variance in rainfall, so (for example) rainfall below the specified minimum can occur in the shadow of a mountain. If you want the minimum and maximum for this parameter to be absolutely respected, you must turn off the orographic precipitation option.

Additionally, with 'Orthographic Precipitation' turned on, orthographic precipitation and rain shadows will only occur in regions with greater than or equal to 50 drainage. [http://www.bay12forums.com/smf/index.php?topic=139916.0 [Report, reproduced 2022]]

==== Temperature ====
{{main|Climate|Temperature}}
These parameters control how hot or cold various areas will be. If you lower the minimum and maximum values, the world will be colder overall, for example. As with the others, changing these values too much could make it impossible for certain biomes to exist. The temperature scale used in this setting is related to regular degrees Urist by the equation "local temp = world temp * 0.75 + 10000".{{cite forum|169696/8395484}} This scale doesn't seem to be used anywhere else in the game. See [[Climate]] for more info.

These parameters form the "base" temperature for an area, and describe peak summer temperature in a scale that isn't used elsewhere in the game. This number also does not correspond 1:1 with the final climate. [[Temperature]] is always influenced by a number of variables, including elevation, time of year, thick forestation, and if [[Advanced_world_generation#Poles|poles]] are enabled, latitude. These other variables are factored in after the temperature mesh is applied, and frequently bring temperatures above and below their set minimum and maximum values. ''The inclusion of Poles is particularly strong in this regard, as it allows latitude to raise and/or lower temperatures by more than 75 degrees Celsius! That said, the temperatures aren't raised or lowered by more than about 65 degrees past the set minimum and maximum. Furthermore, for typical ranges, the temperature will never be raised more than about 25 degrees past the maximum (but will still drop up to about 65 degrees Celsius below the minimum).'' (unsure about exact values, research needed)

Elves can spawn where the temperature is 10 degrees or warmer, and humans can spawn where the temperature is 0 degrees or warmer.

==== Drainage ====
Changing drainage parameters will change the way water-affected biomes are formed. Low drainage will contribute to the formation of [[Lake|lakes]], [[River|rivers]], and [[Swamp|swamps]]. High drainage will cause water to sink into the ground rather than sit on the surface, which is important for forming hills.

Lower drainage values have been reported to contribute to the formation of thicker soil layers, though it is currently unknown exactly how other factors (such as elevation or perhaps rain) impact soil formation.

==== Volcanism ====
Volcanism controls the occurrence of igneous [[layer]]s, and the formation of volcanoes. For a volcano to form, a square must have a volcanism value of 100, so reducing the maximum from 100 will make volcanoes impossible. Raising the minimum will increase the rarity of non-igneous layers.

Setting the minimum to a high value is not a good way to produce multiple volcanoes, as you are likely to get a "Volcanism not evenly distributed" rejection. Instead, use the Minimum Number of Volcanoes parameter, and possibly adjust the weighted ranges for volcanism as described below.

==== Savagery ====
These parameters control the level of [[Surroundings#Savage|savagery]] on the map. Raising the minimum savagery too high may make it impossible for certain races to exist, and similarly lowering the maximum too far can make it impossible for certain creatures to exist. The largest chance of having unusable maps comes from a too-high savagery value.

==== Configuration Tokens ====
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[ELEVATION:1:400:401:401]</nowiki></tt>
| Range: 0 to 400 Maximum of 400 required for mountain peaks. Variance range: 0-3200
|-
| <tt><nowiki>[RAINFALL:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[RAINFALL:0:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|-
| <tt><nowiki>[TEMPERATURE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE:25:75:200:200]</nowiki></tt>
| Range: -1000 to 1000 Variance range: 0-3200
|-
| <tt><nowiki>[DRAINAGE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE:0:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|-
| <tt><nowiki>[VOLCANISM:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM:1:100:200:200]</nowiki></tt>
| Range: 0 to 100 Maximum of 100 required for volcanoes. Variance range: 0-3200
|-
| <tt><nowiki>[SAVAGERY:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY:1:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|}

=== Terrain Mesh Sizes and Range Weights ===
[[File:World_map-large-32x32-elevation-mesh.png|thumb|300px|A large world generated with an Elevation Mesh Size of 32×32 and range weights set to 1:0:0:0:1 (i.e., only extreme high and low elevations). Note how the grid intersections are either set very high (mountains) or very low (oceans) and the space between them is smoothed out.]]
These parameters influence the relative proportions of terrain feature ranges, without making other ranges impossible. For example, to have many more low-elevation squares exist, without making it impossible for high elevations; this makes changing these parameters often preferable to simply changing the above min/max values. See the image on the right for an example.

The basic steps of applying weighted ranges are as follows:
# Divide the world into a grid of quantity <code>2''MeshSize'' - 1</code> areas in both X and Y direction.
# At each grid intersection, set the value according to the weighted ranges.
# Smooth out the areas between the intersection points.
# Add noise according to the variance parameters.
Where ''MeshSize'' is the raw parameter value found in the <code>[[world_gen.txt]]</code>.

==== Interaction between Mesh Size and Weighted Ranges ====
Mesh size determines how many intersection points the world will have. As an example, setting it to 2×2 means the world will be divided into 4 areas, 2 across and 2 tall, and there will be a total of 9 intersection points (3×3). The grid intersection points are in the middle of world tiles, and the minimum size for a grid area is a span of 9 world tiles in either direction, with adjacent areas sharing an overlapping world tile. On a pocket world, this means one grid tile will span 9×9 world tiles, whereas on a large world, one grid tile will span 129×129 world tiles. A pocket world will always use a 2×2 grid of 9×9 world tiles, since it has only 17×17 tiles total (even if the game UI allows setting those worlds to a 4×4 grid, which can happen when changing the world size; changing the world size doesn't adjust mesh size limits, but saving then reloading the parameters does). A world that is 17 tiles wide, but 257 tall, and set to a 32×32 mesh size, will have 3×33 intersection points.

Setting mesh size to something other than Ignore, will apply random values at those intersections, with those random values being more likely to be in the ranges with higher weights. Setting to Ignore will cause the weighted range settings to be ignored for that terrain characteristic; instead setting the 4 corners of the world to completely random values and smoothing between those.

For example, if the Elevation Weighted Range parameters are set to <code>60:10:10:10:10</code> (starting with the 0-20 range, and these values do not need to add up to any particular number), and elevation min and max are left at the defaults of 1 and 400 respectively, then about 60% (on average) of the grid line intersection points will be set to an elevation in the range of 1-80 (0% to 20%), and the other ranges will be represented by around 10% of the intersection points each. The exact distribution is still left up to chance, though ''on average'' it will be close to this specification. This allows random number generation to be non-linear for the given terrain characteristic.

Setting the weight for a range to None only prevents intersection points from being set to a value in that range; terrain between intersection points can still be smoothed to values in ranges set to None that are between the intersection point values. Setting all the weights to None just puts them all at the same weight, the same as the default of all at 1.

Weighted ranges do not make rejection checks, although they can be responsible for many rejections if you neglect to adjust or disable some of the [[#Minimum Number of Mid/Low/High Characteristic Squares|Minimum Number of Mid/Low/High Characteristic Squares]], for example.

==== Interaction between these and Variances ====
The end result can vary greatly depending on how the corresponding [[#X_and_Y_Variance|X and Y Variance]] parameters are set. First of all, if the variance is too high, the noise it adds can completely negate the effect of the weighted ranges. For instance, with a 2×2 mesh, the default variance parameters are high enough that usually the mesh grid can hardly be recognized. How strong the variance's effect is, is also dependent on the mesh size. Having a larger mesh size (i.e. smaller grid tiles) means the variance also has to be higher for a visible effect. For instance, with a variance of 400, the effects are clearly visible with a 2×2 mesh and barely visible at all with a 8×8 mesh. Note that this effect is directly dependent on the mesh size and not, as one might expect, on the actual size of the grid tiles. This means, that a large world with a 32×32 mesh will look essentially the same as a pocket world with a 2×2 mesh, only stretched to 256 times the size.

Also see this [http://www.bay12forums.com/smf/index.php?topic=139916.0 forum post] for more details.

==== Configuration Tokens ====
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[ELEVATION_FREQUENCY:2:1:2:3:4:5]</nowiki></tt>
| rowspan="6" | Valid mesh values:

1 = Ignore

2 = 2x2

3 = 4x4

4 = 8x8

5 = 16x16

6 = 32x32

(limited by world size)
|-
| <tt><nowiki>[RAIN_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[RAIN_FREQUENCY:3:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[DRAINAGE_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE_FREQUENCY:4:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[TEMPERATURE_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE_FREQUENCY:1:1:1:1:1:1]</nowiki></tt>
|-
| <tt><nowiki>[SAVAGERY_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY_FREQUENCY:5:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[VOLCANISM_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM_FREQUENCY:1:1:1:1:1:1]</nowiki></tt>
|}

=== Poles ===

With this, you can influence how polar regions are added. The poles can be on the north or south edge, and the equator will be on the opposite edge, or in the middle if there are two poles. If poles are set to NONE, then there will be no seasonal changes in the weather (e.g. no winter snow in temperate biomes).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[POLE:<placement>]</nowiki></tt>
| <tt><nowiki>[POLE:NORTH]</nowiki></tt>
| Viable options: NONE, NORTH_OR_SOUTH, NORTH_AND_OR_SOUTH, NORTH, SOUTH, NORTH_AND_SOUTH
|}

=== Minimum Mountain Peak Number ===

This will cause the world to be rejected if fewer than this many peaks (based on elevation) are present on the map. EG: elevations of 400 must be possible for mountain peaks to occur. If set to zero, then worlds will not be rejected based on number of peaks.

You may need to adjust elevation parameters, such as the highest weighted range, in order to get the desired number of elevation-400 squares needed for larger numbers of peaks. Like volcanoes, mountain peaks can make embark zones more interesting, but other than that, they don't appear to "do" anything special. Reportedly, they do increase the highest Z-level above ground in all embark zones in the same region, even if the selected embark zone does not include the peak.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PEAK_NUMBER_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[PEAK_NUMBER_MIN:20]</nowiki></tt>
| Elevations of 400 must occur for peaks to form.
|}

=== Minimum Partial Edge Oceans ===

This will cause a world to be rejected unless there are at least this many oceans touching an edge of the map. If set to zero then worlds will not be rejected based on this criterion. Setting both this parameter and Minimum Complete Edge Oceans to values that total more than 4 when added together may cause all worlds to be rejected as you can't have both a partial and complete edge ocean on a given edge.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PARTIAL_OCEAN_EDGE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[PARTIAL_OCEAN_EDGE_MIN:2]</nowiki></tt>
| Maximum of 4
|}

=== Minimum Complete Edge Oceans ===

This will cause a world to be rejected unless there are at least this many oceans which completely cover an edge of the map. Since a square map only has 4 edges, the maximum value possible is 4. If set to zero then worlds will not be rejected based on this criterion but still might end up with complete edge oceans by chance.

Note that the ability for this many edge oceans to exist will be limited by elevation. Therefore, to actually create large oceans you will probably need to change things like the Elevation Mesh Size and Weighted Ranges to increase the number and distribution of very low elevation squares on the map. In addition, if Complete Edge Oceans is set to any value ''other'' than 0 or 4, you may need to lower elevation variance for at least one of the axes: if set too high, such as a variation of 1600 for both X and Y axes (the default for Large Island and Medium Island parameter sets), the game may generate worlds very slowly or even hang.{{bug|565}}

Given appropriate weight, range, and variance values for things like elevation, a setting of: 1 results in a world that seems like a chunk of coastline. One edge of the map will be completely underwater and there will be ocean taking up much of the map on that side (think the east or west coast of the United States, the north coast of Canada, or southern Europe). If your edge ocean happens to pick your world's frozen side, most of it will be glacier.

*2 results in another coastline along with the first one -- the map could end up looking something like Panama if the oceans pick opposite sides of the map.
*3 results in a peninsula, like Florida in the US. There will be oceans surrounding 3 sides of the map, and land touching only one side of the map.
*4 results in one or more island(s) depending on things like elevation variance and weights. Regardless of whether you get one island or multiple islands, the entire map will be surrounded by water.

Unfortunately, there's no easy way to control which oceans end up on which edges, except perhaps setting X/Y variance to different values.

Edge oceans will take up part of the other edges too. For example, a full edge ocean on the east side will have part of the north and south sides underwater, but that does ''not'' add to the ''partial'' edge oceans count.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[COMPLETE_OCEAN_EDGE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[COMPLETE_OCEAN_EDGE_MIN:0]</nowiki></tt>
| Maximum of 4
|}

=== Minimum Volcano Number ===

The game will attempt to place this many volcanoes, but there must be at least this many squares with a volcanism of 100, if there are not the world will be rejected. Therefore, [[Advanced_world_generation#Volcanism|maximum volcanism]] above must be set to 100, and adjusting the [[Advanced_world_generation#Configuration_Tokens_2|volcanism weighted range]] above for 80-100 to a higher value can increase the number of those squares.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[VOLCANO_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[VOLCANO_MIN:15]</nowiki></tt>
| Volcanoes require a volcanism of 100 to occur.
|}

=== Mineral Scarcity ===
Controls the frequency at which minerals occur; setting this value higher will decrease both the number of different types and amounts of ore and gems present on a map. The default value will result in many metal ores, while the old default of ''sparse'' would be only a few ores, which may be limiting until other metals can be requested and traded for.

The options "Very Rare", "Rare", "Sparse", "Frequent", and "Everywhere" in the [[World_generation#Basic_world_generation_menu|basic world generation menu]] use the values 50000, 10000, 2500, 500 and 100 respectively.

According to [http://www.bay12forums.com/smf/index.php?topic=79018.msg2063804#msg2063804 research] by Shandra in v0.31.25, this is the relationship between the value of this setting and the approximate number of gems and ore:

[[File:MineralSetting_v25_limit10k.png]]

This is for the same 8x8 embark region in a world which is otherwise the same, except for the mineral scarcity parameter (although most of the detailed information comes from experiments with previous versions). (The chart legend has an error, the first "Pot.(Types)" should read "Pot.(Amount)".)
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MINERAL_SCARCITY:<number>]</nowiki></tt>
| <tt><nowiki>[MINERAL_SCARCITY:100]</nowiki></tt>
| Range: 100 to 100,000
|}

=== Max Megabeast Caves ===

This is the number of [[megabeast]]s placed at the beginning of history. Megabeasts are [[hydra]]s, [[bronze colossus]]es, [[roc]]s, and [[dragon]]s, which are all placed in equal proportions [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415177#msg3415177 data].

Increasing this value can lead to early extinction of civilizations.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[MEGABEAST_CAP:75]</nowiki></tt>
| Megabeasts count towards BEAST_END_YEAR calculation.
|}

=== Max Semi-Megabeast Caves ===

This is the number of [[semi-megabeast]]s placed at the beginning of history. Semimegabeasts are [[giant]]s, [[ettin]]s, [[minotaur]]s, and [[cyclops]], which are placed in equal proportions [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415188#msg3415188 data].

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEMIMEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SEMIMEGABEAST_CAP:150]</nowiki></tt>
| Semimegabeasts do not count towards the BEAST_END_YEAR calculation.
|}

=== Titan Parameters ===

==== Number ====

This controls the number of [[titan]]s that exist at the beginning of history[http://www.bay12forums.com/smf/index.php?topic=112465.msg3415203#msg3415203 data]. The number of forgotten beasts is unaffected by this parameter [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415155#msg3415155 data].

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TITAN_NUMBER:33]</nowiki></tt>
| Titans count towards BEAST_END_YEAR calculation.
|}

==== Attack Population Requirement ====

[[Titan]]s will begin to attack your fort once at least this many dwarves inhabit it, regardless of whether any other attack criteria have been met.

This number defaults to 80, which isn't usually too difficult to deal with.

==== Exported Wealth Requirement ====

Titans will begin to attack your fort once you have exported at least this many [[Currency|dwarfbucks]]-worth of goods, regardless of whether or not any other criteria have been met. This parameter defaults to None (disabled).

==== Created Wealth Requirement ====

Titans will begin to attack your fort once the fort's total wealth has reached this many [[Currency|dwarfbucks]] in value. This happens regardless of whether any of the other criteria, such as population, have been met; therefore, even with 1 dwarf, a fort could be attacked if the fort were worth at least this value.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_ATTACK_TRIGGER:<population>:<exp wealth>:<created wealth>]</nowiki></tt>
| <tt><nowiki>[TITAN_ATTACK_TRIGGER:80:0:100000]</nowiki></tt>
| 0 = None (disabled). Only one requirement must be met for an attack.
|}

=== Number of Demon Types ===

[[Demon]]s are similar to [[titan]]s and [[forgotten beast]]s, in that they are procedurally generated, but most are not unique. Thus, many different types of demons can exist in the world, but there will also be many individuals of most types. Thanks to [[Underworld spire|certain fun things]], fewer demon types also means fewer goblin civilizations.{{cite forum|112465/7392706}} You need at least 2 demon types, or else goblin civilizations won't exist initially, though if dwarves breach the underworld during world generation, at least one will be generated then.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DEMON_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[DEMON_NUMBER:52]</nowiki></tt>
| 0 to 1000
|}

=== Number of Night Troll Types ===

The number of different [[night troll]]s, also procedurally generated, that will exist in the world. Setting this to zero means that the world will have no night trolls, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[NIGHT_TROLL_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[NIGHT_TROLL_NUMBER:77]</nowiki></tt>
| 0 to 1000
|}

=== Number of Bogeyman Types ===
The number of different [[bogeyman]] forms that will exist in the world. Bogeymen are procedurally generated, though their forms do not vary by much. Setting this to zero means that the world will have no bogeymen, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[BOGEYMAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[BOGEYMAN_NUMBER:27]</nowiki></tt>
| 0 to 1000
|}

=== Number of Nightmare Types ===
The number of different [[nightmare]] forms that will exist in the world. Nightmares are procedurally generated. Setting this to zero means that the world will have no nightmares, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[NIGHTMARE_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[NIGHTMARE_NUMBER:27]</nowiki></tt>
| 0 to 1000
|}

=== Number of Vampire Curse Types ===

The number of different types of [[Vampire|vampires]] that will exist in the world. Although they are generated at the start of a new world, they aren't different from each other. Setting this to zero means no vampires will exist.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[VAMPIRE_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[VAMPIRE_NUMBER:72]</nowiki></tt>
| 0 to 1000
|}

=== Werebeast Parameters ===

==== Number of Werebeast Curse Types====

The number of different types of [[werebeast]]s that can exist in the world. It is common for werebeasts, unlike vampires, to assume many different forms and variations, the most well-known of these amount to different species of animals, from lizards, to wolves, to even bears. Setting this to zero means no werebeasts will exist, and will also remove a large amount of [[fun]] from the game.

In vanilla, there are only 82 possible unique werebeast species. Any further species will generate as wereblobs.{{bug|13308}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[WEREBEAST_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[WEREBEAST_NUMBER:58]</nowiki></tt>
| 0 to 1000
|}

==== Attack Population Requirement ====

Werebeasts will begin to attack your fort once at least this many dwarves inhabit it, regardless of whether any other attack criteria have been met. This number defaults to 50 which will often be reached in the second year of the fort.

==== Exported Wealth Requirement ====
Werebeasts will begin to attack your fort once you have exported at least this many [[Currency|dwarfbucks]]-worth of goods, regardless of whether or not any other criteria have been met. This parameter defaults to 5000.

==== Created Wealth Requirement ====

Werebeasts will begin to attack your fort once the fort's total wealth has reached this many [[Currency|dwarfbucks]] in value. This happens regardless of whether any of the other criteria, such as population, have been met; therefore, even with 1 dwarf, a fort could be attacked if the fort were worth at least this value.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[WEREBEAST_ATTACK_TRIGGER:<population>:<exp wealth>:<created wealth>]</nowiki></tt>
| <tt><nowiki>[WEREBEAST_ATTACK_TRIGGER:50:5000:50000]</nowiki></tt>
| 0 = None (disabled). Only one requirement must be met for an attack.
|}

=== Number of Secret Types ===

The number of secrets that exist in the world. Currently, all secrets are secrets of life and death, and the ones holding these secrets are [[necromancer]]s, thus, setting this to zero means that no necromancers will appear.
Non-necromancer towers can still appear (extremely rarely) with zero secrets, constructed by independent undead groups.
The primary difference between having 1 or 1000 secrets is the chance of your world having any necromancer towers at all. With 1, this chance is low. With the default number, it's seemingly guaranteed.
Even with 1 secret, if you have any necromancer towers at all, it is likely a great number will quickly appear in world generation (though this isn't guaranteed).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SECRET_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[SECRET_NUMBER:52]</nowiki></tt>
| 0 to 1000
|}

=== Number of Regional Interaction Types ===

The number of interactions that can be caused in regions, which may incorporate evil rain and cloud types. Currently, only evil region interactions are generated this way.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[REGIONAL_INTERACTION_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[REGIONAL_INTERACTION_NUMBER:20]</nowiki></tt>
| 0 to 1000
|}

=== Number of Disturbance Interaction Types ===
The number of different [[Mummy|disturbed dead]] that can exist in the world. Setting this to zero should prevent any mummy from appearing{{verify}}, but it will not prevent the creation of [[tomb]]s.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DISTURBANCE_INTERACTION_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[DISTURBANCE_INTERACTION_NUMBER:10]</nowiki></tt>
| 0 to 1000
|}

=== Number of Evil Cloud / Evil Rain Types ===

This number specifies how many [[Weather#Evil weather|various face-melting, eye-boiling, and zombifyingly-fun]] clouds of pure evil may appear in your world. Setting this to zero means you no longer will ever have to deal with encroaching dust walls of doom in that world. It is generally advised to keep this value low...

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EVIL_CLOUD_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[EVIL_CLOUD_NUMBER:45]</nowiki></tt>
| 0 to 1000
|}

The latter number states how many different types of green-ooze drenchers, disconcerting blood-showers, and sickly yellow slime-baths can occur in your world. Compared to evil clouds though, this one hardly is worth stressing out about, usually.... Setting this to zero means the only semi-solid to fully-liquid fluids to fall from the sky will be pure H2O.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EVIL_RAIN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[EVIL_RAIN_NUMBER:352]</nowiki></tt>
| 0 to 1000
|}

=== Generate Divine Materials ===
This turns the generation of [[Divine_metal|divine metals]] on or off. It does not influence the creation of [[vault]]s. Probably determines whenever or not using divination dice spawns weapons.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GENERATE_DIVINE_MATERIALS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[GENERATE_DIVINE_MATERIALS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Generate Mythical Materials ===

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GENERATE_MYTHICAL_MATERIALS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[GENERATE_MYTHICAL_MATERIALS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Mythical Healing ===

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALLOW_MYTHICAL_HEALING:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_MYTHICAL_HEALING:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Divination, Experiments, and Necromancy types ===
These allow or disallow [[die|divination]], demon or necromancer [[experiment]]s, and the more advanced [[necromancer]] abilities.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALLOW_DIVINATION:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_DIVINATION:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_DEMONIC_EXPERIMENTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_DEMONIC_EXPERIMENTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_EXPERIMENTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_EXPERIMENTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_LIEUTENANTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_LIEUTENANTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_GHOULS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_GHOULS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_SUMMONS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_SUMMONS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Desired Good/Evil Square Counts ===

These values change the amount of [[Surroundings#Good|good or evil]] tiles on the map, depending on the size of the region they are being considered for. The counts are for all tiles in all subregions of a given size considered together, ''not'' counts for each subregion considered separately (all tiles in the same subregion share the same [[surroundings]] values).

As used here, a "subregion" is a named world area. Subregion names and locations for a generated world are viewable in legends mode under "Regions". Subregions are classified by size the same way for all map sizes: 1-24 tiles is Small, 25-99 tiles is Medium, and 100+ tiles is Large.

The counts used here will always be restricted to regions of the given size, no matter how large the count. Also, the count is more of a goal than a minimum or maximum. As a result, you can end up with many more or many fewer than the requested number of squares in some situations. In particular, if you have something like a case where only 3 large regions exist in a world, and you request "1 evil square" in large regions, you will end up with one of the large regions being ''entirely evil''. So any non-zero value in one of these settings essentially means "force at least one region of this size to be all good/evil."

Note that the "evilness" of evil biomes is also impacted by savagery. Certain civilizations cannot exist in good and/or evil squares, so too many of one or the other may limit the size of certain types of civilizations - dwarves, for example, need non-aligned biomes. Creating too many evil biomes seems to lead to the danger of many civilizations' early extinction.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GOOD_SQ_COUNTS::<med region>:<lg region>]</nowiki></tt>
| <tt><nowiki>[GOOD_SQ_COUNTS:100:1000:2000]</nowiki></tt>
| rowspan="2" | Set count to zero to disable for that region size.
|-
| <tt><nowiki>[EVIL_SQ_COUNTS::<med region>:<lg region>]</nowiki></tt>
| <tt><nowiki>[EVIL_SQ_COUNTS:100:1000:2000]</nowiki></tt>
|}

=== Minimum Biome Square Counts ===

These numbers control whether or not a world will be rejected based on a lack of different [[biome|biomes]]. Raising these numbers will '''not''' automatically generate the given number of squares of the given biome! For a biome to exist, certain conditions like elevation and rainfall must exist.

These parameters simply filter out worlds that (for example) randomly fail to have enough high elevation squares to support a given number of mountains, etc. Some settings may cause worlds to always be rejected. For example, if for some reason the maximum elevation parameter is set to a value below what will support mountain biomes, it will be impossible to satisfy a non-zero requirement for mountain squares. The same principle goes for other conditions and biomes such as low elevations and oceans, etc.

Certain civilizations require different biomes to exist (such as dwarves and mountains), so eliminating certain biomes will make it impossible for certain civilizations to form.

These parameters often result in infinite world rejection problems. See [[World rejection]] for information on solving problems related to worlds always being rejected due to one or more of these parameters.

0 means no minimum for rejection - setting it to 0 does not guarantee 0 squares of that biome.

==== Biome Type Requirement Table ====

Terrain requirements for various biomes are described below.{{Verify}} Note that some of the exact ranges are unknown.

{| {{prettytable}}
|- bgcolor="#dddddd"
! rowspan="2" | Biome
! colspan="4" | Terrain Requirement
|-
! Elevation
! Rainfall
! Temperature
! Drainage
|-
| Swamp/Marsh
| 100-299
| 33-100
| Non-Freezing
| 0-32
|-
| Desert/Badland
| 100-299
| 0-9
| non-freezing
| note1
|-
| Forest
| 100-299
| 66-100
| non-freezing
| 66-100
|-
| Mountains
| 300-400
| N/A
| N/A
| N/A
|-
| Ocean
| 0-99
| N/A
| N/A
| N/A
|-
| Glacier
| 100-299
| N/A
| Freezing
| 80(?)-100
|-
| Tundra
| 100-299
| N/A
| Freezing
| 0-66
|-
| Grassland
| 100-299
| 0-66
| Non-Freezing
| 0-66
|-
| Hills
| 100-299
| 0-66
| Non-Freezing
| 66-100
|}
note1 drainage: 00-32 sand desert, 33-49 rocky wasteland, 50-65 rocky wasteland but different characters/appearance, 66-100 badlands

==== Minimum Initial Square Count ====

'''Note: The exclusive purpose of these parameters is to cause world rejection.'''

This is the minimum number of squares of the given biome that must exist before things like erosion take place. One thing to keep in mind is the maximum number of squares on a map of a given size - if the total number of squares on a map is lower than the sum of all square count parameters, then you will get infinite world rejection.

To determine the number of squares on a map, just multiply the dimensions. In practice these parameters will need to sum to lower than the maximum because some space is needed for "slack".

{| {{prettytable}}
|- bgcolor="#dddddd"
! Map Size
! Number of Squares
|-
| 17×17
| 289
|-
| 33×33
| 1089
|-
| 65×65
| 4225
|-
| 129×129
| 16614
|-
| 257×257
| 66049
|}

==== Minimum Initial Region Count ====

This is the minimum number of regions of contiguous biome squares that must exist before other processes such as erosion take place.

==== Minimum Final Region Count ====

This many regions of the given biome must exist after erosion and similar phases of generation have been completed.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[REGION_COUNTS:SWAMP:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:SWAMP:1032:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:DESERT:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:DESERT:1032:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:FOREST:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:FOREST:4128:13:12]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:MOUNTAINS:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:MOUNTAINS:8256:9:9]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:OCEAN:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:OCEAN:8256:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:GLACIER:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:GLACIER:0:0:0]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:TUNDRA:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:TUNDRA:0:0:0]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:GRASSLAND:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:GRASSLAND:8256:13:12]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:HILLS:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:HILLS:8256:13:12]</nowiki></tt>
|}

=== Erosion Cycle Count ===

Tells the world generator how long the world has to erode its tall peaks down to mountainsides during the 'running rivers...' stage of world creation. The higher this number, the less jagged the world will be, and the more wide the major rivers will be. If you use the maximum number, your mountains will dissolve before your eyes into plains which can lead to rejections if there aren't enough mountains to use for river start points and dwarven civilization origin points.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EROSION_CYCLE_COUNT:<number>]</nowiki></tt>
| <tt><nowiki>[EROSION_CYCLE_COUNT:250]</nowiki></tt>
| Range: 0 to 1000
|}

=== Minimum/Desired River Start Locations ===

This is the minimum number of riverheads that must exist before and after erosion takes place. Worlds will be rejected if they fail to meet these numbers. As with minimum biome counts, raising this number doesn't automatically create this many riverheads. Other conditions like terrain and rainfall must exist for rivers to form.

Extremely high pre-erosion values speed erosion greatly, while low post erosion values are useful for limiting rejects due to lack of river origin points. One can try the 800 value to get more lakes.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[RIVER_MINS:<min pre-erosion>:<des post-erosion>]</nowiki></tt>
| <tt><nowiki>[RIVER_MINS:200:400]</nowiki></tt>
| Range: 0 to 800
|}

=== Periodically Erode Extreme Cliffs ===

If enabled, makes every impassable rock wall into a series of ramps. Some prefer to pump up erosion to about 250, and turn the "Desired pre-erosion river count" to 0 for good erosion and no extra canyons.

Normally this is set to Yes (1).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PERIODICALLY_ERODE_EXTREMES:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[PERIODICALLY_ERODE_EXTREMES:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Do Orographic Precipitation and Rain Shadows ===

Toggle that allows terrain height to affect rainfall. For example, moist air coming from the ocean blows over the land. As the terrain gets higher, it forces the moist air up, causing it to rain on the seaward side of a mountain. Eventually, all the rain has fallen if the mountain is tall enough. So, when the breeze goes over the top, there's no moisture left to fall on the other side, creating a rain-shadow. In the current version, regions where drainage is above 50 will also create rain shadows, regardless of the underlying biome and elevation.{{cite forum|140685/5484064}}

Turning this on should create a tendency for more extreme rainfall in regions, creating more forests, deserts, marshlands, and grasslands. Also note that it can create rainfall outside of min-max rainfall settings, so even in a world with a 0 max rainfall you may get rainfall biomes. Turning it off should result in more controllable, less complex rainfall conditions based on rainfall parameters as it adds a random element which can distort or otherwise mess up the climates on a pregenerated map.

This should be disabled if you're importing a map or using a preset map file that has weather.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[OROGRAPHIC_PRECIPITATION:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[OROGRAPHIC_PRECIPITATION:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Maximum Number of Subregions ===

This is the number of separate biomes (the flashing regions you see on embark when you hit F1, F2, etc. when there's more than one biome on the embark location) that are allowed to exist on the entire map.

Setting this to very low values will result in numerous rejections depending on [[#X and Y Variance|variance parameters]]. If variance values are set to high numbers, many small biomes will be created causing rejection if this parameter value is not increased beyond the default.

Increasing the value of this tag is often a must when generating "patchwork" worlds with lots of biome variance, but simply increasing it without increasing variance parameters will not guarantee more biomes.

It is also interesting to note that the maximum subregions is 5000 which is more than the total number of squares for a pocket or small map. However, for a medium or large map (16641 or 66049 squares) it quickly becomes a mere fraction of the total number of possible subregions. In fact it would be quite easy on a large map to end up with far too many subregions and get endless rejections of this type.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SUBREGION_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[SUBREGION_MAX:2750]</nowiki></tt>
| Range: 1 to 5000
|}

=== Cavern Parameters ===
[[Caverns]] are the hollow areas underground, which dwarves tend to encounter when they're digging around. The '''Cavern Layer Number''' parameter determines how many cavern systems will be generated, not including the magma layer or the Bottom layer. Defaults to three - setting it to lower values could help FPS. Setting it to 2 will merge cavern 3 species into the 2nd cavern, and setting it to 1 will merge all into one cavern. However, disabling them entirely by setting it to 0 will make it impossible to grow any underground plants, as none will exist for your civilization to cultivate, nor will they be available on embark.

*Setting caverns to a sub-3 number (Spoiler, highlight to view) erases about one-third of HFS spires{{Bug|10267}} and prevents dig deep disasters. Additionally, random plant or animal species can be more frequently absent.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_COUNT:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_COUNT:3]</nowiki></tt>
| Range: 0 to 3
|}

==== Cavern Layout Parameters ====

Open caverns and dense passageways are not mutually exclusive. When both are raised, bizarre results can occur, such as layers showing a combination of open caverns, a cluster of network passages, and natural walls sprinkling the inside of an otherwise open cavern. [http://www.bay12forums.com/smf/index.php?topic=76355.msg1936859#msg1936859 Reference]

If you want the largest open spaces possible, then decrease the density and increase the openness. If you want a labyrinth of passageways, lower the openness and raise the passage density.

Another interesting note about the cavern layers is that the seed and number of demon types affect the layout of the caverns.

<gallery widths=200 heights=200 perrow=2>
File:Open00Density100.jpg|Cavern slice with Openness of 0 and Density of 100
File:Open100Density00.jpg|Cavern slice with Openness of 100 and Density of 0
File:Open100Density100.jpg|Cavern slice with Openness of 100 and Density of 100
File:Open50Density50.jpg|Cavern slice with Openness of 50 and Density of 50
</gallery>

===== Layer Openness min/max =====

Dictates the size of cavern passages. When Passage Density (see below) is set to minimum (0), caverns will be open expanses. Raising the maximum will increase the size of the caverns.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MAX:100]</nowiki></tt>
|}

===== Layer Passage Density min/max =====

Determines how many passages form the cavern. If openness (see above) is set to minimum and density increased, then you will get a maze-like network of small criss-crossing passages. Raising the values further increases the number of the maze-like passages.

Caverns will be large, open spaces at 0, and comprised of many small vertical shafts of rock at 100. Setting both values to be the same results in a uniform look for the caverns.{{Verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MAX:100]</nowiki></tt>
|}

===== Layer Water min/max =====

Determines the minimum and maximum percentage of water each cavern can contain.

Caverns with a water level of 10 or higher can support creatures and plants from the "Subterranean Water" biome, and caverns with a water level of 90 or lower can support the "Subterranean Chasm" biome; levels of 10-90 support ''both'' biomes, while levels below 10 or above 90 support only one.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_WATER_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_WATER_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_WATER_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_WATER_MAX:100]</nowiki></tt>
|}

==== Magma Layer ====

This parameter controls whether the [[magma sea]] exists.

Setting 1/Yes causes the magma layer to exist, value 0/No prevents it. Appears not to have any impact on volcanoes nor volcanism, so even if 0/No, there will still be embark locations with magma. If a [[volcano]] exists, it appears to always tap the magma sea, but the magma sea will not be revealed by revealing the volcano.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[HAVE_BOTTOM_LAYER_1:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[HAVE_BOTTOM_LAYER_1:1]</nowiki></tt>
|}

==== Bottom Layer ====

Determines if the space below the magma sea exists. If Yes the "HFS" layer is always present. Normally you want to leave this set to Yes for maximum fun.

If enabled, this will force the magma layer above it.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[HAVE_BOTTOM_LAYER_2:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[HAVE_BOTTOM_LAYER_2:1]</nowiki></tt>
|}

=== Z Levels (Depth) Settings ===

These parameters control the "thickness" of various "layers" on the map. Note that a "layer" in this case does not refer to one Z-level, but refers to a number of related Z-levels such as "levels above ground".

The following table assumes that you have 3 cavern layers. (out of a minimum of 0-3) The Levels Above Layer settings control how many Z-Levels are above each layer. A layer may itself consist of multiple Z-Levels (and almost always does).

{|style="margin:1em 1em 1em 0;background:#F9F9F9;border:1px #AAA solid;border-collapse:collapse;" class="wikitable"
|-style="background:#F2F2F2;text-align:center;"
!style="border:1px #AAA solid;padding:0.2em;" width="120"|Setting Name
!style="border:1px #AAA solid;padding:0.2em;" width="200"|Token
!style="border:1px #AAA solid;padding:0.2em;"| Description
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Ground
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_GROUND:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| The number of Z-levels of air above the highest surface level. Has no impact on how many Z-levels deep the surface layer is.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above layer 1
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_1:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of stone above the first cavern layer. Making this higher will guarantee ''at least'' that many levels to build your fortress, but will have no impact on how many z-levels thick the surface layer is. Also, the top of a cavern may be higher than the rest of a cavern, so in practice there will be more "solid" levels than this above the cavern.
As of version 0.31.25 this setting is inaccurate. The actual number of z-levels may vary in a range of approx. ±5, which may result in non-existence of any solid z-levels between a surface layer and first cavern layer.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 2
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_2:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very top of the second cavern and the very bottom of the first cavern.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 3
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_3:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very top of the third cavern and the very bottom of the second cavern.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 4
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_4:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very highest magma and the very bottom of the third cavern. Spoiler Hidden (select invisible text to read): Making this high will give a large area for HFS veins, so that it never touches caverns, giving more to mine '''if''' it was impacting the cavern previously.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 5
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_5:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Uncertain. May control the number of levels of "Semi Molten Rock" between HFS and Magma, may control number of levels of magma, may impact both. In experimentation, the overall depth of all magma sea and semi-molten rock levels appears to increase, but not consistent enough to say for certain. Only valid if Magma Layer present. Spoiler Hidden:Often the HFS vein will only extend as high as the highest magma, making this the only guaranteed way to increase amount of HFS to mine, but unfortunately also creating enormous useless semi-molten z-levels
|-
|style="border:1px #AAA solid;padding:0.2em;"| At Bottom
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_AT_BOTTOM:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Appears to be number of levels of HFS chamber. Only valid if Bottom Layer present, often having no impact. Values larger than default result in strange things.
|}

Some implications:
* The number of surface layers (e.g. soil), at this time, cannot be controlled. For example, on a map with 1 layer of peat, then a layer of silt, then a layer of obsidian, there is no control to let you increase either one to be, say, 20 z-levels. (though you may get lucky with the obsidian).
* There can be multiple stone layers between the cavern and the surface, so, increasing Levels Above Layer 1 may give you more conglomerate or more granite, and you have no control over which stone layer spans those Z-levels.
* The layers shown on embark span across the cavern layers in an unknown and inconsistent way. Sometimes those 10 different layers of stone are evenly distributed over your 400 z-level deep map, sometimes the first 9 get 1 z-level each and the last gets the other 391 levels. No way to control found yet.
* The HFS chamber, if present, will always extend into the rock layers, and appears to always make contact with the bottom cave. Large values for levels above layer 5 and layer 4 can result in enormous chambers, but the number of levels at the top (the part with undead) appears to be unaffected.
* Unconfirmed whether number of levels between caverns has any impact on cavern height. There will be connecting ramps and/or shafts between cavern layers no matter how many levels are between them.
* '''Very Important''': These values appear to apply across a whole 16x16 region, not just embark areas. That means that if a 16x16 region is completely flat, but has one tall mountain in one far corner, even if you set Levels Above Ground low (e.g. 2 z-levels) you still have all the empty air of the highest mountain in every embark tile (e.g. 200 z-levels). Also can happen to the semi-molten layer, and can lead to unexpected behavior.
* Very large or small values can cause strange things to happen.

=== Minimum/Maximum Natural Cave Size ===
It's not clear what effect these currently have, other than changing them can change the location of caves somewhat.{{verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVE_MIN_SIZE:<number>]</nowiki></tt>
| <tt><nowiki>[CAVE_MIN_SIZE:5]</nowiki></tt>
| rowspan="2" | Range: 1 to 500
|-
| <tt><nowiki>[CAVE_MAX_SIZE:<number>]</nowiki></tt>
| <tt><nowiki>[CAVE_MAX_SIZE:25]</nowiki></tt>
|}

=== Number of Caves ===
The number of caves generated in mountainous and non-mountainous regions, mountain caves will always be generated on the edge of mountain ranges next to non-mountainous regions. Lurking [[kobold]]s set up shop in caves, and store their stolen items there - a setting of 0 in both will stop kobold civilizations from appearing. Special note: a cave is not initially a [[lair]], although beasts can later use them as their lair.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[MOUNTAIN_CAVE_MIN:100]</nowiki></tt>
| rowspan="2" | Range: 0 to 800
|-
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:200]</nowiki></tt>
|}

=== Number of Mythical Sites ===
The number of [[mysterious dungeon|mysterious sites]] generated around the world. The extended effects of setting this to 0 has not been determined{{verify|is chosen still available? is quest still given? etc.}}.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MYTHICAL_SITE_NUM:<number>]</nowiki></tt>
| <tt><nowiki>[MYTHICAL_SITE_NUM:200]</nowiki></tt>
| rowspan="2" | Range: 0 to 800
|}

=== Make Caves Visible ===
If set to no (default) then the location of caves will not be marked on the map. If set to yes, caves will appear on the map so that they may be sought out or avoided as desired.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALL_CAVES_VISIBLE:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALL_CAVES_VISIBLE:0]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Init Options to Show Tunnels ===

If enabled, you will be able to see the underground tunnels often built by dwarves on the world map, and they will appear as black lines, similar to roads.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SHOW_EMBARK_TUNNEL:<0-2>]</nowiki></tt>
| <tt><nowiki>[SHOW_EMBARK_TUNNEL:2]</nowiki></tt>
| 0 = No 1 = Only in Finder 2 = Always
|}

=== Number of Civilizations ===

This number of [[civilization]]s will be placed on the map before history generation begins. These civilizations may later die out due to historical events. It is noteworthy that the chance for any given civilization to be destroyed through megabeasts decreases with a higher total number of civilizations present[http://www.bay12forums.com/smf/index.php?PHPSESSID=7348f68f41a9659443c05b2acf534e6c&topic=112465.15 data]. The five races are dwarf, elf, human, goblin, and kobold; they will generally be placed in equal numbers until the quota has been reached. If there are not enough biomes or other worldgen prerequisites for an even distribution, certain civs will be much more or less frequent than others[http://www.bay12forums.com/smf/index.php?PHPSESSID=7348f68f41a9659443c05b2acf534e6c&topic=112465.15 data]. If there is an odd number of civs (not divisible by 5), then the remainder is distributed randomly. Kobold civs require caves to be placed; if no caves exist, then kobolds are skipped and will not appear. This does not cause rejections [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415125#msg3415125 data]. Goblin civilizations require multiple demons, see the [[#Number_of_Demon_Types|number of demon types]] section above.

Note that a high value here can cause lots of map rejections, particularly on smaller maps as there simply isn't enough room or regions to put them all in.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_NUMBER:40]</nowiki></tt>
| Range: 0 to 300
|}

=== Playable Civilization Required ===

If this is set to yes (default) then worlds will be rejected if no civilization with [[Entity token|CIV_CONTROLLABLE]] can be placed. In an unmodded game, only the dwarves have this token.

If set to no, the result may be a world that cannot be played in Fortress Mode.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PLAYABLE_CIVILIZATION_REQUIRED:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[PLAYABLE_CIVILIZATION_REQUIRED:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Minimum Number of Mid/Low/High Characteristic Squares ===

Sets the minimum possible number of squares of certain ranges of each of the region qualities, such as elevation, rain, drainage, volcanism, savagery, and temperature. These need to be changed to reflect your regional meshes and weights, and are responsible for a HUGE number of map rejections. These values can all be set to 0 for much fewer map rejections, particularly in the case of more wacky, non-standard maps.

These values will cause worlds to be rejected unless at least the given number of squares of the given type are randomly generated. Setting these values too high could result in worlds always being rejected if other parameters such as the maximum/minimums for elevation, etc., don't allow enough of those squares to get generated.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[ELEVATION_RANGES:8256:16512:8256]</nowiki></tt>
| rowspan="5" | Minimum number of squares that must have low, medium, and high amounts of the given attribute. 
0 = No minimum
|-
| <tt><nowiki>[RAIN_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[RAIN_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[DRAINAGE_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[SAVAGERY_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[VOLCANISM_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM_RANGES:8256:16512:8256]</nowiki></tt>
|}

==World rejection==

:''Main article: [[World rejection]]''

If you are having the common problem of generated worlds always being rejected by the world generator, see [[v0.31:World rejection|Solving World Rejection Problems (v0.31 page)]] as it contains many detailed suggestions on how to troubleshoot and solve these issues.

== Parameter set examples ==

If you're trying to do something specific, then the [[Worldgen examples]] - complete parameter sets that can be copied directly into your ''world_gen.txt'' file and customized as desired - might be helpful.
If none of the examples suit your needs, [[Worldgen tricks]] has strategies and tips on making a world just right for you.

For many, many more examples see:
* [http://www.bay12forums.com/smf/index.php?topic=101280 DF2012 (v0.34) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=140180 DF2014 (v0.40) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=168543.0 DF2014 (v0.44.02+) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=175538 DF2014 (v0.47.01+) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=180805.0 DF2022 (v0.50.01+) WorldGen "Cookbook" Thread]

{{World}}

Release information/53.12

2026-04-14T23:35:57Z

Ziusudra: /* General updates */ added some links

{{release notes}}
:Here's a quality of life patch that addresses various issues. You can see your active petitions now and it's harder to disband squads accidentally. Clothing wears down more slowly. Selecting items inside bins during trade works more intuitively. You can see the products and required items for jobs in workshops. Soldiers wear boots properly. See the full list below.
:—[[Toady One]], April 14, 2026

:Hey everyone,
:We’ve got a jam-packed update today with a big quality of life patch along with a new [https://www.youtube.com/watch?v=LTV5R7JIMQY Tarn Time video] with news about Magic (the update), Magic (the cards) and another surprise! You’ll just have to watch and find out…
:—[[Alexandra]], April 14, 2026
* [https://www.bay12forums.com/smf/index.php?topic=183810.0 Bay 12 Forum thread]
* [https://www.bay12games.com/dwarves/index.html#2026-04-14 Patch notes on Bay 12 Games]
* [https://store.steampowered.com/news/app/975370/view/514113986433651135 Patch notes on Steam]
* [https://kitfoxgames.itch.io/dwarf-fortress/devlog/1489557/myth-magic-news-quality-of-life-update-dwarf-fortress-patch-5312 Patch notes on itch.io]

== General updates ==
* Added display of accepted [[petition]] building projects ([[guildhall]]s and [[temple]]s).
* Added [[standing orders]] to automatically accept or reject citizen petitions and various residency petitions.
* Added standing orders allowing mining designations to globally ignore new [[Digging designation canceled|warm/damp stone warnings]].
* [[Squad]] disband icon is no longer a red X that looks like it closes the menu.
* Disbanding squads now requires confirmation.
* Items suffer less damage from age and worn items [[wear]] down more slowly.
* [[Trade]]rs bring [[clothes]] properly [[size]]d for all fortress citizens and long-term residents.
* Added tooltips showing products and required materials when adding new tasks in [[workshop]]s.
* Changed behavior of bin selection in trade menu. Clicking the [[bin]] now selects all items inside as well, and these can be unselected one at a time. Clicking a selected bin unselects all of its contents.
* You can now click anywhere on item listings in the trade/barter menus to select the item.
* Added a select all button to the move-goods-to-depot menu.
* Made squad soldiers remove shoes properly if they conflict with their [[uniform]]'s boots.
* Reordered [[work order]] buttons.
* Clicking on name of work order or shop text allows number entry.
* Made the [[difficulty]] setting "[[Difficulty#Temples|priesthood unit count]]" properly effect temple petitions.
* Closing the unit selector no longer also closes menu that opened it.
* Made stone use and children's chore scrollbars work properly.
* Changed citizens label to residents in unit list to reflect all who are listed.
* Show residency vs. citizenship status on unit summary sheet.
* Shows the [[deity]] being worshipped in [[meeting hall]] [[location]] info box.
* Shows the deity being worshipped in location assignment list.
* Shows location type in meeting hall location info box.
* Shows location type in location assignment list.
* Shows current guildhall existence/petition status when choosing a new guildhall.
* Shows current temple existence/petition status when choosing a new temple.

== Dwarf Fortress Magic the Gathering cards! ==
We’re excited to announce that Dwarf Fortress is coming to Magic: The Gathering with a Secret Lair drop on April 27th. The drop includes a set of 5 cards featuring classic ASCII art created in collaboration with Tarn and Zach Adams and the amazing artists at Wizards of the Coast! You can sign up for email alerts on the [https://magic.wizards.com/en/news/announcements/secret-lair-back-to-school-superdrop Secret Lair website].

== Organize a community gathering ==
Thank you to everyone who came out to the Dwarf Fortress gathering at PAX East, we hope to make next year’s event bigger and better! Want to host your own Dwarf Fortress meetup and want us to send you some merch? Fill out [https://forms.gle/1MPRqaiU4zv1hL229 this form] with all your details.

== Dwarf Fortress music in concert ==
The Washington Metropolitan Gamer Symphony Orchestra presents Ballads of Earth and Ore. This concert has been programmed to highlight a suite of tunes arranged from Dwarf Fortress. "Songs of Zavazsil" is a symphonic adventure into the procedurally generated musical forms found and described in one world of Dwarf Fortress. For more info: https://givebutter.com/WMGSOSP26

That's all for today. We'll have more details about Myth & Magic and the dinos in future updates.

Release information/53.12

2026-04-14T21:55:07Z

Ziusudra: Creating release notes for v53.12

{{release notes}}
:Here's a quality of life patch that addresses various issues. You can see your active petitions now and it's harder to disband squads accidentally. Clothing wears down more slowly. Selecting items inside bins during trade works more intuitively. You can see the products and required items for jobs in workshops. Soldiers wear boots properly. See the full list below.
:—[[Toady One]], April 14, 2026

:Hey everyone,
:We’ve got a jam-packed update today with a big quality of life patch along with a new [https://www.youtube.com/watch?v=LTV5R7JIMQY Tarn Time video] with news about Magic (the update), Magic (the cards) and another surprise! You’ll just have to watch and find out…
:—[[Alexandra]], April 14, 2026
* [https://www.bay12forums.com/smf/index.php?topic=183810.0 Bay 12 Forum thread]
* [https://www.bay12games.com/dwarves/index.html#2026-04-14 Patch notes on Bay 12 Games]
* [https://store.steampowered.com/news/app/975370/view/514113986433651135 Patch notes on Steam]
* [https://kitfoxgames.itch.io/dwarf-fortress/devlog/1489557/myth-magic-news-quality-of-life-update-dwarf-fortress-patch-5312 Patch notes on itch.io]

== General updates ==
* Added display of accepted petition building projects (guildhalls and temples).
* Added standing orders to automatically accept or reject citizen petitions and various residency petitions.
* Added standing orders allowing mining designations to globally ignore new warm/damp stone warnings.
* Squad disband icon is no longer a red X that looks like it closes the menu.
* Disbanding squads now requires confirmation.
* Items suffer less damage from age and worn items wear down more slowly.
* Traders bring clothes properly sized for all fortress citizens and long-term residents.
* Added tooltips showing products and required materials when adding new tasks in workshops.
* Changed behavior of bin selection in trade menu. Clicking the bin now selects all items inside as well, and these can be unselected one at a time. Clicking a selected bin unselects all of its contents.
* You can now click anywhere on item listings in the trade/barter menus to select the item.
* Added a select all button to the move-goods-to-depot menu.
* Made squad soldiers remove shoes properly if they conflict with their uniform's boots.
* Reordered work order buttons.
* Clicking on name of work order or shop text allows number entry.
* Made the difficulty setting "priesthood unit count" properly effect temple petitions.
* Closing the unit selector no longer also closes menu that opened it.
* Made stone use and children's chore scrollbars work properly.
* Changed citizens label to residents in unit list to reflect all who are listed.
* Show residency vs. citizenship status on unit summary sheet.
* Shows the deity being worshipped in meeting hall location info box.
* Shows the deity being worshipped in location assignment list.
* Shows location type in meeting hall location info box.
* Shows location type in location assignment list.
* Shows current guildhall existence/petition status when choosing a new guildhall.
* Shows current temple existence/petition status when choosing a new temple.

== Dwarf Fortress Magic the Gathering cards! ==
We’re excited to announce that Dwarf Fortress is coming to Magic: The Gathering with a Secret Lair drop on April 27th. The drop includes a set of 5 cards featuring classic ASCII art created in collaboration with Tarn and Zach Adams and the amazing artists at Wizards of the Coast! You can sign up for email alerts on the [https://magic.wizards.com/en/news/announcements/secret-lair-back-to-school-superdrop Secret Lair website].

== Organize a community gathering ==
Thank you to everyone who came out to the Dwarf Fortress gathering at PAX East, we hope to make next year’s event bigger and better! Want to host your own Dwarf Fortress meetup and want us to send you some merch? Fill out [https://forms.gle/1MPRqaiU4zv1hL229 this form] with all your details.

== Dwarf Fortress music in concert ==
The Washington Metropolitan Gamer Symphony Orchestra presents Ballads of Earth and Ore. This concert has been programmed to highlight a suite of tunes arranged from Dwarf Fortress. "Songs of Zavazsil" is a symphonic adventure into the procedurally generated musical forms found and described in one world of Dwarf Fortress. For more info: https://givebutter.com/WMGSOSP26

That's all for today. We'll have more details about Myth & Magic and the dinos in future updates.

Version history

2026-04-14T21:39:59Z

Ziusudra: /* Dwarf Fortress v53 */ .12

This page documents the complete release history of ''Dwarf Fortress'', starting from the very first public release of [[23a:Release information/0.21.93.19a|0.21.93.19a]]. See each release's page for more information.

== Dwarf Fortress v53 ==
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[Release information/53.12|53.12]] || 2026-4-14
| General QoL tweaks for petitions, trade, mining, squads, and more
|-
| [[Release information/53.11|53.11]] || 2026-3-4
| General fixes
|-
| [[Release information/53.10|53.10]] || 2026-1-12
| ''Hotfixes'' and more aquatic animal portraits
|-
| [[Release information/53.09|53.09]] || 2026-1-7
| General fixes, new portraits, experiment graphics
|-
| [[Release information/53.08|53.08]] || 2025-12-19
| ''Hotfix'' for mining and deconstruction speed
|-
| [[Release information/53.07|53.07]] || 2025-12-18
| Siege related ''Bugfixes'' and more animal portraits
|-
| [[Release information/53.06|53.06]] || 2025-11-24
| Siege related ''Bugfixes'' and a new song
|-
| [[Release information/53.05|53.05]] || 2025-11-18
| Quick fix for a few sorting issues.
|-
| [[Release information/53.04|53.04]] || 2025-11-17
| ''Hotfix'' for Siege Update and other ''Bugfixes''.
|-
| [[Release information/53.03|53.03]] || 2025-11-10
| ''Hotfix'' for Siege Update.
|-
| [[Release information/53.02|53.02]] || 2025-11-04
| ''Hotfix'' for Siege Update.
|-
| [[Release information/53.01|53.01]] || 2025-11-03
| '''Siege Update''': Invaders can dig, destroy, build, and plan. Improved siege engines including new [[bolt thrower]].
|-
|}

== Dwarf Fortress v52 ==
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[Release information/52.05|52.05]] || 2025-10-01
| Miscellaneous ''Bugfixes''
|-
| [[Release information/52.04|52.04]] || 2025-08-28
| ''Bugfixes'' relating to traveling squads
|-
| [[Release information/52.03|52.03]] || 2025-08-07
| Added new [[Dye]] related plants and features
|-
| [[Release information/52.02|52.02]] || 2025-07-24
| ''Hotfix''
|-
| [[Release information/52.01|52.01]] || 2025-07-21
| Lua update for easier mod making and future advanced systems
|}

== Dwarf Fortress v51 ==
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[Release information/51.13|51.13]] || 2025-06-27
| ''Hotfix'' for dehydration issues
|-
| [[Release information/51.12|51.12]] || 2025-06-26
| Ranged weapon updates
|-
| [[Release information/51.11|51.11]] || 2025-04-21
| Turned off underground humanoid invasions until fixed, traveling creatures retain room ownership, artifact weapon images
|-
| [[Release information/51.10|51.10]] || 2025-04-03
| ''Hotfix'' for path overflow fix
|-
| [[Release information/51.09|51.09]] || 2025-04-02
| [[Forbidden]] [[coffin]]s now unusable; [[mining]], [[woodcutting]], [[hunting]] [[labor]]s now mutually exclusive; stopped [[Reclaim_fortress_mode|reclaim/unretire]] [[magma]] overflows
|-
| [[Release information/51.08|51.08]] || 2025-03-13
| ''Hotfix'' for issue preventing player input during fast travel in Adventure Mode after a popup appears
|-
| [[Release information/51.07|51.07]] || 2025-03-12
| Quick-pick most-recently-used material for constructions, ordinary adventurers can start anywhere in their civilization, several ''Bugfixes''.
|-
| [[Release information/51.06|51.06]] || 2025-02-26
| Nerfs prepared food value, adjusts metal settings, adds option to disable rectangle size info box, several ''Bugfixes''.
|-
| [[Release information/51.05|51.05]] || 2025-02-12
| Adds Adventure mode speedometer and fixes ASCII Travel map. Adds tree growth graphics. Re-implements non-varied terrain in ASCII mode. ''Bugfixes''.
|-
| [[Release information/51.04|51.04]] || 2025-01-27
| Fixed Steam modding workshop support. ''Steam only''.
|-
| [[Release information/51.03|51.03]] || 2025-01-25
| Fixed two screeching ogg vorbis audio files and made an unknown binary change. ''Premium-only''.
|-
| [[Release information/51.02|51.02]] || 2025-01-221 2025-01-23
| '''Public Adventure release''': Audio changes, keyboard look, ''Bugfixes''.
|-
| [[Release information/51.01|51.01]] || 2024-04-172 2025-01-213
| '''Adventure beta''': [[Adventure mode]] now available, with a new [[soundtrack]] and [[interface]]. Graphics changes, skill archetypes, [[Chosen]] mode, [[mysterious dungeon]]s. ''Steam only''.
|}

1: Dwarf Fortress v51.02 was initially released on the beta branch on Steam ~24 hours before the official release.

2: Adventure mode had an extended beta testing period, with 28 updates being worked on concurrently with v50 releases. This is the initial launch date.

3: The final version of 51.01 was released to the beta branch on this date, and is not listed in-game as a beta.

== Dwarf Fortress v50 ==
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[Release information/50.15|50.15]] || 2024-12-12
| More container graphics, color clothing by dye or profession, negatively-aged migrant fix, more ''Bugfixes''.
|-
| [[Release information/50.14|50.14]] || 2024-09-25
| Child/baby graphics for 5 major civs, more crop & equipment graphics, ''Bugfixes''.
|-
| [[Release information/50.13|50.13]] || 2024-04-23
| Added portraits for most races, ''Bugfixes''.
|-
| [[Release information/50.12|50.12]] || 2024-03-06
| ''Bugfixes'', improvements to UI and UX.
|-
| [[Release information/50.11|50.11]] || 2023-10-03
| ''Bugfixes''
|-
| [[Release information/50.10|50.10]] || 2023-09-19
| [[Alerts]] and combat [[reports]] can be viewed. Linux support. Crash logging. In game [[Settings#Announcements|Announcement Settings]].
|-
| [[Release information/50.09|50.09]] || 2023-06-28
| Updated to SDL2, performance optimization, experimental multithreading (field of view calculations became a separate thread).
|-
| [[Release information/50.08|50.08]] || 2023-05-02
| Re-introduced [[XML dump|XML]] export in [[legends mode]], аdded graphics for many plants and child/baby creatures.
|-
| [[Release information/50.07|50.07]] || 2023-02-07
| ''Hotfix'' - embark warning fix
|-
| [[Release information/50.06|50.06]] || 2023-02-07
| Re-introduced [[arena mode]].
|-
| [[Release information/50.05|50.05]] || 2023-01-05
| ''Bugfixes and optimizations''
|-
| [[Release information/50.04|50.04]] || 2022-12-22
| '''Classic release''': released the free [[Classic]] version on [https://www.bay12games.com/dwarves/ bay12games.com], and enabled classic mode in the Premium version. Added ability to advance time by one frame, and assign everyone to a burrow.
|-
| [[Release information/50.03|50.03]] || 2022-12-12
| ''Premium-only bugfixes''. Improved UX for selecting building materials.
|-
| [[Release information/50.02|50.02]] || 2022-12-08
| ''Premium-only bugfixes''
|-
| [[Release information/50.01|50.01]] || 2022-12-06
| '''Premium release''': launched the paid [[Premium]] version on Steam and itch.io. Introduced [[graphics]], full [[Mouse control|mouse support]], a new user [[interface]], tutorials, and new [[soundtrack|music]] and sound effects. A number of features from v0.47 were lost in 50.01 (see [[Missing features]]).
|}

== Dwarf Fortress v0.47 ==
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[DF2014:Release information/0.47.05|0.47.05]] || 2021-01-28
| ''Bugfix''
|-
| [[DF2014:Release information/0.47.04|0.47.04]] || 2020-02-29
| ''Bugfix''
|-
| [[DF2014:Release information/0.47.03|0.47.03]] || 2020-02-16
| ''Bugfix''
|-
| [[DF2014:Release information/0.47.02|0.47.02]] || 2020-02-06
| ''Bugfix''
|-
| [[DF2014:Release information/0.47.01|0.47.01]] || 2020-01-29
| ''Release'': introduced creation of [[guildhall]]s and [[temple]]s. Introduced [[traitor]]s and [[villain]]s. Many new events in world generation, organizations, sites, pets and mounts in adventure mode, [[Aquifier#Light aquifers|light aquifers]].
|}

== Dwarf Fortress v0.44 ==
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[DF2014:Release information/0.44.12|0.44.12]] || 2018-06-23
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.11|0.44.11]] || 2018-06-23
| Civilizations create nearby sites and associate them with your fortress, can request/send workers, long-term memories can lead to personality changes
|-
| [[DF2014:Release information/0.44.10|0.44.10]] || 2018-05-05
| Dwarves now have short-term and long-term memories of emotional events, Adventurer mode log improved
|-
| [[DF2014:Release information/0.44.09|0.44.09]] || 2018-04-01
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.08|0.44.08]] || 2018-03-29
| ''Bugfix'';
|-
| [[DF2014:Release information/0.44.07|0.44.07]] || 2018-03-12
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.06|0.44.06]] || 2018-03-09
| Raids can pillage/raze sites and demand tribute, will gain skills (e.g. military tactics) during missions
|-
| [[DF2014:Release information/0.44.05|0.44.05]] || 2018-01-14
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.04|0.44.04]] || 2018-01-10
| ''Bugfix'';
|-
| [[DF2014:Release information/0.44.03|0.44.03]] || 2017-12-25
| ''Bugfix'';
|-
| [[DF2014:Release information/0.44.02|0.44.02]] || 2017-11-23
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.01|0.44.01]] || 2017-11-22
| ''Release''; can now send raids to other sites, build museums using pedestals and display cases, artifacts created during worldgen, civilizations can send spies to gather information on artifacts
|}

== Dwarf Fortress v0.43 ==
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[DF2014:Release information/0.43.05|0.43.05]] || 2016-06-20
| '''64-bit support''', bugfixes
|-
| [[DF2014:Release information/0.43.04|0.43.04]] || 2016-06-20
| ''Bugfix'';
|-
| [[DF2014:Release information/0.43.03|0.43.03]] || 2016-05-22
| ''Bugfix'';
|-
| [[DF2014:Release information/0.43.02|0.43.02]] || 2016-05-11
| ''Hotfix'';
|-
| [[DF2014:Release information/0.43.01|0.43.01]] || 2016-05-09
| ''Release''; Adventurers can create sites, make stone axes, fell trees, perform carpentry, and construct buildings; Fortress mode work orders can now specify start conditions, restart frequencies, and how many workshops can be used
|}

== Dwarf Fortress v0.42 ==
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[DF2014:Release information/0.42.06|0.42.06]] || 2016-02-10
| Can specify exact materials for jobs, make specific crafts, apply specific decorations, and even customize the details of art images; Adventurers can now do bone carving, complete with custom images
|-
| [[DF2014:Release information/0.42.05|0.42.05]] || 2016-01-17
| Reputations for hunters and protection from bandits
|-
| [[DF2014:Release information/0.42.04|0.42.04]] || 2015-12-26
| More varieties of [[animal people]] and giant animals, Vampire purges during worldgen, bugfixes
|-
| [[DF2014:Release information/0.42.03|0.42.03]] || 2015-12-12
| ''Bugfix'';
|-
| [[DF2014:Release information/0.42.02|0.42.02]] || 2015-12-05
| ''Bugfix'';
|-
| [[DF2014:Release information/0.42.01|0.42.01]] || 2015-12-01
| ''Release''; introduced taverns, temples, and libraries, added new musical instruments and performance skills, introduced [[need]]s to replace dwarves going On Break, added visitors who can petition for fortress membership, scholars and historians can write books and spread knowledge, and drinking alcohol actually causes inebriation (and eventually fatal alcohol poisoning)
|}

== Dwarf Fortress v0.40 ==
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[DF2014:Release information/0.40.24|0.40.24]] || 2015-01-07
| ''Bugfix''; Misc. bugfixes; allowing 1x1 forts
|-
| [[DF2014:Release information/0.40.23|0.40.23]] || 2014-12-24
| ''Bugfix''; Fixed farming job cancellations, armies camping forever, typos, and channeling bug
|-
| [[DF2014:Release information/0.40.22|0.40.22]] || 2014-12-21
| ''Bugfix''; Fixed multi-item jobs and toggle marker tweak
|-
| [[DF2014:Release information/0.40.21|0.40.21]] || 2014-12-19
| ''Hotfix''; Fixed a crash bug and other issues
|-
| [[DF2014:Release information/0.40.20|0.40.20]] || 2014-12-18
| Job priorities rewrite; vein and cluster automining
|-
| [[DF2014:Release information/0.40.19|0.40.19]] || 2014-11-26
| [[Gelding]] and related profession/skill/etc
|-
| [[DF2014:Release information/0.40.18|0.40.18]] || 2014-11-20
| ''Hotfix''; Fixed a smelting issue on Windows
|-
| [[DF2014:Release information/0.40.17|0.40.17]] || 2014-11-19
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.16|0.40.16]] || 2014-11-12
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.15|0.40.15]] || 2014-11-05
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.14|0.40.14]] || 2014-10-25
| Thought/emotion rewrite, stopped site invaders from always winning
|-
| [[DF2014:Release information/0.40.13|0.40.13]] || 2014-09-17
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.12|0.40.12]] || 2014-09-10
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.11|0.40.11]] || 2014-09-03
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.10|0.40.10]] || 2014-08-24
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.09|0.40.09]] || 2014-08-17
| ''Bugfix''; Misc. bugfixes
|-
| [[DF2014:Release information/0.40.08|0.40.08]] || 2014-08-11
| ''Hotfix''; Fixed a crash bug and issues with constructions
|-
| [[DF2014:Release information/0.40.07|0.40.07]] || 2014-08-10
| ''Bugfix''; AI and invasion fixes
|-
| [[DF2014:Release information/0.40.06|0.40.06]] || 2014-08-03
| ''Bugfix''; stack bugfixes.
|-
| [[DF2014:Release information/0.40.05|0.40.05]] || 2014-07-27
| ''Bugfix''; fixed large world slowdown, decreased rampant tree growth, many old and new bugfixes.
|-
| [[DF2014:Release information/0.40.04|0.40.04]] || 2014-07-20
| ''Bugfix''; several crash fixes, made saplings grow properly.
|-
| [[DF2014:Release information/0.40.03|0.40.03]] || 2014-07-13
| ''Bugfix''; broke save game compatibility again due to more save corruption, several crash fixes.
|-
| [[DF2014:Release information/0.40.02|0.40.02]] || 2014-07-10
| ''Bugfix''; broke save game compatibility due to save corruption, several crash fixes.
|-
| [[DF2014:Release information/0.40.01|0.40.01]] || 2014-07-07
| ''Release''; Introduced world generation running in the background while fortresses and adventurers progress, un-retiring of fortresses, multiple tile trees, climbing & jumping, and more.
|}

== Dwarf Fortress v0.34 ==
In a [http://www.bay12games.com/dwarves/index.html devlog] entry for 2011-01-30, Threetoe announced plans for a series of nine numbered releases ("Short-term Goals" on the [http://www.bay12games.com/dwarves/dev.html dev page]) to finish off the long-planned "caravan" development arc. Release 1, improving towns and introducing markets, along with a variety of supernatural creature types, was predicted to have a version number of [http://www.bay12games.com/media/df_talk_14_transcript.html#14.16 0.33 or 0.34] and was released on Valentine's Day 2012 as version 0.34.01.

{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[v0.34:Release information/0.34.11|0.34.11]] || 2012-06-04
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.10|0.34.10]] || 2012-05-21
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.09|0.34.09]] || 2012-05-17
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.08|0.34.08]] || 2012-05-14
| Hauling overhaul - minecarts and wheelbarrows, more accurate projectiles, reduced mining yields, advanced stockpile/workshop links
|-
| [[v0.34:Release information/0.34.07|0.34.07]] || 2012-03-30
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.06|0.34.06]] || 2012-03-23
| Updates to animal training ([[dungeon master]] removed, having been nonfunctional since 0.31.01), return of good/evil trees and shrubs
|-
| [[v0.34:Release information/0.34.05|0.34.05]] || 2012-03-06
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.04|0.34.04]] || 2012-02-29
| ''Hotfix''
|-
| [[v0.34:Release information/0.34.03|0.34.03]] || 2012-02-28
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.02|0.34.02]] || 2012-02-18
| ''Bugfix''; broke save compatibility due to save corruption, numerous fixes for old issues
|-
| [[v0.34:Release information/0.34.01|0.34.01]] || 2012-02-14
| Introduction of human cities (shops, marketplaces, sewers, dungeons) and tombs, addition of [[interaction]]s ([[necromancer]]s, [[werebeast]]s, [[vampire]]s, etc.), historical migrants, truly evil regions, updated [[justice]] system, many [[Animal sponsorship drive|"sponsorship" creatures]], [[Gem#Gem cuts|gem cuts]], many adventure mode tweaks and minor features
|}

== Dwarf Fortress v0.31 ==
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[v0.31:Release information/0.31.25|0.31.25]] || 2011-03-28
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.24|0.31.24]] || 2011-03-27
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.23|0.31.23]] || 2011-03-26
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.22|0.31.22]] || 2011-03-24
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.21|0.31.21]] || 2011-03-06
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.20|0.31.20]] || 2011-03-06
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.19|0.31.19]] || 2011-02-16
| Worldgen starvation, usually wiping out kobolds; grazing; ceramics; jugs, pots, nest boxes, beehives (and bees); site finder changes. Last major 0.31 release, and the (unnumbered) beginning of the caravan arc series.
|-
| [[v0.31:Release information/0.31.18|0.31.18]] || 2010-11-16
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.17|0.31.17]] || 2010-11-11
| Bandits, Night Creatures, Bogeyman, Adventure mode improvements, combat aiming, castles
|-
| [[v0.31:Release information/0.31.16|0.31.16]] || 2010-10-04
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.15|0.31.15]] || 2010-10-03
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.14|0.31.14]] || 2010-09-23
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.13|0.31.13]] || 2010-09-15
| Entity populations, sprawl, river density tweaking, TrueType font support
|-
| [[v0.31:Release information/0.31.12|0.31.12]] || 2010-07-25
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.11|0.31.11]] || 2010-07-23
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.10|0.31.10]] || 2010-07-11
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.09|0.31.09]] || 2010-07-10
| Adventure mode knapping and butchery, combat improvements
|-
| [[v0.31:Release information/0.31.08|0.31.08]] || 2010-06-19
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.07|0.31.07]] || 2010-06-19
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.06|0.31.06]] || 2010-06-09
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.05|0.31.05]] || 2010-06-04
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.04|0.31.04]] || 2010-05-16
| Merge with the 40d19 branch bringing the return of Mac downloads, SDL and Linux downloads, OpenGL optimizations, macros, and zooming
|-
| [[v0.31:Release information/0.31.03|0.31.03]] || 2010-04-12
| Ability to create undead in arena
|-
| [[v0.31:Release information/0.31.02|0.31.02]] || 2010-04-08
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.01|0.31.01]] || 2010-04-01
| Overhaul of many aspects of the game: new material system, new fortress military system, healthcare and combat system was heavily expanded, creatures now have 19 [[attributes]] which affect [[skills]], body features influences gameplay, underground areas have been totally redone, introduced [[raws]], [[genetics]], [[caste]]s, [[burrow]]s, [[poison]]s, [[Tree#Underground trees|underground trees]], [[forgotten beast]]s, [[arena mode]], and dozens of minor changes
|}

== 3D Version (before 2010) ==
A test branch including 0.28.181.40d2 thru 0.28.181.40d19: OpenGL optimizations, macros, zooming, and native Linux support. Not available on [[Bay 12 Games]], but can be found on the [https://archive.org/details/dwarf-fortress?tab=collection&and%5B%5D=year%3A%5B2009+TO+2010%5D Internet Archive]

{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[40d:Release information/0.28.181.40d|0.28.181.40d]] || 2008-09-06
| ''Bugfix''; [[40d:Cat cancels Store Item in Stockpile: Too injured|Cat bug introduced]]
|-
| [[40d:Release information/0.28.181.40c|0.28.181.40c]] || 2008-08-21
| ''Hotfix'', partial print now allows specifying a frame count
|-
| [[40d:Release information/0.28.181.40b|0.28.181.40b]] || 2008-08-20
| Partial print, windowed/fullscreen gridsizes
|-
| [[40d:Release information/0.28.181.40a|0.28.181.40a]] || 2008-08-18
| Embark profiles added, [[note]]s extended to embark map, customizable forbid [[orders]] added (used ammunition, dead creatures' possessions, etc.), and dwarves now try to store items in partially-filled containers instead of empty ones
|-
| [[40d:Release information/0.28.181.39f|0.28.181.39f]] || 2008-08-09
| [[Custom grid]] sizes added
|-
| [[40d:Release information/0.28.181.39e|0.28.181.39e]] || 2008-07-23
| ''Hotfix''
|-
| [[40d:Release information/0.28.181.39d|0.28.181.39d]] || 2008-07-23
| Added [[Site finder]], can display hidden map features when choosing a site, [[Note]] support implemented, and worldgen presets added
|-
| [[40d:Release information/0.28.181.39c|0.28.181.39c]] || 2008-07-16
| ''Hotfix''
|-
| [[40d:Release information/0.28.181.39b|0.28.181.39b]] || 2008-07-14
| ''Hotfix''; trees in [[Elf|Elven]] forest retreats no longer have names
|-
| [[40d:Release information/0.28.181.39a|0.28.181.39a]] || 2008-07-13
| Lots of worldgen changes, including ethics (leading to wars and conquered sites), dynamic era naming, worldgen roads/bridges/tunnels, megabeasts being killed during worldgen, megabeasts being undead; cats and trained animals are now named on adoption, human weapon stores stock more stuff (including ammo), placing [[construction]]s now destroys engravings, and flying creatures no longer give birth in mid-air
|-
| [[40d:Release information/0.27.176.38c|0.27.176.38c]] || 2008-02-24
| ''Bugfix''
|-
| [[40d:Release information/0.27.176.38b|0.27.176.38b]] || 2008-02-23
| First Macintosh-compatible release; Dwarves no longer carry their artifacts around, booze food no longer melts, worlds can now have custom sizes
|-
| [[40d:Release information/0.27.176.38a|0.27.176.38a]] || 2008-02-15
| Magma pipes now refill, ZERO_RENT and BABY_CHILD_CAP init.txt options were added, strange moods no longer convert workshops, metal crossbows now made by [[weaponsmith]]s instead of [[bowyer]]s, dwarves chat and make friends/grudges and get married, unhappy thoughts from [[masterpiece]] destruction are now reduced based on the number of masterpieces the dwarf has made, and plants can now drown in deep water
|-
| [[40d:Release information/0.27.173.38a|0.27.173.38a]] || 2008-02-04
| [[Sphere]]s added, lots of new entity tags, numerous worldgen improvements, religions implemented, undead [[ruin]]s removed
|-
| [[40d:Release information/0.27.169.33g|0.27.169.33g]] || 2007-12-21
| Mud no longer dries up during winter, occupied cages are named according to their contents, brand new "Bring to depot" interface, [[strange mood]]s no longer require glass until you actually make some
|-
| [[40d:Release information/0.27.169.33f|0.27.169.33f]] || 2007-12-14
| ''Bugfix''; mud and blood no longer spread, auto-[[forbid]] fired ammunition, donkey/horse foals are now named properly, graphics sets can now use custom tiles for appointed nobles, and flux stones now have a value of 2 again.
|-
| [[40d:Release information/0.27.169.33e|0.27.169.33e]] || 2007-12-08
| ''Bugfix''; in particular, nobles no longer order themselves to be punished for failed mandates, donkeys can now breed, most types of vermin no longer have bones, and most types of fish no longer have lungs or throats
|-
| [[40d:Release information/0.27.169.33d|0.27.169.33d]] || 2007-11-30
| ''Bugfix''
|-
| [[40d:Release information/0.27.169.33c|0.27.169.33c]] || 2007-11-23
| Animals screen now labels war dogs and hunting dogs correctly, [[sliver barb]]s now have seeds, and process priority can now be configured in init.txt
|-
| [[40d:Release information/0.27.169.33b|0.27.169.33b]] || 2007-11-16
| [[Carp]] and other fish no longer gain [[swimming]] skill (making them ''slightly'' less dangerous), and various ore types now properly show up as '*' when mined.
|-
| [[40d:Release information/0.27.169.33a|0.27.169.33a]] || 2007-11-01
| added [[wood]]en [[block]]s, renamed aluminum ore to "native aluminum", [[mountain gnome]]s and [[dark gnome]]s no longer butcherable
|-
| [[40d:Release information/0.27.169.32a|0.27.169.32a]] || 2007-10-29
| The very first fully 3D version
|}

== 2D Version ==
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[23a:Release information/0.23.130.23a|0.23.130.23a]] || 2007-01-18
| ''Hotfix'' - Final version
|-
| [[23a:Release information/0.23.125.23b|0.23.125.23b]] || 2007-01-16
| ''Hotfix''
|-
| [[23a:Release information/0.23.125.23a|0.23.125.23a]] || 2007-01-16
| Temperature support was further improved, population/FPS caps were added, coffins could now be restricted to only dwarves or only pets, and animals could now be marked for slaughter from their {{K|v}}-{{K|p}} screen. Spirits of fire also got a '''lot''' hotter. For some reason, [[23a:horse|horse]]s are now made of [[iron]].
|-
| [[23a:Release information/0.22.123.23a|0.22.123.23a]] || 2006-12-21
| More workshop orders were added - auto collect webs, auto slaughter, auto butcher, auto tan; male cows are now called bulls, and whips can no longer get stuck in opponents
|-
| [[23a:Release information/0.22.121.23b|0.22.121.23b]] || 2006-12-16
| The ability to disable temperature and weather were added (to boost FPS)
|-
| [[23a:Release information/0.22.121.23a|0.22.121.23a]] || 2006-12-14
| Bins could now be made from metal, and the embark screen now described your biome and listed what civilizations were nearby
|-
| [[23a:Release information/0.22.120.23b|0.22.120.23b]] || 2006-12-10
| Improved temperature support was added
|-
| [[23a:Release information/0.22.120.23a|0.22.120.23a]] || 2006-11-23
| The ability to use custom [[graphics sets]] was added
|-
| [[23a:Release information/0.22.110.23c|0.22.110.23c]] || 2006-11-17
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.23b|0.22.110.23b]] || 2006-11-15
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.23a|0.22.110.23a]] || 2006-11-14 {{cite devlog|2006|11|14}}
| [[Dye]]s and dyeing were implemented, allowed sewing cloth/leather images into goods, as well as more detailed [[decoration|art]] (historical figures and events, special shapes); standing orders now allowed auto collecting webs and only using dyed cloth
|-
| [[23a:Release information/0.22.110.22f|0.22.110.22f]] || 2006-11-03
| ''Bugfix''; additionally, butterflies, fireflies, and dragonflies can no longer be kept as pets. [[Boatmurdered]] began in this version.
|-
| [[23a:Release information/0.22.110.22e|0.22.110.22e]] || 2006-10-29
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.22d|0.22.110.22d]] || 2006-10-29
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.22c|0.22.110.22c]] || 2006-10-29
| Custom [[stockpile]]s were added (previously, there were only 16 basic stockpile types; things like [[potash]] would be stored with your metal bars and you could not force [[seed]]s to be kept near the farm).
|-
| [[23a:Release information/0.22.110.22b|0.22.110.22b]] || 2006-10-21
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.22a|0.22.110.22a]] || 2006-10-21
| Inventory system changes (most notably, gloves and boots were split into two items (left & right for gloves))
|-
| [[23a:Release information/0.22.107.21a|0.22.107.21a]] || 2006-10-02
| Various changes to [[adventurer mode]] - guards and families, plus "." as a wait key
|-
| [[23a:Release information/0.21.105.21a|0.21.105.21a]] || 2006-09-25
| ''Hotfix''
|-
| [[23a:Release information/0.21.104.21c|0.21.104.21c]] || 2006-09-25
| Making potash no longer required making ashes into lye first.
|-
| [[23a:Release information/0.21.104.21b|0.21.104.21b]] || 2006-09-16
| Workshop profiles were added, along with showing genders on the Animal status screen
|-
| [[23a:Release information/0.21.104.21a|0.21.104.21a]] || 2006-09-08
| [[Designation|Designating]] with the mouse was added
|-
| [[23a:Release information/0.21.104.19d|0.21.104.19d]] || 2006-09-02
| ''Bugfix''
|-
| [[23a:Release information/0.21.104.19c|0.21.104.19c]] || 2006-09-02
| The ability to hide engravings was added, announcement consolidation (x15), seasonal blood cleanup was temporarily added (and would remain until version 0.31)
|-
| [[23a:Release information/0.21.104.19b|0.21.104.19b]] || 2006-08-27
| ''Bugfix''
|-
| [[23a:Release information/0.21.104.19a|0.21.104.19a]] || 2006-08-27
| The ability to "chasm" items was added (complete with attacks from chasm creatures as a result), as well as butchering cats
|-
| [[23a:Release information/0.21.102.19a|0.21.102.19a]] || 2006-08-24
| Dwarves could now have custom nicknames and professions, fullscreen could be toggled, starting animals would have mixed genders, horses could breed
|-
| [[23a:Release information/0.21.101.19d|0.21.101.19d]] || 2006-08-21
| ''Bugfix''
|-
| [[23a:Release information/0.21.101.19c|0.21.101.19c]] || 2006-08-20
| ''Bugfix''
|-
| [[23a:Release information/0.21.101.19b|0.21.101.19b]] || 2006-08-20
| ''Bugfix''
|-
| [[23a:Release information/0.21.101.19a|0.21.101.19a]] || 2006-08-19
| Adventurers could now have custom first names
|-
| [[23a:Release information/0.21.100.19a|0.21.100.19a]] || 2006-08-16
| Gender symbol was added to unit views, config options for disabling sound and the intro movie, command-line world generation, ability to export local map
|-
| [[23a:Release information/0.21.95.19c|0.21.95.19c]] || 2006-08-14
| Farm plot fertilization could be controlled directly
|-
| [[23a:Release information/0.21.95.19b|0.21.95.19b]] || 2006-08-13
| ''Bugfix''
|-
| [[23a:Release information/0.21.95.19a|0.21.95.19a]] || 2006-08-12
| ''Bugfix''
|-
| [[23a:Release information/0.21.93.19c|0.21.93.19c]] || 2006-08-10
| ''Bugfix''
|-
| [[23a:Release information/0.21.93.19b|0.21.93.19b]] || 2006-08-10
| ''Bugfix''
|-
| [[23a:Release information/0.21.93.19a|0.21.93.19a]] || 2006-08-08
| Initial public release
|}
[[Category:Game development]]
[[Category:Release information]]
[[ru:Version history]]

Release information/List

2026-04-14T21:35:52Z

Ziusudra: 53.12

{{release notes link|50.01|compat=no}}
{{release notes link|50.02}}
{{release notes link|50.03}}
{{release notes link|50.04}}
{{release notes link|50.05}}
{{release notes link|50.06}}
{{release notes link|50.07}}
{{release notes link|50.08}}
{{release notes link|50.09}}
{{release notes link|50.10}}
{{release notes link|50.11}}
{{release notes link|50.12}}
{{release notes link|50.13}}
{{release notes link|50.14}}
{{release notes link|50.15}}
{{release notes link|51.01}}
{{release notes link|51.02}}
{{release notes link|51.03}}
{{release notes link|51.04}}
{{release notes link|51.05}}
{{release notes link|51.06}}
{{release notes link|51.07}}
{{release notes link|51.08}}
{{release notes link|51.09}}
{{release notes link|51.10}}
{{release notes link|51.11}}
{{release notes link|51.12}}
{{release notes link|51.13}}
{{release notes link|52.01}}
{{release notes link|52.02}}
{{release notes link|52.03}}
{{release notes link|52.04}}
{{release notes link|52.05}}
{{release notes link|53.01}}
{{release notes link|53.02}}
{{release notes link|53.03}}
{{release notes link|53.04}}
{{release notes link|53.05}}
{{release notes link|53.06}}
{{release notes link|53.07}}
{{release notes link|53.08}}
{{release notes link|53.09}}
{{release notes link|53.10}}
{{release notes link|53.11}}
{{release notes link|53.12}}

Template:Current/lastupdate

2026-04-14T21:35:16Z

Ziusudra: 53.12

April 14, 2026<noinclude>

This template is the date that the latest version was released. (hopefully).
Include it in places that you want to refer to that date.

If this template isn't up to date, feel free to correct it.

[[Category:Version {{current/version}}]][[category:wiki]][[Category:Version templates]]</noinclude>

Advanced world generation

2026-04-10T05:41:09Z

Ziusudra: /* Interaction between Mesh Size and Weighted Ranges */ minor clarity tweaks

{{migrated article}}
{{Quality|Superior}}
{{av}}
:''This article contains information on advanced world generation. For information on basic world generation, see [[World generation]].'' ''See [[World token]] to more easily find information by the names used in the world_gen.txt file, [[World rejection]] for information on solving problems related to worlds always being rejected, and [[Worldgen examples]] for example worlds.''

[[File:adv_worldgen_v50.png|thumb|400px|right|The advanced world generation screen. ''(Click to enlarge)'']]'''Advanced world generation''', also labeled as '''detailed mode''', allows substantially more detail-oriented options of customization than standard, basic world generation. This gives the player much more control over how their world is generated. To better understand this article, it is advised that one should read about [[World generation|'''basic world generation''']] first.

The advanced world generation screen is reached by clicking "Create new world" at the main menu, then clicking "Detailed mode". Once at that screen, clicking "Basic options" will return the user to the standard world generation screen.

== Parameter sets ==
There are multiple default sets of all the advanced world generation parameters hard-coded in ''Dwarf Fortress'', which will be overridden by the <tt>prefs/world_gen.txt</tt> file in the main ''Dwarf Fortress'' directory, if it exists. It does not exist by default, you must create it, either by saving the default sets, or saving a copy from the [[world_gen.txt]] wiki page or elsewhere. This file can then be edited with a text editor, and you can copy and paste other players' sets of parameters into it. For sources of such parameter sets see [[Advanced_world_generation#Parameter_set_examples|Parameter set examples]] below.

To get back the default sets, move the existing <tt>prefs/world_gen.txt</tt> to somewhere else (like Documents), or delete it if you do not want to keep the changes, then load the sets in the game, it will then use the hardcoded defaults.

== User interface ==
First, there is a line of text inputs and buttons along the top of the screen, from left to right:
* The drop down menu of currently defined parameter sets, click the down arrow to select a set that you want to work with. The currently selected set can be renamed by clicking the current name or the [[File:Quill.png]] button. The first set in the file is selected by default, usually "LARGE ISLAND". See [[#Parameter set title|Parameter set title]].
* The dimensions of the world for the selected set, see [[#World dimensions|World dimensions]].
* A text entry box to set all of the seed options to the same seed, will show "Random seed", "Various seeds", or, if all four seeds are set to use the same value, that value. See [[Advanced_world_generation#Seed_values|Seed values]] and [[Advanced_world_generation#Seed_values|Seed notes]].
* The Copy Button to make a copy of the currently selected set and appends it to the bottom of the list.
* The red Delete button to delete the currently selected set, you will be prompted to confirm the deletion.
* The New parameter set to create a new parameter set and appends it to the bottom of the list. This seems to just copy the default "LARGE REGION" set.
* The Save button to save all of the current sets to the <tt>prefs/world_gen.txt</tt> file.
* The Load button to load from the same file, there is no confirmation, '''any unsaved changes will be lost'''. If that file does not exist, this resets all of the sets to the defaults.

Most of the middle is the parameters themselves, with a scroll bar to the right. Each row of the list can include:
* The name of the option
* The range of accepted values; not every option has this, and does not always match the displayed value, for example "0 to 1" might show as "No" and "Yes".
:* Sometimes the range might not initially show on rows that it should, reloading the sets with the Load button sometimes fixes that.{{bug|13176}}
* A plus button to increase the value or cycle through options, when applicable (this button will be missing if the range is missing.)
* The current value; can be clicked to edit, to actually set a value you must press {{k|enter}}, without doing that, clicking another entry box or right clicking will instead reset to the currently set value.
* An edit button to show that the previous box is editable, same as clicking on the text box.
* A minus button to decrease the value or cycle through options, when applicable (this button will be missing if the range is missing).
* A red button to disable this parameter, when applicable, usually setting the value to 0, or -1.

{{notice bar|bgcolor=#faa|bordercolor=#f00|All of the buttons below leave this screen and do not prompt to save the sets, so unsaved changes may be lost.}}
At the bottom right are 3 or 4 more buttons:
* The Create world button to do just that using the currently selected set, '''unsaved changes are lost'''.
* The Basic options button to go back to the normal world generation screen, unsaved changes are not lost if you come directly back to Detailed mode.
* The [[Mods]] button to go to the mod selection screen, unsaved changes are not lost if you come directly back to Detailed mode. Only shown if mods are available.
* Back to main menu button to do just that, '''unsaved changes are lost'''.

=== World painter ===
:''Main article: [[World painter]]
The '''world painter''' tool is not in the current version of ''Dwarf Fortress''; it allowed you to paint features onto a map. '''However''', those maps can still be used when generating a world by pasting world painter parameter set maps created in old versions into the <tt>prefs/world_gen.txt</tt> file. [[Utilities#Perfect_World_DF|Perfect World DF]] is a utility that uses the same parameter functionality as the world painter to paint a map, and it also can work with the current version of ''Dwarf Fortress''.

== Generating a world ==
You can either use an already-defined parameter set, or you can edit them, though it is highly suggested to edit a copy of one of the defaults. Once you are happy with the parameters you should save the values you just edited before you click the Create world button. Information about each parameter is documented below.

The phases of the world generation process are (this order is not completely correct):
* Preparing elevation...
* Setting temperature...
* Running rivers...
* Forming lakes and minerals...
* Growing vegetation...
* Verifying terrain...
* Importing wildlife...
* Recounting legends...
* Placing civilizations...
* Making cave civilizations...
* Making cave pops...
* Placing other beasts...
* Placing megabeasts...
* Placing good/evil...
* Placing caves...
* Prehistory generation
* Finalizing civ mats...
* Finalizing art...
* Finalizing uniforms...
* Finalizing sites...

== Seed notes ==
The world generation process uses a PRNG (Pseudo Random Number Generator) algorithm. A PRNG will produce a sequence of numbers that "looks" random, even though the actual sequence of numbers will always be the same if the PRNG is started with the same seed value. Basically this means that if you run world generation with a certain seed value on your computer, and someone else runs world generation with the same seed value on their computer, the same sequence of random numbers will be generated on both computers. The practical impact of this is that someone else can generate exactly the same world that you generated by entering the same seed value that you used.

In the current version, the seed values for the world itself and the names seem to produce the same result, but you will get changes in events which will result in a very different world history.{{bug|6934}} Keep this in mind if you want to regenerate a particular world.

The way that a world is generated can also be affected by certain world tokens. Changing them causes that code to use more or fewer PRNG values, causing later uses to get different parts of the sequence. So, you cannot for example, change the minimum and maximum rainfall and get 'the same world but drier or wetter', instead, a different world is generated. That said, it would also seem that certain small changes to these world tokens can occasionally generate a very similar world, however, other tokens are more sensitive. For more information see the forum thread [http://www.bay12forums.com/smf/index.php?topic=112132.msg3404199#msg3404199 here].

The following are tokens which use the PRNG values in ways that changing them will likely cause broader changes:

* [DIM:X:X]
* [ELEVATION:X:X:X:X]
* [RAINFALL:X:X:X:X]
* [TEMPERATURE:X:X:X:X]
* [DRAINAGE:X:X:X:X]
* [VOLCANISM:X:X:X:X]
* [SAVAGERY:X:X:X:X]
* [ELEVATION_FREQUENCY:X:X:X:X:X:X]
* [RAIN_FREQUENCY:X:X:X:X:X:X]
* [DRAINAGE_FREQUENCY:X:X:X:X:X:X]
* [TEMPERATURE_FREQUENCY:X:X:X:X:X:X]
* [SAVAGERY_FREQUENCY:X:X:X:X:X:X]
* [VOLCANISM_FREQUENCY:X:X:X:X:X:X]
* [PARTIAL_OCEAN_EDGE_MIN:X]
* [COMPLETE_OCEAN_EDGE_MIN:X]
* [HAVE_BOTTOM_LAYER_1:X]
* [MINERAL_SCARCITY:X] {{cite talk/this|Mineral scarcity}}

Many other world parameters, such as end year and embark points, can, however, be changed without it having any effect on the geography of the world generated from the seed values.

Normally, you don't enter these seed values, the game comes up with values based on some other sort of pseudo-random information from things like the current date and time.

When generating a world, ''Dwarf Fortress'' records the seeds it used in [[gamelog.txt]]; they can also be found with <code>gui/gm-editor world.worldgen.worldgen_parms</code> in [[DFHack]].

== Advanced parameters ==
There are essentially 4 types of controls for the generation of the surface map;

'''Terrain parameters''': as described below, these 5 variables define the basic background world, how hot or cold it is, how much rainfall, how high the mountains are. The world automatically goes through the temperature range along the Y axis, although sometimes it will be hotter in the north, other times in the south, or cold at both. Minimum, maximum and X,Y variance can drastically alter the world.

'''Weighted meshes''': these are a way to fine-tune the amount of the 5 basic variables on the map. They can be used to set the specific distribution of different elevations or rainfall areas for example.

'''Feature parameters''': such as rivers, mountain peaks, volcanoes, and oceans, which can cause rejections if the terrain parameters don't allow enough suitable locations for the features to be placed.

'''Rejection parameters''': ''Dwarf Fortress'' uses a 'belt-and-braces' approach to world generation. The above controls allow you to shape the world, then the rejection parameters throw it out if it does not meet certain criteria. There are a number of rejection parameters for the number and degree of the 5 basic variables, for biome types, etc. If the world does not meet the requirements of any one rejection parameter the world is rejected and re-randomised. Also see [[World rejection]].

Leaving tokens out of a set in <tt>world_gen.txt</tt> will cause the game to use default values which are not adjusted for smaller world sizes, this may cause smaller worlds to always be rejected.

If you are experimenting with world design, there is also a [[Settings#Feature_toggles|game setting]] that will log the rejection reasons to ``[[map_rejection_log.txt]]``. With that information you can then either adjust the rejection parameters to allow those worlds, or the other parameters to prevent them from trying to generate. ''Dwarf Fortress'' will keep adding to the file, so you may want to trim or delete it occasionally.

The parameters are described below in the order that they appear in the list in the game, which is not necessarily the order they appear in <tt>world_gen.txt</tt>. See [[world token]] for an index that will help you look things up by token name. The tokens used in <tt>world_gen.txt</tt> are at the bottom of each of the following parameter descriptions.

=== Parameter set title ===
This sets the name of the parameter set itself, as used in the list of sets (this has nothing to do with the name of the generated world).
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITLE:<name>]</nowiki></tt>
| <tt><nowiki>[TITLE:MEDIUM ISLAND]</nowiki></tt>
| Required
|}

=== World dimensions ===
The size of the map for the current set can be changed by changing the Width and Height values at the top next to the set title. You will need to confirm this, since changing the dimensions of the world will change other parameters, because many of them have different defaults depending on the surface area available.

Larger maps usually take longer to generate and may reduce [[Frames per second|FPS]] in-game, though this is really a matter of larger worlds usually having more civilizations, sites, historical figures, and events; restricting the number of those can speed up the process. Non-square maps may result in crashes{{bug|2928}}.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DIM:<width>:<height>]</nowiki></tt>
| <tt><nowiki>[DIM:257:257]</nowiki></tt>
| Valid values are 17, 33, 65, 129, and 257, other values will use one of those. Changing the size in the file without adjusting other parameters can cause many rejections.
|}

=== Seed values ===
Enables the use of, and specifies seed values for, different parts of the world generation process. Just entering a specific seed does not enable it, that must be done separately, although using the box at the top to set all the seeds to the same value does enable them all. Enabling a seed puts the token in using what ever is in the text box below. If you enable a seed, but do not enter a seed, the string "Seed text" will be used (<tt><nowiki>[SEED:Seed text]</nowiki></tt>). Trying to use a <tt><nowiki>]</nowiki></tt> in the string in the file will end the seed there, since it closes the token, any text after that will be ignored. Normally, just leave these set to Random, unless trying to reproduce the results of a previous world generation. See also the [[Advanced_world_generation#Seed_notes|seed notes section]] above.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEED:<text>]</nowiki></tt>
| <tt><nowiki>[SEED:31337]</nowiki></tt>
| rowspan="4" |
For each of these not in the config file, a random seed will be used, and the first seed is not used to generate the others. The seeds used are output to [[gamelog.txt]] when world generation starts.
|-
| <tt><nowiki>[HISTORY_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[HISTORY_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[NAME_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[NAME_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[CREATURE_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[CREATURE_SEED:31337]</nowiki></tt>
|}

=== World name ===
As previously mentioned, the title of the parameter set doesn't affect the name of the world. You can specify a particular name for your world, or leave the value blank for a random one. (The [[DFHack]] utility adds an option to rename the world using the in-game languages.)
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CUSTOM_NAME:<name>]</nowiki></tt>
| <tt><nowiki>[CUSTOM_NAME:Realm of Cheese Engravings]</nowiki></tt>
| For a random name, simply don't use this token.
|}

=== Embark Points ===
The number of points for equipment and animals when embarking in fortress mode (there is no equivalent setting for adventure mode). Normally, the default of 1504 is fine, but can be increased for various purposes like experimentation or to help dwarves survive in a particularly evil world, or reduced for certain [[challenges]].
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EMBARK_POINTS:<number>]</nowiki></tt>
| <tt><nowiki>[EMBARK_POINTS:1504]</nowiki></tt>
| 0 to 10,000
|}

=== End year ===
The maximum number of years generated for the world, although generation can be paused and the world used as is any time after the second year; the same as the [[World_generation#History|History]] parameter in basic world gen, except that you can enter an exact value. A too-short history can limit the materials available to civilizations, and [[Chosen|certain adventure mode features]] are only available after certain site events, while too long a history often leads to civilizations dying.

For more information on the history aspect of the game, see [[Legends]] and [[Calendar#Ages|Ages]].
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[END_YEAR:<number>]</nowiki></tt>
| <tt><nowiki>[END_YEAR:250]</nowiki></tt>
| 2 to 10,000
|}

=== Population cap after civ creation ===
A soft limit to the total number of [[historical figure]]s alive at the same time during generation across all civilizations, only preventing the birth of new historical figures.{{cite forum|140544/5701667}} Each civilization is allotted a percentage of the total by the percentage of sites they control.{{cite forum|159164/7553641}} Civilizations also have non-historical populations, and there is no setting to limit those (in early versions, all civilization members were historical figures, this is also why the name of this setting is misleading). Each [[entity]] also has limits from their raws, see the [[Entity_token#Population|population]] entity tokens, and setting this to unlimited will not remove those.

Huge historical figure populations can slow generation and the game in general.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_POPULATION:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_POPULATION:15000]</nowiki></tt>
| -1 to 100,000, -1 is no limit
|}

=== Site cap after civ creation ===
Total number of [[site]]s that can be directly created by all civilizations combined like [[hillocks]], [[hamlet]]s, [[dark pits]], [[forest retreat]]s, etc. Does not prevent the placement of initial civilization sites, though they will then be counted for the limit. Does not affect creature sites like [[cave]]s or [[lair]]s, group sites like [[castle]]s, [[monastery|monasteries]], [[tower_(necromancy)|tower]]s, [[fort]]s, or [[camp]]s, or unpopulated sites like [[tomb]]s. After this limit is reached, no civilization will be able to place new sites. See the [[Entity_token#Placement|placement]] entity tokens for other ways that civilization site placement can be limited.

Increasing this will slow generation down and reduce the available places for player sites. Since the {{token|MAX_SITE_POP_NUMBER|entity}} entity token limits the historical figure population per site, this site cap can also limit the total historical figure population of all civilizations combined, and some expand faster than others getting more sites before the limit is reached.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SITE_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SITE_CAP:1500]</nowiki></tt>
| -1 to 100,000, -1 is no limit
|}

=== Beast control ===

These parameters don't usually matter too much, but may matter for small numbers of beasts.

==== Percentage of Megabeasts and Titans Dead for Stoppage ====

The world starts out with a certain number of powerful megabeast and titan entities in existence. If a percentage of the megabeast and titan population dies out during history generation, then history generation will stop early. For example, if the elimination value is 80%, and the generated history starts with 200 entities and 160 of those 200 entities are eliminated by historical events before the End Year is reached, history generation will stop immediately.

If you want to end the creation of your world at the beginning of a certain age, choose the following values:
* Age of Legends: ~34%
* Age of Heroes: ~67%
If there are three or fewer titans or megabeasts in your world, the age will be given a special name reflecting the remaining megabeasts/titans, instead.

==== Year to Begin Checking Megabeast Percentage ====

The percentage of dead [[megabeast]]s and [[titan]]s for stoppage will not be checked until this year is reached in history generation. This can be used to ensure that a world reaches a certain year even if all of the megabeasts in the world are slain earlier.

If the number of living [[megabeast]]s and [[titan]]s starts at or drops to less than four, then world generation will always stop if the current year is equal to or greater than the Year to Begin Checking Megabeast Percentage ''regardless'' of how many [[megabeast]]s and [[titan]]s are dead — Percentage of Megabeasts and Titans Dead for Stoppage is ignored. The number of megabeasts and titans at the start of the world is set by the sum of the [[Advanced_world_generation#Max_Megabeasts_Caves|Max Megabeasts Caves]] and [[Advanced_world_generation#Titan_Parameters|Titan Number]] parameters.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[BEAST_END_YEAR:<year>:<percentage or -1>]</nowiki></tt>
| <tt><nowiki>[BEAST_END_YEAR:200:80]</nowiki></tt>
| Use -1 as percentage to disable. Year must still be at least 2.
|}

=== Cull Unimportant Historical Figures ===
{{main|Historical figure}}
Whether to remove unimportant dead historical figures after history generation; a short CPU-intensive step, but saves space which can speed up loading, saving, and running games with large histories. Legends mode will refer to culled creatures as "an unknown creature", and they will not appear in engravings, but likely would not have anyway.

Exactly what is considered important is not clear. A member of an abstract group killing a named creature is not. Creating an artifact is not, even if that artifact had important history. Unculled historical figures can have parentage described as "The identity of" that parent "has been lost to time", so just having children is not, though having living direct relations seems to prevent culling.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CULL_HISTORICAL_FIGURES:<0 or 1>]</nowiki></tt>
| <tt><nowiki>[CULL_HISTORICAL_FIGURES:0]</nowiki></tt>
| 0 = No, 1 = Yes
|}

=== Reveal All Historical Events ===

Setting this to Yes will allow access to most information about the history of the world in [[Legends mode]]. All events will be revealed, but some [[historical figure]]s, [[site]]s, [[region]]s, and [[civilization]]s and other entities may not be, possibly because they are not known to any civilization. If set to No, then you will have to discover historical information in [[adventure mode]] or by instructing dwarves to make engravings.{{Verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[REVEAL_ALL_HISTORY:<0 or 1>]</nowiki></tt>
| <tt><nowiki>[REVEAL_ALL_HISTORY::1]</nowiki></tt>
| 0 = No, 1 = Yes
|}

=== Terrain Parameters ===

These set limits and variance for terrain elevation, rainfall, temperature, drainage, volcanism, and savagery which determines how those values are generated. What biomes exist are then determined by how these factors overlap with each other.

==== Minima and Maxima ====
These are the absolute minimum and maximum values that can ever be generated for a particular map square characteristic. By ''subtly'' tweaking the min and max values, vastly different maps can be made. Changing these can cause the occurrence of certain [[Biome|biomes]] to become impossible, so you may want to use [[#Terrain Mesh Sizes and Weights|Weighted Ranges]] instead.

==== X and Y Variance ====
These control how wildly things like elevation and rainfall can vary between adjacent map squares. For example, if these values are set to the maximum of 3,200 for elevation then you will end up with more very low areas right next to very high areas. The number for X determines the east-west variance and the number for Y determines the north-south variance. By setting only one of these to a high value you can, for example, create horizontal or vertical bands of areas which are more similar to each other.

Generally speaking, raising both of these values will create a more random "patchwork" of many small biomes while setting both x and y values to 0 will cause every square on the map to use a single random value for the given characteristic.

For "patchwork" worlds to avoid being rejected, [[#Maximum Number of Subregions|Maximum Number of Subregions]] will probably need to be increased from the default.

==== Elevation ====
This controls the range of terrain elevations that can occur in the world. Usually, you just want to leave the min/max values alone. Raising the minimum elevation can, for example, make it impossible for oceans to exist. This does '''not''' directly control the number of available Z-levels at a particular site, though high maximum values may contribute to peaks, which can raise the number of above ground Z-levels - in other words, a maximum elevation of 400 and minimum of 1 does not mean you get 400 Z-levels, but it might increase the number of Z-levels somewhat in some regions compared to others. Raising the variance will result in a more bumpy, uneven landscape.

Some biomes/features that are impacted by elevation:
* A high minimum (above 99) means no oceans, as they need elevations below 100.
* A low maximum (below 300) means no mountains, as mountains need elevations above 300.
* Rivers will be placed when the elevation maximum is 104 or higher. Therefore, keeping both values above 100 and below 104 will prevent all water tiles from appearing.
* Mountain peaks can only form at elevations of 400.

==== Rainfall ====
Controls the amount of rainfall in each map square/area. Setting the minimum or maximum too high or low can make the formation of certain biomes impossible. Rainfall causes it to [[rain]] more in a given area, which can have various effects. Also makes more rivers appear on the world map.

Note that if [[#Do Orographic Precipitation and Rain Shadows|orographic precipitation and rain shadows]] is on, then mountains will cause additional variance in rainfall, so (for example) rainfall below the specified minimum can occur in the shadow of a mountain. If you want the minimum and maximum for this parameter to be absolutely respected, you must turn off the orographic precipitation option.

Additionally, with 'Orthographic Precipitation' turned on, orthographic precipitation and rain shadows will only occur in regions with greater than or equal to 50 drainage. [http://www.bay12forums.com/smf/index.php?topic=139916.0 [Report, reproduced 2022]]

==== Temperature ====
{{main|Climate|Temperature}}
These parameters control how hot or cold various areas will be. If you lower the minimum and maximum values, the world will be colder overall, for example. As with the others, changing these values too much could make it impossible for certain biomes to exist. The temperature scale used in this setting is related to regular degrees Urist by the equation "local temp = world temp * 0.75 + 10000".{{cite forum|169696/8395484}} This scale doesn't seem to be used anywhere else in the game. See [[Climate]] for more info.

These parameters form the "base" temperature for an area, and describe peak summer temperature in a scale that isn't used elsewhere in the game. This number also does not correspond 1:1 with the final climate. [[Temperature]] is always influenced by a number of variables, including elevation, time of year, thick forestation, and if [[Advanced_world_generation#Poles|poles]] are enabled, latitude. These other variables are factored in after the temperature mesh is applied, and frequently bring temperatures above and below their set minimum and maximum values. ''The inclusion of Poles is particularly strong in this regard, as it allows latitude to raise and/or lower temperatures by more than 75 degrees Celsius! That said, the temperatures aren't raised or lowered by more than about 65 degrees past the set minimum and maximum. Furthermore, for typical ranges, the temperature will never be raised more than about 25 degrees past the maximum (but will still drop up to about 65 degrees Celsius below the minimum).'' (unsure about exact values, research needed)

Elves can spawn where the temperature is 10 degrees or warmer, and humans can spawn where the temperature is 0 degrees or warmer.

==== Drainage ====
Changing drainage parameters will change the way water-affected biomes are formed. Low drainage will contribute to the formation of [[Lake|lakes]], [[River|rivers]], and [[Swamp|swamps]]. High drainage will cause water to sink into the ground rather than sit on the surface, which is important for forming hills.

Lower drainage values have been reported to contribute to the formation of thicker soil layers, though it is currently unknown exactly how other factors (such as elevation or perhaps rain) impact soil formation.

==== Volcanism ====
Volcanism controls the occurrence of igneous [[layer]]s, and the formation of volcanoes. For a volcano to form, a square must have a volcanism value of 100, so reducing the maximum from 100 will make volcanoes impossible. Raising the minimum will increase the rarity of non-igneous layers.

Setting the minimum to a high value is not a good way to produce multiple volcanoes, as you are likely to get a "Volcanism not evenly distributed" rejection. Instead, use the Minimum Number of Volcanoes parameter, and possibly adjust the weighted ranges for volcanism as described below.

==== Savagery ====
These parameters control the level of [[Surroundings#Savage|savagery]] on the map. Raising the minimum savagery too high may make it impossible for certain races to exist, and similarly lowering the maximum too far can make it impossible for certain creatures to exist. The largest chance of having unusable maps comes from a too-high savagery value.

==== Configuration Tokens ====
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[ELEVATION:1:400:401:401]</nowiki></tt>
| Range: 0 to 400 Maximum of 400 required for mountain peaks. Variance range: 0-3200
|-
| <tt><nowiki>[RAINFALL:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[RAINFALL:0:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|-
| <tt><nowiki>[TEMPERATURE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE:25:75:200:200]</nowiki></tt>
| Range: -1000 to 1000 Variance range: 0-3200
|-
| <tt><nowiki>[DRAINAGE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE:0:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|-
| <tt><nowiki>[VOLCANISM:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM:1:100:200:200]</nowiki></tt>
| Range: 0 to 100 Maximum of 100 required for volcanoes. Variance range: 0-3200
|-
| <tt><nowiki>[SAVAGERY:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY:1:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|}

=== Terrain Mesh Sizes and Range Weights ===
[[File:World_map-large-32x32-elevation-mesh.png|thumb|300px|A large world generated with an Elevation Mesh Size of 32×32 and range weights set to 1:0:0:0:1 (i.e., only extreme high and low elevations). Note how the grid intersections are either set very high (mountains) or very low (oceans) and the space between them is smoothed out.]]
These parameters influence the relative proportions of terrain feature ranges, without making other ranges impossible. For example, to have many more low-elevation squares exist, without making it impossible for high elevations; this makes changing these parameters often preferable to simply changing the above min/max values. See the image on the right for an example.

The basic steps of applying weighted ranges are as follows:
# Divide the world into a grid of quantity <code>2''MeshSize'' - 1</code> areas in both X and Y direction.
# At each grid intersection, set the value according to the weighted ranges.
# Smooth out the areas between the intersection points.
# Add noise according to the variance parameters.
Where ''MeshSize'' is the raw parameter value found in the <code>[[world_gen.txt]]</code>.

==== Interaction between Mesh Size and Weighted Ranges ====
Mesh size determines how many intersection points the world will have. As an example, setting it to 2×2 means the world will be divided into 4 areas, 2 across and 2 tall, and there will be a total of 9 intersection points (3×3). The grid intersection points are in the middle of world tiles, and the minimum size for a grid area is a span of 9 world tiles in either direction, with adjacent areas sharing an overlapping world tile. On a pocket world, this means one grid tile will span 9×9 world tiles, whereas on a large world, one grid tile will span 129×129 world tiles. A pocket world will always use a 2×2 grid of 9×9 world tiles, since it has only 17×17 tiles total (even if the game UI allows setting those worlds to a 4×4 grid, which can happen when changing the world size; changing the world size doesn't adjust mesh size limits, but saving then reloading the parameters does). A world that is 17 tiles wide, but 257 tall, and set to a 32×32 mesh size, will have 3×33 intersection points.

Setting mesh size to something other than Ignore, will apply random values at those intersections, with those random values being more likely to be in the ranges with higher weights. Setting to Ignore will cause the weighted range settings to be ignored for that terrain characteristic; instead setting the 4 corners of the world to completely random values and smoothing between those.

For example, if the Elevation Weighted Range parameters are set to <code>60:10:10:10:10</code> (starting with the 0-20 range, and these values do not need to add up to any particular number), and elevation min and max are left at the defaults of 1 and 400 respectively, then about 60% (on average) of the grid line intersection points will be set to an elevation in the range of 1-80 (0% to 20%), and the other ranges will be represented by around 10% of the intersection points each. The exact distribution is still left up to chance, though ''on average'' it will be close to this specification. This allows random number generation to be non-linear for the given terrain characteristic.

Setting the weight for a range to None only prevents intersection points from being set to a value in that range; terrain between intersection points can still be smoothed to values in ranges set to None that are between the intersection point values.

Weighted ranges do not make rejection checks, although they can be responsible for many rejections if you neglect to adjust or disable some of the [[#Minimum Number of Mid/Low/High Characteristic Squares|Minimum Number of Mid/Low/High Characteristic Squares]], for example.

==== Interaction between these and Variances ====
The end result can vary greatly depending on how the corresponding [[#X_and_Y_Variance|X and Y Variance]] parameters are set. First of all, if the variance is too high, the noise it adds can completely negate the effect of the weighted ranges. For instance, with a 2×2 mesh, the default variance parameters are high enough that usually the mesh grid can hardly be recognized. How strong the variance's effect is, is also dependent on the mesh size. Having a larger mesh size (i.e. smaller grid tiles) means the variance also has to be higher for a visible effect. For instance, with a variance of 400, the effects are clearly visible with a 2×2 mesh and barely visible at all with a 8×8 mesh. Note that this effect is directly dependent on the mesh size and not, as one might expect, on the actual size of the grid tiles. This means, that a large world with a 32×32 mesh will look essentially the same as a pocket world with a 2×2 mesh, only stretched to 256 times the size.

Also see this [http://www.bay12forums.com/smf/index.php?topic=139916.0 forum post] for more details.

==== Configuration Tokens ====
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[ELEVATION_FREQUENCY:2:1:2:3:4:5]</nowiki></tt>
| rowspan="6" | Valid mesh values:

1 = Ignore

2 = 2x2

3 = 4x4

4 = 8x8

5 = 16x16

6 = 32x32

(limited by world size)
|-
| <tt><nowiki>[RAIN_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[RAIN_FREQUENCY:3:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[DRAINAGE_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE_FREQUENCY:4:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[TEMPERATURE_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE_FREQUENCY:1:1:1:1:1:1]</nowiki></tt>
|-
| <tt><nowiki>[SAVAGERY_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY_FREQUENCY:5:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[VOLCANISM_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM_FREQUENCY:1:1:1:1:1:1]</nowiki></tt>
|}

=== Poles ===

With this, you can influence how polar regions are added. The poles can be on the north or south edge, and the equator will be on the opposite edge, or in the middle if there are two poles. If poles are set to NONE, then there will be no seasonal changes in the weather (e.g. no winter snow in temperate biomes).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[POLE:<placement>]</nowiki></tt>
| <tt><nowiki>[POLE:NORTH]</nowiki></tt>
| Viable options: NONE, NORTH_OR_SOUTH, NORTH_AND_OR_SOUTH, NORTH, SOUTH, NORTH_AND_SOUTH
|}

=== Minimum Mountain Peak Number ===

This will cause the world to be rejected if fewer than this many peaks (based on elevation) are present on the map. EG: elevations of 400 must be possible for mountain peaks to occur. If set to zero, then worlds will not be rejected based on number of peaks.

You may need to adjust elevation parameters, such as the highest weighted range, in order to get the desired number of elevation-400 squares needed for larger numbers of peaks. Like volcanoes, mountain peaks can make embark zones more interesting, but other than that, they don't appear to "do" anything special. Reportedly, they do increase the highest Z-level above ground in all embark zones in the same region, even if the selected embark zone does not include the peak.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PEAK_NUMBER_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[PEAK_NUMBER_MIN:20]</nowiki></tt>
| Elevations of 400 must occur for peaks to form.
|}

=== Minimum Partial Edge Oceans ===

This will cause a world to be rejected unless there are at least this many oceans touching an edge of the map. If set to zero then worlds will not be rejected based on this criterion. Setting both this parameter and Minimum Complete Edge Oceans to values that total more than 4 when added together may cause all worlds to be rejected as you can't have both a partial and complete edge ocean on a given edge.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PARTIAL_OCEAN_EDGE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[PARTIAL_OCEAN_EDGE_MIN:2]</nowiki></tt>
| Maximum of 4
|}

=== Minimum Complete Edge Oceans ===

This will cause a world to be rejected unless there are at least this many oceans which completely cover an edge of the map. Since a square map only has 4 edges, the maximum value possible is 4. If set to zero then worlds will not be rejected based on this criterion but still might end up with complete edge oceans by chance.

Note that the ability for this many edge oceans to exist will be limited by elevation. Therefore, to actually create large oceans you will probably need to change things like the Elevation Mesh Size and Weighted Ranges to increase the number and distribution of very low elevation squares on the map. In addition, if Complete Edge Oceans is set to any value ''other'' than 0 or 4, you may need to lower elevation variance for at least one of the axes: if set too high, such as a variation of 1600 for both X and Y axes (the default for Large Island and Medium Island parameter sets), the game may generate worlds very slowly or even hang.{{bug|565}}

Given appropriate weight, range, and variance values for things like elevation, a setting of: 1 results in a world that seems like a chunk of coastline. One edge of the map will be completely underwater and there will be ocean taking up much of the map on that side (think the east or west coast of the United States, the north coast of Canada, or southern Europe). If your edge ocean happens to pick your world's frozen side, most of it will be glacier.

*2 results in another coastline along with the first one -- the map could end up looking something like Panama if the oceans pick opposite sides of the map.
*3 results in a peninsula, like Florida in the US. There will be oceans surrounding 3 sides of the map, and land touching only one side of the map.
*4 results in one or more island(s) depending on things like elevation variance and weights. Regardless of whether you get one island or multiple islands, the entire map will be surrounded by water.

Unfortunately, there's no easy way to control which oceans end up on which edges, except perhaps setting X/Y variance to different values.

Edge oceans will take up part of the other edges too. For example, a full edge ocean on the east side will have part of the north and south sides underwater, but that does ''not'' add to the ''partial'' edge oceans count.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[COMPLETE_OCEAN_EDGE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[COMPLETE_OCEAN_EDGE_MIN:0]</nowiki></tt>
| Maximum of 4
|}

=== Minimum Volcano Number ===

The game will attempt to place this many volcanoes, but there must be at least this many squares with a volcanism of 100, if there are not the world will be rejected. Therefore, [[Advanced_world_generation#Volcanism|maximum volcanism]] above must be set to 100, and adjusting the [[Advanced_world_generation#Configuration_Tokens_2|volcanism weighted range]] above for 80-100 to a higher value can increase the number of those squares.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[VOLCANO_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[VOLCANO_MIN:15]</nowiki></tt>
| Volcanoes require a volcanism of 100 to occur.
|}

=== Mineral Scarcity ===
Controls the frequency at which minerals occur; setting this value higher will decrease both the number of different types and amounts of ore and gems present on a map. The default value will result in many metal ores, while the old default of ''sparse'' would be only a few ores, which may be limiting until other metals can be requested and traded for.

The options "Very Rare", "Rare", "Sparse", "Frequent", and "Everywhere" in the [[World_generation#Basic_world_generation_menu|basic world generation menu]] use the values 50000, 10000, 2500, 500 and 100 respectively.

According to [http://www.bay12forums.com/smf/index.php?topic=79018.msg2063804#msg2063804 research] by Shandra in v0.31.25, this is the relationship between the value of this setting and the approximate number of gems and ore:

[[File:MineralSetting_v25_limit10k.png]]

This is for the same 8x8 embark region in a world which is otherwise the same, except for the mineral scarcity parameter (although most of the detailed information comes from experiments with previous versions). (The chart legend has an error, the first "Pot.(Types)" should read "Pot.(Amount)".)
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MINERAL_SCARCITY:<number>]</nowiki></tt>
| <tt><nowiki>[MINERAL_SCARCITY:100]</nowiki></tt>
| Range: 100 to 100,000
|}

=== Max Megabeast Caves ===

This is the number of [[megabeast]]s placed at the beginning of history. Megabeasts are [[hydra]]s, [[bronze colossus]]es, [[roc]]s, and [[dragon]]s, which are all placed in equal proportions [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415177#msg3415177 data].

Increasing this value can lead to early extinction of civilizations.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[MEGABEAST_CAP:75]</nowiki></tt>
| Megabeasts count towards BEAST_END_YEAR calculation.
|}

=== Max Semi-Megabeast Caves ===

This is the number of [[semi-megabeast]]s placed at the beginning of history. Semimegabeasts are [[giant]]s, [[ettin]]s, [[minotaur]]s, and [[cyclops]], which are placed in equal proportions [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415188#msg3415188 data].

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEMIMEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SEMIMEGABEAST_CAP:150]</nowiki></tt>
| Semimegabeasts do not count towards the BEAST_END_YEAR calculation.
|}

=== Titan Parameters ===

==== Number ====

This controls the number of [[titan]]s that exist at the beginning of history[http://www.bay12forums.com/smf/index.php?topic=112465.msg3415203#msg3415203 data]. The number of forgotten beasts is unaffected by this parameter [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415155#msg3415155 data].

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TITAN_NUMBER:33]</nowiki></tt>
| Titans count towards BEAST_END_YEAR calculation.
|}

==== Attack Population Requirement ====

[[Titan]]s will begin to attack your fort once at least this many dwarves inhabit it, regardless of whether any other attack criteria have been met.

This number defaults to 80, which isn't usually too difficult to deal with.

==== Exported Wealth Requirement ====

Titans will begin to attack your fort once you have exported at least this many [[Currency|dwarfbucks]]-worth of goods, regardless of whether or not any other criteria have been met. This parameter defaults to None (disabled).

==== Created Wealth Requirement ====

Titans will begin to attack your fort once the fort's total wealth has reached this many [[Currency|dwarfbucks]] in value. This happens regardless of whether any of the other criteria, such as population, have been met; therefore, even with 1 dwarf, a fort could be attacked if the fort were worth at least this value.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_ATTACK_TRIGGER:<population>:<exp wealth>:<created wealth>]</nowiki></tt>
| <tt><nowiki>[TITAN_ATTACK_TRIGGER:80:0:100000]</nowiki></tt>
| 0 = None (disabled). Only one requirement must be met for an attack.
|}

=== Number of Demon Types ===

[[Demon]]s are similar to [[titan]]s and [[forgotten beast]]s, in that they are procedurally generated, but most are not unique. Thus, many different types of demons can exist in the world, but there will also be many individuals of most types. Thanks to [[Underworld spire|certain fun things]], fewer demon types also means fewer goblin civilizations.{{cite forum|112465/7392706}} You need at least 2 demon types, or else goblin civilizations won't exist initially, though if dwarves breach the underworld during world generation, at least one will be generated then.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DEMON_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[DEMON_NUMBER:52]</nowiki></tt>
| 0 to 1000
|}

=== Number of Night Troll Types ===

The number of different [[night troll]]s, also procedurally generated, that will exist in the world. Setting this to zero means that the world will have no night trolls, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[NIGHT_TROLL_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[NIGHT_TROLL_NUMBER:77]</nowiki></tt>
| 0 to 1000
|}

=== Number of Bogeyman Types ===
The number of different [[bogeyman]] forms that will exist in the world. Bogeymen are procedurally generated, though their forms do not vary by much. Setting this to zero means that the world will have no bogeymen, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[BOGEYMAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[BOGEYMAN_NUMBER:27]</nowiki></tt>
| 0 to 1000
|}

=== Number of Nightmare Types ===
The number of different [[nightmare]] forms that will exist in the world. Nightmares are procedurally generated. Setting this to zero means that the world will have no nightmares, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[NIGHTMARE_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[NIGHTMARE_NUMBER:27]</nowiki></tt>
| 0 to 1000
|}

=== Number of Vampire Curse Types ===

The number of different types of [[Vampire|vampires]] that will exist in the world. Although they are generated at the start of a new world, they aren't different from each other. Setting this to zero means no vampires will exist.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[VAMPIRE_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[VAMPIRE_NUMBER:72]</nowiki></tt>
| 0 to 1000
|}

=== Werebeast Parameters ===

==== Number of Werebeast Curse Types====

The number of different types of [[werebeast]]s that can exist in the world. It is common for werebeasts, unlike vampires, to assume many different forms and variations, the most well-known of these amount to different species of animals, from lizards, to wolves, to even bears. Setting this to zero means no werebeasts will exist, and will also remove a large amount of [[fun]] from the game.

In vanilla, there are only 82 possible unique werebeast species. Any further species will generate as wereblobs.{{bug|13308}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[WEREBEAST_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[WEREBEAST_NUMBER:58]</nowiki></tt>
| 0 to 1000
|}

==== Attack Population Requirement ====

Werebeasts will begin to attack your fort once at least this many dwarves inhabit it, regardless of whether any other attack criteria have been met. This number defaults to 50 which will often be reached in the second year of the fort.

==== Exported Wealth Requirement ====
Werebeasts will begin to attack your fort once you have exported at least this many [[Currency|dwarfbucks]]-worth of goods, regardless of whether or not any other criteria have been met. This parameter defaults to 5000.

==== Created Wealth Requirement ====

Werebeasts will begin to attack your fort once the fort's total wealth has reached this many [[Currency|dwarfbucks]] in value. This happens regardless of whether any of the other criteria, such as population, have been met; therefore, even with 1 dwarf, a fort could be attacked if the fort were worth at least this value.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[WEREBEAST_ATTACK_TRIGGER:<population>:<exp wealth>:<created wealth>]</nowiki></tt>
| <tt><nowiki>[WEREBEAST_ATTACK_TRIGGER:50:5000:50000]</nowiki></tt>
| 0 = None (disabled). Only one requirement must be met for an attack.
|}

=== Number of Secret Types ===

The number of secrets that exist in the world. Currently, all secrets are secrets of life and death, and the ones holding these secrets are [[necromancer]]s, thus, setting this to zero means that no necromancers will appear.
Non-necromancer towers can still appear (extremely rarely) with zero secrets, constructed by independent undead groups.
The primary difference between having 1 or 1000 secrets is the chance of your world having any necromancer towers at all. With 1, this chance is low. With the default number, it's seemingly guaranteed.
Even with 1 secret, if you have any necromancer towers at all, it is likely a great number will quickly appear in world generation (though this isn't guaranteed).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SECRET_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[SECRET_NUMBER:52]</nowiki></tt>
| 0 to 1000
|}

=== Number of Regional Interaction Types ===

The number of interactions that can be caused in regions, which may incorporate evil rain and cloud types. Currently, only evil region interactions are generated this way.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[REGIONAL_INTERACTION_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[REGIONAL_INTERACTION_NUMBER:20]</nowiki></tt>
| 0 to 1000
|}

=== Number of Disturbance Interaction Types ===
The number of different [[Mummy|disturbed dead]] that can exist in the world. Setting this to zero should prevent any mummy from appearing{{verify}}, but it will not prevent the creation of [[tomb]]s.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DISTURBANCE_INTERACTION_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[DISTURBANCE_INTERACTION_NUMBER:10]</nowiki></tt>
| 0 to 1000
|}

=== Number of Evil Cloud / Evil Rain Types ===

This number specifies how many [[Weather#Evil weather|various face-melting, eye-boiling, and zombifyingly-fun]] clouds of pure evil may appear in your world. Setting this to zero means you no longer will ever have to deal with encroaching dust walls of doom in that world. It is generally advised to keep this value low...

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EVIL_CLOUD_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[EVIL_CLOUD_NUMBER:45]</nowiki></tt>
| 0 to 1000
|}

The latter number states how many different types of green-ooze drenchers, disconcerting blood-showers, and sickly yellow slime-baths can occur in your world. Compared to evil clouds though, this one hardly is worth stressing out about, usually.... Setting this to zero means the only semi-solid to fully-liquid fluids to fall from the sky will be pure H2O.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EVIL_RAIN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[EVIL_RAIN_NUMBER:352]</nowiki></tt>
| 0 to 1000
|}

=== Generate Divine Materials ===
This turns the generation of [[Divine_metal|divine metals]] on or off. It does not influence the creation of [[vault]]s. Probably determines whenever or not using divination dice spawns weapons.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GENERATE_DIVINE_MATERIALS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[GENERATE_DIVINE_MATERIALS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Generate Mythical Materials ===

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GENERATE_MYTHICAL_MATERIALS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[GENERATE_MYTHICAL_MATERIALS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Mythical Healing ===

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALLOW_MYTHICAL_HEALING:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_MYTHICAL_HEALING:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Divination, Experiments, and Necromancy types ===
These allow or disallow [[die|divination]], demon or necromancer [[experiment]]s, and the more advanced [[necromancer]] abilities.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALLOW_DIVINATION:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_DIVINATION:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_DEMONIC_EXPERIMENTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_DEMONIC_EXPERIMENTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_EXPERIMENTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_EXPERIMENTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_LIEUTENANTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_LIEUTENANTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_GHOULS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_GHOULS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_SUMMONS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_SUMMONS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Desired Good/Evil Square Counts ===

These values change the amount of [[Surroundings#Good|good or evil]] tiles on the map, depending on the size of the region they are being considered for. The counts are for all tiles in all subregions of a given size considered together, ''not'' counts for each subregion considered separately (all tiles in the same subregion share the same [[surroundings]] values).

As used here, a "subregion" is a named world area. Subregion names and locations for a generated world are viewable in legends mode under "Regions". Subregions are classified by size the same way for all map sizes: 1-24 tiles is Small, 25-99 tiles is Medium, and 100+ tiles is Large.

The counts used here will always be restricted to regions of the given size, no matter how large the count. Also, the count is more of a goal than a minimum or maximum. As a result, you can end up with many more or many fewer than the requested number of squares in some situations. In particular, if you have something like a case where only 3 large regions exist in a world, and you request "1 evil square" in large regions, you will end up with one of the large regions being ''entirely evil''. So any non-zero value in one of these settings essentially means "force at least one region of this size to be all good/evil."

Note that the "evilness" of evil biomes is also impacted by savagery. Certain civilizations cannot exist in good and/or evil squares, so too many of one or the other may limit the size of certain types of civilizations - dwarves, for example, need non-aligned biomes. Creating too many evil biomes seems to lead to the danger of many civilizations' early extinction.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GOOD_SQ_COUNTS::<med region>:<lg region>]</nowiki></tt>
| <tt><nowiki>[GOOD_SQ_COUNTS:100:1000:2000]</nowiki></tt>
| rowspan="2" | Set count to zero to disable for that region size.
|-
| <tt><nowiki>[EVIL_SQ_COUNTS::<med region>:<lg region>]</nowiki></tt>
| <tt><nowiki>[EVIL_SQ_COUNTS:100:1000:2000]</nowiki></tt>
|}

=== Minimum Biome Square Counts ===

These numbers control whether or not a world will be rejected based on a lack of different [[biome|biomes]]. Raising these numbers will '''not''' automatically generate the given number of squares of the given biome! For a biome to exist, certain conditions like elevation and rainfall must exist.

These parameters simply filter out worlds that (for example) randomly fail to have enough high elevation squares to support a given number of mountains, etc. Some settings may cause worlds to always be rejected. For example, if for some reason the maximum elevation parameter is set to a value below what will support mountain biomes, it will be impossible to satisfy a non-zero requirement for mountain squares. The same principle goes for other conditions and biomes such as low elevations and oceans, etc.

Certain civilizations require different biomes to exist (such as dwarves and mountains), so eliminating certain biomes will make it impossible for certain civilizations to form.

These parameters often result in infinite world rejection problems. See [[World rejection]] for information on solving problems related to worlds always being rejected due to one or more of these parameters.

0 means no minimum for rejection - setting it to 0 does not guarantee 0 squares of that biome.

==== Biome Type Requirement Table ====

Terrain requirements for various biomes are described below.{{Verify}} Note that some of the exact ranges are unknown.

{| {{prettytable}}
|- bgcolor="#dddddd"
! rowspan="2" | Biome
! colspan="4" | Terrain Requirement
|-
! Elevation
! Rainfall
! Temperature
! Drainage
|-
| Swamp/Marsh
| 100-299
| 33-100
| Non-Freezing
| 0-32
|-
| Desert/Badland
| 100-299
| 0-9
| non-freezing
| note1
|-
| Forest
| 100-299
| 66-100
| non-freezing
| 66-100
|-
| Mountains
| 300-400
| N/A
| N/A
| N/A
|-
| Ocean
| 0-99
| N/A
| N/A
| N/A
|-
| Glacier
| 100-299
| N/A
| Freezing
| 80(?)-100
|-
| Tundra
| 100-299
| N/A
| Freezing
| 0-66
|-
| Grassland
| 100-299
| 0-66
| Non-Freezing
| 0-66
|-
| Hills
| 100-299
| 0-66
| Non-Freezing
| 66-100
|}
note1 drainage: 00-32 sand desert, 33-49 rocky wasteland, 50-65 rocky wasteland but different characters/appearance, 66-100 badlands

==== Minimum Initial Square Count ====

'''Note: The exclusive purpose of these parameters is to cause world rejection.'''

This is the minimum number of squares of the given biome that must exist before things like erosion take place. One thing to keep in mind is the maximum number of squares on a map of a given size - if the total number of squares on a map is lower than the sum of all square count parameters, then you will get infinite world rejection.

To determine the number of squares on a map, just multiply the dimensions. In practice these parameters will need to sum to lower than the maximum because some space is needed for "slack".

{| {{prettytable}}
|- bgcolor="#dddddd"
! Map Size
! Number of Squares
|-
| 17×17
| 289
|-
| 33×33
| 1089
|-
| 65×65
| 4225
|-
| 129×129
| 16614
|-
| 257×257
| 66049
|}

==== Minimum Initial Region Count ====

This is the minimum number of regions of contiguous biome squares that must exist before other processes such as erosion take place.

==== Minimum Final Region Count ====

This many regions of the given biome must exist after erosion and similar phases of generation have been completed.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[REGION_COUNTS:SWAMP:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:SWAMP:1032:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:DESERT:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:DESERT:1032:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:FOREST:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:FOREST:4128:13:12]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:MOUNTAINS:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:MOUNTAINS:8256:9:9]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:OCEAN:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:OCEAN:8256:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:GLACIER:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:GLACIER:0:0:0]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:TUNDRA:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:TUNDRA:0:0:0]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:GRASSLAND:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:GRASSLAND:8256:13:12]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:HILLS:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:HILLS:8256:13:12]</nowiki></tt>
|}

=== Erosion Cycle Count ===

Tells the world generator how long the world has to erode its tall peaks down to mountainsides during the 'running rivers...' stage of world creation. The higher this number, the less jagged the world will be, and the more wide the major rivers will be. If you use the maximum number, your mountains will dissolve before your eyes into plains which can lead to rejections if there aren't enough mountains to use for river start points and dwarven civilization origin points.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EROSION_CYCLE_COUNT:<number>]</nowiki></tt>
| <tt><nowiki>[EROSION_CYCLE_COUNT:250]</nowiki></tt>
| Range: 0 to 1000
|}

=== Minimum/Desired River Start Locations ===

This is the minimum number of riverheads that must exist before and after erosion takes place. Worlds will be rejected if they fail to meet these numbers. As with minimum biome counts, raising this number doesn't automatically create this many riverheads. Other conditions like terrain and rainfall must exist for rivers to form.

Extremely high pre-erosion values speed erosion greatly, while low post erosion values are useful for limiting rejects due to lack of river origin points. One can try the 800 value to get more lakes.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[RIVER_MINS:<min pre-erosion>:<des post-erosion>]</nowiki></tt>
| <tt><nowiki>[RIVER_MINS:200:400]</nowiki></tt>
| Range: 0 to 800
|}

=== Periodically Erode Extreme Cliffs ===

If enabled, makes every impassable rock wall into a series of ramps. Some prefer to pump up erosion to about 250, and turn the "Desired pre-erosion river count" to 0 for good erosion and no extra canyons.

Normally this is set to Yes (1).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PERIODICALLY_ERODE_EXTREMES:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[PERIODICALLY_ERODE_EXTREMES:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Do Orographic Precipitation and Rain Shadows ===

Toggle that allows terrain height to affect rainfall. For example, moist air coming from the ocean blows over the land. As the terrain gets higher, it forces the moist air up, causing it to rain on the seaward side of a mountain. Eventually, all the rain has fallen if the mountain is tall enough. So, when the breeze goes over the top, there's no moisture left to fall on the other side, creating a rain-shadow. In the current version, regions where drainage is above 50 will also create rain shadows, regardless of the underlying biome and elevation.{{cite forum|140685/5484064}}

Turning this on should create a tendency for more extreme rainfall in regions, creating more forests, deserts, marshlands, and grasslands. Also note that it can create rainfall outside of min-max rainfall settings, so even in a world with a 0 max rainfall you may get rainfall biomes. Turning it off should result in more controllable, less complex rainfall conditions based on rainfall parameters as it adds a random element which can distort or otherwise mess up the climates on a pregenerated map.

This should be disabled if you're importing a map or using a preset map file that has weather.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[OROGRAPHIC_PRECIPITATION:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[OROGRAPHIC_PRECIPITATION:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Maximum Number of Subregions ===

This is the number of separate biomes (the flashing regions you see on embark when you hit F1, F2, etc. when there's more than one biome on the embark location) that are allowed to exist on the entire map.

Setting this to very low values will result in numerous rejections depending on [[#X and Y Variance|variance parameters]]. If variance values are set to high numbers, many small biomes will be created causing rejection if this parameter value is not increased beyond the default.

Increasing the value of this tag is often a must when generating "patchwork" worlds with lots of biome variance, but simply increasing it without increasing variance parameters will not guarantee more biomes.

It is also interesting to note that the maximum subregions is 5000 which is more than the total number of squares for a pocket or small map. However, for a medium or large map (16641 or 66049 squares) it quickly becomes a mere fraction of the total number of possible subregions. In fact it would be quite easy on a large map to end up with far too many subregions and get endless rejections of this type.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SUBREGION_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[SUBREGION_MAX:2750]</nowiki></tt>
| Range: 1 to 5000
|}

=== Cavern Parameters ===
[[Caverns]] are the hollow areas underground, which dwarves tend to encounter when they're digging around. The '''Cavern Layer Number''' parameter determines how many cavern systems will be generated, not including the magma layer or the Bottom layer. Defaults to three - setting it to lower values could help FPS. Setting it to 2 will merge cavern 3 species into the 2nd cavern, and setting it to 1 will merge all into one cavern. However, disabling them entirely by setting it to 0 will make it impossible to grow any underground plants, as none will exist for your civilization to cultivate, nor will they be available on embark.

*Setting caverns to a sub-3 number (Spoiler, highlight to view) erases about one-third of HFS spires{{Bug|10267}} and prevents dig deep disasters. Additionally, random plant or animal species can be more frequently absent.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_COUNT:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_COUNT:3]</nowiki></tt>
| Range: 0 to 3
|}

==== Cavern Layout Parameters ====

Open caverns and dense passageways are not mutually exclusive. When both are raised, bizarre results can occur, such as layers showing a combination of open caverns, a cluster of network passages, and natural walls sprinkling the inside of an otherwise open cavern. [http://www.bay12forums.com/smf/index.php?topic=76355.msg1936859#msg1936859 Reference]

If you want the largest open spaces possible, then decrease the density and increase the openness. If you want a labyrinth of passageways, lower the openness and raise the passage density.

Another interesting note about the cavern layers is that the seed and number of demon types affect the layout of the caverns.

<gallery widths=200 heights=200 perrow=2>
File:Open00Density100.jpg|Cavern slice with Openness of 0 and Density of 100
File:Open100Density00.jpg|Cavern slice with Openness of 100 and Density of 0
File:Open100Density100.jpg|Cavern slice with Openness of 100 and Density of 100
File:Open50Density50.jpg|Cavern slice with Openness of 50 and Density of 50
</gallery>

===== Layer Openness min/max =====

Dictates the size of cavern passages. When Passage Density (see below) is set to minimum (0), caverns will be open expanses. Raising the maximum will increase the size of the caverns.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MAX:100]</nowiki></tt>
|}

===== Layer Passage Density min/max =====

Determines how many passages form the cavern. If openness (see above) is set to minimum and density increased, then you will get a maze-like network of small criss-crossing passages. Raising the values further increases the number of the maze-like passages.

Caverns will be large, open spaces at 0, and comprised of many small vertical shafts of rock at 100. Setting both values to be the same results in a uniform look for the caverns.{{Verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MAX:100]</nowiki></tt>
|}

===== Layer Water min/max =====

Determines the minimum and maximum percentage of water each cavern can contain.

Caverns with a water level of 10 or higher can support creatures and plants from the "Subterranean Water" biome, and caverns with a water level of 90 or lower can support the "Subterranean Chasm" biome; levels of 10-90 support ''both'' biomes, while levels below 10 or above 90 support only one.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_WATER_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_WATER_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_WATER_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_WATER_MAX:100]</nowiki></tt>
|}

==== Magma Layer ====

This parameter controls whether the [[magma sea]] exists.

Setting 1/Yes causes the magma layer to exist, value 0/No prevents it. Appears not to have any impact on volcanoes nor volcanism, so even if 0/No, there will still be embark locations with magma. If a [[volcano]] exists, it appears to always tap the magma sea, but the magma sea will not be revealed by revealing the volcano.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[HAVE_BOTTOM_LAYER_1:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[HAVE_BOTTOM_LAYER_1:1]</nowiki></tt>
|}

==== Bottom Layer ====

Determines if the space below the magma sea exists. If Yes the "HFS" layer is always present. Normally you want to leave this set to Yes for maximum fun.

If enabled, this will force the magma layer above it.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[HAVE_BOTTOM_LAYER_2:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[HAVE_BOTTOM_LAYER_2:1]</nowiki></tt>
|}

=== Z Levels (Depth) Settings ===

These parameters control the "thickness" of various "layers" on the map. Note that a "layer" in this case does not refer to one Z-level, but refers to a number of related Z-levels such as "levels above ground".

The following table assumes that you have 3 cavern layers. (out of a minimum of 0-3) The Levels Above Layer settings control how many Z-Levels are above each layer. A layer may itself consist of multiple Z-Levels (and almost always does).

{|style="margin:1em 1em 1em 0;background:#F9F9F9;border:1px #AAA solid;border-collapse:collapse;" class="wikitable"
|-style="background:#F2F2F2;text-align:center;"
!style="border:1px #AAA solid;padding:0.2em;" width="120"|Setting Name
!style="border:1px #AAA solid;padding:0.2em;" width="200"|Token
!style="border:1px #AAA solid;padding:0.2em;"| Description
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Ground
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_GROUND:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| The number of Z-levels of air above the highest surface level. Has no impact on how many Z-levels deep the surface layer is.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above layer 1
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_1:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of stone above the first cavern layer. Making this higher will guarantee ''at least'' that many levels to build your fortress, but will have no impact on how many z-levels thick the surface layer is. Also, the top of a cavern may be higher than the rest of a cavern, so in practice there will be more "solid" levels than this above the cavern.
As of version 0.31.25 this setting is inaccurate. The actual number of z-levels may vary in a range of approx. ±5, which may result in non-existence of any solid z-levels between a surface layer and first cavern layer.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 2
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_2:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very top of the second cavern and the very bottom of the first cavern.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 3
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_3:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very top of the third cavern and the very bottom of the second cavern.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 4
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_4:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very highest magma and the very bottom of the third cavern. Spoiler Hidden (select invisible text to read): Making this high will give a large area for HFS veins, so that it never touches caverns, giving more to mine '''if''' it was impacting the cavern previously.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 5
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_5:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Uncertain. May control the number of levels of "Semi Molten Rock" between HFS and Magma, may control number of levels of magma, may impact both. In experimentation, the overall depth of all magma sea and semi-molten rock levels appears to increase, but not consistent enough to say for certain. Only valid if Magma Layer present. Spoiler Hidden:Often the HFS vein will only extend as high as the highest magma, making this the only guaranteed way to increase amount of HFS to mine, but unfortunately also creating enormous useless semi-molten z-levels
|-
|style="border:1px #AAA solid;padding:0.2em;"| At Bottom
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_AT_BOTTOM:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Appears to be number of levels of HFS chamber. Only valid if Bottom Layer present, often having no impact. Values larger than default result in strange things.
|}

Some implications:
* The number of surface layers (e.g. soil), at this time, cannot be controlled. For example, on a map with 1 layer of peat, then a layer of silt, then a layer of obsidian, there is no control to let you increase either one to be, say, 20 z-levels. (though you may get lucky with the obsidian).
* There can be multiple stone layers between the cavern and the surface, so, increasing Levels Above Layer 1 may give you more conglomerate or more granite, and you have no control over which stone layer spans those Z-levels.
* The layers shown on embark span across the cavern layers in an unknown and inconsistent way. Sometimes those 10 different layers of stone are evenly distributed over your 400 z-level deep map, sometimes the first 9 get 1 z-level each and the last gets the other 391 levels. No way to control found yet.
* The HFS chamber, if present, will always extend into the rock layers, and appears to always make contact with the bottom cave. Large values for levels above layer 5 and layer 4 can result in enormous chambers, but the number of levels at the top (the part with undead) appears to be unaffected.
* Unconfirmed whether number of levels between caverns has any impact on cavern height. There will be connecting ramps and/or shafts between cavern layers no matter how many levels are between them.
* '''Very Important''': These values appear to apply across a whole 16x16 region, not just embark areas. That means that if a 16x16 region is completely flat, but has one tall mountain in one far corner, even if you set Levels Above Ground low (e.g. 2 z-levels) you still have all the empty air of the highest mountain in every embark tile (e.g. 200 z-levels). Also can happen to the semi-molten layer, and can lead to unexpected behavior.
* Very large or small values can cause strange things to happen.

=== Minimum/Maximum Natural Cave Size ===
It's not clear what effect these currently have, other than changing them can change the location of caves somewhat.{{verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVE_MIN_SIZE:<number>]</nowiki></tt>
| <tt><nowiki>[CAVE_MIN_SIZE:5]</nowiki></tt>
| rowspan="2" | Range: 1 to 500
|-
| <tt><nowiki>[CAVE_MAX_SIZE:<number>]</nowiki></tt>
| <tt><nowiki>[CAVE_MAX_SIZE:25]</nowiki></tt>
|}

=== Number of Caves ===
The number of caves generated in mountainous and non-mountainous regions, mountain caves will always be generated on the edge of mountain ranges next to non-mountainous regions. Lurking [[kobold]]s set up shop in caves, and store their stolen items there - a setting of 0 in both will stop kobold civilizations from appearing. Special note: a cave is not initially a [[lair]], although beasts can later use them as their lair.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[MOUNTAIN_CAVE_MIN:100]</nowiki></tt>
| rowspan="2" | Range: 0 to 800
|-
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:200]</nowiki></tt>
|}

=== Number of Mythical Sites ===
The number of [[mysterious dungeon|mysterious sites]] generated around the world. The extended effects of setting this to 0 has not been determined{{verify|is chosen still available? is quest still given? etc.}}.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MYTHICAL_SITE_NUM:<number>]</nowiki></tt>
| <tt><nowiki>[MYTHICAL_SITE_NUM:200]</nowiki></tt>
| rowspan="2" | Range: 0 to 800
|}

=== Make Caves Visible ===
If set to no (default) then the location of caves will not be marked on the map. If set to yes, caves will appear on the map so that they may be sought out or avoided as desired.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALL_CAVES_VISIBLE:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALL_CAVES_VISIBLE:0]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Init Options to Show Tunnels ===

If enabled, you will be able to see the underground tunnels often built by dwarves on the world map, and they will appear as black lines, similar to roads.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SHOW_EMBARK_TUNNEL:<0-2>]</nowiki></tt>
| <tt><nowiki>[SHOW_EMBARK_TUNNEL:2]</nowiki></tt>
| 0 = No 1 = Only in Finder 2 = Always
|}

=== Number of Civilizations ===

This number of [[civilization]]s will be placed on the map before history generation begins. These civilizations may later die out due to historical events. It is noteworthy that the chance for any given civilization to be destroyed through megabeasts decreases with a higher total number of civilizations present[http://www.bay12forums.com/smf/index.php?PHPSESSID=7348f68f41a9659443c05b2acf534e6c&topic=112465.15 data]. The five races are dwarf, elf, human, goblin, and kobold; they will generally be placed in equal numbers until the quota has been reached. If there are not enough biomes or other worldgen prerequisites for an even distribution, certain civs will be much more or less frequent than others[http://www.bay12forums.com/smf/index.php?PHPSESSID=7348f68f41a9659443c05b2acf534e6c&topic=112465.15 data]. If there is an odd number of civs (not divisible by 5), then the remainder is distributed randomly. Kobold civs require caves to be placed; if no caves exist, then kobolds are skipped and will not appear. This does not cause rejections [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415125#msg3415125 data]. Goblin civilizations require multiple demons, see the [[#Number_of_Demon_Types|number of demon types]] section above.

Note that a high value here can cause lots of map rejections, particularly on smaller maps as there simply isn't enough room or regions to put them all in.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_NUMBER:40]</nowiki></tt>
| Range: 0 to 300
|}

=== Playable Civilization Required ===

If this is set to yes (default) then worlds will be rejected if no civilization with [[Entity token|CIV_CONTROLLABLE]] can be placed. In an unmodded game, only the dwarves have this token.

If set to no, the result may be a world that cannot be played in Fortress Mode.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PLAYABLE_CIVILIZATION_REQUIRED:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[PLAYABLE_CIVILIZATION_REQUIRED:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Minimum Number of Mid/Low/High Characteristic Squares ===

Sets the minimum possible number of squares of certain ranges of each of the region qualities, such as elevation, rain, drainage, volcanism, savagery, and temperature. These need to be changed to reflect your regional meshes and weights, and are responsible for a HUGE number of map rejections. These values can all be set to 0 for much fewer map rejections, particularly in the case of more wacky, non-standard maps.

These values will cause worlds to be rejected unless at least the given number of squares of the given type are randomly generated. Setting these values too high could result in worlds always being rejected if other parameters such as the maximum/minimums for elevation, etc., don't allow enough of those squares to get generated.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[ELEVATION_RANGES:8256:16512:8256]</nowiki></tt>
| rowspan="5" | Minimum number of squares that must have low, medium, and high amounts of the given attribute. 
0 = No minimum
|-
| <tt><nowiki>[RAIN_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[RAIN_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[DRAINAGE_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[SAVAGERY_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[VOLCANISM_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM_RANGES:8256:16512:8256]</nowiki></tt>
|}

==World rejection==

:''Main article: [[World rejection]]''

If you are having the common problem of generated worlds always being rejected by the world generator, see [[v0.31:World rejection|Solving World Rejection Problems (v0.31 page)]] as it contains many detailed suggestions on how to troubleshoot and solve these issues.

== Parameter set examples ==

If you're trying to do something specific, then the [[Worldgen examples]] - complete parameter sets that can be copied directly into your ''world_gen.txt'' file and customized as desired - might be helpful.
If none of the examples suit your needs, [[Worldgen tricks]] has strategies and tips on making a world just right for you.

For many, many more examples see:
* [http://www.bay12forums.com/smf/index.php?topic=101280 DF2012 (v0.34) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=140180 DF2014 (v0.40) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=168543.0 DF2014 (v0.44.02+) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=175538 DF2014 (v0.47.01+) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=180805.0 DF2022 (v0.50.01+) WorldGen "Cookbook" Thread]

{{World}}

Advanced world generation

2026-04-10T03:16:52Z

Ziusudra: /* Interaction between Mesh Size and Weighted Ranges */ missing word

{{migrated article}}
{{Quality|Superior}}
{{av}}
:''This article contains information on advanced world generation. For information on basic world generation, see [[World generation]].'' ''See [[World token]] to more easily find information by the names used in the world_gen.txt file, [[World rejection]] for information on solving problems related to worlds always being rejected, and [[Worldgen examples]] for example worlds.''

[[File:adv_worldgen_v50.png|thumb|400px|right|The advanced world generation screen. ''(Click to enlarge)'']]'''Advanced world generation''', also labeled as '''detailed mode''', allows substantially more detail-oriented options of customization than standard, basic world generation. This gives the player much more control over how their world is generated. To better understand this article, it is advised that one should read about [[World generation|'''basic world generation''']] first.

The advanced world generation screen is reached by clicking "Create new world" at the main menu, then clicking "Detailed mode". Once at that screen, clicking "Basic options" will return the user to the standard world generation screen.

== Parameter sets ==
There are multiple default sets of all the advanced world generation parameters hard-coded in ''Dwarf Fortress'', which will be overridden by the <tt>prefs/world_gen.txt</tt> file in the main ''Dwarf Fortress'' directory, if it exists. It does not exist by default, you must create it, either by saving the default sets, or saving a copy from the [[world_gen.txt]] wiki page or elsewhere. This file can then be edited with a text editor, and you can copy and paste other players' sets of parameters into it. For sources of such parameter sets see [[Advanced_world_generation#Parameter_set_examples|Parameter set examples]] below.

To get back the default sets, move the existing <tt>prefs/world_gen.txt</tt> to somewhere else (like Documents), or delete it if you do not want to keep the changes, then load the sets in the game, it will then use the hardcoded defaults.

== User interface ==
First, there is a line of text inputs and buttons along the top of the screen, from left to right:
* The drop down menu of currently defined parameter sets, click the down arrow to select a set that you want to work with. The currently selected set can be renamed by clicking the current name or the [[File:Quill.png]] button. The first set in the file is selected by default, usually "LARGE ISLAND". See [[#Parameter set title|Parameter set title]].
* The dimensions of the world for the selected set, see [[#World dimensions|World dimensions]].
* A text entry box to set all of the seed options to the same seed, will show "Random seed", "Various seeds", or, if all four seeds are set to use the same value, that value. See [[Advanced_world_generation#Seed_values|Seed values]] and [[Advanced_world_generation#Seed_values|Seed notes]].
* The Copy Button to make a copy of the currently selected set and appends it to the bottom of the list.
* The red Delete button to delete the currently selected set, you will be prompted to confirm the deletion.
* The New parameter set to create a new parameter set and appends it to the bottom of the list. This seems to just copy the default "LARGE REGION" set.
* The Save button to save all of the current sets to the <tt>prefs/world_gen.txt</tt> file.
* The Load button to load from the same file, there is no confirmation, '''any unsaved changes will be lost'''. If that file does not exist, this resets all of the sets to the defaults.

Most of the middle is the parameters themselves, with a scroll bar to the right. Each row of the list can include:
* The name of the option
* The range of accepted values; not every option has this, and does not always match the displayed value, for example "0 to 1" might show as "No" and "Yes".
:* Sometimes the range might not initially show on rows that it should, reloading the sets with the Load button sometimes fixes that.{{bug|13176}}
* A plus button to increase the value or cycle through options, when applicable (this button will be missing if the range is missing.)
* The current value; can be clicked to edit, to actually set a value you must press {{k|enter}}, without doing that, clicking another entry box or right clicking will instead reset to the currently set value.
* An edit button to show that the previous box is editable, same as clicking on the text box.
* A minus button to decrease the value or cycle through options, when applicable (this button will be missing if the range is missing).
* A red button to disable this parameter, when applicable, usually setting the value to 0, or -1.

{{notice bar|bgcolor=#faa|bordercolor=#f00|All of the buttons below leave this screen and do not prompt to save the sets, so unsaved changes may be lost.}}
At the bottom right are 3 or 4 more buttons:
* The Create world button to do just that using the currently selected set, '''unsaved changes are lost'''.
* The Basic options button to go back to the normal world generation screen, unsaved changes are not lost if you come directly back to Detailed mode.
* The [[Mods]] button to go to the mod selection screen, unsaved changes are not lost if you come directly back to Detailed mode. Only shown if mods are available.
* Back to main menu button to do just that, '''unsaved changes are lost'''.

=== World painter ===
:''Main article: [[World painter]]
The '''world painter''' tool is not in the current version of ''Dwarf Fortress''; it allowed you to paint features onto a map. '''However''', those maps can still be used when generating a world by pasting world painter parameter set maps created in old versions into the <tt>prefs/world_gen.txt</tt> file. [[Utilities#Perfect_World_DF|Perfect World DF]] is a utility that uses the same parameter functionality as the world painter to paint a map, and it also can work with the current version of ''Dwarf Fortress''.

== Generating a world ==
You can either use an already-defined parameter set, or you can edit them, though it is highly suggested to edit a copy of one of the defaults. Once you are happy with the parameters you should save the values you just edited before you click the Create world button. Information about each parameter is documented below.

The phases of the world generation process are (this order is not completely correct):
* Preparing elevation...
* Setting temperature...
* Running rivers...
* Forming lakes and minerals...
* Growing vegetation...
* Verifying terrain...
* Importing wildlife...
* Recounting legends...
* Placing civilizations...
* Making cave civilizations...
* Making cave pops...
* Placing other beasts...
* Placing megabeasts...
* Placing good/evil...
* Placing caves...
* Prehistory generation
* Finalizing civ mats...
* Finalizing art...
* Finalizing uniforms...
* Finalizing sites...

== Seed notes ==
The world generation process uses a PRNG (Pseudo Random Number Generator) algorithm. A PRNG will produce a sequence of numbers that "looks" random, even though the actual sequence of numbers will always be the same if the PRNG is started with the same seed value. Basically this means that if you run world generation with a certain seed value on your computer, and someone else runs world generation with the same seed value on their computer, the same sequence of random numbers will be generated on both computers. The practical impact of this is that someone else can generate exactly the same world that you generated by entering the same seed value that you used.

In the current version, the seed values for the world itself and the names seem to produce the same result, but you will get changes in events which will result in a very different world history.{{bug|6934}} Keep this in mind if you want to regenerate a particular world.

The way that a world is generated can also be affected by certain world tokens. Changing them causes that code to use more or fewer PRNG values, causing later uses to get different parts of the sequence. So, you cannot for example, change the minimum and maximum rainfall and get 'the same world but drier or wetter', instead, a different world is generated. That said, it would also seem that certain small changes to these world tokens can occasionally generate a very similar world, however, other tokens are more sensitive. For more information see the forum thread [http://www.bay12forums.com/smf/index.php?topic=112132.msg3404199#msg3404199 here].

The following are tokens which use the PRNG values in ways that changing them will likely cause broader changes:

* [DIM:X:X]
* [ELEVATION:X:X:X:X]
* [RAINFALL:X:X:X:X]
* [TEMPERATURE:X:X:X:X]
* [DRAINAGE:X:X:X:X]
* [VOLCANISM:X:X:X:X]
* [SAVAGERY:X:X:X:X]
* [ELEVATION_FREQUENCY:X:X:X:X:X:X]
* [RAIN_FREQUENCY:X:X:X:X:X:X]
* [DRAINAGE_FREQUENCY:X:X:X:X:X:X]
* [TEMPERATURE_FREQUENCY:X:X:X:X:X:X]
* [SAVAGERY_FREQUENCY:X:X:X:X:X:X]
* [VOLCANISM_FREQUENCY:X:X:X:X:X:X]
* [PARTIAL_OCEAN_EDGE_MIN:X]
* [COMPLETE_OCEAN_EDGE_MIN:X]
* [HAVE_BOTTOM_LAYER_1:X]
* [MINERAL_SCARCITY:X] {{cite talk/this|Mineral scarcity}}

Many other world parameters, such as end year and embark points, can, however, be changed without it having any effect on the geography of the world generated from the seed values.

Normally, you don't enter these seed values, the game comes up with values based on some other sort of pseudo-random information from things like the current date and time.

When generating a world, ''Dwarf Fortress'' records the seeds it used in [[gamelog.txt]]; they can also be found with <code>gui/gm-editor world.worldgen.worldgen_parms</code> in [[DFHack]].

== Advanced parameters ==
There are essentially 4 types of controls for the generation of the surface map;

'''Terrain parameters''': as described below, these 5 variables define the basic background world, how hot or cold it is, how much rainfall, how high the mountains are. The world automatically goes through the temperature range along the Y axis, although sometimes it will be hotter in the north, other times in the south, or cold at both. Minimum, maximum and X,Y variance can drastically alter the world.

'''Weighted meshes''': these are a way to fine-tune the amount of the 5 basic variables on the map. They can be used to set the specific distribution of different elevations or rainfall areas for example.

'''Feature parameters''': such as rivers, mountain peaks, volcanoes, and oceans, which can cause rejections if the terrain parameters don't allow enough suitable locations for the features to be placed.

'''Rejection parameters''': ''Dwarf Fortress'' uses a 'belt-and-braces' approach to world generation. The above controls allow you to shape the world, then the rejection parameters throw it out if it does not meet certain criteria. There are a number of rejection parameters for the number and degree of the 5 basic variables, for biome types, etc. If the world does not meet the requirements of any one rejection parameter the world is rejected and re-randomised. Also see [[World rejection]].

Leaving tokens out of a set in <tt>world_gen.txt</tt> will cause the game to use default values which are not adjusted for smaller world sizes, this may cause smaller worlds to always be rejected.

If you are experimenting with world design, there is also a [[Settings#Feature_toggles|game setting]] that will log the rejection reasons to ``[[map_rejection_log.txt]]``. With that information you can then either adjust the rejection parameters to allow those worlds, or the other parameters to prevent them from trying to generate. ''Dwarf Fortress'' will keep adding to the file, so you may want to trim or delete it occasionally.

The parameters are described below in the order that they appear in the list in the game, which is not necessarily the order they appear in <tt>world_gen.txt</tt>. See [[world token]] for an index that will help you look things up by token name. The tokens used in <tt>world_gen.txt</tt> are at the bottom of each of the following parameter descriptions.

=== Parameter set title ===
This sets the name of the parameter set itself, as used in the list of sets (this has nothing to do with the name of the generated world).
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITLE:<name>]</nowiki></tt>
| <tt><nowiki>[TITLE:MEDIUM ISLAND]</nowiki></tt>
| Required
|}

=== World dimensions ===
The size of the map for the current set can be changed by changing the Width and Height values at the top next to the set title. You will need to confirm this, since changing the dimensions of the world will change other parameters, because many of them have different defaults depending on the surface area available.

Larger maps usually take longer to generate and may reduce [[Frames per second|FPS]] in-game, though this is really a matter of larger worlds usually having more civilizations, sites, historical figures, and events; restricting the number of those can speed up the process. Non-square maps may result in crashes{{bug|2928}}.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DIM:<width>:<height>]</nowiki></tt>
| <tt><nowiki>[DIM:257:257]</nowiki></tt>
| Valid values are 17, 33, 65, 129, and 257, other values will use one of those. Changing the size in the file without adjusting other parameters can cause many rejections.
|}

=== Seed values ===
Enables the use of, and specifies seed values for, different parts of the world generation process. Just entering a specific seed does not enable it, that must be done separately, although using the box at the top to set all the seeds to the same value does enable them all. Enabling a seed puts the token in using what ever is in the text box below. If you enable a seed, but do not enter a seed, the string "Seed text" will be used (<tt><nowiki>[SEED:Seed text]</nowiki></tt>). Trying to use a <tt><nowiki>]</nowiki></tt> in the string in the file will end the seed there, since it closes the token, any text after that will be ignored. Normally, just leave these set to Random, unless trying to reproduce the results of a previous world generation. See also the [[Advanced_world_generation#Seed_notes|seed notes section]] above.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEED:<text>]</nowiki></tt>
| <tt><nowiki>[SEED:31337]</nowiki></tt>
| rowspan="4" |
For each of these not in the config file, a random seed will be used, and the first seed is not used to generate the others. The seeds used are output to [[gamelog.txt]] when world generation starts.
|-
| <tt><nowiki>[HISTORY_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[HISTORY_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[NAME_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[NAME_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[CREATURE_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[CREATURE_SEED:31337]</nowiki></tt>
|}

=== World name ===
As previously mentioned, the title of the parameter set doesn't affect the name of the world. You can specify a particular name for your world, or leave the value blank for a random one. (The [[DFHack]] utility adds an option to rename the world using the in-game languages.)
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CUSTOM_NAME:<name>]</nowiki></tt>
| <tt><nowiki>[CUSTOM_NAME:Realm of Cheese Engravings]</nowiki></tt>
| For a random name, simply don't use this token.
|}

=== Embark Points ===
The number of points for equipment and animals when embarking in fortress mode (there is no equivalent setting for adventure mode). Normally, the default of 1504 is fine, but can be increased for various purposes like experimentation or to help dwarves survive in a particularly evil world, or reduced for certain [[challenges]].
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EMBARK_POINTS:<number>]</nowiki></tt>
| <tt><nowiki>[EMBARK_POINTS:1504]</nowiki></tt>
| 0 to 10,000
|}

=== End year ===
The maximum number of years generated for the world, although generation can be paused and the world used as is any time after the second year; the same as the [[World_generation#History|History]] parameter in basic world gen, except that you can enter an exact value. A too-short history can limit the materials available to civilizations, and [[Chosen|certain adventure mode features]] are only available after certain site events, while too long a history often leads to civilizations dying.

For more information on the history aspect of the game, see [[Legends]] and [[Calendar#Ages|Ages]].
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[END_YEAR:<number>]</nowiki></tt>
| <tt><nowiki>[END_YEAR:250]</nowiki></tt>
| 2 to 10,000
|}

=== Population cap after civ creation ===
A soft limit to the total number of [[historical figure]]s alive at the same time during generation across all civilizations, only preventing the birth of new historical figures.{{cite forum|140544/5701667}} Each civilization is allotted a percentage of the total by the percentage of sites they control.{{cite forum|159164/7553641}} Civilizations also have non-historical populations, and there is no setting to limit those (in early versions, all civilization members were historical figures, this is also why the name of this setting is misleading). Each [[entity]] also has limits from their raws, see the [[Entity_token#Population|population]] entity tokens, and setting this to unlimited will not remove those.

Huge historical figure populations can slow generation and the game in general.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_POPULATION:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_POPULATION:15000]</nowiki></tt>
| -1 to 100,000, -1 is no limit
|}

=== Site cap after civ creation ===
Total number of [[site]]s that can be directly created by all civilizations combined like [[hillocks]], [[hamlet]]s, [[dark pits]], [[forest retreat]]s, etc. Does not prevent the placement of initial civilization sites, though they will then be counted for the limit. Does not affect creature sites like [[cave]]s or [[lair]]s, group sites like [[castle]]s, [[monastery|monasteries]], [[tower_(necromancy)|tower]]s, [[fort]]s, or [[camp]]s, or unpopulated sites like [[tomb]]s. After this limit is reached, no civilization will be able to place new sites. See the [[Entity_token#Placement|placement]] entity tokens for other ways that civilization site placement can be limited.

Increasing this will slow generation down and reduce the available places for player sites. Since the {{token|MAX_SITE_POP_NUMBER|entity}} entity token limits the historical figure population per site, this site cap can also limit the total historical figure population of all civilizations combined, and some expand faster than others getting more sites before the limit is reached.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SITE_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SITE_CAP:1500]</nowiki></tt>
| -1 to 100,000, -1 is no limit
|}

=== Beast control ===

These parameters don't usually matter too much, but may matter for small numbers of beasts.

==== Percentage of Megabeasts and Titans Dead for Stoppage ====

The world starts out with a certain number of powerful megabeast and titan entities in existence. If a percentage of the megabeast and titan population dies out during history generation, then history generation will stop early. For example, if the elimination value is 80%, and the generated history starts with 200 entities and 160 of those 200 entities are eliminated by historical events before the End Year is reached, history generation will stop immediately.

If you want to end the creation of your world at the beginning of a certain age, choose the following values:
* Age of Legends: ~34%
* Age of Heroes: ~67%
If there are three or fewer titans or megabeasts in your world, the age will be given a special name reflecting the remaining megabeasts/titans, instead.

==== Year to Begin Checking Megabeast Percentage ====

The percentage of dead [[megabeast]]s and [[titan]]s for stoppage will not be checked until this year is reached in history generation. This can be used to ensure that a world reaches a certain year even if all of the megabeasts in the world are slain earlier.

If the number of living [[megabeast]]s and [[titan]]s starts at or drops to less than four, then world generation will always stop if the current year is equal to or greater than the Year to Begin Checking Megabeast Percentage ''regardless'' of how many [[megabeast]]s and [[titan]]s are dead — Percentage of Megabeasts and Titans Dead for Stoppage is ignored. The number of megabeasts and titans at the start of the world is set by the sum of the [[Advanced_world_generation#Max_Megabeasts_Caves|Max Megabeasts Caves]] and [[Advanced_world_generation#Titan_Parameters|Titan Number]] parameters.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[BEAST_END_YEAR:<year>:<percentage or -1>]</nowiki></tt>
| <tt><nowiki>[BEAST_END_YEAR:200:80]</nowiki></tt>
| Use -1 as percentage to disable. Year must still be at least 2.
|}

=== Cull Unimportant Historical Figures ===
{{main|Historical figure}}
Whether to remove unimportant dead historical figures after history generation; a short CPU-intensive step, but saves space which can speed up loading, saving, and running games with large histories. Legends mode will refer to culled creatures as "an unknown creature", and they will not appear in engravings, but likely would not have anyway.

Exactly what is considered important is not clear. A member of an abstract group killing a named creature is not. Creating an artifact is not, even if that artifact had important history. Unculled historical figures can have parentage described as "The identity of" that parent "has been lost to time", so just having children is not, though having living direct relations seems to prevent culling.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CULL_HISTORICAL_FIGURES:<0 or 1>]</nowiki></tt>
| <tt><nowiki>[CULL_HISTORICAL_FIGURES:0]</nowiki></tt>
| 0 = No, 1 = Yes
|}

=== Reveal All Historical Events ===

Setting this to Yes will allow access to most information about the history of the world in [[Legends mode]]. All events will be revealed, but some [[historical figure]]s, [[site]]s, [[region]]s, and [[civilization]]s and other entities may not be, possibly because they are not known to any civilization. If set to No, then you will have to discover historical information in [[adventure mode]] or by instructing dwarves to make engravings.{{Verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[REVEAL_ALL_HISTORY:<0 or 1>]</nowiki></tt>
| <tt><nowiki>[REVEAL_ALL_HISTORY::1]</nowiki></tt>
| 0 = No, 1 = Yes
|}

=== Terrain Parameters ===

These set limits and variance for terrain elevation, rainfall, temperature, drainage, volcanism, and savagery which determines how those values are generated. What biomes exist are then determined by how these factors overlap with each other.

==== Minima and Maxima ====
These are the absolute minimum and maximum values that can ever be generated for a particular map square characteristic. By ''subtly'' tweaking the min and max values, vastly different maps can be made. Changing these can cause the occurrence of certain [[Biome|biomes]] to become impossible, so you may want to use [[#Terrain Mesh Sizes and Weights|Weighted Ranges]] instead.

==== X and Y Variance ====
These control how wildly things like elevation and rainfall can vary between adjacent map squares. For example, if these values are set to the maximum of 3,200 for elevation then you will end up with more very low areas right next to very high areas. The number for X determines the east-west variance and the number for Y determines the north-south variance. By setting only one of these to a high value you can, for example, create horizontal or vertical bands of areas which are more similar to each other.

Generally speaking, raising both of these values will create a more random "patchwork" of many small biomes while setting both x and y values to 0 will cause every square on the map to use a single random value for the given characteristic.

For "patchwork" worlds to avoid being rejected, [[#Maximum Number of Subregions|Maximum Number of Subregions]] will probably need to be increased from the default.

==== Elevation ====
This controls the range of terrain elevations that can occur in the world. Usually, you just want to leave the min/max values alone. Raising the minimum elevation can, for example, make it impossible for oceans to exist. This does '''not''' directly control the number of available Z-levels at a particular site, though high maximum values may contribute to peaks, which can raise the number of above ground Z-levels - in other words, a maximum elevation of 400 and minimum of 1 does not mean you get 400 Z-levels, but it might increase the number of Z-levels somewhat in some regions compared to others. Raising the variance will result in a more bumpy, uneven landscape.

Some biomes/features that are impacted by elevation:
* A high minimum (above 99) means no oceans, as they need elevations below 100.
* A low maximum (below 300) means no mountains, as mountains need elevations above 300.
* Rivers will be placed when the elevation maximum is 104 or higher. Therefore, keeping both values above 100 and below 104 will prevent all water tiles from appearing.
* Mountain peaks can only form at elevations of 400.

==== Rainfall ====
Controls the amount of rainfall in each map square/area. Setting the minimum or maximum too high or low can make the formation of certain biomes impossible. Rainfall causes it to [[rain]] more in a given area, which can have various effects. Also makes more rivers appear on the world map.

Note that if [[#Do Orographic Precipitation and Rain Shadows|orographic precipitation and rain shadows]] is on, then mountains will cause additional variance in rainfall, so (for example) rainfall below the specified minimum can occur in the shadow of a mountain. If you want the minimum and maximum for this parameter to be absolutely respected, you must turn off the orographic precipitation option.

Additionally, with 'Orthographic Precipitation' turned on, orthographic precipitation and rain shadows will only occur in regions with greater than or equal to 50 drainage. [http://www.bay12forums.com/smf/index.php?topic=139916.0 [Report, reproduced 2022]]

==== Temperature ====
{{main|Climate|Temperature}}
These parameters control how hot or cold various areas will be. If you lower the minimum and maximum values, the world will be colder overall, for example. As with the others, changing these values too much could make it impossible for certain biomes to exist. The temperature scale used in this setting is related to regular degrees Urist by the equation "local temp = world temp * 0.75 + 10000".{{cite forum|169696/8395484}} This scale doesn't seem to be used anywhere else in the game. See [[Climate]] for more info.

These parameters form the "base" temperature for an area, and describe peak summer temperature in a scale that isn't used elsewhere in the game. This number also does not correspond 1:1 with the final climate. [[Temperature]] is always influenced by a number of variables, including elevation, time of year, thick forestation, and if [[Advanced_world_generation#Poles|poles]] are enabled, latitude. These other variables are factored in after the temperature mesh is applied, and frequently bring temperatures above and below their set minimum and maximum values. ''The inclusion of Poles is particularly strong in this regard, as it allows latitude to raise and/or lower temperatures by more than 75 degrees Celsius! That said, the temperatures aren't raised or lowered by more than about 65 degrees past the set minimum and maximum. Furthermore, for typical ranges, the temperature will never be raised more than about 25 degrees past the maximum (but will still drop up to about 65 degrees Celsius below the minimum).'' (unsure about exact values, research needed)

Elves can spawn where the temperature is 10 degrees or warmer, and humans can spawn where the temperature is 0 degrees or warmer.

==== Drainage ====
Changing drainage parameters will change the way water-affected biomes are formed. Low drainage will contribute to the formation of [[Lake|lakes]], [[River|rivers]], and [[Swamp|swamps]]. High drainage will cause water to sink into the ground rather than sit on the surface, which is important for forming hills.

Lower drainage values have been reported to contribute to the formation of thicker soil layers, though it is currently unknown exactly how other factors (such as elevation or perhaps rain) impact soil formation.

==== Volcanism ====
Volcanism controls the occurrence of igneous [[layer]]s, and the formation of volcanoes. For a volcano to form, a square must have a volcanism value of 100, so reducing the maximum from 100 will make volcanoes impossible. Raising the minimum will increase the rarity of non-igneous layers.

Setting the minimum to a high value is not a good way to produce multiple volcanoes, as you are likely to get a "Volcanism not evenly distributed" rejection. Instead, use the Minimum Number of Volcanoes parameter, and possibly adjust the weighted ranges for volcanism as described below.

==== Savagery ====
These parameters control the level of [[Surroundings#Savage|savagery]] on the map. Raising the minimum savagery too high may make it impossible for certain races to exist, and similarly lowering the maximum too far can make it impossible for certain creatures to exist. The largest chance of having unusable maps comes from a too-high savagery value.

==== Configuration Tokens ====
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[ELEVATION:1:400:401:401]</nowiki></tt>
| Range: 0 to 400 Maximum of 400 required for mountain peaks. Variance range: 0-3200
|-
| <tt><nowiki>[RAINFALL:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[RAINFALL:0:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|-
| <tt><nowiki>[TEMPERATURE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE:25:75:200:200]</nowiki></tt>
| Range: -1000 to 1000 Variance range: 0-3200
|-
| <tt><nowiki>[DRAINAGE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE:0:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|-
| <tt><nowiki>[VOLCANISM:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM:1:100:200:200]</nowiki></tt>
| Range: 0 to 100 Maximum of 100 required for volcanoes. Variance range: 0-3200
|-
| <tt><nowiki>[SAVAGERY:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY:1:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|}

=== Terrain Mesh Sizes and Range Weights ===
[[File:World_map-large-32x32-elevation-mesh.png|thumb|300px|A large world generated with an Elevation Mesh Size of 32×32 and range weights set to 1:0:0:0:1 (i.e., only extreme high and low elevations). Note how the grid intersections are either set very high (mountains) or very low (oceans) and the space between them is smoothed out.]]
These parameters influence the relative proportions of terrain feature ranges, without making other ranges impossible. For example, to have many more low-elevation squares exist, without making it impossible for high elevations; this makes changing these parameters often preferable to simply changing the above min/max values. See the image on the right for an example.

The basic steps of applying weighted ranges are as follows:
# Divide the world into a grid of quantity <code>2''MeshSize'' - 1</code> areas in both X and Y direction.
# At each grid intersection, set the value according to the weighted ranges.
# Smooth out the areas between the intersection points.
# Add noise according to the variance parameters.
Where ''MeshSize'' is the raw parameter value found in the <code>[[world_gen.txt]]</code>.

==== Interaction between Mesh Size and Weighted Ranges ====
Mesh size determines how many intersection points the world will have. As an example, setting it to 2×2 means the world will be divided into 4 areas, 2 across and 2 tall, and there will be a total of 9 intersection points (3×3). The grid intersection points are in the middle of world tiles, and the minimum size for a grid area is a span of 9 world tiles in either direction, with adjacent areas sharing an overlapping world tile. On a pocket world, this means one grid tile will span 9×9 world tiles, whereas on a large world, one grid tile will span 129×129 world tiles. A pocket world will always use a 2×2 grid areas of 9×9 world tiles, since it has only 17×17 tiles total (even if the game UI allows setting those worlds to a 4×4 grid, which can happen when changing the world size; changing the world size doesn't adjust mesh size limits, but saving then reloading the parameters does). A world that is 17 tiles wide, but 257 tall, and set to a 32×32 mesh size, will have 3×33 intersection points.

Setting mesh size to something other than Ignore, will apply random values at those intersections, with those random values being more likely to be in the higher weighted ranges. Setting to Ignore will cause the weighted range settings to be ignored for that terrain characteristic; instead setting the 4 corners of the world to completely random values and smoothing between those.

For example, if the Elevation Weighted Range parameters are set to <code>60:10:10:10:10</code> (starting with the 0-20 range, and these values do not have to add up to any particular number), and elevation min and max are left at the defaults of 1 and 400 respectively, then about 60% (on average) of the grid line intersection points will be set to an elevation in the range of 1-80 (0% to 20%), and the other ranges will be represented by around 10% of the intersection points each. The exact distribution is still left up to chance, though ''on average'' it will be close to this specification. This allows random number generation to be non-linear for the given terrain characteristic.

Setting the weight for a range to None only prevents intersection points from being set to a value in that range; terrain between intersection points can still be smoothed to values in ranges set to None that are between the intersection point values.

Weighted ranges do not make rejection checks, although they can be responsible for many rejections if you neglect to adjust or disable some of the [[#Minimum Number of Mid/Low/High Characteristic Squares|Minimum Number of Mid/Low/High Characteristic Squares]], for example.

==== Interaction between these and Variances ====
The end result can vary greatly depending on how the corresponding [[#X_and_Y_Variance|X and Y Variance]] parameters are set. First of all, if the variance is too high, the noise it adds can completely negate the effect of the weighted ranges. For instance, with a 2×2 mesh, the default variance parameters are high enough that usually the mesh grid can hardly be recognized. How strong the variance's effect is, is also dependent on the mesh size. Having a larger mesh size (i.e. smaller grid tiles) means the variance also has to be higher for a visible effect. For instance, with a variance of 400, the effects are clearly visible with a 2×2 mesh and barely visible at all with a 8×8 mesh. Note that this effect is directly dependent on the mesh size and not, as one might expect, on the actual size of the grid tiles. This means, that a large world with a 32×32 mesh will look essentially the same as a pocket world with a 2×2 mesh, only stretched to 256 times the size.

Also see this [http://www.bay12forums.com/smf/index.php?topic=139916.0 forum post] for more details.

==== Configuration Tokens ====
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[ELEVATION_FREQUENCY:2:1:2:3:4:5]</nowiki></tt>
| rowspan="6" | Valid mesh values:

1 = Ignore

2 = 2x2

3 = 4x4

4 = 8x8

5 = 16x16

6 = 32x32

(limited by world size)
|-
| <tt><nowiki>[RAIN_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[RAIN_FREQUENCY:3:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[DRAINAGE_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE_FREQUENCY:4:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[TEMPERATURE_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE_FREQUENCY:1:1:1:1:1:1]</nowiki></tt>
|-
| <tt><nowiki>[SAVAGERY_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY_FREQUENCY:5:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[VOLCANISM_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM_FREQUENCY:1:1:1:1:1:1]</nowiki></tt>
|}

=== Poles ===

With this, you can influence how polar regions are added. The poles can be on the north or south edge, and the equator will be on the opposite edge, or in the middle if there are two poles. If poles are set to NONE, then there will be no seasonal changes in the weather (e.g. no winter snow in temperate biomes).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[POLE:<placement>]</nowiki></tt>
| <tt><nowiki>[POLE:NORTH]</nowiki></tt>
| Viable options: NONE, NORTH_OR_SOUTH, NORTH_AND_OR_SOUTH, NORTH, SOUTH, NORTH_AND_SOUTH
|}

=== Minimum Mountain Peak Number ===

This will cause the world to be rejected if fewer than this many peaks (based on elevation) are present on the map. EG: elevations of 400 must be possible for mountain peaks to occur. If set to zero, then worlds will not be rejected based on number of peaks.

You may need to adjust elevation parameters, such as the highest weighted range, in order to get the desired number of elevation-400 squares needed for larger numbers of peaks. Like volcanoes, mountain peaks can make embark zones more interesting, but other than that, they don't appear to "do" anything special. Reportedly, they do increase the highest Z-level above ground in all embark zones in the same region, even if the selected embark zone does not include the peak.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PEAK_NUMBER_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[PEAK_NUMBER_MIN:20]</nowiki></tt>
| Elevations of 400 must occur for peaks to form.
|}

=== Minimum Partial Edge Oceans ===

This will cause a world to be rejected unless there are at least this many oceans touching an edge of the map. If set to zero then worlds will not be rejected based on this criterion. Setting both this parameter and Minimum Complete Edge Oceans to values that total more than 4 when added together may cause all worlds to be rejected as you can't have both a partial and complete edge ocean on a given edge.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PARTIAL_OCEAN_EDGE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[PARTIAL_OCEAN_EDGE_MIN:2]</nowiki></tt>
| Maximum of 4
|}

=== Minimum Complete Edge Oceans ===

This will cause a world to be rejected unless there are at least this many oceans which completely cover an edge of the map. Since a square map only has 4 edges, the maximum value possible is 4. If set to zero then worlds will not be rejected based on this criterion but still might end up with complete edge oceans by chance.

Note that the ability for this many edge oceans to exist will be limited by elevation. Therefore, to actually create large oceans you will probably need to change things like the Elevation Mesh Size and Weighted Ranges to increase the number and distribution of very low elevation squares on the map. In addition, if Complete Edge Oceans is set to any value ''other'' than 0 or 4, you may need to lower elevation variance for at least one of the axes: if set too high, such as a variation of 1600 for both X and Y axes (the default for Large Island and Medium Island parameter sets), the game may generate worlds very slowly or even hang.{{bug|565}}

Given appropriate weight, range, and variance values for things like elevation, a setting of: 1 results in a world that seems like a chunk of coastline. One edge of the map will be completely underwater and there will be ocean taking up much of the map on that side (think the east or west coast of the United States, the north coast of Canada, or southern Europe). If your edge ocean happens to pick your world's frozen side, most of it will be glacier.

*2 results in another coastline along with the first one -- the map could end up looking something like Panama if the oceans pick opposite sides of the map.
*3 results in a peninsula, like Florida in the US. There will be oceans surrounding 3 sides of the map, and land touching only one side of the map.
*4 results in one or more island(s) depending on things like elevation variance and weights. Regardless of whether you get one island or multiple islands, the entire map will be surrounded by water.

Unfortunately, there's no easy way to control which oceans end up on which edges, except perhaps setting X/Y variance to different values.

Edge oceans will take up part of the other edges too. For example, a full edge ocean on the east side will have part of the north and south sides underwater, but that does ''not'' add to the ''partial'' edge oceans count.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[COMPLETE_OCEAN_EDGE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[COMPLETE_OCEAN_EDGE_MIN:0]</nowiki></tt>
| Maximum of 4
|}

=== Minimum Volcano Number ===

The game will attempt to place this many volcanoes, but there must be at least this many squares with a volcanism of 100, if there are not the world will be rejected. Therefore, [[Advanced_world_generation#Volcanism|maximum volcanism]] above must be set to 100, and adjusting the [[Advanced_world_generation#Configuration_Tokens_2|volcanism weighted range]] above for 80-100 to a higher value can increase the number of those squares.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[VOLCANO_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[VOLCANO_MIN:15]</nowiki></tt>
| Volcanoes require a volcanism of 100 to occur.
|}

=== Mineral Scarcity ===
Controls the frequency at which minerals occur; setting this value higher will decrease both the number of different types and amounts of ore and gems present on a map. The default value will result in many metal ores, while the old default of ''sparse'' would be only a few ores, which may be limiting until other metals can be requested and traded for.

The options "Very Rare", "Rare", "Sparse", "Frequent", and "Everywhere" in the [[World_generation#Basic_world_generation_menu|basic world generation menu]] use the values 50000, 10000, 2500, 500 and 100 respectively.

According to [http://www.bay12forums.com/smf/index.php?topic=79018.msg2063804#msg2063804 research] by Shandra in v0.31.25, this is the relationship between the value of this setting and the approximate number of gems and ore:

[[File:MineralSetting_v25_limit10k.png]]

This is for the same 8x8 embark region in a world which is otherwise the same, except for the mineral scarcity parameter (although most of the detailed information comes from experiments with previous versions). (The chart legend has an error, the first "Pot.(Types)" should read "Pot.(Amount)".)
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MINERAL_SCARCITY:<number>]</nowiki></tt>
| <tt><nowiki>[MINERAL_SCARCITY:100]</nowiki></tt>
| Range: 100 to 100,000
|}

=== Max Megabeast Caves ===

This is the number of [[megabeast]]s placed at the beginning of history. Megabeasts are [[hydra]]s, [[bronze colossus]]es, [[roc]]s, and [[dragon]]s, which are all placed in equal proportions [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415177#msg3415177 data].

Increasing this value can lead to early extinction of civilizations.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[MEGABEAST_CAP:75]</nowiki></tt>
| Megabeasts count towards BEAST_END_YEAR calculation.
|}

=== Max Semi-Megabeast Caves ===

This is the number of [[semi-megabeast]]s placed at the beginning of history. Semimegabeasts are [[giant]]s, [[ettin]]s, [[minotaur]]s, and [[cyclops]], which are placed in equal proportions [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415188#msg3415188 data].

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEMIMEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SEMIMEGABEAST_CAP:150]</nowiki></tt>
| Semimegabeasts do not count towards the BEAST_END_YEAR calculation.
|}

=== Titan Parameters ===

==== Number ====

This controls the number of [[titan]]s that exist at the beginning of history[http://www.bay12forums.com/smf/index.php?topic=112465.msg3415203#msg3415203 data]. The number of forgotten beasts is unaffected by this parameter [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415155#msg3415155 data].

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TITAN_NUMBER:33]</nowiki></tt>
| Titans count towards BEAST_END_YEAR calculation.
|}

==== Attack Population Requirement ====

[[Titan]]s will begin to attack your fort once at least this many dwarves inhabit it, regardless of whether any other attack criteria have been met.

This number defaults to 80, which isn't usually too difficult to deal with.

==== Exported Wealth Requirement ====

Titans will begin to attack your fort once you have exported at least this many [[Currency|dwarfbucks]]-worth of goods, regardless of whether or not any other criteria have been met. This parameter defaults to None (disabled).

==== Created Wealth Requirement ====

Titans will begin to attack your fort once the fort's total wealth has reached this many [[Currency|dwarfbucks]] in value. This happens regardless of whether any of the other criteria, such as population, have been met; therefore, even with 1 dwarf, a fort could be attacked if the fort were worth at least this value.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_ATTACK_TRIGGER:<population>:<exp wealth>:<created wealth>]</nowiki></tt>
| <tt><nowiki>[TITAN_ATTACK_TRIGGER:80:0:100000]</nowiki></tt>
| 0 = None (disabled). Only one requirement must be met for an attack.
|}

=== Number of Demon Types ===

[[Demon]]s are similar to [[titan]]s and [[forgotten beast]]s, in that they are procedurally generated, but most are not unique. Thus, many different types of demons can exist in the world, but there will also be many individuals of most types. Thanks to [[Underworld spire|certain fun things]], fewer demon types also means fewer goblin civilizations.{{cite forum|112465/7392706}} You need at least 2 demon types, or else goblin civilizations won't exist initially, though if dwarves breach the underworld during world generation, at least one will be generated then.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DEMON_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[DEMON_NUMBER:52]</nowiki></tt>
| 0 to 1000
|}

=== Number of Night Troll Types ===

The number of different [[night troll]]s, also procedurally generated, that will exist in the world. Setting this to zero means that the world will have no night trolls, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[NIGHT_TROLL_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[NIGHT_TROLL_NUMBER:77]</nowiki></tt>
| 0 to 1000
|}

=== Number of Bogeyman Types ===
The number of different [[bogeyman]] forms that will exist in the world. Bogeymen are procedurally generated, though their forms do not vary by much. Setting this to zero means that the world will have no bogeymen, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[BOGEYMAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[BOGEYMAN_NUMBER:27]</nowiki></tt>
| 0 to 1000
|}

=== Number of Nightmare Types ===
The number of different [[nightmare]] forms that will exist in the world. Nightmares are procedurally generated. Setting this to zero means that the world will have no nightmares, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[NIGHTMARE_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[NIGHTMARE_NUMBER:27]</nowiki></tt>
| 0 to 1000
|}

=== Number of Vampire Curse Types ===

The number of different types of [[Vampire|vampires]] that will exist in the world. Although they are generated at the start of a new world, they aren't different from each other. Setting this to zero means no vampires will exist.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[VAMPIRE_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[VAMPIRE_NUMBER:72]</nowiki></tt>
| 0 to 1000
|}

=== Werebeast Parameters ===

==== Number of Werebeast Curse Types====

The number of different types of [[werebeast]]s that can exist in the world. It is common for werebeasts, unlike vampires, to assume many different forms and variations, the most well-known of these amount to different species of animals, from lizards, to wolves, to even bears. Setting this to zero means no werebeasts will exist, and will also remove a large amount of [[fun]] from the game.

In vanilla, there are only 82 possible unique werebeast species. Any further species will generate as wereblobs.{{bug|13308}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[WEREBEAST_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[WEREBEAST_NUMBER:58]</nowiki></tt>
| 0 to 1000
|}

==== Attack Population Requirement ====

Werebeasts will begin to attack your fort once at least this many dwarves inhabit it, regardless of whether any other attack criteria have been met. This number defaults to 50 which will often be reached in the second year of the fort.

==== Exported Wealth Requirement ====
Werebeasts will begin to attack your fort once you have exported at least this many [[Currency|dwarfbucks]]-worth of goods, regardless of whether or not any other criteria have been met. This parameter defaults to 5000.

==== Created Wealth Requirement ====

Werebeasts will begin to attack your fort once the fort's total wealth has reached this many [[Currency|dwarfbucks]] in value. This happens regardless of whether any of the other criteria, such as population, have been met; therefore, even with 1 dwarf, a fort could be attacked if the fort were worth at least this value.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[WEREBEAST_ATTACK_TRIGGER:<population>:<exp wealth>:<created wealth>]</nowiki></tt>
| <tt><nowiki>[WEREBEAST_ATTACK_TRIGGER:50:5000:50000]</nowiki></tt>
| 0 = None (disabled). Only one requirement must be met for an attack.
|}

=== Number of Secret Types ===

The number of secrets that exist in the world. Currently, all secrets are secrets of life and death, and the ones holding these secrets are [[necromancer]]s, thus, setting this to zero means that no necromancers will appear.
Non-necromancer towers can still appear (extremely rarely) with zero secrets, constructed by independent undead groups.
The primary difference between having 1 or 1000 secrets is the chance of your world having any necromancer towers at all. With 1, this chance is low. With the default number, it's seemingly guaranteed.
Even with 1 secret, if you have any necromancer towers at all, it is likely a great number will quickly appear in world generation (though this isn't guaranteed).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SECRET_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[SECRET_NUMBER:52]</nowiki></tt>
| 0 to 1000
|}

=== Number of Regional Interaction Types ===

The number of interactions that can be caused in regions, which may incorporate evil rain and cloud types. Currently, only evil region interactions are generated this way.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[REGIONAL_INTERACTION_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[REGIONAL_INTERACTION_NUMBER:20]</nowiki></tt>
| 0 to 1000
|}

=== Number of Disturbance Interaction Types ===
The number of different [[Mummy|disturbed dead]] that can exist in the world. Setting this to zero should prevent any mummy from appearing{{verify}}, but it will not prevent the creation of [[tomb]]s.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DISTURBANCE_INTERACTION_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[DISTURBANCE_INTERACTION_NUMBER:10]</nowiki></tt>
| 0 to 1000
|}

=== Number of Evil Cloud / Evil Rain Types ===

This number specifies how many [[Weather#Evil weather|various face-melting, eye-boiling, and zombifyingly-fun]] clouds of pure evil may appear in your world. Setting this to zero means you no longer will ever have to deal with encroaching dust walls of doom in that world. It is generally advised to keep this value low...

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EVIL_CLOUD_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[EVIL_CLOUD_NUMBER:45]</nowiki></tt>
| 0 to 1000
|}

The latter number states how many different types of green-ooze drenchers, disconcerting blood-showers, and sickly yellow slime-baths can occur in your world. Compared to evil clouds though, this one hardly is worth stressing out about, usually.... Setting this to zero means the only semi-solid to fully-liquid fluids to fall from the sky will be pure H2O.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EVIL_RAIN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[EVIL_RAIN_NUMBER:352]</nowiki></tt>
| 0 to 1000
|}

=== Generate Divine Materials ===
This turns the generation of [[Divine_metal|divine metals]] on or off. It does not influence the creation of [[vault]]s. Probably determines whenever or not using divination dice spawns weapons.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GENERATE_DIVINE_MATERIALS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[GENERATE_DIVINE_MATERIALS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Generate Mythical Materials ===

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GENERATE_MYTHICAL_MATERIALS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[GENERATE_MYTHICAL_MATERIALS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Mythical Healing ===

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALLOW_MYTHICAL_HEALING:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_MYTHICAL_HEALING:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Divination, Experiments, and Necromancy types ===
These allow or disallow [[die|divination]], demon or necromancer [[experiment]]s, and the more advanced [[necromancer]] abilities.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALLOW_DIVINATION:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_DIVINATION:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_DEMONIC_EXPERIMENTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_DEMONIC_EXPERIMENTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_EXPERIMENTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_EXPERIMENTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_LIEUTENANTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_LIEUTENANTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_GHOULS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_GHOULS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_SUMMONS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_SUMMONS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Desired Good/Evil Square Counts ===

These values change the amount of [[Surroundings#Good|good or evil]] tiles on the map, depending on the size of the region they are being considered for. The counts are for all tiles in all subregions of a given size considered together, ''not'' counts for each subregion considered separately (all tiles in the same subregion share the same [[surroundings]] values).

As used here, a "subregion" is a named world area. Subregion names and locations for a generated world are viewable in legends mode under "Regions". Subregions are classified by size the same way for all map sizes: 1-24 tiles is Small, 25-99 tiles is Medium, and 100+ tiles is Large.

The counts used here will always be restricted to regions of the given size, no matter how large the count. Also, the count is more of a goal than a minimum or maximum. As a result, you can end up with many more or many fewer than the requested number of squares in some situations. In particular, if you have something like a case where only 3 large regions exist in a world, and you request "1 evil square" in large regions, you will end up with one of the large regions being ''entirely evil''. So any non-zero value in one of these settings essentially means "force at least one region of this size to be all good/evil."

Note that the "evilness" of evil biomes is also impacted by savagery. Certain civilizations cannot exist in good and/or evil squares, so too many of one or the other may limit the size of certain types of civilizations - dwarves, for example, need non-aligned biomes. Creating too many evil biomes seems to lead to the danger of many civilizations' early extinction.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GOOD_SQ_COUNTS::<med region>:<lg region>]</nowiki></tt>
| <tt><nowiki>[GOOD_SQ_COUNTS:100:1000:2000]</nowiki></tt>
| rowspan="2" | Set count to zero to disable for that region size.
|-
| <tt><nowiki>[EVIL_SQ_COUNTS::<med region>:<lg region>]</nowiki></tt>
| <tt><nowiki>[EVIL_SQ_COUNTS:100:1000:2000]</nowiki></tt>
|}

=== Minimum Biome Square Counts ===

These numbers control whether or not a world will be rejected based on a lack of different [[biome|biomes]]. Raising these numbers will '''not''' automatically generate the given number of squares of the given biome! For a biome to exist, certain conditions like elevation and rainfall must exist.

These parameters simply filter out worlds that (for example) randomly fail to have enough high elevation squares to support a given number of mountains, etc. Some settings may cause worlds to always be rejected. For example, if for some reason the maximum elevation parameter is set to a value below what will support mountain biomes, it will be impossible to satisfy a non-zero requirement for mountain squares. The same principle goes for other conditions and biomes such as low elevations and oceans, etc.

Certain civilizations require different biomes to exist (such as dwarves and mountains), so eliminating certain biomes will make it impossible for certain civilizations to form.

These parameters often result in infinite world rejection problems. See [[World rejection]] for information on solving problems related to worlds always being rejected due to one or more of these parameters.

0 means no minimum for rejection - setting it to 0 does not guarantee 0 squares of that biome.

==== Biome Type Requirement Table ====

Terrain requirements for various biomes are described below.{{Verify}} Note that some of the exact ranges are unknown.

{| {{prettytable}}
|- bgcolor="#dddddd"
! rowspan="2" | Biome
! colspan="4" | Terrain Requirement
|-
! Elevation
! Rainfall
! Temperature
! Drainage
|-
| Swamp/Marsh
| 100-299
| 33-100
| Non-Freezing
| 0-32
|-
| Desert/Badland
| 100-299
| 0-9
| non-freezing
| note1
|-
| Forest
| 100-299
| 66-100
| non-freezing
| 66-100
|-
| Mountains
| 300-400
| N/A
| N/A
| N/A
|-
| Ocean
| 0-99
| N/A
| N/A
| N/A
|-
| Glacier
| 100-299
| N/A
| Freezing
| 80(?)-100
|-
| Tundra
| 100-299
| N/A
| Freezing
| 0-66
|-
| Grassland
| 100-299
| 0-66
| Non-Freezing
| 0-66
|-
| Hills
| 100-299
| 0-66
| Non-Freezing
| 66-100
|}
note1 drainage: 00-32 sand desert, 33-49 rocky wasteland, 50-65 rocky wasteland but different characters/appearance, 66-100 badlands

==== Minimum Initial Square Count ====

'''Note: The exclusive purpose of these parameters is to cause world rejection.'''

This is the minimum number of squares of the given biome that must exist before things like erosion take place. One thing to keep in mind is the maximum number of squares on a map of a given size - if the total number of squares on a map is lower than the sum of all square count parameters, then you will get infinite world rejection.

To determine the number of squares on a map, just multiply the dimensions. In practice these parameters will need to sum to lower than the maximum because some space is needed for "slack".

{| {{prettytable}}
|- bgcolor="#dddddd"
! Map Size
! Number of Squares
|-
| 17×17
| 289
|-
| 33×33
| 1089
|-
| 65×65
| 4225
|-
| 129×129
| 16614
|-
| 257×257
| 66049
|}

==== Minimum Initial Region Count ====

This is the minimum number of regions of contiguous biome squares that must exist before other processes such as erosion take place.

==== Minimum Final Region Count ====

This many regions of the given biome must exist after erosion and similar phases of generation have been completed.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[REGION_COUNTS:SWAMP:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:SWAMP:1032:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:DESERT:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:DESERT:1032:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:FOREST:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:FOREST:4128:13:12]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:MOUNTAINS:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:MOUNTAINS:8256:9:9]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:OCEAN:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:OCEAN:8256:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:GLACIER:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:GLACIER:0:0:0]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:TUNDRA:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:TUNDRA:0:0:0]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:GRASSLAND:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:GRASSLAND:8256:13:12]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:HILLS:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:HILLS:8256:13:12]</nowiki></tt>
|}

=== Erosion Cycle Count ===

Tells the world generator how long the world has to erode its tall peaks down to mountainsides during the 'running rivers...' stage of world creation. The higher this number, the less jagged the world will be, and the more wide the major rivers will be. If you use the maximum number, your mountains will dissolve before your eyes into plains which can lead to rejections if there aren't enough mountains to use for river start points and dwarven civilization origin points.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EROSION_CYCLE_COUNT:<number>]</nowiki></tt>
| <tt><nowiki>[EROSION_CYCLE_COUNT:250]</nowiki></tt>
| Range: 0 to 1000
|}

=== Minimum/Desired River Start Locations ===

This is the minimum number of riverheads that must exist before and after erosion takes place. Worlds will be rejected if they fail to meet these numbers. As with minimum biome counts, raising this number doesn't automatically create this many riverheads. Other conditions like terrain and rainfall must exist for rivers to form.

Extremely high pre-erosion values speed erosion greatly, while low post erosion values are useful for limiting rejects due to lack of river origin points. One can try the 800 value to get more lakes.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[RIVER_MINS:<min pre-erosion>:<des post-erosion>]</nowiki></tt>
| <tt><nowiki>[RIVER_MINS:200:400]</nowiki></tt>
| Range: 0 to 800
|}

=== Periodically Erode Extreme Cliffs ===

If enabled, makes every impassable rock wall into a series of ramps. Some prefer to pump up erosion to about 250, and turn the "Desired pre-erosion river count" to 0 for good erosion and no extra canyons.

Normally this is set to Yes (1).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PERIODICALLY_ERODE_EXTREMES:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[PERIODICALLY_ERODE_EXTREMES:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Do Orographic Precipitation and Rain Shadows ===

Toggle that allows terrain height to affect rainfall. For example, moist air coming from the ocean blows over the land. As the terrain gets higher, it forces the moist air up, causing it to rain on the seaward side of a mountain. Eventually, all the rain has fallen if the mountain is tall enough. So, when the breeze goes over the top, there's no moisture left to fall on the other side, creating a rain-shadow. In the current version, regions where drainage is above 50 will also create rain shadows, regardless of the underlying biome and elevation.{{cite forum|140685/5484064}}

Turning this on should create a tendency for more extreme rainfall in regions, creating more forests, deserts, marshlands, and grasslands. Also note that it can create rainfall outside of min-max rainfall settings, so even in a world with a 0 max rainfall you may get rainfall biomes. Turning it off should result in more controllable, less complex rainfall conditions based on rainfall parameters as it adds a random element which can distort or otherwise mess up the climates on a pregenerated map.

This should be disabled if you're importing a map or using a preset map file that has weather.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[OROGRAPHIC_PRECIPITATION:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[OROGRAPHIC_PRECIPITATION:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Maximum Number of Subregions ===

This is the number of separate biomes (the flashing regions you see on embark when you hit F1, F2, etc. when there's more than one biome on the embark location) that are allowed to exist on the entire map.

Setting this to very low values will result in numerous rejections depending on [[#X and Y Variance|variance parameters]]. If variance values are set to high numbers, many small biomes will be created causing rejection if this parameter value is not increased beyond the default.

Increasing the value of this tag is often a must when generating "patchwork" worlds with lots of biome variance, but simply increasing it without increasing variance parameters will not guarantee more biomes.

It is also interesting to note that the maximum subregions is 5000 which is more than the total number of squares for a pocket or small map. However, for a medium or large map (16641 or 66049 squares) it quickly becomes a mere fraction of the total number of possible subregions. In fact it would be quite easy on a large map to end up with far too many subregions and get endless rejections of this type.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SUBREGION_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[SUBREGION_MAX:2750]</nowiki></tt>
| Range: 1 to 5000
|}

=== Cavern Parameters ===
[[Caverns]] are the hollow areas underground, which dwarves tend to encounter when they're digging around. The '''Cavern Layer Number''' parameter determines how many cavern systems will be generated, not including the magma layer or the Bottom layer. Defaults to three - setting it to lower values could help FPS. Setting it to 2 will merge cavern 3 species into the 2nd cavern, and setting it to 1 will merge all into one cavern. However, disabling them entirely by setting it to 0 will make it impossible to grow any underground plants, as none will exist for your civilization to cultivate, nor will they be available on embark.

*Setting caverns to a sub-3 number (Spoiler, highlight to view) erases about one-third of HFS spires{{Bug|10267}} and prevents dig deep disasters. Additionally, random plant or animal species can be more frequently absent.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_COUNT:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_COUNT:3]</nowiki></tt>
| Range: 0 to 3
|}

==== Cavern Layout Parameters ====

Open caverns and dense passageways are not mutually exclusive. When both are raised, bizarre results can occur, such as layers showing a combination of open caverns, a cluster of network passages, and natural walls sprinkling the inside of an otherwise open cavern. [http://www.bay12forums.com/smf/index.php?topic=76355.msg1936859#msg1936859 Reference]

If you want the largest open spaces possible, then decrease the density and increase the openness. If you want a labyrinth of passageways, lower the openness and raise the passage density.

Another interesting note about the cavern layers is that the seed and number of demon types affect the layout of the caverns.

<gallery widths=200 heights=200 perrow=2>
File:Open00Density100.jpg|Cavern slice with Openness of 0 and Density of 100
File:Open100Density00.jpg|Cavern slice with Openness of 100 and Density of 0
File:Open100Density100.jpg|Cavern slice with Openness of 100 and Density of 100
File:Open50Density50.jpg|Cavern slice with Openness of 50 and Density of 50
</gallery>

===== Layer Openness min/max =====

Dictates the size of cavern passages. When Passage Density (see below) is set to minimum (0), caverns will be open expanses. Raising the maximum will increase the size of the caverns.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MAX:100]</nowiki></tt>
|}

===== Layer Passage Density min/max =====

Determines how many passages form the cavern. If openness (see above) is set to minimum and density increased, then you will get a maze-like network of small criss-crossing passages. Raising the values further increases the number of the maze-like passages.

Caverns will be large, open spaces at 0, and comprised of many small vertical shafts of rock at 100. Setting both values to be the same results in a uniform look for the caverns.{{Verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MAX:100]</nowiki></tt>
|}

===== Layer Water min/max =====

Determines the minimum and maximum percentage of water each cavern can contain.

Caverns with a water level of 10 or higher can support creatures and plants from the "Subterranean Water" biome, and caverns with a water level of 90 or lower can support the "Subterranean Chasm" biome; levels of 10-90 support ''both'' biomes, while levels below 10 or above 90 support only one.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_WATER_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_WATER_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_WATER_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_WATER_MAX:100]</nowiki></tt>
|}

==== Magma Layer ====

This parameter controls whether the [[magma sea]] exists.

Setting 1/Yes causes the magma layer to exist, value 0/No prevents it. Appears not to have any impact on volcanoes nor volcanism, so even if 0/No, there will still be embark locations with magma. If a [[volcano]] exists, it appears to always tap the magma sea, but the magma sea will not be revealed by revealing the volcano.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[HAVE_BOTTOM_LAYER_1:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[HAVE_BOTTOM_LAYER_1:1]</nowiki></tt>
|}

==== Bottom Layer ====

Determines if the space below the magma sea exists. If Yes the "HFS" layer is always present. Normally you want to leave this set to Yes for maximum fun.

If enabled, this will force the magma layer above it.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[HAVE_BOTTOM_LAYER_2:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[HAVE_BOTTOM_LAYER_2:1]</nowiki></tt>
|}

=== Z Levels (Depth) Settings ===

These parameters control the "thickness" of various "layers" on the map. Note that a "layer" in this case does not refer to one Z-level, but refers to a number of related Z-levels such as "levels above ground".

The following table assumes that you have 3 cavern layers. (out of a minimum of 0-3) The Levels Above Layer settings control how many Z-Levels are above each layer. A layer may itself consist of multiple Z-Levels (and almost always does).

{|style="margin:1em 1em 1em 0;background:#F9F9F9;border:1px #AAA solid;border-collapse:collapse;" class="wikitable"
|-style="background:#F2F2F2;text-align:center;"
!style="border:1px #AAA solid;padding:0.2em;" width="120"|Setting Name
!style="border:1px #AAA solid;padding:0.2em;" width="200"|Token
!style="border:1px #AAA solid;padding:0.2em;"| Description
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Ground
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_GROUND:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| The number of Z-levels of air above the highest surface level. Has no impact on how many Z-levels deep the surface layer is.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above layer 1
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_1:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of stone above the first cavern layer. Making this higher will guarantee ''at least'' that many levels to build your fortress, but will have no impact on how many z-levels thick the surface layer is. Also, the top of a cavern may be higher than the rest of a cavern, so in practice there will be more "solid" levels than this above the cavern.
As of version 0.31.25 this setting is inaccurate. The actual number of z-levels may vary in a range of approx. ±5, which may result in non-existence of any solid z-levels between a surface layer and first cavern layer.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 2
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_2:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very top of the second cavern and the very bottom of the first cavern.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 3
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_3:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very top of the third cavern and the very bottom of the second cavern.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 4
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_4:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very highest magma and the very bottom of the third cavern. Spoiler Hidden (select invisible text to read): Making this high will give a large area for HFS veins, so that it never touches caverns, giving more to mine '''if''' it was impacting the cavern previously.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 5
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_5:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Uncertain. May control the number of levels of "Semi Molten Rock" between HFS and Magma, may control number of levels of magma, may impact both. In experimentation, the overall depth of all magma sea and semi-molten rock levels appears to increase, but not consistent enough to say for certain. Only valid if Magma Layer present. Spoiler Hidden:Often the HFS vein will only extend as high as the highest magma, making this the only guaranteed way to increase amount of HFS to mine, but unfortunately also creating enormous useless semi-molten z-levels
|-
|style="border:1px #AAA solid;padding:0.2em;"| At Bottom
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_AT_BOTTOM:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Appears to be number of levels of HFS chamber. Only valid if Bottom Layer present, often having no impact. Values larger than default result in strange things.
|}

Some implications:
* The number of surface layers (e.g. soil), at this time, cannot be controlled. For example, on a map with 1 layer of peat, then a layer of silt, then a layer of obsidian, there is no control to let you increase either one to be, say, 20 z-levels. (though you may get lucky with the obsidian).
* There can be multiple stone layers between the cavern and the surface, so, increasing Levels Above Layer 1 may give you more conglomerate or more granite, and you have no control over which stone layer spans those Z-levels.
* The layers shown on embark span across the cavern layers in an unknown and inconsistent way. Sometimes those 10 different layers of stone are evenly distributed over your 400 z-level deep map, sometimes the first 9 get 1 z-level each and the last gets the other 391 levels. No way to control found yet.
* The HFS chamber, if present, will always extend into the rock layers, and appears to always make contact with the bottom cave. Large values for levels above layer 5 and layer 4 can result in enormous chambers, but the number of levels at the top (the part with undead) appears to be unaffected.
* Unconfirmed whether number of levels between caverns has any impact on cavern height. There will be connecting ramps and/or shafts between cavern layers no matter how many levels are between them.
* '''Very Important''': These values appear to apply across a whole 16x16 region, not just embark areas. That means that if a 16x16 region is completely flat, but has one tall mountain in one far corner, even if you set Levels Above Ground low (e.g. 2 z-levels) you still have all the empty air of the highest mountain in every embark tile (e.g. 200 z-levels). Also can happen to the semi-molten layer, and can lead to unexpected behavior.
* Very large or small values can cause strange things to happen.

=== Minimum/Maximum Natural Cave Size ===
It's not clear what effect these currently have, other than changing them can change the location of caves somewhat.{{verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVE_MIN_SIZE:<number>]</nowiki></tt>
| <tt><nowiki>[CAVE_MIN_SIZE:5]</nowiki></tt>
| rowspan="2" | Range: 1 to 500
|-
| <tt><nowiki>[CAVE_MAX_SIZE:<number>]</nowiki></tt>
| <tt><nowiki>[CAVE_MAX_SIZE:25]</nowiki></tt>
|}

=== Number of Caves ===
The number of caves generated in mountainous and non-mountainous regions, mountain caves will always be generated on the edge of mountain ranges next to non-mountainous regions. Lurking [[kobold]]s set up shop in caves, and store their stolen items there - a setting of 0 in both will stop kobold civilizations from appearing. Special note: a cave is not initially a [[lair]], although beasts can later use them as their lair.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[MOUNTAIN_CAVE_MIN:100]</nowiki></tt>
| rowspan="2" | Range: 0 to 800
|-
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:200]</nowiki></tt>
|}

=== Number of Mythical Sites ===
The number of [[mysterious dungeon|mysterious sites]] generated around the world. The extended effects of setting this to 0 has not been determined{{verify|is chosen still available? is quest still given? etc.}}.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MYTHICAL_SITE_NUM:<number>]</nowiki></tt>
| <tt><nowiki>[MYTHICAL_SITE_NUM:200]</nowiki></tt>
| rowspan="2" | Range: 0 to 800
|}

=== Make Caves Visible ===
If set to no (default) then the location of caves will not be marked on the map. If set to yes, caves will appear on the map so that they may be sought out or avoided as desired.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALL_CAVES_VISIBLE:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALL_CAVES_VISIBLE:0]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Init Options to Show Tunnels ===

If enabled, you will be able to see the underground tunnels often built by dwarves on the world map, and they will appear as black lines, similar to roads.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SHOW_EMBARK_TUNNEL:<0-2>]</nowiki></tt>
| <tt><nowiki>[SHOW_EMBARK_TUNNEL:2]</nowiki></tt>
| 0 = No 1 = Only in Finder 2 = Always
|}

=== Number of Civilizations ===

This number of [[civilization]]s will be placed on the map before history generation begins. These civilizations may later die out due to historical events. It is noteworthy that the chance for any given civilization to be destroyed through megabeasts decreases with a higher total number of civilizations present[http://www.bay12forums.com/smf/index.php?PHPSESSID=7348f68f41a9659443c05b2acf534e6c&topic=112465.15 data]. The five races are dwarf, elf, human, goblin, and kobold; they will generally be placed in equal numbers until the quota has been reached. If there are not enough biomes or other worldgen prerequisites for an even distribution, certain civs will be much more or less frequent than others[http://www.bay12forums.com/smf/index.php?PHPSESSID=7348f68f41a9659443c05b2acf534e6c&topic=112465.15 data]. If there is an odd number of civs (not divisible by 5), then the remainder is distributed randomly. Kobold civs require caves to be placed; if no caves exist, then kobolds are skipped and will not appear. This does not cause rejections [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415125#msg3415125 data]. Goblin civilizations require multiple demons, see the [[#Number_of_Demon_Types|number of demon types]] section above.

Note that a high value here can cause lots of map rejections, particularly on smaller maps as there simply isn't enough room or regions to put them all in.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_NUMBER:40]</nowiki></tt>
| Range: 0 to 300
|}

=== Playable Civilization Required ===

If this is set to yes (default) then worlds will be rejected if no civilization with [[Entity token|CIV_CONTROLLABLE]] can be placed. In an unmodded game, only the dwarves have this token.

If set to no, the result may be a world that cannot be played in Fortress Mode.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PLAYABLE_CIVILIZATION_REQUIRED:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[PLAYABLE_CIVILIZATION_REQUIRED:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Minimum Number of Mid/Low/High Characteristic Squares ===

Sets the minimum possible number of squares of certain ranges of each of the region qualities, such as elevation, rain, drainage, volcanism, savagery, and temperature. These need to be changed to reflect your regional meshes and weights, and are responsible for a HUGE number of map rejections. These values can all be set to 0 for much fewer map rejections, particularly in the case of more wacky, non-standard maps.

These values will cause worlds to be rejected unless at least the given number of squares of the given type are randomly generated. Setting these values too high could result in worlds always being rejected if other parameters such as the maximum/minimums for elevation, etc., don't allow enough of those squares to get generated.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[ELEVATION_RANGES:8256:16512:8256]</nowiki></tt>
| rowspan="5" | Minimum number of squares that must have low, medium, and high amounts of the given attribute. 
0 = No minimum
|-
| <tt><nowiki>[RAIN_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[RAIN_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[DRAINAGE_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[SAVAGERY_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[VOLCANISM_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM_RANGES:8256:16512:8256]</nowiki></tt>
|}

==World rejection==

:''Main article: [[World rejection]]''

If you are having the common problem of generated worlds always being rejected by the world generator, see [[v0.31:World rejection|Solving World Rejection Problems (v0.31 page)]] as it contains many detailed suggestions on how to troubleshoot and solve these issues.

== Parameter set examples ==

If you're trying to do something specific, then the [[Worldgen examples]] - complete parameter sets that can be copied directly into your ''world_gen.txt'' file and customized as desired - might be helpful.
If none of the examples suit your needs, [[Worldgen tricks]] has strategies and tips on making a world just right for you.

For many, many more examples see:
* [http://www.bay12forums.com/smf/index.php?topic=101280 DF2012 (v0.34) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=140180 DF2014 (v0.40) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=168543.0 DF2014 (v0.44.02+) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=175538 DF2014 (v0.47.01+) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=180805.0 DF2022 (v0.50.01+) WorldGen "Cookbook" Thread]

{{World}}

Advanced world generation

2026-04-10T03:08:01Z

Ziusudra: /* Interaction between Mesh Size and Weighted Ranges */ added non-square example

{{migrated article}}
{{Quality|Superior}}
{{av}}
:''This article contains information on advanced world generation. For information on basic world generation, see [[World generation]].'' ''See [[World token]] to more easily find information by the names used in the world_gen.txt file, [[World rejection]] for information on solving problems related to worlds always being rejected, and [[Worldgen examples]] for example worlds.''

[[File:adv_worldgen_v50.png|thumb|400px|right|The advanced world generation screen. ''(Click to enlarge)'']]'''Advanced world generation''', also labeled as '''detailed mode''', allows substantially more detail-oriented options of customization than standard, basic world generation. This gives the player much more control over how their world is generated. To better understand this article, it is advised that one should read about [[World generation|'''basic world generation''']] first.

The advanced world generation screen is reached by clicking "Create new world" at the main menu, then clicking "Detailed mode". Once at that screen, clicking "Basic options" will return the user to the standard world generation screen.

== Parameter sets ==
There are multiple default sets of all the advanced world generation parameters hard-coded in ''Dwarf Fortress'', which will be overridden by the <tt>prefs/world_gen.txt</tt> file in the main ''Dwarf Fortress'' directory, if it exists. It does not exist by default, you must create it, either by saving the default sets, or saving a copy from the [[world_gen.txt]] wiki page or elsewhere. This file can then be edited with a text editor, and you can copy and paste other players' sets of parameters into it. For sources of such parameter sets see [[Advanced_world_generation#Parameter_set_examples|Parameter set examples]] below.

To get back the default sets, move the existing <tt>prefs/world_gen.txt</tt> to somewhere else (like Documents), or delete it if you do not want to keep the changes, then load the sets in the game, it will then use the hardcoded defaults.

== User interface ==
First, there is a line of text inputs and buttons along the top of the screen, from left to right:
* The drop down menu of currently defined parameter sets, click the down arrow to select a set that you want to work with. The currently selected set can be renamed by clicking the current name or the [[File:Quill.png]] button. The first set in the file is selected by default, usually "LARGE ISLAND". See [[#Parameter set title|Parameter set title]].
* The dimensions of the world for the selected set, see [[#World dimensions|World dimensions]].
* A text entry box to set all of the seed options to the same seed, will show "Random seed", "Various seeds", or, if all four seeds are set to use the same value, that value. See [[Advanced_world_generation#Seed_values|Seed values]] and [[Advanced_world_generation#Seed_values|Seed notes]].
* The Copy Button to make a copy of the currently selected set and appends it to the bottom of the list.
* The red Delete button to delete the currently selected set, you will be prompted to confirm the deletion.
* The New parameter set to create a new parameter set and appends it to the bottom of the list. This seems to just copy the default "LARGE REGION" set.
* The Save button to save all of the current sets to the <tt>prefs/world_gen.txt</tt> file.
* The Load button to load from the same file, there is no confirmation, '''any unsaved changes will be lost'''. If that file does not exist, this resets all of the sets to the defaults.

Most of the middle is the parameters themselves, with a scroll bar to the right. Each row of the list can include:
* The name of the option
* The range of accepted values; not every option has this, and does not always match the displayed value, for example "0 to 1" might show as "No" and "Yes".
:* Sometimes the range might not initially show on rows that it should, reloading the sets with the Load button sometimes fixes that.{{bug|13176}}
* A plus button to increase the value or cycle through options, when applicable (this button will be missing if the range is missing.)
* The current value; can be clicked to edit, to actually set a value you must press {{k|enter}}, without doing that, clicking another entry box or right clicking will instead reset to the currently set value.
* An edit button to show that the previous box is editable, same as clicking on the text box.
* A minus button to decrease the value or cycle through options, when applicable (this button will be missing if the range is missing).
* A red button to disable this parameter, when applicable, usually setting the value to 0, or -1.

{{notice bar|bgcolor=#faa|bordercolor=#f00|All of the buttons below leave this screen and do not prompt to save the sets, so unsaved changes may be lost.}}
At the bottom right are 3 or 4 more buttons:
* The Create world button to do just that using the currently selected set, '''unsaved changes are lost'''.
* The Basic options button to go back to the normal world generation screen, unsaved changes are not lost if you come directly back to Detailed mode.
* The [[Mods]] button to go to the mod selection screen, unsaved changes are not lost if you come directly back to Detailed mode. Only shown if mods are available.
* Back to main menu button to do just that, '''unsaved changes are lost'''.

=== World painter ===
:''Main article: [[World painter]]
The '''world painter''' tool is not in the current version of ''Dwarf Fortress''; it allowed you to paint features onto a map. '''However''', those maps can still be used when generating a world by pasting world painter parameter set maps created in old versions into the <tt>prefs/world_gen.txt</tt> file. [[Utilities#Perfect_World_DF|Perfect World DF]] is a utility that uses the same parameter functionality as the world painter to paint a map, and it also can work with the current version of ''Dwarf Fortress''.

== Generating a world ==
You can either use an already-defined parameter set, or you can edit them, though it is highly suggested to edit a copy of one of the defaults. Once you are happy with the parameters you should save the values you just edited before you click the Create world button. Information about each parameter is documented below.

The phases of the world generation process are (this order is not completely correct):
* Preparing elevation...
* Setting temperature...
* Running rivers...
* Forming lakes and minerals...
* Growing vegetation...
* Verifying terrain...
* Importing wildlife...
* Recounting legends...
* Placing civilizations...
* Making cave civilizations...
* Making cave pops...
* Placing other beasts...
* Placing megabeasts...
* Placing good/evil...
* Placing caves...
* Prehistory generation
* Finalizing civ mats...
* Finalizing art...
* Finalizing uniforms...
* Finalizing sites...

== Seed notes ==
The world generation process uses a PRNG (Pseudo Random Number Generator) algorithm. A PRNG will produce a sequence of numbers that "looks" random, even though the actual sequence of numbers will always be the same if the PRNG is started with the same seed value. Basically this means that if you run world generation with a certain seed value on your computer, and someone else runs world generation with the same seed value on their computer, the same sequence of random numbers will be generated on both computers. The practical impact of this is that someone else can generate exactly the same world that you generated by entering the same seed value that you used.

In the current version, the seed values for the world itself and the names seem to produce the same result, but you will get changes in events which will result in a very different world history.{{bug|6934}} Keep this in mind if you want to regenerate a particular world.

The way that a world is generated can also be affected by certain world tokens. Changing them causes that code to use more or fewer PRNG values, causing later uses to get different parts of the sequence. So, you cannot for example, change the minimum and maximum rainfall and get 'the same world but drier or wetter', instead, a different world is generated. That said, it would also seem that certain small changes to these world tokens can occasionally generate a very similar world, however, other tokens are more sensitive. For more information see the forum thread [http://www.bay12forums.com/smf/index.php?topic=112132.msg3404199#msg3404199 here].

The following are tokens which use the PRNG values in ways that changing them will likely cause broader changes:

* [DIM:X:X]
* [ELEVATION:X:X:X:X]
* [RAINFALL:X:X:X:X]
* [TEMPERATURE:X:X:X:X]
* [DRAINAGE:X:X:X:X]
* [VOLCANISM:X:X:X:X]
* [SAVAGERY:X:X:X:X]
* [ELEVATION_FREQUENCY:X:X:X:X:X:X]
* [RAIN_FREQUENCY:X:X:X:X:X:X]
* [DRAINAGE_FREQUENCY:X:X:X:X:X:X]
* [TEMPERATURE_FREQUENCY:X:X:X:X:X:X]
* [SAVAGERY_FREQUENCY:X:X:X:X:X:X]
* [VOLCANISM_FREQUENCY:X:X:X:X:X:X]
* [PARTIAL_OCEAN_EDGE_MIN:X]
* [COMPLETE_OCEAN_EDGE_MIN:X]
* [HAVE_BOTTOM_LAYER_1:X]
* [MINERAL_SCARCITY:X] {{cite talk/this|Mineral scarcity}}

Many other world parameters, such as end year and embark points, can, however, be changed without it having any effect on the geography of the world generated from the seed values.

Normally, you don't enter these seed values, the game comes up with values based on some other sort of pseudo-random information from things like the current date and time.

When generating a world, ''Dwarf Fortress'' records the seeds it used in [[gamelog.txt]]; they can also be found with <code>gui/gm-editor world.worldgen.worldgen_parms</code> in [[DFHack]].

== Advanced parameters ==
There are essentially 4 types of controls for the generation of the surface map;

'''Terrain parameters''': as described below, these 5 variables define the basic background world, how hot or cold it is, how much rainfall, how high the mountains are. The world automatically goes through the temperature range along the Y axis, although sometimes it will be hotter in the north, other times in the south, or cold at both. Minimum, maximum and X,Y variance can drastically alter the world.

'''Weighted meshes''': these are a way to fine-tune the amount of the 5 basic variables on the map. They can be used to set the specific distribution of different elevations or rainfall areas for example.

'''Feature parameters''': such as rivers, mountain peaks, volcanoes, and oceans, which can cause rejections if the terrain parameters don't allow enough suitable locations for the features to be placed.

'''Rejection parameters''': ''Dwarf Fortress'' uses a 'belt-and-braces' approach to world generation. The above controls allow you to shape the world, then the rejection parameters throw it out if it does not meet certain criteria. There are a number of rejection parameters for the number and degree of the 5 basic variables, for biome types, etc. If the world does not meet the requirements of any one rejection parameter the world is rejected and re-randomised. Also see [[World rejection]].

Leaving tokens out of a set in <tt>world_gen.txt</tt> will cause the game to use default values which are not adjusted for smaller world sizes, this may cause smaller worlds to always be rejected.

If you are experimenting with world design, there is also a [[Settings#Feature_toggles|game setting]] that will log the rejection reasons to ``[[map_rejection_log.txt]]``. With that information you can then either adjust the rejection parameters to allow those worlds, or the other parameters to prevent them from trying to generate. ''Dwarf Fortress'' will keep adding to the file, so you may want to trim or delete it occasionally.

The parameters are described below in the order that they appear in the list in the game, which is not necessarily the order they appear in <tt>world_gen.txt</tt>. See [[world token]] for an index that will help you look things up by token name. The tokens used in <tt>world_gen.txt</tt> are at the bottom of each of the following parameter descriptions.

=== Parameter set title ===
This sets the name of the parameter set itself, as used in the list of sets (this has nothing to do with the name of the generated world).
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITLE:<name>]</nowiki></tt>
| <tt><nowiki>[TITLE:MEDIUM ISLAND]</nowiki></tt>
| Required
|}

=== World dimensions ===
The size of the map for the current set can be changed by changing the Width and Height values at the top next to the set title. You will need to confirm this, since changing the dimensions of the world will change other parameters, because many of them have different defaults depending on the surface area available.

Larger maps usually take longer to generate and may reduce [[Frames per second|FPS]] in-game, though this is really a matter of larger worlds usually having more civilizations, sites, historical figures, and events; restricting the number of those can speed up the process. Non-square maps may result in crashes{{bug|2928}}.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DIM:<width>:<height>]</nowiki></tt>
| <tt><nowiki>[DIM:257:257]</nowiki></tt>
| Valid values are 17, 33, 65, 129, and 257, other values will use one of those. Changing the size in the file without adjusting other parameters can cause many rejections.
|}

=== Seed values ===
Enables the use of, and specifies seed values for, different parts of the world generation process. Just entering a specific seed does not enable it, that must be done separately, although using the box at the top to set all the seeds to the same value does enable them all. Enabling a seed puts the token in using what ever is in the text box below. If you enable a seed, but do not enter a seed, the string "Seed text" will be used (<tt><nowiki>[SEED:Seed text]</nowiki></tt>). Trying to use a <tt><nowiki>]</nowiki></tt> in the string in the file will end the seed there, since it closes the token, any text after that will be ignored. Normally, just leave these set to Random, unless trying to reproduce the results of a previous world generation. See also the [[Advanced_world_generation#Seed_notes|seed notes section]] above.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEED:<text>]</nowiki></tt>
| <tt><nowiki>[SEED:31337]</nowiki></tt>
| rowspan="4" |
For each of these not in the config file, a random seed will be used, and the first seed is not used to generate the others. The seeds used are output to [[gamelog.txt]] when world generation starts.
|-
| <tt><nowiki>[HISTORY_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[HISTORY_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[NAME_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[NAME_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[CREATURE_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[CREATURE_SEED:31337]</nowiki></tt>
|}

=== World name ===
As previously mentioned, the title of the parameter set doesn't affect the name of the world. You can specify a particular name for your world, or leave the value blank for a random one. (The [[DFHack]] utility adds an option to rename the world using the in-game languages.)
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CUSTOM_NAME:<name>]</nowiki></tt>
| <tt><nowiki>[CUSTOM_NAME:Realm of Cheese Engravings]</nowiki></tt>
| For a random name, simply don't use this token.
|}

=== Embark Points ===
The number of points for equipment and animals when embarking in fortress mode (there is no equivalent setting for adventure mode). Normally, the default of 1504 is fine, but can be increased for various purposes like experimentation or to help dwarves survive in a particularly evil world, or reduced for certain [[challenges]].
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EMBARK_POINTS:<number>]</nowiki></tt>
| <tt><nowiki>[EMBARK_POINTS:1504]</nowiki></tt>
| 0 to 10,000
|}

=== End year ===
The maximum number of years generated for the world, although generation can be paused and the world used as is any time after the second year; the same as the [[World_generation#History|History]] parameter in basic world gen, except that you can enter an exact value. A too-short history can limit the materials available to civilizations, and [[Chosen|certain adventure mode features]] are only available after certain site events, while too long a history often leads to civilizations dying.

For more information on the history aspect of the game, see [[Legends]] and [[Calendar#Ages|Ages]].
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[END_YEAR:<number>]</nowiki></tt>
| <tt><nowiki>[END_YEAR:250]</nowiki></tt>
| 2 to 10,000
|}

=== Population cap after civ creation ===
A soft limit to the total number of [[historical figure]]s alive at the same time during generation across all civilizations, only preventing the birth of new historical figures.{{cite forum|140544/5701667}} Each civilization is allotted a percentage of the total by the percentage of sites they control.{{cite forum|159164/7553641}} Civilizations also have non-historical populations, and there is no setting to limit those (in early versions, all civilization members were historical figures, this is also why the name of this setting is misleading). Each [[entity]] also has limits from their raws, see the [[Entity_token#Population|population]] entity tokens, and setting this to unlimited will not remove those.

Huge historical figure populations can slow generation and the game in general.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_POPULATION:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_POPULATION:15000]</nowiki></tt>
| -1 to 100,000, -1 is no limit
|}

=== Site cap after civ creation ===
Total number of [[site]]s that can be directly created by all civilizations combined like [[hillocks]], [[hamlet]]s, [[dark pits]], [[forest retreat]]s, etc. Does not prevent the placement of initial civilization sites, though they will then be counted for the limit. Does not affect creature sites like [[cave]]s or [[lair]]s, group sites like [[castle]]s, [[monastery|monasteries]], [[tower_(necromancy)|tower]]s, [[fort]]s, or [[camp]]s, or unpopulated sites like [[tomb]]s. After this limit is reached, no civilization will be able to place new sites. See the [[Entity_token#Placement|placement]] entity tokens for other ways that civilization site placement can be limited.

Increasing this will slow generation down and reduce the available places for player sites. Since the {{token|MAX_SITE_POP_NUMBER|entity}} entity token limits the historical figure population per site, this site cap can also limit the total historical figure population of all civilizations combined, and some expand faster than others getting more sites before the limit is reached.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SITE_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SITE_CAP:1500]</nowiki></tt>
| -1 to 100,000, -1 is no limit
|}

=== Beast control ===

These parameters don't usually matter too much, but may matter for small numbers of beasts.

==== Percentage of Megabeasts and Titans Dead for Stoppage ====

The world starts out with a certain number of powerful megabeast and titan entities in existence. If a percentage of the megabeast and titan population dies out during history generation, then history generation will stop early. For example, if the elimination value is 80%, and the generated history starts with 200 entities and 160 of those 200 entities are eliminated by historical events before the End Year is reached, history generation will stop immediately.

If you want to end the creation of your world at the beginning of a certain age, choose the following values:
* Age of Legends: ~34%
* Age of Heroes: ~67%
If there are three or fewer titans or megabeasts in your world, the age will be given a special name reflecting the remaining megabeasts/titans, instead.

==== Year to Begin Checking Megabeast Percentage ====

The percentage of dead [[megabeast]]s and [[titan]]s for stoppage will not be checked until this year is reached in history generation. This can be used to ensure that a world reaches a certain year even if all of the megabeasts in the world are slain earlier.

If the number of living [[megabeast]]s and [[titan]]s starts at or drops to less than four, then world generation will always stop if the current year is equal to or greater than the Year to Begin Checking Megabeast Percentage ''regardless'' of how many [[megabeast]]s and [[titan]]s are dead — Percentage of Megabeasts and Titans Dead for Stoppage is ignored. The number of megabeasts and titans at the start of the world is set by the sum of the [[Advanced_world_generation#Max_Megabeasts_Caves|Max Megabeasts Caves]] and [[Advanced_world_generation#Titan_Parameters|Titan Number]] parameters.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[BEAST_END_YEAR:<year>:<percentage or -1>]</nowiki></tt>
| <tt><nowiki>[BEAST_END_YEAR:200:80]</nowiki></tt>
| Use -1 as percentage to disable. Year must still be at least 2.
|}

=== Cull Unimportant Historical Figures ===
{{main|Historical figure}}
Whether to remove unimportant dead historical figures after history generation; a short CPU-intensive step, but saves space which can speed up loading, saving, and running games with large histories. Legends mode will refer to culled creatures as "an unknown creature", and they will not appear in engravings, but likely would not have anyway.

Exactly what is considered important is not clear. A member of an abstract group killing a named creature is not. Creating an artifact is not, even if that artifact had important history. Unculled historical figures can have parentage described as "The identity of" that parent "has been lost to time", so just having children is not, though having living direct relations seems to prevent culling.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CULL_HISTORICAL_FIGURES:<0 or 1>]</nowiki></tt>
| <tt><nowiki>[CULL_HISTORICAL_FIGURES:0]</nowiki></tt>
| 0 = No, 1 = Yes
|}

=== Reveal All Historical Events ===

Setting this to Yes will allow access to most information about the history of the world in [[Legends mode]]. All events will be revealed, but some [[historical figure]]s, [[site]]s, [[region]]s, and [[civilization]]s and other entities may not be, possibly because they are not known to any civilization. If set to No, then you will have to discover historical information in [[adventure mode]] or by instructing dwarves to make engravings.{{Verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[REVEAL_ALL_HISTORY:<0 or 1>]</nowiki></tt>
| <tt><nowiki>[REVEAL_ALL_HISTORY::1]</nowiki></tt>
| 0 = No, 1 = Yes
|}

=== Terrain Parameters ===

These set limits and variance for terrain elevation, rainfall, temperature, drainage, volcanism, and savagery which determines how those values are generated. What biomes exist are then determined by how these factors overlap with each other.

==== Minima and Maxima ====
These are the absolute minimum and maximum values that can ever be generated for a particular map square characteristic. By ''subtly'' tweaking the min and max values, vastly different maps can be made. Changing these can cause the occurrence of certain [[Biome|biomes]] to become impossible, so you may want to use [[#Terrain Mesh Sizes and Weights|Weighted Ranges]] instead.

==== X and Y Variance ====
These control how wildly things like elevation and rainfall can vary between adjacent map squares. For example, if these values are set to the maximum of 3,200 for elevation then you will end up with more very low areas right next to very high areas. The number for X determines the east-west variance and the number for Y determines the north-south variance. By setting only one of these to a high value you can, for example, create horizontal or vertical bands of areas which are more similar to each other.

Generally speaking, raising both of these values will create a more random "patchwork" of many small biomes while setting both x and y values to 0 will cause every square on the map to use a single random value for the given characteristic.

For "patchwork" worlds to avoid being rejected, [[#Maximum Number of Subregions|Maximum Number of Subregions]] will probably need to be increased from the default.

==== Elevation ====
This controls the range of terrain elevations that can occur in the world. Usually, you just want to leave the min/max values alone. Raising the minimum elevation can, for example, make it impossible for oceans to exist. This does '''not''' directly control the number of available Z-levels at a particular site, though high maximum values may contribute to peaks, which can raise the number of above ground Z-levels - in other words, a maximum elevation of 400 and minimum of 1 does not mean you get 400 Z-levels, but it might increase the number of Z-levels somewhat in some regions compared to others. Raising the variance will result in a more bumpy, uneven landscape.

Some biomes/features that are impacted by elevation:
* A high minimum (above 99) means no oceans, as they need elevations below 100.
* A low maximum (below 300) means no mountains, as mountains need elevations above 300.
* Rivers will be placed when the elevation maximum is 104 or higher. Therefore, keeping both values above 100 and below 104 will prevent all water tiles from appearing.
* Mountain peaks can only form at elevations of 400.

==== Rainfall ====
Controls the amount of rainfall in each map square/area. Setting the minimum or maximum too high or low can make the formation of certain biomes impossible. Rainfall causes it to [[rain]] more in a given area, which can have various effects. Also makes more rivers appear on the world map.

Note that if [[#Do Orographic Precipitation and Rain Shadows|orographic precipitation and rain shadows]] is on, then mountains will cause additional variance in rainfall, so (for example) rainfall below the specified minimum can occur in the shadow of a mountain. If you want the minimum and maximum for this parameter to be absolutely respected, you must turn off the orographic precipitation option.

Additionally, with 'Orthographic Precipitation' turned on, orthographic precipitation and rain shadows will only occur in regions with greater than or equal to 50 drainage. [http://www.bay12forums.com/smf/index.php?topic=139916.0 [Report, reproduced 2022]]

==== Temperature ====
{{main|Climate|Temperature}}
These parameters control how hot or cold various areas will be. If you lower the minimum and maximum values, the world will be colder overall, for example. As with the others, changing these values too much could make it impossible for certain biomes to exist. The temperature scale used in this setting is related to regular degrees Urist by the equation "local temp = world temp * 0.75 + 10000".{{cite forum|169696/8395484}} This scale doesn't seem to be used anywhere else in the game. See [[Climate]] for more info.

These parameters form the "base" temperature for an area, and describe peak summer temperature in a scale that isn't used elsewhere in the game. This number also does not correspond 1:1 with the final climate. [[Temperature]] is always influenced by a number of variables, including elevation, time of year, thick forestation, and if [[Advanced_world_generation#Poles|poles]] are enabled, latitude. These other variables are factored in after the temperature mesh is applied, and frequently bring temperatures above and below their set minimum and maximum values. ''The inclusion of Poles is particularly strong in this regard, as it allows latitude to raise and/or lower temperatures by more than 75 degrees Celsius! That said, the temperatures aren't raised or lowered by more than about 65 degrees past the set minimum and maximum. Furthermore, for typical ranges, the temperature will never be raised more than about 25 degrees past the maximum (but will still drop up to about 65 degrees Celsius below the minimum).'' (unsure about exact values, research needed)

Elves can spawn where the temperature is 10 degrees or warmer, and humans can spawn where the temperature is 0 degrees or warmer.

==== Drainage ====
Changing drainage parameters will change the way water-affected biomes are formed. Low drainage will contribute to the formation of [[Lake|lakes]], [[River|rivers]], and [[Swamp|swamps]]. High drainage will cause water to sink into the ground rather than sit on the surface, which is important for forming hills.

Lower drainage values have been reported to contribute to the formation of thicker soil layers, though it is currently unknown exactly how other factors (such as elevation or perhaps rain) impact soil formation.

==== Volcanism ====
Volcanism controls the occurrence of igneous [[layer]]s, and the formation of volcanoes. For a volcano to form, a square must have a volcanism value of 100, so reducing the maximum from 100 will make volcanoes impossible. Raising the minimum will increase the rarity of non-igneous layers.

Setting the minimum to a high value is not a good way to produce multiple volcanoes, as you are likely to get a "Volcanism not evenly distributed" rejection. Instead, use the Minimum Number of Volcanoes parameter, and possibly adjust the weighted ranges for volcanism as described below.

==== Savagery ====
These parameters control the level of [[Surroundings#Savage|savagery]] on the map. Raising the minimum savagery too high may make it impossible for certain races to exist, and similarly lowering the maximum too far can make it impossible for certain creatures to exist. The largest chance of having unusable maps comes from a too-high savagery value.

==== Configuration Tokens ====
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[ELEVATION:1:400:401:401]</nowiki></tt>
| Range: 0 to 400 Maximum of 400 required for mountain peaks. Variance range: 0-3200
|-
| <tt><nowiki>[RAINFALL:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[RAINFALL:0:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|-
| <tt><nowiki>[TEMPERATURE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE:25:75:200:200]</nowiki></tt>
| Range: -1000 to 1000 Variance range: 0-3200
|-
| <tt><nowiki>[DRAINAGE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE:0:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|-
| <tt><nowiki>[VOLCANISM:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM:1:100:200:200]</nowiki></tt>
| Range: 0 to 100 Maximum of 100 required for volcanoes. Variance range: 0-3200
|-
| <tt><nowiki>[SAVAGERY:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY:1:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|}

=== Terrain Mesh Sizes and Range Weights ===
[[File:World_map-large-32x32-elevation-mesh.png|thumb|300px|A large world generated with an Elevation Mesh Size of 32×32 and range weights set to 1:0:0:0:1 (i.e., only extreme high and low elevations). Note how the grid intersections are either set very high (mountains) or very low (oceans) and the space between them is smoothed out.]]
These parameters influence the relative proportions of terrain feature ranges, without making other ranges impossible. For example, to have many more low-elevation squares exist, without making it impossible for high elevations; this makes changing these parameters often preferable to simply changing the above min/max values. See the image on the right for an example.

The basic steps of applying weighted ranges are as follows:
# Divide the world into a grid of quantity <code>2''MeshSize'' - 1</code> areas in both X and Y direction.
# At each grid intersection, set the value according to the weighted ranges.
# Smooth out the areas between the intersection points.
# Add noise according to the variance parameters.
Where ''MeshSize'' is the raw parameter value found in the <code>[[world_gen.txt]]</code>.

==== Interaction between Mesh Size and Weighted Ranges ====
Mesh size determines how many intersection points the world will have. As an example, setting it to 2×2 means the world will divided into 4 areas, 2 across and 2 tall, and there will be a total of 9 intersection points (3×3). The grid intersection points are in the middle of world tiles, and the minimum size for a grid area is a span of 9 world tiles in either direction, with adjacent areas sharing an overlapping world tile. On a pocket world, this means one grid tile will span 9×9 world tiles, whereas on a large world, one grid tile will span 129×129 world tiles. A pocket world will always use a 2×2 grid areas of 9×9 world tiles, since it has only 17×17 tiles total (even if the game UI allows setting those worlds to a 4×4 grid, which can happen when changing the world size; changing the world size doesn't adjust mesh size limits, but saving then reloading the parameters does). A world that is 17 tiles wide, but 257 tall, and set to a 32×32 mesh size, will have 3×33 intersection points.

Setting mesh size to something other than Ignore, will apply random values at those intersections, with those random values being more likely to be in the higher weighted ranges. Setting to Ignore will cause the weighted range settings to be ignored for that terrain characteristic; instead setting the 4 corners of the world to completely random values and smoothing between those.

For example, if the Elevation Weighted Range parameters are set to <code>60:10:10:10:10</code> (starting with the 0-20 range, and these values do not have to add up to any particular number), and elevation min and max are left at the defaults of 1 and 400 respectively, then about 60% (on average) of the grid line intersection points will be set to an elevation in the range of 1-80 (0% to 20%), and the other ranges will be represented by around 10% of the intersection points each. The exact distribution is still left up to chance, though ''on average'' it will be close to this specification. This allows random number generation to be non-linear for the given terrain characteristic.

Setting the weight for a range to None only prevents intersection points from being set to a value in that range; terrain between intersection points can still be smoothed to values in ranges set to None that are between the intersection point values.

Weighted ranges do not make rejection checks, although they can be responsible for many rejections if you neglect to adjust or disable some of the [[#Minimum Number of Mid/Low/High Characteristic Squares|Minimum Number of Mid/Low/High Characteristic Squares]], for example.

==== Interaction between these and Variances ====
The end result can vary greatly depending on how the corresponding [[#X_and_Y_Variance|X and Y Variance]] parameters are set. First of all, if the variance is too high, the noise it adds can completely negate the effect of the weighted ranges. For instance, with a 2×2 mesh, the default variance parameters are high enough that usually the mesh grid can hardly be recognized. How strong the variance's effect is, is also dependent on the mesh size. Having a larger mesh size (i.e. smaller grid tiles) means the variance also has to be higher for a visible effect. For instance, with a variance of 400, the effects are clearly visible with a 2×2 mesh and barely visible at all with a 8×8 mesh. Note that this effect is directly dependent on the mesh size and not, as one might expect, on the actual size of the grid tiles. This means, that a large world with a 32×32 mesh will look essentially the same as a pocket world with a 2×2 mesh, only stretched to 256 times the size.

Also see this [http://www.bay12forums.com/smf/index.php?topic=139916.0 forum post] for more details.

==== Configuration Tokens ====
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[ELEVATION_FREQUENCY:2:1:2:3:4:5]</nowiki></tt>
| rowspan="6" | Valid mesh values:

1 = Ignore

2 = 2x2

3 = 4x4

4 = 8x8

5 = 16x16

6 = 32x32

(limited by world size)
|-
| <tt><nowiki>[RAIN_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[RAIN_FREQUENCY:3:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[DRAINAGE_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE_FREQUENCY:4:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[TEMPERATURE_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE_FREQUENCY:1:1:1:1:1:1]</nowiki></tt>
|-
| <tt><nowiki>[SAVAGERY_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY_FREQUENCY:5:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[VOLCANISM_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM_FREQUENCY:1:1:1:1:1:1]</nowiki></tt>
|}

=== Poles ===

With this, you can influence how polar regions are added. The poles can be on the north or south edge, and the equator will be on the opposite edge, or in the middle if there are two poles. If poles are set to NONE, then there will be no seasonal changes in the weather (e.g. no winter snow in temperate biomes).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[POLE:<placement>]</nowiki></tt>
| <tt><nowiki>[POLE:NORTH]</nowiki></tt>
| Viable options: NONE, NORTH_OR_SOUTH, NORTH_AND_OR_SOUTH, NORTH, SOUTH, NORTH_AND_SOUTH
|}

=== Minimum Mountain Peak Number ===

This will cause the world to be rejected if fewer than this many peaks (based on elevation) are present on the map. EG: elevations of 400 must be possible for mountain peaks to occur. If set to zero, then worlds will not be rejected based on number of peaks.

You may need to adjust elevation parameters, such as the highest weighted range, in order to get the desired number of elevation-400 squares needed for larger numbers of peaks. Like volcanoes, mountain peaks can make embark zones more interesting, but other than that, they don't appear to "do" anything special. Reportedly, they do increase the highest Z-level above ground in all embark zones in the same region, even if the selected embark zone does not include the peak.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PEAK_NUMBER_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[PEAK_NUMBER_MIN:20]</nowiki></tt>
| Elevations of 400 must occur for peaks to form.
|}

=== Minimum Partial Edge Oceans ===

This will cause a world to be rejected unless there are at least this many oceans touching an edge of the map. If set to zero then worlds will not be rejected based on this criterion. Setting both this parameter and Minimum Complete Edge Oceans to values that total more than 4 when added together may cause all worlds to be rejected as you can't have both a partial and complete edge ocean on a given edge.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PARTIAL_OCEAN_EDGE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[PARTIAL_OCEAN_EDGE_MIN:2]</nowiki></tt>
| Maximum of 4
|}

=== Minimum Complete Edge Oceans ===

This will cause a world to be rejected unless there are at least this many oceans which completely cover an edge of the map. Since a square map only has 4 edges, the maximum value possible is 4. If set to zero then worlds will not be rejected based on this criterion but still might end up with complete edge oceans by chance.

Note that the ability for this many edge oceans to exist will be limited by elevation. Therefore, to actually create large oceans you will probably need to change things like the Elevation Mesh Size and Weighted Ranges to increase the number and distribution of very low elevation squares on the map. In addition, if Complete Edge Oceans is set to any value ''other'' than 0 or 4, you may need to lower elevation variance for at least one of the axes: if set too high, such as a variation of 1600 for both X and Y axes (the default for Large Island and Medium Island parameter sets), the game may generate worlds very slowly or even hang.{{bug|565}}

Given appropriate weight, range, and variance values for things like elevation, a setting of: 1 results in a world that seems like a chunk of coastline. One edge of the map will be completely underwater and there will be ocean taking up much of the map on that side (think the east or west coast of the United States, the north coast of Canada, or southern Europe). If your edge ocean happens to pick your world's frozen side, most of it will be glacier.

*2 results in another coastline along with the first one -- the map could end up looking something like Panama if the oceans pick opposite sides of the map.
*3 results in a peninsula, like Florida in the US. There will be oceans surrounding 3 sides of the map, and land touching only one side of the map.
*4 results in one or more island(s) depending on things like elevation variance and weights. Regardless of whether you get one island or multiple islands, the entire map will be surrounded by water.

Unfortunately, there's no easy way to control which oceans end up on which edges, except perhaps setting X/Y variance to different values.

Edge oceans will take up part of the other edges too. For example, a full edge ocean on the east side will have part of the north and south sides underwater, but that does ''not'' add to the ''partial'' edge oceans count.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[COMPLETE_OCEAN_EDGE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[COMPLETE_OCEAN_EDGE_MIN:0]</nowiki></tt>
| Maximum of 4
|}

=== Minimum Volcano Number ===

The game will attempt to place this many volcanoes, but there must be at least this many squares with a volcanism of 100, if there are not the world will be rejected. Therefore, [[Advanced_world_generation#Volcanism|maximum volcanism]] above must be set to 100, and adjusting the [[Advanced_world_generation#Configuration_Tokens_2|volcanism weighted range]] above for 80-100 to a higher value can increase the number of those squares.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[VOLCANO_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[VOLCANO_MIN:15]</nowiki></tt>
| Volcanoes require a volcanism of 100 to occur.
|}

=== Mineral Scarcity ===
Controls the frequency at which minerals occur; setting this value higher will decrease both the number of different types and amounts of ore and gems present on a map. The default value will result in many metal ores, while the old default of ''sparse'' would be only a few ores, which may be limiting until other metals can be requested and traded for.

The options "Very Rare", "Rare", "Sparse", "Frequent", and "Everywhere" in the [[World_generation#Basic_world_generation_menu|basic world generation menu]] use the values 50000, 10000, 2500, 500 and 100 respectively.

According to [http://www.bay12forums.com/smf/index.php?topic=79018.msg2063804#msg2063804 research] by Shandra in v0.31.25, this is the relationship between the value of this setting and the approximate number of gems and ore:

[[File:MineralSetting_v25_limit10k.png]]

This is for the same 8x8 embark region in a world which is otherwise the same, except for the mineral scarcity parameter (although most of the detailed information comes from experiments with previous versions). (The chart legend has an error, the first "Pot.(Types)" should read "Pot.(Amount)".)
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MINERAL_SCARCITY:<number>]</nowiki></tt>
| <tt><nowiki>[MINERAL_SCARCITY:100]</nowiki></tt>
| Range: 100 to 100,000
|}

=== Max Megabeast Caves ===

This is the number of [[megabeast]]s placed at the beginning of history. Megabeasts are [[hydra]]s, [[bronze colossus]]es, [[roc]]s, and [[dragon]]s, which are all placed in equal proportions [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415177#msg3415177 data].

Increasing this value can lead to early extinction of civilizations.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[MEGABEAST_CAP:75]</nowiki></tt>
| Megabeasts count towards BEAST_END_YEAR calculation.
|}

=== Max Semi-Megabeast Caves ===

This is the number of [[semi-megabeast]]s placed at the beginning of history. Semimegabeasts are [[giant]]s, [[ettin]]s, [[minotaur]]s, and [[cyclops]], which are placed in equal proportions [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415188#msg3415188 data].

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEMIMEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SEMIMEGABEAST_CAP:150]</nowiki></tt>
| Semimegabeasts do not count towards the BEAST_END_YEAR calculation.
|}

=== Titan Parameters ===

==== Number ====

This controls the number of [[titan]]s that exist at the beginning of history[http://www.bay12forums.com/smf/index.php?topic=112465.msg3415203#msg3415203 data]. The number of forgotten beasts is unaffected by this parameter [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415155#msg3415155 data].

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TITAN_NUMBER:33]</nowiki></tt>
| Titans count towards BEAST_END_YEAR calculation.
|}

==== Attack Population Requirement ====

[[Titan]]s will begin to attack your fort once at least this many dwarves inhabit it, regardless of whether any other attack criteria have been met.

This number defaults to 80, which isn't usually too difficult to deal with.

==== Exported Wealth Requirement ====

Titans will begin to attack your fort once you have exported at least this many [[Currency|dwarfbucks]]-worth of goods, regardless of whether or not any other criteria have been met. This parameter defaults to None (disabled).

==== Created Wealth Requirement ====

Titans will begin to attack your fort once the fort's total wealth has reached this many [[Currency|dwarfbucks]] in value. This happens regardless of whether any of the other criteria, such as population, have been met; therefore, even with 1 dwarf, a fort could be attacked if the fort were worth at least this value.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_ATTACK_TRIGGER:<population>:<exp wealth>:<created wealth>]</nowiki></tt>
| <tt><nowiki>[TITAN_ATTACK_TRIGGER:80:0:100000]</nowiki></tt>
| 0 = None (disabled). Only one requirement must be met for an attack.
|}

=== Number of Demon Types ===

[[Demon]]s are similar to [[titan]]s and [[forgotten beast]]s, in that they are procedurally generated, but most are not unique. Thus, many different types of demons can exist in the world, but there will also be many individuals of most types. Thanks to [[Underworld spire|certain fun things]], fewer demon types also means fewer goblin civilizations.{{cite forum|112465/7392706}} You need at least 2 demon types, or else goblin civilizations won't exist initially, though if dwarves breach the underworld during world generation, at least one will be generated then.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DEMON_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[DEMON_NUMBER:52]</nowiki></tt>
| 0 to 1000
|}

=== Number of Night Troll Types ===

The number of different [[night troll]]s, also procedurally generated, that will exist in the world. Setting this to zero means that the world will have no night trolls, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[NIGHT_TROLL_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[NIGHT_TROLL_NUMBER:77]</nowiki></tt>
| 0 to 1000
|}

=== Number of Bogeyman Types ===
The number of different [[bogeyman]] forms that will exist in the world. Bogeymen are procedurally generated, though their forms do not vary by much. Setting this to zero means that the world will have no bogeymen, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[BOGEYMAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[BOGEYMAN_NUMBER:27]</nowiki></tt>
| 0 to 1000
|}

=== Number of Nightmare Types ===
The number of different [[nightmare]] forms that will exist in the world. Nightmares are procedurally generated. Setting this to zero means that the world will have no nightmares, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[NIGHTMARE_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[NIGHTMARE_NUMBER:27]</nowiki></tt>
| 0 to 1000
|}

=== Number of Vampire Curse Types ===

The number of different types of [[Vampire|vampires]] that will exist in the world. Although they are generated at the start of a new world, they aren't different from each other. Setting this to zero means no vampires will exist.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[VAMPIRE_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[VAMPIRE_NUMBER:72]</nowiki></tt>
| 0 to 1000
|}

=== Werebeast Parameters ===

==== Number of Werebeast Curse Types====

The number of different types of [[werebeast]]s that can exist in the world. It is common for werebeasts, unlike vampires, to assume many different forms and variations, the most well-known of these amount to different species of animals, from lizards, to wolves, to even bears. Setting this to zero means no werebeasts will exist, and will also remove a large amount of [[fun]] from the game.

In vanilla, there are only 82 possible unique werebeast species. Any further species will generate as wereblobs.{{bug|13308}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[WEREBEAST_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[WEREBEAST_NUMBER:58]</nowiki></tt>
| 0 to 1000
|}

==== Attack Population Requirement ====

Werebeasts will begin to attack your fort once at least this many dwarves inhabit it, regardless of whether any other attack criteria have been met. This number defaults to 50 which will often be reached in the second year of the fort.

==== Exported Wealth Requirement ====
Werebeasts will begin to attack your fort once you have exported at least this many [[Currency|dwarfbucks]]-worth of goods, regardless of whether or not any other criteria have been met. This parameter defaults to 5000.

==== Created Wealth Requirement ====

Werebeasts will begin to attack your fort once the fort's total wealth has reached this many [[Currency|dwarfbucks]] in value. This happens regardless of whether any of the other criteria, such as population, have been met; therefore, even with 1 dwarf, a fort could be attacked if the fort were worth at least this value.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[WEREBEAST_ATTACK_TRIGGER:<population>:<exp wealth>:<created wealth>]</nowiki></tt>
| <tt><nowiki>[WEREBEAST_ATTACK_TRIGGER:50:5000:50000]</nowiki></tt>
| 0 = None (disabled). Only one requirement must be met for an attack.
|}

=== Number of Secret Types ===

The number of secrets that exist in the world. Currently, all secrets are secrets of life and death, and the ones holding these secrets are [[necromancer]]s, thus, setting this to zero means that no necromancers will appear.
Non-necromancer towers can still appear (extremely rarely) with zero secrets, constructed by independent undead groups.
The primary difference between having 1 or 1000 secrets is the chance of your world having any necromancer towers at all. With 1, this chance is low. With the default number, it's seemingly guaranteed.
Even with 1 secret, if you have any necromancer towers at all, it is likely a great number will quickly appear in world generation (though this isn't guaranteed).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SECRET_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[SECRET_NUMBER:52]</nowiki></tt>
| 0 to 1000
|}

=== Number of Regional Interaction Types ===

The number of interactions that can be caused in regions, which may incorporate evil rain and cloud types. Currently, only evil region interactions are generated this way.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[REGIONAL_INTERACTION_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[REGIONAL_INTERACTION_NUMBER:20]</nowiki></tt>
| 0 to 1000
|}

=== Number of Disturbance Interaction Types ===
The number of different [[Mummy|disturbed dead]] that can exist in the world. Setting this to zero should prevent any mummy from appearing{{verify}}, but it will not prevent the creation of [[tomb]]s.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DISTURBANCE_INTERACTION_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[DISTURBANCE_INTERACTION_NUMBER:10]</nowiki></tt>
| 0 to 1000
|}

=== Number of Evil Cloud / Evil Rain Types ===

This number specifies how many [[Weather#Evil weather|various face-melting, eye-boiling, and zombifyingly-fun]] clouds of pure evil may appear in your world. Setting this to zero means you no longer will ever have to deal with encroaching dust walls of doom in that world. It is generally advised to keep this value low...

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EVIL_CLOUD_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[EVIL_CLOUD_NUMBER:45]</nowiki></tt>
| 0 to 1000
|}

The latter number states how many different types of green-ooze drenchers, disconcerting blood-showers, and sickly yellow slime-baths can occur in your world. Compared to evil clouds though, this one hardly is worth stressing out about, usually.... Setting this to zero means the only semi-solid to fully-liquid fluids to fall from the sky will be pure H2O.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EVIL_RAIN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[EVIL_RAIN_NUMBER:352]</nowiki></tt>
| 0 to 1000
|}

=== Generate Divine Materials ===
This turns the generation of [[Divine_metal|divine metals]] on or off. It does not influence the creation of [[vault]]s. Probably determines whenever or not using divination dice spawns weapons.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GENERATE_DIVINE_MATERIALS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[GENERATE_DIVINE_MATERIALS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Generate Mythical Materials ===

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GENERATE_MYTHICAL_MATERIALS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[GENERATE_MYTHICAL_MATERIALS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Mythical Healing ===

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALLOW_MYTHICAL_HEALING:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_MYTHICAL_HEALING:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Divination, Experiments, and Necromancy types ===
These allow or disallow [[die|divination]], demon or necromancer [[experiment]]s, and the more advanced [[necromancer]] abilities.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALLOW_DIVINATION:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_DIVINATION:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_DEMONIC_EXPERIMENTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_DEMONIC_EXPERIMENTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_EXPERIMENTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_EXPERIMENTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_LIEUTENANTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_LIEUTENANTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_GHOULS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_GHOULS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_SUMMONS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_SUMMONS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Desired Good/Evil Square Counts ===

These values change the amount of [[Surroundings#Good|good or evil]] tiles on the map, depending on the size of the region they are being considered for. The counts are for all tiles in all subregions of a given size considered together, ''not'' counts for each subregion considered separately (all tiles in the same subregion share the same [[surroundings]] values).

As used here, a "subregion" is a named world area. Subregion names and locations for a generated world are viewable in legends mode under "Regions". Subregions are classified by size the same way for all map sizes: 1-24 tiles is Small, 25-99 tiles is Medium, and 100+ tiles is Large.

The counts used here will always be restricted to regions of the given size, no matter how large the count. Also, the count is more of a goal than a minimum or maximum. As a result, you can end up with many more or many fewer than the requested number of squares in some situations. In particular, if you have something like a case where only 3 large regions exist in a world, and you request "1 evil square" in large regions, you will end up with one of the large regions being ''entirely evil''. So any non-zero value in one of these settings essentially means "force at least one region of this size to be all good/evil."

Note that the "evilness" of evil biomes is also impacted by savagery. Certain civilizations cannot exist in good and/or evil squares, so too many of one or the other may limit the size of certain types of civilizations - dwarves, for example, need non-aligned biomes. Creating too many evil biomes seems to lead to the danger of many civilizations' early extinction.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GOOD_SQ_COUNTS::<med region>:<lg region>]</nowiki></tt>
| <tt><nowiki>[GOOD_SQ_COUNTS:100:1000:2000]</nowiki></tt>
| rowspan="2" | Set count to zero to disable for that region size.
|-
| <tt><nowiki>[EVIL_SQ_COUNTS::<med region>:<lg region>]</nowiki></tt>
| <tt><nowiki>[EVIL_SQ_COUNTS:100:1000:2000]</nowiki></tt>
|}

=== Minimum Biome Square Counts ===

These numbers control whether or not a world will be rejected based on a lack of different [[biome|biomes]]. Raising these numbers will '''not''' automatically generate the given number of squares of the given biome! For a biome to exist, certain conditions like elevation and rainfall must exist.

These parameters simply filter out worlds that (for example) randomly fail to have enough high elevation squares to support a given number of mountains, etc. Some settings may cause worlds to always be rejected. For example, if for some reason the maximum elevation parameter is set to a value below what will support mountain biomes, it will be impossible to satisfy a non-zero requirement for mountain squares. The same principle goes for other conditions and biomes such as low elevations and oceans, etc.

Certain civilizations require different biomes to exist (such as dwarves and mountains), so eliminating certain biomes will make it impossible for certain civilizations to form.

These parameters often result in infinite world rejection problems. See [[World rejection]] for information on solving problems related to worlds always being rejected due to one or more of these parameters.

0 means no minimum for rejection - setting it to 0 does not guarantee 0 squares of that biome.

==== Biome Type Requirement Table ====

Terrain requirements for various biomes are described below.{{Verify}} Note that some of the exact ranges are unknown.

{| {{prettytable}}
|- bgcolor="#dddddd"
! rowspan="2" | Biome
! colspan="4" | Terrain Requirement
|-
! Elevation
! Rainfall
! Temperature
! Drainage
|-
| Swamp/Marsh
| 100-299
| 33-100
| Non-Freezing
| 0-32
|-
| Desert/Badland
| 100-299
| 0-9
| non-freezing
| note1
|-
| Forest
| 100-299
| 66-100
| non-freezing
| 66-100
|-
| Mountains
| 300-400
| N/A
| N/A
| N/A
|-
| Ocean
| 0-99
| N/A
| N/A
| N/A
|-
| Glacier
| 100-299
| N/A
| Freezing
| 80(?)-100
|-
| Tundra
| 100-299
| N/A
| Freezing
| 0-66
|-
| Grassland
| 100-299
| 0-66
| Non-Freezing
| 0-66
|-
| Hills
| 100-299
| 0-66
| Non-Freezing
| 66-100
|}
note1 drainage: 00-32 sand desert, 33-49 rocky wasteland, 50-65 rocky wasteland but different characters/appearance, 66-100 badlands

==== Minimum Initial Square Count ====

'''Note: The exclusive purpose of these parameters is to cause world rejection.'''

This is the minimum number of squares of the given biome that must exist before things like erosion take place. One thing to keep in mind is the maximum number of squares on a map of a given size - if the total number of squares on a map is lower than the sum of all square count parameters, then you will get infinite world rejection.

To determine the number of squares on a map, just multiply the dimensions. In practice these parameters will need to sum to lower than the maximum because some space is needed for "slack".

{| {{prettytable}}
|- bgcolor="#dddddd"
! Map Size
! Number of Squares
|-
| 17×17
| 289
|-
| 33×33
| 1089
|-
| 65×65
| 4225
|-
| 129×129
| 16614
|-
| 257×257
| 66049
|}

==== Minimum Initial Region Count ====

This is the minimum number of regions of contiguous biome squares that must exist before other processes such as erosion take place.

==== Minimum Final Region Count ====

This many regions of the given biome must exist after erosion and similar phases of generation have been completed.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[REGION_COUNTS:SWAMP:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:SWAMP:1032:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:DESERT:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:DESERT:1032:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:FOREST:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:FOREST:4128:13:12]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:MOUNTAINS:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:MOUNTAINS:8256:9:9]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:OCEAN:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:OCEAN:8256:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:GLACIER:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:GLACIER:0:0:0]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:TUNDRA:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:TUNDRA:0:0:0]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:GRASSLAND:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:GRASSLAND:8256:13:12]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:HILLS:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:HILLS:8256:13:12]</nowiki></tt>
|}

=== Erosion Cycle Count ===

Tells the world generator how long the world has to erode its tall peaks down to mountainsides during the 'running rivers...' stage of world creation. The higher this number, the less jagged the world will be, and the more wide the major rivers will be. If you use the maximum number, your mountains will dissolve before your eyes into plains which can lead to rejections if there aren't enough mountains to use for river start points and dwarven civilization origin points.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EROSION_CYCLE_COUNT:<number>]</nowiki></tt>
| <tt><nowiki>[EROSION_CYCLE_COUNT:250]</nowiki></tt>
| Range: 0 to 1000
|}

=== Minimum/Desired River Start Locations ===

This is the minimum number of riverheads that must exist before and after erosion takes place. Worlds will be rejected if they fail to meet these numbers. As with minimum biome counts, raising this number doesn't automatically create this many riverheads. Other conditions like terrain and rainfall must exist for rivers to form.

Extremely high pre-erosion values speed erosion greatly, while low post erosion values are useful for limiting rejects due to lack of river origin points. One can try the 800 value to get more lakes.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[RIVER_MINS:<min pre-erosion>:<des post-erosion>]</nowiki></tt>
| <tt><nowiki>[RIVER_MINS:200:400]</nowiki></tt>
| Range: 0 to 800
|}

=== Periodically Erode Extreme Cliffs ===

If enabled, makes every impassable rock wall into a series of ramps. Some prefer to pump up erosion to about 250, and turn the "Desired pre-erosion river count" to 0 for good erosion and no extra canyons.

Normally this is set to Yes (1).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PERIODICALLY_ERODE_EXTREMES:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[PERIODICALLY_ERODE_EXTREMES:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Do Orographic Precipitation and Rain Shadows ===

Toggle that allows terrain height to affect rainfall. For example, moist air coming from the ocean blows over the land. As the terrain gets higher, it forces the moist air up, causing it to rain on the seaward side of a mountain. Eventually, all the rain has fallen if the mountain is tall enough. So, when the breeze goes over the top, there's no moisture left to fall on the other side, creating a rain-shadow. In the current version, regions where drainage is above 50 will also create rain shadows, regardless of the underlying biome and elevation.{{cite forum|140685/5484064}}

Turning this on should create a tendency for more extreme rainfall in regions, creating more forests, deserts, marshlands, and grasslands. Also note that it can create rainfall outside of min-max rainfall settings, so even in a world with a 0 max rainfall you may get rainfall biomes. Turning it off should result in more controllable, less complex rainfall conditions based on rainfall parameters as it adds a random element which can distort or otherwise mess up the climates on a pregenerated map.

This should be disabled if you're importing a map or using a preset map file that has weather.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[OROGRAPHIC_PRECIPITATION:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[OROGRAPHIC_PRECIPITATION:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Maximum Number of Subregions ===

This is the number of separate biomes (the flashing regions you see on embark when you hit F1, F2, etc. when there's more than one biome on the embark location) that are allowed to exist on the entire map.

Setting this to very low values will result in numerous rejections depending on [[#X and Y Variance|variance parameters]]. If variance values are set to high numbers, many small biomes will be created causing rejection if this parameter value is not increased beyond the default.

Increasing the value of this tag is often a must when generating "patchwork" worlds with lots of biome variance, but simply increasing it without increasing variance parameters will not guarantee more biomes.

It is also interesting to note that the maximum subregions is 5000 which is more than the total number of squares for a pocket or small map. However, for a medium or large map (16641 or 66049 squares) it quickly becomes a mere fraction of the total number of possible subregions. In fact it would be quite easy on a large map to end up with far too many subregions and get endless rejections of this type.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SUBREGION_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[SUBREGION_MAX:2750]</nowiki></tt>
| Range: 1 to 5000
|}

=== Cavern Parameters ===
[[Caverns]] are the hollow areas underground, which dwarves tend to encounter when they're digging around. The '''Cavern Layer Number''' parameter determines how many cavern systems will be generated, not including the magma layer or the Bottom layer. Defaults to three - setting it to lower values could help FPS. Setting it to 2 will merge cavern 3 species into the 2nd cavern, and setting it to 1 will merge all into one cavern. However, disabling them entirely by setting it to 0 will make it impossible to grow any underground plants, as none will exist for your civilization to cultivate, nor will they be available on embark.

*Setting caverns to a sub-3 number (Spoiler, highlight to view) erases about one-third of HFS spires{{Bug|10267}} and prevents dig deep disasters. Additionally, random plant or animal species can be more frequently absent.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_COUNT:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_COUNT:3]</nowiki></tt>
| Range: 0 to 3
|}

==== Cavern Layout Parameters ====

Open caverns and dense passageways are not mutually exclusive. When both are raised, bizarre results can occur, such as layers showing a combination of open caverns, a cluster of network passages, and natural walls sprinkling the inside of an otherwise open cavern. [http://www.bay12forums.com/smf/index.php?topic=76355.msg1936859#msg1936859 Reference]

If you want the largest open spaces possible, then decrease the density and increase the openness. If you want a labyrinth of passageways, lower the openness and raise the passage density.

Another interesting note about the cavern layers is that the seed and number of demon types affect the layout of the caverns.

<gallery widths=200 heights=200 perrow=2>
File:Open00Density100.jpg|Cavern slice with Openness of 0 and Density of 100
File:Open100Density00.jpg|Cavern slice with Openness of 100 and Density of 0
File:Open100Density100.jpg|Cavern slice with Openness of 100 and Density of 100
File:Open50Density50.jpg|Cavern slice with Openness of 50 and Density of 50
</gallery>

===== Layer Openness min/max =====

Dictates the size of cavern passages. When Passage Density (see below) is set to minimum (0), caverns will be open expanses. Raising the maximum will increase the size of the caverns.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MAX:100]</nowiki></tt>
|}

===== Layer Passage Density min/max =====

Determines how many passages form the cavern. If openness (see above) is set to minimum and density increased, then you will get a maze-like network of small criss-crossing passages. Raising the values further increases the number of the maze-like passages.

Caverns will be large, open spaces at 0, and comprised of many small vertical shafts of rock at 100. Setting both values to be the same results in a uniform look for the caverns.{{Verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MAX:100]</nowiki></tt>
|}

===== Layer Water min/max =====

Determines the minimum and maximum percentage of water each cavern can contain.

Caverns with a water level of 10 or higher can support creatures and plants from the "Subterranean Water" biome, and caverns with a water level of 90 or lower can support the "Subterranean Chasm" biome; levels of 10-90 support ''both'' biomes, while levels below 10 or above 90 support only one.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_WATER_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_WATER_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_WATER_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_WATER_MAX:100]</nowiki></tt>
|}

==== Magma Layer ====

This parameter controls whether the [[magma sea]] exists.

Setting 1/Yes causes the magma layer to exist, value 0/No prevents it. Appears not to have any impact on volcanoes nor volcanism, so even if 0/No, there will still be embark locations with magma. If a [[volcano]] exists, it appears to always tap the magma sea, but the magma sea will not be revealed by revealing the volcano.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[HAVE_BOTTOM_LAYER_1:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[HAVE_BOTTOM_LAYER_1:1]</nowiki></tt>
|}

==== Bottom Layer ====

Determines if the space below the magma sea exists. If Yes the "HFS" layer is always present. Normally you want to leave this set to Yes for maximum fun.

If enabled, this will force the magma layer above it.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[HAVE_BOTTOM_LAYER_2:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[HAVE_BOTTOM_LAYER_2:1]</nowiki></tt>
|}

=== Z Levels (Depth) Settings ===

These parameters control the "thickness" of various "layers" on the map. Note that a "layer" in this case does not refer to one Z-level, but refers to a number of related Z-levels such as "levels above ground".

The following table assumes that you have 3 cavern layers. (out of a minimum of 0-3) The Levels Above Layer settings control how many Z-Levels are above each layer. A layer may itself consist of multiple Z-Levels (and almost always does).

{|style="margin:1em 1em 1em 0;background:#F9F9F9;border:1px #AAA solid;border-collapse:collapse;" class="wikitable"
|-style="background:#F2F2F2;text-align:center;"
!style="border:1px #AAA solid;padding:0.2em;" width="120"|Setting Name
!style="border:1px #AAA solid;padding:0.2em;" width="200"|Token
!style="border:1px #AAA solid;padding:0.2em;"| Description
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Ground
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_GROUND:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| The number of Z-levels of air above the highest surface level. Has no impact on how many Z-levels deep the surface layer is.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above layer 1
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_1:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of stone above the first cavern layer. Making this higher will guarantee ''at least'' that many levels to build your fortress, but will have no impact on how many z-levels thick the surface layer is. Also, the top of a cavern may be higher than the rest of a cavern, so in practice there will be more "solid" levels than this above the cavern.
As of version 0.31.25 this setting is inaccurate. The actual number of z-levels may vary in a range of approx. ±5, which may result in non-existence of any solid z-levels between a surface layer and first cavern layer.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 2
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_2:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very top of the second cavern and the very bottom of the first cavern.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 3
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_3:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very top of the third cavern and the very bottom of the second cavern.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 4
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_4:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very highest magma and the very bottom of the third cavern. Spoiler Hidden (select invisible text to read): Making this high will give a large area for HFS veins, so that it never touches caverns, giving more to mine '''if''' it was impacting the cavern previously.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 5
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_5:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Uncertain. May control the number of levels of "Semi Molten Rock" between HFS and Magma, may control number of levels of magma, may impact both. In experimentation, the overall depth of all magma sea and semi-molten rock levels appears to increase, but not consistent enough to say for certain. Only valid if Magma Layer present. Spoiler Hidden:Often the HFS vein will only extend as high as the highest magma, making this the only guaranteed way to increase amount of HFS to mine, but unfortunately also creating enormous useless semi-molten z-levels
|-
|style="border:1px #AAA solid;padding:0.2em;"| At Bottom
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_AT_BOTTOM:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Appears to be number of levels of HFS chamber. Only valid if Bottom Layer present, often having no impact. Values larger than default result in strange things.
|}

Some implications:
* The number of surface layers (e.g. soil), at this time, cannot be controlled. For example, on a map with 1 layer of peat, then a layer of silt, then a layer of obsidian, there is no control to let you increase either one to be, say, 20 z-levels. (though you may get lucky with the obsidian).
* There can be multiple stone layers between the cavern and the surface, so, increasing Levels Above Layer 1 may give you more conglomerate or more granite, and you have no control over which stone layer spans those Z-levels.
* The layers shown on embark span across the cavern layers in an unknown and inconsistent way. Sometimes those 10 different layers of stone are evenly distributed over your 400 z-level deep map, sometimes the first 9 get 1 z-level each and the last gets the other 391 levels. No way to control found yet.
* The HFS chamber, if present, will always extend into the rock layers, and appears to always make contact with the bottom cave. Large values for levels above layer 5 and layer 4 can result in enormous chambers, but the number of levels at the top (the part with undead) appears to be unaffected.
* Unconfirmed whether number of levels between caverns has any impact on cavern height. There will be connecting ramps and/or shafts between cavern layers no matter how many levels are between them.
* '''Very Important''': These values appear to apply across a whole 16x16 region, not just embark areas. That means that if a 16x16 region is completely flat, but has one tall mountain in one far corner, even if you set Levels Above Ground low (e.g. 2 z-levels) you still have all the empty air of the highest mountain in every embark tile (e.g. 200 z-levels). Also can happen to the semi-molten layer, and can lead to unexpected behavior.
* Very large or small values can cause strange things to happen.

=== Minimum/Maximum Natural Cave Size ===
It's not clear what effect these currently have, other than changing them can change the location of caves somewhat.{{verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVE_MIN_SIZE:<number>]</nowiki></tt>
| <tt><nowiki>[CAVE_MIN_SIZE:5]</nowiki></tt>
| rowspan="2" | Range: 1 to 500
|-
| <tt><nowiki>[CAVE_MAX_SIZE:<number>]</nowiki></tt>
| <tt><nowiki>[CAVE_MAX_SIZE:25]</nowiki></tt>
|}

=== Number of Caves ===
The number of caves generated in mountainous and non-mountainous regions, mountain caves will always be generated on the edge of mountain ranges next to non-mountainous regions. Lurking [[kobold]]s set up shop in caves, and store their stolen items there - a setting of 0 in both will stop kobold civilizations from appearing. Special note: a cave is not initially a [[lair]], although beasts can later use them as their lair.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[MOUNTAIN_CAVE_MIN:100]</nowiki></tt>
| rowspan="2" | Range: 0 to 800
|-
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:200]</nowiki></tt>
|}

=== Number of Mythical Sites ===
The number of [[mysterious dungeon|mysterious sites]] generated around the world. The extended effects of setting this to 0 has not been determined{{verify|is chosen still available? is quest still given? etc.}}.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MYTHICAL_SITE_NUM:<number>]</nowiki></tt>
| <tt><nowiki>[MYTHICAL_SITE_NUM:200]</nowiki></tt>
| rowspan="2" | Range: 0 to 800
|}

=== Make Caves Visible ===
If set to no (default) then the location of caves will not be marked on the map. If set to yes, caves will appear on the map so that they may be sought out or avoided as desired.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALL_CAVES_VISIBLE:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALL_CAVES_VISIBLE:0]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Init Options to Show Tunnels ===

If enabled, you will be able to see the underground tunnels often built by dwarves on the world map, and they will appear as black lines, similar to roads.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SHOW_EMBARK_TUNNEL:<0-2>]</nowiki></tt>
| <tt><nowiki>[SHOW_EMBARK_TUNNEL:2]</nowiki></tt>
| 0 = No 1 = Only in Finder 2 = Always
|}

=== Number of Civilizations ===

This number of [[civilization]]s will be placed on the map before history generation begins. These civilizations may later die out due to historical events. It is noteworthy that the chance for any given civilization to be destroyed through megabeasts decreases with a higher total number of civilizations present[http://www.bay12forums.com/smf/index.php?PHPSESSID=7348f68f41a9659443c05b2acf534e6c&topic=112465.15 data]. The five races are dwarf, elf, human, goblin, and kobold; they will generally be placed in equal numbers until the quota has been reached. If there are not enough biomes or other worldgen prerequisites for an even distribution, certain civs will be much more or less frequent than others[http://www.bay12forums.com/smf/index.php?PHPSESSID=7348f68f41a9659443c05b2acf534e6c&topic=112465.15 data]. If there is an odd number of civs (not divisible by 5), then the remainder is distributed randomly. Kobold civs require caves to be placed; if no caves exist, then kobolds are skipped and will not appear. This does not cause rejections [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415125#msg3415125 data]. Goblin civilizations require multiple demons, see the [[#Number_of_Demon_Types|number of demon types]] section above.

Note that a high value here can cause lots of map rejections, particularly on smaller maps as there simply isn't enough room or regions to put them all in.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_NUMBER:40]</nowiki></tt>
| Range: 0 to 300
|}

=== Playable Civilization Required ===

If this is set to yes (default) then worlds will be rejected if no civilization with [[Entity token|CIV_CONTROLLABLE]] can be placed. In an unmodded game, only the dwarves have this token.

If set to no, the result may be a world that cannot be played in Fortress Mode.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PLAYABLE_CIVILIZATION_REQUIRED:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[PLAYABLE_CIVILIZATION_REQUIRED:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Minimum Number of Mid/Low/High Characteristic Squares ===

Sets the minimum possible number of squares of certain ranges of each of the region qualities, such as elevation, rain, drainage, volcanism, savagery, and temperature. These need to be changed to reflect your regional meshes and weights, and are responsible for a HUGE number of map rejections. These values can all be set to 0 for much fewer map rejections, particularly in the case of more wacky, non-standard maps.

These values will cause worlds to be rejected unless at least the given number of squares of the given type are randomly generated. Setting these values too high could result in worlds always being rejected if other parameters such as the maximum/minimums for elevation, etc., don't allow enough of those squares to get generated.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[ELEVATION_RANGES:8256:16512:8256]</nowiki></tt>
| rowspan="5" | Minimum number of squares that must have low, medium, and high amounts of the given attribute. 
0 = No minimum
|-
| <tt><nowiki>[RAIN_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[RAIN_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[DRAINAGE_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[SAVAGERY_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[VOLCANISM_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM_RANGES:8256:16512:8256]</nowiki></tt>
|}

==World rejection==

:''Main article: [[World rejection]]''

If you are having the common problem of generated worlds always being rejected by the world generator, see [[v0.31:World rejection|Solving World Rejection Problems (v0.31 page)]] as it contains many detailed suggestions on how to troubleshoot and solve these issues.

== Parameter set examples ==

If you're trying to do something specific, then the [[Worldgen examples]] - complete parameter sets that can be copied directly into your ''world_gen.txt'' file and customized as desired - might be helpful.
If none of the examples suit your needs, [[Worldgen tricks]] has strategies and tips on making a world just right for you.

For many, many more examples see:
* [http://www.bay12forums.com/smf/index.php?topic=101280 DF2012 (v0.34) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=140180 DF2014 (v0.40) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=168543.0 DF2014 (v0.44.02+) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=175538 DF2014 (v0.47.01+) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=180805.0 DF2022 (v0.50.01+) WorldGen "Cookbook" Thread]

{{World}}

Advanced world generation

2026-04-10T02:46:01Z

Ziusudra: /* Interaction between Mesh Size and Weighted Ranges */ expanded parenthetical about mesh size limits in UI

{{migrated article}}
{{Quality|Superior}}
{{av}}
:''This article contains information on advanced world generation. For information on basic world generation, see [[World generation]].'' ''See [[World token]] to more easily find information by the names used in the world_gen.txt file, [[World rejection]] for information on solving problems related to worlds always being rejected, and [[Worldgen examples]] for example worlds.''

[[File:adv_worldgen_v50.png|thumb|400px|right|The advanced world generation screen. ''(Click to enlarge)'']]'''Advanced world generation''', also labeled as '''detailed mode''', allows substantially more detail-oriented options of customization than standard, basic world generation. This gives the player much more control over how their world is generated. To better understand this article, it is advised that one should read about [[World generation|'''basic world generation''']] first.

The advanced world generation screen is reached by clicking "Create new world" at the main menu, then clicking "Detailed mode". Once at that screen, clicking "Basic options" will return the user to the standard world generation screen.

== Parameter sets ==
There are multiple default sets of all the advanced world generation parameters hard-coded in ''Dwarf Fortress'', which will be overridden by the <tt>prefs/world_gen.txt</tt> file in the main ''Dwarf Fortress'' directory, if it exists. It does not exist by default, you must create it, either by saving the default sets, or saving a copy from the [[world_gen.txt]] wiki page or elsewhere. This file can then be edited with a text editor, and you can copy and paste other players' sets of parameters into it. For sources of such parameter sets see [[Advanced_world_generation#Parameter_set_examples|Parameter set examples]] below.

To get back the default sets, move the existing <tt>prefs/world_gen.txt</tt> to somewhere else (like Documents), or delete it if you do not want to keep the changes, then load the sets in the game, it will then use the hardcoded defaults.

== User interface ==
First, there is a line of text inputs and buttons along the top of the screen, from left to right:
* The drop down menu of currently defined parameter sets, click the down arrow to select a set that you want to work with. The currently selected set can be renamed by clicking the current name or the [[File:Quill.png]] button. The first set in the file is selected by default, usually "LARGE ISLAND". See [[#Parameter set title|Parameter set title]].
* The dimensions of the world for the selected set, see [[#World dimensions|World dimensions]].
* A text entry box to set all of the seed options to the same seed, will show "Random seed", "Various seeds", or, if all four seeds are set to use the same value, that value. See [[Advanced_world_generation#Seed_values|Seed values]] and [[Advanced_world_generation#Seed_values|Seed notes]].
* The Copy Button to make a copy of the currently selected set and appends it to the bottom of the list.
* The red Delete button to delete the currently selected set, you will be prompted to confirm the deletion.
* The New parameter set to create a new parameter set and appends it to the bottom of the list. This seems to just copy the default "LARGE REGION" set.
* The Save button to save all of the current sets to the <tt>prefs/world_gen.txt</tt> file.
* The Load button to load from the same file, there is no confirmation, '''any unsaved changes will be lost'''. If that file does not exist, this resets all of the sets to the defaults.

Most of the middle is the parameters themselves, with a scroll bar to the right. Each row of the list can include:
* The name of the option
* The range of accepted values; not every option has this, and does not always match the displayed value, for example "0 to 1" might show as "No" and "Yes".
:* Sometimes the range might not initially show on rows that it should, reloading the sets with the Load button sometimes fixes that.{{bug|13176}}
* A plus button to increase the value or cycle through options, when applicable (this button will be missing if the range is missing.)
* The current value; can be clicked to edit, to actually set a value you must press {{k|enter}}, without doing that, clicking another entry box or right clicking will instead reset to the currently set value.
* An edit button to show that the previous box is editable, same as clicking on the text box.
* A minus button to decrease the value or cycle through options, when applicable (this button will be missing if the range is missing).
* A red button to disable this parameter, when applicable, usually setting the value to 0, or -1.

{{notice bar|bgcolor=#faa|bordercolor=#f00|All of the buttons below leave this screen and do not prompt to save the sets, so unsaved changes may be lost.}}
At the bottom right are 3 or 4 more buttons:
* The Create world button to do just that using the currently selected set, '''unsaved changes are lost'''.
* The Basic options button to go back to the normal world generation screen, unsaved changes are not lost if you come directly back to Detailed mode.
* The [[Mods]] button to go to the mod selection screen, unsaved changes are not lost if you come directly back to Detailed mode. Only shown if mods are available.
* Back to main menu button to do just that, '''unsaved changes are lost'''.

=== World painter ===
:''Main article: [[World painter]]
The '''world painter''' tool is not in the current version of ''Dwarf Fortress''; it allowed you to paint features onto a map. '''However''', those maps can still be used when generating a world by pasting world painter parameter set maps created in old versions into the <tt>prefs/world_gen.txt</tt> file. [[Utilities#Perfect_World_DF|Perfect World DF]] is a utility that uses the same parameter functionality as the world painter to paint a map, and it also can work with the current version of ''Dwarf Fortress''.

== Generating a world ==
You can either use an already-defined parameter set, or you can edit them, though it is highly suggested to edit a copy of one of the defaults. Once you are happy with the parameters you should save the values you just edited before you click the Create world button. Information about each parameter is documented below.

The phases of the world generation process are (this order is not completely correct):
* Preparing elevation...
* Setting temperature...
* Running rivers...
* Forming lakes and minerals...
* Growing vegetation...
* Verifying terrain...
* Importing wildlife...
* Recounting legends...
* Placing civilizations...
* Making cave civilizations...
* Making cave pops...
* Placing other beasts...
* Placing megabeasts...
* Placing good/evil...
* Placing caves...
* Prehistory generation
* Finalizing civ mats...
* Finalizing art...
* Finalizing uniforms...
* Finalizing sites...

== Seed notes ==
The world generation process uses a PRNG (Pseudo Random Number Generator) algorithm. A PRNG will produce a sequence of numbers that "looks" random, even though the actual sequence of numbers will always be the same if the PRNG is started with the same seed value. Basically this means that if you run world generation with a certain seed value on your computer, and someone else runs world generation with the same seed value on their computer, the same sequence of random numbers will be generated on both computers. The practical impact of this is that someone else can generate exactly the same world that you generated by entering the same seed value that you used.

In the current version, the seed values for the world itself and the names seem to produce the same result, but you will get changes in events which will result in a very different world history.{{bug|6934}} Keep this in mind if you want to regenerate a particular world.

The way that a world is generated can also be affected by certain world tokens. Changing them causes that code to use more or fewer PRNG values, causing later uses to get different parts of the sequence. So, you cannot for example, change the minimum and maximum rainfall and get 'the same world but drier or wetter', instead, a different world is generated. That said, it would also seem that certain small changes to these world tokens can occasionally generate a very similar world, however, other tokens are more sensitive. For more information see the forum thread [http://www.bay12forums.com/smf/index.php?topic=112132.msg3404199#msg3404199 here].

The following are tokens which use the PRNG values in ways that changing them will likely cause broader changes:

* [DIM:X:X]
* [ELEVATION:X:X:X:X]
* [RAINFALL:X:X:X:X]
* [TEMPERATURE:X:X:X:X]
* [DRAINAGE:X:X:X:X]
* [VOLCANISM:X:X:X:X]
* [SAVAGERY:X:X:X:X]
* [ELEVATION_FREQUENCY:X:X:X:X:X:X]
* [RAIN_FREQUENCY:X:X:X:X:X:X]
* [DRAINAGE_FREQUENCY:X:X:X:X:X:X]
* [TEMPERATURE_FREQUENCY:X:X:X:X:X:X]
* [SAVAGERY_FREQUENCY:X:X:X:X:X:X]
* [VOLCANISM_FREQUENCY:X:X:X:X:X:X]
* [PARTIAL_OCEAN_EDGE_MIN:X]
* [COMPLETE_OCEAN_EDGE_MIN:X]
* [HAVE_BOTTOM_LAYER_1:X]
* [MINERAL_SCARCITY:X] {{cite talk/this|Mineral scarcity}}

Many other world parameters, such as end year and embark points, can, however, be changed without it having any effect on the geography of the world generated from the seed values.

Normally, you don't enter these seed values, the game comes up with values based on some other sort of pseudo-random information from things like the current date and time.

When generating a world, ''Dwarf Fortress'' records the seeds it used in [[gamelog.txt]]; they can also be found with <code>gui/gm-editor world.worldgen.worldgen_parms</code> in [[DFHack]].

== Advanced parameters ==
There are essentially 4 types of controls for the generation of the surface map;

'''Terrain parameters''': as described below, these 5 variables define the basic background world, how hot or cold it is, how much rainfall, how high the mountains are. The world automatically goes through the temperature range along the Y axis, although sometimes it will be hotter in the north, other times in the south, or cold at both. Minimum, maximum and X,Y variance can drastically alter the world.

'''Weighted meshes''': these are a way to fine-tune the amount of the 5 basic variables on the map. They can be used to set the specific distribution of different elevations or rainfall areas for example.

'''Feature parameters''': such as rivers, mountain peaks, volcanoes, and oceans, which can cause rejections if the terrain parameters don't allow enough suitable locations for the features to be placed.

'''Rejection parameters''': ''Dwarf Fortress'' uses a 'belt-and-braces' approach to world generation. The above controls allow you to shape the world, then the rejection parameters throw it out if it does not meet certain criteria. There are a number of rejection parameters for the number and degree of the 5 basic variables, for biome types, etc. If the world does not meet the requirements of any one rejection parameter the world is rejected and re-randomised. Also see [[World rejection]].

Leaving tokens out of a set in <tt>world_gen.txt</tt> will cause the game to use default values which are not adjusted for smaller world sizes, this may cause smaller worlds to always be rejected.

If you are experimenting with world design, there is also a [[Settings#Feature_toggles|game setting]] that will log the rejection reasons to ``[[map_rejection_log.txt]]``. With that information you can then either adjust the rejection parameters to allow those worlds, or the other parameters to prevent them from trying to generate. ''Dwarf Fortress'' will keep adding to the file, so you may want to trim or delete it occasionally.

The parameters are described below in the order that they appear in the list in the game, which is not necessarily the order they appear in <tt>world_gen.txt</tt>. See [[world token]] for an index that will help you look things up by token name. The tokens used in <tt>world_gen.txt</tt> are at the bottom of each of the following parameter descriptions.

=== Parameter set title ===
This sets the name of the parameter set itself, as used in the list of sets (this has nothing to do with the name of the generated world).
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITLE:<name>]</nowiki></tt>
| <tt><nowiki>[TITLE:MEDIUM ISLAND]</nowiki></tt>
| Required
|}

=== World dimensions ===
The size of the map for the current set can be changed by changing the Width and Height values at the top next to the set title. You will need to confirm this, since changing the dimensions of the world will change other parameters, because many of them have different defaults depending on the surface area available.

Larger maps usually take longer to generate and may reduce [[Frames per second|FPS]] in-game, though this is really a matter of larger worlds usually having more civilizations, sites, historical figures, and events; restricting the number of those can speed up the process. Non-square maps may result in crashes{{bug|2928}}.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DIM:<width>:<height>]</nowiki></tt>
| <tt><nowiki>[DIM:257:257]</nowiki></tt>
| Valid values are 17, 33, 65, 129, and 257, other values will use one of those. Changing the size in the file without adjusting other parameters can cause many rejections.
|}

=== Seed values ===
Enables the use of, and specifies seed values for, different parts of the world generation process. Just entering a specific seed does not enable it, that must be done separately, although using the box at the top to set all the seeds to the same value does enable them all. Enabling a seed puts the token in using what ever is in the text box below. If you enable a seed, but do not enter a seed, the string "Seed text" will be used (<tt><nowiki>[SEED:Seed text]</nowiki></tt>). Trying to use a <tt><nowiki>]</nowiki></tt> in the string in the file will end the seed there, since it closes the token, any text after that will be ignored. Normally, just leave these set to Random, unless trying to reproduce the results of a previous world generation. See also the [[Advanced_world_generation#Seed_notes|seed notes section]] above.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEED:<text>]</nowiki></tt>
| <tt><nowiki>[SEED:31337]</nowiki></tt>
| rowspan="4" |
For each of these not in the config file, a random seed will be used, and the first seed is not used to generate the others. The seeds used are output to [[gamelog.txt]] when world generation starts.
|-
| <tt><nowiki>[HISTORY_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[HISTORY_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[NAME_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[NAME_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[CREATURE_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[CREATURE_SEED:31337]</nowiki></tt>
|}

=== World name ===
As previously mentioned, the title of the parameter set doesn't affect the name of the world. You can specify a particular name for your world, or leave the value blank for a random one. (The [[DFHack]] utility adds an option to rename the world using the in-game languages.)
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CUSTOM_NAME:<name>]</nowiki></tt>
| <tt><nowiki>[CUSTOM_NAME:Realm of Cheese Engravings]</nowiki></tt>
| For a random name, simply don't use this token.
|}

=== Embark Points ===
The number of points for equipment and animals when embarking in fortress mode (there is no equivalent setting for adventure mode). Normally, the default of 1504 is fine, but can be increased for various purposes like experimentation or to help dwarves survive in a particularly evil world, or reduced for certain [[challenges]].
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EMBARK_POINTS:<number>]</nowiki></tt>
| <tt><nowiki>[EMBARK_POINTS:1504]</nowiki></tt>
| 0 to 10,000
|}

=== End year ===
The maximum number of years generated for the world, although generation can be paused and the world used as is any time after the second year; the same as the [[World_generation#History|History]] parameter in basic world gen, except that you can enter an exact value. A too-short history can limit the materials available to civilizations, and [[Chosen|certain adventure mode features]] are only available after certain site events, while too long a history often leads to civilizations dying.

For more information on the history aspect of the game, see [[Legends]] and [[Calendar#Ages|Ages]].
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[END_YEAR:<number>]</nowiki></tt>
| <tt><nowiki>[END_YEAR:250]</nowiki></tt>
| 2 to 10,000
|}

=== Population cap after civ creation ===
A soft limit to the total number of [[historical figure]]s alive at the same time during generation across all civilizations, only preventing the birth of new historical figures.{{cite forum|140544/5701667}} Each civilization is allotted a percentage of the total by the percentage of sites they control.{{cite forum|159164/7553641}} Civilizations also have non-historical populations, and there is no setting to limit those (in early versions, all civilization members were historical figures, this is also why the name of this setting is misleading). Each [[entity]] also has limits from their raws, see the [[Entity_token#Population|population]] entity tokens, and setting this to unlimited will not remove those.

Huge historical figure populations can slow generation and the game in general.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_POPULATION:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_POPULATION:15000]</nowiki></tt>
| -1 to 100,000, -1 is no limit
|}

=== Site cap after civ creation ===
Total number of [[site]]s that can be directly created by all civilizations combined like [[hillocks]], [[hamlet]]s, [[dark pits]], [[forest retreat]]s, etc. Does not prevent the placement of initial civilization sites, though they will then be counted for the limit. Does not affect creature sites like [[cave]]s or [[lair]]s, group sites like [[castle]]s, [[monastery|monasteries]], [[tower_(necromancy)|tower]]s, [[fort]]s, or [[camp]]s, or unpopulated sites like [[tomb]]s. After this limit is reached, no civilization will be able to place new sites. See the [[Entity_token#Placement|placement]] entity tokens for other ways that civilization site placement can be limited.

Increasing this will slow generation down and reduce the available places for player sites. Since the {{token|MAX_SITE_POP_NUMBER|entity}} entity token limits the historical figure population per site, this site cap can also limit the total historical figure population of all civilizations combined, and some expand faster than others getting more sites before the limit is reached.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SITE_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SITE_CAP:1500]</nowiki></tt>
| -1 to 100,000, -1 is no limit
|}

=== Beast control ===

These parameters don't usually matter too much, but may matter for small numbers of beasts.

==== Percentage of Megabeasts and Titans Dead for Stoppage ====

The world starts out with a certain number of powerful megabeast and titan entities in existence. If a percentage of the megabeast and titan population dies out during history generation, then history generation will stop early. For example, if the elimination value is 80%, and the generated history starts with 200 entities and 160 of those 200 entities are eliminated by historical events before the End Year is reached, history generation will stop immediately.

If you want to end the creation of your world at the beginning of a certain age, choose the following values:
* Age of Legends: ~34%
* Age of Heroes: ~67%
If there are three or fewer titans or megabeasts in your world, the age will be given a special name reflecting the remaining megabeasts/titans, instead.

==== Year to Begin Checking Megabeast Percentage ====

The percentage of dead [[megabeast]]s and [[titan]]s for stoppage will not be checked until this year is reached in history generation. This can be used to ensure that a world reaches a certain year even if all of the megabeasts in the world are slain earlier.

If the number of living [[megabeast]]s and [[titan]]s starts at or drops to less than four, then world generation will always stop if the current year is equal to or greater than the Year to Begin Checking Megabeast Percentage ''regardless'' of how many [[megabeast]]s and [[titan]]s are dead — Percentage of Megabeasts and Titans Dead for Stoppage is ignored. The number of megabeasts and titans at the start of the world is set by the sum of the [[Advanced_world_generation#Max_Megabeasts_Caves|Max Megabeasts Caves]] and [[Advanced_world_generation#Titan_Parameters|Titan Number]] parameters.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[BEAST_END_YEAR:<year>:<percentage or -1>]</nowiki></tt>
| <tt><nowiki>[BEAST_END_YEAR:200:80]</nowiki></tt>
| Use -1 as percentage to disable. Year must still be at least 2.
|}

=== Cull Unimportant Historical Figures ===
{{main|Historical figure}}
Whether to remove unimportant dead historical figures after history generation; a short CPU-intensive step, but saves space which can speed up loading, saving, and running games with large histories. Legends mode will refer to culled creatures as "an unknown creature", and they will not appear in engravings, but likely would not have anyway.

Exactly what is considered important is not clear. A member of an abstract group killing a named creature is not. Creating an artifact is not, even if that artifact had important history. Unculled historical figures can have parentage described as "The identity of" that parent "has been lost to time", so just having children is not, though having living direct relations seems to prevent culling.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CULL_HISTORICAL_FIGURES:<0 or 1>]</nowiki></tt>
| <tt><nowiki>[CULL_HISTORICAL_FIGURES:0]</nowiki></tt>
| 0 = No, 1 = Yes
|}

=== Reveal All Historical Events ===

Setting this to Yes will allow access to most information about the history of the world in [[Legends mode]]. All events will be revealed, but some [[historical figure]]s, [[site]]s, [[region]]s, and [[civilization]]s and other entities may not be, possibly because they are not known to any civilization. If set to No, then you will have to discover historical information in [[adventure mode]] or by instructing dwarves to make engravings.{{Verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[REVEAL_ALL_HISTORY:<0 or 1>]</nowiki></tt>
| <tt><nowiki>[REVEAL_ALL_HISTORY::1]</nowiki></tt>
| 0 = No, 1 = Yes
|}

=== Terrain Parameters ===

These set limits and variance for terrain elevation, rainfall, temperature, drainage, volcanism, and savagery which determines how those values are generated. What biomes exist are then determined by how these factors overlap with each other.

==== Minima and Maxima ====
These are the absolute minimum and maximum values that can ever be generated for a particular map square characteristic. By ''subtly'' tweaking the min and max values, vastly different maps can be made. Changing these can cause the occurrence of certain [[Biome|biomes]] to become impossible, so you may want to use [[#Terrain Mesh Sizes and Weights|Weighted Ranges]] instead.

==== X and Y Variance ====
These control how wildly things like elevation and rainfall can vary between adjacent map squares. For example, if these values are set to the maximum of 3,200 for elevation then you will end up with more very low areas right next to very high areas. The number for X determines the east-west variance and the number for Y determines the north-south variance. By setting only one of these to a high value you can, for example, create horizontal or vertical bands of areas which are more similar to each other.

Generally speaking, raising both of these values will create a more random "patchwork" of many small biomes while setting both x and y values to 0 will cause every square on the map to use a single random value for the given characteristic.

For "patchwork" worlds to avoid being rejected, [[#Maximum Number of Subregions|Maximum Number of Subregions]] will probably need to be increased from the default.

==== Elevation ====
This controls the range of terrain elevations that can occur in the world. Usually, you just want to leave the min/max values alone. Raising the minimum elevation can, for example, make it impossible for oceans to exist. This does '''not''' directly control the number of available Z-levels at a particular site, though high maximum values may contribute to peaks, which can raise the number of above ground Z-levels - in other words, a maximum elevation of 400 and minimum of 1 does not mean you get 400 Z-levels, but it might increase the number of Z-levels somewhat in some regions compared to others. Raising the variance will result in a more bumpy, uneven landscape.

Some biomes/features that are impacted by elevation:
* A high minimum (above 99) means no oceans, as they need elevations below 100.
* A low maximum (below 300) means no mountains, as mountains need elevations above 300.
* Rivers will be placed when the elevation maximum is 104 or higher. Therefore, keeping both values above 100 and below 104 will prevent all water tiles from appearing.
* Mountain peaks can only form at elevations of 400.

==== Rainfall ====
Controls the amount of rainfall in each map square/area. Setting the minimum or maximum too high or low can make the formation of certain biomes impossible. Rainfall causes it to [[rain]] more in a given area, which can have various effects. Also makes more rivers appear on the world map.

Note that if [[#Do Orographic Precipitation and Rain Shadows|orographic precipitation and rain shadows]] is on, then mountains will cause additional variance in rainfall, so (for example) rainfall below the specified minimum can occur in the shadow of a mountain. If you want the minimum and maximum for this parameter to be absolutely respected, you must turn off the orographic precipitation option.

Additionally, with 'Orthographic Precipitation' turned on, orthographic precipitation and rain shadows will only occur in regions with greater than or equal to 50 drainage. [http://www.bay12forums.com/smf/index.php?topic=139916.0 [Report, reproduced 2022]]

==== Temperature ====
{{main|Climate|Temperature}}
These parameters control how hot or cold various areas will be. If you lower the minimum and maximum values, the world will be colder overall, for example. As with the others, changing these values too much could make it impossible for certain biomes to exist. The temperature scale used in this setting is related to regular degrees Urist by the equation "local temp = world temp * 0.75 + 10000".{{cite forum|169696/8395484}} This scale doesn't seem to be used anywhere else in the game. See [[Climate]] for more info.

These parameters form the "base" temperature for an area, and describe peak summer temperature in a scale that isn't used elsewhere in the game. This number also does not correspond 1:1 with the final climate. [[Temperature]] is always influenced by a number of variables, including elevation, time of year, thick forestation, and if [[Advanced_world_generation#Poles|poles]] are enabled, latitude. These other variables are factored in after the temperature mesh is applied, and frequently bring temperatures above and below their set minimum and maximum values. ''The inclusion of Poles is particularly strong in this regard, as it allows latitude to raise and/or lower temperatures by more than 75 degrees Celsius! That said, the temperatures aren't raised or lowered by more than about 65 degrees past the set minimum and maximum. Furthermore, for typical ranges, the temperature will never be raised more than about 25 degrees past the maximum (but will still drop up to about 65 degrees Celsius below the minimum).'' (unsure about exact values, research needed)

Elves can spawn where the temperature is 10 degrees or warmer, and humans can spawn where the temperature is 0 degrees or warmer.

==== Drainage ====
Changing drainage parameters will change the way water-affected biomes are formed. Low drainage will contribute to the formation of [[Lake|lakes]], [[River|rivers]], and [[Swamp|swamps]]. High drainage will cause water to sink into the ground rather than sit on the surface, which is important for forming hills.

Lower drainage values have been reported to contribute to the formation of thicker soil layers, though it is currently unknown exactly how other factors (such as elevation or perhaps rain) impact soil formation.

==== Volcanism ====
Volcanism controls the occurrence of igneous [[layer]]s, and the formation of volcanoes. For a volcano to form, a square must have a volcanism value of 100, so reducing the maximum from 100 will make volcanoes impossible. Raising the minimum will increase the rarity of non-igneous layers.

Setting the minimum to a high value is not a good way to produce multiple volcanoes, as you are likely to get a "Volcanism not evenly distributed" rejection. Instead, use the Minimum Number of Volcanoes parameter, and possibly adjust the weighted ranges for volcanism as described below.

==== Savagery ====
These parameters control the level of [[Surroundings#Savage|savagery]] on the map. Raising the minimum savagery too high may make it impossible for certain races to exist, and similarly lowering the maximum too far can make it impossible for certain creatures to exist. The largest chance of having unusable maps comes from a too-high savagery value.

==== Configuration Tokens ====
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[ELEVATION:1:400:401:401]</nowiki></tt>
| Range: 0 to 400 Maximum of 400 required for mountain peaks. Variance range: 0-3200
|-
| <tt><nowiki>[RAINFALL:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[RAINFALL:0:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|-
| <tt><nowiki>[TEMPERATURE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE:25:75:200:200]</nowiki></tt>
| Range: -1000 to 1000 Variance range: 0-3200
|-
| <tt><nowiki>[DRAINAGE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE:0:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|-
| <tt><nowiki>[VOLCANISM:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM:1:100:200:200]</nowiki></tt>
| Range: 0 to 100 Maximum of 100 required for volcanoes. Variance range: 0-3200
|-
| <tt><nowiki>[SAVAGERY:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY:1:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|}

=== Terrain Mesh Sizes and Range Weights ===
[[File:World_map-large-32x32-elevation-mesh.png|thumb|300px|A large world generated with an Elevation Mesh Size of 32×32 and range weights set to 1:0:0:0:1 (i.e., only extreme high and low elevations). Note how the grid intersections are either set very high (mountains) or very low (oceans) and the space between them is smoothed out.]]
These parameters influence the relative proportions of terrain feature ranges, without making other ranges impossible. For example, to have many more low-elevation squares exist, without making it impossible for high elevations; this makes changing these parameters often preferable to simply changing the above min/max values. See the image on the right for an example.

The basic steps of applying weighted ranges are as follows:
# Divide the world into a grid of quantity <code>2''MeshSize'' - 1</code> areas in both X and Y direction.
# At each grid intersection, set the value according to the weighted ranges.
# Smooth out the areas between the intersection points.
# Add noise according to the variance parameters.
Where ''MeshSize'' is the raw parameter value found in the <code>[[world_gen.txt]]</code>.

==== Interaction between Mesh Size and Weighted Ranges ====
Mesh size determines how many intersection points the world will have. As an example, setting it to 2×2 means the world will divided into 4 areas, 2 across and 2 tall, and there will be a total of 9 intersection points (3×3). The grid intersection points are in the middle of world tiles, and the minimum size for a grid area is a span of 9×9 world tiles, with adjacent areas sharing an overlapping world tile. On a pocket world, this means one grid tile will span 9×9 world tiles, whereas on a large world, one grid tile will span 129×129 world tiles. A pocket world will always use a 2×2 grid areas of 9×9 world tiles, since it has only 17×17 tiles total (even if the game UI allows setting those worlds to a 4×4 grid, which can happen when changing the world size; changing the world size doesn't adjust mesh size limits, but saving then reloading the parameters does).

Setting mesh size to something other than Ignore, will apply random values at those intersections, with those random values being more likely to be in the higher weighted ranges. Setting to Ignore will cause the weighted range settings to be ignored for that terrain characteristic; instead setting the 4 corners of the world to completely random values and smoothing between those.

For example, if the Elevation Weighted Range parameters are set to <code>60:10:10:10:10</code> (starting with the 0-20 range, and these values do not have to add up to any particular number), and elevation min and max are left at the defaults of 1 and 400 respectively, then about 60% (on average) of the grid line intersection points will be set to an elevation in the range of 1-80 (0% to 20%), and the other ranges will be represented by around 10% of the intersection points each. The exact distribution is still left up to chance, though ''on average'' it will be close to this specification. This allows random number generation to be non-linear for the given terrain characteristic.

Setting the weight for a range to None only prevents intersection points from being set to a value in that range; terrain between intersection points can still be smoothed to values in ranges set to None that are between the intersection point values.

Weighted ranges do not make rejection checks, although they can be responsible for many rejections if you neglect to adjust or disable some of the [[#Minimum Number of Mid/Low/High Characteristic Squares|Minimum Number of Mid/Low/High Characteristic Squares]], for example.

==== Interaction between these and Variances ====
The end result can vary greatly depending on how the corresponding [[#X_and_Y_Variance|X and Y Variance]] parameters are set. First of all, if the variance is too high, the noise it adds can completely negate the effect of the weighted ranges. For instance, with a 2×2 mesh, the default variance parameters are high enough that usually the mesh grid can hardly be recognized. How strong the variance's effect is, is also dependent on the mesh size. Having a larger mesh size (i.e. smaller grid tiles) means the variance also has to be higher for a visible effect. For instance, with a variance of 400, the effects are clearly visible with a 2×2 mesh and barely visible at all with a 8×8 mesh. Note that this effect is directly dependent on the mesh size and not, as one might expect, on the actual size of the grid tiles. This means, that a large world with a 32×32 mesh will look essentially the same as a pocket world with a 2×2 mesh, only stretched to 256 times the size.

Also see this [http://www.bay12forums.com/smf/index.php?topic=139916.0 forum post] for more details.

==== Configuration Tokens ====
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[ELEVATION_FREQUENCY:2:1:2:3:4:5]</nowiki></tt>
| rowspan="6" | Valid mesh values:

1 = Ignore

2 = 2x2

3 = 4x4

4 = 8x8

5 = 16x16

6 = 32x32

(limited by world size)
|-
| <tt><nowiki>[RAIN_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[RAIN_FREQUENCY:3:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[DRAINAGE_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE_FREQUENCY:4:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[TEMPERATURE_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE_FREQUENCY:1:1:1:1:1:1]</nowiki></tt>
|-
| <tt><nowiki>[SAVAGERY_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY_FREQUENCY:5:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[VOLCANISM_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM_FREQUENCY:1:1:1:1:1:1]</nowiki></tt>
|}

=== Poles ===

With this, you can influence how polar regions are added. The poles can be on the north or south edge, and the equator will be on the opposite edge, or in the middle if there are two poles. If poles are set to NONE, then there will be no seasonal changes in the weather (e.g. no winter snow in temperate biomes).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[POLE:<placement>]</nowiki></tt>
| <tt><nowiki>[POLE:NORTH]</nowiki></tt>
| Viable options: NONE, NORTH_OR_SOUTH, NORTH_AND_OR_SOUTH, NORTH, SOUTH, NORTH_AND_SOUTH
|}

=== Minimum Mountain Peak Number ===

This will cause the world to be rejected if fewer than this many peaks (based on elevation) are present on the map. EG: elevations of 400 must be possible for mountain peaks to occur. If set to zero, then worlds will not be rejected based on number of peaks.

You may need to adjust elevation parameters, such as the highest weighted range, in order to get the desired number of elevation-400 squares needed for larger numbers of peaks. Like volcanoes, mountain peaks can make embark zones more interesting, but other than that, they don't appear to "do" anything special. Reportedly, they do increase the highest Z-level above ground in all embark zones in the same region, even if the selected embark zone does not include the peak.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PEAK_NUMBER_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[PEAK_NUMBER_MIN:20]</nowiki></tt>
| Elevations of 400 must occur for peaks to form.
|}

=== Minimum Partial Edge Oceans ===

This will cause a world to be rejected unless there are at least this many oceans touching an edge of the map. If set to zero then worlds will not be rejected based on this criterion. Setting both this parameter and Minimum Complete Edge Oceans to values that total more than 4 when added together may cause all worlds to be rejected as you can't have both a partial and complete edge ocean on a given edge.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PARTIAL_OCEAN_EDGE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[PARTIAL_OCEAN_EDGE_MIN:2]</nowiki></tt>
| Maximum of 4
|}

=== Minimum Complete Edge Oceans ===

This will cause a world to be rejected unless there are at least this many oceans which completely cover an edge of the map. Since a square map only has 4 edges, the maximum value possible is 4. If set to zero then worlds will not be rejected based on this criterion but still might end up with complete edge oceans by chance.

Note that the ability for this many edge oceans to exist will be limited by elevation. Therefore, to actually create large oceans you will probably need to change things like the Elevation Mesh Size and Weighted Ranges to increase the number and distribution of very low elevation squares on the map. In addition, if Complete Edge Oceans is set to any value ''other'' than 0 or 4, you may need to lower elevation variance for at least one of the axes: if set too high, such as a variation of 1600 for both X and Y axes (the default for Large Island and Medium Island parameter sets), the game may generate worlds very slowly or even hang.{{bug|565}}

Given appropriate weight, range, and variance values for things like elevation, a setting of: 1 results in a world that seems like a chunk of coastline. One edge of the map will be completely underwater and there will be ocean taking up much of the map on that side (think the east or west coast of the United States, the north coast of Canada, or southern Europe). If your edge ocean happens to pick your world's frozen side, most of it will be glacier.

*2 results in another coastline along with the first one -- the map could end up looking something like Panama if the oceans pick opposite sides of the map.
*3 results in a peninsula, like Florida in the US. There will be oceans surrounding 3 sides of the map, and land touching only one side of the map.
*4 results in one or more island(s) depending on things like elevation variance and weights. Regardless of whether you get one island or multiple islands, the entire map will be surrounded by water.

Unfortunately, there's no easy way to control which oceans end up on which edges, except perhaps setting X/Y variance to different values.

Edge oceans will take up part of the other edges too. For example, a full edge ocean on the east side will have part of the north and south sides underwater, but that does ''not'' add to the ''partial'' edge oceans count.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[COMPLETE_OCEAN_EDGE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[COMPLETE_OCEAN_EDGE_MIN:0]</nowiki></tt>
| Maximum of 4
|}

=== Minimum Volcano Number ===

The game will attempt to place this many volcanoes, but there must be at least this many squares with a volcanism of 100, if there are not the world will be rejected. Therefore, [[Advanced_world_generation#Volcanism|maximum volcanism]] above must be set to 100, and adjusting the [[Advanced_world_generation#Configuration_Tokens_2|volcanism weighted range]] above for 80-100 to a higher value can increase the number of those squares.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[VOLCANO_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[VOLCANO_MIN:15]</nowiki></tt>
| Volcanoes require a volcanism of 100 to occur.
|}

=== Mineral Scarcity ===
Controls the frequency at which minerals occur; setting this value higher will decrease both the number of different types and amounts of ore and gems present on a map. The default value will result in many metal ores, while the old default of ''sparse'' would be only a few ores, which may be limiting until other metals can be requested and traded for.

The options "Very Rare", "Rare", "Sparse", "Frequent", and "Everywhere" in the [[World_generation#Basic_world_generation_menu|basic world generation menu]] use the values 50000, 10000, 2500, 500 and 100 respectively.

According to [http://www.bay12forums.com/smf/index.php?topic=79018.msg2063804#msg2063804 research] by Shandra in v0.31.25, this is the relationship between the value of this setting and the approximate number of gems and ore:

[[File:MineralSetting_v25_limit10k.png]]

This is for the same 8x8 embark region in a world which is otherwise the same, except for the mineral scarcity parameter (although most of the detailed information comes from experiments with previous versions). (The chart legend has an error, the first "Pot.(Types)" should read "Pot.(Amount)".)
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MINERAL_SCARCITY:<number>]</nowiki></tt>
| <tt><nowiki>[MINERAL_SCARCITY:100]</nowiki></tt>
| Range: 100 to 100,000
|}

=== Max Megabeast Caves ===

This is the number of [[megabeast]]s placed at the beginning of history. Megabeasts are [[hydra]]s, [[bronze colossus]]es, [[roc]]s, and [[dragon]]s, which are all placed in equal proportions [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415177#msg3415177 data].

Increasing this value can lead to early extinction of civilizations.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[MEGABEAST_CAP:75]</nowiki></tt>
| Megabeasts count towards BEAST_END_YEAR calculation.
|}

=== Max Semi-Megabeast Caves ===

This is the number of [[semi-megabeast]]s placed at the beginning of history. Semimegabeasts are [[giant]]s, [[ettin]]s, [[minotaur]]s, and [[cyclops]], which are placed in equal proportions [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415188#msg3415188 data].

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEMIMEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SEMIMEGABEAST_CAP:150]</nowiki></tt>
| Semimegabeasts do not count towards the BEAST_END_YEAR calculation.
|}

=== Titan Parameters ===

==== Number ====

This controls the number of [[titan]]s that exist at the beginning of history[http://www.bay12forums.com/smf/index.php?topic=112465.msg3415203#msg3415203 data]. The number of forgotten beasts is unaffected by this parameter [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415155#msg3415155 data].

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TITAN_NUMBER:33]</nowiki></tt>
| Titans count towards BEAST_END_YEAR calculation.
|}

==== Attack Population Requirement ====

[[Titan]]s will begin to attack your fort once at least this many dwarves inhabit it, regardless of whether any other attack criteria have been met.

This number defaults to 80, which isn't usually too difficult to deal with.

==== Exported Wealth Requirement ====

Titans will begin to attack your fort once you have exported at least this many [[Currency|dwarfbucks]]-worth of goods, regardless of whether or not any other criteria have been met. This parameter defaults to None (disabled).

==== Created Wealth Requirement ====

Titans will begin to attack your fort once the fort's total wealth has reached this many [[Currency|dwarfbucks]] in value. This happens regardless of whether any of the other criteria, such as population, have been met; therefore, even with 1 dwarf, a fort could be attacked if the fort were worth at least this value.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_ATTACK_TRIGGER:<population>:<exp wealth>:<created wealth>]</nowiki></tt>
| <tt><nowiki>[TITAN_ATTACK_TRIGGER:80:0:100000]</nowiki></tt>
| 0 = None (disabled). Only one requirement must be met for an attack.
|}

=== Number of Demon Types ===

[[Demon]]s are similar to [[titan]]s and [[forgotten beast]]s, in that they are procedurally generated, but most are not unique. Thus, many different types of demons can exist in the world, but there will also be many individuals of most types. Thanks to [[Underworld spire|certain fun things]], fewer demon types also means fewer goblin civilizations.{{cite forum|112465/7392706}} You need at least 2 demon types, or else goblin civilizations won't exist initially, though if dwarves breach the underworld during world generation, at least one will be generated then.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DEMON_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[DEMON_NUMBER:52]</nowiki></tt>
| 0 to 1000
|}

=== Number of Night Troll Types ===

The number of different [[night troll]]s, also procedurally generated, that will exist in the world. Setting this to zero means that the world will have no night trolls, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[NIGHT_TROLL_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[NIGHT_TROLL_NUMBER:77]</nowiki></tt>
| 0 to 1000
|}

=== Number of Bogeyman Types ===
The number of different [[bogeyman]] forms that will exist in the world. Bogeymen are procedurally generated, though their forms do not vary by much. Setting this to zero means that the world will have no bogeymen, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[BOGEYMAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[BOGEYMAN_NUMBER:27]</nowiki></tt>
| 0 to 1000
|}

=== Number of Nightmare Types ===
The number of different [[nightmare]] forms that will exist in the world. Nightmares are procedurally generated. Setting this to zero means that the world will have no nightmares, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[NIGHTMARE_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[NIGHTMARE_NUMBER:27]</nowiki></tt>
| 0 to 1000
|}

=== Number of Vampire Curse Types ===

The number of different types of [[Vampire|vampires]] that will exist in the world. Although they are generated at the start of a new world, they aren't different from each other. Setting this to zero means no vampires will exist.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[VAMPIRE_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[VAMPIRE_NUMBER:72]</nowiki></tt>
| 0 to 1000
|}

=== Werebeast Parameters ===

==== Number of Werebeast Curse Types====

The number of different types of [[werebeast]]s that can exist in the world. It is common for werebeasts, unlike vampires, to assume many different forms and variations, the most well-known of these amount to different species of animals, from lizards, to wolves, to even bears. Setting this to zero means no werebeasts will exist, and will also remove a large amount of [[fun]] from the game.

In vanilla, there are only 82 possible unique werebeast species. Any further species will generate as wereblobs.{{bug|13308}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[WEREBEAST_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[WEREBEAST_NUMBER:58]</nowiki></tt>
| 0 to 1000
|}

==== Attack Population Requirement ====

Werebeasts will begin to attack your fort once at least this many dwarves inhabit it, regardless of whether any other attack criteria have been met. This number defaults to 50 which will often be reached in the second year of the fort.

==== Exported Wealth Requirement ====
Werebeasts will begin to attack your fort once you have exported at least this many [[Currency|dwarfbucks]]-worth of goods, regardless of whether or not any other criteria have been met. This parameter defaults to 5000.

==== Created Wealth Requirement ====

Werebeasts will begin to attack your fort once the fort's total wealth has reached this many [[Currency|dwarfbucks]] in value. This happens regardless of whether any of the other criteria, such as population, have been met; therefore, even with 1 dwarf, a fort could be attacked if the fort were worth at least this value.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[WEREBEAST_ATTACK_TRIGGER:<population>:<exp wealth>:<created wealth>]</nowiki></tt>
| <tt><nowiki>[WEREBEAST_ATTACK_TRIGGER:50:5000:50000]</nowiki></tt>
| 0 = None (disabled). Only one requirement must be met for an attack.
|}

=== Number of Secret Types ===

The number of secrets that exist in the world. Currently, all secrets are secrets of life and death, and the ones holding these secrets are [[necromancer]]s, thus, setting this to zero means that no necromancers will appear.
Non-necromancer towers can still appear (extremely rarely) with zero secrets, constructed by independent undead groups.
The primary difference between having 1 or 1000 secrets is the chance of your world having any necromancer towers at all. With 1, this chance is low. With the default number, it's seemingly guaranteed.
Even with 1 secret, if you have any necromancer towers at all, it is likely a great number will quickly appear in world generation (though this isn't guaranteed).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SECRET_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[SECRET_NUMBER:52]</nowiki></tt>
| 0 to 1000
|}

=== Number of Regional Interaction Types ===

The number of interactions that can be caused in regions, which may incorporate evil rain and cloud types. Currently, only evil region interactions are generated this way.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[REGIONAL_INTERACTION_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[REGIONAL_INTERACTION_NUMBER:20]</nowiki></tt>
| 0 to 1000
|}

=== Number of Disturbance Interaction Types ===
The number of different [[Mummy|disturbed dead]] that can exist in the world. Setting this to zero should prevent any mummy from appearing{{verify}}, but it will not prevent the creation of [[tomb]]s.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DISTURBANCE_INTERACTION_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[DISTURBANCE_INTERACTION_NUMBER:10]</nowiki></tt>
| 0 to 1000
|}

=== Number of Evil Cloud / Evil Rain Types ===

This number specifies how many [[Weather#Evil weather|various face-melting, eye-boiling, and zombifyingly-fun]] clouds of pure evil may appear in your world. Setting this to zero means you no longer will ever have to deal with encroaching dust walls of doom in that world. It is generally advised to keep this value low...

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EVIL_CLOUD_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[EVIL_CLOUD_NUMBER:45]</nowiki></tt>
| 0 to 1000
|}

The latter number states how many different types of green-ooze drenchers, disconcerting blood-showers, and sickly yellow slime-baths can occur in your world. Compared to evil clouds though, this one hardly is worth stressing out about, usually.... Setting this to zero means the only semi-solid to fully-liquid fluids to fall from the sky will be pure H2O.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EVIL_RAIN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[EVIL_RAIN_NUMBER:352]</nowiki></tt>
| 0 to 1000
|}

=== Generate Divine Materials ===
This turns the generation of [[Divine_metal|divine metals]] on or off. It does not influence the creation of [[vault]]s. Probably determines whenever or not using divination dice spawns weapons.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GENERATE_DIVINE_MATERIALS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[GENERATE_DIVINE_MATERIALS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Generate Mythical Materials ===

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GENERATE_MYTHICAL_MATERIALS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[GENERATE_MYTHICAL_MATERIALS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Mythical Healing ===

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALLOW_MYTHICAL_HEALING:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_MYTHICAL_HEALING:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Divination, Experiments, and Necromancy types ===
These allow or disallow [[die|divination]], demon or necromancer [[experiment]]s, and the more advanced [[necromancer]] abilities.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALLOW_DIVINATION:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_DIVINATION:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_DEMONIC_EXPERIMENTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_DEMONIC_EXPERIMENTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_EXPERIMENTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_EXPERIMENTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_LIEUTENANTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_LIEUTENANTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_GHOULS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_GHOULS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_SUMMONS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_SUMMONS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Desired Good/Evil Square Counts ===

These values change the amount of [[Surroundings#Good|good or evil]] tiles on the map, depending on the size of the region they are being considered for. The counts are for all tiles in all subregions of a given size considered together, ''not'' counts for each subregion considered separately (all tiles in the same subregion share the same [[surroundings]] values).

As used here, a "subregion" is a named world area. Subregion names and locations for a generated world are viewable in legends mode under "Regions". Subregions are classified by size the same way for all map sizes: 1-24 tiles is Small, 25-99 tiles is Medium, and 100+ tiles is Large.

The counts used here will always be restricted to regions of the given size, no matter how large the count. Also, the count is more of a goal than a minimum or maximum. As a result, you can end up with many more or many fewer than the requested number of squares in some situations. In particular, if you have something like a case where only 3 large regions exist in a world, and you request "1 evil square" in large regions, you will end up with one of the large regions being ''entirely evil''. So any non-zero value in one of these settings essentially means "force at least one region of this size to be all good/evil."

Note that the "evilness" of evil biomes is also impacted by savagery. Certain civilizations cannot exist in good and/or evil squares, so too many of one or the other may limit the size of certain types of civilizations - dwarves, for example, need non-aligned biomes. Creating too many evil biomes seems to lead to the danger of many civilizations' early extinction.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GOOD_SQ_COUNTS::<med region>:<lg region>]</nowiki></tt>
| <tt><nowiki>[GOOD_SQ_COUNTS:100:1000:2000]</nowiki></tt>
| rowspan="2" | Set count to zero to disable for that region size.
|-
| <tt><nowiki>[EVIL_SQ_COUNTS::<med region>:<lg region>]</nowiki></tt>
| <tt><nowiki>[EVIL_SQ_COUNTS:100:1000:2000]</nowiki></tt>
|}

=== Minimum Biome Square Counts ===

These numbers control whether or not a world will be rejected based on a lack of different [[biome|biomes]]. Raising these numbers will '''not''' automatically generate the given number of squares of the given biome! For a biome to exist, certain conditions like elevation and rainfall must exist.

These parameters simply filter out worlds that (for example) randomly fail to have enough high elevation squares to support a given number of mountains, etc. Some settings may cause worlds to always be rejected. For example, if for some reason the maximum elevation parameter is set to a value below what will support mountain biomes, it will be impossible to satisfy a non-zero requirement for mountain squares. The same principle goes for other conditions and biomes such as low elevations and oceans, etc.

Certain civilizations require different biomes to exist (such as dwarves and mountains), so eliminating certain biomes will make it impossible for certain civilizations to form.

These parameters often result in infinite world rejection problems. See [[World rejection]] for information on solving problems related to worlds always being rejected due to one or more of these parameters.

0 means no minimum for rejection - setting it to 0 does not guarantee 0 squares of that biome.

==== Biome Type Requirement Table ====

Terrain requirements for various biomes are described below.{{Verify}} Note that some of the exact ranges are unknown.

{| {{prettytable}}
|- bgcolor="#dddddd"
! rowspan="2" | Biome
! colspan="4" | Terrain Requirement
|-
! Elevation
! Rainfall
! Temperature
! Drainage
|-
| Swamp/Marsh
| 100-299
| 33-100
| Non-Freezing
| 0-32
|-
| Desert/Badland
| 100-299
| 0-9
| non-freezing
| note1
|-
| Forest
| 100-299
| 66-100
| non-freezing
| 66-100
|-
| Mountains
| 300-400
| N/A
| N/A
| N/A
|-
| Ocean
| 0-99
| N/A
| N/A
| N/A
|-
| Glacier
| 100-299
| N/A
| Freezing
| 80(?)-100
|-
| Tundra
| 100-299
| N/A
| Freezing
| 0-66
|-
| Grassland
| 100-299
| 0-66
| Non-Freezing
| 0-66
|-
| Hills
| 100-299
| 0-66
| Non-Freezing
| 66-100
|}
note1 drainage: 00-32 sand desert, 33-49 rocky wasteland, 50-65 rocky wasteland but different characters/appearance, 66-100 badlands

==== Minimum Initial Square Count ====

'''Note: The exclusive purpose of these parameters is to cause world rejection.'''

This is the minimum number of squares of the given biome that must exist before things like erosion take place. One thing to keep in mind is the maximum number of squares on a map of a given size - if the total number of squares on a map is lower than the sum of all square count parameters, then you will get infinite world rejection.

To determine the number of squares on a map, just multiply the dimensions. In practice these parameters will need to sum to lower than the maximum because some space is needed for "slack".

{| {{prettytable}}
|- bgcolor="#dddddd"
! Map Size
! Number of Squares
|-
| 17×17
| 289
|-
| 33×33
| 1089
|-
| 65×65
| 4225
|-
| 129×129
| 16614
|-
| 257×257
| 66049
|}

==== Minimum Initial Region Count ====

This is the minimum number of regions of contiguous biome squares that must exist before other processes such as erosion take place.

==== Minimum Final Region Count ====

This many regions of the given biome must exist after erosion and similar phases of generation have been completed.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[REGION_COUNTS:SWAMP:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:SWAMP:1032:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:DESERT:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:DESERT:1032:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:FOREST:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:FOREST:4128:13:12]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:MOUNTAINS:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:MOUNTAINS:8256:9:9]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:OCEAN:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:OCEAN:8256:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:GLACIER:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:GLACIER:0:0:0]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:TUNDRA:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:TUNDRA:0:0:0]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:GRASSLAND:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:GRASSLAND:8256:13:12]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:HILLS:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:HILLS:8256:13:12]</nowiki></tt>
|}

=== Erosion Cycle Count ===

Tells the world generator how long the world has to erode its tall peaks down to mountainsides during the 'running rivers...' stage of world creation. The higher this number, the less jagged the world will be, and the more wide the major rivers will be. If you use the maximum number, your mountains will dissolve before your eyes into plains which can lead to rejections if there aren't enough mountains to use for river start points and dwarven civilization origin points.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EROSION_CYCLE_COUNT:<number>]</nowiki></tt>
| <tt><nowiki>[EROSION_CYCLE_COUNT:250]</nowiki></tt>
| Range: 0 to 1000
|}

=== Minimum/Desired River Start Locations ===

This is the minimum number of riverheads that must exist before and after erosion takes place. Worlds will be rejected if they fail to meet these numbers. As with minimum biome counts, raising this number doesn't automatically create this many riverheads. Other conditions like terrain and rainfall must exist for rivers to form.

Extremely high pre-erosion values speed erosion greatly, while low post erosion values are useful for limiting rejects due to lack of river origin points. One can try the 800 value to get more lakes.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[RIVER_MINS:<min pre-erosion>:<des post-erosion>]</nowiki></tt>
| <tt><nowiki>[RIVER_MINS:200:400]</nowiki></tt>
| Range: 0 to 800
|}

=== Periodically Erode Extreme Cliffs ===

If enabled, makes every impassable rock wall into a series of ramps. Some prefer to pump up erosion to about 250, and turn the "Desired pre-erosion river count" to 0 for good erosion and no extra canyons.

Normally this is set to Yes (1).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PERIODICALLY_ERODE_EXTREMES:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[PERIODICALLY_ERODE_EXTREMES:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Do Orographic Precipitation and Rain Shadows ===

Toggle that allows terrain height to affect rainfall. For example, moist air coming from the ocean blows over the land. As the terrain gets higher, it forces the moist air up, causing it to rain on the seaward side of a mountain. Eventually, all the rain has fallen if the mountain is tall enough. So, when the breeze goes over the top, there's no moisture left to fall on the other side, creating a rain-shadow. In the current version, regions where drainage is above 50 will also create rain shadows, regardless of the underlying biome and elevation.{{cite forum|140685/5484064}}

Turning this on should create a tendency for more extreme rainfall in regions, creating more forests, deserts, marshlands, and grasslands. Also note that it can create rainfall outside of min-max rainfall settings, so even in a world with a 0 max rainfall you may get rainfall biomes. Turning it off should result in more controllable, less complex rainfall conditions based on rainfall parameters as it adds a random element which can distort or otherwise mess up the climates on a pregenerated map.

This should be disabled if you're importing a map or using a preset map file that has weather.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[OROGRAPHIC_PRECIPITATION:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[OROGRAPHIC_PRECIPITATION:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Maximum Number of Subregions ===

This is the number of separate biomes (the flashing regions you see on embark when you hit F1, F2, etc. when there's more than one biome on the embark location) that are allowed to exist on the entire map.

Setting this to very low values will result in numerous rejections depending on [[#X and Y Variance|variance parameters]]. If variance values are set to high numbers, many small biomes will be created causing rejection if this parameter value is not increased beyond the default.

Increasing the value of this tag is often a must when generating "patchwork" worlds with lots of biome variance, but simply increasing it without increasing variance parameters will not guarantee more biomes.

It is also interesting to note that the maximum subregions is 5000 which is more than the total number of squares for a pocket or small map. However, for a medium or large map (16641 or 66049 squares) it quickly becomes a mere fraction of the total number of possible subregions. In fact it would be quite easy on a large map to end up with far too many subregions and get endless rejections of this type.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SUBREGION_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[SUBREGION_MAX:2750]</nowiki></tt>
| Range: 1 to 5000
|}

=== Cavern Parameters ===
[[Caverns]] are the hollow areas underground, which dwarves tend to encounter when they're digging around. The '''Cavern Layer Number''' parameter determines how many cavern systems will be generated, not including the magma layer or the Bottom layer. Defaults to three - setting it to lower values could help FPS. Setting it to 2 will merge cavern 3 species into the 2nd cavern, and setting it to 1 will merge all into one cavern. However, disabling them entirely by setting it to 0 will make it impossible to grow any underground plants, as none will exist for your civilization to cultivate, nor will they be available on embark.

*Setting caverns to a sub-3 number (Spoiler, highlight to view) erases about one-third of HFS spires{{Bug|10267}} and prevents dig deep disasters. Additionally, random plant or animal species can be more frequently absent.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_COUNT:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_COUNT:3]</nowiki></tt>
| Range: 0 to 3
|}

==== Cavern Layout Parameters ====

Open caverns and dense passageways are not mutually exclusive. When both are raised, bizarre results can occur, such as layers showing a combination of open caverns, a cluster of network passages, and natural walls sprinkling the inside of an otherwise open cavern. [http://www.bay12forums.com/smf/index.php?topic=76355.msg1936859#msg1936859 Reference]

If you want the largest open spaces possible, then decrease the density and increase the openness. If you want a labyrinth of passageways, lower the openness and raise the passage density.

Another interesting note about the cavern layers is that the seed and number of demon types affect the layout of the caverns.

<gallery widths=200 heights=200 perrow=2>
File:Open00Density100.jpg|Cavern slice with Openness of 0 and Density of 100
File:Open100Density00.jpg|Cavern slice with Openness of 100 and Density of 0
File:Open100Density100.jpg|Cavern slice with Openness of 100 and Density of 100
File:Open50Density50.jpg|Cavern slice with Openness of 50 and Density of 50
</gallery>

===== Layer Openness min/max =====

Dictates the size of cavern passages. When Passage Density (see below) is set to minimum (0), caverns will be open expanses. Raising the maximum will increase the size of the caverns.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MAX:100]</nowiki></tt>
|}

===== Layer Passage Density min/max =====

Determines how many passages form the cavern. If openness (see above) is set to minimum and density increased, then you will get a maze-like network of small criss-crossing passages. Raising the values further increases the number of the maze-like passages.

Caverns will be large, open spaces at 0, and comprised of many small vertical shafts of rock at 100. Setting both values to be the same results in a uniform look for the caverns.{{Verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MAX:100]</nowiki></tt>
|}

===== Layer Water min/max =====

Determines the minimum and maximum percentage of water each cavern can contain.

Caverns with a water level of 10 or higher can support creatures and plants from the "Subterranean Water" biome, and caverns with a water level of 90 or lower can support the "Subterranean Chasm" biome; levels of 10-90 support ''both'' biomes, while levels below 10 or above 90 support only one.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_WATER_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_WATER_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_WATER_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_WATER_MAX:100]</nowiki></tt>
|}

==== Magma Layer ====

This parameter controls whether the [[magma sea]] exists.

Setting 1/Yes causes the magma layer to exist, value 0/No prevents it. Appears not to have any impact on volcanoes nor volcanism, so even if 0/No, there will still be embark locations with magma. If a [[volcano]] exists, it appears to always tap the magma sea, but the magma sea will not be revealed by revealing the volcano.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[HAVE_BOTTOM_LAYER_1:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[HAVE_BOTTOM_LAYER_1:1]</nowiki></tt>
|}

==== Bottom Layer ====

Determines if the space below the magma sea exists. If Yes the "HFS" layer is always present. Normally you want to leave this set to Yes for maximum fun.

If enabled, this will force the magma layer above it.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[HAVE_BOTTOM_LAYER_2:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[HAVE_BOTTOM_LAYER_2:1]</nowiki></tt>
|}

=== Z Levels (Depth) Settings ===

These parameters control the "thickness" of various "layers" on the map. Note that a "layer" in this case does not refer to one Z-level, but refers to a number of related Z-levels such as "levels above ground".

The following table assumes that you have 3 cavern layers. (out of a minimum of 0-3) The Levels Above Layer settings control how many Z-Levels are above each layer. A layer may itself consist of multiple Z-Levels (and almost always does).

{|style="margin:1em 1em 1em 0;background:#F9F9F9;border:1px #AAA solid;border-collapse:collapse;" class="wikitable"
|-style="background:#F2F2F2;text-align:center;"
!style="border:1px #AAA solid;padding:0.2em;" width="120"|Setting Name
!style="border:1px #AAA solid;padding:0.2em;" width="200"|Token
!style="border:1px #AAA solid;padding:0.2em;"| Description
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Ground
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_GROUND:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| The number of Z-levels of air above the highest surface level. Has no impact on how many Z-levels deep the surface layer is.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above layer 1
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_1:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of stone above the first cavern layer. Making this higher will guarantee ''at least'' that many levels to build your fortress, but will have no impact on how many z-levels thick the surface layer is. Also, the top of a cavern may be higher than the rest of a cavern, so in practice there will be more "solid" levels than this above the cavern.
As of version 0.31.25 this setting is inaccurate. The actual number of z-levels may vary in a range of approx. ±5, which may result in non-existence of any solid z-levels between a surface layer and first cavern layer.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 2
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_2:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very top of the second cavern and the very bottom of the first cavern.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 3
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_3:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very top of the third cavern and the very bottom of the second cavern.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 4
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_4:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very highest magma and the very bottom of the third cavern. Spoiler Hidden (select invisible text to read): Making this high will give a large area for HFS veins, so that it never touches caverns, giving more to mine '''if''' it was impacting the cavern previously.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 5
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_5:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Uncertain. May control the number of levels of "Semi Molten Rock" between HFS and Magma, may control number of levels of magma, may impact both. In experimentation, the overall depth of all magma sea and semi-molten rock levels appears to increase, but not consistent enough to say for certain. Only valid if Magma Layer present. Spoiler Hidden:Often the HFS vein will only extend as high as the highest magma, making this the only guaranteed way to increase amount of HFS to mine, but unfortunately also creating enormous useless semi-molten z-levels
|-
|style="border:1px #AAA solid;padding:0.2em;"| At Bottom
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_AT_BOTTOM:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Appears to be number of levels of HFS chamber. Only valid if Bottom Layer present, often having no impact. Values larger than default result in strange things.
|}

Some implications:
* The number of surface layers (e.g. soil), at this time, cannot be controlled. For example, on a map with 1 layer of peat, then a layer of silt, then a layer of obsidian, there is no control to let you increase either one to be, say, 20 z-levels. (though you may get lucky with the obsidian).
* There can be multiple stone layers between the cavern and the surface, so, increasing Levels Above Layer 1 may give you more conglomerate or more granite, and you have no control over which stone layer spans those Z-levels.
* The layers shown on embark span across the cavern layers in an unknown and inconsistent way. Sometimes those 10 different layers of stone are evenly distributed over your 400 z-level deep map, sometimes the first 9 get 1 z-level each and the last gets the other 391 levels. No way to control found yet.
* The HFS chamber, if present, will always extend into the rock layers, and appears to always make contact with the bottom cave. Large values for levels above layer 5 and layer 4 can result in enormous chambers, but the number of levels at the top (the part with undead) appears to be unaffected.
* Unconfirmed whether number of levels between caverns has any impact on cavern height. There will be connecting ramps and/or shafts between cavern layers no matter how many levels are between them.
* '''Very Important''': These values appear to apply across a whole 16x16 region, not just embark areas. That means that if a 16x16 region is completely flat, but has one tall mountain in one far corner, even if you set Levels Above Ground low (e.g. 2 z-levels) you still have all the empty air of the highest mountain in every embark tile (e.g. 200 z-levels). Also can happen to the semi-molten layer, and can lead to unexpected behavior.
* Very large or small values can cause strange things to happen.

=== Minimum/Maximum Natural Cave Size ===
It's not clear what effect these currently have, other than changing them can change the location of caves somewhat.{{verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVE_MIN_SIZE:<number>]</nowiki></tt>
| <tt><nowiki>[CAVE_MIN_SIZE:5]</nowiki></tt>
| rowspan="2" | Range: 1 to 500
|-
| <tt><nowiki>[CAVE_MAX_SIZE:<number>]</nowiki></tt>
| <tt><nowiki>[CAVE_MAX_SIZE:25]</nowiki></tt>
|}

=== Number of Caves ===
The number of caves generated in mountainous and non-mountainous regions, mountain caves will always be generated on the edge of mountain ranges next to non-mountainous regions. Lurking [[kobold]]s set up shop in caves, and store their stolen items there - a setting of 0 in both will stop kobold civilizations from appearing. Special note: a cave is not initially a [[lair]], although beasts can later use them as their lair.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[MOUNTAIN_CAVE_MIN:100]</nowiki></tt>
| rowspan="2" | Range: 0 to 800
|-
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:200]</nowiki></tt>
|}

=== Number of Mythical Sites ===
The number of [[mysterious dungeon|mysterious sites]] generated around the world. The extended effects of setting this to 0 has not been determined{{verify|is chosen still available? is quest still given? etc.}}.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MYTHICAL_SITE_NUM:<number>]</nowiki></tt>
| <tt><nowiki>[MYTHICAL_SITE_NUM:200]</nowiki></tt>
| rowspan="2" | Range: 0 to 800
|}

=== Make Caves Visible ===
If set to no (default) then the location of caves will not be marked on the map. If set to yes, caves will appear on the map so that they may be sought out or avoided as desired.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALL_CAVES_VISIBLE:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALL_CAVES_VISIBLE:0]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Init Options to Show Tunnels ===

If enabled, you will be able to see the underground tunnels often built by dwarves on the world map, and they will appear as black lines, similar to roads.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SHOW_EMBARK_TUNNEL:<0-2>]</nowiki></tt>
| <tt><nowiki>[SHOW_EMBARK_TUNNEL:2]</nowiki></tt>
| 0 = No 1 = Only in Finder 2 = Always
|}

=== Number of Civilizations ===

This number of [[civilization]]s will be placed on the map before history generation begins. These civilizations may later die out due to historical events. It is noteworthy that the chance for any given civilization to be destroyed through megabeasts decreases with a higher total number of civilizations present[http://www.bay12forums.com/smf/index.php?PHPSESSID=7348f68f41a9659443c05b2acf534e6c&topic=112465.15 data]. The five races are dwarf, elf, human, goblin, and kobold; they will generally be placed in equal numbers until the quota has been reached. If there are not enough biomes or other worldgen prerequisites for an even distribution, certain civs will be much more or less frequent than others[http://www.bay12forums.com/smf/index.php?PHPSESSID=7348f68f41a9659443c05b2acf534e6c&topic=112465.15 data]. If there is an odd number of civs (not divisible by 5), then the remainder is distributed randomly. Kobold civs require caves to be placed; if no caves exist, then kobolds are skipped and will not appear. This does not cause rejections [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415125#msg3415125 data]. Goblin civilizations require multiple demons, see the [[#Number_of_Demon_Types|number of demon types]] section above.

Note that a high value here can cause lots of map rejections, particularly on smaller maps as there simply isn't enough room or regions to put them all in.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_NUMBER:40]</nowiki></tt>
| Range: 0 to 300
|}

=== Playable Civilization Required ===

If this is set to yes (default) then worlds will be rejected if no civilization with [[Entity token|CIV_CONTROLLABLE]] can be placed. In an unmodded game, only the dwarves have this token.

If set to no, the result may be a world that cannot be played in Fortress Mode.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PLAYABLE_CIVILIZATION_REQUIRED:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[PLAYABLE_CIVILIZATION_REQUIRED:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Minimum Number of Mid/Low/High Characteristic Squares ===

Sets the minimum possible number of squares of certain ranges of each of the region qualities, such as elevation, rain, drainage, volcanism, savagery, and temperature. These need to be changed to reflect your regional meshes and weights, and are responsible for a HUGE number of map rejections. These values can all be set to 0 for much fewer map rejections, particularly in the case of more wacky, non-standard maps.

These values will cause worlds to be rejected unless at least the given number of squares of the given type are randomly generated. Setting these values too high could result in worlds always being rejected if other parameters such as the maximum/minimums for elevation, etc., don't allow enough of those squares to get generated.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[ELEVATION_RANGES:8256:16512:8256]</nowiki></tt>
| rowspan="5" | Minimum number of squares that must have low, medium, and high amounts of the given attribute. 
0 = No minimum
|-
| <tt><nowiki>[RAIN_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[RAIN_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[DRAINAGE_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[SAVAGERY_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[VOLCANISM_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM_RANGES:8256:16512:8256]</nowiki></tt>
|}

==World rejection==

:''Main article: [[World rejection]]''

If you are having the common problem of generated worlds always being rejected by the world generator, see [[v0.31:World rejection|Solving World Rejection Problems (v0.31 page)]] as it contains many detailed suggestions on how to troubleshoot and solve these issues.

== Parameter set examples ==

If you're trying to do something specific, then the [[Worldgen examples]] - complete parameter sets that can be copied directly into your ''world_gen.txt'' file and customized as desired - might be helpful.
If none of the examples suit your needs, [[Worldgen tricks]] has strategies and tips on making a world just right for you.

For many, many more examples see:
* [http://www.bay12forums.com/smf/index.php?topic=101280 DF2012 (v0.34) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=140180 DF2014 (v0.40) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=168543.0 DF2014 (v0.44.02+) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=175538 DF2014 (v0.47.01+) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=180805.0 DF2022 (v0.50.01+) WorldGen "Cookbook" Thread]

{{World}}

Advanced world generation

2026-04-10T01:23:24Z

Ziusudra: /* Terrain Mesh Sizes and Weights */ reworded bits in attempt to clarify and disambiguate, moved image up, changed redundant section name

{{migrated article}}
{{Quality|Superior}}
{{av}}
:''This article contains information on advanced world generation. For information on basic world generation, see [[World generation]].'' ''See [[World token]] to more easily find information by the names used in the world_gen.txt file, [[World rejection]] for information on solving problems related to worlds always being rejected, and [[Worldgen examples]] for example worlds.''

[[File:adv_worldgen_v50.png|thumb|400px|right|The advanced world generation screen. ''(Click to enlarge)'']]'''Advanced world generation''', also labeled as '''detailed mode''', allows substantially more detail-oriented options of customization than standard, basic world generation. This gives the player much more control over how their world is generated. To better understand this article, it is advised that one should read about [[World generation|'''basic world generation''']] first.

The advanced world generation screen is reached by clicking "Create new world" at the main menu, then clicking "Detailed mode". Once at that screen, clicking "Basic options" will return the user to the standard world generation screen.

== Parameter sets ==
There are multiple default sets of all the advanced world generation parameters hard-coded in ''Dwarf Fortress'', which will be overridden by the <tt>prefs/world_gen.txt</tt> file in the main ''Dwarf Fortress'' directory, if it exists. It does not exist by default, you must create it, either by saving the default sets, or saving a copy from the [[world_gen.txt]] wiki page or elsewhere. This file can then be edited with a text editor, and you can copy and paste other players' sets of parameters into it. For sources of such parameter sets see [[Advanced_world_generation#Parameter_set_examples|Parameter set examples]] below.

To get back the default sets, move the existing <tt>prefs/world_gen.txt</tt> to somewhere else (like Documents), or delete it if you do not want to keep the changes, then load the sets in the game, it will then use the hardcoded defaults.

== User interface ==
First, there is a line of text inputs and buttons along the top of the screen, from left to right:
* The drop down menu of currently defined parameter sets, click the down arrow to select a set that you want to work with. The currently selected set can be renamed by clicking the current name or the [[File:Quill.png]] button. The first set in the file is selected by default, usually "LARGE ISLAND". See [[#Parameter set title|Parameter set title]].
* The dimensions of the world for the selected set, see [[#World dimensions|World dimensions]].
* A text entry box to set all of the seed options to the same seed, will show "Random seed", "Various seeds", or, if all four seeds are set to use the same value, that value. See [[Advanced_world_generation#Seed_values|Seed values]] and [[Advanced_world_generation#Seed_values|Seed notes]].
* The Copy Button to make a copy of the currently selected set and appends it to the bottom of the list.
* The red Delete button to delete the currently selected set, you will be prompted to confirm the deletion.
* The New parameter set to create a new parameter set and appends it to the bottom of the list. This seems to just copy the default "LARGE REGION" set.
* The Save button to save all of the current sets to the <tt>prefs/world_gen.txt</tt> file.
* The Load button to load from the same file, there is no confirmation, '''any unsaved changes will be lost'''. If that file does not exist, this resets all of the sets to the defaults.

Most of the middle is the parameters themselves, with a scroll bar to the right. Each row of the list can include:
* The name of the option
* The range of accepted values; not every option has this, and does not always match the displayed value, for example "0 to 1" might show as "No" and "Yes".
:* Sometimes the range might not initially show on rows that it should, reloading the sets with the Load button sometimes fixes that.{{bug|13176}}
* A plus button to increase the value or cycle through options, when applicable (this button will be missing if the range is missing.)
* The current value; can be clicked to edit, to actually set a value you must press {{k|enter}}, without doing that, clicking another entry box or right clicking will instead reset to the currently set value.
* An edit button to show that the previous box is editable, same as clicking on the text box.
* A minus button to decrease the value or cycle through options, when applicable (this button will be missing if the range is missing).
* A red button to disable this parameter, when applicable, usually setting the value to 0, or -1.

{{notice bar|bgcolor=#faa|bordercolor=#f00|All of the buttons below leave this screen and do not prompt to save the sets, so unsaved changes may be lost.}}
At the bottom right are 3 or 4 more buttons:
* The Create world button to do just that using the currently selected set, '''unsaved changes are lost'''.
* The Basic options button to go back to the normal world generation screen, unsaved changes are not lost if you come directly back to Detailed mode.
* The [[Mods]] button to go to the mod selection screen, unsaved changes are not lost if you come directly back to Detailed mode. Only shown if mods are available.
* Back to main menu button to do just that, '''unsaved changes are lost'''.

=== World painter ===
:''Main article: [[World painter]]
The '''world painter''' tool is not in the current version of ''Dwarf Fortress''; it allowed you to paint features onto a map. '''However''', those maps can still be used when generating a world by pasting world painter parameter set maps created in old versions into the <tt>prefs/world_gen.txt</tt> file. [[Utilities#Perfect_World_DF|Perfect World DF]] is a utility that uses the same parameter functionality as the world painter to paint a map, and it also can work with the current version of ''Dwarf Fortress''.

== Generating a world ==
You can either use an already-defined parameter set, or you can edit them, though it is highly suggested to edit a copy of one of the defaults. Once you are happy with the parameters you should save the values you just edited before you click the Create world button. Information about each parameter is documented below.

The phases of the world generation process are (this order is not completely correct):
* Preparing elevation...
* Setting temperature...
* Running rivers...
* Forming lakes and minerals...
* Growing vegetation...
* Verifying terrain...
* Importing wildlife...
* Recounting legends...
* Placing civilizations...
* Making cave civilizations...
* Making cave pops...
* Placing other beasts...
* Placing megabeasts...
* Placing good/evil...
* Placing caves...
* Prehistory generation
* Finalizing civ mats...
* Finalizing art...
* Finalizing uniforms...
* Finalizing sites...

== Seed notes ==
The world generation process uses a PRNG (Pseudo Random Number Generator) algorithm. A PRNG will produce a sequence of numbers that "looks" random, even though the actual sequence of numbers will always be the same if the PRNG is started with the same seed value. Basically this means that if you run world generation with a certain seed value on your computer, and someone else runs world generation with the same seed value on their computer, the same sequence of random numbers will be generated on both computers. The practical impact of this is that someone else can generate exactly the same world that you generated by entering the same seed value that you used.

In the current version, the seed values for the world itself and the names seem to produce the same result, but you will get changes in events which will result in a very different world history.{{bug|6934}} Keep this in mind if you want to regenerate a particular world.

The way that a world is generated can also be affected by certain world tokens. Changing them causes that code to use more or fewer PRNG values, causing later uses to get different parts of the sequence. So, you cannot for example, change the minimum and maximum rainfall and get 'the same world but drier or wetter', instead, a different world is generated. That said, it would also seem that certain small changes to these world tokens can occasionally generate a very similar world, however, other tokens are more sensitive. For more information see the forum thread [http://www.bay12forums.com/smf/index.php?topic=112132.msg3404199#msg3404199 here].

The following are tokens which use the PRNG values in ways that changing them will likely cause broader changes:

* [DIM:X:X]
* [ELEVATION:X:X:X:X]
* [RAINFALL:X:X:X:X]
* [TEMPERATURE:X:X:X:X]
* [DRAINAGE:X:X:X:X]
* [VOLCANISM:X:X:X:X]
* [SAVAGERY:X:X:X:X]
* [ELEVATION_FREQUENCY:X:X:X:X:X:X]
* [RAIN_FREQUENCY:X:X:X:X:X:X]
* [DRAINAGE_FREQUENCY:X:X:X:X:X:X]
* [TEMPERATURE_FREQUENCY:X:X:X:X:X:X]
* [SAVAGERY_FREQUENCY:X:X:X:X:X:X]
* [VOLCANISM_FREQUENCY:X:X:X:X:X:X]
* [PARTIAL_OCEAN_EDGE_MIN:X]
* [COMPLETE_OCEAN_EDGE_MIN:X]
* [HAVE_BOTTOM_LAYER_1:X]
* [MINERAL_SCARCITY:X] {{cite talk/this|Mineral scarcity}}

Many other world parameters, such as end year and embark points, can, however, be changed without it having any effect on the geography of the world generated from the seed values.

Normally, you don't enter these seed values, the game comes up with values based on some other sort of pseudo-random information from things like the current date and time.

When generating a world, ''Dwarf Fortress'' records the seeds it used in [[gamelog.txt]]; they can also be found with <code>gui/gm-editor world.worldgen.worldgen_parms</code> in [[DFHack]].

== Advanced parameters ==
There are essentially 4 types of controls for the generation of the surface map;

'''Terrain parameters''': as described below, these 5 variables define the basic background world, how hot or cold it is, how much rainfall, how high the mountains are. The world automatically goes through the temperature range along the Y axis, although sometimes it will be hotter in the north, other times in the south, or cold at both. Minimum, maximum and X,Y variance can drastically alter the world.

'''Weighted meshes''': these are a way to fine-tune the amount of the 5 basic variables on the map. They can be used to set the specific distribution of different elevations or rainfall areas for example.

'''Feature parameters''': such as rivers, mountain peaks, volcanoes, and oceans, which can cause rejections if the terrain parameters don't allow enough suitable locations for the features to be placed.

'''Rejection parameters''': ''Dwarf Fortress'' uses a 'belt-and-braces' approach to world generation. The above controls allow you to shape the world, then the rejection parameters throw it out if it does not meet certain criteria. There are a number of rejection parameters for the number and degree of the 5 basic variables, for biome types, etc. If the world does not meet the requirements of any one rejection parameter the world is rejected and re-randomised. Also see [[World rejection]].

Leaving tokens out of a set in <tt>world_gen.txt</tt> will cause the game to use default values which are not adjusted for smaller world sizes, this may cause smaller worlds to always be rejected.

If you are experimenting with world design, there is also a [[Settings#Feature_toggles|game setting]] that will log the rejection reasons to ``[[map_rejection_log.txt]]``. With that information you can then either adjust the rejection parameters to allow those worlds, or the other parameters to prevent them from trying to generate. ''Dwarf Fortress'' will keep adding to the file, so you may want to trim or delete it occasionally.

The parameters are described below in the order that they appear in the list in the game, which is not necessarily the order they appear in <tt>world_gen.txt</tt>. See [[world token]] for an index that will help you look things up by token name. The tokens used in <tt>world_gen.txt</tt> are at the bottom of each of the following parameter descriptions.

=== Parameter set title ===
This sets the name of the parameter set itself, as used in the list of sets (this has nothing to do with the name of the generated world).
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITLE:<name>]</nowiki></tt>
| <tt><nowiki>[TITLE:MEDIUM ISLAND]</nowiki></tt>
| Required
|}

=== World dimensions ===
The size of the map for the current set can be changed by changing the Width and Height values at the top next to the set title. You will need to confirm this, since changing the dimensions of the world will change other parameters, because many of them have different defaults depending on the surface area available.

Larger maps usually take longer to generate and may reduce [[Frames per second|FPS]] in-game, though this is really a matter of larger worlds usually having more civilizations, sites, historical figures, and events; restricting the number of those can speed up the process. Non-square maps may result in crashes{{bug|2928}}.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DIM:<width>:<height>]</nowiki></tt>
| <tt><nowiki>[DIM:257:257]</nowiki></tt>
| Valid values are 17, 33, 65, 129, and 257, other values will use one of those. Changing the size in the file without adjusting other parameters can cause many rejections.
|}

=== Seed values ===
Enables the use of, and specifies seed values for, different parts of the world generation process. Just entering a specific seed does not enable it, that must be done separately, although using the box at the top to set all the seeds to the same value does enable them all. Enabling a seed puts the token in using what ever is in the text box below. If you enable a seed, but do not enter a seed, the string "Seed text" will be used (<tt><nowiki>[SEED:Seed text]</nowiki></tt>). Trying to use a <tt><nowiki>]</nowiki></tt> in the string in the file will end the seed there, since it closes the token, any text after that will be ignored. Normally, just leave these set to Random, unless trying to reproduce the results of a previous world generation. See also the [[Advanced_world_generation#Seed_notes|seed notes section]] above.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEED:<text>]</nowiki></tt>
| <tt><nowiki>[SEED:31337]</nowiki></tt>
| rowspan="4" |
For each of these not in the config file, a random seed will be used, and the first seed is not used to generate the others. The seeds used are output to [[gamelog.txt]] when world generation starts.
|-
| <tt><nowiki>[HISTORY_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[HISTORY_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[NAME_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[NAME_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[CREATURE_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[CREATURE_SEED:31337]</nowiki></tt>
|}

=== World name ===
As previously mentioned, the title of the parameter set doesn't affect the name of the world. You can specify a particular name for your world, or leave the value blank for a random one. (The [[DFHack]] utility adds an option to rename the world using the in-game languages.)
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CUSTOM_NAME:<name>]</nowiki></tt>
| <tt><nowiki>[CUSTOM_NAME:Realm of Cheese Engravings]</nowiki></tt>
| For a random name, simply don't use this token.
|}

=== Embark Points ===
The number of points for equipment and animals when embarking in fortress mode (there is no equivalent setting for adventure mode). Normally, the default of 1504 is fine, but can be increased for various purposes like experimentation or to help dwarves survive in a particularly evil world, or reduced for certain [[challenges]].
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EMBARK_POINTS:<number>]</nowiki></tt>
| <tt><nowiki>[EMBARK_POINTS:1504]</nowiki></tt>
| 0 to 10,000
|}

=== End year ===
The maximum number of years generated for the world, although generation can be paused and the world used as is any time after the second year; the same as the [[World_generation#History|History]] parameter in basic world gen, except that you can enter an exact value. A too-short history can limit the materials available to civilizations, and [[Chosen|certain adventure mode features]] are only available after certain site events, while too long a history often leads to civilizations dying.

For more information on the history aspect of the game, see [[Legends]] and [[Calendar#Ages|Ages]].
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[END_YEAR:<number>]</nowiki></tt>
| <tt><nowiki>[END_YEAR:250]</nowiki></tt>
| 2 to 10,000
|}

=== Population cap after civ creation ===
A soft limit to the total number of [[historical figure]]s alive at the same time during generation across all civilizations, only preventing the birth of new historical figures.{{cite forum|140544/5701667}} Each civilization is allotted a percentage of the total by the percentage of sites they control.{{cite forum|159164/7553641}} Civilizations also have non-historical populations, and there is no setting to limit those (in early versions, all civilization members were historical figures, this is also why the name of this setting is misleading). Each [[entity]] also has limits from their raws, see the [[Entity_token#Population|population]] entity tokens, and setting this to unlimited will not remove those.

Huge historical figure populations can slow generation and the game in general.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_POPULATION:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_POPULATION:15000]</nowiki></tt>
| -1 to 100,000, -1 is no limit
|}

=== Site cap after civ creation ===
Total number of [[site]]s that can be directly created by all civilizations combined like [[hillocks]], [[hamlet]]s, [[dark pits]], [[forest retreat]]s, etc. Does not prevent the placement of initial civilization sites, though they will then be counted for the limit. Does not affect creature sites like [[cave]]s or [[lair]]s, group sites like [[castle]]s, [[monastery|monasteries]], [[tower_(necromancy)|tower]]s, [[fort]]s, or [[camp]]s, or unpopulated sites like [[tomb]]s. After this limit is reached, no civilization will be able to place new sites. See the [[Entity_token#Placement|placement]] entity tokens for other ways that civilization site placement can be limited.

Increasing this will slow generation down and reduce the available places for player sites. Since the {{token|MAX_SITE_POP_NUMBER|entity}} entity token limits the historical figure population per site, this site cap can also limit the total historical figure population of all civilizations combined, and some expand faster than others getting more sites before the limit is reached.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SITE_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SITE_CAP:1500]</nowiki></tt>
| -1 to 100,000, -1 is no limit
|}

=== Beast control ===

These parameters don't usually matter too much, but may matter for small numbers of beasts.

==== Percentage of Megabeasts and Titans Dead for Stoppage ====

The world starts out with a certain number of powerful megabeast and titan entities in existence. If a percentage of the megabeast and titan population dies out during history generation, then history generation will stop early. For example, if the elimination value is 80%, and the generated history starts with 200 entities and 160 of those 200 entities are eliminated by historical events before the End Year is reached, history generation will stop immediately.

If you want to end the creation of your world at the beginning of a certain age, choose the following values:
* Age of Legends: ~34%
* Age of Heroes: ~67%
If there are three or fewer titans or megabeasts in your world, the age will be given a special name reflecting the remaining megabeasts/titans, instead.

==== Year to Begin Checking Megabeast Percentage ====

The percentage of dead [[megabeast]]s and [[titan]]s for stoppage will not be checked until this year is reached in history generation. This can be used to ensure that a world reaches a certain year even if all of the megabeasts in the world are slain earlier.

If the number of living [[megabeast]]s and [[titan]]s starts at or drops to less than four, then world generation will always stop if the current year is equal to or greater than the Year to Begin Checking Megabeast Percentage ''regardless'' of how many [[megabeast]]s and [[titan]]s are dead — Percentage of Megabeasts and Titans Dead for Stoppage is ignored. The number of megabeasts and titans at the start of the world is set by the sum of the [[Advanced_world_generation#Max_Megabeasts_Caves|Max Megabeasts Caves]] and [[Advanced_world_generation#Titan_Parameters|Titan Number]] parameters.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[BEAST_END_YEAR:<year>:<percentage or -1>]</nowiki></tt>
| <tt><nowiki>[BEAST_END_YEAR:200:80]</nowiki></tt>
| Use -1 as percentage to disable. Year must still be at least 2.
|}

=== Cull Unimportant Historical Figures ===
{{main|Historical figure}}
Whether to remove unimportant dead historical figures after history generation; a short CPU-intensive step, but saves space which can speed up loading, saving, and running games with large histories. Legends mode will refer to culled creatures as "an unknown creature", and they will not appear in engravings, but likely would not have anyway.

Exactly what is considered important is not clear. A member of an abstract group killing a named creature is not. Creating an artifact is not, even if that artifact had important history. Unculled historical figures can have parentage described as "The identity of" that parent "has been lost to time", so just having children is not, though having living direct relations seems to prevent culling.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CULL_HISTORICAL_FIGURES:<0 or 1>]</nowiki></tt>
| <tt><nowiki>[CULL_HISTORICAL_FIGURES:0]</nowiki></tt>
| 0 = No, 1 = Yes
|}

=== Reveal All Historical Events ===

Setting this to Yes will allow access to most information about the history of the world in [[Legends mode]]. All events will be revealed, but some [[historical figure]]s, [[site]]s, [[region]]s, and [[civilization]]s and other entities may not be, possibly because they are not known to any civilization. If set to No, then you will have to discover historical information in [[adventure mode]] or by instructing dwarves to make engravings.{{Verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[REVEAL_ALL_HISTORY:<0 or 1>]</nowiki></tt>
| <tt><nowiki>[REVEAL_ALL_HISTORY::1]</nowiki></tt>
| 0 = No, 1 = Yes
|}

=== Terrain Parameters ===

These set limits and variance for terrain elevation, rainfall, temperature, drainage, volcanism, and savagery which determines how those values are generated. What biomes exist are then determined by how these factors overlap with each other.

==== Minima and Maxima ====
These are the absolute minimum and maximum values that can ever be generated for a particular map square characteristic. By ''subtly'' tweaking the min and max values, vastly different maps can be made. Changing these can cause the occurrence of certain [[Biome|biomes]] to become impossible, so you may want to use [[#Terrain Mesh Sizes and Weights|Weighted Ranges]] instead.

==== X and Y Variance ====
These control how wildly things like elevation and rainfall can vary between adjacent map squares. For example, if these values are set to the maximum of 3,200 for elevation then you will end up with more very low areas right next to very high areas. The number for X determines the east-west variance and the number for Y determines the north-south variance. By setting only one of these to a high value you can, for example, create horizontal or vertical bands of areas which are more similar to each other.

Generally speaking, raising both of these values will create a more random "patchwork" of many small biomes while setting both x and y values to 0 will cause every square on the map to use a single random value for the given characteristic.

For "patchwork" worlds to avoid being rejected, [[#Maximum Number of Subregions|Maximum Number of Subregions]] will probably need to be increased from the default.

==== Elevation ====
This controls the range of terrain elevations that can occur in the world. Usually, you just want to leave the min/max values alone. Raising the minimum elevation can, for example, make it impossible for oceans to exist. This does '''not''' directly control the number of available Z-levels at a particular site, though high maximum values may contribute to peaks, which can raise the number of above ground Z-levels - in other words, a maximum elevation of 400 and minimum of 1 does not mean you get 400 Z-levels, but it might increase the number of Z-levels somewhat in some regions compared to others. Raising the variance will result in a more bumpy, uneven landscape.

Some biomes/features that are impacted by elevation:
* A high minimum (above 99) means no oceans, as they need elevations below 100.
* A low maximum (below 300) means no mountains, as mountains need elevations above 300.
* Rivers will be placed when the elevation maximum is 104 or higher. Therefore, keeping both values above 100 and below 104 will prevent all water tiles from appearing.
* Mountain peaks can only form at elevations of 400.

==== Rainfall ====
Controls the amount of rainfall in each map square/area. Setting the minimum or maximum too high or low can make the formation of certain biomes impossible. Rainfall causes it to [[rain]] more in a given area, which can have various effects. Also makes more rivers appear on the world map.

Note that if [[#Do Orographic Precipitation and Rain Shadows|orographic precipitation and rain shadows]] is on, then mountains will cause additional variance in rainfall, so (for example) rainfall below the specified minimum can occur in the shadow of a mountain. If you want the minimum and maximum for this parameter to be absolutely respected, you must turn off the orographic precipitation option.

Additionally, with 'Orthographic Precipitation' turned on, orthographic precipitation and rain shadows will only occur in regions with greater than or equal to 50 drainage. [http://www.bay12forums.com/smf/index.php?topic=139916.0 [Report, reproduced 2022]]

==== Temperature ====
{{main|Climate|Temperature}}
These parameters control how hot or cold various areas will be. If you lower the minimum and maximum values, the world will be colder overall, for example. As with the others, changing these values too much could make it impossible for certain biomes to exist. The temperature scale used in this setting is related to regular degrees Urist by the equation "local temp = world temp * 0.75 + 10000".{{cite forum|169696/8395484}} This scale doesn't seem to be used anywhere else in the game. See [[Climate]] for more info.

These parameters form the "base" temperature for an area, and describe peak summer temperature in a scale that isn't used elsewhere in the game. This number also does not correspond 1:1 with the final climate. [[Temperature]] is always influenced by a number of variables, including elevation, time of year, thick forestation, and if [[Advanced_world_generation#Poles|poles]] are enabled, latitude. These other variables are factored in after the temperature mesh is applied, and frequently bring temperatures above and below their set minimum and maximum values. ''The inclusion of Poles is particularly strong in this regard, as it allows latitude to raise and/or lower temperatures by more than 75 degrees Celsius! That said, the temperatures aren't raised or lowered by more than about 65 degrees past the set minimum and maximum. Furthermore, for typical ranges, the temperature will never be raised more than about 25 degrees past the maximum (but will still drop up to about 65 degrees Celsius below the minimum).'' (unsure about exact values, research needed)

Elves can spawn where the temperature is 10 degrees or warmer, and humans can spawn where the temperature is 0 degrees or warmer.

==== Drainage ====
Changing drainage parameters will change the way water-affected biomes are formed. Low drainage will contribute to the formation of [[Lake|lakes]], [[River|rivers]], and [[Swamp|swamps]]. High drainage will cause water to sink into the ground rather than sit on the surface, which is important for forming hills.

Lower drainage values have been reported to contribute to the formation of thicker soil layers, though it is currently unknown exactly how other factors (such as elevation or perhaps rain) impact soil formation.

==== Volcanism ====
Volcanism controls the occurrence of igneous [[layer]]s, and the formation of volcanoes. For a volcano to form, a square must have a volcanism value of 100, so reducing the maximum from 100 will make volcanoes impossible. Raising the minimum will increase the rarity of non-igneous layers.

Setting the minimum to a high value is not a good way to produce multiple volcanoes, as you are likely to get a "Volcanism not evenly distributed" rejection. Instead, use the Minimum Number of Volcanoes parameter, and possibly adjust the weighted ranges for volcanism as described below.

==== Savagery ====
These parameters control the level of [[Surroundings#Savage|savagery]] on the map. Raising the minimum savagery too high may make it impossible for certain races to exist, and similarly lowering the maximum too far can make it impossible for certain creatures to exist. The largest chance of having unusable maps comes from a too-high savagery value.

==== Configuration Tokens ====
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[ELEVATION:1:400:401:401]</nowiki></tt>
| Range: 0 to 400 Maximum of 400 required for mountain peaks. Variance range: 0-3200
|-
| <tt><nowiki>[RAINFALL:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[RAINFALL:0:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|-
| <tt><nowiki>[TEMPERATURE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE:25:75:200:200]</nowiki></tt>
| Range: -1000 to 1000 Variance range: 0-3200
|-
| <tt><nowiki>[DRAINAGE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE:0:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|-
| <tt><nowiki>[VOLCANISM:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM:1:100:200:200]</nowiki></tt>
| Range: 0 to 100 Maximum of 100 required for volcanoes. Variance range: 0-3200
|-
| <tt><nowiki>[SAVAGERY:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY:1:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|}

=== Terrain Mesh Sizes and Range Weights ===
[[File:World_map-large-32x32-elevation-mesh.png|thumb|300px|A large world generated with an Elevation Mesh Size of 32×32 and range weights set to 1:0:0:0:1 (i.e., only extreme high and low elevations). Note how the grid intersections are either set very high (mountains) or very low (oceans) and the space between them is smoothed out.]]
These parameters influence the relative proportions of terrain feature ranges, without making other ranges impossible. For example, to have many more low-elevation squares exist, without making it impossible for high elevations; this makes changing these parameters often preferable to simply changing the above min/max values. See the image on the right for an example.

The basic steps of applying weighted ranges are as follows:
# Divide the world into a grid of quantity <code>2''MeshSize'' - 1</code> areas in both X and Y direction.
# At each grid intersection, set the value according to the weighted ranges.
# Smooth out the areas between the intersection points.
# Add noise according to the variance parameters.
Where ''MeshSize'' is the raw parameter value found in the <code>[[world_gen.txt]]</code>.

==== Interaction between Mesh Size and Weighted Ranges ====
Mesh size determines how many intersection points the world will have. As an example, setting it to 2×2 means the world will divided into 4 areas, 2 across and 2 tall, and there will be a total of 9 intersection points (3×3). The grid intersection points are in the middle of world tiles, and the minimum size for a grid area is a span of 9×9 world tiles, with adjacent areas sharing an overlapping world tile. On a pocket world, this means one grid tile will span 9×9 world tiles, whereas on a large world, one grid tile will span 129×129 world tiles. A pocket world will always use a 2×2 grid areas of 9×9 world tiles, since it has only 17×17 tiles total (even though the game UI allows setting those worlds to a 4×4 grid).

Setting mesh size to something other than Ignore, will apply random values at those intersections, with those random values being more likely to be in the higher weighted ranges. Setting to Ignore will cause the weighted range settings to be ignored for that terrain characteristic; instead setting the 4 corners of the world to completely random values and smoothing between those.

For example, if the Elevation Weighted Range parameters are set to <code>60:10:10:10:10</code> (starting with the 0-20 range, and these values do not have to add up to any particular number), and elevation min and max are left at the defaults of 1 and 400 respectively, then about 60% (on average) of the grid line intersection points will be set to an elevation in the range of 1-80 (0% to 20%), and the other ranges will be represented by around 10% of the intersection points each. The exact distribution is still left up to chance, though ''on average'' it will be close to this specification. This allows random number generation to be non-linear for the given terrain characteristic.

Setting the weight for a range to None only prevents intersection points from being set to a value in that range; terrain between intersection points can still be smoothed to values in ranges set to None that are between the intersection point values.

Weighted ranges do not make rejection checks, although they can be responsible for many rejections if you neglect to adjust or disable some of the [[#Minimum Number of Mid/Low/High Characteristic Squares|Minimum Number of Mid/Low/High Characteristic Squares]], for example.

==== Interaction between these and Variances ====
The end result can vary greatly depending on how the corresponding [[#X_and_Y_Variance|X and Y Variance]] parameters are set. First of all, if the variance is too high, the noise it adds can completely negate the effect of the weighted ranges. For instance, with a 2×2 mesh, the default variance parameters are high enough that usually the mesh grid can hardly be recognized. How strong the variance's effect is, is also dependent on the mesh size. Having a larger mesh size (i.e. smaller grid tiles) means the variance also has to be higher for a visible effect. For instance, with a variance of 400, the effects are clearly visible with a 2×2 mesh and barely visible at all with a 8×8 mesh. Note that this effect is directly dependent on the mesh size and not, as one might expect, on the actual size of the grid tiles. This means, that a large world with a 32×32 mesh will look essentially the same as a pocket world with a 2×2 mesh, only stretched to 256 times the size.

Also see this [http://www.bay12forums.com/smf/index.php?topic=139916.0 forum post] for more details.

==== Configuration Tokens ====
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[ELEVATION_FREQUENCY:2:1:2:3:4:5]</nowiki></tt>
| rowspan="6" | Valid mesh values:

1 = Ignore

2 = 2x2

3 = 4x4

4 = 8x8

5 = 16x16

6 = 32x32

(limited by world size)
|-
| <tt><nowiki>[RAIN_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[RAIN_FREQUENCY:3:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[DRAINAGE_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE_FREQUENCY:4:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[TEMPERATURE_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE_FREQUENCY:1:1:1:1:1:1]</nowiki></tt>
|-
| <tt><nowiki>[SAVAGERY_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY_FREQUENCY:5:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[VOLCANISM_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM_FREQUENCY:1:1:1:1:1:1]</nowiki></tt>
|}

=== Poles ===

With this, you can influence how polar regions are added. The poles can be on the north or south edge, and the equator will be on the opposite edge, or in the middle if there are two poles. If poles are set to NONE, then there will be no seasonal changes in the weather (e.g. no winter snow in temperate biomes).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[POLE:<placement>]</nowiki></tt>
| <tt><nowiki>[POLE:NORTH]</nowiki></tt>
| Viable options: NONE, NORTH_OR_SOUTH, NORTH_AND_OR_SOUTH, NORTH, SOUTH, NORTH_AND_SOUTH
|}

=== Minimum Mountain Peak Number ===

This will cause the world to be rejected if fewer than this many peaks (based on elevation) are present on the map. EG: elevations of 400 must be possible for mountain peaks to occur. If set to zero, then worlds will not be rejected based on number of peaks.

You may need to adjust elevation parameters, such as the highest weighted range, in order to get the desired number of elevation-400 squares needed for larger numbers of peaks. Like volcanoes, mountain peaks can make embark zones more interesting, but other than that, they don't appear to "do" anything special. Reportedly, they do increase the highest Z-level above ground in all embark zones in the same region, even if the selected embark zone does not include the peak.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PEAK_NUMBER_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[PEAK_NUMBER_MIN:20]</nowiki></tt>
| Elevations of 400 must occur for peaks to form.
|}

=== Minimum Partial Edge Oceans ===

This will cause a world to be rejected unless there are at least this many oceans touching an edge of the map. If set to zero then worlds will not be rejected based on this criterion. Setting both this parameter and Minimum Complete Edge Oceans to values that total more than 4 when added together may cause all worlds to be rejected as you can't have both a partial and complete edge ocean on a given edge.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PARTIAL_OCEAN_EDGE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[PARTIAL_OCEAN_EDGE_MIN:2]</nowiki></tt>
| Maximum of 4
|}

=== Minimum Complete Edge Oceans ===

This will cause a world to be rejected unless there are at least this many oceans which completely cover an edge of the map. Since a square map only has 4 edges, the maximum value possible is 4. If set to zero then worlds will not be rejected based on this criterion but still might end up with complete edge oceans by chance.

Note that the ability for this many edge oceans to exist will be limited by elevation. Therefore, to actually create large oceans you will probably need to change things like the Elevation Mesh Size and Weighted Ranges to increase the number and distribution of very low elevation squares on the map. In addition, if Complete Edge Oceans is set to any value ''other'' than 0 or 4, you may need to lower elevation variance for at least one of the axes: if set too high, such as a variation of 1600 for both X and Y axes (the default for Large Island and Medium Island parameter sets), the game may generate worlds very slowly or even hang.{{bug|565}}

Given appropriate weight, range, and variance values for things like elevation, a setting of: 1 results in a world that seems like a chunk of coastline. One edge of the map will be completely underwater and there will be ocean taking up much of the map on that side (think the east or west coast of the United States, the north coast of Canada, or southern Europe). If your edge ocean happens to pick your world's frozen side, most of it will be glacier.

*2 results in another coastline along with the first one -- the map could end up looking something like Panama if the oceans pick opposite sides of the map.
*3 results in a peninsula, like Florida in the US. There will be oceans surrounding 3 sides of the map, and land touching only one side of the map.
*4 results in one or more island(s) depending on things like elevation variance and weights. Regardless of whether you get one island or multiple islands, the entire map will be surrounded by water.

Unfortunately, there's no easy way to control which oceans end up on which edges, except perhaps setting X/Y variance to different values.

Edge oceans will take up part of the other edges too. For example, a full edge ocean on the east side will have part of the north and south sides underwater, but that does ''not'' add to the ''partial'' edge oceans count.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[COMPLETE_OCEAN_EDGE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[COMPLETE_OCEAN_EDGE_MIN:0]</nowiki></tt>
| Maximum of 4
|}

=== Minimum Volcano Number ===

The game will attempt to place this many volcanoes, but there must be at least this many squares with a volcanism of 100, if there are not the world will be rejected. Therefore, [[Advanced_world_generation#Volcanism|maximum volcanism]] above must be set to 100, and adjusting the [[Advanced_world_generation#Configuration_Tokens_2|volcanism weighted range]] above for 80-100 to a higher value can increase the number of those squares.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[VOLCANO_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[VOLCANO_MIN:15]</nowiki></tt>
| Volcanoes require a volcanism of 100 to occur.
|}

=== Mineral Scarcity ===
Controls the frequency at which minerals occur; setting this value higher will decrease both the number of different types and amounts of ore and gems present on a map. The default value will result in many metal ores, while the old default of ''sparse'' would be only a few ores, which may be limiting until other metals can be requested and traded for.

The options "Very Rare", "Rare", "Sparse", "Frequent", and "Everywhere" in the [[World_generation#Basic_world_generation_menu|basic world generation menu]] use the values 50000, 10000, 2500, 500 and 100 respectively.

According to [http://www.bay12forums.com/smf/index.php?topic=79018.msg2063804#msg2063804 research] by Shandra in v0.31.25, this is the relationship between the value of this setting and the approximate number of gems and ore:

[[File:MineralSetting_v25_limit10k.png]]

This is for the same 8x8 embark region in a world which is otherwise the same, except for the mineral scarcity parameter (although most of the detailed information comes from experiments with previous versions). (The chart legend has an error, the first "Pot.(Types)" should read "Pot.(Amount)".)
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MINERAL_SCARCITY:<number>]</nowiki></tt>
| <tt><nowiki>[MINERAL_SCARCITY:100]</nowiki></tt>
| Range: 100 to 100,000
|}

=== Max Megabeast Caves ===

This is the number of [[megabeast]]s placed at the beginning of history. Megabeasts are [[hydra]]s, [[bronze colossus]]es, [[roc]]s, and [[dragon]]s, which are all placed in equal proportions [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415177#msg3415177 data].

Increasing this value can lead to early extinction of civilizations.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[MEGABEAST_CAP:75]</nowiki></tt>
| Megabeasts count towards BEAST_END_YEAR calculation.
|}

=== Max Semi-Megabeast Caves ===

This is the number of [[semi-megabeast]]s placed at the beginning of history. Semimegabeasts are [[giant]]s, [[ettin]]s, [[minotaur]]s, and [[cyclops]], which are placed in equal proportions [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415188#msg3415188 data].

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEMIMEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SEMIMEGABEAST_CAP:150]</nowiki></tt>
| Semimegabeasts do not count towards the BEAST_END_YEAR calculation.
|}

=== Titan Parameters ===

==== Number ====

This controls the number of [[titan]]s that exist at the beginning of history[http://www.bay12forums.com/smf/index.php?topic=112465.msg3415203#msg3415203 data]. The number of forgotten beasts is unaffected by this parameter [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415155#msg3415155 data].

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TITAN_NUMBER:33]</nowiki></tt>
| Titans count towards BEAST_END_YEAR calculation.
|}

==== Attack Population Requirement ====

[[Titan]]s will begin to attack your fort once at least this many dwarves inhabit it, regardless of whether any other attack criteria have been met.

This number defaults to 80, which isn't usually too difficult to deal with.

==== Exported Wealth Requirement ====

Titans will begin to attack your fort once you have exported at least this many [[Currency|dwarfbucks]]-worth of goods, regardless of whether or not any other criteria have been met. This parameter defaults to None (disabled).

==== Created Wealth Requirement ====

Titans will begin to attack your fort once the fort's total wealth has reached this many [[Currency|dwarfbucks]] in value. This happens regardless of whether any of the other criteria, such as population, have been met; therefore, even with 1 dwarf, a fort could be attacked if the fort were worth at least this value.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_ATTACK_TRIGGER:<population>:<exp wealth>:<created wealth>]</nowiki></tt>
| <tt><nowiki>[TITAN_ATTACK_TRIGGER:80:0:100000]</nowiki></tt>
| 0 = None (disabled). Only one requirement must be met for an attack.
|}

=== Number of Demon Types ===

[[Demon]]s are similar to [[titan]]s and [[forgotten beast]]s, in that they are procedurally generated, but most are not unique. Thus, many different types of demons can exist in the world, but there will also be many individuals of most types. Thanks to [[Underworld spire|certain fun things]], fewer demon types also means fewer goblin civilizations.{{cite forum|112465/7392706}} You need at least 2 demon types, or else goblin civilizations won't exist initially, though if dwarves breach the underworld during world generation, at least one will be generated then.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DEMON_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[DEMON_NUMBER:52]</nowiki></tt>
| 0 to 1000
|}

=== Number of Night Troll Types ===

The number of different [[night troll]]s, also procedurally generated, that will exist in the world. Setting this to zero means that the world will have no night trolls, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[NIGHT_TROLL_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[NIGHT_TROLL_NUMBER:77]</nowiki></tt>
| 0 to 1000
|}

=== Number of Bogeyman Types ===
The number of different [[bogeyman]] forms that will exist in the world. Bogeymen are procedurally generated, though their forms do not vary by much. Setting this to zero means that the world will have no bogeymen, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[BOGEYMAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[BOGEYMAN_NUMBER:27]</nowiki></tt>
| 0 to 1000
|}

=== Number of Nightmare Types ===
The number of different [[nightmare]] forms that will exist in the world. Nightmares are procedurally generated. Setting this to zero means that the world will have no nightmares, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[NIGHTMARE_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[NIGHTMARE_NUMBER:27]</nowiki></tt>
| 0 to 1000
|}

=== Number of Vampire Curse Types ===

The number of different types of [[Vampire|vampires]] that will exist in the world. Although they are generated at the start of a new world, they aren't different from each other. Setting this to zero means no vampires will exist.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[VAMPIRE_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[VAMPIRE_NUMBER:72]</nowiki></tt>
| 0 to 1000
|}

=== Werebeast Parameters ===

==== Number of Werebeast Curse Types====

The number of different types of [[werebeast]]s that can exist in the world. It is common for werebeasts, unlike vampires, to assume many different forms and variations, the most well-known of these amount to different species of animals, from lizards, to wolves, to even bears. Setting this to zero means no werebeasts will exist, and will also remove a large amount of [[fun]] from the game.

In vanilla, there are only 82 possible unique werebeast species. Any further species will generate as wereblobs.{{bug|13308}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[WEREBEAST_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[WEREBEAST_NUMBER:58]</nowiki></tt>
| 0 to 1000
|}

==== Attack Population Requirement ====

Werebeasts will begin to attack your fort once at least this many dwarves inhabit it, regardless of whether any other attack criteria have been met. This number defaults to 50 which will often be reached in the second year of the fort.

==== Exported Wealth Requirement ====
Werebeasts will begin to attack your fort once you have exported at least this many [[Currency|dwarfbucks]]-worth of goods, regardless of whether or not any other criteria have been met. This parameter defaults to 5000.

==== Created Wealth Requirement ====

Werebeasts will begin to attack your fort once the fort's total wealth has reached this many [[Currency|dwarfbucks]] in value. This happens regardless of whether any of the other criteria, such as population, have been met; therefore, even with 1 dwarf, a fort could be attacked if the fort were worth at least this value.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[WEREBEAST_ATTACK_TRIGGER:<population>:<exp wealth>:<created wealth>]</nowiki></tt>
| <tt><nowiki>[WEREBEAST_ATTACK_TRIGGER:50:5000:50000]</nowiki></tt>
| 0 = None (disabled). Only one requirement must be met for an attack.
|}

=== Number of Secret Types ===

The number of secrets that exist in the world. Currently, all secrets are secrets of life and death, and the ones holding these secrets are [[necromancer]]s, thus, setting this to zero means that no necromancers will appear.
Non-necromancer towers can still appear (extremely rarely) with zero secrets, constructed by independent undead groups.
The primary difference between having 1 or 1000 secrets is the chance of your world having any necromancer towers at all. With 1, this chance is low. With the default number, it's seemingly guaranteed.
Even with 1 secret, if you have any necromancer towers at all, it is likely a great number will quickly appear in world generation (though this isn't guaranteed).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SECRET_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[SECRET_NUMBER:52]</nowiki></tt>
| 0 to 1000
|}

=== Number of Regional Interaction Types ===

The number of interactions that can be caused in regions, which may incorporate evil rain and cloud types. Currently, only evil region interactions are generated this way.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[REGIONAL_INTERACTION_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[REGIONAL_INTERACTION_NUMBER:20]</nowiki></tt>
| 0 to 1000
|}

=== Number of Disturbance Interaction Types ===
The number of different [[Mummy|disturbed dead]] that can exist in the world. Setting this to zero should prevent any mummy from appearing{{verify}}, but it will not prevent the creation of [[tomb]]s.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DISTURBANCE_INTERACTION_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[DISTURBANCE_INTERACTION_NUMBER:10]</nowiki></tt>
| 0 to 1000
|}

=== Number of Evil Cloud / Evil Rain Types ===

This number specifies how many [[Weather#Evil weather|various face-melting, eye-boiling, and zombifyingly-fun]] clouds of pure evil may appear in your world. Setting this to zero means you no longer will ever have to deal with encroaching dust walls of doom in that world. It is generally advised to keep this value low...

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EVIL_CLOUD_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[EVIL_CLOUD_NUMBER:45]</nowiki></tt>
| 0 to 1000
|}

The latter number states how many different types of green-ooze drenchers, disconcerting blood-showers, and sickly yellow slime-baths can occur in your world. Compared to evil clouds though, this one hardly is worth stressing out about, usually.... Setting this to zero means the only semi-solid to fully-liquid fluids to fall from the sky will be pure H2O.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EVIL_RAIN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[EVIL_RAIN_NUMBER:352]</nowiki></tt>
| 0 to 1000
|}

=== Generate Divine Materials ===
This turns the generation of [[Divine_metal|divine metals]] on or off. It does not influence the creation of [[vault]]s. Probably determines whenever or not using divination dice spawns weapons.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GENERATE_DIVINE_MATERIALS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[GENERATE_DIVINE_MATERIALS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Generate Mythical Materials ===

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GENERATE_MYTHICAL_MATERIALS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[GENERATE_MYTHICAL_MATERIALS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Mythical Healing ===

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALLOW_MYTHICAL_HEALING:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_MYTHICAL_HEALING:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Divination, Experiments, and Necromancy types ===
These allow or disallow [[die|divination]], demon or necromancer [[experiment]]s, and the more advanced [[necromancer]] abilities.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALLOW_DIVINATION:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_DIVINATION:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_DEMONIC_EXPERIMENTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_DEMONIC_EXPERIMENTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_EXPERIMENTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_EXPERIMENTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_LIEUTENANTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_LIEUTENANTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_GHOULS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_GHOULS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_SUMMONS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_SUMMONS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Desired Good/Evil Square Counts ===

These values change the amount of [[Surroundings#Good|good or evil]] tiles on the map, depending on the size of the region they are being considered for. The counts are for all tiles in all subregions of a given size considered together, ''not'' counts for each subregion considered separately (all tiles in the same subregion share the same [[surroundings]] values).

As used here, a "subregion" is a named world area. Subregion names and locations for a generated world are viewable in legends mode under "Regions". Subregions are classified by size the same way for all map sizes: 1-24 tiles is Small, 25-99 tiles is Medium, and 100+ tiles is Large.

The counts used here will always be restricted to regions of the given size, no matter how large the count. Also, the count is more of a goal than a minimum or maximum. As a result, you can end up with many more or many fewer than the requested number of squares in some situations. In particular, if you have something like a case where only 3 large regions exist in a world, and you request "1 evil square" in large regions, you will end up with one of the large regions being ''entirely evil''. So any non-zero value in one of these settings essentially means "force at least one region of this size to be all good/evil."

Note that the "evilness" of evil biomes is also impacted by savagery. Certain civilizations cannot exist in good and/or evil squares, so too many of one or the other may limit the size of certain types of civilizations - dwarves, for example, need non-aligned biomes. Creating too many evil biomes seems to lead to the danger of many civilizations' early extinction.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GOOD_SQ_COUNTS::<med region>:<lg region>]</nowiki></tt>
| <tt><nowiki>[GOOD_SQ_COUNTS:100:1000:2000]</nowiki></tt>
| rowspan="2" | Set count to zero to disable for that region size.
|-
| <tt><nowiki>[EVIL_SQ_COUNTS::<med region>:<lg region>]</nowiki></tt>
| <tt><nowiki>[EVIL_SQ_COUNTS:100:1000:2000]</nowiki></tt>
|}

=== Minimum Biome Square Counts ===

These numbers control whether or not a world will be rejected based on a lack of different [[biome|biomes]]. Raising these numbers will '''not''' automatically generate the given number of squares of the given biome! For a biome to exist, certain conditions like elevation and rainfall must exist.

These parameters simply filter out worlds that (for example) randomly fail to have enough high elevation squares to support a given number of mountains, etc. Some settings may cause worlds to always be rejected. For example, if for some reason the maximum elevation parameter is set to a value below what will support mountain biomes, it will be impossible to satisfy a non-zero requirement for mountain squares. The same principle goes for other conditions and biomes such as low elevations and oceans, etc.

Certain civilizations require different biomes to exist (such as dwarves and mountains), so eliminating certain biomes will make it impossible for certain civilizations to form.

These parameters often result in infinite world rejection problems. See [[World rejection]] for information on solving problems related to worlds always being rejected due to one or more of these parameters.

0 means no minimum for rejection - setting it to 0 does not guarantee 0 squares of that biome.

==== Biome Type Requirement Table ====

Terrain requirements for various biomes are described below.{{Verify}} Note that some of the exact ranges are unknown.

{| {{prettytable}}
|- bgcolor="#dddddd"
! rowspan="2" | Biome
! colspan="4" | Terrain Requirement
|-
! Elevation
! Rainfall
! Temperature
! Drainage
|-
| Swamp/Marsh
| 100-299
| 33-100
| Non-Freezing
| 0-32
|-
| Desert/Badland
| 100-299
| 0-9
| non-freezing
| note1
|-
| Forest
| 100-299
| 66-100
| non-freezing
| 66-100
|-
| Mountains
| 300-400
| N/A
| N/A
| N/A
|-
| Ocean
| 0-99
| N/A
| N/A
| N/A
|-
| Glacier
| 100-299
| N/A
| Freezing
| 80(?)-100
|-
| Tundra
| 100-299
| N/A
| Freezing
| 0-66
|-
| Grassland
| 100-299
| 0-66
| Non-Freezing
| 0-66
|-
| Hills
| 100-299
| 0-66
| Non-Freezing
| 66-100
|}
note1 drainage: 00-32 sand desert, 33-49 rocky wasteland, 50-65 rocky wasteland but different characters/appearance, 66-100 badlands

==== Minimum Initial Square Count ====

'''Note: The exclusive purpose of these parameters is to cause world rejection.'''

This is the minimum number of squares of the given biome that must exist before things like erosion take place. One thing to keep in mind is the maximum number of squares on a map of a given size - if the total number of squares on a map is lower than the sum of all square count parameters, then you will get infinite world rejection.

To determine the number of squares on a map, just multiply the dimensions. In practice these parameters will need to sum to lower than the maximum because some space is needed for "slack".

{| {{prettytable}}
|- bgcolor="#dddddd"
! Map Size
! Number of Squares
|-
| 17×17
| 289
|-
| 33×33
| 1089
|-
| 65×65
| 4225
|-
| 129×129
| 16614
|-
| 257×257
| 66049
|}

==== Minimum Initial Region Count ====

This is the minimum number of regions of contiguous biome squares that must exist before other processes such as erosion take place.

==== Minimum Final Region Count ====

This many regions of the given biome must exist after erosion and similar phases of generation have been completed.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[REGION_COUNTS:SWAMP:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:SWAMP:1032:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:DESERT:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:DESERT:1032:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:FOREST:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:FOREST:4128:13:12]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:MOUNTAINS:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:MOUNTAINS:8256:9:9]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:OCEAN:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:OCEAN:8256:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:GLACIER:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:GLACIER:0:0:0]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:TUNDRA:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:TUNDRA:0:0:0]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:GRASSLAND:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:GRASSLAND:8256:13:12]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:HILLS:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:HILLS:8256:13:12]</nowiki></tt>
|}

=== Erosion Cycle Count ===

Tells the world generator how long the world has to erode its tall peaks down to mountainsides during the 'running rivers...' stage of world creation. The higher this number, the less jagged the world will be, and the more wide the major rivers will be. If you use the maximum number, your mountains will dissolve before your eyes into plains which can lead to rejections if there aren't enough mountains to use for river start points and dwarven civilization origin points.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EROSION_CYCLE_COUNT:<number>]</nowiki></tt>
| <tt><nowiki>[EROSION_CYCLE_COUNT:250]</nowiki></tt>
| Range: 0 to 1000
|}

=== Minimum/Desired River Start Locations ===

This is the minimum number of riverheads that must exist before and after erosion takes place. Worlds will be rejected if they fail to meet these numbers. As with minimum biome counts, raising this number doesn't automatically create this many riverheads. Other conditions like terrain and rainfall must exist for rivers to form.

Extremely high pre-erosion values speed erosion greatly, while low post erosion values are useful for limiting rejects due to lack of river origin points. One can try the 800 value to get more lakes.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[RIVER_MINS:<min pre-erosion>:<des post-erosion>]</nowiki></tt>
| <tt><nowiki>[RIVER_MINS:200:400]</nowiki></tt>
| Range: 0 to 800
|}

=== Periodically Erode Extreme Cliffs ===

If enabled, makes every impassable rock wall into a series of ramps. Some prefer to pump up erosion to about 250, and turn the "Desired pre-erosion river count" to 0 for good erosion and no extra canyons.

Normally this is set to Yes (1).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PERIODICALLY_ERODE_EXTREMES:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[PERIODICALLY_ERODE_EXTREMES:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Do Orographic Precipitation and Rain Shadows ===

Toggle that allows terrain height to affect rainfall. For example, moist air coming from the ocean blows over the land. As the terrain gets higher, it forces the moist air up, causing it to rain on the seaward side of a mountain. Eventually, all the rain has fallen if the mountain is tall enough. So, when the breeze goes over the top, there's no moisture left to fall on the other side, creating a rain-shadow. In the current version, regions where drainage is above 50 will also create rain shadows, regardless of the underlying biome and elevation.{{cite forum|140685/5484064}}

Turning this on should create a tendency for more extreme rainfall in regions, creating more forests, deserts, marshlands, and grasslands. Also note that it can create rainfall outside of min-max rainfall settings, so even in a world with a 0 max rainfall you may get rainfall biomes. Turning it off should result in more controllable, less complex rainfall conditions based on rainfall parameters as it adds a random element which can distort or otherwise mess up the climates on a pregenerated map.

This should be disabled if you're importing a map or using a preset map file that has weather.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[OROGRAPHIC_PRECIPITATION:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[OROGRAPHIC_PRECIPITATION:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Maximum Number of Subregions ===

This is the number of separate biomes (the flashing regions you see on embark when you hit F1, F2, etc. when there's more than one biome on the embark location) that are allowed to exist on the entire map.

Setting this to very low values will result in numerous rejections depending on [[#X and Y Variance|variance parameters]]. If variance values are set to high numbers, many small biomes will be created causing rejection if this parameter value is not increased beyond the default.

Increasing the value of this tag is often a must when generating "patchwork" worlds with lots of biome variance, but simply increasing it without increasing variance parameters will not guarantee more biomes.

It is also interesting to note that the maximum subregions is 5000 which is more than the total number of squares for a pocket or small map. However, for a medium or large map (16641 or 66049 squares) it quickly becomes a mere fraction of the total number of possible subregions. In fact it would be quite easy on a large map to end up with far too many subregions and get endless rejections of this type.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SUBREGION_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[SUBREGION_MAX:2750]</nowiki></tt>
| Range: 1 to 5000
|}

=== Cavern Parameters ===
[[Caverns]] are the hollow areas underground, which dwarves tend to encounter when they're digging around. The '''Cavern Layer Number''' parameter determines how many cavern systems will be generated, not including the magma layer or the Bottom layer. Defaults to three - setting it to lower values could help FPS. Setting it to 2 will merge cavern 3 species into the 2nd cavern, and setting it to 1 will merge all into one cavern. However, disabling them entirely by setting it to 0 will make it impossible to grow any underground plants, as none will exist for your civilization to cultivate, nor will they be available on embark.

*Setting caverns to a sub-3 number (Spoiler, highlight to view) erases about one-third of HFS spires{{Bug|10267}} and prevents dig deep disasters. Additionally, random plant or animal species can be more frequently absent.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_COUNT:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_COUNT:3]</nowiki></tt>
| Range: 0 to 3
|}

==== Cavern Layout Parameters ====

Open caverns and dense passageways are not mutually exclusive. When both are raised, bizarre results can occur, such as layers showing a combination of open caverns, a cluster of network passages, and natural walls sprinkling the inside of an otherwise open cavern. [http://www.bay12forums.com/smf/index.php?topic=76355.msg1936859#msg1936859 Reference]

If you want the largest open spaces possible, then decrease the density and increase the openness. If you want a labyrinth of passageways, lower the openness and raise the passage density.

Another interesting note about the cavern layers is that the seed and number of demon types affect the layout of the caverns.

<gallery widths=200 heights=200 perrow=2>
File:Open00Density100.jpg|Cavern slice with Openness of 0 and Density of 100
File:Open100Density00.jpg|Cavern slice with Openness of 100 and Density of 0
File:Open100Density100.jpg|Cavern slice with Openness of 100 and Density of 100
File:Open50Density50.jpg|Cavern slice with Openness of 50 and Density of 50
</gallery>

===== Layer Openness min/max =====

Dictates the size of cavern passages. When Passage Density (see below) is set to minimum (0), caverns will be open expanses. Raising the maximum will increase the size of the caverns.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MAX:100]</nowiki></tt>
|}

===== Layer Passage Density min/max =====

Determines how many passages form the cavern. If openness (see above) is set to minimum and density increased, then you will get a maze-like network of small criss-crossing passages. Raising the values further increases the number of the maze-like passages.

Caverns will be large, open spaces at 0, and comprised of many small vertical shafts of rock at 100. Setting both values to be the same results in a uniform look for the caverns.{{Verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MAX:100]</nowiki></tt>
|}

===== Layer Water min/max =====

Determines the minimum and maximum percentage of water each cavern can contain.

Caverns with a water level of 10 or higher can support creatures and plants from the "Subterranean Water" biome, and caverns with a water level of 90 or lower can support the "Subterranean Chasm" biome; levels of 10-90 support ''both'' biomes, while levels below 10 or above 90 support only one.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_WATER_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_WATER_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_WATER_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_WATER_MAX:100]</nowiki></tt>
|}

==== Magma Layer ====

This parameter controls whether the [[magma sea]] exists.

Setting 1/Yes causes the magma layer to exist, value 0/No prevents it. Appears not to have any impact on volcanoes nor volcanism, so even if 0/No, there will still be embark locations with magma. If a [[volcano]] exists, it appears to always tap the magma sea, but the magma sea will not be revealed by revealing the volcano.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[HAVE_BOTTOM_LAYER_1:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[HAVE_BOTTOM_LAYER_1:1]</nowiki></tt>
|}

==== Bottom Layer ====

Determines if the space below the magma sea exists. If Yes the "HFS" layer is always present. Normally you want to leave this set to Yes for maximum fun.

If enabled, this will force the magma layer above it.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[HAVE_BOTTOM_LAYER_2:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[HAVE_BOTTOM_LAYER_2:1]</nowiki></tt>
|}

=== Z Levels (Depth) Settings ===

These parameters control the "thickness" of various "layers" on the map. Note that a "layer" in this case does not refer to one Z-level, but refers to a number of related Z-levels such as "levels above ground".

The following table assumes that you have 3 cavern layers. (out of a minimum of 0-3) The Levels Above Layer settings control how many Z-Levels are above each layer. A layer may itself consist of multiple Z-Levels (and almost always does).

{|style="margin:1em 1em 1em 0;background:#F9F9F9;border:1px #AAA solid;border-collapse:collapse;" class="wikitable"
|-style="background:#F2F2F2;text-align:center;"
!style="border:1px #AAA solid;padding:0.2em;" width="120"|Setting Name
!style="border:1px #AAA solid;padding:0.2em;" width="200"|Token
!style="border:1px #AAA solid;padding:0.2em;"| Description
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Ground
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_GROUND:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| The number of Z-levels of air above the highest surface level. Has no impact on how many Z-levels deep the surface layer is.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above layer 1
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_1:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of stone above the first cavern layer. Making this higher will guarantee ''at least'' that many levels to build your fortress, but will have no impact on how many z-levels thick the surface layer is. Also, the top of a cavern may be higher than the rest of a cavern, so in practice there will be more "solid" levels than this above the cavern.
As of version 0.31.25 this setting is inaccurate. The actual number of z-levels may vary in a range of approx. ±5, which may result in non-existence of any solid z-levels between a surface layer and first cavern layer.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 2
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_2:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very top of the second cavern and the very bottom of the first cavern.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 3
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_3:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very top of the third cavern and the very bottom of the second cavern.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 4
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_4:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very highest magma and the very bottom of the third cavern. Spoiler Hidden (select invisible text to read): Making this high will give a large area for HFS veins, so that it never touches caverns, giving more to mine '''if''' it was impacting the cavern previously.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 5
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_5:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Uncertain. May control the number of levels of "Semi Molten Rock" between HFS and Magma, may control number of levels of magma, may impact both. In experimentation, the overall depth of all magma sea and semi-molten rock levels appears to increase, but not consistent enough to say for certain. Only valid if Magma Layer present. Spoiler Hidden:Often the HFS vein will only extend as high as the highest magma, making this the only guaranteed way to increase amount of HFS to mine, but unfortunately also creating enormous useless semi-molten z-levels
|-
|style="border:1px #AAA solid;padding:0.2em;"| At Bottom
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_AT_BOTTOM:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Appears to be number of levels of HFS chamber. Only valid if Bottom Layer present, often having no impact. Values larger than default result in strange things.
|}

Some implications:
* The number of surface layers (e.g. soil), at this time, cannot be controlled. For example, on a map with 1 layer of peat, then a layer of silt, then a layer of obsidian, there is no control to let you increase either one to be, say, 20 z-levels. (though you may get lucky with the obsidian).
* There can be multiple stone layers between the cavern and the surface, so, increasing Levels Above Layer 1 may give you more conglomerate or more granite, and you have no control over which stone layer spans those Z-levels.
* The layers shown on embark span across the cavern layers in an unknown and inconsistent way. Sometimes those 10 different layers of stone are evenly distributed over your 400 z-level deep map, sometimes the first 9 get 1 z-level each and the last gets the other 391 levels. No way to control found yet.
* The HFS chamber, if present, will always extend into the rock layers, and appears to always make contact with the bottom cave. Large values for levels above layer 5 and layer 4 can result in enormous chambers, but the number of levels at the top (the part with undead) appears to be unaffected.
* Unconfirmed whether number of levels between caverns has any impact on cavern height. There will be connecting ramps and/or shafts between cavern layers no matter how many levels are between them.
* '''Very Important''': These values appear to apply across a whole 16x16 region, not just embark areas. That means that if a 16x16 region is completely flat, but has one tall mountain in one far corner, even if you set Levels Above Ground low (e.g. 2 z-levels) you still have all the empty air of the highest mountain in every embark tile (e.g. 200 z-levels). Also can happen to the semi-molten layer, and can lead to unexpected behavior.
* Very large or small values can cause strange things to happen.

=== Minimum/Maximum Natural Cave Size ===
It's not clear what effect these currently have, other than changing them can change the location of caves somewhat.{{verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVE_MIN_SIZE:<number>]</nowiki></tt>
| <tt><nowiki>[CAVE_MIN_SIZE:5]</nowiki></tt>
| rowspan="2" | Range: 1 to 500
|-
| <tt><nowiki>[CAVE_MAX_SIZE:<number>]</nowiki></tt>
| <tt><nowiki>[CAVE_MAX_SIZE:25]</nowiki></tt>
|}

=== Number of Caves ===
The number of caves generated in mountainous and non-mountainous regions, mountain caves will always be generated on the edge of mountain ranges next to non-mountainous regions. Lurking [[kobold]]s set up shop in caves, and store their stolen items there - a setting of 0 in both will stop kobold civilizations from appearing. Special note: a cave is not initially a [[lair]], although beasts can later use them as their lair.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[MOUNTAIN_CAVE_MIN:100]</nowiki></tt>
| rowspan="2" | Range: 0 to 800
|-
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:200]</nowiki></tt>
|}

=== Number of Mythical Sites ===
The number of [[mysterious dungeon|mysterious sites]] generated around the world. The extended effects of setting this to 0 has not been determined{{verify|is chosen still available? is quest still given? etc.}}.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MYTHICAL_SITE_NUM:<number>]</nowiki></tt>
| <tt><nowiki>[MYTHICAL_SITE_NUM:200]</nowiki></tt>
| rowspan="2" | Range: 0 to 800
|}

=== Make Caves Visible ===
If set to no (default) then the location of caves will not be marked on the map. If set to yes, caves will appear on the map so that they may be sought out or avoided as desired.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALL_CAVES_VISIBLE:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALL_CAVES_VISIBLE:0]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Init Options to Show Tunnels ===

If enabled, you will be able to see the underground tunnels often built by dwarves on the world map, and they will appear as black lines, similar to roads.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SHOW_EMBARK_TUNNEL:<0-2>]</nowiki></tt>
| <tt><nowiki>[SHOW_EMBARK_TUNNEL:2]</nowiki></tt>
| 0 = No 1 = Only in Finder 2 = Always
|}

=== Number of Civilizations ===

This number of [[civilization]]s will be placed on the map before history generation begins. These civilizations may later die out due to historical events. It is noteworthy that the chance for any given civilization to be destroyed through megabeasts decreases with a higher total number of civilizations present[http://www.bay12forums.com/smf/index.php?PHPSESSID=7348f68f41a9659443c05b2acf534e6c&topic=112465.15 data]. The five races are dwarf, elf, human, goblin, and kobold; they will generally be placed in equal numbers until the quota has been reached. If there are not enough biomes or other worldgen prerequisites for an even distribution, certain civs will be much more or less frequent than others[http://www.bay12forums.com/smf/index.php?PHPSESSID=7348f68f41a9659443c05b2acf534e6c&topic=112465.15 data]. If there is an odd number of civs (not divisible by 5), then the remainder is distributed randomly. Kobold civs require caves to be placed; if no caves exist, then kobolds are skipped and will not appear. This does not cause rejections [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415125#msg3415125 data]. Goblin civilizations require multiple demons, see the [[#Number_of_Demon_Types|number of demon types]] section above.

Note that a high value here can cause lots of map rejections, particularly on smaller maps as there simply isn't enough room or regions to put them all in.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_NUMBER:40]</nowiki></tt>
| Range: 0 to 300
|}

=== Playable Civilization Required ===

If this is set to yes (default) then worlds will be rejected if no civilization with [[Entity token|CIV_CONTROLLABLE]] can be placed. In an unmodded game, only the dwarves have this token.

If set to no, the result may be a world that cannot be played in Fortress Mode.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PLAYABLE_CIVILIZATION_REQUIRED:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[PLAYABLE_CIVILIZATION_REQUIRED:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Minimum Number of Mid/Low/High Characteristic Squares ===

Sets the minimum possible number of squares of certain ranges of each of the region qualities, such as elevation, rain, drainage, volcanism, savagery, and temperature. These need to be changed to reflect your regional meshes and weights, and are responsible for a HUGE number of map rejections. These values can all be set to 0 for much fewer map rejections, particularly in the case of more wacky, non-standard maps.

These values will cause worlds to be rejected unless at least the given number of squares of the given type are randomly generated. Setting these values too high could result in worlds always being rejected if other parameters such as the maximum/minimums for elevation, etc., don't allow enough of those squares to get generated.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[ELEVATION_RANGES:8256:16512:8256]</nowiki></tt>
| rowspan="5" | Minimum number of squares that must have low, medium, and high amounts of the given attribute. 
0 = No minimum
|-
| <tt><nowiki>[RAIN_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[RAIN_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[DRAINAGE_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[SAVAGERY_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[VOLCANISM_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM_RANGES:8256:16512:8256]</nowiki></tt>
|}

==World rejection==

:''Main article: [[World rejection]]''

If you are having the common problem of generated worlds always being rejected by the world generator, see [[v0.31:World rejection|Solving World Rejection Problems (v0.31 page)]] as it contains many detailed suggestions on how to troubleshoot and solve these issues.

== Parameter set examples ==

If you're trying to do something specific, then the [[Worldgen examples]] - complete parameter sets that can be copied directly into your ''world_gen.txt'' file and customized as desired - might be helpful.
If none of the examples suit your needs, [[Worldgen tricks]] has strategies and tips on making a world just right for you.

For many, many more examples see:
* [http://www.bay12forums.com/smf/index.php?topic=101280 DF2012 (v0.34) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=140180 DF2014 (v0.40) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=168543.0 DF2014 (v0.44.02+) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=175538 DF2014 (v0.47.01+) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=180805.0 DF2022 (v0.50.01+) WorldGen "Cookbook" Thread]

{{World}}

Zone

2026-04-04T21:55:36Z

Ziusudra: /* Usage */ added link to value of overlapping rooms section, filling from the furniture, DFHack burial tool

{{Quality|Masterwork}}
{{av}}
[[Image:Zones menu v50.03.png|right]]
A '''zone''' is an area where your citizens will work, socialize, rest, or perform specific duties, such as [[fishing]], dumping objects, or collecting [[water]].

== Usage ==
Zones can be placed in any [[revealed tile]], including in [[open space]], over a [[river]], on top of a [[building]] or [[stockpile]], or a [[wall]]. They are placed in one of three ways: rectangular, draw, or (for some zones) multi. From within the Zones [[menu]] ({{menu icon|z}}), selecting a zone type will open the zone creation menu. From here, you can select whether to create a zone in a rectangle (at which point you click the two corners for the zone) or simply draw it (where clicking adds single squares to the zone). You can enable erasing at any time and use rectangle and draw to remove squares from the zone. The number shown indicates how many selected floor tiles can be used for that type of zone. After selecting some tiles, two numbers are shown with a plus sign (+) between; the first is the number of valid tiles already in the zone, and the second is how many would be added with the new selection or tile.

Unlike [[stockpiles]], multiple zones can overlap, though this can greatly reduce their value, see [[Zone#Overlapping_Rooms|below]].

For zone types that require a piece of furniture, you can change from Paint to Multi mode, in which you can draw a rectangle over multiple rooms, and each room valid for that zone type will be a separate zone. The number shown is the number of zones created in the last rectangle drawn, and the undo button will only undo the last rectangle created. This will define each room from the furniture building (either built or only designated) out to the walls (including diagonally); this requires some way for the game to know where the room ends, i.e. walls all around and a way in and out, either a door, stair, or ramp. The [[DFHack]] tool <code>[https://docs.dfhack.org/en/stable/docs/tools/burial.html burial]</code> can create a 1×1 tomb zone for each built coffin, without the need for walls or a door.

Some zones can be further specified into [[location]]s after creation. To do this, first create the relevant zone, then click the Add Location button ([[File:Ui location add.png]]) to further specify it as a location. Multiple zones can be added to a single location, allowing them to span multiple rooms.

In some cases (pen/pasture, pit/pond) additional orders can then be set from the same menu. The location of a zone is only visible while in the Zones menu, and any object lying on the ground will hide the presence of a zone tile. The size of a zone is unlimited.

== Zone Types ==

=== Meeting area ===
[[File:meeting_icon_preview.png|right]]'''Meeting area zones''' are zones in which idle dwarves and animals will congregate. After a meeting area is designated, it can be left as is, or it can be made into a [[tavern]], [[temple]], [[library]], [[guildhall]] or [[hospital]], but animals will not congegrate to meeting areas, which are assigned to certain locations like temple, tavern or guildhall (and presumably, but not yet tested, library or hospital). Additionally, [[immigration|immigrants]] will collect at a meeting area until their "migrant" status wears off. Note that the [[wagon (embark)|wagon]] you [[embark|arrive with]] constitutes a meeting area until you designate the first meeting area of your own (and it will, at least as long as the embark wagon is around, constitute a meeting area for animals, if all other meeting areas are assigned to locations to which animals do not congregate to). If you start in hostile surroundings, it is important to do so, so as to get your dwarves and animals out of danger quickly. It is a good idea to have at least one meeting area of one form or another: It allows you to make off-duty dwarves and animals gather in an area where they are not vulnerable within the fortress. A meeting area filled with dwarves increases the [[social skill]]s of idlers. It makes idle dwarves a little less idle. Because almost every dwarf visits a meeting area at least occasionally, it's an ideal place to site valuable objects and buildings. A meeting area exposed to sunlight will additionally prevent dwarves from becoming [[cave adaptation|cave-adapted]]. Note that having dwarves socialize will often result in them forming [[relationship]]s.

It is not advisable to have animals mill around in crowded meeting areas for a prolonged time, as they will pick fights with dwarves and other animals. While this may be negligible in the case of a hen, it also applies to your [[Dog#War dogs|war dogs]] (although this can be partly beneficial, since all your dwarves will get combat experience from being bitten occasionally, especially the children, who mill around constantly).

If the meeting area is made a guildhall or a temple, the icon of the zone will change depending on the room's quality. For a guildhall, the icons are [[File:meeting_quality0_sprite.png|19px]] and [[File:meeting_quality1_sprite.png|19px]]. For a temple, the icons are [[File:temple_quality0_sprite.png|20px]], [[File:temple_quality1_sprite.png|20px]] and [[File:temple_quality2_sprite.png|20px]]. Dwarves may petition for these types of rooms of varying qualities.

=== Office ===
{{main|Office}}

[[File:office_medium_icon.png|right]]An office is a zone required by some [[Noble|nobles]], and requires a [[chair]]. [[Manager|Managers]] will use the chair to validate and check [[work orders]]. A [[bookkeeper]] will use the office to update the [[stock]]records and increase the precision of the records. A dwarf with an office assigned will sometimes [[eat]] in their own office if there is no communal [[dining hall]] designated in the fortress, but this does not provide any happy [[thought]], no matter how [[#Quality_and_value|luxuriously decorated]] the office may be, and may even generate a bad thought if the chair doesn't have a [[table]] adjacent to it.

=== Bedroom ===
{{main|Bedroom}}

[[File:bedroom_medium_icon.png|right]]A bedroom is a zone where a single dwarf (and possibly their spouse and children) will sleep and store their belongings in. Requires a [[bed]]. A cabinet can be built for the dwarf to store their [[Wear|old]] clothing; and a chest for dwarves to store their belongings like [[coins]], [[Finished Goods|rings, scepters]] etc. A dwarf with no cabinet, or with low [[Personality facet#ORDERLINESS|orderliness]] personality facet will scatter their old clothing everywhere.

=== Dormitory ===
{{main|Dormitory}}

[[File:bedroom_medium_icon.png|right]]A dormitory is a zone containing multiple [[Bed|beds]] where all dwarves that do not have a bedroom assigned to them will sleep. However, sleeping in a dormitory will generate a negative [[thought]] (embarrassed after sleeping without a proper room).

=== Dining hall ===
{{main|Dining hall}}

[[File:dining_medium_icon.png|right]]A Dining Hall is a zone where dwarves go to eat. Requires one or more [[Table|tables]].

=== Barracks ===
{{main|Barracks}}

[[File:barracks_medium_icon.png|right]]A barracks zone is a zone where a [[military]] will go to sleep, train, or store their equipment.

=== Pen/Pasture ===
{{main|Pasture}}

[[File:pasture_medium_icon.png|right]]A pen or a pasture is used to contain tame animals. Once one is created, animals must be assigned to it individually from the zone information menu. Dwarves will drag the assigned animals to the pen or pasture automatically. Domestic animals tend to aggregate at [[meeting area]]s instead, as will herbivorous ones, which will probably lead to starvation, unless your meeting area is overgrown with [[grass]] or fungi for some reason. '''Any tame creature with the "grazer" token in the raws should be assigned to a pasture. This includes mules, cows, goats, horses, yaks, unicorns etc.''' Animals will not typically wander out of their assigned pasture even if it is not walled in, however animals will abandon their posts and will have to be dragged back to them if they are threatened by enemies, and an exposed pasture may lead to premature slaughter at the hands of invaders. Since pets can be assigned to pen/pastures and a zone can be created under a [[dwarven atom smasher]], this is one of the easiest ways to prevent [[catsplosion]]s.

=== Archery range ===
{{main|Archery range}}

[[File:archery_medium_icon.png|right]]An archery range is used by [[marksdwarves]] (or [[Bow|bowdwarves]] and [[blowgun|blowgunners]] by editing the raw). A marksdwarf will pick up bolts nearest to them And then shoot at the target. Upon depleting the bolts, the markdwarf will gain a happy thought(feels pleasure after practicing at an archery range). The marksdwarf's XP gain by practicing in an archery range is only [[Experience|half the amount]] compared to using a [[Advanced Marksdwarf Training Guide|live target]]. but it has the advantages of being easy to set up and needing much less micromanagement. Note that markdwarves cannot shoot adjacent to the [[archery target]]. and there must be at least 1 tile of walkable perimeter that is from the target in order for archery practice to happen.

=== Pit/Pond ===
{{TipBox2|titlebg=#c00|textbg=#ffd|[[File:warning_icon.png|25px]] Warning!|There have been multiple reports of hostile creatures escaping confinement while pitting. Use of forbidden tightly closed hatches above every hole appears to prevent escape.
See [[Mass pitting]] for more. If there are walls under the hole's edges rather than open space, they will allow [[Climber|grabbing and climbing]], so you may want to dig out an overhang, or at least [[Smoothing|smooth]] these walls.
}}

[[File:pit_medium_icon.png|right]]A Pit/Pond requires a [[ramp]] or hole with adjacent flooring on which a dwarf can stand. Designate the zone from the top of the ramp or hole, such that the zone designation is floating in the open space above the floor of the pit/pond. By default, the zone will be a pit. To toggle between pit and pond, press corresponding icon in zone information menu ([[File:Ui Pit.png|24px]]/[[File:Ui Pond.png|24px]]).

Creatures can be assigned to a pit/pond ([[File:Ui assign creature.png|24px]]). If the creature is [[cage]]d, a dwarf will release it from the cage (rather than bringing the cage to the pit). The dwarf will lead the beast to the pit and throw it in. If the pit is a ramp rather than a hole, the creature will then wander back out, as it will if the pit has some other exit path (which would include straight back up the hole for flying creatures). Note that some (or possibly all?) hostile creatures may escape on being released from their cage, possibly attacking the dwarf who opened the cage.
Additionally, dwarves refuse to pit dwarves, hostile or not.
{{Colored Notice Box||See [[Mass pitting]] for more information on pit design involving hostile creatures.}}

The only real difference between a pit and a pond is that dwarves will attempt to fill a pond with [[water]], carried by [[bucket]] from a water source. They will stand on the floor adjacent to the top of the ramp or hole, and toss the water onto the ramp or into the hole. This works even if there is a forbidden [[floor hatch]] covering the hole. Each bucketful increases the depth of the water in the tile below by 1/7. Once the water is dumped from the bucket, the dwarf will either drop the bucket and perform a different task, or choose to fill a pond zone tile again using the bucket (s)he currently holds. Dwarves will stop scheduling the Fill Pond job when the water depth reaches 6/7. Specifying a pond zone is one technique used for [[irrigation]], in order to make [[mud]] for [[farming]] on areas without soil. Currently, no matter how large the designated pond area, only one dwarf at a time will try to fill the pond. In order to fill a large area quickly, it is necessary to designate multiple smaller pond zones (or several zones overlapping the same area).

To make obsidian or cleanse stagnant water with fresh water, the pond zone must be designated an extra tile above the magma/stagnant pool, so that the water falls for a full tile before contacting the surface.

If you have more than one pond designated as a water source, your dwarves may endlessly try to fill each pond with the other pond's water, making a loop of useless duty; this may be undesirable, although otherwise-idle dwarves performing this task won't be making any friends. Only dwarves with the [[Hauling#Water_hauling|Water hauling]] labor enabled will fill ponds.

Artificial ponds are considered to be the same as Murky Pools - you'll only catch pond fish from them (i.e. turtles). If you want to catch river fish, you must fish from the river's original tiles (or perform some DFHack trickery to mark your new tiles as being part of the river).

=== Garbage Dump ===
{{main|Garbage dump}}
[[File:trash_medium_icon.png|right]]Garbage dump zones are areas in which dwarves will throw items marked for dumping - either by manual setting of dump status from item information menu, or {{menu icon|i|p}} (bulk dumping; note that this designates ''all'' items on the tiles for dumping, even built [[furniture]] and items inside [[Storage|container]]s). Garbage dumps are ''not'' the same as [[Refuse#Refuse|refuse]] stockpiles, which can be designated to accept specific type(s) of refuse, such as animal [[corpse]]s or [[bones]], and then are automatically filled by haulers whenever the items appear on the map. Despite the name, garbage dump zones are useful for many things beyond [[garbage disposal]]; they can create [[quantum stockpile]]s, transport materials to a job site, send items to the [[trade depot]] when no caravan is present, [[trap design#Falling_debris_trap|drop rocks]] on enemies below, and numerous other uses.

Be aware that if a garbage zone is designated beside a cliff or hole (any open space, either natural or dwarf-made), garbage will be thrown into the open space. If a dump is designated over a [[ramp]] to the next level down, some dwarves may walk down the ramp to dump their items, while others may just toss their items down from above and onto those dwarves, injuring or killing them.

The garbage dump may be inappropriately named, as it's more of a matter compression zone. The specifics are beyond human understanding; however, dwarves are in fact capable of compressing an infinite amount of matter into only one tile, as long as it is specified as a garbage dump. If, for some reason [[Main:Urist|Urist]] is yet again incapable of locating his favorite pair of, say, troll fur socks, he should think to look among the black hole of matter that is the nearest garbage dump, as they could be snugly lodged between a few billion rocks.

=== Water source ===
[[File:water_medium_icon.png|right]]Dwarves will use these zones to draw water, to satisfy booze-less [[thirst]], to tend to another thirsty dwarf (with the Give Water job), or to fill a [[#Pit/Pond|Pond zone]]. Only tiles ''adjacent'' to water qualify as usable water sources - thus, if you want to place a single-tile zone, place the zone onto a ground tile next to the water, not over the water itself. This zone should ''not'' be used with [[well]]s - this is redundant, as they are already considered their own water source.

If this zone does not exist, any water source can be used. If at least one water source zone exists, then dwarves will only get water from these zones.

Remember that natural bodies of water usually contain aquatic wildlife, some of which may attack your dwarves, or at least spook civilians, and interrupt their tasks. Often it may be best to simply designate a safe body of water as a water source so dwarves aren't allowed to drink/fish anywhere else.

Normally, creatures cannot attack any dwarves through a [[well]] so long as the well is not on the same z-level as the top of the lake/river, thus building one will allow your dwarves safe access to water inhabited by vicious animals (as long as those can't climb).

When dangerous fish are found in the river, one solution is to dig an artificial [[channel]] and place a [[grate]] between it and the river proper, as fish cannot swim through grates, but grates still allow water through. However, beware [[Grate#Bugs|the bug with flow and ''wall'' grates]] - taking water via U-shaped tunnel capped with ''floor'' grates may be safer. If you use a completely isolated smooth reservoir filled with [[pump]]-filtered water, it may still need protection, since the dwarf operating a pump stands right next to its water source tile.
Placing floor grates over the river or channel may also protect dwarves by preventing them from falling in.

[[Carp]] and other non-[[vermin]] fish suffocate if they are not in water, so in some situations it might be possible to pump the water out of a lake or pond. Conversely, an open water body (river or sea) not only cannot be subjected to temporary drainage, but even if there isn't anything dangerous right now, it may arrive later.

=== Animal Training ===
{{main|Animal Training}}
[[File:animaltraining_medium_icon.png|right]]An animal training zone allows [[Animal trainer|animal training]]. Animals cannot be trained, unless they are in a training zone or [[pasture]], or on a [[restraint]]. To be tamed, they must be in a [[cage]].

For making an animal training zone, it is advisable to create a small room with a [[door]], which can be closed if necessary. The training zone should be combined with a pasture to keep in wild animals. This will make sure your animals don't escape when they are not being trained.

=== Dungeon ===
{{main|Jail}}
[[File:dungeon_medium_icon.png|right]]A dungeon is a room designed for [[justice|dwarven justice]]; and in each room, there must be 1 metal [[cage]] or a [[Restraint|rope/chain]]. Once the prisoner is selected to be imprisoned via the justice screen. the [[fortress guard]]/[[sheriff]] will chain or lock the creature in the selected chain or cage. The prisoner will continuously generate a bad thought while being imprisoned. so with some micromanagement, you can save the poor innocent [[cheese maker]] who violated the [[mayor]]'s export ban, from being overly stressed out, by deconstructing the chain as soon as they were chained up. A chain is recommended over a cage, as the chained up creature can still have access to the 8 tiles adjacent to the chain, granting them access to bed, food stockpile, chair and table, as well as allowing the prisoner to admire the chain if they were made from valuable metal like [[gold]] and [[platinum]]. While a caged prisoner is fully dependent on idle dwarves to deliver them food and drink (and only water instead of alcohol are delivered!). So they are more likely to starve to death than chained prisoners (provided you designate a food & drink stockpile within that can be reached by the chained prisoner). Plus, sleeping on a cage floor is, as expected, [[Stress|not very pleasant]].

=== Tomb ===
{{main|Tomb}}
[[File:tomb_medium_icon.png|right]]A tomb is designated to a specific dwarf ([[File:Interface dwarf face.jpg|26px]]), or a pet's corpse ([[File:Interface tomb pet.png|26px]]), to be buried or memorialized in order to prevent the appearance of [[ghosts]]. A tomb zone can only accommodate one dwarf. The primary function of tombs is to keep nobles happy: certain nobles demand their own tomb, and the more self-important the noble is, the higher the quality they will require. In some circumstances a noble will get an unhappy thought if an "inferior" dwarf has a higher-quality tomb, however it is unclear what quality threshold the tomb must be to trigger the thought. Also, a noble that demands a tomb also generates a bad thought at the end of every year if the tomb is yet to be built for them, or did not reach their [[#Quality_and_value|desired rank]]. Nobles may also store certain favored objects in their tombs. To be considered properly buried, at least ''half'' (rounded up, so no less than one) of their existing body parts must be buried.

=== Fishing ===
[[File:fishing_medium_icon.png|right]]Dwarves will preferably use these zones when [[fishing]], using them up until their supply is exhausted before moving on to the next water source. As with water sources, only tiles ''adjacent'' to water qualify as usable tiles. Far-flung fisherdwarves fishing in a distant [[river]] or [[pool]] are a serious defensive liability in case of an attack, so designating a safer fishing zone and, optionally, restricting non-zone fishing in the [[standing orders]] menu will help keep your fisherdwarves safe. Dwarves can fish through a [[grate]] or even a [[well]], provided there is water in the tile 1 z-level below the activity zone.

The [[Captured live fish|capture live fish]] job can ''only'' be carried out at a designated fishing zone.

=== Gather Fruit ===
[[File:gather_medium_icon.png|right]]This will automate plant-gathering jobs in this area, necessary if you want your dwarves to collect fruit from the floor ([[File:Ui gather fallen fruits.png|28px]]), from the [[shrub]]s ([[File:Ui gather shrubs.png|28px]]) and from the trees ([[File:Ui gather trees.png|28px]]). If there are fruit-bearing trees in the designated area, a dwarf will fetch a [[stepladder]] to climb into the tree. The ladder-using dwarf will drop harvested fruit to the ground for others to collect and haul. The details can be set in a sub-menu.

=== Sand collection ===
{{main|Glass industry#Collecting sand}}
[[File:sandpit_medium_icon.png|right]]A '''sand collection''' zone allows dwarves with the [[item hauling]] labor active to fill an unused [[bag]] with [[sand]] for use in the [[glass industry]]. The 'collect sand' task is created at a [[glass furnace]].

=== Clay collection ===
{{main|Ceramic industry#Clay collection}}
[[File:claypit_medium_icon.png|right]]A '''clay collection''' zone allows dwarves with the [[item hauling]] labor active to create [[clay]] for use in the [[ceramic industry]]. The 'collect clay' task is created at a [[kiln]].

== Quality and value ==

Most dwarves don't have high expectations when it comes to rooms - a communal [[dining room]] and [[dormitory]] are enough for the general populace, though making that dining room high-quality and giving them individual quarters will give them happy [[thoughts]], helping to avoid [[tantrum]]s.
[[Nobles]], on the other hand, require rooms of a particular minimum quality that contain certain [[furniture]]. Not meeting these demands will cause [[Emotion|stressful thoughts]], and may prevent them from functioning at their full capacity.

The thoughts generated by more impressive zones will have a stronger stress–relieving value than the thoughts generated by plain or unimpressive zones.

You can check a current rank of a room in the owner's [[profile]] on the "Rooms" tab. There are 8 rank names for each type of a personal room:

{| class = "wikitable unsortable" style="margin:auto;"
|-
! Bedroom name
! Dining room name
! Office Name
! Grave Name
! Numeric Value
|-
| Meager Quarters
| Meager Dining Room
| Meager Office
| Grave
| style="text-align:right;" | 0
|-
| Modest Quarters
| Modest Dining Room
| Modest Office
| Servant's Burial Chamber
| style="text-align:right;" | 100
|-
| Quarters
| Dining Room
| Office
| Burial Chamber
| style="text-align:right;" | 250
|-
| Decent Quarters
| Decent Dining Room
| Decent Office
| Tomb
| style="text-align:right;" | 500
|-
| Fine Quarters
| Fine Dining Room
| Splendid Office
| Fine Tomb
| style="text-align:right;" | 1000
|-
| Great Bedroom
| Great Dining Room
| Throne Room
| Mausoleum
| style="text-align:right;" | 1500
|-
| Grand Bedroom
| Grand Dining Room
| Opulent Throne Room
| Grand Mausoleum
| style="text-align:right;" | 2500
|-
| Royal Bedroom
| Royal Dining Room
| Royal Throne Room
| Royal Mausoleum
| style="text-align:right;" | 10000
|}
Note: unassigned (or communal) rooms may be referenced by other descriptors, such as the happy thought "... dined in a legendary dining room ...".

=== What counts towards room value ===

Room value can be loosely-split into 3 categories: walls, floors, and furniture (everything that is a placeable object goes here, including doors).

A room's furniture value is calculated simply by counting every item of furniture in the room and adding all their [[item value]]s up. Due to the quality-value nerf in v50, furniture is a less effective way to pump up a room's value.

[[Display furniture]] counts towards room value. However, the items ''displayed in it'' only count if the dwarf has a [[preference]] for them. So if your king likes [[sword]]s then any sword in a display case will count towards room value, and any other item (such as a [[crossbow]]), no matter how valuable, won't.

Unlike previous versions where natural surfaces were preferred, now ''placed'' floors and walls have a higher value than natural, with walls having a slightly higher value than floors. Wall and floor values are also calculated by adding all the individual tiles of walls and floor, but first we have to calculate the individual values...

=== Value calculation ===
The formula for calculating the final room value has changed significantly from prior versions of Dwarf Fortress. Thanks to research by TBTerra{{cite reddit|zzqlfu}}, the new formula has been discovered (and included here with only minor edits).

* '''[[Item value#Material multipliers|Material value]]''' - The value given to an item, floor, wall etc due to the material it is made from. ''Common material types:'' Natural spaces like sky, water, or magma are 1, wood is 1, rocks are 1–3, ores/metals are 2–40, gems are 2–60
* '''Pre v50 quality multiplier''' - This is still used in some places.
* '''Current quality multiplier''' - This is used for items.
* '''Quality bonus''' - a flat bonus added after the multiplier.

{| class="wikitable" style="text-align:right; margin:auto;"
|- style="text-align:center;"
! rowspan="2" | Quality
! colspan="2" | Quality multiplier
! rowspan="2" | Quality bonus
|- style="text-align:center;"
! Pre v50
! Current
|-
| style="text-align:center;" | -well crafted-
| 2
| 1.1
| 3
|-
| style="text-align:center;" | +finely crafted+
| 3
| 1.2
| 6
|-
| style="text-align:center;" | *superior*
| 4
| 4⁄3 ≈ 1.3
| 10
|-
| style="text-align:center;" | ≡exceptional≡
| 5
| 1.5
| 15
|-
| style="text-align:center;" | ☼masterful☼
| 12
| 2.0
| 30
|-
| style="text-align:center;" | Artifact
| 120
| 20.0
| 300
|}

=== Values of floor tiles ===

The value of an individual floor tile depends on if it's the original cave floor, a smoothed cave floor, or a placed floor.

;raw cave floor
:1 × material value
;Smooth cave floor
:4 × material value
;placed cave floor
:7 × material value

Additionally if the floor is engraved you add an extra 10 × material value × old quality multiplier.

=== Values of wall tiles ===

Again value depends on whether its original stone, smoothed stone, or placed wall. (Boulders, bars, and blocks of the same material type all have the same value.)

;original wall
:1 × material value
;smoothed wall
:5 × material value
;placed wall
:9 × material value

[[Engraving]] with walls is not always a simple matter. In order for an engraved wall to add its engraving to the room value, the room must contain both the wall itself ''and'' the location the engraver was standing when it was engraved. This means that an engraved wall shared between two zones will only add its value to one of those zones, whichever one the engraver was standing in when that engraving was done.

The value of a wall engraving is 10 × old quality multiplier × material value.

=== Overlapping Rooms ===
[[File:overlapping_zones_preview.png]]{{clear}}
When room designations such that they share floor tiles, the label of some zones in that same area will be renamed to "Overlapping (Zone)" in red text. When selecting an overlapped area, the player is able to select the zone layers with clickable arrows on either side of the zone name. Zones in this state have their values set to 0{{cite reddit|13097u3/comment/jhwgm0e}}. There is no difference in value between a piece of furniture shared by two rooms, or by forty.

Sharing walls is fine however, and sharing doors is allowed as long as the room contains a wall adjacent to the door. When sharing a door, the floor tile it is on is also shared.

[[Location]]s have individual values and are therefore not affected by overlapping zones (eg. A ''Dining Hall/Tavern'' overlapping a ''Meeting Hall/Temple'' will have both Dining and Meeting halls value to 0, but the Temple and the Tavern will share the same values{{cite forum|181632.msg8475740#msg8475740}}.

=== Building optimally ===

If you are limited on your high-value materials (or have lots of rooms you wish to improve) and don't want to abuse wall sharing or other glitches, here's how best to use those high value mats:

# Use your high-value materials on floor tiles, not furniture. A decently-engraved floor has a value of 37–57 × material value; the only thing that gets close to that is the mechanisms in levers.
# The floors of doors that go between rooms you wish to increase are of particular importance as they will count for both rooms.
# Engravings are tedious to redo (For a natural floor, you will need to carve tracks and smooth over before re-engraving. For constructed floors, you will need to build a wall, then carve fortifications, remove the fortification and replace the floor). To minimize the extra work of redoing engravings, leave your highest-value tiles to be done by your most experienced engraver so they will have a high quality on the first try.

=== Breaking room value ===

Since version 50, there is nothing that requires a room to be a single connected piece. This, combined with wall sharing, allows for some… less than fair cheesing of platinum walls that are somehow owned by every single bedroom. And with a trick in the “how to break room value” section, you can have every room royal quality for as little as 4 platinum and 6 basic wood/stone

So you don’t care about using glitches and non–contiguous rooms. Here’s the way you break room value with minimal effort and resources:
[[File:Zone value breaking example.png|thumb|200px|Steps 2 and 3.]]
# Make a line of wall with a 1 tile gap on either side (if your engravers are really good this might only need to be 2–3 long).
# Make the lines of floor either side of this wall out of the most valuable material you can (aluminum or platinum are great, steel and gold also work), and have your best engraver engrave them.
# Place doors on top of all those engraved tiles, what sort doesn’t really matter, as they will be adding 10–100 value to 2–3k value floor tiles.
# For every room ''on the same [[z-level]]'' add the doors and the wall (this is a convenient rectangle). The wall makes the doors shareable, and the doors make the engraved floor shareable.
# For optimal results hide this to the south east of your area, otherwise the zone icons can get rather confusing.

You can also assign arbitrary stretches of space on the same z-level, such as sky, magma, or water, as part of the zone to increase value. Because the standard 4×4 embark contains 192×192=36864 tiles, each with a value of one, designating one entire z-level of sky would instantly create a royal quality zone.

{{Zones}}
{{V50 menus}}
{{Category|Fortress mode}}
{{Category|Zones}}
[[ru:Zones]]

Dwarf Fortress webcomics

2026-04-04T21:08:31Z

Ziusudra: /* Matul Remrit (Bravemule) */ added archive link, didn't check every page but seems to be the most complete

{{DISPLAYTITLE:''Dwarf Fortress'' webcomics}}
''Dwarf Fortress'', due to a combination of its insane level of complexity and minimal artistic depiction, attracted the attention of various webcomic writers and artists - detail-minded folk, often attracted to games, and with very active imaginations. These webcomic 'strippers have immortalized ''Dwarf Fortress'', sometimes as individual episodes in their ongoing webstrips, sometimes as brand-new webcomics devoted entirely to ''Dwarf Fortress''.

[[File:DF_Cheese.jpg|208px|thumb|right|A ''Dwarf Fortress'' comic]]

==Graphic sagas==

===The Littlest Cheesemaker===
[http://www.bay12forums.com/smf/index.php?topic=136384.0 The Littlest Cheesemaker] is an illustrated interactive story chronicling the adventures of Mistêm "Wheeldream" Kolnåzom (Misty) on her quest to become a legendary [[cheesemaker]].

===Losing Is Fun===
[https://losingisfun.org/ Losing Is Fun] ([https://web.archive.org/web/20191102233928/http://losingisfun.com/ old archive]) is an interactive webcomic about a [[kobold]] on a quest to steal an [[artifact]] dagger from a dwarf fortress. [http://www.bay12forums.com/smf/index.php?topic=164165.0 First forum thread] [http://www.bay12forums.com/smf/index.php?topic=178723.0 Second forum thread] (Currently Ongoing)

===Bronzemurder===
[[Bronzemurder]] is an epic illustrated saga by [http://timdenee.com/bronzemurder/ Tim Denee], concerning a [[forgotten beast]].

===Oilfurnace===
[http://www.timdenee.com/oilfurnace/ Oilfurnace] is another ''Dwarf Fortress'' illustrated saga by Tim Denee, and printed in the July 2010 issue of PCPowerplay magazine, an Australian gamer mag, making it the first ''Dwarf Fortress'' comic in print. (Warning: contains minor spoilers)

===Adventures of Likot Udendeb===
[http://www.bay12forums.com/smf/index.php?topic=109582.0 Adventures of Likot Udendeb] is an illustrated, interactive saga originating from Russian ''Dwarf Fortress''-centered imageboard [http://chuck.dfwk.ru/ DFach]. The story is written and illustrated by several anonymous contributors based on suggestions of the imageboard's users. Starting as a story of one completely ordinary dwarf and his cruel fate of being the hero, it eventually evolved into an epic saga with multiple arcs, various characters and global setting that's loosely based on ''Dwarf Fortress'' game mechanics rich with DF-related memes and influence of general Russian imageboard culture. Permanently in indefinite state of being written/frozen and is being translated (badly) from Russian with a certain lag. Admired for its flexible storyline and several [http://www.youtube.com/channel/UC6Crmf54js5ZEyGlKtEbggg/feed animated episodes].

===Matul Remrit (Bravemule) ===
'''THE LINK IS BROKEN.''' [http://www.bravemule.com/matulremrit Matul Remrit] ([https://web.archive.org/web/20210823135449/https://bravemule.squarespace.com/matulremrit/ archive]) is a tale of a band of dregs who struggle to build their new home amidst strife, internal politics, and a scourge of elf attacks.

===Thabostobok===
'''THE LINK IS BROKEN.'''
[https://www.dream-gears.com/sites/comicwolf.com/index.php?app=comics&app=comics&action=listview&catid=1 Thabostobok] A fully illustrated comic based on a DF game session.

==Ongoing ''Dwarf Fortress'' webcomics==
Ongoing webcomics primarily about ''Dwarf Fortress''.

===Bridgedflickered===
[https://tapas.io/series/Bridgedflickered/info/ Bridgedflickered] is a yonkoma-style strip by Lee Keegan, chronicling a playthrough of ''Dwarf Fortress''.

===Revenge of the FUN===
[http://rotf.thecomicseries.com/ Revenge of the FUN] is a comic series about dwarves striking the earth, and the [[fun|FUN]] striking back, in all outrageous fashions.

===The Chronicles of Boatmurdered===
'''THE LINK IS BROKEN.'''
[http://boatmurdered.smackjeeves.com/comics/735733/chronicles-of-boatmurdered-cover/ The Chronicle of Boatmurdered] is an illustrated version of the infamous [[succession game]] [[Boatmurdered]], with art by Deon. The webcomic began in November 2009 and stopped unfinished in May 2010.

===''Dwarf Fortress'': Histories of...*===
[http://dfstory.thecomicseries.com/comics/1/ ''Dwarf Fortress'': Histories of...*] is a DF chronicle with art and story by Elthar. The webcomic began in July 2010 and died after six pages.

===KittyProblem===
https://archive.org/details/smackjeeves-85447 An archived short comic created by two brothers about the dangers of [[catsplosion]]. Story began on 2nd September 2010.

===Ask Amxu===
Oi, My name is [http://askamxu.tumblr.com/ Amxu Osmösprosusm]. I'm a [[goblin]] and I work as a [[snatcher|compulsory freelance social worker]] for the dwarves in my region. I'm always happy to answer questions for the curious.

===Lord of the Dwarfs===
[https://web.archive.org/web/20180106125719/http://www.dawnsomewhere.com/lotd/ Lord of the Dwarfs] is a webcomic produced by Dawn Somewhere about a group of dwarves attempting to find their way back to their fortress after an unusual encounter with HFS.

==One-off ''Dwarf Fortress'' webcomics==
Ongoing webcomics that are not primarily about ''Dwarf Fortress'', but which have a few ''Dwarf Fortress'' episodes. The relevant strips are linked to here:
===The Chapel===
Has a few ''Dwarf Fortress'' comics, more popular in the Paradox community
[https://chapelcomic.com/]

===Irritability===
In the subsection [http://maze.icomix.com/comicpage/bad.php?o=0 200 Bad Comics], numbers [http://maze.icomix.com/comicpage/badcomics/bad053.png 56], [http://maze.icomix.com/comicpage/badcomics/bad073.png 75 and 76] are about ''Dwarf Fortress'', mainly the [[goblin]] menace.

===Nerfnow===
A manga-influenced webcomic by Josué Pereira. Included a brief ''Dwarf Fortress'' arc: [http://nerfnow.com/comic/352 352] [http://nerfnow.com/comic/370 370] [http://nerfnow.com/comic/371 371]

===twistedspeedo===
Created this comic about the game's motto, "losing is fun" : http://twistedspeedo.com/?p=478

===Three Panel Soul===
[[File:Dorf.jpg|thumb|right|3PS Dorf T-shirt]]

This sequel comic to MacHall gives us five ''Dwarf Fortress'' strips, [http://www.threepanelsoul.com/comic/on-dwarven-fortresses On Dwarven Fortresses], [http://www.threepanelsoul.com/comic/on-trade-goods On Trade Goods], [http://www.threepanelsoul.com/comic/on-mixed-economies On Mixed Economies], and [http://www.threepanelsoul.com/comic/on-learning-curve On Learning Curve]. [http://www.threepanelsoul.com/comic/bug-fix Illustrated DF patch notes]. The first three comics deal with typical ''Dwarf Fortress'' [[fun]], such as [[catsplosion]], stereotypical dwarven literal-mindedness, and the [[Dwarven economy]]. The fourth concerns a new player's introduction to the game.

The ''Dwarf Fortress'' comics were so popular, they spawned a related t-shirt (see picture on right).

===[ENGRAVERY:MISGUIDED]===
A series of one-off, irregularly updated panel-style comics using altered ASCII graphics.
*[http://alluvian.blogspot.com/2011/03/engraverymisguided-noble-mandates.html Noble Mandates]
*[http://alluvian.blogspot.com/2011/03/engraverymisguided-selecting-site.html Selecting a Site]
*[http://alluvian.blogspot.com/2011/03/engraverymisguided-artifact-rope.html Artifact Rope]
*[http://alluvian.blogspot.com/2011/03/engraverymisguided-send-in-clowns.html Send in the Clowns]
*[http://alluvian.blogspot.com/2011/03/engraverymisguided-creepy-forest.html Creepy Forest]
*[http://alluvian.blogspot.com/2011/04/engraverymisguided-noble-rain.html Noble Rain]
*[http://alluvian.blogspot.com/2011/03/engraverymisguided-and-dwarf-road-song.html Interrupted by Peacock] & Dwarf Road Song

==Individual webcomics==
Webcomics done by an individual who does not maintain their own regular ongoing webcomic or site, organized by artist/author if known. Links may become unusable unless these webcomics are archived!

===cdawg===
Created a brief comic episode about [[fell mood]]s: [http://img.photobucket.com/albums/v514/CDawg116/dwarfcomic.png 1]

===Lord Licorice===
Creates comics based around the ''Dwarf Fortress'' [[List of mods#Kobold Camp|mod Kobold camp]], mainly posted at [http://facepunch.com Facepunch]. [http://1d4chan.org/images/thumb/9/9f/Koboldhouse.gif/800px-Koboldhouse.gif Kobold House], [http://suptg.thisisnotatrueending.com/epic/images/gobbo/koboldthief.png Kobold Thief], [http://suptg.thisisnotatrueending.com/epic/images/gobbo/koboldandthemoon-full.gif Kobold and the Moon], and [http://suptg.thisisnotatrueending.com/epic/images/roguelike/goblinfortress.gif Goblin Fortress].

===skullamity===
Creator of the infamous Cheese Engraver comic posted at the top of the page, as well as this one: [https://66.media.tumblr.com/tumblr_m5l37uT1Be1r8swg2o1_500.jpg Miner Cancels Drink]. Skullamity is also the artist behind STRIKE THE EARTH! which was previously listed under [[#Defeated_Webcomics|Defeated Webcomics]] in 2014, but was finally completed and made available for reading in January 2023. [https://skullamity.substack.com/p/strike-the-earth-part-1 STRIKE THE EARTH!] by skullamity originally began posting in November 2009. This comic tells the immediately tragic downfall of the fortress Sunderclasp. The Dwarves hit the usual stumbling blocks of being in a [[sinister]] terrain, including facing [[undead]] wildlife. It was declared dead in 2014 and went offline when its original comic host shut down, but the author went into a fey mood in November 2022 and was inspired to fix up existing pages and finish the short comic project.

===Valcan===
Created this comic about the [[Bronze colossus]]: [http://i39.tinypic.com/258xf2w.jpg 1].
[link broken]

===Unknown Creator===
An awesome comic about [[fun]]: [http://i.imgur.com/mHXiz.png 1].

A comic about [[Elf]] diplomacy: [http://i.imgur.com/I2Stz.jpg 2].

<gallery caption="Some comics">
File:1235703760028.png|First time DF player.
File:Comic df3.png|DF has many types of players.
File:Comic df4.gif
File:Comic df5.png
File:Dwarf-Fortress Poster.jpg
File:FunComic.png
</gallery>

==Defeated Webcomics==

These are links to comics that once were, but now are not. They are lost in the great wasteland of The Barren 404 Desert.

===PixelPainted===
[http://www.dfa.webatu.com/?page=111001 PixelPainted A ''Dwarf Fortress'' Adventure] is a flash comic by Glyphgryph, and based on a Choose Your Own Adventure-style suggestion thread. The webcomic began in September 2009 and is currently on hiatus.

'''Dead:''' December 2014

===I'm Not Mad===
A 3D model comic with three ''Dwarf Fortress'' strips, ''Dwarf Fortress'': Overachiever,''Dwarf Fortress'': Work Music, and ''Dwarf Fortress'': Suspicion. The first comic deals with [[Hidden Fun Stuff]], while the second deals with [[tantrum]]s.

'''Dead:''' July/August 2015

===Dwarven Trail===
[http://www.bay12forums.com/smf/index.php?topic=36953.0 Dwarven Trail: A ''Dwarf Fortress'' Comic] was a sprite comic by Matthew (Opirian) Tracy. It used RPG Maker VX for the graphics, which mimicked some of the popular [[Graphics set repository|''Dwarf Fortress'' graphic sets]]. It followed the journey to and establishment of a new fortress. [[Urist]] was a recurring character. The comic was hosted on a couple different sites at times, but they seem to no longer be available or safe; the forum post appears to provide all the pages, albeit with hosting watermarks. The Wayback Machine on the Internet Archive seems to only include [https://web.archive.org/web/20110506035108/http://www.webcomicsnation.com/dwarventrail/dwarventrail/series.php?view=single&ID=154017 page 9].

===Effigies===
'''THE LINK IS BROKEN.'''
[http://effigies.smackjeeves.com/ Effigies] is a character-driven world-building webcomic by Fault, based on ''Dwarf Fortress'' [[Adventure mode]]. The comic began in November 2009 and was ongoing, updating on a rough weekly schedule. It currently lays dormant.

==Related pages==

* [[List of Dwarf Fortress references|List of ''Dwarf Fortress'' references]]

[[Category:Humor and stories]]
[[Category:Community|webcomics]]
[[ru:Dwarf Fortress webcomics]]
{{unversioned}}

Zone

2026-04-03T23:44:59Z

Ziusudra: moved most of intro to Usage section, added explanation of 2 numbers with plus sign

{{Quality|Masterwork}}
{{av}}
[[Image:Zones menu v50.03.png|right]]
A '''zone''' is an area where your citizens will work, socialize, rest, or perform specific duties, such as [[fishing]], dumping objects, or collecting [[water]].

== Usage ==
Zones can be placed in any [[revealed tile]], including in [[open space]], over a [[river]], on top of a [[building]] or [[stockpile]], or a [[wall]]. They are placed in one of three ways: rectangular, draw, or (for some zones) multi. From within the Zones [[menu]] ({{menu icon|z}}), selecting a zone type will open the zone creation menu. From here, you can select whether to create a zone in a rectangle (at which point you click the two corners for the zone) or simply draw it (where clicking adds single squares to the zone). You can enable erasing at any time and use rectangle and draw to remove squares from the zone. The number shown indicates how many selected floor tiles can be used for that type of zone. After selecting some tiles, two numbers are shown with a plus sign (+) between; the first is the number of valid tiles already in the zone, and the second is how many would be added with the new selection or tile.

Unlike [[stockpiles]], multiple zones can overlap.

For select zone types, you can change from Paint to Multi mode, in which you can draw a rectangle over multiple rooms, and each room valid for that zone type will be a separate zone. The number shown is the number of zones created in the last rectangle drawn, and the undo button will only undo the last rectangle created.

Some zones can be further specified into [[location]]s after creation. To do this, first create the relevant zone, then click the Add Location button ([[File:Ui location add.png]]) to further specify it as a location. Multiple zones can be added to a single location, allowing them to span multiple rooms.

In some cases (pen/pasture, pit/pond) additional orders can then be set from the same menu. The location of a zone is only visible while in the Zones menu, and any object lying on the ground will hide the presence of a zone tile. The size of a zone is unlimited.

== Zone Types ==

=== Meeting area ===
[[File:meeting_icon_preview.png|right]]'''Meeting area zones''' are zones in which idle dwarves and animals will congregate. After a meeting area is designated, it can be left as is, or it can be made into a [[tavern]], [[temple]], [[library]], [[guildhall]] or [[hospital]], but animals will not congegrate to meeting areas, which are assigned to certain locations like temple, tavern or guildhall (and presumably, but not yet tested, library or hospital). Additionally, [[immigration|immigrants]] will collect at a meeting area until their "migrant" status wears off. Note that the [[wagon (embark)|wagon]] you [[embark|arrive with]] constitutes a meeting area until you designate the first meeting area of your own (and it will, at least as long as the embark wagon is around, constitute a meeting area for animals, if all other meeting areas are assigned to locations to which animals do not congregate to). If you start in hostile surroundings, it is important to do so, so as to get your dwarves and animals out of danger quickly. It is a good idea to have at least one meeting area of one form or another: It allows you to make off-duty dwarves and animals gather in an area where they are not vulnerable within the fortress. A meeting area filled with dwarves increases the [[social skill]]s of idlers. It makes idle dwarves a little less idle. Because almost every dwarf visits a meeting area at least occasionally, it's an ideal place to site valuable objects and buildings. A meeting area exposed to sunlight will additionally prevent dwarves from becoming [[cave adaptation|cave-adapted]]. Note that having dwarves socialize will often result in them forming [[relationship]]s.

It is not advisable to have animals mill around in crowded meeting areas for a prolonged time, as they will pick fights with dwarves and other animals. While this may be negligible in the case of a hen, it also applies to your [[Dog#War dogs|war dogs]] (although this can be partly beneficial, since all your dwarves will get combat experience from being bitten occasionally, especially the children, who mill around constantly).

If the meeting area is made a guildhall or a temple, the icon of the zone will change depending on the room's quality. For a guildhall, the icons are [[File:meeting_quality0_sprite.png|19px]] and [[File:meeting_quality1_sprite.png|19px]]. For a temple, the icons are [[File:temple_quality0_sprite.png|20px]], [[File:temple_quality1_sprite.png|20px]] and [[File:temple_quality2_sprite.png|20px]]. Dwarves may petition for these types of rooms of varying qualities.

=== Office ===
{{main|Office}}

[[File:office_medium_icon.png|right]]An office is a zone required by some [[Noble|nobles]], and requires a [[chair]]. [[Manager|Managers]] will use the chair to validate and check [[work orders]]. A [[bookkeeper]] will use the office to update the [[stock]]records and increase the precision of the records. A dwarf with an office assigned will sometimes [[eat]] in their own office if there is no communal [[dining hall]] designated in the fortress, but this does not provide any happy [[thought]], no matter how [[#Quality_and_value|luxuriously decorated]] the office may be, and may even generate a bad thought if the chair doesn't have a [[table]] adjacent to it.

=== Bedroom ===
{{main|Bedroom}}

[[File:bedroom_medium_icon.png|right]]A bedroom is a zone where a single dwarf (and possibly their spouse and children) will sleep and store their belongings in. Requires a [[bed]]. A cabinet can be built for the dwarf to store their [[Wear|old]] clothing; and a chest for dwarves to store their belongings like [[coins]], [[Finished Goods|rings, scepters]] etc. A dwarf with no cabinet, or with low [[Personality facet#ORDERLINESS|orderliness]] personality facet will scatter their old clothing everywhere.

=== Dormitory ===
{{main|Dormitory}}

[[File:bedroom_medium_icon.png|right]]A dormitory is a zone containing multiple [[Bed|beds]] where all dwarves that do not have a bedroom assigned to them will sleep. However, sleeping in a dormitory will generate a negative [[thought]] (embarrassed after sleeping without a proper room).

=== Dining hall ===
{{main|Dining hall}}

[[File:dining_medium_icon.png|right]]A Dining Hall is a zone where dwarves go to eat. Requires one or more [[Table|tables]].

=== Barracks ===
{{main|Barracks}}

[[File:barracks_medium_icon.png|right]]A barracks zone is a zone where a [[military]] will go to sleep, train, or store their equipment.

=== Pen/Pasture ===
{{main|Pasture}}

[[File:pasture_medium_icon.png|right]]A pen or a pasture is used to contain tame animals. Once one is created, animals must be assigned to it individually from the zone information menu. Dwarves will drag the assigned animals to the pen or pasture automatically. Domestic animals tend to aggregate at [[meeting area]]s instead, as will herbivorous ones, which will probably lead to starvation, unless your meeting area is overgrown with [[grass]] or fungi for some reason. '''Any tame creature with the "grazer" token in the raws should be assigned to a pasture. This includes mules, cows, goats, horses, yaks, unicorns etc.''' Animals will not typically wander out of their assigned pasture even if it is not walled in, however animals will abandon their posts and will have to be dragged back to them if they are threatened by enemies, and an exposed pasture may lead to premature slaughter at the hands of invaders. Since pets can be assigned to pen/pastures and a zone can be created under a [[dwarven atom smasher]], this is one of the easiest ways to prevent [[catsplosion]]s.

=== Archery range ===
{{main|Archery range}}

[[File:archery_medium_icon.png|right]]An archery range is used by [[marksdwarves]] (or [[Bow|bowdwarves]] and [[blowgun|blowgunners]] by editing the raw). A marksdwarf will pick up bolts nearest to them And then shoot at the target. Upon depleting the bolts, the markdwarf will gain a happy thought(feels pleasure after practicing at an archery range). The marksdwarf's XP gain by practicing in an archery range is only [[Experience|half the amount]] compared to using a [[Advanced Marksdwarf Training Guide|live target]]. but it has the advantages of being easy to set up and needing much less micromanagement. Note that markdwarves cannot shoot adjacent to the [[archery target]]. and there must be at least 1 tile of walkable perimeter that is from the target in order for archery practice to happen.

=== Pit/Pond ===
{{TipBox2|titlebg=#c00|textbg=#ffd|[[File:warning_icon.png|25px]] Warning!|There have been multiple reports of hostile creatures escaping confinement while pitting. Use of forbidden tightly closed hatches above every hole appears to prevent escape.
See [[Mass pitting]] for more. If there are walls under the hole's edges rather than open space, they will allow [[Climber|grabbing and climbing]], so you may want to dig out an overhang, or at least [[Smoothing|smooth]] these walls.
}}

[[File:pit_medium_icon.png|right]]A Pit/Pond requires a [[ramp]] or hole with adjacent flooring on which a dwarf can stand. Designate the zone from the top of the ramp or hole, such that the zone designation is floating in the open space above the floor of the pit/pond. By default, the zone will be a pit. To toggle between pit and pond, press corresponding icon in zone information menu ([[File:Ui Pit.png|24px]]/[[File:Ui Pond.png|24px]]).

Creatures can be assigned to a pit/pond ([[File:Ui assign creature.png|24px]]). If the creature is [[cage]]d, a dwarf will release it from the cage (rather than bringing the cage to the pit). The dwarf will lead the beast to the pit and throw it in. If the pit is a ramp rather than a hole, the creature will then wander back out, as it will if the pit has some other exit path (which would include straight back up the hole for flying creatures). Note that some (or possibly all?) hostile creatures may escape on being released from their cage, possibly attacking the dwarf who opened the cage.
Additionally, dwarves refuse to pit dwarves, hostile or not.
{{Colored Notice Box||See [[Mass pitting]] for more information on pit design involving hostile creatures.}}

The only real difference between a pit and a pond is that dwarves will attempt to fill a pond with [[water]], carried by [[bucket]] from a water source. They will stand on the floor adjacent to the top of the ramp or hole, and toss the water onto the ramp or into the hole. This works even if there is a forbidden [[floor hatch]] covering the hole. Each bucketful increases the depth of the water in the tile below by 1/7. Once the water is dumped from the bucket, the dwarf will either drop the bucket and perform a different task, or choose to fill a pond zone tile again using the bucket (s)he currently holds. Dwarves will stop scheduling the Fill Pond job when the water depth reaches 6/7. Specifying a pond zone is one technique used for [[irrigation]], in order to make [[mud]] for [[farming]] on areas without soil. Currently, no matter how large the designated pond area, only one dwarf at a time will try to fill the pond. In order to fill a large area quickly, it is necessary to designate multiple smaller pond zones (or several zones overlapping the same area).

To make obsidian or cleanse stagnant water with fresh water, the pond zone must be designated an extra tile above the magma/stagnant pool, so that the water falls for a full tile before contacting the surface.

If you have more than one pond designated as a water source, your dwarves may endlessly try to fill each pond with the other pond's water, making a loop of useless duty; this may be undesirable, although otherwise-idle dwarves performing this task won't be making any friends. Only dwarves with the [[Hauling#Water_hauling|Water hauling]] labor enabled will fill ponds.

Artificial ponds are considered to be the same as Murky Pools - you'll only catch pond fish from them (i.e. turtles). If you want to catch river fish, you must fish from the river's original tiles (or perform some DFHack trickery to mark your new tiles as being part of the river).

=== Garbage Dump ===
{{main|Garbage dump}}
[[File:trash_medium_icon.png|right]]Garbage dump zones are areas in which dwarves will throw items marked for dumping - either by manual setting of dump status from item information menu, or {{menu icon|i|p}} (bulk dumping; note that this designates ''all'' items on the tiles for dumping, even built [[furniture]] and items inside [[Storage|container]]s). Garbage dumps are ''not'' the same as [[Refuse#Refuse|refuse]] stockpiles, which can be designated to accept specific type(s) of refuse, such as animal [[corpse]]s or [[bones]], and then are automatically filled by haulers whenever the items appear on the map. Despite the name, garbage dump zones are useful for many things beyond [[garbage disposal]]; they can create [[quantum stockpile]]s, transport materials to a job site, send items to the [[trade depot]] when no caravan is present, [[trap design#Falling_debris_trap|drop rocks]] on enemies below, and numerous other uses.

Be aware that if a garbage zone is designated beside a cliff or hole (any open space, either natural or dwarf-made), garbage will be thrown into the open space. If a dump is designated over a [[ramp]] to the next level down, some dwarves may walk down the ramp to dump their items, while others may just toss their items down from above and onto those dwarves, injuring or killing them.

The garbage dump may be inappropriately named, as it's more of a matter compression zone. The specifics are beyond human understanding; however, dwarves are in fact capable of compressing an infinite amount of matter into only one tile, as long as it is specified as a garbage dump. If, for some reason [[Main:Urist|Urist]] is yet again incapable of locating his favorite pair of, say, troll fur socks, he should think to look among the black hole of matter that is the nearest garbage dump, as they could be snugly lodged between a few billion rocks.

=== Water source ===
[[File:water_medium_icon.png|right]]Dwarves will use these zones to draw water, to satisfy booze-less [[thirst]], to tend to another thirsty dwarf (with the Give Water job), or to fill a [[#Pit/Pond|Pond zone]]. Only tiles ''adjacent'' to water qualify as usable water sources - thus, if you want to place a single-tile zone, place the zone onto a ground tile next to the water, not over the water itself. This zone should ''not'' be used with [[well]]s - this is redundant, as they are already considered their own water source.

If this zone does not exist, any water source can be used. If at least one water source zone exists, then dwarves will only get water from these zones.

Remember that natural bodies of water usually contain aquatic wildlife, some of which may attack your dwarves, or at least spook civilians, and interrupt their tasks. Often it may be best to simply designate a safe body of water as a water source so dwarves aren't allowed to drink/fish anywhere else.

Normally, creatures cannot attack any dwarves through a [[well]] so long as the well is not on the same z-level as the top of the lake/river, thus building one will allow your dwarves safe access to water inhabited by vicious animals (as long as those can't climb).

When dangerous fish are found in the river, one solution is to dig an artificial [[channel]] and place a [[grate]] between it and the river proper, as fish cannot swim through grates, but grates still allow water through. However, beware [[Grate#Bugs|the bug with flow and ''wall'' grates]] - taking water via U-shaped tunnel capped with ''floor'' grates may be safer. If you use a completely isolated smooth reservoir filled with [[pump]]-filtered water, it may still need protection, since the dwarf operating a pump stands right next to its water source tile.
Placing floor grates over the river or channel may also protect dwarves by preventing them from falling in.

[[Carp]] and other non-[[vermin]] fish suffocate if they are not in water, so in some situations it might be possible to pump the water out of a lake or pond. Conversely, an open water body (river or sea) not only cannot be subjected to temporary drainage, but even if there isn't anything dangerous right now, it may arrive later.

=== Animal Training ===
{{main|Animal Training}}
[[File:animaltraining_medium_icon.png|right]]An animal training zone allows [[Animal trainer|animal training]]. Animals cannot be trained, unless they are in a training zone or [[pasture]], or on a [[restraint]]. To be tamed, they must be in a [[cage]].

For making an animal training zone, it is advisable to create a small room with a [[door]], which can be closed if necessary. The training zone should be combined with a pasture to keep in wild animals. This will make sure your animals don't escape when they are not being trained.

=== Dungeon ===
{{main|Jail}}
[[File:dungeon_medium_icon.png|right]]A dungeon is a room designed for [[justice|dwarven justice]]; and in each room, there must be 1 metal [[cage]] or a [[Restraint|rope/chain]]. Once the prisoner is selected to be imprisoned via the justice screen. the [[fortress guard]]/[[sheriff]] will chain or lock the creature in the selected chain or cage. The prisoner will continuously generate a bad thought while being imprisoned. so with some micromanagement, you can save the poor innocent [[cheese maker]] who violated the [[mayor]]'s export ban, from being overly stressed out, by deconstructing the chain as soon as they were chained up. A chain is recommended over a cage, as the chained up creature can still have access to the 8 tiles adjacent to the chain, granting them access to bed, food stockpile, chair and table, as well as allowing the prisoner to admire the chain if they were made from valuable metal like [[gold]] and [[platinum]]. While a caged prisoner is fully dependent on idle dwarves to deliver them food and drink (and only water instead of alcohol are delivered!). So they are more likely to starve to death than chained prisoners (provided you designate a food & drink stockpile within that can be reached by the chained prisoner). Plus, sleeping on a cage floor is, as expected, [[Stress|not very pleasant]].

=== Tomb ===
{{main|Tomb}}
[[File:tomb_medium_icon.png|right]]A tomb is designated to a specific dwarf ([[File:Interface dwarf face.jpg|26px]]), or a pet's corpse ([[File:Interface tomb pet.png|26px]]), to be buried or memorialized in order to prevent the appearance of [[ghosts]]. A tomb zone can only accommodate one dwarf. The primary function of tombs is to keep nobles happy: certain nobles demand their own tomb, and the more self-important the noble is, the higher the quality they will require. In some circumstances a noble will get an unhappy thought if an "inferior" dwarf has a higher-quality tomb, however it is unclear what quality threshold the tomb must be to trigger the thought. Also, a noble that demands a tomb also generates a bad thought at the end of every year if the tomb is yet to be built for them, or did not reach their [[#Quality_and_value|desired rank]]. Nobles may also store certain favored objects in their tombs. To be considered properly buried, at least ''half'' (rounded up, so no less than one) of their existing body parts must be buried.

=== Fishing ===
[[File:fishing_medium_icon.png|right]]Dwarves will preferably use these zones when [[fishing]], using them up until their supply is exhausted before moving on to the next water source. As with water sources, only tiles ''adjacent'' to water qualify as usable tiles. Far-flung fisherdwarves fishing in a distant [[river]] or [[pool]] are a serious defensive liability in case of an attack, so designating a safer fishing zone and, optionally, restricting non-zone fishing in the [[standing orders]] menu will help keep your fisherdwarves safe. Dwarves can fish through a [[grate]] or even a [[well]], provided there is water in the tile 1 z-level below the activity zone.

The [[Captured live fish|capture live fish]] job can ''only'' be carried out at a designated fishing zone.

=== Gather Fruit ===
[[File:gather_medium_icon.png|right]]This will automate plant-gathering jobs in this area, necessary if you want your dwarves to collect fruit from the floor ([[File:Ui gather fallen fruits.png|28px]]), from the [[shrub]]s ([[File:Ui gather shrubs.png|28px]]) and from the trees ([[File:Ui gather trees.png|28px]]). If there are fruit-bearing trees in the designated area, a dwarf will fetch a [[stepladder]] to climb into the tree. The ladder-using dwarf will drop harvested fruit to the ground for others to collect and haul. The details can be set in a sub-menu.

=== Sand collection ===
{{main|Glass industry#Collecting sand}}
[[File:sandpit_medium_icon.png|right]]A '''sand collection''' zone allows dwarves with the [[item hauling]] labor active to fill an unused [[bag]] with [[sand]] for use in the [[glass industry]]. The 'collect sand' task is created at a [[glass furnace]].

=== Clay collection ===
{{main|Ceramic industry#Clay collection}}
[[File:claypit_medium_icon.png|right]]A '''clay collection''' zone allows dwarves with the [[item hauling]] labor active to create [[clay]] for use in the [[ceramic industry]]. The 'collect clay' task is created at a [[kiln]].

== Quality and value ==

Most dwarves don't have high expectations when it comes to rooms - a communal [[dining room]] and [[dormitory]] are enough for the general populace, though making that dining room high-quality and giving them individual quarters will give them happy [[thoughts]], helping to avoid [[tantrum]]s.
[[Nobles]], on the other hand, require rooms of a particular minimum quality that contain certain [[furniture]]. Not meeting these demands will cause [[Emotion|stressful thoughts]], and may prevent them from functioning at their full capacity.

The thoughts generated by more impressive zones will have a stronger stress–relieving value than the thoughts generated by plain or unimpressive zones.

You can check a current rank of a room in the owner's [[profile]] on the "Rooms" tab. There are 8 rank names for each type of a personal room:

{| class = "wikitable unsortable" style="margin:auto;"
|-
! Bedroom name
! Dining room name
! Office Name
! Grave Name
! Numeric Value
|-
| Meager Quarters
| Meager Dining Room
| Meager Office
| Grave
| style="text-align:right;" | 0
|-
| Modest Quarters
| Modest Dining Room
| Modest Office
| Servant's Burial Chamber
| style="text-align:right;" | 100
|-
| Quarters
| Dining Room
| Office
| Burial Chamber
| style="text-align:right;" | 250
|-
| Decent Quarters
| Decent Dining Room
| Decent Office
| Tomb
| style="text-align:right;" | 500
|-
| Fine Quarters
| Fine Dining Room
| Splendid Office
| Fine Tomb
| style="text-align:right;" | 1000
|-
| Great Bedroom
| Great Dining Room
| Throne Room
| Mausoleum
| style="text-align:right;" | 1500
|-
| Grand Bedroom
| Grand Dining Room
| Opulent Throne Room
| Grand Mausoleum
| style="text-align:right;" | 2500
|-
| Royal Bedroom
| Royal Dining Room
| Royal Throne Room
| Royal Mausoleum
| style="text-align:right;" | 10000
|}
Note: unassigned (or communal) rooms may be referenced by other descriptors, such as the happy thought "... dined in a legendary dining room ...".

=== What counts towards room value ===

Room value can be loosely-split into 3 categories: walls, floors, and furniture (everything that is a placeable object goes here, including doors).

A room's furniture value is calculated simply by counting every item of furniture in the room and adding all their [[item value]]s up. Due to the quality-value nerf in v50, furniture is a less effective way to pump up a room's value.

[[Display furniture]] counts towards room value. However, the items ''displayed in it'' only count if the dwarf has a [[preference]] for them. So if your king likes [[sword]]s then any sword in a display case will count towards room value, and any other item (such as a [[crossbow]]), no matter how valuable, won't.

Unlike previous versions where natural surfaces were preferred, now ''placed'' floors and walls have a higher value than natural, with walls having a slightly higher value than floors. Wall and floor values are also calculated by adding all the individual tiles of walls and floor, but first we have to calculate the individual values...

=== Value calculation ===
The formula for calculating the final room value has changed significantly from prior versions of Dwarf Fortress. Thanks to research by TBTerra{{cite reddit|zzqlfu}}, the new formula has been discovered (and included here with only minor edits).

* '''[[Item value#Material multipliers|Material value]]''' - The value given to an item, floor, wall etc due to the material it is made from. ''Common material types:'' Natural spaces like sky, water, or magma are 1, wood is 1, rocks are 1–3, ores/metals are 2–40, gems are 2–60
* '''Pre v50 quality multiplier''' - This is still used in some places.
* '''Current quality multiplier''' - This is used for items.
* '''Quality bonus''' - a flat bonus added after the multiplier.

{| class="wikitable" style="text-align:right; margin:auto;"
|- style="text-align:center;"
! rowspan="2" | Quality
! colspan="2" | Quality multiplier
! rowspan="2" | Quality bonus
|- style="text-align:center;"
! Pre v50
! Current
|-
| style="text-align:center;" | -well crafted-
| 2
| 1.1
| 3
|-
| style="text-align:center;" | +finely crafted+
| 3
| 1.2
| 6
|-
| style="text-align:center;" | *superior*
| 4
| 4/3 ≈ 1.3
| 10
|-
| style="text-align:center;" | ≡exceptional≡
| 5
| 1.5
| 15
|-
| style="text-align:center;" | ☼masterful☼
| 12
| 2.0
| 30
|-
| style="text-align:center;" | Artifact
| 120
| 20.0
| 300
|}

=== Values of floor tiles ===

The value of an individual floor tile depends on if it's the original cave floor, a smoothed cave floor, or a placed floor.

;raw cave floor
:1 × material value
;Smooth cave floor
:4 × material value
;placed cave floor
:7 × material value

Additionally if the floor is engraved you add an extra 10 × material value × old quality multiplier.

=== Values of wall tiles ===

Again value depends on whether its original stone, smoothed stone, or placed wall. (Boulders, bars, and blocks of the same material type all have the same value.)

;original wall
:1 × material value
;smoothed wall
:5 × material value
;placed wall
:9 × material value

[[Engraving]] with walls is not always a simple matter. In order for an engraved wall to add its engraving to the room value, the room must contain both the wall itself ''and'' the location the engraver was standing when it was engraved. This means that an engraved wall shared between two zones will only add its value to one of those zones, whichever one the engraver was standing in when that engraving was done.

The value of a wall engraving is 10 × old quality multiplier × material value.

=== Overlapping Rooms ===
[[File:overlapping_zones_preview.png]]{{clear}}
When room designations such that they share floor tiles, the label of some zones in that same area will be renamed to "Overlapping (Zone)" in red text. When selecting an overlapped area, the player is able to select the zone layers with clickable arrows on either side of the zone name. Zones in this state have their values set to 0{{cite reddit|13097u3/comment/jhwgm0e}}. There is no difference in value between a piece of furniture shared by two rooms, or by forty.

Sharing walls is fine however, and sharing doors is allowed as long as the room contains a wall adjacent to the door. When sharing a door, the floor tile it is on is also shared.

[[Location]]s have individual values and are therefore not affected by overlapping zones (eg. A ''Dining Hall/Tavern'' overlapping a ''Meeting Hall/Temple'' will have both Dining and Meeting halls value to 0, but the Temple and the Tavern will share the same values{{cite forum|181632.msg8475740#msg8475740}}.

=== Building optimally ===

If you are limited on your high-value materials (or have lots of rooms you wish to improve) and don't want to abuse wall sharing or other glitches, here's how best to use those high value mats:

# Use your high-value materials on floor tiles, not furniture. A decently-engraved floor has a value of 37–57 × material value; the only thing that gets close to that is the mechanisms in levers.
# The floors of doors that go between rooms you wish to increase are of particular importance as they will count for both rooms.
# Engravings are tedious to redo (For a natural floor, you will need to carve tracks and smooth over before re-engraving. For constructed floors, you will need to build a wall, then carve fortifications, remove the fortification and replace the floor). To minimize the extra work of redoing engravings, leave your highest-value tiles to be done by your most experienced engraver so they will have a high quality on the first try.

=== Breaking room value ===

Since version 50, there is nothing that requires a room to be a single connected piece. This, combined with wall sharing, allows for some… less than fair cheesing of platinum walls that are somehow owned by every single bedroom. And with a trick in the “how to break room value” section, you can have every room royal quality for as little as 4 platinum and 6 basic wood/stone

So you don’t care about using glitches and non–contiguous rooms. Here’s the way you break room value with minimal effort and resources:
[[File:Zone value breaking example.png|thumb|200px|Steps 2 and 3.]]
# Make a line of wall with a 1 tile gap on either side (if your engravers are really good this might only need to be 2–3 long).
# Make the lines of floor either side of this wall out of the most valuable material you can (aluminum or platinum are great, steel and gold also work), and have your best engraver engrave them.
# Place doors on top of all those engraved tiles, what sort doesn’t really matter, as they will be adding 10–100 value to 2–3k value floor tiles.
# For every room ''on the same [[z-level]]'' add the doors and the wall (this is a convenient rectangle). The wall makes the doors shareable, and the doors make the engraved floor shareable.
# For optimal results hide this to the south east of your area, otherwise the zone icons can get rather confusing.

You can also assign arbitrary stretches of space on the same z-level, such as sky, magma, or water, as part of the zone to increase value. Because the standard 4×4 embark contains 192×192=36864 tiles, each with a value of one, designating one entire z-level of sky would instantly create a royal quality zone.

{{Zones}}
{{V50 menus}}
{{Category|Fortress mode}}
{{Category|Zones}}
[[ru:Zones]]

Glass industry

2026-04-03T23:26:40Z

Ziusudra: /* Collecting sand */ added that the zone can be next to a sand wall, verify template for exploit

{{Quality|Superior}}
{{av}}
[[File:Agricola-4.png|thumb| The glass industry can be a modern technological marvel.]]
The '''Glass Industry''' is a versatile and, under the right circumstances, sustainable source of items. Everything from [[finished goods]] to [[furniture]] to low value [[glass]] [[gem]]s to [[block]]s to [[trap component]]s can be created from [[glass]], making [[Glassmaker]] a very useful profession. Since glass is [[magma-safe]] and capable of producing all necessary [[screw pump]] components, a glassmaking industry can prove quite valuable when working with [[magma]].

==Producing glass==
The limiting factors to [[glass]] production are [[sand]] and [[fuel]]; in order to produce glass in great quantities, your map must have sand (any single tile has an infinite amount of sand) and either a good source of coal, magma or many trees. Small quantities of sand can regularly be acquired from [[caravan]]s, but rarely enough to run a large industry. Soil layers may or may not include sand; the [[embark screen]] should display "Sand" when/if the embark contains any. If you want to ensure the possibility of a flourishing glass industry, embark on a [[sand desert]] or [[badlands]] biome. Keep in mind that these biomes by themselves don't have [[tree]]s to [[fuel]] your furnaces early on. Another option is to embark adjacent to an [[ocean]], as the [[beach]]es are usually composed of sand, but this usually results in fighting the [[aquifer]]s that predictably accompany a coastline, lengthening the time it takes to begin to [[mine]] down to the [[magma]] sea.

To make items from glass, sand must first be gathered in [[bag]]s using a task available at any [[glass furnace]], "Gather Sand". You must designate a [[activity zone|Sand Collection zone]] from the ({{k|z}})-menu that includes an accessible area of sand in order for this task to be performed. Only cut glass "gems" (and [[artifact]]s) can be made from raw glass purchased from [[caravan]]s. All other glass objects must be made from "sand bearing items", i.e. bags of sand.

Once you have one bag of sand you can order glass to be created at a furnace. A standard [[glass furnace]] will consume one unit of [[fuel]] per job; a [[magma glass furnace]] uses no fuel.

===Collecting sand===
All sustainable types of glassmaking require a [[bag]] of [[sand]]. The "Collect [[Sand]]" order at the glass furnace requires the "[[hauling#Item_hauling|item hauling]]" labor, not glassmaking (i.e. setting a custom work detail for glassmaking will not stop other dwarves from completing a collect sand task at a glass furnace). The Collect Sand order does, however, still occupy the glass furnace, preventing glassmakers from performing any other jobs there until after the collection has been completed.

Sand for glass can only be collected from [[Zone#Sand_collection|collection zones]] placed on floors made of, or floors next to walls made of, "[[Sand (tan)|Sand]]", "[[black sand]]", "[[red sand]]", "[[white sand]]", or "[[yellow sand]]". Any sandy [[soil]] type with "[[Sandy loam|Loam]]" or "[[Loamy sand|Loamy]]" in it will not work for glassmaking.

====Collecting sand efficiently====
Due to the work order rework in {{release notes link|0.43.01|inline=1}}, setting up automatic collect sand orders is fairly simple. The steps to do so are as follows:
:*Create a new work order to Collect Sand.
:*Enter the set conditions menu for the order, and add two new conditions.
:*In the first condition, click Type, then enter "bags". Then click Adj and enter "empty items". You may be sent back to the work order menu when you hit escape, so re-enter the Collect Sand task. Now set the number to something reasonable (if you don't want too many job cancellations, set it higher than the number of times the order is set to run (default is 10). The first condition should now read: "Amount of empty bags available is at least 10".
:*In the second condition, click Adj and enter "sand-bearing items". You may also enter the Type "bags", but it is not necessary. Now set the number to the number of bags you wish to keep on hand at any given time. Finally, set the inequality to "less than" or "at most". The second condition should read: "Amount of sand-bearing items available is less than 20".
I would recommend setting this work order up in a dedicated glass furnace next to your sand collection zone so as not to interfere with glass production. To do this, click on your glass smelter, click on Work Orders, set general work orders allowed to zero, then follow the above steps, clicking on the create new work order button inside the shop instead of in the main Work Orders menu.

====Creating sand tiles====
If your embark has sand as a soil type you might be able to create sand tiles next to your glass furnaces, although this could be considered an exploit:
:* Create mud on a rough rock floor (a dusting of mud is enough).
:* Breach the caverns, allowing fungus to grow on the mud.
:* Once fungus has grown, build a wall on the mud, then deconstruct it. This will change the tile type from rock to soil.
If your embark has sand as the only soil type, then the tile will always change to sand. If you have multiple soil types, one will be randomly chosen.{{verify|Might be what ever the lowest soil layer for that biome is}} If you do not get sand, you can repeat the process on another tile until you do. Once you have a sand tile, build a floor grate over it. This will stop fungus regrowing and will not block sand collection.

==Varieties of glass==
:*Producing '''green glass''' requires only a bag of sand. Green glass items are [[value|worth]] twice as much as objects made from most [[stone]], making it equivalent to cheap metals like [[copper]] and [[zinc]].

:*Producing '''clear glass''' requires one bar of [[pearlash]] in addition to a bag of sand. Clear glass items are worth five times as much as items made from most stones, making it equivalent to metals like [[bronze]].

:*Producing '''crystal glass''' requires no sand, but does require pearlash and rough [[rock crystal]]s, a [[gem]] which is not found on all maps. Cut rock crystals bought from [[trader]]s will not work for producing crystal glass. Crystal glass is worth ten times as much as objects made from most stones, making it equivalent in value to metals like [[silver]].

See also "[[Glass]]" for a full discussion of the properties of glass items.

==Glass Industry Flowchart==

[[Image:Glass Industry 2012 Update.png|Flowchart of the glass industry and its interaction with surrounding industries.]]

==Glassmaking vs. other professions==
Functionally, the glass industry is like a cross between the [[stone industry]] and the [[metal industry]], incorporating elements from both. Functionally, it is similar to metalworking, using a furnace and fuel to produce its products, and its products can have material values similar to metals. Meanwhile, its actual product output is most similar to stoneworking, with only a few differences, and it can pretty much fully replace masonry except for those instances.

===vs. Stoneworking===
There is considerable overlap between items produced from [[stone]] at a [[Mason's workshop]], and items produced from glass at glass furnaces. [[Mason]]ry is easier to get running and will [[stone management|clear excess stone]] from your fortress. Glass produces items with a higher base [[value]] (unless you make your masons use flux or [[obsidian]]), and using a [[magma glass furnace]] allows you to make green glass objects without consuming anything but dwarven labor. Glass also provides a [[magma-safe]] alternative, to prepare for magma-based projects before it's discovered or avoid stockpile micromanagement for the correct building materials. Unique stone products which cannot be made of glass are querns/millstones, slabs, crafts, and stone short swords.

===vs. Metalworking===
There are many similarities in the processes between [[metalsmithing]] and glassmaking. Both require fuel, and both require supplementary materials for certain unique products. Additionally, crafts are made directly at the furnace, rather than at a craftsdwarf's workshop. Metalworking is generally more likely to be started first, as any site will eventually find metals and fuel, (if even only in the form of magma) and quality weapons are often needed to start a military, but how much you can make is limited by how much you can dig up or buy. Glassmaking has the potential to produce ''infinite'' products, if given sand, enough bags, and magma. Also, while metal ores are turned into an intermediary material, (bars) by another profession at a different workshop, which must then be forged into a product, glassmaking produces a product directly from the raw materials, and still leaves you with an empty bag. Finally, metalworking has a far more diverse range of products, including restraints, weapons, and armor.

==Glassmaking and [[minecart]]s==
In a typical fortress, [[magma]] is located deep below, while sand is a soil layer and thus without some creative management is just below ground. Without minecarts, each sand bag will be carried by a single dwarf, thus requiring a lot of dwarf labor and wide staircases. With minecarts one can not only transport a lot of sand bags to the magma furnace without much dwarf-time wasted on hauling, but also transport all the glass products back up. If set up, the track can be also used to supply (and grab from) [[magma smelter]] which is likely to be located close to [[magma glass furnace]].
If one is too lazy to set up a track, minecart system can be easily used simply to haul all the sand bags in a convenient container (requires a wooden minecart). If both endpoints are set to '''guide''', but are left disconnected, dwarves will just grab the minecart and haul it to their destination. Since sand bags and wooden minecarts are both reasonably light, the dwarf won't slow down much. Another solution if you have an iron (magma safe) minecart is to use it to haul magma up and dump it in a channelled tile in your sand level (video tutorial linked [https://youtu.be/jlpj9qimx4s here]). If you then build magma glass furnaces on top of that magma you can avoid multi z-level hauling since your entire glass industry will be in one location.
{{Category|Industry}}
{{Industry}}
[[ru:Glass industry]]

Glass

2026-04-03T22:41:34Z

Ziusudra: /* Uses */ added creatures not seeing through glass floors/walls

{{Quality|Exceptional}}
{{av}}
[[File:glass_preview.png|right]]'''Glass''' is produced at the [[glass furnace]] using [[fuel]] with either [[sand]] (green glass), sand and [[pearlash]] (clear glass), or [[rock crystal]] and [[pearlash]] (crystal glass). A [[magma glass furnace]] can also be used, in which case no fuel is required. Raw glass (of all three types) can also be acquired from some [[trading|trade]] caravans and be purchased in the [[embark]] screen. You have to buy or collect [[sand]] to get the raw materials to make glass.

Glass value corresponds to the difficulty of its production, with green glass having the lowest material value (2), clear glass, intermediate (5), and crystal glass, the highest (10).

== Uses ==
Glass can be used for most things that can be produced at a [[Stoneworker's workshop]], except slabs, querns and millstones. Glass can also be used to make [[tube]]s. Note that the names for some glass products are different from the same products made from different materials. For example, a glass tube has the same uses as a wooden pipe. It can also be used to produce goods normally made at a [[craftsdwarf's workshop]] by a [[stone crafter]], except obsidian short swords and generic crafts. In addition, it may be made as raw glass, which can then be cut as a gem at a [[jeweler's workshop]] by a [[gem cutter]], similarly to cutting generic stones. Note that raw glass '''''cannot''''' be made into glass items (excluding [[strange mood]]s), but can only be cut into [[gem]]-like items which can be used for [[decoration|decorating]] items.

Raw glass, especially raw green glass, is excellent practice for aspiring jewelers (and its production provides experience for [[glassmaker]]s). The value of glass is on par with low-to-mid value gemstones, meaning that a source of sand on your map used in tandem with a [[magma glass furnace]] makes decoration with cut raw green glass an essentially free, and very lucrative, way to increase the value of your goods, while training legendary [[glassmaker]]s and [[jeweler]]s – particularly when those goods are themselves made of glass.

Glass can also be made into [[block]]s which can be used to build [[workshop]]s and [[construction]]s, even glass [[trap component]]s. Creatures cannot see through floors or walls made from glass blocks, even though the graphics are transparent. Unique goods made from glass include glass [[window]]s and [[flask|vial]]s, as well as [[Furniture#Furniture_types_with_multiple_names|renamed versions]] of common furniture.
* A glass [[chest]] is called a box.
* A glass [[door]] is called a [[portal]].
* A glass [[pipe]] is called a tube.
* A glass [[cage]] is called a terrarium.
* A glass [[flask]] is called a [[vial]].

For more information on the use of glass, see the [[Glass industry]] page.

Raw and cut glass storage options can be found under the Gem [[stockpile]] sub-menu. Glass blocks are stored in Bar/Block stockpiles.

==Glass Block Floors, AKA The Dwarven X-Ray==
In DF Premium's graphical mode, floors made out of glass blocks reveal the z-level directly beneath them and everything on those tiles in real time, even if built on top of a solid cave floor. This exploit can be useful when you want to avoid digging into [[Hidden Fun Stuff]], because even though players can see through glass floors no matter what, entities in the game itself never can.[https://www.reddit.com/r/dwarffortress/comments/10tpcbd/glass_floors_reveal_without_digging/]

==Glass and magma==
Glass behaves somewhat oddly with [[magma]], despite being strictly magma-safe (with a melting point of {{ct|13600}}) – '''built''' glass furniture will survive indefinitely when covered with magma, but '''unbuilt''' glass items tend to disappear instantly when submerged in magma.{{bug|10314}}

==Physical properties==
Through memory hacking, the material properties of each type of glass have been determined; for reference, they have been reconstructed below as material definitions:

{{gamedata|title=Green glass
|{{raw|DF2014:hardcoded_materials.txt|MATERIAL|GLASS_GREEN}}}}

{{gamedata|title=Clear glass
|{{raw|DF2014:hardcoded_materials.txt|MATERIAL|GLASS_CLEAR}}}}

{{gamedata|title=Crystal glass
|{{raw|DF2014:hardcoded_materials.txt|MATERIAL|GLASS_CRYSTAL}}}}

==See also==
*[[Glass industry]]
*[[Glassmaker]]

{{materials}}

{{Category|Materials}}
[[ru:Glass]]

Settings

2026-04-03T22:24:51Z

Ziusudra: added mention of colors.txt and arena.txt to intro

{{av}}
{{Quality|Fine}}
Settings for ''Dwarf Fortress'' can be accessed with a button on the main menu, which can be accessed in-game with {{Menu icon|Esc}}. They are divided into six groups; Video, Audio, Game, Keybindings, Announcements, and Difficulty. They are stored in several different files, including [[init.txt]], [[d_init.txt]], and [[interface.txt]], with current values in the <code>prefs\</code> folder and default values in the <code>data\init\</code> folder. The default files in <code>data\init\</code> include explanations of each setting, including possible values. The files in both <code>data\init\</code> and <code>prefs\</code> are read when ''Dwarf Fortress'' starts, in that order, with the last value read for each option being used. The location of the <code>prefs\</code> folder depends on various factors, see [[Game folders and files]]. Not all of the settings can be changed in game, including [[colors.txt]], [[arena.txt]], and some keybindings.

== Video ==
These settings change how the game looks and are all stored in <code>prefs\init.txt</code> and defaults in <code>data\init\init_default.txt</code>.
* '''Windowed or Fullscreen''' - the highlighted button is the active one and they correspond with [WINDOWED:YES] or [WINDOWED:NO] in the files. [WINDOWED:PROMPT] can be set in the files to make the game ask when starting up, in which case neither button will be highlighted.
* '''Resolution''' - the screen mode the game uses when in fullscreen mode, 'Detect' corresponds with [FULLSCREENX:0] and [FULLSCREENY:0] in the files.
* '''Scale interface''' - whether to scale the font used to draw interface elements such as the menus and minimap to a specific number of character cells, [INTERFACE_SCALING_TO_DESIRED_GRID:YES] in the files.
* '''Desired grid width and height''' - how much to scale the interface, in how many character cells wide and tall the interface should be. [INTERFACE_SCALING_DESIRED_GRID_WIDTH:170] and [INTERFACE_SCALING_DESIRED_GRID_HEIGHT:64] in the files. No effect if [INTERFACE_SCALING_TO_DESIRED_GRID:NO] is used.
* '''Interface scale percentage''' - percentage to scale the interface character cell size up when not scaling to specified grid counts, not every value makes a difference since the interface won't display a partial character at the edges. [INTERFACE_SCALING_PERCENTAGE:100] in the files, no effect if [INTERFACE_SCALING_TO_DESIRED_GRID:YES] is used.
* '''Initial window size''' - when not fullscreen, [WINDOWEDX:1200] and [WINDOWEDY:800] in the files.
* '''Window resizable''' - when not fullscreen, [RESIZABLE:YES] in the files.
* '''Maximum interface width''' - what percentage of the display the overlay interface elements can occupy, useful for extra wide displays to make notifications more visible. [MAXIMUM_INTERFACE_PERCENTAGE:100] in the files. The game will still use the entire window/screen and the minimap and elevation bar will stay at the edge.
* '''Graphical FPS cap''' - how many frames to cap the graphical display rate at. [G_FPS_CAP:50] in the files.
* '''Classic ASCII''' - [USE_CLASSIC_ASCII:NO] in the files.
* '''Scaling mode''' - NEAREST, nearest-neighbor, distorts shapes at some zoom levels; LANCZOS, less distortion but fuzzier at some zoom levels; AUTO, the default, will try to select whichever one is more appropriate depending on the zoom level. [TEXTURE_PARAM:AUTO] in the files.

As the interface gets narrower, some elements will be removed from the [[status]] bar when there's not enough room for all of them; some menus may also display elements under other elements or outside their window.

There are a few other file settings that can affect the display, see [[Technical_tricks#Settings_-_init.txt|technical tricks]].

== Audio ==
These settings change how the game plays sounds and are all stored in <code>prefs\init.txt</code> with defaults in <code>data\init\init_default.txt</code>. All volumes can be from 0 to 255 in the game files, with 255 being 100%.
* '''Master Volume''' - [MASTER_VOLUME:255] in the files.
* '''Music Volume (Fortress)''' - [MUSIC_VOLUME:255] in the files.
* '''Ambience Volume (Fortress)''' - [AMBIENCE_VOLUME:230] in the files.
* '''Sound Effects Volume (Fortress)''' - [SFX_VOLUME:204] in the files.
* '''Average Seconds Between Tracks/Interludes (Fortress)''' - [AVERAGE_TIME_BETWEEN_SONGS:240] in the files. The default of 240 gives a range of 180 to 300 seconds, which is 3 to 5 minutes. Can be anywhere from 10 to 600.
* '''Music Volume (Adventure)'''{{v|51.01}} - [MUSIC_VOLUME_ADV:217] in the files.
* '''Ambience Volume (Adventure)'''{{v|51.01}} - [AMBIENCE_VOLUME_ADV:240] in the files.
* '''Sound Effects Volume (Adventure)'''{{v|51.01}} - [SFX_VOLUME_ADV:230] in the files.

The classic version of the game available on the website only includes the original songs, so most of these will have no effect without the [[premium version]] or mods.

All sound can be disabled completely with [SOUND:NO] in the files. If so, the rest of these settings will be replaced by text explaining that sound is disabled and how to enable it.

== Game ==
These settings change how the game plays and most are stored in <code>prefs\d_init.txt</code> with defaults in <code>data\init\d_init_default.txt</code>, but some are in <code>prefs\init.txt</code> with defaults in <code>data\init\init_default.txt</code>.

=== Portable mode ===
* '''Portable mode'''{{v|52.01}} - when set to NO, the game stores mods, preferences, and saves in a folder specific to the user, (see [[game folders and files]] for details) when set to YES, it stores them in the game folder. Changing this to YES creates the empty file <code>prefs\portable.txt</code>, changing back to NO removes it; manually creating or removing the file changes the setting.

=== Autosaves ===
{{for/see|more information about autosaves|[[Saved_game_folder#Save_folder_format|Saved game folder]]}}
* '''Autosave frequency''' - when to autosave, [AUTOSAVE:SEMIANNUAL] in d_init.txt, NONE, SEASONAL, SEMIANNUALLY, or YEARLY.
* '''Autosave at embark''' - [INITIAL_SAVE:NO] in d_init.txt, YES or NO. Additionally to inital saving the game: If set to YES (and the game is paused in the beginning) then the game is paused (and saved) before a dwarf gets assigned to fishing duty (if water to fish in is available), otherwise (meaning this option is set to NO), if there is water, a dwarf is assigned to fishing duty (even if the game is paused in the beginning).

=== Pausing ===
* '''Pause after autosave''' - [AUTOSAVE_PAUSE:NO] in d_init.txt, YES or NO.
* '''Pause after loading''' - [PAUSE_ON_LOAD:YES] in d_init.txt, YES or NO.

=== Embark ===
* '''Always confirm embark''' - asks for confirmation of the embark location even if there are no warnings such as for [[aquifer]]s, dangerous [[surroundings]], etc, [EMBARK_WARNING_ALWAYS:NO] in d_init.txt, YES or NO.
* '''Confirm preparations''' - [POST_PREPARE_EMBARK_CONFIRMATION:IF_POINTS_REMAIN] in d_init.txt, ALWAYS, IF_POINTS_REMAIN, or NO.
* '''Show tunnels when embarking''' - for dwarven [[tunnel]]s, shown as a black dashed line or grey double line with classic ASCII, [SHOW_EMBARK_TUNNEL:FINDER] in d_init.txt, FINDER, ALWAYS, or NO.{{verify|is there a difference between ALWAYS and FINDER now?}} More restrictive world generation settings will override these.
* '''Default embark width and height''' - also determines what is considered a normal embark size and will only warn when the actual embark is larger than this many (width × height) tiles, [EMBARK_RECTANGLE:4:4] in d_init.txt, 2 to 16. See Maximum embark dimension below. (This option is actually listed after the feature toggles on the tab in game.)
* '''Maximum embark dimension''' - maximum width or height for an embark, larger sizes may be buggy and need much more memory, [MAXIMUM_EMBARK_DIM:6] in d_init.txt, 6 to 16. (This option is actually listed in game near the bottom of the tab, before the dye and scroll options.)

=== Feature toggles ===
* '''Enable temperature''' - If temperature calculations are off, only a few direct temperature changes will take place. For example, magma will set tiles and creatures to high temperatures, but those tiles will never cool and those creatures will not catch fire. Effects that rely on temperature calculations, such as water freezing, melting, or evaporating, or creatures and items taking temperature-related damage, will not occur. May affect FPS in unusual circumstances, [TEMPERATURE:YES] in d_init.txt, YES or NO.
* '''Enable weather''' - toggles rain and snow, rarely affects FPS, [WEATHER:YES] in d_init.txt, YES or NO.{{verify|does this affect wind or evil weather?}}
* '''Enable caveins''' - toggles [[cave-ins]], [CAVEINS:YES] in d_init.txt, YES or NO.
* '''Enable artifact moods''' - toggles [[strange mood]]s and the resulting [[artifact]]s, [ARTIFACTS:YES] in d_init.txt, YES or NO.{{verify|does this affect world gen artifacts?}}
* '''Enable testing arena''' - [TESTING_ARENA:YES] in d_init.txt, YES or NO.
* '''Walking spreads spatter (fort mode)''' - toggle the spread of blood spatter and other [[contaminant]]s by creatures on ground tiles in fortress mode. As spatter can infinitely spread, it is recommended to leave this as "NO". [WALKING_SPREADS_SPATTER_DWF:NO] in d_init.txt, YES or NO.
* '''Walking spreads spatter (adv mode)'''{{v|51.01}} - toggle the spread of blood spatter and other [[contaminant]]s by creatures on ground tiles in adventure mode. As spatter can help with tracking creatures, it is recommended to leave this as "YES". [WALKING_SPREADS_SPATTER_ADV:NO] in d_init.txt, YES or NO.
* '''Enable keyboard cursor''' - allows for using the keyboard controls for some designations, [KEYBOARD_CURSOR:NO] in d_init.txt, YES or NO. Arrow keys {{k|↑←↓→}} move one tile, {{k|WASD}} 10 tiles, and {{k|Shift|WASD|sep=+}} 20 tiles; also see [[Settings#Keyboard_scroll_amounts|Keyboard scroll amounts]] section below.
* '''Log world rejects''' - logs the reasons worlds were rejected in ``[[map_rejection_log.txt]]``, useful in [[advanced world generation]] and [[modding]], [LOG_MAP_REJECTS:NO] in d_init.txt, YES or NO. ''Dwarf Fortress'' will keep adding to the file, so you may want to trim or delete it occasionally.
* '''Multithreading''' - limited experimental multithreading, [MULTITHREADING:NO] in d_init.txt.
* '''Classic varied ground tiles'''{{v|51.05}} - if changed to NO, ground tiles will be displayed only with periods in ASCII mode, [CLASSIC_VARIED_GROUND_TILES:YES] in d_init.txt. (This option is actually listed in game near the bottom of the tab, before the scroll options.)
* '''Show rectangle dimensions'''{{v|51.06}} - if changed to NO, hides the size display when drawing selection retangles, [SHOW_RECTANGLE_DIMENSIONS:YES] in d_init.txt. (This option is actually listed in game near the bottom of the tab, before the scroll options.)

=== Pathing costs ===
* '''Path costs''' - extreme changes to these may cause more lag, [PATH_COST:1:2:5:25] in d_init.txt, 1 to 1000.
* '''Storage path cost decreases''' - controls how aggressively dwarves place objects in a container with like items (rather than an empty container). The default combine options are very aggressive. All in d_init.txt, 2 to 1000.
** [STORE_DIST_ITEM_DECREASE:20] - for each object found in a container, one tile is removed from its apparent distance to the dwarf, up to this cap
** [STORE_DIST_SEED_COMBINE:1000] - a bag with seeds already in it will appear this many tiles closer
** [STORE_DIST_BUCKET_COMBINE:1000] - a bucket with the same liquid already in it will appear this many tiles closer
** [STORE_DIST_BARREL_COMBINE:1000] - a barrel with the same item type already in it will appear this many tiles closer
** [STORE_DIST_BIN_COMBINE:1000] - a bin with the same item type already in it will appear this many tiles closer

=== Population and seed capacities ===
* '''Population caps''' - can be changed at will to limit migration, strict also prevents births, [POPULATION_CAP:200] and [STRICT_POPULATION_CAP:220] in d_init.txt, 0 to 5000. Certain game features are triggered by population number, see [[difficulty]]. Some of those features may also cause the actual population to slightly go over these.
* '''Children limits''' - how many and what percentage of total there can be at a time, [BABY_CHILD_CAP:100:1000] in d_init.txt, 0 to 1000. Only prevents further pregnancies, so migrant children, multiple births and existing pregnancies from old saves can still push you over the cap. Setting either number to zero will disallow new pregnancies in the fortress.
* '''Visitor cap''' - This does not include merchants, diplomats, animals or invaders, but only those dropping by for a temporary visit to a tavern, library or temple, or those seeking permanent employment. Once you accept a petition from a visitor to stay at your fort, they no longer count against the cap, even if they never become a full citizen. [VISITOR_CAP:100] in d_init.txt, 0 to 5000.
* '''Dead units cull''' - During a season changeover, the game checks if there's a certain number of units in play. If it is above this amount, it removes all the unimportant dead units who died at least two years ago. [CULL_DEAD_UNITS_AT:1000] in d_init.txt, 100 to 5000.
* '''Seed caps''' - per type and total, when over the total cap, seeds will be periodically removed, starting with the oldest and most worthless. [SPECIFIC_SEED_CAP:200] 0 to 10000 and [FORTRESS_SEED_CAP:3000] 0 to 30000 in d_init.txt.

=== Information display ===
* '''Engraving display''' - [ENGRAVINGS_START_OBSCURED:NO] in d_init.txt, YES or NO.
* '''Improvement quality display''' - [SHOW_IMP_QUALITY:YES] in d_init.txt, YES or NO.
* '''Numeric liquid levels''' - can be toggled in game either with a button next to the minimap or a keybind {{menu icon|f}}, [SHOW_FLOW_AMOUNTS:NO] in d_init.txt, YES or NO.
* '''Ramp arrows''' - can be toggled in game either with a button next to the minimap or a keybind {{menu icon|r}}, [SHOW_RAMP_ARROWS:NO] in d_init.txt, YES or NO.
* '''Elevation layers display''' - [NUMBER_OF_LOWER_ELEVATIONS_SHOWN:8] in d_init.txt, 0 to 8.
* '''Engraving historical events''' - [SHOW_ALL_HISTORY_IN_DWARF_MODE:YES] in d_init.txt, YES or NO.
* '''Nickname display''' - [NICKNAME_DWARF:REPLACE_FIRST], [NICKNAME_ADVENTURE:REPLACE_FIRST], [NICKNAME_LEGENDS:REPLACE_FIRST] in d_init.txt, REPLACE_FIRST, CENTRALIZE (between first and last), or REPLACE_ALL.

=== Grazing coefficient ===
* '''Grazing coefficient''' - how much grazers get from grazing, larger numbers mean less food is needed. [GRAZE_COEFFICIENT:100] in d_init.txt, 1 to 1000000.

=== FPS ===
* '''Show FPS''' - the first number is simulation rate, the number in parentheses is graphical FPS, [FPS:NO] in init.txt, YES or NO.
* '''Game FPS cap''' - limits how quickly the game runs the simulation, [FPS_CAP:100] in init.txt, 5 to 1000. This cap can also be temporarily changed on the fly by ~10% with {{k|Alt|Equals|sep=+}} and {{k|Alt|Minus|sep=+}}; if '''Show FPS''' is set to yes, then pressing either of those will briefly show what the cap has been changed to.

=== Input timings ===
* '''Key hold time''' - [KEY_HOLD_MS:250] in init.txt, 100 to 20000.
* '''Key repeat time''' - [KEY_REPEAT_MS:150] in init.txt, 100 to 20000.
* '''Key repeat acceleration''' - [KEY_REPEAT_ACCEL_START:10] 1 to 1000 and [KEY_REPEAT_ACCEL_LIMIT:8] 2 to 100 in init.txt.
* '''Interface shutdown time''' - how long after a view recenter to ignore input, [RECENTER_INTERFACE_SHUTDOWN_MS:0] in init.txt, 0 to 2000.
* '''Macro timing''' - [MACRO_MS:15] in init.txt, 1 to 2000.

=== Compressed saves ===
* '''Compressed saves''' - saves drive space (since running out of space while saving '''will''' corrupt the save) at the expense of slowing down save operations, [COMPRESSED_SAVES:YES] in init.txt, YES or NO.

=== Dye display ===
* '''Display worn clothing dyes (fort mode)'''{{v|50.15}} - if set to the default NO, color will be determined by [[profession]], mostly only useful in ASCII mode, [DISPLAY_CLOTHING_WITH_DYES_IN_FORT_MODE:NO] in d_init.txt, YES or NO.
* '''Display worn clothing dyes (adv mode)'''{{v|51.01}} - if changed to NO, color will be determined by profession, [DISPLAY_CLOTHING_WITH_DYES_IN_ADV_MODE:YES] in d_init.txt, YES or NO.

=== Keyboard scroll amounts ===
* '''Keyboard scroll tiles'''{{v|51.11}} - how many tiles to scroll with the "Move view/cursor" keys (default {{k|WASD}}, the FAST settings are used for {{k|Shift|WASD|sep=+}}) in the normal and world views, as well as the [[Settings#Feature_toggles|keyboard cursor]], though for that, the cursor keys {{k|↑←↓→}} also always move 1 tile, in addition to these values for the "Move view/cursor" keys. 1 to 100, and the following tokens in d_init.txt
**[HORIZONTAL_SCROLL_SPEED:10]
**[HORIZONTAL_SCROLL_SPEED_FAST:20]
**[VERTICAL_SCROLL_SPEED:10]
**[VERTICAL_SCROLL_SPEED_FAST:20]
**[HORIZONTAL_SCROLL_SPEED_WORLD:10]
**[HORIZONTAL_SCROLL_SPEED_WORLD_FAST:20]
**[VERTICAL_SCROLL_SPEED_WORLD:10]
**[VERTICAL_SCROLL_SPEED_WORLD_FAST:20]

== Keybindings ==
{{main|Controls}}{{main|interface.txt}}
These settings change the controls and are all stored in interface.txt.

== Announcements ==
{{main|Announcement}}{{main|announcements.txt}}
Used to control how different announcements are displayed in Dwarf Fortress. This can be useful to add alerts for critical combat events, stopping the recentering on birth events, or reducing the constant chatter of announcements like 'quota filled' or 'someone is visiting'.

== Difficulty ==
{{main|Difficulty}}
This tab is only available when in a fortress game, and these settings are initially set when starting a fortress game. Since they are specific to each save they are stored as part of the save and are not editable outside the game. They are divided into two groups: enemies and economy; enemies can be disabled, both groups have normal and hard presets, and all of the individual settings can be adjusted in '''Custom settings'''. The values used in each preset can be seen by selecting the preset and then viewing them in '''Custom settings'''.

[[ru:Settings]]

Color scheme

2026-04-03T22:11:26Z

Ziusudra: trimmed intro, added prefs override, moved labels to 1st section

{{Quality|Exceptional}}
{{av}}

''(For a discussion of how DF displays different items, and decides which colors get altered and when, see [[color]].)''

''Dwarf Fortress'' uses '''color schemes''' to determine how the game will be presented during play, with the default color scheme data located in the [[colors.txt]] file, found in the <code>Dwarf Fortress/data/init</code> folder, but <code>prefs/colors.txt</code>{{version|52.02}} will override that, if it exists.

[https://manmademagic.github.io/DFColorGen/ DFColorgen] is a web tool to create and visualize color schemes.

==What colors show up where==
A color scheme is broken down into 16 color labels:

:BLACK, DGRAY
:BLUE, LBLUE
:GREEN, LGREEN
:CYAN, LCYAN
:RED, LRED
:MAGENTA, LMAGENTA
:BROWN, YELLOW
:LGRAY, WHITE

The easiest place to see all the colors next to each other is in the {{k|u}}nits list, where the different [[Skill#Professions.2C_colors.2C_.26_skill_categories|professional categories]] all have their identifying colors. In that order (and with the default color values), they are...
{| style="margin: 0 auto"
|-
| valign='top' |

{{Skill Box|BLACK|0:0|0:0|
''background''
}}

{{Skill Box|LCYAN|0:0|3:1|
''current job listing''
}}

{{Skill Box|LGRAY|7:0|7:0|
[[Miner]]s
}}

{{Skill Box|YELLOW|6:1|6:1|
[[Woodworker]]s
}}

| valign='top' |

{{Skill Box|WHITE|7:1|7:1|
[[Stoneworker]]s
}}

{{Skill Box|GREEN|2:0|2:0|
[[Ranger]]s
}}

{{Skill Box|DGRAY|0:1|0:1|
[[Metalsmith]]s
}}

{{Skill Box|LGREEN|2:1|2:1|
[[Jeweler]]s
}}

| valign='top' |

{{Skill Box|LBLUE|1:1|1:1|
[[Craftsdwarf]]s
}}

{{Skill Box|BLUE|1:0|1:0|
[[Fishery worker]]
}}

{{Skill Box|BROWN|6:0|6:0|
[[Farmer]]s
}}

{{Skill Box|LRED|4:1|4:1|
[[Engineer]]s
}}

| valign='top' |

{{Skill Box|MAGENTA|5:0|5:0|
[[Administrator]]s
}}

{{Skill Box|CYAN|3:0|3:0|
[[Peasant]]s
}}

{{Skill Box|RED|4:0|4:0|
[[Child]]ren
}}

{{Skill Box|LMAGENTA|0:0|5:1|
[[Monarch]]s,
''deceased''
}}
|}

Some other color uses:
* [[Magma]] is LRED. (Magma 1 level lower than current view is RED.)
* [[Water]] is LBLUE. (Water 1 level lower than current view is BLUE.)
* [[Brook]]s are LCYAN on their surface (with water below).
* For aesthetic purposes, almost all colours can be represented in stones (with the exception of LMAGENTA, CYAN, and BLACK).
** BLACK: The background color, which should not be used by anything.
** DGRAY: A wide variety of stones are DGRAY, one example being [[gabbro]].
** BLUE: [[Kimberlite]] is the only stone that is BLUE. [[Nether-cap]]s also produce BLUE wood.
** LBLUE: [[Cobaltite]] is the only stone that is LBLUE.
** GREEN: [[Olivine]] is GREEN, as are malachite and [[serpentine]].
** LGREEN: [[Garnierite]] is the only LGREEN stone.
** CYAN: While there are no stones, [[spore tree]]s are CYAN.
** LCYAN: [[Microcline]] is an LCYAN rock. [[Adamantine]] and its ore, [[raw adamantine]], also display in LCYAN.
** RED: [[Bauxite]] and [[kaolinite]] are RED, as is the [[blood thorn]] tree.
** LRED: [[Realgar]], [[petrified wood]], and [[cinnabar]] are LRED. [[Goblin-cap]]s are also LRED.
** MAGENTA: [[Rutile]] and [[pitchblende]] are MAGENTA, and [[glumprong]]s are MAGENTA trees.
** LMAGENTA: No stones are LMAGENTA, but [[tunnel tube]]s are.
** BROWN: A lot of stones are BROWN; [[chert]] is one example.
** YELLOW: [[Brimstone]], [[gypsum]], [[orthoclase]] and many other stones are YELLOW, as is the [[fungiwood]] tree.
** LGRAY: Lots of stones are LGRAY, such as [[granite]].
** WHITE: Many stones are WHITE, such as [[limestone]], or [[rock salt]]. The [[tower-cap]] and [[feather tree]] both produce WHITE wood.

See [[color#By Color|color]] for a more complete list.

= Default Scheme =

The default ''Dwarf Fortress'' color scheme is based off the 16 standard HTML colors, as discussed [http://en.wikipedia.org/wiki/Web_colors#HTML_color_names here]. (Some have been renamed in DF, but the tones themselves are the same.)

These are broken up into 8 pairs, one darker, one lighter, as ordered below. When a color is flashing or a displayed tile is "dark/bright" according to the game display, these colors are the two that work "together" to create that contrast. Keep this in mind if creating a [[Color scheme#Custom color schemes|custom color scheme]], as described below. (See [[Color]] for a more complete discussion.)

If you lose the default scheme and neglected to make a backup ''(didn't we warn you to use "care and caution" when modding?)'', you can find the standard scheme below, without having to download DF again.

Open Dwarf Fortress/data/init/[[colors.txt]], and copy the text as seen below over the values found at the very bottom of the file. Save that file, restart ''Dwarf Fortress'', and you're set.

{{color scheme
|black=#000000
|dgray=#a0a0a0
|blue=#207df1
|lblue=#8c66ff
|green=#a2dc34
|lgreen=#13fd65
|cyan=#71bbb0
|lcyan=#12fecf
|red=#ff113a
|lred=#ff7111
|magenta=#a73cd5
|lmagenta=#e811ff
|brown=#d79b2d
|yellow=#ffe111
|lgray=#c0c0c0
|white=#ffffff
}}

= Custom color schemes =
{{mod}}

Players who are not satisfied with the default color scheme can alter things to suit their aesthetic tastes. In order for any scheme changes to take effect, the "colors.txt" file must be altered and saved. This file can be found in the data/init/ directory of your ''Dwarf Fortress'' installation. The changes will not take effect until after you close and restart ''Dwarf Fortress''.

The 16 colors are not fixed, except by their definitions in colors.txt. If you wanted to change YELLOW to something slightly brighter or darker, or more orange, or into deep purple, you can by changing the values listed under the label "YELLOW". Note that the color names are ''case sensitive'' - the color is "YELLOW", not "Yellow" or "yellow".

When designing a custom color, 3 "lights" of color are used: '''R'''ed, '''G'''reen, and '''B'''lue (RGB), on a scale of 0-255. The more light (the higher the value), the brighter the color; the less light (the lower the value), the darker. Using "light" is not the same as using "pigment" ''(the standard "paint mixing" formulae we learned in school, where Magenta, Yellow, and Cyan are the 3 basic ingredients)'' - M+C does not give "blue" in this format.

Since we're using Red, Green and Blue light, some form of those three colors is relatively easy to achieve - but look at examples of the other standard colors below to understand how they mix together and how to "shade" or "tint", or brighten or darken a color - or you can simply find a color below that you like and go from that, or use one of these [[Color#Color_tokens|standard RGB colors]]. Always use caution to avoid ending up with colors that are "too similar".

To change to a new color scheme, copy/paste a color list (or part of one or more) found below (or make your own up) over the existing scheme - don't worry, if you don't like it, the original, default scheme is listed above.

''(Note also that when posting screenshots to this wiki (and the forum boards), custom color schemes (or [[tilesets]]) can cause confusion with players who do not use those specific mixes. This wiki requests you use one of the default set-ups that come with the game to post screenshots here.)''

----

=== Pre-v50 Default Scheme ===
The old default color scheme from earlier versions of Dwarf Fortress, for those who prefer it.

{{color scheme
|black=#000000
|dgray=#808080
|blue=#000080
|lblue=#0000ff
|green=#008000
|lgreen=#00ff00
|cyan=#008080
|lcyan=#00ffff
|red=#800000
|lred=#ff0000
|magenta=#800080
|lmagenta=#ff00ff
|brown=#808000
|yellow=#ffff00
|lgray=#c0c0c0
|white=#ffffff
}}

----

=== Lee's Colour scheme ===
A quest to provide the optimal set of colours: all colours very easily distinguishable and earthy/natural without being washed out or too bright and garish.

{{color scheme
|black=#000000
|dgray=#646464
|blue=#1E55A5
|lblue=#5A82D2
|green=#467D37
|lgreen=#6EB437
|cyan=#2D9187
|lcyan=#46D7C3
|red=#AA1400
|lred=#D73C00
|magenta=#822873
|lmagenta=#D255BE
|brown=#785032
|yellow=#EBB400
|lgray=#A0A0A0
|white=#FAFAFA
}}

====Lee's Colour Scheme v2====
New and Improved! All colours have been altered slightly but most notably the brown is much better, the magentas are more of a grape/bubblegum mix, the greens are brighter and less depressing, and the whole thing feels more cohesive.

{{color scheme
|black=#15130F
|dgray=#746E71
|blue=#2D5AA0
|lblue=#6987E1
|green=#508714
|lgreen=#7DB937
|cyan=#198C8C
|lcyan=#3CCDBE
|red=#A0140A
|lred=#DC3214
|magenta=#873C82
|lmagenta=#BE6EB9
|brown=#964B37
|yellow=#E6AA1E
|lgray=#B2AFAC
|white=#E8E3E8
}}

----

=== "Natural" scheme ===

This mix softens the glaring colors of the original to earthtones.

{{color scheme
|black=#000000
|dgray=#585356
|blue=#0d67c4
|lblue=#91caff
|green=#449e35
|lgreen=#83d452
|cyan=#56a3cd
|lcyan=#b0dfd7
|red=#971a1a
|lred=#ff2222
|magenta=#ff6ebb
|lmagenta=#ffa7f6
|brown=#785e2f
|yellow=#ffda5a
|lgray=#b9c0a2
|white=#ffffff
}}

----

=== True Brown ===

Default scheme with BROWN actually being a shade of brown (rather than Olive Green). Created by [[User:Met|Met]].

{{color scheme
|black=#000000
|dgray=#505050
|blue=#000080
|lblue=#0000ff
|green=#008000
|lgreen=#00ff00
|cyan=#008080
|lcyan=#00ffff
|red=#800000
|lred=#ff0000
|magenta=#800080
|lmagenta=#ff00ff
|brown=#785e30
|yellow=#ffff00
|lgray=#c0c0c0
|white=#ffffff
}}

----

=== Another natural scheme ===

{{color scheme
|black=#000000
|dgray=#505050
|blue=#495f9d
|lblue=#6f8aa5
|green=#597537
|lgreen=#a0c852
|cyan=#65909e
|lcyan=#9fc4d2
|red=#920000
|lred=#ce4901
|magenta=#a53665
|lmagenta=#ef96cf
|brown=#8a693b
|yellow=#ffc600
|lgray=#808080
|white=#ffffff
}}

----

=== Higher-visibility scheme ===

Tired of trying to see your metalsmiths (dark grey) and fishery workers (navy blue) against a black background? This scheme "brightens" most of the colors, while trying to stay true to the original tone when possible. (Except BROWN, which is now actually "brown", not olive green.)

{{color scheme
|black=#000000|blackt=*
|dgray=#787878
|blue=#2c88de
|lblue=#90caff
|green=#209020
|lgreen=#42e828
|cyan=#008080|cyant=*
|lcyan=#80e0d8
|red=#b00808
|lred=#ff0000|lredt=*
|magenta=#b038a0
|lmagenta=#ff54ff
|brown=#785e30
|yellow=#ffec30
|lgray=#b0b0b0
|white=#ffffff|whitet=*
}}
:''(* unchanged'')

Original on the left, this scheme on the right...

{| style="margin: 0 auto"
|-
| valign='top' |

{{Skill Box|DGRAY|#888|#888|
[[Metalsmith]]s
}}

{{Skill Box|GREEN|#080|#080|
[[Ranger]]s
}}

{{Skill Box|BLUE|rgb(00, 00, 80)|rgb(00, 00, 80)|
[[Fishery worker]]
}}

{{Skill Box|LBLUE|#00f|#00f|
[[Craftsdwarf]]s
}}

{{Skill Box|BROWN|#880|#880|
[[Farmer]]s
}}

{{Skill Box|MAGENTA|#808|#808|
[[Administrator]]s
}}

{{Skill Box|RED|#800|#800|
[[Child]]ren
}}

| valign='top' |

{{Skill Box|DGRAY|rgb(176, 176, 176)|rgb(176, 176, 176)|
[[Metalsmith]]s
}}

{{Skill Box|GREEN|rgb(32, 144, 32)|rgb(32, 144, 32)|
[[Ranger]]s
}}

{{Skill Box|BLUE|rgb(44, 136, 222)|rgb(44, 136, 222)|
[[Fishery worker]]
}}

{{Skill Box|LBLUE|rgb(144, 202, 255)|rgb(144, 202, 255)|
[[Craftsdwarf]]s
}}

{{Skill Box|BROWN|rgb(120, 94, 48)|rgb(120, 94, 48)|
[[Farmer]]s
}}

{{Skill Box|MAGENTA|rgb(176, 56, 160)|rgb(176, 56, 160)|
[[Administrator]]s
}}

{{Skill Box|RED|rgb(176, 8, 8)|rgb(176, 8, 8)|
[[Child]]ren
}}
|}

----

=== (Yet) Another scheme ===

{{color scheme
|black=#000000
|dgray=#707070
|blue=#203090
|lblue=#2838ff
|green=#309020
|lgreen=#30f020
|cyan=#208090
|lcyan=#38d0ff
|red=#971a1a
|lred=#ff3020
|magenta=#702090
|lmagenta=#d038ff
|brown=#907030
|yellow=#ffe020
|lgray=#b0b0b0
|white=#ffffff
}}

----

=== True CGA Scheme ===

This scheme uses the genuine [http://en.wikipedia.org/wiki/Color_Graphics_Adapter CGA] palette, in case you're an old-school purist.

''(Note that the CGA "brown" can be difficult to distinguish from "red" unless it is immediately nearby. For a slightly more readable version, you can "cheat" and replace the'' [BROWN_G:85]
''with ''[BROWN_G:170]. '')''

{{color scheme
|black=#000000
|dgray=#555555
|blue=#0000aa
|lblue=#5555ff
|green=#00aa00
|lgreen=#55ff55
|cyan=#00aaaa
|lcyan=#55ffff
|red=#aa0000
|lred=#ff5555
|magenta=#aa00aa
|lmagenta=#ff55ff
|brown=#aa5500
|yellow=#ffff55
|lgray=#aaaaaa
|white=#ffffff
}}

----

=== For the Chromatically Challenged ===

Colour blindness can result in colours being too similar, such as red and brown, so this scheme sacrifices true colour accuracy for a greater difference in hues. If you have normal colour vision, then this probably looks really weird.

{{color scheme
|black=#000000
|dgray=#808080
|blue=#0000C0
|lblue=#3030FF
|green=#008000
|lgreen=#00D000
|cyan=#007090
|lcyan=#40D0FF
|red=#C00000
|lred=#FF3030
|magenta=#A00080
|lmagenta=#FF40D0
|brown=#606000
|yellow=#FFFF40
|lgray=#C0C0C0
|white=#FFFFFF
}}

----

=== Red/Green Colorblindness ===

A modification of the chromatically challenged color scheme above, made to the tastes of someone with Red/Green colorblindness.

{{color scheme
|black=#000000
|dgray=#707070
|blue=#0000F0
|lblue=#5050FF
|green=#008000
|lgreen=#00D000
|cyan=#007090
|lcyan=#40D0FF
|red=#F00000
|lred=#FF5050
|magenta=#A00080
|lmagenta=#FF30F0
|brown=#806000
|yellow=#FFFF40
|lgray=#D0D0D0
|white=#FFFFFF
}}

----

=== Tango Scheme ===

Color scheme to match [http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines Tango palette]. Cyan values were missing from palette, so blue/plum values are used instead.

{{color scheme
|black=#2E3436
|dgray=#888a85
|blue=#204a87
|lblue=#3465a4
|green=#4e9a06
|lgreen=#8ae234
|cyan=#75507b
|lcyan=#729fcf
|red=#a40000
|lred=#ef2929
|magenta=#5c3566
|lmagenta=#ad7fa8
|brown=#ce5c00
|yellow=#fce94f
|lgray=#babdb6
|white=#eeeeec
}}

----

=== AngleWyrm's Colorset ===
Blues greens and brown that are easy on the eyes.

{{color scheme
|black=#000
|dgray=#484848
|blue=#303c78
|lblue=#5064b4
|green=#1e6428
|lgreen=#289632
|cyan=#285a82
|lcyan=#729fcf
|red=#a40000
|lred=#ef2929
|magenta=#5c3566
|lmagenta=#ad7fa8
|brown=#785032
|yellow=#b4aa3c
|lgray=#808080
|white=#eeeeec
}}

----

=== Putnam's Fortbent Color Scheme ===

A color scheme designed for closest accuracy to Homestuck's colors; no accuracy to actual in-game colors guaranteed.

{{color scheme
|black=#000000
|dgray=#626262
|dgrayt=(Caliborn gray tumut)
|blue=#000056
|bluet=(Equius B100)
|lblue=#005682
|lbluet=(Vriska Cerulean!!!!!!!!)
|green=#416600
|greent=(:33 < *nepeta green*)
|lgreen=#00FF00
|lgreent=(Calliope's blood)
|cyan=#008282
|cyant=(T3R3Z1 T34L)
|lcyan=#00FFFF
|red=#a10000
|redt=(aradia red)
|lred=#FF0000
|magenta=#6a006a
|magentat=(eridan vviolet)
|lmagenta=#77003c
|lmagentat=(meenah purple)
|brown=#a15000
|brownt=(uHH, tAVROS BROWN)
|yellow=#a1a100
|yellowt=(yucky mu2tard yellow)
|lgray=#929292
|lgrayt=(Calliope gray!)
|white=#FFFFFF
}}

----

=== nocpur's Color Scheme ===
A soft, earth-toned color scheme. Used by nocpur in screenshots of the fortress [http://www.bay12forums.com/smf/index.php?topic=180198 Striketrampled].

{{color scheme
|black=#15130F
|dgray=#746E71
|blue=#2B86A1
|lblue=#3FA4B8
|green=#5B8722
|lgreen=#A5B91F
|cyan=#1A996A
|lcyan=#22D4A5
|red=#A01838
|lred=#C91E35
|magenta=#872B72
|lmagenta=#BE6EB9
|brown=#965A1E
|yellow=#DEA035
|lgray=#B2AFAC
|white=#FFFDFC
}}

----

=== Vherid's Color Schemes ===

====Default +====
{{color scheme
|black=#000000
|dgray=#505050
|blue=#1233af
|lblue=#0072ff
|green=#008000
|lgreen=#00ff00
|cyan=#00b2b2
|lcyan=#00ffff
|red=#6b0000
|lred=#ff0000
|magenta=#800080
|lmagenta=#d100ac
|brown=#765e00
|yellow=#ffff00
|lgray=#c0c0c0
|white=#ffffff
}}

====Natural====
{{color scheme
|black=#1b1209
|dgray=#464132
|blue=#203296
|lblue=#0078ff
|green=#1e6428
|lgreen=#aaff00
|cyan=#107873
|lcyan=#1bd2cd
|red=#6e1414
|lred=#c02424
|magenta=#8511ab
|lmagenta=#e647aa
|brown=#64402a
|yellow=#fab40a
|lgray=#746c54
|white=#dcdcdc
}}

====Warm====
{{color scheme
|black=#1b1209
|dgray=#3e352c
|blue=#1a41a5
|lblue=#006cff
|green=#6e7b15
|lgreen=#c4db26
|cyan=#007860
|lcyan=#00ffcc
|red=#521900
|lred=#c03d24
|magenta=#4c0037
|lmagenta=#ff208d
|brown=#623d26
|yellow=#ffbf00
|lgray=#9a846d
|white=#ffedda
}}

====Bone====
{{color scheme
|black=#26170a
|dgray=#41352b
|blue=#0f52ba
|lblue=#008aff
|green=#788617
|lgreen=#c4db26
|cyan=#56b872
|lcyan=#48ffb8
|red=#840000
|lred=#c03d24
|magenta=#7c1a60
|lmagenta=#ff4282
|brown=#684b3a
|yellow=#ffc322
|lgray=#9a846d
|white=#fcfad0
}}

====Mishka====
{{color scheme
|black=#170f0d
|dgray=#4a342e
|blue=#005fff
|lblue=#00b3ff
|green=#57a000
|lgreen=#c0d600
|cyan=#00875f
|lcyan=#00ffb4
|red=#ba5300
|lred=#ea8400
|magenta=#a72400
|lmagenta=#ff4310
|brown=#b08951
|yellow=#e4b31b
|lgray=#79644b
|white=#f1e3b8
}}

====Dusk====
{{color scheme
|black=#0a0a0a
|dgray=#30262d
|blue=#04518c
|lblue=#00b0ee
|green=#5d6d06
|lgreen=#a6b000
|cyan=#0c4f4c
|lcyan=#0cbba0
|red=#8e2800
|lred=#ce4901
|magenta=#830034
|lmagenta=#a00307
|brown=#eb8800
|yellow=#ffb74d
|lgray=#806d63
|white=#f2f7e6
}}

====Sorrow====
{{color scheme
|black=#050011
|dgray=#392a20
|blue=#2e495e
|lblue=#4c889e
|green=#55532a
|lgreen=#afb54b
|cyan=#437d42
|lcyan=#79bd8f
|red=#8e2800
|lred=#b64926
|magenta=#7b2636
|lmagenta=#a15642
|brown=#816535
|yellow=#cb9a45
|lgray=#878e5d
|white=#fff782
}}

====Jade====
{{color scheme
|black=#110b09
|dgray=#2a1e1b
|blue=#2e495e
|lblue=#4c889e
|green=#6c6b25
|lgreen=#c3c13d
|cyan=#5c633a
|lcyan=#70a16c
|red=#762a1b
|lred=#af652f
|magenta=#ae2c3b
|lmagenta=#ab421e
|brown=#725539
|yellow=#cb9a45
|lgray=#453c31
|white=#dbd69c
}}

====Dark Sand====
{{color scheme
|black=#020110
|dgray=#112334
|blue=#04518c
|lblue=#00b0ee
|green=#5d6d06
|lgreen=#a6b000
|cyan=#0c4f4c
|lcyan=#0cbba0
|red=#8e2800
|lred=#ce4901
|magenta=#830034
|lmagenta=#a00307
|brown=#72593a
|yellow=#ffb74d
|lgray=#334555
|white=#e6f5f7
}}

====Matrix====
{{color scheme
|black=#192007
|dgray=#383a26
|blue=#18774f
|lblue=#0dbd75
|green=#4d7218
|lgreen=#88be12
|cyan=#b38700
|lcyan=#ffcc00
|red=#76440b
|lred=#b96706
|magenta=#204631
|lmagenta=#527f39
|brown=#4d5407
|yellow=#b9da1c
|lgray=#6b6f4b
|white=#d7e894
}}

====Ash====
{{color scheme
|black=#000000
|dgray=#343434
|blue=#494949
|lblue=#818181
|green=#676767
|lgreen=#dbdbdb
|cyan=#a5a5a5
|lcyan=#f7f7f7
|red=#252525
|lred=#505050
|magenta=#555555
|lmagenta=#777778
|brown=#3c3c3c
|yellow=#b6b6b6
|lgray=#8e8e8e
|white=#ffffff
}}

====Fields====
{{color scheme
|black=#0c0811
|dgray=#342d28
|blue=#27445c
|lblue=#2facc7
|green=#6b6819
|lgreen=#bebc27
|cyan=#3e7466
|lcyan=#9ddc85
|red=#5c2514
|lred=#af3b14
|magenta=#621805
|lmagenta=#a42405
|brown=#8d550b
|yellow=#e0a403
|lgray=#4f433a
|white=#ebdec6
}}

====Heat====
{{color scheme
|black=#170a0a
|dgray=#47341b
|blue=#394b45
|lblue=#42b0b6
|green=#7d6f10
|lgreen=#c7c01a
|cyan=#517a4e
|lcyan=#aade6c
|red=#6e2c0c
|lred=#ba420c
|magenta=#741e03
|lmagenta=#b02a03
|brown=#9c5c07
|yellow=#e4a801
|lgray=#624a28
|white=#eee0b5
}}

====Lazer====
{{color scheme
|black=#090900
|dgray=#292701
|blue=#003321
|lblue=#287035
|green=#886d23
|lgreen=#efc140
|cyan=#088313
|lcyan=#23ca37
|red=#62200b
|lred=#af3b14
|magenta=#4a0d02
|lmagenta=#a52102
|brown=#844e06
|yellow=#e9ab03
|lgray=#384023
|white=#ccef73
}}

====Mud====
{{color scheme
|black=#201e15
|dgray=#323723
|blue=#234353
|lblue=#30798f
|green=#777136
|lgreen=#ada45e
|cyan=#445415
|lcyan=#768b20
|red=#89360e
|lred=#bc4a13
|magenta=#846722
|lmagenta=#cca036
|brown=#5c4f28
|yellow=#fba612
|lgray=#4e5537
|white=#fffce3
}}

====Fallen====
{{color scheme
|black=#201e15
|dgray=#323723
|blue=#234353
|lblue=#30798f
|green=#777136
|lgreen=#efc140
|cyan=#3f522b
|lcyan=#737d26
|red=#6a2713
|lred=#b24c15
|magenta=#681708
|lmagenta=#b52a0b
|brown=#5c4f28
|yellow=#fba612
|lgray=#4e5537
|white=#f4ffd0
}}

----
=== Koumakan's Color Schemes ===

KMK Systems color schemes can be found at http://www.bay12forums.com/smf/index.php?topic=169671.0.

====Soyuz====
"The colorscheme shown is my Soyuz colorscheme I made for one of Taffer's more experimental variants of his tileset, check his stuff out if you haven't, it's easily one of the best ASCII sets for DF."
{{color scheme
|black=#281100
|dgray=#4A3226
|blue=#2E495E
|lblue=#4C889E
|green=#333100
|lgreen=#56571B
|cyan=#527F39
|lcyan=#A3B934
|red=#7C0000
|lred=#DB2700
|magenta=#776A36
|lmagenta=#EFC140
|brown=#7C5434
|yellow=#FF9A0A
|lgray=#B98764
|white=#FFF0AD
}}

====Bonsai====
"These colors are based off of Cyprinodon's work that you can see [http://www.bay12forums.com/smf/index.php?topic=150763.0 HERE]
I really liked his color scheme at the time and made a handful of tweaks years ago to try some things out while still keeping the original BG color."
{{color scheme
|black=#2E0018
|dgray=#443025
|blue=#0443B7
|lblue=#0099F0
|green=#076F29
|lgreen=#27EC48
|cyan=#1D9661
|lcyan=#2AFF98
|red=#710000
|lred=#D32800
|magenta=#80234E
|lmagenta=#E559A5
|brown=#724E2F
|yellow=#FFA200
|lgray=#B07F5A
|white=#FFEFA0
}}

====Gordon====

{{color scheme
|black=#150F0A
|dgray=#32230F
|blue=#193A91
|lblue=#2595CF
|green=#334B0E
|lgreen=#88C922
|cyan=#08C49F
|lcyan=#7FE8B5
|red=#550F0A
|lred=#EF3A0C
|magenta=#562E73
|lmagenta=#A03A9E
|brown=#624C01
|yellow=#FFA200
|lgray=#684C3C
|white=#EFD8A1
}}

----

===Monokai===
{{color scheme
|black=#000
|dgray=#555
|blue=#7accda
|lblue=#66d9f9
|green=#9dc54b
|lgreen=#a6e22e
|cyan=#00d9d9
|lcyan=#c8f0f0
|red=#d34278
|lred=#f92672
|magenta=#ae81ff
|lmagenta=#b392ef
|brown=#d1ca89
|yellow=#e6db74
|lgray=#f5deb3
|white=#fff
}}

----

===Qud===

A color scheme based on the game [https://www.cavesofqud.com/ Caves of Qud]. Original by Corporal_Klinger on the DF forums, modified for visibility by Mabelmabel on the CoQ discord.

{{color scheme
|black=#0F3B3A
|dgray=#51797A
|blue=#0048BD
|lblue=#0096FF
|green=#009403
|lgreen=#009403
|cyan=#40A4B9
|lcyan=#77BFCF
|red=#A64A2E
|lred=#D74200
|magenta=#B154CF
|lmagenta=#DA5BD6
|brown=#98875F
|yellow=#CFC041
|lgray=#B1C9C3
|white=#fff
}}

----

===Solarized===

Based on [http://ethanschoonover.com/solarized Ethan Schoonover's syntax highlighting color scheme]. Designed to be easily distinguishable and visible colors that also reduce eye strain and fatigue.

{{color scheme
|black=#002b36
|dgray=#586e75
|blue=#268bd2
|lblue=#7baee6
|green=#859900
|lgreen=#adcb67
|cyan=#2aa198
|lcyan=#7fd7ca
|red=#dc322f
|lred=#f76a6a
|magenta=#d33682
|lmagenta=#f186aa
|brown=#b58a00
|yellow=#ecc853
|lgray=#93a1a1
|white=#fdf6e3
}}

----

===elementary===
{{color scheme
|black=#303030
|dgray=#5d5d5d
|blue=#004f9e
|lblue=#0071ff
|green=#6ab017
|lgreen=#7bc91f
|cyan=#2aa7e7
|lcyan=#4bb8fd
|red=#e1321a
|lred=#ff361e
|magenta=#ec0048
|lmagenta=#ff1d62
|brown=#ffc005
|yellow=#ffd00a
|lgray=#999
|white=#f2f2f2
}}

=== Pseudo Naturalistic Color Scheme ===

Natural colours based on classic colours. Designed for [http://www.bay12forums.com/smf/index.php?topic=53180.4710 Ironhand tileset and DF2014 (see discussion)] but looks nice with ASCII too. Created by [[User:Harmonica|Harmonica]].

This particularly works well with Ironhand due to the colour blending (nice minerals and plants), and also works nicely with the new trees.

{{color scheme
|black=#000000
|dgray=#808080
|blue=#3636ab
|lblue=#628aea
|green=#3daf3d
|lgreen=#70de70
|cyan=#3aafc3
|lcyan=#00ffff
|red=#ab2929
|lred=#f3714b
|magenta=#ab33ab
|lmagenta=#e691e6
|brown=#795c38
|yellow=#e6e600
|lgray=#c0c0c0
|white=#FFFFFF
}}

----

=== CowThing's color schemes ===

This color scheme is for a softer, happier game. Colors were chosen for easy visibility and to be easy on the eyes.
{{color scheme
|black=#31313e
|dgray=#767681
|blue=#4051da
|lblue=#6295ed
|green=#56b636
|lgreen=#aff239
|cyan=#52b7c0
|lcyan=#acebd9
|red=#ce3137
|lred=#f8503e
|magenta=#8e3aba
|lmagenta=#dd62c5
|brown=#f0a22a
|yellow=#fcef62
|lgray=#afb5b7
|white=#ffffff
}}

A darker version of the above color scheme.
{{color scheme
|black=#1f1d26
|dgray=#544f53
|blue=#334ca0
|lblue=#4b99d5
|green=#398f29
|lgreen=#79d733
|cyan=#49948a
|lcyan=#94daaf
|red=#9e2c24
|lred=#d64d2c
|magenta=#6f2a71
|lmagenta=#c3498c
|brown=#bd7e24
|yellow=#ebc942
|lgray=#84827c
|white=#f5f0da
}}

== Snackfox's color scheme ==

This color scheme was designed to be light, pretty, and easy on the eyes, with an emphasis on purples and blues.
{{color scheme
|black=#453c57
|dgray=#9e8db0
|blue=#7062d6
|lblue=#a499fa
|green=#238a64
|lgreen=#17eda6
|cyan=#0099ff
|lcyan=#00ffff
|red=#b300b0
|lred=#ff21a6
|magenta=#d92eff
|lmagenta=#ff8abf
|brown=#b57438
|yellow=#fff652
|lgray=#cecef5
|white=#fffbc8
}}

----

== Runeset Mapmaker ==

This color scheme was designed to work with Runeset to produce beautiful sepia toned fantasy maps.
{{color scheme
|black=#A59B78
|dgray=#48453C
|blue=#2D91DC
|lblue=#8796B9
|green=#2D6E32
|lgreen=#82A569
|cyan=#788C96
|lcyan=#AAC0CD
|red=#640505
|lred=#911E23
|magenta=#642369
|lmagenta=#8C14A0
|brown=#73694B
|yellow=#C6C482
|lgray=#C8C8B4
|white=#FFFFFF
}}

== Runeset ==

A more playable version of Runeset Mapmaker that doesn't make every embark site look like the desert. It's a milder toned scheme with decent contrast.
{{color scheme
|black=#000000
|dgray=#48453C
|blue=#2D91DC
|lblue=#8796B9
|green=#2D6E32
|lgreen=#82A569
|cyan=#788C96
|lcyan=#AAC0CD
|red=#640505
|lred=#911E23
|magenta=#642369
|lmagenta=#8C14A0
|brown=#5F4628
|yellow=#B4B473
|lgray=#A0A0A0
|white=#FFFFFF
}}

----

== Kyzer's Themes ==

=== Kyzer's Light Scheme ===
A light color scheme meant to be easy on the eyes using yellows and relatively low contrast colors. '''Note: cyan is now purple!'''
{{color scheme
|black=#D3C89C
|dgray=#474747
|blue=#C4E6F2
|lblue=#6590F4
|green=#1C851E
|lgreen=#0EB500
|cyan=#683D91
|lcyan=#BD89FA
|red=#AD3636
|lred=#E66060
|magenta=#C95EAC
|lmagenta=#733663
|brown=#A66624
|yellow=#9F9A17
|lgray=#737373
|white=#141414
}}

=== Kyzer's 'true color' Scheme ===
A high brightness color scheme with a lot of contrast, base colors (RED and BLUE, for example) are the most saturated and brightest they can be. Light colors are actually light versions of the previous colors now.
{{color scheme
|black=#000000
|dgray=#595959
|blue=#0000FF
|lblue=#7D89FF
|green=#00FF00
|lgreen=#89FF7D
|cyan=#00FFFF
|lcyan=#9EFDFF
|red=#FF0000
|lred=#FF8787
|magenta=#FF00FF
|lmagenta=#FE8CFF
|brown=#FFA33B
|yellow=#FFFF85
|lgray=#BABABA
|white=#FFFFF
}}

=== Kyzer's Low Contrast Scheme ===
A low contrast, dark theme which prevents your eyes from having issues focusing because of overly bright tones. Basically, it has the same effect of turning your monitor down, without turning it down.
{{color scheme
|black=#000000
|dgray=#292929
|blue=#00285C
|lblue=#004399
|green=#005200
|lgreen=#007A00
|cyan=#005252
|lcyan=#008585
|red=#4F0000
|lred=#7D0000
|magenta=#400063
|lmagenta=#540082
|brown=#733300
|yellow=#877F00
|lgray=#595959
|white=#828282
}}

== Zippy's Themes ==
=== Zippy's Vibrant ===
Colors here are designed to be much softer, richer and brighter than the game's default colors. Most colors are very slightly dimmed as to appear less over saturated than the original color scheme, but still manage to show as unique and vibrant colors.

{{color scheme
|black=#111111
|dgray=#a1a1a1
|blue=#406fec
|lblue=#43c6f7
|green=#539f47
|lgreen=#5fe34d
|cyan=#4fc0d9
|lcyan=#81edef
|red=#b81d1d
|lred=#f13636
|magenta=#cb4096
|lmagenta=#f97ad9
|brown=#ab7611
|yellow=#ffcc00
|lgray=#a19d9a
|white=#fffaf5
}}

=== Zippy's Low Contrast ===
An alternate color scheme where the colors - as the title would denote - have less contrast, as all the colors are much closer to their counterparts. This color scheme may be hard to see on a darker monitor.

{{color scheme
|black=#111111
|dgray=#a1a1a1
|blue=#3a65d7
|lblue=#33D4DF
|green=#39912B
|lgreen=#B2FFA7
|cyan=#4BC8B6
|lcyan=#66FFFA
|red=#d03a17
|lred=#FF8C8C
|magenta=#A821A0
|lmagenta=#FFA6C8
|brown=#B34109
|yellow=#FFBE7D
|lgray=#a19d9a
|white=#ffffff
}}

----

== DPh Kraken's Themes ==

===Minecraft Wool===
Uses the exact hex codes of each wool dye color from Minecraft.

{{color scheme
|black=#1D1D21
|dgray=#474F52
|blue=#8932B8
|lblue=#3C44AA
|green=#5E7C16
|lgreen=#80C71F
|cyan=#169C9C
|lcyan=#3AB3DA
|red=#B02E26
|lred=#F9801D
|magenta=#C74EBD
|lmagenta=#F38BAA
|brown=#835432
|yellow=#FED83D
|lgray=#9D9D97
|white=#F9FFFE
}}

===Minecraft Map===
Another Minecraft-themed set, this uses a selection of tile colors as they appear on Java Edition maps.

{{color scheme
|black=#191919
|dgray=#707070
|blue=#2C2CB2
|lblue=#4040FF
|green=#007C00
|lgreen=#7FB238
|cyan=#7070B4
|lcyan=#A0A0FF
|red=#B40000
|lred=#DC0000
|magenta=#7D3598
|lmagenta=#B24CD8
|brown=#8F7748
|yellow=#F7E9A3
|lgray=#A7A7A7
|white=#FFFFFF
}}

===Painterly===
Uses dye colors from the Painterly texture pack for Minecraft. Dark and saturated.

{{color scheme
|black=#0B0B0B
|dgray=#434343
|blue=#65008F
|lblue=#003DA5
|green=#003C00
|lgreen=#73913A
|cyan=#2A89F4
|lcyan=#47F0E9
|red=#8A0000
|lred=#E77B00
|magenta=#C20089
|lmagenta=#F6959B
|brown=#56390B
|yellow=#F3D233
|lgray=#A8A8A8
|white=#FFFFFF
}}

===Minty===
Based on the default dark mode (Mint-Y-Dark) terminal colors for Linux Mint.

{{color scheme
|black=#2E3435
|dgray=#535756
|blue=#34659F
|lblue=#729FD2
|green=#4E980D
|lgreen=#8AE340
|cyan=#069696
|lcyan=#39E2DE
|red=#CD0001
|lred=#F02727
|magenta=#725179
|lmagenta=#AC7FA5
|brown=#C4A106
|yellow=#FEEA57
|lgray=#A4A5A2
|white=#EDEEE9
}}

== Spaceman00's Themes ==
=== Matrix 1 ===
Pallete inspired by matrix movie screen colors. 
Only, green, light green, blue, light blue, white and black are different as they are the only colors present at the screen.

{{color scheme
|black=#0E0E0E
|dgray=#808080
|blue=#384B89
|lblue=#6588BC
|green=#8EC58C
|lgreen=#B2D8A7
|cyan=#008080
|lcyan=#00FFFF
|red=#800000
|lred=#FF0000
|magenta=#800080
|lmagenta=#FF00FF
|brown=#808000
|yellow=#FFFF00
|lgray=#C0C0C0
|white=#E4E4E2
}}

=== Matrix 2===
Pallete inspired by matrix movie screen colors. 
Only, green, light green, blue, light blue, white and black are from the movie, other colors are decided following some pattern related to original DF pallete pattern.

{{color scheme
|black=#0E0E0E
|dgray=#797978
|blue=#384B89
|lblue=#6588BC
|green=#8EC58C
|lgreen=#B2D8A7
|cyan=#3A7365
|lcyan=#65D8BC
|red=#4E1422
|lred=#8D1A36
|magenta=#27142C
|lmagenta=#401A49
|brown=#4E3C21
|yellow=#8D6A34
|lgray=#AFAFAD
|white=#E4E4E2
}}

=== Matrix 3===
Pallete inspired by matrix movie screen colors. 
Only, green, light green, blue, light blue, white and black are from the movie, other colors are decided following some pattern related to original DF pallete pattern. 
This one assumes, R, G or B, are actually not N but N^2.2.

{{color scheme
|black=#0E0E0E
|dgray=#A7A7A5
|blue=#384B89
|lblue=#6588BC
|green=#8EC58C
|lgreen=#B2D8A7
|cyan=#4A9EA7
|lcyan=#65D8BC
|red=#993F77
|lred=#D255A3
|magenta=#713F77
|lmagenta=#9A55A3
|brown=#998C77
|yellow=#D2C0A3
|lgray=#C8C8C6
|white=#E4E4E2
}}

=== Matrix 4===
Pallete inspired by matrix movie screen colors. 
Only, green, light green, blue, light blue, white and black are from the movie, other colors are decided following some pattern related to original DF pallete pattern. 
This one assumes, R, G or B, are actually not N but N^2.2. It also assumes DF dark colors values are not the mid point between DF white and DF light version of the color but take into account N^2.2 too.

{{color scheme
|black=#0E0E0E
|dgray=#737372
|blue=#384B89
|lblue=#6588BC
|green=#8EC58C
|lgreen=#B2D8A7
|cyan=#346D5F
|lcyan=#65D8BC
|red=#6A2C52
|lred=#D255A3
|magenta=#4E2C52
|lmagenta=#9A55A3
|brown=#6A6152
|yellow=#D2C0A3
|lgray=#ACACAA
|white=#E4E4E2
}}

==Avenskol==
An assortment of combinations fitting various themes and settings.

===Aizalvaran===

{{color scheme
|black=#000000
|dgray=#968386
|blue=#850038
|lblue=#B2004B
|green=#997C99
|lgreen=#C8A2C8
|cyan=#A83D5D
|lcyan=#E75480
|red=#662244
|lred=#993366
|magenta=#BA8C94
|lmagenta=#FFC0CB
|brown=#5E3E47
|yellow=#915F6D
|lgray=#C4ABAE
|white=#FADADD
}}

===Ashilesian===

{{color scheme
|black=#000000
|dgray=#5F7A5F
|blue=#21633E
|lblue=#2E8B57
|green=#719625
|lgreen=#9ACD32
|cyan=#77C777
|lcyan=#98FF98
|red=#525200
|lred=#808000
|magenta=#3A4722
|lmagenta=#556832
|brown=#80BD23
|yellow=#ADFF2F
|lgray=#85AB85
|white=#ADDFAD
}}

===Azkuvalian===

{{color scheme
|black=#000000
|dgray=#7C7C9C
|blue=#C4949C
|lblue=#FFC0CB
|green=#877C31
|lgreen=#B5A642
|cyan=#C2A9AB
|lcyan=#FADADD
|red=#B55A3F
|lred=#E97451
|magenta=#AB3E5F
|lmagenta=#E75480
|brown=#8A6F5C
|yellow=#BC987E
|lgray=#A5A5CF
|white=#CCCCFF
}}

===Dasdarfoxan===

{{color scheme
|black=#000000
|dgray=#3D2F22
|blue=#4A2311
|lblue=#6F351A
|green=#5C5233
|lgreen=#918151
|cyan=#572017
|lcyan=#8A3324
|red=#472500
|lred=#7B3F00
|magenta=#63453F
|lmagenta=#986960
|brown=#59430E
|yellow=#967117
|lgray=#6B533B
|white=#987654
}}

===Doratorian===

{{color scheme
|black=#000000
|dgray=#8A7C61
|blue=#358550
|lblue=#50C878
|green=#719625
|lgreen=#9ACD32
|cyan=#00C261
|lcyan=#00FF7F
|red=#BAA300
|lred=#FFDF00
|magenta=#5C5233
|lmagenta=#918151
|brown=#918560
|yellow=#C2B280
|lgray=#C7B38C
|white=#FFE5B4
}}

===Eilasalian===

{{color scheme
|black=#000000
|dgray=#5A5A70
|blue=#0054A8
|lblue=#007FFF
|green=#006B44
|lgreen=#00A86B
|cyan=#454F59
|lcyan=#708090
|red=#78505A
|lred=#CC8899
|magenta=#856B85
|lmagenta=#C8A2C8
|brown=#50A600
|yellow=#7BFF00
|lgray=#8F8FB3
|white=#CCCCFF
}}

===Eilsavian===

{{color scheme
|black=#000000
|dgray=#262B30
|blue=#1B0036
|lblue=#310062
|green=#2A3319
|lgreen=#556832
|cyan=#330059
|lcyan=#4B0082
|red=#4F4F00
|lred=#808000
|magenta=#38252F
|lmagenta=#614051
|brown=#304A28
|yellow=#4F7942
|lgray=#454F59
|white=#708090
}}

===Eiltaresian===

{{color scheme
|black=#000000
|dgray=#658A8A
|blue=#62A362
|lblue=#98FF98
|green=#246B42
|lgreen=#2E8B57
|cyan=#87AD87
|lcyan=#ADDFAD
|red=#2C004D
|lred=#4B0082
|magenta=#1C0038
|lmagenta=#310062
|brown=#6D9123
|yellow=#9ACD32
|lgray=#85B5B5
|white=#AFEEEE
}}

===Einfieran===

{{color scheme
|black=#000000
|dgray=#695353
|blue=#5E3D3D
|lblue=#905D5D
|green=#52353D
|lgreen=#915F6D
|cyan=#964444
|lcyan=#CD5C5C
|red=#A32F25
|lred=#E34234
|magenta=#593A43
|lmagenta=#915F75
|brown=#732600
|yellow=#C04000
|lgray=#B08C8C
|white=#F4C2C2
}}

===Octusarian===

{{color scheme
|black=#000000
|dgray=#7B408C
|blue=#270030
|lblue=#5C0262
|green=#2E004F
|lgreen=#4B0082
|cyan=#43215C
|lcyan=#673189
|red=#420042
|lred=#660066
|magenta=#6C00C7
|lmagenta=#8B00FF
|brown=#452D39
|yellow=#614051
|lgray=#AC59C4
|white=#DF73FF
}}

===Pakacit's Shade===

{{color scheme
|black=#000000
|dgray=#3B3B3B
|blue=#4C4B66
|lblue=#6C6799
|green=#4A664F
|lgreen=#6B9968
|cyan=#4A6663
|lcyan=#6A9899
|red=#664545
|lred=#996E6E
|magenta=#664262
|lmagenta=#996A92
|brown=#646645
|yellow=#969968
|lgray=#666666
|white=#999999
}}

===Pakacit's Shine===

{{color scheme
|black=#000000
|dgray=#666666
|blue=#737199
|lblue=#9790D4
|green=#6B9970
|lgreen=#96D490
|cyan=#709995
|lcyan=#92D3D4
|red=#996A6A
|lred=#D49797
|magenta=#996396
|lmagenta=#D494C8
|brown=#93996D
|yellow=#CED490
|lgray=#999999
|white=#D4D4D4
}}

===Syrenalian===

{{color scheme
|black=#000000
|dgray=#968A51
|blue=#00BDBD
|lblue=#00FFFF
|green=#89C925
|lgreen=#ADFF2F
|cyan=#5BB899
|lcyan=#7FFFD4
|red=#A87F19
|lred=#DAA520
|magenta=#6D4991
|lmagenta=#9966CC
|brown=#B89324
|yellow=#F4C430
|lgray=#C2B269
|white=#F0DC82
}}

{{Category|Interface}}
[[ru:Color scheme]]

Settings

2026-03-28T21:26:37Z

Ziusudra: /* Keyboard scroll amounts */ added key template, fast with shift

{{av}}
{{Quality|Fine}}
Settings for ''Dwarf Fortress'' can be accessed with a button on the main menu, which can be accessed in-game with {{Menu icon|Esc}}. They are divided into six groups; Video, Audio, Game, Keybindings, Announcements, and Difficulty. They are stored in several different files, including [[init.txt]], [[d_init.txt]], and [[interface.txt]], with current values in the <code>prefs\</code> folder and default values in the <code>data\init\</code> folder. The default files in <code>data\init\</code> include explanations of each setting, including possible values. The files in both <code>data\init\</code> and <code>prefs\</code> are read when ''Dwarf Fortress'' starts, in that order, with the last value read for each option being used. The location of the <code>prefs\</code> folder depends on various factors, see [[Game folders and files]].

== Video ==
These settings change how the game looks and are all stored in <code>prefs\init.txt</code> and defaults in <code>data\init\init_default.txt</code>.
* '''Windowed or Fullscreen''' - the highlighted button is the active one and they correspond with [WINDOWED:YES] or [WINDOWED:NO] in the files. [WINDOWED:PROMPT] can be set in the files to make the game ask when starting up, in which case neither button will be highlighted.
* '''Resolution''' - the screen mode the game uses when in fullscreen mode, 'Detect' corresponds with [FULLSCREENX:0] and [FULLSCREENY:0] in the files.
* '''Scale interface''' - whether to scale the font used to draw interface elements such as the menus and minimap to a specific number of character cells, [INTERFACE_SCALING_TO_DESIRED_GRID:YES] in the files.
* '''Desired grid width and height''' - how much to scale the interface, in how many character cells wide and tall the interface should be. [INTERFACE_SCALING_DESIRED_GRID_WIDTH:170] and [INTERFACE_SCALING_DESIRED_GRID_HEIGHT:64] in the files. No effect if [INTERFACE_SCALING_TO_DESIRED_GRID:NO] is used.
* '''Interface scale percentage''' - percentage to scale the interface character cell size up when not scaling to specified grid counts, not every value makes a difference since the interface won't display a partial character at the edges. [INTERFACE_SCALING_PERCENTAGE:100] in the files, no effect if [INTERFACE_SCALING_TO_DESIRED_GRID:YES] is used.
* '''Initial window size''' - when not fullscreen, [WINDOWEDX:1200] and [WINDOWEDY:800] in the files.
* '''Window resizable''' - when not fullscreen, [RESIZABLE:YES] in the files.
* '''Maximum interface width''' - what percentage of the display the overlay interface elements can occupy, useful for extra wide displays to make notifications more visible. [MAXIMUM_INTERFACE_PERCENTAGE:100] in the files. The game will still use the entire window/screen and the minimap and elevation bar will stay at the edge.
* '''Graphical FPS cap''' - how many frames to cap the graphical display rate at. [G_FPS_CAP:50] in the files.
* '''Classic ASCII''' - [USE_CLASSIC_ASCII:NO] in the files.
* '''Scaling mode''' - NEAREST, nearest-neighbor, distorts shapes at some zoom levels; LANCZOS, less distortion but fuzzier at some zoom levels; AUTO, the default, will try to select whichever one is more appropriate depending on the zoom level. [TEXTURE_PARAM:AUTO] in the files.

As the interface gets narrower, some elements will be removed from the [[status]] bar when there's not enough room for all of them; some menus may also display elements under other elements or outside their window.

There are a few other file settings that can affect the display, see [[Technical_tricks#Settings_-_init.txt|technical tricks]].

== Audio ==
These settings change how the game plays sounds and are all stored in <code>prefs\init.txt</code> with defaults in <code>data\init\init_default.txt</code>. All volumes can be from 0 to 255 in the game files, with 255 being 100%.
* '''Master Volume''' - [MASTER_VOLUME:255] in the files.
* '''Music Volume (Fortress)''' - [MUSIC_VOLUME:255] in the files.
* '''Ambience Volume (Fortress)''' - [AMBIENCE_VOLUME:230] in the files.
* '''Sound Effects Volume (Fortress)''' - [SFX_VOLUME:204] in the files.
* '''Average Seconds Between Tracks/Interludes (Fortress)''' - [AVERAGE_TIME_BETWEEN_SONGS:240] in the files. The default of 240 gives a range of 180 to 300 seconds, which is 3 to 5 minutes. Can be anywhere from 10 to 600.
* '''Music Volume (Adventure)'''{{v|51.01}} - [MUSIC_VOLUME_ADV:217] in the files.
* '''Ambience Volume (Adventure)'''{{v|51.01}} - [AMBIENCE_VOLUME_ADV:240] in the files.
* '''Sound Effects Volume (Adventure)'''{{v|51.01}} - [SFX_VOLUME_ADV:230] in the files.

The classic version of the game available on the website only includes the original songs, so most of these will have no effect without the [[premium version]] or mods.

All sound can be disabled completely with [SOUND:NO] in the files. If so, the rest of these settings will be replaced by text explaining that sound is disabled and how to enable it.

== Game ==
These settings change how the game plays and most are stored in <code>prefs\d_init.txt</code> with defaults in <code>data\init\d_init_default.txt</code>, but some are in <code>prefs\init.txt</code> with defaults in <code>data\init\init_default.txt</code>.

=== Portable mode ===
* '''Portable mode'''{{v|52.01}} - when set to NO, the game stores mods, preferences, and saves in a folder specific to the user, (see [[game folders and files]] for details) when set to YES, it stores them in the game folder. Changing this to YES creates the empty file <code>prefs\portable.txt</code>, changing back to NO removes it; manually creating or removing the file changes the setting.

=== Autosaves ===
{{for/see|more information about autosaves|[[Saved_game_folder#Save_folder_format|Saved game folder]]}}
* '''Autosave frequency''' - when to autosave, [AUTOSAVE:SEMIANNUAL] in d_init.txt, NONE, SEASONAL, SEMIANNUALLY, or YEARLY.
* '''Autosave at embark''' - [INITIAL_SAVE:NO] in d_init.txt, YES or NO. Additionally to inital saving the game: If set to YES (and the game is paused in the beginning) then the game is paused (and saved) before a dwarf gets assigned to fishing duty (if water to fish in is available), otherwise (meaning this option is set to NO), if there is water, a dwarf is assigned to fishing duty (even if the game is paused in the beginning).

=== Pausing ===
* '''Pause after autosave''' - [AUTOSAVE_PAUSE:NO] in d_init.txt, YES or NO.
* '''Pause after loading''' - [PAUSE_ON_LOAD:YES] in d_init.txt, YES or NO.

=== Embark ===
* '''Always confirm embark''' - asks for confirmation of the embark location even if there are no warnings such as for [[aquifer]]s, dangerous [[surroundings]], etc, [EMBARK_WARNING_ALWAYS:NO] in d_init.txt, YES or NO.
* '''Confirm preparations''' - [POST_PREPARE_EMBARK_CONFIRMATION:IF_POINTS_REMAIN] in d_init.txt, ALWAYS, IF_POINTS_REMAIN, or NO.
* '''Show tunnels when embarking''' - for dwarven [[tunnel]]s, shown as a black dashed line or grey double line with classic ASCII, [SHOW_EMBARK_TUNNEL:FINDER] in d_init.txt, FINDER, ALWAYS, or NO.{{verify|is there a difference between ALWAYS and FINDER now?}} More restrictive world generation settings will override these.
* '''Default embark width and height''' - also determines what is considered a normal embark size and will only warn when the actual embark is larger than this many (width × height) tiles, [EMBARK_RECTANGLE:4:4] in d_init.txt, 2 to 16. See Maximum embark dimension below. (This option is actually listed after the feature toggles on the tab in game.)
* '''Maximum embark dimension''' - maximum width or height for an embark, larger sizes may be buggy and need much more memory, [MAXIMUM_EMBARK_DIM:6] in d_init.txt, 6 to 16. (This option is actually listed in game near the bottom of the tab, before the dye and scroll options.)

=== Feature toggles ===
* '''Enable temperature''' - If temperature calculations are off, only a few direct temperature changes will take place. For example, magma will set tiles and creatures to high temperatures, but those tiles will never cool and those creatures will not catch fire. Effects that rely on temperature calculations, such as water freezing, melting, or evaporating, or creatures and items taking temperature-related damage, will not occur. May affect FPS in unusual circumstances, [TEMPERATURE:YES] in d_init.txt, YES or NO.
* '''Enable weather''' - toggles rain and snow, rarely affects FPS, [WEATHER:YES] in d_init.txt, YES or NO.{{verify|does this affect wind or evil weather?}}
* '''Enable caveins''' - toggles [[cave-ins]], [CAVEINS:YES] in d_init.txt, YES or NO.
* '''Enable artifact moods''' - toggles [[strange mood]]s and the resulting [[artifact]]s, [ARTIFACTS:YES] in d_init.txt, YES or NO.{{verify|does this affect world gen artifacts?}}
* '''Enable testing arena''' - [TESTING_ARENA:YES] in d_init.txt, YES or NO.
* '''Walking spreads spatter (fort mode)''' - toggle the spread of blood spatter and other [[contaminant]]s by creatures on ground tiles in fortress mode. As spatter can infinitely spread, it is recommended to leave this as "NO". [WALKING_SPREADS_SPATTER_DWF:NO] in d_init.txt, YES or NO.
* '''Walking spreads spatter (adv mode)'''{{v|51.01}} - toggle the spread of blood spatter and other [[contaminant]]s by creatures on ground tiles in adventure mode. As spatter can help with tracking creatures, it is recommended to leave this as "YES". [WALKING_SPREADS_SPATTER_ADV:NO] in d_init.txt, YES or NO.
* '''Enable keyboard cursor''' - allows for using the keyboard controls for some designations, [KEYBOARD_CURSOR:NO] in d_init.txt, YES or NO. Arrow keys {{k|↑←↓→}} move one tile, {{k|WASD}} 10 tiles, and {{k|Shift|WASD|sep=+}} 20 tiles; also see [[Settings#Keyboard_scroll_amounts|Keyboard scroll amounts]] section below.
* '''Log world rejects''' - logs the reasons worlds were rejected in ``[[map_rejection_log.txt]]``, useful in [[advanced world generation]] and [[modding]], [LOG_MAP_REJECTS:NO] in d_init.txt, YES or NO. ''Dwarf Fortress'' will keep adding to the file, so you may want to trim or delete it occasionally.
* '''Multithreading''' - limited experimental multithreading, [MULTITHREADING:NO] in d_init.txt.
* '''Classic varied ground tiles'''{{v|51.05}} - if changed to NO, ground tiles will be displayed only with periods in ASCII mode, [CLASSIC_VARIED_GROUND_TILES:YES] in d_init.txt. (This option is actually listed in game near the bottom of the tab, before the scroll options.)
* '''Show rectangle dimensions'''{{v|51.06}} - if changed to NO, hides the size display when drawing selection retangles, [SHOW_RECTANGLE_DIMENSIONS:YES] in d_init.txt. (This option is actually listed in game near the bottom of the tab, before the scroll options.)

=== Pathing costs ===
* '''Path costs''' - extreme changes to these may cause more lag, [PATH_COST:1:2:5:25] in d_init.txt, 1 to 1000.
* '''Storage path cost decreases''' - controls how aggressively dwarves place objects in a container with like items (rather than an empty container). The default combine options are very aggressive. All in d_init.txt, 2 to 1000.
** [STORE_DIST_ITEM_DECREASE:20] - for each object found in a container, one tile is removed from its apparent distance to the dwarf, up to this cap
** [STORE_DIST_SEED_COMBINE:1000] - a bag with seeds already in it will appear this many tiles closer
** [STORE_DIST_BUCKET_COMBINE:1000] - a bucket with the same liquid already in it will appear this many tiles closer
** [STORE_DIST_BARREL_COMBINE:1000] - a barrel with the same item type already in it will appear this many tiles closer
** [STORE_DIST_BIN_COMBINE:1000] - a bin with the same item type already in it will appear this many tiles closer

=== Population and seed capacities ===
* '''Population caps''' - can be changed at will to limit migration, strict also prevents births, [POPULATION_CAP:200] and [STRICT_POPULATION_CAP:220] in d_init.txt, 0 to 5000. Certain game features are triggered by population number, see [[difficulty]]. Some of those features may also cause the actual population to slightly go over these.
* '''Children limits''' - how many and what percentage of total there can be at a time, [BABY_CHILD_CAP:100:1000] in d_init.txt, 0 to 1000. Only prevents further pregnancies, so migrant children, multiple births and existing pregnancies from old saves can still push you over the cap. Setting either number to zero will disallow new pregnancies in the fortress.
* '''Visitor cap''' - This does not include merchants, diplomats, animals or invaders, but only those dropping by for a temporary visit to a tavern, library or temple, or those seeking permanent employment. Once you accept a petition from a visitor to stay at your fort, they no longer count against the cap, even if they never become a full citizen. [VISITOR_CAP:100] in d_init.txt, 0 to 5000.
* '''Dead units cull''' - During a season changeover, the game checks if there's a certain number of units in play. If it is above this amount, it removes all the unimportant dead units who died at least two years ago. [CULL_DEAD_UNITS_AT:1000] in d_init.txt, 100 to 5000.
* '''Seed caps''' - per type and total, when over the total cap, seeds will be periodically removed, starting with the oldest and most worthless. [SPECIFIC_SEED_CAP:200] 0 to 10000 and [FORTRESS_SEED_CAP:3000] 0 to 30000 in d_init.txt.

=== Information display ===
* '''Engraving display''' - [ENGRAVINGS_START_OBSCURED:NO] in d_init.txt, YES or NO.
* '''Improvement quality display''' - [SHOW_IMP_QUALITY:YES] in d_init.txt, YES or NO.
* '''Numeric liquid levels''' - can be toggled in game either with a button next to the minimap or a keybind {{menu icon|f}}, [SHOW_FLOW_AMOUNTS:NO] in d_init.txt, YES or NO.
* '''Ramp arrows''' - can be toggled in game either with a button next to the minimap or a keybind {{menu icon|r}}, [SHOW_RAMP_ARROWS:NO] in d_init.txt, YES or NO.
* '''Elevation layers display''' - [NUMBER_OF_LOWER_ELEVATIONS_SHOWN:8] in d_init.txt, 0 to 8.
* '''Engraving historical events''' - [SHOW_ALL_HISTORY_IN_DWARF_MODE:YES] in d_init.txt, YES or NO.
* '''Nickname display''' - [NICKNAME_DWARF:REPLACE_FIRST], [NICKNAME_ADVENTURE:REPLACE_FIRST], [NICKNAME_LEGENDS:REPLACE_FIRST] in d_init.txt, REPLACE_FIRST, CENTRALIZE (between first and last), or REPLACE_ALL.

=== Grazing coefficient ===
* '''Grazing coefficient''' - how much grazers get from grazing, larger numbers mean less food is needed. [GRAZE_COEFFICIENT:100] in d_init.txt, 1 to 1000000.

=== FPS ===
* '''Show FPS''' - the first number is simulation rate, the number in parentheses is graphical FPS, [FPS:NO] in init.txt, YES or NO.
* '''Game FPS cap''' - limits how quickly the game runs the simulation, [FPS_CAP:100] in init.txt, 5 to 1000. This cap can also be temporarily changed on the fly by ~10% with {{k|Alt|Equals|sep=+}} and {{k|Alt|Minus|sep=+}}; if '''Show FPS''' is set to yes, then pressing either of those will briefly show what the cap has been changed to.

=== Input timings ===
* '''Key hold time''' - [KEY_HOLD_MS:250] in init.txt, 100 to 20000.
* '''Key repeat time''' - [KEY_REPEAT_MS:150] in init.txt, 100 to 20000.
* '''Key repeat acceleration''' - [KEY_REPEAT_ACCEL_START:10] 1 to 1000 and [KEY_REPEAT_ACCEL_LIMIT:8] 2 to 100 in init.txt.
* '''Interface shutdown time''' - how long after a view recenter to ignore input, [RECENTER_INTERFACE_SHUTDOWN_MS:0] in init.txt, 0 to 2000.
* '''Macro timing''' - [MACRO_MS:15] in init.txt, 1 to 2000.

=== Compressed saves ===
* '''Compressed saves''' - saves drive space (since running out of space while saving '''will''' corrupt the save) at the expense of slowing down save operations, [COMPRESSED_SAVES:YES] in init.txt, YES or NO.

=== Dye display ===
* '''Display worn clothing dyes (fort mode)'''{{v|50.15}} - if set to the default NO, color will be determined by [[profession]], mostly only useful in ASCII mode, [DISPLAY_CLOTHING_WITH_DYES_IN_FORT_MODE:NO] in d_init.txt, YES or NO.
* '''Display worn clothing dyes (adv mode)'''{{v|51.01}} - if changed to NO, color will be determined by profession, [DISPLAY_CLOTHING_WITH_DYES_IN_ADV_MODE:YES] in d_init.txt, YES or NO.

=== Keyboard scroll amounts ===
* '''Keyboard scroll tiles'''{{v|51.11}} - how many tiles to scroll with the "Move view/cursor" keys (default {{k|WASD}}, the FAST settings are used for {{k|Shift|WASD|sep=+}}) in the normal and world views, as well as the [[Settings#Feature_toggles|keyboard cursor]], though for that, the cursor keys {{k|↑←↓→}} also always move 1 tile, in addition to these values for the "Move view/cursor" keys. 1 to 100, and the following tokens in d_init.txt
**[HORIZONTAL_SCROLL_SPEED:10]
**[HORIZONTAL_SCROLL_SPEED_FAST:20]
**[VERTICAL_SCROLL_SPEED:10]
**[VERTICAL_SCROLL_SPEED_FAST:20]
**[HORIZONTAL_SCROLL_SPEED_WORLD:10]
**[HORIZONTAL_SCROLL_SPEED_WORLD_FAST:20]
**[VERTICAL_SCROLL_SPEED_WORLD:10]
**[VERTICAL_SCROLL_SPEED_WORLD_FAST:20]

== Keybindings ==
{{main|Controls}}{{main|interface.txt}}
These settings change the controls and are all stored in interface.txt.

== Announcements ==
{{main|Announcement}}{{main|announcements.txt}}
Used to control how different announcements are displayed in Dwarf Fortress. This can be useful to add alerts for critical combat events, stopping the recentering on birth events, or reducing the constant chatter of announcements like 'quota filled' or 'someone is visiting'.

== Difficulty ==
{{main|Difficulty}}
This tab is only available when in a fortress game, and these settings are initially set when starting a fortress game. Since they are specific to each save they are stored as part of the save and are not editable outside the game. They are divided into two groups: enemies and economy; enemies can be disabled, both groups have normal and hard presets, and all of the individual settings can be adjusted in '''Custom settings'''. The values used in each preset can be seen by selecting the preset and then viewing them in '''Custom settings'''.

[[ru:Settings]]

Settings

2026-03-28T10:17:48Z

Ziusudra: /* Feature toggles */ added key seperator

{{av}}
{{Quality|Fine}}
Settings for ''Dwarf Fortress'' can be accessed with a button on the main menu, which can be accessed in-game with {{Menu icon|Esc}}. They are divided into six groups; Video, Audio, Game, Keybindings, Announcements, and Difficulty. They are stored in several different files, including [[init.txt]], [[d_init.txt]], and [[interface.txt]], with current values in the <code>prefs\</code> folder and default values in the <code>data\init\</code> folder. The default files in <code>data\init\</code> include explanations of each setting, including possible values. The files in both <code>data\init\</code> and <code>prefs\</code> are read when ''Dwarf Fortress'' starts, in that order, with the last value read for each option being used. The location of the <code>prefs\</code> folder depends on various factors, see [[Game folders and files]].

== Video ==
These settings change how the game looks and are all stored in <code>prefs\init.txt</code> and defaults in <code>data\init\init_default.txt</code>.
* '''Windowed or Fullscreen''' - the highlighted button is the active one and they correspond with [WINDOWED:YES] or [WINDOWED:NO] in the files. [WINDOWED:PROMPT] can be set in the files to make the game ask when starting up, in which case neither button will be highlighted.
* '''Resolution''' - the screen mode the game uses when in fullscreen mode, 'Detect' corresponds with [FULLSCREENX:0] and [FULLSCREENY:0] in the files.
* '''Scale interface''' - whether to scale the font used to draw interface elements such as the menus and minimap to a specific number of character cells, [INTERFACE_SCALING_TO_DESIRED_GRID:YES] in the files.
* '''Desired grid width and height''' - how much to scale the interface, in how many character cells wide and tall the interface should be. [INTERFACE_SCALING_DESIRED_GRID_WIDTH:170] and [INTERFACE_SCALING_DESIRED_GRID_HEIGHT:64] in the files. No effect if [INTERFACE_SCALING_TO_DESIRED_GRID:NO] is used.
* '''Interface scale percentage''' - percentage to scale the interface character cell size up when not scaling to specified grid counts, not every value makes a difference since the interface won't display a partial character at the edges. [INTERFACE_SCALING_PERCENTAGE:100] in the files, no effect if [INTERFACE_SCALING_TO_DESIRED_GRID:YES] is used.
* '''Initial window size''' - when not fullscreen, [WINDOWEDX:1200] and [WINDOWEDY:800] in the files.
* '''Window resizable''' - when not fullscreen, [RESIZABLE:YES] in the files.
* '''Maximum interface width''' - what percentage of the display the overlay interface elements can occupy, useful for extra wide displays to make notifications more visible. [MAXIMUM_INTERFACE_PERCENTAGE:100] in the files. The game will still use the entire window/screen and the minimap and elevation bar will stay at the edge.
* '''Graphical FPS cap''' - how many frames to cap the graphical display rate at. [G_FPS_CAP:50] in the files.
* '''Classic ASCII''' - [USE_CLASSIC_ASCII:NO] in the files.
* '''Scaling mode''' - NEAREST, nearest-neighbor, distorts shapes at some zoom levels; LANCZOS, less distortion but fuzzier at some zoom levels; AUTO, the default, will try to select whichever one is more appropriate depending on the zoom level. [TEXTURE_PARAM:AUTO] in the files.

As the interface gets narrower, some elements will be removed from the [[status]] bar when there's not enough room for all of them; some menus may also display elements under other elements or outside their window.

There are a few other file settings that can affect the display, see [[Technical_tricks#Settings_-_init.txt|technical tricks]].

== Audio ==
These settings change how the game plays sounds and are all stored in <code>prefs\init.txt</code> with defaults in <code>data\init\init_default.txt</code>. All volumes can be from 0 to 255 in the game files, with 255 being 100%.
* '''Master Volume''' - [MASTER_VOLUME:255] in the files.
* '''Music Volume (Fortress)''' - [MUSIC_VOLUME:255] in the files.
* '''Ambience Volume (Fortress)''' - [AMBIENCE_VOLUME:230] in the files.
* '''Sound Effects Volume (Fortress)''' - [SFX_VOLUME:204] in the files.
* '''Average Seconds Between Tracks/Interludes (Fortress)''' - [AVERAGE_TIME_BETWEEN_SONGS:240] in the files. The default of 240 gives a range of 180 to 300 seconds, which is 3 to 5 minutes. Can be anywhere from 10 to 600.
* '''Music Volume (Adventure)'''{{v|51.01}} - [MUSIC_VOLUME_ADV:217] in the files.
* '''Ambience Volume (Adventure)'''{{v|51.01}} - [AMBIENCE_VOLUME_ADV:240] in the files.
* '''Sound Effects Volume (Adventure)'''{{v|51.01}} - [SFX_VOLUME_ADV:230] in the files.

The classic version of the game available on the website only includes the original songs, so most of these will have no effect without the [[premium version]] or mods.

All sound can be disabled completely with [SOUND:NO] in the files. If so, the rest of these settings will be replaced by text explaining that sound is disabled and how to enable it.

== Game ==
These settings change how the game plays and most are stored in <code>prefs\d_init.txt</code> with defaults in <code>data\init\d_init_default.txt</code>, but some are in <code>prefs\init.txt</code> with defaults in <code>data\init\init_default.txt</code>.

=== Portable mode ===
* '''Portable mode'''{{v|52.01}} - when set to NO, the game stores mods, preferences, and saves in a folder specific to the user, (see [[game folders and files]] for details) when set to YES, it stores them in the game folder. Changing this to YES creates the empty file <code>prefs\portable.txt</code>, changing back to NO removes it; manually creating or removing the file changes the setting.

=== Autosaves ===
{{for/see|more information about autosaves|[[Saved_game_folder#Save_folder_format|Saved game folder]]}}
* '''Autosave frequency''' - when to autosave, [AUTOSAVE:SEMIANNUAL] in d_init.txt, NONE, SEASONAL, SEMIANNUALLY, or YEARLY.
* '''Autosave at embark''' - [INITIAL_SAVE:NO] in d_init.txt, YES or NO. Additionally to inital saving the game: If set to YES (and the game is paused in the beginning) then the game is paused (and saved) before a dwarf gets assigned to fishing duty (if water to fish in is available), otherwise (meaning this option is set to NO), if there is water, a dwarf is assigned to fishing duty (even if the game is paused in the beginning).

=== Pausing ===
* '''Pause after autosave''' - [AUTOSAVE_PAUSE:NO] in d_init.txt, YES or NO.
* '''Pause after loading''' - [PAUSE_ON_LOAD:YES] in d_init.txt, YES or NO.

=== Embark ===
* '''Always confirm embark''' - asks for confirmation of the embark location even if there are no warnings such as for [[aquifer]]s, dangerous [[surroundings]], etc, [EMBARK_WARNING_ALWAYS:NO] in d_init.txt, YES or NO.
* '''Confirm preparations''' - [POST_PREPARE_EMBARK_CONFIRMATION:IF_POINTS_REMAIN] in d_init.txt, ALWAYS, IF_POINTS_REMAIN, or NO.
* '''Show tunnels when embarking''' - for dwarven [[tunnel]]s, shown as a black dashed line or grey double line with classic ASCII, [SHOW_EMBARK_TUNNEL:FINDER] in d_init.txt, FINDER, ALWAYS, or NO.{{verify|is there a difference between ALWAYS and FINDER now?}} More restrictive world generation settings will override these.
* '''Default embark width and height''' - also determines what is considered a normal embark size and will only warn when the actual embark is larger than this many (width × height) tiles, [EMBARK_RECTANGLE:4:4] in d_init.txt, 2 to 16. See Maximum embark dimension below. (This option is actually listed after the feature toggles on the tab in game.)
* '''Maximum embark dimension''' - maximum width or height for an embark, larger sizes may be buggy and need much more memory, [MAXIMUM_EMBARK_DIM:6] in d_init.txt, 6 to 16. (This option is actually listed in game near the bottom of the tab, before the dye and scroll options.)

=== Feature toggles ===
* '''Enable temperature''' - If temperature calculations are off, only a few direct temperature changes will take place. For example, magma will set tiles and creatures to high temperatures, but those tiles will never cool and those creatures will not catch fire. Effects that rely on temperature calculations, such as water freezing, melting, or evaporating, or creatures and items taking temperature-related damage, will not occur. May affect FPS in unusual circumstances, [TEMPERATURE:YES] in d_init.txt, YES or NO.
* '''Enable weather''' - toggles rain and snow, rarely affects FPS, [WEATHER:YES] in d_init.txt, YES or NO.{{verify|does this affect wind or evil weather?}}
* '''Enable caveins''' - toggles [[cave-ins]], [CAVEINS:YES] in d_init.txt, YES or NO.
* '''Enable artifact moods''' - toggles [[strange mood]]s and the resulting [[artifact]]s, [ARTIFACTS:YES] in d_init.txt, YES or NO.{{verify|does this affect world gen artifacts?}}
* '''Enable testing arena''' - [TESTING_ARENA:YES] in d_init.txt, YES or NO.
* '''Walking spreads spatter (fort mode)''' - toggle the spread of blood spatter and other [[contaminant]]s by creatures on ground tiles in fortress mode. As spatter can infinitely spread, it is recommended to leave this as "NO". [WALKING_SPREADS_SPATTER_DWF:NO] in d_init.txt, YES or NO.
* '''Walking spreads spatter (adv mode)'''{{v|51.01}} - toggle the spread of blood spatter and other [[contaminant]]s by creatures on ground tiles in adventure mode. As spatter can help with tracking creatures, it is recommended to leave this as "YES". [WALKING_SPREADS_SPATTER_ADV:NO] in d_init.txt, YES or NO.
* '''Enable keyboard cursor''' - allows for using the keyboard controls for some designations, [KEYBOARD_CURSOR:NO] in d_init.txt, YES or NO. Arrow keys {{k|↑←↓→}} move one tile, {{k|WASD}} 10 tiles, and {{k|Shift|WASD|sep=+}} 20 tiles; also see [[Settings#Keyboard_scroll_amounts|Keyboard scroll amounts]] section below.
* '''Log world rejects''' - logs the reasons worlds were rejected in ``[[map_rejection_log.txt]]``, useful in [[advanced world generation]] and [[modding]], [LOG_MAP_REJECTS:NO] in d_init.txt, YES or NO. ''Dwarf Fortress'' will keep adding to the file, so you may want to trim or delete it occasionally.
* '''Multithreading''' - limited experimental multithreading, [MULTITHREADING:NO] in d_init.txt.
* '''Classic varied ground tiles'''{{v|51.05}} - if changed to NO, ground tiles will be displayed only with periods in ASCII mode, [CLASSIC_VARIED_GROUND_TILES:YES] in d_init.txt. (This option is actually listed in game near the bottom of the tab, before the scroll options.)
* '''Show rectangle dimensions'''{{v|51.06}} - if changed to NO, hides the size display when drawing selection retangles, [SHOW_RECTANGLE_DIMENSIONS:YES] in d_init.txt. (This option is actually listed in game near the bottom of the tab, before the scroll options.)

=== Pathing costs ===
* '''Path costs''' - extreme changes to these may cause more lag, [PATH_COST:1:2:5:25] in d_init.txt, 1 to 1000.
* '''Storage path cost decreases''' - controls how aggressively dwarves place objects in a container with like items (rather than an empty container). The default combine options are very aggressive. All in d_init.txt, 2 to 1000.
** [STORE_DIST_ITEM_DECREASE:20] - for each object found in a container, one tile is removed from its apparent distance to the dwarf, up to this cap
** [STORE_DIST_SEED_COMBINE:1000] - a bag with seeds already in it will appear this many tiles closer
** [STORE_DIST_BUCKET_COMBINE:1000] - a bucket with the same liquid already in it will appear this many tiles closer
** [STORE_DIST_BARREL_COMBINE:1000] - a barrel with the same item type already in it will appear this many tiles closer
** [STORE_DIST_BIN_COMBINE:1000] - a bin with the same item type already in it will appear this many tiles closer

=== Population and seed capacities ===
* '''Population caps''' - can be changed at will to limit migration, strict also prevents births, [POPULATION_CAP:200] and [STRICT_POPULATION_CAP:220] in d_init.txt, 0 to 5000. Certain game features are triggered by population number, see [[difficulty]]. Some of those features may also cause the actual population to slightly go over these.
* '''Children limits''' - how many and what percentage of total there can be at a time, [BABY_CHILD_CAP:100:1000] in d_init.txt, 0 to 1000. Only prevents further pregnancies, so migrant children, multiple births and existing pregnancies from old saves can still push you over the cap. Setting either number to zero will disallow new pregnancies in the fortress.
* '''Visitor cap''' - This does not include merchants, diplomats, animals or invaders, but only those dropping by for a temporary visit to a tavern, library or temple, or those seeking permanent employment. Once you accept a petition from a visitor to stay at your fort, they no longer count against the cap, even if they never become a full citizen. [VISITOR_CAP:100] in d_init.txt, 0 to 5000.
* '''Dead units cull''' - During a season changeover, the game checks if there's a certain number of units in play. If it is above this amount, it removes all the unimportant dead units who died at least two years ago. [CULL_DEAD_UNITS_AT:1000] in d_init.txt, 100 to 5000.
* '''Seed caps''' - per type and total, when over the total cap, seeds will be periodically removed, starting with the oldest and most worthless. [SPECIFIC_SEED_CAP:200] 0 to 10000 and [FORTRESS_SEED_CAP:3000] 0 to 30000 in d_init.txt.

=== Information display ===
* '''Engraving display''' - [ENGRAVINGS_START_OBSCURED:NO] in d_init.txt, YES or NO.
* '''Improvement quality display''' - [SHOW_IMP_QUALITY:YES] in d_init.txt, YES or NO.
* '''Numeric liquid levels''' - can be toggled in game either with a button next to the minimap or a keybind {{menu icon|f}}, [SHOW_FLOW_AMOUNTS:NO] in d_init.txt, YES or NO.
* '''Ramp arrows''' - can be toggled in game either with a button next to the minimap or a keybind {{menu icon|r}}, [SHOW_RAMP_ARROWS:NO] in d_init.txt, YES or NO.
* '''Elevation layers display''' - [NUMBER_OF_LOWER_ELEVATIONS_SHOWN:8] in d_init.txt, 0 to 8.
* '''Engraving historical events''' - [SHOW_ALL_HISTORY_IN_DWARF_MODE:YES] in d_init.txt, YES or NO.
* '''Nickname display''' - [NICKNAME_DWARF:REPLACE_FIRST], [NICKNAME_ADVENTURE:REPLACE_FIRST], [NICKNAME_LEGENDS:REPLACE_FIRST] in d_init.txt, REPLACE_FIRST, CENTRALIZE (between first and last), or REPLACE_ALL.

=== Grazing coefficient ===
* '''Grazing coefficient''' - how much grazers get from grazing, larger numbers mean less food is needed. [GRAZE_COEFFICIENT:100] in d_init.txt, 1 to 1000000.

=== FPS ===
* '''Show FPS''' - the first number is simulation rate, the number in parentheses is graphical FPS, [FPS:NO] in init.txt, YES or NO.
* '''Game FPS cap''' - limits how quickly the game runs the simulation, [FPS_CAP:100] in init.txt, 5 to 1000. This cap can also be temporarily changed on the fly by ~10% with {{k|Alt|Equals|sep=+}} and {{k|Alt|Minus|sep=+}}; if '''Show FPS''' is set to yes, then pressing either of those will briefly show what the cap has been changed to.

=== Input timings ===
* '''Key hold time''' - [KEY_HOLD_MS:250] in init.txt, 100 to 20000.
* '''Key repeat time''' - [KEY_REPEAT_MS:150] in init.txt, 100 to 20000.
* '''Key repeat acceleration''' - [KEY_REPEAT_ACCEL_START:10] 1 to 1000 and [KEY_REPEAT_ACCEL_LIMIT:8] 2 to 100 in init.txt.
* '''Interface shutdown time''' - how long after a view recenter to ignore input, [RECENTER_INTERFACE_SHUTDOWN_MS:0] in init.txt, 0 to 2000.
* '''Macro timing''' - [MACRO_MS:15] in init.txt, 1 to 2000.

=== Compressed saves ===
* '''Compressed saves''' - saves drive space (since running out of space while saving '''will''' corrupt the save) at the expense of slowing down save operations, [COMPRESSED_SAVES:YES] in init.txt, YES or NO.

=== Dye display ===
* '''Display worn clothing dyes (fort mode)'''{{v|50.15}} - if set to the default NO, color will be determined by [[profession]], mostly only useful in ASCII mode, [DISPLAY_CLOTHING_WITH_DYES_IN_FORT_MODE:NO] in d_init.txt, YES or NO.
* '''Display worn clothing dyes (adv mode)'''{{v|51.01}} - if changed to NO, color will be determined by profession, [DISPLAY_CLOTHING_WITH_DYES_IN_ADV_MODE:YES] in d_init.txt, YES or NO.

=== Keyboard scroll amounts ===
* '''Keyboard scroll tiles'''{{v|51.11}} - how many tiles to scroll with the "Move view/cursor" keys (default WASD) in the normal and world views, and also the [[Settings#Feature_toggles|keyboard cursor]], though for that, the cursor keys (↑←↓→) also always move 1 tile, in addition to the "Move view/cursor" keys. 1 to 100, and the following tokens in d_init.txt
**[HORIZONTAL_SCROLL_SPEED:10]
**[HORIZONTAL_SCROLL_SPEED_FAST:20]
**[VERTICAL_SCROLL_SPEED:10]
**[VERTICAL_SCROLL_SPEED_FAST:20]
**[HORIZONTAL_SCROLL_SPEED_WORLD:10]
**[HORIZONTAL_SCROLL_SPEED_WORLD_FAST:20]
**[VERTICAL_SCROLL_SPEED_WORLD:10]
**[VERTICAL_SCROLL_SPEED_WORLD_FAST:20]

== Keybindings ==
{{main|Controls}}{{main|interface.txt}}
These settings change the controls and are all stored in interface.txt.

== Announcements ==
{{main|Announcement}}{{main|announcements.txt}}
Used to control how different announcements are displayed in Dwarf Fortress. This can be useful to add alerts for critical combat events, stopping the recentering on birth events, or reducing the constant chatter of announcements like 'quota filled' or 'someone is visiting'.

== Difficulty ==
{{main|Difficulty}}
This tab is only available when in a fortress game, and these settings are initially set when starting a fortress game. Since they are specific to each save they are stored as part of the save and are not editable outside the game. They are divided into two groups: enemies and economy; enemies can be disabled, both groups have normal and hard presets, and all of the individual settings can be adjusted in '''Custom settings'''. The values used in each preset can be seen by selecting the preset and then viewing them in '''Custom settings'''.

[[ru:Settings]]

Royal jelly

2026-03-27T08:51:35Z

Ziusudra: /* Bugs */ added bug template for 4229

{{Quality|Fine}}
{{av}}
'''Royal jelly''' is a product of the [[beekeeping industry]] collected from an artificial bee [[hive]]. Royal jelly is stored in [[jug]]s, and can only be used as a [[liquid]] ingredient in [[prepared meal]]s. Due to a bug, dwarves may store royal jelly jugs as finished goods; combined with a [[cook]]'s aversion to liquid ingredients, it is very rare to see royal jelly cooked at all. That isn't necessarily a bad thing, though, since royal jelly is only available in single-unit stacks and has the same base value as most other foods.

The contents of a [[hive]] with a colony of [[honey bee]]s that is toggled to "gather any products" will be harvested as part of the [[beekeeping industry]]. In order to collect the royal jelly, you must have a dwarf with the [[beekeeper|beekeeping]] labor active and empty [[jug]]s. A [[honeycomb]] will also be produced.

Royal jelly and [[honey]] are the edible products of bees. In real life, it is used as a nutritional substance for larvae.

[[File:Bienenwabe mit Eiern und Brut 5 larva.png|thumb|310px|center|Nutrition for larvae.]]

==Bugs==
*Jugs of royal jelly may be stored in bins as finished goods, preventing its use in the food industry.{{Bug|4229}}
*Collecting royal jelly may require more than 1 jug in storage to begin.
*Cooks will only cook jelly and other fluids as a last resort, instead preferring to cook solid foods with solid foods.{{Bug|2393}} For more information, see the [[Kitchen#Bugs|kitchen]] page.

{{gamedata
|title=[[Honey bee/raw|Raws]]
|[USE_MATERIAL_TEMPLATE:ROYAL_JELLY:CREATURE_EXTRACT_TEMPLATE]
[STATE_NAME_ADJ:ALL_SOLID:frozen honey bee royal jelly]
[STATE_NAME_ADJ:LIQUID:honey bee royal jelly]
[STATE_NAME_ADJ:GAS:boiling honey bee royal jelly]
[STATE_COLOR:ALL:WHITE]
[DISPLAY_COLOR:7:0:1]
[PREFIX:NONE]
[EDIBLE_VERMIN]
[EDIBLE_COOKED]
[EDIBLE_RAW]
}}
{{materials}}

{{Category|Food}}
[[ru:Royal jelly]]

Release information/51.02

2026-03-25T22:32:40Z

Ziusudra: Undo revision 315606 by 107.175.37.112 (talk) spam

{{release notes}}

:It's finally time!

:Become the [[Chosen]] and go beyond your fortress in Dwarf Fortress [[Adventurer mode|Adventure Mode]]. Create a character in your simulated world and -- well, as a pure sandbox, what you do is up to you! To celebrate, we've made a brand new launch trailer [https://youtu.be/7zY0UxSxTzU which you can watch here:]

— Kitfox and Bay 12 Games, January 23, 2025
*[https://kitfoxgames.itch.io/dwarf-fortress/devlog/873366/adventure-mode-is-out-now Patch notes on Itch.io]
*[https://store.steampowered.com/news/app/975370/view/530962536730722479 Patch notes on Steam]

51.02 is the public release of Adventure mode, making the game mode available once more ever since it was [[Missing features|disabled]] in [[Release information/50.01|50.01]]. It features an updated [[interface]], overhauled [[Adventurer mode character creation]], and new mythical content.

==Adventure Mode highlights==
These notes summarize the changes made during the [[Release information/51.01|51.01 beta]].
*Go anywhere! Explore any civilization, earn a reputation, and recruit followers to join you
*Experience your fortress and the simulation in a new, more embodied way
*Explore [[Mysterious dungeon|mythical dungeons]] to find magical items, [[artifact]]s, and fill your [[quest]] journal
*Hints of mythology and [[magic]] as a start of future simulation enrichment to come
*An additional hour of music from Dabu and Simon Swerwer, presented as a second volume of the original [[soundtrack]]

==Patch notes==
===Broader non-Adventure Mode fixes===
*Can enter nicknames on embark screen
*Added tooltips for mode selection
*Fixed a world generation crash
*Fixed error causing invalid characters from being permitted in folder names

===Bugs/additions contained within Adventure Mode===
*Made hero mode select hearthperson by default
*Fixed crash from visiting certain [[forest retreat]]s
*Fixed some crashes related to local adventurer info not being set immediately after travel
*Fixed crash issue from demanding tribute from mythical sites
*Fixed a crash from unit sheets of certain creatures (e.g. roosters)
*Added more combat music
*Added sounds for items being put into containers
*Updates some confirm sounds
*Fixed some footstep sounds
*Fixed issue causing music to sound as if it's indoors
*Fixed some issues with ambient sound
*Added a keyboard-based look-and-interact cursor ('l')
*Stopped items like weapons and shields from starting in the same hand after character creation
*Stopped mythical sites from appearing on rivers (again)

Gremlin

2026-03-23T22:04:21Z

Ziusudra: added no clothing size info

{{Quality|Exceptional}}
{{Creaturelookup/0
|image=Gremlin sprites.png
|portrait=Gremlin portrait.png
|wiki=yes
}}
{{av}}
{{creaturedesc}}
'''Gremlins''' are intelligent [[cavern]] [[creature]]s who are invisible until spotted, and cause various kinds of [[fun]] in your fortress by stepping on [[pressure plate]]s, pulling [[lever]]s, opening [[cage]]s, picking locks and opening forbidden [[door]]s - it is recommended to not have gremlins and easily-accessible [[Stupid dwarf trick#Self-destruct lever|self destruct lever]]s in the same fortress. One way of exploiting their lever-pulling behaviour is to have a lever that triggers a trap to kill the user when pulled, and leaving it in an area likely to see gremlins visiting. All gremlins are born with Competent [[skill]] in [[ambusher]].

When a gremlin is discovered, the game pauses and centers on it, with the message: "{{DFtext|A gremlin! Drive it away!|4:1}}".

Despite being intelligent creatures, gremlins possess the {{token|PET_EXOTIC}} token and can in fact be [[Animal trainer|trained]] by your [[dwarves]], provided you can bypass their [[trapavoid|natural immunity]] to most [[trap]]s. They don't possess a pet value, which theoretically makes them worthless for keeping around your fort, but if you do manage to capture and train a gremlin, it could actually become your [[mayor]]. In fact, this is quite likely because the gremlin is not able to work, so it will spend all its time in your meeting hall making friends. After a certain period of time a trained adult gremlin will turn into a gremlin hunter and will then hunt alongside your [[hunter]]s. This is because gremlins have natural skill in ambushing, which is associated with the hunting labor.

Note that a trained gremlin will not pull levers mischievously anymore. As explained by [[main:Toady One|Toady One]], the reason they are tamable is roughly that they are supposed to be only pretending to listen to your dwarves so they can mess with your levers and then run away, though trained gremlins currently do not perform this function at all and simply act as regular (albeit buggy) pets.[https://youtu.be/nAB93hOcsPI?t=4300 Source]

In the current version, a stray gremlin will claim a [[bed]] in the [[Tavern|inn]] and become a long-term resident, eventually petitioning for citizenship. This can be mortally annoying, because they will then perform labors and ignore requests to be trained, resulting in trainers dying of starvation and thirst if you aren't careful. A solution to this is to make them exclusively soldiers, or assign them to a small burrow with a workshop exclusive to them, and make the area a training ground, which you can also order them to station in. Being trained isn't a job for the gremlin and it just has to be there; the trainer will eventually finish the job if the gremlin is in the same area. This no longer occurs with their tame offspring. This method can also work for other trained intelligent creatures if you've [[modding|modded]] them to be pets.

Gremlins are carnivorous due to having the {{token|BONECARN}} tag, and are notably long-lived, with some living up to 1000 years. Due to their minuscule size they are terrible at handling [[alcohol]], and cannot wear any other creatures' clothes or armor, nor can clothes or armor be ordered to fit them{{verify|Is this due to the PET_EXOTIC token?}}.

Some dwarves [[Preferences|like]] gremlins for their ''mischief''.

[[File:gremlin_preview.jpg|thumb|230px|center|Acts as bad as he looks.]]

== Trivia ==
Gremlins can talk, and be recruited in [[adventurer mode]], which is useful if one is trapped in a cave and cannot find [[animal people]]. Also, because they both inhabit the first cavern layer and are trainable, the dwarven [[Trading|caravan]] will offer their bodily fluids for sale, including gremlin [[blood]], sweat and tears.{{verify}}
{{D for Dwarf}}


[https://www.youtube.com/watch?v=8zWSrT2TfBc Don't expose them to bright light. Don't feed them after midnight. Don't get them wet.]

{{gamedata}}
{{Creatures}}
{{Category|Humanoids}}

DF2014 Talk:Gremlin

2026-03-23T21:23:46Z

Ziusudra: Undo revision 315597 by 71.202.73.127 (talk) Moved to current talk page

My entry to the trivia part of this article (about merchants selling barrels of gremlin tears, sweat and blood) got removed with the claim that this is true for every creature on the first cavern layer. However, I have never seen any other barrels of sweat or tears. Could someone verify this? [[User:DurianGrey|DurianGrey]] ([[User talk:DurianGrey|talk]]) 17:59, 23 January 2017 (UTC)
:It seems you're correct. I confused it with how you can buy barrels of blood out of anything and thought tears and sweat were included, but it appears only intelligent creatures have materials for tears and sweat. I've included your fact back to the page and apologize for the inconvenience. [[User:OluapPlayer|OluapPlayer]] ([[User talk:OluapPlayer|talk]]) 10:08, 24 January 2017 (UTC)

Talk:Gremlin

2026-03-23T21:23:10Z

Ziusudra: Moved anon question from DF2014 Talk:Gremlin

== What clothing size for gremlins? ==
This is actually a question for the recent version's talk page, but apparently a bot deleted it and anonymous users can't create it. Anyway...

The size options for clothing don't have Gremlin in them, how do I make clothes that fit them? – [[template:unsigned|unsigned]] comment by [[User:71.202.73.127|71.202.73.127]]
:This talk page wasn't deleted, it was never created, because most pages' talk page wouldn't get used. Anonymous users can [[Dwarf_Fortress_Wiki:Page_request|request talk page creation]].

:And gremlins are too small to wear any other creature's size, they should be able to wear a size in the 8572-11428 range, but there are [[List of creatures by adult size|none in that range]]. [[User:Ziusudra|Ziusudra]] ([[User talk:Ziusudra|talk]]) 21:23, 23 March 2026 (UTC)

Position token

2026-03-22T06:50:08Z

Ziusudra: /* Related tokens */ switched text anchor to token templates since those are on another page

{{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]]. The position will use the [[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]]. The 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

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

|-
| {{token|SITE_VARIABLE_POSITIONS|entity}}
| 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]]

Variable positions

2026-03-21T21:51:38Z

Ziusudra: /* Site Governments */ more typos (from formatting, I thought they might be from the game, but it doesn't seem like it)

{{Quality|Fine}}
{{Modding}}
'''Variable positions''' are lesser [[noble|nobility]] titles that can be created by entity leaders after initial world generation. In vanilla, this is the case for [[human]] and [[goblin]] [[Civilization|civilizations]], but also for merchants' companies, guilds, mercenary groups, [[Religion|religious groups]] and [[Criminal|criminal]]s.

== Tokens ==
The tokens that manage the creation of positions are {{token|SITE_VARIABLE_POSITIONS|entity}} and {{token|VARIABLE_POSITIONS|entity}}.

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

== General Info ==
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 civilizations 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.

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) explicitly 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 responsibility 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 ===
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 coincides 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 history 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 immediately 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_responsibilities, 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_pretension, punishment_exemption, has_received_positions, quest_giver, special_burial.
:* "dwarf forced admin" 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, is_diplomat, exported_in_legends, determines_coin_design, account_exempt, color, menial_work_exemption, sleep_pretension, 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 household
|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 household 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 household 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 responsibility. 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 addition 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, Militia 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 referred 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 Groups ==
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_MERCENARY_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 illustrious 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 Companies ==
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).

Position token

2026-03-21T21:41:02Z

Ziusudra: /* Related tokens */ added SITE_VARIABLE_POSITIONS

{{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]]. The position will use the [[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]]. The 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).

|-
| {{text anchor|SITE_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]]

Position token

2026-03-21T21:39:56Z

Ziusudra: Undo revision 315582 by Ziusudra (talk) there is another

{{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]]. The position will use the [[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]]. The 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]]

Variable positions

2026-03-21T21:35:31Z

Ziusudra: removed stub template, reworded/reformatted intro, moved tokens section to top, merged similar general info sections, adjusted section heading levels and names, some typos, removed extra whitespace, removed commented out section

{{Quality|Fine}}
{{Modding}}
'''Variable positions''' are lesser [[noble|nobility]] titles that can be created by entity leaders after initial world generation. In vanilla, this is the case for [[human]] and [[goblin]] [[Civilization|civilizations]], but also for merchants' companies, guilds, mercenary groups, [[Religion|religious groups]] and [[Criminal|criminal]]s.

== Tokens ==
The tokens that manage the creation of positions are {{token|SITE_VARIABLE_POSITIONS|entity}} and {{token|VARIABLE_POSITIONS|entity}}.

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

== General Info ==
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 civilizations 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.

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) explicitly 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 responsibility 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 ===
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 coincides 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 history 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 immediately 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 household
|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 household 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 household 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 responsibility. 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 addition 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, Militia 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 referred 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 Groups ==
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_MERCENARY_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 illustrious 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 Companies ==
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).

Position token

2026-03-21T20:59:14Z

Ziusudra: /* Related tokens */ reword section intro after having deleted other token

{{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]]. The position will use the [[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]]. The 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 ENTITY token is not actually a position token, but bears mentioning on this page because it 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]]

Monarch butterfly

2026-03-19T21:11:29Z

Ziusudra: added distinguish template

{{Quality|Fine}}
{{verminlookup/0
|image=monarch_butterfly_sprite.png
|portrait=monarch_butterfly_portrait.png}}
{{av}}
{{creaturedesc}}
{{distinguish|Monarch}}
'''Monarch butterflies''' are a type of [[above ground]] [[vermin]] found flying around in any area that is warmer than [[biome|freezing]], and will not go out in the winter. They may not be caught in [[animal trap]]s. All monarch butterflies possess Legendary [[skill]] in [[Climber|climbing]].

Some dwarves [[Preferences|like]] monarch butterflies for their ''coloration.

[[File:Vermin-MonarchButterfly.jpg|thumb|center|400px|Admired for its ''coloration''.]]

{{D for Dwarf}}
Be very, very careful of the possibility of a dead monarch butterfly jamming your main entrance open. It can lead to some truly absurd scenarios, as the folks at [[Bloodline:Boatmurdered|Boatmurdered]] can attest to.

{{gamedata}}
{{Vermin}}

Monarch

2026-03-19T21:06:00Z

Ziusudra: switched to distinguish template

{{Quality|Superior}}
{{av}}
{{Minorspoiler}}
{{Noble
| noble= Monarch
| office= Royal Throne Room
| quarters= Royal Bedroom
| dining= Royal Dining Room
| tomb= Royal Mausoleum
| chests=10
| cabinets=5
| racks=5
| stands=5
| mandates=5
| demands=10
| arrival=
* Fortress is a duchy capital and the [[duke|duke/duchess]] is alive
* Sufficient happiness
* [[Fortress|Metropolis]] rank
}}
{{distinguish|Monarch butterfly}}
The '''monarch''' is the highest level [[noble]], and also the noble of the highest precedence. Rather than being promoted from within, like the [[baron]], [[count]], and [[duke]], the existing monarch arrives as an immigrant from the previous capital. However, one of your fortress residents may become monarch if the position is vacant, either by inheriting the title or after conducting "polite discussions with local rivals". A male monarch is known as a "king" and a female as a "queen". Either may arrive with a [[consort]], as well as an entourage that can include the [[outpost liaison]], [[general]], elite military dwarves, and ordinary workers.

To attract the existing monarch the fortress must be [[Fortress#Nomenclature|City]] rank, promoted to a duchy with the [[duke|duke/duchess]] still alive, and reach a certain threshold of overall happiness. These requirements notably do not apply when one of your fortress residents is elevated to monarch.

With the presence of the monarch, a fortress becomes the capital of its [[civilization]]. As a result, it can no longer receive visits from a dwarven [[liaison]] (and so can no longer negotiate trade agreements with the dwarven caravans), nor can it give goods to dwarven caravans as offerings.

The monarch arrives at the same time as an [[immigration]] wave, but has an entirely separate entourage that can spawn from a different part of the map. The monarch's entourage includes a "royal guard" consisting of dwarves with Legendary +5 skill in a random weapon (but no skill in Fighter), Accomplished skill in Dodger, Shield User, and Armor User, and the "doesn't really care about anything anymore" trait. The monarch will arrive even if you have exceeded your [[Immigration|population cap]]s, though the entourage may be limited by the caps.

It may be that your monarch is an ancient [[vampire]] with thousands of kills to their name before arriving at your fortress. Some monarchs have been known to drop dead (''of regicide, perhaps'') as soon as they enter the map, especially in older worlds. Monarchs may also be of a different race, such as [[Main:Cacame Awemedinade|an elven king]].

Random dwarves in [[dwarf fortress mode]] can become monarchs, if the current monarch dies, or if the position was vacant (common in dying civilizations). If the position no longer exists (i.e. the civilization is truly [[extinct]]) then no monarch will be appointed until the civilization is "resurrected" (by retiring a fortress, for example).

An adventurer can become a monarch; if they succeed in [[talking|persuading]] the current one to [[Combat#Wounds|yield]], the monarch may then offer their position to the adventurer. (Whether they yield or offer may depend on their relative [[personalities]] and [[social skill]]s.{{verify}})

== Becoming a Mountainhome ==
{{Template:Minorspoiler}}
[[File:WeMustDigDeeper.png|frame|center|By royal decree, avoiding the hidden fun stuff is no longer possible.]]

Once the monarch arrives and all room requirements are met, the player will be prompted to find "seven symbols not of this world" as well as to construct a "true throne". These symbols and the materials needed to build the "true throne" can be found inside an [[unusual volcanic wall]] (see for more details). Upon completion of this quest, you will be elevated from the Capital to the Mountainhome of your civilization, and it will be well-earned: this quest is fraught with danger that can end the entire fortress outright. The monarch's entourage of elite soldiers will make the challenges far more doable, but brute force can only take you so far. You'll have to [[exploit|think like a dwarf]] to stand a chance at seeing this to completion.

== In other civilizations ==

Elves also have a monarch position of sorts, but in terms of function and importance they're royalty in name only. The actual position at the top is the [[druid]], capable of appointing the monarch position. Elves are notable only in that they have a defined princess (both their monarchs and the position under them are always female) position that can succeed a queen. However this doesn't actually replicate a hereditary monarchy, as princesses have to be replaced by the druid appointing a new one. Both serve various noble functions, with princesses having many of the same responsibilities as the dwarven [[general]].

Humans and goblins, meanwhile, generate equivalent positions during worldgen. These tend to have names like "law-giver" or "master", and presumably have most of the functions and behavior dwarven monarchs do – without extracting the information from the world data, however, it can be difficult to tell. In the case of goblins, the position of master often starts off taken by [[demon|something else entirely.]]

[[File:Ezum-sarasti.jpg|thumb|center|300px|Artist rendering of a dwarf king by Mechlin ([http://www.bay12forums.com/smf/index.php?topic=169691.msg7701761#msg7701761 post])]]

== Bugs ==
The arrival of the Monarch is not necessarily an advantage for a fortress, as it comes with a significant risk of an accidental [[loyalty cascade]].

If a dwarf goes berserk, or, during a tantrum, attacks a member of the Monarch's entourage, a loyalty cascade can be triggered. This can be particularly [[fun]] as the entourage can include several dwarves with high proficiency in military skills.

{{gamedata| [POSITION:MONARCH]
[NAME_MALE:king:kings]
[NAME_FEMALE:queen:queens]
[NUMBER:1]
[SPOUSE_MALE:king consort:kings consort]
[SPOUSE_FEMALE:queen consort:queens consort]
[SUCCESSION:BY_HEIR]
[RESPONSIBILITY:LAW_MAKING]
[RESPONSIBILITY:RECEIVE_DIPLOMATS]
[RESPONSIBILITY:MILITARY_GOALS]
[PRECEDENCE:1]
[SPECIAL_BURIAL]
[RULES_FROM_LOCATION]
[MENIAL_WORK_EXEMPTION]
[MENIAL_WORK_EXEMPTION_SPOUSE]
[SLEEP_PRETENSION]
[PUNISHMENT_EXEMPTION]
[FLASHES]
[BRAG_ON_KILL]
[CHAT_WORTHY]
[DO_NOT_CULL]
[KILL_QUEST]
[EXPORTED_IN_LEGENDS]
[DETERMINES_COIN_DESIGN]
[COLOR:5:0:1]
[ACCOUNT_EXEMPT]
[DUTY_BOUND]
[DEMAND_MAX:10]
[MANDATE_MAX:5]
[REQUIRED_BOXES:10]
[REQUIRED_CABINETS:5]
[REQUIRED_RACKS:5]
[REQUIRED_STANDS:5]
[REQUIRED_OFFICE:10000]
[REQUIRED_BEDROOM:10000]
[REQUIRED_DINING:10000]
[REQUIRED_TOMB:10000]}}
{{nobles}}
{{Category|Aristocrats}}

Archery target

2026-03-19T04:17:26Z

Ziusudra: added specific mention of being built from material instead of item

{{Quality|Exceptional}}
{{Building|name=Archery target|key=y|key2=t
|construction=
* [[Building material]] (non-[[economic]])
|construction_job={{Template:Material-specific building labors}}
|purpose=
* Make Archery range
}}{{av}}

An '''archery target''' is a [[building]] which is used to to train your [[marksdwarves]]. Archery targets can be built from [[wood]], which requires [[carpentry]]; [[stone]] or [[glass]], which requires [[masonry]]; or [[metal]], which requires [[metalcrafting]]. Unlike other similar buildings, they are built from the raw materials, rather than an item crafted at a workshop; this means they can also be built from [[block]]s made from the above materials.

==Making an archery range==
To make an archery range,
[[File:Archery_Range_Zone.png|right|An archery range zone Options.]]
#{{Menu icon|b|y|t}} Build one or more Archery targets in a room/area
#{{Menu icon|z}} Make an Archery Range [[zone]] over the constructed archery targets. [[Barracks]] and Archery Range zones can be stacked so the Archery Range can be included in the Barracks footprint.
#Paint the Archery Range zone like any other.
#Select the zone and specify the shooting direction.
#[[File:Ui assign squad.jpg]] Assign the range to the desired [[squads]] using the flag icon.

[[File:archery_range_anim.gif|thumb|343px|right|An archer in archery range. How original.]]
The zone can then be used by military dwarves who have '''''no order''''' (i.e. they're set to inactive or set to only active/training){{Bug|6070}} in their [[schedule]] that month, in order to train ranged [[weapon]] [[skills]]. Since [[bolt]]s are being used up by this training, it may be a good idea to [[equipment|set]] the dwarves to only use [[bone]] or [[wood]]en bolts when training.

Archery ranges may include any number of archery targets. The dwarves will simply line up on one end and shoot at the other end of the range, with one dwarf per 'width' of the zone able to use the range at once.

It is also advisable for the archery target rooms to be included in the area of the barracks where your marksdwarves train. Both the barracks and the archery targets need to be assigned to squads individually.

==Notes==
*The size of the range must be large enough so that the marksdwarf is able to stand at least 1 tile away from the target (Dwarves will '''not''' train if the size of the range means they have to stand adjacent to the target).
*Experience is granted per shot, not per target hit.
*Only one soldier can use an archery target at a time.
*Marksdwarves will only practice at an archery range if their [[quiver]]s contain ammunition which is permitted for training.
*Marksdwarves do not spend all of their free time performing archery practice - during downtime, they will complain that they "cannot follow orders". Assigning marksdwarves to a [[barracks]] will allow them to use this spare time to perform combat drills, though said drills can potentially cut into archery practice.
*When setting up training orders for your marksdwarf squad, rather than setting 1 order for X number of dwarves to train, it's advisable to set multiple training orders of 1 dwarf each. If a train order contains multiple dwarves, even if their only training area is an Archery Range, they may decide to do group drills rather than practice at the range. Since range practice is always solo, setting several 1 dwarf training orders will guarantee they practice their marksdwarfship.

==Bugs==
*The flag for active/inactive seems to get mixed up, so marksdwarves will only use archery targets when they're inactive.{{Bug|6070}}
[[File:archery_target_preview.png|thumb|170px|center|Bullseye!]]
{{buildings}}
{{Zones}}
{{Category|Zones}}

Advanced world generation

2026-03-13T08:21:37Z

Ziusudra: /* Seed notes */ added DFHack command

{{migrated article}}
{{Quality|Superior}}
{{av}}
:''This article contains information on advanced world generation. For information on basic world generation, see [[World generation]].'' ''See [[World token]] to more easily find information by the names used in the world_gen.txt file, [[World rejection]] for information on solving problems related to worlds always being rejected, and [[Worldgen examples]] for example worlds.''

[[File:adv_worldgen_v50.png|thumb|400px|right|The advanced world generation screen. ''(Click to enlarge)'']]'''Advanced world generation''', also labeled as '''detailed mode''', allows substantially more detail-oriented options of customization than standard, basic world generation. This gives the player much more control over how their world is generated. To better understand this article, it is advised that one should read about [[World generation|'''basic world generation''']] first.

The advanced world generation screen is reached by clicking "Create new world" at the main menu, then clicking "Detailed mode". Once at that screen, clicking "Basic options" will return the user to the standard world generation screen.

== Parameter sets ==
There are multiple default sets of all the advanced world generation parameters hard-coded in ''Dwarf Fortress'', which will be overridden by the <tt>prefs/world_gen.txt</tt> file in the main ''Dwarf Fortress'' directory, if it exists. It does not exist by default, you must create it, either by saving the default sets, or saving a copy from the [[world_gen.txt]] wiki page or elsewhere. This file can then be edited with a text editor, and you can copy and paste other players' sets of parameters into it. For sources of such parameter sets see [[Advanced_world_generation#Parameter_set_examples|Parameter set examples]] below.

To get back the default sets, move the existing <tt>prefs/world_gen.txt</tt> to somewhere else (like Documents), or delete it if you do not want to keep the changes, then load the sets in the game, it will then use the hardcoded defaults.

== User interface ==
First, there is a line of text inputs and buttons along the top of the screen, from left to right:
* The drop down menu of currently defined parameter sets, click the down arrow to select a set that you want to work with. The currently selected set can be renamed by clicking the current name or the [[File:Quill.png]] button. The first set in the file is selected by default, usually "LARGE ISLAND". See [[#Parameter set title|Parameter set title]].
* The dimensions of the world for the selected set, see [[#World dimensions|World dimensions]].
* A text entry box to set all of the seed options to the same seed, will show "Random seed", "Various seeds", or, if all four seeds are set to use the same value, that value. See [[Advanced_world_generation#Seed_values|Seed values]] and [[Advanced_world_generation#Seed_values|Seed notes]].
* The Copy Button to make a copy of the currently selected set and appends it to the bottom of the list.
* The red Delete button to delete the currently selected set, you will be prompted to confirm the deletion.
* The New parameter set to create a new parameter set and appends it to the bottom of the list. This seems to just copy the default "LARGE REGION" set.
* The Save button to save all of the current sets to the <tt>prefs/world_gen.txt</tt> file.
* The Load button to load from the same file, there is no confirmation, '''any unsaved changes will be lost'''. If that file does not exist, this resets all of the sets to the defaults.

Most of the middle is the parameters themselves, with a scroll bar to the right. Each row of the list can include:
* The name of the option
* The range of accepted values; not every option has this, and does not always match the displayed value, for example "0 to 1" might show as "No" and "Yes".
:* Sometimes the range might not initially show on rows that it should, reloading the sets with the Load button sometimes fixes that.{{bug|13176}}
* A plus button to increase the value or cycle through options, when applicable (this button will be missing if the range is missing.)
* The current value; can be clicked to edit, to actually set a value you must press {{k|enter}}, without doing that, clicking another entry box or right clicking will instead reset to the currently set value.
* An edit button to show that the previous box is editable, same as clicking on the text box.
* A minus button to decrease the value or cycle through options, when applicable (this button will be missing if the range is missing).
* A red button to disable this parameter, when applicable, usually setting the value to 0, or -1.

{{notice bar|bgcolor=#faa|bordercolor=#f00|All of the buttons below leave this screen and do not prompt to save the sets, so unsaved changes may be lost.}}
At the bottom right are 3 or 4 more buttons:
* The Create world button to do just that using the currently selected set, '''unsaved changes are lost'''.
* The Basic options button to go back to the normal world generation screen, unsaved changes are not lost if you come directly back to Detailed mode.
* The [[Mods]] button to go to the mod selection screen, unsaved changes are not lost if you come directly back to Detailed mode. Only shown if mods are available.
* Back to main menu button to do just that, '''unsaved changes are lost'''.

=== World painter ===
:''Main article: [[World painter]]
The '''world painter''' tool is not in the current version of ''Dwarf Fortress''; it allowed you to paint features onto a map. '''However''', those maps can still be used when generating a world by pasting world painter parameter set maps created in old versions into the <tt>prefs/world_gen.txt</tt> file. [[Utilities#Perfect_World_DF|Perfect World DF]] is a utility that uses the same parameter functionality as the world painter to paint a map, and it also can work with the current version of ''Dwarf Fortress''.

== Generating a world ==
You can either use an already-defined parameter set, or you can edit them, though it is highly suggested to edit a copy of one of the defaults. Once you are happy with the parameters you should save the values you just edited before you click the Create world button. Information about each parameter is documented below.

The phases of the world generation process are (this order is not completely correct):
* Preparing elevation...
* Setting temperature...
* Running rivers...
* Forming lakes and minerals...
* Growing vegetation...
* Verifying terrain...
* Importing wildlife...
* Recounting legends...
* Placing civilizations...
* Making cave civilizations...
* Making cave pops...
* Placing other beasts...
* Placing megabeasts...
* Placing good/evil...
* Placing caves...
* Prehistory generation
* Finalizing civ mats...
* Finalizing art...
* Finalizing uniforms...
* Finalizing sites...

== Seed notes ==
The world generation process uses a PRNG (Pseudo Random Number Generator) algorithm. A PRNG will produce a sequence of numbers that "looks" random, even though the actual sequence of numbers will always be the same if the PRNG is started with the same seed value. Basically this means that if you run world generation with a certain seed value on your computer, and someone else runs world generation with the same seed value on their computer, the same sequence of random numbers will be generated on both computers. The practical impact of this is that someone else can generate exactly the same world that you generated by entering the same seed value that you used.

In the current version, the seed values for the world itself and the names seem to produce the same result, but you will get changes in events which will result in a very different world history.{{bug|6934}} Keep this in mind if you want to regenerate a particular world.

The way that a world is generated can also be affected by certain world tokens. Changing them causes that code to use more or fewer PRNG values, causing later uses to get different parts of the sequence. So, you cannot for example, change the minimum and maximum rainfall and get 'the same world but drier or wetter', instead, a different world is generated. That said, it would also seem that certain small changes to these world tokens can occasionally generate a very similar world, however, other tokens are more sensitive. For more information see the forum thread [http://www.bay12forums.com/smf/index.php?topic=112132.msg3404199#msg3404199 here].

The following are tokens which use the PRNG values in ways that changing them will likely cause broader changes:

* [DIM:X:X]
* [ELEVATION:X:X:X:X]
* [RAINFALL:X:X:X:X]
* [TEMPERATURE:X:X:X:X]
* [DRAINAGE:X:X:X:X]
* [VOLCANISM:X:X:X:X]
* [SAVAGERY:X:X:X:X]
* [ELEVATION_FREQUENCY:X:X:X:X:X:X]
* [RAIN_FREQUENCY:X:X:X:X:X:X]
* [DRAINAGE_FREQUENCY:X:X:X:X:X:X]
* [TEMPERATURE_FREQUENCY:X:X:X:X:X:X]
* [SAVAGERY_FREQUENCY:X:X:X:X:X:X]
* [VOLCANISM_FREQUENCY:X:X:X:X:X:X]
* [PARTIAL_OCEAN_EDGE_MIN:X]
* [COMPLETE_OCEAN_EDGE_MIN:X]
* [HAVE_BOTTOM_LAYER_1:X]
* [MINERAL_SCARCITY:X] {{cite talk/this|Mineral scarcity}}

Many other world parameters, such as end year and embark points, can, however, be changed without it having any effect on the geography of the world generated from the seed values.

Normally, you don't enter these seed values, the game comes up with values based on some other sort of pseudo-random information from things like the current date and time.

When generating a world, ''Dwarf Fortress'' records the seeds it used in [[gamelog.txt]]; they can also be found with <code>gui/gm-editor world.worldgen.worldgen_parms</code> in [[DFHack]].

== Advanced parameters ==
There are essentially 4 types of controls for the generation of the surface map;

'''Terrain parameters''': as described below, these 5 variables define the basic background world, how hot or cold it is, how much rainfall, how high the mountains are. The world automatically goes through the temperature range along the Y axis, although sometimes it will be hotter in the north, other times in the south, or cold at both. Minimum, maximum and X,Y variance can drastically alter the world.

'''Weighted meshes''': these are a way to fine-tune the amount of the 5 basic variables on the map. They can be used to set the specific distribution of different elevations or rainfall areas for example.

'''Feature parameters''': such as rivers, mountain peaks, volcanoes, and oceans, which can cause rejections if the terrain parameters don't allow enough suitable locations for the features to be placed.

'''Rejection parameters''': ''Dwarf Fortress'' uses a 'belt-and-braces' approach to world generation. The above controls allow you to shape the world, then the rejection parameters throw it out if it does not meet certain criteria. There are a number of rejection parameters for the number and degree of the 5 basic variables, for biome types, etc. If the world does not meet the requirements of any one rejection parameter the world is rejected and re-randomised. Also see [[World rejection]].

Leaving tokens out of a set in <tt>world_gen.txt</tt> will cause the game to use default values which are not adjusted for smaller world sizes, this may cause smaller worlds to always be rejected.

If you are experimenting with world design, there is also a [[Settings#Feature_toggles|game setting]] that will log the rejection reasons to ``[[map_rejection_log.txt]]``. With that information you can then either adjust the rejection parameters to allow those worlds, or the other parameters to prevent them from trying to generate. ''Dwarf Fortress'' will keep adding to the file, so you may want to trim or delete it occasionally.

The parameters are described below in the order that they appear in the list in the game, which is not necessarily the order they appear in <tt>world_gen.txt</tt>. See [[world token]] for an index that will help you look things up by token name. The tokens used in <tt>world_gen.txt</tt> are at the bottom of each of the following parameter descriptions.

=== Parameter set title ===
This sets the name of the parameter set itself, as used in the list of sets (this has nothing to do with the name of the generated world).
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITLE:<name>]</nowiki></tt>
| <tt><nowiki>[TITLE:MEDIUM ISLAND]</nowiki></tt>
| Required
|}

=== World dimensions ===
The size of the map for the current set can be changed by changing the Width and Height values at the top next to the set title. You will need to confirm this, since changing the dimensions of the world will change other parameters, because many of them have different defaults depending on the surface area available.

Larger maps usually take longer to generate and may reduce [[Frames per second|FPS]] in-game, though this is really a matter of larger worlds usually having more civilizations, sites, historical figures, and events; restricting the number of those can speed up the process. Non-square maps may result in crashes{{bug|2928}}.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DIM:<width>:<height>]</nowiki></tt>
| <tt><nowiki>[DIM:257:257]</nowiki></tt>
| Valid values are 17, 33, 65, 129, and 257, other values will use one of those. Changing the size in the file without adjusting other parameters can cause many rejections.
|}

=== Seed values ===
Enables the use of, and specifies seed values for, different parts of the world generation process. Just entering a specific seed does not enable it, that must be done separately, although using the box at the top to set all the seeds to the same value does enable them all. Enabling a seed puts the token in using what ever is in the text box below. If you enable a seed, but do not enter a seed, the string "Seed text" will be used (<tt><nowiki>[SEED:Seed text]</nowiki></tt>). Trying to use a <tt><nowiki>]</nowiki></tt> in the string in the file will end the seed there, since it closes the token, any text after that will be ignored. Normally, just leave these set to Random, unless trying to reproduce the results of a previous world generation. See also the [[Advanced_world_generation#Seed_notes|seed notes section]] above.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEED:<text>]</nowiki></tt>
| <tt><nowiki>[SEED:31337]</nowiki></tt>
| rowspan="4" |
For each of these not in the config file, a random seed will be used, and the first seed is not used to generate the others. The seeds used are output to [[gamelog.txt]] when world generation starts.
|-
| <tt><nowiki>[HISTORY_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[HISTORY_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[NAME_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[NAME_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[CREATURE_SEED:<text>]</nowiki></tt>
| <tt><nowiki>[CREATURE_SEED:31337]</nowiki></tt>
|}

=== World name ===
As previously mentioned, the title of the parameter set doesn't affect the name of the world. You can specify a particular name for your world, or leave the value blank for a random one. (The [[DFHack]] utility adds an option to rename the world using the in-game languages.)
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CUSTOM_NAME:<name>]</nowiki></tt>
| <tt><nowiki>[CUSTOM_NAME:Realm of Cheese Engravings]</nowiki></tt>
| For a random name, simply don't use this token.
|}

=== Embark Points ===
The number of points for equipment and animals when embarking in fortress mode (there is no equivalent setting for adventure mode). Normally, the default of 1504 is fine, but can be increased for various purposes like experimentation or to help dwarves survive in a particularly evil world, or reduced for certain [[challenges]].
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EMBARK_POINTS:<number>]</nowiki></tt>
| <tt><nowiki>[EMBARK_POINTS:1504]</nowiki></tt>
| 0 to 10,000
|}

=== End year ===
The maximum number of years generated for the world, although generation can be paused and the world used as is any time after the second year; the same as the [[World_generation#History|History]] parameter in basic world gen, except that you can enter an exact value. A too-short history can limit the materials available to civilizations, and [[Chosen|certain adventure mode features]] are only available after certain site events, while too long a history often leads to civilizations dying.

For more information on the history aspect of the game, see [[Legends]] and [[Calendar#Ages|Ages]].
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[END_YEAR:<number>]</nowiki></tt>
| <tt><nowiki>[END_YEAR:250]</nowiki></tt>
| 2 to 10,000
|}

=== Population cap after civ creation ===
A soft limit to the total number of [[historical figure]]s alive at the same time during generation across all civilizations, only preventing the birth of new historical figures.{{cite forum|140544/5701667}} Each civilization is allotted a percentage of the total by the percentage of sites they control.{{cite forum|159164/7553641}} Civilizations also have non-historical populations, and there is no setting to limit those (in early versions, all civilization members were historical figures, this is also why the name of this setting is misleading). Each [[entity]] also has limits from their raws, see the [[Entity_token#Population|population]] entity tokens, and setting this to unlimited will not remove those.

Huge historical figure populations can slow generation and the game in general.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_POPULATION:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_POPULATION:15000]</nowiki></tt>
| -1 to 100,000, -1 is no limit
|}

=== Site cap after civ creation ===
Total number of [[site]]s that can be directly created by all civilizations combined like [[hillocks]], [[hamlet]]s, [[dark pits]], [[forest retreat]]s, etc. Does not prevent the placement of initial civilization sites, though they will then be counted for the limit. Does not affect creature sites like [[cave]]s or [[lair]]s, group sites like [[castle]]s, [[monastery|monasteries]], [[tower_(necromancy)|tower]]s, [[fort]]s, or [[camp]]s, or unpopulated sites like [[tomb]]s. After this limit is reached, no civilization will be able to place new sites. See the [[Entity_token#Placement|placement]] entity tokens for other ways that civilization site placement can be limited.

Increasing this will slow generation down and reduce the available places for player sites. Since the {{token|MAX_SITE_POP_NUMBER|entity}} entity token limits the historical figure population per site, this site cap can also limit the total historical figure population of all civilizations combined, and some expand faster than others getting more sites before the limit is reached.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SITE_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SITE_CAP:1500]</nowiki></tt>
| -1 to 100,000, -1 is no limit
|}

=== Beast control ===

These parameters don't usually matter too much, but may matter for small numbers of beasts.

==== Percentage of Megabeasts and Titans Dead for Stoppage ====

The world starts out with a certain number of powerful megabeast and titan entities in existence. If a percentage of the megabeast and titan population dies out during history generation, then history generation will stop early. For example, if the elimination value is 80%, and the generated history starts with 200 entities and 160 of those 200 entities are eliminated by historical events before the End Year is reached, history generation will stop immediately.

If you want to end the creation of your world at the beginning of a certain age, choose the following values:
* Age of Legends: ~34%
* Age of Heroes: ~67%
If there are three or fewer titans or megabeasts in your world, the age will be given a special name reflecting the remaining megabeasts/titans, instead.

==== Year to Begin Checking Megabeast Percentage ====

The percentage of dead [[megabeast]]s and [[titan]]s for stoppage will not be checked until this year is reached in history generation. This can be used to ensure that a world reaches a certain year even if all of the megabeasts in the world are slain earlier.

If the number of living [[megabeast]]s and [[titan]]s starts at or drops to less than four, then world generation will always stop if the current year is equal to or greater than the Year to Begin Checking Megabeast Percentage ''regardless'' of how many [[megabeast]]s and [[titan]]s are dead — Percentage of Megabeasts and Titans Dead for Stoppage is ignored. The number of megabeasts and titans at the start of the world is set by the sum of the [[Advanced_world_generation#Max_Megabeasts_Caves|Max Megabeasts Caves]] and [[Advanced_world_generation#Titan_Parameters|Titan Number]] parameters.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[BEAST_END_YEAR:<year>:<percentage or -1>]</nowiki></tt>
| <tt><nowiki>[BEAST_END_YEAR:200:80]</nowiki></tt>
| Use -1 as percentage to disable. Year must still be at least 2.
|}

=== Cull Unimportant Historical Figures ===
{{main|Historical figure}}
Whether to remove unimportant dead historical figures after history generation; a short CPU-intensive step, but saves space which can speed up loading, saving, and running games with large histories. Legends mode will refer to culled creatures as "an unknown creature", and they will not appear in engravings, but likely would not have anyway.

Exactly what is considered important is not clear. A member of an abstract group killing a named creature is not. Creating an artifact is not, even if that artifact had important history. Unculled historical figures can have parentage described as "The identity of" that parent "has been lost to time", so just having children is not, though having living direct relations seems to prevent culling.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CULL_HISTORICAL_FIGURES:<0 or 1>]</nowiki></tt>
| <tt><nowiki>[CULL_HISTORICAL_FIGURES:0]</nowiki></tt>
| 0 = No, 1 = Yes
|}

=== Reveal All Historical Events ===

Setting this to Yes will allow access to most information about the history of the world in [[Legends mode]]. All events will be revealed, but some [[historical figure]]s, [[site]]s, [[region]]s, and [[civilization]]s and other entities may not be, possibly because they are not known to any civilization. If set to No, then you will have to discover historical information in [[adventure mode]] or by instructing dwarves to make engravings.{{Verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[REVEAL_ALL_HISTORY:<0 or 1>]</nowiki></tt>
| <tt><nowiki>[REVEAL_ALL_HISTORY::1]</nowiki></tt>
| 0 = No, 1 = Yes
|}

=== Terrain Parameters ===

These set limits and variance for terrain elevation, rainfall, temperature, drainage, volcanism, and savagery which determines how those values are generated. What biomes exist are then determined by how these factors overlap with each other.

==== Minima and Maxima ====
These are the absolute minimum and maximum values that can ever be generated for a particular map square characteristic. By ''subtly'' tweaking the min and max values, vastly different maps can be made. Changing these can cause the occurrence of certain [[Biome|biomes]] to become impossible, so you may want to use [[#Terrain Mesh Sizes and Weights|Weighted Ranges]] instead.

==== X and Y Variance ====
These control how wildly things like elevation and rainfall can vary between adjacent map squares. For example, if these values are set to the maximum of 3,200 for elevation then you will end up with more very low areas right next to very high areas. The number for X determines the east-west variance and the number for Y determines the north-south variance. By setting only one of these to a high value you can, for example, create horizontal or vertical bands of areas which are more similar to each other.

Generally speaking, raising both of these values will create a more random "patchwork" of many small biomes while setting both x and y values to 0 will cause every square on the map to use a single random value for the given characteristic.

For "patchwork" worlds to avoid being rejected, [[#Maximum Number of Subregions|Maximum Number of Subregions]] will probably need to be increased from the default.

==== Elevation ====
This controls the range of terrain elevations that can occur in the world. Usually, you just want to leave the min/max values alone. Raising the minimum elevation can, for example, make it impossible for oceans to exist. This does '''not''' directly control the number of available Z-levels at a particular site, though high maximum values may contribute to peaks, which can raise the number of above ground Z-levels - in other words, a maximum elevation of 400 and minimum of 1 does not mean you get 400 Z-levels, but it might increase the number of Z-levels somewhat in some regions compared to others. Raising the variance will result in a more bumpy, uneven landscape.

Some biomes/features that are impacted by elevation:
* A high minimum (above 99) means no oceans, as they need elevations below 100.
* A low maximum (below 300) means no mountains, as mountains need elevations above 300.
* Rivers will be placed when the elevation maximum is 104 or higher. Therefore, keeping both values above 100 and below 104 will prevent all water tiles from appearing.
* Mountain peaks can only form at elevations of 400.

==== Rainfall ====
Controls the amount of rainfall in each map square/area. Setting the minimum or maximum too high or low can make the formation of certain biomes impossible. Rainfall causes it to [[rain]] more in a given area, which can have various effects. Also makes more rivers appear on the world map.

Note that if [[#Do Orographic Precipitation and Rain Shadows|orographic precipitation and rain shadows]] is on, then mountains will cause additional variance in rainfall, so (for example) rainfall below the specified minimum can occur in the shadow of a mountain. If you want the minimum and maximum for this parameter to be absolutely respected, you must turn off the orographic precipitation option.

Additionally, with 'Orthographic Precipitation' turned on, orthographic precipitation and rain shadows will only occur in regions with greater than or equal to 50 drainage. [http://www.bay12forums.com/smf/index.php?topic=139916.0 [Report, reproduced 2022]]

==== Temperature ====
{{main|Climate|Temperature}}
These parameters control how hot or cold various areas will be. If you lower the minimum and maximum values, the world will be colder overall, for example. As with the others, changing these values too much could make it impossible for certain biomes to exist. The temperature scale used in this setting is related to regular degrees Urist by the equation "local temp = world temp * 0.75 + 10000".{{cite forum|169696/8395484}} This scale doesn't seem to be used anywhere else in the game. See [[Climate]] for more info.

These parameters form the "base" temperature for an area, and describe peak summer temperature in a scale that isn't used elsewhere in the game. This number also does not correspond 1:1 with the final climate. [[Temperature]] is always influenced by a number of variables, including elevation, time of year, thick forestation, and if [[Advanced_world_generation#Poles|poles]] are enabled, latitude. These other variables are factored in after the temperature mesh is applied, and frequently bring temperatures above and below their set minimum and maximum values. ''The inclusion of Poles is particularly strong in this regard, as it allows latitude to raise and/or lower temperatures by more than 75 degrees Celsius! That said, the temperatures aren't raised or lowered by more than about 65 degrees past the set minimum and maximum. Furthermore, for typical ranges, the temperature will never be raised more than about 25 degrees past the maximum (but will still drop up to about 65 degrees Celsius below the minimum).'' (unsure about exact values, research needed)

Elves can spawn where the temperature is 10 degrees or warmer, and humans can spawn where the temperature is 0 degrees or warmer.

==== Drainage ====
Changing drainage parameters will change the way water-affected biomes are formed. Low drainage will contribute to the formation of [[Lake|lakes]], [[River|rivers]], and [[Swamp|swamps]]. High drainage will cause water to sink into the ground rather than sit on the surface, which is important for forming hills.

Lower drainage values have been reported to contribute to the formation of thicker soil layers, though it is currently unknown exactly how other factors (such as elevation or perhaps rain) impact soil formation.

==== Volcanism ====
Volcanism controls the occurrence of igneous [[layer]]s, and the formation of volcanoes. For a volcano to form, a square must have a volcanism value of 100, so reducing the maximum from 100 will make volcanoes impossible. Raising the minimum will increase the rarity of non-igneous layers.

Setting the minimum to a high value is not a good way to produce multiple volcanoes, as you are likely to get a "Volcanism not evenly distributed" rejection. Instead, use the Minimum Number of Volcanoes parameter, and possibly adjust the weighted ranges for volcanism as described below.

==== Savagery ====
These parameters control the level of [[Surroundings#Savage|savagery]] on the map. Raising the minimum savagery too high may make it impossible for certain races to exist, and similarly lowering the maximum too far can make it impossible for certain creatures to exist. The largest chance of having unusable maps comes from a too-high savagery value.

==== Configuration Tokens ====
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[ELEVATION:1:400:401:401]</nowiki></tt>
| Range: 0 to 400 Maximum of 400 required for mountain peaks. Variance range: 0-3200
|-
| <tt><nowiki>[RAINFALL:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[RAINFALL:0:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|-
| <tt><nowiki>[TEMPERATURE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE:25:75:200:200]</nowiki></tt>
| Range: -1000 to 1000 Variance range: 0-3200
|-
| <tt><nowiki>[DRAINAGE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE:0:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|-
| <tt><nowiki>[VOLCANISM:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM:1:100:200:200]</nowiki></tt>
| Range: 0 to 100 Maximum of 100 required for volcanoes. Variance range: 0-3200
|-
| <tt><nowiki>[SAVAGERY:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY:1:100:200:200]</nowiki></tt>
| Range: 0 to 100 Variance range: 0-3200
|}

=== Terrain Mesh Sizes and Weights ===

These parameters make it possible to influence the number of squares in a particular range, without making conditions outside of that range impossible. For example, you can make it possible for many more low-elevation squares to exist without making it impossible for high elevations to form. Changing these parameters is often preferable to simply changing the min/max values.

The basic steps of applying weighted ranges are as follows:

# Create a grid with 2''MeshSize'' - 1 tiles in both X and Y direction.
# At each grid intersection, set the value according to the weighted ranges.
# Smooth out the area between the intersection points.
# Add noise according to the variance parameters.

where ''MeshSize'' is the raw parameter value found in the world_gen.txt. See the image on the right for an example.

[[File:World_map-large-32x32-elevation-mesh.png|thumb|300px|A large world generated with an Elevation Mesh Size of 32×32 and range weights set to 1:0:0:0:1 (i.e., only extreme high and low elevations). Note how the grid intersections are either set very high or very low and the space between them is smoothed out.]]

==== Mesh Size/Weighted Ranges ====

Mesh size determines how many grid tiles there will be. Setting this to Ignore will cause the weighted range settings to be ignored for that terrain characteristic. As an example, setting it to 2×2 means the grid will be 2 times 2 tiles large and there will be 3×3 for a total of 9 intersection points. On a pocket world, this means one grid tile will be 8×8 world tiles large, whereas on a large world, one grid tile will be 128×128 world tiles. Note that the highest possible value for a given world size will always make the grid tiles 8×8 world tiles large.

If mesh size is set to something other than Ignore, these weights will be applied at the granularity of the selected mesh size for purposes of generating random values in each range. This allows random number generation to be non-linear for the given terrain characteristic.

For example, if the Elevation Weighted Range parameters were set to (starting with the 0-20 range) 60:10:10:10:10 (these values do not have to add up to any particular number) and elevation min and max are set to 1 and 400 respectively then about 60% of the grid line intersection points (on average) will be set to an elevation in the range of 1-80 (0% to 20%), and the other ranges will be represented by around 10% of the intersection points each. The exact distribution is still left up to chance though ''on average'' it will be close to this specification.

Weighted ranges do not make rejection checks, although they can be responsible for many rejections if you neglect to adjust or disable some of the [[#Minimum Number of Mid/Low/High Characteristic Squares|Minimum Number of Mid/Low/High Characteristic Squares]] for example.

==== Interaction between Mesh Size and Variance ====

The end result can vary greatly depending on how the corresponding [[#X_and_Y_Variance|X and Y Variance]] parameters are set. First of all, if the variance is too large the noise it adds can completely negate the effect of the weighted ranges. For instance, with a 2×2 mesh, the default variance parameters are high enough that usually the mesh grid can hardly be recognized. How strong the variance's effect is, is also dependent on the mesh size. Having a larger mesh size (i.e. smaller grid tiles) means the variance also has to be higher for a visible effect. For instance, with a variance of 400, the effects are clearly visible with a 2×2 mesh and barely visible at all with a 8×8 mesh. Note that this effect is directly dependent on the mesh size and not, as one might expect, on the actual size of the grid tiles. This means, that a large world with a 32×32 mesh will look essentially the same as a pocket world with a 2×2 mesh, only stretched to 256 times the size.

Also see this [http://www.bay12forums.com/smf/index.php?topic=139916.0 forum post] for more details.

==== Configuration Tokens ====

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[ELEVATION_FREQUENCY:2:1:2:3:4:5]</nowiki></tt>
| rowspan="6" | Valid mesh values:

1 = Ignore

2 = 2x2

3 = 4x4

4 = 8x8

5 = 16x16

6 = 32x32

(limited by world size)
|-
| <tt><nowiki>[RAIN_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[RAIN_FREQUENCY:3:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[DRAINAGE_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE_FREQUENCY:4:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[TEMPERATURE_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE_FREQUENCY:1:1:1:1:1:1]</nowiki></tt>
|-
| <tt><nowiki>[SAVAGERY_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY_FREQUENCY:5:1:2:3:4:5]</nowiki></tt>
|-
| <tt><nowiki>[VOLCANISM_FREQUENCY:<mesh>:<0-20 weight>:<20-40 weight>:<40-60 weight>:<60-80 weight>:<80-100 weight>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM_FREQUENCY:1:1:1:1:1:1]</nowiki></tt>
|}

=== Poles ===

With this, you can influence how polar regions are added. The poles can be on the north or south edge, and the equator will be on the opposite edge, or in the middle if there are two poles. If poles are set to NONE, then there will be no seasonal changes in the weather (e.g. no winter snow in temperate biomes).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[POLE:<placement>]</nowiki></tt>
| <tt><nowiki>[POLE:NORTH]</nowiki></tt>
| Viable options: NONE, NORTH_OR_SOUTH, NORTH_AND_OR_SOUTH, NORTH, SOUTH, NORTH_AND_SOUTH
|}

=== Minimum Mountain Peak Number ===

This will cause the world to be rejected if fewer than this many peaks (based on elevation) are present on the map. EG: elevations of 400 must be possible for mountain peaks to occur. If set to zero, then worlds will not be rejected based on number of peaks.

You may need to adjust elevation parameters, such as the highest weighted range, in order to get the desired number of elevation-400 squares needed for larger numbers of peaks. Like volcanoes, mountain peaks can make embark zones more interesting, but other than that, they don't appear to "do" anything special. Reportedly, they do increase the highest Z-level above ground in all embark zones in the same region, even if the selected embark zone does not include the peak.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PEAK_NUMBER_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[PEAK_NUMBER_MIN:20]</nowiki></tt>
| Elevations of 400 must occur for peaks to form.
|}

=== Minimum Partial Edge Oceans ===

This will cause a world to be rejected unless there are at least this many oceans touching an edge of the map. If set to zero then worlds will not be rejected based on this criterion. Setting both this parameter and Minimum Complete Edge Oceans to values that total more than 4 when added together may cause all worlds to be rejected as you can't have both a partial and complete edge ocean on a given edge.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PARTIAL_OCEAN_EDGE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[PARTIAL_OCEAN_EDGE_MIN:2]</nowiki></tt>
| Maximum of 4
|}

=== Minimum Complete Edge Oceans ===

This will cause a world to be rejected unless there are at least this many oceans which completely cover an edge of the map. Since a square map only has 4 edges, the maximum value possible is 4. If set to zero then worlds will not be rejected based on this criterion but still might end up with complete edge oceans by chance.

Note that the ability for this many edge oceans to exist will be limited by elevation. Therefore, to actually create large oceans you will probably need to change things like the Elevation Mesh Size and Weighted Ranges to increase the number and distribution of very low elevation squares on the map. In addition, if Complete Edge Oceans is set to any value ''other'' than 0 or 4, you may need to lower elevation variance for at least one of the axes: if set too high, such as a variation of 1600 for both X and Y axes (the default for Large Island and Medium Island parameter sets), the game may generate worlds very slowly or even hang.{{bug|565}}

Given appropriate weight, range, and variance values for things like elevation, a setting of: 1 results in a world that seems like a chunk of coastline. One edge of the map will be completely underwater and there will be ocean taking up much of the map on that side (think the east or west coast of the United States, the north coast of Canada, or southern Europe). If your edge ocean happens to pick your world's frozen side, most of it will be glacier.

*2 results in another coastline along with the first one -- the map could end up looking something like Panama if the oceans pick opposite sides of the map.
*3 results in a peninsula, like Florida in the US. There will be oceans surrounding 3 sides of the map, and land touching only one side of the map.
*4 results in one or more island(s) depending on things like elevation variance and weights. Regardless of whether you get one island or multiple islands, the entire map will be surrounded by water.

Unfortunately, there's no easy way to control which oceans end up on which edges, except perhaps setting X/Y variance to different values.

Edge oceans will take up part of the other edges too. For example, a full edge ocean on the east side will have part of the north and south sides underwater, but that does ''not'' add to the ''partial'' edge oceans count.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[COMPLETE_OCEAN_EDGE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[COMPLETE_OCEAN_EDGE_MIN:0]</nowiki></tt>
| Maximum of 4
|}

=== Minimum Volcano Number ===

The game will attempt to place this many volcanoes, but there must be at least this many squares with a volcanism of 100, if there are not the world will be rejected. Therefore, [[Advanced_world_generation#Volcanism|maximum volcanism]] above must be set to 100, and adjusting the [[Advanced_world_generation#Configuration_Tokens_2|volcanism weighted range]] above for 80-100 to a higher value can increase the number of those squares.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[VOLCANO_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[VOLCANO_MIN:15]</nowiki></tt>
| Volcanoes require a volcanism of 100 to occur.
|}

=== Mineral Scarcity ===
Controls the frequency at which minerals occur; setting this value higher will decrease both the number of different types and amounts of ore and gems present on a map. The default value will result in many metal ores, while the old default of ''sparse'' would be only a few ores, which may be limiting until other metals can be requested and traded for.

The options "Very Rare", "Rare", "Sparse", "Frequent", and "Everywhere" in the [[World_generation#Basic_world_generation_menu|basic world generation menu]] use the values 50000, 10000, 2500, 500 and 100 respectively.

According to [http://www.bay12forums.com/smf/index.php?topic=79018.msg2063804#msg2063804 research] by Shandra in v0.31.25, this is the relationship between the value of this setting and the approximate number of gems and ore:

[[File:MineralSetting_v25_limit10k.png]]

This is for the same 8x8 embark region in a world which is otherwise the same, except for the mineral scarcity parameter (although most of the detailed information comes from experiments with previous versions). (The chart legend has an error, the first "Pot.(Types)" should read "Pot.(Amount)".)
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MINERAL_SCARCITY:<number>]</nowiki></tt>
| <tt><nowiki>[MINERAL_SCARCITY:100]</nowiki></tt>
| Range: 100 to 100,000
|}

=== Max Megabeast Caves ===

This is the number of [[megabeast]]s placed at the beginning of history. Megabeasts are [[hydra]]s, [[bronze colossus]]es, [[roc]]s, and [[dragon]]s, which are all placed in equal proportions [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415177#msg3415177 data].

Increasing this value can lead to early extinction of civilizations.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[MEGABEAST_CAP:75]</nowiki></tt>
| Megabeasts count towards BEAST_END_YEAR calculation.
|}

=== Max Semi-Megabeast Caves ===

This is the number of [[semi-megabeast]]s placed at the beginning of history. Semimegabeasts are [[giant]]s, [[ettin]]s, [[minotaur]]s, and [[cyclops]], which are placed in equal proportions [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415188#msg3415188 data].

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEMIMEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SEMIMEGABEAST_CAP:150]</nowiki></tt>
| Semimegabeasts do not count towards the BEAST_END_YEAR calculation.
|}

=== Titan Parameters ===

==== Number ====

This controls the number of [[titan]]s that exist at the beginning of history[http://www.bay12forums.com/smf/index.php?topic=112465.msg3415203#msg3415203 data]. The number of forgotten beasts is unaffected by this parameter [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415155#msg3415155 data].

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TITAN_NUMBER:33]</nowiki></tt>
| Titans count towards BEAST_END_YEAR calculation.
|}

==== Attack Population Requirement ====

[[Titan]]s will begin to attack your fort once at least this many dwarves inhabit it, regardless of whether any other attack criteria have been met.

This number defaults to 80, which isn't usually too difficult to deal with.

==== Exported Wealth Requirement ====

Titans will begin to attack your fort once you have exported at least this many [[Currency|dwarfbucks]]-worth of goods, regardless of whether or not any other criteria have been met. This parameter defaults to None (disabled).

==== Created Wealth Requirement ====

Titans will begin to attack your fort once the fort's total wealth has reached this many [[Currency|dwarfbucks]] in value. This happens regardless of whether any of the other criteria, such as population, have been met; therefore, even with 1 dwarf, a fort could be attacked if the fort were worth at least this value.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_ATTACK_TRIGGER:<population>:<exp wealth>:<created wealth>]</nowiki></tt>
| <tt><nowiki>[TITAN_ATTACK_TRIGGER:80:0:100000]</nowiki></tt>
| 0 = None (disabled). Only one requirement must be met for an attack.
|}

=== Number of Demon Types ===

[[Demon]]s are similar to [[titan]]s and [[forgotten beast]]s, in that they are procedurally generated, but most are not unique. Thus, many different types of demons can exist in the world, but there will also be many individuals of most types. Thanks to [[Underworld spire|certain fun things]], fewer demon types also means fewer goblin civilizations.{{cite forum|112465/7392706}} You need at least 2 demon types, or else goblin civilizations won't exist initially, though if dwarves breach the underworld during world generation, at least one will be generated then.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DEMON_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[DEMON_NUMBER:52]</nowiki></tt>
| 0 to 1000
|}

=== Number of Night Troll Types ===

The number of different [[night troll]]s, also procedurally generated, that will exist in the world. Setting this to zero means that the world will have no night trolls, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[NIGHT_TROLL_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[NIGHT_TROLL_NUMBER:77]</nowiki></tt>
| 0 to 1000
|}

=== Number of Bogeyman Types ===
The number of different [[bogeyman]] forms that will exist in the world. Bogeymen are procedurally generated, though their forms do not vary by much. Setting this to zero means that the world will have no bogeymen, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[BOGEYMAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[BOGEYMAN_NUMBER:27]</nowiki></tt>
| 0 to 1000
|}

=== Number of Nightmare Types ===
The number of different [[nightmare]] forms that will exist in the world. Nightmares are procedurally generated. Setting this to zero means that the world will have no nightmares, custom or otherwise.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[NIGHTMARE_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[NIGHTMARE_NUMBER:27]</nowiki></tt>
| 0 to 1000
|}

=== Number of Vampire Curse Types ===

The number of different types of [[Vampire|vampires]] that will exist in the world. Although they are generated at the start of a new world, they aren't different from each other. Setting this to zero means no vampires will exist.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[VAMPIRE_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[VAMPIRE_NUMBER:72]</nowiki></tt>
| 0 to 1000
|}

=== Werebeast Parameters ===

==== Number of Werebeast Curse Types====

The number of different types of [[werebeast]]s that can exist in the world. It is common for werebeasts, unlike vampires, to assume many different forms and variations, the most well-known of these amount to different species of animals, from lizards, to wolves, to even bears. Setting this to zero means no werebeasts will exist, and will also remove a large amount of [[fun]] from the game.

In vanilla, there are only 82 possible unique werebeast species. Any further species will generate as wereblobs.{{bug|13308}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[WEREBEAST_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[WEREBEAST_NUMBER:58]</nowiki></tt>
| 0 to 1000
|}

==== Attack Population Requirement ====

Werebeasts will begin to attack your fort once at least this many dwarves inhabit it, regardless of whether any other attack criteria have been met. This number defaults to 50 which will often be reached in the second year of the fort.

==== Exported Wealth Requirement ====
Werebeasts will begin to attack your fort once you have exported at least this many [[Currency|dwarfbucks]]-worth of goods, regardless of whether or not any other criteria have been met. This parameter defaults to 5000.

==== Created Wealth Requirement ====

Werebeasts will begin to attack your fort once the fort's total wealth has reached this many [[Currency|dwarfbucks]] in value. This happens regardless of whether any of the other criteria, such as population, have been met; therefore, even with 1 dwarf, a fort could be attacked if the fort were worth at least this value.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[WEREBEAST_ATTACK_TRIGGER:<population>:<exp wealth>:<created wealth>]</nowiki></tt>
| <tt><nowiki>[WEREBEAST_ATTACK_TRIGGER:50:5000:50000]</nowiki></tt>
| 0 = None (disabled). Only one requirement must be met for an attack.
|}

=== Number of Secret Types ===

The number of secrets that exist in the world. Currently, all secrets are secrets of life and death, and the ones holding these secrets are [[necromancer]]s, thus, setting this to zero means that no necromancers will appear.
Non-necromancer towers can still appear (extremely rarely) with zero secrets, constructed by independent undead groups.
The primary difference between having 1 or 1000 secrets is the chance of your world having any necromancer towers at all. With 1, this chance is low. With the default number, it's seemingly guaranteed.
Even with 1 secret, if you have any necromancer towers at all, it is likely a great number will quickly appear in world generation (though this isn't guaranteed).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SECRET_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[SECRET_NUMBER:52]</nowiki></tt>
| 0 to 1000
|}

=== Number of Regional Interaction Types ===

The number of interactions that can be caused in regions, which may incorporate evil rain and cloud types. Currently, only evil region interactions are generated this way.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[REGIONAL_INTERACTION_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[REGIONAL_INTERACTION_NUMBER:20]</nowiki></tt>
| 0 to 1000
|}

=== Number of Disturbance Interaction Types ===
The number of different [[Mummy|disturbed dead]] that can exist in the world. Setting this to zero should prevent any mummy from appearing{{verify}}, but it will not prevent the creation of [[tomb]]s.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DISTURBANCE_INTERACTION_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[DISTURBANCE_INTERACTION_NUMBER:10]</nowiki></tt>
| 0 to 1000
|}

=== Number of Evil Cloud / Evil Rain Types ===

This number specifies how many [[Weather#Evil weather|various face-melting, eye-boiling, and zombifyingly-fun]] clouds of pure evil may appear in your world. Setting this to zero means you no longer will ever have to deal with encroaching dust walls of doom in that world. It is generally advised to keep this value low...

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EVIL_CLOUD_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[EVIL_CLOUD_NUMBER:45]</nowiki></tt>
| 0 to 1000
|}

The latter number states how many different types of green-ooze drenchers, disconcerting blood-showers, and sickly yellow slime-baths can occur in your world. Compared to evil clouds though, this one hardly is worth stressing out about, usually.... Setting this to zero means the only semi-solid to fully-liquid fluids to fall from the sky will be pure H2O.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EVIL_RAIN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[EVIL_RAIN_NUMBER:352]</nowiki></tt>
| 0 to 1000
|}

=== Generate Divine Materials ===
This turns the generation of [[Divine_metal|divine metals]] on or off. It does not influence the creation of [[vault]]s. Probably determines whenever or not using divination dice spawns weapons.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GENERATE_DIVINE_MATERIALS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[GENERATE_DIVINE_MATERIALS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Generate Mythical Materials ===

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GENERATE_MYTHICAL_MATERIALS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[GENERATE_MYTHICAL_MATERIALS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Mythical Healing ===

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALLOW_MYTHICAL_HEALING:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_MYTHICAL_HEALING:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Divination, Experiments, and Necromancy types ===
These allow or disallow [[die|divination]], demon or necromancer [[experiment]]s, and the more advanced [[necromancer]] abilities.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALLOW_DIVINATION:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_DIVINATION:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_DEMONIC_EXPERIMENTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_DEMONIC_EXPERIMENTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_EXPERIMENTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_EXPERIMENTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_LIEUTENANTS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_LIEUTENANTS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_GHOULS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_GHOULS:1]</nowiki></tt>
| 1/0 = Yes/No
|-
| <tt><nowiki>[ALLOW_NECROMANCER_SUMMONS:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALLOW_NECROMANCER_SUMMONS:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Desired Good/Evil Square Counts ===

These values change the amount of [[Surroundings#Good|good or evil]] tiles on the map, depending on the size of the region they are being considered for. The counts are for all tiles in all subregions of a given size considered together, ''not'' counts for each subregion considered separately (all tiles in the same subregion share the same [[surroundings]] values).

As used here, a "subregion" is a named world area. Subregion names and locations for a generated world are viewable in legends mode under "Regions". Subregions are classified by size the same way for all map sizes: 1-24 tiles is Small, 25-99 tiles is Medium, and 100+ tiles is Large.

The counts used here will always be restricted to regions of the given size, no matter how large the count. Also, the count is more of a goal than a minimum or maximum. As a result, you can end up with many more or many fewer than the requested number of squares in some situations. In particular, if you have something like a case where only 3 large regions exist in a world, and you request "1 evil square" in large regions, you will end up with one of the large regions being ''entirely evil''. So any non-zero value in one of these settings essentially means "force at least one region of this size to be all good/evil."

Note that the "evilness" of evil biomes is also impacted by savagery. Certain civilizations cannot exist in good and/or evil squares, so too many of one or the other may limit the size of certain types of civilizations - dwarves, for example, need non-aligned biomes. Creating too many evil biomes seems to lead to the danger of many civilizations' early extinction.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[GOOD_SQ_COUNTS::<med region>:<lg region>]</nowiki></tt>
| <tt><nowiki>[GOOD_SQ_COUNTS:100:1000:2000]</nowiki></tt>
| rowspan="2" | Set count to zero to disable for that region size.
|-
| <tt><nowiki>[EVIL_SQ_COUNTS::<med region>:<lg region>]</nowiki></tt>
| <tt><nowiki>[EVIL_SQ_COUNTS:100:1000:2000]</nowiki></tt>
|}

=== Minimum Biome Square Counts ===

These numbers control whether or not a world will be rejected based on a lack of different [[biome|biomes]]. Raising these numbers will '''not''' automatically generate the given number of squares of the given biome! For a biome to exist, certain conditions like elevation and rainfall must exist.

These parameters simply filter out worlds that (for example) randomly fail to have enough high elevation squares to support a given number of mountains, etc. Some settings may cause worlds to always be rejected. For example, if for some reason the maximum elevation parameter is set to a value below what will support mountain biomes, it will be impossible to satisfy a non-zero requirement for mountain squares. The same principle goes for other conditions and biomes such as low elevations and oceans, etc.

Certain civilizations require different biomes to exist (such as dwarves and mountains), so eliminating certain biomes will make it impossible for certain civilizations to form.

These parameters often result in infinite world rejection problems. See [[World rejection]] for information on solving problems related to worlds always being rejected due to one or more of these parameters.

0 means no minimum for rejection - setting it to 0 does not guarantee 0 squares of that biome.

==== Biome Type Requirement Table ====

Terrain requirements for various biomes are described below.{{Verify}} Note that some of the exact ranges are unknown.

{| {{prettytable}}
|- bgcolor="#dddddd"
! rowspan="2" | Biome
! colspan="4" | Terrain Requirement
|-
! Elevation
! Rainfall
! Temperature
! Drainage
|-
| Swamp/Marsh
| 100-299
| 33-100
| Non-Freezing
| 0-32
|-
| Desert/Badland
| 100-299
| 0-9
| non-freezing
| note1
|-
| Forest
| 100-299
| 66-100
| non-freezing
| 66-100
|-
| Mountains
| 300-400
| N/A
| N/A
| N/A
|-
| Ocean
| 0-99
| N/A
| N/A
| N/A
|-
| Glacier
| 100-299
| N/A
| Freezing
| 80(?)-100
|-
| Tundra
| 100-299
| N/A
| Freezing
| 0-66
|-
| Grassland
| 100-299
| 0-66
| Non-Freezing
| 0-66
|-
| Hills
| 100-299
| 0-66
| Non-Freezing
| 66-100
|}
note1 drainage: 00-32 sand desert, 33-49 rocky wasteland, 50-65 rocky wasteland but different characters/appearance, 66-100 badlands

==== Minimum Initial Square Count ====

'''Note: The exclusive purpose of these parameters is to cause world rejection.'''

This is the minimum number of squares of the given biome that must exist before things like erosion take place. One thing to keep in mind is the maximum number of squares on a map of a given size - if the total number of squares on a map is lower than the sum of all square count parameters, then you will get infinite world rejection.

To determine the number of squares on a map, just multiply the dimensions. In practice these parameters will need to sum to lower than the maximum because some space is needed for "slack".

{| {{prettytable}}
|- bgcolor="#dddddd"
! Map Size
! Number of Squares
|-
| 17×17
| 289
|-
| 33×33
| 1089
|-
| 65×65
| 4225
|-
| 129×129
| 16614
|-
| 257×257
| 66049
|}

==== Minimum Initial Region Count ====

This is the minimum number of regions of contiguous biome squares that must exist before other processes such as erosion take place.

==== Minimum Final Region Count ====

This many regions of the given biome must exist after erosion and similar phases of generation have been completed.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[REGION_COUNTS:SWAMP:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:SWAMP:1032:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:DESERT:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:DESERT:1032:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:FOREST:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:FOREST:4128:13:12]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:MOUNTAINS:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:MOUNTAINS:8256:9:9]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:OCEAN:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:OCEAN:8256:7:6]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:GLACIER:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:GLACIER:0:0:0]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:TUNDRA:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:TUNDRA:0:0:0]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:GRASSLAND:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:GRASSLAND:8256:13:12]</nowiki></tt>
|-
| <tt><nowiki>[REGION_COUNTS:HILLS:<init sq>:<init rg>:<final rg>]</nowiki></tt>
| <tt><nowiki>[REGION_COUNTS:HILLS:8256:13:12]</nowiki></tt>
|}

=== Erosion Cycle Count ===

Tells the world generator how long the world has to erode its tall peaks down to mountainsides during the 'running rivers...' stage of world creation. The higher this number, the less jagged the world will be, and the more wide the major rivers will be. If you use the maximum number, your mountains will dissolve before your eyes into plains which can lead to rejections if there aren't enough mountains to use for river start points and dwarven civilization origin points.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EROSION_CYCLE_COUNT:<number>]</nowiki></tt>
| <tt><nowiki>[EROSION_CYCLE_COUNT:250]</nowiki></tt>
| Range: 0 to 1000
|}

=== Minimum/Desired River Start Locations ===

This is the minimum number of riverheads that must exist before and after erosion takes place. Worlds will be rejected if they fail to meet these numbers. As with minimum biome counts, raising this number doesn't automatically create this many riverheads. Other conditions like terrain and rainfall must exist for rivers to form.

Extremely high pre-erosion values speed erosion greatly, while low post erosion values are useful for limiting rejects due to lack of river origin points. One can try the 800 value to get more lakes.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[RIVER_MINS:<min pre-erosion>:<des post-erosion>]</nowiki></tt>
| <tt><nowiki>[RIVER_MINS:200:400]</nowiki></tt>
| Range: 0 to 800
|}

=== Periodically Erode Extreme Cliffs ===

If enabled, makes every impassable rock wall into a series of ramps. Some prefer to pump up erosion to about 250, and turn the "Desired pre-erosion river count" to 0 for good erosion and no extra canyons.

Normally this is set to Yes (1).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PERIODICALLY_ERODE_EXTREMES:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[PERIODICALLY_ERODE_EXTREMES:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Do Orographic Precipitation and Rain Shadows ===

Toggle that allows terrain height to affect rainfall. For example, moist air coming from the ocean blows over the land. As the terrain gets higher, it forces the moist air up, causing it to rain on the seaward side of a mountain. Eventually, all the rain has fallen if the mountain is tall enough. So, when the breeze goes over the top, there's no moisture left to fall on the other side, creating a rain-shadow. In the current version, regions where drainage is above 50 will also create rain shadows, regardless of the underlying biome and elevation.{{cite forum|140685/5484064}}

Turning this on should create a tendency for more extreme rainfall in regions, creating more forests, deserts, marshlands, and grasslands. Also note that it can create rainfall outside of min-max rainfall settings, so even in a world with a 0 max rainfall you may get rainfall biomes. Turning it off should result in more controllable, less complex rainfall conditions based on rainfall parameters as it adds a random element which can distort or otherwise mess up the climates on a pregenerated map.

This should be disabled if you're importing a map or using a preset map file that has weather.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[OROGRAPHIC_PRECIPITATION:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[OROGRAPHIC_PRECIPITATION:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Maximum Number of Subregions ===

This is the number of separate biomes (the flashing regions you see on embark when you hit F1, F2, etc. when there's more than one biome on the embark location) that are allowed to exist on the entire map.

Setting this to very low values will result in numerous rejections depending on [[#X and Y Variance|variance parameters]]. If variance values are set to high numbers, many small biomes will be created causing rejection if this parameter value is not increased beyond the default.

Increasing the value of this tag is often a must when generating "patchwork" worlds with lots of biome variance, but simply increasing it without increasing variance parameters will not guarantee more biomes.

It is also interesting to note that the maximum subregions is 5000 which is more than the total number of squares for a pocket or small map. However, for a medium or large map (16641 or 66049 squares) it quickly becomes a mere fraction of the total number of possible subregions. In fact it would be quite easy on a large map to end up with far too many subregions and get endless rejections of this type.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SUBREGION_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[SUBREGION_MAX:2750]</nowiki></tt>
| Range: 1 to 5000
|}

=== Cavern Parameters ===
[[Caverns]] are the hollow areas underground, which dwarves tend to encounter when they're digging around. The '''Cavern Layer Number''' parameter determines how many cavern systems will be generated, not including the magma layer or the Bottom layer. Defaults to three - setting it to lower values could help FPS. Setting it to 2 will merge cavern 3 species into the 2nd cavern, and setting it to 1 will merge all into one cavern. However, disabling them entirely by setting it to 0 will make it impossible to grow any underground plants, as none will exist for your civilization to cultivate, nor will they be available on embark.

*Setting caverns to a sub-3 number (Spoiler, highlight to view) erases about one-third of HFS spires{{Bug|10267}} and prevents dig deep disasters. Additionally, random plant or animal species can be more frequently absent.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_COUNT:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_COUNT:3]</nowiki></tt>
| Range: 0 to 3
|}

==== Cavern Layout Parameters ====

Open caverns and dense passageways are not mutually exclusive. When both are raised, bizarre results can occur, such as layers showing a combination of open caverns, a cluster of network passages, and natural walls sprinkling the inside of an otherwise open cavern. [http://www.bay12forums.com/smf/index.php?topic=76355.msg1936859#msg1936859 Reference]

If you want the largest open spaces possible, then decrease the density and increase the openness. If you want a labyrinth of passageways, lower the openness and raise the passage density.

Another interesting note about the cavern layers is that the seed and number of demon types affect the layout of the caverns.

<gallery widths=200 heights=200 perrow=2>
File:Open00Density100.jpg|Cavern slice with Openness of 0 and Density of 100
File:Open100Density00.jpg|Cavern slice with Openness of 100 and Density of 0
File:Open100Density100.jpg|Cavern slice with Openness of 100 and Density of 100
File:Open50Density50.jpg|Cavern slice with Openness of 50 and Density of 50
</gallery>

===== Layer Openness min/max =====

Dictates the size of cavern passages. When Passage Density (see below) is set to minimum (0), caverns will be open expanses. Raising the maximum will increase the size of the caverns.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_OPENNESS_MAX:100]</nowiki></tt>
|}

===== Layer Passage Density min/max =====

Determines how many passages form the cavern. If openness (see above) is set to minimum and density increased, then you will get a maze-like network of small criss-crossing passages. Raising the values further increases the number of the maze-like passages.

Caverns will be large, open spaces at 0, and comprised of many small vertical shafts of rock at 100. Setting both values to be the same results in a uniform look for the caverns.{{Verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_PASSAGE_DENSITY_MAX:100]</nowiki></tt>
|}

===== Layer Water min/max =====

Determines the minimum and maximum percentage of water each cavern can contain.

Caverns with a water level of 10 or higher can support creatures and plants from the "Subterranean Water" biome, and caverns with a water level of 90 or lower can support the "Subterranean Chasm" biome; levels of 10-90 support ''both'' biomes, while levels below 10 or above 90 support only one.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVERN_LAYER_WATER_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_WATER_MIN:0]</nowiki></tt>
| rowspan="2" | Range: 0 to 100
|-
| <tt><nowiki>[CAVERN_LAYER_WATER_MAX:<number>]</nowiki></tt>
| <tt><nowiki>[CAVERN_LAYER_WATER_MAX:100]</nowiki></tt>
|}

==== Magma Layer ====

This parameter controls whether the [[magma sea]] exists.

Setting 1/Yes causes the magma layer to exist, value 0/No prevents it. Appears not to have any impact on volcanoes nor volcanism, so even if 0/No, there will still be embark locations with magma. If a [[volcano]] exists, it appears to always tap the magma sea, but the magma sea will not be revealed by revealing the volcano.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[HAVE_BOTTOM_LAYER_1:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[HAVE_BOTTOM_LAYER_1:1]</nowiki></tt>
|}

==== Bottom Layer ====

Determines if the space below the magma sea exists. If Yes the "HFS" layer is always present. Normally you want to leave this set to Yes for maximum fun.

If enabled, this will force the magma layer above it.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
|-
| <tt><nowiki>[HAVE_BOTTOM_LAYER_2:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[HAVE_BOTTOM_LAYER_2:1]</nowiki></tt>
|}

=== Z Levels (Depth) Settings ===

These parameters control the "thickness" of various "layers" on the map. Note that a "layer" in this case does not refer to one Z-level, but refers to a number of related Z-levels such as "levels above ground".

The following table assumes that you have 3 cavern layers. (out of a minimum of 0-3) The Levels Above Layer settings control how many Z-Levels are above each layer. A layer may itself consist of multiple Z-Levels (and almost always does).

{|style="margin:1em 1em 1em 0;background:#F9F9F9;border:1px #AAA solid;border-collapse:collapse;" class="wikitable"
|-style="background:#F2F2F2;text-align:center;"
!style="border:1px #AAA solid;padding:0.2em;" width="120"|Setting Name
!style="border:1px #AAA solid;padding:0.2em;" width="200"|Token
!style="border:1px #AAA solid;padding:0.2em;"| Description
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Ground
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_GROUND:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| The number of Z-levels of air above the highest surface level. Has no impact on how many Z-levels deep the surface layer is.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above layer 1
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_1:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of stone above the first cavern layer. Making this higher will guarantee ''at least'' that many levels to build your fortress, but will have no impact on how many z-levels thick the surface layer is. Also, the top of a cavern may be higher than the rest of a cavern, so in practice there will be more "solid" levels than this above the cavern.
As of version 0.31.25 this setting is inaccurate. The actual number of z-levels may vary in a range of approx. ±5, which may result in non-existence of any solid z-levels between a surface layer and first cavern layer.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 2
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_2:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very top of the second cavern and the very bottom of the first cavern.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 3
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_3:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very top of the third cavern and the very bottom of the second cavern.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 4
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_4:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Z-levels of earth between the very highest magma and the very bottom of the third cavern. Spoiler Hidden (select invisible text to read): Making this high will give a large area for HFS veins, so that it never touches caverns, giving more to mine '''if''' it was impacting the cavern previously.
|-
|style="border:1px #AAA solid;padding:0.2em;"| Above Layer 5
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_ABOVE_LAYER_5:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Uncertain. May control the number of levels of "Semi Molten Rock" between HFS and Magma, may control number of levels of magma, may impact both. In experimentation, the overall depth of all magma sea and semi-molten rock levels appears to increase, but not consistent enough to say for certain. Only valid if Magma Layer present. Spoiler Hidden:Often the HFS vein will only extend as high as the highest magma, making this the only guaranteed way to increase amount of HFS to mine, but unfortunately also creating enormous useless semi-molten z-levels
|-
|style="border:1px #AAA solid;padding:0.2em;"| At Bottom
|style="border:1px #AAA solid;padding:0.2em;"| <nowiki>[LEVELS_AT_BOTTOM:<number>]</nowiki>
|style="border:1px #AAA solid;padding:0.2em;"| Appears to be number of levels of HFS chamber. Only valid if Bottom Layer present, often having no impact. Values larger than default result in strange things.
|}

Some implications:
* The number of surface layers (e.g. soil), at this time, cannot be controlled. For example, on a map with 1 layer of peat, then a layer of silt, then a layer of obsidian, there is no control to let you increase either one to be, say, 20 z-levels. (though you may get lucky with the obsidian).
* There can be multiple stone layers between the cavern and the surface, so, increasing Levels Above Layer 1 may give you more conglomerate or more granite, and you have no control over which stone layer spans those Z-levels.
* The layers shown on embark span across the cavern layers in an unknown and inconsistent way. Sometimes those 10 different layers of stone are evenly distributed over your 400 z-level deep map, sometimes the first 9 get 1 z-level each and the last gets the other 391 levels. No way to control found yet.
* The HFS chamber, if present, will always extend into the rock layers, and appears to always make contact with the bottom cave. Large values for levels above layer 5 and layer 4 can result in enormous chambers, but the number of levels at the top (the part with undead) appears to be unaffected.
* Unconfirmed whether number of levels between caverns has any impact on cavern height. There will be connecting ramps and/or shafts between cavern layers no matter how many levels are between them.
* '''Very Important''': These values appear to apply across a whole 16x16 region, not just embark areas. That means that if a 16x16 region is completely flat, but has one tall mountain in one far corner, even if you set Levels Above Ground low (e.g. 2 z-levels) you still have all the empty air of the highest mountain in every embark tile (e.g. 200 z-levels). Also can happen to the semi-molten layer, and can lead to unexpected behavior.
* Very large or small values can cause strange things to happen.

=== Minimum/Maximum Natural Cave Size ===
It's not clear what effect these currently have, other than changing them can change the location of caves somewhat.{{verify}}

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[CAVE_MIN_SIZE:<number>]</nowiki></tt>
| <tt><nowiki>[CAVE_MIN_SIZE:5]</nowiki></tt>
| rowspan="2" | Range: 1 to 500
|-
| <tt><nowiki>[CAVE_MAX_SIZE:<number>]</nowiki></tt>
| <tt><nowiki>[CAVE_MAX_SIZE:25]</nowiki></tt>
|}

=== Number of Caves ===
The number of caves generated in mountainous and non-mountainous regions, mountain caves will always be generated on the edge of mountain ranges next to non-mountainous regions. Lurking [[kobold]]s set up shop in caves, and store their stolen items there - a setting of 0 in both will stop kobold civilizations from appearing. Special note: a cave is not initially a [[lair]], although beasts can later use them as their lair.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[MOUNTAIN_CAVE_MIN:100]</nowiki></tt>
| rowspan="2" | Range: 0 to 800
|-
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:200]</nowiki></tt>
|}

=== Number of Mythical Sites ===
The number of [[mysterious dungeon|mysterious sites]] generated around the world. The extended effects of setting this to 0 has not been determined{{verify|is chosen still available? is quest still given? etc.}}.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MYTHICAL_SITE_NUM:<number>]</nowiki></tt>
| <tt><nowiki>[MYTHICAL_SITE_NUM:200]</nowiki></tt>
| rowspan="2" | Range: 0 to 800
|}

=== Make Caves Visible ===
If set to no (default) then the location of caves will not be marked on the map. If set to yes, caves will appear on the map so that they may be sought out or avoided as desired.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ALL_CAVES_VISIBLE:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[ALL_CAVES_VISIBLE:0]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Allow Init Options to Show Tunnels ===

If enabled, you will be able to see the underground tunnels often built by dwarves on the world map, and they will appear as black lines, similar to roads.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SHOW_EMBARK_TUNNEL:<0-2>]</nowiki></tt>
| <tt><nowiki>[SHOW_EMBARK_TUNNEL:2]</nowiki></tt>
| 0 = No 1 = Only in Finder 2 = Always
|}

=== Number of Civilizations ===

This number of [[civilization]]s will be placed on the map before history generation begins. These civilizations may later die out due to historical events. It is noteworthy that the chance for any given civilization to be destroyed through megabeasts decreases with a higher total number of civilizations present[http://www.bay12forums.com/smf/index.php?PHPSESSID=7348f68f41a9659443c05b2acf534e6c&topic=112465.15 data]. The five races are dwarf, elf, human, goblin, and kobold; they will generally be placed in equal numbers until the quota has been reached. If there are not enough biomes or other worldgen prerequisites for an even distribution, certain civs will be much more or less frequent than others[http://www.bay12forums.com/smf/index.php?PHPSESSID=7348f68f41a9659443c05b2acf534e6c&topic=112465.15 data]. If there is an odd number of civs (not divisible by 5), then the remainder is distributed randomly. Kobold civs require caves to be placed; if no caves exist, then kobolds are skipped and will not appear. This does not cause rejections [http://www.bay12forums.com/smf/index.php?topic=112465.msg3415125#msg3415125 data]. Goblin civilizations require multiple demons, see the [[#Number_of_Demon_Types|number of demon types]] section above.

Note that a high value here can cause lots of map rejections, particularly on smaller maps as there simply isn't enough room or regions to put them all in.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_NUMBER:40]</nowiki></tt>
| Range: 0 to 300
|}

=== Playable Civilization Required ===

If this is set to yes (default) then worlds will be rejected if no civilization with [[Entity token|CIV_CONTROLLABLE]] can be placed. In an unmodded game, only the dwarves have this token.

If set to no, the result may be a world that cannot be played in Fortress Mode.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[PLAYABLE_CIVILIZATION_REQUIRED:<1 or 0>]</nowiki></tt>
| <tt><nowiki>[PLAYABLE_CIVILIZATION_REQUIRED:1]</nowiki></tt>
| 1/0 = Yes/No
|}

=== Minimum Number of Mid/Low/High Characteristic Squares ===

Sets the minimum possible number of squares of certain ranges of each of the region qualities, such as elevation, rain, drainage, volcanism, savagery, and temperature. These need to be changed to reflect your regional meshes and weights, and are responsible for a HUGE number of map rejections. These values can all be set to 0 for much fewer map rejections, particularly in the case of more wacky, non-standard maps.

These values will cause worlds to be rejected unless at least the given number of squares of the given type are randomly generated. Setting these values too high could result in worlds always being rejected if other parameters such as the maximum/minimums for elevation, etc., don't allow enough of those squares to get generated.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[ELEVATION_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[ELEVATION_RANGES:8256:16512:8256]</nowiki></tt>
| rowspan="5" | Minimum number of squares that must have low, medium, and high amounts of the given attribute. 
0 = No minimum
|-
| <tt><nowiki>[RAIN_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[RAIN_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[DRAINAGE_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[SAVAGERY_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY_RANGES:8256:16512:8256]</nowiki></tt>
|-
| <tt><nowiki>[VOLCANISM_RANGES:<low sq>:<mid sq>:<high sq>]</nowiki></tt>
| <tt><nowiki>[VOLCANISM_RANGES:8256:16512:8256]</nowiki></tt>
|}

==World rejection==

:''Main article: [[World rejection]]''

If you are having the common problem of generated worlds always being rejected by the world generator, see [[v0.31:World rejection|Solving World Rejection Problems (v0.31 page)]] as it contains many detailed suggestions on how to troubleshoot and solve these issues.

== Parameter set examples ==

If you're trying to do something specific, then the [[Worldgen examples]] - complete parameter sets that can be copied directly into your ''world_gen.txt'' file and customized as desired - might be helpful.
If none of the examples suit your needs, [[Worldgen tricks]] has strategies and tips on making a world just right for you.

For many, many more examples see:
* [http://www.bay12forums.com/smf/index.php?topic=101280 DF2012 (v0.34) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=140180 DF2014 (v0.40) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=168543.0 DF2014 (v0.44.02+) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=175538 DF2014 (v0.47.01+) WorldGen "Cookbook" Thread]
* [http://www.bay12forums.com/smf/index.php?topic=180805.0 DF2022 (v0.50.01+) WorldGen "Cookbook" Thread]

{{World}}

Difficulty

2026-03-07T07:02:29Z

Ziusudra: /* Siege invaders */ used Toady's own words (which I think are easier to follow) and added cite forum template

{{Quality|Superior}}
{{av}}

'''Difficulty''' is the level of challenge presented by the game in [[Fortress Mode]], largely customizable by the player. These [[settings]] will affect whether your fortress can be attacked by outside forces, how frequent said attacks are, how big invading armies are, [[noble]] neediness, etc. You can modify these settings before and at any time after embarking, the tab will only appear in the settings screen when a [[fortress]] is loaded. Since they are specific to each save, they are stored as part of the save and are not editable outside the game.

== Default settings ==
They are divided into two groups: enemies and economy; enemies can be disabled, both groups have normal and hard presets, and all of the individual settings can be adjusted in Custom settings. The values used in each preset can be seen by selecting the preset and then viewing them in Custom settings.

'''Enemies''' has 3 options:
* '''Off''' will disable [[Ambush|ambushes]], [[Siege|sieges]], [[Megabeast|uninvited]] [[Forgotten beast|guests]], [[Werebeast|werebeasts]], and agitated wildlife attacks, but not [[intrigue]], [[HFS]], or misbehaving dwarves, so it is still recommended to train a military.
* '''Normal''' is the standard ''Dwarf Fortress'' experience.
* '''Hard''' ensures a never-ending stream of [[Fun]], causing invaders to show up earlier, more often, and with more bodies to throw at the gates.
----
'''Economy''' has 2 options:
* '''Normal''' is the standard ''Dwarf Fortress'' economy.
* '''Hard''' requires you to produce more wealth in order to receive higher-ranking nobles, requires [[Temple|temples]] and [[Guildhall|guildhalls]] to be more valuable before satisfying petitions, and causes [[Noble|nobles]] to make more [[Mandate|mandates]] and [[Demand|demands]].

== Enemy settings ==

If you wish, you can also fine-tune individual settings - maybe you only want megabeasts to assault your fortress, and would prefer the elves to leave well enough alone. The following options are available for enemy settings:
=== Individual enemy toggles ===
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Off; Normal; Hard)
|-
| Civilizations can attack || Yes/No || Controls whether [[Ambush|ambushes]] and [[Siege|sieges]] can occur. || No; Yes; Yes
|-
| Megabeasts can attack || Yes/No || Controls whether [[Megabeast|megabeasts]] and [[Forgotten beast|forgotten beasts]] can attack. || No; Yes; Yes
|-
| Werebeasts can attack || Yes/No || Controls whether [[Werebeast|werebeasts]] can attack. || No; Yes; Yes
|-
| Curious wilderness creatures can come to cause trouble || Yes/No || Controls whether agitated animals can assault your fortress, and whether animals will spawn with the intent to steal items. || No; Yes; Yes
|}
=== Enemy civilization triggers ===
In the base game, these might only affect goblins{{verify}} and all the default civilizations only use the third population trigger.
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Off; Normal; Hard)
|-
| Enemy population triggers || 1 to 300 || Sets the population values for each level of {{token|PROGRESS_TRIGGER_POP_SIEGE|entity}}; hostile civilizations might begin sending sieges after a player fortress reaches this many population. || 0/0/0/0/0; 20/50/80/110/140; 15/30/40/55/70
|-
| Enemy production triggers || 0 to 100,000,000 || Sets the created [[Status#Fortress_wealth|wealth]] values for each level of {{token|PROGRESS_TRIGGER_PROD_SIEGE|entity}}; hostile civilizations might begin sending sieges after a player fortress has created various stuff worth this much in total. || 0/0/0/0/0; 5,000/25,000/100,000/200,000/300,000; 2,500/12,500/50,000/100,000/150,000
|-
| Enemy trade triggers || 0 to 100,000,000 || Sets the exported wealth values for each level of {{token|PROGRESS_TRIGGER_TRADE_SIEGE|entity}}; hostile civilizations might begin sending sieges after a player fortress has exported various stuff worth this much in total. || 0/0/0/0/0; 500/2,500/10,000/20,000/30,000; 250/1,250/5,000/10,000/15,000
|}

=== Megabeasts ===
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Off; Normal; Hard)
|-
| Megabeast attack period (seasons) || 0 to 100 || How many seasons must pass before a megabeast may attack your fortress.{{verify}} || 10; 10; 8
|}
=== Forgotten beasts ===
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Off; Normal; Hard)
|-
| Forgotten beast sensitivity || 1 to 100,000 || Performing nature-disrupting actions within the caverns will agitate forgotten beasts and may cause them to attack. [[Noise]] will also increase agitation. A smaller value will require less actions before the maximum attack chance is reached. || 10,000; 10,000; 10,000
|-
| Forgotten beast irritation minimum || 1 to 100,000 || If the hidden agitation counter is at this value or below, no forgotten beasts will attack. || 5,000; 5,000; 2,000
|-
| Forgotten beast wealth divisor || 1 to 100,000 || Your current fortress wealth is divided by this number - the result is added to effective irritation to determine forgotten beast attacks. A smaller number will cause forgotten beasts to attack sooner. || 40; 40; 40
|}
=== Wilderness irritation ===
These only apply to fortresses with an embark area that includes [[savage]]ry.
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Off; Normal; Hard)
|-
| Wilderness sensitivity || 1 to 100,000 || Performing nature-disrupting actions such as cutting down trees will agitate wildlife and may cause them to attack. A smaller value will require less actions before the maximum attack chance is reached. || 10,000; 10,000; 10,000
|-
| Wilderness irritation minimum || 1 to 100,000 || If the hidden agitation counter is at this value or below, no agitated wildlife will spawn. || 2,000; 2,000; 0
|-
| Wilderness irritation decay || 0 to 100,000 || Causes wildlife to be less irritated after every year. A higher value will make them less irritated faster. || 500; 500; 100
|}

=== Werebeasts ===
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Off; Normal; Hard)
|-
| Werebeast attack period (seasons) || 0 to 100 || How many seasons must pass before a werebeast may attack your fortress.{{verify}} || 10; 10; 8
|}
=== Vampires ===
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Off; Normal; Hard)
|-
| Vampire migrant fraction || 1 to 1,000 || Affects what percentage of new migrants will be [[Vampire|vampires]]. A value of 0 will disable vampiric migrants. (Only on '''Off''' difficulty) || 0; 100; 75
|}
=== Invasion caps ===
These were changed as part of the siege update.{{v|53.07}}
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Off; Normal; Hard)
|-
| Invasion creature cap (excluding mounts) || 0 to 5,000 || The maximum amount of enemies that can be thrown at you when a civilization sieges you, not counting mounts. || 0; 140; 140
|-
| Invasion difficulties || 0 to 30,000 || Strength of the consecutive sieging forces {{verify|equipment materials, creature types?}}, each siege after the third increasing in difficulty by the fourth value.{{verify}} Tracked per civilization per fortress{{cite forum|183066/8606428}}. || 0/0/0/0; 50/300/1000/500; 100/600/1500/750
|}

=== Raids ===
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Off; Normal; Hard)
|-
| Minimum raids before first siege (per civ) || 0 to 500 || Affects how many [[Ambush|ambushes]] must be performed before a civilization can try a proper siege for the first time. || 0; 2; 2
|-
| Minimum raids between sieges (per civ) || 0 to 500 || Affects how many ambushes must be performed before a civilization can try a proper siege from the second time onwards. || 0; 3; 1
|-
| Siege frequency (percentage, otherwise raid) || 0 to 100 || Percentage chance to receive a siege instead of an ambush. || 0; 25; 50
|}
=== Cavern dwellers ===
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Off; Normal; Hard)
|-
| Cavern dweller scale (increase per attack) || 0 to 100 || Every time cavern-dwellers attack your fortress, the maximum number of attackers increases by this number. || 0; 10; 20
|-
| Cavern dweller maximum attackers || 0 to 500 || The maximum amount of enemies that can be thrown at you when cavern dwellers attack. || 0; 50; 75
|}
=== Tree quota ===
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Off; Normal; Hard)
|-
| Diplomacy tree-fell count || 1 to 1000 || Affects the default amount of trees [[Elf|elven]] diplomats will request you limit your felling to. Your negotiator will still try and increase the tree limit. || 25; 25; 10
|-
| Diplomacy tree-fell count (untamed wilds) || 1 to 1000 || Affects the default amount of trees elven diplomats will request you limit your felling to if you've settled in a [[savage]] area instead. Your negotiator will still try and increase the tree limit. || 5; 5; 1
|}
=== Siege invaders ===
These were all added with the [[release information/53.01|siege update]].{{version|53.01}} The aversion values are multipliers for pathing cost; for instance, an aversion to deconstruction of 20 means they would just as soon deconstruct 5 tiles as dig 2 natural tiles (as walk 100 steps), because each of those has the same cost (5×20 = 2×50 = 1×100). The material is not used in this calculation, only whether the tile must be deconstructed or dug through.{{cite forum|183066/8606428}}

==== Invader ability toggles ====
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Off; Normal; Hard)
|-
| Break constructed walls || Yes/No || Reinforced walls take longer to break. Speed and aversion can be adjusted, see below. || No; Yes; Yes
|-
| Dig natural walls || Yes/No || Trolls can now come with great picks. Delay, speed, and aversion can be adjusted, see below. || No; Yes; Yes
|-
| Build floors and stairs || Yes/No || Speed and aversion can be adjusted, see below. || No; Yes; Yes
|-
| Free creatures from cages || Yes/No || Is this only cage traps? Or does it include built cages and/or stockpiled cages? || No; Yes; Yes
|}
==== Invader deconstruction ====
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Off; Normal; Hard)
|-
| Speed || 1 to 1000 || The base rate of deconstruction, smaller is slower, reinforced walls take even longer to break. || 10; 50; 100
|-
| Aversion || 1 to 1000 || How likely they are to try deconstruction, smaller is more likely to try. || 20; 20; 20
|}
==== Invader digging ====
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Off; Normal; Hard)
|-
| Speed || 1 to 1000 || The base rate of digging, smaller is slower. || 10; 50; 100
|-
| Horizontal aversion || 1 to 1000 || How likely they are to try digging on the same z-level, smaller is more likely to try. || 50; 50; 50
|-
| Vertical aversion || 1 to 1000 || How likely they are to try digging to a different z-level, smaller is more likely to try. || 1,000; 1,000; 1,000
|-
| Days to delay vertical digging || 1 to 10,000 || Is this before the first try, or before each try? Does it reset each siege? || 84; 84; 84
|}
==== Invader construction ====
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Off; Normal; Hard)
|-
| Speed || 1 to 1000 || The base rate of construction, smaller is slower, reinforced walls take even longer to break. || 10; 50; 100
|-
| Aversion || 1 to 1000 || How likely they are to try construction, smaller is more likely to try. || 5; 5; 5
|}
==== Invader death aversion ====
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Off; Normal; Hard)
|-
| One death || 1 to 1000 || How strongly one death in a location will deter future activity there. || 0; 0; 0
|-
| Two deaths || 1 to 1000 || How strongly two deaths in a location will deter future activity there. || 0; 0; 0
|-
| Three deaths || 1 to 1000 || How strongly three deaths in a location will deter future activity there. || 0; 0; 0
|-
| Four deaths || 1 to 1000 || How strongly four deaths in a location will deter future activity there. || 0; 0; 0
|-
| Five deaths || 1 to 1000 || How strongly five deaths in a location will deter future activity there. || 5; 5; 5
|-
| Six deaths || 1 to 1000 || How strongly six deaths in a location will deter future activity there. || 6; 6; 6
|-
| Seven deaths || 1 to 1000 || How strongly seven deaths in a location will deter future activity there. || 8; 8; 8
|-
| Eight deaths || 1 to 1000 || How strongly eight deaths in a location will deter future activity there. || 10; 10; 10
|-
| Nine deaths || 1 to 1000 || How strongly nine deaths in a location will deter future activity there. || 20; 20; 20
|-
| Ten or more deaths || 1 to 1000 || How strongly more than 9 deaths in a location will deter future activity there. || 100; 100; 100
|}

== Economy settings ==

The following options are available for economy settings:
=== Fortress rank ===
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Normal; Hard)
|-
| Economy population triggers || 1 to 300 || Affects how many citizens you need to increase the rank of your fortress. Must meet population and one of production or trade. Triggers 1 through 5 correspond to Hamlet, Village, Town, City, and Metropolis. || 20/50/80/110/140; 20/50/80/110/140
|-
| Economy production triggers || 1 to 100,000,000 || Affects how much created wealth you need to increase the rank of your fortress. Must meet population and one of production or trade. Triggers 1 through 5 correspond to Hamlet, Village, Town, City, and Metropolis. Setting this trigger to 0 causes it to be met immediately. || 5,000/25,000/100,000/200,000/300,000; 25,000/125,000/500,000/1,000,000/1,500,000
|-
| Economy trade triggers || 1 to 100,000,000 || Affects how much exported wealth you need to increase the rank of your fortress. Must meet population and one of production or trade. Triggers 1 through 5 correspond to Hamlet, Village, Town, City, and Metropolis. Setting a trigger to 0 causes it to be met immediately. || 500/2,500/10,000/20,000/30,000; 2,500/12,500/50,000/100,000/150,000
|}
=== Land holder ===
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Normal; Hard)
|-
| Land holder population triggers || 1 to 300 || Affects how [[Baron|barons]] and upwards are achieved. See [[Noble#Triggers|noble triggers]]. Values 4 through 10 are not used in the base game. || 20/20/20; 20/20/20
|-
| Land holder production triggers || 1 to 100,000,000 || Affects how barons and upwards are achieved. Values 4 through 10 are not used in the base game. || 100,000/200,000/300,000; 500,000/1,000,000/1,500,000
|-
| Land holder trade triggers || 1 to 100,000,000 || Affects how barons and upwards are achieved. Values 4 through 10 are not used in the base game. || 10,000/20,000/30,000; 50,000/100,000/150,000
|}

=== Temples ===
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Normal; Hard)
|-
| Value of temple || 1 to 100,000,000 || Affects how valuable a designated [[temple]] zone must be before it satisfies a petition to create it. || 2,000; 6,000
|-
| Value of temple complex || 1 to 100,000,000 || Affects how valuable a designated temple zone must be before it satisfies a petition to upgrade it. || 10,000; 30,000
|-
| Priesthood unit count || 1 to 300 || Affects how many members of a religion must be citizens in your fortress before a petition for a temple is made. || 10; 10
|-
| High priesthood unit count || 1 to 300 || Affects how many members of a religion must be citizens in your fortress before a petition to upgrade an existing temple is made. || 25; 25
|}
=== Guilds ===
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Normal; Hard)
|-
| Value of guildhall || 1 to 100,000,000 || Affects how valuable a designated [[guildhall]] zone must be before it satisfies a petition to create it. || 2,000; 6,000
|-
| Value of grand guildhall || 1 to 100,000,000 || Affects how valuable a designated guildhall zone must be before it satisfies a petition to upgrade it. || 10,000; 30,000
|-
| Guild unit count || 1 to 300 || Affects how many members of a profession must be citizens in your fortress before a petition for a guildhall is made. || 10; 10
|-
| Grand guild unit count || 1 to 300 || Affects how many members of a profession must be citizens in your fortress before a petition to upgrade an existing guildhall is made. || 25; 25
|}
=== Mandates and demands ===
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Normal; Hard)
|-
| Mandate period (more = fewer) || 1 to 10,000 || Affects how long nobles must wait before making new mandates. A higher value forces them to wait longer before mandating something.|| 1,000; 500
|-
| Demand period (more = fewer) || 1 to 10,000 || Affects how long nobles must wait before making new demands. A higher value forces them to wait longer before making a demand.|| 500; 250
|}

=== Fortress dig speed ===
{| class="wikitable"
|-
! Setting !! Possible values !! Description !! Default values (Normal; Hard)
|-
| Citizen/resident dig speed (more = faster) || 1 to 10,000 || Affects how quickly player fortress creatures can dig natural walls and remove constructions.|| 100; 100
|}

[[ru:Difficulty]]

Bogeyman

2026-03-06T21:07:22Z

Ziusudra: changed link to specific adv world gen option, removed them being friendly in fortress mode, removed bogey summons being rare (I think it's ~24%), removed deity needing nightmare sphere (script only checks for death), added necro summon adv world gen controls

{{Quality|Exceptional}}
{{av}}
{{old|Bogeymen were updated with 0.47.01, are now restricted to certain evil regions and gained new powers}}

[[File:bogeyman_sprite_preview.png|right]]A '''bogeyman''' {{Tile|ñ|0:1}} is a procedurally-generated [[night creature]] which is mostly known for attacking unwary [[adventurer mode|adventurers]] who [[Adventurer mode#Fast Travel|travel]] or [[Adventurer mode#Sleep|sleep]] outside at night, alone, within those [[Sphere|domains of evil affiliated with shadows or nightmares]] – both fast travelling and travelling normally on the local map trigger the appearance of bogeymen. The bane of many a young adventurer, bogeymen can prove to be deadly foes for the inexperienced and the unprepared.

Graphically, the default sprites that bogeymen use will be of malformed, humanoid creatures that resemble the randomly-generated appearance they've been given. This same setup is used for other procedurally-generated creatures, such as [[megabeast]]s and [[demon]]s. However, given the fact that bogeymen can transform into other creatures, they can borrow other sprites as well. Their portrait will remain as the last creature they transformed into, even after transforming back.

== Characteristics ==
[[File:bogeymen_transforming_anim.gif|thumb|275px|right|Two bogeymen transforming in the [[object testing arena]].]][[File:Bogeyman Attack.png|thumb|286px|right|A group of bogeymen attacking a hapless adventurer.]]A number of different types of bogeyman are procedurally generated at every world creation, similar to [[night troll]]s. Their numbers are normally dependent on world size, but can be directly controlled in [[Advanced_world_generation#Number_of_Bogeyman_Types|advanced world generation]] – if you prefer not having to deal with bogeymen, generating a world with "{{tt|Number of bogeymen types}}" set to {{tt|0}} will ensure that no bogeymen exist in your world.

While procedurally generated, bogeymen all possess certain characteristics in common. They are all [[fanciful]], evil-aligned humanoids with either extra or missing features; for example, some bogeymen are generated with wings and thus have the ability to fly, but this doesn't usually affect adventurers unless they too can fly. Others might be generated with appendages such as horns which can be used to gore the bogeyman's prey. All bogeymen are intelligent creatures, and reading their description will reveal the bogeyman "hurls vicious insults constantly". Bogeymen are restricted to regions aligned with [[demon]]ic evil, particularly the [[sphere]]s of nightmares or darkness. Bogeymen can be summoned by [[necromancer]]s with the appropriate [[secret]]s, and by nightmare-aligned [[demon]]s.

Bogeymen are by far the smallest of all night creatures (save transformed small creatures), ranging from 10,000 cm³ to 20,000 cm³, making the largest bogeymen only as big as a [[kobold]]. However, this doesn't mean they should be underestimated; all bogeymen possess Expert [[skill]] in [[wrestling]], [[Combat skill|biting, fighting, striking, kicking, dodging]] and [[Observer|observing]], on top of being one of the most agile types of creature in the game, which makes them exceptionally hard to hit. Bogeymen can [[Amphibious|breathe underwater]], [[No Exert|feel no exertion]], [[No Stun|cannot be stunned]] and are [[No Pain|immune to pain]], nausea, dizziness and fevers. Bogeymen need no food, water or sleep to survive, nor do they need to breathe, meaning they cannot be drowned or strangled. Interestingly, their raws also reveal an [[Trapavoid|immunity to traps]], the ability of [[building destroyer|destroying buildings]] and a [[pet]] value of 2,000. In previous versions, they did not exist in [[fortress mode]], but it seems like visiting necromancers can now sometimes summon them in combat.

Bogeymen have the powers to transform into animals, as well as to 'call upon the night' and summon other creatures – including more bogeymen! They do this, presumably, by using the [[Interaction_token#I_EFFECT|Summon interaction]]. This can make even a single bogeyman quickly turn into several, which then each begin to summon wild animals such as [[tiger]]s. More research needs to be done on the exact limitations of these abilities, and exact data is difficult to extrapolate due to summon interactions being both new and difficult to reverse engineer.

Bogeymen dissolve into harmless smoke shortly after being killed. Severed body parts can be picked up, but they, too, vaporize quickly. However, it is sometimes possible to keep them if you pick them up and fast-travel away before they start smoking. They can't be animated by [[necromancer]]s.

During a bogeyman attack, the "give up" option in the {{k|Esc}} screen becomes {{DFtext|Give in to the night.|7:1}} Selecting this will end the game immediately – if you end the game in this way, you will be described in [[legends mode]] as having {{DFtext|died in the dark.|7:0}}

Some dwarves [[Preferences|like]] bogeymen for their ''terror-inspiring antics''.

== Avoiding bogeymen ==
Bogeymen can be avoided by not traveling in evil, nightmare-aligned regions, and having a companion is no longer necessary to avoid them.

When you are [[ambush]]ed by bogeymen, you will get the message:

{{gametext|You are surrounded by incessant cackling.|5:1}}

A turn after receiving this message, 4–6 bogeymen will begin spawning around you.

If you try to travel or sleep/wait while at least one of the bogeymen is still alive, you will receive the message:

{{gametext|You are still surrounded by cackling.|5:1}}

Interestingly, bogeymen will be friendly towards creatures with the {{token|NOFEAR}} token. Playing as one of those will make you totally safe from bogeymen; in an unmodded game, the (three currently) available creatures with this token are humanoid arachnid people: the [[bark scorpion man]], the [[brown recluse spider man]], and the [[jumping spider man]]. It doesn't prevent bogeyman encounters, however; sleeping in the wilderness may still result in getting surrounded by cackling, and the bogeymen will still teleport towards you, as well as prevent you from sleeping or traveling.

Bogeymen will ambush [[werebeasts]], and are as unfriendly as anyone else toward them, but will vanish on their own within the game hour.

== Dealing with bogeymen ==
If you're playing as an adventurer with a [[gait|speed]] of over 1000, you may be able to run away from bogeymen. However, there is no escaping the night. No matter where you run, the bogeymen will teleport near you if you ever get too far away. You can get rid of these pesky creatures in three ways:

=== Killing them all ===
The most obvious solution. However, it is probably the most difficult one for inexperienced adventurers, and anyone who attempts to do this should be well-prepared. Once your adventurer becomes skilled, this will become a usually trivial task, but don't underestimate their blows. See the "Fighting bogeymen" section for more information.

=== Surviving until dawn ===
Bogeymen will be [[smoke|vaporized]] by the [[The Sun|morning sun]], so if you can't kill them but are able to run away from them or dodge/block their attacks well, you have another option: keep on doing that until dawn breaks. Unfortunately, this can take quite a while, depending on the time of night you were ambushed.

=== Entering a shelter ===
"Shelter" here refers to (non-ruined) buildings, (currently used) paved roads, (inhabited or uninhabited) lairs (including shrines and labyrinths) and [[cave|caves]]. Seeking refuge in such a place will make the bogeymen disappear in a puff of smoke. Incidentally, this was one of the reasons why townspeople encouraged you to spend the night in their homes. You can find the nearest shelter by examining the map in your {{k|Q}}uest Log.

Once you succeed in doing one of the above, you'll get the message:
{{gametext|The cackling fades away.|5:1}}
and then you can get back to adventuring. They will not attack again for the rest of the night.

Note that even if you successfully defeat bogeymen using any of the three methods described above, you can never get rid of them permanently, as they will ambush you again some other night if you do not take precautions.

== Fighting bogeymen ==
Bogeymen are tough because they have very high agility, giving them a high speed and are naturally skilled in unarmed combat and dodging, so their punches hurt and they are difficult to hit. With low weapon skills you'll have a hard time hitting them, but once you can hit them they become very easy to kill. If you know how to fight them effectively, they will go down surprisingly easily. Here are a few tips for fighting them:

*A [[shield]] is invaluable, as getting hit can break your bones and quickly spell your death. Ditto for some [[armor]].
*Legendary [[weapon skill]] or near is highly recommended to help overcome their dodging.
*Carefully planned maneuvering is the key to survival.
*Use your [[size]] to your advantage. Bogeymen are surprisingly small relative to the playable races available in unmodded games. Set your combat preference to '''charge''', and you will knock them over every time you strike. This can easily give you the upper hand in battle, as being prone slows bogeymen down and gives you more time to act.
*Wrestling moves will usually work. Bogeymen are so small that they have a hard time breaking wrestling holds from the other races. They do not feel pain so breaking bones will not disable them, but breaking a leg will slow them down.


Remember, prone bogeymen are much slower, so charge at them as often as you can, so you can knock them off their feet. You could also try to sever off feet or legs, as this will make them permanently prone. If you are carrying a lot of heavy objects, it might be a good idea to drop your backpack or, better yet, [[thrower|throw]] the [[weight|heavier]] and/or pointier objects at the bogeymen if they are not too close to you.

If you are not opposed to cheesy tactics, or just too slow to run away, you can instead block their line of sight by setting grass fires. If you can create at least a partial or full circle of fire around you, the terrestrial bogeymen will be unable to fight you. Once the bogeymen lose sight of your adventurer, it becomes a trivial game of throwing whatever can be grabbed. If you're feeling particularly vindictive, you can jump out of the fire behind them, and just behead them. Be wary of trees, as bogeymen have no qualms about climbing their way to you from above.

If you are really desperate for speed, you might also want to consider dropping your [[armor]] if it is slowing you down too much. Note that, while the extra speed might very well prove vital for your survival, you will also be more exposed to bogeymen attacks and will probably die faster if they manage to attack you and you are not a good [[dodger]]. You might want to consider keeping your helmet-a punch to the head by one of these creatures can easily ram your skull through your brain and end your life.

Despite what your imagination might imply, bogeymen are actually organic creatures. This means that they can be killed by damage to the brain, beheading, bisection (the separation of the lower body from the upper body) and excessive blood loss, and it is also generally easy to sever limbs and break bones. However, like a number of other night creatures, bogeymen do not feel pain and do not breathe, so they do not receive pain-related penalties or die from suffocation. This means that the most effective [[weapon]]s to use against them are edged weapons. With sufficient weapon skill, it is easy to score a hit that will sever a limb or puncture a vital organ such as the heart. Due to their small size, it is also easy to chop off the head or the lower body, killing the bogeyman instantly.

*Whatever you do, don't allow yourself to get surrounded. If a group of bogeymen are approaching you from one direction, move in the opposite direction. This generally leads to them approaching you in a line rather than a group, as the fastest bogeyman reaches you first. Thus you can fight them one at a time if you are fast enough.
*Don't let bogeymen get the initiative. If you let the bogeyman attack you, their skilled punches will likely break a bone and you'll be dead. So you should charge at one, attack it and run away before it has the chance to strike back.
*If the odds are against you, don't hesitate to flee. Remember that you don't need to kill bogeymen to get rid of them – you just have to survive the night or enter a shelter. Thus you should try to run in the direction of the nearest [[town]], [[fortress]], [[cave]] or [[lair]]. If you have a high enough speed, running away should actually be quite easy, as the bogeymen won't be able to catch up with you despite their constant teleportation. If a bogeyman manages to get too close to you, charge at it to knock it over and slow it down, and then continue running.
*Above all, remember that [[Losing|losing is fun]]!

== Summoning ==
Some [[necromancer]] [[secret]]s allow the summoning of bogeymen, who will appear at a random location around the summoner. The bogeyman will still be hostile to any creature that can feel fear, which almost always includes the necromancer that summoned them. In advanced world generation, setting the [[Advanced_world_generation#Number_of_Bogeyman_Types|number of bogeymen types]] to {{tt|0}} will prevent this ability and all [[Advanced_world_generation#Allow_Divination.2C_Experiments.2C_and_Necromancy_types|necromancer summons]] can also be disabled.

[[File:bogeyman2.png|thumb|300px|center|A drawing of bogeymen. ''Art by kruggsmash'']]

{{D for Dwarf}}

Bogeymen most likely don't take their victims to a place called "Never-Never Land".

{{gamedata|title=Example raws (as extracted from world.dat in version [[DF2014:Release_information/0.47.04|0.47.04]])|[CREATURE:NIGHT_CREATURE_16]
[NAME:bogeyman:bogeymen:bogeyman]
[CASTE_NAME:bogeyman:bogeymen:bogeyman]
[GENERATED]
[ATTACK_TRIGGER:50:5000:50000]
[NIGHT_CREATURE_BOGEYMAN]
[NATURAL_SKILL:WRESTLING:6]
[NATURAL_SKILL:BITE:6]
[NATURAL_SKILL:MELEE_COMBAT:6]
[NATURAL_SKILL:GRASP_STRIKE:6]
[NATURAL_SKILL:STANCE_STRIKE:6]
[NATURAL_SKILL:DODGING:6]
[NATURAL_SKILL:SITUATIONAL_AWARENESS:6]
[CAN_LEARN]
[CAN_SPEAK]
[NO_GENDER]
[CLUSTER_NUMBER:4:6]
[PHYS_ATT_RANGE:STRENGTH:450:1050:1150:1250:1350:1550:2250]
[PHYS_ATT_RANGE:TOUGHNESS:450:1050:1150:1250:1350:1550:2250]
[PHYS_ATT_RANGE:ENDURANCE:450:1050:1150:1250:1350:1550:2250]
[PHYS_ATT_RANGE:RECUPERATION:450:1050:1150:1250:1350:1550:2250]
[PHYS_ATT_RANGE:DISEASE_RESISTANCE:700:1300:1400:1500:1600:1800:2500]
[MENT_ATT_RANGE:ANALYTICAL_ABILITY:1250:1500:1750:2000:2500:3000:5000]
[MENT_ATT_RANGE:FOCUS:1250:1500:1750:2000:2500:3000:5000]
[MENT_ATT_RANGE:WILLPOWER:1250:1500:1750:2000:2500:3000:5000]
[MENT_ATT_RANGE:PATIENCE:0:333:666:1000:2333:3666:5000]
[MENT_ATT_RANGE:MEMORY:1250:1500:1750:2000:2500:3000:5000]
[MENT_ATT_RANGE:LINGUISTIC_ABILITY:450:1050:1150:1250:1350:1550:2250]
[MENT_ATT_RANGE:MUSICALITY:0:333:666:1000:2333:3666:5000]
[MENT_ATT_RANGE:SOCIAL_AWARENESS:700:1300:1400:1500:1600:1800:2500]
[PERSONALITY:ANXIETY_PROPENSITY:0:0:0]
[PERSONALITY:DEPRESSION_PROPENSITY:0:0:0]
[PERSONALITY:BASHFUL:0:0:0]
[PERSONALITY:STRESS_VULNERABILITY:0:0:0]
[PERSONALITY:FRIENDLINESS:0:0:0]
[PERSONALITY:ASSERTIVENESS:100:100:100]
[PERSONALITY:DISDAIN_ADVICE:100:100:100]
[PERSONALITY:CHEER_PROPENSITY:0:0:0]
[PERSONALITY:GRATITUDE:0:0:0]
[PERSONALITY:TRUST:0:0:0]
[PERSONALITY:ALTRUISM:0:0:0]
[PERSONALITY:SWAYED_BY_EMOTIONS:0:0:0]
[PERSONALITY:CRUELTY:100:100:100]
[PERSONALITY:HUMOR:100:100:100]
[NO_DRINK]
[NO_EAT]
[NO_SLEEP]
[BODY_APPEARANCE_MODIFIER:HEIGHT:90:95:98:100:102:105:110]
[BODY_APPEARANCE_MODIFIER:BROADNESS:90:95:98:100:102:105:110]
[LARGE_PREDATOR]
[EVIL]
[SUPERNATURAL]
[FANCIFUL]
[AMPHIBIOUS]
[SWIMS_INNATE]
[NONAUSEA]
[NOEXERT]
[NO_DIZZINESS]
[NOPAIN]
[NOSTUN]
[PETVALUE:2000]
[ALL_ACTIVE]
[NOFEAR]
[NO_FEVERS]
[LARGE_PREDATOR]
[SPHERE:MISERY]
[SPHERE:NIGHT]
[SPHERE:NIGHTMARES]
[BODY_SIZE:0:0:14000]
[CREATURE_TILE:164]
[BODY:RCP_UPPER_BODY:RCP_LOWER_BODY:RCP_NECK:RCP_HEAD:RCP_TWO_PART_ARMS:RCP_TWO_PART_LEGS:RCP_TRUNK:RCP_2_EYES:RCP_LUNGS:RCP_HEART:RCP_GUTS:RCP_SPINE:RCP_UPPER_SPINE:RCP_BRAIN:RCP_SKULL:RCP_MOUTH:RCP_TONGUE:RCP_RIBS]
[CANOPENDOORS]
[EQUIPS]
[BODY_DETAIL_PLAN:STANDARD_MATERIALS]
[REMOVE_MATERIAL:HAIR]
[REMOVE_MATERIAL:SKIN]
[BODY_DETAIL_PLAN:STANDARD_TISSUES]
[REMOVE_TISSUE:HAIR]
[REMOVE_TISSUE:SKIN]
[BODY_DETAIL_PLAN:VERTEBRATE_TISSUE_LAYERS:NONE:FAT:MUSCLE:BONE:CARTILAGE]
[BODY_DETAIL_PLAN:STANDARD_HEAD_POSITIONS]
[BODY_DETAIL_PLAN:HUMANOID_HEAD_POSITIONS]
[BODY_DETAIL_PLAN:HUMANOID_RIBCAGE_POSITIONS]
[BODY_DETAIL_PLAN:HUMANOID_RELSIZES]
[USE_MATERIAL_TEMPLATE:SINEW:SINEW_TEMPLATE]
[TENDONS:LOCAL_CREATURE_MAT:SINEW:200]
[LIGAMENTS:LOCAL_CREATURE_MAT:SINEW:200]
[HAS_NERVES]
[NOBREATHE]
[HOMEOTHERM:10040]
[NO_UNIT_TYPE_COLOR]
[COLOR:0:0:1]
[SELECT_TISSUE_LAYER:HEART:BY_CATEGORY:HEART]
[PLUS_TISSUE_LAYER:SCALE:BY_CATEGORY:THROAT]
[TL_MAJOR_ARTERIES]
[USE_MATERIAL_TEMPLATE:BLOOD:BLOOD_TEMPLATE]
[STATE_COLOR:ALL:DARK_INDIGO]
[BLOOD:LOCAL_CREATURE_MAT:BLOOD:LIQUID]
[ATTACK:PUNCH:BODYPART:BY_TYPE:GRASP]
[ATTACK_SKILL:GRASP_STRIKE]
[ATTACK_VERB:punch:punches]
[ATTACK_CONTACT_PERC:100]
[ATTACK_PREPARE_AND_RECOVER:2:2]
[ATTACK_FLAG_WITH]
[ATTACK_PRIORITY:MAIN]
[ATTACK:KICK:BODYPART:BY_TYPE:STANCE]
[ATTACK_SKILL:STANCE_STRIKE]
[ATTACK_VERB:kick:kicks]
[ATTACK_CONTACT_PERC:100]
[ATTACK_PREPARE_AND_RECOVER:2:2]
[ATTACK_FLAG_WITH]
[ATTACK_PRIORITY:MAIN]
[ATTACK_FLAG_BAD_MULTIATTACK]
[ATTACK:BITE:BODYPART:BY_CATEGORY:MOUTH]
[ATTACK_SKILL:BITE]
[ATTACK_VERB:bite:bites]
[ATTACK_CONTACT_PERC:100]
[ATTACK_PREPARE_AND_RECOVER:2:2]
[ATTACK_PRIORITY:MAIN]
[ATTACK_FLAG_CANLATCH]
[GAIT:SWIM:Maximum Swim Speed:725:10:3:2175:50:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:50]
[GAIT:SWIM:Faster Swim:1450:5:3:2175:10:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:20]
[GAIT:SWIM:Fast Swim:2175:NO_BUILD_UP:5:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:10]
[GAIT:SWIM:Swim:2900:NO_BUILD_UP:0]
[GAIT:SWIM:Slow Swim:3900:NO_BUILD_UP:0]
[GAIT:SWIM:Creeping Swim:5900:NO_BUILD_UP:0]
[GAIT:WALK:Sprint:225:10:3:675:50:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:50]
[GAIT:WALK:Run:450:5:3:675:10:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:20]
[GAIT:WALK:Jog:675:NO_BUILD_UP:5:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:10]
[GAIT:WALK:Walk:900:NO_BUILD_UP:0]
[GAIT:WALK:Stroll:1900:NO_BUILD_UP:0]
[GAIT:WALK:Creep:2900:NO_BUILD_UP:0]
[GAIT:CRAWL:Scramble:225:10:3:675:50:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:50]
[GAIT:CRAWL:Faster Crawl:450:5:3:675:10:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:20]
[GAIT:CRAWL:Fast Crawl:675:NO_BUILD_UP:5:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:10]
[GAIT:CRAWL:Crawl:900:NO_BUILD_UP:0]
[GAIT:CRAWL:Slow Crawl:1900:NO_BUILD_UP:0]
[GAIT:CRAWL:Creep:2900:NO_BUILD_UP:0]
[GAIT:CLIMB:Scramble:225:10:3:675:50:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:50]
[GAIT:CLIMB:Faster Climb:450:5:3:675:10:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:20]
[GAIT:CLIMB:Fast Climb:675:NO_BUILD_UP:5:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:10]
[GAIT:CLIMB:Climb:900:NO_BUILD_UP:0]
[GAIT:CLIMB:Slow Climb:1900:NO_BUILD_UP:0]
[GAIT:CLIMB:Creep:2900:NO_BUILD_UP:0]
[CAN_DO_INTERACTION:BOGEYMAN_POLYMORPH]
[CDI:ADV_NAME:Transform]
[CDI:TARGET:A:SELF_ONLY]
[CDI:USAGE_HINT:DEFEND]
[CDI:WAIT_PERIOD:100]
[DESCRIPTION:A small skinless humanoid. It has a curling trunk and it hurls vicious insults constantly. Now you will know why you fear the night.]
[PREFSTRING:terror-inspiring antics]

[CREATURE:NIGHT_CREATURE_17]
[NAME:bogeyman:bogeymen:bogeyman]
[CASTE_NAME:bogeyman:bogeymen:bogeyman]
[GENERATED]
[ATTACK_TRIGGER:50:5000:50000]
[NIGHT_CREATURE_BOGEYMAN]
[NATURAL_SKILL:WRESTLING:6]
[NATURAL_SKILL:BITE:6]
[NATURAL_SKILL:MELEE_COMBAT:6]
[NATURAL_SKILL:GRASP_STRIKE:6]
[NATURAL_SKILL:STANCE_STRIKE:6]
[NATURAL_SKILL:DODGING:6]
[NATURAL_SKILL:SITUATIONAL_AWARENESS:6]
[CAN_LEARN]
[CAN_SPEAK]
[NO_GENDER]
[CLUSTER_NUMBER:4:6]
[PHYS_ATT_RANGE:STRENGTH:450:1050:1150:1250:1350:1550:2250]
[PHYS_ATT_RANGE:TOUGHNESS:450:1050:1150:1250:1350:1550:2250]
[PHYS_ATT_RANGE:ENDURANCE:450:1050:1150:1250:1350:1550:2250]
[PHYS_ATT_RANGE:RECUPERATION:450:1050:1150:1250:1350:1550:2250]
[PHYS_ATT_RANGE:DISEASE_RESISTANCE:700:1300:1400:1500:1600:1800:2500]
[MENT_ATT_RANGE:ANALYTICAL_ABILITY:1250:1500:1750:2000:2500:3000:5000]
[MENT_ATT_RANGE:FOCUS:1250:1500:1750:2000:2500:3000:5000]
[MENT_ATT_RANGE:WILLPOWER:1250:1500:1750:2000:2500:3000:5000]
[MENT_ATT_RANGE:PATIENCE:0:333:666:1000:2333:3666:5000]
[MENT_ATT_RANGE:MEMORY:1250:1500:1750:2000:2500:3000:5000]
[MENT_ATT_RANGE:LINGUISTIC_ABILITY:450:1050:1150:1250:1350:1550:2250]
[MENT_ATT_RANGE:MUSICALITY:0:333:666:1000:2333:3666:5000]
[MENT_ATT_RANGE:SOCIAL_AWARENESS:700:1300:1400:1500:1600:1800:2500]
[PERSONALITY:ANXIETY_PROPENSITY:0:0:0]
[PERSONALITY:DEPRESSION_PROPENSITY:0:0:0]
[PERSONALITY:BASHFUL:0:0:0]
[PERSONALITY:STRESS_VULNERABILITY:0:0:0]
[PERSONALITY:FRIENDLINESS:0:0:0]
[PERSONALITY:ASSERTIVENESS:100:100:100]
[PERSONALITY:DISDAIN_ADVICE:100:100:100]
[PERSONALITY:CHEER_PROPENSITY:0:0:0]
[PERSONALITY:GRATITUDE:0:0:0]
[PERSONALITY:TRUST:0:0:0]
[PERSONALITY:ALTRUISM:0:0:0]
[PERSONALITY:SWAYED_BY_EMOTIONS:0:0:0]
[PERSONALITY:CRUELTY:100:100:100]
[PERSONALITY:HUMOR:100:100:100]
[NO_DRINK]
[NO_EAT]
[NO_SLEEP]
[BODY_APPEARANCE_MODIFIER:HEIGHT:90:95:98:100:102:105:110]
[BODY_APPEARANCE_MODIFIER:BROADNESS:90:95:98:100:102:105:110]
[LARGE_PREDATOR]
[EVIL]
[SUPERNATURAL]
[FANCIFUL]
[AMPHIBIOUS]
[SWIMS_INNATE]
[NONAUSEA]
[NOEXERT]
[NO_DIZZINESS]
[NOPAIN]
[NOSTUN]
[PETVALUE:2000]
[ALL_ACTIVE]
[NOFEAR]
[NO_FEVERS]
[LARGE_PREDATOR]
[SPHERE:MISERY]
[SPHERE:NIGHT]
[SPHERE:NIGHTMARES]
[BODY_SIZE:0:0:14000]
[CREATURE_TILE:164]
[BODY:RCP_UPPER_BODY:RCP_LOWER_BODY:RCP_NECK:RCP_HEAD:RCP_TWO_PART_ARMS:RCP_TWO_PART_LEGS:RCP_TWO_FLIGHTLESS_WINGS:RCP_2_EYES:RCP_LUNGS:RCP_HEART:RCP_GUTS:RCP_THROAT:RCP_SPINE:RCP_UPPER_SPINE:RCP_BRAIN:RCP_SKULL:RCP_MOUTH:RCP_TONGUE:RCP_RIBS]
[CANOPENDOORS]
[EQUIPS]
[BODY_DETAIL_PLAN:STANDARD_MATERIALS]
[REMOVE_MATERIAL:HAIR]
[BODY_DETAIL_PLAN:STANDARD_TISSUES]
[REMOVE_TISSUE:HAIR]
[BODY_DETAIL_PLAN:VERTEBRATE_TISSUE_LAYERS:SKIN:FAT:MUSCLE:BONE:CARTILAGE]
[BODY_DETAIL_PLAN:STANDARD_HEAD_POSITIONS]
[BODY_DETAIL_PLAN:HUMANOID_HEAD_POSITIONS]
[BODY_DETAIL_PLAN:HUMANOID_RIBCAGE_POSITIONS]
[BODY_DETAIL_PLAN:HUMANOID_RELSIZES]
[USE_MATERIAL_TEMPLATE:SINEW:SINEW_TEMPLATE]
[TENDONS:LOCAL_CREATURE_MAT:SINEW:200]
[LIGAMENTS:LOCAL_CREATURE_MAT:SINEW:200]
[HAS_NERVES]
[NOBREATHE]
[HOMEOTHERM:10040]
[SELECT_MATERIAL:SKIN]
[STATE_COLOR:ALL_SOLID:SLATE_GRAY]
[NO_UNIT_TYPE_COLOR]
[COLOR:0:0:1]
[SELECT_TISSUE_LAYER:HEART:BY_CATEGORY:HEART]
[PLUS_TISSUE_LAYER:SCALE:BY_CATEGORY:THROAT]
[TL_MAJOR_ARTERIES]
[USE_MATERIAL_TEMPLATE:BLOOD:BLOOD_TEMPLATE]
[STATE_COLOR:ALL:DARK_INDIGO]
[BLOOD:LOCAL_CREATURE_MAT:BLOOD:LIQUID]
[ATTACK:PUNCH:BODYPART:BY_TYPE:GRASP]
[ATTACK_SKILL:GRASP_STRIKE]
[ATTACK_VERB:punch:punches]
[ATTACK_CONTACT_PERC:100]
[ATTACK_PREPARE_AND_RECOVER:2:2]
[ATTACK_FLAG_WITH]
[ATTACK_PRIORITY:MAIN]
[ATTACK:KICK:BODYPART:BY_TYPE:STANCE]
[ATTACK_SKILL:STANCE_STRIKE]
[ATTACK_VERB:kick:kicks]
[ATTACK_CONTACT_PERC:100]
[ATTACK_PREPARE_AND_RECOVER:2:2]
[ATTACK_FLAG_WITH]
[ATTACK_PRIORITY:MAIN]
[ATTACK_FLAG_BAD_MULTIATTACK]
[ATTACK:BITE:BODYPART:BY_CATEGORY:MOUTH]
[ATTACK_SKILL:BITE]
[ATTACK_VERB:bite:bites]
[ATTACK_CONTACT_PERC:100]
[ATTACK_PREPARE_AND_RECOVER:2:2]
[ATTACK_PRIORITY:MAIN]
[ATTACK_FLAG_CANLATCH]
[GAIT:SWIM:Maximum Swim Speed:725:10:3:2175:50:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:50]
[GAIT:SWIM:Faster Swim:1450:5:3:2175:10:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:20]
[GAIT:SWIM:Fast Swim:2175:NO_BUILD_UP:5:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:10]
[GAIT:SWIM:Swim:2900:NO_BUILD_UP:0]
[GAIT:SWIM:Slow Swim:3900:NO_BUILD_UP:0]
[GAIT:SWIM:Creeping Swim:5900:NO_BUILD_UP:0]
[GAIT:WALK:Sprint:225:10:3:675:50:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:50]
[GAIT:WALK:Run:450:5:3:675:10:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:20]
[GAIT:WALK:Jog:675:NO_BUILD_UP:5:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:10]
[GAIT:WALK:Walk:900:NO_BUILD_UP:0]
[GAIT:WALK:Stroll:1900:NO_BUILD_UP:0]
[GAIT:WALK:Creep:2900:NO_BUILD_UP:0]
[GAIT:CRAWL:Scramble:225:10:3:675:50:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:50]
[GAIT:CRAWL:Faster Crawl:450:5:3:675:10:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:20]
[GAIT:CRAWL:Fast Crawl:675:NO_BUILD_UP:5:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:10]
[GAIT:CRAWL:Crawl:900:NO_BUILD_UP:0]
[GAIT:CRAWL:Slow Crawl:1900:NO_BUILD_UP:0]
[GAIT:CRAWL:Creep:2900:NO_BUILD_UP:0]
[GAIT:CLIMB:Scramble:225:10:3:675:50:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:50]
[GAIT:CLIMB:Faster Climb:450:5:3:675:10:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:20]
[GAIT:CLIMB:Fast Climb:675:NO_BUILD_UP:5:LAYERS_SLOW:STRENGTH:AGILITY:STEALTH_SLOWS:10]
[GAIT:CLIMB:Climb:900:NO_BUILD_UP:0]
[GAIT:CLIMB:Slow Climb:1900:NO_BUILD_UP:0]
[GAIT:CLIMB:Creep:2900:NO_BUILD_UP:0]
[CAN_DO_INTERACTION:BOGEYMAN_POLYMORPH]
[CDI:ADV_NAME:Transform]
[CDI:TARGET:A:SELF_ONLY]
[CDI:USAGE_HINT:DEFEND]
[CDI:WAIT_PERIOD:100]
[DESCRIPTION:A small humanoid with lidless eyes. It has thin wings of stretched skin and it hurls vicious insults constantly. Its slate gray skin is sleek and smooth. Now you will know why you fear the night.]
[PREFSTRING:terror-inspiring antics]
}}
{{Scriptdata}}
{{Creatures}}

{{Category|Amphibious}}
{{Category|Building destroyer}}
{{Category|Fanciful}}
{{Category|Learns}}
{{Category|No Exert}}
{{Category|No Pain}}
{{Category|No Stun}}
{{Category|Trapavoid}}
[[ru:Bogeyman]]

Bauxite

2026-03-06T02:57:48Z

Ziusudra: clarified that it is not a layer stone, matching wording of the similar saltpeter

{{Quality|Exceptional}}
{{stonelookup/0
|graphic=bauxite_sprite.png}}
{{av}}

'''Bauxite''' is a non-economic and low-value dark-red sedimentary [[stone]] that only appears as large clusters in [[sedimentary layer]]s. [[40d:Bauxite|Once]] highly prized as the only practical source of [[magma-safe]] [[mechanism]]s to create magma-proof devices, its importance has declined with the addition of many new heat-resistant forms of stone, as well as the ability to make [[metal]] mechanisms from [[iron]] and [[steel]]. Nevertheless, it is still used by some long-time players for nostalgia, and its rare, bloody appearance makes it an interesting aesthetic choice.

Bauxite may contain both [[sapphire]] and [[ruby]].

==In real life==
In real life, bauxite is an ore of [[aluminum]]. It is often called "hardpan" and the result of progressed chemical leaching of the soil via water. It's commonly found near the surface in well-aged and weathered soil, and is the world's primary source of gallium and aluminum. The technology required to extract these, however, is beyond the level possessed by any of ''Dwarf Fortress''' civilizations.

Bauxite is composed primarily of the minerals gibbsite (aluminum hydroxide: Al(OH)3), boehmite (aluminum oxide-hydroxide: γ-AlO(OH)), and diaspore (aluminum oxide-hydroxide: α-AlO(OH)) (none of which are individually present in ''Dwarf Fortress''). Bauxite forms by the weathering and mineralization of various aluminum-rich soils or clays. Despite the correspondence in-game, corundum, the mineral that makes up [[ruby]] and [[sapphire]] (aluminum oxide: Al2O3), does '''not''' form in bauxite.

Extracting aluminum from bauxite, even in the most primitive way, requires the use of the Hall–Héroult process: the electrolysis of bauxite which has been dissolved into molten [[cryolite]]. The development of this process transformed aluminum from an exceptionally rare metal to a cheap, utilitarian material. Dwarves have not yet discovered electricity, therefore they cannot make use of electrolysis to get aluminum from bauxite.

[[File:Almásfüzitő82.JPG|center|thumb|290px|Bauxite.]]

{{gamedata}}
{{stones}}

Shale

2026-03-06T02:45:09Z

Ziusudra: adjusted sedimentary link to avoid redirect and ambiguity

{{Quality|Superior}}
{{layerlookup/0
|graphic=shale_sprite.png}}
{{av}}

'''Shale''' is a [[sedimentary layer]] [[stone]] that can contain [[vein]]s of [[cinnabar]].

==In Real Life==
Shale is a fine-grained sedimentary rock composed of [[mud]] that is a mix of flakes of [[clay]] minerals and tiny fragments (silt-sized particles) of other minerals, such as quartz and [[calcite]]. It [[Metamorphic|metamorphises]] into [[slate]].
[[File:shale.jpg|thumb|320px|center|One of the hardest forms of mud ever known.]]

{{gamedata}}
{{stones}}

Schorl

2026-03-06T02:44:12Z

Ziusudra: added link for stone layer

{{Quality|Fine}}
{{gemlookup/0
|graphic=cut_schorl_sprite.png
|graphic2=rough_schorl_sprite.png}}
{{av}}

'''Schorls''' are unremarkable low-value [[gem]]s found in [[sedimentary]] and [[metamorphic]] [[stone layer]]s, as well as in [[granite]].

==In Real Life==

Also known as black tourmaline, this variety is by far the most common, constituting an estimated 95% of the world's tourmalines. It is named after the Saxony village of Schorl (curr. Zschorlau) where it was first discovered by German mineralogists.

[[File:Schorl-118689.jpg|thumb|center|300px|Schorl.]]

{{gamedata}}
{{gems}}

Red tourmaline

2026-03-06T02:43:49Z

Ziusudra: added link for stone layer

{{Quality|Fine}}
{{gemlookup/0
|graphic=cut_red_tourmaline_sprite.png
|graphic2=rough_red_tourmaline_sprite.png
|wiki=Tourmaline}}
{{av}}

'''Red tourmaline''' is a semi-precious [[gem]] found within [[sedimentary]] and [[metamorphic]] [[stone layer]]s, as well as [[granite]].

[[File:Tourmaline-195618.jpg|thumb|center|250px|Red tourmaline.]]

{{gamedata}}
{{gems}}

Pink tourmaline

2026-03-06T02:43:28Z

Ziusudra: added link for stone layer

{{Quality|Fine}}
{{gemlookup/0
|graphic=cut_pink_tourmaline_sprite.png
|graphic2=rough_pink_tourmaline_sprite.png
|wiki=Tourmaline}}
{{av}}

'''Pink tourmalines''' are semi-precious [[gem]]s that can be found within [[sedimentary]] and [[metamorphic]] [[stone layer]]s, as well as within [[granite]].

[[File:pink_tourmaline.jpg|thumb|220px|center|Pink tourmaline.]]

{{gamedata}}
{{gems}}

Mudstone

2026-03-06T02:42:59Z

Ziusudra: adjusted sedimentary link to avoid redirect and ambiguity

{{Quality|Superior}}
{{layerlookup/0
|graphic=mudstone_sprite.png}}
{{av}}

'''Mudstone''' is an unremarkable [[sedimentary layer]] [[stone]].

Mudstone cavern floors do not count as [[mud]], and are thus unsuitable for [[farming]] (''unless one subjects them to [[irrigation]], of course'').

==In Real Life==
Mudstone is a fine grained sedimentary rock which originates from [[clay]] and [[mud]]. With increased pressure over time, the clay minerals can form into parallel layers. This finely bedded material that splits readily into thin slices is then called [[shale]].
<Gallery>
Image:Mudstone.jpg|Mudstone
File:South Cliff Hornsea.jpg|Mudstone cliff eroded by waves
</gallery>

{{Translation| dwarven = ol-lam | elvish = salapa-queca | goblin = gob-ngomstu | human = vum-ado}}

{{gamedata}}
{{stones}}

Green tourmaline

2026-03-06T02:42:13Z

Ziusudra: added link for stone layer

{{Quality|Fine}}
{{gemlookup/0
|graphic=cut_green_tourmaline_sprite.png
|graphic2=rough_green_tourmaline_sprite.png
|wiki=Tourmaline}}
{{av}}

'''Green tourmaline''' is a semi-precious [[gem]] found within [[sedimentary]] and [[metamorphic]] [[stone layer]]s, as well as within [[granite]].

[[File:Verdeleite.jpg|center|thumb|290px|Octagon cut green tourmaline.]]

{{gamedata}}
{{gems}}

Indigo tourmaline

2026-03-06T02:41:21Z

Ziusudra: added link for stone layer

{{Quality|Fine}}
{{gemlookup/0
|graphic=cut_indigo_tourmaline_sprite.png
|graphic2=rough_indigo_tourmaline_sprite.png
|wiki=Tourmaline}}
{{av}}

'''Indigo tourmaline''' is one of the higher-value, semi-precious [[gem]]s that can be found within [[sedimentary]] and [[metamorphic]] [[stone layer]]s, as well as within [[granite]]. Scoring a ×25 multiplier, the same as [[clear zircon]], these are great for saving for later, when you have great gem-cutters and gem-setters, to get very high-value objects.

[[File:Indigolith-G-EmpireTheWorldOfGems.jpg|thumb|center|300px|Indigo tourmaline gem.]]

{{gamedata}}
{{gems}}

Clear tourmaline

2026-03-06T02:38:40Z

Ziusudra: added link for stone layer

{{Quality|Fine}}
{{gemlookup/0
|graphic=cut_clear_tourmaline_sprite.png
|graphic2=rough_clear_tourmaline_sprite.png
|wiki=Tourmaline}}
{{av}}

'''Clear tourmalines''' are moderately valuable [[gem]]s that can be found within [[sedimentary]] and [[metamorphic]] [[stone layer]]s, as well as within [[granite]].

[[File:Tourmaline-118598.jpg|center|thumb|170px|Clear tourmaline]]

{{gamedata}}
{{gems}}

Claystone

2026-03-06T02:37:21Z

Ziusudra: adjusted link to avoid redirect and ambiguity

{{Quality|Superior}}
{{layerlookup/0
|graphic=claystone_sprite.png}}
{{av}}

'''Claystone''' is an unremarkable [[sedimentary layer]] [[stone]]. Similar to [[clay]], it will not sustain an [[aquifer]]. Unlike clay, claystone cannot be used for [[ceramic industry|ceramics]].

==In real life==
[http://en.wikipedia.org/wiki/Claystone '''Claystone'''] is composed primarily of [[clay]]-sized particles. It is not to be confused with [[shale]], which splits into thin layers, and is distinct from [[mudstone]] in that it is fully hardened.
<gallery>
File:Museo de La Plata - Arcilita.jpg|Some claystone
</gallery>

{{gamedata}}
{{stones}}

Banded agate

2026-03-06T02:35:20Z

Ziusudra: adjusted link to avoid redirect and the other word was already there

{{Quality|Fine}}
{{gemlookup/0
|graphic=cut_banded_agate_sprite.png
|graphic2=rough_banded_agate_sprite.png
|wiki=Agate}}
{{av}}

'''Banded agates''' are unremarkable low-value [[gem]]s found in [[sedimentary layer]]s. All agates have the same [[material value]]: 2, the lowest any gem can have.

[[File:Agate banded 750pix.jpg|center|thumb|300px|Chalcedony variety]]
{{gamedata}}
{{gems}}