Template talk:Craft table

some missing entries

querying Destroyer Greatsword

{{#ask: [[Has canonical name::Destroyer Greatsword]]
 | ?Has game icon
 | ?Has canonical name
 | ?Has weapon type
 | ?Has weapon strength
 | ?Has item rarity
 | ?Has equipment prefix
 | ?Gives attribute bonus
 | ?Has upgrade component
}}

I know from the page that the strength is 995 – 1100; the rarity is exotic; and that the upgrade component slot is unused. a) I think we should add these to the subobjects. b) surely the canonical name would be "Apothecary's Destroyer Greatsword". (also, my query was pretty lame, but shouldn't equip prefix display here?) -Chieftain Alex 11:42, 16 September 2013 (UTC)

Your query condition [[Has canonical name::Destroyer Greatsword]] shouldn't be returning any results, because that doesn't match the canonical name of any item or recipe. I had omitted the prefix from the recipe subobject's canonical name property for some reason, so I fixed that. The single result that's left is because the infobox on the page is still setting properties, and I'm not sure how we want to deal with that.

Here's the query you were looking for:

	Has game icon	Has canonical name	Has weapon type	Has weapon strength	Has item rarity	Has equipment prefix	Has upgrade component
Destroyer Greatsword		Destroyer Greatsword	Greatsword		Exotic
Destroyer Greatsword (skin)		Destroyer Greatsword
Destroyer Greatsword#itemct1		Apothecary's Destroyer Greatsword	Greatsword	995 (1,100)	Exotic	apothecary
Destroyer Greatsword#itemct2		Assassin's Destroyer Greatsword	Greatsword	995 (1,100)	Exotic	assassin
Destroyer Greatsword#itemct3		Berserker's Destroyer Greatsword	Greatsword	995 (1,100)	Exotic	berserker
Destroyer Greatsword#itemct4		Carrion Destroyer Greatsword	Greatsword	995 (1,100)	Exotic	carrion
Destroyer Greatsword#itemct5		Cleric's Destroyer Greatsword	Greatsword	995 (1,100)	Exotic	cleric
Destroyer Greatsword#itemct6		Knight's Destroyer Greatsword	Greatsword	995 (1,100)	Exotic	knight
Destroyer Greatsword#itemct7		Rampager's Destroyer Greatsword	Greatsword	995 (1,100)	Exotic	rampager
Destroyer Greatsword#itemct8		Sentinel's Destroyer Greatsword	Greatsword	995 (1,100)	Exotic	sentinel
Destroyer Greatsword#itemct9		Valkyrie Destroyer Greatsword	Greatsword	995 (1,100)	Exotic	valkyrie
Destroyer Greatsword#recipe1		Apothecary's Destroyer Greatsword
Destroyer Greatsword#recipe2		Assassin's Destroyer Greatsword
Destroyer Greatsword#recipe3		Berserker's Destroyer Greatsword
Destroyer Greatsword#recipe4		Carrion Destroyer Greatsword
Destroyer Greatsword#recipe5		Cleric's Destroyer Greatsword
Destroyer Greatsword#recipe6		Knight's Destroyer Greatsword
Destroyer Greatsword#recipe7		Rampager's Destroyer Greatsword
Destroyer Greatsword#recipe8		Sentinel's Destroyer Greatsword
Destroyer Greatsword#recipe9		Valkyrie Destroyer Greatsword

—Dr Ishmael 12:40, 16 September 2013 (UTC)

Transcluding to crafting overview pages

Can the table be wrapped in <includeonly> tags so that it can be transcluded to crafting overview pages, such as Artificer/Novice Recipes? Ideally what I'd want to do is something like:

==Scepters==
''Main article: [[Crude scepter]]''
{{:Crude scepter}}
==Focuses==
''Main article: [[Crude scepter]]''
{{:Crude scepter}}
==Staffs==
''Main article: [[Crude scepter]]''
{{:Crude scepter}}
==Tridents==
''Main article: [[Crude scepter]]''
{{:Crude scepter}}

and that would give all the info that would be needed on that page. Is that something that would be a good idea? Psycho Robot (talk) 00:09, 19 September 2013 (UTC)

NOOOOOOOOOooooooo... that's not what you want at all. This template is setting a whole bunch of SMW subobjects, and you do NOT want to have the same thing in two places as that would duplicate all the subobjects. This template sets semantic properties based on input data.

For displaying semantic data based on querying the properties, you want to look at Category:Recipe formatting templates. Your example above would be achieved with {{recipe table|type=<weapon type>}} (don't have to specify discipline because all weapon recipes are distinct to a single discipline). —Dr Ishmael 00:15, 19 September 2013 (UTC)

Ok I figured out why I felt like that wouldn't work right - the individual pages were still out there meaning that things were being listed twice and making the resulting seem too long to be useful. Now I fixed it and its much more manageable. Now the only issue I see is that the simple variants aren't identified and appear in the third position on the table instead of the first position which would be logical. Is there any way that can be easily fixed, or should we just deal with it? Psycho Robot (talk) 00:37, 19 September 2013 (UTC)

I don't know of an easy way to do that, no. Even if we added "(Simple)" to the name, that would actually force it to sort last. —Dr Ishmael 02:00, 19 September 2013 (UTC)

Armor labeled as weapons

As one can see in Draconic Helm and in all other crafted armor tables, the first column identifies the piece of armor as a weapon. I peeked in the template and the term "weapon" is manually entered and isn't part of any switch. You screwed up big this time, ishmael. Psycho Robot (talk) 17:38, 12 October 2013 (UTC)

panic over, fixed. (swapped the column header for {{#var:ct_supertype}}) -Chieftain Alex 17:43, 12 October 2013 (UTC)

Sorting by trading post price

Would love it if there was an option to be able to sort the trading post price column, my use-case for this was figuring out the cheapest variant to buy to unlock an armor/weapon skin to add to wardrobe (but default it to sorted alphabetically/what it is currently since I think people would only be interested in crafting "one" specific variant). Would possibly need to split the trading post price column into buy and sell price columns. --ItVictor (talk) 00:19, 11 February 2024 (UTC)