Template talk:Quest infobox/Archive2009

Acceptance awards?

Some quests have rewards for accepting the quest, not just for completing it. Would it make sense to document these?

mtew 17:28, 24 December 2008 (UTC)

I've seen a few such quests already being specifically noted as getting rewards as the quest is accepted. If you see some quest articles not mentioning it, update it. -- ab.er.rant 15:18, 29 December 2008 (UTC)

I have added quest infobox parameters for rewards. Often, the information is already elsewhere in the article, but it is not uniformly labeled. Unless someone else wants to, I do not intend to modify the infobox to display the added information. I've added 'acceptance'. 'experience' and 'completion' reward parameters to all the Pre-Searing quests. I want to see how to get the information with DPL. If I get it to work well, I'll add the information to other quests as I get to them.

Also, a lot of the quests have a 'please update' (or words to that affect) mark. If I check the article against the formatting standard, and think it's OK, should I pull the mark? mtew 18:44, 30 December 2008 (UTC)

Hmm... so you plan on using those values only for DPL? There might be a chance of mismatch, but then again, it's not a big problem. I don't really have much input for quest as I'm only minimally involved. Other users might have better ideas about this. When you say "mark" do you mean the stubs? It should be fine, but the stubs are removed as per the quest articles project, so maybe just scan through that project and see how they go about it. -- ab.er.rant 04:36, 2 January 2009 (UTC)

The DPL result will make the information available as part of its output, but The intention is not to make it directly available on the quest page.  I have started a discussion in the quest project talk pages.  I'm a bit distracted at the moment, so I don't recall exactly where.  I did bring the quest project's check-list Pre-Searing entries up to the form where all of them use the check list entry template.

I'm not sure that all the marks are in the form of '-stub's, but stubs are one kind of mark I was going to check and possibly remove.

I've also asked for an improvement in the quest formatting guideline.      mtew 19:30, 2 January 2009 (UTC)

Make it pretty/readable?

Backsword has asked about an alternate formatting for this template. Mostly he seems to have added line breaks that make the code more readable. The current coding is pretty horrible when trying to read it, and it is difficult to see if he has made any substantive changes.

Unless someone objects, I will add line breaks here so the two can be compared, probably late on the 8th.

mtew 04:36, 6 April 2009 (UTC)

Have you considered making a copy of it in your userspace so that if you make any mistakes it won't reverberate across the wiki? --JonTheMon 13:03, 6 April 2009 (UTC)

Since the only change would be the formatting of the code, and its function would not be changed, there should be no 'reverberations', but a safety net is always a good idea. WILCO. mtew 03:40, 7 April 2009 (UTC)

Well, even if it's only some formatting changes, there might be a mistake, and even if the final product is different, it might need to recache it or something, increasing server load. --JonTheMon 04:03, 7 April 2009 (UTC)

Agreed with Jon. Even if it's only formatting, chances are something could breaks in the process. Test it on your userspace first, and if everything works fine there then the change can be done.--Fighterdoken 05:27, 7 April 2009 (UTC)

Both of you, read the next to last clause of my previous response. It implies intended compliance with Jon's request. Also, check the meaning of 'WILCO'. GRUMP! mtew 13:51, 7 April 2009 (UTC)

Well, i was trying to clarify my request and give some reasoning for it, since I didn't mention the caching thing the first time. Sorry that i didn't make that clear. --JonTheMon 13:57, 7 April 2009 (UTC)

And I got that you were going to do it, it just didn't come across in my response. --JonTheMon 13:57, 7 April 2009 (UTC)

Well, given that we kinda already told you on your last template modification to test it first, but you were asking here again for doing the changes right away, i thought insisting on the topic was needed XD.--Fighterdoken 17:44, 7 April 2009 (UTC)

FD: The problem with the old edit did not break anything in main space. There was a problem with how I used it on a test page. Also, you have a strange sense of 'right away'. Two days ago I said I would start to do something late tonight (that is a couple hours in the future at the moment) and when Jon mentioned it, I agreed to check the changes before copying them back here. grump, GRUMP! (I have a headache – probably dehydration.) mtew 22:13, 7 April 2009 (UTC)

I think we should discuss any changes you want to make here, as opposed to the talk of User:Mtew/Projects/Drafts/Quest_infobox. Ok, is there a reason that there's an extra space below the title of the box? --JonTheMon 22:29, 7 April 2009 (UTC)

(Reset indent) No — fixed. Sorry FD, I meant I was not originally planning to do anything till tomorrow night. I didn't even took at the draft results. A little surprise in the IRS department has really ruined my day. mtew 04:41, 8 April 2009 (UTC)

Type and Category

Wrong 'infobox' - moved to 'Location infobox'. mtew 21:06, 13 April 2009 (UTC)

OBJECTIONS!

