Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
0007440Dwarf FortressAdventure Mode -- AIpublic2014-07-17 20:592014-08-19 10:17
resolvedunable to reproduce 
0007440: Forgotten beasts found in ruined forts are not hostile, do not respond to attacks
Sought out a forgotten beast in a ruined fortress, in order to kill it and reclaim the ruin in question. Forgotten beast did not attack on sight, sitting motionless in one of the forge rooms. Attacking it (whether the PC or a follower struck first) caused no response.

Notably, my adventurer declared himself lord of the (dwarven) site before engaging the FB.
Linked save has adventurer with two companions right next to the passive beast.
Save at: http://dffd.wimbli.com/file.php?id=9046 [^]
No tags attached.
related to 0006547resolved Toady One Wolves passive in adventure mode. 
Issue History
2014-07-17 20:59FlarpNew Issue
2014-07-18 08:53FootkerchiefRelationship addedrelated to 0006547
2014-07-18 10:57horsefeathersNote Added: 0026881
2014-07-18 19:55FlarpNote Added: 0026926
2014-08-19 07:55smjjamesNote Added: 0029297
2014-08-19 08:07smjjamesNote Edited: 0029297bug_revision_view_page.php?bugnote_id=0029297#r11252
2014-08-19 08:42TalvienoNote Added: 0029303
2014-08-19 10:17FootkerchiefNote Added: 0029311
2014-08-19 10:17FootkerchiefStatusnew => resolved
2014-08-19 10:17FootkerchiefResolutionopen => unable to reproduce
2014-08-19 10:17FootkerchiefAssigned To => Footkerchief

2014-07-18 10:57   
I find that most things in adventure mode are not hostile to you.
2014-07-18 19:55   
Update: trying the save again, that forgotten beast became hostile when No Quarter was triggered, possibly by stepping into its line of sight?
2014-08-19 07:55   
(edited on: 2014-08-19 08:07)
Either this might be fixed or it was just because the one I encountered was a firespitter. Didn't save that game, but then again, I was on fire and fleeing (and bleeding).

2014-08-19 08:42   
Perhaps related to 0006666?
2014-08-19 10:17   
Talvieno, they're related through 0006547.

It sounds like this didn't reproduce. Please reopen this report or PM a manager on the forums if this problem is still present in 0.40.09+.