Dwarf Fortress Wiki - User contributions [en]

Dwarf Fortress Wiki talk:Quality

2010-05-10T21:05:51Z

Oddtwang of Dork: /* Quality categories by version namespace */

==Stone, gem and similar articles==
Any thoughts on how to rate these? Many of them seem to be tagged as stubs, but the stone template in particular seems to me to cover most of the salient information. [[User:Oddtwang of Dork|Oddtwang of Dork]] 20:20, 25 April 2010 (UTC)

==who rates those articles==
who rates those articles?
::I have been. If I shouldn't be, someone say so now. Also, should ~100% of content articles be rated? --[[User:StrongAxe|StrongAxe]] 18:42, 15 April 2010 (UTC)
:::As there isn't much of a vandalism thing going on here, I think it should be the original author of the article who rates it, with some admin verification following--[[User:Smd|Smd]] 15:25, 17 April 2010 (UTC)
::::Anyone and everyone should be rating the articles. Don't agree with an article rating? leave a note why on the talk page and re-rate the page in question. --[[User:Briess|Briess]] 01:35, 22 April 2010 (UTC)

:Anybody can rate an article, it's a wiki and we're ''supposed to'' all work together. Just try to correct or update anything that needs changing. If you spot vandalism, go to the '''history''' tab next to the discussion/edit tabs and revert the page to a pre-vandal version. [[Special:Contributions/97.90.193.201|97.90.193.201]] 17:57, 20 April 2010 (UTC)

== Changing levels ==
:There was a discussion [http://www.bay12forums.com/smf/index.php?topic=54970.msg1183319#msg1183319 on the forums] involving changing the quality levels to Fine, Exceptional, and Masterwork. Yes/no?--[[User:Draco18s|Draco18s]] 17:29, 23 April 2010 (UTC)
::I think this is a great idea. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 17:31, 23 April 2010 (UTC)
::I second. The forum thread linked above garnered broad support for -Fine-, +Exceptional+, *Masterwork* after discussing several options. -Grae
:::Agreed, with the quality modifiers in place, they're awesome for this wiki. I mean, what's more Dwarf Fortressy than having a good *article*? --[[User:Aescula|Aescula]] 21:32, 25 April 2010 (UTC)
::Indeed, it seems to fit the game better rather than fit with common player perceptions of the races in game.[[User:Vattic|Vattic]] 20:51, 23 April 2010 (UTC)
::Although I think the Fine, Exceptional, Masterwork is a better grading scheme I have to question the need for more than two levels. Either an article doesn't have enough information (currently Elven) or it does (currently Human or Dwarven. The distinction between the top too levels is mostly in how it links to other articles which I think is a poor way to grade. For example you could make a Human article Dwarven by removing any red links or badly formed links but arguably this reduces the quality of the article itself. So I'd suggest just having a rating for poor pages and leaving good ones without any tag. --[[User:Shades|Shades]] 14:51, 26 April 2010 (UTC)
:::I think there is some value to pointing out articles that are not only accurate and full of all the information, but also easy to navigate within and between. Hence the distinction between what is good and great. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 16:28, 26 April 2010 (UTC)
::::But that is not what we are doing as by removing the links on a Human article you can end up with a Dwarven article. That is not a good reinforcement. --[[User:Shades|Shades]] 07:50, 27 April 2010 (UTC)
:::::I added another category requirement for an Exceptional article now. --[[User:Briess|Briess]] 00:15, 2 May 2010 (UTC)

== Template/method ==

I see that this was set up with different templates for each quality level. Is that really the best way to go? Couldn't instead of <nowiki> {{elven}} {{dwarven}} {{human}} </nowiki> could we do <nowiki> {{Quality|<low>}} {{Quality|<med>}} {{Quality|<high>}} </nowiki> (for whatever those three are)? Thoughts? [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 17:50, 23 April 2010 (UTC)
:That seems far more sensible to me. The three tags are now very confusing if you don't happen to have been around while the quality thing's been introduced. [[User:Oddtwang of Dork|Oddtwang of Dork]] 15:47, 25 April 2010 (UTC)
::I also agree - it would centralize the formatting rules, and even potentially allow people to set what kind of label they want to see. --[[User:Krenn|Krenn]] 07:06, 26 April 2010 (UTC)
:::Feel free to implement this if you feel so inclined. --[[User:Briess|Briess]] 00:15, 2 May 2010 (UTC)
::::Alright, I'll try to work on this tonight. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 19:30, 3 May 2010 (UTC)

This started out as a project to point what needs fixing. Fine is a '''terrible''' name for the bottom quality rank. If you are hell-bent on driving the DF reference all the way, make the lowest rank XShoddyX [[User:VengefulDonut|VengefulDonut]] 12:39, 6 May 2010 (UTC)

:Also, the comments on the forums seem to be more objections than suggestions. Perhaps the original elven/human/dwarven ranking would work. [[User:VengefulDonut|VengefulDonut]] 12:45, 6 May 2010 (UTC)
::I'd also like to nitpick that the current labels, "-Fine-" "+Exceptional+" and "*Masterwork*", are wrong - they ''should'' be "+Fine+" "≡Exceptional≡" and "☼Masterwork☼". --[[User:Quietust|Quietust]] 13:00, 6 May 2010 (UTC)

:I think the purpose of pointing to what needs fixing works just as fine regardless of names. Anyone who cliks those links (which anyone who wants to fix things on the wiki probably will) understand what fine pages need more work.
:I don't think elven/human/dwarven was any better at showing what needs improvement. While fine/exceptional/masterwork might not accurately measure the bottom level, at least it shows a gradient which elven/human/dwarven does not. I have no objection to bumping it to 4 levels (I think something LIKE stub could be there, shoddy isn't bad) that seems like a very good idea to me.
:Vengeful, I know there are a lot of objections but when asked for some suggestions this change seemed very highly requested. I simply implmented it because I agreed that "elven" doesn't really equal "bad" or even "worse then human".
:Yeah, Agreed Quiest, I'll change that. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 14:30, 6 May 2010 (UTC)

