Dwarf Fortress Wiki - User contributions [en]

Fuel industry

2021-02-21T19:32:29Z

Toxicshadow: changed "primary industry" to "secondary industry" to match the industry drop-down below.

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

The '''fuel industry''' deals with the harvesting and use of wood or minerals for the production of fuel in the [[Metal industry]], [[Glass industry]], and [[Ceramic industry]]. It is considered a secondary industry because it refines raw harvested materials, and prepares them for further use in secondary industries.

== Products ==
{{main|Fuel}}
* Coke
* Charcoal

== Industry overview ==
{| style="border-spacing: 0; width: 41em"

|-

{{Industry Block|industry=Wood industry
|background=#fff
}}

{{Item Block|title=[[Bituminous coal]] veins
|background=#CCC|
| |#fff|☼|#888|☼|#888| |#fff|
| |#fff|☼|#888|☼|#888| |#fff|
}}

{{Item Block|title=[[Lignite]] veins
|background=#CCC|
| |#fff|*|#888|*|#888| |#fff|
| |#fff|*|#888|*|#888| |#fff|
}}

{{Empty Block}}

{{Empty Block}}

|-

{{Arrow Block|
| |L|#fff| |
|E| |C|#fff|E| |
| |A|#fff| |
}}

{{Skill Block|skill=[[Mining]]
|color=7:0|
| |L|#ccc| |
|E| |C|#ccc|E| |
| |A|#ccc| |
}}

{{Skill Block|skill=[[Mining]]
|color=7:0|
| |L|#ccc| |
|E| |C|#ccc|E| |
| |A|#ccc| |
}}

{{Empty Block}}

{{Empty Block}}

|-

{{Item Block|title=Wood
|background=#000|
|▬|#880|▬|#880|▬|#880|▬|#880|
|▬|#880|▬|#880|▬|#880|▬|#880|
}}

{{Item Block|title=[[Bituminous coal]]
|background=#000|
|☼|#888|☼|#888|☼|#888|☼|#888|
|☼|#888|☼|#888|☼|#888|☼|#888|
}}

{{Item Block|title=[[Lignite]]
|background=#000|
|•|#888|•|#888|•|#888|•|#888|
|•|#888|•|#888|•|#888|•|#888|
}}

{{Arrow Block|
| |E| | |
|E| |C|#fa8|L|#fa8|
| |A|#fa8| |
}}

{{Use Block|item=[[Magma]]|use=Powers magma furnaces
|background=#fa8|
}}

|-

{{Workshop Block|workshop=Wood furnace|skill=[[Wood burning|Wood burning]]
|color=6:0|
| |L|#882| |
|E| |C|#882|E| |
| |A|#882| |
}}

{{Arrow Block|
| |L|#888| |
|E| |C|#888|L|#888|
| |E| | |
}}

{{Workshop Block|workshop=Smelter|skill=[[Furnace operating|Furnace operating]]
|color=0:1|
| |L|#888| |
|L|#888|C|#888|L|#fa8|
| |L|#888| |
}}

{{Use Block|item=[[Fuel]]|use=Powers furnaces
|background=#fa8|
}}

{{Arrow Block|
| |E| | |
|L|#fa8|C|#fa8|E| |
| |L|#fa8| |
}}

|-

{{Item Block|title=[[Charcoal]]
|background=#000|
|≡|#888|≡|#888|≡|#888|≡|#888|
|≡|#888|≡|#888|≡|#888|≡|#888|
}}

{{Item Block|title=[[Coke]]
|background=#000|
|≡|#888|≡|#888|≡|#888|≡|#888|
|≡|#888|≡|#888|≡|#888|≡|#888|
}}

{{Arrow Block|
| |L|#888| |
|A|#888|C|#888|E| |
| |E| | |
}}

{{Arrow Block|
| |A|#fff| |
|E| |T|#fff|E| |Powers non-magma furnaces
| |L|#fff| |
}}

{{Arrow Block|
| |L|#fa8| |
|E| |C|#fa8|E| |
| |L|#fa8| |
}}

|-

{{Arrow Block|
| |L|#fff| |
|E| |C|#fff|L|#fff|
| |E| | |
}}

{{Arrow Block|
| |L|#fff| |
|L|#fff|C|#fff|L|#fff|
| |L|#fff| |
}}

{{Arrow Block|
| |E| | |
|L|#fff|C|#fff|L|#fff|
| |E| | |
}}

{{Arrow Block|
| |L|#fff| |
|L|#fff|C|#fff|E| |
| |E| | |
}}

{{Arrow Block|
| |L|#fa8| |
|E| |C|#fa8|E| |
| |L|#fa8| |
}}

|-

{{Empty Block}}

{{Arrow Block|
| |L|#fff| |
|E| |T|#fff|E| |For [[Steel]] production
| |L|#fff| |
}}

{{Arrow Block|
| |E|# | |
|E| |C|#fa8|L|#fa8|
| |A|#fa8| |
}}

{{Arrow Block|
| |E|# | |
|L|#fa8|C|#fa8|L|#fa8|
| |A|#fa8| |
}}

{{Arrow Block|
| |L|#fa8| |
|L|#fa8|C|#fa8|E| |
| |A|#fa8| |
}}

|-

{{Empty Block}}

{{Arrow Block|
| |L|#fff| |
|E| |C|#fff|A|#fff|
| |E| | |
}}

{{Industry Block|industry=Metal industry
|background=#fff|
}}

{{Industry Block|industry=Glass industry
|background=#fff|
}}

{{Industry Block|industry=Ceramic industry
|background=#fff|
}}

|}

{{Category|Industry}}
{{Industry}}
[[ru:Fuel industry]]

Language words.txt

2019-07-03T03:35:06Z

Toxicshadow: Quick reference for the symbols.

== Symbols ==
The symbols in vanilla DF 44.12 are as follows:
# Line 5: [SYMBOL:FLOWERY]
# Line 129: [SYMBOL:NATURE]
# Line 396: [SYMBOL:PRIMITIVE]
# Line 452: [SYMBOL:HOLY]
# Line 489: [SYMBOL:EVIL]
# Line 559: [SYMBOL:NEGATOR]
# Line 688: [SYMBOL:MAGIC]
# Line 725: [SYMBOL:VIOLENT]
# Line 929: [SYMBOL:PEACE]
# Line 956: [SYMBOL:UGLY]
# Line 1067: [SYMBOL:DEATH]
# Line 1125: [SYMBOL:OLD]
# Line 1159: [SYMBOL:SUBORDINATE]
# Line 1247: [SYMBOL:LEADER]
# Line 1302: [SYMBOL:NEW]
# Line 1326: [SYMBOL:DOMESTIC]
# Line 1554: [SYMBOL:MYTHIC]
# Line 1601: [SYMBOL:ARTIFICE]
# Line 1801: [SYMBOL:COLOR]
# Line 1880: [SYMBOL:MYSTERY]
# Line 1962: [SYMBOL:NEGATIVE]
# Line 2253: [SYMBOL:ROMANTIC]
# Line 2292: [SYMBOL:ASSERTIVE]
# Line 2392: [SYMBOL:AQUATIC]
# Line 2432: [SYMBOL:PROTECT]
# Line 2479: [SYMBOL:RESTRAIN]
# Line 2515: [SYMBOL:THOUGHT]
# Line 2560: [SYMBOL:WILD]
# Line 2618: [SYMBOL:NAME_SWAMP]
# Line 2629: [SYMBOL:NAME_DESERT]
# Line 2634: [SYMBOL:NAME_FOREST]
# Line 2638: [SYMBOL:NAME_MOUNTAINS]
# Line 2653: [SYMBOL:NAME_OCEAN]
# Line 2660: [SYMBOL:NAME_GLACIER]
# Line 2666: [SYMBOL:NAME_TUNDRA]
# Line 2672: [SYMBOL:NAME_GRASSLAND]
# Line 2678: [SYMBOL:NAME_HILLS]
# Line 2681: [SYMBOL:NAME_REGION]
# Line 2691: [SYMBOL:NAME_CAVE]
# Line 2719: [SYMBOL:EARTH]
# Line 2754: [SYMBOL:NAME_LAKE]
# Line 2759: [SYMBOL:NAME_ENTITY_KINGDOM]
# Line 2768: [SYMBOL:NAME_ENTITY_TOWN_FOUNDER]
# Line 2777: [SYMBOL:GOOD]
# Line 2818: [SYMBOL:NAME_CONTINENT]
# Line 2822: [SYMBOL:NAME_ISLAND]
# Line 2826: [SYMBOL:NAME_ISLAND_SMALL]
# Line 2830: [SYMBOL:NAME_PEAK]
# Line 2862: [SYMBOL:NAME_VOLCANO]
# Line 2875: [SYMBOL:NAME_COMMON_RELIGION]
# Line 2887: [SYMBOL:BALANCE]
# Line 2903: [SYMBOL:BOUNDARY]
# Line 2914: [SYMBOL:DANCE]
# Line 2923: [SYMBOL:DARKNESS]
# Line 2943: [SYMBOL:LIGHT]
# Line 2970: [SYMBOL:ORDER]
# Line 2985: [SYMBOL:FESTIVAL]
# Line 3007: [SYMBOL:FAMILY]
# Line 3025: [SYMBOL:FIRE]
# Line 3055: [SYMBOL:FOOD]
# Line 3122: [SYMBOL:FREEDOM]
# Line 3134: [SYMBOL:GAMES]
# Line 3155: [SYMBOL:LUCK]
# Line 3169: [SYMBOL:MUSIC]
# Line 3190: [SYMBOL:SKY]
# Line 3203: [SYMBOL:SILENCE]
# Line 3221: [SYMBOL:TRADE]
# Line 3230: [SYMBOL:TRAVEL]
# Line 3244: [SYMBOL:TRUTH]
# Line 3257: [SYMBOL:WEALTH]
# Line 3276: [SYMBOL:NAME_BUILDING_TEMPLE]
# Line 3288: [SYMBOL:NAME_BUILDING_KEEP]
# Line 3296: [SYMBOL:NAME_WAR]
# Line 3300: [SYMBOL:NAME_BATTLE]
# Line 3304: [SYMBOL:NAME_SIEGE]
# Line 3310: [SYMBOL:NAME_ROAD]
# Line 3315: [SYMBOL:NAME_TUNNEL]
# Line 3329: [SYMBOL:NAME_BRIDGE]
# Line 3332: [SYMBOL:NAME_WALL]
# Line 3342: [SYMBOL:NAME_BUILDING_TOMB]
# Line 3347: [SYMBOL:NAME_BUILDING_LIBRARY]
# Line 3358: [SYMBOL:NAME_FESTIVAL]
#

Language token

2019-07-03T03:27:12Z

Toxicshadow: /* SYMBOL */ text issue

{{Quality|Exceptional|21:42, 17 May 2015 (UTC)}}
{{av}}

'''Language tokens''' are used within the language_*.txt raw files. Each token is permitted in a specific context.

