Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
0001005Dwarf FortressDwarf Mode -- Jobs, Cancellation and Suspensionpublic2010-04-11 09:552010-12-11 08:59
Mr. Boh 
Toady One 
normalminorhave not tried
closedduplicate 
PCVista 64Ultimate SP 2
0.31.02 
 
0001005: Bridge over a pit by only entrance to fort breaks pathfinding
I dug a pit in two stages and built two bridges over it in front of the only entrance to my fort in order to draw the bridges up and block access to the fort in the event of an attack.

Once the bridges were built I received a number of notices of job cancellations (seemed to be all hauling jobs) and about 10 of my 39 dwarves just hung out on the bridges. When I saved and reloaded they went on their way.


No tags attached.
child of 0000018closed Toady One Pathfinding fails to update after map changes 
Issue History
2010-04-11 09:55Mr. BohNew Issue
2010-04-11 10:19FootkerchiefRelationship addedchild of 0000018
2010-04-11 18:35FootkerchiefTag Attached: Still Present in 31.03?
2010-04-12 12:36FootkerchiefNote Added: 0003107
2010-04-12 12:36FootkerchiefStatusnew => resolved
2010-04-12 12:36FootkerchiefFixed in Version => 0.31.03
2010-04-12 12:36FootkerchiefResolutionopen => fixed
2010-04-12 12:36FootkerchiefAssigned To => Footkerchief
2010-04-12 12:40FootkerchiefStatusresolved => assigned
2010-04-12 12:40FootkerchiefAssigned ToFootkerchief => Toady One
2010-04-12 12:41FootkerchiefStatusassigned => resolved
2010-04-12 13:12FootkerchiefStatusresolved => assigned
2010-04-12 13:13FootkerchiefStatusassigned => resolved
2010-04-12 13:13FootkerchiefFixed in Version0.31.03 =>
2010-04-12 13:13FootkerchiefResolutionfixed => duplicate
2010-06-04 10:06FootkerchiefTag RenamedStill Present in 31.03? => Fixed in 31.03?
2010-06-09 06:46Toady OneStatusresolved => closed
2010-12-11 08:59DwarfuTag Detached: Fixed in 31.03?

Notes
(0003107)
Footkerchief   
2010-04-12 12:36   
This and other issues are being marked resolved because they fit the symptoms of the general pathing bug described by issues 0000018 and 0000070. If this issue represents an additional bug, it will most likely present different symptoms in 31.03, and a new report should be submitted.