Dwarf Fortress Wiki - User contributions [en]

DF2014 Talk:Thought

2015-07-07T02:14:44Z

Dirst: /* Incomplete */ Pet-related thought, but don't have the info needed to add it properly.

== Incomplete ==

This page isn't complete any more. There are some new thoughts relating to Justice. --[[User:Dree12|Dree12]] ([[User Talk:Dree12|talk]]) 21:50, 24 July 2014 (UTC)

I've noticed "Urist was pleased when interacting with a pet recently" thoughts, too. But I don't know the strength of the thought to add it to the table properly. [[User:Dirst|Dirst]] ([[User talk:Dirst|talk]]) 02:14, 7 July 2015 (UTC)

== Thoughts not triggering properly? ==

I've noticed in my fort that a dwarf's father and brother didn't get the "grieves for somebody's death" bad thought when he was killed (though they were horrified to see him get killed in front of them). Neither did any of his friends. I'm not sure if this is a bug. [[User:Feb Rainyworks|Feb Rainyworks]]

Tool token

2015-06-23T16:57:15Z

Dirst: Added SOFT_MAT.

{{Quality|Superior|12:23, 18 May 2015 (UTC)}}
{{av}}

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

|-
| NAME
|
*singular
*plural
| Name of the tool. Required.

|-
| HARD_MAT
|
| Permits the tool to be made from any "hard" material, such as stone.

|-
| METAL_MAT
|
| Permits the tool to be made from any metal.

|-
| METAL_WEAPON_MAT
|
| Permits the tool to be made from any weapons-grade metal.

|-
| SOFT_MAT
|
| Permits the tool to be made from any "soft" material, such as leather.

|-
| WOOD_MAT
|
| Permits the tool to be made from any wood.

|-
| UNIMPROVABLE
|
| Prevents the tool from being improved. Used on honeycombs.

|-
| VALUE
|
*num
| Defines the item value of the tool. Required.

|-
| TILE
|
*num
| Defines the tile used to represent the tool. Required.

|-
| INVERTED_TILE
|
| Found on minecarts.

|-
| TOOL_USE
|
*tool use, see below
| Defines the task performed using the tool.

|-
| FURNITURE
|
| Allows item to be stored in a furniture stockpile.

|-
| ADJECTIVE
|
*adjective
| Adjective preceding the material name (e.g. "large copper dagger")

|-
| SIZE / WEIGHT
|
*size
| Volume of tool in mL or cubic centimeters. Required.

|-
| CONTAINER_CAPACITY
|
*amount
| How much the item can contain. Defaults to 0.

|-
| SHOOT_FORCE
|
*value
| Required for weapons.

|-
| SHOOT_MAXVEL
|
*value
| Required for weapons.

|-
| SKILL
|
*Skill token
| The skill to determine effectiveness in melee with this tool. Required for weapons.

|-
| RANGED
|
*Skill token
*Ammo item token
| Makes this tool a ranged weapon that uses the specified ammo. The specified skill determines accuracy in ranged combat.

|-
| TWO_HANDED
|
*size
| Creatures under this size (in cm^3) must use the tool two-handed. Required for weapons.

|-
| MINIMUM_SIZE
|
*size
| Minimum body size (in cm^3) to use the tool at all (multigrasp required until TWO_HANDED value) Required for weapons.

|-
| MATERIAL_SIZE
|
*value
| Number of bar units needed for forging, as well as the amount gained from melting. Required for weapons.

|-
| ATTACK
|
*attacktype:BLUNT or EDGE
*contact_area:value
*penetration_size:value
*verb2nd:string
*verb3rd:string
*noun:string
*velocity_multiplier:value
| You can have many ATTACK tags and one will be randomly selected for each attack, with EDGE attacks 100 times more common than BLUNT attacks. Required for weapons.
|}

Valid tool uses (and the default tools used for these tasks) are as follows:
{| class="wikitable sortable"
|- bgcolor="#999999"
! ID
! Token
! Usage
|-
| 0 || LIQUID_COOKING || cauldron
|-
| 1 || LIQUID_SCOOP || ladle
|-
| 2 || GRIND_POWDER_RECEPTACLE || mortar
|-
| 3 || GRIND_POWDER_GRINDER || pestle
|-
| 4 || MEAT_CARVING || carving knife
|-
| 5 || MEAT_BONING || boning knife
|-
| 6 || MEAT_SLICING || slicing knife
|-
| 7 || MEAT_CLEAVING || meat cleaver
|-
| 8 || HOLD_MEAT_FOR_CARVING || carving fork
|-
| 9 || MEAL_CONTAINER || bowl
|-
| 10 || NEST_BOX || nest box
|-
| 11 || LIQUID_CONTAINER || jug
|-
| 12 || FOOD_STORAGE || large pot
|-
| 13 || HIVE || hive
|-
| 14 || SMALL_OBJECT_STORAGE || pouch
|-
| 15 || TRACK_CART || minecart
|-
| 16 || HEAVY_OBJECT_HAULING || wheelbarrow
|-
| 17 || STAND_AND_WORK_ABOVE || stepladder

|}

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

DF2014:Graphic set

2014-10-03T22:17:11Z

Dirst: /* Text File Syntax */ Adjusted the notes for hunting- and war-trained animals.

:''(For an overview of graphics in DF, see [[Graphics]])''
:''(For user-created creature graphics sets, see [[Graphics set repository]].)''

A graphic set is an additional tileset for objects. While this is eventually planned for all objects in game, currently only creatures can assigned to graphic sets.
Graphic sets are placed in raw/graphics (as well as the raw folder of each save); A corresponding text file assigns tiles to objects.
==Documentation==
The graphic sets themselves are placed into subfolders. It is recommended that they have the same tile size as the main [[tileset]], but the number of tiles and their spatial arrangement doesn't matter (see [[Graphic_set#Notes|Notes]] for details).
All [[creature]]s can have separate graphics assigned to their adult and child states, undead, and their -men and giant variants. In addition, the major [[Civilization]]s can have separate graphics for all professions (such as miner, mason, caravan guard, and ghost). You can assign one graphic to several creatures/states, and you can set each tile to either be displayed as it appears or let the game color them. Vermin and different genders cannot have separate graphics assigned to them.
===Text File Syntax===
A Graphic set needs a text file that tells the game which tile is used for which creature. You can use separate text files for each graphic set, or a single one for several. Each text file consists of a header, one or more graphic set definitions (called "TILE_PAGE") and several creature graphics entries, each of which has subentries for professions.

The structure of a typical text file would look like this:
*Header
*Tile page definition
**Creature graphic entry
***profession subentry
***more
***profession
***subentries
**next creature
***with
***more
***professions
*new tile page definition
**a creature
***with adult
***and child graphics
**and another creature
***adult
***child

Below is an example of such a file.

graphics_mygraphics ← '''The first line of the header. You'll be saving the text document as this name (graphics_mygraphics.txt) This name should match the folder name you will be using in "raw/graphics".''' 
[OBJECT:GRAPHICS]
'''This concludes the header. Each graphic set text file needs to contain these lines.'''
<nowiki>------------------------------</nowiki>
below are dwarves ← '''text outside brackets gets ignored. You can use it for comments and organizing your file visually with lines''' 
[TILE_PAGE:MYDWARVES] ← '''Here you are defining properties of a single graphic set image. The title MYDWARVES will be used in creature graphic entries to refer to that graphic set. The title doesn't have to match any creature, folder, or image name.'''
[FILE:mygraphics/mydwarves.png] ← '''The subfolder where the graphic set is located (relative to this text file) and its filename, including the file extension. '''
[TILE_DIM:16:16] ← '''Height:Width - Pixels per tile, so DF knows where one tile ends and another begins'''
[PAGE_DIM:5:3] ← '''Width:Height - Tiles per image and how they're arranged in rows and columns.''' 
'''This concludes the first TILE_PAGE definition.''' 
'''Next are the creature graphic entries. Syntax is: [Profession:TILE_PAGE:X:Y:Color:State]''' 
'''X and Y are the coordinates of the tile on the image. More information below.''' 
[CREATURE_GRAPHICS:DWARF] ← '''The value (DWARF in this case) is the name the creature has in the raws. This NEEDS to be spelled correctly.'''
[DEFAULT:MYDWARVES:0:0:'''ADD_COLOR''':DEFAULT]
↑ ''' The ADD_COLOR value tells DF to give the tile the same colors as the default graphic '''
[STANDARD:MYDWARVES:1:0:'''AS_IS''':DEFAULT]
↑ '''AS_IS takes the tile as it is. Most likely this is the setting you want'''
[MINER:MYDWARVES:2:0:AS_IS:DEFAULT]
↓ '''We defined the tile page above. it refers to the image mydwarves.png '''
[CHILD:'''MYDWARVES''':3:0:AS_IS:DEFAULT]
[BABY:MYDWARVES:4:0:AS_IS:DEFAULT]
<nowiki>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</nowiki>
humans 
[TILE_PAGE:MYHUMANS] ← '''The next TILE_PAGE definition. You could put that (and its creature graphic entries) in a separate text file, but it would have to contain its own header.'''
[FILE:Other_Graphics/humans.png] ← '''This file is in another subfile'''
[TILE_DIM:16:16]
[PAGE_DIM:1:4] 
[CREATURE_GRAPHICS:HUMAN]
[DEFAULT:MYHUMANS:0:0:AS_IS:DEFAULT]
''' Notes can go here too.'''
[SWORDSMAN:MYHUMANS:0:1:AS_IS:DEFAULT]
['''RECRUIT''':MYHUMANS:0:2:AS_IS:'''ADVENTURER'''] ← '''An ADVENTURER with no weapons'''
['''SWORDSMAN''':MYHUMANS:0:3:AS_IS:'''ADVENTURER'''] ← '''An ADVENTURER with a sword'''
<nowiki>==============================</nowiki>
animals 
[TILE_PAGE:MYANIMALS]
[FILE:Other_Graphics/animals'''.bmp'''] ← '''Pictures can be in .BMP format, too.'''
[TILE_DIM:16:16]
[PAGE_DIM:6:2] 
[CREATURE_GRAPHICS:DOG]
[DEFAULT:MYANIMALS:0:0:AS_IS:DEFAULT]
[CHILD:MYANIMALS:1:0:AS_IS:DEFAULT]
['''TRAINED_HUNTER''':MYANIMALS:4:0:AS_IS:DEFAULT] ← '''TRAINED_HUNTER profession only works with animals that have the [TRAINABLE] or [TRAINABLE_HUNTING] tag.'''
['''TRAINED_WAR''':MYANIMALS:5:0:AS_IS:DEFAULT] ← '''TRAINED_WAR profession only works with animals that have the [TRAINABLE] or [TRAINABLE_WAR] tag.'''
[CREATURE_GRAPHICS:CAT]
[DEFAULT:MYANIMALS:0:1:AS_IS:DEFAULT]

