Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
0003898Dwarf FortressReactionspublic2011-01-18 09:102014-07-31 10:57
Toady One 
WindowsWindows 7
0003898: Entire Bone Stacks are used in Reactions instead of a single Bone
For several pre-scripted reactions, as well as custom reactions (such as for a custom building) there are problems when using bone as a material. In specific the problem is that an entire stack of bone will be utilized instead of a single bone.

Crafting a bone bow, at the bowyer, is an example of one of the reactions that seems to work properly at the moment. However for all other custom reactions I have tried, an entire stack of bone is used up as the Reagent in production.

The item is still produced out of the reaction, but the entire stack is depleted in its construction.
Slaughter/Butcher some creature to get some bone.
Use the following reaction information as a custom reaction.

[NAME:Make bone Blocks]

Attempted to even use something like [PRODUCT_DIMENSION:1] to reduce the amount of material utilized, to no avail.

A bone block would be produced correctly with the following reaction. However if you had a stack of 12 cow bones, it would make a single block just as if you had access to only a single cow bone but 'waste' 11 bones in the process.
This problem seems endemic regardless of what is being made in the PRODUCT line. Attempts with other product types (chair, armor, door, etc.) result in the same stack use. For Reagent purposes I would guess that a stack of bone looks just like a single bone for material purposes.

Tried adding the following to the bone material template:

And then changing the reagent above to something like this:

Did not fix the issue of utilizing a whole stack of the substance.
body parts, bones, dwarf fortress mode, reactions, workshops
related to 0002011resolved Toady One Decorating with bone/horn uses whole stack 
has duplicate 0006727resolved lethosor Crafting certain items from bone uses entire stack rather than individual bones. 
child of 0000808resolved Toady One Processing Raw Turtles only makes one shell per stack, and other stack size issues 
Issue History
2011-01-18 09:10Alluvian_Est-EndratiNew Issue
2011-01-18 09:10Alluvian_Est-EndratiTag Attached: bone
2011-01-18 09:11Alluvian_Est-EndratiTag Attached: body parts
2011-01-18 09:11Alluvian_Est-EndratiTag Attached: bones
2011-01-18 09:11Alluvian_Est-EndratiTag Attached: reactions
2011-01-18 09:12Alluvian_Est-EndratiTag Attached: dwarf fortress mode
2011-01-18 09:12Alluvian_Est-EndratiTag Attached: stock
2011-01-18 09:12Alluvian_Est-EndratiTag Attached: stockpiles
2011-01-18 09:12Alluvian_Est-EndratiTag Attached: workshops
2011-01-18 12:34Logical2uRelationship addedchild of 0002011
2011-01-18 19:21QuietustNote Added: 0014904
2012-02-26 11:47BuglistIssue Monitored: Buglist
2012-02-27 06:39FootkerchiefSummaryEntire Bone Statcks are used in Reactions instead of a single Bone => Entire Bone Stacks are used in Reactions instead of a single Bone
2013-12-07 05:14ThundercraftIssue Monitored: Thundercraft
2014-07-08 15:49lethosorRelationship addedhas duplicate 0006727
2014-07-08 15:52lethosorNote Added: 0025168
2014-07-21 05:51LiensNote Added: 0027123
2014-07-21 05:57lethosorTag Detached: stock
2014-07-21 05:57lethosorTag Detached: stockpiles
2014-07-21 05:58lethosorTag Detached: bone
2014-07-27 21:34int_uaIssue Monitored: int_ua
2014-07-30 12:12Toady OneRelationship addedchild of 0000808
2014-07-30 12:12Toady OneRelationship replacedrelated to 0002011
2014-07-31 10:57Toady OneStatusnew => resolved
2014-07-31 10:57Toady OneFixed in Version => Next Version
2014-07-31 10:57Toady OneResolutionopen => fixed
2014-07-31 10:57Toady OneAssigned To => Toady One
2016-07-22 04:18park66665Issue Monitored: park66665
2017-08-02 09:33park66665Issue End Monitor: park66665

2011-01-18 19:21   
The "BONE:NONE:NONE:NONE" in the reagent is technically incorrect, since BONE is not an item token (see http://df.magmawiki.com/index.php/Item_token [^] for a list) - you should either be using NONE (which is probably what it was using anyways) or possibly CORPSE/CORPSEPIECE (which might not work as expected).
2014-07-08 15:52   
Still a problem in 0.40.01, according to 0006727
2014-07-21 05:51   
Confirming still an issue in 0.40.03