Template talk:Default item parameter

multi-value rarity

I've added support for multi-valued {rarity} input. I'm deliberately not documenting this because it should only be used in rare cases like the leveling weapon containers - the infobox is being used to document a group of items that are indistinguishable except for rarity and it doesn't make sense to split the page. I don't foresee any problems arising from annotating two rarities without explicitly linking them to the item IDs, but if any do, then I'll go back and split the pages. —Dr Ishmael 16:14, 23 September 2014 (UTC)

tradeable

What is the purpose of this parameter? Currently it does the same thing as 'bound', except in reverse, which means no item infobox currently features TP prices. Is this intended? Tyndel (talk) 05:04, 15 January 2015 (UTC)

I added this solely for Ominous Portent which is an item that is not account or soulbound (at least in-game it isn’t display—although the API reports it is) but cannot be traded (for the obvious reason that you can’t even keep it in your inventory). So it’s more a workaround to override the automatical detection based on the presence of id and bound. poke | talk 07:09, 15 January 2015 (UTC)

Pages such as Strawberry Cookie for example aren't showing TP links.. deliberate? -Chieftain Alex 08:21, 15 January 2015 (UTC)

I would use an exception with the 'Service' type to intercept the display of the TP price rather than making a new parameter (but that may be much harder than I can imagine). At least the current implementation should be changed so that 'tradable' is optional, with a default of 'yes'. Tyndel (talk) 08:37, 15 January 2015 (UTC)

Derp… Sorry about that, I messed up after trying to do it safe. Yes, of course, the tradable parameter is completely optional and its only use is to set it to “no”. poke | talk 17:45, 15 January 2015 (UTC)

Multiple collection entry

The collection parameter needs to be able to list multiple options: Mystic Staff is for Bo (achievement) and Yggdrasil (achievement). —Mora 15:39, 24 October 2015 (UTC)

Why the fraggle did Anet go and do that... bah. Done. —Dr Ishmael 19:06, 24 October 2015 (UTC)

"Is unique" property

Regarding this bit: {{#ifeq: {{{unique}}} | y | {{#set:Is unique::Y}} ;[[Unique]] :Yes | {{#set:Is unique::N}} }}

Problem #1: someone forgot to create Property:Is unique, so this isn't actually setting any properties at the moment. But let's assume I fix that. Does it make sense to set Is unique::N on tons of items? Since uniqueness is pretty rare, wouldn't it be nicer to set Is unique::Y on the few unique items and just leave it unset otherwise? -- Dagger (talk) 17:29, 27 December 2015 (UTC)

Good spot - it needed to use "=" signs instead of "::" (this has been broken for over 2 years without anyone noticing!). I've made the existing code functional without changing how it otherwise works. Regarding to setting "Is unique=N"; I don't think it will be useful either, but then again if you wanted to sort by "Is unique", then you need the field to be filled in on all the data anyway. -Chieftain Alex 18:21, 27 December 2015 (UTC)

Well, it seems nobody has wanted to for 2.5 years... -- Dagger (talk) 19:57, 27 December 2015 (UTC)

hmmm the only person that would add #set calls on random properties that far back would be...*looks*... yup, that was me.--Relyk ~ talk < 03:29, 28 December 2015 (UTC)

Collection parameter

The collection "Another Side, Another Story" breaks because of the ',' as a separator for multiple collections. —Kvothe (talk) 18:41, 17 September 2020 (UTC)

Done. Changed the separator from "," to ";". 63 pages, which contained multiple collection values, have been updated. --Tolkyria (talk) 20:14, 17 September 2020 (UTC)

External links update

There are some instances where weapons not available in the trading post still link to GW2Efficiency. I'd suggest to link to GW2BLTC in those cases as well, since their database tool is pretty useful. In fact, the ideal scenario would be to link to GW2BLTC every time an item (weapon or not) can be obtained through crafting or collections.--Lon-ami (talk) 13:57, 10 November 2020 (UTC)

Expanding the Tigris recipe in GW2BLTC: "undefinedundefinedundefinedundefined". I guess, they might want to revisit their code, otherwise it's a lightweight version of GW2eff which to be honest is much more detailed. Compare: Tigris (GW2BLTC) with Tigris (GW2Eff)

While linking to GW2BLTC if there's a recipe might be obivious to the wiki users, also linking to it if it's a collection reward isn't obivious at all and will totally have an inconsistent touch to the wiki users. So it's either always or never, but not such confusing circumstances. Beside your mentioned Black Lion Claim Ticket I haven't found any collection reward that has an acquisition on GW2BLTC (I tried a few from Property:Gives item), maybe you can list a few more. Furthermore, this exactly the same as the wiki achievement acquisition section.

Overall, I somehow fail to see the benefits for non-tradable items (the trading post lists and graphs are definitely worth mentioning as we currently already do). --Tolkyria (talk) 19:22, 10 November 2020 (UTC)

Nevermind, seems it's an exception, other somewhat popular collection rewards such as Machined Axe and The North Wind don't have any acquisition information, which makes it too inconsistent to be worth linking.

If there's any way to make an exception for just Black Lion Claim Tickets then go for it; if there isn't, I would say show GWBLTC in every instance GW2Efficiency is shown and call it a day. —The preceding unsigned comment was added by Lon-ami (talk • contribs) at 19:42, 10 November 2020‎ (UTC).

Spidy discontinued (again?)

apparently spidy is being withdrawn again. Delink time? -Chieftain Alex 20:39, 1 February 2023 (UTC)