Template talk:Questbox

Changing of 'heading' parameter

I suggest we change it so it looks like e.g. Valley of Trials (Durotar) so we'd need new arguments like

• headingzone (major zones or instances) and
• headingsubzone (minor zones or subzones in instances if applicable)

and only from the headingzone, a category should be created. I would also keep heading for backwards-compatability.

comments please ;) -watchout 16:19, 11 January 2007 (EST)

As much as I realize the practical value in doing so, I disagree. The zone of the quest, 90% of the time, is pretty apparent from the header. The real reason we're doing it that way is because quests can easily be data-mined/categorized/indexed by the exact same system that the game uses. And for that reason alone we're going to stick with just the heading. Concerns about outlining where the quest actually happens, i.e. Un'goro Crater and not Orgrimmar, should be outlined in the first paragraph of the quest article or in an outside article like a quest guide citing the quest. --Hobinheim (talk · contr) 16:33, 11 January 2007 (EST)

ok, youre absolutely right, I misinterpreted the parameter and don't know why because its actually clearly written in the template description (I thought it's heading like heading to x) -watchout 16:45, 11 January 2007 (EST)

The discussion above is no longer relevant since I changed the parameter from heading to category. That should clear things up.--Hobinheim (talk · contr) 22:58, 21 January 2007 (EST)

{{Questbox}} work still to do: heading → category

I think that User:Hobinbot has a job to do now... change all the heading parameters in old questboxes to category. --Fandyllic (talk · contr) 12:49 PM PST 25 Jan 2007

Bot Convertion

I am considering using bot to convert old table style to use this template. However, I have some issue with available information. Take for example this:   [10] Forged Steel, I can only get faction, name, start, level, levelreq, experience from the box. This is limited. I am wondering what should be done for other two required fields (rewards and end). (My bot is not smart enough to read the rest of the document) --Voidvector 18:57, 30 January 2007 (EST)

You should probably just go ahead and go for it. Maybe add a stub tag at the top of the article. Of course it's not a one to one conversion...--Hobinheim (talk · contr) 11:01, 1 February 2007 (EST)

There might've been some mistake made during the conversion. I believe they are all minor.

1. Because people often used "Subzone, Zone" notation for "where" row in the old table, I converted the zone to "category". This however is not always the case. (e.g. It caused articles to be categorized under Category:Quests:Barrens instead of Category:Quests:The Barrens)
2. I used wild card for XP row and rep row, since people often left them out. This may cause some mix up between the two, but I didn't find any during my spot checks. --Voidvector

id issue

Id for Thottbot, Allakhazam, and Wowhead are not identical for all quests. --Voidvector 13:04, 2 February 2007 (EST)

Yeah, I think I'm going to change the template so it will use id for only when Thottbot and Allakhazam are the same, but add idt for Thottbot-specific and ida for Allakhazam-specific (and WoWHead?) IDs. Maybe someone can add IDs for other DBs. --Fandyllic (talk · contr) 3:51 PM PST 2 Feb 2007

As far as I know, Alla and Wowhead use identical numbers. --Voidvector 20:10, 2 February 2007 (EST)

In most quest cases, they all use the same numbers, I think.--Sky 17:34, 15 February 2007 (EST)

Doesn't use Cost template

I think really it is just the example that doesn't use Cost but it probably should be changed. User:Kitan/Sig 15:24, 12 April 2007 (EDT)

Aye, it's just the part where it explains how to add in the money values that needs changing, both the Source and Example use the Cost template, however. Could do it yourself you know! :) User:Kiltek/Sig 19:00, 12 April 2007 (EDT)

Group quests, raid quests, elite quests

Seems that we're using the 'type' field to indicate Group AND how many people are recommended. Is Okay, but we don't also have a good way to organize group quests. "Quests at 70g5" just doesn't work for me. Suggestions? --Eirik Ratcatcher 23:15, 29 May 2007 (UTC)

Ditto this - if it's a Group Quest / Elite Quest, whatever the game wants to call it now, mods that read the quest level read a G and sometimes a number on it for number of people. But if we list that as part of the level for the quest, it doesn't link properly for the "Quests at X" category. Is there anything that can be done about this, either on the server end or on the contributor end? Hekirou 17:49, 5 July 2007 (UTC)

