GuildWiki talk:Style and formatting/Quests

End of Quest Text
I am of the opinion we should add end of quest text that the NPC usually says before accepting the XP. There are a lot of good story bits contained therein, and although it is a spoiler, I feel it can be artfully done to minimize any unwanted spoilage (although people who don't want to be spoiled that are looking at the quest page are very rare, I would think). I am up for taking on this project, if no one objects. --Ravious 09:06, 1 February 2006 (UTC)
 * If we do include it, it should be done the same way as the beginning of quest dialog, i.e. exactly what is stated. An issue arises with what to do with quests that have multiple parts, where you will get a block of text in the middle of the quest (which may actually explain more than the end of quest text).  --Rainith 12:15, 1 February 2006 (UTC)
 * I guess just have like 'Quest Beginning Dialogue', 'Intermediary Dialogue #', 'Quest Ending Dialogue'. --Ravious 08:43, 2 February 2006 (UTC)
 * I agree with adding all the dialogues. -PanSola 01:08, 25 February 2006 (CST)

List formatting
I think the list of rewards should be in a bulleted list, since usually there are skills or items as rewards as well. 21:09, 18 Jun 2005 (EST)


 * I agree re: bulleted lists for rewards. I'm ok with numbered lists for requirements but I'd prefer bulleted there too because numbered lists imply order and often quests like Cities of Ascalon have no order to their requirements presented in the Quest Summary. I do like Dialogue rather than Mission Text, though. MartinLightbringer(CS) 00:10, 19 Jun 2005 (EST)

Requirements
Also I'm a little confused about the interpretation of Requirements for Althea's Ashes (which I've chaged back to what I'd put originally). The Duke's Daughter must be completed before you can receive Althea's Ashes. This seems like a Requirement to me. Although perhaps Requirements should be split into two parts -- one for dependencies like this and another for requirements like the quest only being available to a certain class.


 * Nah, I'd say that's fine Martin, it IS a requirement. 02:08, 19 Jun 2005 (EST)


 * I agree, too. The requirement either wasn't there when I edited the article or I accidentally removed it. Adraeus 17:26, 20 Jun 2005 (EST)

Skills given
Should there be a standard way of noting what skills, if any, are given when you accept the quest? (This may only apply to Pre-Searing quests, so perhaps it's not important.)

Followup
How about adding a section Followup to the template, to list any quests that become availible after finishing the current one (like "requirements in reverse")? This information was already added to several quests (mostly by me :o), see Barradin's Advance for instance. I think this would be a nice thing to have. --84.175.70.38 00:54, 31 Jul 2005 (EST)
 * Seems like a good idea. --Fyren 01:39, 31 Jul 2005 (EST)
 * I'm for it as well. Seems natural to list it. kaarechr 01:40, 31 Jul 2005 (EST)

Categories
I think we should split quests into categories, at the moment there's just the great ugly category:quests, I propse we make category:Ascalon quests, category:Fissure of Woe quests etc 19:00, 2 March 2006 (CST) 19:05, 22 March 2006 (CST)
 * Considering they also automatically show up under diff headings in the quest log, I agree. -SolaPan 19:07, 22 March 2006 (CST)