Template talk:Equipment variant table row

this is already covered with {{vendor table row}}--Relyk ~ talk < 04:35, 26 December 2013 (UTC)

That's for showing info about the shop, this is for recording info specific to the items including making subobjects for each item, attributes, stats, chat links, etc. While you could do that with the shop template, there's no reason to make it more complex. Psycho Robot (talk) 05:15, 26 December 2013 (UTC)

The vendor information is specific to the vendor, not the item. The correct approach is a generic template for generating item subobjects.--Relyk ~ talk < 10:21, 26 December 2013 (UTC)

I thought of that, but I didn't know how to make unused columns disappear. KOFF KOFF Psycho Robot (talk) 16:27, 26 December 2013 (UTC)

By defining so in the header like I did with vendor table templates. I don't think that's necessary for the general template because any group of items with the same name will have the same information/columns. I would put the upgrade slot with the attributes section like we do on item pages to avoid creating that column.--Relyk ~ talk < 17:53, 26 December 2013 (UTC)

finish the template before adding it to the mainspace please. -Chieftain Alex 08:36, 30 December 2013 (UTC)

I thought it was finished, I didn't realise it was broken when I added it to the aquabreather article. I was tired and saved and then went to bed. Psycho Robot (talk) 18:31, 30 December 2013 (UTC)

Light, Medium and heavy

I'd be a dick if I suggested that we allow this template to be used on pages with all three kinds of armor weight right.

It'd need another column (default to hidden) called "class". This value would be passed to the item stat lookup too. It would then require a patch to the {{armor infobox}} template to stop it screaming about brackets + allow you to either omit or set the class to "all" -Chieftain Alex 22:51, 12 March 2014 (UTC)

I assume this is only for items like Monocle? Are there any others like that? Psycho Robot (talk) 23:03, 12 March 2014 (UTC)

Gavbeorn Breather, Mad King's Shoulders + friends, Kohlopoi Aquabreather, Orsippus Aquabreather.. "Property:Instances of infobox" with 3/4/5 etc. -Chieftain Alex 23:15, 12 March 2014 (UTC)

I was hoping there would be fewer cases. Damn anet you hate us don't you. In light of that it sounds like a good idea to me. I'm not aware of any problems this could cause. Psycho Robot (talk) 23:28, 12 March 2014 (UTC)

PS Mad king's information is wrong. Each item has a different icon and appearance. Therefore I don't think they should be combined. Psycho Robot (talk) 23:30, 12 March 2014 (UTC)

Any chance for "Drops from" and "Drops" parameters ?

Looks like the champion loot bags of particular IDs always drop from the same enemies. If we added two multi-value paramentes in which we can put both specific NPCs and entire NPC types and factions, and another to put all drops each container may generate, we could use this to list every single variant of each champion loot bag on each champion bag page, which champions may drop each variant, and what items each champion loot bag may drop, and create lists that show both all shared drops across all variants, and particular drops exclusive to a certain ranges of variants. Such a thing could also be usable for other items and in other infoboxes, like to list what may drop a type of junk (it'll come in handy too put the 3 variants of Hoof in one page, for example). Allowing us to autocategorize drop tables this way. MithTalk 00:42, 15 September 2014 (UTC)

Small request

I saw that Template:Loot variant table row and Template:Craft table group had links to gw2spidy and gw2tp when the item was unbound. I wondered if someone could do the same with this template. For example, it would be helpful for Iron Ring or Sentinel variants of Iron Axe (loot). Tyndel (talk) 23:20, 22 June 2015 (UTC)

Not immediately obvious how ishmael added the bound check, I'll get around to it if someone else doesn't.--Relyk ~ talk < 01:12, 23 June 2015 (UTC)

Template:Loot variant table row uses {{#var:lvt_bound}} which is set in Template:Loot variant table header. Template:Craft table row uses [[Widget:TP prices]] such that when {{{account bound|}}}{{{requires sheet|}}}{{#var:ct_sheet}} is blank, it outputs class="gw2-tpprice" data-id="{{{item id}}}". I hope that helps. --BryghtShadow (talk) 02:00, 23 June 2015 (UTC)

Another small request

Can we add the 'stat level' parameter to this template? Invader's Ring has odd level requirements. Tyndel (talk) 13:53, 12 October 2015 (UTC)

Looks like it's already in the code {{{statlevel}}}, just not in the documentation. [edit] Never mind, it is in the docs - I only looked at the first part, but that's for the header, not for the row template. Why the heck is the header's documentation here anyway? That's just confusing. —Dr Ishmael 14:14, 12 October 2015 (UTC)

Thanks for the heads-up. I only tried out stat level, not statlevel. Tyndel (talk) 14:22, 12 October 2015 (UTC)

Historical

This template currently does not expose a subobject if the page is marked as historical. This however makes it impossible to find the item using the chat link search functionality. And just because an item is historical (making it no longer accessible), that doesn’t mean that people don’t have this still in their inventory. As an example, I still had Chests of the Crafter in my inventory, and I couldn’t find them via the chat link search.

I’m not sure what kind of properties should not be exposed if the item is historical, but maybe it should be just enough to inherit the “Is historical” property from the parent page. poke | talk 16:22, 10 January 2016 (UTC)

There are 8 pages which use this template and are historical. I don't think there will be an issue if we let it process the subobject. -Chieftain Alex 19:45, 10 January 2016 (UTC)

Heh, alright :D Thanks! poke | talk 19:50, 10 January 2016 (UTC)

Has item type default value

Hey, so with {{Drops table row}}, item types of subobjects will be displayed. For example Gilded Strongbox and Gilded Strongbox (exotic): the item type of the subobject is Shield, while it should be Container. It looks like there are more things to consider than just changing the default value of {{#var:type_ori|shield}} to check for the item type of the page instead, so my request is: can this be fixed?—Nefastu 01:33, 18 February 2017 (UTC)

I've gone ahead and changed the default value for the item type to check for the page's item type. —Nefastu 14:09, 27 February 2017 (UTC)

Item variant table row wasn't originally intended to be used on anything that isn't equippable.

Also, it's bad practise to query the current page with SMW, and this template is rife with self queries (it already had four). I'm not sure why shield was even set as the default anyway. -Chieftain Alex 18:23, 27 February 2017 (UTC)

Parameter for Bound?

It needs a parameter to indicate possible different bindings between variants, for example with Cavalier's Field Guide. - BuffsEverywhere (talk) 00:58, 25 December 2018 (UTC)