Category naming conventions

Should the quests really be organized under [[Category:Quest:Zone]]? Naming conventions seem to dictate that it should be [[Category:Zone quests]]. I understand that all zone categories have a Zone: in their namespace, but there is some notion in the community to abolish this practise. The main reason this hasn't been put into practise is because it requires a bot (there's been a request sitting in WW:BR for a long time that no one seems to want to do). However, since most quests are categorized automatically by Questbox, it makes sense to immediately impliment this. I'd do it myself, but I want at least someone else to agree with me before I do. --Mikaka 07:54, 3 August 2007 (UTC)

Similarly, I suggest that profession quests should be under [[Category:Quests:Profession]] instead of [[Category:Profession]] -- Mordsith - (talk|contr) 12:31, 4 January 2008 (UTC)

Coming back to my comment after having worked on the zone category project, I change my previous statement: The category should be something like [[Category:Blacksmithing quests]]. But if you are removing the automatic categorizing from the questbox, then this would just be something people need to keep in mind when manually categorizing. -- Mordsith - (talk|contr) 14:21, 11 June 2008 (UTC)

Poking at this thing. Sounds better with "The Barrens quests" then "Quest:The Barrens", even now when the "Zone:<zone>" has been changed. Does someone who has editing privileges stop by and comment on this?--g0urra[T҂C] 20:52, 8 June 2008 (UTC)

The problem with this at the moment is that a lot of articles have had the categories custom-placed on the article, rather than in the questbox, to which end, I think having a bot deprecate the "category" tag may be a good idea, as category links are easier to maintain... --Sky (t · c · w) 20:57, 8 June 2008 (UTC)

Wrong answer, really. You can only safely remove an explicit category tag if a) it duplicates the tag in the questbox, or b) there IS not tag in the quest box. Many's the category I've added to quests because while the quest itself is filed under one category in your in-game quest list (the questbox category), it is at least as relevant to some other category - zone, tradeskill, whatever. Please don't wave a one-size-fits-all removal over this. --Eirik Ratcatcher (talk) 18:34, 9 June 2008 (UTC)

Eep, not what I meant at all. I was suggesting the |category= function be deprecated in favor of the normal kind of category tag, and a bot used to switch them. --Sky (t · c · w) 18:46, 9 June 2008 (UTC)

Width of box

Since the width is set and cannpt be altered in pages, can it be increased slightly? Adding coordinate boxes to the players names mean a lot of them are getting chopped in half because of the name lengths of some NPCs. Take  [60] Ice Thistle E'ko for example. Needn't have much added, maybe just 2 to the width (or allow it to be customised). Sanderdolphin 11:40, 15 December 2007 (UTC)

Added parameter width=. --Pcj (TDrop me a line!•C207,729 contributions and counting) 13:59, 4 January 2008 (UTC)

Shareable quests

I would like to see an additional field in the quest box that states whether a quest is shareable or not. (Reeina 19:02, 13 January 2008 (UTC))

