v0.31 Talk:XML dump

2011-07-09T22:09:24Z

MrSparks:

I haven't spotted anything like an "hf born" event. Anyone know if some other event is filling in for that, or is that one of the bits of data that's still not in the dump? [[User:Bryan Derksen|Bryan Derksen]] 07:20, 25 July 2010 (UTC)
: I don't think that's in there at all, sadly. The best you can do is find the earliest event by them and take that as their birth, It's seems like that might work. [[User:Mason11987|Mason]] <sup>([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]])</sup> 13:11, 25 July 2010 (UTC)
:: It's in the place where the hf is declared as birth_year. Which still doesn't help with making family trees. [[User:MrSparks|MrSparks]] 22:09, 9 July 2011 (UTC)

== List of Events ==

Per Toady:

"Some of them aren't in use:"
*<type>field battle</type>
*<type>attacked site</type>
*<type>destroyed site</type>
*<type>plundered site</type>
*<type>site tribute forced</type>
*<type>new site leader</type>
*<type>site taken over</type>
*<type>hf destroyed site</type>
*<type>site died</type>
*<type>site abandoned</type>
*<type>created site</type>
*<type>created structure</type>
*<type>replaced structure</type>
*<type>razed structure</type>
*<type>hf razed structure</type>
*<type>created world construction</type>
*<type>reclaim site</type>
*<type>creature devoured</type>
*<type>hf wounded</type>
*<type>hf simple battle event</type>
*<type>hf reach summit</type>
*<type>hf travel</type>
*<type>hf new pet</type>
*<type>hf reunion</type>
*<type>hf died</type>
*<type>hf abducted</type>
*<type>add hf entity link</type>
*<type>remove hf entity link</type>
*<type>change hf state</type>
*<type>change hf job</type>
*<type>add hf hf link</type>
*<type>remove hf hf link</type>
*<type>add hf site link</type>
*<type>remove hf site link</type>
*<type>first contact</type>
*<type>first contact failed</type>
*<type>agreement concluded</type>
*<type>agreement rejected</type>
*<type>agreement made</type>
*<type>peace accepted</type>
*<type>peace rejected</type>
*<type>diplomat lost</type>
*<type>body abused</type>
*<type>agreement void</type>
*<type>merchant</type>
*<type>artifact hidden</type>
*<type>artifact possessed</type>
*<type>artifact created</type>
*<type>artifact lost</type>
*<type>artifact found</type>
*<type>item stolen</type>
*<type>artifact recovered</type>
*<type>artifact dropped</type>
*<type>entity created</type>
*<type>entity incorporated</type>
*<type>masterpiece arch design</type>
*<type>masterpiece arch constructed</type>
*<type>masterpiece item</type>
*<type>masterpiece dye</type>
*<type>masterpiece item improvement</type>
*<type>masterpiece food</type>
*<type>masterpiece engraving</type>
*<type>masterpiece lost</type>
*<type>impersonate hf</type>
*<type>create entity position</type>

collections
*<type>war</type>
*<type>battle</type>
*<type>duel</type>
*<type>site conquered</type>
*<type>abduction</type>
*<type>theft</type>
*<type>beast attack</type>
*<type>journey</type>

v0.31:Power

2011-07-03T22:22:26Z

MrSparks: /* Frozen Components*/--slightly expanded explanation of the freezing concept

{{quality|Exceptional|21:03, 26 April 2011 (UTC)}}{{av}}

{{L|Power}} is used to drive devices that perform tasks normally done by dwarves, such as {{L|pump}}ing {{L|water}} using a {{L|screw pump}} or {{L|mill}}ing certain types of {{L|food}} into {{L|flour}} at a {{L|millstone}}. Power is produced by {{L|windmill}}s and {{L|water wheel}}s.
==Power requirements==
*{{L|Axle}}: (1) per tile (horizontal axles and verticle axles both)
*{{L|Gear assembly}}: (5)
*{{L|Millstone}}: (10)
*{{L|Pump}}: (10)

==Power transfer==

Power can be transferred between devices using {{L|gear assembly|gear assemblies}} and {{L|axle}}s. Axles transfer power in a single direction -- north, south, east, west, up, or down. Axles are classified as "horizontal" or "vertical", with the former going north/south or east/west, and with the latter going up or down Z levels. Horizontal axles may be built individually up to 10 tiles long; if you want a longer axle, you may simply build two or more of them in a line; you don't need gear assemblies between them. Vertical axles are always placed one tile at a time.

Gear assemblies take up a single tile and transfer power to any device within the six orthogonally adjacent tiles (north, south, east, west, above, below). Gear assemblies are best used for moving power through right-angles. For example, they can be built as bases for windmills to move power out sideways along an axle.

Because of the high power use of gear assemblies (5), axles are more appropriate and convenient to build when transferring power across horizontal or vertical distances. An axle uses (1) power for every tile of power transfer. An axle 5 tiles long will use (5) power. Axles can be directly attached to windmills, waterwheels and screw pumps in order to provide power. For security, one can make a axle-train cross a moat by first going down the moat, across, and then up. Or perhaps a screw pump will make a floor-type security-wall for a downward axle.

Devices that use power are also capable of transferring it. Adjacent screw pumps will transfer power between themselves. The only way to prevent this is to leave a tile gap between devices, or move them diagonally from each other.

==Frozen Components==
Machine components on ice will freeze solid. This also causes all connected components to stop working.
When you look at a component using 'q' you see if the component is 'frozen'(not working because it is frozen solid) or if it's "frozen elsewhere"(not working because another component is frozen solid)

Dwarf Fortress Wiki - User contributions [en]

v0.31 Talk:XML dump

v0.31:Power