Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
0001933Dwarf FortressGeneralpublic2010-05-17 19:512010-06-09 06:45
normalminorhave not tried
0001933: Farmer mysteriously died
All of a sudden, I got an alert that a farmer had died, so I zoomed to location and she was lying dead in a bedroom, missing an upper body and reportedly having a medical history of severe blood loss. There were no battle reports, she couldn't have fallen down a channel. This for was barely a couple of months old. It happened not long after a migrant wave, but the deceased was of my original embark 7.

I really couldn't think of anything that could have actually happened to her.
No tags attached.
duplicate of 0000190closed Toady One Adventurers and dwarves melt in rain/water 
Issue History
2010-05-17 19:51MilkbotNew Issue
2010-05-17 20:20CoriantumrNote Added: 0006916
2010-05-17 20:45FootkerchiefNote Added: 0006919
2010-05-17 20:45FootkerchiefIssue Monitored: Footkerchief
2010-05-17 22:01MilkbotNote Added: 0006925
2010-05-17 23:20FootkerchiefNote Added: 0006927
2010-05-17 23:21FootkerchiefRelationship addedchild of 0000190
2010-05-18 17:34CoriantumrNote Added: 0006984
2010-05-19 03:58MilkbotNote Added: 0007010
2010-05-20 01:55MilkbotNote Added: 0007053
2010-05-30 12:59FirehoundNote Added: 0007495
2010-05-30 14:47MrWigglesNote Added: 0007499
2010-05-30 21:50tatterdemalianNote Added: 0007504
2010-05-31 00:23FootkerchiefNote Added: 0007507
2010-05-31 00:23FootkerchiefRelationship replacedduplicate of 0000190
2010-05-31 00:23FootkerchiefStatusnew => resolved
2010-05-31 00:23FootkerchiefResolutionopen => duplicate
2010-05-31 00:23FootkerchiefAssigned To => Footkerchief
2010-06-09 06:45Toady OneStatusresolved => closed

2010-05-17 20:20   
I had this same problem. I suddenly got the "xDwarfx, Farmer has bled to death." I zoomed to the location and they were lying dead at the end of a blood trail about a dozen tiles long. There were no combat reports, or even any creatures on the map besides my dwarves to have fought with.

It looked exactly like the (supposedly fixed) rain/melting bug... since it had been raining only moments before my farmer died. The map I was playing on was warm enough to have evaporated nearly all of the non flowing water by the beginning of the first summer.
2010-05-17 20:45   
Did you have any failed mandates? Check the [z] -> Justice screen to make sure.

It's very possible that there are still temperature issues, or that the fix even introduced new ones.
2010-05-17 22:01   
Not a one, the fort had just been going for a couple of months. No nobles, no siegers, I couldn't think of anything that could cause it.
2010-05-17 23:20   
Hmm... yeah, we can probably chalk this one up to temperature. It might be helpful if you upload the save to http://dffd.wimbli.com/. [^]
2010-05-18 17:34   
No ... no failed mandates, the fort was only a couple months old. Unfortunately I abandoned the fortress right after this happened ... remembering a moment later that the save might be handy.
2010-05-19 03:58   
http://dffd.wimbli.com/file.php?id=2368 [^]

This is the same save as the warm stone brook one as the farmer died in the same fort. I hope it helps :)
2010-05-20 01:55   
Yes, I'm certain this is related to the rain. Commented on the parent issue.

So many lives lost....oh god the blood, there was so much blood...
2010-05-30 12:59   
I had someone self-destruct
2010-05-30 14:47   
Like a push lever down then kaboom?
2010-05-30 21:50   
Well, it seems the issue hasn't been resolved yet... I embarked into an warm rainy climate with a river (forest biome), and two years on, not one single fish... and now, not even any turtles. It seems the "fix" simply ensured turtles would boil away from the heat, instead of making the rivers and ponds livable.

Also, on activating the [d]esignate -> [d]ig command, the flowing water in the river shows the "warm stone" symbol (yellow sunburst on a red background), instead of remaining a number or showing the "damp stone" symbol. Either it's an interesting glitch, or the river is as hot as magma now.
2010-05-31 00:23   
Well, it seems the issue hasn't been resolved yet...

See Toady's comment at 0000190:0007125. 31.05 should have a more complete fix for the problem.

I'm resolving this report as a duplicate of 0000190.