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 and only from the headingzone, a category should be created. I would also keep heading for backwards-compatability.
 * headingzone (major zones or instances) and
 * headingsubzone (minor zones or subzones in instances if applicable)

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 &rarr; 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: Quest: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 &middot; 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. 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! :) 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 ? Naming conventions seem to dictate that it should be. 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 instead of  --  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  .  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. --  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: " has been changed. Does someone who has editing privileges stop by and comment on this?-- 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 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= . -- 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. 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. 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 &middot; contr) 5:28 PM PST 13 Jun 2008
 * Nevermind... looks like the change takes effect on most reloads. It even shows up in tooltips . --[[Image:gengar orange 22x22.png]] Fandyllic  (talk &middot; 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. 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 . 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: Quest:A Gently Shaken Gift, Quest:Torch Tossing, Quest: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 &lt;sup&gt; or &lt;sub&gt;?--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)". 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
Rewards didn't really work with unordered lists - the first bullet doesn't translate the * into a bullet.

Second, have you thought about adding 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 disambigpage"? There's quest disambiguation templates, if that's what you mean. 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. 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. 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?

-- k_d3 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_d3 00:52, July 20, 2010 (UTC)
 * I agree to condensing or removing them. -- 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...


 * This? -- k_d3 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? 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_d3 02:29, July 21, 2010 (UTC)
 * HA... understand Kay did, Sky. 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. -- 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. -- 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)