Wikia

Final Fantasy Wiki

Final Fantasy Wiki:Manual of Style

Talk468
16,054 pages on
this wiki

This page will give an idea of how to write articles so they are consistent with many of the similar articles.

General Article Guide

  • Article title must follow the subject's official name, e.g. "Revolver" instead of "Squall's Weapon". It must also be written in Singular instead of Plural, e.g. "Gun" instead of "Guns" - exceptions are only when the article is a List, e.g. "List of Airships".
    • For characters, the character's name should be given with no title, unless to avoid tags, e.g. "King Horne".
    • For subjects without official names, please use the most accepted title - discussions encouraged - and place {{Nameless}} at the top of the article, e.g. "Grim Reaper".
  • Always include basic information about the subject when starting an article. The first sentence should detail the name, classification, and game (or compilation, or series if it recurs). In succeeding sentences, the place where the thing is found, what the thing looks like (or sounds like if it is audio), and its purpose within its appearance.
    • Articles should begin by the article's subject in bold, followed by {{J}}. This will bold the subject of the article and provide the equivalent in Japanese, a romaji transliteration and a literal translation, which should be added if not redundant. For example, '''Necron''' {{J|永遠の闇|Eien no Yami|Darkness of Eternity|Eternal Darkness}} gives "Necron (永遠の闇, Eien no Yami?, lit. Darkness of Eternity)". Pages that use infoboxes are exempt of this since the infoboxes already have sections for the Japanese term.
    • For gameplay articles such as enemies and items, the exact name must be used. For character and location articles, the full name should be used including titles, e.g. "Cecil Harvey".
    • If the subject is referred to by multiple names, these must be mentioned in bold followed by the situation, e.g. "Mikoto". If the subject has different names in different languages, these must be mentioned including the versions, e.g. "Rinoa Heartilly".
    • The "International Phonetics Alphabet" (IPA) guide should be mentioned on the introductory sentences; for voiced characters, in the sentence which notes the character's voice actor/actress. Pages that use infoboxes are exempt of this, since the infoboxes already have sections for the IPA.
  • When writing the article content, game titles should be written in italics, e.g. Final Fantasy IX and song titles should be with "quotation marks", e.g. "Prelude".
  • The definite article (the) and indefinite articles (a/an) should be avoided in article titles except if they are used as the official title.
  • Please write in third person: use "the player" instead of "you". Disregard this when writing walkthroughs.
  • Please avoid writing abbreviations for game titles, e.g "FFVII" - it should be "Final Fantasy VII", and gaming systems e.g. "PS" - it should be "PlayStation". Exceptions are for spaces where the full name would not fit.
  • Follow the official game title and use roman numerals, it's Final Fantasy III, NOT Final Fantasy 3.
  • Wikilinking is limited to the first occurrence of the word or phrase.

What should an article have?

This depends on the page. Some things are meant for some pages. Also remember that not everything in the series is entitled to a separate article. Please see the Article Creation Policy for the minimum requirements for articles.

For Games

Recent discussions point out that the game articles, the highlights of this Wiki, should be divided to:

  • the descriptive Intro, describing about the game in general. Some snippets from the content of the article may be written here,
  • the Gameplay, divided into subsections on the aspects of the game that makes it unique from the rest of the series. Links to the gameplay element pages, if any, should be linked too.
  • the Setting in which the story takes place. A link to the main/list location/world article should be added too,
  • the list of playable Characters including a short description. A collage of the characters picture would be a good addition,
  • the Story, written from the point of view of the player character,
  • the Music, describing the composition, composer, soundtrack, including main themes, adding in links to the respective music article,
  • Development, featuring important details on the creation and development of the game, featuring detail on:
    • Themes, describing the main conceptual themes and influences to the game's style and design,
    • Ports and Remakes, listing re-releases of the game in question and their changes,
  • Production Credits, listing the entirity of the staff/cast behind the game,
  • Allusions/Trivia, describing Internal and External Crossovers between the series as well as other series within popular culture,
  • the Packaging artwork gallery for each and every version out there,
  • External links; these pages should link to pages on important fansites (Final Fantasy Compendium or Caves of Narshe, for example), an official site (if one exists), and the GameFAQs page, as well as any other links that may be relevant (see Final Fantasy V for example).

Also, put the relevant wikilink as needed.

For Characters

All character articles follow the same format; however, many sections are exclusive to playable characters.

  • If the character is playable, an infobox designed for the game in which the character appears (see Category:Infoboxes for boxes).
  • An intro, which determines which games the characters is from and their role within the game and a brief explanation of the character in terms of setting and personality.
  • An Appearance and Personality to describe how they appear in their releases in terms of features and attire, and their personality and character within them.
  • A Story section about the role of the character in the series of events that involve them. Divided by events (e.g. early life), and also by game if the timelines do not overlap.
  • A Battle section if the character ever features in battles. Contains general information about their general battle style or job. Divided by release if the character appears with this information in multiple appearances.
    • A Stats sub-section if the character is playable and has unique stat information. For listing base stats, and stat growth data specific to the character.
    • An Abilities sub-section if the character is playable and has abilities specific or related to them. General discussion of abilities and links to the relevant articles for them are featured here. This includes all command and support abilities, including Limit Breaks.
    • An Equipment sub-section if the character has their own equipment not shared by every character or the release involves weapon proficiencies. Statement of weapon types and weapons equippable by the character are made here, and a link to the release's weapons article.
    • A Boss sub-section if the character appears in a boss battle. Mentions of when and where they are fought, and general comments on how they fight, as well as links to the boss pages are featured here.
  • A Creation and Development section describing behind the scenes work.
    • A Voice sub-section if the character appears in a voice acted game with audible lines. Mentions of the voice actor, comments on the voice, and a sample of the character speaking are featured here.
  • A Musical Themes section if the character has themes unique to them. Details said themes based on the soundtrack and in-game occurrences, with a sample of a version of their theme present.
  • An Other Appearances section if the character has appearances in releases outside of their original storyline but within the first-tier of the wiki's scope.
  • A Non-Final Fantasy Appearances section if the character has appearances in releases outside of the first-tier of the wiki's scope.
  • A Merchandise section if any official merchandise made for the character has been released.
  • A Gallery section featuring images relating to the character that show something but are otherwise not placed in the article. Larger galleries are often separated by game and made collapsible.
  • An Etymology section describing the etymological roots of the character's name, and alternative names of the character in foreign translations of the game.
  • A Trivia section describing any popular culture references or other information that does not fit into other sections.
  • An External Links section linking to official and informative resources relating to the character.
  • The navigation templates related to the character, ordinarily the templates for the releases they appear in, and potentially {{Characters}} if they fulfill the criteria.
  • The relevant categories associated with the character.

For Abilities

What constitutes an Ability article?

  • The Intro describing the ability in general, such as which job/skillset generally possesses it, and where the ability first appeared.
  • An Appearance section divided between every game title the ability has appeared before, whether as a status effect, magic, enemy skill or player skill, and listing every possible name the ability has appeared in every possible version of each title.
  • Place the navigation template related to the skillset or ability type, and don't forget to categorize them according to the relevant categories.

For Equipment

Equipment pages have:

  • An Intro describing the Equipment in general, such as which job generally uses it, and where the equipment first appeared.
  • An Appearance section divided between every game title the equipment has appeared in, whether wielded by the player or the enemy, and listing every possible name the equipment has been given in every possible version of each title, plus what attributes, elements or abilities are usually related to the equipment in question.

Place the navigation template related to the type of equipment, and don't forget to categorize them with relevant categories.

For Locations

Locations are usually given the fullest title used in their respective game. For example, the nation of Nabradia in Final Fantasy XII is usually referred to as such, and not as an individual city. Thus, the location page is titled Kingdom of Nabradia. Locations with the article "the" preceding the name are referred to without the article for Wiki organization purposes. Rationale is on Talk:Neverwood, and covers locations such as Bosco Pampa and Gapra Whitewood.

A Location article should include:

  • An intro, which determines which game the location is from, and summarizes its placement in its setting.
  • A Story section for events that occur at the location.
  • A Locations section covering how the location is accessed and its placement in the game's world, and featuring sections for each of the multiple sub-locations or sub-areas that compose the location individually. Descriptions of the setting, events, interesting dialogue, and items found with specific reference to location should be listed here.
  • A Quests section covering every individual subquest, sidequest, or minigame related with the location. In instances where a quest takes place over multiple locations, the quest should have its own article and be mained, featuring only information relevant to the location in question in the section. Item Farming and Blue Magic earned in the are also included here.
  • A Shops section covering the inventory and prices of shops found at the location. Should state the sub-location the shop is found in and link to the relevant place on the page.
  • An Items section listing every item obtained in the field, with the sub-location it is found and a link to the section given. Criteria should also be stated if it is not always present or accessible in the area.
  • An Enemies section for enemies found in the location, divided by sub-location. Most games have specific sets of enemies that appear, whether through random battles or visible on the field map. If so, the section should list groups of enemies, and potentially encounter-rates and battle-type information. Denote bosses with the unlinked phrase (Boss) following each linked enemy.
  • A Creation and Development section, when possible, describing behind the scenes work.
  • A Musical Themes section listing the tracks that plays in the location and when they are played. This includes music that plays during specific scenes that take place at the location.
  • An Other Appearances section if the location has appearances or references in releases outside of their original setting but within the first-tier of the wiki's scope.
  • A Gallery section if there are any useful images that do not fit into the article space.
  • A Trivia section if there is any additional information does not fit into any other section of the article (but we don't like Trivia sections).

For Enemies

Enemy Parent Pages

There are two approaches to this. First up is the Enemy Parent Page, made especially for enemies that are recurring in the series. The parent page contains:

  • The Intro describing the enemies' appearance, typical elemental affinities and status effects commonly used, if any, and notable subspecies,
  • An Image representing the general appearance of the enemy; typically, art is used to depict the enemy, but this is not necessary.
  • An Appearances section listing all the Final Fantasy titles the enemy has occurred in.
    • Add an image of the enemy described on the page,
    • Under each title is listed the enemy's appearance, its other variants, and traits of the enemy in the specific game.
  • Next is the Non-Final Fantasy Appearances section for games outside of our main Scope,
  • A Gallery that showcases images related to the enemy.
  • If not already listed in its Disambig, an Etymology section with an external link, preferably to relevant name origin websites such as Wikipedia.
  • Finally, a Trivia section for any tidbits of trivial information.

The {{enemies}} template should be included on enemy parent pages.

Individual Enemy Pages

The intro should say which game the enemy is from. If there is any relevant story info, add it in. Next, we'll include:

  • the enemy infobox designed for the game, if applicable (once again, see Category:Infoboxes for these boxes). This should be placed before the intro.
  • A Story section depicting its role in the story if a character page is not warranted (such as Astos).
  • Additional info on game-to-game basis:
    • In the case of Final Fantasy XII enemies, its Bestiary Info should be added as well. In the case of Final Fantasy XII Marks, information about location of the petitioner as well as the Mark itself should be added, the battle strategy, the reward and finally, the bestiary info (see Gil Snapper for example).
  • A Formations section if the game has battles that take place off the field. Stats based on battles rather than enemies are listed here, such as ABP in Final Fantasy V.
  • A Locations section which lists all the sub-locations the enemy appears in. Also lists which formations appear in those locations if they exist, or the amount or frequency of enemies in that area if enemies are found in the field.
  • A Stats section if the game in question has different stats per level and are not all displayed in the infobox.
  • A Battle section listing its battle attacks, movement and behavior. Additionally, a Strategy sub-section on how to beat it.
  • An AI Script section if one is known.
  • A Gallery section that showcases images related to the enemy such as artwork and enemy abilities.
  • A Etymology section.
  • A Trivia section listing trivial information.
  • Finally, a Related Enemies section, listing additional parts of a foe or additional enemies in a boss fight, palette swaps, and enemies with the same class and/or genus. Much better if there is already an in-game classification.
    • Should there be related enemies in more than one game in the same continuity (such as an enemy related between Final Fantasy X and Final Fantasy X-2), enemies from games other than the game the enemy of the page is should be listed under a sub-header within the Related Enemies section, sorted by game (See Adamantoise for an example).

A navigation template is not necessary for singular enemy pages, but categorize them according to the relevant enemy categories.

For Jobs

Again, two approaches for this: the Parent Page and the specific Job Page. The Parent Page will contain:

  • An Intro about the job's appearance in the series, with an overview of:
    • Abilities used, Weapons equipped, physical appearance of the job class,
    • the characters who have been in the job class.
  • An Appearances section, which list appropriate traits for the job as it appeared in each game that had a job/class system only,
    • Final Fantasy, Final Fantasy III, Final Fantasy V, Final Fantasy X-2, Final Fantasy XI, Final Fantasy XII International, and the Final Fantasy Tactics series.
  • If not already listed in its Disambig, an Etymology section with an external link, preferably to relevant name origin websites.
  • Finally, a Gallery that showcases Artworks related to the Job class in each title

Next, all individual jobs will have an article dedicated to it. This will be a little difficult since each Job in each game title is unique, so we'll just give a general overview:

  • The Intro should say which game the job is from. If there is any relevant story info, add it in.
  • All of its Abilities, placed inside neat tables with relevant statistics and color coding.
  • Finally, a Gallery that showcases Artworks related to the Job class.

Optional sections include:

  • An Appearance section giving a description on the job's costume design.
  • A Requirement section on unlocking Jobs - if and when the job needs to be unlocked.
  • An Equipment section, as seen in Final Fantasy III job pages.

Place the related job navigation templates in the individual Job pages, and don't forget to categorize them according to the relevant job categories; i.e. job parent pages get the Category: Jobs, while jobs of a specific game get the specific game and job category, e.g. Category: Final Fantasy Tactics Jobs.

For Status Effects

Make to focus on the status itself, not a spell that may share a name. A (Status) tag should differentiate the article from a related spell, and contain:

  • An Intro which describes the general consequences of the status effect and whether it is positive or negative.
  • An Appearances section, which lists the specific effects of the status in each game.
    • List all of the possible abilities, cures, items and any cause or relative of the status in a table.
    • This table should list, in order: the Game Element, its Type (Ability, White Magic, Weapon, Item, etc.), and its Effect.
  • A Gallery of characters under the status or status symbols.
  • Add the navigation template {{Status}} at the end of the page.

For Elements

Element pages are designated with the (Element) tag if another identically named page exists, and outlaid with:

  • The Intro should touch briefly on the element's history in the series, such as when it first was featured. The element's defining qualities and relationship with other elements should be mentioned.
  • A Recurring themes section that lists the element's representation by Abilities, Enemies, Equipment, and Summons throughout the series. This section should not list each example, but rather the most prominent.
  • The Appearances section lists each game that the element makes an impact in.
    • It lists any unique features of the element in that game that may not be as obvious or prevalent in other games.
    • A table listing all abilities, equipment, and items that are related to the element. The table should be ordered by Game Element (the thing that is related to the element, not the element itself), Type, and Effect.
    • The navigation template {{Elements}} at the bottom.

For Music

A substantial amount of discussion have been initiated in the past to decide ways of writing music articles. As recently discussed, music articles have two different approaches, depending on content:

For Albums

It has been discussed that pages for original soundtracks and albums should generally contain:

  • The {{Infobox Album}} template placed and completed before the Intro.
  • the descriptive Intro, describing the album in general. This includes any relevant information such as production staff, release date and retail price.
  • the Numbered Tracklist that includes track names in both Japanese and English, track duration and, if possible, a description on track recurrence. Should there be no track recurrence, prose may describe track characteristics i.e. composer/arranger/artist involved.
  • External Links that link first to official homepages, and then to any notable and relevant websites, such as, gaming news websites.

Place the navigation template {{Music}} and/or the relevant game template, if applicable, and the category "Music" and/or relevant game category as appropriate.

For Individual Tracks

Articles for individual tracks should contain:

  • The {{Listen}} template, which houses a sample of the track. Refer to Working with Media Files on working with music samples.
  • The Intro that describes the track in general, including composer and/or artist involved, its occurrence in-game and the soundtrack, and description of the music, including leitmotifs and other relevant tracks, if any. Subsequent paragraph may include development notes.
  • The Game appearances section, which covers each appearance of the track on a Final Fantasy game title, and detailing any appearances on a "Soundtrack" or "Soundtrack PLUS" album.
  • The Arrangement Album appearances section, which covers each subsequent original arrangement of the track on a Final Fantasy music album.
  • The Live performances section, which covers each individual performance of the song at a concert or tour.
  • The Compilation Album appearances section, which covers each subsequent appearance of an arrangement of the track on a Final Fantasy music compilation.

Place the navigation template {{Songs}} and/or the relevant game template, if applicable, and the category "Music" and/or relevant game category as appropriate.

For Achievement lists

As per most "List of" pages, a page listing the Achievements found in a game will be titled "List of [title] Achievements". However, if the game's achievements are titled differently, then replace "Achievements" with the different title. If two sets of Achievements are included with different titles, then both names should be included in the title (e.g. "Achievements and Trophies").

  • The opening intro must contain the number of achievements found within the game.
  • The first section should simply be List, as "of Achievements" is a tautology. It should contain a table with the following rows:
    • Name, a table header, the simple name of the achievement.
    • Icon, a 50px sized image of the achievement, but it should contain whatever image is common between all forms. For instance, with iOS and Android achievements; as the image in the picture is identical between both, that image should be used.
    • Description, the in-game associated description, using the quote class (|class="quote"|[description]).
    • Notes, explaining various information, tips for acquiring the achievement, and if the method of acquiring is ambiguous, contains details on how to unlock.
    • Value, if any achievements contain a certain value point; replace this with the value in question, for instance, Xbox points or PlayStation Bronze; if there are multiple values, include multiple columns for each.
  • A Gallery should only be included if there are valuable images of the achievements that are not found in the Icon row.

The navbox {{Achievements}} should be at the top of the page, as it is a sidenav. At the bottom of the page, the appropriate game navbox. The "Achievements" category should be used.

Game Order

When adding a game to an Appearances list or something similar, the standard order is detailed at the Scope policy.

When writing an article

Adding a Quote

It's encouraged to have at least one quote in every article. Use the {{Q}} for one-liners and {{RQ2}} for conversations between two characters. It's best to write the quotations under each Section.

Active Voice

The active voice is much stronger than the passive voice. Here is an example of a sentence in the passive voice:

  • Cecil was removed from his post as Captain of the Red Wings by the King of Baron.

Now, here is an example of that same sentence, except written in the active voice

  • The King of Baron removed Cecil from his post as Captain of the Red Wings.

See how the Active Voice is much better? The person performing the action is the subject of the sentence, instead of the person or thing the action is performed on. Action is better than being!

Verb Tense

To determine which tense to use in articles, it is logical to describe events happening in-game in the present tense; even if a game was released decades ago, it still performs the same today as it did on release. Therefore, to simplify:

  • Use present tense to describe plot and events as it happens in-game, including gameplay.
  • Use past tense to describe flashbacks and events that happen prior to the game's plot.

The same applies to describing real world events. When talking about game development, releases and/or promotions, use a tense appropriate for the time period in which the event occurred eg "The PlayStation was launched in 1994" or . When describing the product itself, use present tense eg. "Final Fantasy XI uses the concept of changing Jobs in a similar fashion to Final Fantasy III." Exceptions are for unreleased products that use future tense, and unfinished products that use past tense.

Spelling

There have in the past been edit wars over the territorial spelling of a word (i.e. words spelled differently in between Europe and the United States). It used to be that we're not arrogant and we have no intention on starting a territorial war over something stupid like spelling, and if you had come across a word spelled the way it is in another country (for example if you see "color" spelled as "colour" or vice versa), you would have left it as it is. I.e. the person who inserted the word initially will decide how it's spelled.

However, due to recent discussions on consistency, the community have decided that the "American English" spelling is the accepted language of the Wiki.

Point of view

On most Wikis, there is a policy to give a "Neutral Point of View" (NPOV). This is not the case here when writing story sections of specific articles. The point of view MUST reflect how the events unfold from the article's subject's perspective. For everything else, the article must maintain NPOV.

OMG Spoilers!

Following our Spoiler Policy, it's encouraged to place the {{Spoiler}} above content regarded as spoilers - this mostly being plot sections - and {{Endspoiler}} below it.

Categorizing

Each article must be categorized, and done so according to which category applies to it. Here in the wiki there are two types of articles; general and specific. General types are also known as parent pages; these contain links to articles that tell about a certain element of a specific game. For example; the Sage article, a parent page, is categorized under Category: Jobs, but the Sage (Final Fantasy III) article, a game-specific page, is categorized under Category: Final Fantasy III Jobs.

The idea is to place the game templates in articles related to the game - like the character articles, location articles, respective game-related terms. Other articles like magic, abilities and summons as well as enemies don't have them since they cover the entire series and not specialized. A list of categories can be found here.

Dates

When adding a date to an article, such as a release date, the standard practise is to omit ordinal suffixes (-st, -rd, -nd) and to use the MDY format with a comma following the day e.g. December 26, 2013. If a specific day has not been confirmed, a comma need not be used e.g. December 2013. This should be followed both in info tables and general article information.

When creating tables and infoboxes

For table formatting and markup, see Help:Tables

Some game specific articles may contain information that can be compiled into a table or infobox. Each game has a certain color swatch code for its table headers and subheaders. Instead of inputting the hexadecimal code for each color (bgcolor="#000000"), type in the class code for each game (class="seriesa"). The colors that correspond to each class code are listed in MediaWiki:Common.css, and are also provided further below for consultation. It is preferred that class codes are used.

The table below lists only the specific games that are more likely to have this kind of information; for other titles or compilations, refer to their individual navigation templates.

As for the style of a table:

  • The main row is given the header color, while the main column is given the subheader color. Both contents are centered. Use ! instead of | before each to automatically center and bold the header and subheader, bypassing the use of three apostrophes (''')
  • Wordings are in left-alignment, while numbers or very short terms are centered.
  • Remember to use the class codes.