1. The 'campaign' is NOT optional. Every quest, mission, mini-mission and so on is associated with 'Core', a campaign or a festival in a campaign.
   
2. The 'region' is NOT optional. Every quest, mission and so on is associated with a region.
   
3. The 'section' is redundant. It is either 'Primary' or regional. Some quest like activities do not have sections in the quest log.
   
4. Pre-Searing Ascalon and Post-Searing Ascalon are NOT the same region.
   
5. The mini-game categorization has been stripped.

--The preceding unsigned comment was added by User:Mtew (talk).

In it's current state

1. campaign is not optional.
2. region is getting used in stuff, but doesn't have a field of its own.
3. I think he's going for "Quest log section" which could be useful, but doesn't exist yet. (link goes nowhere)
4. Where are those 2 mixed up?
5. There is now a "minimission" flag.

Also, the first image (above the info) is no longer "map", but "image". And it looks like the categories were condensed into 1 area. --JonTheMon 15:17, 14 April 2009 (UTC)

1. campaign – There should be a categorical warning issued if it is not set.
2. 'region The region where this quest is given. Optional.' – That should read Mandatory and a categorical warning issued if it is not set.
3. section – Its value can be constructed from type and region. It should be available as an override and, as such, be optional. There should not be a categorical warning referring to it. The warning should reference region instead.
4. The Ascalon (pre-searing) region is equated to 'Ascalon' here – '{{#switch:{{lc:{{{region|unset}}}}} | ascalon (pre-searing) = [[Category:Ascalon quests]] | unset = [[Category:Quests that need section set]] | #Default = [[Category:{{{region}}} quests]] }}'. I can see the removal of the parenthesis, but the result should be 'Pre-Searing Ascalon', not just plain 'Ascalon'.
5. 'minimission' is not the same as 'minigame'. The auto-categorization of 'minigame's was removed.
6. Doesn't changing map to image mean that every Quest infobox that has a map will have to be changed? If so, it should have been discussed first.
7. I'm all for a consolidated categorical section. I believe that all the 'cat' stuff should be close to the 'here be kittens' comment. :-)
8. The id is listed as mandatory but did not exist before. Requiring it will break every Quest infobox invocation. Further, if it is related to the 'Game link:quest' links, they are not unique; there are several links that connect to the same page.

mtew 11:09, 15 April 2009 (UTC)

"Categorical warnings" are always bad; if people simply do not have the information, a big red box (or what exactly do you imagine?) won't help. Because then they will more likely stop editing the page at all, meaning no information at all, or the visitors will be distracted by that warning.

Maps are displayed at the bottom of the infobox, that is consistent to the other infoboxes that involve maps and images; so nothing will break just because image was added and the maps were moved to the bottom.

The id is not displayed and as such it will not hurt if it is not set, however it should be added - if possible - to all quest articles. And in general ids are by definition unique. That we have some game links that link to the same page doesn't mean that the ids are not unique; it just says that we don't bother creating an extra page just because the game needs to differ there. poke | talk 11:37, 15 April 2009 (UTC)

In this case 'categorical warning' means put in a category reserved for problems, as in 'Quests that need campaign set'. No big red boxes.

Sorry - scratch the 'map' objection.

The problem with id is marking it 'mandatory'. I've been adding the 'Game link' identification numbers as I go along. It should be the same as the id and allows for multiple links. If that is not what this is intended to be, it needs to be documented better. There are also other things, like professions, locations and skills, that have similar ids.

That leaves a number of issues that should have been discussed before being put into effect. mtew 12:34, 15 April 2009 (UTC)

4. Currently a pre-searing Ascalon quest is put into the category 'Ascalon quests' if it's a secondary quest, but not if it is a primary quest. What is the reasoning behind that? Since pre-searing quests are automatically put into the 'Ascalon (pre-Searing) quests' by code later in the text, shouldn't the line

|ascalon (pre-searing) = [[Category:Ascalon quests]]

be scrapped, since there is no need to put it into a additional category ? Or replace it by

|ascalon (pre-searing) =

if it is intended to change the currently redundant default case of that switch later on. --Alfwyn 22:29, 17 July 2009 (UTC)

Section

Factions repeatable quests are listed under the explorable area in which they are found. For example, Scouting Maishang Hills is listed under the "Maishang Hills" section in the quest log, not "The Jade Sea Quests." The current implementation of the infobox automatically adds "Quests" at the end which isn't needed for these quests. Tedium 02:43, 15 June 2009 (UTC)

Profession specific quests

It has been proposed, as a more detailed proposal stemming from an earlier discussion, that profession and nationality pre-requisite information be added to the infobox, both for display and for use in DPL tables (e.g. List of Prophecies quests). An example has been created to illustrate how this might be done and what it might look like. Consensus seems to have been reached, but a final call for feedback is now being made. --DryHumour 23:43, 4 September 2009 (UTC)