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}}{{ | + | {{av}}{{exceptional}} |
− | '''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 | + | '''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 {{L|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 | + | Some traffic problems can be prevented by good {{L|Design strategies|fortress design}}, such as making hallway which are likely to be high use double or more width and placing {{L|stockpile|stockpiles}} close to relevant {{L|workshop|workshops}}. Other difficulties may be reduced by designating traffic areas. |
− | Vegetation (saplings) will tend to die if repeatedly trampled upon, leaving dead | + | Vegetation (saplings) will tend to die if repeatedly trampled upon, leaving dead {{L|Tree|sapling}}s or {{L|shrub}}s and quickly exposing bare {{L|soil}}. This may be desirable as {{L|tree}}s block dwarves' and {{L|caravan}}s' paths, but unchecked traffic may trample entire areas of {{L|forest}} regrowth. |
− | Only your dwarves will obey your traffic designations, and then only when they can. If a | + | Only your dwarves will obey your traffic designations, and then only when they can. If a {{L|job}} requires that they go into a restricted zone, they will. Other {{L|creature}}s will not recognize your traffic designations, and even {{L|domestic animal}}s or {{L|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 | + | 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 {{L|init.txt}}, or per-fortress values with {{K|d}}{{K|o}}. |
− | * It is often a good idea to set any | + | * It is often a good idea to set any {{L|water}} source in a {{L|biome}} with seasonal freezing to a Restricted area so your dwarves will be less likely to be caught on it when it melts. |
− | * Some dwarves get | + | * Some dwarves get {{L|thought|disturbed}} if they walk through a {{L|butcher's shop}} and see an animal being slaughtered, so you may wish to designate the shop as Restricted. |
− | * If an area occasionally gets | + | * If an area occasionally gets {{L|flood}}ed, or is dangerous for some reason, routing dwarves around it could be lifesaving. |
− | * Setting High traffic areas along | + | * Setting High traffic areas along {{L|road|roads}} outdoors prevents vegetation from being needlessly trampled. |
− | * An important use of traffic designations is to restrict movement in the tile where a | + | * An important use of traffic designations is to restrict movement in the tile where a {{L|ballista}}'s firing arrow originates. This will prevent tragic {{L|siege}} training accidents. Note that {{L|Pet|pets}} can and will be killed by firing ballista even if movement is restricted. |
− | Setting Restricted does not forbid a | + | Setting Restricted does not forbid a {{L|dwarf}} from traveling over those squares, but rather makes them willing to walk around them – for the normal cost table, 12.5 times further, or up to 25 times longer if there is an alternative high-traffic path. If you have an area that absolutely must not be stepped on by dwarves, consider {{L|wall|walls}}. |
==Limitations== | ==Limitations== | ||
Traffic designations only affect path preferences when pathfinding. Dwarves generally choose their jobs without weighing the pathfinding costs. For example, one cannot use traffic designations to direct a dwarf to confine his digging to a specific area. He will still take whatever path necessary to get to the job he has chosen to work. | Traffic designations only affect path preferences when pathfinding. Dwarves generally choose their jobs without weighing the pathfinding costs. For example, one cannot use traffic designations to direct a dwarf to confine his digging to a specific area. He will still take whatever path necessary to get to the job he has chosen to work. | ||
− | 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 | + | 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 {{L|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 == | == Using Traffic Areas to Improve Framerate == | ||
Line 30: | Line 30: | ||
== One-way paths == | == One-way paths == | ||
− | |||
− | See | + | Currently{{version|0.28.181.40d}}, 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''' {{L|ramp}}s - and with those, one-way halls, {{L|stair}}s, and any other restricted {{L|path}} you can create from one controlled access point to another. |
+ | |||
+ | See {{L|One-way}}. | ||
---- | ---- | ||
'''See also:''' | '''See also:''' | ||
− | :* | + | :* {{L|Path}} |
− | + | [[category:designations]] |