- Sunday 6th of February (talk)
- Thursday 21st of October (talk)
- Tuesday 31st of August (talk)
- Tuesday 9th of March (talk)
- Sunday 24th of January (talk)
- Monday 14th of December (talk)
This list contains all recent PvXwiki news.
State of the wiki[]
In October 2010, a copy (or fork) of this wiki was established at www.gwpvx.com. Since then, most of the community has moved over there and PvX@wikia is now receiving little to no attention from active editors.
As a consequence, the information presented on this site is getting more and more outdated. The ongoing changes in the game and in the metagame require continuous maintenance regarding both our skill descriptions and the design, description and categorisation of the builds presented here. Moreover, experienced editors are missing who could help new contributors with the formatting of their submissions in order to make them accessible and useful for interested readers.
In this situation, information found on PvX@wikia should be taken with caution.
How you can help[]
If you have ideas on how to revive this site, please discuss them at the Community Portal.
UPDATE[]
Because of the large amount of requests for the english versions of builds, PvX staff has saved those builds in their english versions here.
"Diversity Month" Starting Early This Year![]
As you all know, November is "diversity month", where people are encouraged (required, in fact) to submit builds in different languages. We here at PvX@Wikia like to celebrate the differences in our culture and want to invite everyone to participate.
However, there have been recent concerns raised about diversity month here on PvX - namely, the fact that with the fork occurring before the end of October, many people will be leaving this site and won't have the chance to participate in this unique cultural exchange on Wikia. Thus, diversity month will be starting today, October 21, so that everyone will get a chance to contribute.
How Can I Help?[]
There are numerous ways you can help with diversity month. Some ideas are listed below, but you're not limited to these:
- Translate existing builds into another language using a translation program or your own knowledge of the language
- Submit new builds in languages other than English
- Welcome new users with non-English languages
- Invite your friends to participate in diversity month here on PvX
To support diversity month, we've created a number of helpful templates you can use when tagging builds, so that those of other cultures can get the full experience of PvX. At the moment, we only have Spanish templates.
Japanese Templates[]
Spanish Templates[]
- Template:Untested-Trial-Spanish
- Template:Untested-Testing-Spanish
- Template:Meta-Build-Spanish
- Template:Great-Build-Spanish
- Template:Good-Build-Spanish
- Template:Trash-Build-Spanish
Best of luck - leave a message on the talk page of this article if you have any questions! -- Gah QQ · I did wut?! 16:36, October 21, 2010 (UTC)
Changes to build archiving[]
We have recently implemented a new name space specifically for archiving builds. This is the appropriately named "Archive" name space (and the associated talk name space is "Archive talk").
As a result of this all currently archived builds will be moved to the Archive name space. Users shouldn't move pages. The reason for that is because a bot is scheduled to run (currently) tomorrow morning (Wednesday 01 September (2010)), to move the large amount of pages (and associated pages) to their new destination, while leaving Special:RecentChanges clear from the massive amount of page moves, and the wiki to function normally. We apologise for the short notice of this, but it shouldn't impede your editing capabilities.
The addition of this name space, also means a small change in policy (specifically the changing of how builds are archived). As such, from now on when a build is archived, the build, it's talk page(s) and any sub pages (and associated talk pages) should be moved to the Archive name space.
This page will be updated when the move has taken place.
~ PheNaxKian talk 22:17, August 31, 2010 (UTC)
- UPDATE: The move has taken place. As such from now on when a build is archived, please move the build to the archive namespace!. ~ PheNaxKian talk 20:13, September 1, 2010 (UTC)
March 2010 Administrator Evaluation[]
Currently the most active administrators are undergoing evaluation by the bureaucratic staff. If you've seen any particular contributions by a particular administrator that make you think they're not fit for being an administrator (such as abusing their rights as an administrator) please add a link to it on this page, under the appropriate administrators heading.
What is this evaluation?[]
Administrators are constantly being monitored by the bureaucratic staff in an informal manner, and users can ask for a formal review of a specific admin at any time. Recently it was requested that a formal review be taken of the (currently) most active admins, as there hadn't been one in a while. The review will result in one of two things for an administrator:
- The administrator has been seen to be doing his duty, and will keep his rights as an administrator and continue as normal.
- The administrator has been seen acting in an unacceptable manner for an administrator (abusing rights etc.), and the Bureaucrats will decide if it's necessary to remove the users right as an administrator.
Concerning Build Master Position Removal[]
The BM position is to be removed entirely on Sunday 31 January. Many on this site view the position as a failed experiment. The position was originally created for knowledgeable PvP'ers - people who would know what they were doing and be able to explain to other users how or why a build was either good or bad. These people would also command respect simply because of who they are and the guilds they play for, not simply because of their "position" on PvX. However, due to many circumstances, the position became one that often resulted in flame wars, trolling, and many headaches for the Administrators.
Understanding the Administrator's Position[]
The Sysop position should be a merely janitorial one. Sysops can delete pages, block users for policy violations, and remove obviously biased/sockpuppet votes, and take any other actions (within policy) in an effort to clean up the site. Sysops should be a neutral third party. They can have build knowledge, and it can help them remove some of the more obviously wrong votes; however, user arguments over build votes should be discussed on the build's talk page or on the user talk page of the voter rather than on the AN. The Noticeboard should only be used for issues that can not be solved through user discussion.
User Responsibilities[]
The void left by the BM position is expected to be filled by the normal users here at PvX. Users will be expected to discuss builds bluntly, and at times explain to other users of this site why builds are good or bad. It will be the responsibility of the users here to discuss builds, vote on builds, report vetting problems to the AN, etc. In turn, we hope this will provide users with more understanding of the game and will help their ability to distinguish between builds.
Suppress Redirect[]
All auto-confirmed users should now have the ability to suppress redirects when they move pages. Suppress redirect is a tool that allows you to move a page and not leave a redirect behind.
This is a useful tool that can help cut down on a lot of unnecessary redirects, but should be used in accordance with redirect policy and is not for deleting pages or wiping votes. Abuse of this tool can result in a lengthy ban.
Suppress redirect can be found on the special 'Move' page. Redirects are suppressed by unchecking the checkbox that says 'Leave a redirect behind'.