Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
0002348Dwarf FortressCombat -- Stuck-inspublic2010-06-15 16:462010-06-15 17:37
highmajorhave not tried
Windows7, don't think it mattersWindows77
0002348: Ocean Steam Titan unkillable, impotent
Basically a ocean titan showed up. He has a steam area of effect thing lagging things out, at first a human spearman showed up engaged, clipped off two wings, but no other damage. 5 other npc dwarves showed up.. then a hydra which they instantly vaporized.... though this caused a second "bug" where the one that dealt the killing blow keeps renaming his sword every 10sec or so - causing the game to pause.

issue 0000001 - unkillable titan not killing anyone aoe effect also causing major lag

issue 0000002 - renaming of short sword causes game pause often.

I am getting someone to dfhack through it atm.. but this kind of thing seems like a problem to me. I could have dealt with it had the titan just wiped everyone out, or if he had been contained by the npcs and not having the game pause every 10sec, centering focus on it.

http://dffd.wimbli.com/file.php?id=2521 [^]
http://dffd.wimbli.com/file.php?id=2521 [^]
http://dffd.wimbli.com/file.php?id=2521 [^]
No tags attached.
duplicate of 0000033resolved Toady One Bronze colossus, skeletal creatures, fleshballs, and others are impossible to kill 
Issue History
2010-06-15 16:46SilverLightNew Issue
2010-06-15 16:47SilverLightNote Added: 0008537
2010-06-15 17:23DwarfuNote Added: 0008539
2010-06-15 17:37Logical2uNote Added: 0008540
2010-06-15 17:37Logical2uRelationship addedduplicate of 0000033
2010-06-15 17:37Logical2uStatusnew => resolved
2010-06-15 17:37Logical2uResolutionopen => duplicate
2010-06-15 17:37Logical2uAssigned To => Logical2u

2010-06-15 16:47   
Sorry for the unintentional links to old issue in this database did not realise typing issue 0000001 and issue 0000002 would result in that - it was not my intention, I doubt those closed issues are related so do not click on the links.
2010-06-15 17:23   
More like:

0000667, resolved for next release (0.31.07);


2010-06-15 17:37   
They aren't, but this one is.