Template talk:CreatureInfo 40d

Just wondering if there's any rationale behind the ordering of the butchering returns. Ordering by descending number of expected units obtained (i.e. bones, chunks and meat; then fat; then skin and skull) seems to me to look more ordered. Also, any reason why skin is Yes/No and not a number? --Mechturk 23:27, 4 November 2007 (EST)

You can have multiple skulls, but only one skin. The categories are listed in an arbitrary order. You can't dynamically order them based on the numbers in the template design. Feel free to reorder the list if you think you can improve it. Later on I or someone else should include size and value info as well as room for special attributes to be listed. I didn't do it making the template because Wikimarkup's table structure is greek to me. I made this by copying the Template:alloy page, and got sick of messing with it. --Ikkonoishi 15:40, 5 November 2007 (EST)

Ah. Nice. From my brief foray into hunting and looking into the raws, it appears that the bone, chunks and meat values are equal to the SIZE specified in the raws, and the fat values are specified in FAT. Skin is present unless NOSKIN appears in the creature descriptor, while the number of skulls should come from the body descriptor, a few of them, such as BODY:HUMANOID_2HEAD having more than one. In the vast majority of cases, SIZE > FAT, and there is only one skull. I figure that having the SIZE related attributes at the top followed by fat, skulls and skin should look, errr... prettier? Since the numbers will be in descending order. I'm not sure this would be the case with one or two of the more fantastic creatures, but it should be true most of the time. --Mechturk 16:11, 5 November 2007 (EST)