|
This page is an official policy or guideline.
Please use the talk page or start a forum thread before making any changes, to ensure community consensus.
|
The following are guidelines and instructions on how to go about submitting and adding team composition suggestions for a monster page. Some basic knowledge in wiki editing is recommended. See here for a quick rundown of wiki syntax.
Page setup[]
Before adding a team comp directly to a monster page, a detailed page should be set up outlining usage of the team, including various runes and stats, as well as strengths and weaknesses, and specific instructions if needed. Generally, the guidelines for setting up a team comp page are quite flexible, and users are allowed to add as much or as little information as needed to convey the effectiveness of the team. However, there are several sections which should be added as a bare minimum. For an example of how a proper build page should look, see our example page.
Page tags[]
All build pages should include a premade message tag, inserted at the top of the page. This can be done by simply copying/pasting "{{Unique monster build message}}" at the top of the page (without quotations). Additionally, newly created build pages should also have the "{{New monster build notice}}" tag displayed at the top as well.
If you know with certainty that the build is being used in the meta, you may also attach the "{{Meta build|}}" tag at the top just below the other tags. Include where the build is being commonly used after the piping (for example {{Meta build|Arena}}).
Overview[]
All build pages should start with an overview table outlining the monsters used in the team, as well as basic rune and stat requirements. A lead paragraph outlining the basic elements of the team comp should be included below the overview table. The table can be done with the Template:Team outline template. See the link for in-depth instructions. An example has been provided below, including instructions on filling out the template properly.
Template syntax
{{Team outline|
{{Team outline content|[Monster Name]|[Relevant rune build and link]}}
|area=
|useful for=
|requirements=
}}
The above is the basic code for creating a table with one monster in the team. Replace the labels displayed after "Team outline content" with the appropriate information. For fields with the "=" sign, simply add in the required information. See below for an example.
Filled out template
{{Team outline|
{{Team outline content|Lushen|[[Guide:General supporter|General supporter]]}}
|area=C1-G3 Arena
|useful for=End-game
|requirements=High
}}
If one wishes to add suggested stats, one can add the fields in and fill them out manually like so:
{{Team outline|
{{Team outline content|Lushen|[[Guide:General supporter|General supporter]]
|Attack=2000
|CRI Rate=70%
|Speed=200
}}
|area=C1-G3 Arena
|useful for=End-game
|requirements=High
}}
If one wishes wishes to add more monsters, one need only add in another "Team outline content" template with filled in information like so:
{{Team outline|
{{Team outline content|Lushen|[[Guide:General supporter|General supporter]]
|Attack=2000
|CRI Rate=70%
|Speed=200
}}
{{Team outline content|Lushen|[[Guide:General supporter|General supporter]]
|Attack=2000
|CRI Rate=70%
|Speed=200
}}
|area=C1-G3 Arena
|useful for=End-game
|requirements=High
}}
Monster sections[]
After an overview table has been provided, users should add in detailed sections for each monster featured in the team. These should ideally be added as subsections below a "Core team" section. The Core team section should give a brief outline of what each monster's role to the team is.
When creating a sub section for each individual monster, one should provide suggested rune builds using the Template:SuggestedRuneBuilds template (see the link for instructions), with brief explanations regarding the choice in runes and stats.
If one has included option monsters, the same setup can be done below an "Options" section.
Other important sections[]
- General usage
- This section should provide general directions or instructions regarding the usage of the team.
- Strengths
- This section should outline the specific strengths of the team.
- Weaknesses
- This section should outline the specific weaknesses of the team.
- Variants
- This section should outline variations on the team comp. A table of different combinations can be provided.
- Additional notes
- This section should provide additional notes or caveats if requited.
Misc sections[]
- Videos
- A section with video demonstrations of the team will help players who like having a visual aid.
Submission box[]
To make the submission process as easy as possible, a page creation box has been added for user convenience. It is recommended that users edit the page in "Source mode". Simply type in the name of the build, and press the "Create" button to begin. Be sure to add the "Build" prefix, followed by the full name of the team comp, followed by "Team" (e.g. Build:Team - Double Lushen Arena). A new page with premade sections will be created automatically and ready for editng. Simply fill out the sections and after your ready, hit the "Publish" button. Be sure to follow the above guidelines, and check our example page as a reference. Feel free to add any additional sections that you think may be needed.
| Build Page Creation |
|---|
Adding the team comp[]
After the team page has been set up, users may add the team directly to the respective monster page, in the "Builds/Teams" section. Monster pages should already have some teams displayed there. Users may add their newly created unique team under the existing ones, following the same conventions as the other teams(team name, links, monsters, etc).
Team review[]
All newly created team pages will be subject to review from either an admin or moderator. Any team comps which don't meet community standards will be subject to deletion.
Post-review changes[]
Newly created team comps may be subject to further edits by both admin/moderators, as well as by regular users. Additionally, approved team comps will be also be added to relevant monster pages and other gameplay articles where appropriate.
Terminology[]
When builds are formally entered into monster pages, the following terminology should be used in the build tables.
| Term used | Guideline |
|---|---|
| All game | Reasonably obtainable runes that work throughout all stages of the game. |
| Beginner | Easily obtainable runes mostly used for set effects regardless of rune grade. Early to Mid game builds are under the Beginner category. Beginner builds are stepping stone builds that falls off later in the game. |
| Mid-End game | 4*-6* runes from shop or Cairos dungeon that are not ridiculous to obtain, with builds that may still be useful for late game content. |
| End Game | 5*-6* runes with amazing substats aimed at optimizing monsters for end game arena or dungeon auto speed teams. Builds are unsuitable for earlier stages of the game normally due to difficulty of obtaining the runes or high stat requirement. |
| Term used | Full name |
|---|---|
| Hp | Health Points |
| Atk | Attack |
| Def | Defense |
| Spd | Speed |
| CR | Critical Rate |
| CD | Critical Damage |
| Res | Resistance |
| Acc | Accuracy |