Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
0002150Dwarf FortressPathfindingpublic2010-06-04 02:212012-03-06 09:27
normalminorunable to reproduce
WindowsXP 64
0002150: Weaver can not find path to webs when door unrelated to path to webs is forbidden, or may be confusing his jobs
I have a weaver who has been venturing down into the caverns, collecting webs and at the same time doing all of the fort's cavern revealing. However, this dwarf is also working as a mason. Near where he has been working as a mason is a door leading to a single tile room with many stones piled up for building. I forbid the door to that room, and he came up to the door. The announcement read "Uzol Zonelis, Weaver cancels Collect Webs: Could not find path. x10", then x6, then x4, then x1, then x3, then x7, then x2. However, this little room is a dead end, in no way connected to the path to the webs, which was a few tiles down the hall with no doors at all involved. There were no webs whatsoever in the small locked room, only basalt stones. When I unlocked the door, he proceeded to pick up a stone and start building walls. I figure either it was an odd pathing problem, or he is reporting the wrong jobs in his cancellations.
Not really sure on this one.
Shortly afterward, another dwarf complained that there was no way to get to the webs, and he was standing in the hospital. It was my weaponsmith, who for some reason also had all craft labors enabled and had minor skill in them all as well. This made me decide that possibly this is because there really were no webs accessible in the caverns, however that doesn't explain why the weaver was cancelling a "collect webs" job when in the process of picking up stones.
No tags attached.
duplicate of 0001254resolved Toady One When cavern is breached, web collection pathfinding spams with "unable to find path" 
Issue History
2010-06-04 02:21SalabasamaNew Issue
2010-06-04 08:58FootkerchiefRelationship addedduplicate of 0001369
2010-06-04 08:58FootkerchiefStatusnew => resolved
2010-06-04 08:58FootkerchiefResolutionopen => duplicate
2010-06-04 08:58FootkerchiefAssigned To => Footkerchief
2010-06-09 06:45Toady OneStatusresolved => closed
2012-03-06 09:27FootkerchiefRelationship addedduplicate of 0001254
2012-03-06 09:27FootkerchiefRelationship deleted0001369

There are no notes attached to this issue.