Revision as of 11:59, 25 November 2015

This style manual dictates rules and guidelines for creating and editing build and team pages. Strict adherence will almost never get you banned and some flexibility is afforded to new users. However, blatant disregard for the rationality and intentions of this guide is sufficient ground for a ban.

Voice

Limit bold words. In most cases there is a precedent set for what can be bolded. Language that needs to be emphasized should never be bold but can be italicized (This includes single words and short phrases).

Language

Define acronyms at least once before using them. (Don't expect your reader to be well-versed in the terminologies).

Example: "Deadly Arts (DA) is a specialization for Thieves."

Omit needless words; Don't use 5 words when 3 will do.

Good Example: Using a Leap Finisher in a Fire Combo Field will activate a Fire Shield.

Bad Example: Whenever a player is using any kind of Leap Finisher in any kind of Fire Combo Field, it will always activate a Fire Shield.

Creating Build & Team Pages

If the build already exists, consider adding content to that article or advocating changes in the discussion tab. Otherwise, you are free to create any new build or team page by following the steps below.

Naming

Creating a new build first requires a name. All build pages should begin with the "Build:" prefix, followed by the profession name, a space, hyphen, and another space. The build title then goes last.

Avoid using "Ultimate", "Perfect", or "Best" in the title. If a build is indeed that good it will surely gain traction from the community regardless of it's title. Sometimes it's easiest to distinguish a build by the weapons it uses or the specific trait/playstyle that makes it unique.

For the sake of consistency, we'll use "Build:Guardian - AoE Staff Farmer" as an example of a new build.

Creating

To actually create the new page, do one of the following:

Address Bar

Type "www.metabattle.com/wiki/Build:Guardian - AoE Staff Farmer" into the address bar and hit enter (Don't worry about spaces or punctuation, the server will figure it out for you).

If the page doesn't exist, you can click "edit this page" in the message or the "Create" tab near your personal navigation bar.

If the page already exists, consider adding your content to the existing page. If you believe your build to be very different consider asking the discussion page or creating a new build under a different name.

Click the red link for your build (If there is no red link, the build already exists! See step 3 above).

You should now be at a text-editor.Here you can type anything you'd like to begin your build. You can always preview your work with the "Show preview" button near the bottom. The page will be created once you "Save" the page.

Template

This is a barebones template of a new build article. Just copy and paste the text on the new page to get started. (Remember to delete the examples!) The following template is taken from the Hambow warrior build:

Template Explanation

Rating/Category settings

Once you submit a build, it should first be marked under the "Draft" category by adding the following code:

{{Build|Profession|Game Type|Draft}}

For example:

{{Build|Guardian|Conquest|Draft}}

In this stage the community will criticise and suggest improvements to the build. The build will be located under "Draft" due to being set to "Draft". Note that it will take some time (ranging from a few hours to a few days) before it appears on the main page, this is an anti-spam measure.

Once you have reviewed the comments and made necessary adjustments to the build and think that it's ready for the community to rate it, you should replace:

{{Build|Profession|Game Type|Draft}}

with:

{{Build|Profession|Game Type|Test}}

This is where people will rate the build. Once a minimum of 5 votes have been gathered you should replace:

{{Build|Profession|Game Type|Test}}

with the following:

Trash (0 – <3.75):

{{Trashed-Build|1=Game Type}}
[[Category:Trash]]

Good (3.75 – <4.75):

{{Build|Profession|Game Type|Good}}

Great (4.75 – 5.0):

{{Build|Profession|Game Type|Great}}

If it happens that this build is also used in the current meta, the tag should be replaced with:

{{Build|Profession|Game Type|Great|Meta}}

Information settings

This is where you write a very short information about the build and what it does.

Example:

Hambow is a strong, easy to play build that brings massive damage to team fight as well as solo fights. The build got a lot of survivability and massive health regeneration every second.

Build/Skills settings

This is simply where you enter skill names for the first and second weapon sets. Using the template above, you would just need to input correct skill names. Skill number one is represented by |Skill1=| and skill number two is represented by |Skill2=| etc.

|Label=| needs to be filled in with the weapon that is being used. If the build is using axe and shield, the label should be set to |Label=Axe/Shield|.

When activating virtue of justice, nearby foes are blinded for 3 seconds.

Specialization settings

How it works.

Specialization is the start of the code.

Arms The specialization name (profession name is not used)

| separates each section of the template.

Variants should be placed right below the specialization it refers to.

Overall variants (swapping one specialization for another) should be written at the top before all three specializations and their individual variants.

What this looks like

{{Specialization/Arms|top|bot|mid}}
{{Specialization/Defense|bot|mid|mid}}
'''Variants'''
* Move adept to mid for more "oomph!"
* Move grandmaster to top for less "wazzah!"
{{Specialization/Discipline|bot|top|top}}
'''Variants'''
* Move master to mid for "krakow!"
* Move master to bot for less "krakow!"

Arms

Precise Strikes

Your critical hits have a 33% chance to inflict 1 stack of bleeding for 4 seconds

Burst skills deal 7% more damage. Regain 3/7/10 adrenaline when using a burst skill based on the amount of adrenaline spent

Variants

Move master to mid for "krakow!"

Move master to bot for less "krakow!"

Weapon settings

This section contains two weapon sets, first and second weapon set that each contains two different weapons.

First weapon in both sets should be filled. The second weapons in both sets should only be filled if the first weapon isn't two handed, otherwise they should be left blank.

Use the following format when filling in the weapon sets:

Weapon: What kind of weapon it is, example: "weapon=Axe"

Stats: What kind of stats does the weapon have, example: "stats=Berserker (Power/Precision/Ferocity)" - Can be left blank if it's a PvP guide!

Sigil1= What kind of sigil does this weapon use, example: "sigil1=Superior Sigil of Battle"

Sigil2= What kind of second sigil does this weapon use, this one is left blank since the weapon isn't two handed. If it was two handed you would fill in the settings just like you did with "Sigil1".

Infusion: What kind of infusion does this weapon use, example: "infusion=Malign Infusion" - Can be left blank if it's a PvP guide!

The second weapon and the second weapon set should be filled in using the same format, note that you can leave some options blank if they are not being used/required.

Equipment settings

The equipments should be filled in using the same format as weapons:

HeadStats: Stats of the head, example: "HeadStats=Berserker (Power/Precision/Ferocity)" - Can be left blank if it's a PvP guide!

HeadRune: Rune that the head is using, example: "HeadStats=Superior Rune of Strength" - Can be left blank if it's a PvP guide!

HeadInfusion: Infusion that the head is using, example: "HeadStats=Malign Infusion" - Can be left blank if it's a PvP guide!

Rest of the settings should be filled in the same way. NOTE: You can leave some fields blank if they are not being used!

Accessories settings

This section uses the same format as "Equipment", fields can be left blank even here. For example if it's a PvP guide, you are only required to fill in the "Amulet" settings. Ring1/2, Earring1/2 and Back item can be left blank!

Usage/Guide settings

Guide on how to use the build, doesn't have to be long. Focus on special qualities of the build and not on basic mechanics of the class.

With New Builds you are submitting, don't spend much time on Usage. The Build itself is more important than the usage, so focus will be placed on the Skills/Traits/Equipment when Testing.

Counters settings

Explain what is countering the build and how you can prevent that.

Video Guides settings

Links to Youtube videos where this guide is used, use this format when adding new links:

Other Templates

Pending-Archive

If you believe that the build in question is outdated you can mark it for archive by adding this code right under "########## Rating/Category settings ##########":

{{Pending-Archive|REASON1|REASON2|...|REASON8}}

The template accepts up to 8 reasons. Example if we fill in 3 reasons:

{{Pending-Archive|REASON1|REASON2|REASON3}}

The above example would display this on the build article:

This build is suggested to be archived, because:

REASON1

REASON2

REASON3

If you disagree with this build's archiving, please explain why on its talk page.
If this page obviously should not be archived, or if you intend to fix it, please remove this notice, but do not remove this notice from articles that you have created yourself.

Archived Build

If the build in question should be archived, replace the "{{Trial/Testing/Good/Great/Meta-Build}}" tag located under "########## Rating/Category settings ##########" with the following code:

The template requires a date when the build was archived, name of the category where the build was located in, up to 8 different reasons why the build got archived and up to 13 different game modes.

{{Archived-Build|date=12 September 2008|category=Great|reason1=reason1|reason2=reason2|reason3=reason3|Roaming|Zerg}}

The above example would display this on the build article:

This build has been archived as of 12 September 2008, for the following reason:

reason1

reason2

reason3

This build was in the category Great before being archived.

This build had been designed for the following use:

Roaming

Zerg

Mark for Deletion

If you belive that the build in questions should be deleted you can mark it for that by adding this code right under "########## Rating/Category settings ##########":

{{Delete|REASON1|REASON2|...|REASON8}}

The template accepts up to 8 reasons. Example if we fill in 3 reasons:

{{Delete|REASON1|REASON2|REASON3}}

The above example would display this on the build article:

This page is a candidate for deletion, because:

REASON1

REASON2

REASON3

If you disagree with this page's deletion, please explain why on its talk page. If this page obviously should not be deleted, or you intend to fix it, please remove this notice, but do not remove this notice from articles that you have created yourself.