Dwarf Fortress Wiki - User contributions [en]

Hide Items or Buildings

2026-06-23T02:17:52Z

Ziusudra: replaced old controls with new, removed migration, rated

{{Quality|Fine}}
{{av}}
:''This article refers to "hide" in terms of removing items or buildings from view, for the article on creature skin, see [[cv:skin|Skin]].''

You can '''hide and unhide Items and Buildings''' using the {{Menu icon|i}} designation menu or the [[File:Ui iH.png]] button the items' information sheet.

The hidden objects will still be there and will still be available for use by [[dwarf|dwarves]], but they will not be visible on screen, which will instead show another visible item, or just the empty tile. Hidden items will still be listed when pointing the mouse at the tile, but cannot be clicked on, while hidden buildings will not be listed.

To hide multiple buildings or items at once, use {{Menu icon|i|h}}, then select the area they are in; use {{Menu icon|i|H}} to reveal them again; these only work on buildings if the center tile is selected.

To hide a single building, click the building, then the [[File:Ui iH.png]] on all of the items used to build that building. To reveal a hidden building, you must do one of: open its information sheet from the locations menu, reveal its build materials from the [[stocks]] menu (or their information sheets opened from stocks), or use {{Menu icon|i|H}} on its center tile.

Note that if you hide all of a material from the stocks menu, all buildings made of that material will also be hidden.

To hide a single item, click the tile it is on, then its tab on the right side of the information sheet (if not already selected), or its line on the list of items (if there are many), then the [[File:Ui iH.png]] at top right of its information sheet.

This can cause what appear to be bugs, if cage traps are hidden after they're set. In this case, click the trap and use [[File:Ui iH.png]] to hide only the mechanisms, and not the cage. This will hide the trap, but still allow the cage to be seen after being triggered. Weapon traps need all their weapons and the mechanisms hidden to disappear.

{{Category|Designations}}

Anatomy

2026-06-21T22:28:34Z

Ziusudra: replaced token links with template

{{Quality|Unrated}}
{{av}}
[[File:many_organs_preview.png|right]]This page details the constituent limbs and '''organs''' one can expect to find in a dwarf's (or other humanoid's) body, based on data from <code>\raw\objects\body_default.txt</code> and <code>\raw\objects\creature_standard.txt</code>.

=Head Structure=
===Hair===
[[Hair]] is common to many creatures, not the least of which are dwarves. Dwarves can exhibit facial hair from birth, though female dwarves do not grow any by default (this <s>mistake</s> can be <s>corrected</s> changed in <code>creature_standard.txt</code> under the token <code>[CASTE:FEMALE]</code>).

