Difference between revisions of "About"

From Speedclear Wiki
Jump to navigation Jump to search
Line 11: Line 11:
  
 
== Why not using PvXwiki? ==
 
== Why not using PvXwiki? ==
PvXwiki is a great archive of builds, but its structure is rigid in having one team-build in one page, which creates two main issues:
+
PvXwiki is a great archive of builds, but its structure is rigid and its voting system makes change difficult. Specifically we saw the following issues:
 
* Lack of cross-referencing: many tactics share the same specific parts, jobs and equipment which we can move on their own page to reduce duplication and increase the overall quality.
 
* Lack of cross-referencing: many tactics share the same specific parts, jobs and equipment which we can move on their own page to reduce duplication and increase the overall quality.
 
* Cannot split pages: Having a DoA guide on PvX would mean having a single monolithic page full of content which becomes extremely hard to browse. In the Speedclear wiki, instead, we split pages depending on their scope.
 
* Cannot split pages: Having a DoA guide on PvX would mean having a single monolithic page full of content which becomes extremely hard to browse. In the Speedclear wiki, instead, we split pages depending on their scope.

Revision as of 00:57, 17 December 2016

Why Speedclear Wiki?

The idea for a wiki was born thanks to the DoA guide by Loa. Many high-end speedclear players realized that the guide was being indeed read by new players and was surprisingly effective at teaching the basics. An effort was made to improve and expand it, but the single-document format soon became a problem as more and more cross-references were needed, and reading was becoming increasingly difficult.

FBGM offered to host the wiki itself, and so we created wiki.fbgmguild.com with Domain of Anguish content.

The obvious next step was to consider all speedclears rather than only DoA, and then we decided to include all speedclear-relevant resources: general equipmenents, game mechanics, speedclear guilds, community creations and websites.

Why not using Guild Wars Wiki?

The official wiki is a great resource, but its scope is much larger than this wiki, which prevents us from creating very specific pages. For example, we have pages such as City which point to the Domain of Anguish area rather than "outpost", and pages such as Assassin Equipment which are only relevant for speedclears.

Why not using PvXwiki?

PvXwiki is a great archive of builds, but its structure is rigid and its voting system makes change difficult. Specifically we saw the following issues:

  • Lack of cross-referencing: many tactics share the same specific parts, jobs and equipment which we can move on their own page to reduce duplication and increase the overall quality.
  • Cannot split pages: Having a DoA guide on PvX would mean having a single monolithic page full of content which becomes extremely hard to browse. In the Speedclear wiki, instead, we split pages depending on their scope.
  • Aging: Unfortunately PvX has become disconnected to the real Speedclear meta years ago, and its rigid rating system makes it hard for current meta builds to replace outdated ones.

Contributing to Speedclear Wiki

As a general main guideline, the content of the speedclear wiki should reflect the current SC meta. This includes builds, equipment, tactics, but even the names of roles and areas.

If you don't have a lot of direct experience with something please refrain from editing or creating related content. Do not theorycraft builds and do not attempt to influence the meta here. The wiki is simply a mirror of the SC meta. On the other hand, feel free to use the talk pages for asking relevant questions.

Please refrain from transforming this wiki into a redundant list of things. For example, do not list everything in FBGM/Golt tactics, but rather list the differences, don't list each spike the TK does, but feel free to list important splits (e.g. Ranger vs Derv) and explain why the role exist in general and how to perform the role-specific tasks.

Credits

A lot of content was copied from existing guides, thanks to the original authors.