Dwarf Fortress Wiki - User contributions [en]

Martial trance

2024-09-15T12:13:48Z

Xjtu-blacksmith: add two links

{{Quality|Superior}}
{{av}}
[[File:martial_status_icon_preview.png|right]]
[[Dwarves]] enter a '''martial trance''' when fighting multiple enemies at once. The trance offers a boost to the dwarf's abilities – a dwarf in a martial trance has a significantly increased chance of blocking or parrying an attack, and is more likely to hit their opponent. However, it does not give a direct damage bonus like '''enraged'''. The [[status icon]] for a dwarf in a trance is {{Tile|!|2:1}} which will flash over their [[Status icon|icon]]. A dwarf also appears to occasionally enter a trance even when not fighting, though this behavior is rare and may be a bug.
[[Image:Champions.png|150px|thumb|right| The aftermath of a dwarf in martial trance.]]
Dwarves are the only creatures which enter martial trances without [[modding]]. The RAW tag which determines this is {{token|TRANCES}}. A dwarven adventurer may also enter a martial trance in [[adventurer mode]]. Fresh recruits can, when pressed to fight, go into a martial trance as well.

This is also a great way to dispose of [[Bogeyman|bogeymen]] in adventurer mode, as you can dodge most of their attacks, and most of your attacks will land successfully, regardless of the difficulty of the shot.

[[File:dwarf_monk.jpg|thumb|300px|center|This dwarf found his chi. ''Art by The-Fronti'']]

[[ru:Martial_trance]]
[[zh:Martial trance]]
{{Category|Dwarves}}

Trading

2024-09-08T07:12:46Z

Xjtu-blacksmith: /* Elven */ layout

{{Quality|Exceptional}}
{{av}}
{{buggy}}
[[File:trading_icon_preview.png|right]]'''Trading''' in ''Dwarf Fortress'' allows your dwarves to trade with friendly [[civilization]]s. They can barter their excess goods for items they need, possibly even items they can't otherwise acquire for themselves. Trade can make up for the lack of [[Industry|industries]] you neglected or don't find interesting, provide resources that aren't available where your dwarves settled, replace key tools you lost or accidentally destroyed, and allow you more freedom in selecting starting gear and skills at [[embark]]. Trading generally begins in the first [[Calendar|autumn]] after establishing your fortress, with the arrival of the [[dwarf|dwarven]] [[caravan]] from your home [[civilization]].

'''Trader''' is the generic term used at your [[trade depot]] to refer to your fortress representative (usually your [[broker]], although it can be anyone else in a pinch) when dealing with merchants in a visiting caravan. As a [[profession]], the term applies to visiting merchants and dwarves whose highest [[skill]] is [[Appraiser]].

To trade at all, you will need a [[trade depot]] and peaceful relations with at least one [[civilization]] that can reach your site. Appointing a citizen as a [[broker]] is not strictly necessary but is very helpful. Newly-founded fortresses begin the game at peace with their home civilization and will generally have at least that one trading partner each year, unless the parent civilization is [[Civilization#Dead and struggling civilizations|dead or dying]], or simply can't reach your site due to intervening mountains or open water. A [[civil war]] in your home civilization will also stop trade with them. Trading with your home civilization is quite important, as being visited by their caravans is part of attracting [[Immigration|immigrants]] after the first two waves.

Graphically, merchants will always appear in white clothing.
==Trading flowchart ==
{{:Trading/Flowchart}}

{{Clear}}

== Trade depot ==

{{Dual image
|premium=File:DFwikiGraphicalTradeDepot.png
|classic=File:DFwikiASCIITradeDepot.png
|width=150px
|caption=A Trade Depot
}}

{{Main|Trade depot}}
Building a [[trade depot]] is a prerequisite for trade with caravans that arrive at your fortress. If traders can't access your trade depot when they show up, their caravans will simply bypass your fortress that year. While it may be convenient to build a depot outside at first, it is usually a good idea to move it inside, or secure it with [[wall]]s, [[bridge]]s and other fortifications, to protect incoming caravans and your goods from [[steals drink|thirsty animals]], [[thief|thieves]], and [[goblin]]s.

Everything that is on your map belongs to you, except:
* the items that are on merchants' animals and wagons
* the items that are in the trade depot (they belong to the caravan until they are moved out of it)
* items worn by creatures that are not [[citizen]]s of your fortress (initially forbidden, but can be claimed via unforbidding and dumping them)

== Trading ==
[[File:merchant_v50_preview.png|right]]
{{Dual image
|premium=File:DFwikiTradeScreen.png
|classic=File:DFwikiASCITradeScreen.png
|width=300px
|caption=Trading screen
}}

Before you can begin trading, you need to designate what goods to trade and have the fortress's representative trader located at the [[trade depot]]. Select the trade depot and then click either "Broker requested at depot" or "Anyone requested at depot" if you have no [[broker]] [[noble]] assigned. Be aware that without an assigned [[broker]], it's likely a random, probably unskilled dwarf will volunteer to conduct the trade. Next click "Move goods to/from depot" to be presented with a list of all items in your fortress that belong to you. Mark the goods you want to sell --insert clever advice--, and your dwarves will begin moving them to the depot. If you are unsure about which goods are in which containers, clicking the bin or barrel within the menu will show every item that is stored inside, along with its perceived value (using your broker's [[Appraisal]] skill). However, individual items cannot be marked if they are in a container. Note that during this step, we are just moving the goods physically to the trade depot, and that containers like [[barrels]] and [[bins]] must be moved with all of their contents (although for bins you will have an opportunity to specify which contained items you wish to trade).

Once the trade goods are moved to the depot and your trader has arrived, select the depot again and finally click the "Trade" button to enter the trade menu. In the trade menu, select the items to offer from the right and the desired items from the left. All caravans have a weight limit which cannot be exceeded, and the allowed additional weight is displayed in the lower left corner. If your trader has sufficient [[Appraisal]] skill, the value of all items will be displayed with reasonable accuracy. Once the proposal is ready, click the "Trade" button to propose the trade; merchants will not agree unless they make adequate profit. Clicking the "Offer as gift" button instead will make a gift of the selected items. The amount of acceptable profit is determined by the trader's [[Broker skills|skills]] and the merchant's mood, described below. Merchants may attempt to propose counteroffers if they do not accept the proposal, which can then be accepted, rejected, or further amended by the trader. If the Trader Profit is listed in green rather than yellow or red the trade will always be accepted.{{Verify}}

With more experienced traders and pleased merchants, even marginally profitable trades can be successful, and counterproposals can be rejected safely, offering the same trade again. Note however that a low profit margin for the traders may not be desirable - it has been suggested that both export and profit numbers influence the size of next year's caravan and, in the case of the dwarven caravan, immigration numbers.{{Verify}}

Note: Goods brought by caravans rarely have base quality higher than superior, and decorations on a good rarely exceed superior as well.

Note if you give or trade away an [[Artifact|artifact]], you will receive a special notification:
;[[File:Treasure_Gift.PNG|750px]]
;[[File:Treasure_Trade.PNG|750px]]

=== Items cue colors ===
{| class="wikitable"
! {{DFtext|Brown|6:0}}
| Items have been created (or modified) by your fortress. They can be traded away or offered as a gift.
|-
! {{DFtext|Gray|7:0}}
| Items were created by another source. They can be traded, but if one of these items has been selected, the entire selection cannot be offered as a gift.
|-
! {{DFtext|Purple|5:0}}
| Items are under a no-export mandate. If they are traded away it will result in disciplinary action (see [[justice]]) against the dwarf that brought the item to the depot.
|-
! {{DFtext|Green|2:0}}
| Items have just been gifted to the caravan and they will not trade it back.
|-
! {{DFtext|Red|4:0}}
| Items have been seized from another caravan and cannot be traded as is; you will need to decorate them or turn them into other items for them to become "valid" trading items.
|}

Note that containers (barrels, bins, etc.) will be displayed according to the origin of the ''container'', not the contents. So a foreign barrel holding locally-produced beer will display as foreign (white). Once you {{k|v}}iew the container, the locally-made contents are displayed as local (brown).

=== Seizing items ===

Clicking "Seize" from the trade menu will seize the selected items of the merchant's. If you seize goods from a caravan, the merchant will respond "Take what you want. I can't stop you." and then leave immediately without the seized goods. Items cannot be seized from the dwarven caravan, and other races will not buy goods stolen from one of their caravans (then marked in red) unless they are tricked into asking for them via counteroffer, or the items are "laundered" by decoration or used to create other goods. Seizing goods will hurt diplomatic relations, but is not grounds for an automatic [[siege]].

Pressing the seize button while no goods are selected will result in the merchant interpreting your seizure as a joke. This apparently does nothing to benefit or hinder your trading.

As a side note, if you deconstruct your trade depot with a caravan in it, all the caravan's items will drop to the ground, to be readily hauled away by your dwarves. This does not mark the items as stolen, and the caravan will leave. However, ''next'' year's caravan is partly based on the profits from the previous year - so if you are relying on that race's caravans for needed items, you're hurting yourself in the long run.

Trying to interrogate a merchant can also cause a wagon to fall apart.

Another way to steal without marking as stolen is to forbid the trade depot just before they leave, causing them to leave their goods at the depot.

If you're using the search plugin for [[Utility:DFHack|DFHack]] (e.g. from the [[Utility:Lazy Newb Pack|Lazy Newb Pack]]), be warned that {{K|s}} means "seize" and '''NOT''' "search", and there is '''no warning''' for it. Use {{K|q}} to search the merchant's goods and {{K|w}} to search yours.

Note that the civilization attached to a particular caravan will keep track of the value of items the caravan was carrying when they set out to trade, and they will compare this value with the value of items they return home with. Regardless of what method you use to confiscate items from a caravan, even if you came to possess the goods through no fault of your own (an [[ambush]] killed the traders and guards, for example) the parent civilization may decide that you stole from them and send a [[siege]] instead of a caravan the following year. It is prudent to take measures to protect caravans visiting your lands!

===Offering items===

You can also give away items, as gifts to the leaders of the [[civilization]] you are trading with. This presumably helps relations between yourself and the other faction, though there is not yet a clear correlation between the value of the offerings and the improvement to relations. The exact effects of offerings on trading are unknown but it is believed due to the offerings' net trade value being counted towards the merchants' profit, possibly with a modifier (possibly a multiplier of more than 1 as a bonus or less than 1 to compensate for the improved relations){{Verify}}, which in turn increases the quantity and variety of trade goods brought by next year's caravan. Also the [[Monarch]] requires offerings to be made before their arrival. You cannot offer items that were not made at your fortress; the merchants do not want your spare [[Goblinite]] clothes.

The value of an offering for the purpose of becoming the capital is adjusted by your current export agreement.

Unless you are looking for [[fun]], under no conditions should you offer or trade items which involve animal products, wood, or used wood in their creation (clear glass, for example) to [[elves]], as they will refuse the trade, take offense, and leave, possibly damaging relations enough to provoke a war between you and the elven civilization you traded with. They will accept their own "grown wood" items in trade without insult, however. See below and the [[elves]] page for more detailed information.

== Miscellaneous trading advice ==
* Thieves and thieving critters tend to follow caravans. Expect assaults and intruders.
* Create your trading depot inside your fort, preferably in the beginning. Place a 3-tile wide path—which must be free of obstructions such as stairways, traps, minecart tracks and boulders (not stones)—to the entrance of the fort and position war-trained animals along it (chains do not block wagons); this will help to protect the traders and keep the depot close to your supplies.
* Avoid having multiple wagon paths to your depot. Caravan [[wagon]]s cannot move through each other, and if two wagons happen to meet at a fork they may become gridlocked against each other, resulting in the destruction of wagons and loss of trade opportunities.
* All caravans will bring extra food (meat and edible plants), wooden logs, and cloth/leather (for making clothes) if the supplies of your fortress are low enough, independent of whether or not you requested them. This does not apply in the case that the weight limit is exceeded by (other) items you requested. The supply situation, as observed by traders, is based solely on the number of unforbidden items in your fortress, stockpiled or not; thus, it is possible to trick caravans into thinking your supplies are low by [[forbid]]ding all of your relevant stocks immediately prior to their arrival.
**In order to '''avoid''' this behavior, you should make sure that, for each dwarf in your fortress, you have the following ''unforbidden'' items:
*** 5 pieces of food - meat, fish, plants, or "other" in your [[Status]] screen (even though "other" includes inedible items)
*** 1 wood log
*** 5 pieces of cloth, pieces of leather, or complete sets of [[wear|pristine]] clothing (shirt+pants+shoe)
* Define your trade depot as a burrow. When traders arrive, you can add your broker or another dwarf, perhaps one you want to train in trading, to the burrow. They will head to the depot immediately, and stay there until you remove them from the burrow.
* Each trade you make (regardless of value) will increase your trader's skills by 50, distributed among Comedian, Judge of Intent, Negotiator, and Persuader. Each skill seems to gain around 5-15 experience points, but the sum will always be 50. The skill gain occurs as soon as the "t" button is pressed - if the offer is rejected, the dwarf will still gain 50 points. If the same offer is subsequently accepted, no additional skill will be gained.
* Selecting "only broker may trade" ensures that you will start negotiations with a decently-skilled trader, but it may require a significant delay if your broker is far away (or is busy with other tasks). Selecting "anyone can trade" will ensure that you get the trading done quickly, but at the cost of all item trade values being extremely inaccurate. Once your fortress can produce enough goods to reliably buy out the whole caravan, waiting for your broker is less important; allowing your commoners to trade spreads out the trading skill gains and eliminates the micromanagement of trying to get your broker to the depot in a timely manner.

== Types of Merchant Caravans==
By default, each friendly [[civilization]] (including your own) will send one merchant [[caravan]] per year. Each race always trades in a particular season: autumn for dwarves, spring for elves, and summer for humans. (No race trades in winter by default.) If you have friendly contact with multiple civilizations of the same race, you may even get multiple caravans in a single season. Each race brings different goods, and they sometimes have different trading preferences.

If your fortress was founded in spring, it is highly unlikely that you will receive an elven caravan that spring, and it is uncommon for a human caravan your first summer, so probably your first and only caravan your first year will be the dwarven one. Caravans will only show up if that race considers the fortress site accessible (as denoted on the embark screen) and "worth the effort" (as determined by the [[Entity token#PROGRESS_TRIGGER_POPULATION|[PROGRESS_TRIGGER_*]]] tokens in the entity definition), with the exception of dwarves, who always arrive unless they are [[extinct]].

=== Dwarven ===
{{quote|
: ''Greetings from the mountainhome. Your efforts are legend there. Let us trade!''
:: (Or, if your fort ''is'' the [[Fortress|mountainhome]]...)
: ''Greetings from the outer lands. Your efforts are legend there. Let us trade!}}

Typically, the first caravan you receive is the [[Dwarves|dwarven]] one from your home civilization, giving you at least 22 weeks to prepare (assuming you started mid-spring, the default). This does require that you are on the same continent as they are, and you are not isolated by mountains or bodies of water.

The dwarven caravan:
* arrives in [[Calendar|autumn]].
* carries metal bars, [[leather]], weapons and armor, food and booze, and more. Dwarves alone may bring [[steel]] and steel goods.
:* If the trading civilization does not have access to [[iron]], they can still bring steel (and steel goods) and [[pig iron]] bars, but will not bring iron products.
* usually carries a selection of books that your civilization has access to. This can include books written in previous forts of yours within the same civilization.
* is heavily guarded.

The dwarven caravan from your home civilization:
* sends a liaison who will speak with the [[Expedition leader]], [[Mayor]], [[Baron]], [[Count]], or [[Duke]] to negotiate an import-export agreement (unless the [[Monarch]] is present).
* influences the number of immigrants received (if the caravan leaves intact).
* will not cause sieges when repeatedly destroyed or lost.
* is the only caravan to arrive during a fortress' first year.
* always arrives, regardless of embark location, unless the dwarven civilization is [[extinct]].
* cannot have its goods seized from the trade menu.
* may not arrive if your civilization lacks any notable figures.
* cannot be offered goods if the monarch is present.

=== Elven ===
{{quote|Greetings. We are enchanted by your more ethical works. We've come to trade.}}
[[Image:Evil_elves.png|thumb|400px|A typical elven caravan.]]

Friendly [[elf|elven]] civilizations will each send a caravan sometime in [[Calendar|spring]], giving you about a full year before the first caravan arrives when starting at the default time.

The elven caravan:
* arrives in the [[Calendar|spring]].
* carries [[cloth]], [[rope]]s, various above-ground seeds, [[plant]]s and their byproducts, [[log]]s, [[wood]]en goods & [[weapon]]s, clothing and [[armor]], and may carry tame exotic [[creature]]s.
* does not use [[wagon]]s, only [[Creature#Domestic animals|pack animals]]
* is unguarded.
* will become angry and immediately leave if offered "unethical" wooden or animal products; see [[Trading#Unacceptable items|below]].

Elven caravans don't use wagons, instead bringing all of their goods on pack animals. This means that they don't need any special accommodation to get to the [[trade depot]]: any untrapped one-tile-wide path will suffice. However, this also means that elven caravans have a much lower weight limit, which means selling them heavy items like [[furniture]] or large [[stone]] goods can be problematic. Their caravans are also unguarded, and may need protection if your fortress is in a [[Surroundings|dangerous environment]] or [[Siege|under attack]].

Elves will only ever have goods made from above-ground plants, goods made from their special "grown" wood, or various exotic [[creature]]s or [[vermin]] in grown wooden [[cage]]s. The possibility of getting a breeding pair of [[giant tiger]]s is nice, although they might just bring something useless like [[raven]]s or [[Green tree frog|tree frog]]s instead. If you trade with elves for unusual [[plant]] [[crop]]s, you may be able to [[brew]] or [[Millstone|otherwise]] [[Farmer's workshop|process]] those plants for [[seed]]s you can later grow in your own [[Tile attributes|above-ground]] [[Farming|farm]]s, if you live in a compatible [[biome]]. Elves also wear and sell the same-sized [[clothing]] as dwarves, if you haven't gotten your [[textile industry]] going yet. Otherwise, food, logs, cloth, or miscellaneous wooden goods like [[cage]]s, [[barrel]]s, and [[bucket]]s can be useful.

Elves don't forge [[metal]]. All of their [[weapon]]s and [[armor]] are made from [[wood]], including item types that dwarves can't normally make from wood, like [[spear]]s or different [[sword]] varieties. These are even less useful than most arms and armor sold by caravans, as wooden weapons and armor are [[Material science#Material and item properties|basically useless in combat]]. Even metal-poor dwarves can cheaply make superior arms and armor from bone or leather. It's probably for the best that elves are so poorly armed, because offending them and damaging your [[Diplomacy|diplomatic relationship]] with their civilization is very easy.

==== Unacceptable items ====
Elves [[Elf#Ethics|view]] living trees as sacred and dislike the killing of non-hostile animals; they're the only [[Ethic#Ethics of vanilla civilizations|unmodded civilization]] to do so. Offering them wood or animal-derived products, either as part of a trade or as a gift, will offend the merchant. The merchant will rebuke your broker and leave immediately. This offense reduces your [[civilization]]'s [[Diplomacy|diplomatic relationship]] with the elves' civilization, possibly leading to [[war]] after multiple infractions.

Examine your items carefully! Elf traders will reject [[container]]s holding a prohibited item, otherwise-acceptable items stored in a prohibited container, and all items «[[decoration|decorated]]» with a prohibited [[material]]. If you want to sell food or liquid to elves, it's best to use a [[large pot]] or one of their own grown wood barrels.

Note that elves only care about the items they are actually offered. It's perfectly allowable to use wooden [[bin]]s to haul items to the [[trade depot]], as long as you only offer the elves acceptable items from the bin and not the bins themselves.

===== Items made from wood =====
{{quote|Once a beautiful tree, and now? It is a rude bauble, fit only for your kind.}}
Elves do not want to be offered items you made from wood, nor do they want most items that require wood as part of their creation process.
* All items made of or decorated with [[wood]]. This includes wood from [[Tree#Underground trees|tree-like subterranean fungus]], such as [[tower-cap]]s. Elves make an exception for the "grown" wood items they make themselves, but items made by other races using "grown" wooden logs are still not acceptable.
* All items made of or decorated with wood derivatives. This includes [[ash]], [[potash]], [[pearlash]], [[charcoal]], and [[lye]]. Note the exception for ash-[[glaze]]d [[earthenware]] below, however.
* Items made from or decorated with clear or crystal [[glass]], as these items require [[pearlash]] in their creation. Again, note the exception for raw or cut glass [[gem]]s below.
* [[Obsidian]] [[short sword]]s. These require wood in their production, for the handle.

===== Animal products =====
{{quote|I see your low race still revels in death. That poor, gentle creature...}}
Elves also reject the majority of animal products. (This taboo extends to items made from intelligent creatures, despite the fact that you may see elven [[historical figure]]s hypocritically wearing items made from the hair or bones of their enemies.)
* Items and decorations made from [[body parts]], such as [[hair]], [[bone]]/[[skull]], [[shell]], [[horn]]/hoof/antler, and [[ivory]]/[[tooth]]. It also includes items dwarves can't normally use for crafting, such as [[nail]]s, [[chitin]], and [[scale]]s.
* [[Leather]] or [[parchment]]/vellum, and all items made from them. These are made from [[skin]]s.
* [[Wool]] [[yarn]] and [[cloth]], as well as all items made from them. Elves have never heard of [[shearing]], so it doesn't matter how well you treat your [[sheep]]; they still associate animal products with death.
* [[Meat]] (including [[prepared organs]]), [[fish]] (both raw and prepared), [[fat]], and [[tallow]]
* [[Egg]]s. Elves aren't keen on keeping chickens, either.
* [[Prepared meals]] made using any of the above products.
* Tallow [[soap]]
* [[Corpse]]s and [[body parts]] themselves, although these are usually worthless anyway.
* [[Blood]], even if you somehow manage to get it into an elf-friendly container.

A distinct retort awaits dwarves who are so tactless as to offer goods made from both wood products '''and''' animal products at the same time (such as tallow soap, or an item decorated with both wood and bone):
{{quote|You truly despise life, don't you? I am beside myself with grief. Perhaps we will show you how they suffered.}}

===== Acceptable items =====
Any item that isn't specifically prohibited above is acceptable to elves. A non-exhaustive list of items they accept:

* The "Feather Tree Egg Yolk" that the elves litter your trade depot with, can be traded back to them. Useful free trade items if you're looking to level another broker.
* Items made from or decorated with [[stone]], as well as raw [[clay]] or raw [[sand]]. This includes items made from [[petrified wood]], [[lignite]], or [[bituminous coal]]; elves aren't concerned with items that were plants or animals in a different geological age.
** [[Gizzard stone]]s are acceptable. Elves can't tell them from any other object made of stone.
* Items made from or decorated with [[metal]] (including [[steel]]), green [[glass]], or [[ceramic]]. Elves are content to assume your dwarves fuel their craft with [[coke]] and [[magma]] rather than [[charcoal]].
* All rough gems and cut gems, as well as items and decorations made from [[gem]] materials. Note that clear glass and crystal glass are not gem materials and are generally not acceptable, even though they can be used for [[Gem setting|gem decoration]]s and gem [[craft]]s.
** Due to a long-standing bug{{bug|919}}, elves do not examine the material rough gems or cut gems are made of. You can safely sell them raw clear or crystal glass, or cut gems made from clear or crystal glass, as long as you haven't used those gems for decorations. Be careful, because clear or crystal glass [[craft]]s from the "cut gems" job, including "large" gems, are still unacceptable.
* [[Plant]] and fungus products in general. Unless otherwise prohibited, all of these items are acceptable either as themselves or as the material for an item or decoration:
** Plant [[crop]]s, [[fruit]]/pods, [[seed]]s/nuts, and [[leaf|leaves]]/bulbs/flowers. Anything that can be grown on a [[farm plot]] or harvested with [[herbalism]] is one of these four. This includes non-wooden produce from trees.
** [[Plant fiber]] [[thread]] and [[cloth]], and all items made from them.
** Processed plant products. This includes (but isn't limited to) [[booze]], [[dye]], [[flour]], [[dwarven sugar]] and [[dwarven syrup]], [[oil]], [[press cake]], and [[paper]]. [[Papyrus]] sheets seem to be a notable exception.
* [[Silk]] [[thread]] and [[cloth]] and items made from them. Elves don't care if you're exploiting spiders.
* Products of the [[beekeeping industry]], including [[honey]], [[royal jelly]], [[mead]], [[wax]], and wax [[craft]]s.
* [[Cheese]] and [[milk]]
* [[Prepared meal]]s made entirely with allowed ingredients.
* "Grown" wood items. These can generally only be obtained from elves, and are made in keeping with elven ethics. Note that these items can still become unacceptable if they contain unacceptable items or are later decorated with unacceptable materials.
* Items made from [[Adamantine|certain]] [[Divine metal|spoiler]] [[Divine fabric|materials]], if you're willing to give these up.
* Live [[creature]]s or [[vermin]]. Since these can only be traded when in a [[cage]] or [[animal trap]], make sure the cage or trap is also made of acceptable materials.
* [[Soap]] made from [[oil]]. This may be a bug{{bug|8571}}, as even plant-based soap requires [[lye]], which is made from [[ash]].
* Otherwise-acceptable items are not disqualified by [[ash]] [[glaze]], which may be a bug{{bug|4652}}.

=== Human ===
{{quote|Greetings. The craftsdwarfship of the dwarves is unparalleled. Let's make a deal!}}

Assuming you do have friendly contact with [[human]]s, their first caravan will arrive sometime in summer, giving you well over a full year before they arrive.

The human caravan:
* arrives in [[Calendar|summer]]. (Usually your first caravan opportunity.)
* carries metal bars, sand, [[leather]], cloth, wood, food and booze, books, ropes, waterskins, quivers, backpacks, metal weapons and clothing and armor, cages and a few domestic animals.
* carries only large-sized clothing and armor, which is unusable by dwarves.
* is moderately guarded.
* sends a chief treasurer to negotiate import/export agreements

==== Good Humor ====
Choosing to seize goods from a human caravan without marking anything to be taken is treated as a joke, which will raise the visiting trader's mood. This can only be done once each year.

=== Goblins and Kobolds ===
{{mod}}
{{main|modding#trade}}

A [[goblin]] caravan will only arrive if you mod the game, primarily because their entity lacks the [[entity token]]s needed to make use of pack animals and wagons. That, and that the token {{token|BABYSNATCHER|e}} makes them hostile to all non-goblin civilizations. The same caveats apply to [[kobold]]s (whose {{token|UTTERANCES|c}} and {{token|ITEM_THIEF|e}} tags, similarly, make them hostile to every civilization).

The goblin caravan:
*will arrive every season, four times per year
*is unguarded
*brings mostly food and cloth
*does not send a liaison or a guild representative
*does not make import/export agreements

== Merchant mood ==
{{Verify|Are we sure that this section is correct?}}
If your trader has Novice or better [[Judge of intent]] skill, there will be a line added below the merchant's dialogue describing the caravan's attitude. Their attitude rises with successful trades (especially if they get lots of profit) and falls when you propose deals they don't like. You can never make a deal that's at a loss for the merchant, even if they are at the highest possible mood.

* {{DFtext|(trader) seems ecstatic with the trading.|2:1}}
* {{DFtext|(trader) seems very happy about the trading.|3:1}}
* {{DFtext|(trader) seems pleased with the trading.|1:1}}
* {{DFtext|(trader) seems willing to trade.|7:1}}
* {{DFtext|(trader) seems to be rapidly losing patience.|6:1}}
* {{DFtext|(trader) is not going to take much more of this.|4:1}}
* {{DFtext|(trader) is unwilling to trade.|5:1}}

The happier you make a merchant, the less profit margin they will demand in a trade. Dwarven merchants start off wanting about 100% profit, maybe a little more. If you repeatedly offer less than what they expect, that will "lower" their mood. If, on the other hand, you meet or exceed their expectation, that will, over several trades, improve their mood. If merchants reach the lowest level, no further trade will be possible, and they will immediately pack up and leave your depot. Since annoyed merchants are more likely to reject deals, you should be generous in initial negotiations. Skilled negotiators seem less likely to offend merchants with unsuccessful deals.

An easy way to capitalize on this mood system is to perform several partial trades. First trade for a few items, offering goods twice the value of the items you ask for (e.g. offer 2000☼ for 1000☼ of his stuff). This will likely make the merchant ecstatic about trading with you. Perform the next trades more aggressively, working them down to about a 30% profit. With the merchant in such a good mood, they are more likely to counteroffer than reject a trade outright. If you don't like the counter-offer, try to split the difference, or just back out of the trade and start again.

== Trade Agreements and Liaisons ==
[[Outpost liaison]]s (from your own civilization) and foreign Merchant Nobles (if added with the [[Position token#TRADE|TRADE responsibility]]) will arrive with the caravan to speak to your [[noble]] dwarves (and they ''will'' speak to those dwarves, even if they have to wait at their bedside in the hospital for months after the caravan has left), appearing on the map edge at the same time as the caravan (though in a different location). Meeting with them allows you to request specific items for the next caravan to bring (at a premium price) or take requests for production for the next caravan (for which the merchants will pay a premium).

Current [[Trade agreement|trade agreements]] can be viewed through the Civilization menu ({{k|c}}). These trade agreements are cleared when a liaison of the corresponding civilization enters the screen, so they are generally not accessible after the caravan has arrived.

In the event that your leader is replaced, killed, or taken by a [[strange mood]], the liaison may decide to leave your fortress [[stymied|"unhappy"]].{{bug|576}} Curiously, this will '''not''' occur if your leader is otherwise unable to perform the "conduct meeting" task. You can currently lock a liaison in a room and they will wait years to attend the meeting your noble is constantly conducting (and all subsequent diplomats appear to wait in line for the first to finish); this behavior is presumably a bug.{{bug|8947}}

Whether having successfully met with your leader or given up, a liaison who has decided to leave but is prevented from reaching the map edge will eventually go [[insane]].

== Bugs ==

* Merchants who are attacked by enemies or even wild animals will sometimes become disconnected from the trade depot and refuse to pack of their things to leave the map, and these items will remain 'stuck' in the depot. Deconstructing the trade depot usually forces them to leave, presumably with the downside of causing those goods to be considered seized by the player.
* Aggressive, untrainable creatures (captured goblins, for example) cannot be traded; when a dwarf attempts to move the caged animal to the Depot, the creature is set free.
* When merchants leave with an animal, the merchants seem to be dragging their beast of burden instead of leading it. If the animal is incapacitated but not dead, the merchant will continue to walk at the same speed, dragging the unconscious beast.
* If a merchant's chosen map edge exit is guarded by a hostile creature (including those on a [[restraint]]), the merchant will wander back and forth repeatedly and eventually go insane rather than path to an alternate exit.
* Animals bought from merchants don't always become available for use.{{bug|10162}}

== Loyalty cascade ==
{{main|Faction#Loyalty cascade|l1=Faction}}
If you order your military to kill merchants from your own civilization, a bizarre result of the way loyalty is handled makes the members of your military who attacked the traders become enemies of your civilization, but remain members of your fort's government (dwarves of this [[faction]] are referred to as ''separatists''). As enemies, they attack your other dwarves (''citizens''), but as members of the fort, they still follow orders. Allowing citizen militia dwarves to attack the separatists will give them opposite loyalties of the separatists, (i.e. loyal to civ, not to fort), or ''loyalists'', who do '''not''' follow orders. And then, if a separatist or loyalist kill a citizen, they become enemies of the civ '''and''' fort, making them ''Renegades'', who are essentially complete enemies of the citizens.

To prevent the cascade from spreading, order the original separatists away from the fortress and let them fight amongst themselves. If the results are renegades, it is okay to allow other dwarves to kill them (by stationing them nearby). If the results are separatists/loyalists, then you will need to separate them, somehow.

== Exploits ==
*Deconstructing the depot will cause merchants to leave your fortress and abandon any goods in the Depot because items are not available until the building is fully deconstructed. However any animals they had caged will still belong to the merchants and only become friendly, you won't actually own them. According to Toady One, this is actually working as intended, and is not really an exploit or bug: "...the reckoning comes when they return with lesser value, and it has the same negative effect (it'll be listed as a disaster rather than an intentional seizing -- the depot could be destroyed, for instance -- but it counts for the same value if I remember). The overall wording could be changed and the interaction could be deepened to recognize this or that, but it's working as intended."{{bug|293}}
*If you wait until the merchants leave the map, you can "claim" caged animals by linking a lever to the cage and opening it, the animals will be released in a tamed state. Check the {{k|u}}nit screen before releasing them; if the creatures still show as Merchant creatures, they will wander off the map when released; if they show as Tame creatures, they will stay once released.
*If you lock them in your fortress for a minute or two (real time), the merchants '''may''' drop items and leave behind pack animals (both of which are yours for the taking!) Note: Results are not consistent.
* If [[Caravan#Destruction|spooked or attacked]] the merchants' caravan could leave their stuff behind as they attempt to flee the map, leaving the items free for the taking.

[[File:Bullock_Team_Wool_Wagon.jpg|thumb|400px|center|An old trading wagon from the 1880's.]]

== World level trade ==
During world generation, trade is established between sites. This probably determines growth.

{{Translation| dwarven = nish | elvish = lathì | goblin = otsmor | human = batow}}

{{Category|Trade| }}
[[ru:Trading]][[zh:Trading]]

Pasture

2024-08-07T13:45:37Z

Xjtu-blacksmith: add new grass type

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

[[File:pasture_icon_preview.png|right]]'''Pastures''' are [[activity zone]]s that the player creates to hold tame animals, especially [[grazer|grazing animals]]. Herbivorous animals require [[grass]] (or [[cave moss]], [[floor fungus]] and [[underlichen]] if stationed in underground pasturage) to graze upon, and larger herbivores need a greater amount of these to feed themselves. [[Panda]]s and their relatives require bamboo rather than other types of grass. Using pastures allows herbivorous animals to be restricted to areas where they will have plenty to eat.

A pasture is defined using the {{k|z}}one menu. Once created, you can then select which animals will graze there by clicking the rabbit icon with the yellow plus. Animals currently assigned to this pasture will have a yellow downwards arrow and a green checkmark left of them. Animals assigned to ''some'' pasture, the previously defined one or otherwise, will just have the yellow downwards arrow. If the brackets contain the 'cage' symbol (‼), it means that animal is currently caged. If that animal is selected for this pasture, they will be automatically uncaged and brought to the pasture by a dwarf (this is actually a good way to get animals you bought from a merchant uncaged quickly, without having to actually build the cage somewhere first). Note that an animal in a stockpiled cage within the defined pen/pasture area (i.e. stockpile overlaps pen/pasture zone) is considered to be within the pasture already and will not be released.

Once all animals are selected, finish by pressing {{K|Esc}} or right clicking and idle [[Hauling#Animal_hauling|animal hauler]]s will lead the animals to pasture.

Any animal may be assigned to a pasture, though wild and hostile animals won't reliably stay in one. You can also create pastures inside (on rock) and use them to confine animals that do not need to eat (like [[pig]]s) in certain areas. If there is fungus or moss on your indoor floors (e.g. on soil after breaching the caverns), the animals will consume that in place of grass.

[[Grass]] on your pastures will replenish at different speeds, depending on [[biome]]; if, on embark, the biome reads "Thick" on "Other Vegetation", it will regrow fast, if it read "Scarce", it may not regenerate at all. Care should be taken to ensure that grass is not consumed more quickly than it can replenish, lest your livestock begin starving - if more than half of the pasture is devoid of grass, it's probably overloaded. Of special note is the fact that [[mountain]] biomes start covered with grass (and numerous [[boulder]]s), but said grass will ''never'' regrow once eaten, so when placing pastures, ensure that there are shrubs and saplings nearby, as their presence ensures that the environment is hospitable to plant (re)growth.

Baby animals born to pastured mothers will automatically be assigned to their mother's pasture, but those hatched from [[egg]]s will not.

If you need to get animals inside quickly when a [[siege]] or [[ambush]] hits, a quick way to do this is to simply make the pasture inactive (''before'' the animals see the invaders, if possible.) Animals without a pasture tend to gravitate to a meeting area, so most of them will head to your [[dining hall]] or other rest area. An inactive pasture retains its occupant list, so all you have to do is make it active again and your dwarves will return them to their correct areas.

==Overcrowding==

{{Main|Overcrowding}}

When a pasture is overcrowded, animals may become enraged and start fights, similarly to a dwarf throwing a [[tantrum]], which can be prevented by enlarging your pasture or keeping fewer animals in it. Another possibility is to split a large pasture which holds many animals into several smaller pastures, with the pasture size reflecting the amount of grazing the animal needs to survive. Animals will only fight each other if their pasture is sharing the same tiles as the creature they are fighting with.

==Other Applications==
Pasturing a [[cat]] in a food [[stockpile]] will make it more effective at keeping [[vermin]] away from your food (or any creature with a {{token|HUNTS_VERMIN|c}} or {{token|DIVE_HUNTS_VERMIN|c}} token).

Lots of 1x1 pastures, each with a chicken and a nest box, is a way to make a [https://en.wikipedia.org/wiki/Battery_cage battery farm].

A pasture can serve as a quick, limited replacement for a [[rope]] or [[restraint]], placing animals exactly in one defined area, even [[pet]]s and animals assigned to dwarves. However, it does not restrict the movement of an animal; if they are threatened by an enemy, the animal will flee as normal, which will trigger a task to re-pasture the animal once it leaves the border of the pasture. Dwarves with the [[Hauling#Animal_hauling|Animal Hauling]] labor enabled may then rush to put them back, probably putting themselves in danger; so maybe only enable that labor on the most durable…or replaceable.

With that in mind, pastures can serve as an early-warning system and distraction for invaders and thieves when placed just outside or inside entrances to the fortress. Of course, this can result in injury to the animals, or even their death, and tame animals that die in ways other than specifically being slaughtered cannot be [[butcher]]ed.

More effective ways of using pastures to get rid of unwanted animals include: placing them in chambers to be flooded (preferably with [[magma]]), in the path of [[Dwarven_atom_smasher|certain bridges]], or in battle arenas to face captured foes. Beware that the death of pets will likely cause unhappy [[thought]]s for their owners.

==Bugs==

* Grass does not grow back on mountain biomes.{{bug|4164}}
* Baby animals hatched from [[egg]]s are not automatically assigned to the mother's pasture.{{bug|5990}}
* During a [[civilian alert]], only tiles within the defined burrow are eligible for grazing. Animals confined to pastures outside the civilian alert burrow will starve to death while standing on dense grass.{{bug|6240}} Since the removal of the alert system in v50 this is no longer relevant.

{{Activity zones}}
{{Category|Fortress mode|Activity zones}}
[[ru:Pasture]]

Faction

2024-08-07T02:45:20Z

Xjtu-blacksmith: /* DFHack */ add zh link

{{migrated article}}
{{Quality|Unrated}}
{{av}}
'''Factions''' govern how [[creature]]s will react in each others' presence - the world is full of dangers for your unfortunate dwarves, and it seems that nearly everything is trying to kill them; fortunately, said dangers are also hostile to each other most of the time. Confrontations between such opposed factions happen in both fortress and [[adventurer mode]]; the wise player will see to it that they weaken each other instead of ganging up against one's fort or adventurer.

In the [[object testing arena]], each creature created can be tied to a faction (referred to in-game as a "side"). Creatures will be friendly to other creatures within their faction, and will be hostile to any other creature. There are a total of 9999 factions, and an "independent" option which is hostile to all other creatures.

==Faction relative hostility==

The table below shows the behavior of different factions when confronted:

{| class="wikitable"
|- bgcolor="#dddddd"
|
| '''[[Dwarf|Dwarves]]'''
| '''[[Elf|Elves]]'''
| '''[[Human]]s'''
| '''[[Goblin]]s'''
| '''[[Kobold]]s'''
| '''[[Necromancer]]s'''
| '''[[Undead]]'''
| '''[[Surroundings|Wildlife]]'''
| '''[[Animal people|Cave civs]]'''2
| '''[[Semi-megabeast|(Semi-)]][[Megabeast]]s'''
| '''[[Demon|HFS]]'''
| '''[[Werebeast]]s'''3

|-
| '''Dwarves'''
|style="background-color:#cfc"| Friendly
|style="background-color:#cfc"| Friendly1
|style="background-color:#cfc"| Friendly1
|style="background-color:#fcc"| Hostile1
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile

|-
| '''Elves'''
|style="background-color:#cfc"| Friendly1
|style="background-color:#cfc"| Friendly
|style="background-color:#cfc"| Friendly1
|style="background-color:#fcc"| Hostile1
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#cfc"| Friendly
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile

|-
| '''Humans'''
|style="background-color:#cfc"| Friendly1
|style="background-color:#cfc"| Friendly1
|style="background-color:#cfc"| Friendly
|style="background-color:#fcc"| Hostile1
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile4
|style="background-color:#fcc"| Hostile

|-
| '''Goblins'''
|style="background-color:#fcc"| Hostile1
|style="background-color:#fcc"| Hostile1
|style="background-color:#fcc"| Hostile1
|style="background-color:#cfc"| Friendly
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile4
|style="background-color:#fcc"| Hostile

|-
| '''Kobolds'''
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile

|-
| '''Necromancers'''
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#cfc"| Friendly
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile

|-
| '''Undead'''
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#cfc"| Friendly
|style="background-color:#cfc"| Friendly
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile

|-
| '''Wildlife'''
|style="background-color:#fcc"| Hostile
|style="background-color:#cfc"| Friendly
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
| Variable5
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile

|-
| '''Cave civs'''
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#cfc"| Friendly
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile

|-
| '''(Semi-)Megabeasts'''
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#cfc"| Friendly
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile

|-
| '''HFS'''
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#cfc"| Friendly
|style="background-color:#fcc"| Hostile

|-
| '''Werebeasts'''
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
|style="background-color:#fcc"| Hostile
| Variable3
|}

1Advanced civilizations are subject to the mechanisms of [[diplomat|diplomacy]] and may routinely go to [[war]] or conclude peace treaties depending on [[World generation|worldgen]] and according to each civilization's [[ethics]]. On the one hand, war against elves or humans is not that uncommon; on the other hand, goblins will almost always be hostile toward everyone else.

2Cave civilizations are always hostile toward adventurers and they are usually hostile toward your dwarves. They often become friendly when confronted with a [[megabeast]]. Note that this behavior does not apply to most [[animal people]], who are simply treated as wildlife.

3[[Werebeast]]s will switch factions from whatever civilization they belong to under their normal form to a special, species-dependent faction on the full moon. Different species of werebeasts will be hostile to each other.

4A [[HFS]] denizen often takes control of a goblin civilization, and sometimes becomes the ruler of a human civilization by posing as their god. Other HFS denizens are typically hostile.

5[LARGE_PREDATOR]s will attack anything significantly smaller than themselves. In most other cases, wildlife will flee from non-[BENIGN] wildlife. Two [BENIGN] wild animals will ignore each other.

==Entities and civilizations==

There are four entity 'factions' that can be created in ''Dwarf Fortress'', although vanilla only uses three of them. These factions are determined by the presence or absence of the [[Entity token#BABYSNATCHER]] or [[Entity token#ITEM_THIEF]] tags, so the four factions can be called the Civilized (with neither tag), the Baby[[snatcher]]s, the Item [[Thief|Thieves]], and the Babysnatching Item Thieves (which do not exist in vanilla DF). Members of the same faction will [[trade]] with you in fort mode, and members of all other factions may [[invader|invade]] you. This is separate from civs at [[war]], which is determined by having opposing [[ethics]]. (A civilization from an opposite faction which is *also* at war with you will simply siege you even more.)

Generally, [[civilization]] relationships override whatever loyalty a creature may have to begin with. Therefore:

* Conquered and otherwise incorporated populations from a foreign civ will always be loyal to that civ, both in fortress and adventure mode, *except* in the case of [[insurrection]]s and nothing else.

* Foreign creatures kidnapped by goblins and raised by them will be loyal to their goblin civ and hostile against non-goblin civs, including your fort. This also includes their descendants, which means some goblin civs can be potentially ''depleted'' of goblins, but still send sieges (composed of humans, dwarves, elves, etc.) and ambushes to your fort.

* More amusingly, foreign creatures occupying a [[noble]] position in a civ for whatever reason (e.g. demons that have impersonated a god to take control of human civs, demon law-givers ruling goblin civs, or necromancer kings) will behave the same way any other civ member would toward your dwarves or adventurer. Hence the ludicrous possibilities for a demon to visit your fortress as a [[diplomat]] (or join you in your adventures) or a friendly necromancer inadvertently wreaking havoc on your fortress by raising corpses whenever they can.

Some caveats: sapient creatures without the ability to communicate will always be hostile, even if they technically would be considered the same faction. They will also wage endless wars, since they lack the ability to form treaties. This includes creatures without CAN_SPEAK (or INTELLIGENT, which is functionally CAN_LEARN and CAN_SPEAK combined). Creatures with UTTERANCES cannot communicate with other civs, however, if they have both UTTERANCES and CAN_SPEAK, they will be able to communicate. For instance: [[kobold]]s are unable to speak besides in [[Creature token#UTTERANCES|utterances]] and are thus at war with everyone else - note that if you start as a kobold in adventure mode when they are available, you will be unable to speak to anyone, and other kobolds will attack you on sight because they won't be able to talk to you either.

Civilizations with the [KILL_NEUTRAL:REQUIRED] [[ethics]] ([[goblin]]s in vanilla DF) will be hostile toward members of foreign civs. If you encounter goblins in Adventure mode, they will usually request that you "identify yourself". A common workaround if you are not from their civilization (which you usually aren't) is to assume a false [[name|identity]] so that they believe you are one of their own (remember that due to conquests, kidnappings, etc. multi-racial civilizations are the norm and being from another race wouldn't be considered suspicious).

==[[Undead]] and [[night creature]]s==

The loyalty of undead and night creatures depends on whether they have a [[soul]] or not. Creatures with souls, even undead, will retain the existing loyalty links they had when they got 'transformed', with possible alterations or a more nefarious agenda of their own. For instance, necromancers, night trolls, mummies, etc. break off from civilizations and form separate entities with their own set of loyalties. Soulless undead (zombies and thralls), on the other hand, are hostile to every living creature (night creatures such as [[vampires]] are considered {{token|NONLIVING}}, even if they do die), due to their {{token|OPPOSED_TO_LIFE|c}} tag, which overrides all other relationships.

Vampires, despite their blood-sucking murder sprees, will still be loyal to their parent civ, including your fortress. In fortress mode, you can take advantage of their neutrality toward undead, ordering them to kill necromancers when facing a siege; a vampire can and will path toward a necromancer unhindered and usually beat them to death. You can also order vampires to kill zombies one by one as they won't react unless attacked. In adventure mode, when they are not exposed, they will behave as any member of a civ. Occasionally, they will be accompanied by cultists who will have formed a separate group gathered around their 'immortality worship': if you confront the vampire, they will turn against you.

[[Werebeasts]] are a notable exception: although nominally a night creature, they do not count as undead. Werebeasts are hostile toward each other (and everyone else) except if they belong to the same were-species (except baby werebeasts, which are generally neutral with everyone).

[[Intelligent undead]] are creatures raised by necromancers to serve as their lieutenants. They retain their soul and aren't opposed to life but their loyalty will shift to that of the necromancer in worldgen. In fortress mode, intelligent undead raised by necromancers from your civilization are considered citizens if they were citizens when they died, and may be hostile (or just 'friendly' and mill around doing nothing) if they were invaders when they died. Intelligent undead raised by your adventurer will retain their loyalty links, so if you're the one that slew them in the first place, they will remember it and attack you on sight. A workaround is to destroy their soul by first raising them as regular undead, slay them, then raise them as intelligent undead - their soul will be a blank slate with no preexisting conflicting loyalties.

In adventure mode, should you learn the secrets of life and death or become a night creature yourself, all zombies will become neutral to you, letting you seize the opportunity to make short work of their squishy and unarmed masters. Undead you raise will follow you as if they were companions; however, they will '''all''' turn neutral if you purposely attack one of them. Generally speaking, there seems to be a worldwide solidarity among night creatures, and if your parent entity does not have beef with any of them, becoming a night creature will allow you to just chat with various necromancers or [[mummy|mummies]], take quests from them, and take them as companions.

==Levels of conflict==
{{Main|Level of conflict}}

In adventure mode, while all hostile nonsapient beings are No Quarter by default (because they do not understand the concept of surrender), sapient creatures that are capable of speech (that means creatures with both [CAN_LEARN] and [CAN_SPEAK], or [INTELLIGENT]) can be talked out of a Lethal fight, either by surrendering to them or making them yield. A notable exception is creatures from civilizations with the [KILL_NEUTRAL:REQUIRED] or [KILL_ENEMY:REQUIRED] [[Ethics|ethics]], which are always No-Quarter with neutral and enemies, respectively. Non-lethal and below types of fighting (often happening at a [[tavern]] or as the result of a spat due to differing values or other grudges) can also be easily de-escalated. This makes conflicts with other hostile sapient beings much easier to manage.

In fortress mode, invaders and your dwarves are No Quarter toward each other (the only exception is elven or human diplomats offering peace treaties). Brawls may also happen at your tavern if non-dwarves drink more alcohol than their livers can handle, but these don't escalate into full blown war, although they do result in sometimes lethal injuries.

==Bandits and [[criminal]]s==

[[Bandits]] are entities consisting of groups harassing [[town]]s (including your fortress) from [[camp]]s in the countryside, and they are hostile toward civilization members. If you don't want them to be hostile to your adventurer, you should start the game as an [[outsider]] with no link to existing entities, or assume the identity of one. Bandits may lay (small-scale) siege to you in fortress mode, and are often given as quest targets in adventure mode. However, as they effectively own sites (camps, with a [[boss]] acting as the lord) it means you can try and de-escalate any [[level of conflict]] you may have with them, talk to the boss, and join them as a [[Hearthperson|lieutenant]], and take quests from them, effectively shifting your loyalty.

[[Criminal#Criminal Organization|Criminal organizations]], on the other hand, dwell in a town's [[dungeon]]s, and although they take part in various [[intrigue| schemes]], they are not nominally hostile toward anyone (apart from the occasional insult or spitting). Their members have links with existing groups in the town, and killing some of them as part of a [[quest]] may not be taken well by the citizenry.

==Insurrections==
{{Main|Insurrection}}

Several civilizations may lay claim to a single site. When a site belonging to a civilization gets occupied by another, there is a chance for the site's inhabitants to revolt, treating their current parent civ as enemies (and their former civ as friendly). This shift of loyalty often translates into a bunch of fights erupting out of nowhere in adventure mode.

==Intelligent wildlife==

Random non-civilized intelligent beings (gorlaks, gremlins, animal people) are hostile (as wildlife would be) in fortress mode. In adventure mode, their behavior depends on their alignment - evil-aligned ones like [[troll]]s or [[ogre]]s will attack you, while neutral and good-aligned ones like animal people or gorlaks can start conversations with you. (A notable exception is ''civilized'' animal people found in caves, that are hostile toward adventurers unlike previous versions.) They won't have much to say if they are not part of a civilization, though. [[Gremlin]]s are special as they can be tamed in fortress mode, which means they are able to become pet citizens, which, in turn, triggers all sorts of weirdness.

Benign wildlife isn't really hostile in that they generally flee conflict if able, but they ''will'' put up a fight if cornered.

==Tamed enemies==
{{Main|Animal trainer}}

In Fortress mode, ''any'' creature that's been labelled as an enemy of your civilization ''will'' be hostile toward your fortress, no matter what. Creatures become enemies of your civilization by either killing a member of your civilization (e.g. one of your dwarves, but even pets qualify) or by belonging to an enemy civilization or otherwise hostile entity in the first place. In practice, this means that the following creatures will always be hostile, ''despite'' their tameable status:

*[[Megabeast]]s ([[Roc|rocs]], [[Hydra|hydras]], [[Dragon|dragons]] are the tameable megabeasts)
*Enemy [[Mount|mounts]] brought in a [[siege]]
*Wildlife creatures that have killed one of your dwarves or pets. Most often, they acquire a [[name]] for this feat.

You may cage and attempt to [[Animal training|train]] these creatures, raise their training level, and sure enough, this will yield experience for your trainers, and raise civilization-level knowledge about the animals. But you should ''never'' set them free inside your fortress, as they will munch on your dwarves ''and'' trigger a loyalty cascade in the process. See below for specific cases.

Interestingly, the offspring of such creatures do ''not'' count as enemies of your civilization. This means you may attempt a breeding program between enemies of the same species, or an enemy and a wild counterpart that's presumably easier to handle. In practice, this leads to extremely disturbing situations where a mother either massacres her offspring as soon as she gives birth, or said offspring overwhelm her as soon as they come out of her. Note that this only ever happens if the species does not lay eggs - enemies do not use your [[nest box]]es (and, if they are [[building destroyer]]s, will simply demolish them) if you provide them with some.

==Miscellaneous==

[[Megabeast]]s and [[semi-megabeast]]s are neutral toward each other, but will try to kill everything else they can find - whether it be in [[World generation|worldgen]], [[adventurer mode]] or [[fortress mode]]. [[Forgotten beast]]s and [[titan]]s are hostile to everyone, including other forgotten beasts and titans.

[[Insanity|Berserk]] dwarves are hostile to everyone, including each other. [[Visitors]] side with their parent civ if it goes to war with you. [[Demon|Demons]] that didn't escape from the [[Underworld|Underworld]] are hostile to every non-demon, and [[Angel|angels]] are hostile to every non-angel. This, obviously, does not apply to demons your adventurer has bound into servitude, nor does it apply to demons who rule (human or goblin) civilizations.

If for some reason a demon is given a nobility title, they will turn neutral to creatures from the same faction. If they are given a [[religion|religious]] title, they will slaughter everyone with a different religion. Bestowing nobility titles can be a way to turn normally hostile creatures like [[night troll]]s or even [[bogeymen]] into becoming friendly to the parent civ the nobility relates to.

==Loyalty cascade==

Loyalty cascades are the result of entity members attacking each other. The conflict will escalate into a full civil war (hence Toady One referring to it as the "civil war bug") and won't resolve until one side of the conflict is wiped out. Loyalty cascades can be triggered in both fortress and adventure mode.

===Attacking [[Trade|merchants]] from your mountainhome===

If you order your military to kill merchants from your own civilization, a bizarre result of the way loyalty is handled makes the members of your military who attacked the traders become enemies of your civilization, but remain members of your fort's government (dwarves of this faction will henceforth be referred to as ''separatists''). As enemies, they attack your other dwarves (''citizens''), but as members of the fort, they still follow orders. Allowing citizen militia dwarves to attack the separatists will give them opposite loyalties of the separatists, (i.e. loyal to civ, not to fort), or ''loyalists'', who do '''not''' follow orders. And then, if a separatist or loyalist kill a citizen, they become enemies of the civ '''and''' fort, making them ''Renegades'', who are essentially complete enemies of the citizens.

===Attempting to tame enemy [[mount]]s===

If you use [[cage]] [[trap]]s against goblin sieges, you are likely to capture [[Giant bat|a]] [[Cave crocodile|few]] [[Giant cave swallow|mounts]] [[Rutherer|from]] [[Jabberer|various]] [[Voracious cave crawler|species]]. You may assign them to your [[animal trainer]]s and attempt to tame them, thus gaining a few facts about each specific species; but under no circumstances should you ever release them from their cages, as they are always considered enemies to your civilization and will wreak havoc as soon as they are free. Not only that, but they will trigger a similar loyalty cascade as soon as they attack your citizens, leading your fort to its demise through a never-ending civil war - as well as, for example, some copious jabberer-chomping. The best course of action is to keep re-training the mounts in their cages over and over again, thus facilitating future taming of their '''wild''' counterparts.

===Attacking a [[werebeast]] in dwarven form===

If one of your dwarves turns into a [[werebeast]] and you send your military to kill them while shapeshifted, their failure to do so (and allowing the dwarf to revert to normal) may cause a loyalty cascade.

===Attacking a berserk citizen or werebeast in wereform===

Dwarven military can no longer be relied upon to put an end to the rampages of citizens gone [[insane|berserk]] or transformed into a beast. Fighting such a threat is treated as assaulting a citizen and will cause ''the defenders of your fort'' to lose loyalty and be hunted down as traitors. {{bug|7107}} Seems partially fixed in 0.42{{Verify}}.

===How to deal with loyalty cascades===

To prevent the cascade from spreading, order the original separatists away from the fortress and let them fight amongst themselves. If the results are renegades, it is okay to allow other dwarves to kill them (by stationing them nearby). If the results are separatists/loyalists, then you will need to separate them somehow. Dwarves from these different "factions" will cancel jobs if they ever come across one another, each running away. This will likely lead to a massive number of job interruption announcements reading ''Urist McDwarf cancels Eat: Interrupted by Farmer''

'''NOTE:''' Tame animals are loyal to civilizations and fortresses indefinitely due to a bug, so they can be used to kill off separatists/loyalists without repercussions.

As of 0.50, loyalty cascades should periodically end on their own[http://www.bay12games.com/dwarves/#2022-03-20]; separate your dwarves from each other until the fighting stops.

{{mod}}

====DFHack====
For those who are using [[Utility:DFHack|DFHack]], the command {{DFtext|fix/loyaltycascade|white}} can be used to immediately end some loyalty cascades, though it does not work on all types of loyalty cascade.

{{Translation
| dwarven = uzlir
| elvish = anoni
| goblin = osmrur
| human = ozo
}}
{{Category|Game mechanics}}{{Category|World}}
[[ru:Faction]]
[[zh:Faction]]

Furniture hauling

2024-08-06T03:21:07Z

Xjtu-blacksmith: More precise redirection

#REDIRECT [[hauling#Furniture hauling]]

Furnace

2024-07-31T12:19:07Z

Xjtu-blacksmith: update key shortcuts

{{Quality|Unrated}}
{{av}}

[[File:furnace_preview.png|right]]'''Furnace''' is an umbrella term for different related [[workshop]]s that heat materials for different purposes. While a "[[wood furnace]]" may be the most basic of these, the list includes smelters and kilns. These different workshops often produce only intermediary products, items that are then used to create something else for the final product.

Every furnace-type workshop '''must''' be built from [[fire-safe]] materials.

Jobs at a furnace generally require [[fuel]] or, in the case of magma furnaces, the heat from [[magma]] - if the latter, they do not use up any magma but merely must be placed over it. To operate, magma version furnaces '''must''' be placed with one of their edge tiles above magma with depth of 4 or more. This can be accomplished by digging a channel for the magma, or hanging it directly over an open [[Magma#Magma_sources|magma source]].

Note that magma versions are '''not''' operable without magma. If the magma source fails, they cannot be used with [[fuel]]. If the magma depth falls below "depth = 4" at any time during operation (even for a single moment), any and all current job(s) will be cancelled in that workshop.

All furnaces are constructed using the Furnaces sub-menu (via {{menu icon|b|o|u}} ).

See main articles for a full discussion of specific workshops, especially of magma versions.

== [[Wood furnace]] ==
Turns [[wood]] [[log]]s into [[ash]] or [[charcoal]].
:*''Shortcut:'' {{menu icon|b|o|u|f}}
:*''Materials used:'' [[wood]]
:*''Items made:'' [[ash]], [[charcoal]]
::*''Feeds into:'' fuel for other furnaces, [[steel]] making, [[Ashery|asheries]] and [[soap]] production

== [[Smelter]] ==
Extracts [[metal]]s from their [[ore]]s, and produces [[coke]] from raw [[coal]].
:*''Shortcut:'' {{menu icon|b|o|u|l}}
:*''Materials used:'' [[bituminous coal]], [[lignite]], [[ore]], [[metal]] [[bar]]s, [[flux]], [[fuel]] (and metal objects to be [[melt]]ed)
:*''Items made:'' [[coke]], metal [[bar]]s
::*''Feeds into:'' [[Forge]]s

===[[Magma smelter]]===
:*''Shortcut:'' {{menu icon|b|o|u|L}}
Note: The only time the magma version uses [[charcoal]] or [[coke]] is in the recipe for [[pig iron]] and [[steel]] production.

== [[Glass furnace]] ==
Turns raw [[sand]] into [[glass]] items.
:*''Shortcut:'' {{menu icon|b|o|u|g}}
:*''Materials used:'' [[sand]], [[pearlash]], [[rock crystal]], [[fuel]]
:*''Items made:'' [[glass]] objects
::*Glass objects are final products

===[[Magma glass furnace]]===
:*''Shortcut:'' {{menu icon|b|o|u|G}}
Magma glass furnaces use only magma as a heat source and require no additional [[fuel]]. They produce the same objects as a regular glass furnace.

== [[Kiln]] ==
Used to fire [[clay]] into items, and to glaze some types of clay items. It also is used to produce [[gypsum plaster]], [[pearlash]], and [[quicklime]].
:*''Shortcut:'' {{menu icon|b|o|u|k}}
:*''Materials used:'' [[potash]], [[ash]], [[cassiterite]], [[clay]], [[clay loam]], [[sandy clay]], [[silty clay]], [[fire clay]], [[kaolinite]], [[gypsum]], [[alabaster]], [[selenite]], [[satinspar]], [[fuel]]
:*''Items made:'' [[ceramic|ceramic/clay items]], [[pearlash]] and [[plaster powder]]
::*''Feeds into:'' pearlash for higher quality [[glass]] production
::*Plaster powder is a final product used by healthcare professionals.
::*Ceramic/clay (earthenware, stoneware, and porcelain) items are final products.

===[[Magma kiln]]===
:*''Shortcut:'' {{menu icon|b|o|u|K}}
Functions just like a regular kiln, but uses magma instead of [[fuel]].

{{Translation
| dwarven = sarvesh
| elvish = lethari
| goblin = usmza
| human = nganiz
}}

{{Workshops}}
{{Buildings}}

Wealth

2024-07-29T15:43:33Z

Xjtu-blacksmith: add zh link

{{Quality|Exceptional}}
{{av}}
[[File:wealth_preview.png|right]]Your '''created wealth''' is the sum product of all the labors of your fortress. It is visible on the [[status|wealth tooltip]] once you have a [[broker]] with the [[appraisal]] [[skill]] and a [[bookkeeper]] maintaining your records, and will update with the continual maintenance of your [[stocks]] by the bookkeeper.

Wealth is the sum of everything of [[value]] in your fortress: basically, everything except corpses and remains, which have absolutely no worth whatsoever. This includes [[stone]]s, [[building]]s, engravings, and any and every kind of created good, all of which contribute to your total wealth to various degrees. [[Artifact]]s are usually one of the largest influences on fortress wealth. Artifacts made of precious resources and heavily [[decorate]]d can easily be worth thrice the value of the rest of your fortress in the early years.

The display of your wealth on the main status screen is broken up into several categories: [[weapon]]s, [[armor]] and [[Clothing|garb]], [[furniture]], other objects (like [[finished goods]]), [[architecture]] ([[building]]s and such), displayed, and held/worn (items created internally that have been claimed by dwarves, like clothing).

For the more abstract wealth count used in [[world generation]] to determine building ownership and help ground various acts of corruption and [[villain]]y, see [[account]].

== Imports and exports ==
[[File:Wealth-tooltip.png|thumb|right|327px|Wealth tooltip in Premium.]]
Items made off-site are not counted in your total fortress wealth, and are instead listed as imports. This only applies so long as the object is unchanged; a decorated imported object will be made your own, and its value will be moved from imports to wealth. This is important when trading with caravans, as they will not accept goods stolen or lost by a previous caravan of that civilization. It is listed under "Imported Wealth".

Similarly, items made in the fortress that leave the map on a [[caravan]], be it dwarven, elven, human or goblin, are counted as exports, listed under "Exported Wealth."

== Influences ==
Wealth influences various game features, some of them good, some of them bad.

On the plus side, it increases the amount of [[migrant]]s you get per wave. Assuming that you are equipped to handle the new dwarves, this is usually a good thing, except when you are producing so much wealth that your migrant arrivals outstrip your ability to house and feed them or give them useful things to do. Drowning in migrants is a very real danger; make sure you are always equipped with surplus beds and food.

A certain level of exports and overall wealth is required to acquire economically-linked [[holding]]s. However for smaller sites fortress wealth is the more important factor in determining economic linkage. Holdings are in turn necessary to go up the [[noble]] ladder: a [[baron]] requires one holding, a [[count]] requires four, and a [[duke]] requires nine. The [[monarch]] has some fairly complicated requirements based on a few different categories.

On the negative side, more wealth attracts more attacks. At first, this will be an above-average amount of [[thief|thieves]], but as the game progresses and your wealth continues to grow, this will develop into [[ambush]]es, [[siege]]s, and visits from [[megabeast]]s, all of which are attracted to increasing amounts of wealth. This keeps the game from being boring, but too much [[fun]] is also a bad thing; if you have a hard time dealing with the numerous waves of immigrants, you're probably not equipped to deal with a full-on siege.

== Building and limiting wealth==
Building wealth is simple - just commit more people to useful industries and continue growing. You will want to establish a major [[industry]] and commit a dwarf to it (producing [[finished goods]] is the easiest way), allowing you to spend grand sums on caravans and get everything you absolutely need quickly and painlessly. If you intend to go this route, be sure to create tons of extra [[bin]]s to ease the transfer of items to the trade depot and prevent stockpiles from becoming too full.

When first starting out, it's typically best to not focus too much on building wealth until you have an effective military that can deal with the [[Megabeast|fun]] [[Werebeasts|things]] that a large amount of wealth can cause.

[[Metal]]s are great materials for creating wealth. Many locations have an [[ore]] of [[iron]] or [[silver]]. Both are of moderate value and can be made into [[weapon]]s, [[furniture]] or crafts. [[Statue]]s make for high-value furniture. Certain butchered [[animal]]s have high-value bones or skulls. [[Ceramic]]s, especially [[stoneware]] made from [[fire clay]] can provide a continuous source of decent valued goods. Rough [[gem]]s can be hard to find but a highly skilled [[gem setter]] can decorate objects to add considerable value to furniture or crafts.

On the opposite side, there are the fortresses that would much rather establish a baseline of sorts before embarking on an expansionist binge - getting a full defensive grid up, for instance, or penetrating an [[aquifer]] without having to waste precious reserves on more dwarves and more enemies. These players concentrate on low-value activities like carpentry, masonry, and mining, and only produce enough trade goods to get what is necessary from the caravans. Although they are slower to grow, they also afford their players more time to plan and to lay the groundwork for the future of the fortress.

Note that, no matter what, you ''will'' have to deal with ''some'' growth - besides the natural expansion of your fortress, there's also the issue of [[artifact]]s. Do what you will, but every once in a while a dwarf will [[Strange mood|claim a workshop]] and produce a valuable trinket, and all you can hope for is that it's not worth too much. It's worth noting that artifact furniture is counted three separate times toward created wealth: as furniture, as architecture, and as displayed. You may wish to hold off on installing that legendary [[coffer]] that's worth three times as much as your fortress when just sitting in a stockpile.

Most players choose to walk the middle line, getting together the necessary industries, but concentrating on the [[metal industry]] early on, to get together their arms and armor. Although [[steel]] is worth its weight in [[gold]], it is much more useful deflecting goblin arrows from your fortress defenders than as a [[statue]] decorating your [[Meeting area|lobby]].

==Bugs==

*Some buggy items can have a negative wealth. This can cause expected events to not happen, as they are tied to wealth. To troubleshoot this, you can move all your items to the trade depot and look through the value of the items. You may want to do this on a backed-up save. Once you find the offending item, you can either atom-smash it or use DFHACK "autodump destroy".

{{Translation
| dwarven = limâr
| elvish = rano
| goblin = sloron
| human = ostri
}}

{{Category|Economy}}
[[ru:Wealth]]
[[zh:Wealth]]

Wealth

2024-07-29T15:36:34Z

Xjtu-blacksmith: /* Imports and exports */ extract pic from status

Labor

2024-07-28T03:09:00Z

Xjtu-blacksmith: /* List of labors */ add zh link

{{Quality|Exceptional}}
{{av}}
{{quote|'''"To get a job done, a dwarf has to do it."''' - Boss Urist McOverstates-the-obvious}}[[File:labor_icon_preview.png|right]]'''Labor''' is how jobs get done in a fortress; which labors are restricted to a dwarf determines which jobs they can or can't do. The [[skill]] level and [[attribute]]s of an individual determine how effectively they perform a job.

The game provides many flexible options to the player to allow or disallow certain actions of their dwarves, which can further add efficiency to a fortress. Visiting [[citizen]]s can also perform some labors.

==Introduction to labor==
*[[File:v50_labor_preview.png|right]]Your dwarves function as semi-autonomous entities, usually fulfilling their own basic needs, and sometimes performing jobs when able.
*Most jobs correspond to a '''labor''', which dwarves can be restricted from doing.
*Labors can be restricted to specific dwarves in groups called '''work details'''.
*'''Jobs''', the specific tasks to be completed, are created in various ways, including [[designation]]s, [[zone]]s, [[workshop]] tasks, and [[manager]] work orders, and once created, an idle dwarf who does not have that labor disabled will be assigned the job.
*As dwarves perform jobs, their '''skill''' in those areas increase. (The terms labor and skill are '''not''' synonyms. Skill is a measure of proficiency for a given labor, while a labor is the ability to do the work.)
**Some skills don't correspond to jobs, like [[social skills]] and miscellaneous abilities like [[swimming]].

==Labor menu==
The '''Labor''' menu tab is accessed with {{k|y}} or the fourth menu button {{menu icon|y}} at the bottom-left of the main [[interface]]. It contains four sub-tabs; [[Labor#Work details|Work details]], [[Labor#Standing orders|Standing orders]], [[Labor#Kitchen|Kitchen]], and [[Labor#Stone use|Stone use]].

===Work details===
The '''Work details''' tab lists the current sets of labors and who is allowed to do them. The work details are listed on the left side of the screen, selecting one shows a list of all labor assignable citizens in your fortress on the right. Each line shows the citizen's name, profession, applicable skill levels for this detail, specialization button, assigned details, and finally a check mark for this selected work detail. Clicking the specialization button will toggle specialization for that citizen, but clicking '''any''' other part of the line will toggle this selected work detail for that citizen, even other work detail icons.

Above the list, each work detail has a setting controlling how it is assigned to citizens:

*When "Only selected do this" is selected, the work detail will be assigned to any citizen with a check in the rightmost box on their line.
*With "Everybody does this" selected, all citizens in the fortress will have permission to do the work detail's labors. (Any checked boxes will be white, showing that the citizen in question will do this job even if specialized).
*When "Nobody does this" is selected, all citizens in the fortress will be ''banned'' from doing the work detail's labors. This does ''not'' override permission given by other works details. Any check marks/permissions set up before selecting "Nobody does this" will go red, showing that they are paused and they will be restored if you go back to "Only selected do this".

Labors associated with dwarf's [[occupation]] (such as being a [[Doctor]]) are always allowed.

Additionally, each citizen has the option to be '''specialized''', this is shown by the hammer and lock icon just to the right of their name (It can also be viewed and interacted with from the {{k|u}} Citizens menu). When this setting is on (icon is red [[File:Labor specialized.png]]), the citizen will only accept tasks given by workshops/[[occupation]]s they are assigned to and labors which have been assigned to them and are not restricted to "Nobody does this".

Here are all the possibilities:

{| class="wikitable"
|+ A dwarf can take a job if ''any'' of the Yes conditions below are satisfied:
|-
! !! Specialized [[File:Labor specialized.png]] !! Unspecialized [[File:Labor unspecialized.png]]
|-
| [[File:UI add worker.png]] The dwarf is assigned to the [[workshop]] or [[lever]] giving this job. || style="background:lightgreen" | Yes || style="background:pink" | No, unless a Yes applies
|-
| [[File:UI add worker.png]] The dwarf is assigned to the [[occupation]] giving this job. || style="background:lightgreen" | Yes || style="background:lightgreen"| Yes
|-
| The dwarf is '''selected''' under any work detail containing this job set to:

[[File:Interface white check.png]] "Everybody does this" OR

[[File:Interface green check.png]] "Only selected do this"
| style="background:lightgreen" | Yes
| style="background:lightgreen" | Yes
|-
| No work detail contains this job OR

the dwarf is '''unselected''' under any work detail containing this job set to
[[File:Interface empty check.png]] "Everybody does this"
| style="background:pink" | No, unless a Yes applies
| style="background:lightgreen" | Yes
|-
|}

====Default work details====
By default, the work details, and the labors associated with them, are as follows{{cite forum|180804/8438104}}

{| class="wikitable"
|-
| Miners†
||
* [[Mining]]
|-
| Woodcutters†
||
* [[Woodcutting]]
|-
| Hunters†
||
* [[Hunting]]
|-
| Planters
||
* [[Farming (fields)]]
|-
| Fisherdwarves
||
* [[Fishing]]
|-
| Plant gatherers
||
* [[Plant gathering]]
|-
| Stonecutters
||
* [[Stonecutting]]
|-
| Engravers
||
* [[Stone engraving]]
|-
| Haulers
||
* All [[hauling]] labors
|-
| Orderlies
||
* [[Suturing]]
* [[Dressing wounds]]
* [[Feed patients/prisoners]]
* [[Recovering wounded]]
|}

† The Mining, Woodcutting, and Hunting labors are only accessible from these default work details.

====Custom work details====
{{TipBox2|titlebg=#dd0|float=right|Utilities|If you would like more control or information for labor assignments, [[Utilities#Dwarf Therapist|Dwarf Therapist]] and/or [[Utility:DFHack|DFHack]] can help, when available.}}
Additional work details can be defined. Click "Add new work detail", select which [[labor]]s will be associated with it, and then click done. You can then rename the new work detail.

There is currently no way to choose the work detail's icon, so you are stuck with what the game chooses. The roman numerals are in the file <code>Dwarf Fortress\data\vanilla\vanilla_interface\graphics\images\interface_bits_labor.png</code> and can be changed, but will still be used in order.

===Standing orders===
{{main|Standing orders}}

===Kitchen===
This tab lists all item types currently within the fortress that can be used for either [[cooking]] or [[brewing]]. It is separated into four tabs:
*Vegetables, fruit, and leaves
*Seeds
*Drinks
*Meat, fish, and others.

On each tab, the items are listed in the left most column ({{DFtext|Ingredient Type|7:1}}). The second column ({{DFtext|Number|7:1}}) lists the number of each ingredient currently possessed. The last column ({{DFtext|Permissions|7:1}}) is subdivided into two additional columns, cooking and brewing. This is the most important part, as it shows you whether dwarves are currently allowed to use the ingredient for the given task. Possible values are:

* [[File:cook_disabled_icon.png|18px]] or [[File:brew_disabled_icon.png|18px]] ({{DFtext|+|6:1}}{{DFtext|C|4:1}} or {{DFtext|+|6:1}}{{DFtext|B|5:0}} in ASCII mode) - This item could be used for the task, but is currently disallowed.
* [[File:cook_enabled_icon.png|18px]] or [[File:brew_enabled_icon.png|18px]] ({{DFtext|+|6:1}}{{DFtext|C|4:1}} or {{DFtext|-|4:0}}{{DFtext|B|5:0}} in ASCII mode) - This item is enabled for use in the task, and dwarves have permission to do so.
* [[File:cook_unused_icon.png|18px]] or [[File:brew_unused_icon.png|18px]] ({{DFtext|X|6:0}}{{DFtext|C|4:1}} or {{DFtext|X|6:0}}{{DFtext|B|5:0}} in ASCII mode) - This indicates that the given item cannot be used in this way. For example, Deer meat cannot be brewed (Any [[Alcohol#Cooking|alcohol can be cooked]]).

Note that when a new food is obtained, the default is [[File:cook_enabled_icon.png|18px]] and [[File:brew_enabled_icon.png|18px]] ({{DFtext|X|6:0}}{{DFtext|C|4:1}} or {{DFtext|X|6:0}}{{DFtext|B|5:0}}). This includes recently [[butcher|butchered]] animals, [[food]]stuffs gained from trading, first [[Crop|crops]] from [[Seed|seeds]], and plants [[Plant gathering|gathered]] from the wild. Item types for which all items have been designated as [[Forbid|forbidden]] will not be listed on this menu.

Cooking permission is also used/needed for [[Cheese|cheesemaking]] from [[milk]] items{{verify|I last embarked with all milks and set them all to not cook so I could make them into cheese first, but I want to double check.}}

===Stone use===
The stone use tab is separated into two tabs, Economic Stone and Other Stone. Economic Stone lists all [[Economic stone|economic stone]] (stones that have a value and purpose besides masonry) that can exist in the game. As an example, [[chalk]] can be used in the process of creating [[steel]]. Other Stone lists all non-economic stone.

Both tabs allows you to control what stone is used for menial purposes (masonry, building construction, walls, etc.). By default all economic stone, except layer stones present on the map, is disallowed and all other stone is allowed.

The Economic Stone tab also provides a full list of each economic stone's uses and if it is [[magma-safe]] or not.

== Tool requirements ==
For a few specific jobs, a matching '''tool''' is also required for a dwarf to obey the job assignment. Any active [[miner]] needs a [[pick]], any active wood cutter needs a [[battle axe]], and any active [[hunter]] needs a [[crossbow]] (with quiver and bolts). If a labor needs a tool, the labor is considered '''exclusive''' such that you can only assign one of the three labors listed to any single dwarf at any one time.

This means that a dwarf cannot be, for instance, a [[Miner]] and a [[Hunter]] simultaneously, since both labors require a tool. If a dwarf is assigned a tool-labor and another tool-labor was previously assigned to said dwarf, the (old) tool-labor is automatically and silently unassigned, and that tool is immediately dropped where they stand at the time.

Additionally, the assignment of these tools '''overrides''' any [[Squad|uniform]] assigned to a dwarf's [[squad]], so [[military]] dwarves should never be assigned any of the aforementioned labors.

To be used, a tool cannot be [[forbidden]], nor in possession of another dwarf (even one that does not currently have a job), and a [[path]] must be available from the dwarf to that type of tool. If a tool is not available, the dwarf will typically attempt to fulfil other [[need]]s. It is possible, by using locked doors etc. to limit the paths, to force a specific tool to be assigned to a dwarf, but otherwise the tool will be randomly assigned, sometimes involving a dwarf walking long distances and past perfectly useful tools to find the one they think they want.

== Facility requirements ==
Many jobs require a workshop or some other [[Furnace|facility]] in order to be completed. Jobs are designated by way of the workshop, and any dwarf with the corresponding labor associated with the workshop will go to the shop, provided they are not eating, sleeping, drinking, etc..., and begin to complete the task. Most workshop jobs also require some raw materials in order to complete the production.

== Managing labor and demand ==
This can be done from the labor menu {{menu icon|y}} under the [[work detail]]s tab.
* You can view a list of all current, queued, and suspended jobs, as well as which dwarves are doing them, on the tasks menu {{menu icon|t}}.
* A [[manager]] is incredibly useful for managing production jobs ([[workshop]] based). They can queue up a significant list of jobs without the need to select the various workshops, and place orders in bulk (or to be repeated). That said, there are some caveats, the most important being that queued jobs must be done in the correct order of materials required, or the orders will auto cancel. Also, you should not assign your manager to labors that are in high demand, as this will keep them from going to their [[office]] to place the orders.
* [[Migrants|Migrating]] dwarves will typically arrive with certain work details already assigned. You will likely want to change these to put them to work in a way that best suits your fortress.

== Advanced labor management and design ==
Managing your dwarves can be a tricky business. If the in-game labor menu is not to your liking, [[Utilities#Dwarf Therapist|Dwarf Therapist]] or [[Utility:DFHack|DFHack]] are both useful tools that assist you in managing your labors.

As your fortress grows, so will your labor pool, and the way you assign that labor will change over time. Typically at embark, you will have at least one Miner, a Wood cutter, Farmer, Carpenter, Mason/Stonecrafter, Cook/Brewer, Mechanic/Architect, one of which will also be a Broker/Appraiser. There are multiple combinations but this is typical (see [[Embark]] and [[Starting build]]). Early on, you will probably want to focus on fortress design and development, such that you will place priority on [[mining]] and [[masonry]], supplemented by [[carpentry]].

In order to maximize the benefit of highly skilled labor, you will eventually want to specialize your labor, such that each dwarf has a very limited number of labors assigned. Keep in mind however, that some dwarves experience minor negative feelings at not being able to perform a craft or a martial art for too long.

Hauling: Nothing can bog down your production like the distraction of hauling jobs. Losing your fort to a siege is [[fun]], but losing because all your skilled laborers spend all their time hauling stuff is no fun. One solution is to use dedicated haulers. The migrants who appear having no skilled labor, and whose attributes pretty much suck all around, aka [[peasant]]s, are best used as dedicated haulers.

== Labor, skill, and product quality ==
The amount of [[experience]] a dwarf has with a certain labor will determine how well they go about performing this labor; the more experience, the greater the skill. Certain job types can be completed more quickly, based on the skill in the labor. There are exceptions, such as [[Health care|nursing]] and [[hauling]] which will never be completed more quickly, regardless of skill.

Certain labors will produce products that have a [[quality]] tag, typically those associated with the production of an item from a workshop. The table below lists in which labors the dwarf's experience will impact the quality of produced items and in which labors a higher experience will only be beneficial for the speed of production.

* Many labors, most notably [[hauling]], have no associated skill, do not generate experience, and do not improve with practice.

==Strange moods==
{{main|Strange mood}}
A dwarf under a strange mood will perform a specific task to create an [[artifact]] that is outside of the player's control. Until they complete the task, both they and the workshop they claim will be unavailable for any labor. If the dwarf cannot complete the artifact, they will go [[insane]] and be permanently unable to perform any labor.

{{Translation
| dwarven = èrith
| elvish = equa
| goblin = akul
| human = ebe
}}

==List of labors==

{| border="1" cellpadding="5" cellspacing="0" class="wikitable"
! Category !! Labor !! Skill !! Benefits of higher skill
|-
| Miner
| [[Mining]]
| [[Miner]]
| speed only
|-
| rowspan=3 | [[Woodworker]]
| Carpentry || [[Carpenter]] || speed; item and furniture quality
|-
| Crossbow-making
| [[Bowyer]]
| speed; weapon quality
|-
| Wood cutting
| [[Wood cutter]]
| speed only
|-
| rowspan=4 | [[Stoneworker]]
| Masonry
| [[Mason]]
| speed only
|-
| Stone carving
| [[Stone carver]]
| speed; items and furniture quality
|-
| Stonecutting
| [[Stonecutter]]
| speed only
|-
| [[Stone engraving]]
| [[Engraver]]
| speed; engraving quality
|-
| rowspan=5 | [[Ranger]]
| Animal training
| [[Animal trainer]]
| speed; training quality
|-
| Animal care
| [[Animal caretaker]]
| none (not implemented)
|-
| Hunting
| [[Ambusher]]
| reduced chance of being detected
|-
| Trapping
| [[Trapper]]
| success rate? trap quality?{{verify}}
|-
| Small animal dissection
| [[Animal dissector]]
| speed only
|-
| rowspan=5 | [[Doctor]]
| Diagnosis || [[Diagnostician]] || speed; chance of accurately diagnosing a [[syndrome]]
|-
| Surgery || [[Surgeon]] || speed, amount of bleeding caused, chance of failure
|-
| Setting bones || [[Bone doctor]] ||rowspan=3 | speed only
|-
| Suturing || [[Suturer]]
|-
| Dressing wounds || [[Wound dresser]]
|-
| rowspan=2 | Other [[Healthcare]]
| Feed patients/prisoners
| rowspan=2 colspan=2 | No associated skill
|-
| Recovering wounded
|-
| rowspan=20 | [[Farmer]]
| Butchery || [[Butcher]] || speed only
|-
| Tanning || [[Tanner]] || speed only
|-
| Farming (fields) || [[Planter]] || speed; crop yield (stack size)
|-
| Dyeing || [[Dyer]] || speed; dye quality
|-
| Gelding || [[Gelder]] || less likely to be injured
|-
| Soap making || [[Soaper]] || speed only
|-
| Wood burning || [[Wood burner]] || speed only
|-
| Potash making || [[Potash maker]] || speed only
|-
| Lye making || [[Lye maker]] || speed only
|-
| Milling || [[Miller]] || speed only
|-
| Brewing || [[Brewer]] || speed only
|-
| Plant gathering || [[Herbalist]] || speed; success and plant yield (stack size)
|-
| Plant processing || [[Thresher]] || speed only
|-
| Cheese making || [[Cheese maker]] || speed only
|-
| Milking || [[Milker]] || speed only
|-
| Shearing || [[Shearer]] || speed only
|-
| Spinning || [[Spinner]] || speed only
|-
| Cooking || [[Cook]] || speed; meal and ingredient quality
|-
| Pressing || [[Presser]] || speed only
|-
| Beekeeping || [[Beekeeper]] || speed only{{verify}}
|-
| rowspan=3 | [[Fishery worker]]
| Fishing || [[Fisherdwarf]] || speed; fish stack size
|-
| Fish cleaning || [[Fish cleaner]] || speed only
|-
| Fish dissection || [[Fish dissector]] || speed only
|-
| rowspan=5 | [[Metalsmith]]
| Furnace operating || [[Furnace operator]] || speed only
|-
| Weaponsmithing || [[Weaponsmith]] || speed; weapon quality
|-
| Armoring || [[Armorsmith]] || speed; armor quality
|-
| Blacksmithing || [[Blacksmith]] || speed; item and furniture quality
|-
| Metalcrafting || [[Metal crafter]] || speed; craft, item, decoration, designed building quality
|-
| rowspan=2 | [[Jeweler]]
| Gem cutting || [[Gem cutter]] || speed; gem craft quality
|-
| Gem setting || [[Gem setter]] || speed; decoration quality
|-
| rowspan=13 | [[Craftsdwarf]]
| Bookbinding || [[Bookbinder]] || ?
|-
| Papermaking || [[Papermaker]] || ?
|-
| Leatherworking || [[Leatherworker]] || speed; clothing, decoration, craft quality
|-
| Woodcrafting || [[Wood crafter]] || speed; craft quality
|-
| Stonecrafting || [[Stone crafter]] || speed; craft quality
|-
| Bone carving || [[Bone carver]] || speed; craft, decoration quality
|-
| Glassmaking || [[Glassmaker]] || speed; craft, item, furniture quality
|-
| Weaving || [[Weaver]] || speed; cloth quality
|-
| Clothesmaking || [[Clothier]] || speed; clothing, decoration quality
|-
| Strand extraction || [[Strand extractor]] || speed only
|-
| Pottery || [[Potter]] || speed; craft, item, furniture quality
|-
| Glazing || [[Glazer]] || speed; glaze quality
|-
| Wax working || [[Wax worker]] || speed; craft quality
|-
| rowspan=4 | [[Engineer]]
| Siege engineering || [[Siege engineer]] || speed; part, ammunition quality
|-
| Siege operating || [[Siege operator]] || speed; accuracy
|-
| Mechanics || [[Mechanic]] || speed; mechanism, furniture quality
|-
| Pump operating || [[Pump operator]] || none
|-
| rowspan=11 | [[Hauling]]
| Stone hauling
| rowspan=11 colspan=2 | No associated skill
|-
| Wood hauling
|-
| Item hauling
|-
| Burial
|-
| Food hauling
|-
| Refuse hauling
|-
| Furniture hauling
|-
| Animal hauling
|-
| Trade Good Hauling
|-
| Water Hauling
|-
| Push/Haul Vehicle
|-
| rowspan=4 | Other Jobs
| [[Cleaning]]
| rowspan=4 colspan=2 | No associated skill
|-
| [[Lever operation]]
|-
| Road building
|-
| Wall/floor construction
|}

Some jobs are not associated with a labor: [[food|eat]]ing, [[thirst|drinking]], [[sleep]]ing, going [[on break]], [[party]]ing, [[clean self|cleaning themselves]], and [[rest]]ing.

A few things are listed as "No Job" but can be considered labors in a different sense: running scared, not having a path to any place useful, and being [[insane]].

{{D for Dwarf}}
Take note before trying to get dwarves to do stuff, they probably won't do it. it's just the sad truth....dwarves are so stupid that when they run out of food, they won't even step outside to get that juicy plant sitting right outside the gate, unless you micro-manage them to death. another famed example: a forgotten beast is walking through a tunnel to your fort, so smart ol' you, decides to build a wall. You then tell someone to do it. Luckily for you, Urist McForgotWhatSide builds the wall. He will take a stone, most likely from across the map, haul to the wall, begin building, and have to get a drink. He drops the stone to get some beer, well, while he's up there, he might as well take a quick nap. well, he finally wakes, goes down to build a wall, only to see Urist McMason stole his rock, so he goes across the map for another boulder. He finally finishes the wall, but hears voices on the other side, "You built from the wrong side!" he then hears a hiss from down the tunnel. The forgotten beast walks up to Urist McForgotWhatSide, and bites him in the head: the severed part sails off in an arc. Poor old Urist, "died of old age".
[[File:labor_preview.jpg|thumb|300px|center|"Put both your backs into it!"]]
{{DFtext|<(: <(: () <): T|2:1}}

{{V50 menus}}
{{Category|Skills|*}}
{{Category|Interface}}
[[ru:Labor]]
[[zh:Labor]]

Occupation

2024-07-28T03:08:28Z

Xjtu-blacksmith: add zh link

{{Quality|Unrated}}
{{av}}
{{For/see|the background setting when creating an adventurer|[[Adventurer_mode_character_creation#Occupation|Adventurer mode character creation]]}}

[[File:Occupations.PNG|thumb|right|600px|A tavern screen, showing dwarves with [[Tavern keeper]] and [[Performer]] occupations assigned. Additional citizens can be assigned to either position.]]

'''Occupations''' are positions in certain [[locations]] that can be assigned to dwarves. To assign a dwarf to an occupation, select the [[zone]] (either via {{Menu icon|z}} '''zones''' and selecting the the zone, or from the {{Menu icon|P}} '''place information menu''' ) and then view the locations details with [[File:Ui location details.png]]. You will see a list of available occupations in that location, and can assign or remove dwarves. In the selection menu, dwarves will be ordered by skills relevant to that occupation. You can assign multiple dwarves with the same occupation at a location.

==Occupations==
{|class="wikitable" style="border-collapse:collapse;"
! Name
! Labor or function
! Location
|-
| Doctor
| [[Diagnosis]], [[surgery]], and [[setting bones]].
| [[Hospital]]
|-
| [[Diagnostician]]
| Diagnosis
| [[Hospital]]
|-
| [[Surgeon]]
| Surgery
| [[Hospital]]
|-
| [[Bone doctor]]
| Setting bones
| [[Hospital]]
|-
| [[Messenger]]
| Allows you to interact with your [[hillocks]] and conquered sites.
| None (your [[holding]]s)
|-
| [[Performer]]
| [[dancer|Dance]], recite [[poet]]ry, sing, or play [[music]] to entertain other dwarves.
| [[Tavern]], [[Temple]]
|-
| [[Scholar]]
| Serve as the great thinkers (aside from you of course) of your fort.
| [[Library]]
|-
| [[Scribe]]
| Make copies of [[scroll]]s, [[quire]]s, and [[book]]s.
| [[Library]]
|-
| [[Tavern keeper]]
| Serve drinks to visitors in [[tavern]] locations.
| [[Tavern]]
|}

{{Category|Occupation| }}
[[ru:Occupation]]
[[zh:Occupation]]

Labor

2024-07-27T15:59:25Z

Xjtu-blacksmith: /* List of labors */ fix skill name

Labor

2024-07-27T14:55:47Z

Xjtu-blacksmith: /* Managing labor and demand */ use menu icons

{{Quality|Exceptional}}
{{av}}
{{quote|'''"To get a job done, a dwarf has to do it."''' - Boss Urist McOverstates-the-obvious}}[[File:labor_icon_preview.png|right]]'''Labor''' is how jobs get done in a fortress; which labors are restricted to a dwarf determines which jobs they can or can't do. The [[skill]] level and [[attribute]]s of an individual determine how effectively they perform a job.

The game provides many flexible options to the player to allow or disallow certain actions of their dwarves, which can further add efficiency to a fortress. Visiting [[citizen]]s can also perform some labors.

==Introduction to labor==
*[[File:v50_labor_preview.png|right]]Your dwarves function as semi-autonomous entities, usually fulfilling their own basic needs, and sometimes performing jobs when able.
*Most jobs correspond to a '''labor''', which dwarves can be restricted from doing.
*Labors can be restricted to specific dwarves in groups called '''work details'''.
*'''Jobs''', the specific tasks to be completed, are created in various ways, including [[designation]]s, [[zone]]s, [[workshop]] tasks, and [[manager]] work orders, and once created, an idle dwarf who does not have that labor disabled will be assigned the job.
*As dwarves perform jobs, their '''skill''' in those areas increase. (The terms labor and skill are '''not''' synonyms. Skill is a measure of proficiency for a given labor, while a labor is the ability to do the work.)
**Some skills don't correspond to jobs, like [[social skills]] and miscellaneous abilities like [[swimming]].

==Labor menu==
The '''Labor''' menu tab is accessed with {{k|y}} or the fourth menu button {{menu icon|y}} at the bottom-left of the main [[interface]]. It contains four sub-tabs; [[Labor#Work details|Work details]], [[Labor#Standing orders|Standing orders]], [[Labor#Kitchen|Kitchen]], and [[Labor#Stone use|Stone use]].

===Work details===
The '''Work details''' tab lists the current sets of labors and who is allowed to do them. The work details are listed on the left side of the screen, selecting one shows a list of all labor assignable citizens in your fortress on the right. Each line shows the citizen's name, profession, applicable skill levels for this detail, specialization button, assigned details, and finally a check mark for this selected work detail. Clicking the specialization button will toggle specialization for that citizen, but clicking '''any''' other part of the line will toggle this selected work detail for that citizen, even other work detail icons.

Above the list, each work detail has a setting controlling how it is assigned to citizens:

*When "Only selected do this" is selected, the work detail will be assigned to any citizen with a check in the rightmost box on their line.
*With "Everybody does this" selected, all citizens in the fortress will have permission to do the work detail's labors. (Any checked boxes will be white, showing that the citizen in question will do this job even if specialized).
*When "Nobody does this" is selected, all citizens in the fortress will be ''banned'' from doing the work detail's labors. This does ''not'' override permission given by other works details. Any check marks/permissions set up before selecting "Nobody does this" will go red, showing that they are paused and they will be restored if you go back to "Only selected do this".

Labors associated with dwarf's [[occupation]] (such as being a [[Doctor]]) are always allowed.

Additionally, each citizen has the option to be '''specialized''', this is shown by the hammer and lock icon just to the right of their name (It can also be viewed and interacted with from the {{k|u}} Citizens menu). When this setting is on (icon is red [[File:Labor specialized.png]]), the citizen will only accept tasks given by workshops/[[occupation]]s they are assigned to and labors which have been assigned to them and are not restricted to "Nobody does this".

Here are all the possibilities:

{| class="wikitable"
|+ A dwarf can take a job if ''any'' of the Yes conditions below are satisfied:
|-
! !! Specialized [[File:Labor specialized.png]] !! Unspecialized [[File:Labor unspecialized.png]]
|-
| [[File:UI add worker.png]] The dwarf is assigned to the [[workshop]] or [[lever]] giving this job. || style="background:lightgreen" | Yes || style="background:pink" | No, unless a Yes applies
|-
| [[File:UI add worker.png]] The dwarf is assigned to the [[occupation]] giving this job. || style="background:lightgreen" | Yes || style="background:lightgreen"| Yes
|-
| The dwarf is '''selected''' under any work detail containing this job set to:

[[File:Interface white check.png]] "Everybody does this" OR

[[File:Interface green check.png]] "Only selected do this"
| style="background:lightgreen" | Yes
| style="background:lightgreen" | Yes
|-
| No work detail contains this job OR

the dwarf is '''unselected''' under any work detail containing this job set to
[[File:Interface empty check.png]] "Everybody does this"
| style="background:pink" | No, unless a Yes applies
| style="background:lightgreen" | Yes
|-
|}

====Default work details====
By default, the work details, and the labors associated with them, are as follows{{cite forum|180804/8438104}}

{| class="wikitable"
|-
| Miners†
||
* [[Mining]]
|-
| Woodcutters†
||
* [[Woodcutting]]
|-
| Hunters†
||
* [[Hunting]]
|-
| Planters
||
* [[Farming (fields)]]
|-
| Fisherdwarves
||
* [[Fishing]]
|-
| Plant gatherers
||
* [[Plant gathering]]
|-
| Stonecutters
||
* [[Stonecutting]]
|-
| Engravers
||
* [[Stone engraving]]
|-
| Haulers
||
* All [[hauling]] labors
|-
| Orderlies
||
* [[Suturing]]
* [[Dressing wounds]]
* [[Feed patients/prisoners]]
* [[Recovering wounded]]
|}

† The Mining, Woodcutting, and Hunting labors are only accessible from these default work details.

====Custom work details====
{{TipBox2|titlebg=#dd0|float=right|Utilities|If you would like more control or information for labor assignments, [[Utilities#Dwarf Therapist|Dwarf Therapist]] and/or [[Utility:DFHack|DFHack]] can help, when available.}}
Additional work details can be defined. Click "Add new work detail", select which [[labor]]s will be associated with it, and then click done. You can then rename the new work detail.

There is currently no way to choose the work detail's icon, so you are stuck with what the game chooses. The roman numerals are in the file <code>Dwarf Fortress\data\vanilla\vanilla_interface\graphics\images\interface_bits_labor.png</code> and can be changed, but will still be used in order.

===Standing orders===
{{main|Standing orders}}

===Kitchen===
This tab lists all item types currently within the fortress that can be used for either [[cooking]] or [[brewing]]. It is separated into four tabs:
*Vegetables, fruit, and leaves
*Seeds
*Drinks
*Meat, fish, and others.

On each tab, the items are listed in the left most column ({{DFtext|Ingredient Type|7:1}}). The second column ({{DFtext|Number|7:1}}) lists the number of each ingredient currently possessed. The last column ({{DFtext|Permissions|7:1}}) is subdivided into two additional columns, cooking and brewing. This is the most important part, as it shows you whether dwarves are currently allowed to use the ingredient for the given task. Possible values are:

* [[File:cook_disabled_icon.png|18px]] or [[File:brew_disabled_icon.png|18px]] ({{DFtext|+|6:1}}{{DFtext|C|4:1}} or {{DFtext|+|6:1}}{{DFtext|B|5:0}} in ASCII mode) - This item could be used for the task, but is currently disallowed.
* [[File:cook_enabled_icon.png|18px]] or [[File:brew_enabled_icon.png|18px]] ({{DFtext|+|6:1}}{{DFtext|C|4:1}} or {{DFtext|-|4:0}}{{DFtext|B|5:0}} in ASCII mode) - This item is enabled for use in the task, and dwarves have permission to do so.
* [[File:cook_unused_icon.png|18px]] or [[File:brew_unused_icon.png|18px]] ({{DFtext|X|6:0}}{{DFtext|C|4:1}} or {{DFtext|X|6:0}}{{DFtext|B|5:0}} in ASCII mode) - This indicates that the given item cannot be used in this way. For example, Deer meat cannot be brewed (Any [[Alcohol#Cooking|alcohol can be cooked]]).

Note that when a new food is obtained, the default is [[File:cook_enabled_icon.png|18px]] and [[File:brew_enabled_icon.png|18px]] ({{DFtext|X|6:0}}{{DFtext|C|4:1}} or {{DFtext|X|6:0}}{{DFtext|B|5:0}}). This includes recently [[butcher|butchered]] animals, [[food]]stuffs gained from trading, first [[Crop|crops]] from [[Seed|seeds]], and plants [[Plant gathering|gathered]] from the wild. Item types for which all items have been designated as [[Forbid|forbidden]] will not be listed on this menu.

Cooking permission is also used/needed for [[Cheese|cheesemaking]] from [[milk]] items{{verify|I last embarked with all milks and set them all to not cook so I could make them into cheese first, but I want to double check.}}

===Stone use===
The stone use tab is separated into two tabs, Economic Stone and Other Stone. Economic Stone lists all [[Economic stone|economic stone]] (stones that have a value and purpose besides masonry) that can exist in the game. As an example, [[chalk]] can be used in the process of creating [[steel]]. Other Stone lists all non-economic stone.

Both tabs allows you to control what stone is used for menial purposes (masonry, building construction, walls, etc.). By default all economic stone, except layer stones present on the map, is disallowed and all other stone is allowed.

The Economic Stone tab also provides a full list of each economic stone's uses and if it is [[magma-safe]] or not.

== Tool requirements ==
For a few specific jobs, a matching '''tool''' is also required for a dwarf to obey the job assignment. Any active [[miner]] needs a [[pick]], any active wood cutter needs a [[battle axe]], and any active [[hunter]] needs a [[crossbow]] (with quiver and bolts). If a labor needs a tool, the labor is considered '''exclusive''' such that you can only assign one of the three labors listed to any single dwarf at any one time.

This means that a dwarf cannot be, for instance, a [[Miner]] and a [[Hunter]] simultaneously, since both labors require a tool. If a dwarf is assigned a tool-labor and another tool-labor was previously assigned to said dwarf, the (old) tool-labor is automatically and silently unassigned, and that tool is immediately dropped where they stand at the time.

Additionally, the assignment of these tools '''overrides''' any [[Squad|uniform]] assigned to a dwarf's [[squad]], so [[military]] dwarves should never be assigned any of the aforementioned labors.

To be used, a tool cannot be [[forbidden]], nor in possession of another dwarf (even one that does not currently have a job), and a [[path]] must be available from the dwarf to that type of tool. If a tool is not available, the dwarf will typically attempt to fulfil other [[need]]s. It is possible, by using locked doors etc. to limit the paths, to force a specific tool to be assigned to a dwarf, but otherwise the tool will be randomly assigned, sometimes involving a dwarf walking long distances and past perfectly useful tools to find the one they think they want.

== Facility requirements ==
Many jobs require a workshop or some other [[Furnace|facility]] in order to be completed. Jobs are designated by way of the workshop, and any dwarf with the corresponding labor associated with the workshop will go to the shop, provided they are not eating, sleeping, drinking, etc..., and begin to complete the task. Most workshop jobs also require some raw materials in order to complete the production.

== Managing labor and demand ==
This can be done from the labor menu {{menu icon|y}} under the [[work detail]]s tab.
* You can view a list of all current, queued, and suspended jobs, as well as which dwarves are doing them, on the tasks menu {{menu icon|t}}.
* A [[manager]] is incredibly useful for managing production jobs ([[workshop]] based). They can queue up a significant list of jobs without the need to select the various workshops, and place orders in bulk (or to be repeated). That said, there are some caveats, the most important being that queued jobs must be done in the correct order of materials required, or the orders will auto cancel. Also, you should not assign your manager to labors that are in high demand, as this will keep them from going to their [[office]] to place the orders.
* [[Migrants|Migrating]] dwarves will typically arrive with certain work details already assigned. You will likely want to change these to put them to work in a way that best suits your fortress.

== Advanced labor management and design ==
Managing your dwarves can be a tricky business. If the in-game labor menu is not to your liking, [[Utilities#Dwarf Therapist|Dwarf Therapist]] or [[Utility:DFHack|DFHack]] are both useful tools that assist you in managing your labors.

As your fortress grows, so will your labor pool, and the way you assign that labor will change over time. Typically at embark, you will have at least one Miner, a Wood cutter, Farmer, Carpenter, Mason/Stonecrafter, Cook/Brewer, Mechanic/Architect, one of which will also be a Broker/Appraiser. There are multiple combinations but this is typical (see [[Embark]] and [[Starting build]]). Early on, you will probably want to focus on fortress design and development, such that you will place priority on [[mining]] and [[masonry]], supplemented by [[carpentry]].

In order to maximize the benefit of highly skilled labor, you will eventually want to specialize your labor, such that each dwarf has a very limited number of labors assigned. Keep in mind however, that some dwarves experience minor negative feelings at not being able to perform a craft or a martial art for too long.

Hauling: Nothing can bog down your production like the distraction of hauling jobs. Losing your fort to a siege is [[fun]], but losing because all your skilled laborers spend all their time hauling stuff is no fun. One solution is to use dedicated haulers. The migrants who appear having no skilled labor, and whose attributes pretty much suck all around, aka [[peasant]]s, are best used as dedicated haulers.

== Labor, skill, and product quality ==
The amount of [[experience]] a dwarf has with a certain labor will determine how well they go about performing this labor; the more experience, the greater the skill. Certain job types can be completed more quickly, based on the skill in the labor. There are exceptions, such as [[Health care|nursing]] and [[hauling]] which will never be completed more quickly, regardless of skill.

Certain labors will produce products that have a [[quality]] tag, typically those associated with the production of an item from a workshop. The table below lists in which labors the dwarf's experience will impact the quality of produced items and in which labors a higher experience will only be beneficial for the speed of production.

* Many labors, most notably [[hauling]], have no associated skill, do not generate experience, and do not improve with practice.

==Strange moods==
{{main|Strange mood}}
A dwarf under a strange mood will perform a specific task to create an [[artifact]] that is outside of the player's control. Until they complete the task, both they and the workshop they claim will be unavailable for any labor. If the dwarf cannot complete the artifact, they will go [[insane]] and be permanently unable to perform any labor.

{{Translation
| dwarven = èrith
| elvish = equa
| goblin = akul
| human = ebe
}}

==List of labors==

{| border="1" cellpadding="5" cellspacing="0" class="wikitable"
! Category !! Labor !! Skill !! Benefits of higher skill
|-
| Miner
| [[Mining]]
| [[Miner]]
| speed only
|-
| rowspan=3 | [[Woodworker]]
| Carpentry || [[Carpenter]] || speed; item and furniture quality
|-
| Crossbow-making
| [[Bowyer]]
| speed; weapon quality
|-
| Wood cutting
| [[Wood cutter]]
| speed only
|-
| rowspan=4 | [[Stoneworker]]
| Masonry
| [[Mason]]
| speed only
|-
| Stone carving
| [[Stone carver]]
| speed; items and furniture quality
|-
| Stonecutting
| [[Stonecutter]]
| speed only
|-
| [[Stone engraving]]
| [[Engraver]]
| speed; engraving quality
|-
| rowspan=5 | [[Ranger]]
| Animal training
| [[Animal trainer]]
| speed; training quality
|-
| Animal care
| [[Animal caretaker]]
| none (not implemented)
|-
| Hunting
| [[Ambusher]]
| reduced chance of being detected
|-
| Trapping
| [[Trapper]]
| success rate? trap quality?{{verify}}
|-
| Small animal dissection
| [[Animal dissector]]
| speed only
|-
| rowspan=5 | [[Doctor]]
| Diagnosis || [[Diagnostician]] || speed; chance of accurately diagnosing a [[syndrome]]
|-
| Surgery || [[Surgeon]] || speed, amount of bleeding caused, chance of failure
|-
| Setting bones || [[Bone doctor]] ||rowspan=3 | speed only
|-
| Suturing || [[Suturer]]
|-
| Dressing wounds || [[Wound dresser]]
|-
| rowspan=2 | Other [[Healthcare]]
| Feed patients/prisoners
| rowspan=2 colspan=2 | No associated skill
|-
| Recovering wounded
|-
| rowspan=20 | [[Farmer]]
| Butchery || [[Butcher]] || speed only
|-
| Tanning || [[Tanner]] || speed only
|-
| Farming (fields) || [[Planter]] || speed; crop yield (stack size)
|-
| Dyeing || [[Dyer]] || speed; dye quality
|-
| Gelding || [[Gelder]] || less likely to be injured
|-
| Soap making || [[Soaper]] || speed only
|-
| Wood burning || [[Wood burner]] || speed only
|-
| Potash making || [[Potash maker]] || speed only
|-
| Lye making || [[Lye maker]] || speed only
|-
| Milling || [[Miller]] || speed only
|-
| Brewing || [[Brewer]] || speed only
|-
| Plant gathering || [[Herbalist]] || speed; success and plant yield (stack size)
|-
| Plant processing || [[Thresher]] || speed only
|-
| Cheese making || [[Cheese maker]] || speed only
|-
| Milking || [[Milker]] || speed only
|-
| Shearing || [[Shearer]] || speed only
|-
| Spinning || [[Spinner]] || speed only
|-
| Cooking || [[Cook]] || speed; meal and ingredient quality
|-
| Pressing || [[Presser]] || speed only
|-
| Beekeeping || [[Beekeeper]] || speed only{{verify}}
|-
| rowspan=3 | [[Fishery worker]]
| Fishing || [[Fisherdwarf]] || speed; fish stack size
|-
| Fish cleaning || [[Fish cleaner]] || speed only
|-
| Fish dissection || [[Fish dissector]] || speed only
|-
| rowspan=5 | [[Metalsmith]]
| Furnace operating || [[Furnace operator]] || speed only
|-
| Weaponsmithing || [[Weaponsmith]] || speed; weapon quality
|-
| Armoring || [[Armorsmith]] || speed; armor quality
|-
| Blacksmithing || [[Blacksmith]] || speed; item and furniture quality
|-
| Metalcrafting || [[Metal crafter]] || speed; craft, item, decoration, designed building quality
|-
| rowspan=2 | [[Jeweler]]
| Gem cutting || [[Gem cutter]] || speed; gem craft quality
|-
| Gem setting || [[Gem setter]] || speed; decoration quality
|-
| rowspan=13 | [[Craftsdwarf]]
| Bookbinding || [[Bookbinder]] || ?
|-
| Papermaking || [[Papermaker]] || ?
|-
| Leatherworking || [[Leatherworker]] || speed; clothing, decoration, craft quality
|-
| Woodcrafting || [[Wood crafter]] || speed; craft quality
|-
| Stonecrafting || [[Stone crafter]] || speed; craft quality
|-
| Bone carving || [[Bone carving]] || speed; craft, decoration quality
|-
| Glassmaking || [[Glassmaking]] || speed; craft, item, furniture quality
|-
| Weaving || [[Weaver]] || speed; cloth quality
|-
| Clothesmaking || [[Clothier]] || speed; clothing, decoration quality
|-
| Strand extraction || [[Strand extractor]] || speed only
|-
| Pottery || [[Potter]] || speed; craft, item, furniture quality
|-
| Glazing || [[Glazer]] || speed; glaze quality
|-
| Wax working || [[Wax worker]] || speed; craft quality
|-
| rowspan=4 | [[Engineer]]
| Siege engineering || [[Siege engineer]] || speed; part, ammunition quality
|-
| Siege operating || [[Siege operator]] || speed; accuracy
|-
| Mechanics || [[Mechanic]] || speed; mechanism, furniture quality
|-
| Pump operating || [[Pump operator]] || none
|-
| rowspan=11 | [[Hauling]]
| Stone hauling
| rowspan=11 colspan=2 | No associated skill
|-
| Wood hauling
|-
| Item hauling
|-
| Burial
|-
| Food hauling
|-
| Refuse hauling
|-
| Furniture hauling
|-
| Animal hauling
|-
| Trade Good Hauling
|-
| Water Hauling
|-
| Push/Haul Vehicle
|-
| rowspan=4 | Other Jobs
| [[Cleaning]]
| rowspan=4 colspan=2 | No associated skill
|-
| [[Lever operation]]
|-
| Road building
|-
| Wall/floor construction
|}

Some jobs are not associated with a labor: [[food|eat]]ing, [[thirst|drinking]], [[sleep]]ing, going [[on break]], [[party]]ing, [[clean self|cleaning themselves]], and [[rest]]ing.

A few things are listed as "No Job" but can be considered labors in a different sense: running scared, not having a path to any place useful, and being [[insane]].

{{D for Dwarf}}
Take note before trying to get dwarves to do stuff, they probably won't do it. it's just the sad truth....dwarves are so stupid that when they run out of food, they won't even step outside to get that juicy plant sitting right outside the gate, unless you micro-manage them to death. another famed example: a forgotten beast is walking through a tunnel to your fort, so smart ol' you, decides to build a wall. You then tell someone to do it. Luckily for you, Urist McForgotWhatSide builds the wall. He will take a stone, most likely from across the map, haul to the wall, begin building, and have to get a drink. He drops the stone to get some beer, well, while he's up there, he might as well take a quick nap. well, he finally wakes, goes down to build a wall, only to see Urist McMason stole his rock, so he goes across the map for another boulder. He finally finishes the wall, but hears voices on the other side, "You built from the wrong side!" he then hears a hiss from down the tunnel. The forgotten beast walks up to Urist McForgotWhatSide, and bites him in the head: the severed part sails off in an arc. Poor old Urist, "died of old age".
[[File:labor_preview.jpg|thumb|300px|center|"Put both your backs into it!"]]
{{DFtext|<(: <(: () <): T|2:1}}

{{V50 menus}}
{{Category|Skills|*}}
{{Category|Interface}}
[[ru:Labor]]

User:Xjtu-blacksmith

2024-07-26T13:42:50Z

Xjtu-blacksmith: change the call

I'm currently the active administrator of [https://dfzh.huijiwiki.com Chinese Dwarf Fortress Wiki].

Labor

2024-07-26T13:12:16Z

Xjtu-blacksmith: /* Labor menu */ add menu icon

{{Quality|Exceptional}}
{{av}}
{{quote|'''"To get a job done, a dwarf has to do it."''' - Boss Urist McOverstates-the-obvious}}[[File:labor_icon_preview.png|right]]'''Labor''' is how jobs get done in a fortress; which labors are restricted to a dwarf determines which jobs they can or can't do. The [[skill]] level and [[attribute]]s of an individual determine how effectively they perform a job.

The game provides many flexible options to the player to allow or disallow certain actions of their dwarves, which can further add efficiency to a fortress. Visiting [[citizen]]s can also perform some labors.

==Introduction to labor==
*[[File:v50_labor_preview.png|right]]Your dwarves function as semi-autonomous entities, usually fulfilling their own basic needs, and sometimes performing jobs when able.
*Most jobs correspond to a '''labor''', which dwarves can be restricted from doing.
*Labors can be restricted to specific dwarves in groups called '''work details'''.
*'''Jobs''', the specific tasks to be completed, are created in various ways, including [[designation]]s, [[zone]]s, [[workshop]] tasks, and [[manager]] work orders, and once created, an idle dwarf who does not have that labor disabled will be assigned the job.
*As dwarves perform jobs, their '''skill''' in those areas increase. (The terms labor and skill are '''not''' synonyms. Skill is a measure of proficiency for a given labor, while a labor is the ability to do the work.)
**Some skills don't correspond to jobs, like [[social skills]] and miscellaneous abilities like [[swimming]].

==Labor menu==
The '''Labor''' menu tab is accessed with {{k|y}} or the fourth menu button {{menu icon|y}} at the bottom-left of the main [[interface]]. It contains four sub-tabs; [[Labor#Work details|Work details]], [[Labor#Standing orders|Standing orders]], [[Labor#Kitchen|Kitchen]], and [[Labor#Stone use|Stone use]].

===Work details===
The '''Work details''' tab lists the current sets of labors and who is allowed to do them. The work details are listed on the left side of the screen, selecting one shows a list of all labor assignable citizens in your fortress on the right. Each line shows the citizen's name, profession, applicable skill levels for this detail, specialization button, assigned details, and finally a check mark for this selected work detail. Clicking the specialization button will toggle specialization for that citizen, but clicking '''any''' other part of the line will toggle this selected work detail for that citizen, even other work detail icons.

Above the list, each work detail has a setting controlling how it is assigned to citizens:

*When "Only selected do this" is selected, the work detail will be assigned to any citizen with a check in the rightmost box on their line.
*With "Everybody does this" selected, all citizens in the fortress will have permission to do the work detail's labors. (Any checked boxes will be white, showing that the citizen in question will do this job even if specialized).
*When "Nobody does this" is selected, all citizens in the fortress will be ''banned'' from doing the work detail's labors. This does ''not'' override permission given by other works details. Any check marks/permissions set up before selecting "Nobody does this" will go red, showing that they are paused and they will be restored if you go back to "Only selected do this".

Labors associated with dwarf's [[occupation]] (such as being a [[Doctor]]) are always allowed.

Additionally, each citizen has the option to be '''specialized''', this is shown by the hammer and lock icon just to the right of their name (It can also be viewed and interacted with from the {{k|u}} Citizens menu). When this setting is on (icon is red [[File:Labor specialized.png]]), the citizen will only accept tasks given by workshops/[[occupation]]s they are assigned to and labors which have been assigned to them and are not restricted to "Nobody does this".

Here are all the possibilities:

{| class="wikitable"
|+ A dwarf can take a job if ''any'' of the Yes conditions below are satisfied:
|-
! !! Specialized [[File:Labor specialized.png]] !! Unspecialized [[File:Labor unspecialized.png]]
|-
| [[File:UI add worker.png]] The dwarf is assigned to the [[workshop]] or [[lever]] giving this job. || style="background:lightgreen" | Yes || style="background:pink" | No, unless a Yes applies
|-
| [[File:UI add worker.png]] The dwarf is assigned to the [[occupation]] giving this job. || style="background:lightgreen" | Yes || style="background:lightgreen"| Yes
|-
| The dwarf is '''selected''' under any work detail containing this job set to:

[[File:Interface white check.png]] "Everybody does this" OR

[[File:Interface green check.png]] "Only selected do this"
| style="background:lightgreen" | Yes
| style="background:lightgreen" | Yes
|-
| No work detail contains this job OR

the dwarf is '''unselected''' under any work detail containing this job set to
[[File:Interface empty check.png]] "Everybody does this"
| style="background:pink" | No, unless a Yes applies
| style="background:lightgreen" | Yes
|-
|}

====Default work details====
By default, the work details, and the labors associated with them, are as follows{{cite forum|180804/8438104}}

{| class="wikitable"
|-
| Miners†
||
* [[Mining]]
|-
| Woodcutters†
||
* [[Woodcutting]]
|-
| Hunters†
||
* [[Hunting]]
|-
| Planters
||
* [[Farming (fields)]]
|-
| Fisherdwarves
||
* [[Fishing]]
|-
| Plant gatherers
||
* [[Plant gathering]]
|-
| Stonecutters
||
* [[Stonecutting]]
|-
| Engravers
||
* [[Stone engraving]]
|-
| Haulers
||
* All [[hauling]] labors
|-
| Orderlies
||
* [[Suturing]]
* [[Dressing wounds]]
* [[Feed patients/prisoners]]
* [[Recovering wounded]]
|}

† The Mining, Woodcutting, and Hunting labors are only accessible from these default work details.

====Custom work details====
{{TipBox2|titlebg=#dd0|float=right|Utilities|If you would like more control or information for labor assignments, [[Utilities#Dwarf Therapist|Dwarf Therapist]] and/or [[Utility:DFHack|DFHack]] can help, when available.}}
Additional work details can be defined. Click "Add new work detail", select which [[labor]]s will be associated with it, and then click done. You can then rename the new work detail.

There is currently no way to choose the work detail's icon, so you are stuck with what the game chooses. The roman numerals are in the file <code>Dwarf Fortress\data\vanilla\vanilla_interface\graphics\images\interface_bits_labor.png</code> and can be changed, but will still be used in order.

===Standing orders===
{{main|Standing orders}}

===Kitchen===
This tab lists all item types currently within the fortress that can be used for either [[cooking]] or [[brewing]]. It is separated into four tabs:
*Vegetables, fruit, and leaves
*Seeds
*Drinks
*Meat, fish, and others.

On each tab, the items are listed in the left most column ({{DFtext|Ingredient Type|7:1}}). The second column ({{DFtext|Number|7:1}}) lists the number of each ingredient currently possessed. The last column ({{DFtext|Permissions|7:1}}) is subdivided into two additional columns, cooking and brewing. This is the most important part, as it shows you whether dwarves are currently allowed to use the ingredient for the given task. Possible values are:

* [[File:cook_disabled_icon.png|18px]] or [[File:brew_disabled_icon.png|18px]] ({{DFtext|+|6:1}}{{DFtext|C|4:1}} or {{DFtext|+|6:1}}{{DFtext|B|5:0}} in ASCII mode) - This item could be used for the task, but is currently disallowed.
* [[File:cook_enabled_icon.png|18px]] or [[File:brew_enabled_icon.png|18px]] ({{DFtext|+|6:1}}{{DFtext|C|4:1}} or {{DFtext|-|4:0}}{{DFtext|B|5:0}} in ASCII mode) - This item is enabled for use in the task, and dwarves have permission to do so.
* [[File:cook_unused_icon.png|18px]] or [[File:brew_unused_icon.png|18px]] ({{DFtext|X|6:0}}{{DFtext|C|4:1}} or {{DFtext|X|6:0}}{{DFtext|B|5:0}} in ASCII mode) - This indicates that the given item cannot be used in this way. For example, Deer meat cannot be brewed (Any [[Alcohol#Cooking|alcohol can be cooked]]).

Note that when a new food is obtained, the default is [[File:cook_enabled_icon.png|18px]] and [[File:brew_enabled_icon.png|18px]] ({{DFtext|X|6:0}}{{DFtext|C|4:1}} or {{DFtext|X|6:0}}{{DFtext|B|5:0}}). This includes recently [[butcher|butchered]] animals, [[food]]stuffs gained from trading, first [[Crop|crops]] from [[Seed|seeds]], and plants [[Plant gathering|gathered]] from the wild. Item types for which all items have been designated as [[Forbid|forbidden]] will not be listed on this menu.

Cooking permission is also used/needed for [[Cheese|cheesemaking]] from [[milk]] items{{verify|I last embarked with all milks and set them all to not cook so I could make them into cheese first, but I want to double check.}}

===Stone use===
The stone use tab is separated into two tabs, Economic Stone and Other Stone. Economic Stone lists all [[Economic stone|economic stone]] (stones that have a value and purpose besides masonry) that can exist in the game. As an example, [[chalk]] can be used in the process of creating [[steel]]. Other Stone lists all non-economic stone.

Both tabs allows you to control what stone is used for menial purposes (masonry, building construction, walls, etc.). By default all economic stone, except layer stones present on the map, is disallowed and all other stone is allowed.

The Economic Stone tab also provides a full list of each economic stone's uses and if it is [[magma-safe]] or not.

== Tool requirements ==
For a few specific jobs, a matching '''tool''' is also required for a dwarf to obey the job assignment. Any active [[miner]] needs a [[pick]], any active wood cutter needs a [[battle axe]], and any active [[hunter]] needs a [[crossbow]] (with quiver and bolts). If a labor needs a tool, the labor is considered '''exclusive''' such that you can only assign one of the three labors listed to any single dwarf at any one time.

This means that a dwarf cannot be, for instance, a [[Miner]] and a [[Hunter]] simultaneously, since both labors require a tool. If a dwarf is assigned a tool-labor and another tool-labor was previously assigned to said dwarf, the (old) tool-labor is automatically and silently unassigned, and that tool is immediately dropped where they stand at the time.

Additionally, the assignment of these tools '''overrides''' any [[Squad|uniform]] assigned to a dwarf's [[squad]], so [[military]] dwarves should never be assigned any of the aforementioned labors.

To be used, a tool cannot be [[forbidden]], nor in possession of another dwarf (even one that does not currently have a job), and a [[path]] must be available from the dwarf to that type of tool. If a tool is not available, the dwarf will typically attempt to fulfil other [[need]]s. It is possible, by using locked doors etc. to limit the paths, to force a specific tool to be assigned to a dwarf, but otherwise the tool will be randomly assigned, sometimes involving a dwarf walking long distances and past perfectly useful tools to find the one they think they want.

== Facility requirements ==
Many jobs require a workshop or some other [[Furnace|facility]] in order to be completed. Jobs are designated by way of the workshop, and any dwarf with the corresponding labor associated with the workshop will go to the shop, provided they are not eating, sleeping, drinking, etc..., and begin to complete the task. Most workshop jobs also require some raw materials in order to complete the production.

== Managing labor and demand ==
This can be done from the labor menu {{k|y}} under the [[work detail]]s tab.
* You can view a list of all current, queued, and suspended jobs, as well as which dwarves are doing them, on the {{k|t}}asks menu.
* A [[manager]] is incredibly useful for managing production jobs ([[workshop]] based). They can queue up a significant list of jobs without the need to select the various workshops, and place orders in bulk (or to be repeated). That said, there are some caveats, the most important being that queued jobs must be done in the correct order of materials required, or the orders will auto cancel. Also, you should not assign your manager to labors that are in high demand, as this will keep them from going to their [[office]] to place the orders.
* [[Migrants|Migrating]] dwarves will typically arrive with certain work details already assigned. You will likely want to change these to put them to work in a way that best suits your fortress.

== Advanced labor management and design ==
Managing your dwarves can be a tricky business. If the in-game labor menu is not to your liking, [[Utilities#Dwarf Therapist|Dwarf Therapist]] or [[Utility:DFHack|DFHack]] are both useful tools that assist you in managing your labors.

As your fortress grows, so will your labor pool, and the way you assign that labor will change over time. Typically at embark, you will have at least one Miner, a Wood cutter, Farmer, Carpenter, Mason/Stonecrafter, Cook/Brewer, Mechanic/Architect, one of which will also be a Broker/Appraiser. There are multiple combinations but this is typical (see [[Embark]] and [[Starting build]]). Early on, you will probably want to focus on fortress design and development, such that you will place priority on [[mining]] and [[masonry]], supplemented by [[carpentry]].

In order to maximize the benefit of highly skilled labor, you will eventually want to specialize your labor, such that each dwarf has a very limited number of labors assigned. Keep in mind however, that some dwarves experience minor negative feelings at not being able to perform a craft or a martial art for too long.

Hauling: Nothing can bog down your production like the distraction of hauling jobs. Losing your fort to a siege is [[fun]], but losing because all your skilled laborers spend all their time hauling stuff is no fun. One solution is to use dedicated haulers. The migrants who appear having no skilled labor, and whose attributes pretty much suck all around, aka [[peasant]]s, are best used as dedicated haulers.

== Labor, skill, and product quality ==
The amount of [[experience]] a dwarf has with a certain labor will determine how well they go about performing this labor; the more experience, the greater the skill. Certain job types can be completed more quickly, based on the skill in the labor. There are exceptions, such as [[Health care|nursing]] and [[hauling]] which will never be completed more quickly, regardless of skill.

Certain labors will produce products that have a [[quality]] tag, typically those associated with the production of an item from a workshop. The table below lists in which labors the dwarf's experience will impact the quality of produced items and in which labors a higher experience will only be beneficial for the speed of production.

* Many labors, most notably [[hauling]], have no associated skill, do not generate experience, and do not improve with practice.

==Strange moods==
{{main|Strange mood}}
A dwarf under a strange mood will perform a specific task to create an [[artifact]] that is outside of the player's control. Until they complete the task, both they and the workshop they claim will be unavailable for any labor. If the dwarf cannot complete the artifact, they will go [[insane]] and be permanently unable to perform any labor.

{{Translation
| dwarven = èrith
| elvish = equa
| goblin = akul
| human = ebe
}}

==List of labors==

{| border="1" cellpadding="5" cellspacing="0" class="wikitable"
! Category !! Labor !! Skill !! Benefits of higher skill
|-
| Miner
| [[Mining]]
| [[Miner]]
| speed only
|-
| rowspan=3 | [[Woodworker]]
| Carpentry || [[Carpenter]] || speed; item and furniture quality
|-
| Crossbow-making
| [[Bowyer]]
| speed; weapon quality
|-
| Wood cutting
| [[Wood cutter]]
| speed only
|-
| rowspan=4 | [[Stoneworker]]
| Masonry
| [[Mason]]
| speed only
|-
| Stone carving
| [[Stone carver]]
| speed; items and furniture quality
|-
| Stonecutting
| [[Stonecutter]]
| speed only
|-
| [[Stone engraving]]
| [[Engraver]]
| speed; engraving quality
|-
| rowspan=5 | [[Ranger]]
| Animal training
| [[Animal trainer]]
| speed; training quality
|-
| Animal care
| [[Animal caretaker]]
| none (not implemented)
|-
| Hunting
| [[Ambusher]]
| reduced chance of being detected
|-
| Trapping
| [[Trapper]]
| success rate? trap quality?{{verify}}
|-
| Small animal dissection
| [[Animal dissector]]
| speed only
|-
| rowspan=5 | [[Doctor]]
| Diagnosis || [[Diagnostician]] || speed; chance of accurately diagnosing a [[syndrome]]
|-
| Surgery || [[Surgeon]] || speed, amount of bleeding caused, chance of failure
|-
| Setting bones || [[Bone doctor]] ||rowspan=3 | speed only
|-
| Suturing || [[Suturer]]
|-
| Dressing wounds || [[Wound dresser]]
|-
| rowspan=2 | Other [[Healthcare]]
| Feed patients/prisoners
| rowspan=2 colspan=2 | No associated skill
|-
| Recovering wounded
|-
| rowspan=20 | [[Farmer]]
| Butchery || [[Butcher]] || speed only
|-
| Tanning || [[Tanner]] || speed only
|-
| Farming (fields) || [[Planter]] || speed; crop yield (stack size)
|-
| Dyeing || [[Dyer]] || speed; dye quality
|-
| Gelding || [[Gelder]] || less likely to be injured
|-
| Soap making || [[Soaper]] || speed only
|-
| Wood burning || [[Wood burner]] || speed only
|-
| Potash making || [[Potash maker]] || speed only
|-
| Lye making || [[Lye maker]] || speed only
|-
| Milling || [[Miller]] || speed only
|-
| Brewing || [[Brewer]] || speed only
|-
| Plant gathering || [[Herbalist]] || speed; success and plant yield (stack size)
|-
| Plant processing || [[Thresher]] || speed only
|-
| Cheese making || [[Cheese maker]] || speed only
|-
| Milking || [[Milker]] || speed only
|-
| Shearing || [[Shearer]] || speed only
|-
| Spinning || [[Spinner]] || speed only
|-
| Cooking || [[Cook]] || speed; meal and ingredient quality
|-
| Pressing || [[Presser]] || speed only
|-
| Beekeeping || [[Beekeeper]] || speed only{{verify}}
|-
| rowspan=3 | [[Fishery worker]]
| Fishing || [[Fisherdwarf]] || speed; fish stack size
|-
| Fish cleaning || [[Fish cleaner]] || speed only
|-
| Fish dissection || [[Fish dissector]] || speed only
|-
| rowspan=5 | [[Metalsmith]]
| Furnace operating || [[Furnace operator]] || speed only
|-
| Weaponsmithing || [[Weaponsmith]] || speed; weapon quality
|-
| Armoring || [[Armorsmith]] || speed; armor quality
|-
| Blacksmithing || [[Blacksmith]] || speed; item and furniture quality
|-
| Metalcrafting || [[Metal crafter]] || speed; craft, item, decoration, designed building quality
|-
| rowspan=2 | [[Jeweler]]
| Gem cutting || [[Gem cutter]] || speed; gem craft quality
|-
| Gem setting || [[Gem setter]] || speed; decoration quality
|-
| rowspan=13 | [[Craftsdwarf]]
| Bookbinding || [[Bookbinder]] || ?
|-
| Papermaking || [[Papermaker]] || ?
|-
| Leatherworking || [[Leatherworker]] || speed; clothing, decoration, craft quality
|-
| Woodcrafting || [[Wood crafter]] || speed; craft quality
|-
| Stonecrafting || [[Stone crafter]] || speed; craft quality
|-
| Bone carving || [[Bone carving]] || speed; craft, decoration quality
|-
| Glassmaking || [[Glassmaking]] || speed; craft, item, furniture quality
|-
| Weaving || [[Weaver]] || speed; cloth quality
|-
| Clothesmaking || [[Clothier]] || speed; clothing, decoration quality
|-
| Strand extraction || [[Strand extractor]] || speed only
|-
| Pottery || [[Potter]] || speed; craft, item, furniture quality
|-
| Glazing || [[Glazer]] || speed; glaze quality
|-
| Wax working || [[Wax worker]] || speed; craft quality
|-
| rowspan=4 | [[Engineer]]
| Siege engineering || [[Siege engineer]] || speed; part, ammunition quality
|-
| Siege operating || [[Siege operator]] || speed; accuracy
|-
| Mechanics || [[Mechanic]] || speed; mechanism, furniture quality
|-
| Pump operating || [[Pump operator]] || none
|-
| rowspan=11 | [[Hauling]]
| Stone hauling
| rowspan=11 colspan=2 | No associated skill
|-
| Wood hauling
|-
| Item hauling
|-
| Burial
|-
| Food hauling
|-
| Refuse hauling
|-
| Furniture hauling
|-
| Animal hauling
|-
| Trade Good Hauling
|-
| Water Hauling
|-
| Push/Haul Vehicle
|-
| rowspan=4 | Other Jobs
| [[Cleaning]]
| rowspan=4 colspan=2 | No associated skill
|-
| [[Lever operation]]
|-
| Road building
|-
| Wall/floor construction
|}

Some jobs are not associated with a labor: [[food|eat]]ing, [[thirst|drinking]], [[sleep]]ing, going [[on break]], [[party]]ing, [[clean self|cleaning themselves]], and [[rest]]ing.

A few things are listed as "No Job" but can be considered labors in a different sense: running scared, not having a path to any place useful, and being [[insane]].

{{D for Dwarf}}
Take note before trying to get dwarves to do stuff, they probably won't do it. it's just the sad truth....dwarves are so stupid that when they run out of food, they won't even step outside to get that juicy plant sitting right outside the gate, unless you micro-manage them to death. another famed example: a forgotten beast is walking through a tunnel to your fort, so smart ol' you, decides to build a wall. You then tell someone to do it. Luckily for you, Urist McForgotWhatSide builds the wall. He will take a stone, most likely from across the map, haul to the wall, begin building, and have to get a drink. He drops the stone to get some beer, well, while he's up there, he might as well take a quick nap. well, he finally wakes, goes down to build a wall, only to see Urist McMason stole his rock, so he goes across the map for another boulder. He finally finishes the wall, but hears voices on the other side, "You built from the wrong side!" he then hears a hiss from down the tunnel. The forgotten beast walks up to Urist McForgotWhatSide, and bites him in the head: the severed part sails off in an arc. Poor old Urist, "died of old age".
[[File:labor_preview.jpg|thumb|300px|center|"Put both your backs into it!"]]
{{DFtext|<(: <(: () <): T|2:1}}

{{V50 menus}}
{{Category|Skills|*}}
{{Category|Interface}}
[[ru:Labor]]

Citizen

2024-07-26T12:53:43Z

Xjtu-blacksmith: create redirect

#REDIRECT [[Citizenship]]

Elf language

2024-07-25T06:45:29Z

Xjtu-blacksmith: fix double link

#REDIRECT[[Elven language]]

Dwarf fortress mode

2023-03-24T13:15:51Z

Xjtu-blacksmith:

{{migrated article}}
{{Quality|Unrated}}
{{av}}
{{old}}
: ''This is a detailed reference guide. For a beginner tutorial, see [[Quickstart guide]], see further [[tutorials]].''
:''[[Modding guide|Modding]] is not covered on this page.''

'''Fortress mode''' is the most popular of three modes in ''Dwarf Fortress'', with the other two being [[Adventurer mode]] and [[Legends mode]], often the mode implied when one talks about ''Dwarf Fortress''. Fortress mode is a construction and management simulation of a colony of dwarves. In fortress mode, you pick an [[embark]] location, and then assign your seven initial [[dwarves]] some starting [[Skill | skills]], equipment, provisions, and perhaps, [[animals]] to bring along. After preparations are complete and your hardy explorers [[embark]], they'll be faced with the fortress site you picked down to every little detail; from geologically appropriate stone types, to roaring waterfalls, to, for example, ornery [[Hippo | hippopotami]]. Rather than control individual dwarves, you design everything, and your dwarves will go about implementing your designs on their own.

== Goals ==
Fortress mode is considered a [[wikipedia:Construction_and_management_simulation_games|construction and management simulation game]]. This entails that few goals are imposed upon the player by the game.

The most apparent goal is survival, as your endeavors at the chosen site will, [[Reclaim fortress mode|for the moment]], end if the last dwarf dies. With this comes the need to keep your dwarves happy, as unhappy dwarves will cultivate some very unhealthy (yet surprisingly [[Losing|Fun]]) habits like murdering their colleagues.

Another goal of sorts, programmed into the game, is creating a fortress that attracts the king/queen of your civilization. Therefore, players typically, but by no means necessarily, choose to expand into a thriving community with skilled [[Labor|workers]], [[military|battle-ready warriors]] and [[nobles]], creating ridiculous amounts of [[wealth|wealth]] like fine [[finished goods|crafts]], excellent armor, valuable [[furniture]], decorated with precious [[gem]]s, all the while protecting them from [[siege|foes]] with deadly [[trap]]s and a trained [[military]]. Avoiding imminent death also requires providing the dwarves with plenty of [[food]] and [[alcohol]], by way of [[farming|farms]] above and below ground, while [[clothing]] from [[leather]] or [[cloth]] will keep them happy.

Of course, every dwarf loves precious [[metal]]s, but the only way to find them is to [[mining|dig]]. Make sure you don't delve too greedily and too deep, for many creatures dwell in the [[caverns]] below...

== The world ==
To play ''Dwarf Fortress'' in fortress mode, you must generate a world that includes a dwarven civilization - see [[World generation]] for detailed instructions. After at least one world has been generated, you will be able to start the game. Only one game may be going on in a world at the same time.

=== Geographic features / Inhabitants / History ===
The main features of a world are [[biome]]s on the surface and [[stone layer]]s underground, some of which may contain [[aquifer]]s. Other surface features that are significant, but which aren't biomes, strictly speaking, are [[river]]s, [[volcano]]es, and [[cave]]s. There are also [[cavern]]s and [[magma sea]]s everywhere underground which your dwarves will most likely encounter, but you can't see these on the world map, or on the local map, for that matter, until you dig into them. There may also be other [[Fun]] things underground that you can't see. You will have to find these on your own, if they exist.

Every playable world will be inhabited by various [[creature]]s, [[civilization]]s, [[night creature]]s, and [[megabeast]]s (including [[titan]]s and [[forgotten beast]]s) in addition to your dwarves. You may encounter all of these types of inhabitants at some point in the form of wildlife, invaders, or rampaging forces of nature.

Given that your world includes creatures and civilizations capable of independent action, it also has a history that is viewable in [[legends mode]], historical events showing up in [[engraving]]s and other artwork created by your dwarves. Historical dates are expressed in terms of the [[Calendar|dwarven calendar]].

You will also be making history as events occur in your fortress, and these events will be recorded for all time in the annals of your world, even if you'd rather that they not be. These events may later become the subject of various [[engraving]]s and [[decoration]]s created by your dwarves, or those in a later fortress.

== Embarking ==
{{Main|Embark}}
:''See also: [[Reclaim fortress mode]]''

[[File:FlowchartDF.png|thumb|250px|right|[[From Caravan to Happy Dwarves|From Caravan to Happy Dwarves]] – a flowchart showing approximately what sequence of actions most people will take after embarking.]]

Before starting to build a fortress, you must choose the embark location in the world, then assign skills and supplies to the seven dwarves on the expedition team you will embark with into that environment. This is the embarking process, and is a major subject on its own - see the [[Embark]] guide for all the details. Also see [[Starting build]] for more information on outfitting your expedition. After you embark, the real game begins.

== Gameplay user interface ==
{{Main|Interface}}
Your main view of the in-game world is a top-down view of a multi-layered environment. You can move your view in the four main cardinal directions as well as up and down [[Z-level]]s (elevation) to see different layers. There is also a command menu that lets you issue commands that your dutiful dwarves will attempt to follow.

This section covers most of the screens and user interface elements used after embarking, at least in brief. It does not necessarily tell you how to accomplish every task you might need to, but instead just describes what you see on the screen and what various keystrokes do.

Later sections in this document and ''many'' other articles on this wiki help you tie all of this together by describing the sequence of actions needed to accomplish various things in the game; see [[Menu]] for a more detailed reference for the UI itself.

=== Common UI concepts ===
{{KeyConventions|4}}

=== Pausing and resuming ===
{| class="wikitable"
|-
| {{K|Space}}
| Pause/Unpause the game
|}

Entering all menus (except the {{K|s}}quads menu) will automatically pause the game, but if you want to pause or unpause the game without entering a menu use {{K|Space}}. You will see {{DFtext|*PAUSED*|3:3:1}} appear in the upper left corner of the window when the game is paused. Certain [[announcement]]s will also pause the game automatically and you will have to unpause it manually to proceed.

=== Main screen ===
{| class="wikitable"
|-
| [[Image:Mouse-wheeldown.png|20px|Scroll mouse wheel down.]][[Image:Mouse-wheelup.png|20px|Scroll mouse wheel up.]] or {{K|[}} {{K|]}}
| Zoom in and out('['and ']' must be set manually in the key bindings)
|-
| {{k|Tab}}
| Toggle mini-map and command menu.
|-
| {{k|F11}}
| Toggle fullscreen mode
|}

The screen at the top level of the user interface hierarchy consists of the '''main map''', a '''command window''', and an '''overview mini-map''' area along with a few '''status indicators''' around the edge. While the main map is always visible at the top level of the UI, you can use the {{K|Tab}} key to show and hide the command window and overview map areas, giving you more space to view the main map if desired.

=== Options screen ===
{| class="wikitable"
|-
| {{K|Esc}}
|
* Enter options menu (if at top level)
* Move back up one UI level (if not at top level)
|}

Assuming you are at the top level of the user interface looking at the map, you can hit {{K|Esc}} to enter the options menu.

*{{DFtext|Save and return to title menu}} – Saves the game, unloads the fortress, and returns to the main menu screen. There is no "save and continue" option, but saves can be [[saved game folder|backed up and reloaded]].
*{{DFtext|Save and continue playing}}
*{{DFtext|Retire the fortress (for the time being)}} – Saves and ends your control of the fort, giving limited control to the game. Most of the fortress remains as is, with citizens, livestock, and most items continuing to exist. Not always available, such as during [[siege]]s. After it saves and returns to the main menu you may start a new game in any mode including to [[Reclaim fortress mode|unretire]] the fortress.
*{{DFtext|Abandon the fortress to ruin}} (or {{DFtext|Succumb to Invasion}}) – This permanently [[abandon]]s the fortress, saves the map to the world's data files for later use, and returns to the main menu. Once you abandon a fort, all of your dwarves leave the site, all of your livestock dies, and all items including corpses will be scattered around the map before it is saved. This is how you "give up" on a fortress. You might later [[Reclaim fortress mode|reclaim]] the fortress with a new group of dwarves or visit it with an adventurer in [[Adventurer mode]].
*{{DFtext|Quit without saving}}
*{{DFtext|Settings}}
*{{DFtext|Return to game}} – Exits the options menu. You can also just press {{K|Esc}}.

=== Main map ===
[[File:bentgirder-embark.png|thumb|300px|Main map on the left, command window on the right.]]
[[Image:3_dimensions.png|right|300px]]
{| class="wikitable"
|-
| {{k|↑}} {{k|↓}} {{k|←}} {{k|→}} ( + {{k|Shift}})
| Move map view around
|-
| {{k|8}} {{k|2}} {{k|4}} {{k|6}} {{k|7}} {{k|9}} {{k|1}} {{k|3}} (keypad)
| Move map view around
|-
| {{k|<}} {{k|>}}
| Move one [[Z-level]] up or down.
|-
| {{k|F1}}
| Zoom to starting location (default [[#Hotkeys|hotkey]])
|}
The main map window is what you will be looking at for the majority of the time. This is where all of the action happens.

While the play area itself is three-dimensional, the window is not; you can only view one [[Z-level]] at a time. You can change which Z-Level is currently displayed using {{k|<}} and {{k|>}}.

On the far right side of the screen is the '''depth bar''' showing you the approximate depth, below or above ground, of the current [[Z-level]] that the map is displaying. This indicator is relative to the surface, so it will change if you move the map around an area with a non-flat surface, even if you don't press {{K|<}} or {{K|>}}.

==== Map cursor ====
{| class="wikitable"
|-
| {{k|8}} {{k|2}} {{k|4}} {{k|6}} {{k|7}} {{k|9}} {{k|1}} {{k|3}} (keypad)
| Move map cursor 1 tile
|-
| {{k|↑}} {{k|↓}} {{k|←}} {{k|→}}
| Move map cursor 1 tile
|-
| {{k|Shift}} + direction key
| Move map cursor 10 tiles
|}

After entering a command that involves the map cursor ({{Raw Tile|X|6:0:1}}), you can use {{k|↑}} {{k|↓}} {{k|←}} {{k|→}} as well as the numeric keypad keys to move the cursor around in all eight directions. If you hold {{k|Shift}} while pressing one of these, the cursor will move 10 tiles instead of one, enabling you to move it more quickly.

=== Overview map ===
The overview mini-map shows a compact version of the entire available map area. This can be useful especially if your embark zone is very large. After the fortress has settled into certain areas of the map, its utility decreases and it can be hidden with {{K|Tab}} to provide more space for the main map.

A cursor that looks like {{Raw Tile|X|6:0:1}} on the overview map shows approximately what part of the map you are viewing in the main map window. Parts of the map inhabited by dwarves will be highlighted in blue.

=== Status indicators ===
In the upper left corner of the screen, you may see some '''report flags''' indicating that new combat-related [[Reports]] have been generated. Some common flags are:

:{{Tile|C|4:7:1}}: new [[combat]] report available
:{{Tile|H|2:7:1}}: new [[Ambusher#Hunting|hunting]] report available
:{{Tile|S|3:7:1}}: new [[sparring]] report available

Press {{K|r}} to view the new reports in the [[DF2014:Reports#Combat|reports screen]]. Once you do so, the flags will be reset.

There is also an '''idle counter''', usually in the upper right, indicating how many dwarves are milling around uselessly, in need of something productive to do.

An '''[[FPS]] (Frames Per Second) counter''' may also be present on the screen if it has been enabled. It is disabled by default. See [[Frames per second]] for more information on what this counter means, as well as how to enable/disable it.

=== Command window ===
[[File:MainMenu.png|The command window.|frame]]
This is where key menus and most of the textual information about tiles and buildings is displayed. You can toggle it between single width, double width, and hidden using {{K|Tab}}. The double-width option is particularly useful when lines of text are too long to fit. Once you become familiar with the UI you may want to hide it completely; it will reappear as needed when you activate a command.

The most important interfaces that use the command window are listed below. Many of these encompass a wide variety of functionality so they will not be fully described here. See the linked articles for more details on how they are used.

== Your dwarves ==

Your [[Dwarf|dwarves]] are one of the creature types who implement your designs in-between periods of drinking, eating, partying, drinking again, sleeping, and entertaining themselves. While you do not have full control of your dwarves, you have more control over them than any other creatures. Be aware that it is not necessarily always the case that a dwarf is friendly; [[Insanity|insane]] dwarves, [[Werebeast|weredwarves]] or [[Vampire|vampires]] are anything but.

For a comprehensive reference, Reddit user DarxusC has done research on the minimum requirements to keep dwarves alive for long periods of time [https://www.reddit.com/r/dwarffortress/comments/cvdssa/a_video_showing_how_little_is_needed_to_survive/ here].

=== Eating, drinking, and sleeping ===
Dwarves need [[food]] to eat, [[alcohol]] to drink (water is a poor substitute), and time to [[sleep]]. If only one of these is available, it better be [[alcohol]]; while water will keep dwarves alive, they will actually work more slowly and get unhappy thoughts (see below) if they don't get much alcohol to drink.

Dwarves will also get unhappy thoughts if forced to eat a single type of food or drink a single type of alcohol all the time, so variety is also important. Dwarves will also get unhappy thoughts if forced to sleep on the floor.

=== Happiness ===
While going about their day, dwarves will get happy and unhappy [[thought]]s, depending on what sorts of things happen to them. This will nudge their happiness levels up or down each time one such event occurs to them. If they become too unhappy, they may throw [[tantrum]]s, or go completely [[Insanity|berserk]], killing and destroying things.

=== Children and immigration ===
Periodically, new dwarves from the outside world will [[Immigration|migrate]] to your fortress, drawn by tales of, and looking to share in, your wealth and success. Female dwarves will also get pregnant and have [[children]], if they are [[Marriage|married]] to a male dwarf.

=== Jobs, labors and skills ===
Any adult dwarf can perform any [[labor]] even if they have no [[skill]] in that area. Unskilled dwarves will simply be slow and not very good at what they are trying to do, but, with practice, dwarves will acquire skill, and become faster and better at their jobs. Lack of practice for long periods leads to skill "rust".

=== Nobles ===
[[Noble]]s are dwarves who have special positions within your fort. Some of these are appointed, such as your [[broker]] and [[bookkeeper]], but others, such as the [[mayor]], are essentially forced on you by conditions in the game. See the main article on [[Noble]]s for more information.

=== Death ===

Assuming they somehow manage to avoid starving, dehydrating, freezing, drowning, burning, falling, being crushed, or otherwise suffering fatal [[wound]]s or [[soap|infections]], your dwarves will inevitably [[Death|die]] of old age. Unfortunately, they are a bit picky about how they are [[Coffin|buried]] or otherwise [[Memorial|memorialized]], and they will [[Ghost|cause trouble]] if they are unsatisfied with their remembrance. Corpses lying around can also pose a hazard if there are [[Necromancer|necromancers]] in the area.

A [[Healthcare]] industry might help your wounded dwarves postpone death.

== Digging ==
{{Main|Mining}}

Digging is an essential part of building a fort. There are several reasons you might want to dig, such as searching for various stone types, ores and gems, or simply to create the basic tunnels and rooms in your fort.

All of the digging operations are considered [[Mining]]. Even if your goal is simply to dig out a passage and you don't care about extracting ore, your miners will be generating [[stone]] as a byproduct unless they are digging through [[soil]]. See [[Stone management]] for ways to deal with all the unwanted stone.

== Stockpiles ==
{{Main|Stockpile}}

'''Stockpiles''' are where [[dwarf|dwarves]] will store items of various types. Dwarves with the corresponding "[[hauling]]" job on will seek out items that aren't already on a stockpile that accepts them and carry them to the appropriate stockpile. See the main [[Stockpile]] article for detailed information on setting up stockpiles.

== Rooms, furniture, and portals ==

To remove one of these, Click on the furniture Item, the press the remove build icon . This will mark the item for removal and a hauling job will be queued. Eventually a dwarf will show up and haul the item off to a [[stockpile]] if one exists.

=== Furniture ===
{| class="wikitable"
|-
| {{Menu icon|b|f|b|sep=-}}
| place Bed
|-
| {{Menu icon|b|f|r|sep=-}}
| place Chair or Throne (seat)
|-
| {{Menu icon|b|f|t|sep=-}}
| place Table
|-
| {{Menu icon|b|f|h|sep=-}}
| place Chest or Container
|-
| {{Menu icon|b|f|n|sep=-}}
| place Cabinet
|-
| {{Menu icon|b|f|x|sep=-}}
| place Burial Receptacle (coffin)
|-
| {{Menu icon|b|f|l|sep=-}}
| place Memorial Slab
|-
| {{Menu icon|b|f|u|sep=-}}
| place Statue
|-
| {{Menu icon|b|f|T|sep=-}}
| place Traction Bench
|-
| {{Menu icon|b|f|o|sep=-}}
| place Book Case
|-
| {{Menu icon|b|f|y|sep=-}}
| place Display (Pedestal)
|-
| {{Menu icon|b|f|p|sep=-}}
| place Offering Place (Alter)
|-
| {{Menu icon|b|f|i|sep=-}}
| place Instrument
|}
Assuming that dwarves have already made a piece of [[furniture]], they can install it somewhere using one of these commands.

=== Defining rooms ===
{{Main|Room}}

Areas can be defined as a [[room]] using {{Menu icon|z|sep=-}} (zones), some rooms may require specific pieces of furniture to function properly. The zones menu can also be used to undefine rooms, with or without removing the associated furniture.

=== Doors and hatches ===
{| class="wikitable"
|-
| {{Menu icon|b|p|r|sep=-}}
| place door
|-
| {{Menu icon|b|p|h|sep=-}}
| place floor hatch
|}
These commands allow you to place already created [[door]]s and [[hatch cover]]s assuming that you have an adjacent wall.

== Constructions ==
{{Main|Construction}}

[[Construction]]s are features that are built in place, rather than carved out of existing rock. Constructions are how you build above-ground structures or structures in any other place where there's no rock or soil to carve them out of.

Constructions are usually built out of, and thus require, [[stone]] or [[wood]], but you can also use a variety of materials (such as metal) to build them. Possible constructions include [[Floor]]s, [[Wall]]s, [[Stair]]s, [[Ramp]]s, and [[Fortification]]s. Some constructions may also require to be created in a workshop first before being able to place them down, such as [[Grate]].

=== Walls, floors, and stairs ===
{| class="wikitable"
|-
| {{Menu icon|b|n|sep=-}}
| build Constructions submenu
|-
| {{Menu icon|b|n|l|sep=-}}
| build Constructed [[Wall]]
|-
| {{Menu icon|b|n|f|sep=-}}
| build Constructed [[Floor]]
|-
| {{Menu icon|b|n|r|sep=-}}
| build Constructed upward [[Ramp]]
|-
| {{Menu icon|b|n|t|sep=-}}
| build Constructed [[Stair]]
|-
| {{Menu icon|b|n|b|sep=-}}
| build a [[bridge]]
|-
| {{Menu icon|b|n|o|sep=-}}
| build Paved [[road]]
|-
| {{Menu icon|b|n|O|sep=-}}
| build Dirt road
|-
| {{Menu icon|b|n|F|sep=-}}
| build a [[Fortification]]
|-
| {{Menu icon|b|n|G|sep=-}}
| build a Wall [[grate]]
|-
| {{Menu icon|b|n|g|sep=-}}
| build a Floor grate
|-
| {{Menu icon|b|n|M|sep=-}}
| build a Vertical bar
|-
| {{Menu icon|b|n|m|sep=-}}
| build a Floor bar
|-
| {{Menu icon|b|n|y|sep=-}}
| build a Glass [[window]]
|-
| {{Menu icon|b|n|Y|sep=-}}
| build a Gem window
|-
| {{Menu icon|b|n|p|sep=-}}
| build a [[Support]]
|-
| {{Menu icon|b|n|k|sep=-}}
| build a [[Track]]
|-
| {{Menu icon|b|n|K|sep=-}}
| build a Track stop
|-
|}

Walls, Floors, and Stairs are removed with the {{Key|m}}ining menu and selecting {{Key|x}} Remove Construction. Bridges and roads are removed by selecting them and clicking the button in the top right corner.

=== Bridges ===

A [[Bridge]] is not only used to cross rivers or chasms, but can also be used as a large door when built as a drawbridge. Such use requires that a [[Lever]] be linked to it in order for dwarves to control its open or closed state.

=== Roads ===

[[Road]]s are most commonly used to give [[caravan|caravans]] a reliable path to your fortress from the map's edge, though they don't really require one. A paved road is much like a [[floor]] except that it requires fewer raw materials per tile to build. A dirt road requires no materials to build, but deteriorates over time.

=== Grates and Bars ===
[[Grates]] and bars are used to stop creatures for passing through, while still allowing liquids such as water and magma to. Bars are similar to grates, but they are made of metal instead of rock or wood and don't have to be built in a workshop first.

== Trading ==
{{Main|Trading}}

When you want to obtain things not available on your map, and you don't want to just kill people to get them, [[Trading]] is the way to go about it. See the main article for everything you ever wanted to know about legitimately and non-violently obtaining things from other creatures.

== Military and combat ==
{{Main|Military}}
:''See also: [[Military interface]]''

The '''military''' is one of the most important aspects of a successful fortress. Even with many [[trap]]s, [[bridge|drawbridges]] and [[magma|other defenses]], your military will still need to fend off [[goblin]] [[siege]]s, [[megabeast]]s, [[titan]]s, and fiendish [[Giant cave spider|underground]] [[Forgotten beast|beasties]]. Using a combination of [[squads|squad orders]] and [[scheduling]], you can set up an elaborate offensive, defensive, or balanced military structure for your [[equipment|well-equipped]] [[soldier]]s to follow. Turning your dwarves from [[immigration|useless migrants]] into bloodthirsty killing machines never hurts (unless you're the enemy).

Setting up a military is a huge subject in and of itself, so check out the [[Military|main article]] on it and the [[military interface]] guide.

== Hospitals and healthcare ==
{{Main|Healthcare}}

Normally your dwarves do just fine assuming they get enough food and alcohol, but sometimes they get wounded. When this happens they can benefit from an efficient [[Healthcare]] system.

== Burrows ==
{{Main|Burrow}}

'''Burrows''' are optional user-defined areas in your fort where selected dwarves live and work. Dwarves will only use workshops, dig walls, use rooms, etc. in burrows they are assigned to, though dwarves not assigned to any burrow will still use workshops etc. even if they are located in a burrow assigned to some other dwarves.

Burrows are by no means required, but are useful when you want to restrict certain dwarves to certain areas of the map.

== Macros ==
{{Main|Macros and Keymaps}}

'''Macros''' allow recording sequences of keystrokes and "playing" them back into the user interface as desired. Since the game often requires using a lot of repetitive keystrokes, this can sometimes make life much easier. See the main article for full information.

== Reference sheet ==
A quick reference guide on fortress mode in DF can be found [https://www.dropbox.com/sh/8akafeuqfsxth7t/U-zOsO7pNr here.] '''Credit to spongemandan on reddit.com'''

It includes a reference sheet on the military, stone, agriculture and a summary reference sheet.

{{Getting Started}}
{{Category|Fortress mode}}
{{Category|Guides}}
{{Category|Interface}}
[[ru:Dwarf fortress mode]]
[[zh:Fortress mode]]

Dwarf fortress mode

2023-03-24T13:15:30Z

Xjtu-blacksmith: ILL

Mining

2023-03-21T11:25:33Z

Xjtu-blacksmith: /* Making a dwarf a miner */

{{Quality|Unrated}}
{{Labor
| labor = Mining
| skill = * [[Miner]]
| tasks =
* Dig
* [[Construction removal|Remove construction]]
}}
{{av}}
[[File:mining_anim_v50.gif|thumb|189px|right|A designated area being mined.]]'''Mining''' is an essential part of building a fort in ''Dwarf Fortress''. There are several reasons you might want to mine, such as [[exploratory mining|searching]] for various [[stone|stone types]], [[ore]]s and [[gem]]s, or simply to create the basic tunnels and [[room]]s in your fort. Mining refers to either the [[skill]] that performs mining, the [[labor]] associated with it, or simply the task or job of performing said labor. Military dwarves equipped with picks will use mining as their "[[Combat skill|weapon skill]]." Mining through softer materials such as [[sand]] or [[soil]] is much faster than mining through stone.

There are several types of jobs associated with this skill:
* '''Digging''' removes the section of the wall while preserving both the ceiling (which is the floor of the level above) and the floor.
* '''[[Channel]]ing''' removes the section of the wall, the floor, and if possible places a ramp one level below.
* '''[[Ramp]]s''' replaces the section with a ramp, also removing the tile and floor one level above.
* '''[[Stairs]]''' carves out upward and/or downward stairs.
* '''Remove [[Construction]]''' removes a construction, ie. a built wall, stair, floor, etc.
* '''Remove Stairs/Ramp''' removes a dug-out stairs or ramp.

Mining can only be done in pre-existing stone or soil. NOTE: Constructed [[wall]]s, [[stairs]] or [[ramp]]s are not dug and instead must be removed using the 'Remove Construction' option ({{K|m}}, {{K|x}}). This uses the mining skill to be completed. When discovering a unique stone, gem or ore, the game will display an annoucement that looks like the following: 
{{DFtext|You have struck saltpeter!|6:1}}

==Understanding digging==
[[Image:DF2014_Terraform.png|thumb|664px|
Side view of various mining tasks.
 
Gray/black areas represent un-mined rock, cyan/black represents mined-out areas. Solid green represents existing floor "tiles", cyan represents mined-out floor tiles. Up stairs, down stairs, and ramps are red, blue, and mustard (yellow) respectively.
 
In each of the 9 "digging" scenarios, the dwarf miner is shown as having completed the command(s) listed in that figure, moving from left to right. Each individual command is separated by a comma ",". (The "x2" notation indicates that the command is completed twice.) The dwarf has completed those commands in the order they are listed. For example, in the bottom right figure: "Down stairs, up/down stairs, up stairs, mine x2" is five separate commands.
]]
Each layer in the three-dimensional ''Dwarf Fortress'' map consists of two parts: a wall-part, and a floor-part. Mining a tunnel removes the wall-part but leaves the floor-part in place. Channeling removes the floor-part as well, leaving open space above, and if a wall-part exists below, it becomes an upward ramp. Digging an upward ramp removes the wall-part of the designated tile and both parts of the tile above it. Up stairs only modify the wall-part of the designated tile (and are unusable without Down stairs in the tile above), the Down stairs designation will remove the wall-part of the tile (if present) and place a stair connection in the floor-part of the designated tile. Up/down stairs modify both parts of the designated tile (but remain unusable until the tile above/below has the proper stair connection).

== Making a dwarf a miner ==

# Go to the {{K|y}} labor menu, then work details tab
# Select the "Miners" work detail on the left side of the screen
# Find the dwarfs you would like to make a miner, and click the rightmost box, a green check mark should appear
# If you would like this dwarf to ''only'' mine, and ignore all other labors (they will still eat, sleep, take breaks, etc. ) you can toggle the dwarf's "Specialize" button (the hammer and lock icon) to be red.
To start mining, a [[miner]] requires an available [[pick]]. A dwarf's agility and mining skill affect how quickly they mine.

Giving a dwarf the miner work detail will effectively disable the "wood cutter" and "hunter" work details, as their associated labors all involve the usage of different tools.{{verify}}

== Designating the area to be mined ==

# Press {{Menu icon|m}} to bring up the digging orders menu.
# Highlight the requested action by pressing:
#* {{K|m}} for mining
#* {{K|u}} for channeling
#* {{K|r}} for an upward ramp
#* {{K|t}} for stairs, set a start and an end point in a different elevation to determine if it leads upwards or downwards
# (Optional) Set the priority by pressing {{k|n}} to open the advanced options, and clicking a number to set the priority. Tiles with first/lowest numbered priority value will be mined first.
# Draw a rectangle using the mouse. An area should now be highlighted, indicating the area to be mined. The opposite corner can also be placed on a different z-level with {{k|c}}/{{k|e}}, designating areas across z-levels for mining.

==Mineral production (profit!)==
When the wall-part is removed from a stone tile, there is a 25% chance that a single [[stone]] (also known as a boulder) will be left behind. Minerals which are found in [[vein]]s have a 33% chance of leaving ore, and minerals found in [[vein|small clusters]] (or individual tiles) have a 100% chance of leaving a stone or rough gem behind. Finally, any "deep" material (i.e. [[adamantine]] or [[slade]]) has a 100% chance of leaving a usable stone (though the latter is normally undiggable). Mining skill only influences the amount of time it takes to mine each tile; it does not affect drop rate.

Carving a channel down or ramp up needs special care to provide the full 25%/33%/100% mineral production: in the case that both the bottom tile (where the new ramp up is) and the top tile (new open-space above the newly carved ramp) are both dug out together as part of the same designation, there is only a single chance of mineral production, even though two tiles had their wall-part removed, effectively halving the mineral production chance to 12.5%/16.5%/50% in that case. But if special care is taken to ensure the top open-space tile is dug out first before carving the ramp below it, the full chance from both tiles can be achieved.

The [[stoneworker's workshop]] can create four [[block]]s from each boulder, so on average you can create one stone block for each tile of stone mined. Each ore stone also produces 4 metal bars at a [[smelter]], so, on average, you will produce 1⅓ bars of the basic metal* for every tile of ore mined, or 4/ for small clusters of rare ore.

: (* Two ores, [[tetrahedrite]] or [[galena]], have a chance to produce additional bars of [[silver]] as well as producing the 4 bars of their basic metal ([[copper]] and [[lead]], respectively). As a footnote, while [[iron]] ores produce 4 bars of iron, and that is all the metal required for 1 bar of steel, [[steel]] production additionally consumes 1 [[flux]] stone and 1 bar of [[fuel]] per single bar of steel produced.)

When tunnels are dug in [[soil]], nothing is left from the material, there is no soil equivalent of a "[[stone]]" to be further used. The floor-part will remain (if it wasn't channeled), and is suitable for [[farming]], or, if the right kind of soil, for sand or [[clay]] collection.

After pressing {{K|m}} and opening the advanced optio{{k|n}}s menu, you can set the designation type to switch between designating all materials ({{k|v}}), designating just {{k|g}}ems, designating just gems and {{k|o}}res, or designating ore/gem clusters or veins to be mined automatically with {{k|V}}. Switching the designation type to automining will allow you to quickly assign mining tasks to entire veins.

==Training mining==
Dwarves gain mining experience for each tile mined, be it stone, ore, gem, or soil. Soil is mined extremely quickly and is one of the fastest ways to train miners. Since the skill of mining also is used in combat, a dwarf with mining enabled that is carrying a pick will increase their mining skill through combat drills. This process is much faster than learning by digging through stone, but not nearly as fast as learning by digging through soil.

The fastest way to train mining is to first dig out upstairs, then remove the upstairs. Removing upstairs (even rock ones) is extremely quick and still provides mining experience.

==Mining warm and damp stone==
[[File:digging_wet_preview.png|thumb|Wet tiles that should not be dug.]]

When designating any digging operation, warm and damp tiles will flash, indicating magma or water in adjacent tiles. Miners can dig these safely, provided there is an escape route. (''"Safely"'' here implies only the short term survival of the digging dwarf, your fortress may well be flooded as a result, even many levels above the digging level, ''eventually'' killing your dwarf.)

Channeling and ramping designations involve two operations, and your dwarf will be submerged in the fluid when done. Unskilled swimmers can reach an exit ramp out of water if near enough, but magma will certainly cost your miner's life (the flow from either can knock dwarves off ledges, or, naturally, [[flood]] the fortress.)

Wall tiles ''above'' magma will flash "warm", and designations will be cancelled even if an entirely safe tunnel is being dug. This is rather annoying when carving out rooms above the magma sea, although there is a way around it. Designating a channel two levels above the magma will mine out the warm wall immediately above the magma, and the designation won't be cancelled because it's not in the area of the warm stone.

==How to cancel a mining operation==
If you placed a designated area for mining but want to cancel the mining (for example if you approached [[Main:Digging designation canceled|damp stone]]) open the eraser tool with {{k|x}} and select an area you want to cancel.

== Rampless channels ==
To create a channel with no ramps, you have to mine out the area underneath the channel first, or manually designate the ramps created for removal afterwards {{K-|m|x}}. If you wish for these channels to be completely inaccessible from the outside, channel out the access-point (downward staircase). Another (more complicated) way of removing any access to the moat is to replace the dug out ramps with constructed ones and creating a cave-in with constructed floors. Rampless channels are an effective substitute for walls against melee enemies that cannot fly, and they can be dug out far faster than a wall can be built. However, channels offer no defense against archers or dragonbreath.

When digging ramps upwards, watch out for loose stone or other items that might be on the floor above, as falling objects can injure the unfortunate miner.

== See also ==
* [[Map tile]]s – Different types of walled, floor and open spaces.
* [[Caverns]] – Large underground tunnel systems.
* [[Exploratory mining]] – Mining focused on finding valuable [[stone]].
* [[Soil]] – A list of soil types.
* [[Stone]] – A list of different types of stones and ores left behind from mining.
* [[Smoothing]] – Increase fortress value and dwarf happiness by improving the quality of your rough-stone mineshafts.

{{Translation| dwarven = avuz | elvish = cèthutha | goblin = ngogngo | human = bora}}

{{labors}}
[[zh:Mining]]

Mining

2023-03-21T11:25:23Z

Xjtu-blacksmith: /* Making a dwarf a miner */ typo

{{Quality|Unrated}}
{{Labor
| labor = Mining
| skill = * [[Miner]]
| tasks =
* Dig
* [[Construction removal|Remove construction]]
}}
{{av}}
[[File:mining_anim_v50.gif|thumb|189px|right|A designated area being mined.]]'''Mining''' is an essential part of building a fort in ''Dwarf Fortress''. There are several reasons you might want to mine, such as [[exploratory mining|searching]] for various [[stone|stone types]], [[ore]]s and [[gem]]s, or simply to create the basic tunnels and [[room]]s in your fort. Mining refers to either the [[skill]] that performs mining, the [[labor]] associated with it, or simply the task or job of performing said labor. Military dwarves equipped with picks will use mining as their "[[Combat skill|weapon skill]]." Mining through softer materials such as [[sand]] or [[soil]] is much faster than mining through stone.

There are several types of jobs associated with this skill:
* '''Digging''' removes the section of the wall while preserving both the ceiling (which is the floor of the level above) and the floor.
* '''[[Channel]]ing''' removes the section of the wall, the floor, and if possible places a ramp one level below.
* '''[[Ramp]]s''' replaces the section with a ramp, also removing the tile and floor one level above.
* '''[[Stairs]]''' carves out upward and/or downward stairs.
* '''Remove [[Construction]]''' removes a construction, ie. a built wall, stair, floor, etc.
* '''Remove Stairs/Ramp''' removes a dug-out stairs or ramp.

Mining can only be done in pre-existing stone or soil. NOTE: Constructed [[wall]]s, [[stairs]] or [[ramp]]s are not dug and instead must be removed using the 'Remove Construction' option ({{K|m}}, {{K|x}}). This uses the mining skill to be completed. When discovering a unique stone, gem or ore, the game will display an annoucement that looks like the following: 
{{DFtext|You have struck saltpeter!|6:1}}

==Understanding digging==
[[Image:DF2014_Terraform.png|thumb|664px|
Side view of various mining tasks.
 
Gray/black areas represent un-mined rock, cyan/black represents mined-out areas. Solid green represents existing floor "tiles", cyan represents mined-out floor tiles. Up stairs, down stairs, and ramps are red, blue, and mustard (yellow) respectively.
 
In each of the 9 "digging" scenarios, the dwarf miner is shown as having completed the command(s) listed in that figure, moving from left to right. Each individual command is separated by a comma ",". (The "x2" notation indicates that the command is completed twice.) The dwarf has completed those commands in the order they are listed. For example, in the bottom right figure: "Down stairs, up/down stairs, up stairs, mine x2" is five separate commands.
]]
Each layer in the three-dimensional ''Dwarf Fortress'' map consists of two parts: a wall-part, and a floor-part. Mining a tunnel removes the wall-part but leaves the floor-part in place. Channeling removes the floor-part as well, leaving open space above, and if a wall-part exists below, it becomes an upward ramp. Digging an upward ramp removes the wall-part of the designated tile and both parts of the tile above it. Up stairs only modify the wall-part of the designated tile (and are unusable without Down stairs in the tile above), the Down stairs designation will remove the wall-part of the tile (if present) and place a stair connection in the floor-part of the designated tile. Up/down stairs modify both parts of the designated tile (but remain unusable until the tile above/below has the proper stair connection).

== Making a dwarf a miner ==

# Go to the {{K|y}} labor menu, then work details tab
# Select the "Miners" work detail on the left side of the screen
# Find the dwarfs you would like to make a miner, and click the rightmost box, a green check mark should appear
# If you would like this dwarf to ''only'' mine, and ignore all other labors (they will still eat, sleep, take breaks, etc. ) you can toggle the dwarf's "Specialize" button (the hammer and lock icon) to be red.
To start mining, a [[miner]] requires an available [[pick]]. A dwarf's agility and mining skill affect how quickly they mine.

Giving a dwarf the miner work detail will effectively disable the "wood cutter" and "hunter" work details, as their associated labors all involve the usage of different tools.{{verfiy}}

== Designating the area to be mined ==

# Press {{Menu icon|m}} to bring up the digging orders menu.
# Highlight the requested action by pressing:
#* {{K|m}} for mining
#* {{K|u}} for channeling
#* {{K|r}} for an upward ramp
#* {{K|t}} for stairs, set a start and an end point in a different elevation to determine if it leads upwards or downwards
# (Optional) Set the priority by pressing {{k|n}} to open the advanced options, and clicking a number to set the priority. Tiles with first/lowest numbered priority value will be mined first.
# Draw a rectangle using the mouse. An area should now be highlighted, indicating the area to be mined. The opposite corner can also be placed on a different z-level with {{k|c}}/{{k|e}}, designating areas across z-levels for mining.

==Mineral production (profit!)==
When the wall-part is removed from a stone tile, there is a 25% chance that a single [[stone]] (also known as a boulder) will be left behind. Minerals which are found in [[vein]]s have a 33% chance of leaving ore, and minerals found in [[vein|small clusters]] (or individual tiles) have a 100% chance of leaving a stone or rough gem behind. Finally, any "deep" material (i.e. [[adamantine]] or [[slade]]) has a 100% chance of leaving a usable stone (though the latter is normally undiggable). Mining skill only influences the amount of time it takes to mine each tile; it does not affect drop rate.

Carving a channel down or ramp up needs special care to provide the full 25%/33%/100% mineral production: in the case that both the bottom tile (where the new ramp up is) and the top tile (new open-space above the newly carved ramp) are both dug out together as part of the same designation, there is only a single chance of mineral production, even though two tiles had their wall-part removed, effectively halving the mineral production chance to 12.5%/16.5%/50% in that case. But if special care is taken to ensure the top open-space tile is dug out first before carving the ramp below it, the full chance from both tiles can be achieved.

The [[stoneworker's workshop]] can create four [[block]]s from each boulder, so on average you can create one stone block for each tile of stone mined. Each ore stone also produces 4 metal bars at a [[smelter]], so, on average, you will produce 1⅓ bars of the basic metal* for every tile of ore mined, or 4/ for small clusters of rare ore.

: (* Two ores, [[tetrahedrite]] or [[galena]], have a chance to produce additional bars of [[silver]] as well as producing the 4 bars of their basic metal ([[copper]] and [[lead]], respectively). As a footnote, while [[iron]] ores produce 4 bars of iron, and that is all the metal required for 1 bar of steel, [[steel]] production additionally consumes 1 [[flux]] stone and 1 bar of [[fuel]] per single bar of steel produced.)

When tunnels are dug in [[soil]], nothing is left from the material, there is no soil equivalent of a "[[stone]]" to be further used. The floor-part will remain (if it wasn't channeled), and is suitable for [[farming]], or, if the right kind of soil, for sand or [[clay]] collection.

After pressing {{K|m}} and opening the advanced optio{{k|n}}s menu, you can set the designation type to switch between designating all materials ({{k|v}}), designating just {{k|g}}ems, designating just gems and {{k|o}}res, or designating ore/gem clusters or veins to be mined automatically with {{k|V}}. Switching the designation type to automining will allow you to quickly assign mining tasks to entire veins.

==Training mining==
Dwarves gain mining experience for each tile mined, be it stone, ore, gem, or soil. Soil is mined extremely quickly and is one of the fastest ways to train miners. Since the skill of mining also is used in combat, a dwarf with mining enabled that is carrying a pick will increase their mining skill through combat drills. This process is much faster than learning by digging through stone, but not nearly as fast as learning by digging through soil.

The fastest way to train mining is to first dig out upstairs, then remove the upstairs. Removing upstairs (even rock ones) is extremely quick and still provides mining experience.

==Mining warm and damp stone==
[[File:digging_wet_preview.png|thumb|Wet tiles that should not be dug.]]

When designating any digging operation, warm and damp tiles will flash, indicating magma or water in adjacent tiles. Miners can dig these safely, provided there is an escape route. (''"Safely"'' here implies only the short term survival of the digging dwarf, your fortress may well be flooded as a result, even many levels above the digging level, ''eventually'' killing your dwarf.)

Channeling and ramping designations involve two operations, and your dwarf will be submerged in the fluid when done. Unskilled swimmers can reach an exit ramp out of water if near enough, but magma will certainly cost your miner's life (the flow from either can knock dwarves off ledges, or, naturally, [[flood]] the fortress.)

Wall tiles ''above'' magma will flash "warm", and designations will be cancelled even if an entirely safe tunnel is being dug. This is rather annoying when carving out rooms above the magma sea, although there is a way around it. Designating a channel two levels above the magma will mine out the warm wall immediately above the magma, and the designation won't be cancelled because it's not in the area of the warm stone.

==How to cancel a mining operation==
If you placed a designated area for mining but want to cancel the mining (for example if you approached [[Main:Digging designation canceled|damp stone]]) open the eraser tool with {{k|x}} and select an area you want to cancel.

== Rampless channels ==
To create a channel with no ramps, you have to mine out the area underneath the channel first, or manually designate the ramps created for removal afterwards {{K-|m|x}}. If you wish for these channels to be completely inaccessible from the outside, channel out the access-point (downward staircase). Another (more complicated) way of removing any access to the moat is to replace the dug out ramps with constructed ones and creating a cave-in with constructed floors. Rampless channels are an effective substitute for walls against melee enemies that cannot fly, and they can be dug out far faster than a wall can be built. However, channels offer no defense against archers or dragonbreath.

When digging ramps upwards, watch out for loose stone or other items that might be on the floor above, as falling objects can injure the unfortunate miner.

== See also ==
* [[Map tile]]s – Different types of walled, floor and open spaces.
* [[Caverns]] – Large underground tunnel systems.
* [[Exploratory mining]] – Mining focused on finding valuable [[stone]].
* [[Soil]] – A list of soil types.
* [[Stone]] – A list of different types of stones and ores left behind from mining.
* [[Smoothing]] – Increase fortress value and dwarf happiness by improving the quality of your rough-stone mineshafts.

{{Translation| dwarven = avuz | elvish = cèthutha | goblin = ngogngo | human = bora}}

{{labors}}
[[zh:Mining]]

Minecart

2023-03-12T01:29:43Z

Xjtu-blacksmith: /* Track Stops */ update build command

{{migrated article}}
{{Quality|Unrated}}
{{av}}

[[File:minecart_sprite_preview.png|right]]A '''minecart''' is a [[tool]] intended for [[hauling]]. It can be made of [[wood]] at a [[carpenter's workshop]] or 2 bars of [[metal]] at a [[metalsmith's forge]] (using the [[Metal crafter|metalcrafting]] labor.) Minecarts store up to five times as many items as [[wheelbarrow]]s and are quite a bit faster than dwarves hauling objects by hand, but have the disadvantages of requiring a dedicated track network, a complex route planning phase, and the possibility of dwarves [[Fun|blundering into the path of carts filled with lead ore]]. Tracks may be carved into stone, or [[Construction|constructed]]; the latter allows above-ground routes, but these are more difficult to set up due to their additional [[building material|material requirements]].

Just like wheelbarrows, minecarts are considered [[item]]s and are stored in a [[furniture]] [[stockpile]]. Despite their five-times-greater capacity, they are only 33% larger than wheelbarrows (minecarts have a size of 4000) and are identical in base [[item value|value]] when made from the same [[material]] (the value may differ due to the [[item quality]]). [[thief|Thieves]] or even mischievous animals can steal minecarts, even when they are moving on a track.{{cite forum|109460/3289070}} However, minecarts moving fast enough or being ridden cannot be stolen.

Although most of the utility of minecarts is in [[fortress mode]], an [[adventure mode|adventurer]] can also ride in a minecart. Adventurers can also pick up and relocate minecarts.

The invention of minecarts revolutionized the [[minecart logic|Science of Dwarfputing]] by enabling smaller, faster logic systems to be built.

== Basic Minecart Usage ==
[[File:Leitnagel Hund.png|thumb|Minecarts]]Minecarts can be used to swiftly transport dwarves, [[flow|fluids]], and/or large amounts of items, but before you have a functional minecart, there are several preconditions that need to be met. First of all, you need an actual minecart, constructed either in a [[carpenter's workshop]] or [[metalsmith's forge]]. For the minecart to be able to move, you also need to carve (with {{Menu icon|v|t}}) or construct (with {{Menu icon|b|n|k}}) a track, which could be as simple as a straight line. Finally, you need to construct stops on your track (with {{Menu icon|b|n|K}}) where the minecart will start and stop.

After you have created the stops and assigned a cart to the track, you must create logic routes connecting several stops and designate starting conditions for each stop. This is done with the {{Menu icon|H}} hauling key. The most basic conditions are how the cart's movement is initiated and in which direction the cart should start moving. Carts can be either pushed (a dwarf stands at a stop and gives the cart a single push) or guided (a dwarf continually pushes the cart forward, guiding it along the track). The [[hauling]] [[labor]] required for pushing and guiding carts is called "Push/Haul Vehicles" and is turned on by default.

To control which items are to be transported, you can add conditions specifying: (1) which kind of items are to be loaded and unloaded, (2) stockpile links to define which stockpile(s) the items should be un/loaded to and from.

===Capacity and weights ===
Minecarts have a [[Size|size capacity]] of 50,000 – five times the capacity of [[wheelbarrow]]s.

'''Examples of the capacity of one cart'''
{| class="wikitable"
|-
! Item
! Amount
|-
| [[stone]]
| 5
|-
| [[wood|log]]
| 10
|-
| [[block]]/[[bar]]
| 83
|-
| minecarts
| 12
|-
| [[Kitchen|prepared meals]]
| 500
|-
| [[Trap_component#Spiked_ball|spiked balls]]
| 500
|-
| [[Sand]] [[bags]]
| 500
|-
| [[Weapon#Native_weapons|mace]]
| 625
|-
| [[Weapon#Native_weapons|spears]]
| 1250
|-
| [[cloth]]
| 2500
|}

The weight of the loaded minecart does not affect the initial velocity received from pushing or launching from a roller.{{bug|6296}} However, the load of a minecart ''does'' affect whether a [[pressure plate]] triggers or not, based on the pressure plate's setting.

'''Weights of different carts'''

{| class="wikitable"
|-
! Type of cart
! Empty cart
! Fully loaded (items)
|-
| oaken minecart
| 28Γ
| 378Γ (10 oak logs)
|-
| iron minecart
| 314Γ
| 1698Γ (83 marble blocks)
|-
|-
| copper minecart
| 357Γ
| 1682Γ (10 obsidian boulders)
|-
| platinum minecart
| 856Γ
| 10482Γ (83 gold bars)
|}

The weight of a minecart is one twenty-fifth (1/25) the [[density]] of its material in Urists. Because pressure plates can be set to trigger at intervals of 50 Urists, minecarts with weights just under a multiple of 50 are ideal for switching based on whether they're full or empty. The best minecart materials for full/empty switching are as follows:

{| class="wikitable sortable"
|-
! Material !! Minecart weight !! Content weight required to trigger !! Banana roasts required to trigger (for scale)
|-
| [[Glumprong]] || 48 || 2 || 4
|-
| [[Electrum]] || 596 || 4 || 7
|-
| [[Nickel silver]] || 346 || 4 || 7
|-
| [[Brass]] || 342 || 8 || 14
|-
| [[Bismuth]] ([[Strange mood|moods]] only) || 391 || 9 || 15
|-
| [[Fine pewter]] || 291 || 9 || 15
|-
| [[Lay pewter]] || 291 || 9 || 15
|-
| [[Tin]] || 291 || 9 || 15
|-
| [[Trifle pewter]] || 291 || 9 || 15
|}

{{anchor|Tracks}}

=== Creating tracks ===
Minecart tracks are made up of contiguous track, tracked ramp, or bridge tiles. Track tiles and tracked ramp tiles have a direction or series of directions associated with them. These directions dictate which directions a minecart on a given tile may move from that tile. For example, a Track NE (northeast) tile allows a minecart on it to move either north or east from its present position. Therefore, if you want your minecart to move east along a straight piece of track, then return west using that same track, you would need to use EW tracks so that the cart could travel east initially, then return west over the same track. Excluding designs in which the cart will "jump" tracks via a drop or other ramp, tracks must be valid end to end to work for most looped or straight-track applications. A single east only track tile in your line of east-west tracks will cause any route using the track to fail the moment it tries to go the wrong way over that tile. Minecart tracks can be built in two ways: Engraved/carved or constructed. A given minecart track need not use engraved or constructed elements exclusively, as the two methods can be used interchangeably depending on the needs of a given section of track. The way the tracks are built is slightly different between the two, as explained below.

====Simple tracks====

'''Carved'''

A single-tile wide strip of natural stone can be designated to be [[Engraver|carved]] (with {{menu icon|v|t}}), which will create a straight two-way track. The creation of corners, crossings, and T-junctions is as simple as designating another strip of track that overlaps an existent or newly designated track. Engraved tracks are removed by [[smoothing]] the rock they're on, which results in a smooth floor (that can be re-engraved if necessary), or by building a [[floor]] on top and subsequently removing it. Dwarves can carve corner tracks in one pass by designating the track carving twice and canceling unwanted carvings (with {{K|d}} {{K|x}}). Tracks can be engraved in any natural floor tile, rough, smooth and even over engravings, providing an easy method to remove low-quality or undesired floor engravings. Once a track has been engraved, it's important to check the track directions for each tile in the route carefully to make sure no mistakes were made by yourself or the game's track engraving logic.

'''Constructed'''

Tracks can also be built as regular [[construction]]s (through {{menu icon|b|n|k}}. This method is resource-expensive, since each track tile requires one stone, [[bar]], or [[block]] for construction, and time-consuming, since you can't designate strips longer than 10 tiles at a time. Corners, crossings, T-junctions, and ramps also have to be designated individually. However, it is usually the only way to build tracks above ground or on soil (barring the [[Obsidian farming|creation of obsidian]]). Constructed tracks are designated for removal like any regular construction; be aware that removing track ramps built on top of natural ones will also remove the original ramp, leaving a flat floor.

====Ramps====

'''Carved'''

The carving of natural ramps is a little more confusing: to carve a two-way track on a ramp (natural only, does not work on constructed ramps), you must designate the track '''starting on the ramp and one square beyond''' in the direction you want the track to go. For the side of the ramp square you want to head upward, there '''must''' be either a natural or constructed wall in the square next to it, otherwise the game assumes you are trying to carve it on the same level – this can result in the track being carved underneath a door or other object. If you have accidentally done this, you can correct it by smoothing the ramp and constructing a single square of wall next to it, then re-carving the ramp correctly, however, the wall must stay there permanently — removing it will disconnect the track.

'''Constructed'''

The track and ramp must be constructed together as a Track/Ramp from the construct track menu ({{K|b}} {{K|C}} {{K|T}}). When constructing track ramps, the stated direction should be the same as the connected tracks. For example, a track going up from West to East would require, starting from the West, a Track (EW), a Track/Ramp (EW) and a Wall behind the ramp, underneath the section of track above it. Incorrectly placed ramps result in minecarts ignoring the ramp and crashing into the supporting wall. They will not, however, display as unusable as when the supporting wall is missing.

'''Examples of ramps'''

A simple ramp would look like this:
{{diagram|spaces=yes|\
z +0 z +1
░░░░ ░░░░
═▲o ░▼═
░░░░ ░░░░
o : wall
}}

Carving track corners into ramps is rather unintuitive and complicated. Since engraving tracks always requires two tiles to connect in a straight line as input, you have to give two separate designations for a single job: a track bit from the ramp tile to the "below" direction and another one to the wall of the "upward" direction. If you wanted to change direction on a ramp from east to north:
{{diagram|spaces=yes|\
z +0 z +1
░░░░░ ░░░░░
░░░░░ ══╗░░
══▲░░ ░░▼░░
░░░░░ ░░░░░
}}

you would need to connect the ramp on z +0 both to the west and to the north by issuing two "carve track" commands, one selecting the ramp and the track tile to the west, and another connecting the ramp tile with the wall to the north. An engraver would then carve a NW track corner into the ramp, allowing carts to pass the corner correctly both going up and down. Such track corners are perfectly serviceable for guided carts, but moving down a route of several of them by pushed or ridden cart is problematic - ramps on corners behave very counter-intuitively, resulting in loss of speed when going down and diagonal movement when going up.

Moving to and from ramps (or between ramps "pointing" in different directions) causes some non-trivial adjustments to speed and even moving along the tiles at a fixed speed ''unrelated to the entry/exit velocity values'', because transitions to/from ramps are processed differently and are not to be "skipped". This affects compact track/ramp combinations (such as e.g. a simple 2x2 ramp spiral) most, and combined with bouncing often makes them work not in the way one could expect. {{cite forum|144328/5705102}}

=== Hauling route ===
A hauling route is a list of directions describing how and under what conditions a minecart will move. The proper setting up of routes is essential for a working rail system. Routes, stops, departure conditions and stockpile links are managed from the {{k|h}}auling menu.

==== Route ====
A route defines the path a minecart will take along a track, as well as under what conditions it will move or stop moving. A route is made up of stops. Stops are precisely what they sound like, a position on the track at which you want a minecart to stop. A minecart track might use as little as a single stop for a looped track, which will serve as both a starting and stopping point for the cart, or it could contain many stops, perhaps to load supplies or wait for a bridge to be manually lowered, before reaching its destination or returning to its starting point. It is important to note that you only need to place stops on a route where you actually want the cart to stop and wait for some action to occur. They are not needed to help navigate the cart along the track beyond telling it where on the track to stop.

New routes are created with the {{k|h}}auling key. Existing ones can be removed (without confirmation) with the {{k|x}} key, and also {{k|n}}icknamed. Before operating, the route must have a {{k|v}}ehicle assigned to it (this can be done with either the route or a stop selected). Assigning a full minecart to a route may result in a slow hauling job if the contents are heavy.

==== Stops ====
Stops are the individual waypoints that make up a hauling route. A given stop consists of the location of a tile, as well as conditions describing when, where, and how a cart should be moved after being stopped at that tile. Stops can be created from within the {{k|h}}auling menu, by placing the cursor over a tile and hitting {{k|s}} while highlighting the route (or a stop within) you've already designated. A minecart will begin its route at the first stop created, and continue through each subsequent stop, being guided, pushed, or ridden from each stop to the next depending on the conditions specified. In many basic minecart applications, the cart will end up at the same stop it began at, though this is not always the case. It is important to note that hauling stop order is enforced, even if there is no track. A dwarf will drag the cart overland back to a skipped stop in the route's list if your tracks bypass it somehow, including if the minecart does not stop on the stop after it is pushed/ridden.

Once a stop has been placed, it is given a default set of conditions under which to move the minecart if it is stopped there. Each new stop gets the same default conditions regardless of the track it is placed upon (e.g. guide the cart to the north). For this reason new stops might get marked by yellow exclamation marks ({{DFtext|!|#ff0}}) due to invalid directions. One important thing to note is that as you place additional stops, the display will show paths between the stops you have defined. However, this is '''not''' necessarily the actual route the minecart will take once the route is in operation. For example, if a route were defined with two stops at opposite ends of a track with many twists and turns, a line will be drawn directly between those stops to show the order in which they will be visited. These route lines may crisscross all over the tracks, but so long as the track is valid end to end, the cart will follow the track from one stop to the next, even across twists, turns, and z-level changes. Route stops, which are the steps that make up a route, should not be confused with physical Track Stops, described below.

===== Stockpile links =====
By placing the cursor on top of a stockpile and using {{k|s}}, you can create stockpile links while defining a hauling stop. Links can also be redefined by selecting them, placing the cursor over a different stockpile, and pressing {{k|p}}. The cart will then be filled by items present in its various linked stockpiles in preference to other items. Note that bins should be used with caution in stockpiles that are linked to minecarts. Bins cause problems when used with the "Desired Items" list in a stop's conditions. For example, if a minecart is set to accept only granite blocks, and to depart north when it is 100% full of granite blocks, it will not depart if any of those granite blocks are in bins, even if bins are also included in the desired items list. Two solutions to this problem exist as of v0.40.24. First, bins can be disallowed in stockpiles that are linked to stops. Alternatively, bins '''can''' be used in conjunction with minecarts provided that the minecart's departure conditions use only "any items" instead of "desired items." This option can be toggled in the advanced conditions menu for a stop, accessible via the {{key|C|}} key. The cart's contents can still be controlled by specifying what items are allowed in the linked stockpile.

===== Departure condition =====
Departure conditions involve setting conditions in which the minecart will leave on the route. Each condition includes:
# A departure mode (Guide, Ride or Push).
# An initial departure direction (NSEW). Note that this defines the initial direction of movement only. Even if a track includes many turns, as long as the initial movement direction is valid the cart will follow the minecart track thereafter.
# A timer, before which the departure condition cannot be met.
# Conditions on the amount of items in the cart.
Departure conditions are created with the {{k|n}} key. A new departure condition will read: "guide north immediately when empty of desired items". This condition can be changed between basic presets with {{k|c}}. "Advanced" mode ({{k|C}}) allows for more precise control over departure conditions: fine tuning the percentage from 0 to 100 in 25% steps ({{k|f}} and {{k|F}}), switching it being either the maximum or the minimum amount of items for the condition to be met ({{k|m}}), and whether the cart accepts all or only a specific set of items ({{k|l}}). Common to both screens are the departure mode ({{k|p}}, Push, Ride or Guide), {{k|d}}irection, and timer ({{k|t}} and {{k|T}}) options.

To have a cart only carry a specific set of items, the stop can be set to only carry "desired" items, opening the selection screen with the {{k|Enter}} key while having said stop condition selected, and toggling as desired, or it can simply be linked to a stockpile and set to depart once it is full of items from its linked stockpiles, regardless of type.

=== Track Stops ===
A Track Stop, not to be confused with a route stop, is an optional, single-tile construction which serves two purposes. First, it can be used to cancel a cart's momentum in order to slow or stop it as it passes over the Track Stop. This might be necessary if a cart were pushed down a series of ramps to its destination. Second, a Track Stop can cause a cart to automatically dump its contents as it passes over the Track Stop. Track Stops are constructed via {{menu icon|b|n|K}}, and must be constructed atop an existing piece of track. If a Track Stop has been set to automatically dump a cart's contents, the cart will dump its contents in the direction indicated when it passes over the Track Stop. Depending on the friction settings chosen for the Track Stop, the cart might then stop after dumping, or it might continue on its route to another destination.

Track Stops are not mandatory; in fact, their main use is in automated rail systems. However, even in basic rail systems it can be useful to set a Track Stop to dump items: this saves time that dwarves would otherwise spend in removing items from the cart, time that is better spent driving the cart back to where it's needed. Dumping will occur even with a guided cart. '''Take care not to set Track Stops at a loading site to dump their contents''', or dwarves will never be able to fill the cart. It will dump any contents the moment they are loaded.

Counter-intuitive to their construction method, Track Stops are considered [[building]]s and must be removed by {{k|q}} {{k|x}}.
* See [[#More_on_Track_stop |More on Track Stops]]

=== Step-by-step tutorial ===

Let's construct a simple minecart route. This route will move stone blocks from an input stockpile to an output stockpile. We'll begin by creating the stockpiles:

[[File:minecart-example-1-v50.03.png|200px|Stockpiles designated.]]

The input stockpile is on the left; the output stockpile is on the right. We'll be moving blocks from left to right. Disable bins in both stockpiles, and set the input stockpile to accept only from links. Then make the stockpile take from the mason's workshop where the blocks are being produced.

Next, carve the track:

[[File:minecart-example-2-v50.03.png|200px|Track carving designation.]]

Note that the ends of the designation are uniquely shaped; this is automatic, and not anything you need to control. Now, wait for your engravers to come along and carve the track into the stone. (Your haulers will probably also fill up the input stockpile while you wait.)

In addition, while we're waiting for that to happen, we'll build an iron minecart in the forge.

[[File:minecart-example-3-v50.03.png|200px|Track carved.]]

When the track has been carved, it will look like the above (the track will be solid instead of flashing). Now, order a track stop to be constructed (Under "Constructions") next to the output stockpile:

{|
| [[File:minecart-example-4-v50.03.png|200px|Track stop designation.]]
| [[File:minecart-example-5-v50.03.png|200px|Select dumping direction.]]
|}

You must select the dumping direction ''before'' placing the track stop. We want our blocks to be dumped into the output stockpile east of the track stop. Then wait for a mechanic to come along and build the track stop.

[[File:minecart-example-6-v50.03.png|200px|Track stop constructed.]]

Now we'll define the actual ''route''. This is done in the {{k|H}}auling menu. Press 'Add New Route' to begin defining a route. Select 'Add a stop' then click the track next to the input stockpile:

{|
| [[File:minecart-example-7-v50.03.png|200px|Route definition, in progress.]]
| [[File:minecart-example-8-v50.03.png|400px|Route definition, in progress.]]
|}

Select 'Add a stop' again then click the stop next to the output stockpile define the second stop:

{|
| [[File:minecart-example-9-v50.03.png|200px|Stop 2 designation.]]
| [[File:minecart-example-10-v50.03.png|400px|Route definition, two stops.]]
|}

At this point, the route has been positioned, but they haven't been ''defined'' yet.

Click the Minecart icon for the route (not the stop) and assign a minecart to the route.

Select the minecart icon for the first stop to select what items will be hauled to the minecart. By default no items will be hauled to the minecart. As we've set the input stockpile to only take blocks from the workshop, you can either set to to accept blocks, or set it to accept all items.

Click the stockpile icon for the first stop, select the "take from" icon (middle button) and select the input stockpile.

[[File:minecart-example-11-v50.03.png|350px|Set the stockpile.]]

Select the Conditions button ('''<>=≠''') for the first stop and check out the defaults. For the first stop, these are largely fine however you should change the direction button for all the conditions so the minecart goes the correct direction when it's ready.

[[File:minecart-example-11.1-v50.03.png|350px|Set the direction.]]

Select Conditions for the second stop. These need to be changed so the minecart is returned to the start immediately. Erase the bottom two conditions, change the direction to point back to the stop, and then finally click the '''>=''' button so it changes to '''<='''. This will make it so the cart is returned regardless of how full it is (which is good, as it'll always be empty!)

[[File:minecart-example-11.2-v50.03.png|350px|Fix the conditions for the second stop.]]

Once the minecart is in place, dwarves should fill it with blocks from the input stockpile, which will in turn be filled with blocks from the workshop where your mason has been toiling dutifully. When the minecart is full, the blocks will be dumped into the 1x1 stockpile on the right. Automatic quantum dumping!

If the route has any issues, you'll see a red ! on the minecart in the route screen. Be aware that this appears initially until the minecart is put in place. If your route is correctly set up, you will be dwarfs carry items to the cart and the percentage will change on the route screen.

{|
| [[File:minecart-example-12-v50.03.png|frame|Route with an issue.]]
| [[File:minecart-example-13-v50.03.png|frame|Cart correctly getting filled up.]]
|}

=== Troubleshooting ===

Because of the complexity of the system, all but the most careful and experienced minecart users will encounter issues. Most route issues can be diagnosed and fixed from the {{k|H}}auling menu.

'''Symptom:''' {{DFtext|! Set dir/connect track|6:1}} message appears to the right of one or more stops

:;Possible Causes:
:* Game cannot find a path for ''guiding'' the cart without carrying. The game checks for haul route validity assuming the cart will be guided. This warning will be shown when the path crosses impassable tiles, requires a dwarf to carry the cart, or is not fully guidable.
:** If your cart path relies upon advanced tricks like deliberate falling into pits or ignoring floor types, even a path designed entirely as you intended will still trigger the yellow warning. If the route is working as intended, you can safely ignore this warning.
:* Invalid departure direction in one or more conditions for the stop. Edit the stop using {{k|Enter}} and press{{k|d}} until it is pointing in a valid direction.
:* Track stop built on trackless tile. Track stops must be built on tiles where tracks already exist to be usable.
:* Discontinuous track. If the route indicator seems to draw between your first and last stop, this is the cause. Make sure destinations are linked by track to both directions, and that there are no sneaky gaps in the tracks.
:** ''Ramps''' are notorious for their finicky use. It is recommended to check every ramp to confirm no unintended one-way ramps remain.
:** To carve a two-way track on a (natural) ramp, you must designate the ramp ''and one square beyond'' in the direction you want the track to go.
:** Ramps '''must''' have a solid wall on the side opposite to the track ("behind" the ramp), or they will neither work nor be marked as "unusable". The wall can be natural or constructed.
:* Discrepancies in desired/kept item configurations.

'''Symptom:''' The status '''0% V''' always appears to the right of one stop.

:;Possible Causes:
:* Stop not set to take from a stockpile. Edit the Stop using {{k|Enter}} and make sure you see a message like "Take from Stockpile #1".
:* Take conditions and stockpile contents do not overlap.
:* Track stop is set to dump. A track stop set to dump cannot be filled. You must either set the stop to a time-based departure or deconstruct the track stop and rebuild it without dumping. (Alternatively, with [[DFHack]] you can modify "Dump on arrival" to "No" using the {{key|q}} menu without rebuilding the stop.)
:* Minecart itself is designated to be dumped (such as when using mass-dump).

'''Symptom:''' Dwarves fill the minecart properly, but will not move it thereafter.

:;Possible Causes:
:* Minecart contains items not listed as desired on its current stop. Check minecart contents using the {{key|k}} and {{key|z}} keys and ensure that all items in the cart are desired items.
:* Minecart contain desired items ''in bins''. Minecarts seem to have problems realizing that they are in fact full of desired items if some of those items are in bins, even if bins are also among the desired items for that stop. '''This cannot be solved by adding the appropriate bins to the stop's desired items.''' Either disallow bins in stockpiles you intend to load minecarts from, or set the departure conditions to rely only on percentage of total load rather than percentage of desired items using the advanced conditions menu ({{key|C}} key).

'''Symptom:''' Dwarves repeatedly attempt to load the minecart, but no items are ever loaded into it.

:;Possible Causes:
:* Track Stop set to dump used as a loading site. Every time a dwarf places an item into a cart resting on such a track stop, the item will be immediately dumped, causing unlimited, useless cart loading jobs. Autodumping Track Stops should never be used at a loading site.

'''Symptom:''' A dwarf picks up the minecart and carries it to its destination.
:* See [[#Quirks|Quirks]]

=== Danger ===
Minecarts are not without <strike>danger</strike> [[fun]]. Although designating a track automatically sets the [[traffic]] designation to low, dwarves ''may'' still walk on them, and [[creature]]s ignore traffic designations altogether. If an unlucky dwarf or creature fails to [[dodger|dodge]] a minecart, they can be injured. Most of this danger can be avoided by setting the minecart {{k|h}}auling commands to guide instead of push or ride (dwarves guiding minecarts will ignore traffic restrictions), as well as by [[pasture|pasturing]] domestic animals and preventing the access of other creatures to the tracks. Note that removing the track doesn't reset that tile back to normal traffic priority, so you may wish to manually clean up traffic designation afterward. Also note that bridges that are used as tracks don't have their traffic priority changed automatically (since they're just normal bridges), which could cause dwarves to pathfind normally through dangerous minecart entrances in your fort's walls if you're not careful.

The only <s>fool</s>''dwarf''-proof method is to make the tracks inaccessible. There are several ways to create a track which works for minecarts but doesn't allow creature-traversal; the simplest is perhaps building a [[statue]] on the tracks. Other options include adding single-tile holes (minecarts moving at reasonable speed will jump the gap), vertical drops, minecart-triggered doors, small pools of liquid (4/7 water or 2/7 magma), and hostile creatures overlooking the tracks. For safety, both ends of the track should be isolated, making the dangerous center sections completely inaccessible (though maintenance access can be provided by a locked door).

Danger does not always involve living victims: careless route designation can also result in minecarts careening off tracks or colliding with each other. If this occurs, the [[item]]s may be scattered; this can cause even more hauling jobs than the minecart aimed to eliminate. Even <s>better</s> worse, scattered items, especially [[weapon]]s, can injure passing [[dwarf|dwarves]] or other [[creature]]s; in the words of Toady One the Great, "Accidental grapeshotting of the dining room should be possible now."

Of course, the danger of using minecarts means they can also be [[Trap_design#Minecarts|used as weapons]] by imaginative players.

== Advanced usage and automation ==
Minecart-specific effects are implemented via track stops, rollers and [[pressure plate]]s with "track" condition set. Since all three are considered [[building]]s, they can't be built on the same square (however convenient track stop + pressure plate would be) nor a simple ramp, and are removed by {{k|q}} {{k|x}}.

=== More on Track stop ===
Track stops are constructions that allow further automation of minecart systems via adjustable features such as braking by friction and automatic dumping of contents. They can be built from logs, bars and blocks through {{K|b}} {{K|C}} {{K|S}}; friction amount, dumping toggle and dumping direction must be set '''before''' construction, and these settings can be neither changed nor seen thereafter*; however, track stops can be linked to [[pressure plate]]s or [[lever]]s to toggle friction and dumping On or Off (trigger state is inverted: switch On = track stop Off). In thoughts screen, dwarves will admire track stops as traps.

*Note: As of v0.47.05, the friction and direction settings '''can''' be adjusted after the track stop has been constructed. The stop can be {{K|q}}ueried to show the settings as they were set prior to construction, and two options will appear that allow the settings to be changed. The friction amount can be decreased or increased by pressing {{K|a}} or {{K|s}} respectively, cycling from "Lowest" to "Highest". The direction to dump can be toggled through the four cardinal points by pressing {{K|d}} until the desired direction is selected.

If a [[stockpile]] is placed on the tile that a track stop is set to dump to, it can act as a [[Exploit#Quantum_stockpiles|quantum stockpile]] and any items dumped from a minecart that match the storage settings of the stockpile will remain there and accumulate. Normally track stops are built on top of existing track to operate on moving minecarts, but they can also be used without tracks to create [[Quantum_stockpile#The_Minecart_Stop|automatic quantum stockpiles]] (see also [[#Step-by-step_tutorial|step-by-step tutorial]]). It is not always desirable to collect ALL of certain items into one quantum stockpile, such as when distributing a material to multiple separate industries. You can link your quantum stockpile to various other stockpiles, ensuring that your dwarves will keep them supplied as necessary. Because quantum stockpiles never fill up like regular stockpiles, it may be a good idea to add a switch to turn them off.

Items dumped from a minecart at a track stop (or dumped by any other means) into open space fall through z-levels until they land on a solid surface. Items falling onto a designated [[stockpile]] will automatically be considered part of that stockpile, even if the stockpile is set to disallow those items (they will, however, be automatically moved to a more appropriate stockpile, if available). Items falling on top of a minecart will '''not''' fall "inside" the minecart. Use with caution; dwarves have fragile skulls.{{bug|5945}}

=== Automated propulsion ===
==== Roller ====
{{Main|Roller}}

A '''roller''' is a [[power]]ed [[machine component]] for the automated propulsion of minecarts. They are built over the top of existing tracks with {{K|b|M|r}}, requiring a [[mechanic]], ''(length/4)+1'' [[mechanism]]s and a [[rope]]. Rollers may also be placed directly on ramps to help pull carts up Z levels. Rollers are very useful to maintain a cart's momentum along long routes, to get them to climb Z-levels without dwarfpower involved, and to get them to reach speeds unattainable by guiding dwarves. These devices are variable-length (1-10), variable-direction and variable-speed ([[Minecart#Numbers_behind_the_scene|see below]]), all traits that can be set at construction time; a roller uses two units of power per tile it is long.

Single-tile rollers transfer power in all four cardinal directions, while other rollers generally only transfer power perpendicular to their activity direction. Longer rollers can also transfer power along their activity direction if built in the correct order, although this can be hard to accomplish and is easily broken. Rollers cannot be powered from above.

Rollers have great acceleration and capped speed. Carts going faster than the roller are unaffected. If a cart moves across an active roller in the direction the roller works and moves slower than the roller's specified speed, the cart will be set to the roller's speed. A cart going against a roller's movement direction will be sent back the way it came (once again at the roller's speed), unless it was moving extremely fast: speed increment of 100000 allows to reverse carts from the full "highest" (50000) speed roller to full "highest" speed back, but ramps can accelerate a cart beyond this. {{cite forum|144328/5702453}}
A cart crossing over a roller perpendicular to its current movement direction will gain the roller's amount of speed in the perpendicular direction without directly changing its forward motion. Without an adjacent wall to constrict its movement, this will typically send a cart off the rails on a diagonal path, completely unable to follow any tracks until it collides with a wall or is otherwise brought to rest. However, if the roller is placed over a track turn and pushes ''from'' the direction of that turn's track, the turn affects carts ''after'' the roller, so they will be forced into the turn rather than derailed in a diagonal direction. {{cite forum|144328/5702453}}

{{diagram|spaces=yes|\
tracks: full:
║ ║
═╗═ ═╢═
║ ║

╢ : roller pushing from W to E
}}
If the roller is powered, carts from ''all'' directions (unless too fast) exit S, because speed imparted by the roller forces carts toward E and ''then'' into the turn.
If not powered, carts from W and N exit S, carts from E and S exit W. Carts above derail speed will ignore the turn, of course.

{{diagram|spaces=yes|\
║ ║
═╗═ ═╟═
║ ║

╟ : Roller pushing from E to W
}}
Carts from the E or W: exit W.
Carts from N: derailed diagonally, exit SW.
Carts from S: derailed diagonally, exit NW.

Rollers affects carts on a track - if placed on a floor or ramp without any tracks, they are ignored. Depowered rollers are also ignored, friction is determined by the tiles underneath.

Because of their one-way nature, rollers are unsuitable for most two-way minecart tracks (unless you set gears toggling roller A->B off while toggling A<-B rollers on). However, a minecart set to be ''guided'' is not affected by rollers at all{{cite forum|109460/3286235}} — this allows a one-way track to be used in both directions. In addition, unpowered rollers do not affect minecarts.

Care must be taken in [[glacier]]s and other extremely cold [[biome]]s, since rollers (and the machinery used to power them) will not operate when constructed on natural [[ice]] floors.

==== Impulse ramps ====
Carts can be given momentum without rollers or changing z-level by exploiting a design oversight in a phenomenon called "impulse ramps". A track ramp which has at least one wall/fortification and exactly one other connection will ''always'' accelerate a cart towards the other connection, no matter where the cart enters the tile from. This means carts can be accelerated even if the cart doesn't actually change z-level at all; ramps don't actually impart any downward velocity even when making cart descend. If a track ramp faces three directions such as ╩, then two of those directions need to be facing walls for the cart to be accelerated towards the remaining direction.

Example of straight impulse acceleration:

{{diagram|spaces=yes|\
▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒
═▲▲▲▲▲▲▲▲▲▲═ ═╚╚╚╚╚╚╚╚╚╚═
▒ : Wall
═ : Normal track
▲/╚ : N/E Track/Ramp
}}

If a cart enters from the left, it will speed up on every track/ramp and exit to the right going very very fast—more than one tile every step. If it enters from the right, then it will bounce back impulsed by the ramp if it's going slow enough.

As another oddity, carts coming from ramps will in some cases "teleport" through most of the next tile. This is called the "checkpoint effect", and is explained in detail in the Physics section, below. This negates the deceleration of the next tile if it is a ramp "angled" in a different direction. You can just make an upward spiral alternating impulse ramps and regular upward ramps. It takes no power, is quick and cheap to build, requiring only channeling and track carving, and the cart goes up fast, but not so fast that it launches its contents.

Examples of impulse elevators:

{{diagram|spaces=yes|\
z +0 z +1 z +2 z +3
░░░░░ ░░░░░ ░░░░░ ░░░░░
░╔░░░ ░▼╚╗░ ░░▼▼░ ░░░░░
░╝░░░ ░▼░░░ ░░░╔░ ░░░▼░
░▼▼░░ ░░░░░ ░░░╝░ ░╚╗▼░
░░░░░ ░░░░░ ░░░░░ ░░░░░

z +0 z +1 z +2 z +3 z +4 z +5 z +6 z +7 z +8 z +9
░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░
░▼░░ ░░╗░ ░╔▼░ ░▼░░ ░░░░ ░╔╝░ ░▼▼░ ░░░░ ░░╗░ ░╔▼░
░╔╝░ ░▼▼░ ░░░░ ░╚░░ ░▼╝░ ░░▼░ ░╚░░ ░▼╝░ ░░▼░ ░░░░
░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░

░ : Wall
╔,╚,╗,╝ : Track/Ramp
▼ : Down Ramp (empty space)
}}

Note that these impulse elevators, due to the checkpoint effect and upward curved ramp effect, will not actually result in carts traveling straight up the ramp. They will lose speed, bounce off a ramp, then be accelerated back into the spiral after a 9-turn delay on both tiles on the floor where they are stopped. This is because the checkpoint effect allows carts to travel up the ramps in a single turn, but also prevents the impulse ramps from adding acceleration unless the cart is slowed to staying on the ramp for more than one turn. Initial acceleration will carry the cart up a variable number of floors before this effect occurs, but this bouncing back and forth will occur every 5 z-levels after the first time the cart stops. When the cart ''is'' traveling upwards, it will pass every tile at a rate of one tile per turn regardless of its actual speed, due to the checkpoint effect. In tracks with only a single cart, this is negligible, but when multiple carts are on the same track (such as when you place multiple carts on a magma cart lift) this can cause collisions which derail carts, or cause other unexpected or undesired behaviors.

The following impulse ramp (while larger) should alleviate these problems by using a straight ramp to go upwards, preceded by an impulse ramp to exploit the checkpoint effect and negate up ramp costs. Corners still decelerate carts, so the cart will tend towards a velocity of 72k, which is derail speed. Derail speed breaks (see Controlling Speed, below) may be necessary at the top.

{{diagram|spaces=yes|\
z +0 z +1 z +2 z +3
░░░░░░ ░░░░░░ ░░░░░░ ░░░░░░
░░░░░░ ░╔╔═░░ ░░▼▼╗░ ░░░░░░
░║░░░░ ░▼░░░░ ░░░░╗░ ░░░░▼░
░╚░░░░ ░▼░░░░ ░░░░║░ ░░░░▼░
░╚▼▼░░ ░░░░░░ ░░░░░░ ░░═╝╝░
░░░░░░ ░░░░░░ ░░░░░░ ░░░░░░

░ : Wall
║,═,╔,╚,╗,╝ : Track/Ramp
▼ : Down Ramp (empty space)
}}

Also, if you want to have a cart following a below-derail speed, the following track works well:
{{diagram|spaces=yes|\
z +0 z +1 z +2 z +3
░░░░░ ░░░░░ ░░░░░ ░░░░░
░░░░░ ░══░░ ░▼▼║░ ░░░▼░
░║░░░ ░▼░░░ ░░░║░ ░░░▼░
░║▼▼░ ░▼░░░ ░░░░░ ░░══░
░░░░░ ░░░░░ ░░░░░ ░░░░░

░ : Wall
║,═ : Track/Ramp
▼ : Down Ramp (empty space)
}}
In this elevator, the cart collides with the walls in the corners, but then realigns on the ramp, picks up speed, checkpoints through the next ramp, and slams into the next wall. It is slower (10 ticks per floor) but produces reliable speeds, and will exit the impulse elevator at little more than push speeds.

A sort of opposite effect to impulse ramps also exists: ramps lacking the proper "up" and "down" connections are treated as flat track, even if they actually go up or down z-levels. This allows building "anti-impulse" slopes consisting entirely of ramps only connected up, which a minecart can travel up forty levels and more, needing no more than a single push.

=== Controlling traffic ===

==== Switching ====

As tracks are constructions or tile features, [[door]]s and other furniture can be built on them. A [[door]] or [[floodgate]] can be turned on or off by a [[lever]], effectively controlling the flow of automated minecarts. This may be <s>dangerous</s> [[fun]], however.
{{diagram|spaces=yes|\
->
A ════┤≡════ B
┤ : roller pushing to East
≡ : door
}}
The roller pushes the cart east, but until the "departure condition" is fulfilled, the door remains closed and blocks the path.

[[Bridge]]s can also act as tracks, but only if they're lowered or not retracted. This property can enable levers to turn tracks on and off. However, care should be taken to ensure that such bridges are never operated while a cart is on top of them, as the cart will be flung off the track. It's worth noting that it's often faster, and cheaper, to construct large bridges than long sections of constructed track.

A powered track switch can be constructed by building an "inverted" corner as illustrated below.
{{diagram|spaces=yes|\
B B
║ -> ║
║ ║
════╚═══ ════├════
A C A C
├ : roller pushing to West.
}}

If the cart is pushed East from the stop at 'A' while the roller is activated, it will arrive at 'B'. If the roller is not running, it will arrive at 'C'. The switch works by the roller first reversing the incoming cart's movement and the cart ''then'' following the track corner.

This switch is very reliable, reacts instantly to on/off signals, and carts of any speed can be switched by this design, although very fast carts will require rollers that are several tiles long, up to three. The requirement for power can be inconvenient or impractical. Non-powered solutions may use controlled derailment, or a connecting bridge.
{{diagram|spaces=yes|\
B ╥
║
║
╞════╝ ════╡
A D C
}}
Here the track between A and C is not continuous. The only continuous track is A->B, with a corner (not a T section). Fast moving carts will tend to derail at D and rejoin the track to C. Placing a door at D will prevent the derailment, so the cart continues to B. The door is operated by mechanisms elsewhere (typically, a lever, but some fun can be had with pressure plates).

Since it depends on derailing, this switch requires a very fast cart, faster than what can be achieved with rollers alone. To gain sufficient speed, a cart must be accelerated further, usually by descending several levels or through impulse ramps. The high speed makes the cart much more dangerous and harder to control.

If carts are moving too slowly to derail at the corner, a retractable bridge may be used as a connector between A and C.
{{diagram|spaces=yes|\
B╥
║
║
A╞════bbb════╡C
}}
The bridge must overlap the corner. Bridges behave like a track crossing, allowing carts to pass in a straight line. When retracted, the corner reappears, so the carts will continue to B. Bridges take 100 steps to react to a signal, necessitating rather long "lead times" when switching tracks via bridge.

As mentioned above, special care must be taken to make sure the bridge doesn't change state while the cart is passing over it. Retracting bridges will throw the cart, causing it to stop dead. Raising bridges can even crush the cart.

==== Controlling Speed ====


Minecarts can reach extremely high speeds, especially when descending multiple Z-levels. A minecart will derail at a track corner if its speed exceeds 0.5 t/st (tiles per step), '''unless''' the route in the direction of travel is blocked:

Will derail at > 0.5 t/st:

{{diagram|spaces=yes|\
in ══╗ -> derailing
║
out
}}

Will not derail at > 0.5 t/st:
{{diagram|spaces=yes|\
in ══╗O
║
out

O : wall/column.
}}

This behavior can be used to build a "speed limiter", that will ensure that when a minecart exits it is traveling below derail speed, as illustrated in these three examples:
{{diagram|spaces=yes|\
░░░░ ░░░░░ ░░░░░
in ═╔═╗░ ░╔S╗░ ░╔S╗░
out ═╬═╝░ out ═╗═╝░ out ═╗═╝░
░╚S╝░ ░╚═╝═ in ░╚S╝░
░░░░░ ░░░░ ║░░░
in
░ : wall
S : Track Stop (High Friction or lower)
}}
If the minecart is traveling below derailment speed, it will not be affected; if above, will be slowed down and checked again. Granted, you could do the same just with track turns, but it may take a lot of turns and time.

Since all the derailings, bounces and ramps can impart a sideway component of speed small enough to start visible drift many tiles away (say, [[Fun|in the middle of a bridge]]), track turns have one more use: forcing the carts to move strictly along the grid directions. Carts passing a turn below derailing speed convert one component of velocity into another, thus eliminating the drift.

=== Loading liquids ===
[[Water]] and [[magma]] can also be loaded into minecarts by submerging them to a depth of at least 6/7 while standing still or moving at speeds of at most 10000. Loading fluids onto minecarts can be difficult because the added friction provided by fluids can stop a cart in a submerged tile. Curiously, filling a minecart with magma does not injure a dwarf ''riding'' it. A minecart will hold enough fluid to increase the depth of a single tile by 2. This amount is listed as 833 units, which weigh 459Γ (water) or 999Γ (magma). An iron or steel cart filled with magma weighs 1313Γ, while an adamantine cart filled with magma weighs 1007Γ. Since you need a minecart above the liquid's level, possible arrangements may include pressure-activated sluices, rollers (with magma-safe chains for magma), pouring from above to "submerge" it briefly on the same level and drain excess away (dig deeper and leave a vaporizer, though if you could have power for rollers, may as well use a pump) and exploits with ramps (not necessarily impulse ramps, "same height" passing dip does it).
The liquids can be dumped by a constructed track stop.

== Quirks ==
This little quirk concerns dwarf-managed minecarts. If a track which was previously open becomes blocked (ex. flipping a switch connected to a floodgate you've built on the track to raise it) and the conditions for departure are met, instead of refusing to ride/guide the minecart or ride/guide it until it reaches the obstacle, the dwarf will pick up the minecart off the tracks and haul it to its scheduled destination on foot. If the distance is long enough and the weight of the cart heavy enough (due to being filled with heavy items such as stones), the dwarf may drop the cart because of fatigue/hunger/thirst before reaching the destination. This will cancel that vehicle setting job and make another dwarf come by and attempt to haul the cart to the nearest appropriate stockpile where another dwarf will pick up the cart and attempt to haul it to its initial stop. If the stockpile is far enough from initial stop, this second dwarf who is attempting to place the minecart on its tracks may also drop the minecart out of fatigue/hunger/thirst creating a loop that will go on until a dwarf with enough endurance manages to place the minecart where it belongs.

In fact, it seems dwarves are more than happy to attempt to carry a minecart from one stop to another even if just waiting until the track is open again would be the more sane option.

Dwarves will also carry a minecart to its next stop if the direction specified is incorrect (or invalid). This can often occur when using the default departure settings and forgetting to set the direction of each condition.

Dwarves can admire buildings while riding mine carts. Dwarves will not fall asleep during a ride (at least not from being drowsy). If riding on a continuous powered track loop, the dwarf will die of dehydration/starvation as they can not jump off to get sustenance.{{cite forum|109460/3377228}} Dwarves riding in submerged minecarts will gain experience in [[swimming]].{{cite forum|129889}}

Tracks block wagon access to trade depots, unless they're on a ramp. [[Bridge]]s can also be used, as they function as tracks but do not block wagons.

== Physics ==


Minecart physics depend greatly on the departure mode set in the route stop conditions.

When set to "Push" or "Ride", minecarts will move according to the regular laws of momentum, gaining speed when going downhill, losing it slowly due to friction when on a flat plane, and more quickly when going uphill. In these modes, minecarts will move in a straight line until they either are brought to a stop by friction or an obstacle, or until they encounter a turn. A minecart will roll straight past "blocked" ends of T-junctions or track ends, they have no power to restrict a cart's movement. The cart's behavior is largely independent of the weight of its contents (including fluids and dwarves): heavily loaded carts gain more momentum when accelerating, but this only plays a role in collisions: a heavy cart gains just as much speed and is as easy to stop as a light one. In either case, dwarves can not push nor ride an unpowered cart up a ramp, bouncing back the direction it came. At best, this is a waste of time; at worst, it will give your cart-pushing dwarf a [[fun|fun surprise]]. To solve this, the player can either use Rollers (see below) or set the cart to be Guided.

The difference between "Push" and "Ride" is whether the dwarf will go along with the cart or not.
{{DFtext|Push}}: the dwarf will give the cart an initial push, not enough to go up a ramp, but enough to go some way along flat track, and the dwarf will remain at the first stop, ready for a new job.
{{DFtext|Ride}}: the dwarf will give the cart the same initial push and then hop aboard the cart riding with it to the next stop.
{{DFtext|Guide}}: minecarts seem to ignore all laws of physics. That is:
*Ignore the weight of any and all items inside. Therefore:
**Move at the speed of the dwarf that is guiding them. It is thus recommended to pick the most [[attribute#Agility|agile]] of your dwarves for cart-guiding tasks.
*Ignore working rollers.
*Will ''not'' collide with other guided carts even when a full frontal collision would be expected.
*Will go up ramps like nobody's business.
This is therefore the recommended method of transport for simple non-powered rail systems, despite it diverting a dwarf from other, potentially more important tasks.

Some samples with behavior:
{{diagram|spaces=yes|\
A <-> B A <-> C A <-> B
B B B
║ ║ ║
A══╝ A══╩══C A══╬╗
You can only go A->B ╚╝
Works when the cart Works
is in Guide mode.
}}
In the second example above, a cart "pushed" from B will go over the junction and roll off into the unknown south.

=== Numbers behind the scenes ===

According to early research by '''expwnent'''{{cite forum|112831/3536975}}:

The minecart has 3 variables for velocity. Velocity can be thought of as tiles per 100000 ticks, so a velocity of one hundred thousand means a cart travels one tile per tick. By going down a large number of ramps, a maximum velocity of 270,000 can be reached, which presents the limit for most practical applications. Short bursts of (much) higher speeds are possible through carefully planned collisions of high-speed carts.{{cite forum|137557/5145499}} (See [[#Perfectly Elastic Collisions|Perfectly Elastic Collisions]].)

Every tick the cart adjusts sub-tile position units by the amount of their velocity, as well as adjusts velocity depending on current tile (speed is reduced by the "friction" of the tile, or accelerated if going "down" a ramp). On flat (non-ramp) tiles, the cart will move to the next tile when the sub-tile position goes 50000 away from the centre of the tile, denoted by the no-fraction integer value - tile 15 e.g. has its centre at the exact value 15 and its borders at co-ordinates 14.5 and 15.5.

Since most deceleration and acceleration is applied per step, with the notable exception of corners, a cart going at twice the speed of another one can travel about four times the distance before coming to a stop when going in a straight line, but only twice the distance along a winding track with very many corners.

A push will teleport a cart to the middle of the next tile in one tick with 19990 speed (10 speed is lost due to track friction), while a roller will directly give a cart the roller's set speed (minus friction) and the cart starts accumulating distance from its standing position. When a cart leaves a ramp it will emerge after one tick at the very end of the next regular tile.

Friction of tiles:
{| class="wikitable"
|-
! Tile
! Friction
! Comment
|-
| Tracks
| 10
|-
| Ground/Floor
| 200
|-
| Unusable ramp
| 10
|-
| Upwards ramp
| 4910 (10+4900)
|-
| Downwards ramp
| -4890 (10-4900)
|-
| Roller
| ±100000 (but capped by the set speed)
|-
| Corner track
| 10
| Speed reduced by 1000 upon leaving the corner tile
|-
| Track stop (highest)
| 50000
|-
| Track stop (high)
| 10000
|-
| Track stop (medium)
| 500
|-
| Track stop (low)
| 50
|-
| Track stop (lowest)
| 10
|-
| Water 1-6
| Additional (WaterLevel - 1) * 100
| rowspan="2" | [[#Skipping|See Skipping]]
|-
| Magma 1-6
| Additional (WaterLevel - 1) * 500
|-
| Empty space
| 0
|}

Water of depth 7/7 provides a friction of about 10000 per step. Maximum-depth magma causes at least as much friction, possibly more. This higher friction may not apply to very slow-moving carts.

Impulse sources:
{| class="wikitable"
|-
! Feature
! Speed
|-
| Push
| 20000
|-
| Roller lowest
| 10000
|-
| Roller low
| 20000
|-
| Roller medium
| 30000
|-
| Roller high
| 40000
|-
| Roller Highest
| 50000
|-
|}

Note, again, that nearly all of these values are applied ''per tick'', rather than ''per tile''. The exceptions are curves, which is 1k deceleration per direction change at the end of the tile, and rollers, which ''set'' the speed every tick. This makes rollers particularly useful in high-deceleration situations, such as underwater, but require that ''nearly every tile'' in such high-deceleration situations have a roller.

A cart heading up a ramp can experience deceleration on multiple ticks, (and stays on the tile more ticks the slower it is going, resulting in greater deceleration,) and as such, a cart leaving a "Highest Speed" roller with 50k velocity will not be able to climb 10 consecutive straight ramps, since they are ''not'' "5k deceleration each". In fact, the first ramp not on a roller will be -15k velocity, and, depending slightly upon other factors of "remainder" x position, the second may completely cancel forward momentum, and send it rolling back down, where it will bounce off the roller repeatedly. Using rollers to power carts up ramps reliably requires rollers every other un-rollered ramp. Fortunately, rollers can be built upon ramps, themselves, which allows for rollers to only need to be built every other floor. (Exploiting the [[#Checkpoint Effect|checkpoint effect]] can allow one to bypass this requirement.)

There are two important speed values which affect carts' behaviour:

"Derailing" can happen when a cart moves at speeds in excess of 50000 - carts will ignore track corners unless forced to obey them by walls or other obstacles blocking the straight path.

The "shotgun" effect takes place when a collision changes a cart's movement speed by more than 55000: loaded carts subject to such a change eject their contents, which then keep on moving in a ballistic trajectory, in the direction and at the speed the cart had before the collision (with a small random vector added). This effect entirely rides on the amount of speed ''change'' - a speeding cart crashing into a wall can be subject to it just as well as a standing cart accelerated by a speedy cart smacking into it. It can even happen when two relatively slow-moving carts (down to speeds below 20000 in extreme cases) collide head-on.

=== Sub-tile Positions and Velocity ===
Carts store six values that are unique to them. Three sub-tile position values, and three velocity values. (X, Y, and Z.)

Note that the Z position and velocity only matter when a cart is in flight. (See [[#Falling|Falling]] and [[#Cart Jumps|Cart Jumps]].)

Each non-ramp tile is functionally composed of 100,000 individual minimal-length positions ''within'' the tile in both dimensions. When a cart has velocity, it is added or subtracted from the current position every tick, and then a friction force is applied to the cart.

In essence, every sub-tile position unit is a decimal value of a tile, 0.00001 tiles, in a game that largely prefers integer values.

The exact cart coordinates shown e.g. by a DFHack script must be rounded arithmetically (up or down to the nearest integer) to find the current tile: a cart in the centre of a tile will be at sub-tile zero in all directions, and it will cross into the next tile when subtile value is more than 50 000 higher or lower than the full number.

When carts move beyond the borders of a tile, they physically move a tile on the map, and start at the far end of the sub-tile position the next tile. (I.E., traveling West, a cart that starts a tick 15,000 X away from the border and has an X velocity of -20,000 will move -5000 X past the adjacent border of the next tile in direction -X. It will also lose 10 velocity in that tick due to friction with the track if it is on a track, or 100 velocity if it is on regular ground, or no velocity if it is airborne.)

Ramp tiles are longer, approximately 141,420{{cite forum|157627/0}} in the direction where it "slants downward", (to approximate a 45 degree slope, it is square root of two times longer,) with a centre-to-border distance of 70,710. Because of this, a cart with no velocity dropped from a hatch will land at the center of a tile, 70,710 away from the tile's borders in both directions, and will start rolling in the ramp's "downward" direction, picking up the ramp's acceleration (4890 per tick in the direction of the ramp's "downward" direction) every single tick, then moving that sub-tile amount every tick. (This results in a cart that takes 5 ticks of acceleration to leave its ramp - 6 ticks overall - and to leave the ramp with about 23k velocity, slightly more than a push.) When it enters another ramp ''facing the same direction downwards'', a cart will start at the -70710 or +70710 position, and have twice as far to travel. This means that if a cart enters a ramp from the side, it will gain twice the momentum of simply starting at the midpoint of a ramp.

Note that passing from one direction of ramp to another or to flat terrain causes unintuitive behavior, "teleporting" to the end of another tile in what is called the "[[#Checkpoint Effect|checkpoint effect]]".

Note, however, that all sub-tile positions are carried over from tile-to-tile. This separate tracking of velocity and position between X and Y can lead to problems with diagonal motion:

{{diagram|spaces=yes|\
z0 z-1
▒║▒ ▒▒▒
═▼═ ▒╬▒
▒ ▒ ▒║▒
▒ : Wall
═, ║ : Track
╬ : Track and Ramp
}}

If a cart is passing West-to-East over this setup, the valid ramp to the South will apply "Southward" acceleration to the cart (-Y velocity) as it passes through the ramp tile. Assuming it only spends two ticks in that tile, it will have gained a lasting -5k Y velocity, which will still apply motion Southward. If the cart continues travelling over straight track for another ten steps, it will have accumulated enough Southward motion to try to move a tile South, even if all tracks are facing East-West.

A single tile spent on the ramp will not grant lasting southward motion, because the acceleration will be neutralised through the checkpoint effect when the cart leaves the ramp again, but the cart will be displaced about 5k sub-tiles southward, which can cause it to gain more or less speed than an undisplaced cart when meeting another south- or north-accelerating ramp.

'''Non-curving tracks do not correct this motion'''.

They don't "tip back over" without adjustments in the track. Any value of sideways motion on tracks larger than 990 will lead to a derailment. (Lower values will be nullified by friction before they are enough to lead to derailment, but there is currently no way to apply such a small amount of velocity.)

If the tile to the South is a wall at that point, it will be considered a collision with a wall that ''halts all motion''. If the tile is open, the cart will simply leave the track and travel over the terrain beside it. In almost any circumstance, this is undesirable behavior.

The only way to appropriately deal with this is to either cancel out this behavior with an equal amount of acceleration in the opposite direction, or to take a curve.

Note, again, that sub-track position is saved in both directions, so when a cart approaches a curve, it will already have a shorter or longer distance past the curve when it makes the turn.

Curves are applied at the end of a tile. If a cart is moving East, and approaches a North-West track corner at 30k velocity, and friction is eliminated for the purposes of a cleaner demonstration, then when it enters the tile on the western (X coordinate) border of the tile, but in a central North-South (Y) orientation (sub-tile -50k X and 0 Y due to arithmetic rounding), it will then move 30k East (+X) the next tick, and be at -20k X sub-tile position, and 0 Y sub-tile position. Next tick, it is at +10k X sub-tile position, and 0k Y sub-tile position. Two more ticks would take it to +70k X, but that's past the tile border, so it stops at 50k, turns (and thus loses 1k velocity, but translates the rest from X-velocity to Y-velocity) and travels another 20k. It is now at 0k X sub-tile position, and -20k Y sub-tile position (i.e. it's re-set from the end to the middle of the tile with respect to the X co-ordinate). Next tick, it travels at 29k velocity North, and so moves to 0k X sub-tile position, and +9k Y sub-tile position. Then in two more turns, it leaves to the North.

In the case of diagonal motion due to having velocities in X and Y at the same time, it is critical which tile the cart actually tries to enter next. Only if the path into that tile is blocked by the corner branches will the cart take the corner and rewrite its velocity, otherwise it leaves the corner tile without changes to its motion. If the cart is redirected by the corner, all sideways velocity is lost, as forwards velocity ''overwrites'' sideways velocity in a curve. If, in that example in the paragraph above, the cart entered at -50k X sub-tile position with 30k X velocity, and 40k Y sub-tile position and -1k Y velocity, it would take that "curve" (or rather, redirection of velocity) on the fourth turn, while it is at 37k Y sub-tile position to start with, and then move to -53k Y sub-tile position at the end of that tick. It would then move to -26k Y sub-tile position in the following turn, and take 3 turns to clear the tile.

But, most importantly, it would be centered in the X sub-tile position, and all sideways velocity is safely removed.

There are two common ways to gain sideways velocity: Rollers facing perpendicular to the cart's travel path (which, as covered above, are almost always a bad idea, as it is easier to push ''against'' the travel direction of a cart into a curve, which redirects all velocity in the new direction,) and [[#Corner Ramp Derail|corner ramps]], and require a curved track to compensate for sideways velocity within a few tiles.

=== Track Direction Irrelevance ===
Carts that are traveling independently (that is, not guided) only care that tracks ''are'' on the tile, not which direction the tracks actually move. Tracks respect only curves (with two exits) and ramps.

This means, for example, that the following tracks, when a (non-guided) cart travels from West-to-East, are functionally identical in effect:

{{diagram|spaces=yes|\
A════════════B A╬║╚╔╣╩╦╠╥╨╞╡B
}}

This is because so far as the cart is concerned, only valid ramps and curves with two exits where there is no exit in the path they are traveling matters.

Hence, if a minecart encounters the end of the track or a T junction with no "exit" in its movement direction, it will simply leave the track and continue on its course in a straight line until it encounters an obstacle, slows to a stop, or encounters another track even if the tile at which it joins the new track instantly sends it around a corner.

In fact, in a track designed for pushes or rides, a "║", a "╦", a "╬", and a "╥" are ''only different in appearance'', and are ignored by an unguided cart, which will continue in its current direction, regardless of the track. For any purpose but guided tracks, ''only curves and ramps matter at all''.

Tracks like T-junctions, however, ''are'' respected by dwarves guiding carts, who will lift and carry carts if they cannot find a valid track to their destination, and can choose to follow any orthogonal direction at a four-way junction in much the same way as they normally pathfind. What this functionally means is that T and four-way junctions ''only guide dwarves hauling a cart, not carts, themselves''.

Carts only check for curves when they are halfway through a tile. When they get there, they look to see if their path has no exit. (That is, if it is traveling East, it checks if there is an East exit.) If there is, it ignores all other track directions, and keeps traveling. If there is not, it checks to see if there are only two exits to the track, and if one of those directions was the direction it "came from". (That is, if traveling West from the East, it checks if there is a valid exit to the West, and if not, if there is an East exit and EITHER a North or South exit.) If there is not, it ignores the track anyway, and keeps on traveling as though it were still on track.

If there is a curve the cart will respect, it checks for derailment. Carts derail if their speed is higher than 50k. Carts at this critical speed will then check for blockages of their forward path. If there is an obstacle to their path, which may be a wall or even furniture or buildings like a door, they will not derail and respect the curve, anyway. Derailing carts do not "[[#Cart Jumps|jump]]" unless they hit completely untracked tile or an invalid ramp, but simply ignore the layout of the tracks entirely. With invalid ramps, this means not respecting the ramp, and likely results in collision with a wall, zeroing of all velocity, and a cart that requires manual retrieval.

If the cart is traveling at a speed that will not derail, or is forced to turn by a supporting wall, it will subtract 1000 from the "forwards" velocity of the cart, and redirect all forward velocity to the direction of the curve. This change in the direction of velocity ''overwrites'' any "diagonal" velocity, which can prevent diagonal velocity derailments, but any perpendicular velocity is not preserved, and is instead discarded.

=== Valid and Invalid Ramps ===
Ramps are functionally defined for cart purposes as being a tile which exerts an acceleration force upon its "downward slope", and which allows connection to tracks a z-level above or below. This downward slope requires a cart to have at least one track branch touching a wall tile and one ''and exactly one'' carved exit to the tile that is the "bottom" of the ramp. Ramps accelerate carts in this "downward" direction (possibly leading to [[#Corner Ramp Derail|diagonal movement]]), and the deceleration of an "uphill" ramp is actually just the acceleration being applied against the direction of a cart's movement.

This is where players can find an exploit in the behavior of ramps - if there are ''two'' "downhill" exits to a ramp (such as a "T junction" on a ramp where only one exit faces a wall), then the ramp provides no acceleration ''or'' deceleration, allowing carts to travel up ramps without any loss of momentum except for the standard "flat track" deceleration, because as far as the cart is concerned, the track ''is'' flat. (A T junction is also not a curve, so the track is considered flat and straight no matter what direction the cart is traveling.)

Similar effects can be achieved when there are ''no'' "downhill" exits to a ramp. This may be the case if you have, for example, an East-West track with a one-tile channel with a ramp in it. The cart will travel through the "dip" with no change in velocity. It can also be the case if you abuse the [[#Track Direction Irrelevance|Track Direction Irrelevance]], and set only exits ''up'' the ramp, and none leading ''down'' the ramp. For example, if a cart is traveling from West to East up a slope, only carving East exits on each tile of ramp will make the cart travel up the ramp, and then recognize the tile it is on as being a "flat" tile, thus ignoring any deceleration from traveling uphill.

Note that this effect only reliably occurs at below-derail speeds as the cart will treat the ramp as an invitation for a ramp jump otherwise. (This almost always results in a collision with a wall that will stop forward progress.)

=== Falling ===
When falling, a minecart appears to cause no damage upon collision, possibly to allow cart "stacking" across Z-levels.{{cite devlog|2012|04|06}} A dwarf riding in a minecart that is dropped multiple z-levels suffers normal fall damage. Minecarts can fall through up/down stairs.

While airborne, carts do not feel the effects of friction in any horizontal direction, and will continue until they strike an obstacle. Carts that land on tracks instantly re-rail themselves regardless of track directionality.

Falling carts accelerate similarly to the way that a ramp will accelerate a cart in a special z-only velocity that only applies to airborne carts. (Actually, since a tile is notionally 1.5 times as high as it is wide/long, acceleration due to gravity in freefall appears slightly ''slower'' than ramp acceleration, since it has to move the cart (or any other object) a greater distance.) Ramp acceleration, while it logically should be partially z-directional, is only recorded as x- or y-directional, and there is no translation of z-directional velocity upon landing. Landing carts zero out their vertical velocity upon landing, even when landing on ramps, although carts that had horizontal momentum while falling preserve it.

This means a cart falling onto a track ramp is accelerated as if starting from the middle of the ramp - i.e. to the same speed, no matter how many Z-levels it was dropped, vertical velocity is negated. {{cite forum|144328/5701211}} As a consequence, the fall damage to passengers is also negated.

Carts falling onto a floor can, however, cause damage to creatures ''one tile below the floor''. This can be used in an [[exploit]] called a "thumper", where carts are caused to repeatedly fall on a floor above an entrance to the fort, inflicting significant damage (as though it were a collision) on those below the cart.

=== Cart Jumps ===
Carts that cross off of "up" ramps relative to their current direction of travel, which do not have a ceiling above them, are traveling above derail speed, and do not have valid ramp track before them can translate a portion of their horizontal velocity into vertical velocity, causing a cart to be projected into the air until vertical velocity is negated and overcome by the gravitational acceleration. Because downwards acceleration is applied per-tick, this creates a reasonable facsimile of the parabolic motion of an actual object rolled up a ramp and launched with significant speed.

{{diagram|spaces=yes|\
z0 z0 hiding ramps z+1 A z+1 B (hidden ramp)
▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒
═▲▲▲▲▲══▲▒▲═ ═╚╚╚╚╚═══▒══ ▼▼▼▼▼ ▼═▼ ▼▼▼▼▼ ▼╚▼
▒ : Wall
═ : track
▲ : Ramp
}}
In this diagram, if there is no ceiling above it, the track in z+1 A will launch its carts airborne when they travel across the ramp. z+1 B (with a ramp on the tile on the hill) will not launch the cart. The cart would also not be launched with ''any'' valid ramp, even if it does not travel in an appropriate direction, such as North/South (which the cart will ignore, as it is not a curve, anyway, although it may produce acceleration that may cause diagonal movement.)

Carts that are traveling at derail velocity will also start "jumping" from the track if it hits an un-tracked tile, flying over and ignoring any tracks until it is ready to land. Carts that land upon tracked tiles re-rail themselves, and clever designers use this feature to jump over curved track sections in one direction or another. (Retracting bridges over untracked tiles can cause jumps or not cause jumps depending upon the status of the bridge.) Minecart speed must be carefully regulated to ensure reliability of jump length.

Hitting untracked tiles at around 70k velocity creates a vertical component to acceleration that allows for jumps of around 6 (horizontal) tiles that do not actually leave the z-level the cart is on, but which do apply z-direction velocity on the cart, as per falling.

Carts that approach a downward slope at a high enough velocity will also make a jump, (or rather, ignore the ramp and fly forwards) but will not do so if the [[#Checkpoint Effect|Checkpoint Effect]] is exploited through an impulse ramp before the actual downhill as the impulse ramp "tricks" the cart into thinking it has already started going downhill.

=== Skipping ===
If a minecart is moving fast enough, it can skip over [[water]] or [[magma]], making splashes of [[mist]] (or [[magma mist]]) as it attempts to move on them horizontally. This horizontal movement is independent of the minecart and its content's [[weight]].

Skipping causes significant friction on the cart, and even a cart going at max speed from ramps can only make about 50 tiles without requiring re-acceleration. (Carts that decelerate enough that they do not trigger the skipping effect will, of course, sink.)

=== Corner Ramp Derail ===

Corners on upward ramps can cause diagonal movement, forcing a derail even if the cart has a wall next to it, which will force a stop when it touches a wall that forces dwarves to manually reset the cart.

This is caused by the fact that a cart, after turning the bend in the track and entering e.g. a flat tile, will be subject to the checkpoint effect which applies 5k acceleration opposed to the last amount of ramp acceleration it received. Since the cart has just passed a corner, this compensatory speed adjustment now goes to the "outside" of the corner and creates enough lateral velocity to carry the cart off the track after eleven steps. (Down corner ramps do not have this problem, as the downward direction is in line with the past-corner movement direction and the checkpoint effect works on the only remaining movement vector.)

There are two fixes to this problem. One is to simply not put corners on up ramps. The other is to "cancel" the lateral speed after a cart has passed the ramp, either by sending the cart through another corner or by putting a high-friction track stop on the exit tile. In the latter case, the cart will lose 10000 speed in the desired direction, but the same speed loss will apply to the undesired lateral speed, nullifying it.

=== Checkpoint Effect ===
The checkpoint effect, [http://www.bay12forums.com/smf/index.php?topic=144328.0 explained in depth by Larix], is an odd and highly exploitable feature of ramps where minecarts "teleport" through the next tile of track, ignoring nearly all minecart physics (except that they stop at all walls or other obstacles and only respect curves with no backing wall and invalid ramps if they are below derail speed) and passing through that tile in just a single tick, and to the very end of the next tile.

This effect occurs when a cart leaves a downward ramp for any other direction of tile. (This includes ramps which accelerate in different directions, even a ramp which goes from accelerating East to accelerating North due to a bend in a chain of standard down ramps in a curve.) This allows, for example, two valid straight ramps directly next to one another with a cart dropped onto one or the other with no momentum to have the cart pick up acceleration going "down" the ramp as normal, but then flying up through the "up" ramp it travels into with no loss of momentum, as though it had come from an impulse ramp. If the two ramps had at least one space of distance between them, and then a cart were dropped in, the cart would instead "rock" back and forth between the two ramps.

This seems to be because ramps have a slightly longer length than regular tiles - 141,420, rather than 100,000 distance. When this "snaps back" after a ramp, it seems to project the cart suddenly further along the track, making it jump a tile ahead even when otherwise moving at relatively low speeds.

This [[bug]] is the cause of a ''wide array'' of unexpected behavior among people who do not take this bug into account. It causes derailments or failure to climb up seemingly valid impulse elevators. In general, it makes a system that behaves extremely counter-intuitively, and operates ''any time a cart encounters a valid ramp''. At the same time, when its effect is accounted for, it is highly exploitable: It causes "perpetual motion devices" using no power when two opposing ramps are placed next to one another, since the "uphill" effect of the opposing ramp is ignored, preventing deceleration.

Another useful thing to note about this exploit is that carts traveling at no less than 71,000 or so speed (enough to travel half a ramp tile in a single tick) can travel through every tile in just one tick at no change in velocity as long as the tiles alternate between impulse ramp or actual down ramp and any other tile type. The cart checkpoints through the non-down-ramp tiles, and can pass through the (impulse) down ramp tiles in a single tick, before they can actually start gaining momentum.

{{diagram|spaces=yes|\
▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒
═▲═▲═▲═▲═▲═ ═╚═╚═╚═╚═╚═
▒ : Wall
═ : Normal track
▲/╚ : N/E Track/Ramp
}}

If the cart enters from the West at less than 72,000 speed, some of those ramps will cause Eastward acceleration.

This means that an impulse ramp not contiguous to other impulse ramps has a top speed of around 75k:

{{diagram|spaces=yes|\
▒▒▒▒▒ ▒▒▒▒▒
▒╔═╗▒ ▒╔═╗▒
▒╚▲╝▒ ▒╚╗╝▒
▒▒▒▒▒ ▒▒▒▒▒
}}
This setup makes a cart that travels clockwise at a speed that fluctuates around 75k velocity. If the cart has more than 72k velocity, it fails to accelerate in the ramp, as it leaves the ramp in a single turn due to checkpointing to the halfway point. After that, the curves sap 1k velocity, and every tick saps 10 velocity.

Two contiguous impulse ramps with a same-facing "downwards slope", however, do not suffer the checkpoint effect in the second tile, giving functionally triple the space to accelerate. This means it will add velocity (at the standard rate of 4.9k per tick) up to a maximum speed of 216k.
{{diagram|spaces=yes|\
▒▒▒▒▒▒ ▒▒▒▒▒▒
▒╔══╗▒ ▒╔══╗▒
▒╚▲▲╝▒ ▒╚╗╗╝▒
▒▒▒▒▒▒ ▒▒▒▒▒▒
}}
This example results in a cart moving three times as fast as the previous cart.

Three successive ramps results in the highest attainable speeds.

In practical terms, this means that only consecutive ramps should be used for high acceleration, but singleton ramps can be used to have speeds that are somewhat regulated.

=== Stacking ===
If a minecart lands on top of another minecart, they may form a stack, with the upper cart on the z-level above the lower. Subsequent carts do not form a stack, but rather quantum stockpile in the same space. This behaviour is useful for [[megaprojects]] and [[trap design]] with minecarts as the weaponry. Moderation should still be exercised: carts take longer to fall into a "stacking" tile already occupied by other carts and will spend that time "hanging" in the air above the stack. This can lead to following carts striking them, which can cause all kinds of malfunctions. The extra time is two game steps for every cart already in the stack, which doesn't hurt stacks of ten carts very much but makes stacks of 100+ rather impractical.

These minecarts on the upper level generally need to be struck with another minecart to move out, or have their support removed. The latter option is safest done by shooting it away with another minecart, manual removal of a stack-supporting cart typically causes the next cart from the stack to [[fun|fall on top]] of the hauler.

=== Perfectly Elastic Collisions ===
Minecart collisions are perfectly elastic, meaning that not only do minecarts not take damage, but that two carts that are rolling which have frontal collisions of near-similar speed, and where one cart is no more than twice the mass of the other cart, will result in a billiard-ball-like effect of the lighter cart bouncing off the heavier cart with a proportional speed increase dependent upon the relative momentum behind the heavier cart.

Using this trick with carts already at the 270,000 maximum speed from ramps can result in "supersonic" carts traveling at speeds in the millions (travelling a dozen tiles per tick), but where they are suddenly subject to 10,000 units of "terminal velocity" friction per tick. [http://www.bay12forums.com/smf/index.php?topic=137557.0 Thread with SCIENCE here].

While hypothetically capable of launching a minecart into orbit when used in conjunction with a ramp, no cargo can be contained in the launched cart, as the collisions will force ejections of the cargo. Your "unwilling volunteer" [[goblin]] space pioneers will simply become paste underneath the wheels of an extreme high-speed cart.

== Non-standard uses ==
Minecarts include some interesting characteristics that have motivated uses beyond hauling. They can be useful for creating fully-automated [[Quantum stockpile|quantum stockpiles]], [[garbage disposal]]s, [[Water_wheel#Micro_Water_Reactor|water reactors]], and [[portable drain]]s. Storing perishable goods (meat, meals, etc.) inside a minecart appears to guard against rot and vermin.
Minecarts can be [[Trap_design#Minecarts|used as weapons]], or as (hopefully non-fatal) triggers to restart stalled [[healthcare]]. They can also be used to time/control game events, either using a basic [[repeater]] or much more advanced [[minecart logic]].
Minecarts trigger [[pressure plate]]s, which means a trap can be designed to trigger when a thief attempts to steal a minecart.
A pressure plate can be used as automatic and more precise custom "launch when full enough" system - as long as weight of your minecarts stays the same. You cannot build a hatch or roller on the same tile, so launch by bumping with another cart. {{cite forum|15096/4580050}}
Dwarves riding minecarts can attack enemies within reach (which goes back to dev log). This applies to shooting, and they actually can hit targets while riding by.{{cite forum|109460/5266119}} Whether a minecart protects the rider and how it interacts with dodging is not known yet. Minecart riders can also [[Swimming#Minecart_training|train swimming]] and [[Megaprojects#Surveillance_Track|detect ambushers]].

== Simple Example Layouts ==

=== 2-way Minecart Route ===
[[File:Simple2wayminecart.PNG|500px|Simple 2-way Minecart Route]]

This is an example of how a 2 way route can be established.
* Stop 1 is non dumping, frictionless (Feeder Stockpile from North in this example)
* Stop 2 friction and dump (dumps South in this example)
* Stop 3 is non dumping, frictionless (Feeder Stockpile from North in this example)
* Stop 4 friction and dump (dumps South in this example)

Now you create a Route hauling your desired items from Stop 1 to Stop 2 . Immediately guide the empty cart to Stop 3 (because the stop has no friction, a kicked cart will overshoot the stop).
Haul desired items from Stop 3 to Stop 4. Immediately guide the empty Cart to Stop 1.

=== Automated Minecart Funicular (Elevator that also goes sideways)===
This is an example to set up stone delivery from multiple Z levels with a common set of tracks while automatically returning the cart to where it is supposed to go. In this example, the South track goes upwards towards the drop off point, the North track goes downwards for cart return.
The design pictured consists of the following:
[[File:MinecartFunicular.gif|frame|left]]
* Two ramps next to a wall spaced one tile apart
* Tracks on top of the ramps to make an inclined track
* A 3X1 channel dug down next to the ramps on the side opposite the wall
* 2 gear assemblies, one between the ramps, one over the middle channel
* Rollers on the upward track pointing towards the wall (South ramp in this example)
* A hatch over the channel next to your downwards ramp (North ramp in this example)
* A wall diagonally adjacent to the to the upwards channel
* Tracks leading from the hatch to the single wall
* A wall next to the curved section of track
* A pressure plate set to trigger on minecarts on the track underneath the minecart. Link the pressure plate to the hatch
* Set up a minecart route with one stop where the minecart is. Set the condition to kick the minecart in the direction of the channel with any condition and contents you wish
* Each subsequent level needs to be shifted one tile in the direction of the ramp down
{{clear}}
The unloading level just needs to pass the cart over a track stop set to dump in whatever direction you want, then send it back down the return track. It also needs to provide power to the rollers, 12 power is required per level.
[[File:MinecartFunicularTop.gif|thumb|left]]
{{clear}}
How it works
* The minecart sitting on the pressure plate keeps the hatch open so that other carts may pass
* When the cart is off the pressure plate the hatch closes. This causes the cart to pass over the hatch back to its loading position
[[File:MinecartFunicularHatch.gif|thumb|left]]
{{clear}}
== Adventure mode ==
In addition to being used for hauling, minecarts can also be ridden in [[adventure mode]]. (Adapted from forum thread {{cite forum|122903/4258212}})

# If the minecart is in your inventory, drop it. If it is already on the ground, proceed to step 2.
# Press {{k|u}} when you are 1 tile away from the minecart (or standing on the same tile as the minecart).
# You will be presented with the following options:
[[File:minecart adventure mode menu.png|left]]
{{clear}}
* If you {{DFtext|Push}} the minecart, it will move a few tiles in the direction you chose. Physics comes into play here, so it will gain/lose speed depending on the usual factors.
* If you {{DFtext|Ride}} the minecart, you will hop into the minecart, even if you were a tile away, and it will move in the chosen direction with you in it. It will gain/lose speed depending on the usual factors. Whilst the minecart is in motion, you should press {{k|.}} to skip your turn; if you attempt to move whilst the minecart is still in motion, the laws of physics come into play, and you will take [[wound|damage]]. However, it is currently possible to jump out of a moving minecart safely.{{bug|10104}} Alternatively, you can push the minecart whilst it's still in motion (although it's unclear how one can bend [[physics]] so as to push a moving minecart whilst inside the minecart). If you push it in the same direction you are already travelling in, you will greatly increase the minecart's velocity. You can also push it in different directions, and this will cause it to gradually change direction-the amount of pushes this requires depends on the minecart's velocity. Once the minecart has stopped moving, you may move out of it safely, or you may want to give it another push. Note that if you push a minecart right after having ridden it (still on the same tile as the minecart), it will act as though you chose to ''ride'' it.
* When the minecart is on a track, options appear to {{DFtext|Guide}} it in directions that the tracks lead. This moves the cart 1 tile in the direction it is guided. Guiding the cart is the only way to move a minecart from a maximum friction track stop (other than taking it into inventory.)

Minecarts in adventure mode are not restricted by a lack of tracks. However, they are hindered by natural ramps. Attempting to go up a slope will lead up the cart slamming into the wall. The good news is you'll make it over the ramp. The bad news is you likely won't stick the landing.

Note that while carts are a powerful weapon if heavy and fast enough, they have their limits, and a collision can sharply reduce the speed of a cart depending on what you hit, potentially enough to eject the rider. Trying to run over a human will send them flying, while trying to ram a dragon will not end well.

If you want to test this out without creating an adventurer, the [[object testing arena]] allows you to spawn minecarts ({{k|k}}-{{k|c}}-{{k|n}})

== Forging and Melting ==
* Metal minecarts cost '''two''' [[metal]] bars to forge, or '''six''' [[adamantine]] wafers.
* When a non-adamantine metal minecart is melted down, it will return '''1.8''' metal bars, for an '''efficiency of 90%'''.
* When an adamantine minecart is melted down, it will produce '''1.8''' wafers, for an '''efficiency of 30%'''.

== See also ==
* [http://www.bay12forums.com/smf/index.php?topic=109460.0 The "How Does Minecart" Thread] by '''Girlinhat''' et al.
* [http://www.bay12forums.com/smf/index.php?topic=112831.0 SCIENCE: Quantifying minecart physics] by '''Snaake''' et al.
* [http://www.bay12forums.com/smf/index.php?topic=129676.0 How to build a Multi-cart Ore to Magma Minecart Project without needing power] by '''WanderingKid'''. (Images recovered from wayback machine and posted here: https://imgur.com/gallery/LpRsDwO)
* [http://www.bay12forums.com/smf/index.php?topic=144328.0 My very own Minecart Education Thread. Ten Lessons, now complete.] by '''Larix'''.
* [https://www.youtube.com/watch?v=hctG2dQzHwg Real-life railcarts/conveyor hybrid] which uses similar mechanics.

== Bugs ==
*A dwarf will drop her [[child|baby]], if she has one, when boarding a minecart set to be ridden.
*Dwarves have no concept of traffic safety and will walk into busy minecart lines to retrieve objects, often with deadly consequences. This is especially problematic in [[Swimming#Minecart_training|clever applications]] depending on dwarves riding the carts very frequently, because they have a bad habit of dumping their worn clothes on the tracks after a minecart ride. Adding an automatically-operated [[hatch cover]] at the end of such a ride can help prevent [[unfortunate accident]]s.
*Dwarves cannot guide a minecart through an unlocked door unless another dwarf opens the door.{{bug|6056}}
*It is possible for a creature and minecart moving towards each other to pass without collision if they exchange tiles in the same tick.
*After a minecart ride, a dwarf will sometimes haul the minecart to a storage stockpile, leaving another dwarf to haul the vehicle back to the route.
*Minecarts falling onto a floor injure creatures in the tile below the floor.{{bug|6068}}
*If a minecart travelling at high speed hits a wall, it and its contents may go through the wall, or even end up embedded in it.{{bug|5996}}
*A minecart's initial velocity is not affected by weight, when pushed or launched from rollers.{{bug|6296}}
*Removing a stop that has a vehicle waiting on it may cause the game to crash.{{bug|5980}}
*Jumping out of a minecart in motion does not lead to injury.{{bug|10104}}
*Jumping into a stationary minecart can lead to significant injury.{{bug|10229}}

{{Gamedata|{{raw|DF2014:item_tool.txt|ITEM_TOOL|ITEM_TOOL_MINECART}}}}

{{Category|Fortress mode}}
{{Category|Interface}}

[[ru:Minecart]]

Minecart

2023-03-12T01:29:08Z

Xjtu-blacksmith: /* Simple tracks */ update build command

{{migrated article}}
{{Quality|Unrated}}
{{av}}

[[File:minecart_sprite_preview.png|right]]A '''minecart''' is a [[tool]] intended for [[hauling]]. It can be made of [[wood]] at a [[carpenter's workshop]] or 2 bars of [[metal]] at a [[metalsmith's forge]] (using the [[Metal crafter|metalcrafting]] labor.) Minecarts store up to five times as many items as [[wheelbarrow]]s and are quite a bit faster than dwarves hauling objects by hand, but have the disadvantages of requiring a dedicated track network, a complex route planning phase, and the possibility of dwarves [[Fun|blundering into the path of carts filled with lead ore]]. Tracks may be carved into stone, or [[Construction|constructed]]; the latter allows above-ground routes, but these are more difficult to set up due to their additional [[building material|material requirements]].

Just like wheelbarrows, minecarts are considered [[item]]s and are stored in a [[furniture]] [[stockpile]]. Despite their five-times-greater capacity, they are only 33% larger than wheelbarrows (minecarts have a size of 4000) and are identical in base [[item value|value]] when made from the same [[material]] (the value may differ due to the [[item quality]]). [[thief|Thieves]] or even mischievous animals can steal minecarts, even when they are moving on a track.{{cite forum|109460/3289070}} However, minecarts moving fast enough or being ridden cannot be stolen.

Although most of the utility of minecarts is in [[fortress mode]], an [[adventure mode|adventurer]] can also ride in a minecart. Adventurers can also pick up and relocate minecarts.

The invention of minecarts revolutionized the [[minecart logic|Science of Dwarfputing]] by enabling smaller, faster logic systems to be built.

== Basic Minecart Usage ==
[[File:Leitnagel Hund.png|thumb|Minecarts]]Minecarts can be used to swiftly transport dwarves, [[flow|fluids]], and/or large amounts of items, but before you have a functional minecart, there are several preconditions that need to be met. First of all, you need an actual minecart, constructed either in a [[carpenter's workshop]] or [[metalsmith's forge]]. For the minecart to be able to move, you also need to carve (with {{Menu icon|v|t}}) or construct (with {{Menu icon|b|n|k}}) a track, which could be as simple as a straight line. Finally, you need to construct stops on your track (with {{Menu icon|b|n|K}}) where the minecart will start and stop.

After you have created the stops and assigned a cart to the track, you must create logic routes connecting several stops and designate starting conditions for each stop. This is done with the {{Menu icon|H}} hauling key. The most basic conditions are how the cart's movement is initiated and in which direction the cart should start moving. Carts can be either pushed (a dwarf stands at a stop and gives the cart a single push) or guided (a dwarf continually pushes the cart forward, guiding it along the track). The [[hauling]] [[labor]] required for pushing and guiding carts is called "Push/Haul Vehicles" and is turned on by default.

To control which items are to be transported, you can add conditions specifying: (1) which kind of items are to be loaded and unloaded, (2) stockpile links to define which stockpile(s) the items should be un/loaded to and from.

===Capacity and weights ===
Minecarts have a [[Size|size capacity]] of 50,000 – five times the capacity of [[wheelbarrow]]s.

'''Examples of the capacity of one cart'''
{| class="wikitable"
|-
! Item
! Amount
|-
| [[stone]]
| 5
|-
| [[wood|log]]
| 10
|-
| [[block]]/[[bar]]
| 83
|-
| minecarts
| 12
|-
| [[Kitchen|prepared meals]]
| 500
|-
| [[Trap_component#Spiked_ball|spiked balls]]
| 500
|-
| [[Sand]] [[bags]]
| 500
|-
| [[Weapon#Native_weapons|mace]]
| 625
|-
| [[Weapon#Native_weapons|spears]]
| 1250
|-
| [[cloth]]
| 2500
|}

The weight of the loaded minecart does not affect the initial velocity received from pushing or launching from a roller.{{bug|6296}} However, the load of a minecart ''does'' affect whether a [[pressure plate]] triggers or not, based on the pressure plate's setting.

'''Weights of different carts'''

{| class="wikitable"
|-
! Type of cart
! Empty cart
! Fully loaded (items)
|-
| oaken minecart
| 28Γ
| 378Γ (10 oak logs)
|-
| iron minecart
| 314Γ
| 1698Γ (83 marble blocks)
|-
|-
| copper minecart
| 357Γ
| 1682Γ (10 obsidian boulders)
|-
| platinum minecart
| 856Γ
| 10482Γ (83 gold bars)
|}

The weight of a minecart is one twenty-fifth (1/25) the [[density]] of its material in Urists. Because pressure plates can be set to trigger at intervals of 50 Urists, minecarts with weights just under a multiple of 50 are ideal for switching based on whether they're full or empty. The best minecart materials for full/empty switching are as follows:

{| class="wikitable sortable"
|-
! Material !! Minecart weight !! Content weight required to trigger !! Banana roasts required to trigger (for scale)
|-
| [[Glumprong]] || 48 || 2 || 4
|-
| [[Electrum]] || 596 || 4 || 7
|-
| [[Nickel silver]] || 346 || 4 || 7
|-
| [[Brass]] || 342 || 8 || 14
|-
| [[Bismuth]] ([[Strange mood|moods]] only) || 391 || 9 || 15
|-
| [[Fine pewter]] || 291 || 9 || 15
|-
| [[Lay pewter]] || 291 || 9 || 15
|-
| [[Tin]] || 291 || 9 || 15
|-
| [[Trifle pewter]] || 291 || 9 || 15
|}

{{anchor|Tracks}}

=== Creating tracks ===
Minecart tracks are made up of contiguous track, tracked ramp, or bridge tiles. Track tiles and tracked ramp tiles have a direction or series of directions associated with them. These directions dictate which directions a minecart on a given tile may move from that tile. For example, a Track NE (northeast) tile allows a minecart on it to move either north or east from its present position. Therefore, if you want your minecart to move east along a straight piece of track, then return west using that same track, you would need to use EW tracks so that the cart could travel east initially, then return west over the same track. Excluding designs in which the cart will "jump" tracks via a drop or other ramp, tracks must be valid end to end to work for most looped or straight-track applications. A single east only track tile in your line of east-west tracks will cause any route using the track to fail the moment it tries to go the wrong way over that tile. Minecart tracks can be built in two ways: Engraved/carved or constructed. A given minecart track need not use engraved or constructed elements exclusively, as the two methods can be used interchangeably depending on the needs of a given section of track. The way the tracks are built is slightly different between the two, as explained below.

====Simple tracks====

'''Carved'''

A single-tile wide strip of natural stone can be designated to be [[Engraver|carved]] (with {{menu icon|v|t}}), which will create a straight two-way track. The creation of corners, crossings, and T-junctions is as simple as designating another strip of track that overlaps an existent or newly designated track. Engraved tracks are removed by [[smoothing]] the rock they're on, which results in a smooth floor (that can be re-engraved if necessary), or by building a [[floor]] on top and subsequently removing it. Dwarves can carve corner tracks in one pass by designating the track carving twice and canceling unwanted carvings (with {{K|d}} {{K|x}}). Tracks can be engraved in any natural floor tile, rough, smooth and even over engravings, providing an easy method to remove low-quality or undesired floor engravings. Once a track has been engraved, it's important to check the track directions for each tile in the route carefully to make sure no mistakes were made by yourself or the game's track engraving logic.

'''Constructed'''

Tracks can also be built as regular [[construction]]s (through {{menu icon|b|n|k}}. This method is resource-expensive, since each track tile requires one stone, [[bar]], or [[block]] for construction, and time-consuming, since you can't designate strips longer than 10 tiles at a time. Corners, crossings, T-junctions, and ramps also have to be designated individually. However, it is usually the only way to build tracks above ground or on soil (barring the [[Obsidian farming|creation of obsidian]]). Constructed tracks are designated for removal like any regular construction; be aware that removing track ramps built on top of natural ones will also remove the original ramp, leaving a flat floor.

====Ramps====

'''Carved'''

The carving of natural ramps is a little more confusing: to carve a two-way track on a ramp (natural only, does not work on constructed ramps), you must designate the track '''starting on the ramp and one square beyond''' in the direction you want the track to go. For the side of the ramp square you want to head upward, there '''must''' be either a natural or constructed wall in the square next to it, otherwise the game assumes you are trying to carve it on the same level – this can result in the track being carved underneath a door or other object. If you have accidentally done this, you can correct it by smoothing the ramp and constructing a single square of wall next to it, then re-carving the ramp correctly, however, the wall must stay there permanently — removing it will disconnect the track.

'''Constructed'''

The track and ramp must be constructed together as a Track/Ramp from the construct track menu ({{K|b}} {{K|C}} {{K|T}}). When constructing track ramps, the stated direction should be the same as the connected tracks. For example, a track going up from West to East would require, starting from the West, a Track (EW), a Track/Ramp (EW) and a Wall behind the ramp, underneath the section of track above it. Incorrectly placed ramps result in minecarts ignoring the ramp and crashing into the supporting wall. They will not, however, display as unusable as when the supporting wall is missing.

'''Examples of ramps'''

A simple ramp would look like this:
{{diagram|spaces=yes|\
z +0 z +1
░░░░ ░░░░
═▲o ░▼═
░░░░ ░░░░
o : wall
}}

Carving track corners into ramps is rather unintuitive and complicated. Since engraving tracks always requires two tiles to connect in a straight line as input, you have to give two separate designations for a single job: a track bit from the ramp tile to the "below" direction and another one to the wall of the "upward" direction. If you wanted to change direction on a ramp from east to north:
{{diagram|spaces=yes|\
z +0 z +1
░░░░░ ░░░░░
░░░░░ ══╗░░
══▲░░ ░░▼░░
░░░░░ ░░░░░
}}

you would need to connect the ramp on z +0 both to the west and to the north by issuing two "carve track" commands, one selecting the ramp and the track tile to the west, and another connecting the ramp tile with the wall to the north. An engraver would then carve a NW track corner into the ramp, allowing carts to pass the corner correctly both going up and down. Such track corners are perfectly serviceable for guided carts, but moving down a route of several of them by pushed or ridden cart is problematic - ramps on corners behave very counter-intuitively, resulting in loss of speed when going down and diagonal movement when going up.

Moving to and from ramps (or between ramps "pointing" in different directions) causes some non-trivial adjustments to speed and even moving along the tiles at a fixed speed ''unrelated to the entry/exit velocity values'', because transitions to/from ramps are processed differently and are not to be "skipped". This affects compact track/ramp combinations (such as e.g. a simple 2x2 ramp spiral) most, and combined with bouncing often makes them work not in the way one could expect. {{cite forum|144328/5705102}}

=== Hauling route ===
A hauling route is a list of directions describing how and under what conditions a minecart will move. The proper setting up of routes is essential for a working rail system. Routes, stops, departure conditions and stockpile links are managed from the {{k|h}}auling menu.

==== Route ====
A route defines the path a minecart will take along a track, as well as under what conditions it will move or stop moving. A route is made up of stops. Stops are precisely what they sound like, a position on the track at which you want a minecart to stop. A minecart track might use as little as a single stop for a looped track, which will serve as both a starting and stopping point for the cart, or it could contain many stops, perhaps to load supplies or wait for a bridge to be manually lowered, before reaching its destination or returning to its starting point. It is important to note that you only need to place stops on a route where you actually want the cart to stop and wait for some action to occur. They are not needed to help navigate the cart along the track beyond telling it where on the track to stop.

New routes are created with the {{k|h}}auling key. Existing ones can be removed (without confirmation) with the {{k|x}} key, and also {{k|n}}icknamed. Before operating, the route must have a {{k|v}}ehicle assigned to it (this can be done with either the route or a stop selected). Assigning a full minecart to a route may result in a slow hauling job if the contents are heavy.

==== Stops ====
Stops are the individual waypoints that make up a hauling route. A given stop consists of the location of a tile, as well as conditions describing when, where, and how a cart should be moved after being stopped at that tile. Stops can be created from within the {{k|h}}auling menu, by placing the cursor over a tile and hitting {{k|s}} while highlighting the route (or a stop within) you've already designated. A minecart will begin its route at the first stop created, and continue through each subsequent stop, being guided, pushed, or ridden from each stop to the next depending on the conditions specified. In many basic minecart applications, the cart will end up at the same stop it began at, though this is not always the case. It is important to note that hauling stop order is enforced, even if there is no track. A dwarf will drag the cart overland back to a skipped stop in the route's list if your tracks bypass it somehow, including if the minecart does not stop on the stop after it is pushed/ridden.

Once a stop has been placed, it is given a default set of conditions under which to move the minecart if it is stopped there. Each new stop gets the same default conditions regardless of the track it is placed upon (e.g. guide the cart to the north). For this reason new stops might get marked by yellow exclamation marks ({{DFtext|!|#ff0}}) due to invalid directions. One important thing to note is that as you place additional stops, the display will show paths between the stops you have defined. However, this is '''not''' necessarily the actual route the minecart will take once the route is in operation. For example, if a route were defined with two stops at opposite ends of a track with many twists and turns, a line will be drawn directly between those stops to show the order in which they will be visited. These route lines may crisscross all over the tracks, but so long as the track is valid end to end, the cart will follow the track from one stop to the next, even across twists, turns, and z-level changes. Route stops, which are the steps that make up a route, should not be confused with physical Track Stops, described below.

===== Stockpile links =====
By placing the cursor on top of a stockpile and using {{k|s}}, you can create stockpile links while defining a hauling stop. Links can also be redefined by selecting them, placing the cursor over a different stockpile, and pressing {{k|p}}. The cart will then be filled by items present in its various linked stockpiles in preference to other items. Note that bins should be used with caution in stockpiles that are linked to minecarts. Bins cause problems when used with the "Desired Items" list in a stop's conditions. For example, if a minecart is set to accept only granite blocks, and to depart north when it is 100% full of granite blocks, it will not depart if any of those granite blocks are in bins, even if bins are also included in the desired items list. Two solutions to this problem exist as of v0.40.24. First, bins can be disallowed in stockpiles that are linked to stops. Alternatively, bins '''can''' be used in conjunction with minecarts provided that the minecart's departure conditions use only "any items" instead of "desired items." This option can be toggled in the advanced conditions menu for a stop, accessible via the {{key|C|}} key. The cart's contents can still be controlled by specifying what items are allowed in the linked stockpile.

===== Departure condition =====
Departure conditions involve setting conditions in which the minecart will leave on the route. Each condition includes:
# A departure mode (Guide, Ride or Push).
# An initial departure direction (NSEW). Note that this defines the initial direction of movement only. Even if a track includes many turns, as long as the initial movement direction is valid the cart will follow the minecart track thereafter.
# A timer, before which the departure condition cannot be met.
# Conditions on the amount of items in the cart.
Departure conditions are created with the {{k|n}} key. A new departure condition will read: "guide north immediately when empty of desired items". This condition can be changed between basic presets with {{k|c}}. "Advanced" mode ({{k|C}}) allows for more precise control over departure conditions: fine tuning the percentage from 0 to 100 in 25% steps ({{k|f}} and {{k|F}}), switching it being either the maximum or the minimum amount of items for the condition to be met ({{k|m}}), and whether the cart accepts all or only a specific set of items ({{k|l}}). Common to both screens are the departure mode ({{k|p}}, Push, Ride or Guide), {{k|d}}irection, and timer ({{k|t}} and {{k|T}}) options.

To have a cart only carry a specific set of items, the stop can be set to only carry "desired" items, opening the selection screen with the {{k|Enter}} key while having said stop condition selected, and toggling as desired, or it can simply be linked to a stockpile and set to depart once it is full of items from its linked stockpiles, regardless of type.

=== Track Stops ===
A Track Stop, not to be confused with a route stop, is an optional, single-tile construction which serves two purposes. First, it can be used to cancel a cart's momentum in order to slow or stop it as it passes over the Track Stop. This might be necessary if a cart were pushed down a series of ramps to its destination. Second, a Track Stop can cause a cart to automatically dump its contents as it passes over the Track Stop. Track Stops are constructed via {{k|b}} {{k|C}} {{k|S}}, and must be constructed atop an existing piece of track. If a Track Stop has been set to automatically dump a cart's contents, the cart will dump its contents in the direction indicated when it passes over the Track Stop. Depending on the friction settings chosen for the Track Stop, the cart might then stop after dumping, or it might continue on its route to another destination.

Track Stops are not mandatory; in fact, their main use is in automated rail systems. However, even in basic rail systems it can be useful to set a Track Stop to dump items: this saves time that dwarves would otherwise spend in removing items from the cart, time that is better spent driving the cart back to where it's needed. Dumping will occur even with a guided cart. '''Take care not to set Track Stops at a loading site to dump their contents''', or dwarves will never be able to fill the cart. It will dump any contents the moment they are loaded.

Counter-intuitive to their construction method, Track Stops are considered [[building]]s and must be removed by {{k|q}} {{k|x}}.
* See [[#More_on_Track_stop |More on Track Stops]]

=== Step-by-step tutorial ===

Let's construct a simple minecart route. This route will move stone blocks from an input stockpile to an output stockpile. We'll begin by creating the stockpiles:

[[File:minecart-example-1-v50.03.png|200px|Stockpiles designated.]]

The input stockpile is on the left; the output stockpile is on the right. We'll be moving blocks from left to right. Disable bins in both stockpiles, and set the input stockpile to accept only from links. Then make the stockpile take from the mason's workshop where the blocks are being produced.

Next, carve the track:

[[File:minecart-example-2-v50.03.png|200px|Track carving designation.]]

Note that the ends of the designation are uniquely shaped; this is automatic, and not anything you need to control. Now, wait for your engravers to come along and carve the track into the stone. (Your haulers will probably also fill up the input stockpile while you wait.)

In addition, while we're waiting for that to happen, we'll build an iron minecart in the forge.

[[File:minecart-example-3-v50.03.png|200px|Track carved.]]

When the track has been carved, it will look like the above (the track will be solid instead of flashing). Now, order a track stop to be constructed (Under "Constructions") next to the output stockpile:

{|
| [[File:minecart-example-4-v50.03.png|200px|Track stop designation.]]
| [[File:minecart-example-5-v50.03.png|200px|Select dumping direction.]]
|}

You must select the dumping direction ''before'' placing the track stop. We want our blocks to be dumped into the output stockpile east of the track stop. Then wait for a mechanic to come along and build the track stop.

[[File:minecart-example-6-v50.03.png|200px|Track stop constructed.]]

Now we'll define the actual ''route''. This is done in the {{k|H}}auling menu. Press 'Add New Route' to begin defining a route. Select 'Add a stop' then click the track next to the input stockpile:

{|
| [[File:minecart-example-7-v50.03.png|200px|Route definition, in progress.]]
| [[File:minecart-example-8-v50.03.png|400px|Route definition, in progress.]]
|}

Select 'Add a stop' again then click the stop next to the output stockpile define the second stop:

{|
| [[File:minecart-example-9-v50.03.png|200px|Stop 2 designation.]]
| [[File:minecart-example-10-v50.03.png|400px|Route definition, two stops.]]
|}

At this point, the route has been positioned, but they haven't been ''defined'' yet.

Click the Minecart icon for the route (not the stop) and assign a minecart to the route.

Select the minecart icon for the first stop to select what items will be hauled to the minecart. By default no items will be hauled to the minecart. As we've set the input stockpile to only take blocks from the workshop, you can either set to to accept blocks, or set it to accept all items.

Click the stockpile icon for the first stop, select the "take from" icon (middle button) and select the input stockpile.

[[File:minecart-example-11-v50.03.png|350px|Set the stockpile.]]

Select the Conditions button ('''<>=≠''') for the first stop and check out the defaults. For the first stop, these are largely fine however you should change the direction button for all the conditions so the minecart goes the correct direction when it's ready.

[[File:minecart-example-11.1-v50.03.png|350px|Set the direction.]]

Select Conditions for the second stop. These need to be changed so the minecart is returned to the start immediately. Erase the bottom two conditions, change the direction to point back to the stop, and then finally click the '''>=''' button so it changes to '''<='''. This will make it so the cart is returned regardless of how full it is (which is good, as it'll always be empty!)

[[File:minecart-example-11.2-v50.03.png|350px|Fix the conditions for the second stop.]]

Once the minecart is in place, dwarves should fill it with blocks from the input stockpile, which will in turn be filled with blocks from the workshop where your mason has been toiling dutifully. When the minecart is full, the blocks will be dumped into the 1x1 stockpile on the right. Automatic quantum dumping!

If the route has any issues, you'll see a red ! on the minecart in the route screen. Be aware that this appears initially until the minecart is put in place. If your route is correctly set up, you will be dwarfs carry items to the cart and the percentage will change on the route screen.

{|
| [[File:minecart-example-12-v50.03.png|frame|Route with an issue.]]
| [[File:minecart-example-13-v50.03.png|frame|Cart correctly getting filled up.]]
|}

=== Troubleshooting ===

Because of the complexity of the system, all but the most careful and experienced minecart users will encounter issues. Most route issues can be diagnosed and fixed from the {{k|H}}auling menu.

'''Symptom:''' {{DFtext|! Set dir/connect track|6:1}} message appears to the right of one or more stops

:;Possible Causes:
:* Game cannot find a path for ''guiding'' the cart without carrying. The game checks for haul route validity assuming the cart will be guided. This warning will be shown when the path crosses impassable tiles, requires a dwarf to carry the cart, or is not fully guidable.
:** If your cart path relies upon advanced tricks like deliberate falling into pits or ignoring floor types, even a path designed entirely as you intended will still trigger the yellow warning. If the route is working as intended, you can safely ignore this warning.
:* Invalid departure direction in one or more conditions for the stop. Edit the stop using {{k|Enter}} and press{{k|d}} until it is pointing in a valid direction.
:* Track stop built on trackless tile. Track stops must be built on tiles where tracks already exist to be usable.
:* Discontinuous track. If the route indicator seems to draw between your first and last stop, this is the cause. Make sure destinations are linked by track to both directions, and that there are no sneaky gaps in the tracks.
:** ''Ramps''' are notorious for their finicky use. It is recommended to check every ramp to confirm no unintended one-way ramps remain.
:** To carve a two-way track on a (natural) ramp, you must designate the ramp ''and one square beyond'' in the direction you want the track to go.
:** Ramps '''must''' have a solid wall on the side opposite to the track ("behind" the ramp), or they will neither work nor be marked as "unusable". The wall can be natural or constructed.
:* Discrepancies in desired/kept item configurations.

'''Symptom:''' The status '''0% V''' always appears to the right of one stop.

:;Possible Causes:
:* Stop not set to take from a stockpile. Edit the Stop using {{k|Enter}} and make sure you see a message like "Take from Stockpile #1".
:* Take conditions and stockpile contents do not overlap.
:* Track stop is set to dump. A track stop set to dump cannot be filled. You must either set the stop to a time-based departure or deconstruct the track stop and rebuild it without dumping. (Alternatively, with [[DFHack]] you can modify "Dump on arrival" to "No" using the {{key|q}} menu without rebuilding the stop.)
:* Minecart itself is designated to be dumped (such as when using mass-dump).

'''Symptom:''' Dwarves fill the minecart properly, but will not move it thereafter.

:;Possible Causes:
:* Minecart contains items not listed as desired on its current stop. Check minecart contents using the {{key|k}} and {{key|z}} keys and ensure that all items in the cart are desired items.
:* Minecart contain desired items ''in bins''. Minecarts seem to have problems realizing that they are in fact full of desired items if some of those items are in bins, even if bins are also among the desired items for that stop. '''This cannot be solved by adding the appropriate bins to the stop's desired items.''' Either disallow bins in stockpiles you intend to load minecarts from, or set the departure conditions to rely only on percentage of total load rather than percentage of desired items using the advanced conditions menu ({{key|C}} key).

'''Symptom:''' Dwarves repeatedly attempt to load the minecart, but no items are ever loaded into it.

:;Possible Causes:
:* Track Stop set to dump used as a loading site. Every time a dwarf places an item into a cart resting on such a track stop, the item will be immediately dumped, causing unlimited, useless cart loading jobs. Autodumping Track Stops should never be used at a loading site.

'''Symptom:''' A dwarf picks up the minecart and carries it to its destination.
:* See [[#Quirks|Quirks]]

=== Danger ===
Minecarts are not without <strike>danger</strike> [[fun]]. Although designating a track automatically sets the [[traffic]] designation to low, dwarves ''may'' still walk on them, and [[creature]]s ignore traffic designations altogether. If an unlucky dwarf or creature fails to [[dodger|dodge]] a minecart, they can be injured. Most of this danger can be avoided by setting the minecart {{k|h}}auling commands to guide instead of push or ride (dwarves guiding minecarts will ignore traffic restrictions), as well as by [[pasture|pasturing]] domestic animals and preventing the access of other creatures to the tracks. Note that removing the track doesn't reset that tile back to normal traffic priority, so you may wish to manually clean up traffic designation afterward. Also note that bridges that are used as tracks don't have their traffic priority changed automatically (since they're just normal bridges), which could cause dwarves to pathfind normally through dangerous minecart entrances in your fort's walls if you're not careful.

The only <s>fool</s>''dwarf''-proof method is to make the tracks inaccessible. There are several ways to create a track which works for minecarts but doesn't allow creature-traversal; the simplest is perhaps building a [[statue]] on the tracks. Other options include adding single-tile holes (minecarts moving at reasonable speed will jump the gap), vertical drops, minecart-triggered doors, small pools of liquid (4/7 water or 2/7 magma), and hostile creatures overlooking the tracks. For safety, both ends of the track should be isolated, making the dangerous center sections completely inaccessible (though maintenance access can be provided by a locked door).

Danger does not always involve living victims: careless route designation can also result in minecarts careening off tracks or colliding with each other. If this occurs, the [[item]]s may be scattered; this can cause even more hauling jobs than the minecart aimed to eliminate. Even <s>better</s> worse, scattered items, especially [[weapon]]s, can injure passing [[dwarf|dwarves]] or other [[creature]]s; in the words of Toady One the Great, "Accidental grapeshotting of the dining room should be possible now."

Of course, the danger of using minecarts means they can also be [[Trap_design#Minecarts|used as weapons]] by imaginative players.

== Advanced usage and automation ==
Minecart-specific effects are implemented via track stops, rollers and [[pressure plate]]s with "track" condition set. Since all three are considered [[building]]s, they can't be built on the same square (however convenient track stop + pressure plate would be) nor a simple ramp, and are removed by {{k|q}} {{k|x}}.

=== More on Track stop ===
Track stops are constructions that allow further automation of minecart systems via adjustable features such as braking by friction and automatic dumping of contents. They can be built from logs, bars and blocks through {{K|b}} {{K|C}} {{K|S}}; friction amount, dumping toggle and dumping direction must be set '''before''' construction, and these settings can be neither changed nor seen thereafter*; however, track stops can be linked to [[pressure plate]]s or [[lever]]s to toggle friction and dumping On or Off (trigger state is inverted: switch On = track stop Off). In thoughts screen, dwarves will admire track stops as traps.

*Note: As of v0.47.05, the friction and direction settings '''can''' be adjusted after the track stop has been constructed. The stop can be {{K|q}}ueried to show the settings as they were set prior to construction, and two options will appear that allow the settings to be changed. The friction amount can be decreased or increased by pressing {{K|a}} or {{K|s}} respectively, cycling from "Lowest" to "Highest". The direction to dump can be toggled through the four cardinal points by pressing {{K|d}} until the desired direction is selected.

If a [[stockpile]] is placed on the tile that a track stop is set to dump to, it can act as a [[Exploit#Quantum_stockpiles|quantum stockpile]] and any items dumped from a minecart that match the storage settings of the stockpile will remain there and accumulate. Normally track stops are built on top of existing track to operate on moving minecarts, but they can also be used without tracks to create [[Quantum_stockpile#The_Minecart_Stop|automatic quantum stockpiles]] (see also [[#Step-by-step_tutorial|step-by-step tutorial]]). It is not always desirable to collect ALL of certain items into one quantum stockpile, such as when distributing a material to multiple separate industries. You can link your quantum stockpile to various other stockpiles, ensuring that your dwarves will keep them supplied as necessary. Because quantum stockpiles never fill up like regular stockpiles, it may be a good idea to add a switch to turn them off.

Items dumped from a minecart at a track stop (or dumped by any other means) into open space fall through z-levels until they land on a solid surface. Items falling onto a designated [[stockpile]] will automatically be considered part of that stockpile, even if the stockpile is set to disallow those items (they will, however, be automatically moved to a more appropriate stockpile, if available). Items falling on top of a minecart will '''not''' fall "inside" the minecart. Use with caution; dwarves have fragile skulls.{{bug|5945}}

=== Automated propulsion ===
==== Roller ====
{{Main|Roller}}

A '''roller''' is a [[power]]ed [[machine component]] for the automated propulsion of minecarts. They are built over the top of existing tracks with {{K|b|M|r}}, requiring a [[mechanic]], ''(length/4)+1'' [[mechanism]]s and a [[rope]]. Rollers may also be placed directly on ramps to help pull carts up Z levels. Rollers are very useful to maintain a cart's momentum along long routes, to get them to climb Z-levels without dwarfpower involved, and to get them to reach speeds unattainable by guiding dwarves. These devices are variable-length (1-10), variable-direction and variable-speed ([[Minecart#Numbers_behind_the_scene|see below]]), all traits that can be set at construction time; a roller uses two units of power per tile it is long.

Single-tile rollers transfer power in all four cardinal directions, while other rollers generally only transfer power perpendicular to their activity direction. Longer rollers can also transfer power along their activity direction if built in the correct order, although this can be hard to accomplish and is easily broken. Rollers cannot be powered from above.

Rollers have great acceleration and capped speed. Carts going faster than the roller are unaffected. If a cart moves across an active roller in the direction the roller works and moves slower than the roller's specified speed, the cart will be set to the roller's speed. A cart going against a roller's movement direction will be sent back the way it came (once again at the roller's speed), unless it was moving extremely fast: speed increment of 100000 allows to reverse carts from the full "highest" (50000) speed roller to full "highest" speed back, but ramps can accelerate a cart beyond this. {{cite forum|144328/5702453}}
A cart crossing over a roller perpendicular to its current movement direction will gain the roller's amount of speed in the perpendicular direction without directly changing its forward motion. Without an adjacent wall to constrict its movement, this will typically send a cart off the rails on a diagonal path, completely unable to follow any tracks until it collides with a wall or is otherwise brought to rest. However, if the roller is placed over a track turn and pushes ''from'' the direction of that turn's track, the turn affects carts ''after'' the roller, so they will be forced into the turn rather than derailed in a diagonal direction. {{cite forum|144328/5702453}}

{{diagram|spaces=yes|\
tracks: full:
║ ║
═╗═ ═╢═
║ ║

╢ : roller pushing from W to E
}}
If the roller is powered, carts from ''all'' directions (unless too fast) exit S, because speed imparted by the roller forces carts toward E and ''then'' into the turn.
If not powered, carts from W and N exit S, carts from E and S exit W. Carts above derail speed will ignore the turn, of course.

{{diagram|spaces=yes|\
║ ║
═╗═ ═╟═
║ ║

╟ : Roller pushing from E to W
}}
Carts from the E or W: exit W.
Carts from N: derailed diagonally, exit SW.
Carts from S: derailed diagonally, exit NW.

Rollers affects carts on a track - if placed on a floor or ramp without any tracks, they are ignored. Depowered rollers are also ignored, friction is determined by the tiles underneath.

Because of their one-way nature, rollers are unsuitable for most two-way minecart tracks (unless you set gears toggling roller A->B off while toggling A<-B rollers on). However, a minecart set to be ''guided'' is not affected by rollers at all{{cite forum|109460/3286235}} — this allows a one-way track to be used in both directions. In addition, unpowered rollers do not affect minecarts.

Care must be taken in [[glacier]]s and other extremely cold [[biome]]s, since rollers (and the machinery used to power them) will not operate when constructed on natural [[ice]] floors.

==== Impulse ramps ====
Carts can be given momentum without rollers or changing z-level by exploiting a design oversight in a phenomenon called "impulse ramps". A track ramp which has at least one wall/fortification and exactly one other connection will ''always'' accelerate a cart towards the other connection, no matter where the cart enters the tile from. This means carts can be accelerated even if the cart doesn't actually change z-level at all; ramps don't actually impart any downward velocity even when making cart descend. If a track ramp faces three directions such as ╩, then two of those directions need to be facing walls for the cart to be accelerated towards the remaining direction.

Example of straight impulse acceleration:

{{diagram|spaces=yes|\
▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒
═▲▲▲▲▲▲▲▲▲▲═ ═╚╚╚╚╚╚╚╚╚╚═
▒ : Wall
═ : Normal track
▲/╚ : N/E Track/Ramp
}}

If a cart enters from the left, it will speed up on every track/ramp and exit to the right going very very fast—more than one tile every step. If it enters from the right, then it will bounce back impulsed by the ramp if it's going slow enough.

As another oddity, carts coming from ramps will in some cases "teleport" through most of the next tile. This is called the "checkpoint effect", and is explained in detail in the Physics section, below. This negates the deceleration of the next tile if it is a ramp "angled" in a different direction. You can just make an upward spiral alternating impulse ramps and regular upward ramps. It takes no power, is quick and cheap to build, requiring only channeling and track carving, and the cart goes up fast, but not so fast that it launches its contents.

Examples of impulse elevators:

{{diagram|spaces=yes|\
z +0 z +1 z +2 z +3
░░░░░ ░░░░░ ░░░░░ ░░░░░
░╔░░░ ░▼╚╗░ ░░▼▼░ ░░░░░
░╝░░░ ░▼░░░ ░░░╔░ ░░░▼░
░▼▼░░ ░░░░░ ░░░╝░ ░╚╗▼░
░░░░░ ░░░░░ ░░░░░ ░░░░░

z +0 z +1 z +2 z +3 z +4 z +5 z +6 z +7 z +8 z +9
░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░
░▼░░ ░░╗░ ░╔▼░ ░▼░░ ░░░░ ░╔╝░ ░▼▼░ ░░░░ ░░╗░ ░╔▼░
░╔╝░ ░▼▼░ ░░░░ ░╚░░ ░▼╝░ ░░▼░ ░╚░░ ░▼╝░ ░░▼░ ░░░░
░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░

░ : Wall
╔,╚,╗,╝ : Track/Ramp
▼ : Down Ramp (empty space)
}}

Note that these impulse elevators, due to the checkpoint effect and upward curved ramp effect, will not actually result in carts traveling straight up the ramp. They will lose speed, bounce off a ramp, then be accelerated back into the spiral after a 9-turn delay on both tiles on the floor where they are stopped. This is because the checkpoint effect allows carts to travel up the ramps in a single turn, but also prevents the impulse ramps from adding acceleration unless the cart is slowed to staying on the ramp for more than one turn. Initial acceleration will carry the cart up a variable number of floors before this effect occurs, but this bouncing back and forth will occur every 5 z-levels after the first time the cart stops. When the cart ''is'' traveling upwards, it will pass every tile at a rate of one tile per turn regardless of its actual speed, due to the checkpoint effect. In tracks with only a single cart, this is negligible, but when multiple carts are on the same track (such as when you place multiple carts on a magma cart lift) this can cause collisions which derail carts, or cause other unexpected or undesired behaviors.

The following impulse ramp (while larger) should alleviate these problems by using a straight ramp to go upwards, preceded by an impulse ramp to exploit the checkpoint effect and negate up ramp costs. Corners still decelerate carts, so the cart will tend towards a velocity of 72k, which is derail speed. Derail speed breaks (see Controlling Speed, below) may be necessary at the top.

{{diagram|spaces=yes|\
z +0 z +1 z +2 z +3
░░░░░░ ░░░░░░ ░░░░░░ ░░░░░░
░░░░░░ ░╔╔═░░ ░░▼▼╗░ ░░░░░░
░║░░░░ ░▼░░░░ ░░░░╗░ ░░░░▼░
░╚░░░░ ░▼░░░░ ░░░░║░ ░░░░▼░
░╚▼▼░░ ░░░░░░ ░░░░░░ ░░═╝╝░
░░░░░░ ░░░░░░ ░░░░░░ ░░░░░░

░ : Wall
║,═,╔,╚,╗,╝ : Track/Ramp
▼ : Down Ramp (empty space)
}}

Also, if you want to have a cart following a below-derail speed, the following track works well:
{{diagram|spaces=yes|\
z +0 z +1 z +2 z +3
░░░░░ ░░░░░ ░░░░░ ░░░░░
░░░░░ ░══░░ ░▼▼║░ ░░░▼░
░║░░░ ░▼░░░ ░░░║░ ░░░▼░
░║▼▼░ ░▼░░░ ░░░░░ ░░══░
░░░░░ ░░░░░ ░░░░░ ░░░░░

░ : Wall
║,═ : Track/Ramp
▼ : Down Ramp (empty space)
}}
In this elevator, the cart collides with the walls in the corners, but then realigns on the ramp, picks up speed, checkpoints through the next ramp, and slams into the next wall. It is slower (10 ticks per floor) but produces reliable speeds, and will exit the impulse elevator at little more than push speeds.

A sort of opposite effect to impulse ramps also exists: ramps lacking the proper "up" and "down" connections are treated as flat track, even if they actually go up or down z-levels. This allows building "anti-impulse" slopes consisting entirely of ramps only connected up, which a minecart can travel up forty levels and more, needing no more than a single push.

=== Controlling traffic ===

==== Switching ====

As tracks are constructions or tile features, [[door]]s and other furniture can be built on them. A [[door]] or [[floodgate]] can be turned on or off by a [[lever]], effectively controlling the flow of automated minecarts. This may be <s>dangerous</s> [[fun]], however.
{{diagram|spaces=yes|\
->
A ════┤≡════ B
┤ : roller pushing to East
≡ : door
}}
The roller pushes the cart east, but until the "departure condition" is fulfilled, the door remains closed and blocks the path.

[[Bridge]]s can also act as tracks, but only if they're lowered or not retracted. This property can enable levers to turn tracks on and off. However, care should be taken to ensure that such bridges are never operated while a cart is on top of them, as the cart will be flung off the track. It's worth noting that it's often faster, and cheaper, to construct large bridges than long sections of constructed track.

A powered track switch can be constructed by building an "inverted" corner as illustrated below.
{{diagram|spaces=yes|\
B B
║ -> ║
║ ║
════╚═══ ════├════
A C A C
├ : roller pushing to West.
}}

If the cart is pushed East from the stop at 'A' while the roller is activated, it will arrive at 'B'. If the roller is not running, it will arrive at 'C'. The switch works by the roller first reversing the incoming cart's movement and the cart ''then'' following the track corner.

This switch is very reliable, reacts instantly to on/off signals, and carts of any speed can be switched by this design, although very fast carts will require rollers that are several tiles long, up to three. The requirement for power can be inconvenient or impractical. Non-powered solutions may use controlled derailment, or a connecting bridge.
{{diagram|spaces=yes|\
B ╥
║
║
╞════╝ ════╡
A D C
}}
Here the track between A and C is not continuous. The only continuous track is A->B, with a corner (not a T section). Fast moving carts will tend to derail at D and rejoin the track to C. Placing a door at D will prevent the derailment, so the cart continues to B. The door is operated by mechanisms elsewhere (typically, a lever, but some fun can be had with pressure plates).

Since it depends on derailing, this switch requires a very fast cart, faster than what can be achieved with rollers alone. To gain sufficient speed, a cart must be accelerated further, usually by descending several levels or through impulse ramps. The high speed makes the cart much more dangerous and harder to control.

If carts are moving too slowly to derail at the corner, a retractable bridge may be used as a connector between A and C.
{{diagram|spaces=yes|\
B╥
║
║
A╞════bbb════╡C
}}
The bridge must overlap the corner. Bridges behave like a track crossing, allowing carts to pass in a straight line. When retracted, the corner reappears, so the carts will continue to B. Bridges take 100 steps to react to a signal, necessitating rather long "lead times" when switching tracks via bridge.

As mentioned above, special care must be taken to make sure the bridge doesn't change state while the cart is passing over it. Retracting bridges will throw the cart, causing it to stop dead. Raising bridges can even crush the cart.

==== Controlling Speed ====


Minecarts can reach extremely high speeds, especially when descending multiple Z-levels. A minecart will derail at a track corner if its speed exceeds 0.5 t/st (tiles per step), '''unless''' the route in the direction of travel is blocked:

Will derail at > 0.5 t/st:

{{diagram|spaces=yes|\
in ══╗ -> derailing
║
out
}}

Will not derail at > 0.5 t/st:
{{diagram|spaces=yes|\
in ══╗O
║
out

O : wall/column.
}}

This behavior can be used to build a "speed limiter", that will ensure that when a minecart exits it is traveling below derail speed, as illustrated in these three examples:
{{diagram|spaces=yes|\
░░░░ ░░░░░ ░░░░░
in ═╔═╗░ ░╔S╗░ ░╔S╗░
out ═╬═╝░ out ═╗═╝░ out ═╗═╝░
░╚S╝░ ░╚═╝═ in ░╚S╝░
░░░░░ ░░░░ ║░░░
in
░ : wall
S : Track Stop (High Friction or lower)
}}
If the minecart is traveling below derailment speed, it will not be affected; if above, will be slowed down and checked again. Granted, you could do the same just with track turns, but it may take a lot of turns and time.

Since all the derailings, bounces and ramps can impart a sideway component of speed small enough to start visible drift many tiles away (say, [[Fun|in the middle of a bridge]]), track turns have one more use: forcing the carts to move strictly along the grid directions. Carts passing a turn below derailing speed convert one component of velocity into another, thus eliminating the drift.

=== Loading liquids ===
[[Water]] and [[magma]] can also be loaded into minecarts by submerging them to a depth of at least 6/7 while standing still or moving at speeds of at most 10000. Loading fluids onto minecarts can be difficult because the added friction provided by fluids can stop a cart in a submerged tile. Curiously, filling a minecart with magma does not injure a dwarf ''riding'' it. A minecart will hold enough fluid to increase the depth of a single tile by 2. This amount is listed as 833 units, which weigh 459Γ (water) or 999Γ (magma). An iron or steel cart filled with magma weighs 1313Γ, while an adamantine cart filled with magma weighs 1007Γ. Since you need a minecart above the liquid's level, possible arrangements may include pressure-activated sluices, rollers (with magma-safe chains for magma), pouring from above to "submerge" it briefly on the same level and drain excess away (dig deeper and leave a vaporizer, though if you could have power for rollers, may as well use a pump) and exploits with ramps (not necessarily impulse ramps, "same height" passing dip does it).
The liquids can be dumped by a constructed track stop.

== Quirks ==
This little quirk concerns dwarf-managed minecarts. If a track which was previously open becomes blocked (ex. flipping a switch connected to a floodgate you've built on the track to raise it) and the conditions for departure are met, instead of refusing to ride/guide the minecart or ride/guide it until it reaches the obstacle, the dwarf will pick up the minecart off the tracks and haul it to its scheduled destination on foot. If the distance is long enough and the weight of the cart heavy enough (due to being filled with heavy items such as stones), the dwarf may drop the cart because of fatigue/hunger/thirst before reaching the destination. This will cancel that vehicle setting job and make another dwarf come by and attempt to haul the cart to the nearest appropriate stockpile where another dwarf will pick up the cart and attempt to haul it to its initial stop. If the stockpile is far enough from initial stop, this second dwarf who is attempting to place the minecart on its tracks may also drop the minecart out of fatigue/hunger/thirst creating a loop that will go on until a dwarf with enough endurance manages to place the minecart where it belongs.

In fact, it seems dwarves are more than happy to attempt to carry a minecart from one stop to another even if just waiting until the track is open again would be the more sane option.

Dwarves will also carry a minecart to its next stop if the direction specified is incorrect (or invalid). This can often occur when using the default departure settings and forgetting to set the direction of each condition.

Dwarves can admire buildings while riding mine carts. Dwarves will not fall asleep during a ride (at least not from being drowsy). If riding on a continuous powered track loop, the dwarf will die of dehydration/starvation as they can not jump off to get sustenance.{{cite forum|109460/3377228}} Dwarves riding in submerged minecarts will gain experience in [[swimming]].{{cite forum|129889}}

Tracks block wagon access to trade depots, unless they're on a ramp. [[Bridge]]s can also be used, as they function as tracks but do not block wagons.

== Physics ==


Minecart physics depend greatly on the departure mode set in the route stop conditions.

When set to "Push" or "Ride", minecarts will move according to the regular laws of momentum, gaining speed when going downhill, losing it slowly due to friction when on a flat plane, and more quickly when going uphill. In these modes, minecarts will move in a straight line until they either are brought to a stop by friction or an obstacle, or until they encounter a turn. A minecart will roll straight past "blocked" ends of T-junctions or track ends, they have no power to restrict a cart's movement. The cart's behavior is largely independent of the weight of its contents (including fluids and dwarves): heavily loaded carts gain more momentum when accelerating, but this only plays a role in collisions: a heavy cart gains just as much speed and is as easy to stop as a light one. In either case, dwarves can not push nor ride an unpowered cart up a ramp, bouncing back the direction it came. At best, this is a waste of time; at worst, it will give your cart-pushing dwarf a [[fun|fun surprise]]. To solve this, the player can either use Rollers (see below) or set the cart to be Guided.

The difference between "Push" and "Ride" is whether the dwarf will go along with the cart or not.
{{DFtext|Push}}: the dwarf will give the cart an initial push, not enough to go up a ramp, but enough to go some way along flat track, and the dwarf will remain at the first stop, ready for a new job.
{{DFtext|Ride}}: the dwarf will give the cart the same initial push and then hop aboard the cart riding with it to the next stop.
{{DFtext|Guide}}: minecarts seem to ignore all laws of physics. That is:
*Ignore the weight of any and all items inside. Therefore:
**Move at the speed of the dwarf that is guiding them. It is thus recommended to pick the most [[attribute#Agility|agile]] of your dwarves for cart-guiding tasks.
*Ignore working rollers.
*Will ''not'' collide with other guided carts even when a full frontal collision would be expected.
*Will go up ramps like nobody's business.
This is therefore the recommended method of transport for simple non-powered rail systems, despite it diverting a dwarf from other, potentially more important tasks.

Some samples with behavior:
{{diagram|spaces=yes|\
A <-> B A <-> C A <-> B
B B B
║ ║ ║
A══╝ A══╩══C A══╬╗
You can only go A->B ╚╝
Works when the cart Works
is in Guide mode.
}}
In the second example above, a cart "pushed" from B will go over the junction and roll off into the unknown south.

=== Numbers behind the scenes ===

According to early research by '''expwnent'''{{cite forum|112831/3536975}}:

The minecart has 3 variables for velocity. Velocity can be thought of as tiles per 100000 ticks, so a velocity of one hundred thousand means a cart travels one tile per tick. By going down a large number of ramps, a maximum velocity of 270,000 can be reached, which presents the limit for most practical applications. Short bursts of (much) higher speeds are possible through carefully planned collisions of high-speed carts.{{cite forum|137557/5145499}} (See [[#Perfectly Elastic Collisions|Perfectly Elastic Collisions]].)

Every tick the cart adjusts sub-tile position units by the amount of their velocity, as well as adjusts velocity depending on current tile (speed is reduced by the "friction" of the tile, or accelerated if going "down" a ramp). On flat (non-ramp) tiles, the cart will move to the next tile when the sub-tile position goes 50000 away from the centre of the tile, denoted by the no-fraction integer value - tile 15 e.g. has its centre at the exact value 15 and its borders at co-ordinates 14.5 and 15.5.

Since most deceleration and acceleration is applied per step, with the notable exception of corners, a cart going at twice the speed of another one can travel about four times the distance before coming to a stop when going in a straight line, but only twice the distance along a winding track with very many corners.

A push will teleport a cart to the middle of the next tile in one tick with 19990 speed (10 speed is lost due to track friction), while a roller will directly give a cart the roller's set speed (minus friction) and the cart starts accumulating distance from its standing position. When a cart leaves a ramp it will emerge after one tick at the very end of the next regular tile.

Friction of tiles:
{| class="wikitable"
|-
! Tile
! Friction
! Comment
|-
| Tracks
| 10
|-
| Ground/Floor
| 200
|-
| Unusable ramp
| 10
|-
| Upwards ramp
| 4910 (10+4900)
|-
| Downwards ramp
| -4890 (10-4900)
|-
| Roller
| ±100000 (but capped by the set speed)
|-
| Corner track
| 10
| Speed reduced by 1000 upon leaving the corner tile
|-
| Track stop (highest)
| 50000
|-
| Track stop (high)
| 10000
|-
| Track stop (medium)
| 500
|-
| Track stop (low)
| 50
|-
| Track stop (lowest)
| 10
|-
| Water 1-6
| Additional (WaterLevel - 1) * 100
| rowspan="2" | [[#Skipping|See Skipping]]
|-
| Magma 1-6
| Additional (WaterLevel - 1) * 500
|-
| Empty space
| 0
|}

Water of depth 7/7 provides a friction of about 10000 per step. Maximum-depth magma causes at least as much friction, possibly more. This higher friction may not apply to very slow-moving carts.

Impulse sources:
{| class="wikitable"
|-
! Feature
! Speed
|-
| Push
| 20000
|-
| Roller lowest
| 10000
|-
| Roller low
| 20000
|-
| Roller medium
| 30000
|-
| Roller high
| 40000
|-
| Roller Highest
| 50000
|-
|}

Note, again, that nearly all of these values are applied ''per tick'', rather than ''per tile''. The exceptions are curves, which is 1k deceleration per direction change at the end of the tile, and rollers, which ''set'' the speed every tick. This makes rollers particularly useful in high-deceleration situations, such as underwater, but require that ''nearly every tile'' in such high-deceleration situations have a roller.

A cart heading up a ramp can experience deceleration on multiple ticks, (and stays on the tile more ticks the slower it is going, resulting in greater deceleration,) and as such, a cart leaving a "Highest Speed" roller with 50k velocity will not be able to climb 10 consecutive straight ramps, since they are ''not'' "5k deceleration each". In fact, the first ramp not on a roller will be -15k velocity, and, depending slightly upon other factors of "remainder" x position, the second may completely cancel forward momentum, and send it rolling back down, where it will bounce off the roller repeatedly. Using rollers to power carts up ramps reliably requires rollers every other un-rollered ramp. Fortunately, rollers can be built upon ramps, themselves, which allows for rollers to only need to be built every other floor. (Exploiting the [[#Checkpoint Effect|checkpoint effect]] can allow one to bypass this requirement.)

There are two important speed values which affect carts' behaviour:

"Derailing" can happen when a cart moves at speeds in excess of 50000 - carts will ignore track corners unless forced to obey them by walls or other obstacles blocking the straight path.

The "shotgun" effect takes place when a collision changes a cart's movement speed by more than 55000: loaded carts subject to such a change eject their contents, which then keep on moving in a ballistic trajectory, in the direction and at the speed the cart had before the collision (with a small random vector added). This effect entirely rides on the amount of speed ''change'' - a speeding cart crashing into a wall can be subject to it just as well as a standing cart accelerated by a speedy cart smacking into it. It can even happen when two relatively slow-moving carts (down to speeds below 20000 in extreme cases) collide head-on.

=== Sub-tile Positions and Velocity ===
Carts store six values that are unique to them. Three sub-tile position values, and three velocity values. (X, Y, and Z.)

Note that the Z position and velocity only matter when a cart is in flight. (See [[#Falling|Falling]] and [[#Cart Jumps|Cart Jumps]].)

Each non-ramp tile is functionally composed of 100,000 individual minimal-length positions ''within'' the tile in both dimensions. When a cart has velocity, it is added or subtracted from the current position every tick, and then a friction force is applied to the cart.

In essence, every sub-tile position unit is a decimal value of a tile, 0.00001 tiles, in a game that largely prefers integer values.

The exact cart coordinates shown e.g. by a DFHack script must be rounded arithmetically (up or down to the nearest integer) to find the current tile: a cart in the centre of a tile will be at sub-tile zero in all directions, and it will cross into the next tile when subtile value is more than 50 000 higher or lower than the full number.

When carts move beyond the borders of a tile, they physically move a tile on the map, and start at the far end of the sub-tile position the next tile. (I.E., traveling West, a cart that starts a tick 15,000 X away from the border and has an X velocity of -20,000 will move -5000 X past the adjacent border of the next tile in direction -X. It will also lose 10 velocity in that tick due to friction with the track if it is on a track, or 100 velocity if it is on regular ground, or no velocity if it is airborne.)

Ramp tiles are longer, approximately 141,420{{cite forum|157627/0}} in the direction where it "slants downward", (to approximate a 45 degree slope, it is square root of two times longer,) with a centre-to-border distance of 70,710. Because of this, a cart with no velocity dropped from a hatch will land at the center of a tile, 70,710 away from the tile's borders in both directions, and will start rolling in the ramp's "downward" direction, picking up the ramp's acceleration (4890 per tick in the direction of the ramp's "downward" direction) every single tick, then moving that sub-tile amount every tick. (This results in a cart that takes 5 ticks of acceleration to leave its ramp - 6 ticks overall - and to leave the ramp with about 23k velocity, slightly more than a push.) When it enters another ramp ''facing the same direction downwards'', a cart will start at the -70710 or +70710 position, and have twice as far to travel. This means that if a cart enters a ramp from the side, it will gain twice the momentum of simply starting at the midpoint of a ramp.

Note that passing from one direction of ramp to another or to flat terrain causes unintuitive behavior, "teleporting" to the end of another tile in what is called the "[[#Checkpoint Effect|checkpoint effect]]".

Note, however, that all sub-tile positions are carried over from tile-to-tile. This separate tracking of velocity and position between X and Y can lead to problems with diagonal motion:

{{diagram|spaces=yes|\
z0 z-1
▒║▒ ▒▒▒
═▼═ ▒╬▒
▒ ▒ ▒║▒
▒ : Wall
═, ║ : Track
╬ : Track and Ramp
}}

If a cart is passing West-to-East over this setup, the valid ramp to the South will apply "Southward" acceleration to the cart (-Y velocity) as it passes through the ramp tile. Assuming it only spends two ticks in that tile, it will have gained a lasting -5k Y velocity, which will still apply motion Southward. If the cart continues travelling over straight track for another ten steps, it will have accumulated enough Southward motion to try to move a tile South, even if all tracks are facing East-West.

A single tile spent on the ramp will not grant lasting southward motion, because the acceleration will be neutralised through the checkpoint effect when the cart leaves the ramp again, but the cart will be displaced about 5k sub-tiles southward, which can cause it to gain more or less speed than an undisplaced cart when meeting another south- or north-accelerating ramp.

'''Non-curving tracks do not correct this motion'''.

They don't "tip back over" without adjustments in the track. Any value of sideways motion on tracks larger than 990 will lead to a derailment. (Lower values will be nullified by friction before they are enough to lead to derailment, but there is currently no way to apply such a small amount of velocity.)

If the tile to the South is a wall at that point, it will be considered a collision with a wall that ''halts all motion''. If the tile is open, the cart will simply leave the track and travel over the terrain beside it. In almost any circumstance, this is undesirable behavior.

The only way to appropriately deal with this is to either cancel out this behavior with an equal amount of acceleration in the opposite direction, or to take a curve.

Note, again, that sub-track position is saved in both directions, so when a cart approaches a curve, it will already have a shorter or longer distance past the curve when it makes the turn.

Curves are applied at the end of a tile. If a cart is moving East, and approaches a North-West track corner at 30k velocity, and friction is eliminated for the purposes of a cleaner demonstration, then when it enters the tile on the western (X coordinate) border of the tile, but in a central North-South (Y) orientation (sub-tile -50k X and 0 Y due to arithmetic rounding), it will then move 30k East (+X) the next tick, and be at -20k X sub-tile position, and 0 Y sub-tile position. Next tick, it is at +10k X sub-tile position, and 0k Y sub-tile position. Two more ticks would take it to +70k X, but that's past the tile border, so it stops at 50k, turns (and thus loses 1k velocity, but translates the rest from X-velocity to Y-velocity) and travels another 20k. It is now at 0k X sub-tile position, and -20k Y sub-tile position (i.e. it's re-set from the end to the middle of the tile with respect to the X co-ordinate). Next tick, it travels at 29k velocity North, and so moves to 0k X sub-tile position, and +9k Y sub-tile position. Then in two more turns, it leaves to the North.

In the case of diagonal motion due to having velocities in X and Y at the same time, it is critical which tile the cart actually tries to enter next. Only if the path into that tile is blocked by the corner branches will the cart take the corner and rewrite its velocity, otherwise it leaves the corner tile without changes to its motion. If the cart is redirected by the corner, all sideways velocity is lost, as forwards velocity ''overwrites'' sideways velocity in a curve. If, in that example in the paragraph above, the cart entered at -50k X sub-tile position with 30k X velocity, and 40k Y sub-tile position and -1k Y velocity, it would take that "curve" (or rather, redirection of velocity) on the fourth turn, while it is at 37k Y sub-tile position to start with, and then move to -53k Y sub-tile position at the end of that tick. It would then move to -26k Y sub-tile position in the following turn, and take 3 turns to clear the tile.

But, most importantly, it would be centered in the X sub-tile position, and all sideways velocity is safely removed.

There are two common ways to gain sideways velocity: Rollers facing perpendicular to the cart's travel path (which, as covered above, are almost always a bad idea, as it is easier to push ''against'' the travel direction of a cart into a curve, which redirects all velocity in the new direction,) and [[#Corner Ramp Derail|corner ramps]], and require a curved track to compensate for sideways velocity within a few tiles.

=== Track Direction Irrelevance ===
Carts that are traveling independently (that is, not guided) only care that tracks ''are'' on the tile, not which direction the tracks actually move. Tracks respect only curves (with two exits) and ramps.

This means, for example, that the following tracks, when a (non-guided) cart travels from West-to-East, are functionally identical in effect:

{{diagram|spaces=yes|\
A════════════B A╬║╚╔╣╩╦╠╥╨╞╡B
}}

This is because so far as the cart is concerned, only valid ramps and curves with two exits where there is no exit in the path they are traveling matters.

Hence, if a minecart encounters the end of the track or a T junction with no "exit" in its movement direction, it will simply leave the track and continue on its course in a straight line until it encounters an obstacle, slows to a stop, or encounters another track even if the tile at which it joins the new track instantly sends it around a corner.

In fact, in a track designed for pushes or rides, a "║", a "╦", a "╬", and a "╥" are ''only different in appearance'', and are ignored by an unguided cart, which will continue in its current direction, regardless of the track. For any purpose but guided tracks, ''only curves and ramps matter at all''.

Tracks like T-junctions, however, ''are'' respected by dwarves guiding carts, who will lift and carry carts if they cannot find a valid track to their destination, and can choose to follow any orthogonal direction at a four-way junction in much the same way as they normally pathfind. What this functionally means is that T and four-way junctions ''only guide dwarves hauling a cart, not carts, themselves''.

Carts only check for curves when they are halfway through a tile. When they get there, they look to see if their path has no exit. (That is, if it is traveling East, it checks if there is an East exit.) If there is, it ignores all other track directions, and keeps traveling. If there is not, it checks to see if there are only two exits to the track, and if one of those directions was the direction it "came from". (That is, if traveling West from the East, it checks if there is a valid exit to the West, and if not, if there is an East exit and EITHER a North or South exit.) If there is not, it ignores the track anyway, and keeps on traveling as though it were still on track.

If there is a curve the cart will respect, it checks for derailment. Carts derail if their speed is higher than 50k. Carts at this critical speed will then check for blockages of their forward path. If there is an obstacle to their path, which may be a wall or even furniture or buildings like a door, they will not derail and respect the curve, anyway. Derailing carts do not "[[#Cart Jumps|jump]]" unless they hit completely untracked tile or an invalid ramp, but simply ignore the layout of the tracks entirely. With invalid ramps, this means not respecting the ramp, and likely results in collision with a wall, zeroing of all velocity, and a cart that requires manual retrieval.

If the cart is traveling at a speed that will not derail, or is forced to turn by a supporting wall, it will subtract 1000 from the "forwards" velocity of the cart, and redirect all forward velocity to the direction of the curve. This change in the direction of velocity ''overwrites'' any "diagonal" velocity, which can prevent diagonal velocity derailments, but any perpendicular velocity is not preserved, and is instead discarded.

=== Valid and Invalid Ramps ===
Ramps are functionally defined for cart purposes as being a tile which exerts an acceleration force upon its "downward slope", and which allows connection to tracks a z-level above or below. This downward slope requires a cart to have at least one track branch touching a wall tile and one ''and exactly one'' carved exit to the tile that is the "bottom" of the ramp. Ramps accelerate carts in this "downward" direction (possibly leading to [[#Corner Ramp Derail|diagonal movement]]), and the deceleration of an "uphill" ramp is actually just the acceleration being applied against the direction of a cart's movement.

This is where players can find an exploit in the behavior of ramps - if there are ''two'' "downhill" exits to a ramp (such as a "T junction" on a ramp where only one exit faces a wall), then the ramp provides no acceleration ''or'' deceleration, allowing carts to travel up ramps without any loss of momentum except for the standard "flat track" deceleration, because as far as the cart is concerned, the track ''is'' flat. (A T junction is also not a curve, so the track is considered flat and straight no matter what direction the cart is traveling.)

Similar effects can be achieved when there are ''no'' "downhill" exits to a ramp. This may be the case if you have, for example, an East-West track with a one-tile channel with a ramp in it. The cart will travel through the "dip" with no change in velocity. It can also be the case if you abuse the [[#Track Direction Irrelevance|Track Direction Irrelevance]], and set only exits ''up'' the ramp, and none leading ''down'' the ramp. For example, if a cart is traveling from West to East up a slope, only carving East exits on each tile of ramp will make the cart travel up the ramp, and then recognize the tile it is on as being a "flat" tile, thus ignoring any deceleration from traveling uphill.

Note that this effect only reliably occurs at below-derail speeds as the cart will treat the ramp as an invitation for a ramp jump otherwise. (This almost always results in a collision with a wall that will stop forward progress.)

=== Falling ===
When falling, a minecart appears to cause no damage upon collision, possibly to allow cart "stacking" across Z-levels.{{cite devlog|2012|04|06}} A dwarf riding in a minecart that is dropped multiple z-levels suffers normal fall damage. Minecarts can fall through up/down stairs.

While airborne, carts do not feel the effects of friction in any horizontal direction, and will continue until they strike an obstacle. Carts that land on tracks instantly re-rail themselves regardless of track directionality.

Falling carts accelerate similarly to the way that a ramp will accelerate a cart in a special z-only velocity that only applies to airborne carts. (Actually, since a tile is notionally 1.5 times as high as it is wide/long, acceleration due to gravity in freefall appears slightly ''slower'' than ramp acceleration, since it has to move the cart (or any other object) a greater distance.) Ramp acceleration, while it logically should be partially z-directional, is only recorded as x- or y-directional, and there is no translation of z-directional velocity upon landing. Landing carts zero out their vertical velocity upon landing, even when landing on ramps, although carts that had horizontal momentum while falling preserve it.

This means a cart falling onto a track ramp is accelerated as if starting from the middle of the ramp - i.e. to the same speed, no matter how many Z-levels it was dropped, vertical velocity is negated. {{cite forum|144328/5701211}} As a consequence, the fall damage to passengers is also negated.

Carts falling onto a floor can, however, cause damage to creatures ''one tile below the floor''. This can be used in an [[exploit]] called a "thumper", where carts are caused to repeatedly fall on a floor above an entrance to the fort, inflicting significant damage (as though it were a collision) on those below the cart.

=== Cart Jumps ===
Carts that cross off of "up" ramps relative to their current direction of travel, which do not have a ceiling above them, are traveling above derail speed, and do not have valid ramp track before them can translate a portion of their horizontal velocity into vertical velocity, causing a cart to be projected into the air until vertical velocity is negated and overcome by the gravitational acceleration. Because downwards acceleration is applied per-tick, this creates a reasonable facsimile of the parabolic motion of an actual object rolled up a ramp and launched with significant speed.

{{diagram|spaces=yes|\
z0 z0 hiding ramps z+1 A z+1 B (hidden ramp)
▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒
═▲▲▲▲▲══▲▒▲═ ═╚╚╚╚╚═══▒══ ▼▼▼▼▼ ▼═▼ ▼▼▼▼▼ ▼╚▼
▒ : Wall
═ : track
▲ : Ramp
}}
In this diagram, if there is no ceiling above it, the track in z+1 A will launch its carts airborne when they travel across the ramp. z+1 B (with a ramp on the tile on the hill) will not launch the cart. The cart would also not be launched with ''any'' valid ramp, even if it does not travel in an appropriate direction, such as North/South (which the cart will ignore, as it is not a curve, anyway, although it may produce acceleration that may cause diagonal movement.)

Carts that are traveling at derail velocity will also start "jumping" from the track if it hits an un-tracked tile, flying over and ignoring any tracks until it is ready to land. Carts that land upon tracked tiles re-rail themselves, and clever designers use this feature to jump over curved track sections in one direction or another. (Retracting bridges over untracked tiles can cause jumps or not cause jumps depending upon the status of the bridge.) Minecart speed must be carefully regulated to ensure reliability of jump length.

Hitting untracked tiles at around 70k velocity creates a vertical component to acceleration that allows for jumps of around 6 (horizontal) tiles that do not actually leave the z-level the cart is on, but which do apply z-direction velocity on the cart, as per falling.

Carts that approach a downward slope at a high enough velocity will also make a jump, (or rather, ignore the ramp and fly forwards) but will not do so if the [[#Checkpoint Effect|Checkpoint Effect]] is exploited through an impulse ramp before the actual downhill as the impulse ramp "tricks" the cart into thinking it has already started going downhill.

=== Skipping ===
If a minecart is moving fast enough, it can skip over [[water]] or [[magma]], making splashes of [[mist]] (or [[magma mist]]) as it attempts to move on them horizontally. This horizontal movement is independent of the minecart and its content's [[weight]].

Skipping causes significant friction on the cart, and even a cart going at max speed from ramps can only make about 50 tiles without requiring re-acceleration. (Carts that decelerate enough that they do not trigger the skipping effect will, of course, sink.)

=== Corner Ramp Derail ===

Corners on upward ramps can cause diagonal movement, forcing a derail even if the cart has a wall next to it, which will force a stop when it touches a wall that forces dwarves to manually reset the cart.

This is caused by the fact that a cart, after turning the bend in the track and entering e.g. a flat tile, will be subject to the checkpoint effect which applies 5k acceleration opposed to the last amount of ramp acceleration it received. Since the cart has just passed a corner, this compensatory speed adjustment now goes to the "outside" of the corner and creates enough lateral velocity to carry the cart off the track after eleven steps. (Down corner ramps do not have this problem, as the downward direction is in line with the past-corner movement direction and the checkpoint effect works on the only remaining movement vector.)

There are two fixes to this problem. One is to simply not put corners on up ramps. The other is to "cancel" the lateral speed after a cart has passed the ramp, either by sending the cart through another corner or by putting a high-friction track stop on the exit tile. In the latter case, the cart will lose 10000 speed in the desired direction, but the same speed loss will apply to the undesired lateral speed, nullifying it.

=== Checkpoint Effect ===
The checkpoint effect, [http://www.bay12forums.com/smf/index.php?topic=144328.0 explained in depth by Larix], is an odd and highly exploitable feature of ramps where minecarts "teleport" through the next tile of track, ignoring nearly all minecart physics (except that they stop at all walls or other obstacles and only respect curves with no backing wall and invalid ramps if they are below derail speed) and passing through that tile in just a single tick, and to the very end of the next tile.

This effect occurs when a cart leaves a downward ramp for any other direction of tile. (This includes ramps which accelerate in different directions, even a ramp which goes from accelerating East to accelerating North due to a bend in a chain of standard down ramps in a curve.) This allows, for example, two valid straight ramps directly next to one another with a cart dropped onto one or the other with no momentum to have the cart pick up acceleration going "down" the ramp as normal, but then flying up through the "up" ramp it travels into with no loss of momentum, as though it had come from an impulse ramp. If the two ramps had at least one space of distance between them, and then a cart were dropped in, the cart would instead "rock" back and forth between the two ramps.

This seems to be because ramps have a slightly longer length than regular tiles - 141,420, rather than 100,000 distance. When this "snaps back" after a ramp, it seems to project the cart suddenly further along the track, making it jump a tile ahead even when otherwise moving at relatively low speeds.

This [[bug]] is the cause of a ''wide array'' of unexpected behavior among people who do not take this bug into account. It causes derailments or failure to climb up seemingly valid impulse elevators. In general, it makes a system that behaves extremely counter-intuitively, and operates ''any time a cart encounters a valid ramp''. At the same time, when its effect is accounted for, it is highly exploitable: It causes "perpetual motion devices" using no power when two opposing ramps are placed next to one another, since the "uphill" effect of the opposing ramp is ignored, preventing deceleration.

Another useful thing to note about this exploit is that carts traveling at no less than 71,000 or so speed (enough to travel half a ramp tile in a single tick) can travel through every tile in just one tick at no change in velocity as long as the tiles alternate between impulse ramp or actual down ramp and any other tile type. The cart checkpoints through the non-down-ramp tiles, and can pass through the (impulse) down ramp tiles in a single tick, before they can actually start gaining momentum.

{{diagram|spaces=yes|\
▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒
═▲═▲═▲═▲═▲═ ═╚═╚═╚═╚═╚═
▒ : Wall
═ : Normal track
▲/╚ : N/E Track/Ramp
}}

If the cart enters from the West at less than 72,000 speed, some of those ramps will cause Eastward acceleration.

This means that an impulse ramp not contiguous to other impulse ramps has a top speed of around 75k:

{{diagram|spaces=yes|\
▒▒▒▒▒ ▒▒▒▒▒
▒╔═╗▒ ▒╔═╗▒
▒╚▲╝▒ ▒╚╗╝▒
▒▒▒▒▒ ▒▒▒▒▒
}}
This setup makes a cart that travels clockwise at a speed that fluctuates around 75k velocity. If the cart has more than 72k velocity, it fails to accelerate in the ramp, as it leaves the ramp in a single turn due to checkpointing to the halfway point. After that, the curves sap 1k velocity, and every tick saps 10 velocity.

Two contiguous impulse ramps with a same-facing "downwards slope", however, do not suffer the checkpoint effect in the second tile, giving functionally triple the space to accelerate. This means it will add velocity (at the standard rate of 4.9k per tick) up to a maximum speed of 216k.
{{diagram|spaces=yes|\
▒▒▒▒▒▒ ▒▒▒▒▒▒
▒╔══╗▒ ▒╔══╗▒
▒╚▲▲╝▒ ▒╚╗╗╝▒
▒▒▒▒▒▒ ▒▒▒▒▒▒
}}
This example results in a cart moving three times as fast as the previous cart.

Three successive ramps results in the highest attainable speeds.

In practical terms, this means that only consecutive ramps should be used for high acceleration, but singleton ramps can be used to have speeds that are somewhat regulated.

=== Stacking ===
If a minecart lands on top of another minecart, they may form a stack, with the upper cart on the z-level above the lower. Subsequent carts do not form a stack, but rather quantum stockpile in the same space. This behaviour is useful for [[megaprojects]] and [[trap design]] with minecarts as the weaponry. Moderation should still be exercised: carts take longer to fall into a "stacking" tile already occupied by other carts and will spend that time "hanging" in the air above the stack. This can lead to following carts striking them, which can cause all kinds of malfunctions. The extra time is two game steps for every cart already in the stack, which doesn't hurt stacks of ten carts very much but makes stacks of 100+ rather impractical.

These minecarts on the upper level generally need to be struck with another minecart to move out, or have their support removed. The latter option is safest done by shooting it away with another minecart, manual removal of a stack-supporting cart typically causes the next cart from the stack to [[fun|fall on top]] of the hauler.

=== Perfectly Elastic Collisions ===
Minecart collisions are perfectly elastic, meaning that not only do minecarts not take damage, but that two carts that are rolling which have frontal collisions of near-similar speed, and where one cart is no more than twice the mass of the other cart, will result in a billiard-ball-like effect of the lighter cart bouncing off the heavier cart with a proportional speed increase dependent upon the relative momentum behind the heavier cart.

Using this trick with carts already at the 270,000 maximum speed from ramps can result in "supersonic" carts traveling at speeds in the millions (travelling a dozen tiles per tick), but where they are suddenly subject to 10,000 units of "terminal velocity" friction per tick. [http://www.bay12forums.com/smf/index.php?topic=137557.0 Thread with SCIENCE here].

While hypothetically capable of launching a minecart into orbit when used in conjunction with a ramp, no cargo can be contained in the launched cart, as the collisions will force ejections of the cargo. Your "unwilling volunteer" [[goblin]] space pioneers will simply become paste underneath the wheels of an extreme high-speed cart.

== Non-standard uses ==
Minecarts include some interesting characteristics that have motivated uses beyond hauling. They can be useful for creating fully-automated [[Quantum stockpile|quantum stockpiles]], [[garbage disposal]]s, [[Water_wheel#Micro_Water_Reactor|water reactors]], and [[portable drain]]s. Storing perishable goods (meat, meals, etc.) inside a minecart appears to guard against rot and vermin.
Minecarts can be [[Trap_design#Minecarts|used as weapons]], or as (hopefully non-fatal) triggers to restart stalled [[healthcare]]. They can also be used to time/control game events, either using a basic [[repeater]] or much more advanced [[minecart logic]].
Minecarts trigger [[pressure plate]]s, which means a trap can be designed to trigger when a thief attempts to steal a minecart.
A pressure plate can be used as automatic and more precise custom "launch when full enough" system - as long as weight of your minecarts stays the same. You cannot build a hatch or roller on the same tile, so launch by bumping with another cart. {{cite forum|15096/4580050}}
Dwarves riding minecarts can attack enemies within reach (which goes back to dev log). This applies to shooting, and they actually can hit targets while riding by.{{cite forum|109460/5266119}} Whether a minecart protects the rider and how it interacts with dodging is not known yet. Minecart riders can also [[Swimming#Minecart_training|train swimming]] and [[Megaprojects#Surveillance_Track|detect ambushers]].

== Simple Example Layouts ==

=== 2-way Minecart Route ===
[[File:Simple2wayminecart.PNG|500px|Simple 2-way Minecart Route]]

This is an example of how a 2 way route can be established.
* Stop 1 is non dumping, frictionless (Feeder Stockpile from North in this example)
* Stop 2 friction and dump (dumps South in this example)
* Stop 3 is non dumping, frictionless (Feeder Stockpile from North in this example)
* Stop 4 friction and dump (dumps South in this example)

Now you create a Route hauling your desired items from Stop 1 to Stop 2 . Immediately guide the empty cart to Stop 3 (because the stop has no friction, a kicked cart will overshoot the stop).
Haul desired items from Stop 3 to Stop 4. Immediately guide the empty Cart to Stop 1.

=== Automated Minecart Funicular (Elevator that also goes sideways)===
This is an example to set up stone delivery from multiple Z levels with a common set of tracks while automatically returning the cart to where it is supposed to go. In this example, the South track goes upwards towards the drop off point, the North track goes downwards for cart return.
The design pictured consists of the following:
[[File:MinecartFunicular.gif|frame|left]]
* Two ramps next to a wall spaced one tile apart
* Tracks on top of the ramps to make an inclined track
* A 3X1 channel dug down next to the ramps on the side opposite the wall
* 2 gear assemblies, one between the ramps, one over the middle channel
* Rollers on the upward track pointing towards the wall (South ramp in this example)
* A hatch over the channel next to your downwards ramp (North ramp in this example)
* A wall diagonally adjacent to the to the upwards channel
* Tracks leading from the hatch to the single wall
* A wall next to the curved section of track
* A pressure plate set to trigger on minecarts on the track underneath the minecart. Link the pressure plate to the hatch
* Set up a minecart route with one stop where the minecart is. Set the condition to kick the minecart in the direction of the channel with any condition and contents you wish
* Each subsequent level needs to be shifted one tile in the direction of the ramp down
{{clear}}
The unloading level just needs to pass the cart over a track stop set to dump in whatever direction you want, then send it back down the return track. It also needs to provide power to the rollers, 12 power is required per level.
[[File:MinecartFunicularTop.gif|thumb|left]]
{{clear}}
How it works
* The minecart sitting on the pressure plate keeps the hatch open so that other carts may pass
* When the cart is off the pressure plate the hatch closes. This causes the cart to pass over the hatch back to its loading position
[[File:MinecartFunicularHatch.gif|thumb|left]]
{{clear}}
== Adventure mode ==
In addition to being used for hauling, minecarts can also be ridden in [[adventure mode]]. (Adapted from forum thread {{cite forum|122903/4258212}})

# If the minecart is in your inventory, drop it. If it is already on the ground, proceed to step 2.
# Press {{k|u}} when you are 1 tile away from the minecart (or standing on the same tile as the minecart).
# You will be presented with the following options:
[[File:minecart adventure mode menu.png|left]]
{{clear}}
* If you {{DFtext|Push}} the minecart, it will move a few tiles in the direction you chose. Physics comes into play here, so it will gain/lose speed depending on the usual factors.
* If you {{DFtext|Ride}} the minecart, you will hop into the minecart, even if you were a tile away, and it will move in the chosen direction with you in it. It will gain/lose speed depending on the usual factors. Whilst the minecart is in motion, you should press {{k|.}} to skip your turn; if you attempt to move whilst the minecart is still in motion, the laws of physics come into play, and you will take [[wound|damage]]. However, it is currently possible to jump out of a moving minecart safely.{{bug|10104}} Alternatively, you can push the minecart whilst it's still in motion (although it's unclear how one can bend [[physics]] so as to push a moving minecart whilst inside the minecart). If you push it in the same direction you are already travelling in, you will greatly increase the minecart's velocity. You can also push it in different directions, and this will cause it to gradually change direction-the amount of pushes this requires depends on the minecart's velocity. Once the minecart has stopped moving, you may move out of it safely, or you may want to give it another push. Note that if you push a minecart right after having ridden it (still on the same tile as the minecart), it will act as though you chose to ''ride'' it.
* When the minecart is on a track, options appear to {{DFtext|Guide}} it in directions that the tracks lead. This moves the cart 1 tile in the direction it is guided. Guiding the cart is the only way to move a minecart from a maximum friction track stop (other than taking it into inventory.)

Minecarts in adventure mode are not restricted by a lack of tracks. However, they are hindered by natural ramps. Attempting to go up a slope will lead up the cart slamming into the wall. The good news is you'll make it over the ramp. The bad news is you likely won't stick the landing.

Note that while carts are a powerful weapon if heavy and fast enough, they have their limits, and a collision can sharply reduce the speed of a cart depending on what you hit, potentially enough to eject the rider. Trying to run over a human will send them flying, while trying to ram a dragon will not end well.

If you want to test this out without creating an adventurer, the [[object testing arena]] allows you to spawn minecarts ({{k|k}}-{{k|c}}-{{k|n}})

== Forging and Melting ==
* Metal minecarts cost '''two''' [[metal]] bars to forge, or '''six''' [[adamantine]] wafers.
* When a non-adamantine metal minecart is melted down, it will return '''1.8''' metal bars, for an '''efficiency of 90%'''.
* When an adamantine minecart is melted down, it will produce '''1.8''' wafers, for an '''efficiency of 30%'''.

== See also ==
* [http://www.bay12forums.com/smf/index.php?topic=109460.0 The "How Does Minecart" Thread] by '''Girlinhat''' et al.
* [http://www.bay12forums.com/smf/index.php?topic=112831.0 SCIENCE: Quantifying minecart physics] by '''Snaake''' et al.
* [http://www.bay12forums.com/smf/index.php?topic=129676.0 How to build a Multi-cart Ore to Magma Minecart Project without needing power] by '''WanderingKid'''. (Images recovered from wayback machine and posted here: https://imgur.com/gallery/LpRsDwO)
* [http://www.bay12forums.com/smf/index.php?topic=144328.0 My very own Minecart Education Thread. Ten Lessons, now complete.] by '''Larix'''.
* [https://www.youtube.com/watch?v=hctG2dQzHwg Real-life railcarts/conveyor hybrid] which uses similar mechanics.

== Bugs ==
*A dwarf will drop her [[child|baby]], if she has one, when boarding a minecart set to be ridden.
*Dwarves have no concept of traffic safety and will walk into busy minecart lines to retrieve objects, often with deadly consequences. This is especially problematic in [[Swimming#Minecart_training|clever applications]] depending on dwarves riding the carts very frequently, because they have a bad habit of dumping their worn clothes on the tracks after a minecart ride. Adding an automatically-operated [[hatch cover]] at the end of such a ride can help prevent [[unfortunate accident]]s.
*Dwarves cannot guide a minecart through an unlocked door unless another dwarf opens the door.{{bug|6056}}
*It is possible for a creature and minecart moving towards each other to pass without collision if they exchange tiles in the same tick.
*After a minecart ride, a dwarf will sometimes haul the minecart to a storage stockpile, leaving another dwarf to haul the vehicle back to the route.
*Minecarts falling onto a floor injure creatures in the tile below the floor.{{bug|6068}}
*If a minecart travelling at high speed hits a wall, it and its contents may go through the wall, or even end up embedded in it.{{bug|5996}}
*A minecart's initial velocity is not affected by weight, when pushed or launched from rollers.{{bug|6296}}
*Removing a stop that has a vehicle waiting on it may cause the game to crash.{{bug|5980}}
*Jumping out of a minecart in motion does not lead to injury.{{bug|10104}}
*Jumping into a stationary minecart can lead to significant injury.{{bug|10229}}

{{Gamedata|{{raw|DF2014:item_tool.txt|ITEM_TOOL|ITEM_TOOL_MINECART}}}}

{{Category|Fortress mode}}
{{Category|Interface}}

[[ru:Minecart]]

Minecart

2023-01-14T03:04:10Z

Xjtu-blacksmith: /* Step-by-step tutorial */ typo

{{migrated article}}
{{Quality|Unrated}}
{{av}}
[[File:Leitnagel Hund.png|thumb|Minecarts]]
A '''minecart''' is a [[tool]] intended for [[hauling]]. It can be made of [[wood]] at a [[carpenter's workshop]] or 2 bars of [[metal]] at a [[metalsmith's forge]] (using the [[Metal crafter|metalcrafting]] labor.) Minecarts store up to five times as many items as [[wheelbarrow]]s and are quite a bit faster than dwarves hauling objects by hand, but have the disadvantages of requiring a dedicated track network, a complex route planning phase, and the possibility of dwarves [[Fun|blundering into the path of carts filled with lead ore]]. Tracks may be carved into stone, or [[Construction|constructed]]; the latter allows above-ground routes, but these are more difficult to set up due to their additional [[building material|material requirements]].

Just like wheelbarrows, minecarts are considered [[item]]s and are stored in a [[furniture]] [[stockpile]]. Despite their five-times-greater capacity, they are only 33% larger than wheelbarrows (minecarts have a size of 4000) and are identical in base [[item value|value]] when made from the same [[material]] (the value may differ due to the [[item quality]]). [[thief|Thieves]] or even mischievous animals can steal minecarts, even when they are moving on a track.{{cite forum|109460/3289070}} However, minecarts moving fast enough or being ridden cannot be stolen.

Although most of the utility of minecarts is in [[fortress mode]], an [[adventure mode|adventurer]] can also ride in a minecart. Adventurers can also pick up and relocate minecarts.

The invention of minecarts revolutionized the [[minecart logic|Science of Dwarfputing]] by enabling smaller, faster logic systems to be built.

== Basic Minecart Usage ==
Minecarts can be used to swiftly transport dwarves, [[flow|fluids]], and/or large amounts of items, but before you have a functional minecart, there are several preconditions that need to be met. First of all, you need an actual minecart, constructed either in a [[carpenter's workshop]] or [[metalsmith's forge]]. For the minecart to be able to move, you also need to carve (with {{k|d}} {{k|T}}) or construct (with {{k|b}} {{k|C}} {{k|T}}) a track, which could be as simple as a straight line. Finally, you need to construct stops on your track (with {{k|b}} {{k|C}} {{k|S}}) where the minecart will start and stop.

After you have created the stops and assigned a cart to the track, you must create logic routes connecting several stops and designate starting conditions for each stop. This is done with the {{k|h}}auling key. The most basic conditions are how the cart's movement is initiated and in which direction the cart should start moving. Carts can be either pushed (a dwarf stands at a stop and gives the cart a single push) or guided (a dwarf continually pushes the cart forward, guiding it along the track). The [[hauling]] [[labor]] required for pushing and guiding carts is called "Push/Haul Vehicles" and is turned on by default.

To control which items are to be transported, you can add conditions specifying: (1) which kind of items are to be loaded and unloaded, (2) stockpile links to define which stockpile(s) the items should be un/loaded to and from.

===Capacity and weights ===
Minecarts have a [[Size|size capacity]] of 500,000 – five times the capacity of [[wheelbarrow]]s.

'''Examples of the capacity of one cart'''
{| class="wikitable"
|-
! Item
! Amount
|-
| [[stone]]
| 5
|-
| [[wood|log]]
| 10
|-
| [[block]]/[[bar]]
| 83
|-
| minecarts
| 12
|-
| [[Kitchen|prepared meals]]
| 500
|-
| [[Trap_component#Spiked_ball|spiked balls]]
| 500
|-
| [[Weapon#Native_weapons|mace]]
| 625
|-
| [[Weapon#Native_weapons|spears]]
| 1250
|-
| [[cloth]]
| 2500
|}

The weight of the loaded minecart does not affect the initial velocity received from pushing or launching from a roller.{{bug|6296}} However, the load of a minecart ''does'' affect whether a [[pressure plate]] triggers or not, based on the pressure plate's setting.

'''Weights of different carts'''

{| class="wikitable"
|-
! Type of cart
! Empty cart
! Fully loaded (items)
|-
| oaken minecart
| 28Γ
| 378Γ (10 oak logs)
|-
| iron minecart
| 314Γ
| 1698Γ (83 marble blocks)
|-
|-
| copper minecart
| 357Γ
| 1682Γ (10 obsidian boulders)
|-
| platinum minecart
| 856Γ
| 10482Γ (83 gold bars)
|}

The weight of a minecart is one twenty-fifth (1/25) the [[density]] of its material in Urists. Because pressure plates can be set to trigger at intervals of 50 Urists, minecarts with weights just under a multiple of 50 are ideal for switching based on whether they're full or empty. The best minecart materials for full/empty switching are as follows:

{| class="wikitable sortable"
|-
! Material !! Minecart weight !! Content weight required to trigger !! Banana roasts required to trigger (for scale)
|-
| [[Glumprong]] || 48 || 2 || 4
|-
| [[Electrum]] || 596 || 4 || 7
|-
| [[Nickel silver]] || 346 || 4 || 7
|-
| [[Brass]] || 342 || 8 || 14
|-
| [[Bismuth]] ([[Strange mood|moods]] only) || 391 || 9 || 15
|-
| [[Fine pewter]] || 291 || 9 || 15
|-
| [[Lay pewter]] || 291 || 9 || 15
|-
| [[Tin]] || 291 || 9 || 15
|-
| [[Trifle pewter]] || 291 || 9 || 15
|}

{{anchor|Tracks}}

=== Creating tracks ===
Minecart tracks are made up of contiguous track, tracked ramp, or bridge tiles. Track tiles and tracked ramp tiles have a direction or series of directions associated with them. These directions dictate which directions a minecart on a given tile may move from that tile. For example, a Track NE (northeast) tile allows a minecart on it to move either north or east from its present position. Therefore, if you want your minecart to move east along a straight piece of track, then return west using that same track, you would need to use EW tracks so that the cart could travel east initially, then return west over the same track. Excluding designs in which the cart will "jump" tracks via a drop or other ramp, tracks must be valid end to end to work for most looped or straight-track applications. A single east only track tile in your line of east-west tracks will cause any route using the track to fail the moment it tries to go the wrong way over that tile. Minecart tracks can be built in two ways: Engraved/carved or constructed. A given minecart track need not use engraved or constructed elements exclusively, as the two methods can be used interchangeably depending on the needs of a given section of track. The way the tracks are built is slightly different between the two, as explained below.

====Simple tracks====

'''Carved'''

A single-tile wide strip of natural stone can be designated to be [[Engraver|carved]] (with {{K|d}} {{k|T}}), which will create a straight two-way track. The creation of corners, crossings, and T-junctions is as simple as designating another strip of track that overlaps an existent or newly designated track. Engraved tracks are removed by [[smoothing]] the rock they're on, which results in a smooth floor (that can be re-engraved if necessary), or by building a [[floor]] on top and subsequently removing it. Dwarves can carve corner tracks in one pass by designating the track carving twice and canceling unwanted carvings (with {{K|d}} {{K|x}}). Tracks can be engraved in any natural floor tile, rough, smooth and even over engravings, providing an easy method to remove low-quality or undesired floor engravings. Once a track has been engraved, it's important to check the track directions for each tile in the route carefully to make sure no mistakes were made by yourself or the game's track engraving logic.

'''Constructed'''

Tracks can also be built as regular [[construction]]s (through {{K|b}} {{K|C}} {{K|T}}). This method is resource-expensive, since each track tile requires one stone, [[bar]], or [[block]] for construction, and time-consuming, since you can't designate strips longer than 10 tiles at a time. Corners, crossings, T-junctions, and ramps also have to be designated individually. However, it is usually the only way to build tracks above ground or on soil (barring the [[Obsidian farming|creation of obsidian]]). Constructed tracks are designated for removal like any regular construction; be aware that removing track ramps built on top of natural ones will also remove the original ramp, leaving a flat floor.

====Ramps====

'''Carved'''

The carving of natural ramps is a little more confusing: to carve a two-way track on a ramp (natural only, does not work on constructed ramps), you must designate the track '''starting on the ramp and one square beyond''' in the direction you want the track to go. For the side of the ramp square you want to head upward, there '''must''' be either a natural or constructed wall in the square next to it, otherwise the game assumes you are trying to carve it on the same level – this can result in the track being carved underneath a door or other object. If you have accidentally done this, you can correct it by smoothing the ramp and constructing a single square of wall next to it, then re-carving the ramp correctly, however, the wall must stay there permanently — removing it will disconnect the track.

'''Constructed'''

The track and ramp must be constructed together as a Track/Ramp from the construct track menu ({{K|b}} {{K|C}} {{K|T}}). When constructing track ramps, the stated direction should be the same as the connected tracks. For example, a track going up from West to East would require, starting from the West, a Track (EW), a Track/Ramp (EW) and a Wall behind the ramp, underneath the section of track above it. Incorrectly placed ramps result in minecarts ignoring the ramp and crashing into the supporting wall. They will not, however, display as unusable as when the supporting wall is missing.

'''Examples of ramps'''

A simple ramp would look like this:
{{diagram|spaces=yes|\
z +0 z +1
░░░░ ░░░░
═▲o ░▼═
░░░░ ░░░░
o : wall
}}

Carving track corners into ramps is rather unintuitive and complicated. Since engraving tracks always requires two tiles to connect in a straight line as input, you have to give two separate designations for a single job: a track bit from the ramp tile to the "below" direction and another one to the wall of the "upward" direction. If you wanted to change direction on a ramp from east to north:
{{diagram|spaces=yes|\
z +0 z +1
░░░░░ ░░░░░
░░░░░ ══╗░░
══▲░░ ░░▼░░
░░░░░ ░░░░░
}}

you would need to connect the ramp on z +0 both to the west and to the north by issuing two "carve track" commands, one selecting the ramp and the track tile to the west, and another connecting the ramp tile with the wall to the north. An engraver would then carve a NW track corner into the ramp, allowing carts to pass the corner correctly both going up and down. Such track corners are perfectly serviceable for guided carts, but moving down a route of several of them by pushed or ridden cart is problematic - ramps on corners behave very counter-intuitively, resulting in loss of speed when going down and diagonal movement when going up.

Moving to and from ramps (or between ramps "pointing" in different directions) causes some non-trivial adjustments to speed and even moving along the tiles at a fixed speed ''unrelated to the entry/exit velocity values'', because transitions to/from ramps are processed differently and are not to be "skipped". This affects compact track/ramp combinations (such as e.g. a simple 2x2 ramp spiral) most, and combined with bouncing often makes them work not in the way one could expect. {{cite forum|144328/5705102}}

=== Hauling route ===
A hauling route is a list of directions describing how and under what conditions a minecart will move. The proper setting up of routes is essential for a working rail system. Routes, stops, departure conditions and stockpile links are managed from the {{k|h}}auling menu.

==== Route ====
A route defines the path a minecart will take along a track, as well as under what conditions it will move or stop moving. A route is made up of stops. Stops are precisely what they sound like, a position on the track at which you want a minecart to stop. A minecart track might use as little as a single stop for a looped track, which will serve as both a starting and stopping point for the cart, or it could contain many stops, perhaps to load supplies or wait for a bridge to be manually lowered, before reaching its destination or returning to its starting point. It is important to note that you only need to place stops on a route where you actually want the cart to stop and wait for some action to occur. They are not needed to help navigate the cart along the track beyond telling it where on the track to stop.

New routes are created with the {{k|h}}auling key. Existing ones can be removed (without confirmation) with the {{k|x}} key, and also {{k|n}}icknamed. Before operating, the route must have a {{k|v}}ehicle assigned to it (this can be done with either the route or a stop selected). Assigning a full minecart to a route may result in a slow hauling job if the contents are heavy.

==== Stops ====
Stops are the individual waypoints that make up a hauling route. A given stop consists of the location of a tile, as well as conditions describing when, where, and how a cart should be moved after being stopped at that tile. Stops can be created from within the {{k|h}}auling menu, by placing the cursor over a tile and hitting {{k|s}} while highlighting the route (or a stop within) you've already designated. A minecart will begin its route at the first stop created, and continue through each subsequent stop, being guided, pushed, or ridden from each stop to the next depending on the conditions specified. In many basic minecart applications, the cart will end up at the same stop it began at, though this is not always the case. It is important to note that hauling stop order is enforced, even if there is no track. A dwarf will drag the cart overland back to a skipped stop in the route's list if your tracks bypass it somehow, including if the minecart does not stop on the stop after it is pushed/ridden.

Once a stop has been placed, it is given a default set of conditions under which to move the minecart if it is stopped there. Each new stop gets the same default conditions regardless of the track it is placed upon (e.g. guide the cart to the north). For this reason new stops might get marked by yellow exclamation marks ({{DFtext|!|#ff0}}) due to invalid directions. One important thing to note is that as you place additional stops, the display will show paths between the stops you have defined. However, this is '''not''' necessarily the actual route the minecart will take once the route is in operation. For example, if a route were defined with two stops at opposite ends of a track with many twists and turns, a line will be drawn directly between those stops to show the order in which they will be visited. These route lines may crisscross all over the tracks, but so long as the track is valid end to end, the cart will follow the track from one stop to the next, even across twists, turns, and z-level changes. Route stops, which are the steps that make up a route, should not be confused with physical Track Stops, described below.

===== Stockpile links =====
By placing the cursor on top of a stockpile and using {{k|s}}, you can create stockpile links while defining a hauling stop. Links can also be redefined by selecting them, placing the cursor over a different stockpile, and pressing {{k|p}}. The cart will then be filled by items present in its various linked stockpiles in preference to other items. Note that bins should be used with caution in stockpiles that are linked to minecarts. Bins cause problems when used with the "Desired Items" list in a stop's conditions. For example, if a minecart is set to accept only granite blocks, and to depart north when it is 100% full of granite blocks, it will not depart if any of those granite blocks are in bins, even if bins are also included in the desired items list. Two solutions to this problem exist as of v0.40.24. First, bins can be disallowed in stockpiles that are linked to stops. Alternatively, bins '''can''' be used in conjunction with minecarts provided that the minecart's departure conditions use only "any items" instead of "desired items." This option can be toggled in the advanced conditions menu for a stop, accessible via the {{key|C|}} key. The cart's contents can still be controlled by specifying what items are allowed in the linked stockpile.

===== Departure condition =====
Departure conditions involve setting conditions in which the minecart will leave on the route. Each condition includes:
# A departure mode (Guide, Ride or Push).
# An initial departure direction (NSEW). Note that this defines the initial direction of movement only. Even if a track includes many turns, as long as the initial movement direction is valid the cart will follow the minecart track thereafter.
# A timer, before which the departure condition cannot be met.
# Conditions on the amount of items in the cart.
Departure conditions are created with the {{k|n}} key. A new departure condition will read: "guide north immediately when empty of desired items". This condition can be changed between basic presets with {{k|c}}. "Advanced" mode ({{k|C}}) allows for more precise control over departure conditions: fine tuning the percentage from 0 to 100 in 25% steps ({{k|f}} and {{k|F}}), switching it being either the maximum or the minimum amount of items for the condition to be met ({{k|m}}), and whether the cart accepts all or only a specific set of items ({{k|l}}). Common to both screens are the departure mode ({{k|p}}, Push, Ride or Guide), {{k|d}}irection, and timer ({{k|t}} and {{k|T}}) options.

To have a cart only carry a specific set of items, the stop can be set to only carry "desired" items, opening the selection screen with the {{k|Enter}} key while having said stop condition selected, and toggling as desired, or it can simply be linked to a stockpile and set to depart once it is full of items from its linked stockpiles, regardless of type.

=== Track Stops ===
A Track Stop, not to be confused with a route stop, is an optional, single-tile construction which serves two purposes. First, it can be used to cancel a cart's momentum in order to slow or stop it as it passes over the Track Stop. This might be necessary if a cart were pushed down a series of ramps to its destination. Second, a Track Stop can cause a cart to automatically dump its contents as it passes over the Track Stop. Track Stops are constructed via {{k|b}} {{k|C}} {{k|S}}, and must be constructed atop an existing piece of track. If a Track Stop has been set to automatically dump a cart's contents, the cart will dump its contents in the direction indicated when it passes over the Track Stop. Depending on the friction settings chosen for the Track Stop, the cart might then stop after dumping, or it might continue on its route to another destination.

Track Stops are not mandatory; in fact, their main use is in automated rail systems. However, even in basic rail systems it can be useful to set a Track Stop to dump items: this saves time that dwarves would otherwise spend in removing items from the cart, time that is better spent driving the cart back to where it's needed. Dumping will occur even with a guided cart. '''Take care not to set Track Stops at a loading site to dump their contents''', or dwarves will never be able to fill the cart. It will dump any contents the moment they are loaded.

Counter-intuitive to their construction method, Track Stops are considered [[building]]s and must be removed by {{k|q}} {{k|x}}.
* See [[#More_on_Track_stop |More on Track Stops]]

=== Step-by-step tutorial ===

Let's construct a simple minecart route. This route will move stone blocks from an input stockpile to an output stockpile. We'll begin by creating the stockpiles:

[[File:minecart-example-1-v50.03.png|200px|Stockpiles designated.]]

The input stockpile is on the left; the output stockpile is on the right. We'll be moving blocks from left to right. Disable bins in both stockpiles, and set the input stockpile to accept only from links. Then make the stockpile take from the mason's workshop where the blocks are being produced.

Next, carve the track:

[[File:minecart-example-2-v50.03.png|200px|Track carving designation.]]

Note that the ends of the designation are uniquely shaped; this is automatic, and not anything you need to control. Now, wait for your engravers to come along and carve the track into the stone. (Your haulers will probably also fill up the input stockpile while you wait.)

In addition, while we're waiting for that to happen, we'll build an iron minecart in the forge.

[[File:minecart-example-3-v50.03.png|200px|Track carved.]]

When the track has been carved, it will look like the above (the track will be solid instead of flashing). Now, order a track stop to be constructed (Under "Constructions") next to the output stockpile:

{|
| [[File:minecart-example-4-v50.03.png|200px|Track stop designation.]]
| [[File:minecart-example-5-v50.03.png|200px|Select dumping direction.]]
|}

You must select the dumping direction ''before'' placing the track stop. We want our blocks to be dumped into the output stockpile east of the track stop. Then wait for a mechanic to come along and build the track stop.

[[File:minecart-example-6-v50.03.png|200px|Track stop constructed.]]

Now we'll define the actual ''route''. This is done in the {{k|H}}auling menu. Press 'Add New Route' to begin defining a route. Select 'Add a stop' then click the track next to the input stockpile:

{|
| [[File:minecart-example-7-v50.03.png|200px|Route definition, in progress.]]
| [[File:minecart-example-8-v50.03.png|400px|Route definition, in progress.]]
|}

Select 'Add a stop' again then click the stop next to the output stockpile define the second stop:

{|
| [[File:minecart-example-9-v50.03.png|200px|Stop 2 designation.]]
| [[File:minecart-example-10-v50.03.png|400px|Route definition, two stops.]]
|}

At this point, the route has been positioned, but they haven't been ''defined'' yet.

Click the Minecart icon for the route (not the stop) and assign a minecart to the route.

Select the minecart icon for the first stop to select what items will be hauled to the minecart. By default no items will be hauled to the minecart. As we've set the input stockpile to only take blocks from the workshop, you can either set to to accept blocks, or set it to accept all items.

Click the stockpile icon for the first stop, select the "take from" icon (middle button) and select the input stockpile.

[[File:minecart-example-11-v50.03.png|350px|Set the stockpile.]]

Select the Conditions button ('''<>=≠''') for the first stop and check out the defaults. For the first stop, these are largely fine however you should change the direction button for all the conditions so the minecart goes the correct direction when it's ready.

[[File:minecart-example-11.1-v50.03.png|350px|Set the direction.]]

Select Conditions for the second stop. These need to be changed so the minecart is returned to the start immediately. Erase the bottom two conditions, change the direction to point back to the stop, and then finally click the '''>=''' button so it changes to '''<='''. This will make it so the cart is returned regardless of how full it is (which is good, as it'll always be empty!)

[[File:minecart-example-11.2-v50.03.png|350px|Fix the conditions for the second stop.]]

Once the minecart is in place, dwarves should fill it with blocks from the input stockpile, which will in turn be filled with blocks from the workshop where your mason has been toiling dutifully. When the minecart is full, the blocks will be dumped into the 1x1 stockpile on the right. Automatic quantum dumping!

If the route has any issues, you'll see a red ! on the minecart in the route screen. Be aware that this appears initially until the minecart is put in place. If your route is correctly set up, you will be dwarfs carry items to the cart and the percentage will change on the route screen.

{|
| [[File:minecart-example-12-v50.03.png|frame|Route with an issue.]]
| [[File:minecart-example-13-v50.03.png|frame|Cart correctly getting filled up.]]
|}

=== Troubleshooting ===

Because of the complexity of the system, all but the most careful and experienced minecart users will encounter issues. Most route issues can be diagnosed and fixed from the {{k|h}}auling menu.

'''Symptom:''' {{DFtext|! Set dir/connect track|6:1}} message appears to the right of one or more stops

:;Possible Causes:
:* Game cannot find a path for ''guiding'' the cart without carrying. The game checks for haul route validity assuming the cart will be guided. This warning will be shown when the path crosses impassable tiles, requires a dwarf to carry the cart, or is not fully guidable.
:** If your cart path relies upon advanced tricks like deliberate falling into pits or ignoring floor types, even a path designed entirely as you intended will still trigger the yellow warning. If the route is working as intended, you can safely ignore this warning.
:* Invalid departure direction in one or more conditions for the stop. Edit the stop using {{k|Enter}} and press{{k|d}} until it is pointing in a valid direction.
:* Track stop built on trackless tile. Track stops must be built on tiles where tracks already exist to be usable.
:* Discontinuous track. If the route indicator seems to draw between your first and last stop, this is the cause. Make sure destinations are linked by track to both directions, and that there are no sneaky gaps in the tracks.
:** ''Ramps''' are notorious for their finicky use. It is recommended to check every ramp to confirm no unintended one-way ramps remain.
:** To carve a two-way track on a (natural) ramp, you must designate the ramp ''and one square beyond'' in the direction you want the track to go.
:** Ramps '''must''' have a solid wall on the side opposite to the track ("behind" the ramp), or they will neither work nor be marked as "unusable". The wall can be natural or constructed.
:* Discrepancies in desired/kept item configurations.

'''Symptom:''' The status '''0% V''' always appears to the right of one stop.

:;Possible Causes:
:* Stop not set to take from a stockpile. Edit the Stop using {{k|Enter}} and make sure you see a message like "Take from Stockpile #1".
:* Take conditions and stockpile contents do not overlap.
:* Track stop is set to dump. A track stop set to dump cannot be filled. You must either set the stop to a time-based departure or deconstruct the track stop and rebuild it without dumping. (Alternatively, with [[DFHack]] you can modify "Dump on arrival" to "No" using the {{key|q}} menu without rebuilding the stop.)
:* Minecart itself is designated to be dumped (such as when using mass-dump).

'''Symptom:''' Dwarves fill the minecart properly, but will not move it thereafter.

:;Possible Causes:
:* Minecart contains items not listed as desired on its current stop. Check minecart contents using the {{key|k}} and {{key|z}} keys and ensure that all items in the cart are desired items.
:* Minecart contain desired items ''in bins''. Minecarts seem to have problems realizing that they are in fact full of desired items if some of those items are in bins, even if bins are also among the desired items for that stop. '''This cannot be solved by adding the appropriate bins to the stop's desired items.''' Either disallow bins in stockpiles you intend to load minecarts from, or set the departure conditions to rely only on percentage of total load rather than percentage of desired items using the advanced conditions menu ({{key|C}} key).

'''Symptom:''' Dwarves repeatedly attempt to load the minecart, but no items are ever loaded into it.

:;Possible Causes:
:* Track Stop set to dump used as a loading site. Every time a dwarf places an item into a cart resting on such a track stop, the item will be immediately dumped, causing unlimited, useless cart loading jobs. Autodumping Track Stops should never be used at a loading site.

'''Symptom:''' A dwarf picks up the minecart and carries it to its destination.
:* See [[#Quirks|Quirks]]

=== Danger ===
Minecarts are not without <strike>danger</strike> [[fun]]. Although designating a track automatically sets the [[traffic]] designation to low, dwarves ''may'' still walk on them, and [[creature]]s ignore traffic designations altogether. If an unlucky dwarf or creature fails to [[dodger|dodge]] a minecart, they can be injured. Most of this danger can be avoided by setting the minecart {{k|h}}auling commands to guide instead of push or ride (dwarves guiding minecarts will ignore traffic restrictions), as well as by [[pasture|pasturing]] domestic animals and preventing the access of other creatures to the tracks. Note that removing the track doesn't reset that tile back to normal traffic priority, so you may wish to manually clean up traffic designation afterward. Also note that bridges that are used as tracks don't have their traffic priority changed automatically (since they're just normal bridges), which could cause dwarves to pathfind normally through dangerous minecart entrances in your fort's walls if you're not careful.

The only <s>fool</s>''dwarf''-proof method is to make the tracks inaccessible. There are several ways to create a track which works for minecarts but doesn't allow creature-traversal; the simplest is perhaps building a [[statue]] on the tracks. Other options include adding single-tile holes (minecarts moving at reasonable speed will jump the gap), vertical drops, minecart-triggered doors, small pools of liquid (4/7 water or 2/7 magma), and hostile creatures overlooking the tracks. For safety, both ends of the track should be isolated, making the dangerous center sections completely inaccessible (though maintenance access can be provided by a locked door).

Danger does not always involve living victims: careless route designation can also result in minecarts careening off tracks or colliding with each other. If this occurs, the [[item]]s may be scattered; this can cause even more hauling jobs than the minecart aimed to eliminate. Even <s>better</s> worse, scattered items, especially [[weapon]]s, can injure passing [[dwarf|dwarves]] or other [[creature]]s; in the words of Toady One the Great, "Accidental grapeshotting of the dining room should be possible now."

Of course, the danger of using minecarts means they can also be [[Trap_design#Minecarts|used as weapons]] by imaginative players.

== Advanced usage and automation ==
Minecart-specific effects are implemented via track stops, rollers and [[pressure plate]]s with "track" condition set. Since all three are considered [[building]]s, they can't be built on the same square (however convenient track stop + pressure plate would be) nor a simple ramp, and are removed by {{k|q}} {{k|x}}.

=== More on Track stop ===
Track stops are constructions that allow further automation of minecart systems via adjustable features such as braking by friction and automatic dumping of contents. They can be built from logs, bars and blocks through {{K|b}} {{K|C}} {{K|S}}; friction amount, dumping toggle and dumping direction must be set '''before''' construction, and these settings can be neither changed nor seen thereafter*; however, track stops can be linked to [[pressure plate]]s or [[lever]]s to toggle friction and dumping On or Off (trigger state is inverted: switch On = track stop Off). In thoughts screen, dwarves will admire track stops as traps.

*Note: As of v0.47.05, the friction and direction settings '''can''' be adjusted after the track stop has been constructed. The stop can be {{K|q}}ueried to show the settings as they were set prior to construction, and two options will appear that allow the settings to be changed. The friction amount can be decreased or increased by pressing {{K|a}} or {{K|s}} respectively, cycling from "Lowest" to "Highest". The direction to dump can be toggled through the four cardinal points by pressing {{K|d}} until the desired direction is selected.

If a [[stockpile]] is placed on the tile that a track stop is set to dump to, it can act as a [[Exploit#Quantum_stockpiles|quantum stockpile]] and any items dumped from a minecart that match the storage settings of the stockpile will remain there and accumulate. Normally track stops are built on top of existing track to operate on moving minecarts, but they can also be used without tracks to create [[Quantum_stockpile#The_Minecart_Stop|automatic quantum stockpiles]] (see also [[#Step-by-step_tutorial|step-by-step tutorial]]). It is not always desirable to collect ALL of certain items into one quantum stockpile, such as when distributing a material to multiple separate industries. You can link your quantum stockpile to various other stockpiles, ensuring that your dwarves will keep them supplied as necessary. Because quantum stockpiles never fill up like regular stockpiles, it may be a good idea to add a switch to turn them off.

Items dumped from a minecart at a track stop (or dumped by any other means) into open space fall through z-levels until they land on a solid surface. Items falling onto a designated [[stockpile]] will automatically be considered part of that stockpile, even if the stockpile is set to disallow those items (they will, however, be automatically moved to a more appropriate stockpile, if available). Items falling on top of a minecart will '''not''' fall "inside" the minecart. Use with caution; dwarves have fragile skulls.{{bug|5945}}

=== Automated propulsion ===
==== Roller ====
{{Main|Roller}}

A '''roller''' is a [[power]]ed [[machine component]] for the automated propulsion of minecarts. They are built over the top of existing tracks with {{K|b|M|r}}, requiring a [[mechanic]], ''(length/4)+1'' [[mechanism]]s and a [[rope]]. Rollers may also be placed directly on ramps to help pull carts up Z levels. Rollers are very useful to maintain a cart's momentum along long routes, to get them to climb Z-levels without dwarfpower involved, and to get them to reach speeds unattainable by guiding dwarves. These devices are variable-length (1-10), variable-direction and variable-speed ([[Minecart#Numbers_behind_the_scene|see below]]), all traits that can be set at construction time; a roller uses two units of power per tile it is long.

Single-tile rollers transfer power in all four cardinal directions, while other rollers generally only transfer power perpendicular to their activity direction. Longer rollers can also transfer power along their activity direction if built in the correct order, although this can be hard to accomplish and is easily broken. Rollers cannot be powered from above.

Rollers have great acceleration and capped speed. Carts going faster than the roller are unaffected. If a cart moves across an active roller in the direction the roller works and moves slower than the roller's specified speed, the cart will be set to the roller's speed. A cart going against a roller's movement direction will be sent back the way it came (once again at the roller's speed), unless it was moving extremely fast: speed increment of 100000 allows to reverse carts from the full "highest" (50000) speed roller to full "highest" speed back, but ramps can accelerate a cart beyond this. {{cite forum|144328/5702453}}
A cart crossing over a roller perpendicular to its current movement direction will gain the roller's amount of speed in the perpendicular direction without directly changing its forward motion. Without an adjacent wall to constrict its movement, this will typically send a cart off the rails on a diagonal path, completely unable to follow any tracks until it collides with a wall or is otherwise brought to rest. However, if the roller is placed over a track turn and pushes ''from'' the direction of that turn's track, the turn affects carts ''after'' the roller, so they will be forced into the turn rather than derailed in a diagonal direction. {{cite forum|144328/5702453}}

{{diagram|spaces=yes|\
tracks: full:
║ ║
═╗═ ═╢═
║ ║

╢ : roller pushing from W to E
}}
If the roller is powered, carts from ''all'' directions (unless too fast) exit S, because speed imparted by the roller forces carts toward E and ''then'' into the turn.
If not powered, carts from W and N exit S, carts from E and S exit W. Carts above derail speed will ignore the turn, of course.

{{diagram|spaces=yes|\
║ ║
═╗═ ═╟═
║ ║

╟ : Roller pushing from E to W
}}
Carts from the E or W: exit W.
Carts from N: derailed diagonally, exit SW.
Carts from S: derailed diagonally, exit NW.

Rollers affects carts on a track - if placed on a floor or ramp without any tracks, they are ignored. Depowered rollers are also ignored, friction is determined by the tiles underneath.

Because of their one-way nature, rollers are unsuitable for most two-way minecart tracks (unless you set gears toggling roller A->B off while toggling A<-B rollers on). However, a minecart set to be ''guided'' is not affected by rollers at all{{cite forum|109460/3286235}} — this allows a one-way track to be used in both directions. In addition, unpowered rollers do not affect minecarts.

Care must be taken in [[glacier]]s and other extremely cold [[biome]]s, since rollers (and the machinery used to power them) will not operate when constructed on natural [[ice]] floors.

==== Impulse ramps ====
Carts can be given momentum without rollers or changing z-level by exploiting a design oversight in a phenomenon called "impulse ramps". A track ramp which has at least one wall/fortification and exactly one other connection will ''always'' accelerate a cart towards the other connection, no matter where the cart enters the tile from. This means carts can be accelerated even if the cart doesn't actually change z-level at all; ramps don't actually impart any downward velocity even when making cart descend. If a track ramp faces three directions such as ╩, then two of those directions need to be facing walls for the cart to be accelerated towards the remaining direction.

Example of straight impulse acceleration:

{{diagram|spaces=yes|\
▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒
═▲▲▲▲▲▲▲▲▲▲═ ═╚╚╚╚╚╚╚╚╚╚═
▒ : Wall
═ : Normal track
▲/╚ : N/E Track/Ramp
}}

If a cart enters from the left, it will speed up on every track/ramp and exit to the right going very very fast—more than one tile every step. If it enters from the right, then it will bounce back impulsed by the ramp if it's going slow enough.

As another oddity, carts coming from ramps will in some cases "teleport" through most of the next tile. This is called the "checkpoint effect", and is explained in detail in the Physics section, below. This negates the deceleration of the next tile if it is a ramp "angled" in a different direction. You can just make an upward spiral alternating impulse ramps and regular upward ramps. It takes no power, is quick and cheap to build, requiring only channeling and track carving, and the cart goes up fast, but not so fast that it launches its contents.

Examples of impulse elevators:

{{diagram|spaces=yes|\
z +0 z +1 z +2 z +3
░░░░░ ░░░░░ ░░░░░ ░░░░░
░╔░░░ ░▼╚╗░ ░░▼▼░ ░░░░░
░╝░░░ ░▼░░░ ░░░╔░ ░░░▼░
░▼▼░░ ░░░░░ ░░░╝░ ░╚╗▼░
░░░░░ ░░░░░ ░░░░░ ░░░░░

z +0 z +1 z +2 z +3 z +4 z +5 z +6 z +7 z +8 z +9
░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░
░▼░░ ░░╗░ ░╔▼░ ░▼░░ ░░░░ ░╔╝░ ░▼▼░ ░░░░ ░░╗░ ░╔▼░
░╔╝░ ░▼▼░ ░░░░ ░╚░░ ░▼╝░ ░░▼░ ░╚░░ ░▼╝░ ░░▼░ ░░░░
░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░ ░░░░

░ : Wall
╔,╚,╗,╝ : Track/Ramp
▼ : Down Ramp (empty space)
}}

Note that these impulse elevators, due to the checkpoint effect and upward curved ramp effect, will not actually result in carts traveling straight up the ramp. They will lose speed, bounce off a ramp, then be accelerated back into the spiral after a 9-turn delay on both tiles on the floor where they are stopped. This is because the checkpoint effect allows carts to travel up the ramps in a single turn, but also prevents the impulse ramps from adding acceleration unless the cart is slowed to staying on the ramp for more than one turn. Initial acceleration will carry the cart up a variable number of floors before this effect occurs, but this bouncing back and forth will occur every 5 z-levels after the first time the cart stops. When the cart ''is'' traveling upwards, it will pass every tile at a rate of one tile per turn regardless of its actual speed, due to the checkpoint effect. In tracks with only a single cart, this is negligible, but when multiple carts are on the same track (such as when you place multiple carts on a magma cart lift) this can cause collisions which derail carts, or cause other unexpected or undesired behaviors.

The following impulse ramp (while larger) should alleviate these problems by using a straight ramp to go upwards, preceded by an impulse ramp to exploit the checkpoint effect and negate up ramp costs. Corners still decelerate carts, so the cart will tend towards a velocity of 72k, which is derail speed. Derail speed breaks (see Controlling Speed, below) may be necessary at the top.

{{diagram|spaces=yes|\
z +0 z +1 z +2 z +3
░░░░░░ ░░░░░░ ░░░░░░ ░░░░░░
░░░░░░ ░╔╔═░░ ░░▼▼╗░ ░░░░░░
░║░░░░ ░▼░░░░ ░░░░╗░ ░░░░▼░
░╚░░░░ ░▼░░░░ ░░░░║░ ░░░░▼░
░╚▼▼░░ ░░░░░░ ░░░░░░ ░░═╝╝░
░░░░░░ ░░░░░░ ░░░░░░ ░░░░░░

░ : Wall
║,═,╔,╚,╗,╝ : Track/Ramp
▼ : Down Ramp (empty space)
}}

Also, if you want to have a cart following a below-derail speed, the following track works well:
{{diagram|spaces=yes|\
z +0 z +1 z +2 z +3
░░░░░ ░░░░░ ░░░░░ ░░░░░
░░░░░ ░══░░ ░▼▼║░ ░░░▼░
░║░░░ ░▼░░░ ░░░║░ ░░░▼░
░║▼▼░ ░▼░░░ ░░░░░ ░░══░
░░░░░ ░░░░░ ░░░░░ ░░░░░

░ : Wall
║,═ : Track/Ramp
▼ : Down Ramp (empty space)
}}
In this elevator, the cart collides with the walls in the corners, but then realigns on the ramp, picks up speed, checkpoints through the next ramp, and slams into the next wall. It is slower (10 ticks per floor) but produces reliable speeds, and will exit the impulse elevator at little more than push speeds.

A sort of opposite effect to impulse ramps also exists: ramps lacking the proper "up" and "down" connections are treated as flat track, even if they actually go up or down z-levels. This allows building "anti-impulse" slopes consisting entirely of ramps only connected up, which a minecart can travel up forty levels and more, needing no more than a single push.

=== Controlling traffic ===

==== Switching ====

As tracks are constructions or tile features, [[door]]s and other furniture can be built on them. A [[door]] or [[floodgate]] can be turned on or off by a [[lever]], effectively controlling the flow of automated minecarts. This may be <s>dangerous</s> [[fun]], however.
{{diagram|spaces=yes|\
->
A ════┤≡════ B
┤ : roller pushing to East
≡ : door
}}
The roller pushes the cart east, but until the "departure condition" is fulfilled, the door remains closed and blocks the path.

[[Bridge]]s can also act as tracks, but only if they're lowered or not retracted. This property can enable levers to turn tracks on and off. However, care should be taken to ensure that such bridges are never operated while a cart is on top of them, as the cart will be flung off the track. It's worth noting that it's often faster, and cheaper, to construct large bridges than long sections of constructed track.

A powered track switch can be constructed by building an "inverted" corner as illustrated below.
{{diagram|spaces=yes|\
B B
║ -> ║
║ ║
════╚═══ ════├════
A C A C
├ : roller pushing to West.
}}

If the cart is pushed East from the stop at 'A' while the roller is activated, it will arrive at 'B'. If the roller is not running, it will arrive at 'C'. The switch works by the roller first reversing the incoming cart's movement and the cart ''then'' following the track corner.

This switch is very reliable, reacts instantly to on/off signals, and carts of any speed can be switched by this design, although very fast carts will require rollers that are several tiles long, up to three. The requirement for power can be inconvenient or impractical. Non-powered solutions may use controlled derailment, or a connecting bridge.
{{diagram|spaces=yes|\
B ╥
║
║
╞════╝ ════╡
A D C
}}
Here the track between A and C is not continuous. The only continuous track is A->B, with a corner (not a T section). Fast moving carts will tend to derail at D and rejoin the track to C. Placing a door at D will prevent the derailment, so the cart continues to B. The door is operated by mechanisms elsewhere (typically, a lever, but some fun can be had with pressure plates).

Since it depends on derailing, this switch requires a very fast cart, faster than what can be achieved with rollers alone. To gain sufficient speed, a cart must be accelerated further, usually by descending several levels or through impulse ramps. The high speed makes the cart much more dangerous and harder to control.

If carts are moving too slowly to derail at the corner, a retractable bridge may be used as a connector between A and C.
{{diagram|spaces=yes|\
B╥
║
║
A╞════bbb════╡C
}}
The bridge must overlap the corner. Bridges behave like a track crossing, allowing carts to pass in a straight line. When retracted, the corner reappears, so the carts will continue to B. Bridges take 100 steps to react to a signal, necessitating rather long "lead times" when switching tracks via bridge.

As mentioned above, special care must be taken to make sure the bridge doesn't change state while the cart is passing over it. Retracting bridges will throw the cart, causing it to stop dead. Raising bridges can even crush the cart.

==== Controlling Speed ====


Minecarts can reach extremely high speeds, especially when descending multiple Z-levels. A minecart will derail at a track corner if its speed exceeds 0.5 t/st (tiles per step), '''unless''' the route in the direction of travel is blocked:

Will derail at > 0.5 t/st:

{{diagram|spaces=yes|\
in ══╗ -> derailing
║
out
}}

Will not derail at > 0.5 t/st:
{{diagram|spaces=yes|\
in ══╗O
║
out

O : wall/column.
}}

This behavior can be used to build a "speed limiter", that will ensure that when a minecart exits it is traveling below derail speed, as illustrated in these three examples:
{{diagram|spaces=yes|\
░░░░ ░░░░░ ░░░░░
in ═╔═╗░ ░╔S╗░ ░╔S╗░
out ═╬═╝░ out ═╗═╝░ out ═╗═╝░
░╚S╝░ ░╚═╝═ in ░╚S╝░
░░░░░ ░░░░ ║░░░
in
░ : wall
S : Track Stop (High Friction or lower)
}}
If the minecart is traveling below derailment speed, it will not be affected; if above, will be slowed down and checked again. Granted, you could do the same just with track turns, but it may take a lot of turns and time.

Since all the derailings, bounces and ramps can impart a sideway component of speed small enough to start visible drift many tiles away (say, [[Fun|in the middle of a bridge]]), track turns have one more use: forcing the carts to move strictly along the grid directions. Carts passing a turn below derailing speed convert one component of velocity into another, thus eliminating the drift.

=== Loading liquids ===
[[Water]] and [[magma]] can also be loaded into minecarts by submerging them to a depth of at least 6/7 while standing still or moving at speeds of at most 10000. Loading fluids onto minecarts can be difficult because the added friction provided by fluids can stop a cart in a submerged tile. Curiously, filling a minecart with magma does not injure a dwarf ''riding'' it. A minecart will hold enough fluid to increase the depth of a single tile by 2. This amount is listed as 833 units, which weigh 459Γ (water) or 999Γ (magma). An iron or steel cart filled with magma weighs 1313Γ, while an adamantine cart filled with magma weighs 1007Γ. Since you need a minecart above the liquid's level, possible arrangements may include pressure-activated sluices, rollers (with magma-safe chains for magma), pouring from above to "submerge" it briefly on the same level and drain excess away (dig deeper and leave a vaporizer, though if you could have power for rollers, may as well use a pump) and exploits with ramps (not necessarily impulse ramps, "same height" passing dip does it).
The liquids can be dumped by a constructed track stop.

== Quirks ==
This little quirk concerns dwarf-managed minecarts. If a track which was previously open becomes blocked (ex. flipping a switch connected to a floodgate you've built on the track to raise it) and the conditions for departure are met, instead of refusing to ride/guide the minecart or ride/guide it until it reaches the obstacle, the dwarf will pick up the minecart off the tracks and haul it to its scheduled destination on foot. If the distance is long enough and the weight of the cart heavy enough (due to being filled with heavy items such as stones), the dwarf may drop the cart because of fatigue/hunger/thirst before reaching the destination. This will cancel that vehicle setting job and make another dwarf come by and attempt to haul the cart to the nearest appropriate stockpile where another dwarf will pick up the cart and attempt to haul it to its initial stop. If the stockpile is far enough from initial stop, this second dwarf who is attempting to place the minecart on its tracks may also drop the minecart out of fatigue/hunger/thirst creating a loop that will go on until a dwarf with enough endurance manages to place the minecart where it belongs.

In fact, it seems dwarves are more than happy to attempt to carry a minecart from one stop to another even if just waiting until the track is open again would be the more sane option.

Dwarves will also carry a minecart to its next stop if the direction specified is incorrect (or invalid). This can often occur when using the default departure settings and forgetting to set the direction of each condition.

Dwarves can admire buildings while riding mine carts. Dwarves will not fall asleep during a ride (at least not from being drowsy). If riding on a continuous powered track loop, the dwarf will die of dehydration/starvation as they can not jump off to get sustenance.{{cite forum|109460/3377228}} Dwarves riding in submerged minecarts will gain experience in [[swimming]].{{cite forum|129889}}

Tracks block wagon access to trade depots, unless they're on a ramp. [[Bridge]]s can also be used, as they function as tracks but do not block wagons.

== Physics ==


Minecart physics depend greatly on the departure mode set in the route stop conditions.

When set to "Push" or "Ride", minecarts will move according to the regular laws of momentum, gaining speed when going downhill, losing it slowly due to friction when on a flat plane, and more quickly when going uphill. In these modes, minecarts will move in a straight line until they either are brought to a stop by friction or an obstacle, or until they encounter a turn. A minecart will roll straight past "blocked" ends of T-junctions or track ends, they have no power to restrict a cart's movement. The cart's behavior is largely independent of the weight of its contents (including fluids and dwarves): heavily loaded carts gain more momentum when accelerating, but this only plays a role in collisions: a heavy cart gains just as much speed and is as easy to stop as a light one. In either case, dwarves can not push nor ride an unpowered cart up a ramp, bouncing back the direction it came. At best, this is a waste of time; at worst, it will give your cart-pushing dwarf a [[fun|fun surprise]]. To solve this, the player can either use Rollers (see below) or set the cart to be Guided.

The difference between "Push" and "Ride" is whether the dwarf will go along with the cart or not.
{{DFtext|Push}}: the dwarf will give the cart an initial push, not enough to go up a ramp, but enough to go some way along flat track, and the dwarf will remain at the first stop, ready for a new job.
{{DFtext|Ride}}: the dwarf will give the cart the same initial push and then hop aboard the cart riding with it to the next stop.
{{DFtext|Guide}}: minecarts seem to ignore all laws of physics. That is:
*Ignore the weight of any and all items inside. Therefore:
**Move at the speed of the dwarf that is guiding them. It is thus recommended to pick the most [[attribute#Agility|agile]] of your dwarves for cart-guiding tasks.
*Ignore working rollers.
*Will ''not'' collide with other guided carts even when a full frontal collision would be expected.
*Will go up ramps like nobody's business.
This is therefore the recommended method of transport for simple non-powered rail systems, despite it diverting a dwarf from other, potentially more important tasks.

Some samples with behavior:
{{diagram|spaces=yes|\
A <-> B A <-> C A <-> B
B B B
║ ║ ║
A══╝ A══╩══C A══╬╗
You can only go A->B ╚╝
Works when the cart Works
is in Guide mode.
}}
In the second example above, a cart "pushed" from B will go over the junction and roll off into the unknown south.

=== Numbers behind the scenes ===

According to early research by '''expwnent'''{{cite forum|112831/3536975}}:

The minecart has 3 variables for velocity. Velocity can be thought of as tiles per 100000 ticks, so a velocity of one hundred thousand means a cart travels one tile per tick. By going down a large number of ramps, a maximum velocity of 270,000 can be reached, which presents the limit for most practical applications. Short bursts of (much) higher speeds are possible through carefully planned collisions of high-speed carts.{{cite forum|137557/5145499}} (See [[#Perfectly Elastic Collisions|Perfectly Elastic Collisions]].)

Every tick the cart adjusts sub-tile position units by the amount of their velocity, as well as adjusts velocity depending on current tile (speed is reduced by the "friction" of the tile, or accelerated if going "down" a ramp). On flat (non-ramp) tiles, the cart will move to the next tile when the sub-tile position goes 50000 away from the centre of the tile, denoted by the no-fraction integer value - tile 15 e.g. has its centre at the exact value 15 and its borders at co-ordinates 14.5 and 15.5.

Since most deceleration and acceleration is applied per step, with the notable exception of corners, a cart going at twice the speed of another one can travel about four times the distance before coming to a stop when going in a straight line, but only twice the distance along a winding track with very many corners.

A push will teleport a cart to the middle of the next tile in one tick with 19990 speed (10 speed is lost due to track friction), while a roller will directly give a cart the roller's set speed (minus friction) and the cart starts accumulating distance from its standing position. When a cart leaves a ramp it will emerge after one tick at the very end of the next regular tile.

Friction of tiles:
{| class="wikitable"
|-
! Tile
! Friction
! Comment
|-
| Tracks
| 10
|-
| Ground/Floor
| 200
|-
| Unusable ramp
| 10
|-
| Upwards ramp
| 4910 (10+4900)
|-
| Downwards ramp
| -4890 (10-4900)
|-
| Roller
| ±100000 (but capped by the set speed)
|-
| Corner track
| 10
| Speed reduced by 1000 upon leaving the corner tile
|-
| Track stop (highest)
| 50000
|-
| Track stop (high)
| 10000
|-
| Track stop (medium)
| 500
|-
| Track stop (low)
| 50
|-
| Track stop (lowest)
| 10
|-
| Water 1-6
| Additional (WaterLevel - 1) * 100
| rowspan="2" | [[#Skipping|See Skipping]]
|-
| Magma 1-6
| Additional (WaterLevel - 1) * 500
|-
| Empty space
| 0
|}

Water of depth 7/7 provides a friction of about 10000 per step. Maximum-depth magma causes at least as much friction, possibly more. This higher friction may not apply to very slow-moving carts.

Impulse sources:
{| class="wikitable"
|-
! Feature
! Speed
|-
| Push
| 20000
|-
| Roller lowest
| 10000
|-
| Roller low
| 20000
|-
| Roller medium
| 30000
|-
| Roller high
| 40000
|-
| Roller Highest
| 50000
|-
|}

Note, again, that nearly all of these values are applied ''per tick'', rather than ''per tile''. The exceptions are curves, which is 1k deceleration per direction change at the end of the tile, and rollers, which ''set'' the speed every tick. This makes rollers particularly useful in high-deceleration situations, such as underwater, but require that ''nearly every tile'' in such high-deceleration situations have a roller.

A cart heading up a ramp can experience deceleration on multiple ticks, (and stays on the tile more ticks the slower it is going, resulting in greater deceleration,) and as such, a cart leaving a "Highest Speed" roller with 50k velocity will not be able to climb 10 consecutive straight ramps, since they are ''not'' "5k deceleration each". In fact, the first ramp not on a roller will be -15k velocity, and, depending slightly upon other factors of "remainder" x position, the second may completely cancel forward momentum, and send it rolling back down, where it will bounce off the roller repeatedly. Using rollers to power carts up ramps reliably requires rollers every other un-rollered ramp. Fortunately, rollers can be built upon ramps, themselves, which allows for rollers to only need to be built every other floor. (Exploiting the [[#Checkpoint Effect|checkpoint effect]] can allow one to bypass this requirement.)

There are two important speed values which affect carts' behaviour:

"Derailing" can happen when a cart moves at speeds in excess of 50000 - carts will ignore track corners unless forced to obey them by walls or other obstacles blocking the straight path.

The "shotgun" effect takes place when a collision changes a cart's movement speed by more than 55000: loaded carts subject to such a change eject their contents, which then keep on moving in a ballistic trajectory, in the direction and at the speed the cart had before the collision (with a small random vector added). This effect entirely rides on the amount of speed ''change'' - a speeding cart crashing into a wall can be subject to it just as well as a standing cart accelerated by a speedy cart smacking into it. It can even happen when two relatively slow-moving carts (down to speeds below 20000 in extreme cases) collide head-on.

=== Sub-tile Positions and Velocity ===
Carts store six values that are unique to them. Three sub-tile position values, and three velocity values. (X, Y, and Z.)

Note that the Z position and velocity only matter when a cart is in flight. (See [[#Falling|Falling]] and [[#Cart Jumps|Cart Jumps]].)

Each non-ramp tile is functionally composed of 100,000 individual minimal-length positions ''within'' the tile in both dimensions. When a cart has velocity, it is added or subtracted from the current position every tick, and then a friction force is applied to the cart.

In essence, every sub-tile position unit is a decimal value of a tile, 0.00001 tiles, in a game that largely prefers integer values.

The exact cart coordinates shown e.g. by a DFHack script must be rounded arithmetically (up or down to the nearest integer) to find the current tile: a cart in the centre of a tile will be at sub-tile zero in all directions, and it will cross into the next tile when subtile value is more than 50 000 higher or lower than the full number.

When carts move beyond the borders of a tile, they physically move a tile on the map, and start at the far end of the sub-tile position the next tile. (I.E., traveling West, a cart that starts a tick 15,000 X away from the border and has an X velocity of -20,000 will move -5000 X past the adjacent border of the next tile in direction -X. It will also lose 10 velocity in that tick due to friction with the track if it is on a track, or 100 velocity if it is on regular ground, or no velocity if it is airborne.)

Ramp tiles are longer, approximately 141,420{{cite forum|157627/0}} in the direction where it "slants downward", (to approximate a 45 degree slope, it is square root of two times longer,) with a centre-to-border distance of 70,710. Because of this, a cart with no velocity dropped from a hatch will land at the center of a tile, 70,710 away from the tile's borders in both directions, and will start rolling in the ramp's "downward" direction, picking up the ramp's acceleration (4890 per tick in the direction of the ramp's "downward" direction) every single tick, then moving that sub-tile amount every tick. (This results in a cart that takes 5 ticks of acceleration to leave its ramp - 6 ticks overall - and to leave the ramp with about 23k velocity, slightly more than a push.) When it enters another ramp ''facing the same direction downwards'', a cart will start at the -70710 or +70710 position, and have twice as far to travel. This means that if a cart enters a ramp from the side, it will gain twice the momentum of simply starting at the midpoint of a ramp.

Note that passing from one direction of ramp to another or to flat terrain causes unintuitive behavior, "teleporting" to the end of another tile in what is called the "[[#Checkpoint Effect|checkpoint effect]]".

Note, however, that all sub-tile positions are carried over from tile-to-tile. This separate tracking of velocity and position between X and Y can lead to problems with diagonal motion:

{{diagram|spaces=yes|\
z0 z-1
▒║▒ ▒▒▒
═▼═ ▒╬▒
▒ ▒ ▒║▒
▒ : Wall
═, ║ : Track
╬ : Track and Ramp
}}

If a cart is passing West-to-East over this setup, the valid ramp to the South will apply "Southward" acceleration to the cart (-Y velocity) as it passes through the ramp tile. Assuming it only spends two ticks in that tile, it will have gained a lasting -5k Y velocity, which will still apply motion Southward. If the cart continues travelling over straight track for another ten steps, it will have accumulated enough Southward motion to try to move a tile South, even if all tracks are facing East-West.

A single tile spent on the ramp will not grant lasting southward motion, because the acceleration will be neutralised through the checkpoint effect when the cart leaves the ramp again, but the cart will be displaced about 5k sub-tiles southward, which can cause it to gain more or less speed than an undisplaced cart when meeting another south- or north-accelerating ramp.

'''Non-curving tracks do not correct this motion'''.

They don't "tip back over" without adjustments in the track. Any value of sideways motion on tracks larger than 990 will lead to a derailment. (Lower values will be nullified by friction before they are enough to lead to derailment, but there is currently no way to apply such a small amount of velocity.)

If the tile to the South is a wall at that point, it will be considered a collision with a wall that ''halts all motion''. If the tile is open, the cart will simply leave the track and travel over the terrain beside it. In almost any circumstance, this is undesirable behavior.

The only way to appropriately deal with this is to either cancel out this behavior with an equal amount of acceleration in the opposite direction, or to take a curve.

Note, again, that sub-track position is saved in both directions, so when a cart approaches a curve, it will already have a shorter or longer distance past the curve when it makes the turn.

Curves are applied at the end of a tile. If a cart is moving East, and approaches a North-West track corner at 30k velocity, and friction is eliminated for the purposes of a cleaner demonstration, then when it enters the tile on the western (X coordinate) border of the tile, but in a central North-South (Y) orientation (sub-tile -50k X and 0 Y due to arithmetic rounding), it will then move 30k East (+X) the next tick, and be at -20k X sub-tile position, and 0 Y sub-tile position. Next tick, it is at +10k X sub-tile position, and 0k Y sub-tile position. Two more ticks would take it to +70k X, but that's past the tile border, so it stops at 50k, turns (and thus loses 1k velocity, but translates the rest from X-velocity to Y-velocity) and travels another 20k. It is now at 0k X sub-tile position, and -20k Y sub-tile position (i.e. it's re-set from the end to the middle of the tile with respect to the X co-ordinate). Next tick, it travels at 29k velocity North, and so moves to 0k X sub-tile position, and +9k Y sub-tile position. Then in two more turns, it leaves to the North.

In the case of diagonal motion due to having velocities in X and Y at the same time, it is critical which tile the cart actually tries to enter next. Only if the path into that tile is blocked by the corner branches will the cart take the corner and rewrite its velocity, otherwise it leaves the corner tile without changes to its motion. If the cart is redirected by the corner, all sideways velocity is lost, as forwards velocity ''overwrites'' sideways velocity in a curve. If, in that example in the paragraph above, the cart entered at -50k X sub-tile position with 30k X velocity, and 40k Y sub-tile position and -1k Y velocity, it would take that "curve" (or rather, redirection of velocity) on the fourth turn, while it is at 37k Y sub-tile position to start with, and then move to -53k Y sub-tile position at the end of that tick. It would then move to -26k Y sub-tile position in the following turn, and take 3 turns to clear the tile.

But, most importantly, it would be centered in the X sub-tile position, and all sideways velocity is safely removed.

There are two common ways to gain sideways velocity: Rollers facing perpendicular to the cart's travel path (which, as covered above, are almost always a bad idea, as it is easier to push ''against'' the travel direction of a cart into a curve, which redirects all velocity in the new direction,) and [[#Corner Ramp Derail|corner ramps]], and require a curved track to compensate for sideways velocity within a few tiles.

=== Track Direction Irrelevance ===
Carts that are traveling independently (that is, not guided) only care that tracks ''are'' on the tile, not which direction the tracks actually move. Tracks respect only curves (with two exits) and ramps.

This means, for example, that the following tracks, when a (non-guided) cart travels from West-to-East, are functionally identical in effect:

{{diagram|spaces=yes|\
A════════════B A╬║╚╔╣╩╦╠╥╨╞╡B
}}

This is because so far as the cart is concerned, only valid ramps and curves with two exits where there is no exit in the path they are traveling matters.

Hence, if a minecart encounters the end of the track or a T junction with no "exit" in its movement direction, it will simply leave the track and continue on its course in a straight line until it encounters an obstacle, slows to a stop, or encounters another track even if the tile at which it joins the new track instantly sends it around a corner.

In fact, in a track designed for pushes or rides, a "║", a "╦", a "╬", and a "╥" are ''only different in appearance'', and are ignored by an unguided cart, which will continue in its current direction, regardless of the track. For any purpose but guided tracks, ''only curves and ramps matter at all''.

Tracks like T-junctions, however, ''are'' respected by dwarves guiding carts, who will lift and carry carts if they cannot find a valid track to their destination, and can choose to follow any orthogonal direction at a four-way junction in much the same way as they normally pathfind. What this functionally means is that T and four-way junctions ''only guide dwarves hauling a cart, not carts, themselves''.

Carts only check for curves when they are halfway through a tile. When they get there, they look to see if their path has no exit. (That is, if it is traveling East, it checks if there is an East exit.) If there is, it ignores all other track directions, and keeps traveling. If there is not, it checks to see if there are only two exits to the track, and if one of those directions was the direction it "came from". (That is, if traveling West from the East, it checks if there is a valid exit to the West, and if not, if there is an East exit and EITHER a North or South exit.) If there is not, it ignores the track anyway, and keeps on traveling as though it were still on track.

If there is a curve the cart will respect, it checks for derailment. Carts derail if their speed is higher than 50k. Carts at this critical speed will then check for blockages of their forward path. If there is an obstacle to their path, which may be a wall or even furniture or buildings like a door, they will not derail and respect the curve, anyway. Derailing carts do not "[[#Cart Jumps|jump]]" unless they hit completely untracked tile or an invalid ramp, but simply ignore the layout of the tracks entirely. With invalid ramps, this means not respecting the ramp, and likely results in collision with a wall, zeroing of all velocity, and a cart that requires manual retrieval.

If the cart is traveling at a speed that will not derail, or is forced to turn by a supporting wall, it will subtract 1000 from the "forwards" velocity of the cart, and redirect all forward velocity to the direction of the curve. This change in the direction of velocity ''overwrites'' any "diagonal" velocity, which can prevent diagonal velocity derailments, but any perpendicular velocity is not preserved, and is instead discarded.

=== Valid and Invalid Ramps ===
Ramps are functionally defined for cart purposes as being a tile which exerts an acceleration force upon its "downward slope", and which allows connection to tracks a z-level above or below. This downward slope requires a cart to have at least one track branch touching a wall tile and one ''and exactly one'' carved exit to the tile that is the "bottom" of the ramp. Ramps accelerate carts in this "downward" direction (possibly leading to [[#Corner Ramp Derail|diagonal movement]]), and the deceleration of an "uphill" ramp is actually just the acceleration being applied against the direction of a cart's movement.

This is where players can find an exploit in the behavior of ramps - if there are ''two'' "downhill" exits to a ramp (such as a "T junction" on a ramp where only one exit faces a wall), then the ramp provides no acceleration ''or'' deceleration, allowing carts to travel up ramps without any loss of momentum except for the standard "flat track" deceleration, because as far as the cart is concerned, the track ''is'' flat. (A T junction is also not a curve, so the track is considered flat and straight no matter what direction the cart is traveling.)

Similar effects can be achieved when there are ''no'' "downhill" exits to a ramp. This may be the case if you have, for example, an East-West track with a one-tile channel with a ramp in it. The cart will travel through the "dip" with no change in velocity. It can also be the case if you abuse the [[#Track Direction Irrelevance|Track Direction Irrelevance]], and set only exits ''up'' the ramp, and none leading ''down'' the ramp. For example, if a cart is traveling from West to East up a slope, only carving East exits on each tile of ramp will make the cart travel up the ramp, and then recognize the tile it is on as being a "flat" tile, thus ignoring any deceleration from traveling uphill.

Note that this effect only reliably occurs at below-derail speeds as the cart will treat the ramp as an invitation for a ramp jump otherwise. (This almost always results in a collision with a wall that will stop forward progress.)

=== Falling ===
When falling, a minecart appears to cause no damage upon collision, possibly to allow cart "stacking" across Z-levels.{{cite devlog|2012|04|06}} A dwarf riding in a minecart that is dropped multiple z-levels suffers normal fall damage. Minecarts can fall through up/down stairs.

While airborne, carts do not feel the effects of friction in any horizontal direction, and will continue until they strike an obstacle. Carts that land on tracks instantly re-rail themselves regardless of track directionality.

Falling carts accelerate similarly to the way that a ramp will accelerate a cart in a special z-only velocity that only applies to airborne carts. (Actually, since a tile is notionally 1.5 times as high as it is wide/long, acceleration due to gravity in freefall appears slightly ''slower'' than ramp acceleration, since it has to move the cart (or any other object) a greater distance.) Ramp acceleration, while it logically should be partially z-directional, is only recorded as x- or y-directional, and there is no translation of z-directional velocity upon landing. Landing carts zero out their vertical velocity upon landing, even when landing on ramps, although carts that had horizontal momentum while falling preserve it.

This means a cart falling onto a track ramp is accelerated as if starting from the middle of the ramp - i.e. to the same speed, no matter how many Z-levels it was dropped, vertical velocity is negated. {{cite forum|144328/5701211}} As a consequence, the fall damage to passengers is also negated.

Carts falling onto a floor can, however, cause damage to creatures ''one tile below the floor''. This can be used in an [[exploit]] called a "thumper", where carts are caused to repeatedly fall on a floor above an entrance to the fort, inflicting significant damage (as though it were a collision) on those below the cart.

=== Cart Jumps ===
Carts that cross off of "up" ramps relative to their current direction of travel, which do not have a ceiling above them, are traveling above derail speed, and do not have valid ramp track before them can translate a portion of their horizontal velocity into vertical velocity, causing a cart to be projected into the air until vertical velocity is negated and overcome by the gravitational acceleration. Because downwards acceleration is applied per-tick, this creates a reasonable facsimile of the parabolic motion of an actual object rolled up a ramp and launched with significant speed.

{{diagram|spaces=yes|\
z0 z0 hiding ramps z+1 A z+1 B (hidden ramp)
▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒
═▲▲▲▲▲══▲▒▲═ ═╚╚╚╚╚═══▒══ ▼▼▼▼▼ ▼═▼ ▼▼▼▼▼ ▼╚▼
▒ : Wall
═ : track
▲ : Ramp
}}
In this diagram, if there is no ceiling above it, the track in z+1 A will launch its carts airborne when they travel across the ramp. z+1 B (with a ramp on the tile on the hill) will not launch the cart. The cart would also not be launched with ''any'' valid ramp, even if it does not travel in an appropriate direction, such as North/South (which the cart will ignore, as it is not a curve, anyway, although it may produce acceleration that may cause diagonal movement.)

Carts that are traveling at derail velocity will also start "jumping" from the track if it hits an un-tracked tile, flying over and ignoring any tracks until it is ready to land. Carts that land upon tracked tiles re-rail themselves, and clever designers use this feature to jump over curved track sections in one direction or another. (Retracting bridges over untracked tiles can cause jumps or not cause jumps depending upon the status of the bridge.) Minecart speed must be carefully regulated to ensure reliability of jump length.

Hitting untracked tiles at around 70k velocity creates a vertical component to acceleration that allows for jumps of around 6 (horizontal) tiles that do not actually leave the z-level the cart is on, but which do apply z-direction velocity on the cart, as per falling.

Carts that approach a downward slope at a high enough velocity will also make a jump, (or rather, ignore the ramp and fly forwards) but will not do so if the [[#Checkpoint Effect|Checkpoint Effect]] is exploited through an impulse ramp before the actual downhill as the impulse ramp "tricks" the cart into thinking it has already started going downhill.

=== Skipping ===
If a minecart is moving fast enough, it can skip over [[water]] or [[magma]], making splashes of [[mist]] (or [[magma mist]]) as it attempts to move on them horizontally. This horizontal movement is independent of the minecart and its content's [[weight]].

Skipping causes significant friction on the cart, and even a cart going at max speed from ramps can only make about 50 tiles without requiring re-acceleration. (Carts that decelerate enough that they do not trigger the skipping effect will, of course, sink.)

=== Corner Ramp Derail ===

Corners on upward ramps can cause diagonal movement, forcing a derail even if the cart has a wall next to it, which will force a stop when it touches a wall that forces dwarves to manually reset the cart.

This is caused by the fact that a cart, after turning the bend in the track and entering e.g. a flat tile, will be subject to the checkpoint effect which applies 5k acceleration opposed to the last amount of ramp acceleration it received. Since the cart has just passed a corner, this compensatory speed adjustment now goes to the "outside" of the corner and creates enough lateral velocity to carry the cart off the track after eleven steps. (Down corner ramps do not have this problem, as the downward direction is in line with the past-corner movement direction and the checkpoint effect works on the only remaining movement vector.)

There are two fixes to this problem. One is to simply not put corners on up ramps. The other is to "cancel" the lateral speed after a cart has passed the ramp, either by sending the cart through another corner or by putting a high-friction track stop on the exit tile. In the latter case, the cart will lose 10000 speed in the desired direction, but the same speed loss will apply to the undesired lateral speed, nullifying it.

=== Checkpoint Effect ===
The checkpoint effect, [http://www.bay12forums.com/smf/index.php?topic=144328.0 explained in depth by Larix], is an odd and highly exploitable feature of ramps where minecarts "teleport" through the next tile of track, ignoring nearly all minecart physics (except that they stop at all walls or other obstacles and only respect curves with no backing wall and invalid ramps if they are below derail speed) and passing through that tile in just a single tick, and to the very end of the next tile.

This effect occurs when a cart leaves a downward ramp for any other direction of tile. (This includes ramps which accelerate in different directions, even a ramp which goes from accelerating East to accelerating North due to a bend in a chain of standard down ramps in a curve.) This allows, for example, two valid straight ramps directly next to one another with a cart dropped onto one or the other with no momentum to have the cart pick up acceleration going "down" the ramp as normal, but then flying up through the "up" ramp it travels into with no loss of momentum, as though it had come from an impulse ramp. If the two ramps had at least one space of distance between them, and then a cart were dropped in, the cart would instead "rock" back and forth between the two ramps.

This seems to be because ramps have a slightly longer length than regular tiles - 141,420, rather than 100,000 distance. When this "snaps back" after a ramp, it seems to project the cart suddenly further along the track, making it jump a tile ahead even when otherwise moving at relatively low speeds.

This [[bug]] is the cause of a ''wide array'' of unexpected behavior among people who do not take this bug into account. It causes derailments or failure to climb up seemingly valid impulse elevators. In general, it makes a system that behaves extremely counter-intuitively, and operates ''any time a cart encounters a valid ramp''. At the same time, when its effect is accounted for, it is highly exploitable: It causes "perpetual motion devices" using no power when two opposing ramps are placed next to one another, since the "uphill" effect of the opposing ramp is ignored, preventing deceleration.

Another useful thing to note about this exploit is that carts traveling at no less than 71,000 or so speed (enough to travel half a ramp tile in a single tick) can travel through every tile in just one tick at no change in velocity as long as the tiles alternate between impulse ramp or actual down ramp and any other tile type. The cart checkpoints through the non-down-ramp tiles, and can pass through the (impulse) down ramp tiles in a single tick, before they can actually start gaining momentum.

{{diagram|spaces=yes|\
▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒
═▲═▲═▲═▲═▲═ ═╚═╚═╚═╚═╚═
▒ : Wall
═ : Normal track
▲/╚ : N/E Track/Ramp
}}

If the cart enters from the West at less than 72,000 speed, some of those ramps will cause Eastward acceleration.

This means that an impulse ramp not contiguous to other impulse ramps has a top speed of around 75k:

{{diagram|spaces=yes|\
▒▒▒▒▒ ▒▒▒▒▒
▒╔═╗▒ ▒╔═╗▒
▒╚▲╝▒ ▒╚╗╝▒
▒▒▒▒▒ ▒▒▒▒▒
}}
This setup makes a cart that travels clockwise at a speed that fluctuates around 75k velocity. If the cart has more than 72k velocity, it fails to accelerate in the ramp, as it leaves the ramp in a single turn due to checkpointing to the halfway point. After that, the curves sap 1k velocity, and every tick saps 10 velocity.

Two contiguous impulse ramps with a same-facing "downwards slope", however, do not suffer the checkpoint effect in the second tile, giving functionally triple the space to accelerate. This means it will add velocity (at the standard rate of 4.9k per tick) up to a maximum speed of 216k.
{{diagram|spaces=yes|\
▒▒▒▒▒▒ ▒▒▒▒▒▒
▒╔══╗▒ ▒╔══╗▒
▒╚▲▲╝▒ ▒╚╗╗╝▒
▒▒▒▒▒▒ ▒▒▒▒▒▒
}}
This example results in a cart moving three times as fast as the previous cart.

Three successive ramps results in the highest attainable speeds.

In practical terms, this means that only consecutive ramps should be used for high acceleration, but singleton ramps can be used to have speeds that are somewhat regulated.

=== Stacking ===
If a minecart lands on top of another minecart, they may form a stack, with the upper cart on the z-level above the lower. Subsequent carts do not form a stack, but rather quantum stockpile in the same space. This behaviour is useful for [[megaprojects]] and [[trap design]] with minecarts as the weaponry. Moderation should still be exercised: carts take longer to fall into a "stacking" tile already occupied by other carts and will spend that time "hanging" in the air above the stack. This can lead to following carts striking them, which can cause all kinds of malfunctions. The extra time is two game steps for every cart already in the stack, which doesn't hurt stacks of ten carts very much but makes stacks of 100+ rather impractical.

These minecarts on the upper level generally need to be struck with another minecart to move out, or have their support removed. The latter option is safest done by shooting it away with another minecart, manual removal of a stack-supporting cart typically causes the next cart from the stack to [[fun|fall on top]] of the hauler.

=== Perfectly Elastic Collisions ===
Minecart collisions are perfectly elastic, meaning that not only do minecarts not take damage, but that two carts that are rolling which have frontal collisions of near-similar speed, and where one cart is no more than twice the mass of the other cart, will result in a billiard-ball-like effect of the lighter cart bouncing off the heavier cart with a proportional speed increase dependent upon the relative momentum behind the heavier cart.

Using this trick with carts already at the 270,000 maximum speed from ramps can result in "supersonic" carts traveling at speeds in the millions (travelling a dozen tiles per tick), but where they are suddenly subject to 10,000 units of "terminal velocity" friction per tick. [http://www.bay12forums.com/smf/index.php?topic=137557.0 Thread with SCIENCE here].

While hypothetically capable of launching a minecart into orbit when used in conjunction with a ramp, no cargo can be contained in the launched cart, as the collisions will force ejections of the cargo. Your "unwilling volunteer" [[goblin]] space pioneers will simply become paste underneath the wheels of an extreme high-speed cart.

== Non-standard uses ==
Minecarts include some interesting characteristics that have motivated uses beyond hauling. They can be useful for creating fully-automated [[Quantum stockpile|quantum stockpiles]], [[garbage disposal]]s, [[Water_wheel#Micro_Water_Reactor|water reactors]], and [[portable drain]]s. Storing perishable goods (meat, meals, etc.) inside a minecart appears to guard against rot and vermin.
Minecarts can be [[Trap_design#Minecarts|used as weapons]], or as (hopefully non-fatal) triggers to restart stalled [[healthcare]]. They can also be used to time/control game events, either using a basic [[repeater]] or much more advanced [[minecart logic]].
Minecarts trigger [[pressure plate]]s, which means a trap can be designed to trigger when a thief attempts to steal a minecart.
A pressure plate can be used as automatic and more precise custom "launch when full enough" system - as long as weight of your minecarts stays the same. You cannot build a hatch or roller on the same tile, so launch by bumping with another cart. {{cite forum|15096/4580050}}
Dwarves riding minecarts can attack enemies within reach (which goes back to dev log). This applies to shooting, and they actually can hit targets while riding by.{{cite forum|109460/5266119}} Whether a minecart protects the rider and how it interacts with dodging is not known yet. Minecart riders can also [[Swimming#Minecart_training|train swimming]] and [[Megaprojects#Surveillance_Track|detect ambushers]].

== Simple Example Layouts ==

=== 2-way Minecart Route ===
[[File:Simple2wayminecart.PNG|500px|Simple 2-way Minecart Route]]

This is an example of how a 2 way route can be established.
* Stop 1 is non dumping, frictionless (Feeder Stockpile from North in this example)
* Stop 2 friction and dump (dumps South in this example)
* Stop 3 is non dumping, frictionless (Feeder Stockpile from North in this example)
* Stop 4 friction and dump (dumps South in this example)

Now you create a Route hauling your desired items from Stop 1 to Stop 2 . Immediately guide the empty cart to Stop 3 (because the stop has no friction, a kicked cart will overshoot the stop).
Haul desired items from Stop 3 to Stop 4. Immediately guide the empty Cart to Stop 1.

=== Automated Minecart Funicular (Elevator that also goes sideways)===
This is an example to set up stone delivery from multiple Z levels with a common set of tracks while automatically returning the cart to where it is supposed to go. In this example, the South track goes upwards towards the drop off point, the North track goes downwards for cart return.
The design pictured consists of the following:
[[File:MinecartFunicular.gif|frame|left]]
* Two ramps next to a wall spaced one tile apart
* Tracks on top of the ramps to make an inclined track
* A 3X1 channel dug down next to the ramps on the side opposite the wall
* 2 gear assemblies, one between the ramps, one over the middle channel
* Rollers on the upward track pointing towards the wall (South ramp in this example)
* A hatch over the channel next to your downwards ramp (North ramp in this example)
* A wall diagonally adjacent to the to the upwards channel
* Tracks leading from the hatch to the single wall
* A wall next to the curved section of track
* A pressure plate set to trigger on minecarts on the track underneath the minecart. Link the pressure plate to the hatch
* Set up a minecart route with one stop where the minecart is. Set the condition to kick the minecart in the direction of the channel with any condition and contents you wish
* Each subsequent level needs to be shifted one tile in the direction of the ramp down
{{clear}}
The unloading level just needs to pass the cart over a track stop set to dump in whatever direction you want, then send it back down the return track. It also needs to provide power to the rollers, 12 power is required per level.
[[File:MinecartFunicularTop.gif|thumb|left]]
{{clear}}
How it works
* The minecart sitting on the pressure plate keeps the hatch open so that other carts may pass
* When the cart is off the pressure plate the hatch closes. This causes the cart to pass over the hatch back to its loading position
[[File:MinecartFunicularHatch.gif|thumb|left]]
{{clear}}
== Adventure mode ==
In addition to being used for hauling, minecarts can also be ridden in [[adventure mode]]. (Adapted from forum thread {{cite forum|122903/4258212}})

# If the minecart is in your inventory, drop it. If it is already on the ground, proceed to step 2.
# Press {{k|u}} when you are 1 tile away from the minecart (or standing on the same tile as the minecart).
# You will be presented with the following options:
[[File:minecart adventure mode menu.png|left]]
{{clear}}
* If you {{DFtext|Push}} the minecart, it will move a few tiles in the direction you chose. Physics comes into play here, so it will gain/lose speed depending on the usual factors.
* If you {{DFtext|Ride}} the minecart, you will hop into the minecart, even if you were a tile away, and it will move in the chosen direction with you in it. It will gain/lose speed depending on the usual factors. Whilst the minecart is in motion, you should press {{k|.}} to skip your turn; if you attempt to move whilst the minecart is still in motion, the laws of physics come into play, and you will take [[wound|damage]]. However, it is currently possible to jump out of a moving minecart safely.{{bug|10104}} Alternatively, you can push the minecart whilst it's still in motion (although it's unclear how one can bend [[physics]] so as to push a moving minecart whilst inside the minecart). If you push it in the same direction you are already travelling in, you will greatly increase the minecart's velocity. You can also push it in different directions, and this will cause it to gradually change direction-the amount of pushes this requires depends on the minecart's velocity. Once the minecart has stopped moving, you may move out of it safely, or you may want to give it another push. Note that if you push a minecart right after having ridden it (still on the same tile as the minecart), it will act as though you chose to ''ride'' it.
* When the minecart is on a track, options appear to {{DFtext|Guide}} it in directions that the tracks lead. This moves the cart 1 tile in the direction it is guided. Guiding the cart is the only way to move a minecart from a maximum friction track stop (other than taking it into inventory.)

Minecarts in adventure mode are not restricted by a lack of tracks. However, they are hindered by natural ramps. Attempting to go up a slope will lead up the cart slamming into the wall. The good news is you'll make it over the ramp. The bad news is you likely won't stick the landing.

Note that while carts are a powerful weapon if heavy and fast enough, they have their limits, and a collision can sharply reduce the speed of a cart depending on what you hit, potentially enough to eject the rider. Trying to run over a human will send them flying, while trying to ram a dragon will not end well.

If you want to test this out without creating an adventurer, the [[object testing arena]] allows you to spawn minecarts ({{k|k}}-{{k|c}}-{{k|n}})

== Forging and Melting ==
* Metal minecarts cost '''two''' [[metal]] bars to forge, or '''six''' [[adamantine]] wafers.
* When a non-adamantine metal minecart is melted down, it will return '''1.8''' metal bars, for an '''efficiency of 90%'''.
* When an adamantine minecart is melted down, it will produce '''1.8''' wafers, for an '''efficiency of 30%'''.

== See also ==
* [http://www.bay12forums.com/smf/index.php?topic=109460.0 The "How Does Minecart" Thread] by '''Girlinhat''' et al.
* [http://www.bay12forums.com/smf/index.php?topic=112831.0 SCIENCE: Quantifying minecart physics] by '''Snaake''' et al.
* [http://www.bay12forums.com/smf/index.php?topic=129676.0 How to build a Multi-cart Ore to Magma Minecart Project without needing power] by '''WanderingKid'''. (Images recovered from wayback machine and posted here: https://imgur.com/gallery/LpRsDwO)
* [http://www.bay12forums.com/smf/index.php?topic=144328.0 My very own Minecart Education Thread. Ten Lessons, now complete.] by '''Larix'''.
* [https://www.youtube.com/watch?v=hctG2dQzHwg Real-life railcarts/conveyor hybrid] which uses similar mechanics.

== Bugs ==
*A dwarf will drop her [[child|baby]], if she has one, when boarding a minecart set to be ridden.
*Dwarves have no concept of traffic safety and will walk into busy minecart lines to retrieve objects, often with deadly consequences. This is especially problematic in [[Swimming#Minecart_training|clever applications]] depending on dwarves riding the carts very frequently, because they have a bad habit of dumping their worn clothes on the tracks after a minecart ride. Adding an automatically-operated [[hatch cover]] at the end of such a ride can help prevent [[unfortunate accident]]s.
*Dwarves cannot guide a minecart through an unlocked door unless another dwarf opens the door.{{bug|6056}}
*It is possible for a creature and minecart moving towards each other to pass without collision if they exchange tiles in the same tick.
*After a minecart ride, a dwarf will sometimes haul the minecart to a storage stockpile, leaving another dwarf to haul the vehicle back to the route.
*Minecarts falling onto a floor injure creatures in the tile below the floor.{{bug|6068}}
*If a minecart travelling at high speed hits a wall, it and its contents may go through the wall, or even end up embedded in it.{{bug|5996}}
*A minecart's initial velocity is not affected by weight, when pushed or launched from rollers.{{bug|6296}}
*Removing a stop that has a vehicle waiting on it may cause the game to crash.{{bug|5980}}
*Jumping out of a minecart in motion does not lead to injury.{{bug|10104}}
*Jumping into a stationary minecart can lead to significant injury.{{bug|10229}}

{{Gamedata|{{raw|DF2014:item_tool.txt|ITEM_TOOL|ITEM_TOOL_MINECART}}}}

{{Category|Fortress mode}}
{{Category|Interface}}

[[ru:Minecart]]

Trading

2022-12-09T01:19:05Z

Xjtu-blacksmith: ILL

{{Quality|Exceptional|20:10, 22 February 2017 (UTC)}}
{{av}}
{{buggy}}
[[File:Barter-Chickens for Subscription.jpg|thumb|300px|right|Bartering in the olden times.]]'''Trading''' in ''Dwarf Fortress'' first occurs in the first [[Calendar|autumn]] after establishing your fortress, with the arrival of the [[dwarf|dwarven]] [[caravan]]. Trading is a good way to acquire resources that aren't readily available in the local area. It also allows for more freedom in selecting starting gear and skills at [[embark]], since neglected items can be obtained through trade later.

'''Trader''' is the term used at your [[trade depot]] to refer to your fortress representative when dealing with merchants in a visiting caravan ({{key|r}} - "''Trader requested at Depot"''). As a [[profession]], the term applies to visiting merchants and dwarves whose highest [[skill]] is [[Appraiser]].

== Trade depot ==
{{Main|Trade depot}}
Building a [[trade depot]] is a prerequisite for trade with caravans that arrive at your fortress. While it may be convenient to build a depot outside at first, it is usually a good idea to move it inside, or secure it with [[wall]]s, [[bridge]]s and other fortifications, to protect incoming caravans and your goods from [[steals drink|thirsty animals]], [[thief|thieves]] and [[goblin]]s.

Everything that is on your map belongs to you, except:
* the items that are on merchants' animals and wagons
* the items that are in the trade depot (they belong to the caravan until they are moved out of it)
* items worn by non-fortress units (initially forbidden, but can be claimed via unforbidding and dumping them)

==Trading flowchart ==
{{:Trading/Flowchart}}

{{Clear}}

== Trading ==
[[File:Trading with the Elves.PNG|thumb|Trading screen]]

Before you can begin trading, you need to designate what goods to trade and have the fortress's representative trader at the [[trade depot]]. Select the trade depot with {{K|q}} and then {{k|r}}equest the trader. Be sure that {{k|b}} reads "Only broker may trade" if you want your [[broker]] to represent your fortress. If it reads "Anyone can trade", a random, probably unskilled dwarf will volunteer to conduct the trade. Pressing {{k|b}} will toggle this setting. Then select the trade depot again and press {{k|g}} for Move Goods, you will be presented with a list of all items in your fortress that belong to you. Mark the goods you want to sell --insert clever advice--, and your dwarves will begin moving them to the depot.

Once the trade goods are moved to the depot and your trader has arrived, select the depot again with {{k|q}} and enter the {{k|t}}rade menu. In the trade menu select the items to offer from the right and the desired items from the left. All caravans have a weight limit which cannot be exceeded, and the allowed additional weight is displayed in the lower right corner. If your broker (specifically, not necessarily your trader) has at least Novice or better [[Appraisal]] skill, the value of all items will be displayed. Once the proposal is ready, press {{K|t}} to propose the trade, but merchants will not agree unless they make adequate profit. Be sure to use '''trade''', not '''offer''' {{K|o}}, as this will make a gift of the selected items. The amount of acceptable profit is determined by the trader's [[Broker skills|skills]] and the merchant's mood, described below. Merchants may attempt to propose counteroffers if they do not accept the proposal, which can then be accepted, rejected, or further amended by the trader.

With more experienced traders and pleased merchants, even marginally profitable trades can be successful, and counterproposals can be rejected safely, offering the same trade again. Note however that a low profit margin for the traders may not be desirable - it has been suggested that both export and profit numbers influence the size of next year's caravan and, in the case of the dwarven caravan, immigration numbers.{{Verify}}

Note: Goods brought by caravans rarely have base quality higher than superior, and decorations on a good rarely exceed superior as well.

Note if you give or trade away an artifact, you will receive a special screen:
[[File:Treasure_Gift.PNG|750px]]
[[File:Treasure_Trade.PNG|750px]]

=== Items cue colors ===
{| class="wikitable"
! {{DFtext|Brown|6:0}}
| Items have been created (or modified) by your fortress. They can be traded away or offered as a gift.
|-
! {{DFtext|Gray|7:0}}
| Items were created by another source. They can be traded, but if one of these items has been selected, the entire selection cannot be offered as a gift.
|-
! {{DFtext|Purple|5:0}}
| Items are under a no-export mandate. If they are traded away it will result in disciplinary action (see [[justice]]) against the dwarf that brought the item to the depot.
|-
! {{DFtext|Green|2:0}}
| Items have just been gifted to the caravan and they will not trade it back.
|-
! {{DFtext|Red|4:0}}
| Items have been seized from another caravan and cannot be traded as is; you will need to decorate them or turn them into other items for them to become "valid" trading items.
|}

Note that containers (barrels, bins, etc.) will be displayed according to the origin of the ''container'', not the contents. So a foreign barrel holding locally-produced beer will display as foreign (white). Once you {{k|v}}iew the container, the locally-made contents are displayed as local (brown).

=== Seizing items ===

Pressing {{K|s}} from the trade menu will seize the selected items of the merchant's. If you seize goods from a caravan, the merchant will respond "Take what you want. I can't stop you." and then leave immediately without the seized goods. Items cannot be seized from the dwarven caravan, and other races will not buy goods stolen from one of their caravans (then marked in red) unless they are tricked into asking for them via counteroffer, or the items are "laundered" by decoration or used to create other goods. Seizing goods will hurt diplomatic relations, but is not grounds for an automatic [[siege]].

Pressing the seize button while no goods are selected will result in the merchant interpreting your seizure as a joke. This apparently does nothing to benefit or hinder your trading.

As a side note, if you deconstruct your trade depot with a caravan in it, all the caravan's items will drop to the ground, to be readily hauled away by your dwarves. This does not mark the items as stolen, and the caravan will leave. However, ''next'' year's caravan is partly based on the profits from the previous year - so if you are relying on that race's caravans for needed items, you're hurting yourself in the long run.

Trying to interrogate a merchant can also cause a wagon to fall apart.

Another way to steal without marking as stolen is to forbid the trade depot just before they leave, causing them to leave their goods at the depot.

If you're using the search plugin for [[Utility:DFHack|DFHack]] (e.g. from the [[Utility:Lazy Newb Pack|Lazy Newb Pack]]), be warned that {{K|s}} means "seize" and '''NOT''' "search", and there is '''no warning''' for it. Use {{K|q}} to search the merchant's goods and {{K|w}} to search yours.

Note that the civilization attached to a particular caravan will keep track of the value of items the caravan was carrying when they set out to trade, and they will compare this value with the value of items they return home with. Regardless of what method you use to confiscate items from a caravan, even if you came to possess the goods through no fault of your own (an [[ambush]] killed the traders and guards, for example) the parent civilization may decide that you stole from them and send a [[siege]] instead of a caravan the following year. It is prudent to take measures to protect caravans visiting your lands!

===Offering items===

{{key|o}} You can also give away items, as gifts to the leaders of the [[civilization]] you are trading with. This presumably helps relations between yourself and the other faction, though there is not yet a clear correlation between the value of the offerings and the improvement to relations. The exact effects of offerings on trading are unknown but it is believed due to the offerings' net trade value being counted towards the merchants' profit, possibly with a modifier (possibly a multiplier of more than 1 as a bonus or less than 1 to compensate for the improved relations){{Verify}}, which in turn increases the quantity and variety of trade goods brought by next year's caravan. Also the [[Monarch]] requires offerings to be made before their arrival. You cannot offer items that were not made at your fortress; the merchants do not want your spare [[Goblinite]] clothes.

The value of an offering for the purpose of becoming the capital is adjusted by your current export agreement.

Unless you are looking for [[fun]], under no conditions should you offer or trade items which are wooden or used wood in their creation (clear glass, for example) to [[elves]], as this will insult the traders, and may cause them to leave or even damage relations enough to provoke a war between you and the elven civilization you traded with. They will accept their own "grown wood" items in trade without insult, however.

== Miscellaneous trading advice ==
* Thieves and thieving critters tend to follow caravans. Expect assaults and intruders.
* Create your trading depot inside your fort, preferably in the beginning. Place a 3-tile wide path (which must be free of obstructions such as stairways, traps, minecart tracks and boulders) to the entrance of the fort and position war-trained animals along it (chains do not block wagons); this will help to protect the traders and keep the depot close to your supplies.
* Avoid having multiple wagon paths to your depot. Caravan [[wagon]]s cannot move through each other, and if two wagons happen to meet at a fork they may become gridlocked against each other, resulting in the destruction of wagons and loss of trade opportunities.
* All caravans will bring extra food (meat and edible plants), wooden logs, and cloth/leather (for making clothes) if the supplies of your fortress are low enough, independent of whether or not you requested them. This does not apply in the case that the weight limit is exceeded by (other) items you requested. The supply situation, as observed by traders, is based solely on the number of unforbidden items in your fortress, stockpiled or not; thus, it is possible to trick caravans into thinking your supplies are low by [[forbid]]ding all of your relevant stocks immediately prior to their arrival.
**In order to '''avoid''' this behavior, you should make sure that, for each dwarf in your fortress, you have the following ''unforbidden'' items:
*** 5 pieces of food - meat, fish, plants, or "other" in your [[Status]] screen (even though "other" includes inedible items)
*** 1 wood log
*** 5 pieces of cloth, pieces of leather, or complete sets of [[wear|pristine]] clothing (shirt+pants+shoe)
* Define your trade depot as a burrow. When traders arrive, you can add your broker or another dwarf, perhaps one you want to train in trading, to the burrow. They will head to the depot immediately, and stay there until you remove them from the burrow.
* Each trade you make (regardless of value) will increase your trader's skills by 50, distributed among Comedian, Judge of Intent, Negotiator, and Persuader. Each skill seems to gain around 5-15 experience points, but the sum will always be 50. The skill gain occurs as soon as the "t" button is pressed - if the offer is rejected, the dwarf will still gain 50 points. If the same offer is subsequently accepted, no additional skill will be gained.
* Selecting "only broker may trade" ensures that you will start negotiations with a decently-skilled trader, but also requires a significant wait while your broker makes his way to the depot. Selecting "anyone can trade" will result in a poorly-trained trader arriving immediately. Once your fortress is producing enough goods to buy out the caravan, waiting for your broker is unnecessary; allowing your commoners to trade spreads out the trading skill gains and eliminates the micromanagement of trying to get your broker to the depot in a timely manner.
* If your trade depot has no values for the worth of items, then ensuring that a dwarf with the Appraiser skill is assigned as the trader will cause the values to appear.

== Types of Merchant Caravans==
By default, each friendly civilization will send one merchant [[caravan]] per year, linked to one season, which is spring for elves, summer for humans, and autumn for dwarves - no race trades in winter by default. Merchants from different races has different trading preferences.

If your fortress was founded in spring, it is highly unlikely that you will receive an elven caravan that spring, and it is uncommon for a human caravan your first summer, so probably your first and only caravan your first year will be the dwarven one. Caravans will only show up if that race considers the fortress site accessible (as denoted on the embark screen) and "worth the effort" (as determined by the [[Entity_token#PROGRESS_TRIGGER_POPULATION|[PROGRESS_TRIGGER_*]]] tokens in the entity definition), with the exception of dwarves, who always arrive unless they are [[extinct]].

=== Dwarven ===
: ''"Greetings from the mountainhome. Your efforts are legend there. Let us trade!"''
:: (Or, if your fort ''is'' the [[Fortress|mountainhome]]...)
: ''"Greetings from the outer lands. Your efforts are legend there. Let us trade!"''

Typically, the first caravan you receive is the [[Dwarves|dwarven]] one from your home civilization, giving you at least 22 weeks to prepare (assuming you started mid-spring, the default). This does require that you are on the same continent as they are, and you are not isolated by mountains or bodies of water.

The dwarven caravan:
* arrives in [[Calendar|autumn]].
* carries metal bars, [[leather]], weapons and armor, food and booze, and more. Dwarves alone may bring [[steel]] and steel goods.
:* If the trading civilization does not have access to [[iron]], they can still bring steel (and steel goods) and [[pig iron]] bars, but will not bring iron products.
* usually carries a selection of books that your civilization has access to. This can include books written in previous forts of yours within the same civilization.
* is heavily guarded.

The dwarven caravan from your home civilization:
* sends a liaison who will speak with the [[Expedition leader]], [[Mayor]], [[Baron]], [[Count]], or [[Duke]] to negotiate an import-export agreement (unless the [[Monarch]] is present).
* influences the number of immigrants received (if the caravan leaves intact).
* will not cause sieges when repeatedly destroyed or lost.
* is the only caravan to arrive during a fortress' first year.
* always arrives, regardless of embark location, unless the dwarven civilization is [[extinct]].
* cannot have its goods seized from the trade menu.
* may not arrive if your civilization lacks any notable figures.
* cannot be offered goods if the monarch is present.

=== Elven ===
[[Image:Evil_elves.png|thumb|400px|A typical elven caravan.]]
:''"Greetings. We are enchanted by your more ethical works. We've come to trade."''

Assuming you do have friendly contact with [[elf|elves]], their first caravan will arrive sometime in spring, giving you about a full year before they arrive.

The elven caravan:
* arrives in the [[Calendar|spring]].
* does not use [[wagon]]s, only [[Creature#Domestic animals|pack animals]]
* carries [[cloth]], [[rope]]s, various above-ground seeds, [[plant]]s and their byproducts, [[log]]s, [[wood]]en goods & [[weapon]]s, clothing and [[armor]], and may carry tame exotic [[creature]]s.
* is unguarded.
* does not accept some items in trade: Elven merchants do not like to be offered any "tree" byproducts, including wood and charcoal products, unless they are "grown", which only elves can produce (see list below).

Because they do not utilize wagons, elven caravans have a much smaller weight limit than dwarven and human ones, making trading heavy items like furniture problematic. Because of this and that they tend to offer only items made of (living) wood*, the total value of what they offer tends to be considerably less than other caravans, meaning your fortress doesn't have to bring nearly as much to trade to get everything that it might find useful.

: (* Wooden items offered by the elves have been "grown" as that item, so, somehow, that makes it acceptable to them. See next section.)

"No wagons" also means that the entire caravan will use the most direct 1-tile-wide path to your Trade Depot, which could be a good or bad thing, depending on that path and your plans for this caravan.

==== Unacceptable items ====
Elves view living trees as [[Elf#Ethics|sacred]] - or some crap like that. Offering or attempting to trade items that required the killing of a tree will greatly offend the merchant, causing their mood to drop rapidly. They will refuse to trade any more that season and leave immediately. Additionally, you will be called "uncouth", "crude", and "barbaric" for not understanding their customs.

: ''"Once a beautiful tree, and now? It is a rude bauble, fit only for your kind."''

Unacceptable items (as offered by dwarves) include:
:* [[Wood]]en items (including all subterranean mushrooms/fungus/etc. such as [[tower-cap]]s)
:* Items derived from wood - [[ash]] and [[charcoal]], as well as [[lye]], [[potash]], and [[pearlash]]
:* Items made from clear and crystal [[glass]] (due to the [[pearlash]] used); basic green glass is perfectly acceptable
:* Items «[[decoration|decorated]]» with any of the above materials
:* [[Obsidian]] shortswords (since they have wooden handles)
:* Any of the above, regardless of who made them (i.e. from earlier trades, or captured gear from fallen enemies)
:* Tallow [[Soap]] (made with [[lye]]), but not Plant Soap{{bug|8571}}

However, [[stone]] and [[metal]] items, even when [[charcoal]] is used in production, are acceptable (since the elves are unfamiliar with metalworking, and do not know that charcoal is used to make metal items). Items made from [[silk]] are acceptable, as are all non-wooden plant-derived products such as [[cloth]] and [[thread]]. Items made of bone (totems too), horn, shell or leather are acceptable, so are meat and fish. You can also transport your goods to the [[trade depot]] in a wooden [[bin]], as long as you do not try to sell the bin. Living animals are acceptable, as long as the [[cage]] or [[trap]] is not made of [[wood]].

Be especially careful with reselling decorated items from other caravans, as non-wood/glass items may have decorations of wood or clear/crystal glass. Note that "grown" wooden items from elven caravans ''can'' be resold to them, as the elves know that they were made in an elf-kosher way.

=== Human ===
:''"Greetings. The craftsdwarfship of the dwarves is unparalleled. Let's make a deal!"''

Assuming you do have friendly contact with [[human]]s, their first caravan will arrive sometime in summer, giving you well over a full year before they arrive.

The human caravan:
* arrives in [[Calendar|summer]].
:* Usually your first caravan opportunity
* carries metal bars, sand, [[leather]], cloth, wood, food and booze, books, ropes, waterskins, quivers, backpacks, metal weapons and clothing and armor, cages and a few domestic animals.
* carries only large-sized clothing and armor, which is unusable by dwarves.
* is moderately guarded.

=== Goblins and Kobolds ===
{{mod}}
{{main|modding#trade}}

A [[goblin]] caravan will only arrive if you mod the game, primarily because their entity lacks the [[entity token]]s needed to make use of pack animals and wagons. That, and that the token {{token|BABYSNATCHER|e}} makes them hostile to all non-goblin civilizations. The same caveats apply to [[kobold]]s (whose {{token|UTTERANCES|c}} and {{token|ITEM_THIEF|e}} tags, similarly, make them hostile to every civilization).

The goblin caravan:
*will arrive every season, four times per year
*is unguarded
*brings mostly food and cloth
*does not send a liaison or a guild representative
*does not make import/export agreements

== Merchant mood ==
{{Verify|Are we sure that this section is correct?}}
If your trader has Novice or better [[Judge of intent]] skill, there will be a line added below the merchant's dialogue describing the caravan's attitude. Their attitude rises with successful trades (especially if they get lots of profit) and falls when you propose deals they don't like. You can never make a deal that's at a loss for the merchant, even if they are at the highest possible mood.

* {{DFtext|(trader) seems ecstatic with the trading.|2:1}}
* {{DFtext|(trader) seems very happy about the trading.|3:1}}
* {{DFtext|(trader) seems pleased with the trading.|1:1}}
* {{DFtext|(trader) seems willing to trade.|7:1}}
* {{DFtext|(trader) seems to be rapidly losing patience.|6:1}}
* {{DFtext|(trader) is not going to take much more of this.|4:1}}
* {{DFtext|(trader) is unwilling to trade.|5:1}}

The happier you make a merchant, the less profit margin they will demand in a trade. Dwarven merchants start off wanting about 100% profit, maybe a little more. If you repeatedly offer less than what they expect, that will "lower" their mood. If, on the other hand, you meet or exceed their expectation, that will, over several trades, improve their mood. If merchants reach the lowest level, no further trade will be possible, and they will immediately pack up and leave your depot. Since annoyed merchants are more likely to reject deals, you should be generous in initial negotiations. Skilled negotiators seem less likely to offend merchants with unsuccessful deals.

An easy way to capitalize on this mood system is to perform several partial trades. First trade for a few items, offering goods twice the value of the items you ask for (e.g. offer 2000☼ for 1000☼ of his stuff). This will likely make the merchant ecstatic about trading with you. Perform the next trades more aggressively, working them down to about a 30% profit. With the merchant in such a good mood, they are more likely to counteroffer than reject a trade outright. If you don't like the counter-offer, try to split the difference, or just back out of the trade and start again.

== Trade Agreements and Liaisons ==
[[Outpost liaison]]s (from your own civilization) and foreign Merchant Nobles (if added with the [[Position token#TRADE|TRADE responsibility]]) will arrive with the caravan to speak to your [[noble]] dwarves (and they ''will'' speak to those dwarves, even if they have to wait at their bedside in the hospital for months after the caravan has left), appearing on the map edge at the same time as the caravan (though in a different location). Meeting with them allows you to request specific items for the next caravan to bring (at a premium price) or take requests for production for the next caravan (for which the merchants will pay a premium).

Current [[Trade agreement|trade agreements]] can be viewed through the Civilization menu ({{k|c}}). These trade agreements are cleared when a liaison of the corresponding civilization enters the screen, so they are generally not accessible after the caravan has arrived.

In the event that your leader is replaced, killed, or taken by a [[strange mood]], the liaison may decide to leave your fortress [[stymied|"unhappy"]].{{bug|576}} Curiously, this will '''not''' occur if your leader is otherwise unable to perform the "conduct meeting" task. You can currently lock a liaison in a room and they will wait years to attend the meeting your noble is constantly conducting (and all subsequent diplomats appear to wait in line for the first to finish); this behavior is presumably a bug.{{bug|8947}}

Whether having successfully met with your leader or given up, a liaison who has decided to leave but is prevented from reaching the map edge will eventually go [[insane]].

== Bugs ==

*Aggressive, untrainable creatures (captured goblins, for example) cannot be traded; when a dwarf attempts to move the caged animal to the Depot, the creature is set free.
*When merchants leave with an animal, the merchants seem to be dragging their beast of burden instead of leading it. If the animal is incapacitated but not dead, the merchant will continue to walk at the same speed, dragging the unconscious beast.
*If a merchant's chosen map edge exit is guarded by a hostile creature (including those on a [[restraint]]), the merchant will wander back and forth repeatedly and eventually go insane rather than path to an alternate exit.
* Animals bought from merchants don't always become available for use.{{bug|10162}}

== Loyalty cascade ==
{{main|Faction#Loyalty cascade|l1=Faction}}
If you order your military to kill merchants from your own civilization, a bizarre result of the way loyalty is handled makes the members of your military who attacked the traders become enemies of your civilization, but remain members of your fort's government (dwarves of this [[faction]] are referred to as ''separatists''). As enemies, they attack your other dwarves (''citizens''), but as members of the fort, they still follow orders. Allowing citizen militia dwarves to attack the separatists will give them opposite loyalties of the separatists, (i.e. loyal to civ, not to fort), or ''loyalists'', who do '''not''' follow orders. And then, if a separatist or loyalist kill a citizen, they become enemies of the civ '''and''' fort, making them ''Renegades'', who are essentially complete enemies of the citizens.

To prevent the cascade from spreading, order the original separatists away from the fortress and let them fight amongst themselves. If the results are renegades, it is okay to allow other dwarves to kill them (by stationing them nearby). If the results are separatists/loyalists, then you will need to separate them, somehow.

== Exploits ==
*Deconstructing the Depot will cause merchants to leave your fortress and abandon any goods in the Depot because items are not available until the building is fully deconstructed. However any animals they had caged will still belong to the merchants and only become friendly, you won't actually own them. According to Toady One, this is actually working as intended, and is not really an exploit or bug: "...the reckoning comes when they return with lesser value, and it has the same negative effect (it'll be listed as a disaster rather than an intentional seizing -- the depot could be destroyed, for instance -- but it counts for the same value if I remember). The overall wording could be changed and the interaction could be deepened to recognize this or that, but it's working as intended."[http://www.bay12games.com/dwarves/mantisbt/view.php?id=293#c8393]
*If you wait until the merchants leave the map, you can "claim" caged animals by linking a lever to the cage and opening it, the animals will be released in a tamed state. Check the {{k|u}}nit screen before releasing them; if the creatures still show as Merchant creatures, they will wander off the map when released; if they show as Tame creatures, they will stay once released.
*If you lock them in your fortress for a minute or two (real time), the merchants '''may''' drop items and leave behind pack animals (both of which are yours for the taking!) Note: Results are not consistent.
* If [[Caravan#Destruction|spooked or attacked]] the merchants' caravan could leave their stuff behind as they attempt to flee the map, leaving the items free for the taking.

[[File:Bullock_Team_Wool_Wagon.jpg|thumb|400px|center|An old trading wagon from the 1880's.]]

== World level Trade ==
During world generation, trade is established between sites. This probably determines growth.

{{Translation| dwarven = nish | elvish = lathì | goblin = otsmor | human = batow}}

{{Category|Trade| }}
[[ru:Trading]][[zh:Trading]]

Cavern

2022-12-08T02:07:28Z

Xjtu-blacksmith: rm extra space

{{av}}
{{Quality|Exceptional}}
{{minorspoiler}}
[[File:Cavern 2014.png|thumb|351px|A cavern found underground.]]
[[File:cavern2.jpg|thumb|351px|Art of an actual cavern.]]
''Not to be confused with [[Cave]].''

'''Caverns''' are ''huge'' natural underground tunnel systems, inhabited by strange and dangerous creatures. They go up, down, left, right, and just about anywhere else. Vanilla worlds provide three cavern layers. Number, size and z-position can be altered in the [[world generation]] parameters.

The caverns will usually have open map edges, allowing all sorts of [[creatures]] to migrate into and from them. By exploring the caverns in adventure mode it is possible to travel large distances below the surface - the caverns effectively connect all sites that access them.

Upon reclaiming a fort, all mud in the caverns is removed.

''In subterranean biomes, Chasm, water, and lava mean land, water (pool), and magma (pipes) respectively.''

==Geography==
The top of the first cavern usually resides about 10-11 z-levels below the surface.
Each cavern layer spans multiple z-levels, and is filled with [[water]] to a certain degree. This can range from a few pools at the bottom level to the whole layer being submerged, forming a gigantic underground sea, including [[fish]] and possibly camps of [[olm man|olm men]] and other [[fun]] aquatic creatures.

The average amount of water cavern layers feature depends on your world generation settings, specifically

[CAVERN_LAYER_WATER_MIN:0]

[CAVERN_LAYER_WATER_MAX:100]

Beneath the third layer lies the [[magma sea]].

If you hit caverns too often then you can create a custom world with a higher number for 'Z Levels Above Layer 1' - Levels of stone above the first cavern layer. Making this higher will guarantee at least this many levels to build your fortress, but will have no impact on how many z-levels thick the surface layer is. Also, the top of a cavern may be higher than the rest of a cavern, so in practice there will be more levels than this.

Generating worlds using the ISLAND template tend to produce much deeper caverns (hundreds of z-levels down) than those with the REGION template, where only 50-60 z levels will separate the surface from the Underworld.

===Features===
Exploring the underground world, you may find a variety of special geographical features. When your dwarves discover a feature, an announcement window will let you know of it.

'''[[Deep pit]]s:''' Deep pits are... deep pits that connect one cavern level to the next. They have a fixed shape. The top z-level, where the pit meets the next cavern level, is un-muddied rough rock floor where the normal space of the deep pit and the random rock spires of the cavern collide.

If your map has an unseen [[cave-in]] at the beginning of embark, the caverns may have a deep pit somewhere. This occurs because some stone in the cavern above the deep pit is unsupported and falls down. This may be a bug.

'''[[Magma pool]]s:''' Despite the name, magma pools are not actual pools, but tubes extending up from the [[magma sea]]. Their shape is fixed and their presence random. A magma tube might extend all the way to the top cavern, or merely a few z-levels. Magma pools can be distinguished from the magma sea even if they are only a single Z-level high due to two important features: they will always be walled by obsidian as opposed to the standard stone of the layer and, more importantly, will (very slowly) refill to their top if any magma is drained.

'''[[Passage]]s:'''
Passages are natural tunnels connecting two layers by ramps and short, twisted tunnel sections. The announcement window will let you know you've found a downward passage even if you happen to discover it from the bottom.

==Wildlife==
A number of [[vermin]] and [[creature]]s can only be found in subterranean biomes, at certain cavern levels. Cavern creatures seem to follow different rules from above-ground creatures - their population numbers are usually far more than their [[Raw file|raws]] imply, and alignment plays no role in whether they can be found in the map or not. Good creatures like the [[gorlak]], evil creatures like the [[troll]] and savage creatures like the [[giant cave spider]] can be found in any cavern, regardless of the actual [[surroundings]].

[[Forgotten beast]]s are a special type of procedurally-generated [[megabeast]] found only in caverns, and may invade your map from any of the three cavern levels.

===Creatures===
{| class="wikitable"
! Name
! Level 1 !! Level 2 !! Level 3 !! Level 4
|-
| {{Tile|M|5:1}} [[Amethyst man]]
| || || {{check}} ||
|-
| {{Tile|a|6:0}} [[Amphibian man]]1
| {{check}} || {{check}} || {{check}} ||
|-
| {{Tile|a|0:1}} [[Antman]]1
| {{check}} || {{check}} || {{check}} ||
|-
| {{Tile|b|0:1}} [[Bat man]]1
| {{check}} || {{check}} || ||
|-
| {{Tile|B|7:1}} [[Blind cave bear]]
| {{check}} || {{check}} || ||
|-
| {{Tile|O|7:1}} [[Blind cave ogre]]
| || {{check}} || {{check}} ||
|-
| {{Tile|M|4:0}} [[Blood man]]
| || || {{check}} ||
|-
| {{Tile|b|5:0}} [[Bugbat]]
| || {{check}} || {{check}} ||
|-
| {{Tile|o|6:1}} [[Cave blob]]
| || || {{check}} ||
|-
| {{Tile|C|7:0}} [[Cave crocodile]]
| {{check}} || {{check}} || ||
|-
| {{Tile|D|7:1}} [[Cave dragon]]
| || || {{check}} ||
|-
| {{Tile|f|7:1}} [[Cave fish man]]1
| {{check}} || {{check}} || ||
|-
| {{Tile|f|6:1}} [[Cave floater]]
| || {{check}} || {{check}} ||
|-
| {{Tile|s|0:1}} [[Cave swallow man]]1
| {{check}} || {{check}} || ||
|-
| {{Tile|e|7:1}} [[Creeping eye]]
| || || {{check}} ||
|-
| {{Tile|c|4:0}} [[Crundle]]
| || {{check}} || {{check}} ||
|-
| {{Tile|D|6:1}} [[Draltha]]
| {{check}} || {{check}} || ||
|-
| {{Tile|d|7:0}} [[Drunian]]
| {{check}} || {{check}} || ||
|-
| {{Tile|E|6:0}} [[Elk bird]]
| {{check}} || {{check}} || {{check}} ||
|-
| {{Tile|i|6:1}} [[Fire imp]]
| {{check}} || {{check}} || {{check}} || {{check}}
|-
| {{Tile|M|4:1}} [[Fire man]]
| || || {{check}} || {{check}}
|-
| {{Tile|o|6:0}} [[Flesh ball]]
| || || {{check}} ||
|-
| {{Tile|%|7:0}} [[Floating guts]]
| || {{check}} || {{check}} ||
|-
| {{Tile|M|0:1}} [[Gabbro man]]
| || || {{check}} ||
|-
| {{Tile|B|0:1}} [[Giant bat]]
| {{check}} || {{check}} || ||
|-
| {{Tile|S|7:0}} [[Giant cave spider]]
| {{check}} || {{check}} || ||
|-
| {{Tile|C|0:1}} [[Giant cave swallow]]
| {{check}} || {{check}} || ||
|-
| {{Tile|T|7:0}} [[Giant cave toad]]
| {{check}} || {{check}} || ||
|-
| {{Tile|W|6:0}} [[Giant earthworm]]
| {{check}} || {{check}} || ||
|-
| {{Tile|m|6:0}} [[Giant mole]]
| {{check}} || {{check}} || ||
|-
| {{Tile|O|7:1}} [[Giant olm]]
| {{check}} || {{check}} || ||
|-
| {{Tile|R|6:0}} [[Giant rat]]
| {{check}} || {{check}} || ||
|-
| {{Tile|g|6:1}} [[Gorlak]]
| {{check}} || {{check}} || {{check}} ||
|-
| {{Tile|G|2:1}} [[Green devourer]]
| || {{check}} || {{check}} ||
|-
| {{Tile|g|2:1}} [[Gremlin]]
| {{check}} || {{check}} || {{check}} ||
|-
| {{Tile|s|7:1}} [[Helmet snake]]
| {{check}} || {{check}} || ||
|-
| {{Tile|h|0:1}} [[Hungry head]]
| || || {{check}} ||
|-
| {{Tile|M|0:1}} [[Iron man]]
| || || {{check}} ||
|-
| {{Tile|J|5:1}} [[Jabberer]]
| || {{check}} || {{check}} ||
|-
| {{Tile|r|6:0}} [[Large rat]]
| {{check}} || || ||
|-
| {{Tile|C|0:1}} [[Magma crab]]
| || || {{check}} || {{check}}
|-
| {{Tile|M|4:1}} [[Magma man]]
| || || {{check}} || {{check}}
|-
| {{Tile|m|6:0}} [[Manera]]
| || {{check}} || ||
|-
| {{Tile|M|4:1}} [[Molemarian]]
| || {{check}} || {{check}} ||
|-
| {{Tile|M|6:0}} [[Mud man]]
| || || {{check}} ||
|-
| {{Tile|n|4:1}} [[Naked mole dog]]
| {{check}} || || ||
|-
| {{Tile|o|7:1}} [[Olm man]]1
| {{check}} || {{check}} || ||
|-
| {{Tile|m|5:0}} [[Plump helmet man]]
| || {{check}} || {{check}} ||
|-
| {{Tile|p|1:1}} [[Pond grabber]]
| {{check}} || {{check}} || ||
|-
| {{Tile|R|7:0}} [[Reacher]]
| || {{check}} || {{check}} ||
|-
| {{Tile|r|2:0}} [[Reptile man]]1
| {{check}} || {{check}} || {{check}} ||
|-
| {{Tile|r|0:1}} [[Rodent man]]1
| {{check}} || {{check}} || {{check}} ||
|-
| {{Tile|R|7:0}} [[Rutherer]]
| || {{check}} || {{check}} ||
|-
| {{Tile|s|7:1}} [[Serpent man]]1
| {{check}} || {{check}} || {{check}} ||
|-
| {{Tile|t|6:0}} [[Troglodyte]]
| {{check}} || {{check}} || ||
|-
| {{Tile|T|0:1}} [[Troll]]
| {{check}} || {{check}} || {{check}} ||
|-
| {{Tile|C|1:0}} [[Voracious cave crawler]]
| || {{check}} || {{check}} ||
|}

:1 [[Animal people#Subterranean animal people|Subterranean animal people]] live in pre-existing "camps" and do not move in/out of caverns like other creatures. If they weren't there from the start, they will never be encountered, and if every animal man present is killed, they will ''not'' reappear from the edge of the map.

===Vermin===
{| class="wikitable"
! Name
! Level 1 !! Level 2 !! Level 3 !! Level 4
|-
| {{Tile|∙|0:1}} [[Bat]]
| {{check}} || {{check}} || ||
|-
| {{Tile|∙|2:0}} [[Cap hopper]]
| {{check}} || {{check}} || ||
|-
| {{Tile|α|7:1}} [[Cave fish]]
| {{check}} || {{check}} || ||
|-
| {{Tile|¥|7:1}} [[Cave lobster]]
| {{check}} || {{check}} || ||
|-
| {{Tile|∙|7:0}} [[Cave spider]]
| {{check}} || {{check}} || ||
|-
| {{Tile|∙|0:1}} [[Cave swallow]]
| {{check}} || {{check}} || ||
|-
| {{Tile|*|6:0}} [[Creepy crawler]]
| || || {{check}} ||
|-
| {{Tile|∙|6:1}} [[Fire snake]]
| || {{check}} || {{check}} || {{check}}
|-
| {{Tile|∙|7:1}} [[Olm]]
| {{check}} || {{check}} || ||
|-
| {{Tile|{|7:1}} [[Purring maggot]]
| || {{check}} || {{check}} ||
|}

==Vegetation==
[[File:Cavern krugg.jpg|thumb|Rendering of cavern Vegetation]]

Any cavern layer without a pool of water will have only muddy dense floor fungus, and no plants or trees except [[blood thorn]]s.

Removing a layer will cause the layer above to randomly pick from trees that the now-removed layer could have handled and that the layer above can handle.

===Shrubs===
{| class="wikitable"
! Name
! Level 1 !! Level 2 !! Level 3
|-
| {{Tile|:|7:1}} [[Cave wheat]]
| {{check}} || {{check}} || {{check}}
|-
| {{Tile|:|1:1}} [[Dimple cup]]
| {{check}} || {{check}} || {{check}}
|-
| {{Tile|:|7:0}} [[Pig tail]]
| {{check}} || {{check}} || {{check}}
|-
| {{Tile|:|5:0}} [[Plump helmet]]
| {{check}} || {{check}} || {{check}}
|-
| {{Tile|:|7:0}} [[Quarry bush]]
| {{check}} || {{check}} || {{check}}
|-
| {{Tile|:|4:1}} [[Sweet pod]]
| {{check}} || {{check}} || {{check}}
|}

===Trees===
{| class="wikitable"
! Name
! Level 1 !! Level 2 !! Level 3
|-
| {{Tile|♠|7:1}} [[Tower-cap]]
| {{check}} || {{check}} ||
|-
| {{Tile|♣|6:1}} [[Fungiwood]]
| {{check}} || {{check}} ||
|-
| {{Tile|♠|4:1}} [[Goblin-cap]]
| || {{check}} || {{check}}
|-
| {{Tile|♣|3:0}} [[Spore tree]]
| || {{check}} || {{check}}
|-
| {{Tile|♠|0:1}} [[Black-cap]]
| || {{check}} || {{check}}
|-
| {{Tile|│|5:1}} [[Tunnel tube]]
| || {{check}} || {{check}}
|-
| {{Tile|♠|1:0}} [[Nether-cap]]
| || || {{check}}
|-
| {{Tile|╡|4:0}} [[Blood thorn]]
| || || {{check}}
|}

===Grasses===
{| class="wikitable"
! Name
! Level 1 !! Level 2 !! Level 3
|-
| {{Tile|.|3:1}} [[Cave moss]]
| {{check}} || {{check}} || {{check}}
|-
| {{Tile|.|7:1}} [[Floor fungus]]
| {{check}} || {{check}} || {{check}}
|}

==Dangers==
Though digging down can be tempting, coupled with the fact that caverns can provide some helpful resources, there are many, many <s>dangerous</s> [[fun]] [[animal]]s in a cavern. This includes [[giant cave spider]]s, [[giant olm]]s, [[troll]]s and [[cave crocodile]]s, but even the seemingly [[gremlin|harmless ones]] can provide great [[Stupid_dwarf_trick#Self_Destruct_Lever|fun]].

Cavern level one is as good as things get, and the following levels will [[Cave dragon|only]] [[Voracious cave crawler|be]] [[Magma crab|worse]]. If you can't stand level one, you won't be able to stand level two or three. [[Hungry head|Flying creatures]] can <s>ruin your day</s> [[Fun|provide some fun]] if your main stairwell leads directly into the cavern (the bottom of up-down/down stairs can be passed by flying creatures). Also, any cavern of sufficient size will be inhabited by [[giant cave spider]]s, which can be both a [[Silk|benefit]] and a hazard.

Opening the caverns will make it possible for your fortress to be attacked by [[forgotten beast]]s, which range in lethality from "not much" to "nigh unkillable". One thing you really have to watch out for is having your main stairwell lead into a cavern. It doesn't have to be so walking creatures can get in, but just so there's an open hole. Any hostile creature sitting under your open stairway will spook any dwarves trying to use it, causing a flood of job cancellation messages as they keep trying to reach their destination. When this happens, it can lead to all your dwarves starving themselves to death. Only build stairs on the side, preferably with a hatch.

And of course, digging too deep will lead the player to encounter certain [[Demon|overwhelmingly fun things]].

==Benefits==
Caverns provide ever-regenerating resources in the form of underground [[wood|forests]], animals to hunt, and fish. On breaching a cavern layer, a variety of [[ore]]s and [[gem]]s lining its walls will be revealed. The cavern floors are always [[Farming#Underground Farming|muddied]], providing soil to a variety of underground [[plant]]s. Also, underground caverns and the [[water]] they provide can be used in constructions and traps. In places like [[glacier]]s, caverns will provide the only source of [[water]] and [[farming|farmable]] land. Throwing your prisoners into a damp hellhole filled with ravaging beasts is a nice addition, too. Additionally, creating a world without caverns will result in no subterranean plants, plant products (plump helmets/spawn/wine etc.) or fish available on embark. However this is a moot point, as without mods, dwarven civilizations only use indoor farming, and so will never form. Worldgen will stall without a usable dwarven civilization.

Once an underground cavern has been discovered, shrubs and trees will spontaneously grow on any subterranean [[soil]] or [[mud]]died [[rock]] on every embark site that accesses the cavern. This means that if you find a cavern in one embark site and embark in another site accessing the same cavern, plants will start growing there even before you discover the branch of the cavern that lies under the site. This allows you to construct underground tree farms and avoid sending dwarves to the surface to harvest wood, or just to get wood in environments without above-ground forests.

As walls can be built right up to the map edge below ground, it is possible to prevent land creatures from spawning by turning all the spawn points into walls. A single level of wall is sufficient to halt most non-fliers, who will appear on the wall and be unable to get down into the cavern itself. Creatures with the ability to climb or jump, however, tend to eventually figure out a way down, so prepare for these accordingly. Fliers can be stopped only by building walls up to the ceiling, and swimmers can't be prevented from spawning without obsidianising the water tiles on the map edge. The next best thing is to block off access, which can be achieved by dropping a layer of natural stone wall into the water.

NOTE: walls come with floors above them, which means that creatures may still spawn on top of the wall and interrupt jobs, or not spawn where you want them to (if you are trying to wall off most entrances and leave a few designated entrances with cage traps). So fortifications without floors on top of them should be built instead to seal an entrance from ground creatures. Also avoid completely walling off all ground creatures with only 1 floor of walls; the game will spawn flying creatures if ground creatures cannot be spawned.

===Creatures===
[[Cage trap]]s placed in the caverns can capture wild animals to potentially [[animal trainer|tame]]. As with above-ground creatures, subterranean groups of creatures are limited to one group at a time. Many of the more interesting creatures appear in groups of one and have small populations, so you'll have to clear out a lot of bugbats and crundles before being able to grab every giant cave spider or jabberer your site can produce.

These small populations may result in all spawned individuals being of the same sex, making breeding programs impossible even for creatures that have the necessary tags. Adding the [CHILD:1] to a creature is a relatively easy mod, but sex changes require the application of a transformational syndrome, and possibly changing the creature from an egg-layer to a live-birther.

==When should I start exploring?==
One standard approach is to wait until you have a working military. The first cavern usually has few hazardous monsters, apart from the occasional [[giant olm]] or [[giant toad|toad]] and [[giant cave spider]]s, but just one giant bat can destroy an early fort, and [[Forgotten beast|uninvited guests]] will wander in sooner or later. The subsequent caverns will become increasingly [[fun]], so don't dig too deep without making adequate preparation. A decent military should be able to handle the cavern fauna, assuming they're not busy dealing with surface [[invader]]s.

Alternatively, you might want to breach the caverns as early as possible, then wall off the entrance. Doing so has several benefits: it will allow you to plan your fortress layout around the underground features, release the spores necessary for an underground [[tree farm]], prevent a calamitous discovery later when [[forgotten beast|powerful enemies]] lie in wait, and minimize the amount of time invested if the caverns prove unsuitable. You can of course continue to explore a cavern without a military, but you will likely get a bunch of dwarves killed.

Another alternative approach is to breach the caverns on a separate tunnel from your main fortress, so that beasts found inside have to path through the surface to reach your citizens, much in the way regular wild animals and invaders have to. Watch out for automatically created 'collect silk' jobs though, since dwarves assigned to them will be all the more in danger.

Not all parts of a cavern are immediately visible; a good portion of a cavern is revealed once you breach it, but other parts remain hidden until your dwarves explore them. Since you often don't know what you'll find in a cavern, they can be exciting places, but also
very <s>dangerous</s> fun.

==Methods of exploration==
:''This section covers methods to explore already-discovered caverns; if you're having trouble finding the caverns, check [[Exploratory mining]] for tips.''

There are many different methods of exploring, some less [[fun]] than others.

'''Military squads''': You can order your [[squads]] into the cavern with move orders. This way you can have dwarves manually explore the cavern by foot. The caverns are dangerous and unpredictable; well equipped dwarves will live longer. The {{k|s}}quad:{{k|a}}ttack:{{k|l}}ist command will help you find and kill enemy creatures which may be located on many different z-levels inside the cavern.

Note that creatures may wander into the cavern from the edges, so, if you want to start collecting silk, gems, ore and the other valuable loot in a cavern, and you want to do so safely, you should first kill or capture the creatures in the cavern, then wall off the edges to keep new creatures from wandering in. Note that, if you want to keep flying creatures out, your walls will need to cover the edge of the cavern from the floor to the ceiling. If you'd still like to fight or capture wandering creatures, but don't want them killing your workers, you can leave some room for creatures to get in, and build doors or cages as necessary.

'''Monster slayers''': Once you've discovered a cavern, a steady stream of wandering [[monster slayer]]s will come to your fort, [[petition]]ing you for the right to live there and kill the awful horrors that live beneath your feet. While it's best not to rely on them to actually keep your fort safe from deep trouble, they actually do a pretty solid job of mapping out your caverns for you. Just be sure to keep [[cage trap]]s and sane armed guards at whatever access route you choose to leave open so your slayers can reach their tasty slayables.

'''Lone woodcutter''': Most cavern creatures are not faster than a normal dwarf, so it may be safer to send out a civilian woodcutter to cut 1 tree at where you want to explore. Unlike exploring with an early unarmed military team that will suicide against [[jabberer]]s, a woodcutter will actually run away when confronted by hostile creatures. Cavern creatures also tend to give up the chase after a while, provided you can dodge the few hits they rarely get in if they catch up (not a problem if your explorer has moderate dodging skill).

'''Fortifications''': as dwarves can see through [[fortification]]s, you can carve out a fortification near the edge of the explored area to safely discover more of the cavern. This prevents wildlife and [[megabeast]]s from entering your fort, as an added benefit. This method does not work for exploring the magma layers - or rather, it ''does'' work, but for a very, very brief time during which there is much [[fun]].

'''Digging and walling''': Instead of [[smoothing]] a wall and then carving a fortification, it can be quicker to just dig out the wall and then blocking off the opening with a [[construction|constructed]] wall. The disadvantage over the fortification method is that if any dangerous creatures are lurking unseen near edge of the explored area they might get to your dwarf before the wall can be put up.

'''Digging from above''': The only method that works in the magma layers, this method requires you to dig a hole from above the caverns into the cavern. It is advisable to seal the hole afterwards if you wish to prevent flying or magma creatures from entering your fort.

'''Autonomous Dwarven Cavern Rover''': [[Activity_zone#Pit.2FPond|Pit]] an animal into the cavern through an access tunnel above the cavern floor, walling it up afterward if you wish. The animal will wander the cavern, revealing more of it, and possibly stumble across things you would prefer your dwarves not encounter unaware. If the animal is tame, its movement can be somewhat controlled by creating a [[Activity zone#Meeting Area|meeting zone]] in the place you would like it to move to.

'''Suicide mission''': Ideal for exploring the bottom of a deep pit or magma pool. Knock a dwarf or animal into the pit, and they will rapidly plummet. Despite being unconscious, they will report everything they see for as long as they are alive. [[Noble]]s, [[cat]]s and [[vampire]]s make excellent geonauts.

'''Separate tunnels''': Digging exploration tunnels from within your fortress will result in a direct path from the caverns to your fortress- this can result in enormous volumes of fun. Players seeking to avoid fun may instead choose to start their exploration tunnels from elsewhere on the surface, outside the fortress. This guarantees that any threats released through exploration must pass through the same entrance utilized by surface threats, such as goblins or elephants, before they can access the fortress.

This method works in conjunction with the "Digging from above" method. Placing the tunnels as close as possible to the edges of the map will reduce obstruction to the fortress. The Dwarf Fortress Wiki assumes no liability for any potential damage to lesser surface races resulting from the release of subterranean monsters directly into the surface world.

==Adventure mode==
You can enter a cavern with an [[Adventurer_mode|adventurer]] and explore it. Ways to enter them include [[cave]]s, dwarven [[fortress]]es that connect to [[tunnel]]s, starting in [[Mountain halls]], and goblin [[dark pits]] that have pits that can be [[climb]]ed down. You can also encounter downward [[passage]]s or [[Cavern#Features|deep pits]] that connect the different cavern levels.

The dangers are obvious; Nasty creatures, pitfalls, etc. You also have to watch out because you can't fast-travel underground, unless you are in a generated [[tunnel]], and you can only start fast travel on those if you are not in a mountain tile or hostile site. That means no easy healing, so you have to be very careful. Make sure you stock up on food, water and (if you use it) ammunition before you head in, though, as caverns are quite massive and it can be difficult to find your way back. Worse, there are tribes of animal men underground, and unlike in the good old days they'll attack on sight. If you're lucky, you'll find a [[gremlin]] or other non-hostile intelligent wildlife, and those can potentially be recruited. Since you can't fast-travel, you have to rely on sleeping to heal, which can be dangerous due to the [[Giant cave spider|nature]] of caverns. You're on your own against [[Forgotten beast|whatever]] [[Troll|shows]] [[Blind cave ogre|up]], unless you brought or find allies. Escaping from the caverns by the same route used as an entrance can be very difficult, though if you manage to reach a cavern area immediately underneath a town you will be able to fast-travel to the surface.

If you discover the underground caves in Adventure mode, then retire and start a fortress, the fortress will grow subterranean plants as if a passage to the underground had already been opened on that map.

==Caravan and embark item availability==
[[Embark]]ation and dwarven [[caravan]]s will only provide resources available in the first cavern level. Since [[purring maggot]]s don't appear in the first cavern level, unlike in 40d, you can't buy dwarven [[cheese]] or dwarven [[milk]] {{Bug|1449}}. A workaround is to edit the global [[raw file]]s to make purring maggots appear on level one, [[world generation|generate a new world]], then edit the raws of the new world to change the maggots back to normal before embark.

{{Translation| dwarven = kor | elvish = nunòre | goblin = aspâd | human = rushan}}

{{World|Biomes}}

Farming

2022-12-03T12:10:04Z

Xjtu-blacksmith: ILL

{{Quality|Masterwork|23:04, 8 April 2015 (UTC)}}
{{av}}
[[Image:Df-crops-diagram.png|thumb|200px|General farming flowchart.]]

'''Farming''' is the act of growing [[crop|crops]] for [[food]], [[alcohol]] production, [[cloth]] manufacturing, and [[paper]] making. While small forts can easily be sustained by plant gathering, [[hunting]] and trading, farming is vital to large settlements.

Farming is done at a '''farm plot''' building ({{k|b}}-{{k|p}}, resize with {{k|u}}{{k|m}}{{k|k}}{{k|h}}). Building uses no resources, and can only be done on [[soil]] or [[Irrigation|muddied rock]]. Mud-free stone will not allow the building of a farm plot on top. Farming requires the "Farming (Fields)" [[labor]], and uses the [[Grower]] skill. Farm plots only display the kind of crops that they are able to grow when selected with the {{k|q}}uery key.

Depending on [[Tile attributes|where the farm plot is constructed]], different crops may be planted. Farm plots built {{DFtext|Above Ground|2:1}} are not suitable for {{DFtext|Subterranean|0:1}} crops and vice versa. Note that the attributes {{DFtext|Inside|6:0:0}}, {{DFtext|Outside|3:0:1}} are of no relevance. You can grow surface plants indoors by channeling out the roof above the desired plot and then constructing a floor ({{k|b}}-{{k|C}}-{{k|f}}) over the open space. Doing this changes the tile from {{DFtext|Dark|0:0:1}} to {{DFtext|Light|6:0:1}}, despite there being a roof (you do '''not''' need to make the roof out of [[glass]] for this to work). A plot with mixed {{DFtext|Light|6:0:1}} and {{DFtext|Dark|0:0:1}} tiles may show plants as "available" when only a tiny fraction of the tiles in the farm are valid for planting them.

Note that although you can construct a farm plot anywhere there's either a soil floor or a mud covering, this doesn't always mean the seeds you have – especially imported ones – can be planted there. Not all crops can be grown in a given [[biome]], and some biomes will prevent the planting of '''all''' above-ground crops. Even seeds you obtained as a result of [[plant gathering]] might not be plantable where you've chosen to put your farm, if they came from a different biome.

The yellow warning message, {{DFtext|No mud/soil for farm, Mud is left by water|6:0:1}}, is displayed on all above-ground tiles, regardless of whether the farm will function.{{version|0.34.11}} This warning may be ignored. Tiles that actually lack mud or soil are excluded from the construction entirely with a red warning message (either {{DFtext|Blocked|4:0:1}} or {{DFtext|Needs soil or mud|4:0:1}}). See the article on [[crop]]s for details on the conditions needed to grow the available plants.

== Introduction to Farming ==

=== Building a farm ===

[[File:farm_view.jpg|thumb|301px|right|Enough to feed 1 dwarf for 2 days!]]First, select an area for your farm. Building a farm on a [[soil]] layer is easiest (farming in non-soil layers will require [[irrigation]]). Aboveground farms can simply be built on the surface (though this exposes your farmers to attack); subterranean farms will need to have a suitable area dug out underground. Once you've decided on a location, open the {{K|b}}uild menu and select {{K|p}}lot to build your [[Farming|farm]].

To define the width and height of your farm plot, use {{K|u}} to increase vertically, {{K|m}} to decrease vertically, {{K|k}} to increase horizontally, and {{K|h}} to decrease horizontally. Keep your farms ''small'' – 2x2, up to 4x4, or so. Farms are surprisingly productive. You can always make more farms later if you run low on plants, and having several small farms lets you diversify your crops. (Each farm plot can only grow one kind of plant per season.) Position the farm plot with the directional keys as normal. Once you are satisfied with the size and position of the plot, confirm it with {{k|Enter}}, and{{K|Esc}} out of the build menu. Now a dwarf with the "Farming (Fields)" labor will come and prepare the plot for planting. (If you don't have a dwarf with farming enabled, the farm plot won't get built.)

Once the farm plot has been built, you must select which crops to grow. Press {{k|q}} and move the cursor over the farm. You will see a list of crops you can select to grow in the local biome and current season. Move the blue selector up and down with {{k|-}} and {{k|+}}, and press {{k|Enter}} to choose a crop to plant during that season (highlighted in white). {{DFtext|Crops displayed in red|4:0:1}} cannot be grown at the moment, either due to a lack of seeds, or (if you have seeds) a lack of growing days left before the crop goes out of season. You can change which season is displayed by pressing {{k|a}},{{k|b}},{{k|c}}, or {{k|d}}. Make sure each season has a crop selected, otherwise you'll end up with an idle field for that 1/4 of the year. Instructing a plot to remain fallow ({{k|z}}) during a particular season will tell dwarves not to plant in that plot during that season, though there is little reason for this. Currently, unlike in real life, crop rotation is not necessary; soil productivity is only affected by fertilizing, and the same crop may be grown indefinitely without a decrease in performance, even without fertilizer.

From the {{k|q}}uery menu, you can press {{k|f}} to fertilize your crop with [[potash]]. Fertilized crops produce larger stacks of plants, which can be vital to grow your [[seed]] supply early on and your food supply later on. Pressing {{k|s}} enables the "Seas Fert" option, which automatically fertilizes this particular plot at the beginning of each season (assuming your dwarves have sufficient [[potash]]). You must have the appropriate [[seed]]s to plant a crop on a plot. To easily see how many of each seed you have, you can go to the Kitchen menu ({{k|z}} {{k|right}} {{k|Enter}}).

Since your dwarves require food, booze and clothing, you should set up a combination of plants that will supply all of these. [[Plump helmet]]s are a good beginning crop for a first cave farm, and [[Strawberry|strawberries]] are a good choice for outdoor fields – both can be eaten raw, or brewed. [[Pig tail]]s produce cloth, which will become important once your clothing starts to [[wear]]. Check the [[crop]]s page for details on different seeds. Cooking plants destroys their seeds, so you should disable the cooking of plants in the Kitchen menu. Eating them, brewing them, or processing them through a farmer's workshop, quern, or millstone, will produce seeds.

'''Help, my farmers won't farm!'''

*Verify that you have farmers – that is, dwarves with the "Farming (fields)" labor enabled, and verify that your farmers have free time – farming appears to be a low-priority task, so it's a good idea to disable ALL other labors on one or two dedicated farmers. (Experienced farmers also produce better yields.)

*Verify that the farm plot has a crop selected for the current season. (Each season must be set up separately, and some crops only grow in certain seasons.)

*Verify that you have [[seed]]s for the chosen crop, and that those seeds are accessible to your farmers (not [[forbid]]den, locked behind a door, being carried across the map by one of your haulers, etc.).

*Verify that your farmers can reach your farm plot (no locked doors, disconnected stairways, etc.).

*Verify that your farm plot is acceptable. An underground plot that has been exposed to sunlight will never grow underground plants again. It may be necessary to remove the plot and rebuild it so that you can select aboveground crops to plant. Farm plots which are partially belowground and aboveground will never be fully planted. Additionally, some aboveground [[biome]]s (such as [[mountain]]s and [[glacier]]s) are unsuitable for farming and will never grow crops.

== Yield and fertilization ==

{| class="wikitable" style="float:right; margin: 1em"
! Farm Size !! Potash !! Per Square
|-
| 1 (1x1) || 1 || ''1.000''
|-
| 2 (1x2) || 1 || 0.500
|-
| 3 (1x3) || 1 || '''0.333'''
|-
| 4 (1x4, 2x2) || 2 || ''0.500''
|-
| 5 (1x5) || 2 || 0.400
|-
| 6 (1x6, 2x3) || 2 || 0.333
|-
| 7 (1x7) || 2 || '''0.286'''
|-
| 8 (1x8, 2x4) || 3 || ''0.375''
|-
| 9 (1x9, 3x3) || 3 || 0.333
|-
| 10 (1x10, 2x5) || 3 || '''0.300'''
|-
| 11 (''n/a'') || 3 || '''''0.272'''''
|-
| 12 (2x6, 3x4) || 4 || ''0.333''
|-
| 15 (3x5) || 4 || '''0.267'''
|-
| 16 (2x8, 4x4) || 5 || ''0.312''
|-
| 18 (2x9, 3x6) || 5 || '''0.278'''
|-
| 19 (''n/a'') || 5 || '''''0.263'''''
|-
| 20 (2x10, 4x5) || 6 || ''0.300''
|-
| 21 (3x7) || 6 || '''0.286'''
|-
| 23 (''n/a'') || 6 || '''''0.261'''''
|-
| 24 (3x8, 4x6) || 7 || ''0.292''
|-
| 27 (3x9) || 7 || '''0.259'''
|-
| 35 (5x7) || 9 || '''0.257'''
|-
| 36 (4x9, 6x6) || 10 || ''0.278''
|-
| 39 (''n/a'') || 10 || '''''0.256'''''
|-
| 42 (6x7) || 11 || '''0.262'''
|-
| 43 (''n/a'') || 11 || '''''0.262'''''
|-
| 45 (5x9) || 12 || 0.267
|-
| 47 (''n/a'') || 12 || '''''0.255'''''
|-
| 49 (7x7) || 13 || 0.265
|-
| 50 (5x10) || 13 || '''0.260'''
|-
| 51 (''n/a'') || 13 || '''''0.255'''''
|-
| 63 (7x9) || 16 || '''0.254'''
|-
| 75 (''n/a'') || 19 || '''''0.253'''''
|-
| 90 (9x10) || 23 || 0.256
|-
| 91 (''n/a'') || 23 || '''''0.253'''''
|-
| 99 (''n/a'') || 25 || '''''0.253'''''
|-
| 100 (10x10) || 26 || ''0.260''
|}
Each farm tile requires a single seed to be planted. Unfertilized farm tiles can produce a stack of 0-6 plants when harvested, depending upon the [[Grower|skill]] of the planter and random chance. Experimentally, fertilizing a farm plot boosts production by 1-3 additional plants per stack each harvest, though the exact mechanism is unknown. For unskilled planters, yield can be effectively doubled with the use of fertilizer. This can be particularly important early on, when your fortress's seed supply is limited, because those extra plants mean more seeds for planting next season. Many crops, like quarry bushes, are impossible to farm effectively in the beginning without fertilizer. Larger harvest stack sizes can also dramatically increase the efficiency of downstream industries; see the [[grower]] article for more discussion. To fertilize a farm plot, one needs [[potash]], which is produced by processing [[ash]]. Each plot must be re-fertilized each season, and the fertilizer must be in place at the time the seeds reach maturity. It does not matter whether the plot is fertilized at the time of planting. {{cite forum|139382/5375231}}

Fertilizing a farm plot requires ''floor(plot_size / 4) + 1'' potash. The table on the right illustrates the efficiency of potash as a function of plot size - the most efficient (for a specific amount of potash) are in '''bold''', the least efficient are in '''italics''', and sizes that are most efficient but very difficult to create in-game (not rectangular numbers less than or equal to 10 per side) are both '''''bold & italicized'''''. Generally, larger farms use less, approaching a limit of 1/4 bar per square. The worst yields per tile are multiples of 4; if one plans to optimize harvest yield, it's most efficient to have plots of size ''4n - 1'', where n is the number of potash used. Suitable sizes are 1x3, 1x7, 3x5, 3x9, 5x7, and 7x9. If one plans to optimize farmer experience, plots of size 2 or 4 can be fertilized and seeded quickest, and experience can be distributed among more farmers. This ensures that if a bounty of crop is needed in the future, your farmers can yield more without potash, can plant and harvest quicker, and will have more time for other jobs in between. Of course, the price you'll pay for this is more time spent highlighting each individual farm and changing the crops if you wish to adjust your farming plan.

Fertilizer may be applied to a plot by pressing {{k|f}} while viewing the plot. Only dwarves with the Farming (Fields) labor will apply fertilizer; this grants 30 XP of farming experience for each unit of potash used. Pressing {{k|s}} toggles seasonal fertilization. This does nothing until the next [[season]], at which time the plot will be automatically fertilized. Note that if you do not have a potash stockpile near your farm plots, your legendary farmers may spend all of their time hauling single bars of potash from all the way on the other side of your fortress, rather than growing food.

'''Potash Production Chain:'''
Wood [[Stockpile]] > Wood [[Furnace]] produces [[Ash]] (as [[bars]]) > [[Ashery]] produces [[potash]] (as [[bars]]).
Note: 5 bars are stored in a [[bin]]. An [[Ashery]] requires a [[block]], barrel, and bucket as components.

=== Exact yield mechanics ===

*Base yield is set to 1.
*If the farm plot is at least 25% fertilized, increase yield by rand(2) (a random number from 0 to 1).
*If the farm plot is at least 50% fertilized, increase yield by rand(2).
*If the farm plot is at least 75% fertilized, increase yield by rand(2).
*If the farm plot is 100% fertilized, increase yield by rand(2).
*If rand(5) (a random number from 0 to 4) is less than the Planting skill for the seed (the Farmer's skill level when the seed was planted, capped at 20 = Legendary+5), increase yield by rand(2).
*If rand(10) is less than the Planting skill for the seed, increase yield by rand(2).
*If rand(15) is less than the Planting skill for the seed, increase yield by rand(2).
*If rand(20) is less than the Planting skill for the seed, increase yield by rand(2).
*If rand(25) is less than the Planting skill for the seed (again, capped at 20) and rand(3) is equal to 0, increase yield by rand(2).

== Subterranean farming ==

To grow the six "dwarven" plants, you will need an underground farm plot. The seeds and spawn available to your dwarves at embark will only grow underground. Underground farm plots must be placed on soil or [[mud]]dy stone.

Muddying a stone floor requires temporarily covering it with water; common methods include a [[Irrigation#via_Buckets|bucket brigade]] or '''controlled''' [[flood]]ing (see: [[Irrigation]]) by temporarily diverting a river or pool, using a [[floodgate]] or [[door]] to stop the flow. You may also find a muddied area in a [[cavern]], but note that each tile underneath the farm plot must be muddied. Most caverns have entire open areas which will be permanently covered in mud, but if you dig into the walls of a cavern or chisel away a pillar, the freshly cut floor area will not be muddied until you get it wet. Underground caverns are dirty, and frequently contain [[Mud|piles of mud]] that are perfect for quickly setting up farms. However, given the wide variety of creatures found in caverns, you may want to take precautions. Consider keeping a [[squad]] close at hand to guard the farm, or walling off a muddied area for your dwarves' exclusive use.

Underground farming is not restricted to soil layers and caverns; underground floor of any material – rough stone, smoothed stone, ore, gem – can support subterranean farm plots once there is a layer of mud covering it. See [[irrigation]] for tips on getting the right amount of water to the farm plots.

== Above-ground farming ==
Farming of above ground crops is only possible on tiles that lie in a biome supporting their growth. Which crops are farmable depends on the biome - only plants ''native'' to a biome can actually be grown in a location: you cannot farm [[yam|yams]] in a [[taiga]], or [[hemp]] in a [[tropical]] rainforest. There are also biomes where aboveground farming is entirely impossible, since no crops are native to them: these are the notoriously cold [[glacier]] and [[tundra]], but also all [[mountain]] and [[ocean]] [[biome]]s. The most widespread crops can be farmed in all land biomes with the exceptions mentioned above; this ubiquitous availability uses the internal reference NOT_FREEZING, but that label is somewhat misleading, since it's a [[Biome token|shorthand]] for a group of specific biomes and doesn't imply anything about the actual temperature - mountains and oceans are generally infertile, no matter what temperature range the embark screen lists, and a [[Taiga]] with "freezing" temperatures allows farming above ground plants.

Above-ground farming is basically the same as underground farming, with the simplifying distinction that above ground plots typically do not require preparatory work. However, there are some complications.

The first complication is that seeds cannot be chosen at embark, as dwarven civilizations do not have access to those sort of plants. They can be bought from [[Elves|elven]] and [[human]] caravans; above-ground plants can be gathered using the [[Plant gathering]] designation, and then [[brewer|brewed]], [[miller|milled]], [[thresher|threshed]] or [[food|eaten]] directly (depending on the plant) to produce seeds.

The second complication is that the farming must be done on [[soil]] or muddied rock, which is [[above ground]]. Typically, it is done on the surface, which is dangerous (due to aggressive animals, ambushes and sieges). However, any land which has ever been exposed to sunlight becomes permanently marked as "above ground". So, if you have multiple Z-layers of soil; you can channel some above-ground land, remove the resulting ramps, then construct a floor, above where the surface once was. The (now inside and protected) lower soil will still be suitable for farming outdoor plants like [[strawberry|strawberries]], [[longland grass]], [[rope reed]], and anything else you may find. If your soil is not thick enough, you may still get a secure above ground farm by doing the same with any stone and muddying it. Alternatively, you may build a greenhouse by [[wall]]ing around some soil.

The various crops require particular environments to grow. On an embark which crosses multiple biomes, it's not unusual for aboveground farms in different biomes to have different lists of available crops.

Note that when creating an above ground plot, the interface may incorrectly display "No mud/soil for farm", even though mud is present. {{bug|249}} The message can be ignored.

== Farm plots in action ==
{| class="wikitable" style="float:right;margin:1em;width:35%"
|+ Growth duration for subterranean crops
|-
! Crops !! Game [[Time|ticks]] until harvest !! Days until harvest
|-
| Plump helmet, pig tail || 30000 || 25 days
|-
| Cave wheat, sweet pod, quarry bush, dimple cup || 50000 || 41.666 days
|}

Once a farm plot has been built and crops have been selected for the current season, dwarves with the "[[Grower|Farming (Fields)]]" labor enabled will begin planting the selected seeds. One seed is used per tile. The higher a dwarf's grower skill in planting, the more plants will be harvested from each seed planted. The farming labor is fairly low in priority, so if you want a full-time farmer, it is best to disable all other labors.

Plants take time to grow, depending on their type. Once a plant is fully grown, a dwarf will harvest it. By default, any dwarf will do this. Harvesting plants is not affected by any skill, although it provides a small amount of grower experience. So it's a good idea to set only your planters to harvest, not anyone. To do that, set option "Only Farmers Harvest" {{k|o}}{{k|h}}. This is useful only to train your planter faster; once they're skilled enough, everyone can be allowed to harvest again so the haulers can take care of half the farming work.

<div style="float:right">
{| style="border-spacing: 0"
|{{RT|≈|6:0}}||{{RT|`|0:1}}||{{RT|τ|6:1}}||{{RT|═|6:0}}||{{RT|≈|6:0}}
|-
|{{RT|≈|6:0}}||{{RT|≈|6:0}}||{{RT|τ|6:1}}||{{RT|═|6:0}}||{{RT|≈|6:0}}
|-
|{{RT|≈|6:0}}||{{RT|≈|6:0}}||{{RT|τ|6:1}}||{{RT|═|6:0}}||{{RT|≈|6:0}}
|-
|{{RT|≈|6:0}}||{{RT|τ|6:1}}||{{RT|═|6:0}}||{{RT|≈|6:0}}||{{RT|≈|6:0}}
|-
|{{RT|≈|6:0}}||{{RT|τ|6:1}}||{{RT|═|6:0}}||{{RT|≈|6:0}}||{{RT|≈|6:0}}
|}
</div>
In the farm plot shown on the right, {{Tile|≈|6:0}} indicates tiles awaiting planting, {{Tile|═|6:0}} indicates tiles that have been planted and are now growing, and {{Tile|τ|6:1}} indicates [[longland grass]] plants that are ready for harvesting.

If harvested plants are not moved to a stockpile in time, they will wither, and eventually [[rot]] away, there being no use for withered plants. If, when the seasons change, the previous crop can not grow anymore, all immature plants will be destroyed, yielding neither seed nor plant. If the farmers are "aware" of this limitation, they will automatically stop planting crops that haven't enough time to ripen, but you might lose a few seeds in your first year when growers of insufficient skill plant seeds too close to the cutoff. Depending on the number of growers and their experience and the rate at which the plant grows, not all squares of large plots may be used. Any farm plot that has both Above Ground and Subterranean tile attributes within the plot will only be partially-planted, if at all. Verify using {{k|k}} over each square of the plot and remake as needed to follow the proper attributes.

=== Farm size ===
{{main|Farm size calculations}}

A beginning fortress has 7 dwarves, each of which consumes 7 units of food and drink per dwarf per season, needs 196 for the whole fortress for the year. This starting group can theoretically be supported by a single farm tile, but in practice a larger farm will be necessary since a young fortress is unable to use farm tiles to their fullest potential.

A properly-managed and fully-utilized 3x3 plot growing plump helmets can produce an average of up to 2700 units of alcohol per year, enough to provide food (through booze-cooking with seeds) and drink for a fortress of 95 dwarves. A similar 5x5 plot can produce up to 7500 units of food and drink per year, enough to support 265 dwarves.

== Management ==
Use the [[stocks]] menu, and go to the Kitchen tab. From here you can see how many of each kind of food you have. If you're running out of a certain kind of seed, toggle the corresponding plant "Cook" setting to red. [[Cooking]] plants doesn't leave a seed. If you have too many of a certain kind of seed, or of plump helmet, as noted above, toggle the seed "Cook" setting to blue. Just make sure you check on the stocks and toggle it back before you run out. It may also be a good idea to set aside a few seeds from each type of crop and [[forbid]] them, as a seed bank in case of [[fun|fun times]].

=== Managing seeds ===
[[Seed]]s are used to grow [[crop]]s. You may begin the game with a certain number of seeds, [[trade]] for them, or [[plant gathering|gather]] them. In addition to this, eating, [[milling]] and [[brewing]] plants often yield a seed (assuming your fortress hasn't hit the seed cap for that plant). [[Cooking]] plants does not yield seeds, and cooking seeds makes them unusable for planting, so you may want to watch out and make sure you don't convert the last of your plants into +strawberry roast+ without the ability to make more.

You can create a custom [[stockpile]] near your [[farm]] which will only accept [[seed]]s. This will consolidate your seeds into one place, instead of having them littered all through the [[dining room]]. Seeds are stored in [[bag]]s (up to 100 seeds per bag), and seed bags can be stored in barrels. However it is recommended to not use barrels on seed stockpiles, since the hauling habits lead to barrels getting carted around to collect each and every loose seed, interrupting the planting work; see the [[#Bugs|Bugs]] section below for workarounds.

For DF2014 the theoretical seed stockpile maximum size is 31 tiles for 200 seeds of each of 155 crops, but the actual maximum needed is much less because no fort will be situated in the right place to grow all of those. Four tiles gives enough space for 20 different crops.

Each plant has a fortress-wide seed cap set at 200 (this value can be adjusted in [[d_init.txt]]). [[Brewing]], [[milling]], and [[food|eating]] raw plants will not generate additional seeds once the cap is reached, although you may still get additional seed bags via [[trading]] and thus exceed this limit. Once the count of seeds falls below 200, new seeds will again be generated.

There is also a fortress-wide total seed cap, initially set at 3000 (also configurable in [[d_init.txt]]). Once your fortress reaches this cap new seeds will still be generated, but the oldest seeds on the map will disappear. Unfortunately, this cap counts all seeds on the map, including those carried by traders {{bug|8108}}, and removes old seeds even if they have already been planted {{bug|8107}}. Finally, because the two caps behave differently, they can cause undesirable behavior when both are in operation {{bug|8091}}.

Seeds may be toggled for [[cooking]] on the Kitchen tab of the [[stocks]] menu. Disabling seed cooking will keep your seeds safe from starving dwarves. Although the item properties label them as EDIBLE_RAW, [[quarry bush|rock nuts]], like all other seeds, are ''not'' consumed as-is.

=== Managing crops ===
When your [[crop]]s are ripe, your dwarves will harvest them from the farm plots. This will yield one or more [[stack]]s of [[plant]]s, which will be [[hauling|hauled]] to the appropriate [[stockpile]]. It is generally a good idea to have sufficient [[barrel]]s to hold the food, as [[food]] is subject to [[wear|withering]] and the predation of [[vermin]]. [[Metal]] barrels are especially effective against vermin. You can create a custom stockpile that will only accept [[plant]]s, to avoid having it all mixed up with your [[meat]] and [[drink]]s. It would be a good idea to have this stockpile near your [[still]], [[farmer's workshop]], [[kitchen]], etc. You may also choose to make more specialized stockpiles, for instance if your [[windmill]] is located far away from your farms, you might have small nearby stockpiles dedicated solely to millable plants and [[flour]] so as to save on hauling.

The Kitchen tab on the [[stocks]] menu allows you to control which crops, if any, your dwarves will use as ingredients when cooking. Be careful when you are cultivating new crops or running low on others, and make sure you don't cook the last of them instead of recovering the valuable seeds. Note that experienced [[farmer]]s and crop [[fertilize|fertilization]] significantly increase the return on planted seeds, and can be quite useful when attempting to build your seed stockpile.

If you suffer from plump helmet overflow, create a plump-helmet-only stockpile, forbid plump helmets from all other food stockpiles, and let the crops in the field die if they can't be picked. It is worth noting that withering crops in the field do not produce miasma.

== Adventure mode ==

Interestingly, farming does work in adventure mode, though it requires the use of [[DFHack]]'s advfort plugin - buy fruit at a market, brew them into booze and seeds, build farming plots, plant the seeds. Unfortunately the time it takes for stuff to grow is adapted to fortress mode, and it make an inordinate amount of time for your adventurer to do a single harvest.

== Bugs ==

* "Store item in container" jobs block access to items already in the container. This causes stored seeds to become unavailable, spamming job cancellations. {{bug|9004}}
** Workaround #1: set your seed stockpile to only take from links ({{k|a}}). When seed supplies run low, toggle it back to "anywhere" temporarily to gather up all the loose seeds.
** Workaround #2: disable barrels ({{k|E}}) in the seed stockpile. This means making the stockpile larger, as only one seed bag will be stored per tile. However, at 100 seeds per bag and with the 200 seed cap per seed type (cf. [[seed]]), this still only amounts to 12 tiles for a full underground-crop seed stockpile, assuming each seed type is only stored in 2 bags. Haulers will still lock a whole bag to gather individual seeds, but this is better than locking a whole barrel full of seed bags.
** Workaround #3: create two custom [[stockpile]]s which only accept [[seed]]s. Disable barrels in the first stockpile, and set it to give to the second stockpile. Set the second to only take from links.
** Workaround #4: disable seeds in all stockpiles and recruit a few extra farmers. No hauled seeds means no planting job cancellation spam.
* Fortress-wide seed cap counts seeds carried by traders {{bug|8108}}
* Fortress-wide seed cap removes seeds that have already been planted {{bug|8107}}
* Conflict between seed caps can cause all seeds for a crop to disappear {{bug|8091}}
* Some crops can't be processed, and so can't be used or replanted {{bug|6940}}
** [http://www.bay12forums.com/smf/index.php?topic=162231.msg7321878#msg7321878 partial workaround] by editing the raws for bitter vetch (possibly works for other crops too)

== Caveats (warnings) ==

=== Red crops ===

Crops will sometimes be displayed as red in the field listing. This means that planting the crop would be fruitless, as it will not survive long enough to be harvested (due to it not being plantable during the next season). Note that this will only happen if your dwarves actually '''know''' that the crop will die, which will be learned either by observation (i.e. having the seeds die during a season transition) or by being planted by a sufficiently skilled Farmer.

== See also ==
* [[Irrigation]]
* [[Tile attributes]]
* [[Crops]]
* [[How large a farm do i need|How large a farm do I need?]]

{{Translation| dwarven = ivom | elvish = tòbafí | goblin = gotåm | human = ab}}

{{Category|Buildings}}
{{Category|Agriculture| }}
{{Industry}}
[[ru:Farming]][[zh:Farming]]

Remains

2022-12-02T14:00:06Z

Xjtu-blacksmith: ILL

{{Quality|Fine|11:57, 18 May 2015 (UTC)}}
{{av}}
{{infostart|Remains}}
{{infocell|{{#tag:nowiki|{{char|{{char|253}}}}}}|style=color: {{fgcolor|5:0:0}}; background: black; font-size:x-large; font-weight: bold; font-family: 'Courier New', 'Quicktype Mono', 'Bitstream Vera Sans Mono', 'Lucida Console', 'Lucida Sans Typewriter', monospace; text-align:center; vertical-align:center}}
{{infoend}}The [[corpse]]s of [[vermin]] are called '''remains'''. Unhappy dwarves in a macabre [[strange mood]] will sometimes request vermin remains to construct their [[artifact]]s. Remains cannot be [[butcher]]ed, and are not otherwise useful.

Creatures with the [[Creature token#H|<tt>HUNTS_VERMIN</tt>]] tag, notably [[cat]]s, will kill vermin, leaving the remains scattered around the fort. (Cats who have adopted a dwarf seem to drag the remains of vermin they kill to their <s>owner</s> slave). While this prevents unhappy [[thoughts]] from [[vermin#Hateable vermin|hateable vermin]], it can also cause areas of your fort to become littered with remains if not properly [[stockpile#Refuse|taken care of]].

[[Honey bee]]s, for example, will leave behind remains after stinging.

With time, remains rot away. Unlike corpses, remains do not cause miasma or leave [[bone]]s upon full decomposition; they simply disappear. Remains are stored in a [[stockpile#Refuse|refuse stockpile]], subject to [[standing orders]] refuse settings.

[[Night troll]]s have vermin remains on tables or in cauldrons, because they have the habit ({{token|HABIT|c|COOK_VERMIN}}).

{{category|Body parts}}
[[ru:Remains]][[zh:Remains]]

Utility:Lazy Newb Pack

2022-12-02T07:49:24Z

Xjtu-blacksmith: ILL

{{Quality|Exceptional|02:12, 3 November 2014 (UTC)}}
{{uv|DF2014}}

The '''Lazy Newb Pack''' or '''Starter Pack''' are [[utility|packages]] to get people started with ''Dwarf Fortress''. They bundle the game with some of the best community graphics packs, tools, and interface improvements already configured. Simply download the version that matches your operating system, and start playing ''Dwarf Fortress''.

Despite the name, the modern packs are ideal for new and veteran players alike. Using a pack lets you focus on playing the game, while still having access to quality-of-life additions like graphics/tilesets, utilities, and being able to change common settings without editing text files.

Packs also make a great basis to start your own set of [[utilities]] from as you don't need to find, configure, compile, install, and update every tool for yourself.

Separate packs are available for Windows, Mac, and Linux. Each platform's version is maintained by different community contributors. These can be found further down this page, see: [[#Where do I get a Pack?]].

== What is a Pack? ==

A Starter pack (sometimes referred to as a "Lazy Newb Pack") is a pack that includes many utilities that a veteran player might want, while configuring everything in such a way that it is still easier for new players. In general, it's safe to simply ignore any option you don't understand and trust that the default settings will be okay.

The packages are built around the idea that newbies will likely have more difficulty with the game than with a package of utilities - which often make the game easier - and that there are many players who are not new but would still prefer an option to get all the extras in one place with a minimum of fiddling. Most include just about everything that still works and could be useful.

It is also important to note that most of the contents of each pack were created by many members of the community and just collected, configured, and redistributed by the maintainer of each pack. Of course there are a few personal touches too, but the vast majority of each is thanks to others - and not least Tarn and Zach for ''Dwarf Fortress'' itself.

;Pack options overview: 
<gallery mode="packed" heights=300px>
File:Lnp-gui1.png|Options tab
File:Lnp-gui2.png|Graphics tab
File:Lnp-gui3.png|Utilities tab
File:Lnp-gui5.png|Advanced tab
File:lnp-dfhack.png|DFHack tab
</gallery>

== Where do I get a Pack? ==

There are several packs available for different platforms, with different maintainers and release schedules.

===Windows: PeridexisErrant's DF Starter Pack===
* DF v0.47.05
* Maintained by [[User:PeridexisErrant|PeridexisErrant]]
* [http://www.bay12forums.com/smf/index.php?topic=126076 Forum thread]
* [https://dffd.bay12games.com/file.php?id=7622 Download] ([http://df.wicked-code.com/ mirror])
* [https://github.com/PeridexisErrant/starter-pack Related GitHub repo]

This pack is maintained by PeridexisErrant, and aims to include everything - while ensuring that ignoring any option still works for new players. Contents and a changelog are listed on the forum thread (linked above).

Legacy versions are available on DFFD for some notable DF versions:
* [https://dffd.bay12games.com/file.php?id=14793 0.44.12]
* [https://dffd.bay12games.com/file.php?id=13201 0.43.05]
* [https://dffd.bay12games.com/file.php?id=12936 0.43.03] (the last 32-bit version of this pack)
* [https://dffd.bay12games.com/file.php?id=11309 0.40.24]
* [https://dffd.bay12games.com/file.php?id=8687 0.34.11]

===Linux: LinuxDwarfPack===
* DF v0.47.05
* Maintained by McArcady
* [http://www.bay12forums.com/smf/index.php?topic=157712 Forum thread]
* [https://dffd.bay12games.com/who.php?id=7393 Download] ([https://github.com/McArcady/lnp-forge/releases/ mirror])
* [https://github.com/McArcady/lnp-forge/actions?query=workflow%3A%22Build+LinuxDwarfPack+package%22 Continuous builds]
* [https://github.com/McArcady/lnp-forge Related GitHub repo]

A simple ready-to-play pack for Linux, with tilesets and utilities. Packages are available for Debian/Ubuntu, Redhat, Arch and in AppImage format.

A legacy version of this pack for v0.44.12 is also available [https://dffd.bay12games.com/file.php?id=14668 here].

===Linux: LinuxLNP===
* DF v0.47.04
* was Maintained by Enay
* [http://www.bay12forums.com/smf/index.php?topic=163211.0 Forum thread]
* Discontinued

This package was a traditional package of compiled utilities, maintained and tested on Debian Jessie (64bit). It worked out-of-the-box with Debian-derived (Ubuntu, Mint, etc.) distributions, but is no longer supported, updated, or available.

An unofficial RPM package of this pack for Fedora can be found [https://github.com/corollari/lazy-newb-pack-fedora here].

===Mac: Lazy Mac Pack===
* DF v0.47.05
* Maintained by Jecowa
* [http://www.bay12forums.com/smf/index.php?topic=158322.0 Forum thread]
* Downloads: [https://dffd.bay12games.com/file.php?id=12202 DFHack version], [https://dffd.bay12games.com/file.php?id=12310 lite version]

A Lazy Newb Pack for Mac with lots of graphics packs but with not so many utilities. The "lite" version includes fewer utilities - see the forum thread for details.

===Mac: Elpuma's Mac Starter Pack===
* DF v0.47.05
* Maintained by Elpuma
* [https://dffd.bay12games.com/file.php?id=13905 Download] ([https://github.com/jipumarino/dfdl/releases/tag/0.4.2 outdated mirror])
* [https://github.com/jipumarino/dfdl Related GitHub repo]

This is actually a script to download the individual parts and assemble them into a pack you can run. See the readme on the repo for usage instructions to get an updated pack.

== History of packs==
[[File:Lazy-newb-pack-screenshot.0.31.12.v4.6.png|thumb|Screenshot of the primary user interface in Lazy Newb Pack v4.6 for DF 0.31.12 from June 2010. Created on Linux in 2017 with wine. ]]
[[File:Lazy-newb-pack-screenshot-v7-2010.png|thumb|Screenshot of the LucasUP released in 2010]]

Maintaining a pack is a lot of work, and over the years, people inevitably lose time or motivation to update their packs. Eventually, someone new steps up and releases their own pack.

This section is provided for information, and should not be interpreted as a recommendation for these packs. It may however be interesting to look back at how the LNP/Starter Pack movement evolved.

==== The first Lazy Newb Pack ====

The first pack with the name Lazy Newb Pack (LNP) was created by [http://www.bay12forums.com/smf/index.php?action=profile;u=16293 LucasUP] for Windows and DF version 0.31.12 and posted [http://www.bay12forums.com/smf/index.php?topic=59026 in the bay12forums] on June 11, 2010. Before the LNP, it was becoming common for the community to bundle up their own distributions of ''Dwarf Fortress'' with tile sets, graphics, and mods to make them more accessible to players. Other notable packs from this era are [http://www.bay12forums.com/smf/index.php?topic=57557.0 Phoebus graphics] and [http://www.bay12forums.com/smf/index.php?topic=53649.0 Mayday's Graphic Set]. The LNP distinguished itself by providing an interface for changing common DF settings, instead of editing the raw text files included with the game.

The first versions of the LNP included a text-based interface (seen on the right) that only permitted the user to enable/disable [[aquifers]] and choose from the Phoebus, Mayday, and Ironhand graphics packs. They included the utilities [[DFHack]], [[Utility:DwarfForeman|Dwarf Foreman]], [[Dwarf Therapist]], [http://www.bay12forums.com/smf/index.php?topic=57428.0 PerfectWorldDF], [http://www.joelpt.net/quickfort/ Quickfort], [http://www.bay12forums.com/smf/index.php?topic=59056.0 Runesmith] , [[Stonesense]].

==== The original launcher with a GUI ====
On December 31, 2010 [http://www.bay12forums.com/smf/index.php?topic=59026.msg1845333#msg1845333 LucasUP released] the first version of the Lazy Newb Pack that contained the graphical interface launcher that is well known today. It became the key component of the pack, which allows easy configuration of the DF installation, choose graphics packs, launching of utilities, and provided one click toggling of settings instead of editing configuration files by hand. The original launcher was built with Visual Basic and .NET 3.5, and for several years this meant that the LNP was only available for Windows systems.

In 2012 Dricus created a [http://www.bay12forums.com/smf/index.php?topic=124613 Java-based launcher], which was cross platform and more flexible, but also required manual configuration. This launcher was never finished and so never achieved wide usage, however some early Mac and Linux packs were available based on this version. It wasn't a complete pack, but just the launcher component that could be used to build platform-specific packs.

==== The End of the First Age ====

In order to elicit help and contributions from the community LucasUP opensourced his graphical interface in February 2013 by releasing [https://github.com/LucasUP/LazyNewbPack/ the source on github] ([http://www.bay12forums.com/smf/index.php?topic=123384.0 forum post]).

By the late autumn of year 2013 the LNP was out of date with new DF releases, and users were clamoring for an update. LucasUP's life had become too busy to focus on the LNP. On November 16, 2013 LucasUP declared his tenure as overseer over, thanked the community for their support and gave his blessings for the successor packs that had appeared on the scene.

<blockquote>
<div style="border: 1px dashed grey; padding: 5px;">
Hello guys. I think I have to apologize for my long absence. :(

Yes it was my intention to let others work on and maybe eventually take over The Lazy Newb pack after I had released it open source. But It was NOT my intention to go dead silent for so long and have it be such a forced/jarring transition. I'm really sorry about that.
Of course other life responsibilities took me away from LNP, but I don't really have great excuses for why I didn't at least give you guys any updates on myself or re-direct you to other versions sooner, other than just my mind has been elsewhere.

Sorry for any frustration this has caused you guys, and I hope I haven't caused too much ill-will. I feel like a jerk and like I've just been trying to avoid confronting that. :(
I've updated the OP to link to the new Windows/Linux/Mac packages. If there's anything else you guys would like to see from me, I am happy to hear from you.
I do read and respond to my PMs too, if you wanted to say/ask me something in private.

Edit:

I just also wanted to say, on a more positive note, that I am really happy and proud to see how many people have cared enough about LNP to want to continue it and work on it. The fact that there is now working and regularly updated Win/Mac/Linux versions is really fantastic, and its something I would have never achieved myself. So, thanks to the DF community! You guys and girls are awesome.
</div>
</blockquote>
-- [http://www.bay12forums.com/smf/index.php?topic=59026.msg4768489#msg4768489 original post]

==== PyLNP: The modern cross platform launcher ====

In mid-2014 Pidgeot released the [http://www.bay12forums.com/smf/index.php?topic=140808 PyLNP launcher] built in Python and compatible with all platforms. As of 2017 the PyLNP is the core launcher of all lazy newb / starter packs available. A number of improvements to the feature set have been made since the original windows-only launcher by LucasUP, including raw merging of graphics to perserve settings, mod management, color schemes, and managing multiple installations of ''Dwarf Fortress''. There are [http://pylnp.birdiesoft.dk/docs/dev/#id5 even more] not mentioned here.

All modern packs since 2014 use the PyLNP launcher. Note that "PyLNP" and "LNP" are not interchangeable - the former refers to the launcher itself, while the latter refers to a pack as a whole.

PyLNP started as a port of LucasUP and tolyK’s Lazy Newb Pack Launcher to Python, with the goal of making a launcher available on all the platforms supported by ''Dwarf Fortress''. Its biggest innovation is the [http://pylnp.birdiesoft.dk/docs/dev/content.html PyLNP content format], a standard for defining manifests for graphics, tilesets, keybinds, utilities, etc that allows a modular and custom pack to be built.

=== Lazy? Newb? Starter Pack? ===

The original pack by LucasUP was named the Lazy Newb Pack, and LucasUP themselves explained the name as "This package is for ''Newbs'' and those too ''Lazy'' to put everything together every new version" (emphasis original). Most derivative packs over the years have retained that name more out of brand recognition and as homage to LucasUP's first attempts.

In November 2013 PeridexisErrant, the maintainer of the current pack for the Windows platform, renamed his pack from "PeridexisErrant's LNP" to "PeridexisErrant's Starter Pack". He [https://www.reddit.com/r/dwarffortress/comments/1qt7c1/df_starter_pack_updated_classic_lazy_newb_pack/cdgpqxq/ has said] the primary reason for the renaming was to distinguish the old legacy LNP from his own pack when providing support to players, as often players would have a problem with the pack and ask PeridexisErrant for help only for him to discover they were using an older version of the pack that he didn't publish nor maintain. He changed the name before the [[DF2014:Release_information|big 2014 release]] in order to help steer new players towards his new maintained starter pack, and prevent them from finding and using old unsupported versions of the LNP.

The maintainers of the different Mac OSX packs have used different names over the years including MacNewbie, and Lazy Mac Pack. The Linux maintainers have remained with the original LNP moniker.

=== Other historical packs ===

Early on, while there were releases of ''Dwarf Fortress'' for Mac and Linux, there were no Lazy Newb Packs offered. The very first batch-script based version of LucasUP's LNP inadvertently worked on Linux via wine, but after the switch to the GUI launcher built with .NET, support for Linux was lost.

The general availability of GUI based launchers (and the packs built around) them for Mac and Linux didn't come about until Dricus' java-based launcher project [http://www.bay12forums.com/smf/index.php?topic=130236.msg4521675#msg4521675 in August 2013].

==== Mac OS X ====
In April 2012, [http://www.bay12forums.com/smf/index.php?action=profile;u=69756 iXen] released [http://www.bay12forums.com/smf/index.php?topic=106790.0 the MacNewbie Pack] as an alternative to the Windows LNP. It was for version release 0.34.07 of ''Dwarf Fortress''. The pack was updated for several months until its final release, v0.6 Cyan, in May. The pack was notable as it included the first GUI launcher for Mac OS. It was built with Apple's Cocoa technology and included special keybindings to make gameplay easier on Apple Wireless & MacBook Keyboards.

<gallery widths=200px>
File:Macnewbie2.png|Screenshot of the MacNewbie pack v0.6 Cyan for ''Dwarf Fortress'' v0.34.11 by iXen.
File:Macnewbie1.png|Screenshot of the MacNewbie pack v0.6 Cyan for ''Dwarf Fortress'' v0.34.11 by iXen.
</gallery>

[http://www.bay12forums.com/smf/index.php?action=profile;u=94479 Fricy] released [http://www.bay12forums.com/smf/index.php?topic=128960 his spiritual successor] to the MacNewbie pack on July 10, 2014 for ''Dwarf Fortress'' v0.40.01. It was based on Dricus' cross platform java launcher has 26 releases from July 2014 until November 28, 2015. It was last updated in November 2015 in January ''Dwarf Fortress'' v0.42.04.

==== Linux ====

The [http://www.bay12forums.com/smf/index.php?topic=130792 Lazy Newb Pack Installer for Linux] created by Andrewd18 in September 2013, was a Linux installer shell script that installed the ''Dwarf Fortress'' Lazy Newb Pack. It downloaded and built a DF installation from available source code and binaries, and also checked for the dependencies required by 64-bit systems. The home of this pack was [https://github.com/andrewd18/df-lnp-installer on Github]. It was last updated on June 2014 for ''Dwarf Fortress'' v0.34.11.

[http://www.bay12forums.com/smf/index.php?topic=140966 Beautato's Linux Lazy Newb Pack] released in July 2014 was a more traditional package of compiled utilities that was previously maintained and tested on Ubuntu. It was last updated in March 2015 for ''Dwarf Fortress'' v0.40.24.

In March 2017 [http://www.bay12forums.com/smf/index.php?action=profile;u=114577 Enay] took up maintainership of the LNP for Linux calling it [http://www.bay12forums.com/smf/index.php?topic=163211.0 LinuxLNP] and released only for 64-bit systems.

The LinuxDwarfPack provides packages for Debian/Ubuntu, Arch and RedHat systems, as well as an AppImage and a regular tar.gz package. Releases and nightly builds may be downloaded on the [https://github.com/McArcady/lnp-forge/releases Github page of lnp-forge].

== The Making of a Pack ==

There are many people involved in the making of a LNP/Starter pack for ''Dwarf Fortress'', starting from Tarn and Zach releasing DF, to the many tilesets and graphics creators, the creators of the utilities (e.g, Soundsense, Dwarf Therapist), the reverse engineering work down by the [[DFHack]] folks, to the many more who contribute on the forums, help manage bug reports, create and test mods, etc.

Creating a pack is a process of curating a set of tilesets, graphics, and utilities and bundling them together with a launcher as well as the latest ''Dwarf Fortress'' release, then, optionally, making this bundle available for download

Over the years the process of making a pack has become more formalized and automated, and a community has formed to make the process easier and provide continuity when someone inevitably retires.

As of 2017, pack maintenance and creation is centered around the following projects:

* The [https://github.com/Pidgeot/python-lnp PyLNP launcher] is maintained by Pidgeot and is available on Github
* The [https://github.com/Lazy-Newb-Pack LazyNewbPack organization on github] provides a home for shared resources and code
* The [https://github.com/DFgraphics/DFgraphics DFgraphics github repository] is a shared home for graphics and tilesets to ease routine maintenance
* The [https://github.com/PeridexisErrant/starter-pack starter-pack builder] by PeridexisErrant that helps build a pack from scratch
* The [https://github.com/McArcady/lnp-forge lnp-forge project] is a pack builder targeting Linux and macOS
* The [https://github.com/jipumarino/dfdl dfdl project] is a pack builder for macOS

{{Category|Utilities}}
[[ru:Utility:Lazy Newb Pack]][[zh:Lazy Newb Pack]]

Biome token

2022-12-02T01:12:27Z

Xjtu-blacksmith: ILL

{{Quality|Superior|21:32, 20 September 2016 (UTC)}}
{{av}}
{{Modding}}

'''Biome tokens''' are used to indicate [[biome]]s for [[creature]]s, [[plant]]s and [[civilisation|entities]].

All objects that use biome tokens can take multiple entries, so they can be found in many different locations.

==Individual Biomes==
{| {{prettytable}}
|- bgcolor="#ddd"
! ID !! Token !! Description
|-
| 0 || {{text anchor|MOUNTAIN}} or {{text anchor|MOUNTAINS}} || Mountain
|-
| 1 || {{text anchor|GLACIER}} || Glacier
|-
| 2 || {{text anchor|TUNDRA}} || Tundra
|-
| 3 || {{text anchor|SWAMP_TEMPERATE_FRESHWATER}} || Temperate Freshwater Swamp
|-
| 4 || {{text anchor|SWAMP_TEMPERATE_SALTWATER}} || Temperate Saltwater Swamp
|-
| 5 || {{text anchor|MARSH_TEMPERATE_FRESHWATER}} || Temperate Freshwater Marsh
|-
| 6 || {{text anchor|MARSH_TEMPERATE_SALTWATER}} || Temperate Saltwater Marsh
|-
| 7 || {{text anchor|SWAMP_TROPICAL_FRESHWATER}} || Tropical Freshwater Swamp
|-
| 8 || {{text anchor|SWAMP_TROPICAL_SALTWATER}} || Tropical Saltwater Swamp
|-
| 9 || {{text anchor|SWAMP_MANGROVE}} || Mangrove Swamp
|-
| 10 || {{text anchor|MARSH_TROPICAL_FRESHWATER}} || Tropical Freshwater Marsh
|-
| 11 || {{text anchor|MARSH_TROPICAL_SALTWATER}} || Tropical Saltwater Marsh
|-
| 12 || {{text anchor|FOREST_TAIGA}} or {{text anchor|TAIGA}} || Taiga
|-
| 13 || {{text anchor|FOREST_TEMPERATE_CONIFER}} || Temperate Coniferous Forest
|-
| 14 || {{text anchor|FOREST_TEMPERATE_BROADLEAF}} || Temperate Broadleaf Forest
|-
| 15 || {{text anchor|FOREST_TROPICAL_CONIFER}} || Tropical Coniferous Forest
|-
| 16 || {{text anchor|FOREST_TROPICAL_DRY_BROADLEAF}} || Tropical Dry Broadleaf Forest
|-
| 17 || {{text anchor|FOREST_TROPICAL_MOIST_BROADLEAF}} || Tropical Moist Broadleaf Forest
|-
| 18 || {{text anchor|GRASSLAND_TEMPERATE}} || Temperate Grassland
|-
| 19 || {{text anchor|SAVANNA_TEMPERATE}} || Temperate Savanna
|-
| 20 || {{text anchor|SHRUBLAND_TEMPERATE}} || Temperate Shrubland
|-
| 21 || {{text anchor|GRASSLAND_TROPICAL}} || Tropical Grassland
|-
| 22 || {{text anchor|SAVANNA_TROPICAL}} || Tropical Savanna
|-
| 23 || {{text anchor|SHRUBLAND_TROPICAL}} || Tropical Shrubland
|-
| 24 || {{text anchor|DESERT_BADLAND}} || Badlands
|-
| 25 || {{text anchor|DESERT_ROCK}} || Rocky Wasteland
|-
| 26 || {{text anchor|DESERT_SAND}} || Sand Desert
|-
| 27 || {{text anchor|OCEAN_TROPICAL}} || Tropical Ocean
|-
| 28 || {{text anchor|OCEAN_TEMPERATE}} || Temperate Ocean
|-
| 29 || {{text anchor|OCEAN_ARCTIC}} || Arctic Ocean
|-
| 30 || {{text anchor|POOL_TEMPERATE_FRESHWATER}} || Temperate Freshwater Pool
|-
| 31 || {{text anchor|POOL_TEMPERATE_BRACKISHWATER}} || Temperate Brackish Pool
|-
| 32 || {{text anchor|POOL_TEMPERATE_SALTWATER}} || Temperate Saltwater Pool
|-
| 33 || {{text anchor|POOL_TROPICAL_FRESHWATER}} || Tropical Freshwater Pool
|-
| 34 || {{text anchor|POOL_TROPICAL_BRACKISHWATER}} || Tropical Brackish Pool
|-
| 35 || {{text anchor|POOL_TROPICAL_SALTWATER}} || Tropical Saltwater Pool
|-
| 36 || {{text anchor|LAKE_TEMPERATE_FRESHWATER}} || Temperate Freshwater Lake
|-
| 37 || {{text anchor|LAKE_TEMPERATE_BRACKISHWATER}} || Temperate Brackish Lake
|-
| 38 || {{text anchor|LAKE_TEMPERATE_SALTWATER}} || Temperate Saltwater Lake
|-
| 39 || {{text anchor|LAKE_TROPICAL_FRESHWATER}} || Tropical Freshwater Lake
|-
| 40 || {{text anchor|LAKE_TROPICAL_BRACKISHWATER}} || Tropical Brackish Lake
|-
| 41 || {{text anchor|LAKE_TROPICAL_SALTWATER}} || Tropical Saltwater Lake
|-
| 42 || {{text anchor|RIVER_TEMPERATE_FRESHWATER}} || Temperate Freshwater River
|-
| 43 || {{text anchor|RIVER_TEMPERATE_BRACKISHWATER}} || Temperate Brackish River
|-
| 44 || {{text anchor|RIVER_TEMPERATE_SALTWATER}} || Temperate Saltwater River
|-
| 45 || {{text anchor|RIVER_TROPICAL_FRESHWATER}} || Tropical Freshwater River
|-
| 46 || {{text anchor|RIVER_TROPICAL_BRACKISHWATER}} || Tropical Brackish River
|-
| 47 || {{text anchor|RIVER_TROPICAL_SALTWATER}} || Tropical Saltwater River
|-
| 48 || {{text anchor|SUBTERRANEAN_WATER}} || Underground caverns (in water)
|-
| 49 || {{text anchor|SUBTERRANEAN_CHASM}} || Underground caverns (out of water)
|-
| 50 || {{text anchor|SUBTERRANEAN_LAVA}} || Magma sea
|}

==Biome Sets==
{| {{prettytable}}
|- bgcolor="#ddd"
! Token !! Biomes !! Description
|-
| {{text anchor|ALL_MAIN}} || 0-29, 36-41 || All biomes excluding pools, rivers, and underground features
|-
| {{text anchor|ANY_LAND}} || 0-26 || All main biomes excluding oceans and lakes
|-
| {{text anchor|ANY_OCEAN}} || 27-29 || All ocean biomes
|-
| {{text anchor|ANY_LAKE}} || 36-41 || All lake biomes
|-
| {{text anchor|ANY_TEMPERATE_LAKE}} || 36-38 || All temperate lake biomes
|-
| {{text anchor|ANY_TROPICAL_LAKE}} || 39-41 || All tropical lake biomes
|-
| {{text anchor|ANY_RIVER}} || 42-47 || All river biomes
|-
| {{text anchor|ANY_TEMPERATE_RIVER}} || 42-44 || All temperate river biomes
|-
| {{text anchor|ANY_TROPICAL_RIVER}} || 45-47 || All tropical river biomes
|-
| {{text anchor|ANY_POOL}} || 30-35 || All pool biomes
|-
| {{text anchor|NOT_FREEZING}} || 3-26 || All land biomes excluding Mountain, Glacier, and Tundra
|-
| {{text anchor|ANY_TEMPERATE}} || 3-6, 13-14, 18-20 || All Temperate land biomes - marshes, swamps, forests, grassland, savanna, and shrubland
|-
| {{text anchor|ANY_TROPICAL}} || 7-11, 15-17, 21-23 || All Tropical land biomes - marshes, swamps (including Mangrove), forests, grassland, savanna, and shrubland
|-
| {{text anchor|ANY_FOREST}} || 13-17 || All Forest biomes (excluding Taiga)
|-
| {{text anchor|ANY_SHRUBLAND}} || 20, 23 || Temperate and Tropical Shrubland
|-
| {{text anchor|ANY_GRASSLAND}} || 18, 21 || Temperate and Tropical Grassland
|-
| {{text anchor|ANY_SAVANNA}} || 19, 22 || Temperate and Tropical Savanna
|-
| {{text anchor|ANY_TEMPERATE_FOREST}} || 13-14 || Temperate Coniferous and Broadleaf Forests
|-
| {{text anchor|ANY_TROPICAL_FOREST}} || 15-17 || Tropical Coniferous and Dry/Moist Broadleaf Forests
|-
| {{text anchor|ANY_TEMPERATE_BROADLEAF}} || 3-6, 14, 18-20 || Temperate Broadleaf Forest, Grassland/Savanna/Shrubland, Swamps, and Marshes
|-
| {{text anchor|ANY_TROPICAL_BROADLEAF}} || 7-11, 16-17, 21-23 || Tropical Dry/Moist Broadleaf Forest, Grassland/Savanna/Shrubland, Swamps (including Mangrove), and Marshes
|-
| {{text anchor|ANY_WETLAND}} || 3-11 || All swamps and marshes
|-
| {{text anchor|ANY_TEMPERATE_WETLAND}} || 3-6 || All temperate swamps and marshes
|-
| {{text anchor|ANY_TROPICAL_WETLAND}} || 7-11 || All tropical swamps and marshes
|-
| {{text anchor|ANY_TROPICAL_MARSH}} || 10-11 || All tropical marshes
|-
| {{text anchor|ANY_TEMPERATE_MARSH}} || 5-6 || All temperate marshes
|-
| {{text anchor|ANY_TROPICAL_SWAMP}} || 7-9 || All tropical swamps (including Mangrove)
|-
| {{text anchor|ANY_TEMPERATE_SWAMP}} || 3-4 || All temperate swamps
|-
| {{text anchor|ANY_DESERT}} || 24-26 || Badlands, Rocky Wasteland, and Sand Desert
|}

{{Category|Modding}}
{{Category|Tokens}}
[[ru:Biome token]][[zh:Biome token]]

Mining

2022-12-01T14:38:07Z

Xjtu-blacksmith: /* See also */ ILL

{{Quality|Exceptional|21:32, 24 May 2013 (UTC)}}
{{Labor
| labor = Mining
| skill = * [[Miner]]
| tasks =
* Dig
}}
{{av}}

[[File:mining_anim.gif|thumb|140px|right|A designated area being mined.]][[File:mineral_flowchart.png|thumb|310px|right|Flowchart of all metals and minerals, done by alansai.]]'''Mining''' is an essential part of building a fort in ''Dwarf Fortress''. There are several reasons you might want to mine, such as [[exploratory mining|searching]] for various [[stone|stone types]], [[ore]]s and [[gem]]s, or simply to create the basic tunnels and [[room]]s in your fort. Mining refers to either the [[skill]] that performs mining, the [[labor]] associated with it, or simply the task or job of performing said labor. Military dwarves equipped with picks will use mining as their "[[Combat skill|weapon skill]]."

There are several types of jobs associated with this skill:
* '''Mining''' removes the section of the wall while preserving both the ceiling (which is the floor of the level above) and the floor.
* '''[[Channel]]ing''' removes the section of the wall, the floor, and if possible places a ramp one level below.
* '''[[Ramp]]s''' replaces the section with a ramp, also removing the tile and floor one level above.
* '''[[Stairs]]''' carves out upward and/or downward stairs.

Mining can only be done in pre-existing stone or soil. NOTE: Constructed [[wall]]s, [[stairs]] or [[ramp]]s cannot be mined; these must be removed using the 'Remove Construction' option ({{K|d}}, {{K|n}})

== Making a dwarf a miner ==

# Specify your dwarf to be a miner via {{K|v}}iew, {{K|p}}ref, {{K|l}}abor.
# Select "Mining" using {{K|+}} or {{K|-}}, then press {{K|enter}}.
Dwarves can be miners or woodcutters, but they may not be both at the same time. To start mining, a [[miner]] requires an available [[pick]]. A dwarf's agility and mining skill affect how quickly they mine.

Selecting the mining labor will disable the [[wood cutting]] and [[hunting]] labors, as they all involve the usage of different tools.

== Designating the area to be mined ==

# Press {{K|d}}esignate to bring up the [[Designations Menu]].
# Highlight the requested action by pressing:
#* {{K|d}} for mining
#* {{K|h}} for channeling
#* {{K|r}} for an upward ramp
#* {{K|u}} for stairs towards the upper level
#* {{K|j}} for stairs towards the lower level
#* {{K|i}} for stairs in both directions
# (Optional) Set the priority with {{K|-}} and {{K|+}}. Tiles with first/lowest numbered priority value will be mined first.
# Move the cursor to the starting point, then press {{K|enter}}. You should see a green flashing cross symbol indicating that it's in Selection Mode.
# Move the cursor to another point to define the opposite corners of a rectangle, press {{K|enter}} again. A yellow area should now be highlighted, indicating the area to be mined. The opposite corner can also be placed on a different z-level with {{k|<|>}}, designating areas across z-levels for mining. Tiles can also be designated by using the mouse and left-clicking.

==Understanding digging==
[[Image:DF2014_Terraform.png|thumb|664px|

Side view of various mining tasks.
 
Gray/black areas represent un-mined rock, cyan/black represents mined-out areas. Solid green represents existing floor "tiles", cyan represents mined-out floor tiles. Up stairs, down stairs, and ramps are red, blue, and mustard (yellow) respectively.
 
In each of the 9 "digging" scenarios, the dwarf miner is shown as having completed the command(s) listed in that figure, moving from left to right. Each individual command is separated by a comma ",". (The "x2" notation indicates that the command is completed twice.) The dwarf has completed those commands in the order they are listed. For example, in the bottom right figure: "Down stairs, up/down stairs, up stairs, mine x2" is five separate commands.
]]

Each layer in the three-dimensional ''Dwarf Fortress'' map consists of two parts: a wall-part, and a floor-part. Mining a tunnel removes the wall-part but leaves the floor-part in place. Channeling removes the floor-part as well, leaving open space above, and if a wall-part exists below, it becomes an upward ramp. Digging an upward ramp removes the wall-part of the designated tile and both parts of the tile above it. Up stairs only modify the wall-part of the designated tile (and are unusable without Down stairs in the tile above), the Down stairs designation will remove the wall-part of the tile (if present) and place a stair connection in the floor-part of the designated tile. Up/down stairs modify both parts of the designated tile (but remain unusable until the tile above/below has the proper stair connection).

==Mineral production (profit!)==
When the wall-part is removed from a stone tile, there is a 25% chance that a single [[stone]] (also known as a boulder) will be left behind. Minerals which are found in [[vein]]s have a 33% chance of leaving ore, and minerals found in [[vein|small clusters]] (or individual tiles) have a 100% chance of leaving a stone or rough gem behind. Finally, any "deep" material (i.e. [[adamantine]] or [[slade]]) has a 100% chance of leaving a usable stone (though the latter is normally undiggable). Mining skill only influences the amount of time it takes to mine each tile; it does not affect drop rate.

Carving a channel down or ramp up needs special care to provide the full 25%/33%/100% mineral production: in the case that both the bottom tile (where the new ramp up is) and the top tile (new open-space above the newly carved ramp) are both dug out together as part of the same designation, there is only a single chance of mineral production, even though two tiles had their wall-part removed, effectively halving the mineral production chance to 12.5%/16.5%/50% in that case. But if special care is taken to ensure the top open-space tile is dug out first before carving the ramp below it, the full chance from both tiles can be achieved.

The [[mason's workshop]] can create four [[block]]s from each boulder, so on average you can create one stone block for each tile of stone mined. Each ore stone also produces 4 metal bars at a [[smelter]], so, on average, you will produce 1⅓ bars of the basic metal* for every tile of ore mined, or 4/ for small clusters of rare ore.

: (* Two ores, [[tetrahedrite]] or [[galena]], have a chance to produce additional bars of [[silver]] as well as producing the 4 bars of their basic metal ([[copper]] and [[lead]], respectively). As a footnote, while [[iron]] ores produce 4 bars of iron, and that is all the metal required for 1 bar of steel, [[steel]] production additionally consumes 1 [[flux]] stone and 1 bar of [[fuel]] per single bar of steel produced.)

When tunnels are dug in [[soil]], nothing is left from the material, there is no soil equivalent of a "[[stone]]" to be further used. The floor-part will remain (if it wasn't channeled), and is suitable for [[farming]], or, if the right kind of soil, for [[sand]] or [[clay]] collection.

After pressing {{K|d}}, set the designation type with {{K|a}} to switch between designating all materials, designating just gems, designating just gems and ores, or designating ore/gem clusters or veins to be mined automatically. Switching the designation type to automining will allow you to quickly assign mining tasks to entire veins.

==Training mining==
Dwarves gain mining experience for each tile mined, be it stone, ore, gem, or soil. Soil is mined extremely quickly and is one of the fastest ways to train miners. Since the skill of mining also is used in combat, a dwarf with mining enabled that is carrying a pick will increase their mining skill through combat drills. This process is much faster than learning by digging through stone, but not nearly as fast as learning by digging through soil.

The fastest way to train mining is to first dig out upstairs, then remove the upstairs. Removing upstairs (even rock ones) is extremely quick and still provides mining experience.

==Mining warm and damp stone==
[[File:Miner krugg.jpg|thumb|strike the earth safely]]

When designating any digging operation, warm and damp tiles will flash, indicating magma or water in adjacent tiles. Miners can dig these safely, provided there is an escape route. (''"Safely"'' here implies only the short term survival of the digging dwarf, your fortress may well be flooded as a result, even many levels above the digging level, ''eventually'' killing your dwarf.)

Channeling and ramping designations involve two operations, and your dwarf will be submerged in the fluid when done. Unskilled swimmers can reach an exit ramp out of water if near enough, but magma will certainly cost your miner's life (the flow from either can knock dwarves off ledges, or, naturally, [[flood]] the fortress.)

Wall tiles ''above'' magma will flash 'warm', and designations will be cancelled even if an entirely safe tunnel is being dug. This is rather annoying when carving out rooms above the magma sea, although there is a way around it. Designating a channel two levels above the magma will mine out the warm wall immediately above the magma, and the designation won't be cancelled because it's not in the area of the warm stone.

==How to cancel a mining operation==
If you placed a designated area for mining but want to cancel the mining (for example if you approached [[Main:Digging designation canceled|damp stone]]) simply go to Designations {{K|d}} and select Remove Designation {{K|x}}. Then select the starting point of the area you want to cancel with {{K|enter}}, move to the ending point and confirm again with {{K|enter}}.

== Rampless channels ==
To create a channel with no ramps, you have to mine out the area underneath the channel first, or manually designate the ramps created for removal afterwards {{K|d}} -> {{K|z}}. If you wish for these channels to be completely inaccessible from the outside, channel out the access-point (downward staircase). Another (more complicated) way of removing any access to the moat is to replace the dug out ramps with constructed ones and creating a cave-in with constructed floors. Rampless channels are an effective substitute for walls against melee enemies that cannot fly, and they can be dug out far faster than a wall can be built. However, channels offer no defense against archers or dragonbreath.

When digging ramps upwards, watch out for loose stone or other items that might be on the floor above, as falling objects can injure the unfortunate miner.

== See also ==
* [[Map tile]]s – Different types of walled, floor and open spaces.
* [[Caverns]] – Large underground tunnel systems.
* [[Exploratory mining]] – Mining focused on finding valuable [[stone]].
* [[Soil]] – A list of soil types.
* [[Stone]] – A list of different types of stones and ores left behind from mining.
* [[Smoothing]] – Increase fortress value and dwarf happiness by improving the quality of your rough-stone mineshafts.

{{Translation| dwarven = avuz | elvish = cèthutha | goblin = ngogngo | human = bora}}

{{labors}}
[[zh:Mining]]

Installation

2022-12-01T06:25:33Z

Xjtu-blacksmith: ILL

{{Quality|Exceptional|12:06, 26 January 2015 (UTC)}}
{{av}}
{{TOC right}}
In order to install [[Dwarf Fortress]], simply download the latest version, extract its contents, and play.
{{quick download|{{current/version/ns}}}}

= Download =

''Dwarf Fortress Classic'' is freely available directly from the developers, Bay 12 Games, at http://www.bay12games.com/dwarves/ . Simply find the version that matches your operating system and click the link. You will be prompted to save a zip file, do so and follow the installation instructions bellow.
: The three downloads linked at the top of the main page are 64-bit versions of DF for Windows, macOS, and Linux. "All versions" links to a page with additional choices, including 32-bit builds for all platforms, "small" builds for Windows (which lack sound files), and "legacy" builds for Windows. Generally, the SDL builds for Windows should be preferred, although the Legacy builds may be necessary on some older computers.

''Dwarf Fortress premium'' is slated to be released on the [https://store.steampowered.com/app/975370/Dwarf_Fortress/ Steam] and [https://kitfoxgames.itch.io/dwarf-fortress itch.io] platforms on December 6th, 2022. These paid versions of the game will include an all-new graphical [[tileset]] and new music tracks. Additionally, the Steam version will include Steam Workshop integration for [[mod]]ding. Most other features will be shared with ''Dwarf Fortress Classic'' (which will remain available for free).

== Third-Party Packages ==

{{main|Utility:Lazy Newb Pack}}

There are several packages which bundle the game with several utilities and graphics sets, usually configurable with an included launcher. These are listed on the [[Utility:Lazy Newb Pack|Lazy Newb Pack]] page.

The ''Dwarf Fortress'' community often creates custom [[Graphics set repository|graphics sets]], [[Tileset repository|tilesets]] and [[Color_scheme#Custom_color_schemes|color schemes]]. They're like graphical mods that make DF look prettier or just different. A lot of people pack the game folder with the tileset installed and everything already set up, so all you have to do is extract and play. Among the most popular of these are [http://www.bay12forums.com/smf/index.php?topic=53180.0 Ironhand's Graphics Set] and [http://www.bay12forums.com/smf/index.php?topic=57557.0 Phoebus' Graphic Set]. Most notable graphics sets are included in the packs mentioned above.

= Installation =
:''Also see: [[System requirements]]''

== Windows ==

There is no installer for the game - simply extract the archive contents to a folder of your choice (we'll refer to it as the "game folder"), and then run the <code>Dwarf Fortress.exe</code> from within that folder to start the game.

Make sure to actually ''extract'' the archive; do not just open the archive and run the game from the window that appears. If you do this, then it may appear to work, but your save game data will get discarded - the cause of many "my saved games keep getting deleted" complaints. The game also needs to be able to write to its own folder, so do '''not''' install it in C:\Program Files if you are running Windows Vista or later. (However, this rather assumes that one actually ''has'' an archive extractor to begin with, perhaps preinstalled: [https://www.7-zip.org/ example remedy for that issue])

If you have an error stating that MSVCP140.dll is missing, it can be obtained by downloading [https://www.microsoft.com/en-us/download/details.aspx?id=48145 Visual C++ Redistributable for Visual Studio 2015]. When prompted choose the x64 version for 64-bit DF, or the x86 version for 32-bit DF.

If Windows is set to scale the display, you may need to disable that for DF. Right-click the ''Dwarf Fortress.exe'' icon, select '''Properties''', select the '''Compatibility''' tab, and then activate the '''Disable display scaling on high DPI settings''' (or '''Override high DPI scaling behavior, scaling performed by: Application''') check box.[https://support.microsoft.com/en-us/help/3025083/windows-scaling-issues-for-high-dpi-devices]

== Mac ==

The Mac version is not an application bundle. Like the Windows version, it consists of a folder containing the application and data files; there is no installer. The entire folder can be dragged into the Applications folder or placed elsewhere. As with the Windows version, the game must be able to write to its own folder.

To start the game, execute the launch script "df". Launching "dwarfort.exe" by itself will ''not'' work (since the "df" script sets up [[wikipedia:environment variables|environment variables]] pointing to DF's libraries).

There are alternative installation options, such as [[Utility:Lazy newb pack|pre-packaged bundles]] and [https://github.com/Bachsau/DF-Mac-Launcher this third-party app launcher], that may make the game easier to start and fix some of the issues listed below.

=== Fixes for common issues ===

Changing the ``PRINT_MODE`` setting in data/init/[[init.txt]] from ``2D`` to ``STANDARD`` is necessary on some systems, particularly macOS 11+ (see below) and machines with Retina displays {{bug|6031}}. Doing this on any macOS system can improve performance significantly {{bug|10052}}. Other values for this setting, like ``FRAME_BUFFER``, may also help.

On macOS 10.15 (Catalina) and above, if you encounter gatekeeper security-related warnings that prevent DF from starting, one solution (from [https://github.com/DFHack/dfhack/issues/1465 here]) is to run the following command from the terminal in the folder containing <code>dwarfort.exe</code>:
* <code>find . -print0 | xargs -0 xattr -d com.apple.quarantine</code>

On macOS 11 (Big Sur) and above, if you see a blank white window when starting the game, you will need to change ``[PRINT_MODE:2D]`` to ``[PRINT_MODE:STANDARD]`` in [[init.txt]]. {{bug|11680}}

On case-sensitive filesystems, a freshly-installed version of the game will not launch. {{bug|11136}}
* Rename "libs/SDL_ttf.framework/Versions/A/Frameworks/FreeType.framework" to "libs/SDL_ttf.framework/Versions/A/Frameworks/freetype.framework" to fix this.

If you are using Parallels Desktop, you might need to change the file association for ``*.exe`` files to prevent the script from opening Parallels automatically. To do this:
* Right click ``dwarfort.exe`` then click "Get Info"
* Then click on "Open with:", select "Other..."
* Then and select "Finder"
* Change "Enable: Recommended Applications" to "Enabled: All Applications"
* Select "Finder" and then click "Add"

== Linux ==

You may want to check if the package manager for the Linux distribution you are using has a ''Dwarf Fortress'' package. A package will get the correct build of DF for your system, handle all the dependencies and configuration, make any necessary system-specific fixes, probably add an entry to the system application launcher or menu, and handle updates. Note that in some cases, these packages can lag behind official DF releases, and they typically only support a single system-wide installation of DF. If you want a version of DF newer than what your package manager provides, or if you want a portable installation, follow the instructions in the rest of this section instead.

As of 0.43.05, both 64-bit and 32-bit compiled builds of ''Dwarf Fortress'' are available for Linux. Note, to get the 32-bit edition, click the All Versions button on the ''Dwarf Fortress'' download page. Older 32-bit only versions can possibly run on a 64-bit system if the system has the required (32-bit) shared libraries, see below.

''Dwarf Fortress'' for Linux is expected to be run from a terminal (command-line) interface, and so the instructions here will assume you know how to log in and get to a command prompt. By default, however, ''Dwarf Fortress'' is a graphical desktop program (an X client), so you should be in a terminal emulator (inside an X session) before starting the game. (See [[Installation#TEXT mode]] for an alternative.) ''Dwarf Fortress'' will create a new window outside of the terminal window by default, so don't worry about the size of the terminal.

When you installed Linux, you chose either a 32-bit (i386, x86) or 64-bit (amd64, x86_64) architecture. Some systems are able to run programs for either, but it is best to use a version of DF compiled for the same architecture. If you've forgotten which one you have, you can check by running the command <code>uname -m</code> in a terminal. A result of <code>x86_64</code> and <code>i686</code> would indicate 64-bit or 32-bit respectively.

'''Downloading''': Either download it from the [http://www.bay12games.com/dwarves/ Dwarf Fortress Homepage] with a web browser, or with one of these terminal commands, replacing "XX_YY" with the numbers in the desired ''Dwarf Fortress'' file version, found on the [http://www.bay12games.com/dwarves/ site]:
wget http://www.bay12games.com/dwarves/df_XX_YY_linux.tar.bz2
or, for the 32-bit version:
wget http://www.bay12games.com/dwarves/df_XX_YY_linux32.tar.bz2

'''Unpacking''': ''Dwarf Fortress'' is shipped as a (bzip2) compressed tar archive. It will extract into a new directory called '''df_linux'''. So, <code>cd</code> to wherever you want the game to be unpacked, perhaps <code>~/games</code>, and then run
tar -xjf /path/to/df_XX_YY_linux.tar.bz2
where /path/to/df_XX_YY_linux.tar.bz2 is the path and filename of the actual file you downloaded.

(note: <code>tar -xjvf ./df_XX_YY_linux.tar.bz2</code> may be needed in some cases. [what cases? all this does is add verbosity and assume the file is in the current dir])

'''Running''': First, change to the new directory
cd df_linux
then execute the launcher script.
./df

Now you need to ensure that the required dependencies are installed. If you try to run the game and get errors about missing SDL_image libraries (etc.) then you need to install them. Use your distribution's package manager for this - details will be extremely distribution-specific. Specific installation commands for some distributions are in the sections below. You don't need the development versions of the packages with the headers (although that won't hurt) - you just need the runtime versions, with the actual shared libraries.

If you see any errors related to libstdc++ when starting DF (for example, "version `CXXABI_1.3.8' not found"), try removing libstdc++.so.6 and libgcc_s.so.1 from the "libs" folder. This will cause DF to use the system version of these libraries, which are more up-to-date on many modern systems than the libraries that DF includes.

Since ''Dwarf Fortress'' 0.43.05 and later are compiled for both architectures, running natively shouldn't be an issue. However if you're wanting to run an older version of ''Dwarf Fortress'' on a 64-bit system, things get a bit trickier. Since older DF is only a 32-bit application, it will need 32-bit versions of the shared libraries. Some Linux distributions provide these in one or more packages that you can download. For example, in Debian, you'll need to enable the 32bit architecture in your package manager and install the relevant 32-bit libraries like libSDL. If your distribution does not include these, then you may have to supply them manually. Though, at that point it may just be easier to run the old windows version of DF in Wine.

=== Debian-based ===

Installing the dependencies for ''Dwarf Fortress'' is simple, but varies slightly depending on whether you're running a 32-bit OS, a 64-bit OS, or a 32-bit version of ''Dwarf Fortress'' on a 64-bit OS.

==== 64-bit (recent version of ''Dwarf Fortress'', most modern machines) ====

===== Install dependencies =====

$ sudo apt install libsdl1.2debian libsdl-image1.2 libsdl-ttf2.0-0 libgtk2.0-0 libopenal1 libsndfile1 libncursesw5

This will install the SDL image and font libraries necessary, as well as libopenal and libsndfile, which are needed to get the sound working. It will also install libncursesw5, which is needed if you want to run ''Dwarf Fortress'' in ''TEXT'' mode.

===== Fix sound issues =====

In some old versions, ''Dwarf Fortress'' does not quite look in the correct place for the sound libraries it needs to play the wonderful music. This is easily fixed.

Switch to the ''Dwarf Fortress'' folder and add some symlinks to the correct location:

$ cd ~/df_linux # or other location, depending on where you installed ''Dwarf Fortress''
$ ln -s /usr/lib/x86_64-linux-gnu/libopenal.so.1 libs/libopenal.so
$ ln -s /usr/lib/x86_64-linux-gnu/libsndfile.so.1 libs/libsndfile.so

Sometimes OpenAL uses PulseAudio instead of ALSA as the output device breaking the sound.

$ sudo echo "drivers = alsa," > .alsoftrc

==== Running 32-bit ''Dwarf Fortress'' on 64-bit Debian ====

===== Install dependencies =====

If you're trying to run a version of ''Dwarf Fortress'' older than 0.43.05, you'll need to install the 32-bit versions of the libraries. You can do this with:

$ sudo dpkg --add-architecture i386
$ sudo apt-get update
$ sudo apt-get install libsdl1.2debian:i386 libsdl-image1.2:i386 libsdl-ttf2.0-0:i386 libgtk2.0-0:i386 libopenal1:i386 libsndfile1:i386 libncursesw5:i386

===== Fix sound issues =====

Almost the same as above, but the libraries will be in a different location as you're looking for the 32-bit versions:

$ cd ~/df_linux # or other location, depending on where you installed ''Dwarf Fortress''
$ ln -s /usr/lib/i386-linux-gnu/libopenal.so.1 libs/libopenal.so
$ ln -s /usr/lib/i386-linux-gnu/libsndfile.so.1 libs/libsndfile.so

Just as above sometimes OpenAL uses PulseAudio instead of ALSA as the output device breaking the sound.

$ sudo echo "drivers = alsa," > .alsoftrc

==== 32-bit ====

===== Install dependencies =====

$ sudo apt-get install libsdl1.2debian libsdl-image1.2 libsdl-ttf2.0-0 libopenal1 libsndfile1 libncursesw5

As above, this will install the SDL image and font libraries, sound libraries, and text libraries.

===== Fix sound issues =====

Switch to the ''Dwarf Fortress'' folder and add some symlinks to the correct location:

$ cd ~/df_linux # or other location, depending on where you installed ''Dwarf Fortress''
$ ln -s /usr/lib/libopenal.so.1 libs/libopenal.so
$ ln -s /usr/lib/libsndfile.so.1 libs/libsndfile.so

==== Standard package ====

''Dwarf Fortress'' is also available as a package in the (non-free) Debian repositories. You can install it (with all dependencies) with a simple

$ sudo apt-get install dwarf-fortress

=== Fedora ===

''Dwarf Fortress'' has been packaged in [https://rpmfusion.org/ RPM Fusion Nonfree], using a similar method as it is done in Arch Linux (see below). After [https://rpmfusion.org/Configuration installing RPM Fusion] you can simply run the following commands to install and run ''Dwarf Fortress'', which will pull in all the required dependencies:

$ sudo dnf install dwarffortress
$ dwarffortress

Some other tools are provided by the same packager in the [https://mars.arosser.com/fedora/dwarffortress/dwarffortress.repo "Dwarf Fortress for Fedora"] repository. For more information please [http://www.bay12forums.com/smf/index.php?topic=158289.msg7009116#msg7009116 see this forum thread].

If you want to install 64-bit ''Dwarf Fortress'' manually, you can run the following:

$ sudo dnf install SDL SDL_image SDL_ttf gtk2-devel openal-soft alsa-lib alsa-plugins-pulseaudio mesa-dri-drivers

On 64-bit Fedora installations, to install 32-bit ''Dwarf Fortress'' you can install 32-bit libraries by appending ".i686" to the package name:

$ sudo dnf install SDL.i686 SDL_image.i686 SDL_ttf.i686 gtk2-devel.i686 openal-soft.i686 alsa-lib.i686 alsa-plugins-pulseaudio.i686 mesa-dri-drivers.i686

Fedora installs all 32-bit libraries to /usr/lib and 64-bit libraries to /usr/lib64 (with /lib and /lib64 being links to these two directories), so if you need to install stuff manually, look in there.

=== Arch Linux ===
A 64-bit ''Dwarf Fortress'' package is available in the [https://wiki.archlinux.org/index.php/Official_repositories#community community repository]. There are also [https://aur.archlinux.org/packages/?O=0&K=dwarffortress other packages] available in the Arch User Repository ([https://wiki.archlinux.org/index.php/Arch_User_Repository AUR]).

==== Official package installation ====
Install the official package like any other
# pacman -Syu dwarffortress
Any required dependencies will be installed, too.

You can then launch ''Dwarf Fortress'' by running 'dwarffortress' in your terminal emulator. The package also includes a .desktop file so the game should appear in whatever application launcher or menu you might use.

The first time a user launches the game, the directory .dwarffortress will be created in that user's home directory. Game settings and files can be changed there. Note that some of the directories in there are links to common directories and changes to them will effect all users. Also, any changes to common files should be backed up since they will be overwritten when the package updates. You can find the locations of files installed by the package with the command
$ pacman -Ql dwarffortress

If you use tools like dfhack you might want to [https://wiki.archlinux.org/index.php/Pacman#Skip_package_from_being_upgraded configure pacman to not update] ''Dwarf Fortress'' until the tools are updated.

==== AUR package installation ====
Install an AUR package [https://wiki.archlinux.org/index.php/Arch_User_Repository#Installing_packages manually] or using an [https://wiki.archlinux.org/index.php/AUR_helpers AUR helper]. The different AUR packages may or may not install the game similarly to the official package - use the previous pacman command to check game file locations.

==== Manual or multiple installations ====
You can also manually install ''Dwarf Fortress'' in case you want to try other versions or with and without mods. Just follow the generic Linux instructions above with a different directory for each install. If you've installed one of the above packages, all the dependencies should already be installed, except maybe GTK2. The package in the official repositories patches ``libgraphics.so`` to remove the GTK2 dependency. If you get an error that ``libgtk-x11-2.0.so.0`` cannot be opened, you can either use the ``libgraphics.so`` from the official package, by copying it to the ``libs`` folder in the new install or linking to it from there, or install GTK2.

To launch this version: in a terminal emulator, ``cd`` to that directory, and run ``./df``. If you get a permission error, you may need to mark the script and executable as being executable with:
$ chmod u+x df libs/Dwarf_Fortress
Once you get an install working you can create a [https://wiki.archlinux.org/index.php/Desktop_entries custom .desktop file] to launch it.

If you want to install a 32-bit version of ''Dwarf Fortress'' you will have to enable the [https://wiki.archlinux.org/index.php/Official_repositories#multilib multilib repository], install the 32-bit system libraries, and install the 32-bit game dependencies manually (check the Arch wiki for more information).

=== CentOS 7 ===

''Dwarf Fortress'' is now 64-bit, so simply run:

sudo yum install SDL SDL_image SDL_ttf openal

Note that CentOS 7 ships with glibc 2.17, but ''Dwarf Fortress'' by default would like 2.18. [http://www.bay12games.com/dwarves/mantisbt/view.php?id=9893 This bug] has a fix, simply copy the [http://pastebin.com/jX4Wf062 Pastebin script], then move the libraries into a new folder.

cd df_linux
curl -L http://pastebin.com/raw/jX4Wf062 > df
mkdir c_libs
mv libs/libgcc_s.so.1 libs/libstdc++.so.6 c_libs/
chmod a+x df

Then run it!
./df

=== Gentoo ===

There is a ''Dwarf Fortress'' [https://packages.gentoo.org/package/games-roguelike/dwarf-fortress ebuild] in the main Gentoo's portage tree compatible with the new multilib support.

# emerge -av games-roguelike/dwarf-fortress

=== Solus ===

Download ''Dwarf Fortress'' from the Bay 12 Games website. If you encounter the following error upon launch:

./libs/Dwarf_Fortress: error while loading shared libraries: libSDL_ttf-2.0.so.0: cannot open shared object file: No such file or directory

then simply run the following command to install the missing libraries:

sudo eopkg install sdl-ttf

If you are running a 32bit version of ''Dwarf Fortress'', simply replace <code>sdl-ttf</code> with <code>sdl-ttf-32bit</code> in the above command. You're all set!

=== OpenSuse Tumbleweed ===
These instructions should work for OpenSuse Leap as well, they just haven't been tested yet.
==== Dependencies ====
$ sudo zypper in libGLU1 libSDL_image-1_2-0 libSDL_ttf-2_0-0
==== Remove the included c++ library ====
The included library isn't compatible with OpenSuse's <code>libGLU1</code> package
$ cd path/to/df_linux/libs
$ rm libstdc++.so.6

cd back to df_linux/ and run the game!
$ cd ../
$ ./df
=== Wine ===
Downloading the windows version and running it with Wine works fine ([https://appdb.winehq.org/objectManager.php?sClass=version&iId=32503 platinum] on 1.7.47 as of .4x.xx, which means the program runs flawlessly without any initial user configuration). This also avoids any issues with 32-bit versus 64-bit mode.

=== Troubleshooting ===
If you get errors, it is likely that others will have had the same problem; Try searching the bay12games forum with the error message.
==== Sound ====

After installing, DF will run, but will complain that it cannot find the OpenAL library and cannot play sounds, even when OpenAL (i386) has been installed. This is due to a bug/feature in which there is no link from the name of the library that DF is looking for ("libopenal.so") to its implementation ("libopenal.so.1" - technically another link). To fix this, simply provide the necessary links in DF's own ''libs'' directory:

$ cd df_linux/libs
$ ln -s /usr/lib/i386-linux-gnu/libopenal.so.1 ./libopenal.so
$ ln -s /usr/lib/i386-linux-gnu/libsndfile.so.1 ./libsndfile.so

==== TEXT mode ====
In this mode - which can be activated in [[init.txt]] - DF uses a terminal as its display, much like classic roguelikes such as Rogue, Moria, and Nethack originally did. There are some caveats for using this mode.

Some key combinations in the default DF configuration will not work. These can be changed in game by pressing {{k|ESC}} then choosing the Key Bindings option or out of the game by editing the [[interface.txt]] file. This is due to the way terminal emulators handle input, the [https://en.wikipedia.org/wiki/Ncurses ncurses] library, and the way DF interfaces with them.{{bug|5494}} Some examples are the keypad keys with modifiers or {{k|Shift+Enter}}.

DF uses the CP437 [[Character_table|character set]] and TEXT mode translates those to UTF-8. Characters will only be displayed correctly if the font the terminal emulator is using has glyphs for all of the set. A UTF-8 encoded text file to test glyph coverage can be found [http://www.orenwatson.be/cp437.htm here]. Download the text file, view it in the terminal (using more, less, cat, etc.), and check if the font the terminal is using includes all the characters shown on the HTML version. Some terminals may be configured to use a [https://en.wikipedia.org/wiki/Fallback_font fallback font] if the main one lacks a glyph - that may result in different sized glyphs being used.

There is a [http://www.bay12forums.com/smf/index.php?topic=59983.0 utility] to convert a DF [[tileset]] to a TTF file. That thread also has downloads for some already converted sets. This does not work for graphics sets. This is one way to get a square font that includes all the characters. [https://www.kreativekorp.com/software/fonts/ksquare.shtml Kreative Square] is another though it has many more glyphs than are needed.

DF's [[colors.txt]] file will have no effect. However, many terminal emulators have settings to change the colors they display. See the terminal emulator's man page for details. Note that the order of the [[Color#Color_values|colors]] is different - the position of the blues and reds are switched as are the cyans and brown/yellow. So, when copying DF color schemes into terminal emulator settings, be sure to change them to the correct order or you'll get yellow "sky", red water, and blue blood.

Many terminal emulators have a setting to treat bright colored text as bold instead. This will cause dark grey text to be "displayed" as bold, black text - usually on a black background - making it unreadable. See the terminal emulator's man page for an option to disable this behavior. (Note that LXTerminal's disallowbold option does not currently seem to work.)

If the [[intro movie]] is enabled, DF will not use the full terminal size unless it receives a resize event. If the intro movie is disabled, DF will use the full size from the start. Note, however, that some DF screens do not use the full size of the window under any circumstance.

==== Upgrading ====

Since every new version of ''Dwarf Fortress'' unpacks in a directory named '''df_linux''' you have to manage upgrades yourself - or use the [http://dffd.wimbli.com/file.php?id=9639 Linux Updater Script]. As on all systems, you should '''not''' unpack a new version of DF on top of an old version's directory -- this will cause things to break, usually in subtle and mysterious ways. Instead, you should either delete or rename the old '''df_linux''' directory first, before extracting the new version.

==== Manually installing 32-bit libraries ====

If you do need to manually install the libraries, then the first step is to figure out where you will be putting them. Check to see where your other 32-bit libraries are already installed; for example, on Debian, some are in /lib32 and others are in /usr/lib32. Since libSDL is in /usr/lib32 on a Debian system, that's where we'll want to put libSDL_image and libSDL_ttf. On other distributions, the path could be different.

The second step is to get the 32-bit libraries. You can typically do this by downloading them directly from your distribution's 32-bit package repository. Again using Debian as our example, we can perform a search at http://packages.debian.org/ for files containing the word libSDL_image for the Intel x86 architecture. This takes us to [http://packages.debian.org/search?searchon=contents&keywords=libSDL_image&mode=filename&suite=stable&arch=i386 a results page] from which we can proceed to [http://packages.debian.org/squeeze/libsdl-image1.2 the libsdl-image1.2 package page] with a list of download links arranged by architecture. Grab the i386 package from here, and repeat this for the libSDL_ttf package, and whatever other library you are missing. Store these package files somewhere convenient.

The third step is to extract the libraries from the packages and get them in the proper location. You probably ''won't'' be able simply to install the packages using your package manager, because they are for the wrong architecture. Instead, you'll probably have to extract them by hand. The steps for doing this are distribution-specific, so when in doubt consult your distribution's help resources. Here are the steps for a .deb package.

* cd into some temporary working directory such as /tmp
* Extract the files from the .deb archive, which is in ar(1) format:
tar x /path/to/libsdl-image1.2*_i386.deb
: This creates three files: debian-binary, control.tar.gz and data.tar.gz. We only care about data.tar.gz.
* Extract data.tar.gz:
tar xzf data.tar.gz
: This creates a subdirectory named usr with various files inside it. We only care about usr/lib/libSDL_image-1.2.so.0.8.2 (or whatever precise version yours has).
* Move the shared library into place:
sudo mv usr/lib/libSDL_image-1.2.so.* /usr/lib32/
* Create a symlink to it:
cd /usr/lib32
sudo ln -s libSDL_image-1.2.so.0.* libSDL_image-1.2.so.0
cd -

Repeat this for libSDL_ttf and whatever other libraries are required.

'''NOTE''': If you get the error that libsndfile.so is not found, you must use the following:
find */libsndfile.so*
cd to the correct directory, then use ln as shown above.

==== "Not found: /data/art/mouse.png" ====
===== Fix 1: Preload zlib=====
Due to incompatibilities between DF's included zlib and newer versions of zlib, libpng can fail on newer systems. A solution is to add this line to the beginning of <code>/your/path/df_linux/df</code> (or <code>/your/path/df_linux/dfhack</code> if you use [[DFHack]]):
export LD_PRELOAD=/usr/lib/libz.so.1
Note that this path can vary - be sure that it is referring to a '''32-bit''' zlib.
===== Fix 2: Use bmp instead =====
Another solution (if preloading zlib doesn't work) is to force DF to use the BMP versions of image files. You must first edit the ''/data/init/init.txt'' file and change all occurrences of "png" to "bmp". This should solve all the error messages except for one: "''Not found: data/art/mouse.png''" since there is no setting in the init files to change it. The workaround for this is to edit the ''Dwarf_Fortress'' file found in the ''/your/path/df_linux/libs'' folder which contains the setting for the mouse cursor.
If you don't know how to do that, you can try this:
* cd to the ''/df_linux/libs'' folder
* open ''Dwarf_Fortress'' in ''vi'' or any other editor of your choise:
vi ./Dwarf_Fortress
: This opens the file for editing (text mode). If you are not familiar with ''vi'', it would be a good idea to follow these steps exactly and not press any other keys since they all activate specific commands. If you do press a key though, you can press the ''ESC key'' a few times to cancel the command.
* With vi open, write the following string and press ''Enter'':
/mouse
: This will search for all the strings that contain the word "mouse" and place the cursor on the first match. Pressing the ''n key'' will cycle through all the matches.
* Press the ''n'' key until the cursor moves to the desired string, which is "''data/art/mouse.png''". If you accidentally move past the string, you can cycle back through the matched strings using the ''N key'' (shift + n).
* Once you find the right string, you will have to move the cursor over the "p" in "[..]/mouse.png". You do that by pressing the ''l key'' which will move the cursor to the right. There is also the ''h key'' to move the cursor to the left, in case you move past it.
* With the cursor in the right position press the following key sequence:
xxxibmp
: This will replace the ''.png'' extension with the ''.bmp'' one which solves the problem of the missing ''/data/art/mouse.png'' error.
* All there is left to do is to save the modifications to the file and quit ''vi''. For that, press the ''ESC key'' once or twice and then press the following key sequence after which you press ''Enter'':
:wq
: This saves the changes and quits 'vi'

Now the game should work properly. Have fun!

==== libGL error ====

''libGL error: MESA-LOADER: failed to open i965''

''libGL error: failed to load driver: swrast''

This can be caused by incompatible libgcc_s.so.1

===== Fix 1: change print mode =====

* Go to /data/init/init.txt
* Edit PRINT_MODE to be any of the 2D modes or TEXT instead of openGL-based modes like STANDARD, VBO or TWBT.

===== Fix 2: change library =====

* Open df_linux/libs folder
* Rename libgcc_s.so.1 to libgcc_s.so.1.bak so that DF will be unable to find it and will default to system libraries.
* If DF still doesn't launch, find and install suitable libgcc with your package manager.
* If you have multiple libgccs, you may need to make a shortcut like with libopenal and libsndfile above.

==FreeBSD==

Although there is no official version ported to FreeBSD, ''Dwarf Fortress'' can nevertheless be run using either Wine or FreeBSD's compatibility with Linux. There is now an [https://www.freshports.org/games/linux-dwarffortress/ official port] and installing it can be done the following way (with ports):

cd /usr/ports/games/linux-dwarffortress/ && make install clean

or, with pkg:

pkg install linux-dwarffortress

You may also wish to download and run it manually. However, attempting to run the Linux version out of the blue will result in an error about missing library files. Such files must be downloaded from special linux-compatible packages or ports; using your preferred installation method, install the following:

===linux-c6===
sudo pkg install linux-c6-gtk2 linux-c6-sdl linux-c6-sdl_image linux-c6-sdl_ttf linux-c6-libGLU \
linux-c6-openal-soft linux-c6-libsndfile linux-c6-alsa-plugins-oss

===linux-f10===
If you don't have the linux-c6 ports available in your system, you can still run ''Dwarf Fortress'' (albeit without sound) using the following packages:
sudo pkg install linux-f10-alsa-lib linux-f10-atk linux-f10-cairo linux-f10-expat linux-f10-fontconfig \
linux-f10-gtk2 linux-f10-jpeg linux-f10-pango linux-f10-png linux-f10-sdl linux-f10-sdl_image linux-f10-tiff \
linux-f10-xorg-libs linux-sdl_ttf linux_base-f10 linux_dri linux-f10-libGLU
linux_dri might be optional if you have the NVIDIA driver. Note that due to the lack of a linux-f10-libsndfile port, the sound will not work. Requests are being made to [http://lists.freebsd.org/pipermail/freebsd-ports-bugs/2013-January/247698.html port] it, as well as a [https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=178474 DF] port itself.

After you install the required packages, copy (or symlink) DF's own library files to the linux-compatible directory:
cd dwarf_fortress_directory
sudo cp libs/lib* /compat/linux/usr/lib/
Or
cd dwarf_fortress_directory
sudo ln -s libs/lib* /compat/linux/usr/lib/

You can then run DF normally. Although it will likely display a bunch of warnings and errors about fonts, it should work.

If you want to avoid polluting your linux-compatible directory, you can always just set LD_LIBRARY_PATH when running df:
LD_LIBRARY_PATH=libs:$LD_LIBRARY_PATH ./df

== Chrome OS (Crostini) ==

It is possible to add ''Dwarf Fortress'' to Chrome OS using the Linux (Beta), to add Linux to Chrome OS, [https://support.google.com/chromebook/answer/9145439?p=chromebook_linuxapps check here to enable it]
You will need to edit the sources list to include the "non-free" repository, this is done by adding "non-free" to the end of the main sources file found at /etc/apt/sources.list

e.g.
# Generated by distrobuilder
deb https://deb.debian.org/debian buster main non-free
deb https://deb.debian.org/debian-security buster/updates main non-free
Followed by running
sudo apt-get update
Then just follow the Debian instructions above

== Android ==

There is no Android version, but the Windows version can be run on it using ExaGear, Eltech's Windows emulator (which is essentially Wine for Android), as documented [http://www.bay12forums.com/smf/index.php?topic=174983.0 here]. The app isn't free though.

== iOS ==

There is no iOS version, but you may remotely connect to a computer running DF through an app called [https://mifki.com/df/ Dwarf Fortress Remote]. This requires a special version of [[DFHack]] to be run on the target computer which you may download at the same time. It also provides a subscription where you connect to an already set up remote server.

= Documentation =

Fortunately, the documentation on this wiki is very detailed and extensive. You may want to start out with:
* [[Tutorials]]
* [[Quickstart_guide|Fortress Mode Quickstart Guide]]
* [[Adventure mode quick start|Adventure Mode Quickstart Guide]]

Then move on to:
* [[Dwarf fortress mode|Fortress Mode reference]]
* [[Adventure mode|Adventure Mode reference]]
* [[Special:Search|Searching]] the wiki

{{Getting Started}}
[[ru:Installation]][[zh:Installation]]

Plump helmet

2022-12-01T01:13:59Z

Xjtu-blacksmith: ILL

{{Quality|Exceptional}}
{{plantlookup|uses=
* [[Food]]
* [[Alcohol]]
|wiki=no}}
{{av}}
'''Plump helmets''' are the most basic, resilient, and versatile of the six underground [[crop|plant]]s for [[Dwarf|dwarves]] to [[grower|grow]]. They are one of the fastest growing plants and can be [[cooking|cooked]], [[brewing|brewed]] into dwarven wine, and even eaten raw. They require an underground [[farm plot]], which requires [[soil]] or muddy ground. They are the only plant food-item that can be purchased at [[embark]].

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

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

[[Plump helmet man|Plump helmet men]] are humanoid, intelligent versions of these plants.

Some dwarves [[Preferences|like]] plump helmets for their ''rounded tops''.
[[File:plump_helmet_preview.png|thumb|268px|center|There's an immature penis joke in there somewhere, but it'd be too long and hard to find. ''Art by Torgeir Fjereide'']]
{{gamedata}}
{{Plants}}
[[zh:Plump helmet]]

Material

2022-11-30T10:38:23Z

Xjtu-blacksmith: ILL

{{av}}{{Quality|Fine|23:45, 4 February 2013 (UTC)}}{{catbox|DF2014:Materials}}
:''For information on the physical properties of materials, see [[Material science]].

'''Materials''' are the wide array of base resources from which objects can be created. Different materials have different base properties (including [[Value#Material_multipliers|value multipliers]] which can significantly affect the [[value]] of the item - a [[gold]] [[throne]] is worth more than an identical-quality [[lead]] one, for example).

Not every end-product can be made of all materials, and similar materials may have very different properties - for instance, [[obsidian]] is the only [[stone]] that can be used to make stone-based [[weapon]]s, only [[magma-safe]] stones will not melt when immersed in [[magma]], and [[fire imp]] [[leather]] will not burn. While nearly all metals can be made into furniture and crafts, only a select few can normally be made into [[weapon]]s and [[armor]]. These metals are generally called weapon-grade metals. This alone doesn't necessarily give these materials a higher base value, but it may make them worth more to you and your fortress in a practical sense.

Some dwarves have [[preference|preferences]] for one material over another - they receive a happy [[thought]] when working with the material, tend to produce higher-[[quality]] results, and perceive items (or rooms) made of that material as higher-[[quality]], which can also give them more happy [[thought]]s:

{{DFtext|Unib Rulushlikot likes [[rhyolite]], [[silver]], [[amber opal]], [[persimmon]] [[wood]] and [[giant emu]] [[leather]].|2:1|links=1|linkcolor=3:1}}

General groups of materials include, but are not limited to:

:* [[Stone]]
:* [[Wood]]
:* [[Metal]]
:* [[Glass]]
:* [[Leather]]
:* [[Cloth]]
:* [[Bone]]
:* [[Shell]]
:* [[Gem]]
:* [[Wax]]

Certain materials tend to be geared toward making certain items - while stone, wood, metal, and glass can be made into similar furniture, there are some items which are normally restricted to certain materials. For example, [[bed]]s can only be made out of wood, and [[bin]]s and [[bucket]]s cannot be made out of stone. Cloth and leather can both be made into clothing, but leather can also be used to make [[armor]]. Gems are largely for [[decoration|encrusting]] finished items made from other materials. Of over two dozen different [[metal]]s and [[alloy]]s, only a handful are usable to make [[weapon]]s.

In all cases, each group of materials is divided into many possible sub-types of material; there are, for instance, 11 pure [[metal]]s, another 14 [[alloy]]s, scores of different types of [[stone]] and well over 100 different types of [[gem]]s. It is best to look up each individual category, or particular material, to become familiar with its value and what it can and cannot be used for.

'''See Also:'''
:* [[The Non-Dwarf's Guide to Rock]]
:* [[Value#Material multipliers|Value/Material Multipliers]]

{{Template:DF2014 materials}}
{{Category|Materials|*}}
[[ru:Material]][[zh:Material]]

Dwarf

2022-11-30T10:37:43Z

Xjtu-blacksmith: IIL

{{Quality|Masterwork|20:51, 20 September 2016 (UTC)}}
{{Creaturelookup/0
|death=nobutcher
|contrib=no
|wiki=Dwarf (mythology)
}}
{{av}}
{{creaturedesc}}

[[Image:Dwarf.jpg|206px|thumb|This is a masterfully-designed engraving of a Dwarf and a battle axe.]]

'''Dwarves''' (singular, '''Dwarf''') are [[Stupid dwarf trick|"intelligent"]], [[alcohol]]-[[Creature_token#ALCOHOL_DEPENDENT|dependent]], {{Catlink|Humanoids|humanoid}} [[creature]]s that are the featured [[civilization|race]] of [[fortress mode]], as well as being playable in [[adventurer mode]]. They are well known for their stout physique and prominent [[beard]]s (on the males), which begin to grow from birth; dwarves are stronger, shorter, stockier, and hairier than the average [[human]], have a heightened sense of their surroundings and possess perfect darkvision. Dwarves live both in elaborate underground [[fortress]]es carved from the [[mountain|mountainside]] and above-ground [[hillock]]s, are naturally gifted [[miner]]s, [[metalsmith]]s, and [[stone crafter]]s, and value the acquisition of [[wealth]] and [[value|rare]] [[metal]]s above all else.

Dwarven civilizations typically form (mostly) peaceful, trade-based relationships with [[human]]s and [[elves]], but are bitter enemies with [[goblin]]s, and consider [[kobold]]s a petty annoyance. Dwarven babies become [[children]] one year after birth, grow up to become adults at their twelfth birthday, and live to be around 150-170 years of age.

Well-trained dwarves are a menace in combat; they are the only race that can enter a [[martial trance]] when beset by multiple foes, granting them a major combat bonus, and their emphasis on mining and metalworking ensures access to the best [[weapon|arms]] and [[armor]]. They are incapable, however, of riding [[mount]]s, and will always fight on foot. Note, however, that this is only applicable to player controlled dwarves in fortress mode, as they have access to mounts if they're the invading force of a [[siege]].

Dwarves have the unique feature of appearing differently in the default [[tileset]]s in windowed and full-screen mode. In full-screen mode, their tiles will have little beards ({{Dwarf|7:1|15px}}), which are absent if the game is played in windowed mode.

Dwarves speak the [[Main:Dwarven language|dwarven language]].

Some non-dwarves [[Preferences|like]] dwarves for their ''beards''.

== Fortress mode ==
Dwarves are the current default race in fortress mode, as in, the only one that can be played without [[modding]]. As a [[trading]] race, dwarves will send a [[caravan]] every year in [[Calendar|Autumn]]. These merchants will bring back tales of a fortress's wealth and goods, which will attract [[immigration|immigrant]]s, and the [[outpost liaison]] will bring news about the goings on of the world centered mainly on the player's civilization, including results of [[mayor]]al elections, flight of various refugee groups from their forts and hillocks during [[war]]s, and replacement of [[monarch]]s if the previous incumbent dies with or without an heir.

Dwarves may occasionally be [[Strange mood|struck by divine inspiration]] and desire to create a [[legendary artifact]], an item of masterful crafting and great value. A dwarf who is successful in this quest will likely become a [[skill|legendary]] worker in that profession; however, if the appropriate materials are not available, the dwarf will instead go [[insanity|insane]]. Dwarves with the dream of creating a great work of art long for a strange mood to strike them.

Being underground creatures, dwarves are not fond of the sun, and when exposed to it after [[Cave_adaptation|spending long enough in the dark]] they will experience negative thoughts and vomiting, which will be worse and last for longer the longer they have spent underground (or would if it weren't currently bugged{{bug|11901}}).

Dwarves react to stress depending on their [[personality trait]]s; some react with fear or violence unless they've become sufficiently [[discipline]]d (or numbed) to such things, while others will not feel anything unless the stress is particularly personal. When pushed to unhappiness by unfortunate events, dwarves will go into emotional breakdowns depending on their personalities, ranging from [[depression]] to aggressive [[tantrum]]s - it is not uncommon to find tantruming dwarves overturning furniture, injuring others, and generally being rowdy. Paradoxically, they also have a strong sense of [[justice]], and those who damage property or other dwarves may find themselves incarcerated, or -- in extreme cases -- on the receiving end of the [[hammerer]]'s corporal punishment, though unintentionally fatal beatings from the fortress guard are not unusual. While older versions of the game were famed for their "tantrum spirals", where dwarves would enrage each other in a domino effect and destroy the fortress in the process, these are not as common in the current day, though a stressed dwarf is nonetheless a plentiful source of [[fun]].

== Adventurer mode ==
Dwarven fortresses exist in adventurer mode, both in their world-generated and player-made forms. They can be a good source of dwarf-sized [[armor]] (as human armor is too large for dwarves).

Most human weapons must be wielded two-handed by dwarves, due to their size, except, of course, the weapons that dwarves can also make.

== Ethics ==
[[File:Dancing dwarves crayon.jpg|thumb|250px|This is a crayon drawing. All craftsdwarfship is of the highest quality. On the item is an image of dwarves in crayon. The dwarves are laughing. The dwarves are dancing. On the item are signatures of [[Main:ThreeToe|Zach]] and [[Main:Toady One|Tarn Adams]] in crayon.]]

Morally speaking, dwarven [[ethics]] most closely resembles human and elven ethics, agrees somewhat with kobold and [[animal people]] ethics, and disagrees strongly with goblin ethics. Unlike elves, dwarves find the devouring of dead enemies unthinkable, and will not butcher or consume intelligent beings (goblins see this as a personal matter). They are entirely opposed to torture of any sort for any reason, unlike elves, humans, kobolds and animal people (who find certain forms of torture acceptable) and especially goblins, who find all torture acceptable. Dwarves tolerate animal trophies but shun those who keep trophies of sapient beings, and find those who keep trophies of other dwarves appalling. Dwarves find the killing of animals, enemies and plants completely acceptable, unlike elves, kobolds and animal people. An exception to this is the killing of neutral beings, which is sanctioned as long as the killing had been officially ordered. A dwarf found to have participated in assault, theft, trespassing or vandalism will be seriously punished; some crimes such as killing other dwarves, breaking oaths, slavery and treason are punishable by death. On the other hand, lying is considered a personal matter.

Dwarves highly value craftsmanship, and deeply respect law, loyalty, family, friendship, truth, artwork, skill and hard work. They place a certain degree of value on martial prowess, cooperation, fairness, independence, stoicism, commerce, merriment, leisure time and perseverance. They have no respect for nature.

== Community outlook ==
Dwarves have accumulated a reputation among players for being slow-witted, although to be fair, this is more a function of the game itself (and certain consequences thereof) than it is the fault of the dwarves. The instances of dwarven stupidity are numerous; examples include [[dodging]] into thin air (off of cliffs and into [[river]]s), never accounting for [[water]] [[flow]] (and being swept off of [[waterfall]]s to a watery grave several [[z-level]]s below), always taking the easy [[path]]s (even through a pond [[syndrome|poisoned]] with toxic [[forgotten beast]] blood), climbing across tree branches and falling into the lakes or ponds the branches hang over, building [[construction]]s from the wrong side (trapping themselves within), [[channel]]ing the floor one <s>is</s> was standing on, wandering off to do dangerous things ([[web|collecting webs]] when a [[giant cave spider]] is visibly lurking), and generally disregarding dangerous circumstances (carrying back friendly [[corpse]]s even when the goblins that have rendered them horizontal are a mere two feet away).

Dwarves also have the reputation of being incredibly irritable, becoming stressed at the slightest provocation. The problem was compounded by dwarven touchiness in previous versions of the game; they easily became depressed, throwing tantrums that spiraled out of control for what seemed like minor reasons (e.g. a temporary lack of [[wear|unworn]] [[clothing#The_great_sock_obsession|socks]]). This inevitably led to players' emphasis of the "dwarfy": failsafe designs, machinery in place of dwarfpower, fun with [[magma]], seizing control of the environment, killing all the cute fuzzy animals, strip-mining the whole place hollow, etc. It is a great insult to be called an [[elf]], implying that the player is apt to sit around and gaze at trees, living in the world rather than bending it to their will.

In accounts of exploits or [[fun]], the generic name [[main:Urist|Urist]] is often used in place of any specific dwarf name, often because the default dwarf names are complex, random, and hard to remember. Several other nicknames for dwarves also exist; some are less polite than others.

== Mythology ==
In real-life mythology, dwarves are much like humans, but generally prefer to live underground and/or in mountainous areas. In their fortresses they have accumulated treasures of [[gold]], [[silver]], and [[gem|precious stones]], and pass their time fabricating costly weapons and armor. They are famed miners and smiths, although, like humans, they can specialize in any number of trades. Generally shorter than humans, they are on average stockier and hairier, and usually sport full beards. Though slow runners and poor riders, dwarves are excellent warriors and defenders of their strongholds. Dwarves have the ability to forge magical items, which shows off their culture's and species' natural craftsmanship. For instance, dwarven smiths created some of the greatest and most powerful items of mythology, which inspired the in-game [[strange mood]]s and [[legendary artifact]]s.

== Myths concerning dwarves ==
{{D for Dwarf}}

Dwarves, much like the Biblical hero Samson, actually gain their strength from their beards. (Think back to Gimli, of Jackson's LOTR; "NOT THE BEARD"). There is some speculation among philosophers and biologists of other species whether there is a connection between alcohol and the near godlike properties dwarves exhibit, to which most dwarves respond with a roaring cascade of laughter, before bashing the offending creature's head in and chuckling, "''is'' there a connection?", while suddenly deciding to create an artifact due to the unexpected boost in happiness.

This brings us to the question of why dwarves become sad when they see a fellow dwarf killing a creature. In this, most species are only partially correct in the assumption that the dwarf regrets the loss of life. The real reason dwarves become upset, occasionally becoming melancholic and often throwing fits, is due to the regret that '''they''' were not the cause of said loss of life. This is especially true when the creature slain belongs to one of the following categories, in ascending order of amount regretted:
A) "LnT" Large and Threatening
B) "SCnI" Small, Cute and Innocent
C) "FB" Forgotten Beast (titans, demons and other large "fun" included here)
D) "g" Goblins
E) "k" Kobolds
Z) "ë" Elves

{{gamedata}}
{{gamedata|title=Entity ([[civilization]]) Raws|{{raw|DF2014:entity_default.txt|ENTITY|MOUNTAIN}}}}
{{Creatures}}

{{Category|Races}}
{{Category|Humanoids}}
{{Category|Creatures}}
[[zh:Dwarf]]

Quickstart guide

2022-11-29T01:09:42Z

Xjtu-blacksmith: /* Feedback */ ILL for zh

{{Quality|Masterwork|17:56, 5 July 2018 (UTC)}}
{{av}}
:''For installation instructions, see [[Installation]].''
:''This is a quickstart guide for [[dwarf fortress mode]] for those who have never played before and quickly want to jump in head-first.'' ''If you are looking to learn adventure mode instead, see the [[Adventure mode quick start]] guide.''
:''Also see [[Tutorials]] for more detailed tutorials that people have submitted.''
{{TipBox2|float=right|Before you get started...|Always remember that '''losing is [[fun]]!''' Be prepared to lose a few fortresses before you get all the way through this guide – it can be easy to accidentally kill the entire fortress while learning. But remember: losing means that next time, ''[[#Situational Awareness|you'll remember how you lost]].'' In a big way, ''Dwarf Fortress'' uses the principle of learning from one's mistakes.}}

So, you want to play '''Dwarf Fortress''', but you have no idea what to do. That's understandable; in ''Dwarf Fortress'' you can really do anything you like. It is a huge, complex, and totally open-ended game. But in order to do anything, first you need a sustainable fortress. It turns out that this is not as hard as you might think.

As this article doesn't always contain the exact key sequences needed to do everything described, you will likely need to refer to the [[Dwarf fortress mode|Fortress Mode Reference Guide]] and the rest of the wiki while reading this.

[[File:FlowchartDF.png|thumb|446px|right|[[Main:From Caravan to Happy Dwarves|From Caravan to Happy Dwarves]] - This is a flowchart showing approximately what sequence of actions players usually take when starting up a new fort. Feel free to ignore it if you want. It's not necessary to refer to this to understand the rest of the guide, but by the time you finish the guide it will probably all make sense.]]

__TOC__

= Common UI Concepts =

{{TipBox2|float=right|titlebg=#0a0|Keeping Up|While the guide contains many links, you may still need to look something up. Refer to the [[Dwarf fortress mode|Fortress Mode Reference Guide]] or use the wiki [[Special:Search|search]] function. Also, don't hesitate to [[Main:Troubleshooting|ask for help]] if you can't find answers on the wiki.}}

Contrary to what you might be used to, the ''Dwarf Fortress'' interface uses a combination of key presses, instead of clicking through menus with the mouse, so, for example, instead of clicking on the Build menu, then on the Workshop submenu, and finally on the specific workshop, you press {{k|b}}-{{k|w}}-{{k|c}}. All the keys you can use in a menu are shown in green somewhere on the screen. (If you see any displayed in red, those are added through [[Utility:DFHack|DFHack]].)

This is just the Quickstart Guide, so we skip lots of details on the UI. If you're looking for more UI help as you get deeper into your first fortress, you may also want to read this section in the [[Dwarf_fortress_mode#Gameplay_user_interface|Fortress Mode Guide]].
{{KeyConventions}}

== Options menu ==
{{main|Dwarf_fortress_mode#Options_screen|l1=Options screen}}

Most basic game-related tasks (saving, keybindings, sound, etc.) are performed through the options menu, which can be reached with {{k|Esc}} from the main screen. There are usually seven available options:
* '''Return to Game''': Exits the options menu (shortcut {{k|Esc}}).
* '''Save Game''': Saves the game, unloads the fortress, and returns to the main menu. There is no "save and continue" option, but saves can be [[saved game folder|backed up and reloaded]].
* '''Key Bindings''': Allows you to change the keys that trigger nearly any function in the game. This can appear extremely confusing to use, but it is fairly simple to navigate through (as it uses the standard arrow keys, {{k|Esc}} and {{k|Enter}}). Changing keys for menus is probably a bad idea, since this guide assumes the default keybindings — however, it may occasionally be useful to change navigation keybindings on some laptops (for example, changing menus to use {{k|{{=}}}} instead of {{k|+}}).
* '''Export Local Image''': Saves full-size images of your selected fortress levels, world generation parameters, and some limited world information to the main ''Dwarf Fortress'' folder.
* '''Music and Sound''': Controls for volume adjustment.
* '''Retire the Fortress (for the time being)''': {{tc|#d00|Do not select this option unless you know what you are doing!}} It retires the fortress from your control and gives control to the normal world updating process. Not always available, such as during [[siege]]s. You can later reclaim the fortress but it may not be as you left it.
* '''Abandon the Fortress to Ruin''': {{tc|#d00|Do not select this option unless you know what you are doing!}} It will end your fortress permanently and return to the main menu (all progress in your fortress will be lost). Your fort and most items will remain, however, so this can be useful in extreme circumstances (e.g. when you know your fortress is doomed and want to start again) – see [[abandon]] for more information.

Notably lacking is an "exit without save" option. Players who wish to quit and leave their previous save unchanged may manually kill the Dwarf Fortress process using the "die" command in [[Utility:DFHack|DFHack]], the Windows Task Manager (you might then have to end the process dumprep.exe), or the Unix "kill" command (on some systems, {{k|ctrl}}-{{k|\}} in the terminal running DF accomplishes the same thing). '''Do not''' attempt this while saving, as your save folder '''will''' become corrupted. Alternatively, you can make a copy of your region folder in the (DF)/data/save folder (e.g. "regionXX") ''before saving'', save the game normally, remove the "regionXX" folder and rename the copy.

=World Generation=

First, [[World generation|generate a new world]]. ''Dwarf Fortress'' worlds are always procedurally randomly generated - there is no "default" or "standard" world. Luckily, the basic version of this process is simple, and with these suggested settings won't take too long. Wait until the game shows that the world has been generated, in this case at year 125, since stopping history too soon can limit material availability for embark and trade.

{{TipBox2|titlebg=#00a|Starting World|
For your first game, [[World generation|generate a new world]] using the {{DFtext|Create New World!}} option in the main menu with the following options:

* {{DFtext|World Size}} is {{DFtext|Medium|3:1}}

* {{DFtext|History}} is {{DFtext|Short|3:1}}

* {{DFtext|Number of Civilizations}} is {{DFtext|Medium|3:1}}

* {{DFtext|Number of Sites}} is {{DFtext|Medium|3:1}}

* {{DFtext|Number of Beasts}} is {{DFtext|Low|3:1}}

* {{DFtext|Natural Savagery}} is {{DFtext|Very Low|3:1}}

* {{DFtext|Mineral Occurrence}} is {{DFtext|Everywhere|3:1}}

Then hit {{k|y}} to generate the world. Note that you don't need to understand what's happening during world generation at this point, you can inspect the world during embark. At the end of world creation, hit {{k|Enter}} to Accept your newly created world.
}}

= Embark =
{{main|Embark}}

Embarking is the process of choosing a site, outfitting your initial dwarves, and sending them on their way. Select {{DFtext|Start Playing}} from the main menu, then {{DFtext|Dwarf Fortress}}. The game will load and update the world, then show the '''Choose Fortress Location''' screen. There are three maps: Local, Region, and World.
* '''World''' shows the whole world.
* '''Region''' shows all of the region tiles in the part of the world indicated by the cursor on the world map.
* '''Local''' shows all of the local embark tiles in the region tile indicated by the cursor on the region map.
In the local map area is the highlighted embark area that you can move around with {{K|u}} {{K|m}} {{K|k}} {{K|h}} and resize with {{K|U}} {{K|M}} {{K|K}} {{K|H}}. This highlighted square will be your play area after you embark; you cannot directly act or see details [[Civilization_and_World_Info|outside of this area]] during your game. Use {{k|↑}} {{k|↓}} {{k|←}} {{k|→}} to move the region and world cursors around. Hold down {{K|Shift}} while doing this to move more rapidly.

== Choosing a Good Site ==

Choosing a good embark site is crucial for beginners. Highly skilled players can run a fortress on an evil glacier, but for now, stick to friendly environments. Look for features in an embark site that will make your first fort easier to manage.

{{ambox
|type=type
|text=The highlighted embark area may contain '''multiple biomes''', and the game will display {{DFtext|F1F2F3|2:1}}⁠{{DFtext|: View Biome|7:1}} near the bottom right. It is '''very important''' to press {{K|F1}}, {{K|F2}}, etc, to check all of them (Macs and laptops may require {{k|fn}}-{{k|F1}}). Each may have significantly different features such as an aquifer or evil biome '''not initially shown''' in the info due to not being in the main biome (the one visible with {{k|F1}}).
}}

{{TipBox2|titlebg=#00a|Starting Site|
[[File:Quickstart-good-location.png|thumb|300px|right|An example of a good starting site.]]
For your first game, find a site with the following properties:
*'''NO [[Aquifer]]''' (or at least not a heavy or varied aquifer. This is '''''very''''' important!)
*'''Trees:''' Woodland or Heavily Forested (or, at the very least, sparsely forested)
*'''Surroundings:''' Serene, calm, or at least '''not''' any evil or savage biome.
*A '''River'''
The following are also good to have, but focus on getting a decent site, not a perfect one.
*'''Temperature:''' Warm
*'''Clay or Soil''' makes farming easier when starting out
*'''Shallow Metals''' (That's Metals, plural, not Metal. You want more than one.)
*'''Deep Metal(s)'''
*'''Flux Stone''' For your steel industry
*Use {{k|Tab}} to check your neighbors and avoid places with '''towers''', '''goblins''', or other groups at war with you.
See '''[[/Starting site/]]''' for more info on why these characteristics are important.}}

[[File:Quickstart-finder.png|thumb|right|Initial finder criteria]]
While finding a site is not as simple as world generation, the {{K|f}}ind tool can help quite a bit. Use {{k|↑}} {{k|↓}} {{k|←}} {{k|→}} to change the criteria as shown to the right, then press {{k|Enter}} to start the search.
[[File:Quickstart-finder-partial.png|thumb|right|Finder partial match missing Good surroundings]]
If the search completes and the world map is covered with red flashing {{DFtext|X|4:1}}s, that means that it couldn't find any area matching your criteria. The criteria list shows which criteria it couldn't meet in red for the closet match — try changing or removing the red criteria and searching again. Or, you can put only some criteria into the tool (at the very least, No Heavy/Varied Aquifer) and add more to narrow the search. Note that "Calm" is classified as Neutral with Low Savagery (see [[Surroundings#Combinations_of_surroundings|the chart here]] for why) and that Neutral is Medium Evil on the finder criteria, while Good is Low Evil.)

Once the find tool has finished searching with matches found, press {{K|ESC}} to look at the results. Any region in which it found a match will be indicated by a green flashing {{DFtext|X|2:1}} on the region and world maps. Since the find tool '''only''' indicates '''regions''' containing matches, you will need to check the local map manually (with {{k|u}} {{k|m}} {{k|k}} {{k|h}}) until you find the most suitable site. Don't forget that there can be multiple biomes to check with {{K|F1}}, {{K|F2}}, etc.

Additionally, you can resize your embark area using {{k|U}} {{k|M}} {{k|K}} {{k|H}}. A 4x4 embark (the default) is usually reasonable, but you may want to change the size to avoid an undesirable biome or match your finder criteria.

If you are unable to find a site that you are willing to embark on, you could always create a new world. Otherwise, once you have the right area highlighted on the local map, press {{K|e}} to move onto the next step.

== Skills and Equipment ==
{{TipBox2|float=right|titlebg=#0a0|Optional: Preparing Carefully|If, at this point, you'd like to get into all of the details of picking individual skills and equipment for your expedition, select {{DFtext|Prepare for the journey carefully}} and see '''[[Quickstart_guide/Preparing_carefully|Preparing carefully]]''' for instructions. '''This is completely optional'''.
And preparing carefully makes little difference in the long run, especially without experience as to what to change.}}

Now the '''Prepare for the Journey''' screen should appear. You will be given the choice to either:
*{{DFtext|Play Now!}}
*{{DFtext|Prepare for the journey carefully}}.

Selecting {{DFtext|Play Now!}} will start you out with a default set of equipment that is reasonably safe, allowing you to skip having to set up your skills and equipment. If you'd like to get going now, just select that option.
{{clear}}

=A Minimal Fortress=
[[File:Quickstart-map-starting.png|thumb|right|Starting out. In this example, the dwarves will be digging out an entrance tunnel in the sandy cliff on the right. (You can use {{K|Tab}} to show or hide the overview map.)]]

At this point, you have embarked, and your dwarves have arrived at their destination. You will see your dwarves clustered around their wagonful of supplies, somewhere near the center of your map. '''Immediately hit {{K|Space}} to pause the game''' unless it is already paused.

==Surveying the Area==
'''Do not unpause the game just yet.''' Take a look around. Use the {{K|k}} command and the arrow keys (remember that {{k|Shift}}+arrow keys will move faster). Look up and down a few [[z-level]]s with {{K|<}} and {{K|>}} ({{k-|Shift|,}} and {{k-|Shift|.}} on many keyboards). The mousewheel will zoom the map in and out. Place the cursor on various tiles to familiarize yourself with what the symbols mean. If you get lost, you can press {{K|F1}} (or {{k-|Fn|F1}} on some systems) to return to the wagon. (You can define more [[hotkeys]] later, to jump quickly to other sites of interest.) Notice the terrain features, the vegetation, and any minerals visible. If you chose a site with flowing water, where is it? What about pools of water? The more carefully you examine your site before breaking ground, the better off you will be.

Remember that this is more of a simulation than a game. It is not "play balanced", and you can very easily find yourself in impossible situations. That is all part of the [[fun]], because even when you lose, you create an interesting story. Your wagon serves as the initial meeting area for your dwarves. Since you should have started in a non-freezing, calm (low savagery), non-evil biome, you shouldn't face any immediate danger, but if for some reason the area around your wagon proves to be unsafe, immediately designate another meeting zone using {{K|i}} (see [[#Temporary Meeting Area|Temporary Meeting Area]] below).

==Controlling Your Dwarves==
The first thing to keep in mind is that, for the most part, you can't directly control your dwarves the way you control characters in a typical fantasy RPG. Instead, you '''designate''' things that need to be done and then dwarves with the appropriate labor assignments will decide what to do.

Some tasks receive a higher priority. For example, if a dwarf needs to eat, then he will go eat, and only get around to digging a tunnel once he is done eating. It is also possible to designate things that no dwarf is able to do. For example, if you designate an area to mine, but no dwarf has mining as one of his allowed labors, or no dwarf has a [[pick]], then the mining will never get done, and the game will not always advise you of why.

So, what you are doing throughout the game is essentially giving your dwarves a detailed group-wide to-do list, but it's up to them to figure out which one of them will execute any given task if the task is even possible. Often many of the details of how a task is performed (such as exactly which rock will be used to make crafts) are left up to them (though you ''can'' specify the details of tasks, such as the material or design, in the {{k|d}}etails menus in workshops).

===''Stout Labor''===
{{TipBox2|float=right|titlebg=#0a0|Keybindings|
If you're on a laptop (or using a restricted keyboard), you may notice that using {{k|+}} to scroll upward on some menus is inconvenient, since it requires the {{k|Shift}} key. Fortunately, this is easy to change by modifying your [[key binding]]s:
# Press {{k|Esc}} to access the [[#Options menu|options menu]] and select {{DFtext|Key Bindings}}
# Select {{DFtext|General}}, scroll down to {{DFtext|Move secondary selector down}} (using the arrow keys), move right, and select {{DFtext|Add binding}}
# Press {{k|1==}} and select either option that appears. (Technically, you can choose any key you like at this point. However, {{k|1==}} (equals) is probably a good choice, since it's next to {{k|-}}, if you are using an American keyboard, and isn't used for anything else in menus.)
# Scroll down, select {{DFtext|By letter: +}}, and press {{k|Backspace}} (or {{k|Delete}}, depending on your keyboard)
# Press {{k|Esc}} and select {{DFtext|Save and exit}}
You can now use {{k|1==}} instead of {{k|+}} to scroll these types of menus (including the labors menu), which can be significantly easier than using {{k|+}} on certain keyboards.
}}
{{TipBox2|float=right|titlebg=#aa0|Utilities|2=
You may have noticed that the UI for managing dwarves is a bit difficult to use. There are a few utilities available for this purpose (for Windows, Mac OS X, and most Linux systems):
* '''[[Utilities#Dwarf_Therapist|Dwarf Therapist]]''' can make labor management considerably easier, especially when you're dealing with twenty times the number of dwarves you have now. It can group and sort dwarves by multiple attributes and display their preferences, mood, and more.
* '''[[Utility:DFHack|DFHack]]''' includes "Dwarf Manipulator", a UI for managing labors. It has fewer features than Dwarf Therapist, but displays much of the same information and is adequate for normal use. In addition, it is accessible from within DF via {{k-|u|l}}, eliminating the need to constantly switch between applications.
}}

'''Labors''' are how you control what types of tasks a dwarf will do. For example, if the [[Fishing]] labor is enabled for a dwarf, that dwarf is allowed to engage in fishing. When dwarves are idle, it could be because you haven't given them anything to do, or it could be because none of the idle dwarves have been told that they're allowed to do the types of tasks you've designated. For example, if you designate an area to mine, but none of the dwarves have the mining labor enabled, they will all just sit around ignoring your mining designation, thinking that it isn't their job. Dwarves will automatically have some labors enabled if they start out with skill in those labors, and some labors (such as hauling and cleaning) are enabled for all dwarves by default. This is why you didn't need to enable any labors on dwarves to get them to haul and mine, but later you may need a labor that no dwarf is currently capable of. Look over your dwarves' assigned [[labor]]s: Press {{K|v}} (View Units) then place the cursor on a dwarf. Now, press {{K|p}}-{{K|l}} for "preferences: labors". You will see a list of labor categories that you can navigate using {{K|-}} and {{K|+}}. You can enter each category with {{k|Enter}} (except for mining, which is a single labor), toggle each labor off and on with {{K|Enter}}, and get back out with {{K|Esc}}. After exiting the View Units menu, you can use {{K|u}} (the units screen) to help you locate dwarves. Hit {{K|u}}, select a dwarf, hit {{K|z}} for "zoom to creature" and you'll automatically be placed in view mode on that dwarf. (Then use {{K|p}}-{{K|l}} to get to the labor configuration menu if necessary.)

Even if no dwarves have the corresponding skills, ensure the following labors are set as specified:

{| class="wikitable"
! Category
! Labor
! Dwarves Assigned
|-
| Woodworking || [[wood cutter|Wood Cutting]] || 1 or more
|-
| Stoneworking || [[engraver|Stone Detailing]] || 1 or more
|-
| Hunting/Related || [[ambusher|Hunting]] || 0 (disabled for all)
|-
| Farming/Related || [[wood burner|Wood Burning]] || 1 or more
|-
| Farming/Related || [[herbalist|Plant Gathering]] || 1 or more
|-
| Fishing/Related || [[fisherdwarf|Fishing]] || 0 (disabled for all)
|-
| Metalsmithing || [[furnace operator|Furnace Operating]] || 1 or more
|-
| Metalsmithing || [[armorsmith|Armoring]] || 1 or more
|-
| Metalsmithing || [[weaponsmith|Weaponsmithing]] || 1 or more
|-
| Metalsmithing || [[blacksmith|Blacksmithing]] || 1 or more
|-
| Metalsmithing || [[metal crafter|Metalcrafting]] || 1 or more
|-
| Jewelry || [[gem cutter|Gem Cutting]] || 1 or more
|}

It's important to disable fishing and hunting until you have your initial fort completed — dwarves with these labors enabled will constantly be outside attempting to perform them. When you're first starting out you don't want dwarves wandering around alone where they can get killed (in addition, they won't be doing anything useful, like hauling). Note that ''any'' unskilled dwarf can perform any labor given the necessary equipment and materials. Dwarves with no skill will simply be slow and produce a smaller quantity of lower-quality goods in a given time period, but they will gain skill points as they do so.

==Strike The Earth!==
{{TipBox2|titlebg=green|float=right|Getting your dwarves to safety|
As you now know, you can't control your dwarves directly. So how do you tell them to get inside your newly dug rooms?
*[[Activity_zone#Meeting_area|Meeting Area]] You can designate a Meeting Area zone inside the new rooms. Press {{k|i}}, then draw the rectangle to create a zone. Afterwards make it a Meeting Area. ''See also the [[zone]] page for more information.''
*[[Stockpiles]] (see [[Quickstart_guide#Stockpiles|below]]) Stockpiles tell your dwarves where to put things. Create a stockpile for everything, and dwarves will start to haul all your items there.}}
Decide where you will build your main entrance. Generally, you will want to get all your dwarves and supplies inside a protected area as quickly as possible. The best strategy is to put the entrance near your wagon to speed up the process of hauling all of your supplies inside.

The {{K|d}}esignations menu allows you to select areas to dig. There are multiple methods of digging:
* '''[[Mining]]''' removes solid, floor-to-ceiling terrain (natural 'walls') on the z-level selected, leaving behind a rock or soil surface (also referred to as a natural floor). This does '''not''' do anything in areas without natural walls (for example, the surface or previously-mined areas).
* '''[[Channel]]ing''' removes ''natural'' (rock/soil) floors (either created naturally or by mining) and creates a ramp (▲) on the z-level below. Note that you will see a down arrow (▼) on the current z-level, indicating a ramp on the level below. (For best results, ensure that the area below is unrevealed, i.e. black).

To designate an area for digging:
#Hit {{K|d}} to bring up the [[Designations Menu]].
#Hit {{K|d}} to mine or {{k|h}} to channel (see above)
#Place the cursor on one corner of the rectangular area you want to designate and press {{K|Enter}}.
#Move the cursor to the other corner of the rectangle and press {{K|Enter}}. A rectangle will be highlighted and a miner will start to dig out this area once you exit the menu (with {{K|Esc}}) and unpause the game with {{K|Space}}.

This is basically how all of the designation commands work. Everything has to be designated one rectangle at a time, but rectangles can be many tiles wide. After you press {{K|d}} to designate, make sure it's set to "Standard" in the settings at the bottom, rather than "Marker only." You can set this with {{K|m}}. If it's set to "Marker only", the designation will not be carried out.

[[File:Digging Channeling tiles.PNG|200px|thumb|right|Demonstrating the difference between mining and channeling. Mining creates empty space on the same level where it is designated. Channeling creates empty space in the level below, clearing the floor. The levels are connected by up/down ramps. ]]

{{TipBox2|titlebg=red|float=left|Channeling|
Note that channeling can be [[fun|dangerous]]. Unless you know what you're doing, you should only ever make a pit one z-level deep. If you dig a pit multiple z-levels deep, only the lowest level will have an upward [[ramp]], which is not enough for dwarves to leave the pit. (Dwarves can [[climb]] out in some circumstances, but this is unreliable.)

<diagram>
Pit depth: 1 z-level 2 z-levels 2 z-levels
Ground[%26] [#2:1]__[#4:1][%31][#2:1]__ __ __ __ [#4:1][%31][#2:1]_
[#6:1][@4:1][%178][%178][#4:1][@][%30][#6:1][@4:1][%178][%178][@#] [#6:1][@4:1][%178][%178][#4:1][@][%31][#6:1][@4:1][%178][%178][@#] [#6:1][@4:1][%178][%178][#4:1][@][%31][#6:1][#4:1][@][%30][#6:1][@4:1][%178][@#]
[#6:1][@4:1][%178][%178][%178][%178][%178][@#] [#6:1][@4:1][%178][%178][#4:1][@][%30][#6:1][@4:1][%178][%178][@#] [#6:1][@4:1][%178][%178][#4:1][@][%30][#6:1][@4:1][%178][%178][@#]
[#6:1][@4:1][%178][%178][%178][%178][%178][@#] [#6:1][@4:1][%178][%178][%178][%178][%178][@#]
</diagram>

This diagram shows the cross-section (side view) of 1x1 pits channeled 1 z-level deep, 2 z-levels deep and the correct way to do a 2 z-level deep ramp. The appearance of "downward ramps" can be confusing as there is no such thing - the down arrow indicates a ramp on the level below. Dwarves in the first pit can walk up the ramp to ground level and escape, while dwarves in the second pit cannot use the ramp at all. The third pit lets dwarves walk back to the surface again since the two ramps are offset to produce a continued slope. In short, channels (particularly channels multiple z-levels deep) can be dangerous. Digging an entryway from the surface level is one of the few times you'll ever need to channel.

Stairs can also be used for an entryway, but channels allow [[wagon]]s entry to your fortress.
}}
If your wagon is near a [[cliff]] or hill (generally speaking, any difference in levels, usually shown by the existence of natural ramps), you can just designate a tunnel to mine ({{K|d}}-{{K|d}}) into the cliff to create an entryway. If the wagon is surrounded by flat terrain, [[channel]] out a 3x3 rectangle on the surface with {{K|d}}-{{K|h}} to create a sort of pit with ramps on the edges, then go down one z-level with {{K|>}} and tunnel into one wall of the pit (with {{K|d}}-{{K|d}}) to create your entry.

Dig a hallway one tile wide and ''at least'' 10 long, ideally more like 20 ({{k|Shift}} moves 10 tiles when digging, so this can be easily accomplished by pressing {{k|Shift}}+an arrow key twice). This will be your entryway.

Your entryway defines the boundary between your safe and protected inner fort, and the big, bad, outside world. You want this to be your only entrance, so that you only have to worry about defending this one opening. A somewhat-outdated video guide to starting a fortress can be found [https://www.youtube.com/watch?v=CLYDcuk29bE&feature=plcp here]. (Note that this applies to v0.34.11, not v{{current/version/ns}}, so some parts may be inaccurate in the current version.)

{{clear}}
=== ''Additional miners'' ===
Mining will go faster if you have more than one dwarf doing it. By default, only one dwarf has the Mining labor enabled, but this can be changed fairly easily:
* Choose a dwarf that isn't doing anything especially useful (the fish cleaner is a good choice for a beginning fortress, but you can always change your mind if you end up with a useless peasant later on)
* Press {{k|v}}, navigate to the dwarf, and press {{k|p}}-{{k|l}}
* Enable the "Mining" option (see [[#Stout Labor|Stout Labor]] above)
* Exit with {{k|Esc}}
The next time you designate an area for mining, both of your miners should start working (assuming they're not busy doing something else).

'''Notes:'''
* Each miner requires a [[pick]]. A standard embark comes with 2 picks. If you want more than two miners, you'll need to forge more picks (forging is covered later in this guide). Two miners should be adequate for most fortresses, but more miners can add reliability (for when a miner decides to sleep) and speed. For now, you'll almost never need more than two miners, but you'll want more once your fortress expands.
* If you're digging a one-tile-wide hallway, only one miner can work from an end.
* Mining, Wood Cutting, & Hunting labors are mutually exclusive - a dwarf can only have up to one of these professions active at a time. For this reason, it's not recommended to make your only woodcutter a miner, since they won't be able to cut wood anymore.

==Delving Secure Lodgings==
Near the middle of the entry tunnel, build a 5x5 room, and link it to the entrance tunnel with a 3-tile-wide passageway. Expand the main entry tunnel to ''three'' tiles wide from the entrance of the new room to the outside entry. At the end of the entry tunnel, dig a small room, which will later become your main stairwell. Two tiles past that, dig a larger room, which will later become your general stockpile, and connect it to the stairwell with a narrow passageway.

[[File:Quickstart lodgings 1.png|thumb|right|An example layout, as described in this section. Note the 3-tile wide passage - this allows merchants to access your depot, which will go in the 5x5 room. Note that the turn also needs to be 3 tiles wide; otherwise, wagons won't be able to access the room.]]

=== ''Room dimensions'' ===
Apart from wagon access (3 tiles wide), the trade depot (5x5), and other workshops (3x3), there are no fixed dimensions you need to worry about. The lower limiting factor is the traffic your tunnels receive (dwarves may have to start climbing over each other), and the space your rooms need (stockpiles, tables/chairs, livestock). The practical maximum size is limited by how long it takes your miners to dig the rooms out, especially if they're digging in stone instead of soil (digging through soil is much faster). Most sites have at least one level soil layer below ground level, which is where you're digging right now, but as you dig deeper you'll hit stone (if you haven't already), and digging will become slower. In most fortresses, even the main hallways never need to be wider than 3 tiles, and needing more than 3 tiles of stairs per floor is very rare. A 3x3 per floor staircase (9 stairs!) is absolute overkill for anything but 20-year-old 300-resident capitals. For most tunnels in your fortress, 2 tiles wide will be sufficient, and many will be fine at just 1 tile wide. 11x11 is a convenient size for stockpile rooms, as the {{k|Shift}}+arrow keys move the cursor 11 tiles. However, something smaller is perfectly fine for rarer stockpiles, offices, and small dining rooms. Commoners’ bedrooms need not be larger than the amount of furniture you want inside.

=== ''Mining safety'' ===
While mining, take care to avoid digging into [[water]]. Dwarves are usually poor swimmers, and are unlikely to escape from an underground flood. However, it is safe to mine ''next to'' underground water, as long as you leave at least one "wall" tile between them (see the picture to the right). You can also mine one z-level under a body of water (for example, mining under a river), but you will have to designate each tile individually because DF automatically cancels digging of newly-revealed "damp" tiles (tiles are considered damp when they are adjacent to a water tile, regardless of whether the water tile is on the same z-level or not).

Also note that '''water can flow diagonally''':
<diagram>
[#00f]≈[#]▓.▓ [#00f]≈[#]▓.▓
▓▓.▓ ▓..▓

[#0f0]ok[#] [#f00]flood[#]
</diagram>

=== ''Stockpiles'' ===
[[File:Quickstart-custom-stockpile.png|right|thumb|Keep corpses, refuse, stone and wood out of general use stockpiles. You can come back and change the settings on this stockpile using {{K|q}}, selecting the stockpile, then pressing {{K|s}}. Try to remember to come back here to disable/forbid types of things as you create more specific stockpiles for them.]]
'''Stockpiles''' are very important. These areas are where your dwarves will drop things for storage when they aren't needed elsewhere. To create a '''general purpose stockpile''' for your first storage area:
#Hit {{K|p}} to open the Stockpiles menu.
#Use {{K|t}} to change the [[Stockpile#Custom_stockpiles|custom stockpile]] settings to {{K|e}}nable everything but '''Corpses''', '''Refuse''', '''Stone''', '''Gems''', and '''Wood'''. Use directional keys, {{K|e}}nable, {{K|d}}isable to do this.
#{{k|Esc}} out of that screen back to the stockpiles menu.
#Hit {{K|c}} to select Custom Stockpile, if it isn't already selected.
#Designate the whole 11x11 storage room as a custom stockpile. This works just like designating an area to dig: place the cursor on one corner of the room, hit {{K|Enter}}, move to the opposite corner, and hit {{K|Enter}} again.
#Press {{K|Esc}} to get out of the Stockpiles menu.
Once you exit the stockpiles menu and unpause, you should see dwarves running off to haul everything from your wagon into the new stockpile area. Later, if you like, you can change what sort of things the stockpile accepts by hitting {{K|q}} (Set Building Tasks/Prefs), placing the cursor on the stockpile, then pressing {{K|s}} to get to the stockpile settings.

It is particularly important to '''keep wood, stone, refuse, and corpses out of your general purpose stockpile''', so you may want to double check to make sure all of these things are disabled in the stockpile settings. Failure to keep these things out of this stockpile will rapidly fill it up, causing workshops to become cluttered when dwarves can't store things in the stockpile.
'''Note:''' When assigning stockpiles, you should make sure they're in a vacant area (i.e. the tiles should not have any items already stored on them). Dwarves will not haul items to occupied tiles, so make sure the area is vacant (and already mined out) before assigning a stockpile.

=== ''Stairways'' ===

{{TipBox2|float=right|titlebg=#0a0|width=45%|Up, Down, Up/Down: Types of Stairs|
In Dwarf Fortress, every [[z-level]] is composed of a [[floor]] and a [[wall]] (or "space between floors"). The confusingly named "down" and "up" [[stairs]] have nothing to do with the direction creatures can move to; instead, down stairs penetrate floors, while up stairs penetrate walls. Up/down stairs penetrate the wall and the floor below. ''(note the picture to the left)''

Consequently, you will normally use up/down stairs, and use down and up stairs only for the top and bottom-most level of your staircase respectively. If you're not sure whether you want to expand the staircase in the future, use up/down stairs at the end.
}}

Designate a downward [[Stairs|stairway]] in the room you dug out for the stairwell (''not'' the 5x5 room that you dug out earlier) with {{K-|d|j}}. Notice that after your miner digs the stairway, it doesn't automatically create another stairway on the z-level below. If you hit {{K|>}} to move the view down a z-level you'll see that there's no stairway below, but there is a revealed tile of rock/soil. Because of the down stairway that was dug, this tile is now accessible to miners. You can then designate an up/down stairway on it with {{K-|d|i}} and the miner dwarf will dig it out. Below that you can then dig out another up/down stairway and so on. For now just dig down one level; we will deepen the stairwell later.

[[Image:DF2014 Terraform.png|thumb|left|600px|''This is how the different stairs would look like from the side.'']]

{{clear}}

==Temporary Meeting Area==
[[File:Quickstart lodgings 2.png|thumb|right|An example meeting area. Note that this layer has a different type of soil than the layer above - this can happen often. Also note that the "north" side of this room is directly below the lake in the level above, but no water is present.]]

On the second z-level below ground (the one below the stockpile level, which you just reached with the staircase), dig a short, 3-tile wide passageway (this only needs to be 1-2 tiles long). Past that, dig out a room between 5x5 and 7x7, leaving room to enlarge it in at least one direction in the future. Using the {{k|i}} key, create an activity zone in the room you just created, filling the entire room (be careful not to make this too small lest your [[overcrowding|overcrowded]] animals start fighting). This works much like creating a stockpile except that you draw the rectangle before defining what the area is for. Draw the rectangle, filling the entire room, and set it to be a {{K|m}}eeting area. Your idle dwarves will hang around in this area, hopefully keeping them inside the fort and out of trouble.

NOTE: Again, make sure your [[DF2014:Activity_zone|activity zones]] is already mined out before attempting to designated the meeting area.

{{clear}}

==Refuse==
[[File:Dwarf fort tut miasma.jpg|thumb|right|Avoiding [[Miasma]]]]
Outside your fort entrance, use {{K|p}} followed by {{K|r}} to create a stock{{K|p}}ile for [[Stockpile#Refuse|{{K|r}}efuse]] ''at least'' 5x5 in size. This should be outside in the open or you will have problems with [[Miasma]]. If you do not disable [[vermin]] (Item Types -> remains), you will probably have to expand it later as it will fill up with vermin remains rather quickly. If you are seeing refuse appear in your general-purpose stockpile instead of the refuse pile, use {{K|q}} on the general stockpile and check its {{K|s}}ettings to make sure refuse has been disabled.
{{clear}}

==Food==

Food is necessary for your dwarves' survival - to keep functioning, they require constant supplies of food and drink - the {{k|z}} stock screen can be used to monitor how much food and drink is available. Luckily, your dwarves will eat almost everything raw, including plants.

===''Farming''===
For a reliable, long-term food and alcohol supply, you'll need to set up a farm. Dig out a medium-sized room in a [[soil]] layer (including sand, clay, loam, silt, peat, and ooze) accessible from inside your existing fortress. 5x5 is a good size to start with, but you'll want to leave room to expand in at least one direction. You must pick an ''underground'' area with mud or soil*. Placing this near the stockpiles is more efficient, since farmers won't need to travel as far.

[[File:Quickstart layout 3.png|thumb|right|A 5x5 room with a 3x3 farm plot]]


* Hopefully you have chosen a site with a soil layer, which will make farming much easier, but if not you will need to [[Irrigation|irrigate]] to create the required mud on stone floors.

Use {{K|b}}-{{k|p}} to build a 3x3 [[Farming|farm plot]] in the room you just created. Notice that some types of buildings (as well as most constructions) are not designated corner-to-corner like digging designations, stockpiles, or activity zones. Instead, you define the length and width of the building using {{K|u}}{{K|m}}{{K|k}}{{K|h}} and position it with the directional keys. Use {{K|u}}{{K|m}}{{K|k}}{{K|k}} to make the plot 3x3 and position it in the room, ideally near the wall to leave space for more plots later on.

Remember that you must enable the {{DFtext|Farming (Fields)}} labour for at least one dwarf, or the farm plot won't get built and farming will not take place. (If you selected "Play Now" earlier then you will start with a dwarf with farming enabled.)

{{K|Esc}} out of the build menu and wait for the farmer dwarf to create the plot. Once the plot is built, use {{K|q}} to set the plot to grow [[plump helmet]]s during all seasons. You can use {{K|+}} and {{K|-}} to select plump helmets (pressing {{k|-}} once should do the trick). Select with {{K|enter}}. '''You will need to press {{K|a}}, {{K|b}}, {{K|c}}, {{K|d}} and select Plump Helmets for each season''' — otherwise you'll end up with an idle field for 3/4ths of the year.

Later, if you are curious what is planted in each plot this season and how much, select the [[Controls_guide#View_items_in_buildings.2C_t|View Items in Buildings]] command {{K|t}} and move to the farm plot.

Note that a default embark starts with ''five'' plump helmet seeds — for now, only half of your field will end up being planted. Eventually, as your dwarves consume plump helmets, more seeds will become available and will be automatically planted by an unoccupied farmer.
:''For more troubleshooting tips, see [[How do I build a farm]]''
{{clear}}

=== ''Emergency food sources'' ===
Occasionally, even with a working plump helmet farm, you may experience food shortages. For now, you should have plenty of food on hand left over from embarking. However, if you ever run low on food, there are a few ways to obtain more:

==== ''Plant gathering'' ====
If you have shrubs ({{raw tile|"|2:0}}) growing above ground, you can harvest plants from them. Note that this requires a dwarf with the {{dftext|Plant gathering}} labor enabled (under {{dftext|Farming}}), and time (this can take a while for an inexperienced dwarf, and it doesn't always yield edible plants). To start, {{k|d}}esignate some {{k|p}}lants to be gathered on the surface (similar to selecting an area for mining, except it only selects plants in the given rectangle). Once processed, some will leave behind harvested plants (often edible berries).

====''Butchering''====
If you suddenly run low on food, butchering an animal is another option. Build a [[butcher]] shop ({{k|b}}, {{k|w}}, {{k|u}}) and mark one of your animals for slaughtering (press {{k|v}}, move the cursor to the animal, then press {{k|p}}, {{k|s}}). A dwarf with the butchering labor enabled will haul the animal off to the butcher's shop, work for a while, and produce neat stacks of meat products.

==Building material==
Initially, [[wood]] is probably a good choice for building material, as it's lightweight and can be easily obtained. You will need plenty of building materials as your fortress grows, but wood will suffice for now. If you are unable to locate enough wood (or if you run out of trees, which is unlikely at this point), extend your staircase down to a stone level ({{k|d}}-{{k|i}}) and mine out a small area (at least 5x5) to obtain stone.

Even if you don't have trees, you can obtain 3 logs from your embark wagon. Press {{K|q}}, place the cursor on your wagon, and hit {{K|x}} to deconstruct it. This will flag the wagon for disassembly. Eventually a carpenter will come along and turn the useless wagon into 3 units of wood. (Removing other buildings is done the same way.)

===''Woodcutting''===
{{Update in next major version}}
Assuming your site has [[tree]]s above ground, now is a good time to start obtaining wood. Create a stock{{K|p}}ile for {{K|w}}ood outside your entrance (preferably near to it). As it will only be temporary, don't make it too big (maybe 5x3, or 15 tiles total). Later, you will move this closer to your carpenter's workshop (once you build one), so don't worry about placement too much. Also near the entry, designate a couple of trees to be chopped down with {{K|d}}-{{K|t}}. One tree will produce many logs, so only designate three to five at this point. If you designate too many trees, your woodcutters will spend all of their time chopping them down and hauling the resulting logs, instead of doing other work. As soon as one tree is cut down and its wood stored in a stockpile, you can proceed to the next step (your woodcutter will continue cutting down any remaining designated trees).

==Drinks==
Drinks can be more problematic than food, since they require more preparation (except for [[water]], that is). In warmer weather, you can specify a "water source" activity zone ({{k|i}}-{{k|w}}) around a lake or river on the surface to keep your dwarves from dying of thirst, but dwarves deprived of [[alcohol]] slow down and become unhappy. In addition, drinking outside can be dangerous — dwarves running outside constantly risk running into wild animals, or worse. Creating a [[still]] to brew alcohol is the simplest solution to these problems.

You need a [[brewer]] to brew drinks. Unfortunately, your brewer is also your woodcutter (with a default embark), who is busy cutting down trees. You will want to make a different dwarf your brewer instead, since both your brewer and woodcutter will be busy (and one dwarf can't do both jobs at the same time).
# Find your woodcutter in the {{k|u}}nits list, select it, and press {{k|z}} (this selects the dwarf without you having to search your entire map). Use the {{k|p}}-{{k|l}} menu to disable brewing (located under "Farming/related" — you can navigate this menu with the {{k|+}} and {{k|-}} buttons).
# Pick another dwarf that isn't doing anything useful. Right now, this can probably be your fish cleaner, but you can change this as soon as some migrants arrive (by following these steps again).
# Use the {{k|u}}-{{k|z}}-{{k|p}}-{{k|l}} menu again to enable brewing on the new dwarf.

[[File:Quickstart still 1.png|thumb|right|A completed still]]
Assuming you have building materials available (which you will if your woodcutter has been doing their job), you can now create a still:
# Dig out a 3x3 area connected to the farm plot.
# Use {{k|b}}-{{k|w}}-{{k|l}} to build a still. Position it in the 3x3 area you just created and press {{k|Enter}}.
# Use {{K|Enter}} to select a building material for the still (this is probably one of the logs you just cut down by default).
# Use {{k|Esc}} to exit the menu, and unpause the game.
After a short delay, your new brewer should run off, drag a log over to the workshop site, and build the workshop. (This is also how building other workshops works, but you won't need to do that yet).

To brew drinks, use {{k|q}} to select the still and press {{k|a}}dd task-{{k|b}}rew drink. '''This will not work yet''', since you don't have any empty barrels or rock pots, but you should start brewing in the first six months (see [[Calendar]] and [[Status]]).
{{clear}}

==Pasture==
{{TipBox2|float=right|Grazers|
If you aren't sure whether or not an animal is a grazer, you can check {{catlink|Grazer|this category}}. (You can also [[Special:search|search]] for the animal on this wiki.)
}}
If you have any grazing animals with you, such as the draft animals used to pull your wagon, they will die if they are kept away from grass for too long. Use {{K|i}} to create a Pe{{K|n}}/[[Pasture]] zone over a grassy area outside and assign your grazing animals to it using {{K|N}} (while still selecting the zone). This area needs to be about 10x10 or so to ensure they have enough grass and don't trample it all. The amount of grass required varies greatly, depending on the type(s) of animals being pastured. If you intend to keep grazing animals permanently, you may need vastly larger pastures later. As an alternative, you might wish to [[Butcher's shop|slaughter]] your largest animals for food and materials.

==Designing your first fortress==
While this guide recommends a vertical fortress design around a central stairwell, with each z-level being used for a particular purpose, it is not really that important to use this design for your first fortress. Therefore, feel free to put any of the areas described in the rest of this guide on your main level or wherever you want as long as dwarves can get to them without going outside the fort. In other words, you can think of the "levels" described in the guide more as areas that can really all be on the same level if you have space. Later you can ponder over what makes things most efficient, but for now just do whatever you find easiest. Note that you may need to dig down a bit to get to stone if you have more than one z-level of sand/clay/soil below the surface.

==Workshops==
[[File:Quickstart workshops 1.png|thumb|right|An example workshop layout. The gem stockpile (empty) is north of the Jeweler's workshop (southwest corner), the wood stockpile is east of the Carpenter's workshop (northwest corner), and the stone stockpile occupies the rest of the space. Note the wheelbarrow (Ö/umlaut-O) in the stone stockpile.]]
Most labors of your dwarves need a place where they can process raw materials — [[workshop]]s. Almost all of them occupy a 3x3 square, and most of them require just 1 unit of any building material (wood, stone, metal). Dig your stairwell down one level (with {{K-|d|i}}), if you haven't already. It's fine if this layer is soil — in fact, soil is better, since it's easier to dig through (if you only have one soil layer, you can put these workshops somewhere on your first level). Dig space for your workshops off of the stairwell. It will hold your [[Mechanic's_workshop|mechanic's]], [[Mason's_workshop|mason's]], [[Carpenter's_workshop|carpenter's]], and [[Jeweler's_workshop|jeweler's]] [[workshop]]s. Something to consider is stockpile proximity: the farther away the material is the dwarves use, the more time they waste with walking. So for now, dig out some more space for stockpiles close to where your new workshops will be (wood for your carpenter, stone for your mason and mechanic, and gems for your jeweler).
It doesn't matter if you put everything in one large room or dig out small rooms for each workshop and stockpile. Note however that some tiles of workshops are impassable: they appear as dark green 'X' when you choose a location (the specific wiki pages of the workshops also show you this). So before you build small 3x3 rooms for each workshop, make sure your dwarves will be able to reach them. Once you've dug out your rooms, set your miners to work by adding a z-level or two to the staircase (you can designate multiple z-levels at once using {{k|<}} and {{k|>}}, just like moving up and down). Hopefully you'll obtain some stone by doing this, which will be useful eventually. While your miners are busy, use {{K-|b|w}} to build the workshops, using whatever building material you have. If you are still digging in soil and don't have stone yet, just use wood; the material really doesn't matter in this case. Be sure that your craftsdwarves still have labors corresponding to each workshop enabled (see [[#Stout Labor|Stout Labor]] above) so they will begin construction. (Dwarves already busy mining or hauling may not immediately stop to construct workshops; if you like, you may temporarily disable other labors in order to jumpstart workshop construction.) If the construction of any building gets "suspended" just use {{K|q}} to unsuspend it. (This can happen if another dwarf or object is blocking the way. See [[#"Garbage" Dumping|Garbage Dumping]] below if you find you need to remove an object.)

{{TipBox2|float=right|titlebg=#0a0|Too Good for Menial Peon Work|Certain labors are crucial in setting up a fort. At some point you may want to disable less important labors such as hauling for dwarves with the crucial skills of mining, masonry, architecture, carpentry, mechanics, and maybe others. You want these dwarves working on creating beds, doors, and trap components before hauling stone and cleaning.}}
Remove the temporary wood stockpile you created outside (using {{K-|p|x}} and selecting the entire stockpile) and dwarves will move the wood to the new wood storage area.

Go to your mason's shop with {{K|q}} and use {{K|a}} to queue up one [[table|{{k|t}}able]] and one [[throne]]/{{k|c}}hair. You will find out why you need these in a second, but now is a good time to start building them. If you still don't have any stone at this point just use wood at the carpenter's workshop.

At this point, it is a good idea to build a few [[wheelbarrow]]s to make hauling large objects (particularly stone) more efficient. Queue up 2 or 3 at the carpenter's workshop. (Wheelbarrows are located near the bottom of the list, on a separate page. They are not visible initially, so you'll need to scroll with {{k|+}} or {{k|-}} — scrolling up with {{k|-}} is more efficient, as it wraps to the bottom of the list.) While the wheelbarrows are being built, select your stone stockpile with {{k|q}} and use {{k|w}} to increase "Max Wheelbarrow" to 3 (the maximum). Your dwarves will automatically move wheelbarrows to the stockpile once they are built.

===''"Where did I build that ____?"''===
As you build workshops, furnaces, Trade Depot, other buildings, rooms and even zones, you may start to lose track of where they all are -- or where they're supposed to be built, but some dwarf is too busy eating/drinking/hauling. There are a couple of commands available from the main UI that will help you locate what you built.

* You can View {{K|R}}ooms/Buildings to see a Building List, and also Zoom {{K|t}}o the building/item, or {{K|q}}uery the building tasks.

* For incomplete buildings/constructions, you can also open the {{K|j}}ob list and then Go to {{K|b}}uilding to find the intended location.

{{clear}}

== Brewing ==
You'll need [[barrel]]s to store drinks for your dwarves. The stockpile you set up earlier will use as many barrels as possible to store items in, which means they can't be used to store drinks. To change this, press {{k|p}} to access the stockpile menu and use {{k|*}} to increase the number of "reserved" barrels (i.e. barrels kept out of stockpiles - 5 barrels is good for now). Queue up two or three barrels in your carpenter's workshop with {{k|a}}-{{k|v}}. (If you run out of wood at any point, cut down another tree or two outside). If a lack of wood cancelled a job, you will need to queue the job again. Go back to your still and order some drinks to be {{k|a}}-{{k|b}}rewed. Each drink requires one barrel and one edible plant, such as a plump helmet. Even if none of yours have been harvested yet, you should have some left over from embark. Also, brewing plump helmets creates ''two'' seeds from one plant, which makes plump helmets an excellent choice for a beginning fortress. Five barrels should be plenty for now (each plant makes 5 "units", or servings, of booze, and dwarves don't need to drink too often, so 30 units should last you a whole year. When the stocks get low, you'll probably want to start queueing up more drinks to be made (you should have more empty barrels by then)).

=="Garbage" Dumping==
{{main|Garbage dump}}

'''Note that garbage is not the same thing as refuse.''' [[Stockpile#Refuse|Refuse]] is [[Miasma|rotting stuff]]. Garbage is anything you designate to be hauled to a [[Activity_zone#Garbage_Dump|garbage dump]], even important things that aren't really garbage. Think of your garbage dump zone as a way to specify that objects you select will be brought to a specific area.

Use {{K|i}} to create a 1x1 activity zone somewhere near your mason's and mechanic's workshops and set it to be a garbage {{k|d}}ump. Unlike stockpile areas where you are limited to storing one object per tile, any number of items may be piled in a garbage area. That means you will only need one tile to hold as much "garbage" as you like. Although many of the room sizes in this guide are suggestions, think of the 1x1 garbage dump size as mandatory. At some point you will probably want to retrieve an important item from your garbage dump, and the more tiles your dump contains, the harder it will be to find anything in it. Press {{k|d}}-{{k|b}} to get to the mass dump/forbid screen and select the {{k|d}}ump option. With "dump" selected, designate a rectangle over the loose stones cluttering up your living area (if there are any – this often isn't a problem yet if you've built your fort in a soil layer). This will designate this stone to be transported to a garbage dump zone. Be sure not to designate the stone in your stockpiles by mistake, since that will only cause your dwarves to perform unnecessary hauling. Once the stone from your living area has been moved there, it will be set as [[Forbid|forbidden]]. Before it can be used you will need to unforbid it using the same {{k|d}}-{{k|b}} screen, hitting {{k|c}} to claim it. Note that dwarves hauling stone (or any large, heavy objects) move slowly, and can take a lot of time to reach their destination. This can be a major waste of time if you designate 50 boulders to be dumped at once. Unless the stone is in the way of something, you don't ''need'' to dump it every time you dig out a new area. Stones lying on the ground don't slow dwarves down at all. If there is a particular dwarf you don't want hauling "garbage", you can disable the "Refuse Hauling" labor (under the "Hauling" category). Miners are good candidates, since they are far more useful when digging than when moving the stone they just dug out.

Congratulations! Knowing how to use garbage dump zones puts you head and shoulders above many new players - it takes some people weeks to figure this out.

==Trading==
Not all embark sites have all the resources you need for a successful fortress, but every site has ''something'' you can sell. A talented dwarf can process any useless resource into something valuable, and [[trading]] is a good way to sell those goods.

''Note that producing goods creates [[wealth]] and getting too much wealth too fast can have [[Immigration#Migrant_wave_sizes|unwanted]] [[Siege|consequences]].''
===Trade Depot===
Build a [[trade depot]] using {{K|b}}-{{K|D}} in the 5x5 room you created near your entrance. This is where [[caravan]]s will park their stuff and where [[trading]] will take place when one arrives. (as stated earlier, the wagons are 3x3 so the entrance tunnel needs to be at least 3x3 for the wagons to go by). You will need one [[architect]], which will be enabled on your mason if you selected {{DFtext|Play now!}} at embark. You also need at least 3 logs or boulders to build the depot.

===Producing for export===
While there are some goods that are more valuable, and some that are less valuable, it's a good idea to simply produce/export what you have too much of and to import what you have too little of.
Generally though, [[Gem]]s and [[Finished goods]] are decent exports for a new player.

===Trading===
Once a caravan has arrived, you can mark the goods you want to sell through the Trade Depot, and your dwarves will begin moving them to the depot. Be careful not to sell wooden items to [[Elf|Elves]]; '''this includes containers:''' even a wooden bin full of metal crafts will make them upset. Also note that the traders will want to make a profit off of you. While they're happy with about 200%, the more profit they make on your site, the more goods they will bring next time, so it can be a good idea to give them even better deals.

''A more detailed overview of the entire process is [[Trading#Trading_Flowchart|here]].''

===What to buy===
In your first fortress, your priority should be importing some [[food]] and [[alcohol]]. In addition, you might want more [[Meat industry|livestock]], [[seed]]s (comes with a free bag), and - depending on what resources you are missing - additional [[pick]]s, [[barrel]]s, [[wood]], [[bag]]s, as well as [[rope]] and a [[bucket]] (for a well). While you're at it, check if you need an [[anvil]]. Maybe you forgot to bring one, or a [[kea]] stole it. Always having a small supply of ''all 3 kinds'' of [[cloth]], some [[gem]]s, [[leather]], a bit of [[sand]] (free bag!) are handy to have, as those are hard to come by on short notice.
If you're short on weapons-grade [[metal]] for your military, import not only actual metal [[bar]]s and [[ore]]s, buy ''all'' metal goods you can afford and [[Melt item|melt]] them down in a [[smelter]] to increase your yield.

===Troubleshooting===
Once the depot is built, use {{K|D}} from the main menu to make sure your depot is accessible. (This command is only available once the depot is built – before building, the command will be disabled, and while the depot is under construction everything will flash red until the depot is built). Once completed, checking {{k|D}}epot access will flash some of the following symbols:
* {{raw tile|X|4:4:1}}: This tile is not accessible by wagon. This could be because something is blocking it (a tree, a natural [[boulder]], etc.).
* {{raw tile|W|2:2:1}}: This tile is accessible by wagon. (These tiles will radiate outward from the depot, not from the map edges.)
:This is good, but does not guarantee wagons will be able to reach the depot. Make sure you see the words {{DFtext|Depot accessible|2:1}} in the menu.
* {{raw tile|D|3:2:1}} The depot is accessible via wagon.
* {{raw tile|D|6:2:1}} The depot is '''not''' accessible by wagon. See below.

If you see the message {{DFtext|Depot inaccessible|4:1}} in the menu (or the {{raw tile|D|6:2:1}}) symbol over the depot, try these solutions:
* Is the path to the depot (in your fortress) less than 3 tiles wide? If so, expand the entranceway and try {{k|D}} again.
* Are there [[tree]]s blocking a path to the depot outside? Try clearing a path by cutting down a few (you probably won't need to cut ''all'' the trees in a 3-tile wide path); usually cutting some at the end of a path of {{raw tile|W|2:2:1}}'s clears a path.
* Are there [[boulder]]s ({{raw tile|∞|7:0:0}}) blocking the path outside? To remove them easily, you need an [[engraver]]. If you selected "play now", you should have one already. Select {{k|d}}-{{k|s}}mooth Stone and designate the boulder(s) for smoothing. They should flash this symbol: {{raw tile|┼|7:0:1}}
* Is the path to the depot only accessible via stairs or did you build traps in the way? Wagons cannot pass traps or stairs, even if they're 3x3 wide.
It's possible that there are multiple obstacles blocking the depot, so keep checking {{k|D}}epot access until the {{DFtext|Depot accessible|2:1}} message appears.

''Note that even if your depot is inaccessible to wagons, traders still will come without wagons. They will carry much less goods and you can sell them much less, because their carrying capacity is greatly reduced.''

== Migrants ==
{{gametext|Some migrants have arrived.}}
At some point soon, you'll most likely be getting migrants (if you haven't already). You'll usually get between 5 and 15 migrants in the first 2 waves, which occur sometime during your second and third seasons. See [[/Migrants|this page]] for advice when you receive migrants.

== Bedrooms ==
Up to this point, your dwarves have probably been sleeping on dirt or rock in your fortress. While this is fine for a short time, your dwarves will gradually become less happy if they are forced to sleep without a bed. Under normal circumstances beds can only be made from wood, so be sure to designate some more trees to be cut down if you're short on logs.

[[Bedroom design|Designing living quarters]] is largely a matter of personal preference and aesthetic sense. While a few useful designs are discussed here, there are many other options. In general, try to keep the bedrooms close to the stairs, and make your access hallways at least two tiles wide to reduce congestion.

=== Location ===
Because noise generated from certain jobs (especially mining and woodcutting) can bother sleeping dwarves, doing these jobs within 8 tiles of a sleeping dwarf should be avoided (see [[noise]] for more information). There are two ways of accomplishing this:
* Placing bedrooms at the end of a hallway at least 8 tiles long will avoid most noise (as long as you are careful to avoid noisy jobs directly above or below the bedrooms).
* Extending your fortress down several z-levels will also work (9 levels from the surface is a safe choice), although extending a 3x3 staircase takes more work than extending a single hallway.
Both options work equally well, as long as you are careful to avoid disturbing sleeping dwarves. Ultimately it depends on how you want your fortress to look.

=== Layout ===
Due to the limited resources of a new fortress, setting up a communal sleeping area in a dormitory is often the best short-term solution. However, you can also set up individual bedrooms for dwarves.

'''Benefits of individual bedrooms:'''
* Dwarves are happier with their own bedroom and furniture.
* Individual rooms can increase your fort's perceived wealth.
'''Benefits of dormitories:'''
* Dormitories are easier to set up and expand (only one room is necessary, and each dwarf only requires one bed).
* Sleeping dwarves are much less likely to be attacked when other dwarves are around them.
* Multiple dwarves can sleep in a dormitory. In contrast, only one dwarf can ever sleep in a bedroom (dwarves cannot sleep in another dwarf's bedroom, even when unoccupied).
* Far fewer beds are needed – in a fort of 50 dwarves, for example, around five dwarves will be sleeping at a time (on average). A dormitory, therefore, rarely requires above ten beds, while individual bedrooms would require 50 beds to be built.
* Even when all of the beds are occupied, dwarves will still sleep in the general area of the dormitory. This is more convenient than having dwarves sleeping all over your fort.
For now, setting up a dormitory is easiest (although you can change this later, if you feel the need to).

=== Building ===
Queue up as many beds as you need in a carpenter's workshop (no more than 3 or 4 should be necessary for a dormitory). Beds are queued with {{k|q}}-{{k|a}}-{{k|b}} at a [[carpenter's workshop]] and built with {{k|b}}-{{k|b}}. (As long as your furniture/general-purpose stockpile isn't full yet, dwarves will store beds in them as they are finished, so there may be a delay before they're available to be built.)

'''Setting up a dormitory:'''
# Dig out an empty room in the location you selected.
# Once you have a bed ready, build it near the middle of the room (towards the end away from the entrance).
# Use {{k|q}} to select the bed and {{k|r}} to turn it into a bedroom. Resize the room until it fills the area you dug out (positioning the bed away from the entrance makes it easier to avoid extending the room out into the hallway). If you decide you don't like the position of the bed, remove it with {{k|q}}-{{k|x}} and place it again.
# Press {{k|d}} to turn the room into a dormitory (the menu should read {{DFtext|d: Dormitory <Y>}})
Once you have more beds built, you can place them in the same room. You don't need to mark them as dormitories as long as they're in the area you designated for the bedroom.

[[File:Quickstart-level-7-bedrooms.png|thumb|right|An example of individual bedrooms (with furniture, discussed below)]]
'''Setting up individual bedrooms:'''
# Dig out a small room for each bed (the size and shape are up to you, but 2 to 4 tiles generally works best).
# Build each bed in a room when ready
# Use {{k|q}}-{{k|r}} to mark the bed as a bedroom.
You should see {{DFtext|Current owner: Nobody}} in the menu. A dwarf will eventually get around to claiming the bedroom – you don't need to assign each dwarf to a specific bedroom.

==Nobles and Administrators==
Hit the {{k|n}} key to open up the [[Noble|nobles and administrators]] screen. The most important positions to assign are '''[[manager]]''', '''[[broker]]''', and '''[[bookkeeper]]'''.
* A '''manager''' will allow you to queue up [[work order]], which will greatly simplify managing your production.
* A '''bookkeeper''' will allow you to maintain inventory counts on the {{K|z}} screen so you'll know what you do and don't have.
* A '''broker''' is necessary to trade with a caravan once one has arrived at your [[trade depot]].

===Manager & Bookkeeper===
Your [[expedition leader]] is a good choice for manager and bookkeeper when starting out. Don't worry that it's just one dwarf doing all this; none of these jobs take very long.

While you are on this screen, highlight the bookkeeper and {{K|s}}et them to work for "Highest Precision" (all counts accurate). This will help train [[record keeper|bookkeeping]] faster and ensure that you aren't dealing with vague inventory counts.
:''See [[Stocks]] for a detailed explanation of the {{k|z}}-stocks screen.''

===Broker===
The broker should be another one of your other dwarves (rather than being the same as your bookkeeper) so that they're not too busy doing bookkeeping to actually talk to the traders when a trade delegation arrives.

Don't worry about the [[chief medical dwarf]] yet. He/she will be needed when you set up your [[Healthcare|hospital]] which won't be covered in this guide. Feel free to go check out the [[Healthcare]] guide once you're done.

===Offices (Studies)===
Some of your administrative positions (manager and bookkeeper) require an [[office]] in order to function. If your manager, for example, doesn't have an office, you will not be able to do any of the things that require a manager even though you have one assigned.
[[File:Quickstart-noble-selection.png|right|thumb|Nobles screen. The red stuff turns white once an office is assigned.]]

Earlier you should have queued up a table and throne in your mason's shop, and they should be done by now.
# Dig out a room near your sleeping quarters or stockpiles (at least 1x3, no more than 5x5).
# Place the furniture in it with {{k|b}}-{{k|c}} (chair) and {{k|b}}-{{k|t}} (table).
# Wait for the dwarves to install the furniture
# Use {{K|q}} to select the '''chair'''/throne (not the table), select "Make Throne Room or Study" ({{k|r}}), size the room appropriately, and then {{k|a}}ssign the chair to your expedition leader (who should be both your bookkeeper and manager).
# Hit {{K|n}} to verify that these positions now have the office they need (if so, {{DFtext|[REQUIRE]|7:1}} should no longer be red).

==Furniture==
{{TipBox2|float=right|titlebg=#0a0|width=45%|Different Names, Same Thing|As you've noticed, some things have different names based on what they're made of (for example, chairs vs. thrones and chests vs. coffers) even if they're functionally the same (material almost never makes a difference). [[Furniture#Furniture_types_with_multiple_names|Here's a list.]]

[[Bed]]s are a notable exception — they can only be made of wood.
}}
Now would be a good time to start building some [[furniture]]. You could queue up all these items directly from your workshops, but why not give your new manager a little practice?
Using the manager screen {{k|j}}-{{k|m}}, hit {{k|q}} to queue up a new job, and type "[[bed]]", and then select "construct bed." Set the quantity to around 4 (or more, depending on how many beds you need). Next, queue up at least four [[table]]s, eight [[throne]]s/chairs, and four doors. Make sure you select a material you have – rock or wood will both work for all of these (except beds), so use whatever you have in your stockpiles. If you like, you can also queue up a few wooden [[chest]]s or rock coffers and [[cabinet]]s (which can be used in bedrooms, if you set up individual bedrooms). The tables and chairs will go in your [[dining room]], speaking of which...

==Dining and Food Prep Area==
Right off the main stairwell (any unused area by the staircase will work), create three rooms. One will be for general food storage, one a [[dining room|dining hall]], and one a [[kitchen]]. The kitchen will allow you to make [[Cook#Recipes|prepared food]]. Make the room for the kitchen 5x5. The storage area and dining hall should be larger. Ideally, leave empty space on at least one side of your dining hall so that it can be expanded later if necessary.

[[File:Quickstart_dining_area.png|right|thumb|Dining level with dining hall (east), kitchen (north), storage area (west), fishery, butcher's workshop, and tanner's workshop (south).]]

Use {{K|b}}-{{K|w}}-{{k|z}} to build the kitchen in the middle of the 5x5 room. Use {{k|p}} to create {{K|f}}ood stockpiles in the remaining space around it, as well as the entire food storage room. Go back to your general-purpose stockpile on the top level and use {{K|q}} to change the {{K|s}}ettings to {{K|d}}isable Food. This will cause any food in your general purpose stockpile to get moved to your new food-only stockpiles. Hit {{K|z}} and select ''[[Kitchen]]'' from the top of the screen, then disable all cooking for plants, using {{K|c}}, {{K|C}} does everything (disable is red) and enable brewing for them so that they will only be used for brewing. Also disable alcoholic beverages for cooking, otherwise your cooks will waste perfectly good hooch in their cooking. The only time you might want to use alcohol in cooking is when you have lots of booze but are running out of food. If you plan to do any fishing, dig out another area and create a [[Fishery]] on this level so the uncleaned fish your fisherdwarf just caught can be cleaned (gutted) for consumption or cooking. If you plan to do any hunting or [[Status#Animal_Status_Screen|slaughter]] any animals, create a [[Butcher's shop]] on this level so animal corpses can be butchered. The fishery/butcher's shop can be placed behind the kitchen or the general food stockpile, for example. A door is recommended for the butcher's shop in order to contain [[Miasma]] should something rot, and to otherwise avoid offending squeamish dwarves. Eventually, go check out the subpage on [[/Stockpiles/]] for more information on fine-tuning these stockpiles for maximum efficiency. For now you can safely procrastinate on this and move on to the next section.

==Placing Furniture==
Once your furnishings are complete, you need to place them in rooms using the {{K|b}}uild command. Put the new {{k|c}}hairs and {{k|t}}ables in the dining room. If you like, you can add doors for aesthetics (they can be useful in case something starts rotting in your food stockpiles). If you created chests and cabinets, you can add them to each room if you want, but it is not urgent now.

==Meeting Hall==
Use {{K|q}} on one of the tables you just placed in the dining room, define the area as a {{k|r}}oom, and configure it to be a meeting {{k|h}}all. This will cause idle dwarves to hang around in the dining hall. You want idlers in a central location, close to where you will be placing your emergency drawbridge levers. You should probably remove the temporary meeting area (and any other meeting areas that you created earlier) with {{K|i}}-{{k|x}}.

==Checking Supplies==
{{TipBox2|float=right|titlebg=#a00|Hostile Wilds|Before turning on either hunting or fishing, examine the {{K|u}}nits screen to see if there are any dangerous critters your hunters/fishers need worry about. With hunting especially, you may need to check this screen frequently.}}
Use the {{K|z}} ([[status]]) screen to check your stock levels. How much food and booze do you have left? You only have unprepared food at this point, and the booze you brought with you, but soon you will be making more. If you are running low on food, you can designate gathering some [[shrub|outdoor plants]], [[Status#Animal_Status_Screen|slaughter]] some animals, turn on [[fishing]], or turn on [[hunting]] to tide you over for a bit. Hunting and slaughtering animals both require a butcher's shop.

==Brewing and Cooking==
Once your first crop of plump helmets starts to come in, you will want to start [[brewing]] as a [[repeat]]ing task. Also, now would be a good time to start [[cooking]] actual meals rather than forcing your dwarves to eat raw food. Cooking [[Cooking#Recipes|easy meals]] will train dwarves faster, but they may be happier with [[Cooking#Recipes|lavish meals]]. So, you might want to cook easy ones until your cook or cooks skill up to a certain point then have them start making lavish meals. Prepared food is cooked from two (easy), three (fine), or four (lavish) raw food/alcohol ingredients. Each prepared food item will be called a 'something' (for instance, a specific animal meat) "biscuit", "stew", or "roast" depending on the lavishness of the meal.

{{TipBox2|float=right|titlebg=#0a0|Conserving Resources|Some things absolutely require wood (like beds and charcoal), but others can be made out of more common materials like stone. For this reason it's best, especially in the beginning, to make everything that you can out of stone. For example, you could make wood chests and barrels, but stone coffers and rock pots would let you save wood for things that require it and help you rid yourself of all that stone. And if you decide you want solid gold chests or something later when you have more resources, you can always throw out the rock coffers.}}
Speaking of booze, in order to keep the booze flowing, you will need to create some [[barrel]]s, or some stone [[pot]]s. Your dwarves should have emptied a few barrels by now to get you started, but you will definitely need more. A ''lot'' more. If you have an abundance of trees, then you can designate some more for cutting, and have your carpenter make a bunch of wooden barrels, but it may be more prudent to make a [[Craftsdwarf's workshop]], make sure someone has the [[Stonecrafting]] labor enabled, and build a bunch of rock pots. (Rock pots are essentially barrels made of rock.) And don't worry that you've made too many; you almost can't get enough of them. Keep checking your food and drink stock levels on the {{K|z}} screen periodically. While cooked food (properly stockpiled) and alcohol don't spoil, there is really no need to stock 2,000 units of dwarven wine at this point. Ten times the number of drinks and meals as you have dwarves is more than enough. If you start running out of food or drinks, designate some wild plants for harvesting, [[Status#Animal_Status_Screen|slaughter]] some of your animals, start hunting or fishing, or start more farms. (Actually, now would be a fine time to make another 3x3 farm. Set it to produce [[sweet pod]]s in the spring and summer, [[cave wheat]] or [[pig tail]]s (your choice) in the fall (autumn), and [[plump helmet]]s in the winter. Having multiple types of plants will give your dwarves more variety in their food and drink, keeping them from [[Thought|grumbling]].)

==Storage Space==
{{TipBox2|titlebg=#0a0|float=right|Advanced Stockpiling|Check out the [[/Stockpiles|Stockpiles]] sub-page for more information on fine-tuning your stockpiles, especially in the food production area. This is somewhat complicated and it can safely be skipped if you don't feel like tinkering with stockpiles right now.}}
You should probably start making some wooden '''[[Bin|bins]]''' to help you store more stuff in less space. You might not need them yet, but you certainly will later. Bins are somewhat like barrels/pots, but they can store things other than just food and drink. Bins will also reduce the amount of labor needed to [[haul]] things to your trade depot or other stockpiles. So designate some more trees to be chopped down and queue up some bins. As with barrels and pots, you almost can't have enough bins.

==Situational Awareness==
At this point you might already have lost one or two games. Understanding why that happened is the most important part to get better and avoid frustration. To do so, you should be aware of what situation your fortress is in at all times: Are there enemies on the map? Do your dwarves have enough food? How many dwarves do you have? What season is it?

Along with just loo{{K|k}}ing around periodically, there are 4 screens that can help you with these questions:

* The {{K|u}}nit screen with its various tabs. Keep an eye out for invaders, dangerous animals and so on
* The status screen ({{K|z}}) and its "stocks" subscreen ''(Remember to appoint a [[bookkeeper]] and set him to the highest accuracy)''. Pay attention to the current date and your supplies.
* {{K|a}}nnouncements, and
* Combat {{K|r}}eports

Check them periodically and you will be able to recognize problems earlier and avoid disasters better.

=Beyond a Minimal Fortress=

By now you should have your main entrance created, along with a farm, general-purpose stockpile, refuse pile (for trash), and [[trade depot]]. Somewhere you should have a mason's shop, a mechanic's shop, a carpenter's shop, and a jeweler's shop, surrounded by appropriate storage piles with garbage zone (for excess stone). You should also have a furnished dining area with kitchen, still, and food storage, and a residential area with furnished bedrooms and an office. You should have selected your administrators, and might even have an optional fishery, butcher's shop, craftsdwarf's workshop, or other stuff. At this point, you have all the components of a minimal but functional fortress! Your next steps will be to make it safer and better-protected, to set up your [[metal industry]], and later to prepare your [[military|militia]].

==Traps==
Start producing '''[[mechanism]]s''' at your [[mechanic's workshop]]. Queue up ten. After they are built, use them to create [[Trap#Stone-fall_Trap|stone fall traps]] using {{K|b}}-{{K|T}}. Be sure not to block access to your depot! Queue up some [[cage]]s, and more mechanisms, and use these to create some [[Trap#Cage_Trap|cage traps]] right after your stone traps. Cage traps are incredibly effective at stopping ambushers, but traps in general will not protect you from [[thief|thieves and kidnappers]] who will almost always bypass them. (To deal with these ambushers, see the next section on [[#Guard Animals|guard animals]]). Continue to fill up your entry hall with alternating rows of stone and cage traps as the parts become available. Ideally you want to have enough cage traps to take out most of the [[goblin]]s so your military will only have to mop up.

Note that traps will block wagons from reaching your trade depot (although pack animals will still arrive safely). A few ways to avoid this are shown below:

{|
|-
|<diagram>
[#1:1]^^^^^
[#2:1].....
.....
.....
[#1:1]^^^^^
</diagram>
|A simple strategy, most useful above ground where invaders can come from the sides – underground, this is less useful (invaders don't tend to emerge from the walls).
'''Legend:''' In this diagram and the one below, traps are blue {{DFtext|^|1:1}} (^) symbols, and the green {{DFtext|.|2:1}} and red {{DFtext|.|4}} (.) symbols represent the ground and cave floor.
|-
|<diagram fg="4:0">
░░░░░░░░░
░.......░
░.......░
░.......░
....[#1:1]^[#]....
....[#1:1]^[#]....
....[#1:1]^[#]....
░░░░░░░░░
</diagram>
|A more complex design, but also extremely effective (best used underground). The majority of invaders will choose to take the shortest path, directly through the traps. This can also be extended to make a wider group of traps of a longer safe route.

This is relatively easy to implement if you already have a 3-tile wide hallway – just dig a small loop off it and place traps in the old location.
|}

Note that this is only necessary when caravans can't get to your trade depot, because the hallway is filled with traps - if your trade depot is not behind a trap-lined hallway, you can safely make a hallway full of traps - citizens won't trigger traps.

If you place a trap somewhere you didn't mean to, remove it with {{k|t}}-{{k|x}} or {{k|q}}-{{k|x}}.

==Guard Animals==
Create one 1x1 [[pasture]] near the beginning of your entryway, in the middle tile, using {{K|i}}. Using the {{K|N}} key inside the zone interface, assign a [[dog]] or other non-grazing animal to it. This animal will spot thieves and raiders before they gain entrance to your fortress. Try to pick a disposable animal, as it ''will'' be slaughtered by the first ambush raiders. Ideally, don't assign female animals; you want them safe for [[Meat industry#Breeding|breeding]] (you should make sure to keep at least one male around for breeding as well).

==Drawbridge==
In case of an [[ambush]] or [[siege]], you will want to close up your fort, keeping the goblins out until your [[squad]]s have formed up and are in position. Therefore, you can build a [[Bridge|drawbridge]] ({{K|b}}-{{K|g}}) to seal off your entryway. Make sure to use {{K|w}}, {{K|a}}, {{K|d}}, or {{K|x}} to make it raise up in the right direction, which then forms a barrier to block enemy ranged units. If you don't get the orientation of the bridge correct, it will just retract (disappear) instead of raising up, allowing enemy ranged units to fire across.

Put the drawbridge between the trade depot and the hall-o-traps so you can lock things out of the fort. Build a lever ({{K|b}}-{{K|T}}-{{K|l}}) near your meeting area and [[Lever#Linking|link]] it to the drawbridge by using {{K|q}} on the lever. (This linking will require 3 [[mechanisms]] in total.)

==Metal Industry==
[[File:Quickstart-level-2-forge.png|thumb|right|Level -2: Forge and smelters with ore stockpile in the middle.]]
Now, below your first workshop level, dig out four more 5x5 rooms around the stairwell. Three of these will be [[smelter]]s ({{k-|b|e|s}}), and one a [[metalsmith's forge]] ({{k-|b|w|f}}). Designate stockpiles for {{K|b}}ars around the smelters and forge. The bar stockpiles will hold [[Fuel|coke and charcoal]] and metal [[bar]]s. You will probably need larger bar stockpiles, but you can dig out more space and expand them later. Also dig out some space and create a stockpile for [[ore]] somewhere nearby. To make an ore stockpile, designate a {{K|s}}tone stockpile, then use {{K|q}} to change the {{K|s}}ettings on it to forbid all types of stone other than ore. Finally, go to your general-purpose stockpile on the top level and use {{K|q}} to disable Bars. Stone should already be disabled on this stockpile, and if so, then ore is already disabled for it.

===Wood Burning===
Somewhere near your carpenter's shop, near your wood stockpile, dig out an area and build a [[wood furnace]] ({{k-|b|e|w}}). This is where you will create charcoal (see below) and ash (for making soap). Dwarf Fortress has two forms of carbon which are useful as [[fuel]] in the metal industry: ''charcoal'' (which is charred wood), and ''coke'' (refined coal). They are completely interchangeable. If your map has a lot of '''lignite''' or '''bituminous coal''', you can process that into coke, using charcoal to jump-start the process. If you don't find coal on your map, you'll need to either dig down to [[magma]] or make charcoal out of wood to run your forges and smelters, but don't worry about this yet. You need to do some digging around.

===Mining===
{{TipBox2|float=right|titlebg=#0a0|"I have struck what?"|New players who don't have a degree in geology usually find themselves confused as to what all these mineral names mean. In DF you'll never strike "iron ore" but you will strike [[magnetite]] or [[limonite]] which are [[ore]]s of [[iron]]. If you don't know that these things are ores of iron then it obviously won't occur to you to try to smelt iron. Note that ores usually look like {{Raw Tile|£|6:7:1}} before they are mined and {{Raw Tile|*|6:1}} after, though the colors will differ. See '''''[[The Non-Dwarf's Guide to Rock]]''''' to help you figure out exactly what you've found.}}
At this point you want to start looking for metal ore. You may have already found some while digging out rooms, in which case you can just mine into the walls of the rooms to get more ore. If you haven't found ore yet or you want to see what else you can find, you will need to dig [[Exploratory mining|exploratory tunnels]] looking for ores, minerals, and [[gem]]s. For now just start digging tunnels out from your stairwell or rooms in all directions and see what you run into. Note that digging into '''damp stone''' or '''warm stone''' is not recommended as those areas may be holding back water or lava which can flood your fort.

===Fuel===
Whether you find [[coal]] or not, you will need to burn wood into at least one unit of [[charcoal]]. If you find some coal ([[lignite]] or [[bituminous coal]]), start your [[smelter]]s out processing it into [[coke]] using your charcoal to get things started. From then out you can burn coke to make more coal into more coke and so on. Put these coke-making jobs on repeat. Only use one smelter to begin with, but you should be getting a group of [[Immigration|immigrants]] fairly soon, if you haven't already, and you can put them to work in the other smelters. Don't give up on finding coal right away. Dig around for a while and if you're starting to get impatient then burn some more wood into charcoal, smelt some ore, and make some [[weapon]]s. If you rely on charcoal for fuel then you'll be needing a ''lot'' of wood, so in that case dig out another room near the furnace and create a wood stockpile. You might also want to just remove a smelter, replace it with a [[wood furnace]], and create the new wood stockpile down in the smelting area. Finally, go designate more trees for chopping.

===Forging===
{{TipBox2|float=right|titlebg=#0a0|Alternative Energy|If you don't find coal then you will have to continue to burn wood into charcoal, or dig down to the bottom of the map and find the magma sea so you can power [[magma smelter]]s and [[magma forge]]s. Getting to magma can be difficult for various reasons that you will discover, so make sure you are ready for some trouble before you go that direction. Burning charcoal should work out okay in the short term.}}
Once you have smelted some ore to get metal bars, and have additional bars of either coal or charcoal, you can start forging metal items. Here are some suggestions on what to make first:
#'''[[Pick]]s''' - You may have only started out with one pick which limits the number of miners you have to one. By this point you are probably wishing you had more miners. Make a few picks and give some dwarves the mining labor once you get some immigrants. It doesn't matter what metal you use to make picks, at least when it comes to mining, so even copper is perfectly good.
#'''[[Weapon]]s''' - Picks actually make pretty good weapons, but there can be some issues equipping them because they're tied to the mining labor. You may want to make a few axes. They make good weapons, at least against most lightly armored opponents you're likely to encounter first, and can be used to chop trees. Start with 5 or so.
#'''[[Armor]]''' - You're going to want some armor. Start with mail shirts, helms, leggings, then gauntlets and boots. Start with 3 or so of each in the order listed, then make more later when your military grows. Also make some shields out of wood, unless you're swimming in metal (since the shield's material doesn't matter for defensive purposes). Once you have the essentials covered, you can include breastplates (but they take 3 bars of metal to make, and they don't cover as much of the torso and arms as a mail shirt).
An important thing to note is that mail shirts protect the upper leg as well as the torso and arms, and high boots protect the lower leg. As dwarves have no knees (at least in military terms), high boots and mail shirts are sufficient to protect your dwarves' legs.
[[Steel]] is the best normal metal to make armor and most weapons out of, but you will likely find that you want some arms before you can make steel. [[Iron]] is good, as is [[bronze]]. [[Copper]] is not ideal, but it still works and is better than no metal weapons/armor at all.

==Gemcutting and Trinkets==
You should have uncovered some [[gem]]s by now, so put your [[jeweler]] to work [[Gem cutter|cutting]] them. These will be used for [[Trading|trade]]. Only buy things that you need in the first year. [[Finished goods|Stone crafts]] produced by a craftsdwarf can make good trading goods as well. To get enough goods, you will need to dedicate a craftsdwarf's workshop and craftsdwarf to this task full-time, but you're very unlikely to ever run out of stone.

==Sticking to the Plan==
{{TipBox2|float=right|titlebg=#a00|Getting Distracted|Say one of your new immigrants turns out to be a legendary weaver. Should you plant some pig tails and create a loom for him? '''No!''' Put his legendary butt to work smelting metal or something that's part of your current industry even though he has no skill at it. Do not split your efforts yet. You can make use of his unique talents later when you can afford to diversify your industry.}}
Metalsmithing will be your primary economic activity, with cutting gems (and possibly making stone crafts) being used to give you some short-term [[wealth]] until the [[metal industry]] gets going. This means you will need miners, haulers, smiths and furnace operators. Unless a dwarf is doing something else vital to the proper functioning of your fort, such as training in the militia, making traps, cooking food, and so forth, they should be doing one of those four things.

==Wealth and Invasion==
{{TipBox2|float=right|titlebg=#a00|Crafting Invitations for Trouble|Creating too much wealth initially is a sure fire method of pulling down a goblin ambush that you are ill-equipped to deal with. Titans will also start attacking you should your wealth go over a certain amount. For this reason, spend no time smelting gold, smoothing, or engraving anything yet. Most of the wealth you create in the beginning should be the [[weapon|sharp pointy kind]].}}
You may have struck [[gold]] or some other valuable metal, and you may be tempted to put your furnaces and smiths to work creating valuable metal crafts. Don't do it! Until you have your militia formed and fully equipped with armor and weaponry, your smelters and forge should be doing nothing else but smelting cheaper materials like coal, iron, making pig iron and steel if possible, and making weapons and armor. Making [[steel]] will actually increase your wealth quite a bit, but at least you can stab and beat things to death with steel; you can't make weapons from gold.

=Military=

Your '''military''' is an important part of fortress defense. Unless you have totally cut yourself off from the outside world, then you will want at least some sort of military. Once you reach this point, you should hopefully have enough dwarves to start a small military training program. You will need at least 5 dwarves who aren't otherwise doing anything important. If you don't have any spare dwarves yet, or just don't want to mess with it yet, just skip to the next section and come back to this later. Don't wait too long to set up your military though; you especially will want soldiers before you reach a population of 80 dwarves. (You will find out why.) When you're ready to start up your military, see the [[Military quickstart]] guide.

= What Next? =

Congratulations! If you've made it this far then you have a self-sustaining fort going and can now start to branch out into whatever you are interested in exploring. Expect some goblin invasions, forgotten beasts, titans, dragons, giants, and other creatures to interrupt your activities at various points. This is part of the [[fun]].

Here are some things that people almost always do eventually, though not necessarily in any particular order (these are somewhat essential):
*Build [[coffin]]s and a graveyard or [[tomb]]s for dead dwarves and pets
*Set up a [[Healthcare|hospital]]
*Build a [[well]]
*Start producing [[textile industry|clothing]] to replace [[wear|worn-out attire]]
*Build a [[jail]] for unruly dwarves
*Set up [[Scheduling#Alert_Levels|civilian alerts]] to get civilians to a safe area during ambushes and sieges

Here are some things that players often do as their population grows:
*[[Smoothing|Smooth]] and [[engraving|engrave]] walls and floors
*Produce [[Meat industry|Meat]], [[Egg production|eggs]], milk and [[Beekeeping industry|honey]]
*Continue to expand the [[military]]
*Explore new [[Industry|industries]]
*Dig down to the [[caverns]] and create a defended lower entrance with traps to defend the fort against the [[creatures|denizens]] below
*Enable [[Animal training]] for a dwarf and train some war animals
*Build a [[Mass pitting]] system to dispose of caged enemies
*Build above-ground [[construction]]s such as an archery tower or garden
*Create a [[statue|statue garden]] or [[zoo]]
*Farm in an [[Farming#Above-ground_farming|above-ground farm plot]]
*Dig down to [[magma]] and set up [[magma forge]]s and [[magma smelter]]s to avoid the need for fuel
*Build [[machine component]]s to pump magma and water
*Create more [[Trap design|elaborate traps]] such as magma and drowning chambers
*Try some [[stupid dwarf trick]]s

You may also want to just read over the [[Dwarf fortress mode|Fortress Mode Reference Guide]] and the many other very useful documents on the wiki to give you other ideas of what to do.

Keep in mind that how you play is not set in stone. Some people never defend, some start a [[Megaprojects|megaproject]] right after settling, some never dig and just build an above ground castle or town using logs. Some never smelt ore, some start smelting as soon as they arrive. Some make their home in the dangerous natural caverns. Some deal with invaders by flooding the map or isolating themselves completely. And that's not even considering the [[List of mods|mods]] and some of the crazier [[challenges]] that people have come up with. There's really no one "right" way to play DF.

= Feedback =
If you have any feedback on this guide, you can leave a message on the [[{{TALKPAGENAME}}|talk page]] for this article, or in [http://www.bay12forums.com/smf/index.php?topic=83452.0 this thread] on the forums.

{{Getting Started}}
{{Category|Fortress mode}}
{{Category|Quickstart guide}}

[[de:DF2012:Schnellstart]]
[[ru:Быстрый старт]]
[[zh:Quickstart guide]]

User talk:Xjtu-blacksmith

2022-11-29T01:04:47Z

Xjtu-blacksmith: /* Interwiki link support for Chinese wiki */

== Interwiki link support for Chinese wiki ==

Hi - in case you missed my response on [[Talk:Main Page]], you can use "zh:" for interwiki links to the Chinese wiki now. [https://dwarffortresswiki.org/index.php?title=Main_Page&diff=266849&oldid=266730 Here is an example.] —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:46, 28 November 2022 (UTC)
:Thanks!!! Terribly grateful to your kindness and laborious support. I'll add links on more pages little by little. [[User:Xjtu-blacksmith|xjtu-blacksmith 黑山雁]] ([[User talk:Xjtu-blacksmith|talk]]) 01:04, 29 November 2022 (UTC)

Plant token

2022-11-21T06:11:51Z

Xjtu-blacksmith: Add more information and update raw file list

{{Quality|Fine|11:40, 18 May 2015 (UTC)}}
{{av}}
{{Modding}}
The <code>[OBJECT:PLANT]</code> [[token]] defines the properties of [[plant]]s.
The default plants are stored in the <code>plant_standard.txt</code> file, while [[grass]]es are stored in <code>plant_grasses.txt</code>. The newly added plants are stored in <code>plant_crops.txt</code>, <code>plant_garden.txt</code> and <code>plant_new_trees.txt</code>.

__TOC__
{{clear}}

==Basic tokens==
These tokens are specified for all plants and define their most basic characteristics.

{| {{prettytable}}
|- style='background-color:#ddd'
! width="20%" | Token
! width="20%" | Arguments
! width="60%" | Description

|-
| {{text anchor|NAME}}
|
*name
| The singular form of the plant's name as seen in-game.

|-
| {{text anchor|NAME_PLURAL}}
|
*name
| The plural form of the plant's name as seen in-game.

|-
| {{text anchor|ADJ}}
|
*adjective
| The word or phrase used to describe items made from this plant.

|-
| {{text anchor|ALL_NAMES}}
|
*name
| Sets the NAME, NAME_PLURAL, and ADJ to the specified string.

|-
| {{text anchor|PREFSTRING}}
|
*reason
| What dwarves can like this object for (e.g. "Urist likes plump helmets for their rounded tops.")

|-
| {{text anchor|MATERIAL}}
|
*material_name
| Starts defining a new local plant material with the given name and '''no''' properties.

|-
| {{text anchor|USE_MATERIAL}}
|
*material_name
*old_material
| Starts defining a new local plant material with the given name and using the properties of another local plant material.

|-
| {{text anchor|USE_MATERIAL_TEMPLATE}}
|
*material_name
*template_name
| Starts defining a new local plant material with the given name and using the properties of the specified material template.

|-
| {{text anchor|BASIC_MAT}}
|
* [[Material token|material]]
| Sets the basic material of the plant. According to Toady, you can use other materials (for instance, iron) but the game may hiccup on plants that aren't structurally plants. For crops, said material should have [STRUCTURAL_PLANT_MAT] to permit proper stockpiling. Generally, this should be "LOCAL_PLANT_MAT:material_name", using a material defined using MATERIAL, USE_MATERIAL, or USE_MATERIAL_TEMPLATE.
|}

==Environment tokens==
These tokens, also applicable to all plants, specify where the plants grow.

{| {{prettytable}}
|- style='background-color:#ddd'
! width="20%" | Token
! width="20%" | Arguments
! width="60%" | Description

|-
| {{text anchor|UNDERGROUND_DEPTH}}
|
*minimum
*maximum
| Designates the highest and lowest cavern levels that the plant can appear in if its [[biome token|biome]] is subterranean. Dwarven civilizations will only export (via the embark screen or caravans) things that are available at depth 1. Defaults to 0:0 (surface only).

|-
| {{text anchor|GOOD}}
|
| Restricts the plant to growing in Good regions. Cannot be combined with [EVIL].

|-
| {{text anchor|EVIL}}
|
| Restricts the plant to growing in Evil regions. Cannot be combined with [GOOD].

|-
| {{text anchor|SAVAGE}}
|
| Restricts the plant to growing in Savage regions (regardless of alignment).

|-
| {{text anchor|FREQUENCY}}
|
*freq (0-100)
| How frequently this plant is generated in a particular area. Defaults to 50. Plants with valid [[biome token]]s and [FREQUENCY:0] will not grow in the wild, but will still be available for entity use and farm plots.

|-
| {{text anchor|WET}}
|
| Restricts the plant to grow near natural water features. A plant with [WET] may be very common or very rare in an area, depending on how many water features that area has. Note that they will not grow next to dwarf-filled channels, since it explicitly checks if the tile type is "River", "River Slope", "River Source", "Waterfall" (used back in 40d for underground rivers), "Brook", "Murky Pool", or "Murky Pool Slope".

|-
| {{text anchor|DRY}}
|
| Allows the plant to grow away from water features.

|-
| {{text anchor|BIOME}}
|
*biome
| What [[biome token|biome]] this plant appears in.

|}

==Growth tokens==
These tokens are used for all plants and specify growths growing on a plant.

Edible or otherwise usable growths should have [STOCKPILE_PLANT_GROWTH] in their [[material definition token|material definitions]] for proper stockpiling. This also lets them be collected from plant gathering and farming jobs.

{| {{prettytable}}
|- style='background-color:#ddd'
! width="20%" | Token
! width="20%" | Arguments
! width="60%" | Description

|-
| {{text anchor|GROWTH}}
|
*name
| Defines a plant growth. Takes the below tokens as arguments.

|-
| {{text anchor|GROWTH_NAME}}
|
*singular
*plural (STP for standard plural)
| The name of a plant growth.

|-
| {{text anchor|GROWTH_ITEM}}
|
* [[item token]]
* [[material token]]
| Specifies what item this growth is and what it is made of. Generally, the item type should be PLANT_GROWTH:NONE.

|-
| {{text anchor|GROWTH_HOST_TILE}}
|
*plant part
| Specifies on which part of the plant or tree the growth appears, usually for multi-tile [[tree]]s. Valid tokens are:
*TWIGS
*BRANCHES_AND_TWIGS / LIGHT_BRANCHES_AND_TWIGS
*BRANCHES / LIGHT_BRANCHES
*ALL_BRANCHES_AND_TWIGS
*HEAVY_BRANCHES / DIRECTED_BRANCHES
*HEAVY_BRANCHES_AND_TRUNK / DIRECTED_BRANCHES_AND_TRUNK
*TRUNK
*ROOTS
*CAP
*SAPLING

|-
| {{text anchor|GROWTH_TRUNK_HEIGHT_PERC}}
|
*integer:integer
|

|-
| {{text anchor|GROWTH_DENSITY}}
|
*integer
| Currently has no effect.

|-
| {{text anchor|GROWTH_TIMING}}
|
*[[time]] start:end (0-403200)
| Specifies at which part of the year the growth appears. Default is all year round.

A single growth can only have one GROWTH_TIMING tag. If multiple are declared, the last one will be used. To make a growth appear multiple times during the year, you need to create a different growth for every GROWTH_TIMING interval. By using the same material for all of the duplicate growths, all of them will be stockpiled together and be eligible for the same reactions. Edible/brewable growths will have separate entries in the kitchen menu, though.

There is no known way to declare a growth timing that lasts from winter into spring. Including numbers below 0 or above 403200 in the range will make the growth available at all times, as though you hadn't defined a growth timing at all. So will including a range for which the start time is later than the end time.

This has no effect on farmed growths; all eligible growths that have [STOCKPILE_PLANT_GROWTH] in their materials will be harvested, regardless of if they are currently within their growth timing or not.

|-
| {{text anchor|GROWTH_PRINT}}
|
*overworld tile
*item tile
*color
*time (0-403200) start:end, ALL, or NONE
*priority
| Specifies the appearance of the growth. Can be specified more than once, for example for autumn leaves. Transitions between different timing periods will happen gradually over the course of 2000 ticks.

The GROWTH_PRINT tile will only be displayed when the growth in question is actually present, even if its timing parameter is ALL.

|-
| {{text anchor|GROWTH_HAS_SEED}}
|
| The growth drops a seed if eaten raw.

|-
| {{text anchor|GROWTH_DROPS_OFF}}
|
| Growths drop from the plant, producing a cloud of items which fall on the ground, which [[herbalist]]s can collect.
|-
| {{text anchor|GROWTH_DROPS_OFF_NO_CLOUD}}
|
| Growths drop collectable items from the plant without producing item clouds.

|}

==Tree tokens==
These tokens are used only for trees.

{| {{prettytable}}
|- style='background-color:#ddd'
! width="20%" | Token
! width="20%" | Arguments
! width="60%" | Description

|-
| {{text anchor|TREE}}
|
* [[Material token|material]] or NONE
| Makes the plant into a [[tree]]. Cutting down the tree will yield logs made of this material. Setting the material to NONE will give no wood from this tree.

|-
| {{text anchor|TRUNK_NAME}}
|
*name
| What the trunk of the tree is named.

|-
| {{text anchor|MAX_TRUNK_HEIGHT}}
|
*1-8
| The maximum z-level height of a mature tree's trunk, starting from about two z-levels above ground and going up.

|-
| {{text anchor|MAX_TRUNK_DIAMETER}}
|
*1-3
| Upper limit of trunk thickness, in tiles. Counted separately for all branching trunks. Has a geometric effect on log yield.

|-
| {{text anchor|TRUNK_PERIOD}}
|
*integer
| The number of years the trunk takes to grow one Z-level upward.

|-
| {{text anchor|TRUNK_WIDTH_PERIOD}}
|
*integer
| The number of years the trunk takes to grow another tile wider.

|-
| {{text anchor|LIGHT_BRANCHES_NAME}}
|
*name
| What thin branches of the tree are named.

|-
| {{text anchor|BRANCH_DENSITY}} / {{text anchor|LIGHT_BRANCHES_DENSITY}}
|
*integer
| How dense the branches grow on this tree.

|-
| {{text anchor|BRANCH_RADIUS}} / {{text anchor|LIGHT_BRANCH_RADIUS}}
|
*integer
| The radius to which branches can reach. Appears to never reach further than seven tiles from the centre. Does not depend on the trunk branching amount or where trunks are. The values used in the game go from 0-3. Higher values than that can cause crashes. {{bug|10419}}

|-
| {{text anchor|HEAVY_BRANCHES_NAME}} / {{text anchor|DIRECTED_BRANCHES_NAME}}
|
*name
| What thick branches of the tree are named.

|-
| {{text anchor|HEAVY_BRANCH_DENSITY}} / {{text anchor|DIRECTED_BRANCH_DENSITY}}
|
*integer
| Similar to [[Plant_token#BRANCH_DENSITY|BRANCH_DENSITY]] for thick branches. Values outside 0-3 can cause crashes. {{bug|10419}}

|-
| {{text anchor|HEAVY_BRANCH_RADIUS}} / {{text anchor|DIRECTED_BRANCH_RADIUS}}
|
*integer
| Similar as [[Plant_token#BRANCH_RADIUS|BRANCH_DENSITY]] for thick branches.

|-
| {{text anchor|TRUNK_BRANCHING}}
|
*integer
| How much the trunk branches out. 0 makes the trunk straight.

|-
| {{text anchor|ROOT_NAME}} / {{text anchor|ROOTS_NAME}}
|
*name
| What the roots of the tree are named.

|-
| {{text anchor|ROOT_DENSITY}}
|
*integer
| Density of the root growth.

|-
| {{text anchor|ROOT_RADIUS}}
|
*integer
| How wide the roots reach out.

|-
| {{text anchor|TWIGS_NAME}}
|
*name
| What the twigs of the tree are named.

|-
| {{text anchor|TWIGS_SIDE_BRANCHES}}
|
*boolean (0 or 1)
| Twigs appear on the side of branches. Defaults to 1.

|-
| {{text anchor|TWIGS_ABOVE_BRANCHES}}
|
*boolean (0 or 1)
| Twigs appear above branches. Defaults to 1.

|-
| {{text anchor|TWIGS_BELOW_BRANCHES}}
|
*boolean (0 or 1)
| Twigs appear below branches. Defaults to 0.

|-
| {{text anchor|TWIGS_SIDE_HEAVY_BRANCHES}}
|
*boolean (0 or 1)
| Twigs appear on the side of heavy branches. Defaults to 0.

|-
| {{text anchor|TWIGS_ABOVE_HEAVY_BRANCHES}}
|
*boolean (0 or 1)
| Twigs appear above heavy branches. Defaults to 0.

|-
| {{text anchor|TWIGS_BELOW_HEAVY_BRANCHES}}
|
*boolean (0 or 1)
| Twigs appear below heavy branches. Defaults to 0.

|-
| {{text anchor|TWIGS_SIDE_TRUNK}}
|
*boolean (0 or 1)
| Twigs appear on the side of the trunk. Defaults to 0.

|-
| {{text anchor|TWIGS_ABOVE_TRUNK}}
|
*boolean (0 or 1)
| Twigs appear above the trunk. Defaults to 0.

|-
| {{text anchor|TWIGS_BELOW_TRUNK}}
|
*boolean (0 or 1)
| Twigs appear below the trunk. Defaults to 0.

|-
| {{text anchor|TREE_HAS_MUSHROOM_CAP}}
|
| The tree has a rounded cap-hood like a giant mushroom. This severely stunts a tree's maximum height - see the [http://www.bay12games.com/dwarves/mantisbt/view.php?id=7313#c26413 bug report.]

|-
| {{text anchor|CAP_NAME}}
|
*name
| What this mushroom-cap is called. Only makes sense with TREE_HAS_MUSHROOM_CAP.

|-
| {{text anchor|CAP_PERIOD}}
|
*integer
| Similar to the other PERIOD tags, influences the rate of the mushroom cap growth. Only makes sense with TREE_HAS_MUSHROOM_CAP.

|-
| {{text anchor|CAP_RADIUS}}
|
*integer
| The radius of a mushroom cap. Only makes sense with TREE_HAS_MUSHROOM_CAP.

|-
| {{text anchor|STANDARD_TILE_NAMES}}
|
| Uses the standard names for the tree components (roots, trunk, branches, etc.)

|-
| {{text anchor|TREE_TILE}}
|
*tile
| The tile used for trees of this type on the world map. Defaults to 24 (↑).

|-
| {{text anchor|DEAD_TREE_TILE}}
|
*tile
| The tile used for (un)dead trees and deciduous trees (generally in winter) of this type. Defaults to 198 (╞).

|-
| {{text anchor|SAPLING_TILE}}
|
*tile
| The tile used for saplings of this tree. Defaults to 231 (τ).

|-
| {{text anchor|DEAD_SAPLING_TILE}}
|
*tile
| The tile used for dead saplings of this tree. Defaults to 231 (τ).

|-
| {{text anchor|TREE_COLOR}}
|
*foreground
*background
*bright
| The [[color]] of the tree on the map. Defaults to 2:0:0 (dark green).

|-
| {{text anchor|DEAD_TREE_COLOR}}
|
*foreground
*background
*bright
| The [[color]] of the tree on the map when (un)dead. Defaults to 0:0:1 (dark gray).

|-
| {{text anchor|SAPLING_COLOR}}
|
*foreground
*background
*bright
| The [[color]] of saplings of this tree. Defaults to 2:0:0 (dark green).

|-
| {{text anchor|DEAD_SAPLING_COLOR}}
|
*foreground
*background
*bright
| The [[color]] of dead saplings of this tree. Defaults to 0:0:1 (dark gray).

|-
| {{text anchor|SAPLING_DROWN_LEVEL}}
|
*depth
| The sapling of this tree will drown once the water on its tile reaches this level. Defaults to 4.

|-
| {{text anchor|TREE_DROWN_LEVEL}}
|
*depth
| The water depth at which this tree will drown. Exact behavior is unknown. Defaults to 7.

|-
| {{text anchor|SAPLING}}
|
| Makes young versions of the tree be called "[tree name] sapling"; otherwise, they are called "young [tree name]".

|}

==Shrub tokens==
These tokens are used for non-grass, non-tree plants.

{| {{prettytable}}
|- style='background-color:#ddd'
! width="20%" | Token
! width="20%" | Arguments
! width="60%" | Description

|-
| {{text anchor|SPRING}}, {{text anchor|SUMMER}}, {{text anchor|AUTUMN}}, {{text anchor|WINTER}}
|
| Allows the plant to grow in farm plots during the given season.

If the plant is a surface plant, allows it to grow in the wild during this season; wild surface plants without this token will disappear at the beginning of the season. Underground plants grow wild in all seasons, regardless of their season tokens.

|-
| {{text anchor|GROWDUR}}
|
*time
| How long the plant takes to grow to harvest in a farm plot. Unit hundreds of ticks, See [[Time]]. There are 1008 GROWDUR units in a season. Defaults to 300.

|-
| {{text anchor|VALUE}}
|
*value
| Has no known effect. Previously set the value of the harvested plant.

|-
| {{text anchor|PICKED_TILE}}
|
*tile
| The tile used when the plant is harvested whole, or is ready to be picked from a farm plot. May either be a cp437 tile number, or a character between single quotes. See [[Main:character table|character table]]. Defaults to 231 (τ).

|-
| {{text anchor|DEAD_PICKED_TILE}}
|
*tile
| The tile used when a plant harvested whole has wilted. Defaults to 169 (⌐).

|-
| {{text anchor|SHRUB_TILE}}
|
*tile
| The tile used to represent this plant when it is wild, alive, and has no growths. Defaults to 34 (").

|-
| {{text anchor|DEAD_SHRUB_TILE}}
|
*tile
| The tile used to represent this plant when it is dead in the wild. Defaults to 34 (").

|-
| {{text anchor|CLUSTERSIZE}}
|
*size
| The maximum stack size collected when gathered via herbalism (possibly also from farm plots?). Defaults to 5.

|-
| {{text anchor|PICKED_COLOR}}
|
*foreground
*background
*bright
| The color of the plant when it has been picked whole, or when it is ready for harvest in a farm plot. Defaults to 2:0:0 (dark green).

|-
| {{text anchor|DEAD_PICKED_COLOR}}
|
*foreground
*background
*bright
| The [[color]] of the plant when it has been picked whole, but has wilted. Defaults to 0:0:1 (dark gray).

|-
| {{text anchor|SHRUB_COLOR}}
|
*foreground
*background
*bright
| The [[color]] of the plant when it is alive, wild, and has no growths. Defaults to 2:0:0 (dark green).

|-
| {{text anchor|DEAD_SHRUB_COLOR}}
|
*foreground
*background
*bright
|The [[color]] of the plant when it is dead in the wild. Defaults to 6:0:0 (brown).

|-
| {{text anchor|SHRUB_DROWN_LEVEL}}
|
*depth
| The shrub will drown once the water on its tile reaches this level. Defaults to 4.

|-
| {{text anchor|DRINK}}
|
* [[Material token|material]]
| Names a [[alcohol|drink]] made from the plant, allowing it to be used in entity resources. Previously also permitted brewing the plant into [[alcohol]] made of this material. Now, a MATERIAL_REACTION_PRODUCT of type DRINK_MAT should be used on the proper plant material.

|-
| {{text anchor|MILL}}
|
* [[Material token|material]]
| Permits milling the plant at a [[quern]] or [[millstone]] into a powder made of this material and allows its use in entity resources. Said material should have [POWDER_MISC_PLANT] to permit proper stockpiling.

|-
| {{text anchor|THREAD}}
|
* [[Material token|material]]
| Permits processing the plant at a [[farmer's workshop]] to yield threads made of this material and allows its use in entity resources. Said material should have [THREAD_PLANT] to permit proper stockpiling.

|-
| {{text anchor|SEED}}
|
*name
*name_plural
*foreground
*background
*bright
*[[Material token|material]]
| Causes the plant to yield plantable seeds made of this material and having these properties. Said material should have [SEED_MAT] to permit proper stockpiling.

|-
| {{text anchor|EXTRACT_STILL_VIAL}}
|
* [[Material token|material]]
| Permits processing the plant into a [[vial]] at a [[still]] to yield extract made of this material. Said material should have [EXTRACT_STORAGE:FLASK].

|-
| {{text anchor|EXTRACT_VIAL}}
|
*[[Material token|material]]
| Permits processing the plant into a [[vial]] at a [[farmer's workshop]] to yield extract made of this material. Said material should have [EXTRACT_STORAGE:FLASK].

|-
| {{text anchor|EXTRACT_BARREL}}
|
* [[Material token|material]]
| Permits processing the plant into a [[barrel]] at a [[farmer's workshop]] to yield extract made of this material. Said material should have [EXTRACT_STORAGE:BARREL].

|}

==Grass tokens==
These tokens are used only for [[grass]]es.

{| {{prettytable}}
|- style='background-color:#ddd'
! width="20%" | Token
! width="20%" | Arguments
! width="60%" | Description

|-
| {{text anchor|GRASS}}
|
| Makes the plant behave as a type of grass. This allows animals to graze on it, and prevents it and its growths from being picked by herbalists. (Grass growths can still be picked in adventure mode, however.)

|-
| {{text anchor|GRASS_TILES}}
|
*tile
*tile
*tile
*tile
| Specifies the 4 tiles used to represent grass of this type. If VARIED_GROUND_TILES is disabled in d_init.txt, these are seemingly ignored. Defaults to 46:44:96:39 (.,`').

|-
| {{text anchor|ALT_PERIOD}}
|
*period
*offset
| How often the grass switches between its main tiles and alternate tiles. The "period" value determines how quickly (in frames) the grass animates, and the "offset" value specifies how much of that time is spent displaying the alternate tiles. If the "offset" value is greater than or equal to the "period" value, the grass will only display using the alternate tiles.{{verify}} Defaults to 0:0.

|-
| {{text anchor|ALT_GRASS_TILES}}
|
*tile
*tile
*tile
*tile
| When used with ALT_PERIOD, specifies the 4 alternate tiles used to represent grass of this type. Defaults to 46:44:96:39 (.,`'). Dead grass does not animate.

|-
| {{text anchor|GRASS_COLORS}}
|
*color 1 (fore:back:bright)
*color 2 (fore:back:bright)
*dry color (fore:back:bright)
*dead color (fore:back:bright)
| Specifies the color of this grass. Defaults to 2:0:1:2:0:0:6:0:1:6:0:0 (light green, dark green, yellow, brown).
|}

{{Category|Modding}}
{{Category|Tokens}}
[[ru:Plant token]]

User talk:Lethosor

2022-11-11T01:20:03Z

Xjtu-blacksmith: /* Request for interwiki (inter-language) link to Chinese wiki */ new section

{{User:Lethosor/header}}
{{Archive|
* [[/archive1|Archive 1 (February-August 2013)]]
* [[/archive2|Archive 2 (Sept. 2013 - May 2014)]]
}}
__TOC__
{{clear}}

==Bot requests==
<div style="" class="plainlinks">
[{{fullurl:User talk:Lethosor|action=edit&section=1&editintro={{urlencode:User:Lethosor/edit intro/bot}}}} '''Add a new request''']
</div>

=== Underpopulated categories ===

Many categories in the DF2014 namespace don't list some of the pages that have the category link. An empty edit on a page (well, any edit) will correct this, but only for that page. This sounds like a job for a bot. [[User:VengefulDonut|VengefulDonut]] ([[User talk:VengefulDonut|talk]]) 19:00, 21 July 2014 (UTC)
:I'm pretty sure that's a cache problem, so I'll try rebuilding link tables on the server side and see if that helps (it would probably be a lot faster than sending a bot around to null-edit every page). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:41, 21 July 2014 (UTC)
::This has been fixed. The problem was that the server that actually runs the job queue was still using the old configuration (without the DF2014 namespace). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:17, 8 November 2014 (UTC)

== Diagram ==

Take a look over [[DF talk:diagram|here]]. [[User:VengefulDonut|VengefulDonut]] ([[User talk:VengefulDonut|talk]]) 15:45, 26 July 2014 (UTC)

== Ceramic Industry page assistance. ==

(Message here) --[[User:DorfyDave|DorfyDave]] ([[User talk:DorfyDave|talk]]) 04:16, 24 August 2014 (UTC)
Thanks for the help with the ceramic industry stuff.

I see what you are doing with the thumbnail workflows on other pages, so if you would rather it be small and let the reader expand it, that would be fine.

I was thinking that the pages looked better with the intro section before the regular content, keeping it separate from the auto TOC / Header listed content, but if you prefer that everything follow the layered header format, that's fine.

:My primary concern was the wrapping caused by inserting the full-size flowchart next to a section. It looks like you've addressed that by splitting up the flowchart, which looks good to me. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 15:48, 25 August 2014 (UTC)

== Removing/restoring [[Main:Fruit]] ==

Not that I am protesting it, but why exactly did you remove and then restore the [[Main:Fruit]] page? Because to me, all that happened now is that the creation entry on the page's history is gone, which isn't really anything notable either.
--{{User:Latias1290/Sig/src|13:03|August 26, 2014}} 13:03, 26 August 2014 (UTC)
:I deleted it at first because I didn't realize AutoRedirect wasn't handling section redirects properly, then restored it when I noticed it was broken. That article's [http://dwarffortresswiki.org/index.php?title=Fruit&action=history history] still shows your revision, so I'm not sure what you mean - is it missing from [[Special:RecentChanges]]? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 13:07, 26 August 2014 (UTC)
::The creation entry I was talking about was actually the first entry, and the entry that is now the only one was the second before you removed it. When I created the page I first had it directly redirect to [[cv:Tree#Fruit]], which after testing didn't work. I usually save the page when the preview doesn't show a red link and the link is correct, and after saving I test it, This time, however, the link in the preview was blue and correct, but actually following the redirect only led to [[cv:Tree]] instead of [[cv:Tree#Fruit]]. The entry you are seeing now is the result of fixing this by making it into a double redirect through [[cv:Fruit]].
:::It looks to me like your first edit was to [[DF2014:Fruit]] - when [[Main:Fruit]] didn't exist, it would have automatically redirected to [[DF2014:Fruit]], so it might have appeared to exist when it didn't. (The problem here is that I made AutoRedirect follow redirect chains internally, since Mediawiki's maximum-redirect setting is buggy, so a nonexistent [[Main:Fruit]] would actually redirect to what [[cv:Fruit]] redirects to - the problem is that it ignores sections at the moment, so section redirects will need to be manually created until I can fix that.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 13:18, 26 August 2014 (UTC)

== settings-manager ==

I don't know where to put it because I don't have a github account and don't know if you have a personal thread for your scripts like the others, but couldn't you add a TEXT mode entry in line 116 of your settings-manager script?
--[[Special:Contributions/78.250.50.116|78.250.50.116]] 04:40, 18 September 2014 (UTC)
:I originally excluded it because it only works on Linux, but I'll add it back for Linux users. Thanks! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:44, 18 September 2014 (UTC)

== Interesting glitch with redirects ==

I went to see what "Candy" was by going to a page named "Candy", and I found out that it meant Adamantine. But I saw that I got redirected to [[v0.34:Adamantine]], which shouldn't happen seeing as mainspace redirects should always go to the cv namespace. So I went back to fix it, and I saw that [[main:Candy]] redirected to [[main:Adamantine]], so I went there to fix it. But that page redirected properly to [[DF2014:Adamantine]]. This is where it gets interesting.

So when you go to [[main:Candy]], you get redirected to [[main:Adamantine]] which in turn redirects to [[DF2014:Adamantine]]. But - for some reason, you don't get sent to [[DF2014:Adamantine]], but to [[v0.34:Adamantine]]. Going to [[main:Adamantine]] in the first place redirects you to [[DF2014:Adamantine]] properly.

I have no idea how this happens, and since you maintain most of the wiki, I think you would be the right person to tell this to.
--{{User:Latias1290/Sig/src|13:42|November 01, 2014}} 13:42, 1 November 2014 (UTC)

:My best guess is that the [[Main:Candy]] redirect is cached and still points to [[v0.34:Adamantine]]. Our [[DF:REDIR|new policy]] is to keep redirects in versioned namespaces, so feel free to tag any broken redirects (in the main namespace) that you find with {{tl|bad redirect}} and I'll delete them. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 14:48, 1 November 2014 (UTC)

:I just saw a redlink on the exploratory tunnels page(redlink to [[DF2014:Break]]) and went to create it, when I discovered that the pages for Break existed for 23a and 40d, but not for 34.11 and 40.x. I went to check those to import content, and they turned out to be redirects. So I just redirected [[DF2014:Break]] to [[DF2014:On break]] and when I went to create additional redirects in the mainspace, I found that [[main:Break]] redirects to [[main:On break]] which redirects to [[cv:On break]]. But, again, it ultimately did not redirect to cv:On break but to v0.34:Break. I think that if it is indeed a cache problem we should rebuild redirect caches. {{User:Latias1290/Sig/src|12:08|November 02, 2014}}
:PS: Or just batch-delete all of this kind of redirects. {{User:Latias1290/Sig/src|12:09|November 02, 2014}}
:I don't like "bumping" this message like this, but since it's rather annoying, and ten days have been since I told you, almost all of these redirects are broken. Take a look at [[main:Aluminium]] for example, it goes to its 34.11 page. I think that it goes like this; when a page in the mainspace redirects to another page in the mainspace, which in turn goes to a cv space page, it goes to 0.34 instead of the current version. Going to the main>cv redirect initially does not cause this glitch. {{User:Latias1290/Sig/src|12:46|November 12, 2014}}
::It would be helpful if you could add {{tl|bad redirect}} to those pages (preferably before the "#REDIRECT" line) so I can delete them. I'm not sure what's causing the problem, but I'll see if I can override broken redirects with the AutoRedirect extension as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:18, 12 November 2014 (UTC)

== Migrated citations ==

As seen on [[DF2014:Dragonfire]], migrated citations can become confused, pointing to non-existent pages. I'm not sure how to fix it, but in general citations shouldn't automatically change what they are pointing at.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 18:26, 14 November 2014 (UTC)

== <nowiki>{{ArticleVersion}}</nowiki> bug ==

I just found another very strange bug regarding the articleversion template. The more research I did on it, the weirder it got. The bug is that when you are not logged in, and you visit a non-DF2014 page with an av template, the latest version shows as v0.40.16 instead of v0.40.18. {{User:Latias1290/Sig/src|10:17|November 25, 2014}}
PS: This bug does not replicate when you are logged in. {{User:Latias1290/Sig/src|10:19|November 25, 2014}}
:This is because pages are cached for logged-out users. You can refresh individual pages by adding "?action=purge" to the end of the URL (or possibly by null-editing them). It appears to occur in DF2014 pages as well - [[DF2014:Hemp]], for example. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:49, 25 November 2014 (UTC)

== Lost password request ==

I've forgotten my password. User: Bumber

:You don't seem to have an email address associated with your account. I sent a message to Bumber on the forums, assuming that's you. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:24, 30 April 2016 (UTC)

Thanks.

== Redirects ==

Thank you for the correction. I felt I might be doing it wrong but couldn't find an example of it done right to copy. Now I know. :) [[User:Volatar|Volatar]] ([[User talk:Volatar|talk]]) 16:02, 30 July 2015 (UTC)

== v0.42.05 raws update ==

Just a friendly reminder that the wiki raws need updated to pick up the [http://dwarffortresswiki.org/index.php?title=Dwarf_Fortress_Wiki:Page_request/List&diff=222917&oldid=222913 new critters in v0.42.05]. It would also be nice if your bot could auto-create the new creature pages so we don't end up with [[back bear man]] and the like.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 23:05, 2 February 2016 (UTC)

:Quietust updated the extension, but I'm having trouble deploying the changes for some reason (which Emily can hopefully figure out). I don't know if I'll have enough time this/next week to write a script to create the new creature pages - if not, Quietust might have something still laying around from 0.34/0.40. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:45, 6 February 2016 (UTC)

== Page move reminder ==

[[DF2014:Box]] to [[DF2014:Container]] please. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 23:01, 7 July 2016 (UTC)

:Done. It took me a second to figure out what the issue was - I'm surprised Mediawiki wouldn't let you move a page over another one that was just a redirect. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:21, 10 July 2016 (UTC)
::Thanks! [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:50, 11 July 2016 (UTC)

== v0.43.05 raws update ==

Just a friendly reminder that the wiki raws need updated to pick up the changes through v0.43.05.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:48, 2 August 2016 (UTC)

:Done. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:43, 22 August 2016 (UTC)

== Multiple redirects leads to incorrect namespace ==

Discussion here: [[Dwarf_Fortress_Wiki_talk:Centralized_Discussion#Solution_for_this]] [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 10:49, 21 November 2016 (UTC)

== Vandalism ==

We had an attack on August 3rd. [[Talk:Main Page (fix plz)]] ‎needs moved back to Talk:Main Page, and the rest of [http://dwarffortresswiki.org/index.php/Special:Contributions/Etihand the vandal's handiwork] can just be deleted. I can't think of any legitimate reason a user would need to move Talk:Main Page, so it should probably be move-locked to prevent future hijacks.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 15:53, 7 August 2017 (UTC)

:It should be cleaned up now. Sorry for the delay there. [[Main Page]] was already move-protected, but apparently that didn't apply to the talk page, so both should be move-protected now too. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 13:29, 8 August 2017 (UTC)

== Sorry, I need a password reset ==

I just logged in, saw the post about passwords needing to be changed. (Feeling all smart since I just setup a password manager) I updated my password, only to realize I didn't save the new password correctly in the manager. I tried to reset it but the wiki had a note saying to contact you since it can't do outbound email right now.

My user name is [[Frobnic8]].

My most notable contribution here are the PDF versions of the old Bronzemurder illustration by Tim Denee: [[Bronzemurder]]

The files are still hosted at my website. To prove it's me, I've also left you a note at http://eldritch.org/erskin/temp/df_wiki.txt

Sorry for the hassle, but if you could set me a temporary password or send me a link to a password reset to the associated email address for the account, that'd be awesome.

Thanks!

--[[Special:Contributions/70.163.4.102|70.163.4.102]] 15:40, 30 October 2017 (UTC)

:Done —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:59, 1 November 2017 (UTC)

::Thanks! --[[User:Frobnic8|Frobnic8]] ([[User talk:Frobnic8|talk]]) 02:51, 1 November 2017 (UTC)

== Password reset ==

I could have sworn I did this already, but now there's no sign of my edit here. Dunno what happened to it. Can I please get a password reset for user Urist McDorf. I believe the email info associated is still good (j*y@y*m). Thanks. [[Special:Contributions/108.49.199.220|108.49.199.220]] 06:56, 1 November 2017 (UTC)

== Totally failed to make an account ==

Really think I did everything right.

The Captcha app you are using says it "shutdown" on 3-31-2018 so i'm wondering if that's the issue. – [[template:unsigned|unsigned]] comment by [[User:216.201.251.142|216.201.251.142]]

:Yeah, we know about it. Emi and Briess are working on some upgrades, and we'll try to upgrade the captcha once it's done. In the meantime, you can PM me on the forums (or email me at gmail.com) and I think I can set up an account for you. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 13:41, 13 April 2018 (UTC)

== Chemist Page Quality Rating ==

The quality rating of the [[chemist]] page is listed as *Superior*, despite being a stub. I can't even decrease the quality down to +Fine+ using the rating script.
I added the memory attribute as stated by Toady's recent FotF reply, and I'll insert the relevant [[topics]] for the skill, but there's probably a lot more work to be done.
--[[User:Bumber|Bumber]] ([[User talk:Bumber|talk]]) 06:39, 1 June 2018 (UTC)

:The "override" link [http://dwarffortresswiki.org/index.php?title=DF2014:Chemist&action=history worked for me]. You have to click on the rating at the top that you want to select, then submit. The calculated score is unreliable, to say the least. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 1 June 2018 (UTC)

::I couldn't figure out how the override worked and just assumed it was an admin thing. Didn't realize you had to click one of the quality options at the top. —[[User:Bumber|Bumber]] ([[User talk:Bumber|talk]]) 22:18, 3 June 2018 (UTC)

== [Proposition] - Wiki preview popups ==

Hi there.

I've read quite a bit of wikipedia these last few days (the real wikipedia website), and I've come to use their preview feature quite a few times.
In case you don't know, the preview is a little JS pop-up that shows an image and some text when you hover a link.
So, you get a rough idea of what the thing is, and you don't have to load the full page (you can still if you click the link).

This feature is not in DF wiki, and I was thinking maybe it could be, as it greatly increase readability (since you don't have to open a new page, read the first few lines, go back, and waste time figuring out where you were; for every topic you're unaware of).

I'm not sure whether I should ask you, or Briess or anyone, but since you've made quite some wiki Extensions, I'll ask anyway.

So, do you think it could be a viable idea to turn this feature on ?

Here's a mediawiki tutorial on how to set this up, just in case :
[https://www.mediawiki.org/wiki/Extension:Popups]

Cheers ! =D
- Spriggans
Aug, 17 2018

:It does sound useful, but it claims to require MediaWiki 1.25+, so it'll probably have to wait until we finish upgrading. There are instructions for 1.24 or earlier in the article, though - I'm not sure how far back "or earlier" includes. The two extensions it depends on, TextExtracts and PageImages, require 1.23+ and 1.25+ respectively, so it's unlikely that it'll work on our current (pre-upgrade) setup.
:(I am a good person to ask, by the way, and <nowiki>~~~~</nowiki> is probably a more convenient way to sign comments.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 15:14, 17 August 2018 (UTC)

== Aesthetically Pleasing Things ==

I know I posted this before but... do I have your permission to spice up some of the templates of tables? I could make some look better and "cleaner" than they do now. Also, are there any plans to change the default look of the wiki? I don't mean this in a nasty way, white with black text is pretty... generic. - [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 14:20, 4 June 2019 (UTC)

== Auto-Welcome ==

It looks like your bot is automatically welcoming editors. Unfortunately, due to the nature of rotating IP addresses, it appears your bot has [//www.dwarffortresswiki.org/index.php/Special:Contributions/LethosorBot welcomed one anonymous user] 7 times in the last 5 days. Perhaps it would be best to restrict auto-welcoming to non-IP users?--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 21:55, 16 June 2019 (UTC)
:Yeah, that's the AutoWelcomeUser extension (just set up to attribute edits to my bot). I definitely agree that it should be changed, and I'll look into it. Fun fact: this was enabled on the old wiki, but I had written it for a ''slightly'' newer Mediawiki version, so I had forgotten about it since it didn't actually work until we upgraded. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:37, 16 June 2019 (UTC)
:I think this is fixed now. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:57, 18 June 2019 (UTC)

== On "Acceptable" Commas ==

Regarding [//www.dwarffortresswiki.org/index.php?title=DF2014:World_generation&curid=32663&diff=245045&oldid=245044 this edit]:

Per the [//en.wikipedia.org/wiki/Wikipedia:Manual_of_Style Wikipedia Manual of Style] (referenced as [[Dwarf_Fortress_Wiki:Community_Portal#S|Rule S]]): "Where more than one style is acceptable under MoS, editors should not change an article from one of those styles to another without a good reason."

So, while that comma is indeed "acceptable" (or optional), editing to add that optional comma is not. I intentionally did not put a comma there when I added that sentence, and I believe my punctuational preference is at least as valid as ‎Silverwing235's.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 23:12, 17 June 2019 (UTC)

:I'm not convinced that comma is optional, but I didn't realize you had added that sentence (I thought it was part of the original quote from Toady before your changes, so I was mistakenly applying rule S there as well). Apologies, and it's your call as to what to do there. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:21, 17 June 2019 (UTC)

== Embark points ==

There's no page explaining embark points in-depth; can I make such a page? Or at least add it to the embark page? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:39, 21 June 2019 (UTC)
: I'd add it to the embark page since I'm not sure it warrants a separate page unless it's a ''lot'' of detail (i.e. more than the current embark page). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:43, 21 June 2019 (UTC)
:: With what I have planned, there's a ton of things I can go over which can fill a page. I can make a "workbench"/fake page and you can tell me if it's worthy or not. Also, is it possible to put things in "collapsable/expandable" tables to not badly stretch out pages? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 04:14, 22 June 2019 (UTC)
:: Sorry, one more thing. You know the "Urist likes [something] for their [something]."? Are these made up on the spot or is that info taken directly from somewhere? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 04:59, 22 June 2019 (UTC)
::: I'm not sure how much detail you can go into about just embark points, but sure, feel free to make a test page if you like and I can provide some input. I wouldn't put things in collapsible tables just because of page length, because pretty much no other page does that (except for some things that aren't really part of the content of a page, like nav boxes and raws). If you're referring to things like "Urist likes [creature]" from pages like [[DF2014:Cat]], those are generated from the raws. I'm not sure if that appears on any other types of pages. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:30, 23 June 2019 (UTC)

==Creature font==
Are you alright if I change the font of the letters in the creature list? Sorry to say this but that font is kinda ugly. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 01:40, 29 June 2019 (UTC)
:Are you talking about [[DF2014:Creature]] or something else? I personally think that page looks fine, but what does it look like on your end? It might be some cross-browser issue that we can try to sort out. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:56, 29 June 2019 (UTC)
::Yes I do mean that DF2014:Creature page. The font of the letters that resemble the creatures are this ugly "Times New Roman"-esque font that looks like an eyesore to me. It could be a much smoother looking font. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:55, 1 July 2019 (UTC)
:::I noticed the font looks ugly on Firefox and Edge but not in the Tor Browser. So yeah, there's a weird browser thing going on and I don't know how to fix things for specific browsers on wiki's... -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 20:45, 1 July 2019 (UTC)
::::I'm guessing you don't have the "Century" font installed, or accessible in those browsers for some reason. For reference, [https://i.imgur.com/wD6QMoG.png here] is what it looks like for me, definitely not Times. I'll see if it can be standardized. Does {{Raw Tile|c|6:0}} look ok to you? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:33, 1 July 2019 (UTC)
:::::At some point in the possibly-recent past, those letters looked the same for me as it did you, but one day it just changed to the uglier font. Also, it's impossible to use the "Upload newer version of this file" function, as that always gives weird errors: Could not read or write file "mwstore://local-backend/local-public/6/6c/Biome_evil.png" due to insufficient permissions or missing directories/containers. I'm assuming I don't have access to do that? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:07, 2 July 2019 (UTC)
::::::I figured out the setting that controlled the font, it's the "Allow pages to choose their own fonts, instead of your selections above" choice, but turning this option off can spoil the fonts everywhere else on other sites. There's something about (my) Firefox that's not recognizing the Century font, even though I have it. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:36, 2 July 2019 (UTC)
:::::::Yeah, not sure it's worth working around browser settings. Does the {{Raw Tile|c|6:0}} from above look ok to you or the same as the one on the creatures page? Also, that error is definitely not intentional; I'll look into it. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:57, 2 July 2019 (UTC)
::::::::The C there looks alright. Creature tile lists on other pages look fine as it's using the "Tile" template, so maybe something's wrong with the template being used in the creature page. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 12:55, 3 July 2019 (UTC)
:::::::::It's a custom template being used for those tables that specifies the font itself. I changed the font to fall back to the ones that {{tl|Tile}} uses. Does it look ok now? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:56, 3 July 2019 (UTC)
::::::::::It does not. But when I use a different computer, it's fine there (still on Firefox). Yeah, I can't figure this out. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 07:54, 4 July 2019 (UTC)
{{od|10}}
I've cleared the cache on the server side (I don't remember if I did that before). If that still doesn't help, maybe clearing your browser's cache would help? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:29, 4 July 2019 (UTC)
::Well, I cleared 1GB worth of data, but that didn't fix the issue? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:14, 5 July 2019 (UTC)

== BREAKING NEWS ==

Here comes Supernerd... the coolest and greatest editor ever on [[Dwarf Fortress Wiki]]. --[[User:Supernerd|Supernerd]] ([[User talk:Supernerd|talk]]) 10:47, 12 September 2019 (UTC)

== Proposal to translate the Wiki into Spanish ==

Good I am an expert player in the game and I would like to translate the wiki to help the Spanish community in this great game.
Should I translate it as I could?.
Here's my email for the answer: cheekonobreeko@gmail.com

== Just signal boosting on someone else's behalf... ==

...apparently a researcher with [http://www.bay12forums.com/smf/index.php?topic=174850.0 research] on [[book]]s got themselves [http://www.bay12forums.com/smf/index.php?topic=175133.0 locked out of the lab]. Any support for this?
--[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 12:02, 7 December 2019 (UTC)

== Minor server-side issues... ==

1. Broken(404) HTML links [[Quotes|here]].

2. Creature [[Giant earthworm|variation]] needs to be added [[Worm|here]].
--[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 11:09, 21 December 2019 (UTC)

:These aren't server-side issues - they can be fixed by editing the pages. In the first case, the forums moved from bay12games.com/forums to bay12forums.com/smf (I'm not sure when that happened, or if there used to be a redirect, but I would recommend {{tl|cite forum}} to make them future-proof). The second issue you pointed out happens when creature variations don't follow the typical naming pattern, but you can override the variations that the templates display. See [[blue jay]], [[bluejay man]], and [[giant bluejay]] for examples, and feel free to let me know if you have any questions about those templates. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 06:30, 22 December 2019 (UTC)
:Update: looks like there's also {{tl|forum link}} if you prefer to keep the text that the links currently use (for #1). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 06:33, 22 December 2019 (UTC)

== can't login... user:garrieirons ==

yeah I tried all the things and posted on the forum.

any advice on how to get a password reset?

https://dwarffortresswiki.org/index.php/User:GarrieIrons

Sorry if you're not an admin.

Cheers,
Garrie

Symptom:
When I click the reset password link, and enter my user name (GarrieIrons) it tells me:
'''A password reset email has already been sent, within the last 24 hours. To prevent abuse, only one password reset email will be sent per 24 hours.'''

Cheers again.
G

:Ok, so it sounds like you already requested a password reset - did you get an email? It should have come from do-not-reply@dwarffortresswiki.org (make sure it didn't get sent to your spam folder). If you don't have access to the email address you registered with anymore, I can try to reset it some other way. Also, where did you post on the forums? I didn't see anything from you on the wiki board. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:36, 16 February 2020 (UTC)
::To be clear, every password reset has resulted in the message above, but, no email. Can you tell me is it going to a hotmail, or a gmail address? If not, I'm stumped and I'll start a different account?
::Also...ok I looked at threads I guess. I coulda sworn at some time in the past I asked about this on the forum but I'm not finding it (only the thread I thought I responded to).
::G
:::OK I found a PM thread on the forum, from ages ago, referring me to you...but I'd never followed up... 🤦‍♂️
:::G.
:::Looks like your username at hotmail.com - do you still have access to that? I just sent you a test email from the wiki, so let me know if that goes through. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:24, 18 February 2020 (UTC)

== Weirdness ensues... ==

...Alright, maybe not, but then again...
[[Interaction_examples|this page]] is fine in Search, but spews redlinkery when linked to as if Ebola-infected - very puzzling.
---[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 21:16, 7 March 2020 (UTC) EDIT: And the mystery deepens, because apparently one has to be [[DF2014:Interaction_examples|very specific]] about phrasing...downright incantational,really...in order to get a clear result with this.

:If you're in a versioned namespace (like DF2014), links will be within that namespace by default; otherwise, they will use the main namespace. Looks like a [https://dwarffortresswiki.org/index.php?title=Interaction_examples&action=history redirect was created] in this case and both of those links seem to work now. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:56, 12 March 2020 (UTC)

== Obok Meatgod ==

Hey Lethesor, thanks for all the work you do for DFhack. I have a favour to ask. I was using the "random page" feature and I stumbled upon [[Obok Meatgod|this article]]. The article is about an adventure mode game from the Bay12 forums where some dude modded genitals into his game so he could [do some really vile stuff]. I don't mean to bug ''you'' about it, but I'm getting an internal error when I try to start a talk page on the article. Basically, can you delete this article? I'm all for some good shock humour, and I know DF stories can get pretty brutal, but this doesn't really seem like it's supposed to be funny. The forum page it links back to just reads like some edge-lord's fanfic power fantasy. Maybe I'm mistaken and this ''is'' relevant to DF, but if not, mind doing me a favour and just purging it from the wiki?
--[[Special:Contributions/130.211.1.83|130.211.1.83]] 00:33, 2 April 2020 (UTC) Jon
:I did a bit of research - given that it was deleted from Bay12 and DFFD, I think I'll follow suit and delete it from here too. (It's not permanent here - an admin could always get it back.) Thanks for bringing it to my attention. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:24, 2 April 2020 (UTC)
::Thanks Lethesor! [[Special:Contributions/35.191.8.35|35.191.8.35]] 17:07, 2 April 2020 (UTC) Jon

== Regarding a certain subst tag: ==

(Stop me if I miss anything, please.)

IIRC, its a since-deprecated holdover of some kind of Wikipedian affiliation, that is pretty much purge-on-sight when found in art licensing around here. The important question is, how to proceed, if at all, when evidence is discovered of apparent holdouts of that sort [https://dwarffortresswiki.org/index.php?search=subst%3A&title=Special%3ASearch&go=Go further afield], outside the verified-for-deletion parameters? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 13:45, 4 April 2020 (UTC)

:I suggest [https://www.mediawiki.org/wiki/Help:Substitution MediaWiki's documentation] for information on what subst does. It's not specifically something that came from Wikipedia. One caveat is that if the template being substituted didn't exist when the page was saved, the subst: won't get replaced until you save the page again. However, in this case, it looks like I [https://dwarffortresswiki.org/index.php?title=MediaWiki:Licenses&diff=prev&oldid=249061 removed] the subst: part from where these templates were being used, so yes, on image pages, removing the "subst: prefix is fine.
:From the search results you linked, a lot of the subst occurrences appear to be in [https://meta.wikimedia.org/wiki/Help:Wikitext_examples#HTML_tags HTML comments], so they won't get substituted when the page is saved. They also won't be displayed to readers, though. I suspect that's either stuff left over from version migrations or moving things to templates. I wouldn't put too much effort into dealing with those, unless you find something on a current-version page (in which case I'd say move things out of the comment if they're relevant or delete them if they're obsolete). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:06, 6 April 2020 (UTC)

== Lost password/email request ==

User: DDR
I've lost the email and password I apparently used to set up my account on this wiki, over a decade ago.

I'm [http://www.bay12forums.com/smf/index.php?action=profile;u=20574 DDR on the forum], which I still have my login for… and the mantis bugtracker, and DFFD.

Thank you. Sorry for the trouble.

:Sent a PM on the forums. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:21, 28 January 2021 (UTC)

== Further comment ==

It's hard to continue to [[wikipedia:WP:AGF|assume good faith]] in [https://dwarffortresswiki.org/index.php?title=User_talk%3ASilverwing235&type=revision&diff=256707&oldid=256705 this case], when the user in question tries to bury discussion of their behavior. Obviously that tactic isn't very effective, but it's a far cry from the openness and transparency required for the wiki to function as a collaborative project. Anyway, I firmly believe in [[wikipedia:WP:AAGF|WP:AAGF]] as a part of [[wikipedia:WP:CIVIL|WP:CIVIL]], which is part of the point I tried to raise in that discussion (which was then ''erased''). I'm linking these policies not because I think you're unfamiliar, but because I want to be clear on where I'm coming from. '''—'''[[User:Sriefmadsakzro|'''οɼѕаk''']] 17:48, 14 February 2021 (UTC)

:We don't have many of our own policies on things like this, but I'll take a look at the ones you linked since I'm not very familiar with them, particularly AAGF. It occurs to me that some of my comments may have come across as not following AAGF, and I apologize for that - I was (and still am) trying to follow AGF on my end, but it is challenging in this situation. I didn't intend to imply that you were not. As for the talk page edits, [[wikipedia:WP:OWNTALK|WP:OWNTALK]] seems to match my thoughts on the matter. Silverwing235's comment appears (to me) to be a more explicit acknowledgement of the criticism you raised, rather than an implicit acknowledgement by just removing your comment. I think your criticism was understood, in any case. (I do plan to respond to the AIV discussion, but am not sure how best to do that yet. In any case, I appreciate your concern for the wiki, and would like to find a solution that's acceptable to everyone involved.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:30, 14 February 2021 (UTC)

::A few phrases in my comments below are bolded—it's really just to emphasize structure, not to alter tone.'''—'''[[User:Sriefmadsakzro|'''οɼѕаk''']] 22:39, 15 February 2021 (UTC)
::---
::I actually wasn't talking about you when I referred to AAGF and my comment (and its erasure). I meant that Silverwing235 has—on this occasion and others—assumed that other editors are ''not engaging'' in good faith, and also that they are ''not assuming'' good faith (as when Silverwing235 referred to me as a “saboteur”); and that Silverwing235's own actions (''immediate'' removal of comments in ongoing discussions from their talk page—I believe this argument stands irrespective of [[wikipedia:OWNTALK|OWNTALK]]) make it hard to ''continue'' to assume good faith on their part.
::And, related to that: I have a hard time parsing many of Silverwing235's comments throughout. They're often vague and overcooked to the point of obscurity. There's very little there—even after the comment removal—that acknowledges the existence of a dispute over either past or ongoing behaviors, let alone the need for specific behaviors to change (let alone ''why'' those behaviors are wrong, or ''how'' those behaviors should change). Where there ''is'', there is also language implying that the issue is really with ''other'' editors and ''their'' disagreement—as if other editors are wrong to raise an issue in the first place. But as Silverwing235's edit summaries (and, incidentally, User+Talk comments) have repeatedly implied, they edit things to suit their personal tastes, ''not'' necessarily to correct mistakes (which they sometimes ''assert'' they are doing, but as has been seen, they frequently are not).
::---
::Another example of the general problem raised in AIV popped up yesterday: while reviewing a substantial [https://dwarffortresswiki.org/index.php?title=DF2014:Climate&curid=31137&diff=256715&oldid=247968 IP edit] (which, to me, looked good), I noticed that the edits immediately prior to it were Silverwing235's, made in late 2019 (soon after their dispute with Loci had ended in Loci's departure). And I quickly saw that [https://dwarffortresswiki.org/index.php?title=DF2014%3AClimate&type=revision&diff=247966&oldid=247965 this edit] was again, apparently, a “stylistic” change which Silverwing235 may honestly have believed necessary (for their own reasons), but which was [https://dwarffortresswiki.org/index.php?title=DF2014:Climate&diff=prev&oldid=256717 actually erroneous]. This sort of edit is partially why I cited IDHT and CIR (which, ''together'', are relevant here, I think) in the [https://dwarffortresswiki.org/index.php?title=Dwarf_Fortress_Wiki:Administrative_intervention_against_vandalism&oldid=256704 AIV discussion].
::And although I can understand why Voliol might have gotten the contrary impression in the AIV discussion, I'm not advocating a high bar for entry, here. I'm saying that if '''an editor has been told to avoid imposing their own judgment where they cannot articulate a rationale''' (such as when deciding whether [https://dwarffortresswiki.org/index.php/User_talk:Silverwing235#Disruptive_Editing commas] need to be inserted before every occurence of [https://dwarffortresswiki.org/index.php?title=DF2014:Justice&diff=prev&oldid=256609 “if”] and “as”; whether a pair of parentheses should be [https://dwarffortresswiki.org/index.php?title=Troubleshooting&diff=prev&oldid=256503 replaced] with an approximation to [https://en.wikipedia.org/wiki/Dash#Em_dash some other punctuation]; whether “he” and “she” should be [https://dwarffortresswiki.org/index.php?title=DF2014:Justice&diff=prev&oldid=256638 replaced], or [https://dwarffortresswiki.org/index.php?title=DF2014:Justice&diff=prev&oldid=256641 eliminated], or simply [https://dwarffortresswiki.org/index.php?title=User_talk:Silverwing235&diff=247445&oldid=247317 left alone] where they already occur; or whether [https://dwarffortresswiki.org/index.php?title=DF2014:Fairy&diff=prev&oldid=256548 miscellaneous comments oblique to the rest of an article] are necessary or even appropriate), as Silverwing235 has, '''but they continue to do so''', then that presents a problem related to both judgment and behavior (hence IDHT, tangential to CIR).
::---
::Now, I hate to have these two discussions at the same time, but at this point, it would be counterproductive to fork it, so: I see that Silverwing235 has actually objected to the ''whole AIV discussion'' on the basis that they do not believe DE constitutes vandalism (which obviously it does not, in general). But as I acknowledged in my first contribution there, the prior AIV thread seemed to be the most appropriate place to make my comments due to the discussion which showed this user has faced similar criticism before. And, as I mentioned both above and in AIV, there is a pattern of civility issues which existed at least as early as that AIV thread. In particular, their [https://dwarffortresswiki.org/index.php/User_talk:Loci#Discussion_in.2C_supposedly.2C_proper_context... responses] to criticism from Loci and in this case have been a mixture of aggressive and [[wikipedia:WP:INDCRIT|passive-aggressive]]. And again, it's hard to assume good faith when critical comments are removed ''immediately'' and without either '''a discussion''' or a '''clear''' and '''substantial''' '''acknowledgment''' that those comments referred to an ongoing pattern of behavior that must change (change ''what'', change ''how'', change ''why''). I.e., yes, users control their own talk pages, but that doesn't prevent their changes from being interpreted one way or another; and in this case, it's hard not to interpret Silverwing235's changes as ''avoiding the issue''. I understand their stated desire to avoid content which [[wikipedia:WP:MASTODON|affects them emotionally]], but this is about conduct as much as it is about content.
::---
::The only reason I've raised this is to avoid continued unease. I don't like writing about disputes, and I prefer to think of the wiki community as inclusive rather than exclusive. But again, it's harder to want to edit if this behavior—not just from Silverwing235, but from ''any'' editor—is unconstrained except by laborious trial and error (a huge time ''and energy'' suck, when you consider putting up with breaks from CIVIL). And I'm not alone in this (which I mention only to emphasize that this is not personal—and I'm ''not'' invoking a silent majority, whether one exists or not, and ultimately, it's not just about this one editor).
::---
::In any case, I appreciate your participation in the matter and in conveying suggestions about specific edits to this editor.
::'''—'''[[User:Sriefmadsakzro|'''οɼѕаk''']] 22:39, 15 February 2021 (UTC)

Point one: Yes, the notion about 'a more explicit acknowledgement' was accurate. A personal policy that I came up with re my talk page: 'If it would cause me significant emotional distress, either immediately or at any time during a review of the content, (aka: 'Nope, not having ''that'' around, causing trouble') it gets removed. If, IMHO, the removal itself would raise questions (as it appears to have done in this case) it will at least get a hopefully emotionally-neutral summary and acknowledgement of the thing that caused my upset to begin with. [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 11:27, 15 February 2021 (UTC)

== Redirect ==

Hello. I noticed in the recent changes you reverted the edit on [[Textile Industry]], and I realized that my edit on [[Expedition Leader]] falls in the same category. The problem is that, as long as they exist, those pages will always appear on autocomplete, and they won't redirect properly if left as is. So I propose that until a decision is made for them to be deleted, that they be allowed to redirect properly to not confuse people who find them through autocomplete, like me. --[[User:Lurker|Lurker]] ([[User talk:Lurker|talk]]) 20:51, 15 February 2021 (UTC)

:The underlying cause here is a Mediawiki bug with double redirects, discussed in detail at [[DF:REDIR]]'s talk page. Making ''any'' sort of edit to the first page in the chain will fix broken double redirects, so even though I reverted your edit, [[Textile Industry]] redirects correctly now, even from the search bar. The other important point is that you need to use "cv" for the namespace in redirect targets - hardcoding a specific version like "DF2014" will have the wrong behavior when we add a new namespace. In this case, I have deleted the page you edited, since [[Expedition leader]] (lowercase L) already exists and turns up in search results (and follows [[DF:Rule N]]). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:16, 15 February 2021 (UTC)
::Very well. Thank you for your time. --[[User:Lurker|Lurker]] ([[User talk:Lurker|talk]]) 21:22, 15 February 2021 (UTC)
:::I should clarify: you're welcome to fix redirects like this that you notice, as long as you use "cv" (and there's a reminder that appears above the edit box when editing pages in the main namespace, in case that's useful). If you notice redirects whose only difference is capitalization, feel free to tag them for deletion with {{tl|delete}} and I can handle them. It occurs to me now that [[Textile Industry]] is another example of that. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:26, 15 February 2021 (UTC)

== Drastic error in judgement ensues.. ==

Derped by starting [https://dwarffortresswiki.org/index.php/DF2014_Talk:Block this up], in a way it turned out I rather shouldn't have - mind cleaning up? Thanks. [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 19:43, 22 February 2021 (UTC)
:I'm not sure - what are you asking me to do? I'm hesitant to remove a discussion entirely, but if it's redundant to one on another talk page, I suppose I could archive it. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:24, 23 February 2021 (UTC)

...Yeah, archival was what I meant - one is always slightly frazzled when caught prepping to sign off for the night. [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 09:49, 23 February 2021 (UTC)

== Random/cv ==

Not that I want more clutter, but what do you think about putting a [[Special:Random/cv]] link in the sidebar? '''—'''[[User:Sriefmadsakzro|'''οɼѕаk''']] 16:24, 23 February 2021 (UTC)

:Do you always want that there, or just in the current version's namespace? For reference, there are custom links added in some namespaces already, like [[Special:Random/Masterwork]] on [[Masterwork:Orc]], so a fourth "random" link on that sidebar could add some clutter. I would lean towards doing this just for versioned pages, but I'm not sure what you think is best. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:55, 26 February 2021 (UTC)

::I don't know. As I said, I'm also not interested in more clutter. Personally, I've frequently been using a bookmark to random/cv just to get a sense of what's on the wiki these days (since I've been “away”/uninvolved). Obviously I don't think that's a good reason for the wiki to change anything, though. When I wrote this on your talk page, my thinking was this: if I'm a new player (or a former one), and I want to know ''what there is'' in this huge game that I don't already know everything about, maybe I'll go to the wiki and click "random page" a few times to satisfy my curiosity. I can always click it again if I end up on something in the Masterwork: namespace (or, if it's in v0.31 etc., just click the link in the Av template). But I'll have to do that ''most'' of the time, since articles in non-cv namespaces outnumber articles in cv. (Right?) I.e., I think my suggestion is only really relevant (at least from the point-of-view of my reasons for bringing it up at all) on the landing/main page. I'm ''not'' attached to it enough to say it should go everywhere. If there's no convenient way to exclude it from pages where there are already namespace-specific random links in the sidebar, then I'm not about to suggest anyone should spend their limited time on the planet worrying about it after all.
::'''—'''[[User:Sriefmadsakzro|'''οɼѕаk''']] 18:54, 26 February 2021 (UTC)

:::[https://www.mediawiki.org/wiki/Manual:$wgContentNamespaces This Mediawiki setting] came to mind as a potential easy way to exclude certain namespaces from [[Special:Random]] by default, but unfortunately it also affects some other special pages that we may not want to change. I could probably update our custom sidebar logic (which I believe is in [[mw:common.js]]) but it likely won't be a high priority. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:50, 28 February 2021 (UTC)

== Handling "!!science!!"-style additions ==

Sorry to repeatedly bring things to you—I don't really know who does what here now, or if there's a discussion board somewhere this belongs on (other than the talk page for just one of the related articles). Could you take a look at [[DF2014_Talk:Stress#SalfordSal_and_0.47.05|this discussion]]? As I mention there, there are a couple of other edits by that IP user at around the same time that (at a glance) look like they are probably similar. In the case of [[stress]], at least, the content of the article prior to the additions is now buried under a single user's experimental results for a game version one year out-of-date.
'''—'''[[User:Sriefmadsakzro|'''οɼѕаk''']] 18:36, 26 February 2021 (UTC)

:I left a comment on the article's talk page. The timing seemed to line up with [http://www.bay12forums.com/smf/index.php?topic=175214.msg8252465#msg8252465] closely enough that I also left a comment there. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:25, 28 February 2021 (UTC)

== A minor but rather elegant Gordian Knot of an error... ==

Is there any chance of fixing an [https://dwarffortresswiki.org/index.php?title=DF2014:Noise&curid=31900&diff=257273&oldid=250713| accidental red link] in the diff explanation, created when attempting to directly cite the reason's source, of an anonymous comment on the article's talk page, by citing the page instead of (obviously) the comment? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 17:06, 3 March 2021 (UTC)
:Edit summaries can't be changed, unfortunately. In case you were unaware, they can be previewed when you click the "Show preview" button (alternatively, just mentioning "the talk page" for something like this would be fine too). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:12, 3 March 2021 (UTC)

== Minor matter afoot.... ==

As it happens, I seem to have [https://dwarffortresswiki.org/index.php?title=DF2014:House&oldid=257129| edited myself into a corner] re proper formatting on the Towers of Bologna reference over here. Some help, please?
--[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 19:51, 7 August 2021 (UTC)

:If you meant the "Towers of Bologna" link, you can use the [https://en.wikipedia.org/wiki/Help:Pipe_trick pipe trick] for that (which I did in [https://dwarffortresswiki.org/index.php?title=DF2014:House&diff=prev&oldid=258665]). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:09, 7 August 2021 (UTC)

== Technical issues ==

Found a bare wire in the wall, somewhat beyond my skill level on account of it leading to, as it were, a broken widget - (https://dwarffortresswiki.org/index.php?title=DF2014:Orientation&curid=40938&diff=258997&oldid=258309) analysis, if you please? Thanks.
--[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 09:51, 6 September 2021 (UTC)

== Issue with #rreplace ==

Hi Lethosor. I want to bring up a possible MediaWiki Extension-related issue: when there's a lot of #rreplace functions (part of [[mediawikiwiki:Extension:RegexFunctions|RegexFunctions]]) on a page, they start breaking and outputting blank after the first hundred instances. I've experimented with a few different regex patterns and replacements, and this number doesn't seem to change. I currently have an [[User:Doorkeeper/sandbox|example on my sandbox]]. Checking the HTML source shows nothing out of the ordinary on the newpp report.

On the [[creature token]] page, there's more than a hundred {{t|token}}s being used (e.g. {{token|GOOD|c}}); they start linking to the Main Page after a little before section O. This is because {{t|token}} uses #rreplace as a method to remove spaces in the {{{2}}} or 'token type' parameter, so that the #switch function can still match strings in case an editor leaves a space in. However since #rreplace stops working after the first hundred (returns blank), the #switch matching fails and defaults, which is currently set to Main Page (the default page was originally [[Creature]]; it should probably default to a more relevant page). But yeah, noticing misdirecting {{t|token}} links on that page is what led me to #rreplace.

Removing #rreplace from the template will fix the issue (it'll lose its space-checking ability, which doesn't seem too big a deal), but I was wondering if it's possible to fix/update #rreplace or RegexFunctions itself, since this seems like a severe limitation. I don't know if #rreplace is used on other templates or if they're used a lot anywhere else on the wiki. It may not even be a problem with the extension. Either way, I thought it would be best to bring up this issue to you (or to another admin reading this). – [[User:Doorkeeper|Doorkeeper]] 05:45, 13 October 2021 (UTC)

:It's a deliberate limitation - we have the ``wgRegexFunctionsPerPage`` config variable set to 100 (up from the default of 10). I don't know exactly what performance impact would come from increasing it. Version 2 of the extension seems to have [https://github.com/wikimedia/mediawiki-extensions-RegexFunctions/commit/7b56f126fdb2c88375e77bca9cc7bf55eaefb3af removed all config variables], so maybe it is fine to just upgrade the extension. You can see the old documentation [https://www.mediawiki.org/w/index.php?title=Extension:RegexFunctions&oldid=3676687 here]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:10, 15 October 2021 (UTC)
:I also see you've made a fair number of changes to the token template. Should [https://dwarffortresswiki.org/index.php?title=Template:Token/guess_type&diff=259366&oldid=259363] be reverted? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:10, 15 October 2021 (UTC)

::If regex functions are just parser functions, then wouldn't they still be [[wikipedia:WP:TLIMIT|limited by MediaWiki software]]? This means that a limit will still exist to prevent overloading, just at a much higher cap. I have no knowledge about the other configuration changes though, or if you or someone else had set up the other configs in the past differently that would affect how the templates using regex will work post-upgrade. Is this what you meant by performance? Optionally, if you're still unsure about upgrading, you could raise the limit a little instead. DF2014:Creature token currently exceeds the limit by 51. I think 200-500 is enough to fix things now and later down the line. Most other wikis I've seen that have RegexFunctions still use 1.5.0, so this is probably the better/safer option. I changed my mind about #rreplace and would like for it to remain, however the limitation is still causing issues for the page. The revert did mitigate it somewhat, but [[DF2014:Creature token#NOTHOUGHT|not perfectly]]. – [[User:Doorkeeper|Doorkeeper]] 13:17, 13 December 2021 (UTC)

Unrelated, but I'd like to request for [[mediawikiwiki:Snippets/Horizontal lists|horizontal lists]]. This feature allows for [[wikipedia:MOS:HLIST|single-row styled lists]] using wiki markups in tables, templates, etc. A lot wikis including WP use them. I want to redesign [[Template:Navbox]], and hlists would be very useful. – [[User:Doorkeeper|Doorkeeper]] 13:24, 13 December 2021 (UTC)

== May want to lock down at least the LNP page to non-registered users... ==

....for a while (two weeks, perhaps?) as we have a dumbass about...the kind of [https://dwarffortresswiki.org/index.php?title=Utility:Lazy_Newb_Pack&oldid=259549| trollish dumbass] who has been sufficiently irritating to deserve an IP trace and a knife in the face, IMHO. "Can't troll on the internet if you're dead, hey? Yeah, let's see how you deal with that." kind of thing,
--[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 20:49, 5 November 2021 (UTC)

:Threats of violence are not acceptable. Consider this a warning. People will inevitably vandalize a public wiki; the appropriate course of action is to post to [[DF:AIV]] or alert an admin, as you did. I blocked the IPs in question and protected the page, so hopefully that helps with the immediate issue. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:39, 6 November 2021 (UTC)

== Copyright issues... ==

...as in, Meph's recent tileset takedown [https://dwarffortresswiki.org/index.php/Dwarf_Fortress_Wiki_talk:Copyrights produced a discussion]. Your contribution may be needed, but particularly, the exact wording of the copyright template needs some adjusting - mind pointing me at it? Thanks. [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 11:51, 21 November 2021 (UTC)

:Are you referring to the "Text is available under GFDL & MIT" suggestion? It's a rather long discussion, so I'm not sure. If so, that is a [https://www.mediawiki.org/wiki/Help:System_message system message], which can only be edited by admins. You can identify the appropriate message ID by overriding the language code to "qqx" as described in that article. Looks like [[mediawiki:copyright]] to me. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:41, 25 December 2021 (UTC)

Yes, I was of course referring to the system message edit suggestion - thanks & happy Xmas. [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 23:25, 25 December 2021 (UTC)

* Comment: While on topic, you might want to add a caveat excluding the content of games raws used on the wiki from the general copyright. I assume we are using them with Today's blessing, however, I doubt that Toady would wave his rights over their content. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 14:50, 30 December 2021 (UTC)

== Redirects ==

Thanks, I was wondering about that, glad you guys have a policy. Also on unrelated topic, would love to hear what you think regarding the [[Dwarf_Fortress_Wiki:Centralized_Discussion/SkillsLaborProfessions|terminology in use on skill articles]]. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:55, 22 December 2021 (UTC)
:At a high level, I am in favor of standardization. I haven't had much time to look at that discussion in detail. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:38, 25 December 2021 (UTC)
::Essentially it is a question of standardization. I outlined (1) some discrepancies in the lead of various skill articles, and I believe (2) the terms in the infobox might be misleading, and referred everywhere else differently. Input from more experienced users of this wiki would be appreciated regarding the direction to take.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 00:13, 26 December 2021 (UTC)

----
Question: How do link from the DF2014 namespace to the main namespace. For example: when I try to link to [[Dwarf Fortress Talk]] from [[DF2014:modding]] it shows broken because it only looks up DF2014 namespace and I don't know how to prefix the mainspace. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 15:32, 30 December 2021 (UTC)

:"Main" as the namespace should work (it's an alias that we've set up). Ex: [[Main:Dwarf Fortress Talk]] or [[Main:Dwarf Fortress Talk|Dwarf Fortress Talk]] —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:15, 1 January 2022 (UTC)
:: That works, thank you. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 00:13, 2 January 2022 (UTC)

== Columns-list ==

Any objections for adding the a [https://en.wikipedia.org/wiki/Template:Columns-list Columns-list] template to replace large list represented by tables. It's easy to use, easy to adjust option that allows to fit more information horizontally (where possible) using columns and wouldn't break layout like on multi columns tables can, like on some mobile devices.

I made an example: [[User:Jan/Columns-list]] for creatures in [[Desert]]. All you need is provide desired column width or number. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 16:54, 24 December 2021 (UTC)

:Seems like a fine approach to me, as long as it's used for tables where we don't anticipate needing more than one column per entry (so I think [[Desert]] is a good use-case). As a plus, it looks like it falls back to a single-column list for browsers that don't support it. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:38, 25 December 2021 (UTC)

:: Sound good. I created [[Template:Columns-list]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 00:13, 26 December 2021 (UTC)

== Found a script [[User:Lethosor/rater_0.1.js| stuck in its drawer]]... ==

...in what might be called the 'Mistakes' subsection, while cleaning up. That is to say, we have a 'Quality ranks in invalid namespaces' situation. What to do?
--[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 12:19, 16 January 2022 (UTC)

== Spam issues ==

For once, what I'd otherwise have to say is available [https://dwarffortresswiki.org/index.php?title=Python&curid=38885&diff=263697&oldid=263696 in the diff desc]. I imagine there's also a Magic redirect that needs some of the same protective treatment. [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 12:32, 21 April 2022 (UTC)
--[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 12:32, 21 April 2022 (UTC)

:Quietust protected [[Python]]. I protected [[Magic]] just now. I think that's what you meant, but could you please be more clear with your requests in the future? Thanks. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:40, 22 April 2022 (UTC)

== Mediawiki:Licenses ==
This is kind of an awkward thing to ask, but... am I allowed temporary access to edit the Mediawiki:Licenses page? There are a lot of licenses I think should be added, so it's nice and up to date. I'm happy with your decision either way, I just thought you wouldn't want me constantly bothering you for every little thing I think should be added. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 18:10, 3 July 2022 (UTC)
:No, it's not something I can grant on a per-page basis, unfortunately. But if you make the edits you want to a user page or sandbox or somewhere else, I'd be happy to copy them in. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:48, 5 July 2022 (UTC)
::Alright then, here's one for the CC0 license: [[:Template:cc-0]] -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 06:22, 21 July 2022 (UTC)
:::Here's another: [[:Template:Cc-by-nc-nd-4.0]] -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 06:28, 21 July 2022 (UTC) 
::::Aaaaand another [[:Template:Cc-by-nd-4.0]] and another [[:Template:Cc-by-sa-4.0]]
Please also include the title you want. Ideally in the format that page uses. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 06:43, 21 July 2022 (UTC)
:::::I thought the titles within those templates were the giveaway, but very well:
*[[:Template:cc-0]] - Creative Commons Public Domain
*[[:Template:Cc-by-nc-nd-4.0]] - Creative Commons Attribution Non-Commercial NoDerivatives 4.0 International
*[[:Template:Cc-by-nd-4.0]] - Creative Commons Attribution-NoDerivatives 4.0 International
*[[:Template:Cc-by-sa-4.0]] - Creative Commons Attribution-ShareAlike 4.0
*[[:Template:Cc-a-2.0]] - Creative Commons Attribution 2.0 Generic (give or take the "generic" part)
*[[:Template:Cc-by-nc-2.5]] - Creative Commons Attribution-NonCommercial 2.5 Generic (give or take the "generic" part)
*[[:Template:Cc-2.5]] - Creative Commons Attribution 2.5 Generic
*[[:Template:Cc-2.5-au]] - Creative Commons Attribution 2.5 Australia
*[[:Template:Cc-by-2.0-uk]] - Creative Commons Attribution 2.0 UK: England & Wales
*[[:Template:Cc-by-3.0-us]] - Creative Commons Attribution 3.0 United States
*[[:Template:Stock_photo]] - Stock Photo Image

The "I do not know the license" and "found the image somewhere" templates seem to be broken or missing. Not sure if I should make templates for those or not... -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 07:24, 21 July 2022 (UTC)
:Ehh, what the hell, I made those two templates anyway. [[:Template:License_unknown]] and [[:Template:Found_image]]. If you need 'em, fine. If not, still fine. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 07:28, 21 July 2022 (UTC)
::Here's more
*[[:Template:public_domain]] - Public Domain
*[[:Template:Cc-1-uni]] - Creative Commons CC0 1.0 Universal

Sorry for the delay. I have a lot of questions about which section(s) these should go in, etc.. I'm guessing you know the answers to these, so to save us some back-and-forth, could you make the changes you want to [[Dwarf_Fortress_Wiki:Sandbox/licenses]] (a copy) and let me know when they're ready to be copied in? Thanks. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:14, 24 July 2022 (UTC)
:I made a mockup on my [[User:Zippy/sandbox|sandbox page]]. Note that the top two are marked by with a "(replace)" because I also made a "don't know" and "license unknown" template to replace the ones that seem to be missing/broken, for some reason. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 12:36, 27 July 2022 (UTC)
::Yeah... I notice you still haven't added these. Did I set this up wrong? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 05:53, 5 August 2022 (UTC)
:::Well, it wasn't in a format that I could easily paste in. I had to remove the bold text, remove your parenthetical remarks, and replace " - " with "|". I think I got it right in [https://dwarffortresswiki.org/index.php?title=MediaWiki:Licenses&diff=266031&oldid=264287]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:26, 30 August 2022 (UTC)

== "Watch" Template ==

Sorry to keep bothering you with stuff, but I made a "watch" template on my [[User:Zippy/sandbox|sandbox page]]. It can be used for those ambiguous 50/50 situations where the copyright infringement is possible, but unknown. Do I have your permission to make that template a reality? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 13:54, 22 July 2022 (UTC)

:I think it should be more specific, like {{tl|possible copyright issue}} and "the copyright status of this image is unconfirmed". —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 15:44, 22 July 2022 (UTC)
::I changed it, but if the template is allowed, you might have to do some CSS changes so that one side isn't a mismatching blue. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 16:22, 22 July 2022 (UTC)
:::Take a look at {{tl|ambox/type}} for a list of valid types. Notably, "green" is not valid and falls back to the default, but "style" or "yellow" match pretty closely. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:18, 22 July 2022 (UTC)
::::Fair enough. So.. am I allowed to make the template or..? Not sure how this works. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:47, 22 July 2022 (UTC)
:::::There are no restrictions on creating templates. That said, I still strongly recommend that you make the template more specific. "watch" is pretty vague for a single-purpose template like this. Can you rename it to {{tl|possible copyright issue}} or something similar? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:21, 23 July 2022 (UTC)
::::::Done. I even made the respective doc page. ([[:Template:Watch|Actual template]]) -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 21:02, 23 July 2022 (UTC)
:::::::Again, it's still named {{tl|watch}}, which I don't recommend (partly since Mediawiki already uses that term for [https://www.mediawiki.org/wiki/Help:Watching_pages something else]), but thanks for the docs. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:05, 23 July 2022 (UTC)
::::::::Done, but should the "watch" redirect stay so that it's not dissociated with images that already have the template? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 21:08, 23 July 2022 (UTC)
:::::::::Yeah, that's a good catch - the redirect should make it easier on us. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:13, 23 July 2022 (UTC)

== Request for interwiki (inter-language) link to Chinese wiki ==

Sorry for repeated content, but I'm wondering if the message has been captured from talk page of Main Page. So I decide to paste my content here as well. We would be really appreciated if interwiki link pointing to our site is enabled, as ''Dwarf Fortress'' itself has not been fully translated to Chinese ever, and our users might find it more convenient to search by English words on original English wiki, and then they may refer to the translated ones on Chinese wiki. Looking forward to a reply about whether it is possible or not. Thanks!

Hello! I'm the admin of [https://dfzh.huijiwiki.com/ Chinese Dwarf Fortress wiki], and I've previous put its link on the main page. We've now enabled interwiki link from our site to English site, and we wish to get one back from English site to CN site as well. Hope that is possible, and thanks so much! The URL for our site should be: <code>https://dfzh.huijiwiki.com/wiki/$1</code> [[User:Xjtu-blacksmith|xjtu-blacksmith 黑山雁]] ([[User talk:Xjtu-blacksmith|talk]]) 01:20, 11 November 2022 (UTC)

Main Page

2022-11-09T15:09:04Z

Xjtu-blacksmith: fix Chinese wiki format & add Chinese forum

{| id="mp-topbanner" style="width:100%; background:#f9f9f9; margin:0; padding:0; border:1px solid #ddd; border-top-left-radius:8px; -moz-border-radius-topleft:8px; -webkit-border-top-left-radius:8px; border-top-right-radius:8px; -moz-border-radius-topright:8px; -webkit-border-top-right-radius:8px; margin-bottom: -2px; border-spacing: 0px;"
| style="color:#000;" |

{| style="width:280px; border:none; background:none; padding-top: 16px; padding-bottom: 16px;"
| style="width:280px; text-align:left; white-space:nowrap; color:#000; padding-left: 12px;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; padding-left: 0; color:#000;">The Dwarf Fortress Wiki</div>
<div id="articlecount" style="font-size:85%; padding-left:2px;">[[Special:Statistics|{{Template:NUMBEROFARTICLES}}]] articles about '''v{{current/version}}''' Previous versions: [[v0.34:Main Page|v0.34]] / [[v0.31:Main Page|v0.31]] / [[40d:Main Page|40d]] / [[23a:Main Page|23a]]</div>
|}
| style="min-width:35%; padding-right: 10px;" |
<div style="border: 1px solid #eee; padding: 8px;">{{:Main_Page/Quote}}<div>[[/Quote/list|More]]</div></div>

| style="width:16%; font-size:12px; border-left: solid 1px #ddd; background: #eef5ff; border-top-right-radius:8px; -moz-border-radius-topright:8px; -webkit-border-top-right-radius:8px;" |
{| style="width: 90%; margin: 0 auto;" |
| style="width:100%; font-size:12px;" |
[[About]]
[[Quickstart guide|Tutorial]]
[[Installation|Downloads]]
|}
|}
{{Main page progress bar}}
{| style="border-spacing:0; margin-top: -2px; width:100%; border:1px solid #ddd; background:#f9f9f9; height: 128px;" |
| style="width:84%;" |
{| style="width:100%; height: 126px; padding-left:12px;"
|
[[Welcome]] to the [[Dwarf Fortress Wiki]]. This is a collection of user-submitted guides, information and advice for [http://www.bay12games.com/dwarves/ ''Dwarf Fortress'']. ''[[Dwarf Fortress]]'' is a game for Windows, Linux and Mac, developed by [http://www.bay12games.com/ Bay 12 Games] featuring two modes of play ([[Dwarf fortress mode|Fortress]] and [[Adventurer mode|Adventurer]]), as well as distinct, randomly-generated worlds (complete with [[Biome|terrain]], [[creatures|wildlife]] and [[legend]]s), gruesome combat mechanics and ubiquitous [[Dwarf|dwarven]] [[alcohol]] dependency.

{{quick download|style=margin-left:-12px;}}
|}
| style="width:16%; border-left: solid 1px #ddd; text-align: left; background: #eef5ff;" |
{| style="width: 90%; text-align: left; height: 126px; margin:0 auto; padding:0; margin-top: 1px;"
|'''v{{current/version}}''' '''{{current/lastupdate}}''' [http://www.bay12games.com/dwarves/ Changelog] [[CV:Release information/{{current/version}}|Release Information]]
|}
|}
{| style="border-spacing:0; margin-top: -2px; width:100%; border:1px solid #ddd; background:#f9f9f9; line-height: 18px; height: 139px; padding: 1px;"
| style="width: 20%; border: 1px solid #CA7A02; box-shadow:0px 0px 4px #CA7A02 inset;" |
{| style="width:100%; height: 150px; padding: 0px 12px;"
|
'''New to ''Dwarf Fortress''?'''

[[Installation|Download & install]]

[[Quickstart guide|Fortress mode tutorial]]

[[Adventure mode quick start|Adventure mode tutorial]]

[[Troubleshooting|How do I get more help?]]

|}
| style="width:45%; border-left: solid 1px #ddd;" |
{| style="width:100%; height: 150px; padding-left:12px; padding-top: 8px;"
|colspan="3"|'''Reference Pages'''
|-
|

[[Design strategies]]

[[Adventurer mode]]

[[Dwarf fortress mode|Fortress mode]]

[[Material]]s

[[Farming]]

[[Trading]]

|style="padding-left:30px;"|

[[World generation]]

[[Advanced world generation]]

[[Industry]]

[[Combat]]

[[Military]]

[[Fun]]

|style="padding-left:12px;"|

[[Creature]]s

[[Weapon]]s

[[Building]]s

[[Dwarf|Dwarves]]

[[Mining]]

[[Skills]]

|}
| style="width:50%; border-left: solid 1px #ddd;" rowspan=2 |
{{random image|size=400x300px}}
|-
| style="border-top: solid 1px #ddd; padding-left: 12px; padding-top: 8px;" colspan=2 |
{| style="width:100%"
|-
| '''Other / [[Mods]]'''
|-
|| [[Bloodline games]] || [[Cheating]] || [[Known bugs and issues|Known bugs]] || [[Framerate]] || [[Modding guide]]
|-
|| [[Masterwork:Main Page|Masterwork DF]] || [[Graphics]] || [[Utilities]] || [[Technical tricks]] || [[Dwarf Fortress webcomics|DF webcomics]]
|}

|}
 

{| id="mp-topbanner" style="width:100%; background:#f9f9f9; margin:0; padding:12px; border:1px solid #ddd; margin-bottom: -2px; border-spacing: 0px;"
| style="color:#000;" |
{| style="width: 100%;"
|-
! style="text-align: left; padding: 0.1em 0.5em" | Forums:
| [http://www.bay12forums.com/smf/ Official Forums], [http://www.bay12forums.com/smf/index.php?board=22.0 Official Wiki Forum], [http://www.reddit.com/r/dwarffortress/ Reddit], [http://www.gamingsteve.com/blab/index.php?topic=6350.0 GamingSteve Thread], [https://knockout.chat/thread/559/1 Knockout! Thread], [http://springrts.com/phpbb/viewtopic.php?f=10&t=10908 SpringRTS Thread], [http://forum.dwarffortress.fr/ French forum], [http://forum.canardpc.com/threads/68897-Dwarf-Fortress.-Le-topic-v2-pour-ceux-qui-ont-encore-des-yeux Canard PC Thread (Fr)], [https://steamcommunity.com/app/975370/discussions/ Steam Discussions], [https://tieba.baidu.com/f?kw=%E7%9F%AE%E4%BA%BA%E8%A6%81%E5%A1%9E Baidu Tieba (Zh)]
|-
! style="text-align: left; padding: 0.1em 0.5em" | Blogs:
| [http://dfstories.com/ Dwarf Fortress Stories], [http://www.bravemule.com/ Bravemule]
|-
! style="text-align: left; vertical-align: top; padding: 0.1em 0.5em" rowspan=2 | [[IRC|IRC Channels]]:
| '''DF-related:''' [irc://irc.esper.net/bay12games #bay12games] on irc.esper.net, [irc://irc.freenode.net/dwarffortress #dwarffortress] on freenode.net, [irc://irc.synirc.net/df #df] on synirc.net, [irc://irc.quakenet.org/DwarfFortress #DwarfFortress] on quakenet.org, [irc://irc.tellaerad.net/DF #DF] on tellaerad.net and [irc://irc.rizon.net/brofortress #brofortress] on rizon.net.
|-
|'''Other:''' [irc://irc.freenode.net/dfwiki #dfwiki] on freenode.net, [irc://irc.freenode.net/lazynewbpack #lazynewbpack] on freenode.net
|-
! style="text-align: left; padding: 0.1em 0.5em" | Discord Server:
| [https://discord.gg/kitfoxgames Official Kitfox Games Discord]
|-
! style="text-align: left; padding: 0.1em 0.5em" | DF Wikis in other languages:
| [http://www.dwarffortress.fr/wiki Le Wiki Français], [http://wikiwiki.jp/dwarffort/ The Japanese (日本語) Wiki], [http://www.dfwk.ru The Russian Wiki], [http://pl.dwarffortress.wikia.com/ The Polish Wiki], [https://dfzh.huijiwiki.com 中文维基]
|-
! style="text-align: left; padding: 0.1em 0.5em" | Useful Links:
| [http://mkv25.net/dfma/ Dwarf Fortress Map Archive], [http://dffd.bay12games.com/ Dwarf Fortress File Depot (DFFD)], [http://www.bay12games.com/dwarves/mantisbt/my_view_page.php Mantis Bug Tracker], [https://store.steampowered.com/app/975370 Dwarf Fortress on Steam]/[https://kitfoxgames.itch.io/dwarf-fortress itch.io], [https://www.twitch.tv/directory/game/Slaves%20to%20Armok%20II%3A%20Dwarf%20Fortress Dwarf Fortress on Twitch]
|-
! style="text-align: left; padding: 0.1em 0.5em" | Archives:
| [[23a:Main Page|v0.23.130.23a Wiki]], [[40d:Main Page|v0.28.181.40d Wiki]], [[v0.31:Main Page|v0.31.25 Wiki]], [[v0.34:Main Page|v0.34.11 Wiki]]
|}
|}


[[ru:Заглавная_страница]]
[[fr:Accueil]]

<div id="norate"></div>

Dwarf Fortress

2022-11-08T10:48:23Z

Xjtu-blacksmith: /* Threats, defense and digging deeper */

{{DISPLAYTITLE:''Dwarf Fortress''}}
[[File:Df logo.png|thumb|350px|Official logo]]

'''''Dwarf Fortress''''' (officially '''''Slaves to Armok: God of Blood Chapter II: Dwarf Fortress''''', referred to as '''DF''') is a part [[wikipedia: Construction and management simulation|construction and management simulation]], part [[wikipedia: roguelike|roguelike]], [[wikipedia: indie video game|indie]] video game created by [[Tarn Adams|Tarn]] (Toady One) and [[Zach Adams]] (ThreeToe). [[wikipedia: Freeware|Freeware]] and in development since 2002, its first [[wikipedia: alpha version|alpha version]] was released in 2006 and it received attention for being a two-member project surviving [[donation|solely on donations]]. The primary game mode is set in a [[wikipedia: procedurally generated|procedurally generated]] fantasy [[world]] in which the player indirectly controls a group of [[dwarves]], and attempts to construct a successful and [[wealth]]y [[fortress]]. Critics praised its complex, [[wikipedia: emergent gameplay|emergent gameplay]] but had mixed reactions to its [[Fun|difficulty]]. The game influenced ''[[wikipedia: Minecraft|Minecraft]] ''and was selected among other games to be featured in the [[wikipedia: Museum of Modern Art|Museum of Modern Art]] to show the history of video gaming in 2012.

The game has [[wikipedia: Text-based game|text-based]] graphics and is [[wikipedia: open-ended (gameplay)|open-ended]] with no main objectives. Before being played, the player has to [[world generation|generate]] worlds with continents, [[ocean]]s and histories documenting [[civilizations]]. The main game mode, [[Fortress Mode]], consists of selecting a suitable [[site]] from the generated-world, establishing a successful colony or fortress, combating threats like [[goblin]] [[invader|invasions]], generating wealth and taking care of the dwarves. Each dwarf is modeled down to its individual [[personality]], has [[Preferences|likes or dislikes]] and specific trainable [[skill]]s in various [[labor]]s, alongside a lovelife system and distractions. The second game mode, [[Adventure mode]], is a [[wikipedia: turn-based|turn-based]], open-ended roguelike where the player starts off as an [[adventurer]] in the world and is free to explore, complete quests, or even visit old [[ruin|abandoned fortresses]]. The [[combat|combat system]] is [[Anatomy|anatomically detailed]] with combat logs describing organs getting pierced, fat getting bruised and [[Body parts|limbs getting severed]].

Prior to ''Dwarf Fortress'', Tarn Adams was working on a project called ''Slaves to [[Armok]]: God of Blood'' which was a [[wikipedia: role-playing game|role-playing game]]. By 2004, Adams decided to shift from the original ''Armok'' to ''Dwarf Fortress'' after the former became difficult to maintain. Adams calls it his life's work and said in 2011, that version 1.0 will not be ready for at least another 20 years, and even after that he would continue to work on it. The game has a [[wikipedia: cult following|cult following]] and an active online community. As there is no way to win, every fortress, no matter how successful, is usually destroyed somehow. This prompts the unofficial community motto: "[[Losing is Fun]]!"

==Gameplay==

===Overview and game modes===
''Dwarf Fortress'' has three primary game modes which take place in worlds created by the player, where most of the elements are randomly generated. [[Fortress Mode]] is a [[wikipedia: construction and management simulation|construction and management simulation]] of a colony of [[dwarves]]. There are no objectives, with the player being free to decide how to go about managing the colony and making them interact with the environment, thus making it an [[wikipedia: open-ended (gameplay)|open-ended]] and [[wikipedia: Sandbox game|sandbox]]-style game. Since there is no way to win, it only ends when the entire colony is [[Losing|defeated by the various possible threats]]. The visuals are [[wikipedia: Text-based game|text-based]] using [[wikipedia: code page 437|code page 437]] characters in various [[color]]s as graphics. Thus, it is fully of letters, numbers and symbols; dwarves are represented by different colored smiling faces, a [[cat]] and [[dog]] are a white "c" and brown "d", while a [[giant cave spider]] is a grey "S".

[[Adventure mode]] is a [[wikipedia: turn-based|turn-based]], open-ended [[wikipedia: roguelike|roguelike]] where the player starts off as an adventurer. In [[Legends mode]], players can view maps, histories of each civilization and any figure who has lived or died in the generated world. Any noticeable achievement made by the player in any of the two game modes is recorded in the Legends. An [[object testing arena]] is present, where players can simulate battles between selected units in various conditions.

===World generation===
{{Main|World generation}}
[[File:WorldGenerationScreen.png|thumb|left|A world being generated and the years being counted. Each game is played in such generated worlds.]]
The first step in ''Dwarf Fortress'' is generating a [[World generation|playable world]]; only one game can be played per world at a time. The player can adjust certain [[World_generation#Parameters|parameters]] governing size, [[Surroundings|savagery]], mineral occurrences and the length of history. The map shows symbols representing [[road]]s, [[hill]]s, [[town]]s and [[cities]] of the various [[civilization]]s, and it changes as the generation progresses. A [[wikipedia: midpoint displacement algorithm|midpoint displacement algorithm]] generates the world.

The process involves [[wikipedia: procedurally generated|procedurally-generated]] basic elements like elevation, [[rain]]fall, mineral distribution, drainage and [[temperature]], using [[wikipedia: fractals|fractals]] (which give it an overall natural look). For example, a high-rainfall and low-drainage area would make a [[swamp]]. Areas are thus categorized into [[biome]]s, which have two variables: savagery and [[wikipedia: Alignment (role-playing games)|alignment]]. They have their own specific type of [[plant]] and [[animal]] populations. The next phase is erosion—which the drainage tries to simulate. [[River]]s are created by tracing their paths from the [[mountain]]s (which get eroded) to its end which is usually an [[ocean]]; some form into [[lake]]s. The salinity field defines oceans, [[mangrove]]s or [[alluvial]] plains. Names are generated for the biomes and rivers. The names depend on the area's [[good]]/[[evil]] variable (the [[alignment]]) and though in English, they are originally in one of the four [[language|in-game language]]s of [[dwarves]], [[elves]], [[human]]s and [[goblin]]s; these are the four main races in any generated world.

After a few minutes the world is populated and its history develops for the amount of in-game [[year]]s selected in the history parameter. Civilizations, races and religions spread and [[war]]s occur, with the "population" and "deaths" counters increasing. The ticker stops at the designated "years" value, at which point the world can be saved for use in any game mode. Should the player choose to retire a [[Dwarf fortress mode|fortress]] or gets [[losing|defeated]], this world will persist and will become available for further games.

===Fortress mode===
{{Main|Dwarf fortress mode}}
====Basics====
[[File:Embark A Map.png|thumb|The game uses text symbols for graphics. For example, a dwarf is a colored smiling face and various other letters represent animals. Here, dwarves and livestock around their wagon of supplies can be seen just after embark.]]

When Fortress mode is selected, the player is given the option to choose the [[embark|embark location]] in the world. The player must consider the environment, elevations, biome, soil types and mineral concentrations, which can pose significant challenges to the development or survival of the fortress.The colony's [[supplies]], [[domestic animals]], and skills can be customised, but each dwarf's [[mental attributes|mental]] and [[physical attributes]] are randomly generated,as are their mental abilities, individual preferences and desires. The game also describes in detail each dwarf's [[Physical_description|physical appearance]], like hair and facial features.. Each dwarf's [[relationships]] with others and the [[deities]] they worship can be viewed.

The player embarks with the expedition team (seven dwarves, and their livestock and supplies by default), and does not have direct control over them. In order to construct and operate the fortress, the dwarves undertake [[labour]]s as designated by the player. They can be assigned any labors, but their work still depends on their relative skill with it, which can increase. Some task categories are stone-working, woodworking, metalworking, farming-related and crafts-making; there are further combat-related skills. They are categorized further, such as [[leatherworking]], [[butchery]], [[clothesmaking]], [[gem]]-related, [[glassmaking]], and [[clay]]-related [[Industry|industries]]. Activities take place in [[workshop]]s which need to be constructed; for example, [[still]]s for brewing alcohol. The [[metal industry]] has a very important role because it produces [[weapon]]s and [[armor]] for the [[military]], [[trap component]]s for defense, and high-value [[furniture]] and [[decoration]]s.

==== Functional mechanics ====
The player initially can see a [[wikipedia: top-down view|top-down view]] of the surface-level of the fortress site; each [[layer]] of a [[z-axis]] [[z-level|level]] can be viewed when the player changes it. An entire underground level would be seen as its entire section of terrain while a mountain at the surface level would have only its section visible with the remaining surface landscape. Thus, for [[dig]]ging, the player can designate, for every z-level starting from the surface, [[staircase]]s to be carved and at the final designated level, ending the staircase by making it dug into a room.

The [[geology]] in ''Dwarf Fortress'' is fairly accurate. Rocks like [[olivine]] or [[gabbro]] can be dug up, while the topmost layer usually consists of [[sand]], [[clay]] or plain [[soil]]—this can be used for underground [[farming]]. Deeper levels are layers of rock; minerals appear in layers or [[cluster]]s around the right depth, while [[gem]]s like [[tourmaline]]s appear in rare clusters. [[Water]] is simulated like falling sand, every space can contain up to seven levels of it. A tile having "one" level of water is the lowest while a tile with "seven" is full. There is a system for simulating temperature and heat. [[Fire]]s can spread and burn dwarves and furniture. There are four basic [[season]]s in an in-game year as in real life: spring, summer, autumn and winter.

[[ore|Mineral ores]] can be mined just like normal stone and the raw ore can be [[smelting|smelted]] to produce their corresponding [[metal bars]]. Different ores or metal bars can be [[alloy]]ed together for higher quality materials. For [[steel]] production, [[flux]] stones are used to make [[pig iron]] bars and smelt it with regular [[iron]] and [[coal]] (or [[charcoal]]). Specific metal items can be melted back to their respective bars. Without steel, the alloy [[bronze]] or regular iron are the next best suitable metals to use. Bronze requires two ores or bars of [[tin]] and [[copper]]. The metal [[adamant]]ine, found deep below, is extremely light but very strong, making it excellent for sharp weapons and armor. [[Raw adamantine]] can be [[Strand extractor|extracted into strands]] and can further be either woven in cloth or smelted into [[wafer]]s.

==== Fortress management and growth ====
Underground [[farming]] has customized crops like "[[plump helmet]]" mushrooms, which can be [[brewer|brewed]] to make [[dwarven wine|mushroom wine]]. As the fortress prospers, [[migrant]]s come in larger numbers from the [[mountain halls|mountainhome]] (the colony's home civilization) and will need further accommodation. [[Trading|Trading caravans]], which can be from the various neighboring civilizations including the home civilization, visit the fortress on a yearly basis and are useful for getting supplies not available in the player's fortress area. The role of [[record keeper]], [[manager]] and [[broker]] can be assigned to any dwarf during early game. The record keeper maintains records of every item present in the fort, the manager [[work order|auto-assigns jobs]] and the broker deals with trading caravans. The production of [[craft]]s from any material are useful for trading. The caravans come from civilizations of [[elves]] and [[humans]] but depending on the embark region and history, they may be absent or sometimes even hostile.

Dwarves need to be provided with [[food]] and [[drink]] (mostly in the form of [[alcohol]]). A dwarf will get [[negative thoughts]] for drinking plain water and even for drinking the same type of alcohol, making it necessary to grow different crops for producing different drinks. Things like not having a separate [[bedroom]] can upset a dwarf. They may make [[friend]]s and sometimes [[marriage|marry]]; females give birth. Dwarves can get upset by sustaining [[injuries]], having poor [[clothing]], [[death|losing]] their [[pet]]s, friends or relatives; interacting with or seeing their [[corpse]]s can aggravate this. A frustrated dwarf may [[tantrum|break furniture or attack others]]. Continuous stress will cause them to go [[insanity|berserk, becoming suicidal or going insane]] before their eventual deaths. Their quality of life can be improved by giving them luxurious personal bedrooms and a well-decorated dining room, [[health care|medical care]], and providing them with a variety of drinks and [[prepared meal|well-cooked meals]]. A [[tantrum spiral|chain reaction]] where a single dwarf's unhappiness causes the entire fortress's population to start throwing tantrums can begin when one dwarf throws a tantrum, attacks and kills another one with many friends, which drastically affects the happiness of many more.

As the fortress expands and develops, new [[noble]] positions become available. While regular dwarves will be happy with simple rooms provided to them, dwarves appointed or elected to noble positions will need more luxurious accommodation. Most nobles will even make [[demand]]s and [[mandates]], getting negative thoughts if they are not fulfilled. A [[justice]] system is present to punish [[crime|criminals]], for example, dwarves who injure or kill another dwarf or destroy furniture. Occasionally, a [[vampire]] dwarf, with a fake background history, may arrive with a migrant wave and start killing and feeding on the other citizens without being noticed.

Inspired or stressed dwarves will occasionally get into a "[[strange mood]]". They will take over a workshop and go searching for the required materials to begin construction of an [[artifact]]. If they cannot find the materials, the dwarf will wait at the workshop, demanding it till it is available. After a few in-game weeks, the work results in a legendary artifact, an item so masterfully crafted that it is usually worth more than a beginning fortress' total wealth put together. These artifacts will be added to the world's records and its exact description can be viewed. Through this entire period of being in a strange mood, a dwarf will not eat, drink or sleep and will eventually go [[insane]] if prolonged due to any reason.

====Threats, defense and digging deeper====
The first in-game year will usually consist of [[kobold]] [[thieves]] and [[goblin]] snatchers trying to infiltrate the fortress. Thieves try to steal valuables while snatchers try to kidnap dwarven [[children]] to raise them as future soldiers. Goblin and kobold civilizations near the fortress will always be hostile and a source of frequent attacks. Wildlife is usually harmless, but depending on the fortress's location, more fierce [[bear]]s, [[unicorn]]s, [[giant cave spider]]s and [[wolf|wolves]] may be a threat. [[Wealth]]ier and more [[immigration|populated]] fortresses will get [[ambush]]es and [[siege]]s from neighboring goblin (or other enemy) civilizations. A thriving fortress will attract certain [[megabeasts]] like [[hydra]]s, [[titan]]s or [[dragon]]s, and randomly-generated creatures called "[[Forgotten Beasts]]". These unique creatures have randomized physical qualities and abilities, thus making them have the potential to be very powerful. [[Undead]] attack mainly in evil biomes or if the player embarks with a [[Necromancer]] [[Tower (necromancy)|Tower]] being near the site. Undead are harder to kill, and often reanimate once they are defeated with their body parts being separate units to fight.

[[Military]] [[squad]]s can be assigned to a [[barracks]] to [[training|train]] in and a uniform (armor and a weapon) can be chosen. Squads can be directly commanded to [[attack]] enemies. [[Crossbow]]s can be made for ranged attacks and a [[Archery target|range with targets]] can be constructed for training. [[Wall]]s can be carved into [[fortification]]s and be used by ranged-units during attacks. Players can use [[trap]]s and [[engineer|engineering]] in addition to training an army. Traps can be made by constructing [[mechanisms]] and using metal or wood to construct large weapons like spikes, ax blades or [[cage]]s. More complex [[lever]]-operated and [[pressure plate]]-triggering trap components are available.

[[File:Combat report.png|thumb|left|Combat messages being displayed during Fortress Mode. Each message describes weapons striking specific parts of the combatants' bodies with organs getting pierced or limbs getting severed.]]
The [[combat]] system in ''Dwarf Fortress'' is [[anatomy|anatomically]] detailed. Combat is displayed by viewing the log which describes each weapon striking a specific part of the character's body. Internal organs can get punctured, combatants can fall to the ground, [[vomit]] and lose body parts. Each dwarf has individually detailed limbs, each with damageable bone, fat, muscle and skin. Fat can be bruised without breaking bones and vice versa. Injuries sometimes can be permanent. There is a medical system where a [[hospital]] can be set up containing [[crutch]]es for disabled dwarves, [[traction bench]]es, [[plaster]]s and cloth for [[cast]]s and bandages, thread for [[suturing]], and [[splint]]s.

[[Dig]]ging deeper is usually done for finding [[magma]], which as a [[fuel|fuel source]], removes the player's dependence on [[coal]] or [[wood]]. Another reason to dig deeper is for searching for specific raw materials, ores or gems. Magma pools or even bigger [[magma sea]]s are found while digging into warm rock. Near magma seas, raw adamantine [[wikipedia: stratum|strata]] can be found. They are shaped like columns, which pass down through the entire magma sea. These columns are hollow and can be broken, revealing an entire shaft leading deeper into the [[hell|underworld]]. [[Demon|Underworld creatures]] are countless and can bring entire fortresses to [[ruin]].

===Adventure mode===
{{main|Adventure mode}}
[[Adventure mode]] is a roguelike played in the generated world, and unlike Fortress mode, it is turn-based. In this mode, there is character creation similar to other role-playing games - players can choose a name, [[gender]] and spend points on specific combat and physical skills, where the amount depends on whether the player chooses a peasant, hero or demigod. The player's character starts off in a random town of their chosen civilisation, depending on their race, and can interact with the various [[wikipedia: non-player character|non-player character]]s (NPCs). NPCs can give quests (usually to slay an outlaw or megabeast), speak about the surrounding areas, or offer to follow and help the player. Players can choose to explore any part of the generated world using quick-travel mode. A player can find the area of their previously-slain character, visit old abandoned fortresses, or seek out their treasures and wield previously-made artifacts. Instead of quitting, the character can be retired, and depending on the player's achievements, their life events will be documented in the Legends Mode among the other historical figures.

==History==
{{main|History of Adventure Mode|History of Dwarf Fortress}}
===Early development (2002–2006)===
[[File:Tarn Adams.jpg|thumb|alt=Tarn Adams|Tarn Adams in 2013; he has been designing games since high school]]
[[File:ZachAdams.jpg|thumb|alt=Zach Adams|His older brother, Zach, who helped him with his game projects and ''Dwarf Fortress'']]
One of Tarn and Zach Adams' early works was a [[wikipedia: text based adventure game|text based adventure game]] called ''dragslay'', written in the [[wikipedia: BASIC|BASIC]] language and influenced by ''[[wikipedia: Dungeons and Dragons|Dungeons and Dragons]]''. This was the brothers' first fantasy project. In high school, Tarn Adams taught himself the [[wikipedia: C (programming language)|C programming language]] and developed it further. ''dragslay'' would later have an important influence on ''Dwarf Fortress''. Adams explained his interest in [[wikipedia: fantasy|fantasy games]], that he had grown up "surrounded by that sort of thing...along with generic sci-fi, generic fantasy is part of our heritage." Years later, before entering graduate school in mathematics, Adams began working on a project he called ''Slaves to Armok: God of Blood''. It was named after a deity in ''dragslay'', originally named for a variable "arm_ok"—which counted the limbs the player still had attached. This new project was a two-dimensional (would later have [[wikipedia: 3D graphics|3D graphics]]) [[wikipedia: isometric 3d|isometric]] fantasy role-playing game in which the player encountered and fought goblins.

Tarn took some time off ''Armok'' to work on small side-projects, and another one which would inspire ''Dwarf Fortress'' was ''Mutant Miner''. It was [[wikipedia: turn-based strategy|turn-based]] loosely inspired by a game called ''Miner VGA''. ''Mutant Miner'' involved the player digging underneath buildings, searching for ores and fighting monsters, and carrying radioactive "goo" back to the surface for application in growing extra limbs and gaining other abilities. Adams was dissatisfied with only having a single miner, and the game began to lag because it was turn-based. Adams said:

<blockquote>instead of rewriting the game, I thought, well maybe it should be dwarves instead. And it should be real-time to combat the [lag] problem. Now, you'd be digging out minerals in a mountain, combating threats inside, and making little workshops. Then I thought, well, how should the high score list work? We really like to keep records of plays. Not just high score lists, but expansive logs. So we'll often try to think of ways to play with the idea. This time, the idea was to let your adventurer come into the fortress after you lose and find the goblets you've made, and journals it generates.</blockquote>

===First release (2006)===
Adams began working on ''Dwarf Fortress'' in October 2002, estimating that the project would take two months, but suspended development soon after, in order to finish his previous work, ''Armok''. He explained that it began like the 1982 arcade game ''[[wikipedia: Dig Dug|Dig Dug]]''. The Adams brothers started the Bay 12 Games company, launching its website and releasing their games online. By 2004, Adams announced on his website that he would be switching his main project to ''Dwarf Fortress'' after he struggled to continue working on ''Armok'', after all its added features became harder to maintain. Adams explained that it would be a dwarf [[wikipedia: simulation game|simulation game]] but he kept Adventure mode as a surprise feature, which was revealed during its release. At that time, his fan base consisted of a few dozen people and more came in when he made this announcement. He put up a [[wikipedia: PayPal|PayPal]] button after a request from a fan; similarly, a subscriber system was added later. In the next five months, they made around $300, which brought in only enough to cover the site's $20 hosting cost. He dubbed the game as ''Slaves to Armok, God of Blood II: Dwarf Fortress''; Adams explained that it was a sequel because it continued to work on much of ''Armok's'' code but said its cumbersome name was mostly "for kicks."

Adams decided to focus on the game's development full-time during his first year of his math post-doctorate at [[wikipedia: Texas A&M|Texas A&M]] in 2006.
He quit it after a year and decided to use up his $15,000 savings. The university offered him $50,000 if he would stay another year. Adams agreed and commented on this, "I woke up the morning after I gave notice, like, I can actually make this work." Adams expected he would have to get a job in order to support himself and use his savings because the game had not been released yet. Development continued till 8 August 2006, when the first [[wikipedia: alpha version|alpha version]] (version 0.21.93.19a) was released. Donations reached $800–$1000 in the following months, this average increased gradually till they were financially stable. He then decided to solely rely on donations.

===Development (2007–present)===
Adams did not use the 3D graphics which ''Armok'' had since its development was hampered because of it. He cited the ease in development of features like [[wikipedia: fluid simulation|fluid simulation]], copyright issues with the art and more unhindered possibilities as further reasons for not using it. Being used to the text-based graphics in [[wikipedia: roguelike|roguelike]]s, he did not want graphical [[wikipedia: Tile-based video game|tilesets]]. The story-generation originated first from ''Armok'', although present to some extent in ''dragslay''. Tarn and Zach would write different chapters of events they would like to see, mix it together and try to implement it. Most of this story writing is managed by Zach, who has a role in the game's development. He graduated in ancient history and books like ''[[wikipedia: The Twelve Caesars|The Twelve Caesars]]'' and the writings of [[wikipedia: Assyria|Assyria]]n kings influenced the game.

Tarn Adams was influenced by roguelike games like 1985 ''[[wikipedia: Hack (Unix video game)|Hack]]'' because of its randomly generated levels and detailed mechanics. The body part and wound system was inspired by 1990 role-playing game ''[[wikipedia: Cyberpunk 2020|Cyberpunk 2020]]''. Adams cited ''[[wikipedia: Ultima series|Ultima series]]'' as the inspiration for his generated worlds. He prefers modeling on individual elements, rather than entire systems, for better simulations with the outcomes being under his control. During world generation, he made an algorithm to simulate [[wikipedia: rain shadow|rain shadow]]s which occur in areas at the side of mountain deserts. For the distinct personalities of each unit, he took it from [[wikipedia: NEO PI-R|NEO PI-R test]] of which he admitted knowing little about. The feature of [[wikipedia: carp|carp]]s eating dwarves was unexpected when the game was released. He had written them having the same size and carps were designed to be carnivorous. Adams composed the game's [[wikipedia: Flamenco guitar|flamenco-inspired]] music.

A z-axis was introduced in the 2008 release because he felt the limitations with a single plane increasing; the feature of making various constructions like walls was also added at this time. In the earlier version, players could dig only into a mountainside and not underground because of having only one "z-level", thus it was considered "[[wikipedia: two-dimensional space|2D]]". This was significantly easier to maintain due to the limited playable area. Adams commented that this major change was further difficult to implement because of considering details like [[wikipedia: fluid mechanics|fluid mechanics]] and cave-ins. In 2012, more traps, abilities, [[wikipedia: syndrome|syndrome]]s, detailed cities and tombs were added in addition to vampiric and [[wikipedia: lycanthropic|lycanthropic]] infections, necromancers and undead.

On his reliance on PayPal donations, Adams says he is content since he feels that people really like his work or they would not pay. Ever since its release, donations kept increasing and remaining stable except having a sudden increase during a new version update. He got $50,000 in 2010 following a major update after a long gap. Their expenses being low, he has maintained that he is happy as long as the game is self-sustaining and will not charge for it. In 2011, Adams refused a job offer from an unspecified major game developer and a $300,000 deal to license the name ''Dwarf Fortress'' from another company. Adams felt that this amount would not equate to the long-term donations he would receive. Adams said that he prefers working on his own and not being part of the gaming industry. In 2013, his average income was $4000 a month and Adams said, "Barely in the black one month, a little in the red another month. ... It's a risk I'm willing to take, and really I couldn't have it any other way." He has spent no money on advertising and was happy when bloggers, reviewers like former game journalist [[wikipedia: Kieron Gillen|Kieron Gillen]] from ''[[wikipedia: PC Gamer|PC Gamer]]'' and ''[[wikipedia: Games for Windows|Games for Windows]],'' wrote about his game. In 2015, Bay 12 Games set up a [[wikipedia: Patreon|Patreon]] account to help fund ''Dwarf Fortress''.

In March of 2019, indie game studio [[wikipedia: Kitfox Games|Kitfox Games]] announced that they would be helping Bay 12 create a version of ''Dwarf Fortress'' for release on Steam with graphics, additional music, and a completely reworked UI. A sudden family health crisis, combined with the rising costs of healthcare and the instability of a Patreon-based income, made the Adamses reconsider their previous stances about remaining aloof from the games industry. Tanya X. Short, the Captain of Kitfox, was a personal friend of Tarn and offered to help with the project. The original version of the game remains available for free and will receive all of the same content updates as the Steam version. On November 1, 2022, Kitfox announced that the Steam version would be released on December 6 of that year.

===Further updates===
As of 2016 February, the latest update was version 0.42.06, years in development despite being in alpha version. Adams says he has been able to maintain focus by shifting his attention to different aspects of the game, given its numerous varied features. While regular game development aim to perfect their work for release, he considers this a drawback since he continues exploring and learning while adding new features. ''[[wikipedia: Wired (magazine)|Wired]]'' and [[wikipedia: Rock, Paper, Shotgun|Rock, Paper, Shotgun]] noted its sometimes funny but unintentional bug fixes, with ''PC Gamer'' saying it makes an entertaining [[wikipedia: RSS feed|RSS feed]] to subscribe to. Adams has two favorite bugs. One is about a farmer dwarf planting their own bed. The other involves a dwarven executioner, with broken arms unable to use his hammer, delivering punishments by biting his victims and tearing off their limbs, keeping one in his mouth for years.

Tarn Adams considers ''Dwarf Fortress'' his life's work, and has stated in 2011 that he does not expect version 1.0 to be released for at least another twenty years, and even after that, he would still continue to update it. Adams calls his game an open-ended "story generator". The game's code base is [[wikipedia: closed source|proprietary]], and Adams has stated he has no plans to release it into the [[wikipedia: open source|open source]] domain, citing the risk of them going into financial trouble. He acknowledged the role of the community in supporting its development and has endorsed third-party tools, visualizers and interface code. He explained he would consider releasing its source if he could not maintain it anymore, seeing different game developers taking it up. He says that he does not mind any modifications as long as he is not put into risk.

Adams describes version 1.0 having an Adventure mode that would be a regular role-playing game, with changing plots and ordering subordinates to perform various tasks. Fortress mode would have a closer relationship with the outside generated world through war, trade and diplomacy. The world being bigger; he envisions the game to have many more features like magic, a tutorial, and a better interface. According to him, a tutorial is a burden because of the additional need of updating it. He said of version 1.0, "sitting down with a fresh DF world would be like sitting down to read a middling fantasy author you haven't read before, but with all the extras that being a video game provides, including the ability to write your own sequels." Modern in-game technologies and 3D graphics were fan requests Adams said he would never implement, yet showing ambivalence about the latter if the task was easy enough.

==Reception==
{{main|Reception of Dwarf Fortress}}

==Community==
{{main|Community of Dwarf Fortress}}

==Legacy==
{{main|Legacy of Dwarf Fortress}}

[[Category: game| ]]
{{unversioned}}

Dwarf Fortress

2022-11-08T10:37:07Z

Xjtu-blacksmith: /* Threats, defense and digging deeper */ Kennel is not for animal training in current version

{{DISPLAYTITLE:''Dwarf Fortress''}}
[[File:Df logo.png|thumb|350px|Official logo]]

'''''Dwarf Fortress''''' (officially '''''Slaves to Armok: God of Blood Chapter II: Dwarf Fortress''''', referred to as '''DF''') is a part [[wikipedia: Construction and management simulation|construction and management simulation]], part [[wikipedia: roguelike|roguelike]], [[wikipedia: indie video game|indie]] video game created by [[Tarn Adams|Tarn]] (Toady One) and [[Zach Adams]] (ThreeToe). [[wikipedia: Freeware|Freeware]] and in development since 2002, its first [[wikipedia: alpha version|alpha version]] was released in 2006 and it received attention for being a two-member project surviving [[donation|solely on donations]]. The primary game mode is set in a [[wikipedia: procedurally generated|procedurally generated]] fantasy [[world]] in which the player indirectly controls a group of [[dwarves]], and attempts to construct a successful and [[wealth]]y [[fortress]]. Critics praised its complex, [[wikipedia: emergent gameplay|emergent gameplay]] but had mixed reactions to its [[Fun|difficulty]]. The game influenced ''[[wikipedia: Minecraft|Minecraft]] ''and was selected among other games to be featured in the [[wikipedia: Museum of Modern Art|Museum of Modern Art]] to show the history of video gaming in 2012.

The game has [[wikipedia: Text-based game|text-based]] graphics and is [[wikipedia: open-ended (gameplay)|open-ended]] with no main objectives. Before being played, the player has to [[world generation|generate]] worlds with continents, [[ocean]]s and histories documenting [[civilizations]]. The main game mode, [[Fortress Mode]], consists of selecting a suitable [[site]] from the generated-world, establishing a successful colony or fortress, combating threats like [[goblin]] [[invader|invasions]], generating wealth and taking care of the dwarves. Each dwarf is modeled down to its individual [[personality]], has [[Preferences|likes or dislikes]] and specific trainable [[skill]]s in various [[labor]]s, alongside a lovelife system and distractions. The second game mode, [[Adventure mode]], is a [[wikipedia: turn-based|turn-based]], open-ended roguelike where the player starts off as an [[adventurer]] in the world and is free to explore, complete quests, or even visit old [[ruin|abandoned fortresses]]. The [[combat|combat system]] is [[Anatomy|anatomically detailed]] with combat logs describing organs getting pierced, fat getting bruised and [[Body parts|limbs getting severed]].

Prior to ''Dwarf Fortress'', Tarn Adams was working on a project called ''Slaves to [[Armok]]: God of Blood'' which was a [[wikipedia: role-playing game|role-playing game]]. By 2004, Adams decided to shift from the original ''Armok'' to ''Dwarf Fortress'' after the former became difficult to maintain. Adams calls it his life's work and said in 2011, that version 1.0 will not be ready for at least another 20 years, and even after that he would continue to work on it. The game has a [[wikipedia: cult following|cult following]] and an active online community. As there is no way to win, every fortress, no matter how successful, is usually destroyed somehow. This prompts the unofficial community motto: "[[Losing is Fun]]!"

==Gameplay==

===Overview and game modes===
''Dwarf Fortress'' has three primary game modes which take place in worlds created by the player, where most of the elements are randomly generated. [[Fortress Mode]] is a [[wikipedia: construction and management simulation|construction and management simulation]] of a colony of [[dwarves]]. There are no objectives, with the player being free to decide how to go about managing the colony and making them interact with the environment, thus making it an [[wikipedia: open-ended (gameplay)|open-ended]] and [[wikipedia: Sandbox game|sandbox]]-style game. Since there is no way to win, it only ends when the entire colony is [[Losing|defeated by the various possible threats]]. The visuals are [[wikipedia: Text-based game|text-based]] using [[wikipedia: code page 437|code page 437]] characters in various [[color]]s as graphics. Thus, it is fully of letters, numbers and symbols; dwarves are represented by different colored smiling faces, a [[cat]] and [[dog]] are a white "c" and brown "d", while a [[giant cave spider]] is a grey "S".

[[Adventure mode]] is a [[wikipedia: turn-based|turn-based]], open-ended [[wikipedia: roguelike|roguelike]] where the player starts off as an adventurer. In [[Legends mode]], players can view maps, histories of each civilization and any figure who has lived or died in the generated world. Any noticeable achievement made by the player in any of the two game modes is recorded in the Legends. An [[object testing arena]] is present, where players can simulate battles between selected units in various conditions.

===World generation===
{{Main|World generation}}
[[File:WorldGenerationScreen.png|thumb|left|A world being generated and the years being counted. Each game is played in such generated worlds.]]
The first step in ''Dwarf Fortress'' is generating a [[World generation|playable world]]; only one game can be played per world at a time. The player can adjust certain [[World_generation#Parameters|parameters]] governing size, [[Surroundings|savagery]], mineral occurrences and the length of history. The map shows symbols representing [[road]]s, [[hill]]s, [[town]]s and [[cities]] of the various [[civilization]]s, and it changes as the generation progresses. A [[wikipedia: midpoint displacement algorithm|midpoint displacement algorithm]] generates the world.

The process involves [[wikipedia: procedurally generated|procedurally-generated]] basic elements like elevation, [[rain]]fall, mineral distribution, drainage and [[temperature]], using [[wikipedia: fractals|fractals]] (which give it an overall natural look). For example, a high-rainfall and low-drainage area would make a [[swamp]]. Areas are thus categorized into [[biome]]s, which have two variables: savagery and [[wikipedia: Alignment (role-playing games)|alignment]]. They have their own specific type of [[plant]] and [[animal]] populations. The next phase is erosion—which the drainage tries to simulate. [[River]]s are created by tracing their paths from the [[mountain]]s (which get eroded) to its end which is usually an [[ocean]]; some form into [[lake]]s. The salinity field defines oceans, [[mangrove]]s or [[alluvial]] plains. Names are generated for the biomes and rivers. The names depend on the area's [[good]]/[[evil]] variable (the [[alignment]]) and though in English, they are originally in one of the four [[language|in-game language]]s of [[dwarves]], [[elves]], [[human]]s and [[goblin]]s; these are the four main races in any generated world.

After a few minutes the world is populated and its history develops for the amount of in-game [[year]]s selected in the history parameter. Civilizations, races and religions spread and [[war]]s occur, with the "population" and "deaths" counters increasing. The ticker stops at the designated "years" value, at which point the world can be saved for use in any game mode. Should the player choose to retire a [[Dwarf fortress mode|fortress]] or gets [[losing|defeated]], this world will persist and will become available for further games.

===Fortress mode===
{{Main|Dwarf fortress mode}}
====Basics====
[[File:Embark A Map.png|thumb|The game uses text symbols for graphics. For example, a dwarf is a colored smiling face and various other letters represent animals. Here, dwarves and livestock around their wagon of supplies can be seen just after embark.]]

When Fortress mode is selected, the player is given the option to choose the [[embark|embark location]] in the world. The player must consider the environment, elevations, biome, soil types and mineral concentrations, which can pose significant challenges to the development or survival of the fortress.The colony's [[supplies]], [[domestic animals]], and skills can be customised, but each dwarf's [[mental attributes|mental]] and [[physical attributes]] are randomly generated,as are their mental abilities, individual preferences and desires. The game also describes in detail each dwarf's [[Physical_description|physical appearance]], like hair and facial features.. Each dwarf's [[relationships]] with others and the [[deities]] they worship can be viewed.

The player embarks with the expedition team (seven dwarves, and their livestock and supplies by default), and does not have direct control over them. In order to construct and operate the fortress, the dwarves undertake [[labour]]s as designated by the player. They can be assigned any labors, but their work still depends on their relative skill with it, which can increase. Some task categories are stone-working, woodworking, metalworking, farming-related and crafts-making; there are further combat-related skills. They are categorized further, such as [[leatherworking]], [[butchery]], [[clothesmaking]], [[gem]]-related, [[glassmaking]], and [[clay]]-related [[Industry|industries]]. Activities take place in [[workshop]]s which need to be constructed; for example, [[still]]s for brewing alcohol. The [[metal industry]] has a very important role because it produces [[weapon]]s and [[armor]] for the [[military]], [[trap component]]s for defense, and high-value [[furniture]] and [[decoration]]s.

==== Functional mechanics ====
The player initially can see a [[wikipedia: top-down view|top-down view]] of the surface-level of the fortress site; each [[layer]] of a [[z-axis]] [[z-level|level]] can be viewed when the player changes it. An entire underground level would be seen as its entire section of terrain while a mountain at the surface level would have only its section visible with the remaining surface landscape. Thus, for [[dig]]ging, the player can designate, for every z-level starting from the surface, [[staircase]]s to be carved and at the final designated level, ending the staircase by making it dug into a room.

The [[geology]] in ''Dwarf Fortress'' is fairly accurate. Rocks like [[olivine]] or [[gabbro]] can be dug up, while the topmost layer usually consists of [[sand]], [[clay]] or plain [[soil]]—this can be used for underground [[farming]]. Deeper levels are layers of rock; minerals appear in layers or [[cluster]]s around the right depth, while [[gem]]s like [[tourmaline]]s appear in rare clusters. [[Water]] is simulated like falling sand, every space can contain up to seven levels of it. A tile having "one" level of water is the lowest while a tile with "seven" is full. There is a system for simulating temperature and heat. [[Fire]]s can spread and burn dwarves and furniture. There are four basic [[season]]s in an in-game year as in real life: spring, summer, autumn and winter.

[[ore|Mineral ores]] can be mined just like normal stone and the raw ore can be [[smelting|smelted]] to produce their corresponding [[metal bars]]. Different ores or metal bars can be [[alloy]]ed together for higher quality materials. For [[steel]] production, [[flux]] stones are used to make [[pig iron]] bars and smelt it with regular [[iron]] and [[coal]] (or [[charcoal]]). Specific metal items can be melted back to their respective bars. Without steel, the alloy [[bronze]] or regular iron are the next best suitable metals to use. Bronze requires two ores or bars of [[tin]] and [[copper]]. The metal [[adamant]]ine, found deep below, is extremely light but very strong, making it excellent for sharp weapons and armor. [[Raw adamantine]] can be [[Strand extractor|extracted into strands]] and can further be either woven in cloth or smelted into [[wafer]]s.

==== Fortress management and growth ====
Underground [[farming]] has customized crops like "[[plump helmet]]" mushrooms, which can be [[brewer|brewed]] to make [[dwarven wine|mushroom wine]]. As the fortress prospers, [[migrant]]s come in larger numbers from the [[mountain halls|mountainhome]] (the colony's home civilization) and will need further accommodation. [[Trading|Trading caravans]], which can be from the various neighboring civilizations including the home civilization, visit the fortress on a yearly basis and are useful for getting supplies not available in the player's fortress area. The role of [[record keeper]], [[manager]] and [[broker]] can be assigned to any dwarf during early game. The record keeper maintains records of every item present in the fort, the manager [[work order|auto-assigns jobs]] and the broker deals with trading caravans. The production of [[craft]]s from any material are useful for trading. The caravans come from civilizations of [[elves]] and [[humans]] but depending on the embark region and history, they may be absent or sometimes even hostile.

Dwarves need to be provided with [[food]] and [[drink]] (mostly in the form of [[alcohol]]). A dwarf will get [[negative thoughts]] for drinking plain water and even for drinking the same type of alcohol, making it necessary to grow different crops for producing different drinks. Things like not having a separate [[bedroom]] can upset a dwarf. They may make [[friend]]s and sometimes [[marriage|marry]]; females give birth. Dwarves can get upset by sustaining [[injuries]], having poor [[clothing]], [[death|losing]] their [[pet]]s, friends or relatives; interacting with or seeing their [[corpse]]s can aggravate this. A frustrated dwarf may [[tantrum|break furniture or attack others]]. Continuous stress will cause them to go [[insanity|berserk, becoming suicidal or going insane]] before their eventual deaths. Their quality of life can be improved by giving them luxurious personal bedrooms and a well-decorated dining room, [[health care|medical care]], and providing them with a variety of drinks and [[prepared meal|well-cooked meals]]. A [[tantrum spiral|chain reaction]] where a single dwarf's unhappiness causes the entire fortress's population to start throwing tantrums can begin when one dwarf throws a tantrum, attacks and kills another one with many friends, which drastically affects the happiness of many more.

As the fortress expands and develops, new [[noble]] positions become available. While regular dwarves will be happy with simple rooms provided to them, dwarves appointed or elected to noble positions will need more luxurious accommodation. Most nobles will even make [[demand]]s and [[mandates]], getting negative thoughts if they are not fulfilled. A [[justice]] system is present to punish [[crime|criminals]], for example, dwarves who injure or kill another dwarf or destroy furniture. Occasionally, a [[vampire]] dwarf, with a fake background history, may arrive with a migrant wave and start killing and feeding on the other citizens without being noticed.

Inspired or stressed dwarves will occasionally get into a "[[strange mood]]". They will take over a workshop and go searching for the required materials to begin construction of an [[artifact]]. If they cannot find the materials, the dwarf will wait at the workshop, demanding it till it is available. After a few in-game weeks, the work results in a legendary artifact, an item so masterfully crafted that it is usually worth more than a beginning fortress' total wealth put together. These artifacts will be added to the world's records and its exact description can be viewed. Through this entire period of being in a strange mood, a dwarf will not eat, drink or sleep and will eventually go [[insane]] if prolonged due to any reason.

====Threats, defense and digging deeper====
The first in-game year will usually consist of [[kobold]] [[thieves]] and [[goblin]] snatchers trying to infiltrate the fortress. Thieves try to steal valuables while snatchers try to kidnap dwarven [[children]] to raise them as future soldiers. Goblin and kobold civilizations near the fortress will always be hostile and a source of frequent attacks. Wildlife is usually harmless, but depending on the fortress's location, more fierce [[bear]]s, [[unicorn]]s, [[giant cave spider]]s and [[wolf|wolves]] may be a threat. [[Wealth]]ier and more [[immigration|populated]] fortresses will get [[ambush]]es and [[siege]]s from neighboring goblin (or other enemy) civilizations. A thriving fortress will attract certain [[megabeasts]] like [[hydra]]s, [[titan]]s or [[dragon]]s, and randomly-generated creatures called "[[Forgotten Beasts]]". These unique creatures have randomized physical qualities and abilities, thus making them have the potential to be very powerful. [[Undead]] attack mainly in evil biomes or if the player embarks with a [[Necromancer]] [[Tower (necromancy)|Tower]] being near the site. Undead are harder to kill, and often reanimate once they are defeated with their body parts being separate units to fight.

[[Military]] [[squad]]s can be assigned to a [[barracks]] to [[training|train]] in and a uniform (armor and a weapon) can be chosen. Squads can be directly commanded to [[attack]] enemies. [[Crossbow]]s can be made for ranged attacks and a [[Archery target|range with targets]] can be constructed for training. [[Wall]]s can be carved into [[fortification]]s and be used by ranged-units during attacks. Players can use [[trap]]s and [[engineer|engineering]] in addition to training an army. Traps can be made by constructing [[mechanisms]] and using metal or wood to construct large weapons like spikes, ax blades or [[cage]]s. More complex [[lever]]-operated and [[pressure plate]]-triggering trap components are available.

[[File:Combat report.png|thumb|left|Combat messages being displayed during Fortress Mode. Each message describes weapons striking specific parts of the combatants' bodies with organs getting pierced or limbs getting severed.]]
The [[combat]] system in ''Dwarf Fortress'' is [[anatomy|anatomically]] detailed. Combat is displayed by viewing the log which describes each weapon striking a specific part of the character's body. Internal organs can get punctured, combatants can fall to the ground, [[vomit]] and lose body parts. Each dwarf has individually detailed limbs, each with damageable bone, fat, muscle and skin. Fat can be bruised without breaking bones and vice versa. Injuries sometimes can be permanent. There is a medical system where a [[hospital]] can be set up containing [[crutch]]es for disabled dwarves, [[traction bench]]es, [[plaster]]s and [cloth for [[cast]]s and bandages, thread for [[suturing]], and [[splint]]s.

[[Dig]]ging deeper is usually done for finding [[magma]], which as a [[fuel|fuel source]], removes the player's dependence on [[coal]] or [[wood]]. Another reason to dig deeper is for searching for specific raw materials, ores or gems. Magma pools or even bigger [[magma sea]]s are found while digging into warm rock. Near magma seas, raw adamantine [[wikipedia: stratum|strata]] can be found. They are shaped like columns, which pass down through the entire magma sea. These columns are hollow and can be broken, revealing an entire shaft leading deeper into the [[hell|underworld]]. [[Demon|Underworld creatures]] are countless and can bring entire fortresses to [[ruin]].

===Adventure mode===
{{main|Adventure mode}}
[[Adventure mode]] is a roguelike played in the generated world, and unlike Fortress mode, it is turn-based. In this mode, there is character creation similar to other role-playing games - players can choose a name, [[gender]] and spend points on specific combat and physical skills, where the amount depends on whether the player chooses a peasant, hero or demigod. The player's character starts off in a random town of their chosen civilisation, depending on their race, and can interact with the various [[wikipedia: non-player character|non-player character]]s (NPCs). NPCs can give quests (usually to slay an outlaw or megabeast), speak about the surrounding areas, or offer to follow and help the player. Players can choose to explore any part of the generated world using quick-travel mode. A player can find the area of their previously-slain character, visit old abandoned fortresses, or seek out their treasures and wield previously-made artifacts. Instead of quitting, the character can be retired, and depending on the player's achievements, their life events will be documented in the Legends Mode among the other historical figures.

==History==
{{main|History of Adventure Mode|History of Dwarf Fortress}}
===Early development (2002–2006)===
[[File:Tarn Adams.jpg|thumb|alt=Tarn Adams|Tarn Adams in 2013; he has been designing games since high school]]
[[File:ZachAdams.jpg|thumb|alt=Zach Adams|His older brother, Zach, who helped him with his game projects and ''Dwarf Fortress'']]
One of Tarn and Zach Adams' early works was a [[wikipedia: text based adventure game|text based adventure game]] called ''dragslay'', written in the [[wikipedia: BASIC|BASIC]] language and influenced by ''[[wikipedia: Dungeons and Dragons|Dungeons and Dragons]]''. This was the brothers' first fantasy project. In high school, Tarn Adams taught himself the [[wikipedia: C (programming language)|C programming language]] and developed it further. ''dragslay'' would later have an important influence on ''Dwarf Fortress''. Adams explained his interest in [[wikipedia: fantasy|fantasy games]], that he had grown up "surrounded by that sort of thing...along with generic sci-fi, generic fantasy is part of our heritage." Years later, before entering graduate school in mathematics, Adams began working on a project he called ''Slaves to Armok: God of Blood''. It was named after a deity in ''dragslay'', originally named for a variable "arm_ok"—which counted the limbs the player still had attached. This new project was a two-dimensional (would later have [[wikipedia: 3D graphics|3D graphics]]) [[wikipedia: isometric 3d|isometric]] fantasy role-playing game in which the player encountered and fought goblins.

Tarn took some time off ''Armok'' to work on small side-projects, and another one which would inspire ''Dwarf Fortress'' was ''Mutant Miner''. It was [[wikipedia: turn-based strategy|turn-based]] loosely inspired by a game called ''Miner VGA''. ''Mutant Miner'' involved the player digging underneath buildings, searching for ores and fighting monsters, and carrying radioactive "goo" back to the surface for application in growing extra limbs and gaining other abilities. Adams was dissatisfied with only having a single miner, and the game began to lag because it was turn-based. Adams said:

<blockquote>instead of rewriting the game, I thought, well maybe it should be dwarves instead. And it should be real-time to combat the [lag] problem. Now, you'd be digging out minerals in a mountain, combating threats inside, and making little workshops. Then I thought, well, how should the high score list work? We really like to keep records of plays. Not just high score lists, but expansive logs. So we'll often try to think of ways to play with the idea. This time, the idea was to let your adventurer come into the fortress after you lose and find the goblets you've made, and journals it generates.</blockquote>

===First release (2006)===
Adams began working on ''Dwarf Fortress'' in October 2002, estimating that the project would take two months, but suspended development soon after, in order to finish his previous work, ''Armok''. He explained that it began like the 1982 arcade game ''[[wikipedia: Dig Dug|Dig Dug]]''. The Adams brothers started the Bay 12 Games company, launching its website and releasing their games online. By 2004, Adams announced on his website that he would be switching his main project to ''Dwarf Fortress'' after he struggled to continue working on ''Armok'', after all its added features became harder to maintain. Adams explained that it would be a dwarf [[wikipedia: simulation game|simulation game]] but he kept Adventure mode as a surprise feature, which was revealed during its release. At that time, his fan base consisted of a few dozen people and more came in when he made this announcement. He put up a [[wikipedia: PayPal|PayPal]] button after a request from a fan; similarly, a subscriber system was added later. In the next five months, they made around $300, which brought in only enough to cover the site's $20 hosting cost. He dubbed the game as ''Slaves to Armok, God of Blood II: Dwarf Fortress''; Adams explained that it was a sequel because it continued to work on much of ''Armok's'' code but said its cumbersome name was mostly "for kicks."

Adams decided to focus on the game's development full-time during his first year of his math post-doctorate at [[wikipedia: Texas A&M|Texas A&M]] in 2006.
He quit it after a year and decided to use up his $15,000 savings. The university offered him $50,000 if he would stay another year. Adams agreed and commented on this, "I woke up the morning after I gave notice, like, I can actually make this work." Adams expected he would have to get a job in order to support himself and use his savings because the game had not been released yet. Development continued till 8 August 2006, when the first [[wikipedia: alpha version|alpha version]] (version 0.21.93.19a) was released. Donations reached $800–$1000 in the following months, this average increased gradually till they were financially stable. He then decided to solely rely on donations.

===Development (2007–present)===
Adams did not use the 3D graphics which ''Armok'' had since its development was hampered because of it. He cited the ease in development of features like [[wikipedia: fluid simulation|fluid simulation]], copyright issues with the art and more unhindered possibilities as further reasons for not using it. Being used to the text-based graphics in [[wikipedia: roguelike|roguelike]]s, he did not want graphical [[wikipedia: Tile-based video game|tilesets]]. The story-generation originated first from ''Armok'', although present to some extent in ''dragslay''. Tarn and Zach would write different chapters of events they would like to see, mix it together and try to implement it. Most of this story writing is managed by Zach, who has a role in the game's development. He graduated in ancient history and books like ''[[wikipedia: The Twelve Caesars|The Twelve Caesars]]'' and the writings of [[wikipedia: Assyria|Assyria]]n kings influenced the game.

Tarn Adams was influenced by roguelike games like 1985 ''[[wikipedia: Hack (Unix video game)|Hack]]'' because of its randomly generated levels and detailed mechanics. The body part and wound system was inspired by 1990 role-playing game ''[[wikipedia: Cyberpunk 2020|Cyberpunk 2020]]''. Adams cited ''[[wikipedia: Ultima series|Ultima series]]'' as the inspiration for his generated worlds. He prefers modeling on individual elements, rather than entire systems, for better simulations with the outcomes being under his control. During world generation, he made an algorithm to simulate [[wikipedia: rain shadow|rain shadow]]s which occur in areas at the side of mountain deserts. For the distinct personalities of each unit, he took it from [[wikipedia: NEO PI-R|NEO PI-R test]] of which he admitted knowing little about. The feature of [[wikipedia: carp|carp]]s eating dwarves was unexpected when the game was released. He had written them having the same size and carps were designed to be carnivorous. Adams composed the game's [[wikipedia: Flamenco guitar|flamenco-inspired]] music.

A z-axis was introduced in the 2008 release because he felt the limitations with a single plane increasing; the feature of making various constructions like walls was also added at this time. In the earlier version, players could dig only into a mountainside and not underground because of having only one "z-level", thus it was considered "[[wikipedia: two-dimensional space|2D]]". This was significantly easier to maintain due to the limited playable area. Adams commented that this major change was further difficult to implement because of considering details like [[wikipedia: fluid mechanics|fluid mechanics]] and cave-ins. In 2012, more traps, abilities, [[wikipedia: syndrome|syndrome]]s, detailed cities and tombs were added in addition to vampiric and [[wikipedia: lycanthropic|lycanthropic]] infections, necromancers and undead.

On his reliance on PayPal donations, Adams says he is content since he feels that people really like his work or they would not pay. Ever since its release, donations kept increasing and remaining stable except having a sudden increase during a new version update. He got $50,000 in 2010 following a major update after a long gap. Their expenses being low, he has maintained that he is happy as long as the game is self-sustaining and will not charge for it. In 2011, Adams refused a job offer from an unspecified major game developer and a $300,000 deal to license the name ''Dwarf Fortress'' from another company. Adams felt that this amount would not equate to the long-term donations he would receive. Adams said that he prefers working on his own and not being part of the gaming industry. In 2013, his average income was $4000 a month and Adams said, "Barely in the black one month, a little in the red another month. ... It's a risk I'm willing to take, and really I couldn't have it any other way." He has spent no money on advertising and was happy when bloggers, reviewers like former game journalist [[wikipedia: Kieron Gillen|Kieron Gillen]] from ''[[wikipedia: PC Gamer|PC Gamer]]'' and ''[[wikipedia: Games for Windows|Games for Windows]],'' wrote about his game. In 2015, Bay 12 Games set up a [[wikipedia: Patreon|Patreon]] account to help fund ''Dwarf Fortress''.

In March of 2019, indie game studio [[wikipedia: Kitfox Games|Kitfox Games]] announced that they would be helping Bay 12 create a version of ''Dwarf Fortress'' for release on Steam with graphics, additional music, and a completely reworked UI. A sudden family health crisis, combined with the rising costs of healthcare and the instability of a Patreon-based income, made the Adamses reconsider their previous stances about remaining aloof from the games industry. Tanya X. Short, the Captain of Kitfox, was a personal friend of Tarn and offered to help with the project. The original version of the game remains available for free and will receive all of the same content updates as the Steam version. On November 1, 2022, Kitfox announced that the Steam version would be released on December 6 of that year.

===Further updates===
As of 2016 February, the latest update was version 0.42.06, years in development despite being in alpha version. Adams says he has been able to maintain focus by shifting his attention to different aspects of the game, given its numerous varied features. While regular game development aim to perfect their work for release, he considers this a drawback since he continues exploring and learning while adding new features. ''[[wikipedia: Wired (magazine)|Wired]]'' and [[wikipedia: Rock, Paper, Shotgun|Rock, Paper, Shotgun]] noted its sometimes funny but unintentional bug fixes, with ''PC Gamer'' saying it makes an entertaining [[wikipedia: RSS feed|RSS feed]] to subscribe to. Adams has two favorite bugs. One is about a farmer dwarf planting their own bed. The other involves a dwarven executioner, with broken arms unable to use his hammer, delivering punishments by biting his victims and tearing off their limbs, keeping one in his mouth for years.

Tarn Adams considers ''Dwarf Fortress'' his life's work, and has stated in 2011 that he does not expect version 1.0 to be released for at least another twenty years, and even after that, he would still continue to update it. Adams calls his game an open-ended "story generator". The game's code base is [[wikipedia: closed source|proprietary]], and Adams has stated he has no plans to release it into the [[wikipedia: open source|open source]] domain, citing the risk of them going into financial trouble. He acknowledged the role of the community in supporting its development and has endorsed third-party tools, visualizers and interface code. He explained he would consider releasing its source if he could not maintain it anymore, seeing different game developers taking it up. He says that he does not mind any modifications as long as he is not put into risk.

Adams describes version 1.0 having an Adventure mode that would be a regular role-playing game, with changing plots and ordering subordinates to perform various tasks. Fortress mode would have a closer relationship with the outside generated world through war, trade and diplomacy. The world being bigger; he envisions the game to have many more features like magic, a tutorial, and a better interface. According to him, a tutorial is a burden because of the additional need of updating it. He said of version 1.0, "sitting down with a fresh DF world would be like sitting down to read a middling fantasy author you haven't read before, but with all the extras that being a video game provides, including the ability to write your own sequels." Modern in-game technologies and 3D graphics were fan requests Adams said he would never implement, yet showing ambivalence about the latter if the task was easy enough.

==Reception==
{{main|Reception of Dwarf Fortress}}

==Community==
{{main|Community of Dwarf Fortress}}

==Legacy==
{{main|Legacy of Dwarf Fortress}}

[[Category: game| ]]
{{unversioned}}

Troubleshooting

2022-11-07T02:06:59Z

Xjtu-blacksmith: /* Forums */ add Baidu Tieba

''Dwarf Fortress'' has only one person writing its code. There's a lot of it, and a lot that is quite new, so it's unfortunately inevitable that some imperfections creep in. The game itself is also just extremely complex, and it's easy to become confused.

== FAQ ==
{{main|Frequently asked questions}}
If other documentation has not helped, you might see the [[Frequently Asked Questions|FAQ]] page.

== Bugs ==
{{main|Known bugs and issues}}

Unfortunately, DF is not immune to bugs. While Toady fixes them as fast as he can, you might find some workarounds on the [[Known bugs and issues|known bugs]] page.

[http://www.bay12games.com/dwarves/mantisbt/ Mantis Bug tracker] - Before creating a new bug report, please search the bug tracker first to see if the bug was already reported. When submitting a bug report:

* Make a note of any mods you're using. If you made the mod yourself, include the raws for any relevant objects (use [code] tags).
* If the game is crashing or refusing to open, include any error message that appears, along with your computer specifications and operating system.
* If you have a save that reliably reproduces the bug, it may be helpful to upload the save to the [https://dffd.bay12games.com/ DF File Depot] or another file hosting site.

== Forums and other resources ==

Not to worry, there are plenty of DF players out there and they are generally very friendly. Usually they'll gladly help you figure out your particular daunting dwarvish dilemma. Remember to be polite and use a forum's search function to see if your question has previously been asked before making a new post. If you follow this advice then people will be more than thrilled to help.

===Forums===
*[http://www.bay12forums.com/smf/ Official Forums]
*[http://www.gamingsteve.com/blab/index.php?topic=6350.0 GamingSteve Thread]
*[https://dwarvenpassion.smfforfree3.com/index.php Dwarves with a Passion]
*[https://www.reddit.com/r/dwarffortress/ Reddit]
*[https://arstechnica.com/civis/viewtopic.php?f=22&t=52391 Ars Technica]
*[https://www.gamerswithjobs.com/node/42890 GamersWithJobs Thread]
*[https://springrts.com/phpbb/viewtopic.php?f=10&t=10908 SpringRTS Thread]
*[https://forum.canardpc.com/showthread.php?t=3652 Canard PC Thread (Fr)]
*[https://dwarf.forumczech.com/forum.htm Ceske a slovenské forum (cz/sk)]
*[https://sg.hu/forum/tema/1290170541 Dwarf Fortress SG Fórum (Hu)]
*[https://tieba.baidu.com/f?kw{{=}}%E7%9F%AE%E4%BA%BA%E8%A6%81%E5%A1%9E Baidu Tieba Thread (zh-CN)]

===IRC Channels===
{{main|IRC}}
*[irc://irc.newnet.net/bay12games #bay12games] on newnet.net
*[irc://irc.synirc.net/df #df] on synirc.net
*[irc://irc.quakenet.org/DwarfFortress #DwarfFortress] on quakenet.org
*[irc://irc.tellaerad.net/DF #DF] on tellaerad.net
*[irc://irc.rizon.net/brofortress #brofortress] on rizon.net
*[irc://irc.freenode.net/DwarfFortress #DwarfFortress] on freenode.net ([http://webchat.freenode.net/?channels=DwarfFortress webchat])
*[irc://irc.esper.net/dwarffortress #DwarfFortress] on Esper.net

===Other wikis===
*[http://www.dwarffortress.fr/wiki Le Wiki Français ]
*[http://dwarffortress.if.land.to/ The Japanese (????) Wiki ]
*[http://www.dfwk.ru The Russian Wiki ]
*[[Dwarf_Fortress_Italia|Wiki Italiano]]
*[https://dfzh.huijiwiki.com The Chinese Wiki]

{{Getting Started}}
{{Category|Guides}}

Talk:Main Page

2022-11-01T11:26:09Z

Xjtu-blacksmith: /* Put Chinese language wiki on other Languages */

{{Archive|
# [[Talk:Main Page/archive1|Archive 1]]
# [[Talk:Main Page/archive2|Archive 2]]
# [[Talk:Main Page/archive3|Archive 3]]
}}

== Thread links on Main Page ==

Hi There - I'm relatively new to the DFwiki, and I noticed that some of the thread links on the Main Page don't work correctly. I logged in to try and edit the page, but when it wasn't an available option, I realized that it is probably restricted to administrators, given the 'please report vandalism' thing in the site announcements header.

The Team17 forums have closed, so the Team17 link is a dead one.
The SomethingAwful.com forums link is behind a login wall, so I'm not sure if you would want to remove this as well? I believe that they do occasionally rotate forums (such as Games) to be available to non-logged in users though, so it would perhaps be available intermittently.
:*<s>[http://forum.team17.com/showthread.php?t{{=}}30824 Team17 Forum Thread]</s>
:*<s>[http://forums.somethingawful.com/showthread.php?threadid{{=}}3466523 Something Awful]</s>
:Agreed and removed. Thanks! --[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:02, 15 August 2013 (UTC)

The Penny Arcade thread is also no longer available or at least incorrectly linked. – [[template:unsigned|unsigned]] comment by [[User:Ispil|Ispil]]
:Removed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:27, 26 August 2014 (UTC)

The dead links are back. [[Special:Contributions/88.195.209.206|88.195.209.206]] 15:04, 9 October 2014 (UTC)

== Fun Comic ==

What happened to the Fun Comic at the Losing page?--[[User:Doktoro Reichard|Doktoro Reichard]] ([[User talk:Doktoro Reichard|talk]]) 21:22, 23 January 2014 (UTC)

:Weird. We had a problem with an image server a while back, so this may be related. I'll get Briess to check on it. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:26, 23 January 2014 (UTC)

::Good to know (and to help). In case the file's lost, there's a crawl of it at the [https://web.archive.org/web/20130512135455/http://dwarffortresswiki.org/images/4/40/FunComic.png Internet Archive]. I also observed similar problems over at the [[Dwarf Fortress webcomics]] page.--[[User:Doktoro Reichard|Doktoro Reichard]] ([[User talk:Doktoro Reichard|talk]]) 21:29, 23 January 2014 (UTC)

:::[[:File:Comic df3.png]] doesn't have an edit history ([http://dwarffortresswiki.org/index.php?title=Comic_df3.png&action=history]), which usually means that it hasn't been uploaded, although that could be incorrect. Same for the rest of them, except [http://dwarffortresswiki.org/index.php?title=File:FunComic.png&action=history FunComic.png]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:34, 23 January 2014 (UTC)
::::I'm rebuilding all the images now. --[[User:Briess|Briess]] ([[User talk:Briess|talk]]) 21:54, 23 January 2014 (UTC)
::::The problem should now be fixed. It appears any time one of the webnodes loses a connection to the image server, it starts invalidating the images in question. I'll investigate ways to automatically rebuild the images when that happens. --[[User:Briess|Briess]] ([[User talk:Briess|talk]]) 22:02, 23 January 2014 (UTC)

== Amount of double redirects or ''how to fix them?'' ==

I come across several cases of double redirection which, as stated both here and in the rest of the wikiverse, are not a good thing to have.

Recently I found about the [[Special:DoubleRedirects]] page. There are roughly 350 double redirects on the wiki. From experience here, they could be easily fixed, because most redirect to the alternate name of the page, instead of the proper page itself.

As I've been adverted slightly due to a wrong fix I did I ask now if there are a set of guidelines, particularly because of the namespace usage here, that are or can be used to begin a duplicate removal process (which as stated, would be a mostly trivial thing to do, albeit costly in time).--[[User:Doktoro Reichard|Doktoro Reichard]] ([[User talk:Doktoro Reichard|talk]]) 17:15, 6 February 2014 (UTC)
*Originally, the policy was to deliberately use double redirects when going from the global namespace to version-specific namespaces and then to specific articles within those namespaces (e.g. "Green glass" -> "DF2012:Green glass" -> "DF2012:Glass") to avoid problems when new pages were created (e.g. if "Green glass" redirected straight to "DF2012:Glass" and somebody created "DF2012:Green glass" as full page, then "Green glass" wouldn't redirect to it properly). I don't know what the actual policies are anymore, though - perhaps one of the admins can chime in with more information. --[[User:Quietust|Quietust]] ([[User talk:Quietust|talk]]) 18:08, 6 February 2014 (UTC)

::That actually doesn't work. I moved the grazer information to the grazer article last week, and, until it was fixed today, [[main:grazer]] was still linking to [[DF2012:pasture]]. It appears the wiki software is caching the double redirect, so it behaves similarly to an un-updated single redirect. Sure the errant redirect can be fixed, but so can a single redirect. In some regards the double redirect is worse, because everything looks correct, yet it doesn't work. The underlying fact is that the wiki software was not intended to support double redirects, and it does so poorly at best. The current policy is available at [[DF:REDIR]], though it isn't set in stone.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:21, 6 February 2014 (UTC)

:For now, I only recommend changing double redirects to point directly to the destination page ''if they don't work''. They ''should'' all work, but some of them don't and there isn't a single, definitive reason we've found yet. Basically, feel free to change non-working double redirects, but you don't need to go through the list and change all 350 of them. (This wiki is actually set up to allow up to 10 consecutive redirects, unlike most [[wikipedia:WMF|WMF]] wikis, but since that feature isn't used by many wikis it tends not to be perfect.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:38, 6 February 2014 (UTC)

== Main Page New Version ==

Toady has announced the new version is due around the beginning of July 2014 (which is pretty soon). This is as big as DF news gets. There should be an announcement and link on the front page. – [[template:unsigned|unsigned]] comment by [[User:‎67.170.60.84|‎67.170.60.84]]
:What exactly are you suggesting? Aside from a wiki-specific announcement regarding migrating the wiki to the new namespace, I don't see a reason to announce the upcoming release here – anyone who reads the devlog or forums already knows, and very few of those who don't would check the main page of this wiki regularly instead. Also, what link are you referring to (devlog, Bay 12 report)? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:10, 21 June 2014 (UTC)

== Raw errors ==

There is something up with the raws for a few of the trees:
*[[DF2014:Alder/raw]]
*[[DF2014:Ash (tree)/raw]]
It appears to be spill over from the previous entry. Any idea how to fix this? [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 03:25, 15 July 2014 (UTC)

:This is actually intentional, since comments (i.e. non-raw text) in the raws usually refer to the raws following them (see most creature pages). It shouldn't be affecting the templates that look up information from the raws, but let me know if it is. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:59, 22 March 2015 (UTC)

== Object Testing Arena: Helmet Snake ==

For some reason I cant spawn them in Object testing arena. When I was looking through Syndromes I came across it and saw how many effects it has and thought I might have some fun with it. When I searched for it, it didn't show up? Can someone help me with this problem Thank you.

== Put Japanese language wiki on sidebar ==

Can't seem to figure out how to do it myself. [http://dwarffortress.if.land.to/ link to the wiki.] [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 12:04, 4 March 2015 (UTC)
:Do you mean an [https://www.mediawiki.org/wiki/Manual:Interwiki interwiki] link? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:47, 7 March 2015 (UTC)
::Can't really see what else I would mean. We have the french and russian one up there, why not the japanese? [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 04:26, 19 March 2015 (UTC)
:::It requires database access, apparently, which I don't have. Aside from installing or putting together an extension to handle this (which I plan to do eventually), [[User:Briess]] is who you should ask. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:57, 22 March 2015 (UTC)

== Sidebar ad format breaks Webkit ==

I have the site loaded up on my WiiU, which uses Webkit as the rendering engine, and I noticed a small issue with the positioning of the sidebar ad. I have div#p-googleadsense.portal at 160px by 655px, right on the edge of the screen. The div.body just inside is 140px by 611px, slightly smaller. However, the ins#aswitf_1_expand inside ''that'' is 160px by 600px - 20px wider than the div.body (but the same width as the .portal). This wouldn't be an issue if the ad was right on the edge of the screen, but the div.body has padding specified for 0.5em above, and 1.25em to the left (using the div#mw-panel CSS). My suggestion for fixing would be to force the ad's div.body to use no left margin (forcing this results in a fixed display until another page is loaded), but this requires a modification to the Wiki's core. In any case, just pointing this out so it could hopefully get fixed at some point. [[Special:Contributions/104.172.191.147|104.172.191.147]] 20:05, 18 April 2015 (UTC)
: Thanks, we'll look into it as part of the upgrade we're doing to the core installation! --[[User:Briess|Briess]] ([[User talk:Briess|talk]]) 03:44, 30 July 2015 (UTC)

== New sidebar link: Random page in current namespace ==

I have a feature request/suggestion for a new link on the main left sidebar: '''Random page in current namespace'''. Would (at this time) link to: http://dfweb4.dwarffortresswiki.org/index.php/Special:Random/DF2014 (unless there's a Special:Random/<token> that always means the latest NS, which would be better.)

I sometimes want to just browse through random pages, hoping to come across something interesting I'd not seen before/not thought to search for.

Random page is not much help because it is more likely to return pages for old versions than the current. I can go to Random by namespace and click DF2014, but then if I want to keep going through random pages I have to keep hitting back and clicking it again, or make my own bookmark to that link.

It's a small thing but it would be quite handy if there was a link dedicated to Random in the current NS.

[[User:TheBloke|TheBloke]] ([[User talk:TheBloke|talk]]) 13:25, 13 December 2015 (UTC)

== German forum link dead ==

Under ''Forums'' there is a link to http://www.dwarffortressforum.de/ – however, one gets redirected to http://www.indiegameforum.de/ which yields a “forum not available” message. I suggest to simply remove the link. (I have no edit rights on the main page.) --[[User:Keba|Keba]] ([[User talk:Keba|talk]]) 15:19, 5 January 2016 (UTC)

== DFFD New address ==

DFFD address should maybe be updated to http://dffd.bay12games.com/
--[[Special:Contributions/88.195.209.206|88.195.209.206]] 10:02, 10 January 2016 (UTC)
:Updated. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 21:39, 25 February 2016 (UTC)

== Can someone fix the spelling ==

It's "dependency" not "dependancy". [[User:Mocha2007|Mocha2007]] ([[User talk:Mocha2007|talk]]) 20:38, 19 September 2016 (UTC)
:Fixed --[[User:Rriegs|Rriegs]] ([[User talk:Rriegs|talk]]) 20:47, 19 September 2016 (UTC)

== B12G Discord ==

Hey, guys, can we have this Discord link added: https://discord.gg/sEeK7kX

It's a general B12G chat with a focus on Dwarf Fortress.
--[[User:Shub-Nullgurath|Shub-Nullgurath]] ([[User talk:Shub-Nullgurath|talk]]) 22:12, 1 April 2017 (UTC)

== How to create a new language page? ==

I've just seen one dwarf requesting a Japanese page.

If possible, I'll gladly translate this wiki into Korean. Korea is relatively a small country so the language is not that widely used, but surely there are some players, I guess.

I don't know where to ask about this :9

== Free SSL Certificate ==

If the operators want to re-enable https, they can get a free (as in beer) certificate from https://letsencrypt.org/ . Instructions are on that site and it's very easy.
:HTTPS is enabled now as of the June 2019 upgrades. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:53, 3 July 2019 (UTC)

== Re: Discord ==

I notice there's a Discord on this page. But shouldn't it be the Kitfox Games Discord, since that's the only official Discord for Dwarf Fortress?

[[User:AlastríonaCatskill|AlastríonaCatskill]] ([[User talk:AlastríonaCatskill|talk]]) 13:43, 12 February 2020 (UTC)
;I wasn't aware of it. If that is the case, then it should probably be added to the page. [[User:OluapPlayer|OluapPlayer]] ([[User talk:OluapPlayer|talk]]) 16:03, 12 February 2020 (UTC)

Yeah, the only reason there is one at all is because somebody added some random one. I changed it to the only DF discord I knew of at the time. The only way I've now been able to find it is to search for 'Kitfox Games discord'. It's not listed on the bay12 links page, a forum thread, the reddit, or the Steam pages. Anyway, I've DMed Victoria on the KitfoxGames discord to make sure they're OK with adding the invite to this page. [[User:Ziusudra|Ziusudra]] ([[User talk:Ziusudra|talk]]) 20:08, 12 February 2020 (UTC)

...Sorry, is it too late for this? I mean, while we're still discussing this, it looks like [https://dwarffortresswiki.org/index.php/Talk:Main_Page#B12G_Discord someone else got left behind as well]. Add, or not? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 22:21, 12 February 2020 (UTC)

I'm not sure what you were trying to link to. Do you mean this: http://www.bay12forums.com/smf/index.php?topic=163555.0 Note that the thread was locked because of drama. There's a lot of red flags: the drama, despite using the name Bay12Games it never uses the word 'unofficial', the rules channel posts are from a deleted user, the announcements channel hasn't updated in well over a year, many channels haven't been active in months. I'm not so much saying no, but I am asking: should it be linked?

There's also this: http://www.bay12forums.com/smf/index.php?topic=157332.0 But that invite is invalid. [[User:Ziusudra|Ziusudra]] ([[User talk:Ziusudra|talk]]) 02:35, 13 February 2020 (UTC)

Ah, it's a ''dead'' discord. I see now. There was just no response to the April '17 topic, I stumbled across it all and got curious. No, I don't think it should be linked. Thanks for the analysis, anyway! [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 11:44, 13 February 2020 (UTC)

== [[Multithreading]] ==

Would it be OK to create [[Multithreading]] page describing why (preferably with citations)
* even perfectly implemented boost would not be significant
* multithreading is not something that can be bolted on complex program
* DF is complicated case where taking advantage of multithreading is not obvious http://www.bay12forums.com/smf/index.php?topic=34311.msg7833713#msg7833713
* DF is filled with many gamebreaking bugs unfixed for many years, multithreading bugs are unusually awful to fix
* author of DF has minimal experiences with multithreading
* writing multithreaded code is hard
* writing correct multithreaded code is awfully hard
* fixing bugs in a multithreaded code is nightmare

and multithreading is not going to happen, ever

http://www.bay12forums.com/smf/index.php?topic=34311.msg7833713#msg7833713
http://www.bay12forums.com/smf/index.php?topic=107833.0
https://bholley.net/blog/2015/must-be-this-tall-to-write-multi-threaded-code.html + “At Mozilla, there is a sign on the wall behind one of our engineer’s desks. The sign has a dark horizontal line, below which is the text, ‘You must be this tall to write multi-threaded code.’ The line is roughly nine feet off the ground. We created Rust to allow us to lower that sign.” http://www.oreilly.com/programming/free/files/why-rust.pdf

[[User:Mko|Mko]] ([[User talk:Mko|talk]]) 03:07, 28 March 2020 (UTC)
:I disagree with some of your talking points
:* In DF each AI actor makes its own decisions, the computations can be done in parallel for an ncores speedup
:* This parallelism should be built into the lowest design levels of the program, it can be done in a DF-like program
:* With training and experience a good developer can write and debug multithreaded code.
:I agree that multithreading is unlikely to be done in DF; It can not easily be bolted on and I rather see the developer spend time on game-play.
:Is it worth to create a wiki page for what is essentially a one line explanation?
:--[[User:MathFox|MathFox]] ([[User talk:MathFox|talk]]) 18:40, 31 March 2020 (UTC)
::We would essentially be writing a page about a thing that doesn't matter to Dwarf Fortress. I can't agree to the existence of a page that's basically "This subject doesn't exist in the context of the game but here's the reasons why it should or shouldn't". This is better reserved for forum discussion, not a wiki. [[User:OluapPlayer|OluapPlayer]] ([[User talk:OluapPlayer|talk]]) 12:54, 1 April 2020 (UTC)

== Re: Discord II ==

Good morning.

I was confiding with some friends, who had alerted me to the "Unofficial Bay 12 Discord" posted on this Wiki. Simply put, allegations of the use of ableist slurs were thrown, as well as screenshot evidence of using hard racist slurs against people of colour.

I feel that the Unofficial Discord should hereby be removed from the social media part of the website for the following reasons:
* No official connection to Bay 12 or the publishers [and, by extension, every non-Bay12 forum should be removed - especially dead ones]
* This unofficial Discord is actively opposed to the standpoints that Toady One and Threetoe have posted on the bay12games site over the recent days.
* This unofficial Discord uses slurs and other problematic language that actively harms the image of the Dwarf Fortress community
* This unofficial Discord will likely make it so that people steer away from the game.

I do not feel comfortable with the Wiki platforming a known racist Discord server, as that is de facto support of the messages of that server.
[[User:AlastríonaCatskill|AlastríonaCatskill]] ([[User talk:AlastríonaCatskill|talk]]) 12:02, 21 June 2020 (UTC)

Update: Apparently, this same Discord has been banned from the r/dwarffortress subreddit for as long as one of the mods can remember, and the link to it was banned on the official Kitfox Discord as well. I can post the screenshots I have of actively problematic behaviour on this Discord but I will not do it unless necessary, as the contents are alarming like that which will not be named. [[User:AlastríonaCatskill|AlastríonaCatskill]] ([[User talk:AlastríonaCatskill|talk]]) 12:10, 21 June 2020 (UTC)

:I've removed the link. Safe to say, we don't need the wiki to be associated with this sort of people. [[User:OluapPlayer|OluapPlayer]] ([[User talk:OluapPlayer|talk]]) 21:58, 21 June 2020 (UTC)

::The "Unofficial Bay 12 Discord" was already not linked on the main page - the only place it was mentioned is this talk page. Are you talking about that one or the Unofficial Dwarf Fortress Discord that is linked on the main page? The latter does have it's #elfposting channel, but that channel is initially hidden, opt-in only, and clearly labelled as a lawless zone. For an analogy, there are many very awful subreddits, but we still link to reddit - (yeah that's a little different but not much). Otherwise the unofficial DF discord is well modded and such behavior is not allowed in other channels. So, are you certain which discord/channel the screenshots came from? [[User:Ziusudra|Ziusudra]] ([[User talk:Ziusudra|talk]]) 22:29, 21 June 2020 (UTC)

Since there's some confusion, AlastríonaCatskill, could you confirm and/or provide some evidence that following the link that was on the main page (removed in [https://dwarffortresswiki.org/index.php?title=Main_Page&diff=253449&oldid=251109]) takes you to the discord that you were referring to? The only reference I can find to a discord removed from the /r/dwarffortress sidebar is for a different discord, not the one that was linked on the main page (although it's possible that just the invite link was different). I just want to make sure that we're removing the right one here. If you have anything that you don't want to share publicly, you can PM me on the forums (same username) or [[Special:EmailUser/Lethosor|email me]] through the wiki, which I think is working. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:45, 22 June 2020 (UTC)

:@Lethosor, I have emailed you the relevant images via the link you had created. The Discord that was on the main page and removed today is indeed what was being referred to, especially with the confirmation of the #elfposting channel being from said Discord. In my opinion, @Ziusudra, the inclusion of a problematic part of that community, even as opt-in, is unacceptable in my book for a community to be platformed on this Wiki. [[User:AlastríonaCatskill|AlastríonaCatskill]] ([[User talk:AlastríonaCatskill|talk]]) 03:26, 22 June 2020 (UTC)

Hello, I am the owner of the Unofficial Dwarf Fortress discord. I just want to clear a few things up and open a channel of communication.
Several years ago, the original owner of the discord left, in no small part due to all the sexism and racism and such.
After a few days of an having an interim owner, it was given to another user, who onboarded several users as admins, including me.
The new owner tried a lot to curb terrible stuff on the server, however this often lead to drama.

The r/dwarffortress delisting happened after some of that drama spawned a new discord with a more "free speech" orientation,
things spilling over to the forums and other places. Some time after that, she left the server to me, due to the amount of
stress running that place caused her. When I took over I also tried to make it a better place, but with slower and subtler
methods that wouldn't spark drama. Completely disallowing some behaviour outside of #elfposting was part of that,
and later making that channel hidden by default was another. Now, the discord is much much better to be in
than it ever was before, though it still has major flaws. I don't like #elfposting at all myself, but I don't rule with an iron fist nor
do I know what much I can do without sparking massive drama again. Since April this year I have had some plans to make the discord
quite a bit better, however some of my mods have been against it in part due to feeling it would cause bigger problems
(though, as you probably know, some of them participate in #elfposting).
With recent events, both within and outside the DF community, we have decided to move ahead, every mod on board,
with some plans including phasing out the #elfposting channel in a way which will not create large issues for moderation.
It will be fully gone within one (1) week of now.

Also, I am a tad annoyed that you posted about this here but completely neglected contacting us. In the future, could you
please contact me or one of my mods when you have any concerns about the server? I really do care about these things and we need feedback.
—[[User:Lonjil|Lonjil]] ([[User talk:Lonjil|talk]]) 10:32, 22 June 2020 (UTC)

: Thank you for replying here Lonjil. Unfortunately, I cannot trust your take on this matter for several reasons.
: # One of the moderators has an anti-semitic stereotype profile picture
: # Even if the only place of no censorship is the elfposting channel, and even if it is opt-in, the complete chaos of racist slurs allowed there is completely unacceptable for minority players and an extremely toxic environment. There have been instances of straight hate speech on the channel / server as well, suggesting to kill people of colour and LGBTQIAA+ people.
: In short, the toxicity of your Discord's community makes it not just uncomfortable, but downright dangerous for minority people playing Dwarf Fortress. As Tarn and Zach have made liberal-to-leftist political views in the past, the chances of minorities to play the game is higher - and I wouldn't want to be a person of colour signing up for a shitposting channel to only be met with over 10,000 instances of the hard-n word being used. The Discord should remain off of the Wiki until things shape up and all instances of hate speech be purged from server history. Personally I would rather all non-official channels of communication be removed from the page, period, but that is a less pressing discussion than active hatred of minorities being platformed on the Wiki via your unofficial Discord. [[User:AlastríonaCatskill|AlastríonaCatskill]] ([[User talk:AlastríonaCatskill|talk]]) 12:30, 22 June 2020 (UTC)

:: Small edit / follow-up to my previous message. My friend tells me that elfposting is the most commonly used channel, which goes to show the level of hatred allowed into the community. It may be best to remove the channel in entirety, and make a new meme channel with no hate speech allowed. [[User:AlastríonaCatskill|AlastríonaCatskill]] ([[User talk:AlastríonaCatskill|talk]]) 12:33, 22 June 2020 (UTC)

::: The admin you are referring to is a jew, who lives in Israel. I prefer to not police people of other ethnicities when it comes to negative stereotypes and such of themselves, they know what they are comfortable with far better than I ever could.

::: Elfposting is not, by any reasonable measure, the most used channel. It has fewer users than any other channel. It has a fair number of messages, but only because there is no rule against spamming in there. So, nearly all of it is spam, which was the point of the channel to begin with.

::: "It may be best to remove the channel in entirety" this is exactly what is happening, as I already said. We're giving the channel regulars a few days to hear the news, but then the channel will be gone. We already have a more pleasant meme channel from an experiment we did in April, which we are bringing back. —[[User:Lonjil|Lonjil]] ([[User talk:Lonjil|talk]]) 13:57, 22 June 2020 (UTC)

Hi all - thanks for keeping this discussion civil. I've been investigating the policies of other DF communities, and I've come to the conclusion that it would be best for the wiki to only link to the official DF Discord (Kitfox). I'll also make a pass through the other sites linked on the main page. I'm sorry to those of you working hard to maintain Discords and other unofficial communities out there - I know it's difficult, and I don't want to judge your communities without being a part of them. However, there will always be debates like these about whether a community deserves to be linked from a more "official" place, like the wiki, and no matter where we draw the line(s), people will be upset. The policy of only linking to the Kitfox Discord seems to have worked for other communities, which is why I'm applying it here. I would be happy to have a broader discussion at [[DF:Centralized Discussion]] if anyone wants to. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:48, 23 June 2020 (UTC)

== Put Chinese language wiki on other Languages ==
Found it on Internet([http://cdf.wikidot.com/start]) – [[template:unsigned|unsigned]] comment by [[User:45.58.187.66|45.58.187.66]]

:I added a link to it. I'm not sure what the process is for adding interwiki link support (support for links to pages in the sidebar, like how [[DF2014:Cat]] links to http://dfwk.ru/Cat) but I can look into that too. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:40, 19 August 2020 (UTC)
::Hello! I'm the admin of [https://dfzh.huijiwiki.com/ Chinese Dwarf Fortress wiki], and I've previous put its link on the main page. We've now enabled interwiki link from our site to English site, and we wish to get one back from English site to CN site as well. Hope that is possible, and thanks so much! The URL for our site should be: <code>https://dfzh.huijiwiki.com/wiki/$1</code> [[User:Xjtu-blacksmith|xjtu-blacksmith 黑山雁]] ([[User talk:Xjtu-blacksmith|talk]]) 11:26, 1 November 2022 (UTC)

== Villains Wiki ==

To started putting some creatures on the Villains Wiki, because I want to spread the word of Dwarf Fortress around, and these creatures fit the theme of the wiki anyway. Here's an example page, and the template of all pages: 
[https://villains.fandom.com/wiki/Goblins_(Dwarf_Fortress) Villains - Goblins] 
[https://villains.fandom.com/wiki/Template:Dwarf_Fortress_Villains Villains - Template of DF Villains]

If anyone could add more info to those pages, or think more creatures should be on that wiki, please let me know. Or you could add it yourself. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 13:37, 9 January 2021 (UTC)

== Replace Chinese Wiki with the new one on Fandom ==

The previous Chinese wiki on wikidot seems to be inactive for a long time, with its main page refers to the download link of v0.44.10, and most pages are never updated even earlier than that version. Recently we are working on a new site on Fandom ([https://dwarf-fortress.fandom.com/zh]), trying to keep everything up to date. Wish to replace the links on dwarffortresswiki's main page and the sidebar link (inter-language link) with the one at Fandom, so that more people may get to the right place and join us. [[User:Xjtu-blacksmith|xjtu-blacksmith 黑山雁]] ([[User talk:Xjtu-blacksmith|talk]]) 04:16, 30 December 2021 (UTC)

:I've added the link of Fandom site onto the main page, without removing the previous one. [[User:Xjtu-blacksmith|xjtu-blacksmith 黑山雁]] ([[User talk:Xjtu-blacksmith|talk]]) 11:09, 12 May 2022 (UTC)
:We've migrated Chinese Wiki to huijiwiki.com, which is now shown on Main Page. [[User:Xjtu-blacksmith|xjtu-blacksmith 黑山雁]] ([[User talk:Xjtu-blacksmith|talk]]) 07:41, 29 May 2022 (UTC)

== Kitfox Discord ==

<blockquote>
''2022-04-15 BlueManedHawk . . (8,594 bytes) (-135)‎ . . (The Kitfox Games discord server has an unethical code of law. I don't think the wiki should be supporting it.)''

''2022-04-15 Ziusudra . . (8,729 bytes) (+135)‎ . . (Undo revision 263652 by BlueManedHawk[:] please discuss changes such as this on the talk page first) (Tag: Undo)''
</blockquote>

Alright, I can do that.

The Kitfox Games discord server has a code of law that contains the following immoralities:

:- Is very vague and nebulous, allowing the moderators to exploit the vagueness to be able to do very different things in similar circumstances in alignment with their biases. (Not that they do that, but the fact that it's possible is concerning.) 
:- Contains a "These rules are subject to common sense." clause, essentially meaning that the moderators are able to do whatever they want and hide it behind the barrier of "common sense". This goes completely against the point of the concept of rules in the first place as a promise from those in power in regards to what they will and will not do. 
:- Allows for infinite punishment.

That last one could do with a bit of explaining. Let us begin with the premise that the punishment for a crime should be proportional to the severity of the crime. I think we can all agree on this. Therefore, an infinite punishment should only ever be given for an infinite crime. However, humans are not infallible. People make mistakes. And this means that if a court of law is able to administer an infinite punishment, they run the risk of accidentally giving somebody an infinite punishment that they do not deserve. This, I think we can all agree, is unnacceptable. Therefore, infinite punishment cannot every be administered ethically.

I hope that this explains why I want the link to the Kitfox games discord removed.

Regards,

—[[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 22:29, 15 April 2022 (UTC)
:* Their rules are not vague or nebulous, they even give examples of what the rules cover. Of all the discords I am on, their rules are some of the most detailed.
:* The "''depending on the action and our judgement''" is quite similar to the "''depending on how disruptive you were and your prior history''" found in the DF forum rules, and is pretty standard social media boilerplate and is itself common sense.
:* Their rules state "''Breaking these rules will result in a warning or ban''", which is not at all "''infinite punishment''", and is again quite similar to the "''If you violate the guidelines, you will be warned, muted for a period of days, or banned completely''" on the forums. It's not like they can keep anyone from playing the game or interacting with the other communities.
: Your referring to their rules as "code of law" is hyperbolic. Their rules are quite similar to the rules of the forum. So, I disagree and think the link should stay. [[User:Ziusudra|Ziusudra]] ([[User talk:Ziusudra|talk]]) 23:13, 15 April 2022 (UTC)
::* The rules are pretty vague. Examples aren't enough. A strict, clear, unambiguous definition is necessary to prevent abuse.
::* While it is true that their clause is ''normal'', that doesn't mean it's ''right''.
::* The explanation of bans doesn't explain how long the bans will last. Since there's nothing explicitly stating that infinite punishment won't be given, and since "ban" by itself generally refers to a permanent ban, I think that it's allowing infinite punishment.
::* I'm not sure how the term "code of law" is hyperbolic. I use the term synonymously with "set of rules".
::* I can't seem to find a code of law for the forums. However, if what you said is true, then clearly we should also remove the link to the forums.
::
:: Regards,
::
:: —[[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 02:59, 16 April 2022 (UTC)
::: http://www.bay12forums.com/smf/index.php?topic=27009 It's linked in the header at the top of every forum page, though if the header is collapsed you won't see it.
::: Unambiguous rules are technically impossible since human behavior is limitless. That's why we hav judges for actual laws - even society's strictest laws need a human adjudicator. Then, even with "permanent bans", both Kitfox and Bay12 hav public email addresses and twitter accounts which can be used to petition to hav a ban removed.
::: Finally, suggesting the removal of the links to the official forums for the game this wiki is dedicated to is unreasonable, to the point of making me wonder if you're trolling. [[User:Ziusudra|Ziusudra]] ([[User talk:Ziusudra|talk]]) 04:59, 16 April 2022 (UTC)

::::I agree with Ziusudra. More broadly, I think we should keep links to "official" DF channels, and Kitfox is a DF publisher. If a potential for "infinite punishment" warrants removing links to the offending site, then by your logic, we should remove all links to the wiki from the wiki because users here have been banned permanently. That has been done based on the best judgement of the people who volunteer their time to run the wiki and has been open to appeals, and I expect other channels are similar. I'm not interested in entertaining this argument here. If you have specific issues with a specific external site, I suggest that you get in touch with the moderators there instead. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:34, 16 April 2022 (UTC)

:::::Hello.

:::::As I mentioned below, the DFWiki is in a position of power, and by removing the link to them, we can potentially force their hand into making their code of law more moral. On the other hand, keeping the link there could potentially be seen as supporting their immoral behavior, tarnishing the reputation of the site. This is why I brought up my issues with an external site onto this one: because these issues also affect it.

:::::It is true that by my logic, the DFwiki is operating immorally. However, I would like to mention that ''you are in a position of power on the wiki'', Lethosor. I would think that you have the ability to change the Wiki's code of law to be more moral. You have the choice to make the wiki a better place, and I advise that you take it.

:::::Regards,

:::::—[[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 06:22, 16 April 2022 (UTC)

::::Hello.

::::* I don't know which header you're referring to—wherever it is, it seems to not be there for me. Regardless, I thank you for clarifying which guidelines you were referring to.
::::* Unambiguous rules are largely impossible because nobody has yet created an unambiguous language. However, that doesn't mean that we shouldn't still seek to get as close to unambiguous as possible when constructing a code of law.
::::* Claiming that the bans are transient because it's possible to appeal them is optimistic, and while there is a place for optimism, this is not it. Any potential that a legal system has for corruption is one that we cannot assume will not be used, and often, corruption begets corruption, continuing the cycle until a revolution happens.
::::* Being a central repository of knowledge on DF, the DFwiki is in a position of power. If we do remove the link to the Kitfox discord under the condition that they make their code of law more moral, then we can theoretically force their hand, maybe. There is, of course, a risk to this, and this should be deliberated before a decision is made.
::::* I am not a troll. Why does everybody keep thinking that?

::::Regards,

::::—[[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 06:22, 16 April 2022 (UTC)

== Advertisements problem ==

One of the full-page advertisements(a pop-up that obscures the whole page) had what looked like a "close" button, but it just tried to redirect me to another page.
Full page advertisments aren't untoward but like, web elements that say 'close' are expected to do what they say, otherwise it's intercepting clicks. – [[template:unsigned|unsigned]] comment by [[User:Eerr|Eerr]]

:Do you have a screenshot of the offending ad, or can you take one if it happens again? My understanding is that that is something we (admins) don't have control over, but we can report misleading ads to Google. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:09, 2 June 2022 (UTC)

== Kitfox Discord (again) ==

Hi. I'm again requesting the removal of the link to the Kitfox discord server for only two reasons this time: the code of law gives infinite power to the moderators, and the criminal justice system uses punishment to deal with criminals. These are obviously both immoral, and until the server fixes these issues, the DF wiki ought to remove the link so as not to seem to be promoting them. [[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 21:45, 15 September 2022 (UTC)
:And again, I don't support removing the official publisher's discord just because you think that there is some thing wrong with their completely normal and reasonable moderation practices, none of which involves "infinite power", "punishment", "criminals", or other such hyperbole. Banning is not "punishment", it is protection of the community from those that act to harm it, nor is it "infinite power" since all it does is keep those rule breakers off one discord server and nothing else. All of which also happens on both the Bay12 Forums and this very wiki, both of which, by your logic, you should immediately stop using lest you appear to be promoting them. [[User:Ziusudra|Ziusudra]] ([[User talk:Ziusudra|talk]]) 03:45, 16 September 2022 (UTC)
::Normalizing of horribly unethical practices is not okay. I do not think it is hyperbole to use the terms "infinite power, "punishment", and "criminals". The server is a jurisdiction like any other, and it should be held to the same standards of morality as any other—this includes not using punishment as a means to deal with those who break the law. It is completely possible to protect the community without using bans—bans simply get rid of problems instead of fixing them, and are ineffective against the diligent. Infinite power is not an okay thing to give to those who govern a jurisdiction—dictatorial power structures have been shown to fail many times over throughout history.
::
::If we simply must keep any official venues for DF on the main page, regardless of morality (this includes the forums, which i agree should also be removed), then the Wiki ought to put a disclaimer of some sort clarifying that they are being listed not in support of the governance policies of the communities, but simply because they are official.
::
::[[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 17:24, 17 September 2022 (UTC)
:::Good god, how many of these discussions are you gonna keep making? Is there anything that ''doesn't'' offend you? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 13:14, 22 September 2022 (UTC)
::::There's no need to be rude. But to answer your question, i'm going to have as many discussions as are necessary until a concensus is reached. [[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 21:43, 22 September 2022 (UTC)
:::::You can't keep just keep making constant requests of "guys can we please remove that and that and that and this and this because of like business and anti-competitive stuff and yeah and like" but then turn around and go "why does everyone think I'm a troll?" Can you seriously not connect those two things together? I've been part of this community for a long time, and you are the one and only person who gets all offended by things that no one else would even care to think about. This wiki is not the place for that. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 10:48, 23 September 2022 (UTC)
::::::I really don't understand why people think that i'm a troll. If you or someone else were to explain it to me in a manner that's more polite than your previous messages have been, i'd be happy to listen. [[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 20:18, 23 September 2022 (UTC)
:::::::Hmmmmmmm, no. I'm gonna skip the "polite" thing and just speak the truth. No regrets. The fact that you can't see why people think you're a troll makes the situation even worse. You're someone who got all bent out of shape over a Minecraft diamond reference, something that no one else would ever care about. You keep saying you don't see how people think you're a troll when it was explained to you many times. All this goofy legal stuff you keep bringing up is best left elsewhere. Not here. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 13:59, 24 September 2022 (UTC)

Bridge

2022-10-27T11:13:48Z

Xjtu-blacksmith: /* Cave-ins */

{{Quality|Masterwork|12:07, 16 August 2019 (UTC)}}
{{av}}

[[File:Lagos48.jpg|thumb|190px|right|Medieval-style drawbridge.]] '''Bridges''' are [[building]]s which provide a temporarily walkable floor that can either be removed ("retracting" bridges) or turned into a wall ("raising" bridges) via linked [[mechanism]]s. Bridges are useful for crossing empty space and dangerous terrain, serve a vital role in [[Defense design|fortress defense]], and have a host of ancillary uses. For example, using bridges to control [[flow|fluids]] can save a ton of mechanisms and time, especially when the [[magma|fluid in question]] requires a wide opening.

==Building bridges==
When first built, any bridge is just a static walkway, often (but not necessarily) over open space. They can be used as is, and use less materials than a [[construction|constructed]] floor of the same size serving the same purpose. if you want them to raise or lower, they must be linked to a trigger (see [[Bridge#Raising and retracting bridges|below]]).

Bridges can be built ({{k|b}} -> {{k|g}}) of [[metal]], [[stone]] or [[wood]]. They are first designed by an [[architect]], then require a specialist worker in the material used* (e.g. a [[mason]] for a stone bridge, etc.). The size of the bridge can be altered with {{k|u}}{{k|m}}{{k|k}}{{k|h}} while placing it, up to a maximum size of 10 squares in each direction (10x10)**.

: (* See note re "core material" under [[:Bridge#Materials|Materials]], below) 
: (** You can place additional bridges side by side to make them infinitely wider. You can also place a second bridge on the ''other'' side of a wide gap to span as much as 20 tiles. Any more requires some solid anchor to provide another 10 tile maximum (in both directions).)

Raising bridges must be anchored to a solid surface on the "raising" edge. Before placing a raising bridge, ensure that the bridge raises from the direction you want it to using {{k|w}}{{k|a}}{{k|d}}{{k|x}}. The direction points to the side of the bridge which will become a wall when the bridge is raised.

Since a retracting bridge completely disappears, direction doesn't matter. Retracting bridges are the default, but if you selected "raising" by mistake, the command key for retracting is {{k|s}}.

=====Placement requirements=====
The error message 'Needs walkable perimeter' suggests that access is required all the way around the perimeter of the bridge, however, only one accessible adjacent tile is required. Placement of the bridge also requires that all of the tiles it occupies not have more than 1/7 water on them at the time of construction.

===Materials===
Bridges require stone, logs, and/or [[block]]s - they can be mixed - with blocks being placed significantly faster during the actual construction. The formula for the number of building materials needed is: number of tiles in the bridge divided by four, rounded down, plus one, or {size/4, rounded down}+1.

So, for example, a 3-tile bridge takes {3 tiles/4=3/4 -> 0} +1 = 1 building material. A 4-tile bridge takes {4/4=1} +1 = 2. A 5x10 bridge would require {50/4=12 1/2 -> 12} +1 = 13, and so on.

The "core" material of the bridge is the ''oldest'' individual building material used (i.e. the first item that was created in the fortress or that entered the map).{{cite forum|134816}} The core material determines the color, style, and description of the bridge, as well as the labor required for construction.

Care should be taken when choosing materials for bridges that will be exposed to [[fire]] or [[magma]]: Bridges built with non-[[magma-safe]] materials will heat up and eventually melt if the center tile (with bias towards the northwest if the center doesn't fall on a single tile) gets covered in magma or exposed to fire, whether the bridge is raised, lowered, or even retracted. The ability of a bridge to withstand heat is limited by the ''least'' fire-resistant item involved - a single non-magmaproof building block or mechanism will cause the whole bridge to deconstruct when exposed to sufficient heat. [[Dragonfire]] almost immediately melts nearly all bridges ([[slade]] being the prime exception).

==Raising and retracting bridges==
When designating a bridge to be built, you can choose to make it "retracting" (the default) or "raising". A retracting bridge disappears when it is "up" and become invisible, and a raising bridge is a "drawbridge", forming a visible wall when it's up. The "wall" is always just 1 z-level high x 1 tile thick (and as wide as the bridge is wide), no matter how long the "drawbridge" is when it's down. For raising bridges, you select which direction you want it to raise when you designate it to be built. This cannot be changed later, which would require deconstructing and rebuilding a new bridge.

All bridges can be either raised or retracted by linking it to a trigger with [[mechanism]]s - this requires a dwarf with the [[mechanics]] labor activated. Once the trigger (either a lever or pressure plate) is in place, use {{k|q}}uery on that trigger and select "link to {{k|b}}ridge". You will then get a pop-up map where you can cycle through all bridges that you have currently built in your fortress. Select one, and then select the 2 specific mechanisms you want to use to link the bridge. Quality of mechanism has no effect on the raising/lowering of the bridge, nor the time to install the mechanisms.

Any bridge, retracting or raising, of any size, will respond to the trigger signal 100 [[Time|tick]]s after the signal is sent. You can link more than one bridge to the same trigger and they will all respond simultaneously.

If a bridge is set to retract when trigger is activated, the bridge essentially disappears, ''tossing'' anything (friend, foe, or object) on the bridge onto whatever is underneath. Clearly this can be used to drop your enemies to rocky/watery/fiery deaths (or anything more imaginative you can think up!). Note that the creatures and objects are "tossed" with a semi-random initial velocity; this can reduce the lethality of pit traps (creatures bouncing off the walls lose the precious momentum that would otherwise result in an unsurvivable splat at the bottom), interfere with the reproducibility of dwarven !!SCIENCE!!, and be [[exploit]]ed as the key mechanic in [[#Coinstar training|coinstar training]].

If a bridge is set to raise when a lever is pulled, the bridge will become a [[wall]] along the edge selected with the {{k|w}}{{k|a}}{{k|d}}{{k|x}} keys when placing the bridge. When activated, the bridge "raises" very quickly, flinging anything on the bridge into the air, with unpleasant if not always deadly side effects. The resulting wall is always one z-level tall, watertight, and invulnerable to [[building destroyer]]s. Raising "drawbridges" can be used to block fortress entrances and corridors. When lowered, bridges will destroy most anything on the underlying tiles. By "destroying", we mean dwarves, foes, and items will entirely disappear from the game, a rare event which led to the creation of the term [[dwarven atom smasher]].

Any water displaced by a raising bridge is destroyed regardless of how much open space is on each side or above. Water resting atop a retracting bridge falls straight down after the bridge retracts.

==== And levers ====
Note that, depending on the design, retracting and raising bridges can provide the opposite reaction from an "open" signal. When the "open" signal is sent, both bridges "disappear" from view - the retracting bridge disappears completely, and the raising bridge becomes a 1-tile high, 1-tile thick wall. But this means that the raising bridge closes the passage on the same level with that wall that it creates on the "open" signal. This can be used to create either an "open" passage or "closed" passage on the "open" signal, depending on the design.

Of course, this is true for bridges and [[pressure plate]]s as well.

==Notes==

Bridges will not operate if any one creature of [[List of creatures by adult size#bridge|size 1,200,000]] or larger is on them. This weight limit is not cumulative - a bridge will still retract if a hundred goblins are standing on it, but a single [[rutherer]] accompanying those goblins will prevent the bridge from operating. Attempting to lower a drawbridge onto such a creature (in order to [[Dwarven atom smasher|atom-smash]] it) will cause the bridge itself to deconstruct. Attempting to "unretract" a bridge while such a creature is in any of the bridge tiles will similarly cause the bridge to deconstruct. The size limit does not apply to creatures inside cages.

It is impossible to channel out stone that is directly under a bridge, raised or not. Likewise digging a ramp under a bridge will not remove the floor tile. To remove these floor tiles, the bridge must be deconstructed. Note that [[obsidian casting]] can ''create'' new floor tiles under a bridge, which then behave in the manner above.

Big bridges can take weeks or even months to complete. You can shorten construction time by moving the materials to the site before starting construction, and by using blocks instead of stones. The material-gathering time is somewhat shorter for blocks due to their lesser weight, and the actual construction is three times faster for blocks.

'''Warning:''' while bridges do not provide structural [[support]], the game will still allow you to place [[construction]]s adjacent to them. Any construction that is completed when attached only to a bridge will cause an immediate [[cave-in]], often tossing the unlucky mason off the edge, to <s>a horrible death</s> any bystanders' great entertainment. However, a construction that connects to an existing supported construction when completed will not cause a cave-in, even if it is also adjacent to a bridge. To build constructions next to a bridge safely, ensure that ''all'' unbuilt constructions adjacent to a bridge are also adjacent to a construction that has already been completed. When building large constructions, it may be useful to [[suspend]] all tiles adjacent to a bridge until the neighboring constructions have been completed.
 '''Example:'''
{| class="wikitable"
|-
|Will cause a cave-in
|Will '''not''' cause a cave-in
|-
|
<diagram>
╔═╗[#3:0]▓[#]
║+║[#0:0][@6:0]O[#@]
╚═╝[#3:0]▓[#]
[#2:1].,'[#3:0]▓[#]
</diagram>
|
<diagram>
╔═╗[#3:0]▓[#]
║+║[#0:0][@6:0]O[#@]
╚═╝║
[#2:1]`,.[#]O
</diagram>
|}

Deconstructing bridges can be hazardous, as dwarves are not as compunctuous as with constructions and diggings to make sure no one is standing on them before destroying them.

A raised bridge cannot be linked to a lever from the inside - the mechanic must be able to access the center tile of the bridge when lowered.

If you aren't sure whether or not a 1 tile thick bridge is raised or lowered, try to build a piece of furniture, like a statue, on it. If it says blocked, the bridge is raised, if it says building present, it is lowered. You can also link another (longer) drawbridge to the same lever, to use as a visual indicator of the other bridge's status. Since this takes additional time and mechanisms, this is best reserved for when it's especially important that you know at a glance whether that bridge is blocking things.

==Uses==
Perhaps the most straightforward use of a bridge is spanning empty space or dangerous terrain. Bridges only need roughly 25% of the material that building [[floor]]s would require, and can be completed relatively quickly as well. Bridges are limited to a span of 20 tiles across open space; greater distances will require columns or other means of support. ("Floating" retracting bridges can be built into spans longer than 20 tiles, but they will deconstruct when support is checked.{{bug|9946}})

===Remote controlled gateways===
Lever-controlled bridges are one of the safer ways to control access. They are immune to building destroyers, though care must be taken to avoid operating them in the presence of exceptionally large creatures. [[Magma safe]] material should be used in the construction if there is any chance magma might flow over the bridge.

Retracting bridges built covering the top of a ramp or stairway can never be destroyed from beneath.

===Floodgates===
Raising bridges make a good replacement for most [[floodgate]] uses (e.g. flow and access control). They have the advantage of not being as easily jammed: they fling or [[Dwarven_atom_smasher|atom smash]] all items and all but the largest enemies on their tile/s when they open or close, whereas a floodgate or door will jam open with a discarded sock in it. Further, bridges cannot be destroyed by [[building destroyer]]s, while [[floodgate]]s can be. A single bridge can also be made up to ten tiles wide, potentially replacing ten floodgates and saving many mechanisims and much work. One minor downside of bridges compared to floodgates is that bridges with a width of 1 look the same when raised as when lowered, so it is easy to confuse whether they are closed or not. If you are unsure of a bridge's status, check the control lever if there is one (in most tilesets, lever to the right means closed), or try to build furniture on top of the bridge and check the resulting warning message ("blocked" means the bridge is raised, "building present" means it's lowered).

===Waste disposal===
{{Main|Dwarven atom smasher}}
Lowering raised bridges can be used as [[waste disposal]] for unwanted stones, [[refuse]], [[goblin]]s (dead or alive), legendary [[cheese]] makers and [[nobles]], to name a few. Even fluids get destroyed. Note, however, that lowering a drawbridge onto a sufficiently large creature (such as a [[forgotten beast]]) simply causes the bridge to deconstruct.

===[[Trap_design#Bridge_and_drop_traps|Traps]]===
Using two bridges at opposite ends of a corridor creates a very large and simple trap by walling in enemies. Or... Smashing them to tiny bits if placed to raise facing each other, with no space in between.
For added effect, place [[pressure plate]]s on both ends to raise the bridge when stepped on, to fling the units. If there is a [[floor]] directly above, they will be stunned. If there is a floor beneath the bridge, and if nobody is on the pressure plate, they will likely be smashed when the bridges come back down. If there is nothing above, they will land rather far away. Bonus points for making them land in a particularly [[Spike#Menacing_spike|nasty spot]].
If there is no floor beneath the bridge, they will fall, sometimes into something [[water|very,]] [[magma|very]] [[megabeast|bad.]]

===Minecart routing===
Lowered/extended bridges "cover" [[Minecart]] track corners constructed or carved underneath, allowing carts to travel in a straight line instead. This can let you change minecart routes via pulling levers.

===[[Cave-in]]s===
Since bridges don't support adjoining rock, it is possible to set up a cave-in so that dust can't come up, dwarves can't fall down, and flying creatures can't come up from beneath the cave-in before you set it off. Bridges are also instrumental in [[magma piston]] applications.

===Improvised ceilings===
Building an outdoor structure, such as an [[Archery tower]], requires considerable expense and time. The reduced material requirements make bridges a viable alternative to roofing it up tile by tile. While it'll still be immune to [[Building destroyer]]s, a proper constructed ceiling is superior if you expect it to be exposed to [[Dragon|extreme temperatures]].

===Improvised walls===
[[Wall]]s cannot be built along map edges above ground, but raising bridges can. Because these bridges can be raised to act as walls, they can be used to control where wildlife, enemies, and [[caravan]]s spawn on the map edges.

A similar technique can be used to prevent fliers from spawning above ground, but it requires bridges to be built at ''every'' z-level. This requires considerable effort, as each bridge needs to be accessible to the dwarves building it, as well as needing support for each bridge. It can also be somewhat [[fun|risky]] if a dangerous creature suddenly spawns near a dwarf working on the bridge (especially in [[evil]] biomes). Note that this technique, when completed, will also prevent fliers from leaving the map.

===Ocean drains===
Designate ramps on the 2nd level below an ocean. Build a retracting bridge directly above the ramps (immediately under the ocean) leaving the ramps in place, and link it to a trigger. In order to build the bridge (and link it) you will need access to the level of the bridge. Now seal that access off (the constructed wall in the below diagram) so the chamber above the bridge is water tight. Now with the bridge in place, designate ramps up to the ocean adjacent to the bridge. Diggers with access to the level ''below'' the bridge can dig those ramps up from the level of the bridge, allowing the ocean to fill the chamber; even with the ramp squares underwater they can still dig them out. And not a drop of water will touch them... provided they clear out before you pull the lever.

Shown below is a 2x1 bridge (any size bridge can be used) before and after designating the ramps adjacent to the bridge. The stairs and passage on Z2 satisfy the 'Needs walkable perimeter' requirement and provide access to the top of the bridge for linking to a trigger. The passage is then blocked with a wall to make it water tight.

Before breaking through After
side X side Y side X side Y
Z3 ≥≥≥≥≥≥≥ ≥≥≥≥≥≥≥≥≥≥ ≥≥>≥>≥≥ ≥≥≥≥≥≥≥≥≥≥
Z2 ###B### ##Z_X_BB## ##^B^## ##Z_X_BB##
Z1 ###^### Z ^^## ###^### Z ^^##
Z0 ####### ########## ####### ##########

≥ = Water with floor > = Water without floor Z = Stairs
^ = Ramp # = Solid Rock X = Constructed Wall _ = Floor (not constructed)

===Caravan exits===
A bridge to nowhere, built well above ground level at the edge of the map, can sometimes serve as a handy exit for [[caravan]]s and [[diplomat]]s when your fortress is under [[siege]].

===Stops on the elevator===
Designate a dumpsite or set up a floodgate at the top of a shaft; use multiple remote-controlled bridges to decide on which level the stuff, water, magma etc. gets off. (bonus: use water falling at one end of the bridge to flush stuff off that was dropped onto the other end without the manual labor)

===Single lever airlock===
Raising bridges and retracting bridges controlled by a single lever will be in opposite states of being open or closed. When one is closed (raised) the other is open (retracted) and vice versa. This fact can be used to construct airlocks that are not vulnerable to [[building destroyer|building destroyers]] or mistimed lever pulls e.g.
Side View:
Z1 XXXXXXR____ D = Raising drawbridge / = Ramp _ = Floor
Z0 D_____/XXXX R = Retracting bridge X = Solid Rock or Constructed Wall

With a suitably long distance between the two bridges, the controlling lever can be placed within the airlock, and by setting the profile of the lever specific dwarves can be moved between isolated areas.

===Decorations===
Bridges benefit from two [[quality]] modifiers--one for the [[architect]]'s design, and one for the builder's creation, and their multipliers are also applied to any attached mechanisms. High-quality bridges can inspire happy [[thought]]s in your dwarves and help meet room value needs. Bridges may also be used to form [[mosaic]]s or even [[Style_project#Mosaics|animations]].

===Coinstar training===
The mechanical "tossing" action of retracting bridges can be used for training [[armor user]] and associated traits by repeatedly flinging small items at the trainee. See [[Danger_room#Coinstar_Room|Danger room]] for more information.
Alternatively, this design can be used as a trap: invaders atop a retracting bridge inside locked room will get thrown around and optionally pummelled with "ammunition" like stones or weapons placed in the room.

==Bugs==
* Metal bridges can be constructed by dwarves with any of the "metalsmith" skills enabled, however the builder's blacksmith skill is used to determine quality{{bug|4899}}
* Trees grow through bridges, may make the bridges unusable{{bug|7872}}
* Retracting bridges can be built without support, but will deconstruct when support is checked{{bug|9946}}

{{Translation
| dwarven = sazir
| elvish = valóna
| goblin = romnu
| human = ori
}}

{{buildings}}
{{Category|Buildings}}

Bridge

2022-10-25T11:36:11Z

Xjtu-blacksmith: /* Waste disposal */ add main article

{{Quality|Masterwork|12:07, 16 August 2019 (UTC)}}
{{av}}

[[File:Lagos48.jpg|thumb|190px|right|Medieval-style drawbridge.]] '''Bridges''' are [[building]]s which provide a temporarily walkable floor that can either be removed ("retracting" bridges) or turned into a wall ("raising" bridges) via linked [[mechanism]]s. Bridges are useful for crossing empty space and dangerous terrain, serve a vital role in [[Defense design|fortress defense]], and have a host of ancillary uses. For example, using bridges to control [[flow|fluids]] can save a ton of mechanisms and time, especially when the [[magma|fluid in question]] requires a wide opening.

==Building bridges==
When first built, any bridge is just a static walkway, often (but not necessarily) over open space. They can be used as is, and use less materials than a [[construction|constructed]] floor of the same size serving the same purpose. if you want them to raise or lower, they must be linked to a trigger (see [[Bridge#Raising and retracting bridges|below]]).

Bridges can be built ({{k|b}} -> {{k|g}}) of [[metal]], [[stone]] or [[wood]]. They are first designed by an [[architect]], then require a specialist worker in the material used* (e.g. a [[mason]] for a stone bridge, etc.). The size of the bridge can be altered with {{k|u}}{{k|m}}{{k|k}}{{k|h}} while placing it, up to a maximum size of 10 squares in each direction (10x10)**.

: (* See note re "core material" under [[:Bridge#Materials|Materials]], below) 
: (** You can place additional bridges side by side to make them infinitely wider. You can also place a second bridge on the ''other'' side of a wide gap to span as much as 20 tiles. Any more requires some solid anchor to provide another 10 tile maximum (in both directions).)

Raising bridges must be anchored to a solid surface on the "raising" edge. Before placing a raising bridge, ensure that the bridge raises from the direction you want it to using {{k|w}}{{k|a}}{{k|d}}{{k|x}}. The direction points to the side of the bridge which will become a wall when the bridge is raised.

Since a retracting bridge completely disappears, direction doesn't matter. Retracting bridges are the default, but if you selected "raising" by mistake, the command key for retracting is {{k|s}}.

=====Placement requirements=====
The error message 'Needs walkable perimeter' suggests that access is required all the way around the perimeter of the bridge, however, only one accessible adjacent tile is required. Placement of the bridge also requires that all of the tiles it occupies not have more than 1/7 water on them at the time of construction.

===Materials===
Bridges require stone, logs, and/or [[block]]s - they can be mixed - with blocks being placed significantly faster during the actual construction. The formula for the number of building materials needed is: number of tiles in the bridge divided by four, rounded down, plus one, or {size/4, rounded down}+1.

So, for example, a 3-tile bridge takes {3 tiles/4=3/4 -> 0} +1 = 1 building material. A 4-tile bridge takes {4/4=1} +1 = 2. A 5x10 bridge would require {50/4=12 1/2 -> 12} +1 = 13, and so on.

The "core" material of the bridge is the ''oldest'' individual building material used (i.e. the first item that was created in the fortress or that entered the map).{{cite forum|134816}} The core material determines the color, style, and description of the bridge, as well as the labor required for construction.

Care should be taken when choosing materials for bridges that will be exposed to [[fire]] or [[magma]]: Bridges built with non-[[magma-safe]] materials will heat up and eventually melt if the center tile (with bias towards the northwest if the center doesn't fall on a single tile) gets covered in magma or exposed to fire, whether the bridge is raised, lowered, or even retracted. The ability of a bridge to withstand heat is limited by the ''least'' fire-resistant item involved - a single non-magmaproof building block or mechanism will cause the whole bridge to deconstruct when exposed to sufficient heat. [[Dragonfire]] almost immediately melts nearly all bridges ([[slade]] being the prime exception).

==Raising and retracting bridges==
When designating a bridge to be built, you can choose to make it "retracting" (the default) or "raising". A retracting bridge disappears when it is "up" and become invisible, and a raising bridge is a "drawbridge", forming a visible wall when it's up. The "wall" is always just 1 z-level high x 1 tile thick (and as wide as the bridge is wide), no matter how long the "drawbridge" is when it's down. For raising bridges, you select which direction you want it to raise when you designate it to be built. This cannot be changed later, which would require deconstructing and rebuilding a new bridge.

All bridges can be either raised or retracted by linking it to a trigger with [[mechanism]]s - this requires a dwarf with the [[mechanics]] labor activated. Once the trigger (either a lever or pressure plate) is in place, use {{k|q}}uery on that trigger and select "link to {{k|b}}ridge". You will then get a pop-up map where you can cycle through all bridges that you have currently built in your fortress. Select one, and then select the 2 specific mechanisms you want to use to link the bridge. Quality of mechanism has no effect on the raising/lowering of the bridge, nor the time to install the mechanisms.

Any bridge, retracting or raising, of any size, will respond to the trigger signal 100 [[Time|tick]]s after the signal is sent. You can link more than one bridge to the same trigger and they will all respond simultaneously.

If a bridge is set to retract when trigger is activated, the bridge essentially disappears, ''tossing'' anything (friend, foe, or object) on the bridge onto whatever is underneath. Clearly this can be used to drop your enemies to rocky/watery/fiery deaths (or anything more imaginative you can think up!). Note that the creatures and objects are "tossed" with a semi-random initial velocity; this can reduce the lethality of pit traps (creatures bouncing off the walls lose the precious momentum that would otherwise result in an unsurvivable splat at the bottom), interfere with the reproducibility of dwarven !!SCIENCE!!, and be [[exploit]]ed as the key mechanic in [[#Coinstar training|coinstar training]].

If a bridge is set to raise when a lever is pulled, the bridge will become a [[wall]] along the edge selected with the {{k|w}}{{k|a}}{{k|d}}{{k|x}} keys when placing the bridge. When activated, the bridge "raises" very quickly, flinging anything on the bridge into the air, with unpleasant if not always deadly side effects. The resulting wall is always one z-level tall, watertight, and invulnerable to [[building destroyer]]s. Raising "drawbridges" can be used to block fortress entrances and corridors. When lowered, bridges will destroy most anything on the underlying tiles. By "destroying", we mean dwarves, foes, and items will entirely disappear from the game, a rare event which led to the creation of the term [[dwarven atom smasher]].

Any water displaced by a raising bridge is destroyed regardless of how much open space is on each side or above. Water resting atop a retracting bridge falls straight down after the bridge retracts.

==== And levers ====
Note that, depending on the design, retracting and raising bridges can provide the opposite reaction from an "open" signal. When the "open" signal is sent, both bridges "disappear" from view - the retracting bridge disappears completely, and the raising bridge becomes a 1-tile high, 1-tile thick wall. But this means that the raising bridge closes the passage on the same level with that wall that it creates on the "open" signal. This can be used to create either an "open" passage or "closed" passage on the "open" signal, depending on the design.

Of course, this is true for bridges and [[pressure plate]]s as well.

==Notes==

Bridges will not operate if any one creature of [[List of creatures by adult size#bridge|size 1,200,000]] or larger is on them. This weight limit is not cumulative - a bridge will still retract if a hundred goblins are standing on it, but a single [[rutherer]] accompanying those goblins will prevent the bridge from operating. Attempting to lower a drawbridge onto such a creature (in order to [[Dwarven atom smasher|atom-smash]] it) will cause the bridge itself to deconstruct. Attempting to "unretract" a bridge while such a creature is in any of the bridge tiles will similarly cause the bridge to deconstruct. The size limit does not apply to creatures inside cages.

It is impossible to channel out stone that is directly under a bridge, raised or not. Likewise digging a ramp under a bridge will not remove the floor tile. To remove these floor tiles, the bridge must be deconstructed. Note that [[obsidian casting]] can ''create'' new floor tiles under a bridge, which then behave in the manner above.

Big bridges can take weeks or even months to complete. You can shorten construction time by moving the materials to the site before starting construction, and by using blocks instead of stones. The material-gathering time is somewhat shorter for blocks due to their lesser weight, and the actual construction is three times faster for blocks.

'''Warning:''' while bridges do not provide structural [[support]], the game will still allow you to place [[construction]]s adjacent to them. Any construction that is completed when attached only to a bridge will cause an immediate [[cave-in]], often tossing the unlucky mason off the edge, to <s>a horrible death</s> any bystanders' great entertainment. However, a construction that connects to an existing supported construction when completed will not cause a cave-in, even if it is also adjacent to a bridge. To build constructions next to a bridge safely, ensure that ''all'' unbuilt constructions adjacent to a bridge are also adjacent to a construction that has already been completed. When building large constructions, it may be useful to [[suspend]] all tiles adjacent to a bridge until the neighboring constructions have been completed.
 '''Example:'''
{| class="wikitable"
|-
|Will cause a cave-in
|Will '''not''' cause a cave-in
|-
|
<diagram>
╔═╗[#3:0]▓[#]
║+║[#0:0][@6:0]O[#@]
╚═╝[#3:0]▓[#]
[#2:1].,'[#3:0]▓[#]
</diagram>
|
<diagram>
╔═╗[#3:0]▓[#]
║+║[#0:0][@6:0]O[#@]
╚═╝║
[#2:1]`,.[#]O
</diagram>
|}

Deconstructing bridges can be hazardous, as dwarves are not as compunctuous as with constructions and diggings to make sure no one is standing on them before destroying them.

A raised bridge cannot be linked to a lever from the inside - the mechanic must be able to access the center tile of the bridge when lowered.

If you aren't sure whether or not a 1 tile thick bridge is raised or lowered, try to build a piece of furniture, like a statue, on it. If it says blocked, the bridge is raised, if it says building present, it is lowered. You can also link another (longer) drawbridge to the same lever, to use as a visual indicator of the other bridge's status. Since this takes additional time and mechanisms, this is best reserved for when it's especially important that you know at a glance whether that bridge is blocking things.

==Uses==
Perhaps the most straightforward use of a bridge is spanning empty space or dangerous terrain. Bridges only need roughly 25% of the material that building [[floor]]s would require, and can be completed relatively quickly as well. Bridges are limited to a span of 20 tiles across open space; greater distances will require columns or other means of support. ("Floating" retracting bridges can be built into spans longer than 20 tiles, but they will deconstruct when support is checked.{{bug|9946}})

===Remote controlled gateways===
Lever-controlled bridges are one of the safer ways to control access. They are immune to building destroyers, though care must be taken to avoid operating them in the presence of exceptionally large creatures. [[Magma safe]] material should be used in the construction if there is any chance magma might flow over the bridge.

Retracting bridges built covering the top of a ramp or stairway can never be destroyed from beneath.

===Floodgates===
Raising bridges make a good replacement for most [[floodgate]] uses (e.g. flow and access control). They have the advantage of not being as easily jammed: they fling or [[Dwarven_atom_smasher|atom smash]] all items and all but the largest enemies on their tile/s when they open or close, whereas a floodgate or door will jam open with a discarded sock in it. Further, bridges cannot be destroyed by [[building destroyer]]s, while [[floodgate]]s can be. A single bridge can also be made up to ten tiles wide, potentially replacing ten floodgates and saving many mechanisims and much work. One minor downside of bridges compared to floodgates is that bridges with a width of 1 look the same when raised as when lowered, so it is easy to confuse whether they are closed or not. If you are unsure of a bridge's status, check the control lever if there is one (in most tilesets, lever to the right means closed), or try to build furniture on top of the bridge and check the resulting warning message ("blocked" means the bridge is raised, "building present" means it's lowered).

===Waste disposal===
{{Main|Dwarven atom smasher}}
Lowering raised bridges can be used as [[waste disposal]] for unwanted stones, [[refuse]], [[goblin]]s (dead or alive), legendary [[cheese]] makers and [[nobles]], to name a few. Even fluids get destroyed. Note, however, that lowering a drawbridge onto a sufficiently large creature (such as a [[forgotten beast]]) simply causes the bridge to deconstruct.

===[[Trap_design#Bridge_and_drop_traps|Traps]]===
Using two bridges at opposite ends of a corridor creates a very large and simple trap by walling in enemies. Or... Smashing them to tiny bits if placed to raise facing each other, with no space in between.
For added effect, place [[pressure plate]]s on both ends to raise the bridge when stepped on, to fling the units. If there is a [[floor]] directly above, they will be stunned. If there is a floor beneath the bridge, and if nobody is on the pressure plate, they will likely be smashed when the bridges come back down. If there is nothing above, they will land rather far away. Bonus points for making them land in a particularly [[Spike#Menacing_spike|nasty spot]].
If there is no floor beneath the bridge, they will fall, sometimes into something [[water|very,]] [[magma|very]] [[megabeast|bad.]]

===Minecart routing===
Lowered/extended bridges "cover" [[Minecart]] track corners constructed or carved underneath, allowing carts to travel in a straight line instead. This can let you change minecart routes via pulling levers.

===[[Cave-in]]s===
Since bridges don't support adjoining rock, it is possible to set up a cave-in so that dust can't come up, dwarves can't fall down, and flying creatures can't come up from beneath the cave-in before you set it off. Bridges are also instrumental in [[magma]]-piston applications.

===Improvised ceilings===
Building an outdoor structure, such as an [[Archery tower]], requires considerable expense and time. The reduced material requirements make bridges a viable alternative to roofing it up tile by tile. While it'll still be immune to [[Building destroyer]]s, a proper constructed ceiling is superior if you expect it to be exposed to [[Dragon|extreme temperatures]].

===Improvised walls===
[[Wall]]s cannot be built along map edges above ground, but raising bridges can. Because these bridges can be raised to act as walls, they can be used to control where wildlife, enemies, and [[caravan]]s spawn on the map edges.

A similar technique can be used to prevent fliers from spawning above ground, but it requires bridges to be built at ''every'' z-level. This requires considerable effort, as each bridge needs to be accessible to the dwarves building it, as well as needing support for each bridge. It can also be somewhat [[fun|risky]] if a dangerous creature suddenly spawns near a dwarf working on the bridge (especially in [[evil]] biomes). Note that this technique, when completed, will also prevent fliers from leaving the map.

===Ocean drains===
Designate ramps on the 2nd level below an ocean. Build a retracting bridge directly above the ramps (immediately under the ocean) leaving the ramps in place, and link it to a trigger. In order to build the bridge (and link it) you will need access to the level of the bridge. Now seal that access off (the constructed wall in the below diagram) so the chamber above the bridge is water tight. Now with the bridge in place, designate ramps up to the ocean adjacent to the bridge. Diggers with access to the level ''below'' the bridge can dig those ramps up from the level of the bridge, allowing the ocean to fill the chamber; even with the ramp squares underwater they can still dig them out. And not a drop of water will touch them... provided they clear out before you pull the lever.

Shown below is a 2x1 bridge (any size bridge can be used) before and after designating the ramps adjacent to the bridge. The stairs and passage on Z2 satisfy the 'Needs walkable perimeter' requirement and provide access to the top of the bridge for linking to a trigger. The passage is then blocked with a wall to make it water tight.

Before breaking through After
side X side Y side X side Y
Z3 ≥≥≥≥≥≥≥ ≥≥≥≥≥≥≥≥≥≥ ≥≥>≥>≥≥ ≥≥≥≥≥≥≥≥≥≥
Z2 ###B### ##Z_X_BB## ##^B^## ##Z_X_BB##
Z1 ###^### Z ^^## ###^### Z ^^##
Z0 ####### ########## ####### ##########

≥ = Water with floor > = Water without floor Z = Stairs
^ = Ramp # = Solid Rock X = Constructed Wall _ = Floor (not constructed)

===Caravan exits===
A bridge to nowhere, built well above ground level at the edge of the map, can sometimes serve as a handy exit for [[caravan]]s and [[diplomat]]s when your fortress is under [[siege]].

===Stops on the elevator===
Designate a dumpsite or set up a floodgate at the top of a shaft; use multiple remote-controlled bridges to decide on which level the stuff, water, magma etc. gets off. (bonus: use water falling at one end of the bridge to flush stuff off that was dropped onto the other end without the manual labor)

===Single lever airlock===
Raising bridges and retracting bridges controlled by a single lever will be in opposite states of being open or closed. When one is closed (raised) the other is open (retracted) and vice versa. This fact can be used to construct airlocks that are not vulnerable to [[building destroyer|building destroyers]] or mistimed lever pulls e.g.
Side View:
Z1 XXXXXXR____ D = Raising drawbridge / = Ramp _ = Floor
Z0 D_____/XXXX R = Retracting bridge X = Solid Rock or Constructed Wall

With a suitably long distance between the two bridges, the controlling lever can be placed within the airlock, and by setting the profile of the lever specific dwarves can be moved between isolated areas.

===Decorations===
Bridges benefit from two [[quality]] modifiers--one for the [[architect]]'s design, and one for the builder's creation, and their multipliers are also applied to any attached mechanisms. High-quality bridges can inspire happy [[thought]]s in your dwarves and help meet room value needs. Bridges may also be used to form [[mosaic]]s or even [[Style_project#Mosaics|animations]].

===Coinstar training===
The mechanical "tossing" action of retracting bridges can be used for training [[armor user]] and associated traits by repeatedly flinging small items at the trainee. See [[Danger_room#Coinstar_Room|Danger room]] for more information.
Alternatively, this design can be used as a trap: invaders atop a retracting bridge inside locked room will get thrown around and optionally pummelled with "ammunition" like stones or weapons placed in the room.

==Bugs==
* Metal bridges can be constructed by dwarves with any of the "metalsmith" skills enabled, however the builder's blacksmith skill is used to determine quality{{bug|4899}}
* Trees grow through bridges, may make the bridges unusable{{bug|7872}}
* Retracting bridges can be built without support, but will deconstruct when support is checked{{bug|9946}}

{{Translation
| dwarven = sazir
| elvish = valóna
| goblin = romnu
| human = ori
}}

{{buildings}}
{{Category|Buildings}}

Tigereye

2022-08-31T15:15:28Z

Xjtu-blacksmith: fix wiki link

{{quality|Exceptional|21:54, 7 December 2010 (UTC)}}{{gemlookup/0|wiki=Tiger's eye}}{{av}}

'''Tigereyes''' are unremarkable low-value [[gem]]s found in [[sedimentary layer]]s.

== In Real Life ==
Tiger's eye (also called Tigers eye or Tiger eye) is a chatoyant gemstone that is usually a metamorphic rock that is a golden to red-brown color, with a silky luster. A member of the quartz group, it is a classic example of pseudomorphous replacement by silica of fibrous crocidolite (blue asbestos). An incompletely silicified blue variant is called Hawk's eye.

[[File:Tig.jpg|center|thumb|300px]]

{{gamedata}}
{{gems}}

DF2014:Spar

2022-08-26T12:54:27Z

Xjtu-blacksmith: Fix redirect

#REDIRECT [[DF2014:Training]]

Shrine (megabeast)

2022-08-26T11:59:32Z

Xjtu-blacksmith: typo

{{Quality|Superior|12:54, 11 April 2021 (UTC)}}
{{av}}
[[File:Shrine.png|thumb|right|180px|A shrine of [[red sand]], decorated with pillars and floors of [[gneiss]]. A [[bronze colossus]] inhabits it.]]
:''Not to be confused with [[Temple#Shrines|small religious locations at civilized sites]].''

'''Shrines''' ({{Raw Tile|Å|7:0:0}}) are a type of [[site]], functioning identically to a [[lair]]. They consist of cubic open spaces decorated with pillars, and some smoothed floors. [[Bronze colossus]]es, [[titan]]s, and sometimes also [[demon|demons]] make their homes at shrines, and will aggressively defend their territory when approached. Shrines will often be littered with the [[corpse]]s of past adventurers who tried to fight their inhabitants but failed.

A shrine can be discovered in [[adventurer mode]] either by travelling, or by asking local people about either the surrounding area, or local beasts. As you approach the site, the beast living there will charge at you the moment it notices your presence, making [[stealth]] an attractive choice when setting foot near a shrine. Becoming a [[necromancer]] and reviving the dozens, if not hundreds of corpses to do your bidding is also a wise choice, however you may be left with an army of skeletons that attack any living sapient being on sight.

{{Translation| dwarven = okun | elvish = dama | goblin = stodrus | human = lipul}}

{{World}}

{{Category|Adventurer mode}}

Semi megabeast

2022-08-26T11:41:44Z

Xjtu-blacksmith: fix redirect

#REDIRECT [[Semi-megabeast]]

Puzzleboxe

2022-08-26T09:11:51Z

Xjtu-blacksmith: Xjtu-blacksmith moved page Puzzleboxe to Puzzlebox: typo

#REDIRECT [[Puzzlebox]]