::We don't need more levels. We just need the labels for the current levels to match their purpose. The bottom level, which represents "needs improvement" articles, needs to have a tag that sounds '''bad'''. xTatteredx and xShoddyx would fit the current theme. Replacing it all with number ranks would solve it (say, level of magma). As long as the label doesn't directly conflict with the purpose of the category, the way fine does. [[User:VengefulDonut|VengefulDonut]] 14:54, 6 May 2010 (UTC)

:::Sounds good, it was a little work to make sure the shift happened correctly. If you want to do the change to "Shoddy" or "Tattered" then cool, otherwise I'll maybe do it sometime this week. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 17:24, 10 May 2010 (UTC)

::::Something a little negative about that, isn't there? "Stub" says 'this needs more adding to it' whereas "shoddy" says 'what's here isn't much cop'. I agree that "Fine" is probably a bit generous. Offhand, however, I don't have another suggestion for the lowest level.
::::There's probably an argument to make that the middle level would be better as "Fine" if the lowest is changed - I think there's a clearer distinction then between it and the top level. [[User:Oddtwang of Dork|Oddtwang of Dork]] 21:02, 10 May 2010 (UTC)

==Quality categories by version namespace==

Is there a relatively simple way to view a list of, say, all DF2010 articles of Fine quality? If not, could there be? It would be quite handy for targeting articles to be improved. --[[User:FunkyWaltDogg|FunkyWaltDogg]] 03:29, 8 May 2010 (UTC)
:Doing so would require editing the {{tl|Quality}} template itself, though it might not be a bad idea. --[[User:Quietust|Quietust]] 04:04, 8 May 2010 (UTC)
::I was thinking of doing that. We'll leave this here for a little so people can comment on it, but then if noone opposes I'll make the change. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 17:22, 10 May 2010 (UTC)
:::With this in place, would calculating the "Overall quality rating" for each version not be more useful? Either for each namespace or for each + the articles in the mainspace, maybe? [[User:Oddtwang of Dork|Oddtwang of Dork]] 21:05, 10 May 2010 (UTC)

==Drop in overall quality rating==
Why has the quality rating seen on the main page dropped so precipitously? It was at over 20% a week or two ago, now it is at 11%. Is this due to articles being rerated downward, or due to the hundreds of nearly-stub pages such as [[DF2010:Aquamarine]]? Has the calculation method changed? Or another cause? —[[User:0x517A5D|0x517A5D]] 20:19, 9 May 2010 (UTC)
:Almost certainly the latter, and probably partially my fault - whenever I find a page that has no rating at all, I just give it a "Fine" rating so it at least has a rating ''at all'' - I'm of the opinion that it's better for a page to be underrated than completely unrated. --[[User:Quietust|Quietust]] 21:33, 9 May 2010 (UTC)
::And I agree, the lowest rating should be applied to the worst articles. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 17:21, 10 May 2010 (UTC)
:::Given that a bunch of the articles have been blindly categorized as "Fine", I'm going through and rerating a bunch of them as "Unrated" which will place them in a distinct category so other users can provide more accurate ratings. It would probably be beneficial to make the template recognize this rating and list it on this project page (and somehow include them on the progress bar thingy). --[[User:Quietust|Quietust]] 19:36, 10 May 2010 (UTC)

== Criteria ==

Currently, having a "substantial number of redlinks" is grounds for an article being rated as Fine. While this is okay for new pages, it's a bit unfair to articles in the 23a namespace, where most of the content is concrete but simply hasn't been imported from the Archive wiki yet. Should this distinguish between redlinks due to incorrect formatting versus redlinks due to pending creation of other pages? --[[User:Quietust|Quietust]] 19:48, 10 May 2010 (UTC)
:I tend to think the rules should be ''substantially'' different in the 23a namespace, as it is essentially historical content being ported into the current wiki for reference purposes. So I would actually argue that 23a pages should not be rated at all, nor taken into account in the quality rating. Speaking of that, it used to be wiki policy to make minimal edits — don't these repeated ratings lead to extra entries in the page histories and extra disk space consumed? Or are the ratings handled thru a database entry maybe? —[[User:0x517A5D|0x517A5D]] 19:57, 10 May 2010 (UTC)
::By that argument, should not 40d articles also be exempt from being rated? --[[User:Quietust|Quietust]] 20:20, 10 May 2010 (UTC)
:::Disk space is not a concern. However, fine as the bottom rating of articles is not fine. --[[User:Briess|Briess]] 20:22, 10 May 2010 (UTC)

Dwarf Fortress Wiki talk:Quality

2010-05-10T21:02:21Z

Oddtwang of Dork: /* Template/method */

==Stone, gem and similar articles==
Any thoughts on how to rate these? Many of them seem to be tagged as stubs, but the stone template in particular seems to me to cover most of the salient information. [[User:Oddtwang of Dork|Oddtwang of Dork]] 20:20, 25 April 2010 (UTC)

==who rates those articles==
who rates those articles?
::I have been. If I shouldn't be, someone say so now. Also, should ~100% of content articles be rated? --[[User:StrongAxe|StrongAxe]] 18:42, 15 April 2010 (UTC)
:::As there isn't much of a vandalism thing going on here, I think it should be the original author of the article who rates it, with some admin verification following--[[User:Smd|Smd]] 15:25, 17 April 2010 (UTC)
::::Anyone and everyone should be rating the articles. Don't agree with an article rating? leave a note why on the talk page and re-rate the page in question. --[[User:Briess|Briess]] 01:35, 22 April 2010 (UTC)

:Anybody can rate an article, it's a wiki and we're ''supposed to'' all work together. Just try to correct or update anything that needs changing. If you spot vandalism, go to the '''history''' tab next to the discussion/edit tabs and revert the page to a pre-vandal version. [[Special:Contributions/97.90.193.201|97.90.193.201]] 17:57, 20 April 2010 (UTC)

== Changing levels ==
:There was a discussion [http://www.bay12forums.com/smf/index.php?topic=54970.msg1183319#msg1183319 on the forums] involving changing the quality levels to Fine, Exceptional, and Masterwork. Yes/no?--[[User:Draco18s|Draco18s]] 17:29, 23 April 2010 (UTC)
::I think this is a great idea. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 17:31, 23 April 2010 (UTC)
::I second. The forum thread linked above garnered broad support for -Fine-, +Exceptional+, *Masterwork* after discussing several options. -Grae
:::Agreed, with the quality modifiers in place, they're awesome for this wiki. I mean, what's more Dwarf Fortressy than having a good *article*? --[[User:Aescula|Aescula]] 21:32, 25 April 2010 (UTC)
::Indeed, it seems to fit the game better rather than fit with common player perceptions of the races in game.[[User:Vattic|Vattic]] 20:51, 23 April 2010 (UTC)
::Although I think the Fine, Exceptional, Masterwork is a better grading scheme I have to question the need for more than two levels. Either an article doesn't have enough information (currently Elven) or it does (currently Human or Dwarven. The distinction between the top too levels is mostly in how it links to other articles which I think is a poor way to grade. For example you could make a Human article Dwarven by removing any red links or badly formed links but arguably this reduces the quality of the article itself. So I'd suggest just having a rating for poor pages and leaving good ones without any tag. --[[User:Shades|Shades]] 14:51, 26 April 2010 (UTC)
:::I think there is some value to pointing out articles that are not only accurate and full of all the information, but also easy to navigate within and between. Hence the distinction between what is good and great. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 16:28, 26 April 2010 (UTC)
::::But that is not what we are doing as by removing the links on a Human article you can end up with a Dwarven article. That is not a good reinforcement. --[[User:Shades|Shades]] 07:50, 27 April 2010 (UTC)
:::::I added another category requirement for an Exceptional article now. --[[User:Briess|Briess]] 00:15, 2 May 2010 (UTC)

== Template/method ==

I see that this was set up with different templates for each quality level. Is that really the best way to go? Couldn't instead of <nowiki> {{elven}} {{dwarven}} {{human}} </nowiki> could we do <nowiki> {{Quality|<low>}} {{Quality|<med>}} {{Quality|<high>}} </nowiki> (for whatever those three are)? Thoughts? [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 17:50, 23 April 2010 (UTC)
:That seems far more sensible to me. The three tags are now very confusing if you don't happen to have been around while the quality thing's been introduced. [[User:Oddtwang of Dork|Oddtwang of Dork]] 15:47, 25 April 2010 (UTC)
::I also agree - it would centralize the formatting rules, and even potentially allow people to set what kind of label they want to see. --[[User:Krenn|Krenn]] 07:06, 26 April 2010 (UTC)
:::Feel free to implement this if you feel so inclined. --[[User:Briess|Briess]] 00:15, 2 May 2010 (UTC)
::::Alright, I'll try to work on this tonight. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 19:30, 3 May 2010 (UTC)

This started out as a project to point what needs fixing. Fine is a '''terrible''' name for the bottom quality rank. If you are hell-bent on driving the DF reference all the way, make the lowest rank XShoddyX [[User:VengefulDonut|VengefulDonut]] 12:39, 6 May 2010 (UTC)

:Also, the comments on the forums seem to be more objections than suggestions. Perhaps the original elven/human/dwarven ranking would work. [[User:VengefulDonut|VengefulDonut]] 12:45, 6 May 2010 (UTC)
::I'd also like to nitpick that the current labels, "-Fine-" "+Exceptional+" and "*Masterwork*", are wrong - they ''should'' be "+Fine+" "≡Exceptional≡" and "☼Masterwork☼". --[[User:Quietust|Quietust]] 13:00, 6 May 2010 (UTC)

:I think the purpose of pointing to what needs fixing works just as fine regardless of names. Anyone who cliks those links (which anyone who wants to fix things on the wiki probably will) understand what fine pages need more work.
:I don't think elven/human/dwarven was any better at showing what needs improvement. While fine/exceptional/masterwork might not accurately measure the bottom level, at least it shows a gradient which elven/human/dwarven does not. I have no objection to bumping it to 4 levels (I think something LIKE stub could be there, shoddy isn't bad) that seems like a very good idea to me.
:Vengeful, I know there are a lot of objections but when asked for some suggestions this change seemed very highly requested. I simply implmented it because I agreed that "elven" doesn't really equal "bad" or even "worse then human".
:Yeah, Agreed Quiest, I'll change that. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 14:30, 6 May 2010 (UTC)

::We don't need more levels. We just need the labels for the current levels to match their purpose. The bottom level, which represents "needs improvement" articles, needs to have a tag that sounds '''bad'''. xTatteredx and xShoddyx would fit the current theme. Replacing it all with number ranks would solve it (say, level of magma). As long as the label doesn't directly conflict with the purpose of the category, the way fine does. [[User:VengefulDonut|VengefulDonut]] 14:54, 6 May 2010 (UTC)

:::Sounds good, it was a little work to make sure the shift happened correctly. If you want to do the change to "Shoddy" or "Tattered" then cool, otherwise I'll maybe do it sometime this week. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 17:24, 10 May 2010 (UTC)

::::Something a little negative about that, isn't there? "Stub" says 'this needs more adding to it' whereas "shoddy" says 'what's here isn't much cop'. I agree that "Fine" is probably a bit generous. Offhand, however, I don't have another suggestion for the lowest level.
::::There's probably an argument to make that the middle level would be better as "Fine" if the lowest is changed - I think there's a clearer distinction then between it and the top level. [[User:Oddtwang of Dork|Oddtwang of Dork]] 21:02, 10 May 2010 (UTC)

==Quality categories by version namespace==

Is there a relatively simple way to view a list of, say, all DF2010 articles of Fine quality? If not, could there be? It would be quite handy for targeting articles to be improved. --[[User:FunkyWaltDogg|FunkyWaltDogg]] 03:29, 8 May 2010 (UTC)
:Doing so would require editing the {{tl|Quality}} template itself, though it might not be a bad idea. --[[User:Quietust|Quietust]] 04:04, 8 May 2010 (UTC)
::I was thinking of doing that. We'll leave this here for a little so people can comment on it, but then if noone opposes I'll make the change. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 17:22, 10 May 2010 (UTC)

==Drop in overall quality rating==
Why has the quality rating seen on the main page dropped so precipitously? It was at over 20% a week or two ago, now it is at 11%. Is this due to articles being rerated downward, or due to the hundreds of nearly-stub pages such as [[DF2010:Aquamarine]]? Has the calculation method changed? Or another cause? —[[User:0x517A5D|0x517A5D]] 20:19, 9 May 2010 (UTC)
:Almost certainly the latter, and probably partially my fault - whenever I find a page that has no rating at all, I just give it a "Fine" rating so it at least has a rating ''at all'' - I'm of the opinion that it's better for a page to be underrated than completely unrated. --[[User:Quietust|Quietust]] 21:33, 9 May 2010 (UTC)
::And I agree, the lowest rating should be applied to the worst articles. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 17:21, 10 May 2010 (UTC)
:::Given that a bunch of the articles have been blindly categorized as "Fine", I'm going through and rerating a bunch of them as "Unrated" which will place them in a distinct category so other users can provide more accurate ratings. It would probably be beneficial to make the template recognize this rating and list it on this project page (and somehow include them on the progress bar thingy). --[[User:Quietust|Quietust]] 19:36, 10 May 2010 (UTC)

== Criteria ==

Currently, having a "substantial number of redlinks" is grounds for an article being rated as Fine. While this is okay for new pages, it's a bit unfair to articles in the 23a namespace, where most of the content is concrete but simply hasn't been imported from the Archive wiki yet. Should this distinguish between redlinks due to incorrect formatting versus redlinks due to pending creation of other pages? --[[User:Quietust|Quietust]] 19:48, 10 May 2010 (UTC)
:I tend to think the rules should be ''substantially'' different in the 23a namespace, as it is essentially historical content being ported into the current wiki for reference purposes. So I would actually argue that 23a pages should not be rated at all, nor taken into account in the quality rating. Speaking of that, it used to be wiki policy to make minimal edits — don't these repeated ratings lead to extra entries in the page histories and extra disk space consumed? Or are the ratings handled thru a database entry maybe? —[[User:0x517A5D|0x517A5D]] 19:57, 10 May 2010 (UTC)
::By that argument, should not 40d articles also be exempt from being rated? --[[User:Quietust|Quietust]] 20:20, 10 May 2010 (UTC)
:::Disk space is not a concern. However, fine as the bottom rating of articles is not fine. --[[User:Briess|Briess]] 20:22, 10 May 2010 (UTC)

v0.31:Fat

2010-05-02T17:09:00Z

Oddtwang of Dork:

{{av}}{{stub}}

Fat is obtained by {{L|Butcher's shop|butchering}} an animal.

It can be rendered into {{L|tallow}} in a {{L|kitchen}}. {{L|Tallow}} is used in the production of {{L|soap}}.

Previously a whole stack of fat was processed per job. Now each process fat job processes a single item from the stack, not the entire stack.

v0.31:Reactions

2010-04-30T12:23:12Z

Oddtwang of Dork:

{{av}}
{{human}}
'''Reactions''' are moddable crafting formulas. They can be tweaked and added onto to allow smelting of new metals, alloys, and many other products. They must be assigned to specific [[Entities]]; if not explicitly added to an entity's definition, they will not be able to produce that reaction. For examples of various forms of reaction, see {{l|Reaction Examples}}.

Currently, a reaction can only result in an object of base quality.

==Reaction Makeup==
[REACTION:<REACTION_IDENTIFIER>]
[NAME:<REACTION_NAME>]
<... [[#Buildings]] One or more reagent declarations ...>
<... [[#Reagents]] Zero or more reagent declarations...>
<... [[#Products]] Zero or more reagent declarations ...>
<... [[#Reaction Modifiers]] Zero or more reagent declarations ...>
<... [[#Skills]] Zero or more skill declarations ...>

'''<REACTION_IDENTIFIER>''' - Refers to a unique identifier for the reaction (Used in Entity Raws to allow an Entity to make use of the reaction.

'''<REACTION_NAME>''' - String displayed in the building for the reaction.

==Entity Use==
In order for an entity to use the reaction a [PERMITTED_REACTION:] tag must be added. It works by using the '''<REACTION_IDENTIFIER>''' after the colon.
[PERMITTED_REACTION:<REACTION_IDENTIFIER>]

==Buildings==
Each reaction requires a building to be declared for it to be used at.

[BUILDING:<BUILDING_IDENTIFIER>:<BUILDING_KEY>]

'''<BUILDING_IDENTIFIER''' - The building at which this reaction can be used. NOTE: SMELTER, KILN, KITCHEN and TANNER seem to be the only non-custom buildings allowed to be specified at this point.{{verify}}

'''<BUILDING_KEY>''' - The key that is pressed at the building (Such as 'b' for bed at a Carpenter or a block at a Mason's). If two reactions have the same key, then one of them will be assigned a different key, the first alphabetically available at the building.

==Reagents==
A reagent is some object that is required to produce whatever the intended object is. This is typically something like needing the ore of a metal to smelt bars of it.

===Reagent Types===
[REAGENT:<Identifier>:<Quantity>:<ITEM_TOKEN>:<ITEM_SUBTYPE>:<MATGLOSS_TOKEN>:<MATGLOSS_SUBTYPE>]
or
[REAGENT:<Identifier>:<Quantity>:<MATGLOSS_TOKEN>:<MATGLOSS_SUBTYPE>]

Type 1: Is used for reactions where a specific type of object is required, such as a BUCKET, SWORD, etc.

Type 2: Is used for when only a material type is needed, such as METAL_ORE for smelter reactions.

<Identifier> - Used to refer to this reagent in the reaction Product.

<Quantity> - Used to refer to the number of individual units of the reagent needed for the reaction. NOTE: If a bar, thread, or cloth is used as the <ITEM_TOKEN>, then this value refers to the PRODUCT_DENSITY of the object (150, 15000, 10000 respectively).

<ITEM_TOKEN> - Refers to the hard coded ITEM_TOKEN that the reagent must be.

<ITEM_SUBTYPE> - Refers to a specific item subtype, defined in the raws, of a specific ITEM_TOKEN, such as TOY:ITEM_TOY_MINIFORGE.

<MATGLOSS_TOKEN> - Refers to the hardcoded material type of the reagent, such as PLANT_MAT, METAL_ORE, etc.

<MATGLOSS_SUBTYPE> - Refers to a specific item subtype, defined in the raws, of a specific MATGLOSS_TOKEN, such as INORGANIC:MICA. In the case of a plant type the syntax is slightly different, the MATGLOSS_SUBTYPE is actually <PLANT_NAME>:<PLANT_PART>.

''<PLANT_NAME>'' - Refers to the actual plant's name in the raw files.

''<PLANT_PART>'' - Refers to the plant 'part' you want, whether it's the PLANT, WOOD, LEAVES, SEED, etc.

===Reagent Modifier===
A reagent can be modified by attaching one, or more, of the following. The modification is used to narrow the available items that can be used for the reaction.

'''[PRESERVE_REAGENT]''' - Reagent is not destroyed, which is the normal effect, at the completion of the reaction. Typically used for containers.

'''[REACTION_CLASS:X]''' - Reagent's MATGLOSS_SUBTYPE must have a REACTION_CLASS of type X attached to it. Such as the various forms of Gypsum having [REACTION_CLASS:GYPSUM] in them. Reaction classes are not hard-coded and you may freely insert REACTION_CLASS tags with custom "X" types into object definitions that will be used as reagents.

'''[HAS_MATERIAL_REACTION_PRODUCT:X]''' - Reagent's MATGLOSS_SUBTYPE must have a MATERIAL_REACTION_PRODUCT tag. This is used primarily on items that come from a dead, or butchered, animal such as skins or fat for tanning and rendering.

'''[UNROTTEN]''' - Reagent must not be rotten, mainly for organic MATGLOSS types.

'''[BUILDMAT]''' - Reagent is able to be used to build structures (Stone, Wood, Blocks, Bars?).

'''[GLASS_MATERIAL]''' - Reagent has a one of the glass MATGLOSS types.

'''[WORTHLESS_STONE_ONLY]''' - Only use objects allowed in the Stone Menu.

'''[FIRE_BUILD_SAFE]''' - Reagent must be considered fire safe (INORGANIC, excluding COAL types).

'''[MAGMA_BUILD_SAFE]''' - Reagent must be considered magma safe (INORGANIC, with a melting point greater than the temperature of Magma.

'''[CAN_USE_ARTIFACT]''' - Reagent can be an Artifact.

'''[ANY_PLANT_MATERIAL]''' - Reagent MATGLOSS must be of a plant subtype.

'''[ANY_SILK_MATERIAL]''' - Reagent MATGLOSS must be of a silk type.

'''[ANY_SOAP_MATERIAL]''' - Reagent MATGLOSS must be of a soap type.

'''[ANY_LEATHER_MATERIAL]''' - Reagent MATGLOSS must be of a leather type.

'''[ANY_BONE_MATERIAL]''' - Reagent MATGLOSS must be of a bone type.

'''[ANY_SHELL_MATERIAL]''' - Reagent MATGLOSS must be of a shell type.

'''[ANY_TOOTH_MATERIAL]''' - Reagent MATGLOSS must be of a tooth type.

'''[ANY_HORN_MATERIAL]''' - Reagent MATGLOSS must be of a horn type.

'''[ANY_PEARL_MATERIAL]''' - Reagent MATGLOSS must be of a pearl type (Excretion from sea creatures?)

'''[USE_BODY_COMPONENT]''' - Reagent MATGLOSS must come off a creature's body.

'''[METAL_ORE]''' - Reagent MATGLOSS must be a metal ore.

'''[NOT_WEB]''' - States that the material cannot be web (For making only plant/adamantine thread?).

'''[WEB_ONLY]''' - States that the material has to be web (For making only silk thread?).

'''[POTASHABLE]''' - The reagent must be able to be turned into pot ash.

'''[EMPTY]''' - If the reagent is a container, it must be empty.

'''[CONTAINS_LYE]''' - If the reagent is a container, it must contain LYE.

'''[NOT_CONTAIN_BARREL_ITEM]''' - If the reagent is a Barrel, it must not contain an item that has to reside in a barrel (Such as alcohol?).

'''[BAG]''' - Reagent has to be a bag. Intended to be used with an item type of BOX, to prevent chests, coffers, and other containers from being used instead.

==Products==
These are the results of a given reaction. There may be any number of such results.

===Product Format===
[PRODUCT:<CHANCE>:<QUANTITY>:<ITEM_TOKEN>:<ITEM_SUBTYPE>:<MATGLOSS>:<MATGLOSS_SUBTYPE>]

'''<CHANCE>''' - This is the chance (As a percent) that the <QUANTITY> number of items will be created after this reaction completes.

'''<QUANTITY>''' - This is the number of the item to be created.

'''<ITEM_TOKEN>''' - This is the ITEM_TOKEN of the result.

'''<ITEM_SUBTYPE>''' - This is a ITEM_SUBTYPE listed in an actual Raw File.

'''<MATGLOSS>''' - This is the MATGLOSS of the item. If you want to use the MATGLOSS information of a Reagent, then this is GET_MATERIAL_FROM_REAGENT:IDENTIFIER, where IDENTIFIER is the reagent's identifier in the reaction.

'''<MATGLOSS_SUBTYPE>''' - Refers to a specific item subtype, defined in the raws, of a specific MATGLOSS_TOKEN, such as PLANT_MAT:MUSHROOM_HELMET_PLUMP. If GET_MATERIAL_FROM_REAGENT was used in the MATGLOSS, you can specify a type, or you can state NONE, to recieve the MATGLOSS_SUBTYPE of the reagent.

Note that vermin can be created by using code similar to: [PRODUCT:100:1:VERMIN:NO_SUBTYPE:ROACH_LARGE:ROACH_LARGE]

===Product Modifiers===
Each product may have a zero, or more, modifiers following its declaration.

'''[PRODUCT_TO_CONTAINER:<IDENTIFIER>]''' - This states that the product should be put into a specific container listed in as a reagent.

''<IDENTIFIER>'' - Refers back to a reagent identifier.

'''[PRODUCT_DIMENSIONS:<DIMENSION>]''' - Used to specify the dimensions of the object, primarily for use with bars, threads, and cloth.

''<DIMENSION>'' - The 'size' of the object, for use in reactions that require a certain amount of bars, threads and cloth. 'Normal' size is bars = 150, threads = 15000 and cloth = 10000.{{verify}}

==Reaction Modifiers==
Reactions can be further modified by the adding zero or more of the following.

'''[FUEL]''' - Which states that it must take some form of COAL (COKE or CHARCOAL) to fuel it. If the building requires magma, it's assumed that this tag is ignored.

'''[AUTOMATIC]''' - Meaning that if the reagents are present, this reaction is automatically added to the work list of the building, such as 'Butcher Animal' at a Butcher's or 'Gather Web' at a Loom.

==Skills==
Skills have to be associated with a reaction. This dictates what skill receives the experience and who can do the job. More than one skill can be associated with the reaction, but only the last SKILL on the list, that a dwarf can perform, receives experience.

[SKILL:<SKILL_TOKEN>]

'''<SKILL_TOKEN>''' - This is SKILL_TOKEN for the reaction.

[[Category:Modding]]

v0.31:Reaction

2010-04-30T12:22:24Z

Oddtwang of Dork: Redirected page to DF2010:Reactions

#REDIRECT [[DF2010:Reactions]]

40d Talk:Loosing

2010-04-30T12:11:38Z

Oddtwang of Dork:

Yeah, normal prose style fits better than sounding like the OED. Should we go completely overboard and give pronunciation advice too? [[User:Anydwarf|Anydwarf]] 14:30, 2 June 2008 (EDT)

:If you'd like to. This is a silly page - do with it what you will! Except, don't make it serious. --[[User:Savok|Savok]] 17:11, 2 June 2008 (EDT)

== -_- ==

Just because I made one mistake... --[[User:Peewee]], unsigned

:You aren't the only one. --[[User:Savok|Savok]] 22:53, 10 June 2008 (EDT)

== Delete? ==

People still make this mistake. I don't see anything wrong with trying to show people Exactly how they're wrong, rather than just a simple redirect, which they may never notice that could cause them to still think it's spelled loosing, and in some cases go through and replace an entire articles use of the word lose with the word loose. [[User:Shardok|Shardok]] 20:45, 24 August 2009 (UTC)

-Don't delete it its hilarious! A perfect D for Dwarf. [[User:Elliott Thinas|Elliott Thinas]] 03:33, 25 August 2009 (UTC)

:I dont mind if it stays either --[[User:Koltom|Koltom]] 14:26, 25 August 2009 (UTC)
::+1 for keeping! Teh only peeple who will find it argh tho'se who knead too. Do'nt delete it, you loosers.--[[User:Albedo|Albedo]] 16:15, 25 August 2009 (UTC)

:::All right all right! I give in! (I do like how a lot of the unpopular changes I've made lately have resulted in better pages anyway. LMAO @ Albedo's comment on the main page) [[User:3lB33|3lB33]] 19:04, 25 August 2009 (UTC)

This page made my day. You guys should do effect/affect next. --[[User:HebaruSan|HebaruSan]] 21:37, 31 October 2009 (UTC)
:Oh Armok no! There way too many esoteric meanings to keep the page stable and it isn't pertinent to DF anyway.
::I agree with the latter poster; seems like an unnecessary page. Besides, who's so stupid as to confuse "losing" with "loosing"? If that elicits a, "Hey!" then go and finish up middle school before posting on here. ;P --[[Special:Contributions/76.110.216.178|76.110.216.178]] 03:34, 28 April 2010 (UTC)
:::Wow, that's nice. "Welcome to the internet, everyone's a douche!" Also confuses ignorance with stupidity and assumes everyone speaks English fluently/natively. [[User:Oddtwang of Dork|Oddtwang of Dork]] 12:11, 30 April 2010 (UTC)

v0.31 Talk:Screw pump

2010-04-28T22:00:49Z

Oddtwang of Dork:

Note: Pumps will transfer power vertically as they did in 40d. It is confirmed they function in all respects as they did in the previous version. For information on vertical power transfer see Pump Stack in the article.
:Moved this to here from the article. [[User:Oddtwang of Dork|Oddtwang of Dork]] 22:00, 28 April 2010 (UTC)

About the service area in the picture. You can use a door at the impassible part of the screw pump instead of using two doors. The dwarves can dig and move diagonally. --[[User:Altaree|Altaree]] 15:38, 13 April 2010 (UTC)

<blockquote>
it can be ... operated by ... using gear assemblies connected to water wheels and/or windmills.
</blockquote>
A gear assembly is not necessary. It is possible to build a water wheel, connected to a horizontal axle, connected to a screw pump. The screw pump will function as intended.

== Pump Speed ==

How much water do screw pumps move? Is it 1/7 of water per game frame? If you wanted to build a 1x1 waterfall that operated constantly without sourcing any new water, how many pump stacks would you need?

:A lot. I don't know. Less than one, so to speak ;) In any case, channel the water through a diagonal after the pump --[[Special:Contributions/92.202.29.45|92.202.29.45]] 17:16, 22 April 2010 (UTC)

:I believe they move 7/7 per step. Make sure your drainage is good :) [[Special:Contributions/66.30.8.88|66.30.8.88]] 21:27, 26 April 2010 (UTC)

== Magma-Safe Pump ==

How is it possible to make a magma-safe pump (or rather, one which does not degrade into its component parts), since pipe sections and corkscrews can (apparently) only be made of wood? [[User:Rodya mirov|Rodya mirov]]
* Nevermind, pipe sections and corkscrews can be made of metal, just not rock. Leaving this here in case anyone else has a similar concern. [[User:Rodya mirov|Rodya mirov]]

v0.31:Screw pump

2010-04-28T21:59:49Z

Oddtwang of Dork: Moved "they work like in 40d" to talk page

{{av}}
{{fine}}

{{Machine_component|name=Screw pump|key=s|job=[[40d:Pump operator|Pump operator]]
|construction=
* {{L|Trap component#Enormous corkscrew|Enormous corkscrew}}
* {{L|Pipe section}}
* {{L|Block}}
|construction_job=
* {{L|Architecture}}
* 1 of
** {{L|Carpentry}}
** {{L|Masonry}}
** {{L|Metalsmithing}}
|power=Needs 10 power.
}}

A '''screw pump''' is a small {{L|building}} that can lift liquids ({{L|water}} or {{L|magma}}) from one level below onto the same {{L|Z-level}} as the pump. It is two tiles by one tile in size, and it can be either manually operated by a {{L|dwarf}} with the {{L|pump operator}} job or by being {{L|power}}ed by {{L|water wheel}}s and/or {{L|windmill}}s.

The direction you want the fluid to travel must be chosen at the time of construction. Pumping only occurs in a straight line, and involves a total of 4 tiles in a row - the liquid source, two for the pump, and the output. The "rise" in levels occurs on the first tile, the intake side, from one level below up to the level of the pump*. Pumped fluids can and will flow immediately after being pumped, as normal for that fluid. Pumped fluids will have a {{L|pressure}} equal to the exit {{L|z-level}} - a pump never "forces" water to a higher {{L|z-level}} than the output tile.

:''(* A DF pump can best be imagined as a simple [http://en.wikipedia.org/wiki/Archimedes%27_screw archimedes screw].)''

Salt water pumped through a pump will become drinkable if then kept separate from natural walls, natural floors, other salt water or an aquifer.{{verify}}

''For a basic overview of how the different machine parts work and work together, see {{L|machinery}}.''

== Construction ==

Building a screw pump requires an {{L|Trap component#Enormous corkscrew|enormous corkscrew}}, a {{L|block}}, and a {{L|pipe section}}. The construction itself is completed in two stages. First a dwarf with the {{L|architect}} labor must design it. Then a dwarf (the same or a different one) with the appropriate labor must complete the building. This could be {{L|carpentry}}, {{L|metalsmithing}}, or {{L|masonry}}, depending on the material of the block.

It's important to choose the proper orientation for your pump, where it will draw water from and where it will deliver the water. This is determined before placement with the {{k|u}}, {{k|k}}, {{k|m}}, or {{k|h}} keys, and the text at the top of the sub-menu will change to confirm your choice. The default (as shown above in the sidebar), "pumps from the north" (top). The ''light'' green X must be next to the liquid source and the ''dark'' green X is where the liquid exits the pump. [[Image:Small pump.jpg|thumb|right|300px|'''Basic Side View of a Pump'''. This pump "pumps from the west", from left to right. The area to the right may fill to the top of that level, but no more (See {{L|pressure}}; see {{L|Screw pump#Pump Stack|Pump stack}}). Note that the entire space required is 4 tiles long by 1 tile wide, not including any retaining walls for the outflow. If pumped manually, the {{L|pump operator}} stands in the light-colored area, as the dark-colored is impassable to both fluid and movement. 
''(Although the "liquid" is shown as blue, this can work for {{L|magma|magma}} as well, with the {{L|magma-safe|appropriate precautions}}.)'']]
 
:{|style="font-family: monospace; font-weight: bold; font-size: 135%; border: 1px solid #0b0; background: #dfd"
|-
|style="color: #0f0; padding: 0"|X||style="color: #070; padding: 0"|X
|}
This example "pumps from the west" (left) to the east (right), the {{k|h}} option. If pumped manually, the dwarf stands on the light-colored tile, as the dark-colored is impassable.

The orientation is visible after placement by using {{k|q}}uery over or near that pump or during placement, using UMKH to select the direction of input. Orientation of a pump cannot be changed after being constructed, but, as with any building, it can be deconstructed into its component parts and rebuilt as and where desired.

Having specified the direction of travel, you must ensure that the source side of the pump is placed adjacent to and above (in the {{L|z-axis}}) a liquid. The screw pump will draw the liquid up from below its level, and distribute it out of the other side of the pump.

== Notes ==

* The source of the pump must be directionally adjacent to "Open Space" that is directly above a source of liquid. The adjacent space cannot be a floor, stairway or wall suspended over water. Screw pumps can pull water through a {{L|grate}}, floor {{L|bars}}, or a {{L|construction|constructed}} {{L|fortification}} on the Z-level below.
* The light pump tile is where a pump operator will stand (if the pump is not powered mechanically). Liquids to be pumped must be 1 level below the (empty) area adjacent to this tile.
* Dwarves must be able to access and stand on the light tile of the pump in order to build the pump and then to be able to operate the pump manually.
* The dark pump tile is on the output side. Liquids will appear in the tile adjacent to this.
* The dark pump tile blocks liquids flow and creature movement, and can be built into a wall to create a solid barrier. The light tile of the pump does not block flow or movement.
* Pumps can also be used in conjunction with a {{L|water wheel}} or a {{L|windmill}} to become self-powered.
* Active mechanisms connected to the pump will automatically start the pump; to prevent this either restrict liquid flow using floodgates or hatches, or put in a {{L|gear assembly}} linked to a {{L|lever}} to disconnect the {{L|power}}.
* Adjacent pumps ''automatically'' transfer mechanical power to any other adjacent pump(s), no {{L|axle}} or {{L|mechanism}} is required. If too many pumps are adjacent, there may be insufficient power to power them.
* A hatch above the input tile (on the same level as the pump) that is linked to a trigger (a {{L|lever}} or {{L|pressure plate}}) makes an effective on/off switch for that pump.
* In order to build pumps in a "hanging" state, as in the stacked screw pump example (below), one of its tiles must be able to connect to a nearby machine, either already existing or designated to be built. If, when the screw pump's construction is completed, the supporting mechanism has not yet been completed, it will promptly collapse into its component parts.
* Pumps do '''not''' push liquids '''up''' additional Z-levels above them. They only deliver water to their own level. That is, if you direct the output of a screw pump into a 1-square space surrounded by walls, the water will not "overflow" the walls. Consequently, a pump will refuse to move liquid if the level it is pumping to is completely filled. Higher levels can be achieved using a "pump stack" (below). (See {{L|Pressure}})
* In order to safely pump magma, you do not need to build a pump out of {{L|magma-safe}} materials, unless the open tile is going to be submerged in magma.{{verify}}
** Exception: Wooden parts {{L|wear}} out fairly quickly when used to pump magma, eventually causing the pump to break down into the non-wooden parts. This is due to the magma heating the adjacent tiles to a temperature at which wood takes heat damage.{{verify}}
* Magma, which normally has no pressure, will behave like pressurized when pumped. For example, when pumped into an U-turn, magma will come out at the other end. Normal (non-pumped) magma would just pool at the lowest level. This may be either very useful (can be used to build pressure towers for magma) or deadly (forge level flooded with magma, because someone tried to pump magma into a volcano).
* Pump's pseudo-pressure doesn't work across diagonals. If there is a diagonal-only passage in your tunnel, liquids will seep slowly through it, instead of bursting through above their normal maximal speed, like they would if there was good passage.

====Common mistakes====
* Orienting a pump incorrectly, and/or not having a proper open liquid source.
* Pumping water into an area with a path to other parts of your fortress. (The pump may work perfectly - the fortress quickly [[40d:flood|flood]]s.)
* Expecting water to rise up above the same level of a pump.
* Building a wall attached only to the light tile - this leaves a diagonal leak between the wall and the dark tile unless sealed there. (If that's not a problem, don't worry about it.)
* Having stairs as input tile. Stairs block input tile, thus rendering the pump useless, even though liquids usually ignore stairs. Output tile can be any liquid-passable tile.

== Example layouts ==
=== Single Pump ===

[[Image:jt_screwpump.png|frame|left|A screw pump delivers from the level below to the tile in front. This pump pumps from the right to the left. The "dark tile" would be on the left - that entire tile is impassible to movement and fluids.]] 
=== Pump Stack ===
[[File:PumpStack2010.png|thumb|right|300px|'''Illustrated Side View of a Pump Stack'''.]]
[[File:PumpStackTopView.png|thumb|right|300px|'''Illustrated Top View of a Pump Stack Layer'''.]]
A Pump Stack is a method used to draw water or magma vertically across multiple z-levels requiring a minimum of parts. The basic functionality is possible because the Output (dark) side of the pump can be built over open space with a machine component located directly below, in this case another Screw Pump. Note that for power to properly transfer the intake (light) side of the pump must line up with the output (dark) side of the pump on the floor above it through a space in the floor, as in the illustration.

A pump stack minimizes the amount of machinery required to lift water or magma by allowing for power to be supplied directly to only the most accessible pump (typically the topmost) which in turn allows the player to operate a stack limited only by how many windmills/water wheels they can fit into the area.

Typical applications for a pump stack include moving magma from a lower level up to a convenient level for forges and furnaces, extracting water from a flooded fort, raising water for a decorative waterfall (and extracting it afterwards), or any other purpose that requires water/magma on a z-level significantly above its current location.

The Illustrated Top View of a Pump Stack Layer shows a basic section of a pump stack. Only the door (or a floodgate) on the Containment side is strictly necessary in order to prevent flooding. Two doorways are used here, each lining up with the solid ground within the pump assembly, in order to prevent workers from trapping themselves after digging channels or assembling the pump.

{{buildings}}

v0.31:Flour

2010-04-28T19:37:01Z

Oddtwang of Dork:

v0.31:Flour

2010-04-28T19:36:48Z

Oddtwang of Dork:

{{av}}{stub}}

40d:Smoke

2010-04-28T19:34:31Z

Oddtwang of Dork:

{{av}}
Where there's '''smoke''', there's {{L|fire}}.

When items burn, they release smoke into the surrounding area. The presence of smoke means that it is reasonably close to a source of fire, which can cause {{L|Losing|fun}} times. If you see smoke, you have (or very recently had) a fire burning somewhere nearby and should take action. ''(Since fire is deadly and can easily spread, this is bad enough by itself.)''

{{L|Dwarves}} that inhale smoke will get unhappy {{L|thoughts}}. They also may get internal injuries or become {{L|unconscious}}.

Smoke will not go through closed doors, but it is apparently thick enough to hold doors open if it gets through. Like {{L|miasma}}, smoke can easily cross {{L|z-level}}s up or down through openings.

{{Category|Fortress mode}}
{{Category|Thoughts}}

v0.31:Melting

2010-04-27T21:53:29Z

Oddtwang of Dork: Redirected page to DF2010:Melt item

#REDIRECT [[DF2010:Melt item]]

Medical status

2010-04-27T09:46:45Z

Oddtwang of Dork:

#REDIRECT: [[cv:Medical status]]

23a:Cavern map

2010-04-27T09:45:43Z

Oddtwang of Dork:

{{av}}

{{stub}} 

''If you're looking for information on Caverns in the current version of the game, please click [[cv:Cavern|here]].''

This article is a rough guide to what you can expect to find as you dig into the mountain. Every mountain in Dwarf Mode has the same internal geological features stretching from the top edge of the map to the bottom in a narrow band, found in the same sequence. From west to east, they are: the underground river, the chasm, the magma flow, the glowing pits, and adamantine. The first three features (river, chasm, and magma) zigzag back and forth quite a bit, so the gems and ores listed may occasionally be found slightly on the near side of the corresponding feature. For instance, you may find a vein of hematite extending just a little bit west of the chasm.

Additionally, when mining gems, you will occasionally get a message that "a miner has found some <gem> mixed in with <some other gem>". This can happen anywhere in the cave and will always produce a gem (of the same color) one level rarer than the type displayed in the cluster. For instance, rose quartz (red) may have red spinel mixed in with it, red spinel may have ruby, or ruby may have red diamond. As always, the Random Number Generator is both your enemy and your friend.

Usually one kind of enemy humanoid will be predominant at each geological feature. For instance, if you encounter antmen at the chasm, you will not see many, if any, ratmen or batmen. However, you may still encounter any of the nonhumanoid enemies.

==Initial rock==

The "initial rock" is the part of the mountain that stretches from the mountain face to the cave river.

New gems

* Turquoise
* Rock crystal
* Rose quartz
* Aventurine

New ore

* Sphalerite (zinc ore; half of brass)
* Cassiterite (tin ore; half of bronze)
* Malachite (copper ore; half of bronze; half of brass)
* Galena (silver ore)

==Cave river==

This river is between 5 and 8 spaces wide, and twists and turns between roughly 48 spaces from the cliff face to about 103 spaces from the cliff face. It is surrounded by limestone 1-2 squares deep on both banks. "Offshoots" of the river will contain either waterfalls or small chasms. These offshoots will stay inside the range of the river, that is, offshoots would appear on the left side only when the river bends far to the right.

Waterfalls and sinks

Waterfalls appear at the ends of "offshoots" that flow downstream into river (i.e. offshoots that point north). In their center, they produce a "fine mist" which causes a happy thought for each dwarf that comes into contact with it.

Sinks appear at the ends of "offshoots" that receive a downstream flow of water from a river (i.e. offshoots that point south ). They are surrounded by a few chasm tiles. A dwarf that falls in the water at the end of one of these channels will immediately die, with the message "Fell down a deep chasm."

Enemies

* {{L|Frogman|Frogmen}}
* {{L|Lizardman|Lizardmen}}
* {{L|Snakeman|Snakemen}}
* {{L|Cave crocodile}}s
* {{L|Giant toad}}s
* {{L|Mud man|Mud men}}

Directly interacting with the river (drinking, fishing, etc.) will trigger subsequent attacks from its denizens. Using wells built anywhere inside the mountain can also trigger attacks, which will sometimes cause enemies to emerge from the wells themselves.

==After the river==

New gems

* Aquamarine
* Red spinel
* Chrysoberyl
* Opal

==Chasm==

This obstacle is between 3 and 5 spaces wide, and angles between 148 to 200 spaces from the cliff face. The chasm tends to make sharper turns than the river, and its offshoots are always straight and between 1 and 2 spaces wide.

Enemies

* {{L|Gremlin}}s
* {{L|Ratman|Ratmen}}
* {{L|Batman|Batmen}}
* {{L|Antman|Antmen}}
* {{L|Troll}}s
* {{L|Giant bat}}s
* {{L|Giant rat}}s
* {{L|Large rat}}s
* {{L|Naked mole dog}}s
* {{L|Troglodyte}}s 
* {{L|Giant mole}}s
* {{L|Giant cave spider}}s
* {{L|Iron man|Iron men}}

Chasming refuse will trigger attacks from chasm-based creatures. This can result in an extended series of attacks as creatures emerge, kill or get killed, and leave remains behind which get thrown into the chasm, triggering more attacks. Flooding the chasm with magma will increase attacks for a short time, then attacks will stop as the bottom of the chasm fills with magma (the center of the chasm turns red). Flooding the chasm with water may reduce attacks, but will never eliminate them.

Attacks from trolls are very rare, but can be dangerous. Trolls are strong and are capable of destroying buildings (including doors and floodgates). Gremlins can throw levers, which can lead to all sorts of havoc, so hide your levers behind a door and a trap or two. But be warned, Gremlins themselves do not set off traps.

==After the chasm==

New gems
* Diamond
* Emerald
* Ruby
* Sapphire

The following rare gems can only be found when mixed in with the above gems:
* Clear diamond
* Red diamond
* Green diamond
* Blue diamond
* Star sapphire
* Star ruby

New ore

* Gold Nuggets
* Platinum Nuggets
* Hematite (iron ore)
* Bituminous Coal (technically not an ore but with many related properties)

==Magma flow==

This obstacle is between roughly 240 and 310 spaces from the cliff face, and is between 7 and 11 spaces wide. Only steel or adamantium may be used to create any bridges or aqueducts that cross it, though there is an exploit where only the topmost material selected to build a structure determines its material. The magma river is surrounded by obsidian 1-2 squares deep on both banks.

Enemies

* {{L|Fire imp}}s
* {{L|Fire man|Fire men}}
* {{L|Magma man|Magma men}}

==The Pits==

Digging past the magma is extremely dangerous. From about 330 to 360 spaces from the cliff face, 1x3 pits are randomly scattered. These pits are usually arranged such that it is impossible to completely avoid them when trying to dig past them (unless you're psychic). Demons emerge from pits not long after they are unearthed, so keep your military ready.

Enemies

* {{L|Frog demon}}s
* {{L|Spirit of fire|Spirits of fire}}
* {{L|Tentacle demon}}s

Approximately a half-dozen demons will show up shortly after you first reach the pits, and not all at once. They are tougher than anything else you are likely to have encountered before this point, and can easily wipe out an entire fortress that is not thoroughly prepared for their arrival. They are wholly immune to traps, magma and steam. Frog demons can breathe underwater, but the others can't.

Beyond the pits is one of the game's greatest rewards: adamantine.

==Adamantine==

The final part of the cave is a layer of adamantine in front of a cave system that you cannot go past (because the game simply won't scroll that far). The chasm occasionally sends a 1x10 cut to the left that is surrounded by adamantine. The adamantine is 1-2 squares thick on the edge of this chasm, much like limestone lines the edge of the cave river. Once you start mining adamantine, the game will check each season and use your total adamantine mined so far as a percentage chance to doom your fortress. When this happens, a one-season timer will start, and then the game will end with a screen describing how you have dug too deep, and released a demon. There is no safe level of adamantine to mine: Once you have mined any, your game will end eventually. You can find (and kill, if you're fast, lucky, and smart) this demon in Your Fortress In Adventure Mode if you find your old fortress again.

Military guide

2010-04-27T09:42:47Z

Oddtwang of Dork:

#REDIRECT: [[cv:Military]]

Dwarf Fortress Wiki talk:Article Consolidation

2010-04-27T09:35:03Z

Oddtwang of Dork: /* How about summary and individual pages? */

== From [[Dwarf Fortress Wiki talk:Centralized Discussion|DFW:Centralized Discussion]] ==
:Will any articles be pruned away or merged? In the jump from 40D to v31 a lot of articles that used to be served well by tables seem to have become their own articles, which really clutters the place up and scatters information all over unfindably. Stones, ores, and gems are the most obvious, they really only need three tables instead of hundreds of articles. --[[User:Corona688|Corona688]] 19:53, 23 April 2010 (UTC)
::Gems are definitely going to have to be consolidated into their own article. Ores and other valuable stones have too much relevant information to stuff in a table, although the worthless stuff like microcline or slate should definitely be relegated to Table Land (presumably we'd have a Stones page, with extra pages for stuff like obsidian or hematite). I think following the example of articles from 40d is a good idea. -- 114.77.43.223
:::What is there to know about Hematite except what it makes and where it's found? What makes it so useful is the metal, which is better described in the Iron page. Seems perfect for a table to me, alongside the myriad other ores that get mined and smelted exactly the same way. Obsidian on the other hand has a fairly unique property that wouldn't be well-described in the valuable stones table alone. --[[Special:Contributions/71.17.242.69|71.17.242.69]] 06:28, 24 April 2010 (UTC)
I agree that ores/stones/gems should be in combined articles. I think I could work on something like this today. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 16:26, 24 April 2010 (UTC)
:Minerals having their own pages is fine with me. There's a bit of information that can be included on the odd page as well as values, pictures and a wikipedia link. Time is better spent elsewhere. One area that could use some looking into is which material is best for each weapon on the weapons article. It currently doesn't have any information on this at all. [[User:Richards|Richards]] 16:40, 24 April 2010 (UTC)
::What are minerals? *SCNR* --[[User:Birthright|Birthright]] 19:43, 24 April 2010 (UTC)
::The "best material" thing is likely to be in flux for some time until Toady gets the damage calculations and so on working. Eventually I'd expect to see something like this in the weapon articles though, naturally. [[User:Oddtwang of Dork|Oddtwang of Dork]] 12:31, 26 April 2010 (UTC)

Generally I don't think "stubs" are a bad thing. Fish cleaner, fishery and fish cleaning may be put in one article+2 redirects, but there are other topics where there is not much to say, and that's just fine, too. With barely 1000 articles it is also rather silly to talk of clutter. How does Wikipedia manage then? Making ''additional'' guides and summarizations is of course useful (and linking to them).
::Stubs that stay stubs are a bad thing. They bury searches in useless results. Wikipedia does not have the problem of filling in hundreds of EMPTY articles following a premade structure that may no longer be relevant or even sensible. And if they're staying stubs, really, they don't deserve a page. --[[Special:Contributions/71.17.241.117|71.17.241.117]] 01:09, 25 April 2010 (UTC)
:::Er, that was me. --[[User:Corona688|Corona688]] 01:11, 25 April 2010 (UTC)

I am not sure why microcline should have it's own article..actually, it should. What I - and a lot of players? - like to do is dig down, find a new stone, look it up. Not just if it's valuable, but also in what layers it appears and if its worth to dig through it into the base layer that may contain interesting or specific stuff. So even when i see that microcline really is everywhere i may decide to not dig on there when I'm looking for, say, platinum. In any case I didn't like the way the table for "generic" stone was organized in the 40d space. As for gems I think we should have both. An article for every gem so i can just check it's value when I find it (before I mine it) without needing the browser search function to find it in a pages-long table, but a table too so we have a central place where one can compare gems with each other. --[[User:Birthright|Birthright]] 19:43, 24 April 2010 (UTC)
:A table would accomplish all that a lot better than an eternally empty stub or a fancy illustration of microcline would. Why couldn't it have a column for value? --[[User:Corona688|Corona688]] 01:11, 25 April 2010 (UTC)
::I'd also add that when you did a search for, say, Diamond, it would bring you to /whatever/page#Diamond but for some reason not forward you to Diamond in the page. That could probably be fixed, so the search would work for you too. --[[Special:Contributions/71.17.241.117|71.17.241.117]] 03:30, 25 April 2010 (UTC)
:::That'll be because there's no heading "Diamond" on the Gem page, so the #Diamond part of the URL is effectively discarded. It'd be great if it could jump you to the right part of the table (i.e. where you end up when you hit Ctrl-F and type it in again) but I suspect that's a non-trivial job. [[User:Oddtwang of Dork|Oddtwang of Dork]] 12:31, 26 April 2010 (UTC)
::Are we clear on the definition of the word 'stub' here? If all there is to say about, say, granite is captured by the table (it's a low-value layer stone, these are its melting & boiling points, whatever) then does the fact that there isn't much text to go with it actually matter? The pictures from Commons and real-world info are nice (and don't fit into a table, though links to WP do of course) but they don't add game value to the article.
::I think I just convinced myself I ike having both pages and tables. [[User:Oddtwang of Dork|Oddtwang of Dork]] 12:31, 26 April 2010 (UTC)

By all means, create your giant tables and combined articles. Nobody will be against more useful content. However, please don't destroy the already existing stone and gem pages. If you really want them gone, we can discuss it ''after'' you've made a suitable replacement. [[User:VengefulDonut|VengefulDonut]] 04:42, 25 April 2010 (UTC)
: Well of course we'd want to replace them with a more useful resource before we remove them, and I also see the potential value in having specific pages, and also table pages. So I might start working on that [[DF2010:Ore]] / [[DF2010:Gems]] / [[DF2010:Stone]] [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 13:33, 25 April 2010 (UTC)

Lumping everything into a table just means more work for a new player to find the information they are looking for. Sure, it seems obvious to anyone that's played for more than a day that microcline is pretty but worthless, but new players shouldn't be forced to scroll through potentially confusing tables to find what they want. But big tables DO have value players both new and old, so having BOTH mega-tables and individual pages is the best solution, in my opinion. The individual pages should however have very clear links to the main stone/gem/ore/etc. pages, plus any information that may be unique to that object. Don't make it hard on newcomers just to "tidy things up" or whatever. A wiki is about getting the relevant information to the user, and if the user wants to know about microcline, it should be as simple as typing it into the box. (on an unrelated note, I apparently don't understand talk pages? why isn't mine signed like everyone elses?)
:I don't see how having the individual pages forwarding to these, quiet small really, tables would make it harder to find information. If anything it would be easier to find similar types of that item or other things in the same layer. The signature is done if you type ~ ~ ~ ~ without the spaces and is generally prefixed with a -- like so --[[User:Shades|Shades]] 14:58, 26 April 2010 (UTC)
::You really think this [[40d:Stone]] is a good way of presenting information, especially to new players? Particularly if they just struck, um, orthoclase? Well obviously you do, and other editors too. Well, I don't. [[40d:The Non-Dwarf's Guide to Rock]] is better, but still far from clearly laid out, complete and easily digested. This is not the editors fault, it's just too much info for a table (so either info is missing or it's bloated). (I ''do'' think, though, that both articles are a valuable ''addition'' to the wiki) If I enter orthoclase, I want info on orthoclase. I don't want to read 4 pages and then find orthoclase on the 5th, if I'm patient and lucky, and ''then'' learn less than from an "empty" "stub" like [[40d:Kimberlite]]. Lets make this wiki usable for all players? --[[User:Old Ancient|Old Ancient]] 15:23, 26 April 2010 (UTC)
:::2 more things:

:::1) stubs: A WP stub is an article that does not contain ''enough'' info or might not even merit an article at all. This does not apply here. The possible lemmata are very limited and this will always be a really small wiki. A lemma is relevant if it is a game term. If there is not much to say about it, then the player has already gained enough from knowing ''that''. Short articles are '''good''' if they are complete.
:::2) "clutter": Only auditors[http://en.wikipedia.org/wiki/Auditors_of_Reality] even perceive that. Not users. We have all the (name-)space in the world. I can imagine topics where info can be too fragmented if an overview article is missing, but have a look at how it's not trivial to even make clear what the [[40d:Restraint]] article is actually about; chains, ropes and restraints (AKA "Huh, why have i been redirected here??"). --[[User:Old Ancient|Old Ancient]] 15:45, 26 April 2010 (UTC)
::::Right now, when the wiki's just an empty skeleton, users can perceive the clutter quite clearly. And the bigger the skeleton, the more work there is to do. Pages can always be split out later if need be, but consolidation needs to happen now if ever. --[[User:Corona688|Corona688]] 06:49, 27 April 2010 (UTC)

== How about summary and individual pages? ==

So it seems like we have a lot of points about the value of individual pages, as well as the value of "combined" pages. How about then we take each article that would apply to: [[DF2010:Ore]] / [[DF2010:Gems]] / [[DF2010:Stone]] and put a single line at the top saying something to the effect of:
:''To view details on all <ore/gem/stones> see here''.
I think this gives value to users who want to look up a specific item, and also to users who want to see similar items. Thoughts? [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 16:26, 26 April 2010 (UTC)
:That seems to be the way many people, myself included, are leaning. --[[User:Oddtwang of Dork|Oddtwang of Dork]] 17:28, 26 April 2010 (UTC)
:Though should 'Gems' not be singular for consistency? --[[User:Oddtwang of Dork|Oddtwang of Dork]] 17:29, 26 April 2010 (UTC)
::I think this would be the way to go. --[[User:Briess|Briess]] 20:40, 26 April 2010 (UTC)
::Details details ;). Yes, it should. Let's wait for some more comments on this. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 01:15, 27 April 2010 (UTC)
:I'm not sold on the value of individual pages. Particularly when most of them aren't and won't ever be filled with anything but raws info, except the ones people have helpfully added spiffy pictures to. Most of the arguments '''against''' tables here are arguments against ugly table arrangements, not tables in general. If we put them in a table -- a '''good table''' with relevant information as one mineral per row, properly fast-forwarded to by the search -- it will be every bit as relevant and informative as the individual article without the search spam. Having both essentially doubles the work and threatens to make the articles go out of sync with each other. --[[User:Corona688|Corona688]] 06:43, 27 April 2010 (UTC)
::Hard to get them out of sync if the data's pulled from the raws, I'd say. As far as I can see from the stone lookup template the raws in question are being stored somewhere centrally anyhow, so they should always be equal. -- [[User:Oddtwang of Dork|Oddtwang of Dork]] 09:35, 27 April 2010 (UTC)

Dwarf Fortress Wiki talk:Article Consolidation

2010-04-26T17:29:40Z

Oddtwang of Dork: /* How about summary and individual pages? */

== From [[Dwarf Fortress Wiki talk:Centralized Discussion|DFW:Centralized Discussion]] ==
:Will any articles be pruned away or merged? In the jump from 40D to v31 a lot of articles that used to be served well by tables seem to have become their own articles, which really clutters the place up and scatters information all over unfindably. Stones, ores, and gems are the most obvious, they really only need three tables instead of hundreds of articles. --[[User:Corona688|Corona688]] 19:53, 23 April 2010 (UTC)
::Gems are definitely going to have to be consolidated into their own article. Ores and other valuable stones have too much relevant information to stuff in a table, although the worthless stuff like microcline or slate should definitely be relegated to Table Land (presumably we'd have a Stones page, with extra pages for stuff like obsidian or hematite). I think following the example of articles from 40d is a good idea. -- 114.77.43.223
:::What is there to know about Hematite except what it makes and where it's found? What makes it so useful is the metal, which is better described in the Iron page. Seems perfect for a table to me, alongside the myriad other ores that get mined and smelted exactly the same way. Obsidian on the other hand has a fairly unique property that wouldn't be well-described in the valuable stones table alone. --[[Special:Contributions/71.17.242.69|71.17.242.69]] 06:28, 24 April 2010 (UTC)
I agree that ores/stones/gems should be in combined articles. I think I could work on something like this today. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 16:26, 24 April 2010 (UTC)
:Minerals having their own pages is fine with me. There's a bit of information that can be included on the odd page as well as values, pictures and a wikipedia link. Time is better spent elsewhere. One area that could use some looking into is which material is best for each weapon on the weapons article. It currently doesn't have any information on this at all. [[User:Richards|Richards]] 16:40, 24 April 2010 (UTC)
::What are minerals? *SCNR* --[[User:Birthright|Birthright]] 19:43, 24 April 2010 (UTC)
::The "best material" thing is likely to be in flux for some time until Toady gets the damage calculations and so on working. Eventually I'd expect to see something like this in the weapon articles though, naturally. [[User:Oddtwang of Dork|Oddtwang of Dork]] 12:31, 26 April 2010 (UTC)

Generally I don't think "stubs" are a bad thing. Fish cleaner, fishery and fish cleaning may be put in one article+2 redirects, but there are other topics where there is not much to say, and that's just fine, too. With barely 1000 articles it is also rather silly to talk of clutter. How does Wikipedia manage then? Making ''additional'' guides and summarizations is of course useful (and linking to them).
::Stubs that stay stubs are a bad thing. They bury searches in useless results. Wikipedia does not have the problem of filling in hundreds of EMPTY articles following a premade structure that may no longer be relevant or even sensible. And if they're staying stubs, really, they don't deserve a page. --[[Special:Contributions/71.17.241.117|71.17.241.117]] 01:09, 25 April 2010 (UTC)
:::Er, that was me. --[[User:Corona688|Corona688]] 01:11, 25 April 2010 (UTC)

I am not sure why microcline should have it's own article..actually, it should. What I - and a lot of players? - like to do is dig down, find a new stone, look it up. Not just if it's valuable, but also in what layers it appears and if its worth to dig through it into the base layer that may contain interesting or specific stuff. So even when i see that microcline really is everywhere i may decide to not dig on there when I'm looking for, say, platinum. In any case I didn't like the way the table for "generic" stone was organized in the 40d space. As for gems I think we should have both. An article for every gem so i can just check it's value when I find it (before I mine it) without needing the browser search function to find it in a pages-long table, but a table too so we have a central place where one can compare gems with each other. --[[User:Birthright|Birthright]] 19:43, 24 April 2010 (UTC)
:A table would accomplish all that a lot better than an eternally empty stub or a fancy illustration of microcline would. Why couldn't it have a column for value? --[[User:Corona688|Corona688]] 01:11, 25 April 2010 (UTC)
::I'd also add that when you did a search for, say, Diamond, it would bring you to /whatever/page#Diamond but for some reason not forward you to Diamond in the page. That could probably be fixed, so the search would work for you too. --[[Special:Contributions/71.17.241.117|71.17.241.117]] 03:30, 25 April 2010 (UTC)
:::That'll be because there's no heading "Diamond" on the Gem page, so the #Diamond part of the URL is effectively discarded. It'd be great if it could jump you to the right part of the table (i.e. where you end up when you hit Ctrl-F and type it in again) but I suspect that's a non-trivial job. [[User:Oddtwang of Dork|Oddtwang of Dork]] 12:31, 26 April 2010 (UTC)
::Are we clear on the definition of the word 'stub' here? If all there is to say about, say, granite is captured by the table (it's a low-value layer stone, these are its melting & boiling points, whatever) then does the fact that there isn't much text to go with it actually matter? The pictures from Commons and real-world info are nice (and don't fit into a table, though links to WP do of course) but they don't add game value to the article.
::I think I just convinced myself I ike having both pages and tables. [[User:Oddtwang of Dork|Oddtwang of Dork]] 12:31, 26 April 2010 (UTC)

By all means, create your giant tables and combined articles. Nobody will be against more useful content. However, please don't destroy the already existing stone and gem pages. If you really want them gone, we can discuss it ''after'' you've made a suitable replacement. [[User:VengefulDonut|VengefulDonut]] 04:42, 25 April 2010 (UTC)
: Well of course we'd want to replace them with a more useful resource before we remove them, and I also see the potential value in having specific pages, and also table pages. So I might start working on that [[DF2010:Ore]] / [[DF2010:Gems]] / [[DF2010:Stone]] [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 13:33, 25 April 2010 (UTC)

Lumping everything into a table just means more work for a new player to find the information they are looking for. Sure, it seems obvious to anyone that's played for more than a day that microcline is pretty but worthless, but new players shouldn't be forced to scroll through potentially confusing tables to find what they want. But big tables DO have value players both new and old, so having BOTH mega-tables and individual pages is the best solution, in my opinion. The individual pages should however have very clear links to the main stone/gem/ore/etc. pages, plus any information that may be unique to that object. Don't make it hard on newcomers just to "tidy things up" or whatever. A wiki is about getting the relevant information to the user, and if the user wants to know about microcline, it should be as simple as typing it into the box. (on an unrelated note, I apparently don't understand talk pages? why isn't mine signed like everyone elses?)
:I don't see how having the individual pages forwarding to these, quiet small really, tables would make it harder to find information. If anything it would be easier to find similar types of that item or other things in the same layer. The signature is done if you type ~ ~ ~ ~ without the spaces and is generally prefixed with a -- like so --[[User:Shades|Shades]] 14:58, 26 April 2010 (UTC)
::You really think this [[40d:Stone]] is a good way of presenting information, especially to new players? Particularly if they just struck, um, orthoclase? Well obviously you do, and other editors too. Well, I don't. [[40d:The Non-Dwarf's Guide to Rock]] is better, but still far from clearly laid out, complete and easily digested. This is not the editors fault, it's just too much info for a table (so either info is missing or it's bloated). (I ''do'' think, though, that both articles are a valuable ''addition'' to the wiki) If I enter orthoclase, I want info on orthoclase. I don't want to read 4 pages and then find orthoclase on the 5th, if I'm patient and lucky, and ''then'' learn less than from an "empty" "stub" like [[40d:Kimberlite]]. Lets make this wiki usable for all players? --[[User:Old Ancient|Old Ancient]] 15:23, 26 April 2010 (UTC)
:::2 more things:

:::1) stubs: A WP stub is an article that does not contain ''enough'' info or might not even merit an article at all. This does not apply here. The possible lemmata are very limited and this will always be a really small wiki. A lemma is relevant if it is a game term. If there is not much to say about it, then the player has already gained enough from knowing ''that''. Short articles are '''good''' if they are complete.
:::2) "clutter": Only auditors[http://en.wikipedia.org/wiki/Auditors_of_Reality] even perceive that. Not users. We have all the (name-)space in the world. I can imagine topics where info can be too fragmented if an overview article is missing, but have a look at how it's not trivial to even make clear what the [[40d:Restraint]] article is actually about; chains, ropes and restraints (AKA "Huh, why have i been redirected here??"). --[[User:Old Ancient|Old Ancient]] 15:45, 26 April 2010 (UTC)

== How about summary and individual pages? ==

So it seems like we have a lot of points about the value of individual pages, as well as the value of "combined" pages. How about then we take each article that would apply to: [[DF2010:Ore]] / [[DF2010:Gems]] / [[DF2010:Stone]] and put a single line at the top saying something to the effect of:
:''To view details on all <ore/gem/stones> see here''.
I think this gives value to users who want to look up a specific item, and also to users who want to see similar items. Thoughts? [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 16:26, 26 April 2010 (UTC)
:That seems to be the way many people, myself included, are leaning. --[[User:Oddtwang of Dork|Oddtwang of Dork]] 17:28, 26 April 2010 (UTC)
:Though should 'Gems' not be singular for consistency? --[[User:Oddtwang of Dork|Oddtwang of Dork]] 17:29, 26 April 2010 (UTC)

Dwarf Fortress Wiki talk:Article Consolidation

2010-04-26T17:28:46Z

Oddtwang of Dork: /* How about summary and individual pages? */

== From [[Dwarf Fortress Wiki talk:Centralized Discussion|DFW:Centralized Discussion]] ==
:Will any articles be pruned away or merged? In the jump from 40D to v31 a lot of articles that used to be served well by tables seem to have become their own articles, which really clutters the place up and scatters information all over unfindably. Stones, ores, and gems are the most obvious, they really only need three tables instead of hundreds of articles. --[[User:Corona688|Corona688]] 19:53, 23 April 2010 (UTC)
::Gems are definitely going to have to be consolidated into their own article. Ores and other valuable stones have too much relevant information to stuff in a table, although the worthless stuff like microcline or slate should definitely be relegated to Table Land (presumably we'd have a Stones page, with extra pages for stuff like obsidian or hematite). I think following the example of articles from 40d is a good idea. -- 114.77.43.223
:::What is there to know about Hematite except what it makes and where it's found? What makes it so useful is the metal, which is better described in the Iron page. Seems perfect for a table to me, alongside the myriad other ores that get mined and smelted exactly the same way. Obsidian on the other hand has a fairly unique property that wouldn't be well-described in the valuable stones table alone. --[[Special:Contributions/71.17.242.69|71.17.242.69]] 06:28, 24 April 2010 (UTC)
I agree that ores/stones/gems should be in combined articles. I think I could work on something like this today. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 16:26, 24 April 2010 (UTC)
:Minerals having their own pages is fine with me. There's a bit of information that can be included on the odd page as well as values, pictures and a wikipedia link. Time is better spent elsewhere. One area that could use some looking into is which material is best for each weapon on the weapons article. It currently doesn't have any information on this at all. [[User:Richards|Richards]] 16:40, 24 April 2010 (UTC)
::What are minerals? *SCNR* --[[User:Birthright|Birthright]] 19:43, 24 April 2010 (UTC)
::The "best material" thing is likely to be in flux for some time until Toady gets the damage calculations and so on working. Eventually I'd expect to see something like this in the weapon articles though, naturally. [[User:Oddtwang of Dork|Oddtwang of Dork]] 12:31, 26 April 2010 (UTC)

Generally I don't think "stubs" are a bad thing. Fish cleaner, fishery and fish cleaning may be put in one article+2 redirects, but there are other topics where there is not much to say, and that's just fine, too. With barely 1000 articles it is also rather silly to talk of clutter. How does Wikipedia manage then? Making ''additional'' guides and summarizations is of course useful (and linking to them).
::Stubs that stay stubs are a bad thing. They bury searches in useless results. Wikipedia does not have the problem of filling in hundreds of EMPTY articles following a premade structure that may no longer be relevant or even sensible. And if they're staying stubs, really, they don't deserve a page. --[[Special:Contributions/71.17.241.117|71.17.241.117]] 01:09, 25 April 2010 (UTC)
:::Er, that was me. --[[User:Corona688|Corona688]] 01:11, 25 April 2010 (UTC)

I am not sure why microcline should have it's own article..actually, it should. What I - and a lot of players? - like to do is dig down, find a new stone, look it up. Not just if it's valuable, but also in what layers it appears and if its worth to dig through it into the base layer that may contain interesting or specific stuff. So even when i see that microcline really is everywhere i may decide to not dig on there when I'm looking for, say, platinum. In any case I didn't like the way the table for "generic" stone was organized in the 40d space. As for gems I think we should have both. An article for every gem so i can just check it's value when I find it (before I mine it) without needing the browser search function to find it in a pages-long table, but a table too so we have a central place where one can compare gems with each other. --[[User:Birthright|Birthright]] 19:43, 24 April 2010 (UTC)
:A table would accomplish all that a lot better than an eternally empty stub or a fancy illustration of microcline would. Why couldn't it have a column for value? --[[User:Corona688|Corona688]] 01:11, 25 April 2010 (UTC)
::I'd also add that when you did a search for, say, Diamond, it would bring you to /whatever/page#Diamond but for some reason not forward you to Diamond in the page. That could probably be fixed, so the search would work for you too. --[[Special:Contributions/71.17.241.117|71.17.241.117]] 03:30, 25 April 2010 (UTC)
:::That'll be because there's no heading "Diamond" on the Gem page, so the #Diamond part of the URL is effectively discarded. It'd be great if it could jump you to the right part of the table (i.e. where you end up when you hit Ctrl-F and type it in again) but I suspect that's a non-trivial job. [[User:Oddtwang of Dork|Oddtwang of Dork]] 12:31, 26 April 2010 (UTC)
::Are we clear on the definition of the word 'stub' here? If all there is to say about, say, granite is captured by the table (it's a low-value layer stone, these are its melting & boiling points, whatever) then does the fact that there isn't much text to go with it actually matter? The pictures from Commons and real-world info are nice (and don't fit into a table, though links to WP do of course) but they don't add game value to the article.
::I think I just convinced myself I ike having both pages and tables. [[User:Oddtwang of Dork|Oddtwang of Dork]] 12:31, 26 April 2010 (UTC)

By all means, create your giant tables and combined articles. Nobody will be against more useful content. However, please don't destroy the already existing stone and gem pages. If you really want them gone, we can discuss it ''after'' you've made a suitable replacement. [[User:VengefulDonut|VengefulDonut]] 04:42, 25 April 2010 (UTC)
: Well of course we'd want to replace them with a more useful resource before we remove them, and I also see the potential value in having specific pages, and also table pages. So I might start working on that [[DF2010:Ore]] / [[DF2010:Gems]] / [[DF2010:Stone]] [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 13:33, 25 April 2010 (UTC)

Lumping everything into a table just means more work for a new player to find the information they are looking for. Sure, it seems obvious to anyone that's played for more than a day that microcline is pretty but worthless, but new players shouldn't be forced to scroll through potentially confusing tables to find what they want. But big tables DO have value players both new and old, so having BOTH mega-tables and individual pages is the best solution, in my opinion. The individual pages should however have very clear links to the main stone/gem/ore/etc. pages, plus any information that may be unique to that object. Don't make it hard on newcomers just to "tidy things up" or whatever. A wiki is about getting the relevant information to the user, and if the user wants to know about microcline, it should be as simple as typing it into the box. (on an unrelated note, I apparently don't understand talk pages? why isn't mine signed like everyone elses?)
:I don't see how having the individual pages forwarding to these, quiet small really, tables would make it harder to find information. If anything it would be easier to find similar types of that item or other things in the same layer. The signature is done if you type ~ ~ ~ ~ without the spaces and is generally prefixed with a -- like so --[[User:Shades|Shades]] 14:58, 26 April 2010 (UTC)
::You really think this [[40d:Stone]] is a good way of presenting information, especially to new players? Particularly if they just struck, um, orthoclase? Well obviously you do, and other editors too. Well, I don't. [[40d:The Non-Dwarf's Guide to Rock]] is better, but still far from clearly laid out, complete and easily digested. This is not the editors fault, it's just too much info for a table (so either info is missing or it's bloated). (I ''do'' think, though, that both articles are a valuable ''addition'' to the wiki) If I enter orthoclase, I want info on orthoclase. I don't want to read 4 pages and then find orthoclase on the 5th, if I'm patient and lucky, and ''then'' learn less than from an "empty" "stub" like [[40d:Kimberlite]]. Lets make this wiki usable for all players? --[[User:Old Ancient|Old Ancient]] 15:23, 26 April 2010 (UTC)
:::2 more things:

:::1) stubs: A WP stub is an article that does not contain ''enough'' info or might not even merit an article at all. This does not apply here. The possible lemmata are very limited and this will always be a really small wiki. A lemma is relevant if it is a game term. If there is not much to say about it, then the player has already gained enough from knowing ''that''. Short articles are '''good''' if they are complete.
:::2) "clutter": Only auditors[http://en.wikipedia.org/wiki/Auditors_of_Reality] even perceive that. Not users. We have all the (name-)space in the world. I can imagine topics where info can be too fragmented if an overview article is missing, but have a look at how it's not trivial to even make clear what the [[40d:Restraint]] article is actually about; chains, ropes and restraints (AKA "Huh, why have i been redirected here??"). --[[User:Old Ancient|Old Ancient]] 15:45, 26 April 2010 (UTC)

== How about summary and individual pages? ==

So it seems like we have a lot of points about the value of individual pages, as well as the value of "combined" pages. How about then we take each article that would apply to: [[DF2010:Ore]] / [[DF2010:Gems]] / [[DF2010:Stone]] and put a single line at the top saying something to the effect of:
:''To view details on all <ore/gem/stones> see here''.
I think this gives value to users who want to look up a specific item, and also to users who want to see similar items. Thoughts? [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 16:26, 26 April 2010 (UTC)
:That seems to be the way many people, myself included, are leaning. --[[User:Oddtwang of Dork|Oddtwang of Dork]] 17:28, 26 April 2010 (UTC)

v0.31:Ore

2010-04-26T17:27:53Z

Oddtwang of Dork:

{{av}}{{fine}}
'''Ores''' are a type of {{l|stone}} that can be used to create {{l|bar}}s of pure {{l|metal}}s and {{l|alloy}}s at the {{l|smelter}}. Many ores are quite valuable as mined, and a {{l|mason}} or {{l|stone crafter}} can work them the same as any stone. However, ores fall into the {{l|economic stone}} category, and so must be designated for non-restricted use in the {{l|z-stone}} menu. Others can be combined when initially smelted into alloys, while others must first be made into bars of pure metal and then ''those'' combined to create the desired alloy.

All ores are {{l|fire-safe}} material. Some are also {{l|magma-safe}}.

Note that in some cases ore {{l|value#material value|value}} (given below) and {{l|metal}} value are not the same (Bismuth, Iron ores). Alloys, too, often have a higher value than the ores/metals they are made of. In most cases furniture made from the ore is as valuable as furniture made from a pure (non-alloy) metal, while requiring one-third the raw materials and significantly less processing.

Metal ores with two possible metals listed below always create the first metal when {{l|smelting}}, but have a chance of creating the second metal as well. Different rules apply to creating alloys.

Nearly all unmined ores are represented by the {{Raw Tile|£|#FFF|#000}} symbol. Exceptions are native aluminum, bismuthinite, and magnetite (which appear as {{Raw Tile|^|#FFF|#000}}, {{Raw Tile|%|#FFF|#000}}, and {{Raw Tile|~|#FFF|#000}}, respectively), as well as cinnabar and cobaltite (which appear as {{Raw Tile|£|#FFF|#000}} but cannot be refined into mercury or cobalt as they would be in real life).

{| class="wikitable" cellspacing="0" border="1" cellpadding="5"
|-
! Ore
! Found in
! Metal created
! Value
! Metal value
|-
|{{l|Raw adamantine|Raw Adamantine}} *||The depths||{{l|Adamantine}} *||250||300
|-
|{{l|Native aluminum|Aluminum, native}}||All {{l|Igneous extrusive layer|Igneous Extrusive}}'''(S)'''||{{l|Aluminum}}||40||40
|-
|{{l|Bismuthinite}}||{{l|Granite}}'''(S)'''||{{l|Bismuth}}||1||2
|-
|{{l|Cassiterite}}||All {{l|Alluvial layer|Alluvial}}'''(S)''', {{l|Granite}}'''(V)'''||{{l|Tin}}||2||2
|-
|{{l|Native copper|Copper, native}}||All {{l|Igneous extrusive layer|Igneous Extrusive}}'''(V)''', {{l|Sandstone}}'''(V)'''||{{l|Copper}}||2||2
|-
|{{l|Galena}}||All {{l|Igneous extrusive layer|Igneous extrusive}}'''(V)''', All {{l|Metamorphic layer|Metamorphic}}'''(V)''', {{l|Granite}}'''(V)''', {{l|Limestone}}'''(V)'''||{{l|Lead}}, {{l|Silver|Silver (50%)}}||5||2 (10)
|-
|{{l|Garnierite}}||{{l|Gabbro}}'''(V)'''||{{l|Nickel}}||2||2
|-
|{{l|Native gold|Gold, native}}||All {{l|stone|Igneous}}'''(V)''', All {{l|Alluvial layer|Alluvial}}'''(S)'''||{{l|Gold}}||30||30
|-
|{{l|Hematite}}||All {{l|Sedimentary layer|Sedimentary}}'''(V)''', All {{l|Igneous extrusive layer|Igneous extrusive}}'''(V)'''||{{l|Iron}}||8||10
|-
|{{l|Horn silver}}||{{l|Native silver}}'''(S)'''||{{l|Silver}}||10||10
|-
|{{l|Limonite}}||All {{l|Sedimentary layer|Sedimentary}}'''(V)'''||{{l|Iron}}||8||10
|-
|{{l|Magnetite}}||All {{l|Sedimentary layer|Sedimentary}}'''(L)'''||{{l|Iron}}||8||10
|-
|{{l|Malachite}}||{{l|Limestone}}'''(V)''', {{l|Marble}}'''(V)'''||{{l|Copper}}||2||2
|-
|{{l|Native platinum|Platinum, native}}||All {{l|Alluvial layer|Alluvial}}'''(S)''', {{l|Olivine}}'''(V)''', {{l|Magnetite}}'''(V)''', {{l|Chromite}}'''(S)'''||{{l|Platinum}}||40||40
|-
|{{l|Native silver|Silver, native}}||{{l|Granite}}'''(V)''', {{l|Gneiss}}'''(V)'''||{{l|Silver}}||10||10
|-
|{{l|Sphalerite}}||All {{l|Metamorphic layer|Metamorphic}}'''(V)'''||{{l|Zinc}}||2||2
|-
|{{l|Tetrahedrite}}||All {{l|Stone}}'''(V)'''||{{l|Copper}}, {{l|Silver|Silver (20%)}}||3||2 (10)
|}
:'''(L)''' - occurs in large clusters
:'''(V)''' - occurs in veins
:'''(S)''' - occurs in small clusters
:'''(1)''' - occurs in individual tiles

:''(* Note that {{l|raw adamantine}}/{{l|adamantine}} does not follow all the usual rules for an ore/metal in several respects - see article for full discussion.)''

===See Also:===

:* {{l|Smelting}}
:* {{l|Metal}}s
:* {{l|Vein|Clusters & Veins}}
:* {{l|Exploratory mining}}
:* {{l|The Non-Dwarf's Guide to Rock}}
:* {{l|stone}}
:* {{l|gem}}

[[Category:Ore|*]]
[[Category:Materials]]

v0.31:Ore

2010-04-26T17:27:30Z

Oddtwang of Dork:

{{av}}{human}}
'''Ores''' are a type of {{l|stone}} that can be used to create {{l|bar}}s of pure {{l|metal}}s and {{l|alloy}}s at the {{l|smelter}}. Many ores are quite valuable as mined, and a {{l|mason}} or {{l|stone crafter}} can work them the same as any stone. However, ores fall into the {{l|economic stone}} category, and so must be designated for non-restricted use in the {{l|z-stone}} menu. Others can be combined when initially smelted into alloys, while others must first be made into bars of pure metal and then ''those'' combined to create the desired alloy.

All ores are {{l|fire-safe}} material. Some are also {{l|magma-safe}}.

Note that in some cases ore {{l|value#material value|value}} (given below) and {{l|metal}} value are not the same (Bismuth, Iron ores). Alloys, too, often have a higher value than the ores/metals they are made of. In most cases furniture made from the ore is as valuable as furniture made from a pure (non-alloy) metal, while requiring one-third the raw materials and significantly less processing.

Metal ores with two possible metals listed below always create the first metal when {{l|smelting}}, but have a chance of creating the second metal as well. Different rules apply to creating alloys.

Nearly all unmined ores are represented by the {{Raw Tile|£|#FFF|#000}} symbol. Exceptions are native aluminum, bismuthinite, and magnetite (which appear as {{Raw Tile|^|#FFF|#000}}, {{Raw Tile|%|#FFF|#000}}, and {{Raw Tile|~|#FFF|#000}}, respectively), as well as cinnabar and cobaltite (which appear as {{Raw Tile|£|#FFF|#000}} but cannot be refined into mercury or cobalt as they would be in real life).

{| class="wikitable" cellspacing="0" border="1" cellpadding="5"
|-
! Ore
! Found in
! Metal created
! Value
! Metal value
|-
|{{l|Raw adamantine|Raw Adamantine}} *||The depths||{{l|Adamantine}} *||250||300
|-
|{{l|Native aluminum|Aluminum, native}}||All {{l|Igneous extrusive layer|Igneous Extrusive}}'''(S)'''||{{l|Aluminum}}||40||40
|-
|{{l|Bismuthinite}}||{{l|Granite}}'''(S)'''||{{l|Bismuth}}||1||2
|-
|{{l|Cassiterite}}||All {{l|Alluvial layer|Alluvial}}'''(S)''', {{l|Granite}}'''(V)'''||{{l|Tin}}||2||2
|-
|{{l|Native copper|Copper, native}}||All {{l|Igneous extrusive layer|Igneous Extrusive}}'''(V)''', {{l|Sandstone}}'''(V)'''||{{l|Copper}}||2||2
|-
|{{l|Galena}}||All {{l|Igneous extrusive layer|Igneous extrusive}}'''(V)''', All {{l|Metamorphic layer|Metamorphic}}'''(V)''', {{l|Granite}}'''(V)''', {{l|Limestone}}'''(V)'''||{{l|Lead}}, {{l|Silver|Silver (50%)}}||5||2 (10)
|-
|{{l|Garnierite}}||{{l|Gabbro}}'''(V)'''||{{l|Nickel}}||2||2
|-
|{{l|Native gold|Gold, native}}||All {{l|stone|Igneous}}'''(V)''', All {{l|Alluvial layer|Alluvial}}'''(S)'''||{{l|Gold}}||30||30
|-
|{{l|Hematite}}||All {{l|Sedimentary layer|Sedimentary}}'''(V)''', All {{l|Igneous extrusive layer|Igneous extrusive}}'''(V)'''||{{l|Iron}}||8||10
|-
|{{l|Horn silver}}||{{l|Native silver}}'''(S)'''||{{l|Silver}}||10||10
|-
|{{l|Limonite}}||All {{l|Sedimentary layer|Sedimentary}}'''(V)'''||{{l|Iron}}||8||10
|-
|{{l|Magnetite}}||All {{l|Sedimentary layer|Sedimentary}}'''(L)'''||{{l|Iron}}||8||10
|-
|{{l|Malachite}}||{{l|Limestone}}'''(V)''', {{l|Marble}}'''(V)'''||{{l|Copper}}||2||2
|-
|{{l|Native platinum|Platinum, native}}||All {{l|Alluvial layer|Alluvial}}'''(S)''', {{l|Olivine}}'''(V)''', {{l|Magnetite}}'''(V)''', {{l|Chromite}}'''(S)'''||{{l|Platinum}}||40||40
|-
|{{l|Native silver|Silver, native}}||{{l|Granite}}'''(V)''', {{l|Gneiss}}'''(V)'''||{{l|Silver}}||10||10
|-
|{{l|Sphalerite}}||All {{l|Metamorphic layer|Metamorphic}}'''(V)'''||{{l|Zinc}}||2||2
|-
|{{l|Tetrahedrite}}||All {{l|Stone}}'''(V)'''||{{l|Copper}}, {{l|Silver|Silver (20%)}}||3||2 (10)
|}
:'''(L)''' - occurs in large clusters
:'''(V)''' - occurs in veins
:'''(S)''' - occurs in small clusters
:'''(1)''' - occurs in individual tiles

:''(* Note that {{l|raw adamantine}}/{{l|adamantine}} does not follow all the usual rules for an ore/metal in several respects - see article for full discussion.)''

===See Also:===

:* {{l|Smelting}}
:* {{l|Metal}}s
:* {{l|Vein|Clusters & Veins}}
:* {{l|Exploratory mining}}
:* {{l|The Non-Dwarf's Guide to Rock}}
:* {{l|stone}}
:* {{l|gem}}

[[Category:Ore|*]]
[[Category:Materials]]

v0.31:Ore

2010-04-26T17:27:13Z

Oddtwang of Dork:

{{av}}{fine}}
'''Ores''' are a type of {{l|stone}} that can be used to create {{l|bar}}s of pure {{l|metal}}s and {{l|alloy}}s at the {{l|smelter}}. Many ores are quite valuable as mined, and a {{l|mason}} or {{l|stone crafter}} can work them the same as any stone. However, ores fall into the {{l|economic stone}} category, and so must be designated for non-restricted use in the {{l|z-stone}} menu. Others can be combined when initially smelted into alloys, while others must first be made into bars of pure metal and then ''those'' combined to create the desired alloy.

All ores are {{l|fire-safe}} material. Some are also {{l|magma-safe}}.

Note that in some cases ore {{l|value#material value|value}} (given below) and {{l|metal}} value are not the same (Bismuth, Iron ores). Alloys, too, often have a higher value than the ores/metals they are made of. In most cases furniture made from the ore is as valuable as furniture made from a pure (non-alloy) metal, while requiring one-third the raw materials and significantly less processing.

Metal ores with two possible metals listed below always create the first metal when {{l|smelting}}, but have a chance of creating the second metal as well. Different rules apply to creating alloys.

Nearly all unmined ores are represented by the {{Raw Tile|£|#FFF|#000}} symbol. Exceptions are native aluminum, bismuthinite, and magnetite (which appear as {{Raw Tile|^|#FFF|#000}}, {{Raw Tile|%|#FFF|#000}}, and {{Raw Tile|~|#FFF|#000}}, respectively), as well as cinnabar and cobaltite (which appear as {{Raw Tile|£|#FFF|#000}} but cannot be refined into mercury or cobalt as they would be in real life).

{| class="wikitable" cellspacing="0" border="1" cellpadding="5"
|-
! Ore
! Found in
! Metal created
! Value
! Metal value
|-
|{{l|Raw adamantine|Raw Adamantine}} *||The depths||{{l|Adamantine}} *||250||300
|-
|{{l|Native aluminum|Aluminum, native}}||All {{l|Igneous extrusive layer|Igneous Extrusive}}'''(S)'''||{{l|Aluminum}}||40||40
|-
|{{l|Bismuthinite}}||{{l|Granite}}'''(S)'''||{{l|Bismuth}}||1||2
|-
|{{l|Cassiterite}}||All {{l|Alluvial layer|Alluvial}}'''(S)''', {{l|Granite}}'''(V)'''||{{l|Tin}}||2||2
|-
|{{l|Native copper|Copper, native}}||All {{l|Igneous extrusive layer|Igneous Extrusive}}'''(V)''', {{l|Sandstone}}'''(V)'''||{{l|Copper}}||2||2
|-
|{{l|Galena}}||All {{l|Igneous extrusive layer|Igneous extrusive}}'''(V)''', All {{l|Metamorphic layer|Metamorphic}}'''(V)''', {{l|Granite}}'''(V)''', {{l|Limestone}}'''(V)'''||{{l|Lead}}, {{l|Silver|Silver (50%)}}||5||2 (10)
|-
|{{l|Garnierite}}||{{l|Gabbro}}'''(V)'''||{{l|Nickel}}||2||2
|-
|{{l|Native gold|Gold, native}}||All {{l|stone|Igneous}}'''(V)''', All {{l|Alluvial layer|Alluvial}}'''(S)'''||{{l|Gold}}||30||30
|-
|{{l|Hematite}}||All {{l|Sedimentary layer|Sedimentary}}'''(V)''', All {{l|Igneous extrusive layer|Igneous extrusive}}'''(V)'''||{{l|Iron}}||8||10
|-
|{{l|Horn silver}}||{{l|Native silver}}'''(S)'''||{{l|Silver}}||10||10
|-
|{{l|Limonite}}||All {{l|Sedimentary layer|Sedimentary}}'''(V)'''||{{l|Iron}}||8||10
|-
|{{l|Magnetite}}||All {{l|Sedimentary layer|Sedimentary}}'''(L)'''||{{l|Iron}}||8||10
|-
|{{l|Malachite}}||{{l|Limestone}}'''(V)''', {{l|Marble}}'''(V)'''||{{l|Copper}}||2||2
|-
|{{l|Native platinum|Platinum, native}}||All {{l|Alluvial layer|Alluvial}}'''(S)''', {{l|Olivine}}'''(V)''', {{l|Magnetite}}'''(V)''', {{l|Chromite}}'''(S)'''||{{l|Platinum}}||40||40
|-
|{{l|Native silver|Silver, native}}||{{l|Granite}}'''(V)''', {{l|Gneiss}}'''(V)'''||{{l|Silver}}||10||10
|-
|{{l|Sphalerite}}||All {{l|Metamorphic layer|Metamorphic}}'''(V)'''||{{l|Zinc}}||2||2
|-
|{{l|Tetrahedrite}}||All {{l|Stone}}'''(V)'''||{{l|Copper}}, {{l|Silver|Silver (20%)}}||3||2 (10)
|}
:'''(L)''' - occurs in large clusters
:'''(V)''' - occurs in veins
:'''(S)''' - occurs in small clusters
:'''(1)''' - occurs in individual tiles

:''(* Note that {{l|raw adamantine}}/{{l|adamantine}} does not follow all the usual rules for an ore/metal in several respects - see article for full discussion.)''

===See Also:===

:* {{l|Smelting}}
:* {{l|Metal}}s
:* {{l|Vein|Clusters & Veins}}
:* {{l|Exploratory mining}}
:* {{l|The Non-Dwarf's Guide to Rock}}
:* {{l|stone}}
:* {{l|gem}}

[[Category:Ore|*]]
[[Category:Materials]]

v0.31:Trap component

2010-04-26T12:55:35Z

Oddtwang of Dork: /* Large, serrated disc */

{{av}}{{human}}
Any {{L|weapon}} in Fortress Mode can be placed into a {{L|Trap#Weapon Trap|weapon trap}}. However, there are five '''trap components''', or '''trap weapons''', that are ''specifically'' for weapons traps (and two also have additional uses). As with any weapon, a total of up to 10 of these can be put in a single weapon trap, creating a true "Indiana Jones" type of threat to any beast of any size, and potentially simply making a fine mince (or paste, depending on the weapons) of lesser creatures.
In the order they appear on the various menus, they are the '''menacing spike''', the '''serrated disc''', the '''spiked ball''', the '''enormous corkscrew''', and the '''giant axe blade'''.



All trap component weapons can be made out of {{L|metal}}s (by a {{L|weaponsmith}}) or {{L|glass}} (by a {{L|glassmaker}}), with appropriate damage. Three can also be made out of {{L|wood}} (by a {{L|carpenter}}), as noted below, which can be useful in getting some heavy weapons traps set up before you have a steady {{L|smelting}} operation going, or if you are short on metal.


Trap components are a separate sub-section of a {{L|forge}} menu, but are at the bottom of the general {{L|glass furnace}} or {{L|carpenter's workshop}} menus.

==The 5 trap weapons==
===Menacing spike===

The '''menacing spike''' can be mounted in both traditional {{L|Trap#Weapon_trap|weapon traps}} and {{L|Trap#Upright_Spear/Spike|upright spike traps}}, which act quite differently. Its small contact size and high penetration depth makes it a decent choice against enemies with impale-able internal organs.

Menacing spikes can also be made from {{L|wood}}.

===Large, serrated disc===
'''Large, serrated discs''' deal large amounts of damage, and have a tendency to sever their victims' limbs. While amusing, this can create several {{L|hauling}} tasks for {{L|dwarves}} as they have to move each severed body part to a {{L|butcher's shop}} or {{L|stockpile|refuse pile}}. Large serrated discs attack three times, giving them a very high damage potential.

===Spiked ball===
The '''spiked ball''' doesn't deal a blunt attack at all, but it does do three attacks with its spikes. Like the menacing spike, it has only a small contact area, but also has a very low penetration depth.

Spiked balls can also be made from {{L|wood}}.

===Enormous corkscrew===

'''Enormous corkscrews''' can be used as components in {{L|Trap}}s as well as for {{L|screw pump}}s. As a result, the corkscrews from unneeded screw pumps can be used to make serviceable weapon traps.

The enormous corkscrew performs a small contact area deeply penetrating attack, much like the menacing spike. It is currently unknown which of these two trap components is the strongest over all.

Enormous corkscrews can also be made from 1 {{L|wood}}.

===Giant axe blade===

The '''giant axe blade''' is a very similar weapon to the large, serrated disc, but only strikes once, compared to the disc's three attacks. However, due to its larger size, its single attack is stronger than each of the large, serrated disc's. It is currently unknown which of these two trap components is the strongest over all.

==Data & comparison==

{|cellpadding="2" border="1"
! Name !! Size !! Number of hits !! Contact Area !! Penetration Depth !! Wood?
|-
| Giant axe blade || 1600 || 1 || 100000 || 10000 || No
|-
| Enormous corkscrew&dagger; || 1600 || 1 || 100 || 10000 || Yes
|-
| Spiked ball || 1000 || 3 || 10 || 200 || Yes
|-
| Large, serrated disc || 1000 || 3 || 100000 || 10000 || No
|-
| Menacing spike&Dagger; || 1600 || 1 || 10 || 6000 || Yes
|-
| colspan=6 | &dagger; ''This trap component is a screw and can also be used in {{l|screw pump|screw pump}}s.'' &Dagger; ''This trap component is a spike and can also be used in {{l|Trap#Upright_Spear/Spike|upright spike traps}}.''
|-
|}
:''(This data has been compiled from raw/objects/item_trapcomp.txt)''

----
'''See also:'''
:*{{l|Weapon}}
:*{{l|Trap}}

{{Category|Weapons}}
{{Category|Items}}
{{Category|Traps}}

v0.31:Blade weed

2010-04-26T12:54:16Z

Oddtwang of Dork:

{{av}}
{{Stub}}
{{Crop|color={{color|2|0}}|seed_color={{color|0|1}}|character=τ|name=Blade weed|seed=Blade weed seed
|spring=1|summer=1|autumn=1|winter=1
|habitat=Not freezing (Dry)
|uses=
* {{L|Dye}}
|other_products=
* {{L|Dye|Emerald dye}} (Mill)
}}

'''Blade weed''' is a plant used only to make emerald {{L|dye}} at a {{L|millstone|mill}} or {{L|quern}}. They can be planted outdoors any time of year and can be collected by {{L|gather plants|gathering plants}} in any dry non-freezing {{L|biome}}.

* Grow time: 500{{verify}}
* Plant value: 4
* Mill value: 20
* Dye color: Emerald
* Seasons: All

==See Also==
*{{L|List of crops|List of crops}}
*{{L|The clothing industry|The clothing industry}}

{{gamedata|[PLANT:WEED_BLADE]
[NAME:blade weed][NAME_PLURAL:blade weed][ADJ:blade weed]
[USE_MATERIAL_TEMPLATE:STRUCTURAL:STRUCTURAL_PLANT_TEMPLATE]
[MATERIAL_VALUE:2]
[BASIC_MAT:LOCAL_PLANT_MAT:STRUCTURAL]
[PICKED_TILE:231][PICKED_COLOR:2:0:0]
[DRY][BIOME:NOT_FREEZING]
[VALUE:2]
[USE_MATERIAL_TEMPLATE:MILL:PLANT_POWDER_TEMPLATE]
[STATE_NAME_ADJ:ALL_SOLID:emerald dye]
[STATE_COLOR:ALL_SOLID:EMERALD]
[DISPLAY_COLOR:2:0:0]
[MATERIAL_VALUE:20]
[POWDER_DYE:EMERALD]
[PREFIX:NONE]
[MILL:LOCAL_PLANT_MAT:MILL]
[SPRING][SUMMER][AUTUMN][WINTER]
[FREQUENCY:25]
[CLUSTERSIZE:5]
[PREFSTRING:stiff, triangular leaves]
[USE_MATERIAL_TEMPLATE:SEED:SEED_TEMPLATE]
[EDIBLE_VERMIN]
[EDIBLE_COOKED]
[SEED:blade weed seed:blade weed seeds:0:0:1:LOCAL_PLANT_MAT:SEED]}}

{{Category|Surface crops}}
{{Category|Non-brewable plants}}
{{Category|Inedible plants}}

v0.31:Burrow

2010-04-26T12:53:50Z

Oddtwang of Dork:

{{AV}}
{{Stub}}
Burrows are part of the new organization of fortresses, user-defined areas in your fort where selected dwarves live and work. You can assign these areas like zones and assign one or more dwarves to them. You may assign the same dwarf to multiple burrows, if desired. 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.

== Defining a new burrow ==

To enter the "define burrow" mode, press {{k|w}}.

You'll be presented with a list of all of your existing burrows. Change which burrow is selected with your secondary selection keys.

To add a new burrow to the list, press {{k|a}}. The new burrow created this way starts with no tiles and a default name.

To configure a burrow, select it and press enter. This is where you'll be able to set the burrow's name, define what tiles it encompasses, and add or remove individual dwarves. Defining the burrow's tiles can be done using rectangles much like other mass-selection or mass-designation situations elsewhere in the game, or you can paint with the mouse. Unlike other area selections, burrow selections can take place over multiple z-levels, meaning that you can select cubes, rather than rectangles; also unlike most other area selections, they may overlap. Press {{k|r}} to set whether you're adding or subtracting tiles from the burrow. You can also set the colors and symbols used for different burrows to help tell them apart. A burrow may span multiple Z levels, so long as a means of getting from one Z level to another is within the Burrow zone.

Unlike {{L|activity zone}}s, burrows can also be extended through not-yet revealed tiles, thus allowing to designate "mining zones" for differently {{L|skill}}ed miners.

== Defending and restricting burrows ==

''Full article: {{l|Scheduling}}

Burrows are one of the ways you can give passive orders to {{l|squads}} and civilians during {{l|Scheduling#Alert levels|alerts}}. Under the squad schedule menu (Press {{k|m}} {{k|s}}) you can add an order to any particular month for the chosen alert with {{k|o}} or edit their existing orders with {{k|e}}. On the Give Orders menu, use {{k|o}} to cycle through the orders given to squads. The order "Defend Burrows" '''cannot''' be given without first creating burrows to assign defenders to. Under a "Defend Burrows" order, dwarves in the squad are stationed in the specific area and will defend it proactively.

Similarly, civilians may be set to only operate within a burrow or set of burrows. They will only leave these burrows when they are dying of hunger/thirst. This is a nice way to ensure your dwarves will work in the mini-fortress you dug out for them (a bed, table/chair, and smelter near magma for example).

==Pathfinding Problems==
In {{version|0.31.01}} pathfinding problems can cause a variety of problems. A common symptom of a pathfinding problem is to see a large percentage of your dwarves suddenly go idle. This can be caused by a single dwarf that is '''stuck'''. There may be other things that will cause pathfinding problems as well. This subject is not terribly well understood just yet but here are some steps that may prove useful in resolving any issues that arise.
*save, exit, and reload your fortress clears many pathfinding issues. This is believed to be due to some sort of caching behavior with pathfinding.
*deleting all burrows can also be a solution when dwarves get '''stuck''', once they are fixed you can attempt to recreate your burrows if desired.
*stripping all labors from a dwarf that is '''stuck''' may help shut him up long enough to rescue him.

Most (all?) pathfinding problems have been fixed in {{version|0.31.03}}.

v0.31:Combat

2010-04-26T12:52:56Z

Oddtwang of Dork:

{{AV}}
{{Stub}}
(This page ''will'' cover the mechanics of combat - once they're figured out. For now, you may want to refer to refer to {{L|combat skill}}s, {{L|military}}, or {{L|squad}}s.)

v0.31:Green zircon

2010-04-26T12:52:40Z

Oddtwang of Dork:

v0.31:Cloth

2010-04-26T12:52:06Z

Oddtwang of Dork:

{{av}}
{{Stub}}

Cloth is made from either plant fiber or silk:
* {{l|cave spider}} silk, found in underground caverns
* {{l|phantom spider}} silk, found in evil forests
* {{l|giant cave spider}} silk, found near giant cave spiders
* {{l|rope reed}}, found/grown above ground
* {{l|pig tail}}, found/grown underground

{{l|Elf|Elves}} bring large amounts of rope reed cloth when they arrive for trading in the spring.

One newly made piece of cloth is worth 10000 'cloth units' and a {{l|thread}} is worth 15000 units of thread, according to {{l|Healthcare|the hospital}}.

v0.31 Talk:Elf

2010-04-26T12:49:59Z

Oddtwang of Dork:

Confirm that trading leather is a no no? [[User:Cpad|Cpad]] 02:04, 10 April 2010 (UTC)

:see update. leather is fine in all forms. --[[User:Birthright|Birthright]] 16:53, 10 April 2010 (UTC)

Needs game data

Creatures that you purchase from them do not appear to breed, even if you have enough of both genders chained or caged in close proximity. Perhaps the elves practice spay/neuter policies with the creatures they trade? [[User:Volouscheur|Volouscheur]] 21:59, 21 April 2010 (UTC)
:That's nothing to do with Elves, it's just that caged animals don't breed. Not sure about chained ones. Incidentally, proximity has nothing to do with breeding at present - everything seems to reproduce through spores :) [[User:Oddtwang of Dork|Oddtwang of Dork]] 12:49, 26 April 2010 (UTC)

==Removed text==

Removed this section as it's not encyclopaedic (or very well-written):

<quote>They are hypocritical, cowardly (Choosing ranged weapons over axes), and "ye best keep your wits about ye" when they are on your map. To sum things up they are not Dwarves... or even Humans (Or even close to Humans), and should therefore be treated as enemies.</quote>

It might be worth including something to the effect of "many players refer to the Elves as 'treehugging hippies' and the like".
[[User:Oddtwang of Dork|Oddtwang of Dork]] 12:49, 26 April 2010 (UTC)

==Demands==

Can anyone verify that Elves still demand you limit deforestation in 0.31? [[User:Oddtwang of Dork|Oddtwang of Dork]] 12:49, 26 April 2010 (UTC)

v0.31:Elf

2010-04-26T12:45:03Z

Oddtwang of Dork:

{{CreatureInfo v0.31
|name=Elf
|symbol=E
|color={{COLOR:3:0:0}}
|biome=
* Any
|butcher=no
}}
{{av}}{{fine}}

:''A medium-sized creature dedicated to the ruthless protection of nature''

Elves are humanoids dedicated to the protection of ''their'' concept of nature (focused on trees).

Elven caravans arrive during the Spring. During {{L|trade}}, elves will '''not''' accept wood, wooden items or any goods {{:|Decoration|decorated}} with wood. This includes ''clear'' {{l|glass}} items and soap, presumably because wood-derived {{L|potash}} and {{L|pearlash}} are used in their production. Elves will, however, gladly trade you their own wooden items. They will not, however, accept their wooden items back. Be careful to not offer them your wooden bins or barrels. If the contents of bins are marked for trade individually, and are not wooden themselves, the elves will not care that you used wooden bins to haul the goods to the depot.

Repeatedly offending elves by attempting to trade wooden items may cause them to attack your fortress with an {{l|ambush}}.{{verify}}

Elves will generally '''accept''' items made of green glass, stone, metal, bone, shell, silk, leather and plant fiber cloth, meat, fish, totems and even plants. They will accept animals in trade, as long as their {{L|Cage|cages}} are not wooden.

They also accept ''raw'' clear glass, ''raw'' crystal glass and raw green glass. (Which are classified as gems, possibly this makes the elves ignore the {{l|pearlash}} used in the first two.)

It is currently unknown if they accept crystal glass ''items'' (a rather scarce trade good anyway).

Elves generally bring all kinds of wooden items like barrels and cages, animals, alcohol, plant fiber and its products as well as small quantities of weapons and plants.

{{Creatures}}
{{Category|Humanoids}}
{{Category|Races}}

v0.31:Elf

2010-04-26T12:44:47Z

Oddtwang of Dork:

{{CreatureInfo v0.31
|name=Elf
|symbol=E
|color={{COLOR:3:0:0}}
|biome=
* Any
|butcher=no
}}
{{av}}{{fine}}

:''A medium-sized creature dedicated to the ruthless protection of nature''

Elves are humanoids dedicated to the protection of ''their'' concept of nature (focused on trees).

Elven caravans arrive during the Spring. During {{L|trade}}, elves will '''not''' accept wood, wooden items or any goods {{:|Decoration|decorated}} with wood. This includes ''clear'' {{l|glass}} items and soap, presumably because wood-derived {{L|potash}} and {{L|Pearlash}} are used in their production. Elves will, however, gladly trade you their own wooden items. They will not, however, accept their wooden items back. Be careful to not offer them your wooden bins or barrels. If the contents of bins are marked for trade individually, and are not wooden themselves, the elves will not care that you used wooden bins to haul the goods to the depot.

Repeatedly offending elves by attempting to trade wooden items may cause them to attack your fortress with an {{l|ambush}}.{{verify}}

Elves will generally '''accept''' items made of green glass, stone, metal, bone, shell, silk, leather and plant fiber cloth, meat, fish, totems and even plants. They will accept animals in trade, as long as their {{L|Cage|cages}} are not wooden.

They also accept ''raw'' clear glass, ''raw'' crystal glass and raw green glass. (Which are classified as gems, possibly this makes the elves ignore the {{l|pearlash}} used in the first two.)

It is currently unknown if they accept crystal glass ''items'' (a rather scarce trade good anyway).

Elves generally bring all kinds of wooden items like barrels and cages, animals, alcohol, plant fiber and its products as well as small quantities of weapons and plants.

{{Creatures}}
{{Category|Humanoids}}
{{Category|Races}}

v0.31:Alluvial layer

2010-04-26T12:36:56Z

Oddtwang of Dork:

{{av}}{{Elven}}
Several minerals and gems are specified to occur within '''alluvial layers'''. However, it is unclear if Dwarf Fortress considers '''any''' layer "alluvial"{{Verify}}.

If such layers were encountered, they would contain small clusters of any of...
:*{{L|native gold}}
:*{{L|native platinum}}
:*{{L|cassiterite}}
:*jade {{L|gem}}s (blue, lavender, pink, white, and green)

{{Category|Stone Layers}}

v0.31:Alluvial layer

2010-04-26T12:36:10Z

Oddtwang of Dork:

{{av}}{{Elven}}
Several minerals and gems are specified to occur within '''alluvial layers'''. However, it is unclear if Dwarf Fortress considers '''any''' layer "alluvial".

If such layers were encountered, they would contain small clusters of any of...
:*{{L|native gold}}
:*{{L|native platinum}}
:*{{L|cassiterite}}
:*jade {{L|gem}}s (blue, lavender, pink, white, and green)

{{Category|Stone Layers}}

Dwarf Fortress Wiki talk:Article Consolidation

2010-04-26T12:31:30Z

Oddtwang of Dork:

v0.31:Screw pump

2010-04-25T23:43:18Z

Oddtwang of Dork:

{{av}}
{{human}}
Note: Pumps will transfer power vertically as they did in 40d. It is confirmed they function in all respects as they did in the previous version. For information on vertical power transfer see Pump Stack below.

{{Machine_component|name=Screw pump|key=s|job=[[40d:Pump operator|Pump operator]]
|construction=
* {{L|Trap component#Enormous corkscrew|Enormous corkscrew}}
* {{L|Pipe section}}
* {{L|Block}}
|construction_job=
* {{L|Architecture}}
* 1 of
** {{L|Carpentry}}
** {{L|Masonry}}
** {{L|Metalsmithing}}
|power=Needs 10 power.
}}

A '''screw pump''' is a small {{L|building}} that can lift liquids ({{L|water}} or {{L|magma}}) from one level below onto the same {{L|Z-level}} as the pump. It is two tiles by one tile in size, and it can be either manually operated by a {{L|dwarf}} with the {{L|pump operator}} job or by being {{L|power}}ed by {{L|water wheel}}s and/or {{L|windmill}}s.

The direction you want the fluid to travel must be chosen at the time of construction. Pumping only occurs in a straight line, and involves a total of 4 tiles in a row - the liquid source, two for the pump, and the output. The "rise" in levels occurs on the first tile, the intake side, from one level below up to the level of the pump*. Pumped fluids can and will flow immediately after being pumped, as normal for that fluid. Pumped fluids will have a {{L|pressure}} equal to the exit {{L|z-level}} - a pump never "forces" water to a higher {{L|z-level}} than the output tile.

:''(* A DF pump can best be imagined as a simple [http://en.wikipedia.org/wiki/Archimedes%27_screw archimedes screw].)''

Salt water pumped through a pump will become drinkable if then kept separate from natural walls, natural floors, other salt water or an aquifer.{{verify}}

''For a basic overview of how the different machine parts work and work together, see {{L|machinery}}.''

== Construction ==

Building a screw pump requires an {{L|Trap component#Enormous corkscrew|enormous corkscrew}}, a {{L|block}}, and a {{L|pipe section}}. The construction itself is completed in two stages. First a dwarf with the {{L|architect}} labor must design it. Then a dwarf (the same or a different one) with the appropriate labor must complete the building. This could be {{L|carpentry}}, {{L|metalsmithing}}, or {{L|masonry}}, depending on the material of the block.

It's important to choose the proper orientation for your pump, where it will draw water from and where it will deliver the water. This is determined before placement with the {{k|u}}, {{k|k}}, {{k|m}}, or {{k|h}} keys, and the text at the top of the sub-menu will change to confirm your choice. The default (as shown above in the sidebar), "pumps from the north" (top). The ''light'' green X must be next to the liquid source and the ''dark'' green X is where the liquid exits the pump. [[Image:Small pump.jpg|thumb|right|300px|'''Basic Side View of a Pump'''. This pump "pumps from the west", from left to right. The area to the right may fill to the top of that level, but no more (See {{L|pressure}}; see {{L|Screw pump#Pump Stack|Pump stack}}). Note that the entire space required is 4 tiles long by 1 tile wide, not including any retaining walls for the outflow. If pumped manually, the {{L|pump operator}} stands in the light-colored area, as the dark-colored is impassable to both fluid and movement. 
''(Although the "liquid" is shown as blue, this can work for {{L|magma|magma}} as well, with the {{L|magma-safe|appropriate precautions}}.)'']]
 
:{|style="font-family: monospace; font-weight: bold; font-size: 135%; border: 1px solid #0b0; background: #dfd"
|-
|style="color: #0f0; padding: 0"|X||style="color: #070; padding: 0"|X
|}
This example "pumps from the west" (left) to the east (right), the {{k|h}} option. If pumped manually, the dwarf stands on the light-colored tile, as the dark-colored is impassable.

The orientation is visible after placement by using {{k|q}}uery over or near that pump or during placement, using UMKH to select the direction of input. Orientation of a pump cannot be changed after being constructed, but, as with any building, it can be deconstructed into its component parts and rebuilt as and where desired.

Having specified the direction of travel, you must ensure that the source side of the pump is placed adjacent to and above (in the {{L|z-axis}}) a liquid. The screw pump will draw the liquid up from below its level, and distribute it out of the other side of the pump.

== Notes ==

* The source of the pump must be directionally adjacent to "Open Space" that is directly above a source of liquid. The adjacent space cannot be a floor, stairway or wall suspended over water. Screw pumps can pull water through a {{L|grate}}, floor {{L|bars}}, or a {{L|construction|constructed}} {{L|fortification}} on the Z-level below.
* The light pump tile is where a pump operator will stand (if the pump is not powered mechanically). Liquids to be pumped must be 1 level below the (empty) area adjacent to this tile.
* Dwarves must be able to access and stand on the light tile of the pump in order to build the pump and then to be able to operate the pump manually.
* The dark pump tile is on the output side. Liquids will appear in the tile adjacent to this.
* The dark pump tile blocks liquids flow and creature movement, and can be built into a wall to create a solid barrier. The light tile of the pump does not block flow or movement.
* Pumps can also be used in conjunction with a {{L|water wheel}} or a {{L|windmill}} to become self-powered.
* Active mechanisms connected to the pump will automatically start the pump; to prevent this either restrict liquid flow using floodgates or hatches, or put in a {{L|gear assembly}} linked to a {{L|lever}} to disconnect the {{L|power}}.
* Adjacent pumps ''automatically'' transfer mechanical power to any other adjacent pump(s), no {{L|axle}} or {{L|mechanism}} is required. If too many pumps are adjacent, there may be insufficient power to power them.
* A hatch above the input tile (on the same level as the pump) that is linked to a trigger (a {{L|lever}} or {{L|pressure plate}}) makes an effective on/off switch for that pump.
* In order to build pumps in a "hanging" state, as in the stacked screw pump example (below), one of its tiles must be able to connect to a nearby machine, either already existing or designated to be built. If, when the screw pump's construction is completed, the supporting mechanism has not yet been completed, it will promptly collapse into its component parts.
* Pumps do '''not''' push liquids '''up''' additional Z-levels above them. They only deliver water to their own level. That is, if you direct the output of a screw pump into a 1-square space surrounded by walls, the water will not "overflow" the walls. Consequently, a pump will refuse to move liquid if the level it is pumping to is completely filled. Higher levels can be achieved using a "pump stack" (below). (See {{L|Pressure}})
* In order to safely pump magma, you do not need to build a pump out of {{L|magma-safe}} materials, unless the open tile is going to be submerged in magma.{{verify}}
** Exception: Wooden parts {{L|wear}} out fairly quickly when used to pump magma, eventually causing the pump to break down into the non-wooden parts. This is due to the magma heating the adjacent tiles to a temperature at which wood takes heat damage.{{verify}}
* Magma, which normally has no pressure, will behave like pressurized when pumped. For example, when pumped into an U-turn, magma will come out at the other end. Normal (non-pumped) magma would just pool at the lowest level. This may be either very useful (can be used to build pressure towers for magma) or deadly (forge level flooded with magma, because someone tried to pump magma into a volcano).
* Pump's pseudo-pressure doesn't work across diagonals. If there is a diagonal-only passage in your tunnel, liquids will seep slowly through it, instead of bursting through above their normal maximal speed, like they would if there was good passage.

====Common mistakes====
* Orienting a pump incorrectly, and/or not having a proper open liquid source.
* Pumping water into an area with a path to other parts of your fortress. (The pump may work perfectly - the fortress quickly [[40d:flood|flood]]s.)
* Expecting water to rise up above the same level of a pump.
* Building a wall attached only to the light tile - this leaves a diagonal leak between the wall and the dark tile unless sealed there. (If that's not a problem, don't worry about it.)
* Having stairs as input tile. Stairs block input tile, thus rendering the pump useless, even though liquids usually ignore stairs. Output tile can be any liquid-passable tile.

== Example layouts ==
=== Single Pump ===

[[Image:jt_screwpump.png|frame|left|A screw pump delivers from the level below to the tile in front. This pump pumps from the right to the left. The "dark tile" would be on the left - that entire tile is impassible to movement and fluids.]] 
=== Pump Stack ===
[[File:PumpStack2010.png|thumb|right|300px|'''Illustrated Side View of a Pump Stack'''.]]
[[File:PumpStackTopView.png|thumb|right|300px|'''Illustrated Top View of a Pump Stack Layer'''.]]
A Pump Stack is a method used to draw water or magma vertically across multiple z-levels requiring a minimum of parts. The basic functionality is possible because the Output (dark) side of the pump can be built over open space with a machine component located directly below, in this case another Screw Pump. Note that for power to properly transfer the intake (light) side of the pump must line up with the output (dark) side of the pump on the floor above it through a space in the floor, as in the illustration.

A pump stack minimizes the amount of machinery required to lift water or magma by allowing for power to be supplied directly to only the most accessible pump (typically the topmost) which in turn allows the player to operate a stack limited only by how many windmills/water wheels they can fit into the area.

Typical applications for a pump stack include moving magma from a lower level up to a convenient level for forges and furnaces, extracting water from a flooded fort, raising water for a decorative waterfall (and extracting it afterwards), or any other purpose that requires water/magma on a z-level significantly above its current location.

The Illustrated Top View of a Pump Stack Layer shows a basic section of a pump stack. Only the door (or a floodgate) on the Containment side is strictly necessary in order to prevent flooding. Two doorways are used here, each lining up with the solid ground within the pump assembly, in order to prevent workers from trapping themselves after digging channels or assembling the pump.

{{buildings}}

v0.31:Screw pump

2010-04-25T23:41:44Z

Oddtwang of Dork: /* Construction */

{{av}}
{{human}}
Note: Pumps will transfer power vertically as they did in 40d. It is confirmed they function in all respects as they did in the previous version. For information on vertical power transfer see Pump Stack below.

{{Machine_component|name=Screw pump|key=s|job=[[40d:Pump operator|Pump operator]]
|construction=
* {{L|Enormous corkscrew}}
* {{L|Pipe}}
* {{L|Block}}
|construction_job=
* {{L|Architecture}}
* 1 of
** {{L|Carpentry}}
** {{L|Masonry}}
** {{L|Metalsmithing}}
|power=Needs 10 power.
}}

A '''screw pump''' is a small {{L|building}} that can lift liquids ({{L|water}} or {{L|magma}}) from one level below onto the same {{L|Z-level}} as the pump. It is two tiles by one tile in size, and it can be either manually operated by a {{L|dwarf}} with the {{L|pump operator}} job or by being {{L|power}}ed by {{L|water wheel}}s and/or {{L|windmill}}s.

The direction you want the fluid to travel must be chosen at the time of construction. Pumping only occurs in a straight line, and involves a total of 4 tiles in a row - the liquid source, two for the pump, and the output. The "rise" in levels occurs on the first tile, the intake side, from one level below up to the level of the pump*. Pumped fluids can and will flow immediately after being pumped, as normal for that fluid. Pumped fluids will have a {{L|pressure}} equal to the exit {{L|z-level}} - a pump never "forces" water to a higher {{L|z-level}} than the output tile.

:''(* A DF pump can best be imagined as a simple [http://en.wikipedia.org/wiki/Archimedes%27_screw archimedes screw].)''

Salt water pumped through a pump will become drinkable if then kept separate from natural walls, natural floors, other salt water or an aquifer.{{verify}}

''For a basic overview of how the different machine parts work and work together, see {{L|machinery}}.''

== Construction ==

Building a screw pump requires an {{L|Trap component#Enormous corkscrew|enormous corkscrew}}, a {{L|block}}, and a {{L|pipe section}}. The construction itself is completed in two stages. First a dwarf with the {{L|architect}} labor must design it. Then a dwarf (the same or a different one) with the appropriate labor must complete the building. This could be {{L|carpentry}}, {{L|metalsmithing}}, or {{L|masonry}}, depending on the material of the block.

It's important to choose the proper orientation for your pump, where it will draw water from and where it will deliver the water. This is determined before placement with the {{k|u}}, {{k|k}}, {{k|m}}, or {{k|h}} keys, and the text at the top of the sub-menu will change to confirm your choice. The default (as shown above in the sidebar), "pumps from the north" (top). The ''light'' green X must be next to the liquid source and the ''dark'' green X is where the liquid exits the pump. [[Image:Small pump.jpg|thumb|right|300px|'''Basic Side View of a Pump'''. This pump "pumps from the west", from left to right. The area to the right may fill to the top of that level, but no more (See {{L|pressure}}; see {{L|Screw pump#Pump Stack|Pump stack}}). Note that the entire space required is 4 tiles long by 1 tile wide, not including any retaining walls for the outflow. If pumped manually, the {{L|pump operator}} stands in the light-colored area, as the dark-colored is impassable to both fluid and movement. 
''(Although the "liquid" is shown as blue, this can work for {{L|magma|magma}} as well, with the {{L|magma-safe|appropriate precautions}}.)'']]
 
:{|style="font-family: monospace; font-weight: bold; font-size: 135%; border: 1px solid #0b0; background: #dfd"
|-
|style="color: #0f0; padding: 0"|X||style="color: #070; padding: 0"|X
|}
This example "pumps from the west" (left) to the east (right), the {{k|h}} option. If pumped manually, the dwarf stands on the light-colored tile, as the dark-colored is impassable.

The orientation is visible after placement by using {{k|q}}uery over or near that pump or during placement, using UMKH to select the direction of input. Orientation of a pump cannot be changed after being constructed, but, as with any building, it can be deconstructed into its component parts and rebuilt as and where desired.

Having specified the direction of travel, you must ensure that the source side of the pump is placed adjacent to and above (in the {{L|z-axis}}) a liquid. The screw pump will draw the liquid up from below its level, and distribute it out of the other side of the pump.

== Notes ==

* The source of the pump must be directionally adjacent to "Open Space" that is directly above a source of liquid. The adjacent space cannot be a floor, stairway or wall suspended over water. Screw pumps can pull water through a {{L|grate}}, floor {{L|bars}}, or a {{L|construction|constructed}} {{L|fortification}} on the Z-level below.
* The light pump tile is where a pump operator will stand (if the pump is not powered mechanically). Liquids to be pumped must be 1 level below the (empty) area adjacent to this tile.
* Dwarves must be able to access and stand on the light tile of the pump in order to build the pump and then to be able to operate the pump manually.
* The dark pump tile is on the output side. Liquids will appear in the tile adjacent to this.
* The dark pump tile blocks liquids flow and creature movement, and can be built into a wall to create a solid barrier. The light tile of the pump does not block flow or movement.
* Pumps can also be used in conjunction with a {{L|water wheel}} or a {{L|windmill}} to become self-powered.
* Active mechanisms connected to the pump will automatically start the pump; to prevent this either restrict liquid flow using floodgates or hatches, or put in a {{L|gear assembly}} linked to a {{L|lever}} to disconnect the {{L|power}}.
* Adjacent pumps ''automatically'' transfer mechanical power to any other adjacent pump(s), no {{L|axle}} or {{L|mechanism}} is required. If too many pumps are adjacent, there may be insufficient power to power them.
* A hatch above the input tile (on the same level as the pump) that is linked to a trigger (a {{L|lever}} or {{L|pressure plate}}) makes an effective on/off switch for that pump.
* In order to build pumps in a "hanging" state, as in the stacked screw pump example (below), one of its tiles must be able to connect to a nearby machine, either already existing or designated to be built. If, when the screw pump's construction is completed, the supporting mechanism has not yet been completed, it will promptly collapse into its component parts.
* Pumps do '''not''' push liquids '''up''' additional Z-levels above them. They only deliver water to their own level. That is, if you direct the output of a screw pump into a 1-square space surrounded by walls, the water will not "overflow" the walls. Consequently, a pump will refuse to move liquid if the level it is pumping to is completely filled. Higher levels can be achieved using a "pump stack" (below). (See {{L|Pressure}})
* In order to safely pump magma, you do not need to build a pump out of {{L|magma-safe}} materials, unless the open tile is going to be submerged in magma.{{verify}}
** Exception: Wooden parts {{L|wear}} out fairly quickly when used to pump magma, eventually causing the pump to break down into the non-wooden parts. This is due to the magma heating the adjacent tiles to a temperature at which wood takes heat damage.{{verify}}
* Magma, which normally has no pressure, will behave like pressurized when pumped. For example, when pumped into an U-turn, magma will come out at the other end. Normal (non-pumped) magma would just pool at the lowest level. This may be either very useful (can be used to build pressure towers for magma) or deadly (forge level flooded with magma, because someone tried to pump magma into a volcano).
* Pump's pseudo-pressure doesn't work across diagonals. If there is a diagonal-only passage in your tunnel, liquids will seep slowly through it, instead of bursting through above their normal maximal speed, like they would if there was good passage.

====Common mistakes====
* Orienting a pump incorrectly, and/or not having a proper open liquid source.
* Pumping water into an area with a path to other parts of your fortress. (The pump may work perfectly - the fortress quickly [[40d:flood|flood]]s.)
* Expecting water to rise up above the same level of a pump.
* Building a wall attached only to the light tile - this leaves a diagonal leak between the wall and the dark tile unless sealed there. (If that's not a problem, don't worry about it.)
* Having stairs as input tile. Stairs block input tile, thus rendering the pump useless, even though liquids usually ignore stairs. Output tile can be any liquid-passable tile.

== Example layouts ==
=== Single Pump ===

[[Image:jt_screwpump.png|frame|left|A screw pump delivers from the level below to the tile in front. This pump pumps from the right to the left. The "dark tile" would be on the left - that entire tile is impassible to movement and fluids.]] 
=== Pump Stack ===
[[File:PumpStack2010.png|thumb|right|300px|'''Illustrated Side View of a Pump Stack'''.]]
[[File:PumpStackTopView.png|thumb|right|300px|'''Illustrated Top View of a Pump Stack Layer'''.]]
A Pump Stack is a method used to draw water or magma vertically across multiple z-levels requiring a minimum of parts. The basic functionality is possible because the Output (dark) side of the pump can be built over open space with a machine component located directly below, in this case another Screw Pump. Note that for power to properly transfer the intake (light) side of the pump must line up with the output (dark) side of the pump on the floor above it through a space in the floor, as in the illustration.

A pump stack minimizes the amount of machinery required to lift water or magma by allowing for power to be supplied directly to only the most accessible pump (typically the topmost) which in turn allows the player to operate a stack limited only by how many windmills/water wheels they can fit into the area.

Typical applications for a pump stack include moving magma from a lower level up to a convenient level for forges and furnaces, extracting water from a flooded fort, raising water for a decorative waterfall (and extracting it afterwards), or any other purpose that requires water/magma on a z-level significantly above its current location.

The Illustrated Top View of a Pump Stack Layer shows a basic section of a pump stack. Only the door (or a floodgate) on the Containment side is strictly necessary in order to prevent flooding. Two doorways are used here, each lining up with the solid ground within the pump assembly, in order to prevent workers from trapping themselves after digging channels or assembling the pump.

{{buildings}}

v0.31:Gnomeblight

2010-04-25T20:25:51Z

Oddtwang of Dork:

{{av}}{{elven}}

Gnomeblight is a poisonous {{L|Extract|extract}} made from {{L|Kobold bulb}}s, and causes moderate necrosis to both {{L|Mountain gnome|Mountain}} and {{L|Dark gnome|Dark}} gnomes. It is extracted into a {{L|flask}} and is worth 100☼.

40d:Alluvial layer

2010-04-25T20:22:50Z

Oddtwang of Dork: Removed "as of this version" text, as it's clear from the namespace / AV template.

{{av}}
Several minerals and gems are specified to occur within '''alluvial layers'''. However, no stone or soil layers are considered to be "alluvial".

~''If''~ they were to exist, they would contain small clusters of any of...
:*{{L|native gold}}
:*{{L|native platinum}}
:*{{L|cassiterite}} (for {{L|tin}})
:*jade {{L|gem}}s (blue, lavender, pink, white, and green)

{{Category|Stone Layers}}

Dwarf Fortress Wiki talk:Quality

2010-04-25T20:20:01Z

Oddtwang of Dork:

v0.31:Calcite

2010-04-25T20:17:20Z

Oddtwang of Dork:

v0.31:Wood industry

2010-04-25T20:16:22Z

Oddtwang of Dork:

{{av}}
{{elven}}

=={{L|Bowyer's workshop|Boyer's workshop}}==
Used for creating wooden {{L|Crossbow|crossbow}}s.
=={{L|Carpenter's workshop}}==
Used for creating:
*Wooden {{L|Furniture|furniture}}
*Wooden {{L|Shield|bucklers and shields}}
*Wooden {{L|Training weapon|training weapons}}
*Wooden {{L|Weapon#Trap weapon statistics|trap components}}

=={{L|Craftsdwarf's workshop}}==
Used for creating:
*Wooden {{L|Craft|crafts}}
*Wooden {{L|Bolt|bolts}}
*{{L|Obsidian}} Short Swords
=={{L|Siege workshop}}==
Used for creating {{L|Siege engine|siege engine parts}}
=={{L|Wood furnace}}==
Used for creating:
*{{L|Ash}}
*{{L|Charcoal}}

[[Category:Materials]]
[[Category:Industry]]

v0.31:Wood industry

2010-04-25T20:14:29Z

Oddtwang of Dork:

{{av}}
{{elven}}
{{av}}

=={{L|Bowyer's workshop|Boyer's workshop}}==
Used for creating wooden {{L|Crossbow|crossbow}}s.
=={{L|Carpenter's workshop}}==
Used for creating:
*Wooden {{L|Furniture|furniture}}
*Wooden {{L|Buckler|bucklers}} and wooden {{L|Shield|shields}}
*Wooden {{L|Training weapon|training weapons}}
*Wooden {{L|Weapon#Trap weapon statistics|trap components}}

=={{L|Craftsdwarf's workshop}}==
Used for creating:
*Wooden {{L|Craft|crafts}}
*Wooden {{L|Bolt|bolts}}
*{{L|Obsidian}} Short Swords
=={{L|Siege workshop}}==
Used for creating {{L|Siege engine|siege engine parts}}
=={{L|Wood furnace}}==
Used for creating:
*{{L|Ash}}
*{{L|Charcoal}}

[[Category:Materials]]
[[Category:Industry]]

v0.31:Turquoise

2010-04-25T20:08:09Z

Oddtwang of Dork:

Template talk:Main page progress bar

2010-04-25T20:06:04Z

Oddtwang of Dork: Undo revision 99298 by Oddtwang of Dork (Talk)

== I like this ==
Good work on this, obviously you're ironing out some details but I can see where it's going and I'm all for it. [[User:Mason11987|Mason]] ([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]]) 01:47, 25 April 2010 (UTC)

Neat idea. I took the liberty of adding a link to the article quality page for anyone who was thinking "how did they decide that?". Might be worth getting some sort of estimate of how many articles are unrated (of the ones in the main, DF2010 and 40d namespaces I'dve thought - maybe just the main and DF2010 ones in fact). [[User:Oddtwang of Dork|Oddtwang of Dork]] 20:03, 25 April 2010 (UTC)

Template talk:Main page progress bar

2010-04-25T20:05:32Z

Oddtwang of Dork:

Template talk:Main page progress bar

2010-04-25T20:03:29Z

Oddtwang of Dork:

Template:Main page progress bar

2010-04-25T20:00:32Z

Oddtwang of Dork: Linkified to article quality page.

<center>
<div style="width:{{{width|95%}}};"><big>'''{{#expr:({{#expr: ((({{PAGESINCAT:Elven Quality Articles|R}} * 0) +({{PAGESINCAT:Human Quality Articles|R}} * 50) + ({{PAGESINCAT:Dwarven Quality Articles|R}} * 100))/(({{PAGESINCAT:Elven Quality Articles|R}} + {{PAGESINCAT:Human Quality Articles|R}} + {{PAGESINCAT:Dwarven Quality Articles|R}})))}}) round 0}} out of 100'''</big> overall wiki [[Dwarf Fortress Wiki:Quality|quality]] rating (estimate)
<p style="-moz-border-radius-bottomright: 6px; -webkit-border-bottom-right-radius: 6px;-moz-border-radius-topleft: 6px; -webkit-border-top-left-radius: 6px;
border:1px solid #bbb; padding:2px; overflow:hidden; background:#eee;"><span style="width:{{#expr: ({{PAGESINCAT:Dwarven Quality Articles|R}}/({{PAGESINCAT:Elven Quality Articles|R}} + {{PAGESINCAT:Human Quality Articles|R}} + {{PAGESINCAT:Dwarven Quality Articles|R}})) * 100 round 1}}%; height:{{{height|16}}}px; background:#bd8; float:right; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 4px; padding:0; margin:0;"> <span style="width:{{#expr: ({{PAGESINCAT:Human Quality Articles|R}}/({{PAGESINCAT:Elven Quality Articles|R}} + {{PAGESINCAT:Human Quality Articles|R}} + {{PAGESINCAT:Dwarven Quality Articles|R}})) * 100 round 1}}%; height:{{{height|16}}}px; background:#49f;
background:-webkit-gradient(
linear,
left bottom,
right bottom,
color-stop(0, #49f),
color-stop(1, #bd8)
);float:right;padding:0; margin:0; text-align:left;"> <span style="width:{{#expr: ({{PAGESINCAT:Elven Quality Articles|R}}/({{PAGESINCAT:Elven Quality Articles|R}} + {{PAGESINCAT:Human Quality Articles|R}} + {{PAGESINCAT:Dwarven Quality Articles|R}})) * 100 round 1}}%; height:{{{height|16}}}px; background: #db8;
background:-webkit-gradient(
linear,
left bottom,
right bottom,
color-stop(0, #ff8),
color-stop(.75, #db8),
color-stop(1, #49f)
);
float:right; -moz-border-radius-topleft: 4px; -webkit-border-top-left-radius: 4px;padding:0; margin:0; text-align:left;"> </div></center>
<noinclude>
{{#expr: ({{PAGESINCAT:Elven Quality Articles|R}}/({{PAGESINCAT:Elven Quality Articles|R}} + {{PAGESINCAT:Human Quality Articles|R}} + {{PAGESINCAT:Dwarven Quality Articles|R}})) * 100 round 1}}% Stub articles 
{{#expr: ({{PAGESINCAT:Human Quality Articles|R}}/({{PAGESINCAT:Elven Quality Articles|R}} + {{PAGESINCAT:Human Quality Articles|R}} + {{PAGESINCAT:Dwarven Quality Articles|R}})) * 100 round 1}}% Fine articles 
{{#expr: ({{PAGESINCAT:Dwarven Quality Articles|R}}/({{PAGESINCAT:Elven Quality Articles|R}} + {{PAGESINCAT:Human Quality Articles|R}} + {{PAGESINCAT:Dwarven Quality Articles|R}})) * 100 round 1}}% Exceptional articles 
{{#expr: (({{PAGESINCAT:Elven Quality Articles|R}} + {{PAGESINCAT:Human Quality Articles|R}} + {{PAGESINCAT:Dwarven Quality Articles|R}}))}} Total rated articles
</noinclude>

Military guide

2010-04-25T19:39:28Z

Oddtwang of Dork: Redirected page to DF2010:Military

#REDIRECT: [[DF2010:Military]]

Talk:Cavern map

2010-04-25T19:38:06Z

Oddtwang of Dork: Created page with 'Redirected to 23a (the only space in which that page exists). I guess there's a chance people will hit this while looking for DF2010:Cavern though. ~~~~'

Redirected to 23a (the only space in which that page exists). I guess there's a chance people will hit this while looking for [[DF2010:Cavern]] though. [[User:Oddtwang of Dork|Oddtwang of Dork]] 19:38, 25 April 2010 (UTC)

Medical status

2010-04-25T19:36:09Z

Oddtwang of Dork: Redirected page to DF2010:Medical status

#REDIRECT: [[DF2010:Medical status]]

Creature texture tokens

2010-04-25T19:30:20Z

Oddtwang of Dork: Redirected page to DF2010:Creature texture tokens

#REDIRECT: [[DF2010:Creature texture tokens]]