View Issue Details

IDProjectCategoryView StatusLast Update
0003525Dwarf FortressDwarf Mode -- Interface, Standing Orderspublic2014-08-01 13:40
ReporterQuietust Assigned ToToady One  
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
Product Version0.31.16 
Fixed in Version0.40.06 
Summary0003525: Auto Collect Webs adds tasks even when all webs are inaccessible
DescriptionMy fortress has a room which contains a giant cave spider and a goblin crossbowman chained up in such a way as to make the giant cave spider shoot lots of webs. The room uses a raising bridge in front of the goblin and floodgates at the entrance so that my weavers can gather the webs without being interrupted by the goblin, yet the looms constantly generate "collect webs" tasks for webs which are physically inaccessible (but are still included within a burrow), resulting in my weavers spamming "cancels Collect Webs: Needs 10 undisturbed thread".

I used the exact same setup back in 0.28.181.40d and didn't have this problem.
TagsNo tags attached.

Relationships

child of 0002469 resolvedToady One If burrow includes unrevealed webs, dwarves try to collect the (inaccessible) webs and spam cancellations 

Activities

Quietust

2010-11-07 19:12

reporter   ~0013668

Last edited: 2010-11-08 06:22

Upon closer examination, "Collect Webs" tasks only seem to get added if the webs are located inside the same burrow as the loom; if the loom isn't inside any burrow, auto-collect webs will never do anything.

Back in 0.28.181.40d and earlier, web collection only happened if the webs were actually accessible from the loom.

Issue History

Date Modified Username Field Change
2010-11-07 18:51 Quietust New Issue
2010-11-07 18:56 Logical2u Relationship added child of 0002469
2010-11-07 19:12 Quietust Note Added: 0013668
2010-11-08 06:19 Quietust Note Edited: 0013668
2010-11-08 06:22 Quietust Note Edited: 0013668
2014-07-31 12:52 user11 Assigned To => user11
2014-07-31 12:52 user11 Status new => acknowledged
2014-08-01 13:40 Toady One Status acknowledged => resolved
2014-08-01 13:40 Toady One Fixed in Version => Next Version
2014-08-01 13:40 Toady One Resolution open => fixed
2014-08-01 13:40 Toady One Assigned To user11 => Toady One