View Issue Details

IDProjectCategoryView StatusLast Update
0000770Dwarf FortressDwarf Mode -- Jobs, Healthcarepublic2014-01-27 10:50
ReporterLightning4 Assigned Touser6 
PrioritynormalSeverityminorReproducibilityrandom
Status resolvedResolutionduplicate 
Product Version0.31.01 
Summary0000770: Resting dwarves tasked to recover wounded
DescriptionTwo dwarves are stranded outside of my fortress as the dwarf who is tasked to "recover wounded" has also been injured in the same attack and is resting, but not losing the jobs on the task screen. Nobody else can collect them.

It doesn't seem these stranded dwarves are eligible for food or water, they could potentially die if the dwarf tasked to recover them has been severely injured.
Additional InformationCould be partly related to the "Cancelled rest: Interrupted by xxxx" bug caused by creatures that should not be. I had two goblin pikemen in cages that caused my military to spam me with that until I atom smashed the cages. Everyone but those two went off to rest. The dwarf tasked to recover wounded, might have gotten the task during this period, but not certain.
TagsNo tags attached.

Relationships

duplicate of 0000973 resolvedToady One OVERWROTE JOB: Pickup Equipment BY Rest 
parent of 0001057 resolveduser6 wounded dwarf gets stuck with "recover wounded" job even after death 

Activities

user6

2010-04-08 04:06

  ~0001993

Did you happen to get an "OVERWROTE JOB" announcement? Try searching your gamelog.txt for that phrase.

Lightning4

2010-04-08 04:44

reporter   ~0001994

Last edited: 2010-04-08 04:58

As a matter of fact, yes. Recover Wounded was overwritten by Rest in two instances, and two dwarves were sitting out there without attempting to move.

Then miscellaneous tasks were spam-overwritten once I atomized the offending goblins, Rest also replacing them.

As an update, the dwarf that is shown as tasked to recover them is moving about already, but has not made an effort to recover the remaining dwarf.

Bug? Maybe this should be bumped up to major seeing as how it's invariably fatal for the victims, unless it's something that there's a workaround for.

Toady One

2010-06-12 02:04

administrator   ~0008183

The job overwrite could very well have caused this, but it's not clear. I'm going to leave this open until we're more sure or another reason is found.

user6

2014-01-27 10:50

  ~0024392

Assuming this is the OVERWROTE JOB thing.

Issue History

Date Modified Username Field Change
2010-04-07 22:02 Lightning4 New Issue
2010-04-08 04:06 user6 Note Added: 0001993
2010-04-08 04:44 Lightning4 Note Added: 0001994
2010-04-08 04:45 Lightning4 Note Edited: 0001994
2010-04-08 04:47 Lightning4 Note Edited: 0001994
2010-04-08 04:57 Lightning4 Note Edited: 0001994
2010-04-08 04:58 Lightning4 Note Edited: 0001994
2010-04-12 13:54 user6 Relationship added parent of 0001057
2010-04-26 17:30 user6 Relationship added parent of 0001167
2010-04-26 17:49 user6 Relationship added related to 0000973
2010-06-12 02:04 Toady One Note Added: 0008183
2010-06-12 02:04 Toady One Assigned To => Toady One
2010-06-12 02:04 Toady One Status new => acknowledged
2011-04-14 12:59 user6 Relationship deleted parent of 0001167
2011-04-14 12:59 user6 Relationship added related to 0000094
2014-01-27 10:50 user6 Note Added: 0024392
2014-01-27 10:50 user6 Relationship replaced duplicate of 0000973
2014-01-27 10:50 user6 Status acknowledged => resolved
2014-01-27 10:50 user6 Resolution open => duplicate
2014-01-27 10:50 user6 Assigned To Toady One => user6
2014-01-27 10:50 user6 Relationship deleted related to 0000094