===Coordinates===
The PAGE_DIM value in the TILE_PAGE section defines how many columns and rows a given TILE_PAGE (graphic set) has. The first value is the X axis (or "width"), the second value the Y axis ("height"). The origin (0,0) is at the top left.
This is how the coordinates would work with the image mydwarves.png from the example above:

{| border="1" cellspacing="0" cellpadding="5"
|-
| 0:0
| 1:0
| 2:0
| '''3:0'''
| 4:0
|-
| 0:1
| 1:1
| 2:1
| 3:1
| 4:1
|-
| 0:2
| 1:2
| 2:2
| 3:2
| 4:2
|-
|}
The position of the dwarven child graphic from the example above ([CHILD:'''MYDWARVES''':3:0:AS_IS:DEFAULT]) is shown in bold.

Note that the coordiantes start at 0, not 1. So, ''the last column in a 5 tile wide image is at 4'', not at 5.

===Notes===
The total number of tiles in a sheet cannot number more than 1024, regardless of how big (18x18) or how small (8x12) each tile is. Thus, a sheet that has its graphics organized into 22 rows and 44 columns works fine (as 22x44=968 which is less than 1024. However, a sheet that has 24 rows and 44 columns (24x44=1056) will not work.
{{Category| Interface}}

Interaction token

2014-09-07T18:28:03Z

Dirst: /* Interaction Definitions */ Added IT_LOCATION:CONTEXT_CREATURE_OR_LOCATION

{{av}}

The following tokens can be used to define and use interactions.

==Interaction Definitions==
{| {{prettytable}}
|- bgcolor="#C0C0C0"
! Token
! Context
! Arguments
! Description

|-
| I_SOURCE
| Global
| type
| Defines what things are capable of triggering this interaction. Can be specified multiple times. Valid values:
* REGION - The interaction takes place in particular types of regions in the world.
* SECRET - The interaction is a secret that can be learned by particular individuals.
* DISTURBANCE - The interaction is triggered when disturbing a [[tomb]].
* DEITY - The interaction is inflicted upon mortals by the gods.
* ATTACK - The interaction is triggered by an attack during combat.
* INGESTION - The interaction is triggered by eating or drinking something.
* CREATURE_ACTION - The interaction is triggered by an explicit action.
* UNDERGROUND_SPECIAL - The interaction takes place in [[Demonic fortress|curious underground structure]]s.

|-
| IS_HIST_STRING_1
| Within I_SOURCE
| text
| Describes what the interaction did to a historical figure. Displayed after the name of the historical figure that performed the interaction.

[IS_HIST_STRING_1: cursed ]

|-
| IS_HIST_STRING_2
| Within I_SOURCE
| text
| Describes what the interaction did to a historical figure. Displayed after the name of the historical figure that was targeted by the interaction.

[IS_HIST_STRING_2: to assume the form of a lizard-like monster every full moon]

|-
| IS_FREQUENCY
| Within I_SOURCE
| Number
| Presumably, the probability of biome specified by [IS_REGION] to have this interaction.

|-
| IS_NAME
| Within I_SOURCE
| string
| Generally used with secrets, describes what the secret is about.

|-
| IS_REGION
| Within I_SOURCE:REGION
| Region type
| Indicates what types regions are capable of performing this interaction. Can be specified multiple times. Valid values:
* ANY
* ANY_TERRAIN
* NORMAL_ALLOWED
* EVIL_ALLOWED
* GOOD_ALLOWED
* SAVAGE_ALLOWED
* EVIL_ONLY
* GOOD_ONLY
* SAVAGE_ONLY
* Region type - SWAMP, DESERT, FOREST, MOUNTAINS, OCEAN, LAKE, GLACIER, TUNDRA, GRASSLAND, HILLS

|-
| IS_SPHERE
| Within I_SOURCE:SECRET
| [[Sphere]]
| Indicates the sphere to which this secret pertains. Only one sphere can be defined for each [I_SOURCE:SECRET] token, thus several [I_SOURCE:SECRET] tokens required to create a valid custom secret, which belongs to several different spheres

|-
| IS_SECRET_GOAL
| Within I_SOURCE:SECRET
| Secret Goal token
| Indicates why somebody would want to learn the secret. Valid values:
* STAY_ALIVE
* MAINTAIN_ENTITY_STATUS
* START_A_FAMILY
* RULE_THE_WORLD
* CREATE_A_GREAT_WORK_OF_ART
* CRAFT_A_MASTERWORK
* BRING_PEACE_TO_THE_WORLD
* BECOME_A_LEGENDARY_WARRIOR
* MASTER_A_SKILL
* FALL_IN_LOVE
* SEE_THE_GREAT_NATURAL_SITES
* IMMORTALITY
However, currently only immortality will result in a secret being pursued during world-gen.

|-
| IS_SECRET
| Within I_SOURCE:SECRET
| Secret Flag
| Indicates how the secret can be learned. Valid values:
* SUPERNATURAL_LEARNING_POSSIBLE - the secret can be learned by supernatural means
* MUNDANE_RESEARCH_POSSIBLE - the secret can be researched by mundane means
* MUNDANE_TEACHING_POSSIBLE - the secret can be taught to apprentices
* MUNDANE_RECORDING_POSSIBLE:objects/text/(book_title).txt:objects/text/(book_topic).txt - the secret can be written in books with the specified title. If this tag is present, a slab will be created upon learning the secret by supernatural means.
|-
| IS_USAGE_HINT
| Within I_SOURCE:DEITY
| Usage Hint token
| Indicates why a deity would choose to perform this interaction. See CDI:USAGE_HINT below for valid values - in this context, MAJOR_CURSE is the only value that makes sense.

|-
| I_TARGET
| Global
| id, type
| Specifies what things this interaction acts upon. Can be specified multiple times. Valid values:
* CORPSE - Also includes pieces of corpses
* CREATURE
* MATERIAL
* LOCATION

|-
| IT_LOCATION
| Within I_TARGET
| Location
| Narrows down exactly what the interaction targets. Valid values:
* CONTEXT_REGION - Can only be used by IS_REGION interactions.
* CONTEXT_CREATURE
* CONTEXT_CREATURE_OR_LOCATION - Lets projectiles be aimed at specific creatures.
* CONTEXT_ITEM - Used when the target is a CORPSE.
* CONTEXT_BP - Use body part from CDI:BP_REQUIRED token (below).
* CONTEXT_LOCATION

|-
| IT_MANUAL_INPUT
| Within I_TARGET
| text
| Tells the player what they should be selecting.

|-
| IT_AFFECTED_CREATURE
| Within I_TARGET:CORPSE or I_TARGET:CREATURE
| CREATURE:CASTE
| Specifies specific creatures the interaction can target.

|-
| IT_AFFECTED_CLASS
| Within I_TARGET:CORPSE or I_TARGET:CREATURE
| Creature class
| Specifies creature classes the interaction can target.

|-
| IT_IMMUNE_CREATURE
| Within I_TARGET:CORPSE or I_TARGET:CREATURE
| CREATURE:CASTE
| Specifies specific creatures the interaction cannot target.

|-
| IT_IMMUNE_CLASS
| Within I_TARGET:CORPSE or I_TARGET:CREATURE
| Creature class
| Specifies creature classes the interaction cannot target.

|-
| IT_REQUIRES
| Within I_TARGET:CORPSE or I_TARGET:CREATURE
| Creature token or property
| Indicates that the target must have the specified property. Valid values:
* FIT_FOR_ANIMATION - Any corpse or body part that can become a zombie (heads, hands, etc.)
* FIT_FOR_RESURRECTION - The target corpse's UPPERBODY must be attached.
* HAS_BLOOD
* MORTAL
* NO_AGING
* STERILE
* Creature token: BLOODSUCKER, CAN_LEARN, CAN_SPEAK, CRAZED, EXTRAVISION, LIKES_FIGHTING (or LIKESFIGHTING), MISCHIEVOUS (or MISCHIEVIOUS), NO_CONNECTIONS_FOR_MOVEMENT, NO_DIZZINESS, NO_DRINK, NO_EAT, NO_FEVERS, NO_PHYS_ATT_GAIN, NO_PHYS_ATT_RUST, NO_SLEEP, NO_THOUGHT_CENTER_FOR_MOVEMENT, NOBREATHE, NOEMOTION, NOEXERT, NOFEAR, NONAUSEA, NOPAIN, NOSTUN, NOT_LIVING, NOTHOUGHT, OPPOSED_TO_LIFE, PARALYZEIMMUNE, SUPERNATURAL, TRANCES, UTTERANCES

|-
| IT_FORBIDDEN
| Within I_TARGET:CORPSE or I_TARGET:CREATURE
| Creature token or property
| Indicates that the target must not have the specified property. Valid values are the same as for IT_REQUIRES.

|-
| IT_CANNOT_TARGET_IF_ALREADY_AFFECTED
| Within I_TARGET:CORPSE or I_TARGET:CREATURE
|
| Prevents the interaction from targeting a creature that's already under the effect of the same interaction.

|-
| IT_CANNOT_HAVE_SYNDROME_CLASS
| Within I_TARGET:CORPSE or I_TARGET:CREATURE
| [[Syndrome]] class
| Prevents the interaction from targeting a creature under the effects of a syndrome having the specified SYN_CLASS value.

|-
| IT_MATERIAL
| Within I_TARGET:MATERIAL
| Type
| Specifies the type of material the interaction targets. Valid values:
* FLOW:Breath attack token - Specifies an attack not made of any material.
* MATERIAL:[[Material token]]:Breath attack token - Specifies an attack made of a specific material.
* CONTEXT_MATERIAL - Use material from CDI:MATERIAL token (below).

|-
| I_EFFECT
| Global
| type
| Specifies what the interaction does to the targets. Can be specified multiple times. Valid values:
* ANIMATE - Raises the target corpse/bodypart as a zombie. The zombie will always be hostile to life and will retain no information about its original personality/loyalties. Syndromes can also be specified within this tag.
* ADD_SYNDROME - Adds one or more syndromes. The actual syndrome is specified with the [SYNDROME] tag.
* RESURRECT - Returns the creature to life. This can be used on parts that are not FIT_FOR_RESURRECTION, but only the main part (with an UPPERBODY attached) will remain loyal to its original faction. Syndromes can also be specified within this tag.
* CLEAN - Cleans off most liquids/dust covering the creature.
* CONTACT - Causes the creatures to touch. The interaction's range must be TOUCHABLE.
* MATERIAL_EMISSION - Used within the MATERIAL_EMISSION interaction.
* HIDE - Allows the creature to hide even if another creature can see it.

|-
| IE_TARGET
| Within I_EFFECT
| ID
| Specifies which I_TARGET this effect will be applied to

|-
| IE_INTERMITTENT
| Within I_EFFECT
| Frequency
| Indicates that the effect happens intermittently and specifies roughly how often. Valid values:
* WEEKLY

|-
| IE_IMMEDIATE
| Within I_EFFECT
|
| Indicates that the effect happens immediately.

|-
| IE_LOCATION
| Within I_EFFECT
| Location Hint
| Indicates where the effect can take place. Valid values:
* IN_WATER
* IN_MAGMA
* NO_WATER
* NO_MAGMA

|-
| IE_ARENA_NAME
| Within I_EFFECT
| text
| Allows the interaction to be applied to newly spawned creatures in Arena mode.

|-
| IE_GRIME_LEVEL
| Within I_EFFECT:CLEAN
| amount?
| [IE_GRIME_LEVEL:2] appears in the default cleaning interaction, and may indicate amount of grime cleaned.

|-
| IE_SYNDROME_TAG
| Within I_EFFECT:CLEAN
| Syndrome flag
| Indicates that cleaning off materials will activate their syndromes if they have this flag.

|-
| GENERATED
| Global
|
| Indicates that this is a generated interaction. Cannot be specified in user-defined raws.

|}

==Interaction Usage==
In order to actually use an interaction, add the [[creature token]] [CAN_DO_INTERACTION:NAME] followed by a series of [CDI:...] tokens. Interactions can also be granted through [[syndrome]]s using the token [CE_CAN_DO_INTERACTION] (plus the same series of CDI tokens).

The following CDI tokens can be specified:
{| {{prettytable}}
|- bgcolor="#C0C0C0"
! Token
! Arguments
! Description

|-
| INTERACTION
| id
| Specifies which interaction can be performed. Only to be used with syndromes, since CE_CAN_DO_INTERACTION does not allow specifying the interaction ID directly.

|-
| TARGET
| target ID, target types
| Specifies how the creature chooses what to . Target ID refers to an I_TARGET defined in the interaction itself. Multiple target types can be specified. If no target is specified, creature will target any available target within range, even through walls. Valid target types:
* LINE_OF_SIGHT - the source needs to be able to see the target
* TOUCHABLE - the source needs to be able to touch the target
* DISTURBER_ONLY - the target must be whoever disturbed the source
* SELF_ALLOWED - the target can be the source
* SELF_ONLY - the target '''must''' be the source

|-
| TARGET_RANGE
| target ID, range
| Specifies how far away the target can be, in tiles.

|-
| LOCATION_HINT
| Location Hint (see above)
| ?

|-
| USAGE_HINT
| Usage hint token
| Indicates when and how CPU-controlled creatures will use the interaction. If no hint is specified, the interaction will be used whenever a valid target is available. Valid values:
* MAJOR_CURSE - Used in disturbance curses and deity curses. Targets the tomb disturber/temple defiler.
* GREETING - Creatures will target 'friendly' creatures, usually at random.
* CLEAN_SELF - Creature targets itself when covered in liquids or dust.
* CLEAN_FRIEND - Same, but targets other friendly units.
* ATTACK - Targets enemy creatures in combat. If the interaction specifies SELF_ONLY, CPU-controlled creatures will never use it.
* FLEEING - Used when fleeing an enemy. Creature will target itself.
* NEGATIVE_SOCIAL_RESPONSE - Used when a creature is expressing contempt (for example, to a murderer). Used for spitting by civilised races.
* TORMENT

|-
| ADV_NAME
| text
| Specifies the interaction's name when used in Adventurer mode.

|-
| MAX_TARGET_NUMBER
| ID, number
| Specifies the maximum number of things that can be selected for a particular I_TARGET.

|-
| WAIT_PERIOD
| number
| Controls how often the interaction can be used.

|-
| VERBAL
|
| Only creatures that can speak will be able to use the interaction. Might also be needed for VERBAL_SPEECH.

|-
| VERBAL_SPEECH
| filename
| Specifies what the creature says when they perform the interaction. Filename path is relative to /data/speech.

|-
| CAN_BE_MUTUAL
|
| Presumably, allows two creatures with this same interaction to use it on each other simultaneously, for example cats cleaning each other.

|-
| FREE_ACTION
|
| Indicates that performing the interaction doesn't take any time.

|-
| VERB
| self:other:mutual
| When a creature uses the interaction, a message will display, describing the source as doing this.

|-
| VERB_REVERSE
| ?
| ?

|-
| TARGET_VERB
| self:other
| When a creature uses the interaction, a message will display, describing the target as doing this.

|-
| BP_REQUIRED
| Body part criteria
| Indicates that a particular body part must be present in order to perform the interaction. Criteria are BY_CATEGORY:category, BY_TYPE:type, or BY_TOKEN:token.

|-
| FLOW
| [[Syndrome#Breath Attack Types|Breath attack token]]
| Causes the interaction to create an effect not made of any material. Only makes sense for FIREBALL, FIREJET, or DRAGONFIRE.

|-
| MATERIAL
| [[Material token]]:Breath attack token
| Causes the interaction to create an effect made of a specific material. Doesn't make sense for FIREBALL, FIREJET, or DRAGONFIRE.

|}

==See Also==
* [[Syndrome]]

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

Utility:Stonesense/Adding Content

2014-08-24T23:12:25Z

Dirst: Added a *very* simple tutorial for Stonesense buildings

{{Quality|Superior|06:39, 4 October 2013 (UTC)}}
=Basics=

===Creating Distributable Content Files===
The default way of distributing content for [[Stonesense]] is to create an archive of the XML configs and the image files. Upload this archive together with a description to the [[Stonesense Content Repository]] page, in much the same way tilesets and graphic packs are distributed for Dwarf Fortress, see the [[Tileset repository]] for reference.

Keep in mind that users installing your content pack will need to place the files in the correct content folder (creatures buildings, etc) and add the XML files to their index.txt file.

===Multiple Definition Files===

Stonesense searches for images in the order that they are found top to bottom in the index file, then in the definition files. So if you are adding a custom set of sprites for something already in the system, you need to add it to the *top* of the index file.

===Tips and Tricks===

While simple creature definitions arent much use without a sheetIndex attribute, it can be useful to define variants without giving the base creature a sprite. This would cause the game to keep looking for creature definitions, allowing you to, for example, define custom professions in one file while still using the basic definitions.

==Understanding Sprites==
Understanding how Stonesense deals with sprites is central to anyone who wishes to modify the content. The scheme is not very complicated, and this guide will give a short introduction to how they work. The way sprites are loaded is fairly generalized. With the exception of floors, which we will discuss later, all sprites are 32x32 pixels big and come in groups known as ''Sprite Sheets''. There are no alpha values yet, so partial transparency is not supported. RGB 255,0,255 (Magenta pink) is considered fully transparent. All sprites are loaded and rendered in 32bit fullcolor pngs.

Here's an example of a typical Stonesense sprite: 
[[File:Stonesene_sprite_sample.png]]

Note that, in order not to conflict with neighboring sprites, a sprite must actually be within a smaller area than its 32x32 block. A template for the area used by most sprites is: 
[[File:Stonesene_sprite_template.png]]

The solid area is the floor space taken up by a sprite, while the dotted box indicates the volume above this area corresponding to one z-level.

===Sprite Sheets===
There can be an arbitrary number of sprite sheets configured for Stonesense, yet some are always present as they contain default sprites (see further down). Most of the content XML files allow users to specify sprite sheets, and this is done by adding a '''file''' attribute to the content nodes. By convention sprite sheets should be placed in their appropriate folder, with creature sprite sheets in the ''creatures'' folder etc. For more information on this, see the specific pages on content configuration.

'''A very helpful tips for modders:''' Pressing '''F10''' in Stonesense will bring up a screen where one can cycle through all the loaded sprite sheets, with sprite indexes superimposed.

===Sprite Index===
Sprite Index (sometimes referred to as Sheet Index) is a concept for referring to a specific sprite on a sheet. The index starts with the upper left sprite which has index zero. It then increments to the right. Stonesense is hardcoded to 20 sprites wide sheets, this means that the last sprite to the right in the first row has Sprite Index 19. The first sprite on the second row has index 20. This boundary is hardcoded and changing the size of the sheet will not affect it.

This image shows how sprites are indexed. Note: Grid added for readability. 
[[File:Stonesene_indexed_sprites.png]]

===Specific Sprite Sheets===

'''objects.png''' is the default sheet for buildings and vegetation. Also used for all hard-coded content, like default plants, the cursor, default walls and liquid.

'''creatures.png''' is the default sprite sheet for creatures. If no file is specified in a creature node, this is the sheet it will use.

'''floors.png''' holds all the Stonesense floors. Unlike the other sprite sheet, this sheet is hard-coded with sprite dimensions of 32x20 pixels.

Stonesense is fully configurable in the way it renders creatures. No information is hardcoded, but rather loaded from the creature databases found in the creatures directory.

=Creatures=

==index.txt==

The first thing the game does when loading the creature configuration is to look in the creatures/index.txt file. It uses this file to tell it what configuration files are available, and in what order to load them (this becomes important later).
The format of the file very straight forward; each line specifies the path of a file to be loaded. The paths are relative to index.txt.

==Creature XML files==

Stonesense is fully configurable in the way it renders creatures. No information is hardcoded, but rather loaded from the creature databases found in the creatures directory.

===Simple configuration===
In it's simplest from, a creature configuration file might look like this:

<pre>
<?xml version="1.0"?>
<creatures>
<creature gameID="MACAQUE_RHESUS" sheetIndex="2" />
<creature gameID="MUSKOX" sheetIndex="25" />
<creature gameID="COW" sheetIndex="5" />
</creatures>
</pre>

As you probably guess, this defines three creatures by their ID: A rhesus monkey, a muskox and a cow. The three animals use the sprites numbered 2, 25 and 5 respectively. No special sprite sheet is specified, so the default creature sheet will be used, ''creatures.png''. More on this later.

As you can see, each creature is identified by a '''gameID''' attribute. This has to match one of the known creature types in Dwarf Fortress, as defined in the '''[CREATURE:critter_name]''' part of the raws. This gameID tag is case sensitive. If Stonesense is unable to match your gameID with one from Dwarf Fortress, a log message will be written to ''Stonesense.log'' upon loading a map.

===Professions===
The <creature> tag can be quite a bit more advanced than what we've seen so far. One thing it is often relevant to distinguish is creature professions. A creature's profession is set by the game, and examples might include "WOODCRAFTER", "ADMINISTRATOR" or "MACEMAN". A complete list of creature professions can be found [[Unit type token|here]]. Also note that all races have the same creature strings, meaning a dwarf swordsman will still be a "SWORDS''MAN''".

To separate creatures on their professions, we first need to add a <variant> node to the base creature node.
By adding a '''prof''' attribute to this node, we can display different sprites for different creature professions.

'''Note:''' The game always picks the ''first'' <variant> node that matches.

Let's have a look at a typical creature configuration that includes professions:
<pre>
<creature gameID="DWARF" sheetIndex="0" file="creatures/dwarves.png">
<variant prof="MINER" sheetIndex="1" />
<variant prof="CLERK" sheetIndex="2" />
<variant prof="AXEMAN" sheetIndex="3" />
</creature>
</pre>

Here we see three professions defined. Notice how the <creature> node now has been expanded.

Also note that the <creature> node still contains a sheetIndex attribute. This is the default creature sprite, meaning that if a dwarf does not match any of the <variant> nodes, it will be shown as this sprite index (in this case 0).
The corresponding sprite sheet (here called ''dwarves.png'') would look something like this:

[[File:Stonesene_dwarf_prof.png]]

===Children and babies===
Children and babies always have the professions "CHILD" and "BABY", and these can be used to have indicate creature ages. Consider the following example for cats and kittens:
<pre>
<creature gameID="CAT" sheetIndex="20">
<variant prof="CHILD" sheetIndex="21" />
</creature>
</pre>
Here the cat sprite would be at index 20, and kittens at 21.

===Creature Genders===
Each <variant> node can be extended with a ''sex'' attribute to add an additional condition for creature gender.
For most races. dwarfs included, the attribute can have one of two values, "M" for male or "F" for female. However, if the creature has more than two castes, a number must be used, starting from "1", and continuing in order that the castes are listed in the rawfile. As of Stonesense Felsite v3.1, castes can be specified by name such as caste="WARRIOR".
Again a simple example would be beneficial:
<pre>
<creature gameID="HUMAN" sheetIndex="100">
<variant prof="BOWMAN" sex="M" sheetIndex="106" />
<variant prof="BOWMAN" sex="F" sheetIndex="107" />
<variant sex="F" sheetIndex="101" />
</creature>
</pre>

This simplified human config shows two different sprites used for bowmen. Male bowmen will use sprite index 106 and female bow-women will use 107.
Another very important thing to note here is the last entry, which only specifies a gender, and no profession. This means the only criteria for this node is that the creature is Human, and it's female. Hence 101 is the default sprite for human females. Together with the default sprite defined in the <creature> node itself (sheetIndex = 100), it allows us to have separate default sprites for men and women.

===Special Creatures===

Sometimes creatures appear as zombies, or skeletons. To tell these creatures apart from normal ones, you can use the '''special''' attribute to the <variant> node.
It accepts three types of arguments, ''Normal'', ''Zombie'' or ''Skeleton'',
and is used in the exact same way as the '''sex''' attribute.

===Coloring creatures===
As of Stonesense Slate RC2, creatures can be automatically colored by numerous factors, using the ''color'' attribute. Valid values are:

''profession'': The sprite is colored according to the creature's current profession. this works the same way as in Dwarf Fortress.

''bodypart'': The sprite is colored according to one of the creatures body part colors. this requires an additional ''bodypart'' attribute that describes which body part to get the color from.

''material'': The sprite is colored according to the floor it is standing on. this probably not very useful, unless you have a chameleon creature.

''vein'': Same as above, but the color comes from the ore veins, disregarding constructions.

''layer'': Same as above, but the color comes from the rock layer, disregarding veins and constructions.

''xml'': Manually specify a color in the creature definition, requires additional ''red'', ''green'', and ''blue'' attributes.

''none'': No color is used.

An example:

<pre>
<creature gameID="HUMAN" sheetIndex="0">
<variant sex="M" sheetIndex="4" color="profession" />
<variant sex="F" sheetIndex="4" color="bodypart" bodypart="skin" />
<variant sex="F" job="AXEMAN" sheetIndex="4" color="xml" red="123" green="0" blue="255" />
</creature>
</pre>

===Subsprites===

Each creature definition can also have any number of subsprites that are layered onto it like a paper doll. each subsprite can be colored differently, so you can have, say, a dwarf with a base sprite, a hair sprite, that's colored according to the hair-color of the dwarf, and a skin sprite, that's colored according to the skin-color of the dwarf.

An example should help:

[[File:japa_gobbos.png]]

<pre>
<?xml version="1.0"?>
<creatures>
<creature gameID="GOBLIN" sheetIndex="0" file="gobbos.png" color="bodypart" bodypart="skin">
<subsprite sheetIndex="1" color="bodypart" bodypart="hair" />
<subsprite sheetIndex="2" />
<subsprite sheetIndex="3" color="profession" />
<variant sex="F" sheetIndex="4" color="bodypart" bodypart="skin">
<subsprite sheetIndex="5" color="bodypart" bodypart="hair" />
<subsprite sheetIndex="6" />
<subsprite sheetIndex="7" color="profession" />
</variant>
</creature>
</creatures>
</pre>

Here, we have a main goblin sprite, that is colored according to the skin color of the individual goblin (usually a shade of green) this is the goblin's body. Then a second sprite is layered over it, which is the hair sprite, and is colored according to the hair. The third layer has no color change, and contains things like claws and eyes, that we don't want to be colored. The final layer contains the clothes, which are colored according to the goblin's profession. this will give us the following completed sprite:

[[File:Japa_gobbo.png]]

===Animating Creatures===

Adding animations to creatures is really quite simple. But before we dive into it, it makes sense to look at how Stonesense animations work.

Currently, the game cycles through six frames at a steady pace. The speed at which these frames are cycles can be specified in the init file, but it global and shared between all sprites.

To add animations to a creature, we add another condition attribute, ''frames'', to the <variant> node, like this:
<pre>
<variant sheetIndex = 7 frames = "012" />
</pre>

Here frames is set to the value "012". This means that this variant node is valid at frames 0, 1 and 2. It is NOT valid, at frames 3, 4 and 5. Remember there are six frames in total, from 0 to 5.
The value of the frames attribute is treated as a string, not as a number. This is important to note, as "frames=354" has the same effect as ''frames=453'', and indeed also ''frames="3 5, 4"'' or ''frames="3x5@ .4"''. The invalid characters are simply ignored.

An example
Let's make an animated Giant Bat, using this awesome sprite sheet made by Beefmo:

[[File:beefmo_giantbat.png]]

Now, to configure up a basic animation for a giant bat, we could add something like this to Wildlife.xml:
<pre>
<creature gameID="BAT_GIANT" sheetIndex = 0 file="giantbat.png" >
<variant sheetIndex = 2 frames = "345"/>
</creature>
</pre>
This will create a simple 2-frame animation. Each frame is used for the same length of time, since the default is used for frames 0, 1 and 2, and the overriding variant is used for frames 3, 4 and 5.
Hint: If you want the bat to flap its wings faster, change the frames for the variant to "024".

But Beefmo's giant bat sheet has three frames, so let's add them all for a complete animation:
<pre>
<creature gameID="BAT_GIANT" sheetIndex = 0 file="giantbat.png" >
<variant sheetIndex = 0 frames = "05"/>
<variant sheetIndex = 1 frames = "14"/>
<variant sheetIndex = 2 frames = "23"/>
</creature>
</pre>
Notice how the frames are used twice, to make a nice cyclic animation.
The indexed sprites will be drawn in order 0 1 2 2 1 0.

=Vegetation=

Vegetation content can be found in the ''vegetation'' folder of Stonesense.

Just like with all the other configurable content, the active plant and shrub XML files are outlined in an ''index.txt'' file.

The buildup of these XML files is very simple. Take a look at this example config file for trees:
<pre>
<?xml version="1.0" ?>
<trees file="vegetation/trees.png">
<plant gameID = "ACACIA" sheetIndex = 0 />
<plant gameID = "ALDER" sheetIndex = 1 />
<plant gameID = "ASH" sheetIndex = 2 />
<plant gameID = "BIRCH" sheetIndex = 31 />
</trees>
</pre>
And this one for shrubs:
<pre>
<?xml version="1.0" ?>
<shrubs file="vegetation/shrubs.png">
<plant gameID = "MUSHROOM_HELMET_PLUMP" sheetIndex = 0 />
<plant gameID = "GRASS_TAIL_PIG" sheetIndex = 1 />
<plant gameID = "GRASS_WHEAT_CAVE" sheetIndex = 2 />
<plant gameID = "POD_SWEET" sheetIndex = 3 />
</shrubs>
</pre>

Note that the only difference is the root node, both of which contain <plant> nodes.
The plant nodes should be rather straight forward; it only has two attributes:
*gameID: the name of the shrub or tree, as defined by the DF raw files. See here [[Talk:Stonesense:Adding_Vegetation|for a complete list]].
*[[Stonesense:Sprites#Sprite_Index|sheetIndex]]: the index of the sprite to be drawn for this plant.

Which sprite sheet the sheetIndex attributes refers to is specified by the file attribute in the root node.
The examples above uses "trees.png" and "shrubs.png" respectively.
If no file is specified, it will use the Objects.png in the Stonesense root folder.

Tree saplings and dead trees can be defined as well by adding the appropriate keywords to their plant entry:
<pre>
<plant gameID = "ALDER" dead="true" sapling="true" sheetIndex = 31 />
</pre>
There is no support for young shrubs, so the "sapling" keyword does nothing for shrubbery.
At present, (in Stonsense Granite) the value of the "dead" and "sapling" keywords is ignored, so:
<pre>
<plant gameID = "ALDER" dead="false" sapling="true" sheetIndex = 31 />
</pre>
... will still select for dead saplings.

=Buildings=
Building content can be found in the ''buildings'' folder of Stonesense.

As with other content, the content is outlined with an ''index.txt'' file, but unlike other content, the included content is very complex and difficult to follow.

Each tile in a workshop has a PositionIndex, starting at 0 for the northwest corner as shown in the 3x3 examples below:

[[file:SimpleWorkshopExample.png]]

This workshop was generated from the simplest possible code, to serve as an example for basic workshop construction. Far more advanced processing is possible, as can be seen from the content included with Stonesense.

<pre>
<?xml version="1.0" ?>

<building name="Example Building" game_type="Workshop" game_subtype="Custom" game_custom="TEST" file="TEST.png">

<if>
<PositionIndex value=0 />
<sprite index=0 />
</if>
<if>
<PositionIndex value=1 />
<sprite index=1 />
</if>
<if>
<PositionIndex value=2 />
<sprite index=2 />
</if>
<if>
<PositionIndex value=3 />
<sprite index=3 />
</if>
<if>
<PositionIndex value=4 />
<sprite index=4 />
</if>
<if>
<PositionIndex value=5 />
<sprite index=5 />
</if>
<if>
<PositionIndex value=6 />
<sprite index=6 />
</if>
<if>
<PositionIndex value=7 />
<sprite index=7 />
</if>
<if>
<PositionIndex value=8 />
<sprite index=8 />
</if>

</building>
</pre>

The above XML code and this graphic produced the example seen above. Note that only the "floor" of each tile was defined in this spritesheet. Actual workshops would likely include taller images.

[[File:SimpleSpritesheetExample.png]]

[[Category:Stonesense]]

File:SimpleSpritesheetExample.png

2014-08-24T23:09:38Z

Dirst: Spritesheet used in the simple workshop example for Stonesense.

== Summary ==
Spritesheet used in the simple workshop example for Stonesense.
== Licensing ==
{{self|cc-by-sa-3.0}}

File:SimpleWorkshopExample.png

2014-08-24T23:00:44Z

Dirst: Illustration of PositionIndexes in Stonesense workshops

== Summary ==
Illustration of PositionIndexes in Stonesense workshops
== Licensing ==
{{self|cc-by-sa-3.0}}

Utility:Stonesense/Adding Content

2014-08-21T15:50:22Z

Dirst: /* Creature Genders */ Added how castes are handled in v3.1

Entity token

2014-07-21T17:30:13Z

Dirst: /* Behavior */ Removed link from "value" since it pointed to an article about item value. There is no page on cultural values?

{{Migrated_article}}
{{quality|unrated}}{{av}}
'''Entity tokens''' define entities, or civilizations, in entity_*.txt files.

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

|-
| {{text anchor|ADVENTURE_TIER}}
| order
| Allows adventure mode for entities with sites. Dwarves, Elves, and Humans take up tier 3, 2, and 1 respectively. Order doesn't need to be maintained; a custom creature can have a tier of 3000 and still work even if it's the only custom creature.
[ADVENTURE_TIER:4]

|-
| {{text anchor|INDIV_CONTROLLABLE}}
|
| Allows the race to be played as an "outsider" in adventure mode. Not having this specified in one of the entities will cause the Adventure mode option to disappear. Note that ADVENTURE_TIER is not required if this token is included, and that this cannot be applied to civilizations that were not in an entity_*.txt file during world gen.

|-
| {{text anchor|CIV_CONTROLLABLE}}
|
| Allows fortress mode. If multiple entities have the CIV_CONTROLLABLE token, than in embark mode the specific civs can be chosen by + or - on the civ list screen (by pressing tab), though it will not state what entity the civs belong to. To check which one, tab to the neighbors screen: the entity's race will be at the top. At least one civilization must have this token.

|-
| {{text anchor|CREATURE}}
| creature
|The type of creature that will inhabit the civilization. If multiple creature types are specified, each civilization will randomly choose one of the creatures.
[CREATURE:DWARF]

|-
| {{text anchor|CREATURE_HFID}}
| integer (or generic token?)
| Found on generated [[angel]] entities. Seemingly draws from all creatures with the same [HFID] token.

|}

== Placement ==

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

|-
| {{text anchor|BIOME_SUPPORT}}
|
* [[Biome token|biome]]
* frequency
| Frequency goes from 0 to 10. Higher numbers make the entity more likely to settle there.
[BIOME_SUPPORT:ANY_GRASSLAND:4]

|-
| {{text anchor|START_BIOME}}
| [[Biome token|biome]]
| Birth of the civilization can be performed on this biome.
[START_BIOME:ANY_FOREST]

|-
| {{text anchor|EXCLUSIVE_START_BIOME}}
| [[Biome token|biome]]
| Birth of the civilization only occurs in this biome.
[EXCLUSIVE_START_BIOME:MOUNTAIN]

|-
| {{text anchor|SETTLEMENT_BIOME}}
| [[Biome token|biome]]
| This civ will create small settlements on this biome, not too far from the EXCLUSIVE_START_BIOME. Used for dwarven hillocks.
[SETTLEMENT_BIOME:ANY_GRASSLAND]

|-
| {{text anchor|DEFAULT_SITE_TYPE}}
| site type
| Valid site types are DARK_FORTRESS (π), CAVE (•), CAVE_DETAILED (Ω), TREE_CITY (î), and CITY (#). Also recognizes PLAYER_FORTRESS, and MONUMENT, though these likely will not work. FORTRESS is no longer a valid entry, instead castles are controlled by BUILDS_OUTDOOR_FORTIFICATIONS. Defaults to CITY.
[DEFAULT_SITE_TYPE:CAVE_DETAILED]

|-
| {{text anchor|LIKES_SITE}}
| site type
| Most residents will try to move to this site type, unless already at one.
[LIKES_SITE:CAVE_DETAILED]

|-
| {{text anchor|TOLERATES_SITE}}
| site type
| Some residents will try to move to this site type, unless already at one.
[TOLERATES_SITE:CITY]

|-
| {{text anchor|WORLD_CONSTRUCTION}}
| construction
| Controls which constructions the civ will build on the world map. Valid constructions are ROAD, TUNNEL, BRIDGE, and WALL.
[WORLD_CONSTRUCTION:BRIDGE]
[WORLD_CONSTRUCTION:ROAD]
[WORLD_CONSTRUCTION:TUNNEL]
[WORLD_CONSTRUCTION:WALL]

|}

== Population ==

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

|-
| {{text anchor|START_GROUP_NUMBER}}
| number
| Number of breeding couples to start with per entity. Helps give a boost to weaker civs by giving them more cannon fodder at the beginning of their histories, and better genetic diversity (if that's modeled for that particular creature). Note that single-gender (e.g. [FEMALE], [MALE], [NO_GENDER]) creatures will not have breeding couples, so a civilization with only these creatures will not be very likely to survive. As of 40d, although many had problems getting such civilizations to survive, there are those who have demonstrably and repeatedly done so. Presumably if the civ-stating code can't place breeding couples, it doesn't start the civ. However, because the children never grow up, the civ is limited to its original individuals).
[START_GROUP_NUMBER:10]

|-
| {{text anchor|MAX_POP_NUMBER}}
| number
| Max population '''per entity'''. Multiply this by max starting civ to get the total population of the species. Defaults to 500.
[MAX_POP_NUMBER:500]

|-
| {{text anchor|MAX_SITE_POP_NUMBER}}
| number
| Max population per individual site. Generic site types will not hold any more than this number of entities. Must be at least 80 for towns to be generated. In general, lower pop numbers mean more sprawl, and higher numbers mean more needing to crawl when entering town stores, which are not affected by this cap. Defaults to 50.
[MAX_SITE_POP_NUMBER:200]

|-
| {{text anchor|MAX_STARTING_CIV_NUMBER}}
| number
| Max number of entities to spawn at world generation. Worldgen picks civs in some sequential order from the raws. Once it reaches the end of the list, it will begin again at the top. Setting this number lower than 100, like say, 7, will cause worldgen to skip over this civ for placement if there are already 7 civs of this type. Note that if all civs are set to lower numbers, and the number of starting civs is set higher than the maximum possible amount of civs in total, it will gracefully stop placing civs and get down to the history aspect of worldgen. Defaults to 3.
[MAX_STARTING_CIV_NUMBER:3]

|}

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

|-
| {{text anchor|PERMITTED_BUILDING}}
| building name
| The named, custom building can be built by a civilization in Fortress Mode.
[PERMITTED_BUILDING:SOAP_MAKER]

|-
| {{text anchor|PERMITTED_JOB}}
| [[Unit type token|profession]]
| Allows this job type to be selected. This applies to worldgen creatures, in the embark screen, and in play. Certain professions also influence the availability of materials for trade.
[PERMITTED_JOB:MINER]

|-
| {{text anchor|PERMITTED_REACTION}}
| reaction name
| Allows this reaction to be used by a civilization. It is used primarily in Fortress Mode, but also allow certain resources, such as [[steel]], to be available to a race. When creating custom reactions, this token MUST be present or the player will not be able to use the reaction in Fortress Mode.
[PERMITTED_REACTION:TAN_A_HIDE]

|-
| {{text anchor|CURRENCY_BY_YEAR}}
|
| Causes the civ's currency to be numbered with the year it was minted.

|-
| {{text anchor|CURRENCY}}
|
* inorganic material
* value
| What kind of metals the civ uses for coin minting as well as the value of the coin.
[CURRENCY:SILVER:5]

|-
| {{text anchor|ART_FACET_MODIFIER}}
|
* type
* number
| OWN_RACE, FANCIFUL, EVIL, GOOD
Number goes from 0 to 25600 where 256 is the default.
[ART_FACET_MODIFIER:OWN_RACE:512]

|-
| {{text anchor|ART_IMAGE_ELEMENT_MODIFIER}}
|
* item
* number
| CREATURE, PLANT, TREE, SHAPE, ITEM 0-25600

Determines the chance of each image occurring in that entity's artwork, such as engravings and on artifacts, for default (non-historical) artwork.

[ART_IMAGE_ELEMENT_MODIFIER:TREE:512]

|-
| {{text anchor|ITEM_IMPROVEMENT_MODIFIER}}
|
* item
* number
| ART_IMAGE, COVERED or GLAZED, RINGS_HANGING, BANDS, SPIKES, ITEMSPECIFIC, THREAD, CLOTH, SEWN_IMAGE 0-25600

Determines the chance of the entity using that particular artwork method, such as "encircled with bands" or "menaces with spikes".

[ITEM_IMPROVEMENT_MODIFIER:SPIKES:0]

This also seems to change the amount that the entity will pay for items that are improved in the ways in their tokens.

|-
| {{text anchor|TRANSLATION}}
| language
| What language raw the entity uses.
* If an entity lacks this tag, translations appear to be drawn randomly from all translation files{{verify}}.
[TRANSLATION:DWARF]

|-
| {{text anchor|SELECT_SYMBOL}}
|
* noun
* symbol
| ALL, REMAINING, CIV, SITE, VESSEL, RELIGION, MILITARY_UNIT, TEMPLE, WAR, BATTLE, SIEGE, ROAD, BRIDGE, TUNNEL, WALL
Causes the entity to more often use these symbols in the particular SYM set.
[SELECT_SYMBOL:ALL:PEACE]

|-
| {{text anchor|SUBSELECT_SYMBOL}}
|
* noun
* symbol
| Unknown.

|-
| {{text anchor|CULL_SYMBOL}}
|
* noun
* symbol
| Causes the entity to not use the words in these SYM sets.
[CULL_SYMBOL:ALL:UGLY]

|-
| {{text anchor|FRIENDLY_COLOR}}
| see [[color]]
|
The color of this entity's civilization settlements in the world gen and embark screens. Defaults to 7:0:1.
[FRIENDLY_COLOR:1:0:1]

|}

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

|-
| {{text anchor|RELIGION}}
| type
|
* REGIONAL_FORCE: The creatures will worship a single force associated with their spheres. Currently hardcoded to only be associated with rivers and nature.
* PANTHEON: The creatures will worship a group of gods, each aligned with their spheres and other appropriate ones as well.

[RELIGION:PANTHEON]

|-
| {{text anchor|RELIGION_SPHERE}}
| sphere
| Can by any available [[Sphere]]. Multiple entries are possible. Choosing a religious sphere will automatically make its opposing sphere not possible for the species to have: adding WATER, for example, means the species will never get FIRE as a religious sphere.

[RELIGION_SPHERE:FORTRESSES]

|-
| {{text anchor|SPHERE_ALIGNMENT}}
|
* type
* number
|
This token forces an entity to favor or disfavor particular religious spheres, causing them to acquire those spheres more often when generating a pantheon.

[SPHERE_ALIGNMENT:TREES:512]

|}

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

|-
| {{text anchor|POSITION}}
| string
| Defines a leader/noble position for a civilization. These replace previous tags such as [MAYOR] and [CAN_HAVE_SITE_LEADER] and so on. To define a position further, see [[Position token]].

|-
| {{text anchor|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.

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

|}

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

|-
| {{text anchor|ETHIC}}
|
*behavior
*reaction
| Sets the civ's view of [[ethic]]s (certain behaviors), from capital punishment to completely acceptable. This also causes the civ to look upon opposing ethics with disfavor, if their reaction to it is opposing, and when at extremes (one ACCEPTABLE, another civ UNTHINKABLE for example) they will often go to war over it.
[ETHIC:EAT_SAPIENT_KILL:ACCEPTABLE]

|-
| {{text anchor|VALUE}}
|
*value
*number
| Sets the civ's cultural values. Numbers range from -50 (completely anathema) to 0 (neutral) to 50 (highly valued).
[VALUE:CRAFTSMANSHIP:50]

|-
| {{text anchor|WILL_ACCEPT_TRIBUTE}}
|
| Makes the civ's traders accept offered goods.

|-
| {{text anchor|WANDERER}}, {{text anchor|BEAST_HUNTER}}, {{text anchor|SCOUT}}
|
| The civ will send out these sorts of adventurers in worldgen. This seems to increase Tracker skill.

|-
| {{text anchor|ABUSE_BODIES}}
|
| The civilization will mutilate bodies when they are the victors in history-gen warfare, such as hanging bodies from trees, putting them on spikes, and so forth. Adventurers killed in Adventurer mode will sometimes be impaled on spikes wherever they died, with or without this token, and regardless of whether they actually antagonized the townspeople.

|-
| {{text anchor|ACTIVE_SEASON}}
| season
| the season when the civ is most active: when they will trade, interact with you via diplomats, and/or invade you. Civs can have multiple season entries. Note: If multiple caravans arrive at the same time, you are able to select which civ to trade with at the depot menu. ACTIVE_SEASON tags may be changed for a currently active fort.
[ACTIVE_SEASON:AUTUMN]

|-
| {{text anchor|AMBUSHER}}
|
| When invading sneaks around and shoots at straggling members of your society. They will spawn on the edge of the map and will only be visible when one of their party are spotted; this can be quite dangerous to undefended trade depots.

|-
| {{text anchor|AT_PEACE_WITH_WILDLIFE}}
|
| Will not attack wildlife, and will not be attacked by them, even if you have them in your party. This can be somewhat disconcerting when attacked by bears in the forest and your elven ally sits back and does nothing.

|-
| {{text anchor|BABYSNATCHER}}
|
| Sends thieves to steal babies. Also sends ambush parties to harass your civilization. Without this tag, enemy civs will only siege, and will siege as early as they would otherwise babysnatch. This can happen as early as the first year of the fort! In addition, babysnatcher civs will snatch children during worldgen, allowing them to become part of the civ if they do not escape.

Note: If the playable civ in Fortress Mode has this tag (i.e. you add BABYSNATCHER to the Dwarf entity) then the roles will be reversed and elves and humans will siege and ambush and goblins will trade with you.

|-
| {{text anchor|BUILDS_OUTDOOR_FORTIFICATIONS}}
|
| Makes the civilization build castles.

|-
| {{text anchor|BUILDS_OUTDOOR_TOMBS}}
|
| Makes the civilization build tombs.

|-
| {{text anchor|BANDITRY}}
| percentage
| Sets a percentage of the entity population to be used as bandits.

|-
| {{text anchor|DIPLOMAT_BODYGUARDS}}
|
| Visiting diplomats are accompanied by a pair of soldiers. Does not work due to a bug.{{bug|5854}}

|-
| {{text anchor|GENERATED}}
|
| Found on generated divine "HF Guardian Entities". Cannot be used in user-defined raws.

|-
| {{text anchor|INVADERS_IGNORE_NEUTRALS}}
|
| Causes invaders to ignore visiting caravans and other neutral creatures.{{verify}}

|-
| {{text anchor|ITEM_THIEF}}
|
| Sends thieves to steal items. This will also occur in history generation, and thieves will have the "thief" profession. Items stolen in history gen will be scattered around that creature's home.

|-
| {{text anchor|LOCAL_BANDITRY}}
|
| Causes the entity to send out patrols that can ambush adventurers. Will cause cities to be hostile to adventurers whenever they enter, regardless of race or nationality. Adding this tag to playable entities will also make adventurers with this token willing to move-attack non-hostile villagers, rather than having to make an aimed attack.

|-
| {{text anchor|MERCHANT_BODYGUARDS}}
|
| Caravan merchants are accompanied by soldiers.

|-
| {{text anchor|MERCHANT_NOBILITY}}
|
| Effect unknown - in previous versions, this resulted in the civ having a Guild Representative / Merchant Baron / Merchant Prince, but now this is controlled solely by positions.

|-
| {{text anchor|PROGRESS_TRIGGER_POPULATION}}
| level
| 0 to 5, civ will come to site once population at site has reached that level. If multiple progress triggers exist for a civ, it will come when any one of them is fulfilled instead of waiting for all of them to be reached. A value of 0 disables the trigger. 1 corresponds to 20 dwarves, 2 to 50 dwarves, 3 to 80, 4 to 110, and 5 to 140. Progress triggers may be changed, added, or deleted for a currently active fort. Note: hostile civs require that the population trigger be fulfilled as well as at least one other trigger before attacking.

|-
| {{text anchor|PROGRESS_TRIGGER_PRODUCTION}}
| level
| 0 to 5, civ will come to site once created wealth has reached that level. If multiple progress triggers exist for a civ, it will come when any one of them is fulfilled instead of waiting for all of them to be reached. A value of 0 disables the trigger. 1 corresponds to 5000☼ created wealth, 2 to 25000☼, 3 to 100000☼, 4 to 200000☼, and 5 to 300000☼. Progress triggers may be changed, added, or deleted for a currently active fort.

|-
| {{text anchor|PROGRESS_TRIGGER_TRADE}}
| level
| 0 to 5, civ will come to site once exported goods has reached that level. If multiple progress triggers exist for a civ, it will come when any one of them is fulfilled instead of waiting for all of them to be reached. A value of 0 disables the trigger. 1 corresponds to 500☼ exported wealth, 2 to 2500☼, 3 to 10000☼, 4 to 20000☼, and 5 to 30000☼. Progress triggers may be changed, added, or deleted for a currently active fort.

|-
| {{text anchor|PROGRESS_TRIGGER_POP_SIEGE}}
| level
| 0 to 5, civ will begin to send sieges against the player civ when this level is reached if it is hostile.

If multiple progress triggers exist for a civ, it will come when any one of them is fulfilled instead of waiting for all of them to be reached. A value of 0 disables the trigger.

|-
| {{text anchor|PROGRESS_TRIGGER_PROD_SIEGE}}
| level
| 0 to 5, civ will begin to send sieges against the player civ when this level is reached if it is hostile.

|-
| {{text anchor|PROGRESS_TRIGGER_TRADE_SIEGE}}
| level
| 0 to 5, civ will begin to send sieges against the player civ when this level is reached if it is hostile.

|-
| {{text anchor|SIEGER}}
|
| Will start campfires and wait around at the edge of your map for a month or two before rushing in to attack.

|-
| {{text anchor|SITE_GUARDIAN}}
|
| Guards certain special sites, such as a [[vault]] belonging to a [[demon]] allied with a [[deity]]. Used in generated divine entities.

|-
| {{text anchor|SKULKING}}
|
| This makes the severity of attacks depend on the extent of item/baby thievery rather than the passage of time. Makes trade impossible with the related civilization.

|-
| {{text anchor|TREE_CAP_DIPLOMACY}}
|
| Visiting diplomats impose tree cutting quotas; without this, they will simply compliment your fortress and leave. Also causes the diplomat to make unannounced first contact at the very beginning of the first Spring after your fortress becomes a Barony.

|-
| {{text anchor|LAYER_LINKED}}
|
| Defines if a civilization is a hidden subterranean entity, such as batman civilizations.

|-
| {{text anchor|UNDEAD_CANDIDATE}}
|
| Unknown. Possibly makes this creature available as a "Corpse" (e.g. Human Corpse) for necromancers in adventure mode.

|}

== Available Resources ==
{| {{prettytable}}
|- bgcolor="#ddd"
! Token
! Arguments
! Description

|-
| {{text anchor|AMMO}}
| item token
|
[AMMO:ITEM_AMMO_BOLTS]

|-
| {{text anchor|ARMOR}}
|
* item token
* rarity
|Rarity is optional. Permitted rarity values are RARE, UNCOMMON, FORCED (anything else is treated as COMMON).
[ARMOR:ITEM_ARMOR_PLATEMAIL:COMMON]

|-
| {{text anchor|DIGGER}}
| item token
|
[DIGGER:ITEM_WEAPON_PICK]

|-
| {{text anchor|GLOVES}}
|
* item token
* rarity
| Rarity is optional. Permitted rarity values are RARE, UNCOMMON, FORCED (anything else is treated as COMMON).
[GLOVES:ITEM_GLOVES_GLOVES:COMMON]

|-
| {{text anchor|HELM}}
|
* item token
* rarity
| Rarity is optional. Permitted rarity values are RARE, UNCOMMON, FORCED (anything else is treated as COMMON).
[HELM:ITEM_HELM_HELM:COMMON]

|-
| {{text anchor|INSTRUMENT}}
| item token
|
[INSTRUMENT:ITEM_INSTRUMENT_FLUTE]

|-
| {{text anchor|PANTS}}
|
* item token
* rarity
| Rarity is optional. Permitted rarity values are RARE, UNCOMMON, FORCED (anything else is treated as COMMON).
[PANTS:ITEM_PANTS_PANTS:COMMON]

|-
| {{text anchor|SHIELD}}
| item token
|
[SHIELD:ITEM_SHIELD_SHIELD]

|-
| {{text anchor|SHOES}}
|
* item token
* rarity
| Rarity is optional. Permitted rarity values are RARE, UNCOMMON, FORCED (anything else is treated as COMMON).
[SHOES:ITEM_SHOES_SHOES:COMMON]

|-
| {{text anchor|SIEGEAMMO}}
| item token
|
[SIEGEAMMO:ITEM_SIEGEAMMO_BALLISTA]

|-
| {{text anchor|TOOL}}
| item token
|
[TOOL:ITEM_TOOL_NEST_BOX]

|-
| {{text anchor|TOY}}
| item token
|
[TOY:ITEM_TOY_PUZZLEBOX]

|-
| {{text anchor|TRAPCOMP}}
| item token
|
[TRAPCOMP:ITEM_TRAPCOMP_GIANTAXEBLADE]

|-
| {{text anchor|WEAPON}}
| item token
|
[WEAPON:ITEM_WEAPON_AXE_BATTLE]

|-
| {{text anchor|USE_ANIMAL_PRODUCTS}}
|
| Allows civilization to use products made from animals. All relevant creatures will be able to provide wool, silk, and extracts (including milk and venom) for trade, and non-sentient creatures (unless ethics state otherwise) will be able to provide eggs, caught fish, meat, leather, bone, shell, pearl, horn, and ivory.

|-
| {{text anchor|USE_ANY_PET_RACE}}
|
| Any creature in the civilization's list of usables (from the surrounding 7x7 or so of squares and map features in those squares) which has PET or PET_EXOTIC will be available as a pet, pack animal (with PACK_ANIMAL), wagon puller (with WAGON_PULLER), mount (with MOUNT or MOUNT_EXOTIC), or siege minion (with TRAINABLE_WAR and ''without'' CAN_LEARN). This notion of the initial usable creature list, which then gets pared down or otherwise considered, applies below as well. All common domestic and equipment creatures are also added to the initial list.

|-
| {{text anchor|USE_CAVE_ANIMALS}}
|
| If they don't have it, creatures with exclusively subterranean biomes are skipped. If they have it, cave creatures with PET will also be available as pets, pack animals (with PACK_ANIMAL), wagon pullers (with WAGON_PULLER), mounts (with MOUNT or MOUNT_EXOTIC), and siege minions (with TRAINABLE_WAR and ''without'' CAN_LEARN).

|-
| {{text anchor|USE_EVIL_ANIMALS}}
|
| Don't have it -> EVIL creatures skipped. If they have it, evil creatures with SLOW_LEARNER or ''without'' CAN_LEARN will be also available as pets (with PET), pack animals (with PACK_ANIMAL), wagon pullers (with WAGON_PULLER), mounts (with MOUNT or MOUNT_EXOTIC), and siege minions (with TRAINABLE_WAR or SLOW_LEARNER).

|-
| {{text anchor|USE_EVIL_PLANTS}}
|
| As EVIL creatures for all uses of plants.

|-
| {{text anchor|USE_EVIL_WOOD}}
|
| As EVIL creatures for all uses of wood.

|-
| {{text anchor|USE_GOOD_ANIMALS}}
|
| Don't have it -> GOOD creatures skipped. If they have it, good creatures ''without'' CAN_LEARN will also be available as pets (with PET), pack animals (with PACK_ANIMAL), wagon pullers (with WAGON_PULLER), mounts (with MOUNT or MOUNT_EXOTIC), and siege minions (with TRAINABLE_WAR).

|-
| {{text anchor|USE_GOOD_PLANTS}}
|
| As GOOD creatures for all uses of plants.

|-
| {{text anchor|USE_GOOD_WOOD}}
|
| As GOOD creatures for all uses of wood.

|-
| {{text anchor|USE_MISC_PROCESSED_WOOD_PRODUCTS}}
|
| If the relevant professions are permitted, controls availability of lye (LYE_MAKING), charcoal (BURN_WOOD), and potash (POTASH_MAKING).

|-
| {{text anchor|COMMON_DOMESTIC_MOUNT}}
|
| Gives the civilization access to creatures with COMMON_DOMESTIC and MOUNT. Additionally, all available (based on USE_ANY_PET_RACE, USE_CAVE_ANIMALS, USE_GOOD_ANIMALS, and USE_EVIL_ANIMALS) creature with MOUNT and PET will be allowed for use as mounts during combat.

|-
| {{text anchor|COMMON_DOMESTIC_PACK}}
|
| Gives the civilization access to creatures with COMMON_DOMESTIC and PACK_ANIMAL. Additionally, all available (see above) creatures with PACK_ANIMAL and PET will be allowed for use during trade as pack animals.

|-
| {{text anchor|COMMON_DOMESTIC_PET}}
|
| Gives the civilization access to creatures with COMMON_DOMESTIC and PET. Additionally, all available (see above) creatures with PET will be allowed for use as pets.

|-
| {{text anchor|COMMON_DOMESTIC_PULL}}
|
| Gives the civilization access to creatures with COMMON_DOMESTIC and WAGON_PULLER. Additionally, all available (see above) creatures with WAGON_PULLER and PET will be allowed for use during trade to pull [[wagon]]s.

|-
| {{text anchor|RIVER_PRODUCTS}}
|
| Allow civ to use river products in the goods it has available for trade.

|-
| {{text anchor|OCEAN_PRODUCTS}}
|
| Allow civ to use ocean products (including [[amber]] and [[coral]]) in the goods it has available for trade. Without OCEAN_PRODUCTS, civilizations will not be able to trade ocean fish even if they are ''also'' available from other sources (e.g. [[sturgeon]]s and [[stingray]]s).

|-
| {{text anchor|INDOOR_FARMING}}
|
| Allow civ to use underground plant products in the goods it has available for trade.

|-
| {{text anchor|OUTDOOR_FARMING}}
|
| Allow civ to use outdoor plant products in the goods it has available for trade.

|-
| {{text anchor|INDOOR_GARDENS}}
|
| Allow civ to use underground plant growths (quarry bush leaves in unmodded games) in the goods it has available for trade.

|-
| {{text anchor|OUTDOOR_GARDENS}}
|
| Allow civ to use outdoor plant growths in the goods it has available for trade.

|-
| {{text anchor|OUTDOOR_ORCHARDS}}
|
| Allows civ to use outdoor tree growths in the goods it has available for trade.

|-
| {{text anchor|CLOTHING}}
|
| Civ members will attempt to wear clothing.

|-
| {{text anchor|SUBTERRANEAN_CLOTHING}}
|
| Will wear things made of spider silk and other subterranean materials.

|-
| {{text anchor|EQUIPMENT_IMPROVEMENTS}}
|
| Adds decorations to equipment based on the level of the generated unit. Also improves item quality.

|-
| {{text anchor|IMPROVED_BOWS}}
|
| Adds decorations to weapons generated for bowman and master bowman. An elf hack.

|-
| {{text anchor|METAL_PREF}}
|
| Allows metal materials to be used to make cages (inexpensive metals only) and crafts.

|-
| {{text anchor|STONE_PREF}}
|
| Allows the civilization to make use of nearby stone types. If the FURNACE_OPERATOR job is permitted, also allows ore-bearing stones to be smelted into metals.

|-
| {{text anchor|WOOD_WEAPONS}}
|
| The civilization can make traditionally metallic weapons such as swords and spears from wood. An elf hack.

|-
| {{text anchor|WOOD_ARMOR}}
|
| The civilization can make traditionally metallic armor such as mail shirts and helmets from wood. An elf hack.

|-
| {{text anchor|GEM_PREF}}
|
| Enables creatures of this entity to bring gems in trade.

|-
| {{text anchor|INDOOR_WOOD}}
|
| Allow civ to use subterranean wood types, such as tower-cap and fungiwood logs.

|-
| {{text anchor|OUTDOOR_WOOD}}
|
| Allow civ to use outdoor wood types, such as mangrove and oak.

|-
| {{text anchor|GEM_SHAPE}}
| [[Descriptor shape token|shape]]
| Precious gems cut by this civilization's jewelers can be of this shape.

|-
| {{text anchor|STONE_SHAPE}}
| [[Descriptor shape token|shape]]
| Ordinary non-gem stones cut by this civilization's jewelers can be of this shape.

|-
| {{text anchor|DIVINE_MAT_CLOTH}}
|
| Allows civ to use materials with [DIVINE] for clothing. Used for generated divine entities.

|-
| {{text anchor|DIVINE_MAT_WEAPONS}}
|
| Allows civ to use metals with [DIVINE] for weapons. Used for generated divine entities.

|-
| {{text anchor|DIVINE_MAT_ARMOR}}
|
| Allows civ to use metals with [DIVINE] for armour. Used for generated divine entities.

|}

== Tissue Styling Related Tokens ==
{| {{prettytable}}
|- bgcolor="#ddd"
! Token
! Arguments
! Description

|-
| {{text anchor|TISSUE_STYLE}}
| tissue style unit ID
| Select tissue layer which have the ID attached using TISSUE_STYLE_UNIT token in unit raws. This allows setting further cultural style parameters for selected tissue layer.

|-
| {{text anchor|TS_MAINTAIN_LENGTH}}
|
* minimum length?
* maximum length?
| Presumably sets culturally preferred tissue length for selected tissue. Needs testing.
Dwarves have their beards set to 100:NONE by default.

|-
| {{text anchor|TS_PREFERRED_SHAPING}}
| styling token
| Valid tokens are NEATLY_COMBED, BRAIDED, DOUBLE_BRAIDS, PONY_TAILS, CLEAN_SHAVEN and STANDARD_HAIR/BEARD/MOUSTACHE/SIDEBURNS_SHAPINGS.
Presumably sets culturally preferred tissue shapings for selected tissue. Needs testing.

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

v0.31:Bolt

2014-05-26T19:05:45Z

Dirst: /* Masterwork Bolts */ Fixed typo.

{{quality|Fine|11:53, 26 December 2010 (UTC)}}{{buggy}}{{av}}

[[Ammunition]] for [[crossbow]]s. Can be made from [[wood]], [[bone]], or weapon-grade [[metal]]s.

Wooden and metal bolts produce a [[stack]] of 25 per [[log]] or [[bar]].

Making bone bolts will take only one bone away from a stack and turn it into 5 bolts.

Wooden and bone bolts are made in a [[Craftsdwarf's workshop]]. Metal bolts are forged at a [[Metalsmith's forge]] or [[Magma forge]].

Wooden bolts use the Woodcrafting skill to make. Bone bolts require Bonecrafting and metal bolts require Weaponsmithing (not Metalcrafting).
[[Quiver]]s are always required for bolts to be equipped.

When fired, Bolts have a chance of shattering on impact or bouncing off and being able to be reclaimed- However, when on the ground they are forbidden.

Tests show that where even masterwork wooden bolts bounce harmlessly off copper armor, iron bolts pierce without any issue. Bone bolts are significantly better than wood, but metal bolts are still recommended for military use.

==Masterwork Bolts==
As with other items, high-skill dwarves can make masterwork-[[Item quality|quality]] bolts. While they don't care if the bolts are fired and shatter on impact, they do get upset if a bolt gets carried off - say by a retreating enemy with the bolt stuck in him. Unfortunately, dwarves also get upset if you melt down individual masterwork bolts, which are otherwise nearly useless.

The simplest remedy for this is to simply '''make more bolts''' - a dwarf who has produced hundreds of masterwork bolts will be more annoyed by [[fly|flies]] than the loss of a masterwork.

==Bugs==
Tests show that bone and wooden bolts are effective against most{{verify}} unarmored targets, like wildlife, but for various reasons are quite useless against some other creatures and armored targets.

The same goes for some metal bolts (silver, copper) with variations depending on the precise metal.{{verify}}

Bone bolts are not advisable for weapon traps as only a stack of 5 will be stored per crossbow, making frequent restocking necessary.

It is largely unclear what of the above constitutes a bug and what is intended behaviour.

*If squad is assigned multiple ammo types, dwarves with "individual choice ranged" carry wrong ammo{{bug|1374}}.
*Masterwork bolts cause unhappy thoughts when they get carried off the map or melted down{{bug|3169}}.

{{gamedata|[ITEM_AMMO:ITEM_AMMO_BOLTS]
[NAME:bolt:bolts]
[CLASS:BOLT]
[SIZE:50]
[ATTACK:EDGE:100:2000:stab:stabs:NO_SUB:1000]
}}

v0.34:Goshenite

2014-05-26T19:00:49Z

Dirst: Added a small amount of description.

{{Quality|Fine}}{{gemlookup/0}}{{av}}

'''Goshenite''' is a semi-precious colorless beryl [[gem]] found in small clusters within layers of [[granite]], [[schist]] and [[marble]].

{{gamedata}}
{{gems}}

v0.34 Talk:Personality facet

2014-04-26T14:54:15Z

Dirst: /* "Trait bins as found examining 16000 dwarves" */

I suspect that the "modesty" personality trait affects the thoughts dwarves get from lack of clothing in the most recent versions. I've got 2 dwarves in my fort who are/were flashing "unhappy". Both of these dwarves had the "no shoes recently" thought, and both also had the "finds immodesty distateful" trait. Presumably other dwarves were also missing shoes (I've got > 180 dwarves), but only these two were unhappy enough to flash the orange bang. Needs more science. --[[User:Greycat|Greycat]] 20:21, 8 April 2012 (UTC)

I'm fairly certain that the "imagination" trait results in more vivid descriptions of decorations such as statues and engravings, however I haven't tested this in any kind of organized way; just noticed far fewer engravings of 'a dwarf' when I make those with higher tokens stone detailers, and instead see historical events and scenes. That may simply be coincidence, however. -- Anonymous 05:46, 3 June 2012 (UTC)

Also, I'm pretty sure it means higher rate of masterwork item creation. On my most recent embark, my now-Great carpenter already has a disproportional number of masterworks to his name. I think it's related, but I am using a lot of wood, so take it with a grain of salt.--[[Special:Contributions/141.219.230.93|141.219.230.93]] 20:35, 8 October 2012 (UTC)

Artistic trait is related to the strength of the thought associated with admiring an object. A dwarf with a low artistic trait, like my current duke, will be "sleeping in a good bedroom/dining in a good dining room" or "admiring fine furniture/traps" even though the pieces/room he's interacting with are worth tens of thousands of dwarfbucks.
:I don't see this pattern in my fort of 107 dwarves. Much more evidence would be required to prove a personality trait claim.--[[User:UristDaVinci|UristDaVinci]] 03:59, 15 December 2012 (UTC)
Seems that you're right. I generated a world with 0:0:0 artistic_interest and my dwarves still had the appropriate thoughts for the bedrooms they owned.

== "Trait bins as found examining 16000 dwarves" ==

What is the purpose of this section? It appears to be notes on a private study, and seems it would be rather illegible to the casual DFwiki reader. Heck, I like to think of myself as more than casual, and I really have no idea what is going on there.

It needs to be updated with an introduction explaining the significance of the work being presented, or it should be moved here to the discussion page until it is ready for proper, complete presentation on the live page. --[[User:777|777]] 17:09, 21 October 2012 (UTC)

I think that it's referring to normal models. I really can't understand what it's saying, so it's a bit more difficult to figure out than it should be. [[User:Putnam3145|Putnam]] 20:14, 28 October 2012 (UTC)

Someone pulled my non normal trait conversion info off the wiki... didnt even bother putting it into the discussion section... anyways... ill try updating it once again [Thistleknot]

Okay, for now, I'm just pasting this here
It is possible to skew non normal traits to the normal breakdown as listed on the wiki.

Example: For 45 Mean Traits (Immoderation I believe is one), by stretching 0 to 45 to 0 to 50, and 55 to 100 to 50 to 100.

Requires an if check and a formula similar to this:

Example: Converting + Traits to Normal

=IF(Value<=55,(Value/55)*50,(((Value-55)/45)*50)+50)

I need this info here for future research purposes. Thx!

Would it be possible for whoever created the 16000 dwarves to post the data here on the Discussion page in 1-point bins? That should make it possible to figure out the distribution. The description of a "bell curve with fat tails" could indicate a censored normal distribution, a t distribution, or a beta distribution. It's virtually impossible to tell these apart with such wide bins. [[User:Dirst|Dirst]] ([[User talk:Dirst|talk]]) 14:54, 26 April 2014 (UTC)

== Updated Rating ==

Reading through this article, I had no idea why it was listed as 'tattered', so I went ahead and upgraded it to Exceptional, based upon the rating script's recommendation. Since it's a jump of two rank levels, feel free to revert down to Fine if you think Exceptional is too generous. [[User:August|August]] 05:53, 8 February 2013 (UTC)

== -23032 in Thrill seeking... ==

anyone else have had this bug ? my dwarff Tholtig Dasëlasob is "Entirely adverse to risk and excitement". which is no surprice as his raw is -23032 as seen in Dwarff Therapist...
http://www4.picturepush.com/photo/a/13237107/img/13237107.png

Yes, "we" believe this is a "true" bug in the game. I don't know if it's been reported to the bugtracker ( http://www.bay12games.com/dwarves/mantisbt/print_all_bug_page.php ), but if not, please do, but it's been addressed in Splinterz version of Dwarf Therapist, but maybe not enough if the bug isn't fixed.