Dwarf Fortress Wiki - User contributions [en]

v0.34:Egg production

2012-05-23T00:21:12Z

Shmo: /* Egg-laying Animals */

{{quality|Exceptional|01:15, 16 April 2011 (UTC)}}{{av}}

'''Producing eggs''', like the [[meat industry]], the [[beekeeping industry]], the [[fishing industry]] and [[farming]], creates [[food]]. In egg production, collection and cooking of [[egg]]s is the primary activity, as, over time, domestic poultry such as [[chicken]]s can produce much more food as eggs than the same animal produces as meat when butchered (1 egg = 1 meal). When starting out a new fortress, raising poultry can be an excellent way to quickly fill up your food [[barrel]]s as it requires very little set-up for your dwarves. As a by-product of egg production, older or excess animals can be butchered as part of the [[meat industry]].

== Acquiring Egg-laying Animals ==
There are several sources for obtaining egg-laying [[animal]]s, outlined below.

===Embark===
You can buy [[Domestic_animal#Comparison_of_domestic_poultry|domestic poultry]] at [[embark]] and even decide how many males and females of each animal you embark with. Since you don't need males to produce eggs, and need only one male to breed, you could embark with three or four hens, and at most one rooster. Poultry animals are very economical to purchase at embark, costing only 6[[currency|☼]] each.

Of the domestic poultry, [[turkey]]s produce the most eggs per clutch on average, followed by [[duck]]s, then [[chicken]]s and [[guineafowl]]. Turkeys are the largest animals, and produce the most meat and other products if butchered as part of the meat industry, with [[goose|geese]] and [[blue peafowl]] only slightly smaller. All domestic poultry become adults one year after hatching, but geese, blue peafowl, and guineafowl grow to full size at one year; other poultry only reach full size after two years.

===Migration===
Immature domestic poultry may arrive at your fortress with a wave of [[migrant]]s. These animals may be strays or [[pet]]s.

===Trading===
''Requires: A [[trade depot]], a [[Broker|trader]], a [[merchant]], and some tradeable goods''

You can purchase egg-laying animals from a merchant. Elves may bring tamed exotic animals which are additionally [[giant eagle|interesting for defense purposes]].

===Cage traps===
''Requires: [[Cage]]s, [[mechanism]]s, a [[mechanic]], a [[kennel]], and a [[animal trainer]]''

It is also possible to catch egg-laying animals through judicious use of [[cage trap]]s. This, of course, involves building cage traps where animals will walk or fly. Once they are trapped the caged animal (or [[invader]]) will be delivered to an animal stockpile and the trap will be reset with a fresh cage.

Cage traps should be built where animals ''will'' walk, not where they are when you decide to trap them. Any dwarves sent out to create and arm traps in the animals' midst will scare them away or trigger their aggression. To successfully trap large animals, form a choke point some distance away from them: build walls, perhaps several z-levels high, to create a continuous barrier to movement.

Leave a small gap one or two tiles wide (depending on how many of the critters you want to trap) and build your cage traps there. If the animals haven't moved off or been scared off by the time you're done, and they're docile enough to not attack once they see your dwarves, use military orders to send a dwarf (or several) around behind the animals and herd them toward the choke point.

Note also that cage traps cannot be built within a certain number of tiles of the map edge, so when planning your funnels and choke points, be sure to leave four or five tiles as a buffer zone.

Egg-laying animals that are caught in a cage trap need to be tamed by an [[animal trainer]] at a [[kennel]] before they can be safely used to produce eggs.

===Breeding===
''Requires: One or more adult females and one adult male of each species, one or more [[nest box]]es, and time''

If a male and a female of the same species exist on your map, and there is an open constructed [[nest box]] for the female to occupy and lay a clutch of eggs in, then sooner or later (and probably sooner) the male will fertilize the eggs laid by the female. No contact between the male and the female or eggs is needed - fertilization can ''and will'' occur regardless of distance, physical obstacles such as walls or locked doors, number of each gender (beyond the first), and even ownership. ''(This is often referred to as "breeding by spores".)'' Even a male in a flock of wild animals outside the fortress walls can fertilize a clutch locked deep in a lowest level. A female can lay a clutch of eggs again immediately after the last clutch hatches. A female that can not claim a nest box ''will not'' lay a clutch of eggs.

A fertilized clutch will only hatch if they are left in the nest box undisturbed and their mother is allowed to incubate the eggs. Collecting the eggs, [[butcher's shop|slaughtering]] the mother, or deconstructing the nest box will all prevent the eggs from hatching. A clutch of eggs to be used for breeding should be [[forbidden]] to prevent their collection. Even if the eggs and mother are left undisturbed, it is possible that clutch was not fertilized. Eggs that don't hatch after two seasons will likely never hatch. To make sure that the eggs are left undisturbed, make sure that no [[stockpile]]s accept that type of egg, and if you [[cooking|cook]] any meals make sure that that type of egg is turned off in the kitchen sub-screen of the [[status]] screen. Alternatively, you can put the nest boxes in a room behind a [[door]] and forbid the door to keep your dwarves away from the eggs.

As a large number of free-roaming animals will reduce your game speed, a common strategy is to cage all your young poultry until matured because they cannot lay eggs, and do not give the same amount of bones, meat, and fat as adults. Keep in mind, though, that some tamed wild species take more than 1 year to mature, unlike most domestic animals. For example, it may be excusable to butcher a [[saltwater crocodile]] hatchling right away, rather than wait 3 years for it to mature and produce more meat and bones.

Using [[cage trap]]s judiciously (or taking advantage of the animals [[elf|elves]] trade) can sometimes snag you a breeding pair of a wild animal. Tame something unusual and start something crazy, like a [[cave crocodile]] farm!

==Egg Collection==
''Requires: A tame adult female egg-laying animal, a [[nest box]], and [[food hauling]]''

Once you have at least one tame adult female egg-laying animal, you need to build a [[nest box]] to begin production of delicious and filling [[egg]]s. Every so often, the adult females will claim a nest box and lay a clutch of eggs. Then, a [[food hauling|food hauler]] will collect the eggs and move them to a food [[stockpile]]. As food hauling is an unskilled labor, any dwarf in the fortress can be as good at egg collection as every other dwarf! Egg collection is a great way to use those [[peasant]]s that otherwise just move boulders around the fortress.

As of v0.31.21, it seems that eggs must be [[cook]]ed into [[prepared meal]]s at a [[kitchen]] before they can be eaten by dwarves.

==Egg-laying Animals==
''This table is incomplete (2012-05-22). You can help by adding to it.''
{| border="1px #AAA solid;" style="text-align:center;" class="wikitable sortable"
|+style="border:1px #AAA solid;background:#EEE;"| '''Outdoor Animals'''
|-
!style="border:1px #AAA solid;background:#DDD;"| Animal
!style="border:1px #AAA solid;background:#DDD;"| Minimum Number of Eggs
!style="border:1px #AAA solid;background:#DDD;"| Maximum Number of Eggs
!style="border:1px #AAA solid;background:#DDD;"| Egg Size
|-
|style="padding:0.2em;"|[[Adder]]
|style="padding:0.2em;"|3
|style="padding:0.2em;"|10
|style="padding:0.2em;"|16
|-
|style="padding:0.2em;"|[[Albatross]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|1
|style="padding:0.2em;"|305
|-
|style="padding:0.2em;"|[[Alligator]]
|style="padding:0.2em;"|10
|style="padding:0.2em;"|30
|style="padding:0.2em;"|80
|-
|style="padding:0.2em;"|[[Alligator snapping turtle]]
|style="padding:0.2em;"|5
|style="padding:0.2em;"|10
|style="padding:0.2em;"|70
|-
|style="padding:0.2em;"|[[Barn owl]]
|style="padding:0.2em;"|3
|style="padding:0.2em;"|6
|style="padding:0.2em;"|32
|-
|style="padding:0.2em;"|[[Beak dog]]
|style="padding:0.2em;"|5
|style="padding:0.2em;"|10
|style="padding:0.2em;"|1600
|-
|style="padding:0.2em;"|[[Black mamba]]
|style="padding:0.2em;"|10
|style="padding:0.2em;"|30
|style="padding:0.2em;"|50
|-
|style="padding:0.2em;"|[[Blue peafowl]]†
|style="padding:0.2em;"|6
|style="padding:0.2em;"|8
|style="padding:0.2em;"|102
|-
|style="padding:0.2em;"|[[Bushmaster]]
|style="padding:0.2em;"|10
|style="padding:0.2em;"|20
|style="padding:0.2em;"|22
|-
|style="padding:0.2em;"|[[Buzzard]]
|style="padding:0.2em;"|2
|style="padding:0.2em;"|3
|style="padding:0.2em;"|60
|-
|style="padding:0.2em;"|[[Cassowary]]
|style="padding:0.2em;"|3
|style="padding:0.2em;"|6
|style="padding:0.2em;"|550
|-
|style="padding:0.2em;"|[[Chicken]]†
|style="padding:0.2em;"|4
|style="padding:0.2em;"|15
|style="padding:0.2em;"|62
|-
|style="padding:0.2em;"|[[Common snapping turtle]]
|style="padding:0.2em;"|5
|style="padding:0.2em;"|10
|style="padding:0.2em;"|50
|-
|style="padding:0.2em;"|[[Crow]]
|style="padding:0.2em;"|4
|style="padding:0.2em;"|6
|style="padding:0.2em;"|21
|-
|style="padding:0.2em;"|[[Desert tortoise]]
|style="padding:0.2em;"|3
|style="padding:0.2em;"|5
|style="padding:0.2em;"|40
|-
|style="padding:0.2em;"|[[Duck]]†
|style="padding:0.2em;"|8
|style="padding:0.2em;"|13
|style="padding:0.2em;"|52
|-
|style="padding:0.2em;"|[[Eagle]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|3
|style="padding:0.2em;"|142
|-
|style="padding:0.2em;"|[[Echidna]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|1
|style="padding:0.2em;"|1
|-
|style="padding:0.2em;"|[[Emperor penguin]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|1
|style="padding:0.2em;"|465
|-
|style="padding:0.2em;"|[[Emu]]
|style="padding:0.2em;"|5
|style="padding:0.2em;"|15
|style="padding:0.2em;"|805
|-
|style="padding:0.2em;"|[[Giant eagle]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|3
|style="padding:0.2em;"|2100
|-
|style="padding:0.2em;"|[[Giant tortoise]]
|style="padding:0.2em;"|5
|style="padding:0.2em;"|10
|style="padding:0.2em;"|82
|-
|style="padding:0.2em;"|[[Gila monster]]
|style="padding:0.2em;"|2
|style="padding:0.2em;"|12
|style="padding:0.2em;"|32
|-
|style="padding:0.2em;"|[[Goose]]†
|style="padding:0.2em;"|3
|style="padding:0.2em;"|8
|style="padding:0.2em;"|152
|-
|style="padding:0.2em;"|[[Grey parrot]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|5
|style="padding:0.2em;"|40
|-
|style="padding:0.2em;"|[[Great horned owl]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|5
|style="padding:0.2em;"|51
|-
|style="padding:0.2em;"|[[Guineafowl]]†
|style="padding:0.2em;"|4
|style="padding:0.2em;"|15
|style="padding:0.2em;"|42
|-
|style="padding:0.2em;"|[[Hornbill]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|4
|style="padding:0.2em;"|50
|-
|style="padding:0.2em;"|[[Kakapo]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|4
|style="padding:0.2em;"|52
|-
|style="padding:0.2em;"|[[Kea]]
|style="padding:0.2em;"|2
|style="padding:0.2em;"|5
|style="padding:0.2em;"|62
|-
|style="padding:0.2em;"|[[Kestrel]]
|style="padding:0.2em;"|3
|style="padding:0.2em;"|6
|style="padding:0.2em;"|32
|-
|style="padding:0.2em;"|[[King cobra]]
|style="padding:0.2em;"|10
|style="padding:0.2em;"|30
|style="padding:0.2em;"|5
|-
|style="padding:0.2em;"|[[Kingsnake]]
|style="padding:0.2em;"|5
|style="padding:0.2em;"|12
|style="padding:0.2em;"|20
|-
|style="padding:0.2em;"|[[Little penguin]]
|style="padding:0.2em;"|2
|style="padding:0.2em;"|2
|style="padding:0.2em;"|53
|-
|style="padding:0.2em;"|[[Loon]]
|style="padding:0.2em;"|2
|style="padding:0.2em;"|4
|style="padding:0.2em;"|152
|-
|style="padding:0.2em;"|[[Monitor lizard]]
|style="padding:0.2em;"|15
|style="padding:0.2em;"|25
|style="padding:0.2em;"|70
|-
|style="padding:0.2em;"|[[Osprey]]
|style="padding:0.2em;"|2
|style="padding:0.2em;"|4
|style="padding:0.2em;"|60
|-
|style="padding:0.2em;"|[[Penguin]]
|style="padding:0.2em;"|2
|style="padding:0.2em;"|2
|style="padding:0.2em;"|125
|-
|style="padding:0.2em;"|[[Peregrine falcon]]
|style="padding:0.2em;"|3
|style="padding:0.2em;"|4
|style="padding:0.2em;"|46
|-
|style="padding:0.2em;"|[[Platypus]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|3
|style="padding:0.2em;"|11
|-
|style="padding:0.2em;"|[[Puffin]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|1
|style="padding:0.2em;"|30
|-
|style="padding:0.2em;"|[[Python]]
|style="padding:0.2em;"|10
|style="padding:0.2em;"|30
|style="padding:0.2em;"|50
|-
|style="padding:0.2em;"|[[Raven]]
|style="padding:0.2em;"|3
|style="padding:0.2em;"|7
|style="padding:0.2em;"|52
|-
|style="padding:0.2em;"|[[Saltwater crocodile]]
|style="padding:0.2em;"|20
|style="padding:0.2em;"|70
|style="padding:0.2em;"|100
|-
|style="padding:0.2em;"|[[Sea_serpent|Sea serpent]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|1
|style="padding:0.2em;"|6100
|-
|style="padding:0.2em;"|[[Snowy owl]]
|style="padding:0.2em;"|5
|style="padding:0.2em;"|10
|style="padding:0.2em;"|62
|-
|style="padding:0.2em;"|[[Swan]]
|style="padding:0.2em;"|5
|style="padding:0.2em;"|7
|style="padding:0.2em;"|340
|-
|style="padding:0.2em;"|[[Turkey]]†
|style="padding:0.2em;"|10
|style="padding:0.2em;"|14
|style="padding:0.2em;"|87
|-
|style="padding:0.2em;"|[[Vulture]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|3
|style="padding:0.2em;"|60
|-
|style="padding:0.2em;"|[[White stork]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|7
|style="padding:0.2em;"|110
|}
:† Common [[domestic animal]], can be purchased at embark

{| border="1px #AAA solid;" style="text-align:center;" class="wikitable sortable"
|+style="border:1px #AAA solid;background:#EEE;"| '''Subterranean Animals'''
|-
!style="border:1px #AAA solid;background:#DDD;"| Animal
!style="border:1px #AAA solid;background:#DDD;"| Minimum Number of Eggs
!style="border:1px #AAA solid;background:#DDD;"| Maximum Number of Eggs
!style="border:1px #AAA solid;background:#DDD;"| Egg Size
|-
|style="padding:0.2em;"|[[Cave crocodile]]
|style="padding:0.2em;"|20
|style="padding:0.2em;"|60
|style="padding:0.2em;"|80
|-
|style="padding:0.2em;"|[[Cave dragon]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|3
|style="padding:0.2em;"|6100
|-
|style="padding:0.2em;"|[[Crundle]]
|style="padding:0.2em;"|5
|style="padding:0.2em;"|20
|style="padding:0.2em;"|60
|-
|style="padding:0.2em;"|[[Elk bird]]
|style="padding:0.2em;"|2
|style="padding:0.2em;"|10
|style="padding:0.2em;"|60
|-
|style="padding:0.2em;"|[[Giant cave swallow]]
|style="padding:0.2em;"|2
|style="padding:0.2em;"|3
|style="padding:0.2em;"|2100
|-
|style="padding:0.2em;"|[[Helmet snake]]
|style="padding:0.2em;"|10
|style="padding:0.2em;"|30
|style="padding:0.2em;"|50
|-
|style="padding:0.2em;"|[[Jabberer]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|2
|style="padding:0.2em;"|5100
|}

{| border="1px #AAA solid;" style="text-align:center;" class="wikitable sortable"
|+style="border:1px #AAA solid;background:#EEE;"| '''[[:Megabeast|Megabeasts]]'''
|-
!style="border:1px #AAA solid;background:#DDD;"| Animal
!style="border:1px #AAA solid;background:#DDD;"| Minimum Number of Eggs
!style="border:1px #AAA solid;background:#DDD;"| Maximum Number of Eggs
!style="border:1px #AAA solid;background:#DDD;"| Egg Size
|-
|style="padding:0.2em;"|[[Dragon]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|3
|style="padding:0.2em;"|6100
|-
|style="padding:0.2em;"|[[Roc]]
|style="padding:0.2em;"|1
|style="padding:0.2em;"|2
|style="padding:0.2em;"|201000
|}

==Bugs==
It appears that aquatic egg laying animals will not claim a nest box. It doesn't matter if the box is built underwater or on land. http://www.bay12forums.com/smf/index.php?topic=75780.105
{{Category|Food}}
{{Category|Guides}}
{{Category|Industry}}

v0.34:Black bronze

2012-05-07T05:35:52Z

Shmo: Rated article "Exceptional" using the rating script

{{quality|Exceptional|05:35, 7 May 2012 (UTC)}}{{Alloy3|name=Black Bronze|color=5:6:0|color1=6:4:0|color2=7:7:1|color3=6:6:1
|uses=
* [[Metal crafter|Metal crafting]]
|recipe=
* 2 [[Copper]] [[bar]]s
* 1 [[Silver]] [[bar]]
* 1 [[Gold]] [[bar]]
|properties=
* [[Material value]] 11
|wiki=Hepatizon
}}{{av}}

'''Black bronze''' is a semiprecious alloy of [[copper]], [[gold]] and [[silver]]. Unlike [[bronze|regular]] or [[bismuth bronze]], black bronze cannot be used to create [[weapon]]s or [[armor]], restricting its uses to [[Blacksmith|blacksmithing]] and [[Metal crafter|metalcrafting]] purposes. Black bronze cannot be [[Smelter|smelt]]ed directly from [[ore]] but only from [[bar]]s of pure [[metal]]s. Unlike some [[alloy]]s, the [[Item value|value]] of a bar of black bronze is equal exactly to the average value of its components - creating this alloy does not increase the total value of the material (2 [[copper]] bars at 2☼ each + 1 [[silver]] bar at 10☼ + 1 [[gold]] bar at 30☼ = 44☼/4 bars = 11☼/bar of black bronze).

Black bronze creations do not count toward [[bronze]] item mandates.

{{gamedata}}
{{metals}}

v0.34:Black bronze

2012-05-07T05:35:02Z

Shmo: minor rewording; added lead sentence

{{Alloy3|name=Black Bronze|color=5:6:0|color1=6:4:0|color2=7:7:1|color3=6:6:1
|uses=
* [[Metal crafter|Metal crafting]]
|recipe=
* 2 [[Copper]] [[bar]]s
* 1 [[Silver]] [[bar]]
* 1 [[Gold]] [[bar]]
|properties=
* [[Material value]] 11
|wiki=Hepatizon
}}{{av}}{{Quality|Fine|11:04, 19 July 2010 (UTC)}}

'''Black bronze''' is a semiprecious alloy of [[copper]], [[gold]] and [[silver]]. Unlike [[bronze|regular]] or [[bismuth bronze]], black bronze cannot be used to create [[weapon]]s or [[armor]], restricting its uses to [[Blacksmith|blacksmithing]] and [[Metal crafter|metalcrafting]] purposes. Black bronze cannot be [[Smelter|smelt]]ed directly from [[ore]] but only from [[bar]]s of pure [[metal]]s. Unlike some [[alloy]]s, the [[Item value|value]] of a bar of black bronze is equal exactly to the average value of its components - creating this alloy does not increase the total value of the material (2 [[copper]] bars at 2☼ each + 1 [[silver]] bar at 10☼ + 1 [[gold]] bar at 30☼ = 44☼/4 bars = 11☼/bar of black bronze).

Black bronze creations do not count toward [[bronze]] item mandates.

{{gamedata}}
{{metals}}

v0.34:Underworld

2012-05-07T05:24:29Z

Shmo: /* Hell itself */

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

==Reaching Hell==
Upon digging sufficiently deep (usually z-level ~160, but it can vary wildly) you will find huge magma lakes. These are surrounded by semi molten rock, which can not 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. There are three ways through the impassible layer:

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

'''Entering a demonic fortress:''' These fortresses are found once per map tile, as frequent as the old [[40d:Eerie glowing pit|eerie glowing pits]]. They also go right through to Hell, however they are defended by undead creatures and demons on the lower levels. [[Demonic fortress|See the full page for more details]].

'''Tunnelling through semi molten rock:''' A new method has been discovered that allows your dwarfs to engineer a convoluted system involving controlled cavern collapsing and exploiting the odd behavior of a [[semi-molten rock|magma flow]] tile. Not only does it allow access to Hell, you can further exploit the Magma Flow tile to dig through Eerie Pits, duplicate any type of stone (including raw adamantine) and [[Slade|mine slade]]. The whole thing is documented and explained in this [http://www.bay12forums.com/smf/index.php?topic=108189.0 Forum Thread].

==Hell itself==

[[File:eerie_cavern.png]]

You will receive the above announcement upon piercing Hell. One frame later, you will get a second announcement: "Horrifying screams come from the darkness below!" At this point a massive number of [[demon]]s 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. If there are multiple adamantine pillars present on the map, only one will trigger the invasion when breached. Thus, it's possible to descend into Hell 'safely' if you guess a right pillar.

Hell takes the shape of a large open cavern made of [[slade]]. It expands out in all directions without bound with a height varying between 1 and 4 z. Its rough floor slopes up and down, making it possible to walk around and explore should you get an adventurer down there. In the floor are glowing cracks that shine purple light up into the main cavern of Hell - whence comes this light, mortal minds dare not speculate.

In Hell proper, demons spawn on the edges much like animals do on the surface; demons thus spawned will be content to meander Hell without going out of their way to extinguish all life they can reach. 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 ants, worms, and other omnipresent vermin.

v0.34:Underworld

2012-05-07T05:22:32Z

Shmo: rewrite to improve organization and clarity

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

==Reaching Hell==
Upon digging sufficiently deep (usually z-level ~160, but it can vary wildly) you will find huge magma lakes. These are surrounded by semi molten rock, which can not 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. There are three ways through the impassible layer:

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

'''Entering a demonic fortress:''' These fortresses are found once per map tile, as frequent as the old [[40d:Eerie glowing pit|eerie glowing pits]]. They also go right through to Hell, however they are defended by undead creatures and demons on the lower levels. [[Demonic fortress|See the full page for more details]].

'''Tunnelling through semi molten rock:''' A new method has been discovered that allows your dwarfs to engineer a convoluted system involving controlled cavern collapsing and exploiting the odd behavior of a [[semi-molten rock|magma flow]] tile. Not only does it allow access to Hell, you can further exploit the Magma Flow tile to dig through Eerie Pits, duplicate any type of stone (including raw adamantine) and [[Slade|mine slade]]. The whole thing is documented and explained in this [http://www.bay12forums.com/smf/index.php?topic=108189.0 Forum Thread].

==Hell itself==

[[File:eerie_cavern.png]]

You will receive the above announcement upon piercing Hell. One frame later, you will get a second announcement: "Horrifying screams come from the darkness below!" At this point a massive number of [[demon]]s 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. If there are multiple adamantine pillars present on the map, only one will trigger the invasion when breached. Thus, it's possible to descend into Hell 'safely' if you guess a right pillar.

Hell takes the shape of a large open cavern made of [[slade]]. It is seemingly infinitely wide and, generally varies between 1 and 4 z high. Its rough floor slopes up and down, making it possible to walk around and explore should you get an adventurer down there. In the floor are glowing cracks that shine purple light up into the main cavern of Hell - whence comes this light, mortal minds dare not speculate.

In Hell proper, demons spawn on the edges much like animals do on the surface; demons thus spawned will be content to meander Hell without going out of their way to extinguish all life they can reach. 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 ants, worms, and other omnipresent vermin.

v0.34:Claro opal

2012-04-12T01:46:36Z

Shmo: Restating the infobox to spare this article the indecency of having no body

{{quality|Fine|20:13, 26 December 2010 (UTC)}}{{gemlookup/0}}{{av}}
'''Claro opals''' are moderately valuable gems found in clusters in all stone layers.
{{gamedata}}
{{gems}}

v0.31:Advanced world generation

2011-12-25T06:19:11Z

Shmo: orthographic incorrectly used in place of orographic

{{quality|Exceptional|23:35, 30 March 2011 (UTC)}}{{av}}
{{buggy}}

:''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.''
:''See [[World rejection]] for information on solving problems related to worlds always being rejected.''
:''See [[Worldgen examples]] for example worlds.''

When you want more control of what your world looks like, it's time for '''advanced world generation'''. A detailed reference with advice is provided below. This article assumes that you are already familiar with [[World generation|'''basic''' world generation]]. If you are not then please read about that first.

= Advanced World Generation Screen =

Once you select {{DFtext|Design New World With Advanced Parameters}} from the main menu, a screen that looks something like this will appear:

[[File:AdvancedWorldGen.png‎]]

This screen is relatively intuitive but some parts could use some explanation.

== Parameter Sets ==

The list of already defined parameter sets is in the upper right corner. You can select the current set that you want to work with using the up and down directional keys.

Hitting {{K|a}} will add a new set to the end of the list. You can also {{K|c}}opy an existing set to a new one allowing you to base a new set on an existing one. Using {{K|t}} you can change the name of the parameter set but note that this will not affect the name of the world that is generated.

Parameter sets are stored in the <tt>data/init/world_gen.txt</tt> file in the main DF directory. The {{K|F1}} and {{K|F6}} keys will load and save '''all''' of the parameter sets to this file. You will need to save the world gen parameters to this file before you hit {{K|Enter}} to generate the world.

The <tt>world_gen.txt</tt> file can also be edited with a text editor. This is particularly useful because people will often post their parameter sets on the forum or wiki in text form. (See below for more info.) The {{K|F1}} key comes in handy when editing this file while the game is still running.

The tokens used in <tt>world_gen.txt</tt> are at the bottom of each parameter description. Here's the one for title.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITLE: <name>]</nowiki></tt>
| <tt><nowiki>[TITLE:MEDIUM ISLAND]</nowiki></tt>
| Required
|}

== World Name ==

As previously mentioned, the title of the parameter set doesn't affect the name of the world. You can force a particular name for your world using {{K|n}} or set it back to the default random setting using {{K|N}}.

{| {{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.
|}

== World Dimensions ==

The size of the map to be generated can be selected with {{K|u}} {{K|i}} {{K|o}} {{K|p}}. Larger maps take longer to generate and may limit [[Frames per second|FPS]] in game.

Changing the dimensions of the world will reset the parameters because many of them have different defaults depending on the surface area available.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DIM:<width>:<height>]</nowiki></tt>
| <tt><nowiki>[DIM:129:129]</nowiki></tt>
| Valid values are 17,33,65,129, and 257. Others may not work.
|}

== Seed Values ==

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 word 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.

A specific seed value can be entered with {{K|s}}. This will change '''all''' of the seed values to the value you enter. If you need to enter different seed values for each type of seed, use {{K|e}}.

In order to find out what seed values were used for the last world you generated you can look at this screen. If you want to be able to tell someone else how to generate exactly the same world that you just generated, they will need all of the seed value listed under Last Param Set.

Normally you don't enter these seed values and the world generation process comes up with seed values based on some sort of "true" random information from things like random values in uninitialized memory, the current date/time, etc. If you have entered a seed value you can revert back to all seeds being random using {{K|S}}.

== Entering Advanced Parameters and Generating a World ==

Unless you're using an already defined parameter set you will probably want to {{K|e}}dit the parameters. Select the set you want to edit using the up/down directional keys and press {{K|e}}. Information about each parameter is documented below.

Once you are happy with the parameters you have set, hit {{K|Esc}} to get back to this screen, hit {{K|F6}} to save the values you just edited, and hit {{K|Enter}} to start. The rest of the process is the same as basic [[World generation]].

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

== World Painter ==
:''Main article [[World painter]]
The '''world painter''' tool allows you to paint features onto a map that is then used when generating a world. It is very difficult to use properly, and tends to result in endless rejected worlds, unless you loosen or remove the restrictions placed on biomes and civilizations in the advanced settings. That being said it is also a very powerful tool, and allows you to generate worlds more to your liking.

To access the world painter, hit {{k|e}} to start editing the advanced parameters and finally hit {{k|p}} to open world painter. How to use the world painter is not entirely obvious so please check out the [[World painter]] documentation to avoid frustration. (Losing may be fun, but frustration is not.)

== Editing the Parameters Init File Directly ==

Parameter sets are stored in ''world_gen.txt'' in the ''\data\init'' folder, using [[world token]]. You can copy and paste other player's sets of parameters into your ''world_gen.txt'' to use their parameter sets, and some are provided at [[Main:Pregenerated worlds|Pregenerated worlds]]. Another place to find parameter sets is the [http://www.bay12games.com/forum/index.php?topic=20638.0 Worldgen cookbook] thread on the official forums.

= Advanced Parameters =

To access advanced parameters, press {{key|e}} when at the screen for creating new worlds with parameters screen. This will bring you to an editable list of various guidelines the world-gen process will use when creating your new world.

The parameters are described below in the order that they appear in the list in the UI, not necessarily the other they appear in the configuration file. See [[world token]] for an index that will help you look things up by token name.

== Seed Values ==

Here you can enter specific seed values for different parts of the world generation process. Different sequences of pseudorandom numbers are used for different parts, so you can use this to reproduce only the particular part of world generation from some previously generated world if you want.

Normally you will want to leave all of these set to Random unless you're specifically trying to reproduce the results of another world generation run.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEED:<number>]</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.
|-
| <tt><nowiki>[HISTORY_SEED:<number>]</nowiki></tt>
| <tt><nowiki>[HISTORY_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[NAME_SEED:<number>]</nowiki></tt>
| <tt><nowiki>[NAME_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[CREATURE_SEED:<number>]</nowiki></tt>
| <tt><nowiki>[CREATURE_SEED:31337]</nowiki></tt>
|}

== Embark Points ==

This controls the number of points that you have for skills and equipment when you embark in fortress mode. Turning this value up will allow games started in this world to start with more skilled dwarves with better equipment. Normally you can do just fine by leaving this value set to default, but you might want to up it for experimental/testing purposes or to help dwarves survive in a particularly evil world.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EMBARK_POINTS:<number>]</nowiki></tt>
| <tt><nowiki>[EMBARK_POINTS:1274]</nowiki></tt>
| Required
|}

== End Year ==

This is how many years of history are generated for the world. This is basically the same as the History parameter in basic world gen, except that you can enter an exact value for number of years. See [[World_generation#History|History]] for more info.

History is divided into "ages" which are determined by the ''percentage'' of megabeasts and semi-megabeasts killed at various points. One can attempt to make a world go through the ages more quickly by pumping up the ratio of semimegabeast to megabeast caves, the former of which are usually more killable than the regular megabeasts. This will net you more "Age of Legends", "Age of Heroes", etc.

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:1050]</nowiki></tt>
| Required
|}

== Population Cap After Civ Creation ==

This determines the maximum possible population of civilization member beings on the map. It should usually be kept the same value as the appropriate sized standard map. Turning the value up will result in larger civilizations. You can enter -1 to make population unlimited in which case populations will only be limited by factors like biome, space, number of sites, and per-civilization population caps.

Each race may have up to 100 civilizations each, and each civilization a maximum population of 10,000. This means that '''if you set this parameter to -1 ("No cap"), you can quickly be overrun''' by sites and population. Civilizations, known as ''entities'' in the [[Raw file|raw files]], have 3 or 4 basic variables that will greatly affect their final placement on the world map, in respect to this kind of unchecked growth. See [[Entity_token#Population|Population (Entity Token)]] for more information on interpreting/editing the raws if you need more precise control of civilization placement.

Huge populations can cause the size of history data to explode, cause history generation to take forever, lower FPS, and generally slow down the game.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_POPULATION:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_POPULATION:15000]</nowiki></tt>
| Required
|}

== Site Cap After Civ Creation ==

This controls the maximum number of towns and similar sites on the entire map. Raising the number will allow for more towns, etc though the number of sites will ultimately still be limited by things like space, terrain, and population cap.

Note that '''this parameter controls only "civilization" sites''' like towns. Other sites such as lairs will be added on to this maximum. After civilizations reach this cap, they will not spread out anymore to place new cities.

By default, the raws limit each civilization site to a population of 120 regardless of the race of the civilization. Therefore, without editing the raws, the total population on the map can't go above site cap x 120.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SITE_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SITE_CAP:1040]</nowiki></tt>
| Required
|}

== Beast Control ==

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

=== Percentage of Beasts Dead for Stoppage ===

The world starts out with a certain number of megabeasts in existence. If this percentage of megabeasts dies during history generation, then history generation will stop early. For example if the value is 80, if history starts with 200 megabeasts and 160 of them are killed by historical events or otherwise die before End Year is reached, history generation will stop early.

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

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

{| {{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 ==

Whether or not the game ignores unimportant figures in history generation. The culling is many CPU-intensive steps in history generation but it saves memory and will speed up loading/saving games a bit. This does mean that the "unimportant" figures will not appear in Legends mode or in things like dwarf engravings, but they might not appear in engravings anyway.

Unimportant figures are people or creatures who suffer early deaths, never having offspring or killing anything named during history generation. For example, residents of goblin towers may get murdered by demons at a young age. After culling unimportant figures, Legends mode would say something like the demon has killed "a creature at Eviltower in the year 102."

{| {{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 all information about the history of the world in Legends mode. 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 determine how random values for terrain elevation, rainfall, temperature, drainage, volcanism, and savagery 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. Changing these can cause the occurrence of certain [[Biome|biomes]] to become impossible, so modify these with care. Because of this problem, you may want to use [[#Weighted Ranges|Weighted Ranges]] instead.

By ''subtly'' tweaking the min and max values, vastly different maps can be made.

=== 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.
* River start locations need a minimum elevation of 300. Therefore, a world with a maximum elevation of 299 everywhere prevents river generation, but rivers can still occur if maximum elevation is set to 300.
*Mountain peaks can only form in squares with an elevation of 400.

=== Rainfall ===

Controls the amount of rainfall in each map square/area. Setting the minimum too high or the maximum too 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 [[DF2010:Advanced world generation#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.

=== 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. See [[Climate]] for more info.

Temperature appears to always be a vertical gradient of some sort no matter how these parameters are set, but if the values are lower then the gradient could be from "cold" to "colder" rather than "cold" to "warm" for example.

So, the value from the temperature rolling process is ''not the absolute temperature value the region will get, but rather local variation.'' The "base" temperature for an area is derived from its latitude (and maybe elevation{{Verify}}), and then the random value determined by these parameters are applied to it to make it vary a bit. The local variation is fairly small compared to the base temperature, which appears to be hard coded.

=== 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|Layers]], 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. Rising the minimum will increase the rarity of non-igneous layers.

Setting minimum to 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 too high of a 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.
|-
| <tt><nowiki>[RAINFALL:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[RAINFALL:0:100:200:200]</nowiki></tt>
| Range: 0 to 100
|-
| <tt><nowiki>[TEMPERATURE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE:25:75:200:200]</nowiki></tt>
| Range: -1000 to 1000
|-
| <tt><nowiki>[DRAINAGE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE:0:100:200:200]</nowiki></tt>
| Range: 0 to 100
|-
| <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.
|-
| <tt><nowiki>[SAVAGERY:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY:1:100:200:200]</nowiki></tt>
| Range: 0 to 100
|}

== Terrain Mesh Sizes and Weights ==

These parameters make it possible to influence the number of squares in a particular range without making conditions outside of that range impossible. For example, you can make it possible for more many more low elevation squares to exist without making it impossible for high elevations to form. Changing these parameters is often preferable to simply changing the min/max values.

[[File:World_map-large-32x32-elevation-mesh.png|thumb|300px|A large world generated with an Elevation Mesh Size of 32x32 and range weights set to 1:0:0:0:1 (i.e., only extreme high and low elevations). Notice that with this coarse mesh, the terrain seems to appear almost like a grid of "pyramids" that are smoothed together. With a finer mesh size, these pyramids will be smaller, more numerous, smoother, and less apparent.]]
=== Mesh Size ===

Mesh size determines how "finely grained" weighted ranges will be applied. Setting this to Ignore will cause the weighted range settings to be ignored for that terrain characteristic.

Mesh Size affects the smoothing brush in the world painter.

=== Weighted Ranges ===

If mesh size is set to something other than Ignore, these weights will be applied at the granularity of the selected mesh size for purposes of generating random values in each range. This allows random number generation to be non-linear for the given terrain characteristic.

For example, if the Elevation Weighted Range parameters were set to (starting with the 0-20 range) 60:10:10:10:10 (these values do not have to add up to any particular number) then about 60% of the map squares (on average) will have an elevation in the range of 0-20, and the other ranges will be represented by around 10% of the map squares each. The exact distribution is still left up to chance though ''on average'' it will be close to this specification.

The way the process appears to work is that the map is divided into a "wireframe mesh" where the lines are Mesh Size number of tiles apart. Each intersection of the "wires" is randomly assigned an elevation (or whatever) and then the tiles between these points are smoothed out. See the image on the right for an example.

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.

=== 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>
|}

== 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. 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.{{Verify}}

{| {{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.

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 and 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 ==

Worlds with less than this number of volcanoes will be rejected. Note that this will not just create this many volcanoes at random; there must be at least this many squares with a Volcanism of 100. Therefore adjusting Weighted Range for 80-100 to some higher value is recommended if you want to facilitate a large number of volcanoes. In addition, Maximum Volcanism must be set to 100 or squares with volcanism of 100 will be impossible making volcanoes impossible.

{| {{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 lower will increase the amount of ore present on a map, the number of different types of ore, and the number/types of gems. The default value will result in a maximum of 2-4 metal ores per map (assuming you choose a good embark location) which may be limiting until the economy is fully implemented and desired metals can be traded for.

According to research by [http://www.bay12forums.com/smf/index.php?action=profile;u=36045 Shandra] on 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. See [http://www.bay12forums.com/smf/index.php?topic=79018.msg2063804#msg2063804 this forum thread] for detailed information on peoples' experiments and possible changes to newer versions.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MINERAL_SCARCITY:<number>]</nowiki></tt>
| <tt><nowiki>[MINERAL_SCARCITY:2500]</nowiki></tt>
| Range: 100 to 100,000
'''setting to lower than 500 may create alot of rejected worlds cause not enough rivers'''(confirmation needed)
|}

== Max Megabeast Caves ==

This is the maximum number of caves that will be inhabited by [[Megabeast|megabeasts]]. Even though the parameter uses the word "caves" it appears to impact the number of sites (lairs) of different types.{{Verify}} If there are more megabeasts than "caves", megabeasts will suffer from a housing shortage and you may end up with things like 10 dragons sharing a lair. Which could make for a [[Fun]] world.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[MEGABEAST_CAP:75]</nowiki></tt>
| Number of caves/labyrinths/lairs, not beasts.
|}

== Max Semi-Megabeast Caves ==

The maximum number of caves that will be inhabited by [[Creature#Semi-Megabeasts|semi-megabeasts]]. If there are more semi-megabeasts than caves, semi-megabeasts will be forced to cohabitate and you may end up with 10 minotaurs in one labyrinth (for example).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEMIMEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SEMIMEGABEAST_CAP:150]</nowiki></tt>
| Number of caves/labyrinths/lairs, not beasts.
|}

== Titan Parameters ==

=== Number ===

This controls the number of megabeasts and semi-megabeasts that exist at the beginning of history. Note that they can get killed or die later due to events during history generation. The number of forgotten beasts is unaffected by this parameter.

Note: One can generate more historical ages by pumping up the amount of semimegabeasts, who are usually more killable than the regular megabeasts.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TITAN_NUMBER:33]</nowiki></tt>
| 0 is a valid number
|}

=== Attack Population Requirement ===

Megabeasts 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 ===

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

=== Created Wealth Requirement ===

Megabeasts 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|Demons]] are similar to titans and forgotten beasts in that they are procedurally generated, but unlike titans they are not unique. Thus many different types of demons will exist in the world but there will be many members of each type. Setting this to zero means no demons will exist, limiting the amount of fun you can have.

{| {{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 Creature Types ==

The number of different [[Night creature|night creatures]] that will exist in the world. Setting this to zero means that the world will have no night creatures.

A setting of zero also means that there will be no [[Bogeyman|Bogeymen]] in adventure mode, though any modded creatures with the [NIGHT_CREATURE:BOGEYMAN] tag will still exist.

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

== 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.

Though the exact size of small, medium, and large are unknown, the counts used here will always be restricted to regions of the given size no matter how large the number. 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 case where only 3 large regions exists 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 can not 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.

{| {{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 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-10(?)
| non-freezing
| N/A (1)
|-
| 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
|}

(1) might affect the [[desert]] subtype, though - needs to be verified; low drainage seems to correlate with sand deserts

=== Minimum Initial Square Count ===

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
|-
| 17x17
| 289
|-
| 33x33
| 1089
|-
| 65x65
| 4225
|-
| 129x129
| 16614
|-
| 257x257
| 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. This should create a tendency for more extreme rainfall in regions, creating more forests, deserts, marshlands, and grasslands. 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.

{| {{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 ==
[[File:Open00Density100.jpg|thumb|200px|Cavern slice with Openness of 0 and Density of 100]]
[[File:Open100Density00.jpg|thumb|200px|Cavern slice with Openness of 100 and Density of 0]]
[[File:Open100Density100.jpg|thumb|left|200px|Cavern slice with Openness of 100 and Density of 100]]
[[File:Open50Density50.jpg|thumb|left|200px|Cavern slice with Openness of 50 and Density of 50]]

[[Caverns]] are the hollow areas underground which dwarves tend to encounter when they're digging around.

=== Cavern Layer Number ===

This 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.

'''Warning:''' If this is 0 then you will not have caverns on your map. Note that disabling caverns will make it impossible to grow any underground plants because none will exist for your civilization to cultivate. (Underground plants will not be available on embark.)

{| {{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.

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

This 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>
|}

See [http://www.bay12forums.com/smf/index.php?topic=76355.0 this forum thread] for more information on openness and density including many more images.

==== Layer Water min\max ====

Determines how many caverns will have water at the bottom. Note that, even at 100, there will be some amount of ground in caverns, but each cavern 'bubble' will contain some amount of water.

At 0, there will be no water in your caverns. This may impact future underground plant growth, although maps will still start with underground flora.{{Verify}}

{| {{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 have impact on volcanoes, nor vulcanism, 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. (Unknown whether this has any impact on occurrence of HFS "temple".){{Verify}}

{| {{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. 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'' this 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 for version 0.31.25 this setting is inaccurate. The actual number of z-levels may vary in a range of ≈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 very top of second cavern and very bottom of 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 very top of third cavern and very bottom of 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 very highest magma and very bottom of 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 has no impact. Values larger than default results in strange things.
|}

Some implications:
* The number of surface layers (e.g. soil), at this time, can not 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 temple, 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 temples, 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 values can cause strange things to happen. Even more true for small values.

== Cave Parameters ==

Caves are sort of like caverns except that they have a passage to the surface and are generally much smaller. Caves can connect to caverns if they are sufficiently deep.

=== Minimum/Maximum Natural Cave Size ===

These parameters appear to control the length and depth of caves.

{| {{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 (Non-)Mountain Caves ===

These are the numbers of mountain and non-mountain caves that will be placed. These parameters will cause this number of caves to be placed, but rejections may occur if a world has an insufficient number of mountain or non-mountain squares to place the caves in.

{| {{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: 1 to 800
|-
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:200]</nowiki></tt>
|}

=== 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 as {{Raw Tile|•|#808080|#00DD00}} symbols 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 ==

This parameter doesn't do anything in DF2010.{{Verify}} In older versions, tunnels could be built between dwarven settlements and these could appear on the map similarly 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 civilizations will be placed on the map before history generation begins. These civilizations may later die out due to historical events.

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. These 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>
|}

="The World Generator is having trouble placing..."=

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

If you are having the common problem of your generated worlds always being rejected by the world generator, see [[World_rejection#Solving_World_Rejection_Problems|Solving World Rejection Problems]] as it contains many detailed suggestions on how to troubleshoot and solve these issues.

= Default Worldgen Parameters =

There is no single default for each parameter. Several advanced world generation profiles come with the game by default. See [[world_gen.txt|Default world_gen.txt]] to take a look at this file.

= Parameter Set Examples =

If you're trying to do something specific then the [[Worldgen examples|Worldgen examples]] might be helpful. These are complete parameter sets that can be copied directly into your ''world_gen.txt'' file and customized as desired.
If they have nothing for you try [[Worldgen Tricks|Worldgen Tricks]], for known tricks and tips on making a world just right for you.

For many many more examples see:
* [http://www.bay12forums.com/smf/index.php?topic=64032.0 DF2010 WorldGen "Cookbook" Thread]

= Bugs =
*Magma sea breaching into [[HFS]]{{bug|1791}}
*Embark on a mountain of Slade, with Eerie Pits immediately revealed{{bug|3356}}
*Anti-Gravity Ants - Floating ant hills above river{{bug|3054}}

{{World}}
[[Category:World]]

v0.31:Advanced world generation

2011-12-25T06:09:28Z

Shmo: /* Minimum and Maximums */

{{quality|Exceptional|23:35, 30 March 2011 (UTC)}}{{av}}
{{buggy}}

:''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.''
:''See [[World rejection]] for information on solving problems related to worlds always being rejected.''
:''See [[Worldgen examples]] for example worlds.''

When you want more control of what your world looks like, it's time for '''advanced world generation'''. A detailed reference with advice is provided below. This article assumes that you are already familiar with [[World generation|'''basic''' world generation]]. If you are not then please read about that first.

= Advanced World Generation Screen =

Once you select {{DFtext|Design New World With Advanced Parameters}} from the main menu, a screen that looks something like this will appear:

[[File:AdvancedWorldGen.png‎]]

This screen is relatively intuitive but some parts could use some explanation.

== Parameter Sets ==

The list of already defined parameter sets is in the upper right corner. You can select the current set that you want to work with using the up and down directional keys.

Hitting {{K|a}} will add a new set to the end of the list. You can also {{K|c}}opy an existing set to a new one allowing you to base a new set on an existing one. Using {{K|t}} you can change the name of the parameter set but note that this will not affect the name of the world that is generated.

Parameter sets are stored in the <tt>data/init/world_gen.txt</tt> file in the main DF directory. The {{K|F1}} and {{K|F6}} keys will load and save '''all''' of the parameter sets to this file. You will need to save the world gen parameters to this file before you hit {{K|Enter}} to generate the world.

The <tt>world_gen.txt</tt> file can also be edited with a text editor. This is particularly useful because people will often post their parameter sets on the forum or wiki in text form. (See below for more info.) The {{K|F1}} key comes in handy when editing this file while the game is still running.

The tokens used in <tt>world_gen.txt</tt> are at the bottom of each parameter description. Here's the one for title.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITLE: <name>]</nowiki></tt>
| <tt><nowiki>[TITLE:MEDIUM ISLAND]</nowiki></tt>
| Required
|}

== World Name ==

As previously mentioned, the title of the parameter set doesn't affect the name of the world. You can force a particular name for your world using {{K|n}} or set it back to the default random setting using {{K|N}}.

{| {{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.
|}

== World Dimensions ==

The size of the map to be generated can be selected with {{K|u}} {{K|i}} {{K|o}} {{K|p}}. Larger maps take longer to generate and may limit [[Frames per second|FPS]] in game.

Changing the dimensions of the world will reset the parameters because many of them have different defaults depending on the surface area available.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[DIM:<width>:<height>]</nowiki></tt>
| <tt><nowiki>[DIM:129:129]</nowiki></tt>
| Valid values are 17,33,65,129, and 257. Others may not work.
|}

== Seed Values ==

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 word 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.

A specific seed value can be entered with {{K|s}}. This will change '''all''' of the seed values to the value you enter. If you need to enter different seed values for each type of seed, use {{K|e}}.

In order to find out what seed values were used for the last world you generated you can look at this screen. If you want to be able to tell someone else how to generate exactly the same world that you just generated, they will need all of the seed value listed under Last Param Set.

Normally you don't enter these seed values and the world generation process comes up with seed values based on some sort of "true" random information from things like random values in uninitialized memory, the current date/time, etc. If you have entered a seed value you can revert back to all seeds being random using {{K|S}}.

== Entering Advanced Parameters and Generating a World ==

Unless you're using an already defined parameter set you will probably want to {{K|e}}dit the parameters. Select the set you want to edit using the up/down directional keys and press {{K|e}}. Information about each parameter is documented below.

Once you are happy with the parameters you have set, hit {{K|Esc}} to get back to this screen, hit {{K|F6}} to save the values you just edited, and hit {{K|Enter}} to start. The rest of the process is the same as basic [[World generation]].

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

== World Painter ==
:''Main article [[World painter]]
The '''world painter''' tool allows you to paint features onto a map that is then used when generating a world. It is very difficult to use properly, and tends to result in endless rejected worlds, unless you loosen or remove the restrictions placed on biomes and civilizations in the advanced settings. That being said it is also a very powerful tool, and allows you to generate worlds more to your liking.

To access the world painter, hit {{k|e}} to start editing the advanced parameters and finally hit {{k|p}} to open world painter. How to use the world painter is not entirely obvious so please check out the [[World painter]] documentation to avoid frustration. (Losing may be fun, but frustration is not.)

== Editing the Parameters Init File Directly ==

Parameter sets are stored in ''world_gen.txt'' in the ''\data\init'' folder, using [[world token]]. You can copy and paste other player's sets of parameters into your ''world_gen.txt'' to use their parameter sets, and some are provided at [[Main:Pregenerated worlds|Pregenerated worlds]]. Another place to find parameter sets is the [http://www.bay12games.com/forum/index.php?topic=20638.0 Worldgen cookbook] thread on the official forums.

= Advanced Parameters =

To access advanced parameters, press {{key|e}} when at the screen for creating new worlds with parameters screen. This will bring you to an editable list of various guidelines the world-gen process will use when creating your new world.

The parameters are described below in the order that they appear in the list in the UI, not necessarily the other they appear in the configuration file. See [[world token]] for an index that will help you look things up by token name.

== Seed Values ==

Here you can enter specific seed values for different parts of the world generation process. Different sequences of pseudorandom numbers are used for different parts, so you can use this to reproduce only the particular part of world generation from some previously generated world if you want.

Normally you will want to leave all of these set to Random unless you're specifically trying to reproduce the results of another world generation run.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEED:<number>]</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.
|-
| <tt><nowiki>[HISTORY_SEED:<number>]</nowiki></tt>
| <tt><nowiki>[HISTORY_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[NAME_SEED:<number>]</nowiki></tt>
| <tt><nowiki>[NAME_SEED:31337]</nowiki></tt>
|-
| <tt><nowiki>[CREATURE_SEED:<number>]</nowiki></tt>
| <tt><nowiki>[CREATURE_SEED:31337]</nowiki></tt>
|}

== Embark Points ==

This controls the number of points that you have for skills and equipment when you embark in fortress mode. Turning this value up will allow games started in this world to start with more skilled dwarves with better equipment. Normally you can do just fine by leaving this value set to default, but you might want to up it for experimental/testing purposes or to help dwarves survive in a particularly evil world.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[EMBARK_POINTS:<number>]</nowiki></tt>
| <tt><nowiki>[EMBARK_POINTS:1274]</nowiki></tt>
| Required
|}

== End Year ==

This is how many years of history are generated for the world. This is basically the same as the History parameter in basic world gen, except that you can enter an exact value for number of years. See [[World_generation#History|History]] for more info.

History is divided into "ages" which are determined by the ''percentage'' of megabeasts and semi-megabeasts killed at various points. One can attempt to make a world go through the ages more quickly by pumping up the ratio of semimegabeast to megabeast caves, the former of which are usually more killable than the regular megabeasts. This will net you more "Age of Legends", "Age of Heroes", etc.

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:1050]</nowiki></tt>
| Required
|}

== Population Cap After Civ Creation ==

This determines the maximum possible population of civilization member beings on the map. It should usually be kept the same value as the appropriate sized standard map. Turning the value up will result in larger civilizations. You can enter -1 to make population unlimited in which case populations will only be limited by factors like biome, space, number of sites, and per-civilization population caps.

Each race may have up to 100 civilizations each, and each civilization a maximum population of 10,000. This means that '''if you set this parameter to -1 ("No cap"), you can quickly be overrun''' by sites and population. Civilizations, known as ''entities'' in the [[Raw file|raw files]], have 3 or 4 basic variables that will greatly affect their final placement on the world map, in respect to this kind of unchecked growth. See [[Entity_token#Population|Population (Entity Token)]] for more information on interpreting/editing the raws if you need more precise control of civilization placement.

Huge populations can cause the size of history data to explode, cause history generation to take forever, lower FPS, and generally slow down the game.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TOTAL_CIV_POPULATION:<number>]</nowiki></tt>
| <tt><nowiki>[TOTAL_CIV_POPULATION:15000]</nowiki></tt>
| Required
|}

== Site Cap After Civ Creation ==

This controls the maximum number of towns and similar sites on the entire map. Raising the number will allow for more towns, etc though the number of sites will ultimately still be limited by things like space, terrain, and population cap.

Note that '''this parameter controls only "civilization" sites''' like towns. Other sites such as lairs will be added on to this maximum. After civilizations reach this cap, they will not spread out anymore to place new cities.

By default, the raws limit each civilization site to a population of 120 regardless of the race of the civilization. Therefore, without editing the raws, the total population on the map can't go above site cap x 120.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SITE_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SITE_CAP:1040]</nowiki></tt>
| Required
|}

== Beast Control ==

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

=== Percentage of Beasts Dead for Stoppage ===

The world starts out with a certain number of megabeasts in existence. If this percentage of megabeasts dies during history generation, then history generation will stop early. For example if the value is 80, if history starts with 200 megabeasts and 160 of them are killed by historical events or otherwise die before End Year is reached, history generation will stop early.

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

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

{| {{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 ==

Whether or not the game ignores unimportant figures in history generation. The culling is many CPU-intensive steps in history generation but it saves memory and will speed up loading/saving games a bit. This does mean that the "unimportant" figures will not appear in Legends mode or in things like dwarf engravings, but they might not appear in engravings anyway.

Unimportant figures are people or creatures who suffer early deaths, never having offspring or killing anything named during history generation. For example, residents of goblin towers may get murdered by demons at a young age. After culling unimportant figures, Legends mode would say something like the demon has killed "a creature at Eviltower in the year 102."

{| {{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 all information about the history of the world in Legends mode. 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 determine how random values for terrain elevation, rainfall, temperature, drainage, volcanism, and savagery 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. Changing these can cause the occurrence of certain [[Biome|biomes]] to become impossible, so modify these with care. Because of this problem, you may want to use [[#Weighted Ranges|Weighted Ranges]] instead.

By ''subtly'' tweaking the min and max values, vastly different maps can be made.

=== 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.
* River start locations need a minimum elevation of 300. Therefore, a world with a maximum elevation of 299 everywhere prevents river generation, but rivers can still occur if maximum elevation is set to 300.
*Mountain peaks can only form in squares with an elevation of 400.

=== Rainfall ===

Controls the amount of rainfall in each map square/area. Setting the minimum too high or the maximum too 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 [[DF2010:Advanced world generation#Do Orthographic Precipitation and Rain Shadows|orthographic 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 orthographic precipitation option.

=== 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. See [[Climate]] for more info.

Temperature appears to always be a vertical gradient of some sort no matter how these parameters are set, but if the values are lower then the gradient could be from "cold" to "colder" rather than "cold" to "warm" for example.

So, the value from the temperature rolling process is ''not the absolute temperature value the region will get, but rather local variation.'' The "base" temperature for an area is derived from its latitude (and maybe elevation{{Verify}}), and then the random value determined by these parameters are applied to it to make it vary a bit. The local variation is fairly small compared to the base temperature, which appears to be hard coded.

=== 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|Layers]], 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. Rising the minimum will increase the rarity of non-igneous layers.

Setting minimum to 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 too high of a 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.
|-
| <tt><nowiki>[RAINFALL:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[RAINFALL:0:100:200:200]</nowiki></tt>
| Range: 0 to 100
|-
| <tt><nowiki>[TEMPERATURE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[TEMPERATURE:25:75:200:200]</nowiki></tt>
| Range: -1000 to 1000
|-
| <tt><nowiki>[DRAINAGE:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[DRAINAGE:0:100:200:200]</nowiki></tt>
| Range: 0 to 100
|-
| <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.
|-
| <tt><nowiki>[SAVAGERY:<min>:<max>:<x variance>:<y variance>]</nowiki></tt>
| <tt><nowiki>[SAVAGERY:1:100:200:200]</nowiki></tt>
| Range: 0 to 100
|}

== Terrain Mesh Sizes and Weights ==

These parameters make it possible to influence the number of squares in a particular range without making conditions outside of that range impossible. For example, you can make it possible for more many more low elevation squares to exist without making it impossible for high elevations to form. Changing these parameters is often preferable to simply changing the min/max values.

[[File:World_map-large-32x32-elevation-mesh.png|thumb|300px|A large world generated with an Elevation Mesh Size of 32x32 and range weights set to 1:0:0:0:1 (i.e., only extreme high and low elevations). Notice that with this coarse mesh, the terrain seems to appear almost like a grid of "pyramids" that are smoothed together. With a finer mesh size, these pyramids will be smaller, more numerous, smoother, and less apparent.]]
=== Mesh Size ===

Mesh size determines how "finely grained" weighted ranges will be applied. Setting this to Ignore will cause the weighted range settings to be ignored for that terrain characteristic.

Mesh Size affects the smoothing brush in the world painter.

=== Weighted Ranges ===

If mesh size is set to something other than Ignore, these weights will be applied at the granularity of the selected mesh size for purposes of generating random values in each range. This allows random number generation to be non-linear for the given terrain characteristic.

For example, if the Elevation Weighted Range parameters were set to (starting with the 0-20 range) 60:10:10:10:10 (these values do not have to add up to any particular number) then about 60% of the map squares (on average) will have an elevation in the range of 0-20, and the other ranges will be represented by around 10% of the map squares each. The exact distribution is still left up to chance though ''on average'' it will be close to this specification.

The way the process appears to work is that the map is divided into a "wireframe mesh" where the lines are Mesh Size number of tiles apart. Each intersection of the "wires" is randomly assigned an elevation (or whatever) and then the tiles between these points are smoothed out. See the image on the right for an example.

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.

=== 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>
|}

== 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. 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.{{Verify}}

{| {{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.

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 and 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 ==

Worlds with less than this number of volcanoes will be rejected. Note that this will not just create this many volcanoes at random; there must be at least this many squares with a Volcanism of 100. Therefore adjusting Weighted Range for 80-100 to some higher value is recommended if you want to facilitate a large number of volcanoes. In addition, Maximum Volcanism must be set to 100 or squares with volcanism of 100 will be impossible making volcanoes impossible.

{| {{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 lower will increase the amount of ore present on a map, the number of different types of ore, and the number/types of gems. The default value will result in a maximum of 2-4 metal ores per map (assuming you choose a good embark location) which may be limiting until the economy is fully implemented and desired metals can be traded for.

According to research by [http://www.bay12forums.com/smf/index.php?action=profile;u=36045 Shandra] on 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. See [http://www.bay12forums.com/smf/index.php?topic=79018.msg2063804#msg2063804 this forum thread] for detailed information on peoples' experiments and possible changes to newer versions.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MINERAL_SCARCITY:<number>]</nowiki></tt>
| <tt><nowiki>[MINERAL_SCARCITY:2500]</nowiki></tt>
| Range: 100 to 100,000
'''setting to lower than 500 may create alot of rejected worlds cause not enough rivers'''(confirmation needed)
|}

== Max Megabeast Caves ==

This is the maximum number of caves that will be inhabited by [[Megabeast|megabeasts]]. Even though the parameter uses the word "caves" it appears to impact the number of sites (lairs) of different types.{{Verify}} If there are more megabeasts than "caves", megabeasts will suffer from a housing shortage and you may end up with things like 10 dragons sharing a lair. Which could make for a [[Fun]] world.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[MEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[MEGABEAST_CAP:75]</nowiki></tt>
| Number of caves/labyrinths/lairs, not beasts.
|}

== Max Semi-Megabeast Caves ==

The maximum number of caves that will be inhabited by [[Creature#Semi-Megabeasts|semi-megabeasts]]. If there are more semi-megabeasts than caves, semi-megabeasts will be forced to cohabitate and you may end up with 10 minotaurs in one labyrinth (for example).

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[SEMIMEGABEAST_CAP:<number>]</nowiki></tt>
| <tt><nowiki>[SEMIMEGABEAST_CAP:150]</nowiki></tt>
| Number of caves/labyrinths/lairs, not beasts.
|}

== Titan Parameters ==

=== Number ===

This controls the number of megabeasts and semi-megabeasts that exist at the beginning of history. Note that they can get killed or die later due to events during history generation. The number of forgotten beasts is unaffected by this parameter.

Note: One can generate more historical ages by pumping up the amount of semimegabeasts, who are usually more killable than the regular megabeasts.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Example
! Notes
|-
| <tt><nowiki>[TITAN_NUMBER:<number>]</nowiki></tt>
| <tt><nowiki>[TITAN_NUMBER:33]</nowiki></tt>
| 0 is a valid number
|}

=== Attack Population Requirement ===

Megabeasts 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 ===

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

=== Created Wealth Requirement ===

Megabeasts 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|Demons]] are similar to titans and forgotten beasts in that they are procedurally generated, but unlike titans they are not unique. Thus many different types of demons will exist in the world but there will be many members of each type. Setting this to zero means no demons will exist, limiting the amount of fun you can have.

{| {{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 Creature Types ==

The number of different [[Night creature|night creatures]] that will exist in the world. Setting this to zero means that the world will have no night creatures.

A setting of zero also means that there will be no [[Bogeyman|Bogeymen]] in adventure mode, though any modded creatures with the [NIGHT_CREATURE:BOGEYMAN] tag will still exist.

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

== 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.

Though the exact size of small, medium, and large are unknown, the counts used here will always be restricted to regions of the given size no matter how large the number. 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 case where only 3 large regions exists 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 can not 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.

{| {{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 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-10(?)
| non-freezing
| N/A (1)
|-
| 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
|}

(1) might affect the [[desert]] subtype, though - needs to be verified; low drainage seems to correlate with sand deserts

=== Minimum Initial Square Count ===

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
|-
| 17x17
| 289
|-
| 33x33
| 1089
|-
| 65x65
| 4225
|-
| 129x129
| 16614
|-
| 257x257
| 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. This should create a tendency for more extreme rainfall in regions, creating more forests, deserts, marshlands, and grasslands. 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.

{| {{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 ==
[[File:Open00Density100.jpg|thumb|200px|Cavern slice with Openness of 0 and Density of 100]]
[[File:Open100Density00.jpg|thumb|200px|Cavern slice with Openness of 100 and Density of 0]]
[[File:Open100Density100.jpg|thumb|left|200px|Cavern slice with Openness of 100 and Density of 100]]
[[File:Open50Density50.jpg|thumb|left|200px|Cavern slice with Openness of 50 and Density of 50]]

[[Caverns]] are the hollow areas underground which dwarves tend to encounter when they're digging around.

=== Cavern Layer Number ===

This 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.

'''Warning:''' If this is 0 then you will not have caverns on your map. Note that disabling caverns will make it impossible to grow any underground plants because none will exist for your civilization to cultivate. (Underground plants will not be available on embark.)

{| {{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.

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

This 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>
|}

See [http://www.bay12forums.com/smf/index.php?topic=76355.0 this forum thread] for more information on openness and density including many more images.

==== Layer Water min\max ====

Determines how many caverns will have water at the bottom. Note that, even at 100, there will be some amount of ground in caverns, but each cavern 'bubble' will contain some amount of water.

At 0, there will be no water in your caverns. This may impact future underground plant growth, although maps will still start with underground flora.{{Verify}}

{| {{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 have impact on volcanoes, nor vulcanism, 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. (Unknown whether this has any impact on occurrence of HFS "temple".){{Verify}}

{| {{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. 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'' this 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 for version 0.31.25 this setting is inaccurate. The actual number of z-levels may vary in a range of ≈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 very top of second cavern and very bottom of 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 very top of third cavern and very bottom of 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 very highest magma and very bottom of 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 has no impact. Values larger than default results in strange things.
|}

Some implications:
* The number of surface layers (e.g. soil), at this time, can not 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 temple, 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 temples, 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 values can cause strange things to happen. Even more true for small values.

== Cave Parameters ==

Caves are sort of like caverns except that they have a passage to the surface and are generally much smaller. Caves can connect to caverns if they are sufficiently deep.

=== Minimum/Maximum Natural Cave Size ===

These parameters appear to control the length and depth of caves.

{| {{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 (Non-)Mountain Caves ===

These are the numbers of mountain and non-mountain caves that will be placed. These parameters will cause this number of caves to be placed, but rejections may occur if a world has an insufficient number of mountain or non-mountain squares to place the caves in.

{| {{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: 1 to 800
|-
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:<number>]</nowiki></tt>
| <tt><nowiki>[NON_MOUNTAIN_CAVE_MIN:200]</nowiki></tt>
|}

=== 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 as {{Raw Tile|•|#808080|#00DD00}} symbols 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 ==

This parameter doesn't do anything in DF2010.{{Verify}} In older versions, tunnels could be built between dwarven settlements and these could appear on the map similarly 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 civilizations will be placed on the map before history generation begins. These civilizations may later die out due to historical events.

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. These 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>
|}

="The World Generator is having trouble placing..."=

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

If you are having the common problem of your generated worlds always being rejected by the world generator, see [[World_rejection#Solving_World_Rejection_Problems|Solving World Rejection Problems]] as it contains many detailed suggestions on how to troubleshoot and solve these issues.

= Default Worldgen Parameters =

There is no single default for each parameter. Several advanced world generation profiles come with the game by default. See [[world_gen.txt|Default world_gen.txt]] to take a look at this file.

= Parameter Set Examples =

If you're trying to do something specific then the [[Worldgen examples|Worldgen examples]] might be helpful. These are complete parameter sets that can be copied directly into your ''world_gen.txt'' file and customized as desired.
If they have nothing for you try [[Worldgen Tricks|Worldgen Tricks]], for known tricks and tips on making a world just right for you.

For many many more examples see:
* [http://www.bay12forums.com/smf/index.php?topic=64032.0 DF2010 WorldGen "Cookbook" Thread]

= Bugs =
*Magma sea breaching into [[HFS]]{{bug|1791}}
*Embark on a mountain of Slade, with Eerie Pits immediately revealed{{bug|3356}}
*Anti-Gravity Ants - Floating ant hills above river{{bug|3054}}

{{World}}
[[Category:World]]

v0.31:Cross-training

2011-12-17T22:47:43Z

Shmo: purged reference to sparring injuries

{{quality|Fine|20:28, 24 August 2010 (UTC)}}{{av}}

'''Cross-training''' is the process of training your civilian dwarves in military pursuits, or vice versa, and can offer several benefits. First and most importantly, it can be a good way of raising attributes, leading to stronger, tougher, faster dwarves. Secondly, it provides a handy pool of recruits for when your military takes a beating or gives your civilians a halfway decent chance of defending themselves. Thirdly, it can provide useful replacements for when your legendary mason accidentally blunders into a troll and gets all his limbs broken. Finally, it's a more productive use of time than standing around idling.

There is nothing saying you have to use only one of these ideas; they are all various approaches toward addressing these areas.

==Cross-training (starting a reserves program)==
The biggest thing to remember with a reserves program is that if you're going to go, you go all the way. Don't institute something "just for a little while" and come up with a handful of novice reservists; they will not get significant stat increases and you'll only waste time. Time is not something you have a heck of a lot of in a reserves program, typically. Remember that after you draft them, most dwarves are going to need about a year of sparring or training before they're ready for heavy combat. You might not have that much time if you are getting sieges regularly.

===Different Programs:===

====Gym ([[pump operator]])====
The Gym is the most basic sort of reserves program; it merely consists of building a bunch of [[screw pump]]s connected to nothing in a room that's close to [[food]], [[bed]]s, and [[drink]]. After the pumps are built, order them to be pumped manually, then turn on [[Pump operator|pump operating]] for your reservists.

'''Pros:'''
*Easy and extremely cheap to set up;
*Requires no continuous oversight on your part.
*Beneficial for fps, air-pumpers consume, produce and move nothing.
*Somewhat fast training; legendary in under a year (if other responsibilities like hauling are minimized).
*Very convenient; gyms can be placed anywhere in your fortress with no issues. 
*Inactive marksdwarf squads can operate pumps to cross-train and be activated at a moment's notice - boost attributes without using bolts.
*If desired, you can arrange your pumps so they power one or more indoor [[waterfall]]s or other water-powered devices.
'''Cons:'''
*Generates nothing useful other than the increased attributes of the trainee.
*Tons of cancel job spam. Every time a reservist exhausts himself and goes to satisfy his basic needs, you'll see "Urist McScrewpumper cancels Operate Pump: Exhausted."
*If you have any pumps around that actually DO need to be operated every so often (refilling your [[well]], for example), it could be a serious pain to juggle the useless gym pumps and the ones that are actually useful.

====Artillery proving ground ([[siege operator]])====
Mass-produce some catapults, line them up near a quarry, and fire away. Works well to dispose of stone from a gulag (see below). 
'''Pros:'''
*Trains a skill that's reasonably useful, and provides a place to put all the sub-par siege engine components your [[siege engineer]] will doubtlessly create if you're going for superior-quality engines.
*Harasses the wildlife, which is always fun. 
'''Cons:'''
*Very slow to train (2+ years for legendary).
*Fairly space-consuming to set up a well-designed and usable proving ground.
*Can be dangerous depending on the biome (especially when [[elephant]]s are present. If they get winged by a stray boulder, you can bet they're going to be coming straight at you).
*[[Siege operator]]s are civilians, and will run in fear when an enemy approaches them.

====Internship MkII ([[manager]])====
Much like bookkeeping, assign a new dwarf to manager, queue several hundred jobs, and rotate a replacement in as soon as he becomes legendary. For bonus points, queue jobs which need to be repeated anyway, like "Prepare Raw Fish" or "Mill Plants", or jobs for which there is no workshop, like "Make Wooden Bow" or "Make Soap". 
'''Pros:'''
*Requires no extra infrastructure at all.
*You need a manager anyway!
*Mostly safe; a manager spends basically all his discretionary time snug in his office, or doing his other assigned jobs.
'''Cons:'''
*Only employs one dwarf at a time; not useful when you have 15-25 candidates for the reserves.
*No announcement when the current intern reaches Legendary status means you can lose time on rotation easily.
*Produces little to no useful attribute gains

====Gulag ([[miner]])====
The gulag is basically a strip mine that is located far away from your main fortress (so you don't have to worry about accidentally screwing up your own building plans; if you are careful in planning, it may be placed closer to your fortress). Take a big square and start leveling it; it's really no more complicated than that. Since [[pick|picks]] can actually be used as weapons, it's worthwhile to give the reservists who will be working in the gulag picks made out of [[bronze]], or, if you are really living large, [[iron]] or even [[steel]]. Note that you will have to turn your usual mining corps (the civilian miners who are already experienced with mining) off or designate separate mining [[burrow]]s for this setup to work properly. It might be convenient to use a locked door to isolate the gulag from the main fortress, once a batch of trainees are inside. 
'''Pros:'''
*Soldiers can be equipped with picks from the military skill, and use the Miner skill in combat - militia squads of highly-skilled miners can provide a decent defence from early threats
*Toting a pick for close-quarters support might make a legendary [[marksdwarf]] more useful, since the pathetic bludgeon damage of his [[wood]] and [[bone]] [[Weapon#Dwarf-manufactured Weapons|crossbows]] are less important.
*Can be quite useful for producing stones you might not have access to normally, or uncovering veins of precious metals.
*Levels quite fast in sand.
*Relatively little oversight from you.
*An overland hike to the gulag will fight [[cave adaptation]] in your military candidates.
*Can easily be transformed into a [[Caverns#Vegetation|underground tree farm]] on suitable maps, providing a safe and replenishable wood source.

*Mining trains all military attributes, so it's perfect for military training too
'''Cons:'''
*Juggling your real miners and your reservists when there's real work to be done on the fort can be a chore.
*Hard to keep dwarves in the gulag for too long; they'll inevitably get hungry, thirsty, and tired and start hiking back to the fortress proper. Could be solved by (temporary) [[burrow]].
*Can be dangerous, depending on the biome.
*Does require some amount of oversight from you, especially when your reservists start getting better at mining and run out of work more quickly.
*Low-skill miners may discover---and then partially destroy---valuable gem or mineral deposits.
*Surplus stone and mining in general are suspected to promote [[Maximizing_framerate|lag]].

====Renovation ([[stone detailing]])====
Another convenient way to buff up your dwarves, assigning your reservists to mass [[stone detailing]] duty increases your fortress' architectural wealth and makes the place look nicer. While they may clutter the halls somewhat, it doesn't require any special allocation of [[food]], [[Bed|beds]] or [[drink]]. Just turn on [[stone detailing]] for your reservists and mark up as much of the fortress as you like for renovation. 
'''Pros:'''
*Even easier to set up; just assign your dwarves and an area and you're good to go.
*Increases your fortress' value and general happiness.
*Requires no continuous oversight on your part.
*Very safe, if you only assign areas inside the fortress.

'''Cons:'''
*Wealth overflow may bring too many [[immigrants]].
*Serious conflict with [[engraving]] assignments; trying to engrave with poorly trained engravers wastes a lot of wealth that essentially comes from nothing. To avoid this, have periods when you only designate stone smoothing, followed by periods where you only designate engraving.
*Careless designation of smoothing areas may have your dwarves trying to smooth walls too close to [[magma]] or a [[river]].


====Sweatshop ([[mason]])====
Make one or more [[mason's workshop]]s in an area with a bunch of junk stone you don't care about, or that you're actively looking to clear. Change the workshop settings to allow only your reservists to use it, then tell the workshop to churn out crafts, junk furniture, stone blocks, and trade goods that you can trade en-masse. Alternatively, forbid your reservists from working in your real mason's workshops, order lots of stone constructions built, and pray that your real masons stay too occupied with the workshops to intrude. Works well in conjunction with a gulag. Alternate ideas for sweatshops include a [[mechanic's workshop]], [[craftsdwarf's workshop]], [[Kiln|magma kiln]], or a [[Glass furnace|magma glass furnace]] to train [[mechanic]], [[Stone crafter|stonecrafter]], [[potter]] and [[glassmaker]] respectively. ''Note: Do NOT try this with the [[carpenter]] skill unless you have a large supply, or any other resource you don't have in near-limitless abundance. Sweatshops will consume huge amounts of their associated resources, and if you run out mid-way you have probably wasted your time. This includes [[coke]] or [[charcoal]] used in the normal (non-magma) [[glass furnace]].'' 
'''Pros:'''
*Quantitatively turns a profit. The inferior trade goods can be dumped on the next caravan for more useful commodities like bags, seeds, and logs. Logs are especially useful, since you'll inevitably stamp out lots of bins to support the trade good output.
*Mass-producing blocks makes your constructions higher value.
*Unlike many other training programs, Sweatshops train a skill that is very useful.

'''Cons:'''
*Slow to level.
*Hard to keep the reservists on task, since they'll need to do plenty of hauling to keep their workshop from becoming chokingly cluttered.
*Can be a logistical nightmare; making bins and organizing hauling for the finished goods can be insane if you're working from a gulag.
*Can be dangerous depending on the biome and location of your sweatshops.
*Note also that stone blocks cannot be made into furniture or stone crafts. This may or may not be an issue depending on where you're putting your gulag.

====Dwarf Powered Mill ([[grower]], [[cook]], [[miller]])====
Start off by creating a surplus of [[longland grass]], [[cave wheat]], and/or [[whip vine]] and some bags. Create multiple [[quern]] all close to the food stockpile which contains the millable plants. Next to this area make a [[kitchen]] assigned to an experienced cook. Enable milling for the dwarves you wish to cross-train and order the cook to make lavish meals. As long as your growers provide a steady supply of millable plants and your cook can empty out bags quick enough, the milling jobs will continue. 
'''Pros:'''
*Produces a lot of wealth as flour is a high value ingredient
*Produces high amounts of food
*Sustains the training of non cross-training dwarves such as the cook and growers

'''Cons:'''
*Requires a surplus of millable plants to ensure continuous milling, thus you may need to increase the number of plots/growers
*If you don't have enough bags and your cook decides to go on break you may end up having job cancellations for the millers
*Dedicated haulers will be required to keep all workshops clutter free

====Clear Cutting====
As long as wood hauling is turned off, dwarves will move from one tree to the next without stopping to bring the wood back. On a heavily forested map, this means that dedicated wood cutters can skill up very quickly.

Of course, this training strategy isn't going endear you with the elves.

'''Pros:'''
*Works quickly
*Trees regrow
*Provides useful lumber to carpenters, charcoal makers, etc
*Can cause problems with elves
'''Cons:'''
*Can cause problems with elves
*Map dependent
*Unless care is taken to only designate a small area for cutting, trainees and haulers can be spread out across the map while, making them vulnerable to creatures and ambushes.

====Dwarf Scouts ([[ambusher]], [[hunter]], [[marksdwarf]])====
Marksdwarves are an important part of any military. A bum rush of low level marksdwarves is good, but not as effective as an elite backup squad! Here is what you can do:
Draft a comfortable amount of dwarves to hunting, give them all cheap crossbows. Your dwarves should hunt as usual. But you are really training an elite squad of assassins, that will one day hunt goblins instead of groundhogs.

'''Pros:'''
*Easy to start.
*Lots of meat, bones and leather around.
*Aforementioned bones can be recycled to make new bolts.

'''Cons:'''
*Doesn't work on some maps.
*Hunting is dangerous!
*Not as economically productive as some other methods.

====Charm School ([[Social skill|Social skills]])====
(Note: Inspired by [http://www.bay12games.com/forum/index.php?topic=47533.0 milaga's Real Wagon experiment], details of this technique are still being investigated.)
This approach is less useful in the new version, as social skills will only produce "Soul" attribute gains. However, teaching your dwarves social skills is useful for training replacement Brokers, and can possibly reduce the chances of tantrums in the fort (more dwarves with high Consoler and Pacifier skill).

Set up a small space with food, booze, and a few beds/chairs/tables, stashing your new immigrants in it, and locking the door for a few seasons. (Be sure to turn off all of their labors and designate it as a meeting place.) With no labors enabled and nothing to do, they'll chat and party and quickly buff up their comedian, flatterer, conversationalist, &c. skills.

'''Pros:'''
*works on any map
*easy to set up
*trains many dwarves at once
*requires almost zero player oversight
*easily scales to any size of immigrant wave
*requires no resources the dwarves would not already be consuming (food, beds, &c)
*very safe
*no conflict with existing workshops or skills, unlike gulag or sweatshop

'''Cons:'''
*dwarves gain no professional skills during this time, and their existing ones may rust
*lowers physical attributes due to rust
*produces no trade goods or useful items for the fortress
*produces many romances and tight-knit friendships, which [[Tantrum#Tantrum Spiral|put you at risk]] of suddenly having lots of [[losing#General Unhappiness|Fun]]
*inter-dwarf personality conflicts can produce early misery and tantrums. This can be prevented with quality furniture and food, and the risk is eliminated once friendships and relationships are formed and producing happy thoughts.
*unless the entrance and path from the exterior are carefully set up, you will probably have to draft new dwarves and station them in the charm school to move them there; this will produce an unhappy thought that can exacerbate the early period of tension

====National self-defense training====
''Note: with the new military system, proper self-defense training is somewhat more complicated to set up, but allows much more effective reservist training once it's running. Make sure you're familiar with the [[Scheduling]] system before attempting this.''

This is the process of training all your civilians in a basic military skill - or at least, most of them. Any time a dwarf is activated into the military, and they do not have at least Novice level in some combat skill, they get a bad thought. The easiest way to do this is to assign every new [[migrant]] to dedicated training [[squad|squads]], and assign that squad a barracks. Then, schedule these squads to Train one or more months in the year, and set all other months to "No Scheduled Order". Then go to the Squads menu and set the squad to "Active/Training". One month in six or one month in 12 will ensure skills don't get too rusty, as well as ensuring all dwarves reach a basic level in soldiering. To increase the rate at which dwarves gain skills, you can place one experienced soldier in each squad, which will make demonstrations much more valuable. It is worth setting the "Train" order in the schedule to less than 10 minimum; this allows dwarves to take time out to eat, drink, sleep...

Then, if they ever get caught where they don't want to be (maybe they bump into a thief coming around a corner, or a flying critter jumps them, or you need to urgently order them out of the path of a magma flood, or send them to the [[Lever|control room]] - anything), not only can you activate them with no bad thoughts, but every dwarf has a better chance at not-dying - which can only be a good thing. Moreover, idle dwarves will now go to "Individual Combat Drill" rather than standing around timewasting.

Note: if you're feeling cheap, training squads can be set to "No Uniform". This will teach wrestling. However, it's probably a better idea to churn out some training weapons, wooden shields and leather armour, as this will allow dwarves to gain the shield user and armour user skills.

===Overview===
*The charm school can cross-train many dwarves in the many mental attributes, but produces no useful items, trade wealth, or professional skills. The method is also still being refined and potential pitfalls may still be uncovered.
*Artillery training can give you some siege operators, which will be useful if you have ballistae.
*The internship only trains up one dwarf at a time. Your stocks could also lag behind if you are unlucky.
*The gulag requires planning, and your dwarves in the fortress proper may run all the way to the gulag to grab a stone for some crafts, a chair, etc. It does, however, train your dwarves in mining quickly, which is always a useful skill.
*Renovation is hands-free, but may bloat your fortress wealth too quickly.
*The sweatshop creates a large amount of goods, which can be traded away to keep traders happy. It also increases your wealth by quite a lot, which can be good or bad depending upon your situation. The goods are also difficult to manage.
*National self-defence training is easy to manage when set up and lets you give your civilians clothes and light armour to keep them safe. However, it can take valuable workers away from their job if the training is too frequent.

Note that the artillery training and internship don't take away [[strange mood]] potential (you can give those dwarves dabbling in anything you want and that's how they'll get theirs), while the gulag, renovation, and sweatshop do.

{{Military FAQ}}

{{Category|Military}}
{{Category|Fortress defense}}

v0.31 Talk:Thought

2011-12-14T22:01:49Z

Shmo:

== Effects of Thoughts==
As of [[DF2010]], some negative thoughts make the dwarf work much more slowly. The dwarf will
continue to work for a time, presumably until the negative thought becomes unbearable, and
then will go attempt to resolve the thought by eating, sleeping, drinking, or some other action.
Um... no. The thoughts do not cause the dwarf to slow down - the thoughts are a result of the pre-existing [[40d:Status icons|status]], which is what both slows them down and causes the thought. That is, they get hungry or tired or whatever, and then they both slow down and have the bad thought about the cause. This is like saying that if a dwarf has a bad thought about losing their foot to magma, the bad thought is what burned their foot off.--[[User:Albedo|Albedo]] 20:22, 6 April 2010 (UTC)
:Hmm. I was just going by observation... I hadn't even seen this string dump business. I saw there was no new article, and sought to get one started. Also, why not fix the mistake instead of making nice big comments detailing the error on the talk pages for both me and the article? [[User:Garanis|Garanis]] 21:07, 6 April 2010 (UTC)
:Also, there are some ''very strange'' unhappy thoughts in that string dump. Gems such as: "has been attacked by a dead and still annoying acquaintance lately" and "had a terrifying nightmare about an army of the dead." I've never seen these, even in some terrifying fortresses. I don't think theres an reason to include everything in the string dump in these lists.[[User:Garanis|Garanis]] 21:20, 6 April 2010 (UTC)
::"By observation" is not a recommended nor perfectly reliable approach, especially not without independent confirmation. Adding "something" to a blank page is, actually, ''not'' better than if it's flawed and misleading, not for the newbie who's relying on it for their information. And I did fix it - I deleted it. And just now I fixed what you put in its place. As for unusual thoughts, the wiki doesn't care so much what one individual has or hasn't seen, it only cares about what is useful to the community - and that's up to the users. I was just tossing it out as a suggestion. (And how many "terrifying fortresses" have you had so far in the new version? nm - rhetorical question - but one that leads us back to "independent confirmation", or the lack of it.) --[[User:Albedo|Albedo]] 21:35, 6 April 2010 (UTC)

:::Regardless of the semantic issues, the way dwarves handle thirst, hunger, and fatigue has changed. Unlike 40d, dwarves now wait to fulfill their needs. This fact should be represented somewhere. Maybe [[Thought]] isn't the best place for it. Should I wait for someone to independently verify that dwarves need food before I go start that article? Where is the best place to ask for independent verification?[[User:Garanis|Garanis]] 21:54, 6 April 2010 (UTC)

Well I do remember something in the dev plans about bringing back the old zombie attacks from the 2D version, I think that will be part of whatever he has planned, and that first thought was hilarious [[Special:Contributions/24.255.86.193|24.255.86.193]]

One of the Happy Thoughts is "took someone to bed recently"? Surely this is a reference to carrying out healthcare duties and not truly as scandalous the article currently suggests. Should we amend?

There are much more thoughts than those in that list. We should make that list bigger. --[[User:Niggy|Niggy]] 19:47, 22 May 2010 (UTC)

Anyone thought about finding the values for each thought? I know that some vary based on preferences, but having a base value would be helpful. Also, Defacement now is a huge hit on happiness and is no longer divided by the number of masterworks. Every dwarf that has had a defacement in my games goes to miserable(0) until the thought goes away. With some having nearly a thousand master works, I doubt the old system of 1000/# of masterworks still applies. Can I get a Verification?

==Personal Hygiene==
I've also noticed the positive thought "had a nice bath recently", but I'm not sure where the dwarf could have possibly had it. Perhaps at my pond? Definitively not ''in'' the pond, there is no ramp or stairs in it.--[[User:Doub|Doub]] 08:14, 1 May 2010 (UTC)
:Outdoor ponds are definitely good for this (I've seen dwarfs do it), not sure about brooks or rivers w/o ramps. Further investigation required. I'm also not sure whether the dwarf needs to be able to physically get into the pond to take a bath.--[[User:Nimblewright|Nimblewright]] 11:36, 24 May 2010 (UTC)
::Maybe it used Soap?--[[Special:Contributions/186.124.211.173|186.124.211.173]] 22:00, 17 September 2010 (UTC)

==Filling in the blank spaces ===
* "Was upset that a criminal could not be properly punished": A noble's mandate was not met, but the offender was able to avoid punishment
* "Was irritated at having to haul somebody to bed lately": Dwarf doing the hauling has the trait "Doesn't like helping others"
* "Was irritated at having to give somebody (food/water) lately": Dwarf doing the hauling has the trait "Doesn't like helping others"

21:50, 31 July 2010 (UTC)

"Complained about the draft lately." ?? I see this in early forts a lot, even if I have doors in place. Related to a dwarf who doesn't like it having to go outside but not being cave adapted yet? [[Special:Contributions/173.65.198.35|173.65.198.35]]
:In this case, "draft" refers to [http://en.wikipedia.org/wiki/Draft_%28conscription%29 conscription] into the military. --[[User:Quietust|Quietust]] 22:58, 6 September 2010 (UTC)

tired of drinking the same old booze lately why???

recieved water today -- I'm not sure if this happens every time.

also, does a dorm not count for the beds within for not sleeping in a bedroom?

==Miscarriages Caused By Moods?==
In a recent fortress(one which has already crumbled), a melancholic female dwarf had the 'had a miscarriage recently' thought. I do not believe she was in the military, and even so the military had seen no greater threats than the occasional kobold. I believe this means that moods can cause miscarriages, or at least merits investigation. [[User:Calite|Calite]] 01:27, 8 October 2010 (UTC)
* Is it possible that the reverse is what happened? The dwarf had a miscarriage and that caused the melancholy? --[[User:Twilightdusk|Twilightdusk]] 05:07, 20 November 2010 (UTC)

== Military thoughts ==

Two unhappy thoughts I currently have that are not in the list:

*Was grumbling about long patrol duty lately
*:My one-squad military is on a continuous training cycle, requiring 7 of 10 dwarves at all times (but they've seen no action yet). I guess this can be brought on by being required to serve 2 months in succession, since 5 or 6 of the 10 are complaining, but I don't know what else might modify it.

*Has complained about the draft lately
*:Just one of the 10 has complained, no idea what makes him so special - maybe in part that he has a non-military skill higher than any of his military skills?

What quality criteria must be met to include these in the list? [[User:Hv|Hv]] 08:14, 11 October 2010 (UTC)

== defacement ==

"She has suffered the travesty of art defacement." This related to the announcement "a masterwork of Urist McWeaponsmith has been lost" - I'd marked all the copper and bronze weapons to be melted, to encourage the reactionaries to pick up something better. [[User:Hv|Hv]] 23:28, 24 October 2010 (UTC)

Melting/Atom Smashing/!!Magma!!ing masterwork items of any sort pisses off the creator from what I've experimented with. Best thing to do is either forbid the item from being used or trade it off at the depot to get rid of it. If you have a problem with thefts, throw the masterwork (junk) in a pit and build a wall over it. Just remember to keep it forbidden so some military dwarf doesn't want to equip it.[[Special:Contributions/74.192.98.80|74.192.98.80]] 19:21, 30 November 2010 (UTC)

== Rescue ==

One of my militia dwarves was injured to the point where he couldn't move (the idiot fell asleep when I sent him to kill a cougar), and he had to be dragged back to the hospital. He now has the thought "was rescued recently", which seems to be missing from the list. I assume it's positive.

== Decay of pet/loved one ==

From my habit of atomsmashing any and all immigrant pets on arrival I've noticed that anyone who thus lost a pet gets the "forced to endure the decay of a pet" thought. I've not experimented with treating dwarves thus, but this suggests that the scope of the "forced to endure decay" thought is broader than merely being exposed (or even there being present) a rotten body.t

v0.31:Plump helmet

2011-12-11T22:55:50Z

Shmo:

{{Quality|Exceptional}}
{{plantlookup/0|uses=
* [[Food]]
* [[Alcohol]]
}}
{{av}}

'''Plump helmets''' are the most basic, resilient, and versatile of the six underground plants for dwarves to grow. They are one of the fastest growing plants and can be cooked, brewed into dwarven wine and even eaten raw. They require an underground [[farm plot]], which requires soil or muddy ground. They are the only plant food-item that can be purchased at [[embark]].

Keep in mind that cooking plants destroys their seeds, or in this case their "spawn". Both eating a plant raw and brewing it will leave plump helmet spawn behind, which can then be transferred to a seed [[bag]], then planted and used to grow more. New players should definitely [[Farming|farm]] this crop because it grows relatively quickly, can be planted in any season, can be used to make alcohol, or eaten raw if need be.

If you grow nothing but plump helmets over a large area, your fort may start drowning in plump helmets, a truly terrible condition wherein barrels upon barrels are needed to hold back the waves of purple mushrooms. There are two ways to combat this - firstly, start cooking them into meals, the fancier the better. These produce no spawn, and thus put a dent in the population. This will also level up a cook and produce happy [[thought]]s in your dwarves. Secondly, rotate your crops to include such things as [[pig tail]] (to bootstrap a [[textile industry]]) or [[cave wheat]] (to provide some variety in the diet).

{{gamedata}}
{{Plants}}

v0.31:Dwarven syrup

2011-11-24T09:15:55Z

Shmo:

{{av}}
{{Quality|Fine}}
'''Dwarven syrup''' is a cooking ingredient made from {{L|sweet pod}}s at a {{L|farmer's workshop}} using the "process plants (barrel)" order and the {{L|plant processing}} labor. Five units of dwarven syrup are made from each sweet pod, and one seed per sweet pod will be left over. Dwarven syrup cannot be eaten in its raw state, but can be made into edible food using {{L|cooking}}.

== Bugs ==

* Cooks will only cook dwarven syrup as a last resort, instead preferring to cook solid foods with solid foods. {{Bug|2393}}

[[Category:Food]]
[[Category:Extracts]]

v0.31:Aqueduct

2011-11-11T22:58:46Z

Shmo:

{{av}}
{{Quality|Fine|08:38, 9 June 2010 (UTC)}}

An '''aqueduct''' is any set of elements that carries {{L|water}} or {{L|magma}} from one location to another. An aqueduct is formed by a combination {{L|channel}}s, {{L|dig|tunnels}}, and natural or constructed {{L|floor}}s and {{L|wall}}s creating the path for the fluid to follow. Aqueducts can tap into the side of a natural source or use {{L|pump}}s and gravity to get the fluid to flow to its destination.

Care needs to be taken in the creation of any aqueduct - namely, certain measures like roofing over channels and installing safety valves - are sometimes necessary in order to handle {{L|pressure|pressurized}} fluids. Since in-game pressure sometimes behaves in counterintuitive ways, it is generally a good idea to familiarize oneself with its mechanics before undertaking any large project, lest {{L|flood|something unintended occurs}}.

Below is an example of the most primitive type of aqueduct, the open surface channel.

'''Simple aqueduct'''
top view
≈≈≈......{{char|186}}++ ≈ = {{L|River}}/{{L|lake}}
≈≈≈......{{char|186}}++ ≈ = {{L|Channel}} filled with water
≈≈≈≈≈≈≈≈≈{{char|186}}≈{{char|9}} +. = {{L|Floor}} (indoor/outdoor)
≈≈≈≈.....{{char|186}}++ {{char|186}} = {{L|Wall}}
≈≈≈≈.....{{char|186}}++ {{char|9}} = {{L|Well}}

== See also ==
:* {{L|Water}}
:* {{L|Magma}}
:* {{L|Screw pump}}
:* {{L|Pressure}}

{{Category|Constructions}}

v0.31:Metamorphic layer

2011-11-11T22:42:13Z

Shmo: Some rewording, added a less brusque introduction and a sentence to introduce each of the lists. While somewhat redundant with the headings, I think these make the article feel more readable.

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

A '''metamorphic layer''' is a {{L|stone layer}} comprised of metamorphic rock. Metamorphic layers contain several unique and valuable types of {{L|gems}}; however, they are generally poor in metal ores, lacking any ores of [[iron]]. Furthermore the only metamorphic [[flux]] layer stone is [[marble]].

==Metamorphic layers==

The following types of metamorphic stone form layers:

{{Layerlookup/layers|METAMORPHIC}}

==Stone found in metamorphic layers==

The following types of stone are found in formations within metamorphic layers:

{{Layerlookup/stones|METAMORPHIC}}

==Gems found in metamorphic layers==

Metamorphic layers may yield the following types of gem:

{{Layerlookup/gems|METAMORPHIC}}

* See also: {{l|stone found everywhere}}

{{stones}}
{{category|stone Layers}}

v0.31 Talk:Bauxite

2011-11-11T22:13:59Z

Shmo: /* Real life information */

==Real life information==

Is it REALLY necessary? There's a link to wikipedia right there, and it doesn't add anything useful to players of dwarf fortress, which, after all, is what this wiki is about. [[User:JohnnyMadhouse|JohnnyMadhouse]] 19:24, 22 May 2010 (UTC)
:I think its interresting to know what all those stones do in real life.--[[User:Niggy|Niggy]] 19:40, 22 May 2010 (UTC)
::Me too. I like that the rocks and layers can be more than tiles and colors, if only in my head. I don't like the <nowiki>==In-Game Information==</nowiki> header though. It is a game wiki. We don't need a header telling us when information is game related. --[[User:Nahno|Nahno]] 22:07, 22 May 2010 (UTC)
:::Agreed. All information here should be assumed to be game-related unless labeled otherwise. --[[User:Greycat|Greycat]] 22:15, 22 May 2010 (UTC)
::::Most stone pages tend to be a single paragraph or sometimes a single sentence, so this extra info helps fill them out for those interested without really detracting from the in-game information.--[[User:Shmo|Shmo]] 22:13, 11 November 2011 (UTC)

v0.31:Ghost

2011-11-11T06:56:34Z

Shmo:

{{Buggy}}
{{quality|Fine|21:27, 22 November 2010 (UTC)}}{{minorspoiler}}

After the death of an intelligent creature or a dwarf its soul may occasionally come back as a '''ghost'''. In a dwarf fortress dead dwarves have a chance of returning as ghosts if they are not promptly {{L|coffin|buried}} or {{L|memorial|memorialized}} after their death. Ghosts often take to haunting their relatives and friends, following them around on the same tile, as well as lingering wistfully near areas they frequented in life or the spot they died. However, not all ghosts bear their anguish calmly.

Even babies can become ghosts and there are currentv31.18 reports that dwarves can [http://www.bay12forums.com/smf/index.php?topic=75255.0 grow up while dead] and even [http://www.bay12forums.com/smf/index.php?topic=75255.15 die of old age].

Ghosts are able to pass through walls and cannot be harmed by {{L|Dwarven Atom Smasher|atom-smashing}}. They can be targeted in the Squad kill screen ({{K|s}},{{K|k}}) even though they won't actually be attacked. Ghosts can be dismissed by burying the remains or by engraving rock slabs in memory of the deceased.

==Paranormal Activity==

Ghosts haunting the fortress will occasionally perform some of the following actions, based on their temperament:
* <ghost> sucks the wind out of <dwarf>
* <ghost> raises a high fever in <dwarf>
* <ghost> makes <dwarf> convulse and retch
* <ghost> inflicts excruciating pain upon <dwarf>
* <ghost> causes a spell of dizziness in <dwarf>
* <ghost> paralyzes <dwarf>
* <ghost> stuns <dwarf>
* <dwarf> is throwing a tantrum, possessed by <ghost>
* <ghost> has risen and is haunting the fortress!
* <ghost> is following <dwarf>
* <item> has been misplaced. No doubt <ghost> is to blame!
* <ghost> is throwing objects around the fortress!
* <ghost> can be heard howling throughout the fortress!

The ghost's activities will in large part be determined by the nature of its death. The following table summarizes the different types of ghosts.

{| class="wikitable" width="70%" align="center"
! scope="col" align="left" width="17%" | Type
! scope="col" align="left" width="17%" | Cause
! scope="col" align="left" width="66%" | Effect
|-
|Murderous Ghost
|Berserk
|Murders dwarves.
|-
|Sadistic Ghost
|Berserk
|Batters, scares and paralyses dwarves. Capable of scaring a dwarf to death.
|-
|Violent Ghost
|Berserk
|Batters dwarves.
|-
|Angry Ghost
|Berserk
|Batters dwarves.
|-
|Moaning Spirit
|???
|Troubles one unfortunate dwarf at a time.
|-
|Howling Spirit
|???
|Makes sleeping difficult.
|-
|Secretive Poltergeist
|???
|''Misplaces'' Items.
|-
|Energetic Poltergeist
|???
|Topples furniture, such as chairs.
|-
|Troublesome Poltergeist
|???
|''Misplaces'' items, may topple furniture and pull levers.confirm?
|-
|Restless Haunt
|Troubled life history.
|Drifts around place of death and frequented locations. Also haunts dwarves, causing unhappy thoughts.
|-
|Forlorn Haunt
|"Accidental" death
|Drifts around place of death and frequented locations.
|}

== Science on Ghosts ==
Cave-ins do not kill ghosts, perhaps because they are already dead.

Ghosts are put to rest when any part of their body is put in a burial receptacle. For example, should a dwarf lose a toe in a fight before dying, the toe can be recovered to put its ghost to rest.

== Bugs ==
Ghost names that can't be engraved on a slab and nameless slab engravings. {{bug|3708}}

v0.31:Ghost

2011-11-11T06:56:05Z

Shmo: A hopefully-beneficial rewrite, no real content changes.

{{Buggy}}
{{quality|Fine|21:27, 22 November 2010 (UTC)}}{{minorspoiler}}

After the death of an intelligent creature or a dwarf, its soul may occasionally come back as a '''ghost'''. In a dwarf fortress dead dwarves have a chance of returning as ghosts if they are not promptly {{L|coffin|buried}} or {{L|memorial|memorialized}} after their death. Ghosts often take to haunting their relatives and friends, following them around on the same tile, as well as lingering wistfully near areas they frequented in life or the spot they died. However, not all ghosts bear their anguish calmly.

Even babies can become ghosts and there are currentv31.18 reports that dwarves can [http://www.bay12forums.com/smf/index.php?topic=75255.0 grow up while dead] and even [http://www.bay12forums.com/smf/index.php?topic=75255.15 die of old age].

Ghosts are able to pass through walls and cannot be harmed by {{L|Dwarven Atom Smasher|atom-smashing}}. They can be targeted in the Squad kill screen ({{K|s}},{{K|k}}) even though they won't actually be attacked. Ghosts can be dismissed by burying the remains or by engraving rock slabs in memory of the deceased.

==Paranormal Activity==

Ghosts haunting the fortress will occasionally perform some of the following actions, based on their temperament:
* <ghost> sucks the wind out of <dwarf>
* <ghost> raises a high fever in <dwarf>
* <ghost> makes <dwarf> convulse and retch
* <ghost> inflicts excruciating pain upon <dwarf>
* <ghost> causes a spell of dizziness in <dwarf>
* <ghost> paralyzes <dwarf>
* <ghost> stuns <dwarf>
* <dwarf> is throwing a tantrum, possessed by <ghost>
* <ghost> has risen and is haunting the fortress!
* <ghost> is following <dwarf>
* <item> has been misplaced. No doubt <ghost> is to blame!
* <ghost> is throwing objects around the fortress!
* <ghost> can be heard howling throughout the fortress!

The ghost's activities will in large part be determined by the nature of its death. The following table summarizes the different types of ghosts.

{| class="wikitable" width="70%" align="center"
! scope="col" align="left" width="17%" | Type
! scope="col" align="left" width="17%" | Cause
! scope="col" align="left" width="66%" | Effect
|-
|Murderous Ghost
|Berserk
|Murders dwarves.
|-
|Sadistic Ghost
|Berserk
|Batters, scares and paralyses dwarves. Capable of scaring a dwarf to death.
|-
|Violent Ghost
|Berserk
|Batters dwarves.
|-
|Angry Ghost
|Berserk
|Batters dwarves.
|-
|Moaning Spirit
|???
|Troubles one unfortunate dwarf at a time.
|-
|Howling Spirit
|???
|Makes sleeping difficult.
|-
|Secretive Poltergeist
|???
|''Misplaces'' Items.
|-
|Energetic Poltergeist
|???
|Topples furniture, such as chairs.
|-
|Troublesome Poltergeist
|???
|''Misplaces'' items, may topple furniture and pull levers.confirm?
|-
|Restless Haunt
|Troubled life history.
|Drifts around place of death and frequented locations. Also haunts dwarves, causing unhappy thoughts.
|-
|Forlorn Haunt
|"Accidental" death
|Drifts around place of death and frequented locations.
|}

== Science on Ghosts ==
Cave-ins do not kill ghosts, perhaps because they are already dead.

Ghosts are put to rest when any part of their body is put in a burial receptacle. For example, should a dwarf lose a toe in a fight before dying, the toe can be recovered to put its ghost to rest.

== Bugs ==
Ghost names that can't be engraved on a slab and nameless slab engravings. {{bug|3708}}

v0.31:Limestone

2011-11-10T22:53:33Z

Shmo:

{{quality|Exceptional|11:41, 26 December 2010 (UTC)}}{{layerlookup/0}}{{av}}

Like {{L|dolomite}} and {{L|chalk}}, '''limestone''' is a {{L|flux}} stone which forms entire {{L|sedimentary layer}}s. In addition, limestone layers are the only ones to contain galena or malachite.

In general, limestone layers tend to yield more ores and gems per volume mined than those of other stones, which makes them a prime candidate for exploratory mining. Any overburden thus generated will also be doubly valuable compared to regular stone for crafting as a result of limestone's flux property.

"Limestone" is also the name of the seventh month of the dwarven {{L|calendar}}, covering early Autumn.

<gallery>
File:Limestone.jpg|Limestone
</gallery>

{{gamedata}}
{{stones}}
{{Category|Economic Stone}}

v0.31:Larch

2011-11-10T22:38:52Z

Shmo:

{{Quality|Exceptional|11:05, 8 August 2010 (UTC)}}
{{Treelookup/0}}
{{av}}

The '''Larch''' is a type of {{L|above ground}} {{L|tree}}. It is found in {{L|temperate}} {{L|forest|forests}} and occasionally in {{L|taiga}} regions. Like the overwhelming majority of overland trees, larch {{L|carpenter|wood}} is brown and produces brown products.

{{gamedata}}
{{Plants}}
{{Category|Surface trees}}

v0.31:Cow

2011-11-10T22:36:14Z

Shmo: Small stylistic rewrite

{{quality|Exceptional|08:08, 1 July 2010 (UTC)}}
{{Creaturelookup/0
|bone=15
|meat=10-14
|fat=9
|skull=1
|horn=2
|hoof=4
|lung=2
|intestine=2
|spleen=1
|kidney=2
|eye=2
|brain=1
|heart=1
|liver=1
|tripe=1
|sweetbread=1
|skin=hide
|contrib=no}}
{{av}}
{{creaturedesc}}

Cows are large mammalian herbivores, analogous to their real-life counterparts. They are a very viable source of {{L|food}} for a fortress and can be bought at {{L|embark}}. The products gained from butchering a single cow can, at an estimate, feed four dwarves for about a year. Cows can also be {{L|milk}}ed at a {{L|farmer's workshop}} with a {{L|bucket}} to procure {{L|milk}}. Loved by some dwarves for their "haunting moos," cows require a {{L|pasture}} to survive.

{{gamedata}}
{{creatures}}
{{Category|Animals}}

v0.31:Bauxite

2011-11-10T22:28:49Z

Shmo:

{{Stonelookup/0}}{{av}}{{Quality|Exceptional|02:34, 11 June 2010 (UTC)}}

'''Bauxite''' is a dark-red sedimentary {{L|stone}}. Once highly prized as the only practical source of {{L|magma-safe}} {{L|mechanism}}s to create magma-proof devices, its importance has declined with the addition of many new heat-resistant forms of stone as well as the ability to make {{L|metal}} mechanisms from {{L|iron}} and {{L|steel}}. Nevertheless, it is still used by some long-time players for nostalgia and its rare, bloody appearance makes it an interesting aesthetic choice.

Bauxite may contain both {{l|sapphire}} and {{l|ruby}}.

In real life, bauxite is an ore of {{L|aluminum}}, but the technology required to extract it is beyond the level possessed by dwarves.

==In Real Life==
Bauxite is a stone comprised primarily of the minerals gibbsite (Aluminum Hydroxide: Al(OH)3), boehmite (Aluminum Oxide-Hydroxide: γ-AlO(OH)), and diaspore (Aluminum Oxide-Hydroxide: α-AlO(OH)) (none of which are individually present in Dwarf Fortress). Bauxite forms by the weathering and mineralization of various aluminum-rich soils or clays. Despite the correspondence in game, corundum, the mineral that makes up {{L|ruby}} and {{L|sapphire}} (Aluminum Oxide: Al2O3) does '''not''' form in bauxite.

Extracting aluminum from bauxite, even in the most primitive way, requires the use of the Hall–Héroult process: the electrolysis of bauxite which has been dissolved into molten {{L|cryolite}}. The development of this process transformed aluminum from an exceptionally rare metal to a cheap, utilitarian material. Dwarves have not yet discovered electricity, therefore they cannot make use of electrolysis to get aluminum from bauxite. (If it were implemented, lightning might work)

{{gamedata}}
{{stones}}

v0.31:Bauxite

2011-11-10T22:27:42Z

Shmo: A rewrite to (hopefully) improve the tone of the article

{{Stonelookup/0}}{{av}}{{Quality|Exceptional|02:34, 11 June 2010 (UTC)}}

'''Bauxite''' is a dark-red sedimentary {{L|stone}}. Once highly prized as the only practical source of {{L|magma-safe}} {{L|mechanism}}s to create magma-proof devices, its importance has declined with the addition of many new heat-resistant forms of stone as well as the ability to make {{L|metal}} mechanisms from {{L|iron}} and {{L|steel}}. Nevertheless, it is still used by some long-time players for nostalgia, and its rare, bloody appearance makes it an interesting aesthetic choice.

Bauxite may contain both {{l|sapphire}} and {{l|ruby}}.

In real life, bauxite is an ore of {{L|aluminum}}, but the technology required to extract it is beyond the level possessed by dwarves.

==In Real Life==
Bauxite is a stone comprised primarily of the minerals gibbsite (Aluminum Hydroxide: Al(OH)3), boehmite (Aluminum Oxide-Hydroxide: γ-AlO(OH)), and diaspore (Aluminum Oxide-Hydroxide: α-AlO(OH)) (none of which are individually present in Dwarf Fortress). Bauxite forms by the weathering and mineralization of various aluminum-rich soils or clays. Despite the correspondence in game, corundum, the mineral that makes up {{L|ruby}} and {{L|sapphire}} (Aluminum Oxide: Al2O3) does '''not''' form in bauxite.

Extracting aluminum from bauxite, even in the most primitive way, requires the use of the Hall–Héroult process: the electrolysis of bauxite which has been dissolved into molten {{L|cryolite}}. The development of this process transformed aluminum from an exceptionally rare metal to a cheap, utilitarian material. Dwarves have not yet discovered electricity, therefore they cannot make use of electrolysis to get aluminum from bauxite. (If it were implemented, lightning might work)

{{gamedata}}
{{stones}}

v0.31:Weight

2011-07-11T19:51:22Z

Shmo: Removed some "in DF2010" and "was changed to be in DF2010" since I found these to be redundant with the page's being labeled DF2010. Also rearranged some things and (hopefully) made some improvements

{{Quality|Exceptional}}

'''Weight''' is an item property, and is measured in units '''Γ''', also known as '''urists''' - one unit urist is equivalent to one real kilogram.

Weight is largely used by the game to determine how fast someone or something should move, due to encumbrance effects and carry weight restrictions; to calculate damage, since object mass factors into impact momentum; and to some extent to make temperature calculations, as mass factors into heat capacity. Note that, for DF, weight and mass are currently indistinguishable because as it stands DF gravity is [http://www.bay12games.com/media/df_talk_8_transcript.html uniform both across the whole universe and from world to world] and buoyancy isn't implemented.

Weight is displayed as a quantity associated with an item. Weight calculation is not entirely straightforward, since each item category - or sometimes even individual items - have their own formula for determining weight.

==Weight Calculation==

The general form for calculating weight in DF is to take the material density 'd' as found in the raws multiplied by an item constant C.
 W = d*C

The formula for C is [http://www.bay12games.com/dwarves/mantisbt/view.php?id=1386 almost always] the same for all items in the same raw file(such as item_helm or item_pants). These variations are thought to be caused by bugs, though confirmation is needed. Note that the displayed weight value is truncated and not rounded after the calculation is done, it is thought that the exact weight is maintained internally.

The following table lists all currently known formulas for finding the value of C.
{| {{prettytable}}
|- bgcolor="#999999"
! Category
! Formula
! Notes

|-
| item_armor
| (layer size/ material size)/ 1 010
| The divisor may be slightly higher but is consistent with other values.

|-
| item_helm
| layer size/ 60 000
| The formula for helms specifically appears to be 1/ 1 010, this is thought to be a bug.

|-
| item_gloves
| 1/ 100 000
| Divisor is approximate.

|-
| item_pants
| layer size/ 5 190
|

|-
| item_shoes
| layer size/ 7 500
| The formula for high boots specifically appears to be 1/ 100 000, this is thought to be a bug.

|-
| item_shield
| 1/ 100 000
| Divisor is approximate.

|-
| item_ammo
| size/ 1 000 000
|

|-
| item_weapon
| size/ 1 000 000
|

|}

These values are up to date as of this writing {{version|0.31.03}}.

Other examples: stack of cheap stones, or stone statue, 161-167 Γ. Steel chainmail 19 Γ. Steel or bronze bars, 15-16 Γ. Iron flask, 12 Γ.
The heaviest metal is [[Platinum]], and the lightest metal is [[Adamantine]].