View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000776 | Dwarf Fortress | Dwarf Mode -- Interface, Announcements: Message Spam | public | 2010-04-07 23:09 | 2010-12-11 08:59 |
| Reporter | DCBomB | Assigned To | Toady One | ||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | closed | Resolution | duplicate | ||
| Product Version | 0.31.01 | ||||
| Summary | 0000776: Butcher cancels Butcher an Animal: Could not find path. | ||||
| Description | It seems that if there's an object related to a job in an unrevealed area that shows up on the stock screen (such as a butcherable corpse that is 45 layers deep when only 36 are currently visible) dwarves are unable to path to the object but would still very much like to try. | ||||
| Steps To Reproduce | So here's what I did... I embarked on a cave that goes down to an expansive underground cavern that is about 57 layers deep (explored in adventurer first.) I can only see down around 27 layers, the rest being unrevealed. First caravan (dwarven) embarks... and heads down into the cave. They pass the threshold into the unrevealed darkness and they dissapear from the unit list (I watched this happen explicitly.) A few minutes later one of my butchers spergs out trying to reach a "Large Rat mutilated corpse" which I can only imagine was slain by the caravan and is sitting down in the darkness waiting to be butchered. The Large Rat is on the Unit List as Deceased (I can't recall if he was there immediately before he died, but I have seen the rat wander around before on the lowest visible layer. The corpse does however show up on the stocks screen, and is on layer -45, which is nine layers below what I can see. | ||||
| Tags | No tags attached. | ||||
|
|
This has also been happening for gathering spider webs since I first built a loom here. |
|
|
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. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-04-07 23:09 | DCBomB | New Issue | |
| 2010-04-07 23:13 | DCBomB | Note Added: 0001959 | |
| 2010-04-07 23:14 | DCBomB | Note Edited: 0001959 | |
| 2010-04-08 00:21 |
|
Relationship added | child of 0000018 |
| 2010-04-11 18:35 |
|
Tag Attached: Still Present in 31.03? | |
| 2010-04-12 12:36 |
|
Note Added: 0003098 | |
| 2010-04-12 12:36 |
|
Status | new => resolved |
| 2010-04-12 12:36 |
|
Fixed in Version | => 0.31.03 |
| 2010-04-12 12:36 |
|
Resolution | open => fixed |
| 2010-04-12 12:36 |
|
Assigned To | => user6 |
| 2010-04-12 12:40 |
|
Status | resolved => assigned |
| 2010-04-12 12:40 |
|
Assigned To | user6 => Toady One |
| 2010-04-12 12:41 |
|
Status | assigned => resolved |
| 2010-04-12 13:12 |
|
Status | resolved => assigned |
| 2010-04-12 13:13 |
|
Status | assigned => resolved |
| 2010-04-12 13:13 |
|
Fixed in Version | 0.31.03 => |
| 2010-04-12 13:13 |
|
Resolution | fixed => duplicate |
| 2010-06-04 10:06 |
|
Tag Renamed | Still Present in 31.03? => Fixed in 31.03? |
| 2010-06-09 06:46 | Toady One | Status | resolved => closed |
| 2010-12-11 08:59 |
|
Tag Detached: Fixed in 31.03? |
