GuildWiki has been locked down: anonymous editing and account creation are disabled. Current registered users are unaffected. Leave any comments on the Community Portal.

Join The Fan Lab, a private Fandom research community for users in the US and UK where you will be asked to share your opinions on all things gaming and entertainment! Click here to see if you qualify

User:Xeeron/Current build procedure

From GuildWiki
Jump to: navigation, search

This is an article showing the current procedure in use in this wiki.

Not policy[edit | edit source]

This wiki currently has no policy on builds, since consensus has not yet been reached. This page documents the procedures currently used on the wiki to help those who are new to the builds process. It documents how things are done, not how things should be done.

New builds[edit | edit source]

Everyone is free to create a new builds article. When using the template in [GuildWiki:Style and formatting/Builds], most builds will start out in the category [:Category:Untested builds|untested builds]. Those that lack proper formating/wording will be moved into category [:Category:Build stubs|build stubs].

Discussion and voting[edit | edit source]

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 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.

Everyone can vote for builds. Voting after testing the build in game and leaving a detailed comment with the vote is prefered, but not needed to make the vote count. According to a vote on the builds talk page, builds are moved to [:Category:Tested builds|tested builds] if 3 more people voted favored instead of unfavored. If 3 more vote unfavored, the build is moved to [:Category:Unfavored builds|unfavored builds]. If you see a build which is not in the correct category, please change the build's category.

Re-voting[edit | edit source]

If the build has been sufficiently altered to render old votes invalid, sometimes a new vote is called. To do so, archive the old vote and put up a fresh Rate-a-Build section.

Deletion of builds[edit | edit source]

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[edit | edit source]

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[edit | edit source]

All build categories with the exception of Build stubs/Abandoned/Untested/Unfavored are reserved for builds which are also in the [:Category:Tested builds|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[edit | edit source]

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

Featured builds[edit | edit source]

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 build if the old build has been up for at least 3 days.