Template talk:Vendor query table

Broken for direct item queries

1. {{Vendor query table | item = Basic Salvage Kit }}
2. Aberash#vendor3, Abram#vendor17, Aclik'lik#vendor3, Agent Caeder#vendor3, Agent Dajan#vendor3, Agent Fellhammer#vendor3, Agent Garvan#vendor3, Agent Glynnis#vendor3, Agent Guthki#vendor3, Agent Havelock#vendor3, Agent Ibboh#vendor3, Agent Jarra#vendor3, Agent Sephony#vendor3, Agent Tangwen#vendor3, Aggo#vendor10, Aggravar Biteeye#vendor3, Alisa#vendor10, Aluta#vendor17, Amela#vendor3, Amerin#vendor3, Anaa Baneblade#vendor3, Anessa#vendor3, Annil Hidestrike#vendor10, Anso#vendor3, Apprentice (armorsmithing)#vendor20, Apprentice (artificing)#vendor10, Apprentice (cooking)#vendor26, Apprentice (huntsman)#vendor10, Apprentice (jeweler)#vendor2, Apprentice (leatherworking)#vendor17, Apprentice (tailoring)#vendor17, Apprentice (weaponsmithing)#vendor9, Archaeologist (merchant)#vendor4, Archen Lun#vendor3, Archivist Lukka#vendor3, Armorer Pearl#vendor20, Armorer Vaxxa#vendor20, Armorsmith Lykaios#vendor20, Aro#vendor3, Arone#vendor20, Arriske#vendor9, Artair Rex Mari#vendor3, Artificer Gisela#vendor10, Artisan (Master Armorsmith)#vendor20, Artisan (Master Artificer)#vendor10, Artisan (Master Chef)#vendor26, Artisan (Master Huntsman)#vendor10, Artisan (Master Jeweler)#vendor2, Artisan (Master Leatherworker)#vendor17, Artisan (Master Tailor)#vendor17... further results
3. Aberash#vendor3, Abram#vendor17, Aclik'lik#vendor3, Agent Caeder#vendor3, Agent Dajan#vendor3, Agent Fellhammer#vendor3, Agent Garvan#vendor3, Agent Glynnis#vendor3, Agent Guthki#vendor3, Agent Havelock#vendor3... further results

The regex like bit doesn't work. Since the form generates the full name, I'd propose sticking with the third format. -Chieftain Alex 09:15, 6 September 2014 (UTC)

Perhaps that logic was in there to try and make "OoOoo Spear (Guard Lugung)#Fine" work. >.> Can of wurms. Using #replace to replace spaces with ? marks might work.. -Chieftain Alex 10:44, 6 September 2014 (UTC)

No vendors found based on constraints.

so many broken karma vendor pages that need ids. -Chieftain Alex 10:47, 6 September 2014 (UTC)

The reason is subobject pages can be referred to by their name, but the spaces mess up the parsing. It happens in the achievement subobjects too. I think it's using the ascii character but I didn't get it to work that way. ? is used as a wild card in the semantic search.--Relyk ~ talk < 14:02, 6 September 2014 (UTC)

Additional fields and headers

It would be convenient if the table also displays the zone of the location. Especially for collection items. --Shena'Fu (talk) 23:55, 7 February 2015 (UTC)

done--Relyk ~ talk < 00:05, 8 February 2015 (UTC)

It's broken, the areas are all one link. •••Mora 16:43, 11 February 2015 (UTC)

{{Vendor query table
|currency = Karka Shell}}

I've made it ignore parent zones if there is more than one area. Seemed like there would be the possibility of duplicate parent zones + long lists... -Chieftain Alex 19:35, 11 February 2015 (UTC)

Yeah, that's why I didn't include the zone as it's not very useful to display in the first place. Displaying the parent zone simply makes it too long.--Relyk ~ talk < 00:11, 12 February 2015 (UTC)

The zone is very convenient to let you know how to plan your routes.

the real problem is that the tables are not normalized properly. a cell should not contain a list of mutually exclusive, independent data. if an item can be found in several areas, then there should be a separate row for each area the item is found. that way there would be no need to mangle the data, each area properly associates with the correct zone, and the table can be sorted normally. Shena'Fu (talk) 01:06, 1 February 2017 (UTC)

Historical Vendor not showing as Historical

Just noticed a small issue with this template in regards to merchants such as Merchant (Halloween NPC) who is historical, but is still showing up on other pages as not historical, in this case that vendor shows up on Plastic Fangs as an option. Not sure how many other removed vendors like him there are(not counting seasonal ones), but I imagine there aren't that many so it's not a huge issue, but an issue nevertheless. - Do_odleplex 22:16, 13 March 2017 (UTC)

It was passing the historical status but not using it. I know Alex did most of the work on historical and implemented the behavior.--Relyk ~ talk < 23:21, 13 March 2017 (UTC)

Ahh okay. I see you added (Historical), is there a way to mark things as (Seasonal) if it's temporary or would that break things? - Do_odleplex 23:42, 13 March 2017 (UTC)

The #if wasn't quite right, since a value is given as "true" or "false", both of which triggered the "..._(historical)" bit.

Seasonal would be difficult to annotate Doodle, so sorry but I've no plans on implementing that. -Chieftain Alex 00:32, 16 March 2017 (UTC)

suggestion: location

Might be useful to add the ability to filter by location. Specifically, filtering by zone and by region seem like the most relevant use cases, so you could get a list of, say, all miniatures sold by vendors in the Crystal Desert (requested by my wife). Assuming all NPCs are still being annotated by sector, the query for zone would be [[Has vendor.Located in.Located in::{{{x}}}]] while region would be [[Has vendor.Located in.Located in.Located in::{{{x}}}]]. —Dr Ishmael 01:15, 3 October 2017 (UTC)

Hello stranger. We hit the query depth limit if we allow it for zones, but I've added a "location" parameter, it still sounds useful even if its only for regions. -Chieftain Alex 06:40, 3 October 2017 (UTC)

What if you just made the parameters explicit, i.e. region = and zone = instead of the ambiguous location? That's what I was thinking of originally, and it would eliminate the need for a #show query to determine the location type. —Dr Ishmael 16:25, 3 October 2017 (UTC)

I'm just the typing monkey here, you know this stuff as well as I do, in any case it isn't used anywhere yet so you can rename it whatever you want. :D -Chieftain Alex 17:44, 3 October 2017 (UTC)

Added level column

→ moved from Talk:List of karma merchant items/Medium armor/by level

I considered the deletion tag, and I'm thinking List of karma merchant items/Medium armor as it currently exists is somewhat annoying since it doesn't list the item's level. Should we move this page to replace the other one, then replicate this page on the Heavy/Light pages? -Chieftain Alex 10:36, 11 September 2022 (UTC)

Same probably applies to:

• One-handed Weapons by level
• Off-hand weapons by level
• Two-handed Weapons by level

-Chieftain Alex 10:39, 11 September 2022 (UTC)

Alternatively we could fix Template:Vendor query table to show item level - I'm baffled that it doesn't do this already. (mentally I was expecting it to show similar columns to Template:Vendor table row. -Chieftain Alex 10:41, 11 September 2022 (UTC)

Agree. Would be actually useful then. I'm in favor of updating the template. —Kvothe (talk) 10:45, 11 September 2022 (UTC)

Implemented, and displayed by default.

Might just be me, but the page load seems a fair bit heavier. Due to the SMW not printing repeated queries, the underlying template uses an individual show to pull the level/icon/name - could well be this as the root cause. Do we want the level shown or hidden by default? -Chieftain Alex 12:18, 11 September 2022 (UTC)