Guild Wars Wiki:Formatting/Missions

This article provides information on starting, expanding on and completing articles about Missions in Guild Wars.

Syntax and example
{| 

An overview of the mission will go in here. It might describe some context for the mission, mention the objectives and provide a summary of the Walkthrough section.

Objectives

 * Objective 1.
 * Objective 2.
 * ADDED: Objective 1.
 * *BONUS* Objective 1.

Allies
Humans
 * 20 (20) Kormir

Foes
Demons (Margonites)
 * 24 (24) Margonite Executioner
 * 24 (24) Margonite Bowmaster
 * 24 (24) Margonite Cleric
 * and so on...

Bosses
Mummies (Undead)
 * 28 (28) Avah the Crafty &amp;rarr; Elite skill (Unique item)
 * 28 (28) Nehmak the Unpleasant &amp;rarr; Signet of Suffering

Dialogue
"Text"

Trivia

 * }

Article header
The following should always be placed at the beginning of the article.

Use the Location disambiguation template to redirect users if they weren't looking for this mission article. If the mission article is a stub, use the mission-stub template to add the page to Category:Mission stubs.

In Factions, certain mission names are shared by two outposts (one for each faction). For that case, use Faction mission outpost link.

Mission infobox template
Use the Mission infobox to create the info box. See the template page for detailed instructions. Example usage:


 * name : The name of the mission. This parameter also specifies the file name of a map showing the mission route and points of interest for the mission. The image is automatically resized to 250 pixels wide.


 * map : An image for the map may be specified but should only be used if a different width needs to be specified.


 * campaign : The campaign in which this mission belongs. Mandatory.


 * region : The region where this mission is located. Mandatory.


 * type : The type of the mission; "Cooperative", "Competitive", "Elite", or "Challenge". Mandatory.


 * duration : Categorize the mission length as "Short", "Medium" or "Long". "Very long" can be used for elite missions. Can be omitted.


 * preceded by : The name of the quest or mission which immediately preceded this mission. Can be omitted if not required.


 * followed by : The name of the quest or mission that the player must undertake to continue the storyline. Can be omitted if not required.

Preferably, stick to the order shown above for consistency.

Overview
Provide an overview of the mission to help the reader get to grips with the basics of what is expected of them in the mission. This might include some context for the mission in the story, a review of the objectives of the mission, a statement about the perceived length or toughness of the mission, or step through the main points of the included walkthrough for the mission. If the mission article as a whole is short this section can be omitted.

Mission information
Details about the mission.

Requirements
Note anything which you need to have to enter the mission, such as a particular hero in your party. This does not include prerequisite quests or missions, as those are recorded in the infobox.

Objectives
Transcribe the objectives as given in the Log screen during the mission.

Reward
If rewards are tiered (i.e, Standard / Expert / Master), show in a table how the bonus objectives relate to the rewards tier. Only include any XP, gold or Skill Point rewards if they are different from those usually rewarded for missions in the campaign. If the rewards are not tiered do not include this section.

Walkthrough
Provide a walkthrough for the primary objective for the mission. Provide a basic strategy for completing the mission and note any problems, with tricks for avoiding them. Listing every single group and patrol encountered and how to pull them is too detailed; however, indicating the number of groups you might encounter on the way and noting any complicated patrol routes is not. Refer to locations on the map for the mission to simplify the description. Try to integrate notes or tips into this section rather than creating a separate "Notes" or "Tips" section.

Bonus
Provide a walkthrough of how the mission's bonus objective(s) can be completed. Again refer to the map to simplify the description. This section is not necessary if the bonus is based on mission completion time, as long as the steps given in the Walkthrough are sufficient to achieve the time required for the Master's reward.

Skill recommendations
Provide any skill tips which players can use to help make a build to easily, or at least successfully, complete the mission. Suggest by skill function rather than actual skills or professions, as not everyone has all the elites or all of the campaigns.

Hard mode
If the walkthrough for hard mode differs sufficiently from normal mode, describe the walk through (including bonus and skill recommendations) for hard mode here.

NPCs
List all NPCs encountered in the mission. Group them by species, then order them by profession (according to the in-game ordering, see: Guild Wars Wiki:Formatting/Professions). Additional ordering should be done by level and alphabet.

Allies
List any NPCs included in the mission whom you must protect, who help you, or who simply follow you around. If there are no allies then this section should be omitted.

Foes
List all hostile NPCs which you might encounter during the mission.

Bosses
List the bosses in this mission including any elite skills which might be captured from them and any unique items they drop. If possible, these should be marked on the mission map also.

Dialogue
Transcribe any cutscene dialogues in the mission. Use sub-headers and indenting where necessary.

Trivia
Capture any trivia or easter eggs in this section. If there is nothing in this section it should be omitted.

Article footer
The following should  always  be placed at the end of the article.

Navigation
Include the navigation aid templates for the mission's region and the mission's campaign.

Categories
The page is automatically put into categories for missions by campaign and missions by type using the template. If possible add further categories to the template first rather than adding them to each mission page.