As a general rule, if the questgiver gives an item with the quest, its not sharable. 99% of the other quests (that don't recieve items from the quest giver) are sharable. So there's really no point to having it, but thats my opinion. Sssssssssssssssssssssssss For Pony! ^{{TDon't hiss at me.•CIf you do things right, people won't be sure you've done anything at all.)} 05:31, 16 January 2008 (UTC)

Daily Quests

I've seen two approaches for indicating a daily quest. "type = Daily" and "repeatable = Yes (daily)". Personally I prefer the latter and suggest specifying this as the standard convention for daily quests. Thoughts? --Cjt 14:14, 27 March 2008 (UTC)

Level vs Levelreq

there seems to be some new template displaying "yellow/green/white/gray" on quests. This template does not appear to observe the constraints of Levelreq. I set level = 60 and levelreq=60 and this template displays "58" as yellow... --Eirik Ratcatcher 22:16, 4 April 2008 (UTC)

yea, thats been bugging me too. Seems it shows, at what level when the color changes. Sssssssssssssssssssssssss For Pony! ^{{TDon't hiss at me.•CIf you do things right, people won't be sure you've done anything at all.)} 22:19, 4 April 2008 (UTC)

levelreq ignored by level list

As mentioned above there is a level series with colors which is misleading because it says that a quest can be obtained before it actually can. Specifically all the Cooking and Fishing dailies are listed at 68, when the levelreq says 70 and the actual ability to obtain them is also level 70 --WoWWiki-Dga (talk) 21:30, 19 May 2008 (UTC)

Level requirements should be treated better by the level strip now; some of those fishing dailies do lacking levelreq and fail to account for it because of that. -- foxlit (talk) 23:30, 30 May 2008 (UTC)

Levelrule and level

I added a new "white=" parameter to the {{levelrule}} template (the thing that spits out colored level numbers) and had the {{questbox}} pass the quest level to white=. I was sick of not being able to find out the actual quest level reported in-game. Now the quest level number appears as white between the yellow and green numbers. Unfortunately, I'm not sure if this change will propagate that fast, so you will still not be able to see the actual quest level in many cases for awhile. -- Fandyllic (talk · contr) 5:28 PM PST 13 Jun 2008

Nevermind... looks like the change takes effect on most reloads. It even shows up in tooltips . -- Fandyllic (talk · contr) 5:30 PM PST 13 Jun 2008

Required Level issue

For some reason like for example you can have a quest that requires level 18 but instead it comes up as 20, is this some kind of problem in WoWiki's engine? --User:YuriElite

What do you mean? User:Coobra/sandbox ← Seems fine to me. Sssssssssssssssssssssssss For Pony! ^{{TDon't hiss at me.•CIf you do things right, people won't be sure you've done anything at all.)} 07:36, 16 July 2008 (UTC)

Well let me give an example of what I mean, say we were talking about the level requirement for the quest "Arugal Must Die", the level requirement for this quest is level 18 but on WoWiki for some reason including loads of other quests it only says in 5's or 10's which I find is odd and strange. In other words it's level requirement is level 18, not level 20. --User:YuriElite

Oh that. Well, it simply ran out of room as it's a level 27 quest and it shows at what level it becomes more difficult. From not very much so, grey, to you shouldn't try alone, red. It would act the same if the quest was a level 70 quest and required you to be level 1, which I added to the examples → User:Coobra/sandbox. Sssssssssssssssssssssssss For Pony! ^{{TDon't hiss at me.•CIf you do things right, people won't be sure you've done anything at all.)} 21:26, 16 July 2008 (UTC)

Unleveled quests

Many of the Event quests show up for all levels of character: quest level = 70 (?), required level = 1. Examples:  [10-70] A Gently Shaken Gift,  [1-70] Torch Tossing,  [1-70] Now This is Ram Racing... Almost.. The current quest level display does not, IMO, present this information in a useful fashion.

Instead, it show "the quest will be red at 63" ... which does not tell anything about what level you are eligible to pick the quest up.

And more amusing, it shows "the quest will go grey at 79"... which might be true after the next update, but is certainly not true currently.

An idea... Perhaps the level you are eligible to take the quest should be at the first of the series: "1...63 66 68 70" Another idea: the two levels (quest and required) could be emphasized by use of <sup> or <sub>?--Eirik Ratcatcher (talk) 17:35, 17 July 2008 (UTC)

Or maybe we could just use the "old" version where the required level was in brackets. For example quest level is 60 and required is 48, it would be "Level: 60 (48)". g0urra[T҂C] 17:37, 17 July 2008 (UTC)

Please revisit this issue. We seem to have reverted to previous behavior (showing required level, and quest level). For event quests, the "level" of the quest seems to be "max level". Thottbot reports it as "-1". That is, it shows up as a valid quest for anyone above the minimum level. As the 'level' parameter creates a category inclusion, I would like the 'level' parameter given a special case for these quests. "Quests at xx" kind of misses the point for these quests. --Eirik Ratcatcher (talk) 19:05, October 8, 2009 (UTC)

Suggestions

Brewfest! (Horde)
Start	Orc Commoner, Troll Commoner, Forsaken Commoner, Goblin Commoner, Blood Elf Commoner, Tauren Commoner
End	Tapper Swindlekeg <Brewfest Organizer>
Level	70 (Requires 1)
Category	Brewfest
Rewards	[Barleybrew Clear]  [Thunder 45] or  [Gordok Grog]

Brewfest! (Horde)
Level: 70 (Requires 1)
Orc Commoner, Troll Commoner, Forsaken Commoner, Goblin Commoner, Blood Elf Commoner, Tauren Commoner
Tapper Swindlekeg <Brewfest Organizer>

Rewards:

 [Barleybrew Clear]

 [Thunder 45] or

 [Gordok Grog]

Rewards didn't really work with unordered lists - the first bullet doesn't translate the * into a bullet.

Second, have you thought about adding {{Questbox|<disambigpage>}} like we have to {{Achievement}}? -Howbizr (talk) 01:43, 1 November 2008 (UTC)

First, you should use something like "rewards = [[item1]], [[item2]] or [[item3]]". Don't use bulleted lists in Questbox.

Second, what do you mean with "adding {{Questbox|<disambigpage>}}"? There's quest disambiguation templates, if that's what you mean. g0urra[T҂C] 01:50, 1 November 2008 (UTC)

Yes to your second question. I couldn't figure out how to do a disambig on the page using {{questbox}}. -Howbizr (talk) 13:13, 2 November 2008 (UTC)

Needs requirement tags

There needs to be a way of entering tags for race, profession, and rep required. Madkaugh (talk) 22:04, 12 January 2009 (UTC)

Use a "Notes" section in the article. g0urra[T҂C] 22:15, 12 January 2009 (UTC)

Well, yeah, I know you can cover it in the article. It's not the same thing. Shouldn't the tooltip have enough information to indicate whether the article is germane? (This came from a real life 10 minutes spent figuring out that the next quest in a chain was for warlocks only. Yes, it was in the fine print. It should be right near Level Required.) Oh, yeah, add class to the list. Madkaugh (talk) 00:48, 15 January 2009 (UTC)

Should Category= be used for all of these restrictions? Madkaugh (talk) 00:51, 15 January 2009 (UTC)

Improvements to template

I ask for the following, knowing that any change to the template will create a horrible spike of "server is busy, try again later."

1) limit categories to appropriate namespace: this talk page is currently included in several categories because a comment includes a questbox example. Categories should be added only if the page is in the main namespace, not in talk, user, help, template, category, template talk, etc.... This may be a common failing of several popular templates.

2) disambigpage parameter: Currently, the name parameter is sometimes being specified as the disambiguated page name (IE "Bashal'Aran (2)" instead of "Bashal'Aran"). At the moment, this is most significant for sorting in categories. The name parameter is used for the default sorting value for categories added by this template. If the ambiguous name is used as the parameter, then sorting is "as encountered".

That is, "Gnome Engineering" (Stormwind City) and "Gnome Engineering" (Barrens) will be sorted in random order because the sort value is limited to "Gnome Engineering" (the questbox name parameter used). By contrast the Bashal'Aran quests (using the disambiguated name for the name parameter) will sort correctly, but display the wrong name in the quest box. --Eirik Ratcatcher (talk) 22:27, 4 May 2009 (UTC)

Note on the first one, use the |doc= parameter to prevent the page from being categorized. Most templates already have this parameter. It's up to the user to use it. Sssssssssssssssssssssssss For Pony! (^Sssss/_Slithered) 02:04, 5 May 2009 (UTC)

Now y'see, that's new to me. And it wasn't in the documentation, so I would have had to see it in action, or read the (uneditable) source of the template. Feel free to correct my note about it. --Eirik Ratcatcher (talk) 23:04, 13 May 2009 (UTC)

elinks display

Would anyone be horribly opposed if I changed the "See also" links?

From

See also

Wowhead Thottbot Allakhazam

To

See also

--k_d³ 23:01, July 18, 2010 (UTC)

I've been wondering about removing them completely, actually. "External links" is perhaps the global standard now (though not implemented on every page; perhaps a bot could be run to convert the quest pages lacking such a section), and is preferable for our purposes of a) keeping users on our pages, and b) ensuring wiki-wide conformity. I think such a change that you propose would be a good one, but not necessarily the correct one. --Sky (t · c) 02:44, July 19, 2010 (UTC)

That's something I've been percolating about as well... Perhaps just change the ID to a flat display (like "Quest ID: 1234") and stick to the elinks section at the end. This is the only infobox template that does the external-link thing, after all. --k_d³ 00:52, July 20, 2010 (UTC)

I agree to condensing or removing them. --Pcj (TDrop me a line!•C207,729 contributions and counting) 00:54, July 20, 2010 (UTC)

That might be suitable. It keeps the useful metadata in the box as well. --Sky (t · c) 02:48, July 20, 2010 (UTC)

So, then...

To

Quest ID

1234

This? --k_d³ 01:21, July 21, 2010 (UTC)

With the correct alignment of course, but yes. --Sky (t · c) 01:35, July 21, 2010 (UTC)

And what of the quest pages we have share, those that would have 2 IDs? Sssssssssssssssssssssssss For Pony! (^Sssss/_Slithered) 02:05, July 21, 2010 (UTC)

That was not understandable English... --Sky (t · c) 02:23, July 21, 2010 (UTC)

I'm probably going to go back to the shared quest pages and add them both in to the questbox. Probably: "|id=1234, 1235" --k_d³ 02:29, July 21, 2010 (UTC)

HA... understand Kay did, Sky. Sssssssssssssssssssssssss For Pony! (^Sssss/_Slithered) 02:37, July 21, 2010 (UTC)

When talk like Yoda you can, scriptwriters you need not! --Eirik Ratcatcher (talk) 22:13, August 10, 2010 (UTC)

I gotta ask... what purpose does leaving the quest ID(s) in the questbox server? I have no tools that simply plug in an ID number and get ... anything... out of. I would agree that it has uses while editing, but that purpose could be served by leaving it an "unused parameter". --Eirik Ratcatcher (talk) 22:15, August 10, 2010 (UTC)

Agreed, let's just make it a semantic value, that way those who want it can have it and the others don't have to see it. --Pcj (TDrop me a line!•C207,729 contributions and counting) 23:56, August 10, 2010 (UTC)

Problem with that chief: some quest pages have two+ numbers, usually demarcated by commas. --Sky (t · c) 01:37, August 11, 2010 (UTC)

Guess we'll make it a string then. --Pcj (TDrop me a line!•C207,729 contributions and counting) 01:40, August 11, 2010 (UTC)

Class requirements

Why is there no parameter in this template for class requirements? -- Dark T Zeratul (talk) 20:05, 14 April 2011 (UTC)

Aldor/Scryer

Any chance of expanding the Faction parameter to include Aldor/Scryer? -- Dark T Zeratul (talk) 22:45, 26 September 2011 (UTC)

It already does. Sssssssssssssssssssssssss For Pony! (^Sssss/_Slithered) 08:13, 27 September 2011 (UTC)

Repeatable Reputation Quests

it isn't listed in the Types section, but if there is not a valid value "Repeatable", there should be. (it didn't break anything specifying it as type for any of Nat Pagle's lunker turn-ins, though.) and it should modify the link tooltip generated to use the blue questionmark in front of the questgiver's name. (also, if only a STARTing Questgiver is given, an ENDing questreceiver line shouldn't be indicated as well...?) per examples I've seen with quests of type Daily, questbox property 'repeatable' should still need to explicitely be Yes. Corwin MacGregor (talk) 00:23, 9 May 2016 (UTC)

Account Bound

Would it be best to have quests that are "account bound" to show the bnet icon (and maybe without the neutral icon) when linked on an article like [[Quest:<Quest Name>]]? (e.g. pet battle quests like  [45] Bloodgazer Team Up show a bnet icon in Quest Log.) Pretty much it'll look something like: [110] Bloodgazer Team Up — SurafbrovWarcraft Wiki administrator T / C 14:05, 22 August 2018 (UTC)

Wouldn't it look a bit confusing? :o Xporc (talk) 10:47, 23 August 2018 (UTC)

How so? — SurafbrovWarcraft Wiki administrator T / C 19:14, 23 August 2018 (UTC)

When I see this icon, I expect something battle.net launcher-related Xporc (talk) 13:37, 24 August 2018 (UTC)

:omegalul: — SurafbrovWarcraft Wiki administrator T / C 13:43, 24 August 2018 (UTC)

The b-net icon shows in the quest log.

While we are at it, there are also icons for weekly quests and blue and green icons for dungeon and raid quests respectively showing up in the log that could probably replace Wowpedia's "D", "R". --Mordecay (talk) 14:15, 24 August 2018 (UTC)

Elite

i notice there's a quest type in classic that isn't indicated on quest links like the other types: Elite. in retail it seems to have been removed in favor of Group, but since it exists again with classic, it might be useful to add to the template —Eithris (talk) 04:18, 13 October 2019 (UTC)

New acronyms

Like two years ago in Legion, BfA added new types of quests, and the template should be updated again like here. The new types missing I found are "Legionfall World Quest", "PvP World Quest", "Magni World Quest", "Faction Assault World Quest", "Faction Assault Elite World Quest", "Island Weekly Quest", PvP World Quest", "Warfront Contribution", "Tortollan World Quest", "Combat Ally Quest". --Mordecay (talk) 19:43, 23 February 2020 (UTC)

I would add that Legion added some of them already as "Tortollian World Quest" is simmiliar to "kirin tor World quest" and PVP world quest already was in legion as in Towers WQ and the naga wq in azuna. (Yuvalal (talk) 19:47, 23 February 2020 (UTC))

Although there are Legion world quests that reward Kirin Tor reputation, I see no match for the "Kirin Tor world quest" type parameter on wowhead (that's two things), but I found the PvP one so added it on the list. --Mordecay (talk) 19:55, 23 February 2020 (UTC)

Kirin tor World quests as a world quests which is simmilar to tortolian world quest (minigames). (Yuvalal (talk) 19:58, 23 February 2020 (UTC))

Yep, those Kirin Tor world quests have the "World Quest" type parameter (as can be seen in the infobox here), but the tortollan world quests have the Tortollan World Quest type listed which the topic is about. --Mordecay (talk) 20:03, 23 February 2020 (UTC)

hmm. maybe to prevent having to add new types of world quests every few patches, we could use parser functions to check whether the input ends in "world quest"? something like this at the end of the switch function (so the template could check for other types first): {{#ifeq:world quest|{{#sub:{{lc:{{{type|}}}}}|-11}}|WQ}} —Eithris (talk) 20:14, 23 February 2020 (UTC)

Anything to make this easier! :D --Mordecay (talk) 20:20, 23 February 2020 (UTC)

here's the full thing that would replace the existing switch function, if anyone with the proper permissions likes the idea... :3c currently you can see a trial run of it on my main user page

also i added Elite since there was never any response on that —Eithris (talk) 20:41, 23 February 2020 (UTC)

Also add support for Bonus Objective (BO). --Mordecay (talk) 17:17, 1 March 2020 (UTC)

bump? also a slightly updated link to the thing. —Eithris (talk) 23:03, 2 May 2020 (UTC)

Level

i've noticed that, presumably because of level scaling, most quests no longer have a "recommended" level displayed on database sites--only a required level. maybe the level param could be made optional as a minor QoL for these cases? so that for instance, if nothing is given for level, the tooltip would use the required level and the infobox would display just "Requires level x" instead of "1 (Requires level x)" or "x (Requires level x)" —Eithris (talk) 02:33, 13 March 2020 (UTC)

For

Seeing how Template:Infobox ability's "disambigpage" parameter puts the "for template" above the infobox, which follows the usage on other wowpedia pages as well as on wikipedia, could the questbox's "other-faction" parameter also do that? Currently, it places the for template below the infobox. -- Mordecay (talk) 16:45, 22 April 2020 (UTC)

Covenant icons for covenant quests

Would it be possible to implement covenant icons (e.g. File:Kyrian sigil.png, File:Venthyr sigil.png) for covenant campaign quests, similar to profession icons for profession quests? Right now it feels pretty unhelpful to just use the same generic neutral icon for both regular leveling quests and covenant-specific ones with no visual distinction between them. --DeludedTroll (talk) 10:48, 9 October 2020 (UTC)

Could you provide examples of Covenant-specific quests? — SurafbrovWarcraft Wiki administrator T / C 13:53, 9 October 2020 (UTC)

All of the quests for  [Kyrian Campaign],  [Necrolords Campaign],  [Night Fae Campaign], and  [Venthyr Campaign]. -- DeludedTroll (talk • contribs) 14:03, 9 October 2020 (UTC)

Looking at the quests, there isn't really anything to go by for the specific covenant as most of the quests with the category parameter are "Covenant Sanctum"... that doesn't help. Could probably implement it by using the faction parameter if the icons were added to FactionIcon, though I'm not sure if there will be any Horde / Alliance specific quests within the Covenants. — SurafbrovWarcraft Wiki administrator T / C 14:09, 9 October 2020 (UTC)

Seconded the proposal. It looks like there are not Alliance/Horde quests for covenants. If some pop up eventually, there can be exceptions for those. With the faction param, like the Aldor/Scryers ones. -- Mordecay (talk) 18:54, 15 December 2020 (UTC)

Added support for it. Though that template could probably really use a rework. Surafbrov (talk) 17:40, 28 December 2020 (UTC)

So would anyone protest if I started adding |faction=Kyrian and the like to covenant quests? -- DeludedTroll (talk • contribs) 00:17, 29 December 2020 (UTC)

Sounds like a great idea to me. -- Dark T Zeratul (talk) 00:43, 29 December 2020 (UTC)

Go for it. -- Mordecay (talk) 17:43, 29 December 2020 (UTC)

Looking at Aiding Maldraxxus, it looks like the icons are sticking out a bit. Would it be possible to align them? -- Mordecay (talk) 22:52, 11 March 2021 (UTC)

I've applied a fix for this. Should look significantly better, tho still iffy on Kyrian. So for now, it'll completely ignore Forum:Icon sizes. (I'm going to look into improving Template:FactionIcon and the uses of all the small faction icons later on.) — SurafbrovWarcraft Wiki administrator T / C 06:18, 12 March 2021 (UTC)

Cool, looks better! -- Mordecay (talk) 09:07, 12 March 2021 (UTC)

Hide start / end for world quests

Eithris recently made it so that the box doesn't show start end lines for world quests. However, there are world quests that are actually turned in at NPCs, such as the various work order / profession world quests. Any idea how to accommodate for that? -- Mordecay (talk) 13:23, 5 March 2021 (UTC)

ah shoot, i totally forgot about those. i could probs change it so that it only hides them if both lines are undefined or defined as “Automatic”. would that work? —Eithris (talk) 20:31, 5 March 2021 (UTC)

Think that sounds good. -- Mordecay (talk) 20:59, 5 March 2021 (UTC)

I was thinking about handling it that way, yea. — SurafbrovWarcraft Wiki administrator T / C 21:13, 5 March 2021 (UTC)

all right, think i've got it fixed up. lemme know if you notice any issues ^^ Eithris (talk) 04:57, 6 March 2021 (UTC)

Category link

Yay for the category cleanup!

I'm wondering if it is possible to have the Category link point to Classic zone page? In  [18] Ignition have the Category link point to Barrens instead of Barrens? (preferably without any change to the category result on the bottom of the page because it's now perfect) -- Mordecay (talk) 22:45, 11 April 2021 (UTC)

Seems this functionality is already a thing, although hiding (Classic) is less than ideal. Thinking of adding disambigcat just for this purpose. — SurafbrovWarcraft Wiki administrator T / C 23:16, 11 April 2021 (UTC)

Done. — SurafbrovWarcraft Wiki administrator T / C 23:31, 11 April 2021 (UTC)

Cool, thx! -- Mordecay (talk) 09:05, 12 April 2021 (UTC)

Reward

Just like Template:MissionSLbox accepts "| reward =" and "| rewards =", have this template do the same? -- Mordecay (talk) 22:05, 26 November 2021 (UTC)

The | money = param doesn't appear to be working. -- Mordecay (talk) 20:39, 15 July 2023 (UTC)

ah, thanks for pointing that out. i messed it up with that last edit i did & didn't catch it because it still showed up when the rewards param was used. it should work properly now. Eithris (talk) 23:43, 15 July 2023 (UTC)