Template talk:Loot variant table row

From Guild Wars 2 Wiki
Jump to navigationJump to search

could shave some nodes off by putting {{NAMESPACE}}{{#ifeq:{{#show:{{PAGENAME}}|?Is historical}}|true|+}} into a variable in the header template. -Chieftain AlexUser Chieftain Alex sig.png 20:45, 27 June 2014 (UTC)

these pages shouldn't use the Infobox tbh.--Relyk ~ talk < 00:21, 28 June 2014 (UTC)
Why the hell not? It shows the icon and a screenshot. —Dr Ishmael User Dr ishmael Diablo the chicken.png 00:26, 28 June 2014 (UTC)
For setting the properties as the infobox properties get queried. I would stick general information in the table header.--Relyk ~ talk < 01:54, 28 June 2014 (UTC)

Has {{#var:ivt_supertype}} type - fails when {{Item variant table header}} hasn't been used. I'd propose that we make the infobox spit out the supertype as a variable + then this will work properly. -Chieftain AlexUser Chieftain Alex sig.png 23:43, 28 June 2014 (UTC)

Should define Property:Has item type for handling the supertype instead of making a switch statement and variable on every page that needs it.--Relyk ~ talk < 00:34, 29 June 2014 (UTC)

How to specify custom values?[edit]

How to specify custom values? Might Country Coat [&AgFFAAAA] is 24 Defense and 5 Power, which is not the level 0 values of 23 defense and 4 power. --BryghtShadow (talk) 03:13, 14 November 2015 (UTC)

According to the API, 23/4 is correct--Relyk ~ talk < 03:19, 14 November 2015 (UTC)
Srsly Relyk? Looks like 24/5 to me. And you really should be using v2 anyway.
Anyway, fixed by adding the somewhat-standard | statlevel = parameter. —Dr Ishmael User Dr ishmael Diablo the chicken.png 05:46, 14 November 2015 (UTC)
don't mind me, just move along--Relyk ~ talk < 06:15, 14 November 2015 (UTC)
Thank you. This will be useful for a few items that have boosted levels. --BryghtShadow (talk) 16:00, 14 November 2015 (UTC)

Showing the name parameter in the table[edit]

As per Talk:Amulet_(loot), is there any particular reason why the in-game name of the item cannot be shown? Is it possible to make a switch in the header to allow this without breaking things? G R E E N E R 19:05, 31 July 2016 (UTC)

So are you looking for a separate column, or just something like Dire in the prefix column? -Chieftain AlexUser Chieftain Alex sig.png 19:30, 31 July 2016 (UTC)
I had nothing special in mind (skipping out right now for a client). The contributor on that talk page pointed out that the name for the items don't always match the page name, so I was thinking that where such a mismatch occurred, the name could be shown.
Since Anet suppresses prefixes and suffixes at its whim, perhaps just a column for the name parameter would be easiest*. *Note: I have no idea what would be easiest G R E E N E R 19:45, 31 July 2016 (UTC)

Trading values[edit]

It seems that this template doesn't show the trading post values of the listed items. For example, look at Orrian Longsword. At the time of writing, the cost of lvl 80 exotic sword (Dire Orrian Longsword of Rage) is Gold coin 20 Silver coin 92 Copper coin. This isn't shown in the table, and I can only guess whether it's a bug in the template or temporary problem with obtaining TP data. Could you please check? --109.252.107.24 19:20, 1 August 2017 (UTC)

This template doesn't even try getting the TP values. -Chieftain AlexUser Chieftain Alex sig.png 19:25, 1 August 2017 (UTC)
As to why we didn't add it to this template, as far as I remember we limited the TP widget to 200 results, and sometimes there's probably more than 200 equipment entries on one page. -Chieftain AlexUser Chieftain Alex sig.png 20:43, 1 August 2017 (UTC)
OK, thanks for this answer, but please understand too, it looks more like a technical limitation due to some particular long lists, not a logical reason why for some tradeable items their TP price is shown in Wiki, while for some others isn't. I assumed that this template potentially could show the TP data because of this phrase:
Set to y if all variants are bound on acquire. This will hide the external links to trading post tracking sites.
Anyway I hope that such limitations have a chance to be less strict in the future :-) --109.252.107.24 21:58, 1 August 2017 (UTC)