This Manual of Style outlines a standard of clean, consistent formatting for articles on the Tekken Wiki. The formatting described here is a guideline and can be overridden where circumstances warrant it. While these guidelines will not be perfect for every situation, please keep to the standard format outlined in this article so others may use your edits as an example when creating and editing other articles.
Reminder: To avoid spam, all users are to have a Fandom account with a confirmed email. (If not, that editor risks being blocked by the Abuse Filter.)
General[]
Every article should always start with the title of said article in bold font.
Grammar[]
Grammar is a writer's toolbox; you can't build good sentences without knowing how to use your tools. Since a wiki article must be as clear as possible for all the people reading it, editors must keep close to correct grammar standards to ensure clear communication. American English is preferred.
Capitalization[]
Always capitalize fighter's names (ie. Paul Phoenix), title of games (ie. Tekken 5), stages (ie. Last Day on Earth) and fighter moves (ie. Dragon Uppercut).
Titles[]
Italics are always used for the titles of the games, such as Tekken 4 and Tekken Tag Tournament 2.
Categories[]
Categories should be added to the end of an article - a full list can be found on Special:Categories. They take the form [[Category:Categoryname]].
Referencing[]
All information added to a page should paraphrase or quote a canonical Tekken source. Occasionally, reasonable speculation based on facts can also be added to a page, usually in the Trivia section. Canonical sources include text from within the mainline Tekken games, game manuals, official Japanese and English Tekken game websites, and, in some instances, Official Strategy Guides and information directly provided by Katsuhiro Harada, such as via his Twitter. A full list of canonical sources the wiki draws on can be found here. Trivia points may also draw from further sources, especially if they are not contributing directly to Tekken lore.
To add a reference, enclose the citation in the following code:
<ref> </ref>
If a page does not already have a section for references, you will need to add the following code to the bottom of the page so that all references are correctly displayed:
==References==
{{Reflist}}
A reference should contain a link to where the information has come from, either within the wiki or to a reputable source outside it, or, if unavailable online, should contain enough bibliographical information that the source can be verified by anyone else with access to the paper copy. E.g.:
A reference within the wiki: <ref>See [[Kazuya Mishima]]'s ''Tekken 2'' profile.</ref>
A reference to a reputable outside source: <ref>[https://www.tk7.tekken-official.jp/chara/ Official profile (in Japanese)]</ref>
A reference to an offline source: <ref>''Tekken 3 Official Strategy Guide''. Prima (1998), p32.</ref>
If one source is being used for multiple references throughout a page, a shorthand can be created for it using the following code: <ref name=" "> </ref>
For example,
<ref name="TK7 Official">[https://www.tk7.tekken-official.jp/chara/ Official profile]</ref>
would create a reference named 'TK7 Official'. After this reference name has been created, future references to it can be written as follows:
<ref name="TK7 Official" />
This shorthand will automatically link to the contents of the original 'TK7 Official' reference.
Article layout[]
One of the most important parts of wiki editing is how to structure an article. The structure is a powerful thing: it dictates what information the reader reads and what they see first. It can influence what people contribute, where it goes, and how it might be written. Structure has the power to inform or confuse the same way good or bad writing does. Keep a well structured article, and you're more likely to have a high quality one.
Organize sections in an article in a hierarchical structure like you would an outline. Keep it logical, but feel free to forsake strict logic for readability. Wherever possible, try to have an introduction for each section. Just like the article as a whole, the section should start with an introduction and then have its subsections below it. Try using a shallow structure rather than a deep one. Too many nested sections usually leads to a confusing or unreadable article.
Above all, keep your layout consistent. With that said do not change a set pages formats, unless you are given permission by a crat.
Stage Layout[]
Like all pages of the wiki, Stage articles are to follow a certain format. Shown below is an example of the Beach stage from Tekken 4. Notice how the image is to the right and a size 400 px, the video under Music is 300 px and the gallery is 200 px. This is the standard setup for every page. It is also important to mind the sections to make the page fill out as much as possible and to have an image big enough to maintain the format.
Character Layout[]
Character articles also have a very specific format, with an info box at the top of the source page, followed by a biography section, a story section subdivided by game, a gameplay section on the character's in-game mechanics, character relationships, and trivia. Story sections contain direct quotes from manuals and other in-universe canonical material and should be preserved as close as possible to the original sources. All direct quotations from manuals and in-game text should be in italics and manuals should be referenced, if possible.
Character pages will also direct to subpages for each character's outfits, gallery, and quotes (if relevant). Characters with a lot of information on them may have additional sections where necessary: see for example Jin Kazama, who also has sections for appearances in other games.
Trivia[]
Please note that trivia, like all information on the wiki, should be relevant and sourced. The only allowed 'similarity' trivia points should be officially stated as inspiration or noted as similar by a reputable Tekken source. Distinctive similarities between Tekken fighters and other franchise characters are allowed if the similarities are clear, but non-relevant trivia will be removed from the page.
Uploading Images[]
It is preferred that all uploaded images have a distinctive name and are of good quality. Small pixel pictures that are unclear or blurry, are not to be posted on any pages and will be removed. Clear and big pictures of high quality are essential and preferred.
AI generated or enhanced images are not allowed and will be properly deleted without warning. Similarly, no 'upscaled' images should be uploaded to the wiki. Only screenshots of official games and official promotional material should be uploaded to the wiki.
In addition, short, to the point, image names that explain what the picture is, are also preferred. For an example, a Tekken 6 photo of Emilie De Rochefort fighting Asuka Kazama at a stage could be entitled
"File:tk 6 lili vs asuka hidden retreat.jpg" or a render of a fighter from a game should be "File:T7FR Heihachi.jpeg".
Images with generic names like "File:King.jpg" or "File:Jin.png" are not allowed.
Gallery Layout[]
Gallery pages should be attached to the main page they are supporting. This is done by giving them the title Main Page/Gallery, where Main Page is the page they are hosting images for. A character gallery page is separated into sections by game, then further divided into 'Art and Renders' and 'Screenshots'. The former is for official art or models of the character, whilst the latter is for in-game images. Other gallery pages may have sections more relevant to the page they are supporting.
- Galleries are not to feature fanart. All images in galleries should be from relevant games or licensed associated sources.
- Galleries are not to be used to display personal customizations or modded items. The purpose of a gallery is to inform the viewer, not to provide a platform for fan content. In-game screenshots of characters are aimed to be informative, showing preset costumes of characters or other relevant visual information. Images that serve no informative purpose are, but not limited to, duplicates of existing images, use of custom mods, or player-made customizations and may be deleted.
- Certain exceptions to customizations or alternate outfits are allowed in the galleries. These are: Preset costumes (e.g: Tekken 7 preset costumes), Item moves (customization of other slots must be done minimally), item sets (e.g: Lili's School outfit parts in Tekken 6, DLC item sets in Tekken 7).
Note: Recolors of a single customization set do not count as multiple sets.
The layout on Gallery pages should consist of galleries subdivided by relevant categories. These galleries should have the same parameters as found on other pages. For example:
The fanart code places a reminder image not to upload fanart to the page. Then a heading for a game is given in italics, followed by the subsection which is bolded. Please use all the gallery parameters given here so that galleries maintain a uniform look across the site. These are as follows:
<gallery spacing="small" position="center" widths="200" captionalign="center">
</gallery>
Move Layout[]
Every move page needs to have a Move or Grapple template. It should be the first thing on a move article and the first thing shown in source mode. If the editor does not know all the information needed for the template, they should just fill out what they do know and not write "i dont know/idk". Leaving it blank will be fine. As stated above, all titles of move articles need to be bold. The default sections of the article should be Description, Usage, Trivia, Gallery. Though it should be noted this is just the default format and not every move page will have a need for each section.
The Infobox on the page should have a gif of the move, and may have a tabber showing the move in different games or performed by different characters. The command notation should be written in standard Tekken notation, details of which can be found on the Move Terminology page (please note the technical difference between capitalized and uncapitalized letters). Damage should be noted at 100% scaling. If a move gives damage for 120%, the editor should work out what the damage is for 100% and only provide this information. For hit range, the terms low, mid, and high should be used, unless a combo is being notated, in which case hit ranges can be abbreviated to letters (l, m, h) but is only highly recommended for moves with a high amount of hits (e.g: Gatling Rush).
After the Infobox, the page should begin with a brief summary of the move, indicating who the move is used by and what game the move was introduced, along with other brief, relevant details and move properties. The Description summary should give a clear, concise summary of the move being performed. If an editor is uncertain of what is occurring in a move, or unfamiliar with what terminology to use, it is better to leave this to an editor more suited to writing move descriptions. This also goes for the Usage section, which should be dedicated to explaining how the move fits into a character's toolset, along with technical details surrounding properties or move execution.
Should it be needed, the Description or Usage section may have a 'Variations' subheading, for variants of the move within a character moveset or between different characters.
Moves originating from stances require the full input including the Stance's abbreviation.
Trivia is for all other relevant information not immediately necessary for explaining the move and its technicalities. Moves that reuse a single animation e.g: (Lee Somersault & Crescent Kick Combo) should be mentioned. Moves that also have a distinctly similar function (e.g: Inferno & Hellfire Blast) can be mentioned in a "See Also" section.
The following images are move page examples:
Stance Layout[]
Stances are a subcategory under Moves and requires at least one tabber with the list of games that the stance has appeared in, and a second, if applicable, for moves that transition into that stance. Under the header will be a table divided into four columns:
- Move Name
- Command
- Hit Range
- Notes
Stances with a low counter that reuses an attack's animation (e.g Leaping Crane) must use that attack's name.
For command, the nickname or abbreviation of the stance MUST be present before the actual command. (e.g: Cheap Shot must be written as RFF f+3). It is recommended to use community resources such as rbnorway and the Move Terminology page if there are unfamiliar terms or jargon used. If an attack has an alternate, it is possible to use the same cell but placing "
" in between commands. For moves that transition to stances, it is required to put the FULL input to transition to the stance (e.g: Rude Boy's transition to Left Flamingo being LFF 4,3,f)
For Hit Range, all attacks, regardless of them being single hit or multi-hit strings, require ALL hits to be abbreviated to l, s, m, h, and ! to help conserve space.
The notes section should only contain added properties which include:
- Combo extending properties (Bound, Screw)
- Transitions to other stances what additional inputs are present if applicable.
- Triggers a special property (Homing, Tag Bufferable, Cancellable, etc)
- A short statement if a move was changed, reanimated, or had its properties changed due to a later patch.
- If the move is a throw, then the throw's break input.
Move properties column should NOT include
- Non-combo extending properties
- Frame data
- Crush properties
- Triggers a type of Stage Effect (Balcony Break, Floor Break, etc)
All these parts should be on that individual move's dedicated page.
Organization Layout[]
Example Pages: G Corporation, Violet Systems, Tekken Force (soldiers)
Organization or corporation pages should start with an Organization infobox template. The page should be laid out with a summary introduction explaining what they are along with, if possible, the logo of the organization as the main image. After this should come a 'Story' section, divided, if relevant, into sections by game. After this should come any subsections about the organization itself: first, any details about the structure of the organization and details such as their research and experiments; second, personnel, employees, or members. The next section should be for relations, or corporate relations, detailing external relationships of the organization with others. After this should come any other needed sections, followed by Trivia, Gallery, References. Each organization is different, so this guideline should only be used for a rough indication, and sections only added if relevant and necessary. The categories for an organization page should include Category:Groups and Category:Organizations (Tekken).
An example for how the page could be laid out is below:
Introduction to the organization (what is it, who is it run by, what are its main aims; corporate logo)
- Story (try to give a history only as it is relevant to the organization being described)
- Tekken
- Tekken 2 (etc)
- Structure
- Headquarters
- Facilities
- Research & Experiments
- Personnel
- Ownership
- Employees
- Military
- Relationships (Can instead be 'Corporate Relations' detailing only the organizations relations with other organizations)
- Stages related to organization
- Trivia
- Gallery
Outfit Layout[]
Example Page: Lars Alexandersson/Outfits
An outfit page should begin with a description of the character's overall general appearance without getting into subjective territory. If there is a main theme in the character's outfits throughout all of their appearances, this should go into the introductory paragraph as well. Underneath the headings of each game the character appears in should be a description of their Player 1, Player 2, and, if applicable, Player 3 and Player 4 outfits. Only default outfits have a bold heading. For outfits that are presets or sets able to be made via the customization screen, create a bulleted list. Trivia pertaining to the specific outfit should also go within bullets, while general trivia such as the DLC the outfits come from should be before the bulleted list. Be as descriptive as necessary when describing clothing and the positioning of items on the outfit (example: red shirt vs red, leather, button-down shirt. A design on the chest vs. a seahorse design on the left lapel, etc.). Information about generic customization items that pertain to all other characters is not needed. If the outfit set has a particular name, include this in the bulleted list before the description begins. Pictures should only be located in galleries and should preferably showcase the outfit without unrelated customization items.
- Lucky Chloe/Outfits - Example for a character that has only appeared in a single game.
- Lee Chaolan/Outfits - Example for a character with appearances as an alter-ego.
Writing[]
When you're editing wikis, you're both academic and artist. You have to be accurate, but you also have to be interesting. Neither one can dominate; you have to skillfully balance both.
Keep your writing concise. Don't use two words where one will do. Keeping your writing simple will make it easy to understand and easy to expand on. Use complete sentences whenever possible. When you write, use grammar as a toolbox: know the rules, but only break them on purpose.
Check your spelling and grammar. Do not use abbreviations, such as "u" in place of "you" or "2" in place of "to". Write the way you would for a class paper or a newspaper article.
Keep all of the topics you cover within the scope of the article. You don't need to give a detailed history of humans on the page about Winston Churchill. Consider the article's title as your point of origin and write from that perspective. Make use of the wiki's ability to link to more detailed articles or external sources for more information.
Write from an impersonal perspective. Do not use the first person. For example, do not write "this glitch occurs once a day in Tumbleweed, as far as I know". Do not use second person either; use of the word "you" is also to be avoided. Refrain from drawing attention to the author (yourself) as much as possible.
Be bold. If you know something is wrong, correct it. If you can word something better, correct it. If an article has a glaring deficiency, fill it. Even if your first attempt isn't golden, either you or someone else can fix it later. Don't be afraid to screw up.
Know the rules. Reading existing pages is a good way to get a general sense of the wiki's style, but the wiki is a work in progress - not all existing pages follow the rules... yet. Be sure to review the wiki's rules such as "Use Third Person".