v50 Steam/Premium information for editors
  • v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
  • Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.

Editing 40d:Traffic

Jump to navigation Jump to search

Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.

You are editing a page for an older version of Dwarf Fortress ("Main" is the current version, not "40d"). Please make sure you intend to do this. If you are here by mistake, see the current page instead.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
{{av}}{{Quality|Masterwork}}
+
'''Traffic''' may become an issue once a settlement begins to grow in size. Movement in narrow hallways is slowed by [[dwarves]] moving past each other.
'''Traffic''' designations determine what path a dwarf will take, not what their final destination is. If a dwarf's task takes them somewhere, only a hard barrier will prevent them from going there. Since movement in narrow hallways is slowed by [[dwarves]] moving past each other, traffic may become an issue once a settlement begins to grow in size.  
 
  
 
Some traffic problems can be prevented by good [[Design strategies|fortress design]], such as making hallway which are likely to be high use double or more width and placing [[stockpile|stockpiles]] close to relevant [[workshop|workshops]]. Other difficulties may be reduced by designating traffic areas.
 
Some traffic problems can be prevented by good [[Design strategies|fortress design]], such as making hallway which are likely to be high use double or more width and placing [[stockpile|stockpiles]] close to relevant [[workshop|workshops]]. Other difficulties may be reduced by designating traffic areas.
  
Vegetation (saplings) will tend to die if repeatedly trampled upon, leaving dead [[Tree|sapling]]s or [[shrub]]s and quickly exposing bare [[soil]]. This may be desirable as [[tree]]s block dwarves' and [[caravan]]s' paths, but unchecked traffic may trample entire areas of [[forest]] regrowth.
+
Vegetation (saplings) will tend to die in outdoor areas with high traffic, quickly exposing bare [[soil]]. This may be desireable as [[tree]]s block dwarves' and [[caravan]]s' paths, but unchecked traffic may trample entire areas of [[forest]] regrowth.
 
 
Only your dwarves will obey your traffic designations, and then only when they can.  If a [[job]] requires that they go into a restricted zone, they will.  Other [[creature]]s will not recognize your traffic designations, and even [[domestic animal]]s or [[caravan]]s will follow their own pathing.
 
  
 
==Setting Traffic Areas==
 
==Setting Traffic Areas==
  
The {{K|d}}{{K|o}} combination sets '''traffic areas''', which are zones used to manipulate the movements of dwarves. Traffic areas can be designated as high, normal, low, or restricted. When walking from one point to another, dwarves consider these designations in finding the shortest path. High level traffic costs the pathfinding AI 1 point per square, Normal (default, undesignated) costs 2 points per square, Low costs 5, and Restricted costs 25. You can change the default values in [[init.txt]], or per-fortress values with {{K|d}}{{K|o}}.
+
The {{K|d}}{{K|o}} combination sets '''traffic areas''', which are zones used to manipulate the movements of dwarves. Traffic areas can be designated as high, normal, low, or restricted. When walking from one point to another, dwarves consider these designations in finding the shortest path. High level traffic costs the pathfinding AI 1 point per square, Normal (default, undesignated) costs 2 points per square, Low costs 5, and Restricted costs 25. You can change these values in [[init.txt]].
  
 
* It is often a good idea to set any [[water]] source in a [[biome]] with seasonal freezing to a Restricted area so your dwarves will be less likely to be caught on it when it melts.
 
* It is often a good idea to set any [[water]] source in a [[biome]] with seasonal freezing to a Restricted area so your dwarves will be less likely to be caught on it when it melts.
Line 25: Line 22:
 
Additionally, traffic designations cannot be used to restrict where a dwarf will stand when building/digging.  In other words, traffic designations will not prevent a dwarf from placing himself on the outside of the fort when the last tile of a [[moat]] or wall is completed.  In some cases, a workaround is to place a wall where you want the dwarf to avoid standing, and suspend it.  This prevents him from standing on that tile while building/digging.  When the job is finished, the suspended wall may be canceled.
 
Additionally, traffic designations cannot be used to restrict where a dwarf will stand when building/digging.  In other words, traffic designations will not prevent a dwarf from placing himself on the outside of the fort when the last tile of a [[moat]] or wall is completed.  In some cases, a workaround is to place a wall where you want the dwarf to avoid standing, and suspend it.  This prevents him from standing on that tile while building/digging.  When the job is finished, the suspended wall may be canceled.
  
== Using Traffic Areas to Improve Framerate ==
+
[[category:designations]]
 
 
In cavernous rooms that handle large amounts of through traffic but have a small number of exits (a large central dining room, for example) designating a few high-traffic paths ("freeways") between the doors can help reduce the pathfinding cost for dwarves who are just passing through.  There may also be benefits to adding low-traffic edges to these freeways to keep the search algorithm from looking for shortcuts.  Likewise, any large dead-end room that branches off a major hallway should have the area around its doorway marked low or restricted traffic to prevent dwarves from searching it for shortcuts.  As noted above in '''Limitations''', this should not affect the dwarves who have a legitimate reason to hang out in the dining hall or visit the storage room - they will path to their destination regardless.  Users may see up to a 10% increase in FPS by implementing these changes throughout their fortress.
 
 
 
== One-way paths ==
 
Due to what seems to be a minor bug rather than a feature, it's not only possible but quite easy to create '''one-way''' [[ramp]]s - and with those, one-way halls, [[stair]]s, and any other restricted [[path]] you can create from one controlled access point to another.
 
 
 
See [[One-way]].
 
 
 
----
 
'''See also:'''
 
 
 
:* [[Path]]
 
 
 
 
 
{{Category|Designations}}
 

Please note that all contributions to Dwarf Fortress Wiki are considered to be released under the GFDL & MIT (see Dwarf Fortress Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)