Wowpedia
Advertisement
Wowpedia
230,048
pages

Comments

Thanks for the initiative; we used to have a gadget that did the same but it may have been disabled. The link is kind of confusing though: I went to the releases page and it offered a .zip download, however there is no .jar file in the directory. --g0urra[T҂C] 10:34, 14 October 2016 (UTC)

Edit: nevermind, I went to the wrong page. --g0urra[T҂C] 10:35, 14 October 2016 (UTC)

Some things I'd like to add: remove the spacing in the headers, add {{subst:el}} in the External links section, and add the category. -g0urra[T҂C] 10:41, 14 October 2016 (UTC)

The tool seem to not work on this quest, just returns "Error": http://www.wowhead.com/quest=43697/warriors-of-light --g0urra[T҂C] 10:44, 14 October 2016 (UTC)

Thanks for the feedback! I'll get all this done soon™, just going to wait a bit for in case more feedback comes up, so I can make all the changes in one fell swoop. - Linneris (talk) 10:50, 14 October 2016 (UTC)
Wow, great job mate Xporc (talk) 11:04, 14 October 2016 (UTC)

Is it possible to grab the "Next" and "Previous" parts? See N Paladin [110] A Light in the Darkness (Wowhead). --g0urra[T҂C] 12:29, 14 October 2016 (UTC)

Indeed, I'll use information from the sidebar whenever possible, though Wowhead's information about quest chains and correct sequences is often very incomplete compared to Wowpedia. - Linneris (talk) 13:18, 14 October 2016 (UTC)
Ohh interesting! Nice initiative. PeterWind (talk) 14:00, 14 October 2016 (UTC)

It seems to miss to grab categories (maybe just some?), for example N Paladin [110] Allies of the Light doesn't grab the Paladin Campaign quests category. --g0urra[T҂C] 07:38, 20 October 2016 (UTC)

How would it know that informa-- Oh. Ooooh. The breadcrumb bar. Got it. I'll put it in the next release. - Linneris (talk) 06:06, 21 October 2016 (UTC)

Change the "Patch notes" to "Patch changes". It also adds an extra (redundant) line right after the Rewards heading. Mordecay (talk) 13:16, 22 October 2016 (UTC)

All done! See release 0.3 above. - Linneris (talk)

Thank you for this cause I agree it was really time consuming doing each quest manually. Snake.gifSssssssssssssssssssssssss Coobra sig3.gifFor Pony! (Sssss/Slithered) 19:18, 22 October 2016 (UTC)

Remaining stylistic questions

  • "Progression" or "Quest progression"? I've seen both used, and used the later in the template, but found it shortened to just "Progression".
  • XP amount with decimal separators or without? "14800 XP" or "14,800 XP"?

- Linneris (talk) 05:17, 30 October 2016 (UTC)

"Progression" should be fine. And with the decimal separators in the infobox and under the gains section too.
+ Maybe add [XP] at the end of | experience =

Mordecay (talk) 23:04, 30 October 2016 (UTC)

