Editing DF2014 Talk:Gem

The article currently claims that "Gem stockpiles cannot be set to permit or restrict cabochons, so dwarfs won't recognize stockpile settings when storing them. This may lead to odd behavior, such as dwarfs moving cabochons from cut gem stockpiles to rough gem stockpiles, regardless of established stockpile/workshop links." Given that cabochons are nothing more than '''cut gems with an assigned shape''', I don't see how this could be a thing - does this actually happen? --[[User:Quietust|Quietust]] ([[User talk:Quietust|talk]]) 13:02, 20 August 2014 (UTC)
@@ Line 1: / Line 1: @@
 The article currently claims that "Gem stockpiles cannot be set to permit or restrict cabochons, so dwarfs won't recognize stockpile settings when storing them. This may lead to odd behavior, such as dwarfs moving cabochons from cut gem stockpiles to rough gem stockpiles, regardless of established stockpile/workshop links." Given that cabochons are nothing more than '''cut gems with an assigned shape''', I don't see how this could be a thing - does this actually happen? --[[User:Quietust|Quietust]] ([[User talk:Quietust|talk]]) 13:02, 20 August 2014 (UTC)
-:{{bugl|6444}} looks like what this is referring to - I'm not exactly clear on what occurs, but it sounds like certain combinations of "Allow/Block all" end up controlling cabochons, despite them not being listed. &mdash;[[User:Lethosor|<span style="color:#074">Lethosor</span>]] ([[User talk:Lethosor|<span style="color:#092">talk</span>]]) 13:56, 20 August 2014 (UTC)
-::Both the note in the article and the bug description are misleading, since I'm pretty sure it only applies to '''stone''' cabochons and not '''gem''' cabochons (which would make sense, because the stone types are hidden from the stockpile menu but still get toggled with the Allow/Block All commands. --[[User:Quietust|Quietust]] ([[User talk:Quietust|talk]]) 15:01, 20 August 2014 (UTC)
-== Change in gem values? ==
-It seems that gem values changed at some point in time. In my embark (v 40.19) I found pipe opal (value 30 instead of 10), citrine (6 instead of 2) and tube agate (6 instead of 2). I just updated those ones and will do for the rest once I find them. If I'm mistaken, please respond and feel free to revert my changes. --[[User:Afghani84|Afghani84]] ([[User talk:Afghani84|talk]]) 20:19, 11 January 2015 (UTC)
-: There were no changes. The numbers given are the material ''multipliers'', not the values of raw stones. A raw gem has a base value of 3☼, so the 30☼ for a raw pipe opal (mul. 10) is the correct value as derived from the table. I'll revert.--[[User:Larix|Larix]] ([[User talk:Larix|talk]]) 21:25, 11 January 2015 (UTC)
-:: Thanks for clearing that up!--[[User:Afghani84|Afghani84]] ([[User talk:Afghani84|talk]]) 19:53, 12 January 2015 (UTC)
-== Large '''''cut''''' gem?? ==
-I've discovered a (-<<large rectangular peridot cabochon>>-) in my current dungeon. It's foreign/white, so not cut locally; probably bought from a trader without my noticing the "large" at the time. Shows up under large gems section of the stock screen. Not usable for encrusting. Glitch? Bug? Feature? v. 40.24 [[User:Urist McDorf|Urist McDorf]] ([[User talk:Urist McDorf|talk]]) 21:16, 20 February 2015 (UTC)
-== Crafts and large gems ==
-"Exactly 5% of all rough gems will be cut into a single craft or large gem (with 1 craft for every 8 large gems)"
-I'm not able to parse what this says, can someone who understands explain more clearly.<small>&ndash; [[template:unsigned|unsigned]] comment by [[User:Archie8300|Archie8300]]</small>
-:It is saying that the ratio of gem crafts to large gems is (1:8). So when a dwarf goes to cut a rough gem, there is a 95% chance that the job will produce a "cut gem", and a 5% chance it will produce something else. When not producing a cut gem, the job will instead produce either a "gem craft" (roughly 11% chance) or a "large gem" (roughly 89% chance). So the direct percentages would be:
-::cut gem: 95%
-::large gem: 4.4%
-::gem craft: 0.6%
-:--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 23:18, 3 April 2019 (UTC)