==WORD==
{| {{prettytable}}
|- bgcolor="#dddddd"
! width="20%" | Token
! width="20%" | Arguments
! width="60%" | Description

|-
| {{text anchor|NOUN}}
|
* singular
* plural
| Begins defining a noun usage of a word.

|-
| {{text anchor|ADJ}}
|
* adjective
| Begins defining an adjective usage of a word.

|-
| {{text anchor|PREFIX}}
|
* prefix
| Begins defining a prefix usage of a word.

|-
| {{text anchor|VERB}}
|
* present first person
* present third person
* [[wikipedia:preterite|preterite]]
* past participle
* present participle
| Defines a verb usage of a word.

|-
| {{text anchor|ADJ_DIST}}
| number 1-7
| Determines what order the adjective being defined comes in when in a string of multiple adjectives.

|-
| {{text anchor|THE_NOUN_SING}}
|
| Lets the singular noun form of the word be used after "the" ("The X of Y", where X is the word with the tag).

|-
| {{text anchor|THE_NOUN_PLUR}}
|
| As above, but with plural ("The Xs of Y").

|-
| {{text anchor|THE_COMPOUND_NOUN_SING}}
|
| Lets the singular noun form of the word be used as part of a compound noun after "the" ("The Z-X of Y").

|-
| {{text anchor|THE_COMPOUND_NOUN_PLUR}}
|
| As above, but with plural ("The Z-Xs of Y").

|-
| {{text anchor|THE_COMPOUND_ADJ}}
|
| Lets the adjective form of the word be used as part of a compound noun after "the" ("The Z-X of Y").

|-
| {{text anchor|OF_NOUN_SING}}
|
| Lets the singular noun form of the word be used after "of" ("The Y of X").

|-
| {{text anchor|OF_NOUN_PLUR}}
|
| As above, but with plural ("The Y of Xs").

|-
| {{text anchor|FRONT_COMPOUND_NOUN_SING}}
|
| Lets the singular noun form of the word be used at the front of a compound noun ("XY", as in surnames).

|-
| {{text anchor|FRONT_COMPOUND_NOUN_PLUR}}
|
| As above, but with plural.

|-
| {{text anchor|REAR_COMPOUND_NOUN_SING}}
|
| Lets the singular noun form of the word be used at the rear of a compound noun ("YX", as in surnames).

|-
| {{text anchor|REAR_COMPOUND_NOUN_PLUR}}
|
| As above, but with plural.

|-
| {{text anchor|FRONT_COMPOUND_ADJ}}
|
| Lets the adjective form of the word be used at the front of a compound noun.

|-
| {{text anchor|REAR_COMPOUND_ADJ}}
|
| As above, but at the rear instead.

|-
| {{text anchor|FRONT_COMPOUND_PREFIX}}
|
| Allows the prefix form to be appended as a prefix to a compound noun.

|-
| {{text anchor|THE_COMPOUND_PREFIX}}
|
| Allows the prefix form to be appended as a prefix to a compound noun following "the".

|-
| {{text anchor|STANDARD_VERB}}
|
| Allows the verb to be used in a compound noun and for its participles to be used as adjectives.
|}

