GuildWiki:Style and formatting/Skills

This article provides information on starting, expanding on and completing articles relating to individual Skills in Guild Wars. This information should be taken into account along with the more general information in Style & Formatting

Starting A New Skill Article
Before starting a new Skill article make sure it isn't already listed in the Skills category.

Skill Stub
All new articles should be classed as stubs, and to avoid confusion it's best to mark a new Skill article a Skill Stub. You can do this by using the wiki code  . This adds the Skill-stub template to the new article. In doing so it also automatically lists the article under the Skill stubs category, so that anyone interested in expanding on this skill article can find it on the skill stubs category page.

Categories
Each skill should be listed under the appropriate categories. If the skill is connected to a particular attribute then it should be included in that attribute's category. Since Orison of Healing is tied to Healing Prayers it should be included in the Healing Prayers category. This means that anyone looking through the list of Healing Prayers can easily find Orison of Healing. To do this add the line  . See the example later in the article if you're unsure.

If the skill is connected to a particular job then it should be included in that profession's category. Since Orison of Healing is only available to Monks then it should be included in the Monk skills category. This means anyone looking through the list of Monk skills can easily find Orison of Healing. To do this add the line  . See the example later in the article if you're unsure.

If a skill is not tied to an attribute and it is not tied to a profession then it can be included in the Common Skills and No Attribute categories with the wiki code  .

Skill Details
The next thing to do is add the Skill Box template, which can be seen on the rigth hand side of this page. This is the Skill Box used for Orison of Healing. It provides details about a particular skill. The template consists of several parts.


 * Skill_begin - starts the table
 * Skill_image - allows for the inclusion of an image
 * Skill_begin_info - begins the different optional entries
 * Skill_profession_entry - The profession related to this skill, if it is profession specific
 * Skill_attribute_entry - The attribute related to this skill, if it is attribute specific
 * Skill_type_entry - The type of the skill (e.g. Spell, Enchantment, Nature Ritual etc.)
 * Skill_energy_entry - The amount of energy this skill consumes
 * Skill_activation_entry - The length of time this skill takes to activate
 * Skill_recharge_entry - The length of time this skill takes to recharge
 * Skill_upkeep_entry - The cost of maintaining this skill (e.g. -1 Energy Regeneration etc.)
 * Skill_adrenaline_entry - Whether this skill uses adrenaline
 * Skill_sacrifice_entry - The amount of health this skill consumes
 * Skill_end_info - ends the optional entries
 * Skill_end - ends the table

This might seem a little intimidating, but it's fairly easy to use. Each template can accept some parameters to customise the Skill box for each individual skill, while retaining the same look and feel. Here is the wiki code used to produce the skill box for Orison of Healing.

It's tidiest not to include entries such as Skill_energy_entry if the energy cost is zero.

Also, for fractions, in order to get 3/4 or the like, use 3/4

Please bear in mind that all skill boxes should be colored lightgreen to allow for other colors for other types of boxes, such as bestiary, items, locations etc.

More Detailed Skill Information
After including all the other information you can actually start writing something about the skill! Important information includes:


 * Description: A description of the skill. Preferably, the official description you get from the Skills window in the game.
 * Usage Notes: Advice on how to use the skill.
 * Acquisition: Where to acquire, the cost of acquiring and a link to further information on acquisition. For example:
 * Serenity Temple: Quest, Replacement Healers
 * Ascalon City (Post-Searing): Trainer, Sir Bertran
 * Elona Reach: Capture, Vassa Ssiss
 * Related Skills: Other skills that do similar things. For example Resurrect might include a link to Restore Life since they both resurrect a fallen party member.

Expanding On Skill Articles
There are currently plenty of skills that could do with more information. Every skill needs a complete set of details in the skill box, a description of what the skill does, where to get the skill and optionally how and when to use the skill and related skills.

The finishing touch to a good skill article is a relevant icon for the skill. Many already exist on the wiki but are not yet being used. Have a look at Special:Unusedimages to see if an icon already exists before uploading another one.

Hyperlinking
It can be useful to hyperlink some of the Guild Wars terms in the Description text.


 * Conditions: If a skill causes a particular condition hyperlink it to the Conditions page, but preserve the original text. For example skill 'Immolate' uses the following wiki code for its description text:
 * Target foe is struck for 5...41 fire damage and is set on fire for 1...3 seconds..
 * Which produces this output:
 * Target foe is struck for 5...41 fire damage and is set on fire for 1...3 seconds.

Completing a Skill Article
This is a general guideline for what to do with complete articles (taken from wikipedia Peer Review), it is probably too much to ask for articles as short as Skill articles, but I've included it here anyway for now.

If you think an article is complete, do the following.


 * Go to the Talk page for that article by clicking the discussion tab at the top of the article, and add the text  . This will add the talk page for the article to the Requests for peer review category.
 * Follow the link that is created and add the text  ===name of nominated article===  at the top of the new page, and then explain why you think the article is complete, signing and dating it using the wiki code  ~ . If it is agreed that the article is good enough, then the   code can be removed from the talk page and the    code can be removed from the article itself.