I have been shortening it to Progression because that is how the Wowpedia quest boilerplate labels it. In regards to using a comma or not for the xp amount, both are acceptable. (Although for myself, I prefer it with a comma because of the game's country of origin.) -- Alayea (talk / contrib) 05:31, 3 November 2016 (UTC)

Errors

  1. The remaining quests of Angry Zurge and Chris Clarkie show error. Any possibility to fix it?
  2. For example this quest awards 3 charges of the item so would it be possible to add the number(s) in the infobox and rewards section?
  3. Noticed that "[XP]" link in infoboxes is absent from the utility. Not sure whether it is really needed but I saw it in regular-made quest pages. Mordecay (talk) 23:48, 18 November 2016 (UTC)
I've opened about a dozen quest articles at random, and none of them had the XP link in infoboxes. The preload boilerplate doesn't have it either. As for the other two problems, thanks for the report — I'll fix them soon™. - Linneris (talk) 07:03, 19 November 2016 (UTC)
Both done in 0.4. - Linneris (talk) 09:44, 19 November 2016 (UTC)

When I loaded this quest, the utility did not create the | shareable = yes line. —The preceding unsigned comment was added by Mordecay (talk · contr).

Fixed in 1.0. - Linneris (talk) 09:02, 27 November 2016 (UTC)
If a quest is shareable, you are to leave out that field entirely (see Help:Quest articles/Preload). It's only used for when a quest isn't shareable since only a small minority of quests in WoW can't be shared. -- Alayea (talk / contrib) 22:56, 28 November 2016 (UTC)
  1. This quest hits error.
  2. this one says that u will gain 54 silver at max lvl. The utility says only "You will also receive: 56s".
  3. Support for removed / older quests:
    1. Would it be possible to add instead of Stub/Quest template the {Removed|patch=XYZ} template when dealing with removed quests?
    2. The util doesn't load reward item from [1]
    3. Any possibility for the util creating [Undercity (faction)|Undercity] instead of [Undercity] (+ other Ali & Horde main factions) in infobox and Gains section? Mordecay (talk) 13:25, 10 December 2016 (UTC)
      1. Thanks for the report, will fix. Basically, if you see an error message, it's a bug in the program.
      2. Sadly, Wowhead doesn't list the patch in which a quest was removed, but I can at least add {{Removed|patch=}} and let the user manually type in the patch. This will be on my list now.
      3. This is by design. I don't see many Wowpedia quest articles list max-level gold rewards, and those that are there are usually outdated (listing max-level rewards for level 80, 90, etc.), so I decided not to bother. But if others think it's necessary to add level 110 gold rewards, then I will.
      4. Sure, this will be on my list as well. - Linneris (talk) 16:10, 10 December 2016 (UTC)
Yep, this is what I meant, to add the beginning of the template, the number would be then added manually. The max level rewards need at least to be fixed because the util treated it as a regular reward though it is not, it is the max-level amount. Also I just checked a quest with wowhead having a different amount of gold than in the game (at least in a video which I checked). With every expansion these get outdated, so I don't think the max-level rewards are that important, IMO. Mordecay (talk) 16:30, 10 December 2016 (UTC)

Wowhead seem to have updated their quest-chain lists and the util no longer loads previous / next quests. Tried it on this. Mordecay (talk) 23:53, 16 December 2016 (UTC)

All these issues should be fixed in 1.1.1. - Linneris (talk) 05:50, 2 January 2017 (UTC)
Cool, thanks! Also, if possible to add |doc= for removed quests? And the rewards from [2] and [3] don't load. Mordecay (talk) 12:00, 2 January 2017 (UTC)
As I said, ignoring max-level rewards is by design - for now, at least. I can implement if there's demand for it. I'll add doc= in the next release. - Linneris (talk) 14:20, 3 January 2017 (UTC)
Oh, we were speaking about items? I thought that it applied only for gold rewards. Mordecay (talk) 18:18, 3 January 2017 (UTC)
Oh! If it doesn't load items, then it's a bug and I'll fix it. - Linneris (talk) 05:18, 4 January 2017 (UTC)

Some new concerns here. Mordecay (talk) 12:03, 24 April 2017 (UTC)


The second part of the objective (the second line) of [4] doesn't load. --Mordecay (talk) 13:52, 16 June 2017 (UTC)

Repeatable turn-in quests

On second thought, it seems I goofed up. These Ashran quests (A [100] Orc Tooth) seem to be repeatable quests, like A [15-30] More Warbeads. They don't even have Objectives and Description sections — only Progress and Completion sections.

What do we do with these? It seems the precedent has been inconsistent: A [15-30] More Warbeads uses the "Objectives" header for the Progress message, while A [60] Additional Runecloth uses Progress, then the bulleted list of objectives, then Completion. Which would be correct? - Linneris (talk) 14:12, 19 November 2016 (UTC)

Oh, u are right those are just turn-ins. Dunno, really, Progress - the list - Completion, just like wowhead has it, looks okay. Mordecay (talk) 20:04, 19 November 2016 (UTC)

Missions

Working good! Things I've noticed so far:

  1. The 7.0 abilities show "type" (boss, minion, spell) but it should be name of the ability like slowing, lethal... although despite the same name each type has different icon (minion-lethal and spell-lethal icon have the same effect but different icon). And ofc they need to be uploaded here first.
  2. Some missions are "Exhausting" so that should probably be added too.
  3. Wowpedia also has Template:MissionLegionbox which changes "followers" to "champions" and add space for class icon. Would it be possible for the utility to differentiate between WoD and Legion missions? Mordecay (talk) 10:09, 27 November 2016 (UTC)
  • Per item:
    1. Fair. I noticed that but didn't bother because even the number of abilities per enemy seems to be incorrect for Legion missions, so you will need to manually process them anyway. But I'll see if I can at least use the right ability names.
    2. The Exhausting attribute needs to be supported by the templates first (Template:Missionbox, Template:Navalbox and Template:MissionLegionbox), after which I can easily add it.
    3. I didn't know about this one, as it's sadly missing in Category:Infobox templates. Yes, it's possible, and in fact it already does differentiate between WoD follower and naval missions (Missionbox vs Navalbox). I'll use this template for Legion missions in the next release. In the meantime, I'd appreciate if someone wrong documentation for it along the same vein as Missionbox and Navalbox. (Perhaps User:Kandooww, its creator? I'll ask them on their talk page.) - Linneris (talk) 10:29, 27 November 2016 (UTC)
  • Addition: Also, the Legion mission enemy abilities (Powerful, Cursed, Disorienting, etc.) need to be supported by Template:Garrison ability first, or possibly a different template. - Linneris (talk) 10:36, 27 November 2016 (UTC)
Done. The type for Legion missions are only 4: Quest (class-specific), Treasure, Special, and Generic. [5] --Kandooww ^^ (talk) 11:20, 27 November 2016 (UTC)
Here is something I don't understand. Take this mission for example. The "Rotwood Saplings" enemy is listed with three abilities (Slowing, Disorienting and Cursed), but in my game, I see only one: Cursed. Is one of the abilities selected at random? - Linneris (talk) 09:35, 3 December 2016 (UTC)


