|Anonymous | Login | Signup for a new account||2020-07-05 18:47 PDT|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006053||Dwarf Fortress||Dwarf Mode -- Items||public||2012-06-24 20:08||2012-06-25 18:02|
|Platform||Custom Built PC||OS||Windows 7 Home||OS Version||Premium 64-bit|
|Target Version||Fixed in Version|
|Summary||0006053: Masterwork wooden bolts cause art defacement penalties when broken during hunting.|
|Description||Masterwork wooden bolts (confirmed, only wooden craft made so far, and the lone woodcrafter had created nothing else other than those bolts, when destroyed through normal wear and tear, cause art defacement thoughts to the creator of those bolts. The effect appears to be cumulative, and often leads to the crafter going insane and having to be put down every few hunts. Can also often lead to the dreaded tantrum spiral (If not for this, I would of listed it as a minor bug instead of a major one)|
|Steps To Reproduce||Set one woodcrafter with only the task of woodcrafting.|
Provide wood, set crafting facility to create bolts.
Let hunters use those bolts for hunting (possibly recruits as well, have not tested that route yet.)
Watch for art defacement thoughts in the woodcrafter once he/she starts producing masterwork bolts.
|Tags||No tags attached.|
|Can you rule out 0003169 as the cause?|
Doh, sorry, I didn't even think of stuck in bolts as the potential cause. I know I've been getting a few Giant Kea's successfully getting away with items, but let me see what I can find if I haven't lost the more specific logs from exiting the game.
Well, one masterpiece message was not associated with any creatures leaving the map with items messages, so it may have been from a break shot or a lodged in shot, no way to determine it. However, I did find that 3 full stacks of masterworks were also stolen by those foolish Kea's, listed as standard 25 stacks, so that probably explains the speed of the tantrum spiral issue, so I may have overestimated the severeity of the issue. I have no way to rule out 0003169 without a way to examine the code that caused the masterpiece message, so I suppose this one could be cleansed or merged into the previous issue.
Sometimes it's hard to notice specific announcements when the list is spammed with interrupted by "monsterx" announcements, I should have noticed them prior to placing the post.
|No problem. Okay, we'll chalk it up to 0003169, but please reopen this if evidence surfaces to the contrary.|
|2012-06-24 20:08||Thoranius||New Issue|
|2012-06-24 22:18||Footkerchief||Note Added: 0023105|
|2012-06-24 22:18||Footkerchief||Tag Attached: AWAITING UPDATE|
|2012-06-24 22:18||Footkerchief||Relationship added||duplicate of 0003169|
|2012-06-25 13:16||Thoranius||Note Added: 0023108|
|2012-06-25 18:02||Footkerchief||Note Added: 0023110|
|2012-06-25 18:02||Footkerchief||Status||new => resolved|
|2012-06-25 18:02||Footkerchief||Resolution||open => duplicate|
|2012-06-25 18:02||Footkerchief||Assigned To||=> Footkerchief|
|2012-06-25 18:02||Footkerchief||Tag Detached: AWAITING UPDATE|
|Copyright © 2000 - 2010 MantisBT Group|