Template talk:Quest/Archive01

This is an archive of: Template talk:Quest

Please do not edit this page- add comments or edits to the original page!

Quest Difficulty?

What about adding a section to the Quest Template specifying how difficult a quest is (easy, average and so on)? This could go in the map box after Duration.

I started to add this myself but wasn't comfortable monkeying with a template.

Snarf, 5/28/10

I second this suggestion, I'd like to see a 5-point scale difficulty rating for the quests Sarkastik (Contributions • Message) 12:34, September 22, 2012 (EDT)

New Template?

What about a quest template similar to this that would add a little more information. It also does away with the small info box since parts of that box need more space than is really provided for it - Sojourner9 13:16, January 5, 2007 (EST)

I deleted the actual template from this page (it's a talk page) but you can find it in history if you need to refer to it. Yes, that sounds good to me - go ahead and create the new template (you can just write it over this old one) if you like, or you can create a new template for this, call it quest_article or something like that perhaps. Maybe move this one to quest_infobox - make sure you check the 'what links here' for this old template and update all the transclusions to work with the new one! elliottcable (talk, site) 13:51, January 5, 2007 (EST)

Any issue with calling the new one Template::Mission - then as we update the quest pages, change them to Mission template. That would make sure that unchanged pages would not be broken since they would continue to use Quest template until updated also. Sojourner9 14:13, January 5, 2007 (EST)

The only thing I'm worried about is people using the wrong one in the future - perhaps use the move button to move Template:Quest to Template:Quest_old... I believe template still work through wiki redirects. Might want to double check that though. Then, add a noinclude'd warning at the top of the quest_old template not to use it... then yeah, Template:Mission would work fine. Sounds good! Go ahead and create the template to your liking, but let me fiddle with it before you start mass editing pages with it. elliottcable (talk, site) 19:14, January 5, 2007 (EST)

Ok, I've created a Template:Mission and pointed the Steal the Healing Elixir quest at it. Take a look, see what you think. Once we get it down, I can move the old Template:Quest to become Template:Quest_Old and then move the Template:Mission to become Template:Quest - Sojourner9 15:42, January 11, 2007 (EST)

Templates

Ok, some things I've learned the hard way from the item and spelldescription templates. 1) You don't want to use sections in your templates. Otherwise, people will try to use the little 'Edit' links on the right had side of the screen to add info, but those edit links take you into the template's edit page, not the quest's edit page, and you'll get random info inserted into the template (and therefore into all quests). 2) Template parameter names are case sensitive, so don't mix case on them. This way when entering data for a fresh quest, people don't have to remember which params are lowercase and which are not. Dedridd 13:24, March 3, 2006 (EST)

Also - suggestion: if you put things that will mostly likely have more than one entry on a newline (such as {{monsters}}, {{opt}}, and {{chestloot}} ) like you did with {{traps}}, then you can use **'s in the values when filling out the params to indent and/or put in lists. I'm not sure if you like this kind of format or not, but it would unjumble the monster list on the The Low Road quest, for example, by allowing something like:

Monsters:

Dedridd 13:32, March 3, 2006 (EST)

I tried that first, but it didnt work. I fiddled around with it more and fixed it. -- koolkat 13:40, March 3, 2006 (EST)

One last question - should these also be in Category:Quests? If so, you might want to put that in the template with an includeonly tag. Dedridd 13:53, March 3, 2006 (EST)

Unfortunately I am not sure how the includeonly tags work, could you change it and then I can see what you did? -- koolkat 14:50, March 3, 2006 (EST)

includeonly just means that anything that uses the template will go in the category, but it keeps the template itself from showing up as part of the category. I had to do a quick edit and save of the Survive the Low Road page to get it to update its categories though (just an fyi, you need to do that sometimes with messing with categories in templates). Luckily that's the only quest using the template so far. :) Dedridd 15:02, March 3, 2006 (EST)

Also, have you already seen a chest with a non-random loot? Tihocan 13:56, March 3, 2006 (EST)

The chest loot was an attempt to elucidate the loot tables from random drops to try and see what level quest you would need to get a +3 sword versus a +2 sword for instance. It has been rolled into Knownloots -- koolkat 14:50, March 3, 2006 (EST)

EXTREME CHALLENGE DUNGEONS.

Turbine has designated a buncha quests "extreme challenge".. Pops up a warning before you enter, if you have tips on. Since I and most ppl like to turn off tips at some point, would be nice to maintain a list here of what they actaully flagged as that. Was gona just add the category but I guess quest cats are mostly done automagically thru this template? Can we get that added or should I just make a regular page?

Few I can think off of top of my head: Proof is in the poison Clearing the air Spies in the house Stealer of souls --Shade 01:04, May 24, 2011 (EDT)

Done... ShoeMaker 01:30, May 24, 2011 (EDT)

Prevent txt Category:Level {{{level}}} quests txt from showing on a quest page

Trying to prevent the text [[Category:Level {{{level}}} quests]] from displaying like it does in In the Belly of the Beast (at bottom of page near Monster Information} when {{level}}/{{lvl}} is 0|no|false|none aka Heroic quest not available but epic is. Think the {{#switch:{{{history}}} is the cause. Any ideas to go about it? Bladedge (Contributions • Message) 19:36, September 19, 2012 (EDT)

It looks like if history value is used to flag the quest as retired, if history is not there, it assumes quest is active and tries to put the category for the appropriately defined "level" quest. Since this particular quest ( and likely future quests ) may not have a level ( for these purposes meaning heroic level ) defined, my suggestion would be to simply put an if statement surrounding the part that displays the category. Something along these lines : {{#switch:{{{history}}} |yes= [[Category:Retired quests]] |#default= {{#if:{{{level|}}} |[[Category:Level {{{level}}} quests]]}} [[Category:{{{zone}}} quests]] [[Category:{{{patron}}} patron quests]] }}

A better long term solution might be to avoid relying on the history tag to not be set to determine what categories get displayed though, maybe create a new flag called 'retired' for quests that are in the retired category, and if zone is populated, throw it in that category, if level is populated, throw it in that category, etc. etc. Joenuts

Thank You for the help. So far its working as I want it to. Probably should avoid using the history tag, but Ill wait a few days see if there is anything else not working correctly or over looked before I mess with the code again. Bladedge (Contributions • Message) 13:49, September 20, 2012 (EDT)

Quest Zones

I find the ways quests are categorized by the zone they are given, rather than the zone that are located in, rather annoying. For example when I look up quests in the Cerulean Hills I expect to see 2 quests, but there's only 1 since one is given out in the Harbor.

Maybe a new "zoneLocated" could be added to the Quest template to specify where the quest is located? I don't have any experience with templates so I don't know how powerful they are....is it possible to do this in such a way that the value defaults to the 'zone' value, if zoneLocated isn't explicity specified? And of course quests should be categorized by the new zoneLocation value, instead of 'zone'.

Thoughts? Sarkastik (Contributions • Message) 12:53, September 22, 2012 (EDT)

If I understand correctly, you're suggesting to collect the information of the zone where the actual quest entrance is located. The "Takes place in" data for quests is already collected, but that data is quite useless as it's just an arbitrary name of the area once quest is entered. I >DO< see value in collecting the information of where quest entrance is, I would not call it zoneLocated, but Quest_Entrance_Zone or something along those lines. I >DO NOT< see value in making the default entrance location the same as quest acquired in. I can think of too many examples of quest entrance being different than quest acquired to rely on that as a default.

Adding the variable to the template would be pretty easy, even associating quests where that field is populated with a new 'quest that take place in <location>' category would not be difficult. My opinion is that it would be useful information, and that it should be implemented.→ Joenuts

Something like :Template:Sandbox/Bladedge. Not sure if its possible to rename the 'zone' value without causing every quest page infobox from acting up or displaying errors. I just add or repurpose the parameters that are in use. Could probably remove zone and loc and add more clearer naming. 'zone' would become 'acquired' , loc would be 'dungeon'. Afterwards all quest pages would have to be edited to add and populate the new parameters and remove the old. Bladedge (Contributions • Message) 17:02, September 23, 2012 (EDT)

Noted and added to my virtual to-do list (the one in my head for now)... ShoeMaker (Contributions • Message) 11:26, September 24, 2012 (EDT)

I think that template is a step in the right direction, exactly what I had envisioned. I copied and made some minor changes Template:Sandbox/joenuts. You can see what it looks like when referenced here : Sandbox/joenuts. The level variable at some point changed to lvl on your template, i had to change it back to display properly. I changed the region variable to entrance, and put a statement defining the category based on entrance variable. What I like about the approach is that if the quest template is referenced without an entrance variable defined, it will categorize those in to 'quests that take place in unspecified' which can then be used to track down all quests that need to be updated. On the comment about renaming variables ( zone to aquired / etc ), I believe that unless the renaming is automated it's not going to be worth the time to update every declaration. I think the precedent has been set for generic / smaller variable names for the sake of simplicity ( ease of use ) and flexibility ( "location" can mean anything we want it to mean ). It is what it is, only thing is that it may be confusing if it's not documented clearly in more detail what the variable is really supposed to be, but I dont think in something like this wiki that really is a big concern. Joenuts

[Template:MissionInfoBox] is nested in this template. Did not change a thing with 'lvl'. 'lvl' is correct for the Template;MissionInfobox (the one in my sandbox), 'level' is correct for Template;Quest. Iam editing the MissionInfobox not the Quest template,which would be done afterwards. Technically this discussion should be taking place here [Template_talk:MissionInfoBox] but it started here. Bladedge (Contributions • Message) 13:53, September 24, 2012 (EDT)

Quest Givers

I'm starting to working out on the individual NPC pages, and was thinking if it would be possible to make the bestower/npc camps to link to their NPC articles, just like the patron/zone camp link to the patron/zone page. I'm not versed enough in wikicode to try to mess up with a vital code like this one. Thank you. → Nibelung (Contributions • Message) 12:13, December 12, 2014 (EST)

Sure, it is possible, but before we do that, someone needs to go through all of the quest pages and make sure that none of them already have it linked. Failure to do that would result in double linking brackets which look really bad and unprofessional in my mind. Let me know once that is done, thanks! ShoeMaker (Contributions • Message) 19:13, December 12, 2014 (EST)
- Done. Nibelung (Contributions • Message) 01:01, December 13, 2014 (EST)
  - Template updated; NPC is now linked. — Zav (C·T·E) 01:29, December 13, 2014 (EST)

Extraneous Text since Template Upgrade

Quests now seem to have extraneous indented text after the Monsters section... unparsed "Category:Level xx quests" text. --Thalone 18:21, August 29, 2015 (EDT)

Erm, to clarify. It seems to only happen for some subset of quests; I haven't figured out what the condition is. Flesh Maker's Laboratory is exhibiting the behaviour. --Thalone 18:31, August 29, 2015 (EDT)
- I fixed the Necro 4 quests. It is caused by having a link in the |level= or |epic= parameters instead of just a number. — Zav (T·C) 02:08, August 30, 2015 (EDT)
- That is the cause, yes. If that is happening, why were there links there? Should pages be merged? ShoeMaker (Contribs • Message • Email) 07:59, August 30, 2015 (EDT)
  - They were duplicate links to the other version of the quest. |heroicxp= or |epicxp= already contain the same link. The heroic and epic versions of the quests are similar; however, some have different monsters and/or objectives. I am neutral on merging. - Zav (T·C) 09:03, August 30, 2015 (EDT)

Forum complaint - heroic lvl not displayed

When updating the template, please also check out this post: DDO Forums --Cru121 (Contribs • Message • Email) 07:14, December 23, 2015 (EST)

It's not the only comment on it either. I've responded and will roll back my changes until I can completely recode the templates. ShoeMaker (Contribs • Message • Email) 10:01, December 23, 2015 (EST)

Raid XP not showing

I may be missing something here since I'm terribly out of date with what's going on in the wiki, but the amount of xp granted is not being displayed on raid pages and I'm assuming this is some kind of mistake. If this has been discussed before, I apologize, but I couldn't find anything in the revision history or on the discussion page to suggest it is intentional. If someone in the know could take a look at this issue I would appreciate it! Susalona (Contribs • Message • Email)

It's one of the issues with the code changes. I'll be recoding this template and dependant templates in the first half of January from scratch basically. ShoeMaker (Contribs • Message • Email) 10:11, December 23, 2015 (EST)