===Eyes===
Eyes allow dwarves to use their sight to view the world around them, and make decisions based on visual information. Losing both eyes can [[Wound#Blindness|render a dwarf blind]], resulting in a dramatic decrease in situational awareness and crafting quality.

===Nose===
Noses ''would'' allow dwarves to smell things that [[Smell|emit odors]], but currently serve no real purpose{{Verify}}. A dwarf without a nose will still get unhappy thoughts from [[miasma]].

===Mouth===
Mouths are used for biting by certain creatures who lack teeth. Interestingly, they are only considered in combat; even if a dwarf somehow loses their mouth, they can still eat meals and talk to other dwarves.

An interesting point to note is that both the mouth and nose can be removed, and the dwarf will still be able to breathe.

===Ears===
Ears are used to hear [[noise]]s. To a dwarf, the only noises that matter are those from tasks that modify tiles, such as mining, carving/smoothing, and woodcutting. Losing both ears can render dwarves deaf, and thus unable to hear noises.

==Head Organs==

===Brain===
Brains allow dwarves to think and are critical to survival. If the brain experiences any damage beyond bruising, it may result in loss of consciousness, or even death.

=Upper Body Structure=

===Neck===
Necks contain part of the upper spine and connect the head to the torso. They contain nervous pathways that are critical to life. Damage to the neck may result in full body paralysis, followed by death.

===Throat===
Throats are the forward-facing portion of the neck. They can be strangled to induce unconsciousness, and contain major arteries that can cause rapid death when opened by attacks.

===Upper Torso===
The upper torso contains critical organs used for sustained life functions. Damage to the chest often results in damage to these critical organs, which can quickly result in death. The upper torso connects the neck and the lower torso, and attaches both arms to the body.

===Arms===
Arms are used for general physical interaction with the world, including lifting and carrying objects, [[wrestling]] with combatants, and grasping items. They may also be used for mobility if the dwarf does not have the ability to stand, which may arise from loss or impairment of the legs.

*Upper arm
**The upper arm connects the torso and the lower arm.

*Lower arm
**The lower arm connects the upper arm and the hand.

*Hand
**Hands are used for attacks and grasping, and are typically populated with five fingers, including the thumb. A dwarf may experience difficulty grasping if one or more fingers are missing from the hand, and will, obviously, completely lose their ability to grasp if all fingers are lost.

==Upper Body Organs==

===Heart===
Hearts ''would'' be necessary to circulate a dwarf's blood around their body, but in reality, they do not serve any real function, and are theoretically not required for a creature to stay alive. However, the high {{token|VASCULAR|tissue}} value of the tissue which the heart is made from, as well as the {{token|MAJOR_ARTERIES|tissue}} token attributed to said tissue, ensure that any puncture to the heart will result in severe blood loss and eventual death.

===Lungs===
Lungs allow dwarves to breathe. Loss of one can impair a dwarf's stamina, and can cause the dwarf to become Winded when doing basic tasks; but loss of both causes death by suffocation.

===Stomach===
Stomachs ''would'' be used to digest food, but their presence is mostly decorative - a dwarf with a missing stomach can still eat. Strikes to the stomach can cause nausea and vomiting.

===Liver===
Livers ''would'' be used to determine how well a given creature can hold its liquor, but currently have no function and are mostly cosmetic in nature. Dwarven livers are 50% larger than normal, perhaps to reflect their innate resistance to inebriation. This is in reality caused by their {{token|SYNDROME_DILUTION_FACTOR|creature}} token, and damage to their livers will have no effect on it.

===Pancreas===
Pancreases would be used to regulate digestion and blood sugars, but dwarven diabetes does not exist, therefore their presence is entirely decorative. They can be damaged, but this is unlikely compared to the stomach, liver, lungs and heart due to their small size.

===Spleen===
Spleens would be used to filter the blood, like the kidneys, but they are entirely decorative, like the pancreas, stomach and liver.

=Lower Body Structure=

===Lower Torso===
The lower torso contains non-critical organs that are not immediately important to continued survival. It connects the upper torso and the legs.

===Legs===
Legs are used for standing, walking, running, and jumping. When missing one or even two, dwarves can use crutches to walk, and may even become skilled enough to return to their standard walking speed.

*Upper Leg
**The upper leg connects the lower torso and lower leg.

*Lower Leg
**The lower leg connects the upper leg and foot.

*Foot
**Feet are used to maintain a stance, and are required for walking. Loss of just one foot may impair a dwarf's mobility severely, especially without a crutch.

==Lower Body Organs==

===Guts===
Guts are considered to be one cohesive unit by the game, and are simulated as such; they represent the small and large intestinal tracts that fill the abdominal cavity. They are considered to be 'under pressure', and thus may be ejected if the lower torso is opened by an attack. Guts being ejected usually results in death.

===Kidneys===
Kidneys would be important in cleaning the blood and creating urine, but the game treats them decoratively. The kidneys are not life-critical, and one or both can be disabled or removed without much incident.

=Limb Components=
Limbs and other components of the body are layered in material that helps protect the vital organs and nervous connections that keep the body functioning.

==Skin==
[[Skin]] is a protective layer that surrounds most external body parts; the first line of defense from infection and disease, and protects dwarves from contaminants such as blood or vomit. Dwarves with healthy skin will usually wash contaminants off of their skin with water, using soap if it is available.

==Fat==
Subcutaneous [[fat]] is held under the skin, where it forms an additional layer of protection against blunt-force and slashing injuries. As Dwarf Fortress' layering system is somewhat abstracted, when a dwarf is set on fire, their fat usually catches alight first, destroying the skin in the process.

Some dwarves can survive burning, even when all of their skin and fat is burned off, forming sinewy "supersoldiers" that do not experience pain. They are, however, very likely to die of blood loss before this can be achieved.

==Muscle==
Muscles are critical in moving parts of the body, and are the core component in the motoric capability of a limb. Torn muscles can heal over time, but will temporarily reduce or negate the ability of a limb to function.

===Sinews===
Sinews connect the muscles and bones together, and include the tendons (muscle-to-bone) and ligaments (bone-to-bone). Sinew tearing will disable limbs until they heal on their own.

==Nerves==
Nerves carry impulses to and from a creature's brain. Nerves are connected between body parts up to the brain; if a nerve is severed, all nerves downstream of it will be paralysed or numb. Nerves cannot heal, and once severed, will never reconnect.

===Sensory===
Sensory nerves are used to experience tactile sensations in limbs, such as bumps, scratches and touches. Loss of sensory nerves can arise from skin damage and deep cuts, which can render the limb numb.

===Motor===
Motor nerves are used to actuate muscles that move limbs. If an attack severs a motor nerve, the limb and any others connected to it will be paralysed.

==Arteries==
Arteries carry blood around the body, typically under moderate pressure. If an attack opens an artery, the blood may spray and spatter walls and floors, and puts the creature in imminent danger of bleeding out if untreated.
[[File:all_organs.png|thumb|200px|center|A doctor's cheat sheet.]]
{{Category|Body parts}}

Thirst

2026-06-21T05:21:38Z

Ziusudra: added some adventurers not needing to drink

{{Quality|Exceptional}}
{{av}}

[[Image:Thirsty_Dwarves.gif‎|thumb|right|Dwarves quenching thirst.]]
[[Dwarf|Dwarves]], given time, will eventually get '''thirsty''', as indicated by [[File:status_thirst_icon.png]] / {{Tile|↓|1:1}} blinking over the thirsty dwarf. If a dwarf fails to drink in time, the thirst will proceed to dehydration and eventually death. A dwarf needs to drink about once in every three weeks.

A thirsty dwarf prefers to drink [[Alcohol|booze]] - if none is available, they will go to the nearest [[water]] source and drink, ideally being a [[well]] inside the fortress, but they will drink from a [[river]], [[brook]], or even [[murky pool]]s if there are no other sources of water. A dwarf can live indefinitely on water alone, but without alcohol they will suffer bad thoughts, reduced movement speed/workrate, and combat abilities: making a dwarf's efficiency highly alcohol-dependent. While dwarves prefer an abundance of alcohol, dwarves give water to other dwarves when a dwarf is [[rest|resting]] and when a dwarf can't find something to drink on their own.

Dwarves seem to be capable of subsisting on [[vomit]] and slime in particularly dire times, though this is (as to be expected) traumatizing and will quickly result in mental breakdowns and [[insanity]]. This will usually only happen in cases of dwarves walling themselves in and being forgotten, and in challenging embark locations.

A [[rest|resting]] dwarf will not do anything on their own until they have recovered from recent injuries (preferably inside a [[hospital]]), and will depend on others to provide them with food and drink. They will not be given booze but receive water carried in [[bucket]]s.

Any baby being carried by its mother will effectively leech drink from her, causing her to become thirsty at double the usual rate. This does not, however, count as alcohol - when a baby is close to 1 year old, it will have severe withdrawal.

[[Vampire]]s and [[necromancer]]s never dehydrate and thus never drink water, but still enjoy consuming [[alcohol]]. In previous versions, [[Werebeast|werebeasts]] also did not need to drink, but this has since been fixed.

Most types of humanoids who join a [[Fortress mode|fortress]], such as [[Human|humans]] and [[Elf|elves]] need to drink, [[Food|eat]], and [[sleep]]. In [[adventure mode]], these needs are only tracked for the currently-controlled character, and some creature types that can become playable after joining other civilizations, do not need to drink, like [[goblin]]s and [[experiment]]s.

==Detailed mechanics==

Thirst increments by 1 during each game [[Time|tick]] ''(i.e. 1,200 per day, 33,600 per month, 403,200 per year)'', possibly more if the dwarf is a mother carrying her child. When it reaches certain thresholds, the following things happen.

===Fortress mode===
:* {{Tooltip|20,000|17 fortress days}} - dwarf starts considering getting something to drink (1/120 chance per tick) if idle
:* {{Tooltip|22,000|18 fortress days}} - dwarf decides to go get something to drink if idle
:* {{Tooltip|25,000|21 fortress days}} - dwarf starts flashing {{dftext|Thirsty|6:0}}
:* {{Tooltip|35,000|29 fortress days}} - dwarf gets an unhappy [[thought]] about being Thirsty, cancels current [[job]] to get something to drink
:* {{Tooltip|50,000|42 fortress days}} - dwarf starts flashing {{dftext|Dehydrated|4:1}}
:* {{Tooltip|60,000|51 fortress days}} - dwarf gets an unhappy thought about being Dehydrated
:* {{Tooltip|75,000|63 fortress days}} - dwarf dies of thirst

===Adventure mode===
:* {{Tooltip|57,600|8 adventure hours}} - adventurer becomes {{dftext|Thirsty|6:0}}
:* {{Tooltip|115,200|16 adventure hours}} - adventurer becomes {{dftext|Thirsty|6:1}}
:* {{Tooltip|172,800|1 adventure day}} - adventurer becomes {{dftext|Very thirsty|5:1}}
:* {{Tooltip|345,600|2 adventure days}} - adventurer becomes {{dftext|Dehydrated|5:1}}
:* {{Tooltip|864,000|5 adventure days}} - adventurer has {{dftext|died of thirst|5:1}}

{{Translation
| dwarven = rëcus
| elvish = pacata
| goblin = strabtom
| human = ethgath
}}
Finishing a drink (either through the {{dftext|Drink|3:1}} job or the {{Adv menu icon|e}} command) decreases the relevant counter by {{Tooltip|50,000|42 fortress days, 7 adventure hours}} (to a minimum of zero), though they may also decrement it additional times during the job's progress. An adventurer drinking a [[contaminant]] (such as tears or liquid on an item) leaves the counter unchanged.

Being dehydrated for even a single [[tick]] will cause a [[miscarriage]] among pregnant dwarves.

Prior to version 0.31.07 (and going all the way back to the 2D versions), the unhappy thoughts resulting from hunger/thirst/drowsiness occurred at the exact same time that the dwarf started flashing, but all of the other numbers were otherwise the same. Additionally, in earlier versions (most notably 40d and earlier) dwarves cancelled jobs for food/drink/sleep much more readily.
{{Category|Dwarves}}
[[ru:Thirst]]

Water

2026-06-21T05:11:47Z

Ziusudra: /* Salt water */ changed adventurer maybe drinking if thirsty enough, removed verify

{{av}}
{{Quality|Exceptional}}
[[File:water_drop_preview.png|right]]
'''Water''' is a [[fluid]] found all over the world. It [[flow]]s from mountain springs, forming the world's [[ocean]]s, [[lake]]s, [[river]]s, and [[brook]]s, falling as [[rain]] and [[snow]], and freezes into [[ice]]. Water is home to a variety of [[Creature#Aquatic|aquatic creatures]]. Many creatures can [[Swimmer|swim]] in deep water, but air-breathing creatures that are submerged in water can [[Swimmer#Drowning|drown]] in it. Water comes in two varieties: '''freshwater''', which makes up almost all inland water, and '''saltwater''', which fills the seas. Some brooks and [[murky pool]]s can be saltwater, even if the fortress site is partially mountainous. - it is not known if this is a bug. To tell the difference, attempt to set up a drinking zone including some of the water in question - if there are zero tiles of [[water source]] available, the water is saltwater. [[Mud]] is a [[contaminant]], which is created any time water covers an area. Any tiles that contain mud may be used for [[farming]].

Water normally will be displayed with a blue tile. You can toggle depth indicators (a white number reflecting the current water level on a given tile) by pressing {{Menu icon|f}} or clicking on the Display Water Levels button to the left of the minimap. Water can also take on other colors indicating [[contaminant|contaminants]], such as '''[[blood]]''', '''ichor''', or '''[[goo]]'''.

Dark-colored water symbols indicate the water is one [[Z-level]] below the camera level. Water has 7 depth levels per tile, with 1 being the equivalent of a shallow puddle, and 7 filling the tile completely. [[Dwarf|Dwarves]] can safely walk through water up to a depth of 3 - at depth 4 or higher, they will cancel jobs due to "Dangerous terrain" and begin to gain [[swimming]] experience. At depth 7, any dwarf that does not have sufficient swimming skill will drown.

Interestingly, water can slow [[Gravity|falls]] - that is, with deep enough water and short enough falls, if the water is deep enough relative to the height of the fall, creatures can be less injured, or even completely uninjured (from a 4-level drop to a 3-level deep pool, for example).

Objects made of [[wood]], including logs, do not float in water; they sink to the bottom like all other objects. Things that enter or fall into water will make visible splashes and ripples.

== Processes ==
=== Evaporation ===
[[File:water_v50_anim.gif|thumb|122px|right|Roughly 4×4 tiles of a [[river]].]]
[[File:water_preview.png|frame|120px|right|A partially flooded fortress. ASCII mode.]]In the normal underground [[temperature]] of {{ct|10015}}, evaporation occurs when water or [[magma]] is at a depth of 1/7. The exact rate of evaporation is unknown, but it is affected by temperature and surrounding liquids - a single 1/7 water tile will evaporate faster than a large recently-flooded area, or a 1/7 water tile by a river, for example.

At high temperatures (usually found in [[Climate#Scorching|scorching climates]]), water can evaporate at greater depths -- even at 7/7. This is generally accompanied by the [[grass]] drying out and turning yellow. Such evaporation can be prevented by [[floor]]ing over water tiles to make them [[Inside]].

Water or magma at 1/7 depth will not evaporate if it is on top of 7/7 depth liquid.

=== Freezing and thawing ===
Many environments get cold enough for water to [[freeze]] in winter. When this happens, any water that is [[Tile attributes|Above Ground]] will freeze into [[ice]]. However, water a single tile away that is in an underground tunnel will not freeze.

When water freezes or thaws, it does so ''instantly''; therefore, any creature [[swimming]] in water when it freezes will <s>die</s> have [[fun]], and anything standing on a frozen pond when it thaws will fall into it and [[swimmer#Drowning|drown]] if it cannot [[swimmer|swim]]. (Note: This is also true in [[adventurer mode]], so keep an eye on the temperature if you plan to cross a river!) When ice walls thaw, they always leave a 7/7 water tile, even if the tile had less than 7/7 when the ice formed.

Mining ice can produce chunks of ice. Taking these chunks into a stone layer will cause them to eventually melt, turning them into [[Liquid|"water" items]] (much like those hauled in [[bucket]]s) which can't be used for anything.{{Bug|360}}

[[Glacier#Cave-in_some ice_|Caving in an ice wall]] into a stone layer will cause it to instantly melt into water (provided it does not become exposed to the outdoors), which can be used to get water near the surface in a [[glacier]] biome without having to use a [[pump]] stack to pump water up from a [[cavern]] pool.

If you constructed a [[well]] or a [[Grate|floor grate]] right over the top of some water and it freezes, the item will be deconstructed to its original parts, but some may fall into the water.

==== Freezing point ====
The freezing point of water, {{ct|10000}}, is an important, if not ''the'' most important, [[temperature]] in ''Dwarf Fortress''. Below this point, water freezes into ice, and above this point, ice will melt into water. A [[biome]] that never dips below this temperature will make obtaining ice next to impossible, and a biome that never rises above this temperature will require underground storage, [[magma]], or an alternative heating method to obtain liquid water.

Although it is most commonly known as the freezing point of water, {{ct|10000}} is also the freezing points of standard [[blood]], ichor, goo, slime, pus, [[milk]], egg white, and egg yolk. [[Nether-cap]]s are naturally constantly at this temperature, but will cause neither water to freeze nor ice to melt. The temperature also acts as the condensation point of [[cave floater]] gas, at which it becomes cave floater juice. As a result of these dependencies, many [[creature]]s will die if they cannot keep their internal body temperature above the freezing point of water.

Below this point, many machine components, including [[screw pump]]s, [[windmill]]s, and [[minecart]] rollers will not work, instead displaying "Frozen here". In colder environments, these machines must either be kept indoors or heated with nearby [[fire]] or [[magma]].

== Lakes and rivers ==
=== Lakes ===
During world generation, the world will create lakes. Lakes are large bodies of still water (for an embark tile at least). They usually have rivers coming to-and-from the lake, giving and exporting water to the lake. Take note, however when embarking with even a partial part of the river on your embark tile, for there have been accounts of the lake being higher than your embark wagon, therefore flooding half of the embark tile. It is unknown whether or not this is a bug, but due to the circumstantial evidence, it most likely is. for more information on lakes, see [[lake]].

===Rivers===
Rivers are bodies of water created during world-gen, that will flow from their starting point, all the way to either a [[lake]], or the [[ocean]]. Rivers can be extremely useful when you embark beside one, however, most rivers have at least a light [[aquifer]] on their tile, therefore making it difficult to settle there. Rivers can be used in many ways to help your fort, but if used improperly, will cause mayhem. for more information concerning rivers, see [[river]].

== Properties ==
=== Depth ===
{{Material properties}}
Water (as well as [[magma]]) can be one of seven different depths. You can find out how deep water is by mousing over the tile containing the water or by turning on {{Menu icon|f}} numeric fluid depth with a button next to the minimap, or in the settings menu under the ''Game'' tab.

Water depth ranges from 0-7, where 0 is no water and 7 is maximum depth. Note that water depth is ''per [[Z-level]]'' (or z-index); that is, if a tile is at depth 7/7, it means that the water ''on that level'' is at maximum depth, not that the water extends down 7 Z-levels. A lake three Z-levels deep, with each level having 7/7 depth, can be thought of as having 21 levels of depth.

Looking at water lower than the depth of its surface can reveal things that are swimming around or have fallen into it.
{| class="wikitable"
|-
! Depth
! Description
|-
| 0
| No water present.
|-
| 1
| Water may evaporate. No effect on dwarven jobs.
|-
| 2
| Knee-deep. Dwarves will suspend build orders if an affected tile has 2/7 or more water.
|-
| 3
| Waist-deep. Water at this depth or lower will cause suffocation in [[aquatic]] creatures.
|-
| 4
| Dangerous terrain. Movement trains [[swimming]]. Dwarves will not path through water at 4/7 or higher. Minimum height to make an ice wall when frozen.
|-
| 5
| Head height. [[Minecart]]s will skip over fluids at this level.
|-
| 6
| Over a dwarf's head, but even non-swimmers can tread water at this height for a time. [[Minecart]]s will collect fluids at this level.
|-
| 7
| Risk of drowning. Can have water on floorless tile above. [[Fortification|Fortifications]] no longer provide a barrier to creature movement.{{Bug|3327}}
|}

=== Sourced water ===
Water that comes from [[aquifer]]s, as well as any water source that extends from the edge of the map ([[river]]s, [[brook]]s, [[ocean]]s, and some [[lake]]s) is considered to be '''sourced water'''. Any sourced water is an endless supply of water that can never run dry, although it can freeze for part or all of the year in colder biomes. Murky pools, although not 'sourced water' as described here, also slowly generate water during [[rain]] storms. This can make it possible for a murky pool to replenish itself even when it has been completely drained.

When using sourced water you should strongly consider installing [[floodgate]]s, and be aware of how [[pressure]] works, or you could easily end up [[flood]]ing your fortress and having a lot more [[fun]] than anticipated.

== Flow ==
{{main|Flow}}
[[File:water_splash_anim.gif|thumb|478px|right|Cut tree logs falling into water, creating splashes and ripples.]]Water and [[magma]] are both fluids which are constantly trying to '''[[flow]]''' into adjacent tiles until they have filled all available space or until they run out of fluid. Fluids technically move in 9 directions: down, and to the sides. Fluids cannot move diagonally up or down. Fluids at a depth of 1/7 no longer attempt to move unless they can move down. Fluids under [[pressure]] can appear to travel upward until the pressure equalizes, though in reality they are moving downward and/or sideways relative to their source. The higher the temperature in the environment, the faster water will flow.

When water falls onto a tile that is already full, the game will always attempt to move it into a non-full tile on the same [[Z-level]] that can be legally reached (i.e. without going through a wall or other obstruction), even if it has to "teleport" the incoming fluid a long distance to do so. Only when all available tiles are full will incoming water "pile up" on top. This behavior can be exploited to move water long distances very quickly (see "Getting rid of unwanted water" below).

If the flow is strong enough, it can move objects such as dwarves, pets, stones, weapons, or corpses.

Fluids in ''Dwarf Fortress'' act like a fairly thick, viscous material. This makes it possible to do highly implausible things like [[pump]] out a dry hole in the middle of a [[river]] or [[ocean]].

== Contamination ==
Water can be contaminated in different ways, both natural and artificial. This contamination can have a negative effect on the water's quality, and can even harm dwarves that ingest it.

=== Salt water ===
Dwarves cannot use salt water directly; while healthy dwarves will usually prefer to drink [[booze]], wounded dwarves can only be given water to drink, so if you have only salt water on your map, it is helpful to desalinate it. In adventurer mode, the controlled character will refuse to drink salt water, even when about to die from dehydration.

To check to see if water is salty, use the {{k|z}} menu and place a water source zone to see how the game shows the pond/pool. If the "Water Source: #" is 0, then the source is salty. If not, then your dwarves will drink it.

A [[screw pump]] or a [[Pressure#Water_in_a_U-Bend|U-bend]] made of stairs can be used to desalinate water. Dwarves will drink water from a well over salt water, give it to sick dwarves and use it to clean wounds. Even if you do not designate the well as a water source (which is unnecessary anyway), the dwarves will still use it.

=== Stagnant water ===

Water taken from a murky pool or wetlands biome will be stagnant, just as water taken from near the ocean will be salty. Dwarves get an unhappy [[thought]] if they have to drink stagnant water, and a [[Health care|patient]] whose [[wound]] is cleaned with stagnant water will have an increased risk of [[Health care#Infection|infection]]. Stagnant water can be purified by the same means as salt water. Also, if clean water (or even salt water) flows into stagnant water, it will convert it to fresh water.{{cite release notes|0.34.09}} Note that water that spawns on the map (such as the output of a screw pump or a dumped bucket) in a tile orthogonally adjacent to a tile of stagnant water, will itself spawn as stagnant water.

The game will describe stagnant water as stagnant if it was in a bucket or [[flask]]/[[waterskin]], and hovering over standing or flowing water with will indicate whether or not it is stagnant.

=== Water laced with mud ===
If a water source is only one Z-level deep and its floor is covered by "a pile of mud" (like most [[cavern|underground pools]]), then any water taken from it will be "water laced with mud". Drinking water laced with mud will give your dwarves an unhappy thought. It might also cause [[Health care#Infection|infection]] if used to clean a [[wound]], similarly to stagnant water.

Unlike stagnant water, merely moving the water with flow or gravity, or keeping a level of water higher than one Z-level will take care of the problem, since it only occurs if the water source tile contains "a pile of mud", and water coming into contact with a clean floor only creates "a dusting of mud".

=== Contaminants ===
Water can be tainted by [[Contaminant|contaminants]] - it is considered tainted when the specific tile in question has more than a dusting/spattering directly on it. Water can be tainted by a contaminated creature going through it, by flowing over dirty items or terrain, directly spilling contaminant into a tile, or by placing LIQUID_MISC items straight into water. Water can wash contaminants into walls, but walls will not spread contaminants to water.

If a creature walks through contaminated water without [[shoes]], they'll come into contact with contaminants therein{{Verify}}, transferring any contact [[syndrome]]s. However, water contaminants obtained on creatures as a result of this process will not be considered tainted.

Water items - such as in buckets when withdrawing water from a well - will always describe what contaminant they're tainted by. However, emptying out the buckets will not produce the contaminant. Additionally, stagnant and salt are special types of contaminants that change the description of liquid water itself.

A dwarf that drinks the contaminated water will be affected by the contaminant if it has ingestion or contact syndrome, and contaminated water is always considered dirty, giving an unhappy thought to the dwarf.

Contaminants that get into water currently can do very strange things. A pool of [[blood]] that gets covered by water will be pushed out of the water as the water flows, creating more pools of blood at the edge of the water. Overflowing a large reservoir that contains contaminants of blood will generate a large amount of blood very quickly. This behavior is thought to be <strike>the will of Armok</strike> a bug.{{Verify}}

== Getting rid of unwanted water ==
Water will flow off the edge of the map endlessly, which is one way to get rid of large amounts of water (evaporation works better with small amounts). Underground, there are at least two ways to accomplish this. One is to channel your excess water into a dry cavern that is open to the map edge, as the water will flow out (depending on slopes, original water level and such). Be careful if you dump the water into an underground lake, as such lakes have some sort of equilibrium built into them, and your excess water may cause them to flood. The other, probably easier method, is to mine to the map edge (since you cannot mine the map edge itself, just up to it), then smooth the edge and then carve [[fortification]]s into it. Water will flow through the fortifications and off the edge of the map. Make sure your exit flow is equal to or, for safety, greater than your input.

Draining lakes and oceans from underneath can be a finicky task, but there's a bit of dwarven magic for it: build a retractable bridge on the level beneath the sea bottom, with ramps directly underneath it. Link this to a lever to control the flow as you desire. Now evacuate the dwarves and wall off the area above the bridge. Then, with the bridge in place, designate ramps around the bridge leading up - breaking through to the sea bottom. Now how can the dwarves dig these squares out? Yep, from beneath the bridge. In this way, they get the water flow started without ever getting their feet wet. This is a great way to set up channels one square in from the map edge near a water source, so that you can properly wall off the baddies from getting into the fort.

'''NOTE: This technique no longer works. Attempt at your own risk.''' If you simply need to tap a single tile of the bottom of a lake/ocean there is a simple <s>and completely foolproof</s> way to do it; dig a tunnel under the lake, and place a door at the very end of the tunnel. Now order the dwarf to dig an upward ramp at the end of the corridor (the upward ramp will pierce the bottom of the lake), he will do so while standing in the door tile and once he finishes digging he will take a step back and the door will automatically close preventing water from following the miner. The final step is to connect a lever to the door and pull the lever to open the door. Done right, this method allows piercing even the deepest lakes without risk to the miner and also provides a way of blocking the flow in future.

Due to the way the game handles water flow, making your drainage vertical rather than horizontal whenever possible will drain water much more quickly and efficiently. IE: A tunnel one tile wide and two Z-levels deep will drain water considerably faster than a 2 tile wide tunnel on a single Z-level.

Dwarves, especially babies, have an almost-supernatural talent for finding ways to get washed down drains. Putting [[grate]]s or floor [[bars]] over any drainage holes, no matter how unlikely they seem, will reduce tantrums by grieving parents.
[[File:water_preview2.jpg|thumb|250px|center|Liquid of life. or more commonly in Dwarf Fortress: liquid of !!FUN!!]]
{{Translation
| dwarven = arel
| elvish = alu
| goblin = esp
| human = thomo
}}

{{gamedata|{{raw|DF2014:hardcoded_materials.txt|MATERIAL|WATER}}}}
{{materials}}

{{Category|Physics}}
[[ru:Water]]

Thirst

2026-06-21T05:06:59Z

Ziusudra: /* Adventure mode */ added death threshold (for a dwarf at least), and drinking contaminant

{{Quality|Exceptional}}
{{av}}

[[Image:Thirsty_Dwarves.gif‎|thumb|right|Dwarves quenching thirst.]]
[[Dwarf|Dwarves]], given time, will eventually get '''thirsty''', as indicated by [[File:status_thirst_icon.png]] / {{Tile|↓|1:1}} blinking over the thirsty dwarf. If a dwarf fails to drink in time, the thirst will proceed to dehydration and eventually death. A dwarf needs to drink about once in every three weeks.

A thirsty dwarf prefers to drink [[Alcohol|booze]] - if none is available, they will go to the nearest [[water]] source and drink, ideally being a [[well]] inside the fortress, but they will drink from a [[river]], [[brook]], or even [[murky pool]]s if there are no other sources of water. A dwarf can live indefinitely on water alone, but without alcohol they will suffer bad thoughts, reduced movement speed/workrate, and combat abilities: making a dwarf's efficiency highly alcohol-dependent. While dwarves prefer an abundance of alcohol, dwarves give water to other dwarves when a dwarf is [[rest|resting]] and when a dwarf can't find something to drink on their own.

Dwarves seem to be capable of subsisting on [[vomit]] and slime in particularly dire times, though this is (as to be expected) traumatizing and will quickly result in mental breakdowns and [[insanity]]. This will usually only happen in cases of dwarves walling themselves in and being forgotten, and in challenging embark locations.

A [[rest|resting]] dwarf will not do anything on their own until they have recovered from recent injuries (preferably inside a [[hospital]]), and will depend on others to provide them with food and drink. They will not be given booze but receive water carried in [[bucket]]s.

Any baby being carried by its mother will effectively leech drink from her, causing her to become thirsty at double the usual rate. This does not, however, count as alcohol - when a baby is close to 1 year old, it will have severe withdrawal.

[[Vampire]]s and [[necromancer]]s never dehydrate and thus never drink water, but still enjoy consuming [[alcohol]]. In previous versions, [[Werebeast|werebeasts]] also did not need to drink, but this has since been fixed.

Most types of humanoids who join a [[Fortress mode|fortress]], such as [[Human|humans]] and [[Elf|elves]] need to drink, [[Food|eat]], and [[sleep]]. In [[adventure mode]], these needs are only tracked for the currently-controlled character.

==Detailed mechanics==

Thirst increments by 1 during each game [[Time|tick]] ''(i.e. 1,200 per day, 33,600 per month, 403,200 per year)'', possibly more if the dwarf is a mother carrying her child. When it reaches certain thresholds, the following things happen.

===Fortress mode===
:* {{Tooltip|20,000|17 fortress days}} - dwarf starts considering getting something to drink (1/120 chance per tick) if idle
:* {{Tooltip|22,000|18 fortress days}} - dwarf decides to go get something to drink if idle
:* {{Tooltip|25,000|21 fortress days}} - dwarf starts flashing {{dftext|Thirsty|6:0}}
:* {{Tooltip|35,000|29 fortress days}} - dwarf gets an unhappy [[thought]] about being Thirsty, cancels current [[job]] to get something to drink
:* {{Tooltip|50,000|42 fortress days}} - dwarf starts flashing {{dftext|Dehydrated|4:1}}
:* {{Tooltip|60,000|51 fortress days}} - dwarf gets an unhappy thought about being Dehydrated
:* {{Tooltip|75,000|63 fortress days}} - dwarf dies of thirst

===Adventure mode===
:* {{Tooltip|57,600|8 adventure hours}} - adventurer becomes {{dftext|Thirsty|6:0}}
:* {{Tooltip|115,200|16 adventure hours}} - adventurer becomes {{dftext|Thirsty|6:1}}
:* {{Tooltip|172,800|1 adventure day}} - adventurer becomes {{dftext|Very thirsty|5:1}}
:* {{Tooltip|345,600|2 adventure days}} - adventurer becomes {{dftext|Dehydrated|5:1}}
:* {{Tooltip|864,000|5 adventure days}} - adventurer has {{dftext|died of thirst|5:1}}

{{Translation
| dwarven = rëcus
| elvish = pacata
| goblin = strabtom
| human = ethgath
}}
Finishing a drink (either through the {{dftext|Drink|3:1}} job or the {{Adv menu icon|e}} command) decreases the relevant counter by {{Tooltip|50,000|42 fortress days, 7 adventure hours}} (to a minimum of zero), though they may also decrement it additional times during the job's progress. An adventurer drinking a [[contaminant]] (such as tears or liquid on an item) leaves the counter unchanged.

Being dehydrated for even a single [[tick]] will cause a [[miscarriage]] among pregnant dwarves.

Prior to version 0.31.07 (and going all the way back to the 2D versions), the unhappy thoughts resulting from hunger/thirst/drowsiness occurred at the exact same time that the dwarf started flashing, but all of the other numbers were otherwise the same. Additionally, in earlier versions (most notably 40d and earlier) dwarves cancelled jobs for food/drink/sleep much more readily.
{{Category|Dwarves}}
[[ru:Thirst]]

Water

2026-06-20T01:47:02Z

Ziusudra: /* Contamination */ added thirst level exception and verify

{{av}}
{{Quality|Exceptional}}
[[File:water_drop_preview.png|right]]
'''Water''' is a [[fluid]] found all over the world. It [[flow]]s from mountain springs, forming the world's [[ocean]]s, [[lake]]s, [[river]]s, and [[brook]]s, falling as [[rain]] and [[snow]], and freezes into [[ice]]. Water is home to a variety of [[Creature#Aquatic|aquatic creatures]]. Many creatures can [[Swimmer|swim]] in deep water, but air-breathing creatures that are submerged in water can [[Swimmer#Drowning|drown]] in it. Water comes in two varieties: '''freshwater''', which makes up almost all inland water, and '''saltwater''', which fills the seas. Some brooks and [[murky pool]]s can be saltwater, even if the fortress site is partially mountainous. - it is not known if this is a bug. To tell the difference, attempt to set up a drinking zone including some of the water in question - if there are zero tiles of [[water source]] available, the water is saltwater. [[Mud]] is a [[contaminant]], which is created any time water covers an area. Any tiles that contain mud may be used for [[farming]].

Water normally will be displayed with a blue tile. You can toggle depth indicators (a white number reflecting the current water level on a given tile) by pressing {{Menu icon|f}} or clicking on the Display Water Levels button to the left of the minimap. Water can also take on other colors indicating [[contaminant|contaminants]], such as '''[[blood]]''', '''ichor''', or '''[[goo]]'''.

Dark-colored water symbols indicate the water is one [[Z-level]] below the camera level. Water has 7 depth levels per tile, with 1 being the equivalent of a shallow puddle, and 7 filling the tile completely. [[Dwarf|Dwarves]] can safely walk through water up to a depth of 3 - at depth 4 or higher, they will cancel jobs due to "Dangerous terrain" and begin to gain [[swimming]] experience. At depth 7, any dwarf that does not have sufficient swimming skill will drown.

Interestingly, water can slow [[Gravity|falls]] - that is, with deep enough water and short enough falls, if the water is deep enough relative to the height of the fall, creatures can be less injured, or even completely uninjured (from a 4-level drop to a 3-level deep pool, for example).

Objects made of [[wood]], including logs, do not float in water; they sink to the bottom like all other objects. Things that enter or fall into water will make visible splashes and ripples.

== Processes ==
=== Evaporation ===
[[File:water_v50_anim.gif|thumb|122px|right|Roughly 4×4 tiles of a [[river]].]]
[[File:water_preview.png|frame|120px|right|A partially flooded fortress. ASCII mode.]]In the normal underground [[temperature]] of {{ct|10015}}, evaporation occurs when water or [[magma]] is at a depth of 1/7. The exact rate of evaporation is unknown, but it is affected by temperature and surrounding liquids - a single 1/7 water tile will evaporate faster than a large recently-flooded area, or a 1/7 water tile by a river, for example.

At high temperatures (usually found in [[Climate#Scorching|scorching climates]]), water can evaporate at greater depths -- even at 7/7. This is generally accompanied by the [[grass]] drying out and turning yellow. Such evaporation can be prevented by [[floor]]ing over water tiles to make them [[Inside]].

Water or magma at 1/7 depth will not evaporate if it is on top of 7/7 depth liquid.

=== Freezing and thawing ===
Many environments get cold enough for water to [[freeze]] in winter. When this happens, any water that is [[Tile attributes|Above Ground]] will freeze into [[ice]]. However, water a single tile away that is in an underground tunnel will not freeze.

When water freezes or thaws, it does so ''instantly''; therefore, any creature [[swimming]] in water when it freezes will <s>die</s> have [[fun]], and anything standing on a frozen pond when it thaws will fall into it and [[swimmer#Drowning|drown]] if it cannot [[swimmer|swim]]. (Note: This is also true in [[adventurer mode]], so keep an eye on the temperature if you plan to cross a river!) When ice walls thaw, they always leave a 7/7 water tile, even if the tile had less than 7/7 when the ice formed.

Mining ice can produce chunks of ice. Taking these chunks into a stone layer will cause them to eventually melt, turning them into [[Liquid|"water" items]] (much like those hauled in [[bucket]]s) which can't be used for anything.{{Bug|360}}

[[Glacier#Cave-in_some ice_|Caving in an ice wall]] into a stone layer will cause it to instantly melt into water (provided it does not become exposed to the outdoors), which can be used to get water near the surface in a [[glacier]] biome without having to use a [[pump]] stack to pump water up from a [[cavern]] pool.

If you constructed a [[well]] or a [[Grate|floor grate]] right over the top of some water and it freezes, the item will be deconstructed to its original parts, but some may fall into the water.

==== Freezing point ====
The freezing point of water, {{ct|10000}}, is an important, if not ''the'' most important, [[temperature]] in ''Dwarf Fortress''. Below this point, water freezes into ice, and above this point, ice will melt into water. A [[biome]] that never dips below this temperature will make obtaining ice next to impossible, and a biome that never rises above this temperature will require underground storage, [[magma]], or an alternative heating method to obtain liquid water.

Although it is most commonly known as the freezing point of water, {{ct|10000}} is also the freezing points of standard [[blood]], ichor, goo, slime, pus, [[milk]], egg white, and egg yolk. [[Nether-cap]]s are naturally constantly at this temperature, but will cause neither water to freeze nor ice to melt. The temperature also acts as the condensation point of [[cave floater]] gas, at which it becomes cave floater juice. As a result of these dependencies, many [[creature]]s will die if they cannot keep their internal body temperature above the freezing point of water.

Below this point, many machine components, including [[screw pump]]s, [[windmill]]s, and [[minecart]] rollers will not work, instead displaying "Frozen here". In colder environments, these machines must either be kept indoors or heated with nearby [[fire]] or [[magma]].

== Lakes and rivers ==
=== Lakes ===
During world generation, the world will create lakes. Lakes are large bodies of still water (for an embark tile at least). They usually have rivers coming to-and-from the lake, giving and exporting water to the lake. Take note, however when embarking with even a partial part of the river on your embark tile, for there have been accounts of the lake being higher than your embark wagon, therefore flooding half of the embark tile. It is unknown whether or not this is a bug, but due to the circumstantial evidence, it most likely is. for more information on lakes, see [[lake]].

===Rivers===
Rivers are bodies of water created during world-gen, that will flow from their starting point, all the way to either a [[lake]], or the [[ocean]]. Rivers can be extremely useful when you embark beside one, however, most rivers have at least a light [[aquifer]] on their tile, therefore making it difficult to settle there. Rivers can be used in many ways to help your fort, but if used improperly, will cause mayhem. for more information concerning rivers, see [[river]].

== Properties ==
=== Depth ===
{{Material properties}}
Water (as well as [[magma]]) can be one of seven different depths. You can find out how deep water is by mousing over the tile containing the water or by turning on {{Menu icon|f}} numeric fluid depth with a button next to the minimap, or in the settings menu under the ''Game'' tab.

Water depth ranges from 0-7, where 0 is no water and 7 is maximum depth. Note that water depth is ''per [[Z-level]]'' (or z-index); that is, if a tile is at depth 7/7, it means that the water ''on that level'' is at maximum depth, not that the water extends down 7 Z-levels. A lake three Z-levels deep, with each level having 7/7 depth, can be thought of as having 21 levels of depth.

Looking at water lower than the depth of its surface can reveal things that are swimming around or have fallen into it.
{| class="wikitable"
|-
! Depth
! Description
|-
| 0
| No water present.
|-
| 1
| Water may evaporate. No effect on dwarven jobs.
|-
| 2
| Knee-deep. Dwarves will suspend build orders if an affected tile has 2/7 or more water.
|-
| 3
| Waist-deep. Water at this depth or lower will cause suffocation in [[aquatic]] creatures.
|-
| 4
| Dangerous terrain. Movement trains [[swimming]]. Dwarves will not path through water at 4/7 or higher. Minimum height to make an ice wall when frozen.
|-
| 5
| Head height. [[Minecart]]s will skip over fluids at this level.
|-
| 6
| Over a dwarf's head, but even non-swimmers can tread water at this height for a time. [[Minecart]]s will collect fluids at this level.
|-
| 7
| Risk of drowning. Can have water on floorless tile above. [[Fortification|Fortifications]] no longer provide a barrier to creature movement.{{Bug|3327}}
|}

=== Sourced water ===
Water that comes from [[aquifer]]s, as well as any water source that extends from the edge of the map ([[river]]s, [[brook]]s, [[ocean]]s, and some [[lake]]s) is considered to be '''sourced water'''. Any sourced water is an endless supply of water that can never run dry, although it can freeze for part or all of the year in colder biomes. Murky pools, although not 'sourced water' as described here, also slowly generate water during [[rain]] storms. This can make it possible for a murky pool to replenish itself even when it has been completely drained.

When using sourced water you should strongly consider installing [[floodgate]]s, and be aware of how [[pressure]] works, or you could easily end up [[flood]]ing your fortress and having a lot more [[fun]] than anticipated.

== Flow ==
{{main|Flow}}
[[File:water_splash_anim.gif|thumb|478px|right|Cut tree logs falling into water, creating splashes and ripples.]]Water and [[magma]] are both fluids which are constantly trying to '''[[flow]]''' into adjacent tiles until they have filled all available space or until they run out of fluid. Fluids technically move in 9 directions: down, and to the sides. Fluids cannot move diagonally up or down. Fluids at a depth of 1/7 no longer attempt to move unless they can move down. Fluids under [[pressure]] can appear to travel upward until the pressure equalizes, though in reality they are moving downward and/or sideways relative to their source. The higher the temperature in the environment, the faster water will flow.

When water falls onto a tile that is already full, the game will always attempt to move it into a non-full tile on the same [[Z-level]] that can be legally reached (i.e. without going through a wall or other obstruction), even if it has to "teleport" the incoming fluid a long distance to do so. Only when all available tiles are full will incoming water "pile up" on top. This behavior can be exploited to move water long distances very quickly (see "Getting rid of unwanted water" below).

If the flow is strong enough, it can move objects such as dwarves, pets, stones, weapons, or corpses.

Fluids in ''Dwarf Fortress'' act like a fairly thick, viscous material. This makes it possible to do highly implausible things like [[pump]] out a dry hole in the middle of a [[river]] or [[ocean]].

== Contamination ==
Water can be contaminated in different ways, both natural and artificial. This contamination can have a negative effect on the water's quality, and can even harm dwarves that ingest it.

=== Salt water ===
Dwarves cannot use salt water directly; while healthy dwarves will usually prefer to drink [[booze]], wounded dwarves can only be given water to drink, so if you have only salt water on your map, it is helpful to desalinate it. In adventurer mode, the controlled character will refuse to drink salt water, though they might if thirsty enough{{verify|... or even more disgusting things? They'll eat vermin when starving.}}.

To check to see if water is salty, use the {{k|z}} menu and place a water source zone to see how the game shows the pond/pool. If the "Water Source: #" is 0, then the source is salty. If not, then your dwarves will drink it.

A [[screw pump]] or a [[Pressure#Water_in_a_U-Bend|U-bend]] made of stairs can be used to desalinate water. Dwarves will drink water from a well over salt water, give it to sick dwarves and use it to clean wounds. Even if you do not designate the well as a water source (which is unnecessary anyway), the dwarves will still use it.

=== Stagnant water ===

Water taken from a murky pool or wetlands biome will be stagnant, just as water taken from near the ocean will be salty. Dwarves get an unhappy [[thought]] if they have to drink stagnant water, and a [[Health care|patient]] whose [[wound]] is cleaned with stagnant water will have an increased risk of [[Health care#Infection|infection]]. Stagnant water can be purified by the same means as salt water. Also, if clean water (or even salt water) flows into stagnant water, it will convert it to fresh water.{{cite release notes|0.34.09}} Note that water that spawns on the map (such as the output of a screw pump or a dumped bucket) in a tile orthogonally adjacent to a tile of stagnant water, will itself spawn as stagnant water.

The game will describe stagnant water as stagnant if it was in a bucket or [[flask]]/[[waterskin]], and looking at standing or flowing water with {{K|k}} will indicate whether or not it is stagnant.

=== Water laced with mud ===
If a water source is only one Z-level deep and its floor is covered by "a pile of mud" (like most [[cavern|underground pools]]), then any water taken from it will be "water laced with mud". Drinking water laced with mud will give your dwarves an unhappy thought. It might also cause [[Health care#Infection|infection]] if used to clean a [[wound]], similarly to stagnant water.

Unlike stagnant water, merely moving the water with flow or gravity, or keeping a level of water higher than one Z-level will take care of the problem, since it only occurs if the water source tile contains "a pile of mud", and water coming into contact with a clean floor only creates "a dusting of mud".

=== Contaminants ===
Water can be tainted by [[Contaminant|contaminants]] - it is considered tainted when the specific tile in question has more than a dusting/spattering directly on it. Water can be tainted by a contaminated creature going through it, by flowing over dirty items or terrain, directly spilling contaminant into a tile, or by placing LIQUID_MISC items straight into water. Water can wash contaminants into walls, but walls will not spread contaminants to water.

If a creature walks through contaminated water without [[shoes]], they'll come into contact with contaminants therein{{Verify}}, transferring any contact [[syndrome]]s. However, water contaminants obtained on creatures as a result of this process will not be considered tainted.

Water items - such as in buckets when withdrawing water from a well - will always describe what contaminant they're tainted by. However, emptying out the buckets will not produce the contaminant. Additionally, stagnant and salt are special types of contaminants that change the description of liquid water itself.

A dwarf that drinks the contaminated water will be affected by the contaminant if it has ingestion or contact syndrome, and contaminated water is always considered dirty, giving an unhappy thought to the dwarf.

Contaminants that get into water currently can do very strange things. A pool of [[blood]] that gets covered by water will be pushed out of the water as the water flows, creating more pools of blood at the edge of the water. Overflowing a large reservoir that contains contaminants of blood will generate a large amount of blood very quickly. This behavior is thought to be <strike>the will of Armok</strike> a bug.{{Verify}}

== Getting rid of unwanted water ==
Water will flow off the edge of the map endlessly, which is one way to get rid of large amounts of water (evaporation works better with small amounts). Underground, there are at least two ways to accomplish this. One is to channel your excess water into a dry cavern that is open to the map edge, as the water will flow out (depending on slopes, original water level and such). Be careful if you dump the water into an underground lake, as such lakes have some sort of equilibrium built into them, and your excess water may cause them to flood. The other, probably easier method, is to mine to the map edge (since you cannot mine the map edge itself, just up to it), then smooth the edge and then carve [[fortification]]s into it. Water will flow through the fortifications and off the edge of the map. Make sure your exit flow is equal to or, for safety, greater than your input.

Draining lakes and oceans from underneath can be a finicky task, but there's a bit of dwarven magic for it: build a retractable bridge on the level beneath the sea bottom, with ramps directly underneath it. Link this to a lever to control the flow as you desire. Now evacuate the dwarves and wall off the area above the bridge. Then, with the bridge in place, designate ramps around the bridge leading up - breaking through to the sea bottom. Now how can the dwarves dig these squares out? Yep, from beneath the bridge. In this way, they get the water flow started without ever getting their feet wet. This is a great way to set up channels one square in from the map edge near a water source, so that you can properly wall off the baddies from getting into the fort.

'''NOTE: This technique no longer works. Attempt at your own risk.''' If you simply need to tap a single tile of the bottom of a lake/ocean there is a simple <s>and completely foolproof</s> way to do it; dig a tunnel under the lake, and place a door at the very end of the tunnel. Now order the dwarf to dig an upward ramp at the end of the corridor (the upward ramp will pierce the bottom of the lake), he will do so while standing in the door tile and once he finishes digging he will take a step back and the door will automatically close preventing water from following the miner. The final step is to connect a lever to the door and pull the lever to open the door. Done right, this method allows piercing even the deepest lakes without risk to the miner and also provides a way of blocking the flow in future.

Due to the way the game handles water flow, making your drainage vertical rather than horizontal whenever possible will drain water much more quickly and efficiently. IE: A tunnel one tile wide and two Z-levels deep will drain water considerably faster than a 2 tile wide tunnel on a single Z-level.

Dwarves, especially babies, have an almost-supernatural talent for finding ways to get washed down drains. Putting [[grate]]s or floor [[bars]] over any drainage holes, no matter how unlikely they seem, will reduce tantrums by grieving parents.
[[File:water_preview2.jpg|thumb|250px|center|Liquid of life. or more commonly in Dwarf Fortress: liquid of !!FUN!!]]
{{Translation
| dwarven = arel
| elvish = alu
| goblin = esp
| human = thomo
}}

{{gamedata|{{raw|DF2014:hardcoded_materials.txt|MATERIAL|WATER}}}}
{{materials}}

{{Category|Physics}}
[[ru:Water]]

Petition

2026-06-13T22:50:52Z

Ziusudra: added version template for accepted temple petition screen shot

{{Quality|Fine}}
{{av}}
[[File:petition_sprite_preview.png|right]]'''Petitions''' are formal demands from foreign entities, be they single [[visitor]]s or [[army|armies]]. They may range from relatively mundane to dramatic with far-ranging consequences for your fort. Petitions are distinct from [[diplomat]]ic agreements with other [[civilization]]s, such as the tree-cutting quota with [[elves]], or peace treaties.

Petitions may be delivered by a foreign petitioner meeting with your [[mayor]] at their [[office]], or they may be more abstract. In both cases, a blinking 'P' will appear on the game screen, indicating that one is pending and awaiting review by the player.{{verify|Isn't this blinking 'P' a pre-v50 thing?}} It is not possible to consult the petitions screen if none are pending. When a petition announcement appears, the following icon will be shown: 
[[File:petition_icon_anim.gif]]

There are currently eight kinds of petitions:
[[File:petition_example.png|thumb|300px|right|Example of a petition of someone wanting to enter your fort and entertain [[alcohol|inebriated]] dwarves.]]
*Petition for [[Long-term resident|long-term residency]] by a passing [[visitor]]; stating the purpose of their stay (entertainment, [[soldier]]ing, study, or slaying monsters) which you are free to accept or not. If you do, they will reside at your [[tavern]] and will not do any other labors than those they were intent on doing. [[Soldier]]ing visitors can be assigned to [[squad]]s, but they cannot be appointed as [[Militia captain]]s.
*Petition for sanctuary by non-citizens of your civilization that you rescue during [[mission]]s. These grateful souls will remain at your fort once granted sanctuary, and can be assigned rooms or work preferences like your actual citizens. However, they cannot be assigned to the military or nobility roles.
*Petition for [[citizenship]] by a long-term resident, usually after living in the fort for two years or so (mercenaries and monster slayers do not ever request this). Accepting the petition turns the resident into a full-fledged citizen of your fort, the same as your dwarves, and their labor preferences can be assigned.
[[File:Accepted Petition.png|thumb|200px|right|An accepted petition for a temple.{{version|53.12}}]]
*Petition for a [[temple]] or [[guildhall]]: If you have many dwarves worshiping the same god, or members of a guild, they may request that you construct them a meeting location with enough [[Zone#Quality_and_value|value]] to be considered a Guildhall or Temple (2000☼). This requirement is tripled (to 6000☼) if the Economy is set to Hard at Embark. Accepting the petition will give these dwarves a positive [[thought]], while rejecting it will give a negative thought. Building a guild hall after accepting it will give them another positive thought.
*Petition for a grand guildhall: Similarly to the previous one, once numerous dwarves are members of a guild, they may request to upgrade their guildhall to a grand guillhall (10000☼). This requirement is tripled (to 30000☼) if the Economy is set to Hard at Embark. Again, accepting and fulfilling the petition will give the dwarves positive thoughts, while rejecting it will give them a negative thought.
*Petition for a [[priest]]: Once you have many dwarves worshiping at a temple or shrine, they will request a specially-designated priest for that location - the priest must be chosen from among that temple's members.
*Petition for an [[artifact]] by a passing [[quester]]. If you accept, a job will be created to deliver the artifact to the visitor, who will then leave. Otherwise, they may do one of the following: turn hostile, leave and sneak back in to attempt to steal it, or report back to the entity they represent, with possible adverse consequences for your fort in the form of a [[siege]].
[[File:army_parley_preview.png|thumb|140px|right|Option for a parley, given by a goblin army.]]
*Petition for parley by an invading [[army]]. This one is delivered abstractly (presumably at shouting distance). The army will camp at the edge of the map, waiting for your response (they will attack if ignored for too long). If you accept, a dwarf will be sent out for the parley, which will inevitably involve the surrender of an artifact that you failed to give to a [[quester]] previously. The parley is fair: the army will not betray you and attack anyway if you give in to their demand, and even if you do not, they will give the herald sufficient time to retreat back to your fortress before they attack.

{{D for Dwarf}}

Occasionally heavily armed, lone [[human]] adventurers will wander to your fortress asking for signatures for a petition to have [[Mandate|whiny]] [[Noble|nobles]] play [[Dwarf Fortress|violent games]]. Such a frivolous and subversive petition carries no legal weight in the Dwarven legal system, but it is best to sign them anyway, or else they may - to use a human expression - [[Berserk|"go postal".]]

{{Category|Game mechanics}}{{Category|Fortress mode}}
[[ru:Petition]]

Petition

2026-06-13T22:43:05Z

Ziusudra: reordered petition types so screen shots line up with their types at wider resolutions

{{Quality|Fine}}
{{av}}
[[File:petition_sprite_preview.png|right]]'''Petitions''' are formal demands from foreign entities, be they single [[visitor]]s or [[army|armies]]. They may range from relatively mundane to dramatic with far-ranging consequences for your fort. Petitions are distinct from [[diplomat]]ic agreements with other [[civilization]]s, such as the tree-cutting quota with [[elves]], or peace treaties.

Petitions may be delivered by a foreign petitioner meeting with your [[mayor]] at their [[office]], or they may be more abstract. In both cases, a blinking 'P' will appear on the game screen, indicating that one is pending and awaiting review by the player.{{verify|Isn't this blinking 'P' a pre-v50 thing?}} It is not possible to consult the petitions screen if none are pending. When a petition announcement appears, the following icon will be shown: 
[[File:petition_icon_anim.gif]]

There are currently eight kinds of petitions:
[[File:petition_example.png|thumb|300px|right|Example of a petition of someone wanting to enter your fort and entertain [[alcohol|inebriated]] dwarves.]]
*Petition for [[Long-term resident|long-term residency]] by a passing [[visitor]]; stating the purpose of their stay (entertainment, [[soldier]]ing, study, or slaying monsters) which you are free to accept or not. If you do, they will reside at your [[tavern]] and will not do any other labors than those they were intent on doing. [[Soldier]]ing visitors can be assigned to [[squad]]s, but they cannot be appointed as [[Militia captain]]s.
*Petition for sanctuary by non-citizens of your civilization that you rescue during [[mission]]s. These grateful souls will remain at your fort once granted sanctuary, and can be assigned rooms or work preferences like your actual citizens. However, they cannot be assigned to the military or nobility roles.
*Petition for [[citizenship]] by a long-term resident, usually after living in the fort for two years or so (mercenaries and monster slayers do not ever request this). Accepting the petition turns the resident into a full-fledged citizen of your fort, the same as your dwarves, and their labor preferences can be assigned.
[[File:Accepted Petition.png|thumb|200px|right|An accepted petition for a temple.]]
*Petition for a [[temple]] or [[guildhall]]: If you have many dwarves worshiping the same god, or members of a guild, they may request that you construct them a meeting location with enough [[Zone#Quality_and_value|value]] to be considered a Guildhall or Temple (2000☼). This requirement is tripled (to 6000☼) if the Economy is set to Hard at Embark. Accepting the petition will give these dwarves a positive [[thought]], while rejecting it will give a negative thought. Building a guild hall after accepting it will give them another positive thought.
*Petition for a grand guildhall: Similarly to the previous one, once numerous dwarves are members of a guild, they may request to upgrade their guildhall to a grand guillhall (10000☼). This requirement is tripled (to 30000☼) if the Economy is set to Hard at Embark. Again, accepting and fulfilling the petition will give the dwarves positive thoughts, while rejecting it will give them a negative thought.
*Petition for a [[priest]]: Once you have many dwarves worshiping at a temple or shrine, they will request a specially-designated priest for that location - the priest must be chosen from among that temple's members.
*Petition for an [[artifact]] by a passing [[quester]]. If you accept, a job will be created to deliver the artifact to the visitor, who will then leave. Otherwise, they may do one of the following: turn hostile, leave and sneak back in to attempt to steal it, or report back to the entity they represent, with possible adverse consequences for your fort in the form of a [[siege]].
[[File:army_parley_preview.png|thumb|140px|right|Option for a parley, given by a goblin army.]]
*Petition for parley by an invading [[army]]. This one is delivered abstractly (presumably at shouting distance). The army will camp at the edge of the map, waiting for your response (they will attack if ignored for too long). If you accept, a dwarf will be sent out for the parley, which will inevitably involve the surrender of an artifact that you failed to give to a [[quester]] previously. The parley is fair: the army will not betray you and attack anyway if you give in to their demand, and even if you do not, they will give the herald sufficient time to retreat back to your fortress before they attack.

{{D for Dwarf}}

Occasionally heavily armed, lone [[human]] adventurers will wander to your fortress asking for signatures for a petition to have [[Mandate|whiny]] [[Noble|nobles]] play [[Dwarf Fortress|violent games]]. Such a frivolous and subversive petition carries no legal weight in the Dwarven legal system, but it is best to sign them anyway, or else they may - to use a human expression - [[Berserk|"go postal".]]

{{Category|Game mechanics}}{{Category|Fortress mode}}
[[ru:Petition]]

Petition

2026-06-13T22:36:20Z

Ziusudra: added screen shot of accepted temple petition

{{Quality|Fine}}
{{av}}
[[File:petition_sprite_preview.png|right]]'''Petitions''' are formal demands from foreign entities, be they single [[visitor]]s or [[army|armies]]. They may range from relatively mundane to dramatic with far-ranging consequences for your fort. Petitions are distinct from [[diplomat]]ic agreements with other [[civilization]]s, such as the tree-cutting quota with [[elves]], or peace treaties.

Petitions may be delivered by a foreign petitioner meeting with your [[mayor]] at their [[office]], or they may be more abstract. In both cases, a blinking 'P' will appear on the game screen, indicating that one is pending and awaiting review by the player.{{verify|Isn't this blinking 'P' a pre-v50 thing?}} It is not possible to consult the petitions screen if none are pending. When a petition announcement appears, the following icon will be shown: 
[[File:petition_icon_anim.gif]]

There are currently eight kinds of petitions:
[[File:petition_example.png|thumb|300px|right|Example of a petition of someone wanting to enter your fort and entertain [[alcohol|inebriated]] dwarves.]]
*Petition for [[Long-term resident|long-term residency]] by a passing [[visitor]]; stating the purpose of their stay (entertainment, [[soldier]]ing, study, or slaying monsters) which you are free to accept or not. If you do, they will reside at your [[tavern]] and will not do any other labors than those they were intent on doing. [[Soldier]]ing visitors can be assigned to [[squad]]s, but they cannot be appointed as [[Militia captain]]s.
*Petition for sanctuary by non-citizens of your civilization that you rescue during [[mission]]s. These grateful souls will remain at your fort once granted sanctuary, and can be assigned rooms or work preferences like your actual citizens. However, they cannot be assigned to the military or nobility roles.
*Petition for [[citizenship]] by a long-term resident, usually after living in the fort for two years or so (mercenaries and monster slayers do not ever request this). Accepting the petition turns the resident into a full-fledged citizen of your fort, the same as your dwarves, and their labor preferences can be assigned.
*Petition for an [[artifact]] by a passing [[quester]]. If you accept, a job will be created to deliver the artifact to the visitor, who will then leave. Otherwise, they may do one of the following: turn hostile, leave and sneak back in to attempt to steal it, or report back to the entity they represent, with possible adverse consequences for your fort in the form of a [[siege]].
[[File:army_parley_preview.png|thumb|140px|right|Option for a parley, given by a goblin army.]]
*Petition for parley by an invading [[army]]. This one is delivered abstractly (presumably at shouting distance). The army will camp at the edge of the map, waiting for your response (they will attack if ignored for too long). If you accept, a dwarf will be sent out for the parley, which will inevitably involve the surrender of an artifact that you failed to give to a [[quester]] previously. The parley is fair: the army will not betray you and attack anyway if you give in to their demand, and even if you do not, they will give the herald sufficient time to retreat back to your fortress before they attack.
[[File:Accepted Petition.png|thumb|200px|right|An accepted petition for a temple.]]
*Petition for a [[temple]] or [[guildhall]]: If you have many dwarves worshiping the same god, or members of a guild, they may request that you construct them a meeting location with enough [[Zone#Quality_and_value|value]] to be considered a Guildhall or Temple (2000☼). This requirement is tripled (to 6000☼) if the Economy is set to Hard at Embark. Accepting the petition will give these dwarves a positive [[thought]], while rejecting it will give a negative thought. Building a guild hall after accepting it will give them another positive thought.
*Petition for a grand guildhall: Similarly to the previous one, once numerous dwarves are members of a guild, they may request to upgrade their guildhall to a grand guillhall (10000☼). This requirement is tripled (to 30000☼) if the Economy is set to Hard at Embark. Again, accepting and fulfilling the petition will give the dwarves positive thoughts, while rejecting it will give them a negative thought.
*Petition for a [[priest]]: Once you have many dwarves worshiping at a temple or shrine, they will request a specially-designated priest for that location - the priest must be chosen from among that temple's members.

{{D for Dwarf}}

Occasionally heavily armed, lone [[human]] adventurers will wander to your fortress asking for signatures for a petition to have [[Mandate|whiny]] [[Noble|nobles]] play [[Dwarf Fortress|violent games]]. Such a frivolous and subversive petition carries no legal weight in the Dwarven legal system, but it is best to sign them anyway, or else they may - to use a human expression - [[Berserk|"go postal".]]

{{Category|Game mechanics}}{{Category|Fortress mode}}
[[ru:Petition]]

File:Accepted Petition.png

2026-06-13T22:16:33Z

Ziusudra: Screen shot showing display of active accepted petition below minimap.

== Summary ==
Screen shot showing display of active accepted petition below minimap.
== Licensing ==
{{Non-free Dwarf Fortress Screenshot}}

Development arc

2026-06-10T22:44:45Z

Ziusudra: /* Future */ added dino release announcement

In earlier days of ''Dwarf Fortress'', development was split up into outlined specific '''Arcs'''. That system has been replaced by a short list of future releases given names after their main focus by [[Toady One]].

== Named Releases ==
=== Future ===
==== Next ====
* [https://youtu.be/LTV5R7JIMQY?t=113 Prehistoric and extinct animals], coming [https://store.steampowered.com/news/app/975370/view/688634078777311387 June 25th, 2026].
* A second siege release focused "[[Release_information/53.07#What.27s_Next_for_Sieges.3F|on magic, armies, and diplomacy]]".

==== Later ====
* The adventure mode site building: the return of [[Camp#Adventurer_camps|camp founding and building]], plus more "cross-mode play and Adventure mode crafting".
* The map rewrites: A rework of the generated spaces and regions, allowing for more dynamic and reactive worlds, with changes focused on the underground, but also some changes above. It has been previously known as the "Big Wait" before myth and magic, but is planned to be released incrementally alongside smaller magical features.
* More villains releases: the continuation of the villains release, finishing what was left when focus shifted to the premium release, divided into multiple smaller releases.
* More myth and magic, world changes, "probably through covens and religion", starting scenarios, and civilization improvements.
==== Sources ====
* ''[https://store.steampowered.com/news/app/975370/view/688634078777311387 Dinos are coming June 25th! 🦖 Dwarf Fortress Dev Update]''
* ''[https://www.bay12forums.com/smf//index.php?topic=183664.0 The Bay 12 Games Report, January 1st 2026]''
* ''[https://store.steampowered.com/news/app/975370/view/520859243419533943 Dwarf Fortress Patch 53.07 🏹 What’s next for Sieges? + New animal portraits]'' Steam news.
* ''[https://www.youtube.com/watch?v=cbzttKQofFg What's Next for Sieges? - Tarn Time (Winter 2025)]'' YouTube video.
* ''[https://www.bay12games.com/dwarves/dev.html Dwarf Fortress Development]'' Bay 12 Games website page (last updated: December 18, 2025).
* ''[https://store.steampowered.com/news/app/975370/view/530964346754301996 Next Steps for Dwarf Fortress + Patch 51.05 ⛏ Dwarf Fortress Dev News]'' Steam news.
* ''[https://www.youtube.com/watch?v=zw_-jdN8zcA Tarn Time - Dwarf Fortress Seasonal Update (Spring 2025)]'' YouTube video.

=== Possible Future ===
These are things that have been discussed as future releases, but have not been officially announced.
* More [[Lua]] functionality, including UI exposure to allow for more mouse versus keyboard control flexibility.
* The boats release: will feature, well, boats, with all that entails (ports, maritime trade routes, pirates, and so on). Probably multi-tile creatures as well, as mechanics on how to make boats (floating superstructures) work will be borrowed to make multi-tile creatures as well.
* The economy release: will piggyback on the new trade and property stuff to establish a new framework that will completely overhaul the old (and deactivated) [[economy]] system.

=== Past ===
* The [[night creature]] release ([[v0.34:Release_information|0.34.01]]): added [[necromancer]]s, [[mummy|mummies]], [[vampire]]s, [[werebeast]]s as well as a complete [[undead]] overhaul. Other notable additions include evil [[weather]], improved human [[site]]s featuring [[catacombs]], [[sewer]]s and [[dungeon]]s, and a number of animals added to the game.
* The [[World activities|world activation]] release ([[DF2014:Release_information/0.40.01|0.40.01]]): allowed many [[world generation]] activities to carry on during normal gameplay, as opposed to a static world. Other notable additions include non-human [[site]]s, multi-tile trees, retireable fortresses, claimable non-player fortresses and a great variety of plants and additional animal people.
* The [[tavern]] release ([[DF2014:Release_information/0.42.01|0.42.01]]): added taverns and [[visitor]]s to the game. Other notable additions include fortress [[temple]]s, [[library|libraries]] (with [[scholar]]s complete with a [[knowledge]] system), a [[paper]] industry, art forms (music, dance and writing) and non-dwarven citizens.
* The [[artifact]] release ([[DF2014:Release_information/0.44.01|0.44.01]]): added non-player artifacts to the game. Other notable additions include the ability to send [[squad]]s of dwarves off the map (on [[mission]]s to raid sites, rescue citizens, retrive artifacts, explore ruins and so on), secret [[agent]]s, non-player [[quester]]s and improved [[kobold]] sites.
* The [[villain]]s release (first part) ([[DF2014:Release_information/0.47.01|0.47.01]]): added villains to the game, giving them goals and the ability to subvert other people into various corruption activities such as embezzlement, sabotage, kidnapping or assassination. Other notable additions included improved relationships (divorce and remarriage, children outside marriage, different kinds of friendships), improved religions (featuring prophets and monastic orders), trade companies, craft guilds, new sites (monasteries, bandit forts and the return of castles) as well as several new [[night creature]]s. This release was cut short, leaving out most of the [[cv:fortress mode|fortress mode]] and [[cv:adventure mode|adventure mode]] villainy, to hasten the Premium release.
* The Premium release (or the Steam release) ([[Release_information/50.01|50.01]]): the first commercial release of ''Dwarf Fortress''. also known as ''Dwarf Fortress Premium''. As the primary commercial platform is [https://store.steampowered.com/app/975370/Dwarf_Fortress/ Steam], it is also known as the Steam release, though it is also available on [https://kitfoxgames.itch.io/dwarf-fortress itch.io]. It included a complete overhaul of UI and graphics, bug fixes, as well as an official pixel-art [[graphics set]]. A concurrent free version is still available as ''Dwarf Fortress Classic'' (Available on 12/22/22 since version 50.04 at [https://bay12games.com/dwarves/ Bay 12 Games]), which has feature parity but not the official graphics set.
* The adventure release ([[Release_information/51.01|51.01]]): Re-enables [[Adventurer mode]] with a new interface and additional graphics. Added [[:Category:Myth|mythical]] features such as [[chosen]] adventurers and [[mysterious dungeon]]s.
* The initial Lua scripting release ([[Release_information/52.01|52.01]]): Exposed previously hard-coded "procedural object generation, like the forgotten beasts, divine curses (vampires and werebeasts), divine items, necromancers and their lieutenants and experiments, evil weather, and so forth."
* The first siege release ([[Release_information/53.01|53.01]]): An improvement of [[siege]]s, with a focus on more intelligent invader tactics, balanced [[trap]]s, and updated [[siege engine]]s. [https://store.steampowered.com/news/app/975370/view/530964346754301996][https://store.steampowered.com/news/app/975370/view/528732929177683220][https://store.steampowered.com/news/app/975370/view/536616130148565319][https://store.steampowered.com/news/app/975370/view/530987265859522075]

== Old arcs ==
''Dwarf Fortress'' development has moved away from the old large arc based strategy. The old [[Consolidated Development]] page lists 21 "short-term arcs" and 15 "long-term arcs". Not all arcs would have taken take the same length of time to complete. Each arc also encompassed certain cores, requirements, bloats, and power goals.

Here are a few notable ones:
*[[Army arc]]: possibly the biggest endeavor out of all the current arcs, it was never fully completed. Version 0.31.01 introduced many army arc features.
*[[Caravan arc]]: another famous arc, focusing on fleshing out the caravans (Status unknown as of v0.47.05, may have been completed.)
*[[County arc]]
*[[Life cycle arc]]
*[[Presentation arc]]

[[Category:Arcs| ]]
[[Category:Game development]]
{{unversioned}}
[[ru:Development arc]]

Dwarf Fortress Wiki:Page request/List

2026-06-07T10:07:47Z

Ziusudra: /* Redirect requests */ added unsigned templates, and Rule N comment about Structures

{{page request header|List of page requests}}
:''This is a '''list''' of page requests. See [[DF:PR|this page]] for assistance with requesting a new page.''
== Recently created pages ==
{{Special:RecentChangesLinked/Template:Newpage|showlinkedto=1}}
----
{{page request footer}}

== Article requests ==

* Request: Stockpile Master List page that has a list of every stockpile type and every item type that exists within it. As far as I can tell, we don't have a single central place that tells you which item belongs in which stockpile. This is particularly challenging for items like scroll rollers - they're store in Finished Goods -> Tools. Nestboxes are also stored there, despite them acting like furniture. Display furniture is stored under Furniture -> Other Large Tools. I've always had a challenge parsing each wiki page to see which stockpile it belongs to, because the mention of the stockpile category is usually offhandedly mentioned in the middle of a paragrph, instead of an infobox. [[User:Zestylimez|Zestylimez]] ([[User talk:Zestylimez|talk]]) 16:35, 20 December 2025 (UTC)

* Request: v50's been out for nearly a year now and there is still no page on this wiki detailing what the new granular [[Difficulty]] settings do. Do we even ''know'' what they do? From what I can gather, '''Off''' stops outside enemies from entering the map (but still allows [[Intrigue]] and wildlife treated as dangerous to occur), '''Normal''' is as per usual, and '''Hard''' ensures a nonstop stream of [[Fun]] will relentlessly assault your fort, but other than that, I've no clue. [[User:CobaltNinja|CobaltNinja]] ([[User talk:CobaltNinja|talk]]) 19:20, 15 October 2023 (UTC)

*Request: [[Unusual volcanic wall]] - Right now there's a small section for this new (added in v50) structure/formation under the page for [[obsidian]] but I think it's notable/complex enough for its own page [[User:KM942|KM942]] ([[User talk:KM942|talk]]) 03:50, 7 January 2023 (UTC)

* Request: I would like to upload a few pictures (that I made and edited for clarity) to demonstrate a modular [[Minecart]] thumper design. [[User:2Bob|2Bob]] ([[User talk:2Bob|talk]]) 15:23, 2 January 2023 (UTC)2Bob

*Request: I would like to create [[The Long Night]] and several associated articles [[The Long Night: Civilizations]], [[The Long Night: Creatures]], [[The Long Night: Materials]], [[The Long Night: Weapons]], and [[The Long Night: Armor]] to form a more easily navigated guide to the new features found in the mod of the same name. [[Special:Contributions/98.212.135.225|98.212.135.225]] 23:51, 1 September 2020 (UTC)
** Since this is a mod, it should go under the mod namespace. I've created [[Mod:The Long Night]]; as it expands, I would suggest creating subpages like [[Mod:The Long Night/Creatures]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:25, 2 September 2020 (UTC)

* request: [[DF2014:Altar]] [[Special:Contributions/35.191.8.17|35.191.8.17]] 00:11, 17 February 2020 (UTC)
** Done. DF also refers to these as "offering place"s in the {{k|b}} menu, but I didn't see existing pages where either of these were mentioned from a quick search. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:03, 30 June 2020 (UTC)

* Request: I would like to create [[DF2014:Messenger]] specifically with the information that they are assigned on the locations screen [[User:Keupo|Keupo]] ([[User talk:Keupo|talk]]) 06:56, 27 June 2018 (UTC)
** You already have permission to do this since you've made 3 edits now. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:31, 27 June 2018 (UTC)

* Request: I would like to create [[Civilization/World_Info_menu]] [[User:Azeroth2b|Azeroth2b]] ([[User talk:Azeroth2b|talk]]) 18:33, 13 December 2017 (UTC)

* Request: I would like to create [[DF2014:Kisat Dur]] [[Special:Contributions/174.27.44.232|174.27.44.232]] 00:14, 31 July 2016 (UTC)
** Done. [http://www.bay12forums.com/smf/index.php?topic=148015.0 Forum thread] for reference. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:09, 1 August 2016 (UTC)

* Request: [[DF2014:Reaction examples]] Simply copy the old page from v0.31 for more resources. Many old pages on modding haven't been pushed through versions even when they are still accurate. [[Special:Contributions/2606:A000:FD44:7A00:B58A:AB43:BD25:B51C|2606:A000:FD44:7A00:B58A:AB43:BD25:B51C]] 22:23, 28 March 2016 (UTC)Ryga_
** Done.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:47, 1 August 2016 (UTC)

* Request: I would like to create [[DF2014:Philosopher]] and [[DF2014:Sage]] because these are new scholar jobs in 42.xx [[User:Lead Cafe|Lead Cafe]] ([[User talk:Lead Cafe|talk]]) 22:33, 28 January 2016 (UTC)
** Both are profession titles associated with scholars; I created them as redirects to [[DF2014:Scholar]].--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 04:08, 29 January 2016 (UTC)

*[[DF2014:Citizenship]] — here's one article on a new mechanic not currently covered by the wiki, we most definitely need to work on this. — [[Special:Contributions/94.19.200.59|94.19.200.59]] 20:39, 8 December 2015 (UTC)
**Done. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:17, 4 January 2016 (UTC)

*[[Masterwork:Titanite]]: I can't find any information about Masterwork's Titanite, either from the wiki or Google. After mining some, I can only cut it like gems. Also need a to-do for this: build a crucible to determine if [[Masterwork:Titanium]] can be extracted from titanite. 1 Jan 2016
**Done. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:17, 4 January 2016 (UTC)

*[[DF2014:Giant firefly]]: Just found one in my latest save of 0.42.05, realized a page didn't exist. [[User:ArcaneMusic|ArcaneMusic]] ([[User talk:ArcaneMusic|talk]]) 22:07, 19 January 2016 (UTC)
** I just added a list of all the new creatures (probably contains some errors) on the talk pages of the [[graphic set]] and [[creature]] pages. Most of those probably need to be added as new pages too. In addition the page [[Back_bear_man]] should be deleted (mistyped b-L-ack bear man). In the future, it would be nice to have a script that simply goes through the creature raws and suggests new pages to be created for missing creature entries. [[User:CLA|CLA]] ([[User talk:CLA|talk]]) 15:12, 20 January 2016 (UTC)
***The admins have bots that can create the pages automatically. Part of the hold-up is that the wiki's raws haven't been updated, so new creature pages aren't able to "autofill" with the appropriate details from the raws (and we prefer not to enter all that information manually).--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:38, 20 January 2016 (UTC)

*[[Masterwork:Drake]] The article is blank. Since these are a domestic animal that players can grab on embark, there should be some information about them for people new to the mod. [[User:Apollo Densin|Apollo Densin]] ([[User talk:Apollo Densin|talk]]) 02:00, 11 March 2019 (UTC)
** Done.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 23:50, 13 March 2019 (UTC)

*Version 0.47.1 added [[DF2014:Fort]], [[DF2014:Constructed creatures]], and perhaps [[DF2014:Intelligent undead]]. It also allows to [[DF2014:Mount]] creatures. A lot of other new features deserve their pages. Perhaps we should create a DF2020 version of pages.

== Talk page requests ==

* Requesting new talk page for https://dwarffortresswiki.org/index.php/Talk:Mass_pitting [[User:Runekri3|Runekri3]] ([[User talk:Runekri3|talk]]) 20:14, 15 November 2023 (UTC)

*Requesting new talk page for [[Main:Building_destroyer]] (https://dwarffortresswiki.org/index.php/Talk:Building_destroyer) [[User:Glumprong|Glumprong]] ([[User talk:Glumprong|talk]]) 20:46, 16 October 2023 (UTC)

Requesting new talk page for https://dwarffortresswiki.org/index.php/Dwarf_Fortress_Wiki:Centralized_Discussion/page_describing_47_v50_differences [[User:Evilishies|Evilishies]]

I would like a page describing the differences between the 2014 (v0.47) and Steam (v0.50) versions. As a new player, a page outlining these differences would be massively helpful and allow me to read existing documentation and forums more easily, as well as make updates to the v0.50 pages.

Requesting new talk page for https://dwarffortresswiki.org/index.php/Template_talk:DF2014_labors please & thank you [[User:Blitz4|Blitz4]] ([[User talk:Blitz4|talk]]) 02:23, 5 July 2022 (UTC)

I would like a talk page for [[DF2014:Bauxite]] and [[DF2014:Aluminum]]. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 04:24, 17 August 2019 (UTC)
:Done. -- [[User:Loci|Loci]] ([[User talk:Loci|talk]]) 18:58, 18 August 2019 (UTC)

Request: Talk page for [[DF2012:Repeater]] [[Special:Contributions/68.6.123.36|68.6.123.36]] 03:38, 25 March 2014 (UTC)
:Done. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:44, 25 March 2014 (UTC)

Masterwork_Talk:Guildhall [[Special:Contributions/68.46.84.117|68.46.84.117]] 14:02, 20 October 2013 (UTC)
:Done. --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 15:01, 20 October 2013 (UTC)

Hello, would you be able to create a Talk page with the following question for me?:

"Do children born during fortress mode (or worldgen if you can find out) adopt the dieties of their friends/parents, or are they assigned a random diety? Is this with immediate effect from birth?

Thanks.

Josh"

Thank you! :)

Hello, I'd like to open another talk/discussion page for "Size" (http://dwarffortresswiki.org/index.php/DF2012:Size) with the following question:

Are there any combat benefits to SMALL dwarves?

On one of the pages for an older version of DF it notes that large creatures like elephants have a hard time landing a hit on small creatures like cavies. Would this alleged bonus to-dodge and/or penalty to-hit modifier translate in any meaningul way for smaller dwarves?
:[[DF2012 talk:Size|Done]]. --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:05, 1 January 2014 (UTC)

I'd like to open a talk page for [[DF2012_Talk:Relationships]] with the following note (two paragraphs):

The royalty section is inaccurate. I have a second-generation native-born dwarf in one of my fortresses who has a plentitude of aunts and uncles and listed maternal and paternal grandparents. I'm not sure why having those relationships is only noticed for royalty, but I think it's partially because shorter worlds mean smaller lineages and partially because most forts don't last long enough to see native-born children grow up, get married, and have children of their own. I really don't think there's any reason why extended family would be limited to royalty in any case.

Anyway, I added parents to the Types section, and also grandparents because I hadn't noticed the Royalty section. I'd add Aunts/Uncles but I'm not sure where they fall in on the list, and baby Sarvesh doesn't have any cousins yet.

Thank you! --[[User:Lielac|Lielac]] ([[User talk:Lielac|talk]]) 02:41, 24 January 2014 (UTC)
:Done. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:37, 24 January 2014 (UTC)

Hello, I feel that [[DF2012:World_generation]] should cover what goes into history simulation, as it is obviously different to simulation in fortress mode.
However, this is not a matter I am educated on. I would put this request on the page, but I cannot yet create a talk page.
:Done. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:05, 22 April 2014 (UTC)

* https://dwarffortresswiki.org/index.php/Template_talk:DF2014_labors
[[User:Blitz4|Blitz4]] ([[User talk:Blitz4|talk]]) 02:23, 5 July 2022 (UTC)

Edits made by 76.116.204.8 were made by me while I was away from school/university on summer/winter vacation at my dad's. I wanted to make a note on [[User talk:76.116.204.8]] claiming attribution for the edits. Additionally, I would like to request the creation of [[Talk:Gem]] so that we can discuss a current bug where the new "cut gem" job never creates a large gem or gem craft (as of 0.50.03). – [[template:unsigned|unsigned]] comment by [[User:ArmokGoB|ArmokGoB]]

:You appear to have the ability to create pages now. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:31, 23 December 2022 (UTC)

== User page requests ==

*{{upr|[[User:Qazwsxplm|Qazwsxplm]] ([[User talk:Qazwsxplm|talk]])}}
{{upr|[[User:ProbablyPuck|ProbablyPuck]] ([[User talk:ProbablyPuck|talk]])}}
{{upr|[[User:Allcrops|Allcrops]] ([[User talk:Allcrops|talk]])}}
{{upr|[[User:Blitz4|Blitz4]] ([[User talk:Blitz4|talk]])}}
{{upr|[[User:uberflut|uberflut]] ([[User talk:uberflut|talk]])}}
{{upr|[[User:DeathByBlue|DeathByBlue]] ([[User talk:DeathByBlue|talk]]) 02:31, 28 March 2020 (UTC)}}
{{upr|[[User:Lead Cafe|Lead Cafe]] ([[User talk:Lead Cafe|talk]])}}
{{upr|[[User:BillyJack|BillyJack]] ([[User talk:BillyJack|talk]])}}
{{upr|[[User:BillyJack|Sandbox]] ([[User talk:BillyJack|talk]])}}
{{upr|[[User:Theit8514|Theit8514]] ([[User talk:Theit8514|talk]])}}
:Created. --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:37, 30 June 2013 (UTC)
{{upr|[[User:Mixtrak|Mixtrak]] ([[User talk:Mixtrak|talk]])}}
{{upr|[[User:Green Sprite|Green Sprite]] ([[User talk:Green Sprite|talk]])}}
{{upr|[[User:Mikerenfro|Mikerenfro]] ([[User talk:Mikerenfro|talk]])}}
{{upr|[[User:BananaUnlimited|BananaUnlimited]] ([[User talk:BananaUnlimited|talk]])}}

== Redirect requests ==

*Redirect [[Drinks]] to [[Drink]]. [[Special:Contributions/82.169.134.128|82.169.134.128]] 14:19, 10 January 2025 (UTC)
** Declining per [[DF:Rule N]]. Links to [[drink]]s can be created with <nowiki>[[drink]]s</nowiki>. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:29, 12 January 2025 (UTC)
*[[Hot tub]] should redirect to [[Magma Sea]]—not very common slang, but I've heard it consistently. [[Special:Contributions/68.56.148.200|68.56.148.200]] 06:57, 1 January 2022 (UTC)
**Do you have an example? I've never heard this. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:14, 1 January 2022 (UTC)
*[[DF2014:Fun]] to [[DF2014:Losing]]
[[dfhack]], [[DFHack]] and [[DF2012:DFHack]] to [[Utility:DFHack]]. --[[User:Lurker|Lurker]] ([[User talk:Lurker|talk]]) 14:07, 7 August 2013 (UTC)
:Done. --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:48, 7 August 2013 (UTC)
* Page "Taming" should redirect to "DF2012:Tame" [[User:Latias1290|Latias1290]] ([[User talk:Latias1290|talk]]) 18:02, 27 August 2013 (UTC)
**[[DF2012:Tame]] is a redirect to [[DF2012:Animal trainer]]. Created [[Taming]] and [[DF2012:Taming]] as redirects. --[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:33, 27 August 2013 (UTC)
* Page "Gcs" should redirect to [[DF2014:Giant_cave_spider]]. [[Special:Contributions/199.60.104.18|199.60.104.18]] 19:00, 1 September 2015 (UTC)
:Done. Just do it yourself next time. Just create the page and add "#REDIRECT" followed by a space and the link to the page.[[User:CLA|CLA]] ([[User talk:CLA|talk]]) 22:19, 1 September 2015 (UTC)
::The reason this page exists is because anonymous users can't create pages. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 12:09, 4 September 2015 (UTC)
:::Oh, that makes sense. Should have figured that out on my own.
* [[DF2014:Combat log]] could redirect to [[DF2014:Reports]], I think it's the phrase new players will search for. [[User:Okdewit|Okdewit]] ([[User talk:Okdewit|talk]]) 18:58, 30 January 2016 (UTC)
**Done. [[User:Jwoodward48|Jwoodward48]] ([[User talk:Jwoodward48|talk]]) 00:05, 2 March 2016 (UTC)
* create redirect page "World Activation" and redirect to World_activities [[User:Untrustedlife|Untrustedlife]] ([[User talk:Untrustedlife|talk]]) 00:13, 26 July 2016 (UTC)
-- Got it done [[User:Untrustedlife|Untrustedlife]] ([[User talk:Untrustedlife|talk]]) 00:16, 26 July 2016 (UTC)
* Page [[DF2014:Guineahen]] and [[DF2014:Keet]] could redirect to [[DF2014:Guineafowl]] the same way [[DF2014:Guineacock]] does currently. [[Special:Contributions/2A01:C50E:D66A:5500:0:0:0:10|2A01:C50E:D66A:5500:0:0:0:10]] 17:43, 29 November 2017 (UTC)
* Create redirect page for "Retire", "Unretiring", and "Retiring" and redirect to "Reclaim Fortress Mode" [[User:Benderdragon|Benderdragon]] ([[User talk:Benderdragon|talk]]) 16:21, 29 June 2020 (UTC)
** Created [[Retire]]; [[Unretire]] already existed, and I'm hesitant to create redirects for the gerund forms - we don't have guidelines that specifically discourage them, but {{Rule|N}} and {{Rule|E}} are similar, and partial searches for "retir" or "unretir" should bring up the relevant pages in the search box anyway. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:12, 30 June 2020 (UTC)
*redirect "ringleader" and potentially several other possible titles for crime bosses to [[DF2014:Boss]][[User:Rugnir|Rugnir]] ([[User talk:Rugnir|talk]]) 21:47, 13 August 2021 (UTC)
*redirect "Non-dwarf's guide to stone" to the page "Non-dwarf's guide to rock" (Confusing Titles) – [[template:unsigned|unsigned]] comment by [[User:121.74.254.159|121.74.254.159]] 22:41, 15 June 2025
* redirect "Structures" to "Site" – [[template:unsigned|unsigned]] comment by [[User:Drakansoul|Drakansoul]] 23:44, 6 June 2026
** Rule N: singular names and there is already [[Structure]], so that would be more confusing. [[User:Ziusudra|Ziusudra]] ([[User talk:Ziusudra|talk]]) 10:07, 7 June 2026 (UTC)

== Other requests ==


* I made some nice v50.xx graphics for the FPS efficient 1x3 pump stack design, and couldn't upload them when I tried to add a new block to the page. For the moment I've uploaded them here: [https://files.jelloraptor.com/s/oiM2z3Wq94ijjwt even-z-levels], [https://files.jelloraptor.com/s/XMLzyFTq4Ca9La9 odd-z-levels], [https://files.jelloraptor.com/s/gQyk8peJZrgzRQy gimp-source]. Could someone please upload them as appropriate and add them to the pump stack page? Thanks. Also I certify that these are all my creation and that DF-wiki can use them as it wishes. {{unsigned|Jello Raptor}}
** Uploaded [[:File:Gimp-z-levels-even.gif|even]] and [[:File:Gimp-z-levels-odd.gif|odd]]. Feel free to add them where you see fit. [[User:OddballJoe|OddballJoe]] ([[User talk:OddballJoe|talk]]) 01:54, 28 January 2023 (UTC)

* Could there please be a smaller version of the "D for Dwarf" template, maybe one that leaves the text ''joke'' near a sentence, so that we don't have a big-ass banner for little one-off jokes in articles and reserve the "D for Dwarf" template for entire sections or articles? [[Special:Contributions/68.56.148.200|68.56.148.200]] 23:15, 6 December 2021 (UTC)

* Can someone include a discussion about how dwarfs choose which jobs/tasks to do if they have enabled multiple labors and there are jobs in multiple labors on the DF2012:Labor page? Is it based on which job is created first? Their skills / traits / attributes? Which labor they are highest ranked or their titled profession? This seems to be an issue in the LPs I've been watching early on when there are only the 7 starting dwarves, sometimes extending into the first migration. I know a solution is to deactivate other labors, or use burrows, but I'm still curious how it works. Thank you, [[Special:Contributions/108.243.77.185|108.243.77.185]] 03:08, 17 August 2013 (UTC)

* Hello. I wanted to know how to make the tiles uniform for the ground. I'm sure to have read somewhere once that it was possible to change the tiles to be all "." (I am currently searching for a Goblin Snatcher for a while now ^^). I searched for "ground" what has yielded me a link to above ground page. There was no link there. Could make one to the relevant article or indicate the settings to do please? [[Special:Contributions/31.164.176.33|31.164.176.33]] 20:04, 23 September 2013 (UTC)
** Done: [[Ground]]. --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:57, 23 September 2013 (UTC)

* Hi, im new and just want to start translation of the wiki into german. im really into this game and i guess i still could learn a shitload of new stuff by doing this. AND there would maybe be more players around if and when i/we translate. not every german is fluent in english. -f4nt4sy [[User:F4nt4sy|F4nt4sy]] ([[User talk:F4nt4sy|talk]]) 15:01, 1 March 2014 (UTC)
:See [[DF:Centralized Discussion/Translating the wiki|here]]. It's been suggested before, but it's been hard to set something up on this wiki. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:22, 2 March 2014 (UTC)

* I'd like to create a page under the centralized discussion for a proposal of subnamespaces for stuff like creatures, skills, etc. under a specific version. Stuff like DF2014:Rat becoming DF2014:Creatures:Rat. I'm not sure if the software allows this, but I thought I'd say it anyway.

* I'd like to add an image of the 'animated bedroom design' section I added to bedroom design. I uploaded a short screen cast here [https://imgur.com/XIGR8Ce], but to get it to below the 2 MB limit I also converted it to a GIF here [https://imgur.com/x86h2u4]. I feel like just adding an imgur link has to be frowned upon so I didn't want to just link to it in the article. [[User:Austin|Austin]] ([[User talk:Austin|talk]]) 05:43, 3 January 2023 (UTC)

*I'd like to add 2 pictures to the water reactor page (lower level and main level), showing how to build this in the Steam DF version. Since its the first edits, I can't get it to upload without request. [[User:Thurlin05|Thurlin05]] ([[User talk:Thurlin05|talk]]) 18:26, 13 January 2023 (UTC) Thurlin05

Tent

2026-06-06T02:19:35Z

Ziusudra: as redirect to Camp

#REDIRECT [[Camp]]

Quest

2026-06-05T20:59:15Z

Ziusudra: /* Rescue */ fixed typo

{{Quality|Superior}}
{{av}}

[[File:quest_preview.jpg|thumb|350px|right|"We gotta find someone's wooden crown in ''THAT?!'' ''Art by Jonás López Moreno'']]'''Quests''' can be completed by [[adventure mode|adventurers]] (and NPCs, who will actively seek out quest targets during both [[world generation]] and in play) to raise their [[reputation]]. Adventurers can start out in (or join) certain groups to be tasked with quests by the group's commander. Objectives can range from slaying monsters, to retrieving lost [[artifact]]s or [[Quest#Rescue|children]]. [[Rumor]]s help spread and circulate information relevant to quests.

== Quest log ==
{{old|v=0.44.01}}

The '''quest log''' menu displays everything known by the adventurer about the world, and is important for quests. Adventurers always start out with information about their local area, unless they began as outsiders - as they explore and discover new things, the log will actively fill up with new information.

Press {{k|Q}} to open the menu. The log can also be opened from the [[fast travel|fast {{k|T}}ravel]] screen. Pressing the green keys at the top of the screen navigates between nine tabs:

* {{k|e}} '''Events''': Events that are happening or have happened in the past.
* {{k|a}} '''Agreements''': The adventurer's existing and previous agreements with leaders and companions.
* {{k|p}} '''People''': People, other historical figures, and their relationships to the adventurer.
* {{k|s}} '''Sites''': Various sites around the world. Only sites that are shown on the map are listed.
* {{k|g}} '''Groups''': Entities and their relationships to the adventurer. This includes civilizations, site governments, bandit gangs, etc.
* {{k|r}} '''Regions''': Regions of the world. 'Additional information' will list the biomes the region possesses.
* {{k|b}} '''Bestiary''': [[Creature]]s encountered by the adventurer, along with their descriptions, where to find them, and how many were slain.
* {{k|A}} '''Artifacts''': Various known artifacts, their descriptions, and their last known whereabouts. Artifacts are only logged after their (rumored) whereabouts become known.
* {{k|i}} '''Intrigue''': Criminal networks. Pressing {{k|Tab}} cycles through '''Actors''', '''Organizations''', and '''Plots'''.

On the right side of the screen is a list of names, which can be searched using the {{K|f}}ilter. On the left is either a navigable world map, or information of the highlighted name. The {{k|m}} key will alternate between the map and info.

On the map screen, navigate using the arrow keys or numpad. To pinpoint a known site, select the site's name and press {{k|z}} to center the cursor {{Tile|O|3:1}} to the site on the map. A green line will be drawn between the player's location {{Tile|@|7:0}} and the site. The line can be disabled with {{k|l}}. Press {{k|c}} to recenter the cursor back to the player's current location. Centering to a site in the same world tile with the player's location will cause the map to zoom into local view and display the player's position and the site tiles. Events, groups, regions, and creatures in the bestiary can also be centered on the map if their whereabouts are known.

The world map can contain unexplored areas that become visible once they are discovered. The initial uncovered range is dependent on the territorial extent of the character's starting civilization. Starting out as an outsider (no civ) will mean that the entire map, except for the starting area, will be hidden.

=== Key bindings ===

{| class="wikitable"
! Key !! Description
|-
| {{k|Q}} || Open quest log
|-
| {{k|Esc}} || Exit quest log
|-
| {{k|e}} || View events
|-
| {{k|a}} || View agreements
|-
| {{k|p}} || View people
|-
| {{k|s}} || View sites
|-
| {{k|g}} || View groups
|-
| {{k|r}} || View regions
|-
| {{k|b}} || View bestiary
|-
| {{k|A}} || View artifacts
|-
| {{k|i}} || View intrigue
|-
| {{k|m}} || Toggle map/info
|-
| {{k|z}} || Recenter on selected
|-
| {{k|c}} || Recenter on current location
|-
| {{k|l}} || Toggle line
|-
| {{k|f}} || Filter the list
|-
| {{k|+|-|*|/}} || Select from list
|-
| {{k|8|2|4|6|7|9|1|3|↑|↓|←|→}} || Navigate the map
|}

== Commander ==

Commanders, or quest givers, are [[position]] holders that can assign orders to their subordinates (a [[squad]]). There are four positions known to give out quests: the [[captain of the guard]], a lord/lady, and the leaders of [[bandit]] and [[outcast]] groups. With the exception of the captain of the guard, commanders flash on screen. Elven civilizations do not have quest givers. Adventurers automatically start off as subordinates, if the player selected the "hearthperson" occupation in the character creation screen.

Adventurers can join existing squads by speaking to a commander and selecting {{DFtext|Ask to become a <squad>}}. Adventurers must have a reputable status as a killer, hero, or hunter before commanders will accept them.{{verify}} Adventurers cannot join more than one squad; joining another will cause them to leave the old squad.

Attacking the commander will cause the standard hostile reaction, but it does not cancel the current agreement. If the commander dies in any way before the completion report can be given, the report can be given to the next person that takes up the position, which automatically happens after a while.

By claiming leadership over a site, characters can become a lord or lady and create their own squad of hearthpeople, but they cannot give out quest orders.

In order for a position to send out quests in adventure mode, it requires the tokens {{token|RESPONSIBILITY|po|LAW_ENFORCEMENT}} and a {{token|SQUAD|po}}. If the entity is using {{token|SITE_VARIABLE_POSITIONS|e}}, it needs to include the {{tt|LAW_ENFORCEMENT}} responsibility to generate hearthpersons.

{| class="wikitable"
|+ List of commanders
! Civilization
! Squad member
! Commander
! Location
|-
| [[Dwarf|Dwarven]]
| [[Fortress guard]]
| [[Captain of the guard]]
| [[Fortress]]
|-
| rowspan="1" | [[Goblin]]
| rowspan="3" | Hearthperson
| rowspan="2" | Lord/Lady
| [[Dark fortress]], [[Dark pits]]
|-
| rowspan="2" | [[Human]]
| [[Mead hall]]
|-
| Baron/Baroness
| [[Keep]]
|-
| Varies1
| rowspan="2" | Lieutenant
| [[Bandit|Bandit leader]]3
| [[Camp]], conquered site/structure
|-
| Human2
| [[Outcast|Outcast leader]]3
| [[Catacombs]], [[Dungeon]], [[Sewers]]
|}

:1 Civilizations with {{token|BANDITRY|e}}. By default, this includes humans, goblins, and kobolds.
:2 Only human collections of outcasts have leaders.
:3 Bandit and outcast leaders have unique titles (''chief'', ''ringleader'', ''warlord'', etc.).

== Process ==

=== Receiving a quest ===

To receive a quest, talk to the commander and select {{DFtext|Request duty or advice pertaining to service as a <squad>}}. The commander will assign an order, including additional information about the target. The details and status of the quest can be checked in the agreements log; quests are identifiable with {{DFtext|Order:}}.

Players are not given the choice to choose a specific quest, nor can they request more than one quest at a time. The order cannot be cancelled and players are required to complete it before they are able to receive another quest. The status will turn from {{DFtext|Not yet completed}} to {{DFtext|Complete: report back|2:1}} once the objective is completed successfully.

Leaving the squad will remove any current orders from the agreements log, but it won't actually cancel the quest. The quest order reappears in the log after returning back to the squad, and players can still complete it per usual.

=== Completing a quest ===

Once the quest is complete, report back to the commander and select: {{DFtext|Give report pertaining to service as a <squad>}}. The quest will finish and its record will disappear from the agreements log. You can ask for a new quest afterwards.

Commanders can run out of quests, such that when asked for more, they say: {{DFtext|You may enjoy these times of peace, but remain vigilant.|7:1}}

=== Rewards ===

Any action committed in a quest will affect the character's [[reputation]]. Upon completion of a quest, the commander will automatically share the adventurer's incidents. To speed this process, adventurers can also spread rumors about themselves on their own. The easiest way to spread news is to talk to someone and choose:

{{DFtext|Bring up specific incident or rumor}}

Pick an incident to tell to the person. Rumors can be {{k|f}}iltered with specific keywords to help faster searches. For example, typing "{{tt|conflict}}" or "{{tt|fight}}" in the filter will only show combat events. By spreading rumors, news of acts will eventually spread throughout the land, and the character's reputation will slowly build up.

People with different personalities, values, and affiliations have varying responses towards certain actions. Reputation is based on an individual's or entity's personal view of your character.

Adventurers performing good and heroic deeds will eventually earn the title of a legendary hero. They will earn respect from others, and taverns will provide free or discounted services and accommodations as thanks. The more amazing the action is, the bigger the impact it will make to the reputation. Keep in mind that accumulated reputation, specifically heroism, can be ruined if the adventurer acts badly. For instance, if word manages to leak out about the character murdering an innocent peasant, the character will become an enemy of the people regardless of previous good deeds.

== Doing quests without a commander ==

=== Temple Quest ===
You can take on a quest for a religious sect by speaking to one of its religious leaders (as in, a [[Priest]] or higher) (usually found at a [[temple]]; ''though it seems to work even if they aren't at a temple.'') and selecting {{DFtext|Offer Service}} from the [[Talking|conversation]] menu.
The quest plays out much like a commander’s quest—except instead of military orders, the priest will send you on a divine errand to recover an [[artifact]], usually a [[Primordial remnant|Primordial Remnant]].

=== Self-guided quest ===
:''See also: [[Rumor]]''

Players can earn heroic reputation without a commander—perhaps the adventurer needs a worthy kill first, before becoming a hearthperson. Adventurers may already start off knowing a few potential opportunities, seen in the events log.

To learn about a potential target, talk to someone and select: {{DFtext|Inquire about any troubles}}. The person will reply with a list of known troubles: choose a type of trouble from that list, and they'll respond with a specific incident of that type. For incidents involving objects or groups, the basic reply structure appears as:

* Trouble pertaining to a creature: {{DFtext|(...) <Site name> is in <region name>. Seek this place if you wish to confront <creature>. (...)|7:1}}
* Trouble pertaining to a group: {{DFtext|(...) They have a <site> called <site name> somewhere in <region name>.|7:1}}
* Trouble pertaining to an artifact{{v|0.44.01}}
** if the speaker wants it: {{DFtext|I desire that <artifact> be returned(...) Last I heard, <location of its whereabouts>.|7:1}}
** if the speaker is part of a group that wants it: {{DFtext|Speaking as a representative of <entity>, it is important that <artifact> be returned(...) It should be brought to <structure name> in <site name>. Last I heard, <location of its whereabouts>.|7:1}}
** if another person wants it: {{DFtext|<Creature> wants <artifact> returned. Last I heard, <location of its whereabouts>.|7:1}}
** if a group wants it: {{DFtext|<Creature> of <entity> wants <artifact> returned. Last I heard, <location of its whereabouts>.|7:1}}

You are then given the option to ask further questions about the information of the location and whereabouts. Once satisfied with the info, set forth on the objective.

== Finding quest locations and objects ==

Completing a quest requires searching for the location of the quest object, which can be difficult at first. If the location was already acquired from someone, open the {{k|Q}}uest log and select the event or entity from the relevant list to find out where it is on the map. If the location is known, the "Recenter on current location" option will be available. Press {{k|z}} to recenter the cursor to the location of the quest object on the map. If the location is unknown, players can {{DFtext|Ask for directions}} to a person.

=== Whereabouts of a site ===

To find the location of a site on the map:

# In the 'Ask for directions' menu, select {{DFtext|Ask for the whereabouts of <site name>}}.
# If they know the location, they will reply:

{{DFtext|<Site name> is a <length of the travel> to the <direction>. [You received a detailed description.]|7:1}}

The site will be listed in the quest log and become searchable on the world map. If they do not know the location, they will either state their lack of knowledge or advise to look for a more well-informed person nearby to ask - fellow travelers, as well as position/occupation holders (e.g. leaders, nobles, tavern keepers) are usually more knowledgeable about the goings-on of the world. People can also be asked to guide adventurers to a location, becoming temporary companions until arriving at the destination.

=== Whereabouts of a creature ===

To find the site where a creature is located:

# In the 'Ask for directions' menu, select {{DFtext|Ask for the whereabouts of <creature>}}.
# If they know the whereabouts, they will reply {{DFtext|<Site name> is in <region name>.|7:1}}

Once at the site, to find the exact location of the creature (such as a hiding vampire), ask for whereabouts again to one of the locals. If the creature lives in a [[structure]], they will say {{DFtext|We are in <site name>. Search first in <structure> to the <direction>.|7:1}} Once at the correct structure, asking once more will give the response {{DFtext|Must be right around here somewhere.|7:1}} In the current version, this is broken.{{bug}} {{verify}} When the precise location is unknown, they will instead say {{DFtext|I'm not sure exactly where to look.|7:1}}

It can also be determined whether a creature is on the move or already dead by asking for its whereabouts. "On the move" means that the creature is not present in any site or structure and is currently wandering outside (or underground), possibly travelling between sites. By chance, targeted creatures can be encountered while travelling (they appear as {{Tile|*|7:0}} in the fast travel map). If the targeted creature is discovered to be already dead and the quest required killing the creature, then simply return to the commander; as its death counts as completion of the order. It is useful to remember that some creatures follow a day-night active cycle. For example, [[night troll]]s are nocturnal, so they usually remain in their lairs during the day and wander outside when night falls.

=== Whereabouts of an artifact ===

{{stub}}

== Types of quests ==

There are three types of quests that can be offered from the commander. Each quest and the type of target can affect different reputations. Commanders always present quests in this sequence: on-site drive off quests, all kill quests, off-site drive off quests, then trouble quests.

=== Kill ===

A kill quest requires the character to search for and slay a particular beast. Quest targets include [[megabeast]]s, [[semi-megabeast]]s, [[titan]]s, and [[forgotten beast]]s. Less powerful creatures include [[night troll]]s and [[vampire]]s. Wild animals with {{token|LARGE_PREDATOR|c}} have a chance to start attacking civilizations and become kill quest targets as well. Kill quests raise the hero reputation, and the hunter reputation is also raised for slaying large predators. The difficulty of the quest critter affects the amount of reputation (e.g. defeating a dragon vs. a dingo).

[[Werebeast]]s are not one of the beasts that can be targeted, though there are [[string dump|strings]] that imply dialogue for werebeast quests.{{verify}}

=== Drive off ===

A drive off quest requires the character to rout an enemy/criminal group from a site. Targeted groups include [[outcast]]s, [[bandit]]s, [[kobold]]s, [[necromancer]]s, and [[war]]ring civilizations. Drive off quests can raise the "hero" and "protector of the weak" reputation.

The quest implies chasing or leading the targeted members out of their location, but that is not necessary to complete the quest. It is also not required to attack or kill anyone to complete the quest, merely encountering the enemy (i.e., the enemy spots the player) then immediately returning back is usually sufficient to qualify as completion. No reputation will be acquired through this way, however, since the main source of reputation from this quest is from slaying the enemies.

Driving off necromancer groups or site governments from warring civilizations is impossible to complete.{{bug|9995}} [[Insurrection]]s do not seem to be the solution.{{verify}}

=== Trouble ===

A trouble quest appears when the character's civilization is in "brewing trouble" with another civilization due to a dispute— which generally means [[war]] is near. The quest requires the character go to an opposing civ's site and "cause trouble" for the local residents. Quest givers will give directions to the nearest site controlled by the opposing civilization.

It is currently unknown what actions are required to complete this quest. Attacking, killing, murdering, robbing, harassing, and arguing with the inhabitants does not seem to work, nor does causing insurrections seem to be the solution. It is possible that trouble quests may be bugged.{{verify}}

=== Non-commander quests ===

These objectives are never ordered by commanders, but are included among the various troubles. Unique reputations can be attained by fulfilling these objectives - adventurers must seek for these quests on their own.

==== Artifact ====

An artifact quest involves the retrieval of an [[artifact]] for another person or group.{{v|0.44.01}} Artifact quests raise the "treasure hunter" reputation. There is also a sub-type artifact quest that involves returning [[book]]s to a [[library]]; this sub-type quest raises the "protector of knowledge" reputation.

Artifacts can be properly given back to the owners by using the barter system, accessible by speaking to the owner and selecting {{DFtext|Exchange, give, take, or show personal items}}. They can also be dropped or placed in the structure, but no reputation will be gained from this method.

Library quests work a little differently - when a book is shown to one of the scholars working for the library in the barter screen, they will request for the book to be donated to the library. Do ''not'' give a book to a scholar; it will register as being in the scholar's personal possession and not the library itself - drop or place a book inside the structure instead, and the book will automatically become part of that library. Donating original books provides more reputation than copies.{{verify}}

Amusingly, players can take an artifact from a structure, leave and wait for a while, then come back to return the artifact and be praised for "finding" it for the owner, even having their adventurers gaining reputation from this method.

One can spread rumors about the specific deed by selecting the appropriate event in the incident/rumor menu. Filter keywords are ''artifact'' and the artifact's name/title.

* For regular artifact quests: {{DFtext|Bring up your giving of <artifact> to <creature> (in <structure>) in <site>}}
* For book quests: {{DFtext|Bring up your placement of <book> in <library> in <site>}}

==== Rescue ====

A rescue quest involves the retrieval of abducted [[children]] who were taken away by goblin [[snatcher]]s and imprisoned at [[dark fortress]]es. Prisoners can be found under the central dark tower in prison cells. After greeting a prisoner, there is the option to save the prisoner. Saving lets them join the adventurer's party (the agreement is identified as "Rescue" in the agreements log). Rescue quests raise the "hero" reputation to legendary for the reunited prisoner and family only. The act of rescue is not recorded in the incident/rumor list, so this reputation cannot be shared to others.

Freed prisoners can be returned to their families, or get adopted by someone. To learn about the location of living family members, talk to the former prisoner and select {{DFtext|Bring up the journey together}}. Former prisoners automatically conclude the rescue agreement when they see and reunite with their family members; or, to get someone to adopt a former prisoner, talk to the person and select {{DFtext|Ask favor, place request, make demand or issue order}}, then select {{DFtext|Ask listener to adopt <former prisoner>}}. People with high family [[value]]s (e.g. most dwarves) are more willing to adopt. More than one person can be taken in by a single adopter.

Warriors can be recruited to aid in the rescue of a prisoner; mention the abduction to a warrior (from the incident/rumor menu) to bring up the option: {{DFtext|Ask listener to join you in a rescue}}. The agreement will end once the prisoner finds a home.

People can (unfortunately) suddenly become hostile to a prisoner after the prisoner has been reunited with their family – this includes the family members of the prisoner, themselves.{{bug|9935}} usually resulting in a [[loyalty cascade]], and a rather tragic and short-lived reunion.

== See also ==

* [[Mission]]

{{Translation
| dwarven = iseth
| elvish = elabe
| goblin = osmod
| human = akul
}}

{{Category|Adventurer mode}}
[[ru:Quest]]

Giant cave spider

2026-06-02T21:51:58Z

Ziusudra: /* Farming silk */ added reference guess

{{Quality|Exceptional}}
{{Creaturelookup/0
|image=giant_cave_spider_sprites.png
|portrait=giant_cave_spider_portrait.png
|wiki=no
|contrib=no
|meat=19
|fat=18
|heart=1
|intestine=1
|brain=1
|skin=chitin
}}
{{av}}
{{creaturedesc}}
'''Giant cave spiders''' (also known as GCS) are large and extremely dangerous [[creature]]s who inhabit the deeper layers of [[cavern]]s. They are far different from your regular [[cave spider]]s; those are just treats for your [[cat]]. Giant cave spiders are as big as [[grizzly bear]]s and will make treats ''of'' cats, [[dwarves]], and the occasional careless adventurer.

You can find giant cave spiders in, obviously, [[cave]]s, caverns and most underground areas. They are '''the''' most dangerous creature in the caverns, excluding some [[forgotten beast]]s, as they [[No Pain|feel no pain]], [[No Stun|cannot be stunned]], can [[syndrome|envenomate]] creatures and have the ability to shoot [[web]]bing to ensnare their prey, with a range of 5 squares. If you see a giant cave spider in [[adventurer mode]], an announcement, "You've spotted a Giant Cave Spider!", will appear.

Giant cave spiders are not a rarity, with dozens present in the underground caverns, deep below the surface. They can be extremely hard to kill. They do not pose a big threat to a fortress when undisturbed, but when a dwarf ''does'' disturb one, [[Armok]] bless the soul of the unlucky dwarf. On occasion, however, a lucky dwarf might pound one to death within a few attacks by punching its skull into its brain, which can be a godsend after an unfortunate cavern breaching exercise.

Webs are quite useful when they aren't being used in an attack against you. Giant cave spider [[silk]] is worth twice as much as plant-derived textile and, given the [[silk farming|proper setup]] and victims, can be produced in endless amounts. Giant cave spiders are [[building destroyer]]s and will topple [[wood]]en [[furniture]] on sight.

Giant cave spiders give live birth and do not lay eggs, contrary to what one may expect. They also can't be gelded.

Some dwarves [[Preferences|like]] giant cave spiders for their ''mystery''.

==Fighting==
Giant cave spiders fight by throwing impressively large amounts of web at their enemies and biting them. Once an enemy is webbed, they are left immobilized for several moments, leaving them completely open to attack. Because the AI prioritizes attacks to the head if there is a good chance to hit, the spider will proceed to bite the victim on the head, which is generally fatal to dwarves or other similarly-sized creatures.

Giant cave spider venom appears to be a neurotoxin which causes progressive [[syndrome|paralysis]] and is usually fatal due to suffocation as the victim's diaphragm succumbs and ceases to function. The venom's effects set in relatively quickly, with complete paralysis after 720 seconds (10 [[time|time units]]). Larger dwarves will sometimes recover from this and resume breathing, assuming they are only bitten once. If not, death usually occurs after 1300 seconds (19 time units). In terms of Fortress mode, and depending on the speed of the victim, the venom will paralyze an infected dwarf within two steps and cause death by suffocation soon after.

Giant cave spider venom is only deadly on relatively small (read: dwarf-sized) creatures. It only tends to induce mild paralysis of members of large creatures such as giants, meaning a giant cave spider cannot typically kill large creatures. However, it will incapacitate and exhaust them very well.

==Killing a GCS==
The web attack of a giant cave spider not only covers a wide area but also has a very short cooldown period, and as such, the creature is easily able to spam it and is able to take out entire [[squad]]s with little trouble, making melee combat extremely risky. Ranged combat with [[crossbow]]s is much safer in comparison, as marksdwarves can out-range a cave spider's web, though this does not make it flawless; marksdwarves have the tendency to charge at their foes (and as such, right into the webs) while the giant cave spider can quickly charge at them itself, plus their large size means they can usually shrug off multiple bolts before going down. The safest method to attack a giant cave spider is either to ambush it in a chokepoint (where your dwarves may get to hit it before it can web all of them), by firing bolts through [[fortification]]s or by shooting it while it is distracted fighting something else (such as your unlucky melee squad). Pray your squads do not waste time attacking the spider's limbs and go straight for the head, before the spider does the same to them.

Due to giant cave spiders only attacking the head of a webbed dwarf, a few dwarves armored with [[steel]] helmets should be a match for a lone GCS. The coding for all creatures sets headshots as the number one priority if possible, and the web ensures that a headshot is indeed always possible. You may want to avoid using untrained dwarves for this, though, because the spider will still counterattack if the dwarf misses, potentially landing a blow on an unprotected area of the dwarf. One way to minimize this problem is to make the dwarf wear full armour (the GCS will still latch on with its bite, however, helm or no, and can still kill a dwarf by shaking them by the head).

Fortunately (or unfortunately...), giant cave spiders tend to take time to kill their prey, giving you time to kill the GCS and save the dwarf, if you are so inclined of course. However, you may not be able to save the dwarf from the GCS's venom.

Another strategy is to use large [[Animal trainer|trained]] animals to kill the GCS; two [[giant black bear]]s, [[giant grizzly bear]]s, or [[giant polar bear]]s will usually kill a GCS. The giant grizzly bears have the advantage that they can be trained for war, potentially increasing their aggression. Other animals that can kill a GCS very effectively include:
*[[Giant alligator]]s
*[[Giant lion]]s
*[[Giant tiger]]s

Clever use of [[trap]]s can also make short work of a giant cave spider before it reaches your fortress. Stone and weapon traps can severely injure, if not kill, the spider before it reaches your front lines, hopefully slowing it down and increasing the chances of your squads killing it before it can kill them.

==Capturing==
Due to the considerable value of giant cave spider silk, many players attempt to capture a live spider and set up a [[silk farm]] to boost their fortress's economy. While simply opening a path to the caverns and lining it with [[cage]] [[trap]]s may eventually work, a much more effective method is to take advantage of one peculiar behavior of building destroyers: simply build a '''[[wood]]en''' [[door]] within the caverns and surround it with cage traps (to a distance of at least 2 tiles), and any giant cave spider (or [[giant cave toad]], [[giant olm]], [[cave crocodile]], etc.) that wanders relatively close enough to the door will immediately charge toward it and be captured. Or, if you have enough [[mechanism]]s, cages and dwarfpower to spare, cage trap all the cavern exits, on map edges and fortress entrance points – a good precaution in any case in order to keep things from wandering out and causing trouble.
[[File:giant_cave_spider.png|thumb|230px|right|Contains even more web! ''Art by kruggsmash]]
Another thing that can be done with a captured giant cave spider is turning it into a [[pet]]. They possess a pet value of 2,500, making them the most valuable animals in the game that aren't cave dragons or megabeasts. It's wasteful to simply [[butcher]] them for meat, as multiple spiders can be captured and bred in order to create a very formidable [[fortress defense]] force. The spiders are born adults and as such cannot be turned fully tame, but a skilled [[animal trainer]] will ensure they never revert into hostility.

Raiding [[kobold]] caves for livestock is an easy way to get tame giant cave spiders.

==Farming silk==
{{main|Silk farming}}
Giant cave spiders can be a very lucrative and nearly-inexhaustible source of [[silk]] [[thread]] for your [[weaver]]s. The general idea is to expose the spider to a target, causing it to spew [[web]]s - fairly easy. The trick is to have a system that can then, on demand, isolate the spider from those webs so they can be ''safely'' collected, and then allow the entire system to be reset to repeat the process. Well-designed silk farms can maximize safety and production and greatly increase fortress [[wealth]].

{{D for Dwarf}}

Contrary to popular belief, giant cave spiders will not enter a [[martial trance]] when struck from behind. There have been reports of them being slain by particularly feisty [[cat]] [[ranger]]s, [[butcher]]s, and [[necromancer]]s, however the mere possibility of cats having these [[skill#professions|professions]] has been heavily disputed.

{{gamedata}}
{{Creatures}}
{{Category|Animals}}
[[ru:Giant Cave Spider]]

Quarry bush

2026-05-25T22:43:23Z

Ziusudra: changed whip vine back to wine since the plant isn't cookable and the latter part of the sentence still used "wine"

{{Quality|Exceptional}}
{{plantlookup|uses=
* [[Food]]
|graphic=quarry_bush_shrub_sprite.png
|seedimage=quarry_bush_seeds_sprite.png
|wiki=no}}
{{av}}

The '''quarry bush''' is one of the six known [[subterranean]] [[crop]]s, and as such, it may only be grown [[underground]]. They can be [[farming|planted]] in [[Calendar|spring, summer and autumn]].

Harvesting a grown quarry bush will yield several leaves, and an equal amount of quarry bush ''plants'', which may be [[plant processing|processed]] into yet more leaves at a [[farmer's workshop]] by selecting the {{DFtext|Process plant to bag|7:0:1}} work order. You will need an empty bag available for this task. This will result in [[bag]]s of quarry bush leaves, which then must be [[cooking|cooked]] in the [[kitchen]] to be edible. Quarry bushes cannot be [[brewing|brewed]] into [[alcohol]].

Processing quarry bushes at a [[farmer's workshop]] requires one [[bag]], and will produce 5 quarry bush leaves (and one rock nut) for every plant in a given stack of quarry bushes. Unlike, say, [[flour]], quarry bush leaves do not ''need'' to stay in bags, but your dwarves will not usually take them out without micro-management (exception: leaves will be removed if taken for cooking while still in a farmer's workshop).

It is also possible to use the generic "process plants" job (which does not require a bag) on quarry bushes, but this will only yield '''one''' leaf per plant, and thus should be avoided whenever possible.

[[Cook]]ing quarry bush leaves can result in very large stacks of prepared food, thus saving space and [[barrel|barrels]]. In a fortress that relies on selling large, expensive stacks of prepared food, quarry bush leaves are great filler: a lavish meal made from [[whip vine|whip wine]] and [[cheese|dwarven cheese]] with two stacks of quarry bush leaves for filler, is worth almost ten times more than an easy meal made from wine and cheese alone.

Some [[dwarves]] [[Preferences|like]] quarry bushes for their ''gray leaves''.

==Rock nuts==

Quarry bush [[seed]]s are known as '''rock nuts'''. Although their material definition marks them as being edible raw, dwarves will '''not''' eat them.

Rock nuts can be milled at a [[millstone]] or [[quern]] into rock nut paste, using the {{k|s}} job to mill seeds/nuts to paste. This paste can then be used in cooking, or pressed at a [[screw press]] into a rock nut [[Press_cake|press cake]] and a [[jug]] of rock nut [[oil]].

Both the rock nut paste and rock nut press cake are cookable and considered a single food category, referred to as "rock nut" in the [[Labor#Kitchen|Kitchen tab]] in the Labor menu {{menu icon|y}} (not to be confused with "rock nuts", the entry for the seeds), the Stocks screen compacted view, and Prepared meal descriptions.

The rock nut oil can be cooked or used in place of tallow to make [[soap]].

Use moderation when commanding rock nuts to be converted to paste - the nuts are required to re-plant the crop; if you grind up your entire supplies, you can't grow new quarry bushes.

The main attraction of grinding up rock nuts is the production of rock nut oil as a soapmaking ingredient. Both the globs of paste and the press cakes are minimum-value cooking ingredients, at 1☼ each. When looking at cooking ingredients, the quarry bush leaves completely overshadow what can be gained from an oil-pressing operation. However, if you have a surplus of rock nuts such that you could never plant them all at once, it makes sense to use them for something productive.

==Plant Gathering==

Like with any [[plant]] growth, a wild quarry bush plant growing underground (not planted) will yield exactly ''one'' leaf when [[herbalist|gathered]], plus the usual random amount of quarry bushes, which can be processed into more leaves as usual.

==Food Value==

Thanks to the increased value of rock nut oil as a by-product of rock nut processing, the highest potential value of products gleaned from one quarry bush plant is 66 (six leaves at a value of 10 each, plus oil and a press cake).

*Grow time: 500
*Plant value: 2
*Spice value: 10(x6)
*Seed value: 1
*Mill value: 1
*Press cake value: 1
*Press oil value: 5

==Trivia==
Quarry bush [[seed]]s are refered to as rock nuts, despite the fact that nuts are a type of fruit, not seed.

{{gamedata}}
{{Plants}}

Children

2026-05-22T20:11:12Z

Ziusudra: /* Chores */ wording quibble, since they start small and get bigger, it "gets" better not worse

{{Quality|Superior}}
{{av}}
[[File:child_sprite_preview.png|right]]
Most [[creature]]s, including [[dwarf|dwarves]], start out as infants, then after a certain number of years become '''children''', and after that become adults - for dwarves, childhood starts after reaching one year of age, and continues until age 18.

In fortress mode, some migrant dwarves are [[marriage|married]] and may bring children. Children who immigrate to your [[fortress]] might be any age from one to 17. You can determine the age of any child by viewing their [[thoughts and preferences|thoughts]] screen, which will give you the child's exact age as well as their date of birth. This information is visible regardless of whether or not the child was born in your fortress.

"Resident" heterosexually [[marriage|married]] female dwarves may also give birth to children. Dwarves can even have [[miscarriage]]s (if they become dehydrated, starving, or are subjected to certain types of physical trauma), which causes an unhappy thought for the mother, but not for the father.

Much of [[goblin]] society is centered around [[thief|stealing the children]] of other races. The appropriate response to a baby-snatcher appearing on the map is the judicious use of a certain subdiscipline of [[magma|dwarven diplomacy]].

Humanoid creatures (the five main species) that are children or babies will appear as unique smaller sprites, and will appear to be wearing red if the option to show worn clothing dyes is disabled. Young animals and other creatures will have a smaller sprite than their adult counterparts, with some of them having baby sprites as well. Curiously enough, portraits can still show dwarven children with facial hair.
{{Translation
| dwarven = tilat
| elvish = imi
| goblin = tox
| human = shin
}}
==Babies==
[[File:dwarf_children.jpg|thumb|260px|right|Before they grow up to realize they're in an unwinnable game. ''Art by Devilingo'']][[File:df_baby_list.png|thumb|260px|right|Many children and a baby seen in the citizen information menu.]][[File:dwarf_child_portrait.png|thumb|96px|right|Portrait of a dwarven child.]]Babies do not have to be born in [[bed]]s, but are born wherever the mother happens to be, which will interrupt most current actions of the mother. The game will play the birth sound effect and [[announcement|announce]] the arrival of the baby. The mother will cancel whatever task she was in the middle of to seek her infant, and then will ''usually'' resume whatever task she was doing before the child was born. It is possible for dwarven mothers to give birth to twins or triplets, although that is exceedingly rare (1 out of 500), due to their [MULTIPLE_LITTER_RARE] token. Babies are looked after by their mother, who will continue working while carrying the babies.

[[Unconscious]] mothers will not wake up when they give birth – [[sleep]]ing and resting in a [[hospital]] will not be interrupted. Dwarves in a [[strange mood]] will also not interrupt their mood when giving birth – cancelling a mood forces instant insanity, so it is likely a coding choice to protect mothers (and children). Imprisoned mothers can grab their child if they give birth while on a chain, but cannot retrieve an infant that is out of their reach, which can cause massive problems, since a mother carrying a child is forced to drop it before being brought to prison. Most jobs performed by a mother upon giving birth will be immediately cancelled to pick up the baby, but for instance a current haul animal job, where the mother is already leading the animal, will not be cancelled, but will be finished before the infant is picked up.

If the mother is sleeping or otherwise prevented from collecting her infant, the baby will be free to roam as it pleases. An emancipated baby acts in a similar manner to a [[insanity|raving mad]] adult, wandering freely over the map without any sense of self-preservation, gravitating to [[Activity_zone#Meeting_area|meeting zone]]s. It may be fed and watered by other dwarves, and in recent versions, such care happens regularly enough to keep orphans alive. As long as a baby is not within reach of a hostile creature, no harm will be done to it. "Job cancellation spam" can be generated as the baby is seen by the game to be "insane" (example: "Urist McBabyname, Dwarven baby, cancels Clean Self: Too Insane"), but once it reaches childhood (at 12 months), that will stop, and they go about their business like any other dwarven child. While dwarven children are dressed in red, a baby's clothes will be dark yellow.

The sex of a baby is determined upon birth; this means that [[Cheating#Savescumming|reloading a save]] before a baby's birth might get a baby of the other sex. After giving birth, it is possible for the mother to become pregnant again immediately, and give birth to another child nine months later.

Babies will crawl to burrows when assigned to them.

Any baby being carried by its mother will effectively leech [[food]] and [[Thirst|drink]] from her, causing her to become hungry or thirsty at double the usual rate. This does not, however, count as alcohol consumption – when a baby is close to 1 year old, it will have severe withdrawal.

Babies can gain memories, although it seems that only thoughts with strong emotions can become the memory of a baby. Many thoughts (with strong emotions), which can become a memory, are able to change the dwarf's values/facets (upon becoming a core memory). And since babies (and small children) will, if any, only have few memories, such memories will have a tremendous effect on the dwarf's happiness (as they will continuously remember the same few memories). Most of the thoughts associated with strong emotions (in a baby) are negative thoughts, and only a few are positive. Of the negative thoughts observed to become memories, aside from the (negative) ones known to be able to change the dwarf's values/facets, is being pestered by vermin (but this thought does rarely become a memory, but being aggrevated by vermin might be another matter as vermin generating such thoughts are hated by the dwarven baby). On the positive side, aside from gaining a sibling (which will usually change the dwarf's values/facets later on), being "near to a favorite (caged) creature" can become a memory (and presumably also being near to a waterfall {{verify}}). All of this means that it is not advised to let a baby-carrying mother (and thus the baby) be caught in the rain. But it might be a good idea to let the baby-carrying mother walk by a cage containing a favorite creature of the baby, as babies getting such a positive memory might be "fine" upon becoming a child (and not merely content or even unhappy). Also, babies can gain knowledge of dance, music and poetry forms by watching performances, although they supposedly cannot gain any other skills (except when eg. taken on a raid mission by their mother).

The first order of business when a baby becomes a child is to pick up their clothing. After finishing that task, the child will start to play in the tile they picked up the last piece of clothing (although they might fetch a toy beforehand). This behaviour, by proper stockpile placement (and stockpile links) and having enough mittens/cloaks/hoods, can be exploited, so that the former dwarven baby will always play in a guildhall after becoming a child.

==Labor==
In [[fortress mode]], children can be assigned the relatively minor labors designated chores, below, but will also perform a few simple tasks on their own, such as:

* Socializing in [[location]]s, also holding [[performance]]s like singing, or reciting poetry (and they can gain skill levels in dancing, poetry and musical instruments). But children can perform music that they know anywhere and everywhere (especially if it only requires one performer), they are not bound by meeting places or locations, but instead start singing in a bedroom or stockpile instead. But performing seems to be currently gated, ie. only children, that have a musician and/or singing skill, will perform music, which means that children born in the current fortress will not display that behaviour, but "void" dwarf children (migrants) can as they can be created with such performance skills.
* Picking out, and wearing, their own [[clothing]].
* Watching (and even leading) guild demonstrations, provided the guild is open to all citizens.
* Attending meetings to complain to someone in charge, if unhappy (ie. as a 1 year old due to being caught in the rain as a baby).
* Eating, drinking, and sleeping as necessary.
* [[Farming|Harvesting]] [[crops]], if the "All dwarves harvest" [[standing orders|order]] is on. This will also increase their [[planter]] skill, which only happens very sporadically in the current version.
* When they want to, storing their items, including toys (specifically, they may perform a Store Item in Bin order for multiple toys).
* Children can play with [[toy]]s, such as puzzle boxes or toy axes, and might also play make believe. Both are basically filler jobs without tangible benefits, except for usually giving the child a happy thought and so unstressing the child (although some children might not feel anything instead).
* Fighting or running from hostiles, depending on circumstances. (Since children are small, can't use armor or weapons, and all start without combat skills, don't expect them to be effective fighters. Nor, for that matter, can they be assigned to squads.)
* Children can enter [[strange mood]]s, going about them the same as an adult dwarf. If they did not watch any guild demonstrations in a moodable skill (prior to the strange mood), they will attempt to make one artifact appropriate for a [[bone carver]], [[wood crafter]], or [[stonecrafter]], otherwise they will create an artifact according to the highest moodable skill (normal strange mood rules apply). They will also gain experience as normal if they complete it, except for possessed moods.
* Children respect [[burrow]] restrictions, including civilian alerts.
* Attempting to [[swim]] if submerged in [[water]].

Children may not be assigned to the [[noble|nobility]] and cannot join any guild (even if legendary in one of the required skills). However, they ''can'' be assigned bedrooms - even though children might still choose to sleep in their parents' bedroom instead of their own. If no tasks are available, they will gladly loiter in meeting areas, like [[dining room]]s for example, for the duration of their youth. Children born in the fort tend to follow their mother by preference, even (especially?) if their mother is a soldier and is currently going into battle.

Children are also known to be invisible to [[vampire]]s, thus making excellent crime detectors, as they speak truthfully in all cases.

The game will create an [[announcement]] when children reach adulthood, and can be assigned labors. This announcement will not pause and/or center the screen by default.

==Chores==
There is a chores tab under Labor/Standing Orders that allows players to disable/enable the chore tasks, which are:

* [[Feed patients/prisoners]]
* [[Milking]]
* [[Stone hauling]]
* [[Wood hauling]]
* [[Item hauling]]
* [[Burial]]
* [[Food hauling]]
* [[Refuse hauling]]
* [[Furniture hauling]]
* [[Animal hauling]]
* [[Trade good hauling]]
* [[Water hauling]]
* [[Cleaning]]
* [[Lever operation]]

Children don't seem to like chores, adding to their [[stress]] level and possibly causing them to become depressed and moody, which, as true with any adult, can then result in a child committing various [[Justice#Crimes|crimes]]. Turning off chores (if only for your more stressed children) will help alleviate this issue - you must decide for yourself if the increased mood is worth the loss of their labor.

Consider turning off Refuse Hauling and Burial as well; children tend to accumulate bad thoughts when hauling corpses, which can stress them out even more than it does adults. Also, children tend to start playing immediately after finishing a task, so if you leave Refuse Hauling on, they may decide that the corpse pile is an excellent playground, adding to the problem.

Furthermore, do not expect children who are younger than 12 years to be as good at hauling as their adult counterparts with similar physical attributes, as they are smaller and size does matter when it comes to hauling. It is even worse for children before they are at least one year & 168 days old (528 days total), as this is another size threshold.

Also note that children are exempt from punishment, so there should not be any repercussions for mandate violation if a child hauled export-prohibited items to the trade depot.

== Dwarven School (aka getting children to watch guild demonstrations) ==
Even though a real school for dwarven children does not exist yet, every guildhall (which is not only open for its members) can serve as a school for them. The only slight hurdles are having someone in the guildhall to teach lessons and getting the children to the guildhall (to study aka watch guild demonstrations). But both of these hurdles can be overcome easily.

First a big enough guildhall is needed and enough levers (preferably unlinked ones) installed in the guildhall, intended to be pulled by the dwarven children - these levers should not be assigned to anyone (of course other levers can be in the guildhall assigned to adult dwarves). If other levers are used for defenses etc. one lever for each such defensive purpose should preferably be located somewhere else, with nearby stockpiles for food and drink (and a few bedrooms for the defensive lever pullers) and a lockable door, so that some dwarves (needed to pull the defensive levers) can be locked in, when it is time to give some lessons to the children (and get them to the guildhall). Also, a work detail just for lever pulling should be created, and only the dwarves (locked in for the defensive lever duty) should be set to do these tasks (at least temporary). All other (adult) dwarves should not be allowed to pull any levers.

Temporarily set the intended teacher and some other adult dwarves (ie. substitute teachers) to not do any labors at all (not even hauling) and then also set them to do the lever-pulling work detail and set a few levers in the guildhall to be pulled (to get the teachers and substitute teachers into the guildhall). After they are in the guildhall, remove them from the lever pulling duty, and let them do some guild demonstrations.

Then disable all chores for children, except lever pulling (which needs to be enabled), and set all levers, which are unlined and not assigned to anyone, in the guildhall to be pulled. Every time a dwarven child takes up a task to pull any of the levers (can be seen in the task list) that dwarven child should be excluded from doing any chores at all (otherwise the dwarven child might decide to pull multiple levers). The child will still pull the lever (finish the current task) and then - unless the child spontaneously decides to pick-up equipment, eat, drink or sleep (in which case the chores for the child need to be enabled again)- the child will start socializing in the guild hall (at least if there is still a guild demonstration in progress or currently a new one is organized) and the child will watch the next guild demonstrations in the guildhall (usually until either the child decides to eat, drink, sleep, pickup some equipment, no new guild demonstrations are organized or some chores are again enabled for the child). This way more or less all children can be goaded into the guildhall to take some lessons (aka watch some guild demonstrations). When nearly all children are in the guildhall or have already watched some guild demonstrations, then the lever pulling of the adults can be reset to the original preference of the player and the locked (forbidden) door for the defensive lever pullers can be unlocked (unforbidden). Also after the player is satisfied with the learning progress of the children the original chores for the children can be set again - some children currently watching a guild demonstration can still be left to temporarily do not chores (if there are still some guild demonstrations in progress). Also the original labors of the teacher (and substitute teachers) can be enabled again.

''Note:'' If at any point, after some children have started watching guild demonstrations, if for one reason or another no one is present to give another guild demonstration, then all children will usually decide that the lessons are over and will immediately start to play (either in the guildhall or somewhere else)which is the main reason why there should be a teacher and substitute teachers present, and the labors for these have to be temporarily disabled (so that they will only leave the guildhall to eat, drink, sleep or pick-up equipment).

==Dwarven parenthood==

In the eighth [http://www.bay12games.com/dwarves/df_talk.html DFTalk], it was mentioned that, due to a programming oversight, children's parents can become so preoccupied with finding their children that they can die of thirst.

==Too many children==
If there are too many children in the fort, [[FPS]] may suffer. [[Unfortunate accident|Removing]] children is difficult, as doing so may quickly lead to [[stress]]. One possibility is to [[burrow]] children outside to aid [[thief|snatchers]]. To prevent a large population of children in the first place, it is preferred to set the child and/or strict population capacities in the [[Settings#Population_and_seed_capacities|settings]].

In longer-running forts, when a parent has more than 10 children of one gender, the 11th onward will merely be referred to as "son" or "daughter". The exception to this is that the youngest will always be referred to as "youngest son" or "youngest daughter".

==Non-dwarven children==
[[Human]]s, goblins, [[Elf|elves]], [[kobold]]s and subterranean [[animal people]] follow the same aging progress of dwarves (born as babies, becoming children at a year old then become adults at eighteen). The same is true for some races of wild humanoid creatures and [[semi-megabeast]]s, though some possess shorter or longer child states than dwarves do, e.g. [[troll]]s become adults at the age of 10. Regardless of how long their child states are, intelligent non-dwarf children are functionally identical to their dwarven counterparts for gameplay purposes.

Young animals possess limited capabilities compared to their adult stages. Infant [[milk]]-bearing livestock can't be milked, young [[wool]]-bearing animals can't be [[shear]]ed, and bird and reptile hatchlings are unable to lay [[egg]]s. However, unlike intelligent creatures, almost all animals follow a different aging progress; they skip the baby stage entirely and are born as children, who become adults at only 1 year of age (though they usually don't stop growing in size until the age of 2). Certain exceptions exist, however, such as [[elephant]]s, who take 10 years to reach adulthood. Savage [[animal people]] versions of these animals follow this same aging progress.

Certain creatures possess no child state to speak of, and are technically adults at birth, having all the capabilities of an 'adult' immediately after starting existing (though most of them are still subject to growing in size as they get older). These creatures include stuff like all species of snakes, [[crundle]]s, [[giant cave spider]]s, [[creeping eye]]s, [[magma crab]]s and most [[megabeast]]s. Inorganic creatures such as [[Gabbro man|gabbro men]], [[Fire man|fire men]] and [[Amethyst man|amethyst men]] also exist only as adults and never as children. If the creature born as an adult is an intelligent creature, they'll be born with generally mild levels in some skills.

Creatures capable of being [[invader]]s can do so regardless of age - as such, you may be attacked by a [[werebeast]] child, or a young [[roc]], [[giant]], [[cyclops]], [[ettin]] or [[minotaur]]. They will behave exactly like their adult counterparts, but will generally be easier to kill than adults due to their smaller size. Such cases are rare, as they require either children being infected by a werebeast and not dying in the process, or for megabeasts to breed, both being particularly uncommon occurrences.

If the mother of a child is not a historical figure (on birth of the child) the game will not keep track of the family relationship between parent and offspring. The game will also not keep track of offspring of male historical figures, unless the mother is already a historical figure at the time of the fertilization of the not yet laid eggs (in case of egg-layers) resp. at the time the pregnancy starts (non egg-layers).


{{Category|Dwarves}}
{{Category|Relationships}}
[[ru:Children]]

Release information/53.14

2026-05-20T21:18:29Z

Ziusudra: Creating release notes for v53.14

{{release notes}}
:This small patch fixes a crash to do with the changes to announcements from [[Release_information/53.13|last time]].
:—[[Toady One]], May 20, 2026
* [https://www.bay12forums.com/smf/index.php?topic=183877.msg8616947#msg8616947 Bay 12 Forum post]
* [https://www.bay12games.com/dwarves/index.html#2026-05-20 Patch note on Bay 12 Games]
* [https://store.steampowered.com/news/app/975370/view/653729380381491342 Patch note on Steam]
* [https://kitfoxgames.itch.io/dwarf-fortress/devlog/1528872/patch-5314 Patch note on itch.io]

Version history

2026-05-20T21:12:48Z

Ziusudra: /* Dwarf Fortress v53 */ .14

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.14|53.14]] || 2026-5-20
| ''Hotfix'' for announcements crash
|-
| [[Release information/53.13|53.13]] || 2026-5-13
| More messenger actions, idle undead and pathing optimizations, and general fixes
|-
| [[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-05-20T21:10:58Z

Ziusudra: 53.14

{{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}}
{{release notes link|53.13}}
{{release notes link|53.14}}

Template:Current/lastupdate

2026-05-20T21:10:18Z

Ziusudra: 53.14

May 20, 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>

Release information/53.13

2026-05-13T21:56:05Z

Ziusudra: /* 20th Anniversary of Dwarf Fortress */ added missed link

{{release notes}}
:This patch gives messengers more tasks, like the ability to make peace and improve or open trade relations. You can assign messengers in the same menu where you assign other positions like the manager and broker, and you can give them missions from the world screen (button on the lower right.) There are also some optimizations and other fixes.
:—[[Toady One]], May 13, 2026

:Hey Urists,
:We’ve got another patch/community news hybrid post today! There’s lots on the go right now as we prepare for a packed summer of news and updates. The artists are finishing up dinos and continuing with the art for the Myth and Magic update. You can expect to see the dinosaur update next and we'll be sharing a release date very soon. Tarn is also in full Wizard-mode but in the meantime, he has a new patch with a focus on diplomacy and bugs.
:See you next time, with dinos!
:—[[Alexandra]], May 13, 2026
* [https://www.bay12forums.com/smf/index.php?topic=183877.0 Bay 12 Forum thread]
* [https://www.bay12games.com/dwarves/index.html#2026-05-13 Patch notes on Bay 12 Games]
* [https://store.steampowered.com/news/app/975370/view/693135146596958388 Patch notes on Steam]
* [https://kitfoxgames.itch.io/dwarf-fortress/devlog/1521849/diplomacy-improvements-20th-anniversary-dwarf-fortress-patch-5313 Patch notes on itch.io]

== Diplomacy ==
* Your appointed [[messenger]]s can now do a variety of diplomatic [[mission]]s from the [[Civilization_and_World_Info|world screen]]. Make peace, declare war, make contact, and improve [[trade]]. You can also seek alliances if you have the [[monarch]] in your fortress.
* Increased the priority of messenger actions.
* It's possible to open trade with [[human]]s and [[elf|elves]] before their usual time if you send a messenger. You can also open trade with multiple [[civilization]]s of the same type.
* If traders don't make decent profits and you do not engage in [[Trade_agreement|negotiations]], trade will taper off.
* Added confirmation to mission interface.
* Changed some colors on mission interface.
* Added a dialog line for dwarven traders from other civilizations.
* Fixed issue where [[Difficulty#Individual_enemy_toggles|turning enemies off]] lead to early caravans (requires resetting difficulty to apply).

== General updates ==
* Optimization: [[Undead|zombies]] don't consider their surrounding until disturbed.
* Optimization: throttled creatures trying to repeatedly failing [[path]].
* Added announcements for residents and creatures that have begun throttling pathing.
* Can view activity details again from the [[Unit list|residents list]].
* Stopped scroll bar from disappearing when closing bins near the bottom of the trade list.
* Increased the maximum number of [[announcement]]s that can be saved.
* Prioritized the removal of [[sparring]] announcements from the announcement list.
* Tries to repair corrupted musical [[instrument]]s upon load.
* Did some exception handing for map saving and loading.
* Added the ability to display all logged errors on screen (useful for debugging mods etc).

== Tarn and Zach open their Magic: The Gathering cards ==
In case you missed it, Tarn and Zach just received their copies of the new Secret Lair x Dwarf Fortress collection of Magic: The Gathering cards. [https://youtu.be/2nMRSBXQDpw They open their packs together and reminisce about ASCII Dwarf Fortress and getting into Magic in the 90s]. You can still [https://secretlair.wizards.com/us/product/1250417/secret-lair-x-dwarf-fortress-create-new-world pre-order the cards here].

== 20th Anniversary of Dwarf Fortress ==
[[File:DF20thAnniversary.png|400px|right]]This year we are celebrating the 20th anniversary of Slaves to Armok: God of Blood Chapter II: Dwarf Fortress. To start, we have a new special logo for the occasion featuring Armok himself, who has never been depicted until now! Credit goes to artist Jacob for the new portrait. You can expect to see more 20th anniversary events throughout the rest of the year. If you’re interested in hosting your own Dwarf Fortress gathering, we’ve opened up a [https://forms.gle/TsimLyvt5zLyTikU7 form where you can apply for merch support here].

Development arc

2026-05-13T21:36:30Z

Ziusudra: /* Next */ swapped order

In earlier days of ''Dwarf Fortress'', development was split up into outlined specific '''Arcs'''. That system has been replaced by a short list of future releases given names after their main focus by [[Toady One]].

== Named Releases ==
=== Future ===
==== Next ====
* [https://youtu.be/LTV5R7JIMQY?t=113 Prehistoric and extinct animals].
* A second siege release focused "[[Release_information/53.07#What.27s_Next_for_Sieges.3F|on magic, armies, and diplomacy]]".

==== Later ====
* The adventure mode site building: the return of [[Camp#Adventurer_camps|camp founding and building]], plus more "cross-mode play and Adventure mode crafting".
* The map rewrites: A rework of the generated spaces and regions, allowing for more dynamic and reactive worlds, with changes focused on the underground, but also some changes above. It has been previously known as the "Big Wait" before myth and magic, but is planned to be released incrementally alongside smaller magical features.
* More villains releases: the continuation of the villains release, finishing what was left when focus shifted to the premium release, divided into multiple smaller releases.
* More myth and magic, world changes, "probably through covens and religion", starting scenarios, and civilization improvements.
==== Sources ====
* ''[https://www.bay12forums.com/smf//index.php?topic=183664.0 The Bay 12 Games Report, January 1st 2026]''
* ''[https://store.steampowered.com/news/app/975370/view/520859243419533943 Dwarf Fortress Patch 53.07 🏹 What’s next for Sieges? + New animal portraits]'' Steam news.
* ''[https://www.youtube.com/watch?v=cbzttKQofFg What's Next for Sieges? - Tarn Time (Winter 2025)]'' YouTube video.
* ''[https://www.bay12games.com/dwarves/dev.html Dwarf Fortress Development]'' Bay 12 Games website page (last updated: December 18, 2025).
* ''[https://store.steampowered.com/news/app/975370/view/530964346754301996 Next Steps for Dwarf Fortress + Patch 51.05 ⛏ Dwarf Fortress Dev News]'' Steam news.
* ''[https://www.youtube.com/watch?v=zw_-jdN8zcA Tarn Time - Dwarf Fortress Seasonal Update (Spring 2025)]'' YouTube video.

=== Possible Future ===
These are things that have been discussed as future releases, but have not been officially announced.
* More [[Lua]] functionality, including UI exposure to allow for more mouse versus keyboard control flexibility.
* The boats release: will feature, well, boats, with all that entails (ports, maritime trade routes, pirates, and so on). Probably multi-tile creatures as well, as mechanics on how to make boats (floating superstructures) work will be borrowed to make multi-tile creatures as well.
* The economy release: will piggyback on the new trade and property stuff to establish a new framework that will completely overhaul the old (and deactivated) [[economy]] system.

=== Past ===
* The [[night creature]] release ([[v0.34:Release_information|0.34.01]]): added [[necromancer]]s, [[mummy|mummies]], [[vampire]]s, [[werebeast]]s as well as a complete [[undead]] overhaul. Other notable additions include evil [[weather]], improved human [[site]]s featuring [[catacombs]], [[sewer]]s and [[dungeon]]s, and a number of animals added to the game.
* The [[World activities|world activation]] release ([[DF2014:Release_information/0.40.01|0.40.01]]): allowed many [[world generation]] activities to carry on during normal gameplay, as opposed to a static world. Other notable additions include non-human [[site]]s, multi-tile trees, retireable fortresses, claimable non-player fortresses and a great variety of plants and additional animal people.
* The [[tavern]] release ([[DF2014:Release_information/0.42.01|0.42.01]]): added taverns and [[visitor]]s to the game. Other notable additions include fortress [[temple]]s, [[library|libraries]] (with [[scholar]]s complete with a [[knowledge]] system), a [[paper]] industry, art forms (music, dance and writing) and non-dwarven citizens.
* The [[artifact]] release ([[DF2014:Release_information/0.44.01|0.44.01]]): added non-player artifacts to the game. Other notable additions include the ability to send [[squad]]s of dwarves off the map (on [[mission]]s to raid sites, rescue citizens, retrive artifacts, explore ruins and so on), secret [[agent]]s, non-player [[quester]]s and improved [[kobold]] sites.
* The [[villain]]s release (first part) ([[DF2014:Release_information/0.47.01|0.47.01]]): added villains to the game, giving them goals and the ability to subvert other people into various corruption activities such as embezzlement, sabotage, kidnapping or assassination. Other notable additions included improved relationships (divorce and remarriage, children outside marriage, different kinds of friendships), improved religions (featuring prophets and monastic orders), trade companies, craft guilds, new sites (monasteries, bandit forts and the return of castles) as well as several new [[night creature]]s. This release was cut short, leaving out most of the [[cv:fortress mode|fortress mode]] and [[cv:adventure mode|adventure mode]] villainy, to hasten the Premium release.
* The Premium release (or the Steam release) ([[Release_information/50.01|50.01]]): the first commercial release of ''Dwarf Fortress''. also known as ''Dwarf Fortress Premium''. As the primary commercial platform is [https://store.steampowered.com/app/975370/Dwarf_Fortress/ Steam], it is also known as the Steam release, though it is also available on [https://kitfoxgames.itch.io/dwarf-fortress itch.io]. It included a complete overhaul of UI and graphics, bug fixes, as well as an official pixel-art [[graphics set]]. A concurrent free version is still available as ''Dwarf Fortress Classic'' (Available on 12/22/22 since version 50.04 at [https://bay12games.com/dwarves/ Bay 12 Games]), which has feature parity but not the official graphics set.
* The adventure release ([[Release_information/51.01|51.01]]): Re-enables [[Adventurer mode]] with a new interface and additional graphics. Added [[:Category:Myth|mythical]] features such as [[chosen]] adventurers and [[mysterious dungeon]]s.
* The initial Lua scripting release ([[Release_information/52.01|52.01]]): Exposed previously hard-coded "procedural object generation, like the forgotten beasts, divine curses (vampires and werebeasts), divine items, necromancers and their lieutenants and experiments, evil weather, and so forth."
* The first siege release ([[Release_information/53.01|53.01]]): An improvement of [[siege]]s, with a focus on more intelligent invader tactics, balanced [[trap]]s, and updated [[siege engine]]s. [https://store.steampowered.com/news/app/975370/view/530964346754301996][https://store.steampowered.com/news/app/975370/view/528732929177683220][https://store.steampowered.com/news/app/975370/view/536616130148565319][https://store.steampowered.com/news/app/975370/view/530987265859522075]

== Old arcs ==
''Dwarf Fortress'' development has moved away from the old large arc based strategy. The old [[Consolidated Development]] page lists 21 "short-term arcs" and 15 "long-term arcs". Not all arcs would have taken take the same length of time to complete. Each arc also encompassed certain cores, requirements, bloats, and power goals.

Here are a few notable ones:
*[[Army arc]]: possibly the biggest endeavor out of all the current arcs, it was never fully completed. Version 0.31.01 introduced many army arc features.
*[[Caravan arc]]: another famous arc, focusing on fleshing out the caravans (Status unknown as of v0.47.05, may have been completed.)
*[[County arc]]
*[[Life cycle arc]]
*[[Presentation arc]]

[[Category:Arcs| ]]
[[Category:Game development]]
{{unversioned}}
[[ru:Development arc]]

Release information/53.13

2026-05-13T21:34:38Z

Ziusudra: Creating release notes for v53.13

File:DF20thAnniversary.png

2026-05-13T21:28:41Z

Ziusudra:

== Licensing ==
{{Non-free Dwarf Fortress Screenshot}}

Version history

2026-05-13T21:09:12Z

Ziusudra: /* Dwarf Fortress v53 */ .13

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.13|53.13]] || 2026-5-13
| More messenger actions, idle undead and pathing optimizations, and general fixes
|-
| [[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-05-13T21:04:02Z

Ziusudra: 53.13

Template:Current/lastupdate

2026-05-13T21:03:10Z

Ziusudra: 53.13

May 13, 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>

Development arc

2026-05-11T02:39:43Z

Ziusudra: /* Named Releases */ removed released bugfix patch, added prehistorics

In earlier days of ''Dwarf Fortress'', development was split up into outlined specific '''Arcs'''. That system has been replaced by a short list of future releases given names after their main focus by [[Toady One]].

== Named Releases ==
=== Future ===
==== Next ====
* A second siege release focused "[[Release_information/53.07#What.27s_Next_for_Sieges.3F|on magic, armies, and diplomacy]]".
* [https://youtu.be/LTV5R7JIMQY?t=113 Prehistoric and extinct animals].
==== Later ====
* The adventure mode site building: the return of [[Camp#Adventurer_camps|camp founding and building]], plus more "cross-mode play and Adventure mode crafting".
* The map rewrites: A rework of the generated spaces and regions, allowing for more dynamic and reactive worlds, with changes focused on the underground, but also some changes above. It has been previously known as the "Big Wait" before myth and magic, but is planned to be released incrementally alongside smaller magical features.
* More villains releases: the continuation of the villains release, finishing what was left when focus shifted to the premium release, divided into multiple smaller releases.
* More myth and magic, world changes, "probably through covens and religion", starting scenarios, and civilization improvements.
==== Sources ====
* ''[https://www.bay12forums.com/smf//index.php?topic=183664.0 The Bay 12 Games Report, January 1st 2026]''
* ''[https://store.steampowered.com/news/app/975370/view/520859243419533943 Dwarf Fortress Patch 53.07 🏹 What’s next for Sieges? + New animal portraits]'' Steam news.
* ''[https://www.youtube.com/watch?v=cbzttKQofFg What's Next for Sieges? - Tarn Time (Winter 2025)]'' YouTube video.
* ''[https://www.bay12games.com/dwarves/dev.html Dwarf Fortress Development]'' Bay 12 Games website page (last updated: December 18, 2025).
* ''[https://store.steampowered.com/news/app/975370/view/530964346754301996 Next Steps for Dwarf Fortress + Patch 51.05 ⛏ Dwarf Fortress Dev News]'' Steam news.
* ''[https://www.youtube.com/watch?v=zw_-jdN8zcA Tarn Time - Dwarf Fortress Seasonal Update (Spring 2025)]'' YouTube video.

=== Possible Future ===
These are things that have been discussed as future releases, but have not been officially announced.
* More [[Lua]] functionality, including UI exposure to allow for more mouse versus keyboard control flexibility.
* The boats release: will feature, well, boats, with all that entails (ports, maritime trade routes, pirates, and so on). Probably multi-tile creatures as well, as mechanics on how to make boats (floating superstructures) work will be borrowed to make multi-tile creatures as well.
* The economy release: will piggyback on the new trade and property stuff to establish a new framework that will completely overhaul the old (and deactivated) [[economy]] system.

=== Past ===
* The [[night creature]] release ([[v0.34:Release_information|0.34.01]]): added [[necromancer]]s, [[mummy|mummies]], [[vampire]]s, [[werebeast]]s as well as a complete [[undead]] overhaul. Other notable additions include evil [[weather]], improved human [[site]]s featuring [[catacombs]], [[sewer]]s and [[dungeon]]s, and a number of animals added to the game.
* The [[World activities|world activation]] release ([[DF2014:Release_information/0.40.01|0.40.01]]): allowed many [[world generation]] activities to carry on during normal gameplay, as opposed to a static world. Other notable additions include non-human [[site]]s, multi-tile trees, retireable fortresses, claimable non-player fortresses and a great variety of plants and additional animal people.
* The [[tavern]] release ([[DF2014:Release_information/0.42.01|0.42.01]]): added taverns and [[visitor]]s to the game. Other notable additions include fortress [[temple]]s, [[library|libraries]] (with [[scholar]]s complete with a [[knowledge]] system), a [[paper]] industry, art forms (music, dance and writing) and non-dwarven citizens.
* The [[artifact]] release ([[DF2014:Release_information/0.44.01|0.44.01]]): added non-player artifacts to the game. Other notable additions include the ability to send [[squad]]s of dwarves off the map (on [[mission]]s to raid sites, rescue citizens, retrive artifacts, explore ruins and so on), secret [[agent]]s, non-player [[quester]]s and improved [[kobold]] sites.
* The [[villain]]s release (first part) ([[DF2014:Release_information/0.47.01|0.47.01]]): added villains to the game, giving them goals and the ability to subvert other people into various corruption activities such as embezzlement, sabotage, kidnapping or assassination. Other notable additions included improved relationships (divorce and remarriage, children outside marriage, different kinds of friendships), improved religions (featuring prophets and monastic orders), trade companies, craft guilds, new sites (monasteries, bandit forts and the return of castles) as well as several new [[night creature]]s. This release was cut short, leaving out most of the [[cv:fortress mode|fortress mode]] and [[cv:adventure mode|adventure mode]] villainy, to hasten the Premium release.
* The Premium release (or the Steam release) ([[Release_information/50.01|50.01]]): the first commercial release of ''Dwarf Fortress''. also known as ''Dwarf Fortress Premium''. As the primary commercial platform is [https://store.steampowered.com/app/975370/Dwarf_Fortress/ Steam], it is also known as the Steam release, though it is also available on [https://kitfoxgames.itch.io/dwarf-fortress itch.io]. It included a complete overhaul of UI and graphics, bug fixes, as well as an official pixel-art [[graphics set]]. A concurrent free version is still available as ''Dwarf Fortress Classic'' (Available on 12/22/22 since version 50.04 at [https://bay12games.com/dwarves/ Bay 12 Games]), which has feature parity but not the official graphics set.
* The adventure release ([[Release_information/51.01|51.01]]): Re-enables [[Adventurer mode]] with a new interface and additional graphics. Added [[:Category:Myth|mythical]] features such as [[chosen]] adventurers and [[mysterious dungeon]]s.
* The initial Lua scripting release ([[Release_information/52.01|52.01]]): Exposed previously hard-coded "procedural object generation, like the forgotten beasts, divine curses (vampires and werebeasts), divine items, necromancers and their lieutenants and experiments, evil weather, and so forth."
* The first siege release ([[Release_information/53.01|53.01]]): An improvement of [[siege]]s, with a focus on more intelligent invader tactics, balanced [[trap]]s, and updated [[siege engine]]s. [https://store.steampowered.com/news/app/975370/view/530964346754301996][https://store.steampowered.com/news/app/975370/view/528732929177683220][https://store.steampowered.com/news/app/975370/view/536616130148565319][https://store.steampowered.com/news/app/975370/view/530987265859522075]

== Old arcs ==
''Dwarf Fortress'' development has moved away from the old large arc based strategy. The old [[Consolidated Development]] page lists 21 "short-term arcs" and 15 "long-term arcs". Not all arcs would have taken take the same length of time to complete. Each arc also encompassed certain cores, requirements, bloats, and power goals.

Here are a few notable ones:
*[[Army arc]]: possibly the biggest endeavor out of all the current arcs, it was never fully completed. Version 0.31.01 introduced many army arc features.
*[[Caravan arc]]: another famous arc, focusing on fleshing out the caravans (Status unknown as of v0.47.05, may have been completed.)
*[[County arc]]
*[[Life cycle arc]]
*[[Presentation arc]]

[[Category:Arcs| ]]
[[Category:Game development]]
{{unversioned}}
[[ru:Development arc]]

Underworld

2026-05-11T02:20:23Z

Ziusudra: /* Starting Adventure mode in the Underworld */ stated current impossibility, commented out method

{{Quality|Exceptional}}
{{av}} Caution: This article contains '''HFS''' (Hidden Fun Stuff). Reader discretion is advised.
{{spoiler}}
[[File:V50 underworld.png|thumb|right|400px|A portion of the Underworld. The large pink & black areas are eerie glowing pits, which go all the way to the lowest z-level in the map. Demons can be seen wandering through it.]]
:''"Hidden fun stuff", "HFS" and "eerie glowing pit" redirects here. For other hidden content in the game, see [[easter eggs]].''

The '''Underworld''' is the absolute bottom of the world, located below the [[semi-molten rock]] reached by digging under the [[magma sea]] and breaching a hollow [[raw adamantine]] vein. Breaching it serves as the end-game of [[dwarf fortress mode]] for those unfortunate or [[Stupid dwarf trick|daring enough]] to do so.

== Details ==

[[File:V50 adamantine spire.png|thumb|right|400px|A cross section of a typical adamantine spire you will need to mine through in order to reach the underworld. Beware that the single empty tiles are likely to contain fun surprises!]]
The Underworld takes the form of a massive open cavern of [[slade]], dotted with giant, bottomless eerie glowing pits ({{Tile|*|4:0:1}}) which will instantly kill anything that falls into them (unless [[floor]]s are constructed over them). It is inhabited by [[demon]]s who, when first encountered, will immediately rush to the nearest exit they can find, typically leading to overwhelming amounts of [[fun]]. The initial demon invasion may reach well over a hundred attackers, sometimes leading to [[Frames per second|FPS death]] before they even reach the fortress itself.

The Underworld expands out in all directions without bound, with a height varying between 1-4 [[z-level]]s. Its rough floor slopes up and down, making it possible to walk around and explore should you get an [[Adventurer mode|adventurer]] down there. If you dig down through a hollow adamantine pillar, but had previously blocked off the particular hallway with a drawbridge and raise it, you can discover the location of all adamantine on the map with no negatives.

Demons spawn on the edges of the Underworld much like animals do on the surface; demons thus spawned will typically rush towards your fortress in order to destroy buildings, as they are [[building destroyers]]. Do note that at the moment building destroyers are bugged and will get stuck when trying to destroy locked doors. It is yet unclear whether the number of demons is finite; in information exported from the legends screen, the population of demonic species is listed as "unnumbered", a descriptor usually reserved for [[ant]]s, [[worm]]s, and other omnipresent [[vermin]]. Clusters of [[web]]s can be found scattered across the Underworld's surface, marking the presence of demons able to spew webs as a form of combat. In worlds [[Advanced world generation|generated]] without demons, the Underworld is empty and [[goblin]]s are not present either, but goblins can still appear through historical deep-dig disasters.

If not properly prepared, breaching into the Underworld can wipe out the entire fortress in seconds - it will be burned to ashes, and levers will often be useless for blocking them off through bridges, because those demons are extremely fast.

When digging through the adamantine spire, there is a mixture of 7/7 squares of magma and water, obsidian, high-quality gems, and raw adamantine. Intermingled with this are single-tile empty squares, which can contain four different types of things:

# An artifact made with [[divine metal]]. "Deep within this strange place, we've uncovered what must be a treasure of the gods!"
# A gout of flame which shoots in a random direction - if it strikes the miner, they will be set on fire. Otherwise, it will harmlessly strike a wall nearby, and burn out shortly. "We checked that stone for heat! What devilry is this?!"
# A single [[demon]]: "Something evil is emerging from this newly exposed pocket!" '''or''' "Some ancient horror was encased here, until now!"
# A single [[angel]]: "We have unleashed the echo of a forgotten divine retribution!" '''or''' "Apocalypse! We are being judged by the gods!" If you dig out both of these at the same time, they will fight each other.

== Names ==

Upon first discovery, the place is referred to as an ''eerie cavern''. Nearly all other references in the game, including dialogues and descriptions, call it ''Underworld'' or ''underworld''.

'''Hell''' is a popular alternative name among DF players due to its hellish overtones, but it is rarely referred to as such in-game. ''Hell'' is included in the game's [[language]]s, and generated names for people, sites, regions, etc., can contain the word ''hell''. When the Underworld and its contents are spoken of in the context of spoilers, players frequently use the term "'''Hidden Fun Stuff'''" ('''HFS''') or the "'''circus'''" (with demons nicknamed "clowns").

==World generation==

In world generation, two kinds of gates to the underworld can be created: [[deity|deties]] may thrust [[underworld spire]]s as part of their ritual to bring unique demons into the world, and [[goblin]] civilizations will be built around those; or dwarven sites may dig too deep, inadvertently breaching into the underworld, with new civilizations created to rule from those sites, with both goblin and non-unique demon citizens. Only the first kind leads to an actual physical passage into the underworld, and every such initial goblin civilization will contain one, while only the second kind will make that underworld region known in legends mode.

== Reaching the Underworld ==
===Fortress mode===

[[File:Underworld.png|thumb|right|390px|Not the best vacationing spot.]]
Upon digging sufficiently deep (usually z-level ~160, but it can vary wildly) you will find [[Magma sea|huge magma lakes]]. These are surrounded by [[semi-molten rock]] which cannot be cleared by digging, but seems otherwise stable. Eventually, you will reach a layer which contains nothing but molten rock and little to no possibilities to pass. You can reach the critical layer by digging through solid rock which gets rarer the deeper you dig. In fortress mode, there are two ways through the impassable layer:

'''Digging through an adamantine vein:''' [[Raw adamantine]] veins are shaped like vertical tubes and breach through any layer of semi-molten rock, right down into the Underworld. The lower layers of the vein are often hollow and act as a tube, leading straight to your doom. Breaching into the hollow center of a vein has the same effect as breaching into the Underworld, so beware. You could easily dig around the hollow core provided you knew where it was, but every vein's hollow center is located at a different height - the risk is all part of the [[fun]]. Adamantine veins always seem to end in mid-air, so once you breach the final layer, you will face a horde of demons which hovers directly below your feet.

'''Channeling through semi molten rock:''' It is possible to channel into semi-molten rock (and, to a lesser extent, slade) from above, as long as the tile below is not yet discovered. In older versions, you had to remove the magma-flow and ramps in a complicated procedure that killed one dwarf per level, but now it is possible to channel directly into the underworld without losing a dwarf, though the miner tapping it will likely get killed by demons or drop into an eerie glowing pit. The difference is that, in older versions, the miner was placed onto the magma flow, but now they are placed under the magma flow, and can channel on.

* Start one or more levels above the lowest rock layer above the magma flow. (this is important, as the miner must fall below the magma flow)
* designate channels (d-h) from here down to the bottom of the map.
* The miner will first generate a downward ramp into the rock. Now build a hatch above this ramp.
* The miner walks down this ramp, and channels into the semi-molten rock, as the game only sees the granite upward slope.
* Now, the miner is trapped below a magma flow (floor) and surrounded by semi molten rock. They will proceed to channel down until they reach the underworld, leaving magma flow tiles above them, as well as channel one level into slade. (if they survive long enough)
* You now have a chute - blocked by magma flow floors - into the underworld. By constructing up/down stairways, you can build a stairway into the underworld (the magma flow is removed in that process).
* If the site has no adamantine (otherwise you probably wouldn't do that), no demons will be generated (except the "wildlife"-demons), and you might even be able to save the miner, if you build the stairway before he starves to death.
* As both magma-free pillars and eerie glowing pits are placed in the corners of embark tiles, the miner will likely fall into an eerie glowing pit - use zones ({{K|i}}) to find solid slade floor and prevent this from happening.

[[File:eerie_cavern.png|thumb|405px|Announcement upon revealing the Underworld]]

Regardless of the method of breaching, you will receive an announcement upon piercing the Underworld. One step later, you will get a second announcement: '''''"Horrifying screams come from the darkness below!"''''' At this point, a ''massive'' number of demons will be spawned - though the number is not fixed, the demons will likely fill many pages on the Units screen. You'd do well to prepare for the worst.

===Adventure mode===

In adventure mode, one may find huge slade [[underworld spire]]s built as gateways to the Underworld. Only the sites that a unique demon rose up from will have an opening into the Underworld. The lowermost levels of these structures indeed lead directly into the Underworld, with several demons waiting below. Due to the underworld spire more or less having to reach the very bottom of the world, the player almost always has to go down at least over a hundred z-levels. Combined with the FPS drop that comes with being near a goblin civilization due to all the activity, it may take a while.

Alternatively, adventurers may enter through player made fortresses that have opened a way into the Underworld. Generated Dwarven sites do not enter the Underworld, even if they have allegedly breached into an eerie cavern during world generation, and will terminate at the top of the magma sea.

Be warned that demons make for highly dangerous opponents for an adventurer: they are big, fast, strong, don't feel pain, don't get stunned or exhausted, and unless you get lucky and one is generated as being composed of something like salt, they frequently can take quite a bit of punishment, especially if they're made of a metal. Finally, like Titans/Forgotten Beasts demons possess a procedurally generated special attack that may or may not easily ruin your day.

==== Starting Adventure mode in the Underworld ====
This is not possible as Adventure camps are not currently available, though it was in the past and possibly will be in some [[Development_arc#Future|future]] version.


== Invading the Underworld ==
Assuming you survive the initial onslaught, you may then proceed to explore the newly discovered land. The most impressive example of this feat is recorded by Sethatos in [http://www.bay12forums.com/smf/index.php?topic=156319.msg6814181#msg6814181 Archcrystal]. Dwarves of the highest skill are recommended.

Note that the Underworld is completely devoid of useful resources, as most demons are sentient and cannot be [[butcher]]ed, there are no [[plant]]s, [[water]], [[soil]] or [[ore]]s, and the unique [[slade]] rock the Underworld is made out of cannot be mined. The only reason one would have to invade the Underworld is pure bragging rights.

{{D for Dwarf}}

== After Settling In ==
For training purposes, the Underworld is a perfect place for a Dwarven Boot Camp. Even if a soldier dies in the battle for hell, you can track down their sorry dwarven butts, and drag them out of the eerie glowing pit... And right back to boot camp! Side effects of Underworld Boot Camp include: Mental trauma; repeated cases of death; losing the will to live; [[fun]].

{{Translation
| dwarven = Arôloram
| elvish = Tariteyo
| goblin = Sumspabuzong
| human = Ngironra
}}

{{World}}
[[Category:Spoilers]]
{{Category|HFS}}

Underworld

2026-05-11T01:57:43Z

Ziusudra: /* World generation */ changed breach civ behavior, fixed plurality disagreement, add underworld region in legends

{{Quality|Exceptional}}
{{av}} Caution: This article contains '''HFS''' (Hidden Fun Stuff). Reader discretion is advised.
{{spoiler}}
[[File:V50 underworld.png|thumb|right|400px|A portion of the Underworld. The large pink & black areas are eerie glowing pits, which go all the way to the lowest z-level in the map. Demons can be seen wandering through it.]]
:''"Hidden fun stuff", "HFS" and "eerie glowing pit" redirects here. For other hidden content in the game, see [[easter eggs]].''

The '''Underworld''' is the absolute bottom of the world, located below the [[semi-molten rock]] reached by digging under the [[magma sea]] and breaching a hollow [[raw adamantine]] vein. Breaching it serves as the end-game of [[dwarf fortress mode]] for those unfortunate or [[Stupid dwarf trick|daring enough]] to do so.

== Details ==

[[File:V50 adamantine spire.png|thumb|right|400px|A cross section of a typical adamantine spire you will need to mine through in order to reach the underworld. Beware that the single empty tiles are likely to contain fun surprises!]]
The Underworld takes the form of a massive open cavern of [[slade]], dotted with giant, bottomless eerie glowing pits ({{Tile|*|4:0:1}}) which will instantly kill anything that falls into them (unless [[floor]]s are constructed over them). It is inhabited by [[demon]]s who, when first encountered, will immediately rush to the nearest exit they can find, typically leading to overwhelming amounts of [[fun]]. The initial demon invasion may reach well over a hundred attackers, sometimes leading to [[Frames per second|FPS death]] before they even reach the fortress itself.

The Underworld expands out in all directions without bound, with a height varying between 1-4 [[z-level]]s. Its rough floor slopes up and down, making it possible to walk around and explore should you get an [[Adventurer mode|adventurer]] down there. If you dig down through a hollow adamantine pillar, but had previously blocked off the particular hallway with a drawbridge and raise it, you can discover the location of all adamantine on the map with no negatives.

Demons spawn on the edges of the Underworld much like animals do on the surface; demons thus spawned will typically rush towards your fortress in order to destroy buildings, as they are [[building destroyers]]. Do note that at the moment building destroyers are bugged and will get stuck when trying to destroy locked doors. It is yet unclear whether the number of demons is finite; in information exported from the legends screen, the population of demonic species is listed as "unnumbered", a descriptor usually reserved for [[ant]]s, [[worm]]s, and other omnipresent [[vermin]]. Clusters of [[web]]s can be found scattered across the Underworld's surface, marking the presence of demons able to spew webs as a form of combat. In worlds [[Advanced world generation|generated]] without demons, the Underworld is empty and [[goblin]]s are not present either, but goblins can still appear through historical deep-dig disasters.

If not properly prepared, breaching into the Underworld can wipe out the entire fortress in seconds - it will be burned to ashes, and levers will often be useless for blocking them off through bridges, because those demons are extremely fast.

When digging through the adamantine spire, there is a mixture of 7/7 squares of magma and water, obsidian, high-quality gems, and raw adamantine. Intermingled with this are single-tile empty squares, which can contain four different types of things:

# An artifact made with [[divine metal]]. "Deep within this strange place, we've uncovered what must be a treasure of the gods!"
# A gout of flame which shoots in a random direction - if it strikes the miner, they will be set on fire. Otherwise, it will harmlessly strike a wall nearby, and burn out shortly. "We checked that stone for heat! What devilry is this?!"
# A single [[demon]]: "Something evil is emerging from this newly exposed pocket!" '''or''' "Some ancient horror was encased here, until now!"
# A single [[angel]]: "We have unleashed the echo of a forgotten divine retribution!" '''or''' "Apocalypse! We are being judged by the gods!" If you dig out both of these at the same time, they will fight each other.

== Names ==

Upon first discovery, the place is referred to as an ''eerie cavern''. Nearly all other references in the game, including dialogues and descriptions, call it ''Underworld'' or ''underworld''.

'''Hell''' is a popular alternative name among DF players due to its hellish overtones, but it is rarely referred to as such in-game. ''Hell'' is included in the game's [[language]]s, and generated names for people, sites, regions, etc., can contain the word ''hell''. When the Underworld and its contents are spoken of in the context of spoilers, players frequently use the term "'''Hidden Fun Stuff'''" ('''HFS''') or the "'''circus'''" (with demons nicknamed "clowns").

==World generation==

In world generation, two kinds of gates to the underworld can be created: [[deity|deties]] may thrust [[underworld spire]]s as part of their ritual to bring unique demons into the world, and [[goblin]] civilizations will be built around those; or dwarven sites may dig too deep, inadvertently breaching into the underworld, with new civilizations created to rule from those sites, with both goblin and non-unique demon citizens. Only the first kind leads to an actual physical passage into the underworld, and every such initial goblin civilization will contain one, while only the second kind will make that underworld region known in legends mode.

== Reaching the Underworld ==
===Fortress mode===

[[File:Underworld.png|thumb|right|390px|Not the best vacationing spot.]]
Upon digging sufficiently deep (usually z-level ~160, but it can vary wildly) you will find [[Magma sea|huge magma lakes]]. These are surrounded by [[semi-molten rock]] which cannot be cleared by digging, but seems otherwise stable. Eventually, you will reach a layer which contains nothing but molten rock and little to no possibilities to pass. You can reach the critical layer by digging through solid rock which gets rarer the deeper you dig. In fortress mode, there are two ways through the impassable layer:

'''Digging through an adamantine vein:''' [[Raw adamantine]] veins are shaped like vertical tubes and breach through any layer of semi-molten rock, right down into the Underworld. The lower layers of the vein are often hollow and act as a tube, leading straight to your doom. Breaching into the hollow center of a vein has the same effect as breaching into the Underworld, so beware. You could easily dig around the hollow core provided you knew where it was, but every vein's hollow center is located at a different height - the risk is all part of the [[fun]]. Adamantine veins always seem to end in mid-air, so once you breach the final layer, you will face a horde of demons which hovers directly below your feet.

'''Channeling through semi molten rock:''' It is possible to channel into semi-molten rock (and, to a lesser extent, slade) from above, as long as the tile below is not yet discovered. In older versions, you had to remove the magma-flow and ramps in a complicated procedure that killed one dwarf per level, but now it is possible to channel directly into the underworld without losing a dwarf, though the miner tapping it will likely get killed by demons or drop into an eerie glowing pit. The difference is that, in older versions, the miner was placed onto the magma flow, but now they are placed under the magma flow, and can channel on.

* Start one or more levels above the lowest rock layer above the magma flow. (this is important, as the miner must fall below the magma flow)
* designate channels (d-h) from here down to the bottom of the map.
* The miner will first generate a downward ramp into the rock. Now build a hatch above this ramp.
* The miner walks down this ramp, and channels into the semi-molten rock, as the game only sees the granite upward slope.
* Now, the miner is trapped below a magma flow (floor) and surrounded by semi molten rock. They will proceed to channel down until they reach the underworld, leaving magma flow tiles above them, as well as channel one level into slade. (if they survive long enough)
* You now have a chute - blocked by magma flow floors - into the underworld. By constructing up/down stairways, you can build a stairway into the underworld (the magma flow is removed in that process).
* If the site has no adamantine (otherwise you probably wouldn't do that), no demons will be generated (except the "wildlife"-demons), and you might even be able to save the miner, if you build the stairway before he starves to death.
* As both magma-free pillars and eerie glowing pits are placed in the corners of embark tiles, the miner will likely fall into an eerie glowing pit - use zones ({{K|i}}) to find solid slade floor and prevent this from happening.

[[File:eerie_cavern.png|thumb|405px|Announcement upon revealing the Underworld]]

Regardless of the method of breaching, you will receive an announcement upon piercing the Underworld. One step later, you will get a second announcement: '''''"Horrifying screams come from the darkness below!"''''' At this point, a ''massive'' number of demons will be spawned - though the number is not fixed, the demons will likely fill many pages on the Units screen. You'd do well to prepare for the worst.

===Adventure mode===

In adventure mode, one may find huge slade [[underworld spire]]s built as gateways to the Underworld. Only the sites that a unique demon rose up from will have an opening into the Underworld. The lowermost levels of these structures indeed lead directly into the Underworld, with several demons waiting below. Due to the underworld spire more or less having to reach the very bottom of the world, the player almost always has to go down at least over a hundred z-levels. Combined with the FPS drop that comes with being near a goblin civilization due to all the activity, it may take a while.

Alternatively, adventurers may enter through player made fortresses that have opened a way into the Underworld. Generated Dwarven sites do not enter the Underworld, even if they have allegedly breached into an eerie cavern during world generation, and will terminate at the top of the magma sea.

Be warned that demons make for highly dangerous opponents for an adventurer: they are big, fast, strong, don't feel pain, don't get stunned or exhausted, and unless you get lucky and one is generated as being composed of something like salt, they frequently can take quite a bit of punishment, especially if they're made of a metal. Finally, like Titans/Forgotten Beasts demons possess a procedurally generated special attack that may or may not easily ruin your day.

==== Starting Adventure mode in the Underworld ====
First, you need to build a [[camp]] and [[claim]] it for yourself. This will turn you into a lord, and make the camp into a proper site to which you will be able to recruit and assign [[hearthpeople]] to.

Then, if you make a zone inside your camp several levels down, assign hearthpeople to that zone, and retire and unretire them, you may very well end up starting the game in the Underworld. In fact, any adventurer with a background of being a hearthperson to that site may start in the Underworld as well.

== Invading the Underworld ==
Assuming you survive the initial onslaught, you may then proceed to explore the newly discovered land. The most impressive example of this feat is recorded by Sethatos in [http://www.bay12forums.com/smf/index.php?topic=156319.msg6814181#msg6814181 Archcrystal]. Dwarves of the highest skill are recommended.

Note that the Underworld is completely devoid of useful resources, as most demons are sentient and cannot be [[butcher]]ed, there are no [[plant]]s, [[water]], [[soil]] or [[ore]]s, and the unique [[slade]] rock the Underworld is made out of cannot be mined. The only reason one would have to invade the Underworld is pure bragging rights.

{{D for Dwarf}}

== After Settling In ==
For training purposes, the Underworld is a perfect place for a Dwarven Boot Camp. Even if a soldier dies in the battle for hell, you can track down their sorry dwarven butts, and drag them out of the eerie glowing pit... And right back to boot camp! Side effects of Underworld Boot Camp include: Mental trauma; repeated cases of death; losing the will to live; [[fun]].

{{Translation
| dwarven = Arôloram
| elvish = Tariteyo
| goblin = Sumspabuzong
| human = Ngironra
}}

{{World}}
[[Category:Spoilers]]
{{Category|HFS}}

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

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]]