Dwarf Fortress Wiki - User contributions [en]

40d:Crossbowman

2010-02-24T21:59:04Z

Adeptable: /* Known issues */ on duty is per squad; also some rewording of carried item dump for clarity

Dwarfs or other creatures armed with [[crossbow]]s deal "[[Weapon#Damage calculation|pierce]]" damage from a long distance. A marks'''dwarf''' will usually open fire at a distance of 20 tiles or so from their target, but a bolt may carry 30 or more*. While also doing decent general [[Weapon#Weapon statistics|damage]], a [[bolt]] does a fine job at piercing the internal organs of a [[creature]], which can possibly cause organ failure and instant death, [[unconscious]]ness or crippling of any size target. This is of limited use against creatures without internal organs, such as [[Magma man|magma men]]. Occasionally a bolt will get stuck in a target; the only known use for this is that a [[wrestling]] dwarf may grab the bolt and twist it in the [[wound]].

: ''(* Note that increase in height (z-levels) ''hurts'' range, rather than helps it.)''

A '''marksdwarf''' who is forced into melee will use the [[hammerdwarf]] skill to bash enemies with their crossbow. If you'd prefer your marksdwarves to reload instead of going into melee combat, you can go the {{key|m}}ilitary menu, {{key|v}}iew their squad, and then toggle {{key|c}} to tell them to stay close to their station. This will cause them to go and collect bolts, then start shooting again, instead of either standing in place because they don't have a path to the enemy, or running out to smack the enemy with their crossbow.

[[Immigrant|Immigrating]] marksdwarves bring their own crossbows and 30-40 bolts. Immigrating [[ranger]]s often arrive with Novice Marksdwarf skill, though will only bring a crossbow and bolts if they also have [[ambusher]] skill. (See [[Ambusher]] for more details.)

==Training==
Increasing Marksman skill requires a successful hit upon a target, with "live targets" granting more experience than an [[archery target]]{{verify}}. Higher skill grants better accuracy and higher rate of fire. An archery range is only used by [[military]] dwarves that are off duty, and they will only use [[wood]] or [[bone]] bolts during practice.

===Known issues===
Training marksdwarves can lead to a number of problems. Marksdwarves only train with bone or wood bolts. They need individual [[archery range]]s of adequate size (3 tiles minimum) set up. Any activated military will only practice if they are "standing down" (not "on duty"), which can be toggled only in the {{k|m}}ilitary screen, and then by {{k|v}}iewing the squad.

Marksdwarves will not equip bolts and practice (or fight) with bolts if they are carrying items in hand (as checked via {{k|v}}iew {{k|i}}nventory). Items get in hand if the marksdwarf has been wrestling, a frequent [[Cross-training]] exercise. You can force the dwarf to drop them (or rather, have another dwarf snatch it from them) by selecting the items from their inventory using {{k|enter}}, then {{k|d}}umping them.

{{Skills}}
[[Category:Skills]][[Category:Military]][[Category:Combat Skills]]
[[Category:Jobs]]

v0.31:Release information

2010-01-31T23:00:06Z

Adeptable: /* Appearances */ clean up markup

{{DFNewVersion}}
This page lists the changes in the [[version]] of [[Dwarf]] [[Fort]]ress to be released in early 2010. The page links to currently existing pages which either have been or will need to be modified to list new details from the new [[version]]. It also lists to pages about entirely new subjects introduced in this [[version]], such as [[burrows]], articles created or completely changed based off of this version are marked in '''bold'''.

Adapted from the [http://docs.google.com/Doc?docid=0AT8EQVUjrv96ZGc5cnBwOHZfMjgyY3FzZHFtanA&hl=en&pli=1 google docs file] by SirPenguin about the upcoming release.
<div style="float: right;">__TOC__</div>

== Behind the scenes ==

=== [[Materials]] ===
* The [[material]] system has been rewritten, and just about everything is made from a [[material]] now.
* It is now possible to track the identity of certain [[materials]], such as [[blood]] spatter.
* The [[color]] of a base [[material]] will now have more effects - a [[wagon]] made out of featherwood will reflect the [[color]] of the wood.
* [[Material]] breath [[weapons]] are possible, and can be made of any [[material]]. These are mainly linked with poisons, and when inhaled by a creature, they will become poisoned.
* Small amounts of certain [[materials]] ([[blood]], snow, etc.) can accumulate in a tile.
** For example, if enough liquid [[gold]] accumulates in a tile, it will cool into a [[glob]] of [[gold]].
** This also works for [[materials]] such as liquid (molten) [[metal]], which will cool into a [[glob]] which can then be used to [[melt]] down into a bar.
* [[Weapons]] and [[armor]] now use various "real world" [[attributes]] to calculate their effectiveness. Each [[material]] (rock, [[metal]]) uses the following:
** '''[[Density]]'''
** '''[[Impact/Shear Yield]]'''
** '''[[Impact/Shear Fracture]]'''
** '''[[Impact/Shear Elasticity]]'''
** '''[[Edge]]'''

=== [[Raws]] ===
* Entity positions are now stored in the raw folders, allowing for custom positions through modding, as well as editing existing positions as you see fit.
** These include the new [[military]] positions.
* [[Attributes]] have also moved into the [[raws]], allowing you set all sorts of values such as how fast an attribute increases.
* Many objects - trees, plants, [[stone]]s, etc. - now have [[material]] lists in the [[raws]].
** Some [[raws]] have been merged, such as trees/plants, and [[stone]]s/[[metal]]s.
* A [[region]]'s raw files are now stored in their respective [[save]] folder.

=== The d# series ===
* Translucent [[tilesets]] are supported, using PNG.
* The DF window can be re[[size]]d on the fly.
* The grid size is autogenerated on startup; such [[init.txt]] [[settings]] are ignored.
* Current desktop size is used for fullscreen size if fullscreen resolution is set to 0x0.
* The DF window can be zoomed on the fly using the mouse wheel. There are two modes, it defaults to mode 1. Pressing mouse wheel switches modes. Pressing F12 resets mode 1, not 2. In mode 1, the zoom from mode 2 is not visible. (And yes, you can use both at once.)
* The keyboard input system has been totally rewritten:
** You can bind multiple [[keys]] to one command.
** You can create keyboard [[macros]].
** Input bindings are divided into sections.
* Lots of bugfixes and performance improvements.

=== '''[[Arena]]s''' ===
* '''[[Arena]]s''' are now in the game, and allow the player to set up battles with any kind of creatures with any type of equipment and have them face off.

== [[Combat]] ==

=== [[Squads]] ===
* The [[fortress guard]] is considered a squad under the [[sheriff]], and the [[royal guard]] is considered a squad under the [[Hammerer]].
* '''[[Captains]]''' can be appointed under your '''[[military leader]]''' and lead [[squads]].
* There is a system in place that will try its best to keep your schedules staffed, going so far as finding replacements when [[soldier]]s get hungry/tired, as well as forcing [[soldier]]s to stay on duty if no replacements are found.
* You have complete control over how [[squads]] handle rations - [[food]] and [[drink]] stored in backpacks and flasks - and [[alcohol]] can now be stored as a [[drink]] option.
* '''[[Champions]]''' are no more. Rather, a single '''[[champion]]''' is an appointed position that your [[baron]]/[[duke]].
* "Lord" [[soldier]]s aren't restricted in their weapon choice, and can be made into [[civilian]]s again.
* Beds, racks, stands, boxes/chests and [[cabinets]] can now be assigned to squad positions.
* You can now use the [[note]] making system to lay out stations and patrol routes for your [[squads]].
* [[Sparring]] has been redone.
* A [[dwarf]] skilled in one [[skill]] can teach students via demonstrations of how to fight. This is set up in a classroom environment, so no actual [[sparring]] takes place (less dangerous).
** Even slightly skilled [[dwarves]] can teach people below them.
** There are also instructor monitored drill and [[sparring]] sessions.
** "They can currently teach weapon [[skill]]s, [[wrestling]], dodging, punching (grasp strikes), kicking (stance strikes), shield and [[armor]] use, yeah. They can also teach general close-quarters/ranged [[combat]] principles."
* [[Personalities]] play a role in these lessons. Naturally lazy [[dwarves]] will have a harder time learning and concentrating, though they can overcome them with [[skill]]/attribute increases.
** An instructor's [[personality]] is also taken into account, as a naturally reckless instructor is more willing to send green recruits into [[sparring]] sessions.
* Squad selection/[[orders]] now can occur in real time.
* The entire [[military]] menu has been entirely redone.
* You can issue [[orders]] to several [[squads]] at once or several individuals across different [[squads]].
* Kill [[orders]] are now possible. You can select any creature your [[fort]] does not control to be killed.
* You can give [[squads]] nicknames if you wish.
** You can also give your [[barracks]] nicknames to help keep them separated.

=== Squad [[Equipment]] ===
* There is now a "'''[[Quartermaster]]'''" position who handles various [[equipment]] delegation.
* You can now establish "'''[[uniforms]]'''" for your [[soldier]]s. With it, you can assign specific [[armor]], [[weapons]], and other such [[equipment]] that you want all [[soldier]]s in a squad to wear.
** This allows for you to establish either [[equipment]] protocols (I want this squad to carry a [[sword]] and a shield) or literal uniforms, such as all guards wearing dyed blue cloaks.
* [[Soldier]]s know the difference between [[training]], battle, and [[civilian]] [[equipment]], and when/how to switch between them, as well as how to store them, which is usually done in [[barracks]] via boxes (which can be assigned to [[squads]]).
** The above also extends to [[woodcutters]]/[[miners]], who know how to properly retrieve/store their picks and axes.
** [[Equipment]] can be stored in squad boxes.
* You can now handle [[ammo]] allocation by [[material]], so you can set aside [[metal]] [[bolts]] for battle and wooden [[bolts]] for [[training]]. [[Squads]] will maintain such [[ammo]] counts on their own.
** You can also handle [[ammo]] by type, so that you can have a squad that only uses [[bolts]]/arrows left over by invaders, etc.
** You have similar control over [[Hunter]] [[ammo]].
* [[Training]] [[weapons]] are in now, made at the carpenter's shop. Due to the nature of the [[material]] rewrite, these [[weapons]] lack of edges make them far less dangerous.
* [[Dwarves]] can handle any weapon now (they are not restricted to the current 6 [[weapons]]).
** [[Blowdart]] [[squads]] confirmed.
* [[Critter]]s now become familiar/accustomed to [[items]] they use often, such as [[armor]] and [[weapons]]. Being familiar with an item gives them better rolls during [[combat]].
** They can also become attached to [[items]] and will refuse upgrades.
* [[Items]] keep track of [[creatures]] they kill now, and that will show up in the [[legends mode]].
* [[Items]] can become "named" - raised to a semi-[[artifact]] level - if they have seen a lot of battles or have killed someone of a historical figure era-level of importance.
* [[Dwarves]] will now fill up their [[quivers]] properly - they will not go into [[combat]] with 1 bolt in their [[quiver]] if they can help it.
* You can assign specific [[items]] to units (useful for cases such as [[artifact]]s).
* [[Dwarves]] assigned to [[squads]] will go train in their free time if they have self-discipline. This includes individual drilling practice.
* 1/3 of [[dwarves]] have a "favored" weapon.

=== [[Weapons]] and [[Armor]] ===
[[Image:DF2010_1.png|thumb|400px|The new [[combat report]]s. [[Note]] the date, ability to zoom on location, and more flavorful descriptions.]]
* All [[weapons]] now have multiple '''[[attack types]]''' (a [[sword]] can use a thrusting attack, or with the blade itself, or even the pommel) and each attack can do a different type of [[damage]].
* [[Armor]] [[skill]] and quality of the [[armor]] increases your "deflection" roll, which alters the effective force of an attack.
* [[Weapons]] don't use hard-coded percentage [[damage]] anymore, but rather, use their [[material]]'s various properties in order to determine [[damage]].
* The swing velocity of a [[hammer]] is determined by the strength and weight of the [[hammer]] itself, among other things.
* Woven/Chain [[items]] have a "structural elasticity" property (compared to [[plate]]/scale).

=== Attacks ===
* [[Combat]] has been entirely rebalanced due to the new [[material]] and body changes.
* Small [[creatures]] are now able to take on larger [[creatures]] by pecking away at their bodies, something which was impossible in the old [[version]].
** Thanks to the [[material]] rewrite, though, a well [[armor]]ed knight will fare without many problems against 20 groundhogs.
** Multiple small attacks will have a cumulative effect.
* "I had a [[dragon]] fight some lions, and after a little bit of dragonfire and close [[combat]], I ended up with a [[dragon]] covered with the grammatically-in-progress "lion [[melted]] [[fat]] spatter"."
* Attacks take into account the position and relative nature of the body. Attacks won't "loopity-loop" through the body.
* Temperature transfer between wrestlers is now possible, so think twice before [[wrestling]] that [[spirit of fire]].
** Stuck-ins also transfer temperature.
* Ranged damage has been nerfed, in addition to [[bolts]] making "logical" paths now. The firing rate remains the same.
* There's now a notion of a "squared shot", in that your attack could hit someone's arm full force, but if you didn't hit in in the right area, the [[bone]] would not break. This helps many problems, such as with [[bolts]], as well as axes/[[sword]]s not lopping everything off everything you swing.
* Twisting your weapon in a [[wound]] has been balanced, and won't just amplify [[damage]] forever.
* [[Toady]] on the path of the force of an attack: "The [[armor]] is all checked in order from outer to inner, then it gets at the tissue [[layer]]s, altering the character of the attack as it goes."
* Attacks can pass through a [[wound]] sufficiently large enough.
* Force from blunt [[weapons]] can transcend [[layer]]s. For instance, a [[hammer]] can bruise the [[skin]] while breaking the [[bone]] underneath.
** As such, [[plate]] [[armor]]'s benefits are generally ignored by blunt attacks, and [[leather]] [[armor]] would prove to be more effective.
* "Solid breath can take the form of a forward moving dust puff that accidentally knocks people out due to some [[cave-in]] code. When I fix that, KOs make or may not be a parameter. Solid breath can also take the form of a solid [[glob]] (a small one right now) that is hurled like a [[stone]]. It might as well be a thrown [[stone]] of the solid. Solid breath can also be an undirected dust puff (also accidental knockouts)."

== [[Creatures]] (general) ==

=== [[Attributes]]/[[Skill]]s ===
* The attribute system has received an overhaul. There are now 19 [[attributes]] split across physical and mental. They are:
** Body:
*** '''[[strength]]'''
*** '''[[agility]]'''
*** '''[[toughness]]'''
*** '''[[endurance]]''' - this'll take some of the weight off of [[toughness]] and control your exertion.
*** '''[[recuperation]]''' - somebody suggested "resilience". i don't really like any of the names... in any case, this will control the [[healing]] of your physical [[wound]]s.
*** '''[[disease resistance]]''' - the more time i spend on infection and venom, the more this will matter for this release. there will also likely be a notion of specific immunities, some of which you could gain with exposure or whatever ends up making the most sense.
** '''[[soul]]''':
*** '''[[analytical ability]]''' - thinky stuff.
*** '''[[memory]]''' - remembery stuff.
*** '''[[creativity]]''' - being able to make up neat stuff.
*** '''[[intuition]]''' - being able to get stuff.
*** '''[[focus]]''' - being able to get into stuff.
*** '''[[willpower]]''' - being able to keep on with and cope with stuff.
*** '''[[patience]]''' - being able to handle not doing stuff.
*** '''[[spatial sense]]''' - sense of surrounding stuff.
*** '''[[kinesthetic sense]]''' - sense of own stuff.
*** '''[[linguistic ability]]''' - all of the wordsy stuff.
*** '''[[musicality]]''' - musicky stuff.
*** '''[[empathy]]''' - being able to feel other peoples' stuff.
*** '''[[social awareness]]''' - being able to manage and handle social stuff.

* [[Creatures]] now have '''[[souls]]''', and these souls serve as storage for a creature's mental [[attributes]] and [[skill]]s.
** [[Creatures]] can have multiple souls, though there is no such use in the current [[version]].
* [[Attributes]] and [[skill]]s can now "'''[[Skill rust|rust]]'''" if the attribute/[[skill]] is unused for a long period of time. The more rust the [[skill]] or attribute has, the less effective it is, and high enough rust will actually "delevel" the ability. Rust can be worked off by simply using the attribute or [[skill]] in question.
* Attribute/[[skill]] display system has been redone so as to not overwhelm the player.
** [[Skill]]s have been split up into '''[[Skill groups|15 logical groups]]''' to make assigning [[skill]]s easier.
* [[Creatures]] now have a "'''[[situational awareness]]'''" [[skill]], which handles a [[creatures]] ability to deal with surprise attacks and ambushes.
* The [[wrestling]] has been split into the following [[skill]]s:
** '''[[Wrestling]]'''
** '''[[Dodging]]'''
** '''[[Grasp strikes]]'''
** '''[[Stance strikes]]'''
* There are also general '''[[melee attack|melee]]''' and '''[[range attack]]''' [[skill]]s (which help with [[combat]] rolls but are separate from "axe mastery", etc.)
* [[Attributes]] and rust rates are linked to specific castes, so you could have brutes intermixed with brainy [[creatures]] of a single race.
* "Ceilings of [[attributes]] are a percentage of the starting value. So a strength 1000 [[dwarf]] might attain 2000, and a strength 750 [[dwarf]] might attain 1500."

=== Appearances ===
[[Image:DF2010_2.png|thumb|400px|The new description window]]
* [[Creatures]] are now unique to each other with different appearances, including hair [[color]], facial features, etc.
** These are visible in [[adventurer]] mode as well.
** Different [[color]] patterns are also available, like striped or mottled.
* [[Creatures]] can also be fatter/taller/etc. than usual. This affects their [[size]]. Fatter [[creatures]] can last without [[food]] longer.
** [[Creatures]] have a '''[[metabolism]]''' now, which deals with how fast they heal and how fast they burn [[fat]].
** [[Fat]] [[creatures]] also move slower.
* The trimming of hair/nails is also possible for civilized [[creatures]], and they will grow long and unkempt without such activities.
* [[Creatures]] '''[[genetics|inherit appearances from their parents]]'''. This includes dominant/recessive genes.
** As one example, you can use this system to breed your dogs to a certain [[color]]/[[size]].
* [[Layer]] trimming/caring uses style definitions from a culture. Some cultures may grow beards, others may shave them. Prisoners, etc. may be forced to adapt these new styles.
* Speaking of beards, as if it wasn't obvious by now, but this means [[dwarves]] finally have beards!
** On a more startling note - so do [[elves]]!
* [[Creatures]] can now be part of a '''[[caste]]''', and this may govern many things, such as their profession, appearance, etc.

=== Bodies ===
* Tissues now come in [[layer]]s. You must bypass a [[layer]] to reach one below it. Some [[layer]]s are dependent on others (hair can only exist if there's [[skin]] underneath it, etc.)
* '''[[Hair]]''' acts as a [[layer]] on [[skin]]. It can come in many different styles (sparse, strands, etc.)
* '''[[Hair]]''' grows and eventually grays over time. It can be trimmed, and if left alone it will become shaggy and unkempt.
* Body parts and tissue [[layer]]s can be made out of any [[material]] you want, such as for logical [[creatures]] like [[Iron Men]], and illogical abominations like [[Dwarf]] Lung Men.
* It's now possible for some [[creatures]] to be made out of solid [[material]], such as [[Iron Men]], who are much harder to fight.
* You can also have hollow body parts, perhaps filled with air or other [[materials]].
* Some [[layer]]s can serve as protection, such as [[chitin]] [[layer]]s. [[Bone]] [[layer]]s also protect organs, such as the [[skull]] protecting the brain.
* [[Creatures]] now have teeth, rib, cheeks, eyelids, nails, and lips. Teeth and ribs are not individualized, but rather are tracked by groups (i.e., top left molars, etc.)
* [[Creatures]] also now have tendons and ligaments, and are made from the "sinew" [[material]].
* [[Creatures]] store energy from their [[food]], getting [[fat]]ter and more muscular.
** [[Fat]] affects such things as insulation, speed, etc.
** Strength also increases muscle [[size]]. Both have an effect on a creature's total [[size]].
* Guts are realistically [[color]]ed - crazy stuff!
* It is now possible to "flay" a creature. Have fun!
* We've also got [[water]] freezing into frosty stuffs on people if they get [[wet]] and then step out into the cold, and [[steam]] coming off of spirits of fire in the rain.
* [[Skeletal]] [[critter]]s now have their [[bone]]s held together by rotted ligaments.

=== [[Thoughts]] ===
* [[Thoughts]]" of a [[dwarf]] have been redone. The new screen includes their current [[thoughts]], age/birthday, physical description paragraph, a description of their [[attributes]], their likes/dislikes, and their mannerisms. Also included are descriptions for their [[wound]]s/scars.
* A [[dwarf]]'s birthday and age are stored in their [[profile]] now.
* [[Dwarves]] now have '''[[mannerisms]]''', such as "always scratches his head when he's trying to remember something", "laughs at his own jokes" or "talks to herself whenever she's bored". There are 65 types with 3-5 situation qualifiers.

== [[Fortress Mode]] ==

=== Organization ===
* '''[[Burrow]]'''s! Burrows are areas in your [[fort]] where [[dwarves]] live and work in. You can assign these areas like [[zones]] and assign [[dwarves]] to them. [[Dwarves]] will only use [[workshops]], rooms, etc. in [[burrow]]s they are assigned to.
* There are a significant number of ways to utilize [[burrow]]s, from restricting certain [[mining]] expeditions to [[skill]]ed [[dwarves]], to making noble districts, to setting "emergency" [[zones]] for [[civilian]]s to flee to, etc.
* You can set [[soldier]]s so that they defend certain [[burrow]]s. If an enemy enters a [[burrow]] they know enough to stop what they're doing and head towards it to defend it.
* You may choose and appoint someone as your [[baron]] when you reach [[barony]] status. You can elect not to have one as well.
* There are now "code generated" positions, such as '''[[priests]]''' who are named after the [[god]] they worship (Priest of Ciramore, etc.)
* [[Dwarves]] won't immediately drop everything if they find themselves hungry or tired, and will try to finish their current [[job]] first.
* There's a difference between sleeping [[barracks]] and squad [[barracks]].
* Liaisons will be be generated from scratch if they die.

=== [[Workshops]] ===
[[Image:DF2010_3.png|thumb|400px|[[Statues]] now have art associated with them.]]
[[Image:DF2010_4.png|thumb|400px|Some new [[crafts]] you can make.]]
* [[Statues]] and figurines now have art associated with them.
** "[[Statues]] of specific [[dwarves]] get the [[dwarf]]'s name right in the item name."
* Custom [[workshops]] are now able to be modded in, allowing you to set up custom [[reactions]].
** These can support [[corpse]] harvested [[items]], like shells/horns, and might use barrels/other [[containers]].
* You can now make [[crafts]] out of horn, ivory, teeth, and other new body parts.
** These include [[dragon]] tooth [[rings]] and [[ivory]] crowns.
* [[Butchery]] has been overhauled due to the new body part systems, with [[creatures]] yielding many more parts for consumption.
* It is now possible to have automated [[fishing]] [[cleaning]] and [[fat]] rendering.

=== Alerts and [[Announcements]] ===
* The alert statuses (i.e., "Stay Indoors") have been entirely redone. You may set several custom alerts with user defined [[reactions]]. For instance, you could set a "[[Underground]] Attack" alert where you force [[soldier]]s to equip melee [[weapons]] and head to a predefined location.
* These alerts can also be assigned to [[civilian]]s, such as telling them to flee to the great hall.
* [[Combat reports]] have been redone in hopes of consolidating sentences and making it more interesting to read
* Combat reports are separated into [[combat]], [[sparring]], and hunting reports. You'll see a notification on the side of the screen letting you know a [[combat report]] has been generated.
** They are also timestamped.
* You can choose different options for each announcement, like whether you want it to pause the game or recenter your view.

== [[Healthcare]] ==

=== Doctors, hospitals, and how to cure what ails you ===
[[Image:DF2010_5.png|thumb|400px|The new [[wound]] [[color]]ing system.]]
* '''[[Hospitals]]''' are used like [[zones]]. [[Items]] used within these [[zones]] (beds, tables, boxes) allow for hospital use.
** They also use a new item, called a '''[[traction bench]].'''
* '''[[Doctors]]''' can "prescribe" treatment, such as bed rest, using splints for broken [[bone]]s, amputation for infected limbs, and surgery.
** Doctors will set [[bone]]s for simple fractures, use traction for difficult overlapping fractures and use surgery for disgusting compound fractures. They also excise [[rotting]] tissue and amputate limbs too rotted off to save.
** The system where [[dwarves]] heal on the [[season]] change is gone.
* [[Wound]]s are dressed with '''[[bandages]]''', which speeds [[healing]] and slows bleeding.
** '''[[Sutures]]''' make [[wound]]s heal faster.
** Sutures can be ripped out in [[combat]], causing pain/bleeding.
* '''[[Crutches]]''' are now in the game, allowing one legged [[dwarves]]/injured people to walk normally (as opposed to crawl). They will move faster as they get comfortable with their new crutch.
** '''[[Casts]]''' are also in.
* [[Creatures]] can now clean the filth they acquire due to various [[materials]], like mud, [[blood]], [[vomit]], etc.
** As such, [[soap]] has a use now, which deserves its own bullet point.
* You can appoint a "'''[[chief medical dwarf]]'''" to handle the various medical information, which requires the "'''[[Diagnosis]]'''" [[skill]].
** What type of various medical information? "unit [[wound]]s/status/required treatments/medical history, etc." - Think of it like the [[bookkeeper]].
* [[Dwarves]] are more proactive in saving [[wound]]ed people, and will do what they can in regards to bleeding on the way to the hospital.
* "Eyelids clean the eyes so you don't have to [[soap]] them off, but if an eyelid is torn off, I think they might [[soap]] the eyes."
* Patients can use [[soap]]/[[water]] to clean [[wound]]s and grime to reduce infections. Sutures, casts, etc. will reduce infection as well.
* All cloth and thread [[items]] have associated lengths/areas now. Threads are use for sutures (thus, one "thread" item could be used for multiple sutures) and cloth is used for bandages. [[Items]] in this way aren't split (a la coins or [[bolts]]), but rather, they're consumed in pieces.
* Unskilled or apprentice doctors can make mistakes when treating a patient or doing surgery.
* "[[Healthcare]]" as a [[skill]] is gone. It's been replaced by 7 new labor [[settings]], 5 unit types, and 6 new [[skill]]s.
** There are different type of doctors associated with the [[skill]]s.
** Dressing [[wound]]s, diagnosis, surgery, setting [[bone]]s, suturing and walking with crutches appear to be the new [[skill]]s.

=== [[Wound]]s and [[injuries]] ===
* The current 15HP-per-body-part system has been dropped in favor of individual [[wound]] tracking.
** The above also allows for scars.
* Open [[wound]]s can get simple infections, which results in oozing pus, slow [[healing]], and can even kill.
** [[Rotting]] [[wound]]s smell and contribute to infection levels, as does grime buildup.
* Tissue [[layer]]s can boil off when exposed to extreme heat.
* Phantom pains are gone.
* You can [[damage]] a creature's motor and sensitivity nerves. Motor [[damage]] prevents that part from working, and sensory nerve damage makes you lose feeling in that body part.
* Partial and compound fractures are now possible.
* Fractured [[bone]] can be knocked inwards to cause [[damage]] to organs, like forcing a jagged piece of [[skull]] into the brain. [[Bone]]s can also [[pierce]] [[layer]]s, like having [[bone]] sticking out of your [[skin]].
* Guts are under [[pressure]] and can pop out of a [[wound]].
* Injured [[creatures]] can continue to work if they are treated. A miner who breaks his left hand will go back to [[mining]] with his right hand (after his broken hand is set in a cast).
* "There are lots of [[wound]]s that won't heal now if they aren't treated (aside from the nerve stuff, the three kinds of bad breaks won't heal if not treated), and infected [[wound]]s heal very slowly."

=== Poisons ===
* Types of poison effects: pain, swelling, oozing [[wound]]s, bruising, blisters, numbness, paralysis, fever, bleeding, coughing/[[vomit]]ing [[blood]], nausea, [[vomit]]ing, unconsciousness, necrosis, impaired vision, drowsiness, and dizziness.
* Poisons can be contacted, injected, or inhaled.
* You can be immune to poisons; [[creatures]] seem immune to their own poisons.
* Severs transfer containment, so that a ripped off venom fang from a [[Giant Cave Spider]] will remain venomous. As of now you cannot use it as a [[weapon]].

== The Underground ==

[[Image:DF2010_6.png|thumb|400px|An example of the new caverns. Here you can see open areas and [[underground]] lakes, as well as passages linking them together]]

=== Underground Features ===
* Underground [[layer]]s have been entirely revamped, allowing for more diverse [[underground]] with new [[creatures]], features, and other interesting goodies, such as Mushroom Forests.
* The standard amount of [[layer]]s (around 15) has been scrapped and increased dramatically; upwards of 50-100 [[layer]]s.
* Each cave [[layer]] [[region]] (which is a certain depth and portion of the world map) has its own name, animal populations, [[civilizations]], etc.
** They also show up on the legends screen.
* '''[[Caverns]]''' now exist [[underground]]. Caverns are open areas underneath the earth, and are home to [[creatures]], [[underground]] lakes, and other interesting features.
* Features are much more easy to discover, and almost every site is guaranteed to have SOMETHING interesting in it.
** For instance, [[magma]] is almost always guaranteed to be at the very bottom [[layer]].
* Features can span multiple world tiles, and can be explored via adventure mode and [[dwarf]] [[fortress]] mode.
* You can use [[world gen]] parameters to get rid of [[underground]] features. The default [[settings]] are set for cavernous so you're guaranteed to find cool stuff.
* Features are not instantly revealed anymore. [[Underground]] areas must be explored by [[dwarves]] prior to revealing features.
** So yeah, the new system is to have a 60 or so tile [[flood]] out from your [[dwarves]] as they go [[underground]], and any time they get within 30 tiles of the 60 tile [[flood]] (flags are kept when the [[flood]] got out to 30, roughly), it'll [[flood]] out again, picking up those flags and placing new ones, so it moves out in a kind of chunky way.
** [[Squads]] can't take [[orders]] to walk into hidden [[zones]] (must reveal first).
* It's possible for an [[adventurer]] to enter a massive [[underground]] cavern on one side of the world and journey all the way to the other.
* Bottomless pits and chasms are gone for the time being, replaced by finite caverns.

=== [[Critter]]s (normal and animalman-y) ===
* Underground animalpeople can use crude [[weapons]] and mounts now.
** Batmen could ride giant bats and shoot poison darts at you with makeshift blowguns made from [[giant cave spider]] legs - whoa!
** Their goal is to cause as much havoc as they can before sneaking back home.
* Underground [[critter]]s are "drawn" from a large population that is off site. They will replenish their population so long as a cavern has an open "edge" allowing them to spawn in.
* The above, coupled with other changes, allows for the possibility of never-ending attacks.
* [[Antmen]] now have creature castes which separate them, including queens.
** There are also [[antmen]] nests to worry about.
* '''[[Gremlins]]''' are back. These sneaky dudes are invisible until spotted, and will step on [[pressure]] [[plate]]s, pull levers, and open cages.
* There are many new [[underground]] [[critter]]s.

=== [[Critter]]s (random beasts) ===
* Random [[critter]]s are now possible. They come in two flavors: "'''[[Titans]]'''", which are above ground and serve as megabeasts, and "'''[[Forgotten Beasts]]'''", who live [[underground]]
* Random [[creatures]] are just that - random. The can have unique attacks, like firebreath or poison, as well as a random number of body modifiers like legs, wings, etc.
** Some examples: a ribbon worm with wings made of stretched [[skin]]. An eyeless antenna lizard. A [[glob]] of [[vomit]] inside a round shell.
* They pull from certain base types (blob, quadruped, humanoid) as well as various animal/creature features.
** Dinosaur types (?!) are also now possible
*** They have feathers to boot
* These are seen as the ultimate challenge of the game

=== [[HFS]] ===
* The old [[HFS]] that we know of is gone, replaced by new baddies. The [[critter]]s of the [[HFS]] seemed to have survived the [[version]] change, however.
* [[Toady]] has spent countless days working on the new [[HFS]], and he's been silent on what it could entail.
* There is a lot of nasty stuff underneath, seemingly related to the old "end of the world" timers.
* It should be a bit different, a bit the same, and always a threat rather than a one-time problem.

== The World ==

=== [[Civilizations]] ===
* There is now the notion of a '''[[split leadership]]'''. Some leaders may prefer to be "traditional" rulers, hanging back in their cities while appointing generals to command their armies. Others may prefer to lead battles and wars themselves.
* [[Goblin]] society is more violent than ever. They respect those with power, and [[demons]] will be forced to kill for their loyalty. Other [[goblin]]s, however, can do the same.
** [[Goblin]]s obtain their structure over the course of world generation. For instance, [[demons]] are not hard-coded as leaders, and must earn their position.
* Forgotten beasts can escape from the [[underground]] and try and pass themselves off as [[god]]s, gaining worshipers and taking control of [[civilizations]].
* Leaders of [[civilizations]] can now own "pets" - and by that, I mean they can [[tame]] wild animals and use them in war. [[Giant eagles]], [[tigers]], everything is fair game.
** [[Elves]] have a great advantage here for obvious reasons, but [[dwarves]] will be able to make use of [[underground]] beasts.
* '''[[Priests]]''' are back.

=== [[World Generation]] ===
* "I've added the ability to specify in the [[world gen]] parameters the number of sky z-levels, the number of z-levels minimum between each [[layer]] (it'll often be more because of elevation changes), and the number of extra z-levels down at the bottom."
* Much of the map feature code was rewritten to be more flexible in future expansions and updates.

=== [[Megabeasts]] (general and [[Titans]]) ===
* [[Megabeasts]] aren't pushovers in worldgen anymore, and will survive longer and get more kills.
* [[Titans]] in good areas will be benign/neutral to [[creatures]].

== Links ==
*[[Notes on new positions]]

40d:Important advice

2010-01-31T22:25:16Z

Adeptable: /* Tricks */ skip redirect

Here are a few things to keep in mind when playing Dwarf Fortress.

Above all, one must remember that '''losing is [[fun]]!''' Be prepared to lose a few fortresses before you get the hang of things – it can be easy to accidentally kill the entire fortress while playing around with the different mechanics.
But remember: losing means that next time, you'll remember how you lost! In a big way, Dwarf Fortress uses the principle of learning from one's mistakes.

If you cannot find your answer on this wiki, check out the forums at [http://www.bay12games.com/forum/index.php Bay12games.com]

== Advice ==

* Keep in mind that Dwarf Fortress doesn't have a "win" condition. It just has a long series of "lose" conditions.

* Learn the [[controls]]. There's lots of them, and learning them may seem daunting at first, but once you get the basics down (like how to check the status of your dwarves or the hotkeys for building certain structures), you'll find yourself playing much more efficiently. [[Efficient_gameplay|Efficient Gameplay]] offers some time-saving tips.

* If your game is running slowly, learn how to [[Maximizing framerate|maximize your framerate]].

* Save often! Although it can be a hassle to have to quit out and get back in, it's a lot better than having to build that long hallway of stone-fall traps, plant the whole bag of plump helmet seeds, and make that shipment of steel battleaxes for the caravan next year, ''all over again''.
** In this vein, there is a seasonal auto-save feature which you can turn on by editing your /data/init/init.txt file.

* Plan ahead a little during construction. When building your first couple dozen rooms, consider that in the future you might want to make certain busy hallways wider so dwarves aren't always climbing over each other. This will be a lot easier if you put rooms back an extra tile so you don't have to rebuild everything.

* Think three-dimensionally. You have a Z-axis. Things will be much closer when they're downstairs one floor than if they're 20 tiles away down the hallway. Also note that, with the default [[tilesets|tileset]], your display of the fortress is not square, so north/south distances will appear longer than east/west distances -- they aren't.

== Tips ==

* Dwarves thrive on [[alcohol]]. If a dwarf drinks only water, the rate at which he gets tasks done decreases. If the fortress has no alcohol for years, things will slow down quite a bit.
* Dwarves also need [[food]], obviously - and a good [[cook]] (and a nice dining hall) go a long way towards keeping your fortress happy.
** Don't cook all your alcohol or all your [[seed]]s (or all the things that leave seeds). ({{k|z}} >> Kitchen).
* Dwarves tend to get trapped easily. They like [[Digging#Dig_Priority|building and digging things from certain directions]], so try to make sure there is a way out (and keep an eye on them just in case they try something crazy). Also keep in mind that workshops block certain squares, so if ever notice that your jeweler dies after constructing a workshop with a door on the east side, that's why.
* Workshops, construction and combat are [[noise|noisy]]. Keep your sleeping areas away from noise and your dwarves will get a good night's rest.
* Workshops will become [[clutter|cluttered]] once they have 15 average goods in them (more for [[craft]]s, less for [[siege weapon]]s). Make stockpiles to receive the goods, and have ample [[hauler]]s, and/or more than one of a workshop that's likely to get cluttered.
* If a dwarf gets badly [[Wound|injured]], he'll need a hospital bed and someone to bring him [[water]] in a [[bucket]]. It's probably a good idea to have a set of those sitting around.
* [[Traps]] can help take care of invaders at no risk to your dwarves. Any fortress can build a  bunch of stone-fall traps. Cage traps are also easy (you can make cages out of wood).
* Having a dwarf with the Appraiser skill to be your [[outpost broker]] will help a lot when [[trading]]. Otherwise, you can't see how much an item is worth.
* [[Chain]]ing some [[dog]]s by your front door may deter thieves.
* Remember that dwarves can be assigned new [[labor|jobs]] at any time. If your carpenter has died, your farmer can start making beds. (He probably won't be very good at it, since he doesn't have the skill, but it's better than sleeping on the ground.)
* Idle carpenters? It's hard to have too many [[barrel]]s (or too many [[bin]]s... [[bed]]s for the next wave of [[immigrant]]s are pretty handy too). Idle masons? You can fit a lot of [[door]]s into your fortress, and buildings constructed from [[blocks]] add value over rough stone.
* Too many [[immigrant]]s? Don't know what to do with them? Have you started an [[army]] yet?
* When setting a [[water]] source (for designated drinking zones) or a [[fishing]] zone, remember that only walkable tiles are valid - you need only mark the shore.
* If you don't have [[magma]] on the map, smelt only what you need; [[coke]] is a finite resource.
* That being said, [[magma]] brings its own unique set of challenges; complete beginners should probably give it a wide berth.

== Tricks ==

* To find a dead dwarf, go under status ({{k|z}}), then select stock>>corpses. Hit tab, and use {{k|z}} to zoom to the particular dwarf to find a hint on where and how he died.

* Don't like all the stone laying around? Instead of using a stone [[stockpile]] create a 1-square garbage [[zone]] and [[dump]] the stone. Reclaim the stone after it's been dumped. This way, you can store an unlimited amount of stone in just 1 tile! (This is especially useful when the tile in question is next to your mason shop).

* Usually the closest available material is used for tasks such as (for example) building a floodgate, but not always. To prevent frustration, you can make a custom stockpile (e.g. for [[bauxite]]) next to your workshop and close the dwarf in. Don't forget theres a z-axis, so make sure there aren't unwanted materials above/below your workshop.
** If you bring [[bauxite]] to a [[magma]] map, you can build the workshop next to the wagon and get your magma-proof grates/floodgate/mechanisms immediately.
** Lock your [[gem setter]] in a room with some cut [[gem]]s and a [[stockpile]] set to gather quality [[furniture]], so that he doesn't waste time (and valuables) encrusting stupid things like barrels.

* The Standing Orders ({{k|o}}) screen can be used for a variety of useful settings, like having your dwarves temporarily ignore wood, or all hide inside for a siege, or making your weavers stop heading outside all the time to collect spiderwebs and get slaughtered by wild animals.

* Hitting {{k|x}} when building a building expands the list of items, so you can pick one with a specific [[quality]] (a nice bed for a noble's bedroom, or a cheap door for the garbage room).

* If you're scanning the outdoors for your next swath of [[tree]]s, move your view up one level. They will appear as little rectangles on a field of dots and will be easier to spot.
** Speaking of timber, try designating some high-traffic lanes ({{k|d}} {{k|o}} {{k|h}}) outside radiating away from your front door to the trees. Your dwarves will stick to the paths somewhat, and probably trample fewer saplings. (They also won't mess up the ground and leave a bunch of ugly [[sand]] spots scattered around on a sandy map.)

* Build a walled [[statue]] garden outside your fortress so that your dwarves don't get [[cave adaptation]].

* Bring along a few [[turtle]]s or [[cave lobster]]s when you start the game. Make sure the dwarves eat them raw (disable cooking) ({{k|z}} >> Kitchen). This way you will have [[shell]]s - useful in case you ever run into a [[strange mood|(spoiler)]].

* [[Trade]] for basic items like [[meat]] and [[wood]]. They're cheap, and it's easier than gathering them yourself.

[[Category:Guides]]

40d:Cross-training

2010-01-31T21:31:20Z

Adeptable: /* Clear Cutting */ sp

'''Cross-training''' is training your military dwarf candidates in civilian disciplines (or vice versa), and offers multiple benefits. First and most importantly, it gives you several extra [[attribute]] increases. Toughness, especially, is extremely important for military dwarves; it allows them to take more wounds before passing out from pain, and to recover from wounds faster. Second, it provides a ready pool of recruits in case your military takes a beating at one point or another, and/or allows civilians a better-than-normal chance to defend themselves. Third, it ensures that your [[soldier]]s have some domestic skills so they will not receive [[thoughts|unhappy thoughts]] from being de-activated from the [[military]] in the event you need to downsize, or just need some extra labor short-term. Finally, most reserves programs provide chronic idlers with some work to do, which can be essential for unskilled workers like peasants to break out of their poverty (and therefore, unhappiness) cycle once the [[dwarven economy]] kicks in.

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

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

===Different Programs:===
====Gym ([[pump operator]])====
[[Image:Pump_farm.png|thumb|right|71px|No pain, no gain.]]
The Gym is the most basic sort of reserves program; it merely consists of building a bunch of [[screw pump]]s connected to nothing in a room that's close to [[food]], [[beds]], and [[drink]]. After the pumps are built, order them to be pumped manually, then turn on [[Pump operator|pump operating]] for your reservists.

[[Toughness]] influences how tired your dwarves get. Tougher dwarves can operate a pump longer before getting tired, meaning they will gain skill more quickly than non-tough dwarves. Once dwarves hit Unbelievably Tough, they can operate pumps non-stop. 
'''Pros:'''
*Easy to set up; 4 pumps in the gym will keep at least 8-10 reservists busy around the clock.
*Extra pumps can be added to expand operations very easily.
*Requires no continuous oversight on your part.
*Somewhat fast training; legendary in under a year (if other responsibilities like hauling are minimized).
*Very safe; gyms can be placed anywhere in the comfort of your fortress with no issues. 
*If you're really clever, you might be able to arrange your pumps so they power one or more indoor [[waterfall]]s. To get the full benefit of this approach, you would probably have to design your fortress around the waterfalls. Remember not to dig under their feeding tubes!
'''Cons:'''
*Tons of cancel job spam. Every time a reservist exhausts himself and goes to satisfy his basic needs, you'll see "Urist McScrewpumper cancels Operate Pump: Exhausted."
*If you have any pumps around that actually DO need to be operated every so often (refilling your [[well]], for example), it could be a serious pain to juggle the useless gym pumps and the ones that are actually useful.

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

====Internship ([[bookkeeper]])====
Turn on highest precision bookkeeping and rotate the appointed noble in and out the second he becomes a legendary bookkeeper. 
'''Pros:'''
*Requires no extra infrastructure at all.
*You need a bookkeeper anyway!
*Totally safe; a bookkeeper spends basically all his discretionary time snug in his office.
*Trains outrageously fast; if the office is very close to [[food]], [[beds]], and [[drink]], a bookkeeper can be legendary or close to it in a mere season. 
'''Cons:'''
*Only employs one dwarf at a time; not useful when you have 15-25 candidates for the reserves.
*No announcement when the current intern reaches Legendary status means you can lose time on rotation easily.
*Legendary bookkeepers might leave their successor without work, losing work and experience.

====Internship MkII ([[manager]])====
Much like bookkeeping, assign a new dwarf to manager, queue several hundred jobs, and rotate a replacement in as soon as he becomes legendary. For bonus points, queue jobs which need to be repeated anyway, like "Prepare Raw Fish" or "Mill Plants", or jobs for which there is no workshop, like "Make Wooden Bow" or "Make Soap". 
'''Pros:'''
*Requires no extra infrastructure at all.
*You need a manager anyway!
*Mostly safe; a manager spends basically all his discretionary time snug in his office, or doing his other assigned jobs.
*Trains fairly quickly; with enough jobs, especially ones which need to be repeated anyway, you can get legendary inside two seasons. 
'''Cons:'''
*Only employs one dwarf at a time; not useful when you have 15-25 candidates for the reserves.
*No announcement when the current intern reaches Legendary status means you can lose time on rotation easily.
*Trains more slowly than bookkeeper, requiring roughly 60 lots of 30 jobs to reach legendary, and 40 more to Legendary+5.
====Gulag ([[miner]])====
The gulag is basically a strip mine that is located far away from your main fortress (so you don't have to worry about accidentally screwing up your own building plans; if you are careful in planning, it may be placed closer to your fortress). Take a big square and start leveling it; it's really no more complicated than that. Since [[pick]]s can actually be used as weapons, it's worthwhile to give the reservists who will be working in the gulag picks made out of [[iron]], or, if you are really living large, [[steel]]. Note that you will have to turn your usual mining corps (the civilian miners who are already experienced with mining) off for this setup to work properly. 
'''Pros:'''
*Soldiers enter the military with an emergency weapon in their hand already; this can be critical in the case of [[speardwarf|speardwarves]], who have a habit of losing their weapons in an enemy, or [[marksdwarf|marksdwarves]], who are forced to use the [[hammerdwarf]] skill in melee, which they may not even have.
*Toting a pick for close-quarters support might make a legendary [[marksdwarf]] more useful, since the pathetic bludgeon damage of his [[wood]] and [[bone]] [[crossbows]] are less important.
*Can be quite useful for producing stones you might not have access to normally, or uncovering veins of precious metals.
*Levels quite fast in sand.
*Relatively little oversight from you.
*An overland hike to the gulag will fight [[cave adaptation]] in your military candidates. 
'''Cons:'''
*Juggling your real miners and your reservists when there's real work to be done on the fort can be a chore.
*Hard to keep dwarves in the gulag for too long; they'll inevitably get hungry, thirsty, and tired and start hiking back to the fortress proper.
*Can be dangerous, depending on the biome.
*Does require some amount of oversight from you, especially when your reservists start getting better at mining and run out of work more quickly.
*Low-skill miners may discover---and then partially destroy---valuable gem or mineral deposits.

====Renovation ([[stone detailing]])====
Another convenient way to buff up your dwarves, assigning your reservists to mass [[stone detailing]] duty increases your fortress' architectural wealth and makes the place look nicer. While they may clutter the halls somewhat, it doesn't require any special allocation of [[food]], [[beds]] or [[drink]]. Just turn on [[stone detailing]] for your reservists and mark up as much of the fortress as you like for renovation. 
'''Pros:'''
*Even easier to set up; just assign your dwarves and an area and you're good to go.
*Increases your fortress' value and general happiness.
*Requires no continuous oversight on your part.
*Very safe, if you only assign areas inside the fortress. 
'''Cons:'''
*Wealth overflow may bring too many [[immigrants]].
*Serious conflict with [[engraving]] assignments; trying to engrave with poorly trained engravers wastes a lot of wealth that essentially comes from nothing. To avoid this, have periods when you only designate stone smoothing, followed by periods where you only designate engraving.
*Careless designation of smoothing areas may have your dwarves trying to smooth walls too close to [[magma]] or a [[river]].

====Sweatshop ([[mason]])====
Make one or more [[mason's workshop]]s in an area with a bunch of junk stone you don't care about, or that you're actively looking to clear. Change the workshop settings to allow only your reservists to use it, then tell the workshop to churn out crafts, junk furniture, stone blocks, and trade goods that you can trade en-masse. Alternatively, forbid your reservists from working in your real mason's workshops, order lots of stone constructions built, and pray that your real masons stay too occupied with the workshops to intrude. Works well in conjunction with a gulag. Alternate ideas for sweatshops include a [[mechanic's workshop]] or a [[magma glass furnace]] to train [[mechanic]] and [[glassmaker]] respectively. ''Note: Do NOT try this with the [[carpenter]] skill, or any other resource you don't have in near-limitless abundance. Sweatshops will consume huge amounts of their associated resources, and if you run out mid-way you have probably wasted your time. This includes [[coke]] or [[charcoal]] used in the normal (non-magma) [[glass furnace]].'' 
'''Pros:'''
*Quantitatively turns a profit. The inferior trade goods can be dumped on the next caravan for more useful commodities like bags, seeds, and logs. Logs are especially useful, since you'll inevitably stamp out lots of bins to support the trade good output.
*Mass-producing blocks makes your constructions higher value.
*Unlike many other training programs, Sweatshops train a skill that is very useful. 
'''Cons:'''
*Slow to level.
*Hard to keep the reservists on task, since they'll need to do plenty of hauling to keep their workshop from becoming chokingly cluttered.
*Can be a logistical nightmare; making bins and organizing hauling for the finished goods can be insane if you're working from a gulag.
*Can be dangerous depending on the biome and location of your sweatshops.
*Note also that stone blocks cannot be made into furniture or stone crafts. This may or may not be an issue depending on where you're putting your gulag.

====Dwarf Powered Mill ([[grower]],[[cook]],[[miller]])====
Start off by creating a surplus of [[longland grass]], [[cave wheat]], and/or [[whip vine]] and some bags. Create multiple [[quern]] all close to the food stockpile which contains the millable plants. Next to this area make a [[kitchen]] assigned to an experienced cook. Enable milling for the dwarves you wish to cross-train and order the cook to make lavish meals. As long as your growers provide a steady supply of millable plants and your cook can empty out bags quick enough, the milling jobs will continue. 
'''Pros:'''
*Produces a lot of wealth as flour is a high value ingredient
*Produces high amounts of food
*Sustains the training of non cross-training dwarves such as the cook and growers 
'''Cons:'''
*Requires a surplus of millable plants to ensure continuous milling, thus you may need to increase the number of plots/growers
*If you don't have enough bags and your cook decides to go on break you may end up having job cancellations for the millers
*Dedicated haulers will be required to keep all workshops clutter free

====Clear Cutting====
As long as wood hauling is turned off, dwarves will move from one tree to the next without stopping to bring the wood back. On a heavily forested map, this means that dedicated wood cutters can skill up very quickly. 
Of course, this training strategy isn't going endear you with the elves. 

'''Pros:'''
*Works quickly
*Trees regrow
*Provides useful lumber to carpenters, charcoal makers, etc
*Can cause problems with elves
'''Cons:'''
*<s>Can cause problems with elves</s>
*Map dependent
*Unless care is taken to only designate a small area for cutting, trainees and haulers can be spread out across the map while, making them vulnerable to creatures and ambushes. (OTOH, if done with more than a few dwarves at a time, a small squad of axe-wielding [[military|recruit]]s is not completely defenseless, and military can be stationed as support.)

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

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

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

====Charm School ([[social skills]])====
(Note: Inspired by [http://www.bay12games.com/forum/index.php?topic=47533.0 milaga's Real Wagon experiment], details of this technique are still being investigated.)
Sure, dwarves get stronger, tougher, and more agile from flinging rocks, carving rocks, smoothing rocks, and taking inventory of rocks or assigning tasks regarding rocks. But since the current version{{version|0.28.181.40d}} weights every skill equally in terms of producing attribute increases, dwarves gain attributes from just standing around and chatting, too!

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

'''Pros:'''
*works on any map
*easy to set up
*trains many dwarves at once
*requires almost zero player oversight
*easily scales to any size of immigrant wave
*requires no resources the dwarves would not already be consuming (food, beds, &c)
*levels quickly: initial tests show 14-15 attribute gains per dwarf by the end of 7 months
*very safe
*no conflict with existing workshops or skills, unlike gulag or sweatshop

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

====National self-defense training====
This is the counter-part to the above - this trains civilians in basic wrestling. All your civilians - or at least, most of them. Any time a dwarf is activated into the military, and they do not have at least Novice level in some combat skill, they get a bad thought. Give every civilian dwarf one or two weeks off when they first [[migrant|immigrate]] and train them up to [[experience|Novice]] in [[wrestling]] - that's all they need. Then, if they ever get caught where they don't want to be (maybe they bump into a thief coming around a corner, or a flying critter jumps them, or you need to urgently order them out of the path of a magma flood, or send them to the [[control room]] - anything), not only can you activate them with no bad thoughts, but every dwarf has a better chance at not-dying - which can only be a good thing.

===Overview===
*The charm school can cross-train many dwarves in less a year, but produces no useful items, trade wealth, or professional skills. The method is also still being refined and potential pitfalls may still be uncovered.
*The gym also trains large amounts of dwarves, though it is relatively slow compared to other methods.
*Artillery training can give you some siege operators, which will be useful if you have ballistae.
*The internship is very fast, but only trains up one dwarf at a time. Your stocks could also lag behind if you are unlucky.
*The gulag requires planning, and your dwarves in the fortress proper may run all the way to the gulag to grab a stone for some crafts, a chair, etc. It does, however, train your dwarves in mining quickly, which is always a useful skill.
*Renovation is hands-free, but may bloat your fortress wealth too quickly.
*The sweatshop creates a large amount of goods, which can be traded away to keep traders happy. It also increases your wealth by quite a lot, which can be good or bad depending upon your situation. The goods are also difficult to manage.

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

----

=Army corps of engineers=
Your actual soldiers are obviously only one facet to your military preparation. [[defense|Defensive]] structures like [[fortification]]s, [[moat]]s, and above-ground bunkers need civilian support, and they need to be constructed - and sometimes that's as dangerous as military service itself. In the best of times it should be done quickly and efficiently, because faster means less time vulnerable to a possible [[ambush]] or dangerous [[creature|predator]]. In emergencies, having a trained, reliable workforce, with enough manpower to tackle any job at any time and can accomplish those projects quickly can be a fortress saver.

The incredible amount of effort required to complete full defensive preparations on many maps (even building a single-floor above ground bunker can take multiple seasons of full-time effort) means that the military can benefit greatly from having a corps of dwarves who are dedicated and trained to support the development full time.

Organizing a Corps of Engineers requires extra effort and planning on your part, but pays off big later on. Corps engineers become incredibly useful and will produce superior, happiness-inducing structures and items even after their chief issues are done. Also, since their highest [[strange mood]] eligible skill tends to be [[masonry]], it improves your chances of getting a legendary [[mason]], which is always a treat.

===Organizing===
The bread and butter skill of the engineer corps are [[masonry]] along with [[mechanics]], and some [[architecture]] thrown in for some trainees (but not necessarily all, see below). Candidates really don't need any prior skills, but if you can recruit some [[immigrant]]s that come with one of these skills already, so much the better. The long term result is a crew that can build anything anywhere, but not until after some training, so you should not use any dwarves who will be needed elsewhere soon. Assign [[potash maker]]s, [[soaper]]s, and the like instead. Miners that have run out of digging work and are suddenly idle (and already have [[attribute]]s for faster hauling of building stones) are also good candidates. You may wish to swap [[masonry]] with [[carpentry]] if you are doing a challenge where your structures are chiefly made out of wood, or conceivably even a [[metalcrafting]] skill, but the gist of it is the same.

Since these dwarves may be performing a lot of construction outside, one variation includes designating them all with the [[woodcutting]] [[labour]], so they will all carry [[axe]]s full time. When wood needs to be cut, one tight area is designated at a time, and they all respond - this encourages mutual support. Other outdoor activities likewise become safer with a number of armed dwarves responding together, and faster with practice, so [[plant gathering]] may be another skill to add to the mix. Assigning war[[dog]]s to these outdoor-engineers is another good plan. (Whether or not to then train them as (reservist) axedwarves is up to you - see [[Cross_training#Cross-training_(starting_a_reserves_program)|cross-training]], at the first half of this article.)

A suitable number of engineer corps members depends on personal preference and the expected scope of your projects, but you want them to support each other, so perhaps a half-dozen or more for an average fortress, or maybe ~10% total. This might seem like a lot when you have the [[fortress guard]] demanding 10%, the [[royal guard]] demanding another 5%, plus what dwarves you have committed to reserves programs or in the regular army, but your goal is a reliable building crew, large enough so they will not all be "[[on break]]" at once. Remember also that engineer corps members are civilians (with [[attribute]]s) and can be temporarily re-assigned to urgent hauling duty when the need arises, so they are not lost to other support tasks.

After you've decided who you want in the engineer corps, it's suggested that you give them a [[Profession#Custom_profession_labels|custom profession]], to distinguish them in your {{k|u}}nits menu. They behave so much like normal civilians that it's hard to keep track of them if you don't. Don't use "[[Engineer]]", because that is an existing (and different) profession. Some suggestions for custom ranks are "Reserves," "Multi", "Corps Engineer", "CE", or some other profession or abbreviation that makes sense to you.

===Training masons===
Once your main fortress has [[what should I build first|the basics]] and things are relatively settled, build some [[mason's workshop]]s for the corps to work out of. Build as many as you have corps engineer members, to make sure that everyone is guaranteed to have work, and do it in areas that are dense with mined stones, preferably in low-traffic areas (but be careful about [[noise]]). A good place to start is anywhere you want to clear of (useless) stone, or any [[economic stone]] you want to turn into building [[block|material]] - that's what they'll be producing, and a lot of it.

After the corps' workshops are set up, we'll need to change the workshop profiles to make sure the regular masons don't use them. You can do this one of two ways. First, {{k|q}}uery the workshop, and choose {{k|P}}rofile to see who is allowed to work there. Then, either:
:*Lower the max skill threshhold to "Proficient" (or your choice). This lets different trainees swap workshops.
:*Or, enable each of the engineer corps' members individually. Tedious, but only needs to be done once, and very effective. This allows you more control over individual engineers over an extended period.
:* Or both.

Then, set the corps' workshops to produce stone [[block]]s, and put that on {{k|r}}epeat. Keep it there. This is going to be the corps' only job for it's few seasons, to train up masonry.

====(Why are we building blocks, again?)====
A couple of reasons. 
:* 1) Blocks have no quality modifier. That means that your dabbling mason engineer corps members are producing blocks every bit as good as your legendary masons.
:* 2) Blocks can be used in building constructions. What was the Corps' first job? Building, of course!
:* 3) Blocks make higher-value constructions than normal stone. Constructions made out of stone will become "Rough (rock) (construction)", while block constructions will eliminate the rough modifier and contribute more to the fortress's wealth.
:* 4) Blocks can be collected into bins (which is not true of raw stones), reducing stone clutter. This is important for moving them to handy on-site stockpiles.
:* 5) Blocks make it easier to budget stone for constructions, so you can see if you're running low on material or using more than you expected.

If you stop at no-label, you will have added 37 blocks/trainee to your stocks: 17 to Novice, and another 20 to No-Label. ''(See [[Experience]] for more info.)''

(If you're training carpenters, you can either mass-produce barrels and bins (you always seem to need more), or, if you are planning wooden constructions, wooden blocks.)

=== Apprentice Mechanics ===
Mechanic skill is important to place [[lever]]s and link them with existing devices, for traps or bridges, or whatever. It also allows them to reload [[trap]]s, and/or clear any that may have jammed, relieving your primary Mechanic of this burden. The importance of this skill depends on the extent of your use of levers and traps in your fortress design.

After you're satisfied with the skill level of your trainees (no-tag is a good place to be), move on to training [[mechanic]]s. Shut down the [[mason's workshop]]s and build [[mechanic's workshop]]s where there is more ([[economic stone|non-economic]]!) stone. Start churning out (no-/low-quality) mechanisms - again, 17 each will give Novice level, another 20 each will give No-Label. After you've got a decent handful, you may decide to build experience by building levers and linking them all a door. Don't go too overboard with training mechanics. Again, no-label is a good place to be, ample - you're just speeding things along a bit. Mechanics are not usually used enough to warrant going all out.

===Architect(s)===
Architecture is useful because dwarves trained in it will increase the quality of the structures they design, and so seeing them will cause happy thoughts. Factor in how easy it is to train up and it's a no-brainer. Of course, feel free to stop this at any time to attend to more urgent matters.

After you're done with mechanics, switch to [[architecture]] on some of your trainees. Only a few [[construction]]s and workshops need architecture, and only one architect can work on any designated structure at a time, regardless the size, so you don't (necessarily) need them all to have it. If you have one, they will train up as they build - if you have a lot, they will share the tasks and not achieve higher levels unless you stop and specifically give them more dedicated training.

The easiest way to train any number of architects is to turn off their [[masonry]] labor* and designate a bunch of supports (you will eventually need 17/trainee, just to start). Use the any nearby stone or blocks that is not needed elsewhere - designate one support over one stone if you can, to reduce hauling time. After they've been designed (and now "need masonry"), ''un''-designate them ({{k|q}}, {{k|x}}. If you want to actually build them, then keep masonry on, and that would train both architecture and masonry, giving you more net experience.

''(* Other dwarves with masonry may respond to build the designed supports, and faster than you'd expect, the little masonic ninjas. If this is a concern, lock your trainees in a room with the stone and let 'em design in peace.)''

===The payoff===
After the training starts taking hold, you will have a cadre of proficient building designers, proficient masons, skilled mechanics, and (optionally, see below) proficient siege operators or axe-dwarves. This can happen in as little as 3 years of training. You can (and should!) continue to train them until they are legendary in all of these, but that is very long term. In the shorter, 3 year term, you have a rock-solid foundation to react to any construction demand with speed, efficiency, and awesome quality.

===Non-professionals===
Remember that every dwarf in this crew will have masonry and mechanic labor designated (and possibly carpenter, etc) - for your primary mason's and mechanic's workshops, go into those workshop Profiles and only allow your primary, best-skilled dwarves to respond to work orders there, either by name or skill level, or both. If you forget to do this, you'll have your trainees jumping in and producing your furniture at lower [[quality]].

===Role in your military===

Especially if you opt for the wood-cutter approach and they are armed 24/7 with axes, a brief (or not so brief) [[sparring]] session will make them extremely dangerous if ambushed, and create a reserve force to support your full-time military. Just be careful to train no military skill near [[Soldier#Heroes_and_Champions|Great]] level, as this will remove them permanently from the civilian workforce! Not even close - remember that combat gives experience quickly. Somewhere between Proficient and Professional should be ample for reserves. This is true for axe or [[wrestler]], both of which can be handy for combatants.

You can also, at your discretion, enable the [[siege operating]] labor to train the engineer corps in the use of artillery. This is mainly to give them an actual military use, and since cross-training them like this reduces the military's overall impact on your society. If you've got enough dwarves to make a separate artillery corps, go right ahead.

{{Military FAQ}}

[[Category:Military| ]]
[[Category:Fortress defense]]

40d:Strange mood

2010-01-30T20:31:20Z

Adeptable: gr

Periodically, individual dwarves are struck with an idea for a [[legendary artifact]] and enter a '''strange mood'''. Dwarves which enter a strange mood will stop whatever they are doing and pursue the construction of this artifact to the exclusion of all else. This will be based on a particular [[skill]] that creates a finished end product that can have a [[quality]], rather than intermediary material such as bars of metal or raw food. They will not stop to eat, drink, sleep, or even run away from dangerous creatures. If they do not manage to begin construction of the artifact within a handful of months, they will go [[Strange mood#Failure|insane]] and die soon afterward.

A dwarf will only be struck by a mood once in their lifetime. Upon completion of their artifact they will usually become [[legendary]] in that skill, and will then return to their normal life in the fortress with their newfound skill. A fortress can have at most one dwarf in a strange mood at any one time.

==Overview==
The entire process can be summarized as follows:
# Strange moods can only occur when the below necessary [[#Conditions|conditions]] are met. [[baby|Babies]] and activated [[Soldier]]s with military skills cannot enter moods, nor [[Noble#Immigrant_Nobles|immigrant nobles]], but any other dwarf can, including [[child]]ren.
# The game will pause, center on a dwarf, and announce that the dwarf has entered one of five different types of strange moods. The [[#Types|types of mood]] are listed below. While in a mood, a dwarf will display a blinking exclamation point (see [[status icons]]).
# For the duration of the mood, the dwarf will claim a workshop related to the skill that the mood affects (not all skills are eligible), kick out any dwarf who was using it, and render it otherwise unusable until the mood has been resolved. If a moody dwarf does not claim a workshop, it is because the appropriate workshop does not exist. (See [[#Skills and workshops|skills and workshops]] below to determine which workshop(s) might be required.) A moody dwarf will ''not'' be available to build a needed workshop; another dwarf with the appropriate [[labor]] designation must do so for them, if one is necessary.
# After claiming a workshop, the dwarf will set about collecting the required materials for their artifact. If the dwarf remains idle inside the workshop, it's because they cannot find the right material. Reference the [[#Demands|demands]] section to determine what may be required.
# Once all materials have been gathered, the game will once again pause and center, and the moody dwarf will begin construction. Upon completion the dwarf will create a semi-random artifact related to the skill affected and gain [[legendary]] (or higher) status in that skill (unless the mood type is [[#Possessed|possessed]]). See the [[#Skills and workshops|skills and workshops]] for information on which skills can be gained, or the [[#Artifacts created|artifacts created]] section for more details on the artifacts themselves.

== Types of moods ==
For each of the following types of moods, the first message is how the mood is [[Announcement|announced]]; the second message appears in the dwarf's profile when he or she is viewed with the {{K|v}} key. All moody dwarves will have "Strange Mood" listed as their active task.

=== Fey ===
* {{Gametext|<dwarf> is taken by a fey mood!|#fff}}
: ''Has the aspect of one fey!''

This is the most basic strange mood. Fey dwarves will clearly state their demands when the workshop they are in is examined.

A fey dwarf's happiness is automatically set to 'quite content'.

=== Secretive ===
* {{Gametext|<dwarf> withdraws from society...|#ccc}}
: ''Peculiarly secretive...''

Secretive moods are the same as fey moods, except a secretive dwarf will sketch pictures of their required materials instead of clearly stating their demands if they cannot find what they need. Descriptions of all these [[Mood#Demands|secretive requirements]] can be seen only by viewing the workshop that the moody dwarf has claimed, with {{k|q}}, and then only while the dwarf is waiting inside it. More than one "picture" is likely; these will cycle through the entire list automatically if any one is not available. (Since materials are gathered ''in order'', it's quite possible that only one of a long list is needed to allow the moody dwarf to continue on their project. If the dwarf has gathered some of the materials (seen as "tasked" when looking at the workshop with {{k|t}}), then the next in the list is what they are looking for.)

A secretive dwarf's happiness is automatically set to 'quite content'.

=== Possessed ===
* {{Gametext|<dwarf> has been possessed!|#f0f}}
: ''Possessed by unknown forces!''

Possessed dwarves have cryptic material requests, and have the unfortunate distinction of not receiving any experience upon successful construction of an artifact. It is unknown if controllable circumstances lead to a possessed mood instead of one of the more desirable fey or secretive moods. Possessed dwarves will mutter the name of the artifact they are working on once they have all the materials they need.

A possession is the only mood that does ''not'' result in a jump in [[experience]].

A possessed dwarf's happiness is automatically set to 'quite content'.

=== Fell ===
* {{Gametext|<dwarf> looses a roaring laughter, fell and terrible!|#a0a}}
: ''Has a horrible fell look!''

A dwarf that goes into a fell mood will always take over a [[butcher's shop]] or a [[tanner's shop]]. The dwarf will then ''murder'' the nearest dwarf, drag the corpse into the shop and make some sort of object out of dwarf [[leather]] or [[bone]]. Once the artifact is completed, the fell dwarf will become a legendary [[bone carver]] or [[leatherworker]]. Strangely, none of the other dwarves seem to mind the murder. Only unhappy dwarves may enter a fell mood.

Aside from the potential loss of an important dwarf in the wrong place at the wrong time, there doesn't seem to be any downside to a fell mood. The end result is always an artifact and a legendary craftsdwarf. Since the only ingredient used (a dwarf) is available in abundance, a fell mood will only fail if the fell dwarf is completely isolated from other dwarves, or if the proper workshop does not exist.

=== Macabre ===
* {{Gametext|<dwarf> begins to stalk and brood...|#777}}
: ''Brooding darkly...''

Macabre moods are similar to fell moods, but the dwarf will not murder a fellow dwarf. A macabre dwarf may require bones, skulls, and chunks/remains; if you do not happen to have any, you will have to "make" some, or let the moody dwarf go insane. Like fell moods, only unhappy dwarves can enter macabre moods.

{{Spoiler}}

== Demands ==
Once a workshop is claimed, the dwarf will begin collecting materials. Each artifact will require between one and ten materials to complete. If the moody dwarf remains idle, then the necessary materials are not available. [[Forbidden]] items must be reclaimed ({{K|d}} - {{K|b}} - {{K|c}}) before they may be used, but moody dwarves will ignore settings regarding [[economic stone]]. Press {{K|q}} and highlight the workshop to receive a series of clues about what the dwarf needs. Hints that stay active for longer than 2 seconds mean that multiple pieces of that material will be required; each single demand will be displayed for 2 seconds, so if it says "gems... shining" for 6 seconds, 3 gems are demanded. Materials will always be fetched ''in order'', so if at least one item has already been retrieved (the items will show up with "TSK" ("task") next to them when the workshop is viewed with the {{K|t}} context menu), it will usually be possible to tell what item is required next.

You can use this to your advantage to get your dwarf to pick specific types of items, even if the moody dwarf has already started storing materials in their workshop: if a fey weaponsmith starts piling up copper bars, forbid those bars and he'll go pick another bar instead. If you forbid all metals except say steel (the stocks screen makes this fairly convenient), then he'll skip all those other metals and make his artifact weapon out of strong, valuable steel instead of whatever random inferior metal he might have picked otherwise. Don't forbid any of his materials after your dwarf has begun building his artifact - he won't go back to collecting materials once started and will end up going insane.

Note though that if a dwarf has a demand for a specific item, such as a [[bar|bar of metal]], raw [[gem]], or [[shell]], then that item type will be ''required''. For this reason, it is usually a good idea to keep an example of each item type on hand, particularly cut and raw gems, shells, bones, leather, raw (green) glass, both silk and plant cloth.

In somewhat rarer cases, a dwarf with a personality preference for a specific material, such as steel or silver [[bars]], will demand exactly that specific sub-type of material. For this reason, it is a good idea to keep as many types of material on hand as possible, including the three different kinds of glass. Forbidding materials won't let you get around this either: if they want a specific material subtype and you forbid it in favor of something else, they'll just sulk in their workshop until you unforbid the material or they are able to find it some other way - or they go [[insane]]. Asking a liaison for likely materials ''in advance'' is a good plan - "next year" is far too long for a moody dwarf to last. Check your dwarves' [[preference]]s if you care.

Once you have struck [[Adamantine]], all moods which use cloth or metal as a primary component will insist on using Adamantine cloth or wafers over all other materials; moody dwarves which happen to want metal for decorations will still choose bars based on distance or preference. Moods involving stone crafting or masonry will not prefer [[raw Adamantine]] over other stones.

The various demands are translated here:

:{| class="wikitable" style="text-align:left;width:90%;"
|-
! Material
! Fey
! Secretive
! Possessed
|-
|
| <dwarf> screams "I must have <demand>!"
| <dwarf> sketches pictures of <demand>.
| <dwarf> mutters "<artifact> needs <demand>..."
|-
| [[Stone]]
| rock
| a quarry
| stone... rock
|-
| Stone [[block]]
| rock blocks
| square blocks
| blocks... bricks
|-
| [[Wood]]
| wood logs
| a forest
| tree... life
|-
| Metal [[bar]]
| metal bars
| shining bars of metal
| bars... metal
|-
| [[Gem]]s (cut)
| cut gems
| cut gems
| gems... shining
|-
| [[Gem]]s (raw)
| rough gems
| rough gems
| rough... color
|-
| [[Glass]] (green)
| raw green glass
| glass
| raw... green
|-
| [[Glass]] (clear)
| clear glass{{verify}}
| glass and burning wood
| raw... clear
|-
| [[Glass]] (crystal)
| crystal glass{{verify}}
| rough gems and glass
| raw... crystal
|-
| [[Bone]]
| bones
| skeletons
| bones... yes
|-
| [[Shell]]
| shells
| a shell
| a shell...
|-
| [[Leather]]
| tanned hides
| stacked leather
| leather... skin
|-
| [[Cloth]] (plant)
| plant fiber cloth
| stacked cloth
| cloth... thread
|-
| [[Cloth]] (silk)
| silk cloth
| stacked cloth
| cloth... thread
|}

====Known quirk====
On maps with magma, dwarfs* who intend to create an artifact at a [[forge]] or [[glass furnace]] may only be willing to use a standard (non-magma) version, or only a magma version, and will find the other completely unacceptable. If they are just standing around, then they won't use the type you have, and you will have to build the other type for them (though no [[fuel]] will be required if using a standard, non-magma version).
:''(* This would include most all [[armorsmith]]s, [[blacksmith]]s, [[metalsmith]]s, [[weaponsmith]]s, and [[glassmaker]]s, and any whose mood is dictated by the relevant skills.)''

== The mechanics of moods ==

=== Frequency===
When a fortress is started, an internal counter is set to 1000. Around 11 or 12 times per day, this counter is decremented by 1, running down to zero in about 3 months. When the counter would ordinarily be decremented when it has already reached zero, there is a 1 in 500 chance that a strange mood will strike. This means that, once all conditions are met and the clock is ticking, while there is approximately a 2.4% chance of a strange mood per day, or ''very approximately'' a 50% chance of a strange mood per month, there is no guarantee when a mood will strike - might be sooner, might be (almost) never.

=== Conditions ===
In order for a dwarf to be struck with a strange mood, three conditions must be met:
:* There is no currently active strange mood,
:* The maximum number of artifacts is not met,
:* There are at least 20 eligible dwarves ''(see below)''.

If all three of these conditions are true, the game may trigger a strange mood according to the frequency.

==== Maximum number of artifacts ====
The maximum number of artifacts in any one fortress is limited by the lower of:
* The number of items created divided by 200. It is unknown whether mined-out rock counts as an "item created", or whether bolts and units of drink are counted individually.
* The number of revealed [[subterranean]] tiles divided by 2308 (this is an area equivalent to a 48x48 square). Using [[Exploratory mining|exploratory methods]] is a great way to increase your artifact limit.
[http://www.bay12games.com/forum/index.php?topic=46803.0 Anecdotal evidence] indicates that obsidian farming will affect at least one of these limits.

==== Eligibility ====
The deciding factor for eligibility is a dwarf's actual [[profession]]. ''(Note that "[[Skill#Custom profession labels|custom professions]]" have no effect on this!)'' Thus, dwarves may enter strange moods regardless of what skills they have or don't have, so long as they are of an acceptable profession. Dwarves who have already created an artifact are not eligible to create another, and since every mood ends in either an artifact or death, every dwarf may enter at most one mood. Dwarves who have obtained one or more legendary skills without creating artifacts may enter strange moods.

Appointed [[nobles]] may enter moods as per their default profession, but [[Noble#Immigrant Nobles|immigrant nobles]] are '''not''' eligible for moods. That includes:
:Advisor, Baron/ess, Baron/ess Consort, Count/ess, Countess Consort, Duke/Duchess, Duke/Duchess Consort, Dungeon Master, Hammerer, King/Queen, King/Queen Consort, Philosopher, and Tax Collector.

Further, dwarfs with a [[Soldier#Soldier professions|military profession]] other than "Recruit" can '''not''' enter moods. Incidental military skills make no difference - eligibility (and weighting) depends purely on the actual ''[[profession]]'', as listed at the time. Military professions include:
:Axedwarf, Axe Lord, Champion, Crossbowdwarf, Elite Crossbowdwarf, Hammerdwarf, Hammer Lord, Macedwarf, Mace Lord, Marksdwarf, Elite Marksdwarf, Speardwarf, Spearmaster, Swordsdwarf, Swordmaster, Wrestler, and Elite Wrestler.

Babies may '''not''' enter moods.

Any other profession is eligible to enter a mood, but not all have the same ''chance'' to enter a mood...

:''('''Note''' - Specifically, and to avoid previous misunderstandings, [[Strand extractor]], [[Clerk]], [[Administrator]], [[Trader]], [[Architect]], [[Alchemist]], [[Soldier#Recruits|Recruit]] and [[Child]] '''are''' moodable professions.)''

=== Chance ===
When determining who will have a strange mood, each eligible dwarf is put into a weighted lottery. The odds are assigned a higher or lower weight based on the dwarf's [[profession]]. The default weight is 6, but some professions are more likely to enter a strange mood than others. (This is like most dwarfs getting 6 tickets to the lottery, and others getting more.)

{| class="wikitable" cellspacing="0" border="2" cellpadding="5"
|-
! Weighting
! Professions

|-
| 21 ||Armorer, Blacksmith, Bone Carver, Clothier, Craftsdwarf, Jeweler, Gem Cutter, Gem Setter, Glassmaker, Leatherworker, Metalcrafter, Metalsmith, Stonecrafter, Weaponsmith, Weaver, Woodcrafter
|-
| 11 ||Bowyer, Carpenter, Stoneworker, Mason, Woodworker
|-
| 6 ||All other eligible professions

|}

:'''''Example:''' What this means is: if you had 21 dwarves, made up of 20 eligible farmers, furnace operators, woodcutters & etc (with 6 chances each), plus one Armorer (with 21 chances), that one Armorer would have a 21 in 141 chance (20 dwarves x 6 chances each = 120, + 21 chances more = 141 total) of the mood striking them. That's about 1 in 7, while the other 20 have a 6 in 141 chance each, or about 1 in 24. The odds are still against the armorer, but much better than for any other single dwarf.''

Note that not every profession is from a moodable skill. An Alchemist, Architect, Furnace Operator or Strand Extractor can be taken by a mood, but that will not make those skills legendary, nor will they create an artifact bar of soap, building, bar of metal or wafer of adamantine.

:NOTE: ''If your game was saved shortly before one of you dwarves acquired a mood, reloading that game will most likely cause the chances to be completely re-figured, resulting in a different mood at a different time for a different dwarf with different materials. This is true for most all random events and results in Dwarf Fortress.''

=== Skills and workshops ===

{| class="wikitable" cellpadding="4" style="border:1px solid black;border-collapse:collapse;text-align:left;float:right;margin:0 0 20px 30px;"
|-
! colspan="2" style="background-color:#eee;border-bottom:1px solid black;text-align:center;" | Artifact Skill Rewards
|-
! Highest skill
! Workshop used
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Armorsmith]]
| [[Magma forge]] or [[Metalsmith's forge]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Bonecarver]]
| [[Craftsdwarf's workshop]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Bowyer]]
| [[Bowyer's workshop]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Carpenter]]
| [[Carpenter's workshop]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Clothier]]
| [[Clothier's shop]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Engraver]]
| [[Craftsdwarf's workshop]] or [[Mason's workshop]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Gem cutter]]
| [[Jeweler's workshop]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Gem setter]]
| [[Jeweler's workshop]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Glassmaker]]
| [[Glass furnace]] or [[Magma glass furnace]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Leatherworker]]
| [[Leatherworks]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Mason]]
| [[Mason's workshop]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Mechanic]]
| [[Mechanic's workshop]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Metal crafter]]
| [[Magma forge]] or [[Metalsmith's forge]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Metalsmith]]
| [[Magma forge]] or [[Metalsmith's forge]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Miner]]
| [[Craftsdwarf's workshop]] or [[Mason's workshop]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Stone crafter]]
| [[Craftsdwarf's workshop]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Tanner]]
| [[Tanner's shop]] or [[Leather works]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Weaponsmith]]
| [[Magma forge]] or [[Metalsmith's forge]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Weaver]]
| [[Clothier's shop]]
|- style="border-top:1px solid #aaa;vertical-align:top;"
| [[Wood crafter]]
| [[Craftsdwarf's workshop]]
|}

A dwarf will claim a workshop according to their highest applicable skill, and upon completion of the artifact, gain 20,000 [[experience]] in that skill (excepting [[Mood#Possessed|possessed]] dwarves). This will give the dwarf a legendary-level [[skill]] (specifically, "legendary+1" or higher, depending on the dwarf's initial skill level) and a number of [[attribute]] gains. The table to the right describes all applicable skills and their potential workshop requirements - there are only 20 skills that determine the workshop and that can be affected by a mood (sometimes referred to as '''moodable''' skills.) If a dwarf does not possess at least one of the mooodable skills listed to the right, they will take over a [[craftsdwarf's workshop]] and gain one of [[bonecarver]], [[stone crafter]], or [[wood crafter]] skills, producing an artifact [[craft]].

If a dwarf has the same experience points in two skills (as opposed to same experience title), the first listed for that dwarf will be the one affected by the mood (the exact experience can only be made visible with 3rd party [[utilities]]).

When multiple workshops are listed, the dwarf may require one or the other, so ensure that ''both'' are available, if possible. If you have one, and the dwarf is not interested, then build the other, right away. (i.e. If you have only [[magma forge]]s, you may have to build a standard [[forge]] for the moody dwarf).

Below is a list of all ''non''-moodable skills; if all of a dwarfs skills are found on this list and none from the table to the right, then they have no moodable skills and will construct their artifact at a [[Craftsdwarf's workshop]], producing an appropriate craft as described above:

{|
|- style="vertical-align:top;"
| style="padding-right:30px;" |
* [[Ambusher]]
* [[Animal caretaker]]
* [[Animal dissector]]
* [[Animal trainer]]
* [[Appraiser]]
* [[Building designer|Architect]]
* [[Brewer]]
* [[Butcher]]
* [[Cheese maker]]
* [[Cook]]
* [[Dyer]]
* [[Fish cleaner]]
* [[Fish dissector]]
* [[Fisherdwarf]]
* [[Furnace operator]]
* [[Grower]]
* [[Herbalist]]
|
* [[Lye maker]]
* [[Milker]]
* [[Miller]]
* [[Potash maker]]
* [[Pump operator]]
* [[Record keeper]]
* [[Siege engineer]]
* [[Siege operator]]
* [[Soaper]]
* [[Strand extractor]]
* [[Thresher]]
* [[Trapper]]
* [[Wood cutter]]
* [[Wood burner]]
* All [[military]] skills
* All [[social skill]]s
|}

This fact can be utilized to maximize the possibility of getting a dwarf with the specific legendary skill you want: since ''non''-moodable skills are ignored, when ever possible make sure that each dwarf's highest ''moodable'' skill is one of those you want*. Have all your peasants, [[farmer]]s, non-professional military and other dwarves without any moodable skills do a tiny bit of work in the skill(s) you most want; if a "[[dabbling]]" skill is the highest moodable skill they have, that is the skill that will be used.

:''(* [[Armorsmith]], [[Weaponsmith]], [[Metal crafter|Metal Crafter]] and [[Metalsmith]] are possibly the most-desired legendary skills, but much depends on your fortress, your current mix of skills, and your play style.)''

:''(Note that [[Tanner]] is a moodable skill, the only [[Farmer]] category skill that is moodable.)''

== Artifacts created ==
The type of artifact created will depend on the dwarf's highest skill. Masons will always create some kind of stone object, usually furniture; bone Carvers, a bone or shell object; carpenters, a wood object, etc. Miners and engravers will usually turn out a stone craft or piece of furniture; metalworkers, metal crafts, weapons, or armor (depending on the type of metalworker); weavers, an article of clothing; tanners, a leather armor or object. If a dwarf has no moodable skills, they will take over a [[craftsdwarf's workshop]] and create a bone, stone or wood craft of some type. The precise type of craft created is usually somewhat random but if a dwarf has a personality preference for a particular thing, such as gauntlets or floodgates or crowns, and that thing is an available choice given the dwarf's profession, he will generally create an object of that type.

The first object grabbed by the dwarf will be the "primary" substance; all other materials will be used to decorate the artifact. If a dwarf grabs a piece of [[chalk]] and makes a statue, for instance, it will be a "chalk statue", but an artifact can potentially be composed of bone, cloth, gems, leather, metal, shell, stone, and wood all at once. In some cases, a moody dwarf will produce an item which normally cannot be made from that material, leading to such odd constructions as an [[obsidian]] [[bed]], [[ruby]] [[floodgate]], or turtle [[shell]] [[cage]].

Once created, most [[artifact]]s will be available for use just like a normal item of its type. Artifact furniture is useful for high value [[noble]] rooms. [[Weapon]]s and [[armor]] will only be used by heroes and champions. Artifact weapons in [[Trap#Weapon Trap|weapon traps]] can also boost a room's value considerably, as in the case of artifact trap components.

== Failure ==
If you can't provide the desired workshop and all the required component materials within a couple of months, the dwarf will go [[insane]], which cancels the mood and the artifact. As if that's not bad enough, any dwarf who goes insane will soon die, one way or another.

A dwarf who is [[melancholy]] or [[stark raving mad]] is harmless to others (until they die and start a [[tantrum]] spiral), but a [[berserk]] dwarf will attack other dwarfs and possibly pull levers at random. You may want to station a squad nearby or assign a few war dogs to the dwarf on the chance that they will lash out. If you build your workshops inside enclosed rooms with doors you can also lock the moody dwarf in the room until he or she starves. In extreme cases, building a wall around an open workshop is the best precaution.

Most events that would ordinarily interrupt a dwarf will not deter a moody dwarf - for example, while passing out from pain will cancel most tasks, a moody dwarf will continue working as soon as he wakes up. Giving birth while in a strange mood does not interrupt the dwarf either; the new mother will ignore the baby until her mood is resolved and it will happily wander off in the meantime.

Severe distractions such as hostile creatures, however, can interrupt a strange mood, resulting in immediate insanity; similar results will happen if the workshop suddenly becomes unavailable, whether from being destroyed (by a cave-in or a dwarf throwing a tantrum) or from losing power (in the case of magma workshops). Note that the insanity can happen even when the dwarf is not deadlocked on an item; there have been observed instances where a dwarf goes insane while in the process of carrying a required item back to the commandeered workshop.

----

'''See also'''
:*[[Insanity]]
:*[[Legendary artifact|Artifact]]
:*[[Profession]]
:*[[Legendary|Legendary Skill]]

40d:Statue

2009-10-27T02:10:44Z

Adeptable: /* Statues versus mechanisms */ clarify

Statues are [[buildings]] which can be built from the {{k|b}}uild menu under {{k|s}}tatue. They can be made using one [[stone]] at the [[mason's workshop]], one bag of [[sand]] at a [[glass furnace]], or three bars of [[metal]] of the same type at a [[metalsmith's forge]] (via the [[Blacksmith|blacksmithing]] [[labor]]).

Statues have a [[item value|base value]] of 25, compared to 10 for all other types of furniture. This makes them a good choice for raising the value of [[room]] — to create a legendary dining room, for instance, or to meet [[noble]]s' requirements for rooms of a certain value. The final value of a statue can vary greatly depending on its [[quality]] and [[material]]; a no-quality regular stone statue is worth only 25☼, whereas a masterpiece platinum statue is worth 12,000☼.

You can create a [[sculpture garden]] from a statue's {{k|q}}uery menu. Dwarves will spend time at a statue garden appreciating the statues (which generates a happy [[thought]]) and may even organize parties there. For the purposes of building appreciation, it is the quality of the statue, not its overall value, that is important: a masterpiece stone statue will generate a happier thought than a base-quality platinum one.{{verify}}

Be careful when placing statues, because dwarves cannot move through the same square they occupy. (This will also prevent dwarves from [[smoothing]] or engraving the floor underneath a statue.) A poorly placed statue can potentially seal off parts of your fortress.

==Ore-based statues==
It is more efficient, as far as [[value]] and time spent are concerned, to make statues from ore rather than to smelt 3 ores into 3 bars to make a metal statue. [[Silver]], [[gold]], [[platinum]], and [[aluminum]] statues, especially, should be made from raw [[ore]] instead of from smelted [[bar]]s (for instance, native gold instead of gold bars). Ore is treated as a type of [[stone]], and making a statue out of it only requires one unit of ore at a [[mason's workshop]], versus three bars at a [[metalsmith's forge]] plus [[fuel]]. A statue made from ore still has the same value as one made from metal bars, and it is easier to get a high-skill [[mason]] than a high-skill [[blacksmith]], further increasing the reasoning for ore-based statues. Other ores may seem to be not a good choice if the resulting alloy is [[Metal#List of metals|considerably more valuable]] than the base metals, but the 3:1 difference in materials consumed would not even be balanced by skill between the crafters (which at most could create a 2:1 quality value difference).

However, a dwarf's good [[thought]]s do not come from value, but from perceived [[quality]] of items they enounter, and that quality can be affected by their [[preference]]s. Stone and metal [[preference]]s are separate, and listed in that order (ore first, metal second). It's possible for a dwarf to have a fondness for native aluminum ore but be unimpressed by that metal, and likewise a dwarf who prefers the metal won't be extra-satisfied by a statue carved from the ore. So, if a dwarf's [[preference]]s are for a metal rather than an ore, or a mandate calls for it, and that's your goal, there is no substitute.

By default, ore is reserved for use for [[smelting]]. To lift this restriction, press {{k|z}}, then go to "stone" and enable (make green) whichever ore(s) you wish to use. To get your mason to use the ore, it must be the nearest type of stone to the mason's workshop. This technique can also be used to make high-value ore-based stone [[craft]]s at a [[craftsdwarf's workshop]].

==Statues versus mechanisms==
As an alternative to building statues to increase a room's value, you can use [[mechanism]]-based structures such as [[gear assemblies]] and [[lever]]s, which have a base value of 30, versus 25 for statues. An additional advantage is that these structures, unlike statues, do not block the passage of dwarves. And levers are useful for, you know, controlling stuff.

To build high-quality levers and gear assemblies, you will need to make high-quality mechanisms, which requires a [[mechanic]] instead of a [[mason]]. By using the techniques detailed in ore-based statues, above, you can make very high-value mechanisms out of ore. (Unfortunately, this technique cannot be used to make [[magma-safe]] mechanisms from the ore of a magma-safe metal, as ores have a different melting point than bars.)

{{buildings}}
[[Category:Furniture]]

40d:Magma-safe

2009-09-27T01:27:51Z

Adeptable: /* Calculations */ tidy up syntax

'''Magma-safe materials''' are known to include [[iron]], [[steel]], [[bauxite]], [[fire imp]] [[bones]] and [[leather]], [[nickel]], [[nickel silver]] and [[adamantine]], but currently it is difficult to control [[magma]] flow with [[floodgate]]s since [[mechanism]]s must be made out of [[Rock|rocks]], most of which are not magma-safe (Bauxite being the notable exception).

[[Mechanisms]] made from raw adamantine are magma-safe, and will properly operate a magma-safe floodgate in a magma [[channel]]. In order to construct mechanisms from raw adamantine, you must first allow its use for non-economic purposes in the stock screen ({{key|z}} and select 'stone'). You might wish to remove other stone-using jobs while adamantine is available for use.

If you are using bauxite, be sure to mark a [[stockpile]] around the [[mechanic's workshop]] which allows bauxite only.

The mechanism on the [[lever|trigger]] need not be magma-safe, only the one on the floodgate. If you do not have any bauxite or adamantine available, you can also work around floodgate based flow control by opting for [[screw pump|screw pumps]] to pump the magma over [[wall]]-barriers.

== Calculations ==

According to the raw data files, magma's temperature is somewhere between 1300°C and 1400°C, which translates to 2300°F–2500°F .

Materials that resist magma are:

Earth:
* Constructions ([[Wall]], [[Floor]], [[Ramp]], [[Stairs]]) can never melt or burn (there is nothing wrong with a [[wood]]en magma reservoir). Natural [[ice]] walls/floors/ramps/stairs may melt however.
* [[Fortification]]s will allow the passage of [[magma]], but not the assorted magma creatures. Fire snakes are vermin, so they can spawn anywhere near their native biome - the magma pipe/pool. They are not affected by fortifications, grates, or anything else you might try to throw at them. Also, there is a bug with fluids which may sometimes let magma (and water) push living things through barriers such as fortifications, bars and grates. [[Pump]]s are a positive defense, but can change the dynamics of fluid [[pressure]].

Metal:
* [[Nickel]] — 2600°F (1427°C)
* [[Nickel silver]] — 2600°F (1427°C)
* [[Iron]] — 2680°F (1471°C)
* [[Steel]] — 2710°F (1488°C)
* [[Platinum]] — 3000°F (1649°C)
* [[Adamantine]] — 15000°F (8315°C)

Stone:
* [[Bauxite]] — 3600°F (1982°C)
* [[Raw adamantine]] — 15000°F (8315°C)

Leather:
* [[Fire imp]] [[leather]] — 13500°F (7482°C)

Bones:
* [[Fire imp]] [[bones]] — 14000°F ((7760°C)

== Glass ==
[[Glass]] behaves oddly in regards to magma. Glass is, in itself, not magma safe; glass [[instrument|instruments]] will melt in magma. However, glass [[furniture]] will not. So glass [[statue|statues]], [[screw pump|screw pumps]], and [[floodgate|floodgates]] are all fine when submerged in magma. Forum link with experiments: http://www.bay12games.com/forum/index.php?topic=27423.msg333562#msg333562

{{Magma FAQ}}
[[Category:Physics]]

40d:Magma-safe

2009-09-27T01:26:52Z

Adeptable: /* Calculations */ gr

'''Magma-safe materials''' are known to include [[iron]], [[steel]], [[bauxite]], [[fire imp]] [[bones]] and [[leather]], [[nickel]], [[nickel silver]] and [[adamantine]], but currently it is difficult to control [[magma]] flow with [[floodgate]]s since [[mechanism]]s must be made out of [[Rock|rocks]], most of which are not magma-safe (Bauxite being the notable exception).

[[Mechanisms]] made from raw adamantine are magma-safe, and will properly operate a magma-safe floodgate in a magma [[channel]]. In order to construct mechanisms from raw adamantine, you must first allow its use for non-economic purposes in the stock screen ({{key|z}} and select 'stone'). You might wish to remove other stone-using jobs while adamantine is available for use.

If you are using bauxite, be sure to mark a [[stockpile]] around the [[mechanic's workshop]] which allows bauxite only.

The mechanism on the [[lever|trigger]] need not be magma-safe, only the one on the floodgate. If you do not have any bauxite or adamantine available, you can also work around floodgate based flow control by opting for [[screw pump|screw pumps]] to pump the magma over [[wall]]-barriers.

== Calculations ==

According to the raw data files, magma's temperature is somewhere between 1300°C and 1400°C, which translates to 2300°F–2500°F .

Materials that resist magma are:

Earth:
* Constructions ([[Wall]], [[Floor]], [[Ramp]], [[Stairs]]) can never melt or burn (there is nothing wrong with a [[wood]]en magma reservoir). Natural [[ice]] walls/floors/ramps/stairs may melt however.
* [[Fortification|fortifications]] will allow the passage of [[magma]], but not the assorted magma creatures. Fire snakes are vermin, so they can spawn anywhere near their native biome - the magma pipe/pool. They are not affected by fortifications, grates, or anything else you might try to throw at them. Also, there is a bug with fluids which may sometimes let magma (and water) push living things through barriers such as fortifications, bars and grates. [[Pump]]s are a positive defense, but can change the dynamics of fluid [[pressure]].

Metal:
* [[Nickel]] — 2600°F (1427°C)
* [[Nickel silver]] — 2600°F (1427°C)
* [[Iron]] — 2680°F (1471°C)
* [[Steel]] — 2710°F (1488°C)
* [[Platinum]] — 3000°F (1649°C)
* [[Adamantine]] — 15000°F (8315°C)

Stone:
* [[Bauxite]] — 3600°F (1982°C)
* [[Raw adamantine]] — 15000°F (8315°C)

Leather:
* [[Fire imp]] [[leather]] — 13500°F (7482°C)

Bones:
* [[Fire imp]] [[bones]] — 14000°F ((7760°C)

== Glass ==
[[Glass]] behaves oddly in regards to magma. Glass is, in itself, not magma safe; glass [[instrument|instruments]] will melt in magma. However, glass [[furniture]] will not. So glass [[statue|statues]], [[screw pump|screw pumps]], and [[floodgate|floodgates]] are all fine when submerged in magma. Forum link with experiments: http://www.bay12games.com/forum/index.php?topic=27423.msg333562#msg333562

{{Magma FAQ}}
[[Category:Physics]]

40d:Magma-safe

2009-09-27T01:26:28Z

Adeptable: /* Calculations */ gr

'''Magma-safe materials''' are known to include [[iron]], [[steel]], [[bauxite]], [[fire imp]] [[bones]] and [[leather]], [[nickel]], [[nickel silver]] and [[adamantine]], but currently it is difficult to control [[magma]] flow with [[floodgate]]s since [[mechanism]]s must be made out of [[Rock|rocks]], most of which are not magma-safe (Bauxite being the notable exception).

[[Mechanisms]] made from raw adamantine are magma-safe, and will properly operate a magma-safe floodgate in a magma [[channel]]. In order to construct mechanisms from raw adamantine, you must first allow its use for non-economic purposes in the stock screen ({{key|z}} and select 'stone'). You might wish to remove other stone-using jobs while adamantine is available for use.

If you are using bauxite, be sure to mark a [[stockpile]] around the [[mechanic's workshop]] which allows bauxite only.

The mechanism on the [[lever|trigger]] need not be magma-safe, only the one on the floodgate. If you do not have any bauxite or adamantine available, you can also work around floodgate based flow control by opting for [[screw pump|screw pumps]] to pump the magma over [[wall]]-barriers.

== Calculations ==

According to the raw data files, magma's temperature is somewhere between 1300°C and 1400°C, which translates to 2300°F–2500°F .

Materials that resist magma are:

Earth:
* Constructions ([[Wall]], [[Floor]], [[Ramp]], [[Stairs]]) can never melt or burn (there is nothing wrong with a [[wood]]en magma reservoir). Natural [[ice]] walls/floors/ramps/stairs may melt however.
* [[fortification|fortifications]] will allow the passage of [[magma]], but not the assorted magma creatures. Fire snakes are vermin, so they can spawn anywhere near their native biome - the magma pipe/pool. They are not affected by fortifications, grates, or anything else you might try to throw at them. Also, there is a bug with fluids which may sometimes let magma (and water) push living things through barriers such as fortifications, bars and grates. [[Pump]]s are a positive defense, but can change the dynamics of fluid [[pressure]].

Metal:
* [[Nickel]] — 2600°F (1427°C)
* [[Nickel silver]] — 2600°F (1427°C)
* [[Iron]] — 2680°F (1471°C)
* [[Steel]] — 2710°F (1488°C)
* [[Platinum]] — 3000°F (1649°C)
* [[Adamantine]] — 15000°F (8315°C)

Stone:
* [[Bauxite]] — 3600°F (1982°C)
* [[Raw adamantine]] — 15000°F (8315°C)

Leather:
* [[Fire imp]] [[leather]] — 13500°F (7482°C)

Bones:
* [[Fire imp]] [[bones]] — 14000°F ((7760°C)

== Glass ==
[[Glass]] behaves oddly in regards to magma. Glass is, in itself, not magma safe; glass [[instrument|instruments]] will melt in magma. However, glass [[furniture]] will not. So glass [[statue|statues]], [[screw pump|screw pumps]], and [[floodgate|floodgates]] are all fine when submerged in magma. Forum link with experiments: http://www.bay12games.com/forum/index.php?topic=27423.msg333562#msg333562

{{Magma FAQ}}
[[Category:Physics]]

40d:Magma-safe

2009-09-27T01:25:45Z

Adeptable: add nickel to the initial list of materials

'''Magma-safe materials''' are known to include [[iron]], [[steel]], [[bauxite]], [[fire imp]] [[bones]] and [[leather]], [[nickel]], [[nickel silver]] and [[adamantine]], but currently it is difficult to control [[magma]] flow with [[floodgate]]s since [[mechanism]]s must be made out of [[Rock|rocks]], most of which are not magma-safe (Bauxite being the notable exception).

[[Mechanisms]] made from raw adamantine are magma-safe, and will properly operate a magma-safe floodgate in a magma [[channel]]. In order to construct mechanisms from raw adamantine, you must first allow its use for non-economic purposes in the stock screen ({{key|z}} and select 'stone'). You might wish to remove other stone-using jobs while adamantine is available for use.

If you are using bauxite, be sure to mark a [[stockpile]] around the [[mechanic's workshop]] which allows bauxite only.

The mechanism on the [[lever|trigger]] need not be magma-safe, only the one on the floodgate. If you do not have any bauxite or adamantine available, you can also work around floodgate based flow control by opting for [[screw pump|screw pumps]] to pump the magma over [[wall]]-barriers.

== Calculations ==

According to the raw data files, magma's temperature is somewhere between 1300°C and 1400°C, which translates to 2300°F–2500°F .

Materials that resist magma are:

Earth:
* Constructions ([[Wall]], [[Floor]], [[Ramp]], [[Stairs]]) can never melt or burn (there is nothing wrong with [[wood]]en magma reservoir). Natural [[ice]] walls/floors/ramps/stairs may melt however.
* [[fortification|fortifications]] will allow the passage of [[magma]], but not the assorted magma creatures. Fire snakes are vermin, so they can spawn anywhere near their native biome - the magma pipe/pool. They are not affected by fortifications, grates, or anything else you might try to throw at them. Also, there is a bug with fluids which may sometimes let magma (and water) push living things through barriers such as fortifications, bars and grates. [[Pump]]s are a positive defense, but can change the dynamics of fluid [[pressure]].

Metal:
* [[Nickel]] — 2600°F (1427°C)
* [[Nickel silver]] — 2600°F (1427°C)
* [[Iron]] — 2680°F (1471°C)
* [[Steel]] — 2710°F (1488°C)
* [[Platinum]] — 3000°F (1649°C)
* [[Adamantine]] — 15000°F (8315°C)

Stone:
* [[Bauxite]] — 3600°F (1982°C)
* [[Raw adamantine]] — 15000°F (8315°C)

Leather:
* [[Fire imp]] [[leather]] — 13500°F (7482°C)

Bones:
* [[Fire imp]] [[bones]] — 14000°F ((7760°C)

== Glass ==
[[Glass]] behaves oddly in regards to magma. Glass is, in itself, not magma safe; glass [[instrument|instruments]] will melt in magma. However, glass [[furniture]] will not. So glass [[statue|statues]], [[screw pump|screw pumps]], and [[floodgate|floodgates]] are all fine when submerged in magma. Forum link with experiments: http://www.bay12games.com/forum/index.php?topic=27423.msg333562#msg333562

{{Magma FAQ}}
[[Category:Physics]]

40d:Experience

2009-09-27T01:03:36Z

Adeptable: gr

'''Experience''' represents how much a certain [[dwarf]] (or other [[humanoid|intelligent creature]]) has learned (about a certain subject, or as a whole). It affects proficiency in [[skills]] and a dwarf's [[attributes]]. Precise points in experience are never displayed directly, except in [[Adventure Mode]].

Every experience point earned is associated with a skill. Skill increases happen when a certain number of points in that skill is reached. Attribute increases happen when a certain total number of points is reached.

The [[announcement]] "''Dwarfname'' is more experienced" signifies an [[attribute]] increase. Skill increases are not announced unless the increase changes a dwarf's [[profession]], when the announcement will be to the effect of "''Dwarfname'' has become a ''new profession''".

== Gaining experience ==

Dwarves gain experience by performing tasks. Experience is gained when the task is ''completed''; if a task takes a long time and is frequently interrupted (by the dwarf going off to drink, for instance), the dwarf will gain the skill very slowly. Tasks without an associated skill (such as [[hauling]]) do not give any experience.

Constructing [[building]]s or [[construction]]s does not give experience unless the building requires [[architecture]] to build. Such buildings give 30 points of experience in [[building designer]] to the architect and 10 experience to whichever dwarf finishes the building once it is designed. The additional experience depends on what material is used to build the building: a building made of [[stone]], stone [[block]]s, or [[glass]] blocks gives [[masonry]] experience; a building made of [[log]]s or wood blocks gives [[carpentry]] experience; a building made of [[metal]] bars or blocks gives [[metalsmith]] experience; and [[soap]] bars appear to give no experience to any skill.

Destroying buildings and constructions of any type gives no experience.

{| style="margin: 0 auto"
|+ style="margin: 0 auto" |'''Known Experience Values'''
| style="vertical-align: top" |
{| style="border-left: 1px solid black; border-right: 1px solid black; border-spacing: 0 1px; background: black"
|- style="background: #fff"
| style="padding: 0.2em 0.4em" | '''Skill''' || '''Task''' || '''XP'''
|- style="background: #bbb"
| style="padding: 0.2em 0.4em" | [[Miner]] || Dig || align="right" style="padding: 0.2em 0.4em" | 10
|- style="background: #bbb"
| style="padding: 0.2em 0.4em" | [[Miner]] || Remove ramp (natural) || align="right" style="padding: 0.2em 0.4em" | 10
|- style="background: #ff6"
| style="padding: 0.2em 0.4em" | [[Bowyer]] || Make wooden [[crossbow]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #ff6"
| style="padding: 0.2em 0.4em" | [[Carpenter]] || Construct [[bed]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #ff6"
| style="padding: 0.2em 0.4em" | [[Wood Cutter]] || Fell [[tree]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #fff"
| style="padding: 0.2em 0.4em" | [[Engraver]] || [[Smooth]] or detail a [[floor]] or [[wall]] || align="right" style="padding: 0.2em 0.4em" | 10
|- style="background: #fff"
| style="padding: 0.2em 0.4em" | [[Mason]] || Construct rock object || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #6b6"
| style="padding: 0.2em 0.4em" | [[Trapper]] || Construct [[animal trap]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #6b6"
| style="padding: 0.2em 0.4em" | [[Trapper]] || Bait [[animal trap]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #888"
| style="padding: 0.2em 0.4em" | [[Armorsmith]] || Make [[armor]] (any type) || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #888"
| style="padding: 0.2em 0.4em" | [[Metalsmith]] || Make metal [[Block]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #88f"
| style="padding: 0.2em 0.4em" | [[Stonecrafter]] || Make stone [[crafts]], [[mug]]s, etc. || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #88f"
| style="padding: 0.2em 0.4em" | [[Weaver]] || Gather [[silk]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #88f"
| style="padding: 0.2em 0.4em" | [[Weaver]] || Weave any [[cloth]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #88f"
| style="padding: 0.2em 0.4em" | [[Wood crafter]] || Make wooden [[bolt]]s || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #88f"
| style="padding: 0.2em 0.4em" | [[Glassmaker]] || Construct [[block]]s,[[window]]s || align="right" style="padding: 0.2em 0.4em" | 30
|}
| style="vertical-align: top" |
{| style="border-left: 1px solid black; border-right: 1px solid black; border-spacing: 0 1px; background: black"
|- style="background: #fff"
| style="padding: 0.2em 0.4em" | '''Skill''' || '''Task''' || '''XP'''
|- style="background: #880"
| style="padding: 0.2em 0.4em" | [[Herbalist]] || Gather plants || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #d00"
| style="padding: 0.2em 0.4em" | [[Mechanic]] || Link a building to trigger || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #d00"
| style="padding: 0.2em 0.4em" | [[Siege engineer]] || Construct catapult/ballista parts || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #d00"
| style="padding: 0.2em 0.4em" | [[Siege engineer]] || Assemble ballista arrow || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #d00"
| style="padding: 0.2em 0.4em" | [[Siege operator]] || Load [[catapult]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #d00"
| style="padding: 0.2em 0.4em" | [[Siege operator]] || Fire [[catapult]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #bb6"
| style="padding: 0.2em 0.4em" | [[Brewer]] || Brew [[alcohol|drink]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #bb6"
| style="padding: 0.2em 0.4em" | [[Butcher]] || Slaughter [[animal]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #bb6"
| style="padding: 0.2em 0.4em" | [[Cook]] || Cook easy/fine/lavish [[meal]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #bb6"
| style="padding: 0.2em 0.4em" | [[Grower]] || Harvest [[plants]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #bb6"
| style="padding: 0.2em 0.4em" | [[Grower]] || Plant [[seeds]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #bb6"
| style="padding: 0.2em 0.4em" | [[Herbalist]] || Gather [[plants]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #a6a"
| style="padding: 0.2em 0.4em" | [[Building designer|Building designer]] || Construct [[building]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #a6a"
| style="padding: 0.2em 0.4em" | [[Organizer]] || Manage Work Order || align="right" style="padding: 0.2em 0.4em" | 10
|- style="background: #6bb"
| style="padding: 0.2em 0.4em" | [[Strand extractor]] || Extract [[adamantine]] || align="right" style="padding: 0.2em 0.4em" | 30
|- style="background: #6b6"
| style="padding: 0.2em 0.4em" | [[Marksdwarf]] || Shoot at archery range || align="right" style="padding: 0.2em 0.4em" | ≈7.5
|}
|}

:* A dwarf taken by a [[strange mood]] will gain 20,000 experience in the affected skill.

== Increasing skills ==

If a dwarf has zero experience in a skill, they will have no skill listed (but can still use that skill at an untrained level if a [[labor]] associated with the skill is designated, and will gain experience from completing such tasks).

As soon as a dwarf gets even 1 point of experience in a skill from completing just one [[job]], they attain '''Dabbling''' rank in that skill. This can be important for [[strange mood]]s.

To reach '''Novice''' level in any skill requires 500 XP. Reaching each successive level requires 500 plus an additional 100 XP per additional rank, so to go from '''Novice''' to '''''(no label)''''' requires 600 XP; '''''(no label)''''' to '''Competent''' requires 700 XP, and so on. The following figures are the ''cumulative'' XP needed to go from unskilled to any given skill level.

As dwarfs gain more experience from completing jobs, they gain more experience in the skill related to those jobs:

{| style="margin: 0 auto; border: 1px solid black; border-spacing: 0"
|-
| width="25%" style="border-right: 1px solid black;" |
{| width="100%"
! Level !! XP
|-
| '''Novice''' || align="right" | 500
|-
| ''(no label)'' || align="right" | 1100
|-
| '''Competent''' || align="right" | 1800
|-
| '''Skilled''' || align="right" | 2600
|-
| '''Proficient'''* || align="right" | 3500
|}
| width="25%" style="border-right: 1px solid black;" |
{| width="100%"
! Level !! XP
|-
|
|-
| '''Talented''' || align="right" | 4500
|-
| '''Adept ''' || align="right" | 5600
|-
| '''Expert ''' || align="right" | 6800
|-
| '''Professional''' || align="right" | 8100
|-
| '''Accomplished''' || align="right" | 9500
|}
| width="25%" style="border-right: 1px solid black;" |
{| width="100%"
! Level !! XP
|-
|
|-
| '''Great ''' || align="right" | 11000
|-
| '''Master ''' || align="right" | 12600
|-
| '''High Master''' || align="right" | 14300
|-
| '''Grand Master''' || align="right" | 16100
|-
| '''Legendary ''' || align="right" | 18000
|}
| width="25%" style="border-right: 1px solid black;" |
{| width="100%"
! Level !! XP
|-
|
|-
| '''Legendary'''(+1) || align="right" | 20000
|-
| '''Legendary'''(+2) || align="right" | 22100
|-
| '''Legendary'''(+3) || align="right" | 24300
|-
| '''Legendary'''(+4) || align="right" | 26600
|-
| '''Legendary'''(+5) || align="right" | 29000
|}
|}

::::::''(* "Proficient" is the highest rank that one of your initial seven dwarves can start with. [[Migrant]]s will arrive with no skills, Novice, or (no label) levels.)''

Although '''[[Legendary]]''' is the highest skill level displayed, there are actually five skill levels above that. Any higher skill levels are known to have an effect on [[item quality]]; a Legendary dwarf will make [[masterpiece]] items 15% of the time, on average, whereas a Legendary+5 dwarf will make masterpieces 27% of the time (and exceptional items the other 73% of the time). Skill beyond Legendary+5 does not increase the probability of creating a masterpiece item.

You can't find out exactly when a dwarf gets to Legendary+5, but if they have no other skills it will happen 1000 XP before their eighth [[attribute]] -- so when they get eight attributes, they are past Legendary+5. Although skill is capped at Legendary+5, experience is not capped at any level; a dwarf can keep gaining [[attribute]]s by using a skill that has long since topped out.

== Increasing attributes ==

[[Attribute]] increases are based on total experience gained across all skills, and are not connected to the attainment of specific skill levels.

Dwarves with a single skill will get their first attribute between Competent and Skilled, their second when reaching Talented, a third between Expert and Professional, a fourth when reaching Great, and a fifth between High Master and Grand Master. Further increases can happen after Legendary.

[[Toady]] has stated that although there is no cap on attribute increases, after the fifth increase they are still displayed as 'Ultra-Mighty' 'Perfectly Agile' or 'Superdwarvenly Tough', so an attribute gain message without a change in displayed attributes is possible.

{| style="margin: 0 auto; border: 1px solid black; border-spacing: 0; text-align: right"
|-
| width="50%" style="border-right: 1px solid black" |
{| width="100%"
! Attributes !! style="padding-left: 35px;"| XP
|-
! 1
| 2000
|-
! 2
| 4500
|-
! 3
| 7500
|-
! 4
| 11000
|-
! 5
| 15000
|-
! 6
| 19500
|-
! 7
| 24500
|-
! 8
| 30000
|}
| width="50%" valign="top" |
{| width="100%"
! Attributes !! style="padding-left: 35px;"| XP
|-
! 9
| 36000
|-
! 10
| 42500
|-
! 11
| 49500
|-
! 12
| 57000
|-
! 13
| 65000
|-
! 14
| 73500
|-
! 15
| 82500
|-
! 16
| 92000
|}
|}

[[Category:Dwarves]]

Dwarf Fortress Wiki:Improvement Drive

2009-09-19T23:39:50Z

Adeptable: sp

Here's some information about the traffic on the wiki. How can we improve the site for players, both new and old? ( I will update these traffic information shots weekly)
<gallery>
Image:Top Pages.png|Top Pages
Image:Search terms.png|Search Terms
Image:Overlay.png|Navigation Flow Overlay
</gallery>

*Advertisements
**No one likes advertisements, but they are a necessary evil. Hosting this wiki costs approximately $60 a month out of my own pocket, which is paid for by 6 ad clicks / day. Currently the average is 1 click / day. Not a huge deal if I loose money on this, though.
**How can we improve placement / filtering so the ads are not as intrusive, yet we get 6 clicks per day so I'm not taking from my ramen budget?

*New Player Experience
**Perhaps the tutorials should be reworked a bit, and made more prominent on the main page. Agree / Disagree?
**Should we include a link to Mayday's graphical compilation on the main page? The default tileset can be more than intimidating for some.

*Overall Site Improvements
**What should we improve?
**To increase the speed of page loads, I can migrate the database to PostgreSQL (this server setup has been optimized for Postgres previously, and not mySQL). However, this would require some downtime (between 0-3 hours, most likely). Thoughts?
**I moved this site from the original (vps) server it was hosted on due to PHP stack issues.
**I have been thinking about updating the captcha plugin to recaptcha, and then re-enabling page edits for unregistered users. Thoughts?
**There may be odd kinks to work out still on the website, as I do not program / have experience in PHP (Ruby on Rails is what I do my web programming in).

*Verify Time!
** Category:Verify has a lot of stuff we need to verify.

==Server Information==
*Centos 5 LAMP stack
*MediaWiki 1.15.1
*PHP 5
*memcached 512m daemon
*4 core 2.33ghz processor
*8g ram

This server is also the memcached server for my company's up and coming applications. These applications are using 6g of memcached space, leaving 1.5g available for apache and php processes.

Hosting cost for the server is $750 a month including my company's applications.

==Recent Fixes==
Favicon replaced. 23:16, 18 September 2009 (UTC)

40d:Farmer's workshop

2009-09-16T10:19:28Z

Adeptable: add Vials to the list of materials used

{{Workshop|name=Farmer's workshop|key=w|job=[[Thresher|Plant processing]], [[Milker|Milking]], [[Cheese maker|Cheese making]]
|construction=
1 of
* [[Block]]
* [[Stone]]
* [[Wood]]
* [[Metal]]
|construction_job=
Any Workshop Farming:
* [[Thresher|Plant processing]], or [[Milker|Milking]], or [[Cheese maker|Cheese making]]
|use=
* Various [[crop]]s
* [[Container|Bags, barrels]] and [[vial]]s for their respective tasks
* [[Purring maggot]]s and [[milk]]
|production=
* [[Pig tail]] [[thread]]s (process plants)
* [[Rope reed]] [[thread]]s (process plants)
* [[Quarry bush]] leaves (" " to [[bag]])
* [[Dwarven syrup]] (" " to [[barrel]])
* Plant [[extracts]] (" " to [[vial]])
* [[Milk]]
* [[Cheese]]
}}
A '''farmer's workshop''' is used to process various [[plant]]s and make [[cheese]]. [[Pig tail]]s and [[Rope reed]]s are processed into [[thread]], [[quarry bush]]es into leaves, and [[sweet pod]]s into [[dwarven syrup]].

It is also used to milk [[purring maggot]]s for [[dwarven milk]]. Dwarven milk as well as other (bought) [[milk]] can then be turned into cheese at a 1:1 ratio. For this the milk has to be allowed for cooking in the kitchen menu, so you might want to make sure it's not used for cooking instead.

==Tasks==
=====Process Plants=====
Requires: [[Pig tail]] or [[Rope reed]], and [[Plant Processing]].

Creates [[Pig tail thread]] or [[Rope reed thread]], repectively. See [[the clothing industry]] for more info on these products.
=====Process Plants (to Bag)=====
Requires: [[Quarry bush]], a [[bag]], and [[Plant Processing]].

Creates [[Quarry bush]] leaves.
=====Process Plants (to Barrel)=====
Requires: [[Sweet pod]], a [[barrel]], and [[Plant Processing]].

Creates [[Dwarven syrup]].
=====Process Plants (to Vial)=====
Requires: [[Kobold bulb]] or [[Valley herb]], a [[vial]], and [[Plant Processing]].

Creates [[Gnomeblight]] or [[Golden salve]], respectively.
=====Milk Creature=====
Requires: [[Purring maggot]], a [[bucket]], and [[Milking]].

Creates [[Dwarven milk]].

=====Make Cheese=====
Requires: Any milk [[Status#Kitchen Status Screen|available for cooking]], and [[Cheese Making]]

Creates the associated cheese. i.e. [[Cow]] milk goes to cow cheese.

{{Workshops}}

40d:Workshop

2009-09-16T01:47:06Z

Adeptable: /* Furnaces & Forges */ syntax

[[Image:Production_chain.gif|thumb|400px|Production chain.]]
'''Workshops''' are where objects are created, refined, altered, and decorated.

== Building==

Most workshops are quick and easy to build, requiring only a single piece of [[stone]], [[wood]], or other common materials (although there are a few exceptions). To build a workshop, open the {{key|b}}uild menu and select {{key|w}}orkshop, then choose which workshop you would like to build and the materials you would like to use in its construction. Your cursor will now change into a floor plan of the workshop.

Attention: '''dark green locations in the plan will be impassable ''' in the completed workshop, while passable locations will be a bright green. Plans cannot be rotated, so it is important to ensure that the impassable squares do not block a door or otherwise cut off access to the workshop. The [[Jeweler's workshop]] and [[Bowyer's workshop]] block off a whole side of the workshop.

Once the plan has been placed in a satisfactory location, you must have a [[dwarf]] with the appropriate [[labor]] enabled to build the workshop ({{key|v}}iew dwarf-{{key|p}}references-{{key|l}}abors). For instance, to build a a [[carpenter's workshop]], you must have a dwarf with the "[[Carpentry]]" labor enabled. Some workshops (such as the [[furnaces]]) must first be designed by a dwarf with the [[architecture]] labor enabled. To see what labor is needed to build a particular workshop, press {{key|q}} and move the cursor over its floor plan.

To build a workshop, a dwarf must first clean the area of loose rock and other items lying on the ground by moving them to neighboring, non-diagonal squares. Items already claimed by other tasks (such as "Bring Item to Stockpile" cannot be moved and will cause the dwarf to suspend construction of the workshop. If this happens, you will need to wait until the interfering tasks are finished (for instance, rock has been cleared away to a stockpile), and then manually un-suspend construction with the {{key|q}} menu. The dwarf will also suspend the construction when he can't find a proper neighboring square to move the items to. This is usually caused by active construction sites on neighboring tiles.

== Use==

Once a workshop has been constructed, you will need to assign a queue of tasks at which the dwarves with that workshop's skill will henceforth toil. To edit the queue, hit {{key|q}} and move the cursor over the workshop. Jobs are completed in order from top to bottom; a job set to 'repeat' will be labeled ''''R'''' in the list, and will be be sent back to the bottom after it is done. This allows you to set a workshop to do a series of tasks repeatedly. The job labeled ''''A'''', if any, is the currently active project.

Alternatively, the [[manager]] can assign jobs to workshops. This is a more efficient way of allocating jobs when the fortress becomes larger.

Most jobs require materials. Any dwarf that starts a job in a workshop will automatically retrieve the necessary materials from the appropriate source (even if they don't have the appropriate [[hauling]] job set). Dwarves work more efficiently if the materials for their workshop are [[stockpile]]d nearby.

Beware of workshop '''[[clutter]]'''! Dwarves will ''not'' automatically haul things away from workshops once the job is completed. Note that there is no way to notice a cluttered workshop without looking specifically inside the workshop ({{key|t}} or {{key|q}}) until a cloud of [[miasma]] erupts from your [[kitchen]].

==Profiles==

Once you have assigned a manager, each workshop will have a profile menu ({{key|q}}-{{key|P}}) which allows you to specify which dwarves are allowed to use the workshop (either by name or by a range of [[skill]]s).

== Variations==

The workshops used in the game include the following:{{Workshops}}

* [[Alchemist's laboratory]]: Used to make [[soap]].
* [[Ashery]]: Used to make [[lye]] and [[potash]].
* [[Bowyer's workshop]]: Used to make bone or wooden [[crossbow]]s.
* [[Butcher's shop]]: Used to turn some corpses and [[animals|livestock]] into [[meat]] and usable materials.
* [[Carpenter's workshop]]: Used to make [[furniture]] from [[wood]]. Also some [[trap]] components.
* [[Clothier's shop]]: Used to make numerous items from [[cloth]].
* [[Craftsdwarf's workshop]]: Used to make a [[crafts|number of items]] from a plethora of materials for trading purposes. Also useful to make [[bolts]] cheaply.
* [[Dyer's shop]]: Used to [[dye]] [[cloth]] or [[thread]].
* [[Farmer's workshop]]: Used to make [[thread]], [[milk]], [[syrup]], and [[quarry bush|leaves]].
* [[Fishery]]: Used to process raw [[fish]] into edible [[meat]] and [[bones]].
* [[Jeweler's workshop]]: Used to cut and encrust with [[gems]].
* [[Kitchen]]: Used to cook [[food]] to decrease needed storage space, and expand the types of edible food.
* [[Leather works]]: Used to make [[leather]] into [[armor]] and [[clothes]].
* [[Loom]]: Used to make [[cloth]] from [[thread]].
* [[Mason's workshop]]: Used to make [[furniture]] from [[stone]].
* [[Mechanic's workshop]]: Used only to make [[mechanism]]s from [[stone]].
* [[Metalsmith's forge]]: Used to make a plethora of items from trading items to [[furniture]] and [[trap]] components from [[metal]] [[bar]]s and [[fuel]].
** [[Magma forge]]: Same as above, but with no [[fuel]] consumption (except for the [[steel]] industry).
* [[Millstone]]: Used to make [[dye]], [[flour]], and [[sugar]].
** [[Quern]]: Same as above, but with muscle power instead of water or [[windmill]]
* [[Siege workshop]]: Used to make [[ballista]] arrows and [[catapult]] and ballista parts.
* [[Still]]: Used to make [[alcohol]] drinks from [[plants]].
* [[Tanner's shop]]: Used to tan [[raw hide]]s into [[leather]].

== Furnaces & Forges==

Furnaces and forges are essentially workshops, except that they need some form of [[fuel]] ([[charcoal]] or [[coke]]) or [[magma]] to operate. Furnaces transform raw material ([[wood]], [[ore]] or [[sand]]) to either a [[bar]] or [[block]] (of [[glass]], [[metal]], [[fuel]], [[ash]] or [[potash]]). Forges turn metal bars into metal products, such as [[weapons]], [[armour]], [[furniture]] or [[craft]]s. To build a furnace, open the {{key|b}}uild menu and select {{key|e}}. Forges are under the normal workshop menu.

Furnaces must be built from [[fire-safe]] material, usually stone or stone blocks.

* [[Glass furnace]]: Used to make [[glass]] items from [[sand]] and [[fuel]].
** [[Magma glass furnace]]: Same as above, but without the [[fuel]] consumption.*
* [[Kiln]]: Used to make [[pearlash]] from [[potash]] and [[fuel]].
** [[Magma kiln]]: Same as above, but without [[fuel]] consumption.*
* [[Smelter]]: Used to make [[metal]] [[bar]]s from [[ore]], and smelt [[coke]], which is [[fuel]].
** [[Magma smelter]]: Same as above, but without [[fuel]] consumption.* (However, see [[smelting]] [[pig iron]] & [[steel]])
* [[Wood furnace]]: Used to make [[charcoal]], which is [[fuel]], from [[wood]]

:''(* Conventional fuels cannot be used at a magma version of a furnace or forge if it loses its magma source.)''

==Workshop Design==
Since workshops are where much of your fortress's day to day work happens, it is important to plan them as carefully as you do your [[Bedroom Design|bedrooms]]. Workshop designs have a couple key considerations:
* Workshops should be as close as possible to the raw materials needed to do their job. The only dwarf who hauls the needed materials into the workshop is the one who works in it. Placing a stockpile with the corresponding materials right next to the workshop will save the precious time of your craftsdwarf by leaving the tedious material transportation to less qualified laborers.
* There should be room to put in duplicate workshops, to accommodate spikes in demand for things like beds and barrels (carpentry) or stone furniture (masons). Workshop construction and deconstruction is cheap and quick in most cases, so do not hesitate do create and remove temporary workshops when the need arises.
* Certain (but not all) workshops should be lockable by forbidding the doors that lead into them. This is important for making sure that specific material can be forced to be used for specific production orders ([[bauxite]] [[mechanisms]] for example, or [[native aluminum]] furniture for your nobles), or that the desired items get decorated with exactly what you want (you don't want rubies on a -mudstone table- while you have a ☼[[platinum]] statue☼ around). Also for locking away a dangerous dwarf in a failing [[strange mood]] so they won't hurt a useful worker. Not all workshops are subject to being claimed by [[mood]]y dwarfs, and not all workshops need be concerned with specific items - a [[farmer's workshop]], for instance, in both cases.
* The design should be expandable. There will ALWAYS be another specialty workshop you'd find useful, whether it be a single-task, lockable Jeweler, a Legendary-only Carpenter's Workshop for beds, a floor of Dabbling to Proficient-only Masonry workshops for a [[Military#Cross-training_.28starting_a_Reserves_program.29|reserves program]], the list goes on. Never assume you'll never need another workshop. You'll always find SOMETHING.
* The design should have good traffic throughput. Workshop complexes are pretty high-traffic areas, so you'll need to keep this in mind.
 
A couple things that may seem like big deals, but really aren't:
* Being close to where the finished good will go. You will definitely need to think of where your chairs, tables, prepared meals, and the like will go after they're done being made, but an average fortress has a lot of spare labor and untrained peasants that are qualified for little more than hauling finished goods. Don't be afraid of putting the prepared food and booze larder 100 steps away from the kitchen and still; just turn off food hauling on your cooks and let the peasants handle it.
* Setting up resource stockpiles somewhat near where the resource is produced. Again, the peasants will handle this.

Specific design ideas are at [[Design_strategies#Workshop_Logistics|Design Strategies]]

==See Also==
:*[[Noise]]
:*[[Labor]]

[[Category:Workshops]]
[[ru:Мастерская]]

40d:Water wheel

2009-09-13T15:43:08Z

Adeptable: /* Channels */ clean up <> to ()

{{Machine_component|name=Water wheel|key=w
|construction=
* 3 [[Wood]]
|construction_job=
# [[Architecture]]
# [[Carpenter]]
|power=Needs 10 power. Generates 100 power. Net gain of 90 power.
}}

A '''water wheel''' is a [[machine component]] that provides [[power]] via [[water]] flow. To build a water wheel, select {{key|b}}uild menu and choose {{key|M}}achine components. It requires 3 [[wood]] and generates 100 power, which can be used for operating a [[pump]] or [[mill]]. You can use [[axle]]s and [[Gear assembly|gear]]s to access the power produced by a water wheel, or connect machinery like a [[pump]] or [[millstone]] directly.

Waterwheels have quality levels for both design and building. These can be checked from the {{k|r}}oom screen by moving to the entry and pressing enter.

== Construction ==
The architecture and carpentry labor are needed for the construction.

A water wheel occupies 3 adjacent tiles (N-S or E-W axis, no diagonals).

Although you can build a stable water wheel on solid ground, this isn't going to do you any good. For this reason, water wheels are almost exclusively built in a hanging state with gaps in the floor below. To do this the water wheel must be attached to a nearby machine component. A water wheel can attach to other machines only on either side of its center tile.

'''Power''' will be sometimes generated once one channel tile under the water wheel is filled with water at a depth of four or greater '''if''' there also is a [[water flow]] in one of the three tiles beneath it (we need more info in the article on what constitutes waterflow). The easiest way to achieve this is to place the water wheel in a river, but also a brook or channel works if done right (read below). Having two floor tiles and one channel tile below the wheel will only sometimes work, even if that one tile fulfills the above conditions. 

You can transport the power wherever it is needed via horizontal and vertical axles and gear assemblies. It is possible to support a waterwheel by building its center next to a preexisting water wheel's center.

==Brook==
Intuitively one would place a water wheel in a river, but they can also be powered if placed over [[brook]] tiles, but '''only if''' you first dig through the surface of the brook. Dig a [[channel]] three tiles long, right on the brook. The water wheel will sit above this channel.

== Channels ==
It is possible to power a water wheel in a channel if it is connected to a river or brook (read as: water that has flow. Further details needed.) A channel connected to a murky pool will not suffice, no matter what water movement is present in the channel.

Any direct non-diagonal connection (see [[water pressure]]) to a [[river]] or [[brook]] that has flow (some do not) will power a waterwheel, even if it's a dead end. A floodgate in the channel will not block this flow either.

==Designs==

{|style="border: 1px solid #0b0; background: #dfd"
|+'''Basic watermill design'''
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #07F; padding: 0"|~
|style="color: #777; padding: 0"|+
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #07F; padding: 0"|~
|style="color: #777; padding: 0"|+
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #333; padding: 0"|O
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #970; padding: 0"|W
|style="color: #777; padding: 0"|+
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #333; padding: 0"|*
|style="color: #970; padding: 0"|=
|style="color: #970; padding: 0"|=
|style="color: #970; padding: 0"|=
|style="color: #970; padding: 0"|W
|style="color: #777; padding: 0"|+
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #970; padding: 0"|W
|style="color: #777; padding: 0"|+
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #7FF; padding: 0"|~
|style="color: #777; padding: 0"|+
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #07F; padding: 0"|~
|style="color: #777; padding: 0"|+
|}
{|style="border: 1px solid #0b0; background: #dfd"
|+'''Dual watermill design'''
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #07F; padding: 0"|~
|style="color: #07f; padding: 0"|~
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #07F; padding: 0"|~
|style="color: #7FF; padding: 0"|~
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #333; padding: 0"|O
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #970; padding: 0"|W
|style="color: #970; padding: 0"|W
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #333; padding: 0"|*
|style="color: #970; padding: 0"|=
|style="color: #970; padding: 0"|=
|style="color: #970; padding: 0"|=
|style="color: #970; padding: 0"|W
|style="color: #970; padding: 0"|W
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #970; padding: 0"|W
|style="color: #970; padding: 0"|W
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #07F; padding: 0"|~
|style="color: #07F; padding: 0"|~
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #07F; padding: 0"|~
|style="color: #07F; padding: 0"|~
|}
This is by no means the limit of water power from one location, depending on the width of your river/brook/channel you can stack many waterwheels side-by-side (really big assembles will need to be artificial as there's a limit to how wide the game created water flows get). Just remember to make sure there's a support structure in place before you place the next wheel.

== Perpetual motion ==

Due to the low power draw of a [[screw pump]], a self-powering assembly can be made with a water wheel that still leaves plenty of excess power for other uses. This is an [[exploit]], and possibly a bug.

 
'''*REMEMBER TO BUILD THE HORIZONTAL AXLE OR GEAR ASSEMBLY BEFORE THE WATER WHEEL*'''
{|style="border: 1px solid #333; background: #000"
|+'''Perpetual Motion Design #1 - Top Floor'''
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #C0C0C0; padding: 0"|`
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|═
|style="color: #FFFFFF; padding: 0"|╗
|style="color: #000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|╚
|style="color: #FFFFFF; padding: 0"|╗
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #C0C0C0; padding: 0"|.
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|║
|style="color: #C0C0C0; padding: 0"|▼
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|╠
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╗
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|║
|style="color: #808000; padding: 0"|X
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|╩
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #008000; padding: 0"|'''X'''
|style="color: #00FF00; padding: 0"|'''X'''
|style="color: #808000; padding: 0"|_
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|╝
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #970; background: #FFFFFF; padding: 0"|W
|style="color: #FFFFFF; padding: 0"|=
|style="color: #808000; padding: 0"|║
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #970; background: #FFFFFF; padding: 0"|W
|style="color: #808000; padding: 0"|=
|style="color: #C0C0C0; padding: 0"|*
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|style="color: #C0C0C0; padding: 0"|`
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #970; background: #FFFFFF; padding: 0"|W
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|═
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|╚
|style="color: #FFFFFF; padding: 0"|═
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #C0C0C0; padding: 0"|%
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|}
 
{|style="border: 1px solid #333; background: #000"
|+'''Perpetual Motion Design #1 - Bottom Floor'''
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╗
|style="color: #000000; padding: 0"|█
|style="color: #C0C0C0; padding: 0"|%
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|║
|style="color: #C0C0C0; padding: 0"|▲
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #C0C0C0; padding: 0"|`
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|╠
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╣
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|║
|style="color: #808000; padding: 0"|X
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|style="color: #C0C0C0; padding: 0"|.
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|╚
|style="color: #FFFFFF; padding: 0"|╗
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|╗
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|╚
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|╚
|style="color: #FFFFFF; padding: 0"|═
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #000000; padding: 0"|█
|}
 
{|style="border: 1px solid #333; background: #000"
|+'''Perpetual Motion Design #2'''
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╗
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #C0C0C0; padding: 0"|▲
|style="color: #FFFFFF; padding: 0"|╚
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╗
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #808000; padding: 0"|_
|style="color: #808000; padding: 0"|_
|style="color: #808000; padding: 0"|_
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #808000; padding: 0"|_
|style="color: #777; padding: 0"|+
|style="color: #808000; padding: 0"|_
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #970; padding: 0"|W
|style="color: #777; padding: 0"|+
|style="color: #008000; padding: 0"|X
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #970; padding: 0"|W
|style="color: #808000; padding: 0"|=
|style="color: #00FF00; padding: 0"|X
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #970; padding: 0"|W
|style="color: #777; padding: 0"|+
|style="color: #808000; padding: 0"|_
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #808000; padding: 0"|_
|style="color: #777; padding: 0"|+
|style="color: #808000; padding: 0"|_
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #808000; padding: 0"|_
|style="color: #808000; padding: 0"|_
|style="color: #808000; padding: 0"|_
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|╚
|style="color: #FFFFFF; padding: 0"|═
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╝
|}
 
'''Key'''
 
'''Wall: ║ ═ ╠ ╝ ╚ ╔ ╗ ╣ ╩'''
 
'''Floor: +'''
 
'''Water Wheel: W'''
 
'''Gear Assembly: *'''
 
'''Axle E/W: ═'''
 
'''Axle N/S: ║'''
 
'''Pump from west: XX'''
 
'''Pump from south: XX'''
 
'''Channel: _ or if background color is white'''
 
'''Closed water source opening: X'''
 

[[Category:Machine components]]

40d:Water wheel

2009-09-13T15:41:38Z

Adeptable: /* Construction */ sp,gr

{{Machine_component|name=Water wheel|key=w
|construction=
* 3 [[Wood]]
|construction_job=
# [[Architecture]]
# [[Carpenter]]
|power=Needs 10 power. Generates 100 power. Net gain of 90 power.
}}

A '''water wheel''' is a [[machine component]] that provides [[power]] via [[water]] flow. To build a water wheel, select {{key|b}}uild menu and choose {{key|M}}achine components. It requires 3 [[wood]] and generates 100 power, which can be used for operating a [[pump]] or [[mill]]. You can use [[axle]]s and [[Gear assembly|gear]]s to access the power produced by a water wheel, or connect machinery like a [[pump]] or [[millstone]] directly.

Waterwheels have quality levels for both design and building. These can be checked from the {{k|r}}oom screen by moving to the entry and pressing enter.

== Construction ==
The architecture and carpentry labor are needed for the construction.

A water wheel occupies 3 adjacent tiles (N-S or E-W axis, no diagonals).

Although you can build a stable water wheel on solid ground, this isn't going to do you any good. For this reason, water wheels are almost exclusively built in a hanging state with gaps in the floor below. To do this the water wheel must be attached to a nearby machine component. A water wheel can attach to other machines only on either side of its center tile.

'''Power''' will be sometimes generated once one channel tile under the water wheel is filled with water at a depth of four or greater '''if''' there also is a [[water flow]] in one of the three tiles beneath it (we need more info in the article on what constitutes waterflow). The easiest way to achieve this is to place the water wheel in a river, but also a brook or channel works if done right (read below). Having two floor tiles and one channel tile below the wheel will only sometimes work, even if that one tile fulfills the above conditions. 

You can transport the power wherever it is needed via horizontal and vertical axles and gear assemblies. It is possible to support a waterwheel by building its center next to a preexisting water wheel's center.

==Brook==
Intuitively one would place a water wheel in a river, but they can also be powered if placed over [[brook]] tiles, but '''only if''' you first dig through the surface of the brook. Dig a [[channel]] three tiles long, right on the brook. The water wheel will sit above this channel.

== Channels ==
It is possible to power a water wheel in a channel if it is connected to a river or brook <read as: water that has flow. Further details needed.> A channel connected to a murky pool will not suffice, no matter what water movement is present in the channel.

Any direct non-diagonal connection (see [[water pressure]]) to a [[river]] or [[brook]] that has flow (some do not) will power a waterwheel, even if it's a dead end. A floodgate in the channel will not block this flow either.

==Designs==

{|style="border: 1px solid #0b0; background: #dfd"
|+'''Basic watermill design'''
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #07F; padding: 0"|~
|style="color: #777; padding: 0"|+
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #07F; padding: 0"|~
|style="color: #777; padding: 0"|+
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #333; padding: 0"|O
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #970; padding: 0"|W
|style="color: #777; padding: 0"|+
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #333; padding: 0"|*
|style="color: #970; padding: 0"|=
|style="color: #970; padding: 0"|=
|style="color: #970; padding: 0"|=
|style="color: #970; padding: 0"|W
|style="color: #777; padding: 0"|+
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #970; padding: 0"|W
|style="color: #777; padding: 0"|+
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #7FF; padding: 0"|~
|style="color: #777; padding: 0"|+
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #07F; padding: 0"|~
|style="color: #777; padding: 0"|+
|}
{|style="border: 1px solid #0b0; background: #dfd"
|+'''Dual watermill design'''
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #07F; padding: 0"|~
|style="color: #07f; padding: 0"|~
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #07F; padding: 0"|~
|style="color: #7FF; padding: 0"|~
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #333; padding: 0"|O
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #970; padding: 0"|W
|style="color: #970; padding: 0"|W
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #333; padding: 0"|*
|style="color: #970; padding: 0"|=
|style="color: #970; padding: 0"|=
|style="color: #970; padding: 0"|=
|style="color: #970; padding: 0"|W
|style="color: #970; padding: 0"|W
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #970; padding: 0"|W
|style="color: #970; padding: 0"|W
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #07F; padding: 0"|~
|style="color: #07F; padding: 0"|~
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #777; padding: 0"|#
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #07F; padding: 0"|~
|style="color: #07F; padding: 0"|~
|}
This is by no means the limit of water power from one location, depending on the width of your river/brook/channel you can stack many waterwheels side-by-side (really big assembles will need to be artificial as there's a limit to how wide the game created water flows get). Just remember to make sure there's a support structure in place before you place the next wheel.

== Perpetual motion ==

Due to the low power draw of a [[screw pump]], a self-powering assembly can be made with a water wheel that still leaves plenty of excess power for other uses. This is an [[exploit]], and possibly a bug.

 
'''*REMEMBER TO BUILD THE HORIZONTAL AXLE OR GEAR ASSEMBLY BEFORE THE WATER WHEEL*'''
{|style="border: 1px solid #333; background: #000"
|+'''Perpetual Motion Design #1 - Top Floor'''
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #C0C0C0; padding: 0"|`
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|═
|style="color: #FFFFFF; padding: 0"|╗
|style="color: #000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|╚
|style="color: #FFFFFF; padding: 0"|╗
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #C0C0C0; padding: 0"|.
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|║
|style="color: #C0C0C0; padding: 0"|▼
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|╠
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╗
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|║
|style="color: #808000; padding: 0"|X
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|╩
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #008000; padding: 0"|'''X'''
|style="color: #00FF00; padding: 0"|'''X'''
|style="color: #808000; padding: 0"|_
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|╝
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #970; background: #FFFFFF; padding: 0"|W
|style="color: #FFFFFF; padding: 0"|=
|style="color: #808000; padding: 0"|║
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #970; background: #FFFFFF; padding: 0"|W
|style="color: #808000; padding: 0"|=
|style="color: #C0C0C0; padding: 0"|*
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|style="color: #C0C0C0; padding: 0"|`
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #970; background: #FFFFFF; padding: 0"|W
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|═
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|╚
|style="color: #FFFFFF; padding: 0"|═
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #C0C0C0; padding: 0"|%
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|}
 
{|style="border: 1px solid #333; background: #000"
|+'''Perpetual Motion Design #1 - Bottom Floor'''
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╗
|style="color: #000000; padding: 0"|█
|style="color: #C0C0C0; padding: 0"|%
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|║
|style="color: #C0C0C0; padding: 0"|▲
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #C0C0C0; padding: 0"|`
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|╠
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╣
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|║
|style="color: #808000; padding: 0"|X
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|style="color: #C0C0C0; padding: 0"|.
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|╚
|style="color: #FFFFFF; padding: 0"|╗
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|╗
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|╚
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|╚
|style="color: #FFFFFF; padding: 0"|═
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #000000; padding: 0"|█
|}
 
{|style="border: 1px solid #333; background: #000"
|+'''Perpetual Motion Design #2'''
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #000000; padding: 0"|█
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╗
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|style="color: #000000; padding: 0"|█
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|╔
|style="color: #FFFFFF; padding: 0"|╝
|style="color: #C0C0C0; padding: 0"|▲
|style="color: #FFFFFF; padding: 0"|╚
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╗
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #808000; padding: 0"|_
|style="color: #808000; padding: 0"|_
|style="color: #808000; padding: 0"|_
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #808000; padding: 0"|_
|style="color: #777; padding: 0"|+
|style="color: #808000; padding: 0"|_
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #970; padding: 0"|W
|style="color: #777; padding: 0"|+
|style="color: #008000; padding: 0"|X
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #970; padding: 0"|W
|style="color: #808000; padding: 0"|=
|style="color: #00FF00; padding: 0"|X
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #970; padding: 0"|W
|style="color: #777; padding: 0"|+
|style="color: #808000; padding: 0"|_
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #808000; padding: 0"|_
|style="color: #777; padding: 0"|+
|style="color: #808000; padding: 0"|_
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #808000; padding: 0"|_
|style="color: #808000; padding: 0"|_
|style="color: #808000; padding: 0"|_
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|║
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #777; padding: 0"|+
|style="color: #FFFFFF; padding: 0"|║
|- style="font-family: monospace; font-weight: bold; font-size: 135%"
|style="color: #FFFFFF; padding: 0"|╚
|style="color: #FFFFFF; padding: 0"|═
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|=
|style="color: #FFFFFF; padding: 0"|╝
|}
 
'''Key'''
 
'''Wall: ║ ═ ╠ ╝ ╚ ╔ ╗ ╣ ╩'''
 
'''Floor: +'''
 
'''Water Wheel: W'''
 
'''Gear Assembly: *'''
 
'''Axle E/W: ═'''
 
'''Axle N/S: ║'''
 
'''Pump from west: XX'''
 
'''Pump from south: XX'''
 
'''Channel: _ or if background color is white'''
 
'''Closed water source opening: X'''
 

[[Category:Machine components]]

40d:Lever

2009-09-09T20:09:59Z

Adeptable: /* Linking */ re-add some stuff about linking a lever to the same object twice, with more detail (see talk)

A '''lever''' is a [[mechanism]] that has been constructed on a floor tile. Once in place, it can be linked to one or more other devices such as [[door]]s, [[bridge]]s or [[support]]s, permitting you to remotely control these other devices through the lever's {{k|q}} menu.

Levers do not block any movement. Levers are counted as furniture for [[created wealth]] of a fortress.

[[Pressure plate]]s are like levers, but are activated automatically by [[creatures]] stepping on it, or by fluids reaching a certain (player-selected) depth.

Either a '''lever''' or a [[pressure plate]], once linked to one or more devices ([[door]]s, [[trap]]s, or whatever), can act as a '''trigger''', an activation mechanism for that secondary system. The two are activated differently, but the connected system is activated just the same. One system can have more than one trigger linked to it, and one trigger can be linked to more than one system.

==Placing a lever==
If you have a spare mechanism, you can designate the new lever job via the "{{k|b}}uild {{k|T}}rap {{k|l}}ever" keys, and can use {{k|x}} to choose which specific mechanism to use. Mechanism [[quality]] has no known effect on the performance of the lever. Low-quality mechanisms work fine, but since they are counted as furniture, high quality mechanisms give more [[created wealth]].

==Linking==

Once a mechanism has been placed as a lever, it then requires a pair of [[mechanisms]] to link that lever to any object, regardless of distance or size, and [[quality]] of the mechanism makes no reported difference. This is done by giving the lever the appropriate job order via {{k|q}}(similar to any workshop), selecting what sort of object you want the lever linked to*, and then using the {{k|-}} and {{k|+}} keys to scroll thru the available examples of those and selecting the one you want. The list is chronological, with the last object finished listed last, and the map will re-center on the exact object as you scroll.

:''(* [[bridge]], [[cage]], [[chain]], [[door]], [[floodgate]], [[hatch]], [[wall grate]], [[floor grate]], [[vertical bars]], [[floor bars]], [[support]], [[spike]], or [[gear assembly]].)

By default you can choose the specific mechanisms you wish to use, from a list of all you have created (and are not forbidden or isolated by [[path]]) - your first selection will be attached to the item/barrier in question (the door, floodgate, cage, whatever), and the second selection will be linked at the lever end (the order is important when dealing with [[magma]]).

A lever can be connected to any number of objects at the same time, but, as each linking is a [[job]] designated at that lever, only one linking job will be tasked at any one time - after that job is finished, the next will begin. (That is, if you want one lever connected to 101 different doors, hatches, cages, bridges and supports, you can do that, but those jobs will not occur ''simultaneously''.) Up to 10 linking jobs can be queued up at any one time on one lever, the same as with jobs at any workshop.

Once a link is completed (not queued), the target will no longer appear in the lever's target list. However, if you queue the same linkage twice then both tasks will be performed. This has no effect other than to use up more mechanisms.

Once linked, a trigger must be deconstructed to de-link it from a system*; this also unlinks all other connected systems to that trigger, but has no effect on other triggers linked to the same system(s).

:''(* Or if the other end is deconstructed, the door, hatch, column, bridge or whatever, that un-links the trigger as well, but any other system remains linked.)''

==Activating levers==
A lever is activated (or "pulled") through its {{k|q}} menu with via the "{{k|a}}dd new task {{k|P}}ull" keys, which establishes a new [[job]] that then needs to be filled. An idle dwarf will then come to pull the lever - no labor need be designated for this task, so ''any'' dwarf might volunteer, and from ''anywhere'' on the map that has a [[path]] to that lever at the time, though in most cases the nearest dwarf will be chosen.

[[Tantrum]]ing dwarves have also been reported to pull levers at random, leading to all kinds of [[fun]].

Note that once the actual ''lever'' is pulled, any attached objects may take more time to respond - see below.

==On/Off vs Open/Close==
Levers normally have an "on" and an "off" state, seen as whether the small tag at the top of the lever is to the left ("off" state) or the right ("on" state). Upon being pulled, the state of the lever changes, and everything they're connected to updates to the ''corresponding'' state of that lever, and does not just ''change'' states ("toggle"). This becomes important if you have several levers attached to the same device, or one trigger attached to several systems.
:Example: 2 levers (both in "off" position) are connected to a drawbridge. After pulling the first lever, the bridge will lift. Pulling the second lever tells the bridge to "open", which it already has done - no visible effect. When it is pulled a second time it will let the bridge down. This in turn requires the ''first'' lever (still in "open/lift" position) to be pulled twice to trigger a change (lift again), and so on.

"On" and "off" state is fixed and dependent on the lever, not the object that lever is linked to:

* "dash to the right" ( '''ó''' ) is '''on'''
* "dash to the left" ( '''ò''' ) is '''off'''

Note, however, that gear assemblies are ''the sole exception'' to this: Instead of On/Off triggers, they indeed '''do''' toggle.

Several devices, such as [[floodgate]]s and [[bridge]]s, have a delayed response to all incoming signals, and will not respond to subsequent signals until the first has taken effect. For instance, if you pull a lever attached to a floodgate on then off in rapid succession, the floodgate will only respond to the first signal, independent of the position the lever rests in eventually.

==On/Off states==
Objects that can be controlled by levers include:

===== Multiple Uses =====

* [[Bridge]] – Activates 100 steps after being triggered
** '''On:''' Turns the bridge into either a raised drawbridge, or a retracted bridge, depending on which option was chosen when the the bridge was constructed.
** '''Off:''' Returns the bridge to normal.

* [[Door]] – Activates instantly. Note that once you connect a door, it is either completely open or locked. There is no "closed, but can be opened by a dwarf" state anymore.
** '''On:''' Opens the door.
** '''Off:''' Closes the door.

* [[Floodgate]] – Activates 100 steps after being triggered. If blocking a narrow passageway, a door will easily suffice.
** '''On:''' Opens the floodgate.
** '''Off:''' Closes the floodgate.

* [[Floor hatch|Hatch]] – Activates instantly. Note that, like doors, once you connect a hatch, it is either completely open or locked.
** '''On:''' Opens the hatch.
** '''Off:''' Closes the hatch.

* [[Grate]] – Activates 100 steps after being triggered. When it is open, it just disappears. Liquids go through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the grate.
** '''Off:''' Closes the grate.

* [[Bars]] – Activates 100 steps after being triggered. When it is open, it just disappears. Liquids go through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the bars.
** '''Off:''' Closes the bars.

* [[Trap|Upright Spear/Spikes]]
** '''On:''' Retracts spears/spikes.
** '''Off:''' Extends spears/spikes.

* [[Gear assembly]] – When it is disengaged, no power goes through it and anything that is being kept up by its presence (like a [[windmill]] right on top of it) falls down.
** '''On:''' Toggles gear state.
** '''Off:''' Toggles gear state.

===== One-Shot =====

These items, when activated, deconstruct, and/or cannot be triggered again until re-linked.

* [[Cage]] – Deconstructs the cage and releases all of its contents. The cage and its attached mechanism will be left on the floor nearby; you recover the [[mechanism]] used on the cage but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.

* [[Restraint]] – Deconstructs the [[Restraint|chain/rope]] and releases whatever creature it held. The restraint's mechanism will be left on the floor nearby, and the restraint itself will remain attached to the creature's neck; again, you recover the [[mechanism]] used on the restraint but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.
* [[Support]] – Deconstructs the support, ideally without a dwarf next to it. Most commonly used to cause controlled [[cave-in]]s.

==Control Room==
Some player prefer to create a "control room" and lock a dwarf in when they expect to need quick response to their levers, to avoid long delays. A control room is an area where important levers are located. It often has doors/hatches on all entrances, so a dwarf (or more than one) can be locked inside to guarantee that one nearby dwarf will be idle who can pull a lever at a moment's notice, rather than wait for the first idle dwarf to respond, who might be far across the map. This can be critical with some of the more complex [[Trap design|trap designs]]. For longer sieges, a small personal stockpile of booze and food is critical, or an "airlock" that can be (re)stocked for prolonged situations.

Some control rooms have all doors linked to a single lever, which is the first one pulled - this seals in the first volunteer to respond, although {{k|A}}ctivating a specific recruit and stationing them and then manually locking them in the control room is sometimes faster. Double doors, one set manual, and one set linked, allow for manual sealing of the room in either manner. (It's advised to have a backup lever somewhere to open the linked doors in case of accidents.)

Advanced players do not trust doors alone to protect their control room, as some fortress invaders are [[building destroyer]]s, and can deconstruct any door or drawbridge they come across.

Because control rooms often contain levers linked to most every important system in the fortress, it's critical to guard it against troublemakers like [[gremlin]]s and [[tantrum]]ing dwarves. Having wardogs or other attack animals chained at all entrances is a good start, and military stationed nearby is popular as well.

Because of the crowded nature of a control room, it's particularly important to [[label]] your levers, and/or organize them for positive identification as to function. Returning to a game after a week and not remembering which "red" lever releases the magma or shuts the main gate is too much [[fun]] for some players.

==Labeling==
There is no way to determine what levers operate what objects except by pulling them and seeing what happens.* Because of this, it can be critical to, somehow, keep track of what lever does what and where (''especially'' in a control room!). [[Note|Label]]ing each individual lever is (possibly) the most foolproof. Some players (additionally) use architecture or color coding to help label their levers, either placing them near the objects they activate, or in small bays organized in groups (even within a control room), and/or making the mechanism (and linked objects) out of a [[The Non-Dwarf's Guide to Rock|particular colored]] stone, or likewise coloring the nearby wall or floor, or even constructing a letter or symbol in a floor mosaic - whatever works, so long as it ''does'' work.

:(*): Not exactly true. You can attempt to link the lever to a new object. Anything already linked to that lever will not show up in the list, as an existing link cannot be duplicated. So you could, in theory, look through the entire list; any item which doesn't appear in that list is linked. However, this process of elimination becomes a very daunting prospect with, say, doors.

== Computing ==

Elaborate combinations of levers (or pressure plates) and other objects can be used to create mechanical systems that can perform various forms of [[computing]].

{{Buildings}}
[[Category:Buildings]][[Category:Physics]]

40d:Lever

2009-09-09T20:05:09Z

Adeptable: /* Labeling */ be more precise when talking about when items don't show up in the target list

A '''lever''' is a [[mechanism]] that has been constructed on a floor tile. Once in place, it can be linked to one or more other devices such as [[door]]s, [[bridge]]s or [[support]]s, permitting you to remotely control these other devices through the lever's {{k|q}} menu.

Levers do not block any movement. Levers are counted as furniture for [[created wealth]] of a fortress.

[[Pressure plate]]s are like levers, but are activated automatically by [[creatures]] stepping on it, or by fluids reaching a certain (player-selected) depth.

Either a '''lever''' or a [[pressure plate]], once linked to one or more devices ([[door]]s, [[trap]]s, or whatever), can act as a '''trigger''', an activation mechanism for that secondary system. The two are activated differently, but the connected system is activated just the same. One system can have more than one trigger linked to it, and one trigger can be linked to more than one system.

==Placing a lever==
If you have a spare mechanism, you can designate the new lever job via the "{{k|b}}uild {{k|T}}rap {{k|l}}ever" keys, and can use {{k|x}} to choose which specific mechanism to use. Mechanism [[quality]] has no known effect on the performance of the lever. Low-quality mechanisms work fine, but since they are counted as furniture, high quality mechanisms give more [[created wealth]].

==Linking==

Once a mechanism has been placed as a lever, it then requires a pair of [[mechanisms]] to link that lever to any object, regardless of distance or size, and [[quality]] of the mechanism makes no reported difference. This is done by giving the lever the appropriate job order via {{k|q}}(similar to any workshop), selecting what sort of object you want the lever linked to*, and then using the {{k|-}} and {{k|+}} keys to scroll thru the available examples of those and selecting the one you want. The list is chronological, with the last object finished listed last, and the map will re-center on the exact object as you scroll.

:''(* [[bridge]], [[cage]], [[chain]], [[door]], [[floodgate]], [[hatch]], [[wall grate]], [[floor grate]], [[vertical bars]], [[floor bars]], [[support]], [[spike]], or [[gear assembly]].)

By default you can choose the specific mechanisms you wish to use, from a list of all you have created (and are not forbidden or isolated by [[path]]) - your first selection will be attached to the item/barrier in question (the door, floodgate, cage, whatever), and the second selection will be linked at the lever end (the order is important when dealing with [[magma]]).

A lever can be connected to any number of objects at the same time, but, as each linking is a [[job]] designated at that lever, only one linking job will be tasked at any one time - after that job is finished, the next will begin. (That is, if you want one lever connected to 101 different doors, hatches, cages, bridges and supports, you can do that, but those jobs will not occur ''simultaneously''.) Up to 10 linking jobs can be queued up at any one time on one lever, the same as with jobs at any workshop.

Once linked, a trigger must be deconstructed to de-link it from a system*; this also unlinks all other connected systems to that trigger, but has no effect on other triggers linked to the same system(s).

:''(* Or if the other end is deconstructed, the door, hatch, column, bridge or whatever, that un-links the trigger as well, but any other system remains linked.)''

==Activating levers==
A lever is activated (or "pulled") through its {{k|q}} menu with via the "{{k|a}}dd new task {{k|P}}ull" keys, which establishes a new [[job]] that then needs to be filled. An idle dwarf will then come to pull the lever - no labor need be designated for this task, so ''any'' dwarf might volunteer, and from ''anywhere'' on the map that has a [[path]] to that lever at the time, though in most cases the nearest dwarf will be chosen.

[[Tantrum]]ing dwarves have also been reported to pull levers at random, leading to all kinds of [[fun]].

Note that once the actual ''lever'' is pulled, any attached objects may take more time to respond - see below.

==On/Off vs Open/Close==
Levers normally have an "on" and an "off" state, seen as whether the small tag at the top of the lever is to the left ("off" state) or the right ("on" state). Upon being pulled, the state of the lever changes, and everything they're connected to updates to the ''corresponding'' state of that lever, and does not just ''change'' states ("toggle"). This becomes important if you have several levers attached to the same device, or one trigger attached to several systems.
:Example: 2 levers (both in "off" position) are connected to a drawbridge. After pulling the first lever, the bridge will lift. Pulling the second lever tells the bridge to "open", which it already has done - no visible effect. When it is pulled a second time it will let the bridge down. This in turn requires the ''first'' lever (still in "open/lift" position) to be pulled twice to trigger a change (lift again), and so on.

"On" and "off" state is fixed and dependent on the lever, not the object that lever is linked to:

* "dash to the right" ( '''ó''' ) is '''on'''
* "dash to the left" ( '''ò''' ) is '''off'''

Note, however, that gear assemblies are ''the sole exception'' to this: Instead of On/Off triggers, they indeed '''do''' toggle.

Several devices, such as [[floodgate]]s and [[bridge]]s, have a delayed response to all incoming signals, and will not respond to subsequent signals until the first has taken effect. For instance, if you pull a lever attached to a floodgate on then off in rapid succession, the floodgate will only respond to the first signal, independent of the position the lever rests in eventually.

==On/Off states==
Objects that can be controlled by levers include:

===== Multiple Uses =====

* [[Bridge]] – Activates 100 steps after being triggered
** '''On:''' Turns the bridge into either a raised drawbridge, or a retracted bridge, depending on which option was chosen when the the bridge was constructed.
** '''Off:''' Returns the bridge to normal.

* [[Door]] – Activates instantly. Note that once you connect a door, it is either completely open or locked. There is no "closed, but can be opened by a dwarf" state anymore.
** '''On:''' Opens the door.
** '''Off:''' Closes the door.

* [[Floodgate]] – Activates 100 steps after being triggered. If blocking a narrow passageway, a door will easily suffice.
** '''On:''' Opens the floodgate.
** '''Off:''' Closes the floodgate.

* [[Floor hatch|Hatch]] – Activates instantly. Note that, like doors, once you connect a hatch, it is either completely open or locked.
** '''On:''' Opens the hatch.
** '''Off:''' Closes the hatch.

* [[Grate]] – Activates 100 steps after being triggered. When it is open, it just disappears. Liquids go through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the grate.
** '''Off:''' Closes the grate.

* [[Bars]] – Activates 100 steps after being triggered. When it is open, it just disappears. Liquids go through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the bars.
** '''Off:''' Closes the bars.

* [[Trap|Upright Spear/Spikes]]
** '''On:''' Retracts spears/spikes.
** '''Off:''' Extends spears/spikes.

* [[Gear assembly]] – When it is disengaged, no power goes through it and anything that is being kept up by its presence (like a [[windmill]] right on top of it) falls down.
** '''On:''' Toggles gear state.
** '''Off:''' Toggles gear state.

===== One-Shot =====

These items, when activated, deconstruct, and/or cannot be triggered again until re-linked.

* [[Cage]] – Deconstructs the cage and releases all of its contents. The cage and its attached mechanism will be left on the floor nearby; you recover the [[mechanism]] used on the cage but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.

* [[Restraint]] – Deconstructs the [[Restraint|chain/rope]] and releases whatever creature it held. The restraint's mechanism will be left on the floor nearby, and the restraint itself will remain attached to the creature's neck; again, you recover the [[mechanism]] used on the restraint but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.
* [[Support]] – Deconstructs the support, ideally without a dwarf next to it. Most commonly used to cause controlled [[cave-in]]s.

==Control Room==
Some player prefer to create a "control room" and lock a dwarf in when they expect to need quick response to their levers, to avoid long delays. A control room is an area where important levers are located. It often has doors/hatches on all entrances, so a dwarf (or more than one) can be locked inside to guarantee that one nearby dwarf will be idle who can pull a lever at a moment's notice, rather than wait for the first idle dwarf to respond, who might be far across the map. This can be critical with some of the more complex [[Trap design|trap designs]]. For longer sieges, a small personal stockpile of booze and food is critical, or an "airlock" that can be (re)stocked for prolonged situations.

Some control rooms have all doors linked to a single lever, which is the first one pulled - this seals in the first volunteer to respond, although {{k|A}}ctivating a specific recruit and stationing them and then manually locking them in the control room is sometimes faster. Double doors, one set manual, and one set linked, allow for manual sealing of the room in either manner. (It's advised to have a backup lever somewhere to open the linked doors in case of accidents.)

Advanced players do not trust doors alone to protect their control room, as some fortress invaders are [[building destroyer]]s, and can deconstruct any door or drawbridge they come across.

Because control rooms often contain levers linked to most every important system in the fortress, it's critical to guard it against troublemakers like [[gremlin]]s and [[tantrum]]ing dwarves. Having wardogs or other attack animals chained at all entrances is a good start, and military stationed nearby is popular as well.

Because of the crowded nature of a control room, it's particularly important to [[label]] your levers, and/or organize them for positive identification as to function. Returning to a game after a week and not remembering which "red" lever releases the magma or shuts the main gate is too much [[fun]] for some players.

==Labeling==
There is no way to determine what levers operate what objects except by pulling them and seeing what happens.* Because of this, it can be critical to, somehow, keep track of what lever does what and where (''especially'' in a control room!). [[Note|Label]]ing each individual lever is (possibly) the most foolproof. Some players (additionally) use architecture or color coding to help label their levers, either placing them near the objects they activate, or in small bays organized in groups (even within a control room), and/or making the mechanism (and linked objects) out of a [[The Non-Dwarf's Guide to Rock|particular colored]] stone, or likewise coloring the nearby wall or floor, or even constructing a letter or symbol in a floor mosaic - whatever works, so long as it ''does'' work.

:(*): Not exactly true. You can attempt to link the lever to a new object. Anything already linked to that lever will not show up in the list, as an existing link cannot be duplicated. So you could, in theory, look through the entire list; any item which doesn't appear in that list is linked. However, this process of elimination becomes a very daunting prospect with, say, doors.

== Computing ==

Elaborate combinations of levers (or pressure plates) and other objects can be used to create mechanical systems that can perform various forms of [[computing]].

{{Buildings}}
[[Category:Buildings]][[Category:Physics]]

40d Talk:Lever

2009-09-09T20:01:36Z

Adeptable: /* Multiple connections for the same lever/object pair */ tested queuing a link twice, both are done.

== floodgates vs. doors misinformation? ==
"''Therefore, it is more logical to use doors, at least until doors aren't usable for holding back water.''"

I'm fairly certain that doors can't be closed while flooded. They work as described for opening via lever, but cannot close when blocked by water or creatures.
Granted, the last time i've levered doors was back in 2d. Please verify or change the wording? --[[User:Vaevictus|Vaevictus]] 15:49, 2 June 2008 (EDT)

:In the current version{{version|0.27.176.38c}} doors can close if water currently occupies the same square. I believe elsewhere the wiki states this destroys the water, but I have not verified if the water is destroyed. --[[User:Quartic|quartic]] 16:18, 2 June 2008 (EDT)
::Does it matter how much water? -- [[User:Vaevictus|Vaevictus]] 13:35, 3 June 2008 (EDT)
:::I have verified this with water of depth 1 and 7, but not values in between.--[[User:Quartic|quartic]] 13:38, 3 June 2008 (EDT)

Todo: Check whether two levers connected to the same door operate it in the same way the older versions did - that is, pulling each lever once would open the door, then do nothing as the second lever is pulled. -- [[User:Zaratustra|Zaratustra]] 19:23, 7 November 2007 (EST)

I'm using vertical bars as portcullis for my keep, and they attach to levers. Perhaps a comment that bars and grates operate identically in this version, specifically with respect to levers? -Gotthard

Doesn't the delay come from the floodgate grinding to close the water/magma channel/tunnel compared to a door slamming shut right away? --[[User:Karpatius|Karp]] 08:51, 31 October 2008 (EDT)
:That is what it is meant to simulate. Like people mentioned above, though, Toady's said that doors shouldn't work as well as floodgates, so in some later version your doors will probably leak. --[[User:ThunderClaw|ThunderClaw]] 10:09, 31 October 2008 (EDT)

== controlling at a distance ==

Does the lever need to be adjacent to the item it is controlling?

I want to put a floodgate at the end of a channel... [[User:GarrieIrons|GarrieIrons]] 02:52, 23 January 2008 (EST)
:No, it can be anywhere.--[[User:Dorten|Dorten]] 02:57, 23 January 2008 (EST)

so, analog to the support-cave-in-trap how about building a nice water basin, say 4x4 for a start and covering it with grates, all connected to a lever - do grates have to be attached to a wall or floor on one side? I will try *broad grin* --[[User:Koltom|Koltom]] 21:45, 22 February 2008 (EST)

:Grates must be attached to a wall on one side, although you can put grates next to only grates and the dwarves will build them. Followed by their collapse. Like walls off bridges.--[[User:Draco18s|Draco18s]] 18:31, 2 March 2008 (EST)

:Try building supports under them. SL's hand of armok uses supports under hatches in a similar way. [[User:VengefulDonut|VengefulDonut]] 23:37, 2 March 2008 (EST)

::Yeah, its not working like i wanted it too. The support thing will probably work. Or I will just leave a few walls in the basin..will try that later, busy right now. *watches goblin fly away in high arc* --[[User:Koltom|Koltom]] 19:52, 3 March 2008 (EST)

Regarding remote activation/control: I just spent 10 minutes berating my dwarves for completely ignoring two Pull Lever commands while vile forces of darkness approached, only to find that once I removed the Dwarves Stay Indoors restriction, they happily stepped up to the, uh, lever. The bridges are outside, the levers are on the level below. Has anyone else experienced this? [[User:Holyfool|Holyfool]] 17:49, 22 March 2008 (EST)

:Was the lever and/or any part of the path to the lever marked as "outside"? Use {{k|k}} to check. --[[User:Savok|Savok]] 10:25, 23 March 2008 (EDT)

::I checked and one of the levers was indeed marked "outside". In fact, there are several squares on my first underground level that are marked "outside". Is that because they are in the general area of the stairway leading outside? Thank you for the info. --[[User:Holyfool|Holyfool]] 18:42, 29 March 2008 (EDT)

:::When I quit reading all new forum messages and stayed at the wiki, I thought this would stop. [[Outside|Read The Wiki]]. Really. Read it. No, really, click on that link. --[[User:Savok|Savok]] 19:57, 29 March 2008 (EDT)

== Megabeasts ==

I have noticed that a bridge that a hydra is standing on cannot be retracted {{version|0.27.176.38c}}. Has anyone else had similar experiences? [[User:VengefulDonut|VengefulDonut]] 00:15, 13 March 2008 (EDT)

:Titans cause the same problem. I conjecture that bridged can't be retracted while megabeasts are standing on them. [[User:VengefulDonut|VengefulDonut]] 02:08, 13 March 2008 (EDT)

:Also elephants, it seems. Possibly creature size. [[User:VengefulDonut|VengefulDonut]] 13:18, 13 March 2008 (EDT)

:Dragons cause the same problem. Are megabeasts supposed to all show up at once like this? [[User:VengefulDonut|VengefulDonut]] 21:43, 13 March 2008 (EDT)

:: "All at once like this," you say? Was their a [[fun|party]] on your bridgeworks?
:: And, yeah, megabeasts kill bridge operation, even "benign" acts like retracting with them on it. It must have something to do with their BUILDINGDESTROYER tag. --[[User:FJH|FJH]] 02:58, 6 April 2009 (UTC)

== Proposed addition: Mechanism sequence ==

Given the problems that arise when using non magma-safe materials for mechanisms on floodgates, it is quite handy to know which mechanisms go where at the link selection (When for example you're really low on bauxite). 
From my experimentation with floodgate-lever, the first mechanism selected goes at the gate and the second one at the lever. I still haven't activated the contraption, but I'm assuming it's going to be ok. 
I'm also assuming the same is usefull for grates and bars. --[[User:Nonickch]], unsigned

:There is some lower-down text that tells you which mechanism goes in where. --[[User:Savok|Savok]] 08:30, 15 June 2008 (EDT)

== Finding Links ==

Is it possible to determine what a lever is linked to without pulling it and checking to see what happens? -[[User:Fuzzy|Fuzzy]] 00:43, 6 September 2008 (EDT)
:AFAIK the only way is to attempt to link the lever to a built object and notice which one if any is not available.
:eg if you have two bridges but only one is available to be linked to, it is because you are already linked to the other one.
:This would be a really good feature if it was implemented.
:[[User:GarrieIrons|GarrieIrons]] 09:55, 6 September 2008 (EDT)

:I guess this is one good use for the new note-feature: Just use the same note for lever and target. --[[User:Doub|Doub]] 10:17, 6 September 2008 (EDT)

:Right now your best way to remember what lever does what is to build a reference behind the lever as a reminder: a one-tile bridge behind the "front door/bridge" lever, a support behind the "collapse the mountain" lever and so forth... or write down what does what on paper. Even naming levers would be useful but for now you need the "references." -[[User:Karpatius|Karp]] 06:10, 19 December 2008 (EST)

== Max number of links? ==

''Is there a limit to the amount of objects that can be linked to a lever?''--[[User:Thendash|Thendash]] 22:56, 19 September 2008 (EDT)

== Speeding the job of linking ==

Is it just me or does it not only take forever to finish the job of linking the lever to something, but also the dwarves treat it as extremely low priority? I've sometimes had to had an entire year for one of them to deign to hook it up. Incidentally, it is the Mechanics job that they use for that, right? -[[User:Fuzzy|Fuzzy]] 15:48, 27 September 2008 (EDT)

: I haven't noticed anything about the priority of the job, but yes, it take hella long to finish it. Some big linking job (eg. linking a large bridge to a remote lever) are virtually impossible to complete without an experienced mecanic... dwarves don't manage to end the job before feeling the urge to eat or drink or something, and all their work is lost when they return, ending in an infinite loop. [[User:Timst|Timst]] 19:47, 27 September 2008 (EDT)

: Unless it's changed in the year since I've played, the mechanic must move the mechanisms to the lever and the "something", then spend time working on both the lever and the "something", all without being interrupted. Consider a 1-square stockpile next to both the lever and the something and choosing those unique mechanisms when you assign the linkage job. -- [[User:Qwip|Qwip]] 16:42, 15 October 2008 (EDT)

:: The catch, so far, is figuring out the "unique" mechanisms in the list. Short of making sure that that stockpile is the only one that carries Schist Mechanisms or something similar... Unlike the other "pick an item" lists, you can't specify a sort and there's nothing zooming you to the item that you will use. On a mildly unrelated note, I realized that part of the reason for my delay was that I was building large amounts of stone traps, so the nearest mechanism that was not already tied up in a trap building job was quote some distance away. I had this problem with the nearby stockpile as well, as it was also fairly close to the traps. It would be nice to even get a distance count on the mechanisms. -[[User:Fuzzy|Fuzzy]] 11:48, 16 October 2008 (EDT)

:::When you choose the mechanism for the lever or trap, it does tell you its distance.--[[User:Maximus|Maximus]] 12:33, 16 October 2008 (EDT)

:::: Addendum to Maximus's comment: When selecting the material to be used, you can e{{k|x}}pand the list of materials, and then select a particular item. Therefore, you can build a single-tile stockpile, then customize it (using {{k|q}} then {{k|s}}settings) to only allow a certain quality mechanism. Link the lever after these stockpiles have been filled. [[User:RomeoFalling|RomeoFalling]] 16:21, 16 October 2008 (EDT)

== Inverting a Lever ==

I think I found a way to automatically invert the signal of a lever, say if you wanted one lever to open one door and close another. It involves a bridge and water, so it would not be instant. I haven't tested it yet. Anyone know if it would work?
<pre>Side view: (Sorry, I realize this isn't the standard tileset, but my text editor doesn't have them all.)
#####
#_~@W
##D##

W - Water source (Under at least 7/7 pressure)
D - Water drain
_ - Pressure plate, set to activate under water of depth 4-7
@ - Hinge of a raisable bridge, connected to the main lever (offscreen)
~ - Bridge over channel
# - Solid rock</pre>
When the main lever is OFF, the bridge is down. It allows water to flow past its hinge, and it covers the drain. Water fills the room, triggering the plate, which sends an ON signal. 
When the main lever is ON, the bridge raises. The hinge blocks water from flowing in, and the uncovered drain empties the room. The plate detriggers, sending OFF. 
WARNING: The drain must not fill! If it does, you wont be able to get into the room to connect more mechanisms to the plate.
Option: If your water source is infinite, make your drain a hallway, at least 3 long, with a raising bridge that comes down from the far end. When the main lever is activated, the hallway floods. Shortly afterwards, the plate detriggers. After a short delay, the bridge slams down, destroying the water. 
--17:52, 1 October 2008 (EDT)

: Isn't it simpler to build two levers? Especially considering the pressure plate takes as many mechanisms? I don't really understand what you are trying to accomplish here.
:--[[User:MagicGuigz|MagicGuigz]] 17:34, 15 October 2008 (EDT)

::If you want a single action to do some "on" actions and some "off" actions - e.g. if from a stylistic point of view you want to have a single "activate outer defenses" lever that raises bridges over moats and puts down bridges blocking catapults.
::--[[User:Random832|Random832]] 19:35, 15 October 2008 (EDT)

::: It's more than stylistic. My designs are complex systems, created on the assumption that only certain combinations of states are possible - that when ''this'' bridge is down, ''that'' bridge is always up, and that when ''this'' floodgate is open, ''that'' door is always closed. If I allow things to enter a condition I hadn't planned for - either because I forgot to throw both leavers, or the dwarf died between them, or whatever - there is literally no telling what would happen. It could drop civilians into a line of fire, or flood the fortress, or expose the marksdwarves to the enemy without also releasing their infantry guards.
:::--[[User:Macdjord|Macdjord]] 16:08, 16 October 2008 (EDT)

:I'd say you should consult the [[Computing]] and [[Mechanical Logic]] pages then. Should find all the components you need there.
:--[[User:Bilkinson|Bilkinson]] 16:13, 16 October 2008 (EDT)

::Doesn't help. That's all about power transfer - gears, axels, waterwheels... It only uses levers for input, not output - I could connect my controll leaver to a not-gate like [[Mechanical_Logic#NOT_or_BUFFER|this one]], but how do i connect ''that'' to a bridge?
::--[[User:Macdjord|Macdjord]] 17:17, 16 October 2008 (EDT)

:::Connect that power to a screw pump, that pours water onto a pressure plate. There's an example of such a device on the mechanics page. Take a look as Water/Fluid logic as well (Linked to on the mechanical page) for some other pump-based devices.
:::--[[User:Bilkinson|Bilkinson]] 06:56, 17 October 2008 (EDT)

:::It's... ''workable'', I suppose. It's much more complex than the bridge system. It might be faster responding, depending on the speed at which a pump works, since there is no 100 step delay like a bridge. It would take a lot more room and mechanisms, not to mention a seperate power source for each one. Remember, each leaver you invert need its own, independent setup.
::::--[[User:Macdjord|Macdjord]] 13:09, 17 October 2008 (EDT)

:::: Check out this page, it might help.. www.dwarffortresswiki.net/index.php/User:SL/Logic_Gates.
::::[[User:Martinuzz|Martinuzz]] 8:54, 28 October 2008 (EDT)

: So the goal here is to have water on a pressure plate when a lever is set to ON. Don't hatch covers respond quicker than bridges?

: Gee, this sucks. I thought things just toggled whenever you flipped the lever. That's how it should be IMHO. [[User:Gairabad|Gairabad]] 20:31, 13 November 2008 (EST)

<pre>
Side view:

####
#^HW
##D#

^ = Pressure Plate
W - Water Inlet
D - Drain
H - Hatch Cover
# - Solid rock
</pre>
:Main lever linked to Hatch Cover (H). When the lever is OFF, the hatch is closed and the Pressure Plate (^) chamber fills. When the lever is ON, the Hatch Cover (H) disappears and water drains away before reaching the pressure plate ledge.
:[[User:Wangcommander|Wangcommander]] 01:27, 12 November 2008 (EST)

:: But since you're not actually blocking off the water, you are dependent on the fickleness of the water pressure simulation. Sure, the room would never fill with an open hatch between the water source and the hatch, but after the first use it ''starts off'' filled. Are you certain it will drain? If the water comes in from the source as fast as it goes out the drain, will it not stay full? That's the advantage of using the bridge - it is the only piece of equipment that blocks water in the ON position.
:: A hybrid design might be useful, using a bridge to block the input bu a hatch to control the output. When you switch it, the hatch instantly starts draining the water, then the bridge seals the inlet 100 ticks later to guarantee a complete drain.
:: --[[User:Macdjord|Macdjord]] 16:04, 12 November 2008 (EST)

I might be misunderstanding the goal of this (and, for the record, I do think it's really cool), but wouldn't hooking up the lever to the thing you want non-inverted, then flipping the switch, and then hooking it up to the inverted thing accomplish the same thing? That way you have two things hooked up to the lever that are in opposite states of each other..... [[User:Zardus|Zardus]] 05:09, 26 February 2009 (EST)
:A 'Pull the lever' task is not a logical toggle. It toggles the lever, and then activates the lever to signal its current state to its linkages... That is, if the lever is in the 'open' position, pulling it flips it to 'closed' and then sends 'closed' to all its linked buildings. Anything which is, for whatever reason, currently in the 'closed' state will simply remain closed. The case you describe is such a situation. It can also arise where a lever is pulled twice in less time than it takes for the first signal to produce its effect. That is: A dwarf pulls a lever linked to a bridge. The dwarf takes 2 steps away, pauses to decide what to do, and notices that there's a pull the lever task on a lever 2 steps away. The dwarf returns to pull the lever again. The bridge has not yet raised when the second signal is sent... A little bit later, the bridge will raise, but unless the lever is pulled again, to get it into the 'raise' state, and then a fourth time to get it to the 'lower' state, the bridge will not lower.--[[User:Wattj|wattj]] 11:03, 26 February 2009 (EST)
Something like this? [[http://dwarf.lendemaindeveille.com/images/4/48/LeverInvert.gif]] --[[Grek]]

== how to disconnect levers? ==

Is there a way to disconnect a lever from an object without destroying the lever and rebuilding it? --[[User:Shaver|Shaver]] 12:53, 2 January 2009 (EST)
:You can't, to my knowledge. Mechanisms in a lever and the connections stay in place until the lever is deconstructed. I use a lever for cage traps in an arena, and after every 'round' I need to rebuild it to get back the mechanisms I used. --[[User:Eddie|Eddie]] 14:17, 2 January 2009 (EST)
:You could deconstruct the object :) --[[User:Adeptable|Adeptable]] 07:47, 9 September 2009 (UTC)

== See what's connected to a lever? ==

Is there a way to see what's connected to a lever? I've lost track of which lever does what, and I'd prefer to not randomly set off my traps trying each one out. --[[User:Katt|Katt]] 00:15, 3 March 2009 (EST)

No. This is why its a good idea to keep levers proximal to objects they connect to. I also try to color code levers to the object and gears used for the connection. --[[User:Squirrelloid|Squirrelloid]] 01:36, 3 March 2009 (EST)

You can also use the Notes thing to label them. --[[User:LegacyCWAL|LegacyCWAL]] 17:15, 3 March 2009 (EST)

Mystery levers have historically been a great source of [[fun]]. Especially in bloodline games. --[[User:Jellyfishgreen|Jellyfishgreen]] 10:16, 4 June 2009 (UTC)

== Multiple connections for the same lever/object pair ==
I've just removed the text:
<blockquote>
A lever can be linked more than once to the same object - this has no effect except to consume more pairs of mechanisms.
</blockquote>

because I don't experience this in 0.28.181.40d15

--[[User:Adeptable|Adeptable]] 17:34, 6 September 2009 (UTC)

:Confirmed - partly. Once a lever is successfully linked(but NOT when the linkage is in queue), that item will no longer appear in the lever's list of things that can be linked. Might need to confirm what happens if you queue the same object twice. I think the second link job spits out an error when the queue reaches it but I'm not sure. --[[User:Shurhaian|Shurhaian]]

:: Hmm, I just tried queuing the same link (lever to door) twice. Both links were made, and now the door contains two mechanisms. So it is possible... I'll add this back to the article with some explanation. --[[User:Adeptable|Adeptable]] 20:01, 9 September 2009 (UTC)

40d Talk:Lever

2009-09-09T07:49:07Z

Adeptable: /* See what's connected to a lever? */ add new section

40d Talk:Lever

2009-09-09T07:47:50Z

Adeptable: /* how to disconnect levers? */ reply - can deconstruct either end

== floodgates vs. doors misinformation? ==
"''Therefore, it is more logical to use doors, at least until doors aren't usable for holding back water.''"

I'm fairly certain that doors can't be closed while flooded. They work as described for opening via lever, but cannot close when blocked by water or creatures.
Granted, the last time i've levered doors was back in 2d. Please verify or change the wording? --[[User:Vaevictus|Vaevictus]] 15:49, 2 June 2008 (EDT)

:In the current version{{version|0.27.176.38c}} doors can close if water currently occupies the same square. I believe elsewhere the wiki states this destroys the water, but I have not verified if the water is destroyed. --[[User:Quartic|quartic]] 16:18, 2 June 2008 (EDT)
::Does it matter how much water? -- [[User:Vaevictus|Vaevictus]] 13:35, 3 June 2008 (EDT)
:::I have verified this with water of depth 1 and 7, but not values in between.--[[User:Quartic|quartic]] 13:38, 3 June 2008 (EDT)

Todo: Check whether two levers connected to the same door operate it in the same way the older versions did - that is, pulling each lever once would open the door, then do nothing as the second lever is pulled. -- [[User:Zaratustra|Zaratustra]] 19:23, 7 November 2007 (EST)

I'm using vertical bars as portcullis for my keep, and they attach to levers. Perhaps a comment that bars and grates operate identically in this version, specifically with respect to levers? -Gotthard

Doesn't the delay come from the floodgate grinding to close the water/magma channel/tunnel compared to a door slamming shut right away? --[[User:Karpatius|Karp]] 08:51, 31 October 2008 (EDT)
:That is what it is meant to simulate. Like people mentioned above, though, Toady's said that doors shouldn't work as well as floodgates, so in some later version your doors will probably leak. --[[User:ThunderClaw|ThunderClaw]] 10:09, 31 October 2008 (EDT)

== controlling at a distance ==

Does the lever need to be adjacent to the item it is controlling?

I want to put a floodgate at the end of a channel... [[User:GarrieIrons|GarrieIrons]] 02:52, 23 January 2008 (EST)
:No, it can be anywhere.--[[User:Dorten|Dorten]] 02:57, 23 January 2008 (EST)

so, analog to the support-cave-in-trap how about building a nice water basin, say 4x4 for a start and covering it with grates, all connected to a lever - do grates have to be attached to a wall or floor on one side? I will try *broad grin* --[[User:Koltom|Koltom]] 21:45, 22 February 2008 (EST)

:Grates must be attached to a wall on one side, although you can put grates next to only grates and the dwarves will build them. Followed by their collapse. Like walls off bridges.--[[User:Draco18s|Draco18s]] 18:31, 2 March 2008 (EST)

:Try building supports under them. SL's hand of armok uses supports under hatches in a similar way. [[User:VengefulDonut|VengefulDonut]] 23:37, 2 March 2008 (EST)

::Yeah, its not working like i wanted it too. The support thing will probably work. Or I will just leave a few walls in the basin..will try that later, busy right now. *watches goblin fly away in high arc* --[[User:Koltom|Koltom]] 19:52, 3 March 2008 (EST)

Regarding remote activation/control: I just spent 10 minutes berating my dwarves for completely ignoring two Pull Lever commands while vile forces of darkness approached, only to find that once I removed the Dwarves Stay Indoors restriction, they happily stepped up to the, uh, lever. The bridges are outside, the levers are on the level below. Has anyone else experienced this? [[User:Holyfool|Holyfool]] 17:49, 22 March 2008 (EST)

:Was the lever and/or any part of the path to the lever marked as "outside"? Use {{k|k}} to check. --[[User:Savok|Savok]] 10:25, 23 March 2008 (EDT)

::I checked and one of the levers was indeed marked "outside". In fact, there are several squares on my first underground level that are marked "outside". Is that because they are in the general area of the stairway leading outside? Thank you for the info. --[[User:Holyfool|Holyfool]] 18:42, 29 March 2008 (EDT)

:::When I quit reading all new forum messages and stayed at the wiki, I thought this would stop. [[Outside|Read The Wiki]]. Really. Read it. No, really, click on that link. --[[User:Savok|Savok]] 19:57, 29 March 2008 (EDT)

== Megabeasts ==

I have noticed that a bridge that a hydra is standing on cannot be retracted {{version|0.27.176.38c}}. Has anyone else had similar experiences? [[User:VengefulDonut|VengefulDonut]] 00:15, 13 March 2008 (EDT)

:Titans cause the same problem. I conjecture that bridged can't be retracted while megabeasts are standing on them. [[User:VengefulDonut|VengefulDonut]] 02:08, 13 March 2008 (EDT)

:Also elephants, it seems. Possibly creature size. [[User:VengefulDonut|VengefulDonut]] 13:18, 13 March 2008 (EDT)

:Dragons cause the same problem. Are megabeasts supposed to all show up at once like this? [[User:VengefulDonut|VengefulDonut]] 21:43, 13 March 2008 (EDT)

:: "All at once like this," you say? Was their a [[fun|party]] on your bridgeworks?
:: And, yeah, megabeasts kill bridge operation, even "benign" acts like retracting with them on it. It must have something to do with their BUILDINGDESTROYER tag. --[[User:FJH|FJH]] 02:58, 6 April 2009 (UTC)

== Proposed addition: Mechanism sequence ==

Given the problems that arise when using non magma-safe materials for mechanisms on floodgates, it is quite handy to know which mechanisms go where at the link selection (When for example you're really low on bauxite). 
From my experimentation with floodgate-lever, the first mechanism selected goes at the gate and the second one at the lever. I still haven't activated the contraption, but I'm assuming it's going to be ok. 
I'm also assuming the same is usefull for grates and bars. --[[User:Nonickch]], unsigned

:There is some lower-down text that tells you which mechanism goes in where. --[[User:Savok|Savok]] 08:30, 15 June 2008 (EDT)

== Finding Links ==

Is it possible to determine what a lever is linked to without pulling it and checking to see what happens? -[[User:Fuzzy|Fuzzy]] 00:43, 6 September 2008 (EDT)
:AFAIK the only way is to attempt to link the lever to a built object and notice which one if any is not available.
:eg if you have two bridges but only one is available to be linked to, it is because you are already linked to the other one.
:This would be a really good feature if it was implemented.
:[[User:GarrieIrons|GarrieIrons]] 09:55, 6 September 2008 (EDT)

:I guess this is one good use for the new note-feature: Just use the same note for lever and target. --[[User:Doub|Doub]] 10:17, 6 September 2008 (EDT)

:Right now your best way to remember what lever does what is to build a reference behind the lever as a reminder: a one-tile bridge behind the "front door/bridge" lever, a support behind the "collapse the mountain" lever and so forth... or write down what does what on paper. Even naming levers would be useful but for now you need the "references." -[[User:Karpatius|Karp]] 06:10, 19 December 2008 (EST)

== Max number of links? ==

''Is there a limit to the amount of objects that can be linked to a lever?''--[[User:Thendash|Thendash]] 22:56, 19 September 2008 (EDT)

== Speeding the job of linking ==

Is it just me or does it not only take forever to finish the job of linking the lever to something, but also the dwarves treat it as extremely low priority? I've sometimes had to had an entire year for one of them to deign to hook it up. Incidentally, it is the Mechanics job that they use for that, right? -[[User:Fuzzy|Fuzzy]] 15:48, 27 September 2008 (EDT)

: I haven't noticed anything about the priority of the job, but yes, it take hella long to finish it. Some big linking job (eg. linking a large bridge to a remote lever) are virtually impossible to complete without an experienced mecanic... dwarves don't manage to end the job before feeling the urge to eat or drink or something, and all their work is lost when they return, ending in an infinite loop. [[User:Timst|Timst]] 19:47, 27 September 2008 (EDT)

: Unless it's changed in the year since I've played, the mechanic must move the mechanisms to the lever and the "something", then spend time working on both the lever and the "something", all without being interrupted. Consider a 1-square stockpile next to both the lever and the something and choosing those unique mechanisms when you assign the linkage job. -- [[User:Qwip|Qwip]] 16:42, 15 October 2008 (EDT)

:: The catch, so far, is figuring out the "unique" mechanisms in the list. Short of making sure that that stockpile is the only one that carries Schist Mechanisms or something similar... Unlike the other "pick an item" lists, you can't specify a sort and there's nothing zooming you to the item that you will use. On a mildly unrelated note, I realized that part of the reason for my delay was that I was building large amounts of stone traps, so the nearest mechanism that was not already tied up in a trap building job was quote some distance away. I had this problem with the nearby stockpile as well, as it was also fairly close to the traps. It would be nice to even get a distance count on the mechanisms. -[[User:Fuzzy|Fuzzy]] 11:48, 16 October 2008 (EDT)

:::When you choose the mechanism for the lever or trap, it does tell you its distance.--[[User:Maximus|Maximus]] 12:33, 16 October 2008 (EDT)

:::: Addendum to Maximus's comment: When selecting the material to be used, you can e{{k|x}}pand the list of materials, and then select a particular item. Therefore, you can build a single-tile stockpile, then customize it (using {{k|q}} then {{k|s}}settings) to only allow a certain quality mechanism. Link the lever after these stockpiles have been filled. [[User:RomeoFalling|RomeoFalling]] 16:21, 16 October 2008 (EDT)

== Inverting a Lever ==

I think I found a way to automatically invert the signal of a lever, say if you wanted one lever to open one door and close another. It involves a bridge and water, so it would not be instant. I haven't tested it yet. Anyone know if it would work?
<pre>Side view: (Sorry, I realize this isn't the standard tileset, but my text editor doesn't have them all.)
#####
#_~@W
##D##

W - Water source (Under at least 7/7 pressure)
D - Water drain
_ - Pressure plate, set to activate under water of depth 4-7
@ - Hinge of a raisable bridge, connected to the main lever (offscreen)
~ - Bridge over channel
# - Solid rock</pre>
When the main lever is OFF, the bridge is down. It allows water to flow past its hinge, and it covers the drain. Water fills the room, triggering the plate, which sends an ON signal. 
When the main lever is ON, the bridge raises. The hinge blocks water from flowing in, and the uncovered drain empties the room. The plate detriggers, sending OFF. 
WARNING: The drain must not fill! If it does, you wont be able to get into the room to connect more mechanisms to the plate.
Option: If your water source is infinite, make your drain a hallway, at least 3 long, with a raising bridge that comes down from the far end. When the main lever is activated, the hallway floods. Shortly afterwards, the plate detriggers. After a short delay, the bridge slams down, destroying the water. 
--17:52, 1 October 2008 (EDT)

: Isn't it simpler to build two levers? Especially considering the pressure plate takes as many mechanisms? I don't really understand what you are trying to accomplish here.
:--[[User:MagicGuigz|MagicGuigz]] 17:34, 15 October 2008 (EDT)

::If you want a single action to do some "on" actions and some "off" actions - e.g. if from a stylistic point of view you want to have a single "activate outer defenses" lever that raises bridges over moats and puts down bridges blocking catapults.
::--[[User:Random832|Random832]] 19:35, 15 October 2008 (EDT)

::: It's more than stylistic. My designs are complex systems, created on the assumption that only certain combinations of states are possible - that when ''this'' bridge is down, ''that'' bridge is always up, and that when ''this'' floodgate is open, ''that'' door is always closed. If I allow things to enter a condition I hadn't planned for - either because I forgot to throw both leavers, or the dwarf died between them, or whatever - there is literally no telling what would happen. It could drop civilians into a line of fire, or flood the fortress, or expose the marksdwarves to the enemy without also releasing their infantry guards.
:::--[[User:Macdjord|Macdjord]] 16:08, 16 October 2008 (EDT)

:I'd say you should consult the [[Computing]] and [[Mechanical Logic]] pages then. Should find all the components you need there.
:--[[User:Bilkinson|Bilkinson]] 16:13, 16 October 2008 (EDT)

::Doesn't help. That's all about power transfer - gears, axels, waterwheels... It only uses levers for input, not output - I could connect my controll leaver to a not-gate like [[Mechanical_Logic#NOT_or_BUFFER|this one]], but how do i connect ''that'' to a bridge?
::--[[User:Macdjord|Macdjord]] 17:17, 16 October 2008 (EDT)

:::Connect that power to a screw pump, that pours water onto a pressure plate. There's an example of such a device on the mechanics page. Take a look as Water/Fluid logic as well (Linked to on the mechanical page) for some other pump-based devices.
:::--[[User:Bilkinson|Bilkinson]] 06:56, 17 October 2008 (EDT)

:::It's... ''workable'', I suppose. It's much more complex than the bridge system. It might be faster responding, depending on the speed at which a pump works, since there is no 100 step delay like a bridge. It would take a lot more room and mechanisms, not to mention a seperate power source for each one. Remember, each leaver you invert need its own, independent setup.
::::--[[User:Macdjord|Macdjord]] 13:09, 17 October 2008 (EDT)

:::: Check out this page, it might help.. www.dwarffortresswiki.net/index.php/User:SL/Logic_Gates.
::::[[User:Martinuzz|Martinuzz]] 8:54, 28 October 2008 (EDT)

: So the goal here is to have water on a pressure plate when a lever is set to ON. Don't hatch covers respond quicker than bridges?

: Gee, this sucks. I thought things just toggled whenever you flipped the lever. That's how it should be IMHO. [[User:Gairabad|Gairabad]] 20:31, 13 November 2008 (EST)

<pre>
Side view:

####
#^HW
##D#

^ = Pressure Plate
W - Water Inlet
D - Drain
H - Hatch Cover
# - Solid rock
</pre>
:Main lever linked to Hatch Cover (H). When the lever is OFF, the hatch is closed and the Pressure Plate (^) chamber fills. When the lever is ON, the Hatch Cover (H) disappears and water drains away before reaching the pressure plate ledge.
:[[User:Wangcommander|Wangcommander]] 01:27, 12 November 2008 (EST)

:: But since you're not actually blocking off the water, you are dependent on the fickleness of the water pressure simulation. Sure, the room would never fill with an open hatch between the water source and the hatch, but after the first use it ''starts off'' filled. Are you certain it will drain? If the water comes in from the source as fast as it goes out the drain, will it not stay full? That's the advantage of using the bridge - it is the only piece of equipment that blocks water in the ON position.
:: A hybrid design might be useful, using a bridge to block the input bu a hatch to control the output. When you switch it, the hatch instantly starts draining the water, then the bridge seals the inlet 100 ticks later to guarantee a complete drain.
:: --[[User:Macdjord|Macdjord]] 16:04, 12 November 2008 (EST)

I might be misunderstanding the goal of this (and, for the record, I do think it's really cool), but wouldn't hooking up the lever to the thing you want non-inverted, then flipping the switch, and then hooking it up to the inverted thing accomplish the same thing? That way you have two things hooked up to the lever that are in opposite states of each other..... [[User:Zardus|Zardus]] 05:09, 26 February 2009 (EST)
:A 'Pull the lever' task is not a logical toggle. It toggles the lever, and then activates the lever to signal its current state to its linkages... That is, if the lever is in the 'open' position, pulling it flips it to 'closed' and then sends 'closed' to all its linked buildings. Anything which is, for whatever reason, currently in the 'closed' state will simply remain closed. The case you describe is such a situation. It can also arise where a lever is pulled twice in less time than it takes for the first signal to produce its effect. That is: A dwarf pulls a lever linked to a bridge. The dwarf takes 2 steps away, pauses to decide what to do, and notices that there's a pull the lever task on a lever 2 steps away. The dwarf returns to pull the lever again. The bridge has not yet raised when the second signal is sent... A little bit later, the bridge will raise, but unless the lever is pulled again, to get it into the 'raise' state, and then a fourth time to get it to the 'lower' state, the bridge will not lower.--[[User:Wattj|wattj]] 11:03, 26 February 2009 (EST)
Something like this? [[http://dwarf.lendemaindeveille.com/images/4/48/LeverInvert.gif]] --[[Grek]]

== how to disconnect levers? ==

Is there a way to disconnect a lever from an object without destroying the lever and rebuilding it? --[[User:Shaver|Shaver]] 12:53, 2 January 2009 (EST)
:You can't, to my knowledge. Mechanisms in a lever and the connections stay in place until the lever is deconstructed. I use a lever for cage traps in an arena, and after every 'round' I need to rebuild it to get back the mechanisms I used. --[[User:Eddie|Eddie]] 14:17, 2 January 2009 (EST)
:You could deconstruct the object :) --[[User:Adeptable|Adeptable]] 07:47, 9 September 2009 (UTC)

== See what's connected to a lever? ==

Is there a way to see what's connected to a lever? I've lost track of which lever does what, and I'd prefer to not randomly set off my traps trying each one out. --[[User:Katt|Katt]] 00:15, 3 March 2009 (EST)

No. This is why its a good idea to keep levers proximal to objects they connect to. I also try to color code levers to the object and gears used for the connection. --[[User:Squirrelloid|Squirrelloid]] 01:36, 3 March 2009 (EST)

You can also use the Notes thing to label them. --[[User:LegacyCWAL|LegacyCWAL]] 17:15, 3 March 2009 (EST)

Mystery levers have historically been a great source of [[fun]]. Especially in bloodline games. --[[User:Jellyfishgreen|Jellyfishgreen]] 10:16, 4 June 2009 (UTC)

I've just removed the text:
<blockquote>
A lever can be linked more than once to the same object - this has no effect except to consume more pairs of mechanisms.
</blockquote>

because I don't experience this in 0.28.181.40d15

--[[User:Adeptable|Adeptable]] 17:34, 6 September 2009 (UTC)

:Confirmed - partly. Once a lever is successfully linked(but NOT when the linkage is in queue), that item will no longer appear in the lever's list of things that can be linked. Might need to confirm what happens if you queue the same object twice. I think the second link job spits out an error when the queue reaches it but I'm not sure. --[[User:Shurhaian|Shurhaian]]

40d:Weather

2009-09-08T21:24:51Z

Adeptable: /* Rain */ gr

'''Weather''' changes with [[season]]s, and brings [[wet]], [[Climate#Cold|cold]], [[Climate#Hot|hot]], and [[dry]] conditions. It can be turned off by editing init.txt. This takes some load off of the CPU and can result in noticeably faster game play.

==Rain==
Rain is an event occurring at random intervals. The message "It has started raining" appears when it begins to rain. Rain has multiple effects: It cleans [[blood]] off of surfaces, fills murky pools, removes uncollected [[silk]] webs, and can give a [[dwarf]] an unhappy thought.

Dwarfs who are out in the rain will soon get wet and have all their body parts described as {{gametext|Water covering (body part)}} in their inventory menu.

As stated above, when a rain hits a tile labeled as a [[murky pool]], it will begin to fill it up with 1/7 water, and if that does not evaporate the water will grow deeper, until the pool is full. Murky pools do not overflow from rain, but this extra water can be drained off and stored/used. (See the [[Well guide#Using ponds/pools in areas with heavy rain|Well Guide]].) While not much, it can really help maps without 'unlimited' [[water]] supplies such as [[river]]s and [[brook]]s.

Rainfall occurs in [[temperate]] to scorching maps.

==Snow==
In [[winter]], instead of raining it will snow. Snowing has very similar effects to rain, but instead of leaving "wet" squares, it will cover outdoor tiles with snow, including frozen pond tiles. No [[water]] is created by falling snow.

"A snowstorm has arrived", is the message you receive when getting a snowstorm. In the event of a snowstorm, snow will slowly cover the surface the map with snow, and any [[dwarf]] caught in one may get an unhappy thought from it.

Snowstorms will occur in winter on temperate to freezing maps.

==See also==
*[[Climate]]
*[[Biome]]
[[Category:World]]

40d:Lever

2009-09-06T17:44:45Z

Adeptable: /* Control Room */ clarity

A '''lever''' is a [[mechanism]] that has been constructed on a floor tile. Once in place, it can be linked to one or more other devices such as [[door]]s, [[bridge]]s or [[support]]s, permitting you to remotely control these other devices through the lever's {{k|q}} menu.

Levers do not block any movement. Levers are counted as furniture for [[created wealth]] of a fortress.

[[Pressure plate]]s are like levers, but are activated automatically by [[creatures]] stepping on it, or by fluids reaching a certain (player-selected) depth.

Either a '''lever''' or a [[pressure plate]], once linked to one or more devices ([[door]]s, [[trap]]s, or whatever), can act as a '''trigger''', an activation mechanism for that secondary system. The two are activated differently, but the connected system is activated just the same. One system can have more than one trigger linked to it, and one trigger can be linked to more than one system.

==Placing a lever==
If you have a spare mechanism, you can designate the new lever job via the "{{k|b}}uild {{k|T}}rap {{k|l}}ever" keys, and can use {{k|x}} to choose which specific mechanism to use. Mechanism [[quality]] has no known effect on the performance of the lever. Low-quality mechanisms work fine, but since they are counted as furniture, high quality mechanisms give more [[created wealth]].

==Linking==

Once a mechanism has been placed as a lever, it then requires a pair of [[mechanisms]] to link that lever to any object, regardless of distance or size, and [[quality]] of the mechanism makes no reported difference. This is done by giving the lever the appropriate job order via {{k|q}}(similar to any workshop), selecting what sort of object you want the lever linked to*, and then using the {{k|-}} and {{k|+}} keys to scroll thru the available examples of those and selecting the one you want. The list is chronological, with the last object finished listed last, and the map will re-center on the exact object as you scroll.

:''(* [[bridge]], [[cage]], [[chain]], [[door]], [[floodgate]], [[hatch]], [[wall grate]], [[floor grate]], [[vertical bars]], [[floor bars]], [[support]], [[spike]], or [[gear assembly]].)

By default you can choose the specific mechanisms you wish to use, from a list of all you have created (and are not forbidden or isolated by [[path]]) - your first selection will be attached to the item/barrier in question (the door, floodgate, cage, whatever), and the second selection will be linked at the lever end (the order is important when dealing with [[magma]]).

A lever can be connected to any number of objects at the same time, but, as each linking is a [[job]] designated at that lever, only one linking job will be tasked at any one time - after that job is finished, the next will begin. (That is, if you want one lever connected to 101 different doors, hatches, cages, bridges and supports, you can do that, but those jobs will not occur ''simultaneously''.) Up to 10 linking jobs can be queued up at any one time on one lever, the same as with jobs at any workshop.

Once linked, a trigger must be deconstructed to de-link it to a system*; this also unlinks all other connected systems to that trigger, but has no effect on other triggers linked to the same system(s).

:''(* Or if the other end is deconstructed, the door, hatch, column, bridge or whatever, that un-links the trigger as well, but any other system remains linked.)''

==Activating levers==
A lever is activated (or "pulled") through its {{k|q}} menu with via the "{{k|a}}dd new task {{k|P}}ull" keys, which establishes a new [[job]] that then needs to be filled. An idle dwarf will then come to pull the lever - no labor need be designated for this task, so ''any'' dwarf might volunteer, and from ''anywhere'' on the map that has a [[path]] to that lever at the time.

[[Tantrum]]ing dwarves have also been reported to pull levers at random, leading to all kinds of [[fun]].

Note that once the actual ''lever'' is pulled, any attached objects may take more time to respond - see below.

==On/Off vs Open/Close==
Levers normally have an "on" and an "off" state, seen as whether the small tag at the top of the lever is to the left ("off" state) or the right ("on" state). Upon being pulled, the state of the lever changes, and everything they're connected to updates to the ''corresponding'' state of that lever, and does not just ''change'' states ("toggle"). This becomes important if you have several levers attached to the same device, or one trigger attached to several systems.
:Example: 2 levers (both in "off" position) are connected to a drawbridge. After pulling the first lever, the bridge will lift. Pulling the second lever tells the bridge to "open", which it already has done - no visible effect. When it is pulled a second time it will let the bridge down. This in turn requires the ''first'' lever (still in "open/lift" position) to be pulled twice to trigger a change (lift again), and so on.

"On" and "off" state is fixed and dependent on the lever, not the object that lever is linked to:

* "dash to the right" ( '''ó''' ) is '''on'''
* "dash to the left" ( '''ò''' ) is '''off'''

Note, however, that gear assemblies are ''the sole exception'' to this: Instead of On/Off triggers, they indeed '''do''' toggle.

Several devices, such as [[floodgate]]s and [[bridge]]s, have a delayed response to all incoming signals, and will not respond to subsequent signals until the first has taken effect. For instance, if you pull a lever attached to a floodgate on then off in rapid succession, the floodgate will only respond to the first signal, independent of the position the lever rests in eventually.

==On/Off states==
Objects that can be controlled by levers include:

===== Multiple Uses =====

* [[Bridge]] – Bridges have a delay of 100 steps when the lever is pulled.
** '''On:''' Turns the bridge into either a raised drawbridge, or a retracted bridge, depending on which option was chosen when the the bridge was constructed.
** '''Off:''' Returns the bridge to normal.

* [[Door]] – Note that once you connect a door, it is either completely open or locked. There is no "closed, but can be opened by a dwarf" state anymore.
** '''On:''' Opens the door.
** '''Off:''' Closes the door.

* [[Floodgate]] – After the lever is installed, it works exactly like a door. Floodgates, however, have a 100 tick delay. Therefore, it is more logical to use doors for narrow passageways, at least until doors aren't usable for holding back liquids.
** '''On:''' Opens the floodgate.
** '''Off:''' Closes the floodgate.

* [[Floor hatch|Hatch]] – When open it just disappears and allows liquids through. Note that, like doors, once you connect a hatch, it is either completely open or locked.
** '''On:''' Opens the hatch.
** '''Off:''' Closes the hatch.

* [[Grate]] – When it is open, it just disappears. Liquids go through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the grate.
** '''Off:''' Closes the grate.

* [[Bars]] – When it is open, it just disappears. Liquids go through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the bars.
** '''Off:''' Closes the bars.

* [[Trap|Upright Spear/Spikes]]
** '''On:''' Retracts spears/spikes.
** '''Off:''' Extends spears/spikes.

* [[Gear assembly]] – When it is disengaged, no power goes through it and anything that is being kept up by its presence (like a [[windmill]] right on top of it) falls down.
** '''On:''' Toggles gear state.
** '''Off:''' Toggles gear state.

===== One-Shot =====

These items, when activated, deconstruct, and/or cannot be triggered again until re-linked.

* [[Cage]] – Deconstructs the cage and releases all of its contents. The cage and its attached mechanism will be left on the floor nearby; you recover the [[mechanism]] used on the cage but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.

* [[Restraint]] – Deconstructs the [[Restraint|chain/rope]] and releases whatever creature it held. The restraint's mechanism will be left on the floor nearby, and the restraint itself will remain attached to the creature's neck; again, you recover the [[mechanism]] used on the restraint but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.
* [[Support]] – Deconstructs the support, ideally without a dwarf next to it. Most commonly used to cause controlled [[cave-in]]s.

==Control Room==
Some player prefer to create a "control room" and lock a dwarf in when they expect to need quick response to their levers, to avoid long delays. A control room is an area where important levers are located. It often has doors/hatches on all entrances, so a dwarf (or more than one) can be locked inside to guarantee that one nearby dwarf will be idle who can pull a lever at a moment's notice, rather than wait for the first idle dwarf to respond, who might be far across the map. This can be critical with some of the more complex [[Trap design|trap designs]]. For longer sieges, a small personal stockpile of booze and food is critical, or an "airlock" that can be (re)stocked for prolonged situations.

Some control rooms have all doors linked to a single lever, which is the first one pulled - this seals in the first volunteer to respond, although {{k|A}}ctivating a specific recruit and stationing them and then manually locking them in the control room is sometimes faster. Double doors, one set manual, and one set linked, allow for manual sealing of the room in either manner. (It's advised to have a backup lever somewhere to open the linked doors in case of accidents.)

Advanced players do not trust doors alone to protect their control room, as some fortress invaders are [[building destroyer]]s, and can deconstruct any door or drawbridge they come across.

Because control rooms often contain levers linked to most every important system in the fortress, it's critical to guard it against troublemakers like [[gremlin]]s and [[tantrum]]ing dwarves. Having wardogs or other attack animals chained at all entrances is a good start, and military stationed nearby is popular as well.

Because of the crowded nature of a control room, it's particularly important to [[label]] your levers, and/or organize them for positive identification as to function. Returning to a game after a week and not remembering which "red" lever releases the magma or shuts the main gate is too much [[fun]] for some players.

==Labeling==
There is no way to determine what levers operate what objects except by pulling them and seeing what happens. Because of this, it can be critical to, somehow, keep track of what lever does what and where (''especially'' in a control room!). [[Note|Label]]ing each individual lever is (possibly) the most foolproof. Some players (additionally) use architecture or color coding to help label their levers, either placing them near the objects they activate, or in small bays organized in groups (even within a control room), and/or making the mechanism (and linked objects) out of a [[The Non-Dwarf's Guide to Rock|particular colored]] stone, or likewise coloring the nearby wall or floor, or even constructing a letter or symbol in a floor mosaic - whatever works, so long as it ''does'' work.

== Computing ==

Elaborate combinations of levers (or pressure plates) and other objects can be used to create mechanical systems that can perform various forms of [[computing]].

{{Buildings}}
[[Category:Buildings]][[Category:Physics]]

40d:Lever

2009-09-06T17:41:49Z

Adeptable: /* Multiple Uses */ water ->liquids

A '''lever''' is a [[mechanism]] that has been constructed on a floor tile. Once in place, it can be linked to one or more other devices such as [[door]]s, [[bridge]]s or [[support]]s, permitting you to remotely control these other devices through the lever's {{k|q}} menu.

Levers do not block any movement. Levers are counted as furniture for [[created wealth]] of a fortress.

[[Pressure plate]]s are like levers, but are activated automatically by [[creatures]] stepping on it, or by fluids reaching a certain (player-selected) depth.

Either a '''lever''' or a [[pressure plate]], once linked to one or more devices ([[door]]s, [[trap]]s, or whatever), can act as a '''trigger''', an activation mechanism for that secondary system. The two are activated differently, but the connected system is activated just the same. One system can have more than one trigger linked to it, and one trigger can be linked to more than one system.

==Placing a lever==
If you have a spare mechanism, you can designate the new lever job via the "{{k|b}}uild {{k|T}}rap {{k|l}}ever" keys, and can use {{k|x}} to choose which specific mechanism to use. Mechanism [[quality]] has no known effect on the performance of the lever. Low-quality mechanisms work fine, but since they are counted as furniture, high quality mechanisms give more [[created wealth]].

==Linking==

Once a mechanism has been placed as a lever, it then requires a pair of [[mechanisms]] to link that lever to any object, regardless of distance or size, and [[quality]] of the mechanism makes no reported difference. This is done by giving the lever the appropriate job order via {{k|q}}(similar to any workshop), selecting what sort of object you want the lever linked to*, and then using the {{k|-}} and {{k|+}} keys to scroll thru the available examples of those and selecting the one you want. The list is chronological, with the last object finished listed last, and the map will re-center on the exact object as you scroll.

:''(* [[bridge]], [[cage]], [[chain]], [[door]], [[floodgate]], [[hatch]], [[wall grate]], [[floor grate]], [[vertical bars]], [[floor bars]], [[support]], [[spike]], or [[gear assembly]].)

By default you can choose the specific mechanisms you wish to use, from a list of all you have created (and are not forbidden or isolated by [[path]]) - your first selection will be attached to the item/barrier in question (the door, floodgate, cage, whatever), and the second selection will be linked at the lever end (the order is important when dealing with [[magma]]).

A lever can be connected to any number of objects at the same time, but, as each linking is a [[job]] designated at that lever, only one linking job will be tasked at any one time - after that job is finished, the next will begin. (That is, if you want one lever connected to 101 different doors, hatches, cages, bridges and supports, you can do that, but those jobs will not occur ''simultaneously''.) Up to 10 linking jobs can be queued up at any one time on one lever, the same as with jobs at any workshop.

Once linked, a trigger must be deconstructed to de-link it to a system*; this also unlinks all other connected systems to that trigger, but has no effect on other triggers linked to the same system(s).

:''(* Or if the other end is deconstructed, the door, hatch, column, bridge or whatever, that un-links the trigger as well, but any other system remains linked.)''

==Activating levers==
A lever is activated (or "pulled") through its {{k|q}} menu with via the "{{k|a}}dd new task {{k|P}}ull" keys, which establishes a new [[job]] that then needs to be filled. An idle dwarf will then come to pull the lever - no labor need be designated for this task, so ''any'' dwarf might volunteer, and from ''anywhere'' on the map that has a [[path]] to that lever at the time.

[[Tantrum]]ing dwarves have also been reported to pull levers at random, leading to all kinds of [[fun]].

Note that once the actual ''lever'' is pulled, any attached objects may take more time to respond - see below.

==On/Off vs Open/Close==
Levers normally have an "on" and an "off" state, seen as whether the small tag at the top of the lever is to the left ("off" state) or the right ("on" state). Upon being pulled, the state of the lever changes, and everything they're connected to updates to the ''corresponding'' state of that lever, and does not just ''change'' states ("toggle"). This becomes important if you have several levers attached to the same device, or one trigger attached to several systems.
:Example: 2 levers (both in "off" position) are connected to a drawbridge. After pulling the first lever, the bridge will lift. Pulling the second lever tells the bridge to "open", which it already has done - no visible effect. When it is pulled a second time it will let the bridge down. This in turn requires the ''first'' lever (still in "open/lift" position) to be pulled twice to trigger a change (lift again), and so on.

"On" and "off" state is fixed and dependent on the lever, not the object that lever is linked to:

* "dash to the right" ( '''ó''' ) is '''on'''
* "dash to the left" ( '''ò''' ) is '''off'''

Note, however, that gear assemblies are ''the sole exception'' to this: Instead of On/Off triggers, they indeed '''do''' toggle.

Several devices, such as [[floodgate]]s and [[bridge]]s, have a delayed response to all incoming signals, and will not respond to subsequent signals until the first has taken effect. For instance, if you pull a lever attached to a floodgate on then off in rapid succession, the floodgate will only respond to the first signal, independent of the position the lever rests in eventually.

==On/Off states==
Objects that can be controlled by levers include:

===== Multiple Uses =====

* [[Bridge]] – Bridges have a delay of 100 steps when the lever is pulled.
** '''On:''' Turns the bridge into either a raised drawbridge, or a retracted bridge, depending on which option was chosen when the the bridge was constructed.
** '''Off:''' Returns the bridge to normal.

* [[Door]] – Note that once you connect a door, it is either completely open or locked. There is no "closed, but can be opened by a dwarf" state anymore.
** '''On:''' Opens the door.
** '''Off:''' Closes the door.

* [[Floodgate]] – After the lever is installed, it works exactly like a door. Floodgates, however, have a 100 tick delay. Therefore, it is more logical to use doors for narrow passageways, at least until doors aren't usable for holding back liquids.
** '''On:''' Opens the floodgate.
** '''Off:''' Closes the floodgate.

* [[Floor hatch|Hatch]] – When open it just disappears and allows liquids through. Note that, like doors, once you connect a hatch, it is either completely open or locked.
** '''On:''' Opens the hatch.
** '''Off:''' Closes the hatch.

* [[Grate]] – When it is open, it just disappears. Liquids go through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the grate.
** '''Off:''' Closes the grate.

* [[Bars]] – When it is open, it just disappears. Liquids go through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the bars.
** '''Off:''' Closes the bars.

* [[Trap|Upright Spear/Spikes]]
** '''On:''' Retracts spears/spikes.
** '''Off:''' Extends spears/spikes.

* [[Gear assembly]] – When it is disengaged, no power goes through it and anything that is being kept up by its presence (like a [[windmill]] right on top of it) falls down.
** '''On:''' Toggles gear state.
** '''Off:''' Toggles gear state.

===== One-Shot =====

These items, when activated, deconstruct, and/or cannot be triggered again until re-linked.

* [[Cage]] – Deconstructs the cage and releases all of its contents. The cage and its attached mechanism will be left on the floor nearby; you recover the [[mechanism]] used on the cage but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.

* [[Restraint]] – Deconstructs the [[Restraint|chain/rope]] and releases whatever creature it held. The restraint's mechanism will be left on the floor nearby, and the restraint itself will remain attached to the creature's neck; again, you recover the [[mechanism]] used on the restraint but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.
* [[Support]] – Deconstructs the support, ideally without a dwarf next to it. Most commonly used to cause controlled [[cave-in]]s.

==Control Room==
Some player prefer to create a "control room" and lock a dwarf in when they expect to need quick response to their levers, to avoid long delays. A control room is an area where all key levers are located. It often has doors/hatches on all entrances, so a dwarf (or more than one) can be locked inside to guarantee that one nearby dwarf will be idle who can pull a lever at a moment's notice, rather than wait for the first idle dwarf to respond, who might be far across the map. This can be critical with some of the more complex [[Trap design|trap designs]]. For longer sieges, a small personal stockpile of booze and food is critical, or an "airlock" that can be (re)stocked for prolonged situations.

Some control rooms have all doors linked to a single lever, which is the first one pulled - this seals in the first volunteer to respond, although {{k|A}}ctivating a specific recruit and stationing them and then manually locking them in the control room is sometimes faster. Double doors, one set manual, and one set linked, allow for manual sealing of the room in either manner. (It's advised to have a backup lever somewhere to open the linked doors in case of accidents.)

Advanced players do not trust doors alone to protect their control room, as some fortress invaders are [[building destroyer]]s, and can deconstruct any door or drawbridge they come across.

Because control rooms often contain levers linked to most every important system in the fortress, it's critical to guard it against troublemakers like [[gremlin]]s and [[tantrum]]ing dwarves. Having wardogs or other attack animals chained at all entrances is a good start, and military stationed nearby is popular as well.

Because of the crowded nature of a control room, it's particularly important to [[label]] your levers, and/or organize them for positive identification as to function. Returning to a game after a week and not remembering which "red" lever releases the magma or shuts the main gate is too much [[fun]] for some players.

==Labeling==
There is no way to determine what levers operate what objects except by pulling them and seeing what happens. Because of this, it can be critical to, somehow, keep track of what lever does what and where (''especially'' in a control room!). [[Note|Label]]ing each individual lever is (possibly) the most foolproof. Some players (additionally) use architecture or color coding to help label their levers, either placing them near the objects they activate, or in small bays organized in groups (even within a control room), and/or making the mechanism (and linked objects) out of a [[The Non-Dwarf's Guide to Rock|particular colored]] stone, or likewise coloring the nearby wall or floor, or even constructing a letter or symbol in a floor mosaic - whatever works, so long as it ''does'' work.

== Computing ==

Elaborate combinations of levers (or pressure plates) and other objects can be used to create mechanical systems that can perform various forms of [[computing]].

{{Buildings}}
[[Category:Buildings]][[Category:Physics]]

40d:Lever

2009-09-06T17:38:55Z

Adeptable: /* On/Off vs Open/Close */ rm info about unlinking - this is explained better in the "Linking" section above

A '''lever''' is a [[mechanism]] that has been constructed on a floor tile. Once in place, it can be linked to one or more other devices such as [[door]]s, [[bridge]]s or [[support]]s, permitting you to remotely control these other devices through the lever's {{k|q}} menu.

Levers do not block any movement. Levers are counted as furniture for [[created wealth]] of a fortress.

[[Pressure plate]]s are like levers, but are activated automatically by [[creatures]] stepping on it, or by fluids reaching a certain (player-selected) depth.

Either a '''lever''' or a [[pressure plate]], once linked to one or more devices ([[door]]s, [[trap]]s, or whatever), can act as a '''trigger''', an activation mechanism for that secondary system. The two are activated differently, but the connected system is activated just the same. One system can have more than one trigger linked to it, and one trigger can be linked to more than one system.

==Placing a lever==
If you have a spare mechanism, you can designate the new lever job via the "{{k|b}}uild {{k|T}}rap {{k|l}}ever" keys, and can use {{k|x}} to choose which specific mechanism to use. Mechanism [[quality]] has no known effect on the performance of the lever. Low-quality mechanisms work fine, but since they are counted as furniture, high quality mechanisms give more [[created wealth]].

==Linking==

Once a mechanism has been placed as a lever, it then requires a pair of [[mechanisms]] to link that lever to any object, regardless of distance or size, and [[quality]] of the mechanism makes no reported difference. This is done by giving the lever the appropriate job order via {{k|q}}(similar to any workshop), selecting what sort of object you want the lever linked to*, and then using the {{k|-}} and {{k|+}} keys to scroll thru the available examples of those and selecting the one you want. The list is chronological, with the last object finished listed last, and the map will re-center on the exact object as you scroll.

:''(* [[bridge]], [[cage]], [[chain]], [[door]], [[floodgate]], [[hatch]], [[wall grate]], [[floor grate]], [[vertical bars]], [[floor bars]], [[support]], [[spike]], or [[gear assembly]].)

By default you can choose the specific mechanisms you wish to use, from a list of all you have created (and are not forbidden or isolated by [[path]]) - your first selection will be attached to the item/barrier in question (the door, floodgate, cage, whatever), and the second selection will be linked at the lever end (the order is important when dealing with [[magma]]).

A lever can be connected to any number of objects at the same time, but, as each linking is a [[job]] designated at that lever, only one linking job will be tasked at any one time - after that job is finished, the next will begin. (That is, if you want one lever connected to 101 different doors, hatches, cages, bridges and supports, you can do that, but those jobs will not occur ''simultaneously''.) Up to 10 linking jobs can be queued up at any one time on one lever, the same as with jobs at any workshop.

Once linked, a trigger must be deconstructed to de-link it to a system*; this also unlinks all other connected systems to that trigger, but has no effect on other triggers linked to the same system(s).

:''(* Or if the other end is deconstructed, the door, hatch, column, bridge or whatever, that un-links the trigger as well, but any other system remains linked.)''

==Activating levers==
A lever is activated (or "pulled") through its {{k|q}} menu with via the "{{k|a}}dd new task {{k|P}}ull" keys, which establishes a new [[job]] that then needs to be filled. An idle dwarf will then come to pull the lever - no labor need be designated for this task, so ''any'' dwarf might volunteer, and from ''anywhere'' on the map that has a [[path]] to that lever at the time.

[[Tantrum]]ing dwarves have also been reported to pull levers at random, leading to all kinds of [[fun]].

Note that once the actual ''lever'' is pulled, any attached objects may take more time to respond - see below.

==On/Off vs Open/Close==
Levers normally have an "on" and an "off" state, seen as whether the small tag at the top of the lever is to the left ("off" state) or the right ("on" state). Upon being pulled, the state of the lever changes, and everything they're connected to updates to the ''corresponding'' state of that lever, and does not just ''change'' states ("toggle"). This becomes important if you have several levers attached to the same device, or one trigger attached to several systems.
:Example: 2 levers (both in "off" position) are connected to a drawbridge. After pulling the first lever, the bridge will lift. Pulling the second lever tells the bridge to "open", which it already has done - no visible effect. When it is pulled a second time it will let the bridge down. This in turn requires the ''first'' lever (still in "open/lift" position) to be pulled twice to trigger a change (lift again), and so on.

"On" and "off" state is fixed and dependent on the lever, not the object that lever is linked to:

* "dash to the right" ( '''ó''' ) is '''on'''
* "dash to the left" ( '''ò''' ) is '''off'''

Note, however, that gear assemblies are ''the sole exception'' to this: Instead of On/Off triggers, they indeed '''do''' toggle.

Several devices, such as [[floodgate]]s and [[bridge]]s, have a delayed response to all incoming signals, and will not respond to subsequent signals until the first has taken effect. For instance, if you pull a lever attached to a floodgate on then off in rapid succession, the floodgate will only respond to the first signal, independent of the position the lever rests in eventually.

==On/Off states==
Objects that can be controlled by levers include:

===== Multiple Uses =====

* [[Bridge]] – Bridges have a delay of 100 steps when the lever is pulled.
** '''On:''' Turns the bridge into either a raised drawbridge, or a retracted bridge, depending on which option was chosen when the the bridge was constructed.
** '''Off:''' Returns the bridge to normal.

* [[Door]] – Note that once you connect a door, it is either completely open or locked. There is no "closed, but can be opened by a dwarf" state anymore.
** '''On:''' Opens the door.
** '''Off:''' Closes the door.

* [[Floodgate]] – After the lever is installed, it works exactly like a door. Floodgates, however, have a 100 tick delay. Therefore, it is more logical to use doors for narrow passageways, at least until doors aren't usable for holding back water.
** '''On:''' Opens the floodgate.
** '''Off:''' Closes the floodgate.

* [[Floor hatch|Hatch]] – When open it just disappears and allows water through. Note that, like doors, once you connect a hatch, it is either completely open or locked.
** '''On:''' Opens the hatch.
** '''Off:''' Closes the hatch.

* [[Grate]] – When it is open, it just disappears. Water goes through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the grate.
** '''Off:''' Closes the grate.

* [[Bars]] – When it is open, it just disappears. Water goes through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the bars.
** '''Off:''' Closes the bars.

* [[Trap|Upright Spear/Spikes]]
** '''On:''' Retracts spears/spikes.
** '''Off:''' Extends spears/spikes.

* [[Gear assembly]] – When it is disengaged, no power goes through it and anything that is being kept up by its presence (like a [[windmill]] right on top of it) falls down.
** '''On:''' Toggles gear state.
** '''Off:''' Toggles gear state.

===== One-Shot =====

These items, when activated, deconstruct, and/or cannot be triggered again until re-linked.

* [[Cage]] – Deconstructs the cage and releases all of its contents. The cage and its attached mechanism will be left on the floor nearby; you recover the [[mechanism]] used on the cage but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.

* [[Restraint]] – Deconstructs the [[Restraint|chain/rope]] and releases whatever creature it held. The restraint's mechanism will be left on the floor nearby, and the restraint itself will remain attached to the creature's neck; again, you recover the [[mechanism]] used on the restraint but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.
* [[Support]] – Deconstructs the support, ideally without a dwarf next to it. Most commonly used to cause controlled [[cave-in]]s.

==Control Room==
Some player prefer to create a "control room" and lock a dwarf in when they expect to need quick response to their levers, to avoid long delays. A control room is an area where all key levers are located. It often has doors/hatches on all entrances, so a dwarf (or more than one) can be locked inside to guarantee that one nearby dwarf will be idle who can pull a lever at a moment's notice, rather than wait for the first idle dwarf to respond, who might be far across the map. This can be critical with some of the more complex [[Trap design|trap designs]]. For longer sieges, a small personal stockpile of booze and food is critical, or an "airlock" that can be (re)stocked for prolonged situations.

Some control rooms have all doors linked to a single lever, which is the first one pulled - this seals in the first volunteer to respond, although {{k|A}}ctivating a specific recruit and stationing them and then manually locking them in the control room is sometimes faster. Double doors, one set manual, and one set linked, allow for manual sealing of the room in either manner. (It's advised to have a backup lever somewhere to open the linked doors in case of accidents.)

Advanced players do not trust doors alone to protect their control room, as some fortress invaders are [[building destroyer]]s, and can deconstruct any door or drawbridge they come across.

Because control rooms often contain levers linked to most every important system in the fortress, it's critical to guard it against troublemakers like [[gremlin]]s and [[tantrum]]ing dwarves. Having wardogs or other attack animals chained at all entrances is a good start, and military stationed nearby is popular as well.

Because of the crowded nature of a control room, it's particularly important to [[label]] your levers, and/or organize them for positive identification as to function. Returning to a game after a week and not remembering which "red" lever releases the magma or shuts the main gate is too much [[fun]] for some players.

==Labeling==
There is no way to determine what levers operate what objects except by pulling them and seeing what happens. Because of this, it can be critical to, somehow, keep track of what lever does what and where (''especially'' in a control room!). [[Note|Label]]ing each individual lever is (possibly) the most foolproof. Some players (additionally) use architecture or color coding to help label their levers, either placing them near the objects they activate, or in small bays organized in groups (even within a control room), and/or making the mechanism (and linked objects) out of a [[The Non-Dwarf's Guide to Rock|particular colored]] stone, or likewise coloring the nearby wall or floor, or even constructing a letter or symbol in a floor mosaic - whatever works, so long as it ''does'' work.

== Computing ==

Elaborate combinations of levers (or pressure plates) and other objects can be used to create mechanical systems that can perform various forms of [[computing]].

{{Buildings}}
[[Category:Buildings]][[Category:Physics]]

User:Adeptable

2009-09-06T17:34:40Z

Adeptable: Created page with 'My website: http://adeptable.org'

My website:

http://adeptable.org

40d Talk:Lever

2009-09-06T17:34:01Z

Adeptable:

== floodgates vs. doors misinformation? ==
"''Therefore, it is more logical to use doors, at least until doors aren't usable for holding back water.''"

I'm fairly certain that doors can't be closed while flooded. They work as described for opening via lever, but cannot close when blocked by water or creatures.
Granted, the last time i've levered doors was back in 2d. Please verify or change the wording? --[[User:Vaevictus|Vaevictus]] 15:49, 2 June 2008 (EDT)

:In the current version{{version|0.27.176.38c}} doors can close if water currently occupies the same square. I believe elsewhere the wiki states this destroys the water, but I have not verified if the water is destroyed. --[[User:Quartic|quartic]] 16:18, 2 June 2008 (EDT)
::Does it matter how much water? -- [[User:Vaevictus|Vaevictus]] 13:35, 3 June 2008 (EDT)
:::I have verified this with water of depth 1 and 7, but not values in between.--[[User:Quartic|quartic]] 13:38, 3 June 2008 (EDT)

Todo: Check whether two levers connected to the same door operate it in the same way the older versions did - that is, pulling each lever once would open the door, then do nothing as the second lever is pulled. -- [[User:Zaratustra|Zaratustra]] 19:23, 7 November 2007 (EST)

I'm using vertical bars as portcullis for my keep, and they attach to levers. Perhaps a comment that bars and grates operate identically in this version, specifically with respect to levers? -Gotthard

Doesn't the delay come from the floodgate grinding to close the water/magma channel/tunnel compared to a door slamming shut right away? --[[User:Karpatius|Karp]] 08:51, 31 October 2008 (EDT)
:That is what it is meant to simulate. Like people mentioned above, though, Toady's said that doors shouldn't work as well as floodgates, so in some later version your doors will probably leak. --[[User:ThunderClaw|ThunderClaw]] 10:09, 31 October 2008 (EDT)

== controlling at a distance ==

Does the lever need to be adjacent to the item it is controlling?

I want to put a floodgate at the end of a channel... [[User:GarrieIrons|GarrieIrons]] 02:52, 23 January 2008 (EST)
:No, it can be anywhere.--[[User:Dorten|Dorten]] 02:57, 23 January 2008 (EST)

so, analog to the support-cave-in-trap how about building a nice water basin, say 4x4 for a start and covering it with grates, all connected to a lever - do grates have to be attached to a wall or floor on one side? I will try *broad grin* --[[User:Koltom|Koltom]] 21:45, 22 February 2008 (EST)

:Grates must be attached to a wall on one side, although you can put grates next to only grates and the dwarves will build them. Followed by their collapse. Like walls off bridges.--[[User:Draco18s|Draco18s]] 18:31, 2 March 2008 (EST)

:Try building supports under them. SL's hand of armok uses supports under hatches in a similar way. [[User:VengefulDonut|VengefulDonut]] 23:37, 2 March 2008 (EST)

::Yeah, its not working like i wanted it too. The support thing will probably work. Or I will just leave a few walls in the basin..will try that later, busy right now. *watches goblin fly away in high arc* --[[User:Koltom|Koltom]] 19:52, 3 March 2008 (EST)

Regarding remote activation/control: I just spent 10 minutes berating my dwarves for completely ignoring two Pull Lever commands while vile forces of darkness approached, only to find that once I removed the Dwarves Stay Indoors restriction, they happily stepped up to the, uh, lever. The bridges are outside, the levers are on the level below. Has anyone else experienced this? [[User:Holyfool|Holyfool]] 17:49, 22 March 2008 (EST)

:Was the lever and/or any part of the path to the lever marked as "outside"? Use {{k|k}} to check. --[[User:Savok|Savok]] 10:25, 23 March 2008 (EDT)

::I checked and one of the levers was indeed marked "outside". In fact, there are several squares on my first underground level that are marked "outside". Is that because they are in the general area of the stairway leading outside? Thank you for the info. --[[User:Holyfool|Holyfool]] 18:42, 29 March 2008 (EDT)

:::When I quit reading all new forum messages and stayed at the wiki, I thought this would stop. [[Outside|Read The Wiki]]. Really. Read it. No, really, click on that link. --[[User:Savok|Savok]] 19:57, 29 March 2008 (EDT)

== Megabeasts ==

I have noticed that a bridge that a hydra is standing on cannot be retracted {{version|0.27.176.38c}}. Has anyone else had similar experiences? [[User:VengefulDonut|VengefulDonut]] 00:15, 13 March 2008 (EDT)

:Titans cause the same problem. I conjecture that bridged can't be retracted while megabeasts are standing on them. [[User:VengefulDonut|VengefulDonut]] 02:08, 13 March 2008 (EDT)

:Also elephants, it seems. Possibly creature size. [[User:VengefulDonut|VengefulDonut]] 13:18, 13 March 2008 (EDT)

:Dragons cause the same problem. Are megabeasts supposed to all show up at once like this? [[User:VengefulDonut|VengefulDonut]] 21:43, 13 March 2008 (EDT)

:: "All at once like this," you say? Was their a [[fun|party]] on your bridgeworks?
:: And, yeah, megabeasts kill bridge operation, even "benign" acts like retracting with them on it. It must have something to do with their BUILDINGDESTROYER tag. --[[User:FJH|FJH]] 02:58, 6 April 2009 (UTC)

== Proposed addition: Mechanism sequence ==

Given the problems that arise when using non magma-safe materials for mechanisms on floodgates, it is quite handy to know which mechanisms go where at the link selection (When for example you're really low on bauxite). 
From my experimentation with floodgate-lever, the first mechanism selected goes at the gate and the second one at the lever. I still haven't activated the contraption, but I'm assuming it's going to be ok. 
I'm also assuming the same is usefull for grates and bars. --[[User:Nonickch]], unsigned

:There is some lower-down text that tells you which mechanism goes in where. --[[User:Savok|Savok]] 08:30, 15 June 2008 (EDT)

== Finding Links ==

Is it possible to determine what a lever is linked to without pulling it and checking to see what happens? -[[User:Fuzzy|Fuzzy]] 00:43, 6 September 2008 (EDT)
:AFAIK the only way is to attempt to link the lever to a built object and notice which one if any is not available.
:eg if you have two bridges but only one is available to be linked to, it is because you are already linked to the other one.
:This would be a really good feature if it was implemented.
:[[User:GarrieIrons|GarrieIrons]] 09:55, 6 September 2008 (EDT)

:I guess this is one good use for the new note-feature: Just use the same note for lever and target. --[[User:Doub|Doub]] 10:17, 6 September 2008 (EDT)

:Right now your best way to remember what lever does what is to build a reference behind the lever as a reminder: a one-tile bridge behind the "front door/bridge" lever, a support behind the "collapse the mountain" lever and so forth... or write down what does what on paper. Even naming levers would be useful but for now you need the "references." -[[User:Karpatius|Karp]] 06:10, 19 December 2008 (EST)

== Max number of links? ==

''Is there a limit to the amount of objects that can be linked to a lever?''--[[User:Thendash|Thendash]] 22:56, 19 September 2008 (EDT)

== Speeding the job of linking ==

Is it just me or does it not only take forever to finish the job of linking the lever to something, but also the dwarves treat it as extremely low priority? I've sometimes had to had an entire year for one of them to deign to hook it up. Incidentally, it is the Mechanics job that they use for that, right? -[[User:Fuzzy|Fuzzy]] 15:48, 27 September 2008 (EDT)

: I haven't noticed anything about the priority of the job, but yes, it take hella long to finish it. Some big linking job (eg. linking a large bridge to a remote lever) are virtually impossible to complete without an experienced mecanic... dwarves don't manage to end the job before feeling the urge to eat or drink or something, and all their work is lost when they return, ending in an infinite loop. [[User:Timst|Timst]] 19:47, 27 September 2008 (EDT)

: Unless it's changed in the year since I've played, the mechanic must move the mechanisms to the lever and the "something", then spend time working on both the lever and the "something", all without being interrupted. Consider a 1-square stockpile next to both the lever and the something and choosing those unique mechanisms when you assign the linkage job. -- [[User:Qwip|Qwip]] 16:42, 15 October 2008 (EDT)

:: The catch, so far, is figuring out the "unique" mechanisms in the list. Short of making sure that that stockpile is the only one that carries Schist Mechanisms or something similar... Unlike the other "pick an item" lists, you can't specify a sort and there's nothing zooming you to the item that you will use. On a mildly unrelated note, I realized that part of the reason for my delay was that I was building large amounts of stone traps, so the nearest mechanism that was not already tied up in a trap building job was quote some distance away. I had this problem with the nearby stockpile as well, as it was also fairly close to the traps. It would be nice to even get a distance count on the mechanisms. -[[User:Fuzzy|Fuzzy]] 11:48, 16 October 2008 (EDT)

:::When you choose the mechanism for the lever or trap, it does tell you its distance.--[[User:Maximus|Maximus]] 12:33, 16 October 2008 (EDT)

:::: Addendum to Maximus's comment: When selecting the material to be used, you can e{{k|x}}pand the list of materials, and then select a particular item. Therefore, you can build a single-tile stockpile, then customize it (using {{k|q}} then {{k|s}}settings) to only allow a certain quality mechanism. Link the lever after these stockpiles have been filled. [[User:RomeoFalling|RomeoFalling]] 16:21, 16 October 2008 (EDT)

== Inverting a Lever ==

I think I found a way to automatically invert the signal of a lever, say if you wanted one lever to open one door and close another. It involves a bridge and water, so it would not be instant. I haven't tested it yet. Anyone know if it would work?
<pre>Side view: (Sorry, I realize this isn't the standard tileset, but my text editor doesn't have them all.)
#####
#_~@W
##D##

W - Water source (Under at least 7/7 pressure)
D - Water drain
_ - Pressure plate, set to activate under water of depth 4-7
@ - Hinge of a raisable bridge, connected to the main lever (offscreen)
~ - Bridge over channel
# - Solid rock</pre>
When the main lever is OFF, the bridge is down. It allows water to flow past its hinge, and it covers the drain. Water fills the room, triggering the plate, which sends an ON signal. 
When the main lever is ON, the bridge raises. The hinge blocks water from flowing in, and the uncovered drain empties the room. The plate detriggers, sending OFF. 
WARNING: The drain must not fill! If it does, you wont be able to get into the room to connect more mechanisms to the plate.
Option: If your water source is infinite, make your drain a hallway, at least 3 long, with a raising bridge that comes down from the far end. When the main lever is activated, the hallway floods. Shortly afterwards, the plate detriggers. After a short delay, the bridge slams down, destroying the water. 
--17:52, 1 October 2008 (EDT)

: Isn't it simpler to build two levers? Especially considering the pressure plate takes as many mechanisms? I don't really understand what you are trying to accomplish here.
:--[[User:MagicGuigz|MagicGuigz]] 17:34, 15 October 2008 (EDT)

::If you want a single action to do some "on" actions and some "off" actions - e.g. if from a stylistic point of view you want to have a single "activate outer defenses" lever that raises bridges over moats and puts down bridges blocking catapults.
::--[[User:Random832|Random832]] 19:35, 15 October 2008 (EDT)

::: It's more than stylistic. My designs are complex systems, created on the assumption that only certain combinations of states are possible - that when ''this'' bridge is down, ''that'' bridge is always up, and that when ''this'' floodgate is open, ''that'' door is always closed. If I allow things to enter a condition I hadn't planned for - either because I forgot to throw both leavers, or the dwarf died between them, or whatever - there is literally no telling what would happen. It could drop civilians into a line of fire, or flood the fortress, or expose the marksdwarves to the enemy without also releasing their infantry guards.
:::--[[User:Macdjord|Macdjord]] 16:08, 16 October 2008 (EDT)

:I'd say you should consult the [[Computing]] and [[Mechanical Logic]] pages then. Should find all the components you need there.
:--[[User:Bilkinson|Bilkinson]] 16:13, 16 October 2008 (EDT)

::Doesn't help. That's all about power transfer - gears, axels, waterwheels... It only uses levers for input, not output - I could connect my controll leaver to a not-gate like [[Mechanical_Logic#NOT_or_BUFFER|this one]], but how do i connect ''that'' to a bridge?
::--[[User:Macdjord|Macdjord]] 17:17, 16 October 2008 (EDT)

:::Connect that power to a screw pump, that pours water onto a pressure plate. There's an example of such a device on the mechanics page. Take a look as Water/Fluid logic as well (Linked to on the mechanical page) for some other pump-based devices.
:::--[[User:Bilkinson|Bilkinson]] 06:56, 17 October 2008 (EDT)

:::It's... ''workable'', I suppose. It's much more complex than the bridge system. It might be faster responding, depending on the speed at which a pump works, since there is no 100 step delay like a bridge. It would take a lot more room and mechanisms, not to mention a seperate power source for each one. Remember, each leaver you invert need its own, independent setup.
::::--[[User:Macdjord|Macdjord]] 13:09, 17 October 2008 (EDT)

:::: Check out this page, it might help.. www.dwarffortresswiki.net/index.php/User:SL/Logic_Gates.
::::[[User:Martinuzz|Martinuzz]] 8:54, 28 October 2008 (EDT)

: So the goal here is to have water on a pressure plate when a lever is set to ON. Don't hatch covers respond quicker than bridges?

: Gee, this sucks. I thought things just toggled whenever you flipped the lever. That's how it should be IMHO. [[User:Gairabad|Gairabad]] 20:31, 13 November 2008 (EST)

<pre>
Side view:

####
#^HW
##D#

^ = Pressure Plate
W - Water Inlet
D - Drain
H - Hatch Cover
# - Solid rock
</pre>
:Main lever linked to Hatch Cover (H). When the lever is OFF, the hatch is closed and the Pressure Plate (^) chamber fills. When the lever is ON, the Hatch Cover (H) disappears and water drains away before reaching the pressure plate ledge.
:[[User:Wangcommander|Wangcommander]] 01:27, 12 November 2008 (EST)

:: But since you're not actually blocking off the water, you are dependent on the fickleness of the water pressure simulation. Sure, the room would never fill with an open hatch between the water source and the hatch, but after the first use it ''starts off'' filled. Are you certain it will drain? If the water comes in from the source as fast as it goes out the drain, will it not stay full? That's the advantage of using the bridge - it is the only piece of equipment that blocks water in the ON position.
:: A hybrid design might be useful, using a bridge to block the input bu a hatch to control the output. When you switch it, the hatch instantly starts draining the water, then the bridge seals the inlet 100 ticks later to guarantee a complete drain.
:: --[[User:Macdjord|Macdjord]] 16:04, 12 November 2008 (EST)

I might be misunderstanding the goal of this (and, for the record, I do think it's really cool), but wouldn't hooking up the lever to the thing you want non-inverted, then flipping the switch, and then hooking it up to the inverted thing accomplish the same thing? That way you have two things hooked up to the lever that are in opposite states of each other..... [[User:Zardus|Zardus]] 05:09, 26 February 2009 (EST)
:A 'Pull the lever' task is not a logical toggle. It toggles the lever, and then activates the lever to signal its current state to its linkages... That is, if the lever is in the 'open' position, pulling it flips it to 'closed' and then sends 'closed' to all its linked buildings. Anything which is, for whatever reason, currently in the 'closed' state will simply remain closed. The case you describe is such a situation. It can also arise where a lever is pulled twice in less time than it takes for the first signal to produce its effect. That is: A dwarf pulls a lever linked to a bridge. The dwarf takes 2 steps away, pauses to decide what to do, and notices that there's a pull the lever task on a lever 2 steps away. The dwarf returns to pull the lever again. The bridge has not yet raised when the second signal is sent... A little bit later, the bridge will raise, but unless the lever is pulled again, to get it into the 'raise' state, and then a fourth time to get it to the 'lower' state, the bridge will not lower.--[[User:Wattj|wattj]] 11:03, 26 February 2009 (EST)
Something like this? [[http://dwarf.lendemaindeveille.com/images/4/48/LeverInvert.gif]] --[[Grek]]

== how to disconnect levers? ==

Is there a way to disconnect a lever from an object without destroying the lever and rebuilding it? --[[User:Shaver|Shaver]] 12:53, 2 January 2009 (EST)
:You can't, to my knowledge. Mechanisms in a lever and the connections stay in place until the lever is deconstructed. I use a lever for cage traps in an arena, and after every 'round' I need to rebuild it to get back the mechanisms I used. --[[User:Eddie|Eddie]] 14:17, 2 January 2009 (EST)

== See what's connected to a lever? ==

Is there a way to see what's connected to a lever? I've lost track of which lever does what, and I'd prefer to not randomly set off my traps trying each one out. --[[User:Katt|Katt]] 00:15, 3 March 2009 (EST)

No. This is why its a good idea to keep levers proximal to objects they connect to. I also try to color code levers to the object and gears used for the connection. --[[User:Squirrelloid|Squirrelloid]] 01:36, 3 March 2009 (EST)

You can also use the Notes thing to label them. --[[User:LegacyCWAL|LegacyCWAL]] 17:15, 3 March 2009 (EST)

Mystery levers have historically been a great source of [[fun]]. Especially in bloodline games. --[[User:Jellyfishgreen|Jellyfishgreen]] 10:16, 4 June 2009 (UTC)

I've just removed the text:
<blockquote>
A lever can be linked more than once to the same object - this has no effect except to consume more pairs of mechanisms.
</blockquote>

because I don't experience this in 0.28.181.40d15

--[[User:Adeptable|Adeptable]] 17:34, 6 September 2009 (UTC)

40d:Lever

2009-09-06T17:15:29Z

Adeptable: /* Linking */ rm "A lever can be linked more than once to the same object - this has no effect except to consume more pairs of mechanisms."

A '''lever''' is a [[mechanism]] that has been constructed on a floor tile. Once in place, it can be linked to one or more other devices such as [[door]]s, [[bridge]]s or [[support]]s, permitting you to remotely control these other devices through the lever's {{k|q}} menu.

Levers do not block any movement. Levers are counted as furniture for [[created wealth]] of a fortress.

[[Pressure plate]]s are like levers, but are activated automatically by [[creatures]] stepping on it, or by fluids reaching a certain (player-selected) depth.

Either a '''lever''' or a [[pressure plate]], once linked to one or more devices ([[door]]s, [[trap]]s, or whatever), can act as a '''trigger''', an activation mechanism for that secondary system. The two are activated differently, but the connected system is activated just the same. One system can have more than one trigger linked to it, and one trigger can be linked to more than one system.

==Placing a lever==
If you have a spare mechanism, you can designate the new lever job via the "{{k|b}}uild {{k|T}}rap {{k|l}}ever" keys, and can use {{k|x}} to choose which specific mechanism to use. Mechanism [[quality]] has no known effect on the performance of the lever. Low-quality mechanisms work fine, but since they are counted as furniture, high quality mechanisms give more [[created wealth]].

==Linking==

Once a mechanism has been placed as a lever, it then requires a pair of [[mechanisms]] to link that lever to any object, regardless of distance or size, and [[quality]] of the mechanism makes no reported difference. This is done by giving the lever the appropriate job order via {{k|q}}(similar to any workshop), selecting what sort of object you want the lever linked to*, and then using the {{k|-}} and {{k|+}} keys to scroll thru the available examples of those and selecting the one you want. The list is chronological, with the last object finished listed last, and the map will re-center on the exact object as you scroll.

:''(* [[bridge]], [[cage]], [[chain]], [[door]], [[floodgate]], [[hatch]], [[wall grate]], [[floor grate]], [[vertical bars]], [[floor bars]], [[support]], [[spike]], or [[gear assembly]].)

By default you can choose the specific mechanisms you wish to use, from a list of all you have created (and are not forbidden or isolated by [[path]]) - your first selection will be attached to the item/barrier in question (the door, floodgate, cage, whatever), and the second selection will be linked at the lever end (the order is important when dealing with [[magma]]).

A lever can be connected to any number of objects at the same time, but, as each linking is a [[job]] designated at that lever, only one linking job will be tasked at any one time - after that job is finished, the next will begin. (That is, if you want one lever connected to 101 different doors, hatches, cages, bridges and supports, you can do that, but those jobs will not occur ''simultaneously''.) Up to 10 linking jobs can be queued up at any one time on one lever, the same as with jobs at any workshop.

Once linked, a trigger must be deconstructed to de-link it to a system*; this also unlinks all other connected systems to that trigger, but has no effect on other triggers linked to the same system(s).

:''(* Or if the other end is deconstructed, the door, hatch, column, bridge or whatever, that un-links the trigger as well, but any other system remains linked.)''

==Activating levers==
A lever is activated (or "pulled") through its {{k|q}} menu with via the "{{k|a}}dd new task {{k|P}}ull" keys, which establishes a new [[job]] that then needs to be filled. An idle dwarf will then come to pull the lever - no labor need be designated for this task, so ''any'' dwarf might volunteer, and from ''anywhere'' on the map that has a [[path]] to that lever at the time.

[[Tantrum]]ing dwarves have also been reported to pull levers at random, leading to all kinds of [[fun]].

Note that once the actual ''lever'' is pulled, any attached objects may take more time to respond - see below.

==On/Off vs Open/Close==
Levers normally have an "on" and an "off" state, seen as whether the small tag at the top of the lever is to the left ("off" state) or the right ("on" state). Upon being pulled, the state of the lever changes, and everything they're connected to updates to the ''corresponding'' state of that lever, and does not just ''change'' states ("toggle"). This becomes important if you have several levers attached to the same device, or one trigger attached to several systems.
:Example: 2 levers (both in "off" position) are connected to a drawbridge. After pulling the first lever, the bridge will lift. Pulling the second lever tells the bridge to "open", which it already has done - no visible effect. When it is pulled a second time it will let the bridge down. This in turn requires the ''first'' lever (still in "open/lift" position) to be pulled twice to trigger a change (lift again), and so on.

"On" and "off" state is fixed and dependent on the lever, not the object that lever is linked to:

* "dash to the right" ( '''ó''' ) is '''on'''
* "dash to the left" ( '''ò''' ) is '''off'''

Note, however, that gear assemblies are ''the sole exception'' to this: Instead of On/Off triggers, they indeed '''do''' toggle.

Several devices, such as [[floodgate]]s and [[bridge]]s, have a delayed response to all incoming signals, and will not respond to subsequent signals until the first has taken effect. For instance, if you pull a lever attached to a floodgate on then off in rapid succession, the floodgate will only respond to the first signal, independent of the position the lever rests in eventually.

Once a device is connected to a lever, it can only be unlinked by deconstructing the lever and reconstructing it. This will obviously require you to relink any other devices that you want to still be connected to this lever.

==On/Off states==
Objects that can be controlled by levers include:

===== Multiple Uses =====

* [[Bridge]] – Bridges have a delay of 100 steps when the lever is pulled.
** '''On:''' Turns the bridge into either a raised drawbridge, or a retracted bridge, depending on which option was chosen when the the bridge was constructed.
** '''Off:''' Returns the bridge to normal.

* [[Door]] – Note that once you connect a door, it is either completely open or locked. There is no "closed, but can be opened by a dwarf" state anymore.
** '''On:''' Opens the door.
** '''Off:''' Closes the door.

* [[Floodgate]] – After the lever is installed, it works exactly like a door. Floodgates, however, have a 100 tick delay. Therefore, it is more logical to use doors for narrow passageways, at least until doors aren't usable for holding back water.
** '''On:''' Opens the floodgate.
** '''Off:''' Closes the floodgate.

* [[Floor hatch|Hatch]] – When open it just disappears and allows water through. Note that, like doors, once you connect a hatch, it is either completely open or locked.
** '''On:''' Opens the hatch.
** '''Off:''' Closes the hatch.

* [[Grate]] – When it is open, it just disappears. Water goes through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the grate.
** '''Off:''' Closes the grate.

* [[Bars]] – When it is open, it just disappears. Water goes through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the bars.
** '''Off:''' Closes the bars.

* [[Trap|Upright Spear/Spikes]]
** '''On:''' Retracts spears/spikes.
** '''Off:''' Extends spears/spikes.

* [[Gear assembly]] – When it is disengaged, no power goes through it and anything that is being kept up by its presence (like a [[windmill]] right on top of it) falls down.
** '''On:''' Toggles gear state.
** '''Off:''' Toggles gear state.

===== One-Shot =====

These items, when activated, deconstruct, and/or cannot be triggered again until re-linked.

* [[Cage]] – Deconstructs the cage and releases all of its contents. The cage and its attached mechanism will be left on the floor nearby; you recover the [[mechanism]] used on the cage but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.

* [[Restraint]] – Deconstructs the [[Restraint|chain/rope]] and releases whatever creature it held. The restraint's mechanism will be left on the floor nearby, and the restraint itself will remain attached to the creature's neck; again, you recover the [[mechanism]] used on the restraint but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.
* [[Support]] – Deconstructs the support, ideally without a dwarf next to it. Most commonly used to cause controlled [[cave-in]]s.

==Control Room==
Some player prefer to create a "control room" and lock a dwarf in when they expect to need quick response to their levers, to avoid long delays. A control room is an area where all key levers are located. It often has doors/hatches on all entrances, so a dwarf (or more than one) can be locked inside to guarantee that one nearby dwarf will be idle who can pull a lever at a moment's notice, rather than wait for the first idle dwarf to respond, who might be far across the map. This can be critical with some of the more complex [[Trap design|trap designs]]. For longer sieges, a small personal stockpile of booze and food is critical, or an "airlock" that can be (re)stocked for prolonged situations.

Some control rooms have all doors linked to a single lever, which is the first one pulled - this seals in the first volunteer to respond, although {{k|A}}ctivating a specific recruit and stationing them and then manually locking them in the control room is sometimes faster. Double doors, one set manual, and one set linked, allow for manual sealing of the room in either manner. (It's advised to have a backup lever somewhere to open the linked doors in case of accidents.)

Advanced players do not trust doors alone to protect their control room, as some fortress invaders are [[building destroyer]]s, and can deconstruct any door or drawbridge they come across.

Because control rooms often contain levers linked to most every important system in the fortress, it's critical to guard it against troublemakers like [[gremlin]]s and [[tantrum]]ing dwarves. Having wardogs or other attack animals chained at all entrances is a good start, and military stationed nearby is popular as well.

Because of the crowded nature of a control room, it's particularly important to [[label]] your levers, and/or organize them for positive identification as to function. Returning to a game after a week and not remembering which "red" lever releases the magma or shuts the main gate is too much [[fun]] for some players.

==Labeling==
There is no way to determine what levers operate what objects except by pulling them and seeing what happens. Because of this, it can be critical to, somehow, keep track of what lever does what and where (''especially'' in a control room!). [[Note|Label]]ing each individual lever is (possibly) the most foolproof. Some players (additionally) use architecture or color coding to help label their levers, either placing them near the objects they activate, or in small bays organized in groups (even within a control room), and/or making the mechanism (and linked objects) out of a [[The Non-Dwarf's Guide to Rock|particular colored]] stone, or likewise coloring the nearby wall or floor, or even constructing a letter or symbol in a floor mosaic - whatever works, so long as it ''does'' work.

== Computing ==

Elaborate combinations of levers (or pressure plates) and other objects can be used to create mechanical systems that can perform various forms of [[computing]].

{{Buildings}}
[[Category:Buildings]][[Category:Physics]]

40d:Lever

2009-09-06T17:14:32Z

Adeptable: /* Linking */ gr

A '''lever''' is a [[mechanism]] that has been constructed on a floor tile. Once in place, it can be linked to one or more other devices such as [[door]]s, [[bridge]]s or [[support]]s, permitting you to remotely control these other devices through the lever's {{k|q}} menu.

Levers do not block any movement. Levers are counted as furniture for [[created wealth]] of a fortress.

[[Pressure plate]]s are like levers, but are activated automatically by [[creatures]] stepping on it, or by fluids reaching a certain (player-selected) depth.

Either a '''lever''' or a [[pressure plate]], once linked to one or more devices ([[door]]s, [[trap]]s, or whatever), can act as a '''trigger''', an activation mechanism for that secondary system. The two are activated differently, but the connected system is activated just the same. One system can have more than one trigger linked to it, and one trigger can be linked to more than one system.

==Placing a lever==
If you have a spare mechanism, you can designate the new lever job via the "{{k|b}}uild {{k|T}}rap {{k|l}}ever" keys, and can use {{k|x}} to choose which specific mechanism to use. Mechanism [[quality]] has no known effect on the performance of the lever. Low-quality mechanisms work fine, but since they are counted as furniture, high quality mechanisms give more [[created wealth]].

==Linking==

Once a mechanism has been placed as a lever, it then requires a pair of [[mechanisms]] to link that lever to any object, regardless of distance or size, and [[quality]] of the mechanism makes no reported difference. This is done by giving the lever the appropriate job order via {{k|q}}(similar to any workshop), selecting what sort of object you want the lever linked to*, and then using the {{k|-}} and {{k|+}} keys to scroll thru the available examples of those and selecting the one you want. The list is chronological, with the last object finished listed last, and the map will re-center on the exact object as you scroll.

:''(* [[bridge]], [[cage]], [[chain]], [[door]], [[floodgate]], [[hatch]], [[wall grate]], [[floor grate]], [[vertical bars]], [[floor bars]], [[support]], [[spike]], or [[gear assembly]].)

By default you can choose the specific mechanisms you wish to use, from a list of all you have created (and are not forbidden or isolated by [[path]]) - your first selection will be attached to the item/barrier in question (the door, floodgate, cage, whatever), and the second selection will be linked at the lever end (the order is important when dealing with [[magma]]).

A lever can be connected to any number of objects at the same time, but, as each linking is a [[job]] designated at that lever, only one linking job will be tasked at any one time - after that job is finished, the next will begin. (That is, if you want one lever connected to 101 different doors, hatches, cages, bridges and supports, you can do that, but those jobs will not occur ''simultaneously''.) Up to 10 linking jobs can be queued up at any one time on one lever, the same as with jobs at any workshop. A lever can be linked more than once to the same object - this has no effect except to consume more pairs of mechanisms.

Once linked, a trigger must be deconstructed to de-link it to a system*; this also unlinks all other connected systems to that trigger, but has no effect on other triggers linked to the same system(s).

:''(* Or if the other end is deconstructed, the door, hatch, column, bridge or whatever, that un-links the trigger as well, but any other system remains linked.)''

==Activating levers==
A lever is activated (or "pulled") through its {{k|q}} menu with via the "{{k|a}}dd new task {{k|P}}ull" keys, which establishes a new [[job]] that then needs to be filled. An idle dwarf will then come to pull the lever - no labor need be designated for this task, so ''any'' dwarf might volunteer, and from ''anywhere'' on the map that has a [[path]] to that lever at the time.

[[Tantrum]]ing dwarves have also been reported to pull levers at random, leading to all kinds of [[fun]].

Note that once the actual ''lever'' is pulled, any attached objects may take more time to respond - see below.

==On/Off vs Open/Close==
Levers normally have an "on" and an "off" state, seen as whether the small tag at the top of the lever is to the left ("off" state) or the right ("on" state). Upon being pulled, the state of the lever changes, and everything they're connected to updates to the ''corresponding'' state of that lever, and does not just ''change'' states ("toggle"). This becomes important if you have several levers attached to the same device, or one trigger attached to several systems.
:Example: 2 levers (both in "off" position) are connected to a drawbridge. After pulling the first lever, the bridge will lift. Pulling the second lever tells the bridge to "open", which it already has done - no visible effect. When it is pulled a second time it will let the bridge down. This in turn requires the ''first'' lever (still in "open/lift" position) to be pulled twice to trigger a change (lift again), and so on.

"On" and "off" state is fixed and dependent on the lever, not the object that lever is linked to:

* "dash to the right" ( '''ó''' ) is '''on'''
* "dash to the left" ( '''ò''' ) is '''off'''

Note, however, that gear assemblies are ''the sole exception'' to this: Instead of On/Off triggers, they indeed '''do''' toggle.

Several devices, such as [[floodgate]]s and [[bridge]]s, have a delayed response to all incoming signals, and will not respond to subsequent signals until the first has taken effect. For instance, if you pull a lever attached to a floodgate on then off in rapid succession, the floodgate will only respond to the first signal, independent of the position the lever rests in eventually.

Once a device is connected to a lever, it can only be unlinked by deconstructing the lever and reconstructing it. This will obviously require you to relink any other devices that you want to still be connected to this lever.

==On/Off states==
Objects that can be controlled by levers include:

===== Multiple Uses =====

* [[Bridge]] – Bridges have a delay of 100 steps when the lever is pulled.
** '''On:''' Turns the bridge into either a raised drawbridge, or a retracted bridge, depending on which option was chosen when the the bridge was constructed.
** '''Off:''' Returns the bridge to normal.

* [[Door]] – Note that once you connect a door, it is either completely open or locked. There is no "closed, but can be opened by a dwarf" state anymore.
** '''On:''' Opens the door.
** '''Off:''' Closes the door.

* [[Floodgate]] – After the lever is installed, it works exactly like a door. Floodgates, however, have a 100 tick delay. Therefore, it is more logical to use doors for narrow passageways, at least until doors aren't usable for holding back water.
** '''On:''' Opens the floodgate.
** '''Off:''' Closes the floodgate.

* [[Floor hatch|Hatch]] – When open it just disappears and allows water through. Note that, like doors, once you connect a hatch, it is either completely open or locked.
** '''On:''' Opens the hatch.
** '''Off:''' Closes the hatch.

* [[Grate]] – When it is open, it just disappears. Water goes through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the grate.
** '''Off:''' Closes the grate.

* [[Bars]] – When it is open, it just disappears. Water goes through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the bars.
** '''Off:''' Closes the bars.

* [[Trap|Upright Spear/Spikes]]
** '''On:''' Retracts spears/spikes.
** '''Off:''' Extends spears/spikes.

* [[Gear assembly]] – When it is disengaged, no power goes through it and anything that is being kept up by its presence (like a [[windmill]] right on top of it) falls down.
** '''On:''' Toggles gear state.
** '''Off:''' Toggles gear state.

===== One-Shot =====

These items, when activated, deconstruct, and/or cannot be triggered again until re-linked.

* [[Cage]] – Deconstructs the cage and releases all of its contents. The cage and its attached mechanism will be left on the floor nearby; you recover the [[mechanism]] used on the cage but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.

* [[Restraint]] – Deconstructs the [[Restraint|chain/rope]] and releases whatever creature it held. The restraint's mechanism will be left on the floor nearby, and the restraint itself will remain attached to the creature's neck; again, you recover the [[mechanism]] used on the restraint but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.
* [[Support]] – Deconstructs the support, ideally without a dwarf next to it. Most commonly used to cause controlled [[cave-in]]s.

==Control Room==
Some player prefer to create a "control room" and lock a dwarf in when they expect to need quick response to their levers, to avoid long delays. A control room is an area where all key levers are located. It often has doors/hatches on all entrances, so a dwarf (or more than one) can be locked inside to guarantee that one nearby dwarf will be idle who can pull a lever at a moment's notice, rather than wait for the first idle dwarf to respond, who might be far across the map. This can be critical with some of the more complex [[Trap design|trap designs]]. For longer sieges, a small personal stockpile of booze and food is critical, or an "airlock" that can be (re)stocked for prolonged situations.

Some control rooms have all doors linked to a single lever, which is the first one pulled - this seals in the first volunteer to respond, although {{k|A}}ctivating a specific recruit and stationing them and then manually locking them in the control room is sometimes faster. Double doors, one set manual, and one set linked, allow for manual sealing of the room in either manner. (It's advised to have a backup lever somewhere to open the linked doors in case of accidents.)

Advanced players do not trust doors alone to protect their control room, as some fortress invaders are [[building destroyer]]s, and can deconstruct any door or drawbridge they come across.

Because control rooms often contain levers linked to most every important system in the fortress, it's critical to guard it against troublemakers like [[gremlin]]s and [[tantrum]]ing dwarves. Having wardogs or other attack animals chained at all entrances is a good start, and military stationed nearby is popular as well.

Because of the crowded nature of a control room, it's particularly important to [[label]] your levers, and/or organize them for positive identification as to function. Returning to a game after a week and not remembering which "red" lever releases the magma or shuts the main gate is too much [[fun]] for some players.

==Labeling==
There is no way to determine what levers operate what objects except by pulling them and seeing what happens. Because of this, it can be critical to, somehow, keep track of what lever does what and where (''especially'' in a control room!). [[Note|Label]]ing each individual lever is (possibly) the most foolproof. Some players (additionally) use architecture or color coding to help label their levers, either placing them near the objects they activate, or in small bays organized in groups (even within a control room), and/or making the mechanism (and linked objects) out of a [[The Non-Dwarf's Guide to Rock|particular colored]] stone, or likewise coloring the nearby wall or floor, or even constructing a letter or symbol in a floor mosaic - whatever works, so long as it ''does'' work.

== Computing ==

Elaborate combinations of levers (or pressure plates) and other objects can be used to create mechanical systems that can perform various forms of [[computing]].

{{Buildings}}
[[Category:Buildings]][[Category:Physics]]

40d:Lever

2009-09-06T17:12:59Z

Adeptable: /* Linking */ gr

A '''lever''' is a [[mechanism]] that has been constructed on a floor tile. Once in place, it can be linked to one or more other devices such as [[door]]s, [[bridge]]s or [[support]]s, permitting you to remotely control these other devices through the lever's {{k|q}} menu.

Levers do not block any movement. Levers are counted as furniture for [[created wealth]] of a fortress.

[[Pressure plate]]s are like levers, but are activated automatically by [[creatures]] stepping on it, or by fluids reaching a certain (player-selected) depth.

Either a '''lever''' or a [[pressure plate]], once linked to one or more devices ([[door]]s, [[trap]]s, or whatever), can act as a '''trigger''', an activation mechanism for that secondary system. The two are activated differently, but the connected system is activated just the same. One system can have more than one trigger linked to it, and one trigger can be linked to more than one system.

==Placing a lever==
If you have a spare mechanism, you can designate the new lever job via the "{{k|b}}uild {{k|T}}rap {{k|l}}ever" keys, and can use {{k|x}} to choose which specific mechanism to use. Mechanism [[quality]] has no known effect on the performance of the lever. Low-quality mechanisms work fine, but since they are counted as furniture, high quality mechanisms give more [[created wealth]].

==Linking==

Once a mechanism has been placed as a lever, it then requires a pair of [[mechanisms]] to link that lever to any object, regardless of distance or size, and [[quality]] of the mechanism makes no reported difference. This is done by giving the lever the appropriate job order via {{k|q}}(similar to any workshop), selecting what sort of object you want the lever linked to*, and then using the {{k|-}} and {{k|+}} keys to scroll thru the available examples of those and selecting the one you want. The list is chronological, with the last object finished listed last, and the map will re-center on the exact object as you scroll.

:''(* [[bridge]], [[cage]], [[chain]], [[door]], [[floodgate]], [[hatch]], [[wall grate]], [[floor grate]], [[vertical bars]], [[floor bars]], [[support]], [[spike]], or [[gear assembly]].)

By default you can choose the specific mechanisms you wish to use, from a list of all you have created (and are not forbidden or isolated by [[path]]) - your first selection will be attached to the item/barrier in question (the door, floodgate, cage, whatever), and the second selection will be linked at the lever end (the order is important when dealing with [[magma]]).

A lever can be connected to any number of objects at the same time, but, as each linking is a [[job]] designated at that lever, only one linking job will be tasked at any one time - after that job is finished, the next will be begun. (That is, if you want one lever connected to 101 different doors, hatches, cages, bridges and supports, you can do that without problem, but those jobs will not occur ''simultaneously'', only the next after the last is finished.) Up to 10 linking jobs can be queued up at any one time on one lever, the same as with jobs at any workshop. A lever can be linked more than once to the same object - this has no effect except to consume more pairs of mechanisms.

Once linked, a trigger must be deconstructed to de-link it to a system*; this also unlinks all other connected systems to that trigger, but has no effect on other triggers linked to the same system(s).

:''(* Or if the other end is deconstructed, the door, hatch, column, bridge or whatever, that un-links the trigger as well, but any other system remains linked.)''

==Activating levers==
A lever is activated (or "pulled") through its {{k|q}} menu with via the "{{k|a}}dd new task {{k|P}}ull" keys, which establishes a new [[job]] that then needs to be filled. An idle dwarf will then come to pull the lever - no labor need be designated for this task, so ''any'' dwarf might volunteer, and from ''anywhere'' on the map that has a [[path]] to that lever at the time.

[[Tantrum]]ing dwarves have also been reported to pull levers at random, leading to all kinds of [[fun]].

Note that once the actual ''lever'' is pulled, any attached objects may take more time to respond - see below.

==On/Off vs Open/Close==
Levers normally have an "on" and an "off" state, seen as whether the small tag at the top of the lever is to the left ("off" state) or the right ("on" state). Upon being pulled, the state of the lever changes, and everything they're connected to updates to the ''corresponding'' state of that lever, and does not just ''change'' states ("toggle"). This becomes important if you have several levers attached to the same device, or one trigger attached to several systems.
:Example: 2 levers (both in "off" position) are connected to a drawbridge. After pulling the first lever, the bridge will lift. Pulling the second lever tells the bridge to "open", which it already has done - no visible effect. When it is pulled a second time it will let the bridge down. This in turn requires the ''first'' lever (still in "open/lift" position) to be pulled twice to trigger a change (lift again), and so on.

"On" and "off" state is fixed and dependent on the lever, not the object that lever is linked to:

* "dash to the right" ( '''ó''' ) is '''on'''
* "dash to the left" ( '''ò''' ) is '''off'''

Note, however, that gear assemblies are ''the sole exception'' to this: Instead of On/Off triggers, they indeed '''do''' toggle.

Several devices, such as [[floodgate]]s and [[bridge]]s, have a delayed response to all incoming signals, and will not respond to subsequent signals until the first has taken effect. For instance, if you pull a lever attached to a floodgate on then off in rapid succession, the floodgate will only respond to the first signal, independent of the position the lever rests in eventually.

Once a device is connected to a lever, it can only be unlinked by deconstructing the lever and reconstructing it. This will obviously require you to relink any other devices that you want to still be connected to this lever.

==On/Off states==
Objects that can be controlled by levers include:

===== Multiple Uses =====

* [[Bridge]] – Bridges have a delay of 100 steps when the lever is pulled.
** '''On:''' Turns the bridge into either a raised drawbridge, or a retracted bridge, depending on which option was chosen when the the bridge was constructed.
** '''Off:''' Returns the bridge to normal.

* [[Door]] – Note that once you connect a door, it is either completely open or locked. There is no "closed, but can be opened by a dwarf" state anymore.
** '''On:''' Opens the door.
** '''Off:''' Closes the door.

* [[Floodgate]] – After the lever is installed, it works exactly like a door. Floodgates, however, have a 100 tick delay. Therefore, it is more logical to use doors for narrow passageways, at least until doors aren't usable for holding back water.
** '''On:''' Opens the floodgate.
** '''Off:''' Closes the floodgate.

* [[Floor hatch|Hatch]] – When open it just disappears and allows water through. Note that, like doors, once you connect a hatch, it is either completely open or locked.
** '''On:''' Opens the hatch.
** '''Off:''' Closes the hatch.

* [[Grate]] – When it is open, it just disappears. Water goes through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the grate.
** '''Off:''' Closes the grate.

* [[Bars]] – When it is open, it just disappears. Water goes through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the bars.
** '''Off:''' Closes the bars.

* [[Trap|Upright Spear/Spikes]]
** '''On:''' Retracts spears/spikes.
** '''Off:''' Extends spears/spikes.

* [[Gear assembly]] – When it is disengaged, no power goes through it and anything that is being kept up by its presence (like a [[windmill]] right on top of it) falls down.
** '''On:''' Toggles gear state.
** '''Off:''' Toggles gear state.

===== One-Shot =====

These items, when activated, deconstruct, and/or cannot be triggered again until re-linked.

* [[Cage]] – Deconstructs the cage and releases all of its contents. The cage and its attached mechanism will be left on the floor nearby; you recover the [[mechanism]] used on the cage but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.

* [[Restraint]] – Deconstructs the [[Restraint|chain/rope]] and releases whatever creature it held. The restraint's mechanism will be left on the floor nearby, and the restraint itself will remain attached to the creature's neck; again, you recover the [[mechanism]] used on the restraint but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.
* [[Support]] – Deconstructs the support, ideally without a dwarf next to it. Most commonly used to cause controlled [[cave-in]]s.

==Control Room==
Some player prefer to create a "control room" and lock a dwarf in when they expect to need quick response to their levers, to avoid long delays. A control room is an area where all key levers are located. It often has doors/hatches on all entrances, so a dwarf (or more than one) can be locked inside to guarantee that one nearby dwarf will be idle who can pull a lever at a moment's notice, rather than wait for the first idle dwarf to respond, who might be far across the map. This can be critical with some of the more complex [[Trap design|trap designs]]. For longer sieges, a small personal stockpile of booze and food is critical, or an "airlock" that can be (re)stocked for prolonged situations.

Some control rooms have all doors linked to a single lever, which is the first one pulled - this seals in the first volunteer to respond, although {{k|A}}ctivating a specific recruit and stationing them and then manually locking them in the control room is sometimes faster. Double doors, one set manual, and one set linked, allow for manual sealing of the room in either manner. (It's advised to have a backup lever somewhere to open the linked doors in case of accidents.)

Advanced players do not trust doors alone to protect their control room, as some fortress invaders are [[building destroyer]]s, and can deconstruct any door or drawbridge they come across.

Because control rooms often contain levers linked to most every important system in the fortress, it's critical to guard it against troublemakers like [[gremlin]]s and [[tantrum]]ing dwarves. Having wardogs or other attack animals chained at all entrances is a good start, and military stationed nearby is popular as well.

Because of the crowded nature of a control room, it's particularly important to [[label]] your levers, and/or organize them for positive identification as to function. Returning to a game after a week and not remembering which "red" lever releases the magma or shuts the main gate is too much [[fun]] for some players.

==Labeling==
There is no way to determine what levers operate what objects except by pulling them and seeing what happens. Because of this, it can be critical to, somehow, keep track of what lever does what and where (''especially'' in a control room!). [[Note|Label]]ing each individual lever is (possibly) the most foolproof. Some players (additionally) use architecture or color coding to help label their levers, either placing them near the objects they activate, or in small bays organized in groups (even within a control room), and/or making the mechanism (and linked objects) out of a [[The Non-Dwarf's Guide to Rock|particular colored]] stone, or likewise coloring the nearby wall or floor, or even constructing a letter or symbol in a floor mosaic - whatever works, so long as it ''does'' work.

== Computing ==

Elaborate combinations of levers (or pressure plates) and other objects can be used to create mechanical systems that can perform various forms of [[computing]].

{{Buildings}}
[[Category:Buildings]][[Category:Physics]]

40d:Lever

2009-09-06T17:10:27Z

Adeptable: /* Placing a lever */ gr

A '''lever''' is a [[mechanism]] that has been constructed on a floor tile. Once in place, it can be linked to one or more other devices such as [[door]]s, [[bridge]]s or [[support]]s, permitting you to remotely control these other devices through the lever's {{k|q}} menu.

Levers do not block any movement. Levers are counted as furniture for [[created wealth]] of a fortress.

[[Pressure plate]]s are like levers, but are activated automatically by [[creatures]] stepping on it, or by fluids reaching a certain (player-selected) depth.

Either a '''lever''' or a [[pressure plate]], once linked to one or more devices ([[door]]s, [[trap]]s, or whatever), can act as a '''trigger''', an activation mechanism for that secondary system. The two are activated differently, but the connected system is activated just the same. One system can have more than one trigger linked to it, and one trigger can be linked to more than one system.

==Placing a lever==
If you have a spare mechanism, you can designate the new lever job via the "{{k|b}}uild {{k|T}}rap {{k|l}}ever" keys, and can use {{k|x}} to choose which specific mechanism to use. Mechanism [[quality]] has no known effect on the performance of the lever. Low-quality mechanisms work fine, but since they are counted as furniture, high quality mechanisms give more [[created wealth]].

==Linking==

Once a mechanism has been placed as a lever, it then requires a pair of [[mechanisms]] to link that lever to any object, regardless of distance or size, and [[quality]] of the mechanism makes no reported difference. This is done by giving the lever the appropriate job order via {{k|q}}(similar to any workshop), selecting what sort of object you want the lever linked to*, and then using the {{k|-}} and {{k|+}} keys to scroll thru the available examples of those and selecting the one you want. The list is chronological, with the last object finished listed last, and the map will re-center on the exact object as you scroll.

:''(* [[bridge]], [[cage]], [[chain]], [[door]], [[floodgate]], [[hatch]], [[wall grate]], [[floor grate]], [[vertical bars]], [[floor bars]], [[support]], [[spike]], or [[gear assembly]].)

By default you can choose the specific mechanisms you wish to use, from a list of all you have created (and are not forbidden or isolated by [[path]]) - your first selection will be attached to the item/barrier in question (the door, floodgate, cage, whatever), and the second selection will be linked at the lever end. (This is important when dealing with [[magma]].)

A lever can be connected to any number of objects at the same time, but, as each linking is a [[job]] designated at that lever, only one linking job will be tasked at any one time - after that job is finished, the next will be begun. (That is, if you want one lever connected to 101 different doors, hatches, cages, bridges and supports, you can do that without problem, but those jobs will not occur ''simultaneously'', only the next after the last is finished.) Up to 10 linking jobs can be queued up at any one time on one lever, the same as with jobs at any workshop. A lever can be linked more than once to the same object - this has no effect except to consume more pairs of mechanisms.

Once linked, a trigger must be deconstructed to de-link it to a system*; this also unlinks all other connected systems to that trigger, but has no effect on other triggers linked to the same system(s).

:''(* Or if the other end is deconstructed, the door, hatch, column, bridge or whatever, that un-links the trigger as well, but any other system remains linked.)''

==Activating levers==
A lever is activated (or "pulled") through its {{k|q}} menu with via the "{{k|a}}dd new task {{k|P}}ull" keys, which establishes a new [[job]] that then needs to be filled. An idle dwarf will then come to pull the lever - no labor need be designated for this task, so ''any'' dwarf might volunteer, and from ''anywhere'' on the map that has a [[path]] to that lever at the time.

[[Tantrum]]ing dwarves have also been reported to pull levers at random, leading to all kinds of [[fun]].

Note that once the actual ''lever'' is pulled, any attached objects may take more time to respond - see below.

==On/Off vs Open/Close==
Levers normally have an "on" and an "off" state, seen as whether the small tag at the top of the lever is to the left ("off" state) or the right ("on" state). Upon being pulled, the state of the lever changes, and everything they're connected to updates to the ''corresponding'' state of that lever, and does not just ''change'' states ("toggle"). This becomes important if you have several levers attached to the same device, or one trigger attached to several systems.
:Example: 2 levers (both in "off" position) are connected to a drawbridge. After pulling the first lever, the bridge will lift. Pulling the second lever tells the bridge to "open", which it already has done - no visible effect. When it is pulled a second time it will let the bridge down. This in turn requires the ''first'' lever (still in "open/lift" position) to be pulled twice to trigger a change (lift again), and so on.

"On" and "off" state is fixed and dependent on the lever, not the object that lever is linked to:

* "dash to the right" ( '''ó''' ) is '''on'''
* "dash to the left" ( '''ò''' ) is '''off'''

Note, however, that gear assemblies are ''the sole exception'' to this: Instead of On/Off triggers, they indeed '''do''' toggle.

Several devices, such as [[floodgate]]s and [[bridge]]s, have a delayed response to all incoming signals, and will not respond to subsequent signals until the first has taken effect. For instance, if you pull a lever attached to a floodgate on then off in rapid succession, the floodgate will only respond to the first signal, independent of the position the lever rests in eventually.

Once a device is connected to a lever, it can only be unlinked by deconstructing the lever and reconstructing it. This will obviously require you to relink any other devices that you want to still be connected to this lever.

==On/Off states==
Objects that can be controlled by levers include:

===== Multiple Uses =====

* [[Bridge]] – Bridges have a delay of 100 steps when the lever is pulled.
** '''On:''' Turns the bridge into either a raised drawbridge, or a retracted bridge, depending on which option was chosen when the the bridge was constructed.
** '''Off:''' Returns the bridge to normal.

* [[Door]] – Note that once you connect a door, it is either completely open or locked. There is no "closed, but can be opened by a dwarf" state anymore.
** '''On:''' Opens the door.
** '''Off:''' Closes the door.

* [[Floodgate]] – After the lever is installed, it works exactly like a door. Floodgates, however, have a 100 tick delay. Therefore, it is more logical to use doors for narrow passageways, at least until doors aren't usable for holding back water.
** '''On:''' Opens the floodgate.
** '''Off:''' Closes the floodgate.

* [[Floor hatch|Hatch]] – When open it just disappears and allows water through. Note that, like doors, once you connect a hatch, it is either completely open or locked.
** '''On:''' Opens the hatch.
** '''Off:''' Closes the hatch.

* [[Grate]] – When it is open, it just disappears. Water goes through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the grate.
** '''Off:''' Closes the grate.

* [[Bars]] – When it is open, it just disappears. Water goes through it just the same, but it cannot be walked on anymore. Anybody on it will fall.
** '''On:''' Opens the bars.
** '''Off:''' Closes the bars.

* [[Trap|Upright Spear/Spikes]]
** '''On:''' Retracts spears/spikes.
** '''Off:''' Extends spears/spikes.

* [[Gear assembly]] – When it is disengaged, no power goes through it and anything that is being kept up by its presence (like a [[windmill]] right on top of it) falls down.
** '''On:''' Toggles gear state.
** '''Off:''' Toggles gear state.

===== One-Shot =====

These items, when activated, deconstruct, and/or cannot be triggered again until re-linked.

* [[Cage]] – Deconstructs the cage and releases all of its contents. The cage and its attached mechanism will be left on the floor nearby; you recover the [[mechanism]] used on the cage but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.

* [[Restraint]] – Deconstructs the [[Restraint|chain/rope]] and releases whatever creature it held. The restraint's mechanism will be left on the floor nearby, and the restraint itself will remain attached to the creature's neck; again, you recover the [[mechanism]] used on the restraint but you do not recover the mechanism used in the lever. For this you need to deconstruct the lever too.
* [[Support]] – Deconstructs the support, ideally without a dwarf next to it. Most commonly used to cause controlled [[cave-in]]s.

==Control Room==
Some player prefer to create a "control room" and lock a dwarf in when they expect to need quick response to their levers, to avoid long delays. A control room is an area where all key levers are located. It often has doors/hatches on all entrances, so a dwarf (or more than one) can be locked inside to guarantee that one nearby dwarf will be idle who can pull a lever at a moment's notice, rather than wait for the first idle dwarf to respond, who might be far across the map. This can be critical with some of the more complex [[Trap design|trap designs]]. For longer sieges, a small personal stockpile of booze and food is critical, or an "airlock" that can be (re)stocked for prolonged situations.

Some control rooms have all doors linked to a single lever, which is the first one pulled - this seals in the first volunteer to respond, although {{k|A}}ctivating a specific recruit and stationing them and then manually locking them in the control room is sometimes faster. Double doors, one set manual, and one set linked, allow for manual sealing of the room in either manner. (It's advised to have a backup lever somewhere to open the linked doors in case of accidents.)

Advanced players do not trust doors alone to protect their control room, as some fortress invaders are [[building destroyer]]s, and can deconstruct any door or drawbridge they come across.

Because control rooms often contain levers linked to most every important system in the fortress, it's critical to guard it against troublemakers like [[gremlin]]s and [[tantrum]]ing dwarves. Having wardogs or other attack animals chained at all entrances is a good start, and military stationed nearby is popular as well.

Because of the crowded nature of a control room, it's particularly important to [[label]] your levers, and/or organize them for positive identification as to function. Returning to a game after a week and not remembering which "red" lever releases the magma or shuts the main gate is too much [[fun]] for some players.

==Labeling==
There is no way to determine what levers operate what objects except by pulling them and seeing what happens. Because of this, it can be critical to, somehow, keep track of what lever does what and where (''especially'' in a control room!). [[Note|Label]]ing each individual lever is (possibly) the most foolproof. Some players (additionally) use architecture or color coding to help label their levers, either placing them near the objects they activate, or in small bays organized in groups (even within a control room), and/or making the mechanism (and linked objects) out of a [[The Non-Dwarf's Guide to Rock|particular colored]] stone, or likewise coloring the nearby wall or floor, or even constructing a letter or symbol in a floor mosaic - whatever works, so long as it ''does'' work.

== Computing ==

Elaborate combinations of levers (or pressure plates) and other objects can be used to create mechanical systems that can perform various forms of [[computing]].

{{Buildings}}
[[Category:Buildings]][[Category:Physics]]

40d:Pressure plate

2009-09-06T17:07:19Z

Adeptable: /* Closing a floodgate when submerged */ clarity

A '''pressure plate''' works somewhat like a [[lever]], acting as a [[trigger]] for one or more systems that have been linked to it, but instead of being deliberately tasked to be toggle by a player (and then by the first dwarf to respond to fill that task), they're activated by the weight of something on them.

Pressure plates are not configured during use, but upon placement. While placing a pressure plate, you can configure it to trigger when the following things are on it:

* [[Water]] - choose minimum and maximum levels
* [[Magma]] - choose minimum and maximum levels
* [[Creatures]] - choose minimum and maximum [[size]]; creatures of the size selected will be listed as example. You can pick whether your own citizens will trigger the plate or not. Friendly NPCs (traders ect) count as civilians.

Pressure plates default to toggleable, where they send an On signal when the determined weight is upon them and send an Off signal when it's released. Pressing {{k|o}} will change them to one-use mode, where upon being activated, they do their work then deconstruct themselves, destroying their mechanisms in the process; thus, it is a bad idea to use [[masterwork]] mechanisms in one-time pressure plates.

Pressure plates can be linked to all the same objects levers can. The effects are listed in the [[Lever]] page.

A toggleable [[trap]] may prove useless when there is a large amount of invaders walking back and forth over it, as there will not be enough time for it to activate before it is switched again. Berserk dwarves will set off pressure plates.

Note that while a pressure plate will send its "on" signal the instant it is triggered, it will not send its "off" signal until it has been in the untriggered state for 100 steps.

== Permanent Effect Pressure Plate System ==

It is possible to hook a toggleable pressure plate up to a device which makes its effect permanent until a lever is flipped. One way to do that is to build a water-sensing pressure plate in a 1x1 room, link that to your [[trap]] (a drawbridge, for example), build a hatch above it, link the hatch to the original pressure plate outside, and then put water on the hatch. When an enemy steps on the pressure plate, the hatch opens, the water falls onto the other pressure plate (water-sensing pressure plate), and it raises the drawbridge.

To make it resettable, you can use [[pump]]s controlled by a lever or by [[dwarf]]-power to move the water back to where it started. You can also build a flood-gate next to the water-sensing pressure plate (linked to a trigger obviously) and have the water flow and spread-out into a room where it can evaporate (water from a 1x1 tile will not require much room to evaporate).

You can use this pressure plate system as an inverted trigger system. In other words, a lever that controls the permanent-effect pressure plate system can be flipped from ''off'' to ''on'' and subsequently trigger a trap or mechanism from ''on'' to ''off'' as a result, and vice versa. It depends on the water level settings used for the water-sensing pressure plate:
* '''3 to 7''' - Normal, on is on and off is off
* '''0 to 2''' - Inverted, subsequent state is opposite the main trigger

The water-sensing pressure plate can be set to trigger for water levels '''0 to 2 or 3 to 7''' because if the room above is filled to the brim with water, then the 1x1 room will fill-up to level 7 quickly and when opening the floodgate or pumping it out will drop to level 2 or below quickly.

:Shortcut {{k|b}}-{{k|T}}-{{k|p}}
:Components used: [[Mechanism]]

==Common procedures==
===Closing a floodgate when submerged===

For this example, say we want to close a [[floodgate]] when a reservoir reaches a depth of 5.

* Build the pressure plate, set to activate under water ({{key|w}}) from 0 ({{key|a}}, {{key|s}}) to 4 ({{Key|z}}, {{key|x}}). Make sure it is set to reset ({{key|o}}) (The default is to reset{{version|0.28.181.40d}}; it's in the correct state when the screen reads 'Resets').
* Place the floodgate
* Connect a lever to the floodgate, and open it.
* Optionally remove the lever.
* Connect the pressure plate to the floodgate.
* Allow the pressure plate to be submerged.

The floodgate should close a few seconds after the water reaches a depth of 5 or more, and open again when the depth falls to 4 or less.

It's worth noting that the reaction time of the pressure plate-floodgate system is quite large - the reservoir may overflow before the floodgate shuts. In order to prevent this (for example, when building a [[well]] filled from a [[river]] or brook), build a run-off pool. This allows the gate enough time to close, and the water will spread out instead of overflowing as it would have in a smaller pool.

==A Word of Warning==
Depending on your setup, it can be dangerous to rely on pressure plates for automatic drains. Because of the opening/closing delay on Floodgates, a pressure plate can sometimes become 'desynced' with the floodgate it's connected to. Floodgates ignore any ON/OFF message they receive while they're in the process of opening or closing, so if your pressure plate is triggered multiple times over a short period (for example if the water on top of it is "sloshing around"), they can sometimes become 'stuck' in a position where a 7-7 plate is covered with 7 water, but the connected floodgate remains closed. It is strongly recommended that if you're building a pressure plate operated drainage system, you also link an "emergency lever" to the floodgate to avoid flooding your fortress in the event this happens. Also, if you intend to flood a passageway as a trap with a pressure plate, ensure that the plate is either one-use or uses the "permanent effect" system described above, otherwise [[goblin]]s will march back and forth across it, opening and closing the floodgates as they do so.

----

'''See Also:''' [[Repeater]]

{{Buildings}}

[[Category:Traps]]

40d:Pressure plate

2009-09-06T17:01:48Z

Adeptable: gr

A '''pressure plate''' works somewhat like a [[lever]], acting as a [[trigger]] for one or more systems that have been linked to it, but instead of being deliberately tasked to be toggle by a player (and then by the first dwarf to respond to fill that task), they're activated by the weight of something on them.

Pressure plates are not configured during use, but upon placement. While placing a pressure plate, you can configure it to trigger when the following things are on it:

* [[Water]] - choose minimum and maximum levels
* [[Magma]] - choose minimum and maximum levels
* [[Creatures]] - choose minimum and maximum [[size]]; creatures of the size selected will be listed as example. You can pick whether your own citizens will trigger the plate or not. Friendly NPCs (traders ect) count as civilians.

Pressure plates default to toggleable, where they send an On signal when the determined weight is upon them and send an Off signal when it's released. Pressing {{k|o}} will change them to one-use mode, where upon being activated, they do their work then deconstruct themselves, destroying their mechanisms in the process; thus, it is a bad idea to use [[masterwork]] mechanisms in one-time pressure plates.

Pressure plates can be linked to all the same objects levers can. The effects are listed in the [[Lever]] page.

A toggleable [[trap]] may prove useless when there is a large amount of invaders walking back and forth over it, as there will not be enough time for it to activate before it is switched again. Berserk dwarves will set off pressure plates.

Note that while a pressure plate will send its "on" signal the instant it is triggered, it will not send its "off" signal until it has been in the untriggered state for 100 steps.

== Permanent Effect Pressure Plate System ==

It is possible to hook a toggleable pressure plate up to a device which makes its effect permanent until a lever is flipped. One way to do that is to build a water-sensing pressure plate in a 1x1 room, link that to your [[trap]] (a drawbridge, for example), build a hatch above it, link the hatch to the original pressure plate outside, and then put water on the hatch. When an enemy steps on the pressure plate, the hatch opens, the water falls onto the other pressure plate (water-sensing pressure plate), and it raises the drawbridge.

To make it resettable, you can use [[pump]]s controlled by a lever or by [[dwarf]]-power to move the water back to where it started. You can also build a flood-gate next to the water-sensing pressure plate (linked to a trigger obviously) and have the water flow and spread-out into a room where it can evaporate (water from a 1x1 tile will not require much room to evaporate).

You can use this pressure plate system as an inverted trigger system. In other words, a lever that controls the permanent-effect pressure plate system can be flipped from ''off'' to ''on'' and subsequently trigger a trap or mechanism from ''on'' to ''off'' as a result, and vice versa. It depends on the water level settings used for the water-sensing pressure plate:
* '''3 to 7''' - Normal, on is on and off is off
* '''0 to 2''' - Inverted, subsequent state is opposite the main trigger

The water-sensing pressure plate can be set to trigger for water levels '''0 to 2 or 3 to 7''' because if the room above is filled to the brim with water, then the 1x1 room will fill-up to level 7 quickly and when opening the floodgate or pumping it out will drop to level 2 or below quickly.

:Shortcut {{k|b}}-{{k|T}}-{{k|p}}
:Components used: [[Mechanism]]

==Common procedures==
===Closing a floodgate when submerged===

For this example, say we want to close a [[floodgate]] when a reservoir reaches a depth of 5.

* Build the pressure plate, set to activate under water ({{key|w}}) from 0 ({{key|a}}, {{key|s}}) to 4 ({{Key|z}}, {{key|x}}). Make sure it is set to reset ({{key|o}}) (The default is auto-reset and does not need to be changed{{version|0.28.181.40d}}, you'll know it's set because the screen will read 'Resets').
* Place the floodgate
* Connect a lever to the floodgate, and open it.
* Optionally remove the lever.
* Connect the pressure plate to the floodgate.
* Allow the pressure plate to be submerged.

The floodgate should close a few seconds after the water reaches a depth of 5 or more, and open again when the depth falls to 4 or less.

It's worth noting that the reaction time of the pressure plate-floodgate system is quite large - the reservoir may overflow before the floodgate shuts. In order to prevent this (for example, when building a [[well]] filled from a [[river]] or brook), build a large run-off pool. This allows the gate enough time to close, and the water will instead continue to spread out instead of overflowing, as it would have in a smaller pool.

==A Word of Warning==
Depending on your setup, it can be dangerous to rely on pressure plates for automatic drains. Because of the opening/closing delay on Floodgates, a pressure plate can sometimes become 'desynced' with the floodgate it's connected to. Floodgates ignore any ON/OFF message they receive while they're in the process of opening or closing, so if your pressure plate is triggered multiple times over a short period (for example if the water on top of it is "sloshing around"), they can sometimes become 'stuck' in a position where a 7-7 plate is covered with 7 water, but the connected floodgate remains closed. It is strongly recommended that if you're building a pressure plate operated drainage system, you also link an "emergency lever" to the floodgate to avoid flooding your fortress in the event this happens. Also, if you intend to flood a passageway as a trap with a pressure plate, ensure that the plate is either one-use or uses the "permanent effect" system described above, otherwise [[goblin]]s will march back and forth across it, opening and closing the floodgates as they do so.

----

'''See Also:''' [[Repeater]]

{{Buildings}}

[[Category:Traps]]

40d:Magma

2009-03-21T01:58:59Z

Adeptable: /* Producing Obsidian */ fix error - magma of depth 1 leaves behind Obsidian when it comes into contact with water (though it can evaporate,whih may be where the mistake came from)

'''Magma''' is red-hot molten rock present in [[volcano]]es (it is called '''lava''' after it is erupted), as well as magma pools and magma pipes. It serves as an energy source, powering [[magma forge]]s, [[magma glass furnace]]s and [[magma smelter]]s. It is extremely dangerous.

==Magma sources==
Magma occurs in three different features; Magma pools, Magma Pipes, and [[Volcano|Volcanoes]].

* A '''Magma Pool''' is a reservoir of magma that occupies only a few Z-Levels in the mountain, without reaching the surface. Magma Pools can be very small, and may have few suitable locations for buildings that rely on magma. Magma in these pools is limited, and pools will not refill with magma once emptied.

* A '''Magma Pipe''' starts at the lowest z-level of the map from a magma (or lava) flow and extend in a pipe shape upwards, sometimes reaching the surface but often not. Magma Pipes gradually refill with magma.

* A [[Volcano]] is similar to a magma pipe, but it has the advantage of being a geographical feature that is visible on the [[location]] screen. This means that it is a lot easier to find. However, it IS actually possible for a volcano that shows up on the "local" and region screen in the starting location chooser to be entirely underground - Although you could see it in the starting location chooser, it would not be visible from the surface once your dwarves have arrived at the fort's site.

== Finding magma ==

Volcanoes are visible on the "local" screen in the starting location chooser. It is represented as a red ≈ mark (a double tilde) - essentially it looks like red water. Note that red ≈ marks in the "region" screen mean something different entirely (e.g. red sand).
If you are using a certain [[utility]], you can also see magma pools and magma pipes on the local screen in the embark menu.
After you have embarked for 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.

While picking a starting location, the easiest place to look for magma is on or near a [[volcano]] (a red ^ mark in the "region" screen). There are often volcanic islands (easy to find, since they are the sole land in the middle of oceans), but since sea travel is not yet implemented, trade with other races may not be possible on such islands. Instead, find a volcano on land, and (optionally) start looking for a vent in nearby squares. "Nearby squares" can mean anything from literally on top of the volcano, to adjacent, to quite a long distance away indeed. The placement of magma seems to be related to the distance from volcanoes, but is still essentially random.

Magma vents occur exclusively in world map tiles that are primarily igneous extrusive. That is to say, if you select an entire tile on the embarkation screen and press F1 to highlight the most common terrain, the tile will only have magma if the top stone is dark gray, signifying igneous extrusive rock. Magma does not necessarily form in this geological zone/biome, rather anywhere in the tile. Even if magma is not evident on the surface, it's almost certain to be underground somewhere, though the chances of finding it without reveal.exe are still slim.

Much harder than simply finding a magma vent is finding a magma vent 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.

Since volcanoes show up on the region finder, and magma vents do not, you may find it easier to simply check all volcanoes on a map for suitability, and generate a new world if none are suitable, rather than scouring tile after tile for magma vents.

If you're willing to search exhaustively, you might want to consider finding magma vents that are not near volcanoes at all. Very occasionally, magma will be visible in the middle of forests, plains, or other terrain nowhere near a volcano or even mountains. There is no way to spot these on the region map, so you have to review the local maps. This can be done from DF, but since it involves a lot of scrolling and is very tedious, you can try exporting the local map of the world which can be much more quickly searched for the distinctive red ≈ symbol.

You can also occasionally find magma that does not extend all the way to the surface, and therefore is not visible on the local map. These are in fact much more numerous than surface-visible magma vents; however, they are almost impossible to find without cheating via one of the [[utilities]] like "reveal.exe", since unlike proper magma vents these smaller deposits must be almost literally mined into to see (you will get a warning about "warm stone" before you actually breach the deposit). These smaller magma deposits appear in the same places as normal magma vents - near volcanoes, or, failing that, near other known magma.

The newly-added "Site Finder" feature neatly sidesteps all of this legwork, allowing you to search for a site with a magma pool or pipe without having to manually check each tile on the world map. Note that unless you edit the .init file so that magma features are shown on the local map, you won't know exactly ''where'' the lava is prior to embarking- just that it exists. Depending on whether or not you like a little mystery, this can be turned on or off at will.

== Using magma ==

On a map with a magma vent, the magma will be clearly visible from every level ground and below, unless the map is in a Freezing area. In Freezing areas, the top few levels of the vent will have cooled to form an [[obsidian]] "cap". This should still be readily recognizable however, as it will comprise a circular area. The minerals directly adjacent to the magma vent will also be immediately visible, even at the lowest level of the map, which can give some hints about where to prospect for ores.

[[Image:magmacap.png|thumb|188px|Obsidian "magmacap" as seen from ground level]]

The vent has a similar, circular shape on each level. However, it is not identical from one level to the next; some levels will have a larger or somewhat misshapen circle of magma.

The primary use for magma is to power [[magma smelter]]s, [[magma glass furnace]]s and [[magma forge]]s. (There are other uses, including defense, [[obsidian]] production, and possibly even garbage disposal.) To build forges, etc. on magma, at least one of the external eight squares must be above a square of magma.

This can be done most easily by simply building on ground level. The magma is visible from ground level but is actually contained one level below ground level, just like any ground-level water source.

To build underground, you will need to dig at least one tile of a [[channel]] above the location you wish to build the smelter or forge. Underneath this channel there must be magma, either directly from the vent or channeled from the vent. You can simply build a tunnel straight into the magma, or use channels to tap into the magma on the level below safely - this latter is easier if there is more magma on the lower level than the level on which you wish to build. Tapping into magma directly is usually safe provided that you are prepared for it (see Pressure note below). Magma is much slower than water, and can be stopped by a simple [[bauxite]] [[floodgate]]. Take care however if you are using a [[screwpump]] to pump magma into a tunnel/funnel with a cistern below - the pump will make the magma overflow as it would with water.

Volcanoes and magma tubes slowly replenish their supply of magma. A miner with less than Unbelievably Agile will die when breaching a magma tube as he can't move away quick enough.

=== Producing Obsidian ===
Magma can also be used to produce [[Obsidian]], a stone which can be used to make swords at a [[Craftsdwarf's Workshop]] and which has a base value of 3 (compare with 1 for normal [[stone]] and 2 for [[flux]]). If you have a magma pipe and an inexhaustible source of water, you can produce an inexhaustible supply of Obsidian. One method: A reservoir must be built with a controlled inflow of water. The floor of this room should be channeled out and replaced with one or more retractable bridges, linked to a (single) lever. One Z-level below the reservoir a 'channeling area' should remain empty. This area should cover the full area beneath the bridges plus a single row 'ledge' to the west or left (Access is only required from this side). The area beneath the bridges should be channeled one Z-level further. The easiest way to do this is one row at a time, from east to west. The ledge allows the last row to be easily channeled. In the lowest Z-level, access for stone haulers should be from the east side, and controlled by a [[magma-safe]] floodgate. Inflow of magma into this area should not be from directly above, nor should it be pressurized by pumping to a higher level. If obsidian is created in the channeling area (rather than in the magma reservoir area below it) one or more bridges will have to be destroyed, re-built, and re-mechanized to resume proper function. Therefore it is important that magma enters this area from the side.

The two reservoirs should be filled to at least 2 units depth, to avoid evaporation. It is not necessary that the depths be balanced, only the area; water and magma are instantly destroyed when they come into contact, resulting in no spillover. In order to prevent flooding, the upper reservoir should be sealed before the bridges are retracted.

==Magma flow==

[[Image:Safemagma.png|thumb|188px|Magma safely diverted underground (cross section)]]

Magma is a chunky liquid and as such will not be forced upwards by pressure under normal circumstances.

Thus it can be safely passed through tunnels to be used at a lower point in the fortress.

A frequent mistake, however, is to assume that a channel is sufficient to cause magma to fall. While magma will not rise out of a channel, it can flow over the top once the channel fills up.

Another common mistake has to deal with magma pipes and volcanos in Freezing areas. Many people will channel into the obsidian cap and then into the magma through there. However, once a tile of the obsidian 'cap' is breached, the tile directly above the breach will then be included as part of the magma pipe and the magma will begin rising until it has filled that square. For fortresses that tapped into the magma, this can result in waves of magma slowly filling up the fortress from the bottom level up to the magma pipe's new top level. The magma can continue to rise all of the way to the surface if an entire section of the obsidian cap is channeled. The magma will not harden into obsidian again, though, just from the cold temperatures.

[[Image:Unsafemagma.png|thumb|188px|Danger: This will overflow (cross section)]]

(v0.28.181.40d:) Also note that screw pumps can cause magma to behave oddly. Magma that is emerging pumped from a screwpump will behave as if pressurized, and be forced upwards to the same level as the pump. However, this only occurs while the pump is actively pumping magma into a tile that is already full. It seems likely that this behavior is a result of code in the pump ignoring what type of fluid is being pumped, causing the pumped fluid to be passed to a connected tile as if pressurized. It may not be desired behavior, and thus may change in subsequent versions.

[[Image:Pumpedmagma.png|thumb|154px|Pumps will cause magma to rise to the level of the pump (cross section)]]

==Magma compared to water==

Magma is a chunky liquid. As such, it acts like water in certain circumstances, but acts differently in others.

===Similarities===

*Magma fills a tile and has seven possible depths.

*Magma flows outward and downward to expand into clear space.

*Screw pumps work in magma.

*Floodgates and [[pressure plate]]s work in magma.

*Constructed [[wall]]s of all kinds safely contain magma.

*Objects thrown into magma sink to the bottom.

*Magma that is only 1 deep "evaporates" over time.

*A magma-fall generates magma mist, just as a waterfall generates normal mist.

===Differences===

*Magma is extremely hot, and capable of melting objects and constructions made of most materials (see [[Magma#Magma vs. built objects|Magma vs. built objects]]) and thus destroying them.

*Magma is not normally pressurized, it seeps out of holes slower than water and slow enough for any [[dwarves]] to outrun, unless they are the ones digging into it.

*Magma flows up from a direct vertical line from the bottom of a [[Magma#Magma sources|Volcano or Magma Pipe]] only. Otherwise, its level may rise only by dripping more magma from above, and new magma may only distribute itself by moving down or to the sides, but never up.

*Magma reacts violently with water, releasing steam and, depending on the amount of magma, leaving behind tiles of solid obsidian which can be mined, smoothed or engraved like any natural tile.

*Magma is not a water source. Dwarves can't drink it or supply it to their wounded.

*Magma mist, unlike regular mist, will burn whatever it touches.

== Magma vs. built objects ==

Some objects that come in contact with magma will function fine, no matter what their material. Others will melt or cease to work properly unless they're made of [[magma-safe materials]].

* [[Workshop]]s that are powered by magma need not be built of magma-safe materials to function.

* Constructed objects like [[wall]]s, [[floor]]s, [[stairs]] and [[ramps]] can be made of any material, even those that are not "Magma-safe", and can come into contact with magma without issues.

* Like walls, [[door]]s can also be built out of any material and still hold back lava as long as it's in the "closed" position. It may be wise to make sure hallways/rooms close to an engineering project involving magma have plenty of doors, just in case you have a little too much [[fun]] when you forget to build that last [[floodgate]].

* [[Bridge]]s that are built over magma may be constructed of any material. However, bridges that are submerged in magma must be constructed of a magma-safe material.

* Most machines must be made of [[magma-safe materials]] to function for more than a few minutes in magma. This includes [[floodgate]]s. Unsafe materials will function for a while, but then burn away. Screw pumps will not melt, but will burn. Stone [[block]]s and [[copper]] [[pipe]]s/[[enormous corkscrew|corkscrews]] will not melt.

* Stone [[mechanism]]s attached to a construction will melt in magma unless made of bauxite or [[raw adamantine]], even if the construction itself is made of [[steel]]. In addition, if the mechanisms melt off of a floodgate, the floodgate will cease to be "constructed" and become an unplaced item again.{{version|0.27.176.38c}} At this point, the magma will flow over it freely.

== Magma creatures ==
[[Fire imp]]s, [[fire man|firemen]], [[magma man|magma men]], and [[fire snake]]s inhabit Magma. Fire snakes are a type of [[vermin]] that can set your fortress on [[fire]] with little to no warning. Like all other vermin, they may spawn a short distance outside their native environment, meaning they can appear in any region near a magma pipe, even if the region and magma have no physical connection.

== Temperature settings ==

Magma is almost harmless if temperature is disabled in the Dwarf Fortress init file. It can still trap and suffocate or simply starve your dwarves in some situations. It will not melt bridges, etc. constructed of non-[[magma-proof]] materials.

== Magma reactions ==

*Water: If magma happens to contact water it produces some steam and [[obsidian]]. Steam is no longer deadly (as in the old 2D version) so steam traps are ineffective; however, it is now much safer to cast large volumes of [[obsidian]] inside mined or constructed molds. The resulting slabs of [[obsidian]] are functionally identical to native stone.
*[[Brook]]s: If magma comes in contact with a brook, it will not produce steam, but will turn the water tile below the brook to obsidian, and give the brook tile the appearance of a dried-up brook.
*Rocks: [[stone|Rock]]s left over from mining will melt if magma covers them.
*Trees: [[Tree]]s will not (yet) burn or be destroyed by magma.
*Speed: Magma moves relatively slowly. While it is nearly impossible to try to seal off water let loose, magma is slow enough for your dwarves to build a floodgate or door, or even wall off the flooding area, if you happen to let magma loose by mistake.
*Pressure: Magma does not transmit [[water pressure|pressure]].
*In a volcano or a magma pipe, magma will occasionally appear in small columns above its surface [http://www.bay12games.com/forum/index.php?topic=26201.msg311730#msg311730] if it is below its original level. It will not be created above floors. It will be created in 7s, and will probably spread around in few seconds. This may be deadly to unlucky dwarves standing around. Therefore, to be sure to avoid casualties, do not build workshops except at the highest level of magma.

[[Category:Physics]]
{{Magma FAQ}}

40d:Magma

2009-03-21T01:55:25Z

Adeptable: /* Using magma */ gr; introduce section header

'''Magma''' is red-hot molten rock present in [[volcano]]es (it is called '''lava''' after it is erupted), as well as magma pools and magma pipes. It serves as an energy source, powering [[magma forge]]s, [[magma glass furnace]]s and [[magma smelter]]s. It is extremely dangerous.

==Magma sources==
Magma occurs in three different features; Magma pools, Magma Pipes, and [[Volcano|Volcanoes]].

* A '''Magma Pool''' is a reservoir of magma that occupies only a few Z-Levels in the mountain, without reaching the surface. Magma Pools can be very small, and may have few suitable locations for buildings that rely on magma. Magma in these pools is limited, and pools will not refill with magma once emptied.

* A '''Magma Pipe''' starts at the lowest z-level of the map from a magma (or lava) flow and extend in a pipe shape upwards, sometimes reaching the surface but often not. Magma Pipes gradually refill with magma.

* A [[Volcano]] is similar to a magma pipe, but it has the advantage of being a geographical feature that is visible on the [[location]] screen. This means that it is a lot easier to find. However, it IS actually possible for a volcano that shows up on the "local" and region screen in the starting location chooser to be entirely underground - Although you could see it in the starting location chooser, it would not be visible from the surface once your dwarves have arrived at the fort's site.

== Finding magma ==

Volcanoes are visible on the "local" screen in the starting location chooser. It is represented as a red ≈ mark (a double tilde) - essentially it looks like red water. Note that red ≈ marks in the "region" screen mean something different entirely (e.g. red sand).
If you are using a certain [[utility]], you can also see magma pools and magma pipes on the local screen in the embark menu.
After you have embarked for 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.

While picking a starting location, the easiest place to look for magma is on or near a [[volcano]] (a red ^ mark in the "region" screen). There are often volcanic islands (easy to find, since they are the sole land in the middle of oceans), but since sea travel is not yet implemented, trade with other races may not be possible on such islands. Instead, find a volcano on land, and (optionally) start looking for a vent in nearby squares. "Nearby squares" can mean anything from literally on top of the volcano, to adjacent, to quite a long distance away indeed. The placement of magma seems to be related to the distance from volcanoes, but is still essentially random.

Magma vents occur exclusively in world map tiles that are primarily igneous extrusive. That is to say, if you select an entire tile on the embarkation screen and press F1 to highlight the most common terrain, the tile will only have magma if the top stone is dark gray, signifying igneous extrusive rock. Magma does not necessarily form in this geological zone/biome, rather anywhere in the tile. Even if magma is not evident on the surface, it's almost certain to be underground somewhere, though the chances of finding it without reveal.exe are still slim.

Much harder than simply finding a magma vent is finding a magma vent 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.

Since volcanoes show up on the region finder, and magma vents do not, you may find it easier to simply check all volcanoes on a map for suitability, and generate a new world if none are suitable, rather than scouring tile after tile for magma vents.

If you're willing to search exhaustively, you might want to consider finding magma vents that are not near volcanoes at all. Very occasionally, magma will be visible in the middle of forests, plains, or other terrain nowhere near a volcano or even mountains. There is no way to spot these on the region map, so you have to review the local maps. This can be done from DF, but since it involves a lot of scrolling and is very tedious, you can try exporting the local map of the world which can be much more quickly searched for the distinctive red ≈ symbol.

You can also occasionally find magma that does not extend all the way to the surface, and therefore is not visible on the local map. These are in fact much more numerous than surface-visible magma vents; however, they are almost impossible to find without cheating via one of the [[utilities]] like "reveal.exe", since unlike proper magma vents these smaller deposits must be almost literally mined into to see (you will get a warning about "warm stone" before you actually breach the deposit). These smaller magma deposits appear in the same places as normal magma vents - near volcanoes, or, failing that, near other known magma.

The newly-added "Site Finder" feature neatly sidesteps all of this legwork, allowing you to search for a site with a magma pool or pipe without having to manually check each tile on the world map. Note that unless you edit the .init file so that magma features are shown on the local map, you won't know exactly ''where'' the lava is prior to embarking- just that it exists. Depending on whether or not you like a little mystery, this can be turned on or off at will.

== Using magma ==

On a map with a magma vent, the magma will be clearly visible from every level ground and below, unless the map is in a Freezing area. In Freezing areas, the top few levels of the vent will have cooled to form an [[obsidian]] "cap". This should still be readily recognizable however, as it will comprise a circular area. The minerals directly adjacent to the magma vent will also be immediately visible, even at the lowest level of the map, which can give some hints about where to prospect for ores.

[[Image:magmacap.png|thumb|188px|Obsidian "magmacap" as seen from ground level]]

The vent has a similar, circular shape on each level. However, it is not identical from one level to the next; some levels will have a larger or somewhat misshapen circle of magma.

The primary use for magma is to power [[magma smelter]]s, [[magma glass furnace]]s and [[magma forge]]s. (There are other uses, including defense, [[obsidian]] production, and possibly even garbage disposal.) To build forges, etc. on magma, at least one of the external eight squares must be above a square of magma.

This can be done most easily by simply building on ground level. The magma is visible from ground level but is actually contained one level below ground level, just like any ground-level water source.

To build underground, you will need to dig at least one tile of a [[channel]] above the location you wish to build the smelter or forge. Underneath this channel there must be magma, either directly from the vent or channeled from the vent. You can simply build a tunnel straight into the magma, or use channels to tap into the magma on the level below safely - this latter is easier if there is more magma on the lower level than the level on which you wish to build. Tapping into magma directly is usually safe provided that you are prepared for it (see Pressure note below). Magma is much slower than water, and can be stopped by a simple [[bauxite]] [[floodgate]]. Take care however if you are using a [[screwpump]] to pump magma into a tunnel/funnel with a cistern below - the pump will make the magma overflow as it would with water.

Volcanoes and magma tubes slowly replenish their supply of magma. A miner with less than Unbelievably Agile will die when breaching a magma tube as he can't move away quick enough.

=== Producing Obsidian ===
Magma can also be used to produce [[Obsidian]], a stone which can be used to make swords at a [[Craftsdwarf's Workshop]] and which has a base value of 3 (compare with 1 for normal [[stone]] and 2 for [[flux]]). If you have a magma pipe and an inexhaustible source of water, you can produce an inexhaustible supply of Obsidian. One method: A reservoir must be built with a controlled inflow of water. The floor of this room should be channeled out and replaced with one or more retractable bridges, linked to a (single) lever. One Z-level below the reservoir a 'channeling area' should remain empty. This area should cover the full area beneath the bridges plus a single row 'ledge' to the west or left (Access is only required from this side). The area beneath the bridges should be channeled one Z-level further. The easiest way to do this is one row at a time, from east to west. The ledge allows the last row to be easily channeled. In the lowest Z-level, access for stone haulers should be from the east side, and controlled by a [[magma-safe]] floodgate. Inflow of magma into this area should not be from directly above, nor should it be pressurized by pumping to a higher level. If obsidian is created in the channeling area (rather than in the magma reservoir area below it) one or more bridges will have to be destroyed, re-built, and re-mechanized to resume proper function. Therefore it is important that magma enters this area from the side.

The two reservoirs should be filled to at least 2 units depth (to avoid evaporation, in the case of the water reservoir, and to ensure that obsidian is created in the case of magma. Magma of depth 1 may be destroyed without producing obsidian.{{verify}}) It is not necessary that the depths be balanced, only the area; water and magma are instantly destroyed when they come into contact, resulting in no spillover. In order to prevent flooding, the upper reservoir should be sealed before the bridges are retracted.

==Magma flow==

[[Image:Safemagma.png|thumb|188px|Magma safely diverted underground (cross section)]]

Magma is a chunky liquid and as such will not be forced upwards by pressure under normal circumstances.

Thus it can be safely passed through tunnels to be used at a lower point in the fortress.

A frequent mistake, however, is to assume that a channel is sufficient to cause magma to fall. While magma will not rise out of a channel, it can flow over the top once the channel fills up.

Another common mistake has to deal with magma pipes and volcanos in Freezing areas. Many people will channel into the obsidian cap and then into the magma through there. However, once a tile of the obsidian 'cap' is breached, the tile directly above the breach will then be included as part of the magma pipe and the magma will begin rising until it has filled that square. For fortresses that tapped into the magma, this can result in waves of magma slowly filling up the fortress from the bottom level up to the magma pipe's new top level. The magma can continue to rise all of the way to the surface if an entire section of the obsidian cap is channeled. The magma will not harden into obsidian again, though, just from the cold temperatures.

[[Image:Unsafemagma.png|thumb|188px|Danger: This will overflow (cross section)]]

(v0.28.181.40d:) Also note that screw pumps can cause magma to behave oddly. Magma that is emerging pumped from a screwpump will behave as if pressurized, and be forced upwards to the same level as the pump. However, this only occurs while the pump is actively pumping magma into a tile that is already full. It seems likely that this behavior is a result of code in the pump ignoring what type of fluid is being pumped, causing the pumped fluid to be passed to a connected tile as if pressurized. It may not be desired behavior, and thus may change in subsequent versions.

[[Image:Pumpedmagma.png|thumb|154px|Pumps will cause magma to rise to the level of the pump (cross section)]]

==Magma compared to water==

Magma is a chunky liquid. As such, it acts like water in certain circumstances, but acts differently in others.

===Similarities===

*Magma fills a tile and has seven possible depths.

*Magma flows outward and downward to expand into clear space.

*Screw pumps work in magma.

*Floodgates and [[pressure plate]]s work in magma.

*Constructed [[wall]]s of all kinds safely contain magma.

*Objects thrown into magma sink to the bottom.

*Magma that is only 1 deep "evaporates" over time.

*A magma-fall generates magma mist, just as a waterfall generates normal mist.

===Differences===

*Magma is extremely hot, and capable of melting objects and constructions made of most materials (see [[Magma#Magma vs. built objects|Magma vs. built objects]]) and thus destroying them.

*Magma is not normally pressurized, it seeps out of holes slower than water and slow enough for any [[dwarves]] to outrun, unless they are the ones digging into it.

*Magma flows up from a direct vertical line from the bottom of a [[Magma#Magma sources|Volcano or Magma Pipe]] only. Otherwise, its level may rise only by dripping more magma from above, and new magma may only distribute itself by moving down or to the sides, but never up.

*Magma reacts violently with water, releasing steam and, depending on the amount of magma, leaving behind tiles of solid obsidian which can be mined, smoothed or engraved like any natural tile.

*Magma is not a water source. Dwarves can't drink it or supply it to their wounded.

*Magma mist, unlike regular mist, will burn whatever it touches.

== Magma vs. built objects ==

Some objects that come in contact with magma will function fine, no matter what their material. Others will melt or cease to work properly unless they're made of [[magma-safe materials]].

* [[Workshop]]s that are powered by magma need not be built of magma-safe materials to function.

* Constructed objects like [[wall]]s, [[floor]]s, [[stairs]] and [[ramps]] can be made of any material, even those that are not "Magma-safe", and can come into contact with magma without issues.

* Like walls, [[door]]s can also be built out of any material and still hold back lava as long as it's in the "closed" position. It may be wise to make sure hallways/rooms close to an engineering project involving magma have plenty of doors, just in case you have a little too much [[fun]] when you forget to build that last [[floodgate]].

* [[Bridge]]s that are built over magma may be constructed of any material. However, bridges that are submerged in magma must be constructed of a magma-safe material.

* Most machines must be made of [[magma-safe materials]] to function for more than a few minutes in magma. This includes [[floodgate]]s. Unsafe materials will function for a while, but then burn away. Screw pumps will not melt, but will burn. Stone [[block]]s and [[copper]] [[pipe]]s/[[enormous corkscrew|corkscrews]] will not melt.

* Stone [[mechanism]]s attached to a construction will melt in magma unless made of bauxite or [[raw adamantine]], even if the construction itself is made of [[steel]]. In addition, if the mechanisms melt off of a floodgate, the floodgate will cease to be "constructed" and become an unplaced item again.{{version|0.27.176.38c}} At this point, the magma will flow over it freely.

== Magma creatures ==
[[Fire imp]]s, [[fire man|firemen]], [[magma man|magma men]], and [[fire snake]]s inhabit Magma. Fire snakes are a type of [[vermin]] that can set your fortress on [[fire]] with little to no warning. Like all other vermin, they may spawn a short distance outside their native environment, meaning they can appear in any region near a magma pipe, even if the region and magma have no physical connection.

== Temperature settings ==

Magma is almost harmless if temperature is disabled in the Dwarf Fortress init file. It can still trap and suffocate or simply starve your dwarves in some situations. It will not melt bridges, etc. constructed of non-[[magma-proof]] materials.

== Magma reactions ==

*Water: If magma happens to contact water it produces some steam and [[obsidian]]. Steam is no longer deadly (as in the old 2D version) so steam traps are ineffective; however, it is now much safer to cast large volumes of [[obsidian]] inside mined or constructed molds. The resulting slabs of [[obsidian]] are functionally identical to native stone.
*[[Brook]]s: If magma comes in contact with a brook, it will not produce steam, but will turn the water tile below the brook to obsidian, and give the brook tile the appearance of a dried-up brook.
*Rocks: [[stone|Rock]]s left over from mining will melt if magma covers them.
*Trees: [[Tree]]s will not (yet) burn or be destroyed by magma.
*Speed: Magma moves relatively slowly. While it is nearly impossible to try to seal off water let loose, magma is slow enough for your dwarves to build a floodgate or door, or even wall off the flooding area, if you happen to let magma loose by mistake.
*Pressure: Magma does not transmit [[water pressure|pressure]].
*In a volcano or a magma pipe, magma will occasionally appear in small columns above its surface [http://www.bay12games.com/forum/index.php?topic=26201.msg311730#msg311730] if it is below its original level. It will not be created above floors. It will be created in 7s, and will probably spread around in few seconds. This may be deadly to unlucky dwarves standing around. Therefore, to be sure to avoid casualties, do not build workshops except at the highest level of magma.

[[Category:Physics]]
{{Magma FAQ}}

40d:Important advice

2009-03-21T01:41:52Z

Adeptable: /* Tips and Tricks */ gr

Here are a few things to keep in mind when playing Dwarf Fortress.

Above all, one must remember that losing is [[fun]]! Be prepared to lose a few fortresses before you get the hang of things – it can be easy to accidentally kill the entire fortress while playing around with the different mechanics.
But remember: losing means that next time, you'll remember how you lost! In a big way, Dwarf Fortress uses the principle of learning from one's mistakes.

== Advice ==

* Keep in mind that Dwarf Fortress doesn't have a "win" condition: It just has a long series of "lose" conditions.

* Learn the [[controls]]. There's lots of them, and learning them may seem daunting at first, but once you get the basics down (like how to check the status of your dwarves or the hotkeys for building certain structures), you'll find yourself playing much more efficiently. [[Efficient_gameplay|Efficient Gameplay]] offers some time-saving tips.

* Save often! Although it can be a hassle to have to quit out and get back in, it's a lot better than having to build that long hallway of stone-fall traps, plant the whole bag of plump helmet seeds, and make that shipment of steel battleaxes for the caravan next year, all over again.
** In this vein, there is a seasonal auto-save feature which you can turn on by editing your /data/init/init.txt file.

* If a dwarf drinks only water, the rate at which he gets tasks done decreases. If the fortress has no alcohol for years, things will slow down quite a bit.

* If your game is running slowly, see [[Maximizing framerate]] for advice.

* If you cannot find your answer on this wiki, check out the forums at [http://www.bay12games.com/forum/index.php Bay12games.com]
[[Category:Guides]]

== Tips and Tricks ==

* To find a dead dwarf, go under status ({{k|z}}), then select stock>>corpses. Hit tab, and use {{k|z}} to zoom to the particular dwarf to find a hint on where and how he died.

* Usually the closest available material is used for ambiguous tasks such as a floodgate, but not always. To prevent frustration, you can make a custom stockpile (e.g. for [[bauxite]]) next to your workshop and close the dwarf in. Don't forget theres a z-axis, so make sure there aren't unwanted materials above/below your workshop. (A good start for magma maps is to build the workshop next to the wagon, and get your magma-proof grate/floodgate/mechanisms painlessly)

* Dwarves get trapped easily. They like building things, digging, etc. from certain directions so make sure there is a way out. For more assumptions see [[Digging#Dig_Priority|digging]].

40d:Important advice

2009-03-21T01:40:29Z

Adeptable: /* Advice */ no need to mention that seasonal autosave is new; also fix link display

Here are a few things to keep in mind when playing Dwarf Fortress.

Above all, one must remember that losing is [[fun]]! Be prepared to lose a few fortresses before you get the hang of things – it can be easy to accidentally kill the entire fortress while playing around with the different mechanics.
But remember: losing means that next time, you'll remember how you lost! In a big way, Dwarf Fortress uses the principle of learning from one's mistakes.

== Advice ==

* Keep in mind that Dwarf Fortress doesn't have a "win" condition: It just has a long series of "lose" conditions.

* Learn the [[controls]]. There's lots of them, and learning them may seem daunting at first, but once you get the basics down (like how to check the status of your dwarves or the hotkeys for building certain structures), you'll find yourself playing much more efficiently. [[Efficient_gameplay|Efficient Gameplay]] offers some time-saving tips.

* Save often! Although it can be a hassle to have to quit out and get back in, it's a lot better than having to build that long hallway of stone-fall traps, plant the whole bag of plump helmet seeds, and make that shipment of steel battleaxes for the caravan next year, all over again.
** In this vein, there is a seasonal auto-save feature which you can turn on by editing your /data/init/init.txt file.

* If a dwarf drinks only water, the rate at which he gets tasks done decreases. If the fortress has no alcohol for years, things will slow down quite a bit.

* If your game is running slowly, see [[Maximizing framerate]] for advice.

* If you cannot find your answer on this wiki, check out the forums at [http://www.bay12games.com/forum/index.php Bay12games.com]
[[Category:Guides]]

== Tips and Tricks ==

* To find a dead dwarf, go under status ({{k|z}}), then select stock>>corpses. Hit tab, and use {{k|z}} to zoom to the particular dwarf to find a hint on where and how he died.

* Usually the closest available material is used for ambiguous tasks such as a floodgate, but not always. To prevent frustration, you can make a custom stockpile (e.g. for [[bauxite]]) next to your workshop and close the dwarf in. Don't forget theres a z-axis, so make sure there aren't unwanted materials above/below your workshop. (A good start for magma maps is to build the workshop next to the wagon, and get your magma-proof grate/floodgate/mechanisms painlessly)

* Dwarves get trapped easily. They like building things/digging/.. from certain directions of the site so make sure there is a way out. For more assumptions see [[Digging#Dig_Priority|digging]].

User:Adeptable/ToDo

2009-03-19T02:01:24Z

Adeptable: create my own ToDo page

* [[Template:CreatureInfo]] is broken

40d:Modding guide

2009-03-19T01:41:10Z

Adeptable: /* Basics of DF modding */ gr

This is intended to be an easy guide for general newbies on how to both edit and add civilizations, creatures, objects, and so on in Dwarf Fortress, both [[Adventure_Mode|adventurer]] and [[Dwarf_Fortress_Mode|fortress]] modes, without breaking anything too much. Generally breaking stuff is fine! Just always back up your work & the originals, and be patient at having to [[World_Generation|generate new worlds]] over and over.

This guide was edited for version 0.27.176.39c and may not be accurate for later versions, particularly the examples.

= Modding Guide =

== Basics of DF modding ==

All of the data you can edit are stored in the \raw\ folder wherever you saved your DF executable. The raw folder contains two subfolders: graphics (where you insert [[Object_Tilesets|graphic packs]] to make custom tiles), and objects, which contains all the data for generally everything in the game that is not hardcoded. Quite a lot is not hardcoded, so you can edit a wide variety of things in the game.

Editing the [[Raw file|raw text files]] is easy and simple. When you go into the \raw\objects folder you will see a wide variety of text files. When you are modding your game, you can either change existing files or add your own. I personally find it easier just to edit the existing ones in a new \DF\ game folder. When you are changing a token you can simply change the values - these are the numbers/strings after the : in a token entry. For example, [CREATURE:DWARF] is a token in the entity text file, which determines what creatures are used for dwarven civilizations. Simply open the text file, edit what you want, save and close, and generate a new world after you're done editing what you want.

Essentially, everything that can be modded uses text files to determine how they interact with the world or with other objects. With a bit of know-how you can tinker with just about everything.

Every text file uses what are called "tokens", also called "flags". They are essentially attributes that you can add or remove or edit for any particular object in the game, that change the way the object works or acts. Most of the actual effects are hardcoded: for example, giving a creature such as a moose the [EVIL] creature token will make it only appear in evil maps, or giving it [BONECARN] will make it chow down on bones.

A few key things to remember when modding the text files:

* Always back up the default text files you plan on editing. This way, if your game crashes (due to say, a typo that you can't find) you can simply copy-paste it back in for a 'vanilla' DF.
* You do not need to delete old saves; simply create a new world using your modded files and things should run fine. Just don't try to play a "non-modded" world with modded files! Should you desire to go back to your old sites, make sure you revert to the raw files used for the creation of that world.
* In general it's better to make whole new text files for new stuff you're adding rather than editing the existing ones by tagging them onto the bottom. This allows you to keep track of them easier and keeps them all in one place so there's less messing about with tons of files.
* The absolute easiest way to add an entirely new creature/entity/etc is to simply copy-paste an existing one and rename it, then edit the various tokens appropriately.

In addition, if you ''rename'' the any of the \raw\ files themselves (such as 'creature_insects.txt' to 'creature_bugs.txt'), you must find the same filename in the \data\objects\ folder and delete it. This is required because once the world is generated it creates the new files and saves them for use next time the world is needed; without deleting the file you will get duplication errors. This is not necessary if you just don't change any of the filenames.

== Modding the civilizations ==

The civilization entries are stored in entity_default.txt. They are quite simple files that are in the following format:

[ENTITY:ENTITYNAME]
[CREATURE:CREATURETYPE]
[TRANSLATION:LANGUAGETYPE]
[BIOME_SUPPORT:BIOMETOKEN:FREQENCY]
...[OTHER TAGS]...

At the top of the file you'll see an 'entity_default' all by itself, that must be at the top of the file only. All game files require those markers at the top. If you're creating a new civilization in its own text file, be sure to add entity_default, and [OBJECT:ENTITY] at the top of the file.

Now what do these tokens mean, exactly? For one, where the tags are located don't generally matter quite a lot. You can add them in any order as long as they're underneath the "[ENTITY:]" token, which is the 'header' of the civilization and lets the game know that everything underneath deals with that civ. The entity token can be anything as long as it's not the same as another one.

'[CREATURE:]' links the civilization with a certain creature defined in a different file. This is the creature you play in adventurer or fortress mode, or that wanders around their towns when you explore them. For example, if you wanted to do something silly you could switch the "DWARF" entry in entity_default.txt with "ELF" and you would be marching elves around in fortress mode, though they would still use dwarven technology and language and names and so forth.

'[TRANSLATION:]' connects the civ to a specific language file that determines things like their natural (untranslated) creature first + last names and city names. The valid ones are HUMAN, DWARF, ELF, and GOBLIN.

'[BIOME_SUPPORT:]' defines biomes that civs will appear in. The 'FREQUENCY' value determines the likelyhood of them appearing there: generally 1 for not very often, up to 3 for very often (ie. dwarves in mountains).

You can find many details about the rest of the civilization tokens [[Entity_Tokens|here]]. The important ones are the CIV_CONTROLLABLE token, which lets you control the civ in dwarf fortress mode and the INDIV_CONTROLLABLE and ADVENTURE_TIER tokens which lets you play the civ in adventure mode via the PLAY NOW! command. Remember that ADVENTURE_TIER must be in order, so if you are adding a new playable race you must put it above dwarves and set its tier 1 higher (4).

If you have more than one civ with the [CIV_CONTROLLABLE] token, groups belonging to that civ will appear in the group selection section on the embark screen, although it is not immediately obvious what species each group may be. While this can be determined from legends mode, experimentation suggests that the topmost species in the 'neighbors' section of the embark screen is the same as the currently selected species: If your group is dwarven, dwarves will be topmost, whilst (say) elves will be topmost if your chosen group is elven. By default, the game seems to choose a group (and therefore a species if there is more than one) at random.

Any token that has to deal with weapons, armor, clothing, etc. are all the items that the civ can build, not necessarily the ones they can wear. For example, you could create a species with no clothes specified, but then rob a clothes shop in adventurer mode and wear everything you want, or give them weapons that are too large to wield and they could sell them, but not use them.

[SELECT_SYMBOL:] and [CULL_SYMBOL:ALL:] are the words that can be randomly generated in names, civs, cities, artifacts, engravings, etc. "SELECT_SYMBOL" means that the civ is far more likely to use those, and CULL_SYMBOL means they never will. You can find a list of every symbol type [[Language|here]]. SUBSELECT_SYMBOL:WAR/BATTLE/SIEGE just determines which language token to use when they begin wars, battles, or sieges in legends mode, ie. 'The Conflict of Craziness' or 'The Siege of Assaults'. All have these as 'violence' by default but they can be changed to any other token.

'SELECT:SYMBOL:ROAD/TUNNEL/BRIDGE/WALL' use the special language tokens NAME_ROAD, NAME_TUNNEL, etc. and determines what the civ names their structures. 'SELECT_SYMBOL:REMAINING': are the standard tokens used for the species language.

An easy method of creating a civilization is just to copy-paste a similar one to the bottom of the entity_default.txt file and edit things to your liking. Remember to always change the civ's ENTITY: name! This name can be anything as long as it's not already existing.

There are many tokens to play with in the entity file, most of which do something interesting. It's best to simply look through the entity tokens list and figure out for yourself what you want to do with them. The ones of interest are:

* [SIEGER] [BABYSNATCHER] [NUISANCE] These determine what the civ does in relation to other civs. Babysnatchers periodically swipe infants from nearby civs and have them grow up in their own civ (if kidnapped/brainwashed infants grow up and have children, their last names will use their capturer's language files: ie. you will have evil dwarves with the name Urist Deathghouls in a goblin fortress).

* [AT_PEACE_WITH_WILDLIFE] This token, currently set only on elves, will mean they will not attack wild animals and animals will not attack them. This ALSO means that if you bring an elf or two along with you in adventurer mode, don't expect them to help you if you get attacked by cougars!

* [RELIGION_SPHERE] This determines what religious deities will have as spheres when the civilization is generated, along with their subspheres. With a SPHERE_ALIGNMENT set you can also make one more likely than others; ie. Elves have trees, plants, and animals set very high so they are likely to get those more often with their deities.

* With [DEFAULT_SITE], LIKES_, and TOLERATES_ you can decide where the species will live. DEFAULT_SITE is their home cities and will usually cluster there in large groups. If a civ conquers another and they do not at least tolerate the enemy's home type they will simply destroy it instead of moving in (sometimes they will destroy it anyway).

* [ETHIC:] tokens determine how the species behaves when it comes to certain unpleasant acts. This also determines what reasons the civ will use when going to war: if a nearby civ has something set ACCEPTABLE that they consider UNTHINKABLE, then it is likely they will go to war over it. It also determines a few other things, like what happens to dead foes: Elves have '[ETHIC:EAT_SAPIENT_KILL:ACCEPTABLE]' for example. Goblins defacing their enemies (ie. hanging, stuck on pikes) is [ABUSE_BODIES], as well as ETHIC:MAKE_TROPHY_ tokens set ACCEPTABLE.

== Modding the creatures ==

Creature modding is great fun. Essentially you can change nearly any aspect of a creature or completely make your own from scratch. You can either add a new creature to the bottom of an existing creature_thing.txt file or make your own file; just be sure to add the name of the file (without the txt) to the top of it. For example, I tend to use a 'creature_newbies.txt' file myself.

Modding creatures is exactly similar to modding civs: just a matter of editing, adding, or removing tokens, enclosed in square brackets underneath the creature's [CREATURE:] header. The creature entries contain all the information about each specific creature in the game, from animals to dwarves to goblins to even caravan wagons. Much of the data of a creature is quite self-explanatory; you can find a list of every creature token [[Creature_Tokens|here]].

There're some tokens which use temperature values. Dwarf Fortress has it's own temperature scale for this. [[Temperature scale|DF temperature scale]].

Note: If you add a butcherable creature to the game such as a domestic animal, people will automatically wander around wearing its fur or skin as leather items when you are in the game, assuming the creature comes from the civ's biome (natural area). So don't be surprised to see 'duck leather armor' or something if you add ducks. Also note if you add a species that has a naturally high body temperature (magma snakes for example) and set it butcherable, people will automatically be generated wearing their skins.. and then since the skins have a naturally high temperature too they tend to burst into flame immediately because they were wearing a +magma snake leather sock+. Woops.

You'll notice many of the creature entries have tokens that other ones don't have. If a token is not present it's considered "default", though sometimes the default can be hard to figure out. All of the creatures referenced in the entity files are present in creature_standard.txt and require certain other tokens that non-entity creatures do not need, such as [INTELLIGENT] and [CANOPENDOORS].

For example, if you wanted to allow your dwarves to eat bones from the refuse stockpile (ew), you would open up creature_standard.txt, add [BONECARN] somewhere in the CREATURE_DWARF: entry at the top, and then save and close it, then generate a new world. Bon appetit! *Notice that this has the unfortunate side effect of making them unable to eat plants.*

[http://www.dwarffortresswiki.net/index.php/User:Deon#How_to How to add a new creature.]

== Modding items ==

Items come in several flavors: 'crafted' items, and 'natural' items. Both are the same in most ways, but are stored in different places: most crafted item data are stored in the item_blah.txt files (such as item_armor.txt), while things like plants, gems, food, and ore are stored in "matgloss" files, ie. matgloss_plant.txt. Both are easily editable just like a creature or civ, but the problem is that there is no definitive list of what most of the tokens for these quite do yet. In any case they are usually pretty self-explanatory and you can guess what they do by checking out similar entries.

For example, let's look at the entry for, of course, the thong:

[ITEM_PANTS:ITEM_PANTS_THONG]
[NAME:thong:thongs]
[WEIGHT:10]
[VALUE:10]
[BLOCKPOWER:5]
[LAYER:UNDER]
[COVERAGE:25]
[LAYER_SIZE:10]
[LAYER_PERMIT:30]
[MATERIAL_SIZE:1]
[SOFT]
[LEATHER]

Most of these are pretty obvious if one compares them to the other entries. Now, if you wanted to mod these to turn them into metal thongs (ouch!), you would simply have to add [METAL] to it somewhere, and probably [HARD] instead of [SOFT]. Simple!

Weapons work largely the same way; but remember that in order to actually use any of these things you'd have to add the ITEM_THING item flag to the civilization's 'useable items' list in entity_default.txt. For example, if you're fond of Scots and decided to make a 'claymore' sword that's even bigger than the two-hander already in the files. It might look like this:

[ITEM_WEAPON:ITEM_WEAPON_SWORD_CLAYMORE]
[NAME:claymore sword:claymore swords]
[DAMAGE:160:SLASH]
[WEIGHT:120]
[SKILL:SWORD]
[CRIT_BOOST:1]
[TWO_HANDED:0]
[MINIMUM_SIZE:7]
[MATERIAL_SIZE:5]

Tada! Yes, it's that easy. Then you just add it to the civ entry so a civilization can actually use and craft it, and it's done.

== Modding language files ==

Let's say you added a whole new species. Sure, you could just swipe one of the existing translation files and steal their language for your species, but that's the lazy way! If you want to create a whole new language, it's very simple.

First, you'd need a whole new language_RACE file, such as language_LIZARDMAN.txt, along with "language_LIZARDMAN" at the top of the file proceeded by [OBJECT:LANGUAGE] and [TRANSLATION:LIZARDMAN]. After that, it's just a matter of copy-pasting one of the existing language lists and editing the finished 'translated' word. That's it! Then just add the translation link to your civ in entity_default.txt and it'll be added to the game on worldgen.

== Modding body parts ==

Imagine you have this fantastic idea for a multi-tentacled winged spider-monster. Sounds great! But in order to make this a reality you may need to create a new set of body parts for it. That's no problem! Making body parts is easy, though it may look complicated at first.

All body definitions are located in body_default.txt and then linked to a creature in the creature's entry. For example, the dwarf creature has: [BODY:HUMANOID:2EYES:2EARS:NOSE:2LUNGS:HEART:GUTS:ORGANS:HUMANOID_JOINTS:THROAT:NECK:SPINE:BRAIN:5FINGERS:5TOES:MOUTH]. All of these are seperate bodypart definitions in body_default.txt. You can mix and match them in the creature entry and it makes no difference, as long as they're there: each bodypart will link itself to the appropriate connection automatically when the creature is first created. This means that if you don't add the appropriate bodyparts, hilarious things can happen: if you forget to add a throat or lungs your new creature will suffocate after taking a few steps (unless you make it a nonbreather).

Body parts work by sections: you can add as many sections as you want to a bodypart definition, but generally you should keep it fairly low for ease of use. Each body section entry is in the very simple format:

[BODY:BODYNAME]
[BP:ID:name][TOKENSGOHERE]

You can add as many sub-parts as you want to an overall section. The most important tokens are 'CONTYPE' and 'CON': CONTYPE means the bodypart in question is connected to a certain *type* of bodypart, while CON means it's connected to a *specific* one. Let's break down a few entries:

[BODY:BASIC_HEAD]
[BP:HD:head][CONTYPE:UPPERBODY][HEAD]

This is a very simple one: a head. It connects directly to an upper body. All the stuff inside the head are seperate entries that call up the head as a different contype in turn:

[BODY:THROAT]
[BP:THROAT:throat][CONTYPE:HEAD][THROAT][EMBEDDED][SMALL]

The foot bone's connected to the ankle bone..

If you wanted someone to be able to break someone else's throat (like breaking a joint) and suffocate them, just add the [JOINT], [BREATHE], and possibly [NERVOUS] to the throat object's tokens.

A 'BODYGLOSS', which you can sometimes find in the creature entries, are simply replacement words for certain defined words in a creature. For example, you'll find the bodygloss [BODYGLOSS:CLAW_HAND:hand:claw] in the body_default.txt, and then you can use this in a creature with '[BODYGLOSS:CLAW_HAND]' and it will replace all instances of "hand" with "claw" in that creature. For all intent and purpose the body part will still function as the proper part, though.

Note that only creatures with the [EQUIPS] token (and possibly [INTELLIGENT]) and a civ that can create clothes/armor/weapons will be able to actually wear stuff. Also, if the creature size is too large for the clothes they will also not be able to wear it.

== Example one: dark dwarves ==

These examples will go over the details for creating several new things as well as editing some old ones.

Remember: Do NOT load an old save after genning a new world with different raws. It's much safer to simply delete all your old saves after you've modded things, or simply copy-and-paste a fresh version of DF into a new folder.

First, we're going to create a new, evil civilization of dwarves called, unsurprisingly, dark dwarves. This will be quite easy, though with a few fundamental differences. Mainly, that dark dwarves are evil and more warlike than regular dwarves.

Now, open up entity_default.txt. All your species civilizations will be in there. We're going to make a whole new one for our dark dwarves. In many ways it'll be a simple copy-paste job of regular dwarves, then tweaking some things.

Add this to the TOP of the entity_default file, before the dwarf entry:

[ENTITY:DARK_DWARF]
[CIV_CONTROLLABLE]
[CREATURE:DARK_DWARF]
[TRANSLATION:DWARF]
[DIGGER:ITEM_WEAPON_PICK]
[WEAPON:ITEM_WEAPON_AXE_BATTLE]
[WEAPON:ITEM_WEAPON_WHIP]
[WEAPON:ITEM_WEAPON_FLAIL]
[WEAPON:ITEM_WEAPON_SCOURGE]
[WEAPON:ITEM_WEAPON_DAGGER_LARGE]
[WEAPON:ITEM_WEAPON_MACE]
[WEAPON:ITEM_WEAPON_SWORD_SHORT]
[WEAPON:ITEM_WEAPON_SCIMITAR]
[WEAPON:ITEM_WEAPON_CROSSBOW]
[AMMO:ITEM_AMMO_BOLTS]
[ARMOR:ITEM_ARMOR_PLATEMAIL:COMMON]
[ARMOR:ITEM_ARMOR_CHAINMAIL:COMMON]
[ARMOR:ITEM_ARMOR_LEATHER:COMMON]
[ARMOR:ITEM_ARMOR_COAT:COMMON]
[ARMOR:ITEM_ARMOR_SHIRT:COMMON]
[ARMOR:ITEM_ARMOR_CLOAK:COMMON]
[ARMOR:ITEM_ARMOR_TOGA:UNCOMMON]
[ARMOR:ITEM_ARMOR_VEST:COMMON]
[ARMOR:ITEM_ARMOR_DRESS:COMMON]
[ARMOR:ITEM_ARMOR_ROBE:COMMON]
[HELM:ITEM_HELM_HELM:COMMON]
[HELM:ITEM_HELM_HOOD:COMMON]
[GLOVES:ITEM_GLOVES_GAUNTLETS:COMMON]
[GLOVES:ITEM_GLOVES_GLOVES:COMMON]
[SHOES:ITEM_SHOES_SHOES:COMMON]
[SHOES:ITEM_SHOES_BOOTS:COMMON]
[SHOES:ITEM_SHOES_BOOTS_LOW:COMMON]
[PANTS:ITEM_PANTS_PANTS:COMMON]
[PANTS:ITEM_PANTS_GREAVES:COMMON]
[PANTS:ITEM_PANTS_LEGGINGS:COMMON]
[SHIELD:ITEM_SHIELD_SHIELD]
[SHIELD:ITEM_SHIELD_BUCKLER]
[SIEGEAMMO:ITEM_SIEGEAMMO_BALLISTA]
[TRAPCOMP:ITEM_TRAPCOMP_GIANTAXEBLADE]
[TRAPCOMP:ITEM_TRAPCOMP_ENORMOUSCORKSCREW]
[TRAPCOMP:ITEM_TRAPCOMP_SPIKEDBALL]
[TRAPCOMP:ITEM_TRAPCOMP_LARGESERRATEDDISC]
[TOY:ITEM_TOY_HAMMER]
[TOY:ITEM_TOY_AXE]
[TOY:ITEM_TOY_MINIFORGE]
[INSTRUMENT:ITEM_INSTRUMENT_TRUMPET]
[INSTRUMENT:ITEM_INSTRUMENT_DRUM]
[CLOTHING]
[SUBTERRANEAN_CLOTHING]
[CURRENCY_BY_YEAR]
[CURRENCY:COPPER:1]
[CURRENCY:SILVER:5]
[CURRENCY:GOLD:15]
[SELECT_SYMBOL:WAR:NAME_WAR]
[SUBSELECT_SYMBOL:WAR:VIOLENT]
[SELECT_SYMBOL:BATTLE:NAME_BATTLE]
[SUBSELECT_SYMBOL:BATTLE:VIOLENT]
[SELECT_SYMBOL:SIEGE:NAME_SIEGE]
[SUBSELECT_SYMBOL:SIEGE:VIOLENT]
[SELECT_SYMBOL:ROAD:NAME_ROAD]
[SELECT_SYMBOL:TUNNEL:NAME_TUNNEL]
[SELECT_SYMBOL:BRIDGE:NAME_BRIDGE]
[SELECT_SYMBOL:WALL:NAME_WALL]
[SELECT_SYMBOL:REMAINING:ARTIFICE]
[SELECT_SYMBOL:REMAINING:EARTH]
[SELECT_SYMBOL:REMAINING:EVIL]
[SELECT_SYMBOL:REMAINING:UNTOWARD]
[SELECT_SYMBOL:REMAINING:UGLY]
[SELECT_SYMBOL:REMAINING:EARTH]
[CULL_SYMBOL:ALL:DOMESTIC]
[CULL_SYMBOL:ALL:FLOWERY]
[CULL_SYMBOL:ALL:HOLY]
[CULL_SYMBOL:ALL:PEACE]
[CULL_SYMBOL:ALL:NEGATOR]
[CULL_SYMBOL:ALL:GOOD]
[METAL_PREF]
[GEM_PREF]
[STONE_PREF]
[INDOOR_FARMING]
[USE_CAVE_ANIMALS]
[USE_ANIMAL_PRODUCTS]
[USE_EVIL_ANIMALS]
[USE_EVIL_PLANTS]
[USE_EVIL_WOOD]
[COMMON_DOMESTIC_PACK]
[COMMON_DOMESTIC_PULL]
[COMMON_DOMESTIC_MOUNT]
[COMMON_DOMESTIC_PET]
[USE_MISC_PROCESSED_WOOD_PRODUCTS]
[EQUIPMENT_IMPROVEMENTS]
[ART_FACET_MODIFIER:GOOD:0]
[ART_FACET_MODIFIER:EVIL:512]
[ITEM_IMPROVEMENT_MODIFIER:RINGS_HANGING:0]
[ITEM_IMPROVEMENT_MODIFIER:BANDS:0]
[ITEM_IMPROVEMENT_MODIFIER:SPIKES:384]
[ADVENTURE_TIER:4]
[FRIENDLY_COLOR:1:0:1]
[DEFAULT_SITE_TYPE:CAVE_DETAILED]
[LIKES_SITE:CAVE_DETAILED]
[TOLERATES_SITE:CITY]
[TOLERATES_SITE:TREE_CITY]
[TOLERATES_SITE:CAVE_DETAILED]
[TOLERATES_SITE:CAVE]
[LEADER_TYPE:KING]
[SITE_LEADER_TYPE:STANDARD]
[START_BIOME:MOUNTAIN]
[BIOME_SUPPORT:ANY_WETLAND:1]
[BIOME_SUPPORT:ANY_DESERT:1]
[BIOME_SUPPORT:ANY_OCEAN:1]
[BIOME_SUPPORT:ANY_LAKE:1]
[BIOME_SUPPORT:MOUNTAIN:3]
[BIOME_SUPPORT:ANY_GRASSLAND:1]
[BIOME_SUPPORT:ANY_SAVANNA:1]
[BIOME_SUPPORT:ANY_SHRUBLAND:1]
[BIOME_SUPPORT:ANY_RIVER:1]
[DIPLOMAT]
[DIPLOMAT_BODYGUARDS]
[MERCHANT_BODYGUARDS]
[ACTIVE_SEASON:WINTER]
[SIEGER]
[MAX_STARTING_CIV_NUMBER:3]
[START_GROUP_NUMBER:10]
[MAX_POP_NUMBER:10000]
[MAX_SITE_POP_NUMBER:200]
[RELIGION:PANTHEON]
[RELIGION_SPHERE:FORTRESSES]
[RELIGION_SPHERE:JEWELS]
[RELIGION_SPHERE:METALS]
[RELIGION_SPHERE:MINERALS]
[RELIGION_SPHERE:MOUNTAINS]
[RELIGION_SPHERE:WEALTH]
[RELIGION_SPHERE:NIGHT]
[RELIGION_SPHERE:WAR]
[RELIGION_SPHERE:DISEASE]
[RELIGION_SPHERE:FIRE]
[MAYOR]
[WANDERER]
[BEAST_HUNTER]
[SCOUT]
[PERMITTED_JOB:MINER]
[PERMITTED_JOB:CARPENTER]
[PERMITTED_JOB:BOWYER]
[PERMITTED_JOB:WOODCUTTER]
[PERMITTED_JOB:ENGRAVER]
[PERMITTED_JOB:MASON]
[PERMITTED_JOB:ANIMAL_CARETAKER]
[PERMITTED_JOB:ANIMAL_TRAINER]
[PERMITTED_JOB:HUNTER]
[PERMITTED_JOB:TRAPPER]
[PERMITTED_JOB:ANIMAL_DISSECTOR]
[PERMITTED_JOB:FURNACE_OPERATOR]
[PERMITTED_JOB:WEAPONSMITH]
[PERMITTED_JOB:ARMORER]
[PERMITTED_JOB:BLACKSMITH]
[PERMITTED_JOB:METALCRAFTER]
[PERMITTED_JOB:GEM_CUTTER]
[PERMITTED_JOB:GEM_SETTER]
[PERMITTED_JOB:WOODCRAFTER]
[PERMITTED_JOB:STONECRAFTER]
[PERMITTED_JOB:LEATHERWORKER]
[PERMITTED_JOB:BONE_CARVER]
[PERMITTED_JOB:WEAVER]
[PERMITTED_JOB:CLOTHIER]
[PERMITTED_JOB:GLASSMAKER]
[PERMITTED_JOB:STRAND_EXTRACTOR]
[PERMITTED_JOB:FISHERMAN]
[PERMITTED_JOB:FISH_DISSECTOR]
[PERMITTED_JOB:FISH_CLEANER]
[PERMITTED_JOB:CHEESE_MAKER]
[PERMITTED_JOB:MILKER]
[PERMITTED_JOB:COOK]
[PERMITTED_JOB:THRESHER]
[PERMITTED_JOB:MILLER]
[PERMITTED_JOB:BUTCHER]
[PERMITTED_JOB:TANNER]
[PERMITTED_JOB:DYER]
[PERMITTED_JOB:PLANTER]
[PERMITTED_JOB:HERBALIST]
[PERMITTED_JOB:BREWER]
[PERMITTED_JOB:SOAP_MAKER]
[PERMITTED_JOB:POTASH_MAKER]
[PERMITTED_JOB:LYE_MAKER]
[PERMITTED_JOB:WOOD_BURNER]
[PERMITTED_JOB:MECHANIC]
[PERMITTED_JOB:SIEGE_ENGINEER]
[PERMITTED_JOB:SIEGE_OPERATOR]
[PERMITTED_JOB:PUMP_OPERATOR]
[PERMITTED_JOB:CLERK]
[PERMITTED_JOB:ADMINISTRATOR]
[PERMITTED_JOB:TRADER]
[PERMITTED_JOB:ARCHITECT]
[WORLD_CONSTRUCTION:TUNNEL]
[WORLD_CONSTRUCTION:BRIDGE]
[WORLD_CONSTRUCTION:ROAD]
[ETHIC:KILL_ENTITY_MEMBER:PUNISH_CAPITAL]
[ETHIC:KILL_NEUTRAL:ACCEPTABLE]
[ETHIC:KILL_ENEMY:ACCEPTABLE]
[ETHIC:KILL_ANIMAL:ACCEPTABLE]
[ETHIC:KILL_PLANT:ACCEPTABLE]
[ETHIC:TORTURE_AS_EXAMPLE:ACCEPTABLE]
[ETHIC:TORTURE_FOR_INFORMATION:ACCEPTABLE]
[ETHIC:TORTURE_FOR_FUN:PERSONAL_MATTER]
[ETHIC:TORTURE_ANIMALS:ACCEPTABLE]
[ETHIC:TREASON:PUNISH_CAPITAL]
[ETHIC:OATH_BREAKING:PUNISH_CAPITAL]
[ETHIC:LYING:PERSONAL_MATTER]
[ETHIC:VANDALISM:ACCEPTABLE]
[ETHIC:TRESPASSING:PUNISH_SERIOUS]
[ETHIC:THEFT:PUNISH_SERIOUS]
[ETHIC:ASSAULT:PUNISH_SERIOUS]
[ETHIC:SLAVERY:ACCEPTABLE]
[ETHIC:EAT_SAPIENT_OTHER:ACCEPTABLE]
[ETHIC:EAT_SAPIENT_KILL:ACCEPTABLE]
[ETHIC:MAKE_TROPHY_SAME_RACE:ACCEPTABLE]
[ETHIC:MAKE_TROPHY_SAPIENT:ACCEPTABLE]
[ETHIC:MAKE_TROPHY_ANIMAL:ACCEPTABLE]
[WILL_ACCEPT_TRIBUTE]

The fun part is that your dark dwarves will, thanks to the specified symbols, have some crazy names that you'd never see with regular dwarves (one of the fortresses it generated was called "Crowanus", for example). If you dislike having bad language, just remove the [SELECT_SYMBOL:ALL:UNTOWARD].

The main differences you'll see here compared to the dwarf entry is that they have different weapons, toys, instruments (thanks to their warlike nature, they build less of them) and [USE_EVIL_ANIMALS] is turned on: this will do nothing in dwarf fort mode but you'll see tamed trolls and ogres in their fortresses in adventurer mode. Many of their other tokens are changed as well, to make them more violent and evil. For example, they will eat their foes like elves do. Yum!

Now, we need to build the DARK_DWARF creature. Create a new text file called 'creature_new.txt'. Immediately, add the following:

creature_new

[OBJECT:CREATURE]

That'll make this text file recognized as a creature file. Now, we simply add our dark_dwarf creature:

[CREATURE:DARK_DWARF]
[NAME:dark dwarf:dark dwarves:dark dwarven]
[TILE:1][COLOR:3:0:0]
[GENPOWER:3]
[INTELLIGENT]
[TRANCES]
[EVIL]
[CANOPENDOORS]
[PREFSTRING:beards]
[PREFSTRING:violent tempers]
[PREFSTRING:sullying of the dead]
[BODY:HUMANOID:2EYES:2EARS:NOSE:2LUNGS:HEART:GUTS:ORGANS:HUMANOID_JOINTS:THROAT:NECK:SPINE:BRAIN:5FINGERS:5TOES:MOUTH]
[STOUT]
[MAXAGE:250:270]
[ATTACK:MAIN:BYTYPE:GRASP:punch:punches:1:2:BLUDGEON][ATTACKFLAG_WITH]
[ATTACK:SECOND:BYTYPE:MOUTH:bite:bites:1:1:GORE][ATTACKFLAG_CANLATCH]
[CHILD:12][BABY:1][MULTIPLE_LITTER_RARE]
[DAMBLOCK:1]
[FAT:3]
[SIZE:6]
[EQUIPS]
[CAVE_ADAPT]
[NOCTURNAL]
[CRAFTSMAN_NAME:craftsdwarf:craftsdwarves]
[FISHERMAN_NAME:fisherdwarf:fisherdwarves]
[HAMMERMAN_NAME:hammerdwarf:hammerdwarves]
[SPEARMAN_NAME:speardwarf:speardwarves]
[CROSSBOWMAN_NAME:marksdwarf:marksdwarves]
[AXEMAN_NAME:axedwarf:axedwarves]
[SWORDSMAN_NAME:swordsdwarf:swordsdwarves]
[MACEMAN_NAME:macedwarf:macedwarves]
[PIKEMAN_NAME:pikedwarf:pikedwarves]
[BOWMAN_NAME:bowdwarf:bowdwarves]
[SPEECH:dwarf.txt]
[STANDARD_FLESH]
[HOMEOTHERM:10067]
[LAYERING:50]
[SWIMS_LEARNED][SWIM_SPEED:2500]
[PERSONALITY:ANGER:25:75:100]
[PERSONALITY:IMMODERATION:0:75:100]
[PERSONALITY:EXCITEMENT_SEEKING:0:60:100]
[PERSONALITY:CHEERFULNESS:0:10:90]
[PERSONALITY:ALTRUISM:0:25:50]
[PERSONALITY:MODESTY:0:20:90]
[PERSONALITY:SYMPATHY:0:25:50]
[PERSONALITY:VULNERABILITY:0:25:100]
[PERSONALITY:STRAIGHTFORWARDNESS:25:65:100]
[PERSONALITY:SELF_DISCIPLINE:30:75:100]

This is largely a copy of the regular dwarves, but with several differences: [LIKES_FIGHTING] will give them happy thoughts when they have fought something, [NOCTURNAL] means they like nights rather than days, and [EVIL] means on the adventurer map their fortresses will tend to end up on evil tiles rather than good ones. Otherwise, they are exactly the same as regular dwarves. To make them extra evil, add [BONECARN] somewhere in there and they can eat bones (they'll actually haul them from your refuse pit to the dining table, yum), but will sometimes (though rarely) choke to death on them. Bear in mind that [BONECARN] implies [CARNIVORE], so they won't eat vegetables making the game much harder. Also, they do not require booze to stay happy (though will happily drink it anyway if they have to).

There! That's all we need to do in order to add our civilization. Just create a new world and they'll be there: however, when you go to adventurer mode, all (or none) of your dwarf entries might be replaced with dark dwarves, so it's really a matter of luck. When you start a new fortress, there will be a 50-50 chance of playing either as dwarves or dark dwarves. The easiest way to tell if a civ is a dark dwarven is if the name is rather unpleasant. 'The Fortress of Rapes' for example would probably not be a standard dwarven one. Remove [CIV_CONTROLLABLE] from the standard dwarves if you only want to play as dark.

== Example two: "Arachnid" playable creature ==

This time, we're going to add a new playable creature to adventurer mode, but not playable in fortress mode. An 'arachnid' is a large, powerful, evil half-elf, half-spider (no copyright violations here!): they are too big to wear standard equipment and are quite nasty enough without it anyway. The downside to playing them is that since they do not form standard civilizations, you cannot start them at a specific location nor will they have any weapon, armor, or [[wrestling]] skills to start out.

First off, we need to add a civilization entry in entity_default.txt. Open it up and add this to the top of the file:

[ENTITY:ARACHNIDS]
[MOUNTAIN_SETTLEMENTS]
[CREATURE:ARACHNID]
[INDIV_CONTROLLABLE]
[ADVENTURE_TIER:4]
Note: adventure_tier should be 5 if you also have the dark dwarves.
[TRANSLATION:ELF]
[BIOME_SUPPORT:ANY_WETLAND:2]
[BIOME_SUPPORT:ANY_DESERT:3]
[BIOME_SUPPORT:ANY_FOREST:1]
[BIOME_SUPPORT:MOUNTAIN:4]
[BIOME_SUPPORT:ANY_GRASSLAND:1]
[BIOME_SUPPORT:ANY_SAVANNA:1]
[BIOME_SUPPORT:ANY_SHRUBLAND:1]
[BIOME_SUPPORT:ANY_RIVER:2]
[START_BIOME:MOUNTAIN]
[SELECT_SYMBOL:ALL:EVIL]
[SELECT_SYMBOL:ALL:VIOLENT]
[SELECT_SYMBOL:ALL:DEATH]
[SELECT_SYMBOL:ALL:UNTOWARD]
[CULL_SYMBOL:ALL:DOMESTIC]
[CULL_SYMBOL:ALL:FLOWERY]
[CULL_SYMBOL:ALL:HOLY]
[CULL_SYMBOL:ALL:PEACE]
[CULL_SYMBOL:ALL:NEGATOR]
[CULL_SYMBOL:ALL:GOOD]
[FRIENDLY_COLOR:7:0:0]
[DEFAULT_SITE_TYPE:CAVE]
[LIKES_SITE:CAVE]
[TOLERATES_SITE:CAVE]
[ACTIVE_SEASON:SPRING]
[ACTIVE_SEASON:SUMMER]
[ACTIVE_SEASON:AUTUMN]
[ACTIVE_SEASON:WINTER]
[MAX_STARTING_CIV_NUMBER:2]
[START_GROUP_NUMBER:1]
[MAX_POP_NUMBER:500]
[MAX_SITE_POP_NUMBER:20]
[ETHIC:KILL_ENTITY_MEMBER:ACCEPTABLE]
[ETHIC:KILL_NEUTRAL:ACCEPTABLE]
[ETHIC:KILL_ENEMY:ACCEPTABLE]
[ETHIC:KILL_ANIMAL:ACCEPTABLE]
[ETHIC:KILL_PLANT:ACCEPTABLE]
[ETHIC:TORTURE_AS_EXAMPLE:ACCEPTABLE]
[ETHIC:TORTURE_FOR_INFORMATION:ACCEPTABLE]
[ETHIC:TORTURE_FOR_FUN:ACCEPTABLE]
[ETHIC:TORTURE_ANIMALS:ACCEPTABLE]
[ETHIC:TREASON:ACCEPTABLE]
[ETHIC:OATH_BREAKING:ACCEPTABLE]
[ETHIC:LYING:ACCEPTABLE]
[ETHIC:VANDALISM:ACCEPTABLE]
[ETHIC:TRESPASSING:NOT_APPLICABLE]
[ETHIC:THEFT:NOT_APPLICABLE]
[ETHIC:ASSAULT:ACCEPTABLE]
[ETHIC:SLAVERY:UNTHINKABLE]
[ETHIC:EAT_SAPIENT_OTHER:ACCEPTABLE]
[ETHIC:EAT_SAPIENT_KILL:ACCEPTABLE]
[ETHIC:MAKE_TROPHY_SAME_RACE:ACCEPTABLE]
[ETHIC:MAKE_TROPHY_SAPIENT:ACCEPTABLE]
[ETHIC:MAKE_TROPHY_ANIMAL:ACCEPTABLE]

INDIV_CONTROLLABLE and ADVENTURE_TIER tokens allows us to use ARACHNID: PLAY NOW! in adventurer mode, which is exactly what we want. They'll be powerful enough to use without gear anyhow.

Next, we open up creature_new.txt (if you haven't made one, check the above example) and add the new creature to it:

[CREATURE:ARACHNID]
[NAME:arachnid:arachnids:arachnid]
[TILE:'&'][COLOR:7:0:0]
[MODVALUE:20][SEMIMEGABEAST]
[INTELLIGENT][CANOPENDOORS]
[LARGE_CHASM][FREQUENCY:1][DIFFICULTY:4]
[SPEED:700]
[STOUT]
[EXTRACT:arachnid venom:7:0:0]
[EXTRACT_VALUE:500]
[EXTRACT_PARALYZE][NATURAL][PET_EXOTIC]
[EXTRACT_ANTIDOTE:arachnid antivenin:7:0:0:100]
[WEBIMMUNE][AMBUSHPREDATOR][PARALYZEIMMUNE]
[GENPOWER:4]
[BLOODTYPE:W][CHITIN]
[PETVALUE:2500]
[GRASSTRAMPLE:10]
[CARNIVORE][BONECARN]
[EXTRAVISION][NOSTUN][NOEXERT][NOFEAR]
[BUILDINGDESTROYER:1]
[PREFSTRING:terrifying presence]
[PREFSTRING:fearsome venom]
[BODY:ARACHNOBODY:8EYES:2EARS:NOSE:2LUNGS:HEART:GUTS:ORGANS:THROAT:NECK:SPINE:BRAIN:MOUTH:5FINGERS]
[SIZE:15]
[MAXAGE:20:30]
[ATTACK:MAIN:BYTYPE:MOUTH:bite:bites:1:6:GORE][SPECIALATTACK_INJECT_EXTRACT:50:100]
[ATTACK:SECOND:BYTYPE:GRASP:punch:punches:1:2:BLUDGEON][ATTACKFLAG_WITH]
[FAT:2]
[CHILD:30][BABY:1][MULTIPLE_LITTER_RARE]
[DAMBLOCK:10]
[ALL_ACTIVE][CAVE_ADAPT]
[STANDARD_FLESH]
[HOMEOTHERM:10067]
[LAYERING:50]
[SWIMS_LEARNED][SWIM_SPEED:2500]
[MUNDANE]

Now, what does this all mean, exactly? Well, compared to dwarves they are big, bad, as fast as elves, as sturdy as dwarves (hard to knock over), they have white blood, can eat bones, are immune to fear, stun, and never get tired, see twice as far, and are almost totally immune to most small-damage attacks. In addition I copied the giant cave spider paralyzing bite attack, so when you bite and hit, you'll sometimes inject a paralyzing poison fairly often that'll knock your prey unconscious in a few combat rounds. Not only is the bite very damaging, but you can even knock out creatures like ettins or giants and rip them up as they sleep at your leisure.

However, we're not done yet. Notice the BODY: token has a few tidbits that we need to take a closer look at- 'ARACHNOBODY' and '8EYES' in particular. These are new to our species and we need to add them. So, close that and open up body_default.txt, or create your own body_something.txt file. Add the following to the bottom:

[BODY:ARACHNOBODY]
[BP:UB:upper body][UPPERBODY]
[BP:LB:abdomen][CON:UB][LOWERBODY]
[BP:HD:head][CON:UB][HEAD]
[BP:RUA:right upper arm][CON:LB][LIMB][RIGHT]
[BP:LUA:left upper arm][CON:LB][LIMB][LEFT]
[BP:RLA:right lower arm][CON:RUA][LIMB][RIGHT]
[BP:LLA:left lower arm][CON:LUA][LIMB][LEFT]
[BP:RH:right hand][CON:RLA][GRASP][RIGHT]
[BP:LH:left hand][CON:LLA][GRASP][LEFT]
[BP:RA1:right first leg][CON:LB][LIMB][RIGHT]
[BP:LA1:left first leg][CON:LB][LIMB][LEFT]
[BP:RF1:right first claw][CON:RA1][STANCE][RIGHT]
[BP:LF1:left first claw][CON:LA1][STANCE][LEFT]
[BP:RA2:right second leg][CON:LB][LIMB][RIGHT]
[BP:LA2:left second leg][CON:LB][LIMB][LEFT]
[BP:RF2:right second claw][CON:RA2][STANCE][RIGHT]
[BP:LF2:left second claw][CON:LA2][STANCE][LEFT]
[BP:RA3:right third leg][CON:LB][LIMB][RIGHT]
[BP:LA3:left third leg][CON:LB][LIMB][LEFT]
[BP:RF3:right third claw][CON:RA3][STANCE][RIGHT]
[BP:LF3:left third claw][CON:LA3][STANCE][LEFT]
[BP:RA4:right fourth leg][CON:LB][LIMB][RIGHT]
[BP:LA4:left fourth leg][CON:LB][LIMB][LEFT]
[BP:RF4:right fourth claw][CON:RA4][STANCE][RIGHT]
[BP:LF4:left fourth claw][CON:LA4][STANCE][LEFT]

[BODY:8EYES]
[BP:REYE:first eye][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL][RIGHT]
[BP:REYE:second eye][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL][RIGHT]
[BP:REYE:third eye][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL]
[BP:REYE:fourth eye][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL]
[BP:REYE:fifth eye][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL]
[BP:REYE:sixth eye][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL]
[BP:REYE:seventh eye][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL][LEFT]
[BP:LEYE:eighth eye][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL][LEFT]

Voila! Now you have your complete arachnid. They are very fun to play in adventurer mode, yet still a challenge. You can tear through unarmed civilians like a knife through butter, armed soldiers pose a minor challenge (much bigger if you are getting ganged up on), elite spearmen are devastating, and archers still rip you to shreds unless you close in on them quickly and poison them. However, thanks to your multiple eyes and legs you can take quite a few direct hits and still keep going (I once had an arrow smash straight through my head, taking out 5 eyes and wounding the throat, brains, and both ears, and survived the encounter).

In any case, you're now done! Create a new world and you will now be able to use arachnids as a playable creature in adventurer mode.

Written by Teldin.

= Modbase =

Modbase is a great tool made by Sean Mirrsen which allows you to freely swap mods and tweak game settings.
[http://www.bay12games.com/forum/index.php?topic=18623.0 Get it now!]
For version 0.38c.

[[Category:Modding]]
[[Category:Guides]]

40d:Modding guide

2009-03-19T01:37:45Z

Adeptable: grammar

This is intended to be an easy guide for general newbies on how to both edit and add civilizations, creatures, objects, and so on in Dwarf Fortress, both [[Adventure_Mode|adventurer]] and [[Dwarf_Fortress_Mode|fortress]] modes, without breaking anything too much. Generally breaking stuff is fine! Just always back up your work & the originals, and be patient at having to [[World_Generation|generate new worlds]] over and over.

This guide was edited for version 0.27.176.39c and may not be accurate for later versions, particularly the examples.

= Modding Guide =

== Basics of DF modding ==

All of the data you can edit are stored in the \raw\ folder wherever you saved your DF executable. The raw folder contains two subfolders: graphics (where you insert [[Object_Tilesets|graphic packs]] to make custom tiles), and objects, which contains all the data for generally everything in the game that is not hardcoded. Quite a lot is not hardcoded, so you can edit a wide variety of things in the game.

Editing the [[Raw file|raw text files]] is easy and simple. When you go into the \raw\objects folder you will see a wide variety of text files. When you are modding your game, you can either change existing files or add your own. I personally find it easier just to edit the existing ones in a new \DF\ game folder. When you are changing a token you can simply change the values - these are the numbers/strings after the : in a token entry. For example, [CREATURE:DWARF] is a token in the entity text file, which determines what creatures are used for dwarven civilizations. Simply open the text file, edit what you want, save and close, and generate a new world after you're done editing what you want.

Essentially, everything that can be modded uses text files to determine how they interact with the world or with other objects. With a bit of know-how you can tinker with just about everything.

Every text file uses what are called "tokens", also called "flags". They are essentially attributes that you can add or remove or edit for any particular object in the game, that change the way the object works or acts. Most of the actual effects are hardcoded: for example, giving a creature such as a moose the [EVIL] creature token will make it only appear in evil maps, or giving it [BONECARN] will make it chow down on bones.

A few key things to remember when modding the text files:

* Always back up the default text files you plan on editing. This way, if your game crashes (due to say, a typo that you can't find) you can simply copy-paste it back in for a 'vanilla' DF.
* You do not need to delete old saves; simply create a new world using your modded files and things should run just fine. Just don't try to play a "non-modded" world with modded files! Should you desire to go back to your old sites, just make sure you revert to the raw files used for the creation of that world.
* In general it's better to make whole new text files for new stuff you're adding rather than editing the existing ones by tagging them onto the bottom. This allows you to keep track of them easier and keeps them all in one place so there's less messing about with tons of files.
* The absolute easiest way to add an entirely new creature/entity/etc is to simply copy-paste an existing one and rename it, then edit the various tokens appropriately.

In addition, if you ''rename'' the any of the \raw\ files themselves (such as 'creature_insects.txt' to 'creature_bugs.txt'), you must find the same filename in the \data\objects\ folder and delete it. This is required because once the world is generated it creates the new files and saves them for use next time the world is needed; without deleting the file you will get duplication errors. This is not necessary if you just don't change any of the filenames.

== Modding the civilizations ==

The civilization entries are stored in entity_default.txt. They are quite simple files that are in the following format:

[ENTITY:ENTITYNAME]
[CREATURE:CREATURETYPE]
[TRANSLATION:LANGUAGETYPE]
[BIOME_SUPPORT:BIOMETOKEN:FREQENCY]
...[OTHER TAGS]...

At the top of the file you'll see an 'entity_default' all by itself, that must be at the top of the file only. All game files require those markers at the top. If you're creating a new civilization in its own text file, be sure to add entity_default, and [OBJECT:ENTITY] at the top of the file.

Now what do these tokens mean, exactly? For one, where the tags are located don't generally matter quite a lot. You can add them in any order as long as they're underneath the "[ENTITY:]" token, which is the 'header' of the civilization and lets the game know that everything underneath deals with that civ. The entity token can be anything as long as it's not the same as another one.

'[CREATURE:]' links the civilization with a certain creature defined in a different file. This is the creature you play in adventurer or fortress mode, or that wanders around their towns when you explore them. For example, if you wanted to do something silly you could switch the "DWARF" entry in entity_default.txt with "ELF" and you would be marching elves around in fortress mode, though they would still use dwarven technology and language and names and so forth.

'[TRANSLATION:]' connects the civ to a specific language file that determines things like their natural (untranslated) creature first + last names and city names. The valid ones are HUMAN, DWARF, ELF, and GOBLIN.

'[BIOME_SUPPORT:]' defines biomes that civs will appear in. The 'FREQUENCY' value determines the likelyhood of them appearing there: generally 1 for not very often, up to 3 for very often (ie. dwarves in mountains).

You can find many details about the rest of the civilization tokens [[Entity_Tokens|here]]. The important ones are the CIV_CONTROLLABLE token, which lets you control the civ in dwarf fortress mode and the INDIV_CONTROLLABLE and ADVENTURE_TIER tokens which lets you play the civ in adventure mode via the PLAY NOW! command. Remember that ADVENTURE_TIER must be in order, so if you are adding a new playable race you must put it above dwarves and set its tier 1 higher (4).

If you have more than one civ with the [CIV_CONTROLLABLE] token, groups belonging to that civ will appear in the group selection section on the embark screen, although it is not immediately obvious what species each group may be. While this can be determined from legends mode, experimentation suggests that the topmost species in the 'neighbors' section of the embark screen is the same as the currently selected species: If your group is dwarven, dwarves will be topmost, whilst (say) elves will be topmost if your chosen group is elven. By default, the game seems to choose a group (and therefore a species if there is more than one) at random.

Any token that has to deal with weapons, armor, clothing, etc. are all the items that the civ can build, not necessarily the ones they can wear. For example, you could create a species with no clothes specified, but then rob a clothes shop in adventurer mode and wear everything you want, or give them weapons that are too large to wield and they could sell them, but not use them.

[SELECT_SYMBOL:] and [CULL_SYMBOL:ALL:] are the words that can be randomly generated in names, civs, cities, artifacts, engravings, etc. "SELECT_SYMBOL" means that the civ is far more likely to use those, and CULL_SYMBOL means they never will. You can find a list of every symbol type [[Language|here]]. SUBSELECT_SYMBOL:WAR/BATTLE/SIEGE just determines which language token to use when they begin wars, battles, or sieges in legends mode, ie. 'The Conflict of Craziness' or 'The Siege of Assaults'. All have these as 'violence' by default but they can be changed to any other token.

'SELECT:SYMBOL:ROAD/TUNNEL/BRIDGE/WALL' use the special language tokens NAME_ROAD, NAME_TUNNEL, etc. and determines what the civ names their structures. 'SELECT_SYMBOL:REMAINING': are the standard tokens used for the species language.

An easy method of creating a civilization is just to copy-paste a similar one to the bottom of the entity_default.txt file and edit things to your liking. Remember to always change the civ's ENTITY: name! This name can be anything as long as it's not already existing.

There are many tokens to play with in the entity file, most of which do something interesting. It's best to simply look through the entity tokens list and figure out for yourself what you want to do with them. The ones of interest are:

* [SIEGER] [BABYSNATCHER] [NUISANCE] These determine what the civ does in relation to other civs. Babysnatchers periodically swipe infants from nearby civs and have them grow up in their own civ (if kidnapped/brainwashed infants grow up and have children, their last names will use their capturer's language files: ie. you will have evil dwarves with the name Urist Deathghouls in a goblin fortress).

* [AT_PEACE_WITH_WILDLIFE] This token, currently set only on elves, will mean they will not attack wild animals and animals will not attack them. This ALSO means that if you bring an elf or two along with you in adventurer mode, don't expect them to help you if you get attacked by cougars!

* [RELIGION_SPHERE] This determines what religious deities will have as spheres when the civilization is generated, along with their subspheres. With a SPHERE_ALIGNMENT set you can also make one more likely than others; ie. Elves have trees, plants, and animals set very high so they are likely to get those more often with their deities.

* With [DEFAULT_SITE], LIKES_, and TOLERATES_ you can decide where the species will live. DEFAULT_SITE is their home cities and will usually cluster there in large groups. If a civ conquers another and they do not at least tolerate the enemy's home type they will simply destroy it instead of moving in (sometimes they will destroy it anyway).

* [ETHIC:] tokens determine how the species behaves when it comes to certain unpleasant acts. This also determines what reasons the civ will use when going to war: if a nearby civ has something set ACCEPTABLE that they consider UNTHINKABLE, then it is likely they will go to war over it. It also determines a few other things, like what happens to dead foes: Elves have '[ETHIC:EAT_SAPIENT_KILL:ACCEPTABLE]' for example. Goblins defacing their enemies (ie. hanging, stuck on pikes) is [ABUSE_BODIES], as well as ETHIC:MAKE_TROPHY_ tokens set ACCEPTABLE.

== Modding the creatures ==

Creature modding is great fun. Essentially you can change nearly any aspect of a creature or completely make your own from scratch. You can either add a new creature to the bottom of an existing creature_thing.txt file or make your own file; just be sure to add the name of the file (without the txt) to the top of it. For example, I tend to use a 'creature_newbies.txt' file myself.

Modding creatures is exactly similar to modding civs: just a matter of editing, adding, or removing tokens, enclosed in square brackets underneath the creature's [CREATURE:] header. The creature entries contain all the information about each specific creature in the game, from animals to dwarves to goblins to even caravan wagons. Much of the data of a creature is quite self-explanatory; you can find a list of every creature token [[Creature_Tokens|here]].

There're some tokens which use temperature values. Dwarf Fortress has it's own temperature scale for this. [[Temperature scale|DF temperature scale]].

Note: If you add a butcherable creature to the game such as a domestic animal, people will automatically wander around wearing its fur or skin as leather items when you are in the game, assuming the creature comes from the civ's biome (natural area). So don't be surprised to see 'duck leather armor' or something if you add ducks. Also note if you add a species that has a naturally high body temperature (magma snakes for example) and set it butcherable, people will automatically be generated wearing their skins.. and then since the skins have a naturally high temperature too they tend to burst into flame immediately because they were wearing a +magma snake leather sock+. Woops.

You'll notice many of the creature entries have tokens that other ones don't have. If a token is not present it's considered "default", though sometimes the default can be hard to figure out. All of the creatures referenced in the entity files are present in creature_standard.txt and require certain other tokens that non-entity creatures do not need, such as [INTELLIGENT] and [CANOPENDOORS].

For example, if you wanted to allow your dwarves to eat bones from the refuse stockpile (ew), you would open up creature_standard.txt, add [BONECARN] somewhere in the CREATURE_DWARF: entry at the top, and then save and close it, then generate a new world. Bon appetit! *Notice that this has the unfortunate side effect of making them unable to eat plants.*

[http://www.dwarffortresswiki.net/index.php/User:Deon#How_to How to add a new creature.]

== Modding items ==

Items come in several flavors: 'crafted' items, and 'natural' items. Both are the same in most ways, but are stored in different places: most crafted item data are stored in the item_blah.txt files (such as item_armor.txt), while things like plants, gems, food, and ore are stored in "matgloss" files, ie. matgloss_plant.txt. Both are easily editable just like a creature or civ, but the problem is that there is no definitive list of what most of the tokens for these quite do yet. In any case they are usually pretty self-explanatory and you can guess what they do by checking out similar entries.

For example, let's look at the entry for, of course, the thong:

[ITEM_PANTS:ITEM_PANTS_THONG]
[NAME:thong:thongs]
[WEIGHT:10]
[VALUE:10]
[BLOCKPOWER:5]
[LAYER:UNDER]
[COVERAGE:25]
[LAYER_SIZE:10]
[LAYER_PERMIT:30]
[MATERIAL_SIZE:1]
[SOFT]
[LEATHER]

Most of these are pretty obvious if one compares them to the other entries. Now, if you wanted to mod these to turn them into metal thongs (ouch!), you would simply have to add [METAL] to it somewhere, and probably [HARD] instead of [SOFT]. Simple!

Weapons work largely the same way; but remember that in order to actually use any of these things you'd have to add the ITEM_THING item flag to the civilization's 'useable items' list in entity_default.txt. For example, if you're fond of Scots and decided to make a 'claymore' sword that's even bigger than the two-hander already in the files. It might look like this:

[ITEM_WEAPON:ITEM_WEAPON_SWORD_CLAYMORE]
[NAME:claymore sword:claymore swords]
[DAMAGE:160:SLASH]
[WEIGHT:120]
[SKILL:SWORD]
[CRIT_BOOST:1]
[TWO_HANDED:0]
[MINIMUM_SIZE:7]
[MATERIAL_SIZE:5]

Tada! Yes, it's that easy. Then you just add it to the civ entry so a civilization can actually use and craft it, and it's done.

== Modding language files ==

Let's say you added a whole new species. Sure, you could just swipe one of the existing translation files and steal their language for your species, but that's the lazy way! If you want to create a whole new language, it's very simple.

First, you'd need a whole new language_RACE file, such as language_LIZARDMAN.txt, along with "language_LIZARDMAN" at the top of the file proceeded by [OBJECT:LANGUAGE] and [TRANSLATION:LIZARDMAN]. After that, it's just a matter of copy-pasting one of the existing language lists and editing the finished 'translated' word. That's it! Then just add the translation link to your civ in entity_default.txt and it'll be added to the game on worldgen.

== Modding body parts ==

Imagine you have this fantastic idea for a multi-tentacled winged spider-monster. Sounds great! But in order to make this a reality you may need to create a new set of body parts for it. That's no problem! Making body parts is easy, though it may look complicated at first.

All body definitions are located in body_default.txt and then linked to a creature in the creature's entry. For example, the dwarf creature has: [BODY:HUMANOID:2EYES:2EARS:NOSE:2LUNGS:HEART:GUTS:ORGANS:HUMANOID_JOINTS:THROAT:NECK:SPINE:BRAIN:5FINGERS:5TOES:MOUTH]. All of these are seperate bodypart definitions in body_default.txt. You can mix and match them in the creature entry and it makes no difference, as long as they're there: each bodypart will link itself to the appropriate connection automatically when the creature is first created. This means that if you don't add the appropriate bodyparts, hilarious things can happen: if you forget to add a throat or lungs your new creature will suffocate after taking a few steps (unless you make it a nonbreather).

Body parts work by sections: you can add as many sections as you want to a bodypart definition, but generally you should keep it fairly low for ease of use. Each body section entry is in the very simple format:

[BODY:BODYNAME]
[BP:ID:name][TOKENSGOHERE]

You can add as many sub-parts as you want to an overall section. The most important tokens are 'CONTYPE' and 'CON': CONTYPE means the bodypart in question is connected to a certain *type* of bodypart, while CON means it's connected to a *specific* one. Let's break down a few entries:

[BODY:BASIC_HEAD]
[BP:HD:head][CONTYPE:UPPERBODY][HEAD]

This is a very simple one: a head. It connects directly to an upper body. All the stuff inside the head are seperate entries that call up the head as a different contype in turn:

[BODY:THROAT]
[BP:THROAT:throat][CONTYPE:HEAD][THROAT][EMBEDDED][SMALL]

The foot bone's connected to the ankle bone..

If you wanted someone to be able to break someone else's throat (like breaking a joint) and suffocate them, just add the [JOINT], [BREATHE], and possibly [NERVOUS] to the throat object's tokens.

A 'BODYGLOSS', which you can sometimes find in the creature entries, are simply replacement words for certain defined words in a creature. For example, you'll find the bodygloss [BODYGLOSS:CLAW_HAND:hand:claw] in the body_default.txt, and then you can use this in a creature with '[BODYGLOSS:CLAW_HAND]' and it will replace all instances of "hand" with "claw" in that creature. For all intent and purpose the body part will still function as the proper part, though.

Note that only creatures with the [EQUIPS] token (and possibly [INTELLIGENT]) and a civ that can create clothes/armor/weapons will be able to actually wear stuff. Also, if the creature size is too large for the clothes they will also not be able to wear it.

== Example one: dark dwarves ==

These examples will go over the details for creating several new things as well as editing some old ones.

Remember: Do NOT load an old save after genning a new world with different raws. It's much safer to simply delete all your old saves after you've modded things, or simply copy-and-paste a fresh version of DF into a new folder.

First, we're going to create a new, evil civilization of dwarves called, unsurprisingly, dark dwarves. This will be quite easy, though with a few fundamental differences. Mainly, that dark dwarves are evil and more warlike than regular dwarves.

Now, open up entity_default.txt. All your species civilizations will be in there. We're going to make a whole new one for our dark dwarves. In many ways it'll be a simple copy-paste job of regular dwarves, then tweaking some things.

Add this to the TOP of the entity_default file, before the dwarf entry:

[ENTITY:DARK_DWARF]
[CIV_CONTROLLABLE]
[CREATURE:DARK_DWARF]
[TRANSLATION:DWARF]
[DIGGER:ITEM_WEAPON_PICK]
[WEAPON:ITEM_WEAPON_AXE_BATTLE]
[WEAPON:ITEM_WEAPON_WHIP]
[WEAPON:ITEM_WEAPON_FLAIL]
[WEAPON:ITEM_WEAPON_SCOURGE]
[WEAPON:ITEM_WEAPON_DAGGER_LARGE]
[WEAPON:ITEM_WEAPON_MACE]
[WEAPON:ITEM_WEAPON_SWORD_SHORT]
[WEAPON:ITEM_WEAPON_SCIMITAR]
[WEAPON:ITEM_WEAPON_CROSSBOW]
[AMMO:ITEM_AMMO_BOLTS]
[ARMOR:ITEM_ARMOR_PLATEMAIL:COMMON]
[ARMOR:ITEM_ARMOR_CHAINMAIL:COMMON]
[ARMOR:ITEM_ARMOR_LEATHER:COMMON]
[ARMOR:ITEM_ARMOR_COAT:COMMON]
[ARMOR:ITEM_ARMOR_SHIRT:COMMON]
[ARMOR:ITEM_ARMOR_CLOAK:COMMON]
[ARMOR:ITEM_ARMOR_TOGA:UNCOMMON]
[ARMOR:ITEM_ARMOR_VEST:COMMON]
[ARMOR:ITEM_ARMOR_DRESS:COMMON]
[ARMOR:ITEM_ARMOR_ROBE:COMMON]
[HELM:ITEM_HELM_HELM:COMMON]
[HELM:ITEM_HELM_HOOD:COMMON]
[GLOVES:ITEM_GLOVES_GAUNTLETS:COMMON]
[GLOVES:ITEM_GLOVES_GLOVES:COMMON]
[SHOES:ITEM_SHOES_SHOES:COMMON]
[SHOES:ITEM_SHOES_BOOTS:COMMON]
[SHOES:ITEM_SHOES_BOOTS_LOW:COMMON]
[PANTS:ITEM_PANTS_PANTS:COMMON]
[PANTS:ITEM_PANTS_GREAVES:COMMON]
[PANTS:ITEM_PANTS_LEGGINGS:COMMON]
[SHIELD:ITEM_SHIELD_SHIELD]
[SHIELD:ITEM_SHIELD_BUCKLER]
[SIEGEAMMO:ITEM_SIEGEAMMO_BALLISTA]
[TRAPCOMP:ITEM_TRAPCOMP_GIANTAXEBLADE]
[TRAPCOMP:ITEM_TRAPCOMP_ENORMOUSCORKSCREW]
[TRAPCOMP:ITEM_TRAPCOMP_SPIKEDBALL]
[TRAPCOMP:ITEM_TRAPCOMP_LARGESERRATEDDISC]
[TOY:ITEM_TOY_HAMMER]
[TOY:ITEM_TOY_AXE]
[TOY:ITEM_TOY_MINIFORGE]
[INSTRUMENT:ITEM_INSTRUMENT_TRUMPET]
[INSTRUMENT:ITEM_INSTRUMENT_DRUM]
[CLOTHING]
[SUBTERRANEAN_CLOTHING]
[CURRENCY_BY_YEAR]
[CURRENCY:COPPER:1]
[CURRENCY:SILVER:5]
[CURRENCY:GOLD:15]
[SELECT_SYMBOL:WAR:NAME_WAR]
[SUBSELECT_SYMBOL:WAR:VIOLENT]
[SELECT_SYMBOL:BATTLE:NAME_BATTLE]
[SUBSELECT_SYMBOL:BATTLE:VIOLENT]
[SELECT_SYMBOL:SIEGE:NAME_SIEGE]
[SUBSELECT_SYMBOL:SIEGE:VIOLENT]
[SELECT_SYMBOL:ROAD:NAME_ROAD]
[SELECT_SYMBOL:TUNNEL:NAME_TUNNEL]
[SELECT_SYMBOL:BRIDGE:NAME_BRIDGE]
[SELECT_SYMBOL:WALL:NAME_WALL]
[SELECT_SYMBOL:REMAINING:ARTIFICE]
[SELECT_SYMBOL:REMAINING:EARTH]
[SELECT_SYMBOL:REMAINING:EVIL]
[SELECT_SYMBOL:REMAINING:UNTOWARD]
[SELECT_SYMBOL:REMAINING:UGLY]
[SELECT_SYMBOL:REMAINING:EARTH]
[CULL_SYMBOL:ALL:DOMESTIC]
[CULL_SYMBOL:ALL:FLOWERY]
[CULL_SYMBOL:ALL:HOLY]
[CULL_SYMBOL:ALL:PEACE]
[CULL_SYMBOL:ALL:NEGATOR]
[CULL_SYMBOL:ALL:GOOD]
[METAL_PREF]
[GEM_PREF]
[STONE_PREF]
[INDOOR_FARMING]
[USE_CAVE_ANIMALS]
[USE_ANIMAL_PRODUCTS]
[USE_EVIL_ANIMALS]
[USE_EVIL_PLANTS]
[USE_EVIL_WOOD]
[COMMON_DOMESTIC_PACK]
[COMMON_DOMESTIC_PULL]
[COMMON_DOMESTIC_MOUNT]
[COMMON_DOMESTIC_PET]
[USE_MISC_PROCESSED_WOOD_PRODUCTS]
[EQUIPMENT_IMPROVEMENTS]
[ART_FACET_MODIFIER:GOOD:0]
[ART_FACET_MODIFIER:EVIL:512]
[ITEM_IMPROVEMENT_MODIFIER:RINGS_HANGING:0]
[ITEM_IMPROVEMENT_MODIFIER:BANDS:0]
[ITEM_IMPROVEMENT_MODIFIER:SPIKES:384]
[ADVENTURE_TIER:4]
[FRIENDLY_COLOR:1:0:1]
[DEFAULT_SITE_TYPE:CAVE_DETAILED]
[LIKES_SITE:CAVE_DETAILED]
[TOLERATES_SITE:CITY]
[TOLERATES_SITE:TREE_CITY]
[TOLERATES_SITE:CAVE_DETAILED]
[TOLERATES_SITE:CAVE]
[LEADER_TYPE:KING]
[SITE_LEADER_TYPE:STANDARD]
[START_BIOME:MOUNTAIN]
[BIOME_SUPPORT:ANY_WETLAND:1]
[BIOME_SUPPORT:ANY_DESERT:1]
[BIOME_SUPPORT:ANY_OCEAN:1]
[BIOME_SUPPORT:ANY_LAKE:1]
[BIOME_SUPPORT:MOUNTAIN:3]
[BIOME_SUPPORT:ANY_GRASSLAND:1]
[BIOME_SUPPORT:ANY_SAVANNA:1]
[BIOME_SUPPORT:ANY_SHRUBLAND:1]
[BIOME_SUPPORT:ANY_RIVER:1]
[DIPLOMAT]
[DIPLOMAT_BODYGUARDS]
[MERCHANT_BODYGUARDS]
[ACTIVE_SEASON:WINTER]
[SIEGER]
[MAX_STARTING_CIV_NUMBER:3]
[START_GROUP_NUMBER:10]
[MAX_POP_NUMBER:10000]
[MAX_SITE_POP_NUMBER:200]
[RELIGION:PANTHEON]
[RELIGION_SPHERE:FORTRESSES]
[RELIGION_SPHERE:JEWELS]
[RELIGION_SPHERE:METALS]
[RELIGION_SPHERE:MINERALS]
[RELIGION_SPHERE:MOUNTAINS]
[RELIGION_SPHERE:WEALTH]
[RELIGION_SPHERE:NIGHT]
[RELIGION_SPHERE:WAR]
[RELIGION_SPHERE:DISEASE]
[RELIGION_SPHERE:FIRE]
[MAYOR]
[WANDERER]
[BEAST_HUNTER]
[SCOUT]
[PERMITTED_JOB:MINER]
[PERMITTED_JOB:CARPENTER]
[PERMITTED_JOB:BOWYER]
[PERMITTED_JOB:WOODCUTTER]
[PERMITTED_JOB:ENGRAVER]
[PERMITTED_JOB:MASON]
[PERMITTED_JOB:ANIMAL_CARETAKER]
[PERMITTED_JOB:ANIMAL_TRAINER]
[PERMITTED_JOB:HUNTER]
[PERMITTED_JOB:TRAPPER]
[PERMITTED_JOB:ANIMAL_DISSECTOR]
[PERMITTED_JOB:FURNACE_OPERATOR]
[PERMITTED_JOB:WEAPONSMITH]
[PERMITTED_JOB:ARMORER]
[PERMITTED_JOB:BLACKSMITH]
[PERMITTED_JOB:METALCRAFTER]
[PERMITTED_JOB:GEM_CUTTER]
[PERMITTED_JOB:GEM_SETTER]
[PERMITTED_JOB:WOODCRAFTER]
[PERMITTED_JOB:STONECRAFTER]
[PERMITTED_JOB:LEATHERWORKER]
[PERMITTED_JOB:BONE_CARVER]
[PERMITTED_JOB:WEAVER]
[PERMITTED_JOB:CLOTHIER]
[PERMITTED_JOB:GLASSMAKER]
[PERMITTED_JOB:STRAND_EXTRACTOR]
[PERMITTED_JOB:FISHERMAN]
[PERMITTED_JOB:FISH_DISSECTOR]
[PERMITTED_JOB:FISH_CLEANER]
[PERMITTED_JOB:CHEESE_MAKER]
[PERMITTED_JOB:MILKER]
[PERMITTED_JOB:COOK]
[PERMITTED_JOB:THRESHER]
[PERMITTED_JOB:MILLER]
[PERMITTED_JOB:BUTCHER]
[PERMITTED_JOB:TANNER]
[PERMITTED_JOB:DYER]
[PERMITTED_JOB:PLANTER]
[PERMITTED_JOB:HERBALIST]
[PERMITTED_JOB:BREWER]
[PERMITTED_JOB:SOAP_MAKER]
[PERMITTED_JOB:POTASH_MAKER]
[PERMITTED_JOB:LYE_MAKER]
[PERMITTED_JOB:WOOD_BURNER]
[PERMITTED_JOB:MECHANIC]
[PERMITTED_JOB:SIEGE_ENGINEER]
[PERMITTED_JOB:SIEGE_OPERATOR]
[PERMITTED_JOB:PUMP_OPERATOR]
[PERMITTED_JOB:CLERK]
[PERMITTED_JOB:ADMINISTRATOR]
[PERMITTED_JOB:TRADER]
[PERMITTED_JOB:ARCHITECT]
[WORLD_CONSTRUCTION:TUNNEL]
[WORLD_CONSTRUCTION:BRIDGE]
[WORLD_CONSTRUCTION:ROAD]
[ETHIC:KILL_ENTITY_MEMBER:PUNISH_CAPITAL]
[ETHIC:KILL_NEUTRAL:ACCEPTABLE]
[ETHIC:KILL_ENEMY:ACCEPTABLE]
[ETHIC:KILL_ANIMAL:ACCEPTABLE]
[ETHIC:KILL_PLANT:ACCEPTABLE]
[ETHIC:TORTURE_AS_EXAMPLE:ACCEPTABLE]
[ETHIC:TORTURE_FOR_INFORMATION:ACCEPTABLE]
[ETHIC:TORTURE_FOR_FUN:PERSONAL_MATTER]
[ETHIC:TORTURE_ANIMALS:ACCEPTABLE]
[ETHIC:TREASON:PUNISH_CAPITAL]
[ETHIC:OATH_BREAKING:PUNISH_CAPITAL]
[ETHIC:LYING:PERSONAL_MATTER]
[ETHIC:VANDALISM:ACCEPTABLE]
[ETHIC:TRESPASSING:PUNISH_SERIOUS]
[ETHIC:THEFT:PUNISH_SERIOUS]
[ETHIC:ASSAULT:PUNISH_SERIOUS]
[ETHIC:SLAVERY:ACCEPTABLE]
[ETHIC:EAT_SAPIENT_OTHER:ACCEPTABLE]
[ETHIC:EAT_SAPIENT_KILL:ACCEPTABLE]
[ETHIC:MAKE_TROPHY_SAME_RACE:ACCEPTABLE]
[ETHIC:MAKE_TROPHY_SAPIENT:ACCEPTABLE]
[ETHIC:MAKE_TROPHY_ANIMAL:ACCEPTABLE]
[WILL_ACCEPT_TRIBUTE]

The fun part is that your dark dwarves will, thanks to the specified symbols, have some crazy names that you'd never see with regular dwarves (one of the fortresses it generated was called "Crowanus", for example). If you dislike having bad language, just remove the [SELECT_SYMBOL:ALL:UNTOWARD].

The main differences you'll see here compared to the dwarf entry is that they have different weapons, toys, instruments (thanks to their warlike nature, they build less of them) and [USE_EVIL_ANIMALS] is turned on: this will do nothing in dwarf fort mode but you'll see tamed trolls and ogres in their fortresses in adventurer mode. Many of their other tokens are changed as well, to make them more violent and evil. For example, they will eat their foes like elves do. Yum!

Now, we need to build the DARK_DWARF creature. Create a new text file called 'creature_new.txt'. Immediately, add the following:

creature_new

[OBJECT:CREATURE]

That'll make this text file recognized as a creature file. Now, we simply add our dark_dwarf creature:

[CREATURE:DARK_DWARF]
[NAME:dark dwarf:dark dwarves:dark dwarven]
[TILE:1][COLOR:3:0:0]
[GENPOWER:3]
[INTELLIGENT]
[TRANCES]
[EVIL]
[CANOPENDOORS]
[PREFSTRING:beards]
[PREFSTRING:violent tempers]
[PREFSTRING:sullying of the dead]
[BODY:HUMANOID:2EYES:2EARS:NOSE:2LUNGS:HEART:GUTS:ORGANS:HUMANOID_JOINTS:THROAT:NECK:SPINE:BRAIN:5FINGERS:5TOES:MOUTH]
[STOUT]
[MAXAGE:250:270]
[ATTACK:MAIN:BYTYPE:GRASP:punch:punches:1:2:BLUDGEON][ATTACKFLAG_WITH]
[ATTACK:SECOND:BYTYPE:MOUTH:bite:bites:1:1:GORE][ATTACKFLAG_CANLATCH]
[CHILD:12][BABY:1][MULTIPLE_LITTER_RARE]
[DAMBLOCK:1]
[FAT:3]
[SIZE:6]
[EQUIPS]
[CAVE_ADAPT]
[NOCTURNAL]
[CRAFTSMAN_NAME:craftsdwarf:craftsdwarves]
[FISHERMAN_NAME:fisherdwarf:fisherdwarves]
[HAMMERMAN_NAME:hammerdwarf:hammerdwarves]
[SPEARMAN_NAME:speardwarf:speardwarves]
[CROSSBOWMAN_NAME:marksdwarf:marksdwarves]
[AXEMAN_NAME:axedwarf:axedwarves]
[SWORDSMAN_NAME:swordsdwarf:swordsdwarves]
[MACEMAN_NAME:macedwarf:macedwarves]
[PIKEMAN_NAME:pikedwarf:pikedwarves]
[BOWMAN_NAME:bowdwarf:bowdwarves]
[SPEECH:dwarf.txt]
[STANDARD_FLESH]
[HOMEOTHERM:10067]
[LAYERING:50]
[SWIMS_LEARNED][SWIM_SPEED:2500]
[PERSONALITY:ANGER:25:75:100]
[PERSONALITY:IMMODERATION:0:75:100]
[PERSONALITY:EXCITEMENT_SEEKING:0:60:100]
[PERSONALITY:CHEERFULNESS:0:10:90]
[PERSONALITY:ALTRUISM:0:25:50]
[PERSONALITY:MODESTY:0:20:90]
[PERSONALITY:SYMPATHY:0:25:50]
[PERSONALITY:VULNERABILITY:0:25:100]
[PERSONALITY:STRAIGHTFORWARDNESS:25:65:100]
[PERSONALITY:SELF_DISCIPLINE:30:75:100]

This is largely a copy of the regular dwarves, but with several differences: [LIKES_FIGHTING] will give them happy thoughts when they have fought something, [NOCTURNAL] means they like nights rather than days, and [EVIL] means on the adventurer map their fortresses will tend to end up on evil tiles rather than good ones. Otherwise, they are exactly the same as regular dwarves. To make them extra evil, add [BONECARN] somewhere in there and they can eat bones (they'll actually haul them from your refuse pit to the dining table, yum), but will sometimes (though rarely) choke to death on them. Bear in mind that [BONECARN] implies [CARNIVORE], so they won't eat vegetables making the game much harder. Also, they do not require booze to stay happy (though will happily drink it anyway if they have to).

There! That's all we need to do in order to add our civilization. Just create a new world and they'll be there: however, when you go to adventurer mode, all (or none) of your dwarf entries might be replaced with dark dwarves, so it's really a matter of luck. When you start a new fortress, there will be a 50-50 chance of playing either as dwarves or dark dwarves. The easiest way to tell if a civ is a dark dwarven is if the name is rather unpleasant. 'The Fortress of Rapes' for example would probably not be a standard dwarven one. Remove [CIV_CONTROLLABLE] from the standard dwarves if you only want to play as dark.

== Example two: "Arachnid" playable creature ==

This time, we're going to add a new playable creature to adventurer mode, but not playable in fortress mode. An 'arachnid' is a large, powerful, evil half-elf, half-spider (no copyright violations here!): they are too big to wear standard equipment and are quite nasty enough without it anyway. The downside to playing them is that since they do not form standard civilizations, you cannot start them at a specific location nor will they have any weapon, armor, or [[wrestling]] skills to start out.

First off, we need to add a civilization entry in entity_default.txt. Open it up and add this to the top of the file:

[ENTITY:ARACHNIDS]
[MOUNTAIN_SETTLEMENTS]
[CREATURE:ARACHNID]
[INDIV_CONTROLLABLE]
[ADVENTURE_TIER:4]
Note: adventure_tier should be 5 if you also have the dark dwarves.
[TRANSLATION:ELF]
[BIOME_SUPPORT:ANY_WETLAND:2]
[BIOME_SUPPORT:ANY_DESERT:3]
[BIOME_SUPPORT:ANY_FOREST:1]
[BIOME_SUPPORT:MOUNTAIN:4]
[BIOME_SUPPORT:ANY_GRASSLAND:1]
[BIOME_SUPPORT:ANY_SAVANNA:1]
[BIOME_SUPPORT:ANY_SHRUBLAND:1]
[BIOME_SUPPORT:ANY_RIVER:2]
[START_BIOME:MOUNTAIN]
[SELECT_SYMBOL:ALL:EVIL]
[SELECT_SYMBOL:ALL:VIOLENT]
[SELECT_SYMBOL:ALL:DEATH]
[SELECT_SYMBOL:ALL:UNTOWARD]
[CULL_SYMBOL:ALL:DOMESTIC]
[CULL_SYMBOL:ALL:FLOWERY]
[CULL_SYMBOL:ALL:HOLY]
[CULL_SYMBOL:ALL:PEACE]
[CULL_SYMBOL:ALL:NEGATOR]
[CULL_SYMBOL:ALL:GOOD]
[FRIENDLY_COLOR:7:0:0]
[DEFAULT_SITE_TYPE:CAVE]
[LIKES_SITE:CAVE]
[TOLERATES_SITE:CAVE]
[ACTIVE_SEASON:SPRING]
[ACTIVE_SEASON:SUMMER]
[ACTIVE_SEASON:AUTUMN]
[ACTIVE_SEASON:WINTER]
[MAX_STARTING_CIV_NUMBER:2]
[START_GROUP_NUMBER:1]
[MAX_POP_NUMBER:500]
[MAX_SITE_POP_NUMBER:20]
[ETHIC:KILL_ENTITY_MEMBER:ACCEPTABLE]
[ETHIC:KILL_NEUTRAL:ACCEPTABLE]
[ETHIC:KILL_ENEMY:ACCEPTABLE]
[ETHIC:KILL_ANIMAL:ACCEPTABLE]
[ETHIC:KILL_PLANT:ACCEPTABLE]
[ETHIC:TORTURE_AS_EXAMPLE:ACCEPTABLE]
[ETHIC:TORTURE_FOR_INFORMATION:ACCEPTABLE]
[ETHIC:TORTURE_FOR_FUN:ACCEPTABLE]
[ETHIC:TORTURE_ANIMALS:ACCEPTABLE]
[ETHIC:TREASON:ACCEPTABLE]
[ETHIC:OATH_BREAKING:ACCEPTABLE]
[ETHIC:LYING:ACCEPTABLE]
[ETHIC:VANDALISM:ACCEPTABLE]
[ETHIC:TRESPASSING:NOT_APPLICABLE]
[ETHIC:THEFT:NOT_APPLICABLE]
[ETHIC:ASSAULT:ACCEPTABLE]
[ETHIC:SLAVERY:UNTHINKABLE]
[ETHIC:EAT_SAPIENT_OTHER:ACCEPTABLE]
[ETHIC:EAT_SAPIENT_KILL:ACCEPTABLE]
[ETHIC:MAKE_TROPHY_SAME_RACE:ACCEPTABLE]
[ETHIC:MAKE_TROPHY_SAPIENT:ACCEPTABLE]
[ETHIC:MAKE_TROPHY_ANIMAL:ACCEPTABLE]

INDIV_CONTROLLABLE and ADVENTURE_TIER tokens allows us to use ARACHNID: PLAY NOW! in adventurer mode, which is exactly what we want. They'll be powerful enough to use without gear anyhow.

Next, we open up creature_new.txt (if you haven't made one, check the above example) and add the new creature to it:

[CREATURE:ARACHNID]
[NAME:arachnid:arachnids:arachnid]
[TILE:'&'][COLOR:7:0:0]
[MODVALUE:20][SEMIMEGABEAST]
[INTELLIGENT][CANOPENDOORS]
[LARGE_CHASM][FREQUENCY:1][DIFFICULTY:4]
[SPEED:700]
[STOUT]
[EXTRACT:arachnid venom:7:0:0]
[EXTRACT_VALUE:500]
[EXTRACT_PARALYZE][NATURAL][PET_EXOTIC]
[EXTRACT_ANTIDOTE:arachnid antivenin:7:0:0:100]
[WEBIMMUNE][AMBUSHPREDATOR][PARALYZEIMMUNE]
[GENPOWER:4]
[BLOODTYPE:W][CHITIN]
[PETVALUE:2500]
[GRASSTRAMPLE:10]
[CARNIVORE][BONECARN]
[EXTRAVISION][NOSTUN][NOEXERT][NOFEAR]
[BUILDINGDESTROYER:1]
[PREFSTRING:terrifying presence]
[PREFSTRING:fearsome venom]
[BODY:ARACHNOBODY:8EYES:2EARS:NOSE:2LUNGS:HEART:GUTS:ORGANS:THROAT:NECK:SPINE:BRAIN:MOUTH:5FINGERS]
[SIZE:15]
[MAXAGE:20:30]
[ATTACK:MAIN:BYTYPE:MOUTH:bite:bites:1:6:GORE][SPECIALATTACK_INJECT_EXTRACT:50:100]
[ATTACK:SECOND:BYTYPE:GRASP:punch:punches:1:2:BLUDGEON][ATTACKFLAG_WITH]
[FAT:2]
[CHILD:30][BABY:1][MULTIPLE_LITTER_RARE]
[DAMBLOCK:10]
[ALL_ACTIVE][CAVE_ADAPT]
[STANDARD_FLESH]
[HOMEOTHERM:10067]
[LAYERING:50]
[SWIMS_LEARNED][SWIM_SPEED:2500]
[MUNDANE]

Now, what does this all mean, exactly? Well, compared to dwarves they are big, bad, as fast as elves, as sturdy as dwarves (hard to knock over), they have white blood, can eat bones, are immune to fear, stun, and never get tired, see twice as far, and are almost totally immune to most small-damage attacks. In addition I copied the giant cave spider paralyzing bite attack, so when you bite and hit, you'll sometimes inject a paralyzing poison fairly often that'll knock your prey unconscious in a few combat rounds. Not only is the bite very damaging, but you can even knock out creatures like ettins or giants and rip them up as they sleep at your leisure.

However, we're not done yet. Notice the BODY: token has a few tidbits that we need to take a closer look at- 'ARACHNOBODY' and '8EYES' in particular. These are new to our species and we need to add them. So, close that and open up body_default.txt, or create your own body_something.txt file. Add the following to the bottom:

[BODY:ARACHNOBODY]
[BP:UB:upper body][UPPERBODY]
[BP:LB:abdomen][CON:UB][LOWERBODY]
[BP:HD:head][CON:UB][HEAD]
[BP:RUA:right upper arm][CON:LB][LIMB][RIGHT]
[BP:LUA:left upper arm][CON:LB][LIMB][LEFT]
[BP:RLA:right lower arm][CON:RUA][LIMB][RIGHT]
[BP:LLA:left lower arm][CON:LUA][LIMB][LEFT]
[BP:RH:right hand][CON:RLA][GRASP][RIGHT]
[BP:LH:left hand][CON:LLA][GRASP][LEFT]
[BP:RA1:right first leg][CON:LB][LIMB][RIGHT]
[BP:LA1:left first leg][CON:LB][LIMB][LEFT]
[BP:RF1:right first claw][CON:RA1][STANCE][RIGHT]
[BP:LF1:left first claw][CON:LA1][STANCE][LEFT]
[BP:RA2:right second leg][CON:LB][LIMB][RIGHT]
[BP:LA2:left second leg][CON:LB][LIMB][LEFT]
[BP:RF2:right second claw][CON:RA2][STANCE][RIGHT]
[BP:LF2:left second claw][CON:LA2][STANCE][LEFT]
[BP:RA3:right third leg][CON:LB][LIMB][RIGHT]
[BP:LA3:left third leg][CON:LB][LIMB][LEFT]
[BP:RF3:right third claw][CON:RA3][STANCE][RIGHT]
[BP:LF3:left third claw][CON:LA3][STANCE][LEFT]
[BP:RA4:right fourth leg][CON:LB][LIMB][RIGHT]
[BP:LA4:left fourth leg][CON:LB][LIMB][LEFT]
[BP:RF4:right fourth claw][CON:RA4][STANCE][RIGHT]
[BP:LF4:left fourth claw][CON:LA4][STANCE][LEFT]

[BODY:8EYES]
[BP:REYE:first eye][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL][RIGHT]
[BP:REYE:second eye][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL][RIGHT]
[BP:REYE:third eye][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL]
[BP:REYE:fourth eye][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL]
[BP:REYE:fifth eye][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL]
[BP:REYE:sixth eye][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL]
[BP:REYE:seventh eye][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL][LEFT]
[BP:LEYE:eighth eye][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL][LEFT]

Voila! Now you have your complete arachnid. They are very fun to play in adventurer mode, yet still a challenge. You can tear through unarmed civilians like a knife through butter, armed soldiers pose a minor challenge (much bigger if you are getting ganged up on), elite spearmen are devastating, and archers still rip you to shreds unless you close in on them quickly and poison them. However, thanks to your multiple eyes and legs you can take quite a few direct hits and still keep going (I once had an arrow smash straight through my head, taking out 5 eyes and wounding the throat, brains, and both ears, and survived the encounter).

In any case, you're now done! Create a new world and you will now be able to use arachnids as a playable creature in adventurer mode.

Written by Teldin.

= Modbase =

Modbase is a great tool made by Sean Mirrsen which allows you to freely swap mods and tweak game settings.
[http://www.bay12games.com/forum/index.php?topic=18623.0 Get it now!]
For version 0.38c.

[[Category:Modding]]
[[Category:Guides]]

Category:FAQ - Interface

2009-03-19T01:32:03Z

Adeptable: add standard FAQ tet and category

If you want to write an answer to somebody else’s posted question, please keep the answer short and simple, and link to the complicated explanations.

[[Category:FAQ|interface]]

Template:Game Interface FAQ

2009-03-19T01:30:24Z

Adeptable: use a hyphen in the FAQ category name (easier to type, and now pointing to an existing category)

<center>
{| class="collapsible collapsed infobox" style="background-color: #f9f9f9; border: 1px solid #aaa; font-size: 90%; margin: 1em 0em 0em; padding: 2px; text-align: center; width: 60%;"
! colspan="2" style="border: 1px solid #aaa; font-weight:bold; background-color: #ccf; padding-left: 1em; padding-right: 1em;" | '''Game Interface FAQ'''
|-
| [[Controls guide|Menu interface guide]]
|-
| [[Tilesets|What do these symbols represent?]]
|-
| [[Status icons|What do the flashing icons mean?]]
|-
| [[Maximizing framerate|How do I make the game run faster?]]
|-
| [[Custom grid|How can I make the game screen larger?]]
|-
| [[Efficient_gameplay|How do I accomplish tasks with fewer keystrokes?]]
|-
| [[Key bindings|What are the recommended key bindings if I have a laptop or other unusual keyboard?]]
|-
| [[Color Tiles|Where can I get color graphic tiles for this game?]]



|-
|height="10"|
|-
| {{Edit|Template:Game_Interface_FAQ|Add a question to the Interface FAQ}}
|-
| [[Frequently Asked Questions|Back to the Main FAQ]]
|}
</center>

<includeonly>[[Category:FAQ - Interface]]</includeonly>
<noinclude>[[Category:Templates]]</noinclude>

Category:FAQ - Game Basics

2009-03-19T01:25:30Z

Adeptable: add standard FAQ category text

If you want to write an answer to somebody else’s posted question, please keep the answer short and simple, and link to the complicated explanations.

[[Category:FAQ|Game Basics]]

Template:Game Basics FAQ

2009-03-19T01:17:04Z

Adeptable: use the more easily typed hyphen instead of a dash

<center>
{| class="collapsible collapsed infobox" style="background-color: #f9f9f9; border: 1px solid #aaa; font-size: 90%; margin: 1em 0em 0em; padding: 2px; text-align: center; width: 60%;"
! colspan="2" style="border: 1px solid #aaa; font-weight:bold; background-color: #ccf; padding-left: 1em; padding-right: 1em;" | '''Game Basics FAQ'''
|-
| [[Z-axis|What is the Z-Axis?]]
|-
| [[Things to Do|What is the point of the game?]]
|-
| [[Losing|Fun]]



|-
|height="10"|
|-
| {{Edit|Template:Game_Basics_FAQ|Add a question to the Game Basics FAQ}}
|-
| [[Frequently Asked Questions|Back to the Main FAQ]]
|}
</center>

<includeonly>[[Category:FAQ - Game Basics]]</includeonly>
<noinclude>[[Category:FAQ templates]]</noinclude>

40d:Item value

2009-03-19T01:13:42Z

Adeptable: /* Decorations */ clearer punctuation

'''Value''' is determined by the base value of the object with multipliers for the material it is made out of, the [[quality]] of its creation, and any [[decoration]]s on it.

==Base values of items==
The base value of an item is found from what the item '''is''', not what it is made out of. For example, a wood block uses the base value for a block, not the one for 'wooden'. A wood log uses the base value for raw material.

===Items with neither material nor quality===
{| style="border-spacing: 0"
|- style="background-color: #EEE"
! Value
! Items
|-
|1||[[Gutter cruor]], [[Prickle berry wine]], [[Seed]], [[Sewer brew]], [[Swamp whiskey]]
|- style="background-color: #EEE"
|2||[[Dwarven ale]], [[Dwarven beer]], [[Dwarven rum]], [[Dwarven wine]], [[Fisher berry wine]], [[Longland beer]], [[River spirits]], [[Strawberry wine]], [[Tuber beer]]
|-
|3||[[Whip wine]]
|- style="background-color: #EEE"
|5||[[Lye]], [[Quarry bush leaves|Quarry bush leaf]], [[Sand]], [[Sunshine]]
|-
|10||[[Redroot dye]]
|- style="background-color: #EEE"
|20||[[Extracts|Cave spider venom]], [[Milk|Cow's milk]], [[Dimple dye]], [[Dwarven sugar]], [[Dwarven syrup]], [[Dwarven wheat flour]], [[Emerald dye]], [[Longland flour]], [[Milk|One-humped camel's milk]], [[Extracts|Phantom spider venom]], [[Sliver dye]], [[Milk|Two-humped camel's milk]]
|-
|25||[[Whip vine flour]]
|- style="background-color: #EEE"
|30||[[Cheese|Cow cheese]], [[Cheese|One-humped camel's cheese]], [[Cheese|Two-humped camel's cheese]]
|-
|50||[[Dwarven milk]], [[Mog juice]]
|- style="background-color: #EEE"
|100||[[Cheese|Dwarven cheese]], [[Extracts|Giant cave spider venom]], [[Extracts|Giant desert scorpion venom]], [[Golden salve]], [[Gnomeblight]], [[Extracts|Liquid fire]], [[Extracts|Snakeman venom]]
|}

The values of tame animals (and pets) are listed [[Tame|here]].

===Items with material but without quality===
{| style="border-spacing: 0"
|- style="background-color: #EEE"
! Value
! Items
|-
|0||[[Severed body part|Body part]], [[Bone]], [[Chunk]], [[Corpse]], [[Fat]], [[Skin|Hide]] (raw), [[Shell]], [[Skull]]
|- style="background-color: #EEE"
|1||[[Animal]] (untamed), [[Tallow]]
|-
|2||[[Fish]] (including raw), [[Meat]], [[Plant]]
|- style="background-color: #EEE"
|3||[[Gem]] (rough), [[Log]], [[Ore]], [[Stone]] (both economic and non-economic)
|-
|5||[[Bar]], [[Block]], [[Gem]] (cut), [[Leather]]
|- style="background-color: #EEE"
|6||[[Thread]]
|-
|10||[[Coin]]
|}

===Items with both material and quality===
{| style="border-spacing: 0"
|- style="background-color: #EEE"
! Value
! Items
|-
|1||[[Arrow]], [[Blowdart]], [[Bolt]]
|- style="background-color: #EEE"
|7||[[Cloth]][4]
|-
|10||[[Animal Trap]], [[Buckler]], [[Cage]], [[Decoration]][1], Finished good[2][4], [[Furniture]][3], [[Prepared meal]], [[Weapon#Trap weapon statistics|Trap component]], [[Weapon]]
|- style="background-color: #EEE"
|15||[[Boot]], [[Gauntlet]], [[Helm]], [[Leggings]], [[Shield]], [[Shoe]][4], [[Clothing|Sock]][4]
|-
|20||[[Ballista arrow]], [[Armor|Leather armor]]
|- style="background-color: #EEE"
|25||[[Statue]], [[Window]]
|-
|30||[[Ballista part]], [[Catapult part]], [[Greaves]], [[Mechanism]]
|- style="background-color: #EEE"
|60||[[Chain mail]]
|-
|100||[[Anvil]], [[Plate mail]]
|}

[1] Decorations include "It is decorated with <material>", "It is banded with <material>", "It is adorned with hanging rings of <material>", "This object menaces with spikes of <material>", "On this object is an image of <description> in <material>", "It is studded with <metal>". See also the section about decorations.

[2] Except for armor, shoes, and socks. [[Crafts|Amulet]], [[Backpack]], [[Crafts|Bracelet]], [[Chain]], [[Clothing]], [[Crafts|Crown]], [[Goblet|Cup]], [[Instrument|Drum]], [[Crafts|Earring]], [[Vial|Flask]], [[Instrument|Flute]], [[Gem]] (large), [[Goblet]], [[Instrument|Harp]], [[Crafts|Idol]], [[Toy|Mini-forge]], [[Goblet|Mug]], [[Instrument|Piccolo]], [[Toy|Puzzlebox]], [[Quiver]], [[Crafts|Ring]], [[Chain|Rope]], [[Crafts|Scepter]], [[Totem|Skull Totem]], [[Toy|Toy axe]], [[Toy|Toy boat]], [[Toy|Toy hammer]], [[Instrument|Trumpet]], [[Vial]], [[Waterskin]]

[3] Except for anvil, ballista part, catapult part, mechanism, statue, and window.

[4] Cloth items get a free decoration made of the same material. Goods made out of cloth get the following built in as decorations: the cloth (with quality mod), the thread (without quality), and the dye (with quality).

==Material multipliers==
The material multiplier of an item is found from what it is made out of. For example, a wood block uses the same multiplier as a log or chest - that for wood. Oddly, burned wood is no longer considered wooden, but has other modifiers.

{| class="collapsible collapsed" style="width:80%; border-spacing: 1"
|- style=background-color:#ccf
! colspan=2|[[Stone]]s
|- style=text-align:left
! style=padding-right:1em|Multiplier
! Stone
|- style="background-color: #EEE"
|x1||[[Bismuthinite]], [[Bituminous coal]], [[Lignite]], [[Stone|Common stone]]
|-
|x2||[[Cassiterite]], [[Copper nuggets]], [[Garnierite]], [[Malachite]], [[Sphalerite]], [[Calcite]], [[Chalk]], [[Dolomite]], [[Limestone]], [[Marble]]
|- style="background-color: #EEE"
|x3||[[Tetrahedrite]], [[Obsidian]]
|-
|x5||[[Galena]]
|- style="background-color: #EEE"
|x8||[[Hematite]], [[Limonite]], [[Magnetite]]
|-
|x10||[[Horn silver]], [[Silver nuggets]]
|- style="background-color: #EEE"
|x30||[[Gold nuggets]]
|-
|x40||[[Native aluminum]], [[Platinum nuggets]]
|- style="background-color: #EEE"
|x250||[[Raw adamantine]]
|}

{| class="collapsible collapsed" style="width:80%; border-spacing: 1"
|- style=background-color:#ccf
! colspan=2|[[Gem]]s
|- style=text-align:left
! style=padding-right:1em|Multiplier
! Gem
|- style="background-color: #EEE"
|x2||[[Banded agate]], [[Dendritic agate]], [[Fire agate]], [[Fortification agate]], [[Lace agate]], [[Moss agate]], [[Plume agate]], [[Tube agate]], [[Bloodstone]], [[Carnelian]], [[Gray chalcedony]], [[White chalcedony]], [[Chrysocolla]], [[Chrysoprase]], [[Rock crystal]], [[Citrine]], [[Tiger iron]], [[Blue jade]], [[Lavender jade]], [[Pink jade]], [[White jade]], [[Brown jasper]], [[Yellow jasper]], [[Lapis lazuli]], [[Moonstone]], [[Morion]], [[Onyx]], [[Prase]], [[Pyrite]], [[Milk quartz]], [[Sard]], [[Sardonyx]], [[Schorl]], [[Sunstone]], [[Tigereye]], [[Turquoise]], [[Variscite]]
|-
|x3||[[Aventurine]], [[Picture jasper]], [[Rose quartz]]
|- style="background-color: #EEE"
|x10||[[Amber opal]], [[Bone opal]], [[Cherry opal]], [[Gold opal]], [[Jasper opal]], [[Milk opal]], [[Moss opal]], [[Onyx opal]], [[Pineapple opal]], [[Pipe opal]], [[Prase opal]], [[Resin opal]], [[Shell opal]], [[Wax opal]], [[Wood opal]], [[Clear tourmaline]]
|-
|x15||[[Melanite]], [[Fire opal]], [[Jelly opal]], [[Pink tourmaline]], [[Red tourmaline]]
|- style="background-color: #EEE"
|x20||[[Alexandrite]], [[Almandine]], [[Amethyst]], [[Aquamarine]], [[Golden beryl]], [[Honey yellow beryl]], [[Red beryl]], [[Chrysoberyl]], [[Cat's eye]], [[Clear garnet]], [[Pink garnet]], [[Goshenite]], [[Cinnamon grossular]], [[Red grossular]], [[Yellow grossular]], [[Heliodor]], [[Green jade]], [[Kunzite]], [[Morganite]], [[Bandfire opal]], [[Claro opal]], [[Crystal opal]], [[Harlequin opal]], [[Levin opal]], [[Pinfire opal]], [[Precious fire opal]], [[Red flash opal]], [[White opal]], [[Peridot]], [[Black pyrope]], [[Red pyrope]], [[Rhodolite]], [[Rubicelle]], [[Violet spessartine]], [[Yellow spessartine]], [[Purple spinel]], [[Red spinel]], [[Tanzanite]], [[Topazolite]], [[Topaz]], [[Green tourmaline]], [[Black zircon]], [[Brown zircon]], [[Green zircon]], [[Red zircon]], [[Yellow zircon]]
|-
|x25||[[Indigo tourmaline]], [[Clear zircon]]
|- style="background-color: #EEE"
|x30||[[Demantoid]], [[Light yellow diamond]], [[Blue garnet]], [[Black opal]], [[Tsavorite]]
|-
|x40||[[Faint yellow diamond]], [[Emerald]], [[Ruby]], [[Sapphire]]
|- style="background-color: #EEE"
|x60||[[Black diamond]], [[Blue diamond]], [[Clear diamond]], [[Green diamond]], [[Red diamond]], [[Yellow diamond]], [[Star ruby]], [[Star sapphire]]
|}

{| class="collapsible collapsed" style="width:80%; border-spacing: 1"
|- style=background-color:#ccf
! colspan=2|[[Metal]]s
|- style=text-align:left
! style=padding-right:1em|Multiplier
! Metal
|- style="background-color: #EEE"
|x2||[[Bismuth]], [[Copper]], [[Lead]], [[Nickel]], [[Tin]], [[Zinc]]
|-
|x3||[[Lay pewter]], [[Nickel silver]]
|- style="background-color: #EEE"
|x4||[[Trifle pewter]]
|-
|x5||[[Bronze]], [[Fine pewter]]
|- style="background-color: #EEE"
|x6||[[Billon]], [[Bismuth bronze]]
|-
|x7||[[Brass]]
|- style="background-color: #EEE"
|x8||[[Sterling silver]]
|-
|x10||[[Iron]], [[Pig iron]], [[Silver]]
|- style="background-color: #EEE"
|x11||[[Black bronze]]
|-
|x20||[[Electrum]]
|- style="background-color: #EEE"
|x23||[[Rose gold]]
|-
|x30||[[Gold]], [[Steel]]
|- style="background-color: #EEE"
|x40||[[Aluminum]], [[Platinum]]
|-
|x300||[[Adamantine]]
|}

{| class="collapsible collapsed" style="width:80%; border-spacing: 1"
|- style=background-color:#ccf
! colspan=2|[[Animal]]s
|- style=text-align:left
! style=padding-right:1em|Multiplier
! Animal
|- style="background-color: #EEE"
|x1||[[Antman]], [[Batman]], [[Bilou]], [[Black-crested gibbon]], [[Black-handed gibbon]], [[Bonobo]], [[Cat]], [[Cave Swallowman]], [[Chimpanzee]], [[Cyclops]], [[Dark gnome]], [[Deer]], [[Dog]], [[Donkey]], [[Dwarf]], [[Elf]], [[Ettin]], [[Fox]], [[Frogman]], [[Gazelle]], [[Giant]], [[Goblin]], [[Gorilla]], [[Gray gibbon]], [[Gremlin]], [[Groundhog]], [[Harpy]], [[Hoary marmot]], [[Horse]], [[Human]], [[Kobold]], [[Lizardman]], [[Mandrill]], [[Minotaur]], [[Mountain gnome]], [[Mountain goat]], [[Mule]], [[Olmman]], [[Orangutan]], [[Phantom spider]], [[Pileated gibbon]], [[Raccoon]], [[Ratman]], [[Rhesus macaque]], [[Siamang]], [[Silvery gibbon]], [[Snakeman]], [[Titan]], [[Troglodyte]], [[White-browed gibbon]], [[White-handed gibbon]], [[Wizard]]
|-
|x2||[[Beak dog]], [[Cow]], [[Elk]], [[Foul blendec]], [[Giant mole]], [[Giant rat]], [[Ice wolf]], [[Large rat]], [[Muskox]], [[Naked mole dog]], [[One-humped camel]], [[Satyr]], [[Two-humped camel]], [[Warthog]], [[Wolf]]
|- style="background-color: #EEE"
|x3||All large oceanic creatures ([[Walrus]], [[Whale]], sharks, oceanic fish), [[Black bear]], [[Carp]], [[Cheetah]], [[Cougar]], [[Elephant]], [[Giant cheetah]], [[Giant jaguar]], [[Giant leopard]], [[Giant lion]], [[Giant tiger]], [[Grizzly bear]], [[Hippo]], [[Jaguar]], [[Leechman]], [[Leopard]], [[Lion]], [[Longnose gar]], [[Pike]], [[Polar bear]], [[Sea monster]], [[Sea serpent]], [[Slugman]], [[Snailman]], [[Strangler]], [[Tiger]], [[Tigerfish]], [[Tigerman]]
|-
|x4||[[Alligator]], [[Nightwing]], [[Saltwater crocodile]], [[Werewolf]]
|- style="background-color: #EEE"
|x5||[[Cave crocodile]], [[Giant bat]], [[Giant cave swallow]], [[Giant eagle]], [[Giant olm]], [[Giant toad]], [[Purring maggot]]
|-
|x10||[[Blizzard man]], [[Fire imp]], [[Giant cave spider]], [[Giant desert scorpion]], [[Ogre]], [[Sasquatch]], [[Troll]], [[Unicorn]]
|- style="background-color: #EEE"
|x20||[[Frog demon]], [[Tentacle demon]]
|-
|x50||[[Demon]], [[Dragon]], [[Hydra]], [[Merperson]]
|}

{| class="collapsible collapsed" style="width:80%; border-spacing: 1"
|- style=background-color:#ccf
! colspan=2|[[Plant]]s
|- style=text-align:left
! style=padding-right:1em|Multiplier
! Plant
|- style="background-color: #EEE"
|x1||[[Hide root]], [[Muck root]], [[Prickle berry]], [[Rat weed]], [[Sliver barb]], [[Sun berry]], [[Whip vine]]
|-
|x2||[[Blade weed]], [[Bloated tuber]], [[Cave wheat]], [[Dimple cup]], [[Fisher berry]], [[Longland grass]], [[Pig tail]], [[Plump helmet]], [[Quarry bush]], [[Rope reed]], [[Sweet pod]], [[Wild strawberry]]
|- style="background-color: #EEE"
|x5||[[Kobold bulb]], [[Valley herb]]
|}

{| class="collapsible collapsed" style="width:80%; border-spacing: 1"
|- style=background-color:#ccf
! colspan=2|Miscellaneous
|- style=text-align:left
! style=padding-right:1em|Multiplier
! Material
|- style="background-color: #EEE"
|x1||[[Ash]], [[Wood]]
|-
|x2||[[Charcoal]], [[Coke]], [[Green glass]], [[Thread|Silk thread]][1]
|- style="background-color: #EEE"
|x3||[[Potash]]
|-
|x4||[[Pearlash]]
|- style="background-color: #EEE"
|x5||[[Clear glass]], [[Soap]][1]
|-
|x10||[[Crystal glass]]
|-
|||[1]The value of objects made from these materials is also multiplied by the value of their source animal.
|}

== Quality ==
Item value is further increased by applying the [[Quality|quality]] modifier.

{|
! style="padding-right: 35px;" | '''Designation''' || style="text-align: left;" | '''Description''' || style="padding-right: 20px; padding-left: 15px; text-align: center;" | '''Value Modifier''' ||
|-
|  Item Name || style="text-align: center;" | —     || style="text-align: center;" | ×1  ||
|-
| -Item Name- || Well-crafted || style="text-align: center;" | ×2  ||
|-
| +Item Name+ || Finely-crafted || style="text-align: center;" | ×3  ||
|-
| *Item Name* || Superior quality || style="text-align: center;" | ×4  ||
|-
| ≡Item Name≡ || Exceptional || style="text-align: center;" | ×5  ||
|-
| ☼Item Name☼ || Masterful || style="text-align: center;" | ×12  ||
|-
| Unique Name || Artifact || style="text-align:center;" | ×120  ||
|}

==Decorations==

Your [[craftsdwarf|craftsdwarves]] can add [[decoration|decorations]] to your objects. This increases their value. The base value of a decoration is 10. This is multiplied with the material the decoration is made of and the [[quality]] of the decoration, and added to the value of the item. For example, a [[gold]] stud would be worth 10 (base value for the decoration) times 30 (material multiplier for gold) =300☼. A finely crafted gold stud would be 3*10*30=900☼.

Engravings are decorations that treat all materials as having a modifier of 1; an engraving in mudstone is as valuable as an engraving in obsidian or raw adamantine.

== Dyeing ==
Value gained by [[dye]]ing is added, like that of decorations. Only [[thread]], [[cloth]] and its products can be dyed. For details see [[Dye]].

==Examples==
===Basic examples===
{| style="border-spacing: 0"
|-
! Base Object
!
! Material
!
! [[Quality]]
!
! Final Value
|-
|[[Anvil]] ||(100)||[[Steel]] ||(x30)||+Item+ ||(x3)||9000☼
|-
|[[Door]] ||(10)||[[Obsidian]] ||(x3)||None ||(x1)||30☼
|-
|[[Block]] ||(5)||[[Wood]] ||(x1)||None ||(x1)||5☼
|-
|[[Goblet]] ||(10)||[[Lead]] ||(x2)||-Item- ||(x2)||40☼
|-
|[[Goblet]] ||(10)||[[Aluminum]]||(x40)||☼Item☼ ||(x12)||4800☼
|}
===+«+Pig tail shoe+»+===
{{Gametext|This is a finely-crafted Pig tail shoe. It is made from well-crafted Pig tail cloth. The thread is midnight blue, finely colored with Dimple dye. On the item is a finely-designed image of squares in Pig tail by Urvad Zonilash. It is made from superior quality Pig tail cloth. The thread is midnight blue, finely colored with Dimple dye.}}
{|
|-
!Base item
!Material
!Quality
!Subtotal
|-
|15 (shoe)||x2 (pig tail)||x3 (fine quality)||= 90
|-
|10 (cloth decoration)||x2 (pig tail)||x2 (well-crafted quality)||= 40
|-
|10 (thread decoration)||x2 (pig tail)||||= 20
|-
|20 (dimple dye)||||x3 (fine quality)||= 60
|-
|10 (image decoration)||x2 (pig tail)||x3 (fine quality)||= 60
|-
|20 (dimple dye)||||x3 (fine quality)||= 60
|}
'''Total:''' 330☼

[[Category:Items|*Value]]

40d:Site map

2008-08-03T21:38:24Z

Adeptable: /* Lower Left */ reword

[[Category:Adventurer mode]]
The site map or location map is one of the possible modes in the [[Adventurer mode]].

== General Information ==

The site map is the most detailed mode available. In other words, its tiles do not represent a larger number of tiles in another map, even though an individual tile may contain several objects and/or [[creatures]] stacked on top of one another.

The exact size of the tiles is not defined and the flexible physics of the game make it difficult to pin down any size. However, it should be noted that each [[chair]], [[table]], [[bed]], or other item of [[furniture]] requires a single tile for itself in order to be placed correctly.

While the adventurer explores the game in site map mode, they will over time grow [[Adventurer mode#Basic Needs|thirsty]] and [[Adventurer mode#Basic Needs|hungry]].

== Screen Structure ==

[[image:ExploredTownAtNight.png]]

=== Central Area ===

The central area of the screen shows the player character and the surrounding area.

Depending on the lighting, not the entire area may be visible. During the night or inside [[caves]], only a limited area is currently visible. In addition, obstacles like [[trees]] or [[walls]] will also impede visiblity.

Tiles which are unknown and currently invisible will be completely black. Tiles which have been seen before (either during the current visit to the area or during a previous visit), will show their usual character, but will be greyed out. If there had been a [[creature]] on a tile when the character last saw the tile, that is, the last turn the tile was visible, the [[creature]]'s symbol will be shown in black on a purple background. It will remain there, until the tile becomes visible again.
[[image:BearInvisible.png|left|thumb|A bear hidden by a tree]][[image:BearVisible.png|center|thumb|The bear visible again]] 

=== Message Line ===

At the bottom of the site map there is the message line where messages will be displayed, deducting one line from the central area. Usually, it is a single line. However, in certain situations where many things happen simultaneously (or rather between two moves of the player character), as in [[combat]], it may turn into several lines covering major parts of the screen.

[[Image:NormalMessageLine.png|left|thumb|A normal message line]][[Image:MassiveMessageLine.png|center|thumb|A message line overflow]] 
You can clear it by pressing the {{k|space}} key.

=== Bottom Line Information ===

The two bottom lines contain several pieces of information.

On the first line on the left hand side, the character name will be displayed.

On the second line on the left hand side, the name of the current location will be displayed. If the character is inside a named building, that building's name will be displayed. When inside a [[Site|town]] or other [[site]], that location's name will be displayed and only if none of these applies will the name of the region (that is, the local region the current travel map tile belongs to) be chosen.

On the first line, in the center, 'W:' is followed by the name of the current [[weapon]].

On the second line, in the center, 'A:' is followed by the name of the current torso [[armor]].

On the first line, on the right hand side, 'Speed:' shows the [[speed]] value of the character. The higher the value, the faster the character moves and acts and the basic value for [[humans]] is 1,000.

=== Upper Left ===

The upper left corner of the screen features a site compass. It lists the nearby [[Site|sites]] of interests closest to the location you are currently at.

Each line lists one [[site]], starting with the [[site]] you are currently at.

The first item in each line is the symbol for the [[site]] as seen on the travel map.

This is then followed either by compass directions or a line of white minusses '---'.

The '---' mean that the player character is currently at the specified [[site]].

If a compass direction is shown, it refers to the direction in which the [[site]] is as seen from the player character's current tile. Compass directions can be simple, like 'N', but can also be more extensive like 'WSW', so they are fairly accurate. The color of the compass direction indicates how far the character is away from the site. Light green means the character is the closest beyond being at a location. Brown means nearby and dark grey indicates any distance beyond that.

There is one special appliance for the compass: If you are currently on a [[quest]] and have reached the [[quest]] location on the travel map, the compass on the site map will not show the white '---' until you have reached the precise [[quest]] location, like for instance the actual entrance to a [[cave]]. Instead, you will have light green compass directions pointing the way towards the [[quest]] location. Note that this is only the [[cave]] entrance or such. The location of a [[quest]] opponent is not given by the compass and needs to be figured through searching the [[quest]] location.

There is one more item a line may contain. That is a cyan 'TSK' marking a [[quest]] destination location. A character is on a [[quest]] for the entire time from accepting the [[quest]] until reporting the success to the [[quest]] giver. While the [[quest]] is not fulfilled yet (i.e. the [[quest]] monster has not been slain yet), the [[site]] of the [[quest]] (where the [[quest]] monster resides) will be marked with the 'TSK'. Once the [[quest]] has been fulfilled (i.e. the [[quest]] monster has been slain), the 'TSK' is moved to the town where the [[quest]] giver resides. Only once the [[quest]] is ended by reporting the success to the [[quest]] giver will the 'TSK' be removed completely.

=== Lower Left ===

The lower left area may contain a mini map if it is available.

The minimap is only available if you are in a [[Site|town]] or when you are directly at a special/[[quest]] location, like for instance inside a [[cave]]. The minimap is not available on normal terrain maps or on [[cave]] location site maps themselves (that is the site map where the entrance to the [[cave]] is located).

In [[caves]], the minimap currently seems to mark only the player character position as a light green '@' ([[image:PlayerIcon.png]]) and the position of the [[cave]] entrance as a yellow 'X'. It does not show tunnels or [[creatures]] or any other features, so it only helps with basic orientation.

In [[Site|towns]], the minimap shows the buildings you have either heard about or visited as well as the position of your character. Other creatures or features are not shown on the map and [[z-level]] differences are also not shown.

* In the town map, your own character is again the light green '@' ([[image:PlayerIcon.png]]).
* A black 'H' on a brown background ([[image:HouseIcon.png]]) marks housing, be it hovels or appartment buildings.
* A blue 'M' on dark blue ([[image:MayorIcon.png]]) marks the town hall where the mayor can be found.
* A grey rectangle of 2x2 tiles size with a white 'T' on a red background in the upper left corner ([[image:TempleIcon.png]]) marks a [[temple]].
* A grey rectangle of 3x3 tiles size with a cyan 'K' on a blue background in the middle ([[image:KeepIcon.png]]) marks a [[keep]].
* Yellow icons on a brown background depict stores:
** Armory : [[image:ArmoryIcon.png]]
** Clothier : [[image:TraderIcon.png]]
** Grocery : [[image:GroceryIcon.png]]
** Weapon Smith : [[image:WeaponSmithieIcon.png]]
** Jeweler : [[image:TrinketIcon.png]]

=== Right Side ===

On the right hand side, neighboring [[z-axis|z-levels]] may be shown.

Their displayal works basically like that of the central area as far as visibility is concerned.

These visuals only pop up once the character moves within range of an area where the character can either see onto a different [[z-level]] or where the character has previously seen the different [[z-level]] (the latter is very common during [[cave]] explorations where the surface [[z-level]] may show up on the right hand side).

These displays are framed and in the middle of the bottom or top frame, an arrow and a number will indicate the relative depth: A downward arrow in the bottom frame indicates that the [[z-level]] displayed is lower than where the character is currently located, while an upward arrow in the top frame indicates that the [[z-level]] is above the character. The number next to the arrow indicates the number of [[z-axis|levels]] difference. So, seeing down a single-level [[slope]] would result in a down arrow next to the number '1', while seeing the roof of a 2-story building would generate an up arrow and the number '2'. In addition, arrow and number are light blue when displaying a [[z-level]] above the character's current position and brown when the extra [[z-level]] is below.

If there is a [[creature]] visible in the extra-display, the frame will be yellow.

== Game Play Function ==

While the travel map allows for quick travel between locations, the site map is actually the location of the main interaction of the game. As such, you can only view your [[inventory]] or interact with it while in site map mode. In addition, [[creature]] [[encounters]] also only take place on site maps; if you come across a [[creature]] while travelling, you will have to switch into site map mode (by pressing {{k|>}}) - if it is not a random [[encounter]], in which case you will automatically be forced into site map mode.

As was noted above, the character will grow [[Adventurer mode#Basic Needs|hungry]] and [[Adventurer mode#Basic Needs|thirsty]] while on a site map. However, site maps are the only location where you actually can obtain [[Adventurer mode#Basic Needs|food]] and [[Adventurer mode#Basic Needs|water]] as the travel map does not offer interaction with any game objects.

Time passes more slowly than on the travel map, but it is subject to day and night, as well as [[weather]] effects like rain.

In [[Site|towns]], the site map allows you to explore the [[Site|town]] and speak with the inhabitants (using {{k|k}}). This way you can gather information for your [[legends]] registry, also learn about nearby [[Site|sites]] and their inhabitants, get [[Quest|quests]] from the mayor, and trade for better equipment or food.

When facing special [[Site|sites]] like [[caves]] or [[goblin]] towers, the site map effectively resembles the normal gameplay of a rogue-like.

40d:Site map

2008-08-03T21:34:37Z

Adeptable: /* Message Line */ grammar

[[Category:Adventurer mode]]
The site map or location map is one of the possible modes in the [[Adventurer mode]].

== General Information ==

The site map is the most detailed mode available. In other words, its tiles do not represent a larger number of tiles in another map, even though an individual tile may contain several objects and/or [[creatures]] stacked on top of one another.

The exact size of the tiles is not defined and the flexible physics of the game make it difficult to pin down any size. However, it should be noted that each [[chair]], [[table]], [[bed]], or other item of [[furniture]] requires a single tile for itself in order to be placed correctly.

While the adventurer explores the game in site map mode, they will over time grow [[Adventurer mode#Basic Needs|thirsty]] and [[Adventurer mode#Basic Needs|hungry]].

== Screen Structure ==

[[image:ExploredTownAtNight.png]]

=== Central Area ===

The central area of the screen shows the player character and the surrounding area.

Depending on the lighting, not the entire area may be visible. During the night or inside [[caves]], only a limited area is currently visible. In addition, obstacles like [[trees]] or [[walls]] will also impede visiblity.

Tiles which are unknown and currently invisible will be completely black. Tiles which have been seen before (either during the current visit to the area or during a previous visit), will show their usual character, but will be greyed out. If there had been a [[creature]] on a tile when the character last saw the tile, that is, the last turn the tile was visible, the [[creature]]'s symbol will be shown in black on a purple background. It will remain there, until the tile becomes visible again.
[[image:BearInvisible.png|left|thumb|A bear hidden by a tree]][[image:BearVisible.png|center|thumb|The bear visible again]] 

=== Message Line ===

At the bottom of the site map there is the message line where messages will be displayed, deducting one line from the central area. Usually, it is a single line. However, in certain situations where many things happen simultaneously (or rather between two moves of the player character), as in [[combat]], it may turn into several lines covering major parts of the screen.

[[Image:NormalMessageLine.png|left|thumb|A normal message line]][[Image:MassiveMessageLine.png|center|thumb|A message line overflow]] 
You can clear it by pressing the {{k|space}} key.

=== Bottom Line Information ===

The two bottom lines contain several pieces of information.

On the first line on the left hand side, the character name will be displayed.

On the second line on the left hand side, the name of the current location will be displayed. If the character is inside a named building, that building's name will be displayed. When inside a [[Site|town]] or other [[site]], that location's name will be displayed and only if none of these applies will the name of the region (that is, the local region the current travel map tile belongs to) be chosen.

On the first line, in the center, 'W:' is followed by the name of the current [[weapon]].

On the second line, in the center, 'A:' is followed by the name of the current torso [[armor]].

On the first line, on the right hand side, 'Speed:' shows the [[speed]] value of the character. The higher the value, the faster the character moves and acts and the basic value for [[humans]] is 1,000.

=== Upper Left ===

The upper left corner of the screen features a site compass. It lists the nearby [[Site|sites]] of interests closest to the location you are currently at.

Each line lists one [[site]], starting with the [[site]] you are currently at.

The first item in each line is the symbol for the [[site]] as seen on the travel map.

This is then followed either by compass directions or a line of white minusses '---'.

The '---' mean that the player character is currently at the specified [[site]].

If a compass direction is shown, it refers to the direction in which the [[site]] is as seen from the player character's current tile. Compass directions can be simple, like 'N', but can also be more extensive like 'WSW', so they are fairly accurate. The color of the compass direction indicates how far the character is away from the site. Light green means the character is the closest beyond being at a location. Brown means nearby and dark grey indicates any distance beyond that.

There is one special appliance for the compass: If you are currently on a [[quest]] and have reached the [[quest]] location on the travel map, the compass on the site map will not show the white '---' until you have reached the precise [[quest]] location, like for instance the actual entrance to a [[cave]]. Instead, you will have light green compass directions pointing the way towards the [[quest]] location. Note that this is only the [[cave]] entrance or such. The location of a [[quest]] opponent is not given by the compass and needs to be figured through searching the [[quest]] location.

There is one more item a line may contain. That is a cyan 'TSK' marking a [[quest]] destination location. A character is on a [[quest]] for the entire time from accepting the [[quest]] until reporting the success to the [[quest]] giver. While the [[quest]] is not fulfilled yet (i.e. the [[quest]] monster has not been slain yet), the [[site]] of the [[quest]] (where the [[quest]] monster resides) will be marked with the 'TSK'. Once the [[quest]] has been fulfilled (i.e. the [[quest]] monster has been slain), the 'TSK' is moved to the town where the [[quest]] giver resides. Only once the [[quest]] is ended by reporting the success to the [[quest]] giver will the 'TSK' be removed completely.

=== Lower Left ===

The lower left area may contain a mini map if it is available.

The minimap is only available if you are in a [[Site|town]] or when you are directly at a special/[[quest]] location, like for instance inside a [[cave]]. The minimap is not available on normal terrain maps or on [[cave]] location site maps themselves (that is the site map where the entrance to the [[cave]] is located).

In [[caves]], the minimap currently seems to mark only the player character position as a light green '@' ([[image:PlayerIcon.png]]) and the position of the [[cave]] entrance as a yellow 'X'. It does not show tunnels or [[creatures]] or any other features, so it basically only helps with basic orientation.

In [[Site|towns]], the minimap shows the buildings you have either heard about or visited as well as the position of your character. Other creatures or features are not shown on the map and [[z-level]] differences are also not shown.

* In the town map, your own character is again the light green '@' ([[image:PlayerIcon.png]]).
* A black 'H' on a brown background ([[image:HouseIcon.png]]) marks housing, be it hovels or appartment buildings.
* A blue 'M' on dark blue ([[image:MayorIcon.png]]) marks the town hall where the mayor can be found.
* A grey rectangle of 2x2 tiles size with a white 'T' on a red background in the upper left corner ([[image:TempleIcon.png]]) marks a [[temple]].
* A grey rectangle of 3x3 tiles size with a cyan 'K' on a blue background in the middle ([[image:KeepIcon.png]]) marks a [[keep]].
* Yellow icons on a brown background depict stores:
** Armory : [[image:ArmoryIcon.png]]
** Clothier : [[image:TraderIcon.png]]
** Grocery : [[image:GroceryIcon.png]]
** Weapon Smith : [[image:WeaponSmithieIcon.png]]
** Jeweler : [[image:TrinketIcon.png]]

=== Right Side ===

On the right hand side, neighboring [[z-axis|z-levels]] may be shown.

Their displayal works basically like that of the central area as far as visibility is concerned.

These visuals only pop up once the character moves within range of an area where the character can either see onto a different [[z-level]] or where the character has previously seen the different [[z-level]] (the latter is very common during [[cave]] explorations where the surface [[z-level]] may show up on the right hand side).

These displays are framed and in the middle of the bottom or top frame, an arrow and a number will indicate the relative depth: A downward arrow in the bottom frame indicates that the [[z-level]] displayed is lower than where the character is currently located, while an upward arrow in the top frame indicates that the [[z-level]] is above the character. The number next to the arrow indicates the number of [[z-axis|levels]] difference. So, seeing down a single-level [[slope]] would result in a down arrow next to the number '1', while seeing the roof of a 2-story building would generate an up arrow and the number '2'. In addition, arrow and number are light blue when displaying a [[z-level]] above the character's current position and brown when the extra [[z-level]] is below.

If there is a [[creature]] visible in the extra-display, the frame will be yellow.

== Game Play Function ==

While the travel map allows for quick travel between locations, the site map is actually the location of the main interaction of the game. As such, you can only view your [[inventory]] or interact with it while in site map mode. In addition, [[creature]] [[encounters]] also only take place on site maps; if you come across a [[creature]] while travelling, you will have to switch into site map mode (by pressing {{k|>}}) - if it is not a random [[encounter]], in which case you will automatically be forced into site map mode.

As was noted above, the character will grow [[Adventurer mode#Basic Needs|hungry]] and [[Adventurer mode#Basic Needs|thirsty]] while on a site map. However, site maps are the only location where you actually can obtain [[Adventurer mode#Basic Needs|food]] and [[Adventurer mode#Basic Needs|water]] as the travel map does not offer interaction with any game objects.

Time passes more slowly than on the travel map, but it is subject to day and night, as well as [[weather]] effects like rain.

In [[Site|towns]], the site map allows you to explore the [[Site|town]] and speak with the inhabitants (using {{k|k}}). This way you can gather information for your [[legends]] registry, also learn about nearby [[Site|sites]] and their inhabitants, get [[Quest|quests]] from the mayor, and trade for better equipment or food.

When facing special [[Site|sites]] like [[caves]] or [[goblin]] towers, the site map effectively resembles the normal gameplay of a rogue-like.

40d:Tilesets

2008-08-03T20:52:34Z

Adeptable: /* Character sets */ rm dead link

''You may be looking for the [[List of user character sets]] or [[List of user graphics sets]].''

'''Tilesets''' are images the game uses to display its graphics; each tile is used to show text and represent things. Users create custom tilesets for a number of reasons, including increased visibility, aesthetics, or small size. Tilesets come in two flavors: "'''character sets'''" (or simply "tilesets") and "'''graphics sets'''".

== Overview and installation ==

=== Character sets ===

A character set is an image in BMP format that contains the 256 different tiles, corresponding to the [[Character table|IBM Code Page 437]] (sometimes called Extended ASCII), which are used to display the main graphics. [[List of user character sets|Here is the list]] of user-made standard tilesets. To install any of these tilesets, follow these steps:

# Download the tileset. (The list is [[List of user character sets|here]])
# Convert it into a 24-bit BMP file. Do NOT just change the extension to .bmp; you must use a program like MS paint to save it as a .bmp.
# Put it in the data/art directory of your Dwarf Fortress installation.
# Open data/init/init.txt
# If you want to use the tileset in fullscreen mode, locate and modify the [FULLSCREENX:800], [FULLSCREENY:600], and [FULLFONT:curses_800x600.bmp] configuration lines to match the specifications from the tileset list. The FULLFONT directive should match the filename of the tileset you downloaded. If you want to use the tileset in windowed mode, search for the [WINDOWEDX:640], [WINDOWEDY:300], and [FONT:curses_640x300.bmp] lines instead, and change them to the correct values.
# It is also recommended you change [BLACK_SPACE:NO] to [BLACK_SPACE:YES] to prevent stretching of the graphics.
# Save the file, then you're ready to play!

=== Graphics sets ===

Character sets only change certain graphics, while others are left out. The confusingly-named [[graphics sets]] are used to change the appearance of [[creatures]] in the game, such as dwarves and unicorns. These are usually designed to work together with certain character sets. The Dystopian Rhetoric graphics set comes with its own DF installer; to install any others (or to install that one manually), you follow a similar process to the above:

# Download the graphics set. (The list is [[Graphics sets|here]].)
# Convert it into a 24-bit BMP file using your favorite image editing program.
# Put it in the raw/graphics/example directory of your Dwarf Fortress installation, so it overwrites the existing file.
# Open /raw/graphics/example_text.txt
# Replace the contents with the appropriate text for the graphics set you downloaded. Save the file.
# Open data/init/init.txt
# Locate the [GRAPHICS:NO] line and change it to [GRAPHICS:YES].
# Change the resolution and font directories as above, this time for the lines starting with GRAPHICS instead. So, if you want to use fullscreen mode, modify [GRAPHICS_FULLSCREENX:800], [GRAPHICS_FULLSCREENY:600], and [GRAPHICS_FULLFONT:curses_800x600.bmp] to suit the standard tileset you want to use. For windowed mode, the lines to change are [GRAPHICS_WINDOWEDX:640], [GRAPHICS_WINDOWEDY:300], and [GRAPHICS_FONT:curses_640x300.bmp].
# Be sure to change [GRAPHICS_BLACK_SPACE] to the same setting as [BLACK_SPACE].
# Save the file, then you're ready to get mangled by a great-looking elephant!

== Custom tileset design ==

The gameplay viewport is 80 characters wide, and 25 characters tall. Therefore, a tileset's target resolution will be TILE_X_LENGTH * 80 by TILE_Y_LENGTH * 25. Since the tileset is arranged into a 16x16 grid of tiles (256 tiles total), the tileset image size will be TILE_X_LENGTH * 16 by TILE_Y_LENGTH * 16. Here are some common tile sizes:

* A tileset with 10x12 tiles will be 160x192 pixels large, and the target resolution will be 800x300.
* A tileset with 16x16 tiles will be 256x256 pixels large, and the target resolution will be 1280x400.

When creating a custom tileset, it's often easiest to start with an existing one, and edit it to your liking. Tilesets generally fall into three categories: rectangular tilesets, square tilesets, and 16x16 square tilesets. Rectangular tilesets have tiles that are taller than they are wide. The text in these tilesets is generally easier to read, but the map appears squished horizontally. Square tilesets usually provide more attractive graphics, but are slightly less readable. The 16x16 square tilesets are just a sub-set, which are grouped together because most [[Object Tilesets]] use 16x16 tiles. The graphics in Dwarf Fortress can be somewhat diversified and enhanced through the use of graphics sets.

Many tiles are used by the game in multiple ways, and this makes customizing the graphics difficult. The same icon is used for chairs and the north end of one-tile-wide vertical bridges. Ashes and broken arrows look the same, and many game entities (such as levers, floodgates, bags, and bins) share characters that are also used in Dwarven names or other bits of text in the interface.

=== How colors other than white and magenta work ===

When the game draws a tile, it will select a foreground color, a background color, and a tile based on the item being drawn. The background color will be used in place of magenta (Hex code #FF00FF or RGB 255 0 255). All other colors in the tile will be treated as a mask against the foreground color. Pure white (#FFFFFF) will always show the foreground color, while light grey (#CCCCCC) will be a slightly darker version of the foreground color, and dark grey (#888888) will be a dark version of the foreground color. Black (#000000) will always be black. It is impossible to use different shades of the background color.

In general, just remember these rules:

* Bright magenta (#FF00FF) is the background.
* Bright white (#FFFFFF) is the foreground.
* Darker shades of white and grey (#C0C0C0, #808080, etc) will display darker shades of the foreground color. It is possible to use any shade of grey, including ones like #333333 and #C2C2C2.
* Black (#000000) will always be black.
* It's probably best to avoid color in normal tilesets.

For an example, the game is drawing an exposed turquoise cluster with color bright blue (#0000FF). While loading the tile image, it encounters the color light grey (#CCCCCC). The color used in its place will be:

{| style="margin-bottom:20px; text-align:left; width:90%"
|-
! Color component || Foreground color || Color mask from tile || Calculation in hex || Calculation in decimal
|-
| Red || #0000FF || #CCCCCC || 0016 * CC16 / 10016 = 0016 || 0 * 204 / 256 = 0
|-
| Green || #0000FF || #CCCCCC ||0016 * CC16 / 10016 = 0016 || 0 * 204 / 256 = 0
|-
| Blue || #0000FF || #CCCCCC || FF16 * CC16 / 10016 = CB16 || 255 * 204 / 256 = 203
|-
| Final Color || || || #0000CB || 0 0 203
|}

Color masks with unequal amounts of R, G and B are calculated in the same fashion. The game is now drawing a speardwarf with color brown (#C0C000). It encounters the color cyan while loading the tile (#008080). The color used instead of cyan will be:

{| style="margin-bottom:20px; text-align:left; width:90%"
|-
! Color component || Foreground color || Color mask from tile || Calculation in hex || Calculation in decimal
|-
| Red || #C0C000 || #008080 || C016 * 0016 / 10016 = 0016 || 192 * 0 / 256 = 0
|-
| Green || #C0C000 || #008080 ||C016 * 8016 / 10016 = 6016 || 192 * 128 / 256 = 96
|-
| Blue || #C0C000 || #008080 || 0016 * 8016 / 10016 = 0016 || 0 * 128 / 256 = 0
|-
| Final Color || || || #006000 || 0 96 0
|}

As illustrated by this example, colors in the tileset can result in colors that aren't in the foreground color or the tile graphic. In this case, a brown foreground color with a cyan pixel color in the tileset results in a final color of green.

Theoretically, the way the game handles color masks could be used to display different graphics for items that use the same tile (but whose respective colors use different color component channels). For example, if a bright red object and a bright blue object use the same tile, the tile can use bright red for all pixels that only the red object uses, bright blue for all pixels only the blue object uses, and bright magenta (but NOT #FF00FF, it would have to be #FE00FE or something similar) for all pixels both objects use. In this fashion the two objects that share a tile would look completely different. In practice however, this is probably impossible because so many objects share the same tile, the chances of the potential foreground colors sharing a red, green, or blue color component are too great.

== What tiles are used for what ==

* Items marked with * can have their tile changed in the [[modding|raw data]] files.
* Items marked with # can have their tile replaced by a [[graphics set]] image, in addition to having their tile changed in the raw data.
* Items marked with $ can be changed in the [[init.txt]] file.

====Row 01 (000-015)====
{|
|-
|
| No use
|-
| {{TST|☺}}
| [[Civilian]] dwarves#
|-
| {{TST|☻}}
| [[Military]] dwarves#
|-
| {{TST|♥}}
| [[Dimple cup]]s*
|-
| {{TST|♦}}
| [[Cut gem]]s, large [[gem]]s
|-
| {{TST|♣}}
| [[Tower-cap]]s*, [[Acacia]] trees*, [[Mangrove]] trees*, [[Maple]] trees*, [[quarry bush]]es*, [[Alder]] trees*, [[Birch]] trees*
|-
| {{TST|♠}}
| [[Plump helmet]]s*, [[Oak]] trees*, [[quarry bush]] leaves*, [[Mahogany]] trees*, [[Chestnut]] trees*, [[Ash tree]]s*
|-
| {{TST|•}}
| [[Stone]], solid [[workshop]] tile for several workshops like the [[magma smelter]], [[lake]]s in main map, [[cave]]s in the main map
|-
| {{TST|◘}}
| Solid workshop tile for several other workshops like the [[magma forge]], [[tanner]] workshop, [[catapult]] cup
|-
| {{TST|○}}
| [[Well]], [[bracelet]], [[ant colony]], [[millstone]], [[quern]]
|-
| {{TST|◙}}
|
|-
| {{TST|♂}}
| Male sign, [[bag]]s
|-
| {{TST|♀}}
| Female sign, [[amulet]]
|-
| {{TST|♪}}
|
|-
| {{TST|♫}}
| [[Armor stand]]s
|-
| {{TST|☼}}
| [[Gem]]s*, bituminous [[coal]]*, [[currency]] symbol, [[masterpiece]] [[quality]] symbol, spider [[web]]s, [[turtle]]*, 'sun' symbol in engravings, [[gear]] assemblies
|-
|}

====Row 02 (016-031)====
{|
|-
| {{TST|►}}
| Head of [[ballista]] facing east, [[vermin|manta ray]]
|-
| {{TST|◄}}
| Head of ballista facing west
|-
| {{TST|↕}}
|
|-
| {{TST|‼}}
| [[Cage]]s, on-[[fire]] symbol
|-
| {{TST|¶}}
| [[Mug]]s, largest elven cities, [[Highwood]] trees*
|-
| {{TST|§}}
| [[Restraint]]s, [[whip vine]]*
|-
| {{TST|▬}}
| [[Log]]s
|-
| {{TST|↨}}
| Some tree types
|-
| {{TST|↑}}
| Interface text (bridge direction), [[Pine]]* trees, [[Larch]]* trees
|-
| {{TST|↓}}
| Hungry/thirsty/drowsy/unhappy indicator, [[bridge]] placement raising direction indicator
|-
| {{TST|→}}
| Interface text (bridge direction)
|-
| {{TST|←}}
| Interface text (bridge direction)
|-
| {{TST|∟}}
| Withered [[plant]]s
|-
| {{TST|↔}}
|
|-
| {{TST|▲}}
| Head of [[ballista]] facing north, ramp up
|-
| {{TST|▼}}
| Head of ballista facing south, ramp down
|-
|}

====Row 03 (032-047)====
{|
|-
| {{TST| }}
| Spaces in text messages.
|-
| {{TST|!}}
| Strange [[mood]] mark, text
|-
| {{TST|"}}
| [[Shrub]], quotation marks, kobold's glowing eyes*
|-
| {{TST|#}}
| Chasm (bottom in fortress mode), pits, [[Sandstone]]*, [[Rock salt]]*, [[Basalt]]*, [[Gypsum]]*, [[floor grate]]s
|-
| {{TST|$}}
| [[Coin]]s
|-
| {{TST|%}}
| [[Prepared food]], unexplored underground, [[Siltstone]]*, [[Slate]]*, [[Brimstone]]*, [[Kimberlite ]]*, [[Bismuthinite]]*, [[Realgar]]*, [[Stibnite]]*, [[Marcasite]]*, [[Olivine]]*, [[Orthoclase]]*, [[Microcline]]*, [[Petrified wood]]*, [[Brimstone]]*, [[Pyrolusite]]*, [[screw pump]] in action
|-
| {{TST|&}}
| [[Demon]]s#
|-
| {{TST|'}}
| Rough [[floor]]s, unexplored underground, [[Claystone]]*, [[Rhyolite]]*, [[Periclase]]*
|-
| {{TST|(}}
| Foreign object opening tag, tile in [[bowyer's workshop]], text
|-
| {{TST|)}}
| Foreign object closing tag, text
|-
| {{TST|*}}
| [[Ore]], superior [[quality]] tags, key reference, working [[gear]] assembly
|-
| {{TST|+}}
| Smooth/constructed [[floor]]s, injured status, finely-crafted [[quality]] tags, text, [[block]]/[[metal|bar]] [[bridge]]
|-
| {{TST|,}}
| Rough [[floor]]s, [[Claystone]]*, unexplored underground, text
|-
| {{TST|-}}
| [[Scepter]]s, [[arrow]]s in flight, well-crafted [[quality]] tags, keyboard reference
|-
| {{TST|.}}
| Rough [[floor]]s, [[Felsite]]*, text, unexplored underground
|-
| {{TST|/}}
| [[Weapon]]s, [[bolt]]s
|-
|}

====Row 04 (048-063)====
{|
|-
| {{TST|0}}
| [[Coffin]]s, text
|-
| {{TST|1}}
|
|-
| {{TST|2}}
|
|-
| {{TST|3}}
|
|-
| {{TST|4}}
|
|-
| {{TST|5}}
|
|-
| {{TST|6}}
|
|-
| {{TST|7}}
|
|-
| {{TST|8}}
|
|-
| {{TST|9}}
|
|-
| {{TST|:}}
| [[Wild strawberry|Wild strawberries]]*, [[Prickle berry|Prickle berries]]*, snowstorms
|-
| {{TST|;}}
| [[Workshop]]s (which ones?)
|-
| {{TST|<}}
| [[Stairs]] up
|-
| {{TST|=}}
| [[Stockpile]]s, [[Chert]]*, [[Gneiss]]*, others?
|-
| {{TST|>}}
| [[Stairs]] down
|-
| {{TST|?}}
| "Task assigned" [[indicator]], looking for path
|-
|}
====Row 05 (064-079)====
{|
|-
| {{TST|@}}
| [[Sheriff]]#, berserk dwarf#, adventurer#, [[fortress guard]]#, [[royal guard]]#, dwarven [[merchant]]s#, [[caravan]] guards#
|-
| {{TST|A}}
| [[Alligator]]#, text
|-
| {{TST|B}}
| Bears#, text
|-
| {{TST|C}}
| [[Cow]]#, camels#, text
|-
| {{TST|D}}
| [[Dragon]]#, text
|-
| {{TST|E}}
| [[Elf]]#, [[elephant]]#, text
|-
| {{TST|F}}
| Text
|-
| {{TST|G}}
| Text
|-
| {{TST|H}}
| [[Horse]]#, text
|-
| {{TST|I}}
| [[Support]], text
|-
| {{TST|J}}
| Text
|-
| {{TST|K}}
| Text
|-
| {{TST|L}}
| [[Leopard]]#, text
|-
| {{TST|M}}
| [[Magma man]]#, [[mule]]#, [[muskox]]#, text
|-
| {{TST|N}}
| Text
|-
| {{TST|O}}
| [[Trade depot]] post, detailed/constructed wall by itself, text, wall ends
|-
|}
====Row 06 (080-095)====
{|
|-
| {{TST|P}}
| Text
|-
| {{TST|Q}}
| Text
|-
| {{TST|R}}
| Text
|-
| {{TST|S}}
| [[Sasquatch]]#, [[giant desert scorpion]]#, text
|-
| {{TST|T}}
| Text
|-
| {{TST|U}}
| [[Human]]#, [[Unicorn]]#, text
|-
| {{TST|V}}
| Text
|-
| {{TST|W}}
| Text
|-
| {{TST|X}}
| [[Bin]], [[floodgate]], shop post, building footprint, nausea/winded/stunned/unconscious/migrant [[indicator]], text, up/down stairs, keyboard cursor
|-
| {{TST|Y}}
| Text
|-
| {{TST|Z}}
| Sleep [[indicator]], text
|-
| {{TST|[}}
| [[Clothing]], [[armor]]
|-
| {{TST|\}}
|
|-
| {{TST|]}}
| Floor tile in [[Workshop|workshops]] and [[furnace|furnaces]]. Clothing?, armor?
|-
| {{TST|^}}
| [[Trap]], [[Alabaster]]*
|-
| {{TST|_}}
| [[Channel]] [[designation]], text
|-
|}

====Row 07 (096-111)====
{|
|-
| {{TST|`}}
| Rough floors, unexplored underground, [[Dolomite]]*, [[Schist]]*, [[Alunite]]*, [[Rutile]]*
|-
| {{TST|a}}
| [[Antman]]#, text
|-
| {{TST|b}}
| [[Batman]]#, text
|-
| {{TST|c}}
| [[Cat]]#, text
|-
| {{TST|d}}
| [[Dog]]#, text
|-
| {{TST|e}}
| Text
|-
| {{TST|f}}
| [[Frogman]]#, text
|-
| {{TST|g}}
| [[Goblin]]#, [[Mountain goat]]#, [[Gremlin]]#, text
|-
| {{TST|h}}
| [[Harpy]]#, text
|-
| {{TST|i}}
| [[Fire imp]]#, text
|-
| {{TST|j}}
| Text
|-
| {{TST|k}}
| [[Kobold]]#, text
|-
| {{TST|l}}
| Text
|-
| {{TST|m}}
| [[Mandrill]]#, [[vermin|mussel]], text
|-
| {{TST|n}}
| Text
|-
| {{TST|o}}
| Well construction, bridge construction, text, [[millstone]] in action, floor tile in magma [[furnace|furnaces]]
|-
|}

====Row 08 (112-127)====
{|
|-
| {{TST|p}}
| Text
|-
| {{TST|q}}
| Text
|-
| {{TST|r}}
| [[Ratman]]#, text
|-
| {{TST|s}}
| [[Snakeman]]#, [[Slugman]]#, [[Snailman]]#, text
|-
| {{TST|t}}
| [[Troglodyte]]#, text
|-
| {{TST|u}}
| Text
|-
| {{TST|v}}
| Text, [[Anhydrite]]*, [[Mica]]*
|-
| {{TST|w}}
| [[Wolf]]#, text
|-
| {{TST|x}}
| [[Saltpeter]]*, text
|-
| {{TST|y}}
| Text
|-
| {{TST|z}}
| Text
|-
| {{TST|{}}
| Forbidden opening tag
|-
| {{TST||}}
| [[Talc]]*
|-
| {{TST|}}}
| Forbidden closing tag
|-
| {{TST|~}}
| Unfinished rough stone [[road]], [[river]], [[magma]], [[flow]]s, dirt [[road]], [[farm plot]] under construction, [[sand]], furrowed soils
|-
| {{TST|⌂}}
| [[Animal trap]], low [[mountain]]s on world map, part of [[mechanic's workshop]]
|-
|}

====Row 09 (128-143)====
{|
|-
| {{TST|Ç}}
| [[Mechanism]]s
|-
| {{TST|ü}}
| Text
|-
| {{TST|é}}
| Text
|-
| {{TST|â}}
| Text
|-
| {{TST|ä}}
| Text
|-
| {{TST|à}}
| Text
|-
| {{TST|å}}
| Text
|-
| {{TST|ç}}
| [[Totem]]s
|-
| {{TST|ê}}
| Text
|-
| {{TST|ë}}
| Text
|-
| {{TST|è}}
| Text
|-
| {{TST|ï}}
| Text
|-
| {{TST|î}}
| Elven forest retreat
|-
| {{TST|ì}}
|
|-
| {{TST|Ä}}
|
|-
| {{TST|Å}}
| [[Idol]]s, text
|-
|}

====Row 10 (144-159)====
{|
|-
| {{TST|É}}
|
|-
| {{TST|æ}}
| [[Toy]]s
|-
| {{TST|Æ}}
| [[Coffer]]s, [[quiver]]s, [[backpack]]s
|-
| {{TST|ô}}
|
|-
| {{TST|ö}}
|
|-
| {{TST|ò}}
| Unactivated [[lever]]s, text
|-
| {{TST|û}}
| [[Bucket]], text
|-
| {{TST|ù}}
|
|-
| {{TST|ÿ}}
| [[Valley herb]]*
|
|-
| {{TST|Ö}}
|
|-
| {{TST|Ü}}
|
|-
| {{TST|¢}}
| Closed [[hatch]]es
|-
| {{TST|£}}
| Many valuable metals* in veins
|-
| {{TST|¥}}
| Lobster*
|-
| {{TST|₧}}
|
|-
| {{TST|ƒ}}
| [[Rope reed]]*
|
|-
|}

====Row 11 (160-175)====
{|
|-
| {{TST|á}}
|
|-
| {{TST|í}}
|
|-
| {{TST|ó}}
| Activated [[lever]]s, text
|-
| {{TST|ú}}
|
|-
| {{TST|ñ}}
|
|-
| {{TST|Ñ}}
|
|-
| {{TST|ª}}
|
|-
| {{TST|º}}
| [[Cloth]]
|-
| {{TST|¿}}
| [[Instrument]]
|-
| {{TST|⌐}}
| Withered [[plant]]s: [[Blade weed]], [[Dimple cup]]
|-
| {{TST|¬}}
|
|-
| {{TST|½}}
|
|-
| {{TST|¼}}
|
|-
| {{TST|¡}}
| [[Flask]], [[waterskin]]
|-
| {{TST|«}}
| [[Ballista arrow]] tail for west-facing ballistae, item with [[decoration]] tag
|-
| {{TST|»}}
| [[Ballista arrow]] tail for east-facing ballistae, item with [[decoration]] tag
|-
|}

====Row 12 (176-191)====
{|
|-
| {{TST|░}}
| Partially dug rock, [[miasma]], [[cave-in]] dust, [[steam]], smoke, [[Fishery]] & Butcher's workshops, [[Jet]]*, [[Chalk]]*, [[Diorite]]*, various soils*
|-
| {{TST|▒}}
| Partially dug rock, [[miasma]], [[cave-in]] dust, [[steam]], smoke, workshops (craftdwarf's, bowyer's, mason's, mechanic's, jeweler's, clothier's, [[kitchen]], and leather works), side tiles for catapult, [[window]], [[Gabbro]]*, [[Obsidian]]*, various soils*
|-
| {{TST|▓}}
| Partially dug rock, [[miasma]], [[cave-in]] dust, [[steam]], smoke, tannery, [[Marble]]*, [[Limestone]]*, [[Flint]]*, [[Granite]]*, various soils*
|-
| {{TST|│}}
| Overworld [[river]]s, [[well]] [[chain]]/[[rope]], rotating [[axle]]s
|-
| {{TST|┤}}
| Overworld [[river]]s, top-right tile for [[Loom]], glumprong [[tree]]*
|-
| {{TST|╡}}
| Tree in winter, [[bridge]]s
|-
| {{TST|╢}}
|
|-
| {{TST|╖}}
| Ends of smooth walls
|-
| {{TST|╕}}
| Ends of smooth walls
|-
| {{TST|╣}}
| Smooth/constructed walls
|-
| {{TST|║}}
| Smooth/constructed walls, [[bridge]]s, wooden [[door]]s, [[axle]]s
|-
| {{TST|╗}}
| Smooth/constructed walls, bridges
|-
| {{TST|╝}}
| Smooth/constructed walls, bridges
|-
| {{TST|╜}}
| Ends of smooth walls
|-
| {{TST|╛}}
| Ends of smooth walls
|-
| {{TST|┐}}
| Overworld [[river]]s
|-
|}

====Row 13 (192-207)====
{|
|-
| {{TST|└}}
| Overworld rivers
|-
| {{TST|┴}}
| Overworld rivers
|-
| {{TST|┬}}
| Overworld rivers
|-
| {{TST|├}}
| Overworld rivers, top-left tile for [[Loom]]
|-
| {{TST|─}}
| Overworld rivers, rotating [[axle]]s
|-
| {{TST|┼}}
| [[Door]]s, overworld rivers, floor detailing/[[engraving]] in progress
|-
| {{TST|╞}}
| Bridges, trees in winter, [[catapult]] tile
|-
| {{TST|╟}}
|
|-
| {{TST|╚}}
| Smooth/constructed walls, bridges
|-
| {{TST|╔}}
| Smooth/constructed walls, bridges
|-
| {{TST|╩}}
| Smooth/constructed walls
|-
| {{TST|╦}}
| Smooth/constructed walls
|-
| {{TST|╠}}
| Smooth/constructed walls
|-
| {{TST|═}}
| Smooth/constructed walls, bridges, planted [[crop]]s, center [[catapult]] tile, [[axle]]s
|-
| {{TST|╬}}
| Smooth/constructed walls, bridges, [[fortification]]s, (flashing) wall [[detailing]]/[[engraving]]/fortifying in progress
|-
| {{TST|╧}}
|
|-
|}
====Row 14 (208-223)====
{|
|-
| {{TST|╨}}
| Bridges
|-
| {{TST|╤}}
| [[Table]]
|-
| {{TST|╥}}
| [[Chair]]s, bridges, farmer's workshop bottom-middle tile
|-
| {{TST|╙}}
| Ends of smooth walls
|-
| {{TST|╘}}
| Ends of smooth walls
|-
| {{TST|╒}}
| Ends of smooth walls
|-
| {{TST|╓}}
| Ends of smooth walls
|-
| {{TST|╫}}
| Some types of floodgates (wood?){{verify}}
|-
| {{TST|╪}}
| Metal doors
|-
| {{TST|┘}}
| Overworld [[river]]s
|-
| {{TST|┌}}
| Overworld rivers
|-
| {{TST|█}}
| Any solid color tile
|-
| {{TST|▄}}
| Siege engine parts
|-
| {{TST|▌}}
| [[Ballista]]
|-
| {{TST|▐}}
| Ballista
|-
| {{TST|▀}}
|
|-
|}

====Row 15 (224-239)====
{|
|-
| {{TST|α}}
| [[Fish]], top-center [[fishery]] tile, [[meat]]
|-
| {{TST|ß}}
| [[Leather]]
|-
| {{TST|Γ}}
| [[Weight]] symbol, candlenet [[tree]]*, mango tree*, rubber tree*, cacao tree*, palm tree*, kapok tree*
|-
| {{TST|π}}
| [[Cabinet]], [[goblin|dark fortress]]es
|-
| {{TST|Σ}}
| [[Trap component]]
|-
| {{TST|σ}}
| [[Anvil]], metalsmith's and magma forge bottom-middle tile
|-
| {{TST|µ}}
| [[Plant]]s*(which?), [[crown]], ruins on world map
|-
| {{TST|τ}}
| [[Pig tail]]s*, [[Tree]] sapling, [[Blade weed]]
|-
| {{TST|Φ}}
| [[Sweet pod]]s*, [[bloated tuber]]*
|-
| {{TST|Θ}}
| [[Bed]]s, [[Puddingstone]]*
|-
| {{TST|Ω}}
| [[Statue]]s, dwarven cities on map, [[fish|sea nettle jellyfish]]
|-
| {{TST|δ}}
| [[Earring]]s, [[kennel]] tile
|-
| {{TST|∞}}
| [[Boulder]], middle-right [[butcher's shop]] tile, [[Andesite]]*, [[Conglomerate]]*
|-
| {{TST|φ}}
| [[Thread]], [[loom]] bottom left tile, farmer's workshop bottom right tile
|-
| {{TST|ε}}
| [[Bowyer's workshop]] middle-right tile
|-
| {{TST|∩}}
| [[Hills]] on world map
|-
|}

====Row 16 (240-255)====
{|
|-
| {{TST|≡}}
| [[metal|Bar]]s, excellent [[quality]] symbol, [[zone]]s, metal [[floodgate]]s
|-
| {{TST|±}}
| Unfinished [[road]]
|-
| {{TST|≥}}
| Spent ammo (catapult stones count), [[ashes]]
|-
| {{TST|≤}}
| Spent ammo (catapult stones count), ashes
|-
| {{TST|⌠}}
| Willow [[tree]]*
|-
| {{TST|⌡}}
|
|-
| {{TST|÷}}
| [[Barrel]], [[screw pump]]
|-
| {{TST|≈}}
| Rough stone [[road]] or [[bridge]], [[water]], [[river]], [[lava]], glob, [[fat]], [[tallow]], [[farm plot]], furrowed soil, [[vomit]], [[blood]] pools, others?
|-
| {{TST|°}}
| [[Ring]], sea foam
|-
| {{TST|∙}}
| [[Vermin]]*, terrain at lower elevation
|-
| {{TST|·}}
| [[Seed]]s, micro-vermin, distant indoors terrain$ (changed by the 'chasm' option in init.txt)
|-
| {{TST|√}}
| [[Weapon rack]]s, [[badlands]] in main map, check mark (selecting production materials, confirmed items on manager window)
|-
| {{TST|ⁿ}}
| [[Savanna]] in main map
|-
| {{TST|²}}
| Body parts, [[chunk]]s, vermin corpses, [[bone]], [[shell]], [[skin]]s, [[skull]]s
|-
| {{TST|■}}
| [[Block]]s, trees at lower elevation
|-
|
| No use
|}



{{Game Interface FAQ}}

[[Category:Modding]]
[[Category:Interface]]

40d:Waterskin

2008-08-03T20:49:29Z

Adeptable: add Category:Items and Category:Military

'''Waterskins''' are made at a [[Leather works]] from any form of [[Leather]]. [[Soldier]]s can be ordered to carry [[water]] using their waterskins from their specific squad menu. This is useful because they will not have to leave their post to get a drink for an extended period of time. This can also be bad because they will only fill their skin with water, and eventually will become unhappy due to [[alcohol]] deprivation. When filling a waterskin a soldier or a hunter will always fill it to the level of 3 units of water.

When in adventurer mode the water in the waterskin will freeze after some time in very cold weather. The resulting ice can be licked instead of drunk but
doesn't quench thirst nor melt from this action.

Waterskins are stored as in Finished Goods [[stockpiles]] as [[flask|flasks]]. Three waterskins are made at the leatherworks from one unit of leather.

[[Category:Items]]
[[Category:Military]]

v0.34:Trading/Flowchart

2008-08-03T02:02:59Z

Adeptable: update flowchart - use new templates for clearer code, and split Liason int it's own branch

{| cellspacing="0" align="right" style="margin:0 0 15px 30px;"
|-
!colspan=15|Suggested trading procedure
|-
|
|-
|width=50|
|width=1|
|width=50|
|width=5|
|width=50|
|width=1|
|width=50|
|width=5|
|width=50|
|width=1|
|width=50|
|width=5|
|width=50|
|width=1|
|width=50|
|-
|colspan=6|
|colspan=3 style="border: 1px solid #aaa;" align=center|Arrive at fortress location
|colspan=6|
|-
|colspan=7|
{{Flowchart Vertical Bar}}
|colspan=7|
|-
|
{{Flowchart Horizontal Bar|13}}
|
|-
|
{{Flowchart Vertical Bar}}
|colspan=7|
{{Flowchart Vertical Bar}}
|colspan=3|
{{Flowchart Vertical Bar}}
|
|-
{{Flowchart Box|Create Goods|5}}
|colspan=5|
{{Flowchart Box|Build Depot}}
|
{{Flowchart Box|Optional: turn off the relevent noble's other labours for a faster response. (Dwarven caravan requires expedition leader/mayor; Human caravan requires broker)|11}}
|-
|colspan=6|
{{Flowchart Vertical Bar}}
|colspan=2|
|-
|colspan=5|
{{Flowchart Box|Check Depot is accessible}}
|
|-
|colspan=6|
{{Flowchart Vertical Bar}}
|
|-
|colspan=5|
{{Flowchart Box|Wait for caravan}}
|-
|
{{Flowchart Vertical Bar}}
|colspan=7|
{{Flowchart Vertical Bar}}
|
|-
|
{{Flowchart Horizontal Bar|9}}
|
|-
|colspan=5|
{{Flowchart Vertical Bar}}
|colspan=5|
|-
|
{{Flowchart Horizontal Bar|9}}
|
|-
|
{{Flowchart Vertical Bar}}
|colspan=3|
{{Flowchart Vertical Bar}}
|colspan=3|
{{Flowchart Vertical Bar}}
|
|-
{{Flowchart Box|Set goods to be traded}}
|
{{Flowchart Box|Request the trader at the depot. Optional: turn off his other labours for a faster response}}
|
{{Flowchart Box|Wait for caravan to arrive at depot and merchants to finish unloading|3}}
|-
|
{{Flowchart Vertical Bar}}
|colspan=3|
{{Flowchart Vertical Bar}}
|colspan=2|
|colspan=2|
{{Flowchart Vertical Bar}}
|
|-
{{Flowchart Box|Wait for goods to be hauled}}
|
{{Flowchart Box|Wait for trader to assign "Trade at Depot" job}}
|
|
{{Flowchart Box|Conduct all 8 meetings with Liason}}
|-
|
{{Flowchart Vertical Bar}}
|colspan=3|
{{Flowchart Vertical Bar}}
|colspan=3|
{{Flowchart Vertical Bar}}
|
|-
|
{{Flowchart Horizontal Bar|9}}
|
|-
|colspan=5|
{{Flowchart Vertical Bar}}
|colspan=5|
|-
|colspan=4|
{{Flowchart Box|Trade}}
|colspan=4|
|}