GuildWiki:Builds

Builds are a major part of the GuildWiki. However, builds differ from other articles, because they can rarely or never be objectively evaluated; therefore, the GuildWiki uses a vetting procedure which ensures that, even though builds can only be subjectively evaluated, good builds can be separated from those which do not work as well.

New builds
Creators of a build should follow the guidelines in Style and formatting/Builds to ensure their builds conform our standards of presentation. All new builds should be placed in the category Build stubs. If a build is finished anyone apart from the original author can nominate the build for testing by moving it into the category Untested builds. It is the nominators responsibility to check that the build confirms with our standards for build presentation and is not non-sensical.

Untested builds
''This is the stage where most of the vetting takes place. Testers are encouraged to discuss and vote on builds (see next section for details).''

When a build is placed in the category untested builds a blank voting form should be added to the build's talk page (this can be done by placing  on the talk page). As soon as a build has 3 more positive votes than negative votes, it can be moved to the category tested builds. If it has 3 more negative votes than positive ones, it is moved to the category unfavored builds.


 * Note that the vote of the original build submitter is not counted here (he/she is thought to be always in favor of the build). It makes counting of votes easier if the original author does not cast a vote.
 * Unlike other votes on the wiki, votes on builds do not have an ending date. Therefore testing of builds is continuous and builds can be moved from one to the other category if sufficient votes are cast.

Testing builds
When testing builds, testers should try their best to look at builds unprejudiced. The usage description of the author and also the types of gameplay (GvG/Farming/etc) for which the build is intended for should be checked carefully. Testers who are not 100% sure of their vote should take the build to Guild Wars and run it before casting the vote. It is helpful to try to improve the build by suggesting changes on the talk page.


 * Do not take a negative vote for one of your builds as a personal attack on yourself. The vetting process tries to ensure the quality of builds on this wiki.
 * Do not use personal attacks on the author while voting. It is always the build which is evaluated, not the author.
 * Testers are highly encouraged to leave a note stating the reason for their vote, especially in case of a negative vote.

Re-evaluating builds
Builds that have been placed in the category tested builds should not be changed without discussion on the talk page first (although typos, grammar mistakes and formatting can be fixed). Builds in untested builds and unfavored builds can be changed. If a build has been changed substantially, a new vote should be called, by archiving the old vote and putting up a new vote form. If an unfavored build has been substantially changed, it can be placed into untested again.

Deleting builds
Builds that sit in the category Build stubs for more than 2 weeks without being nominated and without further modification of the build are deemed abandoned and are flagged for deletion. Deletion will take place if a further 2 weeks dont bring a chance of the situation.


 * To prevent a build from being deleted, either nominate it, or, if you plan to update the build, disagree with the deletion on the talk page