[6] shows error. Mordecay (talk) 18:32, 13 January 2017 (UTC)
Thanks for the bug report, will fix. - Linneris (talk) 07:03, 15 January 2017 (UTC)


Not sure whether it is the plugin or a wowpedia thing, but some icons next to enemies don't show up here Campaign Troops in the Field & Campaign Troops in the Field. --Mordecay (talk) 16:35, 12 May 2017 (UTC)
Looks like Template:Garrison ability is missing some Legion threat types (specifically, Boss, Minions and Spell). - Linneris (talk) 05:55, 4 July 2017 (UTC)

Linneris, was there any reason the word chosen was "Counters" and not "Encounters" (as used on wowhead)? Seeing as English is not my daily spoken language I might be wrong, but I'm pretty sure "counters" does not mean that. --Celellach (talk) 12:04, 23 August 2017 (UTC)

I followed precedent established by pre-existing mission articles on Wowpedia. "Counters" was probably chosen because the enemy abilities are supposed to map to follower abilities that counter them. - Linneris (talk) 12:13, 23 August 2017 (UTC)
I see. Well, I believe this is wrong. The title of the section should be "Encounters" as that is what it is - the current encounter, while the counters are the abilities that counter the enemy threats. Looking at some random missions (Campaign Archmage Vargoth's Travels: The Nightborne Vault as an example), it doesn't even list the counter abilities but just the enemy threats, making the section heading even more off the point. --Celellach (talk) 12:23, 23 August 2017 (UTC)
Since this concerns both generated and manually created mission articles, I suggest creating a thread on the forum rather than here. - Linneris (talk) 12:44, 23 August 2017 (UTC)
Posted on the forums. Pretty sure no one is going to object to this.Celellach (talk) 21:58, 23 August 2017 (UTC)

NPCs?

Hey dude, would you be able to expand the tool to include NPCs? Mordecay (talk) 20:51, 15 April 2017 (UTC)

I'm not a dude, but sure. - Linneris (talk) 05:26, 16 April 2017 (UTC)
Sorry! Mordecay (talk) 12:03, 24 April 2017 (UTC)
Implemented in 1.2.0. - Linneris (talk) 09:25, 4 July 2017 (UTC)
Neat! :) PeterWind (talk) 10:16, 4 July 2017 (UTC)
Very nice! --Mordecay (talk) 11:07, 4 July 2017 (UTC)

Formatting question: should the level range have spaces around the hyphen or not ("Level: 16-17" vs "Level: 16 - 17")? I've seen both on Wowpedia. For now QuestFiller uses the former. - Linneris (talk) 10:54, 4 July 2017 (UTC)

I've seen people adding extra space around hyphen so probably "16 - 17"
A question, would it be possible to get the "race" and gender information from wowhead's names of soundfiles? --Mordecay (talk) 11:16, 4 July 2017 (UTC)
Good idea, I didn't think of that! This will be in 1.2.1, alongside some small fixes like filling a mob's average money dropped when available. - Linneris (talk) 11:26, 4 July 2017 (UTC)
Cool! Also, could the text of the image line be the same as the name (+ ".jpg"). Most of the time, I believe, it is the "default" name for NPC pictures.
Mana numbers don't seem to load.
Wowhead's "Classification: Elite" load in the "level" line, but for it there's the "type" line.
+ Missions no longer load XP. --Mordecay (talk) 20:57, 4 July 2017 (UTC)


By the Old Gods, it even loads quests and punctuation pics! I <3 u! --Mordecay (talk) 17:44, 4 July 2017 (UTC)

The issues above are all fixed in 1.2.1, except for mana. It doesn't load mana because I thought Wowhead doesn't expose mana at all, but apparently it does, but not for all NPCs with mana. Will be in the next release for those NPCs for which Wowhead has mana values. - Linneris (talk) 08:14, 5 July 2017 (UTC)
Very good! Last two questions: since it load quests, could it also load wowhead's "Objective of" quests for mobs (with "Objective of" header)? And the race category.
Thank you very much for this tool it will definitely ease the work here! --Mordecay (talk) 11:47, 5 July 2017 (UTC)
Yes, both are possible. I'll add that in 1.2.2. - Linneris (talk) 13:44, 5 July 2017 (UTC)


Healths from various instance difficulties not loading and would probably be cool with the {{Health}} template?
Level (quests, npcs), requires level (quests), patch changes, factions and affiliations, quest givers, progression chain quests, and most of the fields from missions no longer load. --Mordecay (talk) 00:47, 15 July 2017 (UTC)
Fixed in 1.2.2. I couldn't find the "Objective of" header for NPCs, though - only for items. Could you give an example of an NPC with an "Objective of" header? - Linneris (talk) 06:18, 18 July 2017 (UTC)
Scarlet Archer#Objective of from this. --Mordecay (talk) 12:49, 18 July 2017 (UTC)