==SYMBOL==
{| {{prettytable}}
|- bgcolor="#dddddd"
! width="20%" | Token
! width="20%" | Arguments
! width="60%" | Description

|-
| {{text anchor|S_WORD}}
|
* WORD
| Specifies the given WORD (defined in #REDIRECT [[language_words.txt]]) as belonging to the symbol being defined. A given word can belong to multiple symbols.
|}

==TRANSLATION==

{| {{prettytable}}
|- bgcolor="#dddddd"
! width="20%" | Token
! width="20%" | Arguments
! width="60%" | Description

|-
| {{text anchor|T_WORD}}
|
* WORD
* translation
| Specifies a translation from a given WORD (defined in language_words.txt) into the language being defined.
|}

==English instead of dwarven language==
You can hack the language files with this regular expression command:

'''<nowiki>:%s/T_WORD:$[A-Z_ -]*$:[^\]]*\]/T_WORD:\1:\L\1]/</nowiki>'''

==See also==
[[40d:Language]] (has expanded explanations of parts of the language system, which seems to still be the same in this version)

{{Category|Modding}}
{{Category|Tokens}}

[[ru:Language token]]

Language token

2019-07-03T03:26:18Z

Toxicshadow: /* SYMBOL */ Creating a page with the vanilla symbols for quick reference

{{Quality|Exceptional|21:42, 17 May 2015 (UTC)}}
{{av}}

'''Language tokens''' are used within the language_*.txt raw files. Each token is permitted in a specific context.

==WORD==
{| {{prettytable}}
|- bgcolor="#dddddd"
! width="20%" | Token
! width="20%" | Arguments
! width="60%" | Description

|-
| {{text anchor|NOUN}}
|
* singular
* plural
| Begins defining a noun usage of a word.

|-
| {{text anchor|ADJ}}
|
* adjective
| Begins defining an adjective usage of a word.

|-
| {{text anchor|PREFIX}}
|
* prefix
| Begins defining a prefix usage of a word.

|-
| {{text anchor|VERB}}
|
* present first person
* present third person
* [[wikipedia:preterite|preterite]]
* past participle
* present participle
| Defines a verb usage of a word.

|-
| {{text anchor|ADJ_DIST}}
| number 1-7
| Determines what order the adjective being defined comes in when in a string of multiple adjectives.

|-
| {{text anchor|THE_NOUN_SING}}
|
| Lets the singular noun form of the word be used after "the" ("The X of Y", where X is the word with the tag).

|-
| {{text anchor|THE_NOUN_PLUR}}
|
| As above, but with plural ("The Xs of Y").

|-
| {{text anchor|THE_COMPOUND_NOUN_SING}}
|
| Lets the singular noun form of the word be used as part of a compound noun after "the" ("The Z-X of Y").

|-
| {{text anchor|THE_COMPOUND_NOUN_PLUR}}
|
| As above, but with plural ("The Z-Xs of Y").

|-
| {{text anchor|THE_COMPOUND_ADJ}}
|
| Lets the adjective form of the word be used as part of a compound noun after "the" ("The Z-X of Y").

|-
| {{text anchor|OF_NOUN_SING}}
|
| Lets the singular noun form of the word be used after "of" ("The Y of X").

|-
| {{text anchor|OF_NOUN_PLUR}}
|
| As above, but with plural ("The Y of Xs").

|-
| {{text anchor|FRONT_COMPOUND_NOUN_SING}}
|
| Lets the singular noun form of the word be used at the front of a compound noun ("XY", as in surnames).

|-
| {{text anchor|FRONT_COMPOUND_NOUN_PLUR}}
|
| As above, but with plural.

|-
| {{text anchor|REAR_COMPOUND_NOUN_SING}}
|
| Lets the singular noun form of the word be used at the rear of a compound noun ("YX", as in surnames).

|-
| {{text anchor|REAR_COMPOUND_NOUN_PLUR}}
|
| As above, but with plural.

|-
| {{text anchor|FRONT_COMPOUND_ADJ}}
|
| Lets the adjective form of the word be used at the front of a compound noun.

|-
| {{text anchor|REAR_COMPOUND_ADJ}}
|
| As above, but at the rear instead.

|-
| {{text anchor|FRONT_COMPOUND_PREFIX}}
|
| Allows the prefix form to be appended as a prefix to a compound noun.

|-
| {{text anchor|THE_COMPOUND_PREFIX}}
|
| Allows the prefix form to be appended as a prefix to a compound noun following "the".

|-
| {{text anchor|STANDARD_VERB}}
|
| Allows the verb to be used in a compound noun and for its participles to be used as adjectives.
|}

==SYMBOL==
{| {{prettytable}}
|- bgcolor="#dddddd"
! width="20%" | Token
! width="20%" | Arguments
! width="60%" | Description

|-
| {{text anchor|S_WORD}}
|
* WORD
| Specifies the given WORD (defined in
#REDIRECT [[language_words.txt]]
) as belonging to the symbol being defined. A given word can belong to multiple symbols.
|}

==TRANSLATION==

{| {{prettytable}}
|- bgcolor="#dddddd"
! width="20%" | Token
! width="20%" | Arguments
! width="60%" | Description

|-
| {{text anchor|T_WORD}}
|
* WORD
* translation
| Specifies a translation from a given WORD (defined in language_words.txt) into the language being defined.
|}

==English instead of dwarven language==
You can hack the language files with this regular expression command:

'''<nowiki>:%s/T_WORD:$[A-Z_ -]*$:[^\]]*\]/T_WORD:\1:\L\1]/</nowiki>'''

==See also==
[[40d:Language]] (has expanded explanations of parts of the language system, which seems to still be the same in this version)

{{Category|Modding}}
{{Category|Tokens}}

[[ru:Language token]]

User talk:Emi

2012-07-15T23:32:29Z

Toxicshadow: /* Symbol Sets (Modding) */

Please leave new messages by pressing the new section button. It is next to the edit button, and says "Add topic". Be sure to sign your message with <nowiki>~~~~</nowiki> so I know who left me the message.
{{archive|*[[User_talk:Emi/archive1|archive 1]]}}

== Empty DF:2012 Articles ==

Hello, I'd like to offer a few suggestions:
* Could the bot which went through and replaced all the v0.31 article links with DF:2012 links be modified to actually create those articles with a <nowiki>{{av}}</nowiki> template inserted, so that users can reference an older version easily while understanding that it could be outdated?
* Could a bot be created to go through all the current dead links and create those articles and place a <nowiki>{{av}}</nowiki> template within them?
* Failing that, I'd be willing to volunteer for this; I understand that I should talk to you for article creation. In that case, would I have to present you with a list of articles to be created?
--[[User:Reilwin|Reilwin]] 02:53, 15 March 2012 (UTC)

:Looks like I can create articles myself after enough edits. --[[User:Reilwin|Reilwin]] 06:35, 3 April 2012 (UTC)

== Spanish translation ==

Hello! I'm a Spanish player of this game and I would like to begin the translation of this wiki into Spanish. I hope you like the idea! Regards.

== PROBLEM ==
since you "upgraded" the wiki, sometimes when i try to load a page, any kind of page in the wiki, instead of loading the page, my browser (chrome) starts downloading a file like this: DF2010-Magma.gz
the file never ends downloading and it contains nothing, so i dont know whats the deal with that, sometime is loads teh page as usual
*Take a look at [http://www.bay12forums.com/smf/index.php?topic=96229.0 this forum thread] - most cases seem to result from using Avast Antivirus along with Google Chrome. --[[User:Quietust|Quietust]] 00:38, 10 February 2012 (UTC)

== Upload Button Missing ==
Hello. I've uploaded [[http://dwarffortresswiki.org/index.php/File:DA_Quarters.JPG,stuff]] before, but the upload link seems to have vanished for me. (I'd like to upload a small .exe file which makes the depot tradeing semi-automated so I can link to it from my user page.) What should I do?

Thanks,
--[[User:DDR|-DDR]] 01:28, 19 February 2012 (UTC)

Update: Oh, so it's just down for a few days? OK, I'll be patient. Thanks for all the work you've done here, Emi. :)

== Eagles ==

Why can't I create new pages? I want to create a page about normal eagles.

: This wiki is going through a lot now. New name space for the latest DF version has been created and articles are copied to it, as far as they are still valid for the new version. Also this wiki's cluster size has been increased by two new servers and many things around it are being configured. So I think the admins just prohibited new article creation for a while until they sort things out. --[[User:Nagidal|Nagidal]] 17:31, 19 February 2012 (UTC)

: I've seen Briss has created the Eagle page, maybe it's so that you can fill it with content. --[[User:Nagidal|Nagidal]] 18:50, 19 February 2012 (UTC)

== a namespace just for me? ==

It says that if i'd like a user page i should post here asking for one.
can i have a namespace for me please? under Zazq? [[User:Zazq|Zazq]] 21:48, 19 February 2012 (UTC)

: A namespace is not the same as a user page. I'm almost sure you can't have a namespace just for you, but you can certainly have your own userpage where you can set up your own sandbox. I have created you your userpage, just click on the link on your name in the signature. You can start forging some good articles on your userpage. --[[User:Nagidal|Nagidal]] 23:46, 19 February 2012 (UTC)

== UserPage ==
could i have a page too? to edit and try stuff before posting ... Edit: it is Mohreb by the way ...

I'd like a user page too, name KevinFragger2427. Thanks.

== v34 Utilities ==

Can we get a [[DF2012:Utilities]] page created?

== Giant sponges ==

Hello, I am new to this wiki and I would like to add articles for giant sponges and giant mosquitoes.

I trust I can just copy-paste the old tags from a DF2010 creature page and change them accordyingly ?

[[User:Naryar|Naryar]] 11:28, 23 February 2012 (UTC)

== Can I have two pages created? ==

I'd like to have two pages created for me, please.

1. I'd like my user-page created, so I can do all the other cool stuff that people do with their user-pages.

2. I would also like a whole new mod article made, please. Title it "Modern Warfare: Year 2100" too, please, as well.

EDIT: Username is UristMcHuman. Sorry I forgot that

== Interactions. ==

I would like a page created under 2012:Interaction, please and thank you. [[User:Lofn|Lofn]] 15:54, 25 February 2012 (UTC)
EDIT: a userpage/sandbox would also be very much appreciated, if you find the time.

== User page for Darchitect. ==

I'd like one, if you'd be so kind.
[[User:Darchitect|Darchitect]] 20:24, 29 February 2012 (UTC)Darchitect

== Favicon Recovery ==

I notice the favicon seems to have gotten lost somewhere along the way. Since I'm the one who initially made it using the main site logo for reference, I still have a copy sitting around. [http://dffd.wimbli.com/images/dfwiki_favicon.ico Here it is, feel free to use it again.]

== Request for User Page ==

Hi there, can you please add a user page for me? Thank you. [[User:Timtek|Timtek]] 11:47, 5 March 2012 (UTC)

== Request for Confirmed User ==

I was wondering what I need to do to be able to upload a file. I registered four days ago, and have been waiting to become an "Autoconfirmed user" so that I can add my tileset to the Tileset repository. The "autoconfirmation" never comes, however. Attempting to google the issue said that I should be autoconfirmed after 3 days, which has not occurred. Am I missing something? --[[User:Taffer|Taffer]] 13:10, 6 March 2012 (UTC)

Hello again! Thanks for the help earlier, and sorry for the second message. Would it be alright if I have a user page? Thank you! --[[User:Taffer|Taffer]] 18:51, 7 March 2012 (UTC)

== Cached Special Pages ==

The wiki currently has [http://www.mediawiki.org/wiki/Manual:$wgMiserMode $wgMiserMode] enabled, resulting in a number of [[Special:SpecialPages|special pages]] having their results cached (by MediaWiki itself) to reduce server load, but there's no cron job to run /maintenance/updateSpecialPages.php and actually update those pages - as a result, they're all 3 months out of date. I've mentioned this at least 3 times on IRC but it still hasn't been fixed. --[[User:Quietust|Quietust]] 20:24, 7 March 2012 (UTC)

== Is the DF2012:Creatures page getting too big for the server? ==

The Creatures page still needs to be updated with the new creatures for the lakes/rivers but when I try to submit or preview tha page I get a blank page and a submitted update is not visible on the page. Is the page simply too big now, or is there some server side changes that can be made to fix this? [[User:Organised chaos|Organised chaos]] 20:18, 13 March 2012 (UTC)
*If you ask me, the Creatures page is currently being done '''all wrong''' - it should only list each creature '''once''' and include the relevant biomes, rather than copy/pasting it for every single biome (and introducing errors when one entry has different values from the others). --[[User:Quietust|Quietust]] 21:00, 13 March 2012 (UTC)

== DFRawFunctions ==

I've got an update for DFRawFunctions (corrects behavior for a few functions and adds new features to some others) which also includes a few new raw files - when you've got a chance, pull 'em from github. In fact, some option to automatically pull updates from github either periodically (once or twice a day) or on demand (e.g. editing a particular wiki page) would be really nice so I won't have to bug you about it. --[[User:Quietust|Quietust]] 18:27, 18 March 2012 (UTC)

== I want to make Korean Wiki. ==

I was looking for administrator to discuss this, but I couldn't find anyone... also, I'm not sure that I should talk it to you. anyway, I leave this here.

I want to make Korean Wiki, There're some Korean fan, but they hardly play the game because of the lack of game information. So I thought They need wiki to know the game. I want to know whether the administrator can found Korean version of this wiki or not.

How can I get the permission about it? Is it needed that something to verify myself to them? I hope I would take a positive answer. --[[User:Tragal|Tragal]] 14:44, 30 March 2012 (UTC)

== Create Redir [[DF2012:Well_guide]] ==

Need a redir or crosslink created from: [[DF2012:Well_guide]] (empty page) -> [[v0.31:Well_guide]]. And/or snap relevant links. --[[User:Kim Bruning|Kim Bruning]] 08:37, 24 April 2012 (UTC)

== Froot wants a userpage too. ==

Hey-lo.
Yet another userpage request.
[[User:Froot|Froot]] 02:08, 1 May 2012 (UTC)

there is no "DF2012 Talk:Cave crocodile", added an my issue about my "Bosa, Cave Crocodile (+trained+)" which cost me about an game-hour lost due to reloading save in the article. Wonder, why there is no "talk" pages for everything by default? There are many cases which need some science before editing articles :(

== Minecarts 101 page? ==

Can we get a "Minecarts 101" page started the same way there are intro pages for things like the military?

Thanks,

[[User:Dhokarena56|Dhokarena56]] 17:25, 14 May 2012 (UTC)dhokarena56

== Page request ==

May I request a userpage?

-Erich

== User page request ==

Hello! I am requesting a userpage. --[[User:Spacer|Spacer]] 15:31, 30 May 2012 (UTC)

== DF2012_Talk:Siege ==

please, create http://dwarffortresswiki.org/index.php/DF2012_Talk:Siege

thanks,

[[User:Kartofius al andalus|Kartofius al andalus]] 17:00, 4 June 2012 (UTC) kartofius

== Wiki in spanish??? ==

How can I create a page for the wiki in spanish?

== add #dwarffortress irc.freenode.net to main page IRC section ==

Hello everyone, could you please add #dwarffortress IRC channel on FReeNode in the main page IRC channel list?
Thank you

== new user page request ==

looking for a user page so I can store my scripts in the wiki.

thanks
vjek

[[User:Vjek|Vjek]] 20:17, 23 June 2012 (UTC)

== new page request ==
Hi
could you add a talk page at the "raw adamantine" article
user: grafsnow

== DF2012:World rejection ==

Hi, I'm trying to write the page for DF2012:World rejection http://dwarffortresswiki.org/index.php/DF2012:World_rejection which has a red link on the Advanced World Generation page but I can't create a new page. Do I need somebody to make it for me? Thanks, Seb. --[[User:SAFry|SAFry]] 19:08, 30 June 2012 (UTC)
:I created it for him. -- [[User:HiEv|Hi]][[User talk:HiEv|Ev]] 02:18, 1 July 2012 (UTC)

== Could I get a page for my mod? ==

I'm currently working on a mod, and I'd really like a page where I can put what the mod is, how you use it, what it includes, etc...
I'm sorry if it looks kinda sketchy that I just created this account today and I'm being vague about the mod Dx
Anyways, if/when you create it, could you title it ''PlayableCiv+''
Thanks:)
[[User:Toxicshadow|Toxicshadow]] 05:30, 1 July 2012 (UTC)

== Arms Industry Page ==

Could you create an "Arms Industry" page for information concerning production of weapons? Alternatively, it could be called "Weapons Industry."

== User Page ==

Would be very glad if i had a user page as a kind of sandbox (and to put some !!science!! stuff up there) [[User:Lorb|Lorb]] 09:53, 7 July 2012 (UTC)

== User Page Request ==

Could you make me a user page?

== Requesting Page Creation for 'Fixed Creatures' ==

There has been some discussion on r/DwarfFortress ([http://www.reddit.com/r/dwarffortress/comments/w8ht8/need_help_my_giant_black_mambas_wont_breed/]) about animals that don't lay eggs that should, eggs that don't hatch due to a missing Tag, and other various issues. I would like to create a space where we can create a list of animals with the values and tags modified to be more accurate. Thanks!--Dragoon209

Edit: I haven't received any word that the pages have been created, and a quick search shows no matches for 'Fixed Creatures'. Is there any information I am missing to start the process? Thanks in advance!
[[User:Dragoon209|Dragoon209]] 18:19, 13 July 2012 (UTC)

: What page titlewould you like? --[[User:Briess|Briess]] 18:26, 13 July 2012 (UTC)

:: How about "DF2012:Fixed_Creature_RAWs"? [[User:Dragoon209|Dragoon209]] 18:34, 13 July 2012 (UTC)

== Outpost Liason ==

I am simply looking for more information about a phenomenon that has happened twice now. An outpost liason came to my fort and asked if I wanted to join their colony. What are the pros and cons of saying either yes or no? Please help!

== Yet Another User Page ==

Just requesting a user page created, to play around in and post some of my own DF-related stuff. Thanks! [[User:MasterShizzle|MasterShizzle]] 17:59, 13 July 2012 (UTC)
:Umm... wow. That was fast! You guys are awesome. [[User:MasterShizzle|MasterShizzle]] 18:12, 13 July 2012 (UTC)

== Symbol Sets (Modding) ==

Can someone create a page for Symbol Sets, as used in Entity files, and found in language_SYM.txt?
[[User:Toxicshadow|Toxicshadow]] 23:32, 15 July 2012 (UTC)

User talk:Emi

2012-07-15T23:30:33Z

Toxicshadow: /* Symbol Sets (Modding) */ new section

v0.34:Position token

2012-07-11T02:57:40Z

Toxicshadow: /* Position Tokens */ Added ALLOWED_CREATURE token's description/args

{{quality|Exceptional|18:14, 28 April 2011 (UTC)}}{{av}}
These tokens define positions in entity_*.txt files. See [[Entity token]].
==Position Tokens==
These tokens belong in an entity definition. These tokens apply to a position (such as monarch) and should follow the [POSITION:POSITION_NAME] token.

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Arguments
! Description

|-
| ACCOUNT_EXEMPT
|
| The position holder is not subjected to the Dwarven Economy.

|-
| ALLOWED_CLASS
| CREATURE_CLASS Token
| Only creatures with the specified class token can be appointed to this position.

|-
| ALLOWED_CREATURE
| CREATURE:CASTE
| Restricts the position to only the defined caste. Only works with a caste of the entity's current race (If the entity had multiple CREATURE: tokens)

|-
| APPOINTED_BY
| position
| The position used as an argument selects creatures to fill the role in question. For example, the GENERAL is [APPOINTED_BY:MONARCH].

|-
| BRAG_ON_KILL
|
| A creature that kills this position will be sure to talk about it a lot.

|-
| CHAT_WORTHY
|
| In adventure mode, when referencing locations an NPC may mention this position holder living there or having done some deed there.

|-
| COLOR
| color
| Creatures of this position will have this colour, instead of their profession colour. e.g. [COLOR:5:0:1]

|-
| COMMANDER
| position:ALL
| This position will act as a commander of the specified position{{verify}}. E.g. GENERAL is [COMMANDER:LIEUTENANT:ALL]. Unknown if values other than ALL work.

|-
| CONQUERED_SITE
|
| This position will be available to creatures when the site has been taken over by another civilisation.

|-
| DEMAND_MAX
| number (0-100)
| How many demands at one time the position can make of the population.

|-
| DETERMINES_COIN_DESIGN
|
| Coins minted will have images that reflect the personality of this position holder.

|-
| DO_NOT_CULL
|
| The position won't be culled during world generation.{{verify}}

|-
| DUTY_BOUND
|
| Members of this position will never agree to 'join' your character during adventure mode.

|-
| ELECTED
|
| The population will periodically select the creature to fill this position.

|-
| EXECUTION_SKILL
| weapon skill
| required for the [RESPONSIBILITY:EXECUTIONS] on which weapon class to use for it

|-
| EXPORTED_IN_LEGENDS
|
| The various members who have filled this role will be listed in the civilisation's history.

|-
| FLASHES
|
| The creature holding this position will flash on the display.

|-
| GENDER
|
*MALE/FEMALE
| The position can only be held by specified gender.

|-
| KILL_QUEST
|
| The position can assign quests to adventurers.

|-
| LAND_HOLDER
| number
| The position will arrive when the LAND_HOLDER_TRIGGER in the entity definition has been met.

|-
| LAND_NAME
| string
| The name the area takes on when under the control of a LAND_HOLDER. E.g. for the DUKE, [LAND_NAME:a duchy]

|-
| MANDATE_MAX
| number (0-100)
| The maximum number of mandates the position can make at once.

|-
| MENIAL_WORK_EXEMPTION
|
| The position cannot be assigned labours, and will generally just lounge around like nobles do. Currently does not actually work. {{bug|3721}}

|-
| MENIAL_WORK_EXEMPTION_SPOUSE
|
| The spouse of the position holder doesn't have to work, either. Also doesn't work either. {{bug|3721}}

|-
| MILITARY_SCREEN_ONLY
|
| The position only shows up in the Military screen.{{verify}}

|-
| NAME
| singular:plural
| The name of the position.

|-
| NAME_MALE
| singular:plural
| If the creature holding the position is male, this is the position's name. E.g. for MONARCH, [NAME_MALE:king:kings]

|-
| NAME_FEMALE
| singular:plural
| If the creature holding the position is female, this is the position's name. E.g. for MONARCH, [NAME_FEMALE:queen:queens]

|-
| NUMBER
|
* number/AS_NEEDED
| How many of the position there should be. If the [SITE] token exists, this is per site, otherwise this is per civilisation.

|-
| PRECEDENCE
| number (0-30000)
| How important the position is in society; a lower number is more important. For MONARCH it's 1, for MILITIA_CAPTAIN it's 200.

|-
| PUNISHMENT_EXEMPTION
|
| The position holder will not be held accountable for his or her crimes. Does not appear to work. {{bug|4589}}

|-
| QUEST_GIVER
|
| The position holder can give quests in Adventurer mode. Functionality in 0.31.13 and later is uncertain.

|-
| REJECTED_CLASS
| CREATURE_CLASS Token
| Creatures of the specified class cannot be appointed to this position.

|-
| REJECTED_CREATURE
| ???
| Unknown - may restrict position holders by CREATURE type.

|-
| REPLACED_BY
| position
| For when one position is a lesser form of another. For example, expedition leader is [REPLACED_BY:MAYOR].

|-
| REQUIRED_BEDROOM
| number (0-1000000)
| The position holder requires a bedroom with at least this value.

|-
| REQUIRED_BOXES
| number (0-100)
| The position holder requires at least this many boxes.

|-
| REQUIRED_CABINETS
| number (0-100)
| The position holder requires at least this many cabinets.

|-
| REQUIRED_DINING
| number (0-1000000)
| The position holder requires a dining room with at least this value.

|-
| REQUIRED_OFFICE
| number (0-1000000)
| The position holder requires an office with at least this value.

|-
| REQUIRED_RACKS
| number (0-100)
| The position holder requires at least this many weapon racks.

|-
| REQUIRED_STANDS
| number (0-100)
| The position holder requires at least this many armour stands.

|-
| REQUIRED_TOMB
| number (0-1000000)
| The position holder requires a tomb with at least this value.

|-
| REQUIRES_POPULATION
| number
| The position requires the population to be at least this number before it becomes available or before the position holder will move in.

|-
| RESPONSIBILITY
| responsibility
| See the table below for the available responsibility tokens. E.g. [RESPONSIBILITY:TAME_EXOTICS]

|-
| RULES_FROM_LOCATION
|
| Unknown{{verify}}

|-
| SITE
|
| The civilisation will attempt to have this position separate for each site.

|-
| SLEEP_PRETENSION
|
| The position holder will get upset if someone with a higher precedence holds quarters with a greater value than their own.

|-
| SPOUSE
| singular:plural
| The name of the position holder's spouse.

|-
| SPOUSE_FEMALE
| singular:plural
| If the spouse of the creature holding the position is female, this is the spouse's position name.

|-
| SPOUSE_MALE
| singular:plural
| If the spouse of the creature holding the position is male, this is the spouse's position name.

|-
| SQUAD
| number:singular:plural
| The position holder will be accompanied by this many whatevers; e.g. for HAMMERER, [SQUAD:10:royal guard:royal guards]

|-
| SUCCESSION
|
* BY_HEIR / BY_POSITION:position
| How a new position holder is chosen.

|}

== Responsibilities ==
{| {{prettytable}}
|- bgcolor="#dddddd"
! Argument
! Description

|-
| ACCOUNTING
| Found on bookkeeper. Position will keep track of stocks.

|-
| ATTACK_ENEMIES
| Found on elven ranger captain and human warrior. Effect{{verify}}

|-
| BUILD_MORALE
| Found on champion. Effect{{verify}}

|-
| COLLECT_TAXES
| Not found anywhere in game; has no effect.

|-
| EQUIPMENT_MANIFESTS
| Not found anywhere in game; has no effect.

|-
| ESCORT_TAX_COLLECTOR
| Found on hammerer. Position will accompany the COLLECT_TAXES position during tax collection.

|-
| ESTABLISH_COLONY_TRADE_AGREEMENTS
| Found on outpost liaison. Position will make trade agreements with the civilisation's colonies.

|-
| EXECUTIONS
| Found on hammerer. Position will deliver beatings for great justice.

|-
| HEALTH_MANAGEMENT
| Found on chief medical dwarf. Enables the {{key|z}} menu health screen. Other effect{{verify}}

|-
| LAW_ENFORCEMENT
| Found on sheriff/captain of the guard. Position is in charge of imprisoning criminals.

|-
| LAW_MAKING
| Found on monarch/landholders. Effect{{verify}}

|-
| MAKE_INTRODUCTIONS
| Found on diplomat. Effect{{verify}}

|-
| MAKE_PEACE_AGREEMENTS
| Found on diplomat. Will request peace treaties in order to end wars.

|-
| MAKE_TOPIC_AGREEMENTS
| Found on diplomat. Will make various types of agreements when visiting - tree cutting quotas (for Elves) or simply "such a nice place you've carved out for yourselves".

|-
| MANAGE_PRODUCTION
| Found on manager. Position will verify work orders.

|-
| MEET_WORKERS
| Found on expedition leader/mayor. Dwarves want one of these around to complain to.

|-
| MILITARY_GOALS
| Found on monarch/landholder/leaders. Effect{{verify}}

|-
| MILITARY_STRATEGY
| Found on general/militia commander. During worldgen, position will go on expeditions to tame exotic creatures.

|-
| PATROL_TERRITORY
| Found on elven ranger captain and human warrior. Effect{{verify}}

|-
| RECEIVE_DIPLOMATS
| Found on monarch/landholder/leaders. Position will hold meetings with incoming diplomats/liaisons.

|-
| RELIGION
| Found on elven druid. Possibly it's the one who can tell you information about worship cults{{verify}}

|-
| SORT_AMMUNITION
| Not found anywhere in game; has no effect.

|-
| TAME_EXOTICS
| Not found anywhere in game; has no effect.

|-
| TRADE
| Found on broker. Position will trade at the depot when set to broker only. When applied to other civilizations, the position will arrive with the caravan to make trade agreements.

|-
| UPGRADE_SQUAD_EQUIPMENT
| Not found anywhere in game; has no effect.

|}

== Related Tokens ==
The following two ENTITY tokens are not actually position tokens, but bear mentioning on this page because they can modify the way that a civilization's positions behave:

{| {{prettytable}}
|- bgcolor="#dddddd"
! Token
! Arguments
! Description

|-
| LAND_HOLDER_TRIGGER
|
* land holder number
* population
* wealth exported
* created wealth
| Defines when a particular land-holding noble (baron, count, duke in vanilla) will arrive at a fortress.

|-
| VARIABLE_POSITIONS
| Position responsibility or ALL
| Allows a responsibility to be taken up by a dynamically generated position (such as Law-maker).

|}

== Why Won't My Positions Appear? ==
The way DF determines what positions will actually ''appear'' in your fortress is somewhat counterintuitive and fairly limiting. This guide should help you understand what you can do to actually get your positions working properly.

There are five tokens governing which positions appear in your fortress - LAND_HOLDER, REQUIRES_POPULATION, APPOINTED_BY, ELECTED, and REPLACED_BY. The first two determine when your fortress is eligible for a new position, the next two determine how a new position for which your fortress is eligible can be added, and the fifth allows you to clear up obsolete positions. Unfortunately, they also interact in some strange ways that makes creating interesting position structures difficult.

When you start a new fortress, DF compiles a list of your initial positions. To do this, it looks at the requirements for each position - any position whose only requirement is less than seven dwarves (either because they have no requirement tokens, or because their only requirement tokens are [REQUIRES_POPULATION: =< 7] or [LAND_HOLDER:some trigger whose only requirement is some number of dwarves equal to or less than 7]). Most importantly, ''any'' position whose only requirement is a LAND_HOLDER requirement, regardless of what the trigger for that requirement is, will be added if another eligible starting position is REPLACED_BY it. '''A non-LAND_HOLDER position that is REPLACED_BY a LAND_HOLDER position will never appear.''' With this list compiled, the game culls all positions that are REPLACED_BY another eligible position, and then culls all positions that have the APPOINTED_BY token. '''You may not embark with any appointed positions.''' Any remaining positions are then filled by a dwarf chosen at random.

'''Positions do not automatically appear when you reach their requirements.''' For example, if you remove the ELECTED token from the Mayor, then the Mayor will never appear, even once you reach his required number of dwarves. '''For a position that does not appear at embark to appear in your fortress, it must be APPOINTED_BY another position or ELECTED.'''

Naturally, this is more complicated than it looks. '''APPOINTED_BY positions must be appointed by another position already in your fortress, or a civ-level position. Only LAND_HOLDER positions may be appointed by civ-level positions.''' LAND_HOLDER positions that are APPOINTED_BY civ-level positions are inherently tied to civ-level tokens with the ESTABLISH_COLONY_TRADE_AGREEMENTS responsibility. If a fortress meets the LAND_HOLDER_TRIGGER for a new LAND_HOLDER tier when a caravan leaves, then the next time the outpost liaison or equivalent arrives, he will offer to make you an official colony, which will allow you to select all positions for that LAND_HOLDER level. '''Each time he appears, the outpost liaison will only promote your fortress one tier up the LAND_HOLDER track.''' The biggest problem with this system is that you may set your LAND_HOLDER_TRIGGERS such that you are eligible for the first tier of LAND_HOLDER positions at embark. '''If you are eligible for the first tier of LAND_HOLDER positions at embark, then all first-tier positions will appear twice - once at embark, and again when the outpost liaison comes to appoint you to the first tier.'''

{{Category|Modding}}
{{Category|Tokens}}

v0.34:Modding guide

2012-07-01T18:04:27Z

Toxicshadow: /* Plants */ Added plant guide, still could use some work, and right now isn't very usefull

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

This is intended to be a guide to inform those new to DF modding on what elements of the game can be modified, and how. After reading through this guide, a user should be capable of editing creatures, entities, materials ''et al'', and creating their own.

Generally, breaking stuff is fine - nothing that can be changed will affect the DF executable, and new additions can be easily removed.

This guide is based on [[40d:Modding guide|Teldin's guide]], originally created for version 0.27.176.39c. Per wiki tradition, it has been updated through all the major releases since then; hopefully it reflects current knowledge.

'''See also:''' [[:Category:DF2012:Modding]]

= Modding Guide =

== Basics of DF modding ==

All the base data that can be edited by prospective modders can be found in the \raw\ folder. This folder contains two subfolders: "graphics" (where you insert [[Graphics set repository|graphics sets]]), and "objects", which contains all the data for generally everything in the game that is not hardcoded.

Within the \raw\objects folder are a large number of text files - these are the [[raw file|raw files]], and editing them is quite easy - you can also create your own if you wish. For now, take a look at one of the existing files. It should look something like this:

creature_standard

[OBJECT:CREATURE]

[CREATURE:DWARF]
[DESCRIPTION:A short, sturdy creature fond of drink and industry.]
[NAME:dwarf:dwarves:dwarven]
[CASTE_NAME:dwarf:dwarves:dwarven]
[CREATURE_TILE:1][COLOR:3:0:0]
[CREATURE_SOLDIER_TILE:2]
...

As you can see, each file comprises a header string stating the file name, a second header stating the type of object data it contains, followed by the contents of the file itself. These are all necessary elements of the file, and without them, the file won't be parsed correctly by the game. You may have also noticed the file naming scheme - this is also important; files containing creatures have names starting with "creature_", entity file names must begin with "entity_", etc..

Below the headers, there begins a list of entries. Each entry is made up of its own header (in this case, "[CREATURE:DWARF]"), again stating the type of object, and then the object's unique identifier - if an indentifier isn't unique, the game will mess up and you'll get some serious, and potentially very trippy, errors. Below that, we have the body of the entry, which determines the entry's specific properties.

The body of an entry is made up of a series of "tokens", which are essentially flags that can be added or removed to affect the entry's attributes. Most of these effects are hardcoded: for example, it's possible to make a creature only eat meat with the [CARNIVOROUS] token, but it's impossible to create your own token detailing a specific diet for the creature.

Before we continue, a few key things to remember when modding the raw files:

* Try to avoid modifying the existing raw files when adding objects. It makes removing mods far easier.
* If you want to edit an already-existing creature, always back up the files you plan on editing to a different location. Since v0.31.22, the game no longer loads backup files, but duplicate entries are still a very bad thing.
* When a new world is generated, all the raw files get copied into a \raw\ folder within the applicable save folder. If you want to change something within a world that's already been generated, you'll have to edit those files, not the ones in ~DF\raw\objects.
* There's nothing stopping you from just copying an existing creature/entity/whatever, changing the identifier, and modifying it. This can save you a lot of time, especially when it comes to entities... which are coincidentally what we'll be talking about next.

== Modding civilizations (entities) ==

Entities - the objects that determine how civilisations work - are stored in entity_default.txt (though, like all other files, you may add more). They follow the same format as any other raw file:

entity_default

[OBJECT:ENTITY]

[ENTITY:ENTITYNAME]
[CREATURE:CREATURETYPE]
[TRANSLATION:LANGUAGETYPE]
[BIOME_SUPPORT:BIOMETOKEN:FREQENCY]
...[OTHER TAGS]...

Most of the time, it doesn't matter which order these tokens are in or where they're placed so long as they're below the "ENTITY:" identifier, but there are some important exceptions in the case of other files, especially creatures, which can contain a lot of "nested" tokens.

"[CREATURE:]" links the civilization with a specific creature defined in a creature file. This is the creature that'll be making up the entity's population, and will therefore be the creature you'll be playing as in fortress or adventure mode if the entity is a playable one. For example, if you wanted to do something silly, you could switch the "CREATURE:DWARF" entry in entity_default.txt with "CREATURE:ELF" and you would be marching elves around in fortress mode, although they would still use dwarven technology and language and names and so forth.

Oh, and before you get any funny ideas - it ''is'' possible to define more than one creature for a civ, but that won't work in quite the way you probably expect: later on, in the creature section, you'll learn about castes, which will provide a much more viable alternative, so try to bear with us until then.

"[TRANSLATION:]" defines the language file that the entity will be using, which will determine what their untranslated words are for things. This doesn't determine which words they use for naming things, only the way those words are spelt. The default language files are HUMAN, DWARF, ELF, and GOBLIN.

"[BIOME_SUPPORT:]" defines the biomes that civs will attempt to settle in. The "FREQUENCY" value determines the likelyhood of them building there, but also raises an important point: most of the values you'll be setting for things are relative to each other. If one was to type:

[BIOME_SUPPORT:ANY_FOREST:1]
[BIOME_SUPPORT:SAVANNA:2]

This would have very much the same effect as:

[BIOME_SUPPORT:ANY_FOREST:5]
[BIOME_SUPPORT:SAVANNA:10]

This holds true for a lot of values throughout the files, excluding when it simply doesn't make sense, such as in materials.

You can find many details about the rest of the civilization tokens [[entity token|here]]. Besides those mentioned, some fundamental ones are the CIV_CONTROLLABLE token, which lets you control the civ in fortress mode, the INDIV_CONTROLLABLE token, which allows you to play the civ in adventure mode as an outsider, and the ADVENTURE_TIER token, which allows you to play a civ native (non-outsider) in adventure mode. Other tokens that you should pay attention to are START_BIOME and the ones regarding sites, but in general, you can just run through the aformentioned list and add or remove what you want.

If you have more than one civ with the CIV_CONTROLLABLE token, all the available civs from those entities will appear in the group selection section on the embark screen. It may not be immediately obvious from which species each civ may be - while this can be determined from legends mode, the topmost species in the "neighbors" display in the embark screen is always the same as the currently selected species; if your group is dwarven, dwarves will be topmost, whilst (say) elves will be topmost if your chosen group is elven. By default, the game seems to choose a civ (and therefore a species if there is more than one) at random.

You can also attempt to discern the civ yourself by the names it uses - this is the realm of "symbols", collections of words centered around a specific concept. The civ will use the words comprising whatever symbols are applicable to it for various things. This association might be a little obfuscating at first, so I'll run through it. Let's refer to the DWARF entity:

[SELECT_SYMBOL:WAR:NAME_WAR]
[SUBSELECT_SYMBOL:WAR:VIOLENT]
[SELECT_SYMBOL:BATTLE:NAME_BATTLE]
[SUBSELECT_SYMBOL:BATTLE:VIOLENT]
[SELECT_SYMBOL:SIEGE:NAME_SIEGE]
[SUBSELECT_SYMBOL:SIEGE:VIOLENT]

Here we can see that dwarves will generally name their wars first after words in the "NAME_WAR" symbol group, and then after words in the "VIOLENT" symbol group. This might, for example, result in a war being named "The War of Carnage". The symbols used for the other types of conflict are arrayed in a similar fashion. It would be trivial to replace the instances of VIOLENT with, say, PEACE and end up with a battle called "The Clash of Calm" or something.

[SELECT_SYMBOL:ROAD:NAME_ROAD]
[SELECT_SYMBOL:TUNNEL:NAME_TUNNEL]
[SELECT_SYMBOL:BRIDGE:NAME_BRIDGE]
[SELECT_SYMBOL:WALL:NAME_WALL]

The above applies here. Dwarves are fond of naming their roads and tunnels after roads and tunnels.

[SELECT_SYMBOL:REMAINING:ARTIFICE]
[SELECT_SYMBOL:REMAINING:EARTH]
[CULL_SYMBOL:ALL:DOMESTIC]
[CULL_SYMBOL:ALL:SUBORDINATE]
[CULL_SYMBOL:ALL:EVIL]
[CULL_SYMBOL:ALL:UNTOWARD]
[CULL_SYMBOL:ALL:FLOWERY]
[CULL_SYMBOL:ALL:NEGATIVE]
[CULL_SYMBOL:ALL:UGLY]
[CULL_SYMBOL:ALL:NEGATOR]

This section deals with everything else. The things that haven't already been dealt with (hence the "REMAINING") - such as site names, kingdom names, the names of individuals, and such - will have names from the ARTIFICE and EARTH symbol groups. After that the dwarf entity is told to cull all innapropriate symbols - this applies to everything (hence the "ALL") so if the game happens to choose a symbol associated with, say, EVIL for one of the battles, it'll scrap that name and try again. This sort of thing adds a lot of flavour to DF's entities and can account for a lot of a civ's percieved personality.

Another basic thing to note: any entity token that's dealing with weapons, armor, clothing, etc., will state the items that the civ can build natively, not necessarily the ones they can wear or use. For example, you could create a species with no clothes specified, but then rob a clothes shop in adventurer mode and wear everything you want, or give them weapons that are too large to wield and they could sell them, but not use them.

An easy method of creating a civilization is just to copy-paste a similar one to the bottom of the entity_default.txt file and edit things to your liking. Remember to always change the civ's "ENTITY:" identifier! This can be anything so long as it's not already existing.

At the end of some of the default entries you'll find a list of positions, both ones that'll directly affect you in fort mode (such as nobles) and ones that'll primarily affect worldgen and adventure mode. A list of the tokens applicable to positions can be found [[position token|here]]; they don't require a great deal of explaination.

== Modding the creatures ==

Creature modding is great fun. You can change nearly any aspect of a creature or make your own completely from scratch.

Modding creatures is very similar to modding civs: it's just a matter of editing, adding, or removing tokens, enclosed in square brackets underneath the creature's [CREATURE:] header. The creature entries contain all of the information about each and every non-random creature in the game, from animals to dwarves to goblins to even caravan wagons. A lot of the creature tokens are fairly self-explanatory; you can find a list of such tokens [[creature token|here]]. But before you start creating your own creatures, you'll want to learn how the tissues system works.

=== Creature materials and tissues ===

In the most basic sense, a creature is a series of bodyparts. These parts are defined in their own file, and we'll talk about them later. As a specific aspect of how creatures work which throws off a lot of prospective modders is the relationship between bodyparts, tissues, and materials. We're going to show you part of the creature entry for a bronze colossus (bear with us):

...
[BODY:HUMANOID:2EYES:2EARS:NOSE:HUMANOID_JOINTS:5FINGERS:5TOES]
[NO_THOUGHT_CENTER_FOR_MOVEMENT]
[TISSUE:BRONZE]
[TISSUE_NAME:bronze:bronze]
[TISSUE_MATERIAL:INORGANIC:BRONZE]
[MUSCULAR]
[FUNCTIONAL]
[STRUCTURAL]
[RELATIVE_THICKNESS:1]
[CONNECTS]
[TISSUE_SHAPE:LAYER]
[TISSUE_LAYER:BY_CATEGORY:ALL:BRONZE]
...

At the top, we can see the "BODY:" token, followed by a list of bodyparts. As you've probably guessed, these parts make up the physical form of the colossus. But the colossus has to be made out of something - it has to have tissues. And those tissues also have to be made out of something - in this case, bronze.

Below the BODY token you'll see a TISSUE token, followed by an identifier, much like the others we've seen. The TISSUE block is determining how the tissue works, and which purposes it'll serve. As the colossus is just going to be made out of this one tissue, this tissue needs to act like bone, muscle, and everything else combined, hence the MUSCULAR, FUNCTIONAL and STRUCTURAL tokens. The tissue also references a material - INORGANIC:BRONZE - the properties of which are declared in the inorganic materials file, and the tissue is subsequently made out of this material. With us so far?

Below the tissue definition is the TISSUE_LAYER line. TISSUE_LAYER allows you to control where each tissue is applied. Its first argument defines if it's to search by bodypart category (BY_CATEGORY), bodypart type (BY_TYPE), or look for a specific part (BY_TOKEN). That's followed by the parts argument itself, which is in this case ALL (so the game's looking for parts in all categories, which is to say, every bodypart). This is followed by the tissue to be applied, BRONZE. So the TISSUE_LAYER token is telling the game to select all bodyparts in every category and make them out of the tissue "BRONZE". The colossus is now made of bronze.

By now you're probably thinking "Wow, if this was for a creature made out of however many tissues, this would be amazingly longwinded". And you're right. Luckily, there are two methods by which we can speed things up a lot.

Firstly, there are material and tissue templates. Let's say you were going to make a lot of creatures out of bronze, and you didn't want to have to copy and paste the bronze tissue all over the place. Instead, you create a tissue template. This goes, as you've probably guessed, in a tissue template file.

[TISSUE_TEMPLATE:BRONZE_TEMPLATE]
[TISSUE_NAME:bronze:bronze]
[TISSUE_MATERIAL:INORGANIC:BRONZE]
[MUSCULAR]
[FUNCTIONAL]
[STRUCTURAL]
[RELATIVE_THICKNESS:1]
[CONNECTS]
[TISSUE_SHAPE:LAYER]

Now, instead of applying the tissue to each and every bronze creature you're making, you can just refer to the template:

...
[BODY:HUMANOID:2EYES:2EARS:NOSE:HUMANOID_JOINTS:5FINGERS:5TOES]
[NO_THOUGHT_CENTER_FOR_MOVEMENT]
[USE_TISSUE_TEMPLATE:BRONZE:BRONZE_TEMPLATE]
[TISSUE_LAYER:BY_CATEGORY:ALL:BRONZE]
...

Material templates work in the same way, but refer to materials instead of tissues.

However, if we're looking at something like a dwarf, even with the templates, editing can get very slow indeed:

...
[USE_MATERIAL_TEMPLATE:SKIN:SKIN_TEMPLATE]
[USE_MATERIAL_TEMPLATE:FAT:FAT_TEMPLATE]
[USE_MATERIAL_TEMPLATE:MUSCLE:MUSCLE_TEMPLATE]
[USE_MATERIAL_TEMPLATE:BONE:BONE_TEMPLATE]
[USE_MATERIAL_TEMPLATE:CARTILAGE:CARTILAGE_TEMPLATE]
[USE_MATERIAL_TEMPLATE:HAIR:HAIR_TEMPLATE]
[USE_MATERIAL_TEMPLATE:TOOTH:TOOTH_TEMPLATE]
[USE_MATERIAL_TEMPLATE:EYE:EYE_TEMPLATE]
[USE_MATERIAL_TEMPLATE:NERVE:NERVE_TEMPLATE]
[USE_MATERIAL_TEMPLATE:BRAIN:BRAIN_TEMPLATE]
[USE_MATERIAL_TEMPLATE:LUNG:LUNG_TEMPLATE]
[USE_MATERIAL_TEMPLATE:HEART:HEART_TEMPLATE]
[USE_MATERIAL_TEMPLATE:LIVER:LIVER_TEMPLATE]
[USE_MATERIAL_TEMPLATE:GUT:GUT_TEMPLATE]
[USE_MATERIAL_TEMPLATE:STOMACH:STOMACH_TEMPLATE]
[USE_MATERIAL_TEMPLATE:PANCREAS:PANCREAS_TEMPLATE]
[USE_MATERIAL_TEMPLATE:SPLEEN:SPLEEN_TEMPLATE]
[USE_MATERIAL_TEMPLATE:KIDNEY:KIDNEY_TEMPLATE]
[USE_TISSUE_TEMPLATE:SKIN:SKIN_TEMPLATE]
[USE_TISSUE_TEMPLATE:FAT:FAT_TEMPLATE]
[USE_TISSUE_TEMPLATE:MUSCLE:MUSCLE_TEMPLATE]
...

This is where body detail plans come in. Detail plans, of course, have their own file, and they are designed to help automate some of the more common processes in creature creation. The first entry in b_detail_plan_default.txt does exactly what we've been trying to do above: it takes all the common materials and shoves them into one plan, which can be referenced with a single token.

...
[BODY_DETAIL_PLAN:STANDARD_MATERIALS]
...

Much easier. But what about the TISSUE_LAYER tokens? Will we have to type out all of those manually?

Nope, detail plans have that covered as well. It's possible to place variable arguments into a detail plan. For example:

[BODY_DETAIL_PLAN:VERTEBRATE_TISSUE_LAYERS]
[BP_LAYERS:BY_CATEGORY:BODY:ARG3:50:ARG2:5:ARG1:1]
[BP_LAYERS:BY_CATEGORY:BODY_UPPER:ARG3:50:ARG2:5:ARG1:1]
[BP_LAYERS:BY_CATEGORY:BODY_LOWER:ARG3:50:ARG2:5:ARG1:1]
[BP_LAYERS:BY_CATEGORY:ARM:ARG4:25:ARG3:25:ARG2:5:ARG1:1]
[BP_LAYERS:BY_CATEGORY:ARM_UPPER:ARG4:25:ARG3:25:ARG2:5:ARG1:1]
...
[BP_LAYERS:BY_CATEGORY:NOSE:ARG5:4:ARG1:1]
...

First an argument is placed in the plan (ARG1, ARG2 etc.), followed by the thickness of the tissue that will be inserted in place of the argument. So when we reference the VERTEBRATE_TISSUE_LAYERS plan, we'll be able to do something like this:

[BODY_DETAIL_PLAN:VERTEBRATE_TISSUE_LAYERS:SKIN:FAT:MUSCLE:BONE:CARTILAGE]

ARG1 in the detail plan is replaced by SKIN, the first tissue we entered. ARG2 is replaced by FAT, ARG3 by muscle, ARG4 by bone, and ARG5 by CARTILAGE. Hence, our creature's bodypart designated as BODY is made up of SKIN with thickness 1, FAT with thickness 5, and MUSCLE with thickness 50. Its nose is made up of SKIN (thickness 1) and CARTILAGE (thickness 4).

Things left out of the body plans aside, our dwarf's entire body, material, tissue and tissue layer tokens have been boiled down to this:

...
[BODY:HUMANOID:2EYES:2EARS:NOSE:2LUNGS:HEART:GUTS:ORGANS:HUMANOID_JOINTS:
THROAT:NECK:SPINE:BRAIN:SKULL:5FINGERS:5TOES:MOUTH:FACIAL_FEATURES:TEETH:RIBCAGE]
[BODY_DETAIL_PLAN:STANDARD_MATERIALS]
[BODY_DETAIL_PLAN:STANDARD_TISSUES]
[BODY_DETAIL_PLAN:VERTEBRATE_TISSUE_LAYERS:SKIN:FAT:MUSCLE:BONE:CARTILAGE]
...

This can save you a lot of time and space if you're making lots of changes common to many creatures. In general, if you're making a creature that's fleshy or chitinous, there's detail plans already included in the game to help you out. You should only have to resort to declaring tissues individually (like our bronze colossus) if you're doing something really out-of-the-ordinary.

Another great thing about templates (and so, detail plans) is that they can be modified after being declared. Let's say we wanted our dwarves to be perpetually on fire (don't ask). We declare the body stuff normally:

...
[BODY:HUMANOID:2EYES:2EARS:NOSE:2LUNGS:HEART:GUTS:ORGANS:HUMANOID_JOINTS:
THROAT:NECK:SPINE:BRAIN:SKULL:5FINGERS:5TOES:MOUTH:FACIAL_FEATURES:TEETH:RIBCAGE]
[BODY_DETAIL_PLAN:STANDARD_MATERIALS]
[BODY_DETAIL_PLAN:STANDARD_TISSUES]
[BODY_DETAIL_PLAN:VERTEBRATE_TISSUE_LAYERS:SKIN:FAT:MUSCLE:BONE:CARTILAGE]
...

We then select the appropriate material:

...
[BODY:HUMANOID:2EYES:2EARS:NOSE:2LUNGS:HEART:GUTS:ORGANS:HUMANOID_JOINTS:
THROAT:NECK:SPINE:BRAIN:SKULL:5FINGERS:5TOES:MOUTH:FACIAL_FEATURES:TEETH:RIBCAGE]
[BODY_DETAIL_PLAN:STANDARD_MATERIALS]
[BODY_DETAIL_PLAN:STANDARD_TISSUES]
[BODY_DETAIL_PLAN:VERTEBRATE_TISSUE_LAYERS:SKIN:FAT:MUSCLE:BONE:CARTILAGE]
[SELECT_MATERIAL:SKIN]
[MAT_FIXED_TEMP:10600]
...

We don't want them burning to death, so we'll need to stop that from happening:

...
[BODY:HUMANOID:2EYES:2EARS:NOSE:2LUNGS:HEART:GUTS:ORGANS:HUMANOID_JOINTS:
THROAT:NECK:SPINE:BRAIN:SKULL:5FINGERS:5TOES:MOUTH:FACIAL_FEATURES:TEETH:RIBCAGE]
[BODY_DETAIL_PLAN:STANDARD_MATERIALS]
[BODY_DETAIL_PLAN:STANDARD_TISSUES]
[BODY_DETAIL_PLAN:VERTEBRATE_TISSUE_LAYERS:SKIN:FAT:MUSCLE:BONE:CARTILAGE]
[SELECT_MATERIAL:SKIN]
[MAT_FIXED_TEMP:10600]
[SELECT_MATERIAL:ALL]
[HEATDAM_POINT:NONE]
...

Note that this makes use of DF's built-in temperature scale. You can read more about that [[Temperature|on this page]]. We're also referencing material tokens, which we haven't gone over yet - we'll talk about making your own materials later.

=== Creature castes ===

Another potentially extremely powerful part of the creature raws is the caste system. The caste system handles both true biological castes and lesser variations, such as sexes.

To understand the true potential of the caste system, we only need to take a look at the raws for antmen, found in creature_subterrenean.txt:

...
[CASTE:WORKER]
[CASTE_NAME:worker ant woman:worker ant women:worker ant woman]
Female, but non-breeding.
[POP_RATIO:10000]
[CASTE:SOLDIER]
[CASTE_NAME:soldier ant woman:soldier ant women:soldier ant woman]
Female, but non-breeding.
[POP_RATIO:1000]
[CASTE:DRONE]
[MALE]
[CASTE_NAME:drone ant man:drone ant men:drone ant man]
[POP_RATIO:5]
[CASTE:QUEEN]
[FEMALE]
[CASTE_NAME:queen ant woman:queen ant women:queen ant woman]
[POP_RATIO:1]
[SELECT_CASTE:WORKER]
[SELECT_ADDITIONAL_CASTE:SOLDIER]
[SELECT_ADDITIONAL_CASTE:QUEEN]
[BODY:HUMANOID_4ARMS:2EYES:HEART:GUTS:BRAIN:MOUTH]
[BODYGLOSS:INSECT_UPPERBODY:INSECT_LOWERBODY]
[SELECT_CASTE:DRONE]
[BODY:HUMANOID_4ARMS:2EYES:HEART:GUTS:BRAIN:MOUTH:2WINGS]
[BODYGLOSS:INSECT_UPPERBODY:INSECT_LOWERBODY]
[FLIER]
[SELECT_CASTE:ALL]
[BODY_DETAIL_PLAN:CHITIN_MATERIALS]
[BODY_DETAIL_PLAN:CHITIN_TISSUES]
[BODY_DETAIL_PLAN:EXOSKELETON_TISSUE_LAYERS:CHITIN:FAT:MUSCLE]
[BODY_DETAIL_PLAN:STANDARD_HEAD_POSITIONS]
[ATTACK:PUNCH:BODYPART:BY_TYPE:GRASP]
[ATTACK_SKILL:GRASP_STRIKE]
[ATTACK_VERB:punch:punches]
...

It's evident that the process of creating and editing castes is comparable to the modifications we were making to tissues and materials earlier: A caste is declared, and modifications to the base creature are made. Declared castes can be selected and subsequently modified, again, just like tissues and materials.

In this case, each caste is declared, given its own name, and a POP_RATIO, which determines how commonly a birth results in that caste - for every 10000 workers born, there'll be an average of 1000 soldiers, 5 drones and one queen. You've probably also noticed that the DRONE and QUEEN castes have the MALE and FEMALE tokens respectively - these tokens determine how breeding works. A creature without both a MALE caste and a FEMALE caste will be unable to breed (no asexual creatures yet, unfortunately). As they lack FEMALE, the workers and soldiers are unable to breed with the male drones.

After this, there are some modifications to bodyparts. In this case, the drones have wings and the FLIER token, which the other castes lack. It's entirely possible for creatures of different castes to have completely different body stuctures, even to the extent that they don't resemble each other at all. If you read the section of this guide that dealt with entities, you may remember a passing mention of multi-creature civilisations and how they don't quite work as you may think they would. The castes system is your workaround. You could create a caste that is, for all intents and purposes, a human, and another caste of the same creature that acts exactly like a giant cave spider, put the creature in a civ, and get a human-spider civ. The only flaw in this approach is that the castes will interbreed.

That's the most complex components of creature creation out of the way. You should find the rest trivial by comparison.

== Modding items ==

Items are fairly simple to deal with. By default, each item type is contained in its own file; this may help make browsing for a specific item easier, but from a purely technical point of view, it's possible to throw all items into one file. Unfortunately, item tokens don't seem to be especially well-documented (at least as not as well as the other object types), but you should be able to figure out most things by way of our explainations and your assumptions.

Let's look at the entry for, of course, the thong:

[ITEM_PANTS:ITEM_PANTS_THONG]
[NAME:thong:thongs]
[LAYER:UNDER]
[COVERAGE:25]
[LAYER_SIZE:10]
[LAYER_PERMIT:30]
[MATERIAL_SIZE:1]
[SOFT]
[LEATHER]
[STRUCTURAL_ELASTICITY_WOVEN_THREAD]

Most of these are pretty obvious if one compares them to the other entries in the file. There's a layer for the item, determining where it's worn; a coverage value to determine how well it protects you from cold and other things; a size token to determine how much it counts for when it's under something else; a layer permit token to determine how much can be worn under it; and a material size token to determine how much raw material it takes to make it.

Now, if you wanted to mod these to turn them into metal thongs (ouch!), you would simply have to add [METAL] to it somewhere. Simple! These tokens work by tying into material properties - some materials are designated as suitable for making hard items, some for soft, etc..

Weapons involve a little more detail:

[ITEM_WEAPON:ITEM_WEAPON_SWORD_2H]
[NAME:two-handed sword:two-handed swords]
[SIZE:900]
[SKILL:SWORD]
[TWO_HANDED:67500]
[MINIMUM_SIZE:62500]
[MATERIAL_SIZE:5]
[ATTACK:EDGE:100000:8000:slash:slashes:NO_SUB:1250]
[ATTACK:EDGE:50:4000:stab:stabs:NO_SUB:1000]
[ATTACK:BLUNT:100000:8000:slap:slaps:flat:1250]
[ATTACK:BLUNT:100:1000:strike:strikes:pommel:1000]

SIZE determines how heavy the weapon is. This has a substantial effect on weapon effectiveness. SKILL determines which skill is used in using the weapon; a list of skills can be found [[skill token|on this page]]. MINIMUM_SIZE determines the minimum size a creature must be before the weapon can be wielded, while TWO_HANDED determines how large a creature must be in order to wield the weapon with one hand.

Attacks take a little more explaination. The first value determines the contact area of the weapon's attack; this should be high for slashing weapons and low for bludgeoning, piercing and poking ones. The second value determines how deep the weapon penetrates - for BLUNT attacks this value is ignored as they're not supposed to penetrate anyway, but in the case of EDGE attacks it should generally be lower for slashing attacks and higher for stabbing attacks.

Following these are the adjectives used; they should be self-explanatory. Finally, we have the velocity modifier, which has a multiplying effect on the weapon's size for the purposes of determining how powerful it is in combat.

Other, more miscellaneous items are generally simple and shouldn't require any further explanation.

Once you've made an item, you just add it to the civ entry so a civilization can actually craft it, and it's done.

== Modding language files ==

Let's say you added a whole new species. Sure, you could just swipe one of the existing translation files and steal their language for your species, but that's the lazy way! If you want to create a whole new language, it's very simple.

First, you'd need a whole new language_RACE file, such as language_LIZARDMAN.txt, along with "language_LIZARDMAN" at the top of the file proceeded by [OBJECT:LANGUAGE] and [TRANSLATION:LIZARDMAN]. After that, it's just a matter of copy-pasting one of the existing language lists and editing the finished 'translated' word. That's it! Then just add the translation link to your civ in entity_default.txt and it'll be added to the game on worldgen.

== Modding body parts ==

Imagine you have this fantastic idea for a multi-tentacled winged spider-monster. Sounds great! But in order to make this a reality you may need to create a new set of body parts for it. That's no problem! Making body parts is easy, though it may look complicated at first.

All of the default body definitions are located in body_default.txt and then linked to a creature in the creature's entry. We've talked about how bodyparts make up creatures earlier, in the creature section. You can mix and match them in the creature entry and it makes no difference, as long as they're there: each bodypart will link itself to the appropriate connection automatically when the creature is first created.

Body parts work by sections: you can add as many sections as you want to a bodypart definition, but generally you should keep it fairly low for ease of use. Each body section entry is in the, very simple, format:

[BODY:BODYNAME]
[BP:TOKENID:name][TOKENSGOHERE][DEFAULT_RELSIZE:][CATEGORY:WHATEVER]

The most important tokens are "CONTYPE" and "CON": CONTYPE means the bodypart in question is connected to a certain ''type'' of bodypart, while CON means it's connected to a ''specific'' one. TOKENID is yet another identifier, which should be unique, as it's referenced every time something uses CON or BY_TOKEN. DEFAULT_RELSIZE defines, of course, what the bodypart's size is in relation to the other parts. CATEGORY defines a category for the part, which can be unique or shared with other parts. This is referenced whenever BY_CATEGORY is used.

A list of bodypart tokens can be found [[body token|here]].

Let's take a simple example, a head:

[BODY:BASIC_HEAD]
[BP:HD:head:STP][CONTYPE:UPPERBODY][HEAD][CATEGORY:HEAD]
[DEFAULT_RELSIZE:300]

It connects directly to an upper body.

[BODY:2EYES]
[BP:REYE:right eye:STP][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL][RIGHT][CATEGORY:EYE]
[DEFAULT_RELSIZE:5]
[BP:LEYE:left eye:STP][CONTYPE:HEAD][SIGHT][EMBEDDED][SMALL][LEFT][CATEGORY:EYE]
[DEFAULT_RELSIZE:5]

These are a pair of eyes, connecting to the head.

[BODY:HUMANOID]
[BP:UB:upper body:upper bodies][UPPERBODY][CATEGORY:BODY_UPPER]
[DEFAULT_RELSIZE:1000]
[BP:LB:lower body:lower bodies][CON:UB][LOWERBODY][CATEGORY:BODY_LOWER]
[DEFAULT_RELSIZE:1000]
[BP:HD:head:STP][CON:UB][HEAD][CATEGORY:HEAD]
[DEFAULT_RELSIZE:300]
[BP:RUA:right upper arm:STP][CON:UB][LIMB][RIGHT][CATEGORY:ARM_UPPER]
[DEFAULT_RELSIZE:200]
[BP:LUA:left upper arm:STP][CON:UB][LIMB][LEFT][CATEGORY:ARM_UPPER]
[DEFAULT_RELSIZE:200]
[BP:RLA:right lower arm:STP][CON:RUA][LIMB][RIGHT][CATEGORY:ARM_LOWER]
[DEFAULT_RELSIZE:200]
[BP:LLA:left lower arm:STP][CON:LUA][LIMB][LEFT][CATEGORY:ARM_LOWER]
[DEFAULT_RELSIZE:200]
[BP:RH:right hand:STP][CON:RLA][GRASP][RIGHT][CATEGORY:HAND]
[DEFAULT_RELSIZE:80]
[BP:LH:left hand:STP][CON:LLA][GRASP][LEFT][CATEGORY:HAND]
[DEFAULT_RELSIZE:80]
[BP:RUL:right upper leg:STP][CON:LB][LIMB][RIGHT][CATEGORY:LEG_UPPER]
[DEFAULT_RELSIZE:500]
[BP:LUL:left upper leg:STP][CON:LB][LIMB][LEFT][CATEGORY:LEG_UPPER]
[DEFAULT_RELSIZE:500]
[BP:RLL:right lower leg:STP][CON:RUL][LIMB][RIGHT][CATEGORY:LEG_LOWER]
[DEFAULT_RELSIZE:400]
[BP:LLL:left lower leg:STP][CON:LUL][LIMB][LEFT][CATEGORY:LEG_LOWER]
[DEFAULT_RELSIZE:400]
[BP:RF:right foot:right feet][CON:RLL][STANCE][RIGHT][CATEGORY:FOOT]
[DEFAULT_RELSIZE:120]
[BP:LF:left foot:left feet][CON:LLL][STANCE][LEFT][CATEGORY:FOOT]
[DEFAULT_RELSIZE:120]

An entire humanoid body. The foot bone's connected to the ankle bone...

"BODYGLOSS" entries, which you can sometimes find applied to creature entries, are simply replacement words for specific part name strings in a creature. For example, you'll find the bodygloss [BODYGLOSS:CLAW_HAND:hand:claw] in body_default.txt; you can then use this in a creature via "[BODYGLOSS:CLAW_HAND]" and it'll replace all instances of "hand" with "claw" in that creature. Be warned, however—if you were to, say make a bodygloss [BODYGLOSS:EARSTALK:ear:stalk:ears:stalk], it would not only change "ear" and "ears" to "stalk" and "stalks", it would also change "h'''ear'''t" to "h'''stalk'''t"! For all intents and purposes the body part will still function as the proper part, though.

== Plants ==

Plants are, again, not unlike creatures. With what you've learned so far in regard to tokens and the materials system, running through the notes included in plant_standard.txt should explain most things. [[Plant token|Here's the list of plant-specific tokens]].

[PLANT:MUSHROOM_HELMET_PLUMP]
[NAME:plump helmet][NAME_PLURAL:plump helmets][ADJ:plump helmet]
[USE_MATERIAL_TEMPLATE:STRUCTURAL:STRUCTURAL_PLANT_TEMPLATE]
[MATERIAL_VALUE:2]
[BASIC_MAT:LOCAL_PLANT_MAT:STRUCTURAL]
[EDIBLE_VERMIN]
[EDIBLE_RAW]
[EDIBLE_COOKED]
[PICKED_TILE:161][PICKED_COLOR:6:13:0]
[GROWDUR:300][VALUE:2]
[USE_MATERIAL_TEMPLATE:DRINK:PLANT_ALCOHOL_TEMPLATE]
[STATE_NAME_ADJ:ALL_SOLID:frozen dwarven wine]
[STATE_NAME_ADJ:LIQUID:dwarven wine]
[STATE_NAME_ADJ:GAS:boiling dwarven wine]
[MATERIAL_VALUE:2]
[DISPLAY_COLOR:5:0:0]
[EDIBLE_RAW]
[EDIBLE_COOKED]
[PREFIX:NONE]
[DRINK:LOCAL_PLANT_MAT:DRINK]

[USE_MATERIAL_TEMPLATE:SEED:SEED_TEMPLATE]
[MATERIAL_VALUE:1]
[EDIBLE_VERMIN]
[EDIBLE_COOKED]
[SEED:plump helmet spawn:plump helmet spawn:4:0:1:LOCAL_PLANT_MAT:SEED]
[SPRING][SUMMER][AUTUMN][WINTER]
[FREQUENCY:100]
[CLUSTERSIZE:5]
[PREFSTRING:rounded tops]
[WET][DRY]
[BIOME:SUBTERRANEAN_WATER]
[UNDERGROUND_DEPTH:1:3]
[SHRUB_TILE:142]
[DEAD_SHRUB_TILE:28]
[SHRUB_COLOR:5:13:0]
[DEAD_SHRUB_COLOR:5:6:0]

Let's look at this line by line:
First, we define it's file name. In this case it's MUSHROOM_HELMET_PLUMP. Next we define it's in-game name (plump helmet) and it's adjective for if you were to craft with it. (plump helmet earrings)

[USE_MATERIAL_TEMPLATE:STRUCTURAL:STRUCTURAL_PLANT_TEMPLATE]
[MATERIAL_VALUE:2]
[BASIC_MAT:LOCAL_PLANT_MAT:STRUCTURAL]

This defines the structure and material of the plant. It references STRUCTURAL_PLANT_TEMPLATE in the first line, so if you were to say, add wings to the template, the plump helmet plant would be winged. This is for the plant itself, not the end plump helmets.

After that we get our edible tokens. These say that vermin can eat the plant, and it can be eaten raw or cooked by your dwarves. So if you wanted a plant vermin would leave alone, you'd remove the [EDIBLE_VERMIN] token

[EDIBLE_VERMIN]
[EDIBLE_RAW]
[EDIBLE_COOKED]

Next, [PICKED_TILE:161] is the character(161 in this case) shown when the crop is harvested. See [[character table|character table]] for a table of usable tiles.
[PICKED_COLOR:6:13:0] Is the color used for the crop's tile when harvested. It is in a foreground:background:brightness format. See [[color|color]] for the colors usable.

[PICKED_TILE:161][PICKED_COLOR:6:13:0]

[GROWDUR:300] Is how long it takes for your crop to grow. There are 1008 growdur units in a season.
[VALUE:2] Is the value of harvested plant (default 1). Appears to have no effect in version 0.31.

[GROWDUR:300][VALUE:2]

This define's the plant's alcohol states. [STATE_NAME_ADJ:ALL_SOLID:] Is the frozen name. Followed is the actual drink name, and then it's boiling name. These are achieved by either Scorching or Freezing climates. [DISPLAY_COLOR] Is of course color. And [EDIBLE_RAW] and [EDIBLE_COOKED] are saying you can drink the alcohol raw or cooked?

[USE_MATERIAL_TEMPLATE:DRINK:PLANT_ALCOHOL_TEMPLATE]
[STATE_NAME_ADJ:ALL_SOLID:frozen dwarven wine]
[STATE_NAME_ADJ:LIQUID:dwarven wine]
[STATE_NAME_ADJ:GAS:boiling dwarven wine]
[MATERIAL_VALUE:2]
[DISPLAY_COLOR:5:0:0]
[EDIBLE_RAW]
[EDIBLE_COOKED]
[PREFIX:NONE]
[DRINK:LOCAL_PLANT_MAT:DRINK]

After that we get our seed template:

[USE_MATERIAL_TEMPLATE:SEED:SEED_TEMPLATE]
[MATERIAL_VALUE:1]
[EDIBLE_VERMIN]
[EDIBLE_COOKED]
[SEED:plump helmet spawn:plump helmet spawn:4:0:1:LOCAL_PLANT_MAT:SEED]

And all this says is that the seeds may be eaten by vermin, or cooked. Then it gives the name of our plant's seed, it's plural name, its foreground, background, and brightness colors. Followed by it's seed material, said material should have [SEED_MAT] to permit proper stockpiling.

And finally for the last chunk we have this:

[SPRING][SUMMER][AUTUMN][WINTER]
[FREQUENCY:100]
[CLUSTERSIZE:5]
[PREFSTRING:rounded tops]
[WET][DRY]
[BIOME:SUBTERRANEAN_WATER]
[UNDERGROUND_DEPTH:1:3]
[SHRUB_TILE:142]
[DEAD_SHRUB_TILE:28]
[SHRUB_COLOR:5:13:0]
[DEAD_SHRUB_COLOR:5:6:0]

First we define what seasons the plant may grow in, then we define how frequently this plant is generated in a particular area, followed by how many harvested crop items(fruit?) may come from 1 plant. [PREFSTRING:] Is what your dwarves like about the plant, which in this case is the rounded tops. [WET][DRY] Are the conditions under which the plant can grow. Wet means it can grow close to water, dry means it can grow away from water. This does not mean you can grow the plant on dry stone however. It is just for natural spawning of the plant.
[BIOME] Is what biome the plant grows in. [UNDERGROUND_DEPTH:Minimum:Maximum] Is the highest and lowest cavern levels that the plant can appear in if its biome is subterranean. Dwarven civilizations will only export (via the embark screen or caravans) things that available at depth 1. Defaults to 0:0 (surface only).
Lastly, [SHRUB_TILE] is the character used for the naturally spawning shrub of this plant, [DEAD_SHRUB] Is the dead shrub character. [SHRUB_COLOR] Is the shrub's color, and [DEAD_SHRUB_COLOR] is, of course, the dead shrub's color.
While this may or may not look like a lot of tokens, it's very easy. Just copy an existing plant and edit it to your new plant.
For the rest of the tokens, see [[plant token|plant token.]]

== Workshops ==

Coming sooner rather than later

== Materials ==

As we've seen when talking about creatures, materials are vital. Materials show up in two forms: material templates, which generally show up in creatures, and specific materials (designated as "inorganic"), which are (by default, at least) consigned purely to metal and stone types.

Let's take a look at METAL_TEMPLATE in material_template_default.txt. It's evident that most of the basic properties of metals are already defined in the template - it goes red and melts at a high enough temperature, it's heavy, and (as noted by the very bottom token) is a metal. We already know just how useful templates can be to creatures, and the same applies to other materials.

Now let's take a look at inorganic_metal.txt. You can see that the metals here refer to the templates, and, just like we did with creatures, then modify the properties of that template and expand upon it.

Finally, let's look at inorganic_stone_mineral.txt. Here we can see that in addition to the changes made to the template, there are also ENVIRONMENT tokens - these tell the game where to place these minerals during worldgen.

[[material definition token|Here's a list of material tokens]]. It should also help you out with any modifications you want to make regarding those creature modifications we were making a while back. See, it all ties together in the end. The beauty of the current materials system is that there's actually very little difference between, say, leather and iron - they're fundamentally the same thing, just with different properties, which is how things really should be.

== Examples ==

Coming later

= Modding utilities =

[http://www.bay12forums.com/smf/index.php?topic=28829.0 A list of many mods and community-developed utilities]

{{Category|Modding}}
[[Category:v0.31:Guides]]

User talk:Emi

2012-07-01T05:30:02Z

Toxicshadow: /* Could I get a page for my mod? */ new section