GuildWiki:Style and formatting/Builds
From GuildWiki
 |
Do not add new builds to this
page.
New builds must be posted on a new page.
|
| Style guides |
|---|
 |
This page is a style and formatting guideline on GuildWiki. It has general acceptance among editors and is considered a standard to which articles should adhere. However, it is not set in stone and should be treated with common sense and the occasional exception. |
This article details the style and formatting guidelines for creating and maintaining new articles about character builds. This is a style guide and not an actual build article. Please do not modify the content here with build-specific information. See the next section for an explanation on how to create new pages.
Contents |
[edit] Creating a new build article
Every unique build or team build must be created as a new article. Before creating, try to look through existing builds and see if a variant of your build is already available. If so, consider adding your build as a variant.
To create a new build article, you can proceed in one of two ways.
- Edit the sandbox to create a link to your new build
article. For example, if your new build is called "W/any Gallant
Soldier", then add the following text to the sandbox:
When you save the page, you will find a red link. Click on it to start editing your build article.[[Build:W/any Gallant Soldier]]
- Note:
- For optional professions, please use /any, not /Any.
- It would be appreciated if after finishing, you could remove the link from the sandbox.
- Alternatively, if you are more familiar with wikis, you can go
directly to the URL of your new build. The "W/any Gallant Soldier"
page will be at:
http://gw.gamewikis.org/wiki/Build:W/any_Gallant_Soldier
For general wiki help, please see the article Help:Editing.
Important Note: Before a build is made, check Category:Unfavored builds to see if your build already exists. Making a build over a previous one saves both you and voters time.
[edit] Naming
A new character build article should always be prefixed with the abbreviated names of the primary and secondary professions. Team build articles should be prefixed with "Team -" instead. Always try to come up with a good descriptive name for your article. The following are examples of good build names:
[edit] Template
The following is a barebones template of a new build article, ready for cut-and-pasting.
A build should only be in untested or build stubs, not both.
Until your build is ready for testing, keep it in the stubs section
with {{build-stub}} and when you decide to add on the
{{untested-build}} tag, make sure to remove the build
stub tag.
{{untested-build|Build type 1|Build type 2|Build type 3| etc}}
use "build-stub" for builds being assembled, and "untested-build" for builds that are ready for community review (DELETE THIS LINE)
{{TOCright}}
Describe the build.
== Attributes and Skills ==
{{attributes | Primary | Secondary
| Attribute 1 | 12 + 1 + 3
| Attribute 2 | 10 + 1
| Attribute 3 | 8
}}
{{skill bar|1st skill|2nd skill|3rd skill|4th skill|5th skill|6th skill|7th skill|Generic resurrect}}
* Suggest a few optional skill(s) if you included an Optional slot in the skill bar.
* "Generic resurrect" works like an Optional slot. Replace it if necessary.
== Equipment ==
* Armor
* Weapons
== Usage ==
Describe how to use the build.
== Counters ==
Describe important counters.
== Variants ==
List the major variants.
== Notes ==
Add any additional notes pertaining to your build. Omit this section if it is not needed.
== See also ==
Link to any articles that are related to your build. Omit this section if it is not needed.
<!--[[Category:Category 1|Build name]][[Category:Category 2|build name]]-->
[edit] Sections
Begin the build article with {{untested-build}}.
This will insert a message at the top of your build showing others
that it needs to be tested. After the build undergoes vetting, it
will be replaced with either {{tested-build}} or
{{unfavored-build}}. If you do not add the
{{untested-build}} tag, it will be added for you by
someone else.
Immediately give a short summary of the build. Do not title this summary section as "Overview" or "Introduction", as these titles are understood. It is generally preferred to begin the summary by stating outright what the build does. For example, the R/N Touch Ranger build begins as follows
- A Touch Ranger makes use of a ranger's durability in getting close to his opponents, and uses the "touch" skills from the necromancer's arsenal to steal his opponents' health and deal a large amount of armor ignoring damage. Because the touch skills are not spells, the ranger primary attribute of Expertise helps to reduce their cost greatly.
Notice that the build is referred to in bold (sans the profession prefix). This section should generally contain:
- A mention of the key skill(s) in the build
- A listing of which game styles (PvE or PvP) it applies most to. For PvP, a further clarification of Random Arenas, Team Arenas, Heroes' Ascent, Guild versus Guild or Alliance Battle should be given.
Do not fill the introduction with:
- A mention of every skill used in the build
- A list of attributes and ranks
- Detailed usage or counter discussion.
This introduction section should be no longer than a paragraph.
[edit] Attributes and Skills
Use the {{attributes}} template to list the attributes (documentation).
Use the {{skill bar}} template to list the skills.
See the example above. The attribute listing should use the rank + headgear + rune syntax. Do not add spurious = signs in the attributes or you will confuse the template.
Make sure your attribute point allocation is correct (i.e. you haven't got left over points or used more than 200 points). The Attribute point spending article can be used to check this.
[edit] Equipment
List only the following:
- Essential weapons
- Essential armor
Do not list runes (which can be derived from the attribute listing) and non-essential gear. Try to be as brief as possible.
Note: The only time runes should be listed is when they are essential to the farming builds (e.g. when you have to switch armor or mask at a keypoint in the run).
[edit] Usage
Present usage information as much as possible in brief and in bulleted form.
- Wikify the first mention of a skill, but do not wikify all mentions.
- Try to be as brief in your descriptions as possible. You do not need to document game mechanics such as "hit C to target nearest" unless it is essential and non-intuitive. Assume that readers know how to play the game.
[edit] Counters
List the counters to the build as stated.
- Only list the principal and effective counters for the key idea of the build.
- Do not mention general counters such as "run away" or "kite" unless it is extremely relevant to the build.
[edit] Variants
List the principal variants of the build.
- Try, as much as possible, to not suggest replacements for the key skills in the build.
- If a variant you suggest requires an entirely different style of playing, it should be in a different build article.
- There should only be one attribute and skill bar in a build page. Here, if what you're trying to do cannot be described on one or two lines, it is usually not a viable variant.
[edit] Notes
In this optional section, list information about the build that is not relevant to how to play it. Items of note might be a brief history of the build, or notes on whether the build is or was a premade build, etc.
Try, as much as possible, to avoid adding this section.
[edit] See Also/External Links
In this optional section add references to related pages on the GuildWiki or well known external sources.
Standard limits on linking to external sites apply. Do not link to your guild's website. The link will simply be removed.
[edit] Untested build tag
Once the build is for community testing, apply the {{untested-build|Build type 1|Build type 2|Build type 3| etc}} tag. The codes for the build types are as follows:
-
Build type code Category Game-play type AB Alliance Battle builds PvP CM Competitive Mission builds PvP GvG Guild vs Guild builds PvP HA Hero's Ascent builds PvP HB Hero Battle builds PvP RA Random Arena builds PvP TA Team Arena builds PvP PvP team PvP team builds PvP farming Farming builds PvE running Running builds PvE hero Hero builds PvE PvE team PvE team builds PvE general General PvE builds PvE
[edit] Build Categories
Place your build in one of the following categories, based on what campaigns the skills it uses come from:
- Category:Core builds
- Category:Prophecies builds
- Category:Factions builds
- Category:Nightfall builds
- Category:Multi-campaign builds
Do not add categories to the top of the article as it will mess up the spacing. Categories go at the very bottom of articles. Categories will stay commented out (between <!-- and -->) until and unless the build favored, but they help determine which campaign(s) the build was created for.