Class codes


When making a template

Be sure to add an explanation of what purpose it serves, so that the other users of the wiki do not have to guess. This goes double for admins, since if they see no purpose or even possible future potential use for the template, it is likely to be deleted. The explanation can be written in a "Usage" header beneath the code of the template (which should be wrapped in <onlyinclude> and </onlyinclude>).

Talk Templates

You may have seen a number of users on the forum or on talk pages using templates to make their words appear in speech bubbles. If you want to learn how to create one of these, refer to the FAQ, and, if you're particularly creative, please remain within the guidelines for talk bubbles.

Working with Media Files

For the policy on media files, seek Project:Media

Adding Images

The general practice would be to start Image placement on the right side by adding "right" in the image coding as in "[[File:Example.jpg|right]]". The next image would then be placed on the left - "[[File:Example.jpg|left]]", forming a sort-of zigzag pattern.

An image without white/transparent backgrounds should be thumbnailed by adding "thumb" in the image coding as in "[[File:Example.jpg|thumb]]". A caption should be added to thumbnailed images, a short description of what the image is by writing the caption at the end of the code as in "[[Image.Example.jpg|right|Caption here]]".

Image galleries should be created when a number of images in a section clutter the layout. Image galleries should also be used with a caption to describe each of the images it contains.

{{gallery
|File:Example.png|Caption here
|File:Example.png|Caption here
|File:Example.png|Caption here
}}

On Music and Sound

The Template:Listen is used to help readers listen to an audio sample. While we have no specific guideline, template placement should be aligned to "right" or "left" accordingly. Standard practice is to put those templates on the left-hand side. Seek out the Audio help page for more information.

Embedding Video

When embedding a video from YouTube, it is encouraged to place them inside boxes. Place a caption and the caption box will be colored according to related header - follow game specific colors as above, or the series color if general. Video alignment follows viewer discretion and suitability. The coding below is an example, with those in double brackets being which parameters editors can customize.

To embed a YouTube video, use the following. For more details see Template:Video.

{{Video|[YouTube ID]|align=[align]|title=[title]|class=[class]}}

Around Wikia's network

Random Wiki