User:Namnatulco/bvp

This page documents the procedure currently used on the wiki to help those who are new to the builds process.

New builds
Everyone is free to create a new builds article. You are encouraged to go through the build catagories, to find any builds related to your own. Using the template in is recommended. New builds will start out in the category. Those that lack proper formating/wording will be moved into category build stubs

Discussion and voting
After the build arrives in untested builds, people will start noticing and discussing it. At one point someone will put up a Rate-a-Build section (see below) on the builds talk page. This is sometimes done right after the build is created, sometimes people wait till the first round of discussion is over. Please keep all discussions civil and avoid personal attacks.

Everyone, other than the original author of the specified build or contributors that heavily modified the untested build before voting, can vote for builds. Testing the build is preferred, but an argumentation supported with facts (such as "not enough energy management") is also allowed. When voting while you have used a variant of the build, please note that variant. The popularity of a build alone is not enough to vote it as favored, even though popularity is usually linked to effectivity. Anonymous voting is STRONGLY discouraged.

If 3 or more people vote favored/unfavored, the build is moved to the appropriate catagory.

Two important notes on the votes section:
 * Do NOT strike out other people's votes or delete them for any reason. If you think a vote is objectionable in any way, report it to an admin (see GW:ADMIN for a list of admins).
 * Do NOT discuss other people's votes in the voting section. It makes the votes cluttered and unreadable. Instead, take your issues to the discussion section below or to the respective user's talk page.

Rate-a-Build
''Please test and vote on. See Build_vetting_procedure for more info on voting.''

Favored (works and is superior to all other builds around with the same purpose): Untested (Needs more work, and/or is somewhat inferior than similar builds): Unfavored (greatly inferior to other builds, unfocused, or no real goal):
 * 1) (your vote here)
 * 1) (your vote here)
 * 1) (your vote here)

Re-counting
Once a build is favored or unfavored, it can not be moved back into untested (exception: re-voting, see below). However it can still be moved to the other category, if enough people vote for the other category, such that this category now has 3 more people compared to the current one.

Re-voting
If the build has been sufficiently altered to render old votes invalid, sometimes a new vote is called. To do so, re-name the old vote, put up a fresh Rate-a-Build section and move the build into untested.

Deletion of builds
Builds get put up for deletion if someone feels they are too close to an already existing build. Furthermore, builds get sometimes flagged for deletion if someone feels they are extremely bad. The usual wiki procedure of discussion takes place, but note that especially in the first case, deletion might be swift.

Abandoned builds
If a build in untested or unfavored has not seen work on it in several weeks, it might be put into Abandoned. Builds there will be deleted after a (longer) period of time if no new work on them is done.

Build categories
All build categories with the exception of Build stubs/Abandoned/Untested/Unfavored are reserved for builds which are also in the tested builds category. Builds in one of the beforementioned four categories should not be in any other builds category at the same time.

Archived builds
Builds that are no longer viable, but are kept for historical reasons are put into category archived builds.

Featured builds
The build portal currently has 2 featured build slots. The first, Current featured build, is reserved for tested builds. The second Featured Untested Build for immediate evaluation is for untested builds. Since there is currently no process comparable to wikipedia's featured articles, every registered user can change the featured builds. To prevent too frequent changes, users are asked only to change the featured tested build every 7 days, and the untested build upon evaluation of the previous one.