Dwarf Fortress Wiki - User contributions [en]

User:HebaruSan/2010 Notes

2010-05-18T03:29:22Z

HebaruSan:

Notes on my experiences with the 2010 releases.

== Razorclear ==
Since magma is allegedly no longer hard to come by, I selected a half-mountain, half-forest site with a stream running through the middle and no aquifer. I think there's some flux.

=== Initial skills ===
I want to experiment with one-skill-per-dwarf, one-dwarf-per-skill for civilians, more to minimize task conflicts than as a challenge. Anyone leftover goes to the military.

For the initial load-out, this means maxing out 7 skills important to the early game. For now I'll also violate my 1-per-1 rule by assigning each specialist a significantly less useful, thematically related minor (or a useful skill related to the same main task, as with trading).

{| class="wikitable"
|+ Founders, "The Courageous Lance"
! Tulon Ginetreg
| Grower || Herbalist
|-
! Lor Eralbab
| Mechanic || Trapper
|-
! Reg Liruknish
| Fighter, Wrestler, Striker, Kicker, Dodger || Ambusher
|-
! Iden Likoturrith
| Miner || Building Designer
|-
! Iton Kakdalsibrek
| Brewer || Milker
|-
! Zuglar Lilumolin
| Appraiser || Negotiator
|-
! Zulban Thimshurerith
| Fighter, Wrestler, Striker, Kicker, Dodger || Ambusher
|}
Things I'll be hoping for from (or assigning to) early immigrants:
* Carpenter
* Mason
* Woodcutter
* Cook
* Record Keeper
Later:
* Engraver
* Weaponsmith
* Armorsmith
* Physician
* Bowyer

=== Gear ===
Conventional wagon-load of tools and rations; not looking for a challenge in this area.
* 1 each of many, many 2-point meats, to see if this brings a huge surplus of free barrels.
* 4 dogs, 3 female for parallelized pregnancies.

=== Ambitions ===
* Heavy use of traffic designations to help processing speed
* Attempt to navigate the 0.31.x military screen
** Rest/train/patrol schedules
* Design a good alert/burrow scheme

=== Learnings and observations ===
* <s>Only one of my hunters got free leather armor and a crossbow. So that's either a limit or a bug; either way, one skill point wasted.</s>
** Nope, they both got everything, but their first actions were to drop it all on the ground when I turned off their Hunting labors, and only one of them had done that when I checked!
* {{k|N}}oble screen started with broker, bookkeeper, and manager vacant.
* {{k|D}}epot command displayed but disabled rather than hidden.
* My brewer and planter both show up as Farmer.
* Even with zero frames elapsed, saving took a '''very''' long time.

=== Bugs ===
[[File:Df031-viewport.png|thumb|right|Display shifted downward]]
* Tried the 800x600 font with 80x50 resolution; the display is shifted downward by somewhat less than half its height. Changing back to 80x25 fixes this.
* Yesterday I saw the issue where resizing the window blanks it. But now that's fine; I think the only thing I changed was to use the 800x600 font. This doesn't even have the above artifact with the black space at the top!
* If these flashing question marks and this "Pickup Equipment" action are any indication, designating with the mouse still causes a (partial?) tick of the world clock, similar to pressing {{k|.}}.

User:HebaruSan/2010 Notes

2010-05-18T03:10:25Z

HebaruSan:

Notes on my experiences with the 2010 releases.

== Razorclear ==
Since magma is allegedly no longer hard to come by, I selected a half-mountain, half-forest site with a stream running through the middle and no aquifer. I think there's some flux.

=== Initial skills ===
I want to experiment with one-skill-per-dwarf, one-dwarf-per-skill for civilians, more to minimize task conflicts than as a challenge. Anyone leftover goes to the military.

For the initial load-out, this means maxing out 7 skills important to the early game. For now I'll also violate my 1-per-1 rule by assigning each specialist a significantly less useful, thematically related minor (or a useful skill related to the same main task, as with trading).

{| class="wikitable"
|+ Founders, "The Courageous Lance"
! Tulon Ginetreg
| Grower || Herbalist
|-
! Lor Eralbab
| Mechanic || Trapper
|-
! Reg Liruknish
| Fighter, Wrestler, Striker, Kicker, Dodger || Ambusher
|-
! Iden Likoturrith
| Miner || Building Designer
|-
! Iton Kakdalsibrek
| Brewer || Milker
|-
! Zuglar Lilumolin
| Appraiser || Negotiator
|-
! Zulban Thimshurerith
| Fighter, Wrestler, Striker, Kicker, Dodger || Ambusher
|}
Things I'll be hoping for from (or assigning to) early immigrants:
* Carpenter
* Mason
* Woodcutter
* Cook
* Record Keeper
Later:
* Engraver
* Weaponsmith
* Armorsmith
* Physician
* Bowyer

=== Gear ===
Conventional wagon-load of tools and rations; not looking for a challenge in this area.
* 1 each of many, many 2-point meats, to see if this brings a huge surplus of free barrels.
* 4 dogs, 3 female for parallelized pregnancies.

=== Ambitions ===
* Heavy use of traffic designations to help processing speed
* Attempt to navigate the 0.31.x military screen
** Rest/train/patrol schedules
* Design a good alert/burrow scheme

=== Learnings and observations ===
* Only one of my hunters got free leather armor and a crossbow. So that's either a limit or a bug; either way, one skill point wasted.
* {{k|N}}oble screen started with broker, bookkeeper, and manager vacant.
* {{k|D}}epot command displayed but disabled rather than hidden.
* My brewer and planter both show up as Farmer.
* Even with zero frames elapsed, saving took a '''very''' long time.

=== Bugs ===
[[File:Df031-viewport.png|thumb|right|Display shifted downward]]
* Tried the 800x600 font with 80x50 resolution; the display is shifted downward by somewhat less than half its height. Changing back to 80x25 fixes this.
* Yesterday I saw the issue where resizing the window blanks it. But now that's fine; I think the only thing I changed was to use the 800x600 font. This doesn't even have the above artifact with the black space at the top!
* If these flashing question marks and this "Pickup Equipment" action are any indication, designating with the mouse still causes a (partial?) tick of the world clock, similar to pressing {{k|.}}.

User:HebaruSan/2010 Notes

2010-05-18T03:08:48Z

HebaruSan:

Notes on my experiences with the 2010 releases.

== Razorclear ==
Since magma is allegedly no longer hard to come by, I selected a half-mountain, half-forest site with a stream running through the middle and no aquifer. I think there's some flux.

=== Initial skills ===
I want to experiment with one-skill-per-dwarf, one-dwarf-per-skill for civilians, more to minimize task conflicts than as a challenge. Anyone leftover goes to the military.

For the initial load-out, this means maxing out 7 skills important to the early game. For now I'll also violate my 1-per-1 rule by assigning each specialist a significantly less useful, thematically related minor (or a useful skill related to the same main task, as with trading).

{| class="wikitable"
|+ Founders, "The Courageous Lance"
! Tulon Ginetreg
| Grower || Herbalist
|-
! Lor Eralbab
| Mechanic || Trapper
|-
! Reg Liruknish
| Fighter, Wrestler, Striker, Kicker, Dodger || Ambusher
|-
! Iden Likoturrith
| Miner || Building Designer
|-
! Iton Kakdalsibrek
| Brewer || Milker
|-
! Zuglar Lilumolin
| Appraiser || Negotiator
|-
! Zulban Thimshurerith
| Fighter, Wrestler, Striker, Kicker, Dodger || Ambusher
|}
Things I'll be hoping for from (or assigning to) early immigrants:
* Carpenter
* Mason
* Woodcutter
* Cook
* Record Keeper
Later:
* Engraver
* Weaponsmith
* Armorsmith
* Physician
* Bowyer

=== Gear ===
Conventional wagon-load of tools and rations; not looking for a challenge in this area.
* 1 each of many, many 2-point meats, to see if this brings a huge surplus of free barrels.
* 4 dogs, 3 female for parallelized pregnancies.

=== Ambitions ===
* Heavy use of traffic designations to help processing speed
* Attempt to navigate the 0.31.x military screen
** Rest/train/patrol schedules
* Design a good alert/burrow scheme

=== Learnings and observations ===
* Only one of my hunters got free leather armor and a crossbow. So that's either a limit or a bug; either way, one skill point wasted.
* {{k|N}}oble screen started with broker, bookkeeper, and manager vacant.
* {{k|D}}epot command displayed but disabled rather than hidden.
* My brewer and planter both show up as Farmer.
* Even with zero frames elapsed, saving took a '''very''' long time.

=== Bugs ===
[[File:Df031-viewport.png|thumb|right|Display shifted downward]]
* Tried the 800x600 font with 80x50 resolution; the display is shifted downward by somewhat less than half its height. Changing back to 80x25 fixes this.
* Yesterday I saw the issue where resizing the window blanks it. But now that's fine; I think the only thing I changed was to use the 800x600 font. This doesn't even have the above artifact with the black space at the top!

User:HebaruSan/2010 Notes

2010-05-18T03:02:37Z

HebaruSan:

Notes on my experiences with the 2010 releases.

== Razorclear ==
Since magma is allegedly no longer hard to come by, I selected a half-mountain, half-forest site with a stream running through the middle and no aquifer. I think there's some flux.

=== Initial skills ===
I want to experiment with one-skill-per-dwarf, one-dwarf-per-skill for civilians, more to minimize task conflicts than as a challenge. Anyone leftover goes to the military.

For the initial load-out, this means maxing out 7 skills important to the early game. For now I'll also violate my 1-per-1 rule by assigning each specialist a significantly less useful, thematically related minor (or a useful skill related to the same main task, as with trading).

{| class="wikitable"
|+ Founders, "The Courageous Lance"
! Tulon Ginetreg
| Grower || Herbalist
|-
! Lor Eralbab
| Mechanic || Trapper
|-
! Reg Liruknish
| Fighter, Wrestler, Striker, Kicker, Dodger || Ambusher
|-
! Iden Likoturrith
| Miner || Building Designer
|-
! Iton Kakdalsibrek
| Brewer || Milker
|-
! Zuglar Lilumolin
| Appraiser || Negotiator
|-
! Zulban Thimshurerith
| Fighter, Wrestler, Striker, Kicker, Dodger || Ambusher
|}
Things I'll be hoping for from (or assigning to) early immigrants:
* Carpenter
* Mason
* Woodcutter
* Cook
* Record Keeper
Later:
* Engraver
* Weaponsmith
* Armorsmith
* Physician
* Bowyer

=== Gear ===
Conventional wagon-load of tools and rations; not looking for a challenge in this area.
* 1 each of many, many 2-point meats, to see if this brings a huge surplus of free barrels.
* 4 dogs, 3 female for parallelized pregnancies.

=== Ambitions ===
* Heavy use of traffic designations to help processing speed
* Attempt to navigate the 0.31.x military screen
** Rest/train/patrol schedules
* Design a good alert/burrow scheme

=== Learnings and observations ===
* Only one of my hunters got free leather armor and a crossbow. So that's either a limit or a bug; either way, one skill point wasted.
* {{k|N}}oble screen started with broker, bookkeeper, and manager vacant.
* {{k|D}}epot command displayed but disabled rather than hidden.
* My brewer and planter both show up as Farmer.
* Even with zero frames elapsed, saving took a '''very''' long time.

=== Bugs ===
[[File:Df031-viewport.png|thumb|right|Display shifted downward]]
* Tried the 800x600 font with 80x50 resolution; the display is shifted downward by somewhat less than half its height.

File:Df031-viewport.png

2010-05-18T03:00:18Z

HebaruSan: Looks like there's still a hard-coded assumption of 25 lines somewhere.

Looks like there's still a hard-coded assumption of 25 lines somewhere.

User:HebaruSan/2010 Notes

2010-05-18T02:58:15Z

HebaruSan:

Notes on my experiences with the 2010 releases.

== Razorclear ==
Since magma is allegedly no longer hard to come by, I selected a half-mountain, half-forest site with a stream running through the middle and no aquifer. I think there's some flux.

=== Initial skills ===
I want to experiment with one-skill-per-dwarf, one-dwarf-per-skill for civilians, more to minimize task conflicts than as a challenge. Anyone leftover goes to the military.

For the initial load-out, this means maxing out 7 skills important to the early game. For now I'll also violate my 1-per-1 rule by assigning each specialist a significantly less useful, thematically related minor (or a useful skill related to the same main task, as with trading).

{| class="wikitable"
|+ Founders, "The Courageous Lance"
! Tulon Ginetreg
| Grower || Herbalist
|-
! Lor Eralbab
| Mechanic || Trapper
|-
! Reg Liruknish
| Fighter, Wrestler, Striker, Kicker, Dodger || Ambusher
|-
! Iden Likoturrith
| Miner || Building Designer
|-
! Iton Kakdalsibrek
| Brewer || Milker
|-
! Zuglar Lilumolin
| Appraiser || Negotiator
|-
! Zulban Thimshurerith
| Fighter, Wrestler, Striker, Kicker, Dodger || Ambusher
|}
Things I'll be hoping for from (or assigning to) early immigrants:
* Carpenter
* Mason
* Woodcutter
* Cook
* Record Keeper
Later:
* Engraver
* Weaponsmith
* Armorsmith
* Physician
* Bowyer

=== Gear ===
Conventional wagon-load of tools and rations; not looking for a challenge in this area.
* 1 each of many, many 2-point meats, to see if this brings a huge surplus of free barrels.
* 4 dogs, 3 female for parallelized pregnancies.

=== Ambitions ===
* Heavy use of traffic designations to help processing speed
* Attempt to navigate the 0.31.x military screen
** Rest/train/patrol schedules
* Design a good alert/burrow scheme

=== Learnings and observations ===
* Only one of my hunters got free leather armor and a crossbow. So that's either a limit or a bug; either way, one skill point wasted.
* {{k|N}}oble screen started with broker, bookkeeper, and manager vacant.
* {{k|D}}epot command displayed but disabled rather than hidden.
* My brewer and planter both show up as Farmer.
* Even with zero frames elapsed, saving took a '''very''' long time.

=== Bugs ===
* Tried the 800x600 font with 80x50 resolution; the display is shifted downward by somewhat less than half its height.

User:HebaruSan/2010 Notes

2010-05-18T02:14:02Z

HebaruSan: Created page with 'Notes on my experiences with the 2010 releases. == Razorclear == Since magma is allegedly no longer hard to come by, I selected a half-mountain, half-forest site with a stream r…'

User:HebaruSan

2010-05-18T01:28:57Z

HebaruSan:

__NOTOC__
{| class="wikitable" border="1" cellspacing="0" cellpadding="2"
! Preferred Tileset
| [[Tileset_repository#Kein|Kein]] for its blend of tradition and innovation
|-
! Playing Version
| {{version|0.31.04}}
|-
! Platform
| Mac
|}
I'm a programmer (personally and professionally). I like roguelikes (ascended one barbarian in Nethack) and try to work on them, but don't have anything impressive to show you.

== Reasons for Playing Dwarf Fortress ==
* Open-endedness
* Watching my designs play out
* Appreciating its complexity and intricacy

== Future Goals and Aspirations ==
=== Wiki ===
* Simulate social networking sites' "Like" buttons without spamming/vandalizing categories all over the place.
* Rewrite [[Dwarven physics]] in the in-character voice of a dwarven physicist explaining it to us backward humans, attributing the "discrepancies" not to differences in ''physics'', but to the advanced state of dwarven knowledge. Superior dwarven science has unlocked the secret of explosion-less item annihilation and perpetual motion machines (maybe they're related!).
* Animation template
** <nowiki>{{anim|%|÷}}{{anim|%|÷}}</nowiki> for an active [[screw pump]]
** <nowiki>{{anim|*|☼}}</nowiki> for an active [[gear assembly]]
** <nowiki>{{anim|o|○}}</nowiki> for an active [[millstone]]
*: ab
Things that belong toward the top of [[Special:WantedPages|WantedPages]] (good content could live there) and will appear there by virtue of being linked here:
* [[World map]]
* [[Decoration Industry]]
* [[Arms Industry]]
* [[Keep]]

=== In-game ===
There are several canonical Dwarf Fortress scenarios that I have yet to try or achieve.
* Find "[[Hidden Fun Stuff]]" and avoid spoilers until I do
* Kill, rather than capture, a [[megabeast]]
* Tame a [[Giant eagle]]
* Provoke war with the [[Elf|Elves]]
* Lose to invaders, then reclaim
* Abandon, then visit as adventurer

==== Streamlined bait-based drowning chamber with looting tray ====
Inspired by [http://mkv25.net/dfma/movie-1093-drowningchamber3 Lumpy McUglyFace's drowning chamber] and [http://mkv25.net/dfma/movie-1782-automaticobsidianfactory Quietust's obsidian factory].

Side view:
_______
░.§D.¢░ [[Trap design#Bait animals|Bait animal]], [[hatch cover]] at stairs
___┼____<%% [[Pressure plate]] (not shown), entrance [[door]], [[bridge]], [[stairs]] up, [[screw pump]] (right to left)
.g.▲░░ _____%%≈░ [[Floor grate]]s, internal access, [[screw pump]] (left to right)
░░░░░ ▲░≈≈≈≈≈░░░░ River
When a goblin enters to attack the animal, a pressure plate sets the trap in motion.
# Entrance door sealed shut.
# Hatch cover to upper floor sealed shut.
# Pumps activate, water fills the chamber.
# Time passes.
# Pumps shut off.
# Bridge retracts.
## Water falls through grate to river.
## Corpses and loot land on top of grate.
# Bridge re-extends.
# Hatch cover opens.
# Door opens.
Advantages:
* Bait animal is safe and therefore doesn't need to be replaced.
* Looting tray allows safe retrieval of narrow giant cave spider silk items, at your haulers' leisure.
* No important items in the chamber means dwarves won't get in the way.
* No way for invaders to get into your fortress.
* No manual intervention required.
* Bridge over river affords quick and easy drainage.
Challenges and risks:
* Pressure plate placement; should go outside to allow entire interior to be bridge, but then the timing is very delicate.
** May need to put the plate just outside the door and add a delay.
* Automation is hard.

== Ideas for [[Challenges]] ==

=== Simulate 9/11 ===
Build a pair of very tall, identical towers, using supports, and collapse them both. Two variants:
# Make the links between the walls and the floors tenuous, and simulate "pancaking" as magma ("jet fuel") causes them to weaken and give way.
# Controlled demolition with thermite.
* BONUS: Fill the towers with goblin cages and release them all just in time to be crushed.

=== Megaplumbing ===
Sanitation is one of the primary concerns of city planners, yet most dwarves have no place to use the restroom. Yours will!

Build a giant white stone toilet that flushes, including bowl, tank, handle, and seat. Deviate from realism as little as possible. Use it to dispose of hostile captives.

[http://mkv25.net/dfma/movie-245-flushingtoilet GauHelldragon already did this]! Further suggestions:
* Don't flood the whole map.
* Emulate real toilets' mechanism for stopping flow and refilling the tank automatically.

=== Turnover ===
A mysterious poltergeist in your region takes an unorthodox approach to avoiding overcrowding.
# Construct a large suicide chamber or many small ones, capable of liquidating a whole fortress's population.
# At the start of each migration wave, execute all of your residents and let the migrants take over a vacant fortress.

* Since your population is always new, there is not enough time to build up high levels of skill.
* On the other hand, relationships would also remain relatively shallow.
* Special care must be taken to protect incoming migrants since wiping them out now causes the whole fortress to fail.
* Keeping the fortress secure while it's empty has to be balanced against allowing the migrants to enter. Bridges controlled by indoor and outdoor levers may be one approach.

* BONUS: Try to time it well enough to reduce your population briefly to 1 incoming migrant!

= Fortresses =
Recalling memories of fortresses is fun. Here are some of mine.

== Region 1 (Name lost to the mists of time) ==
{| class="wikitable" style="float:right;margin-left:2em;" border="1" cellspacing="0" cellpadding="2"
! Population
| 7 [[dwarves]], probably; can't imagine this one getting [[immigrants]]
|}
I believe I [[Reclaim fortress mode|abandoned]] this fortress after getting a basic sense of how to play and an understanding of this fortress' non-viability, then started Region 2 in the same [[world]].
=== Noteworthy Occurrences ===
* Took a while to figure out how to get my dwarves to do things. They idled while I learned [[Controls|keystrokes]].
* [[Miner]] got stuck somehow after falling in a hole.
* Fortress layout was partly [[Light|outdoors]], partly wide-open non-defensible underground area.
* Ran out of [[trees]]. Then found a bunch more after discovering the existence of [[Z-axis|Z-levels]]!
{{:User:HebaruSan/Roughnessclasp}}
{{:User:HebaruSan/Perplexedrag}}
{{:User:HebaruSan/Machinehall}}
== Adventure ==
Sometime between Machinehall and Blockedbridge, I created a world in which to try [[Adventure Mode]]. The framerate was very slow and I was unable to find anything to do. I wandered through an [[Elf|Elven]] settlement talking to its residents, but none of them seemed to be the quest boss I wanted to meet, and I had no way to locate him. I decided that if I wanted a single-character questing experience, I could go play Nethack or Crawl instead, whereas [[Dwarf fortress mode]] is far more novel and interesting. Perma-saved.
{{:User:HebaruSan/Blockedbridge}}

User:HebaruSan

2010-05-18T01:28:37Z

HebaruSan:

__NOTOC__
{| class="wikitable" border="1" cellspacing="0" cellpadding="2"
! Preferred Tileset
| [[Tileset_repository#Kein|Kein]] for its blend of tradition and innovation
|-
! Playing Version
| {{version|0.31.04}}
|-
! Platform
|
Mac
|}
I'm a programmer (personally and professionally). I like roguelikes (ascended one barbarian in Nethack) and try to work on them, but don't have anything impressive to show you.

== Reasons for Playing Dwarf Fortress ==
* Open-endedness
* Watching my designs play out
* Appreciating its complexity and intricacy

== Future Goals and Aspirations ==
=== Wiki ===
* Simulate social networking sites' "Like" buttons without spamming/vandalizing categories all over the place.
* Rewrite [[Dwarven physics]] in the in-character voice of a dwarven physicist explaining it to us backward humans, attributing the "discrepancies" not to differences in ''physics'', but to the advanced state of dwarven knowledge. Superior dwarven science has unlocked the secret of explosion-less item annihilation and perpetual motion machines (maybe they're related!).
* Animation template
** <nowiki>{{anim|%|÷}}{{anim|%|÷}}</nowiki> for an active [[screw pump]]
** <nowiki>{{anim|*|☼}}</nowiki> for an active [[gear assembly]]
** <nowiki>{{anim|o|○}}</nowiki> for an active [[millstone]]
*: ab
Things that belong toward the top of [[Special:WantedPages|WantedPages]] (good content could live there) and will appear there by virtue of being linked here:
* [[World map]]
* [[Decoration Industry]]
* [[Arms Industry]]
* [[Keep]]

=== In-game ===
There are several canonical Dwarf Fortress scenarios that I have yet to try or achieve.
* Find "[[Hidden Fun Stuff]]" and avoid spoilers until I do
* Kill, rather than capture, a [[megabeast]]
* Tame a [[Giant eagle]]
* Provoke war with the [[Elf|Elves]]
* Lose to invaders, then reclaim
* Abandon, then visit as adventurer

==== Streamlined bait-based drowning chamber with looting tray ====
Inspired by [http://mkv25.net/dfma/movie-1093-drowningchamber3 Lumpy McUglyFace's drowning chamber] and [http://mkv25.net/dfma/movie-1782-automaticobsidianfactory Quietust's obsidian factory].

Side view:
_______
░.§D.¢░ [[Trap design#Bait animals|Bait animal]], [[hatch cover]] at stairs
___┼____<%% [[Pressure plate]] (not shown), entrance [[door]], [[bridge]], [[stairs]] up, [[screw pump]] (right to left)
.g.▲░░ _____%%≈░ [[Floor grate]]s, internal access, [[screw pump]] (left to right)
░░░░░ ▲░≈≈≈≈≈░░░░ River
When a goblin enters to attack the animal, a pressure plate sets the trap in motion.
# Entrance door sealed shut.
# Hatch cover to upper floor sealed shut.
# Pumps activate, water fills the chamber.
# Time passes.
# Pumps shut off.
# Bridge retracts.
## Water falls through grate to river.
## Corpses and loot land on top of grate.
# Bridge re-extends.
# Hatch cover opens.
# Door opens.
Advantages:
* Bait animal is safe and therefore doesn't need to be replaced.
* Looting tray allows safe retrieval of narrow giant cave spider silk items, at your haulers' leisure.
* No important items in the chamber means dwarves won't get in the way.
* No way for invaders to get into your fortress.
* No manual intervention required.
* Bridge over river affords quick and easy drainage.
Challenges and risks:
* Pressure plate placement; should go outside to allow entire interior to be bridge, but then the timing is very delicate.
** May need to put the plate just outside the door and add a delay.
* Automation is hard.

== Ideas for [[Challenges]] ==

=== Simulate 9/11 ===
Build a pair of very tall, identical towers, using supports, and collapse them both. Two variants:
# Make the links between the walls and the floors tenuous, and simulate "pancaking" as magma ("jet fuel") causes them to weaken and give way.
# Controlled demolition with thermite.
* BONUS: Fill the towers with goblin cages and release them all just in time to be crushed.

=== Megaplumbing ===
Sanitation is one of the primary concerns of city planners, yet most dwarves have no place to use the restroom. Yours will!

Build a giant white stone toilet that flushes, including bowl, tank, handle, and seat. Deviate from realism as little as possible. Use it to dispose of hostile captives.

[http://mkv25.net/dfma/movie-245-flushingtoilet GauHelldragon already did this]! Further suggestions:
* Don't flood the whole map.
* Emulate real toilets' mechanism for stopping flow and refilling the tank automatically.

=== Turnover ===
A mysterious poltergeist in your region takes an unorthodox approach to avoiding overcrowding.
# Construct a large suicide chamber or many small ones, capable of liquidating a whole fortress's population.
# At the start of each migration wave, execute all of your residents and let the migrants take over a vacant fortress.

* Since your population is always new, there is not enough time to build up high levels of skill.
* On the other hand, relationships would also remain relatively shallow.
* Special care must be taken to protect incoming migrants since wiping them out now causes the whole fortress to fail.
* Keeping the fortress secure while it's empty has to be balanced against allowing the migrants to enter. Bridges controlled by indoor and outdoor levers may be one approach.

* BONUS: Try to time it well enough to reduce your population briefly to 1 incoming migrant!

= Fortresses =
Recalling memories of fortresses is fun. Here are some of mine.

== Region 1 (Name lost to the mists of time) ==
{| class="wikitable" style="float:right;margin-left:2em;" border="1" cellspacing="0" cellpadding="2"
! Population
| 7 [[dwarves]], probably; can't imagine this one getting [[immigrants]]
|}
I believe I [[Reclaim fortress mode|abandoned]] this fortress after getting a basic sense of how to play and an understanding of this fortress' non-viability, then started Region 2 in the same [[world]].
=== Noteworthy Occurrences ===
* Took a while to figure out how to get my dwarves to do things. They idled while I learned [[Controls|keystrokes]].
* [[Miner]] got stuck somehow after falling in a hole.
* Fortress layout was partly [[Light|outdoors]], partly wide-open non-defensible underground area.
* Ran out of [[trees]]. Then found a bunch more after discovering the existence of [[Z-axis|Z-levels]]!
{{:User:HebaruSan/Roughnessclasp}}
{{:User:HebaruSan/Perplexedrag}}
{{:User:HebaruSan/Machinehall}}
== Adventure ==
Sometime between Machinehall and Blockedbridge, I created a world in which to try [[Adventure Mode]]. The framerate was very slow and I was unable to find anything to do. I wandered through an [[Elf|Elven]] settlement talking to its residents, but none of them seemed to be the quest boss I wanted to meet, and I had no way to locate him. I decided that if I wanted a single-character questing experience, I could go play Nethack or Crawl instead, whereas [[Dwarf fortress mode]] is far more novel and interesting. Perma-saved.
{{:User:HebaruSan/Blockedbridge}}

User:HebaruSan

2010-05-18T01:07:22Z

HebaruSan: /* In-game */

__NOTOC__
{| class="wikitable" border="1" cellspacing="0" cellpadding="2"
! Preferred Tileset
| [[Tileset_repository#Kein|Kein]] for its blend of tradition and innovation
|-
! Playing Version
| {{version|0.28.181.40d16}}
|-
! Platforms
|
* Mac
* Windows
|}
I'm a programmer (personally and professionally). I like roguelikes (ascended one barbarian in Nethack) and try to work on them, but don't have anything impressive to show you.

== Reasons for Playing Dwarf Fortress ==
* Open-endedness
* Watching my designs play out
* Appreciating its complexity and intricacy

== Future Goals and Aspirations ==
=== Wiki ===
* Simulate social networking sites' "Like" buttons without spamming/vandalizing categories all over the place.
* Rewrite [[Dwarven physics]] in the in-character voice of a dwarven physicist explaining it to us backward humans, attributing the "discrepancies" not to differences in ''physics'', but to the advanced state of dwarven knowledge. Superior dwarven science has unlocked the secret of explosion-less item annihilation and perpetual motion machines (maybe they're related!).
* Animation template
** <nowiki>{{anim|%|÷}}{{anim|%|÷}}</nowiki> for an active [[screw pump]]
** <nowiki>{{anim|*|☼}}</nowiki> for an active [[gear assembly]]
** <nowiki>{{anim|o|○}}</nowiki> for an active [[millstone]]
*: ab
Things that belong toward the top of [[Special:WantedPages|WantedPages]] (good content could live there) and will appear there by virtue of being linked here:
* [[World map]]
* [[Decoration Industry]]
* [[Arms Industry]]
* [[Keep]]

=== In-game ===
There are several canonical Dwarf Fortress scenarios that I have yet to try or achieve.
* Find "[[Hidden Fun Stuff]]" and avoid spoilers until I do
* Kill, rather than capture, a [[megabeast]]
* Tame a [[Giant eagle]]
* Provoke war with the [[Elf|Elves]]
* Lose to invaders, then reclaim
* Abandon, then visit as adventurer

==== Streamlined bait-based drowning chamber with looting tray ====
Inspired by [http://mkv25.net/dfma/movie-1093-drowningchamber3 Lumpy McUglyFace's drowning chamber] and [http://mkv25.net/dfma/movie-1782-automaticobsidianfactory Quietust's obsidian factory].

Side view:
_______
░.§D.¢░ [[Trap design#Bait animals|Bait animal]], [[hatch cover]] at stairs
___┼____<%% [[Pressure plate]] (not shown), entrance [[door]], [[bridge]], [[stairs]] up, [[screw pump]] (right to left)
.g.▲░░ _____%%≈░ [[Floor grate]]s, internal access, [[screw pump]] (left to right)
░░░░░ ▲░≈≈≈≈≈░░░░ River
When a goblin enters to attack the animal, a pressure plate sets the trap in motion.
# Entrance door sealed shut.
# Hatch cover to upper floor sealed shut.
# Pumps activate, water fills the chamber.
# Time passes.
# Pumps shut off.
# Bridge retracts.
## Water falls through grate to river.
## Corpses and loot land on top of grate.
# Bridge re-extends.
# Hatch cover opens.
# Door opens.
Advantages:
* Bait animal is safe and therefore doesn't need to be replaced.
* Looting tray allows safe retrieval of narrow giant cave spider silk items, at your haulers' leisure.
* No important items in the chamber means dwarves won't get in the way.
* No way for invaders to get into your fortress.
* No manual intervention required.
* Bridge over river affords quick and easy drainage.
Challenges and risks:
* Pressure plate placement; should go outside to allow entire interior to be bridge, but then the timing is very delicate.
** May need to put the plate just outside the door and add a delay.
* Automation is hard.

== Ideas for [[Challenges]] ==

=== Simulate 9/11 ===
Build a pair of very tall, identical towers, using supports, and collapse them both. Two variants:
# Make the links between the walls and the floors tenuous, and simulate "pancaking" as magma ("jet fuel") causes them to weaken and give way.
# Controlled demolition with thermite.
* BONUS: Fill the towers with goblin cages and release them all just in time to be crushed.

=== Megaplumbing ===
Sanitation is one of the primary concerns of city planners, yet most dwarves have no place to use the restroom. Yours will!

Build a giant white stone toilet that flushes, including bowl, tank, handle, and seat. Deviate from realism as little as possible. Use it to dispose of hostile captives.

[http://mkv25.net/dfma/movie-245-flushingtoilet GauHelldragon already did this]! Further suggestions:
* Don't flood the whole map.
* Emulate real toilets' mechanism for stopping flow and refilling the tank automatically.

=== Turnover ===
A mysterious poltergeist in your region takes an unorthodox approach to avoiding overcrowding.
# Construct a large suicide chamber or many small ones, capable of liquidating a whole fortress's population.
# At the start of each migration wave, execute all of your residents and let the migrants take over a vacant fortress.

* Since your population is always new, there is not enough time to build up high levels of skill.
* On the other hand, relationships would also remain relatively shallow.
* Special care must be taken to protect incoming migrants since wiping them out now causes the whole fortress to fail.
* Keeping the fortress secure while it's empty has to be balanced against allowing the migrants to enter. Bridges controlled by indoor and outdoor levers may be one approach.

* BONUS: Try to time it well enough to reduce your population briefly to 1 incoming migrant!

= Fortresses =
Recalling memories of fortresses is fun. Here are some of mine.

== Region 1 (Name lost to the mists of time) ==
{| class="wikitable" style="float:right;margin-left:2em;" border="1" cellspacing="0" cellpadding="2"
! Population
| 7 [[dwarves]], probably; can't imagine this one getting [[immigrants]]
|}
I believe I [[Reclaim fortress mode|abandoned]] this fortress after getting a basic sense of how to play and an understanding of this fortress' non-viability, then started Region 2 in the same [[world]].
=== Noteworthy Occurrences ===
* Took a while to figure out how to get my dwarves to do things. They idled while I learned [[Controls|keystrokes]].
* [[Miner]] got stuck somehow after falling in a hole.
* Fortress layout was partly [[Light|outdoors]], partly wide-open non-defensible underground area.
* Ran out of [[trees]]. Then found a bunch more after discovering the existence of [[Z-axis|Z-levels]]!
{{:User:HebaruSan/Roughnessclasp}}
{{:User:HebaruSan/Perplexedrag}}
{{:User:HebaruSan/Machinehall}}
== Adventure ==
Sometime between Machinehall and Blockedbridge, I created a world in which to try [[Adventure Mode]]. The framerate was very slow and I was unable to find anything to do. I wandered through an [[Elf|Elven]] settlement talking to its residents, but none of them seemed to be the quest boss I wanted to meet, and I had no way to locate him. I decided that if I wanted a single-character questing experience, I could go play Nethack or Crawl instead, whereas [[Dwarf fortress mode]] is far more novel and interesting. Perma-saved.
{{:User:HebaruSan/Blockedbridge}}

User:HebaruSan/Blockedbridge

2010-05-18T01:05:51Z

HebaruSan:

__NOTOC__
<includeonly>
{| class="wikitable collapsible collapsed" width="100%"
!
</includeonly>
== Region 5, Rifotsazir, "Blockedbridge" ==
<includeonly>
|-
|
</includeonly>
{| class="wikitable" style="float:right;margin-left:2em;" border="1" cellspacing="0" cellpadding="2"
! Settled by
| The Merchants of Closing
|-
! House Rules
| [[Dwarven Economy|[ZERO_RENT:YES] ]]
|-
! Created [[wealth]]
| {{Money|8,435,373}}
|-
! Population
| 214 [[dwarves]]
126 [[animals]]
|-
! Deaths
| 5 dwarves
7 dogs
|-
! [[Artifacts]]
|
* Leather [[Clothes|thong]]
* Tower-cap [[armor stand]]
* 3 [[Trade good#Crafts|Scepters]]
* [[Mace]]
* [[Chain mail]]
* [[Trade good#Instruments|Flute]]
* Red flash opal [[table]]
* [[Trade good#Instruments|Harp]]
* [[Door]]
* [[Bracelet]]
* [[Coffer]]
* [[Weapon rack]]
* [[Earring]]
* [[Braies]]
* [[Chain]]
* [[Idol]]
|-
! [[Nobles]]
|
* [[Dungeon Master]] ([[underground river]])
* [[Duke/Duchess|Duchess]]
* [[Duke/Duchess Consort|Duke Consort]]
* [[Philosopher]]
* [[Tax Collector]]
* [[Hammerer]]
|-
! [[Military]]
|
27 [[Champions]]
|}
<includeonly>
: ''([[User:HebaruSan/Blockedbridge|main article]])''

</includeonly>I used the [[site finder]], with the only search parameter being the presence of a [[magma pipe]], then carved the bottom [[Z-axis|Z-level]] into 5x10 chunks without finding one. However, I did eventually notice some [[Frogman]] bones in my [[stocks]]. Sure enough, these had sunk to the bottom of an undiscovered [[underground river]].

I also got tired of under-building squalid hovels for my gloriously wealthy tribesdwarves, so I turned off [[Dwarven economy|rent]]. My long-term plan is to build better and better housing, and as they move into it, knock out the walls between older rooms to upgrade them. I might try enabling rent again in future versions if it becomes possible to undercut rents with a housing supply glut.

Much of the created wealth is due to micro-management of [[Strange mood]]s; virtually all artifacts were made from [[native platinum]], raw [[demantoid]], [[aluminum]] bars, [[platinum]] bars, giant cave spider [[silk]], sasquatch [[leather]], giant cave spider [[chitin]], [[Gem|star sapphires]], and [[Gem|clear diamonds]].

When the [[Dungeon Master]] finally arrived, her hood was decorated with an image of Blockedbridge's prized legendary mace. Apparently she was a fan.

=== [[Aquifer]] Prequel ===
My initial plan was to dig this fortress under a [[human]] town, so I selected a site with one. The [[site finder]] courteously warned me in the strongest possible terms that there was an [[aquifer]] at this location, which could seriously hinder my progress. This warning fully indemnified the [[site finder]] as far as I was concerned; however, I had never seen an aquifer before and succumbed to my curiosity.

We arrived in the town and began digging at its center. Five levels of ramp and side-passages were designated in a fit of optimism. Two levels down, the dirt gave way to water, and the remaining designations became a cruel joke, taunting their creators. After a brief attempt to pump out enough liquid to allow further descent, we returned to the surface, re-packed the wagon, wished the [[human]] townsfolk well, and set off for the mountains, where dwarvenkind belongs.

=== Stockpile [[Fun]] and Reclamation ===
Blockedbridge got off to a promising start, with the initial layout carved and all the industries ramping up. Then the [[brewer]] cancelled his task for lack of an empty [[barrel]]. There were plenty of barrels around, but they were all full of food. This seemed to be the result of a stockpiling error; there was a food-and-drink pile but no drinks-only pile, and so the [[kitchen]] outstripped the [[still]] and used up all the barrels. A plague of thirst swept the fortress, and as attempts were made to restart ale production, one of the fortress's most beloved legendary denizens perished. This was deemed an appropriate occasion for [[fun]]; all attempts at survival were forgotten, and Blockedbridge focused on leaving a good-looking corpse.

The entrance was sealed, trapping a [[human]] trade delegation inside with the dwarves. Several new butcher shops were hastily erected to slaughter all the remaining animals. An engraver of legendary skill was sent to the tombs to chronicle the ongoing tragedy in stone. One by one, thirst overtook them all, in some cases while they were carrying another's remains to the cemetery.

As soon as news of Blockedbridge's fall reached the mountainhomes, a band of dwarven warriors set out to revive it, confident that they could succeed where the previous crew had failed. They found an unoccupied, ransacked, but otherwise safe fortress and set to work restoring it. They were ''very'' careful to designate a substantial drinks-only stockpile. This group welcomed many emigres from elsewhere, and today Blockedbridge is a thriving dwarven metropolis.

Of the trapped humans, some later died defending Blockedbridge, several rejoined their countrymen upon their next visit, and one remains to the present day.

=== Notable Features ===
* No [[water]] until [[underground river]] was found
** Minor injuries became death sentences
* Wall around entire map makes the surface safe for dwarvenkind
** Exterior [[Soldier|patrolled]] by [[Champions]]
** [[Ramp]] under wall to tunnel for [[Wagon]]s
* Central [[ramp]] down to (previous) [[trade depot]] location
** 3-tile wide hallways going north/south/east/west from center
** Up/down [[stairs]] in hallways every 20 tiles
* Tower-cap farm
* 8-[[Siege engine|catapult]] training center feeds stoneworking shops
* Embassy Suites:
...╠═════╬═════╣
...║♫....║....Æ║
...┼..╤╥.┼..θ..║
...║√....║....π║
...╠═════╬═════╣
...║√....║....π║
...┼..╤╥.┼..θ..║
...║♫....║....Æ║
...╠═════╬═════╣
...║♫....║....Æ║
...┼..╤╥.┼..θ..║
...║√....║....π║
...╠═════╬═════╣

<includeonly>
|}
</includeonly>

User:HebaruSan/Blockedbridge

2010-05-18T01:05:27Z

HebaruSan:

__NOTOC__
<includeonly>
{| class="wikitable collapsible collapsed"
!
</includeonly>
== Region 5, Rifotsazir, "Blockedbridge" ==
<includeonly>
|-
|
</includeonly>
{| class="wikitable" style="float:right;margin-left:2em;" border="1" cellspacing="0" cellpadding="2"
! Settled by
| The Merchants of Closing
|-
! House Rules
| [[Dwarven Economy|[ZERO_RENT:YES] ]]
|-
! Created [[wealth]]
| {{Money|8,435,373}}
|-
! Population
| 214 [[dwarves]]
126 [[animals]]
|-
! Deaths
| 5 dwarves
7 dogs
|-
! [[Artifacts]]
|
* Leather [[Clothes|thong]]
* Tower-cap [[armor stand]]
* 3 [[Trade good#Crafts|Scepters]]
* [[Mace]]
* [[Chain mail]]
* [[Trade good#Instruments|Flute]]
* Red flash opal [[table]]
* [[Trade good#Instruments|Harp]]
* [[Door]]
* [[Bracelet]]
* [[Coffer]]
* [[Weapon rack]]
* [[Earring]]
* [[Braies]]
* [[Chain]]
* [[Idol]]
|-
! [[Nobles]]
|
* [[Dungeon Master]] ([[underground river]])
* [[Duke/Duchess|Duchess]]
* [[Duke/Duchess Consort|Duke Consort]]
* [[Philosopher]]
* [[Tax Collector]]
* [[Hammerer]]
|-
! [[Military]]
|
27 [[Champions]]
|}
<includeonly>
: ''([[User:HebaruSan/Blockedbridge|main article]])''

</includeonly>I used the [[site finder]], with the only search parameter being the presence of a [[magma pipe]], then carved the bottom [[Z-axis|Z-level]] into 5x10 chunks without finding one. However, I did eventually notice some [[Frogman]] bones in my [[stocks]]. Sure enough, these had sunk to the bottom of an undiscovered [[underground river]].

I also got tired of under-building squalid hovels for my gloriously wealthy tribesdwarves, so I turned off [[Dwarven economy|rent]]. My long-term plan is to build better and better housing, and as they move into it, knock out the walls between older rooms to upgrade them. I might try enabling rent again in future versions if it becomes possible to undercut rents with a housing supply glut.

Much of the created wealth is due to micro-management of [[Strange mood]]s; virtually all artifacts were made from [[native platinum]], raw [[demantoid]], [[aluminum]] bars, [[platinum]] bars, giant cave spider [[silk]], sasquatch [[leather]], giant cave spider [[chitin]], [[Gem|star sapphires]], and [[Gem|clear diamonds]].

When the [[Dungeon Master]] finally arrived, her hood was decorated with an image of Blockedbridge's prized legendary mace. Apparently she was a fan.

=== [[Aquifer]] Prequel ===
My initial plan was to dig this fortress under a [[human]] town, so I selected a site with one. The [[site finder]] courteously warned me in the strongest possible terms that there was an [[aquifer]] at this location, which could seriously hinder my progress. This warning fully indemnified the [[site finder]] as far as I was concerned; however, I had never seen an aquifer before and succumbed to my curiosity.

We arrived in the town and began digging at its center. Five levels of ramp and side-passages were designated in a fit of optimism. Two levels down, the dirt gave way to water, and the remaining designations became a cruel joke, taunting their creators. After a brief attempt to pump out enough liquid to allow further descent, we returned to the surface, re-packed the wagon, wished the [[human]] townsfolk well, and set off for the mountains, where dwarvenkind belongs.

=== Stockpile [[Fun]] and Reclamation ===
Blockedbridge got off to a promising start, with the initial layout carved and all the industries ramping up. Then the [[brewer]] cancelled his task for lack of an empty [[barrel]]. There were plenty of barrels around, but they were all full of food. This seemed to be the result of a stockpiling error; there was a food-and-drink pile but no drinks-only pile, and so the [[kitchen]] outstripped the [[still]] and used up all the barrels. A plague of thirst swept the fortress, and as attempts were made to restart ale production, one of the fortress's most beloved legendary denizens perished. This was deemed an appropriate occasion for [[fun]]; all attempts at survival were forgotten, and Blockedbridge focused on leaving a good-looking corpse.

The entrance was sealed, trapping a [[human]] trade delegation inside with the dwarves. Several new butcher shops were hastily erected to slaughter all the remaining animals. An engraver of legendary skill was sent to the tombs to chronicle the ongoing tragedy in stone. One by one, thirst overtook them all, in some cases while they were carrying another's remains to the cemetery.

As soon as news of Blockedbridge's fall reached the mountainhomes, a band of dwarven warriors set out to revive it, confident that they could succeed where the previous crew had failed. They found an unoccupied, ransacked, but otherwise safe fortress and set to work restoring it. They were ''very'' careful to designate a substantial drinks-only stockpile. This group welcomed many emigres from elsewhere, and today Blockedbridge is a thriving dwarven metropolis.

Of the trapped humans, some later died defending Blockedbridge, several rejoined their countrymen upon their next visit, and one remains to the present day.

=== Notable Features ===
* No [[water]] until [[underground river]] was found
** Minor injuries became death sentences
* Wall around entire map makes the surface safe for dwarvenkind
** Exterior [[Soldier|patrolled]] by [[Champions]]
** [[Ramp]] under wall to tunnel for [[Wagon]]s
* Central [[ramp]] down to (previous) [[trade depot]] location
** 3-tile wide hallways going north/south/east/west from center
** Up/down [[stairs]] in hallways every 20 tiles
* Tower-cap farm
* 8-[[Siege engine|catapult]] training center feeds stoneworking shops
* Embassy Suites:
...╠═════╬═════╣
...║♫....║....Æ║
...┼..╤╥.┼..θ..║
...║√....║....π║
...╠═════╬═════╣
...║√....║....π║
...┼..╤╥.┼..θ..║
...║♫....║....Æ║
...╠═════╬═════╣
...║♫....║....Æ║
...┼..╤╥.┼..θ..║
...║√....║....π║
...╠═════╬═════╣

<includeonly>
|}
</includeonly>

User:HebaruSan/Machinehall

2010-05-18T01:04:13Z

HebaruSan:

__NOTOC__
<includeonly>
{| class="wikitable collapsible collapsed"
!
</includeonly>
== Region 4, Mountainhome Stâkudîton Zustashizkilgostaban Bëmbul, "Machinehall the Ancient Intricate Arch-Construct of Mechanisms" ==
<includeonly>
|-
|
</includeonly>
{| class="wikitable" style="float:right;margin-left:2em;" border="1" cellspacing="0" cellpadding="2"
! Settled by
| Truestrike the Courageous Loyal Rock-Band of Beards
|-
! Created [[wealth]]
| {{Money|3,359,388}}
|-
! Population
| 170 [[dwarves]]
480 [[animals]]
|-
! Deaths
| 25 dwarves
32 dogs
|-
! [[Artifacts]]
|
* [[Trade good#Instruments|Piccolo]]
* 6 [[Trade good#Crafts|Bracelets]]
* 2 [[Mechanisms]]
* [[Trade good#Toys|Toy axe]]
* [[Blowgun]]
* Leather [[Clothes|shirt]]
* [[Trade good#Instruments|Harp]]
* Right [[gauntlet]]
* [[Animal trap]]
* [[Clothes|Trousers]]
* [[Crossbow]]
* [[Trade good#Crafts|Idol]]
* Leather [[Clothes|face veil]]
* [[Bed]]
* Left [[gauntlet]]
|-
! [[Nobles]]
|
* [[Dungeon Master]] ([[River#Surface Rivers|surface river]])
* [[Duke/Duchess]]
* [[Duke/Duchess Consort]]
* [[Philosopher]]
* [[Tax Collector]]
* [[Hammerer]]
* [[King Consort]]
* [[Queen]] (deceased)
|-
! [[Military]]
|
* 2 [[Champions]]
* 14 [[Marksdwarves]] (3 Elite)
* 1 [[Speardwarf]]
* 1 [[Hammerdwarf]]
* 1 [[Axedwarf]]
* 1 [[Swordsdwarf]]
* 2 [[Macedwarf|Macedwarves]]
* 11 [[Fortress guard#The Royal Guards|Royal Guards]]
|}
<includeonly>
: ''([[User:HebaruSan/Machinehall|main article]])''

</includeonly>I got ambitious and carefully customized the fortress and party [[Name]]s before [[embark]].

Machinehall was built in two phases:
# Complex I: Single 32x32 room
#* [[Workshops]] along the walls
#* [[Stockpiles]] in the middle
#* [[Defense design#Goblin detour|Kinked entry passage]] with [[fortifications]] for [[marksdwarves]]
#* [[Well]] and [[waterfall]] in one corner
# Complex II: 17 15x15 levels, with a helix [[ramp]] in the center
#* Planned [[waterfall]] in the center of the ramp (never tested)
#* Each level dedicated to a specific [[industry]] or activity
Unfortunately, these complexes are not close together, and the transition is taking a very long time. Currently most dwarves in Machinehall can be found [[Traffic|walking in the long tunnel]] between them.

=== Queen Saga ===
Eventually, Machinehall grew enough to attract the interest of royalty. After an artifact mechanism was used in a [[Road|drawbridge]], Queen Lorbam Äkiltosid arrived and proclaimed her [[Noble#Room Requirements|demands for the finest, most lavish accommodations]] imaginable. Plans for such were drawn up immediately, and work began. Not fast enough for Her Royal Highness, however; with each passing day, the [[Thought#Unhappy thoughts|indignity of her condition weighed upon the noble monarch]], until finally one day [[Insanity|it was all too much]].

Lorbam Äkiltosid, Queen has gone stark raving mad!

She wandered aimlessly, overcome with despair. Where had she gone wrong? Surely road value is an excellent way to choose where to live! Eventually, the Queen threw herself into Machinehall Complex II's 17-level dry waterfall.

Lorbam Äkiltosid, Queen has died after colliding with an obstacle.

And her subjects [[Tantrum|mourned]]. Or at least I assume they will; the loss of the Queen prompted me to save my game (and not come back to it yet).

=== Other Events ===
* First [[Tax Collector]] [[Mandate]]d items made from unavailable [[materials]].
** Innocent craftdwarf was [[Justice|blamed, charged, and executed]]!
** Some time later, the Tax Collector was found starved to death in his [[Door#Door settings|locked]] quarters.
* First production of [[glass]] and [[soap]].
* Dug out most of bottom Z-level without finding [[magma pipe]].

=== Celebrities ===
* Mayor Ïteb Zasurrïth
** Legendary Record Keeper
** Legendary Appraiser
** Legendary Organizer
** Undefeated in all [[Leader#Mayor|elections]] since founding
** Big fan of [[iron]] and [[doors]]
* First legendary mechanic, Bim Suvasbomrek
** Decided she was Machinehall's de facto matron
** Built her an office/dining/bedroom complex using her favorite materials
* First legendary stonecrafter, Ustuth Inethurol
** Creator of many excellent [[native gold]] [[mugs]]
* Legendary Bone Carver, Led Tizötdodók
** Creator of a continuous stream of [[Item quality#Masterpiece|masterpieces]]

=== Features ===
* Champions [[Defense design#Defending the edge|patrolling edges of map]]
* Wall around roughly 100x100 area above ground for [[Wood cutter|safe forestry]]
* Museum containing [[artifacts]] and two [[Cage trap|captured]] [[Megabeast]]s
* 5-target archery practice hall with captive-release area near targets
* [[Dwarven economy|Low-income housing district]] in sandy area to handle Dwarven economy
* Spiral wall entrance, never tested
** Maximizes length of path per surface area occupied
** Overlooked by fortified marksdwarf tower
Level 0:
...........ggg..
═╦════════╦┼╦═╦═
.║........║.║X║.
.║.╔════╗.║.╠═╝.
.║.║....║.║.║▲..
.║.║.╔O.║.║.║...
.║.║.║▲.║.║.║...
.║.║.╚══╝.║.║...
.║.║......║.║...
.║.╚══════╝.║...
.║..........║...
.╚═════════┼╝...
................
Level 1:
················
+++++++++++·╬╬╬+
·+········+·╬☻╬·
·+·++++++·+·╬╬╬·
·+·+····+·+·+▼··
·+·+·++·+·+·+···
·+·+·+▼·+·+·+···
·+·+·++++·+·+···
·+·+······+·+···
·+·++++++++·+···
·+··········+···
·++++++++++++···
················
* Pit under drawbridges, never tested
** 26 tiles long
** 9 Z-levels deep
* 'Bait' tunnels with war dogs, unsuccessful
* Exotic pet collection
** Rhesus macaques
** Groundhogs
** Jaguar
** Elk
** One-humped Camel
** Deer
* Housing in a [[Bedroom design|spiral pattern]]
** Please forgive resemblance to onerous historical symbols; goal was merely to maximize density and minimize distance from doors to center. If it's any consolation, I think theirs were clockwise instead.
║θ.║θ.║θ.║.┼..║..┼.┼..║..┼.
║..║..║..┼.╠══╬══╣.╠══╬══╣.
╩═┼╩═┼╩══╝.║.θ║θ.║.║.θ║θ.║.
...........┼..║..┼.┼..║..┼.
╦═┼╦═┼╦══╗.╠══╬══╣.╠══╬══╣.
║..║..║..║.║.θ║θ.║.║.θ║θ.║.
║θ.║θ.║θ.┼.┼..║..┼.┼..║..┼.
╬══╬══╬══╣.╠══╬══╣.╠══╬══╣.
║θ.║θ.║θ.║.║.θ║θ.║.║.θ║θ.║.
║..║..║..║.┼..║..║.║..║..║.
╩═┼╩═┼╩═┼╝.╚══╩┼═╝.╚┼═╩┼═╝.
..........X................
┼╗.╔═┼╦══╗.╔┼═╦┼═╦┼═╦┼═╦┼═╦
.║.║..║..┼.║..║..║..║..║..║
.║.║.θ║θ.║.║.θ║.θ║.θ║.θ║.θ║
═╣.╠══╬══╣.╠══╬══╬══╬══╬══╬
.┼.┼..║..┼.┼.θ║.θ║.θ║.θ║.θ║
.║.║.θ║θ.║.║..║..║..║..║..║
═╣.╠══╬══╣.╚══╩┼═╩┼═╩┼═╩┼═╩
.┼.┼..║..┼.................
.║.║.θ║θ.║.╔┼═╦┼═╦┼═╦┼═╦┼═╦

<includeonly>
|}
</includeonly>

User:HebaruSan/Perplexedrag

2010-05-18T01:02:59Z

HebaruSan:

__NOTOC__
<includeonly>
{| class="wikitable collapsible collapsed" width="100%"
!
</includeonly>
== Region 3, Sherikunib, "Perplexedrag" ==
<includeonly>
|-
|
</includeonly>
{| class="wikitable" style="float:right;margin-left:2em;" border="1" cellspacing="0" cellpadding="2"
! Settled by
| The Scholarly Salves
|-
! Created [[wealth]]
| {{Money|318,379}}
|-
! Population
| 71 [[dwarves]]
46 [[animals]]
|-
! Deaths
| 20 dwarves
7 dogs
|-
! [[Artifacts]]
|
* [[Mace]]
* [[Barrel]]
* [[Mug]]
* [[Floodgate]]
* [[Spear]]
|-
! [[Nobles]]
| [[Dungeon Master]] ([[River#Surface Rivers|surface river]])
|-
! [[Military]]
| 8 [[Marksdwarves]]
1 [[Macedwarf]]
|}
<includeonly>
: ''([[User:HebaruSan/Perplexedrag|main article]])''

</includeonly>=== Celebrities ===
* Bomrek Thobdolush, Macedwarf and [[Captain of the guard]]
=== Features ===
* Thick forest, two aboveground rivers
* [[Design Strategies#3D Layout|Flat layout]], everything on 1 Z-level
* Very rigid grid of 7x7 rooms
** 3x3 workshops in each corner
** Attempted to site [[Workshop design|related shops and stockpiles]] near one another
╬═══┼═══╬═══┼═══╬═══┼═══╬
║WWW.SSS║SSS.WWW║WWW.WWW║
║WWW.SSS║SSS.WWW║WWW.WWW║
║WWW.SSS║SSS.WWW║WWW.WWW║
┼.......┼.......┼.......┼
║WWW.WWW║WWW.SSS║WWW.WWW║
║WWW.WWW║WWW.SSS║WWW.WWW║
║WWW.WWW║WWW.SSS║WWW.WWW║
╬═══┼═══╬═══┼═══╬═══┼═══╬
║WWW.WWW║WWW.WWW║WWW.WWW║
║WWW.WWW║WWW.WWW║WWW.WWW║
║WWW.WWW║WWW.WWW║WWW.WWW║
┼.......┼.......┼.......┼
║WWW.WWW║WWW.WWW║WWW.WWW║
║WWW.WWW║WWW.WWW║WWW.WWW║
║WWW.WWW║WWW.WWW║WWW.WWW║
╬═══┼═══╬═══┼═══╬═══┼═══╬
* First [[well]] with [[cistern]]
* Aboveground [[Defense guide#Walls|castle]]
** Archer platforms atop walls
** 3 [[Siege engine|ballistae]]
** 2 [[Siege engine|catapults]]
** 1 [[trade depot]]
** Enclosed [[farm]] field
** [[Drawbridge]] over channeled open-air [[refuse]] pit

<includeonly>
|}
</includeonly>

User:HebaruSan/Roughnessclasp

2010-05-18T01:01:41Z

HebaruSan:

__NOTOC__
<includeonly>
{| class="wikitable collapsible collapsed" width="100%"
! </includeonly>
== Region 2, Dumatdodók, "Roughnessclasp" ==
<includeonly>
|-
|
</includeonly>{| class="wikitable" style="float:right;margin-left:2em;" border="1" cellspacing="0" cellpadding="2"
! Settled by
| The Cloudy Salves
|-
! Created [[wealth]]
| {{Money|452,441}}
|-
! Population
| 94 [[dwarves]]
156 [[animals]]
|-
! Deaths
| 18 dwarves
6 dogs
|-
! [[Artifacts]]
|
* [[Cabinet]]
* [[Throne]]
* Leather [[Clothing|vest]]
* [[Braies]]
* [[Ring]]
* [[Bracelet]]
* Leather [[Clothing|skirt]]
|-
! [[Nobles]]
| [[Dungeon Master]] ([[River#Surface Rivers|surface river]])
|-
! [[Military]]
| 11 [[Marksdwarves]]
|}
<includeonly>
: ''([[User:HebaruSan/Roughnessclasp|main article]])''

</includeonly>After running out of [[food]] due to not assigning [[crops]] to be grown, I set this fortress aside to start Region 3 rather than watch everyone chase rodents and [[Losing#Starvation|starve]]. Later returned to it with more expertise, got food from a [[caravan]], and managed a full recovery. Still have the in-progress save game, but stopped playing it after losing substantial progress (city walls) to a [[Init.txt#Seasonal autosave|crash]].
=== Features ===
* Captive-[[Water|drowning chamber]], extensively used
* Elaborate [[Defense design#Flooded entrance|invader-drowning entrance]], never tested
* [[Design Strategies#3D Layout|Flat layout]] (most things on 2 Z-levels)
* [[Defense design#Simple 5x5 Archer's Tower|Marksdwarf towers]] with [[Archery target]]s and [[Bedroom|sleeping quarters]] underneath
* Passage dug under river
* Dug out and flooded an underground area with an above-ground river to allow underground [[fishing]] and to see if it counted as a tower-cap-enabling "[[underground river]]" (it doesn't)
=== Celebrities ===
* First legendary miner, Domas Dastotganad
* First legendary mason, Îton Momuzimik
* Pair of legendary bone carvers, Urist Inethnulral and Goden Sazirzatam
=== Noteworthy Occurrences ===
* Learned the wonders of [[cage traps]]
* [[Elf|Elven]] caravan stopped coming after one was lost to an [[ambush]]

<includeonly>
|}
</includeonly>

User:HebaruSan/Roughnessclasp

2010-05-18T00:59:32Z

HebaruSan:

__NOTOC__
<includeonly>
{| class="wikitable collapsible collapsed"
! </includeonly>
== Region 2, Dumatdodók, "Roughnessclasp" ==
<includeonly>
|-
|
</includeonly>{| class="wikitable" style="float:right;margin-left:2em;" border="1" cellspacing="0" cellpadding="2"
! Settled by
| The Cloudy Salves
|-
! Created [[wealth]]
| {{Money|452,441}}
|-
! Population
| 94 [[dwarves]]
156 [[animals]]
|-
! Deaths
| 18 dwarves
6 dogs
|-
! [[Artifacts]]
|
* [[Cabinet]]
* [[Throne]]
* Leather [[Clothing|vest]]
* [[Braies]]
* [[Ring]]
* [[Bracelet]]
* Leather [[Clothing|skirt]]
|-
! [[Nobles]]
| [[Dungeon Master]] ([[River#Surface Rivers|surface river]])
|-
! [[Military]]
| 11 [[Marksdwarves]]
|}
<includeonly>
: ''([[User:HebaruSan/Roughnessclasp|main article]])''

</includeonly>After running out of [[food]] due to not assigning [[crops]] to be grown, I set this fortress aside to start Region 3 rather than watch everyone chase rodents and [[Losing#Starvation|starve]]. Later returned to it with more expertise, got food from a [[caravan]], and managed a full recovery. Still have the in-progress save game, but stopped playing it after losing substantial progress (city walls) to a [[Init.txt#Seasonal autosave|crash]].
=== Features ===
* Captive-[[Water|drowning chamber]], extensively used
* Elaborate [[Defense design#Flooded entrance|invader-drowning entrance]], never tested
* [[Design Strategies#3D Layout|Flat layout]] (most things on 2 Z-levels)
* [[Defense design#Simple 5x5 Archer's Tower|Marksdwarf towers]] with [[Archery target]]s and [[Bedroom|sleeping quarters]] underneath
* Passage dug under river
* Dug out and flooded an underground area with an above-ground river to allow underground [[fishing]] and to see if it counted as a tower-cap-enabling "[[underground river]]" (it doesn't)
=== Celebrities ===
* First legendary miner, Domas Dastotganad
* First legendary mason, Îton Momuzimik
* Pair of legendary bone carvers, Urist Inethnulral and Goden Sazirzatam
=== Noteworthy Occurrences ===
* Learned the wonders of [[cage traps]]
* [[Elf|Elven]] caravan stopped coming after one was lost to an [[ambush]]

<includeonly>
|}
</includeonly>

40d Talk:Water pressure

2009-11-27T04:30:29Z

HebaruSan: /* Fast aqueducts */ new section

Verification of U-bend bug. [http://mkv25.net/dfma/movie-207-infinitewaternopumps] [[User:VengefulDonut|VengefulDonut]] 12:37, 7 January 2008 (EST)

: Do you happen to have a save file so I can poke it a bit? --[[User:SL|SL]] 11:06, 15 January 2008 (EST)

::I don't, but it has been reliably reproducible. [[User:VengefulDonut|VengefulDonut]] 23:37, 15 January 2008 (EST)

== Deep water pressure bug? ==

I just had an odd experience. I lucked into a map with a brook high up on a mountain slope, a deep ravine next to it with an extremely narrow mouth I could easily wall off, and goblin buildings down at the bottom of the slope. So I made a huge five-level-deep reservoir and dug a floodgate-controlled tunnel from the lowest level right into the basement of one of the goblin forts. The reservoir was filling slowly so I had the opportunity to test-fire the flood in some disposable save games while the reservoir was still only partly full; it gave the wonderful drowned-goblin corpse-fountain effect I was hoping for. But once the reservoir had finished filling up to 7 on the highest level, even with the brook that was feeding it, opening the floodgate produced only a disappointing unpressurized trickle. It wasn't until I dug a single channel square at the edge of the reservoir, introducing a single non-7 square to the uppermost water layer, that the torrent instantly let loose with all its pressurized might. A known issue? Some of this page is a bit too arcane for me to follow right now so I'm not sure if it's mentioned. [[User:Bryan Derksen|Bryan Derksen]] 01:59, 28 June 2008 (EDT)

:That's almost certainly because it's being treated as part of the brook, since brooks and rivers don't produce (and even neutralize) water pressure. --[[User:N9103|Edward]] 14:49, 28 June 2008 (EDT)

::Ah, so if I closed the floodgates feeding the reservoir to sever the connection with the brook it'd pressurize? Interesting physics in DF world. :) [[User:Bryan Derksen|Bryan Derksen]] 03:09, 30 June 2008 (EDT)

:Are aquifers treated the same way? I have a pond fed by digging stairs up into an aquifer, and dug out the wrong tiles around my pump. My entire fort should be submerged, but all I got was a pond at permanent 7/7.
::Aquifers don't generate water pressure, and don't fill z-levels higher than the one on which they were originally found. [[User:Aosher|Aosher]] 18:29, 12 March 2009 (UTC)

==To clear out==
Water sources attempt to generate water in tiles adjacent to pressurized tiles. They will not generate water in tiles above
pressurized tiles unless the water source has nowhere else to generate any water, and they will never generate water above
the water source's z-level.
What exactly does this mean? If I understand right, then it's a lie--[[User:Dorten|Dorten]]

:What do you think conflicts with the model? [[User:VengefulDonut|VengefulDonut]] 02:43, 9 February 2009 (EST)
::Things like this (side view)

≈≈≈≈≈≈≈# ≈≈≈
≈≈≈≈≈≈≈#≈≈≈≈≈≈++
≈≈≈≈≈≈≈###≈#####
≈≈≈≈≈≈≈≈≈≈≈#
############
The blue water tiles should not be filled before the plus marked ones (empty). But this situation can easily be made ingame--[[User:Dorten|Dorten]] 07:07, 18 March 2009 (UTC)
==Water U - BUG==
http://mkv25.net/dfma/movie-1407-pressurebugwithfortification

W≈≈≈### ## z 0
###≈###≈### z -1
###≈###≈### z -2
###≈≈≈≈≈### z -3

W - Water from a water source
# - Solid wall
≈ - Water

The water does not go up to the z-level it came from.
:Note that this will only happen if the water is able to drain on its source level (e.g. you tapped the side of a river) - if the water on the left side is unable to escape in any other direction (e.g. if you dam the river), the right side of the U-bend '''will''' fill up. --[[User:Quietust|Quietust]] 15:34, 9 September 2009 (UTC)

== U Bend Bug ==

I found a quirky Pressure bug using a U-bend into my main reservoir. I have it tapped directly into the river with a floodgate (1) right at the river to control things. The surprise was when I went to irrigate my fields, I was pulling water out through (2) to fill a vault to irrigate my fields with since the main reservoir was way too large for this purpose. So I had left (1) open expecting it to naturally refill as quickly as I drained it. It did not. It instead pulled the water out filling my vault, emptied the main reservoir and sat there doing nothing. (1) is wide open still, so it SHOULD be refilling, but isn't. Toggling (1) closed and reopened seems to reset the pressure and allow the main reservoir to fill.

: ≈≈≈1≈######
: ####≈#≈≈≈##
: ####≈#≈≈≈##
: ####≈≈≈≈≈2≈
: ######≈≈≈##
: ###########

It's a little unclear on why it behaves this way. It has something to do with multiple floodgates, when one opens, it doesn't seem to bother to check the state of other floodgates that might also affect pressure on this waterway. It may also be important that the top of my reservoir is lower than the river itself, so once it's done filling it may be shutting off the water flow logic since it's full now and doesn't need to waste CPU cycles, and then forgetting to check it again when I pull water away from that.[[User:Doctorzuber|Doctorzuber]] 09:12, 12 July 2009 (UTC)

== overflow behaviour ==
"to a z-level one level lower than the source."

That is just plain contradicting the next sentence. Also, I have read the article at http://www.gamasutra.com/view/feature/3549/interview_the_making_of_dwarf_.php?page=10 , but, please, explain then:

On level '1' I have a tunnel filled with water, steadily being refilled by a pump. It drops its content one level down ('0') through a channel tile, into a room that is open to level '1' via a stairway. The room fills with water and when all tiles are at 7/7 water starts pouring out back to level '1' - lots of water. Of course this makes perfect sense. If there is another mechanism at work that has nothing to do with the pressure model ("Pumps do not create pressure"), then there should still be a warning, or a rewording because, seriously, how is that not "water pressure" --[[User:Birthright|Birthright]] 16:50, 12 July 2009 (UTC)

:By not creating it, it means that the water coming out is at zero pressure. By dropping the water, it can now gain pressure if any of the tiles above it are at 7/7. -[[User:N9103|Edward]] 19:25, 23 July 2009 (UTC)

== Oceans ==

I'm torn on whether to add something specifically about oceans on here. I tunneld into an ocean three z-levels below the ocean's surface with a door which I figured would allow my miner to escape with minor flood beeing the only damage. When I breached the ocean, the room immediatly filled with water. I thought that was odd but I let my miner do his this, and as soon as he opened the door the game went to 0 FPS for about 2 minutes and suddenly my whole fortress below that points (a good 6 z-levels with some sizable rooms) was 7/7. instantly in game time. You can see why I'm tempted to add a warning. [[User:Planetofthedwarves|Planetofthedwarves]] 18:40, 23 July 2009 (UTC)

:Damn, you got romped. Definetly add that warning!--[[User:CrazyMcfobo|CrazyMcfobo]] 18:56, 23 July 2009 (UTC)

:That's no different than would happen with any other large body of water with several Z-levels above where you breached. Fill a giant (x&y, not Z) tower that reaches into the ground with water, and then breach it.. You'll get the same instant fill to a certain level. -[[User:N9103|Edward]] 19:24, 23 July 2009 (UTC)

== Fast aqueducts ==

I'm hoping to transport water a long distance quickly. Side view of initial layout:
▒ target ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒≈≈river≈≈▒
▒▒ area ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒

The obvious naive approach is to dig a tunnel leading to the river:
_____________________
▒ target ≈≈river≈≈▒
▒▒ area ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒

My overall impression from this page is that the water might move faster if a pump on a higher Z-level is involved:
__________________▒ %%
▒ target ▒▒≈≈river≈≈▒
▒▒ area ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
Is that right? Does it help to add more pumps further down the tunnel to re-pressurize? And is there additional risk of flooding?
--[[User:HebaruSan|HebaruSan]] 04:30, 27 November 2009 (UTC)

User talk:63.249.116.37

2009-11-26T17:35:11Z

HebaruSan: i thought the 'hi' template worked :(

Welcome to this wiki! Dwarf Fortress rapidly becomes more complicated, and we're always glad to have new writers. 
Since you should try to follow wiki standards, and you probably don't know ours yet, we've made a list of basic guidelines. Note that this is a template, not a customized message for you.
* To tell us who you are when you talk, please sign your posts on discussion pages by typing <code><nowiki>--~~~~</nowiki></code> after your posts. This can also be inserted with the [[Image:Button sig756222.png]] button if JavaScript is enabled.
* Don't put a question mark in the title of a page. Question marks mess things up, and your page will be moved to a different name.
* When making comments on a talk page, use one more colon before each line in your comment than was used in the comment you reply to. In general, put exactly one empty line between comments by different users but do not use blank lines inside of a comment.
* Avoid making many small edits to a page. Instead, try to make one large edit. This makes the history of the page a lot easier to read.
* Don't edit the user page of another user. If you want to tell them something, add the comment to their talk page.
* If you put a comment at the bottom of a talk page with section headers, you've probably put it in a section. Putting things in the wrong sections is confusing. You can create a section!
* Generally, [[Dwarf_Fortress_Wiki:Community_Portal#We_are_doing_this.21_Let_us_do_it_right.|read and follow the rules.]] They're like a little constitution, except not boring! Really, read them.
<div align=center><div style="width: 28em; padding: 0.5em; margin-bottom: 0.5em; margin-top: 0.5em; border: 1px solid #ccc; background: #eee; text-align: center">''"You have been processed! Go forth, now, and edit!" --[[User:Savok|Savok]]''</div></div>

Many or all of your edits have been reverted because they corrupted the pages by inserting this at random points:
Proxy-Connection: keep-alive
Cache-Control: max-age=0
Please check your browser and proxy settings to see if you can fix this. Thanks!
--[[User:HebaruSan|HebaruSan]] 17:34, 26 November 2009 (UTC)

User talk:63.249.116.37

2009-11-26T17:34:40Z

HebaruSan: please fix your broken proxy

{{Hi}}

Many or all of your edits have been reverted because they corrupted the pages by inserting this at random points:
Proxy-Connection: keep-alive
Cache-Control: max-age=0
Please check your browser and proxy settings to see if you can fix this. Thanks!
--[[User:HebaruSan|HebaruSan]] 17:34, 26 November 2009 (UTC)

40d:Embark

2009-11-24T02:26:11Z

HebaruSan: organize by topic, factor out redundancies

'''Embark''' is the moment at the very beginning of the game, before actual game play begins, when you and your initial 7 dwarves:
# Choose a site, possibly using the [[site finder|site {{k|f}}inder]].
# Assign starting [[skill]]s to each dwarf.
# Select an initial load of [[supplies|supplies and equipment]].
# Arrive at the site with your wagon full of supplies.

"Embark options" can refer to any of the first three steps.

"Information at embark" can include:
* Viewing your [[region]] on the World and Regional maps.
* Viewing your Local map to:
** Confirm the presence of important features, such as [[magma]] vents or [[rivers]].
** Note these features' locations.
* Using the {{k|tab}} and {{k|F1}}, {{k|F2}}, {{k|F3}}, etc. keys to view your:
** Stone [[layer]]s
** [[Biome]]s and climate
** Starting dwarven civilization (and choose if more than one)
** Neighboring civilizations and relationships with them

''(Need a quick list of Embark screen features, with links to full pages)''

Example usages:
* "I made a big mistake '''at embark''' when I forgot..."
* "I knew I was in trouble when I got attacked '''on embark'''..."
* "This is one of the choices you need(ed) to make '''at embark''', before the game..."
* "'''After embark''' the first thing you want to do is..."
* "Once you've '''embarked''', that's when the [[fun]] starts..."

== Before you unpause ==
Before you start the game by unpausing, check the following things to make sure your young fortress runs smoothly and avoids becoming a tiny, tiny tomb. Particularly important in less hospitable [[biome]]s and other dangerous sites.

* Figure out where you're gonna dig your fortress. Look around, get a feel for what is visible, and what the terrain can do for (or to) you. Think about it while you do the rest and come back to it as you need to.
* Press {{k|u}} to check for the presence of hostile wild [[animal]]s. (However, be aware that creatures can appear from off-map after the game has been going for a while.)
** Activate military if desired.
* Press {{k|c}} to check for the presence of other civilizations.
** In that same screen ({{k|u}}nits), {{k|c}}enter on a specific units and set their preferences, especially [[labor]] designations. (You can also {{k|v}}iew them from the map screen.)
*** Make sure at least one dwarf has the [[carpenter]] labor designated to break down the [[wagon]].
***Add any other unskilled labors you want active.
***If the environment is particularly dangerous, you may consider disabling the Hunting and/or Fishing labors at first to keep your dwarves from wandering too far afield.
** You can also give them custom titles or nicknames if you like.
* Press {{k|q}} and mark the [[wagon]] for removal.
* Press {{k|o}} for orders and options. Toggle to suit your preferences.
** Consider {{k|r}}efuse orders
** Consider fishing/drinking {{k|z}}one options.
* Press {{k|i}} and designate a [[meeting area]] for animals and idle dwarves (or the wagon's location will be the default).
* Press {{k|n}} and reassign [[noble]] positions ''if desired''.
* Press {{k|z}} and forbid the kitchen from cooking alcohol and plump helmets if desired.
* Press {{k|d}} to designate areas for plant gathering, wood cutting, and/or stone smoothing if needed/desired. (Stone smoothing is good for getting rid of boulders that impede outdoor farming.)
** Press {{k|d}}, then {{k|o}} to place traffic restrictions. Things to watch for: saplings, wild plants, dangerous shortcuts (like near magma or cave creatures). Consider encouraging your dwarves to traffic specific areas to minimize damage to subsequent growth.
* Press {{k|p}} to create [[stockpile]]s for wild plants, [[wood]], and/or [[refuse]].
* {{k|b}}uild any {{k|w}}orkshops you feel that you need immediately.
* {{k|d}}esignate where your miner(s) will dig in first.

== See also ==
* [[Location]]
* [[Starting build]]
* [[What should I build first]]
* [[Defense guide]]

[[Category:Guides]]
[[Category:Interface]]

40d:Embark

2009-11-24T01:36:07Z

HebaruSan: Undo revision 58598 by 63.249.116.37 (Talk) looks like someone's proxy doesn't like wikis

'''"Embark"''' is a general term that refers to the very beginning of the game, during or immediately following site selection but before actual game play begins. It is used to refer to any choices during that period - site selection, equipment or [[skill]]s selected for your starting 7 dwarfs (or the "Play Now" option), and the actual "landing" on your new site, the 7 dwarfs and any animals around the wagon filled with supplies.

Examples -

:* "I made a big mistake at embark when I forgot..."
:* "I knew I was in trouble when I got attacked on embark..."
:* "This is one of the choices you need(ed) to make at embark, before the game..."
:* "After embark the first thing you want to do is..."
:* "Once you've embarked, that's when the [[fun]] starts..."

"Embark options" can refer to
:* choosing starting skills, equipment and supplies (aka [[Starting build]]),
:* site selection, possibly using the <f>ind function to help locate an acceptable site for your fortress.

"Information at embark" can include:
* looking at the Wold and Regional map to view the general [[region]] you will be playing in
* looking at the Local map to confirm the presence of and note the location of important features of your game map, such as [[magma]] vents or [[rivers]].
* using the {{k|f}} key to "find" a site to your liking
* using the {{k|tab}} key to view your:
:* stone [[layer]]s, by using the various {{k|F1}}, {{k|F2}}, {{k|F3}}, & etc. keys
:* various [[biome]]s, using the same keys, to check for stone layers and climate
:* view and (if more than one) choose your starting dwarven civilization.
:* view neighboring civilizations and relationships with them

''(Need a quick list of Embark screen features, with links to full pages)''

===Before you unpause===

A checklist of what to do before you actually start the game by unpausing to help make sure your young fortress runs smoothly and avoids becoming a tiny, tiny tomb. Particularly important in less hospitable [[biome]]s and other dangerous sites.

* First thing, figure out where you're gonna dig your fortress. Look around, get a feel for what is visible, and what the terrain can do for (or to) you. Think about it while you do the rest, come back to it as you need to...
* Press {{k|u}} to check for the presence of hostile wild [[animal]]s. (However, be aware that creatures can appear from off-map after the game has been going for a while.)
:* Activate military if desired.
* Press {{k|c}} to check for the presence of other civilizations.
:* In that same screen ({{k|u}}nits), {{k|c}}enter on a specific units and set their preferences, especially [[labor]] designations. (You can also {{k|v}}iew them from the map screen.)
::* Make sure at least one dwarf has the [[carpenter]] labor designated to break down the [[wagon]].
::*Add any other unskilled labors you want active.
::*If the environment is particularly dangerous, you may consider disabling the Hunting and/or Fishing labors at first to keep your dwarves from wandering too far afield.
:* You can also give them custom titles or nicknames if you like.
* Press {{k|q}} and mark the [[wagon]] for removal.
* Press {{k|o}} for orders and options. Toggle to suit your preferences.
:* Consider {{k|r}}efuse orders
:* Consider fishing/drinking {{k|z}}one options.
* Press {{k|i}} and designate a [[meeting area]] for animals and idle dwarves (or the wagon's location will be the default).
* Press {{k|n}} and reassign [[noble]] positions ''if desired''.
* Press {{k|z}} and forbid the kitchen from cooking alcohol and plump helmets if desired.
* Press {{k|d}} to designate areas for plant gathering, wood cutting, and/or stone smoothing if needed/desired. (Stone smoothing is good for getting rid of boulders that impede outdoor farming.)
:* Press {{k|d}}, then {{k|o}} to place traffic restrictions. Things to watch for: saplings, wild plants, dangerous shortcuts (like near magma or cave creatures). Consider encouraging your dwarves to traffic specific areas to minimize damage to subsequent growth.
* Press {{k|p}} to create [[stockpile]]s for wild plants, [[wood]], and/or [[refuse]].
* {k|b}}uild any {{k|w}}orkshops you feel that you need immediately.
* {{k|d}}esignate where your miner(s) will dig in first.

----

'''See also:'''
:* [[What_should_I_build_first]]
:* [[Defense guide]] (et al)
:* [[Starting build]]

[[Category:Guides]]

----
'''See Also:'''

:* [[location]]
:* [[starting build]]

40d:How do I construct a wall from a particular direction

2009-11-22T05:10:56Z

HebaruSan: add diagonal planning strategy, tried to guess which "earlier versions" were being referenced based on versions category

It often happens that you need to construct a wall, but your dwarf insists on standing on the wrong side of it during construction, trapping himself.

== Diagonal method{{v|0.28.181.40d}} ==
Dwarves will only build walls from a non-diagonally adjacent square.
@
@░@ <-- to build this wall, a dwarf will only stand at one of the @ signs
@
If you consider this when planning constructions, you can ensure that they are built in the right order:
# Designate the walls that you want constructed.
# Find places where the builder might be trapped.
# Plan a diagonal "escape route" from that area, and {{k|q}}→{{k|s}}uspend the tiles along that path.
# Wait for the non-suspended walls to be built.
# Un-suspend the suspended walls.

=== Example ===
Suppose you want to build a 3x3 ring of walls, enclosing a central square.
░░░
░+░
░░░
If you designate it all at once, it is possible for the first seven walls to be constructed this way:
░░░
░@+@
░░░
Your builder might stand at either @ sign to finish the last wall, and if he picks the one in the middle, he'll be trapped. If you're unlucky, your first sign that this has happened will be the alert about him starving to death.

However, if you {{k|s}}uspend construction of the northeast corner, you'll end up with this:
@
░░+@
░+░
░░░
This time, both of the places where your builder might stand to finish the last wall are outside of the ring, so you can be confident that he won't be trapped.

== Suspended construction method{{v|0.27.176.38c}} ==
# Press {{k|b}}→{{k|C}}→{{k|w}}
# Designate a "temporary" wall to be built in the location where you do ''not'' want the dwarf to stand
# Open the Set Building Tasks/Prefs menu, {{k|q}}
# Move over the temporary wall
# {{k|s}}uspend its construction
# Build your other object (wall, floodgate, etc.) like normal
# Wait for this other object to be fully constructed
# Open the Set Building Tasks/Prefs menu again, {{k|q}}
# Move over the temporary wall
# Cancel its construction {{k|x}}

This does not work in all situations; sometimes you cannot specify that you want a wall built in a certain location due to what is already built there. Specifying other structures instead of a wall may work, if any of them are permitted. You could also place a [[statue]] in the location where the dwarf isn't supposed to stand.

== Traffic restriction method{{v|0.27.169.33g}} ==

# Open the Designate menu {{k|d}}
# Select Set Traffic Areas {{k|o}}
# Press {{k|r}} to select "Restricted Traffic Area"
# Designate the squares you '''don't''' want the dwarf to stand on.

Now, he won't stand there while building the wall. You can optionally remove the designation after the wall is built.

{{Buildings FAQ}}

[[Category:Guides]]

40d:Floor

2009-11-22T04:31:05Z

HebaruSan: replace redundant keystrokes with link, some other clarifications

A '''floor''' is a [[map tile]] that creatures can walk on. A floor is formed:
# naturally, as the ground (typically [[grass]] or a type of [[soil]] or [[stone]]),
# by constructing walls (thus creating a floor on the level above), or
# by [[#Construction|constructing floors]].

Floors enclose spaces making the tiles below them [[inside]].

== Construction ==
Floors may be built using {{k|b}}→{{k|C}}→{{k|f}}, then {{k|u}}, {{k|k}}, {{k|m}} and {{k|h}} to designate a rectangular area. Building the floor requires either the [[Masonry]] skill (for [[stone]] and [[glass]] floors), the [[Carpenter]] skill (for [[wood]] floors), or any of the [[metalsmith]] skills (for [[metal]] floors).

Floors can be constructed on top of existing natural floors; this distinction is subtle but allows for 'paving' (not to be confused with building a [[road]]!). Note that designated constructions, such as stairs dug out of natural soil, can be floored over. Beware the possibility of sealing in your fort when paving your entry hall.

Constructed floors:
* count as [[construction]]s and cannot have [[wall]]s built upon them.
* can have other types of buildings built upon them, such as workshops.
* can be [[irrigation|muddied]] and subsequently [[farming|farmed]].
* [[cave-in]] when unsupported, punching through any floor tile in their way.
* cannot be [[smooth]]ed or [[Engraving|engraved]].

== Risk of clogging ==
Underground, muddied constructed floors can have [[tower-cap]] trees to grow on them if an [[underground river]] has been discovered, just like muddied natural floors. This can wreak havoc on reservoirs if a tree grows where a floodgate wants to close or blocks a narrow access hall.

One method to prevent growth is to build a paved [[road]] over any muddy floors. This can be a good use for all that extra stone.

== See Also ==
*[[Digging]]

{{Buildings}}
[[Category:Constructions]]
[[Category:Map tiles]]

40d:Macros and keymaps

2009-11-21T18:04:27Z

HebaruSan: /* Dumping */ link to orphaned guidumper

Playing Dwarf Fortress means lots of typing. Although the game has no internal macro/keymap system (except in alpha version 40d12), using an external program can save you a great deal of time when dumping, rewalling, designating, and so forth.

# Go to [[Utilities#AutoHotKey]] and download AutoHotKey. Installation is simple and the program uses few system resources.
# Write macro scripts (file type .ahk), which may contain any number of commands. You activate scripts by double-clicking .ahk files and deactivate them by right-clicking the AutoHotKey icon on the task bar. Both of these can be done at any time - even right in the middle of a game. AutoHotKey also allows for automated activation of scripts.

==Troubleshooting Scripts==
Users may experience some issues in getting scripts to work, particularly when using looping scripts when experiencing low frame-rates.
* If experiencing low frame-rates, try adding delays ("Sleep 100" to pause for 100 milliseconds for example) within loops to allow the interface to keep up. If there are nested loops, sometimes adding a pause at the end of an inner loop is all that is needed to flush the keyboard buffer
* Make sure that Dwarf Fortress maintains focus. IM windows are the enemy! Who needs friends anyhow? You've got Dwarf Fortress.
* This may go without saying, but most macros assume standard key-mappings. If you're using non-standard ones, you may have to edit the macro to get it to work.
* Visiting liaisons can bring up screens that eat keystrokes, throwing a long-looping script out-of-phase with where it expects the game to be. Wait for the farewell screen before running a long script.
* The SendPlay function supports keys that the Send function does not, for example {{key|Shift-Enter}}. According to the AutoHotKey documentation, SendPlay may also be better at preventing dropped keystrokes.

== [http://sun2design.com/quickfort/ Quickfort] ==

Quickfort is an AutoHotkey-based utility for Dwarf Fortress that helps you build fortresses from "blueprint" .CSV files (comma separated values). These files are easily created and edited in an app like Excel. Most building-oriented DF commands are supported through the use of multiple .CSV files to describe the different phases of DF construction (designation, building, stockpiles, and making adjustments). Many of the examples below can be reproduced in Quickfort.

== Built-in Macros ==

With the release of df_28_181_40d13, Dwarf Fortress supports macros without any outside program. They can be created by hitting escape to access the options menu and choosing the Key Bindings section. Once in the Key Bindings menu hit Shift+Tab to open the macro screen. The macros you create here are saved in the file "\data\init\interface.txt". Adding the following to the end of that file will create a macro that selects every item on the trade screen when you hit the tilde key (`).

<pre>
[BIND:MACRO0]
[SYM:`]
[MACRO:SELECT:1]
[MACRO:STANDARDSCROLL_DOWN:1]
[MACRO:SELECT:1]
[MACRO:STANDARDSCROLL_DOWN:1]
[MACRO:SELECT:1]
[MACRO:STANDARDSCROLL_DOWN:1]
[MACRO:SELECT:1]
[MACRO:STANDARDSCROLL_DOWN:1]
[MACRO:SELECT:1]
[MACRO:STANDARDSCROLL_DOWN:1]
[MACRO:SELECT:1]
[MACRO:STANDARDSCROLL_DOWN:1]
[MACRO:SELECT:1]
[MACRO:STANDARDSCROLL_DOWN:1]
[MACRO:SELECT:1]
[MACRO:STANDARDSCROLL_DOWN:1]
[MACRO:SELECT:1]
[MACRO:STANDARDSCROLL_DOWN:1]
[MACRO:SELECT:1]
[MACRO:STANDARDSCROLL_DOWN:1]
[MACRO:SELECT:1]
[MACRO:STANDARDSCROLL_DOWN:1]
[MACRO:SELECT:1]
[MACRO:STANDARDSCROLL_DOWN:1]
[MACRO:SELECT:1]
[MACRO:STANDARDSCROLL_DOWN:1]
</pre>

Performance can be increased by changing the macro pause, MACRO_MS, from the default 150ms per command to zero. Most dig macros can be created using combinations of the following:
<pre>
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_DOWN:1]
[MACRO:CURSOR_LEFT:1]
[MACRO:CURSOR_RIGHT:1]
[MACRO:SELECT:1]
[MACRO:DESIGNATE_DIG:1]
[MACRO:DESIGNATE_UNDO:1]
[MACRO:CURSOR_UP_FAST:1]
[MACRO:CURSOR_DOWN_FAST:1]
[MACRO:CURSOR_LEFT_FAST:1]
[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:MACRO123:1]
</pre>
Most of these should be self-explanatory. Each command is followed with a quantity. To call other macros, use <pre>[MACRO:MACRO###:1]</pre> Each new macro begins with a bind command, consisting of BIND, the macro number, and a description:
<pre>[BIND:MACRO11:dig_round_room]</pre> Spaces are not allowed in the description{{verify}}. To bind this macro to a key, SYM is used.<pre>[SYM:Ctrl+Right]</pre> Ctrl, Alt, and Shift combinations are allowed, but not chords with more than one{{verify}}, like Ctrl+Shift+Right. Also, the windows, or meta key, does not appear to be supported{{verify}}. Macros appear to only be terminated by the start of a new macro (BIND command) or the end of the interface.txt file.

Visit this [http://www.bay12games.com/forum/index.php?topic=40751.0 forum post] for additional macros, and discussion on macro creation.

== AutoHotKey Examples ==

===Dumping===

====[[GuiDumper.ahk]]====
This script allows the user to specify a range of squares to dump.

====Stock Screen Dump====
Taken from an old version of [[User:Jackard|Jackard's user page]].

To use, first have your bookeeper do enough desk work so you can view individual items in the stocks listing. Then bring it up and press del to quickly mark stuff. To adjust the key repeat rate, edit the KEY_HOLD_MS value in \data\init\init.txt.

<pre>
del::
IfWinActive Dwarf Fortress
{
send d{down}
return
}
else
{
send {del}
return
}
</pre>

====Designation Dump====
A dumping script by [[User:Dukederek|Dukederek]]:

This script uses a system similar the commands in the designations menu to mark most of the contents of a large area for dumping. [[User:Dukederek|My talk page]] has more detailed instruction.

Essentially you need to create two text files with the following titles and content. When playing DF it is safe to have blockdumpinit running constantly as long as you dont plan on using the ctrl-d combination for something else.

'''blockdumpinit.ahk'''
<pre>
^d::
RunWait, "blockdumpmain.ahk"
Return
</pre>

'''blockdumpmain.ahk'''
<pre>
SetKeyDelay 25
return::
Send k
return
up::
Send w
return
left::
Send a
return
down::
Send s
return
right::
Send d
return
q::
ExitApp
return
shift::
x := 0
y := 1
Loop{
Input, keypress, B, {esc} , w,a,s,d,k,q
if keypress = w
{
y := --y
Send {up}
continue
}else if keypress = s
{
y := ++y
Send {down}
continue
}else if keypress = a
{
x := --x
Send {left}
continue
}else if keypress = d
{
x := ++x
Send {right}
continue
}else if keypress = k
{
break
}else if keypress = q
{
ExitApp
}
}
y := y / 2
z := y
z := Floor(z)
z := y/z
Send d{NumpadAdd}d
If z = 0
{
If x = 0
ExitApp
Else{
Loop %x%{
Send {left}d
}ExitApp
}
}If z <> 1
{
Loop %y%{
Loop %x%{
Send {left}d{NumpadAdd}d
}Send {up}d
Loop %x%{
Send {right}d{NumpadAdd}d
}Send {up}d{NumpadAdd}d
}Loop %x%{
Send {left}d{NumpadAdd}d
}
}Else If z = 1
{
y := y + 0.5
Loop %y%{
Loop %x%{
Send {left}d{NumpadAdd}d
}Send {up}d
Loop %x%{
Send {right}d{NumpadAdd}d
}Send {up}d{NumpadAdd}d
}Send d{NumpadSub}d
}ExitApp
</pre>

===Rewalling ===
Taken from [[User:Valdemar|Valdemar's user page]].

This is a macro to aid with rewalling. To use, copy-paste the script into a new .ahk file and run the script with AutoHotkey. Then, in Dwarf Fortress, press b-C-w, move the cursor to where you want to start the wall, and hold Ctrl-Shift-Arrowkey, using the direction you want to rewall in. To build floors, press b-C-f instead, and use Ctrl-Alt-Arrowkey. To stop, just release the keys.

The script will use the first material in the list. I suggest you create a stockpile near the construction site that only accepts the item you wish to build with and temporarily forbid any nearby materials you don't want to build with.

<pre>
$^+Left:: ProcessEvent("Left","w")
$^+Right:: ProcessEvent("Right","w")
$^+Up:: ProcessEvent("Up","w")
$^+Down:: ProcessEvent("Down","w")

$^!Left:: ProcessEvent("Left","f")
$^!Right:: ProcessEvent("Right","f")
$^!Up:: ProcessEvent("Up","f")
$^!Down:: ProcessEvent("Down","f")

ProcessEvent(direction, type)
{
Send {Enter}
Sleep 100
Send {Enter}
Sleep 100
Send %type%
Sleep 100
Send {%direction%}
Loop
{
if not GetKeyState(direction, "P")
break
Send {Enter}
Sleep 100
Send {Enter}
Sleep 100
Send %type%
Sleep 100
Send {%direction%}
}
}
</pre>

===Grid-by-grid designation===
For easier diagonal and fancy mining. Assumes that DF is active. "^!" means ctrl-alt-direction.

<pre>
^!NumpadEnd::
send {Enter}{Enter}{NumpadEnd}
return
^!NumpadDown::
send {Enter}{Enter}{NumpadDown}
return
^!NumpadPgDn::
send {Enter}{Enter}{NumpadPgDn}
return
^!NumpadLeft::
send {Enter}{Enter}{NumpadLeft}
return
^!NumpadRight::
send {Enter}{Enter}{NumpadRight}
return
^!NumpadHome::
send {Enter}{Enter}{NumpadHome}
return
^!NumpadUp::
send {Enter}{Enter}{NumpadUp}
return
^!NumpadPgUp::
send {Enter}{Enter}{NumpadPgUp}
return
</pre>

===Embark Settings macros===
These macros are used to ease the setup of skills and supplies before you embark.

====Improved Food/Alcohol buying macro====
This macro buys all the cost-2 food (that I have seen), as well as the four types of alcohol. Just press ctrl+f on the Items screen.
It can deal with meat or drink that you already have, or is not currently featured. By [[User:Redfenix|Redfenix]].

<pre>
^f::

send ndwarven{SPACE}ale{RIGHT}{ENTER}{F9}
send ndwarven{SPACE}rum{RIGHT}{ENTER}{F9}
send ndwarven{SPACE}beer{RIGHT}{ENTER}{F9}
send ndwarven{SPACE}wine{RIGHT}{ENTER}{F9}
send ndonkey{SPACE}meat{RIGHT}{ENTER}{F9}
send nchimpanzee{SPACE}meat{RIGHT}{ENTER}{F9}
send ngazelle{SPACE}meat{RIGHT}{ENTER}{F9}
send nbonobo{SPACE}meat{RIGHT}{ENTER}{F9}
send nmule{SPACE}meat{RIGHT}{ENTER}{F9}
send ndeer{SPACE}meat{RIGHT}{ENTER}{F9}
send nraccoon{SPACE}meat{RIGHT}{ENTER}{F9}
send nfox{SPACE}meat{RIGHT}{ENTER}{F9}
send nrhesus{SPACE}macaque{SPACE}meat{RIGHT}{ENTER}{F9}
send nhorse{SPACE}meat{RIGHT}{ENTER}{F9}
send ngroundhog{SPACE}meat{RIGHT}{ENTER}{F9}
send nmountain{SPACE}goat{SPACE}meat{RIGHT}{ENTER}{F9}
send nhoary{SPACE}marmot{SPACE}meat{RIGHT}{ENTER}{F9}
send ngorilla{SPACE}meat{RIGHT}{ENTER}{F9}
send norangutan{SPACE}meat{RIGHT}{ENTER}{F9}
send nsiamang{SPACE}meat{RIGHT}{ENTER}{F9}
send nbilou{SPACE}meat{RIGHT}{ENTER}{F9}
send npileated{SPACE}gibbon{SPACE}meat{RIGHT}{ENTER}{F9}
send nmandrill{SPACE}meat{RIGHT}{ENTER}{F9}
send nturtle{RIGHT}{ENTER}{F9}
</pre>

===='First Fortress' setup====
This macro works with the default setup of DF, and starts you with (almost) the setup suggested in the "Your first fortress" tutorial. The amounts are adjustable with the variables at the top of the macro.
<pre>;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; materialplanner.ahk ;
; this is a ahk script to set up the embark settings roughly as ;
;suggested in the "your first fortress" tutorial. Inventory ;
;can be customized slightly. ;
; use ctrl+shift+e to run ;
; ;
; NOTEs: ;
; change variables to suit your desires ;
; the fourth guy is a Stonecrafter instead of Herbalist ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

;;;;;;;;;;;;;
;;VARIABLES;;
;;;;;;;;;;;;;

PICKS = 2 ;number of picks to pack
AXES = 1 ;number of axes to pack
ANVILS = 0 ;number of anvils to pack
MEATS = 7 ;how much meat to take, each buys one of each cheap type (total number depends on locale)
DRINKS = 26 ;how many drinks to take, each one buys 4 drinks, one of each type
SEEDS = 5 ;each increment buys 5 plump helmet spawn, 2 pig tail, and 2 rock nuts

SetKeyDelay, 12 ;Key delay, to keep Dwarf Fortress from being overwhelmed.
;Set higher if you get weird results, or lower to get the
;script to run faster
SLEEPTIME = 12 ;same thing, only used in the repeated key press loops though

;;;;;;;;;;;;
;;The code;;
;;;;;;;;;;;;

^+e::
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

;remove all of the items
Send {Tab}

loop 105{
Send {NumpadSub}
Sleep %SLEEPTIME%
}

Send {Tab}

;place the skills
;first guy
;Proficient Miner
Send {right}
loop 5{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}
;novice appraiser
Send {PgUp}
loop 7{
Send {Up}
Sleep %SLEEPTIME%
}
Send {NumpadAdd}
;novice Judge of Intent
Send {Up}
Send {NumpadAdd}
;competent gem setter
Send {PgUp}
Send {PgUp}
loop 7{
Send {Up}
Sleep %SLEEPTIME%
}
loop 3{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}
;second guy
Send {Left}
Send {Down}
Send {Right}
Send {PgUp}
;Proficient Miner
loop 5{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}
;Proficient Mason
loop 3{
Send {Down}
Sleep %SLEEPTIME%
}
loop 5{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}
;third guy
Send {Left}
Send {Down}
Send {Right}
;Proficient Carpenter
Send {UP}
loop 5{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}
;Proficient Wood Cutter
Send {UP}
loop 5{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}
;fourth guy
Send {Left}
Send {Down}
Send {Right}
;Proficient Grower
Send {PgDn}
Send {Down}
Send {Down}
loop 5{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}
;Proficient Stone Crafter
loop 9{
Send {Up}
Sleep %SLEEPTIME%
}
loop 5{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}
;fifth guy
Send {Left}
Send {Down}
Send {Right}
;Proficient Mechanic
loop 5{
Send {Down}
Sleep %SLEEPTIME%
}
loop 5{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}
;Proficient Building Designer
Send {PgUp}
loop 5{
Send {Down}
Sleep %SLEEPTIME%
}
loop 5{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}
;sixth guy
Send {Left}
Send {Down}
Send {Right}
;Proficient Weaponsmith
loop 1{
Send {Down}
Sleep %SLEEPTIME%
}
loop 5{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}
;Proficient Armorsmith
loop 2{
Send {Down}
Sleep %SLEEPTIME%
}
loop 5{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}
;seventh guy
Send {Left}
Send {Down}
Send {Right}
;Proficient Cook
Send {PgDn}
loop 2{
Send {Up}
Sleep %SLEEPTIME%
}
loop 5{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}
;Proficient Brewer
loop 1{
Send {Up}
Sleep %SLEEPTIME%
}
loop 5{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

;do the inventory
Send {Tab}

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;Meat

if MEATS > 0
{
tmp := MEATS - 1
send ndonkey{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send nchimpanzee{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send ngazelle{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send nbonobo{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send nmule{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send ndeer{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send nraccoon{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send nfox{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send nrhesus{SPACE}macaque{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send nhorse{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send ngroundhog{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send nmountain{SPACE}goat{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send nhoary{SPACE}marmot{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send ngorilla{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send norangutan{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send nsiamang{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send nbilou{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send npileated{SPACE}gibbon{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send nmandrill{SPACE}meat{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}
send nturtle{RIGHT}{ENTER}
loop %tmp%{
Send {NumpadAdd}
}
Send {F9}

}

;copper picks
if PICKS > 0
{
Send {n}copper picks{Right}{Enter}
tmp := PICKS - 1
loop %tmp%{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}
}
;Axes
if AXES > 0
{
Send {n}steel axes{Right}{Enter}
tmp := AXES - 1
loop %tmp%{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}
}
;Seeds
if SEEDS > 0
{
send {n}Rock nuts{Right}{Enter}
Send {NumpadAdd}
send {n}plump helmet spawn{Right}{Enter}
Send {NumpadAdd}
Send {NumpadAdd}
Send {NumpadAdd}
Send {NumpadAdd}
send {n}Pig tail Seeds{Right}{Enter}
Send {NumpadAdd}

tmp := SEEDS - 1
loop %tmp%{
Send {NumpadAdd}
Send {NumpadAdd}
}
Send {up}
loop %tmp%{
Send {NumpadAdd}
Send {NumpadAdd}
Send {NumpadAdd}
Send {NumpadAdd}
Send {NumpadAdd}
}
Send {up}
loop %tmp%{
Send {NumpadAdd}
Send {NumpadAdd}
}
}

;Anvils
if ANVILS > 0
{
Send {n}iron anvils{Right}{Enter}
tmp := ANVILS - 1
loop %tmp%{
Send {NumpadAdd}
Sleep %SLEEPTIME%
}
}
;Drinks
if DRINKS > 0{
send {n}Dwarven ale{Right}{Enter}
send {n}Dwarven beer{Right}{Enter}
send {n}Dwarven wine{Right}{Enter}
send {n}Dwarven rum{Right}{Enter}

tmp := DRINKS - 1
loop 4{
loop %tmp%{
Send {NumpadAdd}
}
Send {up}
}

return
</pre>

===A more modular approach===
Hit WIN+G to go once you are on the empty item screen

<pre>
#g::
;add an anvil
Additem("iron anvils",1)
;add 31 of the boozes (kind of iffy might end up with dwarven cheese or something if the civilization does not have 4 boozes)
Additem("dw",31)
Additem("dw",31)
Additem("dw",31)
Additem("dw",31)
;adds copper nuggets
Additem("copper n",5)
;adds cassiterite
Additem("cass",5)
;bitumous coal
Additem("coal",5)
;tower cap logs
Additem("logs",11)
return

IsCurrentItemThere()
{
;color of text in the new item screen 0xFFFF00(selected) or 0x808000 (unselected)
;location of text in the new item screen 305, 150
PixelSearch, , , 305, 150, 315, 160, 0x808000, 3,
return !ErrorLevel
}

AddItem(name,amount)
{
Sleep 100
amount -= 1
SetKeyDelay 150
SendInput n
SendInput %name%
;MsgBox Name Check
Sleep 200
if IsCurrentItemThere()
{
Sleep 200
SendInput {Right}
SendInput {Enter}
Sleep 200
Loop
{
if amount <= 0
{
break
}
SendInput {NumpadAdd}
Sleep 10
amount --
}
;MsgBox Done
}
else
{
SendInput {F9}
}
}
</pre>

===Bed Assigning macro===
This will assign bedrooms to your dwarfs. Press F3 followed by a single digit indicating how many beds to assign. Can repeat the action, as the number of beds assigned is stored in a counter. Room size is default, but easily edited into the script. By [[User:Napsterbater|Napsterbater]].

<pre>
bedcounter = 0
F3::
Input, counter, L1
SetKeyDelay, 100
loop %counter% {
loop %bedcounter%
send {Down}
loop % A_Index - 1
send {Down}
send {q}{r}{Enter}{a}
loop %bedcounter%
send {NumPadAdd}
loop % A_Index - 1
send {NumPadAdd}
send {NumPadAdd}{Enter}
send {space}{r}
}
bedcounter += counter
return
</pre>

===Room-designation macros===

====Valdemar's Designator Macro====
This macro can read a spreadsheet and designate rooms according to it. [http://www.bay12games.com/forum/index.php?topic=1428.0 Version 1]

Version 2 of this macro apparently only works in versions up to and including 38c [[verify]], and can be found here: [http://www.bay12games.com/forum/index.php?topic=1890.0 Version 2]

====Fedor's chambered circle====
A circular room with eight equal-sized chambers, suitable for everything from housing to workshops to a mausoleum. 
[http://mkv25.net/dfma/movie-216-room-designationmacro01 See this macro in action] 
[[Macros_and_Keymaps_Examples#Room-designation Macro 01|Macro text]]

====Valdemar's bedroom complex====
A large fractal bedroom/dining complex, with 56 bedrooms and room for 24 tables.

You can press Alt-B to create a bedroom block, or Alt-C to create a full complex with 4 bedroom blocks and a dining block in the center.

Note - the macro is much faster than the demo movie shows, it is done in under a minute.

[http://mkv25.net/dfma/movie-252 Demo Movie]

[http://www.pindi.us/files/fractalbr.zip Download]

====Tulip's room macros====
Based on [[Bedroom_design|the bedroom designs.]]

^g means alt+g, !g means ctrl+g, and so on.
Open up the designations window before using these:
<pre>
; This will make a basic 'x' pattern workshop/room layout
; and will 'land' back on the same tile it starts on each time,
; which happens to be the center.
; It is modified so that you will have 3 staircases, and an extra tile
; because many workshops do not have corner access.
!r::
Send di2{enter}88{enter}4d{enter}4{enter}67{enter}77{enter}66666666
Send {enter}11{enter}1{enter}6{enter}114{enter}4{enter}2{enter}11{enter}
Send 66666666{enter}77{enter}7{enter}6{enter}74
return

; This makes GnomeChomsky's Tessellated Apartments, bedrooms only.
; Your cursor will be over the left staircase.
!g::
Send i999866{enter}{enter}33332{enter}{enter}11114{enter}{enter}
Send d3{enter}22{enter}4{enter}{enter}
Send 78{enter}44{enter}8{enter}{enter}
Send 96{enter}88{enter}6{enter}{enter}
Send 32{enter}66{enter}2{enter}{enter}
Send 96{enter}{enter}6{enter}88{enter}
Send 96{enter}{enter}8{enter}44{enter}
Send 1444{enter}{enter}2{enter}66{enter}
Send 88{enter}88{enter}6{enter}{enter}
Send 78{enter}{enter}8{enter}44{enter}
Send 78{enter}{enter}4{enter}22{enter}
Send 14{enter}{enter}2{enter}66{enter}
Send 66{enter}22{enter}4{enter}{enter}
Send 14{enter}{enter}8{enter}44{enter}
Send 78{enter}{enter}4{enter}22{enter}
Send 14{enter}{enter}2{enter}66{enter}
Send 32{enter}{enter}6{enter}88{enter}7i{enter}{enter}
return

; This makes GnomeChomsky's Tessellated Apartments, bedrooms plus dining.
; Everything above applies.
^g::
Send i{enter}{enter}999866{enter}{enter}33332{enter}{enter}11114{enter}{enter}d
Send 444{enter}{enter}2{enter}66{enter}
Send 32{enter}{enter}6{enter}88{enter}
Send 9966{enter}{enter}6{enter}88{enter}
Send 96{enter}{enter}8{enter}44{enter}
Send 7788{enter}{enter}8{enter}44{enter}
Send 78{enter}{enter}4{enter}22{enter}
Send 1144{enter}{enter}4{enter}22{enter}
Send 14{enter}{enter}2{enter}66{enter}
Send 36{enter}8886666666{enter}
Send 9{enter}4444444{enter}
Send 8{enter}6666{enter}744{enter}{enter}
Send 222222441{enter}6666666{enter}
Send {enter}22{enter}8{enter}4444{enter}
Send 7778
return

; This makes THLawrence's Living Pods (the A is for Arabia).
; Put your cursor where you want the upper left staircase to be.
; Like my other scripts, it recenters on that tile.
; Also, thank you THLawrence, this one was really easy write!
!a::
Send i{enter}{enter}d7{enter}7{enter}666{enter}3{enter}22{enter}1{enter}44{enter}7{enter}
Send 96666666
Send i{enter}{enter}d7{enter}7{enter}666{enter}3{enter}22{enter}1{enter}44{enter}7{enter}
Send 33222
Send i{enter}{enter}d7{enter}7{enter}666{enter}3{enter}22{enter}1{enter}44{enter}7{enter}
Send 7444
Send i{enter}{enter}d7{enter}7{enter}666{enter}3{enter}22{enter}1{enter}44{enter}7{enter}
Send 9988888
return

; This makes the lobby for THLawrence's Living pods.
^a::
Send i{enter}{enter}d7{enter}7{enter}666{enter}3{enter}66{enter}9{enter}66{enter}3{enter}41i{enter}{enter}
Send 36d{enter}1444444{enter}
Send 74{enter}1{enter}22{enter}3{enter}3i{enter}{enter}d1{enter}1{enter}666{enter}9{enter}
Send 66{enter}3{enter}66{enter}9{enter}88{enter}7{enter}74{enter}1144{enter}
Send 36666i{enter}{enter}777777
return
</pre>

====LordGrunt's room macro====
Based on 1 of the fractal [[Bedroom_design| bedroom designs.]]

[http://mkv25.net/dfma/movie-1226-fractalbedrooms Demo Movie]

<pre>
;
; Fractal Apts
; Start script while in 'dig' mode with cursor on desired position of left up staircase
;
; ALT+G to generate,
; CTRL+ALT+G to erase in case of failure
;

!g::
base_cross()
sleep 100
mid_sqr()
sleep 100
corridors()
sleep 100
all_rooms()
return

base_cross()
{
Send i{ENTER}3{ENTER}
Send d1{ENTER}6{SHIFT}+2{SHIFT}+2{SHIFT}+2{SHIFT}+28{ENTER}
Send d{SHIFT}+8{SHIFT}+8{SHIFT}+8{SHIFT}+888{ENTER}4{SHIFT}+8{SHIFT}+8{SHIFT}+8{SHIFT}+82{ENTER}
Send d{SHIFT}+2{SHIFT}+2{SHIFT}+2{SHIFT}+24{ENTER}2{SHIFT}+4{SHIFT}+4{SHIFT}+4{SHIFT}+46{ENTER}
Send d{SHIFT}+6{SHIFT}+6{SHIFT}+6{SHIFT}+666{ENTER}8{SHIFT}+6{SHIFT}+6{SHIFT}+6{SHIFT}+64{ENTER}
Send d{SHIFT}+4{SHIFT}+4{SHIFT}+4{SHIFT}+4474{SHIFT}+8{SHIFT}+888888{ENTER}66666{SHIFT}+2{SHIFT}+2{SHIFT}+2{SHIFT}+2{SHIFT}+2222{ENTER}8
Send d{SHIFT}+8{SHIFT}+88884488888{SHIFT}+6{SHIFT}+6666666{ENTER}22222{SHIFT}+4{SHIFT}+4{SHIFT}+4{SHIFT}+4{SHIFT}+4444{ENTER}6
}
mid_sqr()
{
Send d{SHIFT}+3666
send d{ENTER}{SHIFT}+9{SHIFT}+999999{ENTER}1{ENTER}9999{ENTER}9{ENTER}111{ENTER}
send d{SHIFT}+1{SHIFT}+1{SHIFT}+1{ENTER}999{ENTER}99{ENTER}1111{ENTER}99
send d{SHIFT}+8{SHIFT}+8{SHIFT}+8444{ENTER}333{ENTER}33{ENTER}7777{ENTER}
send d{SHIFT}+3{SHIFT}+3{SHIFT}+37{ENTER}333{ENTER}7{ENTER}7777{ENTER}
}
corridors()
{
send d{SHIFT}+7{SHIFT}+7{SHIFT}+7999{ENTER}{SHIFT}+6{SHIFT}+6{SHIFT}+66{ENTER}
send d333333{ENTER}{SHIFT}+2{SHIFT}+2{SHIFT}+22{ENTER}
send d111111{ENTER}{SHIFT}+4{SHIFT}+4{SHIFT}+44{ENTER}
send d777777{ENTER}{SHIFT}+8{SHIFT}+8{SHIFT}+88{ENTER}
sleep 100
send d3333222{ENTER}{SHIFT}+466{ENTER}
send d{SHIFT}+2{SHIFT}+2888{ENTER}{SHIFT}+644{ENTER}
send d{SHIFT}+9{SHIFT}+9{SHIFT}+6{SHIFT}+6333
send d{ENTER}{SHIFT}+466{ENTER}
send d{SHIFT}+2{SHIFT}+2888{ENTER}{SHIFT}+644{ENTER}
sleep 100
send d{SHIFT}+4{SHIFT}+1966
send d{ENTER}{SHIFT}+288{ENTER}
send d{SHIFT}+4{SHIFT}+4666{ENTER}{SHIFT}+822{ENTER}
sleep 100
send d{SHIFT}+9{SHIFT}+9{SHIFT}+8{SHIFT}+8777
send d{ENTER}{SHIFT}+288{ENTER}
send d{SHIFT}+4{SHIFT}+4666{ENTER}{SHIFT}+822{ENTER}
sleep 100
send d999988{ENTER}{SHIFT}+64{ENTER}
send d{SHIFT}+3{SHIFT}+3{SHIFT}+3777{ENTER}{SHIFT}+28{ENTER}
send d{SHIFT}+1{SHIFT}+1{SHIFT}+1999{ENTER}{SHIFT}+46{ENTER}
send d{SHIFT}+7{SHIFT}+7{SHIFT}+7333{ENTER}{SHIFT}+82{ENTER}
}

rooms_up()
{
send d78{ENTER}96{ENTER}
send d223{ENTER}32{ENTER}
send d44444{ENTER}87{ENTER}
send d63{ENTER}{ENTER}98{ENTER}{ENTER}23{ENTER}{ENTER}7
}
rooms_down()
{
send d32{ENTER}14{ENTER}
send d887{ENTER}78{ENTER}
send d66666{ENTER}32{ENTER}
send d74{ENTER}{ENTER}21{ENTER}{ENTER}78{ENTER}{ENTER}3
}
rooms_left()
{
send d14{ENTER}87{ENTER}
send d996{ENTER}63{ENTER}
send d2222{ENTER}41{ENTER}
send d98{ENTER}{ENTER}47{ENTER}{ENTER}96{ENTER}{ENTER}1
}
rooms_right()
{
send d96{ENTER}32{ENTER}
send d114{ENTER}47{ENTER}
send d8888{ENTER}96{ENTER}
send d21{ENTER}{ENTER}63{ENTER}{ENTER}14{ENTER}{ENTER}9
}
;======= WIDE
rooms_upw()
{
send d78{ENTER}966{ENTER}
send d223{ENTER}32{ENTER}
send d444444{ENTER}87{ENTER}
send d63{ENTER}{ENTER}98{ENTER}6{ENTER}23{ENTER}{ENTER}74
}
rooms_downw()
{
send d32{ENTER}144{ENTER}
send d887{ENTER}78{ENTER}
send d666666{ENTER}32{ENTER}
send d74{ENTER}{ENTER}21{ENTER}4{ENTER}78{ENTER}{ENTER}36
}
rooms_leftw()
{
send d14{ENTER}887{ENTER}
send d996{ENTER}63{ENTER}
send d22222{ENTER}41{ENTER}
send d98{ENTER}{ENTER}47{ENTER}8{ENTER}96{ENTER}{ENTER}12
}
rooms_rightw()
{
send d96{ENTER}322{ENTER}
send d114{ENTER}47{ENTER}
send d88888{ENTER}96{ENTER}
send d21{ENTER}{ENTER}63{ENTER}2{ENTER}14{ENTER}{ENTER}98
}
;============
rooms3up()
{
send d8888888
rooms_up()
send d1111222
rooms_left()
send d66666666
rooms_right()
send d4444
}
rooms3down()
{
send d2222222
rooms_down()
send d7777888
rooms_left()
send d66666666
rooms_right()
send d4444
}
rooms3left()
{
send d4444444
rooms_left()
send d9999666
rooms_up()
send d22222222
rooms_down()
send d8888
}
rooms3right()
{
send d6666666
rooms_right()
send d7777444
rooms_up()
send d22222222
rooms_down()
send d8888
}

;==========
all_rooms()
{
;left wide:
rooms_up()
send d222222222
rooms_down()
send d7777444
rooms_leftw()
;bottom wide:
send d{SHIFT}+3{SHIFT}+3{SHIFT}+3{SHIFT}+378
rooms_downw()
send d9999888
rooms_right()
send d444444444
rooms_left()
;right wide:
send d{SHIFT}+9{SHIFT}+9{SHIFT}+999{SHIFT}+66
rooms_rightw()
send d7777444
rooms_up()
send d222222222
rooms_down()
;top wide
send d{SHIFT}+7{SHIFT}+7{SHIFT}+777{SHIFT}+88
rooms_upw()
send d1111222
rooms_left()
send d666666666
rooms_right()
;remainin 9-room chambers
send d{SHIFT}+26666
rooms3right()
send d{SHIFT}+4{SHIFT}+4666
rooms3left()
send d{SHIFT}+1111
rooms3up()
send d{SHIFT}+2{SHIFT}+2888
rooms3down()
send d{SHIFT}+3333
rooms3left()
send d{SHIFT}+6{SHIFT}+6444
rooms3right()
send d{SHIFT}+9999
rooms3down()
send d{SHIFT}+8{SHIFT}+8222
rooms3up()
;send d{SHIFT}+7777
;rooms3right()
;send d{SHIFT}+2{SHIFT}+4666
;rooms3left()
send d1111144499{ENTER}{SHIFT}+1{SHIFT}+4{SHIFT}+41{ENTER}
send d77444444444{ENTER}8888888{SHIFT}+6{SHIFT}+6{SHIFT}+6{SHIFT}+6{SHIFT}+6666{ENTER}
send d{SHIFT}+7{SHIFT}+487{ENTER}{SHIFT}+1{SHIFT}+2{SHIFT}+21{ENTER}
send d33222222222{ENTER}6666666{SHIFT}+8{SHIFT}+8{SHIFT}+8{SHIFT}+8{SHIFT}+8888{ENTER}
send d{SHIFT}+2{SHIFT}+2221111
send i{ENTER}3{ENTER}7
deco()
}

deco()
{
send x77774{ENTER}{ENTER}9{ENTER}{ENTER}6669{ENTER}6{ENTER}3666{ENTER}{ENTER}3{ENTER}{ENTER}
send x2223{ENTER}2{ENTER}1222{ENTER}{ENTER}1{ENTER}{ENTER}1444{ENTER}4{ENTER}4447
send x{ENTER}{ENTER}7{ENTER}{ENTER}7888{ENTER}8{ENTER}666666
}

; CTRL+ALT+G to erase all
!^g::
send x{SHIFT}+1{SHIFT}+1{SHIFT}+1{SHIFT}+1{SHIFT}+1{ENTER}{SHIFT}+9{SHIFT}+9{SHIFT}+9{SHIFT}+9{SHIFT}+9{SHIFT}+9{SHIFT}+9{SHIFT}+9{SHIFT}+9{SHIFT}+9{ENTER}{SHIFT}+1{SHIFT}+1{SHIFT}+1{SHIFT}+1{SHIFT}+1
return
</pre>

====Pyrofyr's room macro====
Based on Palin88's Apartment design based on Raynard's Fractal Design.

[[File:Pyrofor_room_macro.png]]

<pre>
/*
* Macro by Pyrofyr for Room Design -- Cleaned up by 0x517A5D
* Enter (d)esignate mode, position the cursor where you want the
* middle of the design to be, then press Ctrl+Alt+D to start the Macro.
*/

;Attn Pyrofor: for slash-star style comments, the ending star-slash must
;be the first thing on its line. Otherwise the comment isn't terminated.

#SingleInstance Force
#IfWinActive, Dwarf Fortress
SetKeyDelay 0,, Play

; Ctrl+Alt+D
^!d::
send d{NumPadUp 18}{NumPadLeft 18}
;Attn Pyrofor: note how repeated keystrokes are done in AHK.
;no need for tehLoop().
directions()
send {NumPadRight 18}
directions()
send {NumPadLeft 18}
send {NumPadDown 18}
directions()
send {NumPadRight 18}
directions()
middle()
stairs()
return

directions()
{
;hallway box
send {Enter}{NumPadRight 18}{Enter}
send {Enter}{NumPadDown 18}{Enter}
send {Enter}{NumPadLeft 18}{Enter}
send {Enter}{NumPadUp 18}{Enter}
;indentations on box
send {Enter}{NumPadRight 1}{NumPadDown 2}{Enter}
send {NumPadDown 6}{Enter}{NumPadDown 2}{NumPadRight 1}{Enter}
send {NumPadLeft 1}{NumPadDown 6}{Enter}{NumPadDown 1}{Enter}
send {NumPadRight 6}{Enter}{NumPadRight 4}{Enter}
send {NumPadRight 6}{Enter}{NumPadUp 1}{Enter}
send {NumPadUp 6}{Enter}{NumPadUp 2}{NumPadLeft 1}{Enter}
send {NumPadRight 1}{NumPadUp 6}{Enter}{NumPadUp 1}{Enter}
send {NumPadLeft 6}{Enter}{NumPadLeft 4}{Enter}
; middle hallways
send {NumPadRight 2}{Enter}{NumPadDown 6}{Enter}
send {NumPadRight 1}{Enter}{NumPadDown 4}{NumPadLeft 2}{Enter}
send {NumPadRight 1}{Enter}{NumPadDown 6}{Enter}
send {NumPadUp 8}{NumPadLeft 6}{Enter}{NumPadRight 14}{Enter}
; cross apartments, horizontal segments
send {NumPadDown 4}{Enter}{NumPadLeft 2}{Enter}
send {NumPadDown 1}{NumPadLeft 3}{Enter}{NumPadLeft 6}{Enter}
send {NumPadUp 1}{NumPadLeft 3}{Enter}{NumPadLeft 2}{Enter}
send {NumPadDown 3}{NumPadRight 2}{Enter}{NumPadRight 2}{Enter}
send {NumPadRight 8}{Enter}{NumPadRight 2}{Enter}
send {NumPadUp 5}{NumPadLeft 1}{Enter}{NumPadLeft 2}{Enter}
send {NumPadLeft 6}{Enter}{NumPadLeft 2}{Enter}
send {NumPadUp 4}{Enter}{NumPadRight 2}{Enter}
send {NumPadRight 6}{Enter}{NumPadRight 2}{Enter}
send {NumPadRight 3}{NumPadUp 2}{Enter}{NumPadLeft 2}{Enter}
send {NumPadUp 1}{NumPadLeft 3}{Enter}{NumPadLeft 6}{Enter}
send {NumPadDown 1}{NumPadLeft 3}{Enter}{NumPadLeft 2}{Enter}
send {NumPadUp 3}{NumPadRight 2}{Enter}{NumPadRight 2}{Enter}
send {NumPadRight 8}{Enter}{NumPadRight 2}{Enter}
; cross apartments, vertical segments
send {NumPadRight 1}{NumPadDown 2}{Enter}{NumPadDown 2}{Enter}
send {NumPadDown 6}{Enter}{NumPadDown 2}{Enter}
send {NumPadDown 3}{NumPadLeft 2}{Enter}{NumPadUp 2}{Enter}
send {NumPadLeft 1}{NumPadUp 3}{Enter}{NumPadUp 6}{Enter}
send {NumPadRight 1}{NumPadUp 3}{Enter}{NumPadUp 2}{Enter}
send {NumPadLeft 3}{NumPadDown 2}{Enter}{NumPadDown 2}{Enter}
send {NumPadDown 8}{Enter}{NumPadDown 2}{Enter}
send {NumPadLeft 4}{Enter}{NumPadUp 2}{Enter}
send {NumPadUp 8}{Enter}{NumPadUp 2}{Enter}
send {NumPadUp 2}{NumPadLeft 3}{Enter}{NumPadDown 2}{Enter}
send {NumPadRight 1}{NumPadDown 3}{Enter}{NumPadDown 6}{Enter}
send {NumPadLeft 1}{NumPadDown 3}{Enter}{NumPadDown 2}{Enter}
send {NumPadLeft 2}{NumPadUp 3}{Enter}{NumPadUp 2}{Enter}
send {NumPadUp 6}{Enter}{NumPadUp 2}{Enter}
send {NumPadUp 4}{NumPadLeft 2}
}

middle()
{
send {NumPadUp 10}{NumPadLeft 2}{Enter}{NumPadRight 4}{NumPadDown 20}{Enter}
send {NumPadUp 5}{NumPadRight 1}{Enter}{NumPadUp 10}{NumPadLeft 6}{Enter}
send {NumPadLeft 1}{NumPadDown 1}{Enter}{NumPadDown 8}{NumPadRight 8}{Enter}
send {NumPadUp 2}{NumPadRight 1}{Enter}{NumPadUp 4}{NumPadLeft 10}{Enter}
send {NumPadDown 1}{NumPadLeft 6}{Enter}{NumPadDown 2}{NumPadRight 22}{Enter}
send {NumPadUp 1}{NumPadLeft 11}
}

stairs()
{
send i{NumPadUp 18}{NumPadLeft 9}{Enter 2}
send {NumPadRight 18}{Enter 2}
send {NumPadRight 9}{NumPadDown 9}{Enter 2}
send {NumPadLeft 18}{Enter 2}
send {NumPadLeft 18}{Enter 2}
send {NumPadRight 9}{NumPadDown 9}{Enter 2}
send {NumPadRight 18}{Enter 2}
send {NumPadRight 9}{NumPadDown 9}{Enter 2}
send {NumPadLeft 18}{Enter 2}
send {NumPadLeft 18}{Enter 2}
send {NumPadDown 9}{NumPadRight 9}{Enter 2}
send {NumPadRight 18}{Enter 2}
send {NumPadLeft 9}{NumPadUp 18}
}
</pre>

===Easy Exploration Mining in 2 steps===
This macro will make a 5 row, 11 column UP/DOWN stairway grid (2 empty spaces between each row/column). 
Starting point as indicated (row 3, column 11) 
'''MUST BE IN DESIGNATION MODE WITH CURSOR AT THE ''<-- START HERE'' LOCATION''' 
Link is <ctrl> <windowskey> ` 
Dive is <ctrl> <alt> ` 
<pre>
Link
X--X--X--X--X--X--X--X--X--X--X
| | |
| | |
X--X--X--X--X--X--X--X--X--X--X
| | |
| | |
X--X--X--X--X--X--X--X--X--X--X <-- start here
| | |
| | |
X--X--X--X--X--X--X--X--X--X--X
| | |
| | |
X--X--X--X--X--X--X--X--X--X--X
</pre>
Filename is ExploreMine-Link.ahk
<pre>
;Link
^#`::

send d
send {Enter}
tehLoop(30,"{NumPadLeft}")
send {Enter}
send {Enter}
tehLoop(6,"{NumPadUp}")
send {Enter}
send {Enter}
tehLoop(30,"{NumPadRight}")
send {Enter}
send {Enter}
tehLoop(12,"{NumPadDown}")
send {Enter}
send {Enter}
tehLoop(30,"{NumPadLeft}")
send {Enter}
send {Enter}
tehLoop(9,"{NumPadUp}")
send {Enter}
send {Enter}
tehLoop(30,"{NumPadRight}")
send {Enter}
tehLoop(6,"{NumPadDown}")
send {Enter}
tehLoop(30,"{NumPadLeft}")
send {Enter}
tehLoop(3,"{NumPadDown}")
tehLoop(15,"{NumPadRight}")
send {Enter}
tehLoop(12,"{NumPadUp}")
send {Enter}
tehLoop(15,"{NumPadLeft}")

send i
send {Enter}{Enter}
tehOtherLoop("{NumPadDown}")
tehLoop(3,"{NumPadRight}")
send {Enter}{Enter}
tehOtherLoop("{NumPadUp}")
tehLoop(3,"{NumPadRight}")

send {Enter}{Enter}
tehOtherLoop("{NumPadDown}")
tehLoop(3,"{NumPadRight}")
send {Enter}{Enter}
tehOtherLoop("{NumPadUp}")
tehLoop(3,"{NumPadRight}")

send {Enter}{Enter}
tehOtherLoop("{NumPadDown}")
tehLoop(3,"{NumPadRight}")
send {Enter}{Enter}
tehOtherLoop("{NumPadUp}")
tehLoop(3,"{NumPadRight}")

send {Enter}{Enter}
tehOtherLoop("{NumPadDown}")
tehLoop(3,"{NumPadRight}")
send {Enter}{Enter}
tehOtherLoop("{NumPadUp}")
tehLoop(3,"{NumPadRight}")

send {Enter}{Enter}
tehOtherLoop("{NumPadDown}")
tehLoop(3,"{NumPadRight}")
send {Enter}{Enter}
tehOtherLoop("{NumPadUp}")
tehLoop(3,"{NumPadRight}")

send {Enter}{Enter}
tehOtherLoop("{NumPadDown}")
tehLoop(6,"{NumPadUp}")

tehLoop(tehTimes,tehDir)
{
loop
{
if tehTimes <= 0
{
break
}
send %tehDir%
tehTimes--
}
}

tehOtherLoop(tehOtherDir)
{
loop 4
{
tehLoop(3,tehOtherDir)
send {Enter}{Enter}
}
}
</pre>

<pre>
Dive
X X X X X X X X X X X

X X X X X X X X X X X

X X X X X X X X X X X <-- start here

X X X X X X X X X X X

X X X X X X X X X X X
</pre>

Filename is ExploreMine-Dive.ahk
<pre>
;Dive
^!`::
tehLoop(30,"{NumPadLeft}")
tehLoop(6,"{NumPadUp}")

send i
send {Enter}{Enter}
tehOtherLoop("{NumPadDown}")
tehLoop(3,"{NumPadRight}")
send {Enter}{Enter}
tehOtherLoop("{NumPadUp}")
tehLoop(3,"{NumPadRight}")

send {Enter}{Enter}
tehOtherLoop("{NumPadDown}")
tehLoop(3,"{NumPadRight}")
send {Enter}{Enter}
tehOtherLoop("{NumPadUp}")
tehLoop(3,"{NumPadRight}")

send {Enter}{Enter}
tehOtherLoop("{NumPadDown}")
tehLoop(3,"{NumPadRight}")
send {Enter}{Enter}
tehOtherLoop("{NumPadUp}")
tehLoop(3,"{NumPadRight}")

send {Enter}{Enter}
tehOtherLoop("{NumPadDown}")
tehLoop(3,"{NumPadRight}")
send {Enter}{Enter}
tehOtherLoop("{NumPadUp}")
tehLoop(3,"{NumPadRight}")

send {Enter}{Enter}
tehOtherLoop("{NumPadDown}")
tehLoop(3,"{NumPadRight}")
send {Enter}{Enter}
tehOtherLoop("{NumPadUp}")
tehLoop(3,"{NumPadRight}")

send {Enter}{Enter}
tehOtherLoop("{NumPadDown}")
tehLoop(6,"{NumPadUp}")

tehLoop(tehTimes,tehDir)
{
loop
{
if tehTimes <= 0
{
break
}
send %tehDir%
tehTimes--
}
}

tehOtherLoop(tehOtherDir)
{
loop 4
{
tehLoop(3,tehOtherDir)
send {Enter}{Enter}
}
}

</pre>

===Fancy Exploration Mining===
This script digs a connected series of mine shafts, as in [[Mineshaft Stitching]]. Start this script in the upper-left corner of the area you want to explore. Set the spacing to a value greater than 1 if you want to look for large clusters. Note that this pattern creates a very long walkway back to the start of the mineshafts. If you do not excavate routinely, consider connecting the top-level paths of areas you have already explored.

<pre>

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; stitching.ahk ;
; this is an ahk script to place exploratory mine shafts. ;
; press d and place the cursor ;
; in the top left corner of the area to be explored ;
; then use ctrl+shift+s to run ;
; to change parameters, use ctrl+shift+c ;
; Increasing spacing will increase some shafts ;
; This version resets it's state so that it can be re-run ;
; without having to reload the script ;
; ;
; NOTE: ;
; Author: Corey Amend ;
; Based on a script by Seth Fogarty, ;
; Which was based on a script by StrawberryBunny ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

x = 4
y = 4
depth = 3
wait = 100
spacing = 1
vdir = +.

DropShaft(vertdir, depth, wait)
{
Send i
Send {Enter}
Send {Enter}
Loop %depth%
{
Send %vertdir%
Send {Enter}
Send {Enter}
Sleep %wait%
}
}

^+c::
inputbox x, Input Length, Vertical pattern length: x-axis
inputbox y, Input Width, Horizontal pattern width: y-axis
inputbox depth, Input Depth, Mineshaft depth: z-axis
inputbox spacing, Input Spacing, Spacing multiplier (1 for complete visiblity)
inputbox wait, Input Delay, Delay in miliseconds (100 recommended)
return

^+s::
shafts := (x * y) -1
i := x-1
hdir = {Down}
next = {Up}

Loop %shafts%
{
DropShaft(vdir, depth, wait)
if (vdir = "+.")
{
vdir = +,
}
else
{
vdir = +.
}
Send d
k := spacing-1
Send %hdir%
Send {Enter}
Loop %k%
{
Send %hdir%
Send {Enter}
Send %hdir%
Send {Enter}
Send %hdir%
Sleep %wait%
}
Send %hdir%
Send {Enter}
Send %hdir%
Sleep %wait%
i--
if (i = 0)
{
if (hdir = "{Down}")
{
hdir = {Right}
next = {Up}
i=1
}
else if (hdir = "{Right}")
{
hdir = %next%
i := x-1
}
else if (hdir = "{Up}")
{
hdir = {Right}
next = {Down}
i=1
}
}
}
DropShaft(vdir, depth, wait)
if (vdir = "+.")
{
Loop %depth%
{
Send +,
}
}
else
{
vdir = +.
}
return

</pre>

===Upstairs Mineshaft Finisher===
This script is used to create a series of up staircases in a pattern for use with mineshaft scripts (like the mineshaft stitching above). Most mineshaft scripts use up/down staircases all the way to the bottom, but the lowest z-level will not allow up/down staircases so you mineshafts will be unfinished. This script allows you to correct this problem and place up stairs where the up/down stairs would be.

<pre>

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Upstair stitching.ahk ;
; this is an ahk script to place up stairs at regular ;
; intervals (useful for completing mine shafts). ;
; press d and place the cursor ;
; in the top left corner of the area to be explored ;
; then use ctrl+shift+u to run ;
; to change parameters, use ctrl+shift+p ;
; Increasing spacing will increase some shafts ;
; ;
; NOTE: ;
; Author: Corey Amend ;
; Based on a script by Seth Fogarty, ;
; Which was based on a script by StrawberryBunny ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

x = 4
y = 4
wait = 100
spacing = 1
vdir = +.

^+p::
inputbox x, Input Length, Vertical pattern length: x-axis
inputbox y, Input Width, Horizontal pattern width: y-axis
inputbox spacing, Input Spacing, Spacing multiplier (1 for complete visiblity)
inputbox wait, Input Delay, Delay in miliseconds (100 recommended)
return

^+u::
shafts := (x * y) -1
i := x-1
hdir = {Down}
next = {Up}

Loop %shafts%
{
Send u
Send {Enter}
Send {Enter}
Sleep %wait%

k := spacing-1
Send %hdir%
Loop %k%
{
Send %hdir%
Send %hdir%
Send %hdir%
Sleep %wait%
}
Send %hdir%
Send %hdir%
Sleep %wait%
i--
if (i = 0)
{
if (hdir = "{Down}")
{
hdir = {Right}
next = {Up}
i=1
}
else if (hdir = "{Right}")
{
hdir = %next%
i := x-1
}
else if (hdir = "{Up}")
{
hdir = {Right}
next = {Down}
i=1
}
}
}
Send u
Send {Enter}
Send {Enter}
Sleep %wait%

return

</pre>

===Interface Enhancement Scripts===

====The MOUSE control====
For unrivaled mouse control in DF try [http://www.dwarffortresswiki.net/index.php/User:Digger this DF Mouse script]

====Tile Counter or Scrolling Accelerator====
Lack of reference plus slow scroll speed make planning digging area frustrating,so here is the script that shows coordinate and speed scrolling up.
[http://www.dwarffortresswiki.net/index.php/User:Daedalusai ShowXY]

===4-Pour Water Creation script===
For Automating creation of water using Gibbeds Tweak.

<pre>
;
; 4-pour.ahk
; Dwarf fortress water creation script.
;
;Use this script in conjunction with Gibbeds Dwarf Fortress Tweak to create endless amounts of water.;
;
;Directions
;
;1. Have DF running and position the screen such that when you press "K" the X will appear where you

;want the water to appear.
;2. Have Gbbed's Dwarf Fortress tweak running in the background (with the proper process selected)
;3. run the 4-pour script
;4. press alt-p to get Pouring
;
;The script will then begin a cycle that moves the cursor around in a little 2x2 square editing each

;tile to have 7/7 of water, it then pauses for a half a seond to let the water flow a bit, and repeats.

;It does this until you..
;
;5. press and hold <shift> to stop
;
;As always, save before you experiment with this
;I hold no responsibility for what this script ends up doing to your dwarves/fortress/computer/carpet
;Feel free to clean it up, make it more usable, whatever
;
;

#NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases.
SendMode Input ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory.

!p::
loop

{
GetKeyState, state, Shift
if state = D
Break

IfWinActive Dwarf Fortress
{
WinActivate
}
send k
sleep 100
send {NumpadRight}

IfWinExist Gibbed's Dwarf Fortress Tweak [1.2.0.0]
{
WinActivate
}

click 38, 184, 2
sleep 100

IfWinExist Tile Edit
{
WinActivate
}
sleep 100
click 63, 448
sleep 100
click 106, 70
sleep 100
click 207, 255
sleep 100
send {backspace}
sleep 100
send 7
sleep 100
click 348, 449
sleep 100
IfWinExist Dwarf Fortress
{
WinActivate
}
sleep 100
send {NumpadDown}

IfWinExist Gibbed's Dwarf Fortress Tweak [1.2.0.0]
{
WinActivate
}

click 38, 184, 2
sleep 100

IfWinExist Tile Edit
{
WinActivate
}
sleep 100
click 63, 448
sleep 100
click 106, 70
sleep 100
click 207, 255
sleep 100
send {backspace}
sleep 100
send 7
sleep 100
click 348, 449
sleep 100
IfWinExist Dwarf Fortress
{
WinActivate
}
sleep 100
send {NumpadLeft}

IfWinExist Gibbed's Dwarf Fortress Tweak [1.2.0.0]
{
WinActivate
}

click 38, 184, 2
sleep 100

IfWinExist Tile Edit
{
WinActivate
}
sleep 100
click 63, 448
sleep 100
click 106, 70
sleep 100
click 207, 255
sleep 100
send {backspace}
sleep 100
send 7
sleep 100
click 348, 449
sleep 100
IfWinExist Dwarf Fortress
{
WinActivate
}
sleep 100
send {NumpadUp}

IfWinExist Gibbed's Dwarf Fortress Tweak [1.2.0.0]
{
WinActivate
}

click 38, 184, 2
sleep 100

IfWinExist Tile Edit
{
WinActivate
}
sleep 100
click 63, 448
sleep 100
click 106, 70
sleep 100
click 207, 255
sleep 100
send {backspace}
sleep 100
send 7
sleep 100
click 348, 449
sleep 100
IfWinExist Dwarf Fortress
{
WinActivate
}
send {space}
sleep 800
}

</pre>

===Tesselated Apartments Builder===

This one is another tesselated apartments script, with some larger areas added. Credit for layout to GnomeChomsky.

<pre>
;
; TessApts.ahk
; Start script while in 'dig' mode with cursor on desired position of leftmost staircase
;
; CTRL+G : Central room, 8 apartments (necessary on at least one z-level)
; ALT+G : No central room, 16 apartments
; CTRL+ALT+G : Four "central room" layouts connected in center (28 apartments)
; CTRL+SHIFT+G : Four "16 apartment" layouts, unconnected in center
;
!g::
Send i{ENTER}{ENTER}33332{ENTER}{ENTER}99996{ENTER}{ENTER}77778{ENTER}{ENTER}
Send d7{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 111{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 333333{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}
Send 99999988{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}114444444
return
^g::
Send i{ENTER}{ENTER}33332{ENTER}{ENTER}99996{ENTER}{ENTER}77778{ENTER}{ENTER}
Send d7{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 111{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 333333{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}
Send 99999988{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}
Send 7444{ENTER}{ENTER}1114{ENTER}{ENTER}3332{ENTER}{ENTER}9996{ENTER}{ENTER}788{ENTER}11111{ENTER}
return
!^g::
Send i{ENTER}{ENTER}33332{ENTER}{ENTER}99996{ENTER}{ENTER}77778{ENTER}{ENTER}
Send d7{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 111{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 333333{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}
Send 99999988{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}
Send 7444{ENTER}{ENTER}1114{ENTER}{ENTER}3332{ENTER}{ENTER}9996{ENTER}{ENTER}788{ENTER}11111{ENTER}88899999999
Send i{ENTER}{ENTER}33332{ENTER}{ENTER}99996{ENTER}{ENTER}77778{ENTER}{ENTER}
Send d7{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 111{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 333333{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}
Send 99999988{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}
Send 7444{ENTER}{ENTER}1114{ENTER}{ENTER}3332{ENTER}{ENTER}9996{ENTER}{ENTER}788{ENTER}11111{ENTER}3333332
Send i{ENTER}{ENTER}33332{ENTER}{ENTER}99996{ENTER}{ENTER}77778{ENTER}{ENTER}
Send d7{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 111{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 333333{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}
Send 99999988{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}
Send 7444{ENTER}{ENTER}1114{ENTER}{ENTER}3332{ENTER}{ENTER}9996{ENTER}{ENTER}788{ENTER}11111{ENTER}111114444444
Send i{ENTER}{ENTER}33332{ENTER}{ENTER}99996{ENTER}{ENTER}77778{ENTER}{ENTER}
Send d7{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 111{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 333333{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}
Send 99999988{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}
Send 7444{ENTER}{ENTER}1114{ENTER}{ENTER}3332{ENTER}{ENTER}9996{ENTER}{ENTER}788{ENTER}11111{ENTER}
Send 9988888888{ENTER}999{ENTER}+444444
return

+^g::
Send i{ENTER}{ENTER}33332{ENTER}{ENTER}99996{ENTER}{ENTER}77778{ENTER}{ENTER}
Send d7{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 111{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 333333{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}
Send 99999988{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}888889
Send i{ENTER}{ENTER}33332{ENTER}{ENTER}99996{ENTER}{ENTER}77778{ENTER}{ENTER}
Send d7{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 111{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 333333{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}
Send 99999988{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}+221
Send i{ENTER}{ENTER}33332{ENTER}{ENTER}99996{ENTER}{ENTER}77778{ENTER}{ENTER}
Send d7{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 111{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 333333{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}
Send 99999988{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}+1+46
Send i{ENTER}{ENTER}33332{ENTER}{ENTER}99996{ENTER}{ENTER}77778{ENTER}{ENTER}
Send d7{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 111{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}
Send 333333{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}32{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}
Send 99999988{ENTER}66{ENTER}2{ENTER}{ENTER}14{ENTER}22{ENTER}4{ENTER}{ENTER}78{ENTER}44{ENTER}8{ENTER}{ENTER}96{ENTER}88{ENTER}6{ENTER}{ENTER}+71144444
</pre>

===File pattern builder===

This is a script to create a macro out of any building pattern you like. If you like tesselated, this script will do it. If you like blocky, this script can do that, too. Just create a text file that contains the pattern you want to use and this macro will create it like nobody's business.

<pre>

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; File Pattern.ahk ;
; this is an ahk script to read a text file and use ;
; the pattern contained inside as a blueprint for digging ;
; press d and place the cursor ;
; in a corner of the area to be explored ;
; then use ctrl+shift+d to run ;
; to change parameters, use ctrl+shift+f ;
; ;
; NOTE: ;
; Author: Corey Amend ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

filename = C:\pattern.txt
loc = ul
wait = 100

wallsymbol = 1
floorsymbol = 0
updownsymbol = 2
downsymbol = 3
upsymbol = 4
rampsymbol = 5
channelsymbol = 6

digcommand = d
upcommand = u
downcommand = j
updowncommand = i
rampcommand = r
channelcommand = h

hdir = {Right}
vdir = {Down}

upperleft = ul
upperright = ur
lowerleft = ll
lowerright = lr

inrun = 0

^+f::
inputbox filename, Enter Path, Enter the full path to the file that contains the pattern to use
inputbox loc, Enter Cursor Location, Enter the location of the cursor within the pattern (Upper Left = ul`, Lower Right = lr...etc.)
inputbox wait, Enter Delay, Enter the delay to use (default is 100)
return

^+d::

IfExist, %filename%
{
FileRead, contents, %filename%
StringSplit Array, contents, `r, `n

if (loc = upperleft)
{
hdir = {Right}
vdir = {Down}
}
else if (loc = upperright)
{
hdir = {Left}
vdir = {Down}
}
else if (loc = lowerleft)
{
hdir = {Right}
vdir = {Up}
}
else if (loc = lowerright)
{
hdir = {Left}
vdir = {Up}
}
else
{
MsgBox, Invalid cursor location!
return
}

Loop %Array0%
{
if (loc = upperleft || loc = upperright)
{
current_line = %a_index%
}
else if (loc = lowerleft || loc = lowerright)
{
current_line := (Array0 - a_index + 1)
}

current_value := Array%current_line%

len := StrLen(current_value)

if (hdir = "{Left}")
{
new_value =

Loop %len%
{
new_value := new_value . SubStr(current_value, (len - a_index) + 1, 1)
}

current_value := new_value
}

Loop %len%
{
current_char := SubStr(current_value, a_index, 1)

if (current_char != wallsymbol)
{
if (!inrun)
{
if (current_char = floorsymbol)
{
Send %digcommand%
}
else if (current_char = updownsymbol)
{
Send %updowncommand%
}
else if (current_char = downsymbol)
{
Send %downcommand%
}
else if (current_char = upsymbol)
{
Send %upcommand%
}
else if (current_char = rampsymbol)
{
Send %rampcommand%
}
else if (current_char = channelsymbol)
{
Send %channelcommand%
}

Send {Enter}
inrun = 1
}

;;If we're at the end of a line or the next char is different, then end the run
if ((a_index >= len) || (current_char != SubStr(current_value, a_index + 1, 1)))
{
Send {Enter}
inrun = 0
Sleep %wait%
}
}

if (a_index < len)
{
Send %hdir%
}
}

if (a_index < Array0)
{
Send %vdir%

if (hdir = "{Right}")
{
hdir = {Left}
}
else if (hdir = "{Left}")
{
hdir = {Right}
}
}
}
}
else
{
MsgBox File not found
}

</pre>

Sample file to show how this all works:

<pre>

111111
100001
100201
103001
100401
105001
100601
100001
111111

</pre>

This creates a room filled with up/down stairs, a ramp, and a channel.

And finally, here's a sample pattern based on the decentralized workshop:

<pre>

1111111111111111111111111111111111111
1000000000000001000001000000000000001
1000000000000001000001000000000000001
1000000000000000000000000000000000001
1000000000000001000001000000000000001
1000000000000001000001000000000000001
1000111101111111110111111111011110001
1000100000001000100010001000000010001
1000100000001000100010001000000010001
1000100000001000100010001000000010001
1000000000000010000000100000000000001
1000111101111000100010001111011110001
1000100000001000100010001000000010001
1101100010001000100010001000100011011
1000100000001000100010001000000010001
1000111101111111100011111111011110001
1000100000000000030400000000000010001
1010000000000000030400000000000000101
1000100000000000030400000000000010001
1000111101111111100011111111011110001
1000100000001000100010001000000010001
1101100010001000100010001000100011011
1000100000001000100010001000000010001
1000111101111000100010001111011110001
1000000000000010000000100000000000001
1000100000001000100010001000000010001
1000100000001000100010001000000010001
1000100000001000100010001000000010001
1000111101111111110111111111011110001
1000000000000001000001000000000000001
1000000000000001000001000000000000001
1000000000000000000000000000000000001
1000000000000001000001000000000000001
1000000000000001000001000000000000001
1111111111111111111111111111111111111

</pre>

{{Game_Interface FAQ}}
[[Category:ahk scripts]]

40d:Utilities

2009-11-21T17:59:36Z

HebaruSan: /* 3D Visualizers */ stonesense has a wiki page, so link to it

Here are third party applications developed for Dwarf Fortress.
__TOC__
== [http://dffd.wimbli.com/ Dwarf Fortress File Depot] ==
The Dwarf Fortress File Upload Service - an excellent place to store mods, community games, tilesets and other files. Courtesy of [[User:Janus|Janus]]; for files related to Dwarf Fortress only.

== 3D Visualizers ==

=== [[Stonesense (visualizer)|Stonesense]] by Jonask, Solifuge and Kaypy ===
[[File:stonesense.jpg|208px|thumb|right|Stonesense Screenshot]]

Stonesense is a third party visualizer that lets you view your Dwarf Fortress world in a classic isometric perspective.

More information is available in [http://www.bay12games.com/forum/index.php?topic=43260.0 this forum thread].

=== [http://www.bay12games.com/forum/index.php?topic=39541.0 Visual Fortress] by Baboonanza ===

This is Baboonanza's 3D visualisation application. It's focused on displaying mega-projects and landscapes accurately and hopefully beautifully. Basically like 3Dwarf, but more advanced.

=== [http://www.bay12games.com/forum/index.php?topic=608.0 3Dwarf Visualizer] ===

This is NOT real time! Dwarvis has the ability to be real time, though 3Dwarf is much more recommended. What this does is read the map out of your computer's memory when Dwarf Fortress is running and save it to a file it can read. It can then open that file and show you your fort in glorious 3D. Still in beta, obviously.

=== [http://www.bay12games.com/forum/index.php?topic=34633.0 Khazad] ===

A related fortress viewing engine utilizing memory extraction and saving similar to 3Dwarf, Khazad uses an Isometric perspective reminiscent of SimCity200 & Transport Tycoon while also allowing very free form camera control in a full 3D environment. Khazad is compatible with 40d and 40d11 and entirely open source being licensed under the GPL, source and binary packages are available at [http://sourceforge.net/projects/khazad/ SourceForge]. Development is active and participation is welcome.

=== [http://code.google.com/p/dwarvis/ Dwarvis/MapExtract] (Outdated) ===

This project is meant as a 3rd party utility for the cult-game dwarf fortress. Its purpose is to eventually provide 3-dimensional visualization of static snapshots of the ingame world of a given fortress.

== Movies, Screenshots, Map Files ==

=== DF Map Compressor / DF Map Archive ===

*[http://shadowlord13.googlepages.com/dfmap-index.html SL's DF Map Compressor - Website]
*[http://mkv25.net/dfma/ Dwarf Fortress Map Archive]

The DF Map Compressor encodes multiple bitmaps exported from Dwarf Fortress into a single, very compressed, .fdf-map file. The fdf-map file can then be shared with your friends by uploading to the DF Map Archive that features an online viewer (written in Flash).

The map compressor was created by Shadowlord in May 2007. Extract from the website :
:"The '''DF Map Compressor''' is a program I made to encode Dwarf Fortress fortress or world map images into a much smaller format than is possible with normal image formats. Here's a quick summary of how it works: It determines the size of your tiles from your DF font file (or asks you), splits the map up into tiles, identifies duplicate tiles, writes out every unique tile image, and then writes out a list of ID#s for each tile position which points to the tile image for that tile. What it outputs is piped through the LZMA compressor (the one used in 7-zip), to compress it further. The .df-map file which it writes out is usually less than 100 KB in size. (By comparison, a PNG of the same map can exceed 2 megabytes, depending on how well you compress it, whether you change the color depth, and whether you are using a graphical tileset or detailed font)."

Read more about the [[User:Markavian/DF_Map_Archive|DF Map Archive]] on Markavian's User page.

=== [http://www.geocities.com/jifodus/CMVPlayer.zip CMVPlayer] ===

First released by Jifodus in April 2007. This application enables playback of the DF movies (.cmv) without starting DF. It also provides some more functionalities, such as :
* Rewind
* Pause
* Play frame per frame

To use, simply unzip the file, and drop and drag the movie on CMVPlayer.exe.

=== [http://dffd.wimbli.com/file.php?id=389 DwarfHeightmap] ===

A utility that imports 24bit greyscale bitmaps into world_gen.txt for use in DF's map generator.

=== Terrain Visualizer ===

View worldmaps in 3D! This utilizes version 0.28.181.39d's built in Legends Mode map exporter and a generic HeightMap terrain visualizer. Nothing super fancy, but neat to look at.
Get the [http://www.alpix.com/3d/TerrainViewer/ 3D Terrain Viewer] here, follow the instructions in the [http://www.bay12games.com/forum/index.php?topic=21468 Bay12Forums Thread] if you need help getting set up.

Or if you want super pretty maps, [http://www.bay12games.com/forum/index.php?topic=21469.0 see this topic], and get [http://www.planetside.co.uk/terragen/download.shtml Terragen]!

==Major Utilities==

=== [[User:Bartavelle/DwarfCompanion|Dwarf Companion]] ===

Created by [[User:Bartavelle|Bartavelle]], the Dwarf Companion is a graphical helper utility for dwarf fortress that aims to fill the gaps in the user interface. It allows for some nefarious cheating. For example, you can now mark your nobles as butcherable, and change possessed dwarves to fey moods.

=== [http://dwarfmanager.sourceforge.net/ Dwarf Manager] ===

Dwarf Manager is inspired by Dwarf Foreman (below) and has a similar overall layout, but improved features. You can not only assign jobs to profession groups but also to individual dwarves; you can view their current skill for a given job displayed handily in the job grid; and you can also change their personal and profession names straight from the interface. The program handles social and military skills as well.
In addition the program can be customized and updated by editing the included .xml files.

=== [http://www.pavlovian.net/foreman/ Dwarf Foreman] ===

Makes switching jobs on and off for large numbers of dwarves simple. Dwarves are grouped by their profession, or custom profession if they have one. By clicking on the graph you can enable any job for all dwarves with that profession. Still in alpha for this version of DF, if it doesn't recognize one of the new professions, check the file '''debug.txt''' in the directory you run foreman from.

Though prone to crashing currently, saving and exiting DF, starting foreman and then starting DF again will usually get it working again. Zorba would also appreciate it if you'd email him the crash log located in the Dwarf Foreman directory when this happens (zorba-foremancrash@pavlovian.net).

Dwarf Foreman currently allows you to change the jobs of visiting merchants, outpost liaisons, children, and any other dwarves that aren't normally controllable. It is unsupported but occasionally hilarious, and allows you to finally put those lazy dwarven children to work.

Source code is available.

To make Foreman compatible with '''v0.28.181.40d''', update config file as shown below. Use the [[Talk:Utilities#Dwarf Foreman|talk page]] for previous versions of DF.
<pre>
check=032e4b67
critter_start=01583224
dwarfidpos=0138f690
profession_start=0474
</pre>

'''Note:''' A Dwarf Foreman-like utility, with an expanded feature set, is also available. See Dwarf Manager below.

=== [http://dffd.wimbli.com/file.php?id=695 Mac Foreman] ===

This is a MacOSX 10.5 port of Dwarf Foreman.

Source code is available.

Dwarf Fortress version: '''v0.28.181.40d'''

=== [http://www.bay12games.com/forum/index.php?topic=39229.0 Dwarf Therapist] ===

Reported to be an improvement over Dwarf Manager.

=== [[User:Rick/Tweak|Gibbed's Dwarf Fortress Tweak]] ===

A toolset with many modules for tweaking / editing Dwarf Fortress memory.

=== [http://sun2design.com/quickfort/ Quickfort] ===

Quickfort is an AutoHotkey-based utility for Dwarf Fortress that helps you build fortresses from "blueprint" .CSV files (comma separated values). These files are easily created and edited in an app like Excel. Most building-oriented DF commands are supported through the use of multiple .CSV files to describe the different phases of DF construction (designation, building, stockpiles, and making adjustments).

=== [http://www.bay12games.com/forum/index.php?topic=18623.0 Modbase] ===

Modbase is a great tool made by Sean Mirrsen which allows you to freely swap mods and tweak game settings. For version 0.38c.

=== DF Raw Editor ===

DF Raw Editor is a brand new tool created to help edit the raw files.
It is available [http://www.bay12games.com/forum/index.php?topic=40413.0 here].
For version 0.40d

== Minor Utilities ==

=== DF Log Parser ===

A perl script written by Mephansteras that parses through the logs to show what civs owned what sites, what their overall populations were, and what the overall population levels of cave critters were. The output file makes it pretty easy to see how the various races are doing.

You will see:
Each Civilization, with overall ruler. Each site in that civ, with the local ruler. A summary of every entity in that civ.
A summary of every civ, by race
A listing of every Ruin
A listing of the total populations of cave critters
A listing of the total populations of civilized creatures

[http://dffd.wimbli.com/file.php?id=299 Raw perl script] - requires perl
[http://dffd.wimbli.com/file.php?id=311 Executable version] - does not require perl

=== [http://dffd.wimbli.com/file.php?id=278 DF World Generator] ===

Swiftly written supplement to the command line world generator. Written in Python, so you have to have Python installed to use this. It must be run from the command line and be in the DF Directory to work. Running the program with no parameters will provoke a short help-me dialog which will explain how to run it properly.
Enjoy!

=== [http://www.bay12games.com/forum/index.php?topic=949.0 Dtil] ===

Dtil is a general purpose tool host that supplies a dynamically generated SDK for plugin authors.

=== [http://www.bay12games.com/forum/index.php?topic=21351.0 Embark Anywhere] ===

Code based on 0x517A5D's Regional Prospector (above), allows you to embark ANYWHERE, how well that works depends on where you decide to go. Pure water areas are a suggested no as you can't do anything.

=== [http://dffd.wimbli.com/file.php?id=443 Enable Magma Buildings] ===

You need this utility in the case that you used the reveal utility before discovering any subsurface magma, or if you have reclaimed a fortress whose magma source has already been discovered.{{version|0.28.181.40d}} (If the hide utility is ever updated, you could also hide a few magma tiles and then dig them out. That worked in the old version.) Because there is no actual flag that controls whether magma has been seen (the game searches a list, probably a list of notable events), I had to patch the game's code. This means you need to run the utility every time you start dwarfort.exe and you want to build a new magma-using workshop.

This utility has been made version-independent. It is expected to work with future releases of Dwarf Fortress.

=== [http://75.127.91.201/~jifodus/df/justdigitout.zip Just dig it out!] ===

A utility by Jifodus. Disables warning messages about damp stone and hot stone. [http://www.bay12games.com/forum/index.php?topic=21892.0 Thread]

=== [http://www.bay12games.com/forum/index.php?topic=21601.0 Nano Fortress] ===

A utility that will allow embarks to 1x1 locations.

=== [http://angband.org/~erasmus/df/teleport22.zip Teleport] ===

Teleport dwarves and other creatures. Version 2.2 is independent of the DF version. (33c)

Note: This utility may not work on versions of DF 40d and later. If it doesn't work for you, try Dwarf Companion.

Caveat: The teleport utility does not correctly set the occupancy flag for map squares. As a results, dwarves will permanently crawl through the square that you teleported them out of. In addition, you cannot build structures in those squares.

=== [http://dffd.wimbli.com/file.php?id=645 Reveal] ===

Reveal (or Reveal.exe as it is commonly referred to) is a program that runs alongside Dwarf Fortress and shows all "unexplored" or "undug" tiles of the map (in fortress mode). To reveal entire map designate the entire bottom level to be mined and then remove designation before running reveal. Playing on revealed map might ''(read "will")'' cause some bugs (like not being able to build magma buildings or a tower-cap farm, losing all plants/trees on the map, and a lot more). '''Using Reveal has been known to corrupt saved game folders.''' and, as such, it is highly recommended to only use Reveal to preview a biome's layout and then restart without running Reveal.

There are two versions of Reveal, one for Vista and newer, one for XP and older.

The new version of Reveal.exe (Reveal2) is in public beta, you can find it here [http://dffd.wimbli.com/file.php?id=1044 Reveal2]. Please report problems in [[User_talk:0x517A5D|0x517A5D's Talk page]].

The Old version of Reveal.exe does not require you install anything (if you are using 0.28.181.40d and the updated memory.ini file), just unzip both files and run reveal.exe while DF is running.

If using [http://www.bay12games.com/forum/index.php?topic=40349.0 the OpenGL accelerated version] of DF (40d16) under XP SP3, the newer version of Reveal is required as the older version can't find it. Reveal2.exe works correctly with this setup.

=== [http://dffd.wimbli.com/file.php?id=1165 UltraFinder] ===

This AHK script generates worlds until it finds one with the desired features as defined in the init file.

This is not an advanced application, it is simply meant to take the task of repeated genning out of your hands.

The concept is that you set the parameters as you see fit, and leave it running while you go about your other business.

READ ALL WARNINGS IN THE INIT FILE!

The readme exists for a reason.

== Miscellaneous ==

These utilities were never designed with Dwarf Fortress in mind, but have been adapted to its use.

=== [[User:Jackard/Accent_Removal|Accent Removal]] ===

Certain tilesets leave a bunch of funky icons in the names of your dwarves! Replacing accented letters with normal ones in the raws fixes this problem.

=== [http://www.autohotkey.com/ AutoHotKey] ===

AHK lets you define global hotkeys to send a sequence of keystrokes. For example, you can have {{key|alt}}+{{key|w}} replace {{key|b}}-{{key|C}}-{{key|w}}-{{key|Enter}}-{{key|Enter}} to make wall building much easier. See [[Macros and Keymaps]] for a how-to and some example scripts. See [[:Category:ahk scripts]] for a list of user submitted scripts.

=== [http://winmerge.org/ Winmerge] ===

This utility allows you to compare folders or files. It highlights anything that does not fit in with the other file, so that you can see if you want to merge them into one file or not..

== Outdated Utilities ==

These programs are for previous versions of Dwarf Fortress, and have been left untouched for some time.

=== [http://dffd.wimbli.com/file.php?id=108 DFWall] ===

An utility for automation of mass constructions. Features three modes:

1. Rectangle rewalling - quickly build a rectangle of walls/floors using:
a) the same saved material every time ([http://mkv25.net/dfma/movie-495-dfwalldemo DEMO])
b) any material with at least 1/10/99 units

2. Quick reselect (for ANY single unit construction) - save that green glass box and never again have to look for it between all the bags!

3. Pattern construction - make a pattern file and have stuff constructed according to it ([http://mkv25.net/dfma/movie-520-dfwalldemo2 DEMO]).

For more details look here: [http://www.bay12games.com/cgi-local/ultimatebb.cgi?ubb=get_topic&f=2&t=001847 Thread]

=== [http://www.yourfilehost.com/media.php?cat=other&file=latitudes.zip Latitudes] ===

Latitudes is a utility that, when on the embark map screen, shows the X/Y coordinates of the current region. Until Toady adds [http://www.bay12games.com/cgi-local/ultimatebb.cgi?ubb=get_topic&f=5&t=002191 proper support], this will do the trick. Works in .32a through at least .33g. Technical notes: uses memory injection, so it may be flagged as a suspicious file by anti-virus programs.

=== [http://angband.org/~erasmus/df/lavasquare.exe Lavasquare] ===

Another quick hack to make a 7/7 unit of lava on the currently selected square. Ignore the random text it spams, as it was quickly adapted from a map query tool, and I didn't bother removing the print statements. Only works with version 33e. To hack this executable for a later version of dwarf fortress see the [[Talk:Utilities#Lavasquare|talk page]].

33g version plus autohotkey script: http://www.sendspace.com/file/xsl6gs

=== [http://www.bay12games.com/forum/index.php?topic=1447.0 StartProfile] ===

Jifodus wrote a little utility that lets you maintain profiles of your starting dwarves.

Check the thread on the forums for the latest download link. (Aug 01, 2008)

Incidentally, if you try this utility, please report success/failure in [[Talk:Utilities#StartProfile|the utilities talk page]].

=== [http://angband.org/~erasmus/df/water.exe Water] ===

Quick hack to refill ponds. Run this while your fortress is up, and it'll restore any "murky pool" tiles (i.e. the floor of ponds and lakes) to 7/7 water. If you've tunneled into a pond, it'll still refill but will flow out normally. Only works with version 33e due to its "quick hack" status. Note: If there is lava in a murky pool, it will be raised to depth 7/7.

[[Category:Utilities| ]]

Utility:Stonesense

2009-11-21T17:57:14Z

HebaruSan: categorize

[[File:stonesense.jpg|thumb|right|Stonesense Screenshot]]
''(disambiguation) If you are searching for "Stone Sense", the excellent reveal tool by 0x517A5D, see [http://dffd.wimbli.com/file.php?id=836]''

==Stonesense==
Stonesense is a third party visualizer that lets you view your Dwarf Fortress world in a classic isometric perspective.

The official thread for feedback, questions, requests or bug reports is located at http://www.bay12games.com/forum/index.php?topic=43260.0

==Project Homepage / Source code==
The project homepage and Source code repository (subversion) can be found at: http://code.google.com/p/stonesense/

==Sprites preview and todo list==
All sprite related stuff can be found at http://stonesense.wikia.com/wiki/Stonesense_Wiki
Please use that wiki for submitting sprites, 'claiming' sprites, etc. and not here or on the google code one.

==Credits==
* Stonesense was written by Jonask, peterix, and kaypy.
* Dfhack library was written by peterix.
* Initial graphics were provided by Solifuge.
* Additional Graphics were contributed by many people, including:
* Kaypy, 7centNickel, <many more>

[[Category:Utilities]]

40d:Defense design

2009-11-20T15:29:44Z

HebaruSan: a loophole is a way to avoid something, so it makes sense for taxes but not stimulus; but if this hurt some R's feewings I guess it can be made non-partisan

This page is one of several inter-related articles on the broader topic of defending your fortress and your dwarves. This page will focus on the physical layout and architecture of a fortress - specific suggestions, examples, diagrams and discussions of combining walls, fortifications, tunnels, channels, bridges, and terrain into a defensible whole.

See the [[Defense guide|Defense Guide]] for a general overview of threats and considerations for fortress defense.

For suggestions on training, organizing and deploying soldiers and militia, see [[Military design]].

Many defenses rely on complex traps as a central part, that are, essentially, the defense themselves. For complex traps that are '''not''' a minor/optional part of a larger defensive plan, (but might be adapted or plugged into one) see [[Trap design|Trap Design]].

----

:'''''Editors & Contributors''' - Please see top of [[Talk:Defense design|discussion page]] before posting.''

==Standard key==

'''Key:'''
'''symbol tile'''
· - Empty space
+ - Constructed floor, or top of wall section from lower level
'''0''' - Isolated wall section
╔╦═╗
╠╬═╣ - Connected wall
║║ ║
╚╩═╝
╬ - Fortifications
X - Up/down [[stairs]]
< - Up stair
> - Down stair
▲ - Up ramp/slope
▼ - Down ramp/slope
, - natural ground
☺ - dwarf

==General suggestions==
General designs should include suggestions that can be "plugged in" to a part of any typical fortress, and/or can be modified to suit a number of purposes.

Any fortress defenses need to be able to protect your dwarves while outside, whether that's military or civilians. On the truly labor intensive end, you can fully enclose areas of wilderness you wish to utilize in walls or behind moats with the only access being from within your base. Hostile creatures, even 'invisible' ones like ambushers, start at map edges and travel across the map - they will only spawn in regions where they can path to a dwarf. By controlling which areas have access to paths to dwarves, you can force all hostile forces to appear in predictable and limited killing zones and battlefields that you control.

===Meeting area as defense===

Especially in the very early game, you can use a [[Zone#Meeting_Area|meeting zone]] to attract animals and idle dwarves to a given area. This makes a pretty poor defense in general, but it's not a bad way to create an alarm system against minor threats such as [[thieves]] near your stockpiles, at least until you have something better (which won't be hard). Remove the zone later, or it attracts idle dwarves and children. Note that until you designate something else, the site of your wagon (even once deconstructed) is a default meeting area.

===Guard Animals===

Both [[thieves]] and [[ambush]]es are invisible until something bumps into them - a dwarf, a [[caravan]], a wild creature, a [[domestic animal]], anything. Once this happens (even if it was triggered by a wild [[groundhog]] on the far edge of the map), the game will pause with the appropriate [[announcement]], forcing your attention to the situation - which is nice. Therefore, it's a common practice to use animals to act as alarm systems, by [[restrain]]ing them in entryways.

There are some considerations to good placement of such animals. If you have a 1- or 2-wide hall, one animal is enough. If you have a 3-wide hallway (wide enough for a [[caravan]]), you need to restrain two animals, one at each side of the hall.

══════════ R = restraint
+++1R1++++ 1 = area of animal 1
+++bbb++++ 2 = area of animal 2
+++2R2++++ b = area of both
══════════

This pair creates a thief-proof barrier against unannounced intrusion, as there is no combination of locations where an invisible enemy can sneak by without bumping into one or both. Caravans can pass over [[restraint]]s and restrained creatures without problem.

Unless you're happy losing these animals on a regular basis, you should try to keep them alive...
:* Put them around a corner or behind a U-bend, so archers cannot fire at them from a distance.
:* Don't have them as your "first line of defense" - put them deeper in the entry, behind some traps
:* Put them inside, so flying creatures have to come down to their level to attack them.
:* Consider using a [[pressure plate]] at the extreme entrance to seal off the hall further down and keep your guard animal(s) safe. Thieves won't trigger them, but the animals can deal with those - ambushes ''will'' trigger them, and you don't want them getting to your guard animals.

Remember that anything short of a [[megabeast]] is not a good match for an armoured opponent. While watching your tame [[grizzly bear]] or [[alligator]] tear a thief apart has an amusement value, watching the goblin maceman send them flying across the map, mangled and dying, has less.

===Defending the edge===
You're not allowed to wall within five squares of the edge of the map... but this rule has more loopholes than the US federal income tax code. Until more versatile attackers emerge, it is not clear where effective play ends and exploit begins. ''(Note: we disclaim any responsibility for damage involving [[harpy|harpies]] and skeletal [[giant eagle]]s)''

* To start with, you can channel the '''''second''''' square from the edge. This blocks entry of trade caravans or their movement along the edge of the map. If barriers are used to prevent a Trade Depot near the edge of the map from being accessed from any other direction, caravans will be forced to appear in the un-channeled or bridged section of the edge, even if it is only three tiles wide. Your depot can be ready with stockpiles of favored trade goods, offset behind a wall to protect from archers a few squares away.

Train up diggers in soft soil and you can surround most of the map with a moat by the time the first migrants arrive. Be very, very wary of cave-ins, especially on highly sloped diagonal terrain - note that a downward ramp does not support adjacent floor tiles, and no tiles are supported diagonally.

Diplomats have a strange habit of appearing well inside the moat, but need to be allowed out when finished. ''[Note: On one 6x7 map [[horse]]s and other animals were also found to appear one embark unit (48 squares) left and up from the lower right corner, inside or atop the walls of a 5x5 doorless enclosure. Defend all leaks...]''

==== Design considerations ====

* The moat should be designed to prevent entry except by falling and entry except by climbing, from both sides. (Otherwise inside and outside forces might be tempted to shake hands from adjacent squares, with much annoyance) Despite an abundance of giant corkscrews, grates, ballista bolts, etc., no one has ever invented the ladder, so this keeps anyone from entering or leaving the rest of the map.
* The moat should be dry, because sooner or later you will be tempted to let someone visit the edge to loot goblins or hunt varmints, and next thing you know your Legendary Weaponcrafter who outpaces all your smelters will be whiling away his time carrying a leather thong to a stockpile when he runs into a groundhog and decides to react by jumping into the moat and holding his breath beneath the shallow waters until he drowns. (As always, the notice that he has drowned is the first you'll hear of it)
* The moat doesn't actually ''need'' to be adjacent to the edge of the map except when conserving valuable surface terrain (such as [[tree]]s on a map that is mostly rock). It is easier to free trapped miners when they can dig further outward, and placing the moat on the sixth or further square in from the edge allows further modification with floodgates, walls, and doors. Any [[channeling]] permanently changes the dug-out tile to "Light Above Ground", which restricts these features from tiles near the edge even if floors are later constructed to close the space.
* Because migrants might turn up near wild animals or be followed closely by [[goblin]]s, it is nice to wall off the last square in shorter segments. Each one or two segments are served by a separate lever bridge. This can be done by:
** natural barriers. The map edge is mostly continuous ramp, but occasionally a break appears on an uneven surface, by a river channel, etc.
** trees. If left intact they separate any fertile patches into many small segments.
** floors. Although you can't directly Remove Stairs/Ramps at the edge, building a single square of floor on an up-ramp at the edge will destroy that up-ramp (and the down-ramp above it) and block movement around the edge. Building a square of floor on a down-ramp and then removing it creates a [[one-way]] path.
** You can build drawbridges *along* the edge and raise them. Combined with a channel right next to the drawbridge, this can completely obstruct passage of anything which can't destroy the bridge.
** You can build up ramps at the edge, which may disrupt passage?Needs testing
** Fortifications carved into the outer edge rock the next layer down? It may be possible to carve fortifications all the way around the edge of a rocky map, allowing entrance only onto designated bridges surrounded by moat and with a steep drop beneath, with some sized appropriately to admit siegers only and one other sized for a trade wagon. In this way combat can be reduced to a simple thumbs up/thumbs down decision at the lever.Probably not.
* Migrants, thieves, and sieges turn up all around the map, and can be allowed in by remote controlled bridges. (Doors will not hold back [[building destroyer]]s, and remote [[lever]] control is needed because other gates can be "taken by invaders" and become unlockable) Invaders can be allowed in by small groups and fought if desired, or preferably admitted into underground zigzags with a door waiting to be locked at the far end once they get close to it. If most of the invaders can be trapped inside such spaces, the remainder will stand and be wiped out completely without retreating.

===Simple 5x5 Archer's Tower===

Build a [[tower]] specifically to post archers on, possibly away from your main defenses. This lets you open fire before the enemy approaches your gates. A pillbox can be attached to your walls, or separate, so that the only access is from tunnels below. Thse tunnels can stretch across the map, and only need be 1-tile big if no regular traffic is expected. Construct [[fortification]]s on the second or third floor, so your dwarves can fire out. For extra usefulness, build a [[barracks]], [[archery target]], [[food]] [[stockpile]], [[well]] and [[dining room]] in or near the tower. Add a door or hatch to lock them in.

As discussed step-by-step in the article on [[mega construction]], this particular design is about as basic as it gets. As shown, it assumes entry from an underground tunnel, but a door or drawbridge (with moat!?) could easily be added, or even access via a protected sky-bridge.

When placing multiple towers, know that crossbows have a range of 20 tiles, so, depending on whether you want overlapping fire or not (and how intense/accurate), anywhere from maybe 15 to 38 tiles between the edge of the towers is recommended. Crossbows actually have their range ''reduced'' by extra height in DF, so all you need is 1 level up to keep enemy archers from using your fortifications against you, and you're set. (Channeling a defensive moat further out will also work, moving potential enemy archers even further away, but also moving non-missile targets that far as well.)

Side Below Ground Archer Roof
view: ground: Level: Level: Level:
╔═══╗ ╬╬╬╬╬ ·····
X__ X ║X,,║ ╬X++╬ ·X++·
╬X__╬ ║,,,║ ╬+++╬ ·+++·
___║X__║___ ║,,,║ ╬+++╬ ·+++·
X ╚═══╝ ╬╬╬╬╬ ·····

_ = floor, natural , = ground tile
or constructed

This can hold 3 archers/side, and has the potential to be as many "archer levels" tall as you wish. A top-level "down stair" is necessary to build the "roof" - might as well build an up/down stair instead, no real reason not to. Remember to use the "corners first" technique when necessary. (See [[Tower]].)

All told, for a simple 1 archer-level tower, this takes just over 50 stones or blocks (plus 25/extra archer level).

Larger towers (or this with larger floors on higher levels) could house barracks, practice ranges, and other facilities. Just expand to preferred size with floors, and then attach walls to those to act as a base for the next level of building. Add more stairs (adjacent to each other is always better) if high traffic is anticipated.

====Siege engine turrets====
If it's big enough, build a [[siege engine]] inside a pillbox. Since siege engines cannot fire at targets higher or lower than them, the device needs to be on the same [[z-level]] as any targets, but this could be across a large gap to a nearby plateau. Only a single tile of fortifications is needed to fire through the wall. Position the tower to fire where invaders tend to congregate. Since [[siege operator]]s are civilians, the "dwarves stay underground" order must be off unless this is built as an open room under a natural ceiling.

You will want to guarantee that enemies do not approach the position and scare the civilian operators - this distance has been reported to be up to 20 tiles or so. Dig a moat, have some intervening valley or build some secondary fortifications to keep enemies at a distance. Unlike walls, fortifications on the same z-level do not block siege engine missiles, at any range. Unfortunately, if an enemy can walk up to them, fortifications will protect enemies from your archery fire (but not siege engine fire.)

===Control Room===
Have one (large?) room (or several stacked on top of each other) for all defense-related levers, and central to idle dwarves - near your [[meeting area]]s and [[noble]]s quarters, with one or more halls or stairs leading to it for quick access. Connect a lever to all those doors and hatches as the first lever to be pulled in an emergency, and the respondent will lock themselves in for you, guaranteeing that they will then have nothing else to do but stay there and pull levers.

It may also be an idea to have a second lever to at least one door, for emergency access. And possibly to add a stockpile of booze and food or a well for longer sieges.

===AI abuse===
Taking advantage of the game's Artificial Intelligence and [[path]]finding is a whole article in itself. Try leaving a door un-forbidden during an attack. When the bad guys approach the door, forbid it, and the enemy will wander off. Unlock it again, and they turn around and head back towards the door again. You can get enemies to march back and forth over a set of traps this way, or lure them deep into a complex trap. This could be automated via [[pressure plate]]s. This might count as an [[exploit]], or not - that's up to you, and what you consider fun and challenging.

===Bait animal===
[[Restrain]]ing a sacrificial animal just outside your walls, but within range of your marksdwarves and/or siege engines, can lure an enemy into attacking that while you cut them down. Make sure to place a pattern of some walls (or statues, see below) so enemy archers cannot simply shoot the creature from a safe distance.

=====Fortifications=====
Adding a ring of fortifications to help defend the animal against missile fire will keep melee troops away, but invite archers to come adjacent to the fortifications - and under your walls and crossbows. If you allow any path, the melee troops will try to follow it to the animal - be creative with that fact.

=====Traps=====
Surround the animal with traps to kill or capture approaching goblins.

=====U chumps=====
Surround the far side of the animal with a U shaped 3-sided wall, open facing your defenders, so the enemy has to come closer to attack the animal, and you gun them down.

=====Distractions=====
Releasing a [[cage]] full of surplus animals will keep the enemy archers very busy. They may even be out of ammo when your wrestlers show up.

=====Vanishing act=====
Having a linked drawbridge that can open/shut (perhaps on both a lever to open and a nearby pressure plate to close), to lure the enemy in under your guns and then protect the animal when they get too close (for multiple uses.)

=====Roach motel=====
Build a long, narrow, and twisty passage, accessible from the outside, but unconnected to your fortress. Build as many simple traps as you like. Place a bait animal inside. Enemy attackers walk right in, and get torn apart by the traps. If any manage to make it to the end, and kill the useless animal, they're surrounded by traps, and no closer to your fortress.

If the roach motel is deep enough underground, you can build a tunnel above it, channel down, and mark the channel a [[Activity_zone#Pit.2FPond|pit]]/pond. That way, you can "reload" a new bait animal.

=====vs. building destroyers=====
For [[building destroyers]], spare statues can serve the same purpose as bait animals.

=====Pathing slowdowns=====
If you're playing on a low-powered machine and you close up all entrances to your fortress during a siege, your game may grind to a halt and/or crash as the siegers continuously fail at pathfinding into your fortress. Bait animals may alleviate this.



==Entrance designs==

===Airlock defenses/buffer zone===
Build two walls, each with a drawbridge. Build the trade depot in the buffer zone between them. Keep the outer bridge open, and the inner one closed. When the merchants appear, put crossbows on the walls to guard their approach. Once all the merchants are safely inside, close the outer bridge. Once there's no enemies left in the buffer zone, open the inner bridge so your civilians can start loading up the depot.

The airlock pattern can be useful even without putting the depot there. Let a few siegers in at a time, and crush them. Reset the traps, Rest up the soldiers, and repeat.

===Siege Engines===
One effective way to have [[Siege engine]]s (help) defend your fortress is:

'''One ballista vs 3-wide hallway'''
══════════════════════════╦═════
Entrance++++++++++++▼·····║▐▀\
Entrance++++++++++++▼·····╬◄═«
Entrance++++++++++++▼·····║▐▄/
══════════════════════════╩═════

Using this design you can cripple an army using a well timed volley. The hallway can be much longer than shown if you wish, as ballistae have extended ranges well over 100 tiles. The channeled area is necessary, as civilians (siege operators are "civilians") will run when enemies get within about 5-10 tiles of them, regardless of the actual path to that threat.

====Ballista battery====
3 (or more!) ballistae can be put into a "battery" if overlapped - one per tile-width of the hallway, with each ballista aiming down their row of tiles.

╔═══
══════════════════════════╦══╦══╝▐▀\
Entrance++++++++++++▼·····╬ ╬▐▀\◄═« (~ammo~)
Entrance++++++++++++▼·····╬▐▀\◄═«▐▄/
Entrance++++++++++++▼·····╬◄═«▐▄/ (~ammo~)
══════════════════════════╣▐▄/ (~ammo~)
╚═════════

Be sure to use fortifications to prevent dwarfs from wandering in front of the ballista to their deaths. If desired (and you have the <s>man</s>dwarfpower to spare), catapults may be put behind those, as they shoot safely ''over'' workers in front of them. Altho' less effective than ballistae, it's a little more firepower - and that can't be a bad thing.

For added flavour, channel out one or more tiles down the length of the 3-wide hallway and install retractable bridges. When invaders attack, retract the bridges, forcing them into paths that are only 1-tile wide.

Adding additional channels on either side of the hall will allow stray ammo to be recovered at a later time. Make sure to add locked doors, to prevent siege operators from walking down below enemy archers during a battle.

===Flooded entrance===
Using a chamber as your entrance alongside a chamber full of water and some machinery you can flood or drain the entrance at will.

The basic premise requires two levers, two [[screw pump]]s and two [[Gear assembly|gear assemblies]]. The amount of power required and the number of additional components needed to get the power to the screw pumps varies depending on distance/setup. One pump is placed to draw from chamber 1 and dump into chamber 2. The other is set in reverse. A gear assembly is placed next to each pump and connected to the main power system. Each gear is linked to a lever. Now at the flip of a switch you can submerge your entrance with [[water]] or [[magma]] for easy, secure defense against creatures that aren't amphibious or magma-dwelling, depending.

[[Image:Entflood.jpg]]

The picture above shows the design in action. The green pump is currently on while the red has been disconnected through the grey marked axle. The yellow X is just to mark that there is a channel under the axle.

=== The "Reverse Battlement" design ===

Level Z+0 (ground):
,,,,,,,,,,,,,,,
F ═══════════════
O ,≥,g≥,,,g,,,,,,
R ,,≤,,,,,,g,,,,,
T ,,,g≤,,g,,,,,,, <-- enemies enter here
R ,,≥,,,,,,g,,,,,
E ,g,≤,,,,,,,,,g,
S ═══════════════
S ,,,,,,,,,,,,,,,

Level Z+1 (bridge):

E ·····║+++║·····
N +++++║+++║+++++
T ·····╬☺++║·····
R ·····╬☺++║·····
A ·····╬☺++║····· <-- archers shoot them from up above
N ·····╬☺++║·····
C ·····╬☺++║·····
E +++++║+++║+++++
·····║+++║·····

Note that in this diagram, the fortress interior is to the West, and the enemy forces come from the East. The marksdwarves on the bridge with the [[fortification]]s are one level above the [[goblin]]s (or other attackers), who will pass under the bridge and charge on toward the west. As the first clear from under the bridge, they are targeted from behind (which is one level above), as the marksdwarves wait in ambush. This allows the marksdwarves to face far fewer enemies at any one time, at least to begin with, and any enemy archers must clear the bridge, take their lumps, and then return fire back the other way before the marksdwarves are ever under attack.

For extra safety, hollow this tunnel out from under a ledge of the mountain (so it counts as "surface" and Dwarfs can "stay inside"). The bridge part can then be made out of construction, as soldiers can be ordered to go outside anyway.

If you're feeling especially nasty, make the tunnel really long into the mountain and add a ballista battery (see above). In my current version of the fortress, the goblins have to cross a long series of drawbridges to even get inside the mountain, so the ballista dwarf gets a lot of shots, and I can launch any escaping troops into the air.

''(Adding ammo stockpiles, of your best quality bolts, to these stations will speed up reloading for longer sieges/battles. Even adding small, convenient food and alcohol stockpiles is not unheard of. Some designers place access to/from archery ranges very close to these stations, for faster deployment.)''

==Scenic route==

[[Image:defense_3bridges.png|thumb|right]]
An example of some advanced defensive construction tactics to deal with vile forces of ''any'' size. (See picture).

*'''Bridge 1''' seals off the entire base
*'''Bridge 2''' forces everyone to take the long, winding, heavily trapped/defended path of death.
*'''Bridge 3''' seals the inside of the fortress

Clever triggering of the bridges allows you to break the hostile forces into smaller chunks to be trapped in the courtyard while being caught in traps and a crossfire of arrows from the fortifications around.

===Goblin detour===

This particular design works well with plenty of archers, siege engines, and other ranged weaponry.

++++++++++++++++++ENTRANCE+
══╦════════════════O╞═╡O╦══ <-- Bridge 1
+☺╬·+++++++++++++++++++·╬☺+
++╬·+···············╞═╡·╬++ <-- Bridge 2
++╬·+··+···+···+···++++·╬++
+☺╬·+·+·+·+·+·+·+·+·+++·╬☺+
++╬·+·+·+·+·+·+·+·+·+++·╬++
++╬·+·+·+·+·+·+·+·+·+++·╬++
+☺╬··+···+···+···+··+++·╬☺+
++╬·················+++·╬++
++╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╗·+++·╬++
++☺++☺++☺++☺++☺++☺╬·+++·╬☺+
++++++++++++++++++╬·+++·╬++
++++++++++++++++++╬·+++·╬++
══════════════╗++☺╬·+++·╬☺+
║+++╬·+++·╬++
║+++╬·+++·╬++
║++☺╬·╞═╡·╬☺+ <-- Bridge 3

The 3 tile wide lane is for traders, so if your [[trade depot]] is located before this set-up, cut it down to a 1 tile lane to slow down invaders more.

===Twisty maze===
A maze of turns and blindspots patrolled by quality military can be a very formidable defense. Wide enough for wagons to pass though, but with no clear shots for any ranged weapons. Missile weapons do have a minimum range, so if a target is closer than that range, they will instead just charge to melee - and meet a dwarf with a much better melee skill. Downside to this is that you'd be mixing it up in melee all the time, but so long as you have at least 10 dwarves greeting the goblins as one coherent mass, you should win.

Variations on the twisty maze include:

*A wagon-wide twisty maze, and a not-so-twisty 1-tile wide hall o'traps, with a drawbridge that can force one or the other as the only [[path]] into your fortress.

*Making the side of the maze into fortifications, with a channel separating the fortifications from the actual floor of the maze, and having your archery targets on the other side of the fortifications so your marksdwarves can practice. When the goblins round the corner, they charge through a hail of crossbow bolts, and drop dead.

[[Category:Guides]]
[[Category:Fortress defense| ]]
[[Category:World]]
[[Category:Design]]

40d Talk:Billon

2009-11-20T03:20:22Z

HebaruSan:

== Coins? ==
The page says: "Historically, this was used to mint coins, and that is also one of its uses in this game." I was under the impression that only gold, silver and copper can be used as currency? Can somebody clarify if billon coins can be used as currency? If yes or no, this should be clarified! --[[Special:Contributions/200.105.223.91|200.105.223.91]] 01:06, 6 October 2009 (UTC)
:sorry that was me--[[User:Overspeculated|Overspeculated]] 01:08, 6 October 2009 (UTC)
::They cannot be used as currency, only as collector's coins for other dwarves to purchase, unless you were to edit raw/objects/entity_default.txt and add [CURRENCY:BILLON:3] to the dwarf entry. --[[User:Quietust|Quietust]] 01:21, 6 October 2009 (UTC)
----
I was under the impression that it was called billion, not billon. What gives?--[[User:Zchris13|Zchris13]] 17:44, 19 November 2009 (UTC)
:Are you maybe thinking of bullion? [http://en.wikipedia.org/wiki/Billon Wikipedia seems to confirm "billon"]. --[[User:HebaruSan|HebaruSan]] 03:20, 20 November 2009 (UTC)

File:Oceanside-202-05.jpg

2009-11-18T20:01:02Z

HebaruSan: add caption

Oceanside sleeping quarters.

Template:Sg/caption

2009-11-18T19:54:45Z

HebaruSan: add caption for addition engine

{{choose|c={{{1|default}}}|default=No caption? Add one!
|1=Preparing a ballista.
|2=A well-placed door holds back disaster...
|3=Belal's 16x16 tileset
|4=Use utilities like 3Dwarf to render your fortresses
|5=Communal living: who needs walls?
|6=The burdens of being mayor are great, you barely get enough time for arena combat with a bunch of goblins every now and then. And then its back to conducting meetings.
|7=The dwarves hang around in the ale storage area to get some alone time with their alchohol.
|8=A baby crawling through the aftermath of a human siege at Ringfissures
|9=The dwarves have found a way to paint thier walls. It's a shame they ran out of paint when they were half-way done.
|10=With friends like these...
|11=Some fish are better left alone.
|12=No matter what your orders may be, your dwarves know the real matters of importance.
|13=Maybe Little Miss Muffet was a dwarf?
|14=All the comforts of home.
|15=Fires are very dangerous, and dwarves are not cautious. Ensure your dwarves stay away.
|16=GODS DANGIT MELBUL AND YOUR WATERFALLS!
|17=Ah... the great outdoors.
|18=You heard the man, Gimli. Your cot's in the barracks.
|19=A colossus makes short work of captured goblins in an arena.
|20=Is that a euphemism?
|21=Pain and hardship starts at a young age in dwarven culture.
|22=The vanity of dwarven engravers is not to be underestimated.
|23=Goblins have a very fickle relationship with their body parts. A skilled Axedwarf can quickly have them calling for a divorce.
|24=The King is dead. Long live the King!
|25=A mechanical binary addition engine.
}}

40d:Personality facet

2009-11-17T02:23:58Z

HebaruSan:

''(If looking for a "Profile" for a workshop, see [[Workshop]])''

----

A dwarf's '''personality traits''' can be seen in that dwarf's '''profile''', which can be viewed by selecting that dwarf on the map with {{k|v}}iew, {{k|p}}, {{k|z}}, {{k|Enter}} ), or from the {{k|u}}nit menu with {{k|v}}iew, {{k|Enter}}.

The profile shows (from top to bottom) a dwarf's:
:* recent good/bad [[thoughts]]
:* religious preferences & [[deity|deities]]
:* citizenship & group memberships
:* their [[preference]]s
:* their '''personality traits'''
- see each of those articles for a more complete discussion of them.

The personality traits of a dwarf are rated from 1 (lowest) to 100 (highest), but are categorized as below. A personality value between 40 and 60 is simply not noted in the profile.

----

:'''List of personality traits:'''
{| {{prettytable}}
|- style="background:#ddd"
! Token
! Value
! Description
! Gameplay effects
|- style="border-top: 3px solid #aaa"
| rowspan=6 | ACTIVITY_LEVEL
| style="width:4em" | 91 - 100
| colspan=2 | Is constantly active and energetic.
|-
| 76 - 90
| colspan=2 | Is very energetic and active.
|-
| 61 - 75
| colspan=2 | Is very active.
|-
| 25 - 39
| colspan=2 | Is relaxed.
|-
| 10 - 24
| colspan=2 | Lives life at a leisurely pace.
|-
| 0 - 9
| colspan=2 | Can't be bothered with frantic, fast-paced living.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | ADVENTUROUSNESS
| 91 - 100
| colspan=2 | Lives for risk and excitement.
|-
| 76 - 90
| colspan=2 | Is a risk-taker and a thrill-seeker.
|-
| 61 - 75
| colspan=2 | Loves a good thrill.
|-
| 25 - 39
| colspan=2 | Is not a risk-taker.
|-
| 10 - 24
| colspan=2 | Doesn't need thrills or risks in life.
|-
| 0 - 9
| colspan=2 | Is entirely adverse to risk and excitement.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | ALTRUISM
| 91 - 100
| colspan=2 | Is truly fulfilled by assisting those in need.
|-
| 76 - 90
| colspan=2 | Finds helping others very rewarding.
|-
| 61 - 75
| colspan=2 | Finds helping others rewarding.
|-
| 25 - 39
| colspan=1 | Does not go out of its/his/her way to help others.
| rowspan=3 valign=top | Helping a [[injury|wounded]] dwarf is a bad thought at these levels.
|-
| 10 - 24
| colspan=1 | Dislikes helping others.
|-
| 0 - 9
| colspan=1 | Views helping others as an imposition on own needs to get along with others.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | ANGER
| 91 - 100
| colspan=2 | Is in a constant state of internal rage.
|-
| 76 - 90
| colspan=2 | Is very quick to anger.
|-
| 61 - 75
| colspan=2 | Is quick to anger.
|-
| 25 - 39
| colspan=2 | Is slow to anger.
|-
| 10 - 24
| colspan=2 | Is very slow to anger.
|-
| 0 - 9
| colspan=2 | Never becomes angry.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | ANXIETY
| 91 - 100
| colspan=2 | Is a nervous wreck.
|-
| 76 - 90
| colspan=2 | Is always tense and jittery.
|-
| 61 - 75
| colspan=2 | Is often nervous.
|-
| 25 - 39
| colspan=2 | Has a calm demeanor.
|-
| 10 - 24
| colspan=2 | Has a very calm demeanor.
|-
| 0 - 9
| colspan=2 | Has an incredibly calm demeanor.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | ARTISTIC_INTEREST
| 91 - 100
| colspan=2 | Can easily become absorbed in art and the beauty of the natural world.
|-
| 76 - 90
| colspan=2 | Greatly appreciates art and natural beauty.
|-
| 61 - 75
| colspan=2 | Appreciates art and natural beauty.
|-
| 25 - 39
| colspan=2 | Does not have a great aesthetic sensitivity.
|-
| 10 - 24
| colspan=2 | Is not interested in art.
|-
| 0 - 9
| colspan=2 | Is completely uninterested in art.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | ASSERTIVENESS
| 91 - 100
| colspan=2 | Loves to take charge and direct activities.
|-
| 76 - 90
| colspan=2 | Is very assertive.
|-
| 61 - 75
| colspan=2 | Is assertive.
|-
| 25 - 39
| colspan=1 | Is unassertive.
| rowspan=3 | An unassertive dwarf (under 40) never gains experience in the [[Persuader]] skill.
|-
| 10 - 24
| colspan=1 | Prefers that others handle the leadership roles.
|-
| 0 - 9
| colspan=1 | Never speaks out or attempts to direct activities.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | CHEERFULNESS
| 91 - 100
| colspan=2 | Often feels filled with joy.
|-
| 76 - 90
| colspan=2 | Can be very happy and optimistic.
|-
| 61 - 75
| colspan=2 | Is often cheerful.
|-
| 25 - 39
| colspan=2 | Is rarely happy or enthusiastic.
|-
| 10 - 24
| colspan=2 | Is a pessimist.
|-
| 0 - 9
| colspan=2 | Is never optimistic or enthusiastic about anything.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | COOPERATION
| 91 - 100
| colspan=1 | Sacrifices its/his/her own needs to get along with others.
| rowspan=3 | A cooperative dwarf (over 60) never gains experience in the [[Intimidator]] skill.
|-
| 76 - 90
| colspan=1 | Dislikes confrontations.
|-
| 61 - 75
| colspan=1 | Is willing to compromise with others.
|-
| 25 - 39
| colspan=1 | Doesn't like to compromise with others.
| rowspan=3 | An uncooperative dwarf (under 40) never gains experience in the [[Pacifier]] skill.
|-
| 10 - 24
| colspan=1 | Would rather intimidate others than compromise with them.
|-
| 0 - 9
| colspan=1 | Would never deny its/his/her own needs just to compromise with somebody else.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | DEPRESSION
| 91 - 100
| colspan=2 | Is frequently depressed.
|-
| 76 - 90
| colspan=2 | Is often sad and dejected.
|-
| 61 - 75
| colspan=2 | Often feels discouraged.
|-
| 25 - 39
| colspan=2 | Rarely feels discouraged.
|-
| 10 - 24
| colspan=2 | Almost never feels discouraged.
|-
| 0 - 9
| colspan=2 | Never feels discouraged.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | DUTIFULNESS
| 91 - 100
| colspan=2 | Has a profound sense of duty and obligation.
|-
| 76 - 90
| colspan=2 | Has a strong sense of duty.
|-
| 61 - 75
| colspan=2 | Has a sense of duty.
|-
| 25 - 39
| colspan=2 | Finds rules confining.
|-
| 10 - 24
| colspan=2 | Dislikes contracts and regulations.
|-
| 0 - 9
| colspan=2 | Hates rules, contracts and other confining elements in its/his/her life.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | EXCITEMENT_SEEKING
| 91 - 100
| colspan=1 | Is highly adventurous and loves fresh experiences.
| rowspan=3 | Beings with this trait are more likely to join you in adventure mode.
|-
| 76 - 90
| colspan=1 | Is eager for new experiences.
|-
| 61 - 75
| colspan=1 | Likes to try new things.
|-
| 25 - 39
| colspan=2 | Prefers familiar routines.
|-
| 10 - 24
| colspan=2 | Is uncomfortable with change.
|-
| 0 - 9
| colspan=2 | Is resistant to change.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | FRIENDLINESS
| 91 - 100
| colspan=2 | Truly treasures the company of others.
|-
| 76 - 90
| colspan=2 | Enjoys being in crowds.
|-
| 61 - 75
| colspan=2 | Enjoys the company of others.
|-
| 25 - 39
| colspan=2 | Tends to avoid crowds.
|-
| 10 - 24
| colspan=2 | Prefers to be alone.
|-
| 0 - 9
| colspan=2 | Considers spending time alone much more important than associating with others.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | IMAGINATION
| 91 - 100
| colspan=2 | Is bored by reality and has a wonderful imagination.
|-
| 76 - 90
| colspan=2 | Is incredibly creative.
|-
| 61 - 75
| colspan=2 | Has a fertile imagination.
|-
| 25 - 39
| colspan=2 | Isn't given to flights of fancy.
|-
| 10 - 24
| colspan=2 | Is grounded in reality.
|-
| 0 - 9
| colspan=2 | Is interested only in facts and the real world.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | IMMODERATION
| 91 - 100
| colspan=2 | Is ruled by irresistible cravings and urges.
|-
| 76 - 90
| colspan=2 | Feels strong urges and seeks short-term rewards.
|-
| 61 - 75
| colspan=2 | Occassionally overindulges.
|-
| 25 - 39
| colspan=2 | Doesn't often experience strong cravings or urges.
|-
| 10 - 24
| colspan=2 | Only rarely feels strong cravings or urges.
|-
| 0 - 9
| colspan=2 | Never feels tempted to overindulge in anything.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | INTELLECTUAL_CURIOSITY
| 91 - 100
| colspan=2 | Is entranced by riddles and puzzles and loves to debate issues and ideas.
|-
| 76 - 90
| colspan=2 | Loves new and fresh ideas.
|-
| 61 - 75
| colspan=2 | Is open-minded to new ideas.
|-
| 25 - 39
| colspan=2 | Dislikes intellectual discussions.
|-
| 10 - 24
| colspan=2 | Regards intellectual exercises as a waste of energy.
|-
| 0 - 9
| colspan=2 | Is completely uninterested in ideas and debates over intellectual issues.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | MODESTY
| 91 - 100
| colspan=2 | Would never claim to be better than somebody else.
|-
| 76 - 90
| colspan=2 | Finds immodesty distasteful.
|-
| 61 - 75
| colspan=2 | Is modest.
|-
| 25 - 39
| colspan=2 | Is immodest.
|-
| 10 - 24
| colspan=2 | Is very willing to compare itself/himself/herself favorably with others.
|-
| 0 - 9
| colspan=2 | Would never shy away from an opportunity to say it/he/she is better than somebody else.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | LIBERALISM
| 91 - 100
| colspan=2 | Revels in chaos and disorder.
|-
| 76 - 90
| colspan=2 | Loves to defy convention.
|-
| 61 - 75
| colspan=2 | Is put off by authority and tradition.
|-
| 25 - 39
| colspan=2 | Admires tradition.
|-
| 10 - 24
| colspan=2 | Prefers stability and security to ambiguity and disorder.
|-
| 0 - 9
| colspan=2 | Is an ardent believer in convention and traditional society.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | ORDERLINESS
| 91 - 100
| colspan=2 | Loves to make lists and keep schedules.
|-
| 76 - 90
| colspan=2 | Tries to live a well-organized life.
|-
| 61 - 75
| colspan=2 | Is organized.
|-
| 25 - 39
| colspan=2 | Is disorganized.
|-
| 10 - 24
| colspan=2 | Is very disorganized.
|-
| 0 - 9
| colspan=2 | Is completely disorganized.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | SELF_CONSCIOUSNESS
| 91 - 100
| colspan=1 | Is socially crippled by thoughts that everyone is watching and judging it/him/her.
| rowspan=2 valign=top | A very self-conscious dwarf (over 75) never gains experience in the [[Comedian]] skill.
|-
| 76 - 90
| colspan=1 | Is concerned about rejection and ridicule.
|-
| 61 - 75
| colspan=2 | Is self-conscious.
|-
| 25 - 39
| colspan=2 | Is comfortable in social situations.
|-
| 10 - 24
| colspan=2 | Is very comfortable in social situations.
|-
| 0 - 9
| colspan=2 | Is absolutely unfazed by the opinions of others.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | SELF_DISCIPLINE
| 91 - 100
| colspan=2 | Will persist in the face of any difficulty until the task is complete.
|-
| 76 - 90
| colspan=2 | Possesses great willpower.
|-
| 61 - 75
| colspan=2 | Is self-disciplined.
|-
| 25 - 39
| colspan=2 | Is occasionally given to procrastination.
|-
| 10 - 24
| colspan=2 | Has very little self-discipline.
|-
| 0 - 9
| colspan=2 | Rarely completes tasks and is often overcome by distractions.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | STRAIGHTFORWARDNESS
| 91 - 100
| colspan=1 | Is incredibly frank and candid in dealings with others.
| rowspan=3 | A straightforward dwarf (over 60) never gains experience in the [[Flatterer]] skill.
|-
| 76 - 90
| colspan=1 | Is very straightforward with others.
|-
| 61 - 75
| colspan=1 | Is candid and sincere in dealings with others.
|-
| 25 - 39
| colspan=1 | Is guarded in [[relationships]] with others.
| rowspan=3 | Guarded dwarves (under 40) never gain experience in the [[Consoler]] skill, and are the only ones to gain experience in the [[Liar]] skill.
|-
| 10 - 24
| colspan=1 | Is not straightforward when dealing with others.
|-
| 0 - 9
| colspan=1 | Believes that some deception is necessary in relationships with others.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | GREGARIOUSNESS
| 91 - 100
| colspan=2 | Genuinely likes others and openly expresses positive feelings toward them.
|-
| 76 - 90
| colspan=2 | Makes friends quickly.
|-
| 61 - 75
| colspan=2 | Is very friendly.
|-
| 25 - 39
| colspan=1 | Is somewhat reserved.
| rowspan=3 | A reserved dwarf (under 40) never gains experience in the [[Conversationalist]] skill.
|-
| 10 - 24
| colspan=1 | Is very distant and reserved.
|-
| 0 - 9
| colspan=1 | Does not actively seek friendships and is incredibly distant and reserved.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | TRUST
| 91 - 100
| colspan=2 | Is naturally trustful of everybody.
|-
| 76 - 90
| colspan=2 | Is very trusting.
|-
| 61 - 75
| colspan=2 | Is trusting.
|-
| 25 - 39
| colspan=2 | Is slow to trust others.
|-
| 10 - 24
| colspan=2 | Does not trust others.
|-
| 0 - 9
| colspan=2 | Sees others as selfish and conniving.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | VULNERABILITY
| 91 - 100
| colspan=2 | Becomes completely helpless in stressful situations.
|-
| 76 - 90
| colspan=2 | Cracks easily under pressure.
|-
| 61 - 75
| colspan=2 | Doesn't handle stress well.
|-
| 25 - 39
| colspan=2 | Can handle stress.
|-
| 10 - 24
| colspan=2 | Is confident under pressure.
|-
| 0 - 9
| colspan=2 | Is impervious to the effects of stress.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | ACHIEVEMENT_STRIVING
| 91 - 100
| colspan=2 | Constantly strives for perfection.
|-
| 76 - 90
| colspan=2 | Thinks it is incredibly important to strive for excellence.
|-
| 61 - 75
| colspan=2 | Strives for excellence.
|-
| 25 - 39
| colspan=2 | Doesn't go out of its/his/her way to do more work than necessary.
|-
| 10 - 24
| colspan=2 | Very rarely does more work than necessary.
|-
| 0 - 9
| colspan=2 | Does the bare minimum necessary to accomplish the task at hand.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | EMOTIONALITY
| 91 - 100
| colspan=2 | Has a profound understanding of its/his/her own emotions.
|-
| 76 - 90
| colspan=2 | Has a great awareness of its/his/her own emotions.
|-
| 61 - 75
| colspan=2 | Has a good awareness of its/his/her own emotions.
|-
| 25 - 39
| colspan=2 | Tends not to openly express emotions.
|-
| 10 - 24
| colspan=2 | Is mostly unaware of its/his/her own emotions and rarely expresses them.
|-
| 0 - 9
| colspan=2 | Does not display its/his/her own emotions and has no awareness of them.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | SYMPATHY
| 91 - 100
| colspan=2 | Is incredibly compassionate and feels the pain of others.
|-
| 76 - 90
| colspan=2 | Is easily moved to pity.
|-
| 61 - 75
| colspan=2 | Is compassionate.
|-
| 25 - 39
| colspan=2 | Is not easily moved to pity.
|-
| 10 - 24
| colspan=2 | Is not affected by the suffering of others.
|-
| 0 - 9
| colspan=2 | Would never let an objective judgement be tempered by mercy or pity.
|- style="border-top: 3px solid #aaa"
| rowspan=6 | SELF_EFFICACY
| 91 - 100
| colspan=2 | is incredibly confident
|-
| 76 - 90
| colspan=2 | is very confident
|-
| 61 - 75
| colspan=2 | is confident
|-
| 25 - 39
| colspan=2 | lacks confidence
|-
| 10 - 24
| colspan=2 | does not feel effective in life
|-
| 0 - 9
| colspan=2 | always feels as if it/he/she is not in control of its/his/her life
|- style="border-top: 3px solid #aaa"
| rowspan=6 | CAUTIOUSNESS
| 91 - 100
| colspan=2 | thinks through every alternatives and their consequences before acting
|-
| 76 - 90
| colspan=2 | is extremely cautious
|-
| 61 - 75
| colspan=2 | takes time when making decisions
|-
| 25 - 39
| colspan=2 | often does the first thing that comes to mind
|-
| 10 - 24
| colspan=2 | acts impulsively
|-
| 0 - 9
| colspan=2 | always acts without considering alternatives or thinking through possibilities
|}

Note: Races without the tags for a certain field have a full range of values, presumably with an average value of 50.

Personality traits determine the psychological profile of each race. Currently, the file format for personality traits is:

:[PERSONALITY:name:min:avg:max]

:: "name" is the personality trait
:: "min" is the minimum value for an individual
:: "avg" is the average for a race
:: "max" is the maximum value for an individual.

[[Category:Hacking]]

40d Talk:Liaison

2009-11-15T18:42:37Z

HebaruSan: /* Late arrivals */ new section

Any idea how to keep them from staying till they go insane. Every winter my dwarves live in fear of the bruce lee of liaisons going into a martial trance.

At first I thought they'd stay if they didn't get to talk with my broker but having a meeting doesn't help get them out. --[[User:Lucid|Lucid]] 17:44, 1 November 2007 (EDT)

:Make sure you have your broker free long enough to make your demands and to views theirs, it take about 4 meetings between your broker and the liaison. At least that is how I get him to leave --[[User:Shades|Shades]] 18:08, 1 November 2007 (EDT)

so THAT'S how you do it, good thing I turned off my expo leader from hunting, the damned liason kept on scaring off the deer [the leader, and broker] was chasing :\

== Broker, not Leader? ==

So it's the broker, not the mayor, that meets with these guys? That changes some things. (I'm trying to keep the Liasons outside of my fortess so they don't know where the traps are, if they ever siege.)

No, its the leader/mayor. --[[User:Koltom|Koltom]] 11:33, 20 February 2008 (EST)

:i have my leader and broker separate(not by choice) in my current fort, and noticed that while the dwarf liaison meets with the leader, the human rep most definately meets with the broker, not the leader. --[[User:Chariot|Chariot]] 06:57, 9 March 2008 (EDT)

::Ditto, my broker keeps meeting with the Liasons (all of them, i think, certainly the human one) despite not having been mayor for something like 5 years (military dwarves always seem to get elected mayor...). In fact, I just annoyed a human liason because my broker (not mayor) entered a strange mood just as the liason entered my fortress (thus promptly leaving).
::Now, Diplomats meet with the highest ranking leading noble you have (mayor/baron+/etc...), and I don't know why Diplomat redirects to Liason as humans and elves occasionally send a diplomat to make demands or merely comment 'this is a nice place you've carved out for yourself'.
::--[[User:Squirrelloid|Squirrelloid]] 06:54, 17 April 2008 (EDT)

Ok, I changed this so that it correctly says the human liason meets with your broker. I left the dwarven liason as Mayor but I'm not certain that's true - my one still existent game which is suitably set up to check this otherwise is now the mountainhome, so I'm unable to verify at present. --[[User:Squirrelloid|Squirrelloid]] 21:07, 17 April 2008 (EDT)

::Anecdotal evidence of dwarven liason using Mayor/Exp Leader - I got an initial set of dwarves where they made someone expedition leader who didn't have the broker skills, so exp leader and broker were different dwarves. Dwarven Liason met with Exp Leader. --[[User:Squirrelloid|Squirrelloid]] 15:55, 18 April 2008 (EDT)

Confirming it's the expedition leader, i currently only have on dwarf (hermit challenge) and he's the expedition leader, and the dwarven liason meets with him. (Sorta lame really, let him live, sheesh)

== really set off traps? ==
I have both liaisons walk through a maze of traps every time they visit, never got hurt. Maybe a 38a/b/c bug? What kind of traps were they triggering?--[[User:Koltom|Koltom]] 23:56, 27 February 2008 (EST)

:I'm running DF 38a and every year when the caravans arrive I get a new human corpse to loot. My liasons ''never'' make it past my traps (weapon[disc] and stonefall). I wish they would, I'd like to adjust what they bring. [[User:Ripheus|Ripheus]] 21:00, 3 March 2008 (EST)
::well known bug for 38a, it was fixed in 38b -[[User:Chariot|Chariot]] 21:54, 3 March 2008 (EST)

Mine just set off a Trap too. Died. Running verson 40c for mac. --[[User:OmegaX|OmegaX]] 09:19, 20 September 2008 (EDT)

== Can't assign new leader; wiki article is incorrect ==

Leaders are elected and can't be manually chosen. --[[User:GreyMario|GreyMario]] 23:34, 8 March 2008 (EST)

I may be remembering wrong, but I recall my liasons wanting to meet my Broker, who is manually chosen. [[User:Ripheus|Ripheus]] 01:52, 9 March 2008 (EST)

== Diplomat ==

I have an elven diplomat telling my duchess not to cut down more than 55 trees (and calling her short.. a member of Elves for the Ethical Treatment of Trees?). Is this kind of diplomat separate from the trade liaison? The page [[Diplomat]] redirects here.. [[User:Anydwarf|Anydwarf]] 13:18, 28 March 2008 (EDT)

:Yes and no. We should maybe move this page to "diplomat" as both the human and dwarven one (and the elven one? never had one of those although im trying hard *grin*) are called diplomat in the unit list. On the other hand the elves never send a trade diplomat(?) so, yes he is somewhat different, but should be included then... --[[User:Koltom|Koltom]] 22:37, 28 March 2008 (EDT)

== weird trigger for liaison screens ==
it seems once the meeting has started the usual delay between the screens can be avoided by marking tiles for digging with the mouse - this will cause the screens to pop up during marking (just be careful with pressing space bar) --[[User:Koltom|Koltom]] 14:29, 29 March 2008 (EDT)

== odd behaviour out of season/character ==
My siege engineer has just spend a while wandering around my fortress with the job "Attend Meeting" even though a) he is not the broker or mayor, b) there are no merchants or liasons on the map. He would go to one place and just stand there doing nothing then walk to another place and repeat. This went on for a while then he just went back to normal. There were other jobs he could have been doing at the time. Most odd. Is this a bug should I report it? [[User:Yvain|Yvain]] 19:19, 29 March 2008 (EDT)
:To clear up a point of confusion the job "Conduct Meeting" is the job assigned to the Mayor,Broker, or Baron/Count. After dwarven economy is running a dwarf might get the job "Attend Meeting". That dwarf seeks a meeting with the Mayor. If the Mayor is busy he will continue to follow the Mayor around until he is free. The solution I found is to switch off the Mayor's labors so he's free to conduct the meeting. The meeting is usually quick and then you'll get the other dwarf working again.--[[User:Angus|Angus]] 20:52, 29 March 2008 (EDT)
::Some claim that this is a bug. If the person seeking the meeting gets his meeting, but then the Leader gets distracted, the "Attending Meeting" status will never go away. The [[Meeting|solution suggested]] is to Activate them into the military then deactivate them. [[User:3lB33|3lB33]] 00:55, 4 September 2009 (UTC)

== verified some embarrassment factors ==
From dwarfort.exe
(Name) was embarrassed to have to conduct an official meeting in a dining room.
(Name) was very embarrassed to have to conduct an official meeting in a bedroom.
[[User:Yvain|Yvain]] 19:58, 29 March 2008 (EDT)

: I would be happier if someone could verify that it is actually _used_ in game, but, well. You see, my palace office never triggered any thought. --[[User:Koltom|Koltom]] 21:13, 29 March 2008 (EDT)

::Try giving them a dining room and no office, koltom. [[User:VengefulDonut|VengefulDonut]] 14:26, 30 March 2008 (EDT)

:::I got these unhappy thoughts from meetings conducted in public dining halls that were also designated as meeting halls. (I do not know whether they also happen from nobles' personal dining rooms designated from private tables.) They seem to be very minor unhappy thoughts, so I'm not going out of my way to avoid such designations to keep my idlers from going to hang out by the wagon in the fortresses' early stages. --[[User:Brent Not Broken|Brent Not Broken]] 12:31, 17 April 2008 (EDT)

== Liaisons, zoo material? ==

I want to know whether or not to trap the liaisons before they leave and have them in cages. Should I do this or not?--[[User:CrazyMcfobo|CrazyMcfobo]] 19:17, 12 April 2008 (EDT)

:hm..
: *You can't trap them (unless you mean locking them in a room)
: *You can't assign them to cages
: If u don't let them leave they will go crazy and your requests for trade items will most likely be ignored
: why do you want to trap them? (okay, they are annoying, but also useful) --[[User:Koltom|Koltom]] 08:41, 17 April 2008 (EDT)

==Human Diplomat==
Added information about the human diplomat, whom i've seen meeting with my Baron/Count/Duke often enough (4 different games, multiple times in each). They don't seem to do much at present - though I haven't tried to incur a human siege of my fortress to see if they sue for peace if you beat them. I imagine they could theoretically make demands like the elven diplomat does, except they aren't picky about things like cutting down trees. --[[User:Squirrelloid|Squirrelloid]] 21:07, 17 April 2008 (EDT)

== Meeting With Elves ==

What happens if you choose different option instead of saying yes to whatever they say? The number of trees keep going lower...57....43...37...well they aren't the exact numbers but close to them. I might want to try to fight them once. I've got some ore to melt and I need a good amount of charcoal... They appear every year after cutting too much trees?--[[User:Seaneat|Seaneat]] 23:36, 9 July 2008 (EDT)

New meeting with elves craziness - i've seriously cut down like 10 cacti total, and that was over 5 years ago. Wood imports have been more than sufficient since then. The elf diplomat shows up for the first time and tells me I've been disrespecting the trees. Does the diplomat always say the same thing? Because he's making no sense whatsoever. In addition to their being absolutely no trees on my map (Yay Saguaros?), I haven't even chopped any in ages. I've bought 20x the amount I ever chopped from the elven caravans. How have I been disrespecting the 'trees'? --[[User:Squirrelloid|Squirrelloid]] 02:28, 9 December 2008 (EST)

I have a fortress where I didn't cut a single tree (there is none) and the elf was happy with me... So no, not always the same, but it seems that the disrespect starts at the very first log. [[User:Matakuka|Matakuka]] 12:37, 29 June 2009 (UTC)

== liaison - dead and gone? (death of a salesman) ==
When in the first summer the dwarven caravan arrived with the outpost liaison at my latest fortress, the liason made it savely past the traps but seems to have died just in front of the depot - no blood to be seen, no message in the announcement, just as he had died a natural death.
Strange enough, but after I provided him a coffin, in the next year the dwarves came without another liaison. So I disposed the treacherous coffin and bones in my crush-o-mat. But that didn't have any effect either: There didn't come any liaison anymore.
In the first place I wonder why he died, and also why he isn't succeeded?!--[[User:Doub|Doub]]

== Left Unhappily? ==

I just got a message
"Diplomacy Stymied. A diplomat has left unhappy."
The last part of the meeting never occured, and my mayor was unable to meet him, due to seige. Was the dwarven diplomat. --[[User:OmegaX|OmegaX]] 17:59, 16 September 2008 (EDT)

== Person to meet set when liaison arrives? ==

When the human liaison arrived this year, I had "Trader Joe" Stukosshed as my Broker. Shortly after, the goblins sieged and Joe got hit by a stray arrow while evacuating. His arm is mangled, so he's resting. I assigned a new broker, but it looks like the Human liaison is holding vigil beside Joe's bed, waiting for him to wake up to run the meeting. -[[User:Fuzzy|Fuzzy]] 16:32, 19 September 2008 (EDT)

==Liaison dead??==

The human guild representative was walking around my fort; he seemed all fine, did not set off any traps. Suddenly, a few (real-life) minutes later, I see a human corpse in my refuse stockpile. He also didn't even have a meeting (note: he died about 2 months after the caravan left). Should I expect a human siege?

: Probably, yes. [[User:Timst|Timst]] 13:12, 30 October 2008 (EDT)

== 404 meeting not found ==

Issue resolved. The problem was that my mayor wanted to update stockpile records instead of take the damn meeting. --[[User:GreyMario|GreyMaria]] 23:50, 16 January 2009 (EST)

==No Liaison?==
First year, rather rough terrain, dwarf caravan arrived just fine though but... no liaison? At all? I kind of wanted to request bauxite... I guess I'm glad I brought some with me... Has anyone else had this happen? What's going on? --[[User:Squirrelloid|Squirrelloid]] 14:15, 21 November 2008 (EST)

:I have a similar problem in my current game, for the simple reason that I have embarked as part of a tiny civilisation - one which apparently has no king. No king means no liaison. This happened because of my parameters, but I'm sure that it can happen coincidentally in the unaltered game as well. [[User:Aosher|Aosher]] 12:47, 19 March 2009 (UTC)

::I had a similar incident a while back, where the liaison never showed up, not even in the first year. I didn't think to check whether or not my civ had a king/queen, but I was on a terrifying glacier so I had just assumed he had froze to death or something before reaching my site.--[[User:Mjo625|Mjo625]] 13:46, 19 March 2009 (UTC)

::Hmm... I have the same thing happening to me. I checked my civilization on the civilization menu and it just says: "Ruler/King" for the head of the civilization. Doesn't this mean I have a king? If not, how do you know if you have a king?--[[User:Jpwrunyan|Jpwrunyan]] 09:00, 22 April 2009 (UTC)

==Liaison dead?, help==
My liaison died to a goblin ambush a few years back on his way out.. midwinter. Do I never get a new one or the chance to request stuff again?--[[User:Cultiststeve|cultiststeve]] 11:00, 11 January 2009 (EST)

==Insane Liason==
How long does it take to drive a dwarven liason insane from being ingored? They guy's getting on my nerves, lurking outside the door and not letting poor Elfcrusher leave.

:The timer only seems to start if he's met/seen the dwarf he wants to talk to. I've had a Liaison wander around for 3 years because he couldn't get anywhere near my mayor/broker - enough time he should have gone insane otherwise. --[[User:Squirrelloid|Squirrelloid]] 11:57, 31 January 2009 (EST)

::Then I'm lucky the wolves decided to vist. Cheers anyway. --[[User:Simmura McCrea|Simmura McCrea]] 14:22, 31 January 2009 (EST)

== Elven diplomat, ...what? ==

So, today an elven diplomat came to me and said I had carved a nice place out for myself. Then he left, which left me quite confused. Earlier an elven caravan arrived but was ambushed and brutally killed, is that why the diplomat came? If so, why didn't he say anything? [[User:Tardface|Tardface]] 12:42, 19 March 2009 (UTC)

:Your baroness / countess / duchess will get liaisons from friendly civilisations occasionally. They often just say that you have carved out a lovely place, then leave. Did you get a new noble recently? [[User:Aosher|Aosher]] 12:46, 19 March 2009 (UTC)

:That's sound like what the human diplomat tends to say. Are you sure the elf was from an elf civilization, or was it an elf working for the humans? --[[User:LegacyCWAL|LegacyCWAL]] 20:00, 19 March 2009 (UTC)

::I got an elven diplo who just moped about too many trees cut and how he didn't expect any better from us. No quota. Is that new? Is that bad? Or kinda a prestage? --[[User:Höhlenschreck|Höhlenschreck]] 21:52, 17 June 2009 (UTC)

== Dwarven Liaison becomes Advisor? ==

In my last fortress (which got a standard King), the [[Advisor]] turned out to be the outpost liaison for my civilization. Coincidence, or does this always happen? --[[User:Quietust|Quietust]] 13:14, 3 September 2009 (UTC)
*I should note that my current fortress also had my liaison arrive as the Advisor. --[[User:Quietust|Quietust]] 21:21, 26 September 2009 (UTC)

== humans observing traps ==

----
The human page says that any traps a human noble observes will not trigger for sieging humans. That should probably be mentioned here, plus which of the human liasons (all?) have this ability, plus tips to prevent trap observation from happening. It would also be nice to see whether or not deconstructing a trap and then building an identical one in the same place is enough to counter it (I suspect it is). [[User:Arrkhal|Arrkhal]] 22:01, 3 September 2009 (UTC)

== Cross-racial liasons ==

(No, not *those* kind.) I just had my first dwarf caravan arrive in the fall of my first year, and they seem to have brought an elven outpost liason. Who's missing his left arm below the elbow and keeps passing out on the way to my fort. I know my parent civilization has seen better days (they only have one Mountainhome left after a series of wars), but you're telling me there was nobody better to send than a one-armed treehugger?

So apparently civs can provide liasons from assimilated members of other races. And the game doesn't check for injuries until it puts them in-game (like a lot of guards in adventure mode).
:My current fort's Human neighbors have an Elf Guild Representative, and my own Dwarven civilization has an Elf Diplomat (though a Dwarf Liaison), so it doesn't seem to be all that uncommon. Hell, my civilization even has a Goblin "High Priest/Goblin Drunk", so it would appear that the sky's the limit. --[[User:Quietust|Quietust]] 18:09, 14 November 2009 (UTC)

== Late arrivals ==

I let a winter siege continue through late spring, which kept the elven caravan away. Now in early summer, I got these two events in a row:

[[File:Blockedbridge-diplomats.png]]

Before this, I assumed that the diplomat always arrived with the caravan from that same civilization. Has anybody seen a diplomat postpone their trip like this?

--[[User:HebaruSan|HebaruSan]] 18:42, 15 November 2009 (UTC)

File:Blockedbridge-diplomats.png

2009-11-15T18:33:55Z

HebaruSan: Elven diplomat arriving shortly before human diplomat

Elven diplomat arriving shortly before human diplomat

Dwarf Fortress Wiki talk:Community Portal

2009-11-14T02:30:22Z

HebaruSan: /* Proposal: Category:Best of DF Wiki */ new section

Use this discussion page to talk about any issues or ideas you have about the direction of this wiki. The community portal is a hub for directing our conciousness. Read the rules carefully, take them to heart, post here if you have any questions or you think the rules can be improved.
{{Archive|
#[[Dwarf_Fortress_Wiki_talk:Community_Portal/archive1|Archive 1]]
}}
== Thoughts on {{rule|i}} - Diagrams ==

Isn't [[Template:RT]] really more complexity than we need? How about this?

<pre style="font:bold 20px/1 'Courier New';color:#ccc;background:black;width:auto;padding:0;float:left">
╔═══╗
║+++║
║+++┼
║+++║
╚═══╝
</pre>{{-}}

Save the complex templates for when you actually need color

You can even drop the complexity further for a nice typewriter character set
<pre style="font:bold 20px/1 'Courier New';color:#ccc;background:black;width:auto;padding:0;float:left">
#####
#...#
#...+
#...#
#####
</pre>{{-}}

(I picked this particular size because it makes ░░░▒▒▒▓▓▓ look right in them, which makes it seem that it's the size the font is designed for. I picked this _font_ because it provides all of the CP437 characters. The actual style tag you see above could be moved to a template so it would look like <code><pre <nowiki>{{TD}}</nowiki>></code>)

[[User:Random832|Random832]] 20:28, 30 December 2008 (EST)

== Mod content in regular articles ==

"All mod content, it has been stated, should not appear in the regular articles." --[[User:Zchris13]], at [[Talk:Sand]] 
If I recall correctly, one guy stated that yesterday. Personally, I find it rather counter-DF: 
"In Dwarf Fortress, modding almost ''is'' vanilla." --[[User:Savok]], at the [http://www.bay12games.com/forum/index.php forums] 
Opinions? Beliefs? Comments? Thoughts? Please, answer this, The Community! --[[User:Savok|Savok]] 11:24, 8 March 2009 (EDT)

:I'm probably the one who you're thinking of who stated it ;)
:#I don't think that modding is ''ever'' vanilla, no matter what the game, how mod-friendly the game is, or how many mods exist. Saying that it's incredibly common does not change the definition of the term "unmodded".
:#I think that modding information would be better served by putting it in one place. It's easier to figure out modding and/or find the information you need if it's all on one page (or a small number of pages). And if the information is there, why would you ''also'' put it on ''every single other article in the wiki''?
:#Whenever the ways something can be modded changes, every single article about that something would have to be changed. If a new way to mod metals, for example, was added, then every single metal article would have to be changed to reflect this.
:#tl;dr version: I think it would be horrifically redundant even by typical wiki standards and would never be maintained anyways (seriously, there are still pages that haven't been updated since the 2D version). And that's even before you think about whether it ''should'' be done at all.
:--[[User:LegacyCWAL|LegacyCWAL]] 13:10, 8 March 2009 (EDT)

::Sorry, couldn't find it in all of yesterday's edits.
::#Yeah, I shouldn't go changing my definitions of words. What I mean is "modding is normal."
::#I agree partially, but, since light modding is normal and mainstream, it should go in normal and mainstream articles.
::#No, every article that mentioned metal-modding. And I don't think that there are too many non-modding articles that do.
::#TL/DR: I think that a little mentioning of modding (for example, stating in [[Sand]] that you can mod any soil into sand (although that's a bit obvious)) is fine, although I fully agree that all possible topic-related modding should not be mentioned.
::--[[User:Savok|Savok]] 18:45, 8 March 2009 (EDT)

:::I think I can live with that ;). Also, I appreciate the reformatting: I couldn't find the instructions on how to make such a list, though odds are it's right in front of me =( --[[User:LegacyCWAL|LegacyCWAL]] 19:41, 8 March 2009 (EDT)

== Heading gripe ==

I'd like to add to H that one shouldn't use heading sections of one = because it results in bad html coding and a title the size of the page name. It's also general practice on [http://en.wikipedia.org/wiki/Help:Section#Creation_and_numbering_of_sections wikipedia]. Anyways, I thought I'd post something here before I go ahead and change it so I can at least pretend to have discussed it before hand. --[[User:Mikaka|Mikaka]] 05:39, 4 June 2009 (UTC)

== Modding content ==
Is this, [[New_Plants]], really how we do it? Frankly, i found it a bit confusing at first. At least it should get a better header. --[[User:Confused|Confused]] 00:37, 8 August 2009 (UTC)

== JavaScript seems disabled ==

The collapsible box doesn't seems collapsible anymore. I don't see the [show]/[hide] anymore either, since the wiki broke. Am I the only one with this trouble ? --[[User:Karl|Karl]] 01:02, 22 August 2009 (UTC)
:Apparently it's fixed now, at least for me. I have found that my browser cache can screw with these things on other wikis so no reason why it wouldn't happen here. Javascript becomes disabled on client web browsers far more often than it does on web hosts/sites which previously allowed it. (Possibly belatedly I know.)[[User:GarrieIrons|Gar]][[User Talk:GarrieIrons|rie]] 03:43, 10 September 2009 (UTC)

== Do we detail pointlessly? ==

As everyone knows, the wiki spoils everything about Dwarf Fortress. We have a spoiler-warning system, but it's quite disused. I think one guy said that it's pointless, because we need to put it on every page, because every page is a spoiler. We have a tendency to detail everything, much of which isn't helpful to newbies but ruins a little the delight a newbie can take in DF that no longer exists for us veterans.

For example, to quote the page [[woodcutter]], "Woodcutters are working outdoors where they are in constant danger of being [[ambush]]ed by invaders or attacked by wild animals (unless, of course, you are the proud owner of an [[Tower-cap#Underground_tree_farm|underground tree farm]]), but they are also one of the few civilian professions which carry [[weapons]] with them. Thus, it can be helpful to teach them how to use their axes to defend themselves (and others) properly by making them spend a few months as [[axedwarf]]s in your [[military]]."

Here, all that really should be noted is that woodcutting skill does not help in combat. Yes, another problem with the wiki as it is is that we often assume that newbies know a lot of stuff they don't, making even DFwiki have a steep learning curve - a bit ironic. Regardless, pointless detail such as in the above article not only does not help but hurts, making the wiki dry and boring.

I propose that we write into our little [[Dwarf Fortress Wiki:Community Portal|constitution]] a guideline to avoid such detail in addition to removing large amounts from the wiki, fixing the pages. Of course, this is a major undertaking, not to just be done. What do y'all think? Agree? Argue? Please do comment. --[[User:Savok|Savok]] 02:36, 10 September 2009 (UTC)

:Wikis attract wikignomes who like to tinker and add information to articles until they are "complete". Attempting to define how much information can be added before an article is "over-complete" is pretty difficult.
:Is there a policy that this wiki must not spoil the game for new players?
:There are a lot of different reasons people read this wiki - it isn't just a hosted version of the wonderful instruction manual that is included with the game. Would [[computing]] be possible without collaboration (between players), which is nothing but spoiling?
:The answers would lie in either seperate articles, or some kind of template which hides information regarded as a spoiler.
:There is this option:
{| class="collapsible collapsed" style="width: 100%; background-color: lightblue;"
!colspan="1"| Basic intrduction
|-
|Woodcutters cut down trees.
|-
|}
{| class="collapsible collapsed" style="width: 100%; background-color: lightblue;"
!colspan="1"| Minor spoiler
|-
| They are one of a few civilian trades which involves carrying a weapon. In hostile areas you might want to consider training woodcutters as Axedwarves.
|-
{| class="collapsible" style="width: 100%; background-color: lightblue;"
!colspan="1"| Major spoiler
|-
|Another option on some maps is establishing an underground tree farm.
|-
|}

:However that requires some knowledge of either wikimarkup or html - tbh I just cookbooked it and it took me a fair bit of messing around before I got it right the first time.
:Another option is, linked articles, where you go from [[Woodcutter (base)]] to [[Woodcutter (minor spoiler)]] to [[Woodcutter (major spoiler)]] - it would be easy enough to include (base) in (minor spoiler) and (minor spoiler) in (major spoiler).

:I think "enough" readers ''want'' the major spoilers that taking them out would "degrade" this wiki.
:[[User:GarrieIrons|Gar]][[User Talk:GarrieIrons|rie]] 03:36, 10 September 2009 (UTC)

::I just re-read [[woodcutter]] in full. IMO the article builds nicely from the basic "how to cut trees" to more advanced gameplay strategy, such as "enable woodcutting on every outdoor worker so they all carry weapons". Personally I don't see that as being a good value strategy, for the work involved in equipping that many dwarves with axes you could have a fairly useful (specialised) millitary - but it isn't the first thing a spoiler-adverse reader stumbles over. If it was the first thing in the article it would be a far greater problem.[[User:GarrieIrons|Gar]][[User Talk:GarrieIrons|rie]] 03:41, 10 September 2009 (UTC)

:I'm going to agree with Garrie on this. Counting me, there's at least one person who would not have stuck with DF if he hadn't had access to a thorough DF reference library such as this. When a new player comes to this wiki, odds are they're looking to have ''something'' spoiled.
:One vote for 'Not Too Spoiled' --[[User:Njero|Njero]] 03:45, 10 September 2009 (UTC)

:Sorry to have apparently been totally unclear... I don't want to take spoilers out! I think that there are a lot of things, like the example from woodcutter, that a player can figure out on his <s>on</s>own, which can be a lot more fun than being told all the fine details of fortress 1337. I do think it would be good to separate the spoilers more in some cases, but that's a totally different topic.
:For another example, I think we can agree that it is pointless to have a page telling how to dig a 1-tile channel pit and designate it as a Quantum Dump, given that you know how a Quantum Dump works. We used to have (still have? not sure) one of those. --[[User:Savok|Savok]] 03:59, 10 September 2009 (UTC)

::I think your quantum dump page has been reincarnated at [[dwarven physics]]?
::OK I think I see these points:
::# there is no clear guideline how much spoiling "is alowed"
::# there is no clear guideline on how specific an article can get (scope vs depth)
::# there is no clear guideline on when a "spoiler alert" should be given.
::I think that guidelines are good, in general. The rules are a bit flexible as most of us expect given this is a game-wiki not an encyclopedia. I know you do a lot more admin-editing than anyone else put together so you (Savok) probably have a better 1,000 ft view of the size of this problem than everyone else. Having said that... I would err greatly on allowing pages which are "game-world correct" to remain, allowing pages which don't have (dreadful) spoilers in the lead section to not have "ugly" spoiler warnings, and if we can have articles on [[computing]] and [[Glowing pit]] then pretty much there is no aspect of the game which is off-limits to being exposed by spoilers.
::I'm also agreeing with Njero, that if I hadn't found this wiki as quickly as I did, with detailed (and spoilerific) content of things from "how to dig" to "how to fight" and "what's hard to fight"... I would probably have deleted the game within 2 days of downloading it. Some of us don't find the forum that helpful![[User:GarrieIrons|Gar]][[User Talk:GarrieIrons|rie]] 05:51, 10 September 2009 (UTC)
:::+1 what GI said. I read the wiki before starting - I, personally, hate the whole "trial and errour" thing from scratch, especially in a game where the wrong little mistake can mean GAME OVER. I'm average-bright, and I still found that a lot of the "detail" was lost on me, at least until I had experienced it (or nearly so.) HFS? Still haven't breached one yet (slow computer, and in no rush) - so I can parrot a lot about that, but really have no personal feel for it and still look forward to that experience (even if now I won't walk in blind to that particular practical joke). If I'd wanted a surprise, I'd have not read those articles (and would be someone else).

:::That said, I '''''do''''' find that many mid-experience and advanced articles do repeat basic concepts too much - the "how to dig a channel" for a quantum dump example, above. And over-link, etc. However, if a newb were to stumble on that page, altho' they aren't ready for the advanced stuff, they may wonder what the basic stuff is - and follow those links. So... I don't think it's over-detailed for anyone except those who know the game (i.e. "us"). For the newb, stumbling about on the wiki, they either ''want'' to read about it, or ''need'' to, or both. Less detail is fewer links, and less overall usefulness to the (self-filtering) target audience.--[[User:Albedo|Albedo]] 19:53, 10 September 2009 (UTC)

:We do not detail pointlessly. More spoiler warnings? Why not. The collapsibles might be a nice solution in many places. But no limits to the completeness of the wiki please. It's hard to figure out quite a bit of the more complex, and interesting, stuff like machinery on your own and quite a bit is counterintuitive too, like how levers work. It may be really neat if you think up using channels as moats yourself, but it still took me several tries to get a nice and working setup. Oh and bridges.. I still made so many mistakes ''after'' reading up on things. And as far as strategy goes, I have my own opinion on quite a few things said in the wiki, as do others, and often it's just those views that are put in the articles. Like I think its's fine to have your woodcutter ''not'' trained because an axe as such is a fine defense already. And knowing that, on some maps, with some effort, you can have an UG tree farm improves the fun (no, not [[fun]], '''fun'''). It's still hard and rewarding to actually ''do'' it.

:Information may be a bit (over-!)redundant here and there, yes, but I am confident this will clear out on itself by and by when articles are better organized to be read "in a row". Lastly, what we write here, especially the strategy bits, will be found just as readily in the forums. --[[User:Birthright|Birthright]] 19:22, 12 September 2009 (UTC)

"Woodcutters are working outdoors where they are in constant danger of being ambushed by invaders or attacked by wild animals"

You want to delete that? Savok, You are a cruel man.

"(unless, of course, you are the proud owner of an underground tree farm),"

I'd really like to know how the first player figured tower caps out on his own. Mayor kudos to him, if, but i rather suspect toady dropped a hint. So do we.

"but they are also one of the few civilian professions which carry weapons with them."

Well, it should be obvious that the axe still works as weapon, too...hm...but it isn't. So we say it.

Thus, it can be helpful to teach them how to use their axes to defend themselves (and others) properly by making them spend a few months as axedwarfs in your military."

Okay this part could be reworded like you suggest: Woodcutting does not improve goblincutting. But wouldn't the information be the same? --[[User:Höhlenschreck|Höhlenschreck]] 21:07, 12 September 2009 (UTC)

I know I'm a little late to this discussion; but as an honest to goodness newbie I've found the wiki invaluable as is. I've been playing DF for probably 3 weeks now. I attempted to dive right in and just play without reading the wiki or anything, just the actual in-game help. What a mistake that was! I couldn't even figure out how to turn down the volume on the in game music at first! (partly because on a lap top without a num-pad the numbers for up-down selection were less then intuitive). So far I've found most articles have just about the right amount of depth; although some could use some clarification). With the help of the wiki I discovered how many mistakes I really made on my first embark and how lucky I am to still have that fort nearly 7 dwarf years later. I almost had a lot of [[fun]] with lava; but a quick trip to the wiki made me realize all I needed was a constructed wall or door. That really saved my bacon. --[[User:Kelsa|Kelsa]] 05:38, 11 October 2009 (UTC)

== A for Anonymity? ==

On at least [[Talk:Fortress_defense#Use_of_User_Names_in_Defense_Designs|one page]], the concept of "non-ownership" of wiki contributions has been agreed upon, that designs should not have User's names attached, and phrases like ''"I like to..."'' be changed to ''"Some users like to..."'' . Currently, the letter "[[Dwarf_Fortress_Wiki:Community_Portal#A|A"]] is for "Alphabet" - hardly enlightening. I wouldn't mind seeing this slot used for a more formalized policy in this direction, to avoid repeating [[Talk:Bedroom_design#Personalisation?|this discussion]]. (Or is the alphabet thing now sacrosanct as is?) 
The applications of such "catch-all" pages are endless, especially as mod's become more and more prevalent both in-game and on this site.--[[User:Albedo|Albedo]] 19:42, 10 September 2009 (UTC)

:Eh. For some things, we obviously want to give credit - [[tilesets]], for example. Personally, I would say that [[:File:Housing by Marble Dice.png|this bedroom design]] probably should be credited to Marble Dice. I don't think a policy that putting data here automatically makes ownership of it go to the wiki (and the wiki will make it anonymous) is a very useful one... --[[User:Savok|Savok]] 20:34, 10 September 2009 (UTC)
::Not so much ownership - ''certainly'' not a release of rights to intellectual property in ''any'' legal sense - but more a de-emphasis of personal credit over contribution for contribution's sake. My name would be all over these pages, as would many others' - that would get old fast, and (possibly) encourage competition and possessiveness, rather than collaboration and contribution. But, as you say... eh. Just thought I'd ask.--[[User:Albedo|Albedo]] 21:15, 10 September 2009 (UTC)

:The thing that strikes me here is, it looks to me as though some of the designs (the fractals etc) have not been put here by the person who designed them. They were designed, discussed on a forum, then someone else thought they looked good and put them here.
:Even if that isn't right - the rest of the [[bedroom]] article reads as though that is how it happened. Until you get to the final entry - which in the original form looked very "owned".
:If you want to own something put it in user space. If you put it in article space expect it to get edited.
:I think that is the rule that needs to exist "somewhere", by nature wiki contributions aren't anonymous. [[User:GarrieIrons|Gar]][[User Talk:GarrieIrons|rie]] 00:08, 11 September 2009 (UTC)

== Category titles (capitalization) ==

Reviving [http://dwarf.lendemaindeveille.com/index.php/Dwarf_Fortress_Wiki_talk:Community_Portal/archive1#Category_tags this] section from the archive, you'll see that our [[Special:Categories|categories]] page (also, Category:Templates) has so many capitalization inconsistencies it'll make your head spin. I propose Category:Formatting Templates as preferable to Category:Formatting templates though the existence of both shows that this needs to be addressed. 
Also, how do you wikilink to those catagory pages? Is it possible?--[[User:Rowenlemmings|Rowenlemmings]] 21:01, 13 September 2009 (UTC)
:First I agree there should be a rule for naming categories, and as per "the" wiki, it should be "first letter of first word only capitalised unless there's a really good reason" (eg: <nowiki>[[Category:Toady One]]</nowiki> where the name of the category is a proper noun / "real name" ).
:<s>Secondly - Categories are "just" normal article pages with some magic behind them, link to them the same as any article. </s> oops I'm wrong let me check that.
:[[User:GarrieIrons|Gar]][[User Talk:GarrieIrons|rie]] 03:26, 19 September 2009 (UTC)
::To link to a category page put a colon ''':'''in front of the word Category in the <nowiki>[[ ]]</nowiki> eg <nowiki>[[:Category:Wiki]]</nowiki> -> [[:Category:Wiki]][[User:GarrieIrons|Gar]][[User Talk:GarrieIrons|rie]] 03:34, 19 September 2009 (UTC)
:::Ah hah, mystery solved.--[[User:Rowenlemmings|''Rowen'']][[User Talk:Rowenlemmings|(talk)]] 02:00, 22 September 2009 (UTC)

::While this is all well and good for new categories, renaming existing categories is much more difficult than renaming pages. With a page we can simply redirect, but to rename a category we need to go through each page in it and change the tag. This is a lot of work for relatively little gain. [[User:VengefulDonut|VengefulDonut]] 13:44, 22 September 2009 (UTC)
:::Is there anyone around that can "borrow" a bot from "the other wiki" to do this kind of stuff? From my understanding a bot that
:::#scrapes [[:Bad Category Name]] for the list of articles
:::#scrapes [[:Bad Category Name]] for any actual content
:::#loads each article in turn
::::#searches for [[:Bad Category Name]]
::::#replaces [[:Bad Category Name]] with [[:Good category name]]
::::#saves the article
:::#Writes the content from [[:Bad Category Name]] to [[:Good category name]]
:::is relatively straight forward (as bots go).
:::I don't know anything about actually using bots but I know what they can do.
:::How big is this wiki without the media part anyway? I thought the other thing about wikis is it is "relatively easy" to d/l the whole thing as a flat file, make this kind of edit with a text editor, and write it back up. After checking to see if anyone has edited any of the pages of course ;) [[User:GarrieIrons|Gar]][[User Talk:GarrieIrons|rie]] 13:43, 26 September 2009 (UTC)

==Bottom or Top==
Not a big thing, but it seems we should have a rule whether new edits/sections in any non-article space should go at top or bottom of the page. Might also be added to the newbie welcome template. --[[User:Höhlenschreck|Höhlenschreck]] 21:49, 18 September 2009 (UTC)
:Dunno if a rule is needed, most ppl quickly work out that the default action of the "+" magic button is to add a new section at the bottom of the page so this is how you "should" do it manually.[[User:GarrieIrons|Gar]][[User Talk:GarrieIrons|rie]] 03:22, 19 September 2009 (UTC)

== Proposal: [[:Category:Best of DF Wiki]] ==

[[User:BaronW|BaronW's dwarven calculator]] blew my mind and made me crave some way of recognizing and celebrating it. I propose the creation of a wiki category that would consist entirely of abnormally excellent material to wow the reader and shock the house. This category would be managed by way of nomination and [[:Category talk:Best of DF Wiki|discussion]] rather than ad hoc addition, and a link to it would be added to the [[Main Page]] to encourage newbies to visit and marvel (I guess under "Wiki articles by category"). Think of it as a collective favorites list.

My nominations for initial inclusion:
* [[User:BaronW|BaronW]]'s calculator, of course
* [[:File:DF_Cheese.jpg]]
* [[:File:SquirrSurvCathedralAir1.PNG]]
* [[User:Vattic/Orcsicle maker Explained|Vattic/Orcsicle maker Explained]]
* [[Morul]]

# Feedback on the general concept?
# Comments on these nominations?
# Your own nominations?
--[[User:HebaruSan|HebaruSan]] 02:30, 14 November 2009 (UTC)

40d:Macro design

2009-11-13T16:29:20Z

HebaruSan: improvements negotiated on talk page

Playing Dwarf Fortress means lots of typing. Macros can reduce this typing, but they must be planned and designed carefully. This page discusses how to design a macro and avoid common problems. The specific operation or structure for which you are creating a macro is beyond the scope of this page.

== Macro delay ==
Forum and wiki participants have observed that some macros can take hours to run. This happens because there is a built-in delay between each macro command; since the game as shipped includes no preset macros, this delay is set to a value that allows the human player to see each move and debug any mistakes.

The solution is to change MACRO_MS in [[init.txt]] from 150 to 0. Most macros on any system commonly run better with some delay between commands{{verify}}; a MACRO_MS:1 seems to be a good run-time setting.

== Planning ==
There are thousands of ways to do anything, but we would like to pick the best or near-best solution. In the case of DF's macros we want to see our macro run in the fewest steps possible, getting the most out of each command.

Start by planning out your design as a series of steps to create the final result. Then code each step individually, while taking note of the before and after steps. Like the complete macro, each step has many possible different coding solutions. Try to pick one that is simple (short) but also goes best with the step before it, and will end somewhere that's advantageous for the next step. Try to keep a step to a single type of operation; this will save the time of continuously switching between modes.

:Example: Fields (boxes or area-selections) have four corners. Your code traverses from one corner to the opposite corner to define the field. It doesn't matter which corner you start at. So pick a start and stop point of your field that's convenient for the next and previous steps. This saves a lot of time spent walking the cursor around.

== Repeats ==
The macro syntax allows commands to be repeated using a numeric parameter. The following scripts take the same time to execute.

[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]

[MACRO:CURSOR_UP:'''20''']

The condensed version is more readable, but these work the same way.

== Movement ==
Most of the time a macro takes to run is spent moving the cursor around. This can be sped up through the use of the "_FAST" versions of the move commands and by moving diagonally.

=== Fast movement ===
When you hold the {{key|Shift}} key in the game UI and press an arrow key, the cursor jumps ten squares instead of one. Similarly, each cursor command has a "_FAST" version that jumps ten squares in the same time a normal movement command takes to travel on square.

The following code,

[MACRO:CURSOR_UP:33]

is the same as 33 moving commands however,

[MACRO:CURSOR_UP_FAST:3]
[MACRO:CURSOR_UP:3]

is the exact same action in only 4 commands.

=== Backpedaling ===
When the 1's digit is higher than 5, backing the cursor up can achieve faster run times.

[MACRO:CURSOR_UP:38]

Can be sped up with _FAST commands:

[MACRO:CURSOR_UP_FAST:3]
[MACRO:CURSOR_UP:8]

This brings 38 commands down to just 11. However this can be better optimized by moving ''past'' the intended destination and backing up.

[MACRO:CURSOR_UP_FAST:4]
[MACRO:CURSOR_Down:2]

Is the exact same cursor position change but in only 6 moves. This can have [[#Edge collision|side effects]] however and must be done carefully.

=== Diagonal movement ===
Most people using modern keyboards are familiar with the T-shaped arrow key block. The numeric keypad has arrows too, and on some keyboards the {{key|1}} {{key|3}} {{key|7}} {{key|9}} keys have arrows as well. Regardless of whether your numeric keypad has arrows on it, you can move with the {{key|1}} {{key|3}} {{key|7}} {{key|9}} keys. Diagonal movement is also possible in macros, and it can be used to reduce the number of commands required.

[MACRO:CURSOR_UP:8]
[MACRO:CURSOR_RIGHT:8]

can be replaced by

[MACRO:CURSOR_UPRIGHT:8]

This dropped the command count from 16 to 8. It also works for non-squares too.

[MACRO:CURSOR_UP:12]
[MACRO:CURSOR_RIGHT:16]

can be replaced by

[MACRO:CURSOR_UPRIGHT:12]
[MACRO:CURSOR_RIGHT:4]

This saved us 12 unneeded commands.

The "_FAST" works in the game and in your scripts on diagonals too. Further bringing down the the previous example command count to just,

[MACRO:CURSOR_UPRIGHT_FAST:1]
[MACRO:CURSOR_UPRIGHT:2]
[MACRO:CURSOR_RIGHT:4]

So from 38 commands to just 7, with a little planning.

Diagonal movement commands are written as '''vertical''' then '''horizontal''' with no separating "_"

=== Final cursor placement ===
When designing scripts, it's a good idea to plan where to leave off. The two common ideas are:
* Back where the script started, which is less disorienting to the user. This is best for macros that are intended to be used once.
* In position for an instant repeat of the macro, for macros that are likely to be used several times in a row.
If your macro makes a 3 square wide section of hallway to the left, then put the cursor in a position that allows for a repeat call of the macro to add a second section.

Both are better than just stopping the cursor wherever it happens to be.

= Troubleshooting =

== Off-by-one errors ==
When your script doesn't run as planned, check if you went too far on a movement action. This can happen if you confuse the number of squares ''designated'' with the number of squares ''moved''.

For example, to make a '''5x5''' box, use 4's instead of 5's:

[MACRO:SELECT:1]
[MACRO:CURSOR_LEFT:'''4''']
[MACRO:CURSOR_UP:'''4''']
[MACRO:SELECT:1]

The cursor's initial position always counts as 1 "extra" square, since you're defining movement, not a size.

# 1 square ''designated'', '''0''' squares ''moved''

## 2 squares ''designated'', '''1''' square ''moved''

### 3 squares ''designated'', '''2''' squares ''moved''

== Edge collision ==
When the cursor hits an edge of the map, it stops there, no matter how far your script wants to travel that way. This is per command, and if you're not expecting to hit an edge, this will corrupt that execution of the script. To avoid this, the script-runner must ensure that the script has enough room to run when it is started. The script-designer can help by clearly documenting how much space is needed.

Scripts can also run into trouble with [[#Backpedaling|backpedaling optimizations]]. Backpedaling can extend your script's running area beyond the area where it is making changes. If the script-runner only leaves enough space for the changes themselves, there is a risk that any _FAST jumps outside that area will be shortened by hitting an edge, and any subsequent backpedaling operations will then start from the wrong position. Therefore, it is recommend to only use backpedaling that does not go outside of your script's work area.

For example, if your script operates inside a 17x4 rectangle, getting across it with the following code,

[MACRO:CURSOR_RIGHT_FAST:2]
[MACRO:CURSOR_LEFT:3]

will place the cursor incorrectly if an edge is 19 squares away.

For script areas of 6, 7, 8, or 9, it may be wise to avoid backpedaling entirely, since any _FAST operation would move the cursor outside that range. But with a script area that small, speed probably isn't as much of an issue.

For areas larger than 10 spaces, reordering the commands can keep the cursor in-range while still using backpedaling optimizations. The above example is equivalent to this:

[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_LEFT:3]

Which we can reorder to:

[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_LEFT:3]
[MACRO:CURSOR_RIGHT_FAST:1]

This is the same run time and number of commands, yet the cursor says inside the script area. The backpedaling "LEFT:3" command now backs up in the space the first "_FAST" command had already traveled. (Note that if it had been placed ''first'', the cursor would have backpedaled out the other side.)

[[Category:Guides]]
[[Category:Interface]]

40d Talk:Macro design

2009-11-13T16:25:14Z

HebaruSan:

== Updates to my work in progress ==

Wow thats a lot of updates to a page I was building, that had no links to, with no discussion page entries.., and I had to go to bed.

I like most of what has been done except for the following
*Changing a "Step to Far" to Off-by-one Errors
**This is the exact opposite of the common off-by-one error of arrays and for loops, while it is an error of just 1, this is misleading I think. Also "off-by-one" is really just a CS term.
* The Change (labeled " Off-by-one") to make "current" into "initial"
**This is wrong, as it can occur anywhere in the script not on just the initial movement.
* In Fast Movement
** The Concept of the cursor jumping was removed and replaced with " the cursor moves ten squares instead of one". The old Term of "Jumping" gets across the idea of skipping/is-faster than ten squares of movement
* What was wrong with "(nearly half)"
* "Troubleshooting"
** this is a "design" page, not a how to code page. the Original "Problems to avoid" term is more toward the concept of "read this section first and have it in your head while coding". Not to figure out what when wrong after the fact. Hopefully if they design it right the first time, it will work perfectly with no debugging.
* I think the Second Edge Collision paragraph read a lot better the way it was.
* "applies to a command" isn't correct.
**Original didn't have that issue

Over all I'm glad for the help (especially in the conversion to a 3rd person), I just didn't expect it until the page was actively linked some where. I'll make the above changes if I don't see a justification not-to comments. [[User:Larek|Larek]] 22:37, 12 November 2009 (UTC)

: Heh, yeah, every edit you make shows up in [[Special:RecentChanges]], and there are several people who watch that page. In general, as soon as you click save, people will see your change and look at it, and if it's in the main namespace, they will probably make changes, too. If you want to keep exclusive ownership over something, you can make a user page like [[User:Larek/Macro design]]. We'll still see it, but it's considered bad form to ''edit'' someone else's personal pages.
:* Why do you say it's the opposite of an off by one error? The programming term is used to describe confusion in loop conditions when iterating over an array. It seems quite analogous to me; maybe you can elaborate.
:* Re: current vs initial, my thought was that it's the starting point for a given series of movement commands. Personally I think that's clear from the context, but I'm open to other ideas.
:* Would you be happy with "the cursor '''jumps''' ten squares instead of one"? I wouldn't have a problem with that.
:* I thought "(nearly half)" would be obvious to anyone reading the numbers. In general, if text is unnecessary, then removing it means you get to the next necessary idea faster.
:* You say it's not about debugging, but the first clause was already "When your script doesn't run as planned" before I edited. That sounds like debugging to me. Personally I don't think debugging is inappropriate on a design page; people following along are likely to need debugging strategies unless they somehow do everything perfectly the first time.
:* I thought the edge collision section was missing some key concepts, specifically the possible disparity between changed-area and traversed-area which is the root cause of the problem in the first place. What advantages do you see in its original phrasing?
:* Admittedly, "applies to" is metaphorical. I was trying to express that now instead of (normal jump)(backpedal jump) you have (backpedal jump)(normal jump), since the "backward" movement takes place earlier. I'll try to think of a better phrasing, but please feel free to come up with something yourself.
: But welcome to the wiki, and thank you for contributing!
: --[[User:HebaruSan|HebaruSan]] 00:05, 13 November 2009 (UTC)

::Wow, So we have hawks, perched, looking for fresh meat. :)
::No it wasn't a personal page, It was a initial work in progress that I hadn't gotten to a first release state yet. I had not Idea that you could do sub-user pages. The heavy editing with no comments through me off a bit too. Water under the bridge.
::*"the opposite of an off by one error", off-by-one is a CS term and I'll use your diagram to hopefully show what I mean.
<pre>

In the 'normal' world people count like this

1 2 3 4 5 6 7...
# # # # # # #...

They teach that in Kindergarten I think.

However in the World of Bits, CS (arrays, integers, loops etc) count like this

0 1 2 3 4 5 6...
# # # # # # #...

There starting value is 0, so their first(1) operation is dealing with item zero(0).
Since CS People originally lived in a non bit world, they tend to revert back creating
and off by one.

In DF macros we don't count, we transition like this

1 2 3 4 5 6 ...
#>#>#>#>#>#>#...

So at the end of the first(1) operation we are dealing with item Two(2), thus the
opposite size of '1' than the CS notion is from the Kindergarten method.
</pre>
::* The other place I see programmers use off-by-one is that, a lot of loop and data structures (like ques)have initial-case and/or final-case conditions that differ from the main content of the loop or structure. When their code doesn't run right, instead of trying to recalculate the loop variables, they first test to see if they're off by one (in both directions), and see if it works.
::** This is like DF macros, But in the DF case it should be always one to high, hence the name "a step to far". Where in this second use if off-by-one its multi directional. I'm not set on the old name, but I think that implying a direction and not implying guess-and-check is good.

::*I thought current was easier it to understand, instead of a whole bunch of moves each with an initial position. I guess it's more of a flowing concept than a start, stop, start, stop... Doesn't matter too much, it's just a wording opinion.

::*Yes I think the term jump, helps the concept greatly

::*True the text should short and sweet, but we could also write a page that says "do good coding" and thats it. People tend to get "glossy eyed" when you throw a lot of numbers at them. which this article does. I thought reiterating the the count went from 38->11 is god but taking that to 11->6 its Really good too. Sure it's easily notice that they lost 27 steps in the first optimization, and that saving 5 steps isn't bad. But I wanted ''nearly half'' in there, to draw attention to the second optimization, That it is saving 45.5% ~= 50% which is big, or at least sounds bigger than just 5.

::* Cool you caught me on my own language. Hey it was a work in progress. Yes I do expect them to do a some debugging, but not debugging the design but mistakes when typing in the code.
::** I think however that the design-not-debug is still a good idea. The Back Peddling part shouldn't be a debug anyway since, if script runs correctly once, most people will stop and call it good. (and not see an issue with their Back Peddling) Its a thing that needs to be thought of during the design. And the Travel length should be "in the designers mind" too.

::*The first way, I thought, was easier to read. You made the long middle sentence even longer with more "big' words. And the original seemed to have a lighter tone.

::*OK Lets see,
::** Original
::*** "travels over the same area the previous "_FAST" command covered."
::** Current
::*** "now applies to the first "_FAST" command"
::** If the Original is no good how about
::*** "now backs up in the space the first "_FAST" command had already traveled."
::** Or something else..
::[[User:Larek|Larek]] 14:55, 13 November 2009 (UTC)

::: Take a look at [http://en.wikipedia.org/wiki/Off-by-one_error#Fencepost_error Wikipedia's graphic for "Fencepost" errors], a kind of off-by-one error. It's practically identical to what we're discussing here. Just like you can cover N-1 sections with N posts, you only need to move N-1 times to designate N tiles. If you think the phrase is too technical or obscure, that's one thing, but I don't think there's any question that it's applicable.
::: I like your "now backs up in the space...". I'll add that now, along with "jump".
::: --[[User:HebaruSan|HebaruSan]] 16:25, 13 November 2009 (UTC)

Utility:Stonesense

2009-11-13T15:35:55Z

HebaruSan:

If you are searching for "Stone Sense", the excellent reveal tool by 0x517A5D, see [http://dffd.wimbli.com/file.php?id=836]

This is a temporary placeholder for the Stonesense visualizer by Jonask, Solifuge, peterix (author of dfhack) and others.

==Stonesense==
Stonesense is a third party visualizer that lets you view your Dwarf Fortress world in a classic isometric perspective.

The official thread for feedback, questions, requests or bug reports is located at [http://www.bay12games.com/forum/index.php?topic=43260.0]

==Source code==
Project homepage:
http://code.google.com/p/stonesense/

==Sprites preview and todo list==
write me!

===Credits===
Stonesense was written by Jonask, peterix, and kaypy.
Initial graphics were provided by Solifuge.
Additional Graphics were contributed by:
(fill me in)

40d:Flood

2009-11-13T05:21:22Z

HebaruSan: /* How to flood a fortress */

Flooding generally refers to water getting loose and spreading out over an area, usually in an unregulated fashion. While this can be useful in creating plots of muddy ground for [[farming]], deliberately setting any amount of water loose in an area is risky at best, and at worst, will result in lots of [[fun#Flooding_accidents|fun]].

As in real life, water will seek to spread out given open space. In Dwarf Fortress, this means that water will spread until all tiles achieve a depth of 1/7, or it fills the space it is enclosed in. Water at a depth of 1/7 will eventually evaporate, leaving behind a muddy floor. Because of this, it would be nearly impossible to ruin a fortress with water from finite sources such as a [[murky pool|murky pool]]. Note, however, that [[river]]s, [[brook]]s, and [[ocean]]s are considered to have offscreen water sources; their supply has been observed to be infinite, as has that of [[aquifers]]. Tapping into one of these without some means of regulating the flow is almost certain to result in [[fun#Flooding_accidents|fun]].

Water movement is a major source of lag in the game.

Flood speed is counterintuitive. For example, if you build a ramp beneath the bottom of an [[underground pool]] connected to a large drainage shaft leading to a chasm, all the water in the upper levels of the pool will drain down into the drainage shaft leading all the way out into the chasm, filling it all nearly instantly 7/7 with water and submerging your hapless dorfs however far away in the shaft they may be. But once the space is filled, the flood slows down to the glacial pace at which water usually moves down tunnels, giving them plenty of time to drown.

== How to flood a fortress ==
{{D for Dwarf}}
So all your friends on the forums are recounting tales of the fortresses they've flooded, and you're feeling left out. Fret no more! In a few simple steps, you too can join the ranks of the hydrologically challenged.

The key is to tap into a renewable source of water, such as a river, and use its water [[pressure]] to overcome obstacles like distance or altitude. Remember that water always "wants" to rise back up to the same [[Z-axis|Z-level]] from which it originated!

Side view:
▒≈≈river≈≈ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒o <--well ▒▒▒▒▒▒▒▒▒▒ (well is optional)
▒▒▒▒▒▒▒▒▒▒ channel ▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ your fortress ▒
In this design, water will travel from the river through the channel, then '''up''' through the well and across and down into the rest of the fortress. For convenience, the vertical openings don't even need to be completely hollow chambers--ramps and stairs will work just as well!

If some of the levels that you need to flood are higher than the surface of the river, you can use [[screw pump]]s to compensate.
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
pumps--> %%_ ▒▒▒▒▒▒▒o <--well ▒▒▒▒▒▒▒▒▒▒ (well is optional)
▒_%% ▒ ▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
%% ▒ channel ▒▒▒ your fortress
▒≈≈river≈≈▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
Ordinarily, this above-river fortress would have been unfloodable, but with judicious application of pumps, the water can flow from a higher level than its original source, allowing it to engulf all of your precious bedrooms, workshops, and stockpiles.

=== Common pitfalls ===
Building the well above the level of the river:
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒o <--well ▒▒▒▒▒▒▒▒▒▒ (well is optional)
▒≈≈river≈≈ ▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒ channel ▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ your fortress ▒
In this failed flooding attempt, the water moves through the channel but only rises to the level immediately ''below'' the well. This means that the well will be usable and the fortress remains safe and dry. Better luck next time!

Re-pressurization with pumps:
▒≈≈river≈≈ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒o <--well ▒▒▒▒▒▒▒▒▒▒ (well is optional)
▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒ %% <--pump ▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ your fortress ▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒
Here the reckless placement of a pump blocks water from flowing directly through; instead, the water level is again "reset" to the same level as the pump, and the well will be safe to use. Our condolences to this fort's pathetically dry dwarves.

[[Category:FAQ - Water]][[Category:Physics]]

40d:Flood

2009-11-13T05:10:36Z

HebaruSan: cautionary diagrams disguised as the opposite

Flooding generally refers to water getting loose and spreading out over an area, usually in an unregulated fashion. While this can be useful in creating plots of muddy ground for [[farming]], deliberately setting any amount of water loose in an area is risky at best, and at worst, will result in lots of [[fun#Flooding_accidents|fun]].

As in real life, water will seek to spread out given open space. In Dwarf Fortress, this means that water will spread until all tiles achieve a depth of 1/7, or it fills the space it is enclosed in. Water at a depth of 1/7 will eventually evaporate, leaving behind a muddy floor. Because of this, it would be nearly impossible to ruin a fortress with water from finite sources such as a [[murky pool|murky pool]]. Note, however, that [[river]]s, [[brook]]s, and [[ocean]]s are considered to have offscreen water sources; their supply has been observed to be infinite, as has that of [[aquifers]]. Tapping into one of these without some means of regulating the flow is almost certain to result in [[fun#Flooding_accidents|fun]].

Water movement is a major source of lag in the game.

Flood speed is counterintuitive. For example, if you build a ramp beneath the bottom of an [[underground pool]] connected to a large drainage shaft leading to a chasm, all the water in the upper levels of the pool will drain down into the drainage shaft leading all the way out into the chasm, filling it all nearly instantly 7/7 with water and submerging your hapless dorfs however far away in the shaft they may be. But once the space is filled, the flood slows down to the glacial pace at which water usually moves down tunnels, giving them plenty of time to drown.

== How to flood a fortress ==
{{D for Dwarf}}
So all your friends on the forums are recounting tales of the fortresses they've flooded, and you're feeling left out. Fret no more! In a few simple steps, you too can join the ranks of the hydrologically challenged.

The key is to tap into a renewable source of water, such as a river, and use its water [[pressure]] to overcome obstacles like distance or altitude. Remember that water always "wants" to rise back up to the same [[Z-axis|Z-level]] from which it originated!

Side view:
▒≈≈river≈≈ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒o <--well ▒▒▒▒▒▒▒▒▒▒ (well is optional)
▒▒▒▒▒▒▒▒▒▒ channel ▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ your fortress ▒
In this design, water will travel from the river through the channel, then '''up''' through the well and across and down into the rest of the fortress. For convenience, the vertical openings don't even need to be completely hollow chambers--ramps and stairs will work just as well!

If some of the levels that you need to flood are higher than the surface of the river, you can use [[screw pump]]s to compensate.
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
pumps--> %%_ ▒▒▒▒▒▒▒o <--well ▒▒▒▒▒▒▒▒▒▒ (well is optional)
▒_%% ▒ ▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
%% ▒ channel ▒▒▒ your fortress
≈≈river≈≈ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
Ordinarily, this above-river fortress would have been unfloodable, but with judicious application of pumps, the water can flow from a higher level than its original source, allowing it to engulf all of your precious bedrooms, workshops, and stockpiles.

=== Common pitfalls ===
Building the well above the level of the river:
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒o <--well ▒▒▒▒▒▒▒▒▒▒ (well is optional)
▒≈≈river≈≈ ▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒ channel ▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ your fortress ▒
In this failed flooding attempt, the water moves through the channel but only rises to the level immediately ''below'' the well. This means that the well will be usable and the fortress remains safe and dry. Better luck next time!

Re-pressurization with pumps:
▒≈≈river≈≈ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒o <--well ▒▒▒▒▒▒▒▒▒▒ (well is optional)
▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒ %% <--pump ▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ your fortress ▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒
Here the reckless placement of a pump blocks water from flowing directly through; instead, the water level is again "reset" to the same level as the pump, and the well will be safe to use. Our condolences to this fort's pathetically dry dwarves.

[[Category:FAQ - Water]][[Category:Physics]]

File talk:Typical Humie Caravan.png

2009-11-13T02:18:39Z

HebaruSan: Created page with 'When you unpause, do they get out and exchange insurance information, or perhaps have a fist fight depending on personality traits? --~~~~'

When you unpause, do they get out and exchange insurance information, or perhaps have a fist fight depending on personality traits? --[[User:HebaruSan|HebaruSan]] 02:18, 13 November 2009 (UTC)

40d Talk:Macro design

2009-11-13T00:05:19Z

HebaruSan:

== Updates to my work in progress ==

Wow thats a lot of updates to a page I was building, that had no links to, with no discussion page entires.., and I had to go to bed.

I like most of what has been done except for the following
*Changing a "Step to Far" to Off-by-one Errors
**This is the exact oppiste of the common off-by-one error of arrays and for loops, while it is an error of just 1, this is missleading I think. Also "off-by-one" is really just a CS term.
* The Change (labled " Off-by-one") to make "current" into "initial"
**This is wrong, as it can occure anywhere in the script not on just the inital movement.
* In Fast Movement
** The Concept of the cursor jumping was removed and repalced with " the cursor moves ten squares instead of one". The old Term of "Jumping" gets across the idea of skipping/is-faster than ten squares of movement
* What was wrong with "(nearly half)"
* "Troubleshooting"
** this is a "design" page, not a how to code page. thge Orginal "Problems to avoid" term is more toward the concept of "read this section first and have it in your head while coding". Not to figure out what when wrong after the fact. Hopefully if they design it right the first time, it will work perfectly with no debugging.
* I think the Second Edge Collion paragraph read a lot better the way it was.
* "applies to a comand" isn't correct.
**Original didn't have that issue

Over all I'm glad for the help (espescally in the conversion to a 3rd person), I just didn't expect it until the page was activly linked some where. I'll make the above changes if I don't see a justifaction not-to comments. [[User:Larek|Larek]] 22:37, 12 November 2009 (UTC)

: Heh, yeah, every edit you make shows up in [[Special:RecentChanges]], and there are several people who watch that page. In general, as soon as you click save, people will see your change and look at it, and if it's in the main namespace, they will probably make changes, too. If you want to keep exclusive ownership over something, you can make a user page like [[User:Larek/Macro design]]. We'll still see it, but it's considered bad form to ''edit'' someone else's personal pages.
:* Why do you say it's the opposite of an off by one error? The programming term is used to describe confusion in loop conditions when iterating over an array. It seems quite analogous to me; maybe you can elaborate.
:* Re: current vs initial, my thought was that it's the starting point for a given series of movement commands. Personally I think that's clear from the context, but I'm open to other ideas.
:* Would you be happy with "the cursor '''jumps''' ten squares instead of one"? I wouldn't have a problem with that.
:* I thought "(nearly half)" would be obvious to anyone reading the numbers. In general, if text is unnecessary, then removing it means you get to the next necessary idea faster.
:* You say it's not about debugging, but the first clause was already "When your script doesn't run as planned" before I edited. That sounds like debugging to me. Personally I don't think debugging is inappropriate on a design page; people following along are likely to need debugging strategies unless they somehow do everything perfectly the first time.
:* I thought the edge collision section was missing some key concepts, specifically the possible disparity between changed-area and traversed-area which is the root cause of the problem in the first place. What advantages do you see in its original phrasing?
:* Admittedly, "applies to" is metaphorical. I was trying to express that now instead of (normal jump)(backpedal jump) you have (backpedal jump)(normal jump), since the "backward" movement takes place earlier. I'll try to think of a better phrasing, but please feel free to come up with something yourself.
: But welcome to the wiki, and thank you for contributing!
: --[[User:HebaruSan|HebaruSan]] 00:05, 13 November 2009 (UTC)

40d:Macro design

2009-11-12T17:56:26Z

HebaruSan: /* Off-by-one errors */

Playing Dwarf Fortress means lots of typing. Macros can reduce this typing, but they must be planned and designed carefully. This page discusses how to design a macro and avoid common problems. The specific operation or structure for which you are creating a macro is beyond the scope of this page.

== Macro delay ==
Forum and wiki participants have observed that some macros can take hours to run. This happens because there is a built-in delay between each macro command; since the game as shipped includes no preset macros, this delay is set to a value that allows the human player to see each move and debug any mistakes.

The solution is to change MACRO_MS in [[init.txt]] from 150 to 0. Most macros on any system commonly run better with some delay between commands{{verify}}; a MACRO_MS:1 seems to be a good run-time setting.

== Planning ==
There are thousands of ways to do anything, but we would like to pick the best or near-best solution. In the case of DF's macros we want to see our macro run in the fewest steps possible, getting the most out of each command.

Start by planning out your design as a series of steps to create the final result. Then code each step individually, while taking note of the before and after steps. Like the complete macro, each step has many possible different coding solutions. Try to pick one that is simple (short) but also goes best with the step before it, and will end somewhere that's advantageous for the next step. Try to keep a step to a single type of operation; this will save the time of continuously switching between modes.

:Example: Fields (boxes or area-selections) have four corners. Your code traverses from one corner to the opposite corner to define the field. It doesn't matter which corner you start at. So pick a start and stop point of your field that's convenient for the next and previous steps. This saves a lot of time spent walking the cursor around.

== Repeats ==
The macro syntax allows commands to be repeated using a numeric parameter. The following scripts take the same time to execute.

[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]

[MACRO:CURSOR_UP:'''20''']

The condensed version is more readable, but these work the same way.

== Movement ==
Most of the time a macro takes to run is spent moving the cursor around. This can be sped up through the use of the "_FAST" versions of the move commands and by moving diagonally.

=== Fast movement ===
When you hold the {{key|Shift}} key in the game UI and press an arrow key, the cursor moves ten squares instead of one. Similarly, each cursor command has a "_FAST" version that jumps ten squares in the same time a normal movement command takes to travel on square.

The following code,

[MACRO:CURSOR_UP:33]

is the same as 33 moving commands however,

[MACRO:CURSOR_UP_FAST:3]
[MACRO:CURSOR_UP:3]

is the exact same action in only 4 commands.

=== Backpedaling ===
When the 1's digit is higher than 5, backing the cursor up can achieve faster run times.

[MACRO:CURSOR_UP:38]

Can be sped up with _FAST commands:

[MACRO:CURSOR_UP_FAST:3]
[MACRO:CURSOR_UP:8]

This brings 38 commands down to just 11. However this can be better optimized by moving ''past'' the intended destination and backing up.

[MACRO:CURSOR_UP_FAST:4]
[MACRO:CURSOR_Down:2]

Is the exact same cursor position change but in only 6 moves. This can have [[#Edge collision|side effects]] however and must be done carefully.

=== Diagonal movement ===
Most people using modern keyboards are familiar with the T-shaped arrow key block. The numeric keypad has arrows too, and on some keyboards the {{key|1}} {{key|3}} {{key|7}} {{key|9}} keys have arrows as well. Regardless of whether your numeric keypad has arrows on it, you can move with the {{key|1}} {{key|3}} {{key|7}} {{key|9}} keys. Diagonal movement is also possible in macros, and it can be used to reduce the number of commands required.

[MACRO:CURSOR_UP:8]
[MACRO:CURSOR_RIGHT:8]

can be replaced by

[MACRO:CURSOR_UPRIGHT:8]

This dropped the command count from 16 to 8. It also works for non-squares too.

[MACRO:CURSOR_UP:12]
[MACRO:CURSOR_RIGHT:16]

can be replaced by

[MACRO:CURSOR_UPRIGHT:12]
[MACRO:CURSOR_RIGHT:4]

This saved us 12 unneeded commands.

The "_FAST" works in the game and in your scripts on diagonals too. Further bringing down the the previous example command count to just,

[MACRO:CURSOR_UPRIGHT_FAST:1]
[MACRO:CURSOR_UPRIGHT:2]
[MACRO:CURSOR_RIGHT:4]

So from 38 commands to just 7, with a little planning.

Diagonal movement commands are written as '''vertical''' then '''horizontal''' with no separating "_"

=== Final cursor placement ===
When designing scripts, it's a good idea to plan where to leave off. The two common ideas are:
* Back where the script started, which is less disorienting to the user. This is best for macros that are intended to be used once.
* In position for an instant repeat of the macro, for macros that are likely to be used several times in a row.
If your macro makes a 3 square wide section of hallway to the left, then put the cursor in a position that allows for a repeat call of the macro to add a second section.

Both are better than just stopping the cursor wherever it happens to be.

= Troubleshooting =

== Off-by-one errors ==
When your script doesn't run as planned, check if you went too far on a movement action. This can happen if you confuse the number of squares ''designated'' with the number of squares ''moved''.

For example, to make a '''5x5''' box, use 4's instead of 5's:

[MACRO:SELECT:1]
[MACRO:CURSOR_LEFT:'''4''']
[MACRO:CURSOR_UP:'''4''']
[MACRO:SELECT:1]

The cursor's initial position always counts as 1 "extra" square, since you're defining movement, not a size.

# 1 square ''designated'', '''0''' squares ''moved''

## 2 squares ''designated'', '''1''' square ''moved''

### 3 squares ''designated'', '''2''' squares ''moved''

== Edge collision ==
When the cursor hits an edge of the map, it stops there, no matter how far your script wants to travel that way. This is per command, and if you're not expecting to hit an edge, this will corrupt that execution of the script. To avoid this, the script-runner must ensure that the script has enough room to run when it is started. The script-designer can help by clearly documenting how much space is needed.

Scripts can also run into trouble with [[#Backpedaling|backpedaling optimizations]]. Backpedaling can extend your script's running area beyond the area where it is making changes. If the script-runner only leaves enough space for the changes themselves, there is a risk that any _FAST jumps outside that area will be shortened by hitting an edge, and any subsequent backpedaling operations will then start from the wrong position. Therefore, it is recommend to only use backpedaling that does not go outside of your script's work area.

For example, if your script operates inside a 17x4 rectangle, getting across it with the following code,

[MACRO:CURSOR_RIGHT_FAST:2]
[MACRO:CURSOR_LEFT:3]

will place the cursor incorrectly if an edge is 19 squares away.

For script areas of 6, 7, 8, or 9, it may be wise to avoid backpedaling entirely, since any _FAST operation would move the cursor outside that range. But with a script area that small, speed probably isn't as much of an issue.

For areas larger than 10 spaces, reordering the commands can keep the cursor in-range while still using backpedaling optimizations. The above example is equivalent to this:

[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_LEFT:3]

Which we can reorder to:

[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_LEFT:3]
[MACRO:CURSOR_RIGHT_FAST:1]

This is the same run time and number of commands, yet the cursor says inside the script area. The backpedaling "LEFT:3" command now applies to the first "_FAST" command, rather than the second. (Note that if it had been placed ''first'', the cursor would have backpedaled out the other side.)

[[Category:Guides]]
[[Category:Interface]]

40d:Macro design

2009-11-12T17:55:24Z

HebaruSan:

Playing Dwarf Fortress means lots of typing. Macros can reduce this typing, but they must be planned and designed carefully. This page discusses how to design a macro and avoid common problems. The specific operation or structure for which you are creating a macro is beyond the scope of this page.

== Macro delay ==
Forum and wiki participants have observed that some macros can take hours to run. This happens because there is a built-in delay between each macro command; since the game as shipped includes no preset macros, this delay is set to a value that allows the human player to see each move and debug any mistakes.

The solution is to change MACRO_MS in [[init.txt]] from 150 to 0. Most macros on any system commonly run better with some delay between commands{{verify}}; a MACRO_MS:1 seems to be a good run-time setting.

== Planning ==
There are thousands of ways to do anything, but we would like to pick the best or near-best solution. In the case of DF's macros we want to see our macro run in the fewest steps possible, getting the most out of each command.

Start by planning out your design as a series of steps to create the final result. Then code each step individually, while taking note of the before and after steps. Like the complete macro, each step has many possible different coding solutions. Try to pick one that is simple (short) but also goes best with the step before it, and will end somewhere that's advantageous for the next step. Try to keep a step to a single type of operation; this will save the time of continuously switching between modes.

:Example: Fields (boxes or area-selections) have four corners. Your code traverses from one corner to the opposite corner to define the field. It doesn't matter which corner you start at. So pick a start and stop point of your field that's convenient for the next and previous steps. This saves a lot of time spent walking the cursor around.

== Repeats ==
The macro syntax allows commands to be repeated using a numeric parameter. The following scripts take the same time to execute.

[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]

[MACRO:CURSOR_UP:'''20''']

The condensed version is more readable, but these work the same way.

== Movement ==
Most of the time a macro takes to run is spent moving the cursor around. This can be sped up through the use of the "_FAST" versions of the move commands and by moving diagonally.

=== Fast movement ===
When you hold the {{key|Shift}} key in the game UI and press an arrow key, the cursor moves ten squares instead of one. Similarly, each cursor command has a "_FAST" version that jumps ten squares in the same time a normal movement command takes to travel on square.

The following code,

[MACRO:CURSOR_UP:33]

is the same as 33 moving commands however,

[MACRO:CURSOR_UP_FAST:3]
[MACRO:CURSOR_UP:3]

is the exact same action in only 4 commands.

=== Backpedaling ===
When the 1's digit is higher than 5, backing the cursor up can achieve faster run times.

[MACRO:CURSOR_UP:38]

Can be sped up with _FAST commands:

[MACRO:CURSOR_UP_FAST:3]
[MACRO:CURSOR_UP:8]

This brings 38 commands down to just 11. However this can be better optimized by moving ''past'' the intended destination and backing up.

[MACRO:CURSOR_UP_FAST:4]
[MACRO:CURSOR_Down:2]

Is the exact same cursor position change but in only 6 moves. This can have [[#Edge collision|side effects]] however and must be done carefully.

=== Diagonal movement ===
Most people using modern keyboards are familiar with the T-shaped arrow key block. The numeric keypad has arrows too, and on some keyboards the {{key|1}} {{key|3}} {{key|7}} {{key|9}} keys have arrows as well. Regardless of whether your numeric keypad has arrows on it, you can move with the {{key|1}} {{key|3}} {{key|7}} {{key|9}} keys. Diagonal movement is also possible in macros, and it can be used to reduce the number of commands required.

[MACRO:CURSOR_UP:8]
[MACRO:CURSOR_RIGHT:8]

can be replaced by

[MACRO:CURSOR_UPRIGHT:8]

This dropped the command count from 16 to 8. It also works for non-squares too.

[MACRO:CURSOR_UP:12]
[MACRO:CURSOR_RIGHT:16]

can be replaced by

[MACRO:CURSOR_UPRIGHT:12]
[MACRO:CURSOR_RIGHT:4]

This saved us 12 unneeded commands.

The "_FAST" works in the game and in your scripts on diagonals too. Further bringing down the the previous example command count to just,

[MACRO:CURSOR_UPRIGHT_FAST:1]
[MACRO:CURSOR_UPRIGHT:2]
[MACRO:CURSOR_RIGHT:4]

So from 38 commands to just 7, with a little planning.

Diagonal movement commands are written as '''vertical''' then '''horizontal''' with no separating "_"

=== Final cursor placement ===
When designing scripts, it's a good idea to plan where to leave off. The two common ideas are:
* Back where the script started, which is less disorienting to the user. This is best for macros that are intended to be used once.
* In position for an instant repeat of the macro, for macros that are likely to be used several times in a row.
If your macro makes a 3 square wide section of hallway to the left, then put the cursor in a position that allows for a repeat call of the macro to add a second section.

Both are better than just stopping the cursor wherever it happens to be.

= Troubleshooting =

== Off-by-one errors ==
When your script doesn't run as planned, check if you went too far on a movement action. This can happen if you confuse the number of squares ''designated'' with the number of squares ''moved''.

For example, to make a '''5x5''' box, use 4's instead of 5's:

[MACRO:SELECT:1]
[MACRO:CURSOR_LEFT:'''4''']
[MACRO:CURSOR_UP:'''4''']
[MACRO:SELECT:1]

The cursor's current position always counts as 1 "extra" square, since you're defining movement, not a size.

# 1 square ''designated'', '''0''' squares ''moved''

## 2 squares ''designated'', '''1''' square ''moved''

### 3 squares ''designated'', '''2''' squares ''moved''

== Edge collision ==
When the cursor hits an edge of the map, it stops there, no matter how far your script wants to travel that way. This is per command, and if you're not expecting to hit an edge, this will corrupt that execution of the script. To avoid this, the script-runner must ensure that the script has enough room to run when it is started. The script-designer can help by clearly documenting how much space is needed.

Scripts can also run into trouble with [[#Backpedaling|backpedaling optimizations]]. Backpedaling can extend your script's running area beyond the area where it is making changes. If the script-runner only leaves enough space for the changes themselves, there is a risk that any _FAST jumps outside that area will be shortened by hitting an edge, and any subsequent backpedaling operations will then start from the wrong position. Therefore, it is recommend to only use backpedaling that does not go outside of your script's work area.

For example, if your script operates inside a 17x4 rectangle, getting across it with the following code,

[MACRO:CURSOR_RIGHT_FAST:2]
[MACRO:CURSOR_LEFT:3]

will place the cursor incorrectly if an edge is 19 squares away.

For script areas of 6, 7, 8, or 9, it may be wise to avoid backpedaling entirely, since any _FAST operation would move the cursor outside that range. But with a script area that small, speed probably isn't as much of an issue.

For areas larger than 10 spaces, reordering the commands can keep the cursor in-range while still using backpedaling optimizations. The above example is equivalent to this:

[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_LEFT:3]

Which we can reorder to:

[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_LEFT:3]
[MACRO:CURSOR_RIGHT_FAST:1]

This is the same run time and number of commands, yet the cursor says inside the script area. The backpedaling "LEFT:3" command now applies to the first "_FAST" command, rather than the second. (Note that if it had been placed ''first'', the cursor would have backpedaled out the other side.)

[[Category:Guides]]
[[Category:Interface]]

40d:Macro design

2009-11-12T17:55:08Z

HebaruSan: categorize

Playing Dwarf Fortress means lots of typing. Macros can reduce this typing, but they must be planned and designed carefully. This page discusses how to design a macro and avoid common problems. The specific operation or structure for which you are creating a macro is beyond the scope of this page.

== Macro delay ==
Forum and wiki participants have observed that some macros can take hours to run. This happens because there is a built-in delay between each macro command; since the game as shipped includes no preset macros, this delay is set to a value that allows the human player to see each move and debug any mistakes.

The solution is to change MACRO_MS in [[init.txt]] from 150 to 0. Most macros on any system commonly run better with some delay between commands{{verify}}; a MACRO_MS:1 seems to be a good run-time setting.

== Planning ==
There are thousands of ways to do anything, but we would like to pick the best or near-best solution. In the case of DF's macros we want to see our macro run in the fewest steps possible, getting the most out of each command.

Start by planning out your design as a series of steps to create the final result. Then code each step individually, while taking note of the before and after steps. Like the complete macro, each step has many possible different coding solutions. Try to pick one that is simple (short) but also goes best with the step before it, and will end somewhere that's advantageous for the next step. Try to keep a step to a single type of operation; this will save the time of continuously switching between modes.

:Example: Fields (boxes or area-selections) have four corners. Your code traverses from one corner to the opposite corner to define the field. It doesn't matter which corner you start at. So pick a start and stop point of your field that's convenient for the next and previous steps. This saves a lot of time spent walking the cursor around.

== Repeats ==
The macro syntax allows commands to be repeated using a numeric parameter. The following scripts take the same time to execute.

[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]

[MACRO:CURSOR_UP:'''20''']

The condensed version is more readable, but these work the same way.

== Movement ==
Most of the time a macro takes to run is spent moving the cursor around. This can be sped up through the use of the "_FAST" versions of the move commands and by moving diagonally.

=== Fast movement ===
When you hold the {{key|Shift}} key in the game UI and press an arrow key, the cursor moves ten squares instead of one. Similarly, each cursor command has a "_FAST" version that jumps ten squares in the same time a normal movement command takes to travel on square.

The following code,

[MACRO:CURSOR_UP:33]

is the same as 33 moving commands however,

[MACRO:CURSOR_UP_FAST:3]
[MACRO:CURSOR_UP:3]

is the exact same action in only 4 commands.

=== Backpedaling ===
When the 1's digit is higher than 5, backing the cursor up can achieve faster run times.

[MACRO:CURSOR_UP:38]

Can be sped up with _FAST commands:

[MACRO:CURSOR_UP_FAST:3]
[MACRO:CURSOR_UP:8]

This brings 38 commands down to just 11. However this can be better optimized by moving ''past'' the intended destination and backing up.

[MACRO:CURSOR_UP_FAST:4]
[MACRO:CURSOR_Down:2]

Is the exact same cursor position change but in only 6 moves. This can have [[#Edge collision|side effects]] however and must be done carefully.

=== Diagonal movement ===
Most people using modern keyboards are familiar with the T-shaped arrow key block. The numeric keypad has arrows too, and on some keyboards the {{key|1}} {{key|3}} {{key|7}} {{key|9}} keys have arrows as well. Regardless of whether your numeric keypad has arrows on it, you can move with the {{key|1}} {{key|3}} {{key|7}} {{key|9}} keys. Diagonal movement is also possible in macros, and it can be used to reduce the number of commands required.

[MACRO:CURSOR_UP:8]
[MACRO:CURSOR_RIGHT:8]

can be replaced by

[MACRO:CURSOR_UPRIGHT:8]

This dropped the command count from 16 to 8. It also works for non-squares too.

[MACRO:CURSOR_UP:12]
[MACRO:CURSOR_RIGHT:16]

can be replaced by

[MACRO:CURSOR_UPRIGHT:12]
[MACRO:CURSOR_RIGHT:4]

This saved us 12 unneeded commands.

The "_FAST" works in the game and in your scripts on diagonals too. Further bringing down the the previous example command count to just,

[MACRO:CURSOR_UPRIGHT_FAST:1]
[MACRO:CURSOR_UPRIGHT:2]
[MACRO:CURSOR_RIGHT:4]

So from 38 commands to just 7, with a little planning.

Diagonal movement commands are written as '''vertical''' then '''horizontal''' with no separating "_"

=== Final cursor placement ===
When designing scripts, it's a good idea to plan where to leave off. The two common ideas are:
* Back where the script started, which is less disorienting to the user. This is best for macros that are intended to be used once.
* In position for an instant repeat of the macro, for macros that are likely to be used several times in a row.
If your macro makes a 3 square wide section of hallway to the left, then put the cursor in a position that allows for a repeat call of the macro to add a second section.

Both are better than just stopping the cursor wherever it happens to be.

= Troubleshooting =

== Off-by-one errors ==
When your script doesn't run as planned, check if you went too far on a movement action. This can happen if you confuse the number of squares ''designated'' with the number of squares ''moved''.

For example, to make a '''5x5''' box, use 4's instead of 5's:

[MACRO:SELECT:1]
[MACRO:CURSOR_LEFT:'''4''']
[MACRO:CURSOR_UP:'''4''']
[MACRO:SELECT:1]

The cursor's current position always counts as 1 "extra" square, since you're defining movement, not a size.

# 1 square ''designated'', '''0''' squares ''moved''

## 2 squares ''designated'', '''1''' square ''moved''

### 3 squares ''designated'', '''2''' squares ''moved''

== Edge collision ==
When the cursor hits an edge of the map, it stops there, no matter how far your script wants to travel that way. This is per command, and if you're not expecting to hit an edge, this will corrupt that execution of the script. To avoid this, the script-runner must ensure that the script has enough room to run when it is started. The script-designer can help by clearly documenting how much space is needed.

Scripts can also run into trouble with [[#Backpedaling|backpedaling optimizations]]. Backpedaling can extend your script's running area beyond the area where it is making changes. If the script-runner only leaves enough space for the changes themselves, there is a risk that any _FAST jumps outside that area will be shortened by hitting an edge, and any subsequent backpedaling operations will then start from the wrong position. Therefore, it is recommend to only use backpedaling that does not go outside of your script's work area.

For example, if your script operates inside a 17x4 rectangle, getting across it with the following code,

[MACRO:CURSOR_RIGHT_FAST:2]
[MACRO:CURSOR_LEFT:3]

will place the cursor incorrectly if an edge is 19 squares away.

For script areas of 6, 7, 8, or 9, it may be wise to avoid backpedaling entirely, since any _FAST operation would move the cursor outside that range. But with a script area that small, speed probably isn't as much of an issue.

For areas larger than 10 spaces, reordering the commands can keep the cursor in-range while still using backpedaling optimizations. The above example is equivalent to this:

[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_LEFT:3]

Which we can reorder to:

[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_LEFT:3]
[MACRO:CURSOR_RIGHT_FAST:1]

This is the same run time and number of commands, yet the cursor says inside the script area. The backpedaling "LEFT:3" command now applies to the first "_FAST" command, rather than the second. (Note that if it had been placed ''first'', the cursor would have backpedaled out the other side.)

[[Category:Guide]]
[[Category:Interface]]

40d:Macro design

2009-11-12T17:48:18Z

HebaruSan:

Playing Dwarf Fortress means lots of typing. Macros can reduce this typing, but they must be planned and designed carefully. This page discusses how to design a macro and avoid common problems. The specific operation or structure for which you are creating a macro is beyond the scope of this page.

== Macro delay ==
Forum and wiki participants have observed that some macros can take hours to run. This happens because there is a built-in delay between each macro command; since the game as shipped includes no preset macros, this delay is set to a value that allows the human player to see each move and debug any mistakes.

The solution is to change MACRO_MS in [[init.txt]] from 150 to 0. Most macros on any system commonly run better with some delay between commands{{verify}}; a MACRO_MS:1 seems to be a good run-time setting.

== Planning ==
There are thousands of ways to do anything, but we would like to pick the best or near-best solution. In the case of DF's macros we want to see our macro run in the fewest steps possible, getting the most out of each command.

Start by planning out your design as a series of steps to create the final result. Then code each step individually, while taking note of the before and after steps. Like the complete macro, each step has many possible different coding solutions. Try to pick one that is simple (short) but also goes best with the step before it, and will end somewhere that's advantageous for the next step. Try to keep a step to a single type of operation; this will save the time of continuously switching between modes.

:Example: Fields (boxes or area-selections) have four corners. Your code traverses from one corner to the opposite corner to define the field. It doesn't matter which corner you start at. So pick a start and stop point of your field that's convenient for the next and previous steps. This saves a lot of time spent walking the cursor around.

== Repeats ==
The macro syntax allows commands to be repeated using a numeric parameter. The following scripts take the same time to execute.

[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]

[MACRO:CURSOR_UP:'''20''']

The condensed version is more readable, but these work the same way.

== Movement ==
Most of the time a macro takes to run is spent moving the cursor around. This can be sped up through the use of the "_FAST" versions of the move commands and by moving diagonally.

=== Fast movement ===
When you hold the {{key|Shift}} key in the game UI and press an arrow key, the cursor moves ten squares instead of one. Similarly, each cursor command has a "_FAST" version that jumps ten squares in the same time a normal movement command takes to travel on square.

The following code,

[MACRO:CURSOR_UP:33]

is the same as 33 moving commands however,

[MACRO:CURSOR_UP_FAST:3]
[MACRO:CURSOR_UP:3]

is the exact same action in only 4 commands.

=== Backpedaling ===
When the 1's digit is higher than 5, backing the cursor up can achieve faster run times.

[MACRO:CURSOR_UP:38]

Can be sped up with _FAST commands:

[MACRO:CURSOR_UP_FAST:3]
[MACRO:CURSOR_UP:8]

This brings 38 commands down to just 11. However this can be better optimized by moving ''past'' the intended destination and backing up.

[MACRO:CURSOR_UP_FAST:4]
[MACRO:CURSOR_Down:2]

Is the exact same cursor position change but in only 6 moves. This can have [[#Edge collision|side effects]] however and must be done carefully.

=== Diagonal movement ===
Most people using modern keyboards are familiar with the T-shaped arrow key block. The numeric keypad has arrows too, and on some keyboards the {{key|1}} {{key|3}} {{key|7}} {{key|9}} keys have arrows as well. Regardless of whether your numeric keypad has arrows on it, you can move with the {{key|1}} {{key|3}} {{key|7}} {{key|9}} keys. Diagonal movement is also possible in macros, and it can be used to reduce the number of commands required.

[MACRO:CURSOR_UP:8]
[MACRO:CURSOR_RIGHT:8]

can be replaced by

[MACRO:CURSOR_UPRIGHT:8]

This dropped the command count from 16 to 8. It also works for non-squares too.

[MACRO:CURSOR_UP:12]
[MACRO:CURSOR_RIGHT:16]

can be replaced by

[MACRO:CURSOR_UPRIGHT:12]
[MACRO:CURSOR_RIGHT:4]

This saved us 12 unneeded commands.

The "_FAST" works in the game and in your scripts on diagonals too. Further bringing down the the previous example command count to just,

[MACRO:CURSOR_UPRIGHT_FAST:1]
[MACRO:CURSOR_UPRIGHT:2]
[MACRO:CURSOR_RIGHT:4]

So from 38 commands to just 7, with a little planning.

Diagonal movement commands are written as '''vertical''' then '''horizontal''' with no separating "_"

=== Final cursor placement ===
When designing scripts, it's a good idea to plan where to leave off. The two common ideas are:
* Back where the script started, which is less disorienting to the user. This is best for macros that are intended to be used once.
* In position for an instant repeat of the macro, for macros that are likely to be used several times in a row.
If your macro makes a 3 square wide section of hallway to the left, then put the cursor in a position that allows for a repeat call of the macro to add a second section.

Both are better than just stopping the cursor wherever it happens to be.

= Troubleshooting =

== Off-by-one errors ==
When your script doesn't run as planned, check if you went too far on a movement action. This can happen if you confuse the number of squares ''designated'' with the number of squares ''moved''.

For example, to make a '''5x5''' box, use 4's instead of 5's:

[MACRO:SELECT:1]
[MACRO:CURSOR_LEFT:'''4''']
[MACRO:CURSOR_UP:'''4''']
[MACRO:SELECT:1]

The cursor's current position always counts as 1 "extra" square, since you're defining movement, not a size.

# 1 square ''designated'', '''0''' squares ''moved''

## 2 squares ''designated'', '''1''' square ''moved''

### 3 squares ''designated'', '''2''' squares ''moved''

== Edge collision ==
When the cursor hits an edge of the map, it stops there, no matter how far your script wants to travel that way. This is per command, and if you're not expecting to hit an edge, this will corrupt that execution of the script. To avoid this, the script-runner must ensure that the script has enough room to run when it is started. The script-designer can help by clearly documenting how much space is needed.

Scripts can also run into trouble with [[#Backpedaling|backpedaling optimizations]]. Backpedaling can extend your script's running area beyond the area where it is making changes. If the script-runner only leaves enough space for the changes themselves, there is a risk that any _FAST jumps outside that area will be shortened by hitting an edge, and any subsequent backpedaling operations will then start from the wrong position. Therefore, it is recommend to only use backpedaling that does not go outside of your script's work area.

For example, if your script operates inside a 17x4 rectangle, getting across it with the following code,

[MACRO:CURSOR_RIGHT_FAST:2]
[MACRO:CURSOR_LEFT:3]

will place the cursor incorrectly if an edge is 19 squares away.

For script areas of 6, 7, 8, or 9, it may be wise to avoid backpedaling entirely, since any _FAST operation would move the cursor outside that range. But with a script area that small, speed probably isn't as much of an issue.

For areas larger than 10 spaces, reordering the commands can keep the cursor in-range while still using backpedaling optimizations. The above example is equivalent to this:

[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_LEFT:3]

Which we can reorder to:

[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_LEFT:3]
[MACRO:CURSOR_RIGHT_FAST:1]

This is the same run time and number of commands, yet the cursor says inside the script area. The backpedaling "LEFT:3" command now applies to the first "_FAST" command, rather than the second. (Note that if it had been placed ''first'', the cursor would have backpedaled out the other side.)

40d:Macro design

2009-11-12T17:46:01Z

HebaruSan: /* Problems to avoid */ second pass of clean-up

Playing Dwarf Fortress means lots of typing. Macros can reduce this typing, but they must be planned and designed carefully. This page discusses how to design a macro and avoid common problems. The specific operation or structure for which you are creating a macro is beyond the scope of this page.

== Macro Delay ==
Forum and wiki participants have observed that some macros can take hours to run. This happens because there is a built-in delay between each macro command; since the game as shipped includes no preset macros, this delay is set to a value that allows the human player to see each move and debug any mistakes.

The solution is to change MACRO_MS in [[init.txt]] from 150 to 0. Most macros on any system commonly run better with some delay between commands{{verify}}; a MACRO_MS:1 seems to be a good run-time setting.

== Planning ==
There are thousands of ways to do anything, but we would like to pick the best or near-best solution. In the case of DF's macros we want to see our macro run in the fewest steps possible, getting the most out of each command.

Start by planning out your design as a series of steps to create the final result. Then code each step individually, while taking note of the before and after steps. Like the complete macro, each step has many possible different coding solutions. Try to pick one that is simple (short) but also goes best with the step before it, and will end somewhere that's advantageous for the next step. Try to keep a step to a single type of operation; this will save the time of continuously switching between modes.

:Example: Fields (boxes or area-selections) have four corners. Your code traverses from one corner to the opposite corner to define the field. It doesn't matter which corner you start at. So pick a start and stop point of your field that's convenient for the next and previous steps. This saves a lot of time spent walking the cursor around.

== Repeats ==
The macro syntax allows commands to be repeated using a numeric parameter. The following scripts take the same time to execute.

[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]

[MACRO:CURSOR_UP:'''20''']

The condensed version is more readable, but these work the same way.

== Movement ==
Most of the time a macro takes to run is spent moving the cursor around. This can be sped up through the use of the "_FAST" versions of the move commands and by moving diagonally.

=== Standard Movement ===
When you hold the {{key|Shift}} key in the game UI and press an arrow key, the cursor moves ten squares instead of one. Similarly, each cursor command has a "_FAST" version that jumps ten squares in the same time a normal movement command takes to travel on square.

The following code,

[MACRO:CURSOR_UP:33]

is the same as 33 moving commands however,

[MACRO:CURSOR_UP_FAST:3]
[MACRO:CURSOR_UP:3]

is the exact same action in only 4 commands.

=== Backpedaling ===
When the 1's digit is higher than 5, backing the cursor up can achieve faster run times.

[MACRO:CURSOR_UP:38]

Can be sped up with _FAST commands:

[MACRO:CURSOR_UP_FAST:3]
[MACRO:CURSOR_UP:8]

This brings 38 commands down to just 11. However this can be better optimized by moving ''past'' the intended destination and backing up.

[MACRO:CURSOR_UP_FAST:4]
[MACRO:CURSOR_Down:2]

Is the exact same cursor position change but in only 6 moves. This can have side effects however (covered below) and must be done carefully.

=== Diagonal Movement ===
Most people using modern keyboards are familiar with the T-shaped arrow key block. The numeric keypad has arrows too, and on some keyboards the {{key|1}} {{key|3}} {{key|7}} {{key|9}} keys have arrows as well. Regardless of whether your numeric keypad has arrows on it, you can move with the {{key|1}} {{key|3}} {{key|7}} {{key|9}} keys. Diagonal movement is also possible in macros, and it can be used to reduce the number of commands required.

[MACRO:CURSOR_UP:8]
[MACRO:CURSOR_RIGHT:8]

can be replaced by

[MACRO:CURSOR_UPRIGHT:8]

This dropped the command count from 16 to 8. It also works for non-squares too.

[MACRO:CURSOR_UP:12]
[MACRO:CURSOR_RIGHT:16]

can be replaced by

[MACRO:CURSOR_UPRIGHT:12]
[MACRO:CURSOR_RIGHT:4]

This saved us 12 unneeded commands.

The "_FAST" works in the game and in your scripts on diagonals too. Further bringing down the the previous example command count to just,

[MACRO:CURSOR_UPRIGHT_FAST:1]
[MACRO:CURSOR_UPRIGHT:2]
[MACRO:CURSOR_RIGHT:4]

So from 38 commands to just 7, with a little planning.

Diagonal movement commands are written as '''vertical''' then '''horizontal''' with no separating "_"

=== Cursor Return ===
When designing scripts, it's a good idea to plan where to leave off. The two common ideas are:
* Back where the script started, which is less disorienting to the user. This is best for macros that are intended to be used once.
* In position for an instant repeat of the macro, for macros that are likely to be used several times in a row.
If your macro makes a 3 square wide section of hallway to the left, then put the cursor in a position that allows for a repeat call of the macro to add a second section.

Both are better than just stopping the cursor wherever it happens to be.

= Troubleshooting =

== Off-by-one errors ==
When your script doesn't run as planned, check if you went too far on a movement action. This can happen if you confuse the number of squares ''designated'' with the number of squares ''moved''.

For example, to make a '''5x5''' box, use 4's instead of 5's:

[MACRO:SELECT:1]
[MACRO:CURSOR_LEFT:'''4''']
[MACRO:CURSOR_UP:'''4''']
[MACRO:SELECT:1]

The cursor's current position always counts as 1 "extra" square, since you're defining movement, not a size.

# 1 square ''designated'', '''0''' squares ''moved''

## 2 squares ''designated'', '''1''' square ''moved''

### 3 squares ''designated'', '''2''' squares ''moved''

== Edge collision ==
When the cursor hits an edge of the map, it stops there, no matter how far your script wants to travel that way. This is per command, and if you're not expecting to hit an edge, this will corrupt that execution of the script. To avoid this, the script-runner must ensure that the script has enough room to run when it is started. The script-designer can help by clearly documenting how much space is needed.

Scripts can also run into trouble with [[#Backpedaling|backpedaling optimizations]]. Backpedaling can extend your script's running area beyond the area where it is making changes. If the script-runner only leaves enough space for the changes themselves, there is a risk that any _FAST jumps outside that area will be shortened by hitting an edge, and any subsequent backpedaling operations will then start from the wrong position. Therefore, it is recommend to only use backpedaling that does not go outside of your script's work area.

For example, if your script operates inside a 17x4 rectangle, getting across it with the following code,

[MACRO:CURSOR_RIGHT_FAST:2]
[MACRO:CURSOR_LEFT:3]

will place the cursor incorrectly if an edge is 19 squares away.

For script areas of 6, 7, 8, or 9, it may be wise to avoid backpedaling entirely, since any _FAST operation would move the cursor outside that range. But with a script area that small, speed probably isn't as much of an issue.

For areas larger than 10 spaces, reordering the commands can keep the cursor in-range while still using backpedaling optimizations. The above example is equivalent to this:

[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_LEFT:3]

Which we can reorder to:

[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_LEFT:3]
[MACRO:CURSOR_RIGHT_FAST:1]

This is the same run time and number of commands, yet the cursor says inside the script area. The backpedaling "LEFT:3" command now applies to the first "_FAST" command, rather than the second. (Note that if it had been placed ''first'', the cursor would have backpedaled out the other side.)

Macro Design

2009-11-12T17:09:52Z

HebaruSan: moved Macro Design to Macro design: same upper/lower case as Trap design

#REDIRECT [[Macro design]]

40d:Macro design

2009-11-12T17:09:51Z

HebaruSan: moved Macro Design to Macro design: same upper/lower case as Trap design

Playing Dwarf Fortress means lots of typing. Macros can reduce this typing, but they must be planned and designed carefully. This page discusses how to design a macro and avoid common problems. The specific operation or structure for which you are creating a macro is beyond the scope of this page.

== Macro Delay ==
Forum and wiki participants have observed that some macros can take hours to run. This happens because there is a built-in delay between each macro command; since the game as shipped includes no preset macros, this delay is set to a value that allows the human player to see each move and debug any mistakes.

The solution is to change MACRO_MS in [[init.txt]] from 150 to 0. Most macros on any system commonly run better with some delay between commands{{verify}}; a MACRO_MS:1 seems to be a good run-time setting.

== Planning ==
There are thousands of ways to do anything, but we would like to pick the best or near-best solution. In the case of DF's macros we want to see our macro run in the fewest steps possible, getting the most out of each command.

Start by planning out your design as a series of steps to create the final result. Then code each step individually, while taking note of the before and after steps. Like the complete macro, each step has many possible different coding solutions. Try to pick one that is simple (short) but also goes best with the step before it, and will end somewhere that's advantageous for the next step. Try to keep a step to a single type of operation; this will save the time of continuously switching between modes.

:Example: Fields (boxes or area-selections) have four corners. Your code traverses from one corner to the opposite corner to define the field. It doesn't matter which corner you start at. So pick a start and stop point of your field that's convenient for the next and previous steps. This saves a lot of time spent walking the cursor around.

== Repeats ==
The macro syntax allows commands to be repeated using a numeric parameter. The following scripts take the same time to execute.

[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]

[MACRO:CURSOR_UP:'''20''']

The condensed version is more readable, but these work the same way.

== Movement ==
Most of the time a macro takes to run is spent moving the cursor around. This can be sped up through the use of the "_FAST" versions of the move commands and by moving diagonally.

=== Standard Movement ===
When you hold the {{key|Shift}} key in the game UI and press an arrow key, the cursor moves ten squares instead of one. Similarly, each cursor command has a "_FAST" version that jumps ten squares in the same time a normal movement command takes to travel on square.

The following code,

[MACRO:CURSOR_UP:33]

is the same as 33 moving commands however,

[MACRO:CURSOR_UP_FAST:3]
[MACRO:CURSOR_UP:3]

is the exact same action in only 4 commands.

=== Backpedaling ===
When the 1's digit is higher than 5, backing the cursor up can achieve faster run times.

[MACRO:CURSOR_UP:38]

Can be sped up with _FAST commands:

[MACRO:CURSOR_UP_FAST:3]
[MACRO:CURSOR_UP:8]

This brings 38 commands down to just 11. However this can be better optimized by moving ''past'' the intended destination and backing up.

[MACRO:CURSOR_UP_FAST:4]
[MACRO:CURSOR_Down:2]

Is the exact same cursor position change but in only 6 moves. This can have side effects however (covered below) and must be done carefully.

=== Diagonal Movement ===
Most people using modern keyboards are familiar with the T-shaped arrow key block. The numeric keypad has arrows too, and on some keyboards the {{key|1}} {{key|3}} {{key|7}} {{key|9}} keys have arrows as well. Regardless of whether your numeric keypad has arrows on it, you can move with the {{key|1}} {{key|3}} {{key|7}} {{key|9}} keys. Diagonal movement is also possible in macros, and it can be used to reduce the number of commands required.

[MACRO:CURSOR_UP:8]
[MACRO:CURSOR_RIGHT:8]

can be replaced by

[MACRO:CURSOR_UPRIGHT:8]

This dropped the command count from 16 to 8. It also works for non-squares too.

[MACRO:CURSOR_UP:12]
[MACRO:CURSOR_RIGHT:16]

can be replaced by

[MACRO:CURSOR_UPRIGHT:12]
[MACRO:CURSOR_RIGHT:4]

This saved us 12 unneeded commands.

The "_FAST" works in the game and in your scripts on diagonals too. Further bringing down the the previous example command count to just,

[MACRO:CURSOR_UPRIGHT_FAST:1]
[MACRO:CURSOR_UPRIGHT:2]
[MACRO:CURSOR_RIGHT:4]

So from 38 commands to just 7, with a little planning.

Diagonal movement commands are written as '''vertical''' then '''horizontal''' with no separating "_"

=== Cursor Return ===
When designing scripts, it's a good idea to plan where to leave off. The two common ideas are:
* Back where the script started, which is less disorienting to the user. This is best for macros that are intended to be used once.
* In position for an instant repeat of the macro, for macros that are likely to be used several times in a row.
If your macro makes a 3 square wide section of hallway to the left, then put the cursor in a position that allows for a repeat call of the macro to add a second section.

Both are better than just stopping the cursor wherever it happens to be.

= Problems to avoid =

== A step to far ==
When your script doesn't run as planned, check if you went too far on a movement action. To make a 5x5 box the code is

//written for ease of reading
[MACRO:SELECT:1]
[MACRO:CURSOR_LEFT:4]
[MACRO:CURSOR_UP:4]
[MACRO:SELECT:1]

Those are 4's not 5's. The cursors current position is always 1, since it's really movement your defining not a size. Its an easy concept but also easy to forget/mess up.

==Edge Collision==
Edge Collision can be helpful in several situations. When you hit a edge you stop there, no matter how far your script wants to travel that way. This is per command and if your not expecting to hit a wall, it will corrupt that exeicution of the script. There is no way to avoid this. And in most cases, it's the script-runner's fault not the script-designer's.

However as a designer you can run into trouble with backpedaling optimizations as mentioned above. Backpedaling can jump you out of the working area of your script and then return, as long as there is enough extra space around your script area to do so. If an edge happens to be there, instant problem.

:If your script is made inside a 17x4 rectangle, getting across it with the following code,

[MACRO:CURSOR_RIGHT_FAST:2]
[MACRO:CURSOR_LEFT:3]

is fine, as long as an edge wasn't 19 squares away.

It's recommend to only use backpedaling that does not go outside of your script's work area.

With backpedaling movements, that are larger than 10 spaces, a simple change of order of operations can fix this issue. Here is the above example, with an order changes

[MACRO:CURSOR_RIGHT_FAST:2]
[MACRO:CURSOR_LEFT:3]

is really just

[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_LEFT:3]

so we can reorder it to

[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_LEFT:3]
[MACRO:CURSOR_RIGHT_FAST:1]

This is the same run time and number of commands, yet the cursor says inside the script area.
:For script areas of 6, 7, 8, or 9 your just out of luck and I would suggest not backpedaling, but with a script area so small, speed isn't that much of an issue.

:The backpedaling "LEFT:3" command, travels over the same area the previous "_FAST" command had covered. If it had been placed first, the cursor would have backpedaled out the other side.

40d:Macro design

2009-11-12T16:52:01Z

HebaruSan: first pass of clean-up

Playing Dwarf Fortress means lots of typing. Macros can reduce this typing, but they must be planned and designed carefully. This page discusses how to design a macro and avoid common problems. The specific operation or structure for which you are creating a macro is beyond the scope of this page.

== Macro Delay ==
Forum and wiki participants have observed that some macros can take hours to run. This happens because there is a built-in delay between each macro command; since the game as shipped includes no preset macros, this delay is set to a value that allows the human player to see each move and debug any mistakes.

The solution is to change MACRO_MS in [[init.txt]] from 150 to 0. Most macros on any system commonly run better with some delay between commands{{verify}}; a MACRO_MS:1 seems to be a good run-time setting.

== Planning ==
There are thousands of ways to do anything, but we would like to pick the best or near-best solution. In the case of DF's macros we want to see our macro run in the fewest steps possible, getting the most out of each command.

Start by planning out your design as a series of steps to create the final result. Then code each step individually, while taking note of the before and after steps. Like the complete macro, each step has many possible different coding solutions. Try to pick one that is simple (short) but also goes best with the step before it, and will end somewhere that's advantageous for the next step. Try to keep a step to a single type of operation; this will save the time of continuously switching between modes.

:Example: Fields (boxes or area-selections) have four corners. Your code traverses from one corner to the opposite corner to define the field. It doesn't matter which corner you start at. So pick a start and stop point of your field that's convenient for the next and previous steps. This saves a lot of time spent walking the cursor around.

== Repeats ==
The macro syntax allows commands to be repeated using a numeric parameter. The following scripts take the same time to execute.

[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]
[MACRO:CURSOR_UP:1]

[MACRO:CURSOR_UP:'''20''']

The condensed version is more readable, but these work the same way.

== Movement ==
Most of the time a macro takes to run is spent moving the cursor around. This can be sped up through the use of the "_FAST" versions of the move commands and by moving diagonally.

=== Standard Movement ===
When you hold the {{key|Shift}} key in the game UI and press an arrow key, the cursor moves ten squares instead of one. Similarly, each cursor command has a "_FAST" version that jumps ten squares in the same time a normal movement command takes to travel on square.

The following code,

[MACRO:CURSOR_UP:33]

is the same as 33 moving commands however,

[MACRO:CURSOR_UP_FAST:3]
[MACRO:CURSOR_UP:3]

is the exact same action in only 4 commands.

=== Backpedaling ===
When the 1's digit is higher than 5, backing the cursor up can achieve faster run times.

[MACRO:CURSOR_UP:38]

Can be sped up with _FAST commands:

[MACRO:CURSOR_UP_FAST:3]
[MACRO:CURSOR_UP:8]

This brings 38 commands down to just 11. However this can be better optimized by moving ''past'' the intended destination and backing up.

[MACRO:CURSOR_UP_FAST:4]
[MACRO:CURSOR_Down:2]

Is the exact same cursor position change but in only 6 moves. This can have side effects however (covered below) and must be done carefully.

=== Diagonal Movement ===
Most people using modern keyboards are familiar with the T-shaped arrow key block. The numeric keypad has arrows too, and on some keyboards the {{key|1}} {{key|3}} {{key|7}} {{key|9}} keys have arrows as well. Regardless of whether your numeric keypad has arrows on it, you can move with the {{key|1}} {{key|3}} {{key|7}} {{key|9}} keys. Diagonal movement is also possible in macros, and it can be used to reduce the number of commands required.

[MACRO:CURSOR_UP:8]
[MACRO:CURSOR_RIGHT:8]

can be replaced by

[MACRO:CURSOR_UPRIGHT:8]

This dropped the command count from 16 to 8. It also works for non-squares too.

[MACRO:CURSOR_UP:12]
[MACRO:CURSOR_RIGHT:16]

can be replaced by

[MACRO:CURSOR_UPRIGHT:12]
[MACRO:CURSOR_RIGHT:4]

This saved us 12 unneeded commands.

The "_FAST" works in the game and in your scripts on diagonals too. Further bringing down the the previous example command count to just,

[MACRO:CURSOR_UPRIGHT_FAST:1]
[MACRO:CURSOR_UPRIGHT:2]
[MACRO:CURSOR_RIGHT:4]

So from 38 commands to just 7, with a little planning.

Diagonal movement commands are written as '''vertical''' then '''horizontal''' with no separating "_"

=== Cursor Return ===
When designing scripts, it's a good idea to plan where to leave off. The two common ideas are:
* Back where the script started, which is less disorienting to the user. This is best for macros that are intended to be used once.
* In position for an instant repeat of the macro, for macros that are likely to be used several times in a row.
If your macro makes a 3 square wide section of hallway to the left, then put the cursor in a position that allows for a repeat call of the macro to add a second section.

Both are better than just stopping the cursor wherever it happens to be.

= Problems to avoid =

== A step to far ==
When your script doesn't run as planned, check if you went too far on a movement action. To make a 5x5 box the code is

//written for ease of reading
[MACRO:SELECT:1]
[MACRO:CURSOR_LEFT:4]
[MACRO:CURSOR_UP:4]
[MACRO:SELECT:1]

Those are 4's not 5's. The cursors current position is always 1, since it's really movement your defining not a size. Its an easy concept but also easy to forget/mess up.

==Edge Collision==
Edge Collision can be helpful in several situations. When you hit a edge you stop there, no matter how far your script wants to travel that way. This is per command and if your not expecting to hit a wall, it will corrupt that exeicution of the script. There is no way to avoid this. And in most cases, it's the script-runner's fault not the script-designer's.

However as a designer you can run into trouble with backpedaling optimizations as mentioned above. Backpedaling can jump you out of the working area of your script and then return, as long as there is enough extra space around your script area to do so. If an edge happens to be there, instant problem.

:If your script is made inside a 17x4 rectangle, getting across it with the following code,

[MACRO:CURSOR_RIGHT_FAST:2]
[MACRO:CURSOR_LEFT:3]

is fine, as long as an edge wasn't 19 squares away.

It's recommend to only use backpedaling that does not go outside of your script's work area.

With backpedaling movements, that are larger than 10 spaces, a simple change of order of operations can fix this issue. Here is the above example, with an order changes

[MACRO:CURSOR_RIGHT_FAST:2]
[MACRO:CURSOR_LEFT:3]

is really just

[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_LEFT:3]

so we can reorder it to

[MACRO:CURSOR_RIGHT_FAST:1]
[MACRO:CURSOR_LEFT:3]
[MACRO:CURSOR_RIGHT_FAST:1]

This is the same run time and number of commands, yet the cursor says inside the script area.
:For script areas of 6, 7, 8, or 9 your just out of luck and I would suggest not backpedaling, but with a script area so small, speed isn't that much of an issue.

:The backpedaling "LEFT:3" command, travels over the same area the previous "_FAST" command had covered. If it had been placed first, the cursor would have backpedaled out the other side.

File talk:DF Cheese.jpg

2009-11-11T23:55:46Z

HebaruSan: yes

BISHIEDORF [[User:KoboldInDisguise|KoboldInDisguise]] 12:21, 13 October 2009 (UTC)

Whoever made this, I adore you. [[User:Pariah|Pariah]] 22:00, 11 November 2009 (UTC)
: Seconded. This is amazing. --[[User:HebaruSan|HebaruSan]] 23:55, 11 November 2009 (UTC)

"The limp blueness of ... clapping"? Am I reading that right?--[[User:Albedo|Albedo]] 22:24, 11 November 2009 (UTC)