This article aims to provide a style guide for all articles in the wiki to follow. Although Wikipedia already provides a more general style guide, this article provides guidelines specific to THE FINALS Wiki.
There are often disputes over which style rule or formatting to use so an official style guide helps resolve these disputes and to reaching a consensus.
Content policy[edit | edit source]
Content on the wiki should generally reflect game content and mechanics as of the current patch. Exceptions to this are:
- Content that were previously available.
- Sections that display changes made to such content or display trivia that reference an older version of said content.
- Upcoming announced content. These should only contain information that are officially announced or shown by Embark Studios, Nexon or any of their partners. No leaks or datamining!
Datamining and Leaks[edit | edit source]
Datamining should only be used for information the is already available or previously available, never to leak or spoil future content. Do not add leaked content to the wiki. Make sure that the information you are adding is related to content that is currently or was previously available, or future content that has been officially announced by THE FINALS or Embark Studios.
Notability[edit | edit source]
Articles are only allowed in the main namespace if they fit the following criteria, otherwise they may be deleted without prior notice.
- Articles must contain enough information to warrant a full page. If they do not have enough content, they should be merged with other similar articles.
- Articles must pertain directly to THE FINALS in some way.
General[edit | edit source]
Documentation[edit | edit source]
Please add a summary of your edit by typing in the "Describe what you changed" field after saving changes to a page. This lets the community know what updates a user has made to a page, and makes it easier to recognize a user's specific contributions to the wiki.
Images[edit | edit source]
In most cases, images should only be used to enhance the understanding of an article, not simply decorate the page. Gallery modules should use the following settings: mode="nolines" class="scroll-gallery" widths="224px" heights="126px"
When taking in-game screenshots, it might be useful to hide your UI by pressing the F12 key. Optimal settings for taking high-quality screenshots are as follows:
- Full Epic graphics
- DLAA
- Low post-processing
Templates[edit | edit source]
All templates can be found under Special pages -> All pages -> Namespace: Templates. Directions on template usage can be found on its respective page. To create a new template, simply create a new page with "Template:" in front of the title. All edits to pre-existing templates should be heavily documented to avoid confusion.
Article titles[edit | edit source]
Article titles should generally be in the singular form, except in-game features with explicitly plural names.
Section titles[edit | edit source]
Section titles should generally be in plain text. Refrain from using wikilinks or putting references on the section titles themselves.
Writing style[edit | edit source]
Use a neutral, passive voice instead of addressing the reader directly. Be professional, informative, and concise.
Example:
Original: “Doing this will damage you and your teammates.”
Revised: “Doing this will damage the user and their teammates.”
proper terminology[edit | edit source]
Use terminology from THE FINALS brand guide and official announcements. Take careful note of capitalization and proper names. Limit usage of common gaming-related abbreviations and slang.
| Common Term | Proper Term |
|---|---|
| map | arena |
| character | build |
| player | contestant |
| kill | elimination/eliminate |
Example:
Original: “In The Finals, players can run around the map.”
Revised: “In THE FINALS, contestants can run around the arena.”
Example:
Original: “The sniper is available to the light build.”
Revised: “The SR-84 is available to the Light Build.”
Bias[edit | edit source]
Refrain from using biased language, especially in loadout pages. Do not use "the current meta" or similar language.
Example:
Original: “The Riot Shield is in a very poor state in the current meta…it just sucks.”
Revised: “The Riot Shield is a weapon that can be easily punished, but also has strengths when utilized correctly.”