There's seems to be a new error preventing the app from loading things. Also, it doesn't load yell quotes, only say quotes. --Mordecay (talk) 12:23, 22 August 2017 (UTC)
Could you link a Wowhead page on which it fails? - Linneris (talk) 13:00, 22 August 2017 (UTC)
[7], [8], [9]. Everywhere, I guess. --Mordecay (talk) 13:05, 22 August 2017 (UTC)
I tried all those links and they work for me. Could you post a screenshot of the error? - Linneris (talk) 13:24, 22 August 2017 (UTC)
It says: Error, htttp://wow.zamimg.com/js/locale_enus.js. --Mordecay (talk) 13:29, 22 August 2017 (UTC)
That's really strange. Does the file open in the browser for you? Is there any stack trace in the error message? - Linneris (talk) 13:46, 22 August 2017 (UTC)
File:Wqf.jpg. Wowhead seems to be working properly. --Mordecay (talk) 14:01, 22 August 2017 (UTC)
Try this build: https://lucidfox.org/files/questfiller-1.2.2-debug.jar . It should give a mode detailed error message. - Linneris (talk) 07:08, 23 August 2017 (UTC)
It gave me this File:Wqf2.jpg --Mordecay (talk) 11:41, 23 August 2017 (UTC)
Huuuuuuh. Now that's weird. So the server returns a 404 for this file for you only, and only when accessed via QuestFiller, not the browser? Try https://lucidfox.org/files/questfiller-1.2.2-debug1.jar . - Linneris (talk) 12:42, 23 August 2017 (UTC)
Yea, wowhead opened in browsers works fine. Still not working :-( File:Wqf3.jpg --Mordecay (talk) 12:49, 23 August 2017 (UTC)
What happens if you open this exact link http://wow.zamimg.com/js/locale_enus.js in your browser, and then press F5? - Linneris (talk) 15:40, 23 August 2017 (UTC)
It says: 404 Not Found, nginx --Mordecay (talk) 16:00, 23 August 2017 (UTC)
Should be fixed in 1.2.3. - Linneris (talk) 19:09, 23 August 2017 (UTC)
Working fine! --Mordecay (talk) 19:13, 23 August 2017 (UTC)

V1.2.3 returning error

So v.1.2.3 was working fine when I last used it on Tuesday this week (2017-09-12) when populating the unlocked quests for Mac'Aree. I had other things going on, so I wasn't able to finish the chain. But now that I've got a chance to work on it again, attempting to load a quest now returns an error. Something about java and element and other technical jargon. Wonder if Wowhead changed something again.

Here's a screenshot I took: https://i.imgur.com/GP2GrXl.jpg -- Alayea (talk / contrib) 03:36, 15 September 2017 (UTC)

Thanks for the report! Fixed in 1.2.4. - Linneris (talk) 06:12, 15 September 2017 (UTC)
Great! =) -- Alayea (talk / contrib) 17:14, 15 September 2017 (UTC)


124 new errors File:WQF4.jpg. For quests and missions too. --Mordecay (talk) 15:43, 28 October 2017 (UTC)

Thanks, fixed in 1.2.5! - Linneris (talk) 17:26, 28 October 2017 (UTC)
No longer showing errors, but it creates
"| type = EliteAdded in patch 7.1.0.22810" or "| type = EliteReact: <q2>A <q10>HAdded in patch 3.0.2.8905" and " | level = 110React:" for NPCs;
"| end = [[Anduin WrynnNot sharableDifficulty: 60  63  72Added in patch 1.11.1.10772]]" for quests;
"| duration = 16 hrsCategory: 7.0 Class Hall - Treasure Missions - RaidLevel: 110Champions: 3Mission: 16 hrsAvailable: 10 daysLocation: Antoran WastesAdded in patch 7.3.0.24920" and "| type = 7.0 Class Hall - Treasure Missions - RaidLevel: 110Champions: 3Mission: 16 hrsAvailable: 10 daysLocation: Antoran WastesAdded in patch 7.3.0.24920" for missions. --Mordecay (talk) 17:50, 28 October 2017 (UTC)
Check out 1.2.6. - Linneris (talk) 18:20, 28 October 2017 (UTC)
All good. thx. --Mordecay (talk) 18:27, 28 October 2017 (UTC)

The previous errors occur again. --Mordecay (talk) 11:25, 30 October 2017 (UTC)

Fixed in 1.2.7. - Linneris (talk) 13:09, 30 October 2017 (UTC)

Interest check: browser extension

https://lh3.googleusercontent.com/rpmLfq5Iuhj2uhXNPTmagSasaAJperMM6OvVRCxQLNpssahCW4iF95i09ZThieD5JcJ44v5ciLE=w320-h200

At some point in my spare time, I would be interested in taking a shot at rewriting QuestFiller as a browser extension for Firefox and Chrome. What it would do is add a toolbar button that, when clicked on a supported Wowhead page, would open a popup window with Wowpedia wiki markup to copy.

Advantages: no need to install Java and download a separate program, or even switch away from the browser window. Automatic updates.

Disadvantages: none, as far as I can tell.

Would you folks be interested in this? Tentative ETA would be "sometime in November". - Linneris (talk) 12:30, 29 October 2017 (UTC)

