Dwarf Fortress Wiki - User contributions [en]

Surroundings

2020-07-01T01:57:58Z

Albedo:

{{Quality|Masterwork|17:18, 18 September 2017 (UTC)}}
{{av}}

'''Surroundings''' affect the types of [[crop|plant]] life, wild [[animal]]s and [[creatures]] which will appear in play within a given [[biome]]. It is possible to start a [[fortress]] that overlaps multiple alignment types (for example a terrifying [[forest]] and a calm [[shrubland]]). Some players consider this desirable, as it provides diversity in your little corner of the world, but it also has its dangers in the form of more ferocious wildlife.

Some plants and animals are unique to a certain type of surroundings and will only be found if those surroundings are present on the map. Note that most creatures also require a specific [[climate]] to spawn in. Again, it's important to check the specific biomes making up your site. Once a [[creature]] spawns on the map, it is under no compulsion to stay in its own biome and can roam as it pleases. Because of this, the specifics of what means what can be difficult to pin down sometimes.

[[Cavern]]s are not affected by alignments, despite some subterranean creature definitions including an alignment. Good creatures like the gorlak, evil creatures like the troll and savage creatures like the giant cave spider can be found in any cavern, regardless of whether the fortress is settled in good/evil/savage surroundings or not.

== Combinations & characteristics of surroundings ==
The names given to different areas will reflect their moral standing. For example, good biomes may be named "The Hills of Sweetness" while an evil one may be named "The Prairie of Agony". Neutral biomes will generally have more generic names, such as "The Beige Jungles".
{| {{prettytable}}
|-style="background:#dddddd"
|style="background:#aaaaaa"| ||'''Benign'''||'''Neutral'''||'''Savage'''
|-
|style="background:#dddddd"|'''Good'''||Serene||Mirthful||Joyous Wilds
|-
|style="background:#dddddd"|'''Neutral'''||Calm||Wilderness||Untamed Wilds
|-
|style="background:#dddddd"|'''Evil'''||Sinister||Haunted||Terrifying
|}

===Neutral===

:Including {{DFtext|Calm|7:0}}, {{DFtext|Wilderness|2:0}} and {{DFtext|Untamed Wilds|6:1}}

[[File:neutral_biome_preview.png|thumb|120px|left|A generic, neutral biome.]]'''Neutral''' regions are the easiest to understand. They generally mimic the real world, with recognizable wildlife. They can be quite dangerous depending on the region, holding anything from benign and weak weasels, to the generally non-aggressive but physically powerful [[elephant]]s, to the very aggressive and very dangerous [[giant eagle]]s. As one might expect, ''Benign Neutral'' zones are really very safe, while ''Savage Neutral'' areas can pose some major difficulties, depending on the dominating climate, landforms, [[giant badger|or]] [[giant kea|wildlife]]. You'll find most of the standard aboveground plants in these alignments, such as [[prickle berry|prickle berries]], [[rope reed]], [[strawberry|strawberries]] and the like.
{{clear}}
===Good===

:Including {{DFtext|Serene|1:1}}, {{DFtext|Mirthful|2:1}} and {{DFtext|Joyous Wilds|3:1}}

[[File:good_biome_preview.png|thumb|120px|left|A blue-colored good biome.]]'''Good''' biomes tend to have less aggressive (often {{token|BENIGN}}) and weaker [[creatures]], except for the [[unicorn]]. They also tend to have more [[fanciful]] creatures than neutral biomes. Good regions also support the wild [[sun berry]], which makes the best [[alcohol]] in the game. There are generally slight changes between ''Benign Good'' and ''Savage Good''.

====Distinctive flora & fauna====
* Animals: [[merperson]], [[mountain gnome]], [[satyr]], [[unicorn]]
* Plants: [[bubble bulb]], [[downy grass]], [[sun berry]]
* Trees: [[feather tree]]
* Vermin: [[fairy]], [[fluffy wambler]], [[pixie]]
{{clear}}
===Evil===
:Including {{DFtext|Sinister|5:0}}, {{DFtext|Haunted|5:1}} and {{DFtext|Terrifying|5:1}}

[[File:biome_evil.png|frame|left|Pink patch of an evil biome.]][[File:biome_evil2.png|frame|right|Dark red/grey patch of an evil biome.]]

'''Evil''' regions are much more dangerous and strange than their ''Neutral'' and ''Good'' counterparts across the board. First, in addition to the ordinary wildlife native to the biome, various other [[creatures]] that are nasty, dangerous, and spiteful such as [[beak dog]]s, [[harpy|harpies]], and [[ogre]]s can be found in evil regions.

Evil regions may exist either on their own (where they are known as "primordial" evil regions) or they may be caused by the presence of [[demon]]s or [[necromancer]]s ruling over a [[site]] in it. Evil regions possess [[sphere]]s associated with the entities inhabiting it, which influences them to some extent; for example, blight regions kill plant life, and nightmare regions are home to [[Bogeyman|bogeymen]]. Primordial evil areas are eternal, but evil regions caused by demons or necromancers may fade away if there is no activity in the area, making it possible to revert it back to normal. Presumably, slaying the demons and necromancers responsible for the corruption is the way to do so.{{version|0.47.01}}

Most evil regions have associated evil [[weather]]. Evil clouds can inflict various [[syndrome]]s on par with those of [[forgotten beast]]s, or instantly transform creatures into freakishly powerful [[Undead#Thralls, Husks, and_Zombies|thralls]]. Evil rains may also inflict random evil syndromes, albeit less severe ones, and always cause unhappy [[thought]]s and a desire to wash (evil!). Evil rain won't refill pools, but a single evil biome may have both evil and regular rain, even at the same time.

About half of all evil regions are "reanimating", meaning that all wildlife and plantlife will be [[undead]], and any creature that dies will, after a short time, be reanimated as undead. Undead are hostile to all living creatures, and feel no fear or pain. In general, undead wildlife is '''extremely''' dangerous, especially in Terrifying regions, since the undead may include zombified fliers that swoop down and rip your dwarves to shreds with little to no warning at all, and even discounting those, typically harmless creatures like [[beaver]]s will turn out to be necro-buffed monstrosities that are out for all living blood.

Undead can only be killed in [[combat]] by beheading, bisection, or pulping damage, or otherwise by [[Butcher|butchering]], [[Cave-in|cave-ins]], [[Dwarven atom smasher|particle physics]], or good old fashioned [[Magma|magma]]. Beheading, bisection and butchering may leave remains that can be reanimated; any partial corpse or body part that is not "mangled" and contains at least one hand or head can reanimate. This includes [[skin]] and even [[hair]] left over from butchering.{{clear}}

Creatures that can [[Building destroyer|destroy buildings]], [[Trapavoid|avoid traps]] or [[Steals items|steal items]] will retain these abilities in undeath. Undead do not need to breathe, so they will not be stopped by rivers or moats, and aquatic undead can and will come ashore. Furthermore, the usual strategy of dealing with wildlife by avoiding confrontation is impossible since the undead will always stay in a state of "perpetually murderous towards all living beings" no matter how much you decide to bother them. Maybe a [[vampire]] or [[necromancer]] can help?

If your [[Embark|embark]] site spans multiple biomes then only the evil part will have the reanimating effect, and only wildlife appearing from that side will be undead. The reanimating effect extends all the way underground. The trees at embark may all be dead, and though they can be cut down for logs, will not regrow. Undead shrubs are useless for [[Herbalist|gathering]], too.

When embarking in a reanimating evil region, it is advised to move everything underground as soon as possible, and immediately set up plenty of [[trap]]s and/or a [[military]] armed with blunt weapons. Be very careful with [[refuse]] stockpiles and butcher's shops. Keep livestock to a minimum, as they are a liability. Needless to say, hunting is a very bad idea.

Because of the inhospitablity of evil regions, even ''Benign Evil'' is very difficult for beginning players to earn a niche to work in, so it should be reserved for <s>great [[fun]]</s> a challenge only.

====Distinctive flora & fauna====
* Animals: [[beak dog]], [[blizzard man]], [[dark gnome]], [[foul blendec]], [[grimeling]], [[harpy]], [[ice wolf]], [[nightwing]], [[ogre]], [[sea monster]], [[strangler]]
* Plants: [[sliver barb]], [[staring eyeball]], [[wormy tendril]]
* Trees: [[glumprong]]
* Vermin: [[blood gnat]], [[demon rat]], [[knuckle worm]], [[phantom spider]]

===Savage===
: Including {{DFtext|Untamed Wilds|6:1}}, {{DFtext|Joyous Wilds|3:1}} and {{DFtext|Terrifying|5:1}}

'''Savage''' surroundings are the only surroundings which have [[giant animal|giant]] and [[animal people|humanoid]] versions of some animals. It is also possible that two groups of animals happen outside on a savage biome, instead of one. They are also far more varied in wildlife than the other biomes.

Most of the creatures in savage biomes will leave you alone, especially the animal men who are harmless (with a few exceptions), and most of the giant creatures will not be hostile, but then again a savage biome may just surprise you with [[giant kea]]s or [[giant badger]]s, and some of the creatures found in savage biomes are dangerous indeed. If you don't know what to expect, just look it up. "Savage Good" regions are called Joyous Wilds, "Savage Neutral" regions are called Untamed Wilds, and "Savage Evil" regions are called <s>excessively [[fun]]</s> Terrifying.

Savage biomes also house [[whip vine]]s, a high-value millable/brewable aboveground crop and [[highwood]]s, a slow-growing tree that can grow as thick as 3×3.

Civilizations typically do not settle in high-savagery regions, except for [[elf|elves]] who are naturally at peace with animals. This may cause problems during [[world generation]] if the game can't find enough low-savagery regions to place civilizations in.

====Distinctive flora & fauna====
* Animals: above-ground [[animal people]], [[giant animal]]s, [[giant desert scorpion]] (pre-[[Release information/0.42.04|0.42.04]]), [[sasquatch]], [[sea serpent]], [[yeti]]
* Plants: [[whip vine]]
* Trees: [[highwood]]
* Vermin: [[acorn fly]], [[fox squirrel]], [[moghopper]], [[two-legged rhino lizard]]

{{World}}

Symptom

2020-06-30T22:35:19Z

Albedo: lose capital Hospital

{{av}}{{Quality|Exceptional}}
A '''symptom''' is a status effect most often caused by contracting a [[syndrome]]. Individual symptoms can range from mild temporary annoyances to lifelong disabilities to even death if untreated. An affected dwarf will need to be diagnosed at a [[hospital]] before a treatment can be prescribed.
__TOC__
==Blisters==
'''Effects''': Areas affected become prone to infection, this becomes more and more likely as severity goes up. While usually harmless in itself*, a resulting infection might cause a loss of life or limb if not properly dealt with.
: (* unless in the lungs, in which case the unlucky dwarf may be unable to breathe if the effect or a subsequent infection is severe.)

==Bleeding==
'''Effects''': Areas affected will continue to bleed for the duration of the effect and will not taper off like a normal wound. In effect it suggests that whatever caused the wound had an anti-coagulant in the venom. This will quickly cause an affected creature to bleed out if the syndrome is not immediately treated.

==Bruising==
'''Effects''': Causes pain long after the blunt trauma that caused it is over. Even the most severe bruises will heal without intervention, but may hint at fractures under the skin.

==Cough==
'''Effects''': Dwarf will stop and cough occasionally. While nearly harmless by itself severe coughs will sometimes bring up blood. In this case it's a sign of internal hemorrhaging.

==Dizziness==
'''Effects''': Creature might stumble/fall in a random direction when attempting to perform an action (including moving [!!!]). The more severe the dizziness the more likely this is to happen. Beware that stumbling, much like dodging, might end up putting a dwarf in a moat, or chasm, or magma, or off a wall, or falling just enough to land unconscious for a second on a cage trap. The list goes on.

==Drowsiness==
'''Effects''': Creature tires faster than normal and requires more sleep. This can be almost unnoticeable if the severity is low, but results in narcoleptic fits if high.

==Fever==
'''Effects''': Appears to reduce the ability to focus. Intense fevers can also cause stunning. While a fever in itself seems relatively harmless, it's often just the most visible symptom. Feverish dwarfs blink with a red "X".

==Impaired Function==
'''Effects''': Creature will be unable to use affected body parts for the duration. Much of the functionality here is mirrored in swelling, but this allows certain parts (such as organs) that normally can't swell to still cease functioning

==Nausea==
'''Effects''': Creature will stop and [[Vomit]]. How often this happens depends on severity. Sustained and intense vomiting will cause dwarfs to dehydrate.

==Necrosis==
'''Effects''': The affected tissue starts to rot away, which needless to say is a medical emergency. If action isn't quickly taken to remove the tissue (through either surgery or amputation) it will spread throughout the body and may cause [[Health_care#Infection|infection]], killing the creature. Also commonly seen in [[Undead]] creatures.

==Numbness==
'''Effects''': Creature will not be able to feel affected body parts. This makes pain a non-issue, but also hampers their use (I.E. Something with numb hands will find using weapons difficult, something who has a leg that's fallen asleep with have difficulty standing). Prolonged numbness will lead to permanent sensory nerve damage.

==Oozing==
'''Effects''': A sign of infection. Infected areas heal much slower and might kill if especially severe or widespread.

==Pain==
'''Effects''': Creatures that aren't in a martial trance that have pain above a certain level get all their rolls halved. They might give into pain and fall unconscious depending on toughness. This is more likely to happen more often the more severe the pain is, which is usually fatal in combat, since enemies will automatically target the unconscious victim's head with a perfectly accurate, perfectly square strike.

==Paralysis==
'''Effects''': The creature can't move. Severity only decreases the chance of resisting the symptom. Untargeted paralysis often leads to suffocation in smaller creatures, which can include dwarves.

==Swelling==
'''Effects''': Impedes the ability to use affected areas. Normally fairly harmless but can cause death by suffocation if it affects the throat. Prolonged swelling will lead to necrosis.

==Unconsciousness==
'''Effects''': Affected creature will pass out for the duration of this effect, even if the creature isn't in pain or extremely tired.

==Vomiting Blood==
'''Effects''': Much as excessive vomiting can lead to death from dehydration, vomiting blood can lead to death from blood loss. Considered to be a separate condition from coughing blood. If your creature happens to have green blood you'll be unable to tell this from nausea without checking the tiles.

[[ru:DF2012:Symptom]]

DF2014:Symptoms

2020-06-30T22:32:36Z

Albedo: Changing from {Delete} to #REDIRECT due to older versions auto-linking to this namespace

#REDIRECT [[cv:Symptom]]

Symptom

2020-06-30T22:30:19Z

Albedo:

{{av}}{{Quality|Exceptional}}
A '''symptom''' is a status effect most often caused by contracting a [[syndrome]]. Individual symptoms can range from mild temporary annoyances to lifelong disabilities to even death if untreated. An affected dwarf will need to be diagnosed at a [[Hospital]] before a treatment can be prescribed.
__TOC__
==Blisters==
'''Effects''': Areas affected become prone to infection, this becomes more and more likely as severity goes up. While usually harmless in itself*, a resulting infection might cause a loss of life or limb if not properly dealt with.
: (* unless in the lungs, in which case the unlucky dwarf may be unable to breathe if the effect or a subsequent infection is severe.)

==Bleeding==
'''Effects''': Areas affected will continue to bleed for the duration of the effect and will not taper off like a normal wound. In effect it suggests that whatever caused the wound had an anti-coagulant in the venom. This will quickly cause an affected creature to bleed out if the syndrome is not immediately treated.

==Bruising==
'''Effects''': Causes pain long after the blunt trauma that caused it is over. Even the most severe bruises will heal without intervention, but may hint at fractures under the skin.

==Cough==
'''Effects''': Dwarf will stop and cough occasionally. While nearly harmless by itself severe coughs will sometimes bring up blood. In this case it's a sign of internal hemorrhaging.

==Dizziness==
'''Effects''': Creature might stumble/fall in a random direction when attempting to perform an action (including moving [!!!]). The more severe the dizziness the more likely this is to happen. Beware that stumbling, much like dodging, might end up putting a dwarf in a moat, or chasm, or magma, or off a wall, or falling just enough to land unconscious for a second on a cage trap. The list goes on.

==Drowsiness==
'''Effects''': Creature tires faster than normal and requires more sleep. This can be almost unnoticeable if the severity is low, but results in narcoleptic fits if high.

==Fever==
'''Effects''': Appears to reduce the ability to focus. Intense fevers can also cause stunning. While a fever in itself seems relatively harmless, it's often just the most visible symptom. Feverish dwarfs blink with a red "X".

==Impaired Function==
'''Effects''': Creature will be unable to use affected body parts for the duration. Much of the functionality here is mirrored in swelling, but this allows certain parts (such as organs) that normally can't swell to still cease functioning

==Nausea==
'''Effects''': Creature will stop and [[Vomit]]. How often this happens depends on severity. Sustained and intense vomiting will cause dwarfs to dehydrate.

==Necrosis==
'''Effects''': The affected tissue starts to rot away, which needless to say is a medical emergency. If action isn't quickly taken to remove the tissue (through either surgery or amputation) it will spread throughout the body and may cause [[Health_care#Infection|infection]], killing the creature. Also commonly seen in [[Undead]] creatures.

==Numbness==
'''Effects''': Creature will not be able to feel affected body parts. This makes pain a non-issue, but also hampers their use (I.E. Something with numb hands will find using weapons difficult, something who has a leg that's fallen asleep with have difficulty standing). Prolonged numbness will lead to permanent sensory nerve damage.

==Oozing==
'''Effects''': A sign of infection. Infected areas heal much slower and might kill if especially severe or widespread.

==Pain==
'''Effects''': Creatures that aren't in a martial trance that have pain above a certain level get all their rolls halved. They might give into pain and fall unconscious depending on toughness. This is more likely to happen more often the more severe the pain is, which is usually fatal in combat, since enemies will automatically target the unconscious victim's head with a perfectly accurate, perfectly square strike.

==Paralysis==
'''Effects''': The creature can't move. Severity only decreases the chance of resisting the symptom. Untargeted paralysis often leads to suffocation in smaller creatures, which can include dwarves.

==Swelling==
'''Effects''': Impedes the ability to use affected areas. Normally fairly harmless but can cause death by suffocation if it affects the throat. Prolonged swelling will lead to necrosis.

==Unconsciousness==
'''Effects''': Affected creature will pass out for the duration of this effect, even if the creature isn't in pain or extremely tired.

==Vomiting Blood==
'''Effects''': Much as excessive vomiting can lead to death from dehydration, vomiting blood can lead to death from blood loss. Considered to be a separate condition from coughing blood. If your creature happens to have green blood you'll be unable to tell this from nausea without checking the tiles.

[[ru:DF2012:Symptom]]

Symptoms

2020-06-30T22:26:21Z

Albedo: fix redirect to new page name

#REDIRECT [[cv:Symptom]]

Sleep

2020-06-30T22:25:21Z

Albedo: fix link

{{av}}
{{Quality|Exceptional|17:11, 15 September 2012 (UTC)}}

[[Dwarf|Dwarves]] that have been awake for a long time will eventually become tired and desire '''sleep'''. Along with [[food|eating]] and [[alcohol|drinking]], sleep is a necessary maintenance activity that your dwarves will need to perform at intervals, a few times every season. Drowsy dwarves are indicated by a blinking gray arrow. Dwarves who are unable to sleep for 6 months may go [[insane]].

== Mechanics ==
Dwarves that are tired will work more slowly, and produce poorer-[[quality]] results. However, dwarves generally will not remain drowsy for long; upon getting sleepy they usually finish their current task, find a [[bed]], and fall asleep. If no bed is available, they will fall to the floor immediately after completing their last task (a group of drunken dwarves sleeping upon barrels of hard liquor is quite a common sight). If there is an unassigned bed located closer to them than their assigned room, they will sometimes choose to sleep there instead. Dwarves will not sleep in beds located in [[hospital]]s.

As one might imagine, having to sleep in the dirt is not a happy occurrence, and will give your dwarves unhappy [[thought]]s. On the other hand, sleeping on a nice bed, in a nice room will give them a happy disposition upon waking. The exact arrangement of living conditions ([[bedroom design]]) is a big part of fortress design; some players lavish their dwarves' rooms and see it as an easy way to increase their happiness, some see bedrooms only as necessary provisions, and some do away with them entirely, preferring easier-to-create, easier-to-maintain public dormitories instead (these do have the advantage of making [[vampire]]-spotting a piece of cake). Nonetheless, the need to prevent your dwarves from sleeping under the stars more than a few times at the very beginning is a universally agreed-upon point of importance.

Dwarves do not follow natural sleeping cycles. There is no "night" in fortress mode, beyond references in the form of [[night creature]]s (in adventurer mode, however, this is a different story entirely). Instead, they will sleep according to their own internal clock. At the very beginning, dwarves that arrive at the same time will tend to nod off at the same time, but as time progresses, they will diverge into their own cycles. After some time, at most a quarter of the fortress may be asleep at a time.

Other unhappy thoughts associated with sleep are caused by being tired, collapsing from exhaustion, and being disturbed by nearby [[noise]]. Noise can cause uncomfortable or troubled sleep, or wake the dwarf entirely, with increasingly negative thoughts.

Collapsing from exhaustion only really happens in the [[military]]. Dwarves on active military service (stationed or attacking) will forgo sleep for duty, but will be unhappy when they finally do get to sleep. Military dwarves can nonetheless spontaneously fall to the ground [[unconscious]] if they are exhausted. Since dwarves do not come with portable pillows, cannot munch on rations or take swigs from flasks as they can to relieve hunger and thirst, the need to sleep is the primary limiting factor on how long you can keep your military dwarves on high alert before they fall dangerously unconscious.

Sleeping is not the same thing as being [[unconscious]], although the effect is the same. A dwarf may fall unconscious when they give in to [[Symptom#|Painpain]], universally a bad thing, or when recuperating from [[wound]]s in a hospital. Finally, [[hunter]]s have a tendency to fall asleep anywhere, which can cause problems with their happiness (though at a reduced penalty if they're sufficiently trained). To prevent this behavior, disable hunting from the [[labor]]s.

==Detailed mechanics==

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

:* 50000 - dwarf starts considering going to bed (1/120 chance per tick) if idle
:* 54000 - dwarf decides to go to bed if idle
:* 57600 - dwarf starts flashing "[[Status icon|Drowsy]]"
:* 65000 - dwarf gets an unhappy thought about being Tired
:* 150000 - dwarf starts flashing "[[Status icon|Very Drowsy]]"
:* 160000 - dwarf gets an unhappy thought about being Exhausted
:* 200000 - dwarf goes insane

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

==See Also==
*[[Bedroom design]]
*[[Noise]]
*[[Adventure mode#Sleep|Sleeping in adventurer mode]]

{{Category|Thoughts}}
[[ru:Sleep]]

No Stun

2020-06-30T22:24:48Z

Albedo: fix link

{{Quality|Fine|07:15, 17 May 2015 (UTC)}}
{{av}}
{{catbox}}
<onlyinclude>
[[Creature]]s with the '''{{token|NOSTUN}}''' [[creature token#N|creature token]] cannot be [[Status icon|stunned]]. These creatures can [[gravity|fall]] multiple [[z-level]]s, suffer great [[Symptom#Pain|pain]], or be injected with stunning [[venom]] without the momentary vulnerability of becoming stunned. Creatures with this token will attack relentlessly in combat until they are killed. Luckily creatures with this token are rare.

Interestingly, this protection does not extend to large [[web]]s; webbed creatures will still pause and trigger any [[trap]]s in their current tile.
</onlyinclude>
==Creatures who cannot be stunned==

The following creatures possess the {{token|NOSTUN}} token.

*[[Amethyst man|Amethyst men]]
*[[Angel]]s
*[[Bark scorpion]]s
**[[Bark scorpion man|Bark scorpion men]]
**[[Giant bark scorpion]]s
*[[Blood man|Blood men]]
*[[Bogeyman|Bogeymen]]
*[[Bronze colossus]]es
*[[Brown recluse spider]]s
**[[Brown recluse spider man|Brown recluse spider men]]
**[[Giant brown recluse spider]]s
*[[Cave blob]]s
*[[Cave floater]]s
*[[Cave spider]]s
**[[Giant cave spider]]s
*[[Demon]]s
*[[Ettin]]s
*[[Experiment]]s
*[[Fire man|Fire men]]
*[[Flesh ball]]s
*[[Floating guts]]
*[[Forgotten beast]]s
*[[Gabbro man|Gabbro men]]
*[[Giant desert scorpion]]s
*[[Grimeling]]s
*[[Hydra]]s
*[[Iron man|Iron men]]
*[[Jumping spider]]s
**[[Jumping spider man|Jumping spider men]]
**[[Giant jumping spider]]s
*[[Magma man|Magma men]]
*[[Mud man|Mud men]]
*[[Mummy|Mummies]]
*[[Night troll]]s
*[[Nightwing]]s
*[[Undead]]
*[[Titan]]s
*[[Vampire]]s
*[[Werebeast]]s

{{Category|Creature attributes}}
[[ru:No Stun]]

No Pain

2020-06-30T22:24:20Z

Albedo: fix link

{{Quality|Fine|07:16, 17 May 2015 (UTC)}}
{{av}}
{{catbox}}
<onlyinclude>
[[Creature]]s with the '''{{token|NOPAIN}}''' [[creature token#N|creature token]] feel no [[Symptom#Pain|pain]] in (or out of) [[combat]]. These creatures will suffer grievous [[wound]]s and continue fighting without pause, making them significantly harder to kill - many foes are dispatched by a blow to the head after they fall [[unconscious]] from pain. Luckily, creatures with this token are rare.
</onlyinclude>
==Creatures who feel no pain==

The following creatures possess the {{token|NOPAIN}} token.

*[[Amethyst man|Amethyst men]]
*[[Angel]]s
*[[Bark scorpion]]s
**[[Bark scorpion man|Bark scorpion men]]
**[[Giant bark scorpion]]s
*[[Blood man|Blood men]]
*[[Bogeyman|Bogeymen]]
*[[Bronze colossus]]es
*[[Brown recluse spider]]s
**[[Brown recluse spider man|Brown recluse spider men]]
**[[Giant brown recluse spider]]s
*[[Cave spider]]s
**[[Giant cave spider]]s
*[[Demon]]s
*[[Experiment]]s
*[[Fire man|Fire men]]
*[[Forgotten beast]]s
*[[Gabbro man|Gabbro men]]
*[[Giant desert scorpion]]s
*[[Grimeling]]s
*[[Hydra]]s
*[[Iron man|Iron men]]
*[[Jumping spider]]s
**[[Jumping spider man|Jumping spider men]]
**[[Giant jumping spider]]s
*[[Magma man|Magma men]]
*[[Molemarian]]s
*[[Mud man|Mud men]]
*[[Mummy|Mummies]]
*[[Naked mole dog]]s
*[[Night troll]]s
*[[Nightwing]]s
*[[Undead]]
*[[Titan]]s
*[[Vampire]]s
*[[Werebeast]]s

{{Category|Creature attributes}}
[[ru:No Pain]]

Giant jumping spider

2020-06-30T22:22:56Z

Albedo: fix redirect

{{Quality|Superior|10:39, 18 May 2015 (UTC)}}
{{Creaturelookup/0
|meat=23-65
|skin=chitin
|fat=21-34
|intestine=8
|eye=2
|brain=2
|heart=1
|contrib=no}}
{{av}}
{{creaturedesc}}

'''Giant jumping spiders''' do not share the web-spitting ability nor poisonous fangs of other spider species. They may be considered the least dangerous kind of giant spider, however they are still more than a match for an untrained, [[weapon]]less dwarf. Like other spiders, they are immune to [[stun]]ning and [[Symptom#Pain|pain]], so your dwarves should focus on killing blows, not disabling attacks.

Like all the other new giant bugs introduced in 0.34.01, giant jumping spiders are ''not'' large predators and will generally leave your dwarves alone. They only live a maximum of 3 years, making them a poor choice for [[animal trainer|training]] and [[zoo|display]].

Dwarves may [[preference|admire]] them for their ''ability to leap'' (or their ''striking appearance'').
Breeding attempts have been successful, observed to breed rapidly, although despite being spiders they breed much like mammals do, with the females becoming pregnant and then giving birth to generally one or two young. Given the lack of any maintenance requirement such as pastures or nest boxes they make good meat animals and have the added bonus of being able to effectively defend themselves from attackers, as such they can be pastured with more defenseless creatures that require pastures for protection.
{{gamedata}}
{{Creatures}}

Cave adaptation

2020-06-30T22:22:29Z

Albedo: fix redirect

{{Quality|Exceptional|19:36, 29 January 2015 (UTC)}}
{{av}}

'''Cave adaptation''' is a mechanic that causes [[Dwarf|dwarves]] who spend too much time underground with insufficient exposure to outdoor sunlight to grow sick when finally exposed to it. It is controlled by the {{token|CAVE_ADAPT}} [[creature token|token]].

Exposure of cave-adapted dwarves to outdoor sunlight can cause two negative [[thought]]s: "irritated by the sun" and "nauseated by the sun". The latter results from more severe cave adaptation and triggers profuse [[vomit]]ing, which can leave an otherwise capable soldier momentarily defenseless. Cave adaptation causes no problems if the affected dwarves simply remain [[Tile attributes|underground]].

== Prevention and treatment==
First and foremost, be aware that cave adaptation requires much more effort to fully eradicate than it's worth. Most dwarves can spend their entire lives lurking in the dark with no negative consequences. Cave adaptation is only a major concern for your military dwarves, as they are the only ones who really need to be functioning at full capacity when outside. Menial labor dwarves sent out to build roads or structures can endure the unpleasant aspects of cave adaptation just fine, while dwarves you regularly send out to fish or gather plants will quickly lose their cave adaptation entirely. Also, note that only dwarves suffer from cave adaptation. If this process sounds like too much effort, you might just want to recruit a few non-dwarven [[mercenary|mercenaries]] for outdoor combat.

Treatment of cave adaptation is accomplished by exposing your dwarves to outdoor sunlight for an extended period of time. Any tile with the {{DFtext|Outside|3:1}} trait will suffice, gradually reducing the cave adaptation of any dwarf standing there. This can't be cheated - even seemingly-transparent roofs made of [[grate]]s or [[glass]] still cause the tile to be treated as {{DFtext|Inside|6:0}}. The progress of treating severe cave adaptation can be observed through a dwarf's '''Thoughts and Preferences''', as limited exposure to sunlight will first convert severe cave adaptation into mild cave adaptation; see [[Personality trait#Personality-Trait-Like Characteristics|personality traits]] for details.

It takes a lot of sunlight to undo any serious amount of adaptation; a fully cave-adapted dwarf requires 9 weeks of exposure to be fully cured. As such, you'll need to devise entertaining and well-decorated [[Activity zone#Meeting Area|meeting area]]s to lure your dwarves to the surface and keep them there. Make sure there are plenty of high-value decorations in place, or the negative thoughts associated with being in sunlight will cause your dwarves a lot of stress. Also, be aware that any such zone is ripe for attack by invaders; make sure there are soldiers nearby, surround the site with high walls, and consider building a retractable [[bridge]] above it so you can quickly block out the outside world as needed.

For your military, a cheap and sloppy solution is to simply send them outdoors a lot. Attacking the local wildlife is a low-risk exercise that gives your soldiers valuable military training alongside their cave adaptation treatment. Unfortunately, this is not an automated process; letting your dwarves return to the darkness will gradually reestablish their adaptation, and micromanaging your dwarves that much quickly becomes annoying. If you can prevent the reestablishment of cave adaptation, however, the process is much more effective. An alternative strategy is to simply station your dwarves outside for part of the year, using the [[Scheduling]] screen.

Cave adaptation can be ''prevented'' by keeping your dwarves out of {{DFtext|Dark|0:1}} tiles as much as possible. Every moment spent in the dark slightly increases your dwarves' cave adaptation, eradicating the benefits of your surface garden parties, but fortunately these tiles can be converted to harmless {{DFtext|Light|6:1}} tiles with nothing more expensive than time, effort, and a large supply of rock [[block]]s. Any tile that has had all its roofing removed becomes an {{DFtext|Outside|3:1}} {{DFtext|Light|6:1}} tile, the sort which is useful for treating cave adaptation. Building a roof over these tiles replaces the {{DFtext|Outside|3:1}} trait with {{DFtext|Inside|6:0}}, but leaves the {{DFtext|Light|6:1}} trait untouched. These sunlit indoor tiles neither cure nor cause cave adaptation, making them perfect for housing those dwarves who will be heading to the surface often. Once you have a sizable workforce and some well-trained miners, it shouldn't take too long to channel away the top few floors of your fortress and reconstruct them with blocks. Doing this for your entire fortress, however, is almost certainly more work than it's worth. If you have a dedicated squad of soldiers for surface threats and convert their training and living areas to {{DFtext|Light|6:1}} tiles, they should be safe from cave adaptation going forward, especially if you are regularly treating them to wildlife hunts and [[mission]]s abroad.

=== Cave adaptation mechanics ===
* If a dwarf is in a {{DFtext|Dark|0:1}} tile, cave adaptation increases by 1 every [[Time|tick]] to a maximum of 800,000 (403,200 ticks is one year, so the maximum is just short of 2 years).
* If a dwarf is in an {{DFtext|Outside|3:1}} tile, cave adaptation decreases by 10 every tick.
* If a dwarf is in an {{DFtext|Outside|3:1}} tile while the sun is out (i.e. not [[Weather|raining or snowing]]), the following happens:
** If cave adaptation is between 403,200 and 604,800 (between 1 and 1.5 years), the dwarf will become dizzy and experience minor pain and fatigue. They will also receive the unhappy thought "was irritated by the sun recently".
** If cave adaptation is at 604,800 or higher (1.5 years), the dwarf will experience [[nausea]], [[Stunned|dizziness]], [[Symptom#Pain|pain]], and fatigue. They will start vomiting profusely and will also receive the unhappy thought "was nauseated by the sun recently".
** Otherwise, nothing bad happens.

Negative effects of cave adaptation have a percentage chance to trigger (1/1000 per tick) and they are cumulative, so a sufficiently long string of unlucky rolls can actually cause a cave-adapted dwarf to [[Unconscious|pass out]] from exhaustion upon stepping outside. Note that it is possible to get both cave adaptation thoughts at the same time.

== Explanation ==
{{D for Dwarf}}
'''A [http://www.bay12forums.com/smf/index.php?topic=85908.msg2321608#msg2321608 scientific explanation] of cave adaptation by Deus Machina.'''

Underground has low levels of light and very little air circulation.

Dwarves develop low-light vision (plump helmets are ''packed'' with beta carotene!) and their facial follicles become sensitive to the motions that a breeze produces against their beards, which allows them to tell where tunnels turn.

As they go deeper, their eyes become less relied upon, and they adapt further to rely on their whisker-based follication.

These eventually become so sensitive that, should a dwarf venture outside, the wind is the equivalent of multicolored and varying strobe lights. This is as aggravating to a dwarf's follication as a Pink Floyd show seen while sober is to our sight, up to the point of causing nausea.

While some have proposed beard shaving as a method of treating hyperfollication, these people are believed to be elf spies, and drafted to cavern exploring instead.
{{Category|Dwarves}}
[[ru:Cave adaptation]]

Adder

2020-06-30T22:21:52Z

Albedo: fix double redirect

{{Quality|Exceptional|23:40, 9 October 2014 (UTC)}}
{{Creaturelookup/0
|wiki=Vipera_berus
|skull=1
|contrib=no
}}
{{av}}
:''For logical designs related to the addition of numbers, see [[Adder (Computing)]].''
{{creaturedesc}}

'''Adders''' are [[syndrome|venomous]] [[Creature|snakes]] found in many [[temperate]] [[biome]]s.

Adder bites deliver a [[venom]] that can cause immediate strong [[Symptom#Pain|pain]] followed by long-term (but not permanent) [[syndrome|nausea, blisters, and swelling]]. Though the bite itself is not usually fatal, such pain can cause unconsciousness, which ''can'' lead to fatal complications in combat.

Adders are distinct for being the [[list of creatures by adult size|smallest creatures]] in the game which aren't [[vermin]].

Adders can be captured in [[cage]] [[trap]]s and [[Animal trainer|trained]] into cheap exotic [[pet]]s. They are born adults and as such can't be permanently tamed. [[Butcher]]ing an adder only produces a [[skull]], making them worthless to your [[meat industry]]. Female adders are [[egg]]-layers, producing 3-10 edible eggs with regularity, and providing significantly more food than would be expected from such a small creature.

Some dwarves [[Preferences|like]] adders for their ''warning hisses''.

[[Image:Loch Shin adder.JPG|thumb|center|400px|Admired for its ''warning hisses''.]]

{{gamedata}}
{{Creatures}}
{{Category|Animals}}

Anatomy

2020-06-30T22:20:11Z

Albedo: /* Head */ specific link

{{Quality|Superior|21:17, 20 September 2016 (UTC)}}
{{av}}
This page contains a list of all the body parts in the game.

==Head==

*[[Hair]]
*[[Eye]]s
:Eyes, while not essential for life, are bad to lose. The loss of one or both eyes alone will not cause death, but may have other adverse effects. If both eyes are lost then the creature will lose its vision. Currently, eyes cannot be entirely lost, only damaged.
:*Eyelids
::These can be damaged and Toady believes that eyes will be washed with soap if they cannot be washed by the eyelids due to injury.
*[[Brain]]
:Any major damage to the brain will likely result in [[death]]. Minor damage may result in [[Symptom#Unconsciousness|unconsciousness]].

==Upper Body==

*[[Lung]]s
:Damage to one or both lungs can be sustained, but will cause difficulty of breath and may result in a loss of speed. Major damage will cause death.
*[[Heart]]
:Major damage to the heart will cause certain death.
*Stomach
:It's bad if it's damaged. Anything with a stomach will retch and then puke if the stomach is broken.
*[[Liver]]
:Used for processing [[alcohol]]. Dwarven livers are much stronger than human livers and have never been damaged by alcohol. The loss of a liver is a terrible thing for a dwarf.
*Guts
:Under pressure, and can pop out of wound. Also damage here causes vomiting and pain
*Arms
:*Upper Arms
:*Lower Arms
:*Hands
::*Fingers
:::*[[Nail]]s
Is also considered the main part of every creature. In general when this is gone the creature is dead and this is the part that decides what the corpse is and what the severed parts are.

==Lower Body==

*Legs
:*Upper Legs
:*Lower Legs
:*Feet
::*Toes
:::*[[Nail]]s
::::These will grow and become unkempt if not taken care of. This is done automatically by dwarves.

==[[Skin]]==
The first protective layer.

==[[Fat]]==
[[Fat]] can be gained or lost depending on how much a creature eats and how much it works. It will melt if heated to a high enough temperature. This is a layer below the skin and above the muscle.

==Muscle==
This layer is under the fat.

==Arteries==
If damaged, heavy bleeding will likely result in death. They appear to contain several gallons of blood.

==Nerves==
If damaged, the body part they are connected to will become useless or less effective.

==Tendons==
If destroyed, the limbs they connect will be useless.

DF2014:Pain

2020-06-30T22:16:02Z

Albedo: fix redirect to new page name

#REDIRECT [[DF2014:Symptom#Pain]]

Syndrome

2020-06-30T22:15:42Z

Albedo: fix links to new page name

{{Quality|Masterwork|13:02, 6 April 2015 (UTC)}}
{{av}}
[[File:Snakebite.png|200px|thumb|right|A single bite from a [[helmet snake]] lead to a slow, lingering death for this unfortunate hippo.]]
A '''syndrome''' is a specific combination of [[symptom]]s that a poor, helpless creature might get from a disease, venom or other effect, through encountering certain other creatures, substances, or supernatural [[weather]]. Syndromes generally cause unpleasant and frequently fatal symptoms over a short to long period of time, but some will clear up over time or with the assistance of a [[doctor]]. A [[Health care|hospital]] is required to diagnose and potentially treat those syndromes that can be helped by treatment.

==List of syndromes==
Syndromes are generally named after the animal, substance or effect that delivers them. Note that in a world with [[dragon]]s and [[giant elephant]]s, dwarves (and elves and humans) fall into the "small creatures" category for purposes of this discussion.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Syndrome
! Venom
! Acquired
! Short-term Symptoms
! Long-term Symptoms
! Chronic Symptoms
|-
| Adder bite
| adder venom (injected)
| Being bitten by an [[adder]], [[giant adder]] or [[adder man]]
| Strong pain
| Swelling Blisters Nausea
| None
|-
| Bark scorpion sting
| bark scorpion venom (injected)
| Being stung by a [[bark scorpion]], [[giant bark scorpion]] or [[bark scorpion man]]
| Strong pain
| None
| None
|-
| Black mamba bite
| black mamba venom (injected)
| Being bitten by a [[black mamba]], [[giant black mamba]] or [[black mamba man]]
| Dizziness Drowsiness Strong pain Fever Unconsciousness Complete paralysis1
| None
| None
|-
| Blob blisters
| cave blob fluid (contact or ingested)
| Touching a [[cave blob]]
| Mild pain Mild blisters
| None
| None
|-
| Brown recluse spider bite
| brown recluse spider venom (injected)
| Being bitten by a [[brown recluse spider]], [[giant brown recluse spider]] or [[brown recluse spider man]]
| Nausea Fever Pain 
| Severe localized necrosis
| None
|-
| Bumblebee sting
| bumblebee venom (injected)
| Being stung by a [[bumblebee]] worker
| Pain Strong swelling
| None
| None
|-
| Bushmaster bite
| bushmaster venom (injected)
| Being bitten by a [[bushmaster]], [[giant bushmaster]] or [[bushmaster man]]
| Strong pain Mild bleeding Dizziness Nausea Unconsciousness Complete paralysis1
| None
| None
|-
| Cave floater sickness
| cave floater gas (inhaled or ingested)
| Expelled from [[cave floater]]
| Mild nausea
| Fever Strong drowsiness (delayed) Strong dizziness (delayed)
| None
|-
| Cave spider bite
| cave spider venom (injected)
| Being bitten by a [[cave spider]]
| None
| None
| Very mild dizziness
|-
| Copperhead snake bite
| copperhead snake venom (injected)
| Being bitten by a [[copperhead snake]], [[giant copperhead snake]] or [[copperhead snake man]]
| Pain Swelling Nausea
| None
| None
|-
| Giant cave spider bite
| giant cave spider venom (injected)
| Being bitten by a [[giant cave spider]]
| Size-dependant paralysis.
| Death by asphyxiation, in small targets. Large targets are generally unhindered...unless you count the high probability of being eaten by the giant cave spider as a hindrance.
| None, not that it really matters.
|-
| Gila monster bite
| gila monster venom (injected)
| Being bitten by a [[gila monster]], [[giant gila monster]] or [[gila monster man]]
| Pain Mild swelling
| None
| None
|-
| Gnomeblight
| [[gnomeblight]] (contact, inhaled, injected, or ingested)
| Purposely exposing oneself to the extract. Only affects [[mountain gnome]]s and [[dark gnome]]s.
| None
| Severe systemic necrosis2
| None
|-
| Giant desert scorpion sting
| giant desert scorpion venom (injected)
| Being stung by a [[giant desert scorpion]]
| Necrosis of the brain and nervous system
| '''Certain death'''
| None, not that it really matters.
|-
| Helmet snake bite
| helmet snake venom (injected)
| Being bitten by a [[helmet snake]]
| Minor bleeding
| Fever Nausea Dizziness Localized swelling Localized oozing Localized bruising Strong pain Intense localized necrosis Possible loss of limb
| None
|-
| Honey bee sting
| honey bee venom (injected)
| Being stung by a [[honey bee]] worker
| Pain Strong swelling
| None
| None
|-
| Inebriation{{version|0.42.01}}
| [[Alcohol]] (consumed/injected)
| Consuming alcoholic drinks
| Nausea Dizziness Unconsciousness Personality changes Euphoria Erratic behavior Trouble breathing
| None
| None
|-
| Iron man cough
| iron man gas (inhaled)
| Expelled by [[iron man]]
| Coughing blood
| None
| None
|-
| King cobra bite
| king cobra venom (injected)
| Being bitten by a [[king cobra]]
| Complete paralysis1 Pain, dizziness, drowsiness
| None
| None
|-
| Phantom spider bite
| phantom spider venom (injected)
| Being bitten by a [[phantom spider]]
| None
| Numbness and mild dizziness
| None
|-
| Platypus sting
| platypus venom (injected)
| Being kicked by a [[platypus]], [[giant platypus]] or [[platypus man]]
| Pain and swelling
| Extreme pain, swelling possibly to the point of necrosis
| None
|-
| Rattlesnake bite
| rattlesnake venom (injected)
| Being bitten by a [[rattlesnake]], [[giant rattlesnake]] or [[rattlesnake man]]
| Pain, nausea, blisters, swelling, bruising
| Severe localized necrosis
| None
|-
| Serpent man bite
| serpent man venom (injected)
| Being bitten by a [[serpent man]]
| Complete paralysis1
| None
| None
|-
| Mummy's curse
| [[DF2014:Mummy|Disturbance interaction]].
| Being cursed by a [[mummy]], when caught raiding their tombs
| None
| None
| 20% chance of any skill roll failing, regardless of skill.
|-
| Vampirism
| [[Deity|Divine]] Curse.
| Drinking the blood of a [[vampire]]. Toppling statues in shrines in Adventure Mode or temples in Fortress Mode (random chance).
| None
| None
| Victim becomes a [[vampire]].
|-
| Werebeast Curse
| [[Deity|Divine]] Curse.
| Being bitten by a [[werebeast]] or toppling statues in shrines in Adventure Mode (random chance).
| None
| None
| Victim becomes a [[werebeast]].
|-
| Necromancy
| [[Deity|Divine]] Curse.
| Reading a book/slab that contains the secrets of life and death.
| None
| None
| Reader becomes a [[Necromancer]].
|-
| evil rain sickness3
|rowspan=7| Random
| Being caught outside in [[Weather#Evil weather|freakish weather]] in an evil [[biome]]
|rowspan=7| Random
|rowspan=7| Random
|rowspan=7| Random
|-
| evil cloud sickness4
| Being caught in a [Weather#Evil weather|creeping cloud]] in an evil [[biome]]
|-
| beast sickness5
| Encounters with [[forgotten beast]]s
|-
| titan sickness5
| Encounters with [[titan]]s
|-
| night sickness5
| Encounters with [[werebeast]]s or [[experiment]]s
|-
| demon sickness5
| Encounters with [[demon]]s
|-
| divine sickness5
| Encounters with [[angel]]s
|}
: 1. For small creatures such as humans and dwarves, paralysis tends to result in suffocation.
: 2. Necrosis of the brain will eventually result in death once the brain rots away completely.
: 3. Evil rain typically only causes minor symptoms such as blisters, bruising, coughing blood, dizziness, fever, nausea, oozing, and pain.
: 4. Evil clouds either cause major symptoms (as with beast/titan/demon sicknesses) or permanently transform creatures into [[Undead|zombie-like]] forms.
: 5. [[Titan]]s, [[forgotten beast]]s, [[werebeast]]s, [[experiment]]s, [[demon]]s and [[angel]]s have a chance to have a randomized syndrome. These range from mildly hazardous (mild [[Symptom#Blisters|blisters]] from inhaling boiling blood) to instantly fatal (severe necrosis from a contact poison attached to a breath weapon/creature made of blood).

==The anatomy of a syndrome==
Mechanically, syndromes are bundles of tokens attached to a material (or to an interaction effect; see below) - they're confined to creature materials in vanilla DF, but it's a simple matter to add them to inorganic materials. When the material is injected, touched, inhaled, or ingested (depending on the syndrome), the creature suffers the predations of a nasty disease or poison. Here's an example syndrome, taken from the Giant Cave Spider raws.

If you are having troubles getting the syndromes to work (i.e., in combat reports, getting "'''supersnake''' n/a splatters~etc"), then simply throw the venom template into the actual creature's raw, which is what the LOCAL_CREATURE_MAT actually calls on; the venom being in the same file.

[USE_MATERIAL_TEMPLATE:VENOM:CREATURE_EXTRACT_TEMPLATE]
[STATE_NAME:ALL_SOLID:frozen giant cave spider venom]
[STATE_ADJ:ALL_SOLID:frozen giant cave spider venom]
[STATE_NAME:LIQUID:giant cave spider venom]
[STATE_ADJ:LIQUID:giant cave spider venom]
[STATE_NAME:GAS:boiling giant cave spider venom]
[STATE_ADJ:GAS:boiling giant cave spider venom]
[PREFIX:NONE]
[ENTERS_BLOOD]
[SYNDROME]
[SYN_NAME:giant cave spider bite]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[SYN_IMMUNE_CREATURE:SPIDER_CAVE:ALL]
[SYN_INJECTED]
[CE_PARALYSIS:SEV:100:PROB:100:RESISTABLE:SIZE_DILUTES:START:5:PEAK:10:END:20]

The first line, USE_MATERIAL_TEMPLATE, is creating a new material, called POISON, using the CREATURE_EXTRACT_TEMPLATE as the basis. After this, the STATE_NAME and STATE_ADJ tokens are used to define the names and adjectives assigned to different states of the material - GAS, LIQUID and ALL_SOLID, in this case, though ALL is also a valid token. At this stage, you can use any material tags like MAT_FIXED_TEMP or similar to set further material properties, though this usually isn't necessary.

ENTERS_BLOOD
This tag determines whether a poison enters the blood or not. If it is not included, the poison will splatter (if liquid) or flow (if gas) over the affected body part instead when injected. If you're using a contact poison, leave this out. Necessary for injected poisons.
SYNDROME
This tag ends the material details and begins the definition of the actual syndrome.
SYN_NAME
This one is self-explanatory - the name of the syndrome as it will appear in-game.
SYN_AFFECTED_CLASS
This token defines what CREATURE_CLASS will be affected by the syndrome. Most creatures are classed under GENERAL_POISON. Multiple tokens can be used in a single syndrome.
SYN_IMMUNE_CLASS
As above, but makes class immune.
SYN_IMMUNE_CREATURE
This token defines which creatures CANNOT be affected by the syndrome - useful for addressing specific instances within a population, such as a specific caste or an individual creature that falls under GENERAL_POISON. Syntax is [SYN_IMMUNE_CREATURE:creature:caste]. ALL can be used for the caste.
SYN_AFFECTED_CREATURE
As above, but makes creature or caste susceptible.
SYN_CLASS
This tag sets a class for the syndrome that can be used in [[Interaction token|interactions.]]
SYN_IDENTIFIER{{version|0.42.01}}.
Similar to SYN_CLASS, this sets an identifier that can be shared between multiple syndromes, for use with the SYNDROME_DILUTION_FACTOR creature token. In vanilla DF, this is used to allow dwarves to drink more alcohol before becoming inebriated.
SYN_NO_HOSPITAL{{version|0.42.01}}.
Probably prevents affected dwarves from being carried to the hospital.{{verify}}
SYN_CONCENTRATION_ADDED:x:x{{version|0.42.01}}.
Repeated exposure to the syndrome will result in the effects becoming more intense. In vanilla [SYN_CONCENTRATION_ADDED:100:1000] is used with alcohol.

SYN_INJECTED, SYN_CONTACT, SYN_INHALED, SYN_INGESTED
This token determines the method of infection - injected syndromes must be injected via a creature attack, while contact syndromes result from any contamination of a creature by material splatter (such as blood), inhaled syndromes must be inhaled in gaseous form (such as from boiling or a creature breath attack), and ingestion syndromes must be eaten or drunk. Any combination of these tags can be used. A fun variation on the usual creature injection routine is to create a material with a SYN_CONTACT syndrome and have a creature use it for blood - this tends to end poorly for any predator that chooses to attack them.

[SPECIALATTACK_INJECT_EXTRACT:LOCAL_CREATURE_MAT:VENOM:LIQUID:100:100]
This is one method for getting a poison into a creature. If [ENTERS_BLOOD] is applied, it will be injected into the bloodstream. Otherwise, it will just splatter over the area. Put this on a creature attack. Substance type (gas, liquid, solid) does not appear to have an effect. The numbers on the end are minimum and maximum.

CE_X, or creature effect tokens, are the real meat and bones of your syndrome. They're detailed below.

==Creature effect tokens==
Each and every syndrome has a number of creature effect tokens, represented by CE_X - these lovely little beauties determine exactly how the poor creature suffering from the syndrome is affected. An example CE token is as follows:

[CE_NECROSIS:SEV:100:PROB:100:LOCALIZED:VASCULAR_ONLY:RESISTABLE:START:50:PEAK:1000:END:2000]

In this example, we have an effect that will always cause severe necrosis in whichever bodypart it touches, so long as that bodypart is vascular and that the creature is not able to resist it in some manner. The effect begins shortly after the syndrome is contracted, peaks 1000 [[time|time units]] afterwards, and finally ceases another 1000 time units later.

As a general rule of thumb, so long as CE_X starts the string and START/(PEAK/END) ends it, the order of the intervening tokens isn't important. PEAK and END aren't required.

*CE_X
The effect type. This can be a number of different tokens, as detailed in the table below this list.
*SEV:X
The severity of the effect. Higher values appear to be worse, with SEV:1000 CE_NECROSIS causing a part to near-instantly become rotten.
*PROB:X
The probability of the effect actually manifesting in the victim, as a percentage. 100 means always, 1 means a 1 in 100 chance.
*LOCALIZED (Overwrites BP tokens)
This tag causes an effect to ignore all BP tokens and then forces the game to attempt to apply the effect to the limb that came into contact with the contagion - i.e. the part that was bitten by the creature injecting the syndrome material, or the one that was splattered by a contact contagion. If an effect can not be applied to the contacted limb (such as IMPAIR_FUNCTION on a non-organ) then this token makes the syndrome have no effect. This token also makes inhaled syndromes have no effect.
*BP:BODY_PART:TISSUE (Overwritten by LOCALIZED)
Specifies which body parts and tissues are to be affected by the syndrome. BODY_PART can be BY_CATEGORY:x to target body parts with a matching [CATEGORY:x] [[body token]] (or ALL to affect everything), BY_TYPE:x to target body parts having a particular type (UPPERBODY, LOWERBODY, HEAD, GRASP, or STANCE), or BY_TOKEN:x to target individual body parts by their ID (as specified in the [BP] token). For example, if you wanted to target the lungs of a creature, you would use BP:BY_CATEGORY:LUNG:ALL. The syndrome would act on all bodyparts within the creature with the CATEGORY tag LUNG and affect all tissue layers. For another example, say you wanted to cause the skin to rot off a creature - you could use BP:BY_CATEGORY:ALL:SKIN, targeting the SKIN tissue on all bodyparts. Multiple targets can be given in one syndrome by placing the BP tokens end to end. This is one of the most powerful and useful aspects of the syndrome system, as it allows you to selectively target bodyparts relevant to the contagion, like lungs for coal dust inhalation, or the eyes for exposure to an acid gas. Not everything takes a target!
*VASCULAR_ONLY (Optional)
This syndrome only affects tissue layers with the VASCULAR token.
*MUSCULAR_ONLY (Optional)
This syndrome only affects tissue layers with the MUSCULAR token. Are you seeing a trend here?
*SIZE_DILUTES (Optional)
This token presumably causes the effects of the syndrome to scale with the size of the creature compared to the size of the dose of contagion they received, but has yet to be extensively tested.
*SIZE_DELAYS (Optional)
As above, this token has yet to be tested but presumably delays the onset of a syndrome according to the size of the victim.
*DWF_STRETCH:X{{version|0.42.01}} (Optional)
Multiplies the duration of the syndrome by X in Fortress mode. If X is 72, syndrome will last the same amount of ticks in fortress and adventure mode.
*ABRUPT{{version|0.42.01}} (Optional)
Makes the symptom begin immediately rather than ramping up. {{verify}}
*CAN_BE_HIDDEN (Optional)
Can be hidden by a unit assuming a secret identity, such as a [[vampire]]. {{verify}}
*RESISTABLE (Optional)
Determines if the effect can be hindered by the target creature's [[Attribute#Disease_Resistance|disease resistance attribute]]. Without this token, disease resistance is ignored.

The details of this table are still being thrashed out by modders, so if you have anything to add, please don't hesitate to hit the edit button!

Non-targeted syndromes will ignore any BP tokens and LOCALIZED tokens.
{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Description
|-
| CE_BLEEDING
| Yes
| Causes the targeted bodypart to start bleeding, with heavy enough bleeding resulting in the death of the sufferer. Some conditions seem to cause bleeding to be fatal no matter how weak.
|-
| CE_BLISTERS
| Yes
| Covers the targeted bodypart with blisters.
|-
| CE_BRUISING
| Yes
| Causes the targeted bodypart to undergo bruising.
|-
| CE_IMPAIR_FUNCTION
| Yes
| An organ afflicted with this CE is rendered inoperable - for example, if both lungs are impaired the creature can't breathe and will suffocate. This token only affects organs, not limbs. Note that this effect is currently bugged, and will not "turn off" until the creature receives a wound to cause its body parts to update.
|-
| CE_NECROSIS
| Yes
| Causes the targeted bodypart to rot, with associated tissue damage, miasma emission and bleeding. The victim slowly bleeds to death if the wound is not treated. Badly necrotic limbs will require amputation.
|-
| CE_NUMBNESS
| Yes
| Causes numbness in the affected body part, blocking pain. Extreme numbness may lead to sensory nerve damage.
|-
| CE_OOZING
| Yes
| Causes pus to ooze from the afflicted bodypart.
|-
| CE_PAIN
| Yes
| Afflicts the targeted bodypart with intense pain.
|-
| CE_PARALYSIS
| Yes
| Causes paralysis. Paralysis is complete paralysis and will cause suffocation in smaller creatures. Paralysis on a limb may lead to motor nerve damage.
|-
| CE_SWELLING
| Yes
| Causes the targeted bodypart to swell up. Extreme swelling may lead to necrosis.
|-
| CE_COUGH_BLOOD
| No
| This effect results in the sufferer periodically coughing blood, which stains the tile they're on and requires cleanup. It doesn't appear to be lethal, but may cause minor bleeding damage.
|-
| CE_DIZZINESS
| No
| Inflicts the Dizziness condition, occasional fainting and a general slowdown in movement and work speed.
|-
| CE_DROWSINESS
| No
| Causes the Drowsiness condition.
|-
| CE_FEVER
| No
| Causes the Fever condition.
|-
| CE_NAUSEA
| No
| Causes the Nausea condition, and heavy vomiting. Can eventually lead to dehydration and death.
|-
| CE_UNCONSCIOUSNESS
| No
| Renders unconscious.
|-
| CE_VOMIT_BLOOD
| No
| This effect results in the sufferer periodically vomiting blood, which stains the tile they're on and requires cleanup. It doesn't appear to be lethal, but may cause minor bleeding damage.
|-
| CE_ERRATIC_BEHAVIOR{{version|0.42.01}}
| No
| Causes erratic behavior, meaning "People that like to brawl have a chance of starting a brawl-level fight with any nearby adult" [http://www.bay12forums.com/smf//index.php?topic=159164.msg7632503#msg7632503 -Toady]
|}
====Healing Effects====
Starting with DF version 0.47.01, there are healing counterparts to most of the tokens above that will heal various syndrome effects or physical damage.
{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Description
|-
| CE_STOP_BLEEDING
| Yes?
| Decreases the severity of the bleeding of any wounds or syndrome effects on the targeted bodypart. The SEV value probably controls by how much the bleeding is decreased.
|-
| CE_CLOSE_OPEN_WOUNDS
| Yes?
| Closes any wounds on the targeted bodypart with speed depending on the SEV value.
|-
| CE_HEAL_TISSUES
| Yes?
| Heals the tissues of the targeted bodypart with speed depending on the SEV value.
|-
| CE_HEAL_NERVES
| Yes?
| Heals the nerves of the targeted bodypart with speed depending on the SEV value.
|-
| CE_REDUCE_PAIN
| Yes?
| Decreases the severity of pain produced by wounds or syndrome effects on the targeted bodypart. The SEV value probably controls by how much the pain is decreased.
|-
| CE_REDUCE_SWELLING
| Yes?
| Decreases the severity of swelling on the targeted bodypart.
|-
| CE_CURE_INFECTION
| Yes?
| Probably decreases the severity of the infection from infected wounds over time.
|-
| CE_REDUCE_PARALYSIS
| Yes?
| Decreases the severity of any paralysis effects on the targeted bodypart.
|-
| CE_REGROW_PARTS
| Yes
| Causes missing bodyparts to regrow. SEV controls how quickly bodyparts are regrown. In adventure, parts will be regrown until you travel or wait/sleep {{bug|0011396}}.
|-
| CE_REDUCE_DIZZINESS
| No
| Decreases the severity of any dizziness the creature has.
|-
| CE_REDUCE_NAUSEA
| No
| Decreases the severity of any nausea the creature has.
|-
| CE_REDUCE_FEVER
| No
| Decreases the severity of any fever the creature has.
|}

===Special Effects===
Several special syndrome effects take different arguments than the above. These are used for generated interactions in unmodded games, but may be used as well for any substance or custom interaction.

{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Arguments
! Description
|-
| CE_ADD_TAG
| No
| tags
| Adds a tag to the affected creature. Many arguments can be used sequentially within one syndrome token. Valid tags are the same as that of the [[interaction token]] '''IT_REQUIRES''', ie.

BLOODSUCKER, CAN_LEARN, CAN_SPEAK, CRAZED, EXTRAVISION, LIKES_FIGHTING (or LIKESFIGHTING), MISCHIEVOUS (or MISCHIEVIOUS), NO_CONNECTIONS_FOR_MOVEMENT, NO_DIZZINESS, NO_DRINK, NO_EAT, NO_FEVERS, NO_PHYS_ATT_GAIN, NO_PHYS_ATT_RUST, NO_SLEEP, NO_THOUGHT_CENTER_FOR_MOVEMENT, NOBREATHE, NOEMOTION, NOEXERT, NOFEAR, NONAUSEA, NOPAIN, NOSTUN, NOT_LIVING, NOTHOUGHT, OPPOSED_TO_LIFE, PARALYZEIMMUNE, SUPERNATURAL, TRANCES, NO_AGING, STERILE, UTTERANCES.
|-
| CE_REMOVE_TAG
| No
| tags
| Removes a tag from a creature. Supported arguments are the same as CE_ADD_TAG.
|-
| CE_DISPLAY_TILE
| No
| TILE:[[Tilesets|tile number]]:[[Color#Modding color|colour]]
| The creature displays the specified tile and colour instead of its normal one.
|-
| CE_DISPLAY_NAME
| No
| NAME:singular:plural:adjective
| Attaches a specified name to the creature's normal name.
|-
| CE_FLASH_TILE
| No
| TILE:tile number:colour:FREQUENCY:ticks default tile:ticks syndrome tile
| The creature flashes between its normal tile and the one specified here.
|-
| CE_PHYS_ATT_CHANGE
| No
| [[Attribute]]:percentage:fixed boost(?)
| Alters the physical [[attribute]]s of a creature.
|-
| CE_MENT_ATT_CHANGE
| No
| [[Attribute]]:percentage:fixed boost(?)
| Alters the mental [[attribute]]s of a creature.
|-
| CE_BODY_APPEARANCE_MODIFIER
| No
| APPEARANCE_MODIFIER:HEIGHT/LENGTH/BROADNESS:percentage(?)
| Alters the size of the creature.
|-
| CE_BP_APPEARANCE_MODIFIER
| Yes
| body part:APPEARANCE_MODIFIER:attribute:number]
| Alters the characteristics (height, width etc.) of a body part.
|-
| CE_MATERIAL_FORCE_MULTIPLIER
| No
| MAT_MULT:[[material token|material]]:A:B
| Makes creature affected by materials more or less by a factor of A/B. If A is 3 and B is 2, the creature will be 1.5x weaker to the defined material (can be NONE:NONE for all); if 2:3, the creature will be 1.5 times stronger.
|-
| CE_SPEED_CHANGE
| No
| speed modifier:number
| Changes the speed of a creature.
Speed modifier contains one or both of:
* SPEED_PERC:percentage (this modifies a creature's in-game speed, so higher numbers are faster)
* SPEED_ADD:number (this modifies a creature's [SPEED:XX] token, so higher numbers are slower. Negative numbers are accepted though will only reduce a creature's speed to zero)
The minimum and maximum speeds able to be created by CE_SPEED_CHANGE are 99 and 10,000 respectively.

|-
| CE_CAN_DO_INTERACTION
| No
|
| Makes the creature able to perform an interaction. See [[Interaction token]]. To specify the interaction, use the argument:
* CDI:INTERACTION:interaction name
|-
| CE_SPECIAL_ATTACK_INTERACTION{{version|0.47.01}}
| Yes
| INTERACTION:<interaction name>:BP:<selection criteria>:<name of category,type, or token of designated part/parts>
| Makes the creature able to perform an interaction when using an attack with a designated body part/parts. See [[#Spreading diseases in 0.47.01|below]] for an example

|-
| CE_BODY_MAT_INTERACTION
| No
| MAT_TOKEN:<body material token>
| Causes one of the creature's body materials to trigger an interaction when the material is ingested, injected, etc (depending on the [CE:SYNDROME_TAG]s used; note that more than one may be specified). Generated vampire syndromes use '''RESERVED_BLOOD''' as the body material token in this syndrome tag, so as to specify the blood material of any creature with the syndrome. The following tokens should be inserted after this:
* '''CE:INTERACTION:interaction_id''' - replace 'interaction_id' with the name of the target interaction
* '''CE:SYNDROME_TAG:syndrome_trigger_type''' - replace 'syndrome_trigger_type' with any of SYN_INGESTED, SYN_INJECTED, SYN_CONTACT, SYN_INHALED
The linked interaction must have an [[Interaction_token#I_SOURCE|[I_SOURCE:INGESTION]]] token for this to work!

Note that this currently only works on materials obtained from historical figures and has only been tested with ingested materials linked to interactions with ADD_SYNDROME interaction effects.

|-
| CE_BODY_TRANSFORMATION
| No
| PROB:percentage:START:time:END:time
| Transforms into another creature. PROB and END arguments optional. The target creature may either be specified directly using CE:CREATURE or else set to be randomly selected as guided by creature and/or caste flag restrictions (of which multiple may be specified).
* CE:CREATURE:CREATURE_ID:CASTE_ID - Specify the creature and caste (for example: CE:CREATURE:DWARF:FEMALE). ANY can be used in place of a specific CASTE_ID to randomise the caste for every transformation. 
* CE:CREATURE_FLAG:FLAG{{version|0.47.01}} - Any creature with the specified [[:Interaction_token#Creature_and_Caste_Flags|creature flag]] is a valid transformation target. 
* CE:FORBIDDEN_CREATURE_FLAG{{version|0.47.01}} - Forbids all creatures with the specified [[:Interaction_token#Creature_and_Caste_Flags|creature flag]] from being randomly selected. 
* CE:CREATURE_CASTE_FLAG:FLAG{{version|0.47.01}} - Any creature with the specified [[:Interaction_token#Creature_and_Caste_Flags|caste flag]] is a valid transformation target. 
* CE:FORBIDDEN_CREATURE_CASTE_FLAG{{version|0.47.01}} - Forbids all creatures with the specified [[:Interaction_token#Creature_and_Caste_Flags|caste flag]] from being randomly selected. 
*CE:HAVE_FAST_EFFORTLESS_GAIT_SPEED{{version|0.47.01}} - Unknown. Possibly disallows all creatures with only slow gaits.{{verify}}

Note that any wounds the creature has suffered will instantly heal upon transforming, both into and out of the target form. [[Undead]] limbs of a creature with this token will grow into a full instance of that creature.
|-
| CE_SKILL_ROLL_ADJUST
| No
| PERC:percentage:PERC_ON:percentage
| Alters the skill level of a creature. The argument PERC specifies a percentage of the creature's current skill, and PERC_ON the probability of the effect being applied on a particular roll.
|-
| CE_SENSE_CREATURE_CLASS
| No
| START:time:CLASS:creature class:tile:color
| Allows creature to see other creatures with given class through walls. Vampires, for example, have START:0:CLASS:GENERAL_POISON:15:4:0:1.
|-
| CE_CHANGE_PERSONALITY{{version|0.42.01}}
| No
| FACET:[[DF2014:Personality_trait#Facets|trait]]:amount
| Changes a [[personality trait]] by amount. Multiple FACET:trait:amount sets may be used.
|-
| CE_FEEL_EMOTION{{version|0.42.01}}
| No
| EMOTION:[[emotion]]
| Makes the creature feel a specific [[emotion]]; severity based on standard SEV value. The [[thought]] the creature receives is: "[creature] feels [emotion] due to [syndrome name]". See [[Emotion]] for the list of valid emotions.
|}

'''All''' creature effect tokens take START, END and PROB numbers, and can be followed by [CE:PERIODIC] and/or [CE:COUNTER_TRIGGER] to restrict when they actually take effect.
* PERIODIC:period_type:min_value:max_value
* {{text anchor|COUNTER_TRIGGER}}:counter_name:min_value:max_value:REQUIRED

Currently, the only valid period type is MOON_PHASE.

===Counter Triggers===
Valid counter values are below:

{| {{prettytable}}
|- bgcolor="Bisque"
! Counter
! Description
|-
| ALCOHOLIC
| How long it's been (in [[time]] units) since the creature last had a drink of alcohol. Only present on creatures who need alcohol to get through the working day.
* 100800 (3 months) = and is starting to work slowly due to its scarcity
* 201600 (6 months) = and really wants a drink
* 302400 (9 months) = and has gone without a drink for far, far too long
* 403200 (1 year) = and can't even remember the last time he/she had some
|-
| CAVE_ADAPT
| How cave-adapted the creature is. Increases by 1 for every [[time]] unit spent underground, to a maximum of 800000.
* 403200 (1 year) = going outside causes irritation
* 604800 (1.5 years) = going outside causes nausea
|-
| PARTIED_OUT
| How long before the creature will decide to attend another party. Starts at 3+ months and counts down to zero.
|-
| MILK_COUNTER
| How long before the creature can be milked again. Starts at the creature's MILK frequency and counts down to zero.
|-
| EGG_SPENT
| How long before the creature can lay more eggs. Starts at 3 months and counts down to zero.
|-
| GROUNDED_ANIMAL_ANGER
| How angry (and likely to attack) an animal is from being over-crowded. Increases when over-crowded and otherwise counts down to zero.
|-
| TIME_SINCE_SUCKED_BLOOD
| How long it's been (in [[time]] units) since the creature last sucked somebody's blood.
|-
| DRINKING_BLOOD
| How much longer the creature will be drinking somebody's blood. Starts at 2.4 days and counts down to zero.
|}

{{mod}}

==Inorganic syndromes and you!==
It's perfectly possible - and quite simple - to add a nasty syndrome to a type of rock or metal - you simply add the syndrome tokens to the material definition in the same manner that you would add them to a creature material definition. The only catch is that since your hapless dwarves will only normally encounter the material in metal, gem or boulder form, a bit of creativity must be used to actually get them inside your citizens - that is, you need to make them 'explosively boil' as soon as they're mined or produced. This has the sad side effect of destroying the actual item - sorry, no highly radioactive uranium this release.

The easiest way to accomplish this is to assign the material a low boiling point, usually just under room temperature, and make sure its temperature is fixed to a point above it.
[MELTING_POINT:NONE]
[BOILING_POINT:10000]
[MAT_FIXED_TEMP:10001]
Now, as soon as this substance hits the open air - by being mined, smelted or reaction-produced at a custom workshop - it will EXPLOSIVELY BOIL, flooding a small area with delicious syndrome-rich gas. Creatures who inhale the gas will be immediately hit with the syndrome you thoughtfully attached to the material definition earlier!

There are a number of other tokens you can use to control the colour and naming conventions of your syndrome material, referred to as [[material definition token]]s.

==Spreading diseases==
It's fully possible to make a nasty disease capable of spreading itself from an infected dwarf to others, though it requires some skill in modding [[interaction token|interactions]] as well. Here is an example of a plague-inflicting interaction:

[INTERACTION:PLAGUE]
[I_TARGET:A:CREATURE]
[IT_LOCATION:CONTEXT_CREATURE]
[IT_FORBIDDEN:NOT_LIVING]
[IT_AFFECTED_CLASS:GENERAL_POISON]
[IT_MANUAL_INPUT:creatures]
[I_EFFECT:ADD_SYNDROME]
[IE_TARGET:A]
[IE_IMMEDIATE]
[SYNDROME]
[SYN_NAME:the plague]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[CE_FEVER:SEV:250:PROB:100:START:250:PEAK:1500:END:25000]
[CE_BLISTERS:SEV:325:PROB:100:BP:BY_CATEGORY:ALL:SKIN:START:250:PEAK:1500:END:25000]
[CE_NECROSIS:SEV:300:PROB:100:BP:BY_CATEGORY:ALL:ALL:VASCULAR_ONLY:START:22500:PEAK:23750:END:25000]
[CE_CAN_DO_INTERACTION:START:1500:END:25000]
[CDI:ADV_NAME:Spread the plague]
[CDI:INTERACTION:PLAGUE]
[CDI:TARGET:A:LINE_OF_SIGHT]
[CDI:TARGET_RANGE:A:10]
[CDI:WAIT_PERIOD:30]

As you can see, the syndrome here inflicts blisters, fever and, after roughly a month, necrosis of the whole body - that's when the infected creatures will start dying out. But before that happens, CE_CAN_DO_INTERACTION makes them capable of spreading the plague further.

You also need a disease vector that will bring the plague straight to your fort. (hint: use [[large rat|various]] [[rat man|species]] [[giant rat|of rats]] - they're perfect for that). The following code, added to a creature's raws, ensures the creature will infect anybody it encounters:

[CAN_DO_INTERACTION:PLAGUE]
[CDI:ADV_NAME:Spread the plague]
[CDI:TARGET:A:LINE_OF_SIGHT]
[CDI:TARGET_RANGE:A:10]
[CDI:WAIT_PERIOD:30]

As soon as the said creature is startled by your dwarves, the [[fun]] will begin.

==''In 0.47.01''==
As of version 0.47.01, it may be possible to use a creature's established methods of attack for use in disease-spreading.

Let's use the borrowed example of the plague above. This time, the plague will spread through biting, using the following syndrome code:

[INTERACTION:PLAGUE]
[I_TARGET:A:CREATURE]
[IT_LOCATION:CONTEXT_CREATURE]
[IT_FORBIDDEN:NOT_LIVING]
[IT_AFFECTED_CLASS:GENERAL_POISON]
[IT_MANUAL_INPUT:creatures]
[I_EFFECT:ADD_SYNDROME]
[IE_TARGET:A]
[IE_IMMEDIATE]
[SYNDROME]
[SYN_NAME:the plague]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[CE_FEVER:SEV:250:PROB:100:START:250:PEAK:1500:END:25000]
[CE_BLISTERS:SEV:325:PROB:100:BP:BY_CATEGORY:ALL:SKIN:START:250:PEAK:1500:END:25000]
[CE_NECROSIS:SEV:300:PROB:100:BP:BY_CATEGORY:ALL:ALL:VASCULAR_ONLY:START:22500:PEAK:23750:END:25000]
[CE_SPECIAL_ATTACK_INTERACTION:INTERACTION:PLAGUE:BP:BY_CATEGORY:TOOTH:START:0:ABRUPT]

The line [CE_SPECIAL_ATTACK_INTERACTION:INTERACTION:BITE_PLAGUE:BP:BY_CATEGORY:MOUTH:BP:BY_CATEGORY:TOOTH:START:0:ABRUPT] allows any infected creature with an attack using mouth or tooth category body parts to immediately spread the disease using said attack. The victim of the attack may then spread the disease if they are able to attack with the needed body part/parts.

{{Category|Modding}}
{{Category|Creature attributes}}
{{Category|Tokens}}
[[ru:DF2012:Syndrome]]

Venom

2020-06-30T22:14:47Z

Albedo: fix links to new page name

{{Quality|Superior|05:09, 17 May 2015 (UTC)}}
{{av}}

'''Venom''' is a naturally-occurring poison that will cause a [[syndrome]] in certain creatures when certain conditions are met, typically when entering the [[blood]] via a [[serpent man]] or [[Giant cave spider|giant cave spider bite]]. It is produced by certain creatures according to their [[raw file]], and may be [[extracts|extracted]] and stored in [[vial]]s.

Each specific animal's venom delivers a [[Syndrome#List of syndromes|specific syndrome]], which is a known combination of [[symptom]]s, some short-term, some long-term, and some (in rare cases) permanent (aka "chronic"). Some few syndromes (such as [[gila monster]]s') are seen as mild annoyances, some (such as a [[giant desert scorpion]]s') are a death sentence, but most are a mortal threat, at least. Of the wide of variety possible symptoms, one of the mildest is [[Symptom#Nausea|nausea]] and vomiting, but even that can dehydrate a dwarf and take them out of combat while they seek to quench their thirst. The most immediately dangerous venoms cause [[Symptom#Paralysis|paralysis]], which can stop the lungs, leading to suffocation. Most any bite that causes strong [[Symptom#Pain|pain]] can in turn cause unconsciousness, leaving the victim helpless in combat, which is rarely survived. Longer term, [[Symptom#Blisters|blisters]] can lead to deadly infections, and [[Symptom#Necrosis|necrosis]] (which causes tissue to die) of any body part can also lead to eventual death, but the usual treatment, amputation, is not much better. Even [[Symptom#Dizziness|mild dizziness]] can be a death sentence to any dwarf who works or travels near magma, water, or long falls (and do any ''not''?). There are few venoms that ''can't'' kill an unlucky dwarf, one way or the other; if your fortress has many venomous creatures nearby, have some [[coffin]]s ready.

Currently, it is disputed whether or not venom can be administered, but it may still be purchased or sold.

Research has shown that in at least some circumstances, venom and other syndrome-inducing materials can be spattered or covered upon weapons and bolts, which may result in attacks inflicting the related syndromes. {{cite forum|106397}}

Some [[forgotten beast]]s and [[titan]]s are generated with venom, which they can inject through bites or stingers, alternatively covering their bodies entirely, or making their [[blood]] toxic.

[[File:venom_snake.jpg|thumb|250px|center|A snake's venom.]]

==See also==
*[[Syndrome]] for a list of various venomous varmints.

{{Translation
| dwarven = zamoth
| elvish = neleni
| goblin = luskon
| human = ámtoc
}}

{{Category|Creature attributes}}
{{Category|Extracts}}
[[ru:Venom]]

Titan

2020-06-30T22:13:21Z

Albedo: fix link to new page name

{{Quality|Exceptional|20:49, 28 April 2013 (UTC)}}
{{av}}
{{minorspoiler}}

[[File:Ozosm-sarasti.jpg|400px|thumb|right|''The Mountain Titan Ozosm has come! A great humanoid composed of native platinum. It has wings and it has a regal bearing. Beware its webs!'' ([http://www.bay12forums.com/smf/index.php?topic=169691.msg7701761#msg7701761 post])]]

'''Titans''' are large, monstrous, procedurally generated [[megabeast]]s that lurk in the surface world, [[path]]ing through to your fort and seeding destruction amongst your [[dwarves]]. They are the above-ground equivalent of [[forgotten beast]]s.

Titans are attracted by [[wealth]] and population size. Additionally, one may randomly appear when you reclaim a fortress. When a titan becomes visible onscreen, the game automatically pauses and displays a message.

== Generation ==
Titans are procedurally randomized - being of any form, and made of any sort of material. Multiple titans may come to attack your fortress, each coming at different times. Most take the form of an animal, some not found in vanilla ''Dwarf Fortress'', with extra features (e.g. extra eyes, feathers) or removed body parts (e.g. skinless cobras) and unusual colours. However, a titan can also take more generic forms, such as shelled blobs, quadrupeds, and humanoid golems. Materials range from flesh and [[blood]], to flimsy things like [[ash]] and [[steam]], to truly scary monsters of pure [[rock]], [[gem]], or [[metal]]. They may get a special attack, ranging from things such as venomous stings, poisoned blood, or explosive dust clouds, to flame breath.

If a titan has a venomous attack of some sort, it is randomly generated, as are the resulting [[symptom]]s including, where applicable, the titan's [[Syndrome#Breath attacks||breath attack]]. Venom attacks come in a variety of forms, from boiling ichor to trailing dust, and the effects can range from mild pain to complete and instantaneous necrosis or paralysis. Some forms of venom can spread from spatters and contact with your dwarves, eventually 'infecting' your entire fort - decontaminating your soldiers in shallow running water is one way to deal with this problem. Some titans breathe [[fire]] or shoot [[web]]s in lieu of any syndrome-bearing attacks. Web-shooters are immune to the effects of webs they, or any other creature, create and will shoot web even at targets they lack a proper path to. Titans based on spiders may be capable of shooting webs in addition to any other special abilities.

Unlike forgotten beasts, the number of titans in a world can be controlled if it is created through the [[advanced world generation]] screen. All are [[building destroyer]]s, and are almost entirely [[Trapavoid|immune]] to [[trap]]s (they are {{token|TRAPAVOID}} and {{token|NOSTUN}} but non-webspinners will trigger a trap that has been webbed). They are also [[No Pain|immune to pain]], nausea and fear, and [[No Exert|feel no exertion]]. [[Bridge]]s are also less useful, as they cannot be raised or lowered as long as the beast is standing on (or under) them, preventing the traditional [[magma]] pit / [[dwarven atom smasher]] designs from working. Unlike forgotten beasts, titans possess unique titles depending on the biome they inhabit - titans living in marshes will be known as marsh titans, titans living in savannas may be known as savanna titans, etc.

The description of some titans are also affected by the alignment of the biome from which they come from, possibly most notable with the recorded examples of titans from good-aligned biomes having descriptions ending with "It emanates an aura of giving and kindness".

== Death and application ==
Unless the player has completely walled themselves out of the surface world, it is not possible to avoid confrontation with a titan when one spawns. Titans are not intelligent creatures and those made of "fleshy" materials can be [[butcher]]ed; due to their massive size, they will leave you with hundreds of [[meat]] and [[bone]] units and dozens of [[prepared organs]]. Titan [[shell]]s may prove valuable during a [[strange mood]], particularly on a map without other sources of shells. Unfortunately, all titans have a [[Item value|value]] multiplier of 1.

Some titans whose bodies are made of liquid, gas, fire, or powder will die or lose limbs on the first hit. Others are extremely difficult to kill due to being made of very hard materials or having an amorphous shape. When confronted with such near-invulnerable creatures the only option is usually to use your brain and try to lock it away somehow. Walls and raised [[bridge|draw bridges]] stop them. Since they are [[building destroyer]]s, you can use installed [[furniture]] to lure them to a particular location. If you can put it in a pit, a clever trapmaker can feed it invaders. If a near-indestructible beast isn't in a position to threaten your dwarves, it can be used to train [[Crossbowman|marksdwarves]].

Due to arriving from the surface, [[cave-in]] traps may not be as efficient against a titan as they are against forgotten beasts unless the player deliberately allows them to enter the fortress. They'll be killed by dropping either natural or constructed walls or floors on them. It is also possible to capture some titans in cage traps by using [[giant cave spider]] webs (or similar). Titans possess a [[pet]] value of 2000, but they cannot be [[Animal trainer|tamed]] due to lacking the necessary tokens.

You can prevent titans from appearing by editing [[d_init.txt]] to change [INVADERS:YES] to [INVADERS:NO], though that will also prevent [[ambush]]es and [[siege]]s, or through setting the number of titans generated to 0 in [[advanced world generation]]

== Titan Threat Analysis==
'''If you do not want your [[fun]] spoiled, do not look below!'''
{{clear|both}}
[[File:Forest_Titan_Size.png|frame|Estimated size comparison between a titan and a dwarf.]]
Titans pose different levels of threat to your fortress, based on their composition, body shape, movements or special attacks. This list also works with forgotten beasts and [[demon]]s.

Of course, general threat must be appraised after all categories. A giant blob made of smoke with webs is still pretty harmless and very fragile, despite it having webs, and a no-frills humanoid made of [[steel]] with no special attack will cause dangerously large amounts of [[fun]], being essentially a far more resilient [[bronze colossus]].

'''Material Composition'''
*''Water, Grime, Filth, Salt, Steam, Smoke, Snow'': Liquids, gasses, and powders are incredibly fragile, and most of them don't do any damage either. In fact, they usually die to [[Cat|kittens]] playfully scratching them or babies punching them. Unless paired with a dangerous attack method, these should not be a threat at all.
*''Fire'': While very fragile, [[fire]] is incredibly !![[fun]]!!. This type of titan will usually stay at the edge of the map and may burn large parts of the grasslands when it first enters. Engagement should be avoided if it does not path to your fortress (and into a trap) as it could cause casualties with fire spread, contact, and fireballs (passive ability). Dropping an unarmed [[goblin]] or two (or a ceiling) on top of it should kill it as it will die as easily as any other gas beast. Upon death, titans made of fire tend to explode in a large fireball which will kill all units within range, so keep your melee fighters away!
*''Flesh'': Most forgotten beasts are fleshy. It's about the standard level of threat for a titan. Invertebrates are generally more fragile than vertebrates due to lack of bones, so it's easier to damage the brain or mangle their body parts.
*''Rock or Mineral'': Quite difficult, but not unbeatable. Can be damaged with metallic weapons. Beasts may be made of native copper or silver ore; see below for those.
*''Glass or Gem'': They are generally pretty tough, though not quite as much as being made of diamond might imply. If you have poorly equipped dwarves, military action is not advised.
*''Non-weapon grade metal'': Similar to rock titans. Most weapons-grade metal can damage it.
*''Copper/Silver'': If you've got a good military and weapons as good as bronze, it should at least be beatable. Don't expect an easy fight by any means, however.
*''Bronze'': If you have encountered a bronze colossus before, this beast should be comparable in how dangerous it is. Whether it is more or less dangerous will depend on various features such as size, body type, whether it can fly, material emissions and whatever syndromes it may possess.
*''Iron'': Are you having [[fun]] yet? Do not send anything against it that has less than steel weapons; it will be pointless. [[Magma]] also does nothing against these.
*''Steel'': While exceedingly rare, these are fortress-ending threats on the level of [[HFS]]. These can be beaten only with cave-in traps, falling traps, obsidian/ice traps or adamantine weapons. Be sure to post <s>how your fortress ended horribly</s> the epic story of your struggle with it on the Bay12 forums!

'''Body Shape'''
*''Blob'': Depends on material - fleshy blobs having only a single body part. All attacks will target it, causing it to accumulate damage rapidly until it explodes into gore.{{verify}} Has only a blunt push attack, which at a titan's size is deadly. However, ''inorganic'' blobs are a whole other story, and ''metal'' blobs are a sign that the game hates your guts.
*''Quadruped, Humanoid'': about the average for a titan. Try and use cutting weapons to cripple them. Or spears.
*''Insect, Spider'': Obnoxious because of the large number of redundant limbs. The large majority of spiders (not "tarantulas", apparently) will be guaranteed to have a webbing attack and should thus be treated with extreme care.

'''Movement'''
*''Walking'': Normal movement. All titans are also amphibious.
*''Flying'': More dangerous than walking, for obvious mobility reasons. Be sure you only have one entry for your fortress.

'''Special attack'''
*''None'': Consider yourself lucky—most forgotten beasts have some kind of [[syndrome]]-based effect. However, certain kinds of beasts have inherent abilities, like fireballs for a beast composed of fire, or webs for a spider-based beast.
*''Noxious Secretions'': Every single part of the creature's body is covered in extract. If it's in liquid or solid form and any of your dwarves touch this extract, they will receive the syndrome effects. Usually not a threat since dwarves are often well clothed, your military even more so. If the secretions are in gas form, treat the titan as if it has a toxic breath attack. Note that, unlike other attacks, gaseous noxious secretions are effective even if the beast is caged.
*''Hunger for warm blood'': When the creature stabs the opponent, some blood will be drawn. Additionally, its ability to detect any creature with blood will let it "see" dwarves through walls and other solid objects.
*''Poisonous bite or sting'': Not dangerous by titan standards.
*''Spitting glob'': Generally not dangerous, unless you forgot shields and shield use on your military for some reason.
*''Fire breath'': By itself not threatening if you have shields and decent shield skill. However, [[fun]] is always where fire is — a burst of flame is quite likely to start a wildfire.
*''Toxic blood, vapor, or gas'': Threat depends on the syndrome's effects - can be harmless or kill your entire military. You may want to sacrifice something to see what the titan extract does.
*''Webs'': Webs are incredibly deadly in melee, but do not help much in range. It will slaughter your whole melee squad with incredible ease, but not your ranged squad as long as the ranged squad is out of reach. Engage it with marksdwarves or kill it with a cunning trap.
*''Deadly dust'': Possibly the most [[fun]] attack a titan can come with. Deadly dust acts like [[cave-in]] dust with syndromes. Dust coming from all directions (as opposed to a breath attack) is even more fun. If the material of the titan is weak (like flesh), or if it has articulations or organs to be damaged, it will harm itself with its own deadly dust. However if it is made of stronger material, it will be immune to this effect. Deadly dust is generally a very effective defense against melee and marksdwarves, but is a liability if the titan is fleshy and not a blob.

===Applications===
Titans can be put to various uses if correctly managed. See [[Forgotten beast#Applications|here]] for more information.

==Adventure Mode==
Titans can be encountered in [[adventure mode]] and are considered "beasts" for the purposes of asking about troubles. They are common targets for quests and reside in [[shrine (megabeast)|shrine]]s.

Titans are relatively easy to defeat in adventure mode, at least as far as supernatural creatures go. Though they are gigantic, they have two major weaknesses: they are unintelligent, and so possess no observer skill; and they live in shrines, surrounded by pillars, which make excellent cover for a stealthed adventurer. It is therefore quite possible to sneak up behind a titan and slay it, without it ever noticing that you're there.

This strategy should not be attempted on titans which are naturally without eyes, or which possess a hunger for warm blood, as these have omnidirectional {{token|EXTRAVISION}}.

{{Creatures}}
{{Category|Building destroyer}}
{{Category|Megabeasts}}
{{Category|No Exert}}
{{Category|No Pain}}
{{Category|No Stun}}
{{Category|Flying}}
{{Category|Shell}}
{{Category|Syndrome}}
{{Category|Trapavoid}}
{{Category|Webs}}
[[ru:Titan]]

Forgotten beast

2020-06-30T22:12:52Z

Albedo: fix link to new page name

{{Quality|Exceptional|21:18, 30 September 2016 (UTC)}}
{{av}}
{{minorspoiler}}
{{random image|location=right|size=300px}}

:''In the deep, there are beasts so fell and terrible, that only they know what they are, for none who have met them have lived to tell of it... they are the Forgotten Beasts, born of the chaos from before the world's birth... they have waited, brooding in the dark places of the world... and now... by digging too deep... we have awakened them.''

'''Forgotten beasts''' are large, monstrous, procedurally generated [[megabeast]]s that spawn in the [[caverns]] beneath your fortress, [[path]]ing through to your fort and seeding destruction amongst your [[dwarves]]. They are the subterranean equivalent of [[titan]]s.

Forgotten beasts are attracted by [[wealth]] and population size. Additionally, one may randomly appear when you reclaim a fortress. When a forgotten beast becomes visible onscreen, the game automatically pauses and displays a message.

== Generation ==
Forgotten beasts are procedurally randomized, and may be of any form, and be made of any sort of material. Multiple forgotten beasts may come to attack your fortress, each coming at different times. Most take the form of an animal, some not found in vanilla DF, with extra features (e.g. extra eyes, feathers) or removed body parts (e.g. skinless cobras) and unusual colours. However, a forgotten beast can also take more generic forms, such as shelled blobs, quadrupeds, and humanoid golems. Materials range from flesh and blood, to flimsy things like [[ash]] and [[steam]], to truly scary monsters of pure [[rock]], [[gem]], or [[metal]]. They may get a special attack, ranging from anything between venomous stings, poisoned blood, explosive dust clouds, to flame breath. Some forgotten beasts have "hunger for warm blood", which lets them notice all warm-blooded creatures.

If a forgotten beast has a venomous attack of some sort, it is randomly generated as are the resulting [[symptom]]s. The beast's [[Syndrome#Breath_attacks|breath attack]] is also randomly generated, if it has one. Venom attacks come in a variety of forms, from boiling ichor to trailing dust, and the effects can range from mild pain to complete and instantaneous necrosis or paralysis. Some forms of venom can spread from spatters and contact with your dwarves, eventually infecting your entire fort. Decontaminating your soldiers in shallow running water is one way to deal with this problem. Some beasts breathe fire or shoot [[web]] in lieu of any syndrome-bearing attacks. Web-shooters are immune to the effects of webs they, or any other creature, create and will shoot web even at targets they lack a proper path to. Forgotten beasts based on spiders may be capable of shooting webs in addition to any other special abilities.

The number of forgotten beasts cannot be controlled directly, but is influenced by the size of the world and is directly proportional to the number of cavern layers, as exactly one beast is spawned per each underground region. All are [[building destroyer]]s, and are almost entirely immune to [[trap]]s (they are trapavoid and nostun but non-webspinners will trigger a trap that has been webbed). [[Bridge]]s are also less useful, as they cannot be raised or lowered as long as the beast is standing on (or under) them, preventing the traditional [[magma]] pit / [[dwarven atom smasher]] designs from working. This is probably one of [[Main:Toady One|Toady One]]'s ways of making the encounters even more [[fun]].

[[Image:DF2010ForgottenBeast1.png|thumb|center|500px]]

== Death and application ==
{{random image|location=right|size=300px}}
If you need to kill a forgotten beast, order your military to attack. Some beasts, however, are content not to path to your fortress and will stay dormant underground. Most "fleshy" forgotten beasts can be butchered; some are quite massive and may leave you with hundreds of meat and bone units and dozens of prepared organ units. Forgotten beast [[shell]]s may prove valuable during a [[strange mood]], particularly on a map without other sources of shells. Unfortunately, all forgotten beasts have a value multiplier of 1.

Some forgotten beasts whose bodies are made of liquid, gas, fire, or powder will die or lose limbs on the first hit. Other forgotten beasts are extremely difficult to kill due to being made of very hard materials or having an amorphous shape. When confronted with such near-invulnerable creatures the only option is usually to use your brain and try to lock it away (the beast; dwarven brains are locked away by default) somehow. Walls and raised [[bridge|draw bridges]] stop them. Since they are [[building destroyer]]s, you can use installed [[furniture]] to lure them to a particular location. If you can put it in a pit, a clever trapmaker can feed it invaders. If a near-indestructible beast isn't in a position to threaten your dwarves, it can be used to train marksdwarves.

One method of defeating nearly combat-invulnerable forgotten beasts (those whose bodies are made of rock, for instance) is to cause a [[Cave-in]] on top of them. They'll be killed by dropping either natural or constructed walls or floors on them. It is also possible to capture some forgotten beasts in cage traps by using [[giant cave spider]] webs (or similar).

You can prevent forgotten beasts from appearing by editing [[d_init.txt]] to change [INVADERS:YES] to [INVADERS:NO], though that will also prevent [[ambush]]es and [[siege]]s.

== Forgotten Beast Threat Analysis==
'''If you do not want your [[fun]] spoiled, do not look below!'''

{{clear|both}}

Forgotten beasts pose different levels of threat to your fortress, based on their composition, body shape, movements or special attacks. This list also works with [[titan]]s and [[demon]]s.

Of course, general threat must be appraised after all categories. A giant blob made of smoke with webs is still pretty harmless and very fragile, despite it having webs, and a no-frills humanoid made of steel with no special attack will cause dangerously large amounts of [[fun]], being essentially a far more resilient bronze colossus.

'''Material Composition'''
*''Water, Grime, Filth, Salt, Steam, Smoke, Snow'': Liquids, gasses, and powders are incredibly fragile, and most of them don't do any damage either. In fact, they usually die to kittens playfully scratching them or babies punching them. Unless paired with a dangerous attack method, these should not be a threat at all.
*''Fire'': While very fragile, [[fire]] is incredibly !![[fun]]!!. This type of forgotten beast will usually stay at the edge of the map and may burn large parts of the cavern when it first enters. Engagement should be avoided if it does not path to your fortress (and into a trap) as it could cause casualties with fire spread, contact, and fireballs (passive ability). Dropping an unarmed goblin or two (or a ceiling) on top of it should kill it as it will die as easily as any other gas beast. Upon death, beasts made of fire tend to explode in a large fireball which will kill all units within range, so keep your melee fighters away!
*''Flesh'': Most forgotten beasts are fleshy. It's about the standard level of threat for a forgotten beast. Invertebrates are generally more fragile than vertebrates, due to lack of bones.
*''Rock or Mineral'': Quite difficult, but not unbeatable. Can be damaged with metallic weapons. Beasts may be made of native copper or silver ore; see below for those.
*''Glass or Gem'': They are generally pretty tough, though not quite as much as being made of diamond might imply. If you have poorly equipped dwarves, military action is not advised.
*''Non-weapon grade metal'': Similar to rock forgotten beasts. Most weapons-grade metal can damage it.
*''Copper/Silver'': If you've got a good military and weapons as good as bronze, it should at least be beatable. Don't expect an easy fight by any means, however.
*''Bronze'': If you have encountered a [[bronze colossus]] before, this beast should be comparable in how dangerous it is. Whether it is more or less dangerous will depend on various features such as size, body type, whether it can fly, material emissions and whatever syndromes it may possess.
*''Iron'': Are you having [[fun]] yet? Do not send anything against it that has less than steel weapons; it will be pointless. Magma also does nothing against these.
*''Steel'': While exceedingly rare, these are fortress-ending threats on the level of [[HFS]]. These can be beaten only with cave-in traps, falling traps, obsidian/ice traps or adamantine weapons. Be sure to post <s>how your fortress ended horribly</s> the epic story of your struggle with it on the Bay12 forums !

'''Body Shape'''
[[File:Forgotten_Beast_Size.png|frame|Estimated size comparison between a forgotten beast and a dwarf.]]
*''Blob'': Depends on material - fleshy blobs having only a single body part. All attacks will target it, causing it to accumulate damage rapidly until it explodes into gore.{{verify}} Has only a blunt push attack, which at an FB's size is deadly. However, ''inorganic'' blobs are a whole other story, and ''metal'' blobs are a sign that the game hates your guts.
*''Worm, Slug, Nematode'': Quite slow, and have one huge body part with internal organs (including brain) easily reachable. Unless paired with some dangerous special attack, these should be easy.
*''Quadruped, Humanoid'': about the average for FBs. Try and use cutting weapons to cripple them. Or spears.
*''Insect, Spider'': Obnoxious because of the large number of redundant limbs. The large majority of spiders (not "tarantulas", apparently) will be guaranteed to have a webbing attack and should thus be treated with extreme care.

'''Movement'''
*''Walking'': Normal movement. All FBs are also amphibious.
*''Flying'': More dangerous than walking, for obvious mobility reasons. Be sure you only have one entry for your caverns.

'''Special attack'''
*''None'': Consider yourself lucky—most forgotten beasts have some kind of [[syndrome]]-based effect. However, certain kinds of beasts have inherent abilities, like fire balls for a beast composed of fire, or webs for a spider-based beast.
*''Noxious Secretions'': Every single part of the creature's body is covered in extract. If it's in liquid or solid form and any of your dwarves touch this extract, they will receive the syndrome effects. Curiously enough, [[biter|biting]] does not qualify as touching. Usually not a threat since dwarves are often well clothed, your military even more so. If the secretions are in gas form, treat the FB as if it has a toxic breath attack. Note that, unlike other attacks, gaseous noxious secretions are effective even if the beast is [[cage]]d.
*''Hunger for warm blood'': When the creature stabs the opponent, some blood will be drawn. Additionally, its ability to detect any creature with blood will let it "see" dwarves through walls and other solid objects.
*''Poisonous bite or sting'': Not dangerous by FB standards.
*''Spitting glob'': Generally not dangerous, unless you forgot shields and shield use on your military for some reason.
*''Fire breath'': By itself not threatening if you have shields and decent shield skill. However, [[Fun]] is always where fire is—a burst of flame is quite likely to start a cavern wildfire. Amusingly, fire-breathing organic FBs are not immune to fire and may even burn themselves to death, though this usually takes some time.
*''Toxic blood, vapor, or gas'': Threat depends of the syndrome's effects. Can be harmless or kill your entire military. You may want to sacrifice something for seeing what the FB's extract does.
*''Webs'': Webs are incredibly deadly in melee, but do not help much at range. It will slaughter your whole melee squad with incredible ease, but not your ranged squad as long as the ranged squad is out of reach. Engage it with marksdwarves or kill it with a cunning trap.
*''Deadly dust'': Possibly the most [[fun]] attack a FB can come with. Deadly dust acts like [[cave-in]] dust with syndromes. Dust coming from all directions (as opposed to a breath attack) is even more [[fun]]. If the material of the FB is weak (like flesh), or if it has articulations or organs to be damaged, it will harm itself with its own deadly dust. However if it is made of stronger material, it will be immune to this effect. Deadly dust is generally a very effective defense against melee and marksdwarves, but is a liability if the FB is fleshy and not a blob.

==Applications==
Forgotten beasts are hard to catch, being both [[Creature token#T|[TRAPAVOID]]] and [[Creature token#N|[NOSTUN]]]; however trapping them is not impossible. All webbed creatures become vulnerable to [[trap]]s, except for the ones that have a [[web]]bing attack of their own: having a [[giant cave spider]] shoot web on your cage traps will render them into perfect FB-proof nets. Your new prizes can be put to various uses; the most obvious ones consist in dropping them onto various invaders - forgotten beasts are hostile toward each other and will attack any [[Surroundings|wildlife]] or [[Civilization|civilized]] creature they may encounter - but with careful micromanagement, the opportunities are limitless.

===Silk farm===
Web-shooting forgotten beasts are notoriously hard to catch and you'll only get your hands on one of these through ''very'' careful micromanagement, such as building a 'trap room' with retractable bridges and some random animal at the center to attract the beast. The set-up is otherwise the same as that of a [[silk farm]], except that forgotten beast silk is only as valuable as mere [[cave spider]] silk. Note that some beasts have special attacks ''in addition'' to their web-shooting ability (in the case of beasts based on spider-like anatomy resembling that of the [[giant cave spider]]), which may make them more difficult to capture and use (as they may kill their targets rather than simply covering them with webs).

===Weapon coating===

[http://www.bay12forums.com/smf/index.php?topic=91084 Syndrome-bearing poison can and will affect any creature it can spread to and infect.] While there is no formal job or workshop related to poison coating in vanilla DF (although it does exist in some [http://dwarffortresswiki.org/index.php/Masterwork:Main_Page mods]), poisoning your weapons is still possible thanks to the impossibly infinite metabolism of your caged guests. Pit them in a similar set-up to that of a [[silk farm]] (you may want to set up a pit from above the farm so you can regularly replace the bait used for the silk farm, or just use a syndrome-immune creature, e.g. a [[zombie]]) and put your weapons (and ammo) stockpiles in the farm so your beast will shoot syndrome-inducing dust/spittle on them. '''Make sure your military dwarves wear gloves when they equip your newly poisoned weapons,''' unless you actually want them to vomit or rot themselves in the middle of the battlefield. You also want them to wear cloaks so they don't contaminate each other while sparring. Some poisons can be '''extremely fun'''; dwarves equipped with poisoned weapons can one-shot most creatures - well, most creatures with functioning organs, at least - through the infliction of superficial wounds. If you can prevent your dwarves from infecting themselves, that is.

===Getting rid of cavern creatures===

Forgotten beasts will actively seek and attack any other [[creature]]s, including cavern wildlife. Sealing the FB in a cavern will make it continuously kill wild inhabitants of the cavern, as these keep coming until their local populations are extinct. You can later obtain a decent supply of [[bone]]s from the skeletons of the creatures the FB killed, when the beast accidentally dies or after you manage to deal with it.

==[http://www.reddit.com/r/dwarffortress/comments/19083j/what_makes_forgotten_beasts_forgotten/c8jlvg7 On The Origins of Forgotten Beasts] ==

{{D for Dwarf}}

In the time before time, when Armok himself was not part of the great machine beast framework, the idea itself of ALL-dom, dwarf dom, elf dom, tools and valueless, remained in the greater unknowable realm of hard possibility called <HARDDISKSPACE>; all was concept data idiosyncratic.

Thence came the being of the <flesh machine> and the <machine beast framework> and thence Armok was, is, and ever will be.

Armok hands moved, and invoked the commands of the ur-<plane/realm?>, and raised the possibility of all worlds that can be, of the-blessed-who-can-know-Armok.

Thence Armok exhaled his vaporous breath and said "CREATE NEW WORLD" and the <machine beast framework> began his dire task.

Legions of empires, battalions of timelines, and civilizations of worlds were born, lost, and discarded, as the will of Armok angered in wait.

Finally World Acceptance was allowed.

Yet, the <Flesh Machine Beast Framework> has failed Armok. For Armok knows of the world behind the worlds, of the '''Intent''' of his dimension, of the destination of the unmoving stone.

He knows that the beasts of <null result un-parseable>, those ideas from the time before the rules, exist not.

The Pen-Factor of Armok, the Toady One, foresaw this failure. He knew that the Armok transcended the very power of the universe vessel, the <Machine Beast Framework>, and to please our god, to let him revel in the glory that is the knowing of himself, he forced the existence of the beasts...

== Bugs ==
* If a beast has a dust attack, the dust will behave like it was from a [[cave-in]], flinging dwarves away (causing further damage if they hit a wall) and knocking them out. {{Bug|3133}}
* forgotten beasts will hide in trees in an attempt to ambush dwarves and woodcutters without ever coming down.

==Art==
View a [[Forgotten beast/gallery|gallery]] of artwork from the [http://www.bay12forums.com/smf/index.php?topic=124312.0 forums].

{{random image|location=left|size=600px}}
{{clear}}
{{Creatures}}
{{Category|Megabeasts}}
{{Category|Trapavoid}}
{{Category|Building destroyer}}
{{Category|No Stun}}
{{Category|Flying}}
{{Category|Syndrome}}
{{Category|Webs}}
{{Category|Shell}}
[[ru:DF2012:Forgotten beast]]

Animal person

2020-06-30T22:12:27Z

Albedo: fix link to new page name

{{Quality|Exceptional|21:25, 2 July 2013 (UTC)}}
{{av}}

'''Animal people''' are half-man, half-beast [[creature]]s with various animal-like traits (such as [[flying]], [[steals items|thievery]], and [[syndrome|poisons]]), inherited from their base animal. They generally have significantly longer [[age|lifespans]] than their base animals, as well as the ability to [[learns|learn]]. They can be legless but get arms even if their base animal is limbless. Their body size is the average of their base animal's size and 70,000 (the size of a [[human]]). This works out so that the smallest animal people are 35,000cm³, half the size of a [[human]], but they can get [[sperm whale man|very large]]. Animal people can join [[civilization]]s and live in [[site]]s. They can also come to your fort as [[visitor]]s.

Animal people are playable creatures in [[adventure mode]]. If they became established members of a playable civ (dwarf, elf, human), they will appear listed in the creature selection screen alongside the main races. Otherwise, they are selectable under {{DFtext|Intelligent Wilderness Creature|7:0}}. Some animal people may not be available due to having [[extinction|died out]] or being uncontacted (e.g. excluded to an isolated island).

Wild animal people wander on the surface in [[savage]] environments or dwell underground in the [[cavern]]s; these two populations form distinct groups. Subterranean animal people are actually a civilization in themselves, rarely encountered, in small groups or "tribes". They are equipped with primitive weaponry such as wooden [[spear]]s and [[blowgun]]s (they are the only known source of [[blowdart]]s). Subterranean animal people will be labeled as {{DFtext|Hostile|4:0}} upon discovery. They are not interested in negotiations and will attack your dwarves on sight. Encountering them often comes as a surprise, since there is no way to know about their presence before embarking. They do not appear in the {{k|c}}ivilizations [[menu]].

Subterranean animal people are also found in generated [[sewer]]s, formed from a collection of outcasts.

== Subterranean animal people ==

* {{Tile|a|6:0}} [[Amphibian man]]
* {{Tile|a|0:1}} [[Antman]]
* {{Tile|b|0:1}} [[Bat man]]
* {{Tile|f|7:1}} [[Cave fish man]]
* {{Tile|s|0:1}} [[Cave swallow man]]
* {{Tile|o|7:1}} [[Olm man]]
* {{Tile|r|2:0}} [[Reptile man]]
* {{Tile|r|0:1}} [[Rodent man]]
* {{Tile|s|7:1}} [[Serpent man]]

=== Ethics ===

Being an entity in their own right, subterranean animal people possess ethics much like other civs. Those particular ethics are incomplete for now — being directly copied from [[kobold]]s and their [[personality trait|values]] all set to zero (none).

Like kobolds, subterranean animal people consider the killing of other living beings acceptable, but treason is unthinkable, and they'll respond to the murder of their own kind by exiling the offender from their tribe. They oppose torturing for information and the torture of animals, but consider torturing for fun appropriate. Assault is considered a personal matter, while slavery, the taking of animal trophies, and the consumption of sapient beings (which includes other animal people) are all unthinkable acts.

== Other animal people ==

{| {{prettytable}}
|-
|-
|| {{Tile|a|7:0}} [[Aardvark man]]
|| {{Tile|a|6:0}} [[Adder man]]
|| {{Tile|a|7:1}} [[Albatross man]]
|-
|| {{Tile|A|2:0}} [[Alligator man]]
|| {{Tile|A|2:1}} [[Anaconda man]]
|| {{Tile|a|2:1}} [[Anole man]]
|-
|| {{Tile|a|7:0}} [[Armadillo man]]
|| {{Tile|a|5:0}} [[Axolotl man]]
|| {{Tile|a|7:0}} [[Aye-aye man]]
|-
|| {{Tile|b|7:0}} [[Badger man]]
|| {{Tile|s|6:1}} [[Bark scorpion man]]
|| {{Tile|b|6:0}} [[Barn owl man]]
|-
|| {{Tile|b|6:0}} [[Beaver man]]
|| {{Tile|b|4:0}} [[Beetle man]]
|| {{Tile|B|0:1}} [[Black bear man]]
|-
|| {{Tile|s|0:1}} [[Black mamba man]]
|| {{Tile|b|1:1}} [[Bluejay man]]
|| {{Tile|b|6:0}} [[Bobcat man]]
|-
|| {{Tile|s|6:0}} [[Brown recluse spider man]]
|| {{Tile|s|6:0}} [[Bushmaster man]]
|| {{Tile|b|6:0}} [[Bushtit man]]
|-
|| {{Tile|b|0:1}} [[Buzzard man]]
|| {{Tile|c|7:1}} [[Capuchin man]]
|| {{Tile|c|6:0}} [[Capybara man]]
|-
|| {{Tile|c|4:1}} [[Cardinal man]]
|| {{Tile|c|0:1}} [[Cassowary man]]
|| {{Tile|c|2:1}} [[Chameleon man]]
|-
|| {{Tile|c|6:1}} [[Cheetah man]]
|| {{Tile|c|7:0}} [[Chinchilla man]]
|| {{Tile|c|6:0}} [[Chipmunk man]]
|-
|| {{Tile|c|6:0}} [[Coati man]]
|| {{Tile|c|7:1}} [[Cockatiel man]]
|| {{Tile|s|6:0}} [[Copperhead snake man]]
|-
|| {{Tile|c|6:0}} [[Cougar man]]
|| {{Tile|c|7:0}} [[Coyote man]]
|| {{Tile|c|4:1}} [[Crab man]]
|-
|| {{Tile|c|0:1}} [[Crow man]]
|| {{Tile|c|6:0}} [[Cuttlefish man]]
|| {{Tile|d|3:1}} [[Damselfly man]]
|-
|| {{Tile|d|6:0}} [[Deer man]]
|| {{Tile|t|6:0}} [[Desert tortoise man]]
|| {{Tile|d|6:1}} [[Dingo man]]
|-
|| {{Tile|d|3:1}} [[Dragonfly man]]
|| {{Tile|e|6:0}} [[Eagle man]]
|| {{Tile|e|6:0}} [[Echidna man]]
|-
|| {{Tile|E|7:0}} [[Elephant man]]
|| {{Tile|S|6:0}} [[Elephant seal man]]
|| {{Tile|E|6:0}} [[Elk man]]
|-
|| {{Tile|E|6:0}} [[Emu man]]
|| {{Tile|f|2:1}} [[Firefly man]]
|| {{Tile|f|0:1}} [[Fly man]]
|-
|| {{Tile|f|6:0}} [[Flying squirrel man]]
|| {{Tile|f|4:0}} [[Fox man]]
|| {{Tile|g|6:0}} [[Gazelle man]]
|-
|| {{Tile|T|6:0}} [[Giant tortoise man]]
|| {{Tile|g|4:1}} [[Gila monster man]]
|| {{Tile|G|6:0}} [[Giraffe man]]
|-
|| {{Tile|g|0:1}} [[Grackle man]]
|| {{Tile|g|2:1}} [[Grasshopper man]]
|| {{Tile|l|7:0}} [[Gray langur man]]
|-
|| {{Tile|s|7:0}} [[Gray squirrel man]]
|| {{Tile|o|7:0}} [[Great horned owl man]]
|| {{Tile|f|2:1}} [[Green tree frog man]]
|-
|| {{Tile|p|7:0}} [[Grey parrot man]]
|| {{Tile|B|6:0}} [[Grizzly bear man]]
|| {{Tile|g|6:0}} [[Groundhog man]]
|-
|| {{Tile|h|7:0}} [[Hamster man]]
|| {{Tile|h|6:0}} [[Hare man]]
|| {{Tile|h|7:0}} [[Harp seal man]]
|-
|| {{Tile|h|6:0}} [[Hedgehog man]]
|| {{Tile|H|7:0}} [[Hippo man]]
|| {{Tile|m|7:0}} [[Hoary marmot man]]
|-
|| {{Tile|b|7:1}} [[Honey badger man]]
|| {{Tile|h|0:1}} [[Hornbill man]]
|| {{Tile|h|6:0}} [[Horseshoe crab man]]
|-
|| {{Tile|h|6:0}} [[Hyena man]]
|| {{Tile|i|6:0}} [[Ibex man]]
|| {{Tile|i|2:1}} [[Iguana man]]
|-
|| {{Tile|i|6:0}} [[Impala man]]
|| {{Tile|j|6:0}} [[Jackal man]]
|| {{Tile|J|6:1}} [[Jaguar man]]
|-
|| {{Tile|s|0:1}} [[Jumping spider man]]
|| {{Tile|k|2:0}} [[Kakapo man]]
|| {{Tile|K|6:0}} [[Kangaroo man]]
|-
|| {{Tile|k|2:0}} [[Kea man]]
|| {{Tile|k|4:0}} [[Kestrel man]]
|| {{Tile|k|0:1}} [[King cobra man]]
|-
|| {{Tile|k|7:1}} [[Kingsnake man]]
|| {{Tile|k|6:0}} [[Kiwi man]]
|| {{Tile|k|7:0}} [[Koala man]]
|-
|| {{Tile|l|0:1}} [[Leech man]]
|| {{Tile|g|6:1}} [[Leopard gecko man]]
|| {{Tile|l|6:1}} [[Leopard man]]
|-
|| {{Tile|L|0:1}} [[Leopard seal man]]
|| {{Tile|L|6:1}} [[Lion man]]
|| {{Tile|l|6:1}} [[Lion tamarin man]]
|-
|| {{Tile|l|6:0}} [[Lizard man]]
|| {{Tile|l|0:1}} [[Loon man]]
|| {{Tile|l|4:1}} [[Lorikeet man]]
|-
|| {{Tile|l|6:0}} [[Louse man]]
|| {{Tile|l|6:0}} [[Lynx man]]
|| {{Tile|m|0:1}} [[Magpie man]]
|-
|| {{Tile|m|1:1}} [[Mandrill man]]
|| {{Tile|m|2:1}} [[Mantis man]]
|| {{Tile|l|2:1}} [[Masked lovebird man]]
|-
|| {{Tile|m|6:0}} [[Mink man]]
|| {{Tile|b|4:1}} [[Monarch butterfly man]]
|| {{Tile|m|7:0}} [[Mongoose man]]
|-
|| {{Tile|M|6:0}} [[Monitor lizard man]]
|| {{Tile|s|4:1}} [[Moon snail man]]
|| {{Tile|M|6:0}} [[Moose man]]
|-
|| {{Tile|m|0:1}} [[Mosquito man]]
|| {{Tile|m|6:0}} [[Moth man]]
|| {{Tile|g|7:1}} [[Mountain goat man]]
|-
|| {{Tile|M|6:0}} [[Muskox man]]
|| {{Tile|N|7:0}} [[Narwhal man]]
|| {{Tile|n|4:1}} [[Nautilus man]]
|-
|| {{Tile|o|6:1}} [[Ocelot man]]
|| {{Tile|o|7:0}} [[Octopus man]]
|| {{Tile|C|6:0}} [[One-humped camel man]]
|-
|| {{Tile|o|7:0}} [[Opossum man]]
|| {{Tile|O|0:1}} [[Orca man]]
|| {{Tile|o|6:1}} [[Oriole man]]
|-
|| {{Tile|o|7:1}} [[Osprey man]]
|| {{Tile|O|0:1}} [[Ostrich man]]
|| {{Tile|o|6:0}} [[Otter man]]
|-
|| {{Tile|P|7:1}} [[Panda man]]
|| {{Tile|p|6:0}} [[Pangolin man]]
|| {{Tile|p|2:1}} [[Parakeet man]]
|-
|| {{Tile|l|2:1}} [[Peach-faced lovebird man]]
|| {{Tile|p|7:1}} [[Penguin man]]
|| {{Tile|p|6:0}} [[Peregrine falcon man]]
|-
|| {{Tile|p|6:0}} [[Platypus man]]
|| {{Tile|B|7:1}} [[Polar bear man]]
|| {{Tile|t|2:0}} [[Pond turtle man]]
|-
|| {{Tile|p|6:0}} [[Porcupine man]]
|| {{Tile|p|0:1}} [[Puffin man]]
|| {{Tile|S|6:0}} [[Python man]]
|-
|| {{Tile|r|7:0}} [[Raccoon man]]
|| {{Tile|r|0:1}} [[Rat man]]
|| {{Tile|s|7:0}} [[Rattlesnake man]]
|-
|| {{Tile|r|0:1}} [[Raven man]]
|| {{Tile|r|4:0}} [[Red panda man]]
|| {{Tile|r|6:0}} [[Red squirrel man]]
|-
|| {{Tile|r|0:1}} [[Red-winged blackbird man]]
|| {{Tile|m|7:0}} [[Rhesus macaque man]]
|| {{Tile|R|7:0}} [[Rhinoceros man]]
|-
|| {{Tile|r|6:0}} [[Roach man]]
|| {{Tile|C|2:0}} [[Saltwater crocodile man]]
|| {{Tile|s|7:0}} [[Skink man]]
|-
|| {{Tile|s|0:1}} [[Skunk man]]
|| {{Tile|B|0:1}} [[Sloth bear man]]
|| {{Tile|s|7:0}} [[Sloth man]]
|-
|| {{Tile|s|6:0}} [[Slug man]]
|| {{Tile|s|7:0}} [[Snail man]]
|| {{Tile|t|2:0}} [[Snapping turtle man]]
|-
|| {{Tile|o|7:1}} [[Snowy owl man]]
|| {{Tile|s|6:0}} [[Sparrow man]]
|| {{Tile|W|7:0}} [[Sperm whale man]]
|-
|| {{Tile|m|0:1}} [[Spider monkey man]]
|| {{Tile|s|4:1}} [[Sponge man]]
|| {{Tile|s|7:1}} [[Squid man]]
|-
|| {{Tile|s|6:0}} [[Stoat man]]
|| {{Tile|s|7:1}} [[Swan man]]
|| {{Tile|T|7:1}} [[Tapir man]]
|-
|| {{Tile|t|6:0}} [[Thrips man]]
|| {{Tile|t|0:1}} [[Tick man]]
|| {{Tile|T|6:1}} [[Tiger man]]
|-
|| {{Tile|t|2:0}} [[Toad man]]
|| {{Tile|C|6:0}} [[Two-humped camel man]]
|| {{Tile|v|4:0}} [[Vulture man]]
|-
|| {{Tile|W|6:0}} [[Walrus man]]
|| {{Tile|W|6:0}} [[Warthog man]]
|| {{Tile|w|6:0}} [[Weasel man]]
|-
|| {{Tile|s|7:1}} [[White stork man]]
|| {{Tile|B|6:0}} [[Wild boar man]]
|| {{Tile|w|7:0}} [[Wolf man]]
|-
|| {{Tile|w|6:0}} [[Wolverine man]]
|| {{Tile|w|6:0}} [[Wombat man]]
|| {{Tile|w|7:0}} [[Worm man]]
|-
|| {{Tile|w|6:0}} [[Wren man]]

|}

== Animal people organized by Attributes==

@ Probably only functions as a citizen in Fortress Mode (Needs Testing/Verification)

+ Probably only functions in Adventure Mode (Needs Testing/Verification)

(#) Probably only functions for procedurally generated "mob spawns" and not for adventurers (Needs Testing/Verification)

{| {{prettytable}}
! Attribute !! Effect !! Species of Animal Person
|-
| '''[[Amphibious]]''' || Move and breathe normally on water AND dry land || [[Alligator man]] | [[Axolotl man]] | [[Capybara man]] | [[Crab man]] | [[Elephant seal man]] | [[Gila monster man]] | [[Green tree frog man]] | [[Harp seal man]] | [[Hippo man]] | [[Horseshoe crab man]] | [[Leopard seal man]] | [[Olm man]] | [[Otter man]] | [[Platypus man]] | [[Pond turtle man]] | [[Reptile man]] | [[Saltwater crocodile man]] | [[Snapping turtle man]] | [[Toad man]] | [[Walrus man]]
|-
| '''[[Aquatic]]''' || Move and breathe normally in water, but drown in less than 4/7 units of water. || | [[Cuttlefish man]] | [[Moon snail man]] | [[Narwhal man]] | [[Nautilus man]] | [[Octopus man]] | [[Orca man]] | [[Sperm whale man]] | [[Sponge man]] | [[Squid man]]
|-
| '''[[egg|Egglaying]]@''' || Females will lay (sterile) eggs if given a nest box to claim || | Assumedly all species of egglaying birds
|-
| '''[[Flying]]+(bugged)''' || Can fly through the air || | [[Albatross man]] | [[Barn owl man]] | [[Bluejay man]] | [[Bushtit man]] | [[Buzzard man]] | [[Cardinal man]] | [[Crow man]] | [[Damselfly man]] | [[Dragonfly man]] | [[Eagle man]] | [[Firefly man]] | [[Fly man]] | [[Grackle man]] | [[Great horned owl man]] | [[Grey parrot man]] | [[Hornbill man]] | [[Kea man]] | [[Kestrel man]] | [[Loon man]] | [[Lorikeet man]] | [[Magpie man]] | [[Mantis man]] | [[Masked lovebird man]] | [[Monarch butterfly man]] | [[Mosquito man]] | [[Moth man]] | [[Oriole man]] | [[Osprey man]] | [[Parakeet man]] | [[Peach-faced lovebird man]] | [[Peregrine falcon man]] | [[Puffin man]] | [[Raven man]] | [[Red-winged blackbird man]] | [[Roach man]] | [[Snowy owl man]] | [[Sparrow man]] | [[Swan man]] | [[Thrips man]] | [[Vulture man]] | [[Wren man]]
|-
| '''[[Genderless]]''' || Cannot breed in normal gameplay || | [[Leech man]] | [[Slug man]] | [[Snail man]] | [[Sponge man]] | [[Worm man]]
|-
| '''[[No Pain]]''' || Feels no pain || | [[Bark scorpion man]] | [[Brown recluse spider man]] | [[Jumping spider man]]
|-
| '''[[No Stun]]''' || Cannot be stunned || | [[Bark scorpion man]] | [[Brown recluse spider man]] | [[Jumping spider man]]
|-
| '''[[Shell]]''' || Has a shell that can be yielded if butchered, however, dwarves won't butcher animal people in non-modded DF. || | [[Armadillo man]] | [[Desert tortoise man]] | [[Giant tortoise man]] | [[Moon snail man]] | [[Nautilus man]] | [[Pond turtle man]] | [[Snail man]] | [[Snapping turtle man]]
|-
| '''[[Steals drink]](#)''' || Approaches any available drink and steals it. Guzzles entire barrels at once, on the spot. || | [[Black bear man]] | [[Grizzly bear man]] | [[Polar bear man]] | [[Sloth bear man]]
|-
| '''[[Steals food]](#)''' || Approaches any available drink and steals it, carrying a stack of food off-map. || | [[Black bear man]] | [[Buzzard man]] | [[Capuchin man]] | [[Coati man]] | [[Gray langur man]] | [[Grizzly bear man]] | [[Honey badger man]] | [[Kea man]] | [[Mandrill man]] | [[Polar bear man]] | [[Raccoon man]] | [[Rhesus macaque man]] | [[Sloth bear man]] | [[Vulture man]]
|-
| '''[[Steals items]](#)''' || Approaches an item and steals it, carrying it off-map. || | [[Capuchin man]] | [[Coati man]] | [[Gray langur man]] | [[Kea man]] | [[Mandrill man]] | [[Raccoon man]] | [[Rhesus macaque man]]
|-
| '''[[Syndrome]]''' || Venoms that cause various [[symptom]]s, usually applied by bite or a special sting attack || | [[Adder man]] | [[Bark scorpion man]] | [[Black mamba man]] | [[Brown recluse spider man]] | [[Bushmaster man]] | [[Copperhead snake man]] | [[Gila monster man]] | [[King cobra man]] | [[Platypus man]] | [[Rattlesnake man]]
|-
| '''[[Web]]s''' || Can move through webbing and collect it in adventure mode with {{k|g}}. No web spray attack included. || | [[Brown recluse spider man]]
|-
|}

'''(All animal people have the Learning and Humanoid Attributes)'''

== Creature & Body Tokens Altered From Base Animal Raws ==
These are the tokens removed, added or replaced from the base creature that animal people come from. They are replaced in the c_variation_default.txt raw file by the tokens APPLY_CREATURE_VARIATION:ANIMAL_PERSON and APPLY_CREATURE_VARIATION:ANIMAL_PERSON_LEGLESS which come from the animal person's raws.

'''[[Creature token|Tokens]] removed and added'''
{| {{prettytable}}
|-
|-
! Token
! Change
|-
|| NAME
|| Removed
|-
|| GENERAL_CHILD_NAME
|| Removed
|-
|| GENERAL_BABY_NAME
|| Removed
|-
|| CASTE_NAME
|| Removed
|-
|| CHILDNAME
|| Removed
|-
|| BABYNAME
|| Removed
|-
|| SMALL_REMAINS
|| Removed
|-
|| DESCRIPTION
|| Removed
|-
|| CREATURE_TILE
|| Removed
|-
|| COLOR
|| Removed
|-
|| MAXAGE
|| Removed
|-
|| SOUND
|| Removed
|-
|| PET
|| Removed
|-
|| PETVALUE
|| Removed
|-
|| PENETRATEPOWER
|| Removed
|-
|| VERMIN_EATER
|| Removed
|-
|| VERMIN_HATEABLE
|| Removed
|-
|| VERMIN_GROUNDER
|| Removed
|-
|| VERMIN_FISH
|| Removed
|-
|| VERMIN_SOIL
|| Removed
|-
|| VERMIN_SOIL_COLONY
|| Removed
|-
|| VERMIN_ROTTER
|| Removed
|-
|| VERMIN_NOTRAP
|| Removed
|-
|| FISHITEM
|| Removed
|-
|| IMMOBILE_LAND
|| Removed
|-
|| TRIGGERABLE_GROUP
|| Removed
|-
|| MOUNT
|| Removed only from creatures with legs
|-
|| PET_EXOTIC
|| Removed
|-
|| NOT_BUTCHERABLE
|| Removed
|-
|| SPEED
|| Removed
|-
|| SWIMSPEED
|| Removed
|-
|| MUNDANE
|| Removed
|-
|| POPULATION_NUMBER
|| Removed
|-
|| CLUSTER_NUMBER
|| Removed
|-
|| ATTACK
|| Removed
|-
|| ATTACK_SKILL
|| Removed
|-
|| ATTACK_VERB
|| Removed
|-
|| ATTACK_CONTACT_PERC
|| Removed
|-
|| ATTACK_PRIORITY
|| Removed
|-
|| ATTACK_FLAG_WITH
|| Removed
|-
|| ATTACK_PENETRATION_PERC
|| Removed
|-
|| ATTACK_PREPARE_AND_RECOVER
|| Removed
|-
|| ATTACK_FLAG_EDGE
|| Removed
|-
|| ATTACK_FLAG_CANLATCH
|| Removed
|-
|| SPECIALATTACK_INJECT_EXTRACT
|| Removed
|-
|| SPECIALATTACK_SUCK_BLOOD
|| Removed
|-
|| ATTACK_VELOCITY_MODIFIER
|| Removed
|-
|| GAIT
|| Removed
|-
|| UBIQUITOUS
|| Removed
|-
|| LARGE_ROAMING
|| Added
|-
|| SAVAGE
|| Added
|-
|| GRAVITATE_BODY_SIZE:70000
|| Added
|-
|| CHANGE_FREQUENCY_PERC:10
|| Added
|-
|| CAN_LEARN
|| Added
|-
|| CAN_SPEAK
|| Added
|-
|| EQUIPS
|| Added
|-
|| CANOPENDOORS
|| Added
|-
|| LOCAL_POPS_CONTROLLABLE
|| Added
|-
|| LOCAL_POPS_PRODUCE_HEROES
|| Added
|-
|}

'''APPLY_CREATURE_VARIATION:ANIMAL_PERSON [[Body token|Body Tokens]] Converted'''
{| {{prettytable}}
|-
|-
! Target Tag
! Replacement Tag
|-
|| QUADRUPED
|| HUMANOID
|-
|| QUADRUPED_FRONT_GRASP
|| HUMANOID
|-
|| QUADRUPED_NECK
|| HUMANOID_NECK:3FINGERS
|-
|| QUADRUPED_NECK_FRONT_GRASP
|| HUMANOID_NECK
|-
|| QUADRUPED_HOOF
|| HUMANOID_HOOF:3FINGERS
|-
|| QUADRUPED_NECK_HOOF
|| HUMANOID_NECK_HOOF:3FINGERS
|-
|| HUMANOID_ARMLESS
|| HUMANOID:4FINGERS
|-
|| HUMANOID_ARMLESS_NECK
|| HUMANOID_NECK:4FINGERS
|-
|| BODY_WITH_HEAD_FLAG
|| HUMANOID:3FINGERS
|-
|| BASIC_1PARTBODY:BASIC_HEAD
|| HUMANOID:3FINGERS
|-
|| BASIC_2PARTBODY:BASIC_HEAD
|| HUMANOID:3FINGERS
|-
|| BASIC_1PARTBODY:BASIC_HEAD_NECK
|| HUMANOID_NECK:3FINGERS
|-
|| BASIC_2PARTBODY:BASIC_HEAD_NECK
|| HUMANOID_NECK:3FINGERS
|-
|| INSECT
|| HUMANOID_4ARMS:3FINGERS
|-
|| INSECT_4LEGS_2ARMS
|| HUMANOID:3FINGERS
|-
|| SPIDER
|| HUMANOID_6ARMS:3FINGERS
|-
|| 5TOES_FQ_FINGERS
|| 5FINGERS
|-
|| 4TOES_FQ_FINGERS
|| 4FINGERS
|-
|| 3TOES_FQ_FINGERS
|| 3FINGERS
|-
|| 5TOES_FQ_REG
|| 5FINGERS
|-
|| 4TOES_FQ_REG
|| 4FINGERS
|-
|| 3TOES_FQ_REG
|| 3FINGERS
|-
|| 5TOES_RQ_ANON
|| 5TOES
|-
|| 4TOES_RQ_ANON
|| 4TOES
|-
|| 3TOES_RQ_ANON
|| 3TOES
|-
|| 5TOES_RQ_REG
|| 5TOES
|-
|| 4TOES_RQ_REG
|| 4TOES
|-
|| 3TOES_RQ_REG
|| 3TOES
|-
|}

'''APPLY_CREATURE_VARIATION:ANIMAL_PERSON:LEGLESS [[Body token|Body Tokens]] Converted'''
{| {{prettytable}}
|-
|-
! Target Tag
! Replacement Tag
|-
|| QUADRUPED
|| HUMANOID_LEGLESS
|-
|| QUADRUPED_NECK
|| HUMANOID_LEGLESS_NECK:3FINGERS
|-
|| QUADRUPED_HOOF
|| HUMANOID_LEGLESS:3FINGERS
|-
|| QUADRUPED_NECK_HOOF
|| HUMANOID_LEGLESS_NECK:3FINGERS
|-
|| HUMANOID_ARMLESS
|| HUMANOID_LEGLESS:4FINGERS
|-
|| HUMANOID_ARMLESS_NECK
|| HUMANOID_LEGLESS_NECK:4FINGERS
|-
|| BODY_WITH_HEAD_FLAG
|| HUMANOID_LEGLESS:3FINGERS
|-
|| BASIC_1PARTBODY:BASIC_HEAD
|| HUMANOID_LEGLESS:3FINGERS
|-
|| BASIC_2PARTBODY:BASIC_HEAD
|| HUMANOID_LEGLESS:3FINGERS
|-
|| BASIC_1PARTBODY:BASIC_HEAD_NECK
|| HUMANOID_LEGLESS_NECK:3FINGERS
|-
|| BASIC_2PARTBODY:BASIC_HEAD_NECK
|| HUMANOID_LEGLESS_NECK:3FINGERS
|-
|| INSECT
|| HUMANOID_LEGLESS_4ARMS:3FINGERS
|-
|| SPIDER
|| HUMANOID_LEGLESS_6ARMS:3FINGERS
|-
|| 5TOES_FQ_FINGERS
|| 5FINGERS
|-
|| 4TOES_FQ_FINGERS
|| 4FINGERS
|-
|| 3TOES_FQ_FINGERS
|| 3FINGERS
|-
|| 5TOES_FQ_REG
|| 5FINGERS
|-
|| 4TOES_FQ_REG
|| 4FINGERS
|-
|| 3TOES_FQ_REG
|| 3FINGERS
|-
|| 5TOES_RQ_ANON
|| Removed
|-
|| 4TOES_RQ_ANON
|| Removed
|-
|| 3TOES_RQ_ANON
|| Removed
|-
|| 5TOES_RQ_REG
|| Removed
|-
|| 4TOES_RQ_REG
|| Removed
|-
|| 3TOES_RQ_REG
|| Removed
|-
|}

== History ==

Present from the first official release of the game, the animal people did not exist as a class but were instead part of a small group of subterranean creatures that harassed your dwarves. [[23a:frogman|Frogmen]], [[23a:lizardman|lizardmen]], and [[23a:snakeman|snakemen]] emerged from [[23a:cave river|cave rivers]], and [[23a:antman|antmen]], [[23a:batman|batmen]], and [[23a:ratman|ratmen]] would come out from [[23a:chasm|chasms]] to attack.

[[40d:release information|v0.27.169.32a]] released three-dimensional worlds, and subterranean creatures were moved to flock near generated [[40d:chasm|chasms]], [[40d:underground river|underground rivers]], and [[40d:Underground pool|underground pools]]. [[cave swallow man|Cave swallowmen]] and [[olm man|olmmen]] were introduced. The first set of above-ground savage animal people were also introduced: [[leech man|leechmen]], [[snail man|snailmen]], [[slug man|slugmen]], and [[tiger man|tigermen]].

In [[v0.31:release information|v0.31]], every creature was renamed and/or had their properties revamped (for example, "frogman" was changed to "amphibian man" and "batman" was changed to "bat man"). Not all animal people were redefined in this version, and some continued to use old codes for many releases. The version also introduced "[[creature variation token|creature variation]]" templates, which made converting existing animals to humanoid (and giant) variations much more efficient. Underground features were expanded to the current [[cavern]]s, and subterranean animal people formed civilizations. More anthropomorphic variations of animals present at the time were added.

More animal people were added to the game in [[v0.34:release information|v0.34]].

[[Release information/0.42.01|v0.42.01]] allowed animal people to join civilizations, live in sites, and visit forts. Animal people became playable as adventurers. (A grizzly bear hammerman has much to offer a dwarven society.) [[Release information/0.42.04|v0.42.04]] added more animal people to the game.

== Bugs ==

* Humanoid versions of animals with the {{token|MEANDERER}} token will keep it when converted, leading to severe issues with their pathfinding. These animal people will move extremely slowly unless performing a task.{{Bug|9588}}

{{Creatures}}

{{Category|Humanoids}}
[[Ru:Animal people]]

Anatomy

2020-06-30T22:11:45Z

Albedo: fix link to new page name

{{Quality|Superior|21:17, 20 September 2016 (UTC)}}
{{av}}
This page contains a list of all the body parts in the game.

==Head==

*[[Hair]]
*[[Eye]]s
:Eyes, while not essential for life, are bad to lose. The loss of one or both eyes alone will not cause death, but may have other adverse effects. If both eyes are lost then the creature will lose its vision. Currently, eyes cannot be entirely lost, only damaged.
:*Eyelids
::These can be damaged and Toady believes that eyes will be washed with soap if they cannot be washed by the eyelids due to injury.
*[[Brain]]
:Any major damage to the brain will likely result in [[death]]. Minor damage may result in [[symptom|unconsciousness]].

==Upper Body==

*[[Lung]]s
:Damage to one or both lungs can be sustained, but will cause difficulty of breath and may result in a loss of speed. Major damage will cause death.
*[[Heart]]
:Major damage to the heart will cause certain death.
*Stomach
:It's bad if it's damaged. Anything with a stomach will retch and then puke if the stomach is broken.
*[[Liver]]
:Used for processing [[alcohol]]. Dwarven livers are much stronger than human livers and have never been damaged by alcohol. The loss of a liver is a terrible thing for a dwarf.
*Guts
:Under pressure, and can pop out of wound. Also damage here causes vomiting and pain
*Arms
:*Upper Arms
:*Lower Arms
:*Hands
::*Fingers
:::*[[Nail]]s
Is also considered the main part of every creature. In general when this is gone the creature is dead and this is the part that decides what the corpse is and what the severed parts are.

==Lower Body==

*Legs
:*Upper Legs
:*Lower Legs
:*Feet
::*Toes
:::*[[Nail]]s
::::These will grow and become unkempt if not taken care of. This is done automatically by dwarves.

==[[Skin]]==
The first protective layer.

==[[Fat]]==
[[Fat]] can be gained or lost depending on how much a creature eats and how much it works. It will melt if heated to a high enough temperature. This is a layer below the skin and above the muscle.

==Muscle==
This layer is under the fat.

==Arteries==
If damaged, heavy bleeding will likely result in death. They appear to contain several gallons of blood.

==Nerves==
If damaged, the body part they are connected to will become useless or less effective.

==Tendons==
If destroyed, the limbs they connect will be useless.

DF2014:Symptoms

2020-06-30T22:10:05Z

Albedo: moved to DF2014:Symptom

{{wrong namespace|Symptom}}

Moved to [[DF2014:Symptom]] due to article naming (singular/plural)

Symptom

2020-06-30T22:09:41Z

Albedo: moved from incorrect page name (plural); copy/paste + TOC

{{av}}{{Quality|Exceptional}}
A '''symptom''' is a status effect most often caused by contracting a [[syndrome]]. They range from mild temporary annoyances to lifelong disabilities to even death if untreated. An affected dwarf will need to be diagnosed at a [[Hospital]] before a treatment can be prescribed.
__TOC__
==Blisters==
'''Effects''': Areas affected become prone to infection, this becomes more and more likely as severity goes up. While usually harmless in itself*, a resulting infection might cause a loss of life or limb if not properly dealt with.
: (* unless in the lungs, in which case the unlucky dwarf may be unable to breathe if the effect or a subsequent infection is severe.)

==Bleeding==
'''Effects''': Areas affected will continue to bleed for the duration of the effect and will not taper off like a normal wound. In effect it suggests that whatever caused the wound had an anti-coagulant in the venom. This will quickly cause an affected creature to bleed out if the syndrome is not immediately treated.

==Bruising==
'''Effects''': Causes pain long after the blunt trauma that caused it is over. Even the most severe bruises will heal without intervention, but may hint at fractures under the skin.

==Cough==
'''Effects''': Dwarf will stop and cough occasionally. While nearly harmless by itself severe coughs will sometimes bring up blood. In this case it's a sign of internal hemorrhaging.

==Dizziness==
'''Effects''': Creature might stumble/fall in a random direction when attempting to perform an action (including moving [!!!]). The more severe the dizziness the more likely this is to happen. Beware that stumbling, much like dodging, might end up putting a dwarf in a moat, or chasm, or magma, or off a wall, or falling just enough to land unconscious for a second on a cage trap. The list goes on.

==Drowsiness==
'''Effects''': Creature tires faster than normal and requires more sleep. This can be almost unnoticeable if the severity is low, but results in narcoleptic fits if high.

==Fever==
'''Effects''': Appears to reduce the ability to focus. Intense fevers can also cause stunning. While a fever in itself seems relatively harmless, it's often just the most visible symptom. Feverish dwarfs blink with a red "X".

==Impaired Function==
'''Effects''': Creature will be unable to use affected body parts for the duration. Much of the functionality here is mirrored in swelling, but this allows certain parts (such as organs) that normally can't swell to still cease functioning

==Nausea==
'''Effects''': Creature will stop and [[Vomit]]. How often this happens depends on severity. Sustained and intense vomiting will cause dwarfs to dehydrate.

==Necrosis==
'''Effects''': The affected tissue starts to rot away, which needless to say is a medical emergency. If action isn't quickly taken to remove the tissue (through either surgery or amputation) it will spread throughout the body and may cause [[Health_care#Infection|infection]], killing the creature. Also commonly seen in [[Undead]] creatures.

==Numbness==
'''Effects''': Creature will not be able to feel affected body parts. This makes pain a non-issue, but also hampers their use (I.E. Something with numb hands will find using weapons difficult, something who has a leg that's fallen asleep with have difficulty standing). Prolonged numbness will lead to permanent sensory nerve damage.

==Oozing==
'''Effects''': A sign of infection. Infected areas heal much slower and might kill if especially severe or widespread.

==Pain==
'''Effects''': Creatures that aren't in a martial trance that have pain above a certain level get all their rolls halved. They might give into pain and fall unconscious depending on toughness. This is more likely to happen more often the more severe the pain is, which is usually fatal in combat, since enemies will automatically target the unconscious victim's head with a perfectly accurate, perfectly square strike.

==Paralysis==
'''Effects''': The creature can't move. Severity only decreases the chance of resisting the symptom. Untargeted paralysis often leads to suffocation in smaller creatures, which can include dwarves.

==Swelling==
'''Effects''': Impedes the ability to use affected areas. Normally fairly harmless but can cause death by suffocation if it affects the throat. Prolonged swelling will lead to necrosis.

==Unconsciousness==
'''Effects''': Affected creature will pass out for the duration of this effect, even if the creature isn't in pain or extremely tired.

==Vomiting Blood==
'''Effects''': Much as excessive vomiting can lead to death from dehydration, vomiting blood can lead to death from blood loss. Considered to be a separate condition from coughing blood. If your creature happens to have green blood you'll be unable to tell this from nausea without checking the tiles.

[[ru:DF2012:Symptom]]

Altar

2020-06-30T21:54:17Z

Albedo: token start

{{quality|Tattered|00:01, 30 June 2020 (UTC)}}
{{av}}
{{newpage}}
Altars are used in [[temple]]s.

Wood burner

2020-06-30T21:46:18Z

Albedo: reorder header templates

{{Quality|Exceptional|13:18, 3 February 2017 (UTC)}}
{{av}}
{{Skill
| color = 6:0
| skill = Wood Burner
| profession = [[Farmer]]
| job name = [[Wood burning]]
| tasks =
* turn wood into ash
* turn wood into charcoal
| workshop = [[Wood furnace]]
| attributes =
* Strength
* Toughness
* Endurance
* Kinesthetic Sense
}}
'''Wood burner''' is the [[skill]] associated with the wood burning [[labor]], where [[Dwarf|dwarves]] turn [[wood]] into either [[ash]] or [[charcoal]] at a [[wood furnace]]. Dwarves with high skill level accomplish these tasks more quickly. Typically a wood stockpile and a bar/block stockpile are placed near the furnaces.

==How do I get dwarves to burn wood?==

Wood burner is somewhat tenuously considered a farming related job (because ash can be made into [[potash]], which fertilizes fields) and thus the labor is filed under Farming/''Related'' labor menu, and not [[DF2014:Furnace operator|furnace operating]].

{{Skills}}

Syndrome

2020-06-30T08:04:19Z

Albedo: /* List of syndromes */

{{Quality|Masterwork|13:02, 6 April 2015 (UTC)}}
{{av}}
[[File:Snakebite.png|200px|thumb|right|A single bite from a [[helmet snake]] lead to a slow, lingering death for this unfortunate hippo.]]
A '''syndrome''' is a specific combination of [[symptoms]] that a poor, helpless creature might get from a disease, venom or other effect, through encountering certain other creatures, substances, or supernatural [[weather]]. Syndromes generally cause unpleasant and frequently fatal symptoms over a short to long period of time, but some will clear up over time or with the assistance of a [[doctor]]. A [[Health care|hospital]] is required to diagnose and potentially treat those syndromes that can be helped by treatment.

==List of syndromes==
Syndromes are generally named after the animal, substance or effect that delivers them. Note that in a world with [[dragon]]s and [[giant elephant]]s, dwarves (and elves and humans) fall into the "small creatures" category for purposes of this discussion.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Syndrome
! Venom
! Acquired
! Short-term Symptoms
! Long-term Symptoms
! Chronic Symptoms
|-
| Adder bite
| adder venom (injected)
| Being bitten by an [[adder]], [[giant adder]] or [[adder man]]
| Strong pain
| Swelling Blisters Nausea
| None
|-
| Bark scorpion sting
| bark scorpion venom (injected)
| Being stung by a [[bark scorpion]], [[giant bark scorpion]] or [[bark scorpion man]]
| Strong pain
| None
| None
|-
| Black mamba bite
| black mamba venom (injected)
| Being bitten by a [[black mamba]], [[giant black mamba]] or [[black mamba man]]
| Dizziness Drowsiness Strong pain Fever Unconsciousness Complete paralysis1
| None
| None
|-
| Blob blisters
| cave blob fluid (contact or ingested)
| Touching a [[cave blob]]
| Mild pain Mild blisters
| None
| None
|-
| Brown recluse spider bite
| brown recluse spider venom (injected)
| Being bitten by a [[brown recluse spider]], [[giant brown recluse spider]] or [[brown recluse spider man]]
| Nausea Fever Pain 
| Severe localized necrosis
| None
|-
| Bumblebee sting
| bumblebee venom (injected)
| Being stung by a [[bumblebee]] worker
| Pain Strong swelling
| None
| None
|-
| Bushmaster bite
| bushmaster venom (injected)
| Being bitten by a [[bushmaster]], [[giant bushmaster]] or [[bushmaster man]]
| Strong pain Mild bleeding Dizziness Nausea Unconsciousness Complete paralysis1
| None
| None
|-
| Cave floater sickness
| cave floater gas (inhaled or ingested)
| Expelled from [[cave floater]]
| Mild nausea
| Fever Strong drowsiness (delayed) Strong dizziness (delayed)
| None
|-
| Cave spider bite
| cave spider venom (injected)
| Being bitten by a [[cave spider]]
| None
| None
| Very mild dizziness
|-
| Copperhead snake bite
| copperhead snake venom (injected)
| Being bitten by a [[copperhead snake]], [[giant copperhead snake]] or [[copperhead snake man]]
| Pain Swelling Nausea
| None
| None
|-
| Giant cave spider bite
| giant cave spider venom (injected)
| Being bitten by a [[giant cave spider]]
| Size-dependant paralysis.
| Death by asphyxiation, in small targets. Large targets are generally unhindered...unless you count the high probability of being eaten by the giant cave spider as a hindrance.
| None, not that it really matters.
|-
| Gila monster bite
| gila monster venom (injected)
| Being bitten by a [[gila monster]], [[giant gila monster]] or [[gila monster man]]
| Pain Mild swelling
| None
| None
|-
| Gnomeblight
| [[gnomeblight]] (contact, inhaled, injected, or ingested)
| Purposely exposing oneself to the extract. Only affects [[mountain gnome]]s and [[dark gnome]]s.
| None
| Severe systemic necrosis2
| None
|-
| Giant desert scorpion sting
| giant desert scorpion venom (injected)
| Being stung by a [[giant desert scorpion]]
| Necrosis of the brain and nervous system
| '''Certain death'''
| None, not that it really matters.
|-
| Helmet snake bite
| helmet snake venom (injected)
| Being bitten by a [[helmet snake]]
| Minor bleeding
| Fever Nausea Dizziness Localized swelling Localized oozing Localized bruising Strong pain Intense localized necrosis Possible loss of limb
| None
|-
| Honey bee sting
| honey bee venom (injected)
| Being stung by a [[honey bee]] worker
| Pain Strong swelling
| None
| None
|-
| Inebriation{{version|0.42.01}}
| [[Alcohol]] (consumed/injected)
| Consuming alcoholic drinks
| Nausea Dizziness Unconsciousness Personality changes Euphoria Erratic behavior Trouble breathing
| None
| None
|-
| Iron man cough
| iron man gas (inhaled)
| Expelled by [[iron man]]
| Coughing blood
| None
| None
|-
| King cobra bite
| king cobra venom (injected)
| Being bitten by a [[king cobra]]
| Complete paralysis1 Pain, dizziness, drowsiness
| None
| None
|-
| Phantom spider bite
| phantom spider venom (injected)
| Being bitten by a [[phantom spider]]
| None
| Numbness and mild dizziness
| None
|-
| Platypus sting
| platypus venom (injected)
| Being kicked by a [[platypus]], [[giant platypus]] or [[platypus man]]
| Pain and swelling
| Extreme pain, swelling possibly to the point of necrosis
| None
|-
| Rattlesnake bite
| rattlesnake venom (injected)
| Being bitten by a [[rattlesnake]], [[giant rattlesnake]] or [[rattlesnake man]]
| Pain, nausea, blisters, swelling, bruising
| Severe localized necrosis
| None
|-
| Serpent man bite
| serpent man venom (injected)
| Being bitten by a [[serpent man]]
| Complete paralysis1
| None
| None
|-
| Mummy's curse
| [[DF2014:Mummy|Disturbance interaction]].
| Being cursed by a [[mummy]], when caught raiding their tombs
| None
| None
| 20% chance of any skill roll failing, regardless of skill.
|-
| Vampirism
| [[Deity|Divine]] Curse.
| Drinking the blood of a [[vampire]]. Toppling statues in shrines in Adventure Mode or temples in Fortress Mode (random chance).
| None
| None
| Victim becomes a [[vampire]].
|-
| Werebeast Curse
| [[Deity|Divine]] Curse.
| Being bitten by a [[werebeast]] or toppling statues in shrines in Adventure Mode (random chance).
| None
| None
| Victim becomes a [[werebeast]].
|-
| Necromancy
| [[Deity|Divine]] Curse.
| Reading a book/slab that contains the secrets of life and death.
| None
| None
| Reader becomes a [[Necromancer]].
|-
| evil rain sickness3
|rowspan=7| Random
| Being caught outside in [[Weather#Evil weather|freakish weather]] in an evil [[biome]]
|rowspan=7| Random
|rowspan=7| Random
|rowspan=7| Random
|-
| evil cloud sickness4
| Being caught in a [Weather#Evil weather|creeping cloud]] in an evil [[biome]]
|-
| beast sickness5
| Encounters with [[forgotten beast]]s
|-
| titan sickness5
| Encounters with [[titan]]s
|-
| night sickness5
| Encounters with [[werebeast]]s or [[experiment]]s
|-
| demon sickness5
| Encounters with [[demon]]s
|-
| divine sickness5
| Encounters with [[angel]]s
|}
: 1. For small creatures such as humans and dwarves, paralysis tends to result in suffocation.
: 2. Necrosis of the brain will eventually result in death once the brain rots away completely.
: 3. Evil rain typically only causes minor symptoms such as blisters, bruising, coughing blood, dizziness, fever, nausea, oozing, and pain.
: 4. Evil clouds either cause major symptoms (as with beast/titan/demon sicknesses) or permanently transform creatures into [[Undead|zombie-like]] forms.
: 5. [[Titan]]s, [[forgotten beast]]s, [[werebeast]]s, [[experiment]]s, [[demon]]s and [[angel]]s have a chance to have a randomized syndrome. These range from mildly hazardous (mild [[Symptoms#Blisters|blisters]] from inhaling boiling blood) to instantly fatal (severe necrosis from a contact poison attached to a breath weapon/creature made of blood).

==The anatomy of a syndrome==
Mechanically, syndromes are bundles of tokens attached to a material (or to an interaction effect; see below) - they're confined to creature materials in vanilla DF, but it's a simple matter to add them to inorganic materials. When the material is injected, touched, inhaled, or ingested (depending on the syndrome), the creature suffers the predations of a nasty disease or poison. Here's an example syndrome, taken from the Giant Cave Spider raws.

If you are having troubles getting the syndromes to work (i.e., in combat reports, getting "'''supersnake''' n/a splatters~etc"), then simply throw the venom template into the actual creature's raw, which is what the LOCAL_CREATURE_MAT actually calls on; the venom being in the same file.

[USE_MATERIAL_TEMPLATE:VENOM:CREATURE_EXTRACT_TEMPLATE]
[STATE_NAME:ALL_SOLID:frozen giant cave spider venom]
[STATE_ADJ:ALL_SOLID:frozen giant cave spider venom]
[STATE_NAME:LIQUID:giant cave spider venom]
[STATE_ADJ:LIQUID:giant cave spider venom]
[STATE_NAME:GAS:boiling giant cave spider venom]
[STATE_ADJ:GAS:boiling giant cave spider venom]
[PREFIX:NONE]
[ENTERS_BLOOD]
[SYNDROME]
[SYN_NAME:giant cave spider bite]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[SYN_IMMUNE_CREATURE:SPIDER_CAVE:ALL]
[SYN_INJECTED]
[CE_PARALYSIS:SEV:100:PROB:100:RESISTABLE:SIZE_DILUTES:START:5:PEAK:10:END:20]

The first line, USE_MATERIAL_TEMPLATE, is creating a new material, called POISON, using the CREATURE_EXTRACT_TEMPLATE as the basis. After this, the STATE_NAME and STATE_ADJ tokens are used to define the names and adjectives assigned to different states of the material - GAS, LIQUID and ALL_SOLID, in this case, though ALL is also a valid token. At this stage, you can use any material tags like MAT_FIXED_TEMP or similar to set further material properties, though this usually isn't necessary.

ENTERS_BLOOD
This tag determines whether a poison enters the blood or not. If it is not included, the poison will splatter (if liquid) or flow (if gas) over the affected body part instead when injected. If you're using a contact poison, leave this out. Necessary for injected poisons.
SYNDROME
This tag ends the material details and begins the definition of the actual syndrome.
SYN_NAME
This one is self-explanatory - the name of the syndrome as it will appear in-game.
SYN_AFFECTED_CLASS
This token defines what CREATURE_CLASS will be affected by the syndrome. Most creatures are classed under GENERAL_POISON. Multiple tokens can be used in a single syndrome.
SYN_IMMUNE_CLASS
As above, but makes class immune.
SYN_IMMUNE_CREATURE
This token defines which creatures CANNOT be affected by the syndrome - useful for addressing specific instances within a population, such as a specific caste or an individual creature that falls under GENERAL_POISON. Syntax is [SYN_IMMUNE_CREATURE:creature:caste]. ALL can be used for the caste.
SYN_AFFECTED_CREATURE
As above, but makes creature or caste susceptible.
SYN_CLASS
This tag sets a class for the syndrome that can be used in [[Interaction token|interactions.]]
SYN_IDENTIFIER{{version|0.42.01}}.
Similar to SYN_CLASS, this sets an identifier that can be shared between multiple syndromes, for use with the SYNDROME_DILUTION_FACTOR creature token. In vanilla DF, this is used to allow dwarves to drink more alcohol before becoming inebriated.
SYN_NO_HOSPITAL{{version|0.42.01}}.
Probably prevents affected dwarves from being carried to the hospital.{{verify}}
SYN_CONCENTRATION_ADDED:x:x{{version|0.42.01}}.
Repeated exposure to the syndrome will result in the effects becoming more intense. In vanilla [SYN_CONCENTRATION_ADDED:100:1000] is used with alcohol.

SYN_INJECTED, SYN_CONTACT, SYN_INHALED, SYN_INGESTED
This token determines the method of infection - injected syndromes must be injected via a creature attack, while contact syndromes result from any contamination of a creature by material splatter (such as blood), inhaled syndromes must be inhaled in gaseous form (such as from boiling or a creature breath attack), and ingestion syndromes must be eaten or drunk. Any combination of these tags can be used. A fun variation on the usual creature injection routine is to create a material with a SYN_CONTACT syndrome and have a creature use it for blood - this tends to end poorly for any predator that chooses to attack them.

[SPECIALATTACK_INJECT_EXTRACT:LOCAL_CREATURE_MAT:VENOM:LIQUID:100:100]
This is one method for getting a poison into a creature. If [ENTERS_BLOOD] is applied, it will be injected into the bloodstream. Otherwise, it will just splatter over the area. Put this on a creature attack. Substance type (gas, liquid, solid) does not appear to have an effect. The numbers on the end are minimum and maximum.

CE_X, or creature effect tokens, are the real meat and bones of your syndrome. They're detailed below.

==Creature effect tokens==
Each and every syndrome has a number of creature effect tokens, represented by CE_X - these lovely little beauties determine exactly how the poor creature suffering from the syndrome is affected. An example CE token is as follows:

[CE_NECROSIS:SEV:100:PROB:100:LOCALIZED:VASCULAR_ONLY:RESISTABLE:START:50:PEAK:1000:END:2000]

In this example, we have an effect that will always cause severe necrosis in whichever bodypart it touches, so long as that bodypart is vascular and that the creature is not able to resist it in some manner. The effect begins shortly after the syndrome is contracted, peaks 1000 [[time|time units]] afterwards, and finally ceases another 1000 time units later.

As a general rule of thumb, so long as CE_X starts the string and START/(PEAK/END) ends it, the order of the intervening tokens isn't important. PEAK and END aren't required.

*CE_X
The effect type. This can be a number of different tokens, as detailed in the table below this list.
*SEV:X
The severity of the effect. Higher values appear to be worse, with SEV:1000 CE_NECROSIS causing a part to near-instantly become rotten.
*PROB:X
The probability of the effect actually manifesting in the victim, as a percentage. 100 means always, 1 means a 1 in 100 chance.
*LOCALIZED (Overwrites BP tokens)
This tag causes an effect to ignore all BP tokens and then forces the game to attempt to apply the effect to the limb that came into contact with the contagion - i.e. the part that was bitten by the creature injecting the syndrome material, or the one that was splattered by a contact contagion. If an effect can not be applied to the contacted limb (such as IMPAIR_FUNCTION on a non-organ) then this token makes the syndrome have no effect. This token also makes inhaled syndromes have no effect.
*BP:BODY_PART:TISSUE (Overwritten by LOCALIZED)
Specifies which body parts and tissues are to be affected by the syndrome. BODY_PART can be BY_CATEGORY:x to target body parts with a matching [CATEGORY:x] [[body token]] (or ALL to affect everything), BY_TYPE:x to target body parts having a particular type (UPPERBODY, LOWERBODY, HEAD, GRASP, or STANCE), or BY_TOKEN:x to target individual body parts by their ID (as specified in the [BP] token). For example, if you wanted to target the lungs of a creature, you would use BP:BY_CATEGORY:LUNG:ALL. The syndrome would act on all bodyparts within the creature with the CATEGORY tag LUNG and affect all tissue layers. For another example, say you wanted to cause the skin to rot off a creature - you could use BP:BY_CATEGORY:ALL:SKIN, targeting the SKIN tissue on all bodyparts. Multiple targets can be given in one syndrome by placing the BP tokens end to end. This is one of the most powerful and useful aspects of the syndrome system, as it allows you to selectively target bodyparts relevant to the contagion, like lungs for coal dust inhalation, or the eyes for exposure to an acid gas. Not everything takes a target!
*VASCULAR_ONLY (Optional)
This syndrome only affects tissue layers with the VASCULAR token.
*MUSCULAR_ONLY (Optional)
This syndrome only affects tissue layers with the MUSCULAR token. Are you seeing a trend here?
*SIZE_DILUTES (Optional)
This token presumably causes the effects of the syndrome to scale with the size of the creature compared to the size of the dose of contagion they received, but has yet to be extensively tested.
*SIZE_DELAYS (Optional)
As above, this token has yet to be tested but presumably delays the onset of a syndrome according to the size of the victim.
*DWF_STRETCH:X{{version|0.42.01}} (Optional)
Multiplies the duration of the syndrome by X in Fortress mode. If X is 72, syndrome will last the same amount of ticks in fortress and adventure mode.
*ABRUPT{{version|0.42.01}} (Optional)
Makes the symptom begin immediately rather than ramping up. {{verify}}
*CAN_BE_HIDDEN (Optional)
Can be hidden by a unit assuming a secret identity, such as a [[vampire]]. {{verify}}
*RESISTABLE (Optional)
Determines if the effect can be hindered by the target creature's [[Attribute#Disease_Resistance|disease resistance attribute]]. Without this token, disease resistance is ignored.

The details of this table are still being thrashed out by modders, so if you have anything to add, please don't hesitate to hit the edit button!

Non-targeted syndromes will ignore any BP tokens and LOCALIZED tokens.
{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Description
|-
| CE_BLEEDING
| Yes
| Causes the targeted bodypart to start bleeding, with heavy enough bleeding resulting in the death of the sufferer. Some conditions seem to cause bleeding to be fatal no matter how weak.
|-
| CE_BLISTERS
| Yes
| Covers the targeted bodypart with blisters.
|-
| CE_BRUISING
| Yes
| Causes the targeted bodypart to undergo bruising.
|-
| CE_IMPAIR_FUNCTION
| Yes
| An organ afflicted with this CE is rendered inoperable - for example, if both lungs are impaired the creature can't breathe and will suffocate. This token only affects organs, not limbs. Note that this effect is currently bugged, and will not "turn off" until the creature receives a wound to cause its body parts to update.
|-
| CE_NECROSIS
| Yes
| Causes the targeted bodypart to rot, with associated tissue damage, miasma emission and bleeding. The victim slowly bleeds to death if the wound is not treated. Badly necrotic limbs will require amputation.
|-
| CE_NUMBNESS
| Yes
| Causes numbness in the affected body part, blocking pain. Extreme numbness may lead to sensory nerve damage.
|-
| CE_OOZING
| Yes
| Causes pus to ooze from the afflicted bodypart.
|-
| CE_PAIN
| Yes
| Afflicts the targeted bodypart with intense pain.
|-
| CE_PARALYSIS
| Yes
| Causes paralysis. Paralysis is complete paralysis and will cause suffocation in smaller creatures. Paralysis on a limb may lead to motor nerve damage.
|-
| CE_SWELLING
| Yes
| Causes the targeted bodypart to swell up. Extreme swelling may lead to necrosis.
|-
| CE_COUGH_BLOOD
| No
| This effect results in the sufferer periodically coughing blood, which stains the tile they're on and requires cleanup. It doesn't appear to be lethal, but may cause minor bleeding damage.
|-
| CE_DIZZINESS
| No
| Inflicts the Dizziness condition, occasional fainting and a general slowdown in movement and work speed.
|-
| CE_DROWSINESS
| No
| Causes the Drowsiness condition.
|-
| CE_FEVER
| No
| Causes the Fever condition.
|-
| CE_NAUSEA
| No
| Causes the Nausea condition, and heavy vomiting. Can eventually lead to dehydration and death.
|-
| CE_UNCONSCIOUSNESS
| No
| Renders unconscious.
|-
| CE_VOMIT_BLOOD
| No
| This effect results in the sufferer periodically vomiting blood, which stains the tile they're on and requires cleanup. It doesn't appear to be lethal, but may cause minor bleeding damage.
|-
| CE_ERRATIC_BEHAVIOR{{version|0.42.01}}
| No
| Causes erratic behavior, meaning "People that like to brawl have a chance of starting a brawl-level fight with any nearby adult" [http://www.bay12forums.com/smf//index.php?topic=159164.msg7632503#msg7632503 -Toady]
|}
====Healing Effects====
Starting with DF version 0.47.01, there are healing counterparts to most of the tokens above that will heal various syndrome effects or physical damage.
{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Description
|-
| CE_STOP_BLEEDING
| Yes?
| Decreases the severity of the bleeding of any wounds or syndrome effects on the targeted bodypart. The SEV value probably controls by how much the bleeding is decreased.
|-
| CE_CLOSE_OPEN_WOUNDS
| Yes?
| Closes any wounds on the targeted bodypart with speed depending on the SEV value.
|-
| CE_HEAL_TISSUES
| Yes?
| Heals the tissues of the targeted bodypart with speed depending on the SEV value.
|-
| CE_HEAL_NERVES
| Yes?
| Heals the nerves of the targeted bodypart with speed depending on the SEV value.
|-
| CE_REDUCE_PAIN
| Yes?
| Decreases the severity of pain produced by wounds or syndrome effects on the targeted bodypart. The SEV value probably controls by how much the pain is decreased.
|-
| CE_REDUCE_SWELLING
| Yes?
| Decreases the severity of swelling on the targeted bodypart.
|-
| CE_CURE_INFECTION
| Yes?
| Probably decreases the severity of the infection from infected wounds over time.
|-
| CE_REDUCE_PARALYSIS
| Yes?
| Decreases the severity of any paralysis effects on the targeted bodypart.
|-
| CE_REGROW_PARTS
| Yes
| Causes missing bodyparts to regrow. SEV controls how quickly bodyparts are regrown. In adventure, parts will be regrown until you travel or wait/sleep {{bug|0011396}}.
|-
| CE_REDUCE_DIZZINESS
| No
| Decreases the severity of any dizziness the creature has.
|-
| CE_REDUCE_NAUSEA
| No
| Decreases the severity of any nausea the creature has.
|-
| CE_REDUCE_FEVER
| No
| Decreases the severity of any fever the creature has.
|}

===Special Effects===
Several special syndrome effects take different arguments than the above. These are used for generated interactions in unmodded games, but may be used as well for any substance or custom interaction.

{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Arguments
! Description
|-
| CE_ADD_TAG
| No
| tags
| Adds a tag to the affected creature. Many arguments can be used sequentially within one syndrome token. Valid tags are the same as that of the [[interaction token]] '''IT_REQUIRES''', ie.

BLOODSUCKER, CAN_LEARN, CAN_SPEAK, CRAZED, EXTRAVISION, LIKES_FIGHTING (or LIKESFIGHTING), MISCHIEVOUS (or MISCHIEVIOUS), NO_CONNECTIONS_FOR_MOVEMENT, NO_DIZZINESS, NO_DRINK, NO_EAT, NO_FEVERS, NO_PHYS_ATT_GAIN, NO_PHYS_ATT_RUST, NO_SLEEP, NO_THOUGHT_CENTER_FOR_MOVEMENT, NOBREATHE, NOEMOTION, NOEXERT, NOFEAR, NONAUSEA, NOPAIN, NOSTUN, NOT_LIVING, NOTHOUGHT, OPPOSED_TO_LIFE, PARALYZEIMMUNE, SUPERNATURAL, TRANCES, NO_AGING, STERILE, UTTERANCES.
|-
| CE_REMOVE_TAG
| No
| tags
| Removes a tag from a creature. Supported arguments are the same as CE_ADD_TAG.
|-
| CE_DISPLAY_TILE
| No
| TILE:[[Tilesets|tile number]]:[[Color#Modding color|colour]]
| The creature displays the specified tile and colour instead of its normal one.
|-
| CE_DISPLAY_NAME
| No
| NAME:singular:plural:adjective
| Attaches a specified name to the creature's normal name.
|-
| CE_FLASH_TILE
| No
| TILE:tile number:colour:FREQUENCY:ticks default tile:ticks syndrome tile
| The creature flashes between its normal tile and the one specified here.
|-
| CE_PHYS_ATT_CHANGE
| No
| [[Attribute]]:percentage:fixed boost(?)
| Alters the physical [[attribute]]s of a creature.
|-
| CE_MENT_ATT_CHANGE
| No
| [[Attribute]]:percentage:fixed boost(?)
| Alters the mental [[attribute]]s of a creature.
|-
| CE_BODY_APPEARANCE_MODIFIER
| No
| APPEARANCE_MODIFIER:HEIGHT/LENGTH/BROADNESS:percentage(?)
| Alters the size of the creature.
|-
| CE_BP_APPEARANCE_MODIFIER
| Yes
| body part:APPEARANCE_MODIFIER:attribute:number]
| Alters the characteristics (height, width etc.) of a body part.
|-
| CE_MATERIAL_FORCE_MULTIPLIER
| No
| MAT_MULT:[[material token|material]]:A:B
| Makes creature affected by materials more or less by a factor of A/B. If A is 3 and B is 2, the creature will be 1.5x weaker to the defined material (can be NONE:NONE for all); if 2:3, the creature will be 1.5 times stronger.
|-
| CE_SPEED_CHANGE
| No
| speed modifier:number
| Changes the speed of a creature.
Speed modifier contains one or both of:
* SPEED_PERC:percentage (this modifies a creature's in-game speed, so higher numbers are faster)
* SPEED_ADD:number (this modifies a creature's [SPEED:XX] token, so higher numbers are slower. Negative numbers are accepted though will only reduce a creature's speed to zero)
The minimum and maximum speeds able to be created by CE_SPEED_CHANGE are 99 and 10,000 respectively.

|-
| CE_CAN_DO_INTERACTION
| No
|
| Makes the creature able to perform an interaction. See [[Interaction token]]. To specify the interaction, use the argument:
* CDI:INTERACTION:interaction name
|-
| CE_SPECIAL_ATTACK_INTERACTION{{version|0.47.01}}
| Yes
| INTERACTION:<interaction name>:BP:<selection criteria>:<name of category,type, or token of designated part/parts>
| Makes the creature able to perform an interaction when using an attack with a designated body part/parts. See [[#Spreading diseases in 0.47.01|below]] for an example

|-
| CE_BODY_MAT_INTERACTION
| No
| MAT_TOKEN:<body material token>
| Causes one of the creature's body materials to trigger an interaction when the material is ingested, injected, etc (depending on the [CE:SYNDROME_TAG]s used; note that more than one may be specified). Generated vampire syndromes use '''RESERVED_BLOOD''' as the body material token in this syndrome tag, so as to specify the blood material of any creature with the syndrome. The following tokens should be inserted after this:
* '''CE:INTERACTION:interaction_id''' - replace 'interaction_id' with the name of the target interaction
* '''CE:SYNDROME_TAG:syndrome_trigger_type''' - replace 'syndrome_trigger_type' with any of SYN_INGESTED, SYN_INJECTED, SYN_CONTACT, SYN_INHALED
The linked interaction must have an [[Interaction_token#I_SOURCE|[I_SOURCE:INGESTION]]] token for this to work!

Note that this currently only works on materials obtained from historical figures and has only been tested with ingested materials linked to interactions with ADD_SYNDROME interaction effects.

|-
| CE_BODY_TRANSFORMATION
| No
| PROB:percentage:START:time:END:time
| Transforms into another creature. PROB and END arguments optional. The target creature may either be specified directly using CE:CREATURE or else set to be randomly selected as guided by creature and/or caste flag restrictions (of which multiple may be specified).
* CE:CREATURE:CREATURE_ID:CASTE_ID - Specify the creature and caste (for example: CE:CREATURE:DWARF:FEMALE). ANY can be used in place of a specific CASTE_ID to randomise the caste for every transformation. 
* CE:CREATURE_FLAG:FLAG{{version|0.47.01}} - Any creature with the specified [[:Interaction_token#Creature_and_Caste_Flags|creature flag]] is a valid transformation target. 
* CE:FORBIDDEN_CREATURE_FLAG{{version|0.47.01}} - Forbids all creatures with the specified [[:Interaction_token#Creature_and_Caste_Flags|creature flag]] from being randomly selected. 
* CE:CREATURE_CASTE_FLAG:FLAG{{version|0.47.01}} - Any creature with the specified [[:Interaction_token#Creature_and_Caste_Flags|caste flag]] is a valid transformation target. 
* CE:FORBIDDEN_CREATURE_CASTE_FLAG{{version|0.47.01}} - Forbids all creatures with the specified [[:Interaction_token#Creature_and_Caste_Flags|caste flag]] from being randomly selected. 
*CE:HAVE_FAST_EFFORTLESS_GAIT_SPEED{{version|0.47.01}} - Unknown. Possibly disallows all creatures with only slow gaits.{{verify}}

Note that any wounds the creature has suffered will instantly heal upon transforming, both into and out of the target form. [[Undead]] limbs of a creature with this token will grow into a full instance of that creature.
|-
| CE_SKILL_ROLL_ADJUST
| No
| PERC:percentage:PERC_ON:percentage
| Alters the skill level of a creature. The argument PERC specifies a percentage of the creature's current skill, and PERC_ON the probability of the effect being applied on a particular roll.
|-
| CE_SENSE_CREATURE_CLASS
| No
| START:time:CLASS:creature class:tile:color
| Allows creature to see other creatures with given class through walls. Vampires, for example, have START:0:CLASS:GENERAL_POISON:15:4:0:1.
|-
| CE_CHANGE_PERSONALITY{{version|0.42.01}}
| No
| FACET:[[DF2014:Personality_trait#Facets|trait]]:amount
| Changes a [[personality trait]] by amount. Multiple FACET:trait:amount sets may be used.
|-
| CE_FEEL_EMOTION{{version|0.42.01}}
| No
| EMOTION:[[emotion]]
| Makes the creature feel a specific [[emotion]]; severity based on standard SEV value. The [[thought]] the creature receives is: "[creature] feels [emotion] due to [syndrome name]". See [[Emotion]] for the list of valid emotions.
|}

'''All''' creature effect tokens take START, END and PROB numbers, and can be followed by [CE:PERIODIC] and/or [CE:COUNTER_TRIGGER] to restrict when they actually take effect.
* PERIODIC:period_type:min_value:max_value
* {{text anchor|COUNTER_TRIGGER}}:counter_name:min_value:max_value:REQUIRED

Currently, the only valid period type is MOON_PHASE.

===Counter Triggers===
Valid counter values are below:

{| {{prettytable}}
|- bgcolor="Bisque"
! Counter
! Description
|-
| ALCOHOLIC
| How long it's been (in [[time]] units) since the creature last had a drink of alcohol. Only present on creatures who need alcohol to get through the working day.
* 100800 (3 months) = and is starting to work slowly due to its scarcity
* 201600 (6 months) = and really wants a drink
* 302400 (9 months) = and has gone without a drink for far, far too long
* 403200 (1 year) = and can't even remember the last time he/she had some
|-
| CAVE_ADAPT
| How cave-adapted the creature is. Increases by 1 for every [[time]] unit spent underground, to a maximum of 800000.
* 403200 (1 year) = going outside causes irritation
* 604800 (1.5 years) = going outside causes nausea
|-
| PARTIED_OUT
| How long before the creature will decide to attend another party. Starts at 3+ months and counts down to zero.
|-
| MILK_COUNTER
| How long before the creature can be milked again. Starts at the creature's MILK frequency and counts down to zero.
|-
| EGG_SPENT
| How long before the creature can lay more eggs. Starts at 3 months and counts down to zero.
|-
| GROUNDED_ANIMAL_ANGER
| How angry (and likely to attack) an animal is from being over-crowded. Increases when over-crowded and otherwise counts down to zero.
|-
| TIME_SINCE_SUCKED_BLOOD
| How long it's been (in [[time]] units) since the creature last sucked somebody's blood.
|-
| DRINKING_BLOOD
| How much longer the creature will be drinking somebody's blood. Starts at 2.4 days and counts down to zero.
|}

{{mod}}

==Inorganic syndromes and you!==
It's perfectly possible - and quite simple - to add a nasty syndrome to a type of rock or metal - you simply add the syndrome tokens to the material definition in the same manner that you would add them to a creature material definition. The only catch is that since your hapless dwarves will only normally encounter the material in metal, gem or boulder form, a bit of creativity must be used to actually get them inside your citizens - that is, you need to make them 'explosively boil' as soon as they're mined or produced. This has the sad side effect of destroying the actual item - sorry, no highly radioactive uranium this release.

The easiest way to accomplish this is to assign the material a low boiling point, usually just under room temperature, and make sure its temperature is fixed to a point above it.
[MELTING_POINT:NONE]
[BOILING_POINT:10000]
[MAT_FIXED_TEMP:10001]
Now, as soon as this substance hits the open air - by being mined, smelted or reaction-produced at a custom workshop - it will EXPLOSIVELY BOIL, flooding a small area with delicious syndrome-rich gas. Creatures who inhale the gas will be immediately hit with the syndrome you thoughtfully attached to the material definition earlier!

There are a number of other tokens you can use to control the colour and naming conventions of your syndrome material, referred to as [[material definition token]]s.

==Spreading diseases==
It's fully possible to make a nasty disease capable of spreading itself from an infected dwarf to others, though it requires some skill in modding [[interaction token|interactions]] as well. Here is an example of a plague-inflicting interaction:

[INTERACTION:PLAGUE]
[I_TARGET:A:CREATURE]
[IT_LOCATION:CONTEXT_CREATURE]
[IT_FORBIDDEN:NOT_LIVING]
[IT_AFFECTED_CLASS:GENERAL_POISON]
[IT_MANUAL_INPUT:creatures]
[I_EFFECT:ADD_SYNDROME]
[IE_TARGET:A]
[IE_IMMEDIATE]
[SYNDROME]
[SYN_NAME:the plague]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[CE_FEVER:SEV:250:PROB:100:START:250:PEAK:1500:END:25000]
[CE_BLISTERS:SEV:325:PROB:100:BP:BY_CATEGORY:ALL:SKIN:START:250:PEAK:1500:END:25000]
[CE_NECROSIS:SEV:300:PROB:100:BP:BY_CATEGORY:ALL:ALL:VASCULAR_ONLY:START:22500:PEAK:23750:END:25000]
[CE_CAN_DO_INTERACTION:START:1500:END:25000]
[CDI:ADV_NAME:Spread the plague]
[CDI:INTERACTION:PLAGUE]
[CDI:TARGET:A:LINE_OF_SIGHT]
[CDI:TARGET_RANGE:A:10]
[CDI:WAIT_PERIOD:30]

As you can see, the syndrome here inflicts blisters, fever and, after roughly a month, necrosis of the whole body - that's when the infected creatures will start dying out. But before that happens, CE_CAN_DO_INTERACTION makes them capable of spreading the plague further.

You also need a disease vector that will bring the plague straight to your fort. (hint: use [[large rat|various]] [[rat man|species]] [[giant rat|of rats]] - they're perfect for that). The following code, added to a creature's raws, ensures the creature will infect anybody it encounters:

[CAN_DO_INTERACTION:PLAGUE]
[CDI:ADV_NAME:Spread the plague]
[CDI:TARGET:A:LINE_OF_SIGHT]
[CDI:TARGET_RANGE:A:10]
[CDI:WAIT_PERIOD:30]

As soon as the said creature is startled by your dwarves, the [[fun]] will begin.

==''In 0.47.01''==
As of version 0.47.01, it may be possible to use a creature's established methods of attack for use in disease-spreading.

Let's use the borrowed example of the plague above. This time, the plague will spread through biting, using the following syndrome code:

[INTERACTION:PLAGUE]
[I_TARGET:A:CREATURE]
[IT_LOCATION:CONTEXT_CREATURE]
[IT_FORBIDDEN:NOT_LIVING]
[IT_AFFECTED_CLASS:GENERAL_POISON]
[IT_MANUAL_INPUT:creatures]
[I_EFFECT:ADD_SYNDROME]
[IE_TARGET:A]
[IE_IMMEDIATE]
[SYNDROME]
[SYN_NAME:the plague]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[CE_FEVER:SEV:250:PROB:100:START:250:PEAK:1500:END:25000]
[CE_BLISTERS:SEV:325:PROB:100:BP:BY_CATEGORY:ALL:SKIN:START:250:PEAK:1500:END:25000]
[CE_NECROSIS:SEV:300:PROB:100:BP:BY_CATEGORY:ALL:ALL:VASCULAR_ONLY:START:22500:PEAK:23750:END:25000]
[CE_SPECIAL_ATTACK_INTERACTION:INTERACTION:PLAGUE:BP:BY_CATEGORY:TOOTH:START:0:ABRUPT]

The line [CE_SPECIAL_ATTACK_INTERACTION:INTERACTION:BITE_PLAGUE:BP:BY_CATEGORY:MOUTH:BP:BY_CATEGORY:TOOTH:START:0:ABRUPT] allows any infected creature with an attack using mouth or tooth category body parts to immediately spread the disease using said attack. The victim of the attack may then spread the disease if they are able to attack with the needed body part/parts.

{{Category|Modding}}
{{Category|Creature attributes}}
{{Category|Tokens}}
[[ru:DF2012:Syndrome]]

Syndrome

2020-06-30T08:04:05Z

Albedo: /* List of syndromes */ "small targets" = dwarves

{{Quality|Masterwork|13:02, 6 April 2015 (UTC)}}
{{av}}
[[File:Snakebite.png|200px|thumb|right|A single bite from a [[helmet snake]] lead to a slow, lingering death for this unfortunate hippo.]]
A '''syndrome''' is a specific combination of [[symptoms]] that a poor, helpless creature might get from a disease, venom or other effect, through encountering certain other creatures, substances, or supernatural [[weather]]. Syndromes generally cause unpleasant and frequently fatal symptoms over a short to long period of time, but some will clear up over time or with the assistance of a [[doctor]]. A [[Health care|hospital]] is required to diagnose and potentially treat those syndromes that can be helped by treatment.

==List of syndromes==
Syndromes are generally named after the animal, substance or effect that delivers them. Note that in a world with [[[dragon]]s and [[giant elephant]]s, dwarves (and elves and humans) fall into the "small creatures" category for purposes of this discussion.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Syndrome
! Venom
! Acquired
! Short-term Symptoms
! Long-term Symptoms
! Chronic Symptoms
|-
| Adder bite
| adder venom (injected)
| Being bitten by an [[adder]], [[giant adder]] or [[adder man]]
| Strong pain
| Swelling Blisters Nausea
| None
|-
| Bark scorpion sting
| bark scorpion venom (injected)
| Being stung by a [[bark scorpion]], [[giant bark scorpion]] or [[bark scorpion man]]
| Strong pain
| None
| None
|-
| Black mamba bite
| black mamba venom (injected)
| Being bitten by a [[black mamba]], [[giant black mamba]] or [[black mamba man]]
| Dizziness Drowsiness Strong pain Fever Unconsciousness Complete paralysis1
| None
| None
|-
| Blob blisters
| cave blob fluid (contact or ingested)
| Touching a [[cave blob]]
| Mild pain Mild blisters
| None
| None
|-
| Brown recluse spider bite
| brown recluse spider venom (injected)
| Being bitten by a [[brown recluse spider]], [[giant brown recluse spider]] or [[brown recluse spider man]]
| Nausea Fever Pain 
| Severe localized necrosis
| None
|-
| Bumblebee sting
| bumblebee venom (injected)
| Being stung by a [[bumblebee]] worker
| Pain Strong swelling
| None
| None
|-
| Bushmaster bite
| bushmaster venom (injected)
| Being bitten by a [[bushmaster]], [[giant bushmaster]] or [[bushmaster man]]
| Strong pain Mild bleeding Dizziness Nausea Unconsciousness Complete paralysis1
| None
| None
|-
| Cave floater sickness
| cave floater gas (inhaled or ingested)
| Expelled from [[cave floater]]
| Mild nausea
| Fever Strong drowsiness (delayed) Strong dizziness (delayed)
| None
|-
| Cave spider bite
| cave spider venom (injected)
| Being bitten by a [[cave spider]]
| None
| None
| Very mild dizziness
|-
| Copperhead snake bite
| copperhead snake venom (injected)
| Being bitten by a [[copperhead snake]], [[giant copperhead snake]] or [[copperhead snake man]]
| Pain Swelling Nausea
| None
| None
|-
| Giant cave spider bite
| giant cave spider venom (injected)
| Being bitten by a [[giant cave spider]]
| Size-dependant paralysis.
| Death by asphyxiation, in small targets. Large targets are generally unhindered...unless you count the high probability of being eaten by the giant cave spider as a hindrance.
| None, not that it really matters.
|-
| Gila monster bite
| gila monster venom (injected)
| Being bitten by a [[gila monster]], [[giant gila monster]] or [[gila monster man]]
| Pain Mild swelling
| None
| None
|-
| Gnomeblight
| [[gnomeblight]] (contact, inhaled, injected, or ingested)
| Purposely exposing oneself to the extract. Only affects [[mountain gnome]]s and [[dark gnome]]s.
| None
| Severe systemic necrosis2
| None
|-
| Giant desert scorpion sting
| giant desert scorpion venom (injected)
| Being stung by a [[giant desert scorpion]]
| Necrosis of the brain and nervous system
| '''Certain death'''
| None, not that it really matters.
|-
| Helmet snake bite
| helmet snake venom (injected)
| Being bitten by a [[helmet snake]]
| Minor bleeding
| Fever Nausea Dizziness Localized swelling Localized oozing Localized bruising Strong pain Intense localized necrosis Possible loss of limb
| None
|-
| Honey bee sting
| honey bee venom (injected)
| Being stung by a [[honey bee]] worker
| Pain Strong swelling
| None
| None
|-
| Inebriation{{version|0.42.01}}
| [[Alcohol]] (consumed/injected)
| Consuming alcoholic drinks
| Nausea Dizziness Unconsciousness Personality changes Euphoria Erratic behavior Trouble breathing
| None
| None
|-
| Iron man cough
| iron man gas (inhaled)
| Expelled by [[iron man]]
| Coughing blood
| None
| None
|-
| King cobra bite
| king cobra venom (injected)
| Being bitten by a [[king cobra]]
| Complete paralysis1 Pain, dizziness, drowsiness
| None
| None
|-
| Phantom spider bite
| phantom spider venom (injected)
| Being bitten by a [[phantom spider]]
| None
| Numbness and mild dizziness
| None
|-
| Platypus sting
| platypus venom (injected)
| Being kicked by a [[platypus]], [[giant platypus]] or [[platypus man]]
| Pain and swelling
| Extreme pain, swelling possibly to the point of necrosis
| None
|-
| Rattlesnake bite
| rattlesnake venom (injected)
| Being bitten by a [[rattlesnake]], [[giant rattlesnake]] or [[rattlesnake man]]
| Pain, nausea, blisters, swelling, bruising
| Severe localized necrosis
| None
|-
| Serpent man bite
| serpent man venom (injected)
| Being bitten by a [[serpent man]]
| Complete paralysis1
| None
| None
|-
| Mummy's curse
| [[DF2014:Mummy|Disturbance interaction]].
| Being cursed by a [[mummy]], when caught raiding their tombs
| None
| None
| 20% chance of any skill roll failing, regardless of skill.
|-
| Vampirism
| [[Deity|Divine]] Curse.
| Drinking the blood of a [[vampire]]. Toppling statues in shrines in Adventure Mode or temples in Fortress Mode (random chance).
| None
| None
| Victim becomes a [[vampire]].
|-
| Werebeast Curse
| [[Deity|Divine]] Curse.
| Being bitten by a [[werebeast]] or toppling statues in shrines in Adventure Mode (random chance).
| None
| None
| Victim becomes a [[werebeast]].
|-
| Necromancy
| [[Deity|Divine]] Curse.
| Reading a book/slab that contains the secrets of life and death.
| None
| None
| Reader becomes a [[Necromancer]].
|-
| evil rain sickness3
|rowspan=7| Random
| Being caught outside in [[Weather#Evil weather|freakish weather]] in an evil [[biome]]
|rowspan=7| Random
|rowspan=7| Random
|rowspan=7| Random
|-
| evil cloud sickness4
| Being caught in a [Weather#Evil weather|creeping cloud]] in an evil [[biome]]
|-
| beast sickness5
| Encounters with [[forgotten beast]]s
|-
| titan sickness5
| Encounters with [[titan]]s
|-
| night sickness5
| Encounters with [[werebeast]]s or [[experiment]]s
|-
| demon sickness5
| Encounters with [[demon]]s
|-
| divine sickness5
| Encounters with [[angel]]s
|}
: 1. For small creatures such as humans and dwarves, paralysis tends to result in suffocation.
: 2. Necrosis of the brain will eventually result in death once the brain rots away completely.
: 3. Evil rain typically only causes minor symptoms such as blisters, bruising, coughing blood, dizziness, fever, nausea, oozing, and pain.
: 4. Evil clouds either cause major symptoms (as with beast/titan/demon sicknesses) or permanently transform creatures into [[Undead|zombie-like]] forms.
: 5. [[Titan]]s, [[forgotten beast]]s, [[werebeast]]s, [[experiment]]s, [[demon]]s and [[angel]]s have a chance to have a randomized syndrome. These range from mildly hazardous (mild [[Symptoms#Blisters|blisters]] from inhaling boiling blood) to instantly fatal (severe necrosis from a contact poison attached to a breath weapon/creature made of blood).

==The anatomy of a syndrome==
Mechanically, syndromes are bundles of tokens attached to a material (or to an interaction effect; see below) - they're confined to creature materials in vanilla DF, but it's a simple matter to add them to inorganic materials. When the material is injected, touched, inhaled, or ingested (depending on the syndrome), the creature suffers the predations of a nasty disease or poison. Here's an example syndrome, taken from the Giant Cave Spider raws.

If you are having troubles getting the syndromes to work (i.e., in combat reports, getting "'''supersnake''' n/a splatters~etc"), then simply throw the venom template into the actual creature's raw, which is what the LOCAL_CREATURE_MAT actually calls on; the venom being in the same file.

[USE_MATERIAL_TEMPLATE:VENOM:CREATURE_EXTRACT_TEMPLATE]
[STATE_NAME:ALL_SOLID:frozen giant cave spider venom]
[STATE_ADJ:ALL_SOLID:frozen giant cave spider venom]
[STATE_NAME:LIQUID:giant cave spider venom]
[STATE_ADJ:LIQUID:giant cave spider venom]
[STATE_NAME:GAS:boiling giant cave spider venom]
[STATE_ADJ:GAS:boiling giant cave spider venom]
[PREFIX:NONE]
[ENTERS_BLOOD]
[SYNDROME]
[SYN_NAME:giant cave spider bite]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[SYN_IMMUNE_CREATURE:SPIDER_CAVE:ALL]
[SYN_INJECTED]
[CE_PARALYSIS:SEV:100:PROB:100:RESISTABLE:SIZE_DILUTES:START:5:PEAK:10:END:20]

The first line, USE_MATERIAL_TEMPLATE, is creating a new material, called POISON, using the CREATURE_EXTRACT_TEMPLATE as the basis. After this, the STATE_NAME and STATE_ADJ tokens are used to define the names and adjectives assigned to different states of the material - GAS, LIQUID and ALL_SOLID, in this case, though ALL is also a valid token. At this stage, you can use any material tags like MAT_FIXED_TEMP or similar to set further material properties, though this usually isn't necessary.

ENTERS_BLOOD
This tag determines whether a poison enters the blood or not. If it is not included, the poison will splatter (if liquid) or flow (if gas) over the affected body part instead when injected. If you're using a contact poison, leave this out. Necessary for injected poisons.
SYNDROME
This tag ends the material details and begins the definition of the actual syndrome.
SYN_NAME
This one is self-explanatory - the name of the syndrome as it will appear in-game.
SYN_AFFECTED_CLASS
This token defines what CREATURE_CLASS will be affected by the syndrome. Most creatures are classed under GENERAL_POISON. Multiple tokens can be used in a single syndrome.
SYN_IMMUNE_CLASS
As above, but makes class immune.
SYN_IMMUNE_CREATURE
This token defines which creatures CANNOT be affected by the syndrome - useful for addressing specific instances within a population, such as a specific caste or an individual creature that falls under GENERAL_POISON. Syntax is [SYN_IMMUNE_CREATURE:creature:caste]. ALL can be used for the caste.
SYN_AFFECTED_CREATURE
As above, but makes creature or caste susceptible.
SYN_CLASS
This tag sets a class for the syndrome that can be used in [[Interaction token|interactions.]]
SYN_IDENTIFIER{{version|0.42.01}}.
Similar to SYN_CLASS, this sets an identifier that can be shared between multiple syndromes, for use with the SYNDROME_DILUTION_FACTOR creature token. In vanilla DF, this is used to allow dwarves to drink more alcohol before becoming inebriated.
SYN_NO_HOSPITAL{{version|0.42.01}}.
Probably prevents affected dwarves from being carried to the hospital.{{verify}}
SYN_CONCENTRATION_ADDED:x:x{{version|0.42.01}}.
Repeated exposure to the syndrome will result in the effects becoming more intense. In vanilla [SYN_CONCENTRATION_ADDED:100:1000] is used with alcohol.

SYN_INJECTED, SYN_CONTACT, SYN_INHALED, SYN_INGESTED
This token determines the method of infection - injected syndromes must be injected via a creature attack, while contact syndromes result from any contamination of a creature by material splatter (such as blood), inhaled syndromes must be inhaled in gaseous form (such as from boiling or a creature breath attack), and ingestion syndromes must be eaten or drunk. Any combination of these tags can be used. A fun variation on the usual creature injection routine is to create a material with a SYN_CONTACT syndrome and have a creature use it for blood - this tends to end poorly for any predator that chooses to attack them.

[SPECIALATTACK_INJECT_EXTRACT:LOCAL_CREATURE_MAT:VENOM:LIQUID:100:100]
This is one method for getting a poison into a creature. If [ENTERS_BLOOD] is applied, it will be injected into the bloodstream. Otherwise, it will just splatter over the area. Put this on a creature attack. Substance type (gas, liquid, solid) does not appear to have an effect. The numbers on the end are minimum and maximum.

CE_X, or creature effect tokens, are the real meat and bones of your syndrome. They're detailed below.

==Creature effect tokens==
Each and every syndrome has a number of creature effect tokens, represented by CE_X - these lovely little beauties determine exactly how the poor creature suffering from the syndrome is affected. An example CE token is as follows:

[CE_NECROSIS:SEV:100:PROB:100:LOCALIZED:VASCULAR_ONLY:RESISTABLE:START:50:PEAK:1000:END:2000]

In this example, we have an effect that will always cause severe necrosis in whichever bodypart it touches, so long as that bodypart is vascular and that the creature is not able to resist it in some manner. The effect begins shortly after the syndrome is contracted, peaks 1000 [[time|time units]] afterwards, and finally ceases another 1000 time units later.

As a general rule of thumb, so long as CE_X starts the string and START/(PEAK/END) ends it, the order of the intervening tokens isn't important. PEAK and END aren't required.

*CE_X
The effect type. This can be a number of different tokens, as detailed in the table below this list.
*SEV:X
The severity of the effect. Higher values appear to be worse, with SEV:1000 CE_NECROSIS causing a part to near-instantly become rotten.
*PROB:X
The probability of the effect actually manifesting in the victim, as a percentage. 100 means always, 1 means a 1 in 100 chance.
*LOCALIZED (Overwrites BP tokens)
This tag causes an effect to ignore all BP tokens and then forces the game to attempt to apply the effect to the limb that came into contact with the contagion - i.e. the part that was bitten by the creature injecting the syndrome material, or the one that was splattered by a contact contagion. If an effect can not be applied to the contacted limb (such as IMPAIR_FUNCTION on a non-organ) then this token makes the syndrome have no effect. This token also makes inhaled syndromes have no effect.
*BP:BODY_PART:TISSUE (Overwritten by LOCALIZED)
Specifies which body parts and tissues are to be affected by the syndrome. BODY_PART can be BY_CATEGORY:x to target body parts with a matching [CATEGORY:x] [[body token]] (or ALL to affect everything), BY_TYPE:x to target body parts having a particular type (UPPERBODY, LOWERBODY, HEAD, GRASP, or STANCE), or BY_TOKEN:x to target individual body parts by their ID (as specified in the [BP] token). For example, if you wanted to target the lungs of a creature, you would use BP:BY_CATEGORY:LUNG:ALL. The syndrome would act on all bodyparts within the creature with the CATEGORY tag LUNG and affect all tissue layers. For another example, say you wanted to cause the skin to rot off a creature - you could use BP:BY_CATEGORY:ALL:SKIN, targeting the SKIN tissue on all bodyparts. Multiple targets can be given in one syndrome by placing the BP tokens end to end. This is one of the most powerful and useful aspects of the syndrome system, as it allows you to selectively target bodyparts relevant to the contagion, like lungs for coal dust inhalation, or the eyes for exposure to an acid gas. Not everything takes a target!
*VASCULAR_ONLY (Optional)
This syndrome only affects tissue layers with the VASCULAR token.
*MUSCULAR_ONLY (Optional)
This syndrome only affects tissue layers with the MUSCULAR token. Are you seeing a trend here?
*SIZE_DILUTES (Optional)
This token presumably causes the effects of the syndrome to scale with the size of the creature compared to the size of the dose of contagion they received, but has yet to be extensively tested.
*SIZE_DELAYS (Optional)
As above, this token has yet to be tested but presumably delays the onset of a syndrome according to the size of the victim.
*DWF_STRETCH:X{{version|0.42.01}} (Optional)
Multiplies the duration of the syndrome by X in Fortress mode. If X is 72, syndrome will last the same amount of ticks in fortress and adventure mode.
*ABRUPT{{version|0.42.01}} (Optional)
Makes the symptom begin immediately rather than ramping up. {{verify}}
*CAN_BE_HIDDEN (Optional)
Can be hidden by a unit assuming a secret identity, such as a [[vampire]]. {{verify}}
*RESISTABLE (Optional)
Determines if the effect can be hindered by the target creature's [[Attribute#Disease_Resistance|disease resistance attribute]]. Without this token, disease resistance is ignored.

The details of this table are still being thrashed out by modders, so if you have anything to add, please don't hesitate to hit the edit button!

Non-targeted syndromes will ignore any BP tokens and LOCALIZED tokens.
{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Description
|-
| CE_BLEEDING
| Yes
| Causes the targeted bodypart to start bleeding, with heavy enough bleeding resulting in the death of the sufferer. Some conditions seem to cause bleeding to be fatal no matter how weak.
|-
| CE_BLISTERS
| Yes
| Covers the targeted bodypart with blisters.
|-
| CE_BRUISING
| Yes
| Causes the targeted bodypart to undergo bruising.
|-
| CE_IMPAIR_FUNCTION
| Yes
| An organ afflicted with this CE is rendered inoperable - for example, if both lungs are impaired the creature can't breathe and will suffocate. This token only affects organs, not limbs. Note that this effect is currently bugged, and will not "turn off" until the creature receives a wound to cause its body parts to update.
|-
| CE_NECROSIS
| Yes
| Causes the targeted bodypart to rot, with associated tissue damage, miasma emission and bleeding. The victim slowly bleeds to death if the wound is not treated. Badly necrotic limbs will require amputation.
|-
| CE_NUMBNESS
| Yes
| Causes numbness in the affected body part, blocking pain. Extreme numbness may lead to sensory nerve damage.
|-
| CE_OOZING
| Yes
| Causes pus to ooze from the afflicted bodypart.
|-
| CE_PAIN
| Yes
| Afflicts the targeted bodypart with intense pain.
|-
| CE_PARALYSIS
| Yes
| Causes paralysis. Paralysis is complete paralysis and will cause suffocation in smaller creatures. Paralysis on a limb may lead to motor nerve damage.
|-
| CE_SWELLING
| Yes
| Causes the targeted bodypart to swell up. Extreme swelling may lead to necrosis.
|-
| CE_COUGH_BLOOD
| No
| This effect results in the sufferer periodically coughing blood, which stains the tile they're on and requires cleanup. It doesn't appear to be lethal, but may cause minor bleeding damage.
|-
| CE_DIZZINESS
| No
| Inflicts the Dizziness condition, occasional fainting and a general slowdown in movement and work speed.
|-
| CE_DROWSINESS
| No
| Causes the Drowsiness condition.
|-
| CE_FEVER
| No
| Causes the Fever condition.
|-
| CE_NAUSEA
| No
| Causes the Nausea condition, and heavy vomiting. Can eventually lead to dehydration and death.
|-
| CE_UNCONSCIOUSNESS
| No
| Renders unconscious.
|-
| CE_VOMIT_BLOOD
| No
| This effect results in the sufferer periodically vomiting blood, which stains the tile they're on and requires cleanup. It doesn't appear to be lethal, but may cause minor bleeding damage.
|-
| CE_ERRATIC_BEHAVIOR{{version|0.42.01}}
| No
| Causes erratic behavior, meaning "People that like to brawl have a chance of starting a brawl-level fight with any nearby adult" [http://www.bay12forums.com/smf//index.php?topic=159164.msg7632503#msg7632503 -Toady]
|}
====Healing Effects====
Starting with DF version 0.47.01, there are healing counterparts to most of the tokens above that will heal various syndrome effects or physical damage.
{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Description
|-
| CE_STOP_BLEEDING
| Yes?
| Decreases the severity of the bleeding of any wounds or syndrome effects on the targeted bodypart. The SEV value probably controls by how much the bleeding is decreased.
|-
| CE_CLOSE_OPEN_WOUNDS
| Yes?
| Closes any wounds on the targeted bodypart with speed depending on the SEV value.
|-
| CE_HEAL_TISSUES
| Yes?
| Heals the tissues of the targeted bodypart with speed depending on the SEV value.
|-
| CE_HEAL_NERVES
| Yes?
| Heals the nerves of the targeted bodypart with speed depending on the SEV value.
|-
| CE_REDUCE_PAIN
| Yes?
| Decreases the severity of pain produced by wounds or syndrome effects on the targeted bodypart. The SEV value probably controls by how much the pain is decreased.
|-
| CE_REDUCE_SWELLING
| Yes?
| Decreases the severity of swelling on the targeted bodypart.
|-
| CE_CURE_INFECTION
| Yes?
| Probably decreases the severity of the infection from infected wounds over time.
|-
| CE_REDUCE_PARALYSIS
| Yes?
| Decreases the severity of any paralysis effects on the targeted bodypart.
|-
| CE_REGROW_PARTS
| Yes
| Causes missing bodyparts to regrow. SEV controls how quickly bodyparts are regrown. In adventure, parts will be regrown until you travel or wait/sleep {{bug|0011396}}.
|-
| CE_REDUCE_DIZZINESS
| No
| Decreases the severity of any dizziness the creature has.
|-
| CE_REDUCE_NAUSEA
| No
| Decreases the severity of any nausea the creature has.
|-
| CE_REDUCE_FEVER
| No
| Decreases the severity of any fever the creature has.
|}

===Special Effects===
Several special syndrome effects take different arguments than the above. These are used for generated interactions in unmodded games, but may be used as well for any substance or custom interaction.

{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Arguments
! Description
|-
| CE_ADD_TAG
| No
| tags
| Adds a tag to the affected creature. Many arguments can be used sequentially within one syndrome token. Valid tags are the same as that of the [[interaction token]] '''IT_REQUIRES''', ie.

BLOODSUCKER, CAN_LEARN, CAN_SPEAK, CRAZED, EXTRAVISION, LIKES_FIGHTING (or LIKESFIGHTING), MISCHIEVOUS (or MISCHIEVIOUS), NO_CONNECTIONS_FOR_MOVEMENT, NO_DIZZINESS, NO_DRINK, NO_EAT, NO_FEVERS, NO_PHYS_ATT_GAIN, NO_PHYS_ATT_RUST, NO_SLEEP, NO_THOUGHT_CENTER_FOR_MOVEMENT, NOBREATHE, NOEMOTION, NOEXERT, NOFEAR, NONAUSEA, NOPAIN, NOSTUN, NOT_LIVING, NOTHOUGHT, OPPOSED_TO_LIFE, PARALYZEIMMUNE, SUPERNATURAL, TRANCES, NO_AGING, STERILE, UTTERANCES.
|-
| CE_REMOVE_TAG
| No
| tags
| Removes a tag from a creature. Supported arguments are the same as CE_ADD_TAG.
|-
| CE_DISPLAY_TILE
| No
| TILE:[[Tilesets|tile number]]:[[Color#Modding color|colour]]
| The creature displays the specified tile and colour instead of its normal one.
|-
| CE_DISPLAY_NAME
| No
| NAME:singular:plural:adjective
| Attaches a specified name to the creature's normal name.
|-
| CE_FLASH_TILE
| No
| TILE:tile number:colour:FREQUENCY:ticks default tile:ticks syndrome tile
| The creature flashes between its normal tile and the one specified here.
|-
| CE_PHYS_ATT_CHANGE
| No
| [[Attribute]]:percentage:fixed boost(?)
| Alters the physical [[attribute]]s of a creature.
|-
| CE_MENT_ATT_CHANGE
| No
| [[Attribute]]:percentage:fixed boost(?)
| Alters the mental [[attribute]]s of a creature.
|-
| CE_BODY_APPEARANCE_MODIFIER
| No
| APPEARANCE_MODIFIER:HEIGHT/LENGTH/BROADNESS:percentage(?)
| Alters the size of the creature.
|-
| CE_BP_APPEARANCE_MODIFIER
| Yes
| body part:APPEARANCE_MODIFIER:attribute:number]
| Alters the characteristics (height, width etc.) of a body part.
|-
| CE_MATERIAL_FORCE_MULTIPLIER
| No
| MAT_MULT:[[material token|material]]:A:B
| Makes creature affected by materials more or less by a factor of A/B. If A is 3 and B is 2, the creature will be 1.5x weaker to the defined material (can be NONE:NONE for all); if 2:3, the creature will be 1.5 times stronger.
|-
| CE_SPEED_CHANGE
| No
| speed modifier:number
| Changes the speed of a creature.
Speed modifier contains one or both of:
* SPEED_PERC:percentage (this modifies a creature's in-game speed, so higher numbers are faster)
* SPEED_ADD:number (this modifies a creature's [SPEED:XX] token, so higher numbers are slower. Negative numbers are accepted though will only reduce a creature's speed to zero)
The minimum and maximum speeds able to be created by CE_SPEED_CHANGE are 99 and 10,000 respectively.

|-
| CE_CAN_DO_INTERACTION
| No
|
| Makes the creature able to perform an interaction. See [[Interaction token]]. To specify the interaction, use the argument:
* CDI:INTERACTION:interaction name
|-
| CE_SPECIAL_ATTACK_INTERACTION{{version|0.47.01}}
| Yes
| INTERACTION:<interaction name>:BP:<selection criteria>:<name of category,type, or token of designated part/parts>
| Makes the creature able to perform an interaction when using an attack with a designated body part/parts. See [[#Spreading diseases in 0.47.01|below]] for an example

|-
| CE_BODY_MAT_INTERACTION
| No
| MAT_TOKEN:<body material token>
| Causes one of the creature's body materials to trigger an interaction when the material is ingested, injected, etc (depending on the [CE:SYNDROME_TAG]s used; note that more than one may be specified). Generated vampire syndromes use '''RESERVED_BLOOD''' as the body material token in this syndrome tag, so as to specify the blood material of any creature with the syndrome. The following tokens should be inserted after this:
* '''CE:INTERACTION:interaction_id''' - replace 'interaction_id' with the name of the target interaction
* '''CE:SYNDROME_TAG:syndrome_trigger_type''' - replace 'syndrome_trigger_type' with any of SYN_INGESTED, SYN_INJECTED, SYN_CONTACT, SYN_INHALED
The linked interaction must have an [[Interaction_token#I_SOURCE|[I_SOURCE:INGESTION]]] token for this to work!

Note that this currently only works on materials obtained from historical figures and has only been tested with ingested materials linked to interactions with ADD_SYNDROME interaction effects.

|-
| CE_BODY_TRANSFORMATION
| No
| PROB:percentage:START:time:END:time
| Transforms into another creature. PROB and END arguments optional. The target creature may either be specified directly using CE:CREATURE or else set to be randomly selected as guided by creature and/or caste flag restrictions (of which multiple may be specified).
* CE:CREATURE:CREATURE_ID:CASTE_ID - Specify the creature and caste (for example: CE:CREATURE:DWARF:FEMALE). ANY can be used in place of a specific CASTE_ID to randomise the caste for every transformation. 
* CE:CREATURE_FLAG:FLAG{{version|0.47.01}} - Any creature with the specified [[:Interaction_token#Creature_and_Caste_Flags|creature flag]] is a valid transformation target. 
* CE:FORBIDDEN_CREATURE_FLAG{{version|0.47.01}} - Forbids all creatures with the specified [[:Interaction_token#Creature_and_Caste_Flags|creature flag]] from being randomly selected. 
* CE:CREATURE_CASTE_FLAG:FLAG{{version|0.47.01}} - Any creature with the specified [[:Interaction_token#Creature_and_Caste_Flags|caste flag]] is a valid transformation target. 
* CE:FORBIDDEN_CREATURE_CASTE_FLAG{{version|0.47.01}} - Forbids all creatures with the specified [[:Interaction_token#Creature_and_Caste_Flags|caste flag]] from being randomly selected. 
*CE:HAVE_FAST_EFFORTLESS_GAIT_SPEED{{version|0.47.01}} - Unknown. Possibly disallows all creatures with only slow gaits.{{verify}}

Note that any wounds the creature has suffered will instantly heal upon transforming, both into and out of the target form. [[Undead]] limbs of a creature with this token will grow into a full instance of that creature.
|-
| CE_SKILL_ROLL_ADJUST
| No
| PERC:percentage:PERC_ON:percentage
| Alters the skill level of a creature. The argument PERC specifies a percentage of the creature's current skill, and PERC_ON the probability of the effect being applied on a particular roll.
|-
| CE_SENSE_CREATURE_CLASS
| No
| START:time:CLASS:creature class:tile:color
| Allows creature to see other creatures with given class through walls. Vampires, for example, have START:0:CLASS:GENERAL_POISON:15:4:0:1.
|-
| CE_CHANGE_PERSONALITY{{version|0.42.01}}
| No
| FACET:[[DF2014:Personality_trait#Facets|trait]]:amount
| Changes a [[personality trait]] by amount. Multiple FACET:trait:amount sets may be used.
|-
| CE_FEEL_EMOTION{{version|0.42.01}}
| No
| EMOTION:[[emotion]]
| Makes the creature feel a specific [[emotion]]; severity based on standard SEV value. The [[thought]] the creature receives is: "[creature] feels [emotion] due to [syndrome name]". See [[Emotion]] for the list of valid emotions.
|}

'''All''' creature effect tokens take START, END and PROB numbers, and can be followed by [CE:PERIODIC] and/or [CE:COUNTER_TRIGGER] to restrict when they actually take effect.
* PERIODIC:period_type:min_value:max_value
* {{text anchor|COUNTER_TRIGGER}}:counter_name:min_value:max_value:REQUIRED

Currently, the only valid period type is MOON_PHASE.

===Counter Triggers===
Valid counter values are below:

{| {{prettytable}}
|- bgcolor="Bisque"
! Counter
! Description
|-
| ALCOHOLIC
| How long it's been (in [[time]] units) since the creature last had a drink of alcohol. Only present on creatures who need alcohol to get through the working day.
* 100800 (3 months) = and is starting to work slowly due to its scarcity
* 201600 (6 months) = and really wants a drink
* 302400 (9 months) = and has gone without a drink for far, far too long
* 403200 (1 year) = and can't even remember the last time he/she had some
|-
| CAVE_ADAPT
| How cave-adapted the creature is. Increases by 1 for every [[time]] unit spent underground, to a maximum of 800000.
* 403200 (1 year) = going outside causes irritation
* 604800 (1.5 years) = going outside causes nausea
|-
| PARTIED_OUT
| How long before the creature will decide to attend another party. Starts at 3+ months and counts down to zero.
|-
| MILK_COUNTER
| How long before the creature can be milked again. Starts at the creature's MILK frequency and counts down to zero.
|-
| EGG_SPENT
| How long before the creature can lay more eggs. Starts at 3 months and counts down to zero.
|-
| GROUNDED_ANIMAL_ANGER
| How angry (and likely to attack) an animal is from being over-crowded. Increases when over-crowded and otherwise counts down to zero.
|-
| TIME_SINCE_SUCKED_BLOOD
| How long it's been (in [[time]] units) since the creature last sucked somebody's blood.
|-
| DRINKING_BLOOD
| How much longer the creature will be drinking somebody's blood. Starts at 2.4 days and counts down to zero.
|}

{{mod}}

==Inorganic syndromes and you!==
It's perfectly possible - and quite simple - to add a nasty syndrome to a type of rock or metal - you simply add the syndrome tokens to the material definition in the same manner that you would add them to a creature material definition. The only catch is that since your hapless dwarves will only normally encounter the material in metal, gem or boulder form, a bit of creativity must be used to actually get them inside your citizens - that is, you need to make them 'explosively boil' as soon as they're mined or produced. This has the sad side effect of destroying the actual item - sorry, no highly radioactive uranium this release.

The easiest way to accomplish this is to assign the material a low boiling point, usually just under room temperature, and make sure its temperature is fixed to a point above it.
[MELTING_POINT:NONE]
[BOILING_POINT:10000]
[MAT_FIXED_TEMP:10001]
Now, as soon as this substance hits the open air - by being mined, smelted or reaction-produced at a custom workshop - it will EXPLOSIVELY BOIL, flooding a small area with delicious syndrome-rich gas. Creatures who inhale the gas will be immediately hit with the syndrome you thoughtfully attached to the material definition earlier!

There are a number of other tokens you can use to control the colour and naming conventions of your syndrome material, referred to as [[material definition token]]s.

==Spreading diseases==
It's fully possible to make a nasty disease capable of spreading itself from an infected dwarf to others, though it requires some skill in modding [[interaction token|interactions]] as well. Here is an example of a plague-inflicting interaction:

[INTERACTION:PLAGUE]
[I_TARGET:A:CREATURE]
[IT_LOCATION:CONTEXT_CREATURE]
[IT_FORBIDDEN:NOT_LIVING]
[IT_AFFECTED_CLASS:GENERAL_POISON]
[IT_MANUAL_INPUT:creatures]
[I_EFFECT:ADD_SYNDROME]
[IE_TARGET:A]
[IE_IMMEDIATE]
[SYNDROME]
[SYN_NAME:the plague]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[CE_FEVER:SEV:250:PROB:100:START:250:PEAK:1500:END:25000]
[CE_BLISTERS:SEV:325:PROB:100:BP:BY_CATEGORY:ALL:SKIN:START:250:PEAK:1500:END:25000]
[CE_NECROSIS:SEV:300:PROB:100:BP:BY_CATEGORY:ALL:ALL:VASCULAR_ONLY:START:22500:PEAK:23750:END:25000]
[CE_CAN_DO_INTERACTION:START:1500:END:25000]
[CDI:ADV_NAME:Spread the plague]
[CDI:INTERACTION:PLAGUE]
[CDI:TARGET:A:LINE_OF_SIGHT]
[CDI:TARGET_RANGE:A:10]
[CDI:WAIT_PERIOD:30]

As you can see, the syndrome here inflicts blisters, fever and, after roughly a month, necrosis of the whole body - that's when the infected creatures will start dying out. But before that happens, CE_CAN_DO_INTERACTION makes them capable of spreading the plague further.

You also need a disease vector that will bring the plague straight to your fort. (hint: use [[large rat|various]] [[rat man|species]] [[giant rat|of rats]] - they're perfect for that). The following code, added to a creature's raws, ensures the creature will infect anybody it encounters:

[CAN_DO_INTERACTION:PLAGUE]
[CDI:ADV_NAME:Spread the plague]
[CDI:TARGET:A:LINE_OF_SIGHT]
[CDI:TARGET_RANGE:A:10]
[CDI:WAIT_PERIOD:30]

As soon as the said creature is startled by your dwarves, the [[fun]] will begin.

==''In 0.47.01''==
As of version 0.47.01, it may be possible to use a creature's established methods of attack for use in disease-spreading.

Let's use the borrowed example of the plague above. This time, the plague will spread through biting, using the following syndrome code:

[INTERACTION:PLAGUE]
[I_TARGET:A:CREATURE]
[IT_LOCATION:CONTEXT_CREATURE]
[IT_FORBIDDEN:NOT_LIVING]
[IT_AFFECTED_CLASS:GENERAL_POISON]
[IT_MANUAL_INPUT:creatures]
[I_EFFECT:ADD_SYNDROME]
[IE_TARGET:A]
[IE_IMMEDIATE]
[SYNDROME]
[SYN_NAME:the plague]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[CE_FEVER:SEV:250:PROB:100:START:250:PEAK:1500:END:25000]
[CE_BLISTERS:SEV:325:PROB:100:BP:BY_CATEGORY:ALL:SKIN:START:250:PEAK:1500:END:25000]
[CE_NECROSIS:SEV:300:PROB:100:BP:BY_CATEGORY:ALL:ALL:VASCULAR_ONLY:START:22500:PEAK:23750:END:25000]
[CE_SPECIAL_ATTACK_INTERACTION:INTERACTION:PLAGUE:BP:BY_CATEGORY:TOOTH:START:0:ABRUPT]

The line [CE_SPECIAL_ATTACK_INTERACTION:INTERACTION:BITE_PLAGUE:BP:BY_CATEGORY:MOUTH:BP:BY_CATEGORY:TOOTH:START:0:ABRUPT] allows any infected creature with an attack using mouth or tooth category body parts to immediately spread the disease using said attack. The victim of the attack may then spread the disease if they are able to attack with the needed body part/parts.

{{Category|Modding}}
{{Category|Creature attributes}}
{{Category|Tokens}}
[[ru:DF2012:Syndrome]]

Syndrome

2020-06-30T07:57:29Z

Albedo:

{{Quality|Masterwork|13:02, 6 April 2015 (UTC)}}
{{av}}
[[File:Snakebite.png|200px|thumb|right|A single bite from a [[helmet snake]] lead to a slow, lingering death for this unfortunate hippo.]]
A '''syndrome''' is a specific combination of [[symptoms]] that a poor, helpless creature might get from a disease, venom or other effect, through encountering certain other creatures, substances, or supernatural [[weather]]. Syndromes generally cause unpleasant and frequently fatal symptoms over a short to long period of time, but some will clear up over time or with the assistance of a [[doctor]]. A [[Health care|hospital]] is required to diagnose and potentially treat those syndromes that can be helped by treatment.

==List of syndromes==
Syndromes are generally named after the animal, substance or effect that delivers them.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Syndrome
! Venom
! Acquired
! Short-term Symptoms
! Long-term Symptoms
! Chronic Symptoms
|-
| Adder bite
| adder venom (injected)
| Being bitten by an [[adder]], [[giant adder]] or [[adder man]]
| Strong pain
| Swelling Blisters Nausea
| None
|-
| Bark scorpion sting
| bark scorpion venom (injected)
| Being stung by a [[bark scorpion]], [[giant bark scorpion]] or [[bark scorpion man]]
| Strong pain
| None
| None
|-
| Black mamba bite
| black mamba venom (injected)
| Being bitten by a [[black mamba]], [[giant black mamba]] or [[black mamba man]]
| Dizziness Drowsiness Strong pain Fever Unconsciousness Complete paralysis1
| None
| None
|-
| Blob blisters
| cave blob fluid (contact or ingested)
| Touching a [[cave blob]]
| Mild pain Mild blisters
| None
| None
|-
| Brown recluse spider bite
| brown recluse spider venom (injected)
| Being bitten by a [[brown recluse spider]], [[giant brown recluse spider]] or [[brown recluse spider man]]
| Nausea Fever Pain 
| Severe localized necrosis
| None
|-
| Bumblebee sting
| bumblebee venom (injected)
| Being stung by a [[bumblebee]] worker
| Pain Strong swelling
| None
| None
|-
| Bushmaster bite
| bushmaster venom (injected)
| Being bitten by a [[bushmaster]], [[giant bushmaster]] or [[bushmaster man]]
| Strong pain Mild bleeding Dizziness Nausea Unconsciousness Complete paralysis1
| None
| None
|-
| Cave floater sickness
| cave floater gas (inhaled or ingested)
| Expelled from [[cave floater]]
| Mild nausea
| Fever Strong drowsiness (delayed) Strong dizziness (delayed)
| None
|-
| Cave spider bite
| cave spider venom (injected)
| Being bitten by a [[cave spider]]
| None
| None
| Very mild dizziness
|-
| Copperhead snake bite
| copperhead snake venom (injected)
| Being bitten by a [[copperhead snake]], [[giant copperhead snake]] or [[copperhead snake man]]
| Pain Swelling Nausea
| None
| None
|-
| Giant cave spider bite
| giant cave spider venom (injected)
| Being bitten by a [[giant cave spider]]
| Size-dependant paralysis.
| Death by asphyxiation, in small targets. Large targets are generally unhindered...unless you count the high probability of being eaten by the giant cave spider as a hindrance.
| None, not that it really matters.
|-
| Gila monster bite
| gila monster venom (injected)
| Being bitten by a [[gila monster]], [[giant gila monster]] or [[gila monster man]]
| Pain Mild swelling
| None
| None
|-
| Gnomeblight
| [[gnomeblight]] (contact, inhaled, injected, or ingested)
| Purposely exposing oneself to the extract. Only affects [[mountain gnome]]s and [[dark gnome]]s.
| None
| Severe systemic necrosis2
| None
|-
| Giant desert scorpion sting
| giant desert scorpion venom (injected)
| Being stung by a [[giant desert scorpion]]
| Necrosis of the brain and nervous system
| '''Certain death'''
| None, not that it really matters.
|-
| Helmet snake bite
| helmet snake venom (injected)
| Being bitten by a [[helmet snake]]
| Minor bleeding
| Fever Nausea Dizziness Localized swelling Localized oozing Localized bruising Strong pain Intense localized necrosis Possible loss of limb
| None
|-
| Honey bee sting
| honey bee venom (injected)
| Being stung by a [[honey bee]] worker
| Pain Strong swelling
| None
| None
|-
| Inebriation{{version|0.42.01}}
| [[Alcohol]] (consumed/injected)
| Consuming alcoholic drinks
| Nausea Dizziness Unconsciousness Personality changes Euphoria Erratic behavior Trouble breathing
| None
| None
|-
| Iron man cough
| iron man gas (inhaled)
| Expelled by [[iron man]]
| Coughing blood
| None
| None
|-
| King cobra bite
| king cobra venom (injected)
| Being bitten by a [[king cobra]]
| Complete paralysis1 Pain, dizziness, drowsiness
| None
| None
|-
| Phantom spider bite
| phantom spider venom (injected)
| Being bitten by a [[phantom spider]]
| None
| Numbness and mild dizziness
| None
|-
| Platypus sting
| platypus venom (injected)
| Being kicked by a [[platypus]], [[giant platypus]] or [[platypus man]]
| Pain and swelling
| Extreme pain, swelling possibly to the point of necrosis
| None
|-
| Rattlesnake bite
| rattlesnake venom (injected)
| Being bitten by a [[rattlesnake]], [[giant rattlesnake]] or [[rattlesnake man]]
| Pain, nausea, blisters, swelling, bruising
| Severe localized necrosis
| None
|-
| Serpent man bite
| serpent man venom (injected)
| Being bitten by a [[serpent man]]
| Complete paralysis1
| None
| None
|-
| Mummy's curse
| [[DF2014:Mummy|Disturbance interaction]].
| Being cursed by a [[mummy]], when caught raiding their tombs
| None
| None
| 20% chance of any skill roll failing, regardless of skill.
|-
| Vampirism
| [[Deity|Divine]] Curse.
| Drinking the blood of a [[vampire]]. Toppling statues in shrines in Adventure Mode or temples in Fortress Mode (random chance).
| None
| None
| Victim becomes a [[vampire]].
|-
| Werebeast Curse
| [[Deity|Divine]] Curse.
| Being bitten by a [[werebeast]] or toppling statues in shrines in Adventure Mode (random chance).
| None
| None
| Victim becomes a [[werebeast]].
|-
| Necromancy
| [[Deity|Divine]] Curse.
| Reading a book/slab that contains the secrets of life and death.
| None
| None
| Reader becomes a [[Necromancer]].
|-
| evil rain sickness3
|rowspan=7| Random
| Being caught outside in [[Weather#Evil weather|freakish weather]] in an evil [[biome]]
|rowspan=7| Random
|rowspan=7| Random
|rowspan=7| Random
|-
| evil cloud sickness4
| Being caught in a [Weather#Evil weather|creeping cloud]] in an evil [[biome]]
|-
| beast sickness5
| Encounters with [[forgotten beast]]s
|-
| titan sickness5
| Encounters with [[titan]]s
|-
| night sickness5
| Encounters with [[werebeast]]s or [[experiment]]s
|-
| demon sickness5
| Encounters with [[demon]]s
|-
| divine sickness5
| Encounters with [[angel]]s
|}
: 1. For small creatures such as humans and dwarves, paralysis tends to result in suffocation.
: 2. Necrosis of the brain will eventually result in death once the brain rots away completely.
: 3. Evil rain typically only causes minor symptoms such as blisters, bruising, coughing blood, dizziness, fever, nausea, oozing, and pain.
: 4. Evil clouds either cause major symptoms (as with beast/titan/demon sicknesses) or permanently transform creatures into [[Undead|zombie-like]] forms.
: 5. [[Titan]]s, [[forgotten beast]]s, [[werebeast]]s, [[experiment]]s, [[demon]]s and [[angel]]s have a chance to have a randomized syndrome. These range from mildly hazardous (mild [[Symptoms#Blisters|blisters]] from inhaling boiling blood) to instantly fatal (severe necrosis from a contact poison attached to a breath weapon/creature made of blood).

==The anatomy of a syndrome==
Mechanically, syndromes are bundles of tokens attached to a material (or to an interaction effect; see below) - they're confined to creature materials in vanilla DF, but it's a simple matter to add them to inorganic materials. When the material is injected, touched, inhaled, or ingested (depending on the syndrome), the creature suffers the predations of a nasty disease or poison. Here's an example syndrome, taken from the Giant Cave Spider raws.

If you are having troubles getting the syndromes to work (i.e., in combat reports, getting "'''supersnake''' n/a splatters~etc"), then simply throw the venom template into the actual creature's raw, which is what the LOCAL_CREATURE_MAT actually calls on; the venom being in the same file.

[USE_MATERIAL_TEMPLATE:VENOM:CREATURE_EXTRACT_TEMPLATE]
[STATE_NAME:ALL_SOLID:frozen giant cave spider venom]
[STATE_ADJ:ALL_SOLID:frozen giant cave spider venom]
[STATE_NAME:LIQUID:giant cave spider venom]
[STATE_ADJ:LIQUID:giant cave spider venom]
[STATE_NAME:GAS:boiling giant cave spider venom]
[STATE_ADJ:GAS:boiling giant cave spider venom]
[PREFIX:NONE]
[ENTERS_BLOOD]
[SYNDROME]
[SYN_NAME:giant cave spider bite]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[SYN_IMMUNE_CREATURE:SPIDER_CAVE:ALL]
[SYN_INJECTED]
[CE_PARALYSIS:SEV:100:PROB:100:RESISTABLE:SIZE_DILUTES:START:5:PEAK:10:END:20]

The first line, USE_MATERIAL_TEMPLATE, is creating a new material, called POISON, using the CREATURE_EXTRACT_TEMPLATE as the basis. After this, the STATE_NAME and STATE_ADJ tokens are used to define the names and adjectives assigned to different states of the material - GAS, LIQUID and ALL_SOLID, in this case, though ALL is also a valid token. At this stage, you can use any material tags like MAT_FIXED_TEMP or similar to set further material properties, though this usually isn't necessary.

ENTERS_BLOOD
This tag determines whether a poison enters the blood or not. If it is not included, the poison will splatter (if liquid) or flow (if gas) over the affected body part instead when injected. If you're using a contact poison, leave this out. Necessary for injected poisons.
SYNDROME
This tag ends the material details and begins the definition of the actual syndrome.
SYN_NAME
This one is self-explanatory - the name of the syndrome as it will appear in-game.
SYN_AFFECTED_CLASS
This token defines what CREATURE_CLASS will be affected by the syndrome. Most creatures are classed under GENERAL_POISON. Multiple tokens can be used in a single syndrome.
SYN_IMMUNE_CLASS
As above, but makes class immune.
SYN_IMMUNE_CREATURE
This token defines which creatures CANNOT be affected by the syndrome - useful for addressing specific instances within a population, such as a specific caste or an individual creature that falls under GENERAL_POISON. Syntax is [SYN_IMMUNE_CREATURE:creature:caste]. ALL can be used for the caste.
SYN_AFFECTED_CREATURE
As above, but makes creature or caste susceptible.
SYN_CLASS
This tag sets a class for the syndrome that can be used in [[Interaction token|interactions.]]
SYN_IDENTIFIER{{version|0.42.01}}.
Similar to SYN_CLASS, this sets an identifier that can be shared between multiple syndromes, for use with the SYNDROME_DILUTION_FACTOR creature token. In vanilla DF, this is used to allow dwarves to drink more alcohol before becoming inebriated.
SYN_NO_HOSPITAL{{version|0.42.01}}.
Probably prevents affected dwarves from being carried to the hospital.{{verify}}
SYN_CONCENTRATION_ADDED:x:x{{version|0.42.01}}.
Repeated exposure to the syndrome will result in the effects becoming more intense. In vanilla [SYN_CONCENTRATION_ADDED:100:1000] is used with alcohol.

SYN_INJECTED, SYN_CONTACT, SYN_INHALED, SYN_INGESTED
This token determines the method of infection - injected syndromes must be injected via a creature attack, while contact syndromes result from any contamination of a creature by material splatter (such as blood), inhaled syndromes must be inhaled in gaseous form (such as from boiling or a creature breath attack), and ingestion syndromes must be eaten or drunk. Any combination of these tags can be used. A fun variation on the usual creature injection routine is to create a material with a SYN_CONTACT syndrome and have a creature use it for blood - this tends to end poorly for any predator that chooses to attack them.

[SPECIALATTACK_INJECT_EXTRACT:LOCAL_CREATURE_MAT:VENOM:LIQUID:100:100]
This is one method for getting a poison into a creature. If [ENTERS_BLOOD] is applied, it will be injected into the bloodstream. Otherwise, it will just splatter over the area. Put this on a creature attack. Substance type (gas, liquid, solid) does not appear to have an effect. The numbers on the end are minimum and maximum.

CE_X, or creature effect tokens, are the real meat and bones of your syndrome. They're detailed below.

==Creature effect tokens==
Each and every syndrome has a number of creature effect tokens, represented by CE_X - these lovely little beauties determine exactly how the poor creature suffering from the syndrome is affected. An example CE token is as follows:

[CE_NECROSIS:SEV:100:PROB:100:LOCALIZED:VASCULAR_ONLY:RESISTABLE:START:50:PEAK:1000:END:2000]

In this example, we have an effect that will always cause severe necrosis in whichever bodypart it touches, so long as that bodypart is vascular and that the creature is not able to resist it in some manner. The effect begins shortly after the syndrome is contracted, peaks 1000 [[time|time units]] afterwards, and finally ceases another 1000 time units later.

As a general rule of thumb, so long as CE_X starts the string and START/(PEAK/END) ends it, the order of the intervening tokens isn't important. PEAK and END aren't required.

*CE_X
The effect type. This can be a number of different tokens, as detailed in the table below this list.
*SEV:X
The severity of the effect. Higher values appear to be worse, with SEV:1000 CE_NECROSIS causing a part to near-instantly become rotten.
*PROB:X
The probability of the effect actually manifesting in the victim, as a percentage. 100 means always, 1 means a 1 in 100 chance.
*LOCALIZED (Overwrites BP tokens)
This tag causes an effect to ignore all BP tokens and then forces the game to attempt to apply the effect to the limb that came into contact with the contagion - i.e. the part that was bitten by the creature injecting the syndrome material, or the one that was splattered by a contact contagion. If an effect can not be applied to the contacted limb (such as IMPAIR_FUNCTION on a non-organ) then this token makes the syndrome have no effect. This token also makes inhaled syndromes have no effect.
*BP:BODY_PART:TISSUE (Overwritten by LOCALIZED)
Specifies which body parts and tissues are to be affected by the syndrome. BODY_PART can be BY_CATEGORY:x to target body parts with a matching [CATEGORY:x] [[body token]] (or ALL to affect everything), BY_TYPE:x to target body parts having a particular type (UPPERBODY, LOWERBODY, HEAD, GRASP, or STANCE), or BY_TOKEN:x to target individual body parts by their ID (as specified in the [BP] token). For example, if you wanted to target the lungs of a creature, you would use BP:BY_CATEGORY:LUNG:ALL. The syndrome would act on all bodyparts within the creature with the CATEGORY tag LUNG and affect all tissue layers. For another example, say you wanted to cause the skin to rot off a creature - you could use BP:BY_CATEGORY:ALL:SKIN, targeting the SKIN tissue on all bodyparts. Multiple targets can be given in one syndrome by placing the BP tokens end to end. This is one of the most powerful and useful aspects of the syndrome system, as it allows you to selectively target bodyparts relevant to the contagion, like lungs for coal dust inhalation, or the eyes for exposure to an acid gas. Not everything takes a target!
*VASCULAR_ONLY (Optional)
This syndrome only affects tissue layers with the VASCULAR token.
*MUSCULAR_ONLY (Optional)
This syndrome only affects tissue layers with the MUSCULAR token. Are you seeing a trend here?
*SIZE_DILUTES (Optional)
This token presumably causes the effects of the syndrome to scale with the size of the creature compared to the size of the dose of contagion they received, but has yet to be extensively tested.
*SIZE_DELAYS (Optional)
As above, this token has yet to be tested but presumably delays the onset of a syndrome according to the size of the victim.
*DWF_STRETCH:X{{version|0.42.01}} (Optional)
Multiplies the duration of the syndrome by X in Fortress mode. If X is 72, syndrome will last the same amount of ticks in fortress and adventure mode.
*ABRUPT{{version|0.42.01}} (Optional)
Makes the symptom begin immediately rather than ramping up. {{verify}}
*CAN_BE_HIDDEN (Optional)
Can be hidden by a unit assuming a secret identity, such as a [[vampire]]. {{verify}}
*RESISTABLE (Optional)
Determines if the effect can be hindered by the target creature's [[Attribute#Disease_Resistance|disease resistance attribute]]. Without this token, disease resistance is ignored.

The details of this table are still being thrashed out by modders, so if you have anything to add, please don't hesitate to hit the edit button!

Non-targeted syndromes will ignore any BP tokens and LOCALIZED tokens.
{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Description
|-
| CE_BLEEDING
| Yes
| Causes the targeted bodypart to start bleeding, with heavy enough bleeding resulting in the death of the sufferer. Some conditions seem to cause bleeding to be fatal no matter how weak.
|-
| CE_BLISTERS
| Yes
| Covers the targeted bodypart with blisters.
|-
| CE_BRUISING
| Yes
| Causes the targeted bodypart to undergo bruising.
|-
| CE_IMPAIR_FUNCTION
| Yes
| An organ afflicted with this CE is rendered inoperable - for example, if both lungs are impaired the creature can't breathe and will suffocate. This token only affects organs, not limbs. Note that this effect is currently bugged, and will not "turn off" until the creature receives a wound to cause its body parts to update.
|-
| CE_NECROSIS
| Yes
| Causes the targeted bodypart to rot, with associated tissue damage, miasma emission and bleeding. The victim slowly bleeds to death if the wound is not treated. Badly necrotic limbs will require amputation.
|-
| CE_NUMBNESS
| Yes
| Causes numbness in the affected body part, blocking pain. Extreme numbness may lead to sensory nerve damage.
|-
| CE_OOZING
| Yes
| Causes pus to ooze from the afflicted bodypart.
|-
| CE_PAIN
| Yes
| Afflicts the targeted bodypart with intense pain.
|-
| CE_PARALYSIS
| Yes
| Causes paralysis. Paralysis is complete paralysis and will cause suffocation in smaller creatures. Paralysis on a limb may lead to motor nerve damage.
|-
| CE_SWELLING
| Yes
| Causes the targeted bodypart to swell up. Extreme swelling may lead to necrosis.
|-
| CE_COUGH_BLOOD
| No
| This effect results in the sufferer periodically coughing blood, which stains the tile they're on and requires cleanup. It doesn't appear to be lethal, but may cause minor bleeding damage.
|-
| CE_DIZZINESS
| No
| Inflicts the Dizziness condition, occasional fainting and a general slowdown in movement and work speed.
|-
| CE_DROWSINESS
| No
| Causes the Drowsiness condition.
|-
| CE_FEVER
| No
| Causes the Fever condition.
|-
| CE_NAUSEA
| No
| Causes the Nausea condition, and heavy vomiting. Can eventually lead to dehydration and death.
|-
| CE_UNCONSCIOUSNESS
| No
| Renders unconscious.
|-
| CE_VOMIT_BLOOD
| No
| This effect results in the sufferer periodically vomiting blood, which stains the tile they're on and requires cleanup. It doesn't appear to be lethal, but may cause minor bleeding damage.
|-
| CE_ERRATIC_BEHAVIOR{{version|0.42.01}}
| No
| Causes erratic behavior, meaning "People that like to brawl have a chance of starting a brawl-level fight with any nearby adult" [http://www.bay12forums.com/smf//index.php?topic=159164.msg7632503#msg7632503 -Toady]
|}
====Healing Effects====
Starting with DF version 0.47.01, there are healing counterparts to most of the tokens above that will heal various syndrome effects or physical damage.
{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Description
|-
| CE_STOP_BLEEDING
| Yes?
| Decreases the severity of the bleeding of any wounds or syndrome effects on the targeted bodypart. The SEV value probably controls by how much the bleeding is decreased.
|-
| CE_CLOSE_OPEN_WOUNDS
| Yes?
| Closes any wounds on the targeted bodypart with speed depending on the SEV value.
|-
| CE_HEAL_TISSUES
| Yes?
| Heals the tissues of the targeted bodypart with speed depending on the SEV value.
|-
| CE_HEAL_NERVES
| Yes?
| Heals the nerves of the targeted bodypart with speed depending on the SEV value.
|-
| CE_REDUCE_PAIN
| Yes?
| Decreases the severity of pain produced by wounds or syndrome effects on the targeted bodypart. The SEV value probably controls by how much the pain is decreased.
|-
| CE_REDUCE_SWELLING
| Yes?
| Decreases the severity of swelling on the targeted bodypart.
|-
| CE_CURE_INFECTION
| Yes?
| Probably decreases the severity of the infection from infected wounds over time.
|-
| CE_REDUCE_PARALYSIS
| Yes?
| Decreases the severity of any paralysis effects on the targeted bodypart.
|-
| CE_REGROW_PARTS
| Yes
| Causes missing bodyparts to regrow. SEV controls how quickly bodyparts are regrown. In adventure, parts will be regrown until you travel or wait/sleep {{bug|0011396}}.
|-
| CE_REDUCE_DIZZINESS
| No
| Decreases the severity of any dizziness the creature has.
|-
| CE_REDUCE_NAUSEA
| No
| Decreases the severity of any nausea the creature has.
|-
| CE_REDUCE_FEVER
| No
| Decreases the severity of any fever the creature has.
|}

===Special Effects===
Several special syndrome effects take different arguments than the above. These are used for generated interactions in unmodded games, but may be used as well for any substance or custom interaction.

{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Arguments
! Description
|-
| CE_ADD_TAG
| No
| tags
| Adds a tag to the affected creature. Many arguments can be used sequentially within one syndrome token. Valid tags are the same as that of the [[interaction token]] '''IT_REQUIRES''', ie.

BLOODSUCKER, CAN_LEARN, CAN_SPEAK, CRAZED, EXTRAVISION, LIKES_FIGHTING (or LIKESFIGHTING), MISCHIEVOUS (or MISCHIEVIOUS), NO_CONNECTIONS_FOR_MOVEMENT, NO_DIZZINESS, NO_DRINK, NO_EAT, NO_FEVERS, NO_PHYS_ATT_GAIN, NO_PHYS_ATT_RUST, NO_SLEEP, NO_THOUGHT_CENTER_FOR_MOVEMENT, NOBREATHE, NOEMOTION, NOEXERT, NOFEAR, NONAUSEA, NOPAIN, NOSTUN, NOT_LIVING, NOTHOUGHT, OPPOSED_TO_LIFE, PARALYZEIMMUNE, SUPERNATURAL, TRANCES, NO_AGING, STERILE, UTTERANCES.
|-
| CE_REMOVE_TAG
| No
| tags
| Removes a tag from a creature. Supported arguments are the same as CE_ADD_TAG.
|-
| CE_DISPLAY_TILE
| No
| TILE:[[Tilesets|tile number]]:[[Color#Modding color|colour]]
| The creature displays the specified tile and colour instead of its normal one.
|-
| CE_DISPLAY_NAME
| No
| NAME:singular:plural:adjective
| Attaches a specified name to the creature's normal name.
|-
| CE_FLASH_TILE
| No
| TILE:tile number:colour:FREQUENCY:ticks default tile:ticks syndrome tile
| The creature flashes between its normal tile and the one specified here.
|-
| CE_PHYS_ATT_CHANGE
| No
| [[Attribute]]:percentage:fixed boost(?)
| Alters the physical [[attribute]]s of a creature.
|-
| CE_MENT_ATT_CHANGE
| No
| [[Attribute]]:percentage:fixed boost(?)
| Alters the mental [[attribute]]s of a creature.
|-
| CE_BODY_APPEARANCE_MODIFIER
| No
| APPEARANCE_MODIFIER:HEIGHT/LENGTH/BROADNESS:percentage(?)
| Alters the size of the creature.
|-
| CE_BP_APPEARANCE_MODIFIER
| Yes
| body part:APPEARANCE_MODIFIER:attribute:number]
| Alters the characteristics (height, width etc.) of a body part.
|-
| CE_MATERIAL_FORCE_MULTIPLIER
| No
| MAT_MULT:[[material token|material]]:A:B
| Makes creature affected by materials more or less by a factor of A/B. If A is 3 and B is 2, the creature will be 1.5x weaker to the defined material (can be NONE:NONE for all); if 2:3, the creature will be 1.5 times stronger.
|-
| CE_SPEED_CHANGE
| No
| speed modifier:number
| Changes the speed of a creature.
Speed modifier contains one or both of:
* SPEED_PERC:percentage (this modifies a creature's in-game speed, so higher numbers are faster)
* SPEED_ADD:number (this modifies a creature's [SPEED:XX] token, so higher numbers are slower. Negative numbers are accepted though will only reduce a creature's speed to zero)
The minimum and maximum speeds able to be created by CE_SPEED_CHANGE are 99 and 10,000 respectively.

|-
| CE_CAN_DO_INTERACTION
| No
|
| Makes the creature able to perform an interaction. See [[Interaction token]]. To specify the interaction, use the argument:
* CDI:INTERACTION:interaction name
|-
| CE_SPECIAL_ATTACK_INTERACTION{{version|0.47.01}}
| Yes
| INTERACTION:<interaction name>:BP:<selection criteria>:<name of category,type, or token of designated part/parts>
| Makes the creature able to perform an interaction when using an attack with a designated body part/parts. See [[#Spreading diseases in 0.47.01|below]] for an example

|-
| CE_BODY_MAT_INTERACTION
| No
| MAT_TOKEN:<body material token>
| Causes one of the creature's body materials to trigger an interaction when the material is ingested, injected, etc (depending on the [CE:SYNDROME_TAG]s used; note that more than one may be specified). Generated vampire syndromes use '''RESERVED_BLOOD''' as the body material token in this syndrome tag, so as to specify the blood material of any creature with the syndrome. The following tokens should be inserted after this:
* '''CE:INTERACTION:interaction_id''' - replace 'interaction_id' with the name of the target interaction
* '''CE:SYNDROME_TAG:syndrome_trigger_type''' - replace 'syndrome_trigger_type' with any of SYN_INGESTED, SYN_INJECTED, SYN_CONTACT, SYN_INHALED
The linked interaction must have an [[Interaction_token#I_SOURCE|[I_SOURCE:INGESTION]]] token for this to work!

Note that this currently only works on materials obtained from historical figures and has only been tested with ingested materials linked to interactions with ADD_SYNDROME interaction effects.

|-
| CE_BODY_TRANSFORMATION
| No
| PROB:percentage:START:time:END:time
| Transforms into another creature. PROB and END arguments optional. The target creature may either be specified directly using CE:CREATURE or else set to be randomly selected as guided by creature and/or caste flag restrictions (of which multiple may be specified).
* CE:CREATURE:CREATURE_ID:CASTE_ID - Specify the creature and caste (for example: CE:CREATURE:DWARF:FEMALE). ANY can be used in place of a specific CASTE_ID to randomise the caste for every transformation. 
* CE:CREATURE_FLAG:FLAG{{version|0.47.01}} - Any creature with the specified [[:Interaction_token#Creature_and_Caste_Flags|creature flag]] is a valid transformation target. 
* CE:FORBIDDEN_CREATURE_FLAG{{version|0.47.01}} - Forbids all creatures with the specified [[:Interaction_token#Creature_and_Caste_Flags|creature flag]] from being randomly selected. 
* CE:CREATURE_CASTE_FLAG:FLAG{{version|0.47.01}} - Any creature with the specified [[:Interaction_token#Creature_and_Caste_Flags|caste flag]] is a valid transformation target. 
* CE:FORBIDDEN_CREATURE_CASTE_FLAG{{version|0.47.01}} - Forbids all creatures with the specified [[:Interaction_token#Creature_and_Caste_Flags|caste flag]] from being randomly selected. 
*CE:HAVE_FAST_EFFORTLESS_GAIT_SPEED{{version|0.47.01}} - Unknown. Possibly disallows all creatures with only slow gaits.{{verify}}

Note that any wounds the creature has suffered will instantly heal upon transforming, both into and out of the target form. [[Undead]] limbs of a creature with this token will grow into a full instance of that creature.
|-
| CE_SKILL_ROLL_ADJUST
| No
| PERC:percentage:PERC_ON:percentage
| Alters the skill level of a creature. The argument PERC specifies a percentage of the creature's current skill, and PERC_ON the probability of the effect being applied on a particular roll.
|-
| CE_SENSE_CREATURE_CLASS
| No
| START:time:CLASS:creature class:tile:color
| Allows creature to see other creatures with given class through walls. Vampires, for example, have START:0:CLASS:GENERAL_POISON:15:4:0:1.
|-
| CE_CHANGE_PERSONALITY{{version|0.42.01}}
| No
| FACET:[[DF2014:Personality_trait#Facets|trait]]:amount
| Changes a [[personality trait]] by amount. Multiple FACET:trait:amount sets may be used.
|-
| CE_FEEL_EMOTION{{version|0.42.01}}
| No
| EMOTION:[[emotion]]
| Makes the creature feel a specific [[emotion]]; severity based on standard SEV value. The [[thought]] the creature receives is: "[creature] feels [emotion] due to [syndrome name]". See [[Emotion]] for the list of valid emotions.
|}

'''All''' creature effect tokens take START, END and PROB numbers, and can be followed by [CE:PERIODIC] and/or [CE:COUNTER_TRIGGER] to restrict when they actually take effect.
* PERIODIC:period_type:min_value:max_value
* {{text anchor|COUNTER_TRIGGER}}:counter_name:min_value:max_value:REQUIRED

Currently, the only valid period type is MOON_PHASE.

===Counter Triggers===
Valid counter values are below:

{| {{prettytable}}
|- bgcolor="Bisque"
! Counter
! Description
|-
| ALCOHOLIC
| How long it's been (in [[time]] units) since the creature last had a drink of alcohol. Only present on creatures who need alcohol to get through the working day.
* 100800 (3 months) = and is starting to work slowly due to its scarcity
* 201600 (6 months) = and really wants a drink
* 302400 (9 months) = and has gone without a drink for far, far too long
* 403200 (1 year) = and can't even remember the last time he/she had some
|-
| CAVE_ADAPT
| How cave-adapted the creature is. Increases by 1 for every [[time]] unit spent underground, to a maximum of 800000.
* 403200 (1 year) = going outside causes irritation
* 604800 (1.5 years) = going outside causes nausea
|-
| PARTIED_OUT
| How long before the creature will decide to attend another party. Starts at 3+ months and counts down to zero.
|-
| MILK_COUNTER
| How long before the creature can be milked again. Starts at the creature's MILK frequency and counts down to zero.
|-
| EGG_SPENT
| How long before the creature can lay more eggs. Starts at 3 months and counts down to zero.
|-
| GROUNDED_ANIMAL_ANGER
| How angry (and likely to attack) an animal is from being over-crowded. Increases when over-crowded and otherwise counts down to zero.
|-
| TIME_SINCE_SUCKED_BLOOD
| How long it's been (in [[time]] units) since the creature last sucked somebody's blood.
|-
| DRINKING_BLOOD
| How much longer the creature will be drinking somebody's blood. Starts at 2.4 days and counts down to zero.
|}

{{mod}}

==Inorganic syndromes and you!==
It's perfectly possible - and quite simple - to add a nasty syndrome to a type of rock or metal - you simply add the syndrome tokens to the material definition in the same manner that you would add them to a creature material definition. The only catch is that since your hapless dwarves will only normally encounter the material in metal, gem or boulder form, a bit of creativity must be used to actually get them inside your citizens - that is, you need to make them 'explosively boil' as soon as they're mined or produced. This has the sad side effect of destroying the actual item - sorry, no highly radioactive uranium this release.

The easiest way to accomplish this is to assign the material a low boiling point, usually just under room temperature, and make sure its temperature is fixed to a point above it.
[MELTING_POINT:NONE]
[BOILING_POINT:10000]
[MAT_FIXED_TEMP:10001]
Now, as soon as this substance hits the open air - by being mined, smelted or reaction-produced at a custom workshop - it will EXPLOSIVELY BOIL, flooding a small area with delicious syndrome-rich gas. Creatures who inhale the gas will be immediately hit with the syndrome you thoughtfully attached to the material definition earlier!

There are a number of other tokens you can use to control the colour and naming conventions of your syndrome material, referred to as [[material definition token]]s.

==Spreading diseases==
It's fully possible to make a nasty disease capable of spreading itself from an infected dwarf to others, though it requires some skill in modding [[interaction token|interactions]] as well. Here is an example of a plague-inflicting interaction:

[INTERACTION:PLAGUE]
[I_TARGET:A:CREATURE]
[IT_LOCATION:CONTEXT_CREATURE]
[IT_FORBIDDEN:NOT_LIVING]
[IT_AFFECTED_CLASS:GENERAL_POISON]
[IT_MANUAL_INPUT:creatures]
[I_EFFECT:ADD_SYNDROME]
[IE_TARGET:A]
[IE_IMMEDIATE]
[SYNDROME]
[SYN_NAME:the plague]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[CE_FEVER:SEV:250:PROB:100:START:250:PEAK:1500:END:25000]
[CE_BLISTERS:SEV:325:PROB:100:BP:BY_CATEGORY:ALL:SKIN:START:250:PEAK:1500:END:25000]
[CE_NECROSIS:SEV:300:PROB:100:BP:BY_CATEGORY:ALL:ALL:VASCULAR_ONLY:START:22500:PEAK:23750:END:25000]
[CE_CAN_DO_INTERACTION:START:1500:END:25000]
[CDI:ADV_NAME:Spread the plague]
[CDI:INTERACTION:PLAGUE]
[CDI:TARGET:A:LINE_OF_SIGHT]
[CDI:TARGET_RANGE:A:10]
[CDI:WAIT_PERIOD:30]

As you can see, the syndrome here inflicts blisters, fever and, after roughly a month, necrosis of the whole body - that's when the infected creatures will start dying out. But before that happens, CE_CAN_DO_INTERACTION makes them capable of spreading the plague further.

You also need a disease vector that will bring the plague straight to your fort. (hint: use [[large rat|various]] [[rat man|species]] [[giant rat|of rats]] - they're perfect for that). The following code, added to a creature's raws, ensures the creature will infect anybody it encounters:

[CAN_DO_INTERACTION:PLAGUE]
[CDI:ADV_NAME:Spread the plague]
[CDI:TARGET:A:LINE_OF_SIGHT]
[CDI:TARGET_RANGE:A:10]
[CDI:WAIT_PERIOD:30]

As soon as the said creature is startled by your dwarves, the [[fun]] will begin.

==''In 0.47.01''==
As of version 0.47.01, it may be possible to use a creature's established methods of attack for use in disease-spreading.

Let's use the borrowed example of the plague above. This time, the plague will spread through biting, using the following syndrome code:

[INTERACTION:PLAGUE]
[I_TARGET:A:CREATURE]
[IT_LOCATION:CONTEXT_CREATURE]
[IT_FORBIDDEN:NOT_LIVING]
[IT_AFFECTED_CLASS:GENERAL_POISON]
[IT_MANUAL_INPUT:creatures]
[I_EFFECT:ADD_SYNDROME]
[IE_TARGET:A]
[IE_IMMEDIATE]
[SYNDROME]
[SYN_NAME:the plague]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[CE_FEVER:SEV:250:PROB:100:START:250:PEAK:1500:END:25000]
[CE_BLISTERS:SEV:325:PROB:100:BP:BY_CATEGORY:ALL:SKIN:START:250:PEAK:1500:END:25000]
[CE_NECROSIS:SEV:300:PROB:100:BP:BY_CATEGORY:ALL:ALL:VASCULAR_ONLY:START:22500:PEAK:23750:END:25000]
[CE_SPECIAL_ATTACK_INTERACTION:INTERACTION:PLAGUE:BP:BY_CATEGORY:TOOTH:START:0:ABRUPT]

The line [CE_SPECIAL_ATTACK_INTERACTION:INTERACTION:BITE_PLAGUE:BP:BY_CATEGORY:MOUTH:BP:BY_CATEGORY:TOOTH:START:0:ABRUPT] allows any infected creature with an attack using mouth or tooth category body parts to immediately spread the disease using said attack. The victim of the attack may then spread the disease if they are able to attack with the needed body part/parts.

{{Category|Modding}}
{{Category|Creature attributes}}
{{Category|Tokens}}
[[ru:DF2012:Syndrome]]

Syndrome

2020-06-30T05:25:14Z

Albedo: tighten image text

{{Quality|Masterwork|13:02, 6 April 2015 (UTC)}}
{{av}}
[[File:Snakebite.png|200px|thumb|right|A single bite from a [[helmet snake]] eventually lead to death for this unfortunate hippo.]]
A '''syndrome''' is a specific combination of [[symptoms]] that a poor, helpless creature might get from a disease, venom or other effect, through encountering certain other creatures, substances, or supernatural [[weather]]. Syndromes generally cause unpleasant and frequently fatal symptoms over a short to long period of time, but some will clear up over time or with the assistance of a [[doctor]]. A [[Health care|hospital]] is required to diagnose and potentially treat those syndromes that can be helped by treatment.

==List of syndromes==
Syndromes are generally named after the animal, substance or effect that delivers them.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Syndrome
! Venom
! Acquired
! Short-term Symptoms
! Long-term Symptoms
! Chronic Symptoms
|-
| Adder bite
| adder venom (injected)
| Being bitten by an [[adder]], [[giant adder]] or [[adder man]]
| Strong pain
| Swelling Blisters Nausea
| None
|-
| Bark scorpion sting
| bark scorpion venom (injected)
| Being stung by a [[bark scorpion]], [[giant bark scorpion]] or [[bark scorpion man]]
| Strong pain
| None
| None
|-
| Black mamba bite
| black mamba venom (injected)
| Being bitten by a [[black mamba]], [[giant black mamba]] or [[black mamba man]]
| Dizziness Drowsiness Strong pain Fever Unconsciousness Complete paralysis1
| None
| None
|-
| Blob blisters
| cave blob fluid (contact or ingested)
| Touching a [[cave blob]]
| Mild pain Mild blisters
| None
| None
|-
| Brown recluse spider bite
| brown recluse spider venom (injected)
| Being bitten by a [[brown recluse spider]], [[giant brown recluse spider]] or [[brown recluse spider man]]
| Nausea Fever Pain 
| Severe localized necrosis
| None
|-
| Bumblebee sting
| bumblebee venom (injected)
| Being stung by a [[bumblebee]] worker
| Pain Strong swelling
| None
| None
|-
| Bushmaster bite
| bushmaster venom (injected)
| Being bitten by a [[bushmaster]], [[giant bushmaster]] or [[bushmaster man]]
| Strong pain Mild bleeding Dizziness Nausea Unconsciousness Complete paralysis1
| None
| None
|-
| Cave floater sickness
| cave floater gas (inhaled or ingested)
| Expelled from [[cave floater]]
| Mild nausea
| Fever Strong drowsiness (delayed) Strong dizziness (delayed)
| None
|-
| Cave spider bite
| cave spider venom (injected)
| Being bitten by a [[cave spider]]
| None
| None
| Very mild dizziness
|-
| Copperhead snake bite
| copperhead snake venom (injected)
| Being bitten by a [[copperhead snake]], [[giant copperhead snake]] or [[copperhead snake man]]
| Pain Swelling Nausea
| None
| None
|-
| Giant cave spider bite
| giant cave spider venom (injected)
| Being bitten by a [[giant cave spider]]
| Size-dependant paralysis.
| Death by asphyxiation, in small targets. Large targets are generally unhindered...unless you count the high probability of being eaten by the giant cave spider as a hindrance.
| None, not that it really matters.
|-
| Gila monster bite
| gila monster venom (injected)
| Being bitten by a [[gila monster]], [[giant gila monster]] or [[gila monster man]]
| Pain Mild swelling
| None
| None
|-
| Gnomeblight
| [[gnomeblight]] (contact, inhaled, injected, or ingested)
| Purposely exposing oneself to the extract. Only affects [[mountain gnome]]s and [[dark gnome]]s.
| None
| Severe systemic necrosis2
| None
|-
| Giant desert scorpion sting
| giant desert scorpion venom (injected)
| Being stung by a [[giant desert scorpion]]
| Necrosis of the brain and nervous system
| '''Certain death'''
| None, not that it really matters.
|-
| Helmet snake bite
| helmet snake venom (injected)
| Being bitten by a [[helmet snake]]
| Minor bleeding
| Fever Nausea Dizziness Localized swelling Localized oozing Localized bruising Strong pain Intense localized necrosis Possible loss of limb
| None
|-
| Honey bee sting
| honey bee venom (injected)
| Being stung by a [[honey bee]] worker
| Pain Strong swelling
| None
| None
|-
| Inebriation{{version|0.42.01}}
| [[Alcohol]] (consumed/injected)
| Consuming alcoholic drinks
| Nausea Dizziness Unconsciousness Personality changes Euphoria Erratic behavior Trouble breathing
| None
| None
|-
| Iron man cough
| iron man gas (inhaled)
| Expelled by [[iron man]]
| Coughing blood
| None
| None
|-
| King cobra bite
| king cobra venom (injected)
| Being bitten by a [[king cobra]]
| Complete paralysis1 Pain, dizziness, drowsiness
| None
| None
|-
| Phantom spider bite
| phantom spider venom (injected)
| Being bitten by a [[phantom spider]]
| None
| Numbness and mild dizziness
| None
|-
| Platypus sting
| platypus venom (injected)
| Being kicked by a [[platypus]], [[giant platypus]] or [[platypus man]]
| Pain and swelling
| Extreme pain, swelling possibly to the point of necrosis
| None
|-
| Rattlesnake bite
| rattlesnake venom (injected)
| Being bitten by a [[rattlesnake]], [[giant rattlesnake]] or [[rattlesnake man]]
| Pain, nausea, blisters, swelling, bruising
| Severe localized necrosis
| None
|-
| Serpent man bite
| serpent man venom (injected)
| Being bitten by a [[serpent man]]
| Complete paralysis1
| None
| None
|-
| Mummy's curse
| [[DF2014:Mummy|Disturbance interaction]].
| Being cursed by a [[mummy]], when caught raiding their tombs
| None
| None
| 20% chance of any skill roll failing, regardless of skill.
|-
| Vampirism
| [[Deity|Divine]] Curse.
| Drinking the blood of a [[vampire]]. Toppling statues in shrines in Adventure Mode or temples in Fortress Mode (random chance).
| None
| None
| Victim becomes a [[vampire]].
|-
| Werebeast Curse
| [[Deity|Divine]] Curse.
| Being bitten by a [[werebeast]] or toppling statues in shrines in Adventure Mode (random chance).
| None
| None
| Victim becomes a [[werebeast]].
|-
| Necromancy
| [[Deity|Divine]] Curse.
| Reading a book/slab that contains the secrets of life and death.
| None
| None
| Reader becomes a [[Necromancer]].
|-
| evil rain sickness3
|rowspan=7| Random
| Being caught outside in [[Weather#Evil weather|freakish weather]] in an evil [[biome]]
|rowspan=7| Random
|rowspan=7| Random
|rowspan=7| Random
|-
| evil cloud sickness4
| Being caught in a [Weather#Evil weather|creeping cloud]] in an evil [[biome]]
|-
| beast sickness5
| Encounters with [[forgotten beast]]s
|-
| titan sickness5
| Encounters with [[titan]]s
|-
| night sickness5
| Encounters with [[werebeast]]s or [[experiment]]s
|-
| demon sickness5
| Encounters with [[demon]]s
|-
| divine sickness5
| Encounters with [[angel]]s
|}
: 1. For small creatures such as humans and dwarves, paralysis tends to result in suffocation.
: 2. Necrosis of the brain will eventually result in death once the brain rots away completely.
: 3. Evil rain typically only causes minor symptoms such as blisters, bruising, coughing blood, dizziness, fever, nausea, oozing, and pain.
: 4. Evil clouds either cause major symptoms (as with beast/titan/demon sicknesses) or permanently transform creatures into [[Undead|zombie-like]] forms.
: 5. [[Titan]]s, [[forgotten beast]]s, [[werebeast]]s, [[experiment]]s, [[demon]]s and [[angel]]s have a chance to have a randomized syndrome. These range from mildly hazardous (mild [[Symptoms#Blisters|blisters]] from inhaling boiling blood) to instantly fatal (severe necrosis from a contact poison attached to a breath weapon/creature made of blood).

==The anatomy of a syndrome==
Mechanically, syndromes are bundles of tokens attached to a material (or to an interaction effect; see below) - they're confined to creature materials in vanilla DF, but it's a simple matter to add them to inorganic materials. When the material is injected, touched, inhaled, or ingested (depending on the syndrome), the creature suffers the predations of a nasty disease or poison. Here's an example syndrome, taken from the Giant Cave Spider raws.

If you are having troubles getting the syndromes to work (i.e., in combat reports, getting "'''supersnake''' n/a splatters~etc"), then simply throw the venom template into the actual creature's raw, which is what the LOCAL_CREATURE_MAT actually calls on; the venom being in the same file.

[USE_MATERIAL_TEMPLATE:VENOM:CREATURE_EXTRACT_TEMPLATE]
[STATE_NAME:ALL_SOLID:frozen giant cave spider venom]
[STATE_ADJ:ALL_SOLID:frozen giant cave spider venom]
[STATE_NAME:LIQUID:giant cave spider venom]
[STATE_ADJ:LIQUID:giant cave spider venom]
[STATE_NAME:GAS:boiling giant cave spider venom]
[STATE_ADJ:GAS:boiling giant cave spider venom]
[PREFIX:NONE]
[ENTERS_BLOOD]
[SYNDROME]
[SYN_NAME:giant cave spider bite]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[SYN_IMMUNE_CREATURE:SPIDER_CAVE:ALL]
[SYN_INJECTED]
[CE_PARALYSIS:SEV:100:PROB:100:RESISTABLE:SIZE_DILUTES:START:5:PEAK:10:END:20]

The first line, USE_MATERIAL_TEMPLATE, is creating a new material, called POISON, using the CREATURE_EXTRACT_TEMPLATE as the basis. After this, the STATE_NAME and STATE_ADJ tokens are used to define the names and adjectives assigned to different states of the material - GAS, LIQUID and ALL_SOLID, in this case, though ALL is also a valid token. At this stage, you can use any material tags like MAT_FIXED_TEMP or similar to set further material properties, though this usually isn't necessary.

ENTERS_BLOOD
This tag determines whether a poison enters the blood or not. If it is not included, the poison will splatter (if liquid) or flow (if gas) over the affected body part instead when injected. If you're using a contact poison, leave this out. Necessary for injected poisons.
SYNDROME
This tag ends the material details and begins the definition of the actual syndrome.
SYN_NAME
This one is self-explanatory - the name of the syndrome as it will appear in-game.
SYN_AFFECTED_CLASS
This token defines what CREATURE_CLASS will be affected by the syndrome. Most creatures are classed under GENERAL_POISON. Multiple tokens can be used in a single syndrome.
SYN_IMMUNE_CLASS
As above, but makes class immune.
SYN_IMMUNE_CREATURE
This token defines which creatures CANNOT be affected by the syndrome - useful for addressing specific instances within a population, such as a specific caste or an individual creature that falls under GENERAL_POISON. Syntax is [SYN_IMMUNE_CREATURE:creature:caste]. ALL can be used for the caste.
SYN_AFFECTED_CREATURE
As above, but makes creature or caste susceptible.
SYN_CLASS
This tag sets a class for the syndrome that can be used in [[Interaction token|interactions.]]
SYN_IDENTIFIER{{version|0.42.01}}.
Similar to SYN_CLASS, this sets an identifier that can be shared between multiple syndromes, for use with the SYNDROME_DILUTION_FACTOR creature token. In vanilla DF, this is used to allow dwarves to drink more alcohol before becoming inebriated.
SYN_NO_HOSPITAL{{version|0.42.01}}.
Probably prevents affected dwarves from being carried to the hospital.{{verify}}
SYN_CONCENTRATION_ADDED:x:x{{version|0.42.01}}.
Repeated exposure to the syndrome will result in the effects becoming more intense. In vanilla [SYN_CONCENTRATION_ADDED:100:1000] is used with alcohol.

SYN_INJECTED, SYN_CONTACT, SYN_INHALED, SYN_INGESTED
This token determines the method of infection - injected syndromes must be injected via a creature attack, while contact syndromes result from any contamination of a creature by material splatter (such as blood), inhaled syndromes must be inhaled in gaseous form (such as from boiling or a creature breath attack), and ingestion syndromes must be eaten or drunk. Any combination of these tags can be used. A fun variation on the usual creature injection routine is to create a material with a SYN_CONTACT syndrome and have a creature use it for blood - this tends to end poorly for any predator that chooses to attack them.

[SPECIALATTACK_INJECT_EXTRACT:LOCAL_CREATURE_MAT:VENOM:LIQUID:100:100]
This is one method for getting a poison into a creature. If [ENTERS_BLOOD] is applied, it will be injected into the bloodstream. Otherwise, it will just splatter over the area. Put this on a creature attack. Substance type (gas, liquid, solid) does not appear to have an effect. The numbers on the end are minimum and maximum.

CE_X, or creature effect tokens, are the real meat and bones of your syndrome. They're detailed below.

==Creature effect tokens==
Each and every syndrome has a number of creature effect tokens, represented by CE_X - these lovely little beauties determine exactly how the poor creature suffering from the syndrome is affected. An example CE token is as follows:

[CE_NECROSIS:SEV:100:PROB:100:LOCALIZED:VASCULAR_ONLY:RESISTABLE:START:50:PEAK:1000:END:2000]

In this example, we have an effect that will always cause severe necrosis in whichever bodypart it touches, so long as that bodypart is vascular and that the creature is not able to resist it in some manner. The effect begins shortly after the syndrome is contracted, peaks 1000 [[time|time units]] afterwards, and finally ceases another 1000 time units later.

As a general rule of thumb, so long as CE_X starts the string and START/(PEAK/END) ends it, the order of the intervening tokens isn't important. PEAK and END aren't required.

*CE_X
The effect type. This can be a number of different tokens, as detailed in the table below this list.
*SEV:X
The severity of the effect. Higher values appear to be worse, with SEV:1000 CE_NECROSIS causing a part to near-instantly become rotten.
*PROB:X
The probability of the effect actually manifesting in the victim, as a percentage. 100 means always, 1 means a 1 in 100 chance.
*LOCALIZED (Overwrites BP tokens)
This tag causes an effect to ignore all BP tokens and then forces the game to attempt to apply the effect to the limb that came into contact with the contagion - i.e. the part that was bitten by the creature injecting the syndrome material, or the one that was splattered by a contact contagion. If an effect can not be applied to the contacted limb (such as IMPAIR_FUNCTION on a non-organ) then this token makes the syndrome have no effect. This token also makes inhaled syndromes have no effect.
*BP:BODY_PART:TISSUE (Overwritten by LOCALIZED)
Specifies which body parts and tissues are to be affected by the syndrome. BODY_PART can be BY_CATEGORY:x to target body parts with a matching [CATEGORY:x] [[body token]] (or ALL to affect everything), BY_TYPE:x to target body parts having a particular type (UPPERBODY, LOWERBODY, HEAD, GRASP, or STANCE), or BY_TOKEN:x to target individual body parts by their ID (as specified in the [BP] token). For example, if you wanted to target the lungs of a creature, you would use BP:BY_CATEGORY:LUNG:ALL. The syndrome would act on all bodyparts within the creature with the CATEGORY tag LUNG and affect all tissue layers. For another example, say you wanted to cause the skin to rot off a creature - you could use BP:BY_CATEGORY:ALL:SKIN, targeting the SKIN tissue on all bodyparts. Multiple targets can be given in one syndrome by placing the BP tokens end to end. This is one of the most powerful and useful aspects of the syndrome system, as it allows you to selectively target bodyparts relevant to the contagion, like lungs for coal dust inhalation, or the eyes for exposure to an acid gas. Not everything takes a target!
*VASCULAR_ONLY (Optional)
This syndrome only affects tissue layers with the VASCULAR token.
*MUSCULAR_ONLY (Optional)
This syndrome only affects tissue layers with the MUSCULAR token. Are you seeing a trend here?
*SIZE_DILUTES (Optional)
This token presumably causes the effects of the syndrome to scale with the size of the creature compared to the size of the dose of contagion they received, but has yet to be extensively tested.
*SIZE_DELAYS (Optional)
As above, this token has yet to be tested but presumably delays the onset of a syndrome according to the size of the victim.
*DWF_STRETCH:X{{version|0.42.01}} (Optional)
Multiplies the duration of the syndrome by X in Fortress mode. If X is 72, syndrome will last the same amount of ticks in fortress and adventure mode.
*ABRUPT{{version|0.42.01}} (Optional)
Makes the symptom begin immediately rather than ramping up. {{verify}}
*CAN_BE_HIDDEN (Optional)
Can be hidden by a unit assuming a secret identity, such as a [[vampire]]. {{verify}}
*RESISTABLE (Optional)
Determines if the effect can be hindered by the target creature's [[Attribute#Disease_Resistance|disease resistance attribute]]. Without this token, disease resistance is ignored.

The details of this table are still being thrashed out by modders, so if you have anything to add, please don't hesitate to hit the edit button!

Non-targeted syndromes will ignore any BP tokens and LOCALIZED tokens.
{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Description
|-
| CE_BLEEDING
| Yes
| Causes the targeted bodypart to start bleeding, with heavy enough bleeding resulting in the death of the sufferer. Some conditions seem to cause bleeding to be fatal no matter how weak.
|-
| CE_BLISTERS
| Yes
| Covers the targeted bodypart with blisters.
|-
| CE_BRUISING
| Yes
| Causes the targeted bodypart to undergo bruising.
|-
| CE_IMPAIR_FUNCTION
| Yes
| An organ afflicted with this CE is rendered inoperable - for example, if both lungs are impaired the creature can't breathe and will suffocate. This token only affects organs, not limbs. Note that this effect is currently bugged, and will not "turn off" until the creature receives a wound to cause its body parts to update.
|-
| CE_NECROSIS
| Yes
| Causes the targeted bodypart to rot, with associated tissue damage, miasma emission and bleeding. The victim slowly bleeds to death if the wound is not treated. Badly necrotic limbs will require amputation.
|-
| CE_NUMBNESS
| Yes
| Causes numbness in the affected body part, blocking pain. Extreme numbness may lead to sensory nerve damage.
|-
| CE_OOZING
| Yes
| Causes pus to ooze from the afflicted bodypart.
|-
| CE_PAIN
| Yes
| Afflicts the targeted bodypart with intense pain.
|-
| CE_PARALYSIS
| Yes
| Causes paralysis. Paralysis is complete paralysis and will cause suffocation in smaller creatures. Paralysis on a limb may lead to motor nerve damage.
|-
| CE_SWELLING
| Yes
| Causes the targeted bodypart to swell up. Extreme swelling may lead to necrosis.
|-
| CE_COUGH_BLOOD
| No
| This effect results in the sufferer periodically coughing blood, which stains the tile they're on and requires cleanup. It doesn't appear to be lethal, but may cause minor bleeding damage.
|-
| CE_DIZZINESS
| No
| Inflicts the Dizziness condition, occasional fainting and a general slowdown in movement and work speed.
|-
| CE_DROWSINESS
| No
| Causes the Drowsiness condition.
|-
| CE_FEVER
| No
| Causes the Fever condition.
|-
| CE_NAUSEA
| No
| Causes the Nausea condition, and heavy vomiting. Can eventually lead to dehydration and death.
|-
| CE_UNCONSCIOUSNESS
| No
| Renders unconscious.
|-
| CE_VOMIT_BLOOD
| No
| This effect results in the sufferer periodically vomiting blood, which stains the tile they're on and requires cleanup. It doesn't appear to be lethal, but may cause minor bleeding damage.
|-
| CE_ERRATIC_BEHAVIOR{{version|0.42.01}}
| No
| Causes erratic behavior, meaning "People that like to brawl have a chance of starting a brawl-level fight with any nearby adult" [http://www.bay12forums.com/smf//index.php?topic=159164.msg7632503#msg7632503 -Toady]
|}
====Healing Effects====
Starting with DF version 0.47.01, there are healing counterparts to most of the tokens above that will heal various syndrome effects or physical damage.
{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Description
|-
| CE_STOP_BLEEDING
| Yes?
| Decreases the severity of the bleeding of any wounds or syndrome effects on the targeted bodypart. The SEV value probably controls by how much the bleeding is decreased.
|-
| CE_CLOSE_OPEN_WOUNDS
| Yes?
| Closes any wounds on the targeted bodypart with speed depending on the SEV value.
|-
| CE_HEAL_TISSUES
| Yes?
| Heals the tissues of the targeted bodypart with speed depending on the SEV value.
|-
| CE_HEAL_NERVES
| Yes?
| Heals the nerves of the targeted bodypart with speed depending on the SEV value.
|-
| CE_REDUCE_PAIN
| Yes?
| Decreases the severity of pain produced by wounds or syndrome effects on the targeted bodypart. The SEV value probably controls by how much the pain is decreased.
|-
| CE_REDUCE_SWELLING
| Yes?
| Decreases the severity of swelling on the targeted bodypart.
|-
| CE_CURE_INFECTION
| Yes?
| Probably decreases the severity of the infection from infected wounds over time.
|-
| CE_REDUCE_PARALYSIS
| Yes?
| Decreases the severity of any paralysis effects on the targeted bodypart.
|-
| CE_REGROW_PARTS
| Yes
| Causes missing bodyparts to regrow. SEV controls how quickly bodyparts are regrown. In adventure, parts will be regrown until you travel or wait/sleep {{bug|0011396}}.
|-
| CE_REDUCE_DIZZINESS
| No
| Decreases the severity of any dizziness the creature has.
|-
| CE_REDUCE_NAUSEA
| No
| Decreases the severity of any nausea the creature has.
|-
| CE_REDUCE_FEVER
| No
| Decreases the severity of any fever the creature has.
|}

===Special Effects===
Several special syndrome effects take different arguments than the above. These are used for generated interactions in unmodded games, but may be used as well for any substance or custom interaction.

{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Arguments
! Description
|-
| CE_ADD_TAG
| No
| tags
| Adds a tag to the affected creature. Many arguments can be used sequentially within one syndrome token. Valid tags are the same as that of the [[interaction token]] '''IT_REQUIRES''', ie.

BLOODSUCKER, CAN_LEARN, CAN_SPEAK, CRAZED, EXTRAVISION, LIKES_FIGHTING (or LIKESFIGHTING), MISCHIEVOUS (or MISCHIEVIOUS), NO_CONNECTIONS_FOR_MOVEMENT, NO_DIZZINESS, NO_DRINK, NO_EAT, NO_FEVERS, NO_PHYS_ATT_GAIN, NO_PHYS_ATT_RUST, NO_SLEEP, NO_THOUGHT_CENTER_FOR_MOVEMENT, NOBREATHE, NOEMOTION, NOEXERT, NOFEAR, NONAUSEA, NOPAIN, NOSTUN, NOT_LIVING, NOTHOUGHT, OPPOSED_TO_LIFE, PARALYZEIMMUNE, SUPERNATURAL, TRANCES, NO_AGING, STERILE, UTTERANCES.
|-
| CE_REMOVE_TAG
| No
| tags
| Removes a tag from a creature. Supported arguments are the same as CE_ADD_TAG.
|-
| CE_DISPLAY_TILE
| No
| TILE:[[Tilesets|tile number]]:[[Color#Modding color|colour]]
| The creature displays the specified tile and colour instead of its normal one.
|-
| CE_DISPLAY_NAME
| No
| NAME:singular:plural:adjective
| Attaches a specified name to the creature's normal name.
|-
| CE_FLASH_TILE
| No
| TILE:tile number:colour:FREQUENCY:ticks default tile:ticks syndrome tile
| The creature flashes between its normal tile and the one specified here.
|-
| CE_PHYS_ATT_CHANGE
| No
| [[Attribute]]:percentage:fixed boost(?)
| Alters the physical [[attribute]]s of a creature.
|-
| CE_MENT_ATT_CHANGE
| No
| [[Attribute]]:percentage:fixed boost(?)
| Alters the mental [[attribute]]s of a creature.
|-
| CE_BODY_APPEARANCE_MODIFIER
| No
| APPEARANCE_MODIFIER:HEIGHT/LENGTH/BROADNESS:percentage(?)
| Alters the size of the creature.
|-
| CE_BP_APPEARANCE_MODIFIER
| Yes
| body part:APPEARANCE_MODIFIER:attribute:number]
| Alters the characteristics (height, width etc.) of a body part.
|-
| CE_MATERIAL_FORCE_MULTIPLIER
| No
| MAT_MULT:[[material token|material]]:A:B
| Makes creature affected by materials more or less by a factor of A/B. If A is 3 and B is 2, the creature will be 1.5x weaker to the defined material (can be NONE:NONE for all); if 2:3, the creature will be 1.5 times stronger.
|-
| CE_SPEED_CHANGE
| No
| speed modifier:number
| Changes the speed of a creature.
Speed modifier contains one or both of:
* SPEED_PERC:percentage (this modifies a creature's in-game speed, so higher numbers are faster)
* SPEED_ADD:number (this modifies a creature's [SPEED:XX] token, so higher numbers are slower. Negative numbers are accepted though will only reduce a creature's speed to zero)
The minimum and maximum speeds able to be created by CE_SPEED_CHANGE are 99 and 10,000 respectively.

|-
| CE_CAN_DO_INTERACTION
| No
|
| Makes the creature able to perform an interaction. See [[Interaction token]]. To specify the interaction, use the argument:
* CDI:INTERACTION:interaction name
|-
| CE_SPECIAL_ATTACK_INTERACTION{{version|0.47.01}}
| Yes
| INTERACTION:<interaction name>:BP:<selection criteria>:<name of category,type, or token of designated part/parts>
| Makes the creature able to perform an interaction when using an attack with a designated body part/parts. See [[#Spreading diseases in 0.47.01|below]] for an example

|-
| CE_BODY_MAT_INTERACTION
| No
| MAT_TOKEN:<body material token>
| Causes one of the creature's body materials to trigger an interaction when the material is ingested, injected, etc (depending on the [CE:SYNDROME_TAG]s used; note that more than one may be specified). Generated vampire syndromes use '''RESERVED_BLOOD''' as the body material token in this syndrome tag, so as to specify the blood material of any creature with the syndrome. The following tokens should be inserted after this:
* '''CE:INTERACTION:interaction_id''' - replace 'interaction_id' with the name of the target interaction
* '''CE:SYNDROME_TAG:syndrome_trigger_type''' - replace 'syndrome_trigger_type' with any of SYN_INGESTED, SYN_INJECTED, SYN_CONTACT, SYN_INHALED
The linked interaction must have an [[Interaction_token#I_SOURCE|[I_SOURCE:INGESTION]]] token for this to work!

Note that this currently only works on materials obtained from historical figures and has only been tested with ingested materials linked to interactions with ADD_SYNDROME interaction effects.

|-
| CE_BODY_TRANSFORMATION
| No
| PROB:percentage:START:time:END:time
| Transforms into another creature. PROB and END arguments optional. The target creature may either be specified directly using CE:CREATURE or else set to be randomly selected as guided by creature and/or caste flag restrictions (of which multiple may be specified).
* CE:CREATURE:CREATURE_ID:CASTE_ID - Specify the creature and caste (for example: CE:CREATURE:DWARF:FEMALE). ANY can be used in place of a specific CASTE_ID to randomise the caste for every transformation. 
* CE:CREATURE_FLAG:FLAG{{version|0.47.01}} - Any creature with the specified [[:Interaction_token#Creature_and_Caste_Flags|creature flag]] is a valid transformation target. 
* CE:FORBIDDEN_CREATURE_FLAG{{version|0.47.01}} - Forbids all creatures with the specified [[:Interaction_token#Creature_and_Caste_Flags|creature flag]] from being randomly selected. 
* CE:CREATURE_CASTE_FLAG:FLAG{{version|0.47.01}} - Any creature with the specified [[:Interaction_token#Creature_and_Caste_Flags|caste flag]] is a valid transformation target. 
* CE:FORBIDDEN_CREATURE_CASTE_FLAG{{version|0.47.01}} - Forbids all creatures with the specified [[:Interaction_token#Creature_and_Caste_Flags|caste flag]] from being randomly selected. 
*CE:HAVE_FAST_EFFORTLESS_GAIT_SPEED{{version|0.47.01}} - Unknown. Possibly disallows all creatures with only slow gaits.{{verify}}

Note that any wounds the creature has suffered will instantly heal upon transforming, both into and out of the target form. [[Undead]] limbs of a creature with this token will grow into a full instance of that creature.
|-
| CE_SKILL_ROLL_ADJUST
| No
| PERC:percentage:PERC_ON:percentage
| Alters the skill level of a creature. The argument PERC specifies a percentage of the creature's current skill, and PERC_ON the probability of the effect being applied on a particular roll.
|-
| CE_SENSE_CREATURE_CLASS
| No
| START:time:CLASS:creature class:tile:color
| Allows creature to see other creatures with given class through walls. Vampires, for example, have START:0:CLASS:GENERAL_POISON:15:4:0:1.
|-
| CE_CHANGE_PERSONALITY{{version|0.42.01}}
| No
| FACET:[[DF2014:Personality_trait#Facets|trait]]:amount
| Changes a [[personality trait]] by amount. Multiple FACET:trait:amount sets may be used.
|-
| CE_FEEL_EMOTION{{version|0.42.01}}
| No
| EMOTION:[[emotion]]
| Makes the creature feel a specific [[emotion]]; severity based on standard SEV value. The [[thought]] the creature receives is: "[creature] feels [emotion] due to [syndrome name]". See [[Emotion]] for the list of valid emotions.
|}

'''All''' creature effect tokens take START, END and PROB numbers, and can be followed by [CE:PERIODIC] and/or [CE:COUNTER_TRIGGER] to restrict when they actually take effect.
* PERIODIC:period_type:min_value:max_value
* {{text anchor|COUNTER_TRIGGER}}:counter_name:min_value:max_value:REQUIRED

Currently, the only valid period type is MOON_PHASE.

===Counter Triggers===
Valid counter values are below:

{| {{prettytable}}
|- bgcolor="Bisque"
! Counter
! Description
|-
| ALCOHOLIC
| How long it's been (in [[time]] units) since the creature last had a drink of alcohol. Only present on creatures who need alcohol to get through the working day.
* 100800 (3 months) = and is starting to work slowly due to its scarcity
* 201600 (6 months) = and really wants a drink
* 302400 (9 months) = and has gone without a drink for far, far too long
* 403200 (1 year) = and can't even remember the last time he/she had some
|-
| CAVE_ADAPT
| How cave-adapted the creature is. Increases by 1 for every [[time]] unit spent underground, to a maximum of 800000.
* 403200 (1 year) = going outside causes irritation
* 604800 (1.5 years) = going outside causes nausea
|-
| PARTIED_OUT
| How long before the creature will decide to attend another party. Starts at 3+ months and counts down to zero.
|-
| MILK_COUNTER
| How long before the creature can be milked again. Starts at the creature's MILK frequency and counts down to zero.
|-
| EGG_SPENT
| How long before the creature can lay more eggs. Starts at 3 months and counts down to zero.
|-
| GROUNDED_ANIMAL_ANGER
| How angry (and likely to attack) an animal is from being over-crowded. Increases when over-crowded and otherwise counts down to zero.
|-
| TIME_SINCE_SUCKED_BLOOD
| How long it's been (in [[time]] units) since the creature last sucked somebody's blood.
|-
| DRINKING_BLOOD
| How much longer the creature will be drinking somebody's blood. Starts at 2.4 days and counts down to zero.
|}

{{mod}}

==Inorganic syndromes and you!==
It's perfectly possible - and quite simple - to add a nasty syndrome to a type of rock or metal - you simply add the syndrome tokens to the material definition in the same manner that you would add them to a creature material definition. The only catch is that since your hapless dwarves will only normally encounter the material in metal, gem or boulder form, a bit of creativity must be used to actually get them inside your citizens - that is, you need to make them 'explosively boil' as soon as they're mined or produced. This has the sad side effect of destroying the actual item - sorry, no highly radioactive uranium this release.

The easiest way to accomplish this is to assign the material a low boiling point, usually just under room temperature, and make sure its temperature is fixed to a point above it.
[MELTING_POINT:NONE]
[BOILING_POINT:10000]
[MAT_FIXED_TEMP:10001]
Now, as soon as this substance hits the open air - by being mined, smelted or reaction-produced at a custom workshop - it will EXPLOSIVELY BOIL, flooding a small area with delicious syndrome-rich gas. Creatures who inhale the gas will be immediately hit with the syndrome you thoughtfully attached to the material definition earlier!

There are a number of other tokens you can use to control the colour and naming conventions of your syndrome material, referred to as [[material definition token]]s.

==Spreading diseases==
It's fully possible to make a nasty disease capable of spreading itself from an infected dwarf to others, though it requires some skill in modding [[interaction token|interactions]] as well. Here is an example of a plague-inflicting interaction:

[INTERACTION:PLAGUE]
[I_TARGET:A:CREATURE]
[IT_LOCATION:CONTEXT_CREATURE]
[IT_FORBIDDEN:NOT_LIVING]
[IT_AFFECTED_CLASS:GENERAL_POISON]
[IT_MANUAL_INPUT:creatures]
[I_EFFECT:ADD_SYNDROME]
[IE_TARGET:A]
[IE_IMMEDIATE]
[SYNDROME]
[SYN_NAME:the plague]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[CE_FEVER:SEV:250:PROB:100:START:250:PEAK:1500:END:25000]
[CE_BLISTERS:SEV:325:PROB:100:BP:BY_CATEGORY:ALL:SKIN:START:250:PEAK:1500:END:25000]
[CE_NECROSIS:SEV:300:PROB:100:BP:BY_CATEGORY:ALL:ALL:VASCULAR_ONLY:START:22500:PEAK:23750:END:25000]
[CE_CAN_DO_INTERACTION:START:1500:END:25000]
[CDI:ADV_NAME:Spread the plague]
[CDI:INTERACTION:PLAGUE]
[CDI:TARGET:A:LINE_OF_SIGHT]
[CDI:TARGET_RANGE:A:10]
[CDI:WAIT_PERIOD:30]

As you can see, the syndrome here inflicts blisters, fever and, after roughly a month, necrosis of the whole body - that's when the infected creatures will start dying out. But before that happens, CE_CAN_DO_INTERACTION makes them capable of spreading the plague further.

You also need a disease vector that will bring the plague straight to your fort. (hint: use [[large rat|various]] [[rat man|species]] [[giant rat|of rats]] - they're perfect for that). The following code, added to a creature's raws, ensures the creature will infect anybody it encounters:

[CAN_DO_INTERACTION:PLAGUE]
[CDI:ADV_NAME:Spread the plague]
[CDI:TARGET:A:LINE_OF_SIGHT]
[CDI:TARGET_RANGE:A:10]
[CDI:WAIT_PERIOD:30]

As soon as the said creature is startled by your dwarves, the [[fun]] will begin.

==''In 0.47.01''==
As of version 0.47.01, it may be possible to use a creature's established methods of attack for use in disease-spreading.

Let's use the borrowed example of the plague above. This time, the plague will spread through biting, using the following syndrome code:

[INTERACTION:PLAGUE]
[I_TARGET:A:CREATURE]
[IT_LOCATION:CONTEXT_CREATURE]
[IT_FORBIDDEN:NOT_LIVING]
[IT_AFFECTED_CLASS:GENERAL_POISON]
[IT_MANUAL_INPUT:creatures]
[I_EFFECT:ADD_SYNDROME]
[IE_TARGET:A]
[IE_IMMEDIATE]
[SYNDROME]
[SYN_NAME:the plague]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[CE_FEVER:SEV:250:PROB:100:START:250:PEAK:1500:END:25000]
[CE_BLISTERS:SEV:325:PROB:100:BP:BY_CATEGORY:ALL:SKIN:START:250:PEAK:1500:END:25000]
[CE_NECROSIS:SEV:300:PROB:100:BP:BY_CATEGORY:ALL:ALL:VASCULAR_ONLY:START:22500:PEAK:23750:END:25000]
[CE_SPECIAL_ATTACK_INTERACTION:INTERACTION:PLAGUE:BP:BY_CATEGORY:TOOTH:START:0:ABRUPT]

The line [CE_SPECIAL_ATTACK_INTERACTION:INTERACTION:BITE_PLAGUE:BP:BY_CATEGORY:MOUTH:BP:BY_CATEGORY:TOOTH:START:0:ABRUPT] allows any infected creature with an attack using mouth or tooth category body parts to immediately spread the disease using said attack. The victim of the attack may then spread the disease if they are able to attack with the needed body part/parts.

{{Category|Modding}}
{{Category|Creature attributes}}
{{Category|Tokens}}
[[ru:DF2012:Syndrome]]

Tree farming

2020-06-29T21:08:55Z

Albedo: reorder header templates

{{quality|Fine}}
{{av}}
{{projects}}

'''Tree Farming''' is the process of creating and managing an environment in which saplings can safely form and mature into [[tree]]s. Since planting trees is not currently possible without mods, a more indirect approach must be used. This technique may be used to supplement a thriving [[wood industry]] or to create an orchard stocked with valuable plant products. Tree farms require a moderate area and may not produce fast enough for impatient players due to the growth times involved.

==Method==

Creating a tree farm is generally straightforward, but depends on your situation and needs. A tree farm must be at least two [[z-level]]s tall (though additional z-levels can increase yield) with a [[soil]] or [[irrigation|muddied]] stone floor. Walling off (and optionally roofing over) an outside area may suffice, but larger projects are possible below ground. Note that underground plants (including trees) will only grow after a [[cavern]] has been breached.

===Aboveground===

Walling off an existing plot of trees can provide a safe environment for [[plant gathering]] and [[woodcutting]], even during a [[siege]]. A roof is necessary to fully protect from [[climber|climbing]] and [[flying]] enemies, though a sufficiently-high block wall can stop most threats. If your embark has a wooded valley you can reduce your material and labor costs significantly by incorporating it into your design.

There is a discussion involving creating a large culled Orchard at [https://redd.it/71fy5m this Reddit post].

===Top soil===

If your embark has at least two [[soil]] layers, you can create a simple tree farm by channeling down two or more layers from the surface then roofing over the hole. Surface trees will grow on "[[Tile_attributes|Light Indoor]]" tiles, allowing the creation of an indoor orchard or tree farm.

===Subterranean soil===

If your embark has at least three [[soil]] layers, the fastest way to create an underground tree farm is by channeling out two or more subterranean soil layers while leaving the bottom soil floor intact. Since soil is easily mined and requires no [[irrigation]] this is probably the easiest option if available. Note, however, that your farm might experience "light leakage" and "branch collapse" problems if you mine out the layer directly below the surface.

===Caverns===
[[Image:DF2014_tree_farm.png|thumb|right|350px|An irrigated tree farm]]

If you find a suitably-sized muddy cavern you can opt to just use that as a tree farm. Walling it off provides safety against migrating "wildlife". Existing caverns can be enlarged by channeling out layers above the soil, but any horizontal expansion will need to be [[irrigation|irrigated]]. Note: causing a [[cave-in]] to clear overhanging stone will damage the mud floors, requiring re-[[irrigation]].

===Deep Underground===

If the above options are not for you then your next option is to dig out a large underground space, haul out the waste rock, and flood it. Locate several suitable levels and set your miners to work. While your miners and haulers are hard at work set up an irrigation system. Large amounts of water will need to be utilized since evaporation is a significant force when dealing with liquid spread thin over open areas. [[Aquifer]]s, [[river]]s, and [[underground lake]]s make excellent sources, but be wary of slowing frame rates especially with lakes. Once every tile has been covered then you can opt to recycle the water by dropping it down onto a similarly opened out space on a lower level. This way you may dig out larger farms without requiring more water.

==Use and production==

Freshly watered or sporulated farms will require about three years of growing before trees reach minimal harvest size. In this time a few may show up early, but the majority will mature as a group within the span of a month of in-game time. After the first group of trees appear, trees will show up slightly more frequently and steadily as time progresses.

Certain trees (especially underground -caps) produce only one or two logs, even when fully grown. For optimum yield, those trees should be harvested as soon as they reach minimum size. Other more productive trees ([[blood thorn]]s, [[fungiwood]], and [[spore tree]]s) can be allowed to continue growing for much larger returns.

Your tree farm can be specialized into an orchard indirectly, by allowing desired trees to continue growing and cutting down any undesired trees. Note that there is an upper limit to the number of same-species trees that will grow in an area; specializing on two or more species is recommended for optimum production.

Tree farms can double as [[pasture]]s, but trampling may lead to lowered wood production in the area occupied by grazers. It is generally advisable to create separate pasture and tree farming areas since pastures do not require multiple z-levels of open space.

==Details==

Trees will not grow on soil that is occupied by rocky boulders, items, buildings or stockpiles. Removal of these obstructions will increase the productive area of your farm.

Saplings of underground trees will not form in artificial areas until a cavern has been breached. Underground saplings will die if marked as {{DFtext|Outside|3:1}}.

A sapling must fulfill a few requirements in relation to the environment in order to mature. Saplings will not mature if there are many others of the same species in the area around it. On top of this, surface trees must meet a certain density requirement based on the [[biome]] your fortress is in. If there are too many mature trees in an area then growth will be halted. Underground trees always grow with uniform density.

Harvested trees sometimes remove mud from their growth tile. For long-term sustainable production non-soil tree farms will need occasional [[irrigation]].{{bug|9951}}

Large tree farms can have a ridiculous impact on [[framerate]]s, particularly when displayed on-screen.{{bug|8877}} Multi-tile trees produce much more wood than their single-tile counterparts, so a gigantic tree farm probably isn't necessary. It may be best to create multiple small tree farms (on separate levels) as your fortress's needs increase instead of one [[megaproject]] farm.

{{Translation| dwarven = dák ivom | elvish = thelire tòbafí | goblin = tonspe gotåm | human = akan ab}}

{{Category|Trees}}
{{Category|Agriculture}}
{{Category|Guides}}
[[ru:Tree farming]]

Magma

2020-06-27T14:51:51Z

Albedo: /* Minecarts */ link

{{av}}{{Quality|Exceptional|21:13, 6 July 2010 (UTC)}}
[[File:magma_flow.gif|thumb|320px|right|Dwarves can swim in magma, but only once.]]'''Magma''' is red-hot [[fluid|molten rock]] that wells up from deep within the earth (but not so deep that it cannot be found by dwarves), entering the map either by the edges or by the area beneath a [[magma pool]]. Magma that emerges aboveground is called '''Lava'''; however the substance itself remains the same. Magma is very [[Fun]].

Magma serves as a heat source, replacing [[fuel]] in [[magma smelter]]s, [[magma forge]]s, [[magma glass furnace]]s, and [[magma kiln]]s. Magma is ''extremely'' hot, which can lead to even more [[Fun]]. Materials that can withstand the temperature of magma are called '''[[magma-safe]]''', and the list is rather extensive.

Magma never cools, but can [[Water#Evaporation|evaporate]] if left at a depth of 1/7 for long enough, much like water. When magma is mixed with water, it forms [[obsidian]] (and [[steam]]). Note that magma located above [[semi-molten rock]] will be listed as a Magma Flow; magma in magma flow tiles will disappear when mixed with water (instead of cooling into obsidian).

Without [[screw pump]]s to impart [[pressure]], magma flows rather slowly (though no more slowly than unpressurized water). A pipe to bring magma across the full map can take as much as a year to fill. This, combined with the fact that it will evaporate, can make filling a reservoir difficult and tedious. As a rule of thumb, the area coming out of a 1-wide-pipe shouldn't be more than three squares wide and 20 squares long, or else it will evaporate as fast as you fill it.

Some fire-based [[creature]]s make magma their home, or are just simply immune to it.

==Magma sources==

Magma occurs in several different geological formations:
===[[Magma pool]]s===
[[File:magma_preview.png|frame|120px|right|Not-so-lucky 7's.]]Although the name suggests them as pools, they are more like pipes. They can be found underground, however they rarely reach the upper z-levels (40+). Most end a few z-levels above the magma sea, though some may span more than 100 z-levels.
Magma pools seem to be always connected to a magma sea, and the sea and pipe can occasionally reach up to the same level, making them hard to separate. However, magma pools can be identified by the obsidian walls which surround them.
Magma pools will slowly refill themselves, giving the player an infinite source of magma. The entire embark tile containing the pool will produce sporadic bursts of magma until the magma within it is at its natural level (i.e. the magma level at embark) or until it is halted by a bridge, floor, or bottom of a wall.

===[[Volcano]]es===
Volcanoes are magma pools that extend all the way to the surface. Volcanoes are an endless source of magma as they will always refill themselves. They never erupt, unlike their real-life counterparts. Volcanoes are geographical features visible on the [[location]] screen, making them much easier to find when choosing a site for your fortress.

===[[Magma sea]]===
The magma sea is a large body of magma deep under the earth. Nearly all maps will include a magma sea at the lowest z-levels, though its inconvenient placement may inspire your dwarves to [[#Bringing Magma Up|bring the magma up]] to the fortress proper.

== Finding magma ==

Nearly all maps will have magma available at the lowest z-levels, but it can be advantageous to select a site with a more easily accessible source, particularly when starting out.

Volcanoes are visible on the "local" screen in the starting location chooser as a red ≈ - essentially, red water - and on the "region" screen as a red ^. Note that a red ≈ on the "region" screen mean something different entirely (red sand).

After you have chosen to embark in a place that has a volcano, and once your dwarves have arrived at their target destination, you should see a large red pool of lava on your map. If you don't, you should expect your volcano to be somewhere underground. You then have to use [[exploratory mining]] to find it. If you can find a large patch of obsidian on the surface that is devoid of boulders, chances are there is a magma vent below, so that would be a good place to start your mining.

Much harder than simply finding a volcano is finding a volcano that is also near suitable terrain for building. Depending on your requirements - you may be looking for a source of running [[water]], or a [[mountain]] for minerals, or a healthy [[tree]] population, a layer of [[flux]] for [[steel]] production or even all four - suitable building sites can be extremely scarce.

==Working with magma==

Although magma is a liquid, it does not move via [[pressure]] unless it has been pumped. This reduced rate of flow can allow miners to survive digging into a magma reservoir, ''if'' they are lucky enough. There are ways to minimize this risk however:

'''Digging From Above:'''
If you can find a suitable position above the magma, your miner can dig a [[channel]] while remaining above the level of the magma. Be warned, however, that your dwarves might take the ramp down into the magma channel as a shortcut; preemptively designating the channel for restricted [[traffic]] is recommended.

'''Diagonal Digging:'''
Magma moves more slowly diagonally than orthogonally, giving the miner more time to escape. However, slower flow means you must keep in mind the evaporation. You should dig a smaller channel, wait for it to fill up, and extends the channel by Digging From Above. Workers that dig into a magma reservoir are not instantly killed as the magma touches them, but they are set on fire, which will kill them very quickly. For this reason, taking steps to ensure there is adequate water available to extinguish flaming dwarves running in random directions is advised before digging into any magma pools from the side. Channeling a single square wide pit across the planned magma pipe one tile away from the wall to breach and filling it with 2/7 water using the [[Activity zone#Pit/Pond|pond zone]] tool is recommended, so the panicking dwarves have no choice but to run through the water, and the water itself turns into an obsidian wall as soon as the magma flows into it.

'''Busy To Leave:'''
{{F|111883|(see forum)}}
Dwarves who dig into magma often die not because they are unable to flee but because they choose not to. By ensuring a dwarf has another task waiting (ideally far away) they will immediately move away from the ensuing magma flow.

Simply mine up to the corner of a lava tube and then smooth the last tile. Dig a staircase within a few tiles of the place where you will be breaching that leads up and back into your fortress, this will allow your dwarf to get out before the magma gets him. Now designate the smoothed corner to be carved into a fortification. Now immediately when the dwarf begins to carve the fortification, (and this is the most important part!), designate a bunch of other tiles to be smoothed/carved. It's not important that your dwarves actually smooth, carve, or engrave those tiles, what is important is that your dwarf immediately takes another smooth/carve/engrave task elsewhere in the fortress when they finish the current one. If they do not then they will pause for the briefest of instants as they pick a new task, resulting in their death. If they have the job though, they will instantly turn and head up the staircase, stopping the magma from catching and killing them."

'''Exploit From Below:'''
{{F|110724|(see forum)}}
Miners are able to mine out tiles diagonally above them '''even if there is a bridge over their heads'''. First you dig out your magma tunnel to feed magma to wherever in your fort you need it and dig it right up against the volcano pipe. Then you channel a trench against the pipe that can be the width of the tunnel if you wish. Build a magma-safe bridge over the trench, making sure to cover it completely, and then seal off access to the magma tunnel. Dig a new separate path to access the now bridged-over trench. Finally, designate the magma wall '''on the Z level of the magma tunnel''' for mining. Your dwarves will stand in the trench beneath the bridge but will somehow still mine out the squares diagonally above them, causing the magma to flow safely onto the bridge leaving your dwarves unscathed."

Example (use {{k|<}}{{k|>}} to navigate):
<diagram>
<frame type="level" level="0">
Z=0
[%205][%205][%205][%205][%205]╗[#F00]≈≈≈[#]
....[#080]╥[#000][@880][%186][@][#F00]≈≈≈[#]
....[#080][%186][#000][@880][%186][@][#F00]≈≈≈[#]
....[#080]╨[#000][@880][%186][@][#F00]≈≈≈[#]
[%205][%205][%205][%203][%205][%185][#F00]≈≈≈[#]
[%186]X[%186][#F00]≈≈≈[#]
[%200][%205][%188][#F00]≈≈≈[#]
</frame>
<frame type=level level=1>
Z=1
[#F00]≈≈≈[#]
[#F00]≈≈≈[#]
[#F00]≈≈≈[#]
[#F00]≈≈≈[#]
[%205][%205][%205][%205][%205][%187][#F00]≈≈≈[#]
....X[%186][#F00]≈≈≈[#]
[%205][%205][%205][%205][%205][%188][#F00]≈≈≈[#]
</frame>
<frame type="level" level="-1">
Z=-1
[%201][%205][%187][#F00]≈≈≈[#]
║▲║[#F00]≈≈≈[#]
║▲║[#F00]≈≈≈[#]
║▲║[#F00]≈≈≈[#]
║.║[#F00]≈≈≈[#]
║X║[#F00]≈≈≈[#]
[%200][%205][%188][#F00]≈≈≈[#]
</frame>
</diagram>

Make sure the top z-level is sealed off from miners and '''[[Mining|Mine]]''' ({{k|d}}-{{k|d}}) the highlighted tiles on the upper z-level.

== Bringing magma up ==

Magma can be brought to the surface by three different methods: pump stacks, magma pistons, and minecarts. Pump stacks are conceptually the simplest, but require an enormous amount of in-game time to make. Magma pistons tend to be faster to make, but require more time to understand how to build them. Minecarts are a simple solution, but require more management than pump stacks because they can overfill a reservoir.

=== Pump stacks ===
Pumping magma up from the [[magma sea]] via a conventional [[screw pump#Example layouts#pump stack|pump stack]] is a lot of work, requiring dozens of pumps and significant amounts of power. Making all of the pumps [[magma safe]] also requires a lot of precious materials like iron, or a functioning glass industry.

=== Magma pistons ===
[[Magma piston]]s are another way to move magma near the surface. Magma pistons require less time and fewer precious materials to construct than pump stacks. However, magma pistons are a bit more complicated than pump stacks, so it takes more time to understand how to operate and build them.

=== Minecarts ===
[[Minecart]]s submerged in 7/7 magma (or possibly less, but 2/7 is not enough) will fill with magma. Each minecart holds 2/7 worth of magma, which is subtracted from the amount of magma in the tile. The minecart is then shown as containing magma [833]. Minecarts used for this must be made of [[magma-safe]] material.

Minecarts full of magma can be tipped at a track stop, which will pour the magma in a specified direction from the stop. Therefore, the challenge is to get the minecart full of magma to the track stop. There are two logistical hurdles, and several ways to approach them.

The first decision is how to separate the minecart from the tile of magma. The "obvious" way is to build [[roller]]s in magma to pull the minecarts out; such rollers would also need to be magma-safe. Another way is to drain the magma, and then wait for evaporation. A third way is to pump the magma out of the minecart filling area.

The second task is how to move the liberated magma-laden minecart(s) to the track stop where your smelters/forges will be built. There are, again, multiple valid approaches to this. The "obvious" way is to build tracks from the magma sea to the surface. A minecart track can be operated by dwarves or fully automatic, using powered rollers or [[Minecart#Impulse ramps|impulse ramps]]. Depending on the placement of the track stop, dangerous overflow can be prevented by making the track stop of a material that will melt/burn once the reservoir begins to overflow.

A less obvious way to move the minecarts up is to simply ''carry'' them. Dwarves can safely haul a minecart full of magma (albeit slowly, due to its weight). [[Wheelbarrow]]s may be used to speed the hauling enormously; however, if the wheelbarrows are not [[magma-safe]]* (i.e. if they are [[wood]]en), they will [[wear]] quickly, most likely disintegrating in the middle of the hauling job. If a minecart is left stranded (either because the hauler got tired, or the wheelbarrow burned up), another hauling task is assigned to move it, either back to its origin stockpile, or farther along to its destination. Be sure your stockpile settings account for these possibilities, so you don't waste a lot of time moving a minecart halfway up, then back down, in a loop.

: (* The cheapest magma-safe metal for a wheelbarrow is [[nickel]], which has few other special uses. [[Nether-cap]] is a magma-safe wood (the only one), and only grows underground. You probably [[Cavern|passed some]] on your way to the magma.)

==== Design 1 ====
In {{F|125679/4217863|one design}} posted to the forums by gchristopher, a pump can provide power to the [[roller]], making the ramp eligible for building the roller, and keeping the trench at 7 magma so the carts fill instantly.

{{diagram|spaces=yes|\
▒▒▒
▒#▒ # {{=}} floor grate
▒%▒ % {{=}} south facing pump
▒%▒▒
▒▲▲▒ Left ramp ▲ has a left-pushing roller
▒▒▒▒ Right ramp ▲ has a retracting bridge
}}

If you drop minecarts in directly from at least 2 z-levels above onto the right ramp, this setup has the magical property that it can handle an arbitrary number of minecarts, and dispense them at a constant controlled rate. Carts are pushed up the left ramp by the roller.

If you extend the right bridge, that tile ceases to be a ramp. Exactly one minecart will fall onto the tile and stay there, and all other minecarts dropped from above will form a quantum pile 1 z-level up.

The last time I [gchristopher] built one, I timed the cart dispensing rate at 1 per 8 ticks. This is slow enough that carts can be brought to the surface using an impulse ramp spiral, but fast enough that you can still quickly cover a large area with magma.

The same design works with water, for giving you a lot of flexibility creating tall waterfalls without pump stacks, quickly and cheaply.

==== Design 2 ====
Rafal99 posted {{F|109460/3374816|another design}} using dwarf-powered [[wheelbarrow]]s to transport the magma-filled minecarts from one minecart stockpile to another.

<pre>
▒ddddd=====S==<<Zccccc Near the surface (top view)
U

▒bbbbb== ==<<Xaaaaa Near the magma (side view)
\7777/

\7777/ - Magma reservoir, with tracks in it and rollers to bring minecart up
the ramp
U - Here we want magma
aabbccdd - Stockpiles accepting minecarts
===<< - Track and rollers
S - Track stop, set to lowest friction (so it doesn't stop the minecart),
set to dump the contents into the U
XZ - Track stops set to dump their contents to the left
▒ - Wall to stop minecarts
</pre>

# Empty minecarts are put into stockpile aaaaa.
# There is a hauling route with one stop on X, with assigned vehicle, set to take furniture->minecarts from stockpile aaaaa.
# Empty minecarts are put into the minecart on track stop X, the track stop dumps them to the left, placing them on the rollers.
# Rollers move the empty minecarts into the magma reservoir, they get filled with magma, then the roller on ramp moves them up. They follow the track, then go out of it and stop at the wall; effectively the minecart with magma is being placed in stockpile bbbbb.
# Stockpile ccccc is set to take from stockpile bbbbb and has assigned 3 wheelbarrows. Dwarves safely transport the minecarts with magma inside wheelbarrows up to the surface into stockpile ccccc.
# There is a hauling route with one stop on Z, with assigned vehicle, set to take furniture->minecarts from stockpile ccccc.
# Magma minecarts are put into the minecart on track stop Z, and the track stop dumps them to the left, placing them on the rollers. (Same as in 3.)
# Rollers move the magma minecarts along the track. They pass through the track stop S and dump the magma in the destination point U, then they follow the track, go out of it and stop at the wall; effectively the emptied minecart is being placed in stockpile ddddd.
# Stockpile aaaaa is set to take from stockpile ddddd. Dwarves haul the empty minecarts back underground near the magma into stockpile aaaaa.
Then we go back to start and the whole thing repeats.

==== Design 3: Minimalist magma moving ====

You'll need two magma-safe pumps, a magma-safe wheelbarrow, and at least one magma-safe minecart.
<diagram>
sideview
░░░░░░░░░░░░░░░░░░░░░░░
░░░ %% ░░░░░░░░░░░░
░░░░░░░░░░▲%%_░░░░░░░░░
░░░░░░░░░░░░░[#c00]7777777[#]░░░
</diagram>

# Dig down to the magma sea and channel a tile above the magma
# Optionally build a floor grate (_) over the hole to keep magma critters out
# Build the first pump to pull magma up into a 1x1 room with a ramp (▲)
# Build the second pump to pull the magma out of the 1x1 room and dispose of it (a 3x3 evaporation chamber works fine)
# Designate a garbage dump zone in the 1x1 room and dump all your magma-safe minecarts
# Wait for all the minecarts to be carried down to the dump zone
# Operate pump 1 briefly, then stop it and activate pump 2 briefly (the minecarts should now contain magma)
# Designate a minecart stockpile near your desired magma workshops, and set it to use your magma-safe wheelbarrow
# Unforbid your minecarts and wait for your dwarves to wheelbarrow them up to the stockpile
# Build a dumping track stop to place the magma where you want it
# Create a new hauling route, specify a new stop on the constructed track stop, and assign one of the magma minecarts to the route
# Unassign the cart, and mark it for dumping; once you've emptied all the carts return to step 6

This design is only useful for moving small amounts of magma, but it is simple and flexible. With any luck you can have your topside magma workshops up and running in the first year.

WARNING: do not attempt to over-fill multi-tile magma pits to full (i.e., a 3x1 pit at 6 depth on each tile) there is a high chance of the magma flowing outwards instead of into the other magma tile resulting in burnt dwarves and FUN.
Note: If necessary, use hatches to control pump operation.

==== Design 4: Urist's Cradle ====
This design works fairly reliable while requiring no powered rollers. It works using [[Minecart#Impulse ramps|impulse ramps]] and is thus considered an exploit.

As seen from the side (south):
<pre>
0: ▒▒
-1: ▒▒▲▲▲▲▒▒

Legend:
▲: impulse ramp (south-east or north-east oriented) , 7/7 magma
▒: solid wall / ground
</pre>
The minecarts arrive from the left with high speed, bump into the walls, drop into the 7/7 magma and get accelerated by the impulse ramps. Because of *physics*, the minecarts get stuck at the last impulse ramp on the right. A second minecart, also coming from the left, will push the first minecart out, filled with magma.

==Using magma==
The primary use for magma is to <s>flood your fortress</s> power [[magma smelter]]s, [[magma glass furnace]]s, [[magma kiln]]s, and [[magma forge]]s. To power a building with magma at least one of the external eight squares must be a hole above a square of magma on the level below.
Placing one of the workshop's [[impassable tile]]s above the magma conveniently prevents clumsy dwarves from falling in.
This seems to usually prevent magma critters from pathing in, but there was a bug report {{bugl|1189}} about [[magma man]] who somehow made its way through without [[building destroyer|destroying]] the furnace in question - it's not clear whether this was normal movement, dodging attack of another critter, [[building destroyer]] activity gone wrong, pathfinding bug, etc. Either way, if you feed magma from a wild area to furnaces via channel, locking it with a [[floodgate]] or raised [[bridge]] is a good idea.
Magma used this way is not consumed; a single tile of magma can operate the furnace indefinitely.

Other uses for magma include [[obsidian farming]], [[DF2012:Trap_design#Magma_and_fire_traps|trap design]], melting [[ice]], igniting [[fire]]s, and even [[garbage disposal]]. It's unknown whether flow push bug {{Bug|5458}} can be a problem with magma, so if you want to be sure, protect the intake with floor grate - like water, except it won't get back up on its own.

Magma saves all the work for fuel (but not flux for steel), so "dig down to magma" is a reasonable strategy for starting metal/glass/ceramics industry. As to the other magma uses - if you get lucky, the first dwarven caravan will bring all the tools you need. If not, you can forge your own by melting down the surplus of anvils that caravans carry, or just embark with a couple chunks of iron [[ore]] or ready bars of [[nickel]] (cheaper, but have few other uses). If you are in a hurry, you usually can take a nickel minecart on embark (at the same price as iron anvil), but to have magma-safe rollers you'll need a forge either way: metal chains seem to ''never'' be available on embark {{verify}}.

==Properties of magma==
Magma behaves the same way as water with the exception of not being affected by [[pressure]] (except when being moved by a [[screw pump]]) and apparently not showing [[flow]]. Magma will turn into [[obsidian]]1 if it touches [[water]]. In the game, magma's temperature is {{ct|12000}}. See the list of '''[[magma-safe]]''' materials for more information on what can (or cannot) be safely submerged in magma.

Tiles directly adjacent to magma will be heated to a temperature of {{ct|10075}}, causing revealed unmined tiles to flash with {{Tile|☼|6:4:1}} when placing digging designations and causing unrevealed mining-designated tiles to [[Digging designation canceled|cancel their designation with a "warm stone" warning]] once they are revealed.

Magma can melt ice beyond the "warm" wall, but this happens ''only when magma moves in'': {{F|72296/1795893|later the same reservoir may freeze just like when magma was not there}}. Whether magma needs to be moved out and in, or depth recalculation is enough is unknown {{verify}}.

Implication of the two above effects is that when magma appears or disappears somewhere, that one and several adjacent tiles start or stop being {{Tile|☼|6:4:1}} "warm" - and there are likely to be temperature recalculations for the tiles adjacent to ''them'' - in addition to processing that happens when moving water. This means that having streams of magma changed or pumped (since a pump can drain its source) tend to cause major FPS drop, which can be prevented by keeping the affected tiles continuously "warm" with small buffer reservoirs (see [[Screw_pump#Improved_Magma_Pump_Stack|Improved Magma Pump Stack]] design by NecroRebel).

[[Construction]]s ([[wall]]s, [[floor]]s, etc.) of any material can safely contain magma. Non-construction [[building]]s ([[door]]s, [[bridge]]s, [[Screw pump|pump]]s, etc.) that come into contact with magma should be built entirely of [[magma-safe]] materials. Non-magma-safe components will eventually melt and the building will deconstruct. Any [[mechanism]]s likely to come into contact with magma should also be made of magma-safe materials.

1 - specifically, one of the inorganic materials having the [LAVA] tag, selected randomly ''per biome'' during worldgen.

==Dangers of magma==
Any contact with magma results in nearly instant immolation, followed by death if water is not close at hand. Additionally, dropping large items into magma will generate clouds of [[magma mist]] which can set your haulers on fire if you aren't careful. Magma is also home to various fiery creatures which can present a significant threat to unprepared fortresses.

{{D for Dwarf}}

Magma is very well known for being the perfect solution to any problem encountered by dwarves. Giant badger invasion? Pour magma on it. Noble being his usual snotty, useless, arrogant self? Pour magma on it. Door locked due to invaders? Pour magma on it! Flooded your fortress with magma? [[Fun|Congratulations, you just won the game!]]

Magma is often referred to as the blood of the earth. Some dwarves interpret this literally, expressing concerns that the earth is capable of bleeding to death. This has led dwarven [[elf|conservationists]] to declare magma a finite resource, advocating stricter regulations on the use of magma-powered workshops.

However, this hypothesis is flawed. The larger a creature, the more blood it has. The world is at least twice as large as a [[giant sperm whale]], the largest creature known to dwarfkind. Therefore, any [[Bloodline:Boatmurdered|pumping operation]] capable of bleeding the world dry would flood the surface and caverns to such a degree as to render the world uninhabitable. On the other hand, this would usher in the [[calendar|age of death]], and thus the earth would indeed be considered dead.

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

{{Category|Physics}}
[[Ru:Magma]]

Magma

2020-06-27T14:49:11Z

Albedo: /* Minecarts */ de-cap

{{av}}{{Quality|Exceptional|21:13, 6 July 2010 (UTC)}}
[[File:magma_flow.gif|thumb|320px|right|Dwarves can swim in magma, but only once.]]'''Magma''' is red-hot [[fluid|molten rock]] that wells up from deep within the earth (but not so deep that it cannot be found by dwarves), entering the map either by the edges or by the area beneath a [[magma pool]]. Magma that emerges aboveground is called '''Lava'''; however the substance itself remains the same. Magma is very [[Fun]].

Magma serves as a heat source, replacing [[fuel]] in [[magma smelter]]s, [[magma forge]]s, [[magma glass furnace]]s, and [[magma kiln]]s. Magma is ''extremely'' hot, which can lead to even more [[Fun]]. Materials that can withstand the temperature of magma are called '''[[magma-safe]]''', and the list is rather extensive.

Magma never cools, but can [[Water#Evaporation|evaporate]] if left at a depth of 1/7 for long enough, much like water. When magma is mixed with water, it forms [[obsidian]] (and [[steam]]). Note that magma located above [[semi-molten rock]] will be listed as a Magma Flow; magma in magma flow tiles will disappear when mixed with water (instead of cooling into obsidian).

Without [[screw pump]]s to impart [[pressure]], magma flows rather slowly (though no more slowly than unpressurized water). A pipe to bring magma across the full map can take as much as a year to fill. This, combined with the fact that it will evaporate, can make filling a reservoir difficult and tedious. As a rule of thumb, the area coming out of a 1-wide-pipe shouldn't be more than three squares wide and 20 squares long, or else it will evaporate as fast as you fill it.

Some fire-based [[creature]]s make magma their home, or are just simply immune to it.

==Magma sources==

Magma occurs in several different geological formations:
===[[Magma pool]]s===
[[File:magma_preview.png|frame|120px|right|Not-so-lucky 7's.]]Although the name suggests them as pools, they are more like pipes. They can be found underground, however they rarely reach the upper z-levels (40+). Most end a few z-levels above the magma sea, though some may span more than 100 z-levels.
Magma pools seem to be always connected to a magma sea, and the sea and pipe can occasionally reach up to the same level, making them hard to separate. However, magma pools can be identified by the obsidian walls which surround them.
Magma pools will slowly refill themselves, giving the player an infinite source of magma. The entire embark tile containing the pool will produce sporadic bursts of magma until the magma within it is at its natural level (i.e. the magma level at embark) or until it is halted by a bridge, floor, or bottom of a wall.

===[[Volcano]]es===
Volcanoes are magma pools that extend all the way to the surface. Volcanoes are an endless source of magma as they will always refill themselves. They never erupt, unlike their real-life counterparts. Volcanoes are geographical features visible on the [[location]] screen, making them much easier to find when choosing a site for your fortress.

===[[Magma sea]]===
The magma sea is a large body of magma deep under the earth. Nearly all maps will include a magma sea at the lowest z-levels, though its inconvenient placement may inspire your dwarves to [[#Bringing Magma Up|bring the magma up]] to the fortress proper.

== Finding magma ==

Nearly all maps will have magma available at the lowest z-levels, but it can be advantageous to select a site with a more easily accessible source, particularly when starting out.

Volcanoes are visible on the "local" screen in the starting location chooser as a red ≈ - essentially, red water - and on the "region" screen as a red ^. Note that a red ≈ on the "region" screen mean something different entirely (red sand).

After you have chosen to embark in a place that has a volcano, and once your dwarves have arrived at their target destination, you should see a large red pool of lava on your map. If you don't, you should expect your volcano to be somewhere underground. You then have to use [[exploratory mining]] to find it. If you can find a large patch of obsidian on the surface that is devoid of boulders, chances are there is a magma vent below, so that would be a good place to start your mining.

Much harder than simply finding a volcano is finding a volcano that is also near suitable terrain for building. Depending on your requirements - you may be looking for a source of running [[water]], or a [[mountain]] for minerals, or a healthy [[tree]] population, a layer of [[flux]] for [[steel]] production or even all four - suitable building sites can be extremely scarce.

==Working with magma==

Although magma is a liquid, it does not move via [[pressure]] unless it has been pumped. This reduced rate of flow can allow miners to survive digging into a magma reservoir, ''if'' they are lucky enough. There are ways to minimize this risk however:

'''Digging From Above:'''
If you can find a suitable position above the magma, your miner can dig a [[channel]] while remaining above the level of the magma. Be warned, however, that your dwarves might take the ramp down into the magma channel as a shortcut; preemptively designating the channel for restricted [[traffic]] is recommended.

'''Diagonal Digging:'''
Magma moves more slowly diagonally than orthogonally, giving the miner more time to escape. However, slower flow means you must keep in mind the evaporation. You should dig a smaller channel, wait for it to fill up, and extends the channel by Digging From Above. Workers that dig into a magma reservoir are not instantly killed as the magma touches them, but they are set on fire, which will kill them very quickly. For this reason, taking steps to ensure there is adequate water available to extinguish flaming dwarves running in random directions is advised before digging into any magma pools from the side. Channeling a single square wide pit across the planned magma pipe one tile away from the wall to breach and filling it with 2/7 water using the [[Activity zone#Pit/Pond|pond zone]] tool is recommended, so the panicking dwarves have no choice but to run through the water, and the water itself turns into an obsidian wall as soon as the magma flows into it.

'''Busy To Leave:'''
{{F|111883|(see forum)}}
Dwarves who dig into magma often die not because they are unable to flee but because they choose not to. By ensuring a dwarf has another task waiting (ideally far away) they will immediately move away from the ensuing magma flow.

Simply mine up to the corner of a lava tube and then smooth the last tile. Dig a staircase within a few tiles of the place where you will be breaching that leads up and back into your fortress, this will allow your dwarf to get out before the magma gets him. Now designate the smoothed corner to be carved into a fortification. Now immediately when the dwarf begins to carve the fortification, (and this is the most important part!), designate a bunch of other tiles to be smoothed/carved. It's not important that your dwarves actually smooth, carve, or engrave those tiles, what is important is that your dwarf immediately takes another smooth/carve/engrave task elsewhere in the fortress when they finish the current one. If they do not then they will pause for the briefest of instants as they pick a new task, resulting in their death. If they have the job though, they will instantly turn and head up the staircase, stopping the magma from catching and killing them."

'''Exploit From Below:'''
{{F|110724|(see forum)}}
Miners are able to mine out tiles diagonally above them '''even if there is a bridge over their heads'''. First you dig out your magma tunnel to feed magma to wherever in your fort you need it and dig it right up against the volcano pipe. Then you channel a trench against the pipe that can be the width of the tunnel if you wish. Build a magma-safe bridge over the trench, making sure to cover it completely, and then seal off access to the magma tunnel. Dig a new separate path to access the now bridged-over trench. Finally, designate the magma wall '''on the Z level of the magma tunnel''' for mining. Your dwarves will stand in the trench beneath the bridge but will somehow still mine out the squares diagonally above them, causing the magma to flow safely onto the bridge leaving your dwarves unscathed."

Example (use {{k|<}}{{k|>}} to navigate):
<diagram>
<frame type="level" level="0">
Z=0
[%205][%205][%205][%205][%205]╗[#F00]≈≈≈[#]
....[#080]╥[#000][@880][%186][@][#F00]≈≈≈[#]
....[#080][%186][#000][@880][%186][@][#F00]≈≈≈[#]
....[#080]╨[#000][@880][%186][@][#F00]≈≈≈[#]
[%205][%205][%205][%203][%205][%185][#F00]≈≈≈[#]
[%186]X[%186][#F00]≈≈≈[#]
[%200][%205][%188][#F00]≈≈≈[#]
</frame>
<frame type=level level=1>
Z=1
[#F00]≈≈≈[#]
[#F00]≈≈≈[#]
[#F00]≈≈≈[#]
[#F00]≈≈≈[#]
[%205][%205][%205][%205][%205][%187][#F00]≈≈≈[#]
....X[%186][#F00]≈≈≈[#]
[%205][%205][%205][%205][%205][%188][#F00]≈≈≈[#]
</frame>
<frame type="level" level="-1">
Z=-1
[%201][%205][%187][#F00]≈≈≈[#]
║▲║[#F00]≈≈≈[#]
║▲║[#F00]≈≈≈[#]
║▲║[#F00]≈≈≈[#]
║.║[#F00]≈≈≈[#]
║X║[#F00]≈≈≈[#]
[%200][%205][%188][#F00]≈≈≈[#]
</frame>
</diagram>

Make sure the top z-level is sealed off from miners and '''[[Mining|Mine]]''' ({{k|d}}-{{k|d}}) the highlighted tiles on the upper z-level.

== Bringing magma up ==

Magma can be brought to the surface by three different methods: pump stacks, magma pistons, and minecarts. Pump stacks are conceptually the simplest, but require an enormous amount of in-game time to make. Magma pistons tend to be faster to make, but require more time to understand how to build them. Minecarts are a simple solution, but require more management than pump stacks because they can overfill a reservoir.

=== Pump stacks ===
Pumping magma up from the [[magma sea]] via a conventional [[screw pump#Example layouts#pump stack|pump stack]] is a lot of work, requiring dozens of pumps and significant amounts of power. Making all of the pumps [[magma safe]] also requires a lot of precious materials like iron, or a functioning glass industry.

=== Magma pistons ===
[[Magma piston]]s are another way to move magma near the surface. Magma pistons require less time and fewer precious materials to construct than pump stacks. However, magma pistons are a bit more complicated than pump stacks, so it takes more time to understand how to operate and build them.

=== Minecarts ===
[[Minecart]]s submerged in 7/7 magma (or possibly less, but 2/7 is not enough) will fill with magma. Each minecart holds 2/7 worth of magma, which is subtracted from the amount of magma in the tile. The minecart is then shown as containing magma [833]. Minecarts used for this must be made of [[magma-safe]] material.

Minecarts full of magma can be tipped at a track stop, which will pour the magma in a specified direction from the stop. Therefore, the challenge is to get the minecart full of magma to the track stop. There are two logistical hurdles, and several ways to approach them.

The first decision is how to separate the minecart from the tile of magma. The "obvious" way is to build [[roller]]s in magma to pull the minecarts out; such rollers would also need to be magma-safe. Another way is to drain the magma, and then wait for evaporation. A third way is to pump the magma out of the minecart filling area.

The second task is how to move the liberated magma-laden minecart(s) to the track stop where your smelters/forges will be built. There are, again, multiple valid approaches to this. The "obvious" way is to build tracks from the magma sea to the surface. A minecart track can be operated by dwarves or fully automatic, using powered rollers or [[Minecart#Impulse ramps|impulse ramps]]. Depending on the placement of the track stop, dangerous overflow can be prevented by making the track stop of a material that will melt/burn once the reservoir begins to overflow.

A less obvious way to move the minecarts up is to simply ''carry'' them. Dwarves can safely haul a minecart full of magma (albeit slowly, due to its weight). [[Wheelbarrow]]s may be used to speed the hauling enormously; however, if the wheelbarrows are not [[magma-safe]]* (i.e. if they are [[wood]]en), they will [[wear]] quickly, most likely disintegrating in the middle of the hauling job. If a minecart is left stranded (either because the hauler got tired, or the wheelbarrow burned up), another hauling task is assigned to move it, either back to its origin stockpile, or farther along to its destination. Be sure your stockpile settings account for these possibilities, so you don't waste a lot of time moving a minecart halfway up, then back down, in a loop.

: (* The cheapest magma-safe metal for a wheelbarrow is [[nickel]], which has few other special uses. [[Nether-cap]] is a magma-safe wood (the only one), and only grows underground. You probably passed some on your way to the magma.)

==== Design 1 ====
In {{F|125679/4217863|one design}} posted to the forums by gchristopher, a pump can provide power to the [[roller]], making the ramp eligible for building the roller, and keeping the trench at 7 magma so the carts fill instantly.

{{diagram|spaces=yes|\
▒▒▒
▒#▒ # {{=}} floor grate
▒%▒ % {{=}} south facing pump
▒%▒▒
▒▲▲▒ Left ramp ▲ has a left-pushing roller
▒▒▒▒ Right ramp ▲ has a retracting bridge
}}

If you drop minecarts in directly from at least 2 z-levels above onto the right ramp, this setup has the magical property that it can handle an arbitrary number of minecarts, and dispense them at a constant controlled rate. Carts are pushed up the left ramp by the roller.

If you extend the right bridge, that tile ceases to be a ramp. Exactly one minecart will fall onto the tile and stay there, and all other minecarts dropped from above will form a quantum pile 1 z-level up.

The last time I [gchristopher] built one, I timed the cart dispensing rate at 1 per 8 ticks. This is slow enough that carts can be brought to the surface using an impulse ramp spiral, but fast enough that you can still quickly cover a large area with magma.

The same design works with water, for giving you a lot of flexibility creating tall waterfalls without pump stacks, quickly and cheaply.

==== Design 2 ====
Rafal99 posted {{F|109460/3374816|another design}} using dwarf-powered [[wheelbarrow]]s to transport the magma-filled minecarts from one minecart stockpile to another.

<pre>
▒ddddd=====S==<<Zccccc Near the surface (top view)
U

▒bbbbb== ==<<Xaaaaa Near the magma (side view)
\7777/

\7777/ - Magma reservoir, with tracks in it and rollers to bring minecart up
the ramp
U - Here we want magma
aabbccdd - Stockpiles accepting minecarts
===<< - Track and rollers
S - Track stop, set to lowest friction (so it doesn't stop the minecart),
set to dump the contents into the U
XZ - Track stops set to dump their contents to the left
▒ - Wall to stop minecarts
</pre>

# Empty minecarts are put into stockpile aaaaa.
# There is a hauling route with one stop on X, with assigned vehicle, set to take furniture->minecarts from stockpile aaaaa.
# Empty minecarts are put into the minecart on track stop X, the track stop dumps them to the left, placing them on the rollers.
# Rollers move the empty minecarts into the magma reservoir, they get filled with magma, then the roller on ramp moves them up. They follow the track, then go out of it and stop at the wall; effectively the minecart with magma is being placed in stockpile bbbbb.
# Stockpile ccccc is set to take from stockpile bbbbb and has assigned 3 wheelbarrows. Dwarves safely transport the minecarts with magma inside wheelbarrows up to the surface into stockpile ccccc.
# There is a hauling route with one stop on Z, with assigned vehicle, set to take furniture->minecarts from stockpile ccccc.
# Magma minecarts are put into the minecart on track stop Z, and the track stop dumps them to the left, placing them on the rollers. (Same as in 3.)
# Rollers move the magma minecarts along the track. They pass through the track stop S and dump the magma in the destination point U, then they follow the track, go out of it and stop at the wall; effectively the emptied minecart is being placed in stockpile ddddd.
# Stockpile aaaaa is set to take from stockpile ddddd. Dwarves haul the empty minecarts back underground near the magma into stockpile aaaaa.
Then we go back to start and the whole thing repeats.

==== Design 3: Minimalist magma moving ====

You'll need two magma-safe pumps, a magma-safe wheelbarrow, and at least one magma-safe minecart.
<diagram>
sideview
░░░░░░░░░░░░░░░░░░░░░░░
░░░ %% ░░░░░░░░░░░░
░░░░░░░░░░▲%%_░░░░░░░░░
░░░░░░░░░░░░░[#c00]7777777[#]░░░
</diagram>

# Dig down to the magma sea and channel a tile above the magma
# Optionally build a floor grate (_) over the hole to keep magma critters out
# Build the first pump to pull magma up into a 1x1 room with a ramp (▲)
# Build the second pump to pull the magma out of the 1x1 room and dispose of it (a 3x3 evaporation chamber works fine)
# Designate a garbage dump zone in the 1x1 room and dump all your magma-safe minecarts
# Wait for all the minecarts to be carried down to the dump zone
# Operate pump 1 briefly, then stop it and activate pump 2 briefly (the minecarts should now contain magma)
# Designate a minecart stockpile near your desired magma workshops, and set it to use your magma-safe wheelbarrow
# Unforbid your minecarts and wait for your dwarves to wheelbarrow them up to the stockpile
# Build a dumping track stop to place the magma where you want it
# Create a new hauling route, specify a new stop on the constructed track stop, and assign one of the magma minecarts to the route
# Unassign the cart, and mark it for dumping; once you've emptied all the carts return to step 6

This design is only useful for moving small amounts of magma, but it is simple and flexible. With any luck you can have your topside magma workshops up and running in the first year.

WARNING: do not attempt to over-fill multi-tile magma pits to full (i.e., a 3x1 pit at 6 depth on each tile) there is a high chance of the magma flowing outwards instead of into the other magma tile resulting in burnt dwarves and FUN.
Note: If necessary, use hatches to control pump operation.

==== Design 4: Urist's Cradle ====
This design works fairly reliable while requiring no powered rollers. It works using [[Minecart#Impulse ramps|impulse ramps]] and is thus considered an exploit.

As seen from the side (south):
<pre>
0: ▒▒
-1: ▒▒▲▲▲▲▒▒

Legend:
▲: impulse ramp (south-east or north-east oriented) , 7/7 magma
▒: solid wall / ground
</pre>
The minecarts arrive from the left with high speed, bump into the walls, drop into the 7/7 magma and get accelerated by the impulse ramps. Because of *physics*, the minecarts get stuck at the last impulse ramp on the right. A second minecart, also coming from the left, will push the first minecart out, filled with magma.

==Using magma==
The primary use for magma is to <s>flood your fortress</s> power [[magma smelter]]s, [[magma glass furnace]]s, [[magma kiln]]s, and [[magma forge]]s. To power a building with magma at least one of the external eight squares must be a hole above a square of magma on the level below.
Placing one of the workshop's [[impassable tile]]s above the magma conveniently prevents clumsy dwarves from falling in.
This seems to usually prevent magma critters from pathing in, but there was a bug report {{bugl|1189}} about [[magma man]] who somehow made its way through without [[building destroyer|destroying]] the furnace in question - it's not clear whether this was normal movement, dodging attack of another critter, [[building destroyer]] activity gone wrong, pathfinding bug, etc. Either way, if you feed magma from a wild area to furnaces via channel, locking it with a [[floodgate]] or raised [[bridge]] is a good idea.
Magma used this way is not consumed; a single tile of magma can operate the furnace indefinitely.

Other uses for magma include [[obsidian farming]], [[DF2012:Trap_design#Magma_and_fire_traps|trap design]], melting [[ice]], igniting [[fire]]s, and even [[garbage disposal]]. It's unknown whether flow push bug {{Bug|5458}} can be a problem with magma, so if you want to be sure, protect the intake with floor grate - like water, except it won't get back up on its own.

Magma saves all the work for fuel (but not flux for steel), so "dig down to magma" is a reasonable strategy for starting metal/glass/ceramics industry. As to the other magma uses - if you get lucky, the first dwarven caravan will bring all the tools you need. If not, you can forge your own by melting down the surplus of anvils that caravans carry, or just embark with a couple chunks of iron [[ore]] or ready bars of [[nickel]] (cheaper, but have few other uses). If you are in a hurry, you usually can take a nickel minecart on embark (at the same price as iron anvil), but to have magma-safe rollers you'll need a forge either way: metal chains seem to ''never'' be available on embark {{verify}}.

==Properties of magma==
Magma behaves the same way as water with the exception of not being affected by [[pressure]] (except when being moved by a [[screw pump]]) and apparently not showing [[flow]]. Magma will turn into [[obsidian]]1 if it touches [[water]]. In the game, magma's temperature is {{ct|12000}}. See the list of '''[[magma-safe]]''' materials for more information on what can (or cannot) be safely submerged in magma.

Tiles directly adjacent to magma will be heated to a temperature of {{ct|10075}}, causing revealed unmined tiles to flash with {{Tile|☼|6:4:1}} when placing digging designations and causing unrevealed mining-designated tiles to [[Digging designation canceled|cancel their designation with a "warm stone" warning]] once they are revealed.

Magma can melt ice beyond the "warm" wall, but this happens ''only when magma moves in'': {{F|72296/1795893|later the same reservoir may freeze just like when magma was not there}}. Whether magma needs to be moved out and in, or depth recalculation is enough is unknown {{verify}}.

Implication of the two above effects is that when magma appears or disappears somewhere, that one and several adjacent tiles start or stop being {{Tile|☼|6:4:1}} "warm" - and there are likely to be temperature recalculations for the tiles adjacent to ''them'' - in addition to processing that happens when moving water. This means that having streams of magma changed or pumped (since a pump can drain its source) tend to cause major FPS drop, which can be prevented by keeping the affected tiles continuously "warm" with small buffer reservoirs (see [[Screw_pump#Improved_Magma_Pump_Stack|Improved Magma Pump Stack]] design by NecroRebel).

[[Construction]]s ([[wall]]s, [[floor]]s, etc.) of any material can safely contain magma. Non-construction [[building]]s ([[door]]s, [[bridge]]s, [[Screw pump|pump]]s, etc.) that come into contact with magma should be built entirely of [[magma-safe]] materials. Non-magma-safe components will eventually melt and the building will deconstruct. Any [[mechanism]]s likely to come into contact with magma should also be made of magma-safe materials.

1 - specifically, one of the inorganic materials having the [LAVA] tag, selected randomly ''per biome'' during worldgen.

==Dangers of magma==
Any contact with magma results in nearly instant immolation, followed by death if water is not close at hand. Additionally, dropping large items into magma will generate clouds of [[magma mist]] which can set your haulers on fire if you aren't careful. Magma is also home to various fiery creatures which can present a significant threat to unprepared fortresses.

{{D for Dwarf}}

Magma is very well known for being the perfect solution to any problem encountered by dwarves. Giant badger invasion? Pour magma on it. Noble being his usual snotty, useless, arrogant self? Pour magma on it. Door locked due to invaders? Pour magma on it! Flooded your fortress with magma? [[Fun|Congratulations, you just won the game!]]

Magma is often referred to as the blood of the earth. Some dwarves interpret this literally, expressing concerns that the earth is capable of bleeding to death. This has led dwarven [[elf|conservationists]] to declare magma a finite resource, advocating stricter regulations on the use of magma-powered workshops.

However, this hypothesis is flawed. The larger a creature, the more blood it has. The world is at least twice as large as a [[giant sperm whale]], the largest creature known to dwarfkind. Therefore, any [[Bloodline:Boatmurdered|pumping operation]] capable of bleeding the world dry would flood the surface and caverns to such a degree as to render the world uninhabitable. On the other hand, this would usher in the [[calendar|age of death]], and thus the earth would indeed be considered dead.

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

{{Category|Physics}}
[[Ru:Magma]]

Aquifer

2020-06-27T13:38:10Z

Albedo: subsections

{{Quality|Masterwork|15:04, 18 May 2015 (UTC)}}
{{av}}
[[File:aqua_varied.png|thumb|right|158px|Area with a varied aquifer.]]An '''aquifer''' is a subterranean layer of [[water|groundwater]]-bearing rock or [[soil]]. As of {{version|0.47.01}}, there are two types of aquifers: {{DFtext|Light aquifer|1:1}} and {{DFtext|Heavy aquifer|1:1}}, with Light aquifers being by far the most common. Prior to this, all aquifers behaved as the "Heavy" type.

Aquifers are tiles which produce water in their ''neighboring'' tiles -- north, south, east, west, and below. They do not produce water in the tile above them, nor in any diagonally-adjacent tiles.

Aquifers cannot be drained; the groundwater is limitless, with even a single isolated tile leaking water forever. However, [[smoothing|smoothed]], mined, carved staircase, or channeled aquifer tiles no longer produce water.

Aquifers located in [[ocean]] [[biome]]s will produce salty water; aquifers in other biomes will produce freshwater. The frequency of aquifers differs between embark locations.

If you are digging an up/down staircase in the downward direction and you hit an aquifer, the aquifer tile will be revealed as damp soil or stone and the digging job will be un-designated for that tile. If you are mining horizontally, you will similarly be warned of a "damp stone" before breaching the aquifer. If you are digging an up/down staircase in the ''upward'' direction, or a ramp, and you hit an aquifer from below, the aquifer tile will immediately start producing water in the stairwell. In the case of Heavy aquifers, this can lead to a lot of [[Fun]].

== Types of aquifers ==
=== Light Aquifers ===
Light Aquifers are by far the most common (being ~19 out of every 20 aquifers), and produce water at a greatly diminished rate. As a result, they can easily be penetrated with minimal effort by digging out one level at a time and walling it off reasonably quickly. Light aquifers can be very useful for low-water applications such as slowly filling a cistern for wells, or feeding an atomspheric waterfall.

An open tile will receive light-aquifer water if it's directly north, south, east, west, or below a light aquifer tile. There's no diagonal transmission.

The amount of water that the open tile receives is random. On average, an open tile will receive four units of light-aquifer water per month. But that number can go as low as two or as high as six.

If an open tile is adjacent to a single light-aquifer tile, then it receives just as much water as an open tile surrounded by light-aquifer tiles. One is all you need.

Water at level 1/7 does not evaporate on a floor of what had been a light aquifer tile.

Unlike heavy aquifers, light aquifers tiles do not drain away water.

=== Heavy Aquifers ===
Unlike Light Aquifers, Heavy aquifers produce water almost immediately, effectively halting excavation at or below the aquifer level. This, in conjunction with the fact that they are often located in areas rich in [[loam]] and [[sand]], makes it difficult to find great quantities of [[stone]] in areas with heavy aquifers, making for more challenging gameplay.

Unmined heavy aquifer tiles also act as an infinite ''sink'' for water, just like an open map edge. A single aquifer tile can absorb any amount of [[pressure|pressurized]] water each tick, limited only by the supply. One less obvious consequence is that if an opening is made through a multi-layer aquifer, only the lowest opened layer will ever fill with water.

Empirically, Heavy aquifers gain approximately 1/7 water every 14 ticks, though production has been observed to vary from 2-28 ticks. This rate does not appear to change significantly based on the number of adjacent aquifer tiles.

=== Varied Aquifers ===
In addition to the {{DFtext|Heavy|1:1}} and {{DFtext|Light|1:1}} types of aquifer, DF can also display {{DFtext|Varied aquifer|1:1}} on the pre embark screen, which means there are some tiles with light and some tiles with heavy aquifers in the embark rectangle (also note that the biomes of neighboring tiles can "spill over" into a tile, resulting in different, unannounced, aquifers in those parts).

== Where they are found ==

Aquifers appear based on the elevation of the terrain. Low elevations - particularly those near rivers and oceans - are more prone to having an aquifer present, while locations closer to mountains are much less likely, but still possible.

Layers which '''can''' contain aquifers:
*[[sandy clay loam]]
*[[silty clay loam]]
*[[loam]]
*[[sandy loam]]
*[[silt loam]]
*[[loamy sand]]
*[[silt]]
*[[sand (tan)|sand]]
*[[yellow sand]]
*[[white sand]]
*[[black sand]]
*[[red sand]]
*[[peat]]
*[[pelagic clay]]
*[[calcareous ooze]]
*[[siliceous ooze]]
*[[sandstone]]
*[[conglomerate]]
*[[puddingstone]]



Layers which '''cannot''' contain aquifers, despite their names suggesting otherwise:
*[[clay]]
*[[silty clay]]
*[[sandy clay]]
*[[clay loam]]
*[[siltstone]]
*[[mudstone]]

== Working in aquifers ==
When working in aquifers, some points to keep in mind include:

*Water on the tile where a worker is standing will cause job cancellations if it gets too high. A construction job (e.g. wall building) will be suspended by 2/7 depth, but a mining job will only be stopped by 4/7 depth of water.
* Flowing water will cause parents to drop their infants, leading to job cancellations and occasionally [[fun]].
* Aquifers do not create water in diagonal tiles, but do create water in open tiles directly below them. Therefore, you will want to dig two z-levels below the lowest aquifer layer before continuing with your fortress.

=== Probing an aquifer ===

You can discover what layer lies below an aquifer layer by digging up/down stairs into the aquifer. This will reveal the tile below the aquifer layer, and if this is non-aquifer (for example, clay, ore or bedrock) then you know the aquifer is only 1z deep at that location. This method can only be used to determine whether the aquifer is 1 layer deep, or multiple layers deep, but this is still enough information to help plan how to penetrate it. Using a pump-based method is highly recommended for multiple layer Heavy aquifers.

== Dealing with Heavy Aquifers ==
===Going around===
If your embark site is covered by multiple biomes, there is a chance the Heavy aquifer is not present in every biome. In some maps this may be indicated by an outcropping of stone in a landscape otherwise composed of soil; in other maps the change in biome might be visible as a change in soil type, vegetation type or density. You might be able to dig down through a biome that doesn't have a heavy aquifer, to a Z-level below the heavy aquifer, and then (if you wish) tunnel beneath the heavy aquifer to the previously -inaccessible region.

Even if all the biomes of your site contain aquifers, they might not all be at the same Z-level, so you still might be able to dig down in one biome, reaching a Z-level beneath the aquifer in another biome.

Additionally, if your biome contains deep cliffs, for instance, in the form of a river gorge, it may be possible to build a staircase down the side of the gorge past the aquifer.

=== The double slit method ===
{{Main|Double-slit method}}
This is one of the most commonly-used methods, due to its convenience and power. It was originally developed by QuantumMenace, and is also mentioned below under [[#The pump method|the pump method]].

=== The hatch trick ===
The hatch trick is a simple method for putting one or two dwarves through a single Heavy aquifer layer. (This is not to be mistaken with only working for a single layer aquifer.) You can use the trick to essentially bypass the problematic final layer of a multi-layer aquifer, allowing access to the rock layers and caverns before you've put a sealed staircase through the aquifer.

First you must dig a pair of up/down stairs into the aquifer (i.e. as in twin slit), while draining one of the tiles with a screw pump, simply build a hatch on the tile (the hatch must be built on a downstairs or up/down stairs for the trick to work). Once the hatch is constructed, with the pump still operating, designate an up/down staircase under the hatch, a miner will dig the staircase out while standing 'on top' of the hatch, he can then pass through the hatch to continue digging, the hatch will let 1-2 water through with him before closing and preventing further water from following the miner. The miner is now safely under the aquifer and can dig down to the caverns or to the map edge and establish a drain, allowing you to use the much faster [[#The drainage method|drainage from below method]] to finish penetrating the aquifer. This can save a lot of time for multiple-layer aquifers where the final layer is sand. It is also quicker and cleaner than cave-in for single layer aquifers if you plan to extend a staircase straight down to the caverns anyway (making the drain essentially free).

===The ore method===
On maps where the aquifer is not held in a layer of soil, but instead is held in a [[sedimentary layer]] such as sandstone, it may be possible to tunnel down through deposits of ore such as [[magnetite]]. For this to work you have to find a spot where there is coincidentally an ore deposit on each Z-level you need to dig through. This is only possible through tiresome trial and error, or through the use of a utility like DFHack's <tt>reveal</tt>. The trial and error method can be accomplished somewhat more easily by digging up/down stairs to reveal the layer underneath them without actually digging into the underlying layer. This method is more complicated with aquifers located in layers of [[conglomerate]], as large clusters of [[puddingstone]] will support the aquifer and thus cannot be used to provide a path through it.

=== The "Chicken Run" technique ===
In versions of the game earlier than {{version|0.40.23}}, this term meant having a reasonably fast/skilled miner dig a set of up/down staircases faster than the water from the aquifer could fall down the stairs and block movement into the mining tile. With luck, a miner could breach the caverns this way, allowing the aquifer water to drain. After the addition of job priorities, this became impossible. Now, when a newly revealed damp tile cancels mining, the miner will revert to "No Job" status and will take a few dozen ticks to resume mining. In that time, the miner will walk away and the site will be flooded, making the tile below unreachable.

A limited but useful variant of this technique still exists. By digging downward staircases in the layer above the aquifer, those tiles can be revealed as damp, and thus will not trigger the mining cancellation. A sufficiently fast miner (Professional or so should do for soil layers, depending on agility) can then dig a stair in one of the tiles, and before that tile floods, channel out an adjacent tile. The channel will breach the layer below, and if that layer is also an aquifer, it will of course act as an infinite drain for water from above. This then opens the possibility of opening space to work in the upper layer.

While not a direct staircase in the original method, establishing a drain with just a pick is also possible with a dabbling miner. One can channel an aquifer tile from up to four ramps dug at the corners of the tile to be channeled, such that the channel priority is higher than the ramp-digging priority. Using this, one can establish drains into the next level of a soil aquifer, as digging progress accumulates in revealed tiles.

If you fail to mine fast enough, or if flowing water pushes your miner down the channeled ramp, the dwarf will usually walk up the stairs to safety, but it is possible that the miner might <s>drown</s> have fun. In stone aquifers, a legendary miner can manage with one attempt at channeling, and at minimum, a proficient miner can manage with four, though in the second case they'll risk drowning and can take weeks to dig the next channel to expand the drain.

=== Exploiting cave-ins ===
Conceptually this method involves removing the aquifer-bearing sand, soil or rock using channeling, and then dropping an island of dry sand, soil or clay into the resulting pond, a staircase can then be dug through the center of the resulting artificial island. This requires at least one natural dry layer, but is more flexible if two or more are available. An advantage of these methods is that they can be carried out by a single miner with no resources other than a pick.

This does not work with [[construction|constructed]] walls since they deconstruct on cave-in.

'''Note:''' There is a bug{{bug|1206}} that can occasionally prevent this method from working. Collapsed layers often turn into the layer type that was dug out at the level where they land (e.g. dry loam becomes dry sand). On occasion, a dry layer collapsed into an aquifer will also transform into actual aquifer tiles (e.g. dry loam becomes water-producing sand). It is unknown what triggers this behavior, but when it occurs it will be impossible to pierce the aquifer using cave-ins.

When unmined tiles collapse into a liquid, the displaced liquid teleports to sit ''on top'' of the collapsed tiles. Thus, when plugging an aquifer, it is usually advisable to incorporate aquifer drain space into the design to dispose of the displaced water.

==== Cave-in example ====
[[File:Aquifer-Plug.png|frame|none|Note: Side View]]

*Dig stairs down to the aquifer. Dig over the aquifer layer but under your "plug". You'll need a 5x5 landmass. (Slide 2)
*Channel out the area the plug will fall into. (Slide 3)
*Leave a single floor tile on top of the plug and dig out the outer layer of your plug. The plug should be a 3x3 landmass now. The single floor tile must keep the plug from falling. (Slide 3)
*Channel out the floor tile holding up the plug. (Slides 4 & 5)
*Construct floor tiles to reach the plug and dig through the middle to get under the aquifer. (Slide 6)

==== Concentric Ring Method for Multiple Layers ====

If you build many rings inside one another in your top drop layer, you can breach multi-level aquifers with as little as 2 natural layers of dry soil above it. Drop the rings from the outside to the inside using constructed arms to hold the center rings in place. Once a ring drops into the water below it, pump out the water in the center and dig down another layer. When that is complete, drop the next ring and continue the process until you are through. Since you start dropping rings from the outside it is necessary to know how many levels deep the aquifer is before you begin. 
Tutorial for more than one Aquifier can be found here: [[User:Rhenaya/HowtoDualAquifer]]

==== "Chicken-Run" plug ====

This method was developed for a single-pick challenge on a hostile biome. In the specific (but common) case of a 2-Z thick soil aquifer, with two dry layers above, it is possible to very quickly penetrate the aquifer using a cave-in without breaching the surface and compromising the fort's security. The method starts with a Chicken Run (see above), after which an area of the upper aquifer level is cleared out with drainage into the lower level. The lower dry level is then collapsed, which means that the sub-surface level only needs to be mined (to release the plug) rather than collapsed as part of the plug.

The procedure is described in detail {{Forum|129994.msg4620421#msg4620421|in this and the following posts}}.

While not yet demonstrated, it should be possible to use successive cycles of chicken-running and clearing to pierce arbitrarily deep soil aquifers this way.

=== The pump method ===
The pumping method uses one or more [[screw pump|pumps]] to keep an area dry long enough to smooth or [[wall]] off the sides, stopping the flow of water. It requires no special environment or resources, other than wood and dwarves (and patience). Most commonly, a modestly-sized section of the aquifer layer is channeled out and several screw pumps are built facing it. Directly behind each of the screw pumps a few tiles are channeled out to receive and dispose of the pumped water. When the pumps are activated, they should pump water faster than the aquifer can produce it, allowing masons to smooth or build walls around your future staircase. You ''will'' get job cancellations during this process, as stray 2/7's of water interrupt the building process. Just unsuspend the construction when this happens, as long a dwarf manages to touch the wall before canceling, it will move incrementally toward completion and eventually finish. Depending on the availability of screw pumps and dwarves, you may need to wall off one corner or side at a time, then move the pumps and repeat. When drilling through more than one aquifer layer, be sure to leave yourself enough room to build additional layers of pumps and water disposal channels on lower levels.

Things to consider:
* The smaller your work area, the less water your dwarves will have to remove and the faster construction will finish. For a single-layer soil aquifer, you only need to mine five tiles (your stairway and walls directly North, South, East, and West of it); single-layer stone aquifers require only a single tile be channeled.
* Mechanical [[power]] may come in handy, but dwarf power works just fine and is much more portable.
* Channels can sometimes be used in place of walls, causing water produced by the aquifer on one level to immediately fall and be consumed by the aquifer on the level below.
* This method may take a while.

==== Specific pump methods in detail ====
QuantumMenace's [[double-slit method]] can pierce an aquifer of any depth using only wood and dwarven labor. Taken from [http://www.bay12forums.com/smf/index.php?topic=79224.15 this forum post].

Earlier in the same thread, Hans Lemurson laid out a very dwarfy method that can also pierce aquifers of any depth, using several pumps and machinery. [http://www.bay12forums.com/smf/index.php?topic=79224.0#msg2058307 Find it here].

A convenient method without job cancellation using a [[pump stack]] was presented by kingubu in [http://www.bay12forums.com/smf/index.php?topic=143064.0 this forum post], see [[Pump-stack_method]]

Leonidas posted a [http://www.bay12forums.com/smf/index.php?topic=169616.0 detailed procedure], copiously illustrated, for tunneling through any aquifer with limited resources and relative safety.

===The freezing method===
If you are playing in a freezing or very cold landscape, where it snows in winter and instantly freezes water on the map, you can dig out a 3x3 hole in the ground using [[channel]]s, and make it deeper and deeper until you reach the aquifer level. Once you reach the damp rock, tunnel into it with up/down staircases, then channel out the downstairs, the exposed water will turn to ice, digging the up/downstairs before channeling allows the tiles to safely fill with 7/7 water before being frozen, this avoids the hazard of miners being encased in ice and avoids a bug(?) where frozen water which is less than 7/7 deep does not produce a floor above it. The central square of the 3x3 hole should be tunnelable ice, so you can get to the rock beneath.

If your fortress is in a zone that gets warm, build walls around the inside of the hole to stop the water coming in once the ice melts. In order to build a wall around a 1x1 staircase it will be necessary to have a 5x5 hole, since you need to leave an outer ring of ice to seal the aquifer.

If the aquifer is multiple layers deep you will need to start with a sufficiently large hole to account for both an ice wall to seal the aquifer and a constructed wall to seal the ice wall for each layer of the aquifer. A pump based method might be preferable.

As an alternative to building a second wall to seal the ice wall, you can establish a drain into the caverns, and build a constructed wall when the melt comes.

===The magma/obsidian method===
If you have access to a supply of magma, you can create your own obsidian caissons. By channeling into the aquifer layer and then filling these channels with magma, or by digging staircases and pouring magma down the staircases, it is possible to create a wall of obsidian between your working area and the [[water]]-bearing rock or [[soil]]. However, changes to world generation with the last version have made this method more difficult than it once was, as it is now harder to find magma vents that extend above the aquifer level.

===The drainage method===
Having made an initial hole in the aquifer, you may wish to punch another larger hole through, say for example to grow wild strawberries in the caverns. Or you may simply want an additional (natural stone!) staircase. Once you have access from below this is much easier than digging from above, and it has the additional benefit of producing a shaft of exactly the size you want.

Locate the caverns and dig a drainage shaft of up/down stairs or downward stairs up from the caverns to the aquifer (downward stairs function as grates and are far safer than channeling). Once the drainage shaft is complete punch the shaft up through the aquifer (using up/down stairs) until you hit dry dirt. Now mine out the walls around the shaft and build constructed walls to seal the aquifer. It's even faster if the walls are dug out using down stairs instead, constructed walls can be built on the stairs and water falls straight through, thus construction can always be started and is never suspended. Always build the walls from the highest layer down, so the dwarves aren't having water dumped on them from above.

This method can be used to create arbitrarily large (and shaped) holes. Large holes, which would be impractical to dig from above, are very easy using this technique. It's also extremely useful for digging straight shafts through "layercake" aquifers where aquifer tiles and non-aquifer tiles are intermixed.

Just be very aware that your framerate is bound to suffer, if you are not fast with plugging the aquifer walls.

===The modding method===
By editing the raws and removing the [AQUIFER] tag from all of the appropriate entries in inorganic_stone_layer.txt, inorganic_stone_mineral.txt, and inorganic_stone_soil.txt it is possible to remove all aquifers from the world. This can be done before creating a new world or after, if you find a particularly neat location ruined only by the presence of an aquifer. In order to modify an existing world, you must delete the [AQUIFER] tag from the raws in the savegame's folder.

==== With PyLNP ====
Disable aquifers in the options tab before generating a new world. This works similarly to the command-line method below, but is usually a lot easier.

==== With DFHack ====
The DFHack command "light-aquifers-only" changes all Heavy aquifers to Light Aquifers.

If you prefer not having to deal with aquifers at all, the DFHack command "drain-aquifer" removes the aquifer flag from all tiles in your current embark without requiring raw edits.

If you have DFHack, this is the best method.

===== With DFHack's tiletypes command =====
DFHack's [https://github.com/DFHack/dfhack/blob/master/Readme.rst#tiletypes "tiletypes"] command lets you remove the aquifer flag from specific tiles only. This is useful if you want to keep a Heavy aquifer on your map, but don't want to deal with the hassle of breaching it.

To create 4x4 aquiferless shaft, do this:
1) Type "tiletypes" in DFHack to open the tiletypes tool
2) Type in the following commands to set the tool's filter, paint and brush settings accordingly:
- filter any
- paint aqua 0
- range 4 4
3) In Dwarf Fortress, press 'k' to bring up the cursor, and move the cursor to the position you want the top left tile of your shaft to be.
4) In DFHack, type "run". The aquifer will be removed in a 4x4 square below and to the right of your cursor.
5) Repeat steps 3 and 4 for every aquifer layer you have. Don't worry about hitting non-aquifer tiles, they shouldn't be affected by the tool at all.

Alternatively, in step two you can provide a third number for the range. This number will represent how many Z levels deep to remove aquifers.

If you don't know how deep your aquifer is, either use the "reveal" command in DFHack to check, or just set the tiletypes range to encompass multiple z-levels. For instance, use "range 4 4 20" and use "tiletypes-here" on a tile 20 layers below the surface of your shaft.

==== Command-line (Linux/OS X) ====
Note that this prevents Light aquifers as well as Heavy ones!

cd df_linux/raw/objects/
sed -i 's/\[AQUIFER\]/(AQUIFER)/g' inorganic_stone_*.txt

and generate world. To edit an already generated world, run the <code>sed</code> command in the <tt>df_linux/data/save/''regionNN''/raw/objects</tt> folder instead.

OS X requires an argument to the <code>-i</code> flag, which is used as an extension to create backup files (but it can be empty):

<pre>sed -i '' 's/\[AQUIFER\]/(AQUIFER)/g' inorganic_stone_*.txt</pre>

If you want to restore the tags later, you can do it with the command:

sed -i 's/(AQUIFER)/[AQUIFER]/g' inorganic_stone_*.txt

==== Text editor (All operating systems) ====
You can manually perform the Command-line method above.

There are three files. They can be found in two different places.

For every new world you make:
“THE FOLDER DF IS INSTALLED IN”/raw/objects

For worlds that have already been made:
“THE FOLDER DF IS INSTALLED IN”/data/save/“THE WORLD YOU ARE EDITING”/raw/objects

The three files you are editing are:
inorganic_stone_layer.txt
inorganic_stone_mineral.txt
inorganic_stone_soil.txt

Open these in a text editior.
Open the “Find and Replace” function of your text editor.

Replace all instances of
[AQUIFER]
with
(AQUIFER)

Later on, if you would like to reverse the process, replace (AQUIFER) with [AQUIFER].

== Benefits of aquifers ==
Aquifers can be useful for building a self-sufficient fortress, and are often indispensable for water-related [[megaprojects]] in maps without a river.

Aquifers outside [[ocean]] biomes also contain fresh water. Since aquifers are almost always located close to the surface, freshwater aquifers can easily be turned into a source of infinite, secure, non-freezing drinking water for your dwarves, eliminating the need for a [[Reservoir|cistern]]. While both of these roles can also be filled by [[Caverns|cavern]] features, an aquifer allows you to get the same advantages without exposing yourself to potentially ~~dangerous~~ Fun cavern creatures.

=== A benefit of Heavy Aquifers? ===
Although annoying, Heavy aquifers can absorb an infinite amount of water, meaning they can function as a drain for anything above them. For instance, digging a pit in a lower Z level of the aquifer, then connecting it to a breached aquifer a level above through a channel dug a level above ''that'' will create a permanently flowing, compact, secure water/power source completely contained within the fortress.

== Technical implementation of the aquifer version split ==

The aquifer split introduced in 0.47.01 uses the crude but effective random appearing method of making all aquifers light unless the Drainage modulo 20 equals 7.

== Bugs ==
Some light aquifers may not appear on the embark screen.{{bug|11358}}

== External links ==

* [http://www.bay12forums.com/smf/index.php?topic=79224.15 QuantumMenace's two-slit method] for breaching aquifers of any depth - Illustrated guide
* [http://www.bay12forums.com/smf/index.php?topic=141600 Hatch trick] described with ascii art.
{{World}}

Aquifer

2020-06-27T13:35:36Z

Albedo: good job, L - 1 more for ya

{{Quality|Masterwork|15:04, 18 May 2015 (UTC)}}
{{av}}
[[File:aqua_varied.png|thumb|right|158px|Area with a varied aquifer.]]An '''aquifer''' is a subterranean layer of [[water|groundwater]]-bearing rock or [[soil]]. As of {{version|0.47.01}}, there are two types of aquifers: {{DFtext|Light aquifer|1:1}} and {{DFtext|Heavy aquifer|1:1}}, with Light aquifers being by far the most common. Prior to this, all aquifers behaved as the "Heavy" type.

Aquifers are tiles which produce water in their ''neighboring'' tiles -- north, south, east, west, and below. They do not produce water in the tile above them, nor in any diagonally-adjacent tiles.

Aquifers cannot be drained; the groundwater is limitless, with even a single isolated tile leaking water forever. However, [[smoothing|smoothed]], mined, carved staircase, or channeled aquifer tiles no longer produce water.

Aquifers located in [[ocean]] [[biome]]s will produce salty water; aquifers in other biomes will produce freshwater. The frequency of aquifers differs between embark locations.

If you are digging an up/down staircase in the downward direction and you hit an aquifer, the aquifer tile will be revealed as damp soil or stone and the digging job will be un-designated for that tile. If you are mining horizontally, you will similarly be warned of a "damp stone" before breaching the aquifer. If you are digging an up/down staircase in the ''upward'' direction, or a ramp, and you hit an aquifer from below, the aquifer tile will immediately start producing water in the stairwell. In the case of Heavy aquifers, this can lead to a lot of [[Fun]].

== Light Aquifers ==
Light Aquifers are by far the most common (being ~19 out of every 20 aquifers), and produce water at a greatly diminished rate. As a result, they can easily be penetrated with minimal effort by digging out one level at a time and walling it off reasonably quickly. Light aquifers can be very useful for low-water applications such as slowly filling a cistern for wells, or feeding an atomspheric waterfall.

An open tile will receive light-aquifer water if it's directly north, south, east, west, or below a light aquifer tile. There's no diagonal transmission.

The amount of water that the open tile receives is random. On average, an open tile will receive four units of light-aquifer water per month. But that number can go as low as two or as high as six.

If an open tile is adjacent to a single light-aquifer tile, then it receives just as much water as an open tile surrounded by light-aquifer tiles. One is all you need.

Water at level 1/7 does not evaporate on a floor of what had been a light aquifer tile.

Unlike heavy aquifers, light aquifers tiles do not drain away water.

== Heavy Aquifers ==
Unlike Light Aquifers, Heavy aquifers produce water almost immediately, effectively halting excavation at or below the aquifer level. This, in conjunction with the fact that they are often located in areas rich in [[loam]] and [[sand]], makes it difficult to find great quantities of [[stone]] in areas with heavy aquifers, making for more challenging gameplay.

Unmined heavy aquifer tiles also act as an infinite ''sink'' for water, just like an open map edge. A single aquifer tile can absorb any amount of [[pressure|pressurized]] water each tick, limited only by the supply. One less obvious consequence is that if an opening is made through a multi-layer aquifer, only the lowest opened layer will ever fill with water.

Empirically, Heavy aquifers gain approximately 1/7 water every 14 ticks, though production has been observed to vary from 2-28 ticks. This rate does not appear to change significantly based on the number of adjacent aquifer tiles.

== Varied Aquifers ==
In addition to the {{DFtext|Heavy|1:1}} and {{DFtext|Light|1:1}} types of aquifer, DF can also display {{DFtext|Varied aquifer|1:1}} on the pre embark screen, which means there are some tiles with light and some tiles with heavy aquifers in the embark rectangle (also note that the biomes of neighboring tiles can "spill over" into a tile, resulting in different, unannounced, aquifers in those parts).

== Where they are found ==

Aquifers appear based on the elevation of the terrain. Low elevations - particularly those near rivers and oceans - are more prone to having an aquifer present, while locations closer to mountains are much less likely, but still possible.

Layers which '''can''' contain aquifers:
*[[sandy clay loam]]
*[[silty clay loam]]
*[[loam]]
*[[sandy loam]]
*[[silt loam]]
*[[loamy sand]]
*[[silt]]
*[[sand (tan)|sand]]
*[[yellow sand]]
*[[white sand]]
*[[black sand]]
*[[red sand]]
*[[peat]]
*[[pelagic clay]]
*[[calcareous ooze]]
*[[siliceous ooze]]
*[[sandstone]]
*[[conglomerate]]
*[[puddingstone]]



Layers which '''cannot''' contain aquifers, despite their names suggesting otherwise:
*[[clay]]
*[[silty clay]]
*[[sandy clay]]
*[[clay loam]]
*[[siltstone]]
*[[mudstone]]

== Working in aquifers ==
When working in aquifers, some points to keep in mind include:

*Water on the tile where a worker is standing will cause job cancellations if it gets too high. A construction job (e.g. wall building) will be suspended by 2/7 depth, but a mining job will only be stopped by 4/7 depth of water.
* Flowing water will cause parents to drop their infants, leading to job cancellations and occasionally [[fun]].
* Aquifers do not create water in diagonal tiles, but do create water in open tiles directly below them. Therefore, you will want to dig two z-levels below the lowest aquifer layer before continuing with your fortress.

=== Probing an aquifer ===

You can discover what layer lies below an aquifer layer by digging up/down stairs into the aquifer. This will reveal the tile below the aquifer layer, and if this is non-aquifer (for example, clay, ore or bedrock) then you know the aquifer is only 1z deep at that location. This method can only be used to determine whether the aquifer is 1 layer deep, or multiple layers deep, but this is still enough information to help plan how to penetrate it. Using a pump-based method is highly recommended for multiple layer Heavy aquifers.

== Dealing with Heavy Aquifers ==
===Going around===
If your embark site is covered by multiple biomes, there is a chance the Heavy aquifer is not present in every biome. In some maps this may be indicated by an outcropping of stone in a landscape otherwise composed of soil; in other maps the change in biome might be visible as a change in soil type, vegetation type or density. You might be able to dig down through a biome that doesn't have a heavy aquifer, to a Z-level below the heavy aquifer, and then (if you wish) tunnel beneath the heavy aquifer to the previously -inaccessible region.

Even if all the biomes of your site contain aquifers, they might not all be at the same Z-level, so you still might be able to dig down in one biome, reaching a Z-level beneath the aquifer in another biome.

Additionally, if your biome contains deep cliffs, for instance, in the form of a river gorge, it may be possible to build a staircase down the side of the gorge past the aquifer.

=== The double slit method ===
{{Main|Double-slit method}}
This is one of the most commonly-used methods, due to its convenience and power. It was originally developed by QuantumMenace, and is also mentioned below under [[#The pump method|the pump method]].

=== The hatch trick ===
The hatch trick is a simple method for putting one or two dwarves through a single Heavy aquifer layer. (This is not to be mistaken with only working for a single layer aquifer.) You can use the trick to essentially bypass the problematic final layer of a multi-layer aquifer, allowing access to the rock layers and caverns before you've put a sealed staircase through the aquifer.

First you must dig a pair of up/down stairs into the aquifer (i.e. as in twin slit), while draining one of the tiles with a screw pump, simply build a hatch on the tile (the hatch must be built on a downstairs or up/down stairs for the trick to work). Once the hatch is constructed, with the pump still operating, designate an up/down staircase under the hatch, a miner will dig the staircase out while standing 'on top' of the hatch, he can then pass through the hatch to continue digging, the hatch will let 1-2 water through with him before closing and preventing further water from following the miner. The miner is now safely under the aquifer and can dig down to the caverns or to the map edge and establish a drain, allowing you to use the much faster [[#The drainage method|drainage from below method]] to finish penetrating the aquifer. This can save a lot of time for multiple-layer aquifers where the final layer is sand. It is also quicker and cleaner than cave-in for single layer aquifers if you plan to extend a staircase straight down to the caverns anyway (making the drain essentially free).

===The ore method===
On maps where the aquifer is not held in a layer of soil, but instead is held in a [[sedimentary layer]] such as sandstone, it may be possible to tunnel down through deposits of ore such as [[magnetite]]. For this to work you have to find a spot where there is coincidentally an ore deposit on each Z-level you need to dig through. This is only possible through tiresome trial and error, or through the use of a utility like DFHack's <tt>reveal</tt>. The trial and error method can be accomplished somewhat more easily by digging up/down stairs to reveal the layer underneath them without actually digging into the underlying layer. This method is more complicated with aquifers located in layers of [[conglomerate]], as large clusters of [[puddingstone]] will support the aquifer and thus cannot be used to provide a path through it.

=== The "Chicken Run" technique ===
In versions of the game earlier than {{version|0.40.23}}, this term meant having a reasonably fast/skilled miner dig a set of up/down staircases faster than the water from the aquifer could fall down the stairs and block movement into the mining tile. With luck, a miner could breach the caverns this way, allowing the aquifer water to drain. After the addition of job priorities, this became impossible. Now, when a newly revealed damp tile cancels mining, the miner will revert to "No Job" status and will take a few dozen ticks to resume mining. In that time, the miner will walk away and the site will be flooded, making the tile below unreachable.

A limited but useful variant of this technique still exists. By digging downward staircases in the layer above the aquifer, those tiles can be revealed as damp, and thus will not trigger the mining cancellation. A sufficiently fast miner (Professional or so should do for soil layers, depending on agility) can then dig a stair in one of the tiles, and before that tile floods, channel out an adjacent tile. The channel will breach the layer below, and if that layer is also an aquifer, it will of course act as an infinite drain for water from above. This then opens the possibility of opening space to work in the upper layer.

While not a direct staircase in the original method, establishing a drain with just a pick is also possible with a dabbling miner. One can channel an aquifer tile from up to four ramps dug at the corners of the tile to be channeled, such that the channel priority is higher than the ramp-digging priority. Using this, one can establish drains into the next level of a soil aquifer, as digging progress accumulates in revealed tiles.

If you fail to mine fast enough, or if flowing water pushes your miner down the channeled ramp, the dwarf will usually walk up the stairs to safety, but it is possible that the miner might <s>drown</s> have fun. In stone aquifers, a legendary miner can manage with one attempt at channeling, and at minimum, a proficient miner can manage with four, though in the second case they'll risk drowning and can take weeks to dig the next channel to expand the drain.

=== Exploiting cave-ins ===
Conceptually this method involves removing the aquifer-bearing sand, soil or rock using channeling, and then dropping an island of dry sand, soil or clay into the resulting pond, a staircase can then be dug through the center of the resulting artificial island. This requires at least one natural dry layer, but is more flexible if two or more are available. An advantage of these methods is that they can be carried out by a single miner with no resources other than a pick.

This does not work with [[construction|constructed]] walls since they deconstruct on cave-in.

'''Note:''' There is a bug{{bug|1206}} that can occasionally prevent this method from working. Collapsed layers often turn into the layer type that was dug out at the level where they land (e.g. dry loam becomes dry sand). On occasion, a dry layer collapsed into an aquifer will also transform into actual aquifer tiles (e.g. dry loam becomes water-producing sand). It is unknown what triggers this behavior, but when it occurs it will be impossible to pierce the aquifer using cave-ins.

When unmined tiles collapse into a liquid, the displaced liquid teleports to sit ''on top'' of the collapsed tiles. Thus, when plugging an aquifer, it is usually advisable to incorporate aquifer drain space into the design to dispose of the displaced water.

==== Cave-in example ====
[[File:Aquifer-Plug.png|frame|none|Note: Side View]]

*Dig stairs down to the aquifer. Dig over the aquifer layer but under your "plug". You'll need a 5x5 landmass. (Slide 2)
*Channel out the area the plug will fall into. (Slide 3)
*Leave a single floor tile on top of the plug and dig out the outer layer of your plug. The plug should be a 3x3 landmass now. The single floor tile must keep the plug from falling. (Slide 3)
*Channel out the floor tile holding up the plug. (Slides 4 & 5)
*Construct floor tiles to reach the plug and dig through the middle to get under the aquifer. (Slide 6)

==== Concentric Ring Method for Multiple Layers ====

If you build many rings inside one another in your top drop layer, you can breach multi-level aquifers with as little as 2 natural layers of dry soil above it. Drop the rings from the outside to the inside using constructed arms to hold the center rings in place. Once a ring drops into the water below it, pump out the water in the center and dig down another layer. When that is complete, drop the next ring and continue the process until you are through. Since you start dropping rings from the outside it is necessary to know how many levels deep the aquifer is before you begin. 
Tutorial for more than one Aquifier can be found here: [[User:Rhenaya/HowtoDualAquifer]]

==== "Chicken-Run" plug ====

This method was developed for a single-pick challenge on a hostile biome. In the specific (but common) case of a 2-Z thick soil aquifer, with two dry layers above, it is possible to very quickly penetrate the aquifer using a cave-in without breaching the surface and compromising the fort's security. The method starts with a Chicken Run (see above), after which an area of the upper aquifer level is cleared out with drainage into the lower level. The lower dry level is then collapsed, which means that the sub-surface level only needs to be mined (to release the plug) rather than collapsed as part of the plug.

The procedure is described in detail {{Forum|129994.msg4620421#msg4620421|in this and the following posts}}.

While not yet demonstrated, it should be possible to use successive cycles of chicken-running and clearing to pierce arbitrarily deep soil aquifers this way.

=== The pump method ===
The pumping method uses one or more [[screw pump|pumps]] to keep an area dry long enough to smooth or [[wall]] off the sides, stopping the flow of water. It requires no special environment or resources, other than wood and dwarves (and patience). Most commonly, a modestly-sized section of the aquifer layer is channeled out and several screw pumps are built facing it. Directly behind each of the screw pumps a few tiles are channeled out to receive and dispose of the pumped water. When the pumps are activated, they should pump water faster than the aquifer can produce it, allowing masons to smooth or build walls around your future staircase. You ''will'' get job cancellations during this process, as stray 2/7's of water interrupt the building process. Just unsuspend the construction when this happens, as long a dwarf manages to touch the wall before canceling, it will move incrementally toward completion and eventually finish. Depending on the availability of screw pumps and dwarves, you may need to wall off one corner or side at a time, then move the pumps and repeat. When drilling through more than one aquifer layer, be sure to leave yourself enough room to build additional layers of pumps and water disposal channels on lower levels.

Things to consider:
* The smaller your work area, the less water your dwarves will have to remove and the faster construction will finish. For a single-layer soil aquifer, you only need to mine five tiles (your stairway and walls directly North, South, East, and West of it); single-layer stone aquifers require only a single tile be channeled.
* Mechanical [[power]] may come in handy, but dwarf power works just fine and is much more portable.
* Channels can sometimes be used in place of walls, causing water produced by the aquifer on one level to immediately fall and be consumed by the aquifer on the level below.
* This method may take a while.

==== Specific pump methods in detail ====
QuantumMenace's [[double-slit method]] can pierce an aquifer of any depth using only wood and dwarven labor. Taken from [http://www.bay12forums.com/smf/index.php?topic=79224.15 this forum post].

Earlier in the same thread, Hans Lemurson laid out a very dwarfy method that can also pierce aquifers of any depth, using several pumps and machinery. [http://www.bay12forums.com/smf/index.php?topic=79224.0#msg2058307 Find it here].

A convenient method without job cancellation using a [[pump stack]] was presented by kingubu in [http://www.bay12forums.com/smf/index.php?topic=143064.0 this forum post], see [[Pump-stack_method]]

Leonidas posted a [http://www.bay12forums.com/smf/index.php?topic=169616.0 detailed procedure], copiously illustrated, for tunneling through any aquifer with limited resources and relative safety.

===The freezing method===
If you are playing in a freezing or very cold landscape, where it snows in winter and instantly freezes water on the map, you can dig out a 3x3 hole in the ground using [[channel]]s, and make it deeper and deeper until you reach the aquifer level. Once you reach the damp rock, tunnel into it with up/down staircases, then channel out the downstairs, the exposed water will turn to ice, digging the up/downstairs before channeling allows the tiles to safely fill with 7/7 water before being frozen, this avoids the hazard of miners being encased in ice and avoids a bug(?) where frozen water which is less than 7/7 deep does not produce a floor above it. The central square of the 3x3 hole should be tunnelable ice, so you can get to the rock beneath.

If your fortress is in a zone that gets warm, build walls around the inside of the hole to stop the water coming in once the ice melts. In order to build a wall around a 1x1 staircase it will be necessary to have a 5x5 hole, since you need to leave an outer ring of ice to seal the aquifer.

If the aquifer is multiple layers deep you will need to start with a sufficiently large hole to account for both an ice wall to seal the aquifer and a constructed wall to seal the ice wall for each layer of the aquifer. A pump based method might be preferable.

As an alternative to building a second wall to seal the ice wall, you can establish a drain into the caverns, and build a constructed wall when the melt comes.

===The magma/obsidian method===
If you have access to a supply of magma, you can create your own obsidian caissons. By channeling into the aquifer layer and then filling these channels with magma, or by digging staircases and pouring magma down the staircases, it is possible to create a wall of obsidian between your working area and the [[water]]-bearing rock or [[soil]]. However, changes to world generation with the last version have made this method more difficult than it once was, as it is now harder to find magma vents that extend above the aquifer level.

===The drainage method===
Having made an initial hole in the aquifer, you may wish to punch another larger hole through, say for example to grow wild strawberries in the caverns. Or you may simply want an additional (natural stone!) staircase. Once you have access from below this is much easier than digging from above, and it has the additional benefit of producing a shaft of exactly the size you want.

Locate the caverns and dig a drainage shaft of up/down stairs or downward stairs up from the caverns to the aquifer (downward stairs function as grates and are far safer than channeling). Once the drainage shaft is complete punch the shaft up through the aquifer (using up/down stairs) until you hit dry dirt. Now mine out the walls around the shaft and build constructed walls to seal the aquifer. It's even faster if the walls are dug out using down stairs instead, constructed walls can be built on the stairs and water falls straight through, thus construction can always be started and is never suspended. Always build the walls from the highest layer down, so the dwarves aren't having water dumped on them from above.

This method can be used to create arbitrarily large (and shaped) holes. Large holes, which would be impractical to dig from above, are very easy using this technique. It's also extremely useful for digging straight shafts through "layercake" aquifers where aquifer tiles and non-aquifer tiles are intermixed.

Just be very aware that your framerate is bound to suffer, if you are not fast with plugging the aquifer walls.

===The modding method===
By editing the raws and removing the [AQUIFER] tag from all of the appropriate entries in inorganic_stone_layer.txt, inorganic_stone_mineral.txt, and inorganic_stone_soil.txt it is possible to remove all aquifers from the world. This can be done before creating a new world or after, if you find a particularly neat location ruined only by the presence of an aquifer. In order to modify an existing world, you must delete the [AQUIFER] tag from the raws in the savegame's folder.

==== With PyLNP ====
Disable aquifers in the options tab before generating a new world. This works similarly to the command-line method below, but is usually a lot easier.

==== With DFHack ====
The DFHack command "light-aquifers-only" changes all Heavy aquifers to Light Aquifers.

If you prefer not having to deal with aquifers at all, the DFHack command "drain-aquifer" removes the aquifer flag from all tiles in your current embark without requiring raw edits.

If you have DFHack, this is the best method.

===== With DFHack's tiletypes command =====
DFHack's [https://github.com/DFHack/dfhack/blob/master/Readme.rst#tiletypes "tiletypes"] command lets you remove the aquifer flag from specific tiles only. This is useful if you want to keep a Heavy aquifer on your map, but don't want to deal with the hassle of breaching it.

To create 4x4 aquiferless shaft, do this:
1) Type "tiletypes" in DFHack to open the tiletypes tool
2) Type in the following commands to set the tool's filter, paint and brush settings accordingly:
- filter any
- paint aqua 0
- range 4 4
3) In Dwarf Fortress, press 'k' to bring up the cursor, and move the cursor to the position you want the top left tile of your shaft to be.
4) In DFHack, type "run". The aquifer will be removed in a 4x4 square below and to the right of your cursor.
5) Repeat steps 3 and 4 for every aquifer layer you have. Don't worry about hitting non-aquifer tiles, they shouldn't be affected by the tool at all.

Alternatively, in step two you can provide a third number for the range. This number will represent how many Z levels deep to remove aquifers.

If you don't know how deep your aquifer is, either use the "reveal" command in DFHack to check, or just set the tiletypes range to encompass multiple z-levels. For instance, use "range 4 4 20" and use "tiletypes-here" on a tile 20 layers below the surface of your shaft.

==== Command-line (Linux/OS X) ====
Note that this prevents Light aquifers as well as Heavy ones!

cd df_linux/raw/objects/
sed -i 's/\[AQUIFER\]/(AQUIFER)/g' inorganic_stone_*.txt

and generate world. To edit an already generated world, run the <code>sed</code> command in the <tt>df_linux/data/save/''regionNN''/raw/objects</tt> folder instead.

OS X requires an argument to the <code>-i</code> flag, which is used as an extension to create backup files (but it can be empty):

<pre>sed -i '' 's/\[AQUIFER\]/(AQUIFER)/g' inorganic_stone_*.txt</pre>

If you want to restore the tags later, you can do it with the command:

sed -i 's/(AQUIFER)/[AQUIFER]/g' inorganic_stone_*.txt

==== Text editor (All operating systems) ====
You can manually perform the Command-line method above.

There are three files. They can be found in two different places.

For every new world you make:
“THE FOLDER DF IS INSTALLED IN”/raw/objects

For worlds that have already been made:
“THE FOLDER DF IS INSTALLED IN”/data/save/“THE WORLD YOU ARE EDITING”/raw/objects

The three files you are editing are:
inorganic_stone_layer.txt
inorganic_stone_mineral.txt
inorganic_stone_soil.txt

Open these in a text editior.
Open the “Find and Replace” function of your text editor.

Replace all instances of
[AQUIFER]
with
(AQUIFER)

Later on, if you would like to reverse the process, replace (AQUIFER) with [AQUIFER].

== Benefits of aquifers ==
Aquifers can be useful for building a self-sufficient fortress, and are often indispensable for water-related [[megaprojects]] in maps without a river.

Aquifers outside [[ocean]] biomes also contain fresh water. Since aquifers are almost always located close to the surface, freshwater aquifers can easily be turned into a source of infinite, secure, non-freezing drinking water for your dwarves, eliminating the need for a [[Reservoir|cistern]]. While both of these roles can also be filled by [[Caverns|cavern]] features, an aquifer allows you to get the same advantages without exposing yourself to potentially ~~dangerous~~ Fun cavern creatures.

=== A benefit of Heavy Aquifers? ===
Although annoying, Heavy aquifers can absorb an infinite amount of water, meaning they can function as a drain for anything above them. For instance, digging a pit in a lower Z level of the aquifer, then connecting it to a breached aquifer a level above through a channel dug a level above ''that'' will create a permanently flowing, compact, secure water/power source completely contained within the fortress.

== Technical implementation of the aquifer version split ==

The aquifer split introduced in 0.47.01 uses the crude but effective random appearing method of making all aquifers light unless the Drainage modulo 20 equals 7.

== Bugs ==
Some light aquifers may not appear on the embark screen.{{bug|11358}}

== External links ==

* [http://www.bay12forums.com/smf/index.php?topic=79224.15 QuantumMenace's two-slit method] for breaching aquifers of any depth - Illustrated guide
* [http://www.bay12forums.com/smf/index.php?topic=141600 Hatch trick] described with ascii art.
{{World}}

DF2014 Talk:Immigration

2020-06-27T13:29:45Z

Albedo: /* Necromancers */ you tell me...

== Hard-coded Waves ==

Note that the first two waves are "hard-coded" to appear regardless of fortress wealth, danger, or civilization extinction. Those waves *are* subject to the population caps (and were previously, though with the "liaison information enables the cap feature" it was nearly impossible to enable the cap before the first two waves arrived without setting it directly with DFHack). Now that the population caps take immediate effect it is much easier to block the first two waves, but they still ignore the in-game variables that all other waves use.

== Early Immigration ==

In my new fortress, the first thing I created was a trade depot. Just after finishing the depot, merchants have arrived. Just after the message that they would be leaving soon, the first immigrant wave appeared! Like, two weeks after embarking, 10 dwarves! Although I find it quite a blessing as I'm usually struggling with the low work force of the first seven, I'm not sure if this could be expected behavior. Not a single dwarf, merchant, caravan, etc. has left the map. How could they possibly know? Maybe we should add a paragraph explicitly explaining the danger of early immigration or something, just in case people didn't bring enough food for potentially 17 dwarves. But, is this expected behavior or even an unknown bug? Oh, and to the usefulness of the first waves: it was a legendary shearer, two high master potters and two bone doctors, among other useful skills --[[User:Janni|Janni]] ([[User talk:Janni|talk]]) 10:02, 3 January 2015 (UTC)

== Minimum Migrants for Second Wave? ==

I just had my second wave of migrants, and got the "The fortress attracted no migrants this season." message. Perhaps the claim that the minimum size for the first two waves is 1 is not true?

This is the 2nd fortress in the world. The first one told me that the civilization was extinct, and I'd likely get high-ranked officials. This was true. I had the King and wasted a lot of resources trying to get fancy enough rooms for the guy... until the fortress fell after a crippling werelizard infection followed by a huge swarm of undead. This fortress gave me on such message, but the first dwarven caravan is still here, without a liason.– [[template:unsigned|unsigned]] comment by [[User:Shane|Shane]]

:Did you have a population cap set at or below your current number of dwarves? Or no strict population cap at all? (A bug set the strict population cap to "0" if it wasn't defined in the init file.) Even the "hard coded" migrant waves are affected by the population caps.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 21:22, 1 March 2015 (UTC)

To chime in, I also had "No migrants this season." for the second wave. I only had 3 dwarves arrive the first wave, and chose a dwarf civilization with very few members. My pop cap is set to 30. There was a seize going on during the second year, so maybe the second wave was blocked, though. --[[Special:Contributions/1.175.1.165|1.175.1.165]] 10:54, 26 March 2017 (UTC)

== Migrants even though parent civ dead ==

I embarked on an island and resurrected a dead dwarven civ. One of my dwarves immediately became the king. After the first two migrant waves, I have noticed that more migrants keep arriving, even though the dwarves were wiped out. Is this a bug, or a new feature?
[[Special:Contributions/96.241.60.219|96.241.60.219]] 03:21, 28 February 2015 (UTC)

:Neither? Your civilization was not, in fact, dead. Even without an active site your civilization can live on (think "refugees") for some time. In this quasi-dead state, migrants will be generated "from thin air" to fill your fortress. A truly-dead civilization will produce no migrants beyond the first two hard-coded waves. Unfortunately, determining whether a civilization is quasi-dead or truly-dead isn't straightforward.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 21:22, 1 March 2015 (UTC)

== No Migration ==

I've run three games now in version 0.40.05, each one lasting 2 to 3 years and in all of them I received no immigrants at all. The first one was on an island, so I thought that was it but the next two were not. In one of them my outpost liaison was a goblin so I thought maybe the civilization was extinct, but even if that had been the case I thought I should have gotten the two hard-coded migration waves. The third one had nothing suspicious about it at all.

The only thing I can think of is that I set my population cap to 100 and maybe there's a bug that causes that setting to prevent any immigration at all, but I've checked and there does not appear to be any such bug listed. Does anyone know what I might be doing wrong, or is this an undocumented bug? [[Special:Contributions/64.180.242.196|64.180.242.196]] 14:01, 1 May 2015 (UTC)

:Version 0.40 added a strict population cap, and changed how the caps work. In early releases of the v0.40 branch there were reports that mods were removing the strict population cap from the init file, causing the game to default to "0" (which prevents immigration). If you have both population caps set correctly then you might have more luck asking on the [http://www.bay12forums.com/smf/index.php?board=7.0 gameplay questions forum].--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 18:00, 1 May 2015 (UTC)

::I thought I was on v0.40.24, but it looks like I'm on v0.40.05. The other thing I've checked is whether there's any migrants hanging out on the edges not able to find my fort as I don't have a meeting hall, just a meeting area. I've double checked the pop cap in the d_init file, but I didn't see one in the init file. You mention "both population caps" but I only see one. I'm using the Mayday graphics set, so maybe that's the issue. The pop cap I see is: [POPULATION_CAP:100] in the d_init file. I'll look for what the second setting should be. Thanks. [[Special:Contributions/64.180.242.196|64.180.242.196]] 20:53, 1 May 2015 (UTC)

::Yup, that did it. I added [STRICT_POPULATION_CAP:150] and suddenly there were 8 dwarves that wanted in (despite the fact that 6 of the starting 7 were slaughtered in an ambush - FUN!!! - even the traders were running away in horror).

== Size of first two waves ==
The article says "The first two migrant waves have a minimum size of 1, if it has a relative in your group already, and a maximum size of 10." To the contrary, the first wave I got had 11 migrants, and the second had 12. Anyone know what could have caused this, or if the article is simply wrong? [[Special:Contributions/2001:4830:2446:EE:A46B:F8CE:C01F:6FBF|2001:4830:2446:EE:A46B:F8CE:C01F:6FBF]] 20:21, 23 January 2016 (UTC)

:Well, the first two waves you received may not have been the first two attempted waves (which could have been blocked by a siege or a population cap setting). It's also quite possible that the article is outdated, or that information was simply incorrect when it was added back in [http://dwarffortresswiki.org/index.php?title=v0.31:Immigration&oldid=150267 2011]. If you're reasonably confident those were your first two attempted waves, feel free to fix the article.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 23:29, 23 January 2016 (UTC)

== Necromancers ==

Do these need their own section?
--[[User:GarrieIrons|Gar]][[User Talk:GarrieIrons|rie]] 10:24, 27 June 2020 (UTC)
: [[Dwarf Fortress Wiki:Community Portal#B|Rule B]] is "Be Bold", so you tell me - do we (and by "we" I mean "you", at least to start) have enough information on "Necromancer immigrants" to, specifically, support adding their own sub-section? (I know I don't. :/ ) But if you do, or think you have enough to just start it, do it! [[User:Albedo|Albedo]] ([[User talk:Albedo|talk]]) 13:29, 27 June 2020 (UTC)

DF2014:Symptoms

2020-06-27T13:19:08Z

Albedo: /* Blisters */

{{wrong namespace|Symptom}}

{{av}}{{Quality|Exceptional}}
A '''symptom''' is a status effect most often caused by contracting a [[syndrome]]. They range from mild temporary annoyances to lifelong disabilities to even death if untreated. An affected dwarf will need to be diagnosed at a [[Hospital]] before a treatment can be prescribed.

==Blisters==
'''Effects''': Areas affected become prone to infection, this becomes more and more likely as severity goes up. While usually harmless in itself*, a resulting infection might cause a loss of life or limb if not properly dealt with.
: (* unless in the lungs, in which case the unlucky dwarf may be unable to breathe if the effect or a subsequent infection is severe.)

==Bleeding==
'''Effects''': Areas affected will continue to bleed for the duration of the effect and will not taper off like a normal wound. In effect it suggests that whatever caused the wound had an anti-coagulant in the venom. This will quickly cause an affected creature to bleed out if the syndrome is not immediately treated.

==Bruising==
'''Effects''': Causes pain long after the blunt trauma that caused it is over. Even the most severe bruises will heal without intervention, but may hint at fractures under the skin.

==Cough==
'''Effects''': Dwarf will stop and cough occasionally. While nearly harmless by itself severe coughs will sometimes bring up blood. In this case it's a sign of internal hemorrhaging.

==Dizziness==
'''Effects''': Creature might stumble/fall in a random direction when attempting to perform an action (including moving [!!!]). The more severe the dizziness the more likely this is to happen. Beware that stumbling, much like dodging, might end up putting a dwarf in a moat, or chasm, or magma, or off a wall, or falling just enough to land unconscious for a second on a cage trap. The list goes on.

==Drowsiness==
'''Effects''': Creature tires faster than normal and requires more sleep. This can be almost unnoticeable if the severity is low, but results in narcoleptic fits if high.

==Fever==
'''Effects''': Appears to reduce the ability to focus. Intense fevers can also cause stunning. While a fever in itself seems relatively harmless, it's often just the most visible symptom. Feverish dwarfs blink with a red "X".

==Impaired Function==
'''Effects''': Creature will be unable to use affected body parts for the duration. Much of the functionality here is mirrored in swelling, but this allows certain parts (such as organs) that normally can't swell to still cease functioning

==Nausea==
'''Effects''': Creature will stop and [[Vomit]]. How often this happens depends on severity. Sustained and intense vomiting will cause dwarfs to dehydrate.

==Necrosis==
'''Effects''': The affected tissue starts to rot away, which needless to say is a medical emergency. If action isn't quickly taken to remove the tissue (through either surgery or amputation) it will spread throughout the body and may cause [[Health_care#Infection|infection]], killing the creature. Also commonly seen in [[Undead]] creatures.

==Numbness==
'''Effects''': Creature will not be able to feel affected body parts. This makes pain a non-issue, but also hampers their use (I.E. Something with numb hands will find using weapons difficult, something who has a leg that's fallen asleep with have difficulty standing). Prolonged numbness will lead to permanent sensory nerve damage.

==Oozing==
'''Effects''': A sign of infection. Infected areas heal much slower and might kill if especially severe or widespread.

==Pain==
'''Effects''': Creatures that aren't in a martial trance that have pain above a certain level get all their rolls halved. They might give into pain and fall unconscious depending on toughness. This is more likely to happen more often the more severe the pain is, which is usually fatal in combat, since enemies will automatically target the unconscious victim's head with a perfectly accurate, perfectly square strike.

==Paralysis==
'''Effects''': The creature can't move. Severity only decreases the chance of resisting the symptom. Untargeted paralysis often leads to suffocation in smaller creatures, which can include dwarves.

==Swelling==
'''Effects''': Impedes the ability to use affected areas. Normally fairly harmless but can cause death by suffocation if it affects the throat. Prolonged swelling will lead to necrosis.

==Unconsciousness==
'''Effects''': Affected creature will pass out for the duration of this effect, even if the creature isn't in pain or extremely tired.

==Vomiting Blood==
'''Effects''': Much as excessive vomiting can lead to death from dehydration, vomiting blood can lead to death from blood loss. Considered to be a separate condition from coughing blood. If your creature happens to have green blood you'll be unable to tell this from nausea without checking the tiles.

[[ru:DF2012:Symptoms]]

Syndrome

2020-06-27T13:17:43Z

Albedo: copy edit; format info

{{Quality|Masterwork|13:02, 6 April 2015 (UTC)}}
{{av}}
[[File:Snakebite.png|200px|thumb|right|An example of a syndrome in effect. This hippo did not ultimately survive the encounter despite one bite being the only injury sustained.]]
A '''syndrome''' is a specific combination of [[symptoms]] that a poor, helpless creature might get from a disease, venom or other effect, through encountering certain other creatures, substances, or supernatural [[weather]]. Syndromes generally cause unpleasant and frequently fatal symptoms over a short to long period of time, but some will clear up over time or with the assistance of a [[doctor]]. A [[Health care|hospital]] is required to diagnose and potentially treat those syndromes that can be helped by treatment.

==List of syndromes==
Syndromes are generally named after the animal, substance or effect that delivers them.
{| {{prettytable}}
|- bgcolor="#dddddd"
! Syndrome
! Venom
! Acquired
! Short-term Symptoms
! Long-term Symptoms
! Chronic Symptoms
|-
| Adder bite
| adder venom (injected)
| Being bitten by an [[adder]], [[giant adder]] or [[adder man]]
| Strong pain
| Swelling Blisters Nausea
| None
|-
| Bark scorpion sting
| bark scorpion venom (injected)
| Being stung by a [[bark scorpion]], [[giant bark scorpion]] or [[bark scorpion man]]
| Strong pain
| None
| None
|-
| Black mamba bite
| black mamba venom (injected)
| Being bitten by a [[black mamba]], [[giant black mamba]] or [[black mamba man]]
| Dizziness Drowsiness Strong pain Fever Unconsciousness Complete paralysis1
| None
| None
|-
| Blob blisters
| cave blob fluid (contact or ingested)
| Touching a [[cave blob]]
| Mild pain Mild blisters
| None
| None
|-
| Brown recluse spider bite
| brown recluse spider venom (injected)
| Being bitten by a [[brown recluse spider]], [[giant brown recluse spider]] or [[brown recluse spider man]]
| Nausea Fever Pain 
| Severe localized necrosis
| None
|-
| Bumblebee sting
| bumblebee venom (injected)
| Being stung by a [[bumblebee]] worker
| Pain Strong swelling
| None
| None
|-
| Bushmaster bite
| bushmaster venom (injected)
| Being bitten by a [[bushmaster]], [[giant bushmaster]] or [[bushmaster man]]
| Strong pain Mild bleeding Dizziness Nausea Unconsciousness Complete paralysis1
| None
| None
|-
| Cave floater sickness
| cave floater gas (inhaled or ingested)
| Expelled from [[cave floater]]
| Mild nausea
| Fever Strong drowsiness (delayed) Strong dizziness (delayed)
| None
|-
| Cave spider bite
| cave spider venom (injected)
| Being bitten by a [[cave spider]]
| None
| None
| Very mild dizziness
|-
| Copperhead snake bite
| copperhead snake venom (injected)
| Being bitten by a [[copperhead snake]], [[giant copperhead snake]] or [[copperhead snake man]]
| Pain Swelling Nausea
| None
| None
|-
| Giant cave spider bite
| giant cave spider venom (injected)
| Being bitten by a [[giant cave spider]]
| Size-dependant paralysis.
| Death by asphyxiation, in small targets. Large targets are generally unhindered...unless you count the high probability of being eaten by the giant cave spider as a hindrance.
| None, not that it really matters.
|-
| Gila monster bite
| gila monster venom (injected)
| Being bitten by a [[gila monster]], [[giant gila monster]] or [[gila monster man]]
| Pain Mild swelling
| None
| None
|-
| Gnomeblight
| [[gnomeblight]] (contact, inhaled, injected, or ingested)
| Purposely exposing oneself to the extract. Only affects [[mountain gnome]]s and [[dark gnome]]s.
| None
| Severe systemic necrosis2
| None
|-
| Giant desert scorpion sting
| giant desert scorpion venom (injected)
| Being stung by a [[giant desert scorpion]]
| Necrosis of the brain and nervous system
| '''Certain death'''
| None, not that it really matters.
|-
| Helmet snake bite
| helmet snake venom (injected)
| Being bitten by a [[helmet snake]]
| Minor bleeding
| Fever Nausea Dizziness Localized swelling Localized oozing Localized bruising Strong pain Intense localized necrosis Possible loss of limb
| None
|-
| Honey bee sting
| honey bee venom (injected)
| Being stung by a [[honey bee]] worker
| Pain Strong swelling
| None
| None
|-
| Inebriation{{version|0.42.01}}
| [[Alcohol]] (consumed/injected)
| Consuming alcoholic drinks
| Nausea Dizziness Unconsciousness Personality changes Euphoria Erratic behavior Trouble breathing
| None
| None
|-
| Iron man cough
| iron man gas (inhaled)
| Expelled by [[iron man]]
| Coughing blood
| None
| None
|-
| King cobra bite
| king cobra venom (injected)
| Being bitten by a [[king cobra]]
| Complete paralysis1 Pain, dizziness, drowsiness
| None
| None
|-
| Phantom spider bite
| phantom spider venom (injected)
| Being bitten by a [[phantom spider]]
| None
| Numbness and mild dizziness
| None
|-
| Platypus sting
| platypus venom (injected)
| Being kicked by a [[platypus]], [[giant platypus]] or [[platypus man]]
| Pain and swelling
| Extreme pain, swelling possibly to the point of necrosis
| None
|-
| Rattlesnake bite
| rattlesnake venom (injected)
| Being bitten by a [[rattlesnake]], [[giant rattlesnake]] or [[rattlesnake man]]
| Pain, nausea, blisters, swelling, bruising
| Severe localized necrosis
| None
|-
| Serpent man bite
| serpent man venom (injected)
| Being bitten by a [[serpent man]]
| Complete paralysis1
| None
| None
|-
| Mummy's curse
| [[DF2014:Mummy|Disturbance interaction]].
| Being cursed by a [[mummy]], when caught raiding their tombs
| None
| None
| 20% chance of any skill roll failing, regardless of skill.
|-
| Vampirism
| [[Deity|Divine]] Curse.
| Drinking the blood of a [[vampire]]. Toppling statues in shrines in Adventure Mode or temples in Fortress Mode (random chance).
| None
| None
| Victim becomes a [[vampire]].
|-
| Werebeast Curse
| [[Deity|Divine]] Curse.
| Being bitten by a [[werebeast]] or toppling statues in shrines in Adventure Mode (random chance).
| None
| None
| Victim becomes a [[werebeast]].
|-
| Necromancy
| [[Deity|Divine]] Curse.
| Reading a book/slab that contains the secrets of life and death.
| None
| None
| Reader becomes a [[Necromancer]].
|-
| evil rain sickness3
|rowspan=7| Random
| Being caught outside in [[Weather#Evil weather|freakish weather]] in an evil [[biome]]
|rowspan=7| Random
|rowspan=7| Random
|rowspan=7| Random
|-
| evil cloud sickness4
| Being caught in a [Weather#Evil weather|creeping cloud]] in an evil [[biome]]
|-
| beast sickness5
| Encounters with [[forgotten beast]]s
|-
| titan sickness5
| Encounters with [[titan]]s
|-
| night sickness5
| Encounters with [[werebeast]]s or [[experiment]]s
|-
| demon sickness5
| Encounters with [[demon]]s
|-
| divine sickness5
| Encounters with [[angel]]s
|}
: 1. For small creatures such as humans and dwarves, paralysis tends to result in suffocation.
: 2. Necrosis of the brain will eventually result in death once the brain rots away completely.
: 3. Evil rain typically only causes minor symptoms such as blisters, bruising, coughing blood, dizziness, fever, nausea, oozing, and pain.
: 4. Evil clouds either cause major symptoms (as with beast/titan/demon sicknesses) or permanently transform creatures into [[Undead|zombie-like]] forms.
: 5. [[Titan]]s, [[forgotten beast]]s, [[werebeast]]s, [[experiment]]s, [[demon]]s and [[angel]]s have a chance to have a randomized syndrome. These range from mildly hazardous (mild [[Symptoms#Blisters|blisters]] from inhaling boiling blood) to instantly fatal (severe necrosis from a contact poison attached to a breath weapon/creature made of blood).

==The anatomy of a syndrome==
Mechanically, syndromes are bundles of tokens attached to a material (or to an interaction effect; see below) - they're confined to creature materials in vanilla DF, but it's a simple matter to add them to inorganic materials. When the material is injected, touched, inhaled, or ingested (depending on the syndrome), the creature suffers the predations of a nasty disease or poison. Here's an example syndrome, taken from the Giant Cave Spider raws.

If you are having troubles getting the syndromes to work (i.e., in combat reports, getting "'''supersnake''' n/a splatters~etc"), then simply throw the venom template into the actual creature's raw, which is what the LOCAL_CREATURE_MAT actually calls on; the venom being in the same file.

[USE_MATERIAL_TEMPLATE:VENOM:CREATURE_EXTRACT_TEMPLATE]
[STATE_NAME:ALL_SOLID:frozen giant cave spider venom]
[STATE_ADJ:ALL_SOLID:frozen giant cave spider venom]
[STATE_NAME:LIQUID:giant cave spider venom]
[STATE_ADJ:LIQUID:giant cave spider venom]
[STATE_NAME:GAS:boiling giant cave spider venom]
[STATE_ADJ:GAS:boiling giant cave spider venom]
[PREFIX:NONE]
[ENTERS_BLOOD]
[SYNDROME]
[SYN_NAME:giant cave spider bite]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[SYN_IMMUNE_CREATURE:SPIDER_CAVE:ALL]
[SYN_INJECTED]
[CE_PARALYSIS:SEV:100:PROB:100:RESISTABLE:SIZE_DILUTES:START:5:PEAK:10:END:20]

The first line, USE_MATERIAL_TEMPLATE, is creating a new material, called POISON, using the CREATURE_EXTRACT_TEMPLATE as the basis. After this, the STATE_NAME and STATE_ADJ tokens are used to define the names and adjectives assigned to different states of the material - GAS, LIQUID and ALL_SOLID, in this case, though ALL is also a valid token. At this stage, you can use any material tags like MAT_FIXED_TEMP or similar to set further material properties, though this usually isn't necessary.

ENTERS_BLOOD
This tag determines whether a poison enters the blood or not. If it is not included, the poison will splatter (if liquid) or flow (if gas) over the affected body part instead when injected. If you're using a contact poison, leave this out. Necessary for injected poisons.
SYNDROME
This tag ends the material details and begins the definition of the actual syndrome.
SYN_NAME
This one is self-explanatory - the name of the syndrome as it will appear in-game.
SYN_AFFECTED_CLASS
This token defines what CREATURE_CLASS will be affected by the syndrome. Most creatures are classed under GENERAL_POISON. Multiple tokens can be used in a single syndrome.
SYN_IMMUNE_CLASS
As above, but makes class immune.
SYN_IMMUNE_CREATURE
This token defines which creatures CANNOT be affected by the syndrome - useful for addressing specific instances within a population, such as a specific caste or an individual creature that falls under GENERAL_POISON. Syntax is [SYN_IMMUNE_CREATURE:creature:caste]. ALL can be used for the caste.
SYN_AFFECTED_CREATURE
As above, but makes creature or caste susceptible.
SYN_CLASS
This tag sets a class for the syndrome that can be used in [[Interaction token|interactions.]]
SYN_IDENTIFIER{{version|0.42.01}}.
Similar to SYN_CLASS, this sets an identifier that can be shared between multiple syndromes, for use with the SYNDROME_DILUTION_FACTOR creature token. In vanilla DF, this is used to allow dwarves to drink more alcohol before becoming inebriated.
SYN_NO_HOSPITAL{{version|0.42.01}}.
Probably prevents affected dwarves from being carried to the hospital.{{verify}}
SYN_CONCENTRATION_ADDED:x:x{{version|0.42.01}}.
Repeated exposure to the syndrome will result in the effects becoming more intense. In vanilla [SYN_CONCENTRATION_ADDED:100:1000] is used with alcohol.

SYN_INJECTED, SYN_CONTACT, SYN_INHALED, SYN_INGESTED
This token determines the method of infection - injected syndromes must be injected via a creature attack, while contact syndromes result from any contamination of a creature by material splatter (such as blood), inhaled syndromes must be inhaled in gaseous form (such as from boiling or a creature breath attack), and ingestion syndromes must be eaten or drunk. Any combination of these tags can be used. A fun variation on the usual creature injection routine is to create a material with a SYN_CONTACT syndrome and have a creature use it for blood - this tends to end poorly for any predator that chooses to attack them.

[SPECIALATTACK_INJECT_EXTRACT:LOCAL_CREATURE_MAT:VENOM:LIQUID:100:100]
This is one method for getting a poison into a creature. If [ENTERS_BLOOD] is applied, it will be injected into the bloodstream. Otherwise, it will just splatter over the area. Put this on a creature attack. Substance type (gas, liquid, solid) does not appear to have an effect. The numbers on the end are minimum and maximum.

CE_X, or creature effect tokens, are the real meat and bones of your syndrome. They're detailed below.

==Creature effect tokens==
Each and every syndrome has a number of creature effect tokens, represented by CE_X - these lovely little beauties determine exactly how the poor creature suffering from the syndrome is affected. An example CE token is as follows:

[CE_NECROSIS:SEV:100:PROB:100:LOCALIZED:VASCULAR_ONLY:RESISTABLE:START:50:PEAK:1000:END:2000]

In this example, we have an effect that will always cause severe necrosis in whichever bodypart it touches, so long as that bodypart is vascular and that the creature is not able to resist it in some manner. The effect begins shortly after the syndrome is contracted, peaks 1000 [[time|time units]] afterwards, and finally ceases another 1000 time units later.

As a general rule of thumb, so long as CE_X starts the string and START/(PEAK/END) ends it, the order of the intervening tokens isn't important. PEAK and END aren't required.

*CE_X
The effect type. This can be a number of different tokens, as detailed in the table below this list.
*SEV:X
The severity of the effect. Higher values appear to be worse, with SEV:1000 CE_NECROSIS causing a part to near-instantly become rotten.
*PROB:X
The probability of the effect actually manifesting in the victim, as a percentage. 100 means always, 1 means a 1 in 100 chance.
*LOCALIZED (Overwrites BP tokens)
This tag causes an effect to ignore all BP tokens and then forces the game to attempt to apply the effect to the limb that came into contact with the contagion - i.e. the part that was bitten by the creature injecting the syndrome material, or the one that was splattered by a contact contagion. If an effect can not be applied to the contacted limb (such as IMPAIR_FUNCTION on a non-organ) then this token makes the syndrome have no effect. This token also makes inhaled syndromes have no effect.
*BP:BODY_PART:TISSUE (Overwritten by LOCALIZED)
Specifies which body parts and tissues are to be affected by the syndrome. BODY_PART can be BY_CATEGORY:x to target body parts with a matching [CATEGORY:x] [[body token]] (or ALL to affect everything), BY_TYPE:x to target body parts having a particular type (UPPERBODY, LOWERBODY, HEAD, GRASP, or STANCE), or BY_TOKEN:x to target individual body parts by their ID (as specified in the [BP] token). For example, if you wanted to target the lungs of a creature, you would use BP:BY_CATEGORY:LUNG:ALL. The syndrome would act on all bodyparts within the creature with the CATEGORY tag LUNG and affect all tissue layers. For another example, say you wanted to cause the skin to rot off a creature - you could use BP:BY_CATEGORY:ALL:SKIN, targeting the SKIN tissue on all bodyparts. Multiple targets can be given in one syndrome by placing the BP tokens end to end. This is one of the most powerful and useful aspects of the syndrome system, as it allows you to selectively target bodyparts relevant to the contagion, like lungs for coal dust inhalation, or the eyes for exposure to an acid gas. Not everything takes a target!
*VASCULAR_ONLY (Optional)
This syndrome only affects tissue layers with the VASCULAR token.
*MUSCULAR_ONLY (Optional)
This syndrome only affects tissue layers with the MUSCULAR token. Are you seeing a trend here?
*SIZE_DILUTES (Optional)
This token presumably causes the effects of the syndrome to scale with the size of the creature compared to the size of the dose of contagion they received, but has yet to be extensively tested.
*SIZE_DELAYS (Optional)
As above, this token has yet to be tested but presumably delays the onset of a syndrome according to the size of the victim.
*DWF_STRETCH:X{{version|0.42.01}} (Optional)
Multiplies the duration of the syndrome by X in Fortress mode. If X is 72, syndrome will last the same amount of ticks in fortress and adventure mode.
*ABRUPT{{version|0.42.01}} (Optional)
Makes the symptom begin immediately rather than ramping up. {{verify}}
*CAN_BE_HIDDEN (Optional)
Can be hidden by a unit assuming a secret identity, such as a [[vampire]]. {{verify}}
*RESISTABLE (Optional)
Determines if the effect can be hindered by the target creature's [[Attribute#Disease_Resistance|disease resistance attribute]]. Without this token, disease resistance is ignored.

The details of this table are still being thrashed out by modders, so if you have anything to add, please don't hesitate to hit the edit button!

Non-targeted syndromes will ignore any BP tokens and LOCALIZED tokens.
{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Description
|-
| CE_BLEEDING
| Yes
| Causes the targeted bodypart to start bleeding, with heavy enough bleeding resulting in the death of the sufferer. Some conditions seem to cause bleeding to be fatal no matter how weak.
|-
| CE_BLISTERS
| Yes
| Covers the targeted bodypart with blisters.
|-
| CE_BRUISING
| Yes
| Causes the targeted bodypart to undergo bruising.
|-
| CE_IMPAIR_FUNCTION
| Yes
| An organ afflicted with this CE is rendered inoperable - for example, if both lungs are impaired the creature can't breathe and will suffocate. This token only affects organs, not limbs. Note that this effect is currently bugged, and will not "turn off" until the creature receives a wound to cause its body parts to update.
|-
| CE_NECROSIS
| Yes
| Causes the targeted bodypart to rot, with associated tissue damage, miasma emission and bleeding. The victim slowly bleeds to death if the wound is not treated. Badly necrotic limbs will require amputation.
|-
| CE_NUMBNESS
| Yes
| Causes numbness in the affected body part, blocking pain. Extreme numbness may lead to sensory nerve damage.
|-
| CE_OOZING
| Yes
| Causes pus to ooze from the afflicted bodypart.
|-
| CE_PAIN
| Yes
| Afflicts the targeted bodypart with intense pain.
|-
| CE_PARALYSIS
| Yes
| Causes paralysis. Paralysis is complete paralysis and will cause suffocation in smaller creatures. Paralysis on a limb may lead to motor nerve damage.
|-
| CE_SWELLING
| Yes
| Causes the targeted bodypart to swell up. Extreme swelling may lead to necrosis.
|-
| CE_COUGH_BLOOD
| No
| This effect results in the sufferer periodically coughing blood, which stains the tile they're on and requires cleanup. It doesn't appear to be lethal, but may cause minor bleeding damage.
|-
| CE_DIZZINESS
| No
| Inflicts the Dizziness condition, occasional fainting and a general slowdown in movement and work speed.
|-
| CE_DROWSINESS
| No
| Causes the Drowsiness condition.
|-
| CE_FEVER
| No
| Causes the Fever condition.
|-
| CE_NAUSEA
| No
| Causes the Nausea condition, and heavy vomiting. Can eventually lead to dehydration and death.
|-
| CE_UNCONSCIOUSNESS
| No
| Renders unconscious.
|-
| CE_VOMIT_BLOOD
| No
| This effect results in the sufferer periodically vomiting blood, which stains the tile they're on and requires cleanup. It doesn't appear to be lethal, but may cause minor bleeding damage.
|-
| CE_ERRATIC_BEHAVIOR{{version|0.42.01}}
| No
| Causes erratic behavior, meaning "People that like to brawl have a chance of starting a brawl-level fight with any nearby adult" [http://www.bay12forums.com/smf//index.php?topic=159164.msg7632503#msg7632503 -Toady]
|}
====Healing Effects====
Starting with DF version 0.47.01, there are healing counterparts to most of the tokens above that will heal various syndrome effects or physical damage.
{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Description
|-
| CE_STOP_BLEEDING
| Yes?
| Decreases the severity of the bleeding of any wounds or syndrome effects on the targeted bodypart. The SEV value probably controls by how much the bleeding is decreased.
|-
| CE_CLOSE_OPEN_WOUNDS
| Yes?
| Closes any wounds on the targeted bodypart with speed depending on the SEV value.
|-
| CE_HEAL_TISSUES
| Yes?
| Heals the tissues of the targeted bodypart with speed depending on the SEV value.
|-
| CE_HEAL_NERVES
| Yes?
| Heals the nerves of the targeted bodypart with speed depending on the SEV value.
|-
| CE_REDUCE_PAIN
| Yes?
| Decreases the severity of pain produced by wounds or syndrome effects on the targeted bodypart. The SEV value probably controls by how much the pain is decreased.
|-
| CE_REDUCE_SWELLING
| Yes?
| Decreases the severity of swelling on the targeted bodypart.
|-
| CE_CURE_INFECTION
| Yes?
| Probably decreases the severity of the infection from infected wounds over time.
|-
| CE_REDUCE_PARALYSIS
| Yes?
| Decreases the severity of any paralysis effects on the targeted bodypart.
|-
| CE_REGROW_PARTS
| Yes
| Causes missing bodyparts to regrow. SEV controls how quickly bodyparts are regrown. In adventure, parts will be regrown until you travel or wait/sleep {{bug|0011396}}.
|-
| CE_REDUCE_DIZZINESS
| No
| Decreases the severity of any dizziness the creature has.
|-
| CE_REDUCE_NAUSEA
| No
| Decreases the severity of any nausea the creature has.
|-
| CE_REDUCE_FEVER
| No
| Decreases the severity of any fever the creature has.
|}

===Special Effects===
Several special syndrome effects take different arguments than the above. These are used for generated interactions in unmodded games, but may be used as well for any substance or custom interaction.

{| {{prettytable}}
|- bgcolor="Bisque"
! Token
! Accepts Target
! Arguments
! Description
|-
| CE_ADD_TAG
| No
| tags
| Adds a tag to the affected creature. Many arguments can be used sequentially within one syndrome token. Valid tags are the same as that of the [[interaction token]] '''IT_REQUIRES''', ie.

BLOODSUCKER, CAN_LEARN, CAN_SPEAK, CRAZED, EXTRAVISION, LIKES_FIGHTING (or LIKESFIGHTING), MISCHIEVOUS (or MISCHIEVIOUS), NO_CONNECTIONS_FOR_MOVEMENT, NO_DIZZINESS, NO_DRINK, NO_EAT, NO_FEVERS, NO_PHYS_ATT_GAIN, NO_PHYS_ATT_RUST, NO_SLEEP, NO_THOUGHT_CENTER_FOR_MOVEMENT, NOBREATHE, NOEMOTION, NOEXERT, NOFEAR, NONAUSEA, NOPAIN, NOSTUN, NOT_LIVING, NOTHOUGHT, OPPOSED_TO_LIFE, PARALYZEIMMUNE, SUPERNATURAL, TRANCES, NO_AGING, STERILE, UTTERANCES.
|-
| CE_REMOVE_TAG
| No
| tags
| Removes a tag from a creature. Supported arguments are the same as CE_ADD_TAG.
|-
| CE_DISPLAY_TILE
| No
| TILE:[[Tilesets|tile number]]:[[Color#Modding color|colour]]
| The creature displays the specified tile and colour instead of its normal one.
|-
| CE_DISPLAY_NAME
| No
| NAME:singular:plural:adjective
| Attaches a specified name to the creature's normal name.
|-
| CE_FLASH_TILE
| No
| TILE:tile number:colour:FREQUENCY:ticks default tile:ticks syndrome tile
| The creature flashes between its normal tile and the one specified here.
|-
| CE_PHYS_ATT_CHANGE
| No
| [[Attribute]]:percentage:fixed boost(?)
| Alters the physical [[attribute]]s of a creature.
|-
| CE_MENT_ATT_CHANGE
| No
| [[Attribute]]:percentage:fixed boost(?)
| Alters the mental [[attribute]]s of a creature.
|-
| CE_BODY_APPEARANCE_MODIFIER
| No
| APPEARANCE_MODIFIER:HEIGHT/LENGTH/BROADNESS:percentage(?)
| Alters the size of the creature.
|-
| CE_BP_APPEARANCE_MODIFIER
| Yes
| body part:APPEARANCE_MODIFIER:attribute:number]
| Alters the characteristics (height, width etc.) of a body part.
|-
| CE_MATERIAL_FORCE_MULTIPLIER
| No
| MAT_MULT:[[material token|material]]:A:B
| Makes creature affected by materials more or less by a factor of A/B. If A is 3 and B is 2, the creature will be 1.5x weaker to the defined material (can be NONE:NONE for all); if 2:3, the creature will be 1.5 times stronger.
|-
| CE_SPEED_CHANGE
| No
| speed modifier:number
| Changes the speed of a creature.
Speed modifier contains one or both of:
* SPEED_PERC:percentage (this modifies a creature's in-game speed, so higher numbers are faster)
* SPEED_ADD:number (this modifies a creature's [SPEED:XX] token, so higher numbers are slower. Negative numbers are accepted though will only reduce a creature's speed to zero)
The minimum and maximum speeds able to be created by CE_SPEED_CHANGE are 99 and 10,000 respectively.

|-
| CE_CAN_DO_INTERACTION
| No
|
| Makes the creature able to perform an interaction. See [[Interaction token]]. To specify the interaction, use the argument:
* CDI:INTERACTION:interaction name
|-
| CE_SPECIAL_ATTACK_INTERACTION{{version|0.47.01}}
| Yes
| INTERACTION:<interaction name>:BP:<selection criteria>:<name of category,type, or token of designated part/parts>
| Makes the creature able to perform an interaction when using an attack with a designated body part/parts. See [[#Spreading diseases in 0.47.01|below]] for an example

|-
| CE_BODY_MAT_INTERACTION
| No
| MAT_TOKEN:<body material token>
| Causes one of the creature's body materials to trigger an interaction when the material is ingested, injected, etc (depending on the [CE:SYNDROME_TAG]s used; note that more than one may be specified). Generated vampire syndromes use '''RESERVED_BLOOD''' as the body material token in this syndrome tag, so as to specify the blood material of any creature with the syndrome. The following tokens should be inserted after this:
* '''CE:INTERACTION:interaction_id''' - replace 'interaction_id' with the name of the target interaction
* '''CE:SYNDROME_TAG:syndrome_trigger_type''' - replace 'syndrome_trigger_type' with any of SYN_INGESTED, SYN_INJECTED, SYN_CONTACT, SYN_INHALED
The linked interaction must have an [[Interaction_token#I_SOURCE|[I_SOURCE:INGESTION]]] token for this to work!

Note that this currently only works on materials obtained from historical figures and has only been tested with ingested materials linked to interactions with ADD_SYNDROME interaction effects.

|-
| CE_BODY_TRANSFORMATION
| No
| PROB:percentage:START:time:END:time
| Transforms into another creature. PROB and END arguments optional. The target creature may either be specified directly using CE:CREATURE or else set to be randomly selected as guided by creature and/or caste flag restrictions (of which multiple may be specified).
* CE:CREATURE:CREATURE_ID:CASTE_ID - Specify the creature and caste (for example: CE:CREATURE:DWARF:FEMALE). ANY can be used in place of a specific CASTE_ID to randomise the caste for every transformation. 
* CE:CREATURE_FLAG:FLAG{{version|0.47.01}} - Any creature with the specified [[:Interaction_token#Creature_and_Caste_Flags|creature flag]] is a valid transformation target. 
* CE:FORBIDDEN_CREATURE_FLAG{{version|0.47.01}} - Forbids all creatures with the specified [[:Interaction_token#Creature_and_Caste_Flags|creature flag]] from being randomly selected. 
* CE:CREATURE_CASTE_FLAG:FLAG{{version|0.47.01}} - Any creature with the specified [[:Interaction_token#Creature_and_Caste_Flags|caste flag]] is a valid transformation target. 
* CE:FORBIDDEN_CREATURE_CASTE_FLAG{{version|0.47.01}} - Forbids all creatures with the specified [[:Interaction_token#Creature_and_Caste_Flags|caste flag]] from being randomly selected. 
*CE:HAVE_FAST_EFFORTLESS_GAIT_SPEED{{version|0.47.01}} - Unknown. Possibly disallows all creatures with only slow gaits.{{verify}}

Note that any wounds the creature has suffered will instantly heal upon transforming, both into and out of the target form. [[Undead]] limbs of a creature with this token will grow into a full instance of that creature.
|-
| CE_SKILL_ROLL_ADJUST
| No
| PERC:percentage:PERC_ON:percentage
| Alters the skill level of a creature. The argument PERC specifies a percentage of the creature's current skill, and PERC_ON the probability of the effect being applied on a particular roll.
|-
| CE_SENSE_CREATURE_CLASS
| No
| START:time:CLASS:creature class:tile:color
| Allows creature to see other creatures with given class through walls. Vampires, for example, have START:0:CLASS:GENERAL_POISON:15:4:0:1.
|-
| CE_CHANGE_PERSONALITY{{version|0.42.01}}
| No
| FACET:[[DF2014:Personality_trait#Facets|trait]]:amount
| Changes a [[personality trait]] by amount. Multiple FACET:trait:amount sets may be used.
|-
| CE_FEEL_EMOTION{{version|0.42.01}}
| No
| EMOTION:[[emotion]]
| Makes the creature feel a specific [[emotion]]; severity based on standard SEV value. The [[thought]] the creature receives is: "[creature] feels [emotion] due to [syndrome name]". See [[Emotion]] for the list of valid emotions.
|}

'''All''' creature effect tokens take START, END and PROB numbers, and can be followed by [CE:PERIODIC] and/or [CE:COUNTER_TRIGGER] to restrict when they actually take effect.
* PERIODIC:period_type:min_value:max_value
* {{text anchor|COUNTER_TRIGGER}}:counter_name:min_value:max_value:REQUIRED

Currently, the only valid period type is MOON_PHASE.

===Counter Triggers===
Valid counter values are below:

{| {{prettytable}}
|- bgcolor="Bisque"
! Counter
! Description
|-
| ALCOHOLIC
| How long it's been (in [[time]] units) since the creature last had a drink of alcohol. Only present on creatures who need alcohol to get through the working day.
* 100800 (3 months) = and is starting to work slowly due to its scarcity
* 201600 (6 months) = and really wants a drink
* 302400 (9 months) = and has gone without a drink for far, far too long
* 403200 (1 year) = and can't even remember the last time he/she had some
|-
| CAVE_ADAPT
| How cave-adapted the creature is. Increases by 1 for every [[time]] unit spent underground, to a maximum of 800000.
* 403200 (1 year) = going outside causes irritation
* 604800 (1.5 years) = going outside causes nausea
|-
| PARTIED_OUT
| How long before the creature will decide to attend another party. Starts at 3+ months and counts down to zero.
|-
| MILK_COUNTER
| How long before the creature can be milked again. Starts at the creature's MILK frequency and counts down to zero.
|-
| EGG_SPENT
| How long before the creature can lay more eggs. Starts at 3 months and counts down to zero.
|-
| GROUNDED_ANIMAL_ANGER
| How angry (and likely to attack) an animal is from being over-crowded. Increases when over-crowded and otherwise counts down to zero.
|-
| TIME_SINCE_SUCKED_BLOOD
| How long it's been (in [[time]] units) since the creature last sucked somebody's blood.
|-
| DRINKING_BLOOD
| How much longer the creature will be drinking somebody's blood. Starts at 2.4 days and counts down to zero.
|}

{{mod}}

==Inorganic syndromes and you!==
It's perfectly possible - and quite simple - to add a nasty syndrome to a type of rock or metal - you simply add the syndrome tokens to the material definition in the same manner that you would add them to a creature material definition. The only catch is that since your hapless dwarves will only normally encounter the material in metal, gem or boulder form, a bit of creativity must be used to actually get them inside your citizens - that is, you need to make them 'explosively boil' as soon as they're mined or produced. This has the sad side effect of destroying the actual item - sorry, no highly radioactive uranium this release.

The easiest way to accomplish this is to assign the material a low boiling point, usually just under room temperature, and make sure its temperature is fixed to a point above it.
[MELTING_POINT:NONE]
[BOILING_POINT:10000]
[MAT_FIXED_TEMP:10001]
Now, as soon as this substance hits the open air - by being mined, smelted or reaction-produced at a custom workshop - it will EXPLOSIVELY BOIL, flooding a small area with delicious syndrome-rich gas. Creatures who inhale the gas will be immediately hit with the syndrome you thoughtfully attached to the material definition earlier!

There are a number of other tokens you can use to control the colour and naming conventions of your syndrome material, referred to as [[material definition token]]s.

==Spreading diseases==
It's fully possible to make a nasty disease capable of spreading itself from an infected dwarf to others, though it requires some skill in modding [[interaction token|interactions]] as well. Here is an example of a plague-inflicting interaction:

[INTERACTION:PLAGUE]
[I_TARGET:A:CREATURE]
[IT_LOCATION:CONTEXT_CREATURE]
[IT_FORBIDDEN:NOT_LIVING]
[IT_AFFECTED_CLASS:GENERAL_POISON]
[IT_MANUAL_INPUT:creatures]
[I_EFFECT:ADD_SYNDROME]
[IE_TARGET:A]
[IE_IMMEDIATE]
[SYNDROME]
[SYN_NAME:the plague]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[CE_FEVER:SEV:250:PROB:100:START:250:PEAK:1500:END:25000]
[CE_BLISTERS:SEV:325:PROB:100:BP:BY_CATEGORY:ALL:SKIN:START:250:PEAK:1500:END:25000]
[CE_NECROSIS:SEV:300:PROB:100:BP:BY_CATEGORY:ALL:ALL:VASCULAR_ONLY:START:22500:PEAK:23750:END:25000]
[CE_CAN_DO_INTERACTION:START:1500:END:25000]
[CDI:ADV_NAME:Spread the plague]
[CDI:INTERACTION:PLAGUE]
[CDI:TARGET:A:LINE_OF_SIGHT]
[CDI:TARGET_RANGE:A:10]
[CDI:WAIT_PERIOD:30]

As you can see, the syndrome here inflicts blisters, fever and, after roughly a month, necrosis of the whole body - that's when the infected creatures will start dying out. But before that happens, CE_CAN_DO_INTERACTION makes them capable of spreading the plague further.

You also need a disease vector that will bring the plague straight to your fort. (hint: use [[large rat|various]] [[rat man|species]] [[giant rat|of rats]] - they're perfect for that). The following code, added to a creature's raws, ensures the creature will infect anybody it encounters:

[CAN_DO_INTERACTION:PLAGUE]
[CDI:ADV_NAME:Spread the plague]
[CDI:TARGET:A:LINE_OF_SIGHT]
[CDI:TARGET_RANGE:A:10]
[CDI:WAIT_PERIOD:30]

As soon as the said creature is startled by your dwarves, the [[fun]] will begin.

==''In 0.47.01''==
As of version 0.47.01, it may be possible to use a creature's established methods of attack for use in disease-spreading.

Let's use the borrowed example of the plague above. This time, the plague will spread through biting, using the following syndrome code:

[INTERACTION:PLAGUE]
[I_TARGET:A:CREATURE]
[IT_LOCATION:CONTEXT_CREATURE]
[IT_FORBIDDEN:NOT_LIVING]
[IT_AFFECTED_CLASS:GENERAL_POISON]
[IT_MANUAL_INPUT:creatures]
[I_EFFECT:ADD_SYNDROME]
[IE_TARGET:A]
[IE_IMMEDIATE]
[SYNDROME]
[SYN_NAME:the plague]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[CE_FEVER:SEV:250:PROB:100:START:250:PEAK:1500:END:25000]
[CE_BLISTERS:SEV:325:PROB:100:BP:BY_CATEGORY:ALL:SKIN:START:250:PEAK:1500:END:25000]
[CE_NECROSIS:SEV:300:PROB:100:BP:BY_CATEGORY:ALL:ALL:VASCULAR_ONLY:START:22500:PEAK:23750:END:25000]
[CE_SPECIAL_ATTACK_INTERACTION:INTERACTION:PLAGUE:BP:BY_CATEGORY:TOOTH:START:0:ABRUPT]

The line [CE_SPECIAL_ATTACK_INTERACTION:INTERACTION:BITE_PLAGUE:BP:BY_CATEGORY:MOUTH:BP:BY_CATEGORY:TOOTH:START:0:ABRUPT] allows any infected creature with an attack using mouth or tooth category body parts to immediately spread the disease using said attack. The victim of the attack may then spread the disease if they are able to attack with the needed body part/parts.

{{Category|Modding}}
{{Category|Creature attributes}}
{{Category|Tokens}}
[[ru:DF2012:Syndrome]]

Gila monster

2020-06-27T08:09:48Z

Albedo: "relatively" mild venom

{{Quality|Exceptional|16:23, 9 December 2016 (UTC)}}
{{creaturelookup/0
|bone=0-4
|meat=2-6
|scale=1
|fat=2-6
|skull=1
|contrib=no
|wiki=yes}}
{{av}}
{{creaturedesc}}

'''Gila monsters''' are small [[Creature|reptiles]] found in all [[desert]] [[biome]]s. They are solitary creatures who only spawn one at a time. While carnivorous, they are less than half the size of a [[cat]] and therefore should not pose a threat to an adult [[dwarf]]. They do, however, possess a [[Syndrome|venomous]] bite which is ''relatively'' mild (as far as venoms go), but still causes pain and swelling on the victim; and with a [[Attribute#Toughness|flimsy]] dwarf, pain can lead to unconsciousness, which is never a good look in combat.

Gila monsters are natural swimmers and are able to path through [[water]] and breathe in it, should your desert map possess any.

Gila monsters are fairly standard as far as [[pet]]s go, should the player choose to [[Animal trainer|train]] them. They produce similar products to cats when butchered, and so can be used if the player wants some extra [[meat]]. They fare relatively well when used for [[egg production]] as they are one of the better egg-layers among desert creatures, laying between 2 to 12 [[egg]]s at a time. However, they are ultimately less productive than [[ostrich]]es and several domesticated poultry.

Some dwarves [[Preferences|like]] gila monsters for their ''venomous bite'' and their ''colouration''.

[[File:AZ Gila Monster 01.jpg|thumb|400px|center|Admired for its ''venomous bite''.]]

{{gamedata}}
{{Creatures}}
{{Category|Animals}}

Venom

2020-06-27T08:02:15Z

Albedo: style

{{Quality|Superior|05:09, 17 May 2015 (UTC)}}
{{av}}

'''Venom''' is a naturally-occurring poison that will cause a [[syndrome]] in certain creatures when certain conditions are met, typically when entering the [[blood]] via a [[serpent man]] or [[Giant cave spider|giant cave spider bite]]. It is produced by certain creatures according to their [[raw file]], and may be [[extracts|extracted]] and stored in [[vial]]s.

Each specific animal's venom delivers a [[Syndrome#List of syndromes|specific syndrome]], which is a known combination of [[symptoms]], some short term, some long term, and some (in rare cases) permanent (aka "chronic"). Some few syndromes (such as [[gila monster]]s') are seen as mild annoyances, some (such as a [[giant desert scorpion]]s') are a death sentence, but most are a mortal threat, at least. Of the wide of variety possible symptoms, one of the mildest is [[Symptoms#Nausea|nausea]] and vomiting, but even that can dehydrate a dwarf and take them out of combat while they seek to quench their thirst. The most immediately dangerous venoms cause [[Symptoms#Paralysis|paralysis]], which can stop the lungs, leading to suffocation. Most any bite that causes strong [[Symptoms#Pain|pain]] can in turn cause unconsciousness, leaving the victim helpless in combat, which is rarely survived. Longer term, [[Symptoms#Blisters|blisters]] can lead to deadly infections, and [[Symptoms#Necrosis|necrosis]] (which causes tissue to die) of any body part can also lead to eventual death, but the usual treatment, amputation, is not much better. Even [[Symptoms#Dizziness|mild dizziness]] can be a death sentence to any dwarf who works or travels near magma, water or long falls (and do any ''not''?). There are few venoms that ''can't'' kill an unlucky dwarf, one way or the other; if your fortress has many venomous creatures nearby, have some [[coffin]]s ready.

Currently, it is disputed whether or not venom can be administered, but it may still be purchased or sold.

Research has shown that in at least some circumstances, venom and other syndrome-inducing materials can be spattered or covered upon weapons and bolts, which may result in attacks inflicting the related syndromes. {{cite forum|106397}}

Some [[forgotten beast]]s and [[titan]]s are generated with venom, which they can inject through bites or stingers, alternatively covering their bodies entirely or making their [[blood]] toxic.

[[File:venom_snake.jpg|thumb|250px|center|A snake's venom.]]

==See also==
*[[Syndrome]] for a list of various venomous varmints.

{{Translation
| dwarven = zamoth
| elvish = neleni
| goblin = luskon
| human = ámtoc
}}

{{Category|Creature attributes}}
{{Category|Extracts}}
[[ru:Venom]]

Venom

2020-06-27T07:59:52Z

Albedo: how many different ways can you say "death sentence"?

{{Quality|Superior|05:09, 17 May 2015 (UTC)}}
{{av}}

'''Venom''' is a naturally-occurring poison that will cause a [[syndrome]] in certain creatures when certain conditions are met, typically when entering the [[blood]] via a [[serpent man]] or [[Giant cave spider|giant cave spider bite]]. It is produced by certain creatures according to their [[raw file]], and may be [[extracts|extracted]] and stored in [[vial]]s.

Each specific animal's venom delivers a [[Syndrome#List of syndromes|specific syndrome]], which is a known combination of [[symptoms]], some short term, some long term, and some (in rare cases) permanent (aka "chronic"). Some few syndromes (such as [[gila monster]]s') are seen as mild annoyances, some (such as a [[giant desert scorpion]]s') are a death sentence, but most are a mortal threat, at least. Of the wide of variety possible symptoms, one of the mildest is [[Symptoms#Nausea|nausea]] and vomiting, but even that can dehydrate a dwarf and take them out of combat while they seek to quench their thirst. The most immediately dangerous venoms cause [[Symptoms#Paralysis|paralysis]], which can stop the lungs, leading to suffocation. Most any bite that causes strong [[Symptoms#Pain|pain]] can in turn cause unconsciousness, leaving the victim helpless in combat, which is rarely survived. Even [[Symptoms#Dizziness|mild dizziness]] can be a death sentence to any dwarf who works or travels near magma, water or long falls (and do any ''not''?). Longer term, [[Symptoms#Blisters|blisters]] can lead to deadly infections, and [[Symptoms#Necrosis|necrosis]] (which causes tissue to die) of any body part can also lead to eventual death, but the usual treatment, amputation, is not much better. If your fortress has many venomous creatures nearby, have some [[coffin]]s ready.

Currently, it is disputed whether or not venom can be administered, but it may still be purchased or sold.

Research has shown that in at least some circumstances, venom and other syndrome-inducing materials can be spattered or covered upon weapons and bolts, which may result in attacks inflicting the related syndromes. {{cite forum|106397}}

Some [[forgotten beast]]s and [[titan]]s are generated with venom, which they can inject through bites or stingers, alternatively covering their bodies entirely or making their [[blood]] toxic.

[[File:venom_snake.jpg|thumb|250px|center|A snake's venom.]]

==See also==
*[[Syndrome]] for a list of various venomous varmints.

{{Translation
| dwarven = zamoth
| elvish = neleni
| goblin = luskon
| human = ámtoc
}}

{{Category|Creature attributes}}
{{Category|Extracts}}
[[ru:Venom]]

Venom

2020-06-27T07:58:08Z

Albedo: & more

{{Quality|Superior|05:09, 17 May 2015 (UTC)}}
{{av}}

'''Venom''' is a naturally-occurring poison that will cause a [[syndrome]] in certain creatures when certain conditions are met, typically when entering the [[blood]] via a [[serpent man]] or [[Giant cave spider|giant cave spider bite]]. It is produced by certain creatures according to their [[raw file]], and may be [[extracts|extracted]] and stored in [[vial]]s.

Each specific animal's venom delivers a [[Syndrome#List of syndromes|specific syndrome]], which is a known combination of [[symptoms]], some short term, some long term, and some (in rare cases) permanent (aka "chronic"). Some few syndromes (such as [[gila monster]]s') are seen as mild annoyances, some (such as a [[giant desert scorpion]]s') are a death sentence, but most are a mortal threat, at least. Of the wide of variety possible symptoms, one of the mildest is [[Symptoms#Nausea|nausea]] and vomiting, but even that can dehydrate a dwarf and take them out of combat while they seek to quench their thirst. The most immediately dangerous venoms cause [[Symptoms#Paralysis|paralysis]], which can stop the lungs, leading to suffocation. Most any bite that causes strong [[Symptoms#Pain|pain]] can in turn cause unconsciousness, leaving the victim helpless in combat, which is often fatal. Even [[Symptoms#Dizziness|mild dizziness]] can be a death sentence to any dwarf who works or travels near magma, water or long falls (and do any ''not''?). Longer term, [[Symptoms#Blisters|blisters]] can lead to deadly infections, and [[Symptoms#Necrosis|necrosis]] (which causes tissue to die) of any body part can also lead to eventual death, but the usual treatment, amputation, is not much better. If your fortress has many venomous creatures nearby, have some [[coffin]]s ready.

Currently, it is disputed whether or not venom can be administered, but it may still be purchased or sold.

Research has shown that in at least some circumstances, venom and other syndrome-inducing materials can be spattered or covered upon weapons and bolts, which may result in attacks inflicting the related syndromes. {{cite forum|106397}}

Some [[forgotten beast]]s and [[titan]]s are generated with venom, which they can inject through bites or stingers, alternatively covering their bodies entirely or making their [[blood]] toxic.

[[File:venom_snake.jpg|thumb|250px|center|A snake's venom.]]

==See also==
*[[Syndrome]] for a list of various venomous varmints.

{{Translation
| dwarven = zamoth
| elvish = neleni
| goblin = luskon
| human = ámtoc
}}

{{Category|Creature attributes}}
{{Category|Extracts}}
[[ru:Venom]]

DF2014:Symptoms

2020-06-27T07:48:12Z

Albedo: T:DEL - Rule N, singular nouns

{{wrong namespace|Symptom}}

{{av}}{{Quality|Exceptional}}
A '''symptom''' is a status effect most often caused by contracting a [[syndrome]]. They range from mild temporary annoyances to lifelong disabilities to even death if untreated. An affected dwarf will need to be diagnosed at a [[Hospital]] before a treatment can be prescribed.

==Blisters==
'''Effects''': Areas affected become prone to infection, this becomes more and more likely as severity goes up. While harmless in itself, unless in the lungs in which the unlucky dwarf will be unable to breathe, a resulting infection might cause a loss of life or limb if not properly dealt with.

==Bleeding==
'''Effects''': Areas affected will continue to bleed for the duration of the effect and will not taper off like a normal wound. In effect it suggests that whatever caused the wound had an anti-coagulant in the venom. This will quickly cause an affected creature to bleed out if the syndrome is not immediately treated.

==Bruising==
'''Effects''': Causes pain long after the blunt trauma that caused it is over. Even the most severe bruises will heal without intervention, but may hint at fractures under the skin.

==Cough==
'''Effects''': Dwarf will stop and cough occasionally. While nearly harmless by itself severe coughs will sometimes bring up blood. In this case it's a sign of internal hemorrhaging.

==Dizziness==
'''Effects''': Creature might stumble/fall in a random direction when attempting to perform an action (including moving [!!!]). The more severe the dizziness the more likely this is to happen. Beware that stumbling, much like dodging, might end up putting a dwarf in a moat, or chasm, or magma, or off a wall, or falling just enough to land unconscious for a second on a cage trap. The list goes on.

==Drowsiness==
'''Effects''': Creature tires faster than normal and requires more sleep. This can be almost unnoticeable if the severity is low, but results in narcoleptic fits if high.

==Fever==
'''Effects''': Appears to reduce the ability to focus. Intense fevers can also cause stunning. While a fever in itself seems relatively harmless, it's often just the most visible symptom. Feverish dwarfs blink with a red "X".

==Impaired Function==
'''Effects''': Creature will be unable to use affected body parts for the duration. Much of the functionality here is mirrored in swelling, but this allows certain parts (such as organs) that normally can't swell to still cease functioning

==Nausea==
'''Effects''': Creature will stop and [[Vomit]]. How often this happens depends on severity. Sustained and intense vomiting will cause dwarfs to dehydrate.

==Necrosis==
'''Effects''': The affected tissue starts to rot away, which needless to say is a medical emergency. If action isn't quickly taken to remove the tissue (through either surgery or amputation) it will spread throughout the body and may cause [[Health_care#Infection|infection]], killing the creature. Also commonly seen in [[Undead]] creatures.

==Numbness==
'''Effects''': Creature will not be able to feel affected body parts. This makes pain a non-issue, but also hampers their use (I.E. Something with numb hands will find using weapons difficult, something who has a leg that's fallen asleep with have difficulty standing). Prolonged numbness will lead to permanent sensory nerve damage.

==Oozing==
'''Effects''': A sign of infection. Infected areas heal much slower and might kill if especially severe or widespread.

==Pain==
'''Effects''': Creatures that aren't in a martial trance that have pain above a certain level get all their rolls halved. They might give into pain and fall unconscious depending on toughness. This is more likely to happen more often the more severe the pain is, which is usually fatal in combat, since enemies will automatically target the unconscious victim's head with a perfectly accurate, perfectly square strike.

==Paralysis==
'''Effects''': The creature can't move. Severity only decreases the chance of resisting the symptom. Untargeted paralysis often leads to suffocation in smaller creatures, which can include dwarves.

==Swelling==
'''Effects''': Impedes the ability to use affected areas. Normally fairly harmless but can cause death by suffocation if it affects the throat. Prolonged swelling will lead to necrosis.

==Unconsciousness==
'''Effects''': Affected creature will pass out for the duration of this effect, even if the creature isn't in pain or extremely tired.

==Vomiting Blood==
'''Effects''': Much as excessive vomiting can lead to death from dehydration, vomiting blood can lead to death from blood loss. Considered to be a separate condition from coughing blood. If your creature happens to have green blood you'll be unable to tell this from nausea without checking the tiles.

[[ru:DF2012:Symptoms]]

Venom

2020-06-27T07:41:38Z

Albedo: expansion, examples

{{Quality|Superior|05:09, 17 May 2015 (UTC)}}
{{av}}

'''Venom''' is a naturally-occurring poison that will cause a [[syndrome]] in certain creatures when certain conditions are met, typically when entering the [[blood]] via a [[serpent man]] or [[Giant cave spider|giant cave spider bite]]. It is produced by certain creatures according to their [[raw file]], and may be [[extracts|extracted]] and stored in [[vial]]s.

Each specific animal's venom delivers a [[Syndrome#List of syndromes|specific syndrome]], which is a known combination of [[symptoms]], some short term, some long term, and some (in rare cases) permanent (aka "chronic"). Some syndromes (such as [[gila monster]]s') are seen as mild annoyances, some (such as a [[giant desert scorpion]]s') are mortally serious. Of the wide of variety possible symptoms, one of the mildest is [[Symptoms#Nausea|nausea]] and vomiting, but even that can dehydrate a dwarf and take them out of combat while they seek to quench their thirst. The most immediately dangerous venoms cause [[Symptoms#Paralysis|paralysis]], which can stop the lungs, leading to suffocation. Most any bite that causes strong [[Symptoms#Pain|pain]] can in turn cause unconsciousness, leaving the victim helpless in combat, which is often a death sentence by itself. Longer term, [[Symptoms#Blisters|blisters]] can lead to deadly infections, and [[Symptoms#Necrosis|necrosis]] (which causes tissue to die) of any body part can also lead to eventual death, but the usual treatment, amputation, is not much better.

Currently, it is disputed whether or not venom can be administered, but it may still be purchased or sold.

Research has shown that in at least some circumstances, venom and other syndrome-inducing materials can be spattered or covered upon weapons and bolts, which may result in attacks inflicting the related syndromes. {{cite forum|106397}}

Some [[forgotten beast]]s and [[titan]]s are generated with venom, which they can inject through bites or stingers, alternatively covering their bodies entirely or making their [[blood]] toxic.

[[File:venom_snake.jpg|thumb|250px|center|A snake's venom.]]

==See also==
*[[Syndrome]] for a list of various venomous varmints.

{{Translation
| dwarven = zamoth
| elvish = neleni
| goblin = luskon
| human = ámtoc
}}

{{Category|Creature attributes}}
{{Category|Extracts}}
[[ru:Venom]]

DF2014:Symptoms

2020-06-27T07:21:10Z

Albedo: de-capitalize

{{av}}{{Quality|Exceptional}}
A '''symptom''' is a status effect most often caused by contracting a [[syndrome]]. They range from mild temporary annoyances to lifelong disabilities to even death if untreated. An affected dwarf will need to be diagnosed at a [[Hospital]] before a treatment can be prescribed.

==Blisters==
'''Effects''': Areas affected become prone to infection, this becomes more and more likely as severity goes up. While harmless in itself, unless in the lungs in which the unlucky dwarf will be unable to breathe, a resulting infection might cause a loss of life or limb if not properly dealt with.

==Bleeding==
'''Effects''': Areas affected will continue to bleed for the duration of the effect and will not taper off like a normal wound. In effect it suggests that whatever caused the wound had an anti-coagulant in the venom. This will quickly cause an affected creature to bleed out if the syndrome is not immediately treated.

==Bruising==
'''Effects''': Causes pain long after the blunt trauma that caused it is over. Even the most severe bruises will heal without intervention, but may hint at fractures under the skin.

==Cough==
'''Effects''': Dwarf will stop and cough occasionally. While nearly harmless by itself severe coughs will sometimes bring up blood. In this case it's a sign of internal hemorrhaging.

==Dizziness==
'''Effects''': Creature might stumble/fall in a random direction when attempting to perform an action (including moving [!!!]). The more severe the dizziness the more likely this is to happen. Beware that stumbling, much like dodging, might end up putting a dwarf in a moat, or chasm, or magma, or off a wall, or falling just enough to land unconscious for a second on a cage trap. The list goes on.

==Drowsiness==
'''Effects''': Creature tires faster than normal and requires more sleep. This can be almost unnoticeable if the severity is low, but results in narcoleptic fits if high.

==Fever==
'''Effects''': Appears to reduce the ability to focus. Intense fevers can also cause stunning. While a fever in itself seems relatively harmless, it's often just the most visible symptom. Feverish dwarfs blink with a red "X".

==Impaired Function==
'''Effects''': Creature will be unable to use affected body parts for the duration. Much of the functionality here is mirrored in swelling, but this allows certain parts (such as organs) that normally can't swell to still cease functioning

==Nausea==
'''Effects''': Creature will stop and [[Vomit]]. How often this happens depends on severity. Sustained and intense vomiting will cause dwarfs to dehydrate.

==Necrosis==
'''Effects''': The affected tissue starts to rot away, which needless to say is a medical emergency. If action isn't quickly taken to remove the tissue (through either surgery or amputation) it will spread throughout the body and may cause [[Health_care#Infection|infection]], killing the creature. Also commonly seen in [[Undead]] creatures.

==Numbness==
'''Effects''': Creature will not be able to feel affected body parts. This makes pain a non-issue, but also hampers their use (I.E. Something with numb hands will find using weapons difficult, something who has a leg that's fallen asleep with have difficulty standing). Prolonged numbness will lead to permanent sensory nerve damage.

==Oozing==
'''Effects''': A sign of infection. Infected areas heal much slower and might kill if especially severe or widespread.

==Pain==
'''Effects''': Creatures that aren't in a martial trance that have pain above a certain level get all their rolls halved. They might give into pain and fall unconscious depending on toughness. This is more likely to happen more often the more severe the pain is, which is usually fatal in combat, since enemies will automatically target the unconscious victim's head with a perfectly accurate, perfectly square strike.

==Paralysis==
'''Effects''': The creature can't move. Severity only decreases the chance of resisting the symptom. Untargeted paralysis often leads to suffocation in smaller creatures, which can include dwarves.

==Swelling==
'''Effects''': Impedes the ability to use affected areas. Normally fairly harmless but can cause death by suffocation if it affects the throat. Prolonged swelling will lead to necrosis.

==Unconsciousness==
'''Effects''': Affected creature will pass out for the duration of this effect, even if the creature isn't in pain or extremely tired.

==Vomiting Blood==
'''Effects''': Much as excessive vomiting can lead to death from dehydration, vomiting blood can lead to death from blood loss. Considered to be a separate condition from coughing blood. If your creature happens to have green blood you'll be unable to tell this from nausea without checking the tiles.

[[ru:DF2012:Symptoms]]

DF2014:Symptoms

2020-06-27T07:17:25Z

Albedo: /* Paralysis */

{{av}}{{Quality|Exceptional}}
A '''symptom''' is a status effect most often caused by contracting a [[Syndrome]]. They range from mild temporary annoyances to lifelong disabilities to even death if untreated. An affected dwarf will need to be diagnosed at a [[Hospital]] before a treatment can be prescribed.

==Blisters==
'''Effects''': Areas affected become prone to infection, this becomes more and more likely as severity goes up. While harmless in itself, unless in the lungs in which the unlucky dwarf will be unable to breathe, a resulting infection might cause a loss of life or limb if not properly dealt with.

==Bleeding==
'''Effects''': Areas affected will continue to bleed for the duration of the effect and will not taper off like a normal wound. In effect it suggests that whatever caused the wound had an anti-coagulant in the venom. This will quickly cause an affected creature to bleed out if the syndrome is not immediately treated.

==Bruising==
'''Effects''': Causes pain long after the blunt trauma that caused it is over. Even the most severe bruises will heal without intervention, but may hint at fractures under the skin.

==Cough==
'''Effects''': Dwarf will stop and cough occasionally. While nearly harmless by itself severe coughs will sometimes bring up blood. In this case it's a sign of internal hemorrhaging.

==Dizziness==
'''Effects''': Creature might stumble/fall in a random direction when attempting to perform an action (including moving [!!!]). The more severe the dizziness the more likely this is to happen. Beware that stumbling, much like dodging, might end up putting a dwarf in a moat, or chasm, or magma, or off a wall, or falling just enough to land unconscious for a second on a cage trap. The list goes on.

==Drowsiness==
'''Effects''': Creature tires faster than normal and requires more sleep. This can be almost unnoticeable if the severity is low, but results in narcoleptic fits if high.

==Fever==
'''Effects''': Appears to reduce the ability to focus. Intense fevers can also cause stunning. While a fever in itself seems relatively harmless, it's often just the most visible symptom. Feverish dwarfs blink with a red "X".

==Impaired Function==
'''Effects''': Creature will be unable to use affected body parts for the duration. Much of the functionality here is mirrored in swelling, but this allows certain parts (such as organs) that normally can't swell to still cease functioning

==Nausea==
'''Effects''': Creature will stop and [[Vomit]]. How often this happens depends on severity. Sustained and intense vomiting will cause dwarfs to dehydrate.

==Necrosis==
'''Effects''': The affected tissue starts to rot away, which needless to say is a medical emergency. If action isn't quickly taken to remove the tissue (through either surgery or amputation) it will spread throughout the body and may cause [[Health_care#Infection|infection]], killing the creature. Also commonly seen in [[Undead]] creatures.

==Numbness==
'''Effects''': Creature will not be able to feel affected body parts. This makes pain a non-issue, but also hampers their use (I.E. Something with numb hands will find using weapons difficult, something who has a leg that's fallen asleep with have difficulty standing). Prolonged numbness will lead to permanent sensory nerve damage.

==Oozing==
'''Effects''': A sign of infection. Infected areas heal much slower and might kill if especially severe or widespread.

==Pain==
'''Effects''': Creatures that aren't in a martial trance that have pain above a certain level get all their rolls halved. They might give into pain and fall unconscious depending on toughness. This is more likely to happen more often the more severe the pain is, which is usually fatal in combat, since enemies will automatically target the unconscious victim's head with a perfectly accurate, perfectly square strike.

==Paralysis==
'''Effects''': The creature can't move. Severity only decreases the chance of resisting the symptom. Untargeted paralysis often leads to suffocation in smaller creatures, which can include dwarves.

==Swelling==
'''Effects''': Impedes the ability to use affected areas. Normally fairly harmless but can cause death by suffocation if it affects the throat. Prolonged swelling will lead to necrosis.

==Unconsciousness==
'''Effects''': Affected creature will pass out for the duration of this effect, even if the creature isn't in pain or extremely tired.

==Vomiting Blood==
'''Effects''': Much as excessive vomiting can lead to death from dehydration, vomiting blood can lead to death from blood loss. Considered to be a separate condition from coughing blood. If your creature happens to have green blood you'll be unable to tell this from nausea without checking the tiles.

[[ru:DF2012:Symptoms]]

Adder

2020-06-27T05:50:09Z

Albedo: links, short vs. long-term

{{Quality|Exceptional|23:40, 9 October 2014 (UTC)}}
{{Creaturelookup/0
|wiki=Vipera_berus
|skull=1
|contrib=no
}}
{{av}}
:''For logical designs related to the addition of numbers, see [[Adder (Computing)]].''
{{creaturedesc}}

'''Adders''' are [[syndrome|venomous]] [[Creature|snakes]] found in many [[temperate]] [[biome]]s.

Adder bites deliver a [[venom]] that can cause immediate strong [[pain]] followed by long-term (but not permanent) [[syndrome|nausea, blisters, and swelling]]. Though the bite itself is not usually fatal, such pain can cause unconsciousness, which ''can'' lead to fatal complications in combat.

Adders are distinct for being the [[list of creatures by adult size|smallest creatures]] in the game which aren't [[vermin]].

Adders can be captured in [[cage]] [[trap]]s and [[Animal trainer|trained]] into cheap exotic [[pet]]s. They are born adults and as such can't be permanently tamed. [[Butcher]]ing an adder only produces a [[skull]], making them worthless to your [[meat industry]]. Female adders are [[egg]]-layers, producing 3-10 edible eggs with regularity, and providing significantly more food than would be expected from such a small creature.

Some dwarves [[Preferences|like]] adders for their ''warning hisses''.

[[Image:Loch Shin adder.JPG|thumb|center|400px|Admired for its ''warning hisses''.]]

{{gamedata}}
{{Creatures}}
{{Category|Animals}}

User:Albedo

2020-06-27T04:28:12Z

Albedo: /* Crop Rotation */

And again during the Uristid-19 quarantine - Taverns, Shrines, Missions - FUN![[User:Albedo|Albedo]] ([[User talk:Albedo|talk]]) 01:04, 9 June 2020 (UTC)

Back after a 5+ year hiatus - last edit late May of '10. Just catching up to new version atm - we'll see. [[User:Albedo|Albedo]] ([[User talk:Albedo|talk]]) 16:50, 18 June 2015 (UTC)

<hr><hr>

Feb, 2010: I just added my name to the list for '''Asst. Admin''' for this site - see [[Dwarf Fortress Wiki:Request for Adminship/Albedo|here]].

* [[Template:DFtext]]
<hr>

== Gate Scar ==
New (as of 2020 fortress) diary [[User:Albedo/GateScar|here]].

=Beast Whips=

: BeastWhips game diary moved to [[User:Albedo/BeastWhips|here]].

<hr>

=Basic Farming Article=
There was a recent thread titled "seeds" that was hoping to get "world gen seeds" - but [s]it's now[/s] it was slipping toward page 3, before I accidentally bumped it. ::)

Anyway, these were the 2 responses...

I thought you meant strawberry seeds or something. Now I have nothing to contribute :(

Yeah, I was hoping to learn something new about seeds, but alas...

''mmmm... "seeds"... indeed... well, deep on page 2 doesn't look like "world seeds" is taking off... ok, by request of 2 posters, some thoughts on plant seeds and related topics, targeted at a variety of game experience levels. Don't know how much "new" this will be, but I was struck by a strange mood...''

First, let's talk about the planter, your Grower. Plant stack size is based on the Grower doing the planting, not the harvester. A better Grower means fewer seeds are needed to produce the same number of plants, and your farm plots can be smaller, saving irrigated space and keeping farmplots closer to your kitchens/stills/etc ''(which should all be in the same area, and near the Dining Hall - but we digress.)''

With the exception of Quarry Bushes ''(which pad out prepared meals nicely, but usually a food industry is not up to that level in the first couple seasons)'', plants are mostly for booze, at least to start. [i](Later, flours and such - but not at first.)[/i] You can trade, hunt or breed for all the food you need, but the 1st caravan won't bring enough booze, and you shouldn't rely on them later. Booze is the lubricant of a Fortress, and without it will, quite literally, come to a grinding halt. Plants give you your booze, and Growers give you your plants.

If you count all the tasks, from planting to drinking, Grower is THE single most important skill in DF for multiplying its effect on the labour force. A Legendary grower saves something like ''30 tasks for each stack'' of plants that are brewed. Yes, thirty ''per stack'' - it's just absurd. (See the wiki on [[grower]] for a detailed breakdown.)

By embarking with a proficient Grower and with only 3 of each UG* seed type, you will have more seeds than you need for planting later seasons - the multiplier is huge and the demand low. (If you collect them all and destroy none, 3 seeds -> ~8+ next season -> 20+ and you're set unless your plots are larger than that, which is a bit over-enthusiastic unless you only have 1 or 2 crops.)

''(* UnderGround, vs. AG, above ground. You can only buy UG plants and seeds at embark. There are 4 UG booze plants (all are also edible, some can be processed into other food-stuffs), plus Quarry Bushes, plus the non-edible Dimple Cups.)''

While I cannot emphasize how strongly I, personally, recommend starting with a Proficient Grower, it is also true that an unskilled Grower, if set to "Only Farmers Harvest" and with only 25 tiles or so of crops, will train to Proficient easily within a year. But a Proficient will be Legendary in just over a year, and then you're unstoppable. (They'll be Professional or so by the time your first migrants are expected to show, and a single unskilled apprentice back-up Grower (to help w/ harvests) won't crush the production during planting.)

On the flip side, if using unskilled growers, a 1:1 production of seed:plant seem to be the standard, and so replanting at the same scale requires that 100% of the plants are either eaten or brewed with no seeds eaten - no cooking, no eating seeds, no bad luck (harvests of "stack = 0"), or it's a losing proposition. (Smaller plots mean "bad luck" is easier to come across!)

Splitting the diff and putting only ~2-4 ranks into Grower at embark wouldn't be a dealbreaker by any means - ample to avoid "bad luck", and you'll get a few larger stacks for brewing/cooking. (Some micromanagement is necessary to save the larger stacks for processing and only let the smaller ones be eaten raw.)

For newer players, be aware - eating plants leaves seeds, brewing plants leaves seeds, but [u]cooking plants destroys seeds[/u]. This can be controlled in the z-kitchen menu. ((I'll also presume to draw your attention to the fact that cooking seeds also destroys seeds - as does eating seeds. This is usually only a dealbreaker for early fortresses, but it does happen. Forbid some if you want to be paranoid.)

(And while my rambling refers mainly to food-plants, dye-plants work similarly. They are separate from plot-size discussions, as they feed your cloth industry ([u]if[/u] you have one), not your dwarves.)

So, making seeds into more seeds is the job of a Grower, and now we all understand the trade-offs there.

One seed can produce a single stack size of anywhere from 0-5, with larger stacks being reliably produced only by higher skilled Growers. (Also larger if fertilized.)

So, you don't need to start w/ a lot of seeds if you have a Proficient grower. 1 seed will produce a stack of maybe 2-4, on average, so let's call it 2.5 to be on the safe side. At x5 for booze production, that stack will on average become 12.5 booze. That means that 3 seeds should become [i]at least[/i] 7 plants or 35+ booze, which is more than enough to for 8 thirsty dwarfs for a season. That times your 4 different UG plants [i](Pig Tail = ale, D'n Wheat = beer, Sweet Pods = rum, Plump Helmets = wine)[/i] is... well, more than enough. (4x35 = 140 booze/season, which would keep 35 dwarves/season lubricated, plus more from trading.) And that's only 3 seeds for each of 4 crops, with extremely conservative estimates for stack production.

So, starting with 3 seeds each for your 7 dwarfs is ample, even if you're going to let that grow as the fortress does. (If you can get your crops in before the end of the 1st Spring, you're in good shape; before end of 1st Summer can be a bit tight if you have a large migrant wave early.)

Some players do fine with a single 5x5 plot of Plump Helmets* [i](at least for up to 60-100 dwarves, depending on Grower, fertilization, other food sources and Trade)[/i], but dwarves like a variety of booze. Some combination of UG & AG plots that equal around 25-30 tiles (don't count non-food plants) is adequate unless they're going to be trade exports (or you lose your Proficient Grower). That means 2x2 of each is too big if you have a lot of AG crops; 1x3 seems about right w/ your favorites at 2x2, and [i]possibly[/i] some few larger (sun berries, PH's, quarry bushes?). A strip of adjacent plots, w/ some 1x3 sticking out and seed stockpiles placed in the indents for the 2x2 plots works well for me.

(* If you're going with only 1 or 2 crops, spend the 1 dwarfbuck at the start for 1 seed and a free bag for the other crops. But you still really don't need much more than 3 seeds each, as they'll multiply quickly enough, depending on your use of raw plants, and you should be bringing about 60 total booze to last until the 1st caravan, unless you have a personal plan that calls for another approach.)

So, 1x3 or 2x2 each seems a good size for most crops to start, unless you're going to use plant products as trade exports. (Same w/ UG size plots.) 25 tiles total of [u]food[/u]-plant production is "common wisdom". (Don't count plants that produce only dye/etc.)

And since "[[DF2014:Farming#Yield_and_fertilization|fertilzing]]" sees a cutpoint at "size 3" as a cutpoint (next is size 7), let's go with size 3, which also allows some refined customization if you want to tweak the final output one way or another.

:''(At a total footprint of 3x7, this is only 17 tiles of food production, and so while adequate for your 1st 7 this needs either some expanding or some AG food crops to back it up before your fortress grows too big.)''

Seeds are stored in bags - 100/bag max ''(so getting 6 free bags at embark is a good move, but you won't get any more than that''). And then the bags will be set into barrels. If your settings are on "mix food" (<o, m>), then 1 barrel can hold all you need - but you can easily customize your food stockpiles to have no barrels at all. I like to set 1-tile large stockpiles customized to accept only that one seed adjacent to the plots they will serve - makes planting (and visually checking your seed supply) too easy. (While the bags might get wear from being walked on, the seeds won't suffer - put them in hallways if you have to, and/or use <d, o> to set Restricted traffic on them.)

Adding a specific seed stockpile at the end of each row is handy. Note that walking on seeds/farm plots/crops doesn't seem to hurt them, which is not true of wild plants or saplings. Food does not take "wear".

===Crop Rotation===
A glance at the [[Farming#Farm_plots_in_action|time for growth for underground crops]] shows that different crops grow at different rates - Plump Helmets and Pig Tails grow 3x/season, the others 2x*. With 5 fields of size 3 and a dedicated Grower, you can just about balance the 5 UG crops and feed your fortress up to 100 dwarfs very easily.

: (* At least in theory. The time to harvest/replant is '''very''' tight with 84-day seasons (since all months are only 28 days long).)

{| class="wikitable"
|-
|
! Spring
! Summer
! Autumn
! Winter
|-
| Plot #1
| SP x2
| SP x2
| PT x3
| PH x3
|-
| Plot #2
| SP x2
| PT x3
| PT x3
| PH x3
|-
| Plot #3
| SP x2
| CW x2
| CW x2
| PH x3
|-
| Plot #4
| QB x2
| QB x2
| QB x2
| DC* x2
|-
| Plot #5
| QB x2
| CW x2
| CW x2
| DC* x2
|}

: ''Legend: DC = Dimple Cup, CW = Cave Wheat, PH = Plump Helmet, PT = Pig Tail, QB = Quarry Bush, and SP = Sweet Pod.''

: * Dimple Cups are non-edible, but if you want to start your dye industry, toss them in. Otherwise, Plump Helmets are the only other winter UG crop.

Over 4 seasons, the harvests that these plots yield are...
:* 9x Plump Helmets
:* 9x Pig Tails
:* 8x Cave Wheat
:* 8x Sweet Pods
:* 8x Quarry Bushes
:* 4x Dimple Cups (dye only)

I like to send a quick, large wave of unskilled Plant Gathering out early in the game, 1st Spring or Summer (once everything is nearly underground but before real trouble shows up), to get a nice selection of AG plants, and then brew those up (or forbid all other foods and let them get eaten first) to get the seeds asap for a Summer planting.

Cooking with seeds is a great way to get rid of them in later game as they start to reach triple digits each, but turn off all "cook" orders early on (again, in the z-kitchen menu). This is critical with newly acquired plants/seeds (from Plant Gathering or Trade), as otherwise your Cook might decide a SunBerry Seed Roast is just the ticket. Oh noes.

There. I've probably mispoken somewhere, so I trust the veterans will come along and rub my nose in it and correct me. And/or suggest valid alternatives, and invited to do so - a complete discussion was my goal.

I also have made some strong personal recommendations that are just that - my personal opinion, no apologies. There are many ways to approach DF, and to have fun (in all its forms) - this is just one solid way to get there from here.

= Next Fort =
Beastwhips (see section & link near top of this page) was many versions ago, and this next effort calls for a more refined approach. So, to that end...

(EDITOR'S UPDATE: This is from about 2013, so a LOT of the details are out of date - and in DF, the devil is, indeed, in the details. e.g., Silver is not longer the rough equiv of iron/steel for blunt weapons, etc. etc. etc.

As a result of this edit, the below is now a combo of my most recent beliefs and the original record.)

==Starting Seven==
(updated for 2020)
Screened my original seven slightly, tossing out the first couple groups - no cat lovers, no real slackers, no serious over-indulgers or quitters. Very diff than before, switching several secondary skills, both in choice and pairing.

(Edit - this is not the original BeastWhips 7, but closer to my current (2020) layout.)

The party now consists of the following:

:* 1) "'''Boss Axe'''": Axe +4, Armor User +5, Discipline 1
:* 2) "Dirty" '''Grower''' +5/Glassmaker 5 (or Wrestler 3/Discipline 2?) (or ???)
:* 3) "Stoney" '''Mason''' +5/Stonecrafter +4 (or ???)
:* 4) "Cutter" '''Weaponsmith''' +5/Brewer +3/Appraise +1, Judge of Intent +1 (or ???)
:* 5) "Hardpan" '''Armorsmith''' +5/Cook +5
:* 6) "Cagey" '''Mechanic''' +5/Carpenter +5
:* 7) "Striker" '''Miner''' +5/Armor User +5 (or ???)

:Notes:
(& see [[Sample Starting Builds#Albedo's 7]])

:: 1) '''Boss Axe''': Leader/Security, misc. (non-Moodable) tasks, hauler. Essentially a dedicated hauler to start, also our Trader and early fast-reaction force. He'll also train the dogs early, and cover most misc. skilled jobs like Woodcutting, Furnace operator and Record Keeper. This is my 1-dwarf "starting military"; activate Woodcutting to keep his axe in his hand. Hopefully on a dwarf with high social inclinations and no preferences for any "item". Early on, task him to forge another pick for the fortress, and so get Weaponsmith as his moodable skill.

:: (Note: Go Axe 3/Discipline 2 if expecting undead)

:: 2) '''Dirty''': Non-Hauler. This is partly a "wildcard" - he'll be THE Grower 24/7 until/unless a better replacement migrates in (and maybe even still then), so he shouldn't be given anything that will demand his time early on. Grower 5 will take 2 starting seeds of each and turn them into more than I need by the end of the 1st year.

:: Dealer's choice on the 2nd skill. He could take "nothing" and save the embark points He could take Wrestler (3-5), enough to keep him alive if he gets ambushed while outdoor farming, possibly coupled with enough Discipline not to fall apart at the sight of dead bodies. I chose a moodable skill that he can change to once a capable Grower migrates in to replace him. However, this should be something that can, indeed, wait until that time, and not something that will take time away from growing early on.

::: (Any or all of the four "(or ???)" skills could be any rarely-needed, low time-drain skill(s), something until Migrants can do better. Or, if that dwarf has a useful [[Preference]], take that skill @ 5 and plan to change careers once any decent Grower migrates in (and hope to get that new skill dominant for Moods). Or plan for more starting military - Crossbow 5 or Armor User 5 (or Weapon 1/Armor 4 - "mace" is probably the best all-around weapon, esp vs. undead). Or just save the points and buy another war dog. Whatever works for you. For me, Wrestler is for unpleasant surprises when farming outside, and ''in extremis'' as backup starting military. The miner will shift to military once he has his replacement.)

:: 3) '''Stoney''': Semi-hauler, to-start only. Stonecraft mugs for the Caravan. Plus, a few nice ☼mugs☼ for the Tavern couldn't hurt. Important to keep Mason skill > Stonecraft in case of moods - the goal is an artifact coffin, statue or throne, not a jug or hive. This means little or no early hauling - if he's not making furniture or constructing buildings, he's making blocks for practice and fortress expansion. Mug production starts sometime mid-Summer (or start of Summer if no skill). Often has more than a few each of Mason's and Cratdwarf's workshops cluttered before the Caravan arrives, just because early on it's faster to build new ones ''(in the middle of a stone field)'' than to haul/store everything.

:: 4 & 5) '''Cutter''' & '''Hardpan''': (Initial Haulers, both.) One moodable skill w/ one non-moodable that we don't have to worry about. There are 2 reasons for starting with a high skill - quality or speed. Both Brewer/Cook 5 means they can spend less time away from what's important, and high-quality meals can be used for their trade values (and eventually keep dwarves happier). Brewer 3 is almost as good on speed and saves 17 embark points - 5 more bituminous coal, pls, tysvm.

:: 6) '''Cagey''': (Initial Hauler.) Necessary wooden products (beds, buckets, etc.) will mostly be meh-quality until a better replacement migrates in, but something adequate to start.

:: 7) '''Striker''': No Hauling, the fortress needs a 24/7 miner from the start. I like [[ballista]]e, but they're not for everyone, admittedly. And while you could start with no Miner and train one up to 4-5 in about 1 season (especially in [[soil]]), starting with a 5 means he strikes the earth with alacrity and purpose, going through soil like magma through an elf - which is critical early on to create quick space underground. He gets some stat boosts by the time he makes Legendary, trains up some replacements, then gets transferred to the military once a couple/few migrants can take his place. SE is tough to skill up - or, that skill could as easily be any Military skill(s) for military dwarf #2 (Mace 1, Armor 4?).

::''(Any other personal preferences/likes are, well, pretty much dull and pointless. Squares. Trumpets. Siliceous ooze. Yay.)''

:: ''(These skill mixes were chosen with an eye to several factors, including future possible [[mood]]s, time-demands of skills, and when the skill would be needed in the fortress (sooner vs. later). For me, for my priorities and gamestyle, I like this mix far better than other, more conventional choices.)''

For the start, the Leader/Axedwarf will add in unskilled Woodcutter, Herbalist and Animal Trainer, and cover all the outdoor duties with a few wardogs in tow (until they're assigned elsewhere). The Miner will do nothing else but mine, all hauling turned off until they're legendary (which will be fast enough), and will be some early reserve military with those increased attributes. Almost everyone else will be Furnace Operators, to cover that as it comes up, and almost everyone except the Cook will be a Butcher/Tanner, to cover those duties asap before anything rots (the cook will cook what's butchered, not unspurprisingly). The Weaponsmith/Lthrwrkr will add Carpenter, and cover those duties as well for now - gotta make sure they maintain "Weaponsmith" as a profession, for any mood.

The Mason/Stonecrafter will have their hands full at first, and I know I'll sometimes wish they were two separate dwarfs (been there before with this mix), but, after a few caravans, stonecrafts will only take a few weeks out of the year, and at some point a mood will create a legendary one while this dwarf concentrates on keeping Mason > Stonecraft in case a mood strikes.

The 2nd half of the Grower/X* is a ''"fill in this blank" ''. Armor User is harder to train than Wrestler or Dodge, and any collection of Medical skills is a joke - but ultimately dealer's choice. Even odds whether this Grower or some random migrant will have a better Grower score, so a "production" skill means he's not completely tied to agriculture if he wants to change careers and someone (almost) as good/better comes along.

: ''(* In a previous incarnation of this embark profile, this was a Grower/Gemsetter. For me, Gemsetter was a long-term plan once the [[glass industry]] was up and running.)''

==In the wagon==

I intend to '''[[Make your own weapons|DIY]]''' my own axe for woodcutting and defense, out of bronze, plus a second pick. Bronze is about +33% better in combat than copper and actually takes less fuel (8 bars/1 fuel!). The rest is for moods, and because Bismuth Bronze costs the same # of embark points as regular Bronze ''(a bit more time and fuel)'', but is worth 20% more.

And I have no shame in exploiting the "1 free container for 1 unit" rule. ymmv.

Provisions chosen include:
:* 1 anvil (@ 100/)
:* 1 copper pick (@ 44/)
= 144

:* 4 dogs (@ 16/) ''(not wardogs, just "dogs". 1 male, 3 females. Keep male safe, hope he's not a genetic loser)''
:* 2 cats (@ 11/) ''(to intentionally breed for leather, meat & bones)''
:* 3 sheep (@ 51/) ''(rejected as too expensive. Hope can trade for same later)''
:* 4 rabbits (@ 2/) ''(1 male. Yes, watch-bunnies and bait animals; altho' cavies would suffice. Be afraid.)''
= 94

:* 5 jet stones (@ 3/) ''(lightest fire-safe stone, for early workshops* etc. while digging in dirt. When made into 20 blocks, this will cover all early shops/etc.)''
:* 4 petrified wood (@ 3/) ''(for immediate fire-safe workshops*, and (later) guaranteed magma-safe mechanisms/etc.; lightest of magma-safe stones. Also bright red.)''
:* 2 cinnabar (@ 3/) ''(heaviest common stone - just because. Nice early "welcome" door prize.)''
= 33

:: ''(* Kitchen, Still, Carpenter, Butcher & Tanner, and Furnace, Smelter & Forge... Anything else can be made of nearby stone once that becomes available.)''

Okay...

: 1 Suit of metal* armour requires...
:: Bars
:: 1 : Helm
:: 3 : Breastplate ''(or 2 for chain mail)''
:: 1 : Gauntlets
:: 2 : Greaves ''(not needed if use chain!)''
:: 1 : High Boots
:: '''8 bars total/full suit'''

::: (* Leather for armor is more expensive than ore for bronze. Only consider if expect to need ''immediate'' armor.)

: 2(-3) suits should be good to start, with a couple/few more later...

: 1 Copper ore + 1 Cassiterite (tin) ore = 8 Bronze bars
:: ''That's 1 suit, or 8 misc. items (picks, weapons, chains, whatever). (The axe comes first, obviously, for woodcutting and immediate defense. And a bronze pick too, in case miner needs to join in, and/or we need a 2nd miner. And a crossbow and bolts. And... )''

: 2 Tetrahedrite =
:: 8 copper bars + ~1-2 silver bars.
:: 8 copper bars + 4 Tin bars + 4 Bismuth bars = 16 Bismuth Bronze bars

: That's 2 more (fancier!) suits once Armorsmith gets skilled up a bit.
: Plus a silver hammer* or two ''(rough equiv of steel for hammers)''
:: (* Maces are better vs. undead)
: Good bronze axe (2? or wait for steel?)
: 2 crossbows ''(of any metal - silver is better to beat on stuff with?)''
:: & bolts (bronze)

:* 4 copper ore (@ 6/) ''(= easy 32 bronze bars)''
:* 2(?) tetrahedrite (@ 9/) ''(copper + silver %)''
:* 7 cassiterite (@ 6/) ''(above, +1-2 for moods/etc.)''
:* 3 bismuthinite (@ 3/) ''( " )''
:* 3 garnierite (@ 6/) ''(Nickel, for moods/etc.)''
:* 3 sphalerite (@ 6/) ''(Zinc, for moods/etc.)''
:* 2 iron ore (@ 24/) ''(1 ore = 4 steel, for 2 axes & 1st suit (steel) armor)''
:* 8 (flux stone) (@ 3/) ''(use 4 w/ above 2 iron; hope to find more for 2nd suit)''
:* 20++ bituminous coal (@ 3/)
= 201+?

:* 3 lye (@ 2/) ''(for soap)''
:* 3 gypsum plaster powder (@ 3/) ''(for 3 casts)''
:* 30 sand (6 each @ 1/, x5?) ''(the sand itself is convenient, but the bags are the 1/ target)''
:* 3-6 leather (@ 5/) ''(2-4 quivers, 3-6 waterskins; anything else can wait. I chose "dog" leather on my saved /embark list, because I have faith it will be there. Dog soldiers ftw.)''
:* ? 12 lightweight wood (@ 3/) ''(For training room walls/floors/etc. Depends on map & biome. Featherwood 100 (good), Papaya 130 (tropical), Candlenut 140 (tropical forest), Kapok 260 (Tropical Moist Broadleaf Forest), then...Willow 390, etc.)''
= ~96

Total 9 seeds (@ 1/)
:* 2 seeds for quarry bushes
:* 2 seeds each of cave wheat, pig tails & sweet pods
:* 1 seed for dimple cups ''(no rush, wait until Grower skill improves)''
= 17

:* 5x Plump Helmets (for fast wine. Get seeds = brew!)
:* 2x each seeds Cave Wheat, Sweet Pod, Pig Tail, Quarry bush
:* 1x seed for Dimple Cup (dye)

:* 6x Dwarven Wine (more brewed asap)
:* +38x total Dwarven Ale, D'n Beer, & D'n Rum
::: (16, 11, 11, based on favorite preference for the starting 7)

:* 1 each milk (@ 1/) ''(will become cheese, then meals)''
:* 1 each of every available brewable vegie that costs 2/ ''(for more and different booze)''
:* & then 1 each of every available fish/meat/vegie/egg that costs 2/ (or more if any left).
= the rest of it...

== to do ==

Weaponsmith priority - Wood Furnace, Smelter, Metalsmith Forge.

Working backwards, to brew Plump Helmets, need 6 barrels free. That requires 2 elaborate meals to be cooked ASAP. Kitchen + Still.

Dead animals -> Butcher, Tanner, (& Leatherworker) (Ashery & Soap)

Mason x#! (Stonecrafter x#!)

Cheese -> Farmer's Workshop. Quern.

Mechanic's x#

Food inside, farm plots (UG & AG) and storage, + eventual dining room etc.

Quick meeting room.

Caravan entry, goblin "shortcuts" g ^^^ g

= Density Table =
sandbox, work in progress

Dolomite

2020-06-27T02:50:14Z

Albedo:

{{Quality|Exceptional|20:09, 9 May 2015 (UTC)}}
{{layerlookup/0}}{{av}}

'''Dolomite''' is a [[color|white]] medium-[[value]] and economic type of [[sedimentary layer|sedimentary]] [[stone]] that forms entire layers. It is also a [[flux]] stone, meaning it can be used in the production of [[pig iron]] and [[steel]]. Additionally, it is [[magma safe]], with an extremely high melting point of {{ct|16507}}.

In fact, dolomite has the highest [[Temperature#Melting point|melting point]] of all common* stones and metals. It is not safe from the scorching {{ct|50000}} heat of [[dragon]] fire, though it will last longer than most minerals.

(* The uncommon exceptions being [[raw adamantine]] ore, [[adamantine]] metal, and, because it cannot be melted, [[slade]].)

Because of its abundance and utility, dolomite is one of the most remarkable non-[[ore]] stones, and is much more useful than many other flux stones.

Dolomite is slightly denser than the average rock, inhibiting [[hauling]]. Because of its status as a flux stone, which are in high demand in [[steel]]-making, [[wheelbarrow]]s are useful for the transport of dolomite.

==In real life==

Dolomite is comprised of calcium magnesium carbonate (CaMg(CO3)2) and is related to [[limestone]], [[chalk]], and [[marble]]. Its ionic and crystalline nature contributes to its high melting point. It's dolomite, baby!

[[File:Dolomit - panoramio.jpg|center|thumb|250px|Dolomite.]]

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

Dolomite

2020-06-27T02:49:20Z

Albedo:

{{Quality|Exceptional|20:09, 9 May 2015 (UTC)}}
{{layerlookup/0}}{{av}}

'''Dolomite''' is a [[color|white]] medium-[[value]] and economic type of [[sedimentary layer|sedimentary]] [[stone]] that forms entire layers. It is also a [[flux]] stone, meaning it can be used in the production of [[pig iron]] and [[steel]]. Additionally, it is [[magma safe]], with an extremely high melting point of {{ct|16,507}}.

In fact, dolomite has the highest [[Temperature#Melting point|melting point]] of all common* stones and metals. It is not safe from the scorching {{ct|50,000}} heat of [[dragon]] fire, though it will last longer than most minerals.

(* The uncommon exceptions being [[raw adamantine]] ore, [[adamantine]] metal, and, because it cannot be melted, [[slade]].)

Because of its abundance and utility, dolomite is one of the most remarkable non-[[ore]] stones, and is much more useful than many other flux stones.

Dolomite is slightly denser than the average rock, inhibiting [[hauling]]. Because of its status as a flux stone, which are in high demand in [[steel]]-making, [[wheelbarrow]]s are useful for the transport of dolomite.

==In real life==

Dolomite is comprised of calcium magnesium carbonate (CaMg(CO3)2) and is related to [[limestone]], [[chalk]], and [[marble]]. Its ionic and crystalline nature contributes to its high melting point. It's dolomite, baby!

[[File:Dolomit - panoramio.jpg|center|thumb|250px|Dolomite.]]

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

Dolomite

2020-06-27T02:48:49Z

Albedo: tighten; remove off-topic tangent, material covered elsewhere

Steel

2020-06-26T18:49:46Z

Albedo:

{{Quality|Exceptional|20:56, 20 September 2016 (UTC)}}
{{Alloy3
|name=Steel
|color=0:7:1
|color1=0:0:1
|color2=0:0:1
|color3=7:0:1
|tile3=•
|uses=
* [[weapon|Melee Weapons]]
* [[Crossbow]]s
* [[Bolt]]s
* [[Pick]]s
* [[Armor]]
* [[Anvil]]
* [[Metalsmith's forge|Metal crafting]]
|recipe=
* 1 [[iron]] [[bar]]
* 1 [[pig iron]] [[bar]]
* 1 [[flux]] [[stone]]
* 1 [[fuel|coal]] [[bar]]
|properties=
* [[Material value]] 30
{{firemagmasafe|yes|yes}}
* [[Melting point]] {{ct|12718}}
* [[Boiling point]] {{ct|14968}}
* [[Ignition point]] none
* [[Solid density]] 7850
* Liquid [[density]] 6980
* [[Specific heat]] 500
}}{{av}}

'''Steel''' is an [[alloy]] of [[iron]] and carbon ([[fuel|refined coal]]), made at a smelter. It is the best common metal for smithing most [[weapon]]s and [[armor]]. Steel also has the third highest value of all metals, tied with that of [[gold]].

Steel can be created at a [[smelter]] by a [[dwarf]] with the [[furnace operator]] [[labor]] activated.

==Sedimentary layers==

To smelt steel, you will need [[iron]] [[bar]]s, [[flux]] stone, and [[fuel]]. Flux is used to remove impurities, including carbon, during the smelting process, while fuel (charcoal or coke) removes oxygen and puts back in a small amount of carbon. The end result is steel: iron with just the right amount of carbon in it. The three ores of iron (hematite, magnetite, and limonite) can only be found in [[sedimentary layer]]s, with the exception of hematite, which can occasionally be found in igneous extrusive layers. Furthermore, four of the five [[flux]] stones (calcite, chalk, dolomite, and limestone) are found only in sedimentary layers, as well as both [[coal]] ores (bituminous coal and lignite).

If you have no sedimentary layers at your fortress site, your only hope to make steel is with:
* hematite from [[igneous extrusive]] layers, or iron ore imported from [[trade]] caravans, or [[melt]]ing iron items brought by [[siege]]rs ([[goblinite]]) and caravans
* marble from [[metamorphic]] layers, or imported [[flux]]
* [[charcoal]] from [[wood]], or coke from imported [[bituminous coal]] or [[lignite]]

If you embark in a forest [[biome]], you can produce thousands of units of wood from the surface trees alone, without even tapping into the [[cavern]]s. Charcoal requires more labor per unit than coke, but is often easier to acquire.

Note that bituminous coal and lignite, like most stones, cost only 3☼ at embark or from caravans. With [[Sample_Starting_Builds#Minmax_build|a cunning-enough starting build]], it is possible to embark with enough coal boulders to produce several hundred units of coke, but only if your parent [[civilization]] has access to coal; otherwise, it will not be available at all.

==Recipe==


Steel production is fairly complex compared to the creation of other [[alloy]]s, which only involves one step to combine bars of different pure [[metal]]s to create the final product. Steelmaking from iron bars* has 2 steps, and both steps require coke or charcoal ''as part of the actual reaction'', combining that "[[fuel]]" with the other ingredients. This is required ''in addition'' to any heating source, if using a non-magma smelter (full details below).

: ''(* If starting from iron ''[[ore]]'', you will first need to create iron bars. Steel (or Pig Iron) cannot be created directly from ore. 1 ore creates 4 bars, but the recipe only requires 2 at a time.)''

'''Recipe:''' 
Necessary ingredients; produces '''2 bars of steel''':
:* 2 bars [[iron]]1
:* 2 units [[flux]]2
:* 4 units of [[fuel]] (or only 2 if magma powered)3

: Notes:
:: 1) Unless you are using a [[magma smelter]], melting iron [[ore]] to create iron bars also requires +1 unit of fuel at a conventional ('''non'''-[[magma smelter|magma]]) [[smelter]], producing a total of 4 bars of iron, twice what the recipe uses. This translates to also needing "half a unit" of additional fuel to the ingredients above for each recipe. Since you cannot use "half a unit", you will need a full unit up front, producing 4 iron bars to start, so add that in to any larger, long-term calculations for ore -> steel.
:: 2) [[Calcite]], [[Chalk]], [[Dolomite]], [[Limestone]], and/or [[Marble]]
:: 3) For larger production runs, if using a '''non'''-[[magma smelter]], you may also have to create more fuel. This means either burning wood at a [[wood furnace]], or using 1 fuel to turn [[bituminous coal]] into +8 fuel each or [[lignite]] into +4 fuel each. Add this to any larger, long-term calculations for steel production. (Read: Don't get caught short, and don't consume your very last fuel without a way of producing more!)
[[Image:SteelSword.png|thumb|right|200px|''A [[steel]] [[short sword]].'']]
'''Step 1:''' Use one iron bar to '''create [[pig iron]]''':

:* 1 bar of [[iron]]
:* 1 [[flux]] stone
:* 1 unit of [[fuel]] (as a source of carbon)
:* 1 unit of fuel, or magma (to heat the forge)
: '''Produces''':
:* 1 bar of pig iron

'''Step 2:''' Combine the pig iron bar with the second iron bar to '''produce steel''':

:* 1 bar of iron
:* 1 bar of pig iron
:* 1 [[flux]] stone
:* 1 unit of fuel (as a source of carbon)
:* 1 unit of fuel, or magma (to heat the forge)
: '''Produces''':
:: '''2 bars of steel'''

To go from raw materials to finished products (assuming 1 bar per crafted item) at a conventional forge, a total of...
* 8 iron bearing ore (= 32 iron bars)
* 32 flux stone
* 13 bituminous coal (or 26 lignite or 104 logs)
... will have no leftover raw material and will yield '''32''' single-bar steel items. This is assuming, of course, that your dwarves can time travel and use the last remaining piece of coke to fire the [[furnace]] to create the first [[fuel]] to get things rolling.
[[File:SteelChart.png|center|450px]]


==Automated steel production==

You can fully automate the production of steel via the use of a [[work order]]. The arrangement of these orders would be:

:*Make 9 [[coke]] from [[bituminous coal]] (or 18 [[lignite]], or make 72 [[charcoal]]), then add the {{K|c}}ondition to restart if completed, checked daily.
:*Smelt 8 [[magnetite]] ''(or [[hematite]] or [[limonite]])'' [[ore]], then add the {{K|c}}ondition to restart if completed, checked daily. then set the {{K|o}}rder condition to "Make 9 [[coke]] from [[bituminous coal]]"
:*Make 16 pig iron bars, then add the {{K|c}}ondition to restart if completed, checked daily. then set the {{K|o}}rder condition to "Smelt 8 magnetite ''(or etc.)'' ores"
:*Make 16 steel bars, then add the {{K|c}}ondition to restart if completed, checked daily. then set the {{K|o}}rder condition to "Make 16 pig iron bars"
:*Wait until the "Smelt 8 magnetite" order activates (once the coke or charcoal is done) to set it's{{K|o}}rder to "Make 16 steel bars"

This automated process would produce 32 steel bars every 4 days, assuming you have an adequate flow of ore, coke-producing stone, flux stone and labourers. You can also make multiple work order sets to increase production as much as necessary.

==Planned Steel Production==
It is always recommended to have more [[iron]] bars than [[pig iron]] bars because, supposing you have an abundance of [[charcoal]]/[[coke]] and [[flux]], you can always turn iron into pig iron, but not vice versa. In a fortress with only a limited number of iron bars and pig iron bars, you want to plan the two steps of steel production to maximize the steel bar yield:
* Step 1: Make pig iron bars, but also leave enough iron bars available for step 2 of the steel bar production
* Step 2: Have iron bars and pig iron bars in ratio 1:1, process them into steel bars

===Questions===
* How many pig iron job orders should be issued to result in a 1:1 iron to pig iron ratio?
* How many steel bars can be optimally produced from all this?

===General formulas===
Variables:
''i'': number of available iron bars
''p'': number of available pig iron bars

Formula for stage 1, pig iron production plan:

''j'': job orders for pig iron production to be issued
''j'' = (''i'' – ''p'')/2 (round down for iron surplus, or up for pig iron surplus)

It is recommended to round down for iron surplus. Should need arise, an iron bar can be forged into a [[weapon]], whereas a pig iron bar cannot.

Formula for the potential steel bar yield:

''s'': number of potential steel bars
''s'' = 2 * (round_down(''j'') + p)

===Example===
'''Question:'''

If I have 32 iron bars and 8 pig iron bars, how many steel bars can I produce from this and how? (Presupposing an abundance of [[flux]] and [[fuel]])

'''Current stocks:'''
* 32 iron bars
* 8 pig iron bars
''i'' = 32
''p'' = 8

'''Calculation:'''

Formula for pig iron job orders, (where ''i'' > ''p''):

''j'' = (''i'' – ''p'')/2
''j'' = (32 – 8)/2
''j'' = 24/2

''j'' = 12 (rounded down)

Formula for expected steel bar yield:

''s'' = 2 * (round_down(''j'') + p)
''s'' = 2 * (12 + 8)
''s'' = 2 * 20

''s'' = 40

This can also be calculated from the initial amounts:

''s'' = ''i'' + ''p'' rounded down to the closest even number

'''Answer:'''

From 32 iron bars and 8 pig iron bars, 40 steel bars can be produced. Here is how:

'''Plan:'''
* Stage 1: Issue 12 job orders to make pig iron bars. This will turn 12 iron bars into 12 pig iron bars. 20 of our original 32 iron bars will remain. 12 new pig iron bars are produced, increasing pig iron bar stocks from 8 to 20.
* Stage 2: After stage 1 is completed, we will have 20 iron bars and 20 pig iron bars. We issue 20 job orders to make steel bars (each job order will produce two steel bars).
* Result: 40 new steel bars, 0 iron bars, 0 pig iron bars left unused.
Note: 10 metal bars can produce a full set of [[armor]] and a [[weapon]] for one [[soldier]].

===Simplification, rule of thumb===
If there are at least 20 iron bars more than pig iron bars, issue a job order to make 10 [[pig iron]] bars. If not, issue job orders to make steel bars, as many as there are pig iron bars.

{{Translation
| dwarven = deler
| elvish = inire
| goblin = zodsto
| human = kadest
}}

{{gamedata}}
{{metals}}

Magma

2020-06-26T18:02:15Z

Albedo: /* Minecarts */ copy edit

{{av}}{{Quality|Exceptional|21:13, 6 July 2010 (UTC)}}
[[File:magma_flow.gif|thumb|320px|right|Dwarves can swim in magma, but only once.]]'''Magma''' is red-hot [[fluid|molten rock]] that wells up from deep within the earth (but not so deep that it cannot be found by dwarves), entering the map either by the edges or by the area beneath a [[magma pool]]. Magma that emerges aboveground is called '''Lava'''; however the substance itself remains the same. Magma is very [[Fun]].

Magma serves as a heat source, replacing [[fuel]] in [[magma smelter]]s, [[magma forge]]s, [[magma glass furnace]]s, and [[magma kiln]]s. Magma is ''extremely'' hot, which can lead to even more [[Fun]]. Materials that can withstand the temperature of magma are called '''[[magma-safe]]''', and the list is rather extensive.

Magma never cools, but can [[Water#Evaporation|evaporate]] if left at a depth of 1/7 for long enough, much like water. When magma is mixed with water, it forms [[obsidian]] (and [[steam]]). Note that magma located above [[semi-molten rock]] will be listed as a Magma Flow; magma in magma flow tiles will disappear when mixed with water (instead of cooling into obsidian).

Without [[screw pump]]s to impart [[pressure]], magma flows rather slowly (though no more slowly than unpressurized water). A pipe to bring magma across the full map can take as much as a year to fill. This, combined with the fact that it will evaporate, can make filling a reservoir difficult and tedious. As a rule of thumb, the area coming out of a 1-wide-pipe shouldn't be more than three squares wide and 20 squares long, or else it will evaporate as fast as you fill it.

Some fire-based [[creature]]s make magma their home, or are just simply immune to it.

==Magma sources==

Magma occurs in several different geological formations:
===[[Magma pool]]s===
[[File:magma_preview.png|frame|120px|right|Not-so-lucky 7's.]]Although the name suggests them as pools, they are more like pipes. They can be found underground, however they rarely reach the upper z-levels (40+). Most end a few z-levels above the magma sea, though some may span more than 100 z-levels.
Magma pools seem to be always connected to a magma sea, and the sea and pipe can occasionally reach up to the same level, making them hard to separate. However, magma pools can be identified by the obsidian walls which surround them.
Magma pools will slowly refill themselves, giving the player an infinite source of magma. The entire embark tile containing the pool will produce sporadic bursts of magma until the magma within it is at its natural level (i.e. the magma level at embark) or until it is halted by a bridge, floor, or bottom of a wall.

===[[Volcano]]es===
Volcanoes are magma pools that extend all the way to the surface. Volcanoes are an endless source of magma as they will always refill themselves. They never erupt, unlike their real-life counterparts. Volcanoes are geographical features visible on the [[location]] screen, making them much easier to find when choosing a site for your fortress.

===[[Magma sea]]===
The magma sea is a large body of magma deep under the earth. Nearly all maps will include a magma sea at the lowest z-levels, though its inconvenient placement may inspire your dwarves to [[#Bringing Magma Up|bring the magma up]] to the fortress proper.

== Finding magma ==

Nearly all maps will have magma available at the lowest z-levels, but it can be advantageous to select a site with a more easily accessible source, particularly when starting out.

Volcanoes are visible on the "local" screen in the starting location chooser as a red ≈ - essentially, red water - and on the "region" screen as a red ^. Note that a red ≈ on the "region" screen mean something different entirely (red sand).

After you have chosen to embark in a place that has a volcano, and once your dwarves have arrived at their target destination, you should see a large red pool of lava on your map. If you don't, you should expect your volcano to be somewhere underground. You then have to use [[exploratory mining]] to find it. If you can find a large patch of obsidian on the surface that is devoid of boulders, chances are there is a magma vent below, so that would be a good place to start your mining.

Much harder than simply finding a volcano is finding a volcano that is also near suitable terrain for building. Depending on your requirements - you may be looking for a source of running [[water]], or a [[mountain]] for minerals, or a healthy [[tree]] population, a layer of [[flux]] for [[steel]] production or even all four - suitable building sites can be extremely scarce.

==Working with magma==

Although magma is a liquid, it does not move via [[pressure]] unless it has been pumped. This reduced rate of flow can allow miners to survive digging into a magma reservoir, ''if'' they are lucky enough. There are ways to minimize this risk however:

'''Digging From Above:'''
If you can find a suitable position above the magma, your miner can dig a [[channel]] while remaining above the level of the magma. Be warned, however, that your dwarves might take the ramp down into the magma channel as a shortcut; preemptively designating the channel for restricted [[traffic]] is recommended.

'''Diagonal Digging:'''
Magma moves more slowly diagonally than orthogonally, giving the miner more time to escape. However, slower flow means you must keep in mind the evaporation. You should dig a smaller channel, wait for it to fill up, and extends the channel by Digging From Above. Workers that dig into a magma reservoir are not instantly killed as the magma touches them, but they are set on fire, which will kill them very quickly. For this reason, taking steps to ensure there is adequate water available to extinguish flaming dwarves running in random directions is advised before digging into any magma pools from the side. Channeling a single square wide pit across the planned magma pipe one tile away from the wall to breach and filling it with 2/7 water using the [[Activity zone#Pit/Pond|pond zone]] tool is recommended, so the panicking dwarves have no choice but to run through the water, and the water itself turns into an obsidian wall as soon as the magma flows into it.

'''Busy To Leave:'''
{{F|111883|(see forum)}}
Dwarves who dig into magma often die not because they are unable to flee but because they choose not to. By ensuring a dwarf has another task waiting (ideally far away) they will immediately move away from the ensuing magma flow.

Simply mine up to the corner of a lava tube and then smooth the last tile. Dig a staircase within a few tiles of the place where you will be breaching that leads up and back into your fortress, this will allow your dwarf to get out before the magma gets him. Now designate the smoothed corner to be carved into a fortification. Now immediately when the dwarf begins to carve the fortification, (and this is the most important part!), designate a bunch of other tiles to be smoothed/carved. It's not important that your dwarves actually smooth, carve, or engrave those tiles, what is important is that your dwarf immediately takes another smooth/carve/engrave task elsewhere in the fortress when they finish the current one. If they do not then they will pause for the briefest of instants as they pick a new task, resulting in their death. If they have the job though, they will instantly turn and head up the staircase, stopping the magma from catching and killing them."

'''Exploit From Below:'''
{{F|110724|(see forum)}}
Miners are able to mine out tiles diagonally above them '''even if there is a bridge over their heads'''. First you dig out your magma tunnel to feed magma to wherever in your fort you need it and dig it right up against the volcano pipe. Then you channel a trench against the pipe that can be the width of the tunnel if you wish. Build a magma-safe bridge over the trench, making sure to cover it completely, and then seal off access to the magma tunnel. Dig a new separate path to access the now bridged-over trench. Finally, designate the magma wall '''on the Z level of the magma tunnel''' for mining. Your dwarves will stand in the trench beneath the bridge but will somehow still mine out the squares diagonally above them, causing the magma to flow safely onto the bridge leaving your dwarves unscathed."

Example (use {{k|<}}{{k|>}} to navigate):
<diagram>
<frame type="level" level="0">
Z=0
[%205][%205][%205][%205][%205]╗[#F00]≈≈≈[#]
....[#080]╥[#000][@880][%186][@][#F00]≈≈≈[#]
....[#080][%186][#000][@880][%186][@][#F00]≈≈≈[#]
....[#080]╨[#000][@880][%186][@][#F00]≈≈≈[#]
[%205][%205][%205][%203][%205][%185][#F00]≈≈≈[#]
[%186]X[%186][#F00]≈≈≈[#]
[%200][%205][%188][#F00]≈≈≈[#]
</frame>
<frame type=level level=1>
Z=1
[#F00]≈≈≈[#]
[#F00]≈≈≈[#]
[#F00]≈≈≈[#]
[#F00]≈≈≈[#]
[%205][%205][%205][%205][%205][%187][#F00]≈≈≈[#]
....X[%186][#F00]≈≈≈[#]
[%205][%205][%205][%205][%205][%188][#F00]≈≈≈[#]
</frame>
<frame type="level" level="-1">
Z=-1
[%201][%205][%187][#F00]≈≈≈[#]
║▲║[#F00]≈≈≈[#]
║▲║[#F00]≈≈≈[#]
║▲║[#F00]≈≈≈[#]
║.║[#F00]≈≈≈[#]
║X║[#F00]≈≈≈[#]
[%200][%205][%188][#F00]≈≈≈[#]
</frame>
</diagram>

Make sure the top z-level is sealed off from miners and '''[[Mining|Mine]]''' ({{k|d}}-{{k|d}}) the highlighted tiles on the upper z-level.

== Bringing magma up ==

Magma can be brought to the surface by three different methods: pump stacks, magma pistons, and minecarts. Pump stacks are conceptually the simplest, but require an enormous amount of in-game time to make. Magma pistons tend to be faster to make, but require more time to understand how to build them. Minecarts are a simple solution, but require more management than pump stacks because they can overfill a reservoir.

=== Pump stacks ===
Pumping magma up from the [[magma sea]] via a conventional [[screw pump#Example layouts#pump stack|pump stack]] is a lot of work, requiring dozens of pumps and significant amounts of power. Making all of the pumps [[magma safe]] also requires a lot of precious materials like iron, or a functioning glass industry.

=== Magma pistons ===
[[Magma piston]]s are another way to move magma near the surface. Magma pistons require less time and fewer precious materials to construct than pump stacks. However, magma pistons are a bit more complicated than pump stacks, so it takes more time to understand how to operate and build them.

=== Minecarts ===
[[Minecart]]s submerged in 7/7 magma (or possibly less, but 2/7 is not enough) will fill with magma. Each minecart holds 2/7 worth of magma, which is subtracted from the amount of magma in the tile. The minecart is then shown as containing magma [833]. Minecarts used for this must be made of [[magma-safe]] material.

Minecarts full of magma can be tipped at a track stop, which will pour the magma in a specified direction from the stop. Therefore, the challenge is to get the minecart full of magma to the track stop. There are two logistical hurdles, and several ways to approach them.

The first decision is how to separate the minecart from the tile of magma. The "obvious" way is to build [[roller]]s in magma to pull the minecarts out; such rollers would also need to be magma-safe. Another way is to drain the magma, and then wait for evaporation. A third way is to pump the magma out of the minecart filling area.

The second task is how to move the liberated magma-laden minecart(s) to the track stop where your smelters/forges will be built. There are, again, multiple valid approaches to this. The "obvious" way is to build tracks from the magma sea to the surface. A minecart track can be operated by dwarves or fully automatic, using powered rollers or [[Minecart#Impulse ramps|Impulse ramps]]. Depending on the placement of the track stop, dangerous overflow can be prevented by making the track stop of a material that will melt/burn once the reservoir begins to overflow.

A less obvious way to move the minecarts up is to simply ''carry'' them. Dwarves can safely haul a minecart full of magma (albeit slowly, due to its weight). [[Wheelbarrow]]s may be used to speed the hauling enormously; however, if the wheelbarrows are not [[magma-safe]]* (i.e. if they are [[wood]]en), they will [[wear]] quickly, most likely disintegrating in the middle of the hauling job. If a minecart is left stranded (either because the hauler got tired, or the wheelbarrow burned up), another hauling task is assigned to move it, either back to its origin stockpile, or farther along to its destination. Be sure your stockpile settings account for these possibilities, so you don't waste a lot of time moving a minecart halfway up, then back down, in a loop.

: (* The cheapest magma-safe metal for a wheelbarrow is [[nickel]], which has few other special uses. [[Nether-cap]] is a magma-safe wood (the only one), and only grows underground. You probably passed some on your way to the magma.)

==== Design 1 ====
In {{F|125679/4217863|one design}} posted to the forums by gchristopher, a pump can provide power to the [[roller]], making the ramp eligible for building the roller, and keeping the trench at 7 magma so the carts fill instantly.

{{diagram|spaces=yes|\
▒▒▒
▒#▒ # {{=}} floor grate
▒%▒ % {{=}} south facing pump
▒%▒▒
▒▲▲▒ Left ramp ▲ has a left-pushing roller
▒▒▒▒ Right ramp ▲ has a retracting bridge
}}

If you drop minecarts in directly from at least 2 z-levels above onto the right ramp, this setup has the magical property that it can handle an arbitrary number of minecarts, and dispense them at a constant controlled rate. Carts are pushed up the left ramp by the roller.

If you extend the right bridge, that tile ceases to be a ramp. Exactly one minecart will fall onto the tile and stay there, and all other minecarts dropped from above will form a quantum pile 1 z-level up.

The last time I [gchristopher] built one, I timed the cart dispensing rate at 1 per 8 ticks. This is slow enough that carts can be brought to the surface using an impulse ramp spiral, but fast enough that you can still quickly cover a large area with magma.

The same design works with water, for giving you a lot of flexibility creating tall waterfalls without pump stacks, quickly and cheaply.

==== Design 2 ====
Rafal99 posted {{F|109460/3374816|another design}} using dwarf-powered [[wheelbarrow]]s to transport the magma-filled minecarts from one minecart stockpile to another.

<pre>
▒ddddd=====S==<<Zccccc Near the surface (top view)
U

▒bbbbb== ==<<Xaaaaa Near the magma (side view)
\7777/

\7777/ - Magma reservoir, with tracks in it and rollers to bring minecart up
the ramp
U - Here we want magma
aabbccdd - Stockpiles accepting minecarts
===<< - Track and rollers
S - Track stop, set to lowest friction (so it doesn't stop the minecart),
set to dump the contents into the U
XZ - Track stops set to dump their contents to the left
▒ - Wall to stop minecarts
</pre>

# Empty minecarts are put into stockpile aaaaa.
# There is a hauling route with one stop on X, with assigned vehicle, set to take furniture->minecarts from stockpile aaaaa.
# Empty minecarts are put into the minecart on track stop X, the track stop dumps them to the left, placing them on the rollers.
# Rollers move the empty minecarts into the magma reservoir, they get filled with magma, then the roller on ramp moves them up. They follow the track, then go out of it and stop at the wall; effectively the minecart with magma is being placed in stockpile bbbbb.
# Stockpile ccccc is set to take from stockpile bbbbb and has assigned 3 wheelbarrows. Dwarves safely transport the minecarts with magma inside wheelbarrows up to the surface into stockpile ccccc.
# There is a hauling route with one stop on Z, with assigned vehicle, set to take furniture->minecarts from stockpile ccccc.
# Magma minecarts are put into the minecart on track stop Z, and the track stop dumps them to the left, placing them on the rollers. (Same as in 3.)
# Rollers move the magma minecarts along the track. They pass through the track stop S and dump the magma in the destination point U, then they follow the track, go out of it and stop at the wall; effectively the emptied minecart is being placed in stockpile ddddd.
# Stockpile aaaaa is set to take from stockpile ddddd. Dwarves haul the empty minecarts back underground near the magma into stockpile aaaaa.
Then we go back to start and the whole thing repeats.

==== Design 3: Minimalist magma moving ====

You'll need two magma-safe pumps, a magma-safe wheelbarrow, and at least one magma-safe minecart.
<diagram>
sideview
░░░░░░░░░░░░░░░░░░░░░░░
░░░ %% ░░░░░░░░░░░░
░░░░░░░░░░▲%%_░░░░░░░░░
░░░░░░░░░░░░░[#c00]7777777[#]░░░
</diagram>

# Dig down to the magma sea and channel a tile above the magma
# Optionally build a floor grate (_) over the hole to keep magma critters out
# Build the first pump to pull magma up into a 1x1 room with a ramp (▲)
# Build the second pump to pull the magma out of the 1x1 room and dispose of it (a 3x3 evaporation chamber works fine)
# Designate a garbage dump zone in the 1x1 room and dump all your magma-safe minecarts
# Wait for all the minecarts to be carried down to the dump zone
# Operate pump 1 briefly, then stop it and activate pump 2 briefly (the minecarts should now contain magma)
# Designate a minecart stockpile near your desired magma workshops, and set it to use your magma-safe wheelbarrow
# Unforbid your minecarts and wait for your dwarves to wheelbarrow them up to the stockpile
# Build a dumping track stop to place the magma where you want it
# Create a new hauling route, specify a new stop on the constructed track stop, and assign one of the magma minecarts to the route
# Unassign the cart, and mark it for dumping; once you've emptied all the carts return to step 6

This design is only useful for moving small amounts of magma, but it is simple and flexible. With any luck you can have your topside magma workshops up and running in the first year.

WARNING: do not attempt to over-fill multi-tile magma pits to full (i.e., a 3x1 pit at 6 depth on each tile) there is a high chance of the magma flowing outwards instead of into the other magma tile resulting in burnt dwarves and FUN.
Note: If necessary, use hatches to control pump operation.

==== Design 4: Urist's Cradle ====
This design works fairly reliable while requiring no powered rollers. It works using [[Minecart#Impulse ramps|impulse ramps]] and is thus considered an exploit.

As seen from the side (south):
<pre>
0: ▒▒
-1: ▒▒▲▲▲▲▒▒

Legend:
▲: impulse ramp (south-east or north-east oriented) , 7/7 magma
▒: solid wall / ground
</pre>
The minecarts arrive from the left with high speed, bump into the walls, drop into the 7/7 magma and get accelerated by the impulse ramps. Because of *physics*, the minecarts get stuck at the last impulse ramp on the right. A second minecart, also coming from the left, will push the first minecart out, filled with magma.

==Using magma==
The primary use for magma is to <s>flood your fortress</s> power [[magma smelter]]s, [[magma glass furnace]]s, [[magma kiln]]s, and [[magma forge]]s. To power a building with magma at least one of the external eight squares must be a hole above a square of magma on the level below.
Placing one of the workshop's [[impassable tile]]s above the magma conveniently prevents clumsy dwarves from falling in.
This seems to usually prevent magma critters from pathing in, but there was a bug report {{bugl|1189}} about [[magma man]] who somehow made its way through without [[building destroyer|destroying]] the furnace in question - it's not clear whether this was normal movement, dodging attack of another critter, [[building destroyer]] activity gone wrong, pathfinding bug, etc. Either way, if you feed magma from a wild area to furnaces via channel, locking it with a [[floodgate]] or raised [[bridge]] is a good idea.
Magma used this way is not consumed; a single tile of magma can operate the furnace indefinitely.

Other uses for magma include [[obsidian farming]], [[DF2012:Trap_design#Magma_and_fire_traps|trap design]], melting [[ice]], igniting [[fire]]s, and even [[garbage disposal]]. It's unknown whether flow push bug {{Bug|5458}} can be a problem with magma, so if you want to be sure, protect the intake with floor grate - like water, except it won't get back up on its own.

Magma saves all the work for fuel (but not flux for steel), so "dig down to magma" is a reasonable strategy for starting metal/glass/ceramics industry. As to the other magma uses - if you get lucky, the first dwarven caravan will bring all the tools you need. If not, you can forge your own by melting down the surplus of anvils that caravans carry, or just embark with a couple chunks of iron [[ore]] or ready bars of [[nickel]] (cheaper, but have few other uses). If you are in a hurry, you usually can take a nickel minecart on embark (at the same price as iron anvil), but to have magma-safe rollers you'll need a forge either way: metal chains seem to ''never'' be available on embark {{verify}}.

==Properties of magma==
Magma behaves the same way as water with the exception of not being affected by [[pressure]] (except when being moved by a [[screw pump]]) and apparently not showing [[flow]]. Magma will turn into [[obsidian]]1 if it touches [[water]]. In the game, magma's temperature is {{ct|12000}}. See the list of '''[[magma-safe]]''' materials for more information on what can (or cannot) be safely submerged in magma.

Tiles directly adjacent to magma will be heated to a temperature of {{ct|10075}}, causing revealed unmined tiles to flash with {{Tile|☼|6:4:1}} when placing digging designations and causing unrevealed mining-designated tiles to [[Digging designation canceled|cancel their designation with a "warm stone" warning]] once they are revealed.

Magma can melt ice beyond the "warm" wall, but this happens ''only when magma moves in'': {{F|72296/1795893|later the same reservoir may freeze just like when magma was not there}}. Whether magma needs to be moved out and in, or depth recalculation is enough is unknown {{verify}}.

Implication of the two above effects is that when magma appears or disappears somewhere, that one and several adjacent tiles start or stop being {{Tile|☼|6:4:1}} "warm" - and there are likely to be temperature recalculations for the tiles adjacent to ''them'' - in addition to processing that happens when moving water. This means that having streams of magma changed or pumped (since a pump can drain its source) tend to cause major FPS drop, which can be prevented by keeping the affected tiles continuously "warm" with small buffer reservoirs (see [[Screw_pump#Improved_Magma_Pump_Stack|Improved Magma Pump Stack]] design by NecroRebel).

[[Construction]]s ([[wall]]s, [[floor]]s, etc.) of any material can safely contain magma. Non-construction [[building]]s ([[door]]s, [[bridge]]s, [[Screw pump|pump]]s, etc.) that come into contact with magma should be built entirely of [[magma-safe]] materials. Non-magma-safe components will eventually melt and the building will deconstruct. Any [[mechanism]]s likely to come into contact with magma should also be made of magma-safe materials.

1 - specifically, one of the inorganic materials having the [LAVA] tag, selected randomly ''per biome'' during worldgen.

==Dangers of magma==
Any contact with magma results in nearly instant immolation, followed by death if water is not close at hand. Additionally, dropping large items into magma will generate clouds of [[magma mist]] which can set your haulers on fire if you aren't careful. Magma is also home to various fiery creatures which can present a significant threat to unprepared fortresses.

{{D for Dwarf}}

Magma is very well known for being the perfect solution to any problem encountered by dwarves. Giant badger invasion? Pour magma on it. Noble being his usual snotty, useless, arrogant self? Pour magma on it. Door locked due to invaders? Pour magma on it! Flooded your fortress with magma? [[Fun|Congratulations, you just won the game!]]

Magma is often referred to as the blood of the earth. Some dwarves interpret this literally, expressing concerns that the earth is capable of bleeding to death. This has led dwarven [[elf|conservationists]] to declare magma a finite resource, advocating stricter regulations on the use of magma-powered workshops.

However, this hypothesis is flawed. The larger a creature, the more blood it has. The world is at least twice as large as a [[giant sperm whale]], the largest creature known to dwarfkind. Therefore, any [[Bloodline:Boatmurdered|pumping operation]] capable of bleeding the world dry would flood the surface and caverns to such a degree as to render the world uninhabitable. On the other hand, this would usher in the [[calendar|age of death]], and thus the earth would indeed be considered dead.

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

{{Category|Physics}}
[[Ru:Magma]]