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.

Difference between revisions of "v0.34:Dwarf cancels task: Forbidden area"

From Dwarf Fortress Wiki
Jump to navigation Jump to search
(created to reflect the changes in civilian alert burrows)
 
m (link)
 
Line 1: Line 1:
 
{{av}}
 
{{av}}
This message occurs when a civilian [[burrow]] specified in a [[military]] [[alert]] excludes the destination of a dwarf on a task. This can commonly result from expanding your fortress after designating a civilian burrow, but failing to extend the burrow to encompass the new areas. Unfortunately, this message zooms to the location of the dwarf when the task was canceled, making it quite difficult to track down the location of the task/item that is causing the error.   
+
This message occurs when a civilian [[burrow]] specified in a [[civilian alert]] excludes the destination of a dwarf on a task. This can commonly result from expanding your fortress after designating a civilian burrow, but failing to extend the burrow to encompass the new areas. Unfortunately, this message zooms to the location of the dwarf when the task was canceled, making it quite difficult to track down the location of the task/item that is causing the error.   
  
 
{{Errors FAQ}}
 
{{Errors FAQ}}

Latest revision as of 20:45, 11 January 2013

This article is about an older version of DF.

This message occurs when a civilian burrow specified in a civilian alert excludes the destination of a dwarf on a task. This can commonly result from expanding your fortress after designating a civilian burrow, but failing to extend the burrow to encompass the new areas. Unfortunately, this message zooms to the location of the dwarf when the task was canceled, making it quite difficult to track down the location of the task/item that is causing the error.