Sounds good! --Mordecay (talk) 12:35, 29 October 2017 (UTC)
Sure, sounds neat! :) PeterWind (talk) 13:10, 29 October 2017 (UTC)
Why not? I've never used the old tool so far, but that would be nice Xporc (talk) 09:37, 30 October 2017 (UTC)

Name

The browser extension is shaping up well; by my estimate, it is about 2/3 done. The first version will have exactly the same functionality as the current QuestFiller Java app, and I'll try publishing it on the Firefox and Chrome extension repositories.

A thought occurred to me, though: "QuestFiller" has been an inaccurate name for a while, since it now does more than just quest articles, and in the future it might grow to encompass more functionality to ease Wowpedia editing. A browser extension can aggregate just about any information from any website, as long as it's programmatically possible, and modify the user interface of websites in just about any way. Sky's the limit.

So, perhaps publishing the extension a different name would make sense? Something like "Wowpedia Editor's Toolkit"? Or keep it named "QuestFiller"? Or other suggestions? - Linneris (talk) 15:42, 11 November 2017 (UTC)

Sounds good! Nice idea aswell. I don't have any good ideas myself though :) PeterWind (talk) 16:24, 11 November 2017 (UTC)
"Wowpedia Editor's Toolkit" sounds good, honestly Xporc (talk) 20:08, 11 November 2017 (UTC)

Published

The extension is ready. Screenshot

When browsing a Wowhead quest, mission or NPC page, you should see a "W" icon on the toolbar. Clicking it will produce a popup window with wiki markup.

I tried to exactly replicate the functionality of the Java tool. If there are bugs, report them here, as usual. - Linneris (talk) 08:00, 26 November 2017 (UTC)

Cool! Will give it a try later :) PeterWind (talk) 12:00, 26 November 2017 (UTC)
Very nice! It creates "| aggro = {{Aggro|Hostile|Hostile}}", "| aggro = {{Aggro|Neutral|Neutral}}" and "| aggro = {{Aggro|Friendly|Friendly}}" instead of "| aggro = {{Aggro|-1|-1}}", "| aggro = {{Aggro|0|0}}" and "| aggro = {{Aggro|1|1}}" --Mordecay (talk) 13:15, 26 November 2017 (UTC)
\o/ Xporc (talk) 13:28, 26 November 2017 (UTC)
Pushed version 2.0.1 with the aggro issue fixed. - Linneris (talk) 15:02, 26 November 2017 (UTC)
It doesn't load health for [10]. --Mordecay (talk) 15:42, 26 November 2017 (UTC)
Fixed in 2.0.2. - Linneris (talk) 15:57, 26 November 2017 (UTC)

PTR

Is the Toolkit usable on PTR pages? It doesn't seem to be the case, but I could be wrong. Would that be a possible feature in a later update? PeterWind (talk) 12:03, 13 December 2017 (UTC)

Also for the BfA pages? I know that PTR and BfA wowhead pages may be partially incomplete, but at least the tool creates the infobox and sections which speeds the creation. --Mordecay (talk) 12:02, 9 February 2018 (UTC)
Late, but version 2.0.3 should now work with all wowhead.com subdomains, including ptr.wowhead.com and bfa.wowhead.com. - Linneris (talk) 19:58, 30 May 2018 (UTC)
Very nice! Thank you :) PeterWind (talk) 20:48, 30 May 2018 (UTC)
Thumbs up! Xporc (talk) 20:51, 30 May 2018 (UTC)
Missions on bfa.wowhead don't load. --Mordecay (talk) 11:01, 2 June 2018 (UTC)
Every type of mission (garrison, naval, Legion, BfA) requires separate handling. If you link me an example of a BfA mission article on Wowpedia, I can implement parsing them. - Linneris (talk) 13:59, 8 June 2018 (UTC)
Looked into it and it can wait. Needs template and abilities support here first. --Mordecay (talk) 14:47, 8 June 2018 (UTC)

Quest Boilerplate

A proposed update to combine the sections Rewards and Gains together. You can see the discussion here. — SurafbrovWowpedia's wiki representative T / C 06:11, 28 June 2018 (UTC)

Implemented in 2.0.4. - Linneris (talk) 11:03, 6 July 2018 (UTC)

Feature request - reputation categories

Heya. Your tool has been invaluable in getting BfA content on the wiki. I have a small feature request, and a related bug report:

When quests award reputation with a faction, could the tool add [[Category:<faction> quests]]? For instance, "+25 Storm's Wake" would also add [[Category:Storm's Wake quests]] below the elinks section.

Additionally, it doesn't look like the tool handles quests that reward reputation with multiple factions. For instance, any of the tortollan quests in Stormsong Valley, for instance N [110 - 120] Battle Victorious. The parse only pulls the Storm's Wake rep, but not the Tortollan Seekers rep.

Thanks again for your effort. We couldn't get stuff up to date without you! --k_d3 18:40, 20 August 2018 (UTC)

Plus an additional small request for if the rewards are with the Zandalari Empire faction, let it create this: [[Zandalari Empire (faction)|Zandalari Empire]] (Zandalari Empire). Just like it does with the Orgrimmar and the other factions using the parenthesis (as discussed in the Errors section here). Thanks! --Mordecay (talk) 22:23, 20 August 2018 (UTC)
If it doesn't handle multiple reputations, it's a bug and I'll look into that. And sure, these are easy to implement. I'll do it soon™. - Linneris (talk) 08:54, 21 August 2018 (UTC)
Implemented in 2.0.5. - Linneris (talk) 11:02, 29 August 2018 (UTC)

2.0.5 returns error

Hey! When using the toolkit on quest pages I get the following error message this.getRegexGroup(...) is null. I only just noticed this happening today, but it's been a few days since last time I used it. PeterWind (talk) 09:01, 7 September 2018 (UTC)

I get Cannot read property 'replace' of null on any quest. (On Chrome) I also get Peter's error when using Firefox. — SurafbrovWowpedia's wiki representative T / C 09:04, 7 September 2018 (UTC)
I updated Firefox DE. I got this one now, this.getRegexGroup(...) is null, can't access property "replace" of it. Looks like Chrome and Firefox / Firefox DE may be having the same issue. — SurafbrovWowpedia's wiki representative T / C 09:13, 7 September 2018 (UTC)
I get the same error on missions and NPC wowhead pages as well. Firefox here. --Mordecay (talk) 12:17, 7 September 2018 (UTC)
Fixed in 2.0.6. - Linneris (talk) 14:26, 9 September 2018 (UTC)
Many thanks! :) PeterWind (talk) 15:26, 9 September 2018 (UTC)

Updated naming policy

With the updated naming policy, the editor will probably require yet another update at some point. The quests should still have redirects, so shouldn't be too urgent though :) PeterWind (talk) 06:31, 10 September 2018 (UTC)

To explain what changed, the psuedo-"Quest:" namespace is no longer a thing. For instance, the "Beachhead" quest is now at [[Beachhead]] rather than [[Quest:Beachhead]]. --k_d3 06:42, 10 September 2018 (UTC)

Reports, requests, and updates

Heya, compiled a list of some stuff. If and when you have time could you look at it? Not very urgent and some are very trivial, but it would be nice to have these, if possible. Thanks!

  1. Support for BfA missions with Template:MissionBFAbox (also its gold rewards as previous ones ([11] doesn't load gold even tho the WoD and Legion mission templates have gold parameter).
  2. Wowhead pages have [[7th Legion]] reputation in NPC and quest pages. Have it load as [[7th Legion (faction)]] here (like all the playable race reputations that use "(faction)" in name).
  3. Convert these quotes into this rainbow?
  4. Do an "Objective of" section (Zayoos#Objective of) from [12]?
  5. World quest and bonus objectives like this one don't load the first objective and instead create: ...
  6. In world quests, it creates a start and end parameter with the same content ("Automatic"). If it is the same, the end parameter is not wanted, and was previously requested to not be loaded, and these times is sporadically being removed from pages by a user. IIRC, it used to do that without the same end parameter, but it does it again.
  7. In front of the ending parenthesis of questboxes, It creates an extra space. Example: A [10-50D] Freehold: A Pirate's End. Have the addon not add the extra space.
  8. Quest pages have an extra / redundant line in the Rewards section, also seen in A [10-50D] Freehold: A Pirate's End. Have the addon not add the extra line there.
  9. Quest pages have an extra / redundant line in the questbox between experience and money paramterer when there's no reward (see [13]). Have the addon not create extra line when reward parameter is missing.
  10. To followup on the previous one, when there's the reward parameter, its content starts in the next line (see [14]). Have the addon not add the extra line there.
  11. Doesn't load health into NPCbox from instance mobs like [15].
  12. Not all quest rewards loading from removed quests like [16]. --Mordecay (talk) 01:22, 13 October 2018 (UTC)
All reasonable requests. Extra whitespace is always a bug, and the "Automatic" thing is surprising - it should automatically omit the end parameter if it's the same as start. I'll look into it when I have time. - Linneris (talk) 10:27, 13 October 2018 (UTC)
All these should be fixed in 2.0.7. - Linneris (talk) 10:22, 16 June 2019 (UTC)

Vendor information

When creating a page for Tanubu I noticed that under the ==Sells==, there's a "|" missing after "Itembox". PeterWind (talk) 08:26, 7 November 2018 (UTC)

  • Works correctly for me. This is what is generated:
{{Itembox
|Blood Apples|c1={{Cost|2|50|}}
|Gorgrond Grapes|c2={{Cost|2|50|}}
|Great Turtle Soup|c3={{Cost|2|50|}}
|Mount Mugamba Spring Water|c4={{Cost|2|50|}}
|Riverbeast Stew|c5={{Cost|2|50|}}
|Rootway Papaya|c6={{Cost|2|50|}}
|Seafoam Coconut Water|c7={{Cost|2|50|}}
|Seared Simmerfin|c8={{Cost|2|50|}}
|Sliced Zangar Buttons|c9={{Cost|2|50|}}
|Tanaan Sweetmelon|c10={{Cost|2|50|}}
|Zeb'Ahri Kiwi|c11={{Cost|2|50|}}
|Zocalo Cheddar|c12={{Cost|2|50|}}
}}

- Linneris (talk) 13:35, 8 November 2018 (UTC)

This is what's supposed to be at the beginning:
{{Itembox|
|Blood Apples|c1={{Cost|2|50|}}

--Mordecay (talk) 23:21, 8 November 2018 (UTC)

  • Ah, right, because the first parameter is the caption. Fair enough. - Linneris (talk) 09:45, 9 November 2018 (UTC)
Right, I could've been more specific there :) PeterWind (talk) 10:16, 9 November 2018 (UTC)

Null error

Hello, just popping in to let you know that Wowhead did something either last night or this morning to cause the extension to return the error s is null. I appreciate your work and hopefully the issue can be resolved. :) -- Alayea (talk / contrib) 23:51, 12 December 2018 (UTC)

The two quests in question are Leathered Patterns (Alliance). I got Cannot read property 'nextSibling' of null on Chrome. There is no quest text information, so that may be the result of the error. — SurafbrovWowpedia's wiki representative T / C 00:05, 13 December 2018 (UTC)
Working fine on firefox. Unless it's been fixed in the meantime :-D --Mordecay (talk) 14:35, 14 December 2018 (UTC)
It is working now because there is a "Completion" text. Prior, nothing was there. — SurafbrovWowpedia's wiki representative T / C 19:41, 14 December 2018 (UTC)
If it doesn't work on quests without completion text, that's a bug and I'll fix it. Thanks for reporting. - Linneris (talk) 02:56, 15 December 2018 (UTC)
Should be fixed in 2.0.7. - Linneris (talk) 10:22, 16 June 2019 (UTC)

Suggestions

Hey! Would it be possible to add quantity to the ==Sells== section? "|q11=10" as an example. For the NPCs it lists the parameter as "| repfaction" but I think these days we mostly use "| affiliation". PeterWind (talk) 18:22, 29 December 2018 (UTC)

Also, Category:World of Warcraft NPCs was moved to Category:NPCs. — SurafbrovWowpedia's wiki representative T / C 02:46, 7 April 2019 (UTC)
Incorporated into 2.0.7. Thanks for the pull request! - Linneris (talk) 10:22, 16 June 2019 (UTC)

Hello I do have suggestion as well. Right now when you open the extention window you can close it only if you copy all the window . But There are times i just want to copy part of it and than close it but i cant. I would like to be able to do so . my suggestion is to add another button a X button to close the window . Or Seperate the copy and close to two buttons . one to copy and one to close. Thanks! (Yuvalal (talk) 17:41, 1 January 2020 (UTC))

Reasonable. Will add a close button. - Linneris (talk) 18:36, 1 January 2020 (UTC)

2019 hiatus

The thing is dead, we are doooomed! :-( --Mordecay (talk) 20:07, 30 May 2019 (UTC)

That is a bit of a stretch. — SurafbrovWowpedia's wiki representative T / C 21:05, 30 May 2019 (UTC)
I'm still here, just been slacking. I remember about the tool and will get to implementing the requests soon™. - Linneris (talk) 07:35, 31 May 2019 (UTC)
2.0.7 has been released. - Linneris (talk) 10:22, 16 June 2019 (UTC)
A big thank you! --Mordecay (talk) 10:32, 16 June 2019 (UTC)
Great news! Thank you! PeterWind (talk) 10:44, 16 June 2019 (UTC)
Awesome! Thanks for the updates! — SurafbrovWowpedia's wiki representative T / C 23:00, 17 June 2019 (UTC)

Vendor inventory

Hey! Just recently it seems to me that the toolkit no longer adds vendor inventories. While on the topic on vendors, perhaps quantity could be added as well in the form of "|q1=5|"? PeterWind (talk) 11:31, 13 November 2019 (UTC)

Will look. - Linneris (talk) 16:39, 13 November 2019 (UTC)
Thanks! Seems Wowhead just overhauled their site layout as well. PeterWind (talk) 09:17, 21 November 2019 (UTC)
Yes, and now the extension is broken. I'll look into it when I have time. - Linneris (talk) 09:42, 21 November 2019 (UTC)
All done in 2.0.8. - Linneris (talk) 10:39, 21 November 2019 (UTC)
Very cool! Thanks a bunch! It still doesn't seem to grab quantities for me, but that's a minor issue as well. PeterWind (talk) 12:59, 21 November 2019 (UTC)
My bad, I see now that it's added for limited supply items! Again this is no rush, but would it be possible to have that feature for all vendored items, like food and drink items which are usually sold in numbers of 5? and to have the limited supply number wrapped in parentheses like "Agile Boots|c1={{Cost||36|81}}|q1=(2)" PeterWind (talk) 13:03, 21 November 2019 (UTC)
Can I have an example link to an NPC selling items in stacks? I'll do it when I next have free time. - Linneris (talk) 13:55, 21 November 2019 (UTC)
Sure thing. If you see this one will give lines like "|Alterac Swiss|c1={{Cost||40|}}". If possible, I'd like it to include the quanitiy like so "|Alterac Swiss|q1=5|c1={{Cost||40|}}" or in the case of limited supply like so "|Alterac Swiss|q1=(2)|c1={{Cost||40|}}" PeterWind (talk) 15:24, 21 November 2019 (UTC)
Will do. - Linneris (talk) 17:10, 23 November 2019 (UTC)

Reports, requests, and updates #2

The following are not urgent and concern some minor fixes and additions that would be cool to have.

  1. Let's start by a question whether a dark mode for the extension would be possible?
  2. For some reason, some quest rewards (but not all) are not loading at all. For example this one is not loaded in the infobox or the section.
  3. When Wowhead has "Series" available (like here) have it fill the questbox's "| previous =" and "| next =" parameters.
  4. Previously, it was asked to ignore "repfaction=" and instead do the "affiliation=" parameter which is ok, but the affiliation parameter needs also the square brackets on the word.
  5. Also, there were originally several exceptions when we have reputation names that have "(faction)" in the name, like Orgrimmar (faction) or Zandalari Empire (faction). It used to convert those exceptions to that name and link, but it no longer does that.
  6. Have the first stubs placed next to each other instead of under – [example].
  7. When the aggro is set to Alliance Horde, have it add {{Stub/Mob}} instead of {{Stub/NPC}} as well as the zone category - from "Category: NPCs" to "Category: Mobs".
  8. When both, Activequest & Availablequest are present, or only AvailablequestActivequest is present, have only the Category:Quest givers added.
That means adding Category:Quest enders when only Activequest is present.
Have the quest givers and quest enders category be placed above the zone category.
  1. Some races on Wowhead have "v2" in the sound name. Could it ignore the "v2"?

Thanks! --Mordecay (talk) 15:16, 23 November 2019 (UTC)

All reasonable requests.
  • Regarding series, IIRC, it used to do that, but that functionality may have got broken. Will look into it.
  • The (faction) exceptions work for me — for example, [17] generates "+75 reputation with [[Zandalari Empire (faction)|Zandalari Empire]]". Can I have an example of a page that doesn't do that?
  • Can I have an example of an NPC with a "v2" race?
- Linneris (talk) 17:09, 23 November 2019 (UTC)
The faction exception request is for NPCs / Npcboxes. Here it lists only "Zandalari Empire"
And it's not even formatted as a link. It should be. Will add this to my todo list. - Linneris (talk) 21:24, 24 November 2019 (UTC)
"V2" example --Mordecay (talk) 17:26, 23 November 2019 (UTC)

One more small thingy, here, it shows 17 850 experience, but the extension only loads "850". It should load it as "17,850" in the infobox and the rewards section. --Mordecay (talk) 20:19, 24 November 2019 (UTC)

Could be your browser's locale settings, since it shows 17,850 experience for me and the extension correctly parses it. I'll test with a locale that uses space as the number separator. - Linneris (talk) 21:03, 24 November 2019 (UTC)
Browser locale doesn't seem to affect Wowhead, it always formats numbers with the comma for me. Will add a workaround regardless. - Linneris (talk) 21:09, 24 November 2019 (UTC)
Uploaded version 2.0.9 for Firefox with the requested changes and fixes, but the Chrome version is still pending review. I'll update the main page when the extension is updated for both browsers. - Linneris (talk) 11:21, 13 May 2020 (UTC)
2.0.9 is now published in both Firefox and Chrome. I apologize for the long delay. - Linneris (talk) 13:21, 13 May 2020 (UTC)
Thanks! --HordeRace bloodelf male.jpg Mordecay (talk) 17:34, 13 May 2020 (UTC)
thanks on the new update (Yuvalal (talk) 17:39, 13 May 2020 (UTC))
Thanks for the update! :-) PeterWind (talk) 09:06, 14 May 2020 (UTC)

Item pages

Heloo When i am going to item pages on wowhead such as https://www.wowhead.com/item=39354/light-parchment I cant open the tool kit. I dont know why . but i would like to see there sold by and reagent for list, thanks. (Yuvalal (talk) 14:28, 2 January 2020 (UTC))

  • Item pages are currently not supported, only quest, mission and NPC pages. I could implement support for item pages in the future, though. - Linneris (talk) 13:21, 13 May 2020 (UTC)

A report

ran into a bug on the final The Defias Brotherhood quest (https://www.wowhead.com/quest=166/the-defias-brotherhood). when i click the editor's toolkit button, it pulls up the window as usual, but the only content is this: n.nextElementSibling.getElementsByTagName(...)[0] is undefined

i checked a few other quests and they seem to be fine. turning off uBlock Origin and my Stylish styles doesn't change it, and it happens on both regular and classic wowhead. oh, and i'm using firefox —Eithris (talk) 00:16, 26 February 2020 (UTC)

here's another quest that gives this bug (in case more examples might help find the cause): https://www.wowhead.com/quest=58/the-night-watchEithris (talk) 02:07, 13 March 2020 (UTC)
Fixed in 2.0.9. - Linneris (talk) 13:21, 13 May 2020 (UTC)
sweet, ty ✌️ —Eithris (talk) 18:29, 13 